HVAC Energy Baseline: 12-Month Data Before You Optimize

By Corin Hale on October 10, 2026

hvac-energy-baseline-12-month-guide

Every HVAC optimisation project promises savings, but savings can only be proven against a credible baseline. Without 12 months of clean energy, weather and operating data, a retuned chiller plant or a new schedule produces a number nobody can defend to finance or auditors. This guide covers what to collect, how to clean it, how to judge a baseline model and how maintenance records explain the changes hiding in the data. It also shows how work orders and asset history in a CMMS support defensible measurement and verification.

HVAC energy monitoring and fault detection

HVAC Energy Baseline: 12-Month Data Before You Optimize

Measure the system as it runs today, across a full year of weather and occupancy, so every future saving has a reference point that stands up to scrutiny.

Illustrative shape of a monthly baseline: cooling and heating peaks, mild shoulder months
JFMAMJJASOND

Why the baseline comes before the optimisation

Energy savings cannot be metered directly, because the energy you did not use never passes through a meter. They are calculated by comparing what the building used after a change with what it would have used under the old conditions. That second number is the adjusted baseline.

Core relationship
Savings = Adjusted baseline energy - Actual energy after the change
The adjusted baseline is the baseline model run with post-change weather, occupancy and schedule conditions.

Why twelve months

  • HVAC load swings with season, so a partial year hides entire operating modes
  • A full cycle captures peak cooling, peak heating and shoulder-season behaviour
  • Holiday shutdowns, events and occupancy patterns appear at least once
  • ASHRAE Guideline 14 expects a baseline period of at least 12 months for whole-building models

The data you need, and where it comes from

Data streamPreferred intervalTypical sourceWhy it matters
Whole-building electricity15 minutes or hourlyUtility interval data or main meterAnchors whole-facility models
HVAC sub-metered electricity15 minutes or hourlyChiller, pump and AHU metersIsolates HVAC from other loads
Gas or district heatingDaily or hourlyUtility or building meterCaptures heating energy
Outdoor temperature and humidityHourlyOn-site sensor or nearby weather stationMain driver of cooling and heating load
Occupancy or operating hoursDailyBadge data, schedules, shift calendarsExplains load differences between days
Setpoints and schedulesOn changeBuilding automation systemShows control intent against actual behaviour
Equipment runtime and statusTrend logsBuilding automation systemLinks energy to what was running
Maintenance and repair eventsEvent basedWork orders and asset historyExplains step changes in energy use

A 12-month collection plan

Treat the baseline year as a project with its own schedule. Setting up instrumentation early prevents the common problem of discovering missing months at the end.

Months 1 to 3
  • Define the measurement boundary
  • Check meter accuracy and units
  • Connect weather and trend sources
  • Set naming rules for points
Months 4 to 6
  • Review data completeness monthly
  • Fill gaps through repair or estimation rules
  • Log all schedule and setpoint changes
  • Draft a preliminary model
Months 7 to 9
  • Capture the main cooling season
  • Test the model against new months
  • Record occupancy changes
  • Document non-routine events
Months 10 to 12
  • Close remaining data gaps
  • Finalise and validate the model
  • Agree acceptance criteria
  • Sign off the baseline report

Give your baseline the maintenance context it needs

Record repairs, tuning and equipment changes against each asset, so every shift in energy use has an explanation on file.

Cleaning the data before it touches a model

Raw interval data is rarely ready to use. Meters reset, communications drop, clocks shift and units get mixed. A short, documented cleaning pipeline keeps these problems from quietly distorting the model.

1
Align timestampsUse one time zone, handle daylight saving transitions and match weather to meter intervals.
2
Check units and scalingConfirm kW against kWh, multipliers and CT ratios before comparing meters.
3
Find gaps and flatlinesFlag missing intervals and long runs of identical values that suggest a failed sensor.
4
Handle outliersInvestigate spikes against events before removing them, since real operation can look odd.
5
Fill gaps with rulesApply a documented method for short gaps and exclude long ones rather than guessing.
6
Keep raw and cleaned copiesPreserve the original data so any adjustment can be reviewed later.

Weather normalisation: degree days and regression

Outdoor conditions drive most of the variation in HVAC energy. Two buildings with identical equipment can show very different bills simply because one year was hotter. Normalising for weather removes that noise so efficiency changes become visible.

