Skip to main content

4 posts tagged with "release"

View All Tags

CX-Titan

· 15 min read

Catena-X Standards

With the CX-Titan release, several Catena-X standards have been updated and new standards have been introduced across multiple domains. Updates focus on refining existing specifications, while newly introduced standards extend the ecosystem with additional use cases and capabilities.

Engineering

The Engineering domain has been extended with new standards that strengthen requirements management and software transparency across the ecosystem.

StandardStatus
CX-0158 Car SBOMAdded

Industry Core

The Industry Core standards continue to evolve to support the core digital twin concepts and foundational capabilities of the Catena-X ecosystem.

StandardStatus
CX-0002 Digital Twins in Catena-XUpdated
CX-0151 Industry Core: BasicsUpdated

Network Service

Updates in the Network Services domain improve onboarding, identity management, and connectivity mechanisms within the Catena-X dataspace. A new standard introduces additional capabilities for identity verification.

StandardStatus
CX-0001 Participant Agent RegistrationUpdated
CX-0006 Registration and Initial OnboardingUpdated
CX-0018 Dataspace ConnectivityUpdated
CX-0049 DID DocumentUpdated
CX-0050 CX-Specific CredentialsUpdated
CX-0135 Business Partner Company Certificate ManagementUpdated
CX-NFR-IdP Identity ProofingAdded

Supply Chain and Quality

The Supply Chain & Quality domain introduces new functionality while updating several existing standards to further support data exchange across operational supply chain processes.

StandardStatus
CX-0123 Quality Use CaseUpdated
CX-0125 Traceability Use CaseUpdated
CX-0128 Demand and Capacity Management Data ExchangeUpdated
CX-0150 Logistics Use CaseUpdated
CX-0153 Tariffs Use CaseUpdated
CX-0156 GeometryUpdated
CX-0157 PURISAdded

Sustainability

The Sustainability domain continues to expand with additional standards supporting transparency and circular economy initiatives.

StandardStatus
CX-0143 Use Case Circular Economy – Digital Product PassportUpdated
CX-0159 Material AccountingAdded

Semantic Modelling

The semantic modelling foundation of Catena-X has been further refined with an update to the core modelling framework.

StandardStatus
CX-0003 SAMM Aspect Meta ModelUpdated

Further Information

Details can be found in the changelog

To view the Titan version of the Standards, please refer to the Overview Page of the standards and select CX-Titan.


Catena-X Operating Model

With the release of version 3.1.1, the Operating Model introduces improvements to clarity and consistency across governance, roles, lifecycle management, and service descriptions. The update mainly includes minor refinements, such as clearer terminology, alignment with normative specification language, and the removal of outdated or misleading references

Why: Introduction

References to the former Whitepaper have been removed. The Library is now the primary reference source for Catena-X documentation.

Why: Understanding the Catena-X Data Space

The diagram Catena-X Ecosystem has been updated. The relationship between the Association and Tractus-X has been clarified. The diagram now correctly states that the Association “sponsors, promotes, and coordinates” Tractus-X rather than governing it.

Who: Roles in the Catena-X ecosystem

Normative Terminology

The roles defined in the Operating Model have been updated to align with the terminology used in Catena-X standards. Normative language (MUST, SHOULD, MAY) is now consistently applied to express requirements and recommendations. These adjustments clarify the wording and ensure alignment without introducing changes to the underlying governance structure or role responsibilities. In addition, a reference table has been added to explain the meaning and usage of the terms MUST, SHOULD, and MAY, supporting a consistent interpretation across the Operating Model.

Enablement Service Provider (ESP)

Clarification has been added for Enablement Service Providers (ESPs) regarding the listing of enablement services on the marketplace. ESPs MUST list standalone enablement services on the marketplace. Enablement services that are bundled with other offerings MAY be provided without being listed separately on the marketplace.

Attestation Provider (AtP)

Clarified that details on AtP roles and qualification requirements are defined in domain-specific normative documents such as rulebooks. The documentation now also references the official list of accredited AtPs published by the Association.

Digital Clearing House (DCH)

The description of the Digital Clearing House role has been simplified to improve clarity.

Data Provider and Consumer (DPC)

