Changelog

Summary of Release Jupiter (Preview)

• 13 new standards
• 35 updated standards
• 67 deprecated standards

---

• 3 new non-functional requirements

A) List of new and updated standards

Note: Be aware that more information regarding the changes can be found within the standard documents within the section "COMPARISON WITH THE PREVIOUS VERSION OF THE STANDARD"

Sovereign Data Exchange & Semantics

CX-Nr.	Standard Name	Version	Management Summary
CX-0002	Digital Twins in Catena-X	2.2	Remove all normative references to the EDC implementation. Declare outdated typization mechanism (asset:prop:type) optional
CX-0018	Dataspace Connectivity	3.1	Adopt pinned versions of IATP, DSP, policy definitions. Specify HTTPS and AmazonS3 transfer processes
CX-0067	Ontology Models in Catena-X	1.1	New subchapters Digital Twin and Ontologies, Taxonomy, Asset Content Description, Modeling of the Functions have been added. Text, images and code snippets have been modified to make them easier to understand.
CX-0084	Federated Queries In Data Spaces	1.2	External links have been changed to improve readability. The examples have been updated to reflect recent developments. The the Asset Content Description subsection has been added. Code snippets and text updates in Agent-Related EDC Assets
CX-0126	Industry Core: Part Type	2.0	Added new content in Section 2.1.3 New paragraph "Conventions for Use Case Policy in context data exchange" Notes for versioning Changes in specific AssetIds of Digital Twins in Section 2.1.4: removed assetLifeCyclePhase digitalTwinType is now mandatory (before it was optional) Replaced standardized aspect model in Section 3.1: removed PartAsPlanned 2.0.0 replaced with newly standardized PartTypeInformation 1.0.0 (see link to changelog in section of the aspect model) New version of aspect model in Section 3.2: SingleLevelBomAsPlanned 3.0.0 (see link to changelog in section of the aspect model) Newly standardized aspect model in Section 3.3: SingleLevelUsageAsPlanned 2.0.0 (see link to changelog in section of the aspect model) Added Unique ID Push Notification API in Section 4.1 as content of the industry core deleted "Every certified business application relying on aspects models of this standard MUST be able to consume data conformant to the semantic models specified in this document." from Section 3
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.	2.0	New versions of aspect models in Section 3 SerialPart 3.0.0 (see link to changelog in section of the aspect model) Batch 3.0.0 (see link to changelog in section of the aspect model) JustInSequencePart 3.0.0 (see link to changelog in section of the aspect model) SingleLevelBomAsBuilt 3.0.0 (see link to changelog in section of the aspect model) Newly standardized aspect models in Section 3 SingleLevelUsageAsBuilt 3.0.0 (see link to changelog in section of the aspect model) Aspect model JustInSequencePart now MUST be provided when creating a digital twin for a Just-In-Seuqence-Part (was optional before) in Section 2.1.2 Changes in specificAssetIds of Digital Twins in Section 2.1.4 Removed assetLifeCyclePhase DigitalTwinType is now mandatory (before it was optional) Added intrinsicId specifically for Digital Twins for serialized parts, batches and just-in-sequence-parts Removed partInstanceId from Digital Twins for batches and just-in-sequence-parts Added Unique ID Push Notification API in Section 4.1 as content of industry core New paragraph "Conventions for Use Case Policy in context data exchange" in Section 2.1.3 Added notes for versioning in Section 2.1.3 Deleted "Every certified business application relying on aspects models of this standard MUST be able to consume data conformant to the semantic models specified in this document." from Section 3

Business Partner Data Management

