Ability to limit travel times between visits (requirement & preferences)
complete
H
Harry Pickthall (Ionize)
We would also love to have the ability to limit max travel time per shift both as hard and soft scores.
What we're finding is that some engineers end up with very high travel times when trying to cover urgent work, and trying to balance this using max travel mins per visit so that we can assign a full day without the risk of engineers driving long distances from base in multiple hops is difficult and sometimes not possible at all.
A couple of benefits that we can see are A. we can more easily manage engineer expectations because we can say for example, we will aim to keep your travel under 1.5 hours and the maximum it will ever be is 2 hours. And B. by stopping engineers going on long distance drives to cover work we can more easily identify areas where we need more or different types of resource based on what isn't assigned.
Log In
Jurriaan Persyn
complete
We're considering this feature implemented.
Our FSR model has support for:
- Required maximum shift travel time, see https://docs.timefold.ai/field-service-routing/latest/vehicle-resource-constraints/route-optimization#shiftTravelTimeRequirement
- Preferred maximum shift travel time https://docs.timefold.ai/field-service-routing/latest/vehicle-resource-constraints/route-optimization#shiftTravelTimePreference
These are both properties that can be defined on a vehicle shift.
Thank you for sharing your feedback — it helps us make Timefold even better for you.
Jurriaan Persyn
VP Product
Jurriaan Persyn
under review