Removed the requirement that forced Consumers and Providers to demonstrate value creation through data exchange, as this cannot be verified and is inherent to the concept of a dataspace.

Diagrams and Role Relationships

Added the missing label to the arrow Sandbox Provider → Association to ensure all relationship arrows are consistently labeled and the diagram remains clear and coherent.

What: Service Map

The Policy Hub has been removed from Core Services A because no standard currently exists for this service.

How: Life Cycle Management

The term “breaking change” has been removed from the operating model. The lifecycle documentation now explicitly aligns with the 1+1 principle, meaning that old and new versions must coexist and no change should disrupt the operation of the dataspace. Furthermore specific dates were removed from the release schedule to make the structure reusable and easier to maintain.

Documentation Simplification

The modular system diagrams have been removed from the Operating Model documentation. The modular system is now published and maintained within the official standards documentation. The Operating Model continues to define the governance framework describing how the modular system is created, maintained, and governed, while the authoritative content is hosted externally in the standards documentation.

Further Information

Details can be found in the changelog

To view the Titan version of the Operating Model, please refer to the Operating Model documentation and select CX-Titan.


Tractus-X reference implementations

The CX-Titan release combines the Eclipse Tractus-X releases 25.12 and 26.03.

Community Contribution

As with all Tractus-X releases, Titan was made possible through the contributions of a broad community of developers, architects, documentation authors, and reviewers across the Eclipse Tractus-X project. The combined releases include contributions from over 50 contributors and more than 25 committers, reflecting the collaborative nature of the project.

We would like to sincerely thank the community for their outstanding collaboration. Contributors from many organizations worked together. We highly appreciate everyone’s contributions and look forward to continuing this journey together with the community.

Committer

matbmoser CDiezRodriguez lgblaumeiser stephanbcbauer nicoprow AndrYurk SujitMBRDI typecastcloud bmg13 mgarciaLKS ClosedSourcerer ther3sa tom-rm-meyer-ISST rafaelmag110 tomaszbarwicki saadanzari agg3fe dhiren-singh-007 manojava-gk rogocof Phil91 ds-jhartmann paullatzelsperger nitin-vavdiya evegufy almadigabor mhellmeier saudkhan116 maximilianong ndr-brt ntruchsess florianrusch

Contributor

AYaoZhan jSchuetz88 shijinrajbosch jalvaro-lks bosserf sm29105 Alaitz1 pjuaristi-ikerlan tfjanjua MDSBarbosa ds-asmierzchalski anneramsauer JordanGerada3 Grand-Thibault OlgaIvkovic MonikaJacobsen adkumar1 JulianSchererZF kkotowiczz hokonohara borjakhet leandro-cavalcante Akash-IAV marcelruland manourym sb3nz Usmanfee stanfaldin zygokaktus zanpi8020 th0masgl wehrstedt-jan LukasSchmetz kunyao-cofinity-x tobzahn SanaSalem01 kss682 hkny thomas-henn M-Busk Kuehner-A

Highlights

These are just a few highlights from the 25.12 and 26.03 releases.

KIT 2.0 Architecture

A major redesign of how the KIT ecosystem is visualized and structured has been introduced. The KIT 2.0 Architecture provides a clearer layered representation of the Eclipse Tractus-X ecosystem, improving discoverability and navigation across the growing collection of KITs.

For further information, please refer to the following link.

Golden Record Business Partner Number (BPN) Service

Enhancements improve the reliability and governance of shared business partner data. Immutable history for management relations protects historical accuracy, while automated confidence calculations and contributor metrics increase transparency and trust in Golden Records. Support for relation validity periods allows more accurate modeling of changing business relationships.

Industry Core Hub

New capabilities enhance digital twin and digital product passport management. Improved submodel handling, EcoPass and DPP support, and Notification API integration enable more efficient data exchange and event-driven communication between ecosystem services. Security and architecture improvements further strengthen platform stability.

Tractus-X SDK

SDK updates improve developer experience and ecosystem interoperability. Notification services, alignment with the latest EDC and DSP standards, improved documentation, and security updates simplify the development of Tractus-X compatible applications.

Tractus-X Connector

Connector improvements strengthen the core data exchange infrastructure. Enhanced discovery mechanisms, credential caching, and preparation for multi-tenant architectures improve scalability, performance, and interoperability across dataspace participants.

