New Feature:

Ever thought about how to plan electric vehicles? How to limit the distance a vehicle can drive through one day?

Use the new features published in Route Optimization API 1.9.0 resp. Sequence Optimization API 1.6.0.

With maximumDistance you can restrict the maximum allowed total driving distance for the route. You can adjust this for each vehicle separately as battery charging state may be different for each vehicle. 

Additionally there are even more features available:

• routeStartInterval (available in Route Optimization / Sequence Optimization): 
  Defines an interval in which the vehicle has to start its route. Start and end of the interval may be the same, then the vehicle has to start its route at a concrete point in time.
  Can also be used to model the existence of ramps and therefore the restriction, that only a limited number of vehicle per time can be handled at a depot.
• maximumNumberOfCustomerStops (available in Route Optimization): 
  Restricts the total number of customer stops, i.e. stops at customer locations, for the route of this vehicle.
  
  

See also the concept page vehicles and drivers for Route Optimization resp. Sequence Optimization, which describes the functionalities in terms of vehicles and drivers in general.

You can check the new features in the list below or use the API Changes webpage for more details.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.

New Feature:

Service times may have a great impact on the time scheduling of a trip. Especially in urban planning problems, when driving time between customers is only a small time span, the importance of service time may increase.
With the new version of the PTV Developer Route Optimization API PTV offers more flexibility in modelling service times.

As already introduced in Sequence Optimization the new functionality is about to consider location-dependent service times, which are independent from the quantity of goods.  The location-dependent service time represents, for example, the time to enter the premises or to register at a customer. This can be set via 

• serviceTimePerTransportStop for customers
• serviceTimePerPickupStop resp. serviceTimePerDeliveryStop for depots

Moreover, in Route Optimization it may be important to distinguish vehicles of a fleet in terms of service times by the following attributes:

• With serviceTimePerTransportStop on vehicle level you can define absolut Vehicle-dependent service time for example for maneuvering. This service time is taken into account for each stop served by this vehicle to pick up or deliver goods.
•  The serviceTimeFactor on vehicle level scales transport-dependent service times of all transport-related service actions, for example, if loading and unloading with this vehicle is more or less complicate than normal.
• If for a location this service time factor doesn’t apply e.g. due to special equipment at this site, this service time can be ignored via applyVehicleDependentServiceTimeFactor = False on location level.

See also the concept page for service times, which describes the functionality more in detail.

Improvement:

Formerly the plan results could have been influenced by the choice of location or transport IDs. 
Now the plan results stay the same whatever IDs you choose.

You can check the new features in the list below or use the API Changes webpage for more details.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.

New Feature:

With the new version of the PTV Developer Route Optimization API PTV offers a boost for optimization quality called Optimization Premium.

The higher computational capacity allows for searching in distinct search spaces in a parallel manner. Moreover, Optimization Premium uses diverse exclusive neighborhoods that are only enabled within this mode. These diverse neighborhoods enable the algorithm to explore a larger search space and accordingly find better solutions. 

The bigger the instances are, the more improvement can be gained by using Optimization Premium. Although every use case is unique and improvements cannot be guaranteed, customers with Premium Optimization can expect up to 30% fewer unplanned orders, and/or up to 30% smaller fleet size. In cases where all orders are already planned, Optimization Premium delivers up to 10% cost savings.

Optimization Premium is activated on request base by setting query parameter ‘optimizationPremium’ to true  in operation ‘startOptimization’.

Note: 
To use the feature Optimization Premium productive the usage must be explicitly included in your individual PTV Developer license agreement. Before implementing Optimization Premium please contact our local sales departments.

Security bugfixes:

To ensure security and minimize the chance for attacks, all requests are restricted in the following way:

• Capacity of all array objects in locations, vehicles, drivers, transports, and route is limited. These limits are less restrictive as the ones set by subscription. 
• Requests with more than thirty unreferenced locations are not accepted. Unreferenced locations are locations, which are part of request, but neither used as customer or depot locations for transports nor used as vehicle start or end locations. 

This might lead to rejection of requests that were being accepted in previous API versions.

You can check the new features in the list below or use the API Changes webpage for more details.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.