CX-Nr.	Standard Name	Version	Management Summary
CX-0012	Business Partner Data Pool APIAPI An API is a way for two or more computer programs to communicate with each other.	4.0	changed and added the detailed asset structure removed classification sub-object added "is Catena-X Member data" attribute removed "api/catena/" from the endpoint definitions added data sovereignty chapters as additional requirements fix changelog controller endpoint for business-partners to match the reference implementation
CX-0074	Business Partner Gate APIAPI An API is a way for two or more computer programs to communicate with each other.	3.0	Changed and added the detailed asset structure removed classification sub-object removed business partner state and introduced separate states at representation classes removed "api/catena/" from the endpoint definitions added data sovereignty chapters as additional requirements
CX-0076	Golden Record End to End Requirements Standard	1.2	Adjustment of Table 2 in chapter 2.1.9 Golden Record Output Requirements]. Adding Tax Jurisdiction Code Adjustment in chapter 2.1.11 Confidence Level Adjust text for validation interval District and Region is now mandatory for Romania as listed in Table 2
CX-0077	Data Quality Dashboard	1.2	Corrected 2.3.3 - country list Added chapter 3.5 Data Types and 3.6 Data Attributes Added chapter 3.7 for data sovereignty as additional requirement
CX-0078	Bank Data Verification Dashboard	1.2	Corrected 2.3. - country list Added chapter 3.4 Data Types and 3.5 Data Attributes Added chapter 3.6 for data sovereignty as additional requirement Corrected 2.3. - Enhanced usage policies of BDV API
CX-0079	Natural Person Screening Dashboard	1.2	Natural Person Screening Dashboard v1.2 Corrected 2.3 - country list Added chapter 3.6 Data Types and 3.7 Data Attributes Added chapter 3.8 for data sovereignty as additional requirement
CX-0080	BPDM Fraud Prevention Service	1.1	Added chapter 2.6 Data Types and 2.8 Data Attributes. Added chapter 2.7 for data sovereignty as additional requirement.
CX-0081	BPDM Country Risk	2.2	Update on data asset and added new context for Country Risk Added new section for Additional Requirements Affected chapters are 2.2.3 Data Asset Structure & 2.2.5 Additional Requirements
CX-0116	Sanction Watchlist Dashboard	1.2	Corrected 2.3 - country list Added chapter 3.4 Data Types and 3.5 Data Attributes Added chapter 3.6 for data sovereignty as additional requirement
CX-0135	Company Certificate Management	2.0	Added a new attribute 'status' to the data model (1.5.11 Status) Added new certificate types (1.5.2 TYPE)

Identity Management

CX-Nr.	Standard Name	Version	Management Summary
CX-0013	Identity of Member Companies	2.0	Deprecation of the Summary Credential.
CX-0049	DID Document Schema	2.0	Re-definition of the structure of the did-document.
CX-0050	Framework Agreement Credential	2.1	No Use Case-specific Framework Agreement Credentials anymore. Re-definition of the Framework Agreement structure.
CX-0149	Verified Company Identity	1.0	This document combines the previous standards CX - 0016 Company Attribute Verification v.1.1.0 and CX - 0017 Company Role by the Connector v.1.0.1 including all needed information for the identification of a participant and the Dataspace clients acting on behalf of them Introducing the Identity and Trust Protocol (IATP) used within the identity presentation flow Introducing an API specification for the Creation of Participants Wallet as a foundation for the usage of multiple Wallet providers.

Onboarding

CX-Nr.	Standard Name	Version	Management Summary
CX-0006	Registration and Initial Onboarding	2.0	Updated following chapters: 2.3.4 Company Data Validation 2.3.8 Gaia-X And added: 2.3.5 Business Partner Number Creation 2.3.6 Wallet Tenant Creation Credential Storage Registration Approval and Dataspace Access
CX-0009	CX Registration APIAPI An API is a way for two or more computer programs to communicate with each other.	2.0	Update of the endpoint details which MUST/SHOULD get followed by the Core Service Provider and/or Onboarding service provider. Endpoint path as well as request/response body.

Data Chain Management

CX-Nr.	Standard Name	Version	Management Summary
CX-0005	Item Relationship Service APIAPI An API is a way for two or more computer programs to communicate with each other.	2.1	Adoption of the industry core standards (CX-0126 and CX-0127) Update of optional endpoints
CX-0045	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 Chain Template	1.3	Adoption of the industry core standards (CX-0126 and CX-0127) Update of the template from BAMM to SAMM
CX-0055	Data Processing Patterns for IT System Integration	1.2	New data processing patterns for IT system integration have been added.
CX-0139	Information as a Service – External Data Provider	1.0	The Scope of this Standard is to enable Third-Party Information Provider to deliver Data from outside Catena-X inside Catena-X. This Standard is generic to every Use Case and qualifies Information aaS Provider as a potential Data Provider for a Use Case defined Business Application. The Data can be delivered only to a specific Use Case within Catena-X, realised in an certified Business Application. By this way the Standard enables Third-Party Information Provider to deliver Data from outside Catena-X inside Catena-X and at the same time limits Data Delivery to existing Use Cases, avoiding Violations or Bypasses of existing Standards and Regulations within Catena-X.

