Please make pickup points behave like dropoff points

Question

question

Osman Eralp asked Oct 19 2016 at 12:08 AM Eric M commented Aug 11 2021 at 5:31 PM

Please make pickup points behave like dropoff points

I have noticed that pickup points behave differently than dropoff points. Specifically,

1. When an item is delivered to a dropoff point, it shows up in the queue that the point is attached to. That is good. When an item is created at a queue with a pickup point, the item shows up at the pickup point. That is not so good. This creates the odd behavior of items on AGV tracks:

I think the item should be in queue until it is picked up.

2. When an item is delivered to a dropoff point, the AGV goes to the point with the highest priority. That is good. When an item is create at a queue with a pickup point, the item is created at the pickup point that is closest to the queue, and thus that is where the AGV goes. That is not so good. Compare this image with the last one:

I moved the queue and the item appears at a different point.

In summary, at pickup points, I would like to see the item created in the queue, and the AGV should stop at the unoccupied CP with this highest priority. This would be consistent with the behavior of dropoff points.

Software Version:

FlexSim 16.2.1

agv agv process flow drop off dropoff

screenclip.png (44.1 KiB)

screenclip2.png (45.1 KiB)

· 1

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2016-11-14T18:37:40Z

anthony.johnson answered Nov 14 2016 at 6:37 PM Eric M commented Aug 11 2021 at 5:31 PM

The pickup points implementation was designed to be essentially a mirror of the dropoff points implementation. When there are pickup points, the item moves from the queue to the pickup point, then is loaded by the AGV. When there are dropoff points, the item is unloaded from the agv into the dropoff point, and then eventually moves into the queue. You don't see the items in the dropoff points because you've left the dropoff retrieval time at 0, so the dropoff retrieval process happens in 0 time, and the item is moved immediately into the destination queue.

If you don't want the queue to actually move the items into the pickup location, you can change the Item Pickup section to not do that. The logic there selects a pickup point (Get an Available Pickup Point) and then moves it into the pickup point (Move Item Into Pickup Point). You could remove the activity that moves it into the pickup point, and instead assign a label named pickupPoint to the item that references the selected pickup point. To do this, add an Assign Labels activity with an Assign Labels To of Label: item, and a single label assignment with the name pickupPoint and a value of Label: pickupPoint (this copies the selected pickupPoint from the token to the item itself). Then in the load logic change the agv's destination from wherever the item is held to the item's pickupPoint label (in Travel to Pickup Location change Destination to getlabel(getlabel(token, "item"), "pickupPoint"), i.e. the pickup point that was assigned to that item.

Also, in selecting a pickup point (Get an Available Pickup Point), I set the default query to ORDER BY distance, simply because I didn't know a good prioritization what would work for everyone. If you want to prioritize different, you can just change that query. You could add "priority" labels to each of the pickup points, and then use a query like ORDER BY priority DESC.

· 2

Riccardo P3 commented · Aug 05 2021 at 7:14 AM

I try to implement this solution, it's possible that I get something wrong, because in my model with this modifications the AGV template don't work correctly. I would like to use the AGV advanced template, but I want to eliminate the movement of the load unit on the pickup point and leaving it in the assigned location (on the rack or processor for example) when the agv go to pick up it.

If Someone is able to give me a hand, I will really appreciate.

AGv_Test3.fsm

0 ·

pickuplogic.png (33.4 KiB)

agv-test3.fsm (4.4 MiB)

Eric M Riccardo P3 commented · Aug 11 2021 at 5:31 PM

Hi @Riccardo P3, there were just two additional changes that needed to be made both in the Item Pickup section. In the "Wait for Item to be Loaded" activity, instead of referencing the pickupPoint, I changed this to token.item.up because the item isn't leaving the pickupPoint anymore, it's leaving whatever its container is (which the ".up" returns). I also added an Assign Labels activity in the "No" branch of the "Does CP have Pickup Points" activity. Because the rack doesn't have pickup points, the AGV didn't know where to travel in order to load the item. I copied the original Assign Labels activity and just changed the value from token.pickupPoint, to token.item.up.

agv-test3-em.fsm

0 ·

agv-test3-em.fsm (4.6 MiB)

Answer 2 · 2016-10-19T22:07:44Z

Sam Stubbs answered Oct 19 2016 at 10:07 PM Joerg Vogel edited Oct 22 2016 at 5:49 AM

Your issue is that you were using pickup point connections. The pickup points are what's causing the item to be placed at that point. If you just want them to remain in the queue, simply have the queue connected to the points you want it to be connected to.

· 2

question