Six Introductory Points for Interpreting PVSyst's Loss Tree

Table of Contents

• Why PVSyst's loss tree becomes important

• Point 1 Understand the loss tree as showing the order in which generation is reduced

• Point 2 Read the largest losses first

• Point 3 Read numbers together with their assumptions

• Point 4 Distinguish shading, temperature, soiling, and wiring as separate causes

• Point 5 Do not confuse DC-side and AC-side losses

• Point 6 Confirm differences with comparison cases using the loss tree

• How to tie loss-tree interpretation to practical decisions

Why PVSyst's loss tree becomes important

For practitioners performing generation simulations with PVSyst, the loss tree is not just another result screen. Rather, it is the central information for sequentially understanding where and how generation is being reduced and for prompting revisions to designs and settings. If you only look at the final annual generation number, it is hard to see why that number ended up as it did and where improvements would make the biggest difference. The loss tree is the entry point for organizing that otherwise hard-to-see process.

In practice, it is tempting to judge proposals by annual generation or a few specific indicators only. Of course, final generation is important. However, two proposals that look similar in generation might differ in that one has large shading losses while the other is dominated by temperature or wiring losses. Judging without seeing this difference can cause you to discard a proposal with room for improvement or to adopt a proposal that looks good on paper but is difficult to handle in practice. Reading the loss tree means understanding not only the final result but the path that led there.

The loss tree is also useful for internal explanations. When generation does not reach expectations, merely reporting a low number is often not convincing; showing which stage each loss affects makes it easier to share causes and countermeasure directions. When people from different roles—design, sales, management, client—look at the same figures, an organized view like the loss tree is especially effective. The loss tree is not just an analytical tool for engineers but also a material for aligning stakeholders’ understanding.

Furthermore, PVSyst’s loss tree can serve as a checklist for improving simulation accuracy. If shading losses are excessively large, you may need to revisit the 3D scene or layout conditions; if temperature losses are larger than expected, check the installation environment or array density. In other words, the loss tree not only explains results but also tells you what to check next. Learning this perspective at an introductory level helps you use PVSyst not merely as a calculation tool but as a design-improvement instrument.

Point 1 Understand the loss tree as showing the order in which generation is reduced

The first step in reading the loss tree is to understand it not as a simple list of loss items but as a depiction of the order in which generation is reduced. PVSyst’s loss tree does not present the final generation abruptly; it starts from an ideal irradiance condition and visualizes how various factors gradually shave off generation. Without understanding this sequence, looking at numbers alone makes it easy to misinterpret the meaning of losses.

For example, shading losses and inverter-related losses affect generation at different stages. Shading works nearer to the irradiance and array conditions, while conversion-related losses operate at a later stage. Without understanding this difference, the same percentage loss can be unclear in terms of what to review. The loss tree does not simply list losses; it shows at which point in the generation flow they occur. Being aware of this order alone makes the numbers much clearer.

A common practical mistake is to glance at the loss tree and only pick up prominent numbers. What really matters is capturing which loss appears at which stage. If the shading assumptions are flawed, reviewing wiring losses will have little effect; conversely, adjusting array layout when equipment conditions need change may offer only limited improvement. Understanding the order in the loss tree reduces the chance of prioritizing the wrong countermeasures.

To internalize this view, get into the habit of tracing the sequence in which generation is reduced when you open the loss tree. Rather than jumping to the final annual generation, just checking which stage drops the most will raise the quality of your analysis. Treat PVSyst’s loss tree not as a list of results but as a diagram for reading the generation-decrease process—this is essential as an introduction.

Point 2 Read the largest losses first

The next important point when reading the loss tree is to prioritize the largest losses. PVSyst lists many loss elements, and it is tempting to examine every detailed item carefully. However, in practice, you do not need to treat all losses with equal weight. First identify which losses dominate the overall picture, then dive into the details; this approach makes decision-making easier.

