Aligning Break Configuration Between xRoute and xTour

[CAPcargo]

Hi,

We are currently using both the xRoute and xTour APIs in our product.

Recently, we’ve begun using the configurableWorkingHours and configurableWorkingHoursPreset options under routeOptions.tourRestrictions in xRoute.

In xTour, we've traditionally utilized the following parameters to manage driver breaks and working regulations:

• planToursRequest.Fleet.Driver. BreakInterval

• planToursRequest.planToursOptions.restrictions.workingHours.drivingTimeRegulation

• planToursRequest.planToursOptions.restrictions.workingHours.workingTimeDirective

To maintain consistency between the two services—particularly because dispatchers often first call xTour/planTours with the break functionality and then call xRoute/calculateRoute with the break functionality over the result tour—we've aligned the configuration by switching to:

• xTour/planToursRequest.Fleet.Driver.configurableWorkingHours

• xTour/planToursRequest.Fleet.Driver.configurableWorkingHoursPreset

This alignment works well in terms of functionality.
However, we've encountered a conceptual limitation: by adopting configurableWorkingHours, we lose the capability to define explicit break intervals—for example, specifying that a driver must take a 30-minute break between 12:00 and 14:00 (as supported by BreakInterval in xTour).


The question to you is:
Is there a way to achieve this same break interval functionality in xRoute—perhaps through another mechanism—so that the behavior is consistent across both xTour and xRoute?

Or, if we require unified break behavior, are we effectively limited to using configurableWorkingHours in both services, thereby accepting the loss of detailed break intervals?



Looking forward to your guidance.


Best regards,
Marko Arsovski
CAPcargo

[Bernd Welter]

Hi Marko,
thanks for the question - I forwarded it to DEV experts (ADOS 263673) and asked for some feedback.
Best regards,
Bernd