Introduction to Using PVSyst | 10 Steps from Initial Setup to Energy Yield Calculation

Table of Contents

• The overall picture to grasp before you start using PVSyst

• Step 1 Initial settings and project creation

• Step 2 Prepare the calculation site and meteorological data

• Step 3 Decide installation orientation and tilt angle

• Step 4 Enter the system configuration

• Step 5 Check consistency of capacity and series/parallel connections

• Step 6 Set loss conditions

• Step 7 Reflect the horizon and distant shading

• Step 8 Model proximity shading

• Step 9 Run the simulation

• Step 10 Interpret the energy yield calculation results

• Common practical pitfalls

• Summary

The overall picture to grasp before you start using PVSyst

Many practitioners who look up how to use PVSyst are first unsure where to start, how much configuration is needed to improve calculation reliability, and how to read results so they lead to on-site decisions. Especially when someone is responsible for energy yield simulation for the first time, filling in screen fields in order tends to become the goal itself, and it is not uncommon for calculations to finish while the meaning of inputs remains vague.

PVSyst is software designed with the engineering philosophy of creating multiple calculation scenarios per project and comparing them while progressively reflecting installation conditions, meteorological conditions, system configuration, various losses, distant shading, and proximity shading. Official materials also recommend creating a basic scenario with minimal conditions first, then adding loss and shading details afterward. In other words, rather than trying to enter everything perfectly from the start, it is more practical when using PVSyst to create a coarse model and then refine it.

pvsyst.com

pvsyst.com

This article assumes grid-connected projects common in practice and organizes the workflow from initial setup to energy yield calculation into 10 steps. It avoids specific manufacturer or device names and focuses on a generic approach applicable to many projects. By the time you finish reading, you should understand how to use PVSyst not merely as a sequence of screen operations but as a procedure to quantify and compare design conditions.

Step 1 Initial settings and project creation

The first thing to do is to create the project container correctly. Here, a project is not just a filename but a unit that manages location information, meteorological data, calculation conditions, and derived scenarios for comparison. In PVSyst, the typical workflow is to have multiple simulation scenarios under a single project for comparison. Therefore, make the project name understandable later on by including region, purpose, and distinguishable installation conditions so it is easier to manage.

pvsyst.com

Beginners often stumble by blurring the distinction between projects and calculation scenarios. For example, when changing only the orientation on the same site, it is easier to track differences if you create derived scenarios within the same project rather than creating separate projects. Conversely, if the location or meteorological conditions differ, it’s clearer to split into separate projects. In practice, think of a project as the site unit and calculation scenarios as the units for comparing layouts and loss conditions to avoid confusion.

Also, decide on a save-naming rule at the outset. If you start work with provisional names, similar files will accumulate and it becomes unclear which is the latest. Including region name, project name, capacity range, orientation conditions, and creation date in a consistent order reduces mistakes when handing files within a team. Using PVSyst effectively involves not only screen operations but also organizing information with comparison in mind.

Step 2 Prepare the calculation site and meteorological data

A major early branching point that affects the accuracy of energy yield calculations is the site settings and meteorological data. No matter how carefully you enter system configuration, if the assumptions about irradiation, temperature, wind, and so on are off, both annual and monthly yields will diverge from reality. Therefore, when using PVSyst, it is essential to check the consistency of meteorological conditions before selecting equipment.

The official tutorial also shows selecting the site and meteorological data after creating the project, and using custom site information or available meteorological files as needed. The official documentation organizes the handling of meteorological conditions as a large set of functions, including managing the site database, comparing meteorological data, importing custom files, and generating synthesized time series data. In other words, meteorological data are not just supplemental information but the foundation of the simulation.

pvsyst.com

It is important not to be reassured merely because a site name is nearby. Coastal vs. inland, high elevation vs. plains, basins vs. coastal areas—meteorological characteristics can vary significantly even within the same prefecture. In practice, first select candidate sites and check whether the annual irradiation and temperature trends for that site are consistent with the site’s actual characteristics. If multiple meteorological datasets are available, record which dataset was adopted in the project notes. This ensures that the assumptions are shareable within the team and that the calculation results do not take on a life of their own later.

Additionally, surrounding conditions such as ground albedo should not be ignored. Standard values are often acceptable, but in snowy regions or locations with long-lasting bright surfaces, you should reassess the appropriateness of the setting. Handling meteorological data includes not just choosing numbers but confirming that they are consistent with the site’s reality. Doing this carefully will significantly reduce rework in later stages.

