Building Management System (BMS) — The Backbone of Proactive Maintenance

Most of the failures that shut down an office building are not truly surprises — they send early signals weeks and months before the failure. A chiller whose current draw slowly climbs, a pump that starts to vibrate, an electrical panel that heats up in one corner, a clogged filter with a gradually rising pressure differential above it. The problem is not that there are no signals — the problem is that no one is listening to them. A building without managed monitoring is effectively "in the dark": the building manager learns of a fault only once it has already shut down a system, taken out a floor, or burned out equipment. A building management system — BMS — is the tool that turns these weak signals into visible data, and reactive management into proactive management.

What a BMS actually is — and why it is not "just another gadget"

A Building Management System (sometimes BAS — Building Automation System) is a computerized control system that connects all of a building's systems to a single computer that monitors and controls them. Instead of every system working separately — the HVAC with its own controller, the electrical with its own panel, the fire detection with its own control unit — the BMS unifies them all into a single operational picture.

In practice this means: the controller reads sensors deployed throughout the building — temperature, pressure, flow, current draw, motor status, valve status — displays the situation in real time, starts and stops equipment according to schedules and conditions, and alerts when something deviates from the norm. All of this happens continuously, 24 hours a day, without a person needing to stand in front of the equipment.

It is important to understand what a BMS is not: it does not replace statutory inspections and it does not replace the technician on site. It does not "fix" anything. What it does is give the building continuous eyes and ears — something no building manager and no maintenance team can do manually. This is the critical distinction: a BMS is not a technological luxury, it is the information infrastructure on which real preventive maintenance rests.

What a BMS actually monitors and controls

The scope of coverage varies from building to building and depends on how many sensors and controllers have been installed, but in a well-managed office tower the BMS touches almost every core system:

• Air conditioning (HVAC): chillers, cooling towers, chilled-water pumps, air handling units (AHU), fans and terminal units. The BMS controls the target temperature, schedules start-up and shutdown by occupancy hours, and monitors pressures, temperatures and current draw.
• Electrical and energy: consumption monitoring at the main-panel level, detection of abnormal loads and unbalanced load across phases, tracking of feed and backup status. Integration with the generator and UPS to know immediately about a switch to backup.
• Lighting: scheduling of common-area, corridor and parking lighting by hours and by presence, saving on consumption and alerting on failures.
• Water and plumbing: monitoring of pressure-boosting pumps, water reservoirs and network pressures. In buildings with suitable sensors — also leak detection based on abnormal consumption between two readings.
• Fire detection and safety: the fire detection and suppression system always operates as an independent system for safety and regulatory reasons — but the BMS receives a status indication from it, so the building manager sees the fire system status on a single screen as well.
• Elevators and additional systems: status and fault indication — an entrapment, a shutdown for maintenance, or a communication fault appear in the system immediately and are not "discovered" only when a tenant is trapped.

The value is not in any single component — it is in the unification. When all systems report to one place, the building manager sees the building as a single living system, not as twenty disconnected islands each requiring someone to stand in front of it.

How it talks — BACnet, Modbus and why the protocol is a business question

For systems from different manufacturers to be able to "talk" to the BMS, a common language is needed — a communication protocol. The two most common in the building control world are:

• BACnet — a protocol developed specifically for building automation (the ASHRAE 135 standard). Very common in HVAC controllers, AHUs and chillers. It defines not only the communication protocol but also the data objects (temperature, scheduling, alarm) — so systems from different manufacturers speak "the same language" at a logical level.
• Modbus — a veteran, simple protocol, developed in the 1970s for industry. Common in electrical equipment, energy meters, industrial controllers and pumps. It is less rich than BACnet but is supported by almost every piece of equipment on the market.

A good BMS knows how to communicate over several protocols in parallel and unify them all into a single interface. There are also additional protocols such as KNX (common in lighting and in new buildings) and LonWorks, as well as integrations via API to the cloud.

Why does this matter to a building manager who is not an engineer? Because it determines whether the building is "locked in" with a single vendor. A system built on open, standard protocols allows adding equipment from different manufacturers, replacing a service provider, and expanding the system over the years. A closed, proprietary system, by contrast, may tie you to a single vendor for the entire life of the building — with corresponding price and service implications. When building or upgrading a BMS, the question "which protocols does it work on" is a first-order operational and commercial question, not merely a technical one.

The heart of the matter — how an alert catches a failure before it happens

This is the real reason a BMS changes the rules of the game. Without monitoring, you discover the chiller has burned out when the floor heats up and the phone calls begin. With monitoring, you see the story unfolding well before that.

Here are four real scenarios, of the kind a building manager encounters in the field:

