What does PVSyst do? Explaining its uses in six categories

Table of Contents

• What is PVSyst?

• Use case 1: Preliminary estimates in the early planning stage

• Use case 2: Detailed energy production simulation

• Use case 3: Verification of equipment configuration and capacity design

• Use case 4: Analysis of shading and losses

• Use case 5: Comparison of multiple options and project feasibility evaluation

• Use case 6: Comparison with measured data and improvement

• Points to note when using PVSyst

• Summary

What is PVSyst?

PVSyst is dedicated software for the study, capacity sizing, performance evaluation, and data analysis of photovoltaic power generation systems. According to the official documentation, it is presented as software that handles not only grid-connected systems but also stand-alone systems, pumping applications, and DC-system applications, and is described as an environment equipped with a meteorological database, an equipment database, various solar energy–related tools, and even comparison functions using measured data. In other words, PVSyst is not merely a quick reference table for energy production; understanding it as a practical tool that consolidates the assumptions required for solar projects while supporting design decisions with quantitative evidence makes its true nature easier to grasp.

What practitioners who search for "What is PVSyst" really want to know is not the meaning of the name but what the software does, where it is useful, and how much it can be trusted. From that perspective, PVSyst's characteristic is not that it automatically returns a single answer, but that it can handle—from location, weather, mounting surface, equipment configuration, losses, and shading to comparisons with actual performance—within a single design flow. The official overview also makes clear that, in the early stage, it can quickly produce rough estimates with few conditions, and in the full-scale stage it can perform detailed design with hourly simulations, providing a structure that allows results to be compared and analyzed. This means it is not only calculation software but also a working platform for organizing, comparing, and validating design conditions.

In the field of solar design, there are many situations where you cannot judge things simply by "how many kilowatt‑hours per year." Just a slight difference in the orientation of the installation surface can change the results, and results also vary depending on equipment configuration, shading conditions, wiring, and how temperature is handled. For that reason, in actual practice it is important not only to present the final numbers but also to be able to explain under which conditions those numbers were produced. In that respect, PVSyst can be said to be not merely a calculation tool but software for building up the rationale behind a design. In this article, we organize its roles into six categories from the perspective of "uses" and explain them so that design engineers can more easily grasp when to use it.

Use Case 1 Preliminary rough estimates in the early planning stage

A major initial use of PVSyst is rough preliminary assessment in the early planning stage. In the official pre-design function, this is intended to use only a very small number of general conditions to quickly estimate power generation on a monthly basis. Here, without specifying actual specific equipment in detail, you can create a rough outlook from basic conditions such as available area, the orientation of the installation surface, and the required capacity range. PVSyst is quite easy to use when you want to quickly determine at the project startup stage whether “this plan is likely to be feasible in broad terms.”

In practice, it is rare for all conditions to be decided from the outset. There may be candidate sites while the final layout is undecided, or the capacity is roughly known but the equipment configuration is yet to be determined; such situations are not uncommon. In those cases, jumping straight into a detailed time-step simulation can slow initial decision-making because there are too many input items. What makes PVSyst preliminary design useful is that it allows you to grasp the overall direction from limited information. For example, it is perfectly practical for purposes such as roughly comparing candidate sites, understanding major differences in azimuth or tilt, and deciding what to investigate in detail next.

However, the most important point here is not to assume that the preliminary estimates are the figures for detailed design. The official documentation clearly states that pre-design is a rough estimate of energy production and should not be used for detailed system design, that the expected accuracy should be assumed to have a spread of roughly 10% or more, and that more precise results should be obtained through time-step simulation. In other words, PVSyst’s pre-design is a tool to move an investigation forward, not to make final decisions. Confusing the two leads to treating early-stage numbers as definitive and causes major rework later.

To avoid failures in practical design work, the correct approach is to use PVSyst’s preliminary design as an "entry point to quickly grasp the overall picture." First, view the overall picture under a small number of conditions to understand feasibility and the priorities for further study. Then, when the project progresses, switch to detailed design. Understanding this two-stage approach makes PVSyst feel less like a difficult piece of software and makes it easier to fit into your workflow. Being able to work quickly in the early stages and more deeply in the later stages is itself one of PVSyst’s major uses.

