What is PVSyst? Explained in 7 Points | What It Can and Cannot Do

Table of Contents

• What PVSyst is

• Why it excels at energy-yield simulations

• Why it enables detailed validation of system configuration and capacity

• Why it helps organize meteorological data and assumptions

• Why it proves invaluable for analyzing shading, losses, and layout

• Why it can be extended to measured-data comparisons, economic evaluations, and probabilistic assessments

• What PVSyst cannot do and how to use it in practice

What is PVSyst?

PVSyst is dedicated software for evaluating photovoltaic power systems, sizing capacity, running simulations, and analyzing data. In its official documentation it is positioned as software for photovoltaic systems covering grid-connected, stand-alone, pumping applications, and DC-system applications, and is described as a professional and research environment equipped with meteorological data, a component database, and solar-energy-related tools. In other words, it is more accurate to understand PVSyst not as "a tool for just roughly checking PV generation," but as software for building the evidential basis for design decisions by progressively layering conditions.

If you search for "What is PVSyst" without knowing this point, you are likely to assume it's simply power generation calculation software. However, in reality it is organized with a mode for quickly performing early-stage rough assessments and a mode for conducting detailed studies by building up site conditions, meteorological data, equipment specifications, loss parameters, and shading conditions, and it is premised on the idea of switching between these modes according to the progress of a project. The structure is such that in the initial phase you rapidly estimate from a small number of general inputs, while in the detailed phase you manage conditions on a per-project basis.

At the core of PVSyst is the concept of projects and variants. A project mainly contains site information and meteorological data, within which multiple simulation conditions are saved and compared as alternative cases. This is highly important in practice, because even for the same site you can systematically compare options such as different orientations, different tilts, added shading conditions, or options with stricter loss assumptions. The value for practitioners in using PVSyst lies not in obtaining a single answer but in visualizing how results change with different assumptions.

In short, PVSyst is software for treating solar power generation design studies not as "just formulas" or "just experience", but as simulations that connect site, weather, equipment, losses, and operational conditions. In practice, it is easiest to understand it as a type of tool that is used across stages—from the pre-sales proposal stage, through comparative evaluation in basic design and detailed studies, to post-operation performance analysis—changing its role according to each phase.

Why We're Strong in Power Generation Simulations

PVSyst's core functionality is its ability to simulate the performance of power generation systems in detail on a time-step basis. The official help also explains that the center of project design is the detailed design and performance analysis of solar power generation systems, and that the software is structured to perform simulations based on meteorological data. What makes it valuable in practice is that it allows you to track not only annual energy production but also which seasons, which times of day, and which loss factors cause generation to drop.

In solar projects, even with the same installed capacity, results can vary considerably depending on installation orientation, tilt, surrounding shading, combinations of equipment, temperature conditions, wiring, and operating conditions. PVSyst evaluates performance by building up those conditions individually, which makes it easier to perform a design-consistent analysis than with simple unit-based calculations or rough estimates based only on insolation. The fact that the official documentation is structured to store geographic conditions and meteorological data on a per-project basis and to compare different conditions as variants also reflects that it was designed for this purpose.

Also, the output results do not end with a single total generation value. Simulations handle many variables, and some of them can be saved and reviewed as monthly or hourly results. This is highly meaningful for isolating causes when generation is insufficient. For example, if results come out lower than expected, you can interpret whether the assumptions about solar irradiance are too stringent, the expected shading is too large, or the loss settings are too severe, bringing you closer to an explainable design rather than mere number-matching.

Many search users probably want to know, "What exactly is PVSyst — ultimately, how accurate is it and what can it show?" The answer is that PVSyst is not software that definitively determines power generation; rather, it is software for organizing assumptions and examining generation forecasts on a time-step basis. In practice, whether you understand this distinction greatly changes how you handle the results. Instead of taking the numbers at face value, it is important to read them including which assumptions led to those results.

Reasons why the validity of the equipment configuration and capacity can be finalized

One major reason PVSyst is used in practice is that it allows you to refine not only the energy production estimates but also the validity of the system configuration. In the official help, the definition of system configuration systematically organizes the practical issues that tend to cause concern, such as the number of modules in series and in parallel, matching with the input side, handling of multiple inputs, capacity ratios, design temperature conditions, output limitations, and combinations with batteries or pumps. In other words, PVSyst is not simply a tool for estimating output per unit area, but also a place to examine the consistency of the configuration.

In addition, the availability of an equipment database is important. The official component database organizes solar photovoltaic modules, grid-interconnection power converters, batteries, off‑grid equipment, pump-related equipment, and so on, making it easier to carry out design studies based on specific equipment. For practitioners, this means they can examine the skeleton of an installation not as an assumption but in a form closer to actual conditions. It enables them to consider the impact of equipment specifications and combinations on results without separating that from power generation.

