EU 2023/1542
The passport needs field data.
That is the part factories usually lack.
Most battery makers can produce manufacturing records, but not the in-service performance, cycling and state-of-health data the Digital Battery Passport asks for. We collect that data continuously, from day one of operation.
The gap
Two halves of the data, one is missing
The passport needs both factory-side and field-side data. The field side is where most teams get stuck.
| Data group | Typically available? | How we help |
|---|---|---|
| Material & composition | Usually yes — from your BOM | Consolidated and linked to the device record |
| Carbon footprint | Partially — factory stage only | Operational energy data added to complete the picture |
| Performance & durability | Rarely — needs in-service data | Capacity fade, internal resistance trend, cycle counting |
| State of health | Rarely — needs continuous logging | SOH history with timestamps, exportable per unit |
| Cycling & usage profile | Rarely — no telemetry channel | Charge / discharge cycles, depth, temperature profile |
| Repair & second life | Sometimes — service records | Maintenance and event log kept with the device |
What we collect
Data that maps to passport fields
- Cycle counting: cumulative charge / discharge cycles with depth distribution
- Capacity fade: actual vs. nominal capacity over time, per unit
- SOH history: timestamped series rather than a single snapshot
- Temperature profile: min / max / delta across the pack life
- Energy throughput: cumulative charge and discharge energy
- Event log: alarms, protection events and maintenance actions
Export
Structured, per unit
{
"sn": "BT24080001",
"chemistry": "LFP",
"nominal_capacity_ah": 32,
"cycles": 127,
"energy_throughput_kwh": 4128.6,
"soh_series": [
{ "date": "2026-01", "soh": 99.6 },
{ "date": "2026-06", "soh": 98.9 },
{ "date": "2026-09", "soh": 98.4 }
],
"temp_profile": { "min": -6.2, "max": 58.4 },
"events": [ ... ]
}Machine-readable output, ready to feed into your declaration workflow.
Timeline
When to start
The earlier the better — retroactive collection is not an option.
Add the telemetry channel
Module or firmware integrated at the design stage, so every unit ships with data collection enabled.
Continuous collection
Data accumulates automatically; no action needed from your team or the end user.
Export for declaration
When an EU customer asks, export the dataset for that unit in minutes instead of weeks of manual work.
Records travel with the pack
History follows the battery into reuse and recycling, supporting the full lifecycle requirement.
FAQ
Common questions
No, and we will not claim otherwise. Compliance depends on your product, your declaration and the authority's interpretation. What we provide is the operational dataset the passport requires — the part that cannot be reconstructed later.
We cover the in-service part: performance, durability, cycling, SOH and event history. Factory-side data such as material composition and manufacturing carbon footprint stays in your systems — we link to it rather than replace it.
Yes, if you choose to. Access is controlled by your account, so you decide which parties see which datasets. You can also hand over an export file instead of granting platform access.
If EU export is on your roadmap at all, yes — because the data cannot be backfilled. Units shipped today without a telemetry channel will have no history when the requirement applies to you.
By default in our cloud regions. If your customers require data residency within the EU or inside your own network, on-premise deployment and region selection are both available — discuss it during scoping.