Use this sheet to define the jobs, stops, or deliveries that vehicles may perform.
Each row represents one task. Tasks are assigned to vehicles during optimization, subject to capacity, time windows, and other constraints.
Site
Specifies the location where the task takes place.
This field must match a Site Name defined in the Sites sheet exactly.
Multiple tasks may occur at the same site.
Task ID
Defines the unique identifier for the task.
Examples:
Task 001
Order-15
Pickup_A
Each task ID must be unique.
This field is relational and is referenced in other sheets such as Task Pairs and Demand.
Start Delivery Time Window
Defines the earliest time the task may begin service.
This field is optional. If left blank, no start time window constraint is applied to the task.
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.
End Delivery Time Window
Defines the latest time the task may begin service.
This field is optional. If left blank, no end time window constraint is applied to the task.
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.
Service Time
Defines the amount of time required to complete the task once the vehicle arrives. Service time is added to the route duration and affects scheduling feasibility.
This field is optional. If left blank, service time is assumed to be zero, meaning the pickup or delivery occurs instantaneously.
This value must be a non-negative number and must use the same time unit as the rest of the model.
Prize
Defines the value gained (i.e., revenue) if the task is completed.
This field is used when a positive Prize weight is specified in the Goals sheet. If the prize weight is greater than zero, tasks become optional. The solver will perform a task only if the prize (revenue) outweighs the cost of servicing it within the overall objective.
If the Prize weight in the Goals sheet is zero, prize values entered here will not influence the solution.
If tasks are paired together in the Task Pairs sheet, both tasks in the pair must have the same prize value.
Rules and Structure
Site must exist in the Sites sheet.
Task ID must be unique.
Time values must be numeric and consistent across the model.
End Delivery Time Window must be greater than or equal to Start Delivery Time Window.
Service Time must be non-negative.
Comments
0 comments
Please sign in to leave a comment.