Dual-Mission Turn & Chassis Split Optimization: Drayage Systems Architecture

A technical implementation guide for marine and rail drayage carriers seeking to automate dual-mission turn pairing, empty chassis split routing, and terminal bobtail reduction through enterprise-grade dispatch optimization algorithms.

Category: Intermodal Drayage & Dispatch Primary Subject: Intermodal Dual-Mission Turn Pairing & Chassis Split Dispatch Optimization

Marine and rail drayage carriers routinely burn fuel and driver hours when executing separate single-mission trips for container imports and chassis returns. Strong Tower Consulting designs automated dispatch sequencing algorithms that pair inbound import container pickups with outbound export deliveries and chassis pool splits, eliminating empty bobtail miles and maximizing driver revenue per hour.

Since 2008, Strong Tower Consulting, LLC has delivered transportation systems architecture to the most demanding drayage operators in North America. This guide details the exact data model, constraint engine, routing solver, and integration architecture required to operationalize dual-mission turns and chassis-split logic at enterprise scale.

The Operational Inefficiency Problem

Traditional drayage dispatch treats each container move as an independent task. A typical import load might require:

An export load adds the reverse sequence. When these missions are dispatched independently, drivers average 38-47% non-revenue miles. Automated dual-mission solvers collapse these into a single efficient tour while simultaneously solving the chassis inventory split problem across multiple terminal and pool locations.

Systems Architecture Overview

Figure 1: High-Level Dual-Mission Turn Solver Architecture
+-------------------+     +---------------------+     +------------------------+
|   Order Ingestion |---->|   Mission Graph     |---->|   Dual-Mission Solver  |
| (EDI, API, Portal)|     |   Builder (GraphQL) |     | (Constraint + Routing)|
+-------------------+     +---------------------+     +------------------------+
                                 |                               |
                                 v                               v
                       +-------------------+           +---------------------+
                       | Chassis Inventory |           | Terminal Gate Window|
                       |   State Machine   |<--------->|   & Appointment API |
                       +-------------------+           +---------------------+
                                 |
                                 v
                       +---------------------+
                       | Dispatch Execution  |
                       |   (Exspeedite TMS)  |
                       +---------------------+

The architecture is built around a time-dependent, multi-commodity graph where nodes represent physical locations (marine terminals, rail ramps, customer facilities, chassis pools) and edges encode travel times, gate windows, chassis availability, and equipment compatibility constraints. Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership (separate EINs; liability firewall). The solver is typically deployed as a microservice that feeds optimized tours into the Exspeedite dispatch board.

Core Data Model & Entity Relationships

Table 1: Primary Entities in the Dual-Mission Solver
Entity Key Attributes Relationships
Mission id, type (import/export/empty), containerNumber, chassisType, earliestStart, latestEnd, origin, destination, revenue, priority belongsTo Order, requires ChassisPool, compatibleWith Terminal
DriverShift id, driverId, startTime, endTime, homeTerminal, availableHours, currentLocation, currentEquipment assignedTo Tour, hasCurrent Chassis
ChassisPool id, location, owner, availableCount, chassisType, dailySplitTarget, currentInventory supplies Chassis to Missions, targetSplitRatio
Tour id, driverId, sequenceOfMissions, totalBobtailMiles, totalRevenue, totalDriveTime, chassisSplitEvents contains 2-4 Missions, respects HOS, meets TerminalWindows

Dual-Mission Turn Pairing Algorithm

The solver employs a hybrid approach combining constraint programming with a custom column-generation heuristic. The objective function is defined as:

Maximize: Σ(revenue_mission) - (fuel_cost * total_miles) - (driver_hour_cost * total_hours) + (bobtail_reduction_bonus * eliminated_empty_miles)

Core Constraints

  1. Chassis conservation: number of chassis pulled from pool cannot exceed available inventory at each timestamp.
  2. Terminal gate windows: all arrivals must fall inside published or API-scheduled appointment slots.
  3. Equipment compatibility: import/export container types must match chassis height, pin configuration, and weight ratings.
  4. Driver hours of service: cumulative on-duty time cannot exceed FMCSA limits within the tour.
  5. Chassis split logic: each chassis drop at a pool must be paired with a subsequent pickup of a different chassis type when required by the next mission.
  6. Precedence: import delivery must precede any export pickup that uses the same chassis (street-turn logic).

