Fields | Type | Description | Purpose |
ID (subject identifier) | M | departure | GRAMMAR |
subject name | M | Departure | GRAMMAR |
subject type | M | process | GRAMMAR |
Also known as | O | Vessel departure; gate out process | TIC Description |
Definition | M | Departure is the process by which a carrier is physically leaving the terminal, as the terminal operations or third party services are completed. | |
Further Detail | O | Departure is a subprocess of CarrierVisit process. Departure “start” event occurs when a carrier has finished its cargooperations or 3rd party services and it is “first time ready to departure” (see definition “firsttimecarrierreadyfordeparture”). Departure “end” event occurs when a carrier leaves the boundary of the Port activity. Usually this boundary is a physical border (port gate, barrier or geozone). In case the physical port boundaries or process boundaries do not exist, the terminal borders (gate) act as the relevant boundary (as the terminal is always part of the port). Per carrier type: Vessel: Departure.start is when firsttimecarrierreadyfordeparture: when the captain of the vessel iniciate the departure procedure (gangway up, mooring, pilot, etc). Departure.end is at Start of Sea Passage (SOSP)
Truck: Departure.start once the truck is loaded/unloaded and no more loading/unloading operations have to be done (in that transfer area or another) and the truck starts the leaving procedure: secure the cargo, leaves the transfer area, go to the pregate or gate and exit the port.
If it is not register the “output” of this event (driver confirmation, sensor detection, geofence), then an “ioutput” feedback (assumption) could be considered (in the moment the CHE or TOS confirms the last job is done). Departure.end is usually at the port gate or terminal gate (whatever comes last). If no port gates are present but a general port border or barrier exists, then Departure.end occurs when the carrier passes through the port border/barrier (geofence or access control).
If no port boundaries exist at all, Departure.end will be when the truck passes the terminal pregate (OCR) or gate (whatever comes last).
Rail: Departure.start is when the train is already loaded or unloaded the 3rd party services are finished and the operations to prepare the departure starts (brakes connection, machine connection or join/split wagons). This is determined either manually as an ouput data (e.g. “walk the train” to achieve readiness to departure) or if no data exists it could be considered as a feedback (ioutput) when cargo operations ends or after a time, assuming that the operations to departure start after some time the cargo operations were finished. Departure.end 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 ends to exit the border of the terminal (e.g. the OCR gate).
| TIC Description |
Required Information | M | id, input, output | TIC Description |
SUBJECT | | line, service, servcevisit, cargo, carrier, carriervisit | |
CONCEPT | | id, input, output, start, end, announcement, location | |
Related standards | O | ISO 6346 | TIC Description |
Related TIC 4.0 definition | O | https://tic40.atlassian.net/l/c/3RUk3VuD Arrival (Review) TerminalOperations (Review) Departure (Review) | |
Example | M | carriervisit.start.time.output.actual =2021-11-15T15:14:01.352Z carrierisit.end.time.output.actual =2021-11-16T15:14:01.352Z | |
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 | Please add | |
Version / Date | M | 2021.003 - 15/01/2022 | |
Internal TIC Version | M | 2021115 | |