[R25.09] DCM: KIT Maintenance

[LukasSchmetz]

Overview

General Maintenance of DCM KIT including bug fixes.

DCM KIT Maintenance Roadmap Item

Explain the topic in 2 sentences

This features ensures DCM KIT Maintenance activities. This also include potential bug fixes from previous Releases.

What's the benefit?

Ensure proper DCM KIT representation.

What are the Risks/Dependencies ?

low risk / no dependencies

Detailed explanation

This features ensures DCM KIT Maintenance activities. This also include potential bug fixes from previous Releases.
Set up a readme with proper guidelines to follow for KIT.

Feature Team

Contributor

• @MWADCM
• @LukasSchmetz

Committer

• @ClosedSourcerer

Acceptance Criteria

• DCM KIT Maintenance topics identified

• DCM KIT Maintenance topics developed

• DCM KIT Maintenance topics integrated

• Ensure compability with DCM Standard CX-0128

• Initial PR

• Final PR

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.

• 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)
    • CX-0126 Industry Core: Part Type 2.0.0
    • CX-0127 Industry Core: Part Instance 2.0.0
  • 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)

[ClosedSourcerer]

ToDos:

• Verify QnA
• Move away from .svg and reenable mermaid wherever possible, after docusraus 3.0 upgrade
• Align folder names according to the updated guidelines
• Remove API-Specification pages and link to API-Hub from API pages instead
• Maybe: Include Policy and Contract definition step in API sequence diagrams
• Update standard dependencies within architecture view
• Fix spelling and grammar
  • within a supply chain mist companies act as a "one-up" in one business relationship,
• Adoption ViewMaybe change "Access and Usage Policies" to be more precise and explain what Access und Usage Policy actually means
• Include Examples for Usage Policy, Access Policy and Contract definition
• Integrate simulation scenario relevant stuff in parallel with its addition to the standard

[stephanbcbauer]

was presented during open planning for release 25.09

[LukasSchmetz]

minor adaptations done