Back to Blog
solar design10 min read

Solar Performance Ratio Formula: PR Calculation

Read solar performance ratio reports by checking meter boundaries, data quality, temperature methods, loss evidence and the acceptance rules for each project.

Keyur Rakholiya

Written by

Keyur Rakholiya

CEO & Co-Founder · SurgePV

Rainer Neumann

Edited by

Rainer Neumann

Editorial contributor · SurgePV

Published ·Updated

Answer

Solar performance ratio (PR) is final yield divided by reference yield: AC energy per kW of DC capacity, divided by plane-of-array irradiation in kWh/m² per 1 kW/m². NREL says new systems typically fall between 0.6 and 0.9. A worked 100 kWp month with 11,250 kWh and 150 kWh/m² gives 0.75. Acceptance uses the PR written into the contract.

Last updated: November 2026. SurgePV publishes this post and sells solar design software.

A PR number on its own tells you little. The same plant can read differently depending on the meter, the irradiance sensor and the temperature method. Final yield is AC energy per kW of installed DC capacity (the panel rating). Reference yield is the plane-of-array irradiation (sunlight on the panel surface) in hours at full sun.

This guide gives the PR formula, a worked calculation and the ranges published in primary sources. It also shows how to read a PR report. That means the meter boundary, data checks, temperature correction and loss evidence. For monthly worksheets with full tables, use the PR calculation tutorial. For the term itself, see the performance ratio definition.

Model the PR you expect before the plant is built

SurgePV energy-yield modeling gives a design-stage yield to compare against measured PR once the plant is running.

Book a Demo

Checking cost first? See the SurgePV pricing page · Guided demo · No credit card

PR Formula in Solar: The Performance Ratio Equation

This is the formula for a standard monofacial PV system (panels that use light on the front only). It uses AC energy at a stated boundary:

PR = (E_AC / P_DC,STC) / (H_POA / G_STC)

  • E_AC is the AC energy for the period, in kWh.
  • P_DC,STC is the installed DC nameplate power (the rated power on the panels), in kW.
  • H_POA is the plane-of-array irradiation for the same period (sunlight energy on the panel surface), in kWh/m².
  • G_STC is the reference irradiance, 1 kW/m².

The first bracket is final yield (kWh/kW). The second is reference yield (hours at full sun). Both work out to hours, so their ratio has no unit. IEA PVPS section 2.1.2 and the 2022 IEA PVPS O&M guidelines (section 2.1.2) define PR this way. IEA PVPS is the International Energy Agency’s Photovoltaic Power Systems Technology Collaboration Programme.

PR is not module efficiency. It is also not measured energy divided by a modeled annual forecast. That ratio is the energy performance index (EPI), which uses a different denominator (IEA PVPS KPI guidance, section 2.1.6). Availability (how much of the time the plant can run) is a third, separate indicator (section 2.1.3).

Worked example: PR for one month

Calculate the PR of a 100 kWp array for one month from three inputs. The inputs are hypothetical. They show the arithmetic.

Known inputs
ParameterSymbolValueUnitInput basis
Installed DC capacityP_DC,STC100kWpHypothetical input
Plane-of-array irradiationH_POA150kWh/m²Hypothetical input
AC energy at the meterE_AC11,250kWhHypothetical input
Formula
PR = (E_AC / P_DC,STC) / (H_POA / G_STC), with G_STC = 1 kW/m²
Calculation
Final yield = 11,250 / 100 = 112.5 kWh/kW; reference yield = 150 / 1 = 150 h; PR = 112.5 / 150 = 0.75
Result
PR = 0.75, or 75%
Interpretation
Say the same 11,250 kWh were divided by a capacity record of 110 kWp by mistake. PR would read 11,250 / (110 × 150) = 68.2%. The plant did not change. The denominator did.
Assumptions and limitations
One month, no temperature correction, front-side irradiation only. The 75% figure is an arithmetic example, not a benchmark for any site.
Basis
IEA PVPS Task 13 KPI guidance, section 2.1.2 (formula); inputs are hypothetical

How to calculate the performance ratio of a solar power plant

  1. Pick one period. SMA’s technical note (SMA is an inverter maker) calls one year the best period to analyze. It suggests at least one month. Then low sun angles, low temperatures and shadows do not dominate the result.
  2. Add up the AC energy from the agreed meter for that period.
  3. Add up the plane-of-array irradiation from a sensor that sits in the same plane as the modules. SMA notes that the sensor and the modules must face the same way.
  4. Divide the energy by the installed DC capacity, and the irradiation by 1 kW/m².
  5. Divide the first result by the second.

