Intermodal Drayage Empty Matchbacks: Street Turn Optimization & Export Solvers

Intermodal drayage operators face one of the most persistent inefficiencies in North American freight transportation: the empty container problem. An import ocean container is delivered, stripped of its cargo at a warehouse or distribution center, and then the power unit returns the empty box to a congested marine terminal or off-dock depot. Simultaneously, an export shipper - often moving agricultural commodities or manufactured goods - must dispatch a separate truck to retrieve an empty container from a distant yard before loading can begin. The result is duplicated miles, excessive gate transactions, wasted driver hours, and unnecessary carbon emissions.

Strong Tower Consulting has spent more than 18 years helping motor carriers, freight brokers, and intermodal drayage operators replace these fragmented movements with engineered, continuous triangle routes. This guide details the software engineering, database design, workflow automation, and integration patterns required to implement production-grade street-turn optimization and export solvers inside modern TMS platforms.

The Scale of the Inefficiency

Standard intermodal drayage practice creates three distinct truck movements where one continuous route could suffice:

1. Import loaded move from terminal to consignee (de-vanning location)
2. Empty return from consignee to marine terminal or designated empty return yard
3. Separate empty pull from depot to export shipper for loading

When these legs are performed by the same motor carrier under a street-turn (matchback) arrangement, the empty return leg is eliminated. The de-vanned import container is reloaded directly with export cargo and returned to the terminal as a loaded export. This removes one full bobtail or empty container move per successful match.

Core Components of an Automated Matchback Engine

A production intermodal TMS matchback solver must integrate four primary data domains in near real time:

• Import Visibility Layer: Container discharge, availability, and de-vanning appointment data received via EDI 315, 322, or ocean carrier APIs.
• Export Order Book: Firm and forecasted export bookings with required equipment type, commodity, load date, and destination port.
• Equipment Master & Ownership Rules: Current container owner/operator, lease terms, permitted commodities, and any hazardous or temperature restrictions.
• Geographic & Temporal Constraints: Driving times between facilities, terminal gate hours, chassis availability, and driver hours-of-service windows.

The solver runs on a configurable cadence - typically every 15 to 30 minutes - and produces ranked candidate matches. Each candidate includes a projected financial benefit (avoided empty miles, gate fees, chassis rental days) and a risk score based on historical on-time performance of the involved shippers and receivers.

Database Schema Foundations for Matchback Logic

Effective matchback automation begins with a normalized, query-efficient schema. Key tables include:

Indexes on geographic columns (using PostGIS or equivalent) and composite indexes on (owner_code, size_type, status) enable sub-second candidate generation even at scale.

Street-Turn Approval Automation

Securing ocean carrier approval for a street turn remains the largest source of operational friction. Most steamship lines require formal interchange re-assignment before a container can be loaded with a new shipper's cargo. This is typically handled through one of three channels:

• eModal or terminal operator portals
• Avantida or similar interchange platforms
• Direct EDI 322 (Status Details - Ocean) or 353 (Event Detail) transactions

A mature TMS implementation maintains carrier-specific adapters that translate an approved internal matchback candidate into the required message format, submit the request, poll for approval status, and surface exceptions to operations teams. Once approval is received, the system automatically updates the dispatch board to show a single continuous triangle: import delivery → de-vanning → export loading → terminal return.

Export Solver Algorithm Design

The export solver is a constrained optimization routine that can be implemented with mixed-integer linear programming (via OR-Tools or PuLP) or a high-performance greedy heuristic for real-time use. Primary decision variables include binary assignment flags between each eligible import container and each export order.

Objective function components typically include:

• Minimize total empty and bobtail miles
• Minimize chassis day charges and demurrage risk
• Maximize on-time performance against vessel cutoff times
• Respect equipment ownership and commodity compatibility rules

Constraints incorporate terminal free-time rules, driver availability from the ELD feed, and shipper-specific loading appointment windows. Strong Tower Consulting recommends starting with a heuristic solver that runs in under 10 seconds, then layering an exact MIP solver for nightly optimization of the next-day plan.

Continuous Triangle Routing and Dispatch Integration

Once a matchback is approved, the TMS must collapse three separate orders into a single driver tour. This requires tight integration with the carrier's ELD and EDI systems to transmit accurate load and stop sequences. The dispatch interface should display the full triangle on a map with estimated times between each stop, including realistic terminal gate wait times derived from historical data.

Integration points include:

• Real-time position updates from ELD providers
• Automated EDI 214 shipment status updates at each stop
• Chassis tracking to ensure legal equipment is available for each leg
• Automated notification to the export shipper confirming the street-turn container details

Compliance and Accounting Considerations

Street-turn operations introduce specific requirements for revenue recognition, cost allocation, and regulatory reporting. The TMS must correctly attribute revenue to both the import and export customers while allocating the single continuous move's costs. This demands robust transportation accounting integration that can split or combine loads at the stop level.

From a compliance standpoint, accurate record-keeping of interchange approvals is essential for dispute resolution with ocean carriers. All approval references, timestamps, and message payloads should be retained for the required retention period.

Strong Tower Consulting's transportation accounting integration practice ensures these financial and compliance workflows are correctly modeled during TMS implementations.

Implementation Best Practices

Organizations seeking to deploy or enhance matchback automation should consider the following sequence:

1. Baseline current empty repositioning costs and terminal gate transactions using existing reporting capabilities.
2. Map all current EDI and portal interfaces with ocean carriers and terminal operators.
3. Design and normalize the container and order data model described above.
4. Implement the candidate generation and scoring engine with clear visibility into why specific matches are accepted or rejected.
5. Add automated approval submission and status monitoring.
6. Integrate the resulting continuous moves into dispatch, ELD, and accounting workflows.
7. Establish continuous improvement processes using historical match acceptance rates and realized savings.

Our TMS implementation practice, business process optimization practice, and ELD/EDI integration practice provide the technical depth required to execute this roadmap successfully.