CX-0105 Asset Tracking Use Case v1.1.0
ABSTRACT
The asset tracking use case aims to design a standard solution how diverse IoT solutions, available on the free market, can be incorporated into the Catena-X network keeping the interoperability and data sovereignty requirements respected. Although the main goal was always to track company assets with the various IoT devices, based on the set of standards designed by asset tracking use case team, there is a potential to fully use these in any use case in the Catena-X environment and beyond. The model opens the door for any IoT device manufacturer and any network provider to be part of the Catena-X network.
This standard focuses on the Asset Tracking Use Case. It includes relevant requirements for
- ATP (Asset Tracking Platform) as sensor data provider
- Application/Dashboard as data consumer - non standardized tool
FOR WHOM IS THE STANDARD DESIGNED
Please refer to: AUDIENCE & SCOPE.
COMPARISON WITH THE PREVIOUS VERSION OF THE STANDARD
This is the initial version of the standard.
1 INTRODUCTION
This document defines the so-called standardization triangle for the asset tracking use case. Standardization triangle hereby means the mandatory components, data models, and APIs that are required to enable the asset tracking use case.
1.1 AUDIENCE & SCOPE
This section is non-normative
This document is meant for the following roles:
- Data Provider / Consumer
- Business Application Provider
1.2 CONTEXT AND ARCHITECTURE FIT
This section is non-normative
The Asset Tracking Platform aims to bring different IoT sensor networks to a standard Catena-X network and use sensor data for a variety of use cases, like:
- Logistics teams can track their returnable packages and assets at any time using geo data
- Use of automatic filling level measurements to drive efficient vendor-managed inventories
- Users (Tier suppliers, customers, carriers, insurers, etc.) are encouraged to monitor the quality of critical materials at any time during transportation
Asset Tracking Platform- Component Overview
Asset Tracking Platform- Process Flow Diagram
Components:
Asset Tracking Platform (Data Provider)
The Asset Tracking Platform can be understood as a Hub that accepts data from IoT Networks, standardizes it, and enables it for Catena-X Components, Services, and Applications.
Dashboard/Application (Data Consumer)
A Dashboard/an Application can be used in the Catena-X Network to visualize sensor data from diverse IoT sensors.
It enables users to search & manage assets, devices, pairs & real-time tracking of assets using geo data sensors, optimizing vendor-managed inventories through automatic filling level measurements, allowing stakeholders Tiers, customers, carriers, insurers, etc.
Networks:
The Asset Tracking Platform can be understood as a Hub that accepts data from IoT Networks, standardizes it, and enables it for Catena-X Components, Services, and Applications.
Business Partners:
These are external entities, possibly suppliers, manufacturers, carriers, or other stakeholders, who are a part of the Catena-X network. They interact with the system to exchange data related to assets.
EDC (Eclipse Dataspace Connector):
It's the central communication component for Catena-X that acts as a bridge between different data providers and consumers within the Catena-X ecosystem to implement a framework agreement for sovereign, cross-organizational data exchange. It ensures secure and standardized data exchange.
dDTR (Decentralized Digital Twin registry):
It's a decentralized registry that lists all digital twins and references including information about the underlying asset, asset manufacturer, and access options, like aspect endpoints. Moreover, the dDTR is used to register and find data related to DTs.
AAS (Asset Administration Shell) storage:
It acts as a database for storing standardized device and sensor data. Devices that are paired/active can send their data to the ATP for standardization. The standardized data will be appended as a Submodel to the AAS of the parent IoT Device. The ATP normalizes the sensor data received from various IoT networks, creates an AAS model, and stores it in the AAS Storage component. It is used to describe an asset electronically in a standardized manner.
Service discovery:
It has the ability to map an EDC connector endpoint to a BPN.
BPN Discovery Service:
BPN discovery services help to restrict the number of EDCs to be accessed & it maps certain information to a business partner number (BPN). It helps the business application provider to identify the BPN of the data asset under consideration. e.g. to discover available EDC connectors.
1.3 CONFORMANCE AND PROOF OF CONFORMITY
This section is non-normative
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key words MAY, MUST, MUST NOT, OPTIONAL, RECOMMENDED, REQUIRED, SHOULD and SHOULD NOT in this document document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
All participants and their solutions will need to proof, that they conform to the Catena-X standards. To validate that the standards are applied correctly, Catena-X employs Conformity Assessment Bodies (CABs).
1.3.1 PROOF OF CONFORMITY
This section is normative
To proof conformity with the use case Asset Tracking:
-
An Asset Tracking Platform as a (sensor) data provider:
- MUST be able to convert the device and received network data in standardized semantic data models (IotSensorData and IotSensorDeviceDefinition).
- MUST register Digital Twins for IoT Sensor Devices with specific asset IDs (refer to 2.2 ADDITIONAL REQUIREMENTS)
-
For an Asset Tracking Application as a data consumer:
- MUST be able to link the digital twins of asset with one or multiple devices.
- The consumption of standardized data MUST be done via the EDC.
1.4 EXAMPLES
1.5 TERMINOLOGY
This section is non-normative
ATP: Asset Tracking Platform
EDC: Eclipse Dataspace Connector
dDTR: Decentral Digital Twin Registry
Business Partner Number (BPN): A BPN is the unique identifier of a partner within Catena-x
AAS: Asset Administration Shell
Additional terminology used in this standard can be looked up in the glossary on the association homepage.
2 RELEVANT PARTS OF THE STANDARD FOR SPECIFIC USE CASES
This section is normative
2.1 "Asset Tracking: Triangle Document"
2.1.1 LIST OF STANDALONE STANDARDS
To participate in the Asset Tracking use case, the following single standards MUST be fulfilled by all participants for which the standard is relevant:
- CX-0002 Digital Twins in Catena-X v2.0.0
- CX-0018 Eclipse Data Space Connector (EDC) v2.1.0
2.1.2 DATA REQUIRED
2.1.3 ADDITIONAL REQUIREMENTS
2.1.4 DIGITAL TWINS AND SPECIFIC ASSET IDs
The Asset Tracking Platform as a sensor data provider MUST register the Digital Twins for IoT Sensor Devices with the BPNL for ownerID, device serial number, device type, and name of manufacturer. ex:
{
"description": [],
"globalAssetId": {
"value": [
"b77383db-b9ab-48fd-ae43-d44f356d7898"
]
},
"idShort": "IoTDevice_123-0740-3434-A",
"identification": "b77383db-b9ab-48fd-ae43-d44f356d7898",
"specificAssetIds": [
{
"value": "BPNL00000003ABXD",
"key": "ownerID"
},
{
"value": "15698-0740-3434-A",
"key": "serialNumber"
},
{
"value": "TRACK01111",
"key": "type"
},
{
"value": "Company A",
"key": "manufacturer"
}
],
"submodelDescriptors": [
{
"description": [
{
"language": "en",
"text": "The Shell for IoT Sensor Device"
}
],
"idShort": "IotSensorDeviceDefinition",
"identification": "8c73e97a-62a9-4b29-b33a-e55cfbf5f342",
"semanticId": {
"value": [
"urn:samm:io.catenax.iot_sensor_device_definition:2.0.0#IotSensorDeviceDefinition"
]
},
"endpoints": [
{
"interface": "EDC",
"protocolInformation": {
"endpointAddress": "https://{company_edc}/edcs/19b22764-032d-4625-a9db-cbaa695e5cfa/assets/b77383db-b9ab-48fd-ae43-d44f356d7898",
"endpointProtocol": "IDS/ECLIPSE DATASPACE CONNECTOR",
"endpointProtocolVersion": "0.0.1-SNAPSHOT"
}
}
]
}
]
}
3 ASPECT MODELS
This section is normative
3.1 ASPECT MODEL "IotSensorDeviceDefinition v2.0.0"
3.1.1 INTRODUCTION
This aspect model is needed for the onboarding process of an IoT Sensor Device for the registration in Catena-X network. The onboarding process is done via the Asset Tracking Platform (ATP).
3.1.2 SPECIFICATIONS ARTIFACTS
The modeling of the semantic model specified in this document was done in accordance to the "semantic driven workflow" to create a submodel template specification SMT. The data model is described in SAMM and like all Catena-X data models, this model is available in a machine-readable format on GitHub2F2F conformant to CX-0003.