7 points to check when advancing a grid-connected design in PVSyst

Table of contents

• What to finalize first in a grid-connected design

• Check 1: Align interconnection conditions and design assumptions up front

• Check 2: Don’t determine equipment capacity based solely on energy production

• Check 3: Don’t set losses roughly—align them with wiring conditions and operating conditions

• Check 4: Evaluate azimuth and tilt together with interconnection constraints

• Check 5: Incorporate curtailment and grid acceptance conditions early

• Check 6: Look not only at annual energy but also at hourly behavior

• Check 7: Don’t leave discrepancies between design values and site conditions until the end

• Summary

What to finalize first in a grid-connected design

When proceeding with a grid-connected design in PVSyst, a common practical pattern is to run generation simulations first and only later discover discrepancies with interconnection conditions or site constraints. Repeating this leads to more rework of simulation results and can cause the basis for design decisions to drift. In projects with many stakeholders, every time assumptions change midstream, the communication effort increases and reaching agreement on final capacity and configuration is delayed.

For grid-connected designs, it’s not enough to simply look for configurations that generate the most energy. You need to include from the start perspectives such as what constraints will be imposed at the point of interconnection, how much the AC side can accept, and whether the assumed operating modes are realistic. While PVSyst is strong at comparing generation and losses, if the input assumptions are vague, it can make that vagueness look deceptively precise.

That is why practical users who are proficient with PVSyst focus less on the software’s operation itself and more on what to confirm first and at what level of granularity to model each assumption. This article organizes and explains seven checks that are easy to overlook in PVSyst when advancing a grid-connected design. These viewpoints help avoid judging by generation size alone and guide you to bring designs closer to detailed design from the early stages.

Check 1: Align interconnection conditions and design assumptions up front

The first thing to confirm is whether the interconnection conditions assumed for the project and the design assumptions entered into PVSyst match. If they don’t match, no matter how carefully you refine losses or layouts later, the final conclusion can change. For example, if you increase DC-side capacity without considering the AC-side acceptance limit, the apparent annual generation may look good but the system may be constrained in actual operation.

In practice, designs sometimes start while the concept of the interconnection point, transmission assumptions, the ratio of exported to self-consumed power, and assumed operating hours are still ambiguous. Running PVSyst under such ambiguous assumptions often leads to “this configuration is impractical under those assumptions” later, requiring rework of comparison tables and presentation materials. Therefore, it’s important at the outset to document in writing what assumptions the design is based on and ensure they match the PVSyst settings.

It’s also important that stakeholders are not using the same words with different meanings. Even a mix-up over whether “capacity” refers to the DC-side total or the AC-side rating can derail discussions. PVSyst numbers may look tidy, but if stakeholder understandings diverge, the grid-connected design is on shaky ground. First organize the interconnection conditions and clarify which PVSyst settings they correspond to before running simulations.

Even more important is to make design assumptions traceable rather than fixed permanently. Interconnection-related conditions may be updated to more realistic values as the project progresses. If you keep track of which PVSyst settings were changed each time and how much the results changed, it becomes easier to explain later. Deciding how to manage assumptions in the early design stages leads to more stable design quality.

Check 2: Don’t determine equipment capacity based solely on energy production

When comparing design options in PVSyst, proposals with higher annual generation naturally look attractive. However, in a grid-connected design it’s risky to determine system capacity solely by generation. While increasing DC-side capacity tends to boost apparent generation, piling on capacity without checking the AC-side receptacle and time-of-day behavior can make the system vulnerable to curtailment and conversion losses.

What matters here is how to think about the balance between the DC and AC sides. You want to extract as much capability from the generation equipment as possible, but you also must consider what the grid can accept and the stability of operation. PVSyst makes it easy to compare multiple capacity patterns, so it’s tempting to pick the highest-performing numeric option, but in practice a proposal that can’t be used is meaningless. Capacity should be chosen from the perspective of whether it can be operated reproducibly within interconnection constraints, not simply to maximize generation.

When determining capacity, it’s also essential to look at average usage throughout the year, not just during favorable weather. If performance is only good at peak times and the configuration is heavily weighted toward high-output daytime periods, it will be more susceptible to interconnection constraints and curtailment. As a result, operational results may fall short of design expectations. When reviewing PVSyst results, check not only annual totals but also peak behavior and clipping.

