question

Raashid Mohammed avatar image
0 Likes"
Raashid Mohammed asked Adrian Haws edited

How to send operators to heavy boxes area

HI

I have 3 conv and 3 Trailers queue

Each Conv gets loaded by boxes by label value type

conv1 - 50%

conv2 - 25% conv3 - 25%

each conv to trailer load and unload can have only 2 operators max

I want the operators to start at heavy boxes area then move to the other conv queues

Please help see attached model

@Adrian Haws helped me make this model

having batch process does not help me to scale it to larger model

Is there any other way to have operators go to heavy zone first

Thank you operatorworkingwithshifts.fsm

Choose One
process flowlisttask sequencezonepriority
operatorworkingwithshifts.fsm (46.1 KiB)
· 6
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.

Adrian Haws avatar image Adrian Haws commented ·

@Raashid Mohammed Just to clarify, heavier boxes will always go to one queue (for example, Conv1), and all of the other boxes are the same weight? Or do you need operators to go to the queue with more boxes, then to the other queues?

0 Likes 0 ·
Raashid Mohammed avatar image Raashid Mohammed commented ·

@Adrian Haws

No, It varies by volume. as simulation time progress the value changes sometimes is conv1 or sometimes is conv2 or 3

Thanks

Raashid

0 Likes 0 ·
Adrian Haws avatar image Adrian Haws Raashid Mohammed commented ·

@Raashid Mohammed So basically the priority will always be to have two operators loading at the queue with the most boxes at the time, correct?

0 Likes 0 ·
Raashid Mohammed avatar image Raashid Mohammed Adrian Haws commented ·

@Adrian Haws

Yes that is correct

0 Likes 0 ·
Show more comments

1 Answer

Adrian Haws avatar image
1 Like"
Adrian Haws answered Adrian Haws edited

Hi Raashid,

I apologize for the delay in responding to your question. I believe I've found one way for you to accomplish this logic in your Process Flow.

I actually changed how the model works. Instead of pulling boxes and deciding which operator to load that box, we'll be pulling operators then deciding where to pull the boxes from. The operators will then loop around, similar to how you originally built your model. Some of the tricky issues that had to be worked out had to do with assigning, reassigning, and destroying labels.

There are a few different things I did with the model layout, but you can change how exactly you have it set up. I'll just explain the main thing that solves this problem, then if you would like to ask any other questions about this sample model feel free.

Essentially there are two conditions that must be met in order for an operator to be "assigned" to work at a set of queues. First, there must not already be two operators working there. Second, of those available queues it must go to the one with the most boxes. The most important piece of this logic is found in the Decide activity called "Most boxes?" I wrote some custom code that may look like a lot (and it's possible it can be simplified), but that's basically what it does. It first looks at the content of each queue, then at a set of Process Flow labels that tell how many operators are currently working there. Model is attached.


raashid-model-5.fsm (75.3 KiB)
· 1
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.

Adrian Haws avatar image Adrian Haws commented ·

@Raashid Mohammed Here is a slightly different way of organizing that code that may be easier to follow and change in the future. It first looks at whether or not more operators can work on a queue, then whichever one has more boxes, then if one of the queues is empty.

0 Likes 0 ·
raashid-model-6.fsm (75.4 KiB)