Building Monitoring:
Where to Start

There's a common mistake that even experienced building professionals make when they decide to add monitoring to a facility: they start by selecting hardware.

It's understandable. You've heard about a monitoring device, or a colleague recommended one, or you've seen a product that looks like it solves your problem. So you buy it, deploy it, and start collecting data. Then, somewhere along the way, you realize the data you're getting isn't quite answering the questions you actually had. Or worse — you're generating plenty of data, but you're not sure what to do with it.

The hardware wasn't wrong. The sequence was.

Start with the question, not the equipment

Effective building monitoring begins not with a device, but with a question. What do you actually want to understand about this building?

That question sounds simple, but answering it properly takes some thought. "I want to monitor energy use" is a starting point, not an answer. Do you want to understand total consumption, or consumption by system? Do you need to identify which equipment is driving demand peaks? Are you trying to validate savings from a recent retrofit, or establish a baseline for a future one? Are you satisfying a compliance requirement, or making an operational decision?

From understanding to measurement

Once you know what you want to understand, the next question is: what do you need to measure to get there?

This is where the relationship between your goals and your sensors becomes clear. If you want to understand hot water energy consumption at the unit level, you need flow and temperature sensors at each distribution point — not just a single meter at the plant. If you want to validate HVAC performance, you need pressure and temperature data at multiple points in the system, not just a reading at the air handler.

Sensors are not interchangeable. Different physical phenomena require different measurement technologies. Flow measurement alone has multiple approaches — electromagnetic, ultrasonic, paddle wheel, differential pressure — each suited to different pipe sizes, fluid types, flow ranges, and installation constraints. Choosing the wrong sensor type doesn't just produce inaccurate data; in some cases it produces no useful data at all.

This is why sensor selection is its own discipline. Getting it right requires understanding not just what you want to measure, but the physical environment you're measuring it in.

From measurement to data acquisition

Only once you know what you need to measure — and have selected the sensors that can measure it — does it make sense to select your data acquisition hardware.

This is the step most people start with. But data acquisition hardware is, at its core, a collection of inputs. Its job is to accept signals from sensors and record them accurately, with precise timestamps, at the resolution you need. The right hardware for your deployment depends entirely on what sensors you've selected and how many you need to connect.

BluSENSE hardware is designed with this in mind. BluNODE supports a wide range of sensor protocols — 1-Wire temperature, RS-485/Modbus, 4-20mA analog, pulse inputs, and current transformers — precisely because the sensors you need will vary by application. BluCORE brings edge computing, storage, and connectivity to that sensor network. And BluPULSE, with two pulse and two temperature inputs, enables monitoring of hot and cold water fixtures, water heater performance, and can be attached to existing metering infrastructure without requiring replacement. BluPULSE is optimized for battery usage and can operate for well over a year on a single charge or battery replacement.

From data acquisition to data delivery

Once your hardware is capturing data, the next question is: how does it get to you?

This step is easy to overlook during the planning phase, but it's where many deployments fall short. Data sitting on a local device is only useful if someone can access it — reliably, consistently, and in a format they can actually work with.

There are several layers to consider. How is data transmitted from the device — over Wi-Fi, cellular, or another network? Where is it stored, and what happens if connectivity is interrupted? How often do you need access to it, and in what form — a live dashboard, a periodic report, a raw data export?

BluCORE addresses this directly. It supports Wi-Fi, Bluetooth, LoRa, cellular, and satellite connectivity, with local edge storage and cloud backup running simultaneously — so data is never lost even if a connection drops. Every day, BluCORE delivers the complete data load by email, giving you an audit-ready record without requiring you to log into a dashboard. For teams that want live visibility, a browser-based and cloud dashboard is also available, compatible with AWS, Azure, and Home Assistant.

The role of expertise

Following this sequence — goal → measurement → sensor selection → hardware → data delivery → system analysis — is straightforward in principle. In practice, it requires expertise at each step.

Knowing which questions to ask about a building requires building science knowledge. Knowing which sensors are appropriate for a given measurement requires instrumentation experience. Knowing how to configure a data acquisition system to capture what you need requires technical deployment skill.

This is why BluSENSE offers project support — not as an add-on, but as a recognition that hardware alone doesn't deliver outcomes. The Starter support plan is specifically designed for the sensor selection and hardware design phase: before anything is purchased or installed, our team works through the process with you to make sure the system you deploy answers the questions you started with.

From data delivery to system analysis

Receiving your data is not the end of the process — it's the beginning of the work the data was always meant to do.

System analysis is where you return to the question you started with. Is your hot water system performing as expected? Are there consumption patterns that indicate equipment degradation? Is your HVAC delivering the efficiency your retrofit was designed to achieve? The data you've collected is only valuable if you're asking it the right questions.

BluCORE supports this directly. Onboard analysis capabilities include trend visualization, anomaly flagging, and consumption summaries — giving you the tools to identify patterns, spot deviations from expected performance, and track system behavior over time. Combined with daily data delivery and dashboard access, this means your monitoring system isn't just recording what's happening in your building: it's helping you understand it.

A practical summary

If you're approaching a new monitoring deployment — or revisiting one that isn't delivering what you hoped — here's the sequence to follow:

1. Define your goal.

   What do you want to understand about this building? Be specific. "Monitor energy" is not a goal. "Identify which HVAC systems are responsible for peak demand on hot days" is a goal.
2. Identify what you need to measure.

   What physical phenomena, measured where in the building, would give you the data to answer your question?
3. Select your sensors.

   Based on what you need to measure and the physical environment, choose sensors with appropriate technology, range, accuracy, and installation requirements. If you're unsure, get expert guidance here — mistakes at this stage are expensive to correct later.
4. Select your data acquisition hardware.

   Now that you know your sensors, choose hardware that supports their protocols, handles the number of inputs you need, and fits your connectivity and storage requirements.
5. Plan your data delivery.

   How will data get from your hardware to the people who need it? Consider connectivity, storage redundancy, reporting frequency, and format. Make sure your delivery method matches your actual workflow before you deploy.
6. Deploy, validate, and analyze.

   Before you rely on your data, verify it. Spot-check readings against known values. Confirm timestamps are accurate. Then begin the work the data was always meant to do — analyze trends, flag anomalies, and measure your results against the goal you defined at the start.

Once you know what you need to measure, the next step is understanding how buildings are actually instrumented — the sensors, signal types, and hardware that turn physical conditions into data. That's covered in How Buildings Are Measured: Sensors, Signals, and Data →