Drayage and intermodal operators: AI use cases and data

Where is AI showing up in drayage and intermodal work?#

AI in drayage targets the coordination work that fills a dispatcher's day: booking terminal appointments, predicting turn times, catching per diem exposure before free time runs out, matching chassis to loads and auditing accessorial charges. These are judgment calls made under time pressure, which is why model developers want real examples of how experienced operators made them.

Developers building logistics agents cannot learn these decisions from public schedules or vessel feeds. They need the operator's own sequence of events: the appointment that was missed, the reason, the reschedule, the charge that followed and whether the dispute succeeded.

• 1Appointment agents that book, rebook and confirm terminal, rail ramp and warehouse slots.
• 2Turn-time prediction by terminal, gate, weekday and arrival window.
• 3Per diem and demurrage watchers that flag containers nearing the end of free time.
• 4Chassis and empty-container planning across pools, split moves and street turns.
• 5Rail ramp planning around ingate cutoffs, availability notices and storage exposure.
• 6Invoice audit tools that check detention, pre-pull, storage and dry-run charges against timestamps.
• 7Exception triage that drafts customer updates when a container is on hold or a move fails.

Which drayage records do AI developers value?#

The drayage records AI developers value most are the ones that tie a single container move to its appointments, gate events, equipment, charges and exceptions. Each record family below is useful alone, but a package gains depth when the families share a container number and a move ID.

Most of these records already sit in a drayage TMS, terminal portals, the billing system and a dispute log that is often a spreadsheet. The rights note column flags what usually needs a closer look before anything is scoped.

Why linked container moves beat raw GPS pings#

Linked container moves beat raw GPS pings because a model learns from decisions and outcomes, not from location alone. A ping stream shows that a truck sat outside a terminal; the linked record shows that the appointment was missed because the container was still on a customs hold, that the dispatcher pre-pulled it the next morning, and that the storage charge was billed and accepted.

The practical test is whether one identifier can follow a container from the delivery order through every leg: pickup, yard storage, delivery, empty return and final billing. Run the join check below on a recent month before anyone talks about scope. Where the TMS assigned a move ID and billing kept it, the chain is usually intact; where drivers texted updates and clerks keyed charges by hand, it may need rebuilding from dates and container numbers.

A common mistake is exporting only the clean side of the business, such as completed moves and paid invoices. Failed appointments, disputed charges and abandoned street turns are where the judgment lives, and they are the part of the history no public source can supply.

What can limit what a drayage operator licenses?#

Contracts with customers, equipment providers and terminals can limit what a drayage operator licenses, so rights review comes before any export. The operator usually holds its dispatch, gate and billing records as its own business records, but holding a record is not the same as being free to share every detail in it.

Beneficial cargo owners, freight forwarders and NVOCCs often include confidentiality clauses that cover shipment details, consignees and rates. Interchange and chassis agreements can carry their own terms. Data copied out of terminal or steamship line portals may fall under those sites' terms of use, which differs from the appointment history the operator created itself.

• 1Read the confidentiality and data clauses in the largest customer agreements first.
• 2Check interchange, chassis pool and equipment leasing agreements for data terms.
• 3Separate records the company created from data it downloaded from portals or vendors.
• 4Decide how records for employee drivers and owner-operators will be handled.
• 5Flag cabin camera footage and any biometric features for exclusion or separate review.
• 6Confirm who signs for the operating entity and whether lenders or investors must consent.

What to keep, mask or remove in a drayage package#

A drayage package keeps the operational facts and masks the identities, which preserves patterns such as terminal congestion and dispute outcomes while protecting customers and drivers. Consistent tokens matter: the same consignee should map to the same token across years so a model can still see repeat behavior.

Free-text fields deserve the most care. Dispatcher notes and driver messages mention names, cell numbers, gate clerks and home addresses in ways automated scanners miss, so a person should review samples after every scrubbing pass.

• 1Keep terminals, ports and rail ramps, because congestion and turn-time patterns depend on location.
• 2Keep appointment and gate timestamps; they are the core signal for turn-time and per diem decisions.
• 3Tokenize container numbers, since public tracking and import-record services can tie a container to a shipment.
• 4Tokenize customer and consignee names consistently so repeat behavior survives.
• 5Remove driver names, phone numbers and license details, which add risk and little training value.
• 6Tokenize tractor and chassis numbers to keep equipment history without identifying assets.
• 7Band or exclude charge amounts and rates that customer or carrier terms treat as confidential.
• 8Scrub dispatcher and driver notes automatically, then have a person review samples.

Illustrative: a port drayage carrier scopes its dispatch history#

Illustrative: a fictional port drayage carrier with company drivers, owner-operators and its own container yard has run the same drayage TMS for many years. Per diem disputes live in a shared spreadsheet, terminal appointments in several portals, and billing in an accounting system that kept the TMS move ID on every invoice.

The president asks whether the history could be licensed. A metadata-only fit check shows the strongest record family is the chain from appointment to empty return, joined to per diem disputes and their outcomes. Counsel finds that two large forwarder customers prohibit sharing shipment details in any form, while most other customer agreements are silent on de-identified use.

The carrier scopes a package of tokenized container moves and dispute records, excludes the two restricted customers entirely, removes every driver identity and leaves cabin camera footage out. Before a planned system upgrade, the operations manager also exports the full TMS history so nothing is lost when the old database is retired.

How SourceX approaches drayage records#

SourceX handles a drayage package through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The records are licensed, not sold outright, so the operator keeps ownership. The first step runs on metadata only, such as system names, years of history and record families, so no container data leaves the operator during the assessment.

Rights review covers customer, equipment and portal terms; preparation removes driver and customer identities; and the operator approves the final scope before anything is delivered. Large histories stay in the operator's own storage or ship on encrypted drives, and the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization.