1"use strict";(globalThis.webpackChunkcatenax_ev_github_io_new=globalThis.webpackChunkcatenax_ev_github_io_new||[]).push([[6612],{39208(e,t,a){a.r(t),a.d(t,{assets:()=>l,contentTitle:()=>d,default:()=>m,frontMatter:()=>o,metadata:()=>n,toc:()=>c});const n=JSON.parse('{"id":"standards/CX-0127-IndustryCorePartInstance/CX-0127-IndustryCorePartInstance","title":"CX-0127 Industry Core: Part Instance 2.0.2","description":"ABSTRACT","source":"@site/versioned_docs/version-Saturn/standards/CX-0127-IndustryCorePartInstance/CX-0127-IndustryCorePartInstance.md","sourceDirName":"standards/CX-0127-IndustryCorePartInstance","slug":"/standards/CX-0127-IndustryCorePartInstance/","permalink":"/docs/Saturn/standards/CX-0127-IndustryCorePartInstance/","draft":false,"unlisted":false,"tags":[{"inline":true,"label":"CAT/Semantic","permalink":"/docs/Saturn/tags/cat-semantic"},{"inline":true,"label":"CAT/Industry Core","permalink":"/docs/Saturn/tags/cat-industry-core"}],"version":"Saturn","frontMatter":{"tags":["CAT/Semantic","CAT/Industry Core"]},"sidebar":"sidebar_standards","previous":{"title":"CX-0126 Industry Core: Part Type 2.1.1","permalink":"/docs/Saturn/standards/CX-0126-IndustryCorePartType/"},"next":{"title":"CX-0128 - Demand and Capacity Management Data Exchange v2.2.1","permalink":"/docs/Saturn/standards/CX-0128-DemandandCapacityManagementDataExchange/"}}');var i=a(74848),s=a(28453),r=a(16877);const o={tags:["CAT/Semantic","CAT/Industry Core"]},d="CX-0127 Industry Core: Part Instance 2.0.2",l={},c=[{value:"ABSTRACT",id:"abstract",level:2},{value:"FOR WHOM IS THE STANDARD DESIGNED",id:"for-whom-is-the-standard-designed",level:2},{value:"COMPARISON WITH THE PREVIOUS VERSION OF THE STANDARD",id:"comparison-with-the-previous-version-of-the-standard",level:2},{value:"1 INTRODUCTION",id:"1-introduction",level:2},{value:"1.1 AUDIENCE & SCOPE",id:"11-audience--scope",level:3},{value:"1.2 CONTEXT AND ARCHITECTURE FIT",id:"12-context-and-architecture-fit",level:3},{value:"1.3 CONFORMANCE AND PROOF OF CONFORMITY",id:"13-conformance-and-proof-of-conformity",level:3},{value:"1.4 EXAMPLES",id:"14-examples",level:3},{value:"1.5 TERMINOLOGY",id:"15-terminology",level:3},{value:"2 RELEVANT PARTS OF THE STANDARD FOR SPECIFIC USE CASES",id:"2-relevant-parts-of-the-standard-for-specific-use-cases",level:2},{value:"2.1 "Data Provisioning Industry Core: Part Instance"",id:"21-data-provisioning-industry-core-part-instance",level:3},{value:"2.1.1 LIST OF STANDALONE STANDARDS",id:"211-list-of-standalone-standards",level:4},{value:"2.1.2 DATA REQUIRED",id:"212-data-required",level:4},{value:"2.1.3 ADDITIONAL REQUIREMENTS",id:"213-additional-requirements",level:4},{value:"POLICY CONSTRAINTS FOR DATA EXCHANGE",id:"policy-constraints-for-data-exchange",level:4},{value:"Versioning",id:"versioning",level:5},{value:"2.1.4 DIGITAL TWINS AND SPECIFIC ASSET IDs",id:"214-digital-twins-and-specific-asset-ids",level:4},{value:"Authorization: Visbility of Specific Asset IDs in the DTR",id:"authorization-visbility-of-specific-asset-ids-in-the-dtr",level:5},{value:"3 ASPECT MODELS",id:"3-aspect-models",level:2},{value:"3.1 ASPECT MODEL "SerialPart"",id:"31-aspect-model-serialpart",level:3},{value:"3.1.1 INTRODUCTION",id:"311-introduction",level:4},{value:"3.1.2 SPECIFICATIONS ARTIFACTS",id:"312-specifications-artifacts",level:4},{value:"3.1.3 LICENSE",id:"313-license",level:4},{value:"3.1.4 IDENTIFIER OF SEMANTIC MODEL",id:"314-identifier-of-semantic-model",level:4},{value:"3.1.5 FORMATS OF SEMANTIC MODEL",id:"315-formats-of-semantic-model",level:4},{value:"3.1.5.1 RDF TURTLE",id:"3151-rdf-turtle",level:5},{value:"3.1.5.2 JSON SCHEMA",id:"3152-json-schema",level:5},{value:"3.1.5.3 AASX",id:"3153-aasx",level:5},{value:"3.1.6 EXAMPLE DATA",id:"316-example-data",level:4},{value:"3.2 ASPECT MODEL "Batch"",id:"32-aspect-model-batch",level:3},{value:"3.2.1 INTRODUCTION",id:"321-introduction",level:4},{value:"3.2.2 SPECIFICATIONS ARTIFACTS",id:"322-specifications-artifacts",level:4},{value:"3.2.3 LICENSE",id:"323-license",level:4},{value:"3.2.4 IDENTIFIER OF SEMANTIC MODEL",id:"324-identifier-of-semantic-model",level:4},{value:"3.2.5 FORMATS OF SEMANTIC MODEL",id:"325-formats-of-semantic-model",level:4},{value:"3.2.5.1 RDF TURTLE",id:"3251-rdf-turtle",level:5},{value:"3.2.5.2 JSON SCHEMA",id:"3252-json-schema",level:5},{value:"3.2.5.3 AASX",id:"3253-aasx",level:5},{value:"3.2.6 EXAMPLE DATA",id:"326-example-data",level:4},{value:"3.3 ASPECT MODEL "JustInSequencePart"",id:"33-aspect-model-justinsequencepart",level:3},{value:"3.3.1 INTRODUCTION",id:"331-introduction",level:4}
1,{value:"3.3.2 SPECIFICATIONS ARTIFACTS",id:"332-specifications-artifacts",level:4},{value:"3.3.3 LICENSE",id:"333-license",level:4},{value:"3.3.4 IDENTIFIER OF SEMANTIC MODEL",id:"334-identifier-of-semantic-model",level:4},{value:"3.3.5 FORMATS OF SEMANTIC MODEL",id:"335-formats-of-semantic-model",level:4},{value:"3.3.5.1 RDF TURTLE",id:"3351-rdf-turtle",level:5},{value:"3.3.5.2 JSON SCHEMA",id:"3352-json-schema",level:5},{value:"3.3.5.3 AASX",id:"3353-aasx",level:5},{value:"3.3.6 EXAMPLE DATA",id:"336-example-data",level:4},{value:"3.4 ASPECT MODEL "SingleLevelBomAsBuilt"",id:"34-aspect-model-singlelevelbomasbuilt",level:3},{value:"3.4.1 INTRODUCTION",id:"341-introduction",level:4},{value:"3.4.2 SPECIFICATIONS ARTIFACTS",id:"342-specifications-artifacts",level:4},{value:"3.4.3 LICENSE",id:"343-license",level:4},{value:"3.4.4 IDENTIFIER OF SEMANTIC MODEL",id:"344-identifier-of-semantic-model",level:4},{value:"3.4.5 FORMATS OF SEMANTIC MODEL",id:"345-formats-of-semantic-model",level:4},{value:"3.4.5.1 RDF TURTLE",id:"3451-rdf-turtle",level:5},{value:"3.4.5.2 JSON SCHEMA",id:"3452-json-schema",level:5},{value:"3.4.5.3 AASX",id:"3453-aasx",level:5},{value:"3.4.6 EXAMPLE DATA",id:"346-example-data",level:4},{value:"3.5 ASPECT MODEL "SingleLevelUsageAsBuilt"",id:"35-aspect-model-singlelevelusageasbuilt",level:3},{value:"3.5.1 INTRODUCTION",id:"351-introduction",level:4},{value:"3.5.2 SPECIFICATIONS ARTIFACTS",id:"352-specifications-artifacts",level:4},{value:"3.5.3 LICENSE",id:"353-license",level:4},{value:"3.5.4 IDENTIFIER OF SEMANTIC MODEL",id:"354-identifier-of-semantic-model",level:4},{value:"3.5.5 FORMATS OF SEMANTIC MODEL",id:"355-formats-of-semantic-model",level:4},{value:"3.5.5.1 RDF TURTLE",id:"3551-rdf-turtle",level:5},{value:"3.5.5.2 JSON SCHEMA",id:"3552-json-schema",level:5},{value:"3.5.5.3 AASX",id:"3553-aasx",level:5},{value:"3.5.6 EXAMPLE DATA",id:"356-example-data",level:4},{value:"4 APPLICATION PROGRAMMING INTERFACES",id:"4-application-programming-interfaces",level:2},{value:"4.1 UNIQUE ID PUSH NOTIFICATION API",id:"41-unique-id-push-notification-api",level:3},{value:"4.1.1 PRECONDITIONS AND DEPENDENCIES",id:"411-preconditions-and-dependencies",level:4},{value:"4.1.2 API SPECIFICATION",id:"412-api-specification",level:4},{value:"4.1.2.1 API-ENDPOINTS",id:"4121-api-endpoints",level:5},{value:"4.1.2.2 AVAILABLE DATA TYPES",id:"4122-available-data-types",level:5},{value:"4.1.2.3 API RESOURCES & ENDPOINTS",id:"4123-api-resources--endpoints",level:5},{value:"4.1.3 DATA ASSET STRUCTURE",id:"413-data-asset-structure",level:4},{value:"DATA ASSET FOR UNIQUE ID PUSH NOTIFICATION RECEIVE ENDPOINT",id:"data-asset-for-unique-id-push-notification-receive-endpoint",level:5},{value:"4.1.4 VERSIONING",id:"414-versioning",level:4},{value:"5 PROCESSES",id:"5-processes",level:2},{value:"6 REFERENCES",id:"6-references",level:2},{value:"6.1 NORMATIVE REFERENCES",id:"61-normative-references",level:3},{value:"6.2 NON-NORMATIVE REFERENCES",id:"62-non-normative-references",level:3},{value:"6.3 REFERENCE IMPLEMENTATIONS",id:"63-reference-implementations",level:3},{value:"ANNEXES",id:"annexes",level:2},{value:"FIGURES",id:"figures",level:3},{value:"TABLES",id:"tables",level:3},{value:"Legal",id:"legal",level:2}];function h(e){const t={a:"a",blockquote:"blockquote",code:"code",em:"em",h1:"h1",h2:"h2",h3:"h3",h4:"h4",h5:"h5",header:"header",li:"li",ol:"ol",p:"p",pre:"pre",section:"section",strong:"strong",sup:"sup",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",ul:"ul",...(0,s.R)(),...e.components};return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(t.header,{children:(0,i.jsx)(t.h1,{id:"cx-0127-industry-core-part-instance-202",children:"CX-0127 Industry Core: Part Instance 2.0.2"})}),"\n",(0,i.jsx)(t.h2,{id:"abstract",children:"ABSTRACT"}),"\n",(0,i.jsxs)(t.p,{children:['This standard describes the "Industry Core: ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"Part Instance"}),'". It sets the foundation to describe, identify and find a component on an instance level and enables traversing across several levels in both directions to ensure the creation of data chains. The core makes it possible to configure enablement services for component-based data exchange. Other use cases are meant to build upon the foundation that is given by the industry core.']}),"\n",(0,i.jsx)(t.h2,{id:"for-whom-is-the-standard-designed",children:"FOR WHOM IS THE STANDARD DESIGNED"}),"\n",(0,i.jsxs)(t.p,{children:["This standard is designed for everybody who wants to register, describe and use digital twins on ",(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instance"})," level."]}),"\n",(0,i.jsx)(t.h2,{id:"comparison-with-the-previous-version-of-the-standard",children:"COMPARISON WITH THE PREVIOUS VERSION OF THE STANDARD"}),"\n",(0,i.jsxs)(t.ul,{children:["\n",(0,i.jsxs)(t.li,{children:["New versions of ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect models"})," in ",(0,i.jsx)(t.a,{href:"#3-aspect-models",children:"Section 3"}),"\n",(0,i.jsxs)(t.ul,{children:["\n",(0,i.jsxs)(t.li,{children:["SerialPart 3.0.0 (see link to changelog in section of the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),")"]}),"\n",(0,i.jsxs)(t.li,{children:["Batch 3.0.0 (see link to changelog in section of the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),")"]}),"\n",(0,i.jsxs)(t.li,{children:["JustInSequencePart 3.0.0 (see link to changelog in section of the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),")"]}),"\n",(0,i.jsxs)(t.li,{children:["SingleLevelBomAsBuilt 3.0.0 (see link to changelog in section of the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),")"]}),"\n"]}),"\n"]}),"\n",(0,i.jsxs)(t.li,{children:["Newly standardized ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect models"})," in ",(0,i.jsx)(t.a,{href:"#3-aspect-models",children:"Section 3"}),"\n",(0,i.jsxs)(t.ul,{children:["\n",(0,i.jsxs)(t.li,{children:["SingleLevelUsageAsBuilt 3.0.0 (see link to changelog in section of the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),")"]}),"\n"]}),"\n"]}),"\n",(0,i.jsxs)(t.li,{children:[(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect model"})," JustInSequencePart now ",(0,i.jsx)(t.strong,{children:"MUST"})," be provided when creating a digital twin for a Just-In-Seuqence-Part (was optional before) in ",(0,i.jsx)(t.a,{href:"#212-data-required",children:"Section 2.1.2"})]}),"\n",(0,i.jsxs)(t.li,{children:["Changes in specificAssetIds of Digital Twins in ",(0,i.jsx)(t.a,{href:"#214-digital-twins-and-specific-asset-ids",children:"Section 2.1.4"}),"\n",(0,i.jsxs)(t.ul,{children:["\n",(0,i.jsx)(t.li,{children:"Removed assetLifeCyclePhase"}),"\n",(0,i.jsx)(t.li,{children:"DigitalTwinType is now mandatory (before it was optional)"}),"\n",(0,i.jsxs)(t.li,{children:["Added intrinsicId specifically for Digital Twins for ",(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized parts"}),", batches and just-in-sequence-parts"]}),"\n",(0,i.jsx)(t.li,{children:"Removed partInstanceId from Digital Twins for batches and just-in-sequence-parts"}),"\n"]}),"\n"]}),"\n",(0,i.jsxs)(t.li,{children:["Added Unique ID Push Notification ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," in ",(0,i.jsx)(t.a,{href:"#41-unique-id-push-notification-api",children:"Section 4.1"})," as content of industry core"]}),"\n",(0,i.jsxs)(t.li,{children:['New paragraph "Conventions for Use Case Policy in context data exchange" in ',(0,i.jsx)(t.a,{href:"#213-additional-requirements",children:"Section 2.1.3"})]}),"\n",(0,i.jsxs)(t.li,{children:["Added notes for versioning in ",(0,i.jsx)(t.a,{href:"#213-additional-requirements",children:"Section 2.1.3"})]}),"\n",(0,i.jsxs)(t.li,{children:['Deleted "Every certified business application relying on aspects models of this standard ',(0,i.jsx)(t.strong,{children:"MUST"}),' be able to consume data conformant to the semantic models specified in this document." from ',(0,i.jsx)(t.a,{href:"#3-aspect-models",children:"Section 3"})]}),"\n"]}),"\n",(0,i.jsxs)(t.p,{children:["Note: This release (",(0,i.jsx)(t.strong,{children:"24.05."}),") contains ",(0,i.jsx)(t.strong,{children:"breaking changes"}),"!"]}),"\n",(0,i.jsx)(t.h2,{id:"1-introduction",children:"1 INTRODUCTION"}),"\n",(0,i.jsxs)(t.p,{children:['This standard contains all information on the "Industry Core: ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"Part Instance"}),'". The Industry Core is a shared foundation for use cases that utilize digital twins and ',(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect models"}),' in Catena-X. The "Industry Core: ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"Part Instance"}),'" describes digital twins and ',(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect models"})," that are used to represent identifiable instantiated parts, such as serial parts, just-in-sequence parts or batches, and describes those in the Catena-X network. Digital twins and ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect models"}),' are meant to be reused by other use cases as much as possible, in order to simplify data provisioning across different use cases.\nThe "Industry Core: ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"Part Instance"}),'" provides the basis for the identification, description, findability of ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-
1in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instance"})," digital twins in the Catena-X network and the connection of those twins to build data chains across the supply chain in both directions."]}),"\n",(0,i.jsx)(t.h3,{id:"11-audience--scope",children:"1.1 AUDIENCE & SCOPE"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is non-normative"})}),"\n"]}),"\n",(0,i.jsx)(t.p,{children:"This document is targeting subsets of the following roles:"}),"\n",(0,i.jsxs)(t.ul,{children:["\n",(0,i.jsx)(t.li,{children:"Data Provider / Consumer"}),"\n",(0,i.jsx)(t.li,{children:"Business Application Provider"}),"\n",(0,i.jsx)(t.li,{children:"Enablement Service Provider"}),"\n"]}),"\n",(0,i.jsx)(t.p,{children:"Note: Fulfilling a use-case standard by a data provider / consumer can be done in two ways:"}),"\n",(0,i.jsxs)(t.ol,{children:["\n",(0,i.jsx)(t.li,{children:"Purchase a certified app for the use-case. In this case the data provider / consumer does not need to proof conformity again and"}),"\n",(0,i.jsx)(t.li,{children:"Data Provisioning / Consumption without a certified app for the use-case."}),"\n"]}),"\n",(0,i.jsx)(t.h3,{id:"12-context-and-architecture-fit",children:"1.2 CONTEXT AND ARCHITECTURE FIT"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is non-normative"})}),"\n"]}),"\n",(0,i.jsxs)(t.p,{children:['The aim of the "Industry Core: ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"Part Instance"}),'" is to build the foundation to describe, identify and find a component on an instance level and enables traversing across the levels of the supply chain to ensure the creation of data chains and enable data driven use cases over all n-tier levels without compromising data sovereignty. This standard enables data and app providers to deliver solutions for building data chains for identifiable instantiated parts, such as ',(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized parts"}),", vehicles, just-in-sequence parts and batches. This is achieved via the standardized creation of digital twins of those entities as well as the logical linking to their parent and child components (",(0,i.jsx)(r.A,{term:"Bill of Material",definition:"A Bill of Material (BoM) represents the structure of a product: a list of raw materials, sub-assemblies and sub-components needed to manufacture the end product. In Catena-X Traceability more than one BoM is considered, since the BoM can change during the lifecycle (different BoMs for different lifecycles).",routePath:"/glossary",children:"Bill of Material"})," as built, Usage as Built)."]}),"\n",(0,i.jsxs)(t.p,{children:['The "Industry Core: ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"Part Instance"}),'" is not intended to include all information that may be needed in an use case. Instead, it allows the establishment of a value driven data chain and serves as a basis for further data driven use cases.\nIt enables data owners to provide necessary data with individual access rights and usage restrictions (access and usage policies) to ensure privacy and security. Additional information might be shared by utilizing the ',(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," through additional aspects or submodels."]}),"\n",(0,i.jsxs)(t.p,{children:['The "Industry Core: ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"Part Instance"}),'" is supporting the availability of data of identifiable instantiated parts and the connection to their parent and child parts. It describes the concrete digital reflection of a produced vehicle, product or part and its provisioning towards Catena-X including Interoperability and Data Sovereignty standards and components by the participants willing to share such data. This standard also defines which components (e.g. Digital Twin Registry, CX-0018 compliant connector) must be used in order to be interoperable and sovereign in a data exchange as defined in Catena-X.']}),"\n",(0,i.jsx)(t.h3,{id:"13-conformance-and-proof-of-conformity",children:"1.3 CONFORMANCE AND PROOF OF CONFORMITY"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is non-normative"})}),"\n"]}),"\n",(0,i.jsx)(t.p,{children:"In addition to all sections that are marked as
1non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are also non-normative. Everything else in this specification is normative."}),"\n",(0,i.jsxs)(t.p,{children:["The key words ",(0,i.jsx)(t.strong,{children:"MAY"}),", ",(0,i.jsx)(t.strong,{children:"MUST"}),", ",(0,i.jsx)(t.strong,{children:"MUST NOT"}),", ",(0,i.jsx)(t.strong,{children:"OPTIONAL"}),", ",(0,i.jsx)(t.strong,{children:"RECOMMENDED"}),", ",(0,i.jsx)(t.strong,{children:"REQUIRED"}),", ",(0,i.jsx)(t.strong,{children:"SHOULD"}),"\nand ",(0,i.jsx)(t.strong,{children:"SHOULD NOT"})," in this document document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174]\nwhen, and only when, they appear in all capitals, as shown here."]}),"\n",(0,i.jsxs)(t.p,{children:["All participants* and their solutions will need to proof, that they are conform with the Catena-X standards.\nTo validate that the standards are applied correctly, Catena-X employs Conformity Assessment Bodies (CABs).\nPlease refer to: ",(0,i.jsx)(t.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/certification",children:"https://catena-x.net/en/catena-x-introduce-implement/certification"})," for the process of conformity assessment and certification."]}),"\n",(0,i.jsx)(t.p,{children:"The specific criteria described in this document are describing the usage of the central tools as well as common tools described in the linked standardization documents and therefore compliance should be checked with the tools provided for these components."}),"\n",(0,i.jsxs)(t.p,{children:["The versions of the standardization documents valid for this standard are mentioned in sections where the ",(0,i.jsx)(t.a,{href:"#211-list-of-standalone-standards",children:"standalone standards"}),", ",(0,i.jsx)(t.a,{href:"#61-normative-references",children:"normative references"})," and ",(0,i.jsx)(t.a,{href:"#62-non-normative-references",children:"non-normative references"})," are listed. The valid versions are not specifically mentioned in the body text."]}),"\n",(0,i.jsxs)(t.p,{children:["*",(0,i.jsx)(t.em,{children:"Disclaimer: The operating model released by the Catena-X association will define the roadmap, content and scope for the certification process. This will include the roles, certification and further assessment procedures as well as the rollout phases."})]}),"\n",(0,i.jsx)(t.h3,{id:"14-examples",children:"1.4 EXAMPLES"}),"\n",(0,i.jsxs)(t.p,{children:["Examples for data models: See according subsection ",(0,i.jsx)(t.a,{href:"#3-aspect-models",children:"3 Aspect Models"}),"."]}),"\n",(0,i.jsxs)(t.p,{children:["Examples for ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"APIs"}),": See according subsection ",(0,i.jsx)(t.a,{href:"#4-application-programming-interfaces",children:"4 Application Programming Interfaces"})]}),"\n",(0,i.jsx)(t.h3,{id:"15-terminology",children:"1.5 TERMINOLOGY"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is non-normative"})}),"\n"]}),"\n",(0,i.jsxs)(t.p,{children:[(0,i.jsx)(t.strong,{children:(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect Model"})}),":\nA formal, machine-readable semantic description (expressed with RDF/turtle) of data accessible from an Aspect.\nAn ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect Model"})," must adhere to the Semantic Aspect Meta Model (SAMM), i.e., it utilizes elements and relations defined in the Semantic Aspect Meta Model and is compliant to the validity rules defined by the Semantic Aspect Meta Model.\n",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect models"})," are logical data models which can be used to detail a conceptual model in order to describe the semantics of runtime data related to a concept. Further, elements of an ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect model"})," can/should refer to terms of a standardized Business Glossary (if existing)."]}),"\n",(0,i.jsxs)(t.p,{children:[(0,i.jsx)(t.strong,{children:"Batch"}),":\nA batch is a quantity of (semi-) finished products or (raw) material\nproducts that have been produced under the same circumstances (e.g., same\nproduction location), as specified groups or amounts, within a certain\ntime frame. Every batch can differ in the number or amount of products.\nDifferent batches can have varied specifications, e.g., different\ncolors, quality, etc. A batch is identified via a Batch ID."]}),"\n",(0,i.jsxs)(t.p,{children:[(0,i.jsxs)(t.strong,{children:["Business Partner Number (",(0,i.jsx)(r.A,{term:"BPN",definition:"A BPN is the unique identifier of a partner within Catena-X.",routePath:"/glossary",children:"BPN"}),")"]}),":\nA ",(0,i.jsx)(r.A,{term:"BPN",definition:"A BPN is the unique identifier of a partner within Catena-X.",routePath:"/glossary",children:"BPN"})," is the unique identifier of a partner within Catena-x."]}),"\n",(0,i.jsxs)(t.p,{children:[(0,i.jsxs)(t.strong,{children:["Tractus-X
1Eclipse Dataspace Connector (",(0,i.jsx)(r.A,{term:"Tractus-X EDC",definition:"The Tractus-X Eclipse Dataspace Connector (Tractus-X EDC) is a reference implementation for a connector conformant to CX-0018 and acts as a de-facto standard/reference implementation within Catena-X; other CX-0018-conformant connectors are also valid options.",routePath:"/glossary",children:"Tractus-X EDC"}),")"]}),":\nThe ",(0,i.jsx)(r.A,{term:"Tractus-X EDC",definition:"The Tractus-X Eclipse Dataspace Connector (Tractus-X EDC) is a reference implementation for a connector conformant to CX-0018 and acts as a de-facto standard/reference implementation within Catena-X; other CX-0018-conformant connectors are also valid options.",routePath:"/glossary",children:"Tractus-X EDC"})," is a reference implementation for a connector conformant to CX-0018 currently acting as a de-facto standard and/or reference Implementation within Catena-X. When mentioning the ",(0,i.jsx)(r.A,{term:"Tractus-X EDC",definition:"The Tractus-X Eclipse Dataspace Connector (Tractus-X EDC) is a reference implementation for a connector conformant to CX-0018 and acts as a de-facto standard/reference implementation within Catena-X; other CX-0018-conformant connectors are also valid options.",routePath:"/glossary",children:"Tractus-X EDC"})," in this standard, any other CX-0018 conformant connector is also a valid option."]}),"\n",(0,i.jsxs)(t.p,{children:[(0,i.jsxs)(t.strong,{children:["International Data Space (",(0,i.jsx)(r.A,{term:"IDS",definition:"The International Data Space enables 'smart services' and business processes across companies and industries while ensuring data sovereignty and self-determined control of data use.",routePath:"/glossary",children:"IDS"}),")"]}),":\nInternational Data Space and its protocol for data exchange foresees a compliant connector handling contract negotiations before each data transfer and defines a general architecture for data exchange."]}),"\n",(0,i.jsxs)(t.p,{children:[(0,i.jsx)(t.strong,{children:"Just-in-sequence-part"}),":\nJust-in-sequence is a delivery concept where parts are delivered to the production plant at a requested time in the exact order of installation, typically for a 1:1 dependency on the manufactured product. A just-in-sequence-part is a part for which this concept and order of delivery applies and which does not have a dedicated serial number (then it would be considered a ",(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized part"}),"). Examples for JIS-parts are seats and bumpers."]}),"\n",(0,i.jsxs)(t.p,{children:[(0,i.jsx)(t.strong,{children:(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"Part Instance"})}),": A ",(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instance"})," is a physically produced instance (e.g. ",(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized part"}),", batch, just-in-sequence-part) of a part type."]}),"\n",(0,i.jsxs)(t.p,{children:[(0,i.jsx)(t.strong,{children:"Part Type"}),": A part type is a generic (not physically produced) part on material- or catalog-level as a representation for a designed part."]}),"\n",(0,i.jsxs)(t.p,{children:[(0,i.jsx)(t.strong,{children:(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"Serialized part"})}),":\nInstance of a part, where the particular instance can be uniquely identified by means of a serial number, a similar identifier (e.g. ",(0,i.jsx)(r.A,{term:"VAN",definition:"A number mapped 1:1 to a VIN but pseudonymised to protect vehicle identity.",routePath:"/glossary",children:"VAN"}),") or a combination of multiple identifiers (e.g. combination of manufacturer, date and number)."]}),"\n",(0,i.jsxs)(t.p,{children:[(0,i.jsxs)(t.strong,{children:["Vehicle Anonymised Number (",(0,i.jsx)(r.A,{term:"VAN",definition:"A number mapped 1:1 to a VIN but pseudonymised to protect vehicle identity.",routePath:"/glossary",children:"VAN"}),")"]}),":\nA number mapped 1:1 to ",(0,i.jsx)(r.A,{term:"VIN",definition:"A VIN
1is a 17-character code assigned by the manufacturer to every vehicle; it encodes the vehicle's make, model, year of manufacture and other identifying features and serves as a unique identifier throughout the vehicle's lifespan.",routePath:"/glossary",children:"VIN"}),", but pseudonymized."]}),"\n",(0,i.jsxs)(t.p,{children:[(0,i.jsxs)(t.strong,{children:["Vehicle Identification Number (",(0,i.jsx)(r.A,{term:"VIN",definition:"A VIN is a 17-character code assigned by the manufacturer to every vehicle; it encodes the vehicle's make, model, year of manufacture and other identifying features and serves as a unique identifier throughout the vehicle's lifespan.",routePath:"/glossary",children:"VIN"}),")"]}),":\nThe ",(0,i.jsx)(r.A,{term:"VIN",definition:"A VIN is a 17-character code assigned by the manufacturer to every vehicle; it encodes the vehicle's make, model, year of manufacture and other identifying features and serves as a unique identifier throughout the vehicle's lifespan.",routePath:"/glossary",children:"VIN"})," number is a 17-character code assigned by the manufacturer to every vehicle, providing specific information about its brand, model, year of manufacture, and other key features. It is a unique identifier that allows the vehicle to be easily tracked and identified throughout its lifespan."]}),"\n",(0,i.jsx)(t.p,{children:"Additional terminology used in this standard can be looked up in the glossary on the association homepage."}),"\n",(0,i.jsx)(t.h2,{id:"2-relevant-parts-of-the-standard-for-specific-use-cases",children:"2 RELEVANT PARTS OF THE STANDARD FOR SPECIFIC USE CASES"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is normative"})}),"\n"]}),"\n",(0,i.jsx)(t.h3,{id:"21-data-provisioning-industry-core-part-instance",children:'2.1 "Data Provisioning Industry Core: Part Instance"'}),"\n",(0,i.jsx)(t.h4,{id:"211-list-of-standalone-standards",children:"2.1.1 LIST OF STANDALONE STANDARDS"}),"\n",(0,i.jsxs)(t.p,{children:['To participate in Data Provisioning for the "Industry Core: ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"Part Instance"}),'", the following single standards ',(0,i.jsx)(t.strong,{children:"MUST"})," be fulfilled by all participants for which the standard is relevant:"]}),"\n",(0,i.jsxs)(t.ul,{children:["\n",(0,i.jsx)(t.li,{children:"CX-0002 Digital Twins in Catena-X 2.2.0"}),"\n",(0,i.jsx)(t.li,{children:"CX-0018 Dataspace Connectivity 3.0.0"}),"\n"]}),"\n",(0,i.jsx)(t.h4,{id:"212-data-required",children:"2.1.2 DATA REQUIRED"}),"\n",(0,i.jsxs)(t.p,{children:["A digital twin ",(0,i.jsx)(t.strong,{children:"MAY"})," be created for ",(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized part"}),", just-in-sequence-part or batch of materials produced by the manufacturer."]}),"\n",(0,i.jsxs)(t.p,{children:["The digital twin ",(0,i.jsx)(t.strong,{children:"MUST"})," be provisioned via an ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," as per CX-0002 and registered in a decentral Digital Twin Registry of the data provider (or the decentral Digital Twin Registry host of the manufacturer) as described in CX-0002."]}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),' "SerialPart" ',(0,i.jsx)(t.strong,{children:"MUST"})," be linked to the ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," of a ",(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized part"}),"."]}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),' "JustInSequencePart" ',(0,i.jsx)(t.strong,{children:"MUST"})," be linked to the ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," of a just-in-sequence-part."]}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),' "Batch" ',(0,i.jsx)(t.strong,{children:"MUST"})," be linked to the ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," of a Batch."]}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),' "SingleLevelBomAsBuilt" ',(0,i.jsx)(t.strong,{children:"MAY"})," be linked to the ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," of each part and each batch holding the information on relationship of serialized items and batches. Information on the ",(0,i.jsx)(r.A,{term:"Bill of Material",definition:"A Bill of Material (BoM) represents the structure of a product: a list of raw materials, sub-assemblies and sub-components needed to manufacture the end product. In Catena-X Traceability more than one BoM is considered, since the BoM can change during the lifecycle (different BoMs for different lifecycles).",routePath:"/glossary",children:"Bill of Material"})," of those parts and batches ",(0,i.jsx)(t.strong,{children:"MUST NOT"})," be provided in any other way than with the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),' "SingleLevelBomAsBuilt".']}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),' "SingleLevelUsageAsBuilt" ',(0,i.jsx)(t.strong,{children:"MAY"})," be linked to the ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," of each part and each batch holding the information on usage of this part or batch in serialized items or products in general. Information on the usage of those parts and batches ",(0,i.jsx)(t.strong,{children:"MUST NOT"})," be provided in any other way than with the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),' "SingleLevelUsageAsBuilt".']}),"\n",(0,i.jsxs)(t.p,{children:["The submodel data ",(0,i.jsx)(t.strong,{children:"MUST"})," be transferred using the ",(0,i.jsx)(r.A,{term:"IDS",definition:"The International Data Space enables 'smart services' and business processes across companies and industries while ensuring data sovereignty and self-determined control of data use.",routePath:"/glossary",children:"IDS"}
1)," Protocol as described in CX-0018.\nThe ",(0,i.jsx)(r.A,{term:"Tractus-X EDC",definition:"The Tractus-X Eclipse Dataspace Connector (Tractus-X EDC) is a reference implementation for a connector conformant to CX-0018 and acts as a de-facto standard/reference implementation within Catena-X; other CX-0018-conformant connectors are also valid options.",routePath:"/glossary",children:"Tractus-X EDC"})," as a reference implementation is ",(0,i.jsx)(t.strong,{children:"RECOMMENDED"})," to be used as a connector conformant to CX-0018."]}),"\n",(0,i.jsx)(t.h4,{id:"213-additional-requirements",children:"2.1.3 ADDITIONAL REQUIREMENTS"}),"\n",(0,i.jsxs)(t.p,{children:["As the ",(0,i.jsx)(r.A,{term:"IDS",definition:"The International Data Space enables 'smart services' and business processes across companies and industries while ensuring data sovereignty and self-determined control of data use.",routePath:"/glossary",children:"IDS"})," protocol is being used, data ",(0,i.jsx)(t.strong,{children:"MUST NOT"})," be transferred before a corresponding contract negotiation has been successfully passed by the participants of the data exchange and a valid contract is present as described in CX-0018.\nThe required data offers ",(0,i.jsx)(t.strong,{children:"MUST"})," be discoverable through the decentral Digital Twin Registry as submodel endpoints."]}),"\n",(0,i.jsx)(t.h4,{id:"policy-constraints-for-data-exchange",children:"POLICY CONSTRAINTS FOR DATA EXCHANGE"}),"\n",(0,i.jsxs)(t.p,{children:["In alignment with our commitment to data sovereignty, a specific framework governing the utilization of data within the Catena-X use cases has been outlined. As part of this data sovereignty framework, conventions for access policies, for usage policies and for the constraints contained in the policies have been specified in standard 'CX-0152 Policy Constraints for Data Exchange'. This standard document CX-0152 ",(0,i.jsx)(t.strong,{children:"MUST"})," be followed when providing services or apps for data sharing/consuming and when sharing or consuming data in the Catena-X ecosystem. What conventions are relevant for what roles named in ",(0,i.jsx)(t.a,{href:"#11-audience--scope",children:"1.1 AUDIENCE & SCOPE"})," is specified in the CX-0152 standard document as well. CX-0152 can be found in the ",(0,i.jsx)(t.a,{href:"https://catenax-ev.github.io/docs/standards/overview",children:"standard library"}),"."]}),"\n",(0,i.jsx)(t.h5,{id:"versioning",children:"Versioning"}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect Models"})," that are deployed as Digital Twins ",(0,i.jsx)(t.strong,{children:"MUST"})," be published in ",(0,i.jsxs)(t.a,{href:"http://www.w3.org/ns/dcat#",children:["dcat",":Dataset"]})," in the property that holds the full URN of the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect Model"})," ",(0,i.jsx)(t.a,{href:"https://admin-shell.io/aas/3/0/HasSemantics/semanticId",children:"https://admin-shell.io/aas/3/0/HasSemantics/semanticId"}),". Versions are explicitly contained in the URN.\nThe ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," versions ",(0,i.jsx)(t.strong,{children:"MUST"})," be published in the property ",(0,i.jsx)(t.a,{href:"https://w3id.org/catenax/ontology/common#version",children:"https://w3id.org/catenax/ontology/common#version"})," as version X.Y in ",(0,i.jsxs)(t.a,{href:"http://www.w3.org/ns/dcat#",children:["dcat",":Dataset"]}),".\nNote: Data ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"Assets"})," differentiated only by major version ",(0,i.jsx)(t.strong,{children:"MUST"})," be offered in parallel. The current standard and ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," versions mark the start of Life Cycle Management in Catena-X operations. Previous versions are dismissed."]}),"\n",(0,i.jsx)(t.h4,{id:"214-digital-twins-and-specific-asset-ids",children:"2.1.4 DIGITAL TWINS AND SPECIFIC ASSET IDs"}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"asset"}),"'s globalAssetId ",(0,i.jsx)(t.strong,{children:"MUST"})," be equal to the unique id used in Catena-X."]}),"\n",(0,i.jsxs)(t.p,{children:["The following specific ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"asset"})," ",(0,i.jsx)(r.A,{term:"IDS",definition:"The International Data Space enables 'smart services' and business processes across companies and industries while ensuring data sovereignty and self-determined control of data use.",routePath:"/glossary",children:"IDs"})," not marked as optional ",(0,i.jsx)(t.strong,{children:"MUST"})," be available in the decentral Digital Twin Registry when registering a digital twin or when adding the above mentioned submodels to an existing twin for a ",(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instance"})," in order to allow searching for that specific ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"asset"})," ID (see CX-0002 for additional information). The specific ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"asset"})," ",(0,i.jsx)(r.A,{term:"IDS",definition:"The International Data Space enables 'smart services' and business processes across companies and industries while ensuring data sovereignty and self-determined control of data use.",routePath:"/glossary",children:"IDs"})," marked as optional ",(0,i.jsx)(t.strong,{children:"MAY"})," be used in addition."]}),"\n",(0,i.jsxs)(t.p,{children:["The following conventions for specific ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"Asset"})," ",(0,i.jsx)(r.A,{term:"IDS",definition:"The International Data Space enables 'smart services' and business processes across companies and industries while ensuring data sovereignty and self-determined control of data use.",routePath:"/glossary",children:"IDs"})," apply to all digital twins:"]}),"\n",(0,i.jsxs)("table",{children:[(0,i.jsxs)("tr",{children:[(0,i.jsx)("th",{children:" Key "}),(0,i.jsx)("th",{children:" Availability "}),(0,i.jsx)("th",{children:" Description "}),(0,i.jsx)("th",{children:" Type "})]}),(0,i.jsxs)("tr",{children:[(0,i.jsx)("td",{children:" manufacturerId "}),(0,i.jsx)("td",{children:" Mandatory "}
1),(0,i.jsx)("td",{children:" The Business Partner Number (BPNL) of the manufacturer of the part. "}),(0,i.jsx)("td",{children:" BPNL "})]}),(0,i.jsxs)("tr",{children:[(0,i.jsx)("td",{children:" manufacturerPartId "}),(0,i.jsx)("td",{children:" Mandatory "}),(0,i.jsxs)("td",{children:[" The ID of the type/catalog part from the ",(0,i.jsx)(t.em,{children:(0,i.jsx)(t.strong,{children:"manufacturer"})}),". "]}),(0,i.jsx)("td",{children:" String "})]}),(0,i.jsxs)("tr",{children:[(0,i.jsx)("td",{children:" customerPartId "}),(0,i.jsx)("td",{children:" Optional"}),(0,i.jsxs)("td",{children:[" The ID of the type/catalog part from the ",(0,i.jsx)(t.em,{children:(0,i.jsx)(t.strong,{children:(0,i.jsx)(r.A,{term:"Customer",definition:"In the context of OSim, the receiver of produced goods from a supplier.",routePath:"/glossary",children:"customer"})})}),".",(0,i.jsx)("br",{}),(0,i.jsx)("br",{}),"The main reason why this property is optional is that it cannot be guaranteed that every manufacturer knows the customerPartId for their parts. If known, it is ",(0,i.jsx)(t.em,{children:(0,i.jsx)(t.strong,{children:"recommended"})})," to always add the customerPartId for easier lookup.",(0,i.jsx)("br",{})]}),(0,i.jsx)("td",{children:" String "})]}),(0,i.jsxs)("tr",{children:[(0,i.jsx)("td",{children:" digitalTwinType "}),(0,i.jsx)("td",{children:" Mandatory "}),(0,i.jsxs)("td",{children:[" The types of the digital twin: ",(0,i.jsxs)("ul",{children:[(0,i.jsx)("li",{children:'"PartInstance" for serialized parts, batches, and JIS parts'}),(0,i.jsx)("li",{children:'"PartType" for catalog parts'})]})," DigitalTwinType was added to allow data consumers to search for all digital twins of a particular type, e.g, only for catalog parts by using ",(0,i.jsx)(t.code,{children:'digitalTwinType="PartType"'})," as filter. Without this filter, a search for a particular manufacturer part ID would not only return the digital twin of the catalog part, but also all digital twins of instances of this catalog part, i.e., of the corresponding serial parts."]}),(0,i.jsx)("td",{children:" String "})]})]}),"\n",(0,i.jsx)(t.p,{children:(0,i.jsxs)(t.strong,{children:["For ",(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized parts"}),", additionally the following conventions apply:"]})}),"\n",(0,i.jsxs)(t.table,{children:[(0,i.jsx)(t.thead,{children:(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Key"}),(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Availability"}),(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Description"}),(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Type"})]})}),(0,i.jsxs)(t.tbody,{children:[(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"partInstanceId"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"Mandatory"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"The serial number of the part from the manufacturer."}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"String"})]}),(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"intrinsicId"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"Mandatory"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"The serial number of the part from the manufacturer."}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"String"})]}),(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.td,{style:{textAlign:"left"},children:(0,i.jsx)(r.A,{term:"VAN",definition:"A number mapped 1:1 to a VIN but pseudonymised to protect vehicle identity.",routePath:"/glossary",children:"van"})}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"Optional"}),(0,i.jsxs)(t.td,{style:{textAlign:"left"},children:[(0,i.jsx)(t.strong,{children:"Only for vehicles:"})," The pseudonymized vehicle identification number (",(0,i.jsx)(r.A,{term:"VIN",definition:"A VIN is a 17-character code assigned by the manufacturer to every vehicle; it encodes the vehicle's make, model, year of manufacture and other identifying features and serves as a unique identifier throughout the vehicle's lifespan.",routePath:"/glossary",children:"VIN"}),") of the vehicle."]}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"String"})]})]})]}),"\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.strong,{children:"For batches, additionally the following conventions apply:"})}),"\n",(0,i.jsxs)(t.table,{children:[(0,i.jsx)(t.thead,{children:(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Key"}),(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Availability"}),(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Description"}),(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Type"})]})}),(0,i.jsxs)(t.tbody,{children:[(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"batchId"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"Mandatory"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"The number of the batch from the manufacturer."}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"String"})]}),(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"intrinsicId"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"Mandatory"}),(0,i.jsxs)(t.td,{style:{textAlign:"left"},children:["Also the number of the batch from the manufacturer.",(0,i.jsx)("br",{}),(0,i.jsx)("br",{}),"Currently, we also use the batch number as intrinsicId. This makes looking up digital twins for ",(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized parts"})," and batches easier as a data consumer only has to specify the intrinsicId no matter if they are looking up a ",(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized part"})," or a batch. Otherwise, the data consumer would need to know for what type of digital twin it is looking for or it would have to look for both until a match is found."]}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"String"})]})]})]}),"\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.strong,{children:"For just-in-sequence-parts, additionally the following conventions apply:"})}),"\n",(0,i.jsxs)(t.table,{children:[(0,i.jsx)(t.thead,{children:(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Key"}),(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Availability"}),(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Description"}),(0,i.jsx)(t.th,{style:{textAlign:"left"},children:"Type"})]})}),(0,i.jsxs)(t.tbody,{children:[(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"parentOrderNumber"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"Optional"}),(0,i.jsxs)(t.td,{style:{textAlign:"left"},children:["A number identifying the just-in-sequence- part's destination parent part. The parent part is typically known upfront to the ",(0,i.jsx)(r.A,{term:"Supplier",definition:"In the context of OSim, the producer of goods.",routePath:"/glossary",children:"supplier"})," for just-in-sequence parts."]}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"String"})]}),(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"jisNumber"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"Mandatory"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"A number that is used to identify the call-off that can be assumed unique within the specific just-in-sequence process. This is typically not the sequence number, but the call-off number."}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"String"})]}),(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"jisCallDate"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"Optional"}),(0,i.jsxs)(t.td,{style:{textAlign:"left"},children:["The date of the just-in-sequence call-off as stated on the call-off document itself. ",(0,i.jsx)("br",{}),"The value must be compliant to ISO 8601: ",(0,i.jsx)(t.code,{children:"YYYY-MM-DD"})," or ",(0,i.jsx)(t.code,{children:"YYYY-MM-DDThh:mm:ss"})," or ",(0,i.jsx)(t.code,{children:"YYYY-MM-DDThh:mm:ss\xb1hh:mm"})]}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"Date"})]}),(0,i.jsxs)(t.tr,{children:[(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"intrinsicId"}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"Mandatory"}),(0,i.jsxs)(t.td,{style:{textAlign:"left"},children:["A composition of ",(0,i.jsx)(t.code,{children:"jisNumber"}),", ",(0,i.jsx)(t.code,{children:"parentOrderNumber"})," (if available), ",(0,i.jsx)(t.code,{children:"jisCallDate"})," (if available). This information is typically known upfront to the ",(0,i.jsx)(r.A,{term:"Supplier",definition:"In the context of OSim, the producer of goods.",routePath:"/glossary",children:"supplier"})," ",(0,i.jsx)(t.code,{children:"jisNumber"}),", ",(0,i.jsx)(t.code,{children:"partOrderNumber"})," and ",(0,i.jsx)(t.code,{children:"jisCallDate"})," for just-in-sequence parts."]}),(0,i.jsx)(t.td,{style:{textAlign:"left"},children:"String"})]})]})]}),"\n",(0,i.jsxs)(t.p,{children:["A digital twin is required for each single instance of a ",(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized part"}),", just-in-sequence-part or vehicle and each batch to be traced."]}),"\n",(0,i.jsx)(t.h5,{id:"authorization-visbility-of-specific-asset-ids-in-the-dtr",children:"Authorization: Visbility of Specific Asset IDs in the DTR"}),"\n",(0,i.jsxs)(t.p,{children:["To enforce a strict need-to-know (and prevent data from being exposed to non-authorized parties), the visibility of entr
1ies in the attribute ",(0,i.jsx)(t.code,{children:"specificAssetIds"})," ",(0,i.jsx)(t.a,{href:"https://admin-shell.io/aas/3/0/AssetInformation/specificAssetIds",children:"https://admin-shell.io/aas/3/0/AssetInformation/specificAssetIds"})," must be protected, i.e.,their visibility must be restricted to only the manufacturer of the part (which is represented by the digital twin) and the ",(0,i.jsx)(r.A,{term:"Customer",definition:"In the context of OSim, the receiver of produced goods from a supplier.",routePath:"/glossary",children:"customers"})," of the part. For that, the attribute ",(0,i.jsx)(t.code,{children:"externalSubjectIds"})," (",(0,i.jsx)(t.a,{href:"https://admin-shell.io/aas/3/0/SpecificAssetId/externalSubjectId",children:"https://admin-shell.io/aas/3/0/SpecificAssetId/externalSubjectId"}),") must be used. For more information on the semantics of the mentioned properties, see AAS Pt. 1. For more information on the use of Digital Twins in Catena-X, see CX - 0002."]}),"\n",(0,i.jsx)(t.h2,{id:"3-aspect-models",children:"3 ASPECT MODELS"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is normative"})}),"\n"]}),"\n",(0,i.jsx)(t.p,{children:"Relevant semantic models of this standard are:"}),"\n",(0,i.jsxs)(t.ul,{children:["\n",(0,i.jsx)(t.li,{children:"SerialPart"}),"\n",(0,i.jsx)(t.li,{children:"Batch"}),"\n",(0,i.jsx)(t.li,{children:"JustInSequencePart"}),"\n",(0,i.jsx)(t.li,{children:"SingleLevelBomAsBuilt"}),"\n",(0,i.jsx)(t.li,{children:"SingleLevelUsageAsBuilt"}),"\n"]}),"\n",(0,i.jsxs)(t.p,{children:["Semantic models ",(0,i.jsx)(t.strong,{children:"MAY"})," be used individually or together."]}),"\n",(0,i.jsxs)(t.p,{children:["Semantic models ",(0,i.jsx)(t.strong,{children:"MUST"})," be made available in the central Semantic Hub."]}),"\n",(0,i.jsxs)(t.p,{children:["Data consumers and data provider ",(0,i.jsx)(t.strong,{children:"MUST"})," comply with the license of the semantic models."]}),"\n",(0,i.jsxs)(t.p,{children:["The submodel data ",(0,i.jsx)(t.strong,{children:"MUST"})," be requested and exchanged via a CX-0018 and CX-0002 compliant connector (e.g. Ecplise Dataspace Connector)."]}),"\n",(0,i.jsxs)(t.p,{children:["Data providers ",(0,i.jsx)(t.strong,{children:"MUST"})," provide data as part of a digital twin of the ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"asset"})," for ",(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized parts"})," conformant to CX \u2013 0002 DIGITAL TWINS IN CATENA-X."]}),"\n",(0,i.jsxs)(t.p,{children:["The JSON Payloads of data providers ",(0,i.jsx)(t.strong,{children:"MUST"})," be conformant to the JSON Schemas as specified in this document."]}),"\n",(0,i.jsxs)(t.p,{children:["The unique identifier of the semantic model specified in this document ",(0,i.jsx)(t.strong,{children:"MUST"})," be used by the data provider to define the semantics of the data being transferred."]}),"\n",(0,i.jsx)(t.h3,{id:"31-aspect-model-serialpart",children:'3.1 ASPECT MODEL "SerialPart"'}),"\n",(0,i.jsx)(t.h4,{id:"311-introduction",children:"3.1.1 INTRODUCTION"}),"\n",(0,i.jsxs)(t.p,{children:["The semantic model SerialPart describes a submodel for a digital twin of a serialised part providing essential information about this part. A ",(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"serialized part"})," is an instance of a part, where the particular instance can be uniquely identified by means of a serial number, a similar identifier (e.g. ",(0,i.jsx)(r.A,{term:"VAN",definition:"A number mapped 1:1 to a VIN but pseudonymised to protect vehicle identity.",routePath:"/glossary",children:"VAN"}),") or a combination of multiple identifiers (e.g. combination of manufacturer, date and number).\nMore specific, the model links local identifiers like manufacturerPartId, customerPartId and other data like manufacturing information and part type information to the actual catenaXId from Catena-X, which is a UUIDv4.\nThis allows decoupling of the network identifiers from the actual business process.\nBy accessing this aspect you can link a physical part to its representation within Catena-X."]}),"\n",(0,i.jsxs)(t.p,{children:["Note: The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect model"})," SerialPart ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," is ",(0,i.jsx)(t.strong,{children:"mandatory"}),". Versions higher than that are ",(0,i.jsx)(t.strong,{children:"optional"}),", but might become mandatory in future releases of this standard."]}),"\n",(0,i.jsxs)(t.p,{children:["For the changelog of the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),", ",(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.serial_part/RELEASE_NOTES.md",children:"see here"}),"."]}),"\n",(0,i.jsx)(t.h4,{id:"312-specifications-artifacts",children:"3.1.2 SPECIFICATIONS ARTIFACTS"}),"\n",(0,i.jsxs)(t.p,{children:['The modeling of the semantic model specified in this document was done in accordance to the "semantic driven workflow" to create a submodel template specification ',(0,i.jsx)(t.a,{href:"#62-non-normative-references",children:"SMT"}),"."]}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"})," is written in SAMM 2.1.0 as a modeling language conformant to CX-0003 as input for the semantic driven workflow."]}),"\n",(0,i.jsx)(t.p,{children:"Like all Catena-X data models, this model is available in a machine-readable format on GitHub\nconformant to CX-0003."}),"\n",(0,i.jsx)(t.h4,{id:"313-license",children:"3.1.3 LICENSE"}),"\n",(0,i.jsxs)(t.p,{children:["This Catena-X data model is an outcome of Catena-X use case group\nIndustry Core. This Catena-X data model is made available under the terms\nof the Creative
1Commons Attribution 4.0 International (CC-BY-4.0)\nlicense, which is available at Creative Commons",(0,i.jsx)(t.sup,{children:(0,i.jsx)(t.a,{href:"#user-content-fn-2",id:"user-content-fnref-2","data-footnote-ref":!0,"aria-describedby":"footnote-label",children:"1"})}),"."]}),"\n",(0,i.jsx)(t.p,{children:"The license information is available in github."}),"\n",(0,i.jsx)(t.p,{children:"In case of doubt the license, copyright and authors information in\ngithub overwrites the information in this specification document."}),"\n",(0,i.jsx)(t.h4,{id:"314-identifier-of-semantic-model",children:"3.1.4 IDENTIFIER OF SEMANTIC MODEL"}),"\n",(0,i.jsx)(t.p,{children:"The semantic model has the unique identifier"}),"\n",(0,i.jsxs)(t.p,{children:["SerialPart ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," (mandatory)"]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-text",children:"urn:samm:io.catenax.serial_part:3.0.0#SerialPart \n"})}),"\n",(0,i.jsx)(t.h4,{id:"315-formats-of-semantic-model",children:"3.1.5 FORMATS OF SEMANTIC MODEL"}),"\n",(0,i.jsx)(t.h5,{id:"3151-rdf-turtle",children:"3.1.5.1 RDF TURTLE"}),"\n",(0,i.jsx)(t.p,{children:"The rdf turtle file, an instance of the Semantic Aspect Meta Model, is the master for generating additional file formats and serializations. These can be viewed by following links:"}),"\n",(0,i.jsxs)(t.p,{children:["SerialPart ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," (mandatory)"]}),"\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.serial_part/3.0.0/SerialPart.ttl",children:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.serial_part/3.0.0/SerialPart.ttl"})}),"\n",(0,i.jsxs)(t.p,{children:["The open source command line tool of the Eclipse Semantic Modeling Framework",(0,i.jsx)(t.sup,{children:(0,i.jsx)(t.a,{href:"#user-content-fn-3",id:"user-content-fnref-3","data-footnote-ref":!0,"aria-describedby":"footnote-label",children:"2"})})," is used for generation of other file formats like for example a JSON Schema, aasx for ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," Submodel Template or a HTML documentation."]}),"\n",(0,i.jsx)(t.h5,{id:"3152-json-schema",children:"3.1.5.2 JSON SCHEMA"}),"\n",(0,i.jsxs)(t.p,{children:["A JSON Schema can be generated from the RDF Turtle file. The JSON Schema defines the Value-Only\npayload of the ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," for the ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"}),' operation "GetSubmodel".']}),"\n",(0,i.jsx)(t.h5,{id:"3153-aasx",children:"3.1.5.3 AASX"}),"\n",(0,i.jsxs)(t.p,{children:["An AASX file can be generated from the RDF Turtle file. The AASX file defines one of the requested\nartifacts for a Submodel Template Specification conformant to [",(0,i.jsx)(t.a,{href:"#62-non-normative-references",children:"SMT"}),"]."]}),"\n",(0,i.jsx)(t.h4,{id:"316-example-data",children:"3.1.6 EXAMPLE DATA"}),"\n",(0,i.jsxs)(t.p,{children:["Example JSON payload: Submodel ",(0,i.jsx)(t.strong,{children:'"SerialPart" v3.0.0 for a vehicle'})]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-json",children:'{\n "localIdentifiers": [\n {\n "key": "manufacturerId",\n "value": "BPNL7588787849VQ"\n },\n {\n "key": "manufacturerPartId",\n "value": "95657362-83"\n },\n {\n "key": "partInstanceId",\n "value": "OEM-A-F8LM95T92WJ9KNDD3HA5P"\n },\n {\n "key": "van",\n "value": "OEM-A-F8LM95T92WJ9KNDD3HA5P"\n }\n ],\n "manufacturingInformation": {\n "date": "2022-02-04T14:48:54",\n "country": "DEU",\n "sites": [\n {\n "catenaXsiteId": "BPNS1234567890ZZ",\n "function": "production"\n }\n ]\n },\n "catenaXId": "urn:uuid:580d3adf-1981-44a0-a214-13d6ceed9379",\n "partTypeInformation": {\n "manufacturerPartId": "95657362-83",\n "nameAtManufacturer": "Vehicle Model A",\n "partClassification": [\n {\n "classificationStandard": "GIN 20510-21513",\n "classificationID": "1004712",\n "classificationDescription": "Generic standard for classification of parts in the automotive industry."\n },\n {\n "classificationStandard": "OEM Part Classification 1022-102",\n "classificationID": "Electric vehicle",\n "classificationDescription": "OEM standard for classification of parts."\n }\n ],\n }\n}\n'})}),"\n",(0,i.jsxs)(t.p,{children:["Example JSON payload: Submodel ",(0,i.jsxs)(t.strong,{children:['"SerialPart" v3.0.0 for a ',(0,i.jsx)(r.A,{term:"Serialized part",definition:"An instance of a part which can be uniquely identified by means of a serial number, a similar identifier (e.g., VAN), or a combination of identifiers (e.g., manufacturer + date + number).",routePath:"/glossary",children:"Serialized Part"})," (Non-Vehicle)"]})]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-json",children:'{\n "localIdentifiers": [\n {\n "key": "manufacturerId",\n "value": "BPNL7588787849VQ"\n },\n {\n "key": "manufacturerPartId",\n "value": "95657362-83"\n },\n {\n "key": "partInstanceId",\n "value": "NO-574868639429552535768526"\n }\n ],\n "manufacturingInformation": {\n "date": "2022-02-04T14:48:54",\n "country": "DEU",\n "sites": [\n {\n "catenaXsiteId": "BPNS1234567890ZZ",\n "function": "production"\n }\n ]\n },\n "catenaXId": "urn:uuid:d60b99b0-f269-42f5-94d0-64fe0946ed04",\n "partTypeInformation": {\n "manufacturerPartId": "95657362-83",\n "customerPartId": "798-515297795-A",\n "nameAtManufacturer": "High Voltage Battery",\n "nameAtCustomer": "High Voltage Battery",\n "partClassification": [\n {\n "classificationStandard": "GIN 20510-21513",\n "classificationID": "1004713",\n "classificationDescription": "Generic standard for classification of parts in the automotive industry."\n },\n {\n "classificationStandard": "OEM Part Classification 1022-102",\n "classificationID": "Traction Battery",\n "classificationDescription": "OEM standard for classification of parts."\n }\n ],\n }\n}\n'})}),"\n",(0,i.jsx)(t.h3,{id:"32-aspect-model-batch",children:'3.2 ASPECT MODEL "Batch"'}),"\n",(0,i.jsx)(t.h4,{id:"321-introduction",children:"3.2.1 INTRODUCTION"}),"\n",(0,i.jsx)(t.p,{children:"A batch is a quantity of (semi-) finished products or (raw) material\nproduct that have been produced under the same circumstances (e.g., same\nproduction location), as specified groups or amounts, within a certain\ntime frame. Every batch can differ in the number or amount of products.\nDifferent batches can have varied specifications, e.g., different\ncolors, quality, etc. A batch is identified via a Batch ID."}),"\n",(0,i.jsxs)(t.p,{children:["This submodel template or ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"})," is required to identify a batch\nof materials within Catena-X."]}),"\n",(0,i.jsx)(t.p,{children:"It links local identifiers like manufacturerPartId and batchId to\nthe actual Catena-X ID."}),"\n",(0,i.jsx)(t.p,{children:"This allows decoupling of the Catena-X identifiers from the actual\nbusiness process."}),"\n",(0,i.jsx)(t.p,{children:"By accessing this aspect you can link a physical batch of parts to its\nrepresentation within in Catena-X."}),"\n",(0,i.jsxs)(t.p,{children:["Note: The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect model"})," Batch ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," is ",(0,i.jsx)(t.strong,{children:"mandatory"}),". Versions higher than that are ",(0,i.jsx)(t.strong,{children:"optional"}),", but might become mandatory in future releases of this standard."]}),"\n",(0,i.jsxs)(t.p,{children:["For the changelog of the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),", ",(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.batch/RELEASE_NOTES.md",children:"see here"}),"."]}),"\n",(0,i.jsx)(t.h4,{id:"322-specifications-artifacts",children:"3.2.2 SPECIFICATIONS ARTIFACTS"}),"\n",(0,i.jsxs)(t.p,{children:['The modeling of the semantic model specified in this document was done in accordance to the "semantic driven workflow" to create a submodel template specification ',(0,i.jsx)(t.a,{href:"#62-non-normative-references",children:"SMT"}),"."]}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"})," is written in SAMM 2.1.0 as a modeling language conformant to CX-0003 as input for the semantic driven workflow."]}),"\n",(0,i.jsx)(t.p,{children:"Like all Catena-X data models, this model is available in a machine-readable format on GitHub\nconformant to CX-0003."}),"\n",(0,i.jsx)(t.h4,{id:"323-license",children:"3.2.3 LICENSE"}),"\n",(0,i.jsxs)(t.p,{children:["This Catena-X data model is an outcome of Catena-X use case group\nIndustry Core. This Catena-X data model is made available under the terms\nof the Creative
1Commons Attribution 4.0 International (CC-BY-4.0)\nlicense, which is available at Creative Commons",(0,i.jsx)(t.sup,{children:(0,i.jsx)(t.a,{href:"#user-content-fn-2",id:"user-content-fnref-2-2","data-footnote-ref":!0,"aria-describedby":"footnote-label",children:"1"})}),"."]}),"\n",(0,i.jsx)(t.p,{children:"The license information is available in github."}),"\n",(0,i.jsx)(t.p,{children:"In case of doubt the license, copyright and authors information in\ngithub overwrites the information in this specification document."}),"\n",(0,i.jsx)(t.h4,{id:"324-identifier-of-semantic-model",children:"3.2.4 IDENTIFIER OF SEMANTIC MODEL"}),"\n",(0,i.jsxs)(t.p,{children:["The semantic model has the unique identifier\nBatch ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," (mandatory)"]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-text",children:"urn:samm:io.catenax.batch:3.0.0#Batch\n"})}),"\n",(0,i.jsx)(t.h4,{id:"325-formats-of-semantic-model",children:"3.2.5 FORMATS OF SEMANTIC MODEL"}),"\n",(0,i.jsx)(t.h5,{id:"3251-rdf-turtle",children:"3.2.5.1 RDF TURTLE"}),"\n",(0,i.jsx)(t.p,{children:"The rdf turtle file, an instance of the Semantic Aspect Meta Model, is\nthe master for generating additional file formats and serializations. These can be viewed by following links:"}),"\n",(0,i.jsxs)(t.p,{children:["Batch ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," (mandatory)"]}),"\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.batch/3.0.0/Batch.ttl",children:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.batch/3.0.0/Batch.ttl"})}),"\n",(0,i.jsx)(t.h5,{id:"3252-json-schema",children:"3.2.5.2 JSON SCHEMA"}),"\n",(0,i.jsxs)(t.p,{children:["A JSON Schema can be generated from the RDF Turtle file. The JSON Schema defines the Value-Only\npayload of the ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," for the ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"}),' operation "GetSubmodel".']}),"\n",(0,i.jsx)(t.h5,{id:"3253-aasx",children:"3.2.5.3 AASX"}),"\n",(0,i.jsxs)(t.p,{children:["An AASX file can be generated from the RDF Turtle file. The AASX file defines one of the requested\nartifacts for a Submodel Template Specification conformant to [",(0,i.jsx)(t.a,{href:"#62-non-normative-references",children:"SMT"}),"]."]}),"\n",(0,i.jsx)(t.h4,{id:"326-example-data",children:"3.2.6 EXAMPLE DATA"}),"\n",(0,i.jsxs)(t.p,{children:["Example JSON payload: Submodel ",(0,i.jsx)(t.strong,{children:'"Batch" v3.0.0'})]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-json",children:'{\n "localIdentifiers": [\n {\n "value": "BID12345678",\n "key": "batchId"\n },\n {\n "value": "123-0.740-3434-A",\n "key": "manufacturerPartId"\n },\n ],\n "manufacturingInformation": {\n "date": "2022-02-04T14:48:54",\n "country": "HUR",\n "sites": [\n {\n "catenaXsiteId": "BPNS1234567890ZZ",\n "function": "production"\n }\n ]\n },\n "catenaXId": "urn:uuid:580d3adf-1981-44a0-a214-13d6ceed9379",\n "partTypeInformation": {\n "partClassification": [\n {\n "classificationStandard": "GIN 20510-21513",\n "classificationID": "1004714",\n "classificationDescription": "Generic standard for classification of parts in the automotive industry."\n },\n {\n "classificationStandard": "OEM Part Classification 1022-102",\n "classificationID": "Two-component adhesive",\n "classificationDescription": "OEM standard for classification of parts."\n }\n ],\n "manufacturerPartId": "123-0.740-3434-A",\n "nameAtManufacturer": "PA66-GF30"\n }\n}\n'})}),"\n",(0,i.jsx)(t.h3,{id:"33-aspect-model-justinsequencepart",children:'3.3 ASPECT MODEL "JustInSequencePart"'}),"\n",(0,i.jsx)(t.h4,{id:"331-introduction",children:"3.3.1 INTRODUCTION"}),"\n",(0,i.jsxs)(t.p,{children:["This submodel template or ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"})," is required to identify a just-in-sequence-part within Catena-X (that do not have a dedicated serial number).\nIt links local identifiers like manufacturerPartId, jisNumber and jisCallDate to\nthe actual Catena-X ID.\nThis allows decoupling of the Catena-X identifiers from the actual\nbusiness process.\nBy accessing this aspect you can link a physical just-in-sequence-part to its\nrepresentation within in Catena-X."]}),"\n",(0,i.jsxs)(t.p,{children:["For just-in-sequence-parts with an existing serial number, the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"})," SerialPart is applied, not JustInSequencePart."]}),"\n",(0,i.jsxs)(t.p,{children:["Note: The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect model"})," JustInSequencePart ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," is ",(0,i.jsx)(t.strong,{children:"mandatory"}),". Versions higher than that are ",(0,i.jsx)(t.strong,{children:"optional"}),", but might become mandatory in future releases of this standard."]}),"\n",(0,i.jsxs)(t.p,{children:["For the changelog of the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),", ",(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.just_in_sequence_part/RELEASE_NOTES.md",children:"see here"}),"."]}),"\n",(0,i.jsx)(t.h4,{id:"332-specifications-artifacts",children:"3.3.2 SPECIFICATIONS ARTIFACTS"}),"\n",(0,i.jsxs)(t.p,{children:['The modeling of the semantic model specified in this document was done in accordance to the "semantic driven workflow" to create a submodel template specification ',(0,i.jsx)(t.a,{href:"#62-non-normative-references",children:"SMT"}),"."]}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"})," is written in SAMM 2.1.0 as a modeling language conformant to CX-0003 as input for the semantic driven workflow."]}),"\n",(0,i.jsx)(t.p,{children:"Like all Catena-X data models, this model is available in a machine-readable format on GitHub\nconformant to CX-0003."}),"\n",(0,i.jsx)(t.h4,{id:"333-license",children:"3.3.3 LICENSE"}),"\n",(0,i.jsxs)(t.p,{children:["This Catena-X data model is an outcome of Catena-X use case group\nIndustry Core. This Catena-X data model is made available under the terms\nof the Creative
1Commons Attribution 4.0 International (CC-BY-4.0)\nlicense, which is available at Creative Commons",(0,i.jsx)(t.sup,{children:(0,i.jsx)(t.a,{href:"#user-content-fn-2",id:"user-content-fnref-2-3","data-footnote-ref":!0,"aria-describedby":"footnote-label",children:"1"})}),"."]}),"\n",(0,i.jsx)(t.p,{children:"The license information is available in github."}),"\n",(0,i.jsx)(t.p,{children:"In case of doubt the license, copyright and authors information in\ngithub overwrites the information in this specification document."}),"\n",(0,i.jsx)(t.h4,{id:"334-identifier-of-semantic-model",children:"3.3.4 IDENTIFIER OF SEMANTIC MODEL"}),"\n",(0,i.jsx)(t.p,{children:"The semantic model has the unique identifier"}),"\n",(0,i.jsxs)(t.p,{children:["JustInSequencePart ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," (mandatory)"]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-text",children:"urn:samm:io.catenax.just_in_sequence_part:3.0.0#JustInSequencePart\n"})}),"\n",(0,i.jsx)(t.h4,{id:"335-formats-of-semantic-model",children:"3.3.5 FORMATS OF SEMANTIC MODEL"}),"\n",(0,i.jsx)(t.h5,{id:"3351-rdf-turtle",children:"3.3.5.1 RDF TURTLE"}),"\n",(0,i.jsx)(t.p,{children:"The rdf turtle file, an instance of the Semantic Aspect Meta Model, is\nthe master for generating additional file formats and serializations. These can be viewed by following links:"}),"\n",(0,i.jsxs)(t.p,{children:["JustInSequencePart ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," (mandatory)"]}),"\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.just_in_sequence_part/3.0.0/JustInSequencePart.ttl",children:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.just_in_sequence_part/3.0.0/JustInSequencePart.ttl"})}),"\n",(0,i.jsxs)(t.p,{children:["The open source command line tool of the Eclipse Semantic Modeling Framework",(0,i.jsx)(t.sup,{children:(0,i.jsx)(t.a,{href:"#user-content-fn-3",id:"user-content-fnref-3-2","data-footnote-ref":!0,"aria-describedby":"footnote-label",children:"2"})})," is used for generation of other file formats like for example a JSON Schema, aasx for ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," Submodel Template or a HTML documentation."]}),"\n",(0,i.jsx)(t.h5,{id:"3352-json-schema",children:"3.3.5.2 JSON SCHEMA"}),"\n",(0,i.jsxs)(t.p,{children:["A JSON Schema can be generated from the RDF Turtle file. The JSON Schema defines the Value-Only\npayload of the ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," for the ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"}),' operation "GetSubmodel".']}),"\n",(0,i.jsx)(t.h5,{id:"3353-aasx",children:"3.3.5.3 AASX"}),"\n",(0,i.jsxs)(t.p,{children:["An AASX file can be generated from the RDF Turtle file. The AASX file defines one of the requested\nartifacts for a Submodel Template Specification conformant to [",(0,i.jsx)(t.a,{href:"#62-non-normative-references",children:"SMT"}),"]."]}),"\n",(0,i.jsx)(t.h4,{id:"336-example-data",children:"3.3.6 EXAMPLE DATA"}),"\n",(0,i.jsxs)(t.p,{children:["Example JSON payload: Submodel ",(0,i.jsx)(t.strong,{children:'"JustInSequencePart" v3.0.0'})]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-json",children:'{\n "localIdentifiers": [\n {\n "key": "manufacturerId",\n "value": "BPNL7588787849VQ"\n },\n {\n "key": "jisNumber",\n "value": "894651684"\n },\n {\n "key": "parentOrderNumber",\n "value": "OEM-A-F8LM95T92WJ9KNDD3HA5P"\n },\n {\n "key": "manufacturerPartId",\n "value": "84816168424"\n },\n {\n "key": "nameAtManufacturer",\n "value": "Black Leather Front Row Seat for Vehicle Model B"\n },\n {\n "key": "jisCallDate",\n "value": "2022-01-24T09:13:34"\n }\n ],\n "manufacturingInformation": {\n "date": "2022-02-04T14:48:54",\n "country": "DEU",\n "sites": [\n {\n "catenaXsiteId": "BPNS1234567890ZZ",\n "function": "production"\n }\n ]\n },\n "catenaXId": "urn:uuid:580d3adf-1981-44a0-a214-13d6ceed9379",\n "partTypeInformation": {\n "partClassification": [\n {\n "classificationStandard": "GIN 20510-21513",\n "classificationID": "1004715",\n "classificationDescription": "Generic standard for classification of parts in the automotive industry."\n },\n {\n "classificationStandard": "OEM Part Classification 1022-102",\n "classificationID": "Front row seat",\n "classificationDescription": "OEM standard for classification of parts."\n }\n ],\n "manufacturerPartId": "84816168424",\n "nameAtManufacturer": "Black Leather Front Row Seat for Vehicle Model B",\n }\n}\n'})}),"\n",(0,i.jsx)(t.h3,{id:"34-aspect-model-singlelevelbomasbuilt",children:'3.4 ASPECT MODEL "SingleLevelBomAsBuilt"'}),"\n",(0,i.jsx)(t.h4,{id:"341-introduction",children:"3.4.1 INTRODUCTION"}),"\n",(0,i.jsxs)(t.p,{children:['The "Industry Core: ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"Part Instance"}),'" aims on building product genealogy information throughout\nthe supply chain. Therefore it is required to link a produced part with\nits predecessor and its successor items.\nSingleLevelBoMAsBuilt is the submodel to build such a predecessor linkage between the digital twins. It contains the unique identifiers of the predecessor items of a produced or assembled part and therefore\nallows top-down navigation through the supply chain by Catena-X identifiers.']}),"\n",(0,i.jsxs)(t.p,{children:["More specific, the aspect provides information on the child\nitems (one structural level down) from which the given object is\nassembled. In first priority, it creates the relationship of one ",(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instance"})," in the asBuilt lifecycle phase with its child items by referencing the ",(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instance"})," digital twin of such item. However, when no ",(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instance"})," digital twin of the child item exists to reference, it is in a second priority possible to reference the part type twin of the child item instead."]}),"\n",(0,i.jsxs)(t.p,{children:['Because of gap of information in the production, it is sometimes not possible to identify the single correct digital twin to reference, but just a subset of potential twins. Then all potential alternative twins may be referenced. This will be marked by setting the property "hasAlternatives" true. If the exact digital twin is known, regardless of if it is a part type or ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instance"}),', just this one will be referenced and "hasAlternative" will be false.']}),"\n",(0,i.jsxs)(t.p,{children:["This model was modelled conform to the Catena-X standard CX-0045 ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect Model"})," Data Chain Template."]}),"\n",(0,i.jsxs)(t.p,{children:["Note: The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect model"})," SingleLevelBomAsBuilt ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," is ",(0,i.jsx)(t.strong,{children:"mandatory"}),". Versions higher than that are ",(0,i.jsx)(t.strong,{children:"optional"}),", but might become mandatory in future releases of this standard."]}),"\n",(0,i.jsxs)(t.p,{children:["For the changelog of the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),", ",(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.single_level_bom_as_built/RELEASE_NOTES.md",children:"see here"}),"."]}),"\n",(0,i.jsx)(t.h4,{id:"342-specifications-artifacts",children:"3.4.2 SPECIFICATIONS ARTIFACTS"}),"\n",(0,i.jsxs)(t.p,{children:['The modeling of the semantic model specified in this document was done in accordance to the "semantic driven workflow" to create a submodel template specification ',(0,i.jsx)(t.a,{href:"#62-non-normative-references",children:"SMT"}),"."]}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"})," SingleLevelBomAsBuilt is written in SAMM 2.1.0 as a modeling language conformant to CX-0003\nas input for the semantic driven workflow."]}),"\n",(0,i.jsx)(t.p,{children:"Like all Catena-X data models, this model is available in a machine-readable format on GitHub\nconformant to CX-0003."}
1),"\n",(0,i.jsx)(t.h4,{id:"343-license",children:"3.4.3 LICENSE"}),"\n",(0,i.jsxs)(t.p,{children:["This Catena-X data model is an outcome of Catena-X use case group\nIndustry Core. This Catena-X data model is made available under the terms\nof the Creative Commons Attribution 4.0 International (CC-BY-4.0)\nlicense, which is available at Creative Commons",(0,i.jsx)(t.sup,{children:(0,i.jsx)(t.a,{href:"#user-content-fn-2",id:"user-content-fnref-2-4","data-footnote-ref":!0,"aria-describedby":"footnote-label",children:"1"})}),"."]}),"\n",(0,i.jsx)(t.p,{children:"The license information is available in github."}),"\n",(0,i.jsx)(t.p,{children:"In case of doubt the license, copyright and authors information in\ngithub overwrites the information in this specification document."}),"\n",(0,i.jsx)(t.h4,{id:"344-identifier-of-semantic-model",children:"3.4.4 IDENTIFIER OF SEMANTIC MODEL"}),"\n",(0,i.jsx)(t.p,{children:"The semantic model has the unique identifier"}),"\n",(0,i.jsxs)(t.p,{children:["SingleLevelBomAsBuilt ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," (mandatory)"]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-text",children:"urn:samm:io.catenax.single_level_bom_as_built:3.0.0#SingleLevelBomAsBuilt\n"})}),"\n",(0,i.jsx)(t.h4,{id:"345-formats-of-semantic-model",children:"3.4.5 FORMATS OF SEMANTIC MODEL"}),"\n",(0,i.jsx)(t.h5,{id:"3451-rdf-turtle",children:"3.4.5.1 RDF TURTLE"}),"\n",(0,i.jsx)(t.p,{children:"The rdf turtle file, an instance of the Semantic Aspect Meta Model, is\nthe master for generating additional file formats and serializations. These can be viewed by following links:"}),"\n",(0,i.jsxs)(t.p,{children:["SingleLevelBomAsBuilt ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," (mandatory)"]}),"\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.single_level_bom_as_built/3.0.0/SingleLevelBomAsBuilt.ttl",children:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.single_level_bom_as_built/3.0.0/SingleLevelBomAsBuilt.ttl"})}),"\n",(0,i.jsxs)(t.p,{children:["The open source command line tool of the Eclipse Semantic Modeling Framework",(0,i.jsx)(t.sup,{children:(0,i.jsx)(t.a,{href:"#user-content-fn-3",id:"user-content-fnref-3-3","data-footnote-ref":!0,"aria-describedby":"footnote-label",children:"2"})})," is used for generation of other file formats like for example a JSON Schema, aasx for ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," Submodel Template or a HTML documentation."]}),"\n",(0,i.jsx)(t.h5,{id:"3452-json-schema",children:"3.4.5.2 JSON SCHEMA"}),"\n",(0,i.jsxs)(t.p,{children:["A JSON Schema can be generated from the RDF Turtle file. The JSON Schema defines the Value-Only\npayload of the ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," for the ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"}),' operation "GetSubmodel".']}),"\n",(0,i.jsx)(t.h5,{id:"3453-aasx",children:"3.4.5.3 AASX"}),"\n",(0,i.jsxs)(t.p,{children:["An AASX file can be generated from the RDF Turtle file. The AASX file defines one of the requested\nartifacts for a Submodel Template Specification conformant to [",(0,i.jsx)(t.a,{href:"#62-non-normative-references",children:"SMT"}),"]."]}),"\n",(0,i.jsx)(t.h4,{id:"346-example-data",children:"3.4.6 EXAMPLE DATA"}),"\n",(0,i.jsxs)(t.p,{children:["Example JSON payload: Submodel ",(0,i.jsx)(t.strong,{children:'"SingleLevelBomAsBuilt" v3.0.0 for a SerialPart'})]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-json",children:'{\n "catenaXId": "urn:uuid:580d3adf-1981-44a0-a214-13d6ceed9379",\n "childItems": [\n {\n "catenaXId": "urn:uuid:d60b99b0-f269-42f5-94d0-64fe0946ed04",\n "quantity": {\
1n "value": 1.0,\n "unit": "unit:piece"\n },\n "hasAlternatives": false,\n "createdOn": "2022-02-03",\n "businessPartner": "BPNL50096894aNXY",\n "lastModifiedOn": "2022-02-03T14:48:54.709Z"\n }\n ]\n}\n'})}),"\n",(0,i.jsxs)(t.p,{children:["Example JSON payload: Submodel ",(0,i.jsx)(t.strong,{children:'"SingleLevelBomAsBuilt" v3.0.0 for a Batch'})]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-json",children:'{\n "catenaXId": "urn:uuid:580d3adf-1981-44a0-a214-13d6ceed9379",\n "childItems": [\n {\n "catenaXId": "urn:uuid:d60b99b0-f269-42f5-94d0-64fe0946ed04",\n "quantity": {\n "value": 5.0,\n "unit": "unit:kilogram"\n },\n "hasAlternatives": false,\n "createdOn": "2022-02-03",\n "businessPartner": "BPNL50096894aNXY",\n "lastModifiedOn": "2022-02-03T14:48:54.709Z"\n }\n ]\n}\n'})}),"\n",(0,i.jsx)(t.h3,{id:"35-aspect-model-singlelevelusageasbuilt",children:'3.5 ASPECT MODEL "SingleLevelUsageAsBuilt"'}),"\n",(0,i.jsx)(t.h4,{id:"351-introduction",children:"3.5.1 INTRODUCTION"}),"\n",(0,i.jsxs)(t.p,{children:['The "Industry Core: ',(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"Part Instance"}),'" aims on building product genealogy information throughout the supply\nchain. Therefore it is required to link a produced part with its predecessor items and its successor items.\nSingleLevelUsageAsBuilt is the submodel to build a successor linkage between the digital twins. It contains the\n',(0,i.jsx)(r.A,{term:"Customer",definition:"In the context of OSim, the receiver of produced goods from a supplier.",routePath:"/glossary",children:"customers"})," and the unique identifiers of the successor items (usage) of a produced or assembled product and\ntherefore allows bottom-up navigation through the supply chain by Catena-X identifiers."]}),"\n",(0,i.jsxs)(t.p,{children:["More specific, the aspect provides information on the ",(0,i.jsx)(r.A,{term:"Customer",definition:"In the context of OSim, the receiver of produced goods from a supplier.",routePath:"/glossary",children:"customers"})," and the parent items (one structural level up) that are produced or assembled from the given object. It creates the relationship of one ",(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instance"})," in the asBuilt lifecycle phase with its parent items by referencing the ",(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instance"})," digital twin of such item. In analogy to SingleLevelBomAsBuilt it is possible that a parent item cannot be specified at instance level and therefore no ",(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instance"})," digital twin of that item exists to be referenced. In that case, in contrast to SingleLevelBomAsBuilt, even if it would be possible to reference a part type twin of the parent part instead, no reference will be made."]}),"\n",(0,i.jsx)(t.p,{children:'Because of gaps of information in the production, it is sometimes not possible to identify the single correct\ndigital twin to reference, but just a subset of potential twins that the item has been assembled into. Then from all potential alternative twins a reference can be done. To indicate that there is more than one parent item referenced as potential alternatives, the property "IsOnlyPotentialParent" will be set true for those references. If the exact digital twin of the parent part is known, the property "IsOnlyPotentialParent\u201d will be set false.'}),"\n",(0,i.jsxs)(t.p,{children:["To be able to reference the unique identifiers of the successor items (us
1age) the data provider of this ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"})," has to rely on their ",(0,i.jsx)(r.A,{term:"Customer",definition:"In the context of OSim, the receiver of produced goods from a supplier.",routePath:"/glossary",children:"customer"})," to provide them the correct information of that item. If the data provider does not have that information they are unable to provide the sucessor item but\nonly the ",(0,i.jsx)(r.A,{term:"Customer",definition:"In the context of OSim, the receiver of produced goods from a supplier.",routePath:"/glossary",children:"customer"}),"."]}),"\n",(0,i.jsxs)(t.p,{children:["This model was modelled conform to the Catena-X standard CX-0045 ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect Model"})," Data Chain Template."]}),"\n",(0,i.jsxs)(t.p,{children:["Note: The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect model"})," SingleLevelUsageAsBuilt ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," is ",(0,i.jsx)(t.strong,{children:"mandatory"}),". Versions higher than that are ",(0,i.jsx)(t.strong,{children:"optional"}),", but might become mandatory in future releases of this standard."]}),"\n",(0,i.jsxs)(t.p,{children:["For the changelog of the ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"}),", ",(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.single_level_usage_as_built/RELEASE_NOTES.md",children:"see here"}),"."]}),"\n",(0,i.jsx)(t.h4,{id:"352-specifications-artifacts",children:"3.5.2 SPECIFICATIONS ARTIFACTS"}),"\n",(0,i.jsxs)(t.p,{children:['The modeling of the semantic model specified in this document was done in accordance to the "semantic driven workflow" to create a submodel template specification ',(0,i.jsx)(t.a,{href:"#62-non-normative-references",children:"SMT"}),"."]}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"aspect model"})," SingleLevelUsageAsBuilt is written in SAMM 2.1.0 as a modeling language conformant to CX-0003\nas input for the semantic driven workflow."]}),"\n",(0,i.jsx)(t.p,{children:"Like all Catena-X data models, this model is available in a machine-readable format on GitHub\nconformant to CX-0003."}),"\n",(0,i.jsx)(t.h4,{id:"353-license",children:"3.5.3 LICENSE"}),"\n",(0,i.jsxs)(t.p,{children:["This Catena-X data model is an outcome of Catena-X use case group\nIndustry Core. This Catena-X data model is made available under the terms\nof the Creative
1Commons Attribution 4.0 International (CC-BY-4.0)\nlicense, which is available at Creative Commons",(0,i.jsx)(t.sup,{children:(0,i.jsx)(t.a,{href:"#user-content-fn-2",id:"user-content-fnref-2-5","data-footnote-ref":!0,"aria-describedby":"footnote-label",children:"1"})}),"."]}),"\n",(0,i.jsx)(t.p,{children:"The license information is available in github."}),"\n",(0,i.jsx)(t.p,{children:"In case of doubt the license, copyright and authors information in\ngithub overwrites the information in this specification document."}),"\n",(0,i.jsx)(t.h4,{id:"354-identifier-of-semantic-model",children:"3.5.4 IDENTIFIER OF SEMANTIC MODEL"}),"\n",(0,i.jsx)(t.p,{children:"The semantic model has the unique identifier"}),"\n",(0,i.jsxs)(t.p,{children:["SingleLevelUsageAsBuilt ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," (mandatory)"]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-text",children:"urn:samm:io.catenax.single_level_usage_as_built:3.0.0#SingleLevelUsageAsBuilt\n"})}),"\n",(0,i.jsx)(t.h4,{id:"355-formats-of-semantic-model",children:"3.5.5 FORMATS OF SEMANTIC MODEL"}),"\n",(0,i.jsx)(t.h5,{id:"3551-rdf-turtle",children:"3.5.5.1 RDF TURTLE"}),"\n",(0,i.jsx)(t.p,{children:"The rdf turtle file, an instance of the Semantic Aspect Meta Model, is\nthe master for generating additional file formats and serializations. These can be viewed by following links:"}),"\n",(0,i.jsxs)(t.p,{children:["SingleLevelUsageAsBuilt ",(0,i.jsx)(t.strong,{children:"v3.0.0"})," (mandatory)"]}),"\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.single_level_usage_as_built/3.0.0/SingleLevelUsageAsBuilt.ttl",children:"https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.single_level_usage_as_built/3.0.0/SingleLevelUsageAsBuilt.ttl"})}),"\n",(0,i.jsxs)(t.p,{children:["The open source command line tool of the Eclipse Semantic Modeling Framework",(0,i.jsx)(t.sup,{children:(0,i.jsx)(t.a,{href:"#user-content-fn-3",id:"user-content-fnref-3-4","data-footnote-ref":!0,"aria-describedby":"footnote-label",children:"2"})})," is used for generation of other file formats like for example a JSON Schema, aasx for ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," Submodel Template or a HTML documentation."]}),"\n",(0,i.jsx)(t.h5,{id:"3552-json-schema",children:"3.5.5.2 JSON SCHEMA"}),"\n",(0,i.jsxs)(t.p,{children:["A JSON Schema can be generated from the RDF Turtle file. The JSON Schema defines the Value-Only\npayload of the ",(0,i.jsx)(r.A,{term:"Asset Administration Shell",definition:"The AAS is a digital representation of an asset; it is a form of a digital twin.",routePath:"/glossary",children:"Asset Administration Shell"})," for the ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"}),' operation "GetSubmodel".']}),"\n",(0,i.jsx)(t.h5,{id:"3553-aasx",children:"3.5.5.3 AASX"}),"\n",(0,i.jsxs)(t.p,{children:["An AASX file can be generated from the RDF Turtle file. The AASX file defines one of the requested\nartifacts for a Submodel Template Specification conformant to [",(0,i.jsx)(t.a,{href:"#62-non-normative-references",children:"SMT"}),"]."]}),"\n",(0,i.jsx)(t.h4,{id:"356-example-data",children:"3.5.6 EXAMPLE DATA"}),"\n",(0,i.jsxs)(t.p,{children:["Example JSON payload: Submodel ",(0,i.jsx)(t.strong,{children:'"SingleLevelUsageAsBuilt" v3.0.0 for a SerialPart'})]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-json",children:'{\n "catenaXId": "urn:uuid:580d3adf-1981-44a0-a214-13d6ceed9379",\n "parentItems": [\n {\n "catenaXId": "urn:uuid:055c1128-0375-47c8-98de-7cf802c3241d",\n "isOnlyPotentialParent": false,\n "quantity": {\n "value": 1.0,\n "unit": "unit:piece"\n },\n "createdOn": "2022-02-03",\n "businessPartner": "BPNL50096894aNXY",\n "lastModifiedOn": "2022-02-03T14:48:54.709Z"\n }\n ],\n "customers": [\n "BPNL50096894aNXY"\n ]\n}\n'})}),"\n",(0,i.jsxs)(t.p,{children:["Example JSON payload: Submodel ",(0,i.jsx)(t.strong,{children:'"SingleLevelUsageAsBuilt" v3.0.0 for a Batch'})]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-json",children:'{\n "catenaXId": "urn:uuid:580d3adf-1981-44a0-a214-13d6ceed9379",\n "parentItems": [\n {\n "catenaXId": "urn:uuid:055c1128-0375-47c8-98de-7cf802c3241d",\n "isOnlyPotentialParent": false,\n "quantity": {\
1n "value": 25.0,\n "unit": "unit:kilogram"\n },\n "createdOn": "2022-02-03",\n "businessPartner": "BPNL50096894aNXY",\n "lastModifiedOn": "2022-02-03T14:48:54.709Z"\n }\n ],\n "customers": [\n "BPNL50096894aNXY"\n ]\n}\n'})}),"\n",(0,i.jsx)(t.h2,{id:"4-application-programming-interfaces",children:"4 APPLICATION PROGRAMMING INTERFACES"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is normative"})}),"\n"]}),"\n",(0,i.jsx)(t.h3,{id:"41-unique-id-push-notification-api",children:"4.1 UNIQUE ID PUSH NOTIFICATION API"}),"\n",(0,i.jsx)(t.p,{children:"Unique ID Push notifications provide the possibility to push specific information to a business partner in the value chain (one level up). This can help to provide faster information to reduce necessary information collection activities."}),"\n",(0,i.jsxs)(t.p,{children:["The Unique ID Push Notification ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," ",(0,i.jsx)(t.strong,{children:"MAY"})," be used to push the information \u201cConnect to Parent\u201d to a business partner.\nThe information \u201cConnect to Parent\u201d ",(0,i.jsx)(t.strong,{children:"MUST NOT"})," be provided in any other way than with the\nUnique ID Push Notification ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"}),"."]}),"\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.strong,{children:"Connect to Parent"})}
1),"\n",(0,i.jsxs)(t.p,{children:['Unique ID Push notifications of type "connect-to-parent" are a way for a manufacturer to notify a ',(0,i.jsx)(r.A,{term:"Customer",definition:"In the context of OSim, the receiver of produced goods from a supplier.",routePath:"/glossary",children:"customer"})," as soon as possible when a new digital twin for a part is available."]}),"\n",(0,i.jsxs)(t.p,{children:["The sender of the notification is the ",(0,i.jsx)(r.A,{term:"Supplier",definition:"In the context of OSim, the producer of goods.",routePath:"/glossary",children:"supplier"})," of a part item and the receiver of the notification is the ",(0,i.jsx)(r.A,{term:"Customer",definition:"In the context of OSim, the receiver of produced goods from a supplier.",routePath:"/glossary",children:"customer"})," of that part item. The Unique ID of that part is sent in the notification."]}),"\n",(0,i.jsxs)(t.p,{children:["Connect to Parent notifications ",(0,i.jsx)(t.strong,{children:"MAY"})," be applied to Digital Twins for ",(0,i.jsx)(r.A,{term:"Part Instance",definition:"A Part Instance is a physically produced instance (e.g., serialized part, batch, just-in-sequence part) of a Part Type.",routePath:"/glossary",children:"part instances"})," and for part types."]}),"\n",(0,i.jsx)(t.h4,{id:"411-preconditions-and-dependencies",children:"4.1.1 PRECONDITIONS AND DEPENDENCIES"}),"\n",(0,i.jsxs)(t.p,{children:["Application providers ",(0,i.jsx)(t.strong,{children:"MUST"})," prove their conformity by providing:\nAn openAPI specification of the endpoints described."]}),"\n",(0,i.jsxs)(t.p,{children:["Examples of the data ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"asset"})," and contract definition structure in their ",(0,i.jsx)(r.A,{term:"Tractus-X EDC",definition:"The Tractus-X Eclipse Dataspace Connector (Tractus-X EDC) is a reference implementation for a connector conformant to CX-0018 and acts as a de-facto standard/reference implementation within Catena-X; other CX-0018-conformant connectors are also valid options.",routePath:"/glossary",children:"Tractus-X EDC"})," or any other CX-0018 compliant connector."]}),"\n",(0,i.jsxs)(t.p,{children:["The Unique ID Push Notification ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," ",(0,i.jsx)(t.strong,{children:"MUST"})," be published towards the network using a Data ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"Asset"}),"/Contract Definition in terms of the ",(0,i.jsx)(r.A,{term:"IDSA Protocol",definition:"The protocol used for data exchange in an International Dataspace; this includes contract negotiation.",routePath:"/glossary",children:"IDSA Protocol"})," as described by the reference implementation [CX-0018]."]}),"\n",(0,i.jsxs)(t.p,{children:["The Eclipse Dataspace Connector as a reference implementation ",(0,i.jsx)(t.strong,{children:"SHOULD BE"})," used and is referenced in this document. Other connectors fulfilling the same standards towards Catena-X ",(0,i.jsx)(t.strong,{children:"MAY"})," be leveraged as well."]}),"\n",(0,i.jsxs)(t.p,{children:["It is of importance to mention, that there ",(0,i.jsx)(t.strong,{children:"MUST"})," be an ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," available behind each of the data offers described in the dataspace connector, which works according to the openAPI specifications description."]}),"\n",(0,i.jsxs)(t.p,{children:["Nevertheless, the ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"APIs"})," are ",(0,i.jsx)(t.strong,{children:"OPTIONAL"})," to follow the same structure, as there could even be ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"APIs"})," taking over the job of several of the endpoints mentioned."]}),"\n",(0,i.jsxs)(t.p,{children:["The dataspace connector ",(0,i.jsx)(t.strong,{children:"SHOULD"})," act as a reverse proxy towards those ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"APIs"}),", as it holds the Data Offers linked to the respective implemented endpoints."]}),"\n",(0,i.jsx)(t.h4,{id:"412-api-specification",children:"4.1.2 API SPECIFICATION"}),"\n",(0,i.jsx)(t.h5,{id:"4121-api-endpoints",children:"4.1.2.1 API-ENDPOINTS"}),"\n",(0,i.jsxs)(t.p,{children:["The Unique ID Push Notification ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," ",(0,i.jsx)(t.strong,{children:"MUST"})," be implemented as specified in the openAPI documentation as stated here: ",(0,i.jsx)(t.a,{target:"_blank","data-noBrokenLinkCheck":!0,href:a(28586).A+"",children:"openAPI"})]}),"\n",(0,i.jsxs)(t.p,{children:["To enable compatibility with future versions, additional, unknown attributes in the ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," can be ignored."]}),"\n",(0,i.jsxs)(t.p,{children:["The Unique ID Push Notification ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," ",(0,i.jsx)(t.strong,{children:"MUST"})," implement one endpoint:"]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-text",children:"POST/uniqueidpush/connect-to-parent\n"})}),"\n",(0,i.jsxs)(t.p,{children:["In fact, it is ",(0,i.jsx)(t.strong,{children:"OPTIONAL"})," to implement the endpoint paths exactly as described above. The reason is that those\nendpoints are not called from any supply chain partner directly. Rather, they are called from the ",(0,i.jsx)(r.A,{term:"Tractus-X
1EDC",definition:"The Tractus-X Eclipse Dataspace Connector (Tractus-X EDC) is a reference implementation for a connector conformant to CX-0018 and acts as a de-facto standard/reference implementation within Catena-X; other CX-0018-conformant connectors are also valid options.",routePath:"/glossary",children:"Tractus-X EDC"})," as part of data ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"assets"}),". In that sense, it is just important to implement\nendpoints that can process the defined request body and respond with the ",(0,i.jsx)(r.A,{term:"HTTP",definition:"HTTP is an application-layer protocol for transmitting hypermedia documents (such as HTML). It was designed for communication between web browsers and web servers, but can also be used for other purposes.",routePath:"/glossary",children:"HTTP"})," status codes and - if\nrequired - reply with the defined response body."]}),"\n",(0,i.jsxs)(t.p,{children:["The data ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"assets"})," will act similar to a reverse proxy for the notification endpoints, therefore rather the\ndata ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"assets"})," are of significance, which ",(0,i.jsx)(t.strong,{children:"SHOULD"})," be exposed towards Catena-X through the Data Offer\nCatalogues in the ",(0,i.jsx)(r.A,{term:"Tractus-X EDC",definition:"The Tractus-X Eclipse Dataspace Connector (Tractus-X EDC) is a reference implementation for a connector conformant to CX-0018 and acts as a de-facto standard/reference implementation within Catena-X; other CX-0018-conformant connectors are also valid options.",routePath:"/glossary",children:"Tractus-X EDC"})," or any other CX-0018 compatible connector."]}),"\n",(0,i.jsx)(t.h5,{id:"4122-available-data-types",children:"4.1.2.2 AVAILABLE DATA TYPES"}),"\n",(0,i.jsxs)(t.p,{children:["The notification ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," ",(0,i.jsx)(t.strong,{children:"MUST"})," use JSON as the payload transported via ",(0,i.jsx)(r.A,{term:"HTTP",definition:"HTTP is an application-layer protocol for transmitting hypermedia documents (such as HTML). It was designed for communication between web browsers and web servers, but can also be used for other purposes.",routePath:"/glossary",children:"HTTP"}),"."]}),"\n",(0,i.jsx)(t.h5,{id:"4123-api-resources--endpoints",children:"4.1.2.3 API RESOURCES & ENDPOINTS"}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"HTTP",definition:"HTTP is an application-layer protocol for transmitting hypermedia documents (such as HTML). It was designed for communication between web browsers and web servers, but can also be used for other purposes.",routePath:"/glossary",children:"HTTP"})," POST endpoints introduced in this standard ",(0,i.jsx)(t.strong,{children:"MUST"})," be called via Data Space Protocol.\nThe sending and receiving of notifications ",(0,i.jsx)(t.strong,{children:"MUST"})," be built on the basis of ",(0,i.jsx)(r.A,{term:"HTTP",definition:"HTTP is an application-layer protocol for transmitting hypermedia documents (such as HTML). It was designed for communication between web browsers and web servers, but can also be used for other purposes.",routePath:"/glossary",children:"HTTP"})," POST endpoints."]}),"\n",(0,i.jsx)(t.h4,{id:"413-data-asset-structure",children:"4.1.3 DATA ASSET STRUCTURE"}),"\n",(0,i.jsx)(t.h5,{id:"data-asset-for-unique-id-push-notification-receive-endpoint",children:"DATA ASSET FOR UNIQUE ID PUSH NOTIFICATION RECEIVE ENDPOINT"}),"\n",(0,i.jsxs)(t.p,{children:["When using the ",(0,i.jsx)(r.A,{term:"Tractus-X
1EDC",definition:"The Tractus-X Eclipse Dataspace Connector (Tractus-X EDC) is a reference implementation for a connector conformant to CX-0018 and acts as a de-facto standard/reference implementation within Catena-X; other CX-0018-conformant connectors are also valid options.",routePath:"/glossary",children:"Tractus-X EDC"})," or any other CX-0018 conformant connector, the following ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"asset"})," ",(0,i.jsx)(t.strong,{children:"MUST"})," be registered. Other connectors implementing the CX-0018\nstandard require a similar data ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"asset"})," with the same structure and provisioning towards Catena-X."]}),"\n",(0,i.jsxs)(t.p,{children:["The following properties must be set for this ",(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"asset"}),":"]}),"\n",(0,i.jsx)(t.pre,{children:(0,i.jsx)(t.code,{className:"language-json",children:'{\n "@context": {\n "edc": "https://w3id.org/edc/v0.0.1/ns/",\n "cx-common": "https://w3id.org/catenax/ontology/common#",\n "cx-taxo": "https://w3id.org/catenax/taxonomy#",\n "dct": "https://purl.org/dc/terms/"\n },\n "@id": "{{ _.assetId }}",\n "properties": {\n "dct:type": { "@id": "cx-taxo:UniqueIdPushConnectToParentNotification" },\n "cx-common:version": "2.0"\n }\n}\n'})}),"\n",(0,i.jsxs)(t.p,{children:['Properties "dct',":type",'" and "cx-common',":version",'" are used to classify the ',(0,i.jsx)(r.A,{term:"Asset",definition:"On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer.",routePath:"/glossary",children:"asset"})," and are explained in the ",(0,i.jsx)(t.a,{href:"https://eclipse-tractusx.github.io/docs-kits/kits/Digital%20Twin%20Kit/Software%20Development%20View/Specification%20Digital%20Twin%20KIT#registration-at-edc",children:"Digital Twin KIT"})," in more detail."]}),"\n",(0,i.jsx)(t.h4,{id:"414-versioning",children:"4.1.4 VERSIONING"}),"\n",(0,i.jsxs)(t.p,{children:["The ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," version described in this standard document ",(0,i.jsx)(t.strong,{children:"MUST"})," be published in the property ",(0,i.jsx)(t.a,{href:"https://w3id.org/catenax/ontology/common#version",children:"https://w3id.org/catenax/ontology/common#version"})," as version 2.0 in ",(0,i.jsxs)(t.a,{href:"http://www.w3.org/ns/dcat#",children:["dcat",":Dataset"]}),"."]}),"\n",(0,i.jsx)(t.h2,{id:"5-processes",children:"5 PROCESSES"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is normative"})}),"\n"]}),"\n",(0,i.jsx)(t.p,{children:"There is no prcoess defintion in this standard version available."}),"\n",(0,i.jsx)(t.h2,{id:"6-references",children:"6 REFERENCES"}),"\n",(0,i.jsx)(t.h3,{id:"61-normative-references",children:"6.1 NORMATIVE REFERENCES"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is normative"})}),"\n"]}),"\n",(0,i.jsxs)(t.ul,{children:["\n",(0,i.jsxs)(t.li,{children:["CX-0001 EDC DISCOVERY ",(0,i.jsx)(r.A,{term:"API",definition:"An API is a way for two or more computer programs to communicate with each other.",routePath:"/glossary",children:"API"})," 1.0.2"]}),"\n",(0,i.jsx)(t.li,{children:"CX-0002 Digital Twins in Catena\u2013X 2.2.0"}),"\n",(0,i.jsx)(t.li,{children:"CX-0003 SAMM Aspect Meta Model 1.1.0"}),"\n",(0,i.jsx)(t.li,{children:"CX\u20130018 Dataspace Connectivity 3.0.0"}),"\n",(0,i.jsxs)(t.li,{children:["CX-0045 ",(0,i.jsx)(r.A,{term:"Aspect Model",definition:"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).",routePath:"/glossary",children:"Aspect Model"})," Data Chain Template 1.3.0"]}),"\n",(0,i.jsxs)(t.li,{children:["CX-0053 ",(0,i.jsx)(r.A,{term:"BPN",definition:"A BPN is the unique identifier of a partner within Catena-X.",routePath:"/glossary",children:"BPN"})," Discovery Services 1.1.0"]}),"\n",(0,i.jsx)(t.li,{children:"CX-0152 Policy Constraints For Data Exchange v1.0.0"}),"\n"]}),"\n",(0,i.jsx)(t.h3,{id:"62-non-normative-references",children:"6.2 NON-NORMATIVE REFERENCES"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is non-normative"})}),"\n"]}),"\n",(0,i.jsxs)(t.p,{children:["[SMT] How to create a submodel template specification. Guideline.\nDownload from: ",(0,i.jsx)(t.a,{href:"https://industrialdigitalt
1win.org/wp-content/uploads/2022/12/I40-IDTA-WS-Process-How-to-write-a-SMT-FINAL-.pdf",children:"https://industrialdigitaltwin.org/wp-content/uploads/2022/12/I40-IDTA-WS-Process-How-to-write-a-SMT-FINAL-.pdf"})]}),"\n",(0,i.jsxs)(t.ul,{children:["\n",(0,i.jsx)(t.li,{children:(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/sldt-semantic-models",children:"https://github.com/eclipse-tractusx/sldt-semantic-models"})}),"\n",(0,i.jsx)(t.li,{children:(0,i.jsx)(t.a,{href:"https://catenax-ev.github.io/docs/next/operating-model/why-introduction",children:"https://catenax-ev.github.io/docs/next/operating-model/why-introduction"})}),"\n"]}),"\n",(0,i.jsx)(t.h3,{id:"63-reference-implementations",children:"6.3 REFERENCE IMPLEMENTATIONS"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is non-normative"})}),"\n"]}),"\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.a,{href:"https://github.com/eclipse-tractusx/item-relationship-service",children:"Item Relationship Service"})}),"\n",(0,i.jsx)(t.h2,{id:"annexes",children:"ANNEXES"}),"\n",(0,i.jsx)(t.h3,{id:"figures",children:"FIGURES"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is non-normative"})}),"\n"]}),"\n",(0,i.jsx)(t.p,{children:"This section is empty."}),"\n",(0,i.jsx)(t.h3,{id:"tables",children:"TABLES"}),"\n",(0,i.jsxs)(t.blockquote,{children:["\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.em,{children:"This section is non-normative"})}),"\n"]}),"\n",(0,i.jsx)(t.p,{children:"This section is empty."}),"\n",(0,i.jsx)(t.h2,{id:"legal",children:"Legal"}),"\n",(0,i.jsxs)(t.p,{children:["Copyright \xa9 2025 Catena-X Automotive Network e.V. All rights reserved. For more information, please visit ",(0,i.jsx)(t.a,{href:"/copyright",children:"here"}),"."]}),"\n","\n",(0,i.jsxs)(t.section,{"data-footnotes":!0,className:"footnotes",children:[(0,i.jsx)(t.h2,{className:"sr-only",id:"footnote-label",children:"Footnotes"}),"\n",(0,i.jsxs)(t.ol,{children:["\n",(0,i.jsxs)(t.li,{id:"user-content-fn-2",children:["\n",(0,i.jsxs)(t.p,{children:[(0,i.jsx)(t.a,{href:"https://creativecommons.org/licenses/by/4.0/legalcode",children:"https://creativecommons.org/licenses/by/4.0/legalcode"})," ",(0,i.jsx)(t.a,{href:"#user-content-fnref-2","data-footnote-backref":"","aria-label":"Back to reference 1",className:"data-footnote-backref",children:"\u21a9"})," ",(0,i.jsxs)(t.a,{href:"#user-content-fnref-2-2","data-footnote-backref":"","aria-label":"Back to reference 1-2",className:"data-footnote-backref",children:["\u21a9",(0,i.jsx)(t.sup,{children:"2"})]})," ",(0,i.jsxs)(t.a,{href:"#user-content-fnref-2-3","data-footnote-backref":"","aria-label":"Back to reference 1-3",className:"data-footnote-backref",children:["\u21a9",(0,i.jsx)(t.sup,{children:"3"})]})," ",(0,i.jsxs)(t.a,{href:"#user-content-fnref-2-4","data-footnote-backref":"","aria-label":"Back to reference 1-4",className:"data-footnote-backref",children:["\u21a9",(0,i.jsx)(t.sup,{children:"4"})]})," ",(0,i.jsxs)(t.a,{href:"#user-content-fnref-2-5","data-footnote-backref":"","aria-label":"Back to reference 1-5",className:"data-footnote-backref",children:["\u21a9",(0,i.jsx)(t.sup,{children:"5"})]})]}),"\n"]}),"\n",(0,i.jsxs)(t.li,{id:"user-content-fn-3",children:["\n",(0,i.jsxs)(t.p,{children:[(0,i.jsx)(t.a,{href:"https://github.com/eclipse-esmf/esmf-sdk",children:"https://github.com/eclipse-esmf/esmf-sdk"})," ",(0,i.jsx)(t.a,{href:"#user-content-fnref-3","data-footnote-backref":"","aria-label":"Back to reference 2",className:"data-footnote-backref",children:"\u21a9"})," ",(0,i.jsxs)(t.a,{href:"#user-content-fnref-3-2","data-footnote-backref":"","aria-label":"Back to reference 2-2",className:"data-footnote-backref",children:["\u21a9",(0,i.jsx)(t.sup,{children:"2"})]})," ",(0,i.jsxs)(t.a,{href:"#user-content-fnref-3-3","data-footnote-backref":"","aria-label":"Back to reference 2-3",className:"data-footnote-backref",children:["\u21a9",(0,i.jsx)(t.sup,{children:"3"})]})," ",(0,i.jsxs)(t.a,{href:"#user-content-fnref-3-4","data-footnote-backref":"","aria-label":"Back to reference 2-4",className:"data-footnote-backref",children:["\u21a9",(0,i.jsx)(t.sup,{children:"4"})]})]}),"\n"]}),"\n"]}),"\n"]})]})}function m(e={}){const{wrapper:t}={...(0,s.R)(),...e.components};return t?(0,i.jsx)(t,{...e,children:(0,i.jsx)(h,{...e})}):h(e)}},28586(e,t,a){a.d(t,{A:()=>n});const n=a.p+"assets/files/unique-id-push-2-0-0-39bc6c535ca6960716267b898e6b0a97.yaml"},28453(e,t,a){a.d(t,{R:()=>r,x:()=>o});var n=a(96540);const i={},s=n.createContext(i);function r(e){const t=n.useContext(s);return n.useMemo(function(){return"function"==typeof e?e(t):{...t,...e}},[t,e])}function o(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),n.createElement(s.Provider,{value:t},e.children)}},16877(e,t,a){a.d(t,{A:()=>u});var n=a(96540),i=a(66588);const s="glossaryTermWrapper_xqTQ",r="glossaryTerm_wdF6",o="tooltip_DUhm",d="tooltipFloating_oqgg",l="tooltipTop_L1lz",c="tooltipBottom_GPpw",h="tooltipVisible_fU0u";var m=a(74848);function u({term:e,definition:t,routePath:a="/glossary",children:u}
1){const[f,p]=(0,n.useState)(!1),[A,x]=(0,n.useState)(null),[g,b]=(0,n.useState)("top"),j=(0,n.useRef)(null),y=(0,n.useRef)(null),T=(0,n.useCallback)(()=>{if(!j.current||!y.current)return;const e=j.current.getBoundingClientRect(),t=y.current.getBoundingClientRect(),a=window.innerWidth,n=window.innerHeight,i=e.top>=t.height+8,s=n-e.bottom>=t.height+8,r=i||!s?"top":"bottom";let o;o="top"===r?e.top-t.height-8:e.bottom+8;let d=e.left+e.width/2-t.width/2;d=Math.max(8,Math.min(d,a-t.width-8)),b(r),x({top:Math.max(4,o),left:d})},[]);(0,n.useEffect)(()=>{if(!f)return;let e;const t=requestAnimationFrame(()=>{e=requestAnimationFrame(()=>{T()})}),a=()=>T(),n=()=>T();return window.addEventListener("scroll",a,!0),window.addEventListener("resize",n),()=>{cancelAnimationFrame(t),e&&cancelAnimationFrame(e),window.removeEventListener("scroll",a,!0),window.removeEventListener("resize",n)}},[f,T]);const v=(0,i.P_)("docusaurus-plugin-glossary"),S=(0,n.useMemo)(()=>{if(t&&"string"==typeof t&&t.length>0)return t;const a=(v&&v.terms||[]).find(t=>"string"==typeof t.term&&t.term.toLowerCase()===String(e).toLowerCase());return a&&a.definition?a.definition:void 0},[t,v,e]),I=(0,n.useMemo)(()=>a&&"string"==typeof a&&a.length>0?a:v&&v.routePath||"/glossary",[v,a]),M=u||e,P=e.toLowerCase().replace(/\s+/g,"-");return(0,m.jsxs)("span",{ref:j,className:s,children:[(0,m.jsx)("a",{href:`${I}#${P}`,className:r,onMouseEnter:()=>p(!0),onMouseLeave:()=>p(!1),onFocus:()=>p(!0),onBlur:()=>p(!1),"aria-describedby":`tooltip-${P}`,children:M}),S&&(0,m.jsxs)("span",{ref:y,id:`tooltip-${P}`,className:`${o} ${f?h:""} ${"top"===g?l:c} ${d}`,role:"tooltip",style:f&&A?{top:`${A.top}px`,left:`${A.left}px`}:void 0,children:[(0,m.jsx)("strong",{children:e})," ",S]})]})}}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.