How to assign same operator when using Task Sequence Sub Flow

Question

question

Yunjukuo asked Aug 12, '22 Yunjukuo edited Aug 13, '22

How to assign same operator when using Task Sequence Sub Flow

(Fail to upload FlexSim model, please click link to download model:

https://drive.google.com/drive/folders/1IQkPBcbQ_uMSLKw0PJIYXPDZ0RJHIzYe?usp=sharing )

Process2 of MultiProcessor is a process that requires operator to go to the Material_Room to get material and travel back to MultiProcessor to add material. I tried to use "ProcessFlow: Use Task Sequence Sub Flow" to complete this function but have following problems:

1. The operator assigned to each action is different, for example operator1 goes to the Material_Room to get material, but operator3 add material. The situation I want to practice is that Operator1 will continuously do the get material and add material actions.

2. If this process sometimes requires two operators (when the amount of material is large), for example: Operators 1 and 2 go to get material and add material together, how should the Sub Flow be modified?

3. How to set task preempt, priority when using Task Sequence Sub Flow?

In addition, my real model is very large and complex, and I hope to keep using Dispatcher to dispatch operators. If I dispatch operators by Process Flow might cause a lot of trouble.

I'm using FlexSim 2016.1.2, but I also attach 2022 version incase only few people using 2016.

Software Version:

FlexSim 16.1.2

operator task sequence subflow

1660266682776.png (128.8 KiB)

1660266705991.png (62.9 KiB)

1660266728595.png (16.7 KiB)

Answer 1 · 2022-08-12T08:01:25Z

Felix Möhlmann answered Aug 12, '22 Yunjukuo edited Aug 13, '22

The answer to all three questions is to use "Create TS". When you use the dispatcher as the task executer in each individual process flow activity, a new task sequence is created for each task and passed to the dispatcher who then again passes it on to an operator based on its "Pass To" logic. Instead, if you first use "Create TS" a task sequence is created and written to the specified label on the token. This label can then be used as the task executer reference in subsequent task activities, so the same operator that receives the task sequence from the dispatcher will do all of the tasks.

You can also use this to create a second, parallel task sequence with another token, to coordinate tasks between the operators. Note that, when there might a pause between two task activites, insert a "Wait for Task" task into the sequence via the "Custom Task" activity.

Building this logic is easier in later versions that 16.1 that contain the "coordination" activities. The Synchronize activity makes managing parallel task sequences much more straight forward. (Not sure when exactly those were added)

The following link should allow you to download the modified model.

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

1660291050363.png (19.0 KiB)

1660291071463.png (44.1 KiB)

1660291198104.png (3.0 KiB)

· 1