8 Evaluation Points When Comparing Design Proposals in PVSyst

Table of Contents

• Why comparing design proposals in PVSyst becomes important

• Evaluation Point 1: Compare generation with aligned assumptions

• Evaluation Point 2: Check loss breakdowns to understand reasons for differences

• Evaluation Point 3: Confirm the DC and AC capacity balance

• Evaluation Point 4: Consider azimuth and tilt differences from a profitability perspective

• Evaluation Point 5: Examine shading impacts not only by annual values but also by time of day

• Evaluation Point 6: Verify consistency between meteorological settings and site conditions

• Evaluation Point 7: Judge whether the design is reasonable with maintenance and operation in mind

• Evaluation Point 8: Make the final comparison including site conditions and constructability

• To avoid leaving design comparisons as desk work

Why comparing design proposals in PVSyst becomes important

When comparing multiple design proposals in PVSyst, what practitioners most want to avoid is choosing a proposal that looks good on paper but is difficult to execute. In PV plant design, factors such as module layout, azimuth, tilt, DC/AC capacity ratio, shading effects, and expected losses each influence generation and operability to some extent. Therefore, deciding superiority solely by total annual generation can lead to practical difficulties during construction or operation.

PVSyst makes differences between proposals easy to see numerically, but small input differences can change results. In other words, the more convenient the comparison function is, the more careful you must be about how you compare. Even when you assume the same site, if the meteorological data, loss settings, equipment configuration, or shading modeling differ, the comparison is not fair. A fundamental premise of comparing design proposals is to first put them on an even footing.

Also in practice, it is not enough for only the person doing the analysis to understand the comparison results. You need to organize results in a way that can be explained to in-house designers, sales staff, construction teams, and the client. Beyond just reading PVSyst outputs, being able to explain why differences arose, whether those differences are acceptable on site, and what impacts they will have after operation begins increases the quality of the comparison.

This article narrows down eight evaluation points to keep in mind when comparing design proposals in PVSyst. Rather than merely showing how to read screens, it explains with awareness of the linkages among design, construction, and operation so that practitioners can more easily judge when facing comparison tables.

Evaluation Point 1: Compare generation with aligned assumptions

The first thing that catches the eye in PVSyst is the annual energy yield, but to compare this correctly you must align the assumptions. For example, if one proposal uses slightly more favorable meteorological settings or another uses more optimistic loss assumptions, the difference in generation reflects input differences rather than design quality. At the start of any comparison, verify that meteorological data, site location, treatment of equipment efficiency, and basic loss assumptions are consistent.

Also, looking only at annual generation can be misleading when differences are driven by scale rather than design. If the number of modules differs greatly between proposals, a simple comparison of total generation only reflects size differences. Therefore, it is important to also look at generation per installed capacity or generation per area. If the comparison is not fair, the numbers may look neat but lead to incorrect conclusions.

It is also important to see in which seasons the generation differences occur. Even small differences in annual values can translate into different evaluations depending on whether a proposal performs better in summer or winter, given site usage and grid conditions. When comparing in PVSyst, inspect not only totals but monthly trends to identify when differences occur and enable more practical judgments.

In practice, a proposal with higher generation is not always the best. If slightly higher generation comes with increased construction difficulty, reduced maintainability, or greater sensitivity to shading, another proposal may be more stable overall. Thus, understand that PVSyst’s generation comparison is an entry point, not the final decision.

Evaluation Point 2: Check loss breakdowns to understand reasons for differences

A commonly overlooked aspect in proposal comparisons is the breakdown of losses. PVSyst lets you check not only the final output but also what kinds of losses accumulate along the way. From this you can see why a proposal generates more or why it falls short of expectations. For practitioners, what matters more than the magnitude of results is being able to explain the reasons for differences.

For example, one proposal may have large temperature-related losses while another has relatively larger wiring or conversion losses. In that case, rather than comparing just generation, consider which losses can be improved by design changes. Losses that are easy to improve allow room for design refinement, whereas losses strongly constrained by site or layout may warrant prioritizing stability over aggressive optimization.

When viewing losses, it’s important not to see numbers in isolation but to interpret them in the context of design intent. A high-density layout may look efficient in land use but can increase losses due to shading or poorer ventilation. Conversely, a more relaxed layout may reduce equipment quantity but be advantageous for temperature and shading. PVSyst’s loss breakdown provides numerical material to confirm these differences in design approach.

For internal or client explanations, loss breakdowns are very useful. Saying “this proposal generates more” is less persuasive than saying “this proposal suppresses shading losses and yields more stable output throughout the year.” To leverage PVSyst in practice, you need to be able to read losses and translate them into design intentions.

Evaluation Point 3: Confirm the DC and AC capacity balance