Common model forms

  • Simple linear regression of energy against heating or cooling degree days
  • Change-point models that switch behaviour above and below a balance temperature
  • Multivariable models adding humidity, occupancy, daylight or production
  • Time-of-week and temperature models for hourly interval data

Practical tips

  • Choose the balance temperature from the data rather than assuming a default
  • Use a weather source close to the site and keep the same one for the reporting period
  • Check residuals for patterns, since a pattern means a driver is missing
  • Keep the model as simple as the data allows, because complexity can hide errors

Instrumentation gaps and how to close them

Many sites discover during the baseline year that the meters they assumed existed do not, or that existing meters are mislabelled. Resolve these early, because a missing sub-meter cannot be recovered retroactively.

No HVAC sub-meteringUse whole-building data with Option C, or install meters on the chiller plant, boilers and major air handlers before the baseline starts.
Unreliable trend logsVerify the building automation system stores data at a consistent interval and has enough storage to avoid overwriting.
Unverified sensorsCalibrate temperature and flow sensors that feed calculated values such as cooling tonnage or chiller efficiency.
Shared metersWhere tenants or processes share a meter, document how loads are separated and include adjustment factors in the model.

Documenting operating conditions

A model only explains the variables it is given. Written records of how the building was meant to run turn unexplained variance into understood behaviour.

ConditionRecord to keepEffect on the baseline
Occupancy hoursScheduled and actual hours, holidays and eventsShifts ventilation and cooling load
SetpointsCooling, heating and humidity targets with change datesChanges energy for the same weather
Ventilation strategyMinimum outdoor air, demand control and economizer settingsAlters conditioning load
Floor area useTenant moves, vacant floors, new equipment loadsChanges internal gains
Equipment stagingLead and lag order, rotation and lockoutsAffects plant efficiency

What the baseline report should contain

The baseline report is the document that finance, auditors and project partners will return to long after the project ends. It should make every assumption visible.

  1. Project scope, measurement boundary and chosen IPMVP option
  2. Baseline period dates and the reasons for choosing them
  3. Data sources, meter identifiers, intervals and calibration notes
  4. Cleaning rules, gap treatments and excluded periods
  5. Model form, variables and fitted coefficients
  6. Statistical results, including CV(RMSE), NMBE and any hold-out test
  7. Non-routine events and the adjustments applied
  8. Reporting period conditions and how savings will be calculated

Trends shaping HVAC baselining

  • Interval data from smart meters is now widely available, making hourly and sub-hourly models practical
  • Building automation trend data and analytics platforms allow continuous comparison against the baseline
  • Fault detection and diagnostics tools use baseline behaviour to flag drift between audits
  • Energy performance reporting and decarbonisation targets increase scrutiny of claimed savings
  • Maintenance and energy teams are being asked to work from shared data rather than separate spreadsheets

Why this matters to maintenance teams

Maintenance actions are often the cheapest energy measures available. Proving their value requires a baseline, and protecting that value requires the preventive routines that keep performance from drifting back.

Choosing an IPMVP approach

The International Performance Measurement and Verification Protocol defines four options. The right one depends on the size of the project, the interaction with other loads and the available meters.

OptionWhat is measuredGood fit forMain caution
A: Retrofit isolation, key parameterOne key parameter measured, others estimatedPump or fan motor upgradesEstimates need a clear justification
B: Retrofit isolation, all parametersAll energy parameters of the isolated systemChiller plant or AHU retrofits with sub-metersRequires reliable sub-metering
C: Whole facilityUtility meter for the entire buildingMulti-measure programmes with large expected savingsSavings can be hidden by other changes
D: Calibrated simulationSimulation model tuned to measured dataNew construction or missing baseline dataCalibration effort and expertise

How good is good enough: ASHRAE Guideline 14 criteria

Guideline 14 sets statistical limits for whole-building baseline models so that a model is not accepted on appearance alone. Two measures are used, the coefficient of variation of the root mean square error and the normalised mean bias error.

25%
CV(RMSE) limit for monthly calibration
5%
NMBE limit for monthly calibration
30%
CV(RMSE) limit for hourly calibration
10%
NMBE limit for hourly calibration

