• Energy
  • 26 columns
  • 75 rows
  • 8 formats

IoT Building Energy Anomaly Logs

This dataset logs detailed records of energy usage anomalies detected by IoT sensors across commercial buildings, including sensor metadata, anomaly characteristics, location details, and corrective actions. It enables facilities managers and ESG consultants to benchmark energy performance, identify inefficiencies, and investigate abnormal consumption patterns for smarter, more sustainable building operations.

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

Benchmarking building energy performance for sustainability reporting

Sample rows

preview · 8 of 75 rows · all 26 columns
anomaly_idstringanomaly_severitystringanomaly_duration_minutesfloatbuilding_idstringbuilding_namestringbuilding_street_addressstringbuilding_citystringbuilding_statestringbuilding_postal_codestringbuilding_countrystringfloor_numberintegerzone_namestringsensor_idstringsensor_typestringanomaly_typestringanomaly_statusstringdetection_timestampdatetimeexpected_energy_usage_kwhfloatactual_energy_usage_kwhfloatenergy_deviation_kwhfloatenergy_deviation_percentfloatroot_cause_suspectedstringcorrective_action_takenstringresolved_timestampdatetimereported_bystringnotesstring
ANML-00001high37.2BLDG-1101Aurora Tower245 Market StSan FranciscoCA94105USA7LobbySNSR-E-1001electricity_meterspikeopen2024-05-01T08:27:0015.535.920.4131.6Lighting left on overnightblankblanksystemUnusually high usage detected during off-hours
ANML-00002medium19.8BLDG-1101Aurora Tower245 Market StSan FranciscoCA94105USA12Conference RoomSNSR-T-1107temperature_sensorpattern_deviationinvestigating2024-05-02T13:10:009.212.12.931.5Thermostat misconfigurationblankblankJ.Smithblank
ANML-00003low8.5BLDG-1102Pacific Plaza150 Pine AveLos AngelesCA90045USA3Main OfficeSNSR-O-2013occupancy_sensordropresolved2024-05-04T09:23:007.64.1-3.5-46.1Holiday closureConfirmed closure, no action needed2024-05-04T10:31:00systemPattern matches previous holiday
ANML-00004critical47.9BLDG-1201Harbor Point2232 3rd StSeattleWA98121USA0BasementSNSR-H-3002hvac_sensorequipment_failureopen2024-04-28T18:42:0010.81.5-9.3-86.1HVAC malfunctionblankblanksystemImmediate technician dispatch recommended
ANML-00005medium16.4BLDG-1202Lakeview Center6102 Green Lake DrSeattleWA98103USA2ReceptionSNSR-E-1206electricity_meterspikeinvestigating2024-05-05T17:15:00818.710.7133.8Cleaning crew activityblankblankM.KimSpike coincides with scheduled cleaning
ANML-00006high7BLDG-1202Lakeview Center6102 Green Lake DrSeattleWA98103USA1Break RoomSNSR-T-1211temperature_sensoroutlierdismissed2024-05-06T10:03:005.38.73.464.2Short-term heatwaveNo action required2024-05-06T11:00:00systemblank
ANML-00007critical51.6BLDG-1301Canyon Corporate3300 W 6th StDenverCO80204USA5Server RoomSNSR-E-1302electricity_meterspikeresolved2024-05-07T02:20:0022.749.226.5116.8Server hardware testTest scheduled, anomaly expected2024-05-07T03:15:00A.LopezPlanned spike for maintenance
ANML-00008medium22BLDG-1301Canyon Corporate3300 W 6th StDenverCO80204USA2CafeteriaSNSR-O-1315occupancy_sensordropopen2024-05-08T08:35:0010.28-2.2-21.6Unexpected early closureblankblanksystemblank

What the 75 rows show

from the 75-row sample

Critical (anomaly severity) stands out: mean anomaly_duration_minutes is 43.9, against 17.8 for the rest.

  • 17.0median anomaly_duration_minutes
  • 4anomaly statuses
  • 5sensor types
  • 6anomaly types
  • 12reported_by values
  • 14building states
Mean anomaly_duration_minutes by anomaly_severity75 rows
0501008.9low17 rows18.2medium31 rows26.5high16 rows43.9critical11 rows
anomaly_duration_minutes75 rows, in bands of 10
0153015281310720000050100anomaly_duration_minutes →

Median 17.0, from 5.4 to 51.8.

