• Energy
  • 20 columns
  • 72 rows
  • 8 formats

Building IoT Energy Anomaly Log

This dataset logs energy usage anomalies detected by IoT sensors in smart buildings, including sensor details, anomaly classification, severity, timestamps, and resolution status. It empowers facilities managers and proptech architects to monitor, investigate, and resolve energy inefficiencies, supporting sustainability initiatives and operational optimization. The rich, structured data enables advanced analytics, fault detection, and compliance reporting for modern building management.

  • last updated 12 Jan 2026
  • by GoMask
The brief that made it

Automated detection and tracking of energy usage anomalies for smart buildings

Sample rows

preview · 8 of 72 rows · all 20 columns
anomaly_idstringanomaly_typestringanomaly_duration_minutesintegerreported_bystringbuilding_idstringbuilding_namestringsensor_idstringsensor_typestringlocation_floorstringlocation_zonestringanomaly_severitystringanomaly_detected_atdatetimeenergy_usage_valuefloatexpected_usage_valuefloatusage_unitstringresolution_statusstringresolution_timestampdatetimeresolution_notesstringenvironmental_impact_scorefloattagsstring
ANOM-1A4B-202406A1spike40system_auto_detectBLDG-CHIC-001Loop TowerSENS-HVAC-101hvac_sensor10East Winghigh2024-06-04T09:12:43145.697.5kWhin_progressblankHVAC control recalibration scheduled.39.2HVAC,sustainability,spike
ANOM-2B3C-202406A2drop22energy_managerBLDG-NYC-002Hudson PlazaSENS-SMTR-202smart_meterGroundLobbymedium2024-06-03T18:24:1112.342.8kWhopenblankblank5.7smart_meter,drop,energy
ANOM-3C4D-202406A3sustained120system_auto_detectBLDG-SF-003Market CenterSENS-LGHT-303lighting_sensor3Conference Hallcritical2024-06-01T07:50:29320.9210.4kWhresolved2024-06-01T09:12:30Lighting system replaced.65.1lighting,sustainability,critical
ANOM-4D5E-202406A4pattern_deviation7maintenance_teamBLDG-CHIC-001Loop TowerSENS-TEMP-104temperature_sensor10Server Roomlow2024-06-05T12:18:1048.252Whfalse_positive2024-06-05T12:35:22Sensor calibration error.1.7temperature,sensor,low
ANOM-5E6F-202406A5spike51system_auto_detectBLDG-NYC-002Hudson PlazaSENS-HVAC-107hvac_sensor7West Wingmedium2024-06-04T14:02:44179.8110.2kWhopenblankblank47.8HVAC,energy,medium
ANOM-6F7G-202406A6other3building_operatorBLDG-LA-004Sunset OfficesSENS-OTHR-401other2Receptionlow2024-06-02T11:35:218.214.7Whopenblankblank0.3reception,low,other
ANOM-7G8H-202406A7spike115system_auto_detectBLDG-SF-003Market CenterSENS-SMTR-306smart_meter12Executive Suitecritical2024-06-06T08:43:19410.5260.2kWhresolved2024-06-06T11:20:09Power surge isolated.87.4smart_meter,critical,spike
ANOM-8H9I-202406A8pattern_deviation18facility_managerBLDG-LA-004Sunset OfficesSENS-LGHT-415lighting_sensor5Atriummedium2024-06-03T16:24:0863.457.8Whin_progressblankLighting schedule review ongoing.2.8lighting,medium,review

What the 72 rows show

from the 72-row sample

Sustained (anomaly type) stands out: mean anomaly_duration_minutes is 175.1, against 39.6 for the rest.

  • 37.5median anomaly_duration_minutes
  • 3usage units
  • 4anomaly severities
  • 4resolution statuses
  • 5sensor types
  • 15buildings
Mean anomaly_duration_minutes by anomaly_type72 rows
010020061.0spike21 rows15.9drop15 rows175.1sustai…14 rows41.6patter…16 rows18.7other6 rows
anomaly_duration_minutes72 rows, in bands of 50
0255042156430110200400anomaly_duration_minutes →

