Solar Generation Guarantees: Weather, Availability and Meter Boundaries

A solar generation guarantee is only useful when the owner can reproduce the calculation and identify who controls each loss. An annual MWh promise without a weather basis, meter boundary, availability rule and missing-data procedure can hide more uncertainty than it transfers. Before comparing headline percentages, ask every bidder to return the same measurement and responsibility schedule.

This guide addresses a hypothetical overseas investor procuring rooftop PV across leased factory assets in Vietnam. The PV investor, roof owner and factory tenant may be different parties with separate meters and operating rights. No project, supplier offer, tariff, yield or contractual remedy is asserted here. The examples are original arithmetic demonstrations, not a bankable energy study, legal advice or a QuangAnhcons generation guarantee.

1. Separate the four promises before comparing bids

Procurement teams often receive several promises under the heading “performance.” They should not place them in one spreadsheet column. A product warranty concerns specified equipment and its warranty conditions. An equipment availability commitment concerns defined operating states and eligible time. An energy commitment compares measured energy with an agreed reference. An electricity-cost saving depends additionally on consumption timing, tariffs, settlement and commercial arrangements.

A module warranty does not promise the AC energy delivered to a tenant meter. An inverter availability percentage does not account automatically for a transformer outage. A long-term annual yield estimate is not the same as a weather-adjusted assessment after a cloudy year. Request the underlying obligation, responsible entity, measurement method and exclusions for each promise; leave unresolved fields visibly open rather than treating the strongest marketing phrase as the binding scope.

2. Draw the investor, roof-owner and tenant boundaries

Consider a leased roof where an investor owns the PV plant, a landlord controls roof access and a tenant controls factory production. The same low-energy month could result from weak irradiation, an inverter fault, a factory shutdown or a landlord restriction on maintenance. Those events need different evidence and may involve different contracts. A single annual total cannot allocate responsibility reliably.

Create a meter and interface register before negotiating the guarantee. Identify inverter counters, the PV AC delivery meter, auxiliary consumption, transformer losses where relevant, the tenant import/export meter and any settlement meter. Record each meter’s identifier, ratio, direction, units, time basis, data owner and read-access permission. Distinguish physical delivery from invoice settlement; never subtract one party’s meter total from another without reconciling intervals and boundaries.

The electrical designer should show those boundaries on the single-line diagram. The commercial team should then map each boundary to an agreement: roof access, energy sale where applicable, installation, operation, maintenance and data provision. QuangAnhcons’ factory electrical interface register provides a related method for making responsibility gaps visible. It does not replace transaction-specific legal or utility review.

3. Keep the original forecast and the actual-weather comparison separate

A reference-year forecast answers what a model predicts under its chosen weather dataset and stated configuration. A later actual-weather calculation asks what that same defined system should have produced under the observed assessment-period weather. Both can be valuable, but they answer different questions. A bid should disclose the dataset, coordinates, model version, timestep, geometry and loss assumptions behind its initial forecast.

For the later comparison, agree which inputs remain frozen and which are updated from measurements. Geometry, installed capacity, equipment characteristics and baseline loss assumptions should not be silently changed to fit the result. Corrections, equipment replacements and plant modifications need a documented approval trail. Retain the original model, input files and output series so another appointed reviewer can reproduce the assessment.

The public scope of IEC TS 61724-3:2016, edition 1.0, published 19 July 2016, concerns energy evaluation against expected production under actual weather and distinguishes operating periods from unavailability. The catalogue includes the February 2018 corrigendum. This is a Technical Specification, not a ready-made commercial guarantee. Only its public scope is used here; no licensed procedure, acceptance threshold or conformity assessment is reproduced.

4. Recalculate a weather-risk example in consistent units

Assume, only for this example, that the agreed reference-year model predicts 1,000 MWh, the model using the assessment period’s actual weather predicts 900 MWh, and the delivery meter records 864 MWh. All three figures cover the same period and AC boundary. No plant capacity, location-specific resource value or actual project result is implied.

The 96.0% value is not labelled a standard performance ratio, availability or contractual entitlement. The remaining 36 MWh may include outages, curtailment, model error, meter effects or operating losses. Attribution requires interval evidence. Nor does the calculation prove that 100 MWh is legally excused weather risk: allocation follows the actual agreement, not this illustrative subtraction.

One MWh equals 1,000 kWh, so 864 MWh is 864,000 kWh. Keep that conversion explicit when invoices use kWh and engineering reports use MWh. Do not compare an AC meter total with a DC-side forecast without a documented conversion model and loss boundary.

5. Availability and energy shortfall need two records

Suppose a separate operating log identifies 1,000 eligible hours and 980 available hours. Simple time availability is 980 / 1,000 = 98.0%. That percentage alone says nothing about how much irradiation occurred during the 20 unavailable hours. Twenty hours around high solar production can matter much more to energy than twenty low-production hours. Night-time inclusion, partial outages and plant weighting therefore require explicit definitions.

Return to the 900 MWh actual-weather model for an attribution illustration. Assume valid interval logs allocate 870 MWh of modelled energy to available periods and 30 MWh to unavailable periods. Assume all 864 MWh measured energy belongs to the available periods. The available-period simple ratio is 864 / 870 = 99.31%, while the total-period ratio remains 96.0%. The 36 MWh difference decomposes into 30 MWh modelled during unavailability and 6 MWh during available periods.