Identity Hub

Identity Hub enhancements improve decentralized identity and credential management in the ecosystem. Configurable integration options, improved documentation, and demonstration flows simplify the implementation of credential issuance and verification processes.

Further Information

Details can be found in the changelog


General Website improvements

The CX-Titan release introduces several enhancements to the Catena-X website, aimed at improving navigation, usability, and accessibility of information for all ecosystem participants. These updates make the website more intuitive, informative, and aligned with the evolving needs of the Catena-X community.

The main navigation was updated to clearly separate normative and non-normative content, making it easier to find official specifications versus supporting information.

New Knowledge Resources

  • Glossary: Provides standardized definitions for key terms used across the Catena-X ecosystem.

Non-Functional Requirements

Previously only available on the website, the Certification Framework has now been integrated into the non-functional requirements. This improves clarity on compliance and evaluation expectations for ecosystem participants.

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

CX-Saturn

· 6 min read

Catena-X Standards

  • 4 new standards introduced, expanding the foundation for digital engineering master data, requirements exchange, tariffs, and policy constraints (CX-0154, CX-0155, CX-0153, CX-0152)

  • 15 standards updated to further improve quality, interoperability, and usability

  • Improved processes for supply chain disruption and traceability, supporting more robust risk management and transparency (CX-0146, CX-0125)

  • Enhanced APIs and data models for product carbon footprint, quality management, and circular economy, enabling more efficient and reliable data exchange (CX-0136, CX-0123, CX-0143)

  • Finalized protocols and clearer policy implementation for dataspace connectivity, including update to the final versions of DSP 2025-1 and DCP 1.0, ensuring secure and future-proof integration (CX-0018, CX-0001, CX-0152)

  • Extended support for Digital Twins, including update of AAS interfaces based on Release 25-01 of the Specifications of the Asset Administration Shell (IDTA), strengthening asset management and integration (CX-0002)

  • Improved Business Partner Data Management (BPDM) standards, especially for master data and gate APIs, for better management of business partner data (CX-0012, CX-0074)

  • Updated identity and credential management with new requirements for wallets and verifiable credentials, now supporting "Bring Your Own Wallet" (CX-0149, CX-0049, CX-0050)

  • 1 standard deprecated to consolidate the standards landscape and improve user-friendliness (CX-0013)

Catena-X Operating Model

With the CX-Saturn release, the Operating Model strengthens compliance, clarifies governance rules, enhances lifecycle management, and refreshes the service map. The outlook on Self-Sovereign Identity (SSI) has been realigned, highlighting interoperability and standardization as key priorities.

Roles & Compliance

  • TISAX Requirements
    • TISAX Level 2 becomes mandatory for all OSPs, ESPs, and BAPs effective July 2025, with a 12-month grace period.
    • TISAX Level 3 becomes mandatory for CSP-A and CSP-B roles.
  • Registration
    • Roles including CSP-A, CSP-B, OSP, BAP, AP, and DPC must be registered in the Catena-X data space.
  • New Roles
    • Digital Clearing House: Defined as the trust anchor for onboarding, legal entity verification, and digital self-descriptions, with support for multiple regional DCHs; clarified prerequisites and current limitations.
    • Attestation Provider: Defined as an independent verifier to strengthen trust and assurance within the Catena-X ecosystem.

Governance & Policies

  • Internal systems do not need to be listed on the public marketplace.
  • Reinforced that all data space participants must comply with governance components such as Trust ID and related mechanisms.
  • Removed reference to the deprecated CX-0008 Standard.

Lifecycle Management

  • Introduced an Environments section, including details on the Int environment.

Service Map

  • Updated to reflect the current state of services.
  • Assigned relevant standards to each service.

Strategic Outlook

  • The chapter on “Further Integration of SSI Technologies” was refocused:
    • Shift from purely technical decentralization towards a broader SSI concept.
    • Transition from CSP-provided wallets to a bring-your-own-wallet approach.
    • Enablement of all entities to issue, present, and verify credentials, regardless of role.
    • Increased emphasis on interoperability across data spaces and alignment with global standards.

Further Information

Details can be found in the changelog

