Critical Timer for queue

Question

question

Dustin B asked Mar 1, '23 Dustin B commented Mar 2, '23

Critical Timer for queue

I had hope to use an object sub flow to send items that had "expired" while waiting in queue to a dedicated discard queue. However, it looks like due to simulation timing, items are being processed and discard simultaneously. ie. The output from the pre-processed queue is greater than the input.
Is there another trigger / set up I can use to avoid this from happening?
I would prefer not to use multiple pre-processor queues to achieve this if possible.

Thanks,

Dustin

230103 Crit Timer.fsm

Software Version:

FlexSim 23.0.3

queue logic object flow

230103-crit-timer.fsm (104.6 KiB)

Answer 1 · 2023-03-02T00:41:14Z

Kavika F answered Mar 2, '23 Dustin B commented Mar 2, '23

Hey @Dustin B, you can use a Max Wait timer on the "Wait for Event" activity to send tokens that took too long down a different path.

At the bottom of the Wait for Event activity, you'll see a check box "Use Max Wait Timer". Check it, set the max wait time, and what to do when that time is reached.

As you can see from my above example, on normal behavior, it will continue through; however, on failure (i.e., reached 5 minutes wait time), it will move the box into the Critical queue.

(I sped up the model so it may look like it doesn't wait that long, but it does)

230103-crit-timer_1.fsm

1677717437580.png (23.5 KiB)

1677717450110.png (6.1 KiB)

box-wait-too-long.gif (235.9 KiB)

230103-crit-timer-1.fsm (105.0 KiB)

· 3

Dustin B commented · Mar 02, 2023 at 03:33 PM

This seems to work. The 3D model is correct, although the tokens on the subflow don't seem to add up, but I don't think that's necessarily an issue?

0 ·

Kavika F ♦ Dustin B commented · Mar 02, 2023 at 05:20 PM

True that the model seems to have the correct amounts in the queues. After digging into the model a little more, I notice that all of the stats get reset at around time 10080 in the model, right when /DSTech in for Day Shift and starts cleaning.

I found some interesting behavior where if you put a model stop time at 10079 model time, fast forward to that time, press skip (to end up at 10080 time), then hit run/fast forward, the statistics behave as expected. Otherwise, they get reset.

Stats without the above method:

Stats with the above method:

I will investigate this further to see what could be the issue. Thank you for pointing this out!

0 ·

1677777547130.png (41.5 KiB)

Dustin B Kavika F ♦ commented · Mar 02, 2023 at 05:55 PM

Yes, that would make sense. It seems the warm up timer is resetting the counters in the 3D model, but not the object flow.

0 ·

question