What is PVSyst? A comprehensive explanation of why it is widely used in the solar industry

Table of Contents

• What is PVSyst

• Reason 1: You can view the entire design, not just energy production

• Reason 2: Enables discussion starting from meteorological data

• Reason 3: Connects initial estimates through to detailed design

• Reason 4: Allows simultaneous refinement of the installation surface and equipment configuration

• Reason 5: Losses can be decomposed and analyzed

• Reason 6: Allows in-depth evaluation of shading

• Reason 7: Extends to comparison, economic assessment, and validation with measured data

• Things to know before adopting it

• Summary

What is PVSyst?

PVSyst is specialized software for studying photovoltaic (PV) systems, sizing capacity, performance evaluation, and data analysis. The official documentation describes it as an environment that handles not only grid-connected systems but also stand-alone systems, pumping applications, and DC-system applications, and it is presented as a fairly comprehensive practical tool equipped with a weather database, a component database, various tools, and functions for comparing measured data. In other words, PVSyst is not merely a one-time calculator for annual energy production; understanding it as a foundation that consolidates and organizes project assumptions while numerically supporting design decisions makes the overall picture easier to grasp.

To put it simply, the reason it is commonly used in the solar industry is that you can trace not only the power generation figures but also the conditions that produced those figures. In official project design, detailed hourly simulations are performed, and it is explained that multiple simulation runs for the same project can be compared. In other words, PVSyst is not "software that returns a single answer" but also "software that organizes conditions, compares options, and identifies weaknesses." The fact that practitioners can easily explain the rationale behind their designs is part of the reason it is so widely used.

Also, PVSyst has a structure that makes it easy to adapt to the way a project progresses. In the initial stage it can quickly produce monthly estimates with a small number of conditions, and in the full-scale stage the official workflow is organized as a two-pronged approach that tightens up losses and shading with hourly simulations. The fact that it fits readily into the practical workflow of planning, basic design, detailed design, and verification is another reason it is widely adopted.

Reason 1: You can view the overall design, not just the power output

The primary reason PVSyst is widely used is that it isn’t merely software that outputs energy production; it’s software that allows you to view the entire design. In the official overview, PVsyst 8.1 is described as software for the study, sizing and data analysis of complete photovoltaic systems, and is said to be suitable for architects, engineers, researchers, and educational use. Furthermore, the detailed design items include orientation settings, system definition, losses, shading, results, economic evaluation, and P50/P90 assessments. In other words, it is assumed that the entire process—from the early to the late stages of design—can be followed within a single environment.

In solar projects, there are surprisingly few situations where you can make a judgment based solely on "how many kilowatt-hours will be produced." Questions such as why that number is reached, what happens if you change the orientation or tilt, where shading and temperature effects take effect, and even how the economics look inevitably arise. PVSyst lets you handle these issues without separating them from the energy production calculation results, making it easier to view the overall design as a single flow. What makes it valuable in practice is not so much that it has many features, but that it makes it harder to fragment the design conversation.

This sense of being able to "see the whole design" is something that practical professionals tend to value more than beginners. Beginners initially pay attention to the power generation figures themselves, but when using the tool professionally, accountability for the numbers and the ease of comparative evaluation become important. Because PVSyst can hold different system variants within a project, it is easy to proceed with the design while preserving differences in conditions, and the workflow remains easy to follow when you review it later. Being usable throughout the entire design process is a major reason it is chosen in the solar industry.

Reason 2: Discussions can start from meteorological data

The second reason is that it allows discussions to start from meteorological data. PVSyst's official documentation states that the fundamentals of a project are the geographic conditions and time-based meteorological data, and that its meteorological database can create geographic sites, generate time-based data, visualize and compare meteorological data, and import external files. In other words, the approach built into the software is to begin design not from equipment specifications but from "what kind of solar irradiation conditions are present at that location." This sequence is very important in solar design.

One reason it is widely used in the industry is that it is highly practical. Even with the same system capacity, power generation and seasonal variability can differ greatly depending on location, and even at the same location the results can vary depending on the meteorological data’s reference years, averaging periods, and processing methods used. The official meteorological data comparison page also explains that there are significant differences among the available data sources and that it is not easy to determine precisely which is optimal for a given project. PVSyst’s strength is that it does not treat those differences as invisible or ignore them, but rather handles them as comparable options.

More importantly, PVSyst does not use horizontal-plane meteorological data directly as the final result. The official simulation workflow explains that it reads hourly meteorological data and then calculates the global, beam, diffuse, and reflected components on the installation surface. In other words, regional meteorological data do not directly represent the generation conditions of the system; they only become meaningful once the program calculates “how light reaches that surface.” The ability to start from meteorological conditions and relate them to the installation-surface conditions for discussion is a major strength of PVSyst.

Reason 3: Connects initial estimates to detailed design

