Eight checkpoints to correctly read PVSyst calculation results

Table of contents

• It is important not to judge PVSyst calculation results by numbers alone

• Checkpoint 1 First confirm that calculation conditions and assumptions are aligned

• Checkpoint 2 Do not evaluate solely by the magnitude of annual energy production

• Checkpoint 3 Check for any unnatural monthly variations

• Checkpoint 4 Review the breakdown of losses to understand where reductions occur

• Checkpoint 5 Confirm how installation orientation and tilt are reflected in the results

• Checkpoint 6 Reassess whether the impact of shading is being underestimated

• Checkpoint 7 Verify consistency between system configuration and results

• Checkpoint 8 Distinguish differences from alternative proposals by condition

• Perspectives to connect PVSyst calculation results to practical decision-making

It is important not to judge PVSyst calculation results by numbers alone

What practitioners using PVSyst should grasp first is that the calculation results are not the end once the numbers appear. What is truly important is interpreting what assumptions produced those numbers and what they mean. If you judge solely by the annual energy production figure, you may miss unrealistic design assumptions, lax loss settings, or overlooked influencing factors as the project proceeds.

In solar PV assessments, results change depending on how assumptions are set even for the same site. Installation orientation, tilt angle, site conditions, system configuration, treatment of shading, and how losses are considered—each condition affects the final energy production and evaluation. Therefore, correctly reading PVSyst results does not mean simply checking the numbers on the output screen; it means checking the design assumptions behind those results as well.

In practice, calculation results are used in many situations: internal explanations, reporting to clients, rough comparisons, and design reviews. If the basis for the results is vague each time, confidence in the numbers falls and decisions tend to rely on intuition. To master PVSyst, being able to read results correctly is more important than producing good-looking numbers. Below, from the practitioner’s perspective, we organize eight items to pay particular attention to when reviewing calculation results.

Checkpoint 1 First confirm that calculation conditions and assumptions are aligned

When reading PVSyst results, the first thing to check is not the annual energy production itself but whether the calculation conditions and assumptions are aligned. No matter how impressive the number looks, if the assumptions are vague the number is weak as practical decision material. It is important to first verify that the installation location, climatic data, capacity assumptions, installation orientation, tilt angle, and loss assumptions match the project’s expectations.

This check is essential especially when comparing options. For example, even if you think you are comparing multiple proposals, you cannot do a straightforward comparison if one uses conservative loss assumptions while another leans toward ideal assumptions. PVSyst results naturally change when conditions change. Therefore, if you do not confirm that assumptions are aligned before comparing, you may end up comparing differences in settings rather than the design proposals themselves.

Even for a single proposal, verifying assumptions is necessary. If a calculation result feels off, rather than immediately suspecting equipment conditions or influencing factors, it is more efficient to first check for input errors or misunderstandings in the assumptions. Using PVSyst draws attention to the numbers on the result screen, but in reality confirming the assumptions is the first step in reading results. Being thorough here stabilizes subsequent interpretation.

Furthermore, the habit of confirming assumptions helps internal sharing. When passing results to other staff, if it is clear under which assumptions the calculations were made, it becomes easier to share the meaning of the numbers. The ability to read PVSyst results correctly deepens individual understanding and improves organizational decision accuracy.

Checkpoint 2 Do not evaluate solely by the magnitude of annual energy production

Annual energy production tends to attract the most attention in PVSyst results, but judging solely by its magnitude is risky. Annual energy production is indeed an important metric, but it is merely the result of multiple conditions stacked together. If you simply equate higher numbers with better and lower numbers with worse, you risk overlooking unrealistic assumptions or future rework.

In practice, people tend to focus on the proposal that yields the highest energy production. However, if that proposal does not fit site conditions, underestimates losses, or treats shading superficially, it will require revision later. Conversely, a proposal whose annual energy production appears modest but whose assumptions are realistic and easy to explain may be more valuable in practice. PVSyst results should be evaluated not only on the number itself but on the plausibility of that number.

Also, annual energy production alone makes it hard to see where improvements are possible. If a result seems low, you must distinguish whether it is due to site conditions, system configuration, or loss assumptions to identify next steps. To leverage PVSyst in practice, view annual energy production as an initial figure and always follow up on the background assumptions.

Moreover, the habit of not evaluating by annual energy production alone makes internal explanations easier. If you present only high numbers and build expectations, adjustments become difficult when assumptions are later revised. If you can explain numbers together with their assumptions from the start, stakeholders understand more readily. Correctly reading PVSyst results means not jumping on eye-catching numbers but judging them together with the design details.

Checkpoint 3 Check for any unnatural monthly variations

