Formally document Digital Product Pass Verification add-on in Github

[matbmoser]

Description

Document formally the architecture from the addon for the digital product pass, where aspects models can be certified and verified using the application.

Include it in dpp-verification\* folder as an separated add-on component.

Acceptance Criteria

• [ ] Have complete documentation from confluence published
• [ ] Publish it in release v24.05

[matbmoser]

I started to document here the Verification concept: https://github.com/eclipse-tractusx/digital-product-pass/tree/docs/verification/dpp-verification

I am migrating slowly the things from confluence

[matbmoser]

Points:

• Split work for each tutorial
• Split participants first from developers and business
• List all the kits we are using (logos)

[matbmoser]

To be done by trainees:

Per part (Unique per part):

• PCF (Product Carbon Footprint)
• Dimentions (Height, Lenght, Width)
• Weight (g)
• Name
• Description
• ID (uuid 4) -> urn:uuid:fd3872e7-cb59-4a50-15f3-8f2d1d0d0594 -> https://www.uuidgenerator.net/version4
• PartInstanceId (Random unique Id example: BAH-1235)
• Manufacturing date (random)
• Place on the market (random) after manufacturing date
• List of materials (random %)
• HazardMaterials: (Names) (in some of them some and some of them no)
• Garantee Data (Random) in years

Per part (shared)

• Recycling documentation URL: "https://github.com/eclipse-tractusx/digital-product-pass/dpp-tutorial/resources/recycling.pdf"
• Life cycle type: "asBuilt"
• ManufacturingPartId: HZ11343G

Parts Ideas:

• Battery (Battery Pass)
• Transmission (Transmission Pass)
• Door Front Left (Digital Product Pass)
• .etc... (Digital Product Pass)

Every part gets a word sheet

Other Tasks:

• Map parts to generate a tree (show the relationships)

[matbmoser]

Picture from the planning board: (Still a bit messy):