What is PVSyst? Basic Features and How to Use It — A 5-Minute Guide for Beginners

Table of Contents

• What is PVSyst

• Five Basic Functions of PVSyst

• Overview of How to Use PVSyst

• Settings Beginners Should Configure First

• How to Read Simulation Results

• Common Pitfalls for Beginners

• How to Use It in Practice

• Summary

What is PVSyst

PVSyst is PC-based simulation software for integrating the study, system sizing, energy yield forecasting, and data analysis of photovoltaic power generation systems. Its scope is not limited to simple estimates; it covers a wide range including grid-connected systems, standalone power supplies, pumped storage, and DC systems, and it also includes meteorological data and equipment databases. Therefore, it is easier to grasp its role if you understand it not as an introductory tool for merely getting a rough idea of energy production, but as a practical tool for interpreting performance while organizing the conditions of a project.

When a beginner searches "What is PVSyst", what they want to know is less about the detailed meanings of the interface screens and more about what this software can do and where it can be useful in their work — the overall picture. The strength of this software is that it separates the stage of getting a sense of direction with minimal inputs from the stage of detailed, hourly analysis, allowing you to use each according to the progress of a project. Because you can link the flow — first a rough estimate, then detailed design, and finally comparison and evaluation — within a single environment, it is easy to carry the work forward from initial study to design decisions without losing continuity.

Even more important is the idea of treating each case as a single project and creating multiple alternative proposals with different conditions within it to compare. The official PVSyst documentation also explains that a project contains geographic information and time-step meteorological data, and that it has a structure allowing different simulation proposals to be held as variations within it. In other words, this software is not something that outputs numbers once and is finished; it is a tool for comparing what affects the results by changing orientation and tilt, loss assumptions, shading conditions, and so on.

One reason this software is often recommended to beginners is that, despite its high level of specialization, it makes it easy to organize the basic concepts of photovoltaic power generation. In PV system design, if you confuse location conditions, meteorological conditions, system configuration conditions, and loss conditions, your judgments will become inconsistent. PVSyst requires these to be entered separately in stages and for accuracy to be increased step by step, so as a result it helps organize the design approach itself. The structure naturally links learning how to operate the software with learning how to break down and understand the energy production.

What practitioners cannot overlook is that it makes it easy to record differences in conditions as data rather than as impressions. Small differences—such as a candidate site's orientation being slightly different, the impact of obstacles being different, or the assumed loss rate being different—can greatly affect the final decision. If such differences are discussed only by verbal impression, the basis for decision-making tends to become ambiguous. PVSyst has a structure that lets you save multiple scenarios within the same project and refine them while comparing, so it can be said to be software that facilitates consensus-building while preserving the history of the analysis.

5 Basic Functions of PVSyst

The first basic feature is a quick estimation function for grasping the overall picture in a short time. The official documentation's "Preliminary design" describes a workflow in which you enter only a few general conditions and quickly evaluate on a monthly basis. In the early stages of a project, detailed equipment configurations and specific shading conditions are often not yet fixed, so it is important to rapidly understand roughly what scale the project is likely to be and the expected range of power generation. For beginners, this estimation function serves as the initial entry point.

The second core function is a detailed simulation that refines conditions on an hourly basis. The official "Project design" explains that, within the framework of a project, detailed system design and performance analysis are carried out using hourly weather data. Here, location, weather, the orientation and tilt of the installation surface, equipment configuration, loss conditions, and so on are combined to track behavior that is closer to reality. Because seasonal differences and the effects of condition changes that are difficult to see in rough estimates become apparent, this function becomes central in practical work.

The third basic function is support for system configuration design. In the official definition of grid-connected systems, a system is described as being treated as an integrated configuration that includes generation modules, strings, conversion equipment, and the grid connection. In other words, rather than simply placing capacity and calculating generation, you can refine the design while checking whether the combination constitutes a viable installation in practice. This part can feel somewhat difficult for beginners, but once you understand this way of thinking about configurations, you can take a step from desk-based estimates to practical design work.