Resiliency

CX-Nr.	Standard Name	Version	Management Summary
CX-0115	Manufacturing Capability Exchange	1.0	Manufacturing-as-a-Service (MaaS) scenarios focus on connecting buyers looking for manufacturers in possession of the available production know-how and resources to produce specific products. The standard makes use of the newly introduced all-in-one use-case template. The Manufacturing Capability data model is being expanded to include the entities Machine, Tool, and Material, along with their corresponding properties. Additionally, an APIAPI An API is a way for two or more computer programs to communicate with each other. is defined, so that these Manufacturing Capabilities can be exchanged in a standardized way. Note: The CX-0115 standard obsoletes CX-0052 Manufacturing Capability Aspect Mode l v1.0.0
CX-0118	Delivery Information Exchange	2.0	Changes: integration and usage of digital twins as defined in CX-0002 Digital Twins in Catena-X harmonization of aspect model in accordance with CX-0126 Industry Core: Part Type discontinuation of the proprietary API used in v1.0.0 of this standard grammatical, spelling and semantic improvements New Content: added a note on the obligation of standard implementers to make aware that sensitive data is being handled, see Chapter 2.1.3.
CX-0120	Short-Term Material Demand Exchange	2.0	Changes: integration and usage of digital twins as defined in CX-0002 Digital Twins in Catena-X harmonization of aspect model in accordance with CX-0126 Industry Core: Part Type new specific submodel io.catenax.short_term_material_demand:1.0.0:ShortTermMaterialDemand from io.catenax.material_demand:1.0.0:MaterialDemand discontinuation of the proprietary API used in v1.0.0 of this standard grammatical, spelling and semantic improvements New Content: added a note on the obligation of standard implementers to make aware that sensitive data is being handled, see Chapter 2.1.3
CX-0121	Planned Production Output Exchange	2.0	Changes: integration and usage of digital twins as defined in CX-0002 Digital Twins in Catena-X harmonization of aspect model in accordance with CX-0126 Industry Core: Part Type discontinuation of the proprietary API used in v1.0.0 of this standard grammatical, spelling and semantic improvements New Content: added a note on the obligation of standard implementers to make aware that sensitive data is being handled, see Chapter 2.1.3
CX-0122	Item Stock Exchange	2.0	Changes: integration and usage of digital twins as defined in CX-0002 Digital Twins in Catena-X harmonization of aspect model in accordance with CX-0126 Industry Core: Part Type discontinuation of the proprietary API used in v1.0.0 of this standard grammatical, spelling and semantic improvements New Content: added a note on the obligation of standard implementers to make aware that sensitive data is being handled, see Chapter 2.1.3
CX-0128	Demand and Capacity Management Data Exchange	2.0	Replaced MaterialDemand with WeekBasedMaterialDemand aspect model Added deactivation of WeekBasedCapacityGroup to Section 4.2.2.2 Added deactivation of WeekBasedMaterialDemand to Section 4.1.2.2 Added Chapter 2.3 Additional Requirements Added Chapter 5.10 Supply Chain Disruption Notifications Added Chapter 5.11 Demand Volatility Metrics Added Agreed Capacity to Section 5.6.1 Added Repositories to Annexes Updated References in Chapter 7 Updated WeekBasedCapacityGroup aspect model Updated WeekBasedMaterialDemand aspect model Updated MessageHeaderAspect version in Chapter 4 Updated Policies in Chapter 6 Updated choice of words and writing pattern throughout this standard
CX-0129	Request-for-Quotation Exchange	2.0	In this version of the standard, the processes entity of the RequestForQuotation semantic model has been replaced by the "Bill of Process" data model (cf. Chapter 3.2)
CX-0133	Online Control and Simulation	2.0	Updated references to new versions Providers must ensure BPNL provisioning to OSim
CX-0142	Shop-Floor-Information-Service	1.0	The current version of the standard provides two different kinds of data: Production Forecasting, and Production Tracking data. To give an example of forecasting data, suppose a customerCustomer In the context of OSim, the receiver of produced goods from a supplier. wants to know when production is expected to start. He can use the Shop-Floor-Information-Service in order to get the information either directly, via cyclic messages or via notifications when the calculated production dates change. As an example of production tracking, a customerCustomer In the context of OSim, the receiver of produced goods from a supplier. can request certain production attributes collected during production, such as the torque of a particular process step. This data can then be used for both documentation and tracking. Note: This standard Merges CX-0068, CX-0069 and CX0075 by combining the different standards that describe the data model, the API and and the process into this combined standard. Additional functionality added: production tracking aspects. Update of Production Forecast Models due to update of CX-header.
CX-0145	Days of supply Exchange	1.0	Days of Supply (DoS) in logistics is a critical metric used to estimate how long current inventory levels will last under normal consumption patterns. This calculation is essential in supply chain management as it assists in forecasting when stock replenishment is needed, thereby preventing stock shortages or overstocking. It plays a significant role in ensuring efficient inventory turnover, maintaining a balance between having enough stock to meet demand and avoiding excess inventory that ties up capital. To effectively address the challenges associated with manual calculation and estimation of Days of Supply, the standardization and interoperable exchange of this data among Catena-X business partners is essential. Establishing a standardized semantic definition to describe Days of Supply and a common APIAPI An API is a way for two or more computer programs to communicate with each other. is a fundamental step to enable this exchange and foster compatibility. This approach maximizes the range of solutions available to mitigate potential supply shortages and supports precise inventory planning.
CX-0146	Supply Chain Disruption Notifications	1.0	The Catena-X Supply Chain Disruption Notifications Standard is created for all members of the automotive supply chain. The aim is to have a functionality to easily and quickly inform the affected supply chain partners in case of supply chain disruptions at some point in the value chain. Having this information is key to be able to take the right countermeasures and make the whole value chain more resilient. Recent incidents (e.g. semi-conductor-crisis or COVID pandemic) have demonstrated the requirement for such a fast standardized process among all partners.

