top of page

Table of Contents

• What is PVSyst

• Point 1: Use for rough preliminary estimates in the early planning stage

• Point 2: Use for detailed design and time-step simulations

• Point 3: Use to visualize shading and losses

• Point 4: Use to compare multiple options and optimize

• Point 5: Use for comparison with measured data and economic evaluation

• Point 6: Introduce it with the assumption that it is not all-purpose

• Summary


What is PVSyst?

PVSyst is dedicated software for studying photovoltaic power generation systems, sizing capacity, evaluating performance, and analyzing data. According to the official documentation, it is described as software that handles not only grid-connected systems but also stand-alone systems, pumping applications, and DC-system applications, and is organized as a professional environment equipped with meteorological data, an equipment database, and a range of tools. In other words, PVSyst is not merely a simple power generation estimate—it is easier to grasp its essence by understanding it as software that builds up a solar project's assumptions one by one and supports design decisions with numerical data.


Many practitioners who search "What is PVSyst" have heard the name but often remain unclear about what the software is actually used for. In practice, it can be used to produce rough forecasts in the early planning stages, and it can also be used later in a project to dig into shading and losses and refine detailed design. Furthermore, it provides ways to compare operational performance data with simulations to analyze deviations from expectations. If you are considering adopting it, it is more accurate to view it not as a tool to calculate generation once, but as a tool that connects planning, design, comparison, and verification.


At the core of this software is the concept of a project. According to the official help, a project holds geographic conditions and hourly meteorological data, and is structured so that multiple simulation conditions can be kept as alternative scenarios within it. Because you can compare alternatives while changing the orientation of the installation surface, system configuration, and loss conditions, it becomes easier to organize “what the differences are between this option and that option” within the same project. If you grasp this before getting started, it makes it easier to understand PVSyst not as a standalone calculation screen but as a work platform for managing a project end to end.


It should not be overlooked that PVSyst uses physical models for its calculations. In the official documentation, models for solar position, incident irradiance, photovoltaic modules, conversion equipment, batteries, and pumps are organized as the basis for the calculations. In other words, it is not an approach that simply multiplies irradiance by a fixed coefficient, but is built on a step-by-step philosophy of “how light enters, how it becomes electricity, and where losses occur.” Knowing this structure before implementation makes it clear why there are so many input items and why interpreting the results is important.


Point 1 Use for rough estimates in the early stages of planning

One of the major initial uses of PVSyst is rough preliminary assessment in the early stages of a project. In its official pre-design feature, this is described as the stage for preliminary sizing of a project and a mechanism to perform monthly evaluations very quickly. Moreover, it requires only a very small number of general conditions and can be used even at a stage where specific equipment has not yet been decided. Many people tend to misunderstand this before adoption, but the software is not something that can only be used after all detailed conditions are finalized. Rather, it provides an entry point for grasping the overall picture while conditions are still in flux.


In practice, it is common to begin studies with site candidates identified but the final layout undecided, the capacity range assumed but the configuration not fixed, and the orientation of the installation surface broadly understood but shading conditions yet to be examined. At that stage, starting from detailed design every time leaves insufficient time. PVSyst’s preliminary design is useful because it lets you quickly grasp, at an early stage of a project, “how much potential there is for this location and this orientation.” It is fully practical for screening during the planning stage and for first-round comparisons among multiple candidates.


What is particularly helpful for practitioners is that it makes it easier to advance discussions during the preliminary estimation stage. Even if design details are not finalized, once the overall direction is clear it becomes obvious what should be investigated next. For example, it becomes easier to set priorities such as whether to refine the installation angle, whether rechecking site conditions should come first, or whether shadow analysis is more important than assessing solar irradiance conditions. What you should know before adopting it is that PVSyst can be used not only for detailed design but also effectively for organizing initial studies.


However, what is obtained here is only material for an initial judgment. Even officially, preliminary design is a quick evaluation based on a small number of general conditions, and its role differs from that of detailed time-based simulations. Therefore, it is important to use the results of rough estimates on the assumption that, as the project progresses, you will move on to detailed design, rather than treating them as definitive values. If this distinction is understood before implementation, it is easier to avoid mismatches such as "coarser than expected" or "requiring more input than expected."


Point 2 Used for detailed design and time-based simulation

