CX-0128 - Demand and Capacity Management Data Exchange v2.1.0
ABSTRACT
This section and all its subsections are non-normative
The Catena-X Demand and Capacity Management (DCM) standard is designed for all members of the automotive supply chain. Its goal is to help these members prevent or anticipate production issues that can arise from fluctuations in demand or capacity planning. This standard is particularly relevant for mid- to long-term planning, covering periods up to 24 months into the future. Effective collaboration between partners in a direct business relationship (also referred to as “one-up” and “one-down”) is a key element of success.
The Catena-X DCM standard is accessible to all supply chain participants, including suppliers and Original Equipment Manufacturers (OEMs), regardless of their size and position in the supply chain. It is particularly useful for those involved in production and production planning. The standard prioritizes parts and materials that are critical to manufacturing, aiming to create mutually beneficial outcomes for all parties involved and to enhance the flexibility in meeting customer needs.
This standard offers an alternative to proprietary systems or manual processes that are often resource-intensive and prone to errors. It provides a collaborative foundation for demand and capacity management within the automotive industry, ensuring compatibility with existing systems and maintaining data sovereignty for all users.
Recent global supply chain disruptions have highlighted the need for greater resilience. The automotive industry, with its complex and volatile environment, has multiple IT solutions and interfaces within a single company and across the supply chain. However, there is a lack of a unified process understanding among all partners.
Demand and Capacity Management (DCM) involves the exchange of demand and capacity data between customers and suppliers within their direct business relationships. Customers communicate their anticipated material needs for specific timeframes and suppliers respond with their planned production capacities for those materials and timeframes.
For successful DCM, companies must share a common understanding that enables the exchange of data across different partners and systems while respecting each partner's data sovereignty.
This standard describes the data models, data exchange protocols and a core business logic for interpreting the data, ensuring a consistent approach for all DCM participants.
Cross-company interactions and common business logic required for DCM are standardized in Chapter 5, while the Application Programming Interfaces (APIs) are described in Chapter 4. The data models are presented in Chapter 3.
COMPARISON WITH PREVIOUS VERSIONS OF THIS STANDARD
This section and all its subsections are non-normative
Release 24.05
- Replaced
MaterialDemand
withWeekBasedMaterialDemand
aspect model - Added deactivation of
WeekBasedCapacityGroup
to Section 4.2.2.2 - Added deactivation of
WeekBasedMaterialDemand
to Section 4.1.2.2 - Added Chapter 2.3 Additional Requirements
- Added Chapter 5.10 Supply Chain Disruption Notifications
- Added Chapter 5.11 Demand Volatility Metrics
- Added Agreed Capacity to Section 5.6.1
- Added Repositories to Annexes
- Updated References in Chapter 7
- Updated
WeekBasedCapacityGroup
aspect model - Updated
WeekBasedMaterialDemand
aspect model - Updated
MessageHeaderAspect
version in Chapter 4 - Updated Policies in Chapter 6
- Updated choice of words and writing pattern throughout this standard
Release 24.03
- Merged CX-0046, CX-0047 and CX-0048 into this standard
- Replaced
WeekBasedMaterialDemand
withMaterialDemand
aspect model - Added Nesting of
WeekBasedCapacityGroup
to Section 5.6.2 - Added Section 5.6.4 Load Factors
- Added Section 5.7.2 Simulated Delta-Production (Pre-/Post-production)
- Added Chapter 5.8 Request for Update
- Added Chapter 5.9 Collaboration functionalities for DCM
- Updated
WeekBasedCapacityGroup
aspect model - Updated unit of measure representation and handling
Release 23.09
- Initial release
1 INTRODUCTION
This section and all its subsections are non-normative
1.1 Audience and Scope
This standard is intended for the three roles below, who are involved in the Demand and Capacity Management (DCM) process within the automotive industry:
- Data Provider
- Data Consumer
- Business Application Provider
For clarity on the roles and responsibility of each actor, please see Chapter 5.2. The scope of this standard includes regulations for managing future demands and capacities. It does not cover the specific methods companies use to calculate their demand or capacity data, nor does it address internal company measures.
Illustrations and descriptions of roles are provided to help explain concepts and processes but are not mandatory. This standard requires that data consumers, providers and business application providers must adopt a uniform business logic, data models and data exchange protocols to ensure interoperable data exchange.
This standard focuses on direct one-to-one business relationships between customers and suppliers. Companies participating in Catena-X DCM must have agreed to the Data Exchange Governance framework agreement.
1.2 Context and Architecture Fit
This standard (CX-0128) defines the standard data models and APIs for the following objects, utilized by the DCM use case: WeekBasedMaterialDemand
, WeekBasedCapacityGroup
, IdBasedRequestForUpdate
and IdBasedComment
. Applying these standards ensures that:
- All actors participating in the DCM use case provide and consume demand-, capacity- and comment-information in an identical manner
- All actors participating in the DCM use case process data in an identical manner
- All actors participating in the DCM use case exchange data only via a connector conformant to [CX-0018] (e.g. Tractus-X EDC)
- All actors participating in the DCM use case interpret the exchanged data in an identical manner
The APIs must only be used on the context of Catena-X and must only be accessible via a connector conformant to [CX-0018] (e.g. Tractus-X EDC).
1.2.1 Architectural Overview
This standard covers the exchange of WeekBasedMaterialDemand
, WeekBasedCapacityGroup
, IdBasedRequestForUpdate
and IdBasedComment
data as JSON strings through a connector conformant to [CX-0018].
This standard also discusses the optional use of digital twin registries to support the transmission of WeekBasedMaterialDemand
and WeekBasedCapacityGroup
objects.
How to build an application that creates and handles these objects is not part of this standard.
1.3 Conformity and Proof of Conformity
Non-mandatory sections include authoring guidelines, diagrams, examples and notes. All other content is mandatory.
The capitalized key words such as MAY, MUST, MUST NOT, OPTIONAL, RECOMMENDED, REQUIRED, SHOULD and SHOULD NOT are to be interpreted as defined in BCP 14 [RFC2119] [RFC8174].
Participants must demonstrate conformity with Catena-X standards. Conformity Assessment Bodies (CABs) verify that standards are correctly applied.
If a participant or application only implements either the business role customer or the business role supplier, then conformity must only be demonstrated along conformity assessment criteria (CACs) that apply to the specific business role.
Proof of Conformity for Data Models
Participants must implement and conform to the standardized data models as described in Chapter 3. Depending on which business role a participant or application implements only parts of Chapter 3 are relevant for conformity.
Data model | Business role | Relevant capability |
---|---|---|
WeekBasedMaterialDemand | Customer | Data provider |
WeekBasedMaterialDemand | Supplier | Data consumer |
WeekBasedCapacityGroup | Customer | Data consumer |
WeekBasedMaterialDemand | Supplier | Data provider |
IdBasedRequestForUpdate | Customer or supplier | Data provider and data consumer |
IdBasedComment | Customer or supplier | Data provider and data consumer |
Proof of Conformity for APIs
Participants must implement and conform to the standardized APIs as described in Chapter 4. Depending on which business role a participant or application implements only parts of Chapter 4 are relevant for conformity.
API taxonomy | Business role | Relevant capability |
---|---|---|
DcmWeekBasedMaterialDemand | Customer | Call API |
DcmWeekBasedMaterialDemand | Supplier | Offer API |
DcmWeekBasedCapacityGroup | Customer | Offer API |
DcmWeekBasedCapacityGroup | Supplier | Call API |
DcmIdBasedRequestForUpdate | Customer and supplier | Offer and call API |
DcmIdBasedComment | Customer or supplier | Offer and call API |
Submodel | Customer or supplier | Offer and call API |
Proof of Conformity for Process and Core Business Logic
Participants must implement and conform to the DCM core business logic as described in Chapter 5. Depending on which business role a participant or application implements only parts of Chapter 5 are relevant for conformity.
Relevant process step | Business role |
---|---|
Manage demands | Customer |
Manage capacities | Supplier |
Bottleneck calculation | Customer and supplier |
Collaborate | Customer and supplier |
Align capacities and demands | Customer and supplier |
Update demands | Customer |
Update capacities | Supplier |
1.4 Examples
1.4.1 Examples for Process and Core Business Logic
Customers and suppliers must have agreed to the Data Exchange Governance framework agreement, implement the core business logic from Chapter 5 and manage their access authorizations. They should ensure that material demand and capacity data are accurate, regularly updated and shared in a standardized format.
Business application providers must implement APIs as described in this standard and enforce requirements for a trusted usage environment, contractual agreements and antitrust requirements. Their applications must also enforce process traceability and data sovereignty.
1.4.2 Examples for Data Models
This section provides JSON examples for WeekBasedMaterialDemand
, WeekBasedCapacityGroup
, IdBasedRequestForUpdate
and IdBasedComment
payloads. The actual values must replace the placeholders in double curly braces. Further property descriptions are available in Chapter 5.
1.4.2.1 WeekBasedMaterialDemand data model JSON structure
value-only payload serialization example
{
"unitOfMeasureIsOmitted" : false,
"unitOfMeasure" : "unit:piece",
"materialDescriptionCustomer" : "Spark Plug",
"materialGlobalAssetId" : "urn:uuid:48878d48-6f1d-47f5-8ded-a441d0d879df",
"materialDemandId" : "0157ba42-d2a8-4e28-8565-7b07830c1110",
"materialNumberSupplier" : "MNR-8101-ID146955.001",
"supplier" : "{{CATENAX-SUPPLIER-BPNL}}",
"changedAt" : "2023-11-05T08:15:30.123-05:00",
"demandSeries" : [ {
"expectedSupplierLocation" : "{{CATENAX-SUPPLIER-BPNS}}",
"demands" : [ {
"demand" : 1000,
"pointInTime" : "2023-10-09"
} ],
"customerLocation" : "{{CATENAX-CUSTOMER-BPNS}}",
"demandCategory" : {
"demandCategoryCode" : "0001"
}
} ],
"materialDemandIsInactive" : true,
"materialNumberCustomer" : "MNR-7307-AU340474.002",
"customer" : "{{CATENAX-CUSTOMER-BPNL}}"
}
1.4.2.2 WeekBasedCapacityGroup data model JSON structure
value-only payload serialization example
{
"unitOfMeasure" : "unit:piece",
"linkedDemandSeries" : [ {
"loadFactor" : 3.5,
"materialNumberCustomer" : "MNR-7307-AU340474.002",
"materialNumberSupplier" : "MNR-8101-ID146955.001",
"customerLocation" : "{{CATENAX-CUSTOMER-BPNS}}",
"demandCategory" : {
"demandCategoryCode" : "0001"
}
} ],
"linkedCapacityGroups" : [ "be4d8470-2de6-43d2-b5f8-2e5d3eebf3fd" ],
"unitOfMeasureIsOmitted" : false,
"capacityGroupIsInactive" : true,
"demandVolatilityParameters" : {
"rollingHorizonAlertThresholds" : [ {
"sequenceNumber" : 1,
"absoluteNegativeDeviation" : 100.0,
"subhorizonLength" : 4,
"relativeNegativeDeviation" : 0.3,
"absolutePositiveDeviation" : 100.0,
"relativePositiveDeviation" : 0.2
} ],
"measurementInterval" : 4,
"startReferenceDateTime" : "2024-01-10T12:00:00.320Z"
},
"supplier" : "{{CATENAX-SUPPLIER-BPNL}}",
"name" : "Spark Plugs on drilling machine for car model XYZ",
"supplierLocations" : [ "{{CATENAX-SUPPLIER-BPNS}}" ],
"capacities" : [ {
"pointInTime" : "2022-08-01",
"agreedCapacity" : 1800,
"actualCapacity" : 1000,
"maximumCapacity" : 2000,
"deltaProductionResult" : 400
} ],
"changedAt" : "2023-03-10T12:27:11.320Z",
"capacityGroupId" : "0157ba42-d2a8-4e28-8565-7b07830c1110",
"customer" : "{{CATENAX-CUSTOMER-BPNL}}"
}
1.4.2.3 IdBasedRequestForUpdate data model JSON structure
value-only payload serialization example
{
"weekBasedMaterialDemand" : [ {
"materialDemandId" : "0157ba42-d2a8-4e28-8565-7b07830c3456",
"changedAt" : "2023-03-10T12:27:11.320Z"
} ],
"weekBasedCapacityGroup" : [ {
"capacityGroupId" : "0157ba42-d2a8-4e28-8565-7b07830c1110",
"changedAt" : "2023-03-10T12:27:11.320Z"
} ]
}
1.4.2.4 IdBasedComment data model JSON structure
value-only payload serialization example
{
"postedAt" : "2023-03-10T12:27:11.320Z",
"listOfReferenceDates" : [ "2023-11-05" ],
"author" : "someone@company.com",
"supplier" : "{{CATENAX-SUPPLIER-BPNL}}",
"commentType" : "information",
"commentId" : "f5c151e4-30b5-4456-94fd-2a7b559b6121",
"changedAt" : "2023-03-10T12:27:11.320Z",
"commentText" : "Hello, this is a comment!",
"requestDelete" : true,
"objectId" : "dfeb1334-497e-4dab-97c1-4e6f4e1c0320",
"objectType" : "urn:samm:io.catenax.week_based_capacity_group",
"customer" : "{{CATENAX-CUSTOMER-BPNL}}"
}
1.5 Terminology
Term | Description |
---|---|
Actual Capacity | This is the capacity a supplier realistically plans to have available to produce a certain amount of material per week for a customer. It takes into account the supplier's own assessment of their capabilities, inventory and existing commitments. |
Agreed Capacity | May be coordinated between customer and supplier. The agreed capacity must not constitute a legal obligation to deliver. Using the agreed capacity is optional and has purely informative character. The agreed capacity may be greater than, less than or equal to the actual or maximum capacity of the supplier. It may be used for a time frame shorter than the whole time series. |
Aspect Model | An Aspect model is a structured, machine-readable description of data. It utilizes the Turtle file format to serialize a Resource Description Framework (RDF) graph, that relates to a specific aspect. It must follow the Semantic Aspect Meta Model (SAMM) guidelines, meaning it uses defined elements and rules from SAMM. Aspect models help to clarify the meaning of data at runtime and should link to standardized business glossary terms, if available. |
Bottleneck | A facility, function, department, or resource whose capacity is less than the demand placed upon it. For example, a bottleneck machine or work center exists where jobs are processed at a slower rate than they are demanded (Source: ASCM Supply Chain Dictionary, 17th edition). |
Business application provider | Offers tools for demand and capacity management that conform to the core business logic, data models and APIs described in this standard. |
Business Partner Number Legal Entity (BPNL) | A BPNL is an unique identifier for a company or partner within the Catena-X network. |
Business Partner Number Site (BPNS) | A BPNS is an unique identifier for a specific location, such as a factory, within the Catena-X network. |
Calendar Week | A week consisting of seven days, typically numbered according to the week containing the year's first Thursday. For example, if the first Thursday of the year is on January 1st, that week is considered Week 1. |
Capacity | 1. The capability of a system to perform its expected function. 2. The capability of a worker, machine, work center, plant, or organization to produce output per time period. (Source: ASCM Supply Chain Dictionary, 17th edition). |
Capacity Group | A Capacity Group is where material demand and capacity information are matched for collaborative planning. When written as WeekBasedCapacityGroup , it refers to a specific data model within this standard. |
Comment | A feature that allows two business partners to exchange messages about material demand and capacity, facilitating direct collaboration and quick issue resolution. |
Comments | These are purely text-based exchanges without the transfer of documents or attachments. |
CreationEntity | Currently, a Creation Entity groups WeekBasedCapacityGroup objects to support digital twins in the planning process. It may represent a production plant and will be further defined in future revisions of this standard. |
Customer | A role within the DCM use case. Receives goods from its suppliers. Participating companies can have multiple roles at the same time. Customers provide consistent and up-to-date demand forecast and receive capacity data from suppliers. |
(Simulated) Delta-Production | This is an optional feature that allows suppliers to manage capacity bottlenecks by simulating changes in production without altering actual or maximum capacity. |
Demand Deviation | This is an optional metric that allows suppliers to monitor changes in customer demands and to identify significant changes that can collaboratively be addressed by suppliers and customers. |
Digital Twin | Based on [CX-0002] Standard a digital twin (DT) describes a digital representation of an asset sufficient to meet the requirements of a set of use cases. For detailed information please refer to [CX-0002] Digital Twins in Catena-X. |
Flexible Capacity | The difference between maximum and actual capacity, representing the potential to increase capacity without further agreements, such as extending the use of production resources within a week. In particular, it refers to measures to extend the weekly utilization of the available production resources. |
Linking material demand | Material demands can be linked directly to a capacity group or indirectly through another capacity group, which is known as "Nesting." |
Load Factor | Optional feature of a capacity group. ~ adds individual numerical material load factors to WeekBasedMaterialDemand linked by the WeekBasedCapacityGroup . ~ adds flexibility to the unit of measure of the capacity group. |
Material | The elements, constituents, or substances of which something is composed or can be made. Usually referred to by a material number. |
(Material) demand | A need for a particular product or component. The demand could come from any number of sources (e.g., a customer order or forecast, an interplant requirement, a branch warehouse request for a service part, or the manufacturing of another product). At the finished goods level, demand data is usually different from sales data because demand does not necessarily result in sales (i.e., If there is no stock, there will be no sale (Source: ASCM Supply Chain Dictionary, 17th edition)). Material demand may comprise multiple demand series by location and demand categories. When the term is written as one word (WeekBasedMaterialDemand ), the term refers specifically to the respective aspect model. |
Maximum Capacity | Is the maximum releasable capacity of a supplier which should be possible to achieve a material output per calendar week with a certain unit of measure for one customer. The maximum capacity is based on capacity-increasing measures, agreed by the parties involved. Capacity-increasing measures can be, for example, a longer utilization of the available production resources, a shift extension or additional shifts. Secondarily, additional resources can also be activated. |
Nesting | A method by which a capacity group links another capacity group, allowing for dynamic changes and centralized data management. |
Supplier | A role within the DCM use case. Supplies goods to its customers. Participating companies can have multiple roles at the same time. Suppliers provide consistent and up-to-date capacity data and receive demands from customers. |
Surplus | A surplus is a situation in which an oversupply exists. |
WeekBasedCapacityGroup | This term refers to the specific WeekBasedCapacityGroup object defined in this standard. |
For additional terminology, please refer to the glossary on the association's homepage.
2 RELEVANT PARTS OF THIS STANDARD FOR SPECIFIC USE CASES
This section and all its subsections are normative
This chapter lists all aspects of this standard that directly impact other Catena-X use cases if modified.
2.1 Digital Twins
This standard utilizes digital twins of "part type" (BOM as planned). Digital twins of "part instance" (BOM as built) are not utilized. Part type twins are also relevant to various other Catena-X standards. For additional details see [CX-0126] Industry Core: Part Type.
2.2 Supply Chain Disruption Notifications
This standard utilizes Supply Chain Disruption Notifications. Supply Chain Disruption Notifications are also relevant to other Catena-X standards. For additional details see [CX-0146] Supply Chain Disruption Notifications.
2.3 Additional Requirements
2.3.1 Conventions for Use Case Policy in Context Data Exchange
In alignment with our commitment to data sovereignty, a specific framework governing the utilization of data within the Catena-X use cases has been described. A set of specific policies on data offering and data usage level detail the conditions under which data may be accessed, shared, and used, ensuring compliance with legal standards.
For a comprehensive understanding of the rights, restrictions, and obligations associated with data usage in the Catena-X ecosystem, we refer users to:
- The detailed [ODRL] policy repository. This document provides in-depth explanations of the terms and conditions applied to data access and utilization, ensuring that all engagement with our data is conducted responsibly and in accordance with established guidelines.
- The ODRL schema template. This defines how policies used for data sharing/usage should get defined. Those schemas MUST be followed when providing services or apps for data sharing/consuming.
2.3.1.1 Additional details regarding access policies
A data provider may tie certain access authorizations Access Policies
to its data offers for members of Catena-X and one or several data consumers. By limiting access to certain Participants, data provider maintains control over its anti-trust obligations when sharing certain data. In particular, data providers may apply access policies to restrict access to a particular data offer for only one participant identified by a specific business partner number.
2.3.1.2 Additional details regarding usage policies
In the context of data usage policies Usage Policies
, participants and related services MUST use the following policy rules:
- Data Exchange Governance framework agreement.
- At least one use case purpose
UsagePurpose
from the above mentioned [ODRL] policy repository.
Additionally, respective usage policies MAY include the following policy rule:
- Reference Contract
ContractReference
.
Details on namespaces and ODRL policy rule values to be used for the above-mentioned types are provided via the [ODRL] policy repository.
3 ASPECT MODELS
This section and all its subsections are normative
3.1 Aspect Model WeekBasedMaterialDemand
3.1.1 Introduction
For the exchange of material demand information, customers MUST provide data to suppliers. The data format specified in this standard MUST be conformed to.
Customers and suppliers MUST implement the WeekBasedMaterialDemand
data model.
Suppliers MUST be able to consume and process material demand information.
Customers MUST be able to provide and process material demand information.
Data providers of WeekBasedMaterialDemand
data MUST ensure that it aligns with the semantic model specified in this standard.
The unique identifier for the semantic model, as specified in this standard, MUST be used to define the meaning of the data being transferred.
Business applications utilizing WeekBasedMaterialDemand
data MUST consume this data, conforming to the semantic model specified in this standard.
This semantic model MUST be made available in the central Semantic Hub.
Data consumers and data providers MUST comply with the license of the semantic model specified in Section 3.1.3.
Within the Catena-X data space WeekBasedMaterialDemand
data MUST be requested and exchanged using a connector, conforming to the standards [CX-0018] and [CX-0002].
The JSON Payload provided by data providers MUST comply with the JSON schema as specified in this standard.
The characteristics BPNL and BPNS MUST be used, conforming with [CX-0010].
3.1.2 Specification Artifacts
The creation of the semantic model specified in this section followed a sematic driven workflow, conforming to [SMT]. Conforming with [CX-0003] the resulting aspect model was written in SAMM 2.0.0 and is available on GitHub.
3.1.3 License
This Catena-X data model is released under the CC-BY-4.0 license.
3.1.4 Identifier of Semantic Model
The semantic model has the unique identifier
urn:samm:io.catenax.week_based_material_demand:3.0.1
Data providers MUST use this identifier to clearly define the semantics of the data they are transferring.
3.1.5 Formats of Semantic Model
3.1.5.1 RDF turtle
All other file format and serializations are derived from a RDF turtle file. It is the source for the Semantic Aspect Meta Model. You can access the RDF turtle file at the following URL:
https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.week_based_material_demand/3.0.1/WeekBasedMaterialDemand.ttl
The open source command line tool of the Eclipse Semantic Modeling Framework is used to generate other file formats such as JSON schema, AASX for Asset Administration Shell Submodel template or HTML documentation.
3.1.5.2 JSON schema
A JSON schema, which describes the structure of the data payload, can be created from the RDF turtle file. This schema specifically describes the data format for the GetSubmodel
API operation within the Asset Administration Shell, focusing on the values without including semantic information. This allows for a clear and structured way to retrieve data from the API.
3.1.5.3 AASX
An AASX file can be generated from the RDF turtle file. The AASX file defines one of the requested artifacts for a Submodel template specification conformant to [SMT].
3.1.6 Semantic Model
Not applicable.
3.2 Aspect Model WeekBasedCapacityGroup
3.2.1 Introduction
For the exchange of capacity group information, suppliers MUST provide data to customers. The data format specified in this standard MUST be conformed to.
Customers and suppliers MUST implement the WeekBasedCapacityGroup
data model.
Suppliers MUST be able to provide and process capacity group information.
Customers MUST be able to consume and process capacity group information.
Data providers of WeekBasedCapacityGroup
data MUST ensure that it aligns with the semantic model specified in this standard.
The unique identifier for the semantic model, as specified in this standard, MUST be used to define the meaning of the data being transferred.
Business applications utilizing WeekBasedCapacityGroup
data MUST consume this data, conforming to the semantic model specified in this standard.
This semantic model MUST be made available in the central Semantic Hub.
Data consumers and data providers MUST comply with the license of the semantic model specified in Section 3.2.3.
Within the Catena-X data space WeekBasedCapacityGroup
data MUST be requested and exchanged using a connector, conforming to the standards [CX-0018] and [CX-0002].
The JSON Payload provided by data providers MUST comply with the JSON schema as specified in this standard.
The characteristics BPNL and BPNS MUST be used, conforming with [CX-0010].
3.2.2 Specification Artifacts
The creation of the semantic model specified in this section followed a sematic driven workflow, conforming to [SMT]. Conforming with [CX-0003] the resulting aspect model was written in SAMM 2.0.0 and is available on GitHub.
3.2.3 License
This Catena-X data model is released under the (CC-BY-4.0) license.
3.2.4 Identifier of Semantic Model
The semantic model has the unique identifier
urn:samm:io.catenax.week_based_capacity_group:3.0.1
Data providers MUST use this identifier to clearly define the semantics of the data they are transferring.
3.2.5 Formats of Semantic Model
3.2.5.1 RDF turtle
All other file format and serializations are derived from a RDF turtle file. It is the source for the Semantic Aspect Meta Model. You can access the RDF turtle file at the following URL:
https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.week_based_capacity_group/3.0.1/WeekBasedCapacityGroup.ttl
The open source command line tool of the Eclipse Semantic Modeling Framework is used to generate other file formats such as JSON schema, AASX for Asset Administration Shell Submodel template or HTML documentation.