Arrival

Fields

Type

Description

Purpose

ID (subject identifier)

M

arrival

GRAMMAR

subject name

M

Arrival

GRAMMAR

subject type

M

process

GRAMMAR

Also known as

O

vessel Visit arrival; Visit arrival, Truck visit arrival, train visit arrival, vessel call arrival

TIC Description

Definition

M

“Arrival" is the process by which a carrier is physically approaching its destination (terminal), in preparation for the terminal operations activity or to receive other 3rd party services provided at the terminal site .

Further Detail

O

Arrival is a sub process of CarrierVisit process.

Open

The Arrival “start” event occurs when a carrier enters inside the boundary of the Port activity zone. Usually, this boundary is a physical border (port gate, barrier or geo zone) but may also be located outside a physical border (e.g., a pregate control point).

In case the physical port boundaries or process boundaries do not exist, the terminal borders (e.g. gate) act as the relevant boundary (as the terminal is always part of the port).

Arrival “end” event occurs when a carrier is “first time ready to work”: at the transfer area and just ready to load/unload cargo or conduct services (see definition “firsttimecarrierreadytowork”).

Open

Per carrier type:

The arrival.start always take place at the “border” of the port and ends when the carrier is ready for the cargo operations or 3rd party services, but this may happen in different places depending of the carrier type.

Vessel:

• Arrival.start is at End of Sea Passage (EOSP)

• Arrival.end is when firsttimecarrierreadytowork occurs: mooring last line, safety accessible (gangway down) and clearance to initiate cargo operations with the terminal or 3rd party service on the vessel.

Truck:

• Arrival.start is usually at the port gate or pregate (whichever comes first based on the terminal characteristics). If no port gates/pregates are present but a general port border or barrier exists, then Arrival.start occurs when the carrier passes through the port border/barrier (geofence or access control).
  If no port boundaries exist at all, Arrival.start will be when the truck passes the terminal pregate (OCR) or gate (whichever comes first).

• Arrival.end is when the truck is ready to be loaded or unloaded with the cargo: i.e. when the truck is in the transfer area and confirms that it can be loaded/unloaded.
  If terminals do not register the “output” of this event (driver confirmation, sensor detection, geofence), then an “ioutput” feedback (assumption) could be considered (e.g. 2 minutes after passing the gate or XX minutes after passing the gate - depending on the distance to be driven).

Rail:

• Arrival.start is when the train passes the gate or boundary of the port limits. If no such gate or boundary exists, it will be in the moment the train starts to enter the border of the terminal (e.g. the OCR gate).

• Arrival.end is when the train is ready to be loaded or unloaded. This is determined either manually (output) (e.g. “walk the train” to achieve readiness for cargo operations) or automatically assuming the train is ready after a long enough time to prepare the train (ioutput).

Open

TIC Description

Required Information

M

CarrierVisit

TIC Description

SUBJECT

carriervisit, anchorage, drift, pilot, towage, mooring, portgate, terminalgate (& pregate).

CONCEPT

id, name, active, inactive, idle, working, start, end

Related standards

O

 ISO 6346

TIC Description

Related TIC 4.0 definition

O

https://tic40.atlassian.net/l/c/3RUk3VuD Arrival TerminalOperations Departure Inbound Check-In Dwell CargoVisit Check-out Outbound

Example

M

carriervisit.id = MLT1974

carriervisit.start.time.output.actual =2022-04-26T10:00:00.000Z

carriervisit.arrival.start.time.output.actual =2022-04-26T10:00:00.000Z

carriervisit.terminaloperations.start.time.output.actual =2022-04-26T10:30:00.000Z

carrierisit.arrival.end.time.output.actual =2022-04-26T11:00:00.000Z

cargovisit.inbound.time.output.actual =2022-04-26T11:00:00.000Z

carriervisit.cargooperations.start.time.output.actual =2022-04-26T11:10:00.000Z

carriervisit.cargooperations.end.time.output.actual =2022-04-26T18:00:00.000Z

cargovisit.outbound.time.output.actual =2022-04-26T18:30:00.000Z

carriervisit.departure.start.time.output.actual =2022-04-26T18:30:00.000Z

carriervisit.terminaloperations.end.time.output.actual =2022-04-26T18:40:00.000Z

carriervisit.departure.end.time.output.actual =2022-04-26T19:00:00.000Z

carriervisit.end.time.output.actual =2022-04-26T19:00:00.000Z

Example in the context of the grammar

M

see below the complete JSON data model

Link to one or more operational processes

M

Search tags

M

arrival, carrier, carriervisit, departure, inbound, outbound, cargooperations, anchorage, drift, pilot, towage, mooring, portgate, terminalgate, pregate

Version / Date

M

2022.004 - 1/05/2022

Internal TIC Version

M

20220426