Over the last decade, the industry has built an impressive stack of systems to observe solar performance. Each one does its job well. None of them are broken.
But when these systems operate in isolation, they quietly create the same outcome:
More activity. More spend. Less discipline.
Let’s break it down.
1) SCADA & plant control systems
SCADA excels at real-time visibility and control. It tells you what is happening right now.
What it doesn’t tell you is whether intervening is economically justified.
It answers:
“Is something abnormal?”
It does not answer:
“Is this worth fixing now — or at all?”
2) Inverter, string, and electrical telemetry
Electrical telemetry is strong at fault detection and localization.
But at scale, signal volume explodes. Without prioritization, teams react to alerts instead of making tradeoffs.
It answers:
“Where is the fault?”
It does not answer:
“What is the financial consequence of acting vs. waiting?”
3) Environmental & performance normalization
Normalization explains variance and flags underperformance.
It answers:
“This site is underperforming relative to expectation.”
It does not answer:
“What work should this trigger — if any?”
4) Inspection & ground-truth capture
Inspections surface panel-level issues telemetry can’t see.
They answer:
“What’s wrong?”
They do not answer:
“What decision does this justify financially?”
5) Work execution & cost recording
Work systems document what was done and what was paid — after decisions are already locked in.
They answer:
“What did we spend?”
They do not answer:
“Should we have spent it?”
What operators should be doing instead
Effective solar O&M is not about adding another monitoring layer.
It’s about introducing a decision layer that sits above all of them.
A modern O&M operating model should do five things consistently:
1) Translate signals into dollars
Every alert, anomaly, or inspection finding must be converted into estimated revenue at risk — not severity labels.
If you can’t express an issue in dollars, you can’t prioritize it.
2) Compare action vs. inaction explicitly
Before work is dispatched, the system should answer:
Cost to fix now
Cost of deferring
Risk of compounding failure
If this comparison isn’t made, the decision is emotional, not operational.
3) Trigger work selectively, not reflexively
Most portfolios still run on:
fixed inspection cadences
blanket cleaning schedules
reactive dispatches
Efficient portfolios trigger work only when the economics justify it.
4) Close the loop after execution
Once work is done, outcomes should feed back into the system:
Was revenue recovered?
Was the intervention worth it?
Would we make the same call again?
Without this loop, the system never improves.
5) Optimize for fewer actions, not faster reactions
The goal is not to fix everything quickly.
The goal is to:
avoid unnecessary truck rolls
intervene earlier where it’s cheap
let low-impact issues wait
That’s how OPEX stays controlled as portfolios scale.
The real differentiator
Every operator can see problems.
The best operators know which problems are worth paying for — and which ones aren’t.
Until your systems can confidently tell you when not to act,
you don’t have O&M discipline.
You have activity.
— CC