IC | IC-Hub Industry Core Reference Implementation

[eckardg]

Overview

Create a new application that is built on the Industry Core Standards and KITs. With that we want to make the industry core more tangible, provide a reference for other applications, but also provide services or code that can be used by use cases building on the industry core.
The development will be done from scratch but will also incorporate experience and potentially available building blocks from other applications if available.

Even though the target is a functionality that completely implements the industry core standards, the capabilities will be provided subsequently in order to provide early results that can be enhanced later.

The application has to provide capabilities for data providers and data consumers. As there is a potential overlap with the Industry Core Testbed, we will focus on data provisioning in the first step.

Explain the topic in 2 sentences

Create a new reference implementation for the industry core, providing capabilities for data providers and data consumers.

What's the benefit?

The reference implementation makes the industry core more tangible.
It will also serve as the single source of truth for future testing activities.
As the code is available application developers can get insights how to use the EDC and the DTR or even make use of appropriate services
This increases interoperability between partner applications in the value chain, making onboarding more efficient and accelerates the introduction of new use cases built on the industry core.

What are the Risks/Dependencies ?

This will be completely open source development, we depend on the developers that want to participate.

There is a dependency to #1159; regular alignment meetings have to be conducted in order to avoid overlap and redundant features.
As a first approach, we will focus on data provisioning in IC-Hub and on data consumption in IC testbed. In a later step we have to bring the features together.

Detailed explanation

Current implementation

Currently several FOSS applications are available that implement the industry core partly. Most are not developed as open source any more, and they typically contain parts that are not part of the industry core. It is difficult to onboard new developers.

Proposed improvements

In addition to the program logic a good documentation is required and an easy access to deployment. It must be possible to deploy the application locally and test the features.

Feature Team

Contributor

• nya
• Contributor 1
• Contributor 2

Committer

• Mathias Moser
• Committer 1
• Committer 2

User Stories

• Issue 1, linked to specific repository
• Issue 2, linked to another specific repository

Acceptance Criteria

• Criteria 1
• Criteria 2
• Criteria 3

Test Cases

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented.

In the context of the standards 126 and 127, typically only one is applicable, depending on the specific use case. Please cross out one of the two standards that does not apply.

• [x ] This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
    • [x ] CX-0010 Business Partner Number
    • [x ] CX-0013 Identity of Member Companies
    • [x ] CX-0018 Data Space Connectivity (EDC)
    • [x ] CX-0049 DID Document Schema
    • [x ] CX-0050 Framework Agreement Credential
    • [ x] CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
    • [x ] CX-0001 EDC Discovery API
    • [x ] CX-0002 Digital Twins in Catena-X
    • [x ] CX-0018 Data Space Connectivity (EDC)
    • [x ] CX-0126 Industry Core: Part Type 2.0.0
    • [x ] CX-0127 Industry Core: Part Instance 2.0.0
  • Data Format:
    • [x ] The data model is based on a published Semantic Model
• The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• Potential risks or conflicts with existing architecture has been assessed

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

• [x ] I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)