5 checks in the PVSyst manual to prevent capacity overruns

Table of Contents

• Background behind capacity exceedance occurring in PVSyst

• Check item 1: Verify the consistency between module capacity and PCS capacity

• Check item 2: Confirm the number of strings and the maximum number of input circuits

• Checkpoint 3: Review the DC/AC ratio to align with project conditions

• Checkpoint 4: Do not overlook voltage rise caused by temperature conditions

• Checkpoint 5: Verify clipping of simulation results

• Practical steps to prevent capacity overrun

• Tips for making it easier to explain proposal materials and internal reviews

• Summary

Background of Capacity Overruns in PVSyst

When using PVSyst to assess the energy production and losses of a photovoltaic installation, you may notice warnings about capacity or anomalous loss values. In particular, when assembling a project for the first time or hurriedly creating a simulation based on existing design figures, you can end up running calculations with inconsistencies in module capacity, PCS capacity, string configuration, number of input circuits, temperature conditions, and so on.

Here, capacity exceedance does not simply mean that the installed capacity is large. It refers to situations where the DC capacity on the photovoltaic module side is excessive relative to the PCS's acceptance capability, the string voltage exceeds the allowable range, or the input current or the number of connections per MPPT exceeds actual equipment specifications. Even if calculations proceed in a simulation, the configuration may be one that cannot be adopted in real designs or proposals.

The purpose of consulting the PVSyst manual is not merely to follow the on-screen operation steps. It is important to understand which conditions each configuration item is linked to, which design risks the warnings indicate, and which numbers on the results screen you should check to assess the impact of overcapacity.

In photovoltaic system design, there are situations where you want to increase module capacity to boost power generation. Even when land area is limited, choosing high‑output modules can increase installed capacity. Also, designing the DC side slightly larger relative to the PCS can raise generation in the early morning and late afternoon or under low irradiance. However, excessive capacity sizing leads to increased clipping losses, exceeding equipment specifications, difficulty in explaining the design, and rework during construction.

In particular, if you only look at estimates of power generation, issues of capacity exceedance tend to be overlooked. If you conclude there is no problem simply because the annual energy production appears high, inconsistencies with equipment selection, grid connection, or construction conditions may emerge later. In analyses using PVSyst, you need to check not only the magnitude of the results but also whether those results arise from assumptions that are safe and explainable.

To prevent capacity overruns, start by checking the capacity balance between the modules and the PCS, then review—in order—the string configuration, the DC/AC ratio, the temperature conditions, and the losses shown in the simulation results; this sequence makes the process easier to organize. From here, I will explain, in order, the five points you should check in practice.

Checkpoint 1: Verify consistency between module capacity and PCS capacity

The first thing to check is the relationship between module capacity and PCS capacity. In solar power systems, the DC-side capacity—the sum of the modules' nominal outputs—and the AC-side capacity, which is the PCS's rated output, do not necessarily have to be the same. Rather, it is common practice to design the DC-side capacity larger than the AC-side capacity.

However, simply increasing the DC side is not always better. To prevent capacity exceedance in PVSyst, first verify that the number of modules set in the project, the nominal output per module, the total array capacity, and the rated capacity of the PCS align with the actual design policy.

For example, if you increase the number of modules but forget to update the number of PCS units, only the DC side will grow, resulting in a configuration where the PCS side appears undersized. Conversely, if you change the PCS capacity but do not revisit the string configuration, the capacity balance shown on screen may diverge from the actual equipment specifications.

In PVSyst, you create a configuration in the system settings by combining modules, inverters, the number of strings, and the number of parallel strings. What’s important is not just the simple total capacity, but being aware of which strings are assumed to be connected to which PCS. Even if the total capacity appears to match at first glance, if the load is concentrated on specific inputs or MPPTs, the configuration may actually be inappropriate.

Also, in project briefing materials it is easy for equipment capacity to be represented inconsistently as DC capacity or AC capacity. In studies of power generation projects, the DC-side equipment size may be emphasized, while from the perspective of grid interconnection and PCS output the AC-side capacity becomes important. If the input values in PVSyst and the notations in internal documents are misaligned, it can be easy to overlook capacity exceedances.

When checking capacity consistency, it is important to compare the total module capacity, total PCS capacity, number of PCS units, number of connection strings per unit, and the capacity per input under the same assumptions. In particular, when creating a new project by copying data from past projects, only the module model and PCS model may have been changed, leaving the number of strings and the number of units unchanged.

When reading the PVSyst manual, it's important not only to pay attention to where to enter values but also to adopt an approach of checking what capacity balance warnings and messages mean. If a warning is issued yet the predicted energy production appears high, the calculation may be based on assumptions that the design cannot justify.

