Operator walk times

Question

question

A Kamphaus asked May 26, '16 Mischa Spelt answered May 27, '16

Operator walk times

I'm working on a model where I have some operator walk times that are part of a standard work time. I would like to find a way to put in these times in a manner where I would tell the operator walk to nodeX in 7 secs, or walk to nodeX in 4 sec then nodeY in 3 sec. What would be a good approach to doing something along these lines?

Software Version:

FlexSim 16.0.1

operator walk times

Answer 1 · 2016-05-27T08:04:37Z

Mischa Spelt answered May 27, '16

I recently had to do exactly this, I used distancetotravel to find the calculated distance along the network, and then just set the maxspeed variable of the operator to distanceToTravel / desiredTravelTime. Only thing to keep in mind is that your network may restrict the speed, you should double click the network nodes and make sure that the Speed Limit is not set lower than the calculated speed.

Answer 2 · 2016-05-26T15:58:33Z

bill.strong answered May 26, '16

There are a couple possible options:

I am attaching a small model that I created where the operator travels exactly three seconds from the pickup queue to the dropoff queue. The operator then travels back to the pickup queue in exactly six seconds. This is accomplished by setting the operator speed to 1000 fps and the acc/dec rates to 0 (instantaneous acc/dec). The speed limit for the connection from NN1 to NN2 is set to 10 fps and the current distance is 30 so it takes exactly 3 seconds to travel from NN1 to NN2. The speed limit for the connection from NN2 to NN1 is set to 5 fps and the current distance is 30 so it takes exactly 6 seconds to travel from NN2 to NN1.

A virtual distance will also work, which is probably the best way to go in case nodes get accidently moved around. If you want to make the travel times variables you could create a global table with all of the different path segments listed in the table that you want to make variables. All of the virtual distances could be modified in this table and reset before running the model in order to modify the travel times between nodes. I am attaching another version of the sample model with these modifications included. The reset trigger on each node is where I set the virtual distance for each path segment. I also added macros for referencing each path segment.

operator-times.fsm (18.9 KiB)

operator-times-1.fsm (19.5 KiB)

question