Monthly variations provide important information that annual totals cannot show. When reviewing PVSyst results, it is important not only to look at annual figures but also to check for any unnatural month-by-month generation patterns. Even if the annual total looks reasonable, monthly data may reveal that generation drops sharply in specific periods or that certain months are unnaturally high. Such biases can indicate points where settings need to be reviewed.

In practice, examining monthly results makes it easier to understand the impacts of shading, orientation, and how losses appear. Particularly when a large drop is seen in only one season, it may be caused by the combination of design conditions rather than simple weather variability. Correctly reading PVSyst results requires not being satisfied with the annual total and instead understanding the character of the result by looking at the monthly distribution.

Additionally, monthly variations affect operational impressions and revenue projections. When explaining results internally, annual figures alone can fail to convey an intuitive image, but month-by-month trends help communicate seasonal fluctuations and busy or slow periods. PVSyst is both a design tool and a source of material for explanations, so learning to interpret monthly data is highly valuable.

Furthermore, the habit of checking monthly variations helps when evaluating alternative proposals. Two proposals with nearly identical annual energy production may differ in that one has a stable distribution while another shows weakness in specific periods. Such differences are not visible from annual totals alone. To read PVSyst results deeply, you must look beyond sums to the monthly behavior.

Checkpoint 4 Review the breakdown of losses to understand where reductions occur

A particularly important element in correctly reading PVSyst results is the breakdown of losses. If energy production is lower than expected but the cause is unknown, you cannot take effective measures. Conversely, if results look good but loss estimates are optimistic, those numbers lack practical reliability. Therefore, when reviewing results, it is important not only to look at the final energy production but also to check at which stages and to what extent reductions occur.

In practice, losses are sometimes considered as a single lump. However, the value of PVSyst lies in making losses easy to consider by factor. If you can identify which losses have the greatest effect, you can see whether to revise the layout, reconsider the configuration, or review operational conditions more carefully. Reading where reductions occur, not just that numbers are low, is the starting point for improvement.

Also, reviewing the breakdown of losses has significant value for accountability. When questioned by internal stakeholders or partners about the plausibility of results, showing only annual energy production is less convincing. If you can organize and explain which losses were incorporated and how, confidence in the numbers increases. The ability to read PVSyst results correctly deepens the designer’s understanding and improves the quality of explanations to others.

Furthermore, the breakdown of losses provides clues to project-specific characteristics. Even if site conditions seem similar, one project may experience small impacts while another has significant losses. By understanding these characteristics, you can improve estimates and apply lessons to similar projects. If you want to use PVSyst in practice, the breakdown of losses is a must-check item.

Checkpoint 5 Confirm how installation orientation and tilt are reflected in the results

When reviewing PVSyst results, it is necessary to confirm how installation orientation and tilt are reflected. In solar PV, installation direction and angle change generation patterns, so understanding how these conditions affect the results is important. Whether the results look good or bad, without checking if the choice of orientation and tilt is reasonable, design decisions are incomplete.

In practice, not all projects can be installed under ideal conditions. Constraints such as site shape, land preparation, surrounding environment, and constructability require finding a realistic compromise. Therefore, when looking at PVSyst results, it is important to consider not the theoretical optimum but how reasonable the outcome is under the project’s conditions. Understanding the influence of orientation and tilt makes it easier to explain differences in results as design choices.

Also, checking orientation and tilt helps when comparing proposals. To determine whether a higher figure for one proposal is simply due to orientation differences or also due to other design improvements, you need this perspective. PVSyst results combine multiple factors, so separating the influence of orientation and tilt leads to correct interpretation.

Moreover, making this check habitual clarifies the link between field conditions and desk calculations. Installation conditions are strongly affected by site constraints, so reviewing not only the results but also why a particular orientation and tilt were chosen improves design reproducibility. The more you use PVSyst in practice, the more valuable the ability to read the relationship between conditions and results becomes.

Checkpoint 6 Reassess whether the impact of shading is being underestimated

One item to pay attention to in PVSyst results is the impact of shading. Even if the calculation suggests sufficient energy production, if shading is handled lightly the actual outcome may be much worse. Elements that affect shading—surrounding terrain, existing structures, spacing between equipment—vary by project. Therefore, when reading results, it is important to recheck whether the effect of shading is appropriately reflected.

In practice, there is a tendency to tighten equipment spacing to use the site efficiently. However, prioritizing layout density too much can cause strong shading impacts at specific times or seasons. When PVSyst results look good, it is easy to become complacent, but if shading evaluation is insufficient that confidence is precarious. In particularly constrained projects, not underestimating shading is a basic requirement for interpreting results.

