How to Use PVSyst in 7 Steps [For Beginners]

Table of Contents

• Prerequisites to grasp before learning how to use PVSyst

• Step 1 Decide in advance what you want to know

• Step 2 Organize the installation site and meteorological conditions

• Step 3 Enter the system conditions

• Step 4 Set the layout, azimuth, and tilt angles

• Step 5 Make shading and loss assumptions closer to reality

• Step 6 Run the simulation and check the results

• Step 7 Compare cases and organize the report

• Common pitfall areas when using PVSyst

• Summary

Prerequisites to grasp before learning how to use PVSyst

There is a mindset you should have at the outset of learning how to use PVSyst. Namely, this type of generation simulation is not meant to produce a single definitive answer at once, but to compare design proposals while organizing the underlying assumptions. Beginners tend to try to produce perfectly accurate numbers in one go, but in practice there are few projects where all conditions are fixed from the start. Site conditions, equipment configurations, and actual construction conditions become more concrete as the study progresses. Therefore, it is important to first build a model based on reasonable assumptions and then improve accuracy by repeating comparisons and reviews.

Also, do not think simply that more input items in a simulation like PVSyst always lead to higher accuracy. It is true that entering detailed conditions can bring the model closer to reality, but forcing many values with unclear justification can create a superficially detailed but unstable model. What matters is entering data with a clear understanding of what is fixed and what is assumed. If some parts proceed as assumptions, they should be used for comparison with that awareness and not treated as fixed values.

Another important point is not to focus solely on annual energy yield. In practice, annual total generation is of course important, but it alone does not determine whether a project is good or bad. Check whether monthly imbalances are too large, where shading and losses are effective, whether the installation layout is realistic, and whether maintainability or constructability are compromised. In other words, learning how to use PVSyst is not just learning the software operations; it is also learning how to interpret the meaning of the results.

With this mindset, you are less likely to be swayed by individual on-screen settings. You will be able to organize what you want to compare, which conditions are important, and what should be reviewed later. Below, following this practical thinking, we proceed in seven steps that are easy for beginners to follow.

Step 1 Decide in advance what you want to know

The first step is to clarify what you want to learn from the simulation before opening the software. If you start with that unclear, filling input fields can become the objective itself, and you will not know how to use the results. In practice, simulations are performed to support decision-making. Therefore, first organize what decisions you want to make using the simulation.

For example, in an initial project study you will often want to know roughly how much energy can be expected at this site, the approximate scale of capacity, and which candidate options look promising. At this stage, capturing the differences in energy yield due to different conditions is more important than pursuing extremely detailed settings. On the other hand, in progressed design projects, more specific comparisons are required, such as differences in azimuth and tilt, the impact of shading, the balance between the DC and AC sides, and how to estimate losses. In short, the settings you emphasize in PVSyst change depending on what you want to know.

Be sure to make the comparison axes as clear as possible. Decide whether you will fix the installation site and only compare tilt angles, keep capacity the same and compare different layouts, or observe how losses behave with different equipment configurations. If you change multiple conditions significantly at once, it will be hard to explain the reasons for any differences. For simulations that are easy to evaluate in practice, it is important to decide at the outset what to fix and what to make variables.

Also decide in advance which outputs you will focus on. Do you only need the annual energy yield, or do you also want to check monthly generation trends and the potential for curtailment at peak times? The items to confirm will vary. Projects focused on self-consumption and those prioritizing annual totals may evaluate the same generation differently. To avoid confusion in using PVSyst, clarifying how the results will be used is the starting point.

Step 2 Organize the installation site and meteorological conditions

Next, organize the installation site and meteorological conditions. No matter how elaborate your layout or equipment configuration is, if the foundational site conditions are off, the overall results will drift. Therefore, beginners should pay particular attention to this from the start.

For the installation site, simply entering an address or region may be insufficient. Coastal and inland areas, plains and mountainous regions, places that tend to be hot and places with good ventilation may have different irradiance and temperature conditions even within the same prefecture. On large sites, there can be elevation differences within the site and influences from surrounding terrain. In other words, treat the installation site as the actual field conditions, not merely a place name.

