Catena-X Automotive Data Interoperability

I am building a Catena-X based data-exchange environment for an automotive program and need an expert who can make different partner systems speak the same language without compromising Catena-X rules. Your core mission is to design and validate the interoperability layer so that material, production and quality datasets flow seamlessly between OEMs, Tier-1s and digital service providers.

Here is what I’m aiming for:
• A clear, end-to-end interoperability concept covering semantic models, IDs & global identifiers, and the hand-shake logic expected by the Catena-X reference architecture.
• Mapping guidelines that show how existing ERP/MES/PLM data structures align with the Catena-X data models (BOM, Traceability, CO₂ Passport, etc.).
• A working proof-of-concept using common Catena-X tooling—e.g., Eclipse Dataspace Connector, Tractus-X semantic hub or similar—demonstrating a secure exchange between at least two mock partners.
• Concise documentation so that internal developers can extend the approach to additional partners later.

Acceptance criteria
1. Data objects can be queried and retrieved through Catena-X compliant APIs without manual reformatting.
2. Partner A’s payload passes validation in Partner B’s environment and vice-versa.
3. All artifacts (schemas, mappings, test scripts) are delivered in a version-controlled repository and reviewed with me in a hand-off session.

If you have hands-on experience orchestrating interoperability inside Catena-X or IDS-based ecosystems—and can point to a live or demo environment—I’d love to collaborate.