What is PVSyst? Basic knowledge to avoid failure in solar PV design

Table of Contents

• What PVSyst Is

• Fundamental Knowledge 1 Do not confuse rough estimates with detailed design

• Fundamental Knowledge 2 Meteorological data forms the basis of design

• Fundamental Knowledge 3 Consider installation conditions and system configuration together

• Fundamental Knowledge 4 Accumulate time-resolved results using physical models

• Fundamental Knowledge 5 Include losses in the design from the start, not as an afterthought

• Fundamental Knowledge 6 Evaluate shading by its electrical impact rather than by area fraction

• Fundamental Knowledge 7 Interpret results using loss diagrams and the performance ratio

• Fundamental Knowledge 8 Databases are useful but do not take them at face value

• How to use it in practice without making mistakes

• Summary

What is PVSyst?

PVSyst is dedicated software for studying photovoltaic power systems, performing system sizing, evaluating performance, and analyzing data. In the official documentation, it is presented as an environment that covers not only grid-connected systems but also stand-alone systems, pumping applications, and DC-system applications, and is described as a practical design platform equipped with a meteorological database, an equipment database, and functions for comparing measured data. In other words, PVSyst is not merely a power generation calculation tool; understanding it as software for organizing design conditions and verifying which assumptions produced which results makes it easier to grasp the overall picture.

When a practitioner searches for "What is PVSyst", what they really want to know is, I think, not the origin of the name but where it is useful and where it tends to trip people up. At the core of PVSyst is the concept of holding site information and time-series meteorological data within a project framework and comparing multiple simulation conditions within it. Because you can line up and evaluate proposals that change the orientation of the installation surface, equipment configuration, loss assumptions, and shading conditions, it is characterized by making it easier to explain design decisions rather than merely producing numbers. To avoid failures in solar PV design, it is important to understand this "refining while comparing" philosophy from the outset.

Basic Knowledge 1: Do not confuse rough estimates with detailed design

The first thing to grasp when using PVSyst is that the functions for preliminary estimates and those for detailed design serve different roles. The official documentation explains that preliminary design is the stage for determining a project's preliminary sizing and is a mechanism to quickly perform month-by-month evaluations using only a very small number of general conditions. By contrast, project design is the functionality for full-scale design and performance analysis using detailed time-step simulations. Using the software without understanding this difference can lead you to treat coarse estimates as if they were definitive values, making it easy to arrive at incorrect design decisions.

In practice, what you need in the early planning stage is to quickly grasp whether a candidate site is likely to be viable and whether the general orientation of the installation surface is reasonable. At that stage, preliminary design is extremely useful, but the figures obtained there are only for early decision-making. The official help also states that preliminary design provides a rough estimate of power generation and should not be used for detailed design; more precise results should be obtained through detailed time-step simulations. To avoid design failures, it is important to treat the initial figures as numbers to move the conversation forward and the later figures as numbers to bring the design closer to finalization.

Basic Knowledge 2: Weather Data as the Foundation of Design

In solar design, the most fundamental consideration is the site's meteorological conditions, even before the equipment itself. In PVSyst's official description, a project is defined as a framework that includes geographic conditions and time-series meteorological data. In other words, PVSyst's calculations do not begin with the selection of equipment models but with deciding which location and which meteorological assumptions to adopt. If solar irradiance conditions are left ambiguous, no matter how precisely you design afterward, the credibility of the results will not increase.

PVSyst also supports workflows that encompass importing, comparing, and verifying the quality of meteorological data. It can import external data and also includes quality-checking functions for custom meteorological files, providing an approach that lets you use data while assessing its validity. This means power generation forecasting is treated not merely as a computational process but as a design task that includes the quality of the input data. Beginners often focus on equipment parameters, but to avoid mistakes in practical work it is essential to first understand that the selection and handling of meteorological data can determine the results.

More importantly, PVSyst does not use meteorological data on the horizontal plane as-is; it converts it into incident irradiance according to the orientation and tilt of the installation surface. In the official physical model, solar position and incident irradiance models are the basis, and evaluations then proceed for each sub-array. In other words, even at the same location, changing azimuth or tilt alters both the amount of irradiance received and the times at which it is received. To avoid design failures, it is important to understand that meteorological data only become meaningful once they have been converted from “the average conditions at that location” to “the conditions the installation surface actually receives.”

Basic Knowledge 3: Consider Installation Conditions and Equipment Configuration Together

PVSyst is easy for designers to use because it treats installation conditions and equipment configuration not as separate items but as a single integrated entity. The official documentation presents a workflow in which, during project design, the orientation of the mounting surface, whether tracking is used, and the conditions for racked installations are defined, and then equipment is selected and the number of modules in series and in parallel is designed. In other words, rather than simply entering system capacity and checking the energy yield, you can evaluate how that capacity will actually be realized in terms of configuration.

