PTV Route Optimization OptiFlow API is continuously improving with new features that enhance logistics efficiency and effectiveness for clients. This update outlines some important changes related to vehicle configurations that affect the optimization of pickup and delivery orders.
Introducing the new vehicle compartment parameter
A new compartment parameter for vehicles has been introduced in the Route Optimization OptiFlow API V1.6.0. This parameter allows users to specify multiple compartments available for loading orders. Each compartment can follow its own specific loading strategy, which may affect the unloading sequence. The aim is to provide greater flexibility in modeling the loading and unloading process, giving clients more control over route efficiency and load management.
How does this work?
-
By setting constraints on the combinations of orders and compartments, you gain complete control over which orders are assigned to specific compartments in your vehicle.
-
If multiple compartments are defined for a vehicle, orders assigned to different compartments can be unloaded without any restrictions.
-
If orders are placed in the same compartment, the loading strategy of that compartment will dictate the unloading sequence. For instance, the new loading strategy could determine that certain items must be unloaded before others, based on the nature of the goods or operational constraints.
-
When the compartment parameter is not specified, the vehicle is assumed to have a single compartment with a default loading strategy of “NONE” or “LAST_IN_FIRST_OUT” for certain order types. This is crucial for optimizing routes for both pickups and deliveries.
Important notice for users of pickup-delivery orders
A key change will impact users who utilize pickup-delivery orders. Specifically, the default behavior for vehicles without a specified compartment parameter is set to change. This will happen in the next few weeks and a specific date will be announced separately.
Previously, if no compartment details were provided, the vehicle was assumed to have a single compartment with a LAST_IN_FIRST_OUT loading strategy for pickup-delivery orders. However, this behavior will soon be revised to assume a loading strategy of NONE regardless of the type of orders specified. This change is crucial for ensuring that the optimization algorithm functions consistently and predictably across various use cases.
What does this mean?
-
If current implementations rely on the default LAST_IN_FIRST_OUT behavior, it is necessary to adapt vehicle configurations by explicitly specifying a single compartment with a loading strategy of LAST_IN_FIRST_OUT.
-
This modification will help ensure that the change does not impact existing optimization results, allowing for a smoother transition and consistent logistics operations.
Next steps for developers
For developers working with the Route Optimization OptiFlow API, the following actions are recommended:
-
Review the API Reference: Familiarize yourself with the new compartment parameter and understand how it may influence existing or planned configurations. Refer to the documentation here.
-
Make Necessary Updates: If the application involves pickup-delivery orders, review the code and add a specification for a single compartment with a LAST_IN_FIRST_OUT loading strategy to ensure there are no disruptions.
-
Test Thoroughly: Once changes are implemented, thoroughly test routes and order configurations to ensure that optimization results align with expectations.
To keep yourself updated about releases and news you can use the subscribe button at the top of the page. If you got any question do not hesitate to get in contact.