On October 13, Kuehne+Nagel's weekly port operations bulletin put berth waiting at Singapore at 3 to 5 days with the yard near full, reported yard utilization above 90 percent at Busan and above 95 percent at Kaohsiung, and listed Vung Tau's yard at more than 100 percent of nominal capacity. At each of those ports, a vessel's arrival time and its berthing time were days apart, and the gap was the news.
Every schedule carries 2 clocks. The vessel ETA says when the ship will reach the pilot station. The berth ETA says when it will be alongside and a crane will touch the first container. They are routinely conflated, in schedules, in customer portals, and in planning systems, and the conflation is the source of most of the inland chaos that follows a congested week.
Why the 2 clocks drift apart
The vessel ETA is physics: distance over speed, corrected for weather and the odd deviation. It is predictable within hours over a 10 day voyage, and getting better every year as positional data improves.
The berth ETA is a queue. It depends on when the vessel ahead finishes, which depends on how many moves it has and how fast the cranes run, which depends on how full the yard is, which depends on how fast trucks and trains are pulling boxes out, which depends on the hinterland. None of those are the arriving ship's variables. A terminal at 70 percent yard utilization absorbs an early arrival. The same terminal at 95 percent turns it into 3 days at anchor, and the vessel ETA was correct all along.
The 2 clocks agree in a quiet terminal and diverge as utilization rises, and they diverge fastest exactly when the planning matters most.
Which clock to plan on
The terminal should plan on the berth clock, because it owns it. The berth ETA is a function of the terminal's own state: berth occupancy, crane allocation, yard density, gate throughput. A terminal that computes it from its own data and publishes it, rather than echoing the carrier's vessel ETA, gives everyone downstream a number they can act on. Trucking firms stop sending drivers to wait for containers that will not be discharged for 2 days. Rail operators stop holding wagons. Shippers stop promising delivery dates based on a ship that is anchored outside the port.
The carrier should plan on the berth clock too, in the opposite direction. A vessel told its berth is 3 days away can slow down and arrive on time, burning less fuel, rather than steaming at full speed to join a queue. In the operations we have seen, that single change, matching speed to the berth slot rather than to a schedule written months earlier, is worth more fuel than most route optimizations.
The planning consequence
A system that stores 1 ETA per vessel is storing the wrong thing. It needs 2 fields, 2 sources, and a measured gap between them, by terminal and by week. The gap is the leading indicator of congestion: it opens before the delays show up in delivery data, and it closes before the news says the problem is over. When the gap is small, the vessel clock is good enough. When it is large, nothing downstream should be planned on anything but the berth clock, and the terminal is the only party that can supply it.