Catena-X Regulatory Framework

The latest update to the Catena-X Regulatory Framework includes adjustments to country clearance lists, the addition of a new contracting chapter, and an updated version of the Data Exchange Governance. These changes ensure that regulatory requirements are accurately reflected and consistently applied.

Updates to Country Clearance Lists

  • Ukraine has been added to the Allow List, including additional country information.
  • Mexico has been added to the Allow List.
  • Turkey has been added to the Allow List.

New Chapter

  • Contracting has been introduced as a new chapter in the Regulatory Framework.

Updated Version of Data Exchange Governance

  • A new version of Data Exchange Governance (dated 30 September 2025) has been published.

Further Information

Details can be found in the changelog.

Tractus-X reference implementations

The Saturn release combines the Eclipse Tractus-X releases 25.06 and 25.09.
This ensures a solid baseline of updated components together with new capabilities for data sovereignty, interoperability, and traceability. Non-compatible or other compatible versions of the Tractus-X release or the apps are listed below. If a version is interoperable with the initial release version and those features and with all other listed versions its listed as compatible.

Compatible versions

CX-Jupiter

ComponentVersions
Tractus-X Connector
(Eclipse Dataspace Components Connector)
0.7.7
0.8.0
0.8.1
0.9.0
0.10.0

CX-Saturn

ComponentVersions
Tractus-X Connector
(Eclipse Dataspace Components Connector)
0.11.1 [Latest]
warning

Please ensure that you carefully review the current known knowns, familiarize yourself with the updated policy changes, and adhere to the migration guidelines.

Important: Please be aware that based on the Catena-X standard CX-0018 you MUST use the Tractus-X Connector version 0.11.1 and higher to be compatible.

Non-compatible versions

ComponentVersions
N/AN/A

Further Scope Clarification

To uphold the integrity and reliability of the onboarding process, there will be a temporary change of the standards. This change is in-line with a feature supported in the current reference implementation.

Impact: CSP-B & OSP roles:

  • CX-0006.
    • The standard has been slightly adjusted. Onboarding service providers and core service providers must continue to support the possibility of creating a Self-Description (SD) of the Legal Person. However, this requirement is no longer strictly tied to the initial registration process; the creation of the SD can now occur at a later stage. For any SDs that are issued, they must be stored in a central location and must comply with GAIA-X standards and guidelines.

The functionality of Catena-X and the security framework will remain unaffected furthermore the validation of company data and identifiers will continue as usual.

CX-Io

· 4 min read

Catena-X Standards

  • 2 new standards, completing the set of Catena-X' initial use cases
  • 12 updated standards to ensure quality
  • 1 deprecated standards in the course of consolidation to achieve more user-friendliness
  • updated modular certification framework (see Operating Model)

details to be found here

Catena-X Operating Model

  • updated to version 3.0.5
  • only patch changes e.g. clarification of the Sandbox, update modular System covering the new standards and update glossary etc.

details to be found here

Catena-X Regulatory Framework

  • only patch changes in comparison to CX-Jupiter

details to be found here

Tractus-X reference implementations

A comprehensive, coherent and compatible set of development artefacts. Highlights include:

Portal

  • Enhance the App/Service registration process
    • Reduces necessity of creating multiple services to enable the usage of multiple technical users; leads to more flexibility for the app/service provider
  • Optimization of the Service/App Subscription Process
    • Enhances security and user experience
  • Automatic Setting of the Catena-X Membership Flag
    • Automates the flag-setting process, making onboarding more efficient
  • Integration of the Gaia-X Clearinghouse Interface
    • The new API provides more flexibility from a Gaia-X perspective. The Portal backend must switch to the new API for proper data validation during company onboarding and SD document creation

SSI Credential Issuer

  • Support for Bitstring Status List
    • Ensures compliance with the updated W3C standard.
  • Process Status List API
    • Enables the retriggering of failed process steps to improve stability

EDC

  • Empty Asset Selector
    • Blocks contract definitions with an empty asset selector to prevent erroneous data publication
  • Policy Checks
    • Adds policy validation APIs and validation during policy creation
  • Restart Broken Transfers
    • Automatically restarts an abandoned data transfer, e.g., after a data plane crash

