Skip to main content
The Full Loop Building Operations System

Data-driven maintenance: service what needs it, not what's scheduled.

PEAK reads your plant continuously, ranks every fault by what it costs, assigns it and verifies the fix held. The engineer who knows the building decides what gets serviced - not a calendar written before anyone looked at the data.

PEAK Actions Manager for a sample site: open maintenance actions ranked by impact, with priority, assigned contractor and status

80%

P1 and P2 actions verified

82%

Action closure across 58 properties

50%

More active projects, no extra staff

Trusted by leading global portfolios
Charter HallGPTQICLaSalleCenturiaKyko Group
In short

Data-driven maintenance uses live data from your plant and equipment to decide what gets serviced, when, and in what order. CIM PEAK, the Full Loop Building Operations System, runs it across a portfolio and keeps every job moving until the fix is verified in the equipment data.

The problem

You are paying to inspect equipment that is working fine

Most maintenance contracts run on planned preventive schedules, unplanned reactive callouts, or both. Neither is driven by what the equipment is actually doing.

How it runs today

Planned preventive (PPM)

Rigidly scheduled checks. Time and money spent inspecting plant that is running perfectly well, on a calendar written before anyone looked at the data.

How it runs today

Unplanned reactive (UPM)

The absence of a strategy. Work happens when something breaks or a tenant complains, which makes budgeting a guess and disruption routine.

What it costs

Missed issues

While a contractor inspects working equipment, genuine faults elsewhere can sit unaddressed for months - quietly degrading efficiency until they become a failure or a tenant complaint.

What it costs

Misaligned objectives

Traditional routines were not designed around what asset managers are judged on today - tenants, sustainability and cost - so they can jeopardise all three at once.

Predictive maintenance

Predictive maintenance is the forecast. Someone still has to do the work.

Predictive maintenance uses live equipment data to anticipate failures before they happen, so plant is serviced on evidence of deteriorating condition rather than on a fixed schedule. It is the forecasting half of data-driven maintenance, and PEAK does it: continuous analysis of BMS, meter and sensor data flags equipment drifting away from expected performance, well before it fails outright.

The half that gets skipped is what happens next. A prediction that nobody is assigned to act on changes nothing about the building.

Prediction only
01
Failure forecast
02
Report issued
03
Nobody assigned

The forecast is right. The equipment still fails on schedule.

CIMData-driven maintenance on PEAK
01
Failure forecast
02
Ranked and assigned
03
Verified fixed

The same data that predicts the failure assigns the work, follows it up and proves it was done. 80% monthly completion standard on P1 and P2 actions.

How PEAK runs it

Every job ends verified, not just predicted

PEAK covers what the industry calls predictive maintenance, and goes further: the same data that predicts a failure also ranks the work, assigns it and proves it was done.

01

Reads your equipment continuously

PEAK connects to your existing BMS, meters and sensors and analyses millions of data points as they arrive - so a dip in performance is visible the day it starts, not at the next scheduled inspection.

Any BMS
02

Predicts what needs attention next

The Rules Engine flags equipment drifting away from expected performance before it fails. Reactive work still happens - but it is triggered by the data, not by a tenant complaint.

Rules Engine
PREDICTIVE MAINTENANCE STOPS HERECIMWhere PEAK keeps going
03

Ranks the work by what it costs you

Every fault is scored on energy cost, comfort impact and equipment risk, so your team and your contractors work the most consequential issues first rather than the next item on a list.

Impact ranking
04

Closes the job out and proves it

Work is assigned to a named person, followed up when it goes overdue, and checked against the equipment data afterwards. If the fix did not hold, PEAK reopens it.

Verified close-out
The four strategies

Reactive, preventive, predictive, data-driven: what triggers the work in each

Four ways to decide what gets maintained. They differ in one respect above all: what triggers the work.

Strategy 1

Reactive

TRIGGERED BY
Something breaks, or a tenant complains
DATA NEEDED
None
WHERE IT FAILS
Budgets are unpredictable and disruption is routine
Strategy 2

Planned preventive

TRIGGERED BY
The calendar
DATA NEEDED
An asset register and a schedule
WHERE IT FAILS
You inspect healthy plant while faults elsewhere run for months
Strategy 3

