What is PVSyst? 8 Essential Basics Useful for Practical Work

Table of Contents

• What is PVSyst?

• Basic Knowledge 1 Not just software for calculating energy production

• Basic Knowledge 2 Its role changes between preliminary assessment and detailed design

• Basic Knowledge 3 Use it to compare projects and variants

• Basic Knowledge 4 Meteorological data is the foundation of prediction accuracy

• Basic Knowledge 5 You can design including the equipment configuration

• Basic Knowledge 6 Builds results from physical models

• Basic Knowledge 7 Interpret results with loss diagrams and performance indicators

• Basic Knowledge 8 Comparing with measured data also leads to improvements after operation

• Summary

What is PVSyst?

PVSyst is dedicated software for the design, capacity assessment, performance evaluation, and data analysis of photovoltaic power generation systems. In its official documentation it is presented as an environment for design and performance analysis using detailed time-step simulations, and it is structured so that each project can contain its geographic conditions and time-resolved weather data, allowing simulations under different conditions to be compared within that framework. In other words, PVSyst is not a simple calculator that looks only at a single generation output; understanding it as practical software for organizing assumptions on a per-project basis and supporting design decisions with numerical evidence makes its true purpose easier to grasp.

When a practitioner searches for "What is PVSyst", what they want to know is less the meaning of the name than in what situations it is useful and how reliable it is. The important point in answering that is that PVSyst is not just a tool for producing energy-yield numbers; it handles meteorological conditions, installation conditions, system configuration, losses, shading, and comparison with measured data all in a single workflow. Moreover, it can be used differently depending on the depth of study—rough estimates at an early stage and detailed simulations as a project progresses. Its widespread use in practice is due to this kind of flexibility.

Mastering the eight basic concepts introduced below will make it easier to view PVSyst not as a "difficult specialist software" but as a tool for which the appropriate uses in different situations become clear. In particular, the way it links early-stage estimates through detailed design, loss interpretation, and post-operation verification provides great value to practitioners. Conversely, if you adopt it without understanding these points, it will appear to be software that merely has many input fields, making it easy to use incorrectly.

Basic Knowledge 1: Not Just Software for Power Generation Calculations

Put simply, PVSyst is software that calculates the power output of solar photovoltaic systems. However, if you stop the explanation there, you miss out on much of its real value. Looking at the official breakdown, PVSyst presents detailed design, meteorological data management, an equipment database, measured-data comparison, and explanations of its physical models. In other words, it provides mechanisms that support the entire design and verification workflow—not only the final result of energy production but also the underlying meteorological conditions, the equipment chosen, how losses are accounted for, and even post-operation comparisons. In practice, because it is important not only to show the magnitude of a number but also to be able to explain why that number occurred, this breadth proves valuable.

Also, PVSyst manages cases within a project framework and can hold multiple simulation conditions as variants within that framework. This concept is important because, in practice, it is more common to compare multiple proposals and choose the most appropriate one than to adopt a single proposal as-is. For example, you can compare and decide while looking at scenarios such as changing the tilt angle, changing the row spacing, applying stricter shading conditions, or assuming losses more conservatively. Simple energy-yield calculation software tends to treat each run as a separate calculation, but because PVSyst strongly follows the idea of “comparing within a project,” it is easy to use for presentation materials and internal reviews.

Therefore, if you think of PVSyst as "software just for producing generation figures," the large number of inputs and screens can seem burdensome. In reality, those are functions for organizing design assumptions, comparing differences in conditions, and validating results. If you correctly grasp what it is, it is more accurate to consider PVSyst a working platform for quantifying design decisions for solar power generation. Understanding it that way makes it easier to see why it has been used in practice for so long.

Basic Knowledge 2 Roles change between preliminary estimates and detailed design

The key point to grasp when using PVSyst is that preliminary estimates and detailed design are separate things. The official pre-design feature explicitly states that it is a rough generation estimate carried out using only a small number of general conditions, intended for early-stage site assessment and not for detailed design. In other words, in the initial stage when equipment conditions have not yet been finalized, the intended use is to get a rough overall sense. If you do not know this, there is a danger of treating the results of the simple calculation as definitive values.

