One piece flow: operator has to pass process just like the product

Question

question

Christian M20 asked Oct 20, '22 Christian M20 commented Oct 21, '22

One piece flow: operator has to pass process just like the product

Hi all,

like in a standard lean management process setup for one piece flow I need to create a process with several Multiprocessors in a line. Starting from a queue a first operator picks a product, transports it to a processor#1, sticks with the product and passes it to the second processor#2 and so on until the product is finished. ANOTHER operator in the meantime also starts picking a product from the queue and transports it to the processor#1 (if free for another operation), sticks with the product and passes it to the second processor#2 and so on until the product is finished.

So, basically I want the operator to accompany the product through all of the processes and not switching tasks whenever he is free. I tried with tagged resources but it throws an error as soon as the same operator is required to do the transport AND an a process.

If you have any simple to use ideas, please let me know.

Best regards,

Chris

Software Version:

FlexSim 22.2.0

lean manufacuring one-piece-flow

5 |100000

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

Answer 1 · 2022-10-20T13:24:52Z

Jason Lightfoot answered Oct 20, '22 Christian M20 commented Oct 21, '22

Put a label on the part that points to the operator and reference that in all transport and process dispatchers. Use a list of available operators to choose one for the first OP and then push them back to the list when finished.

Also used with agvs in this answer

· 2

5 |100000

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

Lucas Antonio Risso commented · Oct 20, 2022 at 06:00 PM

Interesting idea, thank you for sharing.

0 ·

Christian M20 commented · Oct 21, 2022 at 12:40 PM

Thanks for the quick response. It works just like I needed.

0 ·

Answer 2 · 2022-10-20T17:59:54Z

Lucas Antonio Risso answered Oct 20, '22 Christian M20 commented Oct 21, '22

Hi Christian,

I have implemented Jason's insightful idea in a sample model, which you find attached.

Please, vote on his answer, and not on this one.

Notice that each operator has a set label command on the trigger "On load". Then, the processors and queues call the resource based on the label set.

Operator-label.fsm

operator-label.fsm (38.9 KiB)

· 1

5 |100000

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

Christian M20 commented · Oct 21, 2022 at 12:43 PM

Hi Lucas, thanks for the model. I got rid of the Dispatcher and used a task executor list just like Jason mentioned. Otherwise the operators use their idle time to transport and label new items.

0 ·

question