Skip to content

Track 5: Digital Battery Passport Workshop

Jump to bottom
juileetikekar edited this page Sep 24, 2026 · 2 revisions

Track 5: Digital Battery Passport Workshop

Table of Contents

Motivation

From February 2027, the EU Battery Regulation (EU) 2023/1542 makes it mandatory: every qualifying battery needs a Digital Battery Passport - the same idea as a food nutrition label, but legally binding. It's built on the AAS, the same open standard used across Industrie 4.0, as 7 standardized submodels tied together by a DPP Metadata submodel.

A battery passes through many hands over its life - manufacturer, integrator, driver, recycler - each running independent systems. This workshop answers: who builds this record, and how does anyone downstream ever find it?

Overview

You'll build one complete Digital Battery Passport yourself, publish it to a real (fictional-data) AAS infrastructure, and then retrieve someone else's battery passport on a system you don't know the address of, using nothing but a product ID.

Two independent, fictional companies run the infrastructure for this workshop:

Provider A Provider B
Company VoltaForge Battery Systems GmbH ArcCell Energy Solutions Ltd.
Battery VF-EV82 - EV traction battery AC-IND150 - industrial energy storage

Both run their own AAS Repository.

Target Group

AAS practitioners. No battery domain knowledge is required or expected.

Prerequisites

  1. A laptop with a modern browser
  2. ADX Hub login credentials (provided by the organizers at the start of the session)

A Note on the Data

VoltaForge, ArcCell, and every document referenced from their submodels are entirely fictional, created for this workshop only. Each document states this explicitly.

Tutorial

Step 0: Get Your Starter File

  • Download your assigned file from Starter AASX Files - VoltaForge_ProviderA_battery-NN.aasx or ArcCell_ProviderB_battery-NN.aasx, where NN is your battery number
  • Open it in AAS Editor using your ADX Hub login Your file already contains all 8 submodels and every identifier (AAS id, product ID, submodel ids) pre-set and unique to your battery number. Everything is pre-filled except 5 fields, on purpose.

Step 1: Build Your Battery

Persona: You are the battery manufacturer, completing the last few fields before your Digital Battery Passport is ready to publish. Goal: Fill in exactly 5 fields. No battery domain knowledge required - any plausible value is fine.

Submodel Field VoltaForge (Provider A) ArcCell (Provider B)
Battery Nameplate serialNumber Any short ID, e.g. VF-EV82-2026-00017 Any short ID, e.g. AC-IND150-2026-00042
Technical Data batteryMass A realistic figure, ~480 kg for an 82 kWh EV pack A realistic figure, ~900 kg for a 150 kWh industrial rack
Product Condition energyCapacityChargeState.stateOfCharge Any percentage, e.g. 65% Any percentage, e.g. 70%
Carbon Footprint productCarbonFootprints[0].pcfCO2eq A plausible value in kg CO₂-eq/kWh, ~58 (NMC chemistry) A plausible value in kg CO₂-eq/kWh, ~45 (LFP chemistry tends lower)
DPP Metadata contentSpecificationIds Check all 7 boxes Check all 7 boxes

Everything else in your file is already complete.

Step 2: Validate

Before publishing, run your AAS through the Validation Service. Fix anything it flags.

  1. In AAS Editor, export your AAS as an AASX file. Use Export from the ⋮ menu next to your project.
  2. Open the Validation Service in ADX Hub and upload that AASX file.
  3. Review the results. If anything is flagged, go back to AAS Editor, fix it, re-export, and re-validate before moving on.

Step 3: Publish to Your AAS Repository

In AAS Editor, use "Upload to AAS Repository."

Not "Upload DPP to Repository." What gets stored is your battery's shell and its submodels - not a "DPP." A Digital Product Passport is assembled fresh, on demand, every time someone retrieves it.

Your file publishes to whichever provider you were assigned - VoltaForge participants to Provider A's AAS Repository, ArcCell participants to Provider B's.

Your file Provider AAS Repository
VoltaForge_ProviderA_battery-NN.aasx Provider A - VoltaForge https://provider-a.adx-hub.com/api/v3.2
ArcCell_ProviderB_battery-NN.aasx Provider B - ArcCell https://provider-b.adx-hub.com/api/v3.2

Before publishing, point AAS Editor at the correct repository:

  1. Click the ⋮ menu next to Import AAS, then select Editor Settings.
  2. Paste your assigned AAS Repository URL from the table above into the AAS Repository URL field.
  3. Leave DPP Repository URL blank - this workshop only uses "Upload to AAS Repository," not the DPP publish path.
  4. Click Save.

Step 4: Retrieve

  • Open the DPP Viewer and enter your own battery's product ID (e.g. https://provider-a.adx-hub.com/battery-07).
  • Watch your own passport come back, assembled fresh from what you just published.
  • If you're interested, exchange product IDs with another participant - anyone in the room, not necessarily someone on your provider - and look up theirs too. Notice you may not even be able to tell whether it came from Provider A or Provider B.

Two entirely separate, independently hosted systems were behind every passport in the room today. Nobody needed to know which one held the battery they were looking up. Standardized submodels are what made the result readable and trustworthy regardless of who built it.

Built once. Owned by no one system. Readable by everyone who ever needs to trust it.

Links

Home

2026

2024

Clone this wiki locally