What is PVSyst? A Simple Explanation｜An Introductory Guide Beginners Should Read First

Table of Contents

• What is PVSyst?

• What you should know first about PVSyst's role

• How does power generation forecasting proceed?

• Key input items to set first

• Key points to check first on the results screen

• Common misconceptions for beginners

• How it helps in practical work

• Summary

What is PVSyst?

PVSyst is dedicated software for studying photovoltaic power systems, sizing capacity, evaluating performance, and analyzing data. In the official documentation it is presented not only as a tool for grid-connected systems but also for stand‑alone systems, pumping applications, and DC-system applications, and is described as an environment that includes a weather database, a component database, various tools, and measured-data comparison functionality. In other words, rather than being merely a tool to calculate annual energy production once, it is easier to grasp the overall picture if you think of PVSyst as practical software for managing the assumptions required for design.

What beginners should grasp first is that PVSyst is not a "black box that only returns the answer for energy production." In the official project design, design and performance analyses are performed using detailed hourly simulations, and those calculations are managed within the framework of a project. Furthermore, that project incorporates geographic conditions and hourly weather data, and multiple simulations with different conditions can be compared as variants. In other words, PVSyst is not just software that produces numbers, but also a tool for organizing the conditions under which those numbers were produced.

When practitioners search for "What is PVSyst", what they really want to know is less the meaning of the name and more where it is useful, how much it can be trusted, and how to get started using it. The short answer is that PVSyst can be used for rough estimates in the early planning stages, but its real strength lies in detailed design and interpreting results. Because it can handle meteorological conditions, mounting surfaces, equipment configurations, losses, shading, and even comparisons with measured data in a single workflow, it makes solar projects easier to understand not just on paper but within the actual work process.

What you should know first about the role of PVSyst

Rephrasing the role of PVSyst for beginners: it is a common foundation for organizing solar power project planning numerically. For example, when you install a solar power system at a given site, you can check numerically, one by one, issues such as how much energy it is likely to generate, which orientation is best, whether the combination of equipment is feasible, and where shading and losses take effect. Simple quick-reference tables or per-unit calculations can give a rough sense of direction, but to use them as the basis for a design you need the intermediate reasons behind the results. A major role of PVSyst is that it makes those intermediate reasons easy to visualize.

Also, there are broadly two ways to use PVSyst. One is the preliminary design, which uses only a small number of general conditions to quickly make rough estimates on a monthly basis. The other is the project design, which performs detailed hourly simulations to refine the design and performance analysis. The official documentation states that the preliminary design is a coarse estimate of energy production and should not be used for detailed design; more precise results should be obtained from detailed hourly simulations. Beginners will be less likely to be confused if they first understand the difference between these two roles.

A common misconception here is that "PVSyst cannot be used unless you enter all the conditions from the start." In reality, that is not the case: in the early stages of a project you are expected to grasp the overall picture with a preliminary design, and once conditions are finalized you proceed to the project design. In other words, beginners in particular will use it better by first getting a rough overall view and then detailing the important conditions, rather than aiming for perfect input from the outset. It is more accurate to understand PVSyst not as a difficult piece of software, but as software whose depth can be adjusted according to the stage of use.

How Will Power Generation Forecasting Progress?

PVSyst's power yield prediction is not a simple calculation of "multiplying system capacity by insolation." First, you select the site and meteorological data and determine how much solar energy is available at that location. Next, you convert that irradiance from the horizontal plane to the actual installation plane, reflecting azimuth and tilt. On top of that, you sequentially account for module output characteristics, shading, incidence angle, temperature, wiring, conversion efficiency, and so on to arrive at the final energy. PVSyst is used in practice because this calculation process is visible. Since it is easy to trace not only the results but also what affected each stage, it produces forecasts that are easy to explain.

The starting point for this process is the meteorological data. In the official documentation, a project is described as a framework that holds geographic conditions and time-based meteorological data, and the meteorological database is said to handle creating geographic sites, generating, comparing, and visualizing time-series meteorological data, and importing external files. In other words, PVSyst’s calculations begin not with “which equipment to install” but with “which location and which meteorological assumptions to use.” If you want to improve the accuracy of power generation forecasts, you must first handle the meteorological assumptions carefully.

