BuildMEP Guide Hub
HVAC Controls, Detection & Efficiency: The Complete BuildMEP Guide
Every controls decision comes down to the same three questions: what signal is the system actually reading, what condition is it really responding to, and how do you verify it’s working as designed. This hub works through the control-signal foundation, two real applications built on it, the efficiency and metering concepts used to judge performance, and the field maintenance practice that keeps it all running.
Part 1 — How the System Talks: Control Signals & Demand Response
Every controlled valve, damper, or airflow decision starts with a signal the BMS can read, command, and trend. Get the signal type wrong and nothing downstream works reliably — including demand-based control that depends on it.
The actuator submittal offers four control-signal options and “digital is better” isn’t a real answer. What each signal type actually costs and gains in commissioning, monitoring, and maintenance.
DCV isn’t “put a CO₂ sensor on the wall and open the damper at 1,000 ppm.” It’s changing ventilation in response to measured demand while never dropping below the code-minimum outdoor air floor.
Part 2 — Detection Systems That Protect People
Gas detection is a control signal with a safety consequence attached — choosing the wrong sensor for the wrong gas doesn’t just waste energy, it leaves a hazard undetected.
“Petrol means CO, diesel means NO₂” is useful background and nowhere near enough for an actual design. What the adopted code and the real vehicle mix determine instead.
Part 3 — Measuring Efficiency and Capacity
A rated number is only useful if you know what it was measured against. These three concepts get misread constantly — comparing incompatible ratings, sizing a meter for one operating point, or reading a spec that means something different than it appears to.
12 EER next to 16 SEER2 doesn’t tell you which unit actually performs better — the two numbers come from different test procedures entirely. What to check before comparing any two ratings.
A meter sized purely by pipe size will often measure the design condition correctly and the rest of the operating year badly — because sizing a BTU meter is really two separate problems wearing one name.
The term shows up across BTU meter, DCV and design-mistakes discussions without always being defined — and it means something different for a flow meter than it does for a burner.
Part 4 — Field Practice: Keeping It Running
Every concept above eventually meets a technician on a ladder with a checklist. What actually prevents downtime is rarely the exotic failure — it’s the routine check that got skipped.
Package units almost never fail with a bang — performance just fades until someone notices. Field-tested checks from hospital maintenance work, where a missed one has consequences beyond comfort.
Where These Get Mixed Up on Site
- A submittal offers four control-signal options and the spec doesn’t say which one — the default becomes “whichever is digital,” without checking what the BMS can actually commission and trend.
- A CO₂ sensor gets treated as ventilation control on its own, without confirming it still respects the code-minimum outdoor air floor underneath it.
- A diesel-heavy parking garage gets CO detection because that’s what’s familiar — and NO₂ goes unmonitored.
- Two units get compared on EER against SEER2 as if the numbers sit on the same scale.
- A turndown-ratio spec gets read as an accuracy figure when it’s actually describing stable firing range, or the reverse.
Every one of these guides traces back to the same discipline.
Read what’s actually being measured before designing or specifying around it. A control signal that can’t be commissioned, a sensor sized for the wrong gas, an efficiency number compared on the wrong scale — each mistake above stays quiet until commissioning, when the system doesn’t do what the drawing promised.
