Unload items at once and priority in processor

Question

question

Paúl Alejandro R asked Aug 21, '18 Joerg Vogel commented Aug 22, '18

Unload items at once and priority in processor

Hello. Please, somebody could help me with the following issue?

I the attached model, I have two operators which a load capacity of 50 and 100 items, respectively. They unload at Queue 2; however, they take a great amount of time to unload the items. I need the operator unload all item at once. Also, I am trying that processing in Procesor 1 be the most importat task develop by operators, so I increased its priority to 10000. Eventhough, none of the operator leave to load items to processing. Is there a better way to achieve that processing in processor 1 be the most important task for one of the operators, while the other one continues load items?

Thanks in advance.

example.fsm

Software Version:

FlexSim 18.1.1

priority unload items

example.fsm (26.1 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 1 · 2018-08-22T06:38:24Z

Joerg Vogel answered Aug 22, '18 Joerg Vogel commented Aug 22, '18

A priority P1 set to 2 is greater than a priority P2 set to 1. If FlexSim evaluates the priority then the task sequence with P1 will get executed previous to the tasksequence with P2. The value difference isn't important. There are only some automated generated task sequences, that use a priority set to a similar value like 10001. Those task sequences are the result of the command stopobject. You shouldn't use on your own priority values near such high values, because the model may behave a bit strange.

The unloading doesn't consume time, if you don't set an unload time. What you see at the queue and what takes time, is the offset travel of the operator to the next location to place the item. The stacking is a parameter of the queue. If you set the Item Placement to Stack Vertically in the queue the operator unloads the items at the same location.

Alternatively you can add a path network in your model and set the option of the taskexecuter to Do not travel offsets for load/unload tasks.

You use a dispatcher to transfer and store the task sequences. An operator can load more items at once, but the operator must know where the task sequences are to find. Please open the properties of the operator and edit the Break To function in the template editor and choose the Object queueing tasksequences to the second option current.inObjects[1].

· 2

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 22, 2018 at 02:09 PM

example-2.fsm

Thanks @Jörg Vogel for your answer. Please could you explain me a little more about what you mean with P1 and P2 and the values 1 and 2. In the second attached model, I made the changes in the properties of the operators. However, as you can see the processor is waiting for an operator, but I need one of the operators to stop loading items from Queue 1 to Queue 2 and work processing in processor 1.

0 ·

example-2.fsm (26.2 KiB)

Joerg Vogel Paúl Alejandro R commented · Aug 22, 2018 at 04:12 PM

Please look for the keyword tagged resource to keep an operator at a processor. If you want to build a special logic, you should try ProcessFlow to manage the begun tasksequences at the operators and not transfered tasksequences.

0 ·

question