Five Checkpoints When Reflecting Racking Conditions in PVSyst

Table of contents

• Concepts to grasp before reflecting racking conditions in PVSyst

• Checkpoint 1: Are the placement assumptions consistent with the actual racking plan?

• Checkpoint 2: Are the racking tilt angle and azimuth appropriate as generation conditions?

• Checkpoint 3: Are you underestimating row spacing and how shadows form?

• Checkpoint 4: Are you ignoring terrain and differences in installation height?

• Checkpoint 5: Have you confirmed the linkage between racking conditions and electrical design?

• How to handle site information to improve the accuracy of racking conditions

• Summary

Concepts to grasp before reflecting racking conditions in PVSyst

When entering racking conditions in PVSyst, the first thing practitioners should be aware of is that it is not enough to simply fill in numbers. Racking conditions may appear to be just part of a generation simulation, but in reality they are important inputs that connect to layout planning, earthwork planning, shadow assessment, maintenance access routes, and even assumptions for electrical design. If you take the reflection of racking conditions lightly, the overall design consistency can easily break down later.

Especially at the stage when you start examining things in PVSyst, detailed drawings are often not yet finalized. If you enter too many provisional numbers in that state, you may produce plausible-looking results while the evaluation drifts away from actual site conditions. Conversely, if you align conditions early on to be close to final design dimensions and concepts, you can reduce rework in later stages.

What matters when reflecting racking conditions is not only checking each input item individually. It is important to consider the tilt angle, azimuth, row spacing, installation height, and relationship with terrain together as a single design intent. This article organizes common practical oversights to watch for when reflecting racking conditions in PVSyst into Checkpoint 1 through Checkpoint 5.

Checkpoint 1: Are the placement assumptions consistent with the actual racking plan?

The first thing to confirm is whether the placement assumptions you set in PVSyst match the actual racking plan you intend. If this point is left ambiguous, even careful adjustments of tilt angle and row spacing afterward will shift the foundation of the entire simulation. Because it is easy to miss this discrepancy if you only look at generation results, caution is required.

For example, the arrangement of racks may be assumed to be continuously aligned in some cases, while in other sites they may be arranged discontinuously by blocks to follow the site shape. On sites with earthwork conditions, site boundaries, maintenance access routes, or slope setbacks, a simple repetitive layout may not reflect reality. Nevertheless, if you proceed with an evaluation using uniform placement conditions, you may end up overestimating area efficiency and shadow behavior.

Also, within a single project not all racks necessarily follow the same conditions. A site may contain blocks predominantly facing south and other blocks where azimuths are unavoidably rotated due to terrain. On sloped sites, even if things look consistent on a single drawing, construction details may differ, and in practice rack heights or spacing conditions can change. Ignoring such differences and treating the whole as a single representative condition may produce averaged results that hide risks needed for practical decision-making.

Therefore, before entering racking conditions in PVSyst, it is effective to be able to describe the actual racking plan in writing. Organize which directions, what tilt angles, what spacing, and where exceptions occur before inputting them so the necessary partitions become clearer. Verifying the placement concept before inputting numbers is the quickest path to improved accuracy.

Even more important is not to treat early provisional layouts as finalized conditions. As the design progresses, rack layouts will gradually change due to revisions to access widths, earthwork volumes, and the allocation of combiner boxes or maintenance spaces. PVSyst conditions should be updated accordingly, but in practice initial inputs often remain unchanged. Consider placement assumptions not as fixed information but as data to be reviewed according to design progress.

Checkpoint 2: Are the racking tilt angle and azimuth appropriate as generation conditions?

Among racking conditions, tilt angle and azimuth are representative items that directly affect generation. Many practitioners naturally focus on these first, but what to note here is that an angle that looks good in theory may not necessarily be adoptable in practice. Because PVSyst responds directly to the input angles, chasing numbers alone can steer you away from your design intent.

Tilt angle relates not only to annual generation but also to seasonal output balance, shadow impact, wind considerations, structural fit, and maintainability. Increasing the angle may appear advantageous for generation in some cases, but it can require wider row spacing or create disadvantages in wind and structural aspects. Conversely, decreasing the angle may improve shadow performance but negatively affect rain runoff, soiling retention, and constructability. In short, tilt angle is not a number decided solely by generation.