IRS

  • Efficient Orchestration of EDC Negotiations
    • Reduces unnecessary duplicate negotiations and improves performance
  • Remediation of technical Debt
    • Improved calculation of order and batch statuses, along with integration of progress indicators.
  • Limitation of Parallel Job Execution
    • Reduces system load and prevents resource exhaustion

details to be found here

Details on compatible and non-compatible versions

By default, the versions listed in the Tractus-X changelog are the recommended versions. Non-compatible or other compatible versions of the Tractus-X release or the apps are listed below. If a version is interoperable with the initial release version and those features and with all other listed versions its listed as compatible.

Compatible versions

ComponentVersionsComments
Eclipse Data Space Connector
(Tractus-X EDC)
0.7.7
0.8.0
0.8.1
0.9.0 [Latest]

Non-compatible versions

ComponentVersions
N/AN/A

Further Scope Clarification

To uphold the integrity and reliability of the onboarding process, there will be a temporary change of the standards. This change is in-line with a feature supported in the current reference implementation.

Impact: CSP-B & OSP roles:

  • CX-0006.
    • The standard has been slightly adjusted. Onboarding service providers and core service providers must continue to support the possibility of creating a Self-Description (SD) of the Legal Person. However, this requirement is no longer strictly tied to the initial registration process; the creation of the SD can now occur at a later stage. For any SDs that are issued, they must be stored in a central location and must comply with GAIA-X standards and guidelines.

The functionality of Catena-X and the security framework will remain unaffected furthermore the validation of company data and identifiers will continue as usual.

CX-Jupiter

· 3 min read

Catena-X Standards

  • 13 new standards, completing the set of Catena-X' initial use cases
  • 35 updated standards to ensure quality, coherence and the implementation of our "breaking change" via SSI
  • 67 deprecated standards in the course of consolidation to achieve more user-friendliness
  • updated modular certification framework

details to be found here

Catena-X Operating Model

  • updated to version 3.0 enabling many new ecosystem components such as the OSP role, Catena-X Sandboxes and an overhaul to release management focused on stability and reliability

details to be found here

Catena-X Regulatory Framework

  • introduced the official Catena-X ODRL profile including standardized Catena-X policies.
  • adding various pre-defined use case frameworks, e.g. Circular Economy, Demand and Capacity Management, etc.
  • moving China to White List, allowing onboarding of Chinese companies to the Catena-X network

details to be found here

Tractus-X reference implementations

A comprehensive, coherent and compatible set of development artefacts. Highlights include:

  • an update to the Multi-OpCo solutions
  • the full implementation of the Industry Core KIT
  • the advancement of Self Sovereign Identity concepts
  • several improvements to the user-friendliness of KITs based on feedback received to date, making Tractus-X overall more accessible and welcoming to newcomers and veterans alike.

details to be found here

Details on compatible and non-compatible versions

By default, the versions listed in the Tractus-X changelog are the recommended versions. Non-compatible or other compatible versions of the Tractus-X release or the apps are listed below. If a version is interoperable with the initial release version and those features and with all other listed versions its listed as compatible.

Compatible versions

ComponentVersionsComments
Eclipse Data Space Connector
(Tractus-X EDC)
0.7.3
0.7.4
0.7.5
0.7.6
0.7.7 [Latest]
Versions ≤ 0.7.5 are effected by a security issue details here.

[Latest] – latest released version
[Recommended] – recommended by the Catena-X association (Compatible with the Catena-X Standards and [End-to-End] tested)

Non-compatible versions

ComponentVersions
N/AN/A

Further Scope Clarification

To uphold the integrity and reliability of the onboarding process, there will be a temporary change of the standards. This change is in-line with a feature supported in the current reference implementation.

Impact: CSP-B & OSP roles:

  • CX-0006.
    • The standard has been slightly adjusted. Onboarding service providers and core service providers must continue to support the possibility of creating a Self-Description (SD) of the Legal Person. However, this requirement is no longer strictly tied to the initial registration process; the creation of the SD can now occur at a later stage. For any SDs that are issued, they must be stored in a central location and must comply with GAIA-X standards and guidelines.

The functionality of Catena-X and the security framework will remain unaffected furthermore the validation of company data and identifiers will continue as usual.