Hi I have some operators connected to Dispatcher 1 and different ones connected to Dispatcher 2.
I would like the operators connected to Dispatcher 1 be able to work on tasks of Dispatcher 2, but ONLY when they're idle.
I have done some search (https://answers.flexsim.com/questions/108980/how-to-pass-task-to-correct-dispatcher-when-operat.html) but I am unable to find a solution.
Seems like a simple problem, could you please help?
Hi @Lambert, was one of Felix Möhlmann's or Long G's answers helpful? If so, please click the "Accept" button at the bottom of the one that best answers your question. 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.
I think a "Pull logic" where the operators decide which available task to work on next would work better in this case.
You can implement this by having the processors push the tasks to a list and pull them in a Process Flow by tokens that each represent one operator. To distinguish between the groups, you can push the tasks to different partitions. The tokens first try to pull a task from their own group, if not successful they see if other work is available.
For multiple groups of operators, using partitions can get cumbersome, since you can only ever try to pull from one partition at a time.
An alternative approach is to write the task group to the list as a push argument (added directly to the push command in the processors' operator field code at line 36).
Tokens can then compare their value to that of the list entry and sort by whether they match or not when pulling a task sequence.
Hi, I have a follow up question if I may.
Is there a way of forcing a dispatcher assign a task to a specific operator based for example on an operator label?
In other words, I have 5 operators connected to one dispatcher moving items from queues. I want 1 specific operator of those to be the only one able to pick up items from a different queue.
thank you!
I think of for example a tag tasktype to be inserted in your transport task to distinguish between your different travel destinations.
For Example: Operator3 is connected to output port number 4 of a dispatcher. He should load all transport task from Queue C. Then you can insert a tag task to all your receiving tasksequences at this dispatcher. First parameter is by default e.g, 25 or any other number and for loadstation Queue C is it 2. In Pass To function you evaluate the first parameter of tag task in Port by Case picklist option. Case 2 returns for output port number 4 a 4. And any other case are returning by default statement a value of 0 which is interpreted as any available port.
This approach can you enhance to connect at output port number 4 another dispatcher, which is connected to other or already used operators to filter different conditions for tasksequences. In Pass To function the option first available or in source code a return 0; statement chooses to pass tasksequences to availble taskexecuter by order of output port connections. See @Jason Lightfoot comment on this above.
If you had pushed all tasksequences to a list you can naturally filter the list by customized expression fields and control transfers of tasksequences this way. Each list properties has got an Advanced Tab to insert fields to evaluate different attributes of pushed value. Those field values can you use to choose a distinct value from a list by matching conditions. In your case you push as a list value your tasksequences.
I've never done anything like that.
Thanks again
The TAG task type is (to my understanding) mostly useful if you build custom task sequences with a varying amounts and types of tasks in them. A tag can then be an easy way to distinguish between them.
If you only use the dispatcher to assign task executers to transport tasks that were generated by fixed resources you can generally rely on the format being the same for all tasks. (Travel, Load, Break, Travel, Unload in that order)
So in the "Pass To" field you can access any determining features directly. For example the destination would either be "involved1" of task 4 or "involved2" of task 5.
In the attached example, all items going to Queue3 must be transported by Operator3. Others use the "First Available" method ("Pass To" returns a 0).
16 People are following this question.
© 1993- FlexSim Software Products, Inc. All Rights Reserved.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