Handling meteorological conditions is also important. PVSyst evaluates generation based on irradiance and temperature conditions, but you must consider how well those data represent the actual site. Beginners tend to think that using the loaded data as-is is sufficient, but in practice you should consider whether the data are representative values, whether they contain biases for certain periods, and how well they reflect terrain differences. Especially when using expected generation for internal or external explanations, the appropriateness of the meteorological conditions directly affects the credibility of the numbers.

Also, identify shading factors early on when organizing the installation site. Shading causes can include neighboring buildings, trees, retaining walls, equipment-row spacing, and distant terrain—there are multiple sources. Even if you cannot build a complete shading model at the initial stage, organizing information such as what lies in which direction, whether shading occurs easily in the morning and evening, and whether seasonal differences are likely to be significant will improve later setting accuracy. Proceeding with awareness of shading as a risk factor is better than completely ignoring it, as it reduces the likelihood of misinterpreting results.

Temperature also significantly affects generation. Even in regions with strong irradiance, output reduction due to temperature rises may not be negligible. The way temperature impacts output varies with ventilation and layout conditions at the installation surface, so do not judge by irradiance alone. When using PVSyst, you should capture the site not only by irradiance but also by thermal environment and installation conditions.

Step 3 Enter the system conditions

Once the installation site and meteorological conditions are organized, enter the system conditions. Here you set the skeleton of the equipment: how much capacity to install, how to balance the DC and AC sides, and how to consider the connection configuration. Although this step looks like entering numbers, it is actually an important process that reflects design policy.

First consider not how much you can install, but how much can realistically be implemented. For roofs, you need to consider shape, obstacles, clearances, and maintenance routes; for ground-mounted systems, consider row spacing, terrain, and constructability. Even if the area seems to allow a large installation on paper, effective area may shrink when taking shading and maintenance spaces into account. Therefore, capacity setting should be judged not by the simple maximum but by the amount that constitutes a feasible design.

Next, the balance between the DC and AC sides is important. Slightly oversizing the DC side can increase annual energy yield under variable irradiance conditions, but it may also lead to clipping when the AC side hits its limit during certain periods. This balance depends on whether you prioritize annual total, want to reduce peak-time curtailment, or emphasize equipment rationality. Beginners tend to think there is a single correct ratio, but in practice it is more reasonable to compare multiple options according to the project’s objectives.

The approach to connection configuration is also important. If irradiance or shading conditions differ by installation surface, how you combine them affects generation behavior. Treating faces with different orientations or different shading exposures as identical can produce results that are unrealistically good or bad relative to the real situation. In other words, entering system conditions in PVSyst is not just listing rated values; it requires imagining how the system will operate in the field and configuring settings accordingly.

If detailed equipment configuration is undecided at the initial stage, proceed with conservative yet reasonable assumptions. Importantly, keep track of which items are still assumptions. That makes it easier to see which results will be affected when the configuration changes later. Treat system condition entry carefully as a stage that creates the framework for design decisions, not as something to be glossed over because everything can be changed later.

Step 4 Set the layout, azimuth, and tilt angles

Once system conditions are set, next set the layout and the azimuth and tilt angles. This step directly affects energy yield and therefore attracts attention, but it is also where beginners are most likely to be misled. That is because settings that look ideal when considering only generation numbers are not necessarily the best for the actual site.

For example, orientations or tilts that appear advantageous purely in terms of theoretical energy yield may increase row-to-row shading, reduce usable installation surface, or complicate construction and maintenance. Conversely, a layout that looks slightly disadvantageous by generation numbers might allow more capacity to be installed comfortably in practice and thus be superior overall. When designing a layout in PVSyst, you must judge not by individual numbers but by the feasibility of the entire layout.

On roofs, you are often constrained by existing roof orientation and slope and may not be free to optimize. Even then, decisions on which surfaces to prioritize, how much clearance to take, and how to treat areas prone to shading will affect the results. For ground installations, row spacing, layout density, maintenance routes, and terrain conformity are major discussion points. Recognize that a layout that fits visually and one that operates without issues after construction are not necessarily the same.