The same applies to azimuth. While getting closer to an ideal orientation is important, actual projects often cannot perfectly align due to site shape, terrain, or adjacent equipment. At that point, you must clarify how much azimuth deviation is acceptable, whether to evaluate by block, or whether to summarize with a representative condition. Ignoring azimuth variation and treating it as averaged will reduce not only generation accuracy but also the reproducibility of shadow conditions.

In practice, it is effective to judge tilt angle and azimuth in combination with row spacing and installation area rather than trying to optimize them separately. When reviewing PVSyst results, check not only differences in annual generation but also generation per unit area, the relationship with shadow losses, and seasonal biases. Do not adopt an angle simply because it yields slightly higher numbers; consider whether that angle can actually be reproduced on site.

Also, racking types may change during design. For example, an angle that was feasible under assumed support conditions may become impractical after reviewing foundation or ground conditions. If only the PVSyst settings remain as before, the simulation results will no longer reflect the current design. Because tilt angle and azimuth are frequently reviewed items, it is important to regularly verify that they match the latest racking conditions.

Checkpoint 3: Are you underestimating row spacing and how shadows form?

When handling racking conditions in PVSyst, row spacing and shadow evaluation are areas where practical discrepancies often arise. Spacing between racks is not merely a dimensional issue; it directly affects generation, land utilization efficiency, maintainability, and constructability. Despite this, in early design people often prioritize using the site as effectively as possible and tend to underestimate shadow formation.

If row spacing is too narrow, shadows during winter or at morning and evening times can intensify and cause greater-than-expected losses. Moreover, this impact is not limited to a few time periods but accumulates over the year and cannot be ignored. When checking results in PVSyst, overall generation differences may look small, but time-of-day or seasonal analysis can reveal concentrated losses under specific conditions. You need to consider whether such biases are acceptable for operation.

What makes judging row spacing difficult is the interaction with angle and installation height. For the same tilt angle, shadow length changes with height, and for the same height the apparent view changes with ground slope. Additionally, when you consider maintenance paths, drainage, and earthwork fit, the spacing you thought you secured on drawings may not be sufficient in the field. Numbers entered into PVSyst may seem simple, but multiple design conditions lie behind them.

A common practical mistake is determining row spacing based only on rack dimensions and not reflecting site clearance margins. Considering construction tolerances, foundation position variability, ground irregularity, and future maintenance space, dimensions that theoretically fit exactly are often impractical. Even if a simulation looks acceptable, slight on-site deviations can change shadow conditions and create discrepancies with the generation assessment. It is safer to think of row spacing in terms of dimensions that can realistically be maintained rather than minimum values.

Do not forget that shadow considerations involve not only inter-row effects but also relationships with surrounding conditions. Where earthworks create slopes, where part of the site has elevation changes, or where adjacent equipment is close, the issue is not just row spacing. Even if racking conditions entered into PVSyst are well defined, if the site’s three-dimensional conditions are not considered elsewhere, shadow losses may be underestimated. When deciding row spacing, it is important to consider sectional views as well as plan views.

Checkpoint 4: Are you ignoring terrain and differences in installation height?

When reflecting racking conditions, proceeding with inputs that assume flat land will greatly reduce result reliability on sites with terrain. In reality, it is rare for an entire site to be completely flat; gentle slopes, localized undulations, and earthwork-induced steps often exist. Entering only representative racking conditions in PVSyst may not sufficiently represent those influences.

Installation height is another easily overlooked item. The minimum ground clearance of racks and front-back height differences affect shadow formation and maintainability, and combined with terrain they change effective clearances. Even if you feel reassured by height dimensions on drawings, variations in ground surface can leave insufficient clearance in certain locations. As a result, expected ventilation conditions or maintenance spaces may become difficult to secure.

Be especially careful about fixing racking conditions at a stage before earthwork plans are finalized. The way racks appear and shadow conditions will change between pre-earthwork terrain and post-earthwork finishes. If you carry simulation results based on existing ground forward unchanged, they will diverge from detailed design. Conversely, if earthwork direction is understood, even without finalized details you should organize assumptions about the degree of flattening expected and which blocks will retain elevation differences.

Also, within the same project it is common for installation heights to be inconsistent. Due to differences in ground conditions or support methods, rack heights may change in some blocks. Treating the whole as a single averaged height will yield half-measures in shadow and maintainability evaluations. Even when you want to simplify PVSyst inputs, if condition differences are large enough to affect generation or construction, it is more realistic to separate blocks.