Step 3 Decide installation orientation and tilt angle

Next is setting the orientation and tilt of the installed surface. Many people searching for how to use PVSyst assume that choosing a single optimal angle is the correct approach, but in practice this is not always the case. Constraints such as site shape, surrounding shading, row spacing, building orientations, maintenance access, and mounting structure often mean that a setting that is reasonable within the overall conditions is chosen over a theoretical optimum.

The official tutorial shows deciding on a tilt and orientation for the fixed plane in the initial scenario and then adding other conditions for comparison. In other words, orientation and tilt are important inputs that become the baseline for later scenario comparisons rather than something you set once and forget. Since PVSyst allows comparing multiple scenarios within a project, it is practical not to narrow down to a single scenario at the start but to keep several candidate patterns.

pvsyst.com

A tip at this stage is not to consider the installation angle in isolation. For example, increasing tilt can improve irradiance conditions for each module, but if row spacing is not widened, self-shading increases and the site’s overall installed capacity may decrease. Conversely, reducing tilt can make it easier to increase installed capacity but may change dirt accumulation, drainage, and seasonal generation balance. Therefore, in PVSyst it is easier to interpret results when orientation and tilt are considered together with capacity, shading, and maintenance.

When evaluating installation conditions, first create a standard baseline scenario, then separately test variations in orientation, tilt, and row spacing to make it easier to see what affects annual generation. Changing many variables at once from the start makes it difficult to determine why results improved or worsened. Ease of comparison is a major value of using PVSyst.

Step 4 Enter the system configuration

After deciding orientation and tilt, the next step is entering the system configuration. Here you define how the generation-side components are combined. PVSyst is designed to calculate not only surface conditions but also system configuration and its consistency within a project, so the roughness of inputs at this stage affects later result reliability. The official documentation explains that in detailed simulations, in addition to defining the surface, you select the system configuration and, if necessary, receive support for designing the number of series or parallel strings.

pvsyst.com

What matters here is to be aware not just of matching nominal capacity but of device behavior and operating conditions. Even if the sum of rated outputs matches, if voltage ranges, temperature conditions, input imbalance, or circuit partitioning are inappropriate, the configuration will be unrealistic. PVSyst is good at helping to confirm such consistency, but designers still need at least a minimum understanding of circuit concepts.

In practice, it is easier to decide the rough capacity first and then refine whether the circuit configuration is feasible. Some projects have installed capacity determined by site constraints first, while others are reverse-engineered from grid connection conditions or target output. In any case, make sure you can explain why you chose that configuration when entering it. PVSyst results are persuasive, but if the assumptions are opaque, internal and external explanations become weak.

For grid-connected projects, do not be satisfied with looking only at capacity ratios; keep seasonal and hourly behavior in mind. In regions where time near maximum output is short, consider annual revenue and curtailment relationships, not just apparent overloading ratios. When learning to use PVSyst, treat configuration entry not as mere registration but as a step to quantify design intent.

Step 5 Check consistency of capacity and series/parallel connections

After entering the system configuration, refine the consistency of capacity and series/parallel connections. This is a step beginners tend to overlook, but it is an important point that can undermine the assumptions of the energy yield calculation. It is understandable to want to see annual generation quickly, but if you run calculations with ambiguity here, you may get seemingly plausible numbers that are not viable designs.

The official tutorial introduces a design assistance screen where you check available area, module configuration, voltage conditions, and whether the circuits are feasible. In other words, PVSyst is not just an irradiation calculator but also helps confirm whether the system lies within a practical range. Whether the installation site is cold or warm and how you treat high summer temperatures changes acceptable design approaches.

pvsyst.com

There are, roughly speaking, three practical checkpoints. First, ensure voltage does not rise too much during winter low temperatures. Second, ensure the system is not likely to operate outside its range during summer high temperatures. Third, ensure the circuit partitioning aligns with field construction and maintenance realities. Even if it works on the PVSyst screen, on-site constraints such as cable length, combiner box layout, or partitioning can make it hard to adopt as-is. Therefore, check consistency with the bridge between desk calculations and construction planning in mind.

Also, for projects with multiple installation surfaces, do not force everything under a single representative condition. Grouping surfaces with different tilts or orientations into one condition may look simpler but can reduce both calculation accuracy and implementability. Divide conditions into units that reflect actual circumstances as much as possible and clearly document what you combined and what you separated—this aids later explanations.

