Six Important Points When Accounting for Degradation in PVSyst

Table of Contents

• The importance of accounting for degradation in PVSyst

• Point 1: Don’t treat degradation as a single fixed value

• Point 2: Separate first-year performance and long-term performance

• Point 3: View the impact on the entire system, not just the module

• Point 4: Align assumptions in comparative simulations

• Point 5: Do not separate temperature, soiling, shading, and maintenance conditions

• Point 6: Decide how to read results and back-check assumptions

• How to turn PVSyst degradation modeling into practical outcomes

The importance of accounting for degradation in PVSyst

For practitioners running PV generation simulations in PVSyst, handling degradation is an assumption that is easy to postpone, yet it is a critical premise that greatly affects long-term generation forecasts. The first-year annual yield is easy to compare and explain internally, so attention naturally focuses there. However, in real projects, evaluations often include how the system will appear several years or a decade later, and if the approach to degradation is vague, the overall credibility of the simulation tends to weaken.

In practice, even with the same system configuration, how you set degradation can greatly change the impression of long-term generation. An option that looks favorable in the first year may, when accounting for long-term expectations, appear less stable than an alternative. Conversely, overestimating degradation can prematurely make a viable option look unfavorable. The purpose of reflecting degradation in PVSyst is not merely to reduce generation numbers, but to create a realistic comparison axis that assumes long-term operation.

Degradation does not only mean a decline in module performance. Factors that change how generation looks in practice include temperature conditions, soiling, wiring, partial shading, and maintainability. Treating degradation as a single number can fail to adequately represent the long-term behavior of the system. When handling degradation in PVSyst, read it not merely as an annual decline rate input, but as a condition to shape the long-term appearance of the whole system.

Also, in internal checks and proposal materials, it is important to be able to explain why a particular degradation premise was chosen. Numbers organized under long-term, convincing premises are often stronger in practice than higher first-year yields. Correctly reflecting degradation in PVSyst is not only about calculating future yields, but also about extending the basis for design decisions over time.

Point 1: Don’t treat degradation as a single fixed value

The first caution when reflecting degradation is not to handle it crudely as a single fixed value. In practice, people tend to think that entering one degradation rate number is sufficient. Of course, you need to set a consistent premise in PVSyst to run simulations, but if you do not consider what that number signifies, your interpretation of the results will be shallow. Even if degradation is expressed as a single coefficient, its background includes equipment characteristics, installation environment, and operational assumptions.

For example, even projects that appear similar can look different in the long term if the surrounding environment or maintenance assumptions differ. If you reuse figures from previous projects or pick a seemingly safe value without thought, you won’t know whether that premise is natural for the current project. Differences in PVSyst comparisons arise not only from the magnitude of the degradation rate but also from whether you can explain that number for the specific project.

Treating it as a fixed value can also lead to misreading differences between options. One option may be easy to maintain and feel stable over the long term; another may have a higher first-year yield but warrant heavier weighting of long-term risks. If you enter the same fixed value across the board despite such differences, long-term evaluations will become overly uniform. In PVSyst, treating degradation fairly is not the same as treating it uniformly.

As a countermeasure, organize in your mind the reason for adopting a specific degradation rate before entering it. Whether the comparison is a first-year-focused rough estimate or an evaluation conscious of long-term business viability affects how you set and weight the number. When reflecting degradation in PVSyst, it is more important to consider whether the number is a natural premise for the project than simply whether you can input it.

Point 2: Separate first-year performance and long-term performance

When handling degradation, it is important not to view first-year performance and long-term performance with the same mindset. In practice, people often first compare the first-year annual yield and then tack on long-term considerations. However, if you treat degradation properly in PVSyst, it is more practical to separate these two. This is because an option that looks strong in the first year and one that appears stable long-term do not necessarily coincide.

For example, an option may look high in first-year yield but the gap may narrow over the long term. Conversely, an option that looks slightly disadvantageous in the first year may gain persuasive power when long-term expectations are included. PVSyst makes first-year numbers easy to grasp, so impressions tend to be drawn toward them, but for projects that assume long-term operation, you should organize the post-degradation outlook as a separate tier.