Reading the numbers

  • CV(RMSE) describes scatter: how far individual predictions sit from actual values
  • NMBE describes bias: whether the model systematically over- or under-predicts
  • Both should be met, and passing one does not excuse failing the other
  • Check the current edition of the guideline and your project specification for exact requirements

Common baseline mistakes: before and after

Weak practiceUsing three months of data and extrapolating to a year
Stronger practiceCollecting a full 12 months that spans every season
Weak practiceIgnoring weather and comparing raw bills
Stronger practiceNormalising for temperature, humidity and degree days
Weak practiceDeleting odd readings without investigation
Stronger practiceChecking outliers against events and logging every decision
Weak practiceForgetting about repairs and equipment changes mid-year
Stronger practiceRecording non-routine events with dates and estimated impact
Weak practiceAccepting a model because the chart looks close
Stronger practiceTesting statistical criteria and a hold-out period

Maintenance events: the hidden variable in every baseline

A baseline is meant to describe normal operation, but real buildings are repaired throughout the year. A failed economizer damper, a stuck valve or a refrigerant leak changes energy use, and the model will treat it as normal unless someone records it.

Events worth logging against the asset

  • Component failures that forced equipment into fallback or manual operation
  • Repairs and parts replacements that changed capacity or efficiency
  • Control changes such as setpoint resets, schedule edits and sequence updates
  • Filter changes, coil cleaning and calibration of sensors and valves
  • Temporary conditions such as portable cooling, construction or tenant moves

Fix first, or measure first?

Safety, comfort and compliance faults should be repaired promptly. The key is to document the fix as a non-routine adjustment, with date and reasoning, so the baseline can be adjusted rather than silently contaminated.

How Oxmaint supports the baseline year

Oxmaint is a maintenance management platform, not a replacement for your metering or analytics tools. Its role is to hold the maintenance context that explains your data and keep upkeep consistent during measurement.

Asset recordsChillers, boilers, AHUs, pumps and VAV units with their locations, specifications and service history.
Preventive maintenanceScheduled filter, belt, coil and calibration tasks so the baseline reflects stable upkeep.
Work ordersDated repair and tuning events that can be flagged as non-routine adjustments.
InspectionsMobile checklists to record readings and observations that complement automated trends.
Reports and dashboardsExports of maintenance events by asset and date range to attach to the baseline report.
Corrective maintenanceTracking of faults found by monitoring until they are verified closed.

From baseline to fault detection

A strong baseline does more than prove savings. It reveals how equipment should behave, which lets analytics flag deviations that point to real maintenance work.

Baseline signalDeviation to watchTypical maintenance response
Cooling energy at given outdoor temperatureRising consumption for the same conditionsInspect coils, refrigerant charge and condenser performance
Fan energy against airflow demandFans running at high speed with little demandCheck filters, dampers and static pressure control
Night and weekend loadHigher than the scheduled shutdown profileReview schedules and overrides, then correct controls
Simultaneous heating and coolingBoth active in the same zone or systemInspect valves, actuators and sensor calibration
Economizer operation in mild weatherLittle or no free cooling when availableTest dampers, linkages and enthalpy or temperature sensors

Checklist before optimisation begins

  • Measurement boundary and options agreed in writing
  • Twelve consecutive months of energy data collected
  • Weather data aligned to the same intervals
  • Occupancy and operating schedules documented
  • Meter accuracy and units verified
  • Data gaps and fills documented with method
  • Non-routine events logged with dates
  • Model tested against statistical criteria
  • Raw data and cleaned data archived
  • Baseline report approved by all stakeholders

Frequently asked questions

Why must an HVAC baseline cover 12 months?

A full year captures every season and occupancy pattern. Shorter periods miss operating modes and weaken the model.

What if I do not have 12 months of data yet?

Start collecting now and use any historical utility data to bridge gaps. Sign up to log events from day one.

Do maintenance activities change the baseline?

Yes. Repairs, tuning and control changes shift energy use, so they should be logged as non-routine events and adjusted for.

Which IPMVP option should I use?

Option B suits sub-metered retrofits, and Option C suits whole-building programmes. Confirm your choice in the M&V plan.

Can a CMMS calculate energy savings?

It does not replace M&V analytics, but it supplies the event history. Book a demo to see how it fits your workflow.

Make your next HVAC saving impossible to dispute

Pair clean baseline data with a complete maintenance record and give finance a number they can trust.


Share This Story, Choose Your Platform!