Updated a type in a blog entry

docs-kits/Resiliency/DCM_Kit.mdx → docs-kits/Resiliency/DCM KIT/page-adoption-view.mdx

@@ -1,8 +1,8 @@
 ---
-id: DCM Kit
-title: DCM Kit
+id: Adoption View
+title: Adoption View
 description: 'Demand and Capacity Management Kit'
-sidebar_position: 2
+sidebar_position: 1
 ---
 
 import LicenceV3 from '@site/static/icons/Icon_Licence_V3.svg'
@@ -13,6 +13,8 @@ import bannerImg from '@site/static/img/DCMKitLogoIcon-min.png'
 
 <img src={bannerImg} style={{width:"12rem"}}/>
 
+## Vision & Mission
+
 The Catena-X-Standards for Demand- and Capacity-Management enable participants of the automotive supply chain to become more resilient and to increase the degree of collaboration aimed at avoiding or solving production bottlenecks as well as surplus situations in a tactical horizon of 1-2 years.
 
 Thereby the standards empower participants to share data in a secure and sovereign way while ensuring the interoperability of the different applications involved in the process. 
@@ -24,7 +26,9 @@ Resilience has become imperative within Supply Chain Management, especially over
 
 Inside the volatile and highly complex surroundings of the automotive industry nowadays, mostly tailor-made, proprietary and often fully manual IT solutions support the demand and capacity management processes along the value chain. On the one side there is no common understanding of these processes among the participants. On the other side, different data formats as well as application programming interfaces are used, which is increasing the complexity in the data exchange and which is leading to transfer problems, inconsistencies, or even loss of data.
 
-## Why DCM KIT?
+## Business Value
+
+### Why DCM KIT?
 
 The purpose and focus of Demand and Capacity Management (DCM) KIT is twofold: 
 - Define a common understanding of the DCM process thus paving the way for more proactive and efficient collaboration.
@@ -34,37 +38,63 @@ Implementing the DCM standards will add the following core capabilities to busin
 - Provisioning and consumption of material demands data in a sovereign manner.
 - Provisioning and consumption of capacity data in a sovereign manner.
 - Discovery of bottlenecks and surplus capacity situations by employing a unified calculation logic.
+
+## Standards
 
-(Coming soon) The DCM standard comprises three main elements: 
+The DCM standard comprises three main elements: 
 - **Core Business logic** – to focus on a **common understanding** of the **DCM processes** among the participants.
