SUBJECT
Fields | Type | Description | Purpose |
ID (subject identifier) | M | closingatdeparture | GRAMMAR |
subject name | M | ClosingAtDeparture | GRAMMAR |
subject type | M | process | GRAMMAR |
Also known as | O | boom-up, after operations | TIC Description |
Definition | M | ClosingAtDeparture is a process of TerminalOperations by which a subject (usually a Terminal) facilitates the Carrier, that belongs to a CarrierVisit process, leaving the terminal after ends the CargoOperations and includes all the subject activities necesary to ends the Terminals operations related to the CarrierVisit. |
|
Further Detail | O | ClosingAtDeparture is consider “active” if the resources are in place ready to perform the activity (driving, booming, hoisting, standby). The ClosingAtDeparture “start” will define the first time the process is active and the “end” the last time during the CarrierVisit. During the ClosingAtDeparture the process could be inactive because one CHE iniciates and ends the ClosingAtDeparture process but others are still active in the CargoOperations. carriervisit.terminaloperations.closingatdeparture is a subprocess of TerminalOperations process: 
 Preparation at Arrival and Closing at Departure belongs to Terminal Operations: Preparation and closing are necessary to execute the terminal operation, therefore they are included within terminal operations. Preparation and closing could be active before/after as they are preparatory/finalizing works. It is a preparatory/finalizing work before/after the terminal operations process start/ends and can be considered “active”. So preparation will always “start” before the terminal operations “start” and the closing will always “end” after terminal operations “end” because are activities that needs to be done before and after the terminal operations. Carrier Visit vs CHE Preparation at Arrival and Closing at Departure considerations:  Several CHE and lashing processes may participate at the same time in a Terminal Operations. The Carrier Visit Preparation at Arrival or Closing at Departure always includes any kind of lashing or che.cycle activity (usually without cargo cycle.moves) moving hashcovers, twistlock boxs, boom-up/boom-down, drive) or some times just a cycle.move with cargo but with a lot of idle time waiting for the arrival. Terminal Operations, Cargo Operations, Preparation at Arrival and Closing at Departure are always linked to a CHE or Lashing process. In the example Preparation at Arrival will start with the start of the che.@1.cycle necesary to do the boom-up, with a lot of idle time and until the end with the first cycle.move with cargo. The Closing at Departure will start with the end of the che.@1.cycle of the last cargo move, and will contain a che.@1.cycle without cargo and some lashing activies. The cargo operations will start with the start of the che.@3.cycle with the first cargo, but later the che.@3 will jump to another Carrier Visit Cargo Operation. Considerations per Carrier type: TO REVIEW Vessel:
Truck:
Rail:
| TIC Description |
Required Information | M | CarrierVisit id | TIC Description |
SUBJECT |
| carriervisit; preparationatarrival; cargooperations; lashing; closingatdeparture |
|
CONCEPT |
| id, name, active, inactive, idle, working, start, end |
|
Related standards | O |
| TIC Description |
Related TIC 4.0 definition | O | https://tic40.atlassian.net/l/c/3RUk3VuDhttps://tic40.atlassian.net/l/c/H6AHQTgPhttps://tic40.atlassian.net/l/c/V7pHyb1Shttps://tic40.atlassian.net/l/c/2dVQBRjY https://tic40.atlassian.net/l/c/T5XGh24c Cargo Operations Lashing | |
Example | M | carriervisit.terminaloperations.preparationatarrival.start.time.output.actual = visit.terminaloperations.preparationatarrival..end.time.output.actual = | |
Example in the context of the grammar | M |  | |
Link to one or more operational processes | M |
| |
Search tags | M | Operations; cargo operations; vessel operations; truck operations; train operations; cargo operations; port operations; terminal activities; load; discharge; unload; loading; discharging. | |
Version / Date | M | 2022.005 - 01/10/2022 | |
Internal TIC Version | M | 20220622 |
Created by | Edited by | Review / Approve | Published |
Francisco Blanquer Jaraiz 2021-11-157 |
|
|
|
|
|
|