TIC 4.0

Ir al final de los metadatos
Ir al inicio de los metadatos

Estás viendo una versión antigua de esta página. Ve a la versión actual.

Comparar con el actual Ver el historial de la página

« Anterior Versión 2 Siguiente »

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:

  • carriervisit.terminaloperations.closingatdeparture “start” event is when any of the CHE that belongs to the Terminal ends CargoOperations (last che.cycle.move of the specific carriervisit) and iniciate the process to get the terminalberthreadyfordeparture allowing the carriervisit departure process take place.

  • carriervisit.terminaloperations.closingatdeparture “end” event is when the terminal is “firsttimeterminalberthreadyfordeparture” and the CHE equipment that participates in the carrier visit is OFF or active in another che.cycle that doesnt corresponds to the specific CarrierVisit.

Preparation at arrival and closing at departure: 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.

Considerations per Carrier type:

Vessel:

  • carriervisit.terminaloperations.closingatdeparture.start is when at least one of the terminal CHE deployed for performing the carriervisit.terminaloperations ends the cargooperations with the the aim of get the “TerminalBerthReadyForDeparture” or to start the another che.cycle that doesnt corresponds to the specific carriervisit.

  • carriervisit.terminaloperations.closingatdeparture.end is when the terminal confirms that all CHE that participates in the carriervisit are OFF (che.off.status = true) or working in another che.cycle that doesnt corresponds to the specific carriervisit and the “FirstTimeTerminalBerthReadyForDeparture” events has happened.

Truck:

  • carriervisit.terminaloperations.closingatdeparture.start is when the CHE finish the last cycle.

  • carriervisit.terminaloperations.closingatdeparture.end is when the (CHE is off or start another cycle) and (firsttimeterminalberthreadyfordeparture = spreader and che allow the truck to drive).

Rail:

  • carriervisit.terminaloperations.closingatdeparture.start is when at least one of the terminal CHE deployed for performing the carriervisit.terminaloperations ends the cargooperations with the the aim of get the “TerminalBerthReadyForDeparture” or to start the another che.cycle that doesnt corresponds to the specific carriervisit.

  • carriervisit.terminaloperations.closingatdeparture.end is when the terminal confirms that all CHE that participates in the carriervisit are OFF (che.off.status = true) or working in another che.cycle that doesnt corresponds to the specific carriervisit and the “FirstTimeTerminalBerthReadyForDeparture” events has happened so the train is free to move. Train departure process like brake check, machine connection etc is not included in the closingatdeparture activities.

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 =2021-11-15T15:14:01.352Z

visit.terminaloperations.preparationatarrival..end.time.output.actual =2021-11-16T15:14:01.352Z

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


 Haz clic aquí para ampliar...

Created by

Edited by

Review / Approve

Published

  Francisco Blanquer Jaraiz 2021-11-157

 

 

 

  

 

 

  • Sin etiquetas