In practice, what is needed in the early stages of a project is to determine whether “this candidate site is likely to be viable in broad terms.” It’s not realistic to resolve all the details from the start, such as exact equipment configuration and shading conditions. For that reason, preliminary design using PVSyst is useful. If you can create a rough outlook from only a few parameters—location, orientation, and approximate capacity—you can see where to investigate in detail next. What makes it easy to use during the planning and sales stages is this sense of speed.

On the other hand, at the basic design and detailed design stages, rough estimates are not sufficient. In formal project design, thorough design and performance analysis of a photovoltaic power generation system are performed using detailed hourly simulations. In this process, meteorological data, the orientation of the installation surface, system configuration, loss conditions, shading conditions, and so on are built up. In other words, even with the same PVSyst, the correct understanding is to use it in two stages: in the initial study to see the overall picture, and in the detailed design to追う causes and reasons.

When you understand this two-tiered approach, the appropriate use of PVSyst becomes much clearer. The initial numbers are figures to move the conversation forward, while the later numbers are figures that support design decisions. Both are necessary, but they mean different things. If asked what PVSyst is, saying "it can provide rough estimates, but its real strength lies in detailed design and comparative analysis" reflects a well-organized practical understanding.

Basic Knowledge 3 Using Projects and Variants While Comparing

One of PVSyst's major features is the concept of projects and variants. According to the official documentation, a project is a central framework that holds geographic conditions and hourly weather data, within which different simulation runs are managed as variants. This is not merely a matter of file organization. It is a mechanism to allow comparisons within the same project by changing assumptions one by one. What is useful in practice is that you can present alternative options side by side while preserving the context of the project.

For example, even on the same site, results change depending on whether it is oriented south or east–west, whether the tilt is shallow or steep, and whether row spacing is tightened or widened. With PVSyst, rather than managing each of these as separate, disconnected projects, you can organize them within a single project. This makes it easier to track and explain the differences between the changed conditions and the results. Whether designers are comparing internally or explaining to clients and stakeholders, having the differences in assumptions visible is extremely important.

Additionally, project design assumes that optimization and parameter analysis are conducted by running different simulation scenarios. In other words, PVSyst is a tool for finding reasonable solutions by comparing varying conditions, rather than an instrument that delivers a single correct answer in one shot. In solar projects, it is rare for a single definitive solution to be determined from the outset; the practical core of the work is searching for better proposals within the given constraints. In that sense, understanding PVSyst as "software for thinking while comparing" makes it easier to apply in day-to-day work.

Basic Knowledge 4: Weather Data Is the Foundation of Forecast Accuracy

When forecasting power generation, the first and most important factor is meteorological data. In PVSyst’s official documentation, a project is described as retaining geographic conditions and hourly meteorological data, and the meteorological database is organized so that you can create site information, generate hourly meteorological data, compare and visualize data, and import external data. In other words, in PVSyst meteorological data is treated not as just one input field but as the foundation of the entire forecast. This is an extremely important concept that influences the reliability of results in practical work.

Even with the same installed capacity, results can change depending on the location, and even at the same site the appearance of results can vary depending on which meteorological data are used. One reason PVSyst is used for generation forecasts is that it can address this premise directly. Rather than merely outputting predicted values and stopping there, it allows the project to retain which location information and which time-series data were used, making it easier to explain the context behind the numbers. For practitioners, there are many situations where having a clear basis for the figures is more important than the magnitude of the figures themselves.

Also, PVSyst does not use meteorological data measured on a horizontal plane directly as input for the power-generating surface. The physical model includes representations of sun position and incident solar irradiance, and it follows a process that calculates the irradiance reaching a tilted installation surface from the horizontal-plane irradiance. In other words, meteorological data do not directly translate into the final result; they only become linked to the generated energy once combined with the orientation and tilt of the installation surface. Knowing this structure makes it easier to understand why results change with even slight differences in orientation or tilt, and why installation conditions as well as location are important.

Treating meteorological data as the foundation is both a strength of PVSyst and a responsibility for its users. No matter how advanced the simulation, if the underlying meteorological assumptions are inappropriate, the results will be unreliable. For that reason, practitioners using PVSyst must always be aware not only of how to operate the software but also of "which meteorological conditions the figures are based on." Whether one has this awareness greatly affects how generation forecasts are used.

Basic Knowledge 5 Capable of designing including equipment configuration