Separating first-year and long-term performance also makes internal explanations easier. Mixing first-year expectations with long-term, degradation-reflected assumptions makes it harder for stakeholders to understand. If you clearly show the expected generation for the first year and how you expect it to evolve thereafter, the design intent is easier to convey. Although PVSyst outputs may look like a single result, in practice you need to organize them along a time axis.

As a countermeasure, when evaluating options, check first-year generation and degradation-reflected long-term outlooks separately. Then decide what you prioritize and use that to stabilize your decision-making. When reflecting degradation in PVSyst, avoid being overly swayed by first-year numbers and evaluate long-term performance from a separate perspective.

Point 3: View the impact on the entire system, not just the module

When considering degradation, focusing only on module-level performance decline leads to shallow interpretations in practice. In PVSyst, degradation is easy to see as an annual change in module performance, so you may be tempted to think of it solely as a module issue. However, the differences that appear in generation are determined not only by the module but by how the PCS receives power, the string configuration, array layout, and overlaps with loss conditions. In other words, degradation is not just about an individual component but about how the entire system appears.

For example, even with the same degradation rate, one configuration might change how output clipping appears while another might change the distribution of losses. An option that includes areas prone to shading or soiling may look harsher after years. Conversely, an option with well-grouped strings and a natural layout may appear relatively stable over time. To read PVSyst numbers practically, you need to see how degradation propagates through the entire system.

This viewpoint also makes it easier to explain why an option looks unfavorable long-term. Rather than simply framing it as a module performance issue, you can organize it as a difference in how the overall configuration absorbs the impact of degradation. In practice, if this is not organized, differences in degradation can be mistaken for simple equipment differences, and interpretation of comparisons will be shallow. PVSyst simulation results should be used to compare the robustness of systems, not to rank individual component performance alone.

As a countermeasure, after inputting degradation, review results not only as module losses but also in combination with PCS, string, and array conditions to confirm the impact on the whole system. Reading which option looks stable long-term and why the difference arises as a system-level effect greatly improves the quality of comparisons. When reflecting degradation in PVSyst, do not stop at viewing module-level decline rates.

Point 4: Align assumptions in comparative simulations

When comparing options including degradation, it is crucial to align assumptions. In practice, even when you intend to compare different degradation rates, module conditions, array layout, azimuth, and loss conditions may also change. Then it becomes difficult to tell whether long-term performance differences truly stem from how you set degradation or from other differing assumptions. Although PVSyst makes comparisons easy, if you do not align conditions, the meaning of the numbers can become ambiguous.

For example, if you want a long-term comparison but one option has stricter shading conditions and another has lower wiring losses, the long-term generation differences will be the result of multiple mixed factors. In such a state, it is hard to judge which option is really suitable for long-term operation. In practice, clarifying the purpose of the comparison and aligning conditions unrelated to that purpose directly improves the readability of simulations.

Aligned conditions also make internal explanations much easier. If you can keep the same site, array, PCS, and loss conditions and only change the degradation premise, you can directly explain that observed difference. Conversely, if conditions are inconsistent, you may have numbers but cannot succinctly explain what you compared. If you want to use PVSyst results strongly as decision material, organizing comparison conditions is indispensable.

As a countermeasure, before beginning comparisons, put into words what you will vary and what you will fix. Be clear whether you want to examine degradation scenarios or the combination of equipment configuration and long-term performance, and consciously align all other conditions. When reflecting degradation in PVSyst, aligning comparison assumptions is a basic practical step before looking at numerical differences.

Point 5: Do not separate temperature, soiling, shading, and maintenance conditions

To reflect degradation realistically, it is also important not to consider temperature, soiling, shading, and maintenance conditions in isolation. In practice, people tend to treat degradation as long-term performance decline, soiling as a separate loss, temperature as another loss, and shading as yet another. However, when viewing long-term generation forecasts, these factors do not exist independently. In the field, they overlap and change how generation appears over the years. Differences in PVSyst results reflect how much attention you pay to these overlaps.

For example, an option that includes areas prone to shading can show differences not only in the first year but also in how it appears long-term. An option with narrow, hard-to-clean aisles may require a somewhat conservative view of soiling losses. A layout with poor ventilation may change the temperature-related outlook. Even if you do not directly fold all of these into the degradation number, you must always consider them together when interpreting long-term generation.