Azimuth and tilt should not be optimized in isolation. Increasing tilt can improve incident irradiance but worsen row-to-row shading; lower tilt may look disadvantageous but could be beneficial when balancing shading and site utilization. Therefore, rather than sticking to a single setting, compare multiple cases with aligned conditions and interpret the meaning of the differences.

Be careful about how you compare. If you change azimuth, try to keep capacity and installation position assumptions as consistent as possible; if you change tilt, fix other conditions so that the reason for differences is easy to understand. Beginners often change many items at once, which makes it difficult to explain result differences. In layout settings, it is important not only to increase energy yield but also to be able to explain which conditions affected the results.

Step 5 Make shading and loss assumptions closer to reality

Where accuracy tends to vary most in PVSyst is in how shading and loss assumptions are handled. Beginners may feel that energy yield is almost determined by irradiance and capacity, but in practice the accumulation of shading and various losses greatly influences the results. Discrepancies from actual generation often come from coarse estimates of these loss conditions.

First, do not think of shading as a binary presence-or-absence issue. Shading arises not only from external factors such as neighboring buildings and trees but also from your own layout, like row spacing and roof shapes. Moreover, shading impacts vary by season and time of day. For projects with suspected shading, organize as concretely as possible where and to what extent shading is likely before setting it in the model. Ignoring shading tends to overestimate yield, while overestimating it leads to unnecessarily conservative results.

Loss assumptions also deserve similar care. There are multiple losses to consider in practice: temperature-induced output reduction, wiring losses, conversion losses, variability, soiling, downtime, and more. The important point is not to blindly trust default values or to layer many conservative losses without justification. Determine which losses are likely to be dominant for the project. If the site tends to get hot, emphasize temperature effects; if morning and evening shading is significant, estimate shading carefully.

Also avoid double-counting the same phenomenon. For example, if shading is partly represented in the layout, and you then also apply the same reduction across another loss item, the overall result becomes overly pessimistic. Conversely, assuming something is absorbed elsewhere and setting nothing anywhere can produce overly optimistic numbers. Treat PVSyst’s loss settings as a task of organizing which phenomena are represented where, not as merely filling items.

Furthermore, losses that appear small on an annual average can have biased effects in particular months or time periods. Therefore, check monthly trends as well as annual totals. Making loss assumptions closer to reality does not mean making values more granular; it means modeling on-site reduction factors without duplication or omission and in a way that can be explained. Adopting this approach brings PVSyst usage closer to practical work.

Step 6 Run the simulation and check the results

After setting the necessary conditions, run the simulation and check the results. However, do not rejoice or despair simply by looking at the annual energy number. In practice, what matters is interpreting whether the results are consistent with your assumptions and where there is room for improvement.

First check whether the results deviate significantly from intuition. Consider whether values are extremely good or bad given the site, capacity, azimuth, tilt, shading, and loss assumptions. Beginners tend to accept software outputs as correct, but in practice it is better to start with a skeptical stance. Input omissions, unit misunderstandings, duplicated conditions, and insufficient shading settings can all cause large deviations. If something feels off, use that as a starting point to review the settings.

Next, inspect monthly generation trends. Even if annual totals are similar, a plan that concentrates generation in summer versus one that also secures generation in winter may be evaluated differently as a project. Depending on demand patterns and operational policies, seasonal stability can be more important than total generation. Checking monthly behavior also helps you see which seasons azimuth, tilt, shading, and losses have the strongest effects.

Also pay attention to the breakdown of losses. If you know which factors are reducing generation the most, improvement directions become clear. Large shading suggests revisiting the layout; a strong temperature effect suggests rethinking installation conditions or ventilation. If conversion or connection assumptions are unreasonable, return to the system conditions. In other words, reading the results is not about judging good or bad but about finding what to improve next.

If you are comparing multiple cases, interpret the differences carefully. Even if one option slightly exceeds another in annual generation, if that comes with increased shading risk, reduced maintainability, or higher construction difficulty, another option may be more reasonable in practice. PVSyst presents numbers, but final evaluations should be comprehensive decisions that include constructability and operability, not numbers alone.

Step 7 Compare cases and organize the report

