Update DCM KIT to match Version 2.3 of the standard

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)