This decomposition is only coherent if the interval classification, model and meter boundary are consistent and the allocations sum to the original total. It does not authorise removing downtime from an energy obligation, and the two ratios must not be advertised interchangeably. Report both the operational energy comparison and the outage record. If a guarantee excludes an outage category, show its original energy effect and the contractual basis for the exclusion rather than making the event disappear.

6. Freeze the data-quality procedure before the assessment

A guarantee cannot be independently verified if only a monthly PDF is available. Require exportable interval data, meter registers, event logs, sensor maintenance records, calibration information and model inputs. Specify retention, access rights and a handover format that does not depend on a single vendor portal remaining available. Protect credentials and commercially sensitive tenant information through the agreed access arrangements.

IEC 61724-1:2021, edition 2.0, published 21 July 2021, addresses PV performance-monitoring terminology, equipment, methods and monitoring-system classes. Its public catalogue scope supports the need to define the monitoring basis; it does not establish a contractual yield or prove that a particular sensor installation complies. The appointed technical parties need the applicable full documents for their design and assessment work.

Agree how timestamps, duplicated intervals, communications outages, sensor cleaning, shading changes and implausible values are handled. A missing reading is not automatically zero energy or an exempt interval. Define a hierarchy of replacement evidence and a review trigger when coverage is inadequate. Keep the untouched raw series, the cleaned series and a reason-coded change log. Do not fill gaps using an unexplained average chosen after seeing whether the guarantee passes.

7. Make uncertainty visible without inventing confidence

Expected energy is modelled, not a perfect measurement of what must happen. Weather sensors, transposition, temperature representation, loss assumptions and metering can affect the comparison. Ask the independent technical reviewer to identify material uncertainties and the contract team to agree how those uncertainties affect acceptance. Do not import a generic uncertainty percentage from another roof.

As a sensitivity exercise only, vary the 900 MWh expected value by plus or minus 18 MWh, leaving measured energy at 864 MWh. At 882 MWh expected, the simple ratio is 97.96%; at 918 MWh it is 94.12%. The nominal result remains 96.0%. This range is not a statistical confidence interval or a tolerance prescribed by IEC. It demonstrates why the origin and treatment of uncertain inputs can matter when a contractual decision lies close to a threshold.

Require bidders to provide their own justified inputs and sensitivity cases, then compare like with like. A fixed energy promise and a weather-adjusted promise can allocate very different risks. Choosing between them is a commercial decision supported by engineering evidence, not a contest to select the largest percentage in a proposal.

8. Return a common guarantee schedule with every bid

Include a worked report template in the RFQ. Have the bidder populate it with clearly hypothetical numbers before award. An owner should be able to follow raw energy through quality checks, valid intervals, exclusions and the final comparison without requesting an undocumented spreadsheet password. Technical review should identify unresolved fields; it should not silently supply favourable assumptions on behalf of a bidder.

9. Operational safety must not become a guarantee exception

A low-energy alarm does not authorise roof access, live electrical work, controller changes or protection bypasses. The operator must retain switching and isolation authority. Investigations should begin with authorised remote data checks; intrusive testing follows approved procedures, competent personnel, isolation verification, roof-access controls and the applicable equipment manuals. Preserve safe operation even when commercial reporting deadlines are approaching.

Allocate response responsibilities between the PV operator, factory electrical team, landlord, equipment supplier and appointed specialists. Document who can request an outage, who can approve access and who verifies restoration. A tenant production shutdown or utility instruction requires a timestamped event record and an identified decision maker. It must not be recategorised casually as equipment failure or force majeure by an automated dashboard.

10. What to send for a scoped interface review

Prepare the proposed guarantee wording, SLD, meter register, model input list, interval-data sample, operating calendar and responsibility matrix. Remove personal information and confidential customer details before initial sharing; agree a suitable confidentiality channel for detailed records. Describe separately who owns the roof, PV equipment, electrical connection and energy account.

For construction boundaries, review the Solar Electrical BoP integration scope. For broader site inputs, see the industrial rooftop solar service scope. These service descriptions do not promise generation, payback, statutory approval or a full EPC package without an agreed appointment. QuangAnhcons can discuss the defined electrical interfaces; energy modelling, independent performance assessment and legal obligations must remain with the appropriately appointed parties.

Frequently asked questions

Does a cloudy year automatically mean the contractor failed?

No. Compare the agreed obligation with valid measured data and its defined weather basis. A shortfall from a reference-year forecast alone does not establish technical cause or contractual liability.

Can 98% availability prove 98% of expected annual energy?

No. Time and energy are different quantities. The energy effect depends on when the outage occurred, partial plant behaviour and the assessment method. Keep outage and energy records linked but separate.

Does an IEC reference make the guarantee enforceable?

No. A technical reference has a defined scope; it does not by itself settle contract wording, statutory duties, responsibility, remedies or dispute procedures. Obtain project-specific technical and legal review.

No quick estimate yet. You can still submit a project quotation request.