CoreVecta AtlasPractical knowledge
Yield & performance · the audit

Performance ratio from measured yield

Every solar estimate leans on an assumed performance ratio, and assumptions age badly on roofs. This lesson turns the logic around: given what your system actually delivered over a year, it recovers the performance ratio you really achieved. That single measured number is the health check for an existing installation — the difference between “it seems fine” and “it is measurably doing what was promised”.

Verified engine journey 9 min lesson 13 guided sections Performance ratio definition
On this page13 sections
01

How a metered year becomes a verdict on the whole installation

The performance ratio is the standard yardstick of PV system health — the quantity monitoring practice, IEC 61724-style, is built around. It compares delivered energy against a reference: what the same nameplate would have yielded from the same sun if conversion were perfect. Because that reference already contains the site’s solar resource, the ratio measures the SYSTEM, not the weather — a cloudy region and a desert can both host an installation that scores well.

Within this cluster it is the closing of a loop. The sizing page divided by an assumed ratio; the yield page multiplied by the same assumption; this page derives the real one from a meter reading, using algebra the estimate would recognise — the same product of nameplate, sun hours and days, now sitting under the measured energy instead of beside an assumed factor. Setting the derived value beside the assumed one is the single most informative comparison a system owner can make.

What the ratio cannot do is say WHY. Elevated cell temperature, soiling, a string down for a month, inverter losses, creeping degradation and plain shading all pull it down through the same arithmetic, so a disappointing value is a flag, not a diagnosis. Its job is to say “look closer” cheaply and defensibly; the pack’s derate calculators — temperature, shading, soiling — are where the looking happens.

Because the sun is divided out, the ratio travels. Systems of different sizes, on different roofs, in different countries can be ranked on it directly, which raw kilowatt-hours cannot do at all and even specific yield — energy per installed kilowatt — can only do within one region’s resource. That portability is why fleet operators track it as the first-order health metric across a portfolio.

02

Concepts to hold first

01
Measured yield

The energy your installation actually delivered, read from the system’s own meter or monitoring over a full year. It is a fact about your roof, not a projection — the only input in this journey that nobody can dispute.

02
Measured performance ratio

The fraction of the theoretically available energy your installation really converted, recovered from the measured yield. Where lesson two’s ratio was a modelling choice, this one is an observation.

03
Reference yield

What the array would have delivered under the site’s sun with no losses at all — the denominator the measurement is judged against. It comes from the same peak sun figure the estimates used, which is why an honest sun figure matters twice.

04
A full year

The minimum honest measurement window. A summer of readings flatters the system; a winter slanders it. Twelve months lets the seasons cancel, so the ratio describes the installation rather than the weather it was measured in.

03

Reading a year of meter data

The measurement itself is unglamorous: one number from the system’s generation meter twelve months ago, one number today, and their difference. Monitoring apps will offer the same total with more ceremony. What matters is that the window is genuinely a year, that the meter is the system’s own rather than the household import meter, and that nothing in between — an inverter replacement, weeks of scaffolding shade — went unrecorded.

The recovered ratio is only as honest as the sun figure it is judged against. Use the same site peak-sun-hours value the original estimate used, not a value tuned until the answer looks respectable. The point of the measurement is to audit the assumption, and an audit that adjusts the evidence is a testimonial.

One measured year also sets a baseline that makes every future year cheap to judge: measure again next year and the comparison is ratio against ratio, with the site’s geography already cancelled out of both sides.

Assumed ratio flows into the estimate; measured yield flows back into the measured ratio, closing the loop

The audit loop: the assumption produced an estimate; the measurement produces a ratio that judges the assumption.

Illustrative
assumed ratioestimated yieldmeasured yieldmeasured ratio
Rebuild this with the live engine
04

When the ratio accuses the wrong suspect

A disappointing measured ratio does not say what failed — it says that something did. Before blaming the hardware, interrogate the inputs: a measurement window that quietly excluded a strong month, a sun figure from the wrong side of a mountain range, a capacity figure that still includes the string that was never installed. Input errors are cheaper to find than inverter faults, and more common.

When the inputs survive interrogation, the ratio becomes a genuine diagnostic. A ratio that sagged gradually over years suggests soiling or degradation; one that stepped down suddenly points at a failed string or a curtailing inverter; one that was never respectable from the first year suggests the installation never matched its design — shading the survey missed, or an orientation compromise nobody re-modelled.

A suspiciously excellent ratio deserves the same scepticism in reverse. Ratios beyond the plausible band usually mean the reference sun figure is understated or the meter is counting something it should not. The calculator’s guards refuse the physically impossible; the merely implausible remains yours to question.

05

How the method works

1

The measured annual yield is divided by the energy the array would have delivered under the site’s sun with no losses — the installed capacity extended across the year’s peak sun hours.

2

The quotient is the measured performance ratio: the fraction of the theoretically available energy the installation actually converted, everything included, nothing itemised.

3

The certified engine performs this calculation and refuses inputs outside the physically credible range. This page explains the reasoning and reproduces none of it.

06

Try the worked scenario

The engine below arrives pre-filled with the journey’s reference system — the pack’s own worked example, whose measured year matches what the yield lesson estimated. Substitute your own metered year and capacity, keep the sun figure honest, and the ratio that appears is your installation’s real report card.

Performance ratio from measured yieldVerified engine · signed pack
Ready

Calculator

The calculator runs on the same signed pack and certified engine as the CoreVecta apps. It is fetched and verified when you need it, so this page stays light until then.