Use Case 2 Detailed Power Generation Simulation

PVSyst's primary purpose is detailed energy yield simulation. In official project design, it is described that detailed time-step simulations are used to perform the design and performance analysis of photovoltaic systems. Within a project it holds site location information and meteorological data, and performs calculations while defining the orientation of the installation surface, system configuration, loss conditions, shading conditions, and so on. This allows the results to be read not simply as a total annual energy production but as an accumulation of the contributing conditions.

In photovoltaic power generation, results can vary greatly even with the same installed capacity. If the location differs, solar irradiance conditions change, and even at the same location, different orientation and tilt change the amount and timing of incident sunlight. Furthermore, when temperature conditions, wind conditions, equipment configuration, and loss settings are added, the generated energy is not determined by a simple proportion. PVSyst is used in detailed design because it can link and evaluate these multiple factors over time. The official documentation also shows that the results include many simulation variables and can be displayed by month, by day, and by hour. This is a major advantage for designers who want to explain the background of the results.

Also, PVSyst’s calculations are supported by physical models. In the official list of physical models, solar position, incident solar irradiance models, photovoltaic modules, conversion equipment, batteries, pumps, and so on are organized as the main models. In other words, PVSyst is not merely a collection of empirical rules, but is structured to follow in sequence “where the light comes from,” “how that light enters the mounting surface,” “how the module converts it to electricity,” and “how it becomes usable energy through the conversion equipment.” Detailed simulations are useful because when conditions change, they make it easier to understand where and how differences arise.

A common misunderstanding among beginners is to view detailed simulation solely as a function to produce a more accurate annual energy yield. Of course improving accuracy is a major objective, but even more important is that it lets you see the intermediate results. For example, if a proposal produces lower-than-expected results, it becomes easier to determine whether the issue is seasonal variation, temperature, or shading. PVSyst's detailed simulation is not only a function for producing a single result but also a tool for finding weaknesses in a design.

Purpose 3: Verification of equipment configuration and capacity design

The third use of PVSyst is to verify equipment configuration and capacity design. The official documentation states that within project design you can define the orientation of the installation surface, select the components that make up the system, and design the number of modules in series and in parallel. In other words, it is not simply software for seeing "how many kilowatts to install," but a tool that lets you consider "how to realize that capacity." In photovoltaic design, if you chase only energy production while leaving this aspect vague, you may choose a proposal that looks good on paper but is impractical as an actual configuration.

In practical design work, even with the same nominal output, the behavior varies depending on how the system is configured. Whether you size the system to match the available installation area or to meet the desired capacity, how many modules are placed in series or parallel, whether the input-side voltage conditions are feasible, and whether the operating range of the conversion equipment is matched—these factors affect not only the energy yield but also the feasibility of the installation. PVSyst’s system definition treats such configuration conditions as part of the design, making it easier to evaluate not just the capacity size but also the validity of the configuration. One reason designers favor PVSyst is its ability to provide this energy-yield assessment that takes configuration into account.

PVSyst includes an equipment database that makes it easy to create a draft using photovoltaic modules, inverters, and the like. The official documentation explains that the module database contains numerous pieces of equipment, the power conversion equipment database also covers a wide range of equipment, and the data are regularly updated based on manufacturer-provided information. This is convenient for speeding up the initial stages of design, but you should also understand that "convenience" and "unconditional accuracy" are not the same.

In its official description of the conversion equipment database, it states that the recorded parameters cannot be guaranteed and, because transcription errors or specification changes are possible, it strongly recommends that users carefully cross-check against the latest specifications when actually using the data. In other words, PVSyst is not software that automates equipment selection and accepts responsibility for it. It is a tool for quickly producing a draft configuration and supporting design decisions. To avoid design failures, you should use the database as a convenient baseline while always performing a final project-by-project consistency check.

Use Case 4 Shadow and Loss Analysis

The fourth use of PVSyst is shade and loss analysis. One common failure mode in solar design is producing large numbers under ideal conditions and then deducting losses all at once at the end as a kind of safety factor. PVSyst is built on the opposite idea: it embeds losses into the design from the start. The official project design workflow also shows, after the initial minimal-configuration simulation, a step-by-step addition of far shading, near shading, thermal effects, wiring, module quality differences, mismatch, soiling, angle-of-incidence losses, and so on. In other words, losses are not a retroactive correction but part of the design itself.

