Seven Points to Note When Analyzing Rooftop Installations with PVSyst

Table of Contents

• In rooftop projects, how you set assumptions greatly affects results

• Point 1: Do not reuse input conditions with a ground-mounted mindset

• Point 2: Do not over-aggregate roof orientations and tilts

• Point 3: Do not oversimplify rooftop shading conditions

• Point 4: Do not equate usable installation area with power-generating area

• Point 5: Do not underestimate temperature and ventilation conditions

• Point 6: Do not postpone wiring plans and electrical constraints

• Point 7: Do not judge analysis results by annual energy only

• Summary

In rooftop projects, how you set assumptions greatly affects results

When analyzing rooftop projects with PVSyst, many practitioners first want to know how much energy can be expected, whether the economics work, and whether the proposed installation conditions are feasible. However, compared with ground-mounted projects, rooftop projects tend to be much more sensitive to how input assumptions are set. This is because orientation, tilt, obstructions, spacing, temperature rise, wiring constraints, and other factors interact complexly within the limited area of a roof.

In practice, analyses are often performed at multiple stages—rough estimates during sales, comparisons in basic design, and feasibility checks before detailed design. The required accuracy differs slightly at each stage, but what is commonly important at every stage is how accurately site conditions are reflected in the assumptions. If inputs are not well prepared and you only look at analysis outputs, numbers will come out, but whether those numbers hold up on site is another matter.

Even roofs that look simple can actually have different conditions on the south and north faces, or within the same face be affected by parapets or equipment mounts, or require evacuation routes and maintenance spaces. Ignoring these practical conditions in an analysis can cause later-stage problems such as layouts that won’t fit, wiring that can’t be routed, or generation that falls short of expectations. Below are seven often-overlooked points to keep in mind when handling rooftop projects in PVSyst.

Point 1: Do not reuse input conditions with a ground-mounted mindset

The first thing to watch for in rooftop projects is not to simply reuse assumptions from ground-mounted projects. Ground-mounted projects tend to allow consolidated orientations, tilts, and row-spacing conditions and generally have higher layout flexibility. Therefore, using representative values often does not produce large overall errors. That approach does not translate directly to rooftop projects.

For example, even on the same building, mono-pitched (shed) roofs, gabled roofs, flat roofs, and profiled metal roofs require very different design approaches. On flat roofs you can more freely set the tilt angle when mounting racks, but shadow impacts and spacing considerations become important. On pitched roofs you often follow the existing roof angle, so despite apparent simplicity, orientation differences and per-face generation differences can appear directly. Ignoring these differences and applying uniform conditions will produce neat-looking results that are difficult to use in practice.

Rooftop projects are often strongly constrained by building-related conditions and cannot prioritize generation alone. Factors such as load-bearing capacity, roof waterproofing, circulation during equipment replacement, and the need to secure firefighting equipment or access hatches affect layouts beyond generation considerations. In other words, before inputting into PVSyst you should recognize that rooftop projects are less about optimizing generation and more about determining how far a solution can be realized within constraints. That recognition alone changes how you construct input conditions.

Also avoid overly idealized assumptions at the rough-estimate stage. Practitioners often need early-stage numbers, but if you analyze assuming full use of the roof, no shading, and standard temperature conditions, numbers tend to drop when conditions are tightened later. If the initial proposal is too optimistic, it becomes hard to revise internally and with clients. For rooftop projects it is better to start from conservative, realistic assumptions to make later-stage alignment easier.

Point 2: Do not over-aggregate roof orientations and tilts

If you generalize roof orientations and tilts too much in rooftop projects, analysis accuracy can fall significantly. Especially on buildings with multiple roof faces, south, east-west, and north-leaning faces may coexist, each with different irradiance conditions. Processing these with a single representative value can mislead not only annual generation but also generation characteristics by time of day.

For example, grouping east- and west-facing roof faces together and inputting an average orientation can distort the shape of morning and evening generation peaks and the noon peak. These differences matter in practice. For self-consumption projects, when generation occurs is important; for projects that must consider reverse power flow or coordination with utility connection equipment, time-based characteristics cannot be ignored. It is not enough that annual totals are similar; modeling must reflect per-roof-face generation behavior.

The same applies to tilt: roofs that appear to have similar angles can actually vary slightly. Ignoring these small differences can accumulate—low-tilt roofs may suffer more from soiling, high-tilt roofs may receive light differently—and produce notable differences in results. Especially for existing buildings with multiple connected structures, renovation histories can cause greater-than-expected variability in roof conditions.