PVSyst is not software that simply takes a capacity input and outputs energy production. In the official system definition, for each subarray you choose the desired capacity or the available area, the PV modules, the power conversion equipment, and optimization devices if necessary, and the tool automatically proposes an appropriate configuration. Moreover, it proposes arrangements for the number of modules in series and the number of strings that are viable within the allowable ranges. In other words, the prediction covers not only "how many kilowatts to install" but also "which combination will make the system feasible."

In practical work, this difference is very significant. This is because, even with the same nominal output, the behavior of the power conversion side and the way losses manifest change depending on how the system is configured. Whether the configuration is based on the area of the installation surface or on the desired capacity also changes the design approach. PVSyst allows simulations to proceed on the premise of such configuration conditions, so it is easier to produce figures closer to real designs than with simple per-unit calculations. The reason PVSyst is easy to use in practice is that designers can proceed while checking whether "this configuration will really work."

It is also important that there is an equipment database. The official component database includes solar photovoltaic modules, power conversion equipment for grid connection, batteries, equipment for off‑grid systems, generators, pumps, and so on. In other words, PVSyst is designed so that not only the meteorological conditions but also the equipment-side conditions can be organized within a project. This ensures that meteorology, design, and equipment are connected as a single framework of assumptions rather than being separate.

However, there is an important caveat. While the official module database improves reliability by including manufacturer-provided data, PVSyst explicitly states that it does not guarantee the database parameters and strongly recommends that users carefully cross-check them against the latest datasheets before actual use. It also explains that some parameters required by the model are not normally listed in the datasheets, so assumptions may be involved. In other words, a comprehensive database does not mean verification is unnecessary. To use PVSyst correctly, you should leverage the convenient database while ultimately taking responsibility on the project side to ensure consistency.

Basic Knowledge 6: Building Results with Physical Models

One reason PVSyst is trusted in professional practice is that its calculations are founded on physical models. In the official list of physical models, solar position, incident irradiance models, photovoltaic modules, conversion equipment, batteries, pumps, and so on are organized as the primary models. In other words, PVSyst is not software that merely compiles past empirical rules into coefficients. It is structured to sequentially build up where the light comes from, how it enters the power-generating surface, how it is converted into electricity there, and finally how it is delivered to the output.

For solar cell modules, a single-diode model is adopted. The official documentation explains that this model was originally used to describe the behavior of a single cell and has been generalized for use with an entire module. It also indicates that the basic values found in ordinary datasheets are not sufficient, and additional parameters not listed in the datasheet—such as series resistance and parallel (shunt) resistance—are involved. Because these values strongly affect behavior under low irradiance, PVSyst does not simply list the datasheet numbers but uses them while supplementing the model so that it is consistent.

This point also affects how you interpret power generation forecasts. For example, during periods of low irradiance such as morning, evening, or overcast conditions, differences appear that are hard to capture with a simple proportional calculation. The reason PVSyst tends to show behavior closer to reality under those conditions is that it uses a model that includes the effects of low irradiance and temperature. Put another way, PVSyst’s results are not simply the product of input values but are results refined through its model. Therefore, readers of the results should pay attention not only to the "numbers alone" but to "what physical assumptions the numbers were built on."

Also, the efficiency of conversion equipment is treated not as a fixed value but as something that depends primarily on power and can also depend on input voltage. This means the equipment does not always operate at ideal efficiency. Because PVSyst models this kind of real-equipment behavior, it can produce results that better reflect changing conditions than simple fixed-efficiency calculations. PVSyst is used in practice because of this reality-based, bottom-up approach.

Basic Knowledge 7 Interpreting Results with Loss Plots and Performance Metrics

On PVSyst's results screen, the loss diagram is particularly important. According to the official documentation, the loss diagram is a chart for quickly assessing the quality of a photovoltaic system design and helps identify the main sources of loss. Moreover, it is always shown in the annual report and can also be checked on a monthly basis. This is a tool for understanding not just whether annual energy production is high or low, but at which stages which losses are taking effect. In practice, being able to view this diagram greatly influences the thoroughness of design review.

One of the useful features of PVSyst is that it lets you view the effects of losses on an hourly, daily, and monthly basis. The official losses page also explains that the effect of each loss can be checked as hourly, daily, and monthly values and visualized in loss diagrams. In other words, when generated energy is lower than expected, you don’t have to attribute the cause to a single factor. Because you can distinguish whether it’s temperature loss, wiring, shading, or the inverter side, it becomes easier to consider directions for improvement. The ability to trace “why the numbers are poor” when performance is bad is a major strength for practical software.