In practice, even with the same nominal output, results can vary greatly depending on how the system is configured. If orientation or tilt differ, the daytime output curve changes, and differences in the number of series or parallel strings also affect the input-side voltage conditions and the operating range of the power conversion equipment. PVSyst lets you handle these conditions together within a single project rather than separately, so you can move beyond simply asking “how many kilowatts to install” and address the more essential design question of “whether the system will operate without issues.” To avoid design failures, you must always consider not only the size of the capacity but also the consistency of the configuration.

Fundamentals 4: Accumulating Results Over Time with a Physical Model

PVSyst's calculations are not a simple multiplication of coefficients. In the official list of physical models, solar position, incident irradiance models, photovoltaic modules, power conversion equipment, batteries, pumps, and so on are organized as the main models. In other words, it is an approach that builds up, in chronological order, where the light comes from, how it reaches the installation surface, how the modules convert it into electricity, and how it is routed through conversion equipment to the output. Because of this structure, it is easier to explain why the results are what they are.

For solar photovoltaic modules, a single-diode model is adopted. The official documentation describes the approach of generalizing the model used for a single cell to the entire module, and advocates adopting the single-diode model—taking into account input accuracy and internal mismatch—rather than more complex methods such as the two-diode model. Furthermore, not only the basic specification values but also additional parameters that are usually not fully documented in datasheets, such as series resistance and shunt (parallel) resistance, are involved. This makes it easier to reproduce behavior under low irradiance and during temperature changes that is closer to reality.

The conversion equipment is also not treated as a box with constant efficiency. According to the official documentation, the input side is subject to voltage and current constraints, and evaluations include the effects of maximum power point tracking conditions and output limitations. Furthermore, efficiency is treated as something that can vary depending on load conditions and input voltage. In other words, the energy obtained on the DC side does not necessarily appear on the AC side in the same amount. The reason PVSyst is supported in design practice is that it connects these real equipment behaviors within time-based simulations.

Basic Knowledge 5: Incorporate losses into the design from the start, not as an afterthought

One common mistake in solar PV design is to first produce large figures under ideal conditions and then subtract losses all at once, as if applying a safety factor. PVSyst does the opposite: it integrates losses into the design from the outset. The official documentation says that detailed effects such as thermal behavior, wiring, module quality, mismatch, incidence-angle loss, far shading, and near shading can be specified in a second stage, and the results include numerous variables and loss diagrams. In other words, the philosophy is that losses should be treated as part of the design conditions themselves, not as a final adjustment.

Even in its actual calculation process, PVSyst sequentially evaluates array temperature, low-irradiance losses, temperature losses, electrical mismatch caused by shading, module quality differences and other mismatches, wiring losses, and so on, and from those results determines the energy available at the array. After that, the actual usable energy is determined by the constraints of the power conversion equipment and the overall system conditions. What is important for designers to understand is that a reduction in energy yield is not caused by a single factor but by the accumulation of multiple losses. If this is not understood, efforts to improve the design will be misdirected.

Basic Knowledge 6: Consider shadows in terms of electrical effects rather than area ratios

Underestimating the impact of shading is another common pitfall in solar design. Even shadows that look small can cause electrical losses greater than expected. Official module layout documentation indicates that partial shading losses include not only a reduction in irradiance but also electrical mismatch effects. In particular, when multiple strings are connected in parallel to the same input, a partially shaded string can affect the operating point of the whole system and cause losses to increase sharply. In other words, shading cannot be fully assessed solely by “what percentage is shaded.”

Furthermore, the official guidance explains that bypass diodes and submodule configuration have a major influence on electrical shading losses. Submodules are the basic unit for considering electrical shading, and the results change depending on where the shadow falls and which string and input it is connected to. This means it is risky to simply approximate shadows in bulk during the design phase. PVSyst is useful because it can evaluate shading step by step, not merely as an area ratio but including the electrical effects.

For beginners, simply distinguishing between far-field and near-field shading is already worthwhile. From there, for projects where row spacing or the influence of surrounding obstructions is likely to be significant, you should proceed to a more detailed shading assessment. You don't need to delve into the deepest details right away, but you should avoid the notion that "shading can simply be accounted for by reducing area proportionally." To avoid failures in solar PV design, it's important to assess shading from both spatial and electrical perspectives.

Basic Knowledge 7: Interpreting Results with Loss Plots and Performance Ratios

When looking at PVSyst results, judging solely by the annual energy production is a wasteful way to use it. On the official loss diagram page, the loss diagram is described as a chart for quickly assessing the quality of a system design and identifying the main sources of loss. Moreover, because it can be viewed not only annually but also by month, it becomes easier to track which losses are affecting performance in each season. To avoid design failures, it is essential to first look at this loss diagram and understand where energy is being lost.

