8 Practical Points to Keep in Mind for Array Design in PVSyst

Table of Contents

• Why array design in PVSyst becomes important

• Practical Point 1: Align the purpose and assumptions of the array design up front

• Practical Point 2: First clarify the buildable area and clearance conditions

• Practical Point 3: Decide azimuth and tilt angle based on the consistency of the entire array

• Practical Point 4: Consider row spacing together with shading effects

• Practical Point 5: Do not lay out arrays while ignoring terrain and grading conditions

• Practical Point 6: Incorporate maintenance access and constructability from the initial stages

• Practical Point 7: Divide arrays with attention to electrical groupings

• Practical Point 8: Use comparative simulations to discern differences between layout proposals

• How to turn PVSyst array design into practical outcomes

Why array design in PVSyst becomes important

For practitioners running simulations in PVSyst, array design is not merely about making a pleasing layout. How arrays are arranged affects expected annual energy generation, shading impacts, site utilization efficiency, ease of maintenance, constructability, and even how easily the plan can be explained internally. In other words, array design is both about where equipment is placed and a judgment that can determine the viability of the entire project.

In practice, attention often gravitates toward installed capacity and generation figures, and array design can be treated as a later step to make those numbers feasible. In reality, it’s the other way around. If the approach to array design is vague, no matter how favorable the generation numbers you create, you may later discover issues such as equipment that cannot be placed on site, insufficient access paths, excessive shading, or excessive earthworks. If you intend to use PVSyst outputs in practice, you need the attitude of shaping figures around arrays that can actually be placed, rather than producing numbers first and trying to fit arrays to them later.

Also, array design is not about finding a single correct solution. On the same site, layouts that prioritize maximum generation, constructability, minimized earthworks, or maintainability will differ. Therefore, when considering array design in PVSyst, don’t aim solely for maximum generation; design while clarifying what the project prioritizes. If those priorities are not set, comparisons will be inconsistent and decision-making will be unstable.

Furthermore, the quality of array design directly affects the persuasiveness of later reports and comparison materials. If you can explain why you chose a particular layout, a specific walkway width, or a given row spacing, the simulation numbers will be more credible. Conversely, if your rationale for the layout is vague, the generation figures will seem detached and stakeholders will find them hard to accept. Below are eight practical points to focus on in PVSyst array design.

Practical Point 1: Align the purpose and assumptions of the array design up front

The first thing to do in array design is to clarify the design purpose and assumptions. The required level of detail for array design differs depending on whether the goal is a rough site comparison, the detailing of a single proposal, or an initial layout for internal explanation. If you start laying out arrays without this clarity, you may waste time on unnecessary detail or, conversely, produce numbers based on overly coarse assumptions.

In practice, even within the same project the approach to layout changes depending on whether you want to maximize generation, minimize earthworks, or shorten construction time. For example, an array that aligns neatly assuming a flat graded surface might be unrealistic for a project where major reshaping of terrain is to be avoided. First organize the priorities the array design must meet for this project, and then start PVSyst comparisons—this makes later decisions much easier.

If assumptions are not organized, even the creation of comparison scenarios becomes unclear. One proposal might emphasize site utilization while another prioritizes shading mitigation; if you only look at generation numbers without clarifying those differences, the results lose meaning. PVSyst facilitates comparison, but if the axes of comparison are vague, the numbers will just pile up and be hard to use.

A practical countermeasure is to briefly verbalize what you want each layout to show before starting a design: for example, “for rough comparison,” “for shading check,” or “for constructability check.” If the role is defined up front, the depth of layout and the results to examine become aligned. Setting the initial purpose is the most important step to balance efficiency and accuracy in array design.

Practical Point 2: First clarify the buildable area and clearance conditions

A common mistake in array design is placing as much equipment as possible first and then trying to adjust clearances and margins later. In practice, there are always areas you must not touch or clearances you must secure from the start—site boundaries, slope edges, existing structures, drainage facilities, access paths, and maintenance spaces. Postponing these considerations can lead to major rework of an initial layout and reduce the usefulness of comparative simulations.

When designing arrays in PVSyst, it is especially important not to treat the site’s effective area as a simple geometric area. Although the plan might look sufficiently large on paper, the usable area can be considerably limited by edge setbacks and inspection access requirements. Additionally, grading and drainage plans may create bands that, though they look placeable, should be avoided. If you start laying out arrays without incorporating these conditions, generation may appear high but the plan may later be infeasible.

Clearance requirements are not only for regulatory or safety reasons but also affect the overall neatness of the layout. Layouts with ambiguous edge treatments are harder to evaluate for shading and maintainability. In practice, a visually neat array is easier to compare and explain later. When comparing in PVSyst, specifying the usable area from the beginning makes differences between scenarios readable as differences in design conditions.

As a countermeasure, clearly separate usable and non-usable areas before placing arrays. If you first organize where clearances, access paths, and margins must be, you’ll reduce layout revisions and stabilize downstream decisions. Practically, array design should start by defining where you are allowed to place equipment, not by searching for places to put it.

