Six Ways to Correctly View Performance Ratio in PVSyst

Table of Contents

• Why the way you view Performance Ratio in PVSyst becomes important

• Method 1: Do not judge PR solely on its own

• Method 2: Align meteodata and installation-condition assumptions when reviewing

• Method 3: Read the PR breakdown together with the loss tree

• Method 4: Separate shading, temperature, wiring, and outage conditions

• Method 5: In comparative simulations, organize condition differences before viewing PR

• Method 6: Check not only annual values but monthly and per-scenario trends

• How to link PVSyst PR evaluation to practical decisions

Why the way you view Performance Ratio in PVSyst becomes important

For practitioners running generation simulations in PVSyst, the Performance Ratio is a metric that draws a lot of attention. Often abbreviated as PR, it is used as a quick indicator to assess the validity of a design or to compare multiple proposals. Precisely because of this, when users first start using PVSyst they tend to look first at the annual energy and PR numbers and want to judge whether a proposal is good or bad. In practice, however, relying on this view alone can easily lead to incorrect judgments.

The reason is simple: PR is not a standalone figure but the result of many underlying assumptions. PR emerges after stacking up assumptions about meteodata placement, azimuth and tilt angles, shading expectations, temperature losses, wiring losses, PCS behavior, and utilization-loss assumptions. In other words, the same PR can hide very different internal details, and conversely a slightly lower-looking PR can be perfectly reasonable if its assumptions are realistic.

A common practical mistake is to immediately conclude a design is poor when PR is lower than expected, or to feel reassured if it is high. While PVSyst faithfully reflects input conditions, impressions vary greatly depending on whether those inputs are optimistic or realistic. For example, underestimating shading will tend to make PR look higher, while realistically incorporating maintenance and outage conditions can make PR look conservative. Therefore, it is important not only to note whether PR is high or low, but to be able to explain why that number arose.

Organizing how you read PR also greatly improves the quality of internal explanations and comparison documents. Rather than saying a plan is advantageous simply because it has a higher PR, you can explain that one plan has lower shading loss but somewhat higher temperature loss, or that another plan appears lower on an annual basis but is realistic when outage conditions are included. Mastering PVSyst in practice means not just looking at the final energy number, but being able to interpret a design’s contents through the PR.

Method 1: Do not judge PR solely on its own

The first method to correctly view PR is to avoid judging PR by itself. In practice, annual energy and PR are the first figures you see, and it’s natural to want to rank proposals by those two numbers. Of course, PR is an important metric and convenient as an entry point for comparison. However, directly equating PVSyst’s PR to a good-or-bad judgment can lead to misreading the design’s meaning.

For example, two proposals with similar-looking PRs might differ internally: one might have small shading losses while the other compensates for large shading losses through other assumptions. Also, one proposal might look high because it uses idealized assumptions, while another looks slightly low because it carefully reflects site conditions. Deciding superiority from numbers alone without seeing these differences often leads to rework later.

Moreover, PR is a summary of the project’s overall loss structure, so it doesn’t reveal causes by itself. Knowing only that PR is low does not tell you whether shading, temperature, PCS issues, or utilization losses are responsible. In other words, PR is a conclusion, not an explanation. Practitioners need the habit of returning from the PR number to its underlying assumptions.

Therefore, when viewing PR, first treat it as an indicator and then always check its contents. Avoid the simplistic view of “high equals safe” or “low equals failure,” and read why the number arose by navigating other screens and settings. If you want to use PR practically in PVSyst, it is more useful to consider PR not as a single-score evaluation of a proposal but as an entry point to identify items that require verification.

Method 2: Align meteodata and installation-condition assumptions when reviewing

The second method to correctly view PR is to align the meteodata and installation-condition assumptions. In practice, when you see PR differences you naturally suspect differences in equipment conditions or loss factors. But before that, you should confirm whether the installation location and meteodata are consistent, and whether azimuth, tilt, and layout conditions match on-site conditions. If these are not aligned, comparing PRs becomes ambiguous.

