What is PVSyst｜A preemptive guide to the pitfalls that trip up beginners

Table of Contents

• What is PVSyst?

• An overview of PVSyst you should know first

• Beginner stumbling point 1 Difference between rough estimation and detailed design

• Beginner stumbling point 2 How to handle meteorological data

• Beginner stumbling point 3 How to think about mounting surfaces and system configuration

• Beginner stumbling point 4 How to account for losses

• Beginner stumbling point 5 How to interpret shading

• Beginner stumbling point 6 How to read the results

• Beginner stumbling point 7 When to use performance comparisons

• Summary

What is PVSyst?

PVSyst is specialized software for studying photovoltaic power generation systems, sizing capacity, evaluating performance, and analyzing data. The official documentation presents it as an environment that covers not only grid-connected systems but also standalone systems, pumping applications, and DC-system applications, and it is designed so that the meteorological database, component database, simulations, loss analyses, economic assessments, and comparisons with measured data can all be handled in a single workflow. In other words, PVSyst is not simply a calculator that once computes annual energy production; understanding it as practical software that consolidates a PV project's assumptions and supports design decisions with numerical evidence makes it easier to grasp the overall picture.

When a practitioner searches for "What is PVSyst", what they want to know first is not the meaning of the name but what it can do, why it is widely used, and where people tend to get stuck. The strength of PVSyst is that it links site, weather, mounting surface, equipment configuration, losses, shading, result comparison, and performance validation within a single conceptual framework. Within a project, you can save and compare multiple simulation runs with different conditions, which makes it easier to explain not just a series of numbers but why the results occurred. This is a major reason it has been used in practice for so long.

However, when beginners start using PVSyst, the large number of features can make it hard to know where to begin. In particular, the differences between preliminary and detailed design, how to choose meteorological data, how to assign losses, shading assessment, and how to interpret results are areas that, if not understood up front, may allow someone to operate the software yet make it difficult to translate that into design decisions. Therefore, in this article we go beyond explanations of PVSyst itself and proactively organize the points where beginners tend to stumble. If you first grasp the overall workflow and then address the commonly troublesome issues one by one, your perspective on PVSyst will change considerably.

What You Should Know First: An Overview of PVSyst

In a nutshell, PVSyst is software for organizing solar power planning by the connections between conditions and outcomes rather than by "intuition." According to the official general description, it first performs quick monthly estimates from a small number of inputs in the preliminary design, and in the full phase it carries out detailed time-step simulations in project design. In other words, you use it initially to get a rough sense of direction, and once the conditions are set you delve deeply into the mounting surface, system configuration, losses, shading, and so on—a two-stage approach. The ability to be used step by step is one reason it is easy to use for both beginners and project practitioners.

To put it a little more simply, PVSyst is software that sequentially follows "which location", "which orientation", "what configuration", "how much loss is expected", and "how much usable energy results." Rather than aiming for a finished answer right away, you use it by first setting the basic conditions, then adding design conditions, and finally refining losses and shading and interpreting the results. The official tutorial likewise recommends creating an initial proposal with the minimum parameters, then progressively adding far shading, near shading, and individual losses. In other words, the proper way to use PVSyst is not to produce the correct answer in one pass, but to develop the design while observing differences in the conditions.

Having this overall picture in advance considerably eases the impression that “there are too many input items and it’s difficult.” That’s because you realize you don’t need to enter everything perfectly from the start—you can deepen it step by step. Conversely, if you start without this overall picture, you may treat the initial estimate as if it were a definitive value or postpone losses and shading too much, making it easy to misuse the tool. Beginners, in particular, find it easier to understand PVSyst if they view it not as a “highly capable calculation program” but as “software for organizing the design workflow.”

Common Beginner Pitfall 1: The Difference Between Rough Estimates and Detailed Design

A common initial stumbling block is confusing a preliminary estimate with detailed design. PVSyst’s preliminary design is intended to quickly evaluate monthly system yield using only a small number of general conditions. Even the official documentation explains that this stage produces a rough estimate with very few parameters, without specifying the actual system components. In other words, the numbers at this stage can be used to screen candidate sites or get a sense of direction, but they should not be treated as final values for detailed design.

Beginners tend to assume that the initial numbers shown are the final values. However, in a full-scale PVSyst project design, within the time-step simulation you sequentially add factors such as the orientation of the installation surface, the specific system configuration, thermal behavior, wiring, module quality differences, mismatch, incidence-angle losses, far shading, and near shading. In other words, the differences seen later are not the software's whims but the result of adding conditions that were not included at the initial stage. If you don't understand this, you may feel that "the numbers are different from the beginning" and end up losing confidence in the software.

To avoid failures in practical work, it is important to assign different roles to initial estimated values and detailed design values from the outset. Use estimated values as numbers for comparing options and setting priorities, and detailed design values as numbers for design decisions and explanatory materials—this distinction makes confusion less likely. PVSyst is a powerful software that can also produce estimates, but because estimating is so convenient, overreliance on it can lead to substantial rework later on. The mindset beginners should adopt at first is: “the first numbers are a provisional entry point; in the latter stages, refine the conditions to bring them closer to the true design values.”