PVSyst's core capability is detailed hourly simulation. In its official project design feature, it explains that, within a project that contains geographical conditions and hourly meteorological data, detailed hourly simulations are used to perform the design and performance analysis of photovoltaic systems. Moreover, because it allows organization of mounting surface orientation, system configuration, loss settings, and comparison conditions, it can be used not merely as a calculator for annual energy production but as a tool for assembling the design approach itself.


In solar PV projects, results can vary greatly even with the same installed capacity. Different locations change insolation conditions, and differences in orientation and tilt alter both the timing and the amount of light received. Furthermore, when temperature conditions, wind conditions, shading conditions, and combinations with power conversion equipment are included, differences arise that simple unit-based comparisons cannot explain. PVSyst is strong in detailed design because it handles these conditions together, making it easier to trace where the differences occurred. The value of this feature increases in tasks that require explaining the validity of the design.


Another major practical advantage is the abundance of information available in the results. The official documentation states that many variables are provided as simulation outputs and can be reviewed on a monthly, daily, and hourly basis. Because you can track intermediate values—such as the solar irradiance incident on the installation surface, the irradiance after accounting for optical losses, and the energy delivered to the AC side—it becomes easier to explain the background behind the numbers. This is important for those who don’t want to end approval documents or client presentations with simply “it’s X kilowatt-hours per year.”


Furthermore, PVSyst has physical models behind its calculations. In the official documentation, models such as solar position, incident irradiance, photovoltaic modules, conversion equipment, batteries, and pumps are organized, and for photovoltaic modules a single-diode model–based approach is presented. What you should know before adopting it is that this software is not an extension of "rough coefficient calculations." Precisely because it requires many inputs, it enables you to handle design assumptions and the meaning of the results more carefully.


Point 3 Used to visualize shading and losses

The value of adopting PVSyst becomes most apparent in situations where shading and losses can be visualized. In the official description of the loss diagram, the loss diagram is described as a chart for quickly gauging the quality of a photovoltaic system design and is useful for identifying the main sources of loss. Furthermore, because it can be viewed not only in annual reports but also on a monthly basis, it becomes easier to track what is affecting performance by season. When energy generation does not increase as much as expected, being able to organize the influencing factors as a flow of losses rather than relying on guesswork is a major strength.


In practical work, being able to explain why a result is low is more important than the mere fact that it is low. PVSyst lets you trace, starting from plane-of-array irradiance, through reflection, shading, temperature, mismatch, wiring, conversion efficiency, and so on, to determine how much is being lost at each stage. The official documentation also states that the impact of each loss can be visualized hourly, daily, and monthly, and reviewed in loss charts. Because of this structure, it is easier to move discussions beyond simple comparisons of energy production and toward correcting design weaknesses.


Particularly, the way shadows are handled is one of the aspects where the practical value of this software is most readily appreciated. Official shading-related documentation explains that losses caused by shadows appear not only as a simple lack of incident light but also as electrical mismatch losses due to nonuniformities in series and parallel connections. In other words, there are cases where a subjective judgment like "it's fine because it's only a little shading" does not suffice. The idea of treating shading not only as a reduction in solar irradiance but also as an electrical loss is a point that practitioners especially should keep in mind.


Furthermore, for detailed electrical loss calculations, a mechanism is provided to define the exact position of each module and which string or input it belongs to. Official guidance states that detailed electrical loss calculations require the precise positioning of each module, and as an alternative approximate method it also outlines a partitioning model for regularly spaced row layouts. This means that the treatment of shading is likewise tiered according to the complexity of the project. One advantage of adopting this approach is that, if site conditions are simple you can run a quick approximation, while if they are complex you can work through the details more thoroughly.


Also, because losses such as soiling can be handled on a monthly basis, you can represent conditions that are closer to practice than fixing the same loss rate throughout the year. The official documentation also states that soiling losses depend strongly on rainfall and can be defined as monthly values. When such detailed settings are possible, it becomes easier to create conservative, realistic forecasts rather than simply producing high figures under ideal conditions. Understanding this before adopting PVSyst makes it clear that the software is not designed to deliver flashy results, but to address losses directly.


Point 4: Use for comparing and optimizing multiple proposals

