Building energy analytics can help facilities teams turn meter and building automation system data into prioritized operational improvements. But software alone does not reduce energy use: people must review findings, investigate causes and implement corrective actions. Results from the U.S. Department of Energyâs Smart Energy Analytics Campaign, reported in 2019, illustrate both the potential of energy management and information systems (EMIS) and the work required to use them effectively.
The campaign included 96 commercial organizations, representing 5,900 buildings and 518 million square feet. Its findings are not a guarantee of results for any individual facility, and reported energy changes could reflect projects beyond analytics. Still, the data provide a useful reference for teams evaluating continuous monitoring and commissioning approaches.
Building energy analytics: turning data into operational insight
Building automation systems (BAS) control equipment and can generate alarms when individual values move outside set limits. However, point alarms do not necessarily reveal how several conditions interact, whether a system is operating efficiently over time, or where energy use changes across a portfolio. EMIS tools add analytical capabilities by collecting, organizing and assessing energy and system data.
Two common EMIS categories serve different purposes:
- Energy information systems (EIS) analyze whole-building or submeter energy data, often at hourly or more frequent intervals. Teams use them to track consumption, compare buildings, review load profiles and identify scheduling or baseline opportunities.
- Fault detection and diagnostics (FDD) analyze BAS data to detect system faults or suboptimal operation and help identify possible causes. Examples include economizer problems, failed sensors, leaking valves, unstable control loops and simultaneous heating and cooling.
These tools support monitoring-based commissioning (MBCx), an ongoing process that uses regular data collection and analysis to identify issues, prioritize investigation, verify improvements and look for further opportunities. MBCx can also help teams check whether improvements made during retrocommissioning continue to perform.
What the campaign found about energy savings
Among participants with at least two years of implementation data, the reported median whole-building savings were 4% for EIS users and 9% for FDD users. The corresponding median savings were $0.04 and $0.24 per square foot per year. Across 45 participants, the most recent available energy data showed a combined reduction of 2.6 trillion Btu per year and $59 million per year compared with baseline years.
These are observed whole-building changes, not savings attributed solely to EMIS. Other energy projects and changes may have contributed. The campaign also reported that savings generally increased over time among participants with multiple years of data, while cautioning that later-year results were based on fewer organizations. For decision-makers, the figures indicate potential, but they should not be treated as a forecast for a new installation.
The most frequently reported measures were operational adjustments rather than major equipment replacements. HVAC scheduling was the leading measure, followed by space temperature setpoint changes, reducing simultaneous heating and cooling, improving economizer operation and resetting supply air temperature. EIS load profiles and heat maps can help flag schedules and unusual consumption patterns; FDD can provide more detailed clues about equipment and control behavior.
Understand costs, labor and payback together
For participants reporting costs, median one-time software installation and configuration costs were $0.01 per square foot for EIS and $0.05 for FDD. Median annual recurring costs were $0.01 per square foot for EIS and $0.02 for FDD. Reported in-house use also differed: a median of one hour per month per building for EIS and nine hours for FDD.
FDDâs higher reported costs and labor reflect the work involved in connecting and mapping BAS points, configuring diagnostic rules and interpreting findings. Actual costs varied with implementation scope, portfolio size and service-provider support. The campaignâs figures exclude some potential expenses, including metering hardware, communications upgrades, BAS point additions and retrofit work. Budget planning should therefore consider the full project rather than software fees alone.
Using its stated cost-effectiveness method, the campaign estimated median simple payback periods of 1.5 years for EIS and 1.1 years for FDD. These estimates included implementation and labor costs, plus an estimated cost for operational measures. Because EMIS enables action rather than directly producing most savings, payback depends on the opportunities found, the resources available to address them and how savings are measured.
Build the operating process before scaling analytics
Successful implementation depends on more than selecting a platform. Campaign participants identified staff time, management support, metering gaps, data quality and integration as recurring challenges. Legacy BAS, inconsistent naming conventions and separate data sources can make it difficult to bring information into a usable central system. Poorly configured analytics can also create data overload instead of clear priorities.
Several practical steps can reduce these risks:
- Define the operational need. Choose analytics around specific questions, such as portfolio energy tracking or diagnosis of HVAC faults, rather than pursuing every available feature.
- Check data readiness. Review meter coverage, BAS access, data continuity and integration requirements before setting implementation expectations.
- Assign responsibility. Establish who reviews outputs, investigates issues, approves work and records results. Consider whether in-house teams need support from an MBCx service provider.
- Make review routine. Integrate analytics into existing operations meetings, work processes and reporting so that findings receive follow-up.
- Plan verification. Set a consistent approach for assessing energy changes and distinguish analytics-supported actions from other projects where possible.
Conclusion: analytics needs an action pathway
The campaignâs findings show that EIS and FDD can help commercial building teams uncover operational opportunities, track energy performance and inform retrofit decisions. They also show why results depend on implementation scope, data quality, staff capacity and sustained follow-through. For technical and operational leaders, the practical priority is to connect analytics to a clear process: collect reliable data, focus on useful diagnostics, assign owners to findings and verify the effects of implemented measures.
Access Official Technical PDF