Introduction
In TIC4.0 we started with a bottom-up approach defining the language to translate different equipment data into a unified, standardised data view, meaning into the same type of information. Then we realised the industry needs more: and so expanded the engineering driven language into a language to represent any type of reality in a data driven digital view.
“CHE talks TIC” is only the beginning - and it is also a pre-requisite for digitization and digitilization in the terminal industry. Only if TIC4.0 is being requested by terminal operators in technical specifications and also only if TIC4.0 is being offered by solution providers to the industry, TIC4.0 will become reality.
This document provides a guideline and structure supporting the technical clarification process between terminal operator and solution provider.The aim is to support the clarification and help to understand what the terminal provider is requesting and what the solution provider is providing.
The required definitions and background ideas will be explained first, the main points that need to be agreed upon are explained, illustrations of a possible system architecture are given and based on the CHE Data Model 2022.005 an example is given on how the two main dimensions “Content Level” and “Level of Data Provision” should be clustered to gain mutual understanding.
...
Introduction
In TIC4.0 we started with a bottom-up approach defining the language to translate different equipment data into a unified, standardised data view, meaning into the same type of information. Then we realised the industry needs more: and so expanded the engineering driven language into a language to represent any type of reality in a data driven digital view.
“CHE talks TIC” is only the beginning - and it is also a pre-requisite for digitization and digitilization in the terminal industry. Only if TIC4.0 is being requested by terminal operators in technical specifications and also only if TIC4.0 is being offered by solution providers to the industry, TIC4.0 will become reality.
Management Summary
This document provides a guideline and structure supporting the technical clarification process between terminal operator and solution provider. The aim is to support the clarification and help to understand what the terminal operator is requesting and what the solution provider is providing.
At a very high level the technical clarification process between terminal operator and solution provider is described first and identified at which point in the process it is important to apply the two “CHE talks TIC” principles: “Content Level” and “Data Provision Level”.
Both principles will then be explained, before this guideline becomes quite technical and dives deep into….
The required definitions and background ideas will be explained first, the main points that need to be agreed upon are explained, illustrations of a possible system architecture are given and based on the CHE Data Model 2022.005 an example is given on how the two main dimensions “Content Level” and “Level of Data Provision” should be clustered to gain mutual understanding.
Therefore, this document describes the “Content Level” and the “Level of Data Provision” and concepts with a view towards including TIC4.0 in technical specifications. It is independent of the current data level supported by the CHE, an actual implementation or the direction of data flow.
High-Level technical clarification process
Drawio | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Definitions and background
...
Drawio | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Data Provision Level
Another important question in the technical specification process is the question: “Who is actually delivering, which part of the solution?” To gain a clear understanding between terminal operator and solution provider we are differentiating into three different levels of “Data Provision”: AVAILABLE, PROVIDED and PROCESSES. The level of Data Provision also has an influence on the number or the quality of data points that can be provided or computed by the CHE. We developed a rule to identify the level of “Data Provision” depending on the observed property, which is part of the data set.
...
Terminal operator to specify the following to CHE solution provider
Content level Level requirements (Level 1, Level 2, Level 3 as specified by TIC4.0)
Data Provision Level requirements
Physical network (e.g., WiFi, Wireless mesh, 4G, 5G, etc.) that is implemented at the terminal for data exchange.
Messaging framework (PUB/SUB software) and provide
the lightweight client version to the CHE operator (for them to install on the CHE for communicating with the broker).
Broker details for CHE to establish the connections with the Broker
...