Route Plan
The planned path from origin to destination including waypoints, stops, estimated transit times, fuel stops, and rest breaks that guide driver execution and serve as baseline for deviation detection.
Why This Object Matters for AI
AI route optimization produces a new route plan while ETA prediction and deviation detection compare actual execution against this plan; without an explicit route object, systems cannot measure compliance or improvement.
Freight Operations & Transportation Management Capacity Profile
Typical CMC levels for freight operations & transportation management in Logistics organizations.
CMC Dimension Scenarios
What each CMC level looks like specifically for Route Plan. Baseline level is highlighted.
Routes exist only in the driver's memory. A veteran driver knows to avoid the I-40 interchange during construction season and which truck stops have diesel under $4, but none of this is written down. When that driver retires, the route knowledge goes with them.
None — AI cannot optimize or compare routes because no route plan exists in any system. Every trip is a blank slate.
Start documenting routes in any form — even a spreadsheet of origin-destination pairs with preferred waypoints and estimated drive times.
Dispatchers give drivers verbal routing instructions or write them on the load sheet — 'take I-81 south, avoid the DC beltway during rush hour.' Some drivers use personal GPS apps. There's no standard route plan format, and what the dispatcher intended often doesn't match what the driver actually drove.
AI could generate basic directions from origin to destination using mapping APIs, but cannot compare planned vs actual routes or identify systematic routing inefficiencies because no formal route plan exists as a record.
Implement route planning in the TMS that generates a documented route for each shipment — waypoints, estimated segments, and planned stops — before the driver departs.
The TMS generates a planned route for each shipment — origin, destination, waypoints, estimated drive time per segment, and planned fuel stops. Dispatchers can view and adjust routes before assigning them to drivers. But the route plan is static — it doesn't update once the driver departs, and actual execution isn't tracked against the plan.
AI can calculate optimal routes using mapping data and generate plans that minimize mileage or transit time. Cannot measure route compliance or identify systematic deviations because there's no actual-vs-planned comparison mechanism.
Connect GPS telematics feeds to the route plan so the system can track actual route execution against the planned path and flag deviations in real-time.
Route plans are living documents — the TMS tracks actual GPS breadcrumbs against the planned route and records deviations with timestamps and duration. Planners can query 'show me all routes on the ATL-MIA lane where drivers deviated by more than 20 miles' and get precise results linking the deviation to weather, construction, or driver preference.
AI can analyze planned-vs-actual route performance, identify systematically suboptimal routing patterns, and recommend route improvements based on historical execution patterns. Predictive ETA models incorporate actual route behavior, not just planned paths.
Integrate real-time traffic, weather, and road condition feeds into the route plan so it recalculates dynamically during execution rather than remaining a static pre-departure artifact.
Route plans are schema-driven entities with formal relationships to shipments, drivers, vehicles, fuel stops, rest areas, and delivery appointments. Each route segment carries constraints (HOS limits, hazmat restrictions, bridge clearances, appointment windows). An AI agent can query the route model and understand not just the path but the constraints governing it.
AI can autonomously generate constraint-aware routes, dynamically reroute around disruptions while respecting HOS and appointment windows, and optimize fleet-wide routing across multiple simultaneous shipments. Full autonomous route management for routine scenarios.
Implement real-time streaming route optimization where the route plan continuously recalculates based on live traffic, weather, and fleet position data, publishing updates to drivers and downstream systems instantly.
Route plans are dynamic, self-updating entities that continuously optimize based on real-time conditions — traffic, weather, fuel prices, driver HOS remaining, dock availability, and fleet positions. The route plan adapts minute-by-minute during execution, and each adjustment is captured as a versioned record with its reasoning.
Fully autonomous route management. AI agents plan, monitor, and adjust routes in real-time for the entire fleet simultaneously, optimizing for cost, time, emissions, and driver compliance without human intervention.
Ceiling of the CMC framework for this dimension.
Capabilities That Depend on Route Plan
Other Objects in Freight Operations & Transportation Management
Related business objects in the same function area.
Shipment Record
EntityThe core transactional record of a freight movement — origin, destination, pickup/delivery times, carrier, equipment type, commodity, weight, cube, and status milestones that define what moves where and when.
Carrier Profile
EntityThe master record of a carrier — authority credentials, insurance, equipment types, lane preferences, capacity, historical performance metrics, and tender acceptance patterns that define carrier capabilities.
Rate Agreement
EntityThe contracted or quoted rate structure by lane, mode, and accessorial — base rates, fuel surcharges, accessorial schedules, and volume commitments that determine the cost of freight movements.
Load
EntityThe physical cargo configuration on a truck or container — what's loaded, how it's positioned, weight distribution, and fill percentage that determines capacity utilization and consolidation opportunity.
Delivery Appointment
EntityThe scheduled arrival window at a destination facility — dock door assignment, expected arrival time, loading/unloading duration, and detention rules that coordinate freight-facility handoffs.
Freight Invoice
EntityThe carrier's bill for transportation services — line items, rates, accessorials, fuel surcharges, and supporting documentation that must reconcile against shipment records and rate agreements.
Carbon Emission Record
EntityThe calculated CO2 emissions for a shipment or route — emissions by mode, distance, fuel type, and load factor that enable sustainability tracking and optimization decisions.
Lane
EntityAn origin-destination corridor that defines a repeating traffic pattern — geography, typical volumes, seasonal variations, and carrier coverage that structures network planning and rate negotiations.
What Can Your Organization Deploy?
Enter your context profile or request an assessment to see which capabilities your infrastructure supports.