Skip to content

Industry Core Hub

Jump to bottom Edit New page
Carlos Diez edited this page Jul 2, 2026 · 12 revisions

Industry Core Hub — Hands-on Workshop Guide

Sixth Community Days · Eclipse Tractus-X · Industry Core Hub

A hands-on challenge to share real data across the Catena-X dataspace using the PCF and CCM use cases.

Contents

Before you start

The Challenge — if you already know the application, jump straight here:

Description

In this workshop you will work, hands-on, with the two use cases implemented in the Industry Core Hub (ICH):

  • PCF — Product Carbon Footprint: define, request, provide and consume the carbon-footprint data of your parts and their subparts.
  • CCM — Company Certificate Management: create, share, request and consume compliance certificates across the dataspace.

You do not have to deploy or install anything. The Industry Core Hub instances are already up and running — you simply open them in your browser using the links in the Links section at the bottom of this guide. In this guide, "deployment" means one of those already-hosted instances, not something you set up.

You will play both sides of every exchange — Provider and Consumer — across two of these live instances, exchanging real data through a Catena-X connector. Follow the checklists step by step. Beyond completing the flows, we ask you to report any feedback so we can keep improving the application.

Throughout the guide, each action is marked with the role that performs it:

Provider actions are done on the instance you use as provider (open its link from Links).

Consumer actions are done on the instance you use as consumer (open its link from Links).

Coaches

  • Carlos Diez Rodriguez — Dataspace Consultant, LKS Next (Spain)
  • Joseba Alvaro Hernandez — Dataspace Consultant, LKS Next (Spain)

If you get stuck at any point, ask a coach.

Prerequisites and setup

You do not need to install anything. Everything runs in your browser.

  1. A modern web browser (Chrome, Edge or Firefox).
  2. Your workshop ticket (the paper slip). It contains:
    • ID — your unique identifier, in the format XXX-[your name] (for example 001-alice).
    • Consumer — the deployment number you use when acting as consumer.
    • Provider — the deployment number you use when acting as provider.
    • Guide URL — the link to this guide.
  3. A PDF file (any PDF) to upload during the CCM challenge. If you do not have one, ask a coach.

Use your ID everywhere

All participants share the same deployments, so many people create parts and certificates at the same time. To find your own data among everyone else's, name everything you create with your ID:

  • Catalog part name: 001-alice-wheel
  • Subpart / part IDs: 001-alice-rim, 001-alice-tyre
  • Certificate name: 001-alice, then 001-alice.2, 001-alice.3, 001-alice.4 for the later CCM scenarios.

If a field accepts a name, put your ID in it. That is how you and the coaches tell your work apart from everyone else's.

How the deployments work

There are four live Industry Core Hub instances (we call them deployments), already hosted and reachable from the URLs in the Links section — you do not deploy them yourself. They are paired as follows:

  • Deployment 1 with Deployment 2
  • Deployment 3 with Deployment 4

Your ticket tells you which deployment is your Consumer and which is your Provider, always within the same pair. During the challenge you open both instances in your browser (for example, in two browser tabs, using their links from Links) and drive each exchange end to end: you provide data on your provider instance and consume it on your consumer instance. Roles vary between participants, so both deployments are exercised as provider and as consumer.

Recommended: open your Provider instance in one tab and your Consumer instance in another, and keep both open for the whole workshop.

Feedback form

Keep the feedback form open in a separate tab for the whole workshop. Use it to report, at any time:

  • Bugs — anything that does not work as expected.
  • Usability improvements — anything that felt confusing or could be smoother.
  • Questions — anything you did not understand.

Feedback form: [link to be added by the coaches]

Your input directly shapes the next iterations of the Industry Core Hub.

The application at a glance

The left sidebar groups features by KIT. For this workshop you will use:

KIT Screen Route Purpose
Industry Core Catalog Parts /catalog Create, register and share catalog (type) parts
Industry Core Dataspace Discovery /dataspace-discovery Discover parts shared by partners
Business Partner Contact List /partners Register the partners you share with
PCF PCF Precalculation /pcf/precalculation Request PCF of subparts from suppliers
PCF PCF Management /pcf/management Upload and manage PCF data for your parts
PCF PCF Requests /pcf/requests Respond to incoming PCF requests
CCM Certificate Management /certificates Create and manage your certificates
CCM CCM Provision Management /ccm-provision Respond to and send certificates (provider)
CCM CCM Consumption /ccm-consumption Request, download and review certificates (consumer)

