TIC 4.0
2026.018 Release
1. Introduction
The publication TIC4.0 2026.018 covers the following topics:
2026.018 PAS 4000 vs TIC4.0 legacy semantic: Summary outlining all changes made to the semantics due to the adaptation to PAS4000, alongside a document detailing how and why PAS4000 was created.
Place as a subject: The ontology around “Place” has been described and developed. This work is enabling to show all data within a Container Terminal from the point of view of the place. This is a fundamental work that is required to optimize a yard from the perspective of the place.
TF Automation: Planning Module: TIC4.0 has convened on the following “Planning” definition: Planning is the function responsible for defining future cargo moves. It determines what work is required, where cargo should be positioned, and by when, based on forecasted demand and estimated resource availability. Planning operates with a long time horizon with high uncertainty. Depending on the operational configuration and carrier type, Planning output may include preliminary sequences or resource allocations.
Smart eCHE Operations: The TF eCHE will publish the definitions Energy Source 2026.018 , Energy Storage System , Energy Supply , Motor and the revisions of Plugged 2026.018 and Unplugged 2026.018 . These adapt key concepts of the Electric Vehicle world into the TIC4.0 language, enabling the digital modelling of these systems.
EDIFACT: CODECO to TIC4.0: Continuing previous work, the EDIFACT Task Force has completed the translation of the CODECO Message to the TIC4.0 environment.
KPI: Three new KPIs have been developed in this publication cycle: Quay Throughput TEU Density (QTpTD) , Berth Throughput TEU Density (BTpTD) , Frequency of Unplanned Assignment Interruption (FUAI) .
General Definitions: A new definition for “Quay” has been created, complementing the existing for “Berth”.
FOR-FREIGHT - Wrap Up: A reflection on how the FOR-FREIGHT project provided TIC4.0 with concrete strategic benefits, including the establishment of a partnership with the Open Logistics Foundation, writing of policy recommendations for the European Commission, and the first operational proof of interoperability with another transportation mode, namely the IATA ONE Record Proof of Concept. These outcomes offer TIC4.0 practical tools, validated standards, and new avenues for collaboration across multimodal transport.
PAS4000 - Adaptation and publishing
TIC4.0 has partnered with the British Standards Institution (BSI) to develop PAS 4000, a Publicly Available Specification that formalizes TIC4.0's semantics framework. The goal is to strengthen the credibility and interoperability of TIC4.0's semantic model, while laying the groundwork for full ISO standardization by 2029. Supported by PEMA as external sponsor, the specification went through several rounds of expert review before receiving formal approval in January 2026 and being published by BSI in February. Alongside this milestone, the publication introduced several updates to TIC4.0's semantics: messages are now formally structured into a header and a payload, and "Points of Measurement" have been reclassified under a broader category called Measurement Essentials, which also encompasses metadata. These changes bring greater clarity and consistency to how data is modelled and exchanged across systems.
Place as a subject
This document defines the TIC4.0 ontology for “Place” as a core Subject representing any physical space in a terminal that can host cargo or operations, whether static (e.g., yard slots, berths, buildings) or dynamic (e.g., spreaders, chassis positions). A Place is always addressable through a Location, which may be expressed logically, geographically (e.g., WGS-84), or technically through machine-based coordinate systems, with Reference Coordinate Systems ensuring consistent transformations between global, terminal-local, and equipment frames. By using a single conceptual model for both fixed yard structures and moving equipment, and by deriving logical identifiers from geometry, the framework creates a deterministic, interoperable foundation that unifies static layout, machine motion, and cargo traceability—allowing terminals to consistently answer where cargo is, how it moves, and how space is structured across operational and analytical contexts.
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.
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.
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 |
2026.018 | Place as a subject | The “Place as a subject” publication defines Place as any physical space in a terminal that can host cargo or operations—whether static yard infrastructure or dynamic equipment positions—treated as a core, inventorized TIC4.0 Subject. Each Place is described via a Location (logical, geographic, or machine-based coordinates) tied together by Reference Coordinate Systems, creating a single, interoperable model that unifies layout, equipment movement, and cargo traceability across all use cases. | Publication | |
2026.018 | FOR-FREIGHT - Wrap Up | Shows how the FOR-FREIGHT project validated TIC4.0 semantics in real multimodal use cases, built a TIC4.0 message translator powering multiple AI optimisation tools, and delivered the first operational interoperability proof with IATA ONE Record, plus a partnership with the Open Logistics Foundation and policy recommendations for the European Commission. | Publication | |
2026.018 | How PAS4000 was created | Document describing how the process of PAS4000 was conducted, detailing the steps of how TIC4.0’s semantics became an official standard for the first time. | Publication | |
2026.018 | 2026.018 PAS 4000 vs TIC4.0 legacy semantic | Details on the major changes PAS4000 brings to TIC4.0’s semantics. | Publication | |
2026.018 | A Flexible Decision Framework for Container Terminal Control | White Paper: A Flexible Decision Framework for Container Terminal Control | TIC4.0 has clarified its approach to decision modes in terminal automation — defining how authority is distributed between functions such as Scheduling and Dispatching — concluding that these modes should be documented at the architectural level rather than embedded in the data model, preserving interoperability and flexibility across different implementations. | Publication |
4. Definitions
The following definitions have been created or modified in this 2026.018 publication:
4.1 General Definitions
Publication | Definition | Link | Definition | TIC4.0 Semantic |
2026.018 | Quay | A quay (pronounced key or kay) is a solid, linear, man-made platform built along the shore where carriers can be positioned for loading or unloading cargo or passengers, for refueling and/or repairs safely. | SUBJECT |
4.2 Automation
Publication | Definition | Link | Definition | TIC4.0 Semantic |
2026.018 | Planning module | Planning is the function responsible for defining future cargo moves. It determines what work is required, where cargo should be positioned, and by when, based on forecasted demand and estimated resource availability. Planning operates with a long time horizon with high uncertainty. Depending on the operational configuration and carrier type, Planning output may include preliminary sequences or resource allocations. | SUBJECT |
4.3 Place
Publication | Definition | Link | Definition | TIC4.0 Semantic |
2026.018 | Place | Place refers to a precisely defined and uniquely identifiable place within the subject's operational domain, well defined by its location (mandatory), physical dimension and shape, that can be used, occupied or referenced by an object. This definition includes both fixed and moving places, as well as permanent and temporary ones. | SUBJECT |
4.4 KPI
Publication | Definition | Link | Definition | TIC4.0 Semantic |
2026.018 | Quay Throughput TEU Density (QTpTD) | Quay Throughput TEU Density (QTpTD) measures the total number of TEUs handled over a defined time window, normalized by the total physical quay length. | KPI | |
2026.018 | Berth Throughput TEU Density (BTpTD) | Berth Throughput TEU Density (BTpTD) measures the total number of TEUs handled over a defined time window, normalized by the total physical berth length. | KPI | |
2026.018 | Frequency of Unplanned Assignment Interruption (FUAI) | Frequency of Unplanned Assignment Interruption (FUAI) measures the frequency (count) of which unplanned equipment faults occur, over the reporting windown, that interrupt an active assignment and require corrective maintenance action. Here, assignment refers to the active job instruction. | KPI |
4.5 TF Smart eCHE Operations for Container Terminals
Publication | Definition | Link | Definition | TIC4.0 Semantic |
2026.018 | Energy Source | The matter or material that contains and supplies energy to the Container Handling Equipment (CHE), enabling it to operate. | SUBJECT | |
2026.018 | Energy Storage Systems (ESS) | A device composed of the actual energy storage (physical, chemical, etc.) plus a management system that operates it according to operational and safety parameters. | SUBJECT | |
2026.018 | Energy Supply | Unit or combination of units converting the energy from the Energy Source or/and Energy Storage System to useable energy to perform specific tasks required on the eCHE. | SUBJECT | |
2026.018 | Motor | Motor refers to the component responsible for the motion for an equipment. It consumes energy (in whatever format = fuel, electric energy, hydraulics, ..) and converts it into motion. | SUBJECT | |
2026.018 | Plugged 2026.018 | Defines the state of the referred subject - If it is physically ready to be powered. | CONCEPT | |
2026.018 | Unplugged 2026.018 | Defines the state of the referred subject - If it is not plugged (physically attached to a power source) | CONCEPT |
4.6 EDIFACT to TIC4.0
Publication | Definition | Link | Definition | TIC4.0 Semantic |
2026.018 | CODECO UNH Message Header - BGM Beginning of Message | UNH is a service segment starting and uniquely identifying a message. The message type code for the Container gate-in/gate-out report message is CODECO. | EDIFACT | |
2026.018 | CODECO Segment Group 1: RFF - Reference | Segment group 1 expresses a reference which applies to the entire message, such as: - reference to the previous message. It is part of the “Header” of the CODECO and doesn’t give details to the content. | EDIFACT | |
2026.018 | CODECO Segment Group 2: TDT + RFF - Details of Transport and Reference | CODECO Segment Group 2: TDT + RFF - Details of Transport and Reference | A segment to indicate transport details related to the main carriage stage of the transport (sea), such as carrier/liner service. | EDIFACT |
2026.018 | CODECO Segment Group 3: LOC+DTM | A segment to specify a location related to the main carriage stage such as place of arrival and place of departure. | EDIFACT | |
2026.018 | CODECO Segment Group 4: NAD | A segment to identify the party's name and address, and function, such as: - message recipient - message sender - ordering customer - ordering customer agent. | EDIFACT | |
2026.018 | CODECO Segment Group 5: CTA - COM | A segment to identify a person or department of a message sender and/or message recipient, such as: - information contact | EDIFACT | |
2026.018 | CODECO Segment Group 10: EQD-RFF-TMD-DTM-LOC- MEA-DIM-SEL-FTX-EQA-HAN | CODECO Segment Group 10: EQD-RFF-TMD-DTM-LOC- MEA-DIM-SEL-FTX-EQA-HAN | A segment identifying a container, container size/type. The equipment status may be e.g. overlanded, shortlanded, import, export. | EDIFACT |
2026.018 | CODECO Segment Group 11: DAM - COD | A segment to specify equipment damages, such as the point of the damage on the equipment, and the type of damage. A segment to specify component details of the damaged equipment. | EDIFACT | |
2026.018 | CODECO Segment Group 12: TDT- DTM | TDT is a segment to identify the pre-carriage or on-carriage transport details by which the container will arrive before being loaded or by which the container will depart after being discharged. DTM is this group is a segment to specify a date/time relating to the on-carriage location, such as arrival or departure date/time. | EDIFACT | |
2026.018 | CODECO Segment Group 13: LOC | The LOC segment in this place is used to specify ports/locations associated with inland transport of a container, such as: - place of departure - place of arrival | EDIFACT | |
2026.018 | CODECO Segment Group 10: NAD - Name and Address | A segment to specify the actual address where a piece of equipment is to be delivered finally (final place of positioning). (It’s part of the equipment details | EDIFACT | |
2026.018 | CODECO Segment Group 14: DGS - FTX | A segment to identify the UN-number and the class of the dangerous goods loaded in the container. | EDIFACT | |
2026.018 | CODECO Segment Group 16: TMP-RNG | Temperature - A segment which identifies the transport temperature setting of the container. Range Details - A segment to specify the transport temperature range setting of the container. | EDIFACT | |
2026.018 | CODECO Segment CNT Control Total - UNT Message Trailer (Draft) | CODECO Segment CNT Control Total - UNT Message Trailer (Draft) | CNT is a segment to specify the number of containers in the message, explicitly given by the sender. UNT is the message trailer and service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message. | EDIFACT |