Battery Passport vs Battery Management System

Engineering teams frequently ask whether the battery management system already satisfies the passport obligation, on the reasonable grounds that it holds more battery data than anything else in the company. It does not, and understanding why prevents an integration designed around the wrong assumption.

What each system is actually for

Almost every row differs, and the two that matter most are lifetime and audience. A BMS stops producing data when the battery stops operating, which is exactly the moment a recycler needs the record. And a BMS is designed for a machine that trusts it completely, whereas a passport is read by parties who must be able to verify what it says.

Where the two genuinely overlap

State of health is the overlap, and it is a real one. The regulation requires the passport to reflect the battery’s condition, and the only system that knows the condition is the BMS.

The overlap is narrow, though. The BMS computes state of health continuously from cell voltages, temperatures, impedance and cycle history. The passport needs a periodic, attributable summary of that computation — not the inputs to it.

What the integration should actually look like

The sampling policy is the design decision worth arguing about. Too frequent and the passport becomes a telemetry archive; too infrequent and a second-life buyer cannot see the degradation curve that decides residual value. Quarterly, plus an event on any significant intervention, is a defensible starting point.

Why the BMS cannot be the passport

• It stops at end of life, when recyclers and repurposers most need the record.
• It is proprietary, and the passport must be readable by parties with no relationship to you.
• It holds no composition, recycled content, due diligence or dismantling data at all.
• It offers no role-scoped access, so it cannot separate public fields from restricted ones.
• Its data cannot be independently verified, whereas passport claims are signed by their author.

The last point is the deepest. A BMS value is trusted because the system trusts itself. A passport claim is trusted because it carries a signature from the party that asserted it, which a regulator can check without trusting the platform holding it — the mechanism described in verifiable credentials explained.

Why the passport cannot be the BMS

The reverse confusion is rarer but does occur, usually in procurement conversations where a passport platform is asked to take on monitoring. It should not.

A passport updates on material change and is optimised for long-lived retrievability by external readers. A control system needs millisecond latency and safety certification. Nothing about a compliance record’s architecture suits real-time control, and combining them produces a system that is poor at both jobs and certified for neither.

Who owns each system inside the company?

The organisational split is usually the real obstacle rather than the technical one. A battery management system belongs to engineering, is specified alongside the cell and is judged on safety and range. A passport belongs to compliance or sustainability, is specified by a regulation, and is judged on whether an authority accepts it.

Those two functions frequently have no shared roadmap, and the integration between their systems is nobody’s objective. Programmes that stall at the state of health field almost always stall here rather than at any technical boundary — the data exists, the interface is straightforward, and no one owns making the request.

• Name a single owner for the state of health interface before designing it.
• Agree the sampling policy jointly, because it is both an engineering and a disclosure decision.
• Decide who signs the resulting claim, since a passport figure carries an asserting party.
• Settle retention early: the passport outlives the fleet platform that produced the data.

The retention point catches people. Fleet telemetry platforms are replaced every few years. A passport must still resolve after two such replacements, which means the summarised values have to live in the passport record rather than being fetched from whatever system currently holds the telemetry.

How the boundary changes at second life

When a pack is repurposed, the original BMS may be replaced entirely, and the vehicle platform that held its history is gone. The passport is the only artefact that survives the transition, which is what makes the earlier sampling decisions consequential rather than academic.

Preparation for repurposing also creates a fresh passport obligation on the operator performing it, as covered in battery second life and the passport. That operator inherits whatever history the original passport recorded and nothing else, so a passport that carried a single overwritten state of health value leaves them pricing an unknown asset.

What this means for procurement

If a vendor tells you their BMS platform delivers battery passport compliance, the question to ask is which of the nine data categories it holds. Most hold one. The remaining eight come from cell producers, cathode suppliers, refiners and your own pack assembly records, and no telemetry platform has access to any of them.