Digital Battery Passport

🚧Evolving Knowledge Base

The RBTP Knowledge Base is evolving weekly as part of our pilot programs with RBA members. We’d love your input — submit feedback or help shape the protocol in real time by joining a pilot.

Digital Battery Passport (DBP): Implementation Guide

If you're looking for an Overview, go to Digital Battery Passport Overview

The Digital Battery Passports (DBP) is a commodity-specific extension of the UNTP Digital Product Passport. It is designed to meet the unique traceability, compliance, and circularity needs of battery passports.

Before implementing a DBP, implementers should become familiar with the core UNTP DPP specification, which defines the base structure, vocabulary, and requirements shared by all passport types in the RBTP ecosystem

📦 DBP Profile Information

Name	Current Version	Status	Release Date	UNTP dependency
Digital Battery Passport	0.1.0	Draft	10-04-2025	UNTP DPP v0.5.0

🔧 What Makes the DBP Unique?

While a DRP reuses the full UNTP DPP model, it introduces an additional specification layer with structures and rules tailored to batteries. These include:

A new BatterySpecifications extension block (for capacity, voltage, energyDensity, etc.)
A new BatteryCertifications extension block (for battery production certifications and warantyPeriods)
Stricter field requirements for product IDs, classification schemes, and traceability references
Encouragement to use linked passports wherever applicable

The DBP is modular—not every battery product requires every field—but validators and Conformity Assessment Bodies (CABs) may enforce stricter conformance depending on your pilot or compliance target.

📐 Logical Model

A visual overview of the DBP profile and extensions is available here:

📎 Logical Model: Digital Battery Passport

Core structure: identical to the UNTP DPP with these additions:

BatterySpecifications (new object block)
BatteryCertifications (new object block)

DBP Logical Model

📏 Profile Rules

Note: This section outlines constraints and required patterns that make a valid DBP

TBD

Note: This section defines strict dependencies and requirements for product information. For instance, the ID field may be required to originate from a designated register, product.productCategory must conform to recognized international coding schemes, Claim.assessmentCriteria must be selected from predefined controlled vocabularies, etc.

Field	Requirements
`id`	Must be a globally resolvable URI (preferably `did:web` or GS1 identifier)
`product.productCategory`	Must conform to a recognized product classification system (e.g., UN CPC, HS, or industry standard)
`conformityClaim.assessmentCriteria`	Must reference RBTP-approved controlled vocabularies
`traceabilityInformation.traceabilityEvent[].linkType`	Must be drawn from the UNTP vocabulary
`BatterySpecifications`	Required for all batteries
`BatteryCertifications`	Must list the battery production certifications
`producedAtFacility`	Should reference a resolvable and verifiable identifier (e.g., GS1 GLN, cadastral boundary ID)

A JSON Schema validator will be made available in a future stable release.

🛠 Technical Artifacts

These artifacts are in development. Once published, they will include:

JSON-LD @context for DBP extension fields
JSON Schema validator for DBP conformance
Controlled vocabularies and code lists (repairability, safety topics, classification)
Sample DBP instances (e.g., alcaline battery, AAA battery, car battery, etc.)

📝 Status: Draft format available internally via Notion; will be moved to RBTP GitHub once stable.

📄 Working Sample

Clickable Link	Scan the QR	Comments
Digital Battery Passport		This is a sample DBP, work in progress. Click on the JSON tab to see the underlying RBTP data. Download the signed credential to test verification in your own system.