The fourth core function is the analysis of shading and various losses. In PVSyst, rather than combining all factors that reduce energy yield into a single large number, you can understand the effects of temperature, wiring, soiling, angle of incidence, mismatch, shading, and other factors step by step. The official loss-related page recommends carefully reviewing each loss factor after the initial simulation, and the loss diagram makes it easy to quickly identify the main sources of loss. When you know where the losses are occurring, your ability to interpret the results improves dramatically.

The fifth core function is comparison with measured data and result verification. In the official measured-data analysis, hourly or sub-hourly measurement data can be imported and compared with simulation values while being reviewed in tables and graphs. This is useful not only for design-stage considerations but also for checking deviations from expectations after commissioning and for detecting signs of anomalies. In other words, PVSyst is not just a pre-design tool; it can also be used as an analysis platform for understanding operations.

For beginners, what is particularly easy to grasp is that losses can be considered not as a lump sum but separated by element. In solar power generation, the effects of temperature, wiring losses, soiling, mismatch, shading, and so on overlap little by little and ultimately affect the final output. When experience is limited, it's easy to write off low generation with a single phrase, but in truth you can't decide on improvement measures unless you determine which losses are dominant. Thinking of PVSyst not as software that simply produces generation figures but as software for breaking down and understanding why the generation reached those figures makes its real value easier to see.

Overview of How to Use PVSyst

What beginners should grasp first is that PVSyst is not a program you fill out completely from the start. Even the official tutorial recommends creating the first system with the minimum required inputs, then progressively making variations by adding distant shading, near shading, individual losses, and so on. In other words, this software is not meant to produce perfect numbers in one go; it is meant to create a baseline case and deepen understanding by layering conditions one by one. Beginners, in particular, will find it harder to get stuck if they follow this order.

The basic flow is to first create a project that will serve as the container for the case, then define the location and weather data, and afterward proceed to the orientation and tilt of the installation surface, system configuration, loss conditions, and shading conditions. In the official project definition, the steps are also presented as file name and project name, site, weather file, and project settings. The order matters: if the earlier conditions are not finalized, the meaning of the shading and loss settings configured later becomes unstable. That is why the basic approach is to prepare the foundation first and then move on to the details.

Even more important is to save condition changes separately within a single project and keep them in a state that allows comparison. If you save them step by step — the baseline case with no shading, a case with distant obstacles added, a case reflecting even close shadows, and a case with revised loss assumptions — you can see where and by how much the numbers moved. Being able to do this lets you explain differences as condition variances rather than mere guesses, both internally and externally. PVSyst’s variation feature is the core that supports that comparative thinking.

What beginners can take comfort in here is that they don't need to master all the advanced features from the start. In practice, it's uncommon to perform detailed shadow analysis or complex multi-condition comparisons all at once on the first try. At first, produce one result for a representative condition, and then dig deeper into points of concern one by one. What matters is not being overwhelmed by the number of screens, but grasping the order of what to decide first and what to refine later.

Items beginners should set up first

The first and most important things to prioritize are the site and meteorological data. In formal project design, geographic information and weather data are treated as the core of the project, and the handling of weather data underpins the assumptions of simulations. No matter how carefully you model configurations and losses, if the underlying site or weather conditions are unclear, the reliability of the results will not improve. Beginners tend to focus on equipment selection first, but what truly determines accuracy from the outset is this foundation.

The next things to set are the orientation and tilt of the mounting surface. Both in the initial estimate stage and in the detailed design stage, orientation and tilt are treated as important parameters that directly affect energy production. Furthermore, these conditions influence not only the annual total but also the seasonal distribution of output. For beginners, rather than trying to determine the optimal values in one shot, it is easier to first establish a baseline using representative conditions and then vary them gradually to compare. PVSyst has a structure suited to such comparisons, so making straightforward use of that characteristic is the quickest way.