Capacity settings also affect maintainability and flexibility for future operational changes. Even if a configuration works under current assumptions, ease of adaptation when operating conditions or load-side circumstances change can greatly affect usability. Rather than rushing to conclusions based on generation alone in the early design stage, compare multiple options with different capacity ratios and confirm which is most stable given the interconnection assumptions. This is a basic principle for using PVSyst practically.

Check 3: Don’t set losses roughly—align them with wiring conditions and operating conditions

PVSyst contains many input items for losses, and it’s tempting to enter representative values for simplicity at first. Some simplification is necessary in initial studies, but for grid-connected designs, keeping loss settings coarse can easily lead to mistaken judgments. Especially in projects where AC-side conditions matter, lumping DC wiring loss, AC wiring loss, temperature effects, and equipment conversion efficiency decline into a single number hides where improvement is possible.

A common practical mistake is carrying initial loss settings through to the later stages. Even when site conditions become clearer and cabling distances or installation methods are specified, PVSyst models often remain at their initial provisional values. That makes the design look progressed while evaluation accuracy hasn’t actually improved. In grid-connected contexts, how you set AC-side losses and conversion conditions can change the apparent send-out capability, so late corrections tend to be large.

To align loss settings with practical conditions, first avoid treating losses as a single lump. Separating which losses arise from wiring, which from temperature, and which from conversion processes changes how you read PVSyst results. Instead of just saying generation dropped by a certain percentage, you can see which conditions to improve to reduce specific losses.

Also, setting losses conservatively across the board is not always appropriate. Excessive uniform loss margins can mask differences between design options and blunt decision sensitivity. Conversely, underestimating losses creates unjustifiable expectations. Because PVSyst faithfully reflects the entered assumptions, the work of bringing loss settings closer to actual site and operating conditions determines design quality. In grid-connected projects, the accuracy of loss estimation is foundational to design decisions.

Check 4: Evaluate azimuth and tilt together with interconnection constraints

In solar design, optimizing azimuth and tilt is often discussed purely from the perspective of improving generation. PVSyst also makes it easy to compare angle changes, so naturally you want to find the condition that yields the most generation. However, for grid-connected designs, adopting the angle that simply maximizes annual accumulation can be premature. What’s important is what the output curve looks like at different times of day, and you must consider compatibility with interconnection constraints.

For example, a certain tilt may yield a slightly higher annual generation but concentrate output in a particular time window. If that time window is prone to grid constraints, the theoretical advantage in generation is hard to realize in practice. Conversely, a configuration that’s slightly inferior in annual generation but produces gentler, easier-to-handle output peaks may be more usable. In PVSyst, evaluate not only annual values but also daily and seasonal variations.

Azimuth and tilt also relate to shading and temperature conditions. If a layout is impractical on site, it may work on paper but be disadvantageous in actual operation. In sites with strict spatial constraints, the optimal angle may not be adoptable. In such cases, what matters is how you evaluate the gap from the ideal. Compare multiple options in PVSyst and judge how large a difference is acceptable in favor of constructability and interconnection stability.

Moreover, angle selection ties into overall accountability for the design. Explaining angle choice solely by generation can give the impression that interconnection considerations were overlooked. Being able to explain selection with respect to output characteristics, operational stability, and reduced risk of curtailment increases design credibility. PVSyst is both a tool for optimization and for visualizing design decisions, so angle settings should be read together with interconnection constraints.

Check 5: Incorporate curtailment and grid acceptance conditions early

A common oversight in grid-connected designs is considering curtailment and grid acceptance conditions only afterward. One approach is to first assess ideal generation potential in PVSyst and then consider constraints, but in practice this often causes rework. Especially for projects where AC-side acceptance conditions determine design assumptions, initial proposals that ignore constraints become poor bases for comparison.

When considering the impact of curtailment, the important perspective is not a binary “curtailment or not” but when and how much the system might be affected. Differences that look small on an annual basis can matter greatly if they are concentrated in the time window when generation peaks occur; that may change capacity or tilt decisions. When reading PVSyst results, look at annual totals together with peak margins and output imbalances to avoid biased design decisions.

Grid acceptance conditions are not just about upper limits. In practice, the assumptions at the planning stage and the stability required in operation are not always the same. Therefore, when evaluating design options, check not only under best-case conditions but also whether a proposal remains viable when subject to constraints. PVSyst’s comparison capabilities are well suited for evaluating multiple scenarios. Rather than presenting a single idealized figure, prepare options that can be justified even under constrained conditions.

