Five Basic Points When Handling Sloped Roof Projects in PVSyst

Table of Contents

• Basic 1: Clarify roof conditions first for sloped roof projects

• Basic 2: Treat azimuth and tilt settings by separating site conditions and design conditions

• Basic 3: Read shading carefully based on the actual items on the roof

• Basic 4: Tighten electrical design based on differences by roof surface and operational conditions

• Basic 5: Judge simulation results including constructability and on-site verification

Basic 1: Clarify roof conditions first for sloped roof projects

When handling sloped roof projects in PVSyst, what you should lock down first is not the power generation calculation itself but the organization of roof conditions. In practice, upon receiving drawings you may want to start inputting data immediately, but for sloped roofs proceeding in that order tends to increase rework later. If you do not first整理 the roof shape, roof-surface orientation, pitch, positions of ridges and valleys, roofing material, and installation constraints, you can easily end up with a design that looks fine in terms of generation figures but is not feasible in reality.

Be especially aware that in sloped roof projects conditions vary greatly from building to building. Unlike ground-mounted installations where repeated identical conditions can be treated uniformly, optimal layouts for the same capacity can differ by building. Whether the roof is a single slope or a gable, whether the roof surface is a simple rectangle or has penetrations, all of these change the number of modules that can be installed, how shading is received, and how wiring is consolidated. Therefore, if you bias a PVSyst model too much toward a single representative condition, you may get tidy-looking results that diverge significantly from the field situation.

Also, you need to be cautious about what constitutes usable installation area in sloped roof projects. The roof area on a drawing is not necessarily fully usable. Considering edge clearances, margins near ridges and eaves, maintenance access routes, avoidance of existing equipment, and allowances for snow shedding and rainwater management, the actually usable area can be substantially reduced. If you leave this ambiguous when inputting data, assumptions about the number of modules will collapse, string configurations will need to be revised, and you may have to redo the generation evaluation as a result.

A frequent dilemma for practitioners is how finely to divide roof surfaces when modeling. The answer is: if a difference affects generation, separate them; if the impact is essentially the same, combine them. For example, south- and west-facing surfaces clearly have different irradiance conditions and should be separated, and even on the same south face, a small area with strong shadow from an adjacent building is worth modeling as a separate face. On the other hand, if shapes differ slightly but orientation, tilt, and shading conditions are almost identical, excessive subdivision only increases workload. What matters is not the level of detail in the input but not overlooking factors that produce differences.

Furthermore, it is not uncommon for actual site conditions to differ from architectural drawings. A roof that looks simple on paper may in reality host ventilation equipment, piping, rails, inspection components, lightning protection, and more. PVSyst is a convenient analysis tool, but if the assumptions are different, the output figures naturally change. That is why the basic approach for sloped roof projects is to view the roof not just as an installation surface but as a set of constraints. Simply performing this整理 well at the start will greatly improve the accuracy of later settings.

Basic 2: Treat azimuth and tilt settings by separating site conditions and design conditions

The next important point for sloped roof projects is how to think about azimuth and tilt. Many PVSyst users first focus on azimuth and tilt angles, but what matters here is not merely entering numbers but being clear about what those numbers represent. For sloped roofs, the building’s roof pitch may directly determine the installation angle in some cases, while in others the effective irradiance conditions change depending on mounting systems and brackets. In other words, you must distinguish between the roof as a site condition and the photovoltaic equipment as a design condition.

For example, a south-facing sloped roof may look advantageous from a generation standpoint, but that alone is not sufficient for practical decisions. On east- or west-tilting roofs, morning and evening generation characteristics change and evaluations can reverse depending on how they match demand. In projects prioritizing self-consumption, not only annual generation but how much energy is produced during the desired time periods becomes important. Entering azimuth and tilt into PVSyst organizes the numbers, but how you read those numbers depends on the project’s objectives. Simple simplifications like “south-facing is good” or “steep tilt is disadvantageous” are inadequate for practical judgement.

