Nathan H5 avatar image
1 Like"
Nathan H5 asked Ryan Clark commented

Tasks still assigned to off shift resource

I have an operators group where the operators are on time table schedules. I am using the travel to location and then delay function for when the resource goes off shift/on break. For some reason my resources that are off shift are still getting tasks assigned to them, so the task has to wait until the resource starts their shift to be processed. How do I make sure that only operators that are on shift are getting tasks assigned to them.

FlexSim 21.2.4
resourcesscheduled down
· 5
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Joerg Vogel avatar image Joerg Vogel commented ·

Add a cascade of dispatcher in your model. A dispatcher belongs to each group and then when the operators get into off shift the dispatcher stops by timetable, too. A supervisor dispatcher controls transfer of taskesequences by default send to function first available to assigned group dispatchers. This approach works only if tasksequences are created continuously over run time, otherwise you have to empty group dispatcher tasksequencequeue if they go down and transfer them back to supervisor dispatcher.

0 Likes 0 ·
Nathan H5 avatar image Nathan H5 Joerg Vogel commented ·
If I am using process flow to create a custom task sequence for my operators, am I still able to use dispatchers in this way?
0 Likes 0 ·
Joerg Vogel avatar image Joerg Vogel Nathan H5 commented ·
This depends on how you dispatch tasksequences. If you activate and use “wait until complete”, then you can’t work good with dispatchers. Then you have to divert or preempt your involved token, release your resource and acquire another active resource.

Process Flow Tasksequence option mimics a tasksequence, but it dispatches only one task tasksequences into your Taskexecuter and then it calls the process flow again.

If you create a tasksequence as a treenode bound complete sequence which you dispatch at a last activity step, then you can work with dispatchers. But this approach is not part of tutorials yet. You don’t need to acquire a resource for this approach, because dispatchers will do this instead.

0 Likes 0 ·
Show more comments
Ryan Clark avatar image Ryan Clark commented ·

Hi @Nathan H5, was my answer helpful? If so, please click the "Accept" button at the bottom of my 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 Likes 0 ·

1 Answer

Ryan Clark avatar image
1 Like"
Ryan Clark answered

Hi @Nathan H5,

I don't think that your query suggestion would work, but you should be able to use preemption logic in your ProcessFlow to accomplish what you want. See Preemption ( for more information on how to do this.

As an alternative to this, you could add some logic to your "Break" section of your process flow. As the operator is going on break, you could acquire the resource associated with that operator, then execute the travel to location and delay activities. Then, when the break has concluded, you could release the resource to make the operator available for other tasks.

I hope this helps! Let us know if you have further questions!

5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.