Here is a model that does what you want:
order-picking-by-orderno-v2.fsm
It has this process flow:
This flow creates one token per row of the global table. Then it uses a batch to merge tokens from the same order into a single order token. The order token acquires the operator.
Once the order token has an operator, it is ready to begin picking. To do picking, the order token creates one token per SKU. The SKU token creates one token per item of that SKU, which is the pick token.
Each pick token tries pull and item from the list that has the correct SKU. Once all pick tokens have pulled an item, the pick tokens are then batched into groups of up to 10 (the operator limit), and merged into a single token, which represents each trip the operator must make to pick the order.
For each trip, the trip token creates a task sequence that travels to and loads all the items, travels to the staging area, and then unloads all the items. Then, this task sequence is dispatched to the operator. Some orders will require multiple trips, and so will end up creating multiple trip tokens. The operator will do task sequences in the order they are received.
My guess is that you will want to modify and expand on this model. Before doing that, I recommend making sure you understand how this model works fully before proceeding.
The issue is that the direction the racks face is important to A*. I rotated Rack2 180 degrees, and the operator now travels more sensibly:
order-picking-by-orderno-v3.fsm
Type a product name
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement. 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.