PVSyst is useful because it lets you break down which losses are affecting performance and by how much. On the official losses chart page, the loss diagram is described as a chart for quickly grasping the quality of a photovoltaic system design and finding the main sources of loss. Moreover, because it can be viewed not only annually but also by month, you can track what is affecting performance seasonally. For example, when a proposal performs below expectations, it becomes easier to distinguish whether the cause is the irradiation conditions themselves, temperature, shading, or the conversion side. This is an entry point for design improvements that can be difficult to see from simple energy-yield comparisons alone.

Shading is one area where PVSyst is particularly strong. On its official shading page, distant shading and near shading are clearly distinguished: distant shading is handled with a horizon line, whereas near shading, which casts shadows that fall on parts of the generator surface, requires a more complex 3D definition. Moreover, near shading does not only affect the proportion of area in shadow but also causes electrical mismatch losses. In other words, “it’s fine because only a little is shaded” is not necessarily true. If shading is taken lightly during the design phase, it can lead to significant differences later, so PVSyst’s shading assessment is very practical.

Furthermore, the official module layout feature allows you to define the position of each module and which string or input that module belongs to, in order to calculate electrical shading mismatch losses in detail. This is an approach that views the effects of shading not simply as an "area fraction" but also as a circuit-level problem. Of course, such an in-depth evaluation requires accurate 3D definitions and system definitions, but the fact that you can push the analysis that far when necessary is one of PVSyst's major uses. The more difficult a project's shading is to handle, the greater the value of this feature.

Use Case 5 Comparison of Multiple Proposals and Business Feasibility Assessment

The fifth use of PVSyst is comparing multiple proposals and evaluating project feasibility. In official project design, it is stated that different simulation runs within the same project can be compared, and optimization and parameter analysis are extensions of that idea. In other words, PVSyst is not software meant to calculate a single scenario and stop, but also software for laying out and examining scenarios with different conditions side by side. In practice this purpose is very important, since proposals are often narrowed down by comparing differences in orientation and tilt, loss conditions, shading conditions, and configurations.

Even on the same site, results change if you slightly change the orientation, adjust the row spacing, assume stricter losses, or treat shading conditions more realistically. With PVSyst, you can manage and compare those factors within the context of a project. This makes it easier to see not only which option generates more energy, but also which has a more stable loss structure and which conditions the results are sensitive to. In design practice, these comparisons directly affect how easily you can explain decisions internally and externally, so PVSyst’s comparison features are highly practical.

Additionally, PVSyst has an economic evaluation function. The official documentation explains that after simulation you can define conditions such as initial installation costs and annual operating expenses, and evaluate the cost of electricity generation and long-term profitability. The important point here is that a proposal with higher energy production is not necessarily the optimal one. In some cases, the configuration becomes more complex to slightly increase production, which is not advantageous overall. By using PVSyst, performance and commercial viability can be viewed together as a single workflow rather than separately, making practical decision-making easier.

This use is particularly important for design engineers to become not just people who produce numbers but people who can demonstrate the reasons for their choices. Rather than only showing annual power generation, by comparing alternative proposals and indicating how much each difference in conditions affects the results, and by extending that to an assessment of business viability, the quality of proposals and internal coordination will improve greatly. PVSyst is, at the same time, software that produces calculated values and software that prepares the materials needed for design decision-making.

Use Case 6 Comparison with Measured Data and Improvement

The sixth use of PVSyst is comparison with and improvement using measured data. This is a point that beginners tend to overlook, but it is very important in practice. The official measured-data feature explains that you can import data obtained from the actual system, display performance in tables and graphs, and compare it to the simulation values in a similar form. The comparison process is quite close to a normal simulation and is carried out by linking the measured-data file to a variant instead of the original meteorological data file. In other words, the assumptions made at design time and the actual performance during operation can be compared in the same context.

This feature is useful because it allows you to learn from the difference between predictions and actual results. Even in the official approach to measured data analysis, it is explained that you can perform a close comparison between on-site measured values and simulation values, observe the differences while analyzing their causes, and, if necessary, revise the input conditions. Furthermore, this process is said to be a powerful means not only for validating the software but also for detecting small faults or temporary anomalies in equipment that is actually in operation. PVSyst is therefore not only forecasting software used before installation but also software for post-installation verification and improvement.

