I want to make the operator to transport the batch items sequentially to the queues in storage Area #1 for the purpose of the operator's shortest moving distance.
But I found the loading sequence to be different from the exit sequence from the queue.
I want to know followed;
1) the operator's loading sequence of items
2) how to control the unloading sequence of the items.
The best way to control all aspects of a TS is to create a manual task sequence. Attached is your model with the changes that I've made to it. Basically, I gather all the flowitems from the main queues (Queue70 and Queue69) then travel to each of the storage queues. I use a sub task to check at each storage location to see if there are any flowitems to drop off. If there are, they get dropped off. If not, it goes to the next storage queue.
Would a solution like this work for you?
Thanks.
You don't really have to "sort" the two main queues (upper ones in model are not sorted) and it will still drop them off in order of the storage area queues. It just looks a little funny because it will pull items from the transporter leaving "gaps" in the remaining flowitems. But it will still work. Not sure which way would work for you the best.
Yes. According to your manual script, the main queue do not need the sort script onEntry trigger. If the transporter load the items as exiting sequence from main queue, the transporter unload the items sequentially to the storage queues?
The transporter's arbitrary loading default sequence is funny and some ridiculous.
Only manual sequence can solve this problem?
Yes. Thanks. That's my want. But...
I want to know why the transporter not to load the items according to the exiting sequence from the queue.
What's the default sequence logic when transporter loading items? Why does the transporter load items arbitrarily with ignoring the exiting sequence from queue?
Manual tasksequence like yours is the only solution about my issue?
When you think about how queues work, it's not so ridiculous. Queues handle incoming flowitems immediately upon entry. The queue knows what order each flowitem entered. That is the order that the queue will handle incoming flowitems. It doesn't matter if you "sort" the queue after a flowitem enters or not. The queue will still handle (load) the flowitems in the order they entered the queue. And moving them from one queue (after sorting) to another, still does not change the order they entered or will be processed.
So, to get flowitems to load/unload exactly how you want then to when they don't come into the queue in the right order, you have to use a manual task sequence to handle that. You can probably do it easier with Process Flow than with a manual task sequence but if your not using PF a manual TS is the only way that I know of.
Attached is your model (well, part of it anyway) with the changes that I made to use Process Flow instead of a manual task sequence. Maybe this would be more to your liking?
7 People are following this question.
© 1993- FlexSim Software Products, Inc. All Rights Reserved.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
