SUBJECT
Fields | Type | Description | Purpose | ||||||||||||||||
ID (subject identifier) | M | carriervisit | GRAMMAR | ||||||||||||||||
subject name | M | CarrierVisit | GRAMMAR | ||||||||||||||||
subject type | M | process | GRAMMAR | ||||||||||||||||
Also known as | O | vessel Visit; Visit, Truck visit, train visit, call, vessel voyage | TIC Description | ||||||||||||||||
Definition | M | CarrierVisit describes the process of a carrier (vessel, truck, barge, train) passing through a terminal (visiting the terminal) to load or unload cargo, or utilize other 3rd party-services (e.g. bunkering, garbage disposal, etc). |
| ||||||||||||||||
Further Detail | O | A Carrier visit CarrierVisit is unique given by the combination of the carrier id, the subject visited and the continuous period that the carrier stays in the facilities. This feature allows assigning a unique id per subject visited (port, terminal inland port, warehouse, etc).
Terminaloperations TerminalOperations
Each of the above processes can have several subprocesses. Further subprocesses of CarrierVisit could be, e.g. 3rdPartyService/CarrierServices. Further concepts of CarrierVisit could be, e.g. CarrierSafetyAccesible, CarrierReadyToWork, TerminalReadyToWork, Active, Working, Idle, start or end that describes different status, events or actions. For carrier type “vessel”: CarrierVisit starts at the time and location the vessel declares the voyage (sea passage) has ended or reached the restricted navigation area within the outer port limits as locally defined and declares readiness to proceed to the port. This is also knows as “End of Sea Passage” (EOSP). CarrierVisit ends at the time and location the the vessel declares the voyage has begun (sea passage) or left the restricted navigation area within the outer port limits as locally defined. This is also knows as “Start Of Sea Passage” SOSP. 2022.003 will only focus on the carrier type vessel The examples of 2022.003 release only include the vessel visit datamodel. | TIC Description | ||||||||||||||||
Required Information | M | id, carrier | TIC Description | ||||||||||||||||
SUBJECT |
| line, service, servicevisit, cargo, carrier, arrival, terminaloperations, departure, 3rdpartyservice/carrierservice |
| ||||||||||||||||
CONCEPT |
| id, name, lloysid, active, inactive, working, idle, start, end, carriersafetyaccesible, carrierreadytowork, terminalreadytowork |
| ||||||||||||||||
Related standards | O |
| TIC Description | ||||||||||||||||
Related TIC 4.0 definition | O | https://tic40.atlassian.net/l/c/9KWw5Qmp https://tic40.atlassian.net/l/c/xm72UHso https://tic40.atlassian.net/l/c/XgSJDCAZ https://tic40.atlassian.net/l/c/y12RUbG6 | |||||||||||||||||
Example | M | carriervisit.id = 20211210jacquessaadee carriervisit.start.time.scheduled = carriervisit.start.time.proposal = carriervisit.start.time.request = carriervisit.start.time.planning = carriervisit.start.time.estimated = carriervisit.start.time.actual = carrierisit.end.time.actual = | |||||||||||||||||
Example in the context of the grammar | M | Search tags | M | Version / Date | M | 2021.003 - 15/01/2022 | Internal TIC Version | M | Carrier Vsiit The CarrierVisit data model is very extensive as it includes several subprocess with many concepts. Below you can find an screenshot of the basic structure up to concept level breakdown. After it Further down you will find the complete data model.  CarrierVisit 2022.003 Data Model in Json format:
| Link to one or more operational processes | M |
| 2021210  for JSON data model please see below (click to expand) | ||||||
Link to one or more operational processes | M |
| |||||||||||||||||
Search tags | M | ||||||||||||||||||
Version / Date | M | 2021.003 - 15/01/2022 | |||||||||||||||||
Internal TIC Version | M | 2021210 |
Port Call Events & Timestamps
| Sugerencia |
|---|
INFO MODEL - With the defined processes, following events are considered for this publication - these are aligned as much as possible with mentioned references by IMO and DCSA, but include some specific ones for Terminal Operators and Ports for TIC 4.0. |
https://tic40.atlassian.net/l/cp/UhKTD7oe
Owner of the action and Proposal vs Request
The different pomt (Point of Mesearament in Time) are explained here https://tic40.atlassian.net/wiki/spaces/TIC40Definitions/pages/8618041/TIC4.0+Semantic#Where%2FWhen-in-the-timeline-%E2%80%9Cpomt%E2%80%9D%3A. During the Carriervisit process, it is very relevant who is the owner of the action as the owner will control the process and determine who makes the proposal, request and planning. For further details please seehttps://tic40.atlassian.net/wiki/spaces/TIC40Definitions/pages/8618041/TIC4.0+Semantic#Owner-of-the-action-and-Proposal-vs-Request
Subject (Process) | Owner (propose) | Partners (require) |
|---|---|---|
carriervisit | carrier | terminal, pilot service, towage service, mooring service, PA |
arrival | carrier | terminal, pilot service, towage service, mooring service, PA |
anchorage | carrier | PA |
drift | carrier | |
pilot | pilot service | carrier |
vesselatpilotboardingplace | carrier | pilot service |
firstimepilotonboard | pilot service | carrier |
towage | towage service | carrier, pilot service |
terminalberthreadyforarrival | terminal | carrier |
mooring | mooring service | carrier |
carriersafetyaccesible | carrier | terminal, PA |
carrierreadytowork | carrier | terminal |
terminalreadytowork | terminal | carrier |
terminaloperations | terminal | carrier |
3partyservice/carrierservices | 3rd party services | carrier |
terminalberthreadyfordeparture | terminal | carrier, mooring |
departure | carrier | terminal, pilot service, towage service, mooring service, PA |
Created by | Edited by | Review / Approve | Published |
Francisco Blanquer Jaraiz 2021-11-15 | Francisco Blanquer Jaraiz 2021-12-10 |
| |
|
|
|