Median 37.5, from 2 to 388.

reported_by72 rows · top 10 of 26 values
  1. system_auto_detect12
  2. energy_manager7
  3. AutoDetectAI6
  4. facility_manager5
  5. building_ops5
  6. maintenance_team4
  7. facility_mgr4
  8. building_operator3
  9. jlee3
  10. temp_monitor2
20 columns by typefrom the column list below
  • string 14
  • integer 1
  • float 3
  • datetime 2

Columns

20 columns in three groups
blueprint · 20 columns
columntypedescriptionexample
Text 14 columns
anomaly_idstringUnique identifier for the detected energy anomaly eventuniqueANOM-1A4B-202406A1
building_idstringUnique identifier for the building where the anomaly was detectedBLDG-CHIC-001
building_namestringHuman-readable name of the buildingLoop Tower
sensor_idstringUnique identifier for the IoT sensor that detected the anomalySENS-HVAC-101
sensor_typestringType of IoT sensor (e.g., smart meter, HVAC sensor, lighting sensor)5 valueshvac_sensor
location_floorstringFloor within the building where the sensor is locatedoptional10
location_zonestringZone or area within the building (e.g., west wing, conference room)optionalEast Wing
anomaly_typestringClassification of the anomaly (e.g., spike, drop, sustained abnormal usage)spike · drop · sustained · pattern_deviation · otherspike
anomaly_severitystringSeverity level of the anomaly (e.g., low, medium, high, critical)low · medium · high · criticalhigh
usage_unitstringUnit of measurement for energy usage (e.g., kWh, MWh)kWh · MWh · WhkWh
resolution_statusstringCurrent status of the anomaly resolution processopen · in_progress · resolved · false_positivein_progress
resolution_notesstringNotes or comments regarding the resolution of the anomalyoptionalPower surge isolated.
reported_bystringName or identifier of the person/system who reported or confirmed the anomalyoptionalsystem_auto_detect
tagsstringComma-separated tags for anomaly categorization (e.g., sustainability, HVAC, lighting)optionalsmart_meter,drop,energy
Numbers 4 columns
energy_usage_valuefloatMeasured energy usage value at the time of anomaly (e.g., kWh)0 or more145.6
expected_usage_valuefloatExpected or baseline energy usage value for comparison0 or more · optional97.5
anomaly_duration_minutesintegerDuration of the anomaly in minutes0 or more · optional40
environmental_impact_scorefloatEstimated environmental impact score of the anomaly (e.g., CO2 equivalent)0 or more · optional39.2
Dates and times 2 columns
anomaly_detected_atdatetimeTimestamp when the anomaly was detected2024-06-04T09:12:43
resolution_timestampdatetimeTimestamp when the anomaly was resolved (if applicable)optional2024-06-01T09:12:30

Use it for

  • median anomaly…37.572 rowsmean anomaly duration…61.0spike15.9drop175.1sust…41.6patt…

    An energy dashboard

    Anomaly_duration_minutes by anomaly_type and a breakdown of reported_by. Excel, Power BI or Tableau.

  • Why do the 14 sustained rows have a mean anomaly_duration_minutes of 175.1?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable anomalies with building_id, building_name and sensor_id to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 20 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset72 rows20 columns
Yours1,000 rows20 columnslocation_floor: UK only

blueprint · building-iot-energy-anomaly-log

Behind this dataset

Same schema. As many rows as you need.

These 72 rows came out of a blueprint — 20 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Each row represents a unique anomaly event flagged by IoT devices
  • Anomaly type must be categorized (e.g., overconsumption, device failure, unauthorized access)
  • Include device location, timestamp, and affected energy zone
  • Severity level classified as low, medium, or high
  • Resolution status tracked (open, investigating, resolved)
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
building-iot-energy-anomaly-log

What should your data show?

Preview 20 rows free
No signup. No card.