Conformity Assessment Criteria

General Information

• cxId: CX-XXXX
• name: Material Accounting
• capability: Material Accounting
• version: 1.0.0
• release: CX-Titan

CX-XXXX-CAC-001 Digital Twin Logic

• type: MUST
• topic: Logics and Semantics
• automisable: true
• assessment:
  • Inspection
  • Observation
  • Self-Assessment
  • Inquiry
  • Confirmation
  • Recalculation
  • Reperformance
  • Analytical
  • Procedures

Requirement

A digital twin conformant with CX-0002 MUST be created for the processed assetsAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. in case of exchanging material accounting data within Catena-X, conformant with chapter 2.1.4, chapter 3 and chapter 4.1.2, and providing the Batch ID. All processed goods MUST be connected between the individual existing digital twins of them (e.g. partInstance) and the digital twin containing one or more 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). specified in chapter 3.

Proof of Conformity

Data Provider: AAS ID (used as a digital twin ID)

Additional Information

N/A

CX-XXXX-CAC-002 Technical Requirements and Normative Standards

• type: MUST
• topic: Logics
• automisable: true
• assessment:
  • Inspection
  • Observation
  • Self-Assessment
  • Inquiry
  • Confirmation
  • Recalculation
  • Reperformance
  • Analytical
  • Procedures

Requirement

The normative standards MUST be followed and applied, notably CX-0001, CX-0002, CX-0003, CX-0018, CX-0127 and CX-0152. This also applies for 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). data transferred via 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). specified in chapter 3.

Proof of Conformity

N/A

Additional Information

N/A

CX-XXXX-CAC-003 Usage Policy

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

Requirement

Connector AssetsAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. for Material Accounting MUST contain a usage policy conformant with the normative references and all subsections of chapter 2.1, and contain the usage purpose 'cx.materialaccounting.base:1’.

Proof of Conformity

N/A

Additional Information

Policies

CX-XXXX-CAC-004 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). VehicleInformation

• type: MUST
• topic: Semantics, Logics
• automisable: true
• assessment:
  • Inspection
  • Observation
  • Self-Assessment
  • Inquiry
  • Confirmation
  • Recalculation
  • Reperformance
  • Analytical
  • Procedures

Requirement

All paricipants MUST implement the 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). VehicleInformation if applicable for their respective role and be able to request, consume and provide material accounting information, compliant with the license of the semantic model. Data on this 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). MUST be conformant with the semantic model. The JSON Payloads of data providers MUST be conformant to the JSON Schemas as specified in chapter 3.1. The unique identifier of the model MUST be used to define the semantics and the meaning of the data being transferred. Business applications using the semantic model MUST consume this data conforming to the semantic model. Data MUST be consistent with other data exchanged and updated whenever changes occur.

Proof of Conformity

N/A

Additional Information

N/A

CX-XXXX-CAC-005 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). WasteCode

• type: MUST
• topic: Semantics, Logics
• automisable: true
• assessment:
  • Inspection
  • Observation
  • Self-Assessment
  • Inquiry
  • Confirmation
  • Recalculation
  • Reperformance
  • Analytical
  • Procedures

Requirement

All paricipants MUST implement the 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). WasteCode if applicable for their respective role and be able to request, consume and provide material accounting information, compliant with the license of the semantic model. Data on this 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). MUST be conformant with the semantic model. The JSON Payloads of data providers MUST be conformant to the JSON Schemas as specified in chapter 3.2. The unique identifier of the model MUST be used to define the semantics and the meaning of the data being transferred. Business applications using the semantic model MUST consume this data conforming to the semantic model. Data MUST be consistent with other data exchanged and updated whenever changes occur.

Proof of Conformity

Chapter 3.2.7 defines mandatory data attributes for specific actors as well as eligible values for specific data attributes which are required for conformance.

Additional Information

N/A

CX-XXXX-CAC-006 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). RecyclingBatch

• type: MUST
• topic: Semantics, Logics
• automisable: true
• assessment:
  • Inspection
  • Observation
  • Self-Assessment
  • Inquiry
  • Confirmation
  • Recalculation
  • Reperformance
  • Analytical
  • Procedures

Requirement

All paricipants MUST implement the 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). RecyclingBatch if applicable for their respective role and be able to request, consume and provide material accounting information, compliant with the license of the semantic model. Data on this 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). MUST be conformant with the semantic model. The JSON Payloads of data providers MUST be conformant to the JSON Schemas as specified in chapter 3.3. The unique identifier of the model MUST be used to define the semantics and the meaning of the data being transferred. Business applications using the semantic model MUST consume this data conforming to the semantic model. Data MUST be consistent with other data exchanged and updated whenever changes occur.

