1.   Introduction

The publication TIC4.0 2024.013 covers the following topics:

• 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.

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

Terminal Automation is a field where the TIC4.0 semantics can show its potential to achieve seamless and harmonised communications. For this purpose, the Task Force “Terminal Automation” was founded inside of the organisation, comprised of all major experts from the members. In this latest publication, the different systems and methodology of work are described, based on methods with proven track record. The future vision is to achieve a harmonised document or “TIC4.0 standard requirements” that can be added into Request for Proposals (RFP) of automated terminals.

Translation: Reefer Monitoring Systems to TIC4.0

In the previous version of this document, the equivalencies of the data flowing between the TOS and the RMS were detailed, mainly related to the measurements from IoT sensors, the different Set Points, and the characteristics of the Reefer Cargo Visit. This allowed for the representation of the most relevant states of the reefer through the exchanged data. In this iteration, a key aspect has been incorporated: the tasks that a reefer cargo must receive from various parties while within the terminal's domains. This task focused on establishing the equivalencies between these actions and their representation using the terms defined in TIC4.0, such as "Job Instruction" and "Order." This new set of translations allows the TOS and RMS to exchange messages, incorporating actions to be taken by a party on a reefer cargo, such as connecting or disconnecting the cargo from the power source.

2.   Data Model

For the digital formatting of the semantic and Dataset we need a Data Model to structure the data and a Data Schema to define the details of the content, such as the validity of the format, the type of data (Boolean, entire, real etc.), which data is mandatory or could be omitted etc.

The Dataset has been defined based upon the RDF Resource Description Framework using the subject->predicate->object schema.

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 MEASUREMENTs in 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 MEASUREMENTs that need to be represented.

A detailed definition of the Data Model can be found in Data Model.

The Dataset is the content of the Data Model, a flat version without hierarchy or rules. The Dataset is used by humans, but machines need the Data Model and the Data Schema to translate it to a digital format. 

3.  Generic Documentation

In this release, the following generic documents, definitions and other information are available:

4.  Definitions

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

4.1 General

 4.2 TOS

4.3 KPI