Operators support each other

Question

question

Fengjun0113 asked Aug 31, '22 Jeanette F commented Sep 6, '22

Operators support each other

This is a Flexsim 2016 model. In this model, I want to make:

1. Operator1 in charge of Multiprocessor1 and Processor1.

2. Operator2 in charge of Multiprocessor2 and Processor2.

3. When Operator1 is idle, he will support Operator2. Once the item goes to either Multiprocessor1 or Processor1, he will go back to his work immediately (when he is laoding item to next station, he will finish loading first then go back to his work). Operator2 will finish the rest processing time.

4. When Operator2 is idle, he will support Operator1. Once the item goes to either Multiprocessor2 or Processor2, he will go back to his work immediately (when he is laoding item to next station, he will finish loading first then go back to his work). Operator1 will finish the rest processing time.

(Dispatcher is removable if it is not needed)

https://drive.google.com/file/d/1AksGKkqM9wAtx5bM8eCQ2tMrR9E2NzFe/view?usp=sharing

Software Version:

FlexSim 16.1.2

operator dispatcher support

1661907649510.png (102.2 KiB)

· 1

Jeanette F ♦♦ commented · Sep 06, 2022 at 12:41 PM

Hi @Fengjun0113,

Your product is at end of life. Please contact you local distributor to upgrade your software. FlexSim releases newer versions of its software 3 times a year, so there are a substantial number of improvements and new features in the upgraded version.

was Felix Möhlmann's answer helpful? If so, please click the "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 · 2022-08-31T07:20:55Z

Felix Möhlmann answered Aug 31, '22 Fengjun0113 commented Aug 31, '22

You could push the task sequences to a list, partitioned by the areas (1, 2). In a process flow, each operator can then first try to pull a task in it's area and if none are available it checks for tasks in the other area.

For the transport tasks, the option to push them to a list is available by default in the "Use Transport" option.

The process tasks have to be pushed to the list in code. A quick approach is to use the "Example Task Sequence" option and adjust the code to:

A: create the task sequence in the processor itself, so the dispatcher doesn't interfere with the process flow logic
B: push the created task sequence to the list, instead of dispatching it directly.

In the case of the multiprocessors, you also have to free the operators in the "OnProcessFinish" trigger.

The zone in the process is there to make sure that each operator can first try to pull a task in "their area" before the fallback option is used.

Operator support each other_1.fsm.pdf

(Rightclick on the file attachment -> Save Link/Target As (might be called differently depending on the browser) -> Set "Save as type" to All Types -> Save with a name ends with .fsm)

1661930195024.png (10.0 KiB)

1661930246457.png (45.5 KiB)

1661930269115.png (17.1 KiB)

1661930335213.png (29.2 KiB)

operator-support-each-other-1fsm.pdf (28.7 KiB)