The third reason is that the same way of thinking connects initial estimates to detailed design. In PVSyst’s official overview, preliminary design is described as a pre-sizing step carried out very quickly in monthly values, allowing a rough estimate with only a few general conditions. On the other hand, project design is described as a thorough system design using detailed hourly simulations, the full-scale phase in which more granular conditions are worked out. In other words, PVSyst contains both the coarse-look stage and the deep-look stage within a single software.

In practice, this becomes a very significant advantage. It is rare for all conditions to be decided from the start; often a study begins with a candidate site but undecided equipment, or with the capacity range visible but the layout still to be determined. If only tools dedicated to detailed design are available at that stage, the input burden becomes large and discussions are more likely to stall. With PVSyst, you can first grasp the direction with only a few conditions, and as the project progresses it is easy to move straight into detailed simulation, so the flow of evaluation is less likely to be interrupted.

Also, the official preliminary design page explicitly states that the results at this stage are rough estimates and should not be used for detailed design, and that more precise results should be obtained from time-based simulations. This is a point of caution, but conversely it means the roles of "rough estimate" and "detailed design" are clearly delineated. First grasp the overall picture, then refine the design. Because this two-stage approach is organized officially, it is easy to adopt for both beginners and practitioners.

Reason 4: You can finalize the installation site and equipment configuration at the same time

The fourth reason is that you can refine the mounting surface and the equipment configuration simultaneously. In PVSyst’s project design, it is explained that you first define the orientation of the mounting surface and the tracking conditions, and then select specific components and design the number of series and parallel strings of the array. This means it is software that treats “in which orientation and with what configuration to mount” as an integrated whole, not just software that looks at “how many kilowatts to install.” In solar design, this integration is very important.

Even with the same nominal output, differences in orientation or tilt change the times of day when sunlight is received, and differences in series/parallel arrangements change the input-side voltage conditions and how conversion-side constraints are experienced. In other words, installed capacity alone does not amount to a true design. PVSyst proceeds without separating the definition of the mounting surface from the definition of the equipment configuration, making it easier to reduce design oversights such as “this capacity looks fine, but this configuration is impractical.” The ease of verifying consistency including these configuration details is why it is used in the industry.

Furthermore, the official components database includes modules, power conversion equipment, batteries, pumps, and other items, and is structured so you can easily select components suitable for a project while managing manufacturers and components. Of course, there is a caveat that the recorded data should not be taken at face value and should be cross-checked with the latest information, but even so it is a significant advantage for speeding up initial design. Being able to finalize installation layout and system configuration simultaneously is one reason PVSyst is recognized as a "design" tool rather than merely a "calculation" tool.

Reason 5: The loss can be decomposed and inspected

The fifth reason is that it can break down and interpret losses. According to PVSyst’s official description, in the second stage of detailed design you can analyze subtle effects such as thermal behavior, wiring, module quality differences, mismatch, angle-of-incidence losses, distant shading, and nearby shading. The results also include dozens of simulation variables and can be displayed by month, day, or hour. In other words, PVSyst is not just software for viewing total energy production; it is also a tool for tracking “where and by how much” generation was reduced.

Particularly valued in the industry is the loss diagram. On the official loss diagram page, the loss diagram is described as a chart for quickly assessing the quality of a PV system design and identifying the main sources of loss, and it can be viewed not only annually but also by month. This makes it easier to distinguish whether the solar irradiance conditions themselves are poor, whether temperature or shading are the dominant factors, or whether the wiring or conversion side is weak. Discussions about design improvements are easier because losses can be read as a breakdown rather than as a single aggregated value.

Also, the performance ratio metric is deeply related to why PVSyst is chosen. According to the official definition, the performance ratio is the ratio of the energy actually available for useful use to the theoretical amount derived from the irradiation on the plane of the installation and the nominal power, and it is described as broadly including optical losses, array losses, and system losses. Annual energy yield alone is heavily influenced by site differences, but by looking at the performance ratio, it becomes easier to see from another angle how cleanly the system is operating. PVSyst’s strength is that it makes it easier to discern a well‑integrated design rather than simply “high output.”

Reason 6: Can evaluate shadows in depth

The sixth reason is its ability to evaluate shading in depth. In PVSyst's description of shading, it distinguishes two fundamentally different types of shadings: far-field shading and near-field shading. Far-field shading is represented by the horizon line and affects the entire PV field uniformly, whereas near-field shading is caused by nearby objects casting visible shadows and is said to require a complete, detailed 3D description of the surrounding environment. In other words, it embodies from the outset a design philosophy that does not make do with representing shading by a single rough coefficient.

Furthermore, PVSyst considers not only the shading's "linear deficit" but also the "electrical shading loss." In the official terminology, electrical shading loss is described as the additional loss obtained by subtracting the linear component due to reduced irradiance from the actual shading loss; it occurs because partial shading of cells or modules disturbs the I-V characteristics and limits the string current. This means that even a shadow that looks small can become an electrically much larger loss than it appears. PVSyst is valued in the industry because it confronts this practical difficulty head-on.

