20 November 2026 · 8 min read

When your battery fleet grows, telemetry becomes a revenue dispute

European BESS asset management is moving from “keep it alive” to “prove it, settle it, repeat.”

Control desk with monitors showing conflicting battery performance traces beside an open contract.

A battery is easy to explain when it is one site and a small team. You know the electricians. You know the integrator. You can call the OEM, get a firmware tweak, and everyone nods along when you say “availability is good”.

Then you add a second site. Then a third. Then different inverter stacks, different EMS choices, different grid requirements, different dispatch counterparties. And suddenly the conversation is not about chemistry or containers. It is about proof.

That is why I liked the way Giga Storage framed the biggest shift as scale. Scale changes the job. You stop “operating a project” and start running a fleet. Fleet work is unglamorous: availability accounting, warranty evidence, dispatch discipline, data ownership, and the boring interfaces between parties who all touch the same stack but do not share incentives.

My conviction: if you do not treat revenue-grade telemetry and event evidence as a product from day one, you will pay for it twice. First in lost revenue. Then in disputes that burn months of attention and quietly poison partnerships.

Scale does not break hardware first, it breaks accountability

When people say “asset management”, many still picture a monitoring screen and a maintenance contract. That is the early stage. At fleet stage, asset management becomes a settlement function.

The simplest way to see it is this: every euro your battery earns comes with a question attached.

  • Were you available when you said you were?
  • Did you follow dispatch instructions, within constraints?
  • Was the limitation technical, contractual, or market-driven?
  • Who caused the deviation, and who pays?

At small scale you can answer those questions with informal trust. At larger scale trust becomes a rounding error. You need a shared record that survives disagreement.

That is where European complexity matters. Different markets, different grid codes, different metering arrangements, and a patchwork of service providers. The more parties you have, the more seams you have. And seams are where performance turns into argument. If you want a related lesson from a different domain, this is the same failure mode as connected products: the seams break before the sensors do.

Availability is not a feeling, it is a definition you can litigate

Most teams underestimate how quickly the word “availability” becomes contested. Not because anyone is dishonest, but because everyone measures it differently.

If you want availability to scale, make it boring and explicit:

  • Define states. Charging, discharging, idle, constrained, stopped, islanded, commissioning, test, forced outage. If your SCADA or EMS cannot label states consistently, you do not have availability, you have vibes.
  • Separate technical capability from commercial permission. A grid constraint or a market suspension is not the same as an inverter fault. Both kill revenue, but they belong to different buckets.
  • Time-align everything. Clocks drifting across meters, EMS, PPC, and OEM logs will turn every incident into a debate about what happened first.
  • Make exclusions explicit. Planned maintenance, curtailment, force majeure, commissioning windows, cyber events. Decide what counts before it happens.

Fleet availability is not a single number. It is a hierarchy: site, block, component class, root cause category. If you cannot slice it, you cannot manage it.

One practical rule: every “downtime” entry needs an owner. Not a person to blame, but a party accountable for closing the loop. Otherwise you get the deadliest sentence in this business: “We saw that too.”

Warranty evidence is a system, not a folder of PDFs

When a battery fails early, you do not win by being angry. You win by being able to prove what happened, in the format the warranty requires, inside the time window the warranty allows.

This is where asset management shifts from maintenance to forensics. The OEM wants logs. The integrator points to site conditions. The EMS vendor points to setpoints. The trader points to dispatch instructions. Everyone has partial truth.

I have watched this pattern in another high-mix technology environment: once you have enough versions in the field, the only thing that scales is disciplined evidence capture. Not heroics.

Build your warranty evidence pipeline like you would build a financial close process:

  • Event capture is automatic. Fault codes, alarms, trips, limiters, comms drops. No manual copy-paste.
  • Raw data is retained. Aggregations are helpful, but warranty fights are won in high-resolution traces and unmodified logs.
  • Chain of custody is clear. Who collected the data, where it was stored, who accessed it, and whether it was altered. If you cannot answer that, expect pushback.
  • Site context is attached. Ambient conditions, grid events, maintenance actions, firmware versions, configuration changes.

Most teams do the opposite: they build a dashboard first, then scramble for raw evidence later. Dashboards are for humans. Warranties are for contracts.

