1. Introduction

The publication TIC4.0 2026.019 covers the following topics:

• TF Terminal Automation: The Task Force has published the white paper Chain of Command, focused on how operational intentions are transformed into executable machine actions across ISA-95/IEC 62264 functional levels. In addition, new definitions for Machine Control and Execution Control have been introduced to support clearer interoperability between operational and automation layers.

• Yard Inventory: The new TIC4.0 paper Place as a Subject – Yard Digital Representation establishes the semantic foundation for representing terminal spaces, yard layouts, inventory, and operational states in a standardized and queryable way. The work enables interoperable descriptions of static and dynamic terminal places, including yard slots, cargo locations, mobile equipment, and coordinate-based positioning, supporting future digital twin, analytics, and automation use cases.

• Smart eCHE Operations: TIC4.0 has published two new papers related to Smart eCHE Operations: Smart eCHE Operations – Charging Process, focused on the operational and semantic modelling of the eCHE charging lifecycle, and Smart eCHE Operations – IEC TS 61851-27 Alignment, focused on the interoperability alignment between TIC4.0 and IEC TS 61851-27. In addition, new TIC4.0 definitions including aEVSE, Plugging, Unplugging, and Mating Space have been introduced to support the digital representation of automated charging infrastructure and operations.

• Chain of Command: TIC4.0 updates the TOS TIC4.0 data model to formalize and differentiate “Order”-related concepts across terminal and logistics operations, establishing a mutually exclusive naming structure and a clear automation-layer “Chain of Command.” At the ERP level, Purchase Orders manage procurement activities, while Logistic Orders govern operational logistics flows. The processed Logistic Order is transformed into a Job Instruction, then into Job Orders for scheduling and dispatching. Execution Control converts Job Orders into machine-level Tasks, enabling traceable, data-driven execution and feedback across all TIC4.0 automation layers.

• KPI: TIC4.0 has introduced the new KPI definition Equivalent Moves Per Hour (EMPH), which measures the operational productivity of Ship-to-Shore (STS) quay cranes normalized according to crane size and expressed as equivalent moves per hour based on a standard reference crane.

Smart eCHE Operations – Charging Process

This document outlines the alignment between the TIC4.0 Smart eCHE operational model and the IEC TS 61851-27 standard for automated conductive charging, highlighting how TIC4.0 provides a critical semantic layer to bridge the gap between physical device behavior and terminal-wide data interoperability. While the IEC standard focuses on the technical requirements for docking and energy transfer, TIC4.0 introduces a subject-oriented framework that formalizes these processes into structured data exchanges—such as state transitions for the aEVSE, manipulator, and charging session—enabling seamless integration into fleet management, digital twins, and automated terminal workflows.

Chain of Command

The whitepaper clarifies the term “Order” in maritime logistics and updates the TIC 4.0 data model to distinguish clearly between contractual, logistical, and operational layers. It defines a chain of command across ISA‑95/IEC 62264 functional levels, mapping how high-level intentions become machine-executable work. This standardization reduces ambiguity, improves interoperability between ERP, Terminal Operating Systems (TOS), and equipment control layers, and supports accurate telemetry and feedback loops.

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.

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’ 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 MEASUREMENT ESSENTIALS 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 MEASUREMENT ESSENTIALS that need to be represented.

A detailed definition of the Data Model can be found in Data Model. Furthermore, the latest, official version of the Semantics (PAS 4000) can be downloaded from BSI’s website here.

Alignment with IEC TS 61851-27

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 2026.019 publication:

4.1 Automation

4.2 Smart eCHE Operations for Container Terminals

4.3 KPI