CX-0121 Planned Production Output Exchange 1.0.1
ABSTRACT
The supplier's Planned Production Output is one of the key determinants for avoiding a shortage at the customer's site. With information about the supplier's Planned Production Output quantities allocated to a specific customer, it can be monitored and predicted whether the customer demands can be fully supplied. If this is not the case, the information can be used by the customer to derive adequate countermeasures to keep the impact as low as possible. These measures can range, for example, from creating an adapted production plan with the supplier, rescheduling or reducing the customer's demand and production to, e.g. organizing an express delivery from an alternative supplier.
However, collecting the Planned Production Output information manually e.g. by phone or e-mail is error prone and slow. As a result, unmet demands often remain unnoticed for too long and unnecessarily restrict the scope for countermeasures. This often leads to shortages, costly fire-fighting measures in the supply chain, production interruptions and ultimately to customer dissatisfaction.
The standardization of the supplier's Planned Production Output semantics and exchange API enables participants in the supply chain to share information about time-bound Planned Production Output quantities at a supplier's site in an interoperable manner.
FOR WHOM IS THE STANDARD DESIGNED
COMPARISON WITH THE PREVIOUS VERSION OF THE STANDARD
Changes:
- integration and usage of digital twins as defined in [CX-0002] Digital Twins in Catena-X
- harmonization of aspect model in accordance with [CX-0126] Industry Core: Part Type
- discontinuation of the proprietary API used in v1.0.0 of this standard
- grammatical, spelling and semantic improvements
New Content:
- added a note on the obligation of standard implementers to make aware that sensitive data is being handled, see [Chapter 2.1.3]
1 INTRODUCTION
In recent years global supply chains have been significantly affected by global crises. This is compounded by ever-increasing complexity and interdependencies. As a result small and medium-sized enterprises as well as large enterprises are exposed to an increased risk of disruptions in their supply chains. To adapt to short-term fluctuations and develop the right countermeasures, it is essential to have sound information about the Planned Production Output of their suppliers.
This document describes and standardizes the semantic aspect model for the Planned Production Output as well as the associated API to exchange Planned Production Output information between supply chain partners. The supplier's Planned Production Output is the planned quantity of a material allocated to a specific customer in a time horizon of up to four weeks, that has not yet been produced. It has not yet been produced and is allocated to a specific partner. The scope of application is limited to existing business relationships and build-to-order (BTO) scenarios. Build-to-stock (BTS) use cases with no existing business relationships are explicitly not covered. In contrast to the strategic Demand and Capacity Management standard (DCM) [CX-0128], the Planned Production Output refers to short-term production planning, i.e. the actual utilization of existing and available capacity that resulted from capacity planning. It shows the latest production schedule-related information for a period of up to four weeks.
1.1 AUDIENCE & SCOPE
This section is non-normative
This standard is relevant for the following roles defined in [CX-OMW]:
- Data Providers willing to provide Planned Production Output data
- Data Consumers interested in requesting and receiving Planned Production Output data
- Business Application Providers interested in providing solutions implementing this standard
- Consulting Services Providers interested in supporting companies fulfilling the standard
The scope of this standard is only the Planned Production Output aspect model and API. It describes the exchange of Planned Production Output data through a connector in accordance to [CX-0018].
1.2 CONTEXT AND ARCHITECTURE FIT
This section is non-normative
A typical order-based procurement process includes a customer who places an order and a supplier fulfilling it. If the ordered material is not on stock in a sufficient quantity at a supplier's facility (see [CX-0122] Item Stock Exchange) it needs to be scheduled for production. These quantities of scheduled production are the subject of this standard and are referred to as the Planned Production Output. To ensure that the Planned Production Output information will be interpreted, handled and exchanged in an interoperable manner between partners participating in Catena-X, this standard document defines the PlannedProductionOutput aspect model and the API to be used in the Catena-X network.
Figure 1 shows the high-level architecture of the "Planned Production Output Exchange" in the Catena-X dataspace and the services that are involved. Both the data consumer and the data provider must be members of the Catena-X network in order to communicate with each other. With the help of the Credential Service and the Identity Access Management (IAM) each participant can authenticate itself, verify the identity of the requesting party and decide whether to authorize the request. The Planned Production Output data is provisioned in accordance with [CX-0002].
Figure 1: high-level architecture of the Planned Production Output Exchange in Catena-X
1.3 CONFORMANCE AND PROOF OF CONFORMITY
This section is non-normative
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative. The keywords MAY , MUST , MUST NOT , OPTIONAL , RECOMMENDED , REQUIRED , SHOULD and SHOULD NOT in this document are to be interpreted as described in [BCP 14] [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
All participants and their solutions will need to prove, that they are conform with the Catena-X standards. To validate that the standards are applied correctly, Catena-X employs Conformity Assessment Bodies (CABs). The proof of conformity for a single semantic model is done according to the general rules for proving the conformity of data provided to a semantic model or the ability to consume the corresponding data. Furthermore, participants agree to follow the normative language of this standardization document and to implement the required API-Endpoints described in Chapter 4.
1.4 EXAMPLES
The following JSON provides an example of the value-only serialization of the "PlannedProductionOutput" aspect model. It contains the Planned Production Output quantities for three consecutive days in two different sites (BPNS).
{
"materialGlobalAssetId":"urn:uuid:48878d48-6f1d-47f5-8ded-a441d0d879df",
"positions":[
{
"lastUpdatedOnDateTime":"2023-04-01T14:23:00+01:00",
"orderPositionReference": {
"supplierOrderId":"M-Nbr-4711",
"customerOrderId":"C-Nbr-4711",
"customerOrderPositionId":"PositionId-01"
},
"allocatedPlannedProductionOutputs":[
{
"plannedProductionQuantity":{
"value": 10,
"unit":"unit:piece"
},
"productionSiteBpns":"BPNS0123456789ZZ",
"estimatedTimeOfCompletion":"2023-04-01T14:23:00+01:00"
},
{
"plannedProductionQuantity":{
"value":20,
"unit":"unit:piece"
},
"productionSiteBpns":"BPNS0123456789YZ",
"estimatedTimeOfCompletion":"2023-04-02T14:23:00+01:00"
},
{
"plannedProductionQuantity":{
"value": 10,
"unit":"unit:piece"
},
"productionSiteBpns":"BPNS0123456789ZZ",
"estimatedTimeOfCompletion":"2023-04-03T14:23:00+01:00"
}
]
}
]
}
1.5 TERMINOLOGY
This section is non-normative
Name | Abrv. | Description |
---|---|---|
Business Partner Number | BPN | A BPN is the unique identifier of a partner within Catena-X as defined in [CX-0010]. |
Business Partner Number Legal Entity | BPNL | A BPNL is the unique identifier of a partner legal entity within Catena-X as defined in [CX-0010]. |
Business Partner Number Site | BPNS | A BPNS is the unique identifier of a partner site within Catena-X as defined in [CX-0010]. |
Business Partner Number Address | BPNA | A BPNA is the unique identifier of a partner address within Catena-X as defined in [CX-0010]. |
Position | A position within an order defines the product and the quantity the supplier has to manufacture / supply for a customer. A single order may contain multiple positions for different products. | |
Order | Request from a customer towards a supplier to manufacture / supply a given quantity of a specific product in a predefined time frame. | |
Allocated Stock | The already manufactured and not yet been used products, components or material. They are allocated to a specific customer based on the orders made by the latter and are either still in the supplier's warehouse or already in the customer's warehouse. | |
Provider | The party providing the Planned Production Output data. In the context of the Planned Production Output exchange API this is the supplier. | |
Consumer | The party requesting and consuming the Planned Production Output data provided by the provider. In the context of the Planned Production Output exchange API this is the customer. | |
Stock Location | The physical location of a stock specified by its corresponding BPNS and BPNA. More information on BPN/S/A is provided in [CX-0010]. | |
Customer | The recipient of products ordered from / manufactured by a supplier. | |
Supplier | The supplier / manufacturer of a product. | |
Stock | Two way direction of material on stock: - One can have a stock of material which is ready for delivery to customers. - One can have a stock of material which can be used for the own production. | |
Material | The term material is used as a catalogue item in the meaning of the Industry Core Part Type ([CX-0126]). Whenever referring to material also products, components or items are considered. Semi-finished goods are not intended to be covered. | |
Production Output | The output quantity in a defined period of time for a component or material. | |
Digital Twin | DT | Digital representation of an asset that provides data on aspects of the represented data following [CX-0002]. |
decentralized Digital Twin Registry | dDTR | Component providing registration and discovery API implementations following [CX-0002]. Sometimes referred to without the "decentralized" BUT in Catena-X those are always decentralized. |
Asset Administration Shell | AAS | Technical concept for Digital Twins consisting of different standards. Application in Catena-X is described in Digital Twins in Catena-X standard ([CX-0002]) |
Shell Descriptor | Technical concept of the AAS API describing metadata of an Asset Administration Shell representing a Digital Twin. It holds identification information and metadata about which submodels are available and where to get the data from (see [CX-0002], [IDTA-01002-3-0]). There may exist multiple Shell Descriptor for the same represented Asset (see [CX-0126]). | |
Submodel Descriptor | Technical concept of the AAS API describing metadata of Submodels within a Shell Descriptor (Asset Administration Shell) (see [CX-0002], [IDTA-01002-3-0]). | |
Specific Asset Ids | Identifiers of the Shell Descriptor (Asset Administration Shell) that refer to common identification data for an asset/material at hand e.g., manufacturer part Id. Common specific asset ids used for identification are described in Industry Core Part Type Standard (see [CX-0126]). | |
Asset Administration Shell Identifier | AAS ID | Also referred to as Shell Descriptor Id, is the technical identifier of the Shell Descriptor. |
Global Asset Id | Also referred to as Catena-X Id, is the Catena-X identifier for assets represented by Digital Twins (see [CX-0126]). | |
Aspect | A domain-specific view on information and functionality associated with a specific Digital Twin with a reference to a concrete Aspect Model (see [CX-0002]). Within Catena-X, an aspect is formally described using the Semantic Aspect Meta Model (see [CX-0003]). | |
Semantic Id | Identifier including namespace to specify the semantic description of submodels using the Semantic Aspect Meta Model (SAMM). It allows partners to know the exact data format and semantics when e.g., browsing catalogs (see [CX-0003]). | |
Data Space Protocol | DSP | A set of specifications designed to facilitate interoperable data sharing between entities governed by usage control and based on Web technologies. These specifications define the schemas and protocols required for entities to publish data, negotiate Agreements, and access data as part of a Dataspace. It is governed by the International Data Spaces Association. Connectors compliant to [CX-0018] support the Data Space Protocol. |
Table 1: Terminology Planned Production Output Standard
Additional terminology used in this standard can be looked up in the glossary on the association homepage.
2 RELEVANT PARTS OF THE STANDARD FOR SPECIFIC USE CASES
This section is normative
2.1 Planned Production Output Exchange
2.1.1 LIST OF STANDALONE STANDARDS
The following Catena-X standards are prerequisites for the implementation of this standard and therefore MUST be considered / implemented by the relevant parties specified in each of them.
Number | Standard | Version |
---|---|---|
[CX-0001] | EDC Discovery API | 1.0.2 |
[CX-0002] | Digital Twins in Catena-X | 2.2.0 |
[CX-0003] | SAMM Aspect Meta Model | 1.1.0 |
[CX-0006] | Registration and initial onboarding | 2.0.0 |
[CX-0010] | Business Partner Number (BPN) | 2.0.0 |
[CX-0018] | Dataspace Connectivity | 3.0.0 |
[CX-0126] | Industry Core Part Type | 2.0.0 |
Table 2: List of mandatory standards
The usage of this standard may be complemented with the following Catena-X standards to further extend the range of shortage prevention possibilities:
Number | Standard | Version |
---|---|---|
[CX-0118] | Delivery Information Exchange | 2.0.0 |
[CX-0120] | Short-term Material Demand Exchange | 2.0.0 |
[CX-0122] | Item Stock Exchange | 2.0.0 |
[CX-0145] | Days of Supply Exchange | 1.0.0 |
[CX-0146] | Supply Chain Disruption Notifications | 1.0.0 |
Table 3: List of non-mandatory complementary standards
2.1.2 DATA REQUIRED
No additional data requirements
2.1.3 POLICY CONSTRAINTS FOR 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 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 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 1.1 AUDIENCE & SCOPE is specified in the CX-0152 standard document as well.