Intermodal Drayage Demurrage & Ocean Container Per Diem Mitigation Playbook

Executive Summary

Intermodal drayage carriers continue to lose millions annually to avoidable demurrage, storage, and chassis per diem charges. Most of these losses are not caused by operational failure but by the absence of real-time event visibility, automated exception handling, and defensible documentation.

This playbook presents the systems architecture used by leading intermodal carriers to reduce these expenses by 65-85 percent. The solution combines terminal EDI 322 ingestion, web-scraped Last Free Day (LFD) data, dual-transaction turn logic, and automated dispute compilation that meets Federal Maritime Commission (FMC) OSRA-22 standards.

Strong Tower Consulting designs these solutions to work alongside your existing Truckmate, McLeod, or TMW dispatch system without forcing a full TMS replacement.

The Real Cost of Uncontrolled Demurrage and Per Diem

Typical mid-size intermodal drayage operations (75-150 power units) incur between $1.2M and $3.8M per year in combined demurrage, rail storage, and chassis per diem. Industry data shows that 38-47 percent of these charges are avoidable through better process control and documentation.

Common failure points include:

• Missing or delayed EDI 322 reports from marine terminals and rail ramps
• Manual entry of container return times creating timestamp disputes
• Inability to prove chassis interchange times to pool operators
• Lack of automated evidence packages when disputing charges under FMC rules

Core Systems Architecture for Mitigation

The mitigation framework rests on four integrated layers:

1. Event Ingestion Layer - Real-time consumption of EDI 322, 214, and terminal API/web data
2. Correlation Engine - SQL-based matching of container, chassis, and load records across disparate systems
3. Decision & Automation Layer - Business rules that trigger status updates, alerts, and dispute generation
4. Evidence & Settlement Layer - Compiled PDF and EDI 210 packages for carrier, terminal, and pool billing disputes

This architecture is deliberately vendor-neutral. Whether your primary system is McLeod, TMW Systems, or Truckmate, the mitigation layer operates independently.

EDI 322 and 214 Event Workflows

The foundation of effective mitigation is accurate, timestamped event data. EDI 322 reports from marine terminals provide critical status events including:

• Arrival at terminal (AV)
• Loaded on vessel or rail (LD)
• Available for pickup (AP)
• Return of empty container (RE)

These events must be mapped to internal load records within seconds of receipt. Our recommended approach uses a dedicated EDI gateway that normalizes 322 transactions into a unified SQL schema before writing to a central event log. From there, automated 214 status updates are generated and transmitted to the ocean carrier or beneficial cargo owner (BCO) with precise GPS-verified timestamps.

Terminal Web Scraper and Last Free Day Tracking

Many terminals still do not transmit Last Free Day information reliably via EDI. The solution is a secure, rules-based web scraper that polls terminal customer portals every 15 minutes for each active container. Extracted LFD dates are stored alongside the container number, bill of lading, and terminal code.

When combined with the EDI 322 data, this creates a single source of truth for free-time calculations. The system automatically flags containers approaching their LFD and recommends accelerated dispatch or provides documentation for unavoidable delays caused by terminal congestion.

Dual-Transaction Turn Solvers

One of the most effective tools for reducing chassis per diem is the dual-transaction turn solver. This logic identifies opportunities to use a single chassis for both a loaded move and an empty return (or vice versa) within the same terminal or rail facility.

The solver continuously scans open loads, available chassis pools, and container status to recommend optimized sequences. When executed, these turns reduce daily chassis rental days by an average of 0.7 per container move.

Chassis Pool Interchange Billing Reconciliation

Chassis pool operators (OCP, TRAC, Flexi-Van, etc.) bill per diem on a daily basis with little transparency. The reconciliation engine ingests pool invoices, matches them against internal GPS and EDI 214 return events, and automatically generates disputes for any charges assessed after documented interchange.

This process typically recovers 22-31 percent of billed per diem in the first six months of operation.

Automated Demurrage Dispute Evidence Compilation

Under the Ocean Shipping Reform Act of 2022 (OSRA-22), marine terminals and ocean carriers must apply a "reasonable" standard when assessing demurrage and detention. Carriers that can produce clear, timestamped evidence of when containers were returned or when delays were caused by the terminal have dramatically higher success rates in disputes.

The playbook includes an automated evidence compiler that assembles:

• EDI 322 transaction history
• GPS-verified return timestamps
• Terminal web portal screenshots
• Driver settlement records showing attempted pickup times
• Calculated free-time windows

These packages are generated as searchable PDFs and can be submitted via the ocean carrier's dispute portal or through the FMC billing complaint process.

Demurrage vs. Detention vs. Per Diem Comparison

Frequently Asked Questions