The third important point is the system configuration. Here we examine the power generation modules, the series and parallel arrangements, and combinations with power conversion equipment, etc., in a form that can be realized as actual installations. If you focus on the power output first, you may end up producing convenient figures for configurations that are difficult to realize in practice. The system definition in PVSyst is not merely a place to input numbers, but a process to verify whether the configuration is feasible as equipment. Especially for beginners, it is important to prioritize whether the configuration is realizable rather than the magnitude of the numbers.

The fourth point concerns the assumptions about losses. PVSyst has the advantage of allowing losses to be handled in detail, but it provides reasonable default values as initial settings, and it is recommended to review each loss after the first simulation. In other words, you don’t need to tweak every loss item in detail on the first run. Rather, it’s easier to understand why the results changed if you first create a baseline case and then review soiling, wiring, temperature, mismatch, shading, and so on, in sequence.

A fifth thing to keep in mind is importing external data. In practice, there are many situations where you will want to use in-house meteorological data or on-site observation data. PVSyst has a mechanism to import external meteorological and measurement data from CSV and other formats and convert them into a format usable for simulation. Even if you do not use in-house data at this time, simply knowing this entry point will broaden your operational options if you want to improve accuracy in the future.

What’s important in input work is not trying to fill everything using only your own knowledge. Default values and standard assumptions are useful as a foundation for progressing initial assessments. The key is not to follow them blindly, but to first create a baseline case and then replace its elements with project-specific conditions. Keeping this order makes it easier to trace what caused changes when results differ. Especially for beginners, it’s better to prioritize having one comparable baseline rather than aiming for perfect input from the outset.

How to Interpret Simulation Results

When PVSyst produces results, beginners tend to look first at the annual energy yield, but judging based on that alone is risky. While the annual figure is easy to understand, it hides the process that produced the number. Even two proposals with similar annual totals might differ: one may perform well in summer but poorly in winter, while the other may suffer larger shading losses but have other conditions working in its favor. In practice, it’s important not just to look at the totals but to read what assumptions led to those values.

To do that, the first thing you should look at is the loss diagram. According to the official documentation, a loss diagram is intended to identify the main sources of loss and quickly assess the quality of a design. Because it lets you grasp, as a flow, how much the incident energy decreases at each stage and how much can ultimately be taken out as output, it is very useful even for beginners. If you can see where the losses occur, it naturally becomes clear which settings you should review next.

Next, what we want to check are the monthly results. In the official loss diagram description, it is stated that results can be checked not only annually but also by month, allowing assessment of differences in loss impacts due to seasonality. Because solar power generation does not produce uniformly over the year, checking by month is essential to see whether temperature effects are stronger in summer, whether orientation and tilt settings are affecting performance in winter, or whether shading effects are biased toward certain seasons. If you judge only by annual values, these kinds of biases are easy to overlook.

Furthermore, what is truly important when interpreting results is comparison. Looking at a single result alone makes it difficult to judge whether it is good or bad. By comparing conditions—against the baseline case, what happens if you change the orientation, how much it drops when shading is introduced, how it improves when you revise loss assumptions—the meaning of the numbers becomes clear. If you think of PVSyst not as one-off calculation software but as software for comparing decision-making inputs, the way to use the results becomes much easier to understand.

When checking results, you deepen your understanding more by focusing on whether you can explain the reasons rather than on whether the numbers are high or low. For example, even if the annual energy production is lower than expected, the next steps will differ completely depending on whether the primary cause is orientation, shading, or loss assumptions. Conversely, if you repeatedly change settings without knowing the reasons, you may obtain results but will not build knowledge. In PVSyst, interpreting the results of changes is more important than changing the settings themselves.

Common pitfalls for beginners

The most common mistake is to take the initial simulation results as correct. Simulation software presents tidy numbers, so people tend to feel reassured the moment values appear. However, even official meteorological data tutorials note that weather data are a major source of uncertainty in simulations, and they recommend using reliable data and performing basic cross-checks. In other words, producing results is not the same as being able to trust them.