• A weakening chiller: the compressor's current draw climbs gradually over weeks, or the temperature difference between inlet and outlet narrows — a sign that the refrigerant is "weakening." The BMS sees the trend and alerts, and a technician checks the refrigerant charge or the compressor before the chiller collapses in the middle of a heat wave.
• A pump before failure: a rise in current draw, a drop in flow pressure, or repeated and too-frequent starts — all indicate bearing wear, partial blockage, or mechanical drag. An early alert allows a planned replacement to be scheduled and a spare part chosen in advance, instead of a sudden shutdown of the water system at a moment of pressure.
• An overheating electrical panel: a temperature sensor in the panel enclosure, or an abnormal current draw on one phase, can indicate a loose connection or an unbalanced load — exactly the conditions that precede a panel fire. Early detection here is not only a saving — it is fire safety.
• A clogged filter: a rise in the pressure differential across a filter in an air handling unit (AHU) means the filter is full. Instead of replacing on a rigid calendar ("every three months"), you replace exactly when needed — and also save energy, since a fan pushing through a clogged filter consumes significantly more electricity.

The difference between an alert and a trend is critical. An alert is a point in time — a value has just crossed a threshold. A trend is the history — the BMS records data over time, and thus a slow degradation that no single reading would have revealed becomes visible. It is precisely the trends, not the immediate alerts, that turn maintenance predictive: you don't wait for the threshold to be crossed, you see that it is about to be crossed and head off the problem before it becomes a crisis.

From "in the dark" to open eyes — what the difference is in practice

Picture two identical office buildings, two building managers with the same budget. In the first there is no monitoring: when the chiller burns out on Friday evening, no one knows until Sunday morning, when the tenants arrive to hot floors. The repair is an emergency — spare parts urgently, a technician at a weekend rate, furious tenants demanding a rent discount, and damage to the property's reputation. In the second there is a BMS: two weeks earlier a trend alert appeared about rising compressor current, a planned service call was opened, the problem was handled during regular working hours with a spare part ordered in advance, and none of the tenants ever knew that something had almost happened.

This is the difference between reactive management and proactive management, and it is not a matter of luck but of information. A building without monitoring is not "a building where no faults have occurred" — it is a building where faults simply have not yet been discovered. The larger and more complex the building, the larger the gap between the two approaches, and the greater the danger that a silent fault will become an expensive crisis.

From direct experience working with buildings in Israel: buildings whose transition from reactive management to data-based management is carried out systematically experience a significant drop in emergency calls and in dealing with unplanned shutdowns. The parameter that changes the most is not the quality of the monitoring equipment — but whether there is a clear process of who sees the alerts and who acts on them.

The critical connection — BMS meets CMMS

Here lies the gap that many miss. A BMS alone only alerts — it tells you that something is wrong. But an alert that no one handles is just another beep that gets ignored. The full value is created when the BMS data connects to a maintenance management system — CMMS (Computerized Maintenance Management System) — which turns an alert into a task, a task into a service call, and a call into closed documentation.

This is what the full chain looks like:

1. The BMS identifies a deviation or an abnormal trend.
2. A service call is opened — automatically or manually — in the CMMS.
3. The call is routed to the right technician with the full history of that equipment.
4. The treatment is documented, including the finding and the solution.
5. The historical data joins the equipment file and serves as a basis for planning ahead.

In parallel, the CMMS manages planned preventive maintenance (PPM) — the periodic inspections that do not depend on an alert but on a schedule — and the BMS feeds it real data that allows the frequencies to be tuned. Instead of replacing a filter every three months "because that's what it says," you replace according to the actual pressure differential; instead of lubricating a pump by the calendar, you see when the vibration level starts to rise.

This is the shift from time-based maintenance to condition-based maintenance, and it is the heart of the message. The BMS is the sense of touch, the CMMS is the memory and the discipline. Without the CMMS, the BMS is an alarm screaming into an empty space. Without the BMS, the CMMS works blind and relies only on the calendar. Together they turn the building into a system that is managed proactively rather than reactively. We expanded on this principle in the annual preventive maintenance checklist.

Energy savings — not just alerts

Beyond preventing faults, a BMS is one of the most powerful tools for saving on energy consumption — which in an Israeli office building is a huge share of operating expenses, led by the air conditioning system.

The BMS saves energy through several parallel routes:

• Smart scheduling: it shuts off air conditioning and lighting in unoccupied areas and during empty hours, instead of running everything around the clock. A building that starts doing this systematically sees a noticeable difference in the electricity bill — without harming occupant comfort.
• Coordination between units: it prevents situations in which a heating unit and a cooling unit work together, or a fan pushes already-conditioned air again.
• Waste detection: a clogged filter that burdens a fan, a unit operating outside its efficient range, or equipment that stays "awake" even during empty hours — all become visible in the data.
• Load-based optimization: a modern air conditioning system with variable-frequency drives (VFD) managed by a BMS can adapt the motor power to the instantaneous load, which saves significantly compared with a motor running at a fixed output.

The beauty is that energy savings and equipment protection go hand in hand: equipment that operates fewer hours and under the right conditions wears out more slowly and lasts many more years. Thus the same investment in a BMS pays for itself through three channels simultaneously — lower energy bills, fewer emergency faults, and a longer asset life for the building's most expensive systems.

For depth on energy audits — which are the starting point for any efficiency effort — see energy audit for an office building.

BMS by system — where it matters most

Air conditioning

