Successor of xTour1.toursMustFitIntoSingleOperatingInterval
Posted: Wed Jun 12, 2024 3:04 pm
Hi there,
recently I've been asked for the xTour2 parameter that replaces xtour1's BaseVehicle property:
As an example, users modell a vehicle with the 5 operating intervals "monday to friday, 9am to 5pm"...
So here's how Alex and I discussed the two potential values:
recently I've been asked for the xTour2 parameter that replaces xtour1's BaseVehicle property:
toursMustFitIntoSingleOperatingInterval | boolean | If set to true, tours must fit into a single operating interval. This attribute is ignored for the method planOvernightTours because this use case must consider several operating intervals. |
So here's how Alex and I discussed the two potential values:
- true : that's the default behaviour. Simply use 5 operating intervals. As a trip has to be contained in a single interval this will ensure the driver returns home at the end of the interval.
Attention: if your planning approach doesn't use trip delimiters (depots), e.g. because you exclusively plan VisitOrders, this may return single day tours only... - false :
- use one large global interval from "monday 9am" to "friday 5pm"
- besides the breaks during the day just create further BreakIntervals with fixed length for each night:
Code: Select all
{ "interval": { "$type": "StartEndInterval", "start" : ..monday.. 5pm, "end" : ..tuesday.. 9am }, "breakTime" : 57600 }, { "interval": { "$type": "StartEndInterval", "start" : ..tuesday.. 5pm, "end" : ..wednesday.. 9am }, "breakTime" : 57600 }, and so forth