Regarding near shading, you can define the surrounding environment in 3D and, if necessary, set the module layout to calculate electrical shading losses in greater detail. Of course, you don't need to go that far for every project, but the deeper level of modeling makes a difference for projects where shading has a large impact. The ability to go beyond a simple area-based estimate of shading and perform a more detailed design is one reason PVSyst is commonly used in the solar industry. The practical value—making shading assessments less prone to error and thereby reducing the risk of failure—is substantial.

Reason 7: Enables comparison, economic evaluation, and empirical validation

The seventh reason is that it connects through to comparison, economic evaluation, and verification against actual measurements. PVSyst’s official description states that different simulation runs within the same project can be compared, and furthermore, for economic evaluation, initial installation costs, annual operating costs, financing conditions, and tariff conditions can be used to estimate LCOE, long-term profitability, ROI, payback period, NPV, and so on. In other words, it can handle not only technical comparisons of design proposals but also how those proposals appear as business cases in a single workflow.

In solar PV projects, a proposal with a higher energy yield is not necessarily the optimal option. Increasing the yield slightly can complicate the equipment configuration and construction conditions, making the project disadvantageous overall. Because PVSyst treats performance evaluation and economic evaluation side by side, designers can more easily consider both "technically good proposals" and "commercially good proposals." This is a strength that simple energy-yield calculation software does not have, and one reason it has enjoyed long-standing support in the industry.

Additionally, it has a measured-data analysis function. According to the official documentation, it can import measured data from almost any ASCII format, display actual performance in tables and graphs, and perform close comparisons with simulation variables. And its purpose is not only to validate the software, but also to analyze the operation of real systems and detect small anomalies. In other words, PVSyst is not only prediction software for pre-installation, but also improvement software after installation. The ability to link predictions and actual results and learn from them is why its value increases the longer it is used.

Important Points to Know Before Implementation

At this point, PVSyst may look extremely convenient and versatile. However, there are caveats you should know before adopting it. First, PVSyst is software that strongly depends on its assumptions. If meteorological data, mounting surfaces, shading conditions, loss settings, and component data are not well aligned, no matter how impressive the results appear, their reliability for design decisions will not improve. Even on the official weather data comparison page, there are large differences between data sources, and determining which is optimal is not straightforward. In other words, it is important to understand that PVSyst is not "software that automatically gives you the correct answer," but "software that methodically calculates based on the assumptions you set."

Secondly, the component database is convenient, but you should not take it at face value. The official module model description notes that the single-diode model involves additional parameters that cannot be determined from the datasheet alone, and the overview page also explains that the component database covers a broad range. In other words, PVSyst is useful for creating a preliminary design, but it does not assume responsibility for the final verification of specifications. You should not be reassured simply because a database exists; rather, view the database as something that makes the verification work easier.

Third, while PVSyst is strong for design and assessment, it is not software that replaces site surveys or construction management themselves. Detailed evaluation of near shading and precise calculation of electrical shading losses require 3D definitions of the surrounding environment and the interconnection relationships of the modules. In other words, the accuracy of desk-based simulations is supported by the accuracy of information obtained on site. No matter how detailed the simulations are, if the understanding of on-site spatial relationships and obstacles is vague, discrepancies between design assumptions and reality will remain. When implementing it, it is important not to consider the software alone but to treat it as part of a system that includes on-site verification.

Summary

Summarizing why PVSyst is widely used in the solar industry: it allows you to view the entire design, not just energy output; enables discussions grounded in meteorological data; connects initial estimates to detailed design; lets you refine the installation layout and equipment configuration simultaneously; allows losses to be broken down and interpreted; can evaluate shading in depth; and handles the whole workflow from comparison and economic evaluation to validation with measured data. In short, PVSyst is not “software that simply produces a single annual energy production number,” but “software that organizes design assumptions, enables comparisons, identifies weaknesses, and leads to improvements.”

For practitioners, what is truly valuable is not the mere generation of numbers, but that it makes it easy to provide reasons for those numbers. Because you can organize which weather conditions were used, what orientation it was placed in, what configuration was chosen, which losses were effective, and how it differs compared with alternative proposals, internal and customer explanations become easier. On the other hand, because the quality of the assumptions and the precision of site information strongly influence the results, when adopting it you should not think "we're safe because it's highly capable," but rather "precisely because it's highly capable, it's necessary to handle the assumptions carefully."

The more thoroughly power generation forecasts and shading assessments are carried out at the desk, the more important the accuracy of on-site positional information and equipment layout becomes. Even if design conditions are refined in PVSyst, if site positioning and obstacle identification are ambiguous, discrepancies between design assumptions and construction realities tend to grow. Therefore, organizing power generation and loss structures in PVSyst during the design phase and combining that with an iPhone-mounted, high-precision GNSS positioning device such as LRTK during the site phase makes it easier to connect design, construction, and maintenance more consistently. The idea of improving desk-based accuracy with PVSyst and aligning on-site positional accuracy with LRTK is well suited to enhancing the reproducibility of photovoltaic operations as a whole.