Beginner Pitfall 2: Handling Meteorological Data

The second stumbling block is how to handle meteorological data. In PVSyst, geographic conditions and hourly meteorological data lie at the heart of a project. Even in the official general description, the roles of the meteorological database are listed as creating sites, generating hourly data, visualizing data, comparing data, and importing external data. In other words, PVSyst is not software that starts from equipment models; it begins with “where to perform the calculations” and “which meteorological assumptions to adopt.” If you proceed without being conscious of this, no matter how detailed you make the design conditions later, the underlying ambiguity will remain.

What often trips up beginners is thinking, "It probably doesn't matter which weather data I use." In reality, the appearance of the results can change depending on the data's reference year, averaging period, processing method, how climate change is treated, and so on. Even official comparisons of data sources show significant differences among the available meteorological datasets, and it is not easy to determine rigorously which is optimal or how large the errors are. In other words, PVSyst does not automatically provide a universally correct dataset; it is software meant to be used for design with an awareness of differences in meteorological assumptions.

More importantly, PVSyst does not simply use meteorological data for the horizontal plane as-is; it converts it into the solar irradiance that reaches the installation surface. The official simulation procedure explains that it reads meteorological data hour by hour and then determines the global, beam, diffuse, and reflected components on the installation surface. This means the calculations directly address the obvious fact that even within the same region, the light received changes with orientation and tilt. When beginners understand this, they realize that meteorological data are not just regional numbers but only become meaningful once converted into the conditions that reach that surface, and it becomes easier to appreciate the importance of installation-surface conditions.

Beginner Pitfall 3: Considerations for the Installation Surface and System Configuration

The third stumbling block is treating the mounting surface conditions and the system configuration as separate. In PVSyst project design, you first define the orientation of the mounting surface and the tracking conditions, and then select the system components and design the number of modules in series and parallel. The official documentation also explains that project design involves defining the orientation of the mounting surface and designing the PV array’s series–parallel configuration based on the selected system components. In other words, the mounting surface and the configuration are not separate; they are linked within a single design.

Beginners tend to take the approach of “decide the capacity first, then think about the orientation.” However, in reality, if the orientation or tilt changes, the times of day when the array receives sunlight change, and accordingly the operating conditions for modules and power-conversion equipment and the way losses occur also change. If the number of series or parallel strings is configured differently, the input-side voltage conditions and how constraints affect the system also change, so looking only at capacity does not constitute a proper design. What makes PVSyst useful is that it lets you view these conditions together. Not separating capacity from configuration is an intuition beginners should learn early.

Also, PVSyst includes a component database that makes it easy to choose modules and inverters as a starting point. While this is convenient, it is also risky to assume “it’s correct because it’s in the database.” The official documentation for the inverter database states that it cannot guarantee the accuracy of the recorded parameters and strongly recommends carefully cross-checking them against the latest specifications before use. In other words, PVSyst can help you quickly create a design draft, but it does not eliminate the need for verification. For beginners, understanding that convenience and the responsibility to verify are separate will make failures less likely.

Beginner Pitfall 4: How to Include Losses

The fourth stumbling block is how to account for losses. Beginners often assume they can first compute energy production under ideal conditions and then roughly subtract losses at the end as a safety margin. However, PVSyst does not operate on that kind of after-the-fact approach. The official general description states that in the second stage of the detailed design you can specify fine effects such as thermal behavior, wiring, module quality differences, mismatch, angle-of-incidence losses, distant shading, and near shading. In other words, losses are not a final adjustment but a central element of the simulation.

In PVSyst's simulation workflow, after calculating the irradiance incident on the installation surface, it applies nearby shading and optical effects, and then considers array-side thermal effects, mismatch, wiring, and component variations. The important point is that losses are not a single item but an accumulation of many small factors. When a project's results are low, the cause might be the meteorological data, temperature, shading, wiring, or the conversion side. What makes PVSyst useful is that it makes that breakdown easy to follow step by step. Understanding how to input losses also makes it easier to identify points for design improvement.

Furthermore, understanding the concept of the performance ratio makes it easier to organize how you view losses. Officially, the performance ratio is described as broadly including optical losses, array losses, and system losses. In other words, the performance ratio is not just a number for efficiency, but a comprehensive indicator of how much energy is being used while accounting for losses. Beginners do not need to grasp this deeply at first, but simply adopting the sense that "losses are not something to be subtracted all at once afterward, but something treated as part of the design" will significantly change how you use PVSyst.

5 Common Pitfalls for Beginners: How to Read Shadows

The fifth stumbling block is the way shading is viewed. Beginners in solar design tend to think of shading simply as "the proportion of area that is shaded." However, PVSyst's shading-related documentation shows that losses from nearby shading include not only a lack of irradiance but also additional losses due to electrical mismatch. In other words, even a little shading can, depending on the electrical connections, increase losses more than you might expect.

The official module layout feature states that, in order to calculate electrical shading mismatch losses in detail, it is necessary to define the position of each module and which string or input it belongs to. It further explains that detailed electrical loss calculations require the precise placement of each module and which input it is connected to. This means that shading is not merely a spatial issue but also a circuit issue. It may seem difficult for beginners, but it is very important to know, at a minimum, that "shading does not end with area ratios."

