7 checklist items for module selection in PVSyst

Table of contents

• Why module selection becomes important in PVSyst

• Checkpoint 1: Align the purpose of module selection and the comparison conditions first

• Checkpoint 2: Confirm not only the output value but also the dimensions and the number of modules that can be installed

• Checkpoint 3: Check how generation appears taking temperature conditions into account

• Checkpoint 4: Judge while checking consistency with the string configuration

• Checkpoint 5: Confirm compatibility with orientation, tilt, and array layout

• Checkpoint 6: Don’t separate loss settings and degradation assumptions from the evaluation

• Checkpoint 7: Interpret the meaning of differences in comparative simulations

• How to turn PVSyst module selection into practical results

Why module selection becomes important in PVSyst

When performing energy generation simulations in PVSyst, module selection is not merely a choice of equipment. In practice, differences between modules affect not only the appearance of generation results but also the ease of arranging the layout, the feasibility of string configurations, how shading is received, maintainability, and even the ease of explaining choices internally. Therefore, if module selection is postponed or decided based only on output values, unexpected rework often occurs later in the process.

Especially in PVSyst, the moment you choose a module the assumptions for the entire system become quite concrete. If module dimensions change, the way they are arranged on the same site changes, and if electrical conditions change, the way strings are built and losses appear also change. In other words, module selection may look like a comparison of a single piece of equipment, but in reality it becomes the starting point for simultaneously adjusting site conditions, array design, electrical design, and generation forecasting.

What practitioners should be careful about is not to think of module selection solely as maximizing generation. Of course, aiming for a high annual generation in simulation results is important. However, if a module is difficult to place on site, hard to form strings with, more susceptible to shading, or lowers maintainability, that module is not necessarily the best choice for the overall project. If you use PVSyst in practice, you need a perspective that prioritizes finding a module that can be integrated into the project without forcing things, rather than the module that simply produces the highest number.

Also, module selection is frequently questioned in internal comparison documents and reports. If you cannot explain why that module was adopted or why it was judged superior to alternative options, relying on numbers alone will make adoption decisions difficult. That is why, when proceeding with module selection in PVSyst, it is important not just to swap candidates and look at results, but to organize what to check while comparing. Below, I explain seven checkpoints that are especially important in practice.

Checkpoint 1: Align the purpose of module selection and the comparison conditions first

The first thing to confirm is the reason you are comparing modules in the first place. When you start module selection in PVSyst, your attention immediately goes to output values and simulation result figures. However, the purpose of comparison differs by project. Depending on whether you want to fit as many modules as possible on the site, maximize annual generation, prioritize layout flexibility, or make string configuration easier, the points you should look at change.

In practice, module comparisons are sometimes advanced while the purpose remains ambiguous, and the evaluation criteria shift midway. At one stage high output may seem attractive, at another stage handling of dimensions may become a concern, and finally you may want to prioritize electrical coherence — this kind of flow is not uncommon. Of course, it is necessary to look from multiple perspectives, but unless you at least organize what to prioritize in this comparison from the start, your judgment will be unstable even when looking at PVSyst results.

Also, aligning the comparison conditions is extremely important. If you want to compare modules only, but at the same time array conditions, loss settings, orientation, or tilt assumptions also change, you will not know which differences are due to the modules. Although PVSyst makes comparative simulation easy, if assumptions are not well organized you can easily misinterpret the meaning of differences. If you want to see differences between modules, you should align other assumptions as much as possible.

As a countermeasure, before starting the comparison briefly verbalize what you want to decide in this selection. If it becomes clear whether you are aiming for capacity maximization, layout efficiency, or design feasibility, it will be easier to organize which results to review. When proceeding with module selection in PVSyst, simply aligning the purpose and comparison conditions at the start will greatly improve readability of the results and speed of decision-making.

Checkpoint 2: Confirm not only the output value but also the dimensions and the number of modules that can be installed

A common mistake in module selection is judging advantages and disadvantages only by output values. Indeed, modules with higher rated output can look attractive at first glance. However, in practice that alone does not determine the decision. If module dimensions change, the number of modules that can be placed on the same site changes. In other words, even if the output per module is higher, it does not necessarily mean it will be the most advantageous when viewed across the entire site.

When simulating in PVSyst, the generation figures appear first, so you tend to be pulled by the impression of high output. But when you move into array design, the impact of dimensional differences becomes apparent through access aisles, clearances, edge treatments, and inter-row spacing. Even slightly larger modules can change how edges are left over and disrupt the overall fit. Conversely, slightly smaller modules may offer higher placement flexibility and be advantageous in total output. In practice, if you misjudge this point, a module that looked high-performance on paper can become a difficult choice on site.

