Color coding of this document:

Still needs to be amended

Is ready

Introduction

This publication TIC4.0 2022.004 contains the Semantics, Dataset Roadmap, Data Model and Definitions on the following topics:

• Cycle: extension of the 2022.003 release with regards to terminal, berth, yard, train and horizontal transport cycle.

• Carrier Visit: includes 2 important concepts to follow the process of a carrier visit, such as “Arrival” and “Departure”.

• Cargo Visit: includes important concepts to follow the process of the cargo on a terminal, such as “Inbound” and “Outbound” as well as unambigous definitions related to the weight of cargo.

• Schema JSON to FLAT: very important work was done for anyone who really wants to implement TIC4.0. Clear instructions for a human to convert a dataset from a JSON format into a FLAT format are included in this instruction plus an open source tool was developed to convert from JSON to FLAT automatically. The source code can be included into any program and is available here: Link to Github Open Source.

• JSON Schema: is also new

Update of Datamodel R2022.004

Focus of the following would be extension of existing topics. Plus promoting JSON to FLAT Schema.

In line with the priority set by TIC4.0 members, this publication constitutes a first attempt to cover the most important processes found in terminal operations: the Cargo Visit - which constitutes the sole purpose of terminals, the Carrier Visit - which constitutes the major link(s) to the cargo value chain, and the Health of CHE, which is very important as “healthy” equipment is required to perform all activities on a terminal. The additional topic Drive and Movement constitutes an important step from an engineering perspective to ensure an unambiguous understanding across the industry.

As in the case of Cycle from release 2021.002, Carrier Visit and Cargo Visit are real life processes that TIC4.0 chose to virtualise as “subjects” in the Data Model. Both have a significant and direct relationship to the cargo value chain and are critical to optimise and improve the client experience.

The Carrier Visit Data Model constitutes the pilar of Port Call Optimisation. In the spirit of decarbonising maritime transport, enhancing vessel navigation sustainability, and minimising energy consumption and carbon emissions, TIC4.0 provides a solid way to digitalise the port call process for the whole industry. The implementation of the TIC4.0 definitions leverages the vessel port call process from a very traditional point-to-point communication and analogue interactions between stakeholders, to a digital, highly connected and systematic interaction. The Carrier Visit Data Model will allow terminal operators and shipping lines (or any other type of carriers applying the same logic) to measure every single subprocess of the process, regardless of whether it is a vessel, truck, train. “If you cannot measure it, you cannot improve it”: the basis for big optimisation lies in these definitions.

Important benefits are foreseen for the different stakeholders:

1. Carriers can make vessel navigation more sustainable and more efficient,

2. Ports can maximise throughput and optimise assets utilisation,

3. Terminals can comply with agreed berthing windows and optimise assets utilisation,

4. Supply chain users can access more predictable and prescriptive cargo info. 

Focussing on the Vessel Carrier Visit (carrier type: vessel), TIC4.0 has developed an extended definition of events and timestamps, which also integrates the more limited list of events adopted by IMO Compendium and DCSA, which articulate the vessel port call. The availability of a complete Data Model facilitates the use of existing and new supporting software applications for the digitalisation and systematic exchange of relevant events between stakeholders.

This work needs to be adopted broadly by the industry - ideally on a global level, to ensure that its benefits can be realised in terms of efficiency and decarbonisation by: (1) implementing data interactions across software applications within Port ecosystems and (2) digitalising & connecting associated planning processes between Carrier-Port-Terminal.

What we expect from the combination of these different standardisation initiatives is:

• Empowerment from a systematic and compliance Framework,

• Follow Data Modeling and API Architecture guidelines,

• Endorse standards and validate published APIs (e.g. Vessel Schedules),

• Improvement areas assessment (root-cause and benefit analysis),

• Leverage pilots and proof-of-concepts outcome into (global) industry adoption.

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.

...

To apply the words in each entry in several digital protocols, a Data Schema is needed. TIC 4.0 will propose Data Schema for each of the most common protocols, but the Data Schema can be used for any protocol. For the examples, TIC 4.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.

...

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'smetadata 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 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.

...

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 Definitions

In this 2022.004 release we defined the following elements:

Cycle

Carrier Visit

First definitions in relation this important topic for terminal operations being part of the TOS Data Model. This will be further expanded in future releases.

Cargo Visit

First definitions in relation this important topic for terminal operations being part of the TOS Data Model. This will be further expanded in future releases.

Schema JSON to FLAT

Text Text