Marine Container & Chassis Pool Street-Turn Pairing: Drayage Systems Architecture

Intermodal drayage operations lose millions of dollars annually to unproductive terminal gate turns, bare-chassis repositioning, and chassis-pool interchange delays. Strong Tower Consulting designs and implements enterprise-grade automated street-turn solvers that intelligently pair empty marine containers with available chassis-pool assets and export loads, dramatically reducing gate congestion, fuel burn, and equipment dwell time.

Since 2008, Strong Tower Consulting, LLC has delivered transportation systems architecture and optimization engines to the most demanding motor carriers and intermodal drayage fleets in North America. Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership (separate EINs; liability firewall). Exspeedite is a Strong Tower company.

The Business Problem: Terminal Gate Inefficiency in Marine Drayage

At major U.S. container ports, drayage tractors routinely enter marine terminals to perform one of three unproductive moves:

Each of these moves consumes 45-90 minutes of gate time, fuel, and driver hours while adding zero freight revenue. Industry studies consistently show that 22-28% of all port gate transactions are pure equipment repositioning. Automated street-turn pairing engines eliminate the majority of these transactions by creating real-time, constraint-aware matches between empty containers, available chassis, and pending export orders.

Core Optimization Objective: The Street-Turn Solver

The street-turn solver is a mixed-integer linear programming (MILP) and constraint-programming hybrid engine that continuously solves for the lowest-cost, highest-service assignment of empty containers to export orders while respecting marine chassis pool rules, terminal appointment windows, equipment inspection standards, and driver hours-of-service.

Decision Variables

Variable Type Description
Xij Binary 1 if empty container i is assigned to export order j (street-turn)
Yjk Binary 1 if chassis-pool asset k is assigned to support export order j
Zlm Integer Number of bare-chassis repositioning moves between terminal l and chassis pool m

Objective Function (Simplified)

Minimize: Σ (GateCostij + FuelCostij + DelayPenaltyij) * Xij 
          + Σ ChassisPoolFeek * Yjk
          + Σ BareChassisMoveCostlm * Zlm

Systems Architecture Overview

The production-grade street-turn solver is implemented as a microservices-based event-driven architecture built for sub-60-second re-optimization cycles.

High-Level Systems Architecture for Automated Street-Turn Pairing
External Data Sources
├── EDI 322 / 404 (Ocean Carrier, Terminal, Chassis Pool)
├── Terminal Appointment API (e.g., PierPASS, Terminal-specific)
├── Chassis Pool Inventory (Pool operators - TRAC, Flexi-Van, etc.)
├── TMS / Order Management (Exspeedite or third-party)
├── Driver ELD / Mobile (real-time GPS & availability)
└── Equipment Inspection API (OCEMA, chassis condition)

                     ↓ (Kafka / MQTT events)

               Strong Tower Event Bus
                     ↓
┌────────────────────┬────────────────────┐
│   Real-Time Data   │   Constraint       │
│   Ingestion Layer  │   Engine Service   │
└────────────────────┴────────────────────┘
                     ↓
               Optimization Core
          (Gurobi + Google OR-Tools + Custom Heuristics)
                     ↓
┌────────────────────┬────────────────────┐
│   Solution         │   Validation &     │
│   Publisher        │   Business Rules   │
└────────────────────┴────────────────────┘
                     ↓
               Dispatch & Mobile
          (Exspeedite Dispatch Board + Driver App)
                     ↓
               Terminal Gate Execution
          (Automated appointment updates, gate pass issuance)

Key Data Entities and Mapping

Successful automation requires precise, normalized data models across disparate systems. The table below shows the canonical mapping used in Strong Tower implementations.

Source System Entity Key Attributes Target Model (Unified)
Ocean Carrier EDI Empty Container Container #, Size/Type, Location, Available Timestamp, Clean/Dirty status EmptyContainer (with geo-fence, readiness score)
Chassis Pool API Marine Chassis Chassis #, Pool ID, Last Inspection, Location (street or terminal), Status ChassisAsset (with pool contract rules, maintenance due date)
TMS Export Order Export Load Booking #, Earliest Pickup, Cutoff, Destination, Equipment Requirements ExportOrder (with time windows, hazmat flags, weight)
Terminal System Appointment Window Terminal ID, Gate Slot, Transaction Type (street-turn allowed?) TerminalConstraint (hard/soft windows, transaction rules)

Constraint Categories Implemented

Hard Constraints (must be satisfied)
  • Container type and export booking compatibility (20/40/45, reefer, high-cube)
  • Chassis pool ownership and interchange agreement rules
  • Terminal appointment slot availability and street-turn eligibility
  • Driver hours-of-service and maximum driving distance for street-turn
  • Equipment inspection validity (valid safety inspection within 90 days)
Soft Constraints (weighted penalties)
  • Preferred chassis pool utilization targets
  • Driver familiarity with specific terminals
  • Minimization of chassis dwell time at customer sites
  • Balancing workload across drayage fleet

Implementation Workflow: From Event to Executed Street-Turn

  1. Event Ingestion: Real-time EDI 322, terminal API, and chassis-pool status updates are normalized and published to the event bus.
  2. Readiness Scoring: Each empty container and chassis receives a dynamic readiness score based on location, inspection status, and time-to-gate.
  3. Incremental Re-Optimization: The solver is triggered on a 45-second cycle or on significant events (new export order, new empty availability, appointment change).
  4. Solution Validation: Human-in-the-loop review for exceptions exceeding penalty thresholds. Approved solutions are published to the dispatch board.
  5. Automated Execution: Approved street-turns trigger:
    • Updated terminal appointments (API)
    • Driver mobile assignments with precise routing and gate instructions
    • Chassis-pool interchange confirmation
    • EDI 990/214 status updates to ocean carriers
  6. Post-Move Reconciliation: Actual gate transaction data is compared against planned solution. Variances feed back into the constraint weights and readiness models.

Measured Results from Deployed Systems

Strong Tower Consulting implementations at scale have consistently delivered:

These outcomes are achieved through rigorous data integration, accurate constraint modeling, and continuous tuning of the solver against live terminal and chassis-pool behavior.

Technology Stack Recommendations

For enterprise-grade performance and maintainability, Strong Tower recommends the following stack for the street-turn solver:

Getting Started: Assessment and Roadmap

Implementing an automated street-turn solver requires mature data integration, accurate equipment visibility, and disciplined operational processes. Strong Tower Consulting offers a structured four-week technical assessment that maps your current terminal, chassis-pool, and TMS data flows, identifies constraint gaps, and delivers a prioritized implementation roadmap.

Ready to reduce port gate congestion and eliminate unproductive bare-chassis moves? Schedule a technical assessment or contact Strong Tower Consulting at 763-244-1373.

Related Practices & Insights