Prioritizing the operator

Question

question

Trex asked Aug 27, '16 Paúl Alejandro R commented Aug 17, '18

Prioritizing the operator

Hello guys, I have a problem in prioritizing the operator. As I have 3 processors and 3 queue. I have attached the operator with centerport to all the queues. But I want the operator to follow a certain sequence, that isn't working with me as I have provided the priority in each queue under the flow transport box. here each queue have different items. Parts are always available on all the queues. I want the operator movement to be as : Queue 1 --> processor 1 ---> travel to queue 3 and take the part from queue 3 --> processor 3 ---> travel to queue 2 and take part from queue 2 --> processor 2.

If I can do it with task sequence do let me know, how should I do that. Thanks in advance.

Software Version:

Choose One

task sequence operator assignment priorty flow transport

· 1

5 |100000

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

Paúl Alejandro R commented · Aug 17, 2018 at 06:25 PM

Hello, I tryed to use the model suggested by Brandon Peterson in a model created in Flexsim 18.1; however, it does not work properly because the lenguage is deprecated. Somebody can tell me how to update it? Thank you

0 ·

Answer 1 · 2016-08-31T15:04:52Z

Brandon Peterson answered Aug 31, '16

Trex,

Here is a sample model that uses a TaskSequence List. The Queues create task sequences for the operators and place them on a list with the Partition ID being equal to the queue number (1,2,or 3). The Operator has a OnResourceAvailable trigger that pulls from the list with the partion ID being equal to 1 plus the remainder of the operator's input divided by 3. This essentially causes the operator to pull from queue 1, then queue 2, then queue 3, then queue 1 and so on. If you want to change the sequence you could do so by changing the code for the partition ID.

Another alternative to using the partition ID would be to use the query field of the pull from list GUI in combination with a field on the list.

Good Luck,

Brandon

task-sequence-list-v2016-1-1-mv-1.fsm (19.2 KiB)

5 |100000

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

Answer 2 · 2016-08-30T18:29:19Z

Adrian Haws answered Aug 30, '16 Adrian Haws edited Aug 30, '16

Here is just a different way of looking at it, without any custom code. You can connect all of the queues to another queue, and set the pull strategy to be Round Robin. Then determine which of the processors that queue will send to based on a label that was set in each of the original three queues. See example model.

operator-transport.fsm (19.3 KiB)

5 |100000

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

Answer 3 · 2016-08-29T07:20:19Z

Aditya Prakash answered Aug 29, '16

If you want to do it using just priority, then here's a easy but not so elagent solution. Basically I'm just decrementing priority of each queue at it's OnExit trigger. And since by default tasksequence queuing strategy is priority based , operator follows the assigned order of events. prioritzing-operator.fsm

prioritzing-operator.fsm (19.6 KiB)

5 |100000

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

question