Buildings rarely perform as designed — and almost never keep performing as commissioned. Control strategies drift, overrides accumulate, sensors fail silently, and the team that inherits the building inherits problems nobody documented. Empirical research published in Science and Technology for the Built Environment found that on any given day, 40% of air handling units and 30% of variable air volume terminals are running with at least one identifiable fault. Not catastrophic failures — the quiet kind that waste energy, erode comfort and shorten equipment life without ever tripping an alarm.
Monitoring-based commissioning (MBCx) — also called ongoing or continuous commissioning — exists because of that reality. It turns commissioning from a handover event into a permanent feedback loop.
This guide covers what MBCx actually is, why buildings drift, what a real program looks like, where most implementations quietly fail, and how to evaluate the platforms that support it.
Key takeaways
- MBCx uses continuous data and automated fault detection to hold building performance at its commissioned level — indefinitely, not just at handover.
- Buildings lose efficiency steadily after commissioning as equipment wears, overrides accumulate and sensors drift; the losses are individually invisible and collectively expensive.
- The U.S. DOE puts median whole-building energy savings from fault detection at 9%, with a realistic range of 5–30%.
- Most MBCx programs fail not at detection but at follow-through: the gap between finding a fault and verifying it was fixed.
- Evaluate platforms on data integration, fault-detection quality, and — above all — whether the loop closes.
What is monitoring-based commissioning?
MBCx is the practice of using analytics software, live building data and automated fault detection and diagnostics (FDD) to maintain building performance continuously after initial commissioning. Where traditional commissioning verifies design intent at a point in time, MBCx assumes the truth about buildings: they change. Occupancy shifts, someone overrides an economy cycle during a heatwave and never removes it, a temperature sensor drifts out of calibration and takes a chiller schedule with it.
The distinction is simple to state and profound in practice: traditional commissioning is a project; MBCx is a program. A project ends. A program answers, every month, the question a project can't: is the building still performing?
MBCx vs retro-commissioning
Retro-commissioning (RCx) is a one-time project that brings an existing building back to optimal performance — find the accumulated faults, fix them, re-baseline. MBCx is what stops the building sliding straight back. The two work best in sequence: RCx recovers the performance, MBCx holds it. Many firms now deliver them as a single continuous engagement, which is quietly reshaping how commissioning services get bought — from projects to retainers.
Why buildings need it: the drift problem
Nobody decides to let a building degrade. It happens one small, reasonable decision at a time. A manual override during a complaint. A belt that stretches. A damper actuator that sticks at 80% and reads fine from the front end. Each is trivial; together they compound, and because they arrive gradually, monthly utility bills never show a step change worth investigating.
That's why drift is so dangerous for rated buildings in particular. A NABERS 5-star asset doesn't announce that it's become a 4.5-star asset — it just quietly is one, and the owner finds out at the next assessment, after a year of the underperformance is already priced into the energy bills.
The alternative to catching drift early is reactive maintenance, and its costs go well beyond the repair bill: emergency call-outs at premium rates, equipment running degraded for months before failing outright, comfort complaints that damage tenant relationships, and an operations team permanently in firefighting mode. MBCx inverts the pattern — the stuck actuator gets flagged within hours and fixed in a normal maintenance window, not discovered via a complaint in February.
The three components of a real MBCx program
1. The analytics layer. A platform that connects to the existing BMS (whoever made it), utility meters and any additional sensors, normalises that data, and runs FDD rules against it continuously. The critical requirement is BMS-agnosticism and no forced capital works — an MBCx program that starts with a hardware retrofit is a program that starts next financial year.
2. The fault-detection intelligence. Rules that compare actual behaviour against expected behaviour: chillers running out of hours, simultaneous heating and cooling, economy cycles that never engage, sensors reporting the physically impossible. Quality matters more than quantity here — badly tuned rules bury teams in false positives, and a team that has learned to ignore alerts has an expensive screensaver, not a commissioning program. Rules built and tuned by mechanical engineers, prioritised by financial and comfort impact, are what separate signal from noise.
3. The response loop. This is the component most programs skip, and it's where they die. Detection has to flow into assignment, assignment into work, and work into verification that the fix actually held — timestamped, in the data, not in a contractor's close-out note. Without that last step, MBCx degenerates into a monthly PDF of findings that nobody actions, which is just traditional commissioning's report, delivered more often.
That verification step is also what makes commissioning honest. Commissioning has always been an independence discipline — the party verifying performance shouldn't be the party whose work is being verified. A contractor closing out their own faults in their own system is marking their own homework. An independent monitoring layer referees the loop for everyone: the owner sees verified outcomes, and good contractors get data that proves their work rather than assertions about it.
Implementing MBCx: six steps
Define goals and scope. Energy intensity, NABERS protection, comfort complaint reduction, maintenance cost — pick the metric that matters and let it drive which assets go first. Buildings with known issues, high energy intensity or an approaching rating assessment are natural starting points.
Baseline current performance. Document how systems actually run today — not design intent, reality. The baseline isn't a target; it's the reference that makes both improvement and drift measurable.
Integrate the data. Connect BMS points, meters and weather feeds into one normalised dataset. This is where timelines blow out on most platforms — months of manual point-mapping. Modern ML-assisted tagging compresses it to weeks; ask any vendor for their median contract-to-live time and treat evasion as data.
Tune the fault detection. Thresholds calibrated to the actual building, not the design manual. This is where engineering expertise earns its keep — the same rule needs different tuning in a Brisbane shopping centre and a Melbourne office tower, and the first month of tuning determines whether the team trusts the system in month six.
Establish the response process. Who triages alerts, who assigns, how contractors receive and close work, what the escalation path is, and how fixes are verified in the data. Write it down; train everyone. Consistency beats heroics.
Review and compound. Monthly or quarterly reviews of open faults, resolution rates and performance trends. Feed the findings into capital planning — equipment that keeps flagging is telling you something about its remaining life, and the data turns replacement debates into evidence.
Evaluating platforms for MBCx
Five questions do most of the work:
- Can it connect to what exists? Any BMS, no new sensors as a precondition, gaps and messy data handled gracefully.
- Is the fault detection engineered or just relayed? Analysing behaviour the BMS can't see, rules customisable without coding, a credible story on false-positive reduction.
- Do alerts arrive with answers? Cause, impact in dollars or comfort terms, recommended fix, mobile access for the people actually on site.
- Does the loop close? Task assignment, progress tracking, and automated verification that the repair restored normal operation — the feature that separates an MBCx platform from a dashboard.
- Who stands behind it? Qualified engineers who tune rules and interpret the ambiguous cases, or a help desk reading the same screen you are.
Where CIM's PEAK Platform fits
PEAK was built as the continuous layer this guide describes: BMS-agnostic data extraction with no new hardware, onboarding in weeks via ML-assisted tagging, thousands of engineer-built FDD rules tuned per building, and a closed workflow that runs from alert through assignment to verified resolution — with NABERS tracked monthly to decimal precision so drift is caught long before an assessment. Every customer gets a dedicated engineer with mechanical or mechatronic qualifications, and across more than 100 million square feet monitored, assets average 19% energy savings — savings that persist precisely because the monitoring does.
It's also how commissioning firms themselves deliver MBCx at scale. Aero Performance Group, an Illinois RCx and MBCx leader, runs its client portfolio on PEAK — growing active projects 50% without adding an engineer and winning their utility's Top Performer award for most kWh saved three years running. For owners, that's the model working; for commissioning providers, it's the build-versus-buy answer.
Common failure modes (and how to avoid them)
Messy data. Point names that match no documentation, uncalibrated sensors, gaps when systems drop offline. Fix it systematically at onboarding — validate the critical points first — rather than discovering it fault by fault.
Alert fatigue. Start with high-impact rules only, tune hard in the first weeks, expand as trust builds. An ignored alert system is worse than none, because it manufactures false confidence.
Organisational resistance. Contractors fear the accountability; site staff fear the implication. The honest answer is that the data helps good operators and exposes only the other kind — lead with quick wins that make the site team look good, and bring contractors in as participants in the loop, not subjects of it.
The bottom line
MBCx is the difference between commissioning as a certificate and commissioning as a state of affairs. The technology is proven, the savings are well-documented, and the drift it prevents is happening in your buildings right now whether it's being measured or not. The programs that work share one trait: they close the loop — from data to fault to fix to proof. The ones that don't produce very sophisticated descriptions of problems nobody solved.
If you want to see what a closed loop looks like on your own portfolio, watch a PEAK demo — or, if you're a commissioning firm weighing build versus buy, talk to our partner team.
FAQs about monitoring-based commissioning
What's the difference between MBCx and retro-commissioning?
RCx is a one-time project that restores an existing building to optimal performance; MBCx is the ongoing program that keeps it there. RCx fixes accumulated problems, MBCx catches new ones as they develop. The strongest results come from running RCx first and MBCx permanently after.
How long does implementation take?
With ML-assisted point tagging and no new hardware, initial onboarding now takes weeks rather than months, with first fault-detection rules live within about 30 days of starting integration. Full tuning and workflow bedding-in typically takes a few months more.
Does MBCx require new sensors?
Usually not. Modern platforms extract from the existing BMS, meters and sensor networks. Targeted sensor additions can sharpen specific monitoring later, but they're an optimisation, not a prerequisite.
What ROI should operations teams expect?
The U.S. Department of Energy reports a median 9% whole-building energy saving from fault detection, with a realistic range of 5–30% depending on how well-optimised the building was to start. Further returns come from avoided emergency repairs, extended equipment life and protected sustainability ratings.
Which buildings benefit most?
Anything with complex HVAC — offices, retail centres, hotels, hospitals, airports, universities. The strongest paybacks come in buildings with high energy intensity, ambitious rating targets, or a history of comfort complaints.
How does MBCx change the contractor relationship?
Work shifts from calendar-based inspections to condition-based responses to specific, evidenced faults — and resolution becomes measurable. For good contractors that's an upgrade, not a threat: verified performance data proves the value of their work in a way a service report never could.
