How a high-density intermodal terminal moved from radio-based coordination to event-driven execution
Full operational digitization at a high-density intermodal terminal in Zaragoza: gate, yard, rail, weighing, EDI and external collaboration
The challenge of an intermodal terminal growing faster than its coordination
This high-density intermodal terminal in Zaragoza had reached an operating volume that exceeded its coordination tools. Part of the inventory was still tracked on paper, team communication depended on radio, and too many yard decisions were made without outbound visibility. The result was accumulated daily friction: avoidable repositioning, extended gate cycles and a growing administrative burden.
Essentos was deployed as the operating layer for the terminal, covering the complete flow from gate to dispatch: outbound-driven yard logic, rail priority, integrated weighing, stabilized EDI and a collaboration portal for actors without EDI connectivity. The operation moved from reactive to event-governed, with early validation and management focused on real exceptions.
Terminal operating context
The terminal handles containers in an intermodal regime, with truck inbound and outbound flow throughout the day and rail windows with committed schedules.
The bottleneck was neither equipment nor space. It was the lack of synchronization between information and execution. When data arrives late, the operation is disrupted at the highest-pressure moment: at the gate, in the yard, or just before closing a rail composition.
Observed operating outcomes
Results observed in this specific deployment. Actual improvement depends on volume, layout and each terminal's operating discipline.
Operating barriers identified during deployment
Before deployment, the yard was being managed reactively. Without a reliable outbound view at the moment of receipt, containers were stacked wherever space was available instead of where logistics priority said they should go. That created an expensive pattern: when an urgent pickup or a rail composition appeared, the target unit could be buried at the bottom of a stack three, four, or even five high.
Every rehandle added minutes per unit and multiplied fuel use, wear, and cycle loss. Over the course of a month, the effect accumulated and reduced the yard's real capacity during high-pressure periods.
The site had areas with uneven coverage, and that affected the continuity of operating records whenever the system depended on stable connectivity. In a terminal, that kind of interruption is not just an IT issue. It is a flow issue: if an event is not recorded on time, uncertainty appears and manual validation comes back into the process.
Connectivity was reinforced through 5G to stabilize access to the systems and protect continuity at critical operating points. With stronger coverage, events are recorded consistently and the terminal avoids stoppages caused by weak signal.
Weighing was a classic island: the data was born at the scale, but entered the system through manual transcription.
That human step was the source of administrative errors and unnecessary delays.
The weighing hardware was integrated directly so the data could be captured, tied to the container, and linked to the operating flow without manual transcription.
Scope of the Essentos deployment
A full operating layer was deployed so the terminal could execute from a shared reference, from gate entry to dispatch, and so connectivity would drive execution instead of slowing it down.
The most significant change was anticipating issue detection. Instead of discovering problems with the truck already at the gatehouse, prerequisites were verified before access: incomplete data or inconsistencies were resolved in advance.
Operating result: Most of the flow advanced automatically, and the team could focus on real exceptions instead of routine checks.
Not every carrier or external actor has EDI connectivity. The portal allowed them to reserve time slots, upload documentation and pre-register cargo without relying on paper or 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 that internal execution and the information reflected in the external ecosystem advanced in sync. This reduced discrepancies and eliminated recurring manual confirmations.
With data available before placement, the yard stopped functioning as reactive storage and was organized by dispatch priority. Units with immediate departure were placed in fast-access zones, while longer-dwell units were positioned to avoid generating repositioning.
At the same time, the rail composition was aligned with real yard inventory, and discrepancies were detected before loading moves began.
Real operating change after deployment
- The operation stopped depending on radio as its primary coordination system
- The yard moved from operating without visibility to being organized by dispatch priority
- Weighing was integrated into the operating flow and stopped being an isolated data point
- Coordination with third parties stopped depending on emails, calls and repeated confirmations
- The terminal gained control over its operating information and, with it, real visibility of its capacity
Does your intermodal terminal need this transformation?
If your terminal operates under yard pressure, demanding rail windows and fragmented external coordination, the leap is not expanding infrastructure. It is turning information into coordinated execution.