8 Steps and Points to Note for Shadow Analysis in PVSyst

Table of Contents

• Why shadow analysis becomes important in PVSyst

• Step 1 Clarify the purpose and assumptions of the shadow analysis

• Step 2 Accurately understand site conditions and surrounding obstacles

• Step 3 Arrange array layout under realistic conditions

• Step 4 Model shadow sources separately

• Step 5 Observe how shadows appear by season and time of day

• Step 6 Distinguish partial shading from electrical impacts

• Step 7 Create comparison scenarios to judge acceptable shadow levels

• Step 8 Bring results back to the field and perform reverse-checks

• Perspectives for turning PVSyst shadow analysis into practical outcomes

Why shadow analysis becomes important in PVSyst

When running PV system simulations with PVSyst, shadow analysis is not just an auxiliary check. In practice, module capacity, azimuth, tilt angle, and PCS conditions are more visually prominent and tend to be prioritized. However, what significantly affects actual generation is not how ideal the assumed conditions are, but how well those conditions can be met on site. Shadow analysis is a crucial step for confirming that feasibility.

Especially for projects aiming to use the site efficiently, there is a tendency to place as many arrays as possible. As a result, row spacing may be tightened or equipment placed right up to the site edges. Although the desktop model may promise high generation, in reality shadows in winter or at morning and evening can be strong and actual generation may fall short of expectations. The purpose of performing shadow analysis in PVSyst is to grasp in advance the gap between desk-based ideals and on-site reality.

Also, the issue of shadows is not simply about the presence or absence of shade. Where the shadow originates, how much it impacts at which times of day, and which strings the shaded modules belong to all change how generation declines. In other words, shadow analysis is not only about layout design but is deeply tied to electrical design and interpretation of generation forecasts.

In internal comparisons and design presentations, shadow analysis results also carry significant meaning. Whether you can organize and explain why a particular row spacing was chosen, why a layout was adopted, or why a proposal appears slightly inferior in generation will affect how convincing your proposal is. Understand that PVSyst shadow analysis is not just a numerical task but a process for building the rationale for design decisions.

Step 1 Clarify the purpose and assumptions of the shadow analysis

Before starting shadow analysis, you must first clarify why you are performing it. The required level of accuracy for the shadow analysis varies depending on whether it is for a rough comparison of candidate sites, validation of a single proposal, or a detailed check before proceeding to detailed design. If you begin without a clear purpose, you may waste time chasing unnecessarily detailed conditions or conversely reach conclusions based on overly coarse assumptions.

In practice, multiple purposes often overlap for the same project. It is not uncommon to want a rough estimate of generation while also seeing layout flexibility within the site and having enough supporting evidence for internal explanations. Even in such cases, deciding one primary question the shadow analysis should answer makes it easier to focus on the relevant results. PVSyst can display a lot of information, so without a clear purpose you may end up with many numbers and have difficulty making a judgment.

Organizing the assumptions is equally important. If you do not clarify which point within the site is the reference for placement, whether the array arrangement is provisional or fairly fixed, and how much surrounding obstacle information is reflected, you can misread results later. In particular, shadow analysis is highly sensitive to input conditions, so mixing provisional and confirmed assumptions leads to ambiguous results.

As a measure, before entering shadow analysis, write a one-sentence summary of what decision this analysis is meant to support, and note the confidence level of the assumptions. Simply clarifying whether it is for a rough comparison or a detailed check makes it easier to see how far to refine inputs in PVSyst. Failures in shadow analysis are more often due to insufficient clarification of purpose and assumptions than to input mistakes.

Step 2 Accurately understand site conditions and surrounding obstacles

The accuracy of shadow analysis depends on the site conditions and understanding of surrounding obstacles you input. Even if you build a neat model on PVSyst’s screen, if your grasp of actual site conditions is weak, the credibility of the results will not improve. It is particularly important to know how well you have captured potential shadow sources such as site boundaries, cut slopes, retaining walls, existing structures, fences, trees, and adjacent buildings.

In practice, people often focus on inter-equipment shadows within the site and downplay shadows coming from outside the site or from surrounding terrain. However, during morning and evening hours or in winter, distant obstacles and terrain effects can gradually impact annual generation. Conversely, obstacles you were worried about may turn out to be insignificant. The value of performing shadow analysis in PVSyst is that it lets you reorganize such intuitive concerns and expectations into explicit conditions.

Also, the quality of obstacle data matters more than quantity. Even if you try to model everything in detail, in practice the information may be incomplete. That said, it is better to prioritize and include items that are likely to have large impacts than to include nothing. Just capturing nearby elevation differences, slope direction, tall structures, and obstacles on the south, east, and west sides of arrays—conditions prone to cause shading—can significantly change the quality of the analysis.

As a countermeasure, before starting shadow analysis, list potential shadow-causing elements divided into on-site and off-site categories. It is more important not to miss items with large impacts than to input everything perfectly. To avoid failure in PVSyst shadow analysis, the starting point is to carefully organize site conditions before focusing on screen operations.

Step 3 Arrange array layout under realistic conditions

