Arrival Schedule from source to two queues one arrival at a time.

Question

question

Ken L3 asked Nov 9, '20 Ben Wilson commented Nov 21, '20

Arrival Schedule from source to two queues one arrival at a time.

Stator New - Stage 3_Schedule.fsmI am trying to build one source that will build based on a arrival schedule. I would like only one arrival per queue. The quantities are different each arrival so I cannot set limits to queue size. Essentially, i would like the source to send one arrival at a time to the first available queue with no partial pieces/order and only one order at a time.

Software Version:

FlexSim 20.0.0

flexsim 20.0.0 arrival schedule flow production schedule

stator-new-stage-3-schedule.fsm (13.7 MiB)

· 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.

Ben Wilson ♦♦ commented · Nov 21, 2020 at 05:03 PM

Hi @Ken L3, was tannerp's or jason.lightfoot's answer helpful? If so, please click the red "Accept" button on one of their answers. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

0 ·

Answer 1 · 2020-11-13T12:37:24Z

Jason Lightfoot answered Nov 13, '20 Jason Lightfoot edited Nov 13, '20

Here's a working model example using a List for the queue availability. Just add new queues to the group "Queues".

SendOrderToQueue2.fsm

sendordertoqueue2.fsm (36.5 KiB)

· 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.

Jason Lightfoot ♦♦ commented · Nov 13, 2020 at 01:41 PM

Updated to check the queue is empty before waiting for an exit event.

0 ·

Answer 2 · 2020-11-10T02:07:35Z

tannerp answered Nov 10, '20 Jason Lightfoot converted comment to answer Nov 13, '20

@Ken L3,

You might consider using Process Flow. I created a small example model that creates random small orders with varying sizes and sends it to a random queue.

In the example, the tokens are created randomly and then receive a label that represents a random number of items to create ("numberUnits" label).

Then, the "numberUnits" label is used to create that number of items. The queue where the items are sent is decided randomly based on a percentage.

You could also send all the items into a third queue that would then sort based on "First Available", as that seems to be an important criteria in your model.

I'm not sure if I entirely understood your question, but I hope this is on the right track and that it gives you some ideas. I'm attaching my example model for your reference. If I'm off target, please provide some more details or perhaps an example and I'll try to help.

random orders.fsm

1604973903473.png (14.5 KiB)

1604973980442.png (37.3 KiB)

random-orders.fsm (26.8 KiB)

· 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.

Ken L3 commented · Nov 10, 2020 at 01:59 PM

I was hoping there was a way to avoid the process flow but that is okay. So with your example the interval arrival is what is driving the delivery of the box. From there you are saying I could take a step further and send to a third queue as first available. Would the first available pull one order at a time or just "x" qty of pieces? I guess because it will be in process flow, it would have a token per unit not per order?

0 ·

question