Step 6 Set loss conditions

The area where the gap between beginners and practitioners shows most in using PVSyst is loss settings. Energy yield simulation must consider not only how much irradiance arrives but how much of that irradiance converts into usable electrical power. The official documentation shows that detailed losses—soiling, incidence angle losses, temperature behavior, wiring losses, module quality differences, mismatch, downtime rate, and so on—can be set.

pvsyst.com

A common mistake is to apply all losses uniformly large to be conservative. Although this may seem cautious, stacking losses with different bases makes it unclear which factors truly reduce generation. For example, the effects of soiling and downtime are different in meaning, and temperature loss and wiring loss require different countermeasures. In practice, rather than lumping losses together, separate them by cause so that you can identify mitigation measures.

Start by creating a baseline scenario with standard conditions, then add deltas according to site circumstances. Whether the site is coastal with salt or soiling concerns, near agricultural land with a lot of dust, in a snowy region with seasonal downtime, or has a particular maintenance frequency will change appropriate values. PVSyst’s strength is the ability to break down these factors as losses and visualize their effects on annual generation.

Loss settings also serve as a starting point for internal agreement. Sales may prefer optimistic yields while engineering prefers conservative assumptions, but if you can separate and explain loss factors in PVSyst, it becomes easier to discuss which assumptions and ranges are appropriate. Sharing the logic of loss conditions improves project accuracy more than arguing only about final numbers.

Step 7 Reflect the horizon and distant shading

When reflecting surrounding site conditions, first address the horizon and distant shading. Projects where morning and evening irradiance is reduced by mountain ranges, distant buildings, or terrain undulation will show large monthly generation biases if this is ignored. The official documentation explicitly treats horizon profiles as a second stage of detail and regards distant shading as an important element to raise precision beyond the basic scenario.

pvsyst.com

An important point with distant shading settings is not to confuse them with proximity shading. Distant shading mainly cuts out parts of the visible sky and affects hourly irradiance conditions, but it is different in nature from complex shadows cast by nearby structures. Therefore, it is easier to first capture the major losses from the horizon and surrounding terrain, and then add proximity shading if necessary.

In practice, identify obstacles affecting morning and evening using azimuth diagrams, site photos, topographic maps, and existing drawings. If entered carelessly here, morning and evening generation in winter can appear unnaturally high or be underestimated. Horizon settings are not flashy, but they affect not only annual generation but also time-of-day output patterns, so they are particularly important in projects involving storage or output control.

Also, after adding distant shading, compare results before and after. Knowing which month, which time of day, and how much difference occurred strengthens explanations to external parties and internal reviews. PVSyst’s design for comparison makes this differential check a useful habit to raise precision.

Step 8 Model proximity shading

Among PVSyst usage tasks, proximity shading is the most difficult. Official materials explain that proximity shading is the visible shadow produced by nearby objects and requires detailed three-dimensional descriptions, making it one of the hardest parts for beginners. Moreover, proximity shading not only reduces irradiance but the electrical loss patterns change depending on wiring and module interconnections, making interpretation more complex than distant shading.

pvsyst.com

When dealing with proximity shading in practice, first decide what to reproduce and to what level. It is not necessary to model every obstacle in detail; prioritize elements that affect generation. For example, self-shading between rows, fences and retaining walls, equipment racks, and shadows from nearby buildings that influence generation throughout the year should be addressed first. Overmodeling elements with minimal impact wastes effort relative to the precision gain.

The official documentation states that proximity shading calculations are done for hourly solar positions and handle not only direct components but also effects on diffuse and ground-reflected components, and to keep computational load manageable, PVSyst uses shading coefficient tables according to solar altitude and azimuth. You can operate without knowing these mechanisms, but understanding them is important for interpreting results. If loss is small despite visible shading, or losses are larger than expected, considering which component is affected helps comprehension.

pvsyst.com

Be careful about handling electrical effects of shading as well. Official materials provide both simplified methods according to wiring groupings and more detailed electrical calculations based on module layout. That means the same shadow can produce different losses depending on how circuits are arranged. When setting proximity shading, consider not only the visible shadow but also which circuit it affects to get a practice-oriented assessment.

pvsyst.com

Step 9 Run the simulation

Once you have configured up to this point, finally run the simulation. However, in practice this moment is not the goal; rather, it is the start of comparison and verification. The official tutorial also shows creating a basic scenario with minimal conditions and then saving derived scenarios that add shading and losses in sequence for comparison. The important part of using PVSyst is not hitting the correct answer in one run but tracking how differences in conditions produce differences in results.

