How to monitor parts of distances travelled by operator (with AStar)

Question

question

Sabrina S asked May 27, '21 Eric M answered May 28, '21

How to monitor parts of distances travelled by operator (with AStar)

Hello,

I would like to measure the distance an operator walks, not as a total distance travelled but in partial routes, e.g.:
From Queue1 to Processor1, from Processor1 to Queue2, from Queue2 to Queue1.

I am using the AStar. The aim is to show the distance and the number of times the operator used this part of route in the dashboard (e.g. as a table).

Can somebody help me how to build this up please? Thanks a lot in advance!

Software Version:

FlexSim 21.0.5

astar flexsim 21.0.5 distance

· 1

Joerg Vogel commented · May 27, 2021 at 09:00 AM

You will probably get only the total traveled distance. But you can compute the distance from destination to a next destination. Each time an operator has reached a destination by a traveltask, load task, unload task, pick offset task or pick offset unload task you write the destination object and the total travel distance into a table and you compute the difference to the previous entry.

The command distancetotravel returns only the theoretical distance to an object and not the actual walked distance.

1 ·

Answer 1 · 2021-05-28T23:34:19Z

Eric M answered May 28, '21

Hi @Sabrina S, like Jörg said there's not currently an automatic way of doing this. I've made a demo model that does what Jörg suggested in writing the distances to a table. First, I create labels on the operators that give a measurement of how far they've gone by recording the "pre-travel" distance and the "final" distance and finding the difference between them. Each time the operator repeats that travel activity, the distance is added to the previous distance using the "increment" feature of labels. As you can see, each travel activity need two sets of labels, one to record the initial value of the total travel distance and one to record the final value and calculate the difference. The operators then have a "on finish task" trigger that writes the value of the labels to the table "TravelDistances."

Hopefully this helps you see one way that you could do this (I believe you could also bypass the labels entirely and only record the data in the table, but labels seemed more straightforward to me).

dist measurements by type.fsm

dist-measurements-by-type.fsm (76.1 KiB)

question