Another common pitfall is doing detailed shadow analysis too early. The official module layout requires defining each module’s position within the 3D scene and mapping them to the string configuration determined by the system. The procedure summary also specifies the order: define the system first, then define the 3D shadow scene. In other words, if you develop the shadows before the mounting surface and configuration are finalized, you will create more rework later. It’s important to first create a baseline case without shadows.

The third is taking warning messages lightly. In the official project design and system definitions, red warnings indicate that simulation is not possible, while orange indicates conditions that are permissible but not ideal. Beginners often want to move quickly to the results screen, but if they look only at the numbers without understanding what the warnings mean, they will miss cases where the assumptions are unrealistic. Developing the habit of checking consistency before looking at the results, though it may seem like a detour, is actually the shortest route.

The fourth is underestimating the quality of external data. Being able to incorporate measurement data and external meteorological data is a major advantage, but if checks on time definitions, missing values, and outliers are lax, the overall results become unstable. The official measurement-data verification page also indicates that time synchronization is important for solar position calculations and that checking time definitions is necessary. Being able to import data is not the same as being able to trust it. It’s a low-key step, but it’s where practical work makes a difference.

How to use them differently in practice

In practice, it is more effective to use PVSyst differently according to the project phase rather than using it for a single purpose. In initial studies, it is important to quickly grasp the scale and direction from limited information. At this stage, use the estimation function to capture candidate sites, a rough sense of capacity, and differences due to installation surface conditions. What is needed here is not precision but the decision-making material to move the study forward.

In the next design phase, we move on to detailed simulations and sequentially refine the location, weather conditions, installation surface, system configuration, and loss assumptions. At this stage, it is more important to compare multiple scenarios with different conditions than to rely on a single result. Understanding how much the outcome changes when a condition is altered clarifies the basis for design decisions. In internal reviews and stakeholder briefings, having these comparative results also tends to make discussions more concrete.

Furthermore, it can also be used for evaluations after commissioning. In official analyses of measurement data, measured and simulated values are compared at a similar granularity, which helps analyze the behavior of systems in operation and detect minor faults. In other words, PVSyst is not software that ends with pre‑installation desktop studies; it can become a foundation that connects design, explanation, and operational improvement. For beginners, it is sufficient to understand it as design software, but in practice its value increases when used as a common language for continuously understanding power generation systems.

From the perspective of creating explanatory materials, this software is also useful. If you present only the power generation figures, recipients will find it difficult to judge whether the numbers are high or low or under what conditions they apply. However, placing a baseline case alongside a comparison case and explaining assumptions about losses and seasonal differences makes it easier to build consensus. Numbers that the person responsible for the design is not convinced of will not be conveyed to others. For that reason, a structure that enables understanding through comparison is an advantage in practical work.

Summary

PVSyst is a specialized software for designing photovoltaic systems and forecasting power generation. It is not merely for calculating annual energy output; it is a practical tool for organizing location, weather conditions, orientation, tilt, system configuration, shading, and various losses while comparing and evaluating project performance. What beginners should learn first is not to master all the complex features. Start by creating a baseline case, then add conditions one by one and interpret the differences—mastering this basic workflow. Once you can do this, you will not be swayed by numbers and will be able to use them to make informed decisions.

Moreover, what supports the accuracy of such simulations is not just proficiency with the software, but how accurately you can grasp the on-site conditions. If the installation position, orientation, the positional relationships of obstacles, and the site’s coordinate information remain ambiguous, the assumptions will be off no matter how carefully subsequent calculations are done. In situations where you want to efficiently organize on-site positional information and the handling of reference points, using an iPhone-mounted GNSS high-precision positioning device such as LRTK can make it easier to connect site awareness with desk-based design. Going forward in practice, the perspective of not treating simulation and on-site positioning as separate but aligning both to improve design accuracy will be important.