Planning Restrictions (MaxDistanceBetween . . .)

This forum deals with any kind of trip optimization based on xTour1, xTour2 and the Developer APIs "RouteOptimization" and "SequenceOptimization". No matter whether it is automatic planning or manual dispatching, refering to transport orders or service planning.
Attention: this does not refer to PTV Optiflow SaaS and PTV Developer RouteOptimization Optiflow.
Post Reply
User avatar
MISTERX
Posts: 58
Joined: Mon Jun 02, 2014 11:50 am

Planning Restrictions (MaxDistanceBetween . . .)

Post by MISTERX »

By reviewing release notes (Version 1.24) I realized that there are additional restrictions for vehicle available, dealing with the maximum allowed distances between stops.

Seems that these working quite similar to the well known TourRestrictions which enhance PlanningParams.

Is there any experience with the new VehicleRestrictions? How is the logic behind the scenes, does VehicleRestriction dominate TourRestriction?
Mr. X
  • Integration PTV <> SAP
  • Senior Consultant

________________________________________________

Optimism is only a lack of data!
User avatar
Bernd Welter
Site Admin
Posts: 2695
Joined: Mon Apr 14, 2014 10:28 am
Contact:

Re: Planning Restrictions (MaxDistanceBetween . . .)

Post by Bernd Welter »

Hello Mr X,

you are right, we invented some more parameters / properties: since xTour 1.20.0.0 there are VehicleRestrictions which are related 1:1 to a concrete Vehicle instance, so each Vehicle can set his own values for those properties:
VehicleRestrictions<br />since 1.20: maxTransportPointCountPerTour, maxDrivingPeriodPerChain, maxTourCountPerChain<br />since 1.24: maxDistancePerTour
VehicleRestrictions
since 1.20: maxTransportPointCountPerTour, maxDrivingPeriodPerChain, maxTourCountPerChain
since 1.24: maxDistancePerTour
On the other hand there are the transaction-wide TourRestrictions that are applied with the same values for all Vehicles
TourRestricions. Unique in a planning call and refer to all Vehicles.
TourRestricions. Unique in a planning call and refer to all Vehicles.
The only overlap in these parameters is the VehicleRestrictions.maxDistancePerTour versus TourRestrictions.maxDistance.
Whether one of these restrictions dominates the other depends on your perspective:
Both values have to be considered. So if you apply both for Vehicle #666 the minimum of the two values is relevant.

Best regards Bernd
Bernd Welter
Technical Partner Manager Developer Components
PTV Logistics - Germany

Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning... :twisted:
Post Reply