Nothing is computed in this page. Every figure comes back from the verified engine, or the calculator refuses.

Open this scenario in the full calculator

Read the result against the band the sizing lesson called realistic: comfortably inside it, your system is healthy; below it, something specific is wrong and worth finding; above it, check the inputs before celebrating. Every figure is computed live by the verified engine.

07

What each input represents

01
Measured annual yield

The energy the system actually exported over a FULL year, from the generation meter or inverter totaliser. The full year matters: production is seasonal, so a part-year reading scaled up from summer flatters the system and one scaled up from winter slanders it. Use generated energy, not the fraction self-consumed.

02
Array size (STC)

The as-built nameplate: the modules actually on the roof times their rated STC output, in kilowatts-peak. If the installed array grew or shrank from the design during installation, the ratio must be computed against what was built — auditing a meter reading against a nameplate that was never installed corrupts the comparison at the source.

03
Peak sun hours (PSH)

The site’s daily solar resource in equivalent full-strength hours. Ideally this is the resource of the measured year itself, from local irradiance data; the long-term average is the usual fallback. Whichever is used, it should be the same basis the original estimate used, because this input is the reference the system is being judged against.

08

Worked example

The scenario

Let the cluster’s reference system face its reckoning: the 5 kWp array, at the site the design rated at 5.5 peak sun hours, with the generation meter showing 8,030 kWh over the first full year of operation.

The engine returns the performance ratio the installation actually achieved. Put it directly beside the value the sizing and yield pages assumed: matching it means the system is doing what the forecast claimed, landing below it means real losses the design did not concede, and landing above it usually means the sun figure was conservative rather than the hardware miraculous.

The verdict is only as honest as the reference. Overstate the peak sun hours and the derived ratio falls even though the system did nothing wrong; understate them and a mediocre installation grades itself excellent. When the derived value surprises, audit the sun input before blaming the roof.

09

Reading the result

01

A measured ratio inside the realistic band closes the case: the installation performs, and the original estimate’s assumption is now evidence.

02

A shortfall of a few points is money, not catastrophe — locate it in the cheap causes first: soiling, a mis-set monitoring baseline, a season of scaffolding.

03

The measured ratio replaces the assumed one in every future calculation. Feed it back into the yield estimate and your projections stop being generic; carry it into the payback calculation and the economics stand on your roof rather than a typical one.

10

Common mistakes

Measuring generation from the household import meter instead of the system’s own generation meter — self-consumed energy vanishes and the system looks worse than it is.

Using eleven months and calling it a year. The missing month is never an average one.

Judging the measurement against tuned sun figures until the ratio flatters. The reference must be the same one the original estimate used.

Treating one bad ratio as a verdict on solar rather than a question about this installation.

11

Questions readers arrive with

How often should I re-measure?

Yearly, on the same date, from the same meter. The first measurement builds the baseline; every later one is a one-division health check that catches degradation while it is still a maintenance item rather than a warranty argument.

My monitoring app already shows a performance figure. Why compute one?

An app’s figure is computed from the vendor’s own assumptions, which you cannot always inspect and which rarely match your site’s sun data. A ratio you computed from your own meter and your own sun figure is one you can defend — and compare across vendor ecosystems.

What if my system is new and I have no full year yet?

Wait. A partial year measures the weather more than the installation. If you cannot wait, compare like with like — the same months against the same months of sun data — and treat the result as provisional until the seasons have cancelled.

Does a good ratio mean the investment was sound?

It means the engineering delivered. Whether the money works is a tariff question, and it is exactly where this journey goes next.

12

When this calculation is used

01

Commissioning: the first full year’s meter reading, turned into a ratio and set against the value the design assumed.

02

Year-on-year tracking, where a slow slide in the ratio is how soiling or degradation announces itself before any fault does.

03

Comparing installations across different sites or sizes on one scale, since the site’s resource is already normalised out.

04

Interrogating the sun figure itself: a derived ratio that comes out implausibly high or low is often the peak-sun-hours estimate confessing, not the hardware.

13

Assumptions and guards

The measurement spans a complete year. A partial year inherits whichever seasons it happened to contain, and no correction for that bias is applied here.

The peak-sun-hours input represents the resource of the measured period. Using a long-term average during an unusually dull or bright year moves the ratio for reasons that have nothing to do with the system.

The nameplate is taken at face value; module rating tolerance and early light-induced degradation fold silently into the derived ratio.

One number aggregates every loss mechanism. Nothing here distinguishes soiling from shading from downtime — that separation belongs to the pack’s dedicated derate calculators.

Peak sun hours below the physical band are refused — the pack ships that refusal as a declared test vector. A sub-unity figure is almost always an irradiance value in the wrong units, and dividing by it would manufacture a spectacular ratio out of a unit mistake.

The measured energy and the array size must both be positive: a zero in either leaves nothing to audit, and the ratio is refused as a domain error rather than returned as zero or infinity.

Upper bounds on the measured energy catch a lifetime totaliser reading entered where a single year belongs — an inflated ratio from that slip would read as a healthy system rather than as the data error it is.

Method authorityPerformance ratio definition, PR = measured annual kWh / (kWp × peak sun hours × 365) · The measured annual energy is divided by the reference yield — nameplate array size times daily peak sun hours times 365 days — returning the dimensionless performance ratio the system achieved over the measured year.

Continue the journey

The next stop shares this lesson's scenario — carry it forward instead of starting over.

View Energy lessons