-- **APIs** – to make sure that data are transmitted and consumed properly as well as are identically interpreted across companies. 
-- **Data model** – to align the structure of the shared data and enable the adoption of the core business logic without misinterpretation.
+- **APIs** – to make sure that data are transmitted and consumed properly as well as are identically interpreted across companies. Version 1.0.0 (Release 3.1) [CX-0048 DCM API Material Demand & Capacity Group]( https://catena-x.net/de/standard-library).
+- **Data model** – to align the structure of the shared data and enable the adoption of the core business logic without misinterpretation. Version 1.0.0 (Release 3.1) [CX-0047 DCM Data Model Material Demand & Capacity Group]( https://catena-x.net/de/standard-library).
 
 <!-- ![Power of standards icon](@site/static/icons/Icon_Licence_V3.svg) -->
-## <LicenceV3 width="4rem" /> POWER of STANDARD
+### <LicenceV3 width="4rem" /> Power of standard
 
 Standards create trust. Customer and Supplier can form new partnerships confidently. Knowing that integration in the network will be dramatically simplified. Standardization can help reduce costs by eliminating redundancies and streamlining processes. By adopting a common set of practices and technologies, businesses can avoid the need to develop their own proprietary systems, which can be expensive and time-consuming.
 
 <!-- ![Data Souvereignity icon](@site/static/icons/Icon_Easy_to_use_V3.svg) -->
 
-## <EasyToUseV3 width="4rem"/> DATA SOVEREIGNTY in FOCUS
+### <EasyToUseV3 width="4rem"/> Data sovereignty in focus
 
 DCM KIT keeps up with Catena X commitment to data sovereignty. This KIT has the goal to always comply with the data sovereignty principle implemented by the Eclipse Dataspace Connector. That enables all participants in the supply chain  to always stay in full control of their own data.  
 
 This is how sharing data is fun.
 
 <!-- ![Interoperability at its best icon](@site/static/icons/Icon_Open_Source_V3.svg) -->
 
-## <OpenSourceV3 width="4rem"/> INTEROPERABILITY at its BEST
+### <OpenSourceV3 width="4rem"/> Interoperability at its best
 
 Application and Service Provider can reduce investments to integrate DCM data models/API specification from DCM KIT.
 
 The Kit enables the offering of value-add services and innovation based on process description of the core business logic and how a collaborative approach is a win-win-situation for customer and supplier.
 
 <!-- ![Collaboration is key icon](@site/static/icons/Icon_Adoption_V2.svg) -->
 
-## <AdoptionV2 width="4rem"/> COLLABORATION is KEY
+### <AdoptionV2 width="4rem"/> Collaboration is key
 
 The DCM KIT enables better and faster issue resolution. We believe that collaboration is the key to creating and maintaining strong partnerships between customers and suppliers and, at the same time, enhancing problem solving to reach a more balanced and efficient supply and demand management.
 
 Of course, by realizing efficiency through improved collaboration all involved partners will gain competitive advantage over those that do not collaborate.
+
+## Semantic Models
+
+WeekBasedCapacityGroup: 
+https://github.com/eclipse-tractusx/sldt-semantic-models/tree/main/io.catenax.week_based_capacity_group
+
+WeekBasedMaterialDemand
+https://github.com/eclipse-tractusx/sldt-semantic-models/tree/main/io.catenax.week_based_material_demand
+
+## Notice
+
+This work is licensed under the CC-BY-4.0.
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023,2023 ZF Friedrichshafen AG
+- SPDX-FileCopyrightText: 2023,2023 Bayerische Motoren Werke Aktiengesellschaft (BMW AG)
+- SPDX-FileCopyrightText: 2023,2023 SAP SE
+- SPDX-FileCopyrightText: 2023,2023 Volkswagen AG
+- SPDX-FileCopyrightText: 2023,2023 Mercedes Benz Group
+- SPDX-FileCopyrightText: 2023,2023 BASF SE
+- SPDX-FileCopyrightText: 2023,2023 SupplyOn AG
+- SPDX-FileCopyrightText: 2023,2023 Henkel AG & Co.KGaA
+- SPDX-FileCopyrightText: 2023,2023 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V (Fraunhofer)
+- SPDX-FileCopyrightText: 2023,2023 Contributors to the Eclipse
+

docs-kits/Resiliency/DCM KIT/page-software-development-view.md

@@ -0,0 +1,58 @@
+---
+id: Development View
+title: Development View
+description: 'Demand and Capacity Management Kit'
+sidebar_position: 2
+---
+
+## Material Demand API
+
+The WeekBasedMaterialDemand contains the material demand information which is send from the customer to the supplier.
+All participants participating in Catena-X DCM in the role of a customer MUST be able to send the WeekBasedMaterialDemand. All participants participating in Catena-X DCM in the role of a supplier MUST be able to receive and process the WeekBasedMaterialDemand.
+
+### Precondtions and dependencies
+
+The WeekBasedMaterialDemand API MUST be published towards the network using a Data Asset/Contract Offer in terms of the Dataspace Protocol as defined by IDSA, following the Catena-X standard SOV-001. 
+
+## API specification
+
+### API Endpoints & resources
+
+To support the exchange of WeekBasedMaterialDemand data, a business application MUST define a single endpoint supporting the HTTP POST request method as described in [RFC9110]. The structure of the endpoint MAY be freely chosen. The address of the endpoint MUST be provided as part of the EDC Data Asset defined in chapter 2.2.5 of this document.
+
+### Data exchange
+
+The WeekBasedMaterialDemand data MUST be sent from the customer to the supplier using an HTTP POST request. The data format described here MUST be followed for the exchange of the material demand information.
+
+Multiple WeekBasedMaterialDemand aspects MAY be sent in one transfer as a JSON list. If only one WeekBasedMaterialDemand aspect is transmitted, it MUST still be sent as a list with one entry.
+
+The serialized JSON MUST NOT be larger than 15 MiB in size.
+
+The WeekBasedMaterialDemand endpoint MUST be implemented by all participants who wish to participate in the Catena-X DCM network as a supplier. Customers MUST be able to send material demand objects to their suppliers.
+The data payload itself MUST be a valid JSON file.
+
+All attributes marked as mandatory in the standard CX-DCM-SEM-SEMANTICMODEL MUST be included in the dataset. Attributes marked as 'Optional' MAY be included in the data set.
+
+The usage of the attributes in the data model MUST follow the attribute descriptions in the definitions in CX-DCM-PROCESS. While some attributes are technically a string, not any string is valid. For example, expectedSupplierLocations MUST be formatted as a BPNS.
+The calenderWeek MUST be set to a Monday of the week for that specific demand. The date format MUST be in accordance with ISO 70907 and MUST be in the format YYYY-MM-DD (for example 2023-02-13).
+
+The attributes ‘demandCategory’ and ‘unitOfMeasure’ MUST be set to one of the defined values as defined in the standard CX-DCM-SEMANTICMODEL.
+
+** Definition from CX-DCM-PROCESS **
+
+The customer owns and MUST publish its own demand with its supplier for the future horizon and it is highly RECOMMENDED to avoid any gaps as far as possible and to share demand data at least till month 9, to ensure DCM participants to have also sufficient demand data to work with.  
+If more demand data is available (i.e. demand related to a horizon that spans beyond month 9), the customer MAY ideally provide them until month 24. If a customer has even more demand data available (i.e. demand related to a horizon that spans beyond month 24), he MAY also provide this to his supplier. 
+The data series MAY start already from week n+2.
+Although the data series MAY start already from week n+2 and can be elaborated from a technical perspective, the DCM process have a clear focus on the tactical mid- to long-term horizon (typically considered from month 4 to 24) to enable a more resilient supply chain.
+
+In addition to the definitions from CX-DCM-PROCESS quoted above, the following rules have to be followed:
+
+The data series in the WeekBasedMaterialDemand SHOULD start already from week n+2.
+The demand for the current week (n=0) and the next week (n=1) MAY be included in the dataset. The WeekBasedMaterialDemand MUST include at least one week other than the current or the next week (meaning it may not be empty). Every week MUST NOT be included multiple times in the same WeekBasedMaterialDemand.
+
+If the demand for one of the weeks changes, the whole dataset MUST be sent to the supplier; sending the changes only (delta update / incremental update) is not possible. By this procedure, inconsistent or incomplete data sets are avoided. One data transfer MUST contain at least one WeekBasedMaterialDemand data set.
+
+For the combination of the attributes supplier, customer and materialNumberCustomer in the object WeekBasedMaterialDemand, there MUST NOT be more than one WeekBasedMaterialDemand object in existence. This means that the customer needs to collect all demands for all factories and send them aggregated as one WeekBasedMaterialDemand to the supplier.
+
+If the demand in a certain week has the value 0, it MUST be explicitly included as such in the WeekBasedMaterialDemand, meaning the week cannot be left out (as there is a difference between null and 0). Weeks with an unknown demand (value (null)) SHOULD be left out.
+

sidebarsDocsKits.js

@@ -474,7 +474,18 @@ const sidebars = {
                 id: 'Resiliency/resiliency'
             },
             items: [
-                'Resiliency/DCM Kit',
+                {
+                    type: 'category',
+                    label: 'DCM KIT',
+                    link: {
+                        type: 'doc',
+                        id: 'Resiliency/DCM KIT/Adoption View'
+                    },
+                    items: [
+                        'Resiliency/DCM KIT/Adoption View',
+                        'Resiliency/DCM KIT/Development View',
+                    ]
+                },
                 'Resiliency/maas',
                 'Resiliency/PURIS',
                 'Resiliency/mp kit',