For several months or a full year, add the energy and the irradiation first, then divide. Do not average monthly percentages. The tutorial shows this with three hypothetical monthly worksheets.

What is a good performance ratio?

Published figures, with the source of each:

Source Figure What it covers
NREL, Weather-Corrected Performance Ratio (April 2013) 0.6 to 0.9 PR values for new systems, as the report summarises its references
NREL, same report Up to ±10% over the year Seasonal swing in PR, linked to module temperature
NREL, same report Some systems at or above 0.9 About 100 German systems in a cool climate
SMA technical note (version 1.1) Up to 80% SMA’s statement for high-performance plants; the PDF is undated and its file metadata shows 2010 and 2016
IEA PVPS O&M guidelines (2022) 85% theoretical, 83% guaranteed A worked contract example, not a benchmark
Published performance ratio figures, as each source states them (PR, percent)
  • NREL: low end of new-system range60%
  • SMA: high-performance plants, up to80%
  • IEA PVPS example: guaranteed PR83%
  • IEA PVPS example: theoretical PR85%
  • NREL: high end of new-system range90%

Source: NREL Weather-Corrected Performance Ratio (2013), SMA technical note (undated), IEA PVPS O&M Guidelines (2022). The bases differ, so read them as separate statements, checked November 2026.

Key Takeaway

The published ranges disagree because they come from different plants, climates and dates. Use the PR your own model predicts for the site, and the PR written in the contract for acceptance.

The two general ranges disagree. NREL gives 0.6 to 0.9 for new systems and says cool-climate German systems reached about 0.9. SMA’s older note says up to 80%. Both are printed here as published. For a new design, use the PR your own model predicts for that site, not a range from another climate.

For acceptance, use the contract PR. The IEA PVPS O&M guidelines (O&M means operations and maintenance) say the theoretical PR is calculated when the contract is made. It uses typical meteorological year data, which is a modeled year of typical weather. The guaranteed PR is then set equal to it or slightly lower. Their example is a plant with a theoretical PR of 85%, with the guarantee set at 85% or at 83%. The guidelines also say to agree the PR formula. The formula should account for factors such as temperature and plant availability. They also say to use correct measured inputs.

PR can read above 100%. SMA lists a shaded or misaligned irradiance sensor as a cause. Check the sensor first. A value above 100% is a data flag, not proof of a perfect plant.

Plant design also moves PR. IEA PVPS notes that some plants have far more DC capacity than inverter (AC) capacity, a high DC-to-AC ratio. For these plants, higher irradiation lowers PR because of clipping. Clipping is when the inverter cuts off power it cannot handle. See the inverter sizing guide for how the ratio is chosen, and the glossary entry on inverter clipping.

For bifacial systems (panels that also use light on the back), IEC 61724-1:2021 proposes a bifacial PR. It uses the bifaciality coefficient and the rear-side irradiance ratio (IEA PVPS section 2.1.2). PVsyst’s PR documentation (PVsyst is solar simulation software) records that its bifacial PR changed at version 8.0.12 to include the bifaciality factor. Record the software version and the metric name before you compare two reports.

Turn a PR target into a modeled yield

Book a guided demo to see how SurgePV models energy yield and what the output contains, so your expected PR has a traceable basis.

Book a Demo

Checking cost first? See the SurgePV pricing page · Guided demo · No credit card

Solar plant performance ratio calculation: set the measurement boundary first

Fix these items before you compare results over time:

Field What to record Why a change matters
Electrical energy Meter location, gross or net, self-consumption coverage Grid export alone omits on-site PV use
DC capacity Installed module rating, additions, removals A denominator change mimics a performance change
Irradiation POA orientation, source, sensor coverage, units A different plane or source changes the reference
Time Timezone, intervals, start and end, synchronised records Misalignment creates false patterns
Data treatment Missing intervals, replacements, filtering, exclusions Different samples hide lost energy
Corrections Metric name, temperature reference, coefficients, method Corrected and uncorrected figures differ
Operating events Outages, curtailment, maintenance A low ratio is not always a module fault

