Every building with a BMS has a maintenance contract — or at least, it should. The reality is that most facilities managers inherit a contract they didn't write, with a provider they didn't choose, covering a scope that nobody has reviewed since it was first signed. And when something goes wrong — a chiller locks out on a Friday afternoon in August, or an AHU is running full-speed supply into an empty building at 3am — that's when the gaps in the contract become painfully visible.
The problem isn't that BMS maintenance contracts are inherently bad. It's that most of them are written to protect the provider, not the building. Understanding the difference between a contract that actually maintains your system and one that just generates quarterly invoices is one of the most commercially important decisions an FM team or building owner can make.
At its core, a BMS maintenance contract should provide planned preventative maintenance (PPM), reactive fault response, software and firmware management, and a clear route to system support when things go wrong. That sounds straightforward, but the detail matters enormously.
Planned preventative maintenance for a building management system isn't the same as PPM on a boiler or an AHU. BMS PPM should include controller health checks, sensor calibration verification, network communication audits, alarm configuration reviews, trend log analysis, and time schedule validation. If your contract just says "quarterly BMS inspection" without defining what that inspection actually involves, you're paying for someone to walk around with a clipboard and confirm the supervisor screen is still on. That's not maintenance — that's attendance.
SFG20, the industry-standard maintenance specification for building services, provides detailed task schedules for BMS equipment maintenance. SFG20 sets out specific inspection frequencies, test procedures, and documentation requirements for building control systems — including controller diagnostics, sensor accuracy checks, actuator stroke testing, and software backup verification. If your maintenance provider can't tell you how their PPM schedule maps to SFG20 task specifications, that's a question worth asking. A contract aligned with SFG20 gives you an auditable, defensible maintenance regime rather than one built on whatever the provider feels like doing on the day.
The response SLA is where most BMS maintenance contracts either prove their worth or expose their limitations. A typical contract will specify a response time — often four hours during business hours, next business day otherwise. But there's a critical difference between "response" and "resolution" that many contracts deliberately blur.
Response means acknowledgement. It means someone has read the email or answered the phone. Resolution means the fault is fixed, the plant is running, the building is comfortable. A contract that guarantees a four-hour response but says nothing about resolution timescales, escalation procedures, or what happens when the first engineer can't fix the problem on site is a contract designed to look good on paper while delivering very little under pressure.
What you want to see is a tiered SLA structure: critical faults (total loss of control, fire system interface failures, plant safety issues) with a defined attendance time — typically two to four hours including out-of-hours. High-priority faults (zone failures, persistent comfort complaints, communication losses) with a defined response and an expected resolution window. And standard faults (cosmetic issues, non-critical alarm configuration, graphics amendments) handled within an agreed timeframe that doesn't consume emergency resource.
CIBSE Guide H: Building Control Systems sets out that a properly specified BMS should include defined maintenance and support arrangements as part of the overall system design. Guide H emphasises that the criticality classification of controlled plant should directly inform the response and restoration requirements in any maintenance agreement — a chiller serving a data hall and an FCU serving a rarely-used meeting room should not carry the same SLA priority, and any contract that treats them identically hasn't been written with the building in mind.
Any BMS maintenance contract written after 2020 that doesn't include remote monitoring capability is, frankly, behind the curve. Remote access to the BMS supervisor is no longer a premium feature — it's a basic requirement for efficient fault diagnosis, alarm management, and proactive maintenance.
Remote monitoring means your maintenance provider can see what the BMS is doing without sending an engineer to site. That's not just a cost saving on callouts — it fundamentally changes the quality of the service. A provider with remote access can identify sensor drift before it causes comfort complaints. They can verify that time schedules are running correctly after a clock change. They can diagnose a communication fault between a controller and the supervisor in minutes rather than the hours it would take to get someone on site, into the building, and in front of the panel.
What you should be looking for in the contract is clarity on what remote monitoring actually includes. Is it 24/7 alarm monitoring with defined responses, or is it just remote access that the provider uses when they happen to think of it? Are trend logs being reviewed proactively, or only pulled after a complaint? Is there a monthly or quarterly remote monitoring report that tells you what was observed, what was actioned, and what needs attention? The difference between these two approaches is the difference between a reactive maintenance contract and a genuinely proactive one.
Buildings that have moved to a proper remote monitoring model — and we've implemented this across a number of sites including the Pinsent Masons project — consistently see reduced reactive callout volumes, faster fault resolution times, and better energy performance. It's not magic. It's just what happens when someone is actually watching the data.
Spare parts are one of the most common sources of dispute and surprise cost in BMS maintenance contracts. The question every FM team should be asking is simple: when a controller, sensor, actuator, or network switch fails, who pays for the replacement part, and how quickly can it be sourced?
Some contracts include parts within the annual fee — typically for like-for-like replacements of standard components. Others cover labour but exclude parts entirely, meaning every hardware failure generates a separate purchase order and potentially weeks of delay while procurement processes grind through. Neither approach is inherently wrong, but you need to know which one you've signed up to.
The more important question is whether your maintenance provider holds strategic spares for your site. For buildings running Trend IQ4 controllers, Distech ECLYPSE units, or any other specific platform, having a small stock of spare controllers, common sensor types, and critical network components either held on site or readily available from the provider's stores can be the difference between a same-day repair and a two-week wait for a factory order.
If your building is running end-of-life equipment — and plenty still are, as we've covered in our guide to Trend IQ3 obsolescence — the spare parts situation becomes critical. A good maintenance contract for a legacy system should explicitly address parts sourcing strategy, including what happens when components are no longer available through normal channels. If the contract is silent on this, you're exposed.
Having worked across hundreds of BMS maintenance contracts — both inheriting other providers' arrangements and writing our own — the pattern of what goes wrong is remarkably consistent.
The first red flag is a contract that's been rolled over annually without review. Building services change. Tenants change. Plant gets replaced. Extensions get built. If the maintenance scope hasn't been updated to reflect the current state of the building, the provider is maintaining a system that no longer exists as described, and neither party has a clear understanding of what's actually covered.
The second is a provider who doesn't hold — or can't demonstrate — relevant accreditations and competencies for the specific BMS platform installed. Trend systems require Trend-accredited engineers. Distech systems require trained Niagara/ECLYPSE engineers. A general M&E maintenance contractor whose BMS capability is "we've got a bloke who can look at it" is not the same as a specialist controls contractor with manufacturer-backed training and access to technical support channels. The quality difference shows up in every callout.
The third red flag is the absence of any reporting. A maintenance provider should be producing documentation after every visit — what was checked, what was found, what was actioned, what's outstanding. If your provider isn't generating this paperwork, you have no audit trail, no evidence of compliance with SFG20 task requirements, and no basis for holding them accountable when something falls through the cracks.
The fourth, and perhaps most commercially damaging, is a contract that locks you in with punitive exit terms but doesn't commit the provider to any measurable performance standard. If the provider can underperform for years with no consequence while you can't leave without a six-month notice period and a termination fee, the contract has been written entirely in their favour.
BMS maintenance isn't just about comfort and energy — there are genuine compliance obligations that a maintenance contract needs to address.
Approved Document L of the Building Regulations sets energy efficiency requirements for buildings, including specific expectations around controls. Part L requires that building services are maintained so as to continue to meet the energy efficiency standards they were designed to deliver. A BMS that was commissioned to provide optimum start/stop, weather compensation, and demand-controlled ventilation but has drifted out of calibration or had its schedules overridden is technically non-compliant with Part L. Your maintenance contract should explicitly include verification of these control strategies as part of the PPM scope.
For buildings with BREEAM certification, the ongoing performance of the BMS is a factor in maintaining credits under the Management category. BREEAM requires evidence of building tuning and seasonal commissioning — both of which depend on a functioning, properly maintained BMS and a provider who understands what the certification demands.
The MEES regulations are tightening. Commercial properties need to reach EPC Band B by 2030. Controls are a core component of the EPC calculation methodology, and a BMS that isn't delivering its designed energy performance because maintenance has been neglected will directly affect the building's rating. If you're unclear on how your BMS connects to your overall building controls strategy, it's worth understanding that relationship before your next EPC assessment.
A well-structured BMS maintenance contract should be clear on scope, honest about limitations, and measurable in its outcomes. Here's what that means in practice.
The scope should list every controller, every outstation, every supervisor, every network switch, and every integrated third-party device. If it's connected to the BMS, it should be named in the schedule. The PPM tasks should be defined against SFG20 or an equivalent auditable standard, with visit frequencies that match the building's operational profile — a 24/7 data centre needs a different PPM rhythm than a Monday-to-Friday office.
Response SLAs should be tiered by criticality, with attendance and resolution targets for each tier. Out-of-hours cover should be explicitly defined — is it included, or is it charged separately? If separately, at what rate? These are the questions that matter at 2am when the heating plant has tripped and the building needs to be warm by 7am.
Remote monitoring should be included as standard, with a defined reporting cadence and clear accountability for what gets actioned from the data. Spare parts arrangements should be stated — included, excluded, or a hybrid model. And the contract should include an annual review mechanism where both parties sit down, assess the system's condition, review the year's performance data, and adjust the scope if the building has changed.
The contract should also include provision for a proper BMS recommissioning at agreed intervals — seasonal commissioning is where many of the most impactful energy savings are found, and it's the first thing that gets cut when a provider is trying to deliver a contract cheaply.
If you haven't reviewed your BMS maintenance contract in the last two years, now is the time. If you've had persistent comfort complaints, unexplained energy bill increases, or a growing volume of reactive callouts, the contract is a good place to start looking for answers.
The strongest position for any FM team or building owner is to commission an independent BMS audit before entering into or renewing a maintenance contract. That audit gives you an accurate picture of the system's current condition, the hardware inventory, the outstanding faults, and the areas where maintenance has been lacking — and it gives you the information you need to hold any provider to a meaningful standard.
If your current contract is coming up for renewal and you want to understand what a properly structured BMS maintenance arrangement should look like for your building, get in touch with the team or request a quote. We'll assess the existing system and put together a proposal that's built around the building, not around a template.
A comprehensive BMS PPM contract should cover controller health checks, sensor calibration verification, actuator testing, network communication audits, alarm configuration reviews, time schedule validation, trend log analysis, firmware and software backup verification, and supervisor system health checks. These tasks should be defined against a recognised standard such as SFG20, with documented frequencies and outputs. If your contract just says "quarterly BMS visit" without defining the scope of each visit, you don't have a PPM contract — you have a retainer for someone to turn up.
Most commercial BMS installations should receive a minimum of four PPM visits per year — quarterly — with additional seasonal commissioning visits in spring and autumn to adjust control strategies for heating and cooling changeover. Critical environments such as data centres, hospitals, and laboratories may require monthly or even more frequent maintenance visits. The frequency should be driven by the building's operational profile and the criticality of the controlled plant, not by a one-size-fits-all schedule.
An FM contract typically covers the broad spectrum of building maintenance — cleaning, security, M&E maintenance across all plant, and sometimes soft services. A BMS maintenance contract is a specialist sub-discipline focused specifically on the building controls infrastructure: controllers, sensors, actuators, software, network, and supervisor systems. Many FM providers subcontract BMS maintenance to specialist controls contractors because it requires platform-specific expertise — Trend, Distech, Siemens, Schneider — that general M&E engineers don't carry. If your FM provider claims to cover BMS maintenance in-house, check whether their engineers hold the relevant manufacturer accreditations for the platform installed in your building.
You can, subject to the notice period and termination terms in your existing contract. The key practical consideration is documentation handover. Your outgoing provider should supply all controller configurations, supervisor backups, network diagrams, alarm schedules, trend log archives, and any site-specific knowledge accumulated during the contract. BSRIA BG 11/2010 (Soft Landings) establishes the principle that system documentation should be maintained and transferable — if your provider can't hand over a complete documentation pack, that tells you something about how the contract was being delivered. Insist on a documented handover as a condition of the transition.
Our team of building automation specialists is ready to help you optimise your building's performance and efficiency.
Get in Touch
