Intermodal terminal operating layer: from radio coordination to event-driven execution
A documented Essentos deployment at a high-density intermodal terminal in Zaragoza, Spain, covering gate, yard, rail, weighing, EDI and a collaboration portal for hauliers without EDI, all running on the C-CORE evidence layer.
The challenge: an intermodal terminal outgrowing its coordination
This high-density intermodal terminal in Zaragoza had reached an operating volume its coordination tooling could no longer carry. Part of the inventory still lived on paper, cross-team comms ran over radio and most yard decisions were taken with no outbound visibility. The result accumulated daily: avoidable rehandles, long gate cycles and a growing administrative tail.
Essentos was deployed as the intermodal terminal operating layer, end to end: gate, yard with outbound-driven slotting, rail with departure-window priority, weighing integrated into the operation, EDI stabilized and a collaboration portal for actors without EDI connectivity. The operation moved from reactive coordination to event-governed execution, with prerequisites validated upstream and the team focused on real exceptions.
Operating context of the intermodal terminal
The terminal handles containers under an intermodal regime: truck inbound and outbound flow across the full shift, with rail departure windows tied to committed schedules.
The bottleneck was not equipment, and it was not surface area. It was the absence of synchrony between information and execution. When data lands late, the operation breaks at the moment of highest pressure: at the gate, in the yard or right before a rail composition closes.
Observed operating outcomes for intermodal terminal operations
Note: Figures observed in this Essentos deployment. Actual gains depend on volume, layout and the terminal's operating discipline.
Operating barriers identified during the intermodal deployment
Before deployment, the yard ran reactively. Without a reliable outbound view at receipt time, containers were stacked wherever space allowed, not where the logistics priority demanded. The pattern that followed was costly: when an urgent pickup or a rail cut arrived, the target box was buried three, four, even five high.
Each rehandle added minutes per unit and compounded into fuel, wear and lost cycle. Over a month, the effect quietly ate the yard's real capacity during high-pressure windows.
Parts of the site had uneven coverage, breaking the operating record whenever the system depended on stable connectivity. In a terminal that kind of outage is not an IT issue, it is a flow issue: when an event does not land on time, doubts surface and manual validation creeps back in.
Connectivity was reinforced with 5G to stabilize system access and protect continuity at the critical operating points. With stronger coverage, events are written consistently and the terminal stops absorbing stoppages caused by weak signal.
Weighing was a classic island. The reading was born at the weighbridge and entered the system through human transcription.
That human step was the source of administrative errors and unnecessary delays in the chain.
The weighbridge hardware was integrated directly so the reading is captured, bound to the container and linked into the operating flow with no manual transcription.
Scope of the Essentos intermodal deployment
A full intermodal terminal operating layer was deployed so the terminal could execute from a single shared reference, from gate to dispatch, and so connectivity would carry execution forward rather than block it.
The load-bearing change was anticipating exception detection. Instead of surfacing problems with the truck already at the gatehouse, prerequisites are verified before access. Missing data and inconsistencies are resolved upstream.
Operating result: Most of the flow moves automatically, and the team focuses on real exceptions instead of routine checks.
Not every haulier or external actor has EDI connectivity. The portal lets them reserve slots, upload documentation and pre-register cargo with no paper and no phone calls.
Operating result: One platform and one shared operating reference for both EDI and non-EDI actors.
EDI messaging and event consistency were stabilized so internal execution and the picture in the external ecosystem advance in sync. Discrepancies dropped and recurring manual confirmations went away.
With data in hand before placement, the yard stopped behaving like reactive storage. Slotting is now driven by dispatch priority: units with immediate departure land in fast-access zones, and longer-dwell units sit where they will not generate rehandles.
In parallel, the rail composition is aligned with live yard inventory, so discrepancies surface before any loading move starts.
Real operating change at the intermodal terminal
- The operation stopped depending on radio as its primary coordination system
- The yard moved from working without visibility to slotting by dispatch priority
- Weighing was wired into the operating flow and stopped being an isolated data point
- Coordination with third parties stopped relying on emails, calls and repeat confirmations
- The terminal took control of its operating information and, with it, gained real visibility of its capacity
Does your intermodal terminal need this same transformation?
If your intermodal terminal runs under yard pressure, demanding rail windows and fragmented external coordination, the answer is not more infrastructure. It is turning information into coordinated execution. Essentos delivers this intermodal terminal operating layer at terminals in Spain and across Europe and the United States, on the same C-CORE evidence foundation.