building_id75 rows · top 10 of 33 values
  1. BLDG_10510
  2. BLDG_1109
  3. BLDG_1119
  4. BLDG_2079
  5. BLDG-11012
  6. BLDG-12022
  7. BLDG-13012
  8. BLDG-15012
  9. BLDG-16012
  10. BLDG-17012
26 columns by typefrom the column list below
  • string 18
  • integer 1
  • float 5
  • datetime 2

Columns

26 columns in three groups
blueprint · 26 columns
columntypedescriptionexample
Text 18 columns
anomaly_idstringUnique identifier for each detected energy anomaly eventuniqueANML-00001
building_idstringUnique identifier for the building where the anomaly was detectedBLDG-1101
building_namestringName of the buildingoptionalAurora Tower
building_street_addressstringStreet address of the buildingoptional245 Market St
building_citystringCity where the building is locatedoptionalSan Francisco
building_statestringState or province where the building is locatedoptionalCA
building_postal_codestringPostal or ZIP code of the buildingoptional94105
building_countrystringCountry where the building is locatedoptionalUSA
zone_namestringName or label of the building zone/area (e.g., 'Lobby', 'Conference Room')optionalLobby
sensor_idstringUnique identifier for the IoT sensor that detected the anomalySNSR-E-1001
sensor_typestringType of IoT sensor (e.g., 'electricity_meter', 'temperature_sensor', 'occupancy_sensor')5 valueselectricity_meter
anomaly_typestringCategory of anomaly detected (e.g., 'spike', 'drop', 'pattern_deviation', 'equipment_failure')6 valuesspike
anomaly_severitystringSeverity level of the anomaly (e.g., 'low', 'medium', 'high', 'critical')low · medium · high · criticalhigh
anomaly_statusstringCurrent status of the anomaly (e.g., 'open', 'investigating', 'resolved', 'dismissed')open · investigating · resolved · dismissedopen
root_cause_suspectedstringSuspected root cause of the anomaly (e.g., 'HVAC malfunction', 'occupancy spike', 'sensor error')optionalHoliday closure
corrective_action_takenstringDescription of any corrective action taken in response to the anomalyoptionalNo action required
reported_bystringName or identifier of the person or system that reported or confirmed the anomaly12 values · optionalsystem
notesstringAdditional notes or comments regarding the anomalyoptionalTechnician dispatched
Numbers 6 columns
floor_numberintegerFloor number within the building where the anomaly was detected0 or more · optional7
anomaly_duration_minutesfloatDuration of the anomaly in minutes (if applicable)0 or more · optional37.2
expected_energy_usage_kwhfloatExpected energy usage in kWh for the period in which the anomaly occurred0 or more · optional15.5
actual_energy_usage_kwhfloatActual measured energy usage in kWh during the anomaly period0 or more · optional35.9
energy_deviation_kwhfloatDifference between actual and expected energy usage in kWhoptional20.4
energy_deviation_percentfloatPercentage deviation from expected energy usage-100 to 1,000 · optional131.6
Dates and times 2 columns
detection_timestampdatetimeDate and time when the anomaly was detected2024-05-01T08:27:00
resolved_timestampdatetimeDate and time when the anomaly was resolved (if applicable)optional2024-05-04T10:31:00

Use it for

  • median anomaly…17.075 rowsmean anomaly duration…8.9low18.2medi…26.5high43.9crit…

    An energy dashboard

    Anomaly_duration_minutes by anomaly_severity and a breakdown of building_id. Excel, Power BI or Tableau.

  • Why do the 11 critical rows have a mean anomaly_duration_minutes of 43.9?

    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 building_street_address to fill a screen in front of a buyer.

Not quite right?

Make it yours.

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

Preview 20 rows free

10,000 rows of yours: $12.99One-time. No subscription. All prices

This dataset75 rows26 columns
Yours10,000 rows26 columnsbuilding_street_address: UK only

blueprint · iot-building-energy-anomaly-logs

Behind this dataset

Same schema. As many rows as you need.

These 75 rows came out of a blueprint — 26 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 detected by a sensor.
  • Includes timestamp, anomaly type, severity rating, affected zone, baseline consumption, and deviation value.
  • Only anomalies exceeding 10% deviation from baseline are recorded.
  • Events are tagged by likely cause (equipment fault, peak demand, unauthorized usage, etc.).
  • Sensor IDs and building IDs are anonymized for privacy compliance.
  • All entries must include a recommended action field.
Rows
Open the blueprint in Data Factory

1 credit per row. New accounts start with 25 free credits.

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

What should your data show?

Preview 20 rows free
No signup. No card.