When comparing proposals, the balance between DC and AC capacities is an essential evaluation axis. PVSyst allows examination of the relationship between module capacity and how the AC-side equipment handles it, letting you decide how aggressively to size the DC side. This balance affects not only generation but also curtailment at peak times and equipment utilization, so it cannot be judged by simple bigger-or-smaller logic.

Proposals with a thicker DC side can be advantageous during low-irradiance periods or seasons. They can boost output in early morning, late afternoon, or winter, and thus increase annual generation. However, during high-irradiance periods, the AC side may not be able to accept all output, leading to clipping. When comparing in PVSyst, determine how much clipping occurs and whether the annual benefit justifies it.

On the other hand, proposals with conservative DC/AC ratios reduce peak waste and are simpler from an equipment configuration standpoint, but may be disadvantaged in total energy capture over the year. In regions with high weather variability or large seasonal differences, how the system captures the tails of the irradiance distribution can strongly influence results. Therefore, evaluate not only peak performance but overall annual efficiency.

As a practitioner, consider how differences in capacity balance translate to construction and operation. Overly complex configurations can make on-site checks and maintenance harder. Conversely, overly conservative configurations may fail to fully exploit site conditions. When comparing designs in PVSyst, judge capacity balance not just as numeric optimization but for how manageable it will be in the field.

Evaluation Point 4: Consider azimuth and tilt differences from a profitability perspective

When comparing multiple proposals in PVSyst, differences in azimuth and tilt often change the distribution of generation. It is important to note that maximizing annual generation is not always the right objective. Given site constraints and layout restrictions, a proposal that is easier to implement and more stable can yield better overall outcomes than chasing ideal orientation or angle.

Azimuth differences affect which time of day the system generates more, while tilt differences affect seasonal irradiance capture. Therefore, in PVSyst comparisons you should look at not just annual totals but the shape of the generation profile. A proposal that is slightly superior in annual terms might concentrate output in specific hours, while another with slightly lower total may deliver a steadier generation curve across the year.

Also, selecting azimuth and tilt ties into racking layout and earthworks. Pursuing ideal values too strictly can lead to designs that fight the site topography, increasing earthwork and construction effort. As a result, a proposal that looks favorable in simulation may be inferior on site. PVSyst numbers are important, but when comparing proposals you must also consider what was sacrificed to achieve those numbers.

In practice, viewing azimuth and tilt comparisons in a profitability context makes decisions easier. If a small generation advantage incurs large increases in construction or maintenance risk, pursuing that gain may be pointless. Conversely, if the installation conditions are reasonable and small adjustments can improve annual balance, adopting that approach can be worthwhile. When comparing in PVSyst, treat azimuth and tilt as part of the overall design fit rather than isolated numbers.

Evaluation Point 5: Examine shading impacts not only by annual values but also by time of day

Shading evaluation significantly affects the accuracy of design comparisons. PVSyst quantifies shading losses, but relying solely on an annual loss rate is dangerous. Shading can be small on an annual average yet concentrated in particular seasons or times of day. Understanding how those impacts manifest in output ramp-ups and drop-offs is critically important in practice.

For example, a proposal with shading concentrated in winter mornings and evenings may show little annual loss, but given winter operating conditions and grid constraints, losses in those hours can be more detrimental than the annual figure suggests. Conversely, two proposals with similar annual loss rates may differ in operational stability if one’s shading is more dispersed. When comparing in PVSyst, don’t stop at a single shading number—examine how shading occurs over time.

Shading is also directly linked to layout compactness and often trades off with land-use efficiency. Increasing equipment density reduces row spacing and raises the likelihood of shading at low solar elevations. Even if total installed capacity increases and total generation rises, increased shading and output variability may erode expected gains. In design comparisons, evaluate effective performance including shading rather than focusing only on equipment count.

Furthermore, shading assessment must align with on-site understanding. Surrounding terrain, slopes, existing structures, and adjacent objects that seemed minor on paper can impose major constraints in reality. Do not take PVSyst shading outputs at face value—verify whether shading assumptions match site awareness. Ignoring shading details when comparing proposals increases the risk of unexpected discrepancies after completion.

Evaluation Point 6: Verify consistency between meteorological settings and site conditions

PVSyst comparison results are strongly influenced by the meteorological inputs. Therefore, when comparing proposals, adopt a stance of questioning the consistency between meteorological settings and site conditions. If assumptions subtly differ by proposal even though the same site is intended, result reliability drops sharply. In design comparisons, meteorological conditions are not background—they are the foundation.

In practice, how well the simulation aligns with local impressions matters. Wind exposure, perceived seasonal temperatures, topography effects, and surrounding reflectance conditions are examples where those who know the site may sense inconsistencies. Even if PVSyst outputs look clean, if they diverge from on-site feeling, you should revisit the comparison assumptions. Fit with real site conditions takes precedence over pretty numbers.

