Reference — priority P1. One term = one definition, reused identically across all pages (see terminology consistency best practices).
| Term | Definition |
|---|---|
| Route | The ordered sequence of stops a single resource performs within a plan’s solution — called a tour in the API response (tours[], with resourceId, distanceInKm, workingDuration, and wayPoints). “Route” is the everyday term; tour is the field name you’ll see in payloads. |
| Route plan (or just “plan”) | The full request submitted for optimization — resources, orders, and any plan-level constraints or objectives — called Plan in the API. Submitting a plan doesn’t return a route directly; it returns a solution containing one route (tour) per resource. See Data model. |
| Disruption | An event during execution that invalidates part of an already-computed solution and calls for a new one: a delay, a cancellation, or an urgent new order, typically. A disruption is handled by re-optimizing the affected plan, not by starting a new one — see Real-time re-optimization. |
| Re-optimization | Submitting an update to a plan that already has a solution, using the same id (the version increments automatically). The engine treats this as “same problem, here’s what changed”: it degrades the previous solution just enough to stay valid for the new data, then keeps improving from there, rather than searching from scratch. See How the optimization engine works. |
| Delivery window | The time window during which a delivery-kind stop should or must be visited — authorizedTimeWindows (hard: outside of it, the stop can’t be planned at all) or preferredTimeWindows (soft: reachable outside it, at the cost of minimizeDelay). See Hard vs soft constraints and Data model. |