In solar projects, there is rarely a single correct answer determined from the outset. There are many conditions you want to decide by comparison, such as which azimuth to use, what tilt to set, how to space the rows, what capacity ratio to choose, and how strictly to treat shading. In PVSyst project design, a structure is provided to create multiple variants within the same project and compare different conditions. The official documentation also explains that optimization and parameter analysis are performed by running these different simulations.


This mechanism is useful in practice because it makes it easier to secure internal agreement and explain things to external stakeholders. Presenting only a single proposal tends to weaken the explanation of why that proposal was chosen. On the other hand, if multiple proposals can be compared within the same framework of assumptions, it becomes easier to explain things like, "this option yields higher power generation but carries shading risk," and "this one yields slightly lower power generation but has a more stable loss structure." PVSyst is software that is valuable not only for providing a single answer, but for preparing comparative materials to support decision-making.


Furthermore, the official help also outlines a mechanism for parametric analysis that runs a series of simulations based on predefined condition changes and consolidates the key results for analysis. In practice, being able to compare results in an organized way is vastly more efficient than manually changing angles or loss conditions one by one and comparing outcomes. From a pre-adoption perspective, the easier this comparison becomes as the number of projects increases, the more directly it affects work quality. For one-off estimates, other methods may suffice, but for ongoing project decision-making the value of the comparison feature becomes substantial.


Also, the basis for comparison is not limited to energy production. By looking at the loss diagram and performance indicators together, it becomes easier to distinguish between proposals that simply benefit from more favorable irradiance conditions and those that are better integrated as a system. In the official outputs, you can check the loss diagram, the performance ratio, and the annual energy production per unit of capacity. In other words, comparisons serve not only to determine "which one produces more power" but also to provide material for considering "which one is easier to explain and likely easier to operate stably." Understanding this before deployment makes the range of applications for PVSyst appear considerably wider.


Point 5 Use for measured comparison and economic evaluation

PVSyst is not software that ends at design-stage simulation. The official measured-data comparison feature allows you to import measured data from an operating system and perform close comparisons with simulation values while checking them in tables and graphs. The comparison process follows a flow similar to a normal simulation, but you can limit the period based on the dates in the measured data and configure which measured items correspond to which simulation variables. This means you can not only view the differences between assumptions and actual results qualitatively, but also verify them under matched conditions.


This feature is useful in practice because it can be used for post-implementation review and anomaly analysis. The official documentation also explains that by importing measured data you can analyze actual operating parameters and identify even small irregularities. In other words, PVSyst is both a pre-deployment planning tool and a post-deployment evaluation tool. Even in organizations where design and operations are handled by separate teams, the ability to connect "predictions" and "actuals" within the same software is a major advantage.


When interpreting results, not only the loss diagram but also the performance ratio is important. In the official documentation, the performance ratio is described as an indicator obtained by dividing the actually and effectively generated energy by the ideal value derived from the solar irradiance incident on the installation surface and the nominal output. In addition, the results screen also displays the annual energy yield per unit capacity. While the energy yield itself is influenced by site conditions, the performance ratio is a useful auxiliary indicator for assessing how well the system is operating. Knowing about this metric before installation makes it less likely that result interpretation will be biased solely toward the magnitude of annual energy yield.


Additionally, PVSyst includes economic assessment features, and the official guidance states that, based on simulation results, you can define initial costs and annual operating expenses to evaluate the cost of electricity and long-term profitability. The important point is that a proposal with higher energy production is not necessarily optimal overall. Making the configuration more complex to gain a slight increase in generation can change the operational burden and the way total costs appear. Because PVSyst provides an entry point that views generation and project economics together rather than separately, designers can more easily keep economic considerations in mind.


Another point to be aware of before adoption is that it can handle probabilistic assessments such as P50 and P90. However, the official help clarifies that evaluations like P50 and P90 are probabilistic interpretations of results over several years, and that users must assume additional parameters that the simulation itself does not contain. In other words, you do not get a number that guarantees the future with the click of a button. Conversely, PVSyst should be seen as a tool that, by making assumptions explicit, helps broaden perspectives rather than ignoring uncertainty and asserting certainties.


Point 6: Introduce it with the assumption that it is not a panacea

