Lane

Lanes aren't formally defined. The dispatch team talks about 'the Dallas to Chicago run' but there's no record defining what that lane includes — which zip codes, which facilities, what typical volumes, or which carriers cover it. Lane knowledge lives in the broker's experience.

None — AI cannot perform lane-level analysis because no lane definitions exist as structured records. Every query about 'how much freight moves on this lane?' requires manual compilation.

Someone maintains a list of 'key lanes' in a spreadsheet — origin city, destination city, and the carrier who usually covers it. But lane definitions are inconsistent — some are city-to-city, others are state-to-state, and some overlap. 'Dallas to Chicago' and 'DFW to Chicagoland' might be the same lane or different ones depending on who you ask.

AI can read the lane list but cannot perform reliable lane analytics because definitions overlap and aren't geographically precise. Volume aggregation produces different numbers depending on which lane definition is used.

Lanes are formally defined in the TMS using standardized geography — origin and destination regions defined by 3-digit zip prefixes. Every shipment automatically maps to a lane based on its pickup and delivery locations. Planners can report volume, cost, and performance by lane. But the lane record is static — it doesn't capture seasonal patterns, capacity constraints, or market rate dynamics.

AI can perform reliable lane-level analytics — volume trending, carrier performance comparison, and cost benchmarking. Cannot forecast demand or predict rate movements because the lane record lacks temporal patterns and market context.

Lane records are comprehensive entities — each carries geographic definition, historical volume patterns (weekly, seasonal, year-over-year trends), carrier coverage (which carriers serve it and at what acceptance rates), rate history (contracted and spot), and transit time benchmarks. A planner can query 'show me lanes where volume is growing but carrier coverage is shrinking' and get actionable network intelligence.

AI can perform lane-level demand forecasting, carrier capacity gap analysis, and network design optimization using rich lane profiles. Rate prediction models incorporate lane-specific historical patterns and market dynamics.

Lane records are schema-driven network entities with formal relationships to shipments, carriers, rate agreements, facilities, and market indicators. Each lane carries real-time market signals — spot rate index, capacity tightness indicator, carrier availability count, and volume forecast. An AI agent can query 'what is the DAL-CHI lane's current market temperature and how does it compare to seasonal norms?' and receive a structured market intelligence answer.

AI can autonomously manage the freight network — adjusting carrier allocations, shifting volume between lanes based on market conditions, and proactively procuring capacity before constraints develop. Full autonomous network management for routine decisions.

Lane records are living network intelligence entities — volume patterns, rate dynamics, capacity signals, and market conditions stream continuously from shipment flows, load board transactions, and carrier APIs. New lanes auto-detect when shipment patterns establish new origin-destination corridors. The lane model is a real-time map of the freight market.

Fully autonomous freight network management. AI agents operate on a live model of the freight market, detecting lane trends, predicting capacity constraints, and optimizing network strategy in real-time.

Ceiling of the CMC framework for this dimension.