NOTES
Three systems, one truth
A renewable-energy asset does not have one record of performance. It usually has at least three.
SCADA records what the asset did. The contract defines what counterparties promised, what exceptions apply and who carries the consequence when performance moves. The financial model translates those assumptions into revenue, cash flow, covenants and value.
Each can be correct on its own while the portfolio-level conclusion is wrong.
An availability report can show 97.2%. A contract can guarantee 98%. The model can continue to assume the original operating case. If nobody compares them at the same time, the gap exists without becoming a decision.
That is the reconciliation problem.
Operating evidence, contractual obligations and financial assumptions are usually managed by different teams on different schedules.
Asset management reviews production, outages, curtailment and availability. Commercial teams work through warranties, performance guarantees, notice periods and claim mechanics. Finance closes the ledger, reconciles settlements and prepares lender or investor reporting. The model may be updated quarterly, annually or only when a transaction forces the issue.
The result is not necessarily bad data. It is disconnected data.
A shortfall can appear in SCADA before it reaches a formal report. The contract consequence may depend on exclusions, thresholds or notice requirements that sit in a document nobody is reading alongside the operating record. The model may continue to carry an assumption that was reasonable at acquisition but is no longer supported by realised performance.
Three systems. Three owners. Three schedules. Reconciled once a quarter — if at all.
Consider an asset that records 97.2% availability against a contractual guarantee of 98%.
The difference is 0.8 percentage points. Small enough to disappear inside a monthly pack. Large enough to matter if it persists, affects a liquidated-damages calculation, changes expected generation or sits inside a notice window.
The operating number alone does not answer the commercial question.
The team needs to know what caused the shortfall, whether the event qualifies for an exclusion, which measurement period applies, whether notice has been given, what remedy is available and how the result changes forecast cash flow. That requires SCADA, the contract and the model to be read together.
Without that connection, value can be lost in ordinary ways: a claim is not raised, an exception is accepted without evidence, a forecast is left unchanged, or a buyer discovers the gap during diligence before the seller has explained it.
The numbers did not move. Nobody was watching them together.
The answer is not another dashboard beside the existing systems.
It is a traceable operating record that connects the asset event to the relevant contract term and carries the consequence into the financial view.
For each material variance, that record should answer:
- What happened at the asset?
- Which source record supports it?
- What does the contract require or permit?
- Which exclusions, thresholds and notice periods apply?
- What is the expected financial consequence?
- Has the model and ledger absorbed that consequence?
- What decision is required, by whom and by when?
The value comes from keeping those answers current. A team should not need to rebuild the chain from raw data every time a board pack, lender report, warranty claim or transaction begins.
In routine reporting, one connected record changes the conversation from variance description to decision.
Instead of reporting that availability fell below budget, the team can show the source event, the contractual treatment, the revenue effect and the action already underway. Finance can see why the number moved. Asset management can see whether a commercial deadline is approaching. Investors can trace the conclusion without asking for another reconciliation.
The reporting pack becomes the output of an operating process rather than a quarter-end reconstruction.
In contract management, the same record protects optionality.
Performance guarantees, liquidated damages, defect obligations and warranty rights often depend on precise definitions and deadlines. A right can exist in the contract and still disappear operationally if the relevant event is not identified, evidenced and notified in time.
Continuous comparison makes the contract active. It links measured performance to the clause that governs it and flags the next required step before the window closes.
This does not automate judgment out of the process. It gives the team a complete record on which to exercise judgment.
During a sale or acquisition, disconnected records become a diligence burden.
A buyer receives operating reports, contracts, settlement files and a financial model, then spends weeks testing whether they describe the same asset. Any unexplained gap becomes a request, a qualification or a price discussion.
A continuous, traceable record shortens that path. Sellers can support the earnings case with evidence that links physical performance to contract treatment and realised value. Buyers can see where assumptions have held, where they have moved and which risks remain open.
One quarter unchecked can become a renegotiation. A connected record makes the issue visible before the data room does.
Brian is the operating layer for renewable-energy portfolios — agents that read your contracts, your ledger and your assets, and write back.
For asset performance, that means comparing what the asset did with what the contract promised and what the model assumed, continuously.
The result is one traceable commercial story across operations, contracts and finance.
Nothing missed. Nothing lost. Value gained.
Three systems, one truth. Time spent deciding, not reconciling.