For example, if one proposal assumes a location very close to the actual site while another uses a representative nearby station, the observed PR difference might stem from meteodata assumptions rather than design differences. The same applies to azimuth and tilt. It is natural that PR will differ between a proposal leaning toward ideal conditions and one tailored to site reality. When comparing multiple proposals in PVSyst, clearly define what variables are being changed and keep other assumptions as consistent as possible.

Meteodata differences affect not only irradiance but also temperature conditions, which in turn influence perceived temperature losses and thus PR. Therefore, before attributing PR differences to design quality, confirm that the underlying assumptions are on the same footing. Skipping this check can undermine the basis of your conclusions.

As a countermeasure, before comparing PRs, first confirm that meteodata location, azimuth, tilt, array layout, and shading assumptions are aligned. Fix as many conditions as possible except for the variables you want to compare; viewing PR in a context where the meaning of differences is clear makes interpretation much more stable. To correctly view PR in PVSyst, it is important to align the assumptions that produced the number before you judge the number itself.

Method 3: Read the PR breakdown together with the loss tree

The third method is to read PR together with the loss tree rather than viewing PR alone. PVSyst provides a single PR metric that conveys the overall sense of efficiency, but the loss tree shows how that PR results from accumulated losses. In practice, what is most useful is not the PR number itself but understanding the order and magnitude of the losses that produced it.

For example, whether PR is low because shading dominates, temperature losses are large, or wiring and PCS issues are significant determines completely different directions for improvement. If shading is large, you might need to review the 3D scene or row spacing; if temperature is large, check array density and installation environment; if wiring/PCS losses are significant, review site consolidation, PCS placement, and stringing. You can’t tell these differences by looking at PR alone. Viewing the loss tree together reveals where the PR number comes from.

The loss tree is also very effective when explaining differences between proposals. A proposal with a slightly higher PR may be due to lower shading losses or lower wiring/utilization losses, and the decision value changes depending on which it is. Even small numerical differences can reveal which proposal is more robust on-site when you look at the loss structure. If you use PVSyst in practice, get into the habit of viewing PR and the loss tree together.

The practical countermeasure is to always return to the loss tree when PR is a concern and check the largest losses first. Looking beyond the annual summary number to see at which stage and by how much energy drops helps identify where to focus PR improvements. To correctly view Performance Ratio in PVSyst, understand PR not as an isolated report card but as a summary value of the loss tree.

Method 4: Separate shading, temperature, wiring, and outage conditions

The fourth method is to separate major loss factors—shading, temperature, wiring, and outage conditions—rather than mixing them together. In practice, when PR is low all losses can appear jointly worsened, making it unclear where to start. However, if you read PVSyst results carefully, you see that losses have different natures. Failing to separate them mixes improvable losses with those that must be accepted.

For example, if shading loss is large you may need to review Near Shading, the 3D scene, or array layout. If temperature loss is large, reassess ventilation conditions, array density, or module assumptions. If wiring loss is significant, reconsider site consolidation, PCS location, and string configuration. If outage conditions are affecting PR, organize utilization-loss and maintenance assumptions. These are all “losses,” but the remedies differ entirely.

This separation also helps compare multiple proposals. One proposal may have little shading but strict outage conditions, while another may have low temperature loss but high wiring loss. Decomposing PR differences shows this. In practice, choosing the highest-PR proposal is not always correct. Only by identifying the main loss drivers and judging whether they are reasonable for the site can you assess a proposal’s value.

As a countermeasure, when you see PR do not immediately fix on a single cause; first divide and check the main factors—shading, temperature, wiring, and utilization. Doing so turns PVSyst results from mere high/low differences into actionable design improvement notes. Correctly viewing PR means not only knowing what the number means but categorizing and handling its internal components.

Method 5: In comparative simulations, organize condition differences before viewing PR

The fifth method is to organize condition differences before viewing PR when running comparative simulations. In practice, the more proposals you create, the more conditions tend to change simultaneously. If module, PCS, DC/AC ratio, azimuth, tilt, shading assumptions, and loss factors all vary together, it becomes unclear where PR differences come from. While PVSyst makes comparisons easy, poorly organized comparison conditions multiply numbers without strengthening conclusions.

