NDD Task SequenceTask Sequence

Overview

A task sequence defines a predefined ordering of tasks for a specific vehicle on a specific day. Task sequences are used to provide starting solutions for ReOptimise requests, to specify routes for Evaluate requests, or to recover a detailed schedule from a point on the Pareto frontier returned in the solution response.

The NDD task sequence differs from the standard IVR7 task sequence by including a dayIndex field, which specifies which day in the planning period this sequence applies to.

Applicable models

• NDD ndd-cmibu6krtqja

TaskSequence

Schema definition

message TaskSequence {
  required string vehicleId = 1;
  required int32 dayIndex = 2;
  repeated string taskId = 3;
}

Fields

vehicleId

The identifier of the vehicle to which this sequence applies.

dayIndex

The day index (zero-based) within the planning period to which this sequence applies. A dayIndex of 0 corresponds to the first day.

taskId

An ordered list of task identifiers defining the sequence in which tasks should be performed on this day by this vehicle.

Examples

A task sequence for truck-01 on the first day of the period:

vehicleId: "truck-01"
dayIndex: 0
taskId: "customer-001:dropoff"
taskId: "customer-005:dropoff"
taskId: "customer-012:dropoff"

A task sequence for the same vehicle on the third day:

vehicleId: "truck-01"
dayIndex: 2
taskId: "customer-003:dropoff"
taskId: "customer-007:dropoff"

Notes

• Task sequences are typically populated in the compact solutions returned on the Pareto frontier. To recover the full detail of a frontier solution, the task sequences from a chosen compact solution are submitted in an Evaluate solve request.
• The dayIndex must be within the range defined by the periodLength in the dimension configuration.
• Shift-start and shift-end tasks for the vehicle should not be included in the task sequence; they are implied.