-
Notifications
You must be signed in to change notification settings - Fork 122
DPP Industry Core
Welcome to the DPP & Industry Core Hub workshop! In this session, you will learn how to upload a DPP submodel, transfer it to the DTR, and successfully exchange DPPs with others—all within the Industry Core Hub environment. You will also use the Connector and Discovery Services to enable secure data exchange and efficient discovery of assets across the dataspace.
- Mathias Brunkow Moser Chief Software Architect, Catena-X Automotive Network e.V.
- Carlos Diez Rodriguez Dataspace Consultant, LKS Next
- Joseba Alvaro Hernandez Dataspace Consultant, LKS Next
- A laptop with browser!
- Lots of motivation!
- And a bit of patience — it is a challenge!
In this first challenge, everyone jumps in by creating a basic DPP using the wizard. Before starting, we take a quick moment to refresh what a DPP actually is, why it matters, and how it fits into the bigger picture. To access the wizard, you first need to enable the Eco Pass Kit — Provisioning feature. Once that’s done, each person goes through the wizard step by step until the DPP is completed and saved. Along the way, we chat about the usual mistakes people make and share small tips that make the process smoother. Once your DPP is created, don’t forget the final step: share it with the OEM so it can move forward in the process. The goal is simple—everyone should finish this challenge with one solid, valid DPP they created confidently and shared correctly.
Now it’s time to change perspective and also switch to the OEM account. Instead of creating data, you get to see how others consume it. You scan a QR code from someone else’s Serialized DPP and explore what shows up. It’s a good moment to understand what details become visible, how everything is structured, and what someone on the “receiving end” actually experiences. After that, you try looking up Tariff information through Discovery by entering a Manufacturer ID and pulling in data created by others. This helps make sense of how Catalog Parts, Discovery, and Tariffs connect in real life.
For anyone who’s already comfortable with the basics, there’s a final challenge. Here you take the OEM perspective and build a Catalog Part for a car. You pull in PCF coming from different component suppliers, stitch everything together, and make sure your part shows up correctly in Discovery. At the end, you share what you created so we can check how the full ecosystem flow comes together. This challenge ties all previous steps into one complete story: suppliers create data, OEMs combine it, and the final product becomes traceable and meaningful.
If you're feeling ready for a bit more, the next challenge is to extend one of your Catalog Parts by adding Tariff information through ICHUB. Once you’ve created your Catalog Part and shared it with the OEM, your next challenge is to level it up by adding a US Tariff submodel. Just open the Submodel Creator inside that same Catalog Part and start building the tariff submodel there. Make sure the information feels right and fits what you’re trying to describe. When it all looks good, save it. This step is simply about getting comfortable adding extra layers of information to a product as it moves through the process.
- Industry Core Hub
- Industry Core Hub - Submodel Creator Guide
- ICHUB1/Supplier(BPNLA3600000ICH1): https://frontend-ichub-1-txcd.arena2036-x.de/
- ICHUB2/Supplier(BPNLA3600000ICH2): https://frontend-ichub-2-txcd.arena2036-x.de/
- ICHUB3/Supplier(BPNLA3600000ICH3): https://frontend-ichub-3-txcd.arena2036-x.de/
- ICHUB4/OEM(BPNLA3600000ICH4): https://frontend-ichub-4-txcd.arena2036-x.de/
Fifth Eclipse Tractus-X Community Days
- Welcome
- Business Perspective
- Workshops / Tutorials
- Challenges / Coding
Fourth Eclipse Tractus-X Community Days
- Welcome
- Business Perspective
- Business game (Catena-X)
- Workshops / Tutorials
- Challenges / Coding
General
Working with KITs
- Automate KIT documentation update
- How to create a KIT website
- KIT Artefacts
- Understanding our multi instance and versioning behaviour
Working with the Webpage