Checkpoint 2: Verify the number of strings and the maximum number of input circuits

Next, what we want to check is the relationship between the number of strings and the PCS input circuitry. When talking about capacity exceedance, attention tends to focus on total capacity, but in practice the connection conditions at the string level are extremely important. A PCS has specifications such as the allowable DC input voltage range, maximum input current, number of MPPTs, allowable current per input, and the number of strings that can be connected.

When configuring the string layout in PVSyst, you decide the number of modules in series and the number in parallel. The number of modules in series affects the string voltage, while the number in parallel affects the current and the input capacity. Increasing the number of parallel strings too much just to raise module capacity may exceed the PCS's input current limit.

Also, it is necessary to confirm whether the number of strings matches the PCS input terminals and the specifications of the combiner box. Even if the number of strings can be freely set in a simulation, the actual equipment configuration limits the number of circuits that can be connected. Whether you add combiner boxes, distribute the inputs, or increase the number of PCS units will significantly change the equipment configuration.

Particular care should be taken not to be reassured by looking only at the total number of strings. Even if the total string count looks reasonable, an uneven distribution across MPPTs can cause certain inputs to become overloaded. In PVSyst settings, when handling multiple sub-arrays or multiple PCS, you need to carefully verify which configuration is assigned to which range.

String configuration is also affected by shading conditions, orientation, and tilt. Combining arrays with different orientations or tilts onto the same MPPT can increase losses due to differences in generation characteristics. It is important not only to avoid exceeding capacity, but also to verify whether the grouping of inputs is reasonable.

When referring to the PVSyst manual, make sure not to overlook the voltage, current, and number of inputs displayed on the string configuration screen. If warnings or colored indicators appear, they should be treated as design cautions even if the calculation does not stop.

In practice, the electrical design team, the construction team, and the estimating team may each be working from different documents. Therefore, checking early that the string configuration in PVSyst, the single-line wiring diagram, the equipment specifications, and the estimated quantities all match can reduce rework in later stages. It is important to treat capacity overrun not just as a simulation issue but as a matter of consistency across the entire set of design documents.

Checkpoint 3: Review the DC/AC ratio to match project conditions

The third point to check is the DC-to-AC ratio. The DC-to-AC ratio is the ratio of the module-side DC capacity to the PCS-side AC capacity. In solar power system design, making the DC capacity larger than the PCS capacity can sometimes increase annual energy production. This is because modules do not always generate at their rated output.

However, if the DC/AC ratio is too high, the PCS can reach its output limit during periods of strong solar irradiance, and part of the potentially generated power will be curtailed. This phenomenon is treated as clipping and appears as a loss in PVSyst results. A certain degree of clipping may be acceptable as a design decision, but if it is excessively large it may indicate capacity overrun.

The appropriate DC-to-AC ratio depends on the project's region, solar irradiance conditions, temperature, orientation, tilt, PCS specifications, power purchase conditions, grid constraints, and cost-effectiveness. Therefore, rather than judging solely by a simple general guideline, it is necessary to verify it according to the objectives of each project.

For example, in projects that prioritize generation during low-irradiance hours, there is rationale for designing the DC side somewhat larger. On the other hand, if daytime peak output frequently reaches the PCS limit and clipping losses are large, the added module capacity may not be fully utilized.

When comparing multiple cases in PVSyst, it becomes easier to judge if you create scenarios that gradually change the DC/AC ratio and compare annual energy production, clipping losses, installed capacity, number of PCS units, and projected revenue. Rather than simply choosing the case with the highest energy production, it is important to see how much the energy production increases for the added modules.

A common mistake when checking the DC/AC ratio is being unable to separate the effect of increasing module capacity from clipping losses. If energy production has increased but losses have also risen, you cannot judge whether the design is truly reasonable without looking at cost-effectiveness. On PVSyst’s results screen, you need to check not only the annual energy production but also the breakdown of losses.

Also, clearly stating the DC/AC ratio in the proposal materials makes it easier to explain the design intent. To demonstrate that the design is an intentional oversizing rather than a capacity overrun, you need to show how much loss will occur and whether there is still an advantage in annual energy generation and profitability. Conversely, if clipping is so large that you cannot make that explanation, the configuration should be reconsidered.

Checkpoint 4: Do not overlook voltage rise due to temperature conditions

The fourth point to check is the temperature conditions. The voltage of a photovoltaic module varies with temperature. In general, module voltage increases as ambient temperature decreases. Therefore, during cold winter conditions the string’s open-circuit voltage can become high, posing a risk of exceeding the PCS’s maximum input voltage.

