PTV Logistics Product Forum

Api	VarVersion	Type	Date	Description
Route Optimization OptiFlow API	1.59.0	FEATURE	20.04.2026	Added availability windows to resources. Deprecated resource ids on routes in favor of a more generalized object.
Route Optimization OptiFlow API	1.59.0	FEATURE	20.04.2026	Added vehicle-charging station combination constraints.

I also asked PTV MIRA for the new features:

Two new features were introduced:

1. Availability Windows for Resources

Added availability windows to resources. Deprecated resource ids on routes in favor of a more generalized object.

Resources now support availability windows — time-based slots that define when a resource is available. This allows modeling scenarios like:

• A shared truck that is only available in the morning shift (06:00–14:00) and again in the evening (18:00–22:00)
• Equipment or drivers with specific working schedules

Additionally, the way resources are referenced on routes has changed: the previous resourceIds field on routes is deprecated in favor of a more generalized object structure (resources array with id and availabilityId), allowing routes to reference specific availability windows of a resource.

Input fields:

• resources[].availabilities[] — array of availability windows with id, earliestStart, latestEnd
• routes[].resources[] — new object format with id and availabilityId (replaces deprecated routes[].resourceIds[])

2. Vehicle–Charging Station Combination Constraints

Added vehicle-charging station combination constraints.

A new combination constraint type allows controlling which vehicles can use which charging stations. This enables scenarios like:

• Restricting certain charger types to specific vehicle categories (e.g., only heavy trucks can use high-power DC chargers)
• Preventing vehicles from using incompatible charging infrastructure
• Modeling proprietary charging networks accessible only to certain fleet segments

Input field:

• constraints.combinations.vehicleChargingStation[] — with types CHARGING_STATION_REQUIRES_VEHICLE, VEHICLE_REQUIRES_CHARGING_STATION, and FORBIDDEN_COMBINATION, using vehicleCategory and chargingStationCategory matchers

Full details: route-optimization-optiflow-api/api-changes