question

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.