Proof of Conformity

N/A

Additional Information

N/A

CX-XXXX-CAC-007 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). Material

• type: MUST
• topic: Semantics, Logics
• automisable: true
• assessment:
  • Inspection
  • Observation
  • Self-Assessment
  • Inquiry
  • Confirmation
  • Recalculation
  • Reperformance
  • Analytical
  • Procedures

Requirement

All paricipants MUST implement the 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). Material if applicable for their respective role and be able to request, consume and provide material accounting information, compliant with the license of the semantic model. Data on this 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). MUST be conformant with the semantic model. The JSON Payloads of data providers MUST be conformant to the JSON Schemas as specified in chapter 3.4. The unique identifier of the model MUST be used to define the semantics and the meaning of the data being transferred. Business applications using the semantic model MUST consume this data conforming to the semantic model. Data MUST be consistent with other data exchanged and updated whenever changes occur.

Proof of Conformity

Chapter 3.4.7 defines eligible values for specific data attributes which are required for conformance.

CX-XXXX-CAC-008 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). RecyclingInformation

• type: MUST
• topic: Semantics, Logics
• automisable: true
• assessment:
  • Inspection
  • Observation
  • Self-Assessment
  • Inquiry
  • Confirmation
  • Recalculation
  • Reperformance
  • Analytical
  • Procedures

Requirement

All paricipants MUST implement the 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). RecyclingInformation if applicable for their respective role and be able to request, consume and provide material accounting information, compliant with the license of the semantic model. Data on this 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). MUST be conformant with the semantic model. The JSON Payloads of data providers MUST be conformant to the JSON Schemas as specified in chapter 3.5. The unique identifier of the model MUST be used to define the semantics and the meaning of the data being transferred. Business applications using the semantic model MUST consume this data conforming to the semantic model. Data MUST be consistent with other data exchanged and updated whenever changes occur.

Proof of Conformity

N/A

Additional Information

N/A

CX-XXXX-CAC-009 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). Composition

• type: MUST
• topic: Semantics, Logics
• automisable: true
• assessment:
  • Inspection
  • Observation
  • Self-Assessment
  • Inquiry
  • Confirmation
  • Recalculation
  • Reperformance
  • Analytical
  • Procedures

Requirement

All paricipants MUST implement the 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). Composition if applicable for their respective role and be able to request, consume and provide material accounting information, compliant with the license of the semantic model. Data on this 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). MUST be conformant with the semantic model. The JSON Payloads of data providers MUST be conformant to the JSON Schemas as specified in chapter 3.6. The unique identifier of the model MUST be used to define the semantics and the meaning of the data being transferred. Business applications using the semantic model MUST consume this data conforming to the semantic model. Data MUST be consistent with other data exchanged and updated whenever changes occur.

Proof of Conformity

Chapter 3.6.7 defines mandatory data attributes for specific actors as well as eligible values for specific data attributes which are required for conformance.

Additional Information

N/A

CX-XXXX-CAC-010 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). SerialPart of CX-0127 Industry Core Part InstancePart Instance A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.

• type: MUST
• topic: Semantics
• automisable: true
• assessment:
  • Inspection
  • Observation
  • Self-Assessment
  • Inquiry
  • Confirmation
  • Recalculation
  • Reperformance
  • Analytical
  • Procedures

Requirement

Actors who are identified or identify themselves as a Dismantling Facility / Authorized Treatment Facility or as a Shredding Facility MUST apply the SerialPart 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). and provide data on the included mandatory data attributes as specified in CX-0127.

Proof of Conformity

N/A

Additional Information

N/A

CX-XXXX-CAC-011 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). SingleLevelBomAsBuilt of CX-0127 Industry Core Part InstancePart Instance A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.

• type: MUST
• topic: Semantics
• automisable: true
• assessment:
  • Inspection
  • Observation
  • Self-Assessment
  • Inquiry
  • Confirmation
  • Recalculation
  • Reperformance
  • Analytical
  • Procedures

Requirement

Actors who are identified or identify themselves as a Dismantling Facility / Authorized Treatment Facility or as a Shredding Facility MUST apply the SingleLevelBomAsBuilt 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). and provide data on the included mandatory data attributes as specified in CX-0127.

Proof of Conformity

N/A

Additional Information

N/A

Legal

Copyright © 2026 Catena-X Automotive Network e.V. All rights reserved. For more information, please see Catena-X Copyright Notice.