That said, it is not necessary to split everything to the smallest detail. In practice you need to judge where to separate and where to aggregate. Distinctly different orientations, tilts with non-negligible differences, or faces with different obstruction conditions should be separated. Conversely, over-segmenting identical faces complicates model management and comparison. The purpose of using PVSyst is to create a decision-making state close to reality. Design your roof-face segmentation against that purpose.

Point 3: Do not oversimplify rooftop shading conditions

If you oversimplify shading on rooftop projects, the reliability of analysis results drops quickly. Unlike ground-mounted projects, roofs often have more obstructions than expected: HVAC units, ventilation equipment, parapets, penthouses, railings, antennas, lightning protection, and many other non-generation-related items that cast local shadows. These are commonplace on site but easily overlooked in the analysis model.

Pay special attention not only to large obstacles that cast significant shadows year-round but also to small obstacles that matter at low sun angles in winter. Equipment or upstands that seem insignificant during casual site checks can have non-negligible effects in the morning, evening, or winter. Shading does not just reduce usable area; it leads to non-uniform irradiance across modules and string-level output drops, which can cause actual generation to differ far more than expected.

Shading issues also depend on off-roof factors: adjacent buildings, trees, signs, and wall upstands near the site boundary can sometimes be significant. In urban rooftop projects, nearby buildings can cast strong shadows on particular faces in the morning and evening. It is easy to assume short-duration shading is negligible, but concentrated shading on specific orientations can bias time-of-day generation and reduce expected self-consumption benefits.

In practice you do not need to reproduce every micro-detail, but prioritize incorporating shading that has a large impact on generation. To do that, gather site photos, roof plans, elevation data, and equipment layout drawings as early as possible. For rooftop analyses, assume shading exists from the start rather than treating it as a later consideration. Analyses that understate shading may look attractive, but as design progresses required corrections tend to grow, so treat shading cautiously from the outset.

Point 4: Do not equate usable installation area with power-generating area

A very common mistake in rooftop projects is treating the usable installation area as the same as the power-generating area. A roof may look large on drawings, giving the impression that most of it can be filled with PV equipment; in reality it is not that simple. For construction, maintenance, and safety reasons there are multiple spaces on roofs that should be left clear.

First consider maintenance access. If widths for inspection, cleaning, and equipment replacement are not secured, post-installation maintenance becomes extremely difficult. Also account for areas around access hatches or inspection ports, access paths to mechanical equipment, evacuation routes, and safety clearances along the perimeter. Forcing modules into these areas may increase theoretical installed capacity on paper, but in detailed design substantial removals will be necessary.

Next are less-visible constraints related to roof shape. Parapet upstands, drains, steps, expansion joints, waterproofing interfaces, and roof edges include numerous elements that affect installation feasibility but are hard to read from drawings alone. On existing buildings, drawings and current conditions may differ, so estimating generation area from drawing dimensions alone is risky. Layout assumptions entered into PVSyst must be realizable configurations to be meaningful.

Also, more modules on a roof is not always better. Densely packed layouts create shading issues, reduce workability, create heat pockets, and impose constraints for future replacements. On multi-face projects, installation and maintenance characteristics differ by face, so judging by area efficiency alone can be misleading. In practice you must balance maximizing installed capacity with producing a design that can be operated.

Therefore, in rooftop analyses start by defining the actually usable effective area rather than looking only at total roof area. In other words, PVSyst should be used to evaluate realistic installed capacity that reflects constraints, not an idealized maximum. This approach may yield somewhat conservative early generation estimates, but it reduces rework later in design.

Point 5: Do not underestimate temperature and ventilation conditions

Temperature conditions are also important in rooftop projects. While irradiance and orientation draw attention in generation analyses, module temperature rise is a key factor influencing actual generation. Rooftops are more susceptible to reflected and retained heat from roofing materials, and conditions can be harsher than ground-mounted scenarios.

For example, when installing modules flush with a pitched roof, ventilation strategy can trap heat. On flat roofs, rack height and arrangement change wind flow, so temperature rise tendencies can differ even under the same irradiance. If you handle temperature conditions in analysis only with generic representative values, summer generation drops may not be fully reflected. Even if annual generation differences look small, outputs during demand-peak hours can be affected, making this an important practical consideration.

Roofing material and building use also change conditions. Metal roofs, well-insulated roofs, or buildings with high HVAC loads can produce different thermal environments around the roof surface. Some roofs feel much hotter on site than expected; assuming standard conditions in those cases tends to be optimistic. Temperature is a less visible input but an important point in justifying differences in generation.