On the other hand, in the early stages of a project, it is not uncommon for details to remain undecided. For this reason, PVSyst also offers a preliminary-design approach that enables quick, rough estimates using only a few general conditions. The official documentation likewise positions preliminary design as the project’s pre-design phase, providing rapid month-by-month evaluations based on limited general conditions. In other words, the software makes it easy to grasp a rough overall picture when the basic plan is not yet finalized, and to refine equipment specifications as you move into detailed design.

What’s important here is that PVSyst is not “software only for people who have everything decided from the start.” Rather, it’s more accurate for practical work to think of it as software for firming up conditions through comparative evaluations from an initial stage when conditions are still vague. If the reader is a project practitioner, keeping in mind a workflow of performing rough estimates early in a project and then transitioning to detailed conditions once the system configuration becomes clear will make it easier to grasp PVSyst’s value.

Why It Helps Organize Meteorological Data and Assumptions

One of the most critical factors that determine PVSyst results is the meteorological data. The official documentation also describes a project as a framework that holds geographic conditions and time-series meteorological data. In other words, however meticulously you build up the configuration and loss assumptions, if the handling of the underlying meteorological data is lax, the reliability of the results will not improve. PVSyst is valued not simply because it has computational capabilities, but because it allows meteorological assumptions to be addressed directly as items to be managed.

The official help provides both a mechanism for importing weather data in known formats and a way to import files in custom formats. For custom formats, you can map columns such as date/time, solar irradiance, and temperature when importing, and the handling of required variables is clearly organized. Furthermore, it recommends inputs such as horizontal-plane solar irradiance, diffuse components, and air temperature, making clear that how the input data are prepared directly affects the results.

Additionally, the current official help also outlines a feature for performing quality checks when importing custom weather files. This shows a philosophy of confirming the validity of the data itself as it is used, rather than assuming that a file can be used as-is simply because it could be loaded. Furthermore, the explanation on comparing weather sources explicitly states that even for the same location, the reference years and averaging periods can differ by source, the treatment of climate change may vary, and some locations may lack usable data. In other words, PVSyst is not an all-purpose oracle; it should be used with consideration of the differences in weather assumptions.

Therefore, when using PVSyst in practice, it is important to decide, before operating the software, "which meteorological data to adopt as representative for which period." Even for the same site, results can change depending on the meteorological data source adopted and the way the data are processed. What PVSyst excels at is that it does not hide this fact and can handle everything from comparing and importing meteorological data to validating them. The more practitioners want to deepen discussions about power generation, the more they should value this point.

Why It Excels When Evaluating Shading, Losses, and Layout

The reason PVSyst is regarded as a step above simple energy-yield estimates is its treatment of shading and losses. In the official shading-related documentation, shading calculations are described as being performed for each time step and applied differently to the direct, diffuse, and reflected components. This embodies the concept of treating the components of light separately rather than lumping shading into a single "percentage reduction." The difference is not negligible at sites where shading has a significant impact in practice.

What is even more important is that shading losses are not treated as merely a reduction in irradiance. According to the official explanation, when part of a cell or module is shaded, not only is the amount of light received reduced, but additional losses occur due to electrical mismatch. In PVSyst, this electrical shading loss is treated separately from linear shading loss, making it easier to interpret output reductions that more closely match real-world performance. Its strength is that it allows you to take a deeper look at the common intuition in shading assessments — “the shadow is small, so the impact should be small” — and reassess it.

In detailed electrical loss calculations, an approach is presented that evaluates the impact of shading for each grouping of input circuits. This means that even within the same site, the effect can vary depending on the circuit configuration and the way arrays are arranged. In practice, it is important whether you can address issues close to on‑site design—such as the arrangement of mounting surfaces, the setting of row spacing, clarifying relationships with obstacles, and how to partition input units. PVSyst is precisely the kind of software that tends to deliver value in that area.

Furthermore, the concept of losses is not limited to shading. The official documentation includes settings for downtime losses that assume operational shutdowns and maintenance stoppages, which can be defined as a time fraction, a number of days, or as stoppages during specific periods. Because it even allows for the random introduction of unpredictable outages, you can model not only ideal conditions but also a certain degree of realistic operational degradation. Rather than producing only a neat annual energy yield, PVSyst is highly practical for considering a loss structure close to reality from the design stage.

Reasons Why It Can Be Linked from Empirical Measurement Comparisons to Economic and Probabilistic Evaluations

