Release: CX-Neptune (Preview)

2 RELEVANT PARTS OF THE STANDARD FOR SPECIFIC USE CASES

This section is normative

2.1 "DIGITAL PRODUCT PASSPORT"

2.1.1 LIST OF STANDALONE STANDARDS

The following standalone standards are relevant for the Use Case Digital Product Passport:

To participate in the digital product passport use case, the following single standards SHOULD be fulfilled by data consumers / applications providers for which the standard is relevant:

CX-0005 Item Relationship Service

2.1.2 DATA REQUIRED

2.1.3 ADDITIONAL REQUIREMENTS

2.1.3.1 Onboarding and IAM

All participant mentioned under 1.1 MUST follow the CX Standards CX-0006 and CX-0014

2.1.3.2 Fetching EDC Endpoints

To find the decentralized registries of related parties in Catena-X, app provider MUST follow the CX-0001 standard.

2.1.4 DIGITAL TWINS AND SPECIFIC ASSET IDs

2.1.4.1 Searching for Decentralized Digital Twin Registries

To find decentralized Digital Twin Registries of related parties in Catena-X, app provider MUST follow the CX-0002 Standard.

2.1.4.2 Registration at the BPN Discovery Service

To find the Business Partner Number of the related parties in Catena-X, data provider MUST follow the CX-0053 standard.

2.1.4.3 Registration of the Digital Twin and the Submodels in the Digital Twin Registry

As described in the industry core standards CX-0126 and CX-0127, when digital twins MUST include the key digitalTwinType. When in Instance Level the value PartInstance MUST be used and in case of Type Level the value PartType MUST be used.

Key	Availability	Description	Type
manufacturerId	mandatory	The Business Partner Number (BPNL) of the manufacturer of the part.	BPNL
digitalTwinType	mandatory	The digitalTwinType has to be set to `digitalTwinType="PartInstance"` or `digitalTwinType="PartType"`. Without this filter, a search for a particular manufacturer part ID would not only return the digital twin of the engineered part, but also all digital twins of the manufacturer that are accessible, i.e., of the corresponding serial parts.	String

Data provider MUST provide their product passport information in the submodelDescriptors depending on their product with the following information:

Product type	used data model	mandatory `idShort`
Generic Passport	Generic Digital Product Pass 6.1.0	`digitalProductPass`
Transmissions	Transmission Pass 3.1.0	`transmissionPass`

The data provider also MUST provide a API Endpoint following the CX-0002. Data- provider MUST register the related sub-models as shown in the example below.
The id added to the subprotocolBody SHOULD be a UUIDv4.
The href definition follows CX-0002.
- After the negotiation and transfer of the subprotocolBody asset following CX-0018 the the href EDR token from the EDC Data Plane Proxy will be used it MUST return the aspect model JSON payload.

Example of a transmission:

"submodelDescriptors":[
  {
    "endpoints": [
      {
        "interface": "SUBMODEL-3.0",
        "protocolInformation": {
          "href": "https://{{edc.data.plane}}/{{path}}/urn:uuid:777a3f0a-6d29-4fcd-81ea-1c27c1b870cc",
          "endpointProtocol": "HTTP",
          "endpointProtocolVersion": [
            "1.1"
          ],
          "subprotocol": "DSP",
          "subprotocolBody": "{{AssetId_of_EDCAsset}};dspEndpoint=https://{{edc.control.plane}}",
          "subprotocolBodyEncoding": "plain",
          "securityAttributes": [
            {
              "type": "NONE",
              "key": "NONE",
              "value": "NONE"
            }
          ]
        }
      }
    ],
    "idShort": "transmissionPass",
    "id": "urn:uuid:777a3f0a-6d29-4fcd-81ea-1c27c1b870cc",
    "semanticId": {
      "type": "ExternalReference",
      "keys": [
        {
          "type": "Submodel",
          "value": "urn:samm:io.catenax.transmission.transmission_pass:3.1.0#TransmissionPass"
        }
      ]
    },
    "description": [
      {
        "language": "en",
        "text": "Transmission Passport Submodel"
      }
    ],
    {
      "endpoints": [
        {
          "interface": "SUBMODEL-3.0",
          "protocolInformation": {
            "href": "https://{{edc.data.plane}}/{{path}}/urn:uuid:777a3f0a-6d29-4fcd-81ea-1c27c1b870cc",
            "endpointProtocol": "HTTP",
            "endpointProtocolVersion": [
              "1.1"
            ],
            "subprotocol": "DSP",
            "subprotocolBody": "{{AssetId_of_EDCAsset}};dspEndpoint=https://{{edc.control.plane}}",
            "subprotocolBodyEncoding": "plain",
            "securityAttributes": [
              {
                "type": "NONE",
                "key": "NONE",
                "value": "NONE"
              }
            ]
          }
        }
      ],
      "idShort": "digitalProductPass",
      "id": "urn:uuid:777a3f0a-6d29-4fcd-81ea-1c27c1b870cc",
      "semanticId": {
        "type": "ExternalReference",
        "keys": [
          {
            "type": "Submodel",
            "value": "urn:samm:io.catenax.generic.digital_product_passport:6.1.0#DigitalProductPassport"
          }
        ]
      },
      "description": [
        {
          "language": "en",
          "text": "Generic Digital Product Passport Submodel"
        }
      ]
    }
  }
]

2.1 "DIGITAL PRODUCT PASSPORT"​

2.1.1 LIST OF STANDALONE STANDARDS​

2.1.2 DATA REQUIRED​

2.1.3 ADDITIONAL REQUIREMENTS​

2.1.3.1 Onboarding and IAM​

2.1.3.2 Fetching EDC Endpoints​

2.1.4 DIGITAL TWINS AND SPECIFIC ASSET IDs​

2.1.4.1 Searching for Decentralized Digital Twin Registries​

2.1.4.2 Registration at the BPN Discovery Service​

2.1.4.3 Registration of the Digital Twin and the Submodels in the Digital Twin Registry​

Legal​