Dispatch discipline is a profit lever, but it starts as restraint

At fleet scale, a battery is not just an asset. It is a promise: to the grid, to a market, to a counterparty, sometimes to multiple at once. The fastest way to destroy that promise is to treat dispatch as “someone else’s job”.

Dispatch discipline has three parts.

1) A single source of truth for constraints

State of charge limits, temperature derates, grid export caps, maintenance windows, warranty cycling constraints. If these live in spreadsheets, you will eventually trade a capability you do not have.

2) A clear hierarchy when things conflict

When the trader wants action but the asset needs protection, who wins? If the answer changes by who shouts loudest, your performance will look random over a quarter.

3) Post-dispatch reconciliation

Every missed dispatch should produce a clean story in 24 hours: what was requested, what was delivered, what blocked it, and whether it was avoidable. That story becomes improvement work, and it becomes commercial ammunition when revenue is questioned.

This is also where data integrity stops being a technical preference and becomes a money problem. If you have ever lived through a major cloud outage, you know the real question is not “did it go down?”, it is “what kept the organisation moving while it did?” The same mindset applies to fleet operations: design for the day your primary telemetry path is unavailable. If you want that muscle in another context, the lesson carries in what keeps your organisation moving when core services go dark.

Who owns revenue-grade telemetry when everyone touches the stack?

This is the part people avoid because it feels political. It is actually just commercial hygiene.

In a typical European BESS setup, you may have:

  • an OEM supplying batteries and often a monitoring layer,
  • an integrator delivering EPC plus controls,
  • an EMS vendor optimising or dispatching,
  • a meter provider and a grid interface,
  • a trader or aggregator monetising markets,
  • an owner or asset manager responsible for outcomes.

Every one of them can produce “the truth” about performance. If you do not decide which truth is used for settlement, warranty claims, and internal reporting, you will end up with three truths and one argument.

My position is simple: the asset owner needs an independent, contract-backed right to collect and store the raw operational data required to prove performance. Not a forwarded dashboard. Not an OEM portal export when requested. A right.

That does not mean you distrust partners. It means you refuse to run a business where the evidence lives in someone else’s system, on someone else’s retention policy, accessed through someone else’s goodwill.

If you want one sentence to put into negotiations: “We need owner-access to raw telemetry, timestamped events, configuration history, and meter alignment, with retention long enough to support warranty and revenue disputes.”

And then you make it real with four clauses:

  1. Data rights. Owner can collect, store, and use required data for operations, compliance, warranty, and settlement.
  2. Data format. Specify what is delivered (schemas, sampling rates, event codes), not “reasonable access”.
  3. Retention and availability. How long raw data is kept, and what happens if a vendor platform changes.
  4. Auditability. Ability to reconstruct an incident end-to-end, across OEM and EMS layers.

This is also why I think the question “Who owns performance risk after commissioning?” matters so much in storage. If you want a deeper treatment of that boundary, it is worth reading who owns performance risk after the battery is commissioned?.

A fleet-ready checklist you can apply this quarter

If you are moving from “a few containers” to a fleet, I would not start by buying more software. I would start by forcing clarity in five places:

  • Define availability like a contract. States, exclusions, and ownership of downtime classification.
  • Build an evidence pipeline. Raw logs, event capture, chain of custody, configuration history.
  • Harden time and metering alignment. Common clock discipline, meter reconciliation, and a clear link between operational data and settlement data.
  • Put constraints into one system. Not in emails, not in meetings, not in a trader’s memory.
  • Write the data-rights clause before the next procurement. If you wait until you have a dispute, you are already late.

The unglamorous truth is that scale rewards the teams who treat boring definitions as core product work. That is how you keep revenue clean, warranties enforceable, and partnerships healthy when the fleet gets big enough that nobody can “just call the guy who knows”.

If you disagree with me on one thing, disagree on this: I do not think you can outsource accountability for evidence. You can outsource maintenance. You can outsource market access. You cannot outsource the ability to prove what happened.

Newsletter

Working notes, straight to your inbox.

Occasional, no-noise notes from inside the work: what shipped, what broke, and what I would do differently.