When considering overcapacity, attention tends to focus on the number of modules and PCS capacity, but if the number of modules in series is too high, the voltage rise at low temperatures becomes a problem. PVSyst performs simulations based on weather data and temperature conditions, but for design verification it is necessary to separately consider whether the equipment specifications remain safe even under worst-case conditions.

Especially in cold regions and at high altitudes, underestimating minimum temperature conditions can be dangerous. Even if there are no problems under normal conditions, if the open-circuit voltage exceeds the PCS upper limit at low temperatures, it can affect equipment protection and increase the risk of failure. Even if the energy production results in PVSyst look favorable, if the voltage range has not been sufficiently checked, the design may not be acceptable.

When deciding the number of modules connected in series per string, verify the module open-circuit voltage, temperature coefficient, expected minimum temperature, and the PCS maximum input voltage in combination. It is also important to ensure that the operating maximum power point voltage falls within the PCS’s MPPT range. You need to confirm not only that it does not exceed the maximum input voltage, but also that it lies within the range where the PCS can efficiently track during normal operation.

The issue of capacity exceedance due to temperature conditions is something that can be easily overlooked if you only look at power generation. In particular, copying project settings from a previously warmer region and applying them to a cold-region project can result in an inappropriate number of modules in series. Even with the same combination of module and PCS, the allowable number of modules in series can vary depending on the installation area, so it is important to understand this.

When reviewing the PVSyst manual, it is useful in practice to know which screens set the temperature conditions and which results they affect. The selection of meteorological data, installation conditions, and the module temperature model relate not only to energy yield but also to verification of electrical validity.

To prevent exceeding capacity, evaluate safety not only by the size of the DC-side capacity but also from both voltage and current perspectives. Voltage tends to be the issue in the series direction and current in the parallel direction, so when you change the string configuration it is important to make a habit of always checking both.

Checkpoint 5: Verify clipping of simulation results

The fifth point to check is the clipping losses that appear in the simulation results. When reviewing results calculated with PVSyst, it is insufficient to only check the annual energy production and the PR. The effects of capacity oversizing can appear in the loss diagram and in sections related to output limiting.

Clipping is the phenomenon where the portion of DC power that modules can generate is lost when it exceeds the PCS's output limit and cannot be converted to AC. It can occur to some extent in designs with a high DC-to-AC ratio, but if the proportion is too large, the capacity setting may be excessive.

In PVSyst, by checking the breakdown of losses you can identify which factors are affecting energy production. Comparing temperature losses, wiring losses, mismatch losses, shading losses, and PCS-related losses makes it easier to determine to what extent problems caused by capacity oversizing are present.

What's important here is not to simply dismiss clipping losses as a bad thing. In oversized design, there is the idea of increasing output in the mornings, evenings, and on cloudy days at the expense of trimming part of the peak output. Therefore, a small amount of clipping can be reasonable in terms of annual energy yield and profitability.

The problem arises when clipping losses are large and the effect of the added module capacity is small. If you increase the number of modules but much is being clipped during peak hours, the increase in generated energy relative to the investment becomes small. Furthermore, it becomes difficult to explain the excess capacity, which can become a concern for internal approvals and when explaining the project to customers.

When checking PVSyst results, looking at monthly and time-of-day trends as well as the annual totals will deepen your understanding. Design decisions change depending on whether the output is frequently pinned at the upper limit during high summer irradiance or whether the issue occurs only in certain seasons. Output clipping may be acceptable if it is localized, but if it occurs for long periods it needs to be reassessed.

Also, when checking clipping losses, it becomes easier to make a decision by comparing options such as increasing PCS capacity, reducing the number of modules, adjusting azimuth or tilt, and revising the string configuration. Rather than simply reducing capacity, arranging the layout to flatten the power generation curve can sometimes reduce peak concentration.

If you don't understand how to read the results screens, you may end up preparing proposal documents while overlooking the effects of capacity overrun. When using the PVSyst manual, it's important to check not only the input screens but also the loss diagram, monthly results, and the meaning of the main indicators.

Practical approach to preventing capacity overruns

To prevent exceeding capacity, it is important not to immediately build detailed conditions in PVSyst, but to organize the design assumptions first and then input them. Confirm the module model, PCS model, installation region, assumed minimum temperature, azimuth, tilt, array layout, combiner boxes, number of PCS units, grid capacity, etc., and decide which values to reflect in PVSyst.

It is common in practice for PVSyst inputs to be prepared before the design documents have been finalized. In such cases, the number of modules and the PCS model/type may be changed later, causing the simulation conditions to diverge from the actual design. While this is acceptable for an initial estimate, when using the results for proposals or internal approvals you must always cross-check them against the latest design conditions.

Especially when multiple people are working, looking at only a PVSyst file may not make it clear at what point in time the design conditions apply. Including the module capacity, PCS capacity, DC/AC ratio, creation date, and the design option category in the file name or case name makes it easier to compare them later.

