Use this sheet to define each individual vehicle available in the model. Every row represents one vehicle instance. Vehicles reference the Vehicle Types and Sites sheets and define availability and operating constraints.
Vehicle ID
Defines the unique identifier for the vehicle.
Examples:
Truck 01
Van-A
Vehicle_12
Each Vehicle ID must be unique. This field is relational and is referenced by other sheets.
Start Site
Defines the location where the vehicle begins its route. If it's irrelevant where the vehicle begins its trip, you can use the Skip First Trip field defined later in this table.
This field must match a Site Name defined in the Sites sheet.
End Site
Defines the location where the vehicle must end its route. If it's irrelevant where the vehicle ends its trip, you can use the Drop Return Trip field defined later in this table.
This field must match a Site Name defined in the Sites sheet.
The start and end sites may be the same (e.g., a depot-return model), or different if modeling open routes.
Type
Defines the vehicle type for this vehicle. This field must match a Name defined in the Vehicle Types sheet. Travel cost and travel time for the vehicle are determined by this vehicle type.
Available Start Time
Defines the earliest time the vehicle is allowed to begin service.
This field is optional. Leave blank if there are no start time limits on the vehicle.
This value must be entered as a non-negative number (for example, 0, 8, 480, 12.5). Do not enter clock-formatted times such as 8:00 AM or 14:30. All time values in cuOpt are numeric and represent whatever unit you choose to model (minutes, hours, days, etc.). NVIDIA cuOpt does not interpret calendar time, it only uses numeric values consistently throughout the model.
Available End Time
Defines the latest time the vehicle must complete its route.
This field is optional. Leave blank if there are no end time limits on the vehicle.
This value must be entered as a non-negative number (for example, 0, 8, 480, 12.5). Do not enter clock-formatted times such as 8:00 AM or 14:30. All time values in cuOpt are numeric and represent whatever unit you choose to model (minutes, hours, days, etc.). NVIDIA cuOpt does not interpret calendar time, it only uses numeric values consistently throughout the model.
Max Cost
Defines the maximum total route cost allowed for this vehicle. If specified, cuOpt will ensure the total accumulated cost does not exceed this value.
This field is optional. Leave blank if no cost limit is required.
Max Time
Defines the maximum total route time allowed for this vehicle. If specified, cuOpt will ensure the total accumulated travel, service, and break time does not exceed this value.
This field is optional. Leave blank if no route duration limit is required.
Fixed Costs
Defines a fixed cost incurred if the vehicle is used. This allows the model to choose whether to activate a vehicle when minimizing total cost.
If left blank or set to zero, no fixed usage penalty is applied.
For this field to take effect, the Vehicle Fixed Cost weight specified in the Goals sheet must be greater than zero. If that weight is zero, fixed costs will not influence the solution.
Skip First Trip
Indicates whether the first trip from the start site should be excluded from cost and time calculations. Enter the appropriate Boolean value of TRUE or FALSE.
If left blank, defaults to FALSE.
Drop Return Trip
Indicates whether the vehicle is not required to return to its End Site. If enabled, the vehicle may finish at its last serviced task location instead of returning. Enter the appropriate Boolean value of TRUE or FALSE.
If left blank, defaults to FALSE.
Rules and Structure
Vehicle ID must be unique.
Start Site and End Site must exist in the Sites sheet.
Type must exist in the Vehicle Types sheet.
Time-related fields must be consistent with the model’s time unit.
Comments
0 comments
Please sign in to leave a comment.