[R.25.09] DCM: Tier-N Collaboration

[LukasSchmetz]

Description

Develop Tier-N collaboration functionality beyond one-up and and one-down relationship

Feature Team

Contributor

• Philipp Mai
• Markus Wagner

Committer

• @stephanbcbauer
• Committer List to be added to PR

Explain the topic in 2 sentences

The idea is to develop a functionality to enable collaboration/data exchange beyond the 1:1 business relationship. This means e.g. collaboration between OEM, Tier 1 and Tier 2 for specifics materials/parts (e.g. direct buy parts).

What's the benefit?

Increased transparency, cost reduction and tier-n collaboration possibility along the whole supply chain.

What are the Risks/Dependencies ?

(Unclear) Legal Risks / PURIS EG also elaborating on n-tier collaboration + exchange with Regulatory Expert Group

Detailed explanation

Enable collaboration beyond one-up/one-down relationship

Current implementation

Data Exchange/Collaboration only in 1:1 business relationsship

Proposed improvements

Data Exchange/Collaboration beyond 1:1 business relationsship

User Stories

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

Acceptance Criteria

• Tier-N collaboration concept developed
• Tier-N collaboration concept refined
• Tier-N collaboration concept finalized
• Initial PR
• Final PR

Architectural Relevance

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

• 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)
    • CX-0010 Business Partner Number
    • CX-0013 Identity of Member Companies
    • CX-0018 Data Space Connectivity (EDC)
    • CX-0049 DID Document Schema
    • CX-0050 Framework Agreement Credential
    • CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
    • CX-0001 EDC Discovery API
    • CX-0002 Digital Twins in Catena-X
    • CX-0018 Data Space Connectivity (EDC)
  • Data Format:
    • 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

• 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)

[stephanbcbauer]

@LukasSchmetz , @MWADCM replaced the Additional Information section

[reginePrivat]

I would like to contribute

[kenobi79]

I would like to contribute

[Frank-Globisch]

I'd like to contribute

[lanfrans]

I'd like to contribute

[KZI-CatX]

I'd like to contribute

[LukasSchmetz]

No delivery artefact for R 25.03 expected and therefore changed to R25.06