Also, shading impacts may not be visible from the annual total. They can appear as month-by-month differences or as drops in specific periods, so it is important to review related results together. Correctly reading PVSyst results requires a perspective that is not a binary “shaded or not” but rather an assessment of the degree of impact. Grasping this helps trigger layout or design revisions.

Furthermore, reassessing shading reduces rework in later stages. A proposal that looked good at the planning stage can encounter shading issues during detailed assessments, necessitating layout or capacity rethinking. Carefully checking for underestimation of shading when reading PVSyst results raises realism at an early stage. This is a significant advantage for practitioners.

Checkpoint 7 Verify consistency between system configuration and results

When reading PVSyst results, always verify consistency between the system configuration and the results. Results may look reasonable at first glance, but if the configuration assumptions are unrealistic the figures become difficult to use in practice. In solar PV design, configuration conditions and results are inseparable. Therefore, you need to judge not only energy production and losses but also whether the underlying system configuration is natural for the project.

In practice, configurations tend to be provisional in the early stages, and results can start to circulate on their own. However, if configuration assumptions are far removed from reality, results can change significantly when details are worked out later. Correctly reading PVSyst results requires confirming what configuration the numbers are based on and whether that configuration is reasonable for the project.

Also, checking consistency between configuration and results makes it easier to find the cause of any oddness. Whether results are too high or too low, instead of being surprised by the figures alone, comparing them to configuration conditions points the way to corrections. A strength of PVSyst is that it allows you to verify results while organizing conditions; mastering this reading improves usability significantly.

Furthermore, confirming consistency with system configuration helps in project management. When a different person takes over or the project is reviewed after some time, understanding is easier if the connection between configuration and results is organized. If you want to use PVSyst outputs as practical documentation, do not leave only numbers; keep them paired with the configuration.

Checkpoint 8 Distinguish differences from alternative proposals by condition

PVSyst results become more valuable when viewed not only individually but also by distinguishing differences from alternative proposals by condition. In practice, multiple design proposals are often considered for a single project, and you need to determine which proposal is more appropriate. At that time, it is important not to compare only the final energy production but to read which condition differences are creating the result differences.

For example, even if one proposal shows higher energy production, the evaluation changes depending on whether that is due to orientation differences, loss assumptions, or different shading expectations. A higher number alone does not allow you to judge feasibility or reproducibility. When reading PVSyst comparison results, you must examine not only the magnitude of differences but also the conditions that produce those differences. Doing so lets you understand the character of each proposal rather than simply ranking them.

Additionally, the ability to read differences between alternatives by condition supports internal decision-making. In meetings, opinions may prioritize energy production, constructability, or ease of explanation. If you present PVSyst comparison results organized by condition, it becomes easier to conduct discussions that include the background behind the numbers. This is valuable not only for designers but also for management and planning staff.

Moreover, the habit of distinguishing comparison proposals by condition builds institutional knowledge. By understanding on a project-by-project basis how much different condition changes affect results, initial judgments for future projects become faster. To use PVSyst effectively in practice, do not stop at one-off estimates; accumulate design insights from comparison results.

Perspectives to connect PVSyst calculation results to practical decision-making

What the eight checkpoints above have in common is the concept of reading PVSyst results not as numbers alone but in relation to the conditions. From confirming assumptions, to interpreting annual energy production, monthly variations, the breakdown of losses, orientation and tilt, shading impacts, consistency with system configuration, and distinguishing differences among proposals, all are perspectives necessary for understanding the background of results. By covering these points, PVSyst outputs become not just calculations but materials usable for practical decision-making.

For practitioners, the important thing is not to stop at viewing results but to turn them into the next actions. If you can see what to revise, which proposal is realistic, and which conditions are key to explanations, design and internal coordination proceed more smoothly. The value of PVSyst lies less in producing advanced numbers and more in organizing materials that link design and decision-making. Therefore, learning how to read results is more important than becoming merely familiar with the operation.

To further leverage PVSyst in practice, improving the accuracy of on-site understanding as well as desk assumptions is effective. If understanding of the installation location, the reasonableness of orientation and tilt, shading potential, and constraints on layout is vague, misinterpretation is more likely. The accuracy of input conditions themselves is important to correctly read results.

In that sense, when you want to efficiently carry out on-site position confirmation and coordinate acquisition, using iPhone-mounted GNSS high-precision positioning devices such as LRTK is a practical idea. If the accuracy of on-site position information and site condition data improves, the reliability of the assumptions fed into PVSyst also increases, and result interpretation becomes more practical. Establishing a workflow that interprets PVSyst results and supports on-site data capture with LRTK makes it easier to connect desk estimates with site reality. The ability to correctly read calculation results is not merely analytical skill but the practical capability to connect design and site.