70/100

Moderate evidence

GainPublished recordClimateGood Space

Artificial intelligence for energy optimization in smart buildings: A systematic review and meta-analysis

Truvace record
TRV-2026-2777raw data (JSON)
Version
v1Published
First published
Evidence type
Systematic review or meta-analysis
Sources
1 sourcePeer-reviewed
sha256
1b5a3cb0f922…check it

This systematic review and meta-analysis critically evaluates artificial intelligence (AI) applications for energy optimization in smart buildings through comprehensive analysis of 126 peer-reviewed studies (2010–2024) from four major databases. We present a novel taxonomic framework categorizing AI implementations into five distinct approaches: predictive systems, adaptive control, pattern recognition, hybrid ensemble methods, and edge AI implementations. Our meta-analysis reveals significant performance variat…

The gain

A meta-analysis of 126 studies found reinforcement-learning building controls cut energy use by an average 22.3% against conventional building management systems, and hybrid methods by 28.1%.

What this doesn’t fix

Studies skew toward wealthy countries and office buildings, most were simulations or single-season tests, and the authors note that negative results are likely underrepresented.

Sources

1 on file
  1. Energy Informaticsdoi:10.1186/s42162-025-00592-8
    Peer-reviewed2025-11-05

Cite this record

v1

Truvace Impact Record TRV-2026-2777, v1: “Artificial intelligence for energy optimization in smart buildings: A systematic review and meta-analysis.” Truvace, 2026-11-12. /record/TRV-2026-2777 (accessed on the day you copy it). sha256 1b5a3cb0f9225011…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv11b5a3cb0f922…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2777 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.