Introduction

This publication TIC4.0 2022.005 contains two main blocks: a very extensive and detailed presentation of the TIC4.0 concepts (TIC4.0 MasterClass) and a set of Semantics, Data Model and Definitions on the following topics:

• CycleJob Instruction: It this is an update of the 2022.003 release. The terminal.gate.cycle is now included. With this definition, the most important cycles within a terminal have been defined; the highest level process: terminal.cycle, the subprocesses: terminal.berth.cycle, terminal.yard.cycle, terminals.gate.cycle, terminal.train.cycle, terminal.horizontaltransport.cycle and at the equipment level: CHE.cycle.

• Carrier Visit: includes important definitions for processes from the perspective of a carrier visit: Arrival, TerminalOperations and Departure.

• Cargo Visit: includes important definitions to follow the process of the cargo on a terminal, such as Inbound and Outbound as well as unambiguous definitions related to the weight of cargo. With these definitions, the most important definitions for the “Cargo Visit” have been defined.

• Schema JSON to FLAT: a very important work has been done for anyone who intends to implement TIC4.0. The JSON Schema is defined and clear instructions for a human to convert a JSON format dataset into a FLAT format are included. TIC4.0 developed and published an open-source software tool to automatically convert datasets from JSON to FLAT. The source code can be included in any program and is available via GitHub.

• Datamodel: The existing data models are updated reflecting the definitions of this release and the latest development around the TIC4.0 semantic.

This publication extends definitions of previous releases on 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 Cycle - which is required to describe the processes of a terminal related to moving payloads.

With the Schema JSON to FLAT this publication provides the required step by step instructions (and an open-source conversion tool) to convert the data from the JSON format to the FLAT format. This is important for the implementation of the semantics.

...

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

• Order: belongs to Job Instructions, and defines the specific coordinate action (with other orders) to be done by the subject over the object.

• Job Instruction List: this is just a collection of job instructions, but very relevant to organising the sequences.

• Preparation At Arrival: belongs to terminal operations related to any carrier visit process. It includes all the activities of the terminal in preparation for the start of carrier visit cargo operations.

• Cargo Operations: this is the process that moves the cargo itself.

• Lashing: this includes all related to the lashing/unlashing activities to securitize the cargo in the carrier.

• Closing At Departure: belongs to terminal operations related to any carrier visit process. It includes all the activities of the terminal in preparation for the departure of the carrier visit.

The publication 2022.005 clarifies very important concepts and insights into why TIC4.0 is the way it is. The TIC4.0 MasterClass tries to show up these concepts and will be used in several seminars to explain to the public why TIC4.0 is ready for BigData.

With the introduction of Job Instruction (Orders and Job Instruction List), the most important element of the TOS data model is finally available. This definition will allow describing any instruction to any subject (CHE, driver, maintenance, etc). It will facilitate de transmision of orders between different ecosystems.

With the definitions of the Terminal Operations elements, a very detailed description of the carrier visit can finally be done. Including all the effort preparing the cargo operations and the departure of the carrier.

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.

...

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

...

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.

...

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.

A detailed definition of the Data Model can be found in https://tic40.atlassian.net/l/c/XBT1vEBA

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

...