PVsyst’s documentation defines the energy term by system type. For a plain grid system it is grid export. Where the site uses some of its own output, it is grid export plus self-consumed solar energy. For stand-alone systems it is the energy delivered to the user. Do not assume a two-way connection meter gives a PV generation total.

Pro Tip

Before you compare two PR reports, write down the meter location, the irradiance sensor plane, the capacity used and the temperature reference for each. If any of the four differ, the numbers are not comparable.

Keep raw records and a processing log. Then another reviewer can repeat the reported period without guessing which samples were removed.

Check data quality before sending a crew

A PR change can start in the energy (the top of the ratio), the capacity and irradiation (the bottom) or how they line up in time. Check these first:

  • Meter resets, counters that roll over, unit changes and missing energy intervals.
  • Frozen or unlikely sunlight and temperature readings.
  • Which way the sensor faces, its calibration record, shading and cleanliness.
  • Timestamp offsets, daylight-saving handling and where totals start and end.
  • Swapped equipment or changed capacity in the monitoring setup.

Use measurements from the actual period for operating PR. A typical meteorological year is a modeled reference year, not the weather that occurred. IEA PVPS’s uncertainty note says the observed PR is easy to determine, including its uncertainty. The expected PR is the major issue, because it depends on system design and operating conditions.

Report missing-data coverage next to the result. Extra decimal places do not improve the evidence.

How does temperature change PR?

Module temperature moves PR. The NREL report gives a typical power change of about 0.5% per °C. A corrected metric needs four things. They are a named reference temperature, the module power coefficient, the temperature input and the aggregation method (how values are combined over time).

The IEA PVPS O&M guidelines say the reference is often the annual weighted module temperature from a standard model. It can also be the standard test temperature of 25°C. They also say that when you use combined values, the mean module temperature must be irradiance-weighted. The 2024 IEA PVPS KPI (key performance indicator) guidance adds a point. Apply the correction to the finest data you have, preferably sub-daily. Correcting a PR built from coarser data gives wrong results, because averaging hides the detail.

The two temperature references give different numbers. NREL points out that correcting to 25°C usually raises PR, because modules often run at 45°C. It adds that this can overstate the performance a financier should expect. NREL’s weather-corrected method uses an annual reference cell temperature taken from the site weather file. So the annual PR is unchanged while seasonal swings shrink.

If a correction changes an acceptance result, show the original and corrected figures with their inputs.

Build a loss evidence register

A ratio reports a result. It does not name a cause. Work from what you observe and what backs it up:

Observation Possible explanations to test Useful corroboration
Several inputs fall together Shared operating constraint or measurement issue Event log, meter and sensor checks, system settings
One comparable input diverges Local irradiation, wiring, module or input issue Configuration, shade record, qualified diagnostics
Output plateaus AC limit, control setpoint, thermal limit Limit and status records, the model’s loss breakdown
Trend changes after cleaning Soiling, or changed weather or sample Matched conditions and a documented comparison
Seasonal movement Temperature, optical conditions or operations Corrected metric and event history

Thermal images, string measurements (readings from a group of panels wired together) and inspections need a qualified person to read them and an agreed procedure. A bright region in an image does not point to one cause of failure.

Read a loss waterfall without adding percentages

PVsyst’s loss-diagram documentation states that each loss is a percentage of the previous energy amount. So the percentages do not add up. A grouped loss is not the sum of the detailed values.

Hypothetical sequential losses: keep each denominator visible

Apply two assumed reductions to a starting amount of energy. These percentages are inputs for the arithmetic, not plant-loss benchmarks.

Known inputs
ParameterSymbolValueUnitInput basis
Starting energyE₀1,000kWhHypothetical input
First reductionL₁5%Hypothetical input
Second reductionL₂3%Applied to remaining energy
Formula
E₂ = E₀ × (1 − L₁) × (1 − L₂); combined reduction = (E₀ − E₂) / E₀
Calculation
1,000 × 0.95 = 950 kWh; 950 × 0.97 = 921.5 kWh; (1,000 − 921.5) / 1,000 = 0.0785
Result
921.5 kWh remains; combined reduction is 78.5 kWh, or 7.85% of starting energy
Interpretation
The second reduction applies to 950 kWh. Adding 5% and 3% would use a different base and would not give this result.
Assumptions and limitations
These are hypothetical reductions in sequence. Real reports can include branches, gains and exclusions. Keep each energy boundary and avoid double-counting modeled losses.
Basis
PVsyst loss-diagram definition; hypothetical inputs

