[PURIS KIT] PURIS KIT maintenance

[tom-rm-meyer-ISST]

Overview

Explain the topic in 2 sentences

We want to improve the PURIS KIT with business-wise content and further implementation support.

What's the benefit?

Pull more adopters by explaining the ideas and the implementation pragmatically.

What are the Risks/Dependencies ?

No

Detailed explanation

Current implementation

See Kit, files

Proposed improvements

Feature Team

Contributor

• @Clemens-L-Schwarz
• Contributor 2

Committer

• @tom-rm-meyer-ISST
• Committer 2

User Stories

• [Story] Emphasize Business Scenarios in Adoption View eclipse-tractusx.github.io#1081
• [Story] Add a getting started with PURIS section to PURIS KIT (organizational) eclipse-tractusx.github.io#1082
• [Story] Add a getting started with PURIS section to PURIS KIT (technical) eclipse-tractusx.github.io#1083

Acceptance Criteria

• Quality Gate Ticket has been created
• Quality Gate has been passed

Test Cases

Not applicable

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]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Inbox. ⇾ Only features with status backlog are considered in open planning