Differences in the number of installable modules affect not only capacity but also array cohesion. Whether you can form neat row configurations or end up with awkward leftover panels impacts maintainability and the ease of organizing wiring. In PVSyst comparisons, generation differences may look small, but differences in layout cohesion can later become significant design differences. If module selection is advanced based only on output values, this practical difference is easy to overlook.

As a countermeasure, when comparing candidate modules, confirm the dimensions and the number of installable modules together with the output per module. By checking how many modules can be installed and how they group when arranged under the same site conditions, you will deepen your understanding of the numerical results. Module selection in PVSyst should focus not on single-unit performance comparison, but on how they fit across the entire site.

Checkpoint 3: Check how generation appears taking temperature conditions into account

It is also indispensable in module selection to check how generation appears taking temperature conditions into account. In practice attention tends to go first to output values and layout efficiency, and the impact of temperature is often postponed. However, PVSyst simulations reflect the combination of local meteorological conditions and module characteristics in the results. Therefore, if you compare modules without being aware of temperature conditions, the apparent output differences can be smaller than expected or even reverse.

Especially when comparing multiple modules on the same site, how temperature conditions present themselves is important. Depending on the installation environment, the influence of ambient temperature and the way the equipment absorbs heat can have a non-negligible effect on generation. In PVSyst, these differences can appear not only in annual values but also in seasonal patterns. If you choose a high-output module without viewing temperature effects, the expected difference may not materialize under assumptions closer to actual operation.

Moreover, the impact of temperature should be seen more as compatibility with the project than as a simple module-to-module performance comparison. A module that looks advantageous at one site, in one configuration, or under one installation condition might appear different in another project. For practitioners using PVSyst, the important point is not which module is generally good, but how it appears when combined with the current site conditions. Without this viewpoint, it is easy to carry judgments from other projects unchanged.

As a countermeasure, when comparing modules check not only annual generation but also monthly behavior and how losses present themselves. If you view results with awareness of how much temperature influences performance, you can more clearly see differences that simple output comparisons hide. When conducting module selection in PVSyst, you need an approach that interprets temperature conditions as part of performance differences.

Checkpoint 4: Judge while checking consistency with the string configuration

An often-overlooked point when advancing module selection is consistency with the string configuration. In PVSyst, after you choose a module you build the overall system configuration, and at this stage difficulties in the selection can surface. Even if apparent generation and layout efficiency look good, when considering the actual string configuration they may be hard to handle or create complex partitions.

In practice, module comparisons are often driven by layout first, and only afterward is electrical consistency checked. This flow itself is natural, but if you do not have a prospective view of string configuration from the module selection stage, you may have to significantly revise assumptions later. For example, if you see many leftover panels, poor array cohesion, or difficulty organizing by grid connection, the evaluation of the arrangement proposal itself changes. If you use PVSyst in practice for module selection, you should value the ease of forming the configuration as much as the simulation numbers.

Also, consistency with string configuration ties into maintainability and ease of isolating faults. Considering later troubleshooting and inspection work, a module that naturally forms coherent configurations may be easier to handle than one that simply produces higher generation. If you pick based only on annual values from PVSyst results, you may miss such practical differences.

As a countermeasure, when comparing candidate modules be conscious not only of whether the layout can be realized but also of how it will come together electrically. You do not need to refine it to detailed design level, but you should at least confirm there are no major infeasibilities. When moving forward with module selection in PVSyst, treating layout and string configuration as one design condition rather than separate issues reduces rework later.

Checkpoint 5: Confirm compatibility with orientation, tilt, and array layout

Module selection does not end with a single-unit comparison. In practice you need to consider compatibility with orientation, tilt, and array layout. Just as evaluating the same module under different orientations or tilts in PVSyst can change impressions, modules themselves can be evaluated differently depending on the combination with placement conditions. In other words, you cannot decide which module is best while ignoring site conditions and placement policy.

For example, at sites with strict constraints where array arrangement has many limitations, small differences in dimensions or row cohesion can have a large effect. When adopting layouts with rotated orientations or different tilts, the question can become whether the array as a whole can remain coherent rather than simply the apparent performance. In PVSyst comparisons, a module may be superior under ideal conditions but another module may be easier to handle under a constrained layout.

Also, compatibility with orientation and tilt affects shading. If inter-row spacing and the way shadows fall change, impressions of module selection change as well. Thus, module superiority is not decided by output difference alone but by how the module is placed. Because PVSyst makes comparisons easy, it is important not just to swap modules but to read results in combination with layout.

As a countermeasure, when comparing modules confirm at least how they appear under the assumed orientations, tilts, and array conditions. It makes sense to look once under ideal conditions, but the final judgment should be made within placement proposals that reflect site conditions. If you advance module selection in PVSyst practically, thinking of it as checking placement compatibility rather than equipment selection makes decisions easier.

