Managed Service Orchestrator Release 23.12 Compliance Acceptance Criteria

[kelaja]

Release Compliance 23.12

Source in Catena-X Confluence + Expert Contacts here. (Source only accessible for Catena-X Consortia members in current transition phase)

• Gaia-X compliance confirmed by dedicated expert.

  • Obtain approval from CX Gaia-X expert(s), prior to Gate review.
  • Provide info as early as possible; expect optimization loops based on feedback
    => check linked PDF summary for requirements (Source only accessible for Catena-X Consortia members in current transition phase).

  Contact:

  • Release Mangement

• GDPR compliance confirmed
  (personal data; Data Protection & Privacy DPP)

  • assessment must be completed via Catena-X GDPR questionnaire (Source only accessible for Catena-X Consortia members in current transition phase.)
  • either the product/service doesn`t process any relevant data,
  • or - in case the assessment reveals potential issues - a more severe "Data Privacy Impact Assessment" shall be conducted (if applicable: robust mitigation actions must be completed)
    Provide evidence for GDPR compliance prior to Gate review. Previous assessments remain valid, as long as approach to handling of personal data was not changed.

  Contact:

  • Release Mangement

• Interoperability Check

  Acceptance criteria are fulfilled as described in in the following area on confluence: Interoperability Quality Gate Requirements (Source only accessible for Catena-X Consortia members in current transition phase.)

  • Approval will be documented centrally by Expert(s)

  • Obtain approval from Interoperability experts prior to Gate review.

  Therefore consult the regular office hours as early as possible; expect optimization loops based on feedback. (Source only accessible for Catena-X Consortia members in current transition phase.)

  Contact:

  • SYSTEM ARCHITECT2

• Data Sovereignty Check

  Acceptance criteria are fulfilled as described in in the following area on confluence:

  • Data Sovereignty Guardrails for Release 3.2 (Source only accessible for Catena-X Consortia members in current transition phase.)
  • Approval will be documented centrally by Expert(s)
  • Obtain approval from Data Sovereignty experts prior to Gate review: Experts will schedule a review with your team.

  Expect optimization loops based on feedback.

  Contact:

  • SYSTEM ARCHITECT3,
  • SYSTEM ARCHITECT4

• Confirmation of published CX Standards

  Product Owner confirms:

  • The FOSS product under review is compliant to all relevant Catena-X Standards which are already published on the Association website.
  • Failure to do so may ultimately make the reference implementation useless, as the mandatory CX Certification cannot be accomplished.

• Verification of foreseen CX Standards

  Product Owner confirms:

  • The content of upcoming CX Standardization Requests (STAN) has been reviewed and feedback was provided to the responsible PCA/BDA. As per current status, the FOSS product under review will be compliant as soon as the CX Standard is published. (Info here) (Source only accessible for Catena-X Consortia members in current transition phase.)
  • 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 available and CX Standard is published on website.

[MehranRoshandel]

@dvasunin there are no changes regarding GPDR and Gaia-X; please add the documents from last Release 3.2 to this ticket.
@kelaja we need someone for the data Sovereignty; what should we do here?
@kelaja: and @RolaH1t, last time we agreed on no need for the data Interoperability check anymore

[sharathshivprasad]

The links are available for Catena-X members.

Managed service Orchestrator QG4 Acceptance Criteria FOSS | R3.2.0 QG4: https://jira.catena-x.net/browse/CXRM-1629

Not Applicable.

[kelaja]

@MehranRoshandel kindly provide your confimation regarding standards.

[kelaja]

For Data Sovereignty POs can do a self-declaration if products have not undergone any significant changes.
See Links (available to Consortia Members only)
2023-11-20 Stay informed & Release 23.12 & 24.03

[MehranRoshandel]

There are no changes regarding the data Sovereignty for managed service Orchestrator. So, I prove this by referencing the approval of R3.2.

[MehranRoshandel]

Approval of Standards: There is no changes since R3.2. Managed Service Orchastror does not define any standard. It is only using the existing standard. The tests show that we are compatible with the current standards.