Considering curtailment and acceptance conditions also helps internal and external coordination. Presenting only high-generation options can erode confidence later if revisions due to constraints are required. Showing constraint-inclusive evaluations from the start yields realistic, convincing proposals even if the numbers are less flashy. In grid-connected designs, producing explainable, operationally valid figures is more important than presenting the highest-looking numbers.

Check 6: Look not only at annual energy but also at hourly behavior

When reviewing PVSyst results, many practitioners first look at annual generation. While this is an important metric, in grid-connected designs relying on it alone can lead to mistakes because many interconnection issues manifest not in annual totals but at certain seasons and times of day. In other words, without inspecting time-of-day behavior, you cannot see the true usability of a design.

For example, two options with identical annual generation can differ in how quickly output ramps up, the shape of daytime peaks, and afternoon decline. These differences directly affect compatibility with the grid and susceptibility to curtailment. In practice, use PVSyst to check monthly trends, daytime output distributions, and how peak output appears to determine which option is easier to manage. Annual numbers alone will obscure such differences.

Examining hourly behavior also helps understand the causes of losses. If an option underperforms in summer midday compared to expectations, it may be due to temperature effects, conversion efficiency, or configuration bias. Reading PVSyst values along the time axis rather than accepting them as standalone results reveals what to improve next. This increases the accuracy of design comparisons.

Understanding time-of-day behavior also makes stakeholder explanations easier. If the conversation cannot be conveyed by “annual generation increased by X%,” showing when the differences occur clarifies the design intent. In grid-connected projects, explaining why numbers are as they are is as important as the numbers themselves. PVSyst results become actionable for design decisions only when you examine behavior across time, not just annual totals.

Check 7: Don’t leave discrepancies between design values and site conditions until the end

As a PVSyst design progresses, on-screen numbers and comparison tables can make the design feel finalized. What you must watch until the end, however, is discrepancies between design values and actual site conditions. Conditions that could be provisional early on must be updated in the model as site information becomes available. Failing to do so can yield a well-presented design that does not hold up in the field.

Common places where mismatches occur are how installation space is used, shading conditions, cabling distances, impractical equipment layouts, and maintenance access routes. These tend to be abstracted in early simulations but become increasingly significant as you approach final decisions. Even if PVSyst numbers looked favorable, their advantage can vanish once site conditions are reflected. Therefore, the closer you narrow down design options, the more rigorously you must reconcile them with site conditions.

Discrepancies between design values and site conditions also affect not just construction but post‑commissioning evaluation. Large gaps between assumptions and actual performance complicate cause analysis and may call the original design assumptions into question. This affects not only energy figures but the credibility of the entire design process. PVSyst should be used to produce decision materials that are close to reality, not just attractive numbers.

Thus, in the final design stage it is essential to cross-check PVSyst assumptions against verified site conditions one by one. Review whether any conditions omitted from the model remain, whether initial provisional assumptions persist, and whether any numbers cannot be explained under the interconnection premise. This mundane work is a key step that raises final design quality. The more a project depends on grid connection, the more the final consistency check determines overall completeness.

Summary

When advancing a grid-connected design in PVSyst, what matters more than simply running generation simulations is what assumptions you align beforehand and from what perspectives you interpret results. By organizing interconnection conditions early, not deciding capacity based solely on generation, bringing loss settings closer to site conditions, and evaluating angles with output characteristics in mind, the quality of design decisions changes dramatically. Furthermore, by checking curtailment and grid acceptance, examining time-of-day behavior, and reconciling site conditions, PVSyst results become not just estimates but practical decision materials.

For practitioners, the goal is not to find the single best-looking number but to produce reproducible, explainable proposals under the interconnection premise. PVSyst is a powerful tool for that purpose, but if input assumptions are vague, the outputs will also remain vague. Reviewing the seven checks introduced here at each design milestone is an efficient way to reduce rework and prevent misalignment among stakeholders.

Also, as you increase the accuracy of desk-based design, the importance of on-site position and coordinate verification grows. To connect design values and site conditions smoothly, it helps greatly to have a way to quickly confirm positions on site and move decisions forward. In such cases, using iPhone-mounted GNSS high-precision positioning devices like LRTK can improve the speed and accuracy of site verification. For practitioners who want to validate PVSyst-refined designs on site and minimize gaps between design and construction, having such on-site verification methods ultimately raises overall design quality.