The Conversation I Kept Having at the Battery Asset Management Summit

I attended the Battery Asset Management Summit (BAMS) in Orange County, CA, expecting to spend two days talking about data-driven BESS operations. Instead, I had the same conversation four separate times. It happened on the expo floor, in the hallway after a session on BESS KPIs, and at a happy hour with someone I’d just met — all with people from different companies, with portfolios ranging from a few hundred MWh to several GWh.

Each conversation started on different topics but led to the same issue. It goes like this.

A project reaches COD. The completion certificate gets signed, the commissioning crew demobilizes, and the performance management team is now responsible for a site that nobody on the operations side has ever seen the inside of. Months later there’s a container running warm, cells drifting out of balance within a module, auxiliary loads tanking net RTE, or an availability number missing its guarantee.

Here’s what came up each time: most of those problems would have been visible on the day the plant energized. The container that fails in year two was often already running a degree or two above its neighbors during acceptance testing. The data that would have shown it was overwritten in a buffer long ago, but nobody was looking at it then.

So, the operator is left arguing a warranty claim they can’t substantiate. To claim against the OEM, you have to prove the deficiency wasn’t caused by your dispatch actions — depth of cycling, C-rate, SOC dwell, thermal exposure. Successful claims require high-frequency cell-level data from the commissioning period forward. What most operators have is one-minute averaged SCADA points from a site controller.  Often, the SCADA vendor doesn’t even configure the necessary tags.

Two things about this struck me.

First, nobody described this as a data problem. Rather they described it as a warranty problem, an availability problem, a staffing problem. The data gap was the cause, but it was never the headline.

Second, it’s a timing problem more than anything. Before the completion certificate is signed, a finding is a punch list item your EPC and your OEM to resolve while you’re still holding retainage. Four months later, the identical finding is a claim you have to litigate from a weak position. Same finding. Completely different outcome. And the independent baseline you’d need to win that argument can only be established once, during commissioning, or never.

There’s a catch-22 budget issue underneath it as well. The tooling that could circumvent this outcome is a rounding error inside a capex budget and a hard ask against an operating budget. Which means the window where it’s easiest to approve occurs before the window where everyone realizes the need.  By the time everyone does, it’s an operating line item nobody budgeted for.

There’s nothing complicated about the solution. You install full-resolution instrumentation before energization instead of after, and you make sure it comes from a party with no stake in the performance numbers it’s producing. It’s one of the smaller line items in the whole value chain, and it ends up deciding who pays for the next three years of problems.

Every one of those conversations ended the same way. Nobody needed the mechanics explained to them, they just needed to have caught it before the certificate was signed.

If you were at BAMS, I’d be curious whether this matches what you heard. And if you’ve energized a project in the last eighteen months — did your operations team get a data baseline, or a PDF?