Next important is the photovoltaic module model. PVSyst adopts a single-diode model, and while the official documentation acknowledges that a more complex two-diode approach exists, PVSyst explains that it uses the single-diode model taking into account the accuracy of input values and internal mismatch. Furthermore, it handles not only the basic values commonly listed in datasheets but also additional parameters, such as series resistance and parallel (shunt) resistance, which are usually not fully specified in datasheets. This is to make the behavior under low irradiance and the effects of temperature variations more realistic. What beginners should remember is that PVSyst does not simply multiply rated values; it produces results through an internal model.

The conversion equipment side is not treated as having a simple fixed efficiency either. In the official converter model, the rated AC output is the basic condition, there are constraints on the relationship between the input side and the output side, and the way efficiency is considered also changes depending on power and input voltage. Also, the efficiency curve can be defined not only by database values but, when necessary, as a series of points. In other words, the power taken from the DC side does not necessarily appear on the AC side in the same amount; the calculation includes portions that may be trimmed off depending on conditions. PVSyst is valued for generation forecasting because it can treat the realistic behavior of equipment as intermediate states in this way.

Items to confirm in the initial input

When beginners start using PVSyst, there are three inputs they should first grasp: the site, the installation conditions, and the system conditions. In the official project definition, you first decide the project name, then define the project site, select the meteorological file, and finally proceed to the project settings. In other words, in PVSyst it is important to determine "where the calculation will be done" first, rather than entering detailed equipment models from the outset. If the location remains ambiguous, the entire subsequent calculation can easily become unstable.

Next, the conditions of the mounting surface are important. Azimuth, tilt, and—when necessary—how to handle distant horizon conditions and the effects of nearby obstacles have a major impact on power generation forecasts. Even in formal project design workflows, there are steps to define the mounting surface’s orientation, tracking, row layout, distant shading, near-field shading, and so on. For beginners, simply entering azimuth and tilt carefully can substantially change how the results look. Detailed shading calculations can be explored later, but orientation and angle are the initial foundation, so it’s important not to be sloppy here.

The next thing to look at is the system conditions. In PVSyst you can select modules and power conversion equipment for each sub-array and design the series and parallel counts (number of modules in series and number of parallel strings). This is not merely an input of capacity, but a process to proceed while confirming the conditions that make the installation technically viable. For beginners, rather than trying to create a complex configuration from the start, it is easier to first run calculations on a single standard configuration and then adjust detailed conditions as needed. PVSyst’s strength is that it lets you inspect the equipment configuration, but that strength is easier to master when used progressively.

Another thing you must not forget is the loss conditions. The official losses page explains that PVSyst treats incident-angle losses, soiling, irradiance, temperature, module quality differences, mismatch, wiring losses, downtime, and other factors in detail. However, you do not need to determine all of these perfectly from the outset: reasonable default values are provided for the first simulation, and it is recommended that you review them later according to the project. For beginners, instead of trying to finalize everything in the initial calculation, it is easier to understand if you first look at the overall picture and then correct the important losses one by one.

Points to check first on the results screen

The first thing to look at on PVSyst’s results screen is not just the annual energy production figure. What you should check first is the loss diagram. On the official loss diagram page, this chart is described as a way to quickly grasp the quality of a photovoltaic system design and to help identify the main sources of loss. Moreover, because it can be viewed not only in the annual report but also on a monthly basis, you can track which losses are more pronounced in each season. Especially for beginners, instead of looking at only the annual values at first, getting into the habit of looking at this loss diagram to see "from where to where the energy is reduced" will speed up understanding.

Next, it's useful to look at the list of simulation variables. According to the official results description, the outputs include numerous variables and can be displayed or exported by month, by day, or by hour. In other words, you can check not only the final AC output but also variables such as the solar irradiance incident on the installation surface, behavior on the DC side, post‑conversion output, and efficiency. Beginners don't need to follow everything, but even just comparing the two—how much solar irradiance reached the installation surface and how much electrical output was produced in the end—will significantly change how you interpret the forecast results.

One more thing to remember is the performance ratio. Officially, the performance ratio is described as an indicator obtained by dividing the energy actually available for useful use by the ideal amount calculated from the solar irradiance incident on the installation surface and the nameplate capacity. It is further presented as an indicator that includes optical losses, array losses, and system losses. The performance ratio may seem somewhat abstract to beginners, but in practice it serves as an auxiliary indicator to see "how well this system is operating." Looking at the performance ratio as well as the annual energy production makes it easier to grasp the overall coherence of the design and differences in the loss structure.

