Sujit avatar image
Sujit asked Sujit commented

Operator work as per priority in batch production


In my attached model, Operator 1 should work as per priority and in batch quantity. now he is working as per availability.

The priorities are as below,

Work on Processor3 till he finishes the batch of 5 pieces. Then if 2 parts are available in Queue9 then Operator1 should transfer the parts to Queue3, work on those 2 parts one by one and then transfer to Queue4. Then pick those 2 parts from Queue4 to Queue 10. Then only he should return to Processor3.

Refer attached model.sample model for operator sequence.fsm

Thanks in Advance.

FlexSim 23.0.4
operator control
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

Felix Möhlmann avatar image
Felix Möhlmann answered Sujit commented

This has been suggested to you before and will do so again here. Please consider using Process Flow for process sequences like this. That or generating the needed task sequences manually via code are the only really feasible options to implement a logic in this form (do sequence A X times, then, under some condition do sequence B).

In the attached model I demonstrate how this can be done. I deactivated the 3d model logic for the involved objects by disconnecting them from each other and unchecking the various "Use Operator" options. The queues 6 and 9 push their items to list. A token in the process flow tries to pull the required number of items from this list. If successful it will run through each step one by one and finally loop back to pull the next batch.


· 3
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Sujit avatar image Sujit commented ·

Thank you so much... it is working... But Operator is climbing on the processors though I have given the network node. Also operator is walking towards Queue 10 and then return to Queue 9 instead of directly going to Queue 9 ( this is if I connect to network node - without it, operator is working in correct manner )

0 Likes 0 ·
Felix Möhlmann avatar image Felix Möhlmann Sujit commented ·

When using a travel network you have to insert a travel activity every time the operator has to move to another network node to do the next action. See example below: First travel to processor1, then unload. Because the next load activity also happens at processor1 no travel is needed. But before unloading to the Queue it is needed again, if the queue is connected to a different network node.


If you don't want the operator to move away from the network nodes to load/unload items, then choose the option "Do not travel offset for load/unload tasks" in its properties.


0 Likes 0 ·
1679130482012.png (9.8 KiB)
1679130598821.png (10.1 KiB)
Sujit avatar image Sujit Felix Möhlmann commented ·

Thank you so much.... Now working as per my requirement...

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.