The Hidden Costs of Getting Solar + BESS Wrong

What every PV operator needs to know before adding battery storage to their portfolio

Most operators manage BESS the way they manage PV. And that's quietly costing them money.

In a recent webinar hosted by PV Magazine, TWAICE engineers Jonas Soellner and Chris Pickett laid out why the jump from PV to PV+BESS is much harder than it looks and identified four hidden cost traps that show up again and again in hybrid portfolios.

Key Takeaways

1. BESS generates 10x more data than PV, but the most critical number — State of Charge — is always an estimate, never a direct measurement.

2. Undersizing inverters to cut CAPEX creates hidden performance losses that compound silently over the life of the asset.

3. There is no PVSyst for BESS. Static models locked at financial close can't keep up with a system that changes every five minutes.

4. LTSAs guarantee availability, not speed of resolution. When a fault is disputed, the burden of proof falls on the operator.

5. Root causes in BESS live layers below what standard telemetry reveals. Cross-system analytics across BMS, PCS, and HVAC is the only way to find them.

You can watch the entire webinar here.

The PV Playbook Doesn't Transfer to BESS

If you've spent years managing solar assets, you've built up a reliable toolkit. Performance models, loss diagrams, annual reviews: the methods are well-established and, for the most part, they work.

The challenge is that none of those transfers cleanly to battery storage.

A typical PV plant generates somewhere between 2,000 and 4,000 AC data points. A BESS generates over 50,000 DC data points. That number can push into the hundreds of thousands when you're tracking at the cell level. More data isn't just a technical nuance: it changes what's possible, what's required, and what happens when you get it wrong.

But the large volume of data isn't even the hardest part. The hardest part is that the most critical metric in any BESS, State of Charge, is never directly measured. It's always an estimate. The sensors give you voltage, current, and temperature. Everything else is inference.

This matters because operators who treat BESS like a solar asset are making decisions based on a number that, by definition, contains uncertainty. The instincts built up over years of PV work — trust the meter, model it at financial close, review it once a year — can actively mislead you when applied to batteries.

BESS performance assurance is not a single performance engineer running occasional reports. It's a fundamentally different operational model.

The 4 Hidden Costs

1. Value Engineering: The CAPEX Trap

When projects go through value engineering to hit a budget, power conversion systems (PCS) and inverters are often the first line items to get squeezed. It seems like a sensible tradeoff: slightly smaller hardware, meaningfully lower upfront cost.

What gets missed is what happens at runtime. Size an inverter at nameplate capacity, and it will derate under load. Size it with appropriate headroom, and it operates cleanly across its full range. The difference on paper might look like 5% lower efficiency. But in practice, once thermal derating, clipping, and degradation compound, real-world output losses can reach 20%. And that gap compounds over the 20-year life of an asset, especially when environmental factors like temperature swings, humidity, and salt exposure accelerate degradation in inverters, PCS units, and DC-DC converters. Yet these variables are frequently skipped at the design stage — treated as edge cases rather than routine stressors. By the time the effects show up in performance data, the opportunity to address them at low cost has long passed.

The hidden cost: Upfront hardware savings come at the cost of a system that quietly underperforms for its entire life. Without solid baseline data, there's no way to prove the design was the problem.

2. Static Modeling: Flying Without Instruments

In PV, the standard approach is to build your performance model at financial close and let it run. The variables (e.g., irradiance, temperature, equipment specs) are stable enough that a well-constructed model stays valid for years. Lock it in and check back annually.

BESS doesn't work that way. Battery performance changes every five minutes. State of charge, temperature gradients, cycle history, degradation state, all of it is dynamic, and all of it affects how the system performs against expectations. There is no PVSyst equivalent for BESS.

The result is that most operators are relying on static loss diagrams locked at a point in time, reviewing performance periodically and reactively. That works for PV, but a BESS has already changed by the time the next review comes around. Issues that could have been caught and corrected early become entrenched performance losses instead.

A problem caught this week is a performance correction. The same problem caught next year is accelerated degradation and a harder conversation with investors.

The hidden cost: A static model locked at financial close won't catch a BESS degrading faster than expected. By the time the annual review flags it, months of reduced output have already gone unrecovered.

3. Maintenance Delays: The Burden of Proof Problem

In PV, inverter downtime is the most common driver of unplanned revenue loss. The same pattern is now emerging in BESS.

Long-term service agreements (LTSAs) typically guarantee power output and system availability. What they don't guarantee is how quickly a fault gets diagnosed, how definitively it gets fixed, or how fast the service team responds. When something goes wrong and the cause is disputed (i.e., is this a warranty issue, or an operational issue?), the burden of proof almost always falls on the operator.

That means building the case. Pulling historical data. Correlating events. Demonstrating that the system was operated within spec. For operators without comprehensive analytics infrastructure, this process can take weeks. Every one of those weeks is lost revenue, plus the internal cost of the investigation itself.

Operators with continuous warranty KPI tracking are in a fundamentally different position. When a fault happens, the documentation is already there. The claim becomes an export, not an investigation.

The hidden cost: Without continuous data, proving a fault is a warranty issue takes weeks of digging, while the asset keeps losing revenue the whole time.

4. Trusting Basic Telemetry: The Signal You're Not Reading

A real-world example from one of our customers: A battery rack was running hot. The AC-level data flagged it as a thermal anomaly, which, naturally, pointed toward a battery problem. The team started investigating the cells. After some time, they found the actual cause: a clogged HVAC filter.

The signal was in the data the whole time. But identifying it required cross-system analytics: reading across the BMS, the PCS, and the HVAC simultaneously, with rack-to-rack baselines that made the anomaly visible in context. Without that layer of analysis, the right diagnosis was invisible. With it, the issue was caught before it became a shutdown.

This is the gap between basic telemetry and real analytics. AC-level data tells you what happened at the system boundary. It doesn't tell you why, and it doesn't tell you where. Root causes in BESS typically live two or three layers below what top-level monitoring reveals. Operators relying on standard dashboards are systematically missing the actual story.

The hidden cost: Standard monitoring shows a symptom. It rarely shows the cause. Reading only top-level data means solving the wrong problem.

Moving from Reactive to Proactive

The shift from PV to PV+BESS operations isn't just a technical upgrade. It's a change in operating philosophy. The PV playbook — measure what you can, model what you can't, review annually — needs to give way to something faster, more continuous, and more cross-functional.

The good news is that the data is there. The question is whether you have the analytics to correlate across systems and the baseline data to measure drift against.

Curious to see how BESS analytics can help out? Watch our product demo!

‍