Sequencing and not Optimization in PTV Developer

[mehdi]

Hello Bernd,

one of the partners is currently migrating to PTV Developer. 

They have recently placed two orders:
xServer 1‎ : On Premise : Basic (xLocate + xMap + xRoute) + Sequence (xTour Light)‎


They want to continue using Sequencing but not Optimization.

Is there any way to just Sequencing and not Optimization in PTV Developer? 
If so, which API corresponds to this?

Thank you.
Best Regards, 
Mehdi

[Bernd Welter]

Hello Mehdi,

please look into the Sequence Optimization API and consider the known restrictions:

• max. planning horizon = 24 hours

As an alternative you can consider the
Route Optimization Optiflow API.

Bernd

[mehdi]

Hello Bernd,

Thank you. Here is the final analysis and explanation I prepared by the element that you gave, which might be useful for someone else:

• Route sequencing was originally an operation of xTour. This is why clients specify that they do not want to use planning optimization, which is more expensive. With Developer, we now distinguish between tour optimization (Routing Optimization API) and sequence optimization (Sequence Optimization API). In other words, these are distinct APIs (even though there may be some common algorithms internally).
  Therefore, clients can fully utilize the Sequence Optimization API.

Explanation of the case according to the documentation:
To use only sequencing without optimization in PTV Developer, we can use the Sequence Optimization API. This API allows us to optimize the order of stops in routes without performing additional optimization, such as solving complex routing problems or considering additional constraints.

Here’s how to proceed to use only sequencing in PTV Developer:

1. Use the Sequence Optimization API to submit your stops and obtain the optimal order for your routes.
2. When using this API, make sure not to include additional options that trigger route optimization or the resolution of more complex routing problems.
3. After obtaining the optimal order of stops, you can use it to plan your routes without going through the complete routing optimization process.

By following these steps, you can use only stop sequencing without performing additional optimization.

If a client wants to optimize only the order of stops on a route for a single vehicle without recalculating or optimizing the entire route, they should use only the Sequence Optimization API and avoid using options that pertain to the Route Optimization API features. To avoid triggering more complex and comprehensive route optimization, ensure not to include options intended for the Route Optimization API in the request.

By using the Sequence Optimization API, users can focus solely on sequencing their stops efficiently, without needing a complete tour optimization. This ensures that the API meets the specific need to optimize the order of stops without adding the overhead associated with additional optimization processes.

The link providing information on the Sequence Optimization API is: Sequence Optimization API Documentation
Clients can learn more by clicking on this link to the documentation.

This guide specifically covers the Sequence Optimization API and provides detailed information on how to use it to optimize the order of stops in routes.

Best regards,

[Bernd Welter]

some short feedback:

• SequenceOptimization API is restricted to a planning horizon of 24 hours - so if you want to compute a driver's whole week in one go, this would technically require a switch to RouteOptimization API.