Catena-X
Catena-X dataspace nodes for Flow-Like — EDC (assets, policies, catalog, negotiation, transfer, EDR), Digital Twin Registry (AAS), Discovery Services, BPDM and Industry Core building blocks
About
Catena-X for Flow-Like
Connect your flows to the Catena-X automotive dataspace — no dataspace expertise required.
This package brings the full Eclipse Tractus-X / Catena-X stack into Flow-Like as 66 drag-and-drop nodes. Offer data to partners, consume theirs, register digital twins, exchange PCF values, send quality notifications or run DCM/PURIS supply flows — each as a visual building block that hides the protocol machinery (DSP catalog requests, contract negotiation, transfer processes, EDR tokens, policy dialects) behind a handful of pins.
What you can build
- Share a backend API as a dataspace offer — one node creates the EDC asset, access & usage policies and contract definition, idempotently.
- Pull data from a partner — one node does catalog lookup, policy check, negotiation, transfer and data-plane pull, with automatic reuse of existing contract agreements.
- Register and resolve digital twins — publish AAS shell descriptors to your Digital Twin Registry, discover partner twins by part number or VAN, and fetch typed submodel payloads.
- Run Catena-X use cases out of the box — Traceability & quality notifications, Product Carbon Footprint exchange, Digital Product Pass / Battery Pass, DCM demand & capacity, PURIS item stock, company certificates and IRS chain traversal.
The nodes at a glance
Category | Nodes | What's inside |
|---|---|---|
Core | 19 | High-level, one-node-per-use-case: Provide Data, Consume Data, Register/Resolve Twin, Fetch Submodel, Publish Part, Traverse BOM, Product Passport, PCF send/get, quality notifications, DCM & certificate exchange |
EDC / Provide | 6 | Granular provider control: assets, policy definitions, contract definitions, asset queries and cleanup |
EDC / Consume | 6 | Granular consumer control: catalog requests, negotiation, negotiation state, transfer, EDR retrieval, authenticated proxy calls |
Digital Twin | 6 | Direct DTR access: create/get/delete shells, add submodel descriptors, lookup by specific asset IDs |
Discovery | 4 | Discovery Finder, BPN Discovery, EDC Discovery and business-partner-to-connector resolution |
BPDM | 5 | Business partner golden records: pool search & lookup, Gate upload, sharing state, Gate output |
Utils | 20 | Builders and validators for 15 official SAMM aspect models (SerialPart, Batch, PCF, ItemStock, BOM aspects, week-based DCM models …), policy builder, BPN validation, DPP code parsing, OAuth tokens |
Every aspect builder emits standards-compliant payloads with the correct semantic model version — no hand-crafting urn:samm:… JSON.
Designed for real dataspaces
- Current policy dialect — speaks the Tractus-X 2025 profile (Membership, FrameworkAgreement, UsagePurpose) and correctly separates access from usage policies so your offers stay visible.
- Idempotent by default — re-running a flow won't fail on already-existing assets, policies or twins; duplicates are detected and reported via output pins instead of errors.
- Agreement caching — consume nodes reuse finalized contract agreements, so repeated fetches skip negotiation entirely.
- Battle-tested — 55 of the 66 nodes run end-to-end against a live Tractus-X Umbrella dataspace (two EDC connectors, DTR, wallet, submodel backend) on every change: 117 scenario steps covering real negotiations, transfers, twin registrations and use-case round-trips. The remainder (Discovery, BPDM, IRS) is covered by unit and lint tests until those services join the test environment.
Getting started
- Add your EDC Connection (management URL, API key, your BPN) and, if you provide twins, a DTR Connection.
- Drop Provide Data (EDC) to publish your first offer, or Consume Data (EDC) with a partner's BPN and connector address to fetch one.
- Compose bigger flows from the granular nodes when you need fine control — every intermediate artifact (offer, agreement, EDR, shell descriptor) is available as a typed pin.
Catena-X® is a registered trademark of the Catena-X Automotive Network e.V. This package is an independent community integration built on the open Eclipse Tractus-X reference implementations.
Provided Nodes
66 nodes included in this package.
Catena-X / BPDM
Fetches the curated golden record for an uploaded partner (POST /v6/output/business-partners/search) including the assigned BPNL
Fetches a legal entity's golden record from the BPDM Pool by BPNL
Reads the golden-record processing state of an uploaded partner record (GET /v6/sharing-states) — Success yields the assigned BPN
Full-text search for legal entities in the BPDM Pool (name, BPNL, address)
Uploads a business partner record to the BPDM Gate input stage (PUT /v6/input/business-partners) to start the golden-record process
Catena-X / Core
Consumes the partner's offer with a given dct:type taxonomy IRI (catalog filter → policy gate → negotiate → transfer → EDR → request). The pattern behind DCM, PCF, certificate and notification KITs. Agreements are cached per partner+type.
Fetches data from a partner asset in one step: catalog lookup, policy allow-list check, negotiation, transfer, EDR pull. Reuses cached agreements.
Finds the submodel descriptor matching a semantic id in a shell, consumes the referenced EDC asset and fetches the payload through the data plane
Fetches BusinessPartnerCertificate data (e.g. ISO 9001) through the partner's company-certificate offer (Company Certificate KIT; API path is release-dependent and configurable)
Requests a Product Carbon Footprint through the partner's PCF Exchange offer (dct:type PcfExchange). Async flows return 202 (accepted).
Resolves the partner's digital twin by specific asset ids and fetches its product passport submodel (digital_product_passport, battery_pass, transmission_pass, …) — the EcoPass consumption flow
Reads an IRS traversal job (GET /irs/jobs/{id}) and returns state, shells, relationships and collected submodels
Registers a BOM traversal job on a managed Item Relationship Service (POST /irs/jobs) — cross-company alternative to Traverse BOM
Publishes a backend API as a dataspace offer in one step: creates asset, policy definition and contract definition (all idempotent via HTTP 409)
Publishes a catalog part end-to-end: EDC submodel asset + policy + contract definition, then a digital twin with a PartTypeInformation submodel descriptor in the DTR
Creates a shell descriptor with inline submodel descriptors in the DTR (missing ids auto-generated)
Resolves a company name to its BPNL and golden record via the BPDM Pool (first match)
Consumes the partner's Digital Twin Registry offer (dct:type DigitalTwinRegistry), looks up shells by specific asset ids and returns the first matching shell descriptor
Pushes a WeekBasedCapacityGroup payload to the partner's DCM capacity asset (Demand & Capacity Management KIT)
Pushes a WeekBasedMaterialDemand payload to the partner's DCM demand asset (Demand & Capacity Management KIT)
Pushes a Product Carbon Footprint to the requesting partner's PcfExchange offer (PUT productIds/{id}?requestId=…) — the provider response leg of the async PCF flow
Delivers a quality investigation notification through the partner's notification offer (Traceability KIT)
Resolves a start twin, then walks SingleLevelBomAsBuilt child relations breadth-first within the partner's DTR, returning a node/edge graph
Sends a status transition (ACKNOWLEDGED/ACCEPTED/DECLINED/CLOSED) for a quality notification through the partner's update offer (Traceability KIT)
Catena-X / Digital Twin
Adds a submodel descriptor (DSP endpoint) to an existing shell in the DTR
Registers an Asset Administration Shell descriptor in the DTR. Missing ids are auto-generated (urn:uuid).
Removes a shell descriptor from the DTR by AAS id
Builds a connection descriptor for a Digital Twin Registry (AAS v3 API)
Reads a shell descriptor (including submodel descriptors) from the DTR by AAS id
Finds AAS ids by specific asset ids (e.g. manufacturerPartId) via the DTR lookup API
Catena-X / Discovery
Resolves identifiers (e.g. manufacturerPartId) to BPNs via a BPN Discovery service
Queries the Discovery Finder for discovery endpoints handling given id types (e.g. bpn, manufacturerPartId)
Resolves BPNs to registered connector endpoints via the Portal's EDC Discovery service
Fetches an access token via OAuth2 client-credentials (Catena-X Portal IDP / Keycloak)
Catena-X / EDC / Consume
Performs an HTTP request through the provider data plane using an EDR token
Fetches the Endpoint Data Reference (auto-refreshed) by transfer process id, or looks it up via agreement id
Reads the current state of a contract negotiation
Initiates a contract negotiation for a catalog offer and polls until it is finalized
Requests the DSP catalog of a partner connector and parses the dataset offers
Starts an HttpData-PULL transfer process for a contract agreement and polls until STARTED
Catena-X / EDC / Provide
Binds access & contract policies to an asset so it appears in the catalog. Idempotent: HTTP 409 is reported as already existing.
Registers an asset (HttpData data address) in the EDC Management API. Idempotent: HTTP 409 is reported as already existing.
Registers an ODRL policy definition in the EDC. Idempotent: HTTP 409 is reported as already existing.
Deletes an asset from the own EDC (fails while referenced by an agreement)
Builds a connection descriptor for a Tractus-X EDC Management API
Queries assets on the own EDC via QuerySpec filter
Catena-X / Utils
Builds a SAMM Batch 3.0.0 aspect payload for a production batch
Builds a SAMM SingleLevelBomAsBuilt 3.0.0 aspect payload (parent → child relationships)
Builds a SAMM SingleLevelBomAsPlanned 3.0.0 aspect payload (planned parent → child relationships)
Builds a Catena-X ODRL policy (Membership, FrameworkAgreement, UsagePurpose constraints)
Builds a SAMM DeliveryInformation 2.0.0 aspect payload (PURIS) with a single delivery position
Builds a SAMM ItemStock 2.0.0 aspect payload (PURIS) with a single allocated stock position
Builds a SAMM JustInSequencePart 3.0.0 aspect payload for a JIS part
Builds a SAMM ShortTermMaterialDemand 1.0.0 aspect payload (PURIS) with a single demand position
Builds a SAMM PartTypeInformation 1.0.0 aspect payload for a part type (catalog part)
Builds a minimal SAMM Pcf 7.0.0 payload (id, product, declared unit, footprint values). Supply the remaining mandatory PCF data model fields via the extra pin.
Builds a SAMM PlannedProductionOutput 2.0.0 aspect payload (PURIS) with a single production position
Builds a SAMM SerialPart 3.0.0 aspect payload for a serialized part
Builds the Industry Core specificAssetIds set (manufacturerPartId, manufacturerId, …) with BPN visibility
Builds a SAMM SingleLevelUsageAsBuilt 3.0.0 aspect payload (child → parent usage relationships)
Builds a SAMM WeekBasedCapacityGroup 3.0.0 payload (DCM supplier response)
Builds a SAMM WeekBasedMaterialDemand 3.0.0 payload (DCM) with a single demand series
Generates a UUIDv4 in urn:uuid format (Catena-X id convention)
Parses a Digital Product Pass code (CX:<manufacturerPartId>:<partInstanceId>) into specific asset ids ready for twin resolution
Checks an aspect payload for required fields (dot-paths). Default fields are derived from well-known semantic ids.
Checks BPNL/BPNS/BPNA format (16 chars, valid prefix, 12 alphanumerics)