Brand new feature in Route Optimization OptiFlow API:
- Added input routes that allow continuing optimizations from predefined routes.
- Please check your individual price plan or contract to see if this feature is available to you.
And I already received some questions:
| When will you add fixations in the input plan? |
|---|
| You can already use the known constraints to keep assignments. |
| Is the handling of the input plan equal to what we are used to in xTour1/xTour2? |
|---|
No, it is different. In xTour each input vehicle would first hav e been assigned to one of these three categories:
- Vehicle is not asigned an input tour
- Vehicle is assigned an unviolated input tour
- Vehicle is assigned a violated input tour. And vehicles of this category were simply mirrored with their input structure, we provided the driving times, arrival times, loading conditions and the VIOLATIONS. But we did change these vehicle's structrures.
Optiflow API is different: ... we first get rid of the violations by removing orders from violated tours step by step. And if you apply too many fixations at that stage you might run into infeasable behaviour. I will try to gather a more in depth description of this approach.
|
Best regards,
Bernd
