question

The keyword you are looking for is a tagged operator. A second approach is to place a dispatcher for each operator in your model. This dipatcher is connected to first input port of the operator. At the moment the operator gets a transport tasksequence to a separator he sends a message to the separator. You have to insert this task previous to the unload task in the transport tasksequence wether at the creation or later when the operator receives the tasksequence. The message will tell the separator to dispatch the new created tasksequences to the dispatcher connected to the first input port of the delivering operator. This references can you set in a label when the message is received. To identify the sender you use the command msgsendingobject(). If the utilize tasksequence is already in another tasksequencequeue you have to transfere this sequence also to the same dispatcher connected to the first input port of the operator. The utilize tasksequence is responsible for letting the operator assisting the unpack process.

The inserted dispatcher is a storage object especially for the connected operator. Because the dispatcher is connected to first input port the operator looks for new tasksequences first at this dispatcher. But it is necessary that all tasksequences belonging to the separation process getting to this dispatcher.

Don't use centerport connections or any other code references to reference the operator directly, this will disturb the search for new tasksequences at connected dispatchers. This means you can add more or different dispatchers to operator.

The attached model contain my 2nd approach. I had to add delay task to the tasksequences to let the Flexsim engine build in the background the tasksequences for the utilize task and the transport task. Otherwise the Operators don't find at their own dispatchers instantly the next task to do. The delay time can be really small.

Could you please explain more exactly what you are looking for? Am I right, that never more then 2 Operators are working at the same time? When does the next Operator get the Job to Transport another item?

You only have to know that Standard is, the Tasksequence is created and dispatched as soon as the items are available in the "Operation" Queue and a place is available in the target Queue. Than the Tasksequence is sended to Dispatcher, which starts searching for a free Operator.

My first idea is to just use 2 Operators instead of 4, if 2 are never working anyway, why connecting them to the Dispatcher!?

Another idea would be to add a Queue with max Content 1 behind your Operation Queues. Close the Input and just open it as soon as the next Transport is allowed to search for a free Operator. In this case every Queue is allways sending max. 1 Item.

I´m quite sure there is another cool solution by using ProcessFlow, but at first we Need more Informations.