pvsyst.com

Before running simulations, check for missing inputs and consistency errors. In particular, confirm whether site conditions are correct, orientation and tilt are as intended, circuit configuration is feasible, losses are not double-counted, and shading settings are neither lacking nor excessive. Even if the calculation itself finishes in minutes, spending time reviewing assumptions is worthwhile. In practice, time spent checking assumptions affects result quality more than calculation runtime.

When creating derived scenarios, avoid changing too many things at once. For example, changing orientation, losses, shading, and capacity ratio simultaneously makes it hard to identify which condition caused result differences. Separate calculation scenarios by the points you want to compare and record reasons for changes in project notes to make reviews much easier. Using PVSyst as a comparison tool gives it value beyond mere calculation results.

Step 10 Interpret the energy yield calculation results

After simulation, the first thing you may want to see is annual generation, but judging by that alone is risky. The official documentation explains that many simulation variables can be checked monthly, daily, and hourly, and that loss diagrams are particularly useful for identifying system design weaknesses. In other words, PVSyst results should be read not just for annual totals but to understand where losses occurred.

pvsyst.com

Practically, first check annual generation, specific yield, performance ratio, monthly generation distribution, and the loss breakdown. Even if annual generation looks high, if temperature losses in summer are too large or shading impacts are concentrated in winter mornings and evenings, operational issues remain. Conversely, a scenario with a slightly worse annual number but a clear, consistent loss breakdown that aligns with site conditions may be easier to adopt.

When looking at loss diagrams, do not just search for the largest items; consider whether that loss can be improved by design changes or only by operational improvements. Temperature and wiring losses often have room for design improvement, whereas regional meteorological characteristics cannot be changed. For shading losses, decide whether layout changes can reduce them or whether they must be accepted due to site constraints.

Additionally, monthly and hourly trends provide practical insights that annual totals do not. For instance, scenarios with weaker mornings/evenings versus those leaning toward midday can have different values despite equal annual generation. Reading results in the context of output control, the customer’s consumption pattern, and maintenance planning turns PVSyst outputs into information usable for decision-making.

Common practical pitfalls

Even if you think you have learned how to use PVSyst, several practical pitfalls commonly cause mistakes. First, skipping validation of meteorological data appropriateness. Assuming a nearby site is good enough overlooks terrain and climate differences. Second, lumping losses together too roughly. This mixes losses that can be improved with those that must be accepted, making it hard to feed results back into design.

Third, oversimplifying shading settings or, conversely, over-modeling them. Oversimplification reduces accuracy; over-detailing yields little benefit relative to effort. The key is prioritizing shading elements that affect annual generation. Fourth, creating comparison scenarios sloppily so you cannot tell what was changed. Simulations that cannot explain differences are hard to use in practice even if the numbers look clean.

Finally, separating simulation results from site realities. Desk designs may be feasible in calculation but on the actual site there may be insufficient clearances, interference with delivery routes, difficult maintenance access, or influence from surrounding equipment. PVSyst results are extremely useful, but their value increases when combined with on-site condition checks. Using PVSyst with iteration between design and site is the shortest route to improving practical accuracy.

Summary

Using PVSyst is not just about initial settings and pressing the calculate button. The essence is creating a project, preparing site and meteorological data, deciding orientation and tilt, confirming system configuration and series/parallel consistency, and sequentially reflecting losses, horizon, and proximity shading while comparing multiple scenarios to approach an optimal solution. Rather than aiming for perfection from the start, rigorously creating a basic scenario and then adding detail makes PVSyst a very powerful practical tool.

pvsyst.com

To further increase practical accuracy, do not stop at desk simulations—confirm on-site terrain, obstacles, construction constraints, and maintenance conditions. In particular, the quality of pre-simulation assumptions changes greatly depending on how quickly and accurately you can collect on-site records such as post-formation ground undulation, actual clearances around equipment, maintenance access routes, and photo-documented site conditions. A useful tool here is LRTK, a high-precision GNSS positioning device that mounts on an iPhone. Using LRTK makes it easier to collect high-precision photos with location information and point clouds on site, linking pre-design checks, as-built verification after construction, and maintenance record sharing in one workflow. Connecting desk energy yield calculations with measured on-site information makes PVSyst simulations an even more practical asset.