7 Ways to Compare System Configurations in PVSyst

Table of Contents

• Why comparing system configurations in PVSyst matters

• Method 1: Align assumptions before comparing

• Method 2: Compare combinations of module capacity and PCS capacity

• Method 3: Compare by differences in DC/AC ratio

• Method 4: Compare by changing azimuth and tilt angles

• Method 5: Compare array layout and string configuration

• Method 6: Compare loss behavior and output limiting

• Method 7: Separate annual values and monthly trends for comparison

• How to turn PVSyst system configuration comparisons into practical decisions

Why comparing system configurations in PVSyst matters

For practitioners using PVSyst, comparing system configurations is not a mere equipment swap exercise. How you combine modules, PCS, strings, arrays, azimuth, tilt, and loss conditions affects not only the view of annual generation but also the feasibility of the design, constructability, and maintainability. Therefore, even if you ultimately adopt a single proposal, the work of comparing multiple configurations and clarifying the meaning of their differences is indispensable.

In practice, people often feel reassured once one proposal produces numbers and want to proceed directly to detailing. However, a proposal that yields results in PVSyst is not necessarily optimal for the project. Changing how modules are stacked can alter how generation increases, and changing how the PCS accepts power can alter how output limiting appears. In other words, comparing system configurations is important not only to find higher numbers but also to understand which differences in conditions are affecting the results.

Also, comparing system configurations directly impacts internal explanations and decision-making. When asked why a proposal was chosen, saying only that it produced higher generation can be weak in practice. Only when you can explain what it is better than the alternative, where it has no unreasonable aspects, and which conditions were prioritized to select it does the comparison have real value. PVSyst is not only a tool to produce numbers but also a tool to organize the rationale for comparisons.

Moreover, getting good at comparing system configurations increases the speed of project evaluations. Instead of starting from scratch each time, you learn which aspects to treat as variables and which to fix for comparison. Organizing comparison methods reduces hesitation when looking at PVSyst results and stabilizes both design and decision-making. Below, the following organizes seven practical methods for comparing system configurations.

Method 1: Align assumptions before comparing

The first thing to do when comparing system configurations is to align the assumptions. This seems obvious, but in practice it is where the largest differences arise. If it’s unclear whether you want to compare module differences, PCS capacity differences, or azimuth differences and you create multiple proposals under that ambiguity, you will not know which difference is driving the results. PVSyst makes comparison easy, but if your alignment of assumptions is weak, you can end up with larger numbers that are hard to judge.

For example, if you want to see differences in module configuration but simultaneously change azimuth and loss conditions, the reasons for generation differences become mixed. Conversely, if you want to see differences in DC/AC ratio but significantly change array layout or shading conditions, you won’t know what to evaluate. In practice it’s common that while adjusting one proposal, other conditions change inadvertently. That’s why you need to organize fixed conditions and variable conditions before comparing.

The advantage of aligning assumptions is not only that it makes the result differences easier to read. It also clarifies what is being compared when preparing internal explanations or reports. If you know whether you changed only the PCS under the same meteorological, site, and azimuth conditions, or whether you also changed the number of modules, explanations become more concise. When the axis of comparison is set, the materials are easier for readers to understand.

As a practical countermeasure, decide in one sentence what you want to see in this comparison before you start. Fix the purpose—module condition comparison, PCS condition comparison, DC/AC ratio comparison, azimuth comparison—so that PVSyst settings can be prepared accordingly. The first step to avoid failed comparisons is not to increase the number of proposals, but to align assumptions and clarify the meaning of the differences.

Method 2: Compare combinations of module capacity and PCS capacity

Next, an effective approach is to compare different combinations of module capacity and PCS capacity. When considering system configuration in PVSyst, many practitioners tend to focus on either the module side or the PCS side. In reality, however, how the two are combined changes the view of annual generation, the way output limiting occurs, and the feasibility of strings. In practice, it is important to compare combinations rather than single pieces of equipment.

For example, a proposal adopting high-output modules and a proposal stacking somewhat lower-output modules in greater numbers may yield different results even with the same PCS conditions. Conversely, if you fix module conditions and change only the PCS, impressions of output limiting and capacity balance may change. PVSyst makes it easy to compare such combination differences, so it’s suitable for checking how the system appears as a whole rather than chasing the performance differences of a single device.

The practical value of this comparison method is that it allows you to confirm not only numbers but also how natural the design feels. One combination may show high generation but lead to complex string configurations or poor site fit. Another combination may produce slightly less generation but allow orderly array layouts and easier maintenance and construction. By comparing combinations in PVSyst, you can check these differences both numerically and in terms of conditions.