As a verification procedure to prevent capacity overruns, first check the total module capacity and the total PCS capacity. Next, confirm the number of modules in series and the number in parallel in each string, and verify that the voltage and current fall within the equipment specifications. After that, check the DC/AC ratio and clipping losses, and assess the balance between generation and losses. Reviewing in this order reduces the chance of major oversights.

Also, when a design change is made, it is necessary to review the overall capacity balance rather than looking only at the changed parts. For example, changing the module model will affect not only the output but also the open-circuit voltage, current, and temperature coefficient. Changing the PCS model will affect not only the rated capacity but also the input voltage range and the number of MPPTs. You must be aware that a single change can propagate to multiple verification items.

When using the PVSyst manual in your business operations, it's important not only to read the operating instructions but to incorporate them into your company's verification workflow. Decide what to check on which screen, who will make the final decision, and which documents to cross-check if a warning appears — doing so will reduce missed capacity exceedances.

Tips to make explanations easier in proposal documents and internal reviews

To prevent capacity overruns, it is not sufficient for only the simulation personnel to understand. The meaning of the numerical values needs to be organized and conveyed so that design, sales, estimating, construction, and client-side personnel can understand them on the same assumptions.

In proposal materials, it is important to clearly explain DC capacity, AC capacity, the DC/AC ratio, the number of PCS units, and the assumed losses. In particular, when the DC side is designed to be somewhat larger, it must be made clear that this is not a design mistake but a choice made with consideration of power generation and profitability.

However, just because it can be explained does not mean that excessive capacity settings are permissible. If clipping losses are large or if you are too close to the upper limits of the equipment specifications, a review is necessary from the standpoint of safety and maintainability. Good simulation results are not the same as a design being appropriate.

For internal review, rather than simply pasting the PVSyst result screens as-is, it's easier to convey your findings if you supplement them with written explanations of the points you checked. For example, organizing the relationship between module capacity and PCS capacity, the validity of the string configuration, voltage checks under temperature conditions, and the extent of clipping losses will make it easier for approvers to make a decision.

Also, when comparing multiple options, you need to explain not only the differences in power generation but also the differences in the risk of exceeding capacity. The option with the highest power generation is not necessarily the optimal one. Compare an option that increases PCS capacity, an option that reduces the number of modules, and an option that adjusts the DC/AC ratio, and evaluate them in terms of both cost-effectiveness and design risk.

When explaining to customers, simply listing technical terms can make it difficult to get your point across. The term "exceeding capacity" can give the impression of a dangerous design. Therefore, you need to explain separately whether the actual issue is that the equipment's allowable range is being exceeded, that some generation is being curtailed during peak times, or that it falls within the range intended by the design.

When creating internal documentation while referring to the PVSyst manual, standardizing screen names and indicator names makes later verification easier. If different staff use inconsistent expressions, judgments can diverge even when looking at the same numbers. Standardizing terms within the company—such as DC capacity, AC capacity, overloading rate, and clipping loss—is also a practical measure to prevent capacity exceedance.

Summary

To prevent capacity exceedance in PVSyst, you must not rely solely on the power output results; you need to carefully verify the consistency between the input conditions and equipment specifications. In particular, the following five points— the relationship between module capacity and PCS capacity, the number of strings and the limits of input circuits, the DC/AC ratio, voltage rise due to temperature conditions, and clipping losses—are important checks that are easy to overlook in practice.

Overcapacity can occur as a simple input error or as the result of attempting to increase power generation. Even when oversizing is an intentional design choice, if equipment specifications and losses cannot be explained it will cause problems during the proposal and installation stages. When using the PVSyst manual, it is important to understand not only how to operate the software but also how each setting connects to design decisions.

First, check the total module capacity and the total PCS capacity, then review the string configuration. After that, confirm whether the DC/AC ratio aligns with the project’s objectives, whether the voltage at low temperatures stays within the safe range, and whether the simulation results show excessive clipping. By making this sequence a habit, you can significantly reduce rework caused by capacity overages.

PVSyst is a convenient tool for calculating energy production, but it does not automatically verify that all entered conditions are correct. Designers must make a comprehensive judgment based on equipment specifications, site conditions, construction conditions, and profitability. By reading the manual and integrating into your company's workflow what to check on each screen, you can carry out more consistent design evaluations.

Preventing capacity overrun is not simply about clearing warnings. It means creating a system configuration that is safe, easy to explain, and acceptable in terms of profitability. By correctly interpreting PVSyst's input and output values and checking each of the five verification points, it becomes easier to make consistent decisions from initial study through proposal, internal approval, and pre-construction verification.