A terminal is a yard, a gate, a berth, a control network and a customs boundary at the same time, and the water in front of it is a perimeter with no fence. Cargo, cyber, access, airspace and weather risk all act on the same berth window, and each one is watched by a different desk on a different system.
One shift at a container terminal. Every system does exactly what it was bought to do, and every operator follows the procedure correctly.
The documentation desk applies both amendments as filed.
Amendment appliedThe service desk confirms the vendor holds a live contract and closes the check.
Access verifiedThe gate clerk refuses entry and logs the turn-away.
Entry refusedThree desks, three queues, three correct procedures. The documentation system, the controls access log and the gate refusal record do not talk to each other, and nothing on the terminal is responsible for the line that runs through all three. At the shift handover the three items are read out separately, if they are read out at all. The pattern was never the problem. Ownership of the pattern was.
The same six domains resolve onto every estate. This is what they are when the estate is a port.
The terminal operating system, the port community system and the manifest messaging behind them, plus the control networks under ship-to-shore and yard cranes, gate automation and reefer power. A controls alarm and a network alert are the same story more often than either console can tell.
Truck and pedestrian gates, cameras and intrusion detection across the yard, patrol and incident reporting, and the access record that says who was on the terminal and when. The approach is the part of the perimeter that cannot be fenced.
Detection is now common at terminals. The unanswered question is what a track means alongside a berth window, a gate event and a network alert in the same hour, and who is authorized to act on it.
Bookings, manifests and customs declarations, haulier and drayage scheduling, stevedore and lashing crews, and the vendors who sit upstream of a crane or a gate system. Cargo integrity and access are the same exposure viewed from two directions.
Wind that stops crane work, visibility on the approach, tide and draft on the channel, and a storm that closes the landside corridor. That is one event acting on throughput, not several unrelated tickets, and counting it twice is its own failure.
Sanctions exposure, ownership and flag history on a calling vessel, labor action on the dock, and instability along a trade lane. All of it changes what a routine indicator on the berth actually means.
The same event matters differently at the gate, in the terminal operations center and at the port director's desk. One object, delivered at each altitude, with the clock that altitude actually runs on.
What changed against the berth and yard plan in the last hour, and what it costs to hold a move or work around it.
The ranked picture across domains, the converging set behind each item, and the option set with an owner attached, in the language the facility security plan already uses.
What is moving on the water, what posture is recommended for the approach and the berths, and what has to be passed to customs, police and the coast guard liaison.
Comparable exposure across terminals and berths, ranked by policy that was ratified rather than inferred by a vendor, and defensible if it is questioned later.
Nothing here assumes a complete estate or a rip and replace. Sources are added as adapters against a common contract, and the score states the coverage it was computed on.
Onboarding is four things, in order.
Build the asset model for the terminal, so a signal has something to attach to: berths, yard blocks, gates, cranes and the systems behind them. Connect what exists and state what does not. Ratify the policy: the weights, thresholds and windows that decide what outranks what, signed by a named person rather than shipped as a default. Then run it against real traffic and compare the queue to the judgment of the people who already do this work.
Where a feed does not exist, coverage is disclosed on the object instead of the gap being quietly absorbed into a number.
We walk one real convergence case from your terminal, and we name what is built, what is specified, and what is neither.