For designers, this application also carries over to subsequent projects. When a discrepancy between predicted and actual performance appears at a site, being able to consider whether it stems from differing meteorological assumptions, how losses were accounted for, the assessment of shading, or the configuration conditions makes it easier to incorporate into the next design. In other words, PVSyst is not software for a single project but a learning platform for building up design quality. Its value increases the more it is used because it makes it easier to create a cycle of verification and improvement.

Of course, there are prerequisites for comparisons with measured data as well. The measured dataset must include the necessary meteorological data, and for the comparison you must carefully define the real system’s conditions in the same way as for a standard simulation. In other words, PVSyst does not automatically ensure the comparison is correct; it provides a framework that makes the comparison easier. With that framework in place, predictions and actual performance are less likely to become disconnected, and communication between design engineers and operations personnel becomes easier.

Points to note when using PVSyst

Up to this point, PVSyst may appear to be extremely versatile. However, if used incorrectly it can actually make design decisions more ambiguous. The first thing to note is that PVSyst is software that heavily depends on its assumptions. Preliminary design is nothing more than a rough estimate, and even in detailed design, if the consistency of site, weather, mounting surface, losses, shading, and equipment data is lax, the reliability of the results will not improve. It is important to adopt the mindset that the software does not hold the answer, but calculates the outcomes based on the assumptions you set.

Another important point is that PVSyst is strong for design and assessment, but it is not a substitute for the site survey itself or for construction management. Detailed evaluation of near shading and module layout calculations requires accurate 3D definitions, module positions, and connection information. In other words, the accuracy of desk-based simulations is supported by the accuracy of on-site information. If dimensions, obstacles, and equipment placement remain unclear, no matter how advanced the simulation, discrepancies with reality will persist. To use PVSyst effectively, you need to consider not only how to operate the software but also how to gather site information.

Furthermore, it is important not to rely too heavily on the convenience of the database. The official guidance states that while the equipment database is convenient and is updated, it cannot guarantee the parameters it contains, and users should carefully cross-check with the latest information when using it. In other words, PVSyst is not software that “returns correct answers without verification,” but software that “makes it easier to organize the points that need verification.” To avoid failures in design practice, you should not overtrust convenient features and must clearly identify which points you need to verify yourself when using them.

Summary

When clarifying what kind of software PVSyst is, its uses can broadly be divided into six categories: preliminary estimates in the early planning stages, detailed energy production simulations, verification of equipment configuration and capacity design, analysis of shading and losses, comparison of multiple proposals and evaluation of project feasibility, and comparison with measured data and improvement. In other words, PVSyst is not only software that calculates the energy production of solar PV systems, but also software for organizing assumptions, comparing options, and validating decisions to support design judgment. It is not merely a tool for looking at generation numbers; if you understand it as a tool that makes it easier to explain why those numbers occur, its appropriate uses become clear.

To make effective use of PVSyst in practice, it's important to use it step by step—from rough estimates to detailed design, and from comparison to verification—rather than aiming for perfect inputs from the start. Begin by grasping the overall picture, then refine losses and shading, and finally interpret the results with loss diagrams and performance ratios, comparing with actual results and making improvements where necessary. Once this workflow is established, PVSyst becomes not merely a calculation tool but a practical foundation that enhances design accuracy and explanatory power. The software is particularly valuable for those who want to organize solar PV design numerically.

The more carefully generation forecasts and shading analyses are performed at the desk, the more important the accuracy of on-site location information and equipment layout becomes. Even if installation conditions are refined in PVSyst, if on-site positioning and identification of obstacles are vague, discrepancies between design assumptions and construction realities tend to increase. That is why organizing generation estimates and the loss structure in PVSyst during the design stage, and combining that with iPhone-mounted high-precision GNSS positioning devices like LRTK in the field, makes it easier to connect design, construction, and operation and maintenance more consistently. The idea of improving desk-based accuracy with PVSyst and harmonizing on-site positional accuracy with LRTK is well suited to enhancing the reproducibility of the entire solar PV workflow.