What is PVSyst? A Summary of Roles and Features for Design Engineers

Table of Contents

• What is PVSyst?

• Role for design engineers 1: Organizing rough estimates in the early planning stage

• Role for design engineers 2: Building the foundation for detailed design

• Feature 1: Manage conditions on a per-project basis

• Feature 2: Use meteorological data as the basis for design

• Feature 3: Consider installation conditions and equipment configuration together

• Feature 4: Perform time-step calculations using physical models

• Feature 5: Interpret results with loss diagrams and performance indicators

• Feature 6: Deeply analyze the effects of shading

• Feature 7: Facilitate post-operation improvements through comparison with measured data

• Points to clarify before adoption

• Summary

What is PVSyst?

PVSyst is specialized software for studying photovoltaic power generation systems, performing capacity design, evaluating performance, and analyzing data. The official documentation describes it as software that handles not only grid-connected systems but also stand-alone systems, pump applications, and DC-system applications, and it incorporates the meteorological and equipment databases needed for design as well as various analysis functions. In other words, it is easier to understand PVSyst not merely as a tool to calculate annual energy production once, but as practical software for organizing project-specific assumptions and numerically verifying the validity of designs.

From the perspective of a design engineer, the value of PVSyst lies less in the fact that it produces numbers than in how easily it allows you to explain under which conditions those numbers were obtained. The official help also states that detailed design is carried out within the framework of a project, and the software is structured so that multiple simulation conditions can be compared while retaining geographical conditions and time-based meteorological data. In other words, PVSyst is not only a calculation tool but also a working environment for managing, comparing, and interpreting design conditions. If we organize its roles and characteristics for design engineers, this point is the natural starting point.

Role 1 for Designers: Organizing Rough Estimates in the Early Planning Stage

In the design field, it is rare for all conditions to be finalized from the outset. Often there are candidate sites but the equipment is undecided, or the capacity range is visible but the detailed configuration is still to be determined, and studies begin in that state. PVSyst has a preliminary design function suited to these early stages, and officially it is described as a system that can very quickly perform monthly evaluations using only a few general conditions. Because it can be used to grasp a broad direction without specifying a detailed system configuration, it is well suited to early-stage screening and candidate comparisons.

At this stage, the point of a design engineer using PVSyst is not to produce a single correct answer but to move the evaluation forward. For example, it makes it easier to judge whether there is likely to be a significant difference due to the orientation of the installation surface, whether the solar irradiance conditions are viable in the first place, and which conditions should be explored in more depth next. Even in the official explanation of pre-design, this is positioned strictly as a preliminary sizing stage and not as a substitute for detailed design. That is why it is important to use it with an emphasis on speed in the early phase and then link it to detailed design as the project progresses. For the designer, PVSyst also serves as an entry point for organizing initial project decisions.

Role for Designers 2: Building the Foundation for Detailed Design

PVSyst's true strength is, as expected, in detailed design. In official project design it is positioned as a core design function, performing thorough design and performance analysis of photovoltaic systems through detailed time-step simulations. Here, by stacking location, meteorological data, mounting surface orientation, equipment configuration, loss conditions, shading conditions, and so on one by one, you produce results that allow you to read not only the annual energy yield but also the background behind it. For designers, this part provides the foundation for translating rough figures into detailed review.

In practical work, what matters is not only whether the power generation figures are high or low. It is important to be able to trace why those numbers occur, which conditions are affecting them, and where there is room for improvement. In PVSyst, many simulation variables can be checked monthly, daily, and hourly—such as the irradiance incident on the installation surface, the effective irradiance after accounting for shading and optical losses, the energy on the DC side, and the energy delivered on the AC side. Therefore, designers can use the results not merely as final values but as verification material for the design process. This is a major reason why PVSyst is highly valued in design practice.

Feature 1: Manage conditions on a per-project basis

An essential concept for understanding PVSyst’s design philosophy is the idea of projects and variants. The official documentation explains that a project is a framework holding the geographic conditions and time-series meteorological data, and that different simulation runs within that framework are managed as variants. In other words, PVSyst is not a one-off calculation screen; it has a structure for lining up and comparing multiple design proposals within a single project. This is very important for designers because it makes it easier to organize the differences between proposals in the context of the project.

In practice, it is rare to be able to commit to a single design from the outset, and it is common to compare options by varying orientation, tilt, row spacing, loss conditions, shading conditions, and so on. With PVSyst, instead of scattering and managing those as separate files, you can organize differences in assumptions within a single project. Furthermore, the official tutorial recommends first running an initial simulation under standard conditions, then creating separate variants step by step by adding far shading, near shading, individual losses, and so on. Put another way for designers, PVSyst is not "software that gives you a finished proposal in one shot," but "software that searches for a reasonable solution by adding design conditions one by one."

Feature 2: Use weather data as the foundation for design

The foundation of power generation forecasting is meteorological data. Even in PVSyst’s official help, it states that at the center of a project are the geographic conditions and hourly meteorological data, and that handling the meteorological database is placed at an early stage of the design flow. This reflects the idea that no matter how carefully equipment and layouts are refined, if the underlying meteorological assumptions are weak, the reliability of the results will not improve. When design engineers use PVSyst, the first thing they should be conscious of is deciding which meteorological conditions to assume, rather than the software operation itself.

