Introduction

This publication TIC4.0 2022.006 contains the following topics:

• “CHE talks TIC” - Guideline on how the include TIC in technical specifications: aims to support the technical clarification process between terminal operator and solution provider by providing a framework on how to structure and classify the available data points.

• Carrier Visit: an extensive overview of the main events and processes along the carrier visit process, including a direct mapping to the timestamps defined by DCSA (Digital Shipping Association). In addition, the majority of events and processes are defined and published according to the TIC4.0 semantics.

• Job Instruction: this is the most important process related to the TOS data model. It includes any order sent to any subject to execute any action over any object… basically, any kind of instruction to be executed. In this publication, the “Job Instruction Subject” and the “Job Instruction Object” are defined.

• Spreader: this is the first set of definitions directly targeting the Spreader. It is an important set of definitions as the spreader is an important component in the whole process across all CHE, being constantly in contact with the container (cargo).

• FLAT to JSON: in addition to the “JSON to FLAT” converter published in Release R2022.004 the principles of how to translate the dataset from the FLAT format into the JSON format is now being published. TIC4.0 developed and published an open-source software tool to automatically convert datasets from FLAT to JSON. The source code can be included in any program and is available via GitHub.

This publication adds to previous publications with “CHE talks TIC” with a very important guideline in making sure TIC4.0 becomes reality. It makes the procurement and specification process easier on all sides, as it offers a framework that can easily be applied and is a very good starting point to get an agreement.

Are you a terminal manager and you would like to implement TIC4.0 standards in your terminal, but your engineers, your IT department or your solution provider, vendor, or manufacturer tell you: it is too big, they do not know, what to focus on, there are too many data points available. And you just want to get them started? Then “CHE talks TIC” is the document you should look at! We structured the available Data Model into 4 Content Levels starting from very basic (Level 1) up to the full scope (Level 4). This will help you to make decisions and inform you what else needs to be considered when procuring a CHE, which “talks TIC”.

Are you an engineer and you have to specify, which TIC data shall be provided by the solution provider, vendor, or manufacturer? Then “CHE talks TIC” is the document you should look at! This provides a framework on how to structure and classify the available datapoints, when procuring a CHE, which “talks TIC”.

Are you a solution provider, vendor or manufacturer and you are convinced, that providing your equipment with a TIC interface, but just seems to be too overwhelming. Then “CHE talks TIC” is the document you should look at! We structured the available Data Model into 4 Content Level starting from very basic (Level 1) up to the full scope (Level 4). You could offer and market various "language levels” or you could support your customer by applying the principles defined in this document.

This publication adds to previous publications and also extends definitions of previous releases on one of the most important processes found in terminal operations: the Carrier Visit - which is the interaction of the terminal with the other parties in the logistics chain: vessel, truck, and train. In addition, the first set of definitions directly targeting the Spreader, a very important component in the whole process can be found. Job Instruction is extended and with the FLAT to JSON this publication provides the required step-by-step instructions (and an open-source conversion tool) to convert the data from the FLAT format to the JSON format. This is important for the implementation of the semantics especially when there is limited possibility for big messages.

These definitions are part of TIC4.0’s ongoing work to develop a common vocabulary for the cargo handling industry and will be followed by future releases, as defined by the TIC4.0 Dataset Roadmap. The current list of definitions being worked on can be accessed on the digital platform of TIC4.0. This publication release provides the actual definitions and includes them in the TIC4.0 templates with the general approach on how to use these in Data Models, Data Schema's, JSON formats and provides high-level scenarios as examples.

1. TIC 4.0 scope

The purpose of TIC4.0 is to define a common language that can be represented in an understandable format, including data and information elements suitable for digitalization.

With the definitions and language, any reality (equipment or process) in a port terminal environment can be uniquely described. The vocabulary needs to be valid for any equipment, process and protocol (digital or human) in any port terminal in any location. The typical elements that make up the port terminal activities are cargo handling equipment (any kind of machine within the terminal that performs a job or task), external vehicles (trucks, vessels, trains), terminal infrastructure (berth, yard, gate), or auxiliary elements (energy, light, refuelling…).

For data-driven terminal operations, the subject of standardization concerns the data and information elements linking the digital solutions to the physical equipment and hardware.

To achieve the above goal TIC4.0 has developed a Semantic set of rules based on human language which helps in the creation process of the definitions/vocabulary. The definitions/vocabulary can be considered as the building blocks and together with the TIC4.0 semantic rules, allow the user to describe any reality in a specific, unambiguous way, irrespective of the level of technology used in a terminal.

The vocabulary is managed in a Dataset, which is basically a one-dimensional database list. This list is not static and will grow exponentially as TIC4.0 continues to work on more and more segments and areas of a terminal.

The work of TIC4.0 is to define the individual entries of the Dataset/Dictionary, focusing on a logical group or theme. In the Dataset/Dictionary the user can see the status of each entry and which entries are published and a link to the definition is provided.

To apply the vocabulary in each entry in several digital protocols, a Data Schema is needed. TIC4.0 will propose a Data Schema for each of the most common protocols, but the Data Schema is compatible with any protocol. In the examples that are provided, TIC4.0 usually uses JSON as it is very user-friendly and easy to read.

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

Open

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” 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 PROPERTies 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 as long as 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 https://tic40.atlassian.net/l/c/XBT1vEBA

The Data Schema was provided as part of the 2022.004 release and it defines the rules that the Data Model will follow and allows the translation from a hierarchy format to a flat format.

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 we are publishing the following element:

4. Definitions

In this release we defined the following elements:

Generic Definitions

Carrier Visit

Job Instruction

Spreader