The test environment supports stakeholders in validating Battery Passport implementations. The platform combines data validation with practical testing, enabling compliance and interoperability requirements to be checked early and reliably.
Partners with a central role in concept development and implementation.
Organizations that support the project with their expertise.
Certain batteries are about to get a digital ID: a data set that follows it through its entire life, from manufacturing to recycling. It records what the battery is made of, where its raw materials come from, how large its carbon footprint is and what condition it is in – machine-readable and available through standardised interfaces. It becomes mandatory under Regulation (EU) 2023/1542 for traction batteries, batteries for light means of transport and industrial batteries above 2 kWh, once they are placed on the EU market from 18 February 2027 onward.
BatteryPass Ready is a research project: it makes the implementation of the digital battery passport practically testable. It is run by TU Berlin, Fraunhofer IPK, acatech and GEFEG, supported by bitkom, ZIV, VDA and VDMA.
The test environment checks your battery passport data against the official data model and tests your implementation's lifecycle API with predefined test cases, automated, logged and free to use.
Short answers to the questions we are asked most often about the battery passport and this test environment — with a pointer to the regulation wherever it applies.
A research project. It is run by TU Berlin, Fraunhofer IPK, acatech and GEFEG, supported by bitkom, ZIV, VDA and VDMA. The BatteryPass Ready test environment is what comes out of it technically: provided by GEFEG mbH and free to use.
Very complex requirements, some still unclearly defined and often still changing, currently make implementing a formally correct product passport system in the EU a major challenge. The project aims to help here: it supports the actors involved with guidance and this test environment on the way to a correct implementation.
Two things. Data validation checks a passport JSON file for completeness against the battery passport schema files created in the project by acatech. System testing checks a running DPP system's implementation through the lifecycle API and a test adapter, for functions, consistency and interoperability.
In four steps: configure (role, lifecycle API endpoint, test adapter endpoint), pick a test case (for example BringProductPassportToMarket), start the run, review the result. The environment compares expected against actual responses and logs every step. You can find more detailed information in the usage documentation.
On 18 February 2027. From that date on, every traction battery, every battery for light means of transport and every industrial battery above 2 kWh needs a digital battery passport under Regulation (EU) 2023/1542 as soon as it is placed on the EU market.
Four categories: traction batteries for electric vehicles, batteries for light means of transport, other industrial batteries above 2 kWh and stationary industrial batteries above 2 kWh. The test environment provides matching validation schemas for these categories.
The CEN/CENELEC JTC 24 family of standards, EN 18216 to EN 18223. EN 18222 describes the lifecycle API operations, among them ReadDPPById, CreateDPP and UpdateDPPById. The test cases in this environment follow those operations.
Nothing. Data validation and system tests require a user account, but no licence fees and no usage fees are charged for them.
No. The test environment is a beta release from a research project: it supports development and experimentation, but it cannot guarantee that a system passing its checks is fully compliant. The results are indicative feedback, not a certification.
The digital product passport (DPP) is the general framework from the Ecodesign Regulation (EU) 2024/1781. The battery passport is the first product-specific passport to become mandatory. It is defined in Regulation (EU) 2023/1542 and applies ahead of all other product groups.
The environment is built for Early Access iteration: test continuously, share feedback, and improve your DPP implementation against upcoming requirements.
Use this form for inquiries and initial contact. We will gladly get back to you.