Being aware of terrain and installation height differences is not only about improving simulation accuracy. It also allows you to feed probable on-site issues back into the design earlier. For example, if a block shows strong shading, narrow maintenance paths, or insufficient under-rack clearance, you can revise layout plans or earthwork policies. It is important to use PVSyst not only as a tool for checking results but also as a tool for detecting inconsistencies with terrain conditions.

Checkpoint 5: Have you confirmed the linkage between racking conditions and electrical design?

Racking conditions are often thought to be about mechanical layout only, but in reality they are strongly linked to electrical design. If you treat these separately, you may get PVSyst simulation results yet create an impractical overall plan. In practice, changes in layout affect circuit configuration, cable routing lengths, and block divisions, so reflecting racking conditions must be considered together with electrical conditions.

For example, if the number of rows or block divisions change, assumptions about where to consolidate and how to configure circuits also change. Forcing blocks with differing azimuths or shadow conditions into the same circuit scheme can be disadvantageous both for generation assessment and operation. Do not be satisfied only with entering racking conditions into PVSyst; confirm whether that layout leads to an electrically straightforward configuration.

Minor adjustments to racking conditions can also affect electrical losses and operability. For instance, shifting layouts to widen maintenance paths can lengthen cable runs. Or dividing blocks to fit terrain may create cases where it is better to separate electrical groupings. Ignoring such impacts and comparing only generation figures can produce inconsistent evaluations.

As a practitioner, develop a habit of checking what the updated racking conditions will demand from the electrical design when you change them. Conversely, if circuit configurations or equipment placements change for electrical reasons, those changes must be fed back into PVSyst’s racking conditions. Avoid a state where only one side is updated. As the design progresses, mechanical and electrical information become less independent.

Ultimately, what matters is that the project is viable, not merely that conditions are established in PVSyst. Even if racking conditions are neatly reflected in generation numbers, if they are not consistent with electrical design, constructability, and maintainability, they are insufficient for practical decision-making. The point of Checkpoint 5 is to treat racking conditions not as inputs only for generation simulation but as design conditions for the whole project.

How to handle site information to improve the accuracy of racking conditions

We have covered Checkpoints 1 through 5, but what ultimately determines final accuracy is how site information is handled. Even if you refine racking conditions on paper, if site elevation differences, site boundaries, earthwork direction, and relationships with existing structures are unclear, the basis for input conditions becomes weak. Improving PVSyst setting accuracy requires converting site information into design assumptions.

In practice, information obtained during site surveys is not always organized in a form readily usable for simulation. You may have elevation data that is hard to apply by block, or plan shapes without a clarified approach to maintenance paths. Therefore, it is necessary not only to collect site information but to reorganize it into units needed to confirm racking conditions. Make it possible to determine which blocks have differing conditions and which can be treated as representative.

Also, the role of site information changes between early and late design stages. Early on it is important to grasp major terrain trends and layout constraints, while later height and spacing details become important. In other words, the same site information cannot be fully utilized unless you clarify when and for what purpose you will use it. When reflecting racking conditions in PVSyst, assess whether the necessary site information is available at that time.

If you want to streamline site condition capture, it is advantageous to have methods that quickly organize positional and height information. Especially for projects where you refine design while checking block-by-block differences, being able to quickly confirm site shape and elevation differences directly affects how fast you can revise racking conditions. Useful for this is an iPhone-mounted high-precision GNSS positioning device like LRTK. By making it easier to capture position and height on site, you can more easily organize assumptions before reflecting them in PVSyst and strengthen the basis for racking conditions.

Summary

When reflecting racking conditions in PVSyst, the goal is not merely to input tilt and azimuth numbers. What matters is verifying that the input conditions match project reality, including actual layout planning, row spacing, terrain conditions, installation heights, and linkage with electrical design. Carefully reviewing Checkpoints 1 through 5 can significantly change the reliability of simulation results.

In practice, racking conditions will change gradually as design progresses. Therefore, do not fix initial settings once entered; review PVSyst conditions along with updates to layout plans and site conditions. Rather than chasing generation figures alone, continuously check what design assumptions those figures rest upon to reduce rework.

If you want to further improve the accuracy of racking condition reflection, do not complete everything as desk work—establish a system that can organize site information early. For practitioners who want to align PVSyst assumptions with site conditions and elevation differences, an iPhone-mounted high-precision GNSS positioning device like LRTK can be a powerful option linking site surveys and design. When you want to make racking conditions closer to reality, consider such site-measurement approaches as part of your process.