Practical Point 3: Decide azimuth and tilt angle based on the consistency of the entire array

In array design, azimuth and tilt angle should be decided not by seeking a standalone optimum but by considering the consistency of the entire array. In PVSyst, changes in angle make generation differences easy to spot, which tends to draw attention to the angle that gives the highest numbers. However, in practice orientation and tilt are never decided independently; they must be considered together with row spacing, site shape, shading behavior, grading ease, and access configuration.

For example, a certain tilt angle may be advantageous for annual generation but might require wider row spacing and thus reduce site utilization. A particular azimuth might look good numerically but could worsen the handling of site edges and break the overall coherence of the array. What to look at in PVSyst is not the superiority of a single angle but how well the entire array works when that angle is adopted.

In practice, it is common to pick the ideal azimuth and tilt first and then design the layout, but this approach often reveals difficulties later. Rather, based on site shape, clearance conditions, and row configuration strategy, search for an azimuth and tilt angle range that fits without forcing the layout. PVSyst simulations are effective for making those adjustments.

As a countermeasure, when comparing azimuth and tilt options, always verify not only generation but also the overall feasibility of the array. Look for the condition that fits most naturally, not just the condition that gives the highest number. In array design, prioritizing the consistency of the overall layout often yields stronger proposals than optimizing angles alone.

Practical Point 4: Consider row spacing together with shading effects

An unavoidable topic in array design is the relationship between row spacing and shading. If you try to make generation look as high as possible in PVSyst, you will be tempted to pack as many arrays onto the site as possible. But tighter row spacing increases shading impacts, causing significant losses during certain hours or seasons. Conversely, wider spacing reduces shading but raises questions about site utilization and capacity. In short, row spacing is not just a dimension; it is a design parameter that balances generation and site efficiency.

A common mistake in practice is choosing row spacing by feel after the tilt is set. In reality, required spacing changes with tilt, and shading behavior also depends on site orientation and terrain. When reviewing PVSyst results, you must check shading losses and verify whether the chosen row spacing is truly appropriate. Proposals that make generation look better often do so by applying lenient shading assumptions—this should prompt skepticism.

Row spacing also affects maintenance access and safety. Spacing should be considered not only for shading but also for whether people can enter easily, perform cleaning and inspections, and respond to incidents. Spacing widened to avoid shading can also improve maintainability, while layouts packed to the limit can make on-site work difficult. In PVSyst array design, do not consider shading and access separately.

As a countermeasure, when deciding row spacing, compare shading effects, site efficiency, and maintainability together. Make sure you can explain in words why that spacing is appropriate, not just show numbers. The quality of array design is judged not by how many rows you can place but by whether you can justify the chosen spacing.

Practical Point 5: Do not lay out arrays while ignoring terrain and grading conditions

Designing arrays in PVSyst assuming a flat surface and arranging them neatly makes generation comparisons easier. However, actual sites are not always flat. There are always constraints on site—undulations, level differences, slopes, existing ground conditions, and drainage gradients. Ignoring these in array design can make a tabletop plan attractive but highly susceptible to major revisions during grading or construction.

In practice, designers sometimes lightly treat terrain at the initial layout stage to first look at capacity and generation. That approach has value at the conceptual stage. Even so, you must be aware where the layout is idealized and where it follows actual site conditions. Treating a terrain-ignored plan as if it were a real proposal reduces the value of comparisons because it fails to align with grading volumes, slope treatments, and drainage planning.

Ignoring grading conditions also clouds judgment on azimuth and tilt. Without considering how much ground adjustment is needed to achieve an ideal orientation or tilt, you cannot judge whether a given option is practically adoptable. In PVSyst array design, the goal should not be the layout that yields the highest numbers but the layout that is most likely to be realized on that site. Being aware of terrain and grading conditions early reduces the need for large rework later.

As a countermeasure, from the initial stages of array design, consider at least the general terrain and grading policy when placing arrays. Full detail is unnecessary, but clearly distinguish whether a layout is a flat-idealized proposal or a site-following proposal. If that distinction is made, PVSyst comparisons will be meaningful. Remember that array design is not about neat arrangement on drawings but about whether the layout can actually be placed on the site.

Practical Point 6: Incorporate maintenance access and constructability from the initial stages

If you chase generation and site efficiency in array design, maintenance access and constructability tend to be postponed. In practice, if later you find insufficient walkways, no working space, or difficult movement between equipment, you will need to revisit the entire layout. Maintenance access and constructability are not only operational concerns post-completion; they are conditions that determine the quality of the array design itself.

Especially when comparing in PVSyst, more tightly packed layouts may look attractive for generation and capacity. But if such a layout causes problems during construction or compromises maintenance routes, it becomes impractical. Considering inspection, cleaning, replacement procedures, and emergency checks, some margin and planned work zones are needed from the start. Layouts with ambiguous maintenance access are hard to defend even if their numbers look good.