As a countermeasure, create several candidate combinations and compare them rather than looking at only modules or PCS. When doing so, align conditions other than the points you want to compare so the differences are easier to read. When comparing system configurations in PVSyst, it’s important to evaluate the appropriateness of combinations rather than the superiority of individual components.

Method 3: Compare by differences in DC/AC ratio

Comparing by differences in DC/AC ratio is very effective for narrowing down practical proposals in PVSyst. The DC/AC ratio is just a ratio, but how you choose it affects module stacking, how the PCS accepts power, the occurrence of output limiting, and how arrays fit within the site. Therefore, when comparing system configurations, arranging proposals along the axis of DC/AC ratio makes the design direction easier to see.

In practice, when changing the DC/AC ratio attention tends to focus on how annual generation increases. That is important, of course, but you should not only look at incremental gains. Compare from which ratio output limiting becomes noticeable, at which ratio array design can be arranged straightforwardly, and which ratios are easier to explain internally. PVSyst’s result screens make it easy to check these differences, so stepwise comparison of DC/AC ratios is appropriate.

Also, comparing DC/AC ratios largely overlaps with discussions of oversizing ratio, so it has the advantage of letting you organize not only generation maximization but also the way limitations are handled and the cohesiveness of the design. One ratio may produce slightly higher annual values but be heavily limited, while another ratio may have small incremental gain but a natural and manageable configuration. Seeing these differences lets you judge proposals by their character rather than by a single performance metric. This is a critical viewpoint in practice.

As a countermeasure, don’t decide the DC/AC ratio at a single point; create multiple realistic proposals across a range and compare them. Confirm annual generation, output limiting, array cohesiveness, and string feasibility together to make final decisions easier. In PVSyst, the DC/AC ratio is an important comparison axis not only for numerical differences but for organizing design direction.

Method 4: Compare by changing azimuth and tilt angles

When comparing system configurations, it’s important to not only vary equipment conditions but also compare by changing azimuth and tilt angles. In PVSyst, configuration often evokes modules and PCS, but in practice the orientation and angle of arrays are also part of the system configuration. That’s because changing azimuth and tilt alters generation behavior even with the same equipment, as well as shading conditions, row spacing, and land use efficiency.

In practice, you may want to decide equipment configuration based on ideal orientation and angle. However, site conditions, earthworks, slope orientations, and access planning often make those ideal conditions unsuitable for the field. Comparing azimuth and tilt in PVSyst reveals not only simple annual generation differences but also the ease of arrangement and shading impacts, making the character of proposals clearer. This is very useful for practical comparisons.

Also, comparing orientation and tilt can change how you evaluate equipment combinations. A module or PCS combination that is advantageous under ideal conditions may be less suitable when shifted to orientations or angles closer to real site conditions, and an alternative configuration may fit the site better. When comparing system configurations in PVSyst, you should not fix equipment and optimize only it; you need to review orientation and tilt within realistic conditions as part of the same evaluation.

As a countermeasure, after narrowing the main equipment configurations, vary azimuth and tilt within realistic ranges and compare. This shows which configurations are strong on paper and which are strong in the field. When comparing system configurations in PVSyst, avoid over-separating equipment conditions and installation conditions; it’s important to view them together.

Method 5: Compare array layout and string configuration

Comparing array layout and string configuration is also highly practical in PVSyst. Even using the same modules and PCS, the arrangement of arrays and the way strings are divided affect annual generation, shading behavior, and ease of construction and maintenance. In other words, comparing system configurations only by equipment selection is incomplete; it only becomes meaningful when you look at array and string cohesion.

For example, within the same site, a plan that packs arrays densely and another that leaves some space to reduce shading can produce differences that are hard to explain by annual totals alone. Furthermore, whether string divisions are natural affects PCS compatibility and maintainability. By comparing in PVSyst, you can determine which approach doesn’t just produce higher numbers but forms a coherent, feasible system.

In practice, this area is sometimes treated lightly: people pick the proposal with better numbers and then try to refine array and string later. That approach can require major rework later. Especially on sites with strong constraints, how arrays and strings are combined can greatly change impressions of a system configuration, so it’s rational to include these aspects in comparisons from the start.

As a countermeasure, align main equipment conditions and compare multiple patterns of array layout and string configuration. Look not only at annual totals but also at shading, natural cohesiveness, and ease of maintenance to identify proposals that are practical to adopt. When comparing system configurations in PVSyst, evaluate not only differences in equipment but also differences in layout and configuration.