PLM and Quality

CX-Nr.	Standard Name	Version	Management Summary
CX-0059	Behavioral Twin Endurance Estimator Use Case	2.0	This standard upgrades the triangle (previously CX-0059:1.2) to an Use Case Standard and consolidates the contents of the previously independent standards CX-0056, CX-0057 and CX-0058 within a single comprehensive standard.
CX-0105	AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. Tracking Use Case	1.1	This standard upgrades the triangle (previously CX-0105:1.0) to an Use Case Standard and consolidates the contents of the previously independent standards CX-0070, CX-0083, CX-0004 and CX-0106 within a single comprehensive standard. Note: No content relevant to the certification has been changed.
CX-0123	Quality Use Case Standard	2.0	Update semantic models QualityTask, PartsAnalyses, ManufacturedPartsQualityInformation, Fleet.DiagnosticData, Fleet.ClaimData Update model Fleet.Vehicles and integrate model Vehicle.ProductDescription New semantic models Early Warning Norification and Failure Pattern Update 2.1 Data Sharing Rules Define Notification Process and API
CX-0125	Traceability Use Case	2.0	Redundancies to the standard CX-0127 in all relevant chapters removed: Submodel SerialPart, Submodel Batch, Submodel SingleLevelBoMAsBuilt Adapted parts (introductions, examples) of the standard document contents to suit the use case specifications Quality Alerts are set to mandatory New paragraph "Conventions for Use Case Policy in context data exchange" in Section 2.1.3 Added notes for versioning in Section 2.1.3 Deleted "Every certified business application relying on aspects models of this standard MUST be able to consume data conformant to the semantic models specified in this document." from Section 3 Deleted old references in Section 6.1
CX-0138	Use Case Behaviour Twin Endurance Estimator	1.0	The 1.0 version changed from a triangle (originally CX-0089) to an Use Case Standard and consolidates the contents of the previously independent standards CX-0057, CX-0088, CX-0090 within a single comprehensive standard.
CX-0141	Health Indicator Use Case	1.0	This standard focuses on the Health Indicator Use Case. The Health Indicator recieves dynamic input data, that has been recorded in the vehicle, through the Catena-X network. The input data, combined with additional product knowledge by the service provider, is used to calculate precise health indicator values for specific components

