From 8e29890ec8a889273d166aecd67db430348a0ed6 Mon Sep 17 00:00:00 2001 From: tobzahn <147095229+tobzahn@users.noreply.github.com> Date: Thu, 18 Dec 2025 11:58:11 +0100 Subject: [PATCH 01/10] Update DCM KIT to match Version 2.3 of the standard In version 2.3 of the DCM standard, the agreed capacity has been defined more clearly. Also, new features for BPNS handling have been included. This update to the KIT incorporates those changes. --- .../use-case/business-process.md | 20 ++++++++++++++++++- 1 file changed, 19 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..03fea3ede31c 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 @@ -654,7 +654,7 @@ Further properties are added at lower level below the “Capacities” property. | 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.| +| 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. Could be used to document a capacity agreed to by both parties, e.g. in a contract. | | 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.| @@ -1031,6 +1031,24 @@ In order to facilitate collaboration with the Catena-X dataspace the DCM standar For further details, please refer to [CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary]. +## Colaboration in multi-company scenarios +There are situations where multiple companies are involved in the DCM process. This section gives an overview of some potential cases/situations 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 are 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 are 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). + ## Notice This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode) From 9dfeecc6b3c3d78ec3a110e1b9a79e074602be9c Mon Sep 17 00:00:00 2001 From: tobzahn <147095229+tobzahn@users.noreply.github.com> Date: Tue, 3 Mar 2026 08:14:48 +0100 Subject: [PATCH 02/10] Accepted Copilot typo fix Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .../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 03fea3ede31c..8da25113e79f 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 @@ -1047,7 +1047,7 @@ There are situations where multiple companies are involved in the DCM process. T **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). ## Notice From b701ad918aa338854490fafa2568db9cf44c9722 Mon Sep 17 00:00:00 2001 From: tobzahn <147095229+tobzahn@users.noreply.github.com> Date: Tue, 3 Mar 2026 08:15:27 +0100 Subject: [PATCH 03/10] Blank line removed As suggested by Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .../adoption-view/use-case/business-process.md | 1 - 1 file changed, 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 8da25113e79f..c96c93308d84 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 @@ -1042,7 +1042,6 @@ There are situations where multiple companies are involved in the DCM process. T **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 are 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 are 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. From ef773b23a75a8934f9848ca65308cfa08bfaadaa Mon Sep 17 00:00:00 2001 From: tobzahn <147095229+tobzahn@users.noreply.github.com> Date: Tue, 3 Mar 2026 08:15:45 +0100 Subject: [PATCH 04/10] Blank line removed As suggested by Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .../adoption-view/use-case/business-process.md | 1 - 1 file changed, 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 c96c93308d84..f9d7c5d4596c 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 @@ -1043,7 +1043,6 @@ There are situations where multiple companies are involved in the DCM process. T - If the part 1 are 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 are 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). From d930e4d554af018527b5646565a6b7e9def4e2db Mon Sep 17 00:00:00 2001 From: tobzahn <147095229+tobzahn@users.noreply.github.com> Date: Tue, 3 Mar 2026 08:16:22 +0100 Subject: [PATCH 05/10] Removed whitespace at EOL As suggested by Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .../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 f9d7c5d4596c..4af4498e3c28 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 @@ -1032,7 +1032,7 @@ In order to facilitate collaboration with the Catena-X dataspace the DCM standar For further details, please refer to [CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary]. ## Colaboration in multi-company scenarios -There are situations where multiple companies are involved in the DCM process. This section gives an overview of some potential cases/situations and how to handle them. +There are situations where multiple companies are involved in the DCM process. This section gives an overview of some potential cases/situations 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. From 1bb5ae4ead2174bfce534644b54728e541d845e4 Mon Sep 17 00:00:00 2001 From: tobzahn <147095229+tobzahn@users.noreply.github.com> Date: Tue, 3 Mar 2026 08:16:47 +0100 Subject: [PATCH 06/10] Accepted Copilot typo fix Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .../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 4af4498e3c28..dc82c4e498ed 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 @@ -1031,7 +1031,7 @@ In order to facilitate collaboration with the Catena-X dataspace the DCM standar For further details, please refer to [CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary]. -## Colaboration in multi-company scenarios +## Collaboration in multi-company scenarios There are situations where multiple companies are involved in the DCM process. This section gives an overview of some potential cases/situations 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 From dd38902c8d135b00dff2c79f9835da6eefb9721f Mon Sep 17 00:00:00 2001 From: tobzahn <147095229+tobzahn@users.noreply.github.com> Date: Tue, 3 Mar 2026 08:20:24 +0100 Subject: [PATCH 07/10] Accepted Copilot rephrasing Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .../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 dc82c4e498ed..da6fd1505036 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 @@ -1036,7 +1036,7 @@ There are situations where multiple companies are involved in the DCM process. T **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. +- Following the Catena-X DCM process, supplier A creates demands and sends them to supplier B who replies with the corresponding 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. From a75868fe92eaee2320f7d228279b448c8512fbb6 Mon Sep 17 00:00:00 2001 From: tobzahn <147095229+tobzahn@users.noreply.github.com> Date: Tue, 3 Mar 2026 08:21:54 +0100 Subject: [PATCH 08/10] Accepted Copilot rephrasing Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .../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 da6fd1505036..be23c89ba298 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 @@ -1040,8 +1040,8 @@ There are situations where multiple companies are involved in the DCM process. T - 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 are 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 are 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. +- If 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 supplier A. +- In case 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 the demands and sends them 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. From 40b147c92eaea5f3ecd7b83de4c6d5f65b8053bb Mon Sep 17 00:00:00 2001 From: Stephan Bauer Date: Tue, 3 Mar 2026 18:13:29 +0100 Subject: [PATCH 09/10] Refactor business process documentation for improved readability and formatting --- .../use-case/business-process.md | 89 ++++++++++--------- 1 file changed, 46 insertions(+), 43 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 be23c89ba298..2e3087904fe7 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 @@ -20,22 +20,22 @@ sidebar_position: 1 The core DCM business process is executed by two roles and uses two APIs as well as two aspect models. The customer is responsible for `WeekBasedMaterialDemand`, the supplier for `WeekBasedCapacityGroup`. Within `WeekBasedCapacityGroup` the supplier has to link material demands. -|Function / Role|Customer|Supplier| -|-|-|-| -|Manage demand data|X|| -|Inform supplier about demand|X|| -|Manage capacity data||X| -|Link demand and capacity||X| -|Inform customer about capacity||X| -|Compare demand to capacity|X|X| -|Collaborate to resolve bottlenecks|X|X| +| Function / Role | Customer | Supplier | +|------------------------------------|----------|----------| +| Manage demand data | X | | +| Inform supplier about demand | X | | +| Manage capacity data | | X | +| Link demand and capacity | | X | +| Inform customer about capacity | | X | +| Compare demand to capacity | X | X | +| Collaborate to resolve bottlenecks | X | X | ## User Journey ```mermaid journey title Basic DCM User Journey - section Exchange demand + section Exchange demand Manage demand:3: Customer Provide demand data:3: Customer Consume demand data:3: Supplier @@ -213,7 +213,7 @@ Figure: *Material demand structure* titlePadding: 10 titleFontSize: 20 showTitle: true - plotReservedSpacePercent: 50 + plotReservedSpacePercent: 50 themeVariables: xyChart: backgroundColor: "#000000" @@ -231,7 +231,7 @@ Figure: *Material demand structure* --- xychart-beta title "Example: Demand Data" - x-axis [Week 1, Week 2, Week 3, Week 4, Week 5, Week 6, Week 7, Week 8] + x-axis [Week 1, Week 2, Week 3, Week 4, Week 5, Week 6, Week 7, Week 8] y-axis 0 --> 6000 bar [3000, 3000, 3000, 3000, 4000, 4000, 4000, 5000] ``` @@ -298,7 +298,7 @@ The customer is responsible for publishing capacity groups to their customer and - Refresh the data at a minimum of once every four weeks. - Align, ideally within a contract, the unit of measure for capacity quantities (e.g., pieces, kilograms, metric tons) with the Customer and utilize lead factors as conversion factors, if applicable. -The supplier must provide capacity data to the customer, corresponding to the material demand data previously shared. Thereby, the supplier is acting as a data provider and the customer as a data consumer of the exchanged capacity group.  +The supplier must provide capacity data to the customer, corresponding to the material demand data previously shared. Thereby, the supplier is acting as a data provider and the customer as a data consumer of the exchanged capacity group.  The customer must have the capability to consume the capacity group data from the supplier. @@ -356,7 +356,7 @@ Figure: *Capacity group structure* titlePadding: 10 titleFontSize: 20 showTitle: true - plotReservedSpacePercent: 50 + plotReservedSpacePercent: 50 themeVariables: xyChart: backgroundColor: "#000000" @@ -427,7 +427,7 @@ config: yAxisTickColor: "#F4F2F3" yAxisLineColor: "#F4F2F3" plotColorPalette: "#FFA600,#d91e18,#809500,#ffffff,#00ffff" ---- +--- xychart-beta title "Example 1" x-axis [Week14, Week15, Week16, Week17, Week18, Week19, Week20, Week21, Week22, Week23] @@ -489,7 +489,7 @@ config: yAxisTickColor: "#F4F2F3" yAxisLineColor: "#F4F2F3" plotColorPalette: "#FFA600,#d91e18,#809500,#ffffff,#00ffff" ---- +--- xychart-beta title "Example 2" x-axis [Week14, Week15, Week16, Week17, Week18, Week19, Week20, Week21, Week22, Week23] @@ -535,7 +535,7 @@ config: yAxisTickColor: "#F4F2F3" yAxisLineColor: "#F4F2F3" plotColorPalette: "#FFA600,#d91e18,#809500,#ffffff,#046b99" ---- +--- xychart-beta title "Example 3: Capacity Group with little Flexible Capacity" x-axis [Week14, Week15, Week16, Week17, Week18, Week19, Week20, Week21, Week22, Week23] @@ -577,7 +577,7 @@ config: yAxisTickColor: "#F4F2F3" yAxisLineColor: "#F4F2F3" plotColorPalette: "#FFA600,#d91e18,#809500,#ffffff,#00ffff" ---- +--- xychart-beta title "Example 4a" x-axis [Week14, Week15, Week16, Week17, Week18, Week19, Week20, Week21, Week22, Week23] @@ -618,7 +618,7 @@ config: yAxisTickColor: "#F4F2F3" yAxisLineColor: "#F4F2F3" plotColorPalette: "#FFA600,#d91e18,#809500,#ffffff,#00ffff" ---- +--- xychart-beta title "Example 4b" x-axis [Week14, Week15, Week16, Week17, Week18, Week19, Week20, Week21, Week22, Week23] @@ -636,27 +636,27 @@ Figure: *Visualizing capacity and demand* 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 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| +| 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 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 | 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. Could be used to document a capacity agreed to by both parties, e.g. in a contract. | -| 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.| +| 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. Could be used to document a capacity agreed to by both parties, e.g. in a contract. | +| 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 @@ -1032,20 +1032,23 @@ In order to facilitate collaboration with the Catena-X dataspace the DCM standar For further details, please refer to [CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary]. ## Collaboration in multi-company scenarios + There are situations where multiple companies are involved in the DCM process. This section gives an overview of some potential cases/situations 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 corresponding capacity information. +**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 corresponding 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 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 supplier A. +**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 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 supplier A. - In case 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 the demands and sends them 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). +**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). ## Notice From ab015a4dd2e6c2ae3ff96acbb374c55988e66c87 Mon Sep 17 00:00:00 2001 From: Stephan Bauer Date: Tue, 3 Mar 2026 18:16:41 +0100 Subject: [PATCH 10/10] Fix formatting issue in business process documentation --- .../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 2e3087904fe7..724238080553 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 @@ -298,7 +298,7 @@ The customer is responsible for publishing capacity groups to their customer and - Refresh the data at a minimum of once every four weeks. - Align, ideally within a contract, the unit of measure for capacity quantities (e.g., pieces, kilograms, metric tons) with the Customer and utilize lead factors as conversion factors, if applicable. -The supplier must provide capacity data to the customer, corresponding to the material demand data previously shared. Thereby, the supplier is acting as a data provider and the customer as a data consumer of the exchanged capacity group.  +The supplier must provide capacity data to the customer, corresponding to the material demand data previously shared. Thereby, the supplier is acting as a data provider and the customer as a data consumer of the exchanged capacity group. The customer must have the capability to consume the capacity group data from the supplier.