Method 6: Compare loss behavior and output limiting

When comparing system configurations, it is essential to compare not only total generation but also how losses arise and how output limiting occurs. PVSyst displays annual generation clearly, which leads people to judge by that number alone. However, even proposals with similar annual values can mean different things depending on what kinds of losses produced those numbers. PCS settings, DC/AC ratio, and string configuration differences especially tend to reflect in output limiting and conversion loss behavior.

In practice, proposals with higher annual generation may seem preferable, but if that advantage comes with significant output limiting, another proposal may be easier to explain and handle. Conversely, between proposals with small differences in generation, the one whose losses arise more gently and naturally may be stronger as a design. Comparing how losses and limiting appear in PVSyst helps you judge which proposal is more acceptable in practice rather than just which number is higher.

Comparing losses also makes it easier to find where a system configuration has unrealistic aspects. By organizing whether the issue stems from array design, inverter acceptance, or string configuration differences, you can identify what to fix next. PVSyst comparisons are effective not only for choosing good proposals but for diagnosing why bad proposals perform poorly.

As a countermeasure, when comparing proposals always check not just annual generation but the breakdown of losses and the appearance of output limiting. That reveals the background of number differences and supports internal explanations and design revisions. When comparing system configurations in PVSyst, evaluate not only the final figures but also the differences in how those figures were reached.

Method 7: Separate annual values and monthly trends for comparison

Finally, an effective method is to separate annual values and monthly trends for comparison. Annual generation stands out in PVSyst comparisons, so it naturally becomes the center of attention. However, differences in system configurations show up not only in annual totals but also in monthly generation trends and the timing of limiting. In practice annual values often drive final decisions, but examining their breakdown helps you understand the character of proposals.

For example, a configuration may be slightly advantageous annually but concentrate output limiting during a specific season. Another configuration may be somewhat modest annually but have a well-balanced monthly profile and stable loss behavior. These differences help with internal explanations and operational image planning. When comparing system configurations in PVSyst, don’t conclude solely on annual rankings; checking monthly differences makes the assessment more practical.

Looking at monthly trends also makes it easier to see which conditions the configuration differences respond strongly to—whether it’s the match with meteorological conditions, the impact of azimuth and tilt, or differences in PCS settings and DC/AC ratio. PVSyst makes monthly results easy to confirm, so you should use this information in comparisons. Differences that are buried in annual totals often become clear when viewed monthly.

As a countermeasure, whenever you compare proposals, separately check annual generation differences and monthly trend differences. This lets you grasp not only which proposal ranks higher but also each proposal’s character. When comparing system configurations in PVSyst, use annual values as the entry point and monthly trends as supporting lines to make more practical judgments.

How to turn PVSyst system configuration comparisons into practical decisions

What the seven methods above have in common is that system configuration comparison is not simply replacing components and comparing numbers, but interpreting the meaning of differences. Align assumptions, look at module and PCS combinations, and organize DC/AC ratio, azimuth, tilt, array layout, string configuration, losses, limiting, and monthly trends. Once you establish this flow, PVSyst comparisons become practical decision-support material rather than mere estimates.

For practitioners, the important task is not only to find the proposal that yields the highest annual generation. The real value is being able to explain why that configuration is adopted for the project. If the numerical increments, cohesion of the configuration, ease of construction and maintenance, and how output limiting is handled are all organized, the comparison results are usable for internal decisions and design documents. Conversely, prioritizing numbers alone often causes infeasibility to appear later in the process.

Also, improving the accuracy of system configuration comparisons requires not finishing with desk simulations alone. If site boundaries, topography, slopes, access paths, existing conditions, and construction circulation are ambiguous, it becomes difficult to judge which configuration will actually be feasible. To connect PVSyst results to practical decisions you need to iterate between site understanding and simulation to confirm the meaning of differences. System configuration is not decided solely on the screen; it must be evaluated together with site conditions.

In that sense, when you want to make site positioning and coordinate acquisition more reliable, using iPhone-mounted high-precision GNSS positioning devices such as LRTK is an effective approach. When on-site position information and site conditions are easier to organize, the placement assumptions and array feasibility in PVSyst comparisons become clearer. If you can improve desk comparison accuracy with PVSyst and support on-site understanding with LRTK, system configuration comparison moves from a numbers competition toward grounded practical decisions. Careful comparison of system configurations not only raises the accuracy of generation forecasts but also enhances the design capability that connects desk work and field work.