Performance ratio is also an important indicator for interpreting results. According to the official definition, the performance ratio includes optical losses such as shading, angle-of-incidence losses, and soiling, in addition to module conversion, degradation over time, quality differences, mismatch, wiring, and system-side losses. In other words, the performance ratio is a comprehensive indicator to see "how cleanly the system is operating." Total energy production alone is confounded by differences in site conditions, but when you look at the performance ratio as well, it becomes easier to compare design proposals and operating conditions.

When reading results, don't stop at annual values; looking at monthly and hourly changes makes it easier to spot design weaknesses. The official documentation also states that results include numerous simulation variables and can be displayed or output by month, day, and hour. For example, if performance drops dramatically only in summer, suspect temperature or ventilation conditions; if it only performs poorly in the mornings and evenings, consider reviewing orientation or shading. To avoid design failures, it's important to read results not as a single annual value but as a set of information for investigating causes.

Basic Knowledge 8: Databases are useful but don't take them at face value

PVSyst has an equipment database, which is very useful even for beginners. The database for power conversion equipment contains a large number of devices, and new definitions can be created based on similar devices as needed. In other words, even if you do not have all the configuration information on hand, you can easily begin design studies using a standard workflow. For beginners in photovoltaic design, this ease of getting started is a major advantage.

However, being convenient and being unconditionally correct are different things. The official conversion equipment database documentation states that the database parameters cannot be guaranteed, and since transcription errors or specification changes are possible, we strongly recommend that you carefully cross-check against the latest datasheets when actually using it. Furthermore, the single-diode model of photovoltaic modules involves additional parameters that are not usually listed in datasheets. In other words, the PVSyst database is a powerful aid for advancing a design quickly, but it does not assume responsibility for the final verification.

If you don’t understand this point, you may proceed with the design under the assumption that “it’s okay because it was in the database,” only to notice differences in specifications or assumptions later. To avoid failures in solar PV design, it’s important to use PVSyst’s database as a starting point and to always confirm details with the project side at the end. Adopting this attitude from the beginning as a beginner will help stabilize both the accuracy of your designs and your ability to explain them.

How to Use Without Failing in Practical Work

With the foundational knowledge covered so far, the practical use of PVSyst becomes quite clear. First, grasp the overall picture during the preliminary design phase; once the project advances, move on to project design and sequentially refine the installation surface, equipment configuration, losses, and shading conditions. The official tutorial also illustrates a workflow where you create an initial simulation under very basic conditions and then progressively add distant shading, near shading, and various losses. Rather than aiming for perfection from the outset, starting with a rough proposal and improving accuracy better matches both PVSyst’s philosophy and real-world practice.

Next, it is essential to always interpret results in a comparative context. Instead of judging solely by the numbers from a single scenario, create alternative cases such as different orientations, different loss conditions, and different shading conditions, and use loss diagrams and performance ratios to verify where the differences originate. PVSyst is designed to allow comparison of multiple simulation runs within a project, so it would be a waste not to use it. To avoid design failures, you should not treat the process as “calculate once and be done,” but rather adopt the approach of “seeking a reasonable solution while observing differences in conditions.”

Finally, having a system in place to review post‑operation performance further increases the value of PVSyst. The official software provides features to import measured data and make close comparisons with simulations to analyze actual system behavior and small anomalies. If design and operation are not separated and you can learn from the differences between forecasts and actual performance, it becomes easier to improve loss assumptions and the accuracy of baseline conditions for the next project. Rather than using PVSyst merely as pre‑installation calculation software, you are less likely to fail if you use it as a practical platform that connects design through improvement.

Summary

PVSyst is specialized software that organizes the prerequisites needed for photovoltaic system design into a single workflow, linking energy yield prediction with design decisions. Basic knowledge to avoid failure includes not confusing preliminary estimates with detailed design, treating meteorological data as the foundation, considering site conditions and equipment configuration together, building up time-step results with a physical model, including losses in the design from the start, considering shading including its electrical effects, interpreting the results using loss diagrams and the performance ratio, and not blindly trusting databases. Simply grasping these points will significantly change how you view PVSyst.

And the more you improve desk-based design accuracy, the more important on-site location information and equipment placement accuracy become. Even if you carefully refine the installation surface orientation and shading conditions in PVSyst, if on-site positioning or obstacle identification is vague, a gap will form between desk assumptions and reality. That is precisely why, in the design phase, organizing energy production forecasts and loss structures in PVSyst, and in the field combining an iPhone-mounted, high-precision GNSS positioning device such as LRTK, makes it easier to seamlessly connect design, construction, and operation & maintenance. Correctly understanding PVSyst is not only essential to avoid design failures but also the first step in creating a high-precision workflow that includes the site.