For example, if you want to see PR differences due to azimuth but PCS capacity and utilization-loss assumptions have also changed, you cannot attribute the difference to azimuth. Conversely, if you want to study the effect of shading, keep equipment and loss factors as consistent as possible so the differential is clear. When comparing proposals in PVSyst, decide in advance what the variables are and fix everything else.

When comparison conditions are organized, explaining PR differences becomes concise. If all weather and equipment conditions are the same and only row spacing is changed, the difference is easy to interpret as shading/layout-related. In practice, this clarity is very important. A comparison that cannot be summarized in one sentence at a meeting or review is weak as decision material even if many numbers exist.

As a countermeasure, before creating comparative proposals in PVSyst explicitly state what you will change and what you will fix. Viewing PR after this makes the origin of number differences much clearer. Organizing comparison conditions is often overlooked but is highly effective in practice for correctly viewing PR.

Method 6: Check not only annual values but monthly and per-scenario trends

Finally, it is important to check PR not only as an annual value but also by monthly and per-scenario trends. In PVSyst the annual PR is the first thing you notice, and it’s tempting to form an impression based on that number alone. In practice, however, it is crucial to see whether a low PR is uniform across the year or whether differences occur mainly in specific seasons, because shading, temperature, and utilization losses vary seasonally.

For example, if PR drops significantly only in summer, suspect temperature conditions or PCS behavior. If differences appear only in winter mornings and evenings, shading assumptions may be the cause. If PR is consistently slightly low year-round, consider reviewing wiring, utilization, or overall loss-factor placement. Viewing only annual values in PVSyst makes such source separation difficult, but monthly and per-scenario trends reveal the dominant factors.

Viewing proposals month-by-month also helps you understand each proposal’s character. Two proposals that are close in annual totals may show that one is strong in summer while the other is stable in winter. In practice, such differences can influence maintenance, operations, and ease of explanation. Using PVSyst not merely as an annual energy comparison tool but as a way to observe seasonal behaviors makes design decisions far more practical.

As a countermeasure, when confirming PR always return to monthly trends after checking the annual total. Identify which seasons show the differences and when per-scenario gaps concentrate; this clarifies root-cause identification. To correctly view Performance Ratio in PVSyst, it is essential not only to note annual height or depth but to see how that number appears along a timeline.

How to link PVSyst PR evaluation to practical decisions

What the six methods above share is the idea of not treating PR as a standalone score. Instead of using PR as a binary good/bad judgment, read it in conjunction with meteorological assumptions, installation conditions, the loss tree, shading, temperature, wiring, outage conditions, comparison conditions, and monthly trends. Once you can do this, PR becomes not merely a final number but a strong indicator to organize design assumptions and find improvement points.

For practitioners, the important thing is not choosing the proposal with the highest PR. The real value is being able to explain why that PR reached its number. A high PR based on overly ideal assumptions is fragile, while a slightly lower PR that aligns with site conditions can be a robust design. If you use PVSyst in practice, emphasize how convincing the PR is rather than just its magnitude.

Also, strengthening PR interpretation requires not stopping at desk-based simulations. If site boundaries, slopes, access paths, buildings, obstacles, maintenance routes, and on-site accessibility are unclear, the PR background remains ambiguous. To connect PVSyst results to practice, iterate between site understanding and simulation to judge which assumptions are natural and which are optimistic.

In that sense, when you want to increase certainty in on-site position checks and coordinate acquisition, using iPhone-mounted GNSS high-precision positioning devices such as LRTK is also effective. If position information and site conditions obtained on-site are easier to organize, PVSyst assumptions about layout, shading, aisles, and maintenance conditions become clearer. If you can improve desktop comparison accuracy in PVSyst and support site understanding accuracy with LRTK, PR evaluation moves from mere numeric comparison toward site-grounded practical judgment. Carefully interpreting Performance Ratio not only improves the accuracy of generation forecasts but also enhances design capability that connects office simulations with the field.