Additionally, PVSyst supports importing and comparing meteorological data. The official documentation explains that there is a mechanism to import external meteorological and measured data from CSV files and similar formats, and to convert them into the standard format while mapping the variable columns. Furthermore, the current official help provides checks that perform quality control on meteorological data imported in proprietary formats and evaluate the reliability of the data. This is highly meaningful for designers, because when using external data they can not only simply load it, but also more easily reflect it in designs while being mindful of input quality.

Furthermore, meteorological data should not be considered only as the total solar irradiance on a horizontal plane. PVSyst’s physical model includes a transposition model that derives the incident irradiance on an inclined plane from horizontal-plane irradiance and calculates how differences in azimuth and tilt affect the results. In other words, it is only when the mounting-surface conditions set by the designer are combined with the meteorological data that a power production forecast can be produced. Understanding this structure makes it easier to grasp why results change with different mounting-surface conditions at the same location and why the accuracy of the meteorological assumptions is important.

Feature 3 Enables integrated consideration of installation conditions and equipment configuration

PVSyst’s practical strength lies in its ability to treat installation site conditions and equipment configuration not separately but as an integrated whole. In the official grid-interconnection system definition, a system is described as a set of components that includes photovoltaic modules, strings, power conversion equipment, and the grid connection. Furthermore, it outlines a workflow in which, for each subarray, you select a module model and a power conversion equipment model and design the combination of series and parallel counts. In other words, PVSyst is not merely a capacity-input calculation tool; it is software that allows you to consider how to realize the installation as an operational system.

This integration is very important for designers, because even with the same nominal output, the DC-side behavior and the AC-side constraints change depending on how the system is configured. In PVSyst, you can go into the equipment configuration in addition to the installation surface orientation, whether trackers are used, and racking layout conditions, so it handles not just "how many kilowatts to install" but also "how to design that capacity" — a form closer to practical design questions. What makes PVSyst practical is that designers can proceed to energy yield predictions while verifying the validity of the configuration.

On the other hand, the existence of an equipment database does not mean you can unconditionally use the values it contains. The official component database can handle PV modules and inverters, but it does not guarantee the database values for module data, and users are advised to carefully cross-check them against the latest datasheets when using them. When designers use PVSyst, they should take advantage of the convenient database while maintaining diligence in performing project-specific consistency checks. In other words, PVSyst is a tool to make design work easier, not a tool that eliminates the need for verification.

Feature 4: Calculate accumulations over time using a physical model

The confidence in PVSyst rests on the fact that it builds results from physical models. In the official list of physical models, meteorology, solar position, incident irradiance models, photovoltaic modules, power conversion equipment, batteries, pumps, and so on are organized as the primary models. In other words, PVSyst is not simply a compilation of empirical rules; it is based on an approach that follows in sequence “where the light comes from, how it reaches the generating surface, how it becomes electricity, and how it is converted to output.” For design engineers, it is precisely this layered buildup that allows them to read results while understanding the meaning of changes in conditions.

For photovoltaic modules, a single-diode model is adopted. The official documentation explains that this model is based on the equivalent circuit of the cell and is generalized for use across the entire module. Furthermore, additional parameters such as series and parallel resistances, which are not fully provided in standard datasheets, are said to affect behavior under low irradiance. In other words, PVSyst does not simply multiply the rated values from the datasheet as-is; it has an internal model to bring the output characteristics closer to reality. This is a feature that designers cannot afford to overlook when trying to understand the background of the results.

The same is true for the conversion equipment: in the official input/output models, maximum power point tracking (MPPT) operates within a fixed voltage window; if the true maximum power point lies outside that window, losses occur, and the output side is furthermore subject to constraints such as rated power. Efficiency is not a fixed value either; it can vary depending on output and input voltage. From a designer's perspective, this means that "the power obtained on the DC side does not simply appear unchanged on the AC side." PVSyst is useful for design because it can incorporate these real-plant behaviors into time-step calculations.

Feature 5: Interpret results using loss plots and performance metrics

The most important thing when viewing results in PVSyst is the loss diagram. On the official loss diagram page, the loss diagram is described as a chart that quickly conveys the quality of a photovoltaic system design and helps identify the main sources of losses. Moreover, because it can be reviewed not only in the annual report but also as monthly graphs, it becomes easier to track which losses are most pronounced in which seasons. What matters to designers is not a single annual energy figure but being able to see "at which stage and by how much things were reduced." The loss diagram is the central screen for that purpose.

Furthermore, PVSyst handles losses in considerable detail. On its official losses page, it states that it treats incidence-angle losses, soiling losses, irradiance losses, temperature losses, module quality differences, mismatch, wiring losses, downtime losses, and so on in detail. Moreover, for the initial simulation it recommends using reasonable initial values and, in a second stage, carefully reconfiguring each loss according to the project. This is very practical for designers, because the intended workflow is to first quickly create an overall picture and then tighten up the validity of the losses.

