Combiner - Combine/Process based on label

Question

question

Håkon L asked Nov 25, '22 Håkon L commented Nov 25, '22

Combiner - Combine/Process based on label

Hi!

I am trying so simulate a rather compelx production line, or rather the production flow.
In this case there is a machine which processes some items, and combines (joins) other items.

I've added my file, the machine in question is M57, and here is a more detailed description of how I think it should work:
IF Label on flowitem = 035236 Process item in 0.5 hours and move to Queue 035236_1
IF Label on flowitem = 0352361 Process item in 0.75 hours and move to Queue 035237
IF Label on flowitem = 005657 or 039940 combine (JOIN) in 3 hours with the other and move to Queue 005659

How do I set the combiner up to be able to both process and combine based on the label on the flowitem? Secondary how doI set up the processing times also? - They are different based on labels.

In advance - thanks for all the help, it is greatly appreciated!

JobShopRoute V0.7.fsm

Software Version:

FlexSim 22.2.2

combiner pulling from lists

jobshoproute-v07.fsm (45.7 KiB)

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-11-25T10:52:58Z

Joerg Vogel answered Nov 25, '22 Håkon L commented Nov 25, '22

Update component list On Entry trigger does this efficiently. Items entering by Port one which doesn't need any components to join simply gets a zero in update components list column by label value. I attach a simplified model taking into account that any item Type can enter a combiner through port 1 but only Types 2 and 3 can be used to get joined if Port one Type is Type one. To distinguish joined and not joined items I assign a label called "joinedType" and I use it with a send to expression to divert it to green and blue queue. Process time is different is a matter of port by case.

If you need a better adjusted process time then I suggest to use setup and process time to evaluate differently joined Types. This has not been implemented so far.

Process_join_and_not_combiner.fsm

combine-or-not-combine.jpg (53.5 KiB)

process-join-and-not-combiner.fsm (33.2 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.

Håkon L commented · Nov 25, 2022 at 03:00 PM

Thank you very much Joerg! Awesome! I think this is just what I am looking for, I do however need to take a better look at how I would set my own code up, for my specific case. If you want to contribute even more i posted this as a new question: https://answers.flexsim.com/questions/131982/code-for-pull-requirement.html

I will however continue to try and figure it out by myself in the meantime, and I will have to look at this some more during the weekend. Best of wishes to you! Again - thanks!

0 ·

Answer 2 · 2022-11-25T10:26:13Z

Felix Möhlmann answered Nov 25, '22

I would suggest to just use a processor for all timed processes and combine the two components that have to be joined ahead of the processor in 0s.

For the different times and directions you can use the "Values By Case" option. Since that is not available for changing the label after processing that can be done in a simple code snippet.

jobshoproute-v07-fm.fsm

1669371873393.png (89.2 KiB)

jobshoproute-v07-fm.fsm (45.7 KiB)

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.

question