Predictive

TRIGGERED BY
A forecast that equipment is heading for failure
DATA NEEDED
Live equipment data and fault analytics
WHERE IT FAILS
Predicts well, but nothing guarantees the work gets done
CIMStrategy 4

Data-driven

TRIGGERED BY
Measured condition, ranked by business impact
DATA NEEDED
The same, plus assignment, tracking and verification
WHERE IT FAILS
It doesn't, if the loop is genuinely closed and verified
One record

One record of the work that owner and contractor both trust

Most maintenance reporting comes from the people doing the maintenance. PEAK keeps an independent record - what was raised, who it went to, how long it sat, and whether the equipment actually recovered - so every contract review starts from the same facts.

Performance against KPIs
Contractor performance measured against agreed standards, on data neither party can edit.
Full task oversight
Every assigned task tracked in real time - raised, in progress, overdue, closed.
Verified, not assumed
The equipment data confirms the fix held. Work that didn't land gets reopened.
PEAK contractor performance report against agreed KPIs: four contractors with sites, on-target, overdue and reopened status
What changes

What data-driven maintenance changes

Six places the difference shows up, from what the contract costs to what tenants notice.

Maintenance contracts

Fewer reactive callouts and a tighter focus on real issues change what you are buying - and what it should cost.

Equipment downtime

Continuous monitoring and automated fault detection catch issues before building users feel them.

Equipment life

Timely intervention mitigates wear, so plant runs properly for longer and capital replacement moves out.

Sustainability performance

Better-run equipment uses less electricity, gas and water - feeding ratings, net zero targets and green lease commitments.

Team productivity

Fewer wasted onsite hours, root causes addressed directly, and issues resolved centrally rather than building by building.

Tenant experience

Fewer disruptions and steadier conditions across all zones, because problems are found before they are reported.

The size of the prize

What the evidence says about maintenance

40%

of air handling units are carrying a fault on any given day - which is the work a calendar-based schedule is not looking for.

Source

Lawrence Berkeley National Laboratory, analysis of 60,000+ pieces of HVAC equipment.

5-20%

savings on energy bills from operations and maintenance programmes targeting efficiency, without significant capital investment.

Source

US Department of Energy, Federal Energy Management Program, O&M Best Practices Guide.

80%

monthly completion standard on P1 and P2 actions across PEAK portfolios - the measure most maintenance reporting never states.

Source

CIM operating standard, measured on platform data.

Getting there

How the transition actually happens

This is a contract change as much as a technology change. It runs in three stages, usually across renewal cycles rather than overnight.

01Run alongside

Initial integration

Analytics goes in alongside the existing contract. It adds cost at first, and it produces the evidence of what the building actually needs.

02Renegotiate

Contract evolution

The maintenance contract is rewritten around condition rather than schedule. Analytics moves inside the core contract; routine servicing costs come down.

03Steady state

Mastery and refinement

Condition-based maintenance becomes the operating norm. Backlogs clear, equipment lasts longer, and costs settle lower than where you started.

In our clients' own words

Teams who stopped servicing to a calendar

See all customer stories →
In their own words
QIC logoOwner-operator · Australia

Scheduled maintenance checks are now a thing of the past.

"Scheduled maintenance checks and servicing is now a thing of the past as the data helps us determine precisely when and where maintenance is needed. We can now actively anticipate and prevent equipment breakdowns which means equipment is more likely to last its specified lifespan and we don't have to resort to costly fixes or replacements."

Damien Stacey
National Capital & Planning Manager, QICGRE
Brisbane Airport Corporation logoAirport · Australia

Improving our operations through data-driven decisions.

"Brisbane Airport Corporation was pleased to engage CIM to assist with delivering energy savings, optimising building performance and improving our operations through data-driven decisions."

Ken Hughes
Head of Airport Facilities, Brisbane Airport Corporation
UniversitiesUniversity · Australia

It finds what's broken and guides better maintenance man-hours.

"We want maintenance time to be better spent in a more productive fashion. It's impossible to check every sensor and every actuator every month. We want our BMS and Mech to investigate real alerts. That's where analytics like CIM have helped. It finds what's broken and guides better maintenance man-hours."

