Skip to main content
Release: CX-Neptune (Preview)

Conformity Assessment Criteria

General Information​

  • cxId: CX-0128
  • name: Demand and Capacity Management Data Exchange
  • capability: Demand and Capacity
  • version: 2.3.1
  • release: CX-Saturn

Conformity Assessment Criteria​

CX-0128-CAC-001​

  • type: MUST
  • topic: Policy
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Policies within Catena-X MUST be aligned with the example usage policy in the CX ODRL Profile and with all subsections of 2.3 Additional Requirements.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Contract Definitions, Policies and AssetsAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. used by the EDC for the respective APIsAPI An API is a way for two or more computer programs to communicate with each other..

Information​

Policies

CX-0128-CAC-002​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedMaterialDemand
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The unique identifier for the semantic model, as specified in this standard, MUST be used to define the meaning of the data being transferred.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier.: Egest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedMaterialDemand

CX-0128-CAC-003​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedMaterialDemand
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The JSON payload provided by data providers MUST comply with the JSON schema as specified in this standard and MUST be validated against the same JSON schema by data consumers.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier.: Egest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing)., SupplierSupplier In the context of OSim, the producer of goods.: Ingest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedMaterialDemand

CX-0128-CAC-004​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedMaterialDemand
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Within the Catena-X data space WeekBasedMaterialDemand data MUST be requested and exchanged using a connector, conforming to the standards [CX-0018] and [CX-0002]. It MUST be transferred using the WeekBasedMaterialDemand API

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier.: Egest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing)., SupplierSupplier In the context of OSim, the producer of goods.: Ingest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedMaterialDemand

CX-0128-CAC-005​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedCapacityGroup
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The unique identifier for the semantic model, as specified in this standard, MUST be used to define the meaning of the data being transferred.

Proof of Conformity​

SupplierSupplier In the context of OSim, the producer of goods.: Egest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedCapacityGroup

CX-0128-CAC-006​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedCapacityGroup
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The JSON payload provided by data providers MUST comply with the JSON schema as specified in this standard and MUST be validated against the same JSON schema by data consumers.

Proof of Conformity​

SupplierSupplier In the context of OSim, the producer of goods.: Egest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing)., CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier.: Ingest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedCapacityGroup

CX-0128-CAC-007​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedCapacityGroup
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Within the Catena-X data space WeekBasedMaterialCapacityGroup data MUST be requested and exchanged using a connector, conforming to the standards [CX-0018] and [CX-0002]. It MUST be transferred using the WeekBasedCapacityGroup API

Proof of Conformity​

SupplierSupplier In the context of OSim, the producer of goods.: Egest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing)., CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier.: Ingest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). WeekBasedCapacityGroup

CX-0128-CAC-008​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedRequestForUpdate
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The unique identifier for the semantic model, as specified in this standard, MUST be used to define the meaning of the data being transferred.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Egest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedRequestForUpdate

CX-0128-CAC-009​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedRequestForUpdate
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The JSON payload provided by data providers MUST comply with the JSON schema as specified in this standard and MUST be validated against the same JSON schema by data consumers.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Egest and Ingest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedRequestForUpdate

CX-0128-CAC-010​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedRequestForUpdate
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Within the Catena-X data space IdBasedRequestForUpdate data MUST be requested and exchanged using a connector, conforming to the standards [CX-0018] and [CX-0002]. It MUST be transferred using the RequestForUpdate API.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Egest and Ingest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedRequestForUpdate

CX-0128-CAC-011​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedComment
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The unique identifier for the semantic model, as specified in this standard, MUST be used to define the meaning of the data being transferred.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Egest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedComment

CX-0128-CAC-012​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedComment
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The JSON Payload provided by data providers MUST comply with the JSON schema as specified in this standard and MUST be validated against the same JSON schema by data consumers.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Egest and Ingest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedComment

CX-0128-CAC-013​

  • type: MUST
  • topic: Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedComment
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Within the Catena-X data space IdBasedComment data MUST be requested and exchanged using a connector, conforming to the standards [CX-0018] and [CX-0002]. It must be transferred using the IdBasedComment API.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Egest and Ingest of Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing).

Information​

Aspect ModelAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). IdBasedComment

CX-0128-CAC-014​

  • type: MUST
  • topic: Payload Structure
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

When exchanging data with a DCM partner, the POST request payload MUST be structured as follows:

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Serialization of Aspect ModelsAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing). as Payloads

Information​

Payload Structure

CX-0128-CAC-015​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedMaterialDemand
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Within the Catena-X data space APIsAPI An API is a way for two or more computer programs to communicate with each other. MUST only be accessible via a connector, conforming to the standard [CX-0018].

Proof of Conformity​

SupplierSupplier In the context of OSim, the producer of goods.: EDC AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedMaterialDemand

CX-0128-CAC-016​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedMaterialDemand
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The APIAPI An API is a way for two or more computer programs to communicate with each other. MUST be registered as a data assetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. as defined in Section 4.1.2.5.

Proof of Conformity​

SupplierSupplier In the context of OSim, the producer of goods.: EDC AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedMaterialDemand

CX-0128-CAC-017​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedMaterialDemand
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The APIAPI An API is a way for two or more computer programs to communicate with each other. MUST be implemented as defined in Section 4.1.2.

Proof of Conformity​

SupplierSupplier In the context of OSim, the producer of goods.: APIAPI An API is a way for two or more computer programs to communicate with each other. Logic

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedMaterialDemand

CX-0128-CAC-018​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedCapacityGroup
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Within the Catena-X data space APIsAPI An API is a way for two or more computer programs to communicate with each other. MUST only be accessible via a connector, conforming to the standard [CX-0018].

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier.: EDC AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedCapacityGroup

CX-0128-CAC-019​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedCapacityGroup
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The APIAPI An API is a way for two or more computer programs to communicate with each other. MUST be registered as a data assetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. as defined in Section 4.2.2.5.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier.: EDC AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedCapacityGroup

CX-0128-CAC-020​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedCapacityGroup
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The APIAPI An API is a way for two or more computer programs to communicate with each other. MUST be implemented as defined in Section 4.2.2.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier.: APIAPI An API is a way for two or more computer programs to communicate with each other. Logic

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. WeekBasedCapacityGroup

CX-0128-CAC-021​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedRequestForUpdate
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Within the Catena-X data space APIsAPI An API is a way for two or more computer programs to communicate with each other. MUST only be accessible via a connector, conforming to the standard [CX-0018].

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: EDC AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedRequestForUpdate

CX-0128-CAC-022​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedRequestForUpdate
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The APIAPI An API is a way for two or more computer programs to communicate with each other. MUST be registered as a data assetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. as defined in Section 4.3.2.4.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: EDC AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedRequestForUpdate

CX-0128-CAC-023​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedRequestForUpdate
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The APIAPI An API is a way for two or more computer programs to communicate with each other. MUST be implemented as defined in Section 4.3.2.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: APIAPI An API is a way for two or more computer programs to communicate with each other. Logic

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedRequestForUpdate

CX-0128-CAC-024​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedComment
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Within the Catena-X data space APIsAPI An API is a way for two or more computer programs to communicate with each other. MUST only be accessible via a connector, conforming to the standard [CX-0018].

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: EDC AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedComment

CX-0128-CAC-025​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedComment
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The APIAPI An API is a way for two or more computer programs to communicate with each other. MUST be registered as a data assetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. as defined in Section 4.4.2.5.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: EDC AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedComment

CX-0128-CAC-026​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedComment
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The APIAPI An API is a way for two or more computer programs to communicate with each other. MUST be implemented as defined in Section 4.4.2.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: APIAPI An API is a way for two or more computer programs to communicate with each other. Logic

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. IdBasedComment

CX-0128-CAC-027​

  • type: MAY
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. DCM AAS
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Data providers MAY adopt the DCM AAS APIAPI An API is a way for two or more computer programs to communicate with each other.. If they choose otherwise, none of the obligations of this section apply.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Self Assessment

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. DCM AAS

CX-0128-CAC-028​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. DCM AAS
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Within the Catena-X data space APIsAPI An API is a way for two or more computer programs to communicate with each other. MUST only be accessible via a connector, conforming to the standard [CX-0018].

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: EDC AssetsAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. DCM AAS

CX-0128-CAC-029​

  • type: MUST
  • topic: APIAPI An API is a way for two or more computer programs to communicate with each other. DCM AAS
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The APIAPI An API is a way for two or more computer programs to communicate with each other. MUST be implemented as defined in Section 4.5.2.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: APIAPI An API is a way for two or more computer programs to communicate with each other. Logic

Information​

APIAPI An API is a way for two or more computer programs to communicate with each other. DCM AAS

CX-0128-CAC-030​

  • type: MUST
  • topic: Processes
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Companies adopting demand and capacity management in Catena-X MUST conform to the processes and guidelies defined in Chapter 5 and all its subsections.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Application and Business Logic

Information​

Processes

CX-0128-CAC-031​

  • type: REQUIRED
  • topic: Capabilities
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The following sections describe capabilities, that are REQUIRED (except for subsections that are defined as optional):

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Self Assessment

Information​

Capabilities

CX-0128-CAC-032​

  • type: OPTIONAL
  • topic: Capabilities
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

The following sections describe capabilities, that are OPTIONAL:

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Self Assessment

Information​

Capabilities

CX-0128-CAC-033​

  • type: MUST
  • topic: Capabilities
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

Software solutions implementing demand and capacity management in Catena-X MUST conform to the data formats and processes defined in the following sections, for every capability they intend to offer:

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Application and Business Logic

Information​

Capabilities

CX-0128-CAC-034​

  • type: MUST
  • topic: Framework
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

All participants involved in the Catena-X DCM use case MUST consent to the Data Exchange Governance framework agreement.

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Cofinity-X Wallet

Information​

Framework

CX-0128-CAC-035​

  • type: MUST
  • topic: Policies
  • automisable: false
  • assessment:   - [ ] Inspection   - [ ] Observation   - [ ] Self-Assessment   - [ ] Inquiry   - [x] Confirmation   - [ ] Recalculation   - [ ] Reperformance   - [ ] Analytical   - [ ] Procedures

Requirement​

A key aspect of managing business partner relationships within Catena-X involves defining and applying policies that facilitate and protect data exchange. Both customersCustomer In the context of OSim, the receiver of produced goods from a supplier. and suppliersSupplier In the context of OSim, the producer of goods. MUST implement and uphold these policies in order to guarantee a secure and collaborative data exchange:

Proof of Conformity​

CustomerCustomer In the context of OSim, the receiver of produced goods from a supplier. and SupplierSupplier In the context of OSim, the producer of goods.: Contract Definitions, Policies and AssetsAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. used by the EDC for the respective APIsAPI An API is a way for two or more computer programs to communicate with each other. and Application and Business Logic

Information​

Policies