...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
SUBJECT
Fields | Type | Description | Purpose |
ID ( |
subject identifier) | M |
gearboxes | GRAMMAR |
subject name | M |
Gearboxes | GRAMMAR |
subject type | M |
process | GRAMMAR |
Also known as | O |
Gearboxes, twistlock bins | TIC Description |
Definition | M |
Event when a carrier (vessel, barge, rail, truck) reports First time readiness for cargo operations as reported by the carrier to the terminal according to local regulations
Terminal Operations Gearboxes is a sub-process of TerminalOperations by which a subject (usually the terminal’s personnel) performs the operation to discharge/load gearboxes from/to the carrier. |
|
Further Detail | O |
CarrierFirstTimeReadyToWork is a sub-concept of the subject (process) CarrierVisit.
Vessel:
Event when the vessel reports First time readiness for cargo operations as reported by the vessel to the terminal according to local regulations
Truck:
Event when the truck is First Time ready to be unloaded/loaded with cargo, i.e. when the truck is in the transfer area and confirms that it can be loaded/unloaded.
Rail:
Event when the train is First Time ready to be loaded or unloaded. This is determined either manually (output) (e.g. “walk the train” to achieve readiness for cargo operations).Terminal Operations gearboxes is considered “active” if the resources are in place ready to perform the activity (discharge or load the gearboxes) The “start” will define the first time the process is active and the end the last time. During the terminal operations the process could be inactive because the resources are not in place (i.e. suspension of operations because of high wind). tos.carriervisit.terminaloperations.gearboxes is a subprocess of TerminalOperations process:
TerminalOperations Gearboxes vs CargoOperations: Gearboxes usually start before CargoOperations to enable the start of CargoOperations. CargoOperations and gearboxes can work in parallel, after the first gearboxes are discharged (working in parallel in multiple bays). Vessel:
Truck (as external carrier): Not Applicable Rail: Not Applicable | TIC Description | ||
Required Information | M |
CarrierVisit | TIC Description |
SUBJECT |
|
carriervisit, terminaloperations |
|
OBSERVED PROPERTY
#status; #duration; #timer; #totaltimer; #startevent; #startcounter; #endevent; #endcounter
Value
TRUE; FALSE;
CONCEPT |
|
#input;#internal_in ; #internal_out ;#output
#planning; #estimated; #actual; #performed
id, name, active, inactive, working, start, end, move |
|
Related standards | O |
Example
M
carriervisit.carrierfirsttimereadytowork: TRUE = The carrier is ready to be operated or for any other cargo operations to be carried out.
TIC Description
| TIC Description |
Related TIC 4.0 definition | O |
TIC Description
https://tic40.atlassian.net/l/c/3RUk3VuD https://tic40.atlassian.net/wiki/pages/resumedraft.action?draftId=1000407869 TerminalOperations Departure Inbound Check-In Dwell CargoVisit Check-out Outbound Lashing | |||
Example | M | carriervisit.id = MLT1974 tos.@.carriervisit.@.terminaloperations.@.gearboxes.@.start.time.output.actual = tos.@.carriervisit.@.terminaloperations.@.gearboxes.@.end.time.output.actual = | |
Example in the context of the grammar | M |
 | ||
Link to one or more operational processes | M |
|
TIC Description
Search tags | M |
arrival, carrier, carriervisit, departure, inbound, outbound, cargooperations, anchorage, drift, pilot, towage, mooring, portgate, terminalgate, pregate | |
Version / Date | M |
2022.006 - 1/12/2022 | |
Internal TIC Version | M |
20230313 |
Technical
M = Mandatory
O = Optional
...
| View file | ||
|---|---|---|
|
Created by | Edited by | Review / Approve | Published |
RBS EMEA 2022-10-20 | 20221121 |
|
|
2022-10-20 |
|
|
|