Shadow analysis is meaningful only when performed on realistic array layouts. In practice, people often first pack arrays under ideal conditions and later check for shading. But if that layout cannot actually be implemented on site, the shadow analysis results are of limited practical use. Before running shadow analysis in PVSyst, you need to check at least whether the array layout is feasible given site constraints and separation requirements.

For example, an option that tightens row spacing may look attractive based purely on expected generation. However, shadow analysis might reveal significant winter shading, making it less advantageous than assumed. Conversely, a slightly more generous layout that appears disadvantageous in capacity could be more realistic in terms of reduced shading, annual generation, and maintenance access. When comparing in PVSyst, layouts should be created under realistic conditions so that these differences are easy to interpret.

Array layout is also linked to azimuth and tilt. Changing orientation alters how rows are arranged, and increasing tilt changes required spacing. It’s important to consider layout conditions and shading together from the outset, rather than performing shading analysis after fixing layout separately. PVSyst requires sequential setting inputs, but in practice these factors are not independent.

As a measure, when creating arrays for shadow analysis, include realistic constraints such as usable site area, edge setbacks, accessways, maintenance spaces, azimuth, and tilt. Rather than checking shadows on an idealized layout, check them for layouts that might actually be adopted—those results are far more useful in practice. Basic practice when doing shadow analysis in PVSyst is to evaluate shading on candidate layouts under real-world conditions, not on layouts made solely to visualize shadows.

Step 4 Model shadow sources separately

In shadow analysis, it is important not to treat all shadows as a single lump but to separate and consider them by source. PVSyst ultimately summarizes results as annual generation and losses, but what is meaningful in practice is understanding what the shadows originate from. Self-shading between arrays, slopes and terrain shadows, and shadows from surrounding buildings or trees all require different improvement measures and prioritization.

For instance, if you treat shadows that can be mitigated by adjusting row spacing the same as shadows from off-site buildings that you must accept, design responses become unclear. In practice, you need to decide how much of the reducible shading to eliminate and how much inevitable shading to tolerate. Organizing shadows by source in PVSyst makes that judgment easier.

Understanding differences by source also makes comparative simulations easier to read. One scenario may be dominated by self-shading while another is dominated by external obstacles—different shading characteristics lead to different countermeasures. Looking only at aggregate shading losses without separating sources can cause you to miss important design differences. PVSyst provides numbers, but design judgment must be interpreted by humans.

As a measure, before running shadow analysis or when reviewing results, categorize shadow sources into self-shading, terrain shading, and surrounding obstacle shading, etc. Even if you cannot classify everything strictly, being aware of shading characteristics helps identify improvement priorities. To make PVSyst shadow analysis useful in practice, focus on where the shadows come from, not just the total amount.

Step 5 Observe how shadows appear by season and time of day

When reviewing shadow analysis results, you must consider not just annual values but also seasonal and time-of-day patterns. PVSyst’s annual totals for generation and losses are prominent, so it is easy to evaluate only by yearly numbers. However, shading does not affect the year uniformly. Some shading concentrates in winter mornings and evenings, while some has a small continuous effect throughout the year. Drawing conclusions without seeing these differences can lead to misunderstanding a proposal’s character.

In practice, people may want to dismiss a scenario thinking morning-only shading is not a problem or winter-only shading is a minor impact. Those judgments may be valid, but once you run shadow analysis in PVSyst you should verify those instincts against results. Even if annual losses appear small, if they concentrate in critical times they may not be easily ignored in comparisons. Conversely, losses that appear somewhat large might still be acceptable in the context of the entire project.

Also, examining seasonal and time-of-day bias makes it easier to explain why a proposal is advantageous or not. For example, a layout with wider row spacing may reduce winter-morning shading and offer greater stability even if annual differences are small. If you will use PVSyst results for internal comparisons, this explanatory ability is very important. Presenting the timing of impacts along a time axis makes decisions easier than simply listing numbers.

As a measure, after checking annual values, always verify seasonal and time-of-day biases in shadow analysis results. Knowing when specific shadows are effective helps you judge whether they should be treated as significant or acceptable. When conducting shadow analysis in PVSyst, understanding not just annual totals but also when shadows occur is fundamental.

Step 6 Distinguish partial shading from electrical impacts

An important point when progressing with shadow analysis is to separate the visual appearance of shading from its electrical impact. PVSyst’s partial shading simulation is useful not only because it shows the shaded area but because it lets you see how that shading affects the entire system electrically. In practice, people tend to assume that a small amount of shading results in a small drop in generation, but in reality the effect is not that simple. Losses vary depending on shadow location and string configuration.

For example, the results can differ even for the same shaded area depending on whether a thin portion of a row is shaded versus shading concentrated in a particular block. PVSyst users in charge of shadow analysis must not be reassured by visual shading alone. You need to check which blocks or groupings receive partial shading and interpret the electrical magnitude of the impact when reading results.