A weighted inverter rating is not the annual conversion loss. Ask for the efficiency curve the model used. Keep inverter clipping separate from conversion loss and control limits.

Choose an action from the evidence and the recoverable energy

After you check the report, list what you saw, the energy it affects, the cost and the access limits. Cleaning, layout changes, settings, repair and replacement each need their own evidence and approval.

Keep the reporting definition the same when you compare before and after. Record the dates of the work and the weather. A PR rise after work does not show that the whole difference came from that work.

Keep reversible operating losses apart from long-term degradation (panels slowly losing output). A fixed yearly PR fall is not a warranty claim by itself. The warranty terms, test method and component evidence decide that.

When you review a design instead of an operating plant, compare energy and documented loss assumptions together. A higher PR can come with a smaller installed capacity or less delivered energy. The energy simulation guide covers how to set up that review. The PVsyst report bankability guide covers how to review a simulation report. To make the expected PR traceable, keep a production estimate assumption register.

Acceptance tests and contractual reports

Agree the metric and procedure before you measure anything for acceptance. Record the period, boundary, instruments and how capacity is counted. Record the corrections, valid-data rules, exclusions and how uncertainty is handled.

A monthly operating report, a short performance test and an annual guarantee serve different purposes. The signed agreement sets the terms of each. The IEA PVPS KPI guidance lists typical contract exclusions. They are curtailment, planned shutdown, force majeure (events outside a party’s control) including grid outage, tracker wind-stow (trackers moved to a safe position in high wind) and missing data.

Where exclusions apply, keep an all-event production view as well. An excluded outage still cost the owner that energy.

The final handoff should include the calculation version, the raw-data reference, the processing log and the event timeline. It should also include open limits and the reviewer’s reason for accepting or investigating the result.

For a design-stage view of the same chain, see how SurgePV handles energy-yield modeling, or book a demo with one of your own projects.

Frequently Asked Questions

What is the performance ratio formula for solar?

PR = (E_AC / P_DC,STC) / (H_POA / G_STC). Divide measured AC energy by the installed DC nameplate power (the panel rating) to get final yield. Divide plane-of-array irradiation by 1 kW/m² to get reference yield. PR is the first result divided by the second.

What is a good performance ratio for a solar system?

The NREL weather-corrected PR report says PR values for new systems typically range from 0.6 to 0.9. It says some of about 100 German systems approached or exceeded 0.9 in a cool climate. For acceptance, use the PR set in the contract. One example is a theoretical PR of 85% with a guaranteed PR of 83%, as in the IEA PVPS O&M guidelines.

How do you calculate the performance ratio of a solar plant?

Take one period, usually a month or a year. Add up the AC energy and the plane-of-array irradiation for that period. Divide the energy by the installed DC capacity. Divide the irradiation by 1 kW/m². Then divide the first result by the second. Use the same meter and the same period for both.

What causes low performance ratio in solar panels?

Outages, curtailment (forced output cuts), shading, soiling (dirt on panels), hot modules, inverter clipping and equipment faults all lower PR. So do meter or irradiance sensor errors. Check the data first. Then compare event logs and site inspections before you name a cause.

What is the difference between performance ratio and capacity factor?

PR divides the energy produced by the energy the array would make at its rated efficiency under the irradiation received. Capacity factor divides energy by rated power times the hours in the period. PR adjusts for the irradiation received. Capacity factor does not.

What is temperature-corrected performance ratio?

It is PR adjusted to a reference module temperature, using the module power temperature coefficient. The reference is either 25°C or an annual weighted module temperature. Apply the correction at the finest time resolution available. Correcting monthly averages gives errors (IEA PVPS).

Sources

Primary research and reference material used for this desk-research article.

Where this fits

This article is part of SurgePV's Solar Design hub, which works through the topic from first principles to the decisions a project team actually has to make.

About the Contributors

Author
Keyur Rakholiya
Keyur Rakholiya

CEO & Co-Founder · SurgePV

Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.

Editor
Rainer Neumann
Rainer Neumann

Editorial contributor · SurgePV

Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.

Get Solar Design Tips in Your Inbox

Join 2,000+ solar professionals. One email per week - no spam.

No spam · Unsubscribe anytime

Book Free Demo

Choose which optional technologies SurgePV may use. Essential storage remains active for security and requested features.