...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
1. Introduction
The publication TIC4.0 2024.013 covers the following topics:
...
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.
...
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.
...
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:
...
Release | Title | Link | Definition | TIC4.0 Classification |
2024.013 | 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 | Publication | |
2024.013 | Translation of "Reefer Monitoring System" to TIC4.0 2024.013 | Translation of "Reefer Monitoring System" to TIC4.0 2024.013 | Description of how the information of a Reefer Monitoring System can be translated to TIC4.0, complete with a table of equivalences | Publication |
2024.013 | Reefer Data Model 2024.013 | Data Model representing any reality of the cargo reefer related to status and processes. | Data Model | |
2024.013 | COARRI to TIC4.0 | Translation from COARRI to TIC4.0 | Publication |
4. Definitions
The following definitions have been created or modified in this 2024.013 publication:
...
Publication | Definition | Link | Definition | TIC4.0 Semantic |
2024.013 | Available | Subject is able to be used or obtained. | CONCEPT | |
2024.013 | Not available | Subject is unable to be used or obtained | CONCEPT | |
2024.013 | Is Scheduled | Status indicates that the subject concept was intended to be or do regularly in the far future, for example, a timetable | CONCEPT | |
2024.013 | Is Planned | This status indicates that the subject concept was intended by all the actors to be or do an action/status (concept) in the future in a specific and detailed way and time | CONCEPT | |
2024.013 | Not available and Is Scheduled | Status that indicates that the subject is not available to be used or obtained due to a scheduled closure (event notified 12 hours in advance) | CONCEPT | |
2024.013 | Not available and Is Planned | Subject is not available to be used or obtained due to a planned closure (public holiday, legal rest times, religious customs and others). | CONCEPT | |
2024.013 | Terminal Closed Is Planned | Subject is not available to be used or obtained due to a planned closure .(event notified at least 12 hours in advance) | CONCEPT | |
2024.013 | Terminal Closed IS Scheduled | Subject’s (by default, terminal) scheduled closure time periods due to public holidays, legal rest times or other local customs (prayers, festivities, etc.). | CONCEPT |
4.2 TOS
Publication | Definition | Link | Definition | TIC4.0 Semantic |
2024.013 | Job Instruction 2024.013 | A job instruction is a collection of orders (something) that a source (system/someone) tells to subjects (system/someone/something/equipment) to do to an object (system/someone/something/equipment) in a coordinated way. Modified by the Reefer Task Force. | CONCEPT | |
2024.013 | Order 2024.013 | “Order” (order) indicates one action to perform with the JobInstruction. It includes only one subject, doing one action to one object. | CONCEPT |
4.3 KPI
Publication | Definition | Link | Definition | TIC4.0 Semantic |
2024.013 | Gross Berth Hours | Amount of time that the carriervisit has been actually at berth or in contact with the berth (carrieratberth|status = true), measured for a completed carriervisit period | KPI | |
2024.013 | Quay Container Moves (Box) “QCM” | Quay Box Moves is the volume of cargo type container, measured in unit “box”, moved from/to all the berths to/from the waterside carrier of the terminal during a specific period of time | KPI | |
2024.013 | Quay Throughput (TEUs) “QT” | Quay Throughput is the volume of cargo type container, measured in unit TEU, moved from/to all the berths to/from the waterside carrier of the terminal during a specific period of time | KPI |