vehicle_efficiency
constraints object[]
This feature enables efficiency constraints for vehicles, managing how much capacity they utilize. It works by defining a list of constraints for various demand types. These constraints focus on two optional checks during a vehicle's trip:
Minimum Load: Ensures the vehicle is loaded with at least a specified minimum capacity throughout the trip. This promotes efficient vehicle usage. Maximum Remaining Load: Ensures the vehicle's remaining load at the end of a trip doesn't exceed a specified maximum. This discourages returns to the depot with significant unused capacity. Each check can be either strict or weak:
Strict: These constraints must be met. Failing a strict constraint is unacceptable, even if it means no solution is found. Weak: These constraints are preferred but not mandatory. If a weak constraint is violated, a penalty is added to the overall objective value. The penalty for violating a weak constraint is calculated as the sum of two components:
Fixed Penalty: A pre-defined penalty value. Linear Penalty: Calculated by multiplying the cost of over/under capacity by the amount of over/under capacity.
Demand name to apply the constraint.
This demand type must be present in at least one full booking.
If the demand set here is not present in any of the booking as a set demand type, the optimizer will fail the validation.
Minimum capacity after a series of consecutive pickups before dropoffs. If check is not strict then penalty is added to cost if capacity is less than minimum. If check is strict then route with too small capacity is invalid.
The same as loaded_min_capacity but represented as percentage.
Fixed penalty of undercapacity.
0Cost of undercapacity. The additional penalty is calculated as the product of undercapacity_cost and the undercapacity value.
0Flag indicates that check of undercapacity must be strict.
falseMaximum capacity after a series of consecutive dropoffs before pickups. If check is not strict then penalty is added to cost if capacity is greater than maximum. If check is strict then route with too large capacity is invalid.
Same as unloaded_max_capacity but represented as percentage.
Fixed penalty of overcapacity.
0Cost of overcapacity. The additional penalty is calculated as the product of overcapacity_cost and the overcapacity value.
0Flag, indicates, that check for overcapacity must be strict.
false"Unknown Type: object,null"