Changelog

0.59.0

Naming changes in the input API

To improve clarity and consistency in the input API, we have updated the way capacities and demands are defined for drivers and jobs. The guide to the driver capacity constraint has been updated to reflect these changes.

Please see the Driver capacity section for more details.

The specific changes can also be found in the upgrade guide.

Extend output information

The output now contains information about unassigned jobs and their stops. It was also extended with additional information about the driver’s vehicle’s previous and current load for each stop in an output itinerary. For each capacity type, the following information will be displayed:

"load": [
    {
        "type": "storage",
        "previous": 0,
        "current": 2
    }
]

The load on a driver’s vehicle will be visible at each stop in the output itinerary. type specifies the capacity type, previous the load before visiting the stop, and current the load after visiting the stop. This additional information can help users to better understand the solution and analyze the performance of their routing model.

Raising the maximum number of threads

The maximum number of threads that the solver can use has been increased from 1 to 6. This enables multithreaded solving in the PDR model and can lead to faster solving times and improved performance for larger and more complex problems.

0.58.0

Maximum time burden on the job level

It is now possible to define maximum time burdens on the job level. Before, it was only possible to define maximum time burdens in the configuration for the entire set of jobs. With this change, there is more flexibility to define different maximum time burdens for different jobs and still use the global definition as a default value. More details can be found in the Maximum time burden section.

Handling input itineraries in the Pick-up and Delivery Routing model

The Pick-up and Delivery Routing model now supports input itineraries, allowing users to define pre-planned routes for drivers. The pre-planned routes will be used as a starting point for optimization. There is a new section in the user guide that explains how to use input itineraries for real-time planning scenarios.

Extending the options for defining shift hours, including overtime hours

The options for defining shift hours have been extended to include overtime hours and other options. These added options are:

  • A soft end time of a shift, which now allows defining a preferred end time for a shift and a maximum end time.

  • A hard maximum departure time from the last stop of a shift.

  • A preferred maximum departure time from the last stop of a shift.

More details on how these definitions can be used, can be found in the Shift hours and overtime section.

0.57.0

Custom job priorities

New "opt-1" to "opt-10" built-in optional job priorities have been added to the "1" to "10" built-in mandatory job priorities, making it possible to define the priority of optional jobs. In addition, it is now possible to define a custom priority and its weight.

This gives the user finer control over the penalty of leaving a job unassigned.

Please see Priority jobs section for additional details.

Improved quality of solution

A new custom move has been added to the model that allows already assigned jobs to be replaced, leading to solutions with better score.

For instance, a low priority job that is assigned early in the solving process can now be replaced by a high priority job.

0.56.0

Hello World: Pick-up and Delivery Routing model public preview release

The public preview release of the Pick-up and Delivery Routing model is now available for all users to explore.

The Pick-up and Delivery Routing model assigns pick-ups and deliveries to drivers so that multiple pick-ups and deliveries can be made at the same time. The model balances the driver’s vehicle capacity, current load, and demand while minimizing driving time and customer wait times.

The initial release includes the following constraints:

As we continue to iterate, we will update the changelog with new features, improvements, and enhancements to the model.

Subscribe to the changelog.