Essentos
Use case | Yard management for container terminals

Yard management with slot decision rules that protect departures and capacity

How Essentos rebuilt yard management for container terminals: slot-level inventory, physical stacking and weight rules, and outbound-driven zones to cut rehandles and recover real capacity at an intermodal terminal in Spain.

A yard that worked, but could not hold up under pressure

At this inland and intermodal terminal the yard was running, but it was not stable. Occupancy moved with the campaign calendar, units piled up in the easy zones and the team burned shift time on searches and last-minute repositioning. There was no single visible failure: just a daily accumulation of moves without value, retries and lost rhythm whenever occupancy ran close to its ceiling.

Essentos deployed a yard management layer with three load-bearing pieces: real slot-level inventory, written physical rules (stacking heights, weight, compatibility) and outbound-driven zoning. After several months of tracking, the picture was unambiguous: fewer repeat moves, a more coherent yard at high occupancy and more real capacity without adding a square metre.

Yard operating sequence at a container terminal
Slot · Purpose-driven zones · Physical rules · Zone pressure
Yard
Slot Real inventory by unit and slot
one shared reference across yard, gate and admin
Zones Outbound · Preparation · Buffer · Holding
a container yard organized by dispatch priority
Fast release · truck
Preparation · dispatch
Buffers · peaks
Holding · no immediate outbound
Physical rules Stacking · Weight · Compatibility
safety and consistency under occupancy pressure
Pressure Zone occupancy at a glance
anticipate saturation before it blocks the flow
Fast release80 %
Preparation70 %
Buffers55 %
Observed operating impact on yard management
20% Placement efficiency
Slot decision rules tied to expected outbound flow cut repositioning from the first move.
40% Non-value moves
Outbound-driven slotting reduces unnecessary rehandles across the shift.
25% Zone pressure control
Earlier saturation detection per zone keeps blockages from forming.

Note: Figures observed in comparable Essentos yard management deployments. Actual gains depend on layout, volume and operating discipline.

Day-to-day operation at a container yard

The terminal handles containers with both truck and rail dispatch. The yard is both an operating buffer and the preparation area for outbound flow, so every poor slot decision compounds across the shift.

Yard volume and operating dynamics
  • Between 1,200 and 2,100 units per month moved through the yard, including inbound, outbound and internal repositioning
  • Typical occupancy around 65 to 80 percent, with campaign weeks pushing above 85 percent
  • Truck departures prepared throughout the day, with rail train makeup prepared inside fixed operating windows
Roles involved in the yard
  • 1 yard supervisor running priorities and resolving exceptions
  • 2 to 4 yard or crane operators (depending on the day and workload) executing moves and rehandles
  • 1 administration or planning role handling searches, exceptions and slot confirmations whenever doubts surfaced

When slot data is unreliable or the yard loses coherence, the cost multiplies: the team moves more boxes, makes weaker decisions and arrives late to the outbound flow.

Scope of the yard management deployment

The brief was to build a governable container yard, not a tidy inventory view. Essentos worked along three operating pillars, all backed by C-CORE evidence:

1) Slot-level inventory with operating truth

Each unit is bound to a real slot and to a visible operating status. Search time drops and the yard stops running on two parallel realities: what the system says and what the team remembers.

2) Physical and operating rules per slot

The yard now runs on criteria the team can read and follow:

  • Stacking heights per zone
  • Weight and placement criteria
  • Compatibility rules and safety restrictions
  • Area organization around distinct operating objectives
3) Outbound-driven zones with operating purpose

Each zone was defined by a clear operating intent:

  • Fast-release truck areas
  • Preparation and pre-positioning areas for dispatch
  • Buffers sized to absorb peaks
  • Holding zones for units with no immediate outbound flow

The yard ended up built for dispatch, not for static storage.

Real operating change inside the yard

  • Less shift time spent searching for units flagged for release, inspection or service
  • Fewer rehandles caused by saturation in the easy zones
  • Fewer repeated moves caused by "put it where it fits" instead of "put it where it belongs"
  • Better coordination at high occupancy because the team knew which slots to protect and which to release

The supervisor moved from running the yard on intuition to running it on operating criteria: zone occupancy, operating pressure and outbound priority.

Operating indicators tracked for yard performance

Indicators were tracked monthly because yard performance only shows up across periods, campaigns and pressure conditions:

  • Total internal moves and share of non-value moves
  • Rehandles per unit (how often the same box gets moved without going out)
  • Average locate time for releases and inspections
  • Zone occupancy and pressure in critical areas
  • Dwell by unit family and by zone, when relevant

Does your container yard lose coherence when occupancy climbs?

If your yard loses order at high occupancy and the team spends shifts searching, repositioning and deciding without slot data, Essentos can help you define zones, rules and an executable yard management model. The same model runs at container terminals in Spain and across Essentos deployments in Europe and the United States.

Related modules

Solution