Common Misunderstandings for Beginners

One of the most common misunderstandings for beginners is assuming that the preliminary design figures are the same as the detailed design figures. The official preliminary design page clearly states that these are rough estimates of power generation based on a small number of general conditions and should not be used for detailed design. Furthermore, it advises that you should generally expect an uncertainty of more than 10%, and that more precise results should be obtained through detailed hourly simulations. Beginners who understand that the initial figures are only meant to provide a sense of direction will be less likely to misuse them.

Another common misconception is believing that the default values are sufficiently precise. On the official losses page, the loss parameters are initially set to reasonable defaults, but it is recommended to carefully redefine each loss according to the project after the first simulation. In other words, PVSyst does not provide a one-size-fits-all answer from the start; the more the user refines the conditions, the higher the quality of the results. For beginners, it is realistic to use the defaults to get an overall grasp and then reassess soiling, temperature, wiring, shading, and downtime.

Also, it is dangerous to unconditionally trust the equipment information listed in a database. The official documentation states that module models include additional parameters not normally found in datasheets, and that database values must ultimately be cross-checked against the most up-to-date specification information. Beginners tend to think “it’s safe because it’s in the database,” but in practice it is essential to verify conditions for each project. PVSyst has a convenient database, but it does not remove the need for the verification work itself.

Moreover, it is easy to misunderstand that detailed shadow calculations are a later-stage process. In the official module layout function, calculating electrical shading mismatch losses in detail requires defining the position of each module in 3D and also setting which string each module belongs to. In addition, these definitions are typically performed at the final stage of system studies. In other words, beginners do not need to jump into that from the start. First, understand normal design practices and how to interpret losses, and only proceed to detailed shading assessment for projects where it is necessary.

How it helps in practical work

The practical use of PVSyst is, first and foremost, for comparing options in the early planning stage. Even when conditions are not yet fully fixed, you can quickly create monthly outlooks in preliminary design using only a few general assumptions. This makes it easier to screen site candidates, roughly compare mounting orientations, and organize the issues that should be examined in more depth next. If a beginner is using PVSyst for the first time, I recommend first grasping the overall workflow at this level. Rather than jumping straight into full detailed design, this makes the role of the software easier to understand.

What becomes useful next is detailed design and the creation of explanatory materials. PVSyst makes it easy to compare conditions using the project-and-variant approach, and the results include loss diagrams and numerous simulation variables. In other words, it becomes easier to explain why this design option was adopted, which losses are large, and where improvements should be made. For designers, the major value is being able to make comparisons with reasons, not just simple differences in energy output. Even for beginners, if you consciously use it in this “compare and explain” way, PVSyst becomes easier to use not merely as a calculator but as a design support tool.

Moreover, the fact that it facilitates post‑operation performance verification should not be overlooked. The official measured-data function is described as being able to import measured data from almost any text format as hourly or sub‑hourly data, view it in tables and graphs, and make close comparisons with simulations. The General Philosophy page also states that this function is useful not only for validating the software but also for analyzing operating systems and detecting minor anomalies. In other words, PVSyst is not software that ends with prediction; it is also software for reviewing predictions against actual results and leveraging those insights for subsequent projects.

Summary

To briefly summarize what PVSyst is for beginners: it is a practical software that handles solar power system design and generation forecasting in a single workflow, from weather conditions to equipment configuration, losses, shading, and result analysis. In preliminary design you grasp the general direction; in project design you refine the design with detailed hourly simulations; and in the results you read loss diagrams and the performance ratio, and, if necessary, compare with measured data. Because of this complete workflow, PVSyst has been used for a long time by both beginners and practitioners. As a first step, it is easiest to understand it not as "software that gives the answer for energy generation" but as "software that organizes the reasons behind a design."

Moreover, for solar projects it is important not only to perform desktop calculations but also to verify on-site spatial relationships and equipment layouts. Even if you carefully organize power generation forecasts and shading considerations in PVSyst, ambiguous on-site location information can easily create discrepancies between design assumptions and actual construction. That is why it is effective to deepen analysis in PVSyst during the design phase and combine it with a system capable of handling high-precision location information at the site. With that flow in mind, the iPhone-mounted GNSS high-precision positioning device LRTK becomes a natural choice. Adopting an approach that links desktop design accuracy with on-site positioning accuracy makes it easier to improve the overall quality of solar work.