Smart Data Models’ Candidates repository now includes a new candidate standard translated from the Catena-X semantic models: catena-x-semantic-models, with 8 candidate models from the Catena-X Industry Core, the traceability backbone of the automotive data space. The source models are published under CC-BY-4.0. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.
About the Catena-X semantic models
Catena-X is the data space of the automotive industry. Its shared vocabulary is a set of aspect models written in SAMM, the Semantic Aspect Meta Model, and published by the Catena-X Automotive Network through the Eclipse Tractus-X project in the sldt-semantic-models repository. Each aspect describes one view of a digital twin, such as a serialized part, its bill of material or its product carbon footprint. All the aspects of a twin share one identifier, the globalAssetId. The repository holds about 150 aspect models. This first candidate covers the Industry Core, the eight aspects that every Catena-X traceability use case builds on, in their current versions (the io.catenax.industry_core namespaces introduced in release 26.09).
The models
| Model | Source aspect | What it describes |
|---|---|---|
SerialPart |
serial_part 4.0.0 | a part instance identified by a serial number or similar identifier |
Batch |
batch 4.0.0 | a set of parts produced together and tracked by batch |
JustInSequencePart |
just_in_sequence_part 4.0.0 | a part delivered just in sequence to an assembly line |
PartType |
part_type 2.0.0 | a part as designed, with its planned production sites |
SingleLevelBomAsBuilt |
single_level_bom_as_built 4.0.0 | the child items actually built into a part |
SingleLevelUsageAsBuilt |
single_level_usage_as_built 4.0.0 | the parent items a part was actually built into |
SingleLevelBomAsPlanned |
single_level_bom_as_planned 4.0.0 | the planned child items of a part type |
SingleLevelUsageAsPlanned |
single_level_usage_as_planned 3.0.0 | the planned parent items of a part type |
Examples from the Tractus-X reference data
Real Catena-X data is exchanged between companies under usage policies and is not public. The examples therefore come from the Eclipse Tractus-X reference test data set used by the Item Relationship Service, which forms consistent twin trees. A “Door front-left” serial part, its as-built bill of material and its as-built usage describe the same twin, and its child is the just-in-sequence part “Mirror left”. On the planning side, an “OEM A High Voltage Battery” part type is planned into a “Vehicle Model A”. The test data uses older aspect versions, so each record was updated to the current version using the renames in each model’s release notes.
Translation notes
- One aspect, one entity type. NGSI-LD has no notion of aspects, so each aspect becomes its own entity type, with the id
urn:ngsi-ld:<Aspect>:<twin UUID>. The entities of one twin share the sameglobalAssetId. - Payloads map one-to-one. The schemas are built from the JSON Schemas that the SAMM tooling generates, with names, nesting, required fields, enumerations and patterns kept exactly. Each aspect’s own sample payload validates against the translated schema.
- Structured values stay JSON. The
@contextmaps each attribute to its SAMM URN and declares structured attributes as JSON literals, so nested keys such as a classification’sidare not reinterpreted as NGSI-LD keywords. - Part links kept as Catena-X writes them. Bill-of-material and usage entries reference other twins by
globalAssetId, together with quantity, business partner and timestamps. They are kept as property values rather than NGSI-LD Relationships. - Licence verified. The aspect models are CC-BY-4.0, and the example data is Apache-2.0.
Try it, and tell us what’s missing
These are Candidates: first, carefully sourced translations that are not yet official Smart Data Models subjects. Before that step, the open questions are whether to expose part links as NGSI-LD Relationships, and how these models relate to dataModel.AAS (Catena-X twins are published as Asset Administration Shells), dataModel.ManufacturingMachine and dataModel.Battery. Natural next steps are other Catena-X aspects: Product Carbon Footprint, the Digital Product Passport and the Battery Pass.
Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/catena-x-semantic-models