For interpreting results, the performance ratio is also important. The official documentation defines the performance ratio as the actual useful energy produced divided by the ideal amount calculated from the solar irradiation incident on the installation surface and the nominal output. Unlike energy yield per unit capacity, this metric is less directly dependent on weather conditions or installation orientation, making it easier to compare system quality. When designers compare multiple options, looking only at total generation mixes in site and orientation differences, whereas examining the performance ratio makes it easier to discern the system’s overall coherence and differences in its loss structure.

Feature 6: Dive Deeper into the Impact of Shadows

For design engineers, the way shading is handled is a factor that greatly affects the accuracy of energy yield predictions. The official PVSyst help covers both far-field shading and shading from nearby obstacles, and is structured to allow proceeding to detailed calculations of electrical shading losses when necessary. Rather than simply treating shading as a single “X percent reduction,” it enables spatial conditions and electrical effects to be organized step by step, so designers can adjust the depth of their analysis according to the complexity of the project.

What’s particularly important is that PVSyst does not treat shading as merely a reduction in irradiance. The official module layout feature describes defining the position of each module and which string or input it connects to in order to calculate electrical shading mismatch losses in detail. This is because partial shading is assumed to cause additional losses as electrical mismatch, not just a shortfall in received irradiance. Even in situations where a designer might think “it’s a small shadow, so the impact will be small,” PVSyst allows for a deeper level of analysis.

Of course, deeper shading assessment also requires prerequisite information. Even the official documentation states that for detailed electrical loss calculations, the exact position and defined connections of each module are necessary. In other words, while PVSyst can handle shading in depth, it also demands accurate site conditions and layout information. For designers, PVSyst is not a tool that magically and automatically solves shading problems; it is powerful when correct spatial information is provided. Understanding and using it with this point in mind greatly increases the credibility of the shading assessment.

Feature 7: Easier to make post-operation improvements through comparison with actual measurements

The role of PVSyst does not end at the design stage. The official measured-data feature is described as being able to import data from operating systems, display it in tables and graphs, and perform comparisons against simulated values. Furthermore, its purpose is not merely to display data but to analyze actual operating parameters and detect even small anomalies. In other words, PVSyst is both pre-installation power generation forecasting software and a post-installation verification and improvement tool.

This feature is important for design engineers because it allows them to view forecasts and actual results together rather than separately. When a site produces less power than expected, it provides an entry point to consider whether the cause is different weather conditions, the way losses were assumed, or a minor equipment fault. Even officially, comparisons with measured data are considered not only useful for validating software but also a powerful tool for analyzing live operational systems and detecting faults. When design engineers have an environment in which they can review operational results, it becomes easier to improve the accuracy of loss settings and assumptions in future projects.

Moreover, PVSyst provides a mechanism to define the items for comparison and to decide in advance which measured values correspond to which simulation variables. This is not simply about looking at graphs, but an approach to verification that clarifies the rules of comparison. Put another way for designers, PVSyst is not "software that ends with a prediction," but also "software that develops predictions through actual results." It is precisely because of this cycle that PVSyst offers value beyond a mere estimation tool.

Points to Clarify Before Implementation

From this perspective, PVSyst may seem extremely versatile. However, before introducing it you need to understand its limitations. First, preliminary design is only a rough estimate at an early stage, and even the official guidance indicates it should not be used for detailed design. Also, even with detailed simulations, the results depend heavily on the quality of the input assumptions. If meteorological data, shading conditions, loss settings, and equipment data are inconsistent or of poor quality, no matter how sophisticated the software is the reliability of the results will not improve. What is important for designers is not to use PVSyst as a black box, but to use it while explicitly stating the assumptions.

Also, while PVSyst is strong for design and evaluation, it is not a substitute for conducting on-site surveys or for construction management. Detailed shading calculations and module layout calculations require accurate location information and connection data. In other words, precise desk-based calculations only become effective once correct spatial information has been obtained on site. When design engineers adopt PVSyst, it is important not to try to rely on the software alone, but to plan operations that include how site data will be collected and the verification procedures.

Summary

PVSyst is not just software for designers to calculate the power output of photovoltaic systems. It can be used for rough estimates in the early planning stages, serve as the basis for detailed design, enable condition comparisons on a project-by-project basis, be grounded in meteorological data, treat installation conditions and equipment configuration as an integrated whole, perform time-step calculations with physical models, interpret results through loss diagrams and performance indicators, and even lead to post-operation improvements via comparison with measured data. In short, to summarize PVSyst’s role and features in one phrase: it is a practical foundation for advancing design decisions based on evidence rather than intuition.

The more you improve desk-based design accuracy, the more important onsite positioning and placement verification accuracy become. Even if you carefully refine shading and mounting surface conditions in PVSyst, if onsite surveying and equipment placement are ambiguous, the gap between desk conditions and reality tends to widen. That is why, on the design side, organizing energy yield forecasts and loss structures in PVSyst while, on the site side, combining an iPhone-mounted GNSS high-precision positioning device such as LRTK makes it easier to link design, construction, and operation and maintenance more consistently. Understanding PVSyst is not just about mastering the software; it is also the first step in creating a high-precision workflow that connects design and the field.