Ignoring maintenance conditions makes degradation interpretations unrealistically optimistic. Options that are easy to inspect and those with poor maintenance access differ in long-term reliability. In practice, even if first-year numbers are the same, an option that is easier to maintain can be easier to explain over the long term. PVSyst is a tool not only for comparing equipment conditions but also for incorporating differences in operational conditions into comparisons.

As a countermeasure, when reviewing degradation-reflected results, simultaneously check temperature, soiling, shading, and maintenance conditions. Rather than reading degradation in isolation, simply checking whether there are site conditions that make long-term differences widen makes evaluations much more practice-oriented. To understand degradation in PVSyst, avoid separating single-year loss conditions too much from long-term performance decline.

Point 6: Decide how to read results and back-check assumptions

Finally, an important point is to decide in advance how you will read PVSyst results and then back-check degradation settings. In practice, people tend to look at result screens and then pick out points of concern piecemeal, but this approach makes comparison axes unstable. If it is unclear whether you mainly want to see first-year generation, post-degradation generation, annual differences, or differences between options, it is also unclear how to evaluate the degradation rate. To handle degradation practically in PVSyst, first decide the indicators to view, and then verify whether the input premises are natural.

For example, whether you prioritize generation trends over years, long-term differences between options, or a simple index for use in internal explanation changes how you read results. Even if a large difference appears in one option, you must confirm whether it truly stems from degradation assumptions or from differences in other loss conditions before judging. PVSyst allows multifaceted result views, but without deciding what you are looking for, you can become more confused.

Also develop the habit of returning to assumptions after viewing results. If long-term generation looks harsher than expected, check whether you set the degradation rate too strictly or whether it overlaps too much with other loss conditions. Conversely, if long-term differences seem too small, question whether you are underestimating degradation. In practice, what matters is not treating input numbers as absolute. Considering PVSyst as a tool to iterate between inputs and results leads to more stable outcomes.

As a countermeasure, before comparison, decide whether your primary indicator is first-year, post-degradation, or their difference, and after viewing results, check whether the premise is natural relative to that indicator. The final practical point in handling degradation in PVSyst is not to stop at entering numbers but to question their validity from the results and adjust. Differences due to degradation settings depend not on whether you know the perfect number, but on whether you can question the number based on results and refine it.

How to turn PVSyst degradation modeling into practical outcomes

What the six cautions share is the idea of not ending degradation as a mere long-term loss. Do not treat it crudely as a fixed value; separate first-year and long-term performance; read it as an impact on the whole system rather than on the module alone; align comparison assumptions; connect it with temperature, soiling, shading, and maintenance conditions; and finally back-check from the results. If you can follow this flow, reflecting degradation in PVSyst becomes the foundation for design decisions that assume long-term operation, not merely a setting to lower numbers.

What matters most for practitioners is not choosing the option that shows the highest first-year yield. The valuable thing is being able to explain why you set that long-term premise for the project. If first-year expectations, forecasts after years, and relationships with other loss conditions are organized, comparison results are easier to use for internal checks and proposals. Conversely, treating degradation with vague numbers weakens the rationale as soon as long-term discussion begins.

Improving the accuracy of degradation reflection also requires not limiting yourself to desk simulations. If site conditions, layout, maintenance access, surrounding environment, and shading behavior are unclear, the long-term outlook itself becomes ambiguous. To connect PVSyst numbers to practice, repeatedly iterate between site understanding and simulation to confirm whether the option is truly natural long-term. Degradation is both a time-axis condition and an accumulation of site conditions.

In that sense, when you want to more reliably proceed with on-site position checks or coordinate acquisition, it is effective to consider using iPhone-mounted high-precision GNSS positioning devices such as LRTK. If on-site position information and site conditions become easier to organize, the assumptions for layout and maintenance when reflecting degradation in PVSyst also become clearer. If you can increase desk-comparison accuracy with PVSyst and support site understanding accuracy with LRTK, reflecting degradation moves closer to field-rooted long-term design decisions. Treating degradation carefully not only improves the accuracy of generation forecasts but also enhances the practical capability to connect desk work and field work.