Load
The 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.
Why This Object Matters for AI
AI load consolidation and optimization capabilities need to understand current load composition to identify consolidation opportunities; load factor analysis depends on explicit load objects.
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 Load. Baseline level is highlighted.
Load information exists only in the driver's visual assessment when they open the trailer doors. Nobody records what's actually on the truck, how it's arranged, or what percentage of capacity is used. The dispatcher knows a truck was sent, but not whether it left half-empty or overweight.
None — AI cannot optimize load utilization or identify consolidation opportunities because no load record exists in any system.
Start recording basic load information at pickup — at minimum, the number of pallets, total weight, and a subjective fill percentage for each truck that departs.
The warehouse team notes the pallet count and total weight on the bill of lading. Some shipments have a fill percentage estimate written by the dock worker. But the information varies by facility and shift — one dock records detailed cube dimensions, another just writes '22 pallets'. Finding load data for last month's shipments means reading individual BOLs.
AI could extract load information from scanned BOLs, but inconsistent detail levels make automated load factor analysis unreliable. Consolidation opportunity identification is impossible when half the loads lack cube utilization details.
Standardize load recording in the WMS or TMS — require pallet count, total weight, commodity type, cube utilization percentage, and equipment type for every outbound load.
Every outbound load has a standard record in the WMS — pallet count, total weight, cube utilization, commodity type, and equipment type. Warehouse managers can report on average load factors by lane or customer. But the load record is disconnected from the shipment and order records — linking a load's contents to the customer orders it carries requires manual cross-referencing.
AI can analyze load utilization trends and identify lanes with consistently low fill rates. Cannot optimize load consolidation across orders because the load record doesn't link to the customer orders or shipment records it carries.
Link load records to their constituent customer orders and shipment records so the system knows exactly which orders are on which truck, enabling AI to plan multi-order load consolidation.
Load records are connected — each load links to its constituent orders, shipment record, vehicle assignment, and warehouse dock. A planner can query 'show me all loads leaving the Chicago DC this week that are under 70% fill and heading toward Atlanta' and get precise results with order-level detail for consolidation analysis.
AI can perform intelligent load consolidation — identifying orders heading to similar destinations that could share a truck, calculating combined weight and cube, and proposing consolidated load plans. Multi-order, multi-stop load optimization is achievable.
Add item-level load detail — SKU-level dimensions, stacking constraints, temperature requirements, and hazmat classifications — so the load model captures not just total metrics but the compatibility rules governing what can share a truck.
Load records are schema-driven entities with formal relationships to orders, SKUs, vehicles, and facilities. Each item carries its dimensions, weight, stacking rules, temperature requirements, and hazmat class. The load model understands physical constraints — maximum axle weight, trailer cube limits, product compatibility rules, and loading sequence optimization.
AI can autonomously build optimized load plans that respect all physical and regulatory constraints — weight distribution, cube maximization, product compatibility, loading sequence for multi-stop deliveries, and hazmat segregation rules. Full autonomous load planning for standard scenarios.
Implement real-time load visibility through IoT sensors (weight sensors, fill-level cameras, temperature monitors) that stream actual load conditions during transit, creating a live digital twin of every active load.
Load records are living digital twins — IoT sensors on the trailer floor measure actual weight distribution, cameras capture fill level, temperature probes monitor conditions, and GPS tracks the physical load through every transfer point. The load record updates itself from creation through delivery without manual data entry.
Fully autonomous load management. AI agents plan, monitor, and adjust loads in real-time using sensor-driven load awareness. The load record is a continuous stream of physical reality, not a planning document.
Ceiling of the CMC framework for this dimension.
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.
Route Plan
EntityThe 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.
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.
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.