How OwlWatt Calculates Your System's Expected Production

When OwlWatt says your system should have produced 1,240 kWh last month, that number is not an estimate pulled from your installer's sales pitch. It comes from a published, publicly auditable model — the same model the U.S. solar industry uses to design and price systems. This page documents exactly how that number is produced, what inputs go into it, and why it holds up when an installer wants to push back.

The short answer: pvlib running NREL's PVWatts model

OwlWatt's expected-production calculation uses pvlib — the open-source Python library — to run the same PVWatts algorithms that NREL publishes at pvwatts.nrel.gov. The inputs are your system's specific parameters: DC nameplate capacity, tilt, azimuth, location, and installation date. The output is an hourly expected AC production curve that accumulates into daily, monthly, and annual totals.

Every report OwlWatt generates records the pvlib version used, the complete parameter set, and the date window of the analysis. A report produced today can be reproduced exactly from those recorded inputs — there is no black box.

Who is NREL?

NREL — the National Renewable Energy Laboratory — is a U.S. Department of Energy federal laboratory headquartered in Golden, Colorado. Established in 1977, it is the primary U.S. government research institution for renewable energy and energy efficiency. NREL develops the scientific models, datasets, and standards that the solar industry runs on.

Critically: NREL has no commercial stake in any solar installation, equipment vendor, or monitoring company. It is a neutral scientific authority. When OwlWatt's calculation methodology cites NREL, that citation carries the same scientific and institutional credibility as citing the USDA for food safety data or the CDC for clinical evidence — it is the federal expert, not a party with a position to defend.

NREL also publishes the National Solar Radiation Database (NSRDB), the historical irradiance data underlying much of U.S. solar energy modeling.

What is PVWatts?

PVWatts is NREL's free, publicly available solar production estimator, available at pvwatts.nrel.gov. You enter a location, system size, tilt, and azimuth, and PVWatts returns a monthly and annual production estimate. It has been the industry-standard sizing tool for over a decade.

Who uses PVWatts?

• Solar installers — to design system sizes and produce the production estimates they show customers.
• Solar lenders — to underwrite solar loans and leases, verifying that the system being financed can produce the promised output.
• Utilities and grid operators — to model distributed generation capacity and plan interconnection.
• State regulators — to evaluate incentive program eligibility and SREC valuations.
• Courts and arbitrators — as a reference for production disputes, because it is the industry's own standard.

This ubiquity is the point. OwlWatt chose PVWatts not because it is the only production model, but because it is the model the entire industry already accepts as authoritative. An installer cannot simultaneously use PVWatts to project your system's production at sale and then reject it as a measurement standard when you file a shortfall claim.

What is pvlib?

pvlib is an open-source Python library that implements the PVWatts algorithms (along with dozens of other solar modeling tools). It is maintained by a community of researchers and engineers, with significant contributions from Sandia National Laboratories, NREL, and academic institutions. The source code is public, peer-reviewed, and used in published research.

OwlWatt runs pvlib in its cloud infrastructure to compute expected production for each customer's system. Every computation records the pvlib version used, so any report can be exactly reproduced from the same inputs and the same code version. The pvlib library also implements the Ineichen clear-sky model and the Faiman cell temperature model used in OwlWatt's pipeline — both well-established in solar science literature.

The parameters OwlWatt uses — and what they mean

PVWatts is only as accurate as the parameters you give it. Here is what OwlWatt records for your system, why each parameter matters, and how we obtain it.

The calculation pipeline, step by step

For each hour of each day in the report window, OwlWatt runs the following sequence using pvlib:

Integrated over a day, the hourly AC values sum to expected kWh for that day. Integrated over the report window, they produce the total expected kWh that OwlWatt compares against your measured production.

Weather adjustment

The clear-sky model produces the maximum possible expected production for a cloudless day. Real days have clouds. OwlWatt adjusts the expected production curve using measured ground-level irradiance data when available — scaling the clear-sky irradiance by the ratio of actual measured irradiance to the clear-sky ceiling. This preserves the correct daily shape (sunrise to sunset) while rescaling the magnitude to reflect actual weather conditions.