For example, in a project where shading losses are obviously large, worrying from the start about small differences in wiring may yield little design improvement. Conversely, if shading is negligible and temperature or inverter-related losses stand out, those should be checked first. The loss tree is a screen for deciding where to start based on the overall picture. Finding the large losses first is important.

Reading large losses first also changes how you compare proposals. Two proposals that look similar in final generation might differ in that one compensates large shading losses with other conditions, while another has fewer big losses and is more stable. Grasping what is large in the loss tree reveals strengths and weaknesses that the raw numbers do not show. In practice, this difference can directly affect selection decisions.

As a practical measure, when you open the loss tree, roughly identify which losses are large and which are small. Then investigate causes from the top losses down—this helps keep the analysis focused. When interpreting PVSyst loss trees, don’t treat everything equally; finding the dominant losses first is the practical entry.

Point 3 Read numbers together with their assumptions

To correctly understand loss-tree numbers, you must read them together with the underlying assumptions, not as standalone figures. PVSyst quantifies results in an easy-to-understand way, and it is tempting to judge proposals solely by magnitudes. However, the practical meaning of the same loss rate differs depending on the assumptions behind it. Looking at numbers alone obscures the difference between losses that can be reduced and losses that must be accepted.

For instance, even if shading loss is large, if it stems from self-shading there may be room to revise row spacing or array layout. But if the shading is caused by off-site buildings, layout changes may not solve the problem. Similarly, a large temperature loss may be due to poor ventilation or dense layout, or it may simply reflect local weather characteristics—each case demands a different judgment. Viewing the loss tree only by numbers makes it hard to know where to act.

Reading numbers together with assumptions also makes it easier to explain differences between proposals. If one proposal shows large shading loss because it prioritized site utilization, and another reduces loss by limiting capacity, then the numerical difference gains meaning. PVSyst comparisons become useful in practice only when you understand what assumptions produced those numbers.

As a countermeasure, always check which settings or design conditions correspond to a given loss when you view the loss tree. Make it a habit to go back to related conditions—shading, temperature, wiring, PCS, string configuration, meteo assumptions, etc.—to reduce misreading. Keep in mind that the loss tree is not a list of numbers but the result reflecting assumptions.

Point 4 Distinguish shading, temperature, soiling, and wiring as separate causes

Practically speaking, an important skill in reading the loss tree is to treat shading, temperature, soiling, and wiring as separate causes rather than lumping them together. In practice, people tend to focus on the final percentage drop and overlook differences in the nature of each loss. However, these losses differ in causes and in how they can be improved. The same percentage means entirely different design measures for shading versus wiring losses.

For example, if shading loss is large, you may need to review the 3D scene, Near Shading, array layout, or row spacing. If temperature loss is large, consider array density, installation environment, or ventilation conditions. If soiling loss appears strong, review site conditions and maintenance assumptions. If wiring loss is the issue, improvements may be available in layout, PCS placement, or how strings are grouped. The loss tree points to design review targets by cause.

Separating these losses also clarifies differences between comparison proposals. If one proposal has low shading but high wiring losses, and another has low temperature loss but stricter soiling assumptions, you can compare proposals by character rather than by simple annual generation differences. To use PVSyst results in practice, you must look at not only the total loss amount but also the nature of those losses.

As an approach, when viewing the loss tree, separate what is affecting generation by loss type. Simply distinguishing shading, temperature, soiling, and wiring makes it clearer what to check next. For beginners interpreting PVSyst’s loss tree, organizing losses by cause is much more important than jumping to totals.

Point 5 Do not confuse DC-side and AC-side losses

When reading the loss tree, it is also important not to confuse DC-side and AC-side losses. In practice, losses are often viewed in aggregate, but in PVSyst the remedies differ depending on whether a problem occurs on the DC side or the AC side. If you cannot separate these, identifying causes and prioritizing countermeasures will be unclear.