Also, when a roof has multiple surfaces, do not speak for the whole project using only a representative surface. In sloped roof projects south, east, west, and north faces may coexist, and module layouts differ by face. If you summarize everything into a single average value, differences by string and morning/afternoon output biases become hard to see. Whether you split settings by face in PVSyst or group them depends on project scale, but you should at least evaluate separately any surfaces with clearly different generation characteristics.

Another pitfall unique to sloped roofs is that even when designs appear to share the same tilt, actual installation conditions can vary due to construction or component details. Intersections with roofing material, fastening methods, installation clearances, and ridge or eave terminations can shift the assumed ideal arrangement. PVSyst can generate theoretically neat layouts, but on-site you may need to drop one row, leave end gaps, or avoid specific areas. Therefore, the angle conditions you input are not mere physical data but must be set as conditions that can be reproduced after construction.

Thus, azimuth and tilt are central items in generation calculations, but tracking numbers alone makes practical failure more likely. Understanding how the actual roof is shaped, how you will mount equipment on it, and whether that mounting method is truly feasible—all of this is the basics for sloped roof projects. PVSyst is powerful when used as a tool to quantify the result of condition整理, but if you skip condition整理 and use it only to search for an optimum angle, you will likely end up with large discrepancies from the field.

Basic 3: Read shading carefully based on the actual items on the roof

Shading is a factor that can greatly change generation outcomes in sloped roof projects. When running analyses in PVSyst, attention often shifts to orientation and tilt, but in practice misreading shading can significantly distort results. Especially for sloped roofs, unlike ground-mounted sites that assume open surroundings, complex shading from the building itself and nearby objects is common. Treating shading lightly is risky. External factors such as adjacent buildings, rooftop equipment, upstands, parapets, trees, and utility poles are important, and on-roof items like equipment and piping cannot be ignored.

The first thing to be aware of in shading evaluation is to understand during which times of the year, which hours of the day, and on which faces shading occurs and to what extent. On sloped roofs, the same building can experience different shading by face; one string may be shaded only in the morning, another may be significantly affected only in winter, or a single obstacle may strongly impact generation only during specific periods. It is important not only to check the presence of shading but to read shading frequency and duration. Setting shading in PVSyst may look like just another input task, but in practice it’s a fundamental task that determines the reliability of generation figures.

Moreover, shading on sloped roofs often affects only part of a module row, complicating output reduction. Near valleys or roof projections, a seemingly small shadow can concentrate on parts of specific rows and reduce generation more widely than expected. Especially at low solar altitudes in the morning or afternoon, short obstacles can cast long shadows that are hard to intuit from drawings alone. The important point here is to treat shading not as an abstract theoretical factor but as a practical condition directly linked to array layout and electrical design.

Additionally, the quality of on-site verification appears directly in the accuracy of shading analysis. Even with roof plans and elevations, it is common to find differences on site due to added or updated equipment. For sloped roof projects, meticulously identifying what is actually on the roof and incorporating that information into the simulation assumptions is indispensable. If you try to complete everything within the analysis tool input screens, you may mistakenly assume modules are placed where they should be avoided or underestimate shaded areas.

Estimating shading too pessimistically reduces project attractiveness, while too optimistic estimates cause problems later. That is why the basic approach for sloped roof projects is to read shading carefully based on actual conditions. Before checking numbers in PVSyst results tables, you should be able to visualize what happens where on the roof. Practitioners who can read shading correctly make consistent judgments from layout planning to circuit division and expectation-setting.

Basic 4: Tighten electrical design based on differences by roof surface and operational conditions

In sloped roof projects, just because you have mechanically determined how many modules can be placed does not mean the electrical design is settled. When analyzing in PVSyst, you need to consider not only generation-side conditions but also differences by roof surface, how strings are grouped, and alignment with operational conditions. Especially in projects spanning multiple surfaces, even if the layout looks tidy, the electrical combination can be unfavorable. For practitioners, the priority is not maximizing installed capacity but configuring a system that yields stable and meaningful output.

On sloped roofs, because orientation and shading differ by surface, how you treat modules from surfaces with different conditions is key. Forcing surfaces with large condition differences into a single system can increase output variability by time of day and make it hard to achieve expected performance. Conversely, appropriately separating surfaces by condition makes analysis results easier to interpret and design intent easier to explain. PVSyst helps confirm numerical validity, but before that a design decision about how to organize differences by surface is necessary.

