question

Theresa B avatar image
0 Likes"
Theresa B asked Theresa B commented

Using Dispatcher vs. Acquire TE from a Group

Hi, again, another Dispatcher/Process flow question from me - but theoretical this time!

I've seen 2 kinds of implementation around:

  • using a dispatcher to organise the dispersal of resources (and assign multiple operators to a processor) around a model
  • creating a group of task executers and acquiring the requisite number in an Acquire Resource activity


Is there any difference between doing it one way or the other?

I assume if you were not using Process Flow, you'd use a Dispatcher for the organisation of several Task Executers; would you bother using a dispatcher rather than creating a group of TEs and drawing from that list?

Thanks in advance!


FlexSim 22.2.0
processflowdispatcherobject group
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

1 Answer

David Seo avatar image
1 Like"
David Seo answered Theresa B commented

Using dispatcher object in standard library is more easer than using TE resource group like TE List. You should make a custome logic for using an available resource among the TEs group.

· 4
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

Felix Möhlmann avatar image Felix Möhlmann commented ·
To add to this:

In my mind, the dispatcher is simpler to use, but as a trade-off, is a lot more restricted in how it can be used. If your goal is just "some operator needs to do single, independent task somewhere" with a relatively simple heuristic to decide which operator out of group of available ones should be used, then the dispatcher is a perfectly fine method to achieve this.

As soon as tasks get more complex (for example involve multiple steps in a certain order) or the rules that determine who should do them have multiple restrictions, a Process Flow with a resource or list will end up easier to use.

1 Like 1 ·
Theresa B avatar image Theresa B Felix Möhlmann commented ·
Thanks for both your responses!

To clarify, Dispatcher is easier to use for the listed heuristics for "Pass To" and "Queue Strategy", otherwise I would need to design my own "Dispatcher" by creating a group of Task Executers.

I know that "Find Slot" is a built-in activity that I can use to find a specific slot using SQL; is there a similar thing for TEs in process flow, or would this be a chunk of custom code?

0 Likes 0 ·
Jason Lightfoot avatar image Jason Lightfoot ♦♦ Theresa B commented ·
You can use query syntax in pull from lists and acquire resource activities in process flow
1 Like 1 ·
Show more comments