Demand and Capacity Management KIT 24.12

[ClosedSourcerer]

Description

This PR introduces the Next Version of the Demand and Capacity Management KIT

Addressed Issues

eclipse-tractusx/sig-release#838
eclipse-tractusx/sig-release#799
eclipse-tractusx/sig-release#780
eclipse-tractusx/sig-release#773
eclipse-tractusx/sig-release#772
eclipse-tractusx/sig-release#771
eclipse-tractusx/sig-release#770
eclipse-tractusx/sig-release#769
eclipse-tractusx/sig-release#766

Added

• Added E2E Tests to Development View
• Added Glossary to Adoption View
• Added Delta Production to Adoption View
• Added Demand Volatility to Adoption View
• Added Load Factors to Adoption View
• Added Nesting to Adoption View

Changed

• Updated Core Business Process with assorted examples of capacity groups and material demands
• Updated Onboarding to include an onboarding journey

Bug Fixes

• Removed Catena-X NG reference
• Unified License Notice for DCM KIT
• Renamed DCM KIT in the sidebar and header into Demand and Capacity Management KIT in order to be consistent with the other KITs

Pre-review checks

Docusaurus builds locally all touched pages run fine locally

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files
• IP-Issue created

[stephanbcbauer]

But I think we have some bigger issues ;) Markdown linting can be solved ⇾ easy, but there are some contributors who didn't sign the ECA? That's a problem.
And for this PR we need IP Ticket because of the huge number of changes. Can you change here somehow the working model? No committer would be able to review this PR

@MWADCM @LukasSchmetz

1. As expert group lead the working model is your issue.
2. Please also initiate the IP Ticket with our designated commiter.
3. @eckardg Also contacted me regarding @lanfrans requirement for the Eclipse account and ECA. Please take care of this as well

Meanwhile i created the IP Issue

@jSchuetz88 , @ClosedSourcerer Wow this was fast -> IP Tickets was approved

[kenobi79]

LGTM

[jSchuetz88]

@jSchuetz88

• When the KIT gets released with 24.12 should the changelog.md of tractus-X (https://eclipse-tractusx.github.io/CHANGELOG/) get changed as well in order to reflect the move from /DCM-KIT/ to /Demand and Capacity Management KIT/

@ClosedSourcerer Sorry for the late reply.

Initial PR at latest: 15. November
Merged at latest: 29. November
Formal publication (creation of the new Version / Release): 2. December

[ClosedSourcerer]

The Eclipse Dash is erroneous. Afaik this is known to @stephanbcbauer

From a business perspective: We did nit add any code, therefore any code dependencies to the KIT.

@danielmiehle If I remember correctly you volunteered to act as committer for this PR.

• How do we proceed now?

[LukasSchmetz]

Corrections implemented as discussed with @ClosedSourcerer . LGTM

[stephanbcbauer]

The Eclipse Dash is erroneous. Afaik this is known to @stephanbcbauer

From a business perspective: We did nit add any code, therefore any code dependencies to the KIT.

@danielmiehle If I remember correctly you volunteered to act as committer for this PR.

• How do we proceed now?

@ClosedSourcerer in this case it's not the broken checker. There is really an issue. "Your" DEPENDECIES file is not up-to-date. There are new states "on the server" which are right now not in your DEPENDENCIES file. This is not done automatically.

left your file, right the new status of the lib

There are two options:

1. maybe someone already updated the DEPENDENCIES file on main, and you can just merge it
2. you have to update the file locally on your own and push it to your branch

[stephanbcbauer]

The Eclipse Dash is erroneous. Afaik this is known to @stephanbcbauer
From a business perspective: We did nit add any code, therefore any code dependencies to the KIT.
@danielmiehle If I remember correctly you volunteered to act as committer for this PR.

• How do we proceed now?

@ClosedSourcerer in this case it's not the broken checker. There is really an issue. "Your" DEPENDECIES file is not up-to-date. There are new states "on the server" which are right now not in your DEPENDENCIES file. This is not done automatically.

left your file, right the new status of the lib

There are two options:

1. maybe someone already updated the DEPENDENCIES file on main, and you can just merge it
2. you have to update the file locally on your own and push it to your branch

Additional information to update the DEPENDENCIES file ... here the command, needs to be executed in root folder

java -jar org.eclipse.dash.licenses-1.1.0.jar package-lock.json -project automotive.tractusx -summary ./DEPENDENCIES

https://eclipse-tractusx.github.io/docs/release/trg-7/trg-7-04#checking-libraries-using-the-eclipse-dash-license-tool

[ClosedSourcerer]

@stephanbcbauer Thank you, I already had dependencies mentally taken care off and totally forgot that between the DB being down and dash working beforehand that I might just need to merge the upstream back into downstream to get this fixed.

[stephanbcbauer]

@stephanbcbauer Thank you, I already had dependencies mentally taken care off and totally forgot that between the DB being down and dash working beforehand that I might just need to merge the upstream back into downstream to get this fixed.

i think merging helped :)

[danielmiehle]

lgtm