Also, due to roof shape constraints, it can be difficult to match ideal module counts in sloped roof projects. One face may fit modules perfectly, while another may end up with awkward counts because of edge clearances or equipment avoidance, complicating circuit design. In such projects it is important not to chase only analytic optima but to translate designs into configurations that are easy to construct and maintain. Even if a design is valid in PVSyst, if wiring routes become excessively complex on site or fault isolation at maintenance becomes difficult, the long-term operational perspective can make it disadvantageous.

Furthermore, designing with operational conditions in mind is essential. Sloped roof projects have various objectives: prioritizing feed-in revenue, prioritizing self-consumption, or planning for future expansion, among others. A configuration that maximizes annual generation is not always optimal for the project. Considering alignment with daytime loads, seasonal output bias, the building’s power acceptance conditions, and relationships with existing equipment, a design that slightly reduces installed capacity but better fits operation may be preferable. PVSyst numbers are very useful for comparison, but you need the perspective to judge whether a design suits the project purpose.

Thus, electrical design is not a mere mid-project coordination step but the central link between roof conditions and generation evaluation in sloped roof projects. Appropriately organize differences by roof surface, devise feasible circuit layouts, and verify validity against operational conditions. When progressing while looking at PVSyst numbers, it is easy to focus on generation quantity, but in practice reproducible designs and explainable rationale are required. Assembling all that is the basic practice for sloped roof projects.

Basic 5: Judge simulation results including constructability and on-site verification

In the final stage of handling sloped roof projects with PVSyst, how you judge the simulation results becomes critical. A common mistake is to finalize design based solely on numbers such as annual generation or performance ratio. In practice, however, the quality of results is not determined by numbers alone. Those numbers only become meaningful once you have confirmed they rest on a constructible layout, a feasible schedule, details that consider maintenance, and conditions that can be verified on site.

In sloped roof projects, squeezing layout a little tighter may seem to increase generation, but in reality it can reduce on-site safety, complicate edge treatments, and worsen maintenance access. Even if the simulation performs well, if the required construction procedures become cumbersome and affect work quality or schedule, the design should be reconsidered. PVSyst provides strong backing for design decisions, but avoid adopting numbers uncritically when the assumptions cannot be realized on site.

Also, when explaining results internally or to stakeholders, you must be able to verbally justify why you chose that layout and those conditions. Sloped roof projects often allow multiple design options for the same building, and numerical differences can be small. In such cases, merely showing the highest number is insufficient; explaining shading impacts, construction constraints, ease of wiring consolidation, maintainability, and alignment with operational goals increases the persuasiveness of the design. For practitioners, the important task is not just reading software output but converting that output into project decisions.

Furthermore, to improve result accuracy, it is effective to return once more to on-site verification. Even after checking drawings, layout options, analysis settings, and electrical design, verifying site conditions can reveal discrepancies from assumptions. Dimensions of sloped roofs, obstacle positions, delivery paths, and conditions for working on the roof are often hard to judge on paper alone. Raising the accuracy of on-site understanding before final decision-making allows PVSyst results to be used in a way that is closer to practical reality.

As described above, in sloped roof projects the flow from organizing roof conditions, thinking about azimuth and tilt, reading shading, electrical design, and result judgment is connected. PVSyst is an excellent tool that numerically supports this flow, but if understanding of the site between inputs and outputs is weak, valuable analysis results cannot be fully utilized. That is why practitioners should not finish with analysis tasks alone but should observe the roof,整理 the constraints, and use results after considering construction and operation.

Finally, to further improve the accuracy of sloped roof projects, enhancing the quality of on-site verification is indispensable. When you need to grasp roof shapes and surrounding conditions more efficiently, incorporating means to handle high-precision positioning on site—such as LRTK (iPhone-mounted GNSS high-precision positioning devices)—makes整理 of design assumptions easier. To raise the accuracy of PVSyst analysis, the foundation is the precision of information obtained at the site as well as desk settings. If you want to advance sloped roof projects more reliably, it is important to review not only how you use analysis software but also the methods for on-site understanding.