Core Business Process
TABLE OF CONTENTS
- Business Roles and Functions
- Material Demand
- Capacity Group
- Match and Comparison of Demand and Capacity
- Collaboration
- User Journey
Business Roles and Functions
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 |
User Journey
Figure: Basic DCM user journey
Personas
The basic DCM user journey encompasses two key personas, each with distinct roles and responsibilities that highlight their value within the supply chain.
Customer
Individuals that act as this persona may hold various titles within their organization, but share the common responsibility of managing material demand and ensuring that supply aligns with their forecasted needs. The value of DCM for the customer lies in the capability to provide clear visibility into future demand and to facilitate efficient communication and alignment with suppliers.
The responsibilities of the customer include:
- safeguarding sufficient capacity of his suppliers for required materials and prevent bottleneck situations
- allocation of production capacity on customer side
- production rough cut planning
- material allocation
Supplier
Individuals that act as this persona may hold various titles within their organization, but share the common responsibility of providing capacity data in response to the customer's material demand. The value of DCM for the supplier lies in the capability to receive material demand data, which enables them to plan and allocate resources effectively, ensuring they can meet the customer's demands.
The responsibilities of the supplier include:
- allocation of production capacity
- production rough cut planning
- material allocation
- communication to a customer business partner regarding capacity figures in a mid to - long term horizon
- resolving bottleneck situations
User Journey Description
The starting point within the DCM user journey is the exchange of demand data, which is provided by the customer and consumed by the supplier as WeekBasedMaterialDemand. For an effective demand and capacity management the data needs to be of a certain quality. This includes sorting the demand into weekly buckets, extending the demand data 24 months into the future and subsequently keeping it up to data. Whether the customer has to manually prepare the demand data or it gets automatically generated and updated from existing systems, is not restricted by the Catena-X standards.
The exchange of demand data is followed by the exchange of capacity data, which is provided by the supplier und consumed by the customer. For an effective demand and capacity management the data needs to be of a certain quality. This included linking material demands to the capacity group ,providing a capacity quantity for every calendar week the customer provided demand quantities for, matching unit of measures correctly and utilizing advanced features like load factors and delta production in order to model demand and capacity management as closely to real life as possible. Whether the supplier has to manually prepare the capacity data or it gets automatically generated and updated from existing systems, is not restricted by the Catena-X standards. However matching material numbers and linking material demands to capacity groups will most likely required human intervention at some point.
After exchanging demand and capacity data both customer and supplier do have the same view of the current situation and can begin matching and comparing the data. This is something that usually happening locally within the respective DCM application. Ideally the whole process of finding problems (bottleneck or surplus) is automated.
If either customer or supplier identify a problem they can collaborate by exchanging comments as described by the DCM standard or by communicating outside the Catena-X dataspace using email or online-meetings. Regardless of how communication is initiated and maintained solving an identified problem is always the result of proposing, evaluating and simulating potential solutions. Customers and supplier discuss potential measures, modify their demand and capacity respectively and exchange the modified data until a solution that works for both sides has been found.
Tools available to the customer for solving problems are fairly limited. They can increase or decrease demand quantities.
The supplier on the other hand has more options to solve problems. They can not only increase and decrease capacity quantities, but also use flexible capacity, load factors and delta production.
Material Demand
A material demand represents the need for a particular product, part, component or material over a certain time period in a specified quantity. Demand quantities must refer to a time period of one calendar week (weekly buckets).
The customer is responsible for publishing material demands to their supplier for upcoming time periods and it is strongly recommended to:
- Minimize any data gaps to the greatest extent possible by maintaining continuity and establishing consistency.
- Provide material demand data for at least nine months into the future to ensure that DCM participants have sufficient information to work with.
- Implement a rolling demand plan by continuously updating the planning horizon with recent data.
- Refresh the data at a minimum of once every four weeks.
- Align, ideally within a contract, the unit of measure for demand quantities (e.g., pieces, kilograms, metric tons) with the supplier before providing the demand.
The supplier must have the capability to consume the material demand data from the customer.
Material Demand Structure
Figure: Material demand structure
Visualization Example
Figure: Visualizing demand quantities as bars
Capacity Group
A capacity groups represents the answer to one ore more material demands. It contains the information on how a supplier intends to fulfill customer needs, by contrasting demands with capacities over a certain time period in a specified quantity. Capacity quantities must refer to a time period of one calendar week (weekly buckets).
The customer is responsible for publishing capacity groups to their customer and it is strongly recommended to:
- Minimize any data gaps to the greatest extent possible by maintaining continuity and establishing consistency.
- Provide capacity data for every calendar week that has associated demand data.
- 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 customer must have the capability to consume the capacity group data from the supplier.
Capacity Group Structure
The Capacity Group is the entity where Material Demand and capacity information are matched and compared for the purpose of a collaborative DCM. Thereby, the Capacity Group builds the common view on the data exchanged between a customer and a supplier.
The entity Capacity Group may be used, i.e. to combine capacities related to one or more machines, facilities or plants.
Figure: Capacity group structure
Example Visualization
Figure: Visualizing capacity quantities as lines
Capacity Types
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.
In addition the difference between actual capacity and maximum capacity is commonly understood as flexible capacity.
WeekBasedCapacityGroup Properties
A Capacity Group dataset comprises the following basic components:
Properties | Description |
---|---|
Supplier | The Business Partner Number (BPNL) of the party providing materials to a customer |
Customer | The Business Partner Number (BPNL) of the party requesting material from a supplier |
Capacity Group ID | The Capacity Group ID uniquely identifies the capacity group within the business relationship between a supplier and its customer |
Changed At | 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 | Name of the capacity group. |
Inactive Flag | Indicates that this capacity group is currently not in use/maintained by the supplier |
Unit of Measure | Unit of Measurement (UoM) for capacity quantities |
Linked Demand Series | Set of demand series assigned tio this capacity group. |
Capacities | A time series with week-based granularity along a given time period containing the capacity values |
Unit of Measure is Omitted | 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.
Properties | Description |
---|---|
Actual Capacity | 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 | 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 | 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 supplier maximum capacity minus actual capacity |
Point in Time | ISO Calendar Week of the given time series entry. UstIt must be given as a date of the Monday in the week. |
Linking Capacity Groups to Material Demands
For a functional Capacity Group, the supplier must link it directly or indirectly to a Material Demand:
- Direct linking means that the Capacity Group links at least one Material Demand
- Indirect linking means that the Capacity Group links to another Capacity Group which links at least one Material Demand. This is also referred to as nesting.
Direct Linking
Figure: Capacity group structure with linked material demand
For the technical representation of a CapacityGroup the aspect model WeekBasedCapacityGroup is utilized.
The aspect model WeekBasedCapacityGroup must be used by a supplier to provide capacity information to the customer.
For further details refer to the semantic model in Chapter 3.2 and to the APIs in Chapter 4.2.
A partner acting as a supplier sends a Capacity Group to its customer. In order to link demand series in the Capacity Group between customer and supplier, the following properties must be filled-in:
- supplier
- customer
- materialNumberCustomer
- customerLocation
- demandCategory
If there’s no complete match between supplier and customer data, it’s recommended to initiate collaboration (i.e. see chapter “Comments”)
The supplier has the option to mark a WeekBasedCapacityGroup as inactive (i.e. the capacity is obsolete), in this case the capacity will not be considered in the demand-capacity matching. However, the WeekBasedCapacityGroup can be reactivated again.
Building n-tier chains via capacity groups
Building supply chain via capacity groups is crucial to improve resiliency, transparency and efficiency along the value chain. Using the individual one-to-one capacity groups between one-ups and one-downs step by step builds the whole supply network. This enables all partners to collaborate along the whole value chain and navigate through complex and dynamic market conditions.
The following figure illustrates how plastic granulate ends up being used in the housing of a control unit and how this would be viewed from a birds eye perspective.
Figure: A small supply chain built by three capacity groups
The following figure illustrates the flow of demand and capacity data through the supply network. Capacity and demand blocks are placed according to responsibility. Data exchange that is happening within the Catena-X dataspace is denoted by arrows with "Provide" written on them.
Figure: A small supply network built by seven capacity groups
Match and Comparison of Demand and Capacity
Both customer and supplier need to apply the same logic when comparing demand and capacity data in order to get the same results and come to identical conclusions.
The standard describes exactly which scenario leads to the three possible matching results:
- Zero deviation
- Surplus
- Bottleneck
Within a DCM application those three matching results are commonly represented as a traffic light status, with zero deviation and surplus being green and bottleneck being orange or red, depending on whether demand is higher than maximum capacity or just actual capacity.
While customers might not feel impacted by a surplus, because the demand is matched, it still represents capacity that the supplier could better utilize.
For ease of use demand and capacity data should be shown on the same graph and colored in appropriately, within a DCM application.
Figure: Visualizing the comparison of demand and capacity quantities
Collaboration
Collaboration is key within the DCM process. It is the final part of the DCM user journey, where actual solutions for problems (surplus and bottlenecks) are proposed, discussed and finally deployed.
In order to facilitate collaboration with the Catena-X dataspace the DCM standards describes the exchange of comments, using an own aspect model and API. Communication features outside the Catena-X dataspace, such as eMail, phone calls, online meetings, etc. are not prohibited and should be used as the individual customers and suppliers see fit.
For further details, please refer to CX-0128 Demand and Capacity Management Data Exchange.
Notice
This work is licensed under the CC-BY-4.0
- SPDX-License-Identifier: CC-BY-4.0
- SPDX-FileCopyrightText: 2023,2024 ZF Friedrichshafen AG
- SPDX-FileCopyrightText: 2023,2024 Bayerische Motoren Werke Aktiengesellschaft (BMW AG)
- SPDX-FileCopyrightText: 2023,2024 SAP SE
- SPDX-FileCopyrightText: 2023,2024 Volkswagen AG
- SPDX-FileCopyrightText: 2023,2024 Mercedes Benz Group AG
- SPDX-FileCopyrightText: 2023,2024 BASF SE
- SPDX-FileCopyrightText: 2023,2024 SupplyOn AG
- SPDX-FileCopyrightText: 2023,2024 Henkel AG & Co.KGaA
- SPDX-FileCopyrightText: 2023,2024 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V (Fraunhofer)
- SPDX-FileCopyrightText: 2023,2024 Contributors to the Eclipse Foundation