An energy savings performance contract lives or dies on measurement. When an energy service company (ESCO) guarantees that a retrofit will cut a facility's energy use, the guarantee is only as credible as the data used to prove it. That puts utility consumption records at the center of the business model, both for setting the baseline and for verifying savings year after year.
Proving savings against a baseline is its own discipline, covered in weather normalization, CUSUM and RETScreen for measurement and verification.
The stakes are not small. Lawrence Berkeley National Laboratory estimated total U.S. ESCO industry revenue at about $6 billion in 2018, with public and institutional customers such as governments, universities, and K-12 schools accounting for more than 90 percent of that revenue. The same research put the remaining market potential at $92 billion to $201 billion. Every one of those projects rests on a defensible energy baseline.
Why performance contracts depend on utility data
The guaranteed savings model has been a fixture of the industry since the U.S. Energy Policy Act of 1992 established energy savings performance contracts as a federal procurement mechanism. Under that model the ESCO is paid based on measured results, so the contract needs an agreed way to answer a simple question: how much energy would the building have used without the project, and how much did it actually use?
Answering that requires clean, continuous consumption history. A baseline built on a few manually keyed bills is fragile. A missing month, a misread PDF, or an estimated bill can shift the calculated savings enough to trigger a dispute over a guarantee payment.
The exposure is asymmetric. When savings fall short of the guarantee, the ESCO usually makes up the difference, so the company carries the downside of any weakness in the data. That is a strong reason to treat data collection as a controlled, repeatable process rather than a manual scramble at the end of each measurement year, when the people who set up the accounts may have moved on and the original logins no longer work.
Measurement and verification runs on consumption history
The International Performance Measurement and Verification Protocol (IPMVP), maintained by the Efficiency Valuation Organization, is the common reference for quantifying savings. It offers several options: Option A and Option B isolate specific measures with metering, Option C uses whole-facility utility-bill analysis, and Option D uses calibrated simulation.
Option C, the whole-facility approach, regresses utility-bill data against variables such as weather to model expected use and compare it to actual use. It is only as reliable as the meter and bill data feeding it. For an ESCO managing many contracts at once, keeping that data complete and current across a whole portfolio of buildings is a real operational burden.
What the M&V plan asks of your data
Before a contract is signed, the measurement and verification plan fixes how savings will be calculated for its whole life. Every line in that plan is a data commitment, and each one is easier to meet if the collection process is already running rather than assembled retroactively.
| What the plan specifies | What it requires from the data |
|---|---|
| Baseline period | A continuous consumption history covering the agreed period, usually at least 12 months, with no estimated or missing reads standing in for real ones |
| Measurement boundary | Every meter inside the boundary identified, including gas and water where they are in scope, not only the main electricity account |
| Independent variables | Weather and operational drivers aligned to the same billing periods as the consumption data |
| Reporting period | The same meters, the same units and the same period definitions as the baseline, for years after the project closes |
| Non routine adjustments | Enough account level detail to explain a change in occupancy, hours or equipment when the numbers move for reasons the project did not cause |
The recurring failure is subtle: the baseline is assembled carefully by the engineering team during development, and then the reporting period data is collected by whoever is available in year two, from different portals, in a different format. The comparison stops being like for like, and the dispute that follows is about data provenance rather than engineering.
A data checklist before the contract is signed
Worth settling while both parties are still negotiating rather than after the guarantee is live:
- Name every account and meter inside the measurement boundary, with account numbers and the utility that serves each one.
- Agree how many months of baseline history are required, and confirm that history actually exists before it is written into the contract.
- Decide how estimated reads and missing periods will be treated, in writing, rather than case by case later.
- Agree who collects the reporting period data, through what route, and what happens if a utility changes its portal or its formats.
- Confirm the data will be available in the same structure at the end of the term as at the start, including after staff turnover on either side.
- Set the trigger for a non routine adjustment and the evidence needed to support one.
For the regression side of an Option C analysis, the baseline mechanics are worked through in more detail in IPMVP option C baselines.
The data problems that hurt ESCOs
- Baseline gaps: missing or estimated bills weaken the pre-project baseline that every savings claim is measured against.
- Multi-utility portfolios: a single client can span several utilities for electricity and gas, each with a different portal and export format.
- Ongoing verification: savings are typically verified over multiple years, so the data feed cannot be a one-time pull. It has to keep arriving.
- Manual entry risk: rekeying figures from PDF bills introduces transcription errors into the exact numbers a guarantee depends on.
How EZGB supports M&V workflows
EZGB collects the utility data that performance contracting depends on and keeps it in a standardized form:
- Green Button DMD and CMD: standardized electricity and gas usage exports, plus ongoing CMD feeds so verification data keeps flowing across a multi-year contract.
- Multi-utility coverage: one collection workflow across the several utilities a client portfolio may span, rather than a separate manual process per utility.
- Bill digitization: PDF bills converted into structured data, useful for building historical baselines and for accounts at utilities that do not offer Green Button.
- API and ongoing feed: connected accounts deliver new reads on a schedule, which suits the multi-year measurement window a performance contract requires.
For an Option C style analysis, the value is a consistent, gap-free consumption series that can be pulled into whatever measurement and verification or regression tool the ESCO already uses. Clean input data reduces the number of judgment calls and estimates that later become points of dispute.
The same data layer also serves the sales side of the business. Before a contract is signed, an ESCO has to size the opportunity, and that starts with the customer's historical use. Standardized collection means the same pipeline that later supports verification can also produce the baseline used to scope a project, so the numbers a customer sees in a proposal are drawn from the same source that will later confirm the results. That continuity is easier to defend than a proposal built on one set of figures and a verification built on another.
What good data hygiene looks like
Whatever tools an ESCO uses, a few practices keep performance contracts defensible:
- Establish the baseline from complete history: pull enough continuous pre-project data to model normal use, and flag any estimated or missing bills before they enter the baseline.
- Standardize formats early: convert bills and exports into one structure so electricity and gas from different utilities line up.
- Keep the feed live: use an ongoing feed rather than periodic manual pulls, so the verification period never develops gaps.
- Separate collection from analysis: treat data collection as its own reliable layer, so the analysis team spends its time on modeling, not on chasing downloads.
EZGB keeps the underlying consumption and billing history arriving in one structure for the life of a contract, across the several utilities a single client usually spans. You can check which utilities we collect from and what it costs per meter.
Performance contracting is a promise backed by numbers, and the numbers come from utility meters. The more complete and consistent the consumption history, the more defensible the savings guarantee. Reliable, standardized data collection across every utility a client touches is not the glamorous part of an ESCO's work, but it is the foundation the guarantee stands on.
Source: emp.lbl.gov