Page 1 of 1

how to replace xtour2.serviceTimeFactorForOrders in Optiflow?

Posted: Mon May 04, 2026 12:19 pm
by Bernd Welter
Hi there,
We noticed that one functionality seems to have been missed during the migration from xTour to OptiFlow and it is “serviceTimeFactorForOrders”.
In xTour, this parameter allowed us to represent technician productivity levels. For example:
  • 0.8 for expert technicians (faster execution)
  • 1.0 for standard technicians
  • 1.2 for junior technicians (slower execution)
This factor was applied to adjust the service times of all order performed by a technician / vehicle.
Could you please advise how we can achieve the same behaviour in OptiFlow?
That is simple: use RULES:

Code: Select all

"rules": {
  "tasks": [
    { "conditions": [{"vehicleCategory": "Expert"}],
      "duration": {"factor": 0.8}       },
    {"conditions": [{"vehicleCategory": "Junior"}],
      "duration": {"factor": 1.2}    }
  ]
}
and ensure that
  • any Junior technician's vehicle belongs to the category "Junior"
  • any Expert technician's vehicle belongs to the category "Expert"
With this approach
  • Any order will be accellerated/decellerated
  • It is also possible to restrict this rule to a subset of orders.
As you can see in the GANTT: though all original durations in this example are set to 60 minutes the juniors require longer, the Experts are faster and can manage to service 10/11 orders during the shift
As you can see in the GANTT: though all original durations in this example are set to 60 minutes the juniors require longer, the Experts are faster and can manage to service 10/11 orders during the shift
Best regards,
Bernd