Including constructability considerations early can change layout priorities. A layout with slightly lower generation but easier material delivery, simpler construction sequencing, and lower construction risk may have higher adoption value overall. Because PVSyst does not easily quantify constructability, practitioners need to consciously incorporate these concerns into layouts. Over-optimizing on the desktop often leads to difficulties during construction.

As a countermeasure, from the initial stage of array design, decide which areas will be access paths and which will be working zones, and design accordingly. Don’t select layouts based solely on PVSyst generation comparisons—organize proposals also by maintainability and constructability so later explanations go smoothly. Strong practical array designs are not just those with high numbers; they are proposals that consider construction, maintenance, and repair.

Practical Point 7: Divide arrays with attention to electrical groupings

Array design should be considered not only in terms of visual arrangement but also with attention to electrical grouping. When evaluating layouts in PVSyst, it’s natural to focus on area utilization and shading, but in practice it’s also important to decide how arrays will be grouped electrically and in what units they will be managed. Poor electrical grouping complicates later design, and makes result organization and comparison harder.

In practice, layouts that look neat may still progress with ambiguous electrical divisions. Then, although layout comparison is possible, at the detailed design stage you must reorganize divisions, which can change shading and wiring considerations. Ignoring electrical groupings at the array design stage allows later constraints to intrude and can reduce the meaning of the initial comparison results. To connect PVSyst results to detailed design, do not separate layout and electrical divisions.

Electrical coherence also aids fault isolation and maintenance response. If it’s clear where equipment is electrically segmented, differences between comparison proposals are easier to explain. Conversely, layouts that were densely packed for visual purposes often require later reorganization, increasing the explanatory burden in reports and internal reviews. In PVSyst array design, consider whether the layout links smoothly to downstream processes, not just how it looks or what the numbers are.

As a countermeasure, when examining layouts, pay attention to how arrays are divided and grouped electrically. You don’t need to work out complex detailed designs at this stage, but at minimum check whether the layout can be split into electrically reasonable units. Balancing visual alignment and electrical consistency in array design ultimately simplifies the entire design process.

Practical Point 8: Use comparative simulations to discern differences between layout proposals

The final point in array design is to use comparative simulations to discern the differences between layout proposals. In practice, it’s tempting to rely solely on experience to pick a layout, but optimal arrangements change with site conditions and priorities. The value of PVSyst is that it lets you compare multiple proposals both numerically and in terms of conditions, and organize why you would select a given option.

In comparative simulations, it is important to be clear about what variables you are changing. For example, whether you want to examine differences in row spacing, azimuth, or compare a grading-minimizing proposal with a generation-prioritizing proposal will determine which conditions should be held constant. If this is unclear, multiple differences can overlap across proposals and it becomes hard to know which condition drove the results. PVSyst comparisons are convenient, but without organized axes the numbers will multiply without insight.

Comparative simulations are not only for selecting the single highest-generation proposal. Use them to characterize each proposal: one may be slightly superior in generation, another may be better for constructability, and a third may have less shading and be easier to maintain. PVSyst highlights numeric differences, but in practice you must interpret what those differences mean. If differences are small, that can justify prioritizing other conditions; if differences are large, it is worth investigating the reasons in depth.

As a countermeasure, when creating comparison proposals, clearly define common conditions and differing conditions. Then judge proposals holistically by annual energy, monthly trends, shading impacts, layout efficiency, constructability, and maintainability. To turn PVSyst array design into practical outcomes, you need the ability to read not only the numbers but also the character of each proposal. Comparative simulation is the most practical means to do that.

How to turn PVSyst array design into practical outcomes

The eight practical points above share a common theme: do not treat array design as a mere placement task. From clarifying purpose, to defining buildable area, to azimuth and tilt, row spacing, terrain, maintenance access, electrical grouping, and comparative simulation—everything is connected. Conducting array design in PVSyst should be seen as balancing generation and feasibility, not simply deciding positions for equipment.

For practitioners, the goal is not to find the layout with the absolute highest generation. Real value lies in being able to explain why a given layout is appropriate within the site and construction conditions. If array design thinking is organized, simulation numbers become easy to use in internal comparisons and explanatory materials. If layout rationale is vague, numbers lead and rework and explanatory burdens increase.

To truly improve the accuracy of array design, do not stop at desk-based simulations. If site boundaries, terrain undulations, slope orientations, existing structures, access paths, and grading conditions are unclear, layout comparisons tend toward idealization. To make PVSyst results practical, you must iterate between site understanding and simulation to refine accuracy.

In that sense, when you need more reliable on-site position confirmation or coordinate acquisition, using iPhone-mounted high-precision GNSS positioning devices such as LRTK is an effective option. If you can organize on-site position information and site conditions more reliably, PVSyst assumptions become clearer. Increasing desktop comparison accuracy with PVSyst while supporting on-site understanding with LRTK creates a workflow in which array design becomes not just a calculation but a judgment rooted in the site. Carefully refining array design not only improves the accuracy of generation forecasts but also enhances the design capability that connects desktop work and the field.