Another important item is the performance metric. On the official performance ratio page, the performance ratio is defined as the indicator obtained by dividing the energy that was actually usefully utilized by the ideal amount calculated from the solar irradiance incident on the installation surface and the nominal output. Moreover, unlike energy yield per unit of capacity, this indicator is less directly affected by weather conditions and orientation, making it useful as an auxiliary indicator for comparing system quality. Since generation itself varies greatly by location, there is considerable value in looking at the performance ratio when comparing projects or proposals.

The official documentation also explains that the performance ratio is an important industry metric and is often used for performance guarantees at the start of operation and for verifying annual energy yield. In other words, PVSyst results are not merely internal design-stage indicators but reflect an approach that connects to on-site operational evaluation. Rather than chasing annual energy production alone, if you can interpret PVSyst results by combining the loss diagram with performance indicators, those results become far more practical. For practitioners, this is basic knowledge worth remembering.

Basic Knowledge 8: Comparison with actual measurements can lead to improvements after operation

The value of PVSyst also lies in the fact that it does not end at the design stage. Its official measured-data feature is described as allowing users to import data obtained from a system in operation and compare it to simulated values in a comparable way. Moreover, instead of the original meteorological data file, a measured-data file is linked to a variant, so the project structure and the approach to parameter definitions are preserved. This means that design assumptions and operational data can be handled without being treated as entirely separate entities.

Even on the official site’s top description, the measured-data feature is described as displaying actual operational performance in tables and graphs and, by closely comparing it with simulation variables, serving as a means to analyze the real system’s operating parameters and detect even very small anomalies. In other words, PVSyst is not only software for forecasting power generation before installation, but also software for verification and improvement after installation. Rather than treating design and operation as separate topics, being able to review “how the predicted values actually performed” is a major reason to use PVSyst in practice.

This perspective also applies to future projects. When there is a discrepancy between forecast and actual results at a site, analyzing the causes allows you to reflect them in the next loss settings, the way shading conditions are applied, and revisions to the meteorological assumptions. If the design team does not treat a prediction they produced as final but has a system to compare it against operational results and learn, the quality of forecasts will gradually improve. One reason PVSyst has been used in practice for a long time is that it is not merely a forecasting tool but also makes it easy to create a cycle of design and verification.

However, the important point here is not to regard PVSyst as omnipotent. Even if measured-data comparisons are possible, if the underlying measured data are of poor quality or the synchronization is sloppy, the interpretation of the comparison will be unreliable. PVSyst provides a strong framework for comparison, but it does not automatically guarantee how data are collected or the precision of on-site management. Precisely for that reason, in practical work using PVSyst, it is important not only to leverage the software but also to maintain field data and manage location information.

Summary

Summarized from a practical standpoint, what PVSyst is: it is photovoltaic generation yield forecasting software and, at the same time, a practical foundation that connects design, comparison, and verification. It is not software only for generation calculation, its role changes between preliminary and detailed design, it allows comparison by project and variant, meteorological data form the basis, it enables design including equipment configuration, it builds results up from physical models, results can be interpreted with loss diagrams and performance indicators, and comparison with measured data can lead to improvements after operation. Understanding these eight points makes PVSyst’s position quite clear.

What is truly useful in practice is not merely memorizing how to operate the software. It is understanding which function to use at which stage, where to treat something as an estimate and where to treat it as a detailed analysis, and how to interpret the resulting numbers. In that sense, PVSyst can be described as "software whose ability to explain a design improves the more you master it." On the other hand, values in the equipment database must be checked against specifications, and the treatment of shading and losses also heavily depends on the assumptions set in the model. Instead of over-trusting it as a black box, using it while making your assumptions explicit is the shortcut to success.

And the more you improve design accuracy at the drawing board, the more important the accuracy of on-site positional information and layout verification becomes. Even if you carefully refine design parameters and generation forecasts in PVSyst, if on-site staking out and understanding of equipment placement are vague, the gap between desk assumptions and reality tends to widen. That is why increasing predictive accuracy in PVSyst on the design side while combining it with an iPhone-mounted high-precision GNSS positioning device such as LRTK in the field makes it easier to integrate planning, construction, and maintenance. Understanding PVSyst is also the first step toward creating a high-accuracy workflow that includes not only design but also on-site operations.