Of course, you don't need to create a detailed module layout for every project from the very beginning. Even the official project tutorial recommends making a basic plan first and then progressively adding elements such as distant shading, near shading, and losses. In other words, shading assessment doesn't have to be carried out to the deepest level right away; you can deepen it according to the importance and complexity of the project. What beginners should keep in mind are two instincts: "don't underestimate shading" and "a deeper evaluation is available if necessary." Even just observing these two points will significantly reduce oversights in practical work.

Six Pitfalls Beginners Face: How to Interpret Results

The sixth stumbling block is how to interpret the results. When you use PVSyst for the first time, it's easy to focus solely on the annual energy production figure. However, the official general description states that the results include dozens of simulation variables and can be displayed by month, day, and hour. It also explains that the loss diagram is particularly useful for identifying weaknesses in system design. In other words, PVSyst results should be used not just to see "how many kilowatt‑hours per year" but to track "where and what is happening."

What beginners should first check is the loss diagram. By looking at it, you can immediately see how much of the energy incident on the installation surface is being lost at each stage. It makes it easy to broadly identify whether the cause is solar irradiance conditions, shading, temperature, wiring, or the conversion side. Rather than ending with a simple “high” or “low” judgment based only on the annual energy production, examining the process that leads to that number is the first step to making effective use of PVSyst’s results. In most cases, clues for design improvement are found in these intermediate steps.

Another important metric is the performance ratio. The official documentation explains that the performance ratio is relatively insensitive to a specific site or azimuth and is easy to use as an indicator for comparing system quality. In other words, while annual energy production includes many site-dependent differences, the performance ratio makes it easier to see the system’s overall coherence. This may seem somewhat abstract to beginners, but simply knowing that “a larger energy yield” and “better design quality” are not necessarily the same will significantly change how you interpret the results. Rather than taking PVSyst’s numbers at face value, make a habit of reading the loss diagram together with the performance ratio — doing so will deepen your understanding of the design.

Beginner Pitfall 7: When to Use Performance Comparisons

The seventh stumbling block is knowing when to use the performance-comparison feature. Many beginners think of PVSyst only as "pre-design prediction software." However, in the official description of measured-data analysis, this feature is presented as a means to closely compare on-site measured data with simulation values on an hourly or daily basis, and at the same time as a powerful tool that makes it easier to detect even small anomalies in systems in operation. In other words, PVSyst is not software that ends with prediction; it is also software that links predictions and actual performance.

Where beginners get stuck is in taking the simplistic view that "if the results differ, it's wrong." In reality, the difference between prediction and actual performance becomes an entry point to consider whether it was due to differing weather conditions, lax loss settings, insufficient shading evaluation, or equipment malfunction. Even official documentation explains that comparison functions not only help validate the software but can also be used for operational analysis of real systems and for detecting faults. In other words, more important than the mere existence of a difference is how you interpret that difference.

From a practical perspective, this is where PVSyst delivers very significant value. Because you can review the design assumptions and the realities observed after operation in the same context, it becomes easier to feed insights back into the next project. If you can reflect what you noticed at one site in the next loss settings, shading assessment, and configuration considerations, the quality of design will gradually improve. If beginners understand from the start that "PVSyst is not a tool you use once and finish with, but a tool that cultivates design quality," their perspective after implementation will change significantly.

Summary

PVSyst is design software that can handle photovoltaic power generation planning in a single workflow—from site, weather, mounting surface, equipment configuration, losses, and shading to result analysis and performance comparison. What beginners tend to stumble on first is confusing preliminary estimates with detailed design, taking meteorological data lightly, thinking of the mounting surface and configuration separately, trying to treat losses as an afterthought, considering shading only by area ratio, reading results only by annual energy yield, and using performance comparisons solely to judge forecast deviations. By understanding these points in advance, PVSyst becomes easier to view not as "difficult software" but as "software that organizes the design workflow."

In practice, the value of PVSyst is not simply that it produces numbers. Its value lies in clarifying assumptions, comparing differences in conditions, identifying weaknesses, and feeding improvements back into the next design. For this reason, the more you use PVSyst as a tool to connect design and verification rather than as a black box, the more you will feel its impact. Especially for first-time users, rather than trying to understand everything at once, it is recommended to deepen your understanding little by little while keeping in mind the common pitfalls raised in this article.

The more carefully you perform desk-based power output forecasting and shading assessments, the more important the accuracy of on-site position information and equipment placement becomes. Even if you finely tune design conditions in PVSyst, if on-site positioning and obstacle identification are vague, discrepancies between design assumptions and construction reality tend to grow. That is why organizing desk-based conditions with PVSyst at the design stage and combining that with iPhone-mounted high-precision GNSS positioning devices like LRTK during the field stage makes it easier to link design, construction, and maintenance consistently. The idea of keeping design integrity with PVSyst and aligning on-site positional accuracy with LRTK is well suited to improving reproducibility across the entire solar workflow.