Flow configuration

Question

question

Isabel P asked Jul 15, '21 Jeanette F commented Aug 22, '21

Flow configuration

Hello,

I need your help to configure the workflow of an operator preparing picking, the idea is that once the work order is assigned, the operator randomly loads the products, moving in a straight line along one side of the rack and then returns by the other side of the rack, also moving in 1 direction only. In the attached file, the operator moves in a U from one side of the rack to the other removing the products he needs, adding unnecessary movements and erroneously increasing the preparation time. Antofagasta_2OP_3Pasillos_Optimista_TA.fsm

I am using version 20.0.6 and License "Express"

Software Version:

Choose One

Software Version:

Other (please specify)

Software Version:

Other

configuracion flujos de trabajo workflow

antofagasta-2op-3pasillos-optimista-ta.fsm (81.8 KiB)

· 1

Jeanette F ♦♦ commented · Aug 22, 2021 at 03:38 AM

Hi @isabel.p, was Eric M's answer helpful? If so, please click the red "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

0 ·

Answer 1 · 2021-07-21T18:34:05Z

Eric M answered Jul 21, '21 Eric M commented Aug 9, '21

Hi @Isabel P, I added a travel network to your model to get the operators to move in one direction around the rack. I also changed the load activity to a move object activity. This means all the objects will be moved into the operator at one time, but I figured this tradeoff would be worth it to get the travel right.

I also condensed your process flow a bit to free up room for 3 travel activities that I would have needed (condensed down to one in attached model). The logic works by using 1 list with a partition for each rack. Because the decide activity was using round robin, I used the token creation index to determine which rack the operator should go to (important labels created in Assign Labels activity). These labels are used to determine the locations, list partition, and how many tokens should be created in the subflow. Let me know if you have any questions!

antofagasta-2op-3pasillos-optimista-ta em.fsm

antofagasta-2op-3pasillos-optimista-ta-em.fsm (85.5 KiB)

· 11

Isabel P commented · Jul 21, 2021 at 09:25 PM

Hi @Eric M, thank you very much for your help!

Regarding the direction of the operator's travel, it was just what I was looking for, however it still does not reflect what I need, that is, that the operator advances along the rack taking boxes from each location until completing the total of his work order (OT), so that you can see the time difference between a preparation of 100 boxes versus another of 300.

With the current model, the number of boxes requested does not matter, because the operator advances to the end of the rack, takes the total and returns, taking the same delay even if it takes 50 or 500 boxes. This is the most important thing for me, to simulate the preparation times according to the number of boxes requested in his OT.

Any ideas on how to achieve this? At least the "round robin" setting did generate that difference in time preparation, but the "U" movement was wrong.

I hope I have explained more clearly what my question is.

Thank you for your support!

0 ·

Eric M Isabel P commented · Jul 22, 2021 at 05:26 PM

Here's a model that does that. It pulls random items off the list and stores their rack / bay / slot / level. These items are put in a table (AddressTable1 and 2) and then sorted and shown in GlobalTable1 and 2 which correspond to operator 1 and 2. They are sorted in a way that will make the highest bay number get picked first using the Table.query command (see here). These sorted items are then stored by the operator in the cajas label. Now, the operator goes and loads one item at a time along his path in the desired order. I split the rack in half and gave each rack a label (RackN) which is 1 or 2 depending on which comes first in the travel.

This is just working for Operator 2 on PasilloC. You'll just need to split the other two racks in half and include the labels. Then move the correct Assign Labels activity back into the flow (Assing Labels: real), and fix the resource to reference the group of operators. Please note that the placement of the nodes is important because the operator will go to the closest node to the item when loading it. In the example, you can see that the nodes are placed very close to the center of each bay. Let me know if you have any questions.

antofagasta-2op-3pasillos-optimista-ta-em-1_2.fsm

0 ·

antofagasta-2op-3pasillos-optimista-ta-em-1-2.fsm (116.0 KiB)

Isabel P Eric M commented · Jul 23, 2021 at 02:31 PM

@Eric M, thank you so much, that was exactly what I needed the operator to do!

I just have a question, how do I modify the number of boxes that the operator must take from each rack? For example, if he wanted him to take 100 from rack C, 200 from D and 300 from E.

Thank you very much for your help!

0 ·

Show more comments

Eric M commented · Jul 29, 2021 at 10:46 PM

1. You could make it so the operator "delays" at every node (or however many nodes you would like) by adding the nodes to a group and then using an event triggered source in process flow. You would then probably need to use a Create TS with a priority > 0 and preemption set to "preempt only" and then a TS delay and then a Finish TS. That would make it so the Operator's time was the same whenever he went around the rack (some variation could be added to the delay too). Changing the operator's acceleration and deceleration time to 0 would also make it so the operator wouldn't stop while loading boxes until he gets to a node you want him to stop.

2. The operator is loading items from the closest node. You'll notice that the box he's loading when he comes back around is an item from the opposite rack. To fix this, just move the nodes so they are more evenly spaced around the rack. In the image below you can see the bottom is much closer than the top.

Just as a note, I would point you to this section of the manual that talks a bit about the Express License. Just keep in mind that because the random number generator is fixed, your results won't be statistically valid. You can always contact your local FlexSim distributor if you would like information on obtaining a more functional license.

Let me know if you have any more questions!

0 ·

1627598068029.png (11.4 KiB)

Isabel P Eric M commented · Aug 02, 2021 at 09:24 PM

Hi @Eric M ,

I already adjusted the position of the nodes and now it works fine giving only 1 loop around the rack, however what you mentioned in #1, I did not understand it very well.

What I need is the operator to walk the length of the racks, pick up requested boxes, and the time it takes to be a function of the boxes he should take.

I'm not sure if assigning a delay per node is the best solution, because in that case the time will be a function of the route and it should not take the same time for the operator to collect 50 boxes versus 150.

Please if you have any additional suggestions on this point and help me understand that configuration, I would greatly appreciate it.

There are also some errors that appear to me that do not interrupt the simulation, but I would like to know how to eliminate.

Thanks!

Corregido Flexsim_006.fsm

0 ·

corregido-flexsim-006.fsm (141.6 KiB)

Claudia S4 Isabel P commented · Aug 08, 2021 at 09:39 PM

Add more nodes Isa. Nodes are the key, because operators pick the boxes from the closest node. If you have one node per bay, the operatos is going to pick all the boxes from the bay when he arrives to the closes node, either 1 or 20. corregido-flexsim-006.fsm

However, I don't know how to fix the initial errors when you open the file.

@Eric M do you know how to fix it?

0 ·

corregido-flexsim-006.fsm (702.1 KiB)

Show more comments

question