Transportation Business Information Model

This Business Information Model lays out the data entities that a transportation or logistics operation actually runs on — shipments, loads, assets, routes, and the shifting cast of parties that move freight from origin to destination — grouped into foundational, transactional, and informational categories in an editable Word document.

Why Freight Doesn't Fit a Generic Template

Transportation data looks simple from a distance — shipper, carrier, shipment — until you try to model how freight actually moves. A single customer order routinely splits across multiple shipments, and a single truckload or container often consolidates cargo from several unrelated orders, so order and shipment can't be treated as a one-to-one pair. Multi-leg and intermodal moves turn a shipment into a chain of legs across different carriers and modes, each with its own status and timing. Party roles compound the problem: the same legal entity can be a shipper on one movement, a carrier on the next, and a broker arranging a third, so roles need to attach to the relationship rather than to the party record itself. Equipment — trailers, containers, chassis — has to be modeled as its own asset entity independent of the cargo it carries, because empty repositioning and interchange happen constantly.

Inside the Model

• Foundational entities: Party (Shipper/Carrier/Broker/Consignee), Asset/Equipment, Location, Lane, Rate/Tariff
• Transactional entities: Order, Shipment, Load, Leg/Movement, Tracking Event, Freight Invoice
• Informational entities: On-Time Performance, Lane Cost Analysis, Carrier Scorecards, Capacity Utilization
• Entity relationship diagram covering multi-leg and multimodal movements
• Delivered as a fully editable Word document

How It Gets Used

• As a starting point for a transportation management system (TMS) or freight data model
• To scope master data management for party, equipment, and lane/rate domains
• To design integrations between order management, dispatch, and tracking or telematics systems
• As a reference for aligning logistics, IT, and finance on shared shipment and billing definitions

Data architects and IT leaders at carriers, 3PLs, freight brokers, and shippers use it as a working starting point for TMS implementations, EDI/API integration, or broader supply chain architecture.