The value of PVSyst also lies in the fact that it does not end with simulations at the design stage. The official help describes a function for importing measured data from a system in operation, reviewing it in tables and graphs, and making comparisons that are close to the simulation values. Moreover, it explains that the purpose is not merely to compare visually but to analyze real operating parameters so that even small anomalies can be identified. In other words, PVSyst is not software only for pre-installation use; it is a tool that readily supports post-installation verification and root-cause analysis.

Variant comparisons and parameter scans pair well with this comparison with measured data. The official documentation outlines a workflow where you start from an initial simple condition, save alternative scenarios that sequentially add items such as far-field shielding, near-field shielding, and individual losses, and compare them later. It also provides a feature to run simulations continuously while varying parameters and to aggregate the results for analysis. In practice, this set of features is highly practical, because in many cases you seek a reasonable solution by comparing differences in conditions rather than committing to a single option from the outset.

Furthermore, you can perform economic evaluations after the simulation. The official help explains that by setting initial costs, annual operating costs, financing terms, tariff/pricing conditions, and so on, you can estimate the cost of electricity generation and long-term profitability. What matters for practitioners is that an option that produces more energy is not necessarily the optimal option. Increasing equipment to reduce losses does not necessarily lead to an overall optimum. A strength of PVSyst is that it makes it easy to compare not only performance but also economic aspects within the same workflow.

Additionally, it can handle P50 and P90 as probabilistic assessments. However, this is an area that is easily misunderstood. The official help explicitly states that P50/P90 evaluations are probabilistic interpretations over multiple years, and that users must assume and provide additional parameters that the simulation itself does not have. In other words, just because the software can produce P50 or P90 does not mean it guarantees the future. Rather, it's an area in which the crucial issue is what uncertainties were assumed and how they were assumed.

What PVSyst Cannot Do and How to Use It in Practice

After reading this far, PVSyst may seem like an all-purpose software that can do anything. However, in practice it is important to distinguish what it can and cannot do. The first thing to grasp is that PVSyst is simulation software based on assumptions, and it is not a tool that can definitively determine future actual power generation. There are differences among meteorological data sources, and they also differ in the target year, averaging period, and how they treat climate change; probability assessments such as P50 and P90 require separate assumptions. Therefore, the numbers produced should be treated not as "answers" but as "results given certain assumptions."

Next, PVSyst is neither drafting/CAD software for finalizing drawings, nor a tool that automatically prepares permit and licensing paperwork, nor software that directly manages on-site construction. Even looking at the official documentation as a whole, its focus is project design, simulation, economic evaluation, comparison with measured data, and data analysis. For this reason, in practice it is natural to position PVSyst as the "core of study and validation" and to combine it with processes for producing drawings, construction planning, site verification, and operation and maintenance that occur before and after. Confusing these roles will lead to excessive expectations of PVSyst.

Also, while it can handle batteries and operational strategies, it cannot represent every operational logic with the same level of detail. The official help also includes descriptions of functional scope—for example, that a certain battery operation strategy currently does not handle self-consumption. This means you should not judge solely by whether the software has a feature, but verify whether the operational case you want to examine falls within that feature’s intended scope. The more someone uses PVSyst, the more they need to look not at "whether a feature exists" but at "what assumptions that feature is based on."

Moreover, the smartest way to use PVSyst is to switch its role to match the progress of the project. Use it for rough comparisons in the initial stages, refine losses and system configuration with detailed simulations once conditions are settled, and after commissioning verify anomalies and deviations by comparing to measured data. When used in this workflow, PVSyst, while a single piece of software, becomes the axis that links the planning, design, evaluation, and improvement stages. Conversely, if you treat it as a black box that produces the correct answer in one go, you will not be able to fully extract its value.

If you had to summarize "What is PVSyst" in one sentence, it is a practical software tool that supports design decisions for solar power generation with numerical analysis. It can do many things, but its essence lies less in the simulation itself than in organizing assumptions, comparing proposals, and putting the results into a state that can be explained. For that reason, differences in mastery show up not in operating speed but in how input assumptions are set and how results are interpreted. Practitioners who are unsure about adopting PVSyst will find its necessity easier to see if they first organize "which decisions they want to explain" rather than "what they want to calculate".

In practical work on solar PV projects, there are many situations that cannot be completed by desk-based simulations alone. Checking site conditions, grasping equipment layout on site, staking out positions during construction, and recording equipment locations during operation and maintenance—on-site accuracy often affects the reproducibility of results. By using PVSyst in the design phase to firm up the power generation forecast and combining tools that improve the accuracy of position information during the site phase, it becomes easier to reduce discrepancies between the plans and the actual site. If you take on-site coordination into account, considering measures such as LRTK, an iPhone-mounted GNSS high-precision positioning device, can help create a consistent workflow from design through construction and operation and maintenance.