Skip to main content

Energy Efficiency Measurement

Data Inputs & Configurations Guide​

About This Guide

This guide explains the data inputs and configuration settings required to enable Energy Efficiency Measurement within FLEX Programs. It outlines the datasets needed to calculate measured savings and the available program configuration options. It describes how these elements align with program objectives and regulatory requirements so performance can be measured consistently, transparently, and throughout the program lifecycle.

Measurement Overview

Continuous Program Performance​

Measurement is the foundation of FLEX Programs. It establishes how energy efficiency performance is tracked and reported, and configured to meet the unique requirements of each program. Using interval-level metering data, project installation records, and program configuration settings, FLEX Programs calculates measured savings for every participating site throughout the life of the program. Program Administrators can configure measurement settings to align with internal operations, regulatory reporting requirements, and evaluation frameworks while enabling continuous tracking of program performance.

Once configured, FLEX Programs automatically applies these settings across the program lifecycle. Rather than relying solely on deemed or engineering estimates, the platform continuously evaluates actual energy usage before and after project installation to quantify real-world impacts. Results update automatically in the Measurement view as new data is received and processed, providing a clear and continuously evolving view of program performance over time.

Using Measurement, you’ll know:​
  • The measured energy savings for each project and participant
  • How savings evolve following project installation
  • Which measures, technologies, or contractors are delivering the most impact
  • How performance varies across customer segments, building types, and geographies
  • The aggregate program savings relative to forecasted or deemed expectations

Core Data​

Below are the core data needed to calculate ongoing performance measurement:

CATEGORYDESCRIPTION
Interval Load DataHourly or 15-minute AMI data for all participating service points. This data provides the observed load used to calculate project impacts and serves as the basis for performance measurement. Historical data is required from up to 1 year before the start of the program’s season to calibrate models. The data flow should be continuous throughout the program to enable ongoing performance measurement.
Customer MetadataFoundational customer and site attributes that allow segmentation, normalization, and contextual analysis. These fields enable the assessment of performance across various customer types, rate structures, and equity groups. Update customer metadata alongside new Interval and Project Data to account for new accounts, tariff changes, and classification updates.

Fields:
• Service account ID
• Utility’s Premise or location ID
• Customer class (residential, commercial, industrial)
• Tariff or rate schedule
• Income or equity flag (e.g., CARE/FERA, low-income indicator)
• Building type or NAICS sector code
• Climate zone Net metering
Project DataProject data can be provided on an ongoing basis using the Implementation Tools features, bulk transfers, or via API integration. Links sites to the specific projects and performance groups that will be measured. Project datasets should be updated at least monthly so each program’s impact reflects the latest enrollment information.

Fields:
• Program ID and name
• Enrollment start and end date
• Aggregator Enrolled project, measure(s) and associated load shape(s)
• Project installation dates (blackout period)
• Forecasted kWh and/or Therms savings for the project
• Population segments such as NAICS codes, sectors, business types, etc.
• Equity data such as DAC, local contractor, ESL, etc.
• Building square footage
Non Participant Data
Optional		Customer metadata and AMI data from accounts not enrolled in the measured program. While optional, it is strongly encouraged to include this data to significantly improve measurement accuracy by accounting for external factors that influence energy use beyond program activity, such as economic conditions or broader system trends. This distinction enables the platform to separate true energy efficiency project impacts from background variation, yielding more precise and defensible measurement results.

Measurement Configuration All configurations must be compliant with the Program M&V Plan​

CONFIGURATION AREADESCRIPTION
General Program ConfigurationGeneral program design informs configuration options listed below. May or may not apply depending on program type.

Configuration:
• Program enrollment start & end dates
• Accepted population segment(s)
• Optional value stream inputs (Avoided Cost Curve, Total System Benefit value curve, etc.)
• Measure characteristics such as Effective Useful Life (EUL), deemed/standard measure load shapes, and therms profile Net-to-Gross ratios (Ex, Commercial vs. Residential)
• Discount rates
Assigned Savings MethodologyPortfolio Average Forecast with Realization Rate Forecast Direct (or Deemed)
Disqualification ThresholdsRecurve can set automated validations to flag savings-outlier projects with measured savings that are within +/- X% of the counterfactual, based on what makes sense for the accepted program measures. The system automatically disqualifies flagged projects for further review, and administrators can override them back to qualified or measured status if justified. The typical recommended savings outlier thresholds for energy efficiency projects are as follows: Electric meters: Minimum percent savings -50% of the counterfactual Maximum percent savings of 50% of the counterfactual Gas meters: Minimum percent savings of -50% of the counterfactual Maximum percent savings of 50% of the counterfactual Other optional disqualification settings include total usage outliers, to flag sites with total counterfactual usage values beyond specified thresholds.