Sustainability

CX-Nr.	Standard Name	Version	Management Summary
CX-0117	Use Case Circular Economy - Secondary Marketplace	1.0	CX-0117 Use Case Circular Economy - Secondary Marketplace v1.0.0 is a new standard which is based on the deprecated CX-0100 Triangle for Secondary Marketplace v.1.0.0 standard. The data models from: CX-0033 Data Model ReturnRequest (deprecated) CX-0034 Data Model Battery Pass (deprecated) CX-0035 Data Model Marketplaceoffer (deprecated)have been included with their newest released versions to assure consistency between standards.
CX-0131	Circularity Core	1.1	Adoption of the industry core standards (CX-0126 and CX-0127) Additionally, CX-0131 merges (and, thus, obsoletes) the following 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).: CX-0036: Aspect Model: QualityTask CX-0037: Aspect Model: Vehicle.ProductionData CX-0038: Aspect Model: Fleet.DiagnosticData CX-0039: Aspect Model: Fleet.ClaimData CX-0040: Aspect Model: PartAnalyses CX-0041: Aspect Model: ManufacturedPartsQualityInformation CX-0091: Aspect Model: Fleet.Vehicles CX-0092: Aspect Model: QualityTaskAttachment CX-0107: Aspect Model: Reuse Certificate  CX-0109: Aspect Model: Refrubishing Certificate CX-0111: Aspect Model: Remanufacturing Certificate CX-0147: Aspect Modelt Non-ReusableParts CX-0148: Aspect Model Repair Certificate
CX-0136	Use Case PCF	2.0	This standard focuses on the PCF (Product Carbon Footprint) exchange use case. This includes relevant requirements for: data provider, that want to provide PCF data through Catena-X, data consumer, that are want to consume PCF values in Catena-X and application developer/ provider supporting the provisioning and consuming of PCF values. It will provide information about the used core components as well as the structure of the Digital Twin Registry entry, the data model exchanged and the EDC (Eclipse Dataspace Connector) data structure. Additionally in v2.0 next to the APIsAPI An API is a way for two or more computer programs to communicate with each other. 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). urn:samm:io.catenax.pcf:6.0.0 has been updated to urn:samm:io.catenax.pcf:7.0.0.
CX-0143	Use Case Circular Economy - Digital Product Passport Standard	1.0	This standard focuses on the digital product passport use case. This includes relevant requirements for data provider, that want to provide different passports through Catena-X, data consumer, that are searching for different passports in Catena-X, and application developer / provider supporting the provisioning and consuming of passport data. Specific passports that shall be mentioned here are the battery passport and the transmission passport, which are first realizations of product passports in Catena-X.
CX-0144	ESS Use Case Standard	1.0	Catena-X aims to support supply chain due diligence obligations in a market environment that miss full up- and downstream transparency. This is argued to be relevant for Environmental and Social Standards (ESS) incident tracking, without compromising GAIA-X and Catena-X principles like data sovereignty, interoperability, standardization, and use of federated services. In case a violation against these laws occurs, an ESS incident can be created and transmitted to the Catena-X network. The Catena-X network and the ESS use case standard support the Catena-X members in this process. Note: The ESS incident 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)., which was described in CX-0113, has been integrated into this document.

B) List of new / updated non-functional requirements

Name	Version	Description
PCF-Rulebook	v3.0	To reduce the room for interpretation, Catena-X developed this Product Carbon Footprint Rulebook with a focus on the exchange of production carbon footprints from tier to tier with increased consistency for PCF accounting. This increased consistency will ensure comparability for the PCFs of parts and components and allow for part and supplierSupplier In the context of OSim, the producer of goods. selection. Consequently, the Catena-X Rulebook focusses on the production stage of vehicles.
PCF-Verification Framework v1.0	v1.0	The scope of this document is to provide guidelines for the verification of the product carbon footprint according to the PCF rulebooks. The document is applicable to all companies and suppliersSupplier In the context of OSim, the producer of goods. in the automotive and chemical supply chains or all those outside the aforementioned industries who opt to report according to those PCF rulebooks. The framework covers the entire certification process for PCF programs and the verification process of PCF datasets, including the planning, execution, and creation of the verification report and the verification statement.
ESS Code of Conduct (EN | DE)	v1.0	In the Catena-X use case sustainability / environmental and social standards, principles are established with the aim of establishing transparent and trustworthy practices within the Catena-X network.

