From 06771885665941874d2224b584178cdd24fa25a9 Mon Sep 17 00:00:00 2001 From: tobzahn <147095229+tobzahn@users.noreply.github.com> Date: Mon, 12 Jan 2026 13:38:50 +0100 Subject: [PATCH 01/13] DCM update to incorporate changes from standard update --- .../use-case/business-process.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md index 6e42902af235..8a6c1d8cb34c 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md @@ -396,7 +396,7 @@ Embedded into the WeekBasedCapacityGroup are - **Actual Capacity** as the planned available capacity of a supplier - **Maximum Capacity** as the maximum releasable capacity of a supplier -- **Agreed Capacity** as the understanding between Customer and supplier, regardless of contractual obligations. It is optional. +- **Agreed Capacity** as the understanding between Customer and supplier. It is optional. In addition the difference between actual capacity and maximum capacity is commonly understood as flexible capacity. @@ -859,6 +859,23 @@ block-beta Figure: *A small supply network built by seven capacity groups* +### Specific cross-company scenerios +This section gives an overview of some potential cases in cross-company scenarios and how to handle them. + +- **Directed buy**: in this case a company (e.g. an OEM) asks its supplier A to buy parts from supplier B, whereas + - The purchasing contracts are in place between supplier A and B. The OEM has only a contract with supplier A. + - Following the Catena-X DCM process, supplier A creates demands and sends them to supplier B who replies with the according capacity information. + - The OEM is not involved since the OEM is not part of the contract and therefore does not receive any data related to demand and/or capacity exchange between supplier A and B. +- **Customer supplied material**: in this case, the customer (e.g. an OEM) orders part 1 at supplier A (Tier-2) and provides them to supplier B (Tier-1) to produce part 2 that is delivered to the OEM. + - If the part 1 is delivered by supplier A to the OEM and then transported to the supplier B, for the Catena-X DCM process the OEM creates the demands and sends them to the supplier A. + - In case the part 1 is ordered by the OEM from supplier A but delivered directly to supplier B, for the Catena-X DCM process the OEM creates demands and sends it to supplier A, indicating a delivery location BPNS belonging to supplier B. +- **Contract manufacturing / cooperation plants**: in case of manufacturing plants co-owned by multiple companies or producing on behalf of other companies, a possible solution is to create the plant as BPNS for all manufacturers involved. For example, if a plant is co-owned by OEMs A and B, two BPNS can be created (one each for the BPNL of OEM A and B). That way, each OEM can send out his respective demand using his own BPNL and BPNS, avoiding confusion. +- **Joint ventures**: joint ventures are often separate legal entities and are operated independently, therefore they would need to be onboarded to Catena-X as a separate BPNL with separate BPNS. + +**Note**: in all cases, the demands need to be send out by the company who orders the parts (i.e. is the purchasing party in the contract and pays for the parts). + + + ## Match and Comparison of Demand and Capacity ```mermaid From 6928a6dcc6faed08b80967ad84743b056de0f3ac Mon Sep 17 00:00:00 2001 From: Stefania Lanfranchini <104498106+lanfrans@users.noreply.github.com> Date: Mon, 2 Feb 2026 14:26:00 +0100 Subject: [PATCH 02/13] Update glossary.md terminology was updated --- .../adoption-view/glossary.md | 21 ++++++++++--------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/glossary.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/glossary.md index 750dbecb78a0..9ce6b0188101 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/glossary.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/glossary.md @@ -10,32 +10,33 @@ description: Glossary |Term|Description| |----|-----------| -|Actual Capacity|This is the capacity a supplier realistically plans to have available to satisfy the demand of a certain material per week for a specific customer. It considers the supplier’s own assessment of their capabilities, inventory and existing commitments.| -|Agreed Capacity|This is a capacity value coordinated between customer and supplier and it may refer e.g. to capacity values defined in mutually agreed contracts. Using the agreed capacity is optional, it has purely informative character and therefore does not constitute a legal obligation to deliver. The agreed capacity may be greater than, less than or equal to the actual or Maximum Capacity. It may be used for a time frame different than the whole time series.| +|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. Can be used to document a capacity agreed in a contract. The agreed capacity must not constitute a legal obligation to deliver (as this would need to be done e.g. in a contract outside Catena-X DCM). 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.| |API|Application Programming Interface is a set of rules, protocols, and tools for building software and applications. Examples for DCM can be found here: [Development View - APIs utilized by a DCM application](../software-development-view/overview.md#apis-utilized-by-a-dcm-application)| -|Aspect Model|See: [CX-0002 Digital Twins in Catena-X][StandardLibrary]| +|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. See: [CX-0002 Digital Twins in Catena-X][StandardLibrary]| |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|Typically, it is a third party that offers tools to data consumers and data providers for demand and capacity management purposes that conform to the core business logic, data models and APIs described in the Catena-X DCM standard.| -|Business Partner Number Legal Entity (BPNL)|See: [CX-0010 Business Partner Number][StandardLibrary]| -|Business Partner Number Site (BPNS)|See: [CX-0010 Business Partner Number][StandardLibrary]| +|Business Partner Number Legal Entity (BPNL)|A BPNL is an unique identifier for a company or partner within the Catena-X network. See: [CX-0010 Business Partner Number][StandardLibrary]| +|Business Partner Number Site (BPNS)|A BPNS is an unique identifier for a specific location, such as a factory, within the Catena-X network. See: [CX-0010 Business Partner Number][StandardLibrary]| |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 a virtual entity that contains capacity information, which depend on production capabilities (based e.g. on grouping of one or more machines, plants, production lines or similar), as well as the material demands linked to it. The capacity group is the place where demand and capacity information come together and are compared, in order to recognize production bottlenecks and/or surplus. When written as WeekBasedCapacityGroup, it refers to a specific data model within this standard.| -|Comments|A feature that allows two business partners to exchange messages about material demand and capacity, facilitating direct collaboration and quick issue resolution.| +|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.| |Customer|A role within the DCM use case, which represents a company that receives goods from its suppliers. Participating companies can have multiple roles at the same time: in this context, a customer provides consistent and up-to-date demand forecast to and receives capacity data from suppliers. Synonym: one-up.| |Data Consumer|A data consumer refers to any entity that retrieves and uses data from a source. This can be an individual, application, or system that accesses and processes data for various purposes or simply in context of Catena-X receiving data from a business partner.| |Data Provider|A data provider is an entity that supplies or makes data available to others. In case of Catena-X, this can be a business partner supplying information. In the context of information technology and data management, a data provider can be a database, a web service, an API, a file system, or any other system that allows data to be accessed by data consumers.| -|(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 values published to customers. See also pre-/post-production.| +|Delta-Production|This is an optional feature that allows suppliers to manage capacity bottlenecks by shifting demand from one week to another in production without altering actual capacity, maximum capacity or the material demand. See also pre-/post-production.| |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.| |Demand Volatility|Demand Volatility help suppliers to identify and measure volatility in demands. It allows them to address demand volatility directly to their customers, increasing transparency for a more effective collaborative capacity planning. Demand deviation is the first metric for measuring demand volatility.| -|Digital Twin|See: [CX-0002 Digital Twins in Catena-X][StandardLibrary].| -|Flexible Capacity|The difference between maximum and Actual Capacity, which represents the measures to potentially increase capacity without further agreements between partners, such as extending the utilization of production resources within a week.| +|Digital Twin|Based on [[CX-0002](#71-normative-references)] 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](#71-normative-references)] 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.| |JSON|The JavaScript Object Notation (JSON) is a standard text-based format for representing structured data based on JavaScript object syntax. It is commonly used for transferring data in web applications (e.g. sending some data from the server to the client, so it can be displayed on a web page, or vice versa).| |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|An optional feature of a capacity group that adds individual numerical material load factors to WeekBasedMaterialDemand linked by the WeekBasedCapacityGroup. It 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 of. 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 (e.g. 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|This is the highest achievable production capacity of a supplier within a given calendar week, in a certain unit of measure, for a specific customer. The Maximum Capacity is equal or higher than the Actual Capacity. It considers further capacity-increasing measures that have been planned upfront between the parties involved and can be activated whenever needed. Capacity-increasing measures can be, e.g. a longer utilization of the available production resources, a shift extension or additional shifts. Secondarily, additional resources can also be activated.| +|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 to another capacity group (instead to material demand series), allowing for dynamic changes and centralized data management. See also: linking material demand. Synonym: indirect linking| |One-down|Synonym: “supplier”| |One-up|Synonym: “customer”| From beb696ff987862c830180e08b809817f76b79147 Mon Sep 17 00:00:00 2001 From: Stefania Lanfranchini <104498106+lanfrans@users.noreply.github.com> Date: Mon, 2 Feb 2026 14:29:51 +0100 Subject: [PATCH 03/13] Update rfu.md text added --- .../adoption-view/use-case/rfu.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/rfu.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/rfu.md index 7e4f8b48dfff..ceda174bf0d0 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/rfu.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/rfu.md @@ -9,7 +9,11 @@ sidebar_position: 5 ## Business Roles and Functions -Request for update uses its own aspect model and API. Request for update is provided and consumed by both customer and supplier. +Request for update uses its own aspect model and API. Customers and Supplier must be able to consume and process a RfU. Being able to provide a RfU is recommended. + +To properly process a RfU, the following steps must be executed: +1. Response: Answering with the appropriate HTTP status code +2. Action: If that status code is `200 OK`: Providing the requested material demands and capacity groups via `WeekBasedMaterialDemand` API or `WeekBasedCapacityGroup` API respectively. |Function / Role|Customer|Supplier| |-|-|-| From 959f147016704f8041dcbe7f7923670382c9101f Mon Sep 17 00:00:00 2001 From: Stefania Lanfranchini <104498106+lanfrans@users.noreply.github.com> Date: Wed, 4 Feb 2026 17:09:10 +0100 Subject: [PATCH 04/13] Update overview.md table Access and Usage Policies updated --- .../adoption-view/overview.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md index 649e1634c5d8..42d1d872f2c5 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md @@ -137,12 +137,14 @@ Because of the way that communication within CX-0128 is defined companies are no Conforming to [CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary] the following policies have to be applied. -| Category | Policy Name | Description |Usage recommendation| -|:---------|:------------|:------------|:-------------------| -| **Access Policy** | BPN-restricted Data Usage | Limit access to the data offered to a list of specified BPNs (to the connectors with the BPN attribute listed in the policy) |Limit access to assets to all your known business partners.| -| **Access Policy** | Membership Credential | Limit access to data offered to Catena-X participants |Use as is.| -| **Usage Policy** | DCM Framework Agreement Credential | Limit access to data offered to participants who have signed the DCM Framework Agreement |Use as is.| - +| Policy Type | Constraint | leftOperand ("@context": ["https://w3id.org/catenax/2025/9/policy/context.jsonld"]) | operator | right Operand | Usage Requirement | +| -- | -- | -- | -- | -- | -- | +| Access Policy | BPNL | BusinessPartnerNumber | isAnyOf, isNoneOf | `{{ PARTNER_BPNLs }}` | optional | +| Access Policy | BPNL-Group | BusinessPartnerGroup | isAnyOf, isNoneOf | `{{ PARTNER_GROUPs }}` | optional | +| Access Policy | Membership | Membership | eq | active | optional | +| **Usage Policy** | Data Exchange Governance | FrameworkAgreement | eq | DataExchangeGovernance:1.0 | mandatory | +| **Usage Policy** | Usage Purpose | UsagePurpose | isAnyOf | cx.dcm.base:1 | mandatory | +| Usage Policy | Contract Reference | ContractReference | isAllOf | `{{ Contract References }}` | optional | ### Standards |Content|Standard|Version|Section|Description| From b8e2d5c8033f7647f51c2f58d1d40cf534740acf Mon Sep 17 00:00:00 2001 From: Stefania Lanfranchini <104498106+lanfrans@users.noreply.github.com> Date: Wed, 4 Feb 2026 17:24:41 +0100 Subject: [PATCH 05/13] Update overview.md Reference to standard updated --- .../adoption-view/overview.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md index 42d1d872f2c5..f4ffc3327373 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md @@ -149,10 +149,10 @@ Because of the way that communication within CX-0128 is defined companies are no |Content|Standard|Version|Section|Description| |-|-|-|-|-| -|DCM Business Logic|[CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary]|2.1.0|5|Focuses on a common understanding of the DCM processes among participants.| -|DCM Aspect Models|[CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary]|2.1.0|3|Aligns the structure of the shared information and enables the adoption of the core business logic without misinterpretation.| -|DCM APIs|[CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary]|2.1.0|4|Ensures that data is provided and consumed properly as well as identically interpreted across companies.| -|Notification Process, Aspect Model and API|[CX-0146 Supply Chain Disruption Notifications][StandardLibrary]|1.0.0|*|Optional capability referenced in Section 5.10 of CX-0128. Focuses on quickly informing business partners of impactful events, where the impact cannot be precisely quantified yet.| +|DCM Business Logic|[CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary]|2.2.1|5|Focuses on a common understanding of the DCM processes among participants.| +|DCM Aspect Models|[CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary]|2.2.1|3|Aligns the structure of the shared information and enables the adoption of the core business logic without misinterpretation.| +|DCM APIs|[CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary]|2.2.1|4|Ensures that data is provided and consumed properly as well as identically interpreted across companies.| +|Notification Process, Aspect Model and API|[CX-0146 Supply Chain Disruption Notifications][StandardLibrary]|2.0.1|*|Optional capability referenced in Section 5.10 of CX-0128. Focuses on quickly informing business partners of impactful events, where the impact cannot be precisely quantified yet.| ## Frequently asked Questions From bce838e8eb79af47ea545078c33938d74da5475e Mon Sep 17 00:00:00 2001 From: Stefania Lanfranchini <104498106+lanfrans@users.noreply.github.com> Date: Wed, 4 Feb 2026 17:38:11 +0100 Subject: [PATCH 06/13] Update business-process.md Customer Location added in WeekBasedCapacityGroup properties --- .../adoption-view/use-case/business-process.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md index 8a6c1d8cb34c..86c9e2097a51 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md @@ -640,6 +640,7 @@ A capacity group dataset comprises the following basic components: |-|-|-| | Supplier | Yes |The Business Partner Number Legal (BPNL) of the party providing materials to a customer| | Customer | Yes |The Business Partner Number Legal (BPNL) of the party requesting material from a supplier| +| Customer Location| Yes |The Business Partner Number Site (BPNS) that identifies the location, where a supplier has to deliver the material(s) to. It refers to the BPNS provided by the customer within the WeekBasedMaterialDemand and can by any BPNS (i.e. no matter what BPNL it belongs to). The suppler should assume that the materials requested will be delivered to the named BPNS based on an existing contract between the two BPNLs (i.e. the one that generates the demand and the one that receives the material).| | Capacity Group ID | Yes |The capacity group ID uniquely identifies the capacity group within the business relationship between a supplier and its customer| | Changed At | Yes |Point in time when the content (any property according to the data model) of the capacity group was changed, at the supplier, either by a human user or an automated process| | Capacity Group Name | Yes |Name of the capacity group| From 923e13ec5197bf7a8a0f5ab463903917ec10d1ac Mon Sep 17 00:00:00 2001 From: Stefania Lanfranchini <104498106+lanfrans@users.noreply.github.com> Date: Fri, 6 Feb 2026 14:07:08 +0100 Subject: [PATCH 07/13] Update business-process.md added paraamter table for Material Demand --- .../use-case/business-process.md | 35 +++++++++++++++++-- 1 file changed, 32 insertions(+), 3 deletions(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md index 86c9e2097a51..369aeec4909f 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md @@ -238,6 +238,36 @@ Figure: *Material demand structure* Figure: *Visualizing demand quantities as bars* +### WeekBasedMaterialDemand Properties + +A material demand dataset comprises the following basic components: + +| Main Parameters | Required? | Description | +|-|-|-| +| Supplier | Yes |The Business Partner Number Legal (BPNL) of the party providing materials to a customer| +| Customer | Yes |The Business Partner Number Legal (BPNL) of the party requesting material from a supplier| +| Material Demand ID | Yes |The material demand ID uniquely identifies the material demand within the business relationship between a customers and its supplier| +| Changed At | Yes |Point in time when the content (any property according to the data model) of the material demand was changed, at the customer, either by a human user or an automated process| +| Material Description Customer | Yes |Description of the material, which a demand refers to| +| Customer Material Number | Yes |Material identifier as assigned by the customer. This material number identifies the material (as planned) in customer's database. It must be unique for each Material Demands in the customer-supplier relationship| +| Supplier Material Number | No |Material identifier as assigned by the supplier. This material number identifies the material (as planned) in supplier's database| +| Material Demand is Inactive | Yes |Indicates that this material demand is currently not in use/maintained by the customer| +| Unit of Measure | No |Unit of Measurement (UoM) for demand quantities| +| Demand Series | Yes |The demands for a dedicated material in a given time period of a given demand rate, distinguished by their demand location and demand category| +| Unit of Measure is Omitted | Yes |Explicit indicator of whether the unit of measure is left out of the payload intentionally. If “true” it means the sending application sends the demand values without unit of measure intentionally and the unit of measure must not be contained in the payload. If “false” a unit of measure must be supplied| +| Material Global Asset ID | No |Identifier used uniquely to identify part type twin (Digital Twin)| + +Further properties are added at lower level below the “Demand Series” property. Demand Series contain the following components. + +| Main Parameters | Required? | Description | +|-|-|-| +| Customer Location | Yes |The Business Partner Number Site (BPNS) of the site at which the customer needs the specified material for this demand series. It refers to the BPNS provided by the customer within the WeekBasedMaterialDemand and can be any BPNS (i.e. no matter what BPNL it belongs to). The supplier should assume that the materials requested will be delivered to the named BPNS based on an existing contract between the Business Partner that generates the demand and the Business Partner that receives the material| +| Expected Supplier Location | No |The Business Partner Nomber Site (BPNS) of the site from where the cusomer expects the supplier to fulfill the demands of the demand series. The value is used for i nformational purposes only and is therefore not binding for the supplier| +| Demand | Yes |Quantity of materials required for the specified point in time. This demand should be as close as possible to the demand that is derived from the actual production program| +| Point in Time | Yes |ISO calendar week in which the given demand is needed. It must be given as a date of the Monday in the week.| +| Demand Category Code | Yes |The code identifying a demand category as described in the standard under Demand Category Types| + + ## Capacity Group ```mermaid @@ -640,15 +670,14 @@ A capacity group dataset comprises the following basic components: |-|-|-| | Supplier | Yes |The Business Partner Number Legal (BPNL) of the party providing materials to a customer| | Customer | Yes |The Business Partner Number Legal (BPNL) of the party requesting material from a supplier| -| Customer Location| Yes |The Business Partner Number Site (BPNS) that identifies the location, where a supplier has to deliver the material(s) to. It refers to the BPNS provided by the customer within the WeekBasedMaterialDemand and can by any BPNS (i.e. no matter what BPNL it belongs to). The suppler should assume that the materials requested will be delivered to the named BPNS based on an existing contract between the two BPNLs (i.e. the one that generates the demand and the one that receives the material).| | Capacity Group ID | Yes |The capacity group ID uniquely identifies the capacity group within the business relationship between a supplier and its customer| | Changed At | Yes |Point in time when the content (any property according to the data model) of the capacity group was changed, at the supplier, either by a human user or an automated process| | Capacity Group Name | Yes |Name of the capacity group| -| Capacity Group is Inactive | Yes |Indicates that this capacity Group is currently not in use/maintained by the Supplier| +| Capacity Group is Inactive | Yes |Indicates that this capacity group is currently not in use/maintained by the supplier| | Unit of Measure | No |Unit of Measurement (UoM) for capacity quantities| | Linked Demand Series | No |Set of demand series assigned to this capacity group| | Capacities | No |A time series with week-based granularity along a given time period containing the capacity values| -| Unit of Measure is Omitted | Yes |Explicit indicator of whether the unit of measure is left out of the payload intentionally. If “true” it means the sending application sends the demand values without unit of measure intentionally and the unit of measure must not be contained in the payload. If “false” a unit of measure must be supplied| +| Unit of Measure is Omitted | Yes |Explicit indicator of whether the unit of measure is left out of the payload intentionally. If “true” it means the sending application sends the capacity values without unit of measure intentionally and the unit of measure must not be contained in the payload. If “false” a unit of measure must be supplied| Further properties are added at lower level below the “Capacities” property. A capacity time series contains the following components. From e6511570dc45cb7a79cc39c7dbb0824b13932c4f Mon Sep 17 00:00:00 2001 From: Stefania Lanfranchini <104498106+lanfrans@users.noreply.github.com> Date: Fri, 6 Feb 2026 14:16:03 +0100 Subject: [PATCH 08/13] Update overview.md URI in URL amended --- .../software-development-view/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/software-development-view/overview.md b/docs-kits/kits/demand-and-capacity-management-kit/software-development-view/overview.md index f75e946e7cb8..de92c0383134 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/software-development-view/overview.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/software-development-view/overview.md @@ -58,7 +58,7 @@ A MVP approach can be followed when developing software, implementing CX-0128, b ### APIs as data assets -The data consumer registers one data-asset per API with its own EDC. Those data-assets need a `dataAddress` with a `baseURL` pointing to the URI of the API endpoint. The same `dataAddress` needs to be setup to use the consumers EDC as a proxy, utilizing the different proxy related properties within the `dataAddress` object. +The data consumer registers one data-asset per API with its own EDC. Those data-assets need a `dataAddress` with a `baseURL` pointing to the URL of the API endpoint. The same `dataAddress` needs to be setup to use the consumers EDC as a proxy, utilizing the different proxy related properties within the `dataAddress` object. #### Asset example From 68ea5d7c7241baecab2be67a6041030f81242bdb Mon Sep 17 00:00:00 2001 From: LukasSchmetz <120170734+LukasSchmetz@users.noreply.github.com> Date: Fri, 6 Feb 2026 14:59:37 +0100 Subject: [PATCH 09/13] Typo correction --- .../adoption-view/use-case/business-process.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md index 369aeec4909f..0a65b22364af 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md @@ -889,7 +889,7 @@ block-beta Figure: *A small supply network built by seven capacity groups* -### Specific cross-company scenerios +### Specific cross-company scenarios This section gives an overview of some potential cases in cross-company scenarios and how to handle them. - **Directed buy**: in this case a company (e.g. an OEM) asks its supplier A to buy parts from supplier B, whereas @@ -902,7 +902,7 @@ This section gives an overview of some potential cases in cross-company scenario - **Contract manufacturing / cooperation plants**: in case of manufacturing plants co-owned by multiple companies or producing on behalf of other companies, a possible solution is to create the plant as BPNS for all manufacturers involved. For example, if a plant is co-owned by OEMs A and B, two BPNS can be created (one each for the BPNL of OEM A and B). That way, each OEM can send out his respective demand using his own BPNL and BPNS, avoiding confusion. - **Joint ventures**: joint ventures are often separate legal entities and are operated independently, therefore they would need to be onboarded to Catena-X as a separate BPNL with separate BPNS. -**Note**: in all cases, the demands need to be send out by the company who orders the parts (i.e. is the purchasing party in the contract and pays for the parts). +**Note**: in all cases, the demands need to be sent out by the company who orders the parts (i.e. is the purchasing party in the contract and pays for the parts). From b656fdb28f332c1e84178e433dbc50f390e8c777 Mon Sep 17 00:00:00 2001 From: LukasSchmetz <120170734+LukasSchmetz@users.noreply.github.com> Date: Wed, 18 Feb 2026 11:23:58 +0100 Subject: [PATCH 10/13] Specify Admin Role within RfU functionality Admin is only business partner internal person and nobody in the role of an admin configures the RfU itself --- .../software-development-view/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/software-development-view/overview.md b/docs-kits/kits/demand-and-capacity-management-kit/software-development-view/overview.md index de92c0383134..376de6b7f253 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/software-development-view/overview.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/software-development-view/overview.md @@ -45,7 +45,7 @@ A MVP approach can be followed when developing software, implementing CX-0128, b |-|-| |Customer| - Modify WeekBasedMaterialDemand
- Compare WeekBasedMaterialDemand to WeekBasedCapacityGroup
- Utilize comments
- Utilize supply chain disruption notification| |Supplier| - Modify WeekBasedCapacityGroup
- Compare WeekBasedMaterialDemand to WeekBasedCapacityGroup
- Link WeekBasedMaterialDemand to WeekBasedCapacityGroup
- Utilize comments
- Utilize supply chain disruption notification| -|Admin| - Configure Request for update| +|Admin| - Configure Request for update within its own company| ## Aspect models utilized by a DCM application From 111bfdc87547054de0aa82167232def9b1b15137 Mon Sep 17 00:00:00 2001 From: tobzahn <147095229+tobzahn@users.noreply.github.com> Date: Fri, 20 Feb 2026 09:14:58 +0100 Subject: [PATCH 11/13] fixed typo --- .../adoption-view/use-case/business-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md index 0a65b22364af..fdf39263a680 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md @@ -262,7 +262,7 @@ Further properties are added at lower level below the “Demand Series” proper | Main Parameters | Required? | Description | |-|-|-| | Customer Location | Yes |The Business Partner Number Site (BPNS) of the site at which the customer needs the specified material for this demand series. It refers to the BPNS provided by the customer within the WeekBasedMaterialDemand and can be any BPNS (i.e. no matter what BPNL it belongs to). The supplier should assume that the materials requested will be delivered to the named BPNS based on an existing contract between the Business Partner that generates the demand and the Business Partner that receives the material| -| Expected Supplier Location | No |The Business Partner Nomber Site (BPNS) of the site from where the cusomer expects the supplier to fulfill the demands of the demand series. The value is used for i nformational purposes only and is therefore not binding for the supplier| +| Expected Supplier Location | No |The Business Partner Number Site (BPNS) of the site from where the customer expects the supplier to fulfill the demands of the demand series. The value is used for informational purposes only and is therefore not binding for the supplier| | Demand | Yes |Quantity of materials required for the specified point in time. This demand should be as close as possible to the demand that is derived from the actual production program| | Point in Time | Yes |ISO calendar week in which the given demand is needed. It must be given as a date of the Monday in the week.| | Demand Category Code | Yes |The code identifying a demand category as described in the standard under Demand Category Types| From 7e4f6ef5f9bdd75895e17bf48ce67f5bef3fd9f6 Mon Sep 17 00:00:00 2001 From: LukasSchmetz <120170734+LukasSchmetz@users.noreply.github.com> Date: Fri, 20 Feb 2026 10:08:12 +0100 Subject: [PATCH 12/13] common handling in parameter table overview 1) "." at the end of a sentence if there are multiple sentences within one description. 2) blank spaces at the beginning and the end of the description of each parameter --- .../use-case/business-process.md | 62 +++++++++---------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md index fdf39263a680..aa37c952a861 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md @@ -244,28 +244,28 @@ A material demand dataset comprises the following basic components: | Main Parameters | Required? | Description | |-|-|-| -| Supplier | Yes |The Business Partner Number Legal (BPNL) of the party providing materials to a customer| -| Customer | Yes |The Business Partner Number Legal (BPNL) of the party requesting material from a supplier| -| Material Demand ID | Yes |The material demand ID uniquely identifies the material demand within the business relationship between a customers and its supplier| -| Changed At | Yes |Point in time when the content (any property according to the data model) of the material demand was changed, at the customer, either by a human user or an automated process| -| Material Description Customer | Yes |Description of the material, which a demand refers to| -| Customer Material Number | Yes |Material identifier as assigned by the customer. This material number identifies the material (as planned) in customer's database. It must be unique for each Material Demands in the customer-supplier relationship| -| Supplier Material Number | No |Material identifier as assigned by the supplier. This material number identifies the material (as planned) in supplier's database| -| Material Demand is Inactive | Yes |Indicates that this material demand is currently not in use/maintained by the customer| -| Unit of Measure | No |Unit of Measurement (UoM) for demand quantities| -| Demand Series | Yes |The demands for a dedicated material in a given time period of a given demand rate, distinguished by their demand location and demand category| -| Unit of Measure is Omitted | Yes |Explicit indicator of whether the unit of measure is left out of the payload intentionally. If “true” it means the sending application sends the demand values without unit of measure intentionally and the unit of measure must not be contained in the payload. If “false” a unit of measure must be supplied| -| Material Global Asset ID | No |Identifier used uniquely to identify part type twin (Digital Twin)| +| Supplier | Yes | The Business Partner Number Legal (BPNL) of the party providing materials to a customer | +| Customer | Yes | The Business Partner Number Legal (BPNL) of the party requesting material from a supplier | +| Material Demand ID | Yes | The material demand ID uniquely identifies the material demand within the business relationship between a customers and its supplier | +| Changed At | Yes | Point in time when the content (any property according to the data model) of the material demand was changed, at the customer, either by a human user or an automated process | +| Material Description Customer | Yes | Description of the material, which a demand refers to | +| Customer Material Number | Yes | Material identifier as assigned by the customer. This material number identifies the material (as planned) in customer's database. It must be unique for each Material Demands in the customer-supplier relationship. | +| Supplier Material Number | No | Material identifier as assigned by the supplier. This material number identifies the material (as planned) in supplier's database | +| Material Demand is Inactive | Yes | Indicates that this material demand is currently not in use/maintained by the customer | +| Unit of Measure | No | Unit of Measurement (UoM) for demand quantities | +| Demand Series | Yes | The demands for a dedicated material in a given time period of a given demand rate, distinguished by their demand location and demand category | +| Unit of Measure is Omitted | Yes | Explicit indicator of whether the unit of measure is left out of the payload intentionally. If “true” it means the sending application sends the demand values without unit of measure intentionally and the unit of measure must not be contained in the payload. If “false” a unit of measure must be supplied. | +| Material Global Asset ID | No | Identifier used uniquely to identify part type twin (Digital Twin) | Further properties are added at lower level below the “Demand Series” property. Demand Series contain the following components. | Main Parameters | Required? | Description | |-|-|-| -| Customer Location | Yes |The Business Partner Number Site (BPNS) of the site at which the customer needs the specified material for this demand series. It refers to the BPNS provided by the customer within the WeekBasedMaterialDemand and can be any BPNS (i.e. no matter what BPNL it belongs to). The supplier should assume that the materials requested will be delivered to the named BPNS based on an existing contract between the Business Partner that generates the demand and the Business Partner that receives the material| -| Expected Supplier Location | No |The Business Partner Number Site (BPNS) of the site from where the customer expects the supplier to fulfill the demands of the demand series. The value is used for informational purposes only and is therefore not binding for the supplier| -| Demand | Yes |Quantity of materials required for the specified point in time. This demand should be as close as possible to the demand that is derived from the actual production program| -| Point in Time | Yes |ISO calendar week in which the given demand is needed. It must be given as a date of the Monday in the week.| -| Demand Category Code | Yes |The code identifying a demand category as described in the standard under Demand Category Types| +| Customer Location | Yes | The Business Partner Number Site (BPNS) of the site at which the customer needs the specified material for this demand series. It refers to the BPNS provided by the customer within the WeekBasedMaterialDemand and can be any BPNS (i.e. no matter what BPNL it belongs to). The supplier should assume that the materials requested will be delivered to the named BPNS based on an existing contract between the Business Partner that generates the demand and the Business Partner that receives the material. | +| Expected Supplier Location | No | The Business Partner Number Site (BPNS) of the site from where the customer expects the supplier to fulfill the demands of the demand series. The value is used for informational purposes only and is therefore not binding for the supplier. | +| Demand | Yes | Quantity of materials required for the specified point in time. This demand should be as close as possible to the demand that is derived from the actual production program. | +| Point in Time | Yes | ISO calendar week in which the given demand is needed. It must be given as a date of the Monday in the week. | +| Demand Category Code | Yes | The code identifying a demand category as described in the standard under Demand Category Types | ## Capacity Group @@ -668,25 +668,25 @@ A capacity group dataset comprises the following basic components: | Main Parameters | Required? | Description | |-|-|-| -| Supplier | Yes |The Business Partner Number Legal (BPNL) of the party providing materials to a customer| -| Customer | Yes |The Business Partner Number Legal (BPNL) of the party requesting material from a supplier| -| Capacity Group ID | Yes |The capacity group ID uniquely identifies the capacity group within the business relationship between a supplier and its customer| -| Changed At | Yes |Point in time when the content (any property according to the data model) of the capacity group was changed, at the supplier, either by a human user or an automated process| -| Capacity Group Name | Yes |Name of the capacity group| -| Capacity Group is Inactive | Yes |Indicates that this capacity group is currently not in use/maintained by the supplier| -| Unit of Measure | No |Unit of Measurement (UoM) for capacity quantities| -| Linked Demand Series | No |Set of demand series assigned to this capacity group| -| Capacities | No |A time series with week-based granularity along a given time period containing the capacity values| -| Unit of Measure is Omitted | Yes |Explicit indicator of whether the unit of measure is left out of the payload intentionally. If “true” it means the sending application sends the capacity values without unit of measure intentionally and the unit of measure must not be contained in the payload. If “false” a unit of measure must be supplied| +| Supplier | Yes | The Business Partner Number Legal (BPNL) of the party providing materials to a customer | +| Customer | Yes | The Business Partner Number Legal (BPNL) of the party requesting material from a supplier | +| Capacity Group ID | Yes | The capacity group ID uniquely identifies the capacity group within the business relationship between a supplier and its customer | +| Changed At | Yes | Point in time when the content (any property according to the data model) of the capacity group was changed, at the supplier, either by a human user or an automated process | +| Capacity Group Name | Yes | Name of the capacity group | +| Capacity Group is Inactive | Yes | Indicates that this capacity group is currently not in use/maintained by the supplier | +| Unit of Measure | No | Unit of Measurement (UoM) for capacity quantities | +| Linked Demand Series | No | Set of demand series assigned to this capacity group | +| Capacities | No | A time series with week-based granularity along a given time period containing the capacity values | +| Unit of Measure is Omitted | Yes | Explicit indicator of whether the unit of measure is left out of the payload intentionally. If “true” it means the sending application sends the capacity values without unit of measure intentionally and the unit of measure must not be contained in the payload. If “false” a unit of measure must be supplied. | Further properties are added at lower level below the “Capacities” property. A capacity time series contains the following components. | Main Parameters | Required? | Description | |-|-|-| -| Actual Capacity | Yes |The actual capacity is the realistically planned output per calendar week and material for a specific customer in a specific unit of measure, considering all positive or negative impacts on this capacity| -| Agreed Capacity | No |The agreed capacity of a supplier for a specific customer material(s) within a capacity group. The agreed capacity must not constitute a legal obligation to deliver.| -| Maximum Capacity | Yes |The supplier's maximum capacity is the maximal available output per calendar week and material for a specific customer in a specific unit of measure. The maximum capacity thereby restricts the flexible capacity, as the flexible capacity is obtained from the difference of a suppliers maximum capacity minus actual capacity| -| Point in Time | Yes |ISO calendar week of the given time series entry. It must be given as a date of the Monday in the week.| +| Actual Capacity | Yes | The actual capacity is the realistically planned output per calendar week and material for a specific customer in a specific unit of measure, considering all positive or negative impacts on this capacity | +| Agreed Capacity | No | The agreed capacity of a supplier for a specific customer material(s) within a capacity group. The agreed capacity must not constitute a legal obligation to deliver. | +| Maximum Capacity | Yes | The supplier's maximum capacity is the maximal available output per calendar week and material for a specific customer in a specific unit of measure. The maximum capacity thereby restricts the flexible capacity, as the flexible capacity is obtained from the difference of a suppliers maximum capacity minus actual capacity | +| Point in Time | Yes | ISO calendar week of the given time series entry. It must be given as a date of the Monday in the week. | ### Linking Capacity Groups to Material Demands From c8b7d3851e01b8bac6b4c2299904ac7704ef5ee6 Mon Sep 17 00:00:00 2001 From: Thibault Grandemenge <160125763+Grand-Thibault@users.noreply.github.com> Date: Fri, 27 Feb 2026 09:16:54 +0100 Subject: [PATCH 13/13] fixed linting issues --- .../adoption-view/overview.md | 1 + .../use-case/business-process.md | 20 +++++++++---------- .../adoption-view/use-case/rfu.md | 1 + 3 files changed, 12 insertions(+), 10 deletions(-) diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md index f4ffc3327373..54747baf68ad 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/overview.md @@ -145,6 +145,7 @@ Because of the way that communication within CX-0128 is defined companies are no | **Usage Policy** | Data Exchange Governance | FrameworkAgreement | eq | DataExchangeGovernance:1.0 | mandatory | | **Usage Policy** | Usage Purpose | UsagePurpose | isAnyOf | cx.dcm.base:1 | mandatory | | Usage Policy | Contract Reference | ContractReference | isAllOf | `{{ Contract References }}` | optional | + ### Standards |Content|Standard|Version|Section|Description| diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md index aa37c952a861..ae66151c4352 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/business-process.md @@ -267,7 +267,6 @@ Further properties are added at lower level below the “Demand Series” proper | Point in Time | Yes | ISO calendar week in which the given demand is needed. It must be given as a date of the Monday in the week. | | Demand Category Code | Yes | The code identifying a demand category as described in the standard under Demand Category Types | - ## Capacity Group ```mermaid @@ -890,19 +889,20 @@ block-beta Figure: *A small supply network built by seven capacity groups* ### Specific cross-company scenarios -This section gives an overview of some potential cases in cross-company scenarios and how to handle them. + +This section gives an overview of some potential cases in cross-company scenarios and how to handle them. - **Directed buy**: in this case a company (e.g. an OEM) asks its supplier A to buy parts from supplier B, whereas - The purchasing contracts are in place between supplier A and B. The OEM has only a contract with supplier A. - Following the Catena-X DCM process, supplier A creates demands and sends them to supplier B who replies with the according capacity information. - - The OEM is not involved since the OEM is not part of the contract and therefore does not receive any data related to demand and/or capacity exchange between supplier A and B. -- **Customer supplied material**: in this case, the customer (e.g. an OEM) orders part 1 at supplier A (Tier-2) and provides them to supplier B (Tier-1) to produce part 2 that is delivered to the OEM. - - If the part 1 is delivered by supplier A to the OEM and then transported to the supplier B, for the Catena-X DCM process the OEM creates the demands and sends them to the supplier A. - - In case the part 1 is ordered by the OEM from supplier A but delivered directly to supplier B, for the Catena-X DCM process the OEM creates demands and sends it to supplier A, indicating a delivery location BPNS belonging to supplier B. -- **Contract manufacturing / cooperation plants**: in case of manufacturing plants co-owned by multiple companies or producing on behalf of other companies, a possible solution is to create the plant as BPNS for all manufacturers involved. For example, if a plant is co-owned by OEMs A and B, two BPNS can be created (one each for the BPNL of OEM A and B). That way, each OEM can send out his respective demand using his own BPNL and BPNS, avoiding confusion. -- **Joint ventures**: joint ventures are often separate legal entities and are operated independently, therefore they would need to be onboarded to Catena-X as a separate BPNL with separate BPNS. - -**Note**: in all cases, the demands need to be sent out by the company who orders the parts (i.e. is the purchasing party in the contract and pays for the parts). + - The OEM is not involved since the OEM is not part of the contract and therefore does not receive any data related to demand and/or capacity exchange between supplier A and B. +- **Customer supplied material**: in this case, the customer (e.g. an OEM) orders part 1 at supplier A (Tier-2) and provides them to supplier B (Tier-1) to produce part 2 that is delivered to the OEM. + - If the part 1 is delivered by supplier A to the OEM and then transported to the supplier B, for the Catena-X DCM process the OEM creates the demands and sends them to the supplier A. + - In case the part 1 is ordered by the OEM from supplier A but delivered directly to supplier B, for the Catena-X DCM process the OEM creates demands and sends it to supplier A, indicating a delivery location BPNS belonging to supplier B. +- **Contract manufacturing / cooperation plants**: in case of manufacturing plants co-owned by multiple companies or producing on behalf of other companies, a possible solution is to create the plant as BPNS for all manufacturers involved. For example, if a plant is co-owned by OEMs A and B, two BPNS can be created (one each for the BPNL of OEM A and B). That way, each OEM can send out his respective demand using his own BPNL and BPNS, avoiding confusion. +- **Joint ventures**: joint ventures are often separate legal entities and are operated independently, therefore they would need to be onboarded to Catena-X as a separate BPNL with separate BPNS. + +**Note**: in all cases, the demands need to be sent out by the company who orders the parts (i.e. is the purchasing party in the contract and pays for the parts). diff --git a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/rfu.md b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/rfu.md index ceda174bf0d0..14b2b2bd6ded 100644 --- a/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/rfu.md +++ b/docs-kits/kits/demand-and-capacity-management-kit/adoption-view/use-case/rfu.md @@ -12,6 +12,7 @@ sidebar_position: 5 Request for update uses its own aspect model and API. Customers and Supplier must be able to consume and process a RfU. Being able to provide a RfU is recommended. To properly process a RfU, the following steps must be executed: + 1. Response: Answering with the appropriate HTTP status code 2. Action: If that status code is `200 OK`: Providing the requested material demands and capacity groups via `WeekBasedMaterialDemand` API or `WeekBasedCapacityGroup` API respectively.