Transport
BetaDispatch. Carrier selection. Mode optimization. Appointment-window coordination. Transport decisions made in minutes-to-hours, informed by the same world model that drives supply and production.
What makes this a distinct decision domain
Transport's exogenous information is traffic, carrier capacity and availability, appointment windows, and weather. Decisions are minutes-to-hours. The policy class is PFA / DLA, with short-horizon rolling optimization that responds to live signals from carriers, drivers, and receiving docks.
Why it belongs on the same platform
Transport's inputs come from upstream, production schedules, transfer orders, customer promise dates, and its outputs feed downstream execution (warehouse receiving, customer notifications). Every discrepancy between the TMS and the supply plan becomes a reconciliation cost. On Autonomy, the world model is one state that both transport and supply plan against, so a delivery slip propagates immediately into promise-date management.
Beta
Transport is in early customer deployments. Core TO Execution and dispatch policies are live; dynamic routing and appointment-window coordination are rolling out through Q2.
This plane intersects with
Where the collaboration contract lives, not an integration project.
Supply Planning × Transport
Deployment plans become TMS loads; landed-cost and capacity warnings feed back.
Production × Transport
Inbound material arrival windows and outbound ship-by commitments.
Transport × Warehouse
Dock appointment negotiation and staging-lane coordination.
See unified supply + transport decisions
One world model. One Decision Stream. Dispatch that knows what's upstream and what's waiting at the dock.