Challenge 1 — PCF (Product Carbon Footprint)

The PCF use case has two flows:

  • SYNC — you publish PCF data directly on a catalog part and the consumer reads it after discovery.
  • ASYNC — the consumer requests the PCF of a subpart, the provider accepts the request in PCF Requests, and the consumer receives the data back.

Reminder: name every part with your ID (for example 001-alice-wheel).

How to do it, step by step. This checklist tells you what to do. The full illustrated, click-by-click walkthrough lives in the Industry Core Hub repository, under docs/user. Open the PCF KIT User Guide and follow it alongside this checklist.

Flow A — SYNC (direct sharing on a catalog part)

Provider Create, register and share the part

  1. Go to Catalog Parts (/catalog) and click Create Catalog Part.
  2. Fill in the required fields:
    • Manufacturer Part ID: for example 001-alice-wheel
    • Part Name: for example 001-alice Wheel
    • Optionally add Category, BPNS, dimensions and materials.
  3. Click Create.
  4. On the new part card, click Register part (registers the digital twin).
  5. Click Share part, select your partner (your consumer deployment's BPNL) and confirm.
  6. Open the part's View Details, go to the Submodels section and click New Submodel.
  7. Choose the PCF schema, fill it in and save. The PCF submodel is now attached to your shared part.

Consumer Discover and read the PCF

  1. Go to Dataspace Discovery (/dataspace-discovery).
  2. Select the Partner BPNL (your provider deployment) and click Start Discovery.
  3. In the results, locate the part you created (001-alice-wheel).
  4. Open it, click View Submodels and open the PCF submodel.
  5. Check: can you see the exact PCF data you created on the provider side?

Flow B — ASYNC (request, accept, receive)

Consumer Create the part and request the subpart

  1. On your consumer deployment, go to Catalog Parts and Create Catalog Part identifiable with your ID (for example 001-alice-wheel). Register it.
  2. Enable the PCF Precalculation by clicking the '+' icon, then navigating to PCF KIT → PCF Precalculation.
  3. Go to PCF Precalculation (/pcf/precalculation).
  4. Type your Manufacturer Part ID in the search field and click Calculate PCF to select the part.
  5. Click Add Subpart Relation. In the dialog enter:
    • Supplier BPN: the BPNL of your provider deployment.
    • Manufacturer Part ID: the subpart you want (for example 001-alice-rim).
  6. Click Add Subpart Relation to confirm. The subpart appears with status Pending.
  7. Click the Request PCF button on that subpart.
  8. Check: the subpart request reaches status Delivered (it may pass through sending and awaiting response first).

Provider Accept the request

  1. Enable the PCF Requests and PCF Management by clicking the '+' icon, then navigating to PCF KIT → PCF Requests, PCF Management.
  2. On your provider deployment, go to PCF Requests (/pcf/requests).
  3. Check: you have received a Pending request for the subpart the consumer defined (001-alice-rim).
  4. If you cannot accept it yet, it is because you have not published PCF data for that subpart:
    • Go to Catalog Parts and create a part named exactly like the requested subpart (001-alice-rim). Register it.
    • Go to PCF Management (/pcf/management), search that part, click Upload PCF Data and complete the Dual PCF Creation (v9.0.0 + v7.0.0) wizard (validate both versions, then Save Both PCFs).
  5. Back in PCF Requests, click Accept on the request.

Consumer Receive the data

  1. Return to PCF Precalculation. The subpart moves to status Received.
  2. Expand the subpart row to see the PCF Details (carbon footprint value, delivered date, and so on).
  3. Check: the PCF values match what you defined on the provider side.
  4. When all subparts are collected, click Download JSON to export the aggregated PCF.

Extra challenge — update and propagate

  1. Provider In PCF Management, edit the PCF of the part you provided and save. When prompted, use Notify Participants and Send PCF Update.
  2. Consumer Confirm the data has been updated on your side (the subpart shows the Updated status and the new values).

Challenge 2 — CCM (Company Certificate Management)

You will run four provisioning scenarios. Each combines:

  • How the provider delivers the certificate: AVAILABLE (consumer must pull/download the data) versus PUSH (provider sends the data directly).
  • Who starts the exchange: RESPONDING (provider responds to a consumer request) versus SENDING (provider sends proactively, with no request).

How to do it, step by step. This checklist tells you what to do. The full illustrated, click-by-click walkthrough lives in the Industry Core Hub repository, under docs/user. Open the CCM KIT User Guide and follow it alongside this checklist.

For each scenario, create the certificate with your ID as the name and the suffix indicated:

Scenario Certificate name Delivery Trigger
1 — Responding · Available 001-alice AVAILABLE Consumer requests first
2 — Responding · Push 001-alice.2 PUSH Consumer requests first
3 — Sending · Available 001-alice.3 AVAILABLE Provider sends directly
4 — Sending · Push 001-alice.4 PUSH Provider sends directly

To create a certificate: Certificate Management (/certificates) → Upload Certificate → 3-step wizard: (1) Certificate Type, Name and Issuer, (2) Valid From and other validity fields, (3) upload your PDF. Pick any certificate type you like.

Prerequisites:

  • Enable the Certificate Management by clicking the '+' icon, then navigating to CCM KIT → Certificate Management.
  • Enable the CCM Provision Management by clicking the '+' icon, then navigating to CCM KIT → CCM Provision Management.
  • Enable the CCM Consumption by clicking the '+' icon, then navigating to CCM KIT → CCM Consumption.

Scenario 1 — Responding · Available

  1. Provider In Certificate Management, click Upload Certificate and create one named 001-alice (any type, upload your PDF).
  2. Consumer Go to CCM Consumption (/ccm-consumption) and click New Request. Fill in the Provider BPN, Certified BPN and Certificate Type matching the certificate you can see on the provider side. Optionally click Verify CCM support, then Send Request.
  3. Provider Go to CCM Provision Management (/ccm-provision), open the Inbound Requests tab, find the incoming request and click Provide. Choose Make available (PULL), select the certificate and click Send Availability.
  4. Consumer In CCM Consumption, click the Pull certificate (download) icon on your request, then click again to View and open the PDF. Then send feedback: click the Send feedback icon, choose RECEIVED, ACCEPTED or REJECTED, and click Send Feedback.
  5. Provider In CCM Provision Management, open the Shares tab and check the share status and the Consumer Status feedback the consumer sent.

Scenario 2 — Responding · Push

  1. Provider Create a certificate of another type named 001-alice.2 and upload a PDF.
  2. Consumer Click New Request for that certificate (same as before).
  3. Provider In the Inbound Requests tab, click Provide, choose Push directly and click Push Certificate.
  4. Consumer You no longer need to pull first — the document arrived directly. Click the View icon to open the PDF, then send feedback (RECEIVED / ACCEPTED / REJECTED).
  5. Provider Check the Shares tab for the status and the consumer's feedback.

Scenario 3 — Sending · Available

  1. Provider Create a certificate of another type named 001-alice.3 and upload a PDF.
  2. Provider In CCM Provision Management, click Send Available, select the certificate and the Recipient (Consumer BPN), then click Send Availability — no request needed.
  3. Consumer In CCM Consumption, without sending any request, find the incoming certificate. Because it is available, pull/download it first, then View and open it. Send feedback (RECEIVED / ACCEPTED / REJECTED).
  4. Provider Check the Shares tab for status and feedback.

Scenario 4 — Sending · Push

  1. Provider Create a certificate of another type named 001-alice.4 and upload a PDF.
  2. Provider In CCM Provision Management, click Push Certificate, select the certificate and the Recipient (Consumer BPN), then click Push Certificate — no request needed.
  3. Consumer The document arrived directly (push) — no download needed. Just View and open it. Send feedback (RECEIVED / ACCEPTED / REJECTED).
  4. Provider Check the Shares tab for status and feedback.

Status reference

  • PCF subpart (PCF Precalculation): Pending → Delivered / Received → Updated (also Rejected, Error).
  • PCF request (PCF Requests): Pending → Accepted → Delivered (also Rejected, Updated, Failed).
  • CCM inbound (Provision → Inbound): Registered, Available, Pushed, NotFound.
  • CCM share (Provision → Shares): Active, Pending, Revoked.
  • CCM request (Consumption): Pending, Found, NotFound, Failed.
  • Consumer feedback (both sides): RECEIVED, ACCEPTED, REJECTED.

Links

Or scan the QR code above:

Código QR para Industry Core Hub Workshop — Feedback

Helping Resources

Add a custom footer

Six Eclipse Tractus-X Community Days

Fifth Eclipse Tractus-X Community Days

Fourth Eclipse Tractus-X Community Days

General

Working with KITs

Working with the Webpage

Clone this wiki locally