Tracking the time it takes for dispatcher to find available operator for task?

Question

question

Noah Z asked Aug 8, '16 Jordan Johnson commented Aug 8, '16

Tracking the time it takes for dispatcher to find available operator for task?

capture-dispatcher-wait-time-for-task.fsm

I'm wondering if there is a way to have a model provide output stats on how long it takes a dispatcher to successfully send out a task sequence to an available operator? Even more useful would be if I could pull out average wait time before the task was sent out to an available operator by center port of the dispatcher. This would allow me to gauge the impact that putting priorities on certain tasks has on creating bottlenecks at other system points.

I've attached a dummy model that is personnel constrained (1 operator and three processors with fast arrival rates).

Software Version:

FlexSim 16.0.1

dispatcher wait time getstats

capture-dispatcher-wait-time-for-task.fsm (21.4 KiB)

Answer 1 · 2016-08-08T20:50:52Z

Jordan Johnson answered Aug 8, '16 Jordan Johnson edited Aug 8, '16

capture-dispatcher-wait-time-for-task-2.fsmWith Process Flow, you can get this information fairly easily.

You can listen to the Dispatcher's OnReceiveTaskSequence event, and create a token in response. You can assign the task sequence to a label on the Token. To get the object that possesses the task sequence, you can use the findownerobject() command. Using this command, you can find out which dispatcher received the task sequence.

The token then waits for zero time. If the dispatcher can immediately assign the task sequence to one of its task executers, then that will happen while the token waits on the delay activity. The next activity uses the findownerobject() command to get the current owner of the task sequence. The token then enters a zone, which I will explain later.

The token then checks to see if the current owner of the task sequence (the operator) is the same as the first owner (the dispatcher). If they are the same, then the task sequence has not been assigned, and the token needs to wait for the task to be assigned. In this model, you can wait for the OnResourceAvailable event (be sure to make sure that the token's task sequence is the Next Task Seq in the event; use the match option). If they are different, then this task has been handled, and we don't need the token anymore.

This model collects two statistics. The Staytime statistic on the Wait For Start activity records the staytimes of task sequences that had to wait to be assigned. The Staytime statistic on the zone records the staytimes of every task sequence, even those that didn't have to wait. Both values might be important.

capturedispatchtime.png (17.7 KiB)

capture-dispatcher-wait-time-for-task-2.fsm (28.6 KiB)

· 1

Jordan Johnson ♦♦ commented · Aug 08, 2016 at 10:59 PM

Previously, I had posted an answer that had bad information. If you read that answer, disregard it.

0 ·

question