Intermodal drayage operators face a uniquely complex operational environment where ocean and domestic rail container movements intersect with strict free-time rules, chassis rental agreements, and terminal-specific billing cycles. Strong Tower Consulting has spent more than 18 years helping motor carriers design and implement systems that eliminate manual data entry, reduce chassis per-diem exposure, and defend against erroneous demurrage and detention invoices.
This guide details the technical architecture required to automatically ingest Class I rail ramp EDI 322 status messages, calculate Last Free Day (LFD) countdowns in real time, geofence terminal wait times, and generate auditable records for chassis split-fee and per-diem disputes. The architecture is TMS-agnostic and works alongside Truckmate, McLeod, TMW, and custom SQL-based dispatch systems.
Rail Ramp Data Acquisition Architecture
The foundation of any effective intermodal telematics solution is reliable, automated capture of rail ramp events. Most Class I railroads transmit EDI 322 intermodal status messages containing rail arrival, unload, available-for-pickup, and load events. These messages must be ingested, parsed, and matched to internal load records without human intervention.
A production-grade solution uses a dedicated EDI gateway that polls or receives 322 transactions via AS2 or SFTP, then stores the raw transaction in a normalized SQL schema. Key tables include:
- rail_322_raw - stores the original X12 payload with receipt timestamp
- rail_event - normalized events with container number, rail origin/destination, event code, and event datetime
- container_assignment - links container to internal order, chassis, and driver
Once normalized, the system can trigger real-time business rules. For example, an "unload complete" event (event code U7 or equivalent) starts the Last Free Day clock based on the specific terminal's free-time tariff.
Last Free Day (LFD) Engine Design
The LFD solver is the most critical component for intermodal carriers. It must account for:
- Terminal-specific free days (often 1-5 days depending on commodity and contract)
- Weekend and holiday rules that vary by port or ramp
- Early return credits for empty containers
- Chassis pool agreements that may shift the free-time responsibility
A robust LFD engine stores tariff matrices in SQL and calculates remaining free time on every status change. The calculation is exposed via an API endpoint that TMS dispatch boards can call to surface a color-coded countdown (green, yellow, red) next to each container.
| Rail Event Code | Description | LFD Trigger | Typical Free Days (Domestic) | Typical Free Days (Import) |
|---|---|---|---|---|
| RL | Rail Loaded | No | N/A | N/A |
| UR | Unloaded at Ramp | Yes - Start Clock | 2 | 4 |
| AV | Available for Pickup | Yes - Reinforce Clock | 2 | 4 |
| RL (empty return) | Empty Returned to Rail | Yes - Stop & Credit | 0 | 0 |
Geofenced Terminal Telematics Integration
Accurate terminal wait-time tracking is essential for both detention billing to shippers and defense against terminal demurrage charges. Modern ELD and telematics providers (including those already integrated with your fleet) can be configured to emit geofence events when a tractor crosses a virtual boundary around a rail ramp or ocean terminal.
These events should be written to a terminal_visit table that records arrival time, departure time, chassis number, and container number. When a carrier is later billed for demurrage or chassis per diem, the system can automatically generate a dispute package showing exact in-gate and out-gate timestamps, supporting documentation, and reference to the original EDI 322 record.
Chassis Per Diem and Split Fee Defense Workflow
Chassis split fees and daily per-diem charges represent one of the fastest-growing cost categories in intermodal drayage. A well-designed system automatically matches chassis usage against pool agreements and generates dispute files when the equipment provider's invoice does not align with actual usage or agreed free time.
The architecture typically includes a nightly reconciliation job that joins:
- EDI 322 arrival and departure events
- Telematics geofence records
- Chassis pool contract terms stored in a rate matrix table
- Driver settlement records from Truckmate or McLeod to validate equipment responsibility
When discrepancies are found, the system generates a PDF dispute packet containing timeline visualizations, raw EDI segments, and geofence timestamps. This packet is emailed to the chassis provider with a copy retained for audit.
Recommended SQL Schema Fragments
Core tables that have proven effective across multiple intermodal fleets include:
CREATE TABLE rail_322_raw (
id BIGINT IDENTITY(1,1) PRIMARY KEY,
container VARCHAR(20) NOT NULL,
event_code VARCHAR(10) NOT NULL,
event_ts DATETIME NOT NULL,
raw_x12 TEXT NOT NULL,
received_ts DATETIME DEFAULT GETDATE()
);
CREATE TABLE container_lfd (
container VARCHAR(20) PRIMARY KEY,
lfd_date DATE NOT NULL,
terminal_id VARCHAR(20),
free_days_remaining INT,
last_updated DATETIME DEFAULT GETDATE()
);Integration With Existing TMS Platforms
The architecture described above is deliberately TMS-agnostic. Whether your operation runs McLeod LoadMaster, Truckmate, TMW, or a custom SQL dispatch system, the rail ramp data can be pushed back into your operational database via scheduled SQL jobs or REST APIs. This allows dispatchers to see real-time LFD status directly in their existing load boards without learning a new interface.
For carriers also running EDI 204/214/210 transaction sets with their customers, the same normalized rail events can be used to generate accurate 214 status updates that reflect actual rail unload times rather than estimated times.
Implementation Roadmap
Strong Tower Consulting recommends a phased approach:
- EDI 322 ingestion and normalization (4-6 weeks)
- LFD calculation engine and tariff matrix (3-4 weeks)
- Telematics geofence integration and terminal wait-time tracking (4 weeks)
- Automated dispute generation and chassis per-diem reconciliation (4-6 weeks)
- Driver settlement and fuel surcharge validation layer (optional, 3 weeks)
Frequently Asked Questions
How do you handle varying free-day rules across different Class I railroads and ocean carriers?
We maintain a centralized tariff matrix table that is updated by operations staff through a simple web interface. The LFD engine references the specific SCAC, terminal, and commodity combination to apply the correct free days, weekend rules, and holiday calendar. This matrix is versioned so historical calculations remain accurate for dispute resolution.
Can this architecture work with both Truckmate and McLeod simultaneously?
Yes. The data ingestion and calculation layers are independent of the TMS. Normalized rail events and LFD results are written to SQL Server tables that both systems can read via linked servers, views, or nightly synchronization jobs. We have implemented this exact pattern for carriers running dual TMS environments during acquisition transitions.
What is the typical ROI timeline for an automated rail ramp telematics solution?
Most clients see measurable reduction in chassis per-diem and demurrage within 90 days. Average annual savings range from $180,000 to over $450,000 depending on fleet size and current exposure. Because Strong Tower Consulting and Exspeedite LLC are separately organized sister companies under common ownership, carriers are never required to purchase software. Our only product is better decisions.
How do you defend against chassis split-fee charges when the equipment provider claims the chassis was not returned on time?
The system creates an immutable audit trail using EDI 322 timestamps, telematics geofence events, and chassis pool contract terms. When a dispute arises, the platform automatically assembles a chronological report showing exact arrival, unload, and return times. This package has successfully reversed charges at all major chassis providers and Class I railroads.
Strong Tower Consulting, LLC was founded in Minnesota in 2008 by Scott Elliott. In business for more than 18 years, the firm continues to deliver independent, vendor-neutral guidance to motor carriers, freight brokers, and private fleets. For a no-obligation review of your current intermodal systems and processes, contact us at 763-244-1373.