C) List of deprecated standards

CX-Nr.	Standard Name	Reason to depricate
CX-0019	SerialPart	Merged by 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.
CX-0020	Batch	Merged by 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.
CX-0021	SingleLevelBoMAsBuilt	Merged by 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.
CX-0042	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). - SinglelevelBomAsPlanned	Merged by CX-0126 Industry Core Part Type
CX-0043	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). - PartAsPlanned	Merged by CX-0126 Industry Core Part Type
CX-0022	Notification APIAPI An API is a way for two or more computer programs to communicate with each other.	Merged by CX-0125 Traceability Use Case
CX-0023	Notification Process	Merged by CX-0125 Traceability Use Case
CX-0060	Tracebility BomAsBuild Triangle	Merged by CX-0125 Traceability Use Case
CX-0036	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).: QualityTask	Merged by CX-0131 Circularity Core and CX-0123 Quality Use Case Standards
CX-0037	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).: Vehicle.ProductionData	Merged by CX-0131 Circularity Core
CX-0038	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).: Fleet.DiagnosticData	Merged by CX-0131 Circularity Core and CX-0123 Quality Use Case Standards
CX-0039	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).: Fleet.ClaimData	Merged by CX-0131 Circularity Core and CX-0123 Quality Use Case Standards
CX-0040	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).: PartAnalyses	Merged by CX-0131 Circularity Core and CX-0123 Quality Use Case Standards
CX-0041	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).: ManufacturedPartsQualityInformation	Merged by CX-0131 Circularity Core
CX-0065	Triangle for Dismantling Service	Merged by CX-0131 Circularity Core
CX-0066	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).: End of Life of Vehicle Compliance	Merged by CX-0131 Circularity Core
CX-0071	Triangle Quality Early Warning Field and Root Cause	Merged by CX-0123 Quality Use Case Standards
CX-0091	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).: Fleet.Vehicles	Merged by CX-0131 Circularity Core and CX-0123 Quality Use Case Standards
CX-0092	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).: QualityTaskAttachment	Merged by CX-0131 Circularity and CX-0123 Quality Use Case Standards Core
CX-0098	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).: Secondary Material Content	Merged by CX-0131 Circularity Core
CX-0099	Data Model: Certificate of Decommissioning	Merged by CX-0131 Circularity Core
CX-0107	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).: Reuse Certificate	Merged by CX-0131 Circularity Core
CX-0108	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).: Waste Certificate	Merged by CX-0131 Circularity Core
CX-0109	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).: Refrubishing Certificate	Merged by CX-0131 Circularity Core
CX-0111	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).: Remanufacturing Certificate	Merged by CX-0131 Circularity Core
CX-0112	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 Recycling Certificate	Merged by CX-0131 Circularity Core
CX-0033	Data Model ReturnRequest	Merged into CX-0117 Use Case Circular Economy - Secondary Marketplace
CX-0035	Data Model Marketplaceoffer	Merged into CX-0117 Use Case Circular Economy - Secondary Marketplace
CX-0057	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). for user estimated loading	Merged into CX-0059 and CX-0138 Use Case Behaviour Twin Endurance Estimator
CX-0056	Semantic Model: Classified Load Spectrum	Merged into CX-0059 Use Case Behaviour Twin Endurance Predictor
CX-0058	APIAPI An API is a way for two or more computer programs to communicate with each other.: Endurance Predictor	Merged into CX-0059 Use Case Behaviour Twin Endurance Predictor
CX-0088	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). for Remaining Useful Life data	Merged into CX-0138 Use Case Behaviour Twin Endurance Estimator Digital Product Pass
CX-0090	APIAPI An API is a way for two or more computer programs to communicate with each other. Endurance Estimator	Merged into CX-0138 Use Case Behaviour Twin Endurance Estimator
CX-0089	Triangle Behavioral Twin Endurance Estimator Service	Merged into CX-0138 Use Case Behaviour Twin Endurance Estimator Digital Product Pass
CX-0026	PCF Data Model	Merged into CX-0136 Use Case PCF
CX-0027	Product Carbon Footprint 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).	Merged into CX-0136 Use Case PCF
CX-0028	PCF Request APIAPI An API is a way for two or more computer programs to communicate with each other.	Merged into CX-0136 Use Case PCF
CX-0134	PCF Calculation Integration	Merged into CX-0143 Use Case PCF
CX-0063	PCF Triangle	Merged into CX-0136 Use Case PCF
CX-0052	Manufacturing Capability 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).	Merged into CX-0115 Manufacturing Capability Exchange
CX-0100	Triangle for Secondary Marketplace	Merged into CX-0117 Use Case Circular Economy - Secondary Marketplace
CX-0016	Company Attribute Verification	Merged into CX-0149 Verified Company Identity
CX-0017	Company Role by the Connector	Merged into CX-0149 Verified Company Identity
CX-0051	Summary Credentials	Deprecated with the introduction of IATP (see CX-0018 and CX-0149)
CX-0061	Triangle Traceability Data Provisioning Digital Twin As Planned	Merged into CX-0125 Traceability Use Case
CX-0062	Traceability Notifications Triangle	Merged into CX-0125 Verified Company Identity
CX-0093	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). Traction Battery Code	Merged into CX-0125 Verified Company Identity
CX-0070	AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. Tracking Platform APIAPI An API is a way for two or more computer programs to communicate with each other. Standardization	Merged into CX-105 AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. Tracking Use Case Identity
CX-0083	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). IotSensorDeviceDefinition	Merged into CX-105 AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. Tracking Use Case Identity
CX-0104	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). AssetTrackerLinks v1.0.0	Merged into CX-105 AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. Tracking Use Case Identity
CX-0106	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). IotSensorData	Merged into CX-105 AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. Tracking Use Case Identity
CX-0096	Triangle For Digital Product Pass	Merged into CX-0143 Use Case Circular Economy - Digital Product Passport Standard
CX-0034	Data Model Battery Pass	Merged into CX-0143 Use Case Circular Economy - Digital Product Passport Standard
CX-0095	Data Model: Transmission Pass	Merged into CX-0143 Use Case Circular Economy - Digital Product Passport Standard
CX-0103	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). Digital Product Passport	Merged into CX-0143 Use Case Circular Economy - Digital Product Passport Standard
CX-0068	MP Shop Floor Information Service APIAPI An API is a way for two or more computer programs to communicate with each other.	Merged into CX-0142 Shop Floor Information Service
CX-0069	Shop-Floor-Information-Service 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).	Merged into CX-0142 Shop Floor Information Service
CX-0075	Shop-Floor-Information-Service Process	Merged into CX-0142 Shop Floor Information Service
CX-0113	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). ESS Incident Data Model	Merged into CX-0144 Shop Floor Information Service
CX-0072	OSim Process & Core Business Logic	Merged into CX-0133 Online Control and Simulation
CX-0073	OSim APIAPI An API is a way for two or more computer programs to communicate with each other.	Merged into CX-0133 Online Control and Simulation
CX-0087	OSim Data Model: Materialflow Simulation Result	Merged into CX-0133 Online Control and Simulation
CX-0085	Product Stock 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).	Merged into CX-0133 Online Control and Simulation
CX-0086	Product Stock Exchange APIAPI An API is a way for two or more computer programs to communicate with each other.	Merged into CX-0133 Online Control and Simulation
CX-0046	Demand and Capacity Management Process and Core Business Logic	Merged into CX-0128 Demand and Capacity Data Exchange
CX-0047	Demand and Capacity Management Data Model Material Demand and Capacity Group	Merged into CX-0128 Demand and Capacity Data Exchange
CX-0048	Demand and Capacity Management APIAPI An API is a way for two or more computer programs to communicate with each other. Material Demand and Capacity Group	Merged into CX-0128 Demand and Capacity Data Exchange