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 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).
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 | 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. Further down you will find the complete data model. 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 |
...
# | TIC 4.0 | Event Timestamp | Phase | Owner | Description | TIC 4.0 = DCSA |
1 | carriervisit.arrival.start | End of Sea Passage, Arrival (EOSP) | Arrival | Carrier | The date/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. | carriervisit.arrival.start.schedule = XXX carriervisit.arrival.start.proposal = XXX carriervisit.arrival.start.request = XXX carriervisit.arrival.start.planning = XXX carriervisit.arrival.start.estimated = XXX carriervisit.arrival.start.actual = EOSP |
2 | carriervisit.arrival.pilot.vesselatpilotboardingplace | Time of Arrival, Pilot | Arrival | Carrier | The date/time a vessel estimates it will arrive at Pilot Boarding Place: whenever ETA PBP is communicated, starting after PTA Berth is received. | carriervisit.arrivalvesselatpilotboardingplace.schedule = XXX carriervisit.arrival.vesselatpilotboardingplace.proposal = ETA PBP carriervisit.arrival.vesselatpilotboardingplace.request = XXX carriervisit.arrival.vesselatpilotboardingplace.planning = XXX carriervisit.arrival.vesselatpilotboardingplace.estimated = XXX carriervisit.arrival.vesselatpilotboardingplace.actual = ATA PBP |
3 | carriervisit.arrival.pilot.firstimepilotonboard | Start Pilotage service Arrival | Arrival | Port, Pilot | The date/time a pilotage service provider confirms to attend to the vessel: whenever PTS is communicated. | carriervisit.arrival.pilotage.firstimepilotonboard.schedule = XXX carriervisit.arrival.pilotage.firstimepilotonboard.proposal = XXX carriervisit.arrival.pilotage.firstimepilotonboard.request = XXX carriervisit.arrival.pilotage.firstimepilotonboard.planning = XXX carriervisit.arrival.pilotage.firstimepilotonboard.estimated = XXX carriervisit.arrival.pilotage.firstimepilotonboard.actual = ATS Pilotage |
4 | carriervisit.arrival.pilotage.lasttimepilotonboard | End Pilotage service Arrival | Arrival | Port, Pilots | The date/time a pilotage service provider confirms to attend to the vessel: whenever ETC is communicated. | carriervisit.arrival.pilotage.lasttimepilotonboard.schedule = XXX carriervisit.arrival.pilotage.lasttimepilotonboard.proposal = XXX carriervisit.arrival.pilotage.lasttimepilotonboard.request = XXX carriervisit.arrival.pilotage.lasttimepilotonboard.planning = XXX carriervisit.arrival.pilotage.lasttimepilotonboard.estimated = XXX carriervisit.arrival.pilotage.lasttimepilotonboard.actual = XXX |
5 | carriervisit.arrival.towage.firsttimefirstlinestart | Start Towage service Arrival | Arrival | Port, Tugs | The date/time a towage service provider confirms to attend to the vessel: whenever PTS is communicated. | carriervisit.arrival.towage.firsttimefirstlinestart.schedule = XXX carriervisit.arrival.towage.firsttimefirstlinestart.proposal = XXX carriervisit.arrival.towage.firsttimefirstlinestart.request = XXX carriervisit.arrival.towage.firsttimefirstlinestart.planning = XXX carriervisit.arrival.towage.firsttimefirstlinestart.estimated = XXX carriervisit.arrival.towage.firsttimefirstlinestart.actual = ATS Towage |
6 | carriervisit.arrival.towage.lasttimelastline | Planned End Towage service Arrival | Arrival | Port, Tugs | The date/time a towage service provider confirms to attend to the vessel: whenever ETC is communicated. | carriervisit.arrival.towage.lasttimelastline.schedule = XXX carriervisit.arrival.towage.lasttimelastline.proposal = XXX carriervisit.arrival.towage.lasttimelastline.request = XXX carriervisit.arrival.towage.lasttimelastline.planning = XXX carriervisit.arrival.towage.lasttimelastline.estimated = XXX carriervisit.arrival.towage.lasttimelastline.actual = ATC Towage |
7 | carriervisit.arrival.mooring.start | Start Mooring service Arrival | Arrival | Port, Linemen | The date/time a mooring service provider confirms to attend to the vessel: whenever PTS is communicated. This is related to first line event for mooring. | carriervisit.arrival.mooring.start.schedule = XXX carriervisit.arrival.mooring.start.proposal = XXX carriervisit.arrival.mooring.start.request = XXX carriervisit.arrival.mooring.start.planning = XXX carriervisit.arrival.mooring.start.estimated = XXX carriervisit.arrival.mooring.start.actual = XXX |
8 | arriervisit.arrival.mooring.firstline | Time of Arrival at Berth First line mooring | Arrival | Carrier | The date/time a vessel estimates it will arrive at berth: whenever ETA Berth is communicated, starting at departure of the previous berth. | carriervisit.arrival.mooring.firstline.schedule = XXX carriervisit.arrival.mooring.firstline.proposal = ETA Berth carriervisit.arrival.mooring.firstline.request = RTA Berth carriervisit.arrival.mooring.firstline.planning = PTA Berth carriervisit.arrival.mooring.firstline.estimated = XXX carriervisit.arrival.mooring.firstline.actual = ATA Berth |
9 | carriervisit.arrival.mooring.lastline | End Mooring service Arrival | Arrival | Port, Linemen | The date/time a mooring service provider confirms to attend to the vessel: whenever ETC is communicated by linemen. This is related to all fast event for mooring. | carriervisit.arrival.mooring.endlastline.schedule = XXX carriervisit.arrival.mooring.endlastline.proposal = XXX carriervisit.arrival.mooring.endlastline.request = XXX carriervisit.arrival.mooring.endlastline.planning = XXX carriervisit.arrival.mooring.endlastline.estimated = XXX carriervisit.arrival.mooring.endenlastlined.actual = AT All Fast |
10 | carriervisit.firsttimecarriersafetyaccesible | Carrier safely accessible | Arrival | Carrier | Gangway down and safety net available for access enabled to vessel: whenever safe access to vessel is communicated by vessel. | carriervisit.firsttimecarriersafetyaccesible.schedule = XXX carriervisit.firsttimecarriersafetyaccesible.proposal = XXX carriervisit.firsttimecarriersafetyaccesible.request = XXX carriervisit.firsttimecarriersafetyaccesible.planning = XXX carriervisit.firsttimecarriersafetyaccesible.estimated = XXX carriervisit.firsttimecarriersafetyaccesible.actual = Vessel Readiness for Cargo OPS? |
11 | carriervisit.firsttimecarrierreadytowork | Carrier ready for Cargo OPS | Arrival | Carrier | Readiness for cargo operations as reported by the vessel to the vessel according to local regulations: whenever vessel readiness for cargo ops is communicated by vessel. | carriervisit.firsttimecarriercarrierreadytowork.schedule = XXX carriervisit.firsttimecarriercarrierreadytowork.proposal = XXX carriervisit.firsttimecarriercarrierreadytowork.request = XXX carriervisit.firsttimecarriercarrierreadytowork.planning = XXX carriervisit.firsttimecarriercarrierreadytowork.estimated = XXX carriervisit.firsttimecarriercarrierreadytowork.actual = Vessel Readiness for Cargo OPS? |
12 | carriervisit.firsttimeterminalreadytowork | Terminal ready for Cargo OPS | Arrival | Terminal | Readiness for cargo operations as reported by the terminal to the terminal according to local regulations: whenever vessel readiness for cargo ops is communicated by terminal. | carriervisit.firsttimeterminalreadytowork.schedule = XXX carriervisit.firsttimeterminalreadytowork.proposal = XXX carriervisit.firsttimeterminalreadytowork.request = XXX carriervisit.firsttimeterminalreadytowork.planning = XXX carriervisit.firsttimeterminalreadytowork.estimated = XXX carriervisit.firsttimeterminalreadytowork.actual = XXX |
13 | carriervisit.terminaloperations.cargooperations.start | Start of Cargo OPS, first container lift | Cargo OPS | Terminal | The date/time a terminal operator estimates cargo operations will start/fist commercial lift: whenever ETS is communicated. | carriervisit.terminaloperations.cargooperations.start.schedule = XXX carriervisit.terminaloperations.cargooperations.start.proposal = ETS Cargo OPS carriervisit.terminaloperations.cargooperations.start.request = RTS Cargo OPS carriervisit.terminaloperations.cargooperations.start.planning = PTS Cargo OPS carriervisit.terminaloperations.cargooperations.start.actual = ATS Cargo OPS |
14 | carriervisit.terminaloperations.cargooperations.end | End of Cargo OPS, last container lift | Cargo OPS | Terminal | The date/time a terminal operator estimates cargo operations will be completed/last commercial lift: whenever ETC is communicated. | carriervisit.terminaloperations.cargooperations.end.schedule = XXX carriervisit.terminaloperations.cargooperations.end.proposal = ETC Cargo OPS carriervisit.terminaloperations.cargooperations.end.request = RTC Cargo OPS carriervisit.terminaloperations.cargooperations.end.planning = PTC Cargo OPS carriervisit.terminaloperations.cargooperations.end.actual = ATC Cargo OPS |
15 | carriervisit.terminaloperations.lashing.end | End of lashing, | Cargo OPS | Terminal | carriervisit.terminaloperations.lashing.end.schedule = XXX carriervisit.terminaloperations.lashing.end.proposal = XXX carriervisit.terminaloperations.lashing.end.request = XXX carriervisit.terminaloperations.lashing.end.planning = XXX carriervisit.terminaloperations.lashing.end.actual = ATC Lashing? | |
16 | carriervisit.firsttimecarrierreadyfordeparture | Vessel Ready to Sail | Cargo OPS | Carrier | Vessel readiness for safe departure as reported by the vessel | carriervisit.carriervisit.firsttimecarrierreadyfordeparture.schedule = XXX carriervisit.carriervisit.firsttimecarrierreadyfordeparture.proposal = XXX carriervisit.carriervisit.firsttimecarrierreadyfordeparture.request = XXX carriervisit.carriervisit.firsttimecarrierreadyfordeparture.planning = XXX carriervisit.carriervisit.firsttimecarrierreadyfordeparture.actual = Vessel Ready to Sail |
17 | carriervisit.firsttimeterminalberthreadyfordeparture | Terminal ready for Vessel departure | Departure | Terminal | After cargo operations terminal declares carry is free for departure. In case of vessel, cranes interference out of berth and resources out vessel. | carriervisit.carriervisit.firsttimeterminalberthreadyfordeparture.schedule = XXX carriervisit.carriervisit.firsttimeterminalberthreadyfordeparture.proposal = XXX carriervisit.carriervisit.firsttimeterminalberthreadyfordeparture.request = XXX carriervisit.carriervisit.firsttimeterminalberthreadyfordeparture.planning = XXX carriervisit.carriervisit.firsttimeterminalberthreadyfordeparture.actual = Terminal ready for Vessel Departure |
18 | carriervisit.departure.mooring.firstline | Start Mooring service Departure (first line) Time of Departure, Berth | Departure | Port, Linemen | The date/time a mooring service provider confirms to attend the vessel: whenever PTS is communicated (first line) The date/time when a vessel estimates it will depart from berth: whenever ETD is communicated. | carriervisit.departure.mooring.firstline.schedule = XXX carriervisit.departure.mooring.firstline.proposal = ETD Berth carriervisit.departure.mooring.firstline.request = RTD Berth carriervisit.departure.mooring.firstline.planning = PTD Berth carriervisit.departure.mooring.firstline.actual = ATD |
19 | carriervisit.departure.mooring.lastline | End Mooring service Departure (last line) | Departure | Port, Linemen | The date/time a mooring service provider confirms to finalize the mooring: whenever ETC is communicated and matching with ‘Last Line’ (OFF) event. | carriervisit.departure.mooring.lastline.schedule = XXX carriervisit.departure.mooring.lastline.proposal = XXX carriervisit.departure.mooring.lastline.request = XXX carriervisit.departure.mooring.lastline.planning = XXX carriervisit.departure.mooring.lastline.actual = XXX |
20 | carriervisit.departure.towage.firsttimefirstlinestart | Start Towage service Departure | Departure | Port, Tugs | The date/time a towage service provider confirms to attend the vessel: whenever PTS is communicated. | carriervisit.departure.towage.firsttimefirstlinestart.schedule = XXX carriervisit.departure.towage.firsttimefirstlinestart.proposal = XXX carriervisit.departure..towage.firsttimefirstlinestart.request = XXX carriervisit.departure..towage.firsttimefirstlinestart.planning = XXX carriervisit.departure..towage.firsttimefirstlinestart.actual = ATS Towage |
21 | carriervisit.departure.towage.lasttimelastline | Planned End Towage service Departure | Departure | Port, Tugs | The date/time a towage service provider confirms to finalize towage: whenever ETC is communicated. | carriervisit.departure.towage.lasttimelastline.schedule = XXX carriervisit.departure.towage.lasttimelastline.proposal = XXX carriervisit.departure..towage.lasttimelastline.request = XXX carriervisit.departure..towage.lasttimelastline.planning = XXX carriervisit.departure..towage.lasttimelastline.actual = ATC Towage |
22 | carriervisit.departure.pilotage.firstimepilotonboard | Planned Start Pilotage service Departure | Departure | Port, Pilotage | The date/time a pilotage service provider confirms to attend the vessel: whenever PTS is communicated. | carriervisit.departure.pilotage.firstimepilotonboard.schedule = XXX carriervisit.departure.pilotage.firstimepilotonboard.proposal = XXX carriervisit.departure.pilotage.firstimepilotonboard.request = XXX carriervisit.departure.pilotage.firstimepilotonboard.planning = XXX carriervisit.departure.pilotage.firstimepilotonboard.actual = ATS Pilotage |
23 | carriervisit.departure.pilotage.lasttimepilotonboard | Planned End Pilotage service Departure | Departure | Port, Pilotage | The date/time a pilotage service provider confirms to attend the vessel: whenever ETC is communicated and matching with ‘Pilot Off’ (PD) event. | carriervisit.departure.pilotage.lasttimepilotonboard.schedule = XXX carriervisit.departure.pilotage.lasttimepilotonboard.proposal = XXX carriervisit.departure.pilotage.lasttimepilotonboard.request = XXX carriervisit.departure.pilotage.lasttimepilotonboard.planning = XXX carriervisit.departure.pilotage.lasttimepilotonboard.actual = ATC Pilotage |
24 | carriervisit.arrival.end | Start Of Sea Passage, Departure | Departure | Carrier | The time and the location when the vessel declares the voyage has begun (sea passage) or left the restricted navigation area within the outer port limits as locally defined: when the captain declares SOSP. Vessel position/coordinates required. | carriervisit.arrival.end.schedule = XXX carriervisit.arrival.end.proposal = XXX carriervisit.arrival.end.request = XXX carriervisit.arrival.end.planning = XXX carriervisit.arrival.end.actual = SOSP |
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
...