Integrate Digital Twin Registry into MXD

[alexandrudanciu]

Why

The Digital Twin Registry (DTR) is a solution which lists all digital twins and references their aspects including information about the underlying asset, asset manufacturer, and access options, like aspect endpoints. Moreover, the DTR is used to register and find data related to DTs. In general, every partner must proactively register their DTs / Aspects to this service in order to reveal their "order" to share respective data sets.

Hence, the DTR represents an enabling component for Catena-X. Within the interdisciplinary E2E User Journey work stream, the integration of the DTR into the MXD was requested.

The major contribution expected from this integration will be the demonstration of how a consumer actually derives its information demand in terms of relevant providers and data assets.

How

• The DTR shall be integrated based on Helm charts.
• It needs to be investigated if/what persistence service the DTR requires and if the existing PostgreSQL can be reused.
• The DTR can be seeded during the setup phase or could be populated with data by the tutorial user to learn more out it.

What

• Attached are Postman collections demonstrating relevant API calls.
• These DT KIT docs provide detailed descriptions on API calls.

Threats

• The DTR could bloat the MXD cluster.
• The API interaction with the DTR could bloat the tutorial description.

References:

• https://eclipse-tractusx.github.io/docs-kits/next/kits/Digital%20Twin%20Kit/Software%20Development%20View/Specification%20Digital%20Twin%20Kit
• https://github.com/eclipse-tractusx/sldt-digital-twin-registry

Postman_collections.zip