Empty Container Depot Re-Direction & Swap: Drayage TMS Systems

Drayage motor carriers routinely suffer heavy financial losses when ocean carriers abruptly issue empty container return location changes while drivers are en route. Strong Tower Consulting designs automated empty depot swap solvers that ingest ocean carrier steamship line EDI and API broadcast updates, instantly re-route en-route drivers, generate automated diversion billing invoices, and maintain accurate IEP interchange reconciliation.

Since 2008, Strong Tower Consulting has delivered transportation systems architecture to intermodal drayage fleets across North America. Our specialized empty container redirection engines eliminate the majority of avoidable detention, deadhead miles, and gate rejection costs that plague conventional drayage operations.

The Operational Problem: Last-Minute Depot Changes

Ocean carriers and terminal operators frequently change the designated empty return depot after a container has been unloaded. When this occurs after the driver has left the terminal, the carrier faces:

• Rejected gate transactions at the original depot
• Additional empty miles (often 40-90 miles round-trip)
• Chassis detention charges from both the original and new location
• Disrupted driver hours-of-service and load sequencing
• Manual invoice creation for diversion charges that are frequently disputed

Without real-time automation, these events create both direct cost leakage and significant administrative overhead.

Architecture of an Automated Empty Depot Swap Solver

The solution is a purpose-built microservice that operates alongside or inside a modern drayage TMS. Core components include:

Event Ingestion Layer
    ├── Ocean Carrier EDI 214 / 990 (real-time)
    ├── Terminal API status feeds
    ├── Driver ELD GPS telemetry
    └── Order and equipment master data

Rule & Optimization Engine
    ├── Business rule repository (per steamship line)
    ├── Cost calculation matrix (deadhead, detention, diversion)
    ├── Geospatial routing engine with live traffic
    ├── Driver & chassis availability checker
    └── Multi-objective solver (cost, time, utilization)

Decision & Execution Layer
    ├── Driver mobile push / dispatch update
    ├── Automated diversion billing record
    ├── IEP 401/501 interchange message generator
    └── Reconciliation ledger for ocean carrier disputes
    

The solver runs continuously. When an empty return change event arrives, it evaluates the current position of the driver, compares all approved depot options, and selects the lowest total landed cost solution that also respects terminal cut-off times and driver availability.

Data Flow and Integration Points

Successful deployment requires clean integration with five primary systems:

Dynamic Re-Direction Billing Automation

One of the highest-ROI features is the automatic creation of diversion invoices. When the solver approves a swap, it immediately:

1. Calculates additional miles using the carrier's rate matrix
2. Applies the correct detention and diversion accessorial codes
3. Generates a line item tied to the original load number
4. Attaches GPS breadcrumb proof and EDI event timestamps
5. Posts the charge to the host TMS accounts receivable workflow

This eliminates the "we never received the diversion notice" disputes that commonly reduce recovery rates.

Cross-Practice Applications

The same solver architecture delivers value beyond pure drayage. Carriers engaged in specialized heavy haul and brokerage and 3PL operations use similar real-time re-direction logic when equipment or route changes occur mid-transit. The underlying decision engine is reusable across use cases.

Strong Tower Consulting frequently implements these solvers as part of broader TMS implementation and ELD-EDI integration projects. The solver also pairs naturally with carrier rate matrix optimization work to ensure diversion charges reflect current contractual economics.

Implementation Roadmap

A typical deployment follows this sequence:

1. Current-state assessment of EDI ingestion, rate matrices, and billing workflows
2. Mapping of each steamship line's depot rules and interchange requirements
3. Development or configuration of the solver microservice
4. Integration with the host TMS and mobile driver application
5. Parallel testing against historical diversion events
6. Go-live with exception-based human review
7. Continuous tuning of the cost and routing algorithms

Most clients see measurable reduction in empty miles and detention within the first 90 days of production use.

Frequently Asked Questions

Exspeedite is a Strong Tower company under common ownership. All systems architecture, integration, and optimization services are delivered by Strong Tower Consulting, LLC (founded 2008 in Minnesota).