Before getting started, the most important thing is not to assume PVSyst is an infallible answer machine. Even in the official documentation, the core of this software is detailed time-step simulations, comparisons, loss analysis, economic evaluation, and comparison with measured data. All of these are powerful, but their dependence on underlying assumptions does not change. In particular, the documentation explicitly states that probabilistic assessments like P50 and P90 require the user to provide additional assumptions. In other words, PVSyst’s figures are a projection of “this is what will happen under these conditions,” not an automatic guarantee of real-world outcomes.


Weather data is a major factor that strongly influences that assumption dependency. The official guidance explains that, as a basic requirement for a project, you should have geographic conditions and time-resolved weather data, and mechanisms for comparing, importing, and validating weather data are provided. On the data quality check screen, it is noted that comparing against a clear-sky model makes it easy to detect time offsets, amplitude inconsistencies in solar irradiance, anomalous nighttime values, and missing data. In other words, if the quality of input data is poor, no matter how advanced the calculations, the reliability of the results will not improve. Before implementation, you need to consider not only software deployment but also the rules for handling data.


Also, the fact that an equipment database is comprehensive is not the same as being able to unconditionally trust the values it contains. The official equipment database can handle modules, conversion equipment, storage batteries, pumps, and so on, but for module data it cannot guarantee the database parameters, so users are advised to carefully cross-check with the latest specification sheets when actually using them. This is a point that must be understood before implementation. Precisely because such convenient databases exist, it does not mean that verification can be skipped; ultimately, the responsibility for ensuring consistency remains with the project side.


Furthermore, while PVSyst is strong for design and evaluation, it is not software that replaces on-site surveys themselves, construction management itself, or the preparation of drawings themselves. As the official documentation states—that detailed calculations of electrical shading losses require the exact positions and connection information of each module—the accuracy of inputs is supported by the accuracy of field information. If site dimensions, obstacles, or equipment locations are unclear, there are limits to the accuracy of desk-based simulations. Before implementation, it is important to clearly define the division of responsibilities: what to finalize in PVSyst and what to verify on site.


For that reason, PVSyst is better suited to organizations that want to compare options with explicit assumptions and make well‑justified design decisions, rather than those that just want a one‑shot answer. Even the official help is rich in features for tracing “why” — variant comparisons, loss diagrams, detailed results, measured‑data comparisons, and so on. In other words, PVSyst’s true value lies not in speed of operation but in enabling an explainable design process. When deciding whether to adopt it, thinking in terms of “do we want to be able to explain our design decisions?” rather than simply “do we want to get generation numbers?” will help keep the decision consistent.


Summary

If you organize what PVSyst is used for from a pre-introduction perspective, its roles can be broadly classified into six. That it can be used for preliminary rough estimates in the early stages of planning, for detailed design and hourly simulations, to visualize shading and losses, for comparing multiple options and optimization, for comparison with measured data and economic evaluation, and that it must be operated with the understanding that it is not a cure-all. In other words, PVSyst is not a one-off power generation forecasting tool, but a practical software for progressively assembling the decision-making materials for solar PV projects.


To enhance the effectiveness of implementation, you should not seek a perfect answer from the start but instead adopt a mindset of using rough estimates before detailed ones, and comparisons before validations. Grasp the overall direction in preliminary design, tighten shading and loss assumptions with detailed simulation, check loss diagrams and performance ratios in the results, and after operation reassess validity by comparing with measured data. When this workflow is established, PVSyst becomes more than just software; it becomes a common language connecting planning, design, and operation. What practitioners really want to know when they search "What is PVSyst" is precisely the breadth of this practical role.


And in solar projects, as the accuracy of desktop simulations increases, the precision of on-site location information and layout verification also becomes more important. In design, firm up power generation forecasts with PVSyst, and on site, carefully check for positional shifts and equipment placement so that discrepancies between plan and implementation are reduced. If you want to organize operations to include that whole workflow, combining an iPhone-mounted high-precision GNSS positioning device such as LRTK in the field makes it easier to link the accuracy of design-stage studies with on-site work. When considering whether to introduce PVSyst, view it not as standalone software but from the perspective of how to ensure consistency from design through to the field to make failures less likely.


Next Steps:
Explore LRTK Products & Workflows

LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.

LRTK supercharges field accuracy and efficiency

​

The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.

bottom of page