The aim is not to be overly pessimistic but to understand rooftop-specific thermal risks and reflect them in assumptions. Evaluate whether the layout allows adequate ventilation, whether spacing from the roof surface is sufficient, or whether the array is densely packed. Even with favorable irradiance, poor temperature conditions can prevent expected performance. Differences might appear small in raw numbers but are useful discriminators when comparing multiple options, so handle temperature carefully.

Point 6: Do not postpone wiring plans and electrical constraints

Even if a rooftop layout appears to work spatially, it may become unfeasible once wiring plans and electrical constraints are finalized. When analyzing in PVSyst you tend to focus on irradiance and layout, but in real projects how roof faces are divided and the location of equipment cause constraints on cable length, circuit partitioning, and consolidation methods. Postponing these considerations causes large discrepancies between analysis assumptions and detailed design.

In multi-face projects, electrical consolidation varies even for the same area. How you group faces with different orientations or tilts into systems, how you route cables to equipment locations, and how you take indoor drop routes affect losses and constructability. A neat layout in analysis can result in complex circuit configurations in practice and lower-than-expected efficiency.

Also, on rooftop projects modules cannot always be placed uniformly due to obstruction avoidance and maintenance access, resulting in uneven string layouts or faces with differing conditions, which complicates electrical design. If the analysis assumes ideal configurations, translating to a real circuit layout can change output conditions and require re-calculation. In other words, wiring planning should not be left to the end; it should be considered alongside initial analysis.

In practice, choose configurations that are feasible and reproducible rather than only those with highest generation. Consider how to segment systems by roof face, cable distances, and ease of isolation during maintenance; basing analyses on electrically realistic configurations reduces rework. Good PVSyst numbers are not enough if wiring and equipment placement render a plan impractical—construction phases will require repeated adjustments. It is important to link generation analysis and electrical design early in rooftop projects.

Point 7: Do not judge analysis results by annual energy only

Annual generation tends to attract attention in rooftop analyses. Although annual generation is an important metric, judging a project solely by that number is risky. Rooftop projects with similar annual totals can vary widely in layout feasibility, shading bias, temperature conditions, constructability, and maintenance friendliness. Similar numbers do not mean equivalence.

For example, one option might show slightly higher annual generation but leave little roof margin, cramped maintenance access, and susceptibility to shading at particular times. Another option might have a lower annual figure but a simpler circuit layout, better roof utilization balance, and lower operational risk. Practitioners need to know which option can be implemented stably on site. Analysis outputs are decision-making inputs; the numbers themselves are not the goal.

Also read results in light of the building owner’s objectives. Whether the focus is on self-consumption, exporting surplus, matching daytime demand, or peak shaving changes how the same generation figure is evaluated. Roofs with dispersed orientations may generate more in the morning and evening while suppressing noon peaks, offering benefits not visible in annual totals. Conversely, a south-facing concentrated layout with a high annual total may be misaligned with operational goals.

When reading results, consider annual generation, monthly trends, time-of-day characteristics, loss breakdowns, shading impacts, temperature effects, and differences by face. For rooftop projects especially, be prepared to explain why a figure is as it is. For internal approvals and client explanations, simply presenting the highest generation option is insufficient; you must demonstrate that the option is reasonable given constraints. Use PVSyst not only to produce numbers but also to structure design rationale.

Summary

When analyzing rooftop projects with PVSyst, the most important thing is not to treat them as an extension of ground-mounted projects. How you divide roof orientations and tilts, how much shading you reflect, how you define usable installation area, how you consider temperature and ventilation, and when you incorporate wiring and circuit configuration—all these change the meaning of analysis results. Rooftop projects have more constraints than they appear to, and optimizing for generation alone can lead to plans that are hard to realize on site.

For practitioners, the goal is not to create attractive numbers but to prepare comparable, explainable options that do not break down in later stages. To do that requires judgment about which conditions to include and at what level of precision, beyond just mastering PVSyst operation. Because the quality of site information directly affects analysis quality in rooftop projects, do not proceed from drawings alone; pair analysis with on-site verification.

In that sense, do not try to complete everything inside analysis software—improving the accuracy of site surveys and position confirmations also raises analysis quality. When you need more reliable information about rooftop equipment positions, clearances from obstructions, and surrounding conditions, combining methods that make high-precision positional data easy to handle on site—such as LRTK (iPhone-mounted GNSS high-precision positioning device)—can help organize design assumptions before design begins. Practitioners who want to improve PVSyst analysis accuracy should review not only software settings but also how they collect the site data that becomes the analysis input, including using cm level accuracy (half-inch accuracy) methods when appropriate.