Maritime transport chain and port roles · Lesson 2
Vessel-call sequence and times
7 min read
Lesson objectives
Construct a dated vessel-call event chain and distinguish estimated, confirmed and completed milestones.
Reading tools
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A vessel-call plan changes as a forecast becomes an observed event. Estimated time of arrival, or ETA, is a revisable forecast; it is not evidence that a ship has arrived. Arrival at anchorage is distinct from berthing. Berthing is followed by the start and completion of cargo handling and then departure. If someone says the ship was six hours late, ask which two events they compared. Was the difference between ETA and arrival, arrival and berth, or berth and handling completion? Each interval has a different possible cause and response. Port performance reporting distinguishes a ship's waiting interval from its whole time in port. Combining the two makes a dashboard misleading.
Keep an event log with a forecast time, a confirmed time from a named source and the time the record was updated. Suppose the agent initially gives an ETA of 06:00 and revises it at 04:00 to 09:00. Retain both versions and the revision time. Deleting the old forecast erases the basis of decisions already made. Name the source of each fact: carrier or agent for voyage estimates, the berth coordinator for a confirmed berth window, and the terminal for handling start and end. An information source is not necessarily the authority granting an operational approval. A terminal can report handling status while another body makes a berth-allocation decision.
For a simple critical-path view, ask which delayed prerequisite would actually move departure. The ship may be alongside while yard cargo is unavailable; cargo may be ready while departure services or documents are incomplete. Draw dependencies instead of adding all delays. If crane work is late by two hours and cargo readiness is late by three, the total effect is not automatically five hours. Were the delays parallel or sequential? Record each explanation's effect on the final milestone and update the customer promise only when the needed confirmation arrives. An administrative event log never substitutes for navigational instruction or a safety decision.
A timeline needs more than subtracting an earlier clock reading from a later one. Record the date, time zone and source for each timestamp. A ship arriving at 23:30 and berthing at 01:00 the next day waited an hour and a half, not a negative interval. If the agent message uses UTC but the terminal log uses local time, convert both to one basis while retaining the originals. This lets customer and operator reproduce the calculation from versioned evidence. If berth time is absent, waiting cannot yet be calculated; a planned window is a forecast, not a substitute observed event.
Two accurate timestamps may describe different events. The agent says a message arrived at nine, while the operator records entry into the observation area at nine ten. Keep the event description beside the time. Select the timestamp matching the indicator definition and explain why the other is excluded from that calculation. A separate recording-time field is useful when staff enter an event late. If berthing occurred at ten and was entered at ten thirty, calculations use the evidenced event time. This distinction also permits measurement of information delay. You now have an operational indicator and an information-quality indicator, each pointing to a different improvement action.
Lesson summary
This lesson shows how to construct a dated vessel-call event chain and distinguish estimated, confirmed and completed milestones.