BluSENSE Resources
What Is Building Monitoring?
Buildings consume energy, water, and resources constantly — whether anyone is paying attention or not. Building monitoring is the practice of paying attention, systematically, using sensors and data.
A plain-language guide to what building monitoring is, what it isn't, and why it matters.
Talk to an ExpertBuildings consume energy, water, and resources constantly — heating, cooling, pumping, lighting — whether anyone is paying attention or not. Building monitoring is simply the practice of paying attention, systematically, using sensors and data.
That's the short version. The longer version is a bit more nuanced, and worth understanding — because "building monitoring" is a term that gets used to describe everything from a single temperature sensor in a server room to a fully instrumented campus measuring dozens of systems simultaneously. Knowing what it actually means helps you figure out what you actually need.
What building monitoring does
At its core, building monitoring measures physical conditions — temperature, pressure, flow, power consumption, water usage — at specific points in a building, at regular intervals, over time. Those measurements are recorded and stored so that you can look at them, analyze them, and draw conclusions from them.
The key phrase is "over time." A single reading tells you what's happening right now. A series of readings tells you what's normal, what's changing, and when something is going wrong. That's the difference between a snapshot and a story.
What you do with those readings depends entirely on what you're trying to understand. Building monitoring is a tool, not an outcome — and like any tool, its value depends on how it's applied.
What can be monitored
Almost any physical system in a building can be monitored if you have the right sensor for it. In practice, the most common things people monitor fall into a few broad categories:
Energy consumption — electricity, gas, or other fuels, typically measured at the meter or at individual pieces of equipment using current transformers or pulse inputs from existing meters.
Water consumption and flow — how much water is being used, where, and at what rate. This is especially useful for hot water systems, irrigation, and leak detection.
Temperature — ambient air temperature in spaces or mechanical rooms, fluid temperature in pipes and tanks, surface temperature on equipment. One of the most versatile measurements in building science.
Pressure — water pressure in distribution systems, differential pressure across filters or heat exchangers, air pressure in HVAC systems.
Equipment status — whether a pump, fan, boiler, or other piece of equipment is running, and for how long. Often captured via pulse outputs or current transformers rather than direct communication with the equipment.
These categories often overlap. Understanding hot water system performance, for example, typically requires temperature, flow, and equipment status data together — each measurement on its own tells only part of the story.
What building monitoring is not
It's worth being clear about a few things building monitoring doesn't do on its own.
Monitoring is not control. A monitoring system observes and records — it doesn't adjust setpoints, switch equipment on or off, or respond to conditions automatically. That's the domain of building automation systems (BAS) and control systems, which are a separate category entirely.
Monitoring is not analysis. The data a monitoring system produces is raw material. Turning it into insight — identifying a pattern, diagnosing a fault, validating a savings claim — requires someone to look at it thoughtfully. Good monitoring makes that analysis easier. It doesn't replace it.
And monitoring is not a guarantee of action. This one is important. Many buildings have monitoring equipment installed that nobody looks at regularly. Data accumulates, problems go unnoticed, and the investment delivers nothing. Monitoring only creates value when the data is used.
Who uses building monitoring, and why
Building monitoring is used across a wide range of industries and roles, often for quite different purposes. A few examples:
Use monitoring to establish baselines before a retrofit and verify measured savings afterward. Continuous data is often required to meet IPMVP protocols for measurement and verification.
Use monitoring to track utility consumption across a portfolio, identify unusual spikes that may indicate leaks or equipment faults, and produce data for tenant billing or sustainability reporting.
Use monitoring to validate that newly installed equipment is performing as specified, and to diagnose problems in existing systems without repeated site visits.
Use monitoring to maintain compliance with water safety regulations — particularly around hot water temperature for Legionella risk management — where consistent records are a regulatory requirement.
What these use cases have in common is a need for reliable, timestamped data over time. The specific sensors, hardware, and analysis methods differ — but the underlying discipline is the same.
What makes a monitoring system good
Not all monitoring systems are created equal. A few characteristics separate systems that deliver real value from those that look good on paper but fall short in practice.
Data integrity. If a monitoring system loses data — because a connection dropped, a battery died, or a device restarted — that gap can undermine the entire purpose of monitoring. A system built for reliability records locally, backs up to the cloud, and uses battery power to bridge connectivity outages. No gaps means no excuses.
Resolution. How often is data being recorded? A reading every 15 minutes might be sufficient for monthly utility reporting. It's completely inadequate for diagnosing an HVAC fault that happens for 90 seconds every morning. The right resolution depends on what you're monitoring and why — but more granular is almost always more useful than less.
Sensor compatibility. Buildings contain an enormous variety of systems using an enormous variety of communication protocols. A monitoring system that only speaks one protocol will leave whole categories of equipment invisible. Flexibility — support for 1-Wire, Modbus, 4-20mA, pulse inputs, current transformers — is what allows a single system to monitor the full picture of a building.
Accessible data. Data that requires specialized software to access, or that lives only on a device in a mechanical room, is data that doesn't get used. The most useful monitoring systems deliver data proactively — to email, to a dashboard, to a format that the people who need it can actually work with.
A useful way to think about it
If you're new to building monitoring, here's a framing that tends to help: think of it as giving a building a memory.
Without monitoring, a building has no record of what it's done. Equipment runs or doesn't run, water flows or doesn't flow, energy is consumed or isn't consumed — and all of it disappears the moment it happens. When something goes wrong, you're working from guesswork and gut feel. When something improves, you can't prove it.
With monitoring, a building accumulates a continuous record of its own behavior. That record becomes the basis for every intelligent decision you make about the building — maintenance, upgrades, reporting, compliance, cost management. The longer it runs, the more valuable it gets.
That's worth setting up correctly from the start. Which is why the next question — once you understand what building monitoring is — is how to approach it for your specific building and goals.
That's covered in our guide: Building Monitoring: Where to Start →