Quick answer
Energy production forecasting estimates monthly, annual or lifetime solar electricity output for a documented project configuration, resource basis, loss treatment and output boundary.
Answer: Solar energy production forecasting estimates a project’s monthly, annual or lifetime electricity output from documented resource, equipment, geometry and operating assumptions. A usable forecast identifies the output boundary and design revision, explains losses and uncertainty, and separates expected production from guaranteed performance. It supports customer and financial decisions, but representative weather cannot predict the exact sequence of a future year’s conditions.
Define the project deliverable
This page concerns the production estimate issued with a proposed solar project. Energy forecasting also covers short-term operating forecasts and their evaluation; energy modeling explains the underlying physical calculation chain.
Before running a model, identify DC nameplate capacity, inverter configuration, orientations, site obstructions and the weather dataset. State whether the result is inverter AC output, energy delivered at a meter or exported energy after site consumption. Storage and export limits need explicit treatment if they are within the requested boundary.
Choose inputs and method for the decision
A screening estimate uses fewer inputs than a detailed component simulation. More settings do not automatically improve accuracy: the geometry, resource and equipment data must be credible. Record source versions and dates, model version and assumptions that remain provisional.
A typical meteorological year represents a resource basis rather than a prediction of next year’s actual weather. An actual-year file can support performance investigation when measurements cover the same period. Keep these uses distinct. SAM’s results documentation explains its annual and lifetime outputs; modeled lifetime weather treatment does not establish a forecast of each future calendar year’s weather.
A checked annual screening calculation
Twenty-five modules rated 400 W give 10 kW DC nameplate capacity. For a deliberately simplified scenario, assume annual plane-of-array irradiation equivalent to 5.5 peak-sun-hours per day and a retained performance factor of 0.80:
10 kW × 5.5 h/day × 365 days × 0.80 = 16,060 kWh/year
Specific yield is 1,606 kWh/kW DC/year. Peak-sun-hours express irradiation normalized to reference irradiance, not literal hours of constant sunshine. These are hypothetical inputs, not a location benchmark. If the factor already includes a loss, do not subtract that loss again.
This annual scalar estimate cannot resolve interval clipping, time-dependent shading or tariff value. Detailed models need appropriate temporal inputs and component limits.
Explain the loss and uncertainty assumptions
Document shading geometry, temperature treatment, soiling, electrical losses, inverter limits, availability and applicable curtailment. Their values depend on the installation and model; no single loss table applies to every project. A DC/AC ratio alone does not establish a clipping percentage.
Separate expected losses from uncertainty about the weather and model inputs. PVsyst’s P50/P90 documentation describes a model requiring user-specified uncertainty inputs. P50 is a median exceedance outcome, while P90 is exceeded with modeled probability 90% for the stated horizon. Neither is a guaranteed minimum or automatic lender acceptance. Consult P50/P90 for interpretation.
Do not quietly reduce a result and call it conservative. Label the adjusted scenario, changed assumptions and reason so readers can compare like-for-like outputs.
What the issued report should contain
| Report element | Review question |
|---|---|
| Design/run identity | Which layout, equipment and model version produced this result? |
| Resource basis | Which dataset, period, coordinates and timestamp convention were used? |
| Monthly and annual output | Are units and the AC/DC or export boundary explicit? |
| Loss explanation | Which losses are modeled, combined or excluded? |
| Uncertainty | What horizon, method and provisional assumptions underpin the range? |
| Lifetime assumptions | How are degradation, replacements and outages treated? |
| Conditions and revisions | What site evidence remains unresolved, and what changes trigger a rerun? |
Use monthly production simulation when seasonal timing matters. Hand financial analysis a time series at the relevant billing boundary, not just an annual total.
Use the estimate without overpromising savings
Hypothetical example: a 15% difference on 14,000 kWh/year is 2,100 kWh. At an assumed constant value of $0.15 per kWh for every affected unit, the difference is $315/year. Export rates, self-consumption and time-dependent tariffs can change that value. Energy changes therefore do not translate automatically into the same percentage change in returns.
After installation, reconcile the as-built configuration and compare time-aligned measurements with appropriate actual-period weather. Comparing one unusual year directly against a typical-year estimate does not isolate model error.
Common questions
Does a typical-year estimate predict exact next-year production?
No. It provides a representative resource-based estimate with stated assumptions.
Should every forecast include P90?
Use an uncertainty deliverable appropriate to the decision and contractual requirements; do not imply that every customer or lender requires the same format.
Is annual energy enough to calculate savings?
Often it is insufficient. Billing interval, self-consumption, export and tariff conditions can matter.
When should a forecast be revised?
When material equipment, layout, site evidence or operating assumptions change, document the revision and rerun the relevant analysis.
Related Glossary Terms
About the Contributors
Co-Founder · SurgePV
Akash Hirpara is identified by SurgePV as a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; education, certifications, project totals, financial results, speaking engagements, and media appearances are not asserted without retained evidence.
Editorial contributor · SurgePV
Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.