Checking meteorological consistency also helps correctly interpret differences between proposals. For example, if you want to isolate the effect of tilt angle but meteorological conditions vary, you cannot tell the primary cause of differences. To increase comparison precision, avoid changing multiple factors at once. Keep everything except the design element under study fixed so the cause of differences is clear—this is an important PVSyst practice.

Moreover, aligning meteorological and site conditions aids internal consensus building. Even if designers are convinced, if construction or sales teams have doubts the proposal will not proceed smoothly. If you can explain why these conditions were chosen and how site features were reflected, PVSyst outputs become grounded decision materials rather than mere calculations.

Evaluation Point 7: Judge whether the design is reasonable with maintenance and operation in mind

When comparing designs in PVSyst, attention naturally focuses on generation and losses. However, practitioners should pay attention to whether the design can be reasonably maintained after commissioning. A proposal may look numerically superior but be hard to inspect, difficult to access, or make fault detection challenging—issues that erode performance over long-term operation. Considering maintainability during the design comparison phase helps avoid rework later.

For example, a high-density layout can fit more equipment in the same area but leave little room for aisles or workspaces. That can hinder routine maintenance such as cleaning, visual inspections, or replacement tasks. While such issues may not be directly visible in PVSyst numbers, when comparing layouts and equipment configurations you must always evaluate ease of maintenance and operation.

From an operational perspective, ease of fault isolation is also important. Excessively complex equipment configurations can make it time-consuming to identify causes when output drops or partial failures occur. In practice, not only normal operation efficiency but also response speed to abnormalities affect operational results. When comparing proposals in PVSyst, imagine not only normal operation numbers but also how manageable the system would be under fault conditions to improve judgment quality.

Additionally, considering maintainability in comparisons ties directly to discussions with clients. For projects that prioritize long-term reliable use, a slightly lower-generating but easier-to-maintain proposal may be chosen. Treat PVSyst design comparisons not only as design competition but as an exercise that determines the long-term quality of operation.

Evaluation Point 8: Make the final comparison including site conditions and constructability

When making the final comparison of design proposals, include site conditions and constructability in your judgment. PVSyst is an excellent comparison tool, but it cannot fully replace on-site realities. Terrain undulation, delivery routes, availability of a work yard, construction safety, and compatibility with earthworks are aspects that simulations cannot fully capture. Therefore, avoid directly equating numerical superiority with selection.

When differences between proposals are small, constructability often becomes the decisive factor. A proposal with slightly higher annual generation but complex construction procedures that increase schedule and quality control burden raises overall risk. Conversely, a numerically conservative proposal that fits the site well and can be built stably is more likely to deliver expected performance.

Including site conditions in comparisons also strengthens the persuasiveness of a proposal. Presenting only PVSyst outputs tends to look theoretical. But if you can explain how the design respects terrain and construction constraints, clients and internal stakeholders are more likely to accept it. In practice, a good proposal is not the one with the highest numbers but the one that is easily reproducible on site and easy to bring into operation.

In the final design comparison, review generation, losses, capacity balance, shading, meteorological conditions, maintainability, and constructability together. Don’t stop at laying PVSyst results in a single comparison table—verify whether the proposal can be executed on site, explained to stakeholders, and maintained. Only then does the comparison become useful in practice.

To avoid leaving design comparisons as desk work

When comparing design proposals in PVSyst, how you interpret differences matters more than simply spotting numeric gaps. Attractive aspects—high annual generation, low losses, aggressive capacity balance—each have their appeal. But practitioners should choose proposals that withstand calculation, construction, operation, and communication. The accuracy of comparisons depends less on table reading and more on whether you consider the design background in depth.

Especially when differences in generation are small, the true value of design comparison emerges. Big gaps are relatively easy to decide, but when differences are minor, the quality of losses, shading patterns, maintainability, and constructability matter. Skilled PVSyst users are not swayed by numbers alone; they carefully set comparison conditions and interpret the meaning of differences. This carefulness reduces rework and explanation burdens downstream.

Also, to link desk-based comparisons to the field, the precision of site understanding is indispensable. Small layout differences, shading-causing surroundings, and how to handle elevation changes and construction logistics can destabilize simulation assumptions if site knowledge is shallow. Therefore, when you want to improve comparison accuracy, accurately capturing site spatial information is essential.

In situations where efficient site understanding is needed, using an iPhone-mounted GNSS high-precision positioning device like LRTK can be effective. Confirming position information accurately on site while organizing design conditions and layout assumptions makes it easier to prepare comparison inputs and thus improves the accuracy of PVSyst comparisons. Practitioners who want to connect desk work with field reality will find adopting such measures highly valuable.