Strong Tower Consulting implements this solver using a combination of Google OR-Tools CP-SAT for initial feasible solutions and a custom large-neighborhood search that iteratively destroys and repairs mission pairs. Typical solve time for a 180-driver fleet with 420 daily missions is under 90 seconds on commodity cloud infrastructure.

Empty Chassis Split Routing & Terminal Bobtail Reduction

Chassis split optimization is the most complex sub-problem. Many terminals require that an empty chassis be returned before a new one can be pulled. The solver maintains a rolling inventory projection for each chassis pool and terminal and inserts "split moves" (drop one chassis, immediately pull another) at optimal points in the tour.

Key performance outcomes observed across multiple deployments include:

Integration Workflows with Existing TMS

The dual-mission solver is designed as an event-driven microservice. Primary integration points include:

Table 2: Integration Interfaces
System Direction Protocol Payload
Exspeedite TMS (sister company under common ownership) Bidirectional REST + WebSocket Order, Mission, Driver, Chassis state
Terminal Appointment APIs (Pasha, SSA, APMT, etc.) Outbound JSON/EDI Proposed arrival windows
Chassis Pool Providers (TRAC, Flexi-Van, etc.) Inbound API polling Real-time inventory by type and location
ELD / Telematics Inbound MQTT Current driver location and HOS status

Strong Tower Consulting, LLC provides the full integration layer, including idempotent event handling, optimistic locking on chassis counts, and graceful degradation when real-time data feeds are unavailable.

Implementation Roadmap

  1. Discovery & Data Audit (4-6 weeks): Map all current order sources, terminal APIs, chassis pool feeds, and dispatch workflows.
  2. Graph & Constraint Model Build (6-8 weeks): Construct the location graph and encode business rules into the constraint engine.
  3. Solver Development & Tuning (8-10 weeks): Implement column generation, test against historical data, and calibrate objective weights.
  4. Exspeedite Integration & UI Enhancements (4 weeks): Surface optimized tours in the dispatch board with driver acceptance workflow.
  5. Parallel Run & Go-Live (4 weeks): Shadow current dispatch, measure KPI lift, then cut over.

Typical total project duration is 5-7 months from kickoff to full production use.

Measured Enterprise Outcomes

Carriers who have implemented this architecture routinely achieve 22-31% improvement in loaded miles percentage and 17-26% reduction in total fuel expense. These gains are delivered without increasing fleet size and while improving on-time performance at marine and rail terminals.

Frequently Asked Questions

What is the minimum fleet size for positive ROI?
Most deployments achieve payback within 7-9 months with 35 or more daily drayage drivers. Smaller fleets can still benefit but typically require a shared SaaS version of the solver.
Does the system support street turns?
Yes. Street-turn logic is a first-class constraint. When an import and export can share the same chassis without returning to a pool, the solver automatically prefers that sequence and adjusts the chassis inventory projection accordingly.
How does the solver handle appointment changes?
The system subscribes to terminal appointment webhooks and re-optimizes only the affected tours in under 15 seconds, pushing updated instructions to drivers via the Exspeedite mobile application.

Ready to Eliminate Bobtail Miles?

Strong Tower Consulting, LLC has been delivering transportation technology architecture since 2008. Our team combines deep intermodal operational knowledge with modern constraint-based optimization techniques.

Request a Drayage Optimization Assessment or call us directly at 763-244-1373 to discuss your specific terminal mix, chassis pool agreements, and dispatch challenges.

Explore additional technical guidance:
Intermodal Drayage Dispatch Optimization Practice
Automated TMS Implementation
Rail Intermodal Visibility & Integration Guide

Enterprise Systems Advisory

Ready to modernize your transportation management software, eliminate manual spreadsheets, or optimize telematics and recruiting workflows? Contact Strong Tower Consulting for direct architect guidance.

Schedule Architecture Consultation