Having this perspective can also lead to reconsideration of string design and array partitioning. If you cannot eliminate shading, you might think about which blocks should be allowed to be shaded to minimize electrical loss. In other words, partial shading analysis is not only for confirming the presence of shadows but also provides material to consider where to change design to reduce their impact. The purpose of using PVSyst is not merely to know shading losses, but to understand their electrical implications.

As a measure, when reviewing shadow analysis results, avoid linking visual shading and generation loss one-to-one. Cultivate the habit of examining where the shading occurs and how those groupings are electrically configured—this makes result interpretation more practical. When performing shadow analysis in PVSyst, it is important to read visual shading and electrical impacts separately.

Step 7 Create comparison scenarios to judge acceptable shadow levels

In shadow analysis, it is often more useful in practice to prepare comparative scenarios and perform relative evaluation than to examine a single scenario in detail. If you look at only one scenario in PVSyst, it can be hard to judge whether the shading is large or small and whether it should be tolerated or avoided. However, laying out scenarios with slightly different row spacings, tilt angles, or accessway positions makes the meaning of shading impacts much clearer.

In practice, a scenario that completely avoids shading is not always the best. Widening spacing to avoid shading may reduce capacity or site utilization efficiency. Conversely, accepting some shading may allow for more equipment to be installed. The trade-off for where to strike the balance differs by project, so it is important to use PVSyst to compare multiple scenarios and check that balance.

Preparing comparison scenarios also helps internal explanations and decision-making. Rather than simply claiming one scenario is good, showing a shading-reduced scenario, a capacity-prioritized scenario, and an intermediate option makes it easier for stakeholders to decide. PVSyst can quantify differences, making it highly effective for relative evaluation in shadow analysis. Having comparisons also facilitates discussion about how much shading loss to tolerate.

As a measure, for projects where shading is an issue, always prepare multiple layout scenarios and clearly state what is fixed and what is varied when comparing. If the axes of comparison are well organized, PVSyst results will illustrate not only which design is better but also the differences in design philosophy. To make shadow analysis useful in practice, proceed on the premise of relative evaluation as well as absolute evaluation.

Step 8 Bring results back to the field and perform reverse-checks

Finally, you should bring shadow analysis results back to on-site conditions and perform reverse-checks. It is easy to feel reassured when calculations on PVSyst are consistent and the numbers look tidy. However, because shadow analysis depends heavily on input conditions, the validity of results can only be confirmed by comparing them to site understanding. If you rely solely on desk calculations, you may adopt a plan that looks natural on screen but is at odds with on-site reality.

For example, if on site you are clearly concerned about a morning obstacle but PVSyst shows little impact, you should review the modeling assumptions. Conversely, places you assumed would have large shading issues may turn out not to be significant. What matters is not blind faith in on-site intuition or absolute trust in PVSyst numbers, but comparing both to find inconsistencies.

Reverse-checks also make it easier to translate shadow analysis results into design improvements. You can see which rows to shift slightly, which accessway positions to change to reduce shading, or which partitioning is more natural. To truly leverage PVSyst shadow analysis in practice, do not stop at reviewing results—return to site conditions and consider the next steps.

As a measure, after reviewing simulation results, return to site constraints, surrounding obstacles, accessways, slopes, and layout plans to check whether the results make sense. Comparing drawings and on-site information makes PVSyst shadow analysis a more reliable decision-making tool. In practice, never fail to return to the field as the final step in shadow analysis.

Perspectives for turning PVSyst shadow analysis into practical outcomes

What ties together the eight steps and cautions above is the idea of not treating shadow analysis as mere loss confirmation. Clarify the purpose, understand site conditions, assume realistic array layouts, separate shadow sources, check seasonal and time biases, interpret electrical impacts of partial shading, use comparative scenarios for relative evaluation, and finally return to the field for reverse-checks. If you follow this flow, PVSyst shadow analysis becomes central to design decision-making rather than just a supplement to generation forecasts.

For practitioners, the goal is not only to eliminate shading losses. The real value lies in being able to explain how much shading should be mitigated and how much is reasonable to accept. Balancing multiple objectives—effective site use, securing generation, and preserving constructability and maintainability—is the essence of shadow analysis. Consider PVSyst as a tool to organize those trade-offs numerically and by condition.

Furthermore, to truly improve shadow analysis accuracy you must not stop at desktop comparisons. If site boundaries, terrain, slopes, surrounding structures, accessways, and existing equipment are ambiguous, the assumptions of shadow analysis will be unstable. When using PVSyst results in practice, you need to iterate between field understanding and simulation to decide which shadows to weight more heavily. Shadow analysis is both a modeling task and a process of interpreting field conditions.

In that sense, when you need to obtain more reliable on-site position checks or coordinate acquisition, it can be effective to use an iPhone-mounted high-precision GNSS positioning device such as LRTK. If on-site position information and site conditions are easier to organize, the assumed array positions and surrounding obstacle relationships in PVSyst become clearer. If you improve desktop comparison accuracy with PVSyst and support field understanding accuracy with LRTK, shadow analysis becomes not just a desk calculation but a field-rooted design decision. Conducting shadow analysis carefully not only improves generation forecast accuracy but also enhances the practical capability to connect desk work with on-site execution.