When measured irradiance data is not available for a specific day, the report falls back to the clear-sky estimate and tags that day accordingly. A full methodology description including the weather-adjustment approach is documented at owlwatt.com/methodology.

Why disputing OwlWatt means disputing PVWatts

Here is the structural argument that makes OwlWatt's calculation defensible:

Your installer almost certainly used PVWatts — either directly via pvwatts.nrel.gov, or through a design tool like Helioscope or Aurora that runs PVWatts under the hood — to produce the production estimate in your sales proposal. That estimate was the basis for the system size they sold you, the financial projections they showed you, and very likely the production guarantee number in your contract.

When OwlWatt runs PVWatts with your specific system parameters and finds that your actual production fell short of what the model predicts, the installer's methodological options are narrow:

• Contest the input parameters — dispute that OwlWatt has the correct tilt, azimuth, or system size. This is addressable: OwlWatt's parameters come from your system documentation and onboarding data.
• Argue about shading or site factors — claim that shading from trees, neighboring buildings, or other obstructions accounts for the gap. This is a factual dispute about your specific installation, not a methodological one.
• Accept the calculation — the model is correct and the system underperformed.

What an installer cannot credibly do is reject the PVWatts methodology itself. Doing so would invalidate the very tool they used to size your system and justify the price they charged you.

Documentation as evidence — what homeowners should know

OwlWatt's reports are designed to be evidence documents: structured, dated, reproducible, and methodologically transparent. When a production dispute escalates beyond an informal exchange with your installer, the report is what you hand to a licensing board, a consumer protection agency, or an attorney.

That said, here is what OwlWatt's documentation covers:

• Measured production — the actual kWh your Enphase system recorded over the report period, drawn directly from your inverter data.
• Expected production — the PVWatts model output for your specific system parameters and date window.
• Weather-adjusted comparison — expected production scaled to actual measured irradiance, removing weather as a confounding variable.
• Shortfall calculation — the kWh gap, the percentage gap, and the dollar value at your applicable electricity rate.
• Methodology statement — the pvlib version, the model parameters, and the data sources, so the calculation is fully auditable.

A consumer protection attorney reviewing a production dispute needs exactly this: a documented baseline, a documented measurement, and a transparent calculation connecting the two. OwlWatt's report provides that documentation; the attorney applies the legal analysis to it.

For the full technical methodology, including the complete parameter set, see OwlWatt's methodology page.

What OwlWatt does not model

Transparency about model limits is part of the methodology. A few things OwlWatt does not currently account for automatically:

• Shading from trees or structures — complex 3D shading is not modeled. Shading shows up in the measured-vs-expected gap over time. If your installer ran a Helioscope or Aurora shading analysis at design time, those site-specific losses can be incorporated.
• Snow cover — reports flag days where production dropped sharply in conditions consistent with snow accumulation. These days are excluded from shortfall calculations by default.
• Extreme soiling events — the 14% system losses derate covers normal soiling, not extraordinary dust or pollen seasons. Significant soiling beyond the baseline can be annotated manually.
• Per-panel attribution on string inverters — Enphase microinverter systems give per-panel data. String inverter systems without per-panel reporting expose only aggregate output.

OwlWatt currently supports Enphase systems. The methodology documentation will be updated as additional inverter integrations are added.

Related guides

• Solar Expected vs. Actual Production Explained — what normal derating looks like and how to spot a real fault.
• What's a Solar Production Guarantee Report and Why Does It Matter? — the four contract clauses and what a claim-ready report contains.
• Solar Panel Degradation Over Time — the 0.5%/year assumption, when it breaks, and how to verify your panels are aging on schedule.
• OwlWatt Methodology — the complete technical reference including data sources, shortfall formula, and versioning policy.
• How OwlWatt works — the collector, monitoring, and report workflow end to end.