Checkpoint 6: Don’t separate loss settings and degradation assumptions from the evaluation

When progressing module selection, it is important not to evaluate modules in isolation from loss settings and degradation assumptions. In practice there is a tendency to choose modules first and then refine loss conditions later, but that approach alone is insufficient. This is because generation in PVSyst is revealed not only by basic module performance but also through various losses and considerations of time progression.

For example, even if there are output differences between modules, once you include how losses are modeled and degradation is assumed, the meaning of differences between options can change. In practice people are easily attracted to candidates that look numerically higher, but when considered alongside loss assumptions the overall project advantage may not be that large. If you use PVSyst, you need to choose not only based on single-unit performance but including how the system will appear in the end.

Also, ignoring loss settings and degradation weakens the explanation of comparison results. If you explain a module was advantageous only by simple output differences, you will need to add clarifications later when loss assumptions or long-term operation are discussed. Conversely, if you select with losses and time progression in mind from the start, it is easier to organize where generation differences come from. This greatly helps in internal consensus building.

As a countermeasure, when comparing modules in PVSyst pay attention not only to annual values but also to how losses appear and how assumptions are set. There is no need to detail everything, but at minimum check how stable the comparison results are when losses and degradation are considered. Module selection requires the perspective that it is an evaluation of system feasibility, not a competition of single-unit performance.

Checkpoint 7: Interpret the meaning of differences in comparative simulations

Finally, it is important to interpret the meaning of differences in comparative simulations. PVSyst makes it easy to swap candidate modules and compare, so you may be tempted to judge solely by the final annual generation difference. However, in practice it is more important to understand why a difference occurred and how meaningful that difference is for project decisions than the size of the difference itself. Without the ability to read differences, the numbers will be weak as justification.

For example, even if one candidate slightly outperforms another in annual generation, the evaluation changes depending on whether that difference is due to dimensional differences affecting the number of modules that fit, temperature effects, or ease of forming string configurations. Conversely, it is dangerous to assume two options are equivalent just because the difference is small. Within a small difference, one option may still be superior in terms of layout cohesion, maintainability, or stability of comparison assumptions. Comparative work in PVSyst is not about listing numbers but about organizing the reasons for differences.

In practice, if only numbers are shared early on, the discussion about why a module was chosen tends to come later. Then, when another stakeholder raises a different viewpoint, you may have to redo explanations. If you organize the reasons for differences during the comparative simulation stage, it will be easier to accommodate design, procurement, and maintenance perspectives later. If you use PVSyst results for decision-making, organize how to read differences as well.

As a countermeasure, when creating comparison proposals make clear what conditions are common and which differences you are examining, and then read results including annual values, monthly trends, placement feasibility, and configuration cohesion. Rather than picking the highest number, choose the option that shows the most convincing reason for the difference. When proceeding with module selection in PVSyst, judging after understanding the meaning of differences leads to choices that are stronger in practical terms.

How to turn PVSyst module selection into practical results

What is common to the seven checkpoints above is not treating module selection as a mere equipment comparison. Align the purpose and comparison conditions, look at dimensions and counts as well as output, take temperature conditions into account, ensure consistency with string configuration, confirm compatibility with orientation, tilt, and array layout, include loss and degradation assumptions, and finally interpret the meaning of differences in comparative simulations. If you follow this flow, module selection in PVSyst becomes a design decision to make the entire project feasible rather than just a numeric comparison.

What matters for practitioners is not finding the module that yields the highest generation. The real value is being able to explain why that module is appropriate within the site conditions, layout constraints, electrical conditions, and maintenance considerations. If the approach to module selection is well organized, simulation results become easy to use for internal comparisons and design discussions. Conversely, prioritizing numbers can cause layouts and configurations to collapse downstream, weakening the meaning of the results.

Also, to truly improve the accuracy of module selection, it is important not to conclude with desk-based comparisons alone. If site boundary, orientation, topography, slopes, aisles, and nearby structures are ambiguous, assessments of placement compatibility and the number of installable modules will be weak. To connect PVSyst comparisons to practice you need to iterate between site understanding and simulation. Module selection is not something that is completed on the screen; it is a judgment that includes alignment with on-site conditions.

In that sense, when you want to make on-site positioning and coordinate acquisition more reliable, using iPhone-mounted GNSS high-precision positioning devices like LRTK is an effective approach. If you can more readily organize on-site position information and site conditions, the placement assumptions used in PVSyst module selection will be clearer. By improving desk-based comparison accuracy with PVSyst and supporting on-site surveying accuracy with LRTK, module selection becomes less a performance comparison and more a practice-grounded engineering decision. Carefully advancing module selection not only improves the accuracy of generation forecasts but also enhances the design capability that links desk work and the field.