1.   Introduction

...

• General Definitions: The concepts “Available”, “Not Available”, “Scheduled”, “Planned”, “Not Available and Scheduled”, “Not Available and Planned” and “Terminal Closed Scheduled” have all been defined to achieve clarity on what each of them represents. Furthermore, a new version of the “Job Instruction” definition has been created that adds some remarks made by the Reefer Task Force.

• Redefining Terminal Automation: Progress and Visions for the Future – Status November 2024 (2024.13 Release): This document presents the methodology adopted to develop standardised references for terminal automation. Establishing this framework was a vital initial step towards the creation of a strong basis to tackle Terminal Automation’s future challenges and setting the scene for the future developments, while showcasing the advancements made across the various working groups that compose the Task Force.

• KPI definitions: KPIs “Gross Berth Hours”, “Quay Container Moves (Box) ‘QCM’” and “Quay Throughput ‘QT’” have been defined during this publication period, offering a comprehensive overview on these operational performance indicators.

• Reefer definitions: This release updates the subjects "Order" and "Job Instruction," adding the Task Services related to reefer interventions. Furthermore, a new version of the “Translation: Reefer Monitoring Systems to TIC4.0” has been created. Lastly, a first version of the Data Model containing all of these changes has been created.

• TF Communication to vessel EDI: After the publication of the White Paper EDI to TIC4.0, the Task Force has been working on translating one of the most important messages, COARRI, taking into account all the different segments present in the message. All the work is reflected in the COARRI to TIC4.0 publication, which highlights the equivalences between the two standards, facilitating the understanding and interpretation of the data.

Redefining Terminal Automation: Progress and Visions for the Future – Status November 2024 (2024.13 Release):

...

Following the semantic web standard (subject: object) the model has 3 main components: header, asset description and measurement.

...

SUBJECT creates the hierarchy tree structure (we have sub-subjects) that helps to identify the boundary of the value. The hierarchy is fixed by TIC4.0 for each kind of subject (CHE, TOS, Terminal) and can mix any type of subjects (e.g. machine.process = che.move). The subjects conform to an array defined by the (concept) metadata so various identical subjects but with different metadata (id or name or location or…) can be sent in the same message. (one message with several CHE's or one CHE with several spreaders).

The CONCEPT's metadata defines ‘what is’ and the CONCEPT‘what does’. Both are flat (no hierarchy, no arrays) and as many as necessary can be used. Additionally, two concepts can be combined with ‘and’ or ‘or’ creating a new concept which includes the condition that makes both true. For e.g. ‘hoisting_and_trolleying’ that represents the action of hoisting and trolleying at the same time (both statuses must be true).

OBSERVED PROPERTIES define the ‘magnitude’ of the CONCEPT, are flat (no hierarchy) and can be used as many times as necessary with a CONCEPT.

For each OBSERVED PROPERTY, an array created by the combination of the different POINT OF MEASUREMENTsin time (actual, estimated, etc), place (input, iinput, ioutput, output), timestamps and the different Units will give an array (a list) of VALUEs. The array could be if necessary in each message. The length will depend on the relation between the data frequency and the message frequency and also the amount of different POINT OF MEASUREMENTsthat need to be represented.

...

4.  Definitions

The following definitions have been created or modified in this 2024.013 publication:

...

 4.2 TOS

4.3 KPI