The output is a route solution - an assignment of visits (stops) to fleet objects (drivers). It essentially produces a schedule for each driver, giving him the order in which he should visit his stops (so as to be as efficient as possible while respecting time windows, capacity constraints etc) and the estimated arrival time at each location. Below is the output for job 141df046-2bb7-4a3c-93a5-1253274673a5 that was used as an example in the quickstart section.
When the optimization is first run, it will have the status of pending. When it is complete, it will show finished.
input
Object
The raw json object that was sent as input for the optimization job.
output
Object
The output contains a solution object with the optimized schedule, where the keys reference the vehicle IDs and the values are ordered arrays of visits (and estimated arrival and finish times).
fleet
Number
The number of fleet objects in the route solution.
visits
Number
The number of visit objects in the route solution.
started_at
String
finished_at
String
When there are too many visits — or the time windows are too tight — and the fleet cannot possibly visit all locations, some visits will be unserved. We will return both those visit IDs in unserved as follows in the API response: