I am modeling some transport routes using GIS Navigator and I would need the trucks to take a variable time (according to a probability distribution) to complete the journey.
In the route settings I can only set the duration of the trip or the speed of the task executer .
Hi @Filippo C5, was one of Phil BoBo's or Sara Bonansea's answers helpful? If so, please click the "Accept" button at the bottom of the one that best answers your question. 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.
Hi Filippo,
a possible solution can be to set the duration before the transport task starts. For example, in the model attached, I modify the duration value accessing the corresponding treenode using the on exit trigger on the source. 
Otherwise, you can write a ProcessFlow for each mission where you increase the mission time using a delay calculated with a probability distribution.
Which is your opinion @Phil BoBo?
Thank you so much for the answer.
This is very interesting. But if there are many trucks traveling on the same route and at the same time the duration will change for every truck or this method will not work properly? Beacuse I need to model a logistic service, with many trucks traveling at the same time, but strating their travel at different times.
Unfortunaely the second option you suggest is not possible, because there are many many missions.
You would construct a process flow so that it was generic - maybe each is defined by data structures - not have a process flow for each mission.
The route's duration is not stored per-traveler. If you dynamically change the duration of a route, then it will affect the other travelers that are already on that route. Their totaltraveldist statistics will not be calculated correctly, and they won't be positioned correctly as they travel along the route. Stopping or preempting a traveler mid-route will also not work properly.
Making a route's duration vary by traveler would require significant changes to how the GIS Navigator works.
Sara's suggestion of adding a delay at the end of the travel to account for the variability of durations is probably the best workaround right now. Set the route to the minimum duration of your distribution and then add a delay for the variable range of the distribution.
I'll add a case to the dev list to consider updating the GIS Navigator to be able to handle variable route durations per traveler for a future version.
@ phil, an idea could be to provide to the user a custom field to define the duration.
Something like this:
With a custom duration the user is free to return the defined duration value, increases or reduces it with a "traffic" coefficient or anything else.
In my mind the custom duration would receive as input parameters:
In this way I could define dinamically the travel time to simulate traffic or any sort of time variation without any impact on the route choice.
This is an idea. Take it into account for the future GIS module improvements.
Hi @Phil BoBo , you can add my vote to the case "updating the GIS Navigator to be able to handle variable route durations per traveler for a future version."
One of our users wants to simulate a public transport network by bus. The travel times between bus stops are defined by statistical distributions. Most of the times there is only one bus travelling between 2 bus stops, so updating the route duration just before the travel task starts could work. But sometimes there are also several buses on the same route, with their own travel times since they are defined with statistical distributions.
19 People are following this question.
© 1993- FlexSim Software Products, Inc. All Rights Reserved.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
