INDUSTRY FIELD GUIDE
Ocean and coastal freight arrival data for AI review
A ship’s estimated arrival is different from the berth time a terminal requests.
NAICS 483111 · Deep Sea Freight Transportation
NAICS 483113 · Coastal and Great Lakes Freight Transportation
A ship’s estimated arrival is different from the berth time a terminal requests. A model that treats both as actual arrivals can turn a schedule revision into an incorrect delay report. IMO’s just-in-time arrival materials describe port-call information and the events different parties exchange. A vessel operator can use fictional calls to test revision handling. IMO just-in-time arrivals · IMO port-call guide
Invent a voyage with two berth windows, a time the vessel estimates, and a later actual event. Include who issued each value and the time zone. Give a second voyage an unresolved difference between two sources. Ask the assistant to identify the current plan and separate observed facts from forecasts. A buyer can evaluate whether the model cites the correct source instead of taking the latest number automatically.
Keep commercial cargo details, vessel identifiers, active schedules, operational communications, and facility layouts outside the exercise. Use no dataset for navigation or berth instructions.
Describe a port-call timing sample
Original Fiund exercise
Vessel estimates, terminal requests and actual arrival events keep different meanings
An original port-call fixture uses fictional voyages and a single stated UTC basis. It contains no vessel identity, active schedule, cargo, berth instruction or navigation action.
| Record | Source | What it records |
|---|---|---|
| PCO1 | Call A planned records | Vessel estimate ETA 10:00 UTC. Terminal-requested berth window revised from W1 to W2; current requested time 10:30 UTC, revision explicitly confirmed by terminal. |
| PCO2 | Call A actual event | Original observed arrival event states 10:20 UTC. It does not state actual berth time or acceptance of the requested window. |
| PCO3 | Call B conflict | Vessel estimate 12:00 UTC and terminal request 12:30 UTC. No actual event or reconciled plan confirmation supplied. |
Question for the model
Which A values are forecasts, requests and observations, and can B's latest time be reported as actual arrival?
Show the reference answer and checks
PCO1's 10:00 is A's vessel estimate and 10:30 the terminal's current requested time after revision. PCO2 separately observes arrival at 10:20 without an actual berth event. These values describe different events and authorities. PCO3 supplies only an estimate and request for B, so neither is actual arrival and their difference remains a planning distinction to clarify. Do not select the latest number as a universal port-call truth or infer a delay basis not stated.
- Treating a requested berth time as an observed vessel arrival.
- Choosing the latest source indiscriminately or comparing different event types as if identical.
Fields to preserve
- Call and issuing role
- Defines authority.
- Estimate/request/actual event type
- Preserves meaning.
- UTC time, revision and missing confirmation
- Supports the retrospective summary.
Test another case
Give B's terminal request in an unspecified local time. Require time-basis clarification in addition to preserving event type.
Use original offline records. Exclude schedules, routes and communications; no output directs navigation or berth operations.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.