Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[R25.03] DCM: KIT Maintenance #1140

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ description: Glossary
|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.|
|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 transmitting 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).|
|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.|
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ If you are interested in utilizing DCM within the Catena-X dataspace you can fol

#### Onboarding

Business Application Providers that want to enable their commercial software for Catena-X DCM need to register for the Catena-X Ecosystem following the specific information described in [Offering a Catena-X Solution](https://catena-x.net/en/catena-x-introduce-implement/offering-a-catena-x-solution) (including next steps & contacts).
Business Application Providers that want to enable their commercial software for Catena-X DCM need to register for the Catena-X Ecosystem following the specific information described in [Offering a Catena-X Solution](https://catena-x.net/en/catena-x-introduce-implement/offering-a-catena-x-solution) (including next steps and contacts).

Please refer to the [Catena-X Library][StandardLibrary] for the newest version of the DCM as well as other standards.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ toc_max_heading_level: 2

![DCM kit banner](@site/static/img/kits/demand-and-capacity-management/demand-and-capacity-management-kit-logo.drawio.svg)

## Vision & Mission
## Vision and 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.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ C3((" ")):1
C4("Capacity"):1
space:4
space:1
E2("Match & Comparison"):2
E2("Match and Comparison"):2
space:1
space:4
G1((" "))
Expand Down Expand Up @@ -283,7 +283,7 @@ C3((" ")):1
C4("Capacity"):1
space:4
space:1
E2("Match & Comparison"):2
E2("Match and Comparison"):2
space:1
space:4
G1((" "))
Expand Down Expand Up @@ -975,7 +975,7 @@ C3((" ")):1
C4("Capacity"):1
space:4
space:1
E2("Match & Comparison"):2
E2("Match and Comparison"):2
space:1
space:4
G1((" "))
Expand Down Expand Up @@ -1105,7 +1105,7 @@ C3((" ")):1
C4("Capacity"):1
space:4
space:1
E2("Match & Comparison"):2
E2("Match and Comparison"):2
space:1
space:4
G1((" "))
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Both customers and suppliers must be able to send and receive comments regarding

To aid in the interpretation of received comments, a comment type must be specified during its creation. Each comment must align with one of the defined types in the standard. The consumer of the comment is responsible for determining the appropriate actions in response to the comment type.

The provider of a comment can freely write their message in a designated text field, as outlined in the corresponding data model. Any editing of comments, such as changes to content, date, or time, does not alter the CommentID.
The provider of a comment can freely write their message in a designated text field, as described in the corresponding data model. Any editing of comments, such as changes to content, date, or time, does not alter the CommentID.

Additionally, comments may include references to specific calendar weeks of the time series data for clarity.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -106,17 +106,17 @@ sequenceDiagram
activate CustomerConnector
CustomerConnector ->> SupplierConnector: Resolve connector Endpoint and connector service catalogue into MaterialDemand API URL
activate SupplierConnector
SupplierConnector ->> CustomerConnector: Framework & Contract Negotiation
CustomerConnector -->> SupplierConnector: Framework & Contract Negotiation
SupplierConnector ->> CustomerConnector: Framework and Contract Negotiation
CustomerConnector -->> SupplierConnector: Framework and Contract Negotiation
SupplierConnector -->> CustomerConnector: MaterialDemand API URL
end
rect rgb(221,130,0)
note right of Customer: Exchange Material Demand
CustomerApp ->> CustomerConnector: Transmit MaterialDemand
CustomerConnector ->> SupplierConnector: Transmit MaterialDemand
SupplierConnector ->> SupplierApp: Transmit MaterialDemand
CustomerApp ->> CustomerConnector: Transfer MaterialDemand
CustomerConnector ->> SupplierConnector: Transfer MaterialDemand
SupplierConnector ->> SupplierApp: Transfer MaterialDemand
activate SupplierApp
SupplierApp ->> Supplier: Transmit MaterialDemand
SupplierApp ->> Supplier: Transfer MaterialDemand
Supplier -->> SupplierApp: MaterialDemand received
SupplierApp -->> SupplierConnector: MaterialDemand received
deactivate SupplierApp
Expand Down Expand Up @@ -151,20 +151,20 @@ sequenceDiagram
CoreEdcDiscovery -->> SupplierApp: connector URL catalogue
deactivate CoreEdcDiscovery
SupplierApp ->> SupplierApp: Find correct connector via URL catalogue inspection
SupplierApp ->> SupplierConnector: Transmit CapacityGroup
SupplierApp ->> SupplierConnector: Transfer CapacityGroup
activate SupplierConnector
SupplierConnector ->> CustomerConnector: Resolve connector Endpoint and connector service catalogue into CapacityGroup API URL
activate CustomerConnector
CustomerConnector ->> SupplierConnector: Framework & Contract Negotiation
SupplierConnector -->> CustomerConnector: Framework & Contract Negotiation
CustomerConnector ->> SupplierConnector: Framework and Contract Negotiation
SupplierConnector -->> CustomerConnector: Framework and Contract Negotiation
CustomerConnector -->> SupplierConnector: CapacityGroup API Endpoint
end
rect rgb(128,149,0)
note left of Supplier: Exchange Capacity Group
SupplierConnector ->> CustomerConnector: Transmit CapacityGroup
CustomerConnector ->> CustomerApp: Transmit CapacityGroup
SupplierConnector ->> CustomerConnector: Transfer CapacityGroup
CustomerConnector ->> CustomerApp: Transfer CapacityGroup
activate CustomerApp
CustomerApp ->> Customer: Transmit CapacityGroup
CustomerApp ->> Customer: Transfer CapacityGroup
Customer -->> CustomerApp: CapacityGroup received
CustomerApp -->> CustomerConnector: CapacityGroup received
deactivate CustomerApp
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ All notable changes to this Kit will be documented in this file.
- Added multiple diagrams to [Development View](./development-view/overview.md)
- Added APIs to [Development View](./development-view/overview.md)
- Added Use Case to [Adoption View](./adoption-view/overview.md)
- Added Q&A to [Adoption View](./adoption-view/overview.md)
- Added QnA to [Adoption View](./adoption-view/overview.md)

### Changed

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -118,20 +118,20 @@ Feature: Customer: Prepare yourself

Examples:
| object | function | test |
| MD_alpha | A WeekBasedMaterialDemand created by the customer and transmitted via Filetransfer Alpha | Create WeekBasedMaterialDemand for base journey, Provide WeekBasedMaterialDemand for base journey |
| MD_beta | A WeekBasedMaterialDemand created by the customer and transmitted via Filetransfer Alpha | Create WeekBasedMaterialDemand for base journey, Provide WeekBasedMaterialDemand for base journey, Calculation for base journey |
| MD_gamma | A WeekBasedMaterialDemand created by the customer and transmitted via Filetransfer Alpha and Theta | Create WeekBasedMaterialDemand for base journey, Provide WeekBasedMaterialDemand for base journey, Calculation for base journey, Consume IdBasedRequestForUpdate for base journey |
| MD_delta | A WeekBasedMaterialDemand created by the customer and transmitted via Filetransfer Beta | Create WeekBasedMaterialDemand for base journey, Provide WeekBasedMaterialDemand for base journey |
| CG_alpha | A WeekBasedCapacityGroup created by the supplier and transmitted via Filetransfer Gamma and Eta | Consume WeekBasedCapacityGroup for base journey, Provide IdBasedRequestForUpdate for base journey |
| CG_beta | A WeekBasedCapacityGroup created by the supplier and transmitted via Filetransfer Gamma | Consume WeekBasedCapacityGroup for base journey, Calculation for base journey |
| CG_gamma | A WeekBasedCapacityGroup created by the supplier and transmitted via Filetransfer Delta | Consume WeekBasedCapacityGroup for base journey |
| CG_delta | A WeekBasedCapacityGroup created by the supplier and transmitted via Filetransfer Delta | Consume WeekBasedCapacityGroup for base journey |
| RU_alpha | An IdBasedRequestForUpdate created by the customer and transmitted via Filetransfer Epsilon | Create IdBasedRequestForUpdate for base journey, Provide IdBasedRequestForUpdate for base journey |
| RU_beta | An IdBasedRequestForUpdate created by the supplier and transmitted via Filetransfer Zeta | Consume IdBasedRequestForUpdate for base journey |
| CT_alpha | An IdBasedComment created by the customer and transmitted via Filetransfer Iota | Create IdBasedComment for base journey, Provide IdBasedComment for base journey |
| CT_beta | An IdBasedComment created by the customer and transmitted via Filetransfer Iota | Create IdBasedComment for base journey, Provide IdBasedComment for base journey |
| CT_gamma | An IdBasedComment created by the supplier and transmitted via Filetransfer Kappa | Consume IdBasedComment for base journey |
| CT_delta | An IdBasedComment created by the supplier and transmitted via Filetransfer Kappa | Consume IdBasedComment for base journey |
| MD_alpha | A WeekBasedMaterialDemand created by the customer and transferred via Filetransfer Alpha | Create WeekBasedMaterialDemand for base journey, Provide WeekBasedMaterialDemand for base journey |
| MD_beta | A WeekBasedMaterialDemand created by the customer and transferred via Filetransfer Alpha | Create WeekBasedMaterialDemand for base journey, Provide WeekBasedMaterialDemand for base journey, Calculation for base journey |
| MD_gamma | A WeekBasedMaterialDemand created by the customer and transferred via Filetransfer Alpha and Theta | Create WeekBasedMaterialDemand for base journey, Provide WeekBasedMaterialDemand for base journey, Calculation for base journey, Consume IdBasedRequestForUpdate for base journey |
| MD_delta | A WeekBasedMaterialDemand created by the customer and transferred via Filetransfer Beta | Create WeekBasedMaterialDemand for base journey, Provide WeekBasedMaterialDemand for base journey |
| CG_alpha | A WeekBasedCapacityGroup created by the supplier and transferred via Filetransfer Gamma and Eta | Consume WeekBasedCapacityGroup for base journey, Provide IdBasedRequestForUpdate for base journey |
| CG_beta | A WeekBasedCapacityGroup created by the supplier and transferred via Filetransfer Gamma | Consume WeekBasedCapacityGroup for base journey, Calculation for base journey |
| CG_gamma | A WeekBasedCapacityGroup created by the supplier and transferred via Filetransfer Delta | Consume WeekBasedCapacityGroup for base journey |
| CG_delta | A WeekBasedCapacityGroup created by the supplier and transferred via Filetransfer Delta | Consume WeekBasedCapacityGroup for base journey |
| RU_alpha | An IdBasedRequestForUpdate created by the customer and transferred via Filetransfer Epsilon | Create IdBasedRequestForUpdate for base journey, Provide IdBasedRequestForUpdate for base journey |
| RU_beta | An IdBasedRequestForUpdate created by the supplier and transferred via Filetransfer Zeta | Consume IdBasedRequestForUpdate for base journey |
| CT_alpha | An IdBasedComment created by the customer and transferred via Filetransfer Iota | Create IdBasedComment for base journey, Provide IdBasedComment for base journey |
| CT_beta | An IdBasedComment created by the customer and transferred via Filetransfer Iota | Create IdBasedComment for base journey, Provide IdBasedComment for base journey |
| CT_gamma | An IdBasedComment created by the supplier and transferred via Filetransfer Kappa | Consume IdBasedComment for base journey |
| CT_delta | An IdBasedComment created by the supplier and transferred via Filetransfer Kappa | Consume IdBasedComment for base journey |
| FT_alpha | A Filetransfer providing WeekBasedMaterialDemand for the supplier to consume | Provide WeekBasedMaterialDemand for base journey |
| FT_beta | A Filetransfer providing WeekBasedMaterialDemand for the supplier to consume | Provide WeekBasedMaterialDemand for base journey |
| FT_gamma | A Filetransfer providing WeekBasedCapacityGroup for the customer to consume | Consume WeekBasedCapacityGroup for base journey |
Expand Down
Loading