When using PVSyst in practice, the final important step is comparing cases and organizing the report. Running a single simulation and stopping leaves results as isolated numbers. In practice, you need to be able to explain why one option is better and what changes when a condition is altered. Therefore, recording and organizing comparisons is not mere administrative work but a crucial process to improve the quality of design decisions.

In case comparisons, organize so that the factors producing differences are clear. For example, separate cases where azimuth is changed, tilt is changed, shading conditions are changed, and capacity balance is changed so you can see which conditions affected the results and to what extent. If this is not organized, it will be ambiguous later when explaining to stakeholders why a particular option was chosen. The value of comparisons lies not in the existence of differences but in understanding the reasons behind them.

When organizing reports, always include assumptions along with results. If only annual energy is recorded, without knowing the meteorological conditions, layout, or loss settings used to calculate it, the results are hard to reuse later. In practice, project conditions often change mid-course. Capacity may change, installation surfaces may change, and perceptions of shading may be revised. If assumptions are organized, it becomes clear what to modify.

Also tailor reports to the intended audience. Design personnel may need explanations that delve into loss and shading reasoning, while decision-makers may prefer concise presentation of comparison results and reasons for selection. Rather than simply listing PVSyst outputs, prepare the material with awareness of who will decide what.

If you complete this step carefully, PVSyst becomes not just a calculation tool but a tool that supports comparative studies and accountability in design proposals. For beginners to step forward, learning this way of organizing matters more than mastering the operations themselves.

Common pitfall areas when using PVSyst

We have reviewed the flow in seven steps; finally, note the points where beginners often stumble. One of the most frequent mistakes is making the act of filling inputs the goal. PVSyst has many settings, so it is easy to feel you have progressed by simply filling the screens, but that leaves unclear what you are comparing and deciding. First set the purpose, then prioritize organizing conditions that relate to that purpose.

Another common mistake is blindly trusting default values. Defaults are only a starting point and should be checked for reasonableness per project. Using loss and installation condition numbers without review reduces result credibility. Conversely, entering harsh values repeatedly without basis is also a problem. Avoid bias toward optimism or pessimism and set values that are explainable in light of the project.

Deciding based only on annual energy is also a typical error. If you do not check monthly imbalances, shading behavior, loss breakdowns, and layout feasibility, the results are hard to use for practical decisions. When comparing multiple options, you must look beyond total differences to see where those differences come from. Small differences can mean major design implications depending on underlying conditions.

If your comparison method is sloppy, you will not learn much even by creating multiple cases. Changing many conditions at once makes it impossible to know the reason for differences. Focusing on one or two elements at a time makes results easier to understand and leads to actionable improvements. Those who use PVSyst well design their comparison conditions intentionally rather than creating many cases indiscriminately.

Finally, do not assume simulation results are the final conclusion. Generation simulations are extremely useful, but they are models based on assumptions. In practice, site verification, construction conditions, maintainability, and actual positional relationships remain elements that cannot be fully determined on paper alone. That is why thinking about what to check on-site using the results is the truly practical way to use them.

Summary

Organizing how to use PVSyst for beginners into seven steps looks like this: first define the objective, organize the installation site and meteorological conditions, enter the system conditions, compare layouts and azimuth/tilt, make shading and loss assumptions closer to reality, interpret simulation results, and finally compare cases and organize reports. Understanding this flow enables you not only to generate numbers but also to see how to apply those numbers to design and proposals.

Beginners tend to focus on the mechanics of operation, but what matters in practice is understanding which assumptions to make, which conditions to compare, and which results to use for decision-making. PVSyst may look difficult because of many input items, but if you break the flow down, each part is manageable. Don’t seek perfection at first; create models with reasonable assumptions that can be compared, and improve them iteratively—that is the quickest path to mastery.

After refining simulations at the desk, it is important to consider how to verify the plan on-site. Even if a design is feasible on paper, unclear position setting or on-site confirmation can cause deviations during construction. LRTK, an iPhone-mounted GNSS high-precision positioning device, can be useful here. It helps efficiently confirm equipment placement, capture coordinates on-site, and check positions before and after construction, making it a good complement to desk simulations. By using PVSyst to solidify the design direction and LRTK to verify positions on-site, you can improve the accuracy and speed from study to construction verification.