Executive Manager
Building Services and Operations, Australian university
How it fits together

Fault detection is the engine. Maintenance is what it drives.

Fault detection and diagnostics sits inside data-driven maintenance. FDD finds and diagnoses what is wrong; data-driven maintenance is the operating model that decides what gets done about it, by whom, and in what order.

The engine

FDD

Reads BMS, meter and sensor data
Diagnoses the probable cause
Ranks faults by impact
Confirms the fix cleared
Evidence
CIMThe operating model

Data-driven maintenance

Decides what gets maintained, when, by whom, and how it is paid for.

Maintenance schedulesCondition-based, not calendar-based
Contracts and scopeAnalytics-driven tasks written into scope
Resourcing and effortWhere the team's hours actually go
KPIs and accountabilityMeasured on resolution and verification

You can have FDD without data-driven maintenance. Most organisations do: the platform runs, the faults are found, and the contract keeps billing for the same calendar inspections.

See how fault detection and diagnostics works →
Who it's for

Two ways teams run data-driven maintenance on PEAK

Owners and operators use PEAK to manage maintenance on evidence. Maintenance and engineering firms use it to cover every point on every contract without adding engineers.

PEAK Enterprise

You own or operate the buildings

Maintenance spend follows equipment condition rather than the calendar. Every job has an owner and a verified close-out, so the maintenance contract is managed on evidence.

PEAK Professional

You maintain buildings for clients

Calendar-driven checks become automated verification of every point, every 15 minutes - closing the gap between what a maintenance standard requires and what a dispatch team can physically cover.

Free guide

Go deeper on data-driven maintenance

Free guide

A Guide to Data-Driven Property Maintenance

The practical playbook for moving a portfolio off calendar-based servicing - and rewriting the contract that goes with it.

What to measure before you renegotiate
How the scope changes, clause by clause
How to hold contractors to the new standard
Download the guideFree. No sales call required.
Compatibility

Works with your existing BMS

Condition-based maintenance starts with the data your building already produces. PEAK reads your system through BACnet/IP, routed BACnet MS/TP, a vendor API or scheduled CSV exports, without a rip-and-replace of your existing controls.

See how PEAK connects to your BMS →
Your BMS
no rip-and-replace
BACnet/IPRouted BACnet MS/TPVendor APIScheduled CSV exports
CIM
PEAK
Maintenance on condition
Running in production with
TrendTridium NiagaraSchneider ElectricHoneywellSiemensJohnson ControlsDistech ControlsDelta ControlsAlertonAutomated Logic
Questions

Data-driven maintenance, explained

Something not covered here? Talk to our team.

What is data-driven maintenance?+

Maintenance decided by the condition of the equipment rather than by a fixed schedule. Live data from plant and equipment determines what needs attention, when, and in what priority order.

How is it different from predictive maintenance?+

Predictive maintenance is the forecasting part - using data to anticipate failure. Data-driven maintenance includes that, and adds the operating model around it: prioritising the work, assigning it, tracking it and verifying the equipment recovered.

Does it replace planned preventive maintenance entirely?+

No. Statutory and safety-critical servicing still runs to schedule. What changes is the discretionary work: routine checks on equipment that is running well get replaced by attention to equipment that is not.

What happens to our existing maintenance contract?+

It typically changes at renewal rather than immediately. Analytics runs alongside the current contract first, then the scope is renegotiated once there is evidence of what the building actually needs.

Do we need new sensors?+

Usually not. Most buildings already produce far more data than anyone reads. PEAK is BMS-agnostic and works with the meters, sensors and equipment feeds already in place.

How does it hold contractors accountable?+

Every raised issue is tracked from detection to close-out on data neither party can edit, and the equipment data confirms whether the fix held. Performance is measured against agreed KPIs rather than self-reported completion.

Can maintenance contractors run data-driven maintenance on PEAK?+

Yes. PEAK Professional is built for maintenance, engineering and FM firms that look after buildings for clients. Calendar-driven checks become automated verification of every point, every 15 minutes, and the verified record of what was fixed goes straight into client reporting.