This is the heart of most BMS systems, and rightly so: air conditioning is the largest energy consumer in an Israeli office building, and the system with the most mechanical components that wear out. Monitoring chillers, pumps and cooling towers is precisely where predictive maintenance saves buildings from expensive shutdowns — mainly during the harsh heat waves of the Israeli summer, which are the time when cooling demand peaks and the failure of a central chiller hits the entire building at once. We expanded on maintaining the system itself in HVAC maintenance in office buildings.

Electrical systems

Consumption monitoring at the panel level, detection of unbalanced loads across phases, and tracking of connection temperatures — all of these catch problems that could lead to an electrical failure or a panel fire. A building with a BMS monitoring its electrical panels gains a protective layer that is not part of the periodic statutory inspections. We covered the maintenance principles of the system itself in electrical systems maintenance in an office building.

Fire safety

For safety and regulatory reasons, the fire detection and suppression system always operates as an independent system and does not depend on the BMS for its operation — so even if the BMS fails, the fire system continues to function. But the BMS receives a status indication from it, so the building manager sees a fault in the fire system on a single screen and can respond immediately.

Water and plumbing

Monitoring pressure-boosting pumps is especially vital in tall buildings where a pump failure could cut off entire floors from water. In addition, monitoring water consumption allows internal leaks to be detected early — before the damage reaches the surface.

How not to buy a "white elephant" — common mistakes

A BMS is a powerful tool, but many buildings install an expensive system and then... don't use it properly. Some of the common traps worth avoiding:

• A system with no one watching it: a BMS that alerts and no one listens is worthless. A clear process is needed — who sees the alerts, who routes them for handling, and who closes and documents them. Without such a process, the alerts pile up and get ignored.
• Disconnection from the CMMS: when alerts don't turn into documented service calls, they are forgotten. The connection to maintenance is what realizes the investment — without it, the BMS is a "dashboard that no one acted on."
• Lock-in to a single vendor: a closed, proprietary system that ties you to one vendor for the entire life of the building — with dependence on it for every upgrade, addition and treatment. It is better to demand open, standard protocols even if the initial price is slightly higher.
• "Alert flooding": a system configured too broadly generates dozens and hundreds of false alerts a day, and the team learns to ignore them — exactly like false alarms in fire detection. Proper calibration of the thresholds after a familiarization period is critical; poor calibration is worse than no system at all.
• Investment without maintenance for the system itself: the BMS and its sensors also need maintenance. A sensor that has lost calibration gives a wrong reading — and that may be worse than the absence of data, because the building manager decides based on incorrect information.
• Partial coverage without a boundary map: if a BMS covers only part of the systems, it is important to know exactly what is not covered — so as not to think that silence is a sign of soundness. What is not monitored is not "sound," it is simply not visible.

Israeli Standard 1525 and the BMS — two complementary layers

It is important to see where the BMS fits into the regulatory picture. Israeli Standard 1525 defines a framework for planned preventive maintenance — a plan, a log and periodic inspections for various types of equipment. The BMS does not replace the standard: the statutory and functional inspections must be carried out in the field by qualified parties, and the documentation is required as required.

But the BMS upgrades compliance with the standard in two respects:

• Calibrating the inspection schedule: the BMS provides real data on the condition of the equipment — so the inspection frequency can be adapted to the actual condition rather than adhering to a generic schedule that does not take the specific building's conditions into account.
• Continuous monitoring between inspections: the BMS adds a layer of tracking between the periodic visits — and it is precisely in the interval between two inspections that most failures develop. Thus the building is protected even at the moments when there is no technician in front of the equipment.

The question "does the BMS comply with the standard" is not the right question. The right question is: "do the two layers — the continuous monitoring of the BMS and the periodic inspections under Standard 1525 — work together?"

A BMS for a small building — is it worth it?

A question that often comes up: is a full BMS justified even in a mid-size building that is not a tower? The answer depends on the critical equipment in it. A building with a central chiller, pressure-boosting pumps, and main electrical panels — all equipment whose failure affects all the tenants — justifies monitoring even if it is "only" five stories.

The practical approach for a small building: you don't necessarily start with a comprehensive BMS. You can start with focused monitoring of the critical systems — current sensors on the pumps and chiller, a temperature sensor in the main panel, and a load meter on the generator — and expand gradually. IoT sensor technology has made this possible even without installing a full classic BMS. We expanded on this approach in IoT sensors in buildings.

Bottom line — stop being surprised

If there is one message to take from this guide, it is this: a building without monitoring is not a safer building — it is a building where you simply do not know what is happening. Every fault that ever paralyzed a system sent early signals, and the BMS is the tool that listens to them for you, 24 hours a day, across all systems at once.

Combined with a CMMS that translates the alerts into documented tasks, you move from "putting out fires" to "preventing them" — and that is the difference between a building manager who runs after faults and a manager who leads the building with a steady hand.

This transition does not require replacing everything in a single day. You can start with monitoring the critical systems — air conditioning and electrical — and expand gradually. The main thing is the principle: stop managing in the dark, and start seeing.

At Domera we connect the building's monitoring data to a documented preventive maintenance plan, so that every alert becomes a treatment closed on time. For more information see comprehensive property management, or get a quote for a review of the monitoring status of your property.