Is metered data always better than modelled data?

Not always. Modelled data is the right tool at the design and feasibility stage, before a system exists. Metered data is what replaces projections with actual records once a system is live. A clear evidence trail uses both honestly, making plain which figures are projected and which are recorded.

Does metered data make a sustainability claim audit-ready?

Not by itself. Metered generation data proves what a system produced. Turning that into a carbon claim requires the right organisational boundary, an appropriate emissions factor and a consistent accounting method — the GHG Protocol's Scope 2 guidance sets out what is needed — and different reporting frameworks vary in what they accept. What metered data gives you is a solid, attributable starting point rather than an estimate.

Is inverter monitoring the same as metered data?

Not quite. Inverter-reported figures are useful for day-to-day operational visibility, but they are not automatically equivalent to a properly commissioned meter at a defined boundary. Where a figure has to stand up to scrutiny, what the meter measures and where it sits both matter.

Does lower-than-expected generation mean the system is underperforming?

Not necessarily. Output is legitimately affected by irradiance, system downtime, shading changes, export curtailment on a constrained connection, and normal panel degradation. A shortfall against the original model is a reason to investigate, not proof of a fault — which is why the comparison has to be adjusted for the conditions the system actually experienced.

Does metered generation data prove a financial saving?

Not on its own. Generation tells you what the system produced. A savings figure also depends on import, export, how much of the generation was used on site, your actual tariff, and a sensible view of what you would otherwise have paid.

When should metered data be in place?

From commissioning. If monitoring is specified as part of the system from the outset, metered data accumulates from day one. If it is added later, the period before monitoring started relies on modelled figures — which is worth being honest about in any report.

All articles

Energy data30 July 20264 min read

Metered vs modelled energy data: what is the difference and why does it matter?

Metered data is a record of what a system actually generated. Modelled data is a projection of what it was designed to do. The difference matters the moment someone asks for evidence rather than a headline number.

Metered energy data is a recorded figure from an installed system — what it actually generated at a specific site, during a specific period. Modelled energy data is a projected figure from a system's design specification, calculated before installation based on expected conditions. The difference matters when someone asks a harder question than the headline number, and those questions are coming from more directions than they used to.

What is metered energy data?

Metered data comes from the metering and monitoring connected to a live system, recording what it produced, when, and at which site. What a figure actually represents depends on where the meter sits: generation, import and export meters answer different questions, and a metered figure is only as good as its boundary, its configuration and the completeness of the record.

It is worth separating the two halves of that. Inverter-reported figures are valuable for day-to-day operational visibility, but where a number has to stand up to scrutiny, what matters is a properly commissioned meter at a defined boundary. Because Nuvolt designs, installs and monitors the systems it delivers, that data starts recording from commissioning — not added after the fact.

What is modelled energy data?

Modelled data is the projected output from a system's design specification, typically calculated during the feasibility or design phase before installation. It is a projection of what the system was designed to do under expected conditions, not a record of what it did.

That does not make it redundant once the system is live. Modelling is what lets you weather-normalise a comparison, forecast future output, and spot a fault — because a fault only shows up as a gap between what the system should have produced in the conditions it actually experienced, and what it did.

The two together

Neither figure means much in isolation. A meter tells you the system produced 412 MWh last year; it cannot tell you whether that is good. The model tells you what it should have produced; it cannot tell you what happened. Set them side by side, adjusted for the conditions the system actually experienced, and you get the answer that matters: is this investment doing what it was designed to do?

Which is also why a shortfall against the model is not automatically a fault. Several things move output legitimately:

Irradiance. A dull year produces less. Comparing one year's kWh to the next without normalising for weather is not a performance comparison.
Availability and downtime. Time when the system was off — inverter faults, grid outages, planned maintenance — has to be accounted for, not averaged in silently.
Shading changes. A tree grows, a neighbouring unit gets an extension. The site changed; the original model did not.
Curtailment. On a constrained connection, output can be limited deliberately. That is a network condition, not a system fault.
Degradation. Panels lose a small, predictable amount of output each year. Year 8 should not be measured against year 1.

A gap between the two numbers is a reason to look, not a verdict. What matters is that you can run the comparison at all.

Why does the difference matter for reporting?

A procurement team asking for evidence behind a supplier's sustainability claims, a lender attaching conditions to how progress is demonstrated, or a board member asking what is behind the number on the slide — all of them are asking for a record, not a projection. Reporting frameworks, financing conditions, and procurement questionnaires increasingly ask which of the two a figure is. The businesses that handle follow-up questions with confidence are usually the ones who can point to metered figures, not just modelled ones.

What does a strong evidence trail look like in practice?

Well-kept operational data does not automatically make a claim audit-ready — no single dataset satisfies every reporting framework. What it does is make the underlying evidence easier to produce and easier to defend. That means a recorded generation figure tied to a specific site and period, rather than an estimate reconstructed after the fact. A baseline to measure against. And the ability to answer a follow-up question without a spreadsheet assembled the week the request arrived.

It is worth being precise about what that record does and does not settle on its own. Measured kWh is an input to a carbon claim, not the claim itself — reporting under the GHG Protocol's Scope 2 guidance also needs the right organisational boundary, an appropriate emissions factor and a consistent accounting method. The meter contributes one number to that calculation; it does not complete it.

Where does the gap usually show up?

The gap tends to appear when monitoring was added as an afterthought — once someone realised there was no visibility — rather than specified as part of the system from the outset. Closing that gap retrospectively is a harder job than avoiding it. If your organisation is starting to face more detailed questions about its energy or carbon performance and you are not confident how easily you could answer them, that is worth looking at before the pressure is on.