On the DC side, modules, arrays, strings, wiring, shading, and temperature conditions have strong influence. On the AC side, PCS behavior, conversion losses, and connections to the grid are involved. If generation underperforms and you treat both sides together, it becomes difficult to decide whether to fix the array or to revisit PCS settings. PVSyst’s loss tree helps to separate these issues.

This perspective is also useful when comparing proposals. One proposal may have somewhat larger DC losses but a straightforward AC side, while another may have a well-optimized DC side but distinctive output limitation behavior. To understand a proposal’s tendencies that are not visible in annual totals, read DC and AC separately. In practice, identifying which side is strained helps greatly narrow down design corrections.

As a practical tip, when you view the loss tree, first note whether a loss pertains to the DC side or the AC side. If DC-related, return to array, string, shading, and temperature settings; if AC-related, check PCS settings and how output limitations appear. When interpreting PVSyst loss trees in practice, think of generation losses not as a single block but divided into the system’s front (DC) and back (AC).

Point 6 Confirm differences with comparison cases using the loss tree

Finally, confirm differences between comparison cases with the loss tree. In practice, it is easy to choose based solely on annual generation comparisons, but that does not reveal why differences arise. Comparing loss trees case by case shows which losses are the main contributors to the differences and which items are nearly identical. This reading is highly effective for improving the quality of comparisons.

For example, even if the annual generation difference between two proposals is small, one may have large shading loss while the other has slightly larger temperature or wiring losses. In such cases, which proposal is easier to handle in practice should be judged not only by total loss but by the internal makeup of those losses. PVSyst’s comparisons are useful not simply for ranking proposals but for organizing each proposal’s character.

Comparing loss trees also helps spot input errors or mismatched assumptions. If a certain loss is unnaturally large or small in only one case, it may be due to input differences rather than design differences. In practice, the sooner you detect such issues, the less rework you will have. PVSyst’s loss tree can be used not only to rank proposals but also to check the validity of comparison assumptions.

As a countermeasure, whenever you create comparison cases, look at loss trees side by side as well as final annual generation. Checking which losses create the differences reveals each proposal’s characteristics and possible improvements. To understand PVSyst’s loss tree at an introductory level, make a habit of reading differences within comparisons, not only analyzing single cases.

How to tie loss-tree interpretation to practical decisions

What the six points above have in common is: do not treat the loss tree as a simple list of results. Understand the order in which generation is reduced, prioritize large losses, read numbers together with assumptions, treat shading/temperature/soiling/wiring as separate causes, separate DC and AC sides, and finally confirm differences with comparison cases. When you can follow this flow, PVSyst’s loss tree becomes not just a series of numbers but a tool for improving design.

For practitioners, the important thing is not to lament that the loss tree shows large losses. The real value is being able to judge where those losses originate, what to change to reduce them, and what must be accepted. PVSyst is not merely a tool to show theoretical generation; it decomposes the reasons for generation reduction and feeds them back into design decisions. That is why skill in reading the loss tree becomes increasingly important with more simulation experience.

Also, improving the accuracy of loss-tree interpretation requires not finishing the exercise as a desk-based simulation. If site conditions—slopes, buildings, trees, access routes, maintenance paths, string segmentation, etc.—are ambiguous, it becomes hard to know how much to trust the loss-tree numbers. When using PVSyst results in practice, repeatedly looping between site understanding and simulation to verify the numbers’ background is necessary. The loss tree is both a calculation result and a reflection of site conditions.

In that sense, when you want to make on-site position confirmation and coordinate acquisition more reliable, using high-precision GNSS positioning devices that attach an iPhone, such as LRTK, can be effective. If site location information and conditions gathered on site are easier to organize, the assumptions for shading, layout, access, and zoning used when reading the PVSyst loss tree become clearer. Creating a workflow that improves desktop comparison accuracy with PVSyst and supports on-site accuracy with LRTK makes loss-tree interpretation not just analysis but on-site–grounded design decision-making. Reading the loss tree carefully thus not only improves the accuracy of generation forecasts but also strengthens the practical capability to link desk work and field work.