Modular Production (MP) KIT Release 23.12 Adoption View Acceptance Criteria

[kelaja]

Release 23.12 KIT Adoption View

• [x] KIT Repo in Tractus-X

  • A KIT must have an own repository in Eclipse Tractus-X. The naming of the repository must have a postfix "-kit"
  • e.g. "traceability-kit"
  • this applies to all KITs with own source code, test cases, test data etc

  Artifact Repository:

  • eclipse-tractusx

  Contacts:

  • Responsible: PCA/BDA
  • Consult: KIT-CONTACT1, KIT-CONTACT2
  • Review by: Tractus-X Project Leads: KIT-CONTACT2, SYSTEM_TEAM3, SYSTEM_TEAM2

• [x] Vision and Mission Documents in Repository

  • Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.

  Best Practice:

  • eclipse tractusx-docs-artefacts
  • How-to-create-a-KIT-website

  Artifact Repository:

  • eclipse-tractusx

  Contacts:

  • Responsible: PO/BO (from relevant Domain)
  • Consult: KIT-CONTACT1, KIT-CONTACT2
  • Review by: PCA/BDA

• [x] Business Value Documents in Repository

  • Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.

  Best Practice:

  • eclipse tractusx-docs-artefacts
  • How-to-create-a-KIT-website

  Artifact Repository:

  • eclipse-tractusx

  Contacts:

  • Responsible: PO/BO (from relevant Domain)
  • Consult: KIT-CONTACT1, KIT-CONTACT2
  • Review by: PCA/BDA

• [x] Semantic Model standards submitted and published

  • KIT Product Owner confirms:
  • The KIT under review is compliant to all relevant Semantic Model Standards which are already published on the Association website.
  • The content of upcoming Semantic Model Standardization Requests (STAN) has been reviewed and feedback was provided to the responsible PCA/BDA.
  • An appendix has been created with a list of certification criteria (e.g., test cases) for the conformity assessment process.

  Best Practice:

  • A KIT must link to the published semantic model standards on the Catena-X Association website.
  • https://catena-x.net/de/standard-library
  • eclipse tractusx-docs-artefacts
  • How-to-create-a-KIT-website
  • Note: Please create and submit standards in time according to process and timeline > The standardization process (Source only accessible for Catena-X Consortia members in current transition phase.)
  • Note: Failure to do so may ultimately make the KIT useless, as the mandatory CX Certification cannot be accomplished

  Artifact Repository:

  • eclipse-tractusx

  Contacts:

  • Responsible: PO/BO (from relevant Domain)
  • Responsible for Process: Semantic Team
  • Consult: KIT-CONTACT1, KIT-CONTACT2
  • Review by: PCA/BDA

• [x] Logic / Schema standards submitted and published

  • KIT Product Owner confirms:
  • The KIT under review is compliant to all relevant Logic / Schema Standards which are already published on the Association website.
  • The content of upcoming Logic / Schema Standardization Requests (STAN) has been reviewed and feedback was provided to the responsible PCA/BDA.
  • An appendix has been created with a list of certification criteria (e.g., test cases) for the conformity assessment process.

  Best Practice:

  • A KIT must link to the published logic/schema standards on the CX Website.
  • https://catena-x.net/de/standard-library
  • eclipse tractusx-docs-artefacts
  • How-to-create-a-KIT-website
  • Minimum: PCA/BDA have finalized all release-relevant Standardization Requests (STAN). Those have passed the CX Association`s technical committee (TC4S) and are pre-published on the website. Opt-out period in progress.
  • Best case: Association Board approval is available and CX Standard is published on website.
  • Note: Please create and submit standards in time according to process and timeline > The standardization process (Source only accessible for Catena-X Consortia members in current transition phase.)

  Contacts:

  • Responsible: PO/BO (from relevant Domain)
  • Responsible for Process: PCA/BDA
  • Consult: KIT-CONTACT1, KIT-CONTACT2
  • Review by: PCA/BDA

• [x] Business Process Documentation

  • Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.

  Best Practice:

  • eclipse tractusx-docs-artefacts
  • How-to-create-a-KIT-website

  Contacts:

  • Responsible: PO/BO (from relevant Domain)
  • Consult: KIT-CONTACT1, KIT-CONTACT2
  • Review by: PCA/BDA

• [ ] Architecture Documentation

  • Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.

  Best Practice:

  • eclipse tractusx-docs-artefacts
  • How-to-create-a-KIT-website

  Contacts:

  • Responsible: PO/BO (from relevant Domain)
  • Responsible for Process: EAs
  • Consult: KIT-CONTACT1, KIT-CONTACT2
  • Review by: PCA/BDA

• [x] Access and Usage Policies Documentation

  • Mandatory if a use case needs access & usage policies.
  • Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.
  • Policies must contain:
  • a human-readable text (aligned with legal)
  • a technical policy that can be executed by the EDC

  Best Practice:

  • eclipse tractusx-docs-artefacts
  • How-to-create-a-KIT-website
  • https://github.com/eclipse-tractusx/edc-legal-policies

  Artifact Repository:

  • eclipse-tractusx

  Contacts:

  • Responsible: PO/BO (from relevant Domain)
  • Support for Data Sovereignty: SYSTEM ARCHITECT3
  • Consult: KIT-CONTACT1, KIT-CONTACT2
  • Review by: PO / BO (from relevant Domain)

• [x] Tutorials and Documenation

  • recommended; not mandatory
  • Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.

  Best Practice:

  • eclipse tractusx-docs-artefacts
  • How-to-create-a-KIT-website

  Contacts:

  • Responsible: PO/BO (from relevant Domain)
  • Consult: KIT-CONTACT1, KIT-CONTACT2
  • Review by: PCA/BDA

• [x] White Paper

  • recommended; not mandatory
  • Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.

  Best Practice:

  • eclipse tractusx-docs-artefacts
  • How-to-create-a-KIT-website

  Contacts:

  • Responsible: PO/BO (from relevant Domain)
  • Consult: KIT-CONTACT1, KIT-CONTACT2
  • Review by: PCA/BDA

[kelaja]

• KIT Repo in Tractus-X, no reference implementation so the PR is sufficient @maximilianong https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/pull/495/files
• Vision and Mission okay @danielmiehle
• Business Value Document okay @danielmiehle
• Semantic Model Standards submitted and published okay @danielmiehle
• Logic and Schema Standards submitted and published okay @danielmiehle
• Business Process Documentation okay @danielmiehle
• Architecture Documents okay @maximilianong
• Access and Usage Policies OPTIONAL @maximilianong
• Tutorial and Documentation OPTIONAL @maximilianong
• White Paper Okay, IP clearance okay @maximilianong