7NOX

04/09/2026

The deadliest water problem in most buildings isn't a leak. It's biological.
CDC data shows reported Legionnaires' disease case counts grew nearly nine times between 2000 and 2018 — and when the CDC investigated outbreaks, nine in ten involved problems that effective water management could have prevented.
That's not an act-of-nature risk. That's an operations risk.

And it's now a regulated one. CMS has expected documented water-management policies from Medicare-certified healthcare facilities since 2017. New Jersey's law requires written water-management programs by 12 September 2026, fully implemented by 12 December — with five years of record retention to follow. Other jurisdictions are moving in the same direction.

The latest NOXTalks episode covers the controls angle most compliance guides miss: a BAS can't replace a water-management program, but it can automate and document much of the monitoring that makes one work. Hot water temperature trending. Cooling-tower treatment supervision. Flow data that flags stagnation before it becomes a hazard.

The same trend infrastructure that demonstrates energy performance can provide timestamped evidence that your water-control parameters were monitored and maintained.

27/08/2026

Who programs your building in 2035? Not which vendor. Which person.

JLL's research puts 39% of US facilities managers over the age of 55, against 28% across all occupations. The Department of Energy calls the shortage of people entering building controls a critical need. And LBNL found that the higher-level BAS skills, the ones that actually diagnose faults, are mostly built through years of field experience, not classrooms.

So a lot of your building's operational knowledge lives in a small number of heads. Some of them are retiring. Some of them work for your integrator, not for you.
The new episode looks at this as an owner's risk rather than an industry "skills gap": integrator dependency, knowledge trapped in one person, and what happens to your contract leverage when only one firm can touch the controls.
Three things you can do without buying a new platform:

1. Make current, version-controlled programming documentation a contract deliverable, not a courtesy.
2. Solve lock-in for the people, not just the protocol. BACnet gives you interoperability. It doesn't give you serviceability.
3. Train your own team to read the sequences. Not write them. Read them.
If your building's logic lives on one vendor's laptop, you don't own your building's brain. You're renting it.

13/08/2026

Your BMS already knows how to shed load. It does it every day.
So why isn't it earning money?
This week's episode looks at the least glamorous part of grid-interactive buildings: enrollment and measurement. Not the digital-twin future vision. The plumbing.
Three things most FMs haven't done yet:
1. Asked whether their controls can receive an automated grid signal (capability and connectivity are two different questions)
2. Mapped the enrollment path for their market: direct utility participation or a curtailment service provider
3. Separated their internal IPMVP-aligned reporting baseline from the program's settlement baseline, so DR value actually shows up in financial reporting
The US DOE roadmap put system-wide savings from grid-interactive efficient buildings at one hundred to two hundred billion dollars over two decades. Your building's slice arrives as event incentives, capacity payments, and lower peak-demand costs. But only if the money is measured, documented, and reported.
Invisible money looks like zero money at budget time.
Full episode link in the comments.

02/08/2026

$25 an hour. Or $350 an hour. Both can be a perfectly fair after-hours HVAC rate.
That spread is exactly why "what should I charge?" is so hard to answer. The right number depends on your market, your building class, your plant, and what's bundled into the rate.
A few benchmarks from real lease clauses and tenant handbooks:
Most single-zone rates land between $50 and $100 per hour. High-cost metros like Manhattan run $80 to $150 per floor, and premium towers push well past that. Nearly every program carries a one or two-hour minimum.
And watch the per-zone trap: when several tenants share one plant, charging each the full rate can overcharge badly. One audit found a firm overpaying close to $175,000 a year because of it.
Full benchmark guide here, including what drives the number and how to tell if yours is fair. https://7nox.com/after-hours-hvac-cost/

After-hours HVAC typically costs $25–$150/hour per zone, $50–$100 in most markets. See real benchmark rates, what drives them, and how to tell if yours is fair.

30/07/2026

In 1994, an explosion at the Texaco Milford Haven refinery injured 26 people. The UK Health and Safety Executive's investigation found that in the final eleven minutes, two operators had to recognize, acknowledge, and act on 275 alarms.

One every two to three seconds.

The alarms weren't broken. There were simply too many of them, poorly prioritized, arriving faster than any human could respond. That incident became a defining case behind EEMUA 191, the guide that still defines healthy alarm-system performance today.

Here's the uncomfortable part: most commercial buildings run alarm systems that would fail every one of its benchmarks. The BAS ships with alarms "for free," nobody designs them, and twenty years later operators are ignoring thousands of notifications a day — rationally, because almost none of them require action.

Until one does.

The latest episode borrows the process industry's playbook for facilities teams:

➡ Alarm rationalization: every alarm needs a defined operator response, or it gets demoted or deleted. One published ISA case study reported an 84% reduction in alarm load.
➡Smart routing: only alarms requiring timely intervention should interrupt a person, and the critical ones should flow into your CMMS with an owner and an escalation trail.
➡ Alarm health as a KPI: track average alarm rate, floods, chattering points, stale alarms, and priority distribution — the way mature alarm-management programs already do.

Alarm fatigue isn't an operator failure. It's a design failure that operators absorb on behalf of everyone who never looked at the alarm summary.

23/07/2026

"It still works" and "it's still supportable" are two very different statements about a building automation system.

Mainstream Windows 10 support ended on October 14, 2025. Extended Security Updates and certain LTSC editions created exceptions, but only for owners who knew exactly which edition they were running and had a documented patching path. For everyone else, the deadline exposed a budgeting blind spot: critical building controls with no funded replacement cycle.

The IT department refreshes laptops on a planned three-to-four-year cycle. Meanwhile, some industry sources put the optimal controls refresh window around seven to ten years, yet many buildings have no formally funded controls refresh plan at all. Obsolescence arrives as an emergency instead of a line item.

The latest episode covers what a lifecycle discipline actually looks like: ASHRAE Guideline 13-2024's guidance on legacy control systems, Albireo Energy's ten-plus-year screening threshold for legacy risk, the lesson of Tridium's 2021 Niagara AX deprecation, and three practical moves. Run a legacy checklist before anything fails. Get facilities, IT, and cybersecurity working from one lifecycle plan. Build a risk-based modernization roadmap so a failed hard drive doesn't set your capital schedule for you.

Every BAS has several clocks running. The only real decision is who's reading them.

16/07/2026

In 1980, a fire at the MGM Grand Hotel was largely confined to the casino level. Eighty-five people died anyway. Investigators documented 61 victims in the high-rise tower, far from the flames, and identified HVAC systems, stairways, elevator hoistways and seismic joints as the smoke-spread paths. Dampers had been restrained against closing. Air handlers had no smoke detectors arranged to shut them down. The litigation involved over a thousand plaintiff interests and roughly US$223 million in total settlements.

Forty-five years later, the boundary that failed there still sits between two disciplines. The fire contractor commissions the alarm system. The controls contractor commissions the BAS. The interface between them, the shutdown relay, the smoke control sequence, the damper interlock, belongs to both. In practice, that can mean it belongs to neither.

The latest episode covers what governs that seam: UL 864 listing for smoke control equipment in US jurisdictions adopting the IBC, the preprogrammed weekly self-test the code demands, and why a standard BAS controller doesn't become listed just because a smoke control point lands on it.

Three things worth doing this quarter:

1. Get a written, signed-off boundary diagram showing what the fire system controls, what the BAS controls, and every interface point between them.
2. Functionally test the seam end to end at commissioning and re-commissioning. Initiate each cause, verify every fan response, prove damper positions, check pressures and feedback.
3. Confirm who's responsible for each interface, verify listed equipment is applied within its listing, and retest after any controls upgrade.

A change on the BAS side can quietly undo what was certified on the fire side, and nothing on the graphics will look wrong.

05/07/2026

Search "after-hours HVAC" and you'll get two completely different answers.
To an HVAC contractor, it means an emergency repair at 9pm, billed at an overtime labor rate. To a property manager, it means something else entirely: conditioning a tenant's space outside building hours, billed by the hour.
If you own or manage commercial space, it's the second one that matters, and hybrid work has turned it from a nice-to-have into a standard expectation. Evening sessions, weekend pushes, distributed teams. The predictable 9-to-5 occupancy pattern that leases were built around no longer matches how tenants actually use their space.

We put together a complete guide to what after-hours HVAC is: what it costs, how it's billed, how it shows up in a lease, and how modern buildings automate it.

Start here if the topic is new to you, or send it to a colleague who keeps asking why there's a separate charge on the invoice. Link in comments.

02/07/2026

Every building owner is paying a tax nobody put on the invoice.
It's called tagging debt. When your data points are labeled inconsistently one system says "AHU1_SAT," the next says "Air Handler 1 Supply Temp" every new analytics platform, fault-detection tool, or controls vendor has to hand-map the whole building from scratch. Point by point. Every single time.

Here's the number that reframes it: the 2004 NIST study estimated inadequate interoperability cost the U.S. capital facilities industry about $15.8 billion a year (2002 data) — and roughly two-thirds of that landed on owners and operators, mostly during operations and maintenance. The part you actually live in.

The encouraging part is that this is finally being addressed at the standards level. ASHRAE 223P is building a formal, machine-readable way to describe building systems designed to define and connect Project Haystack and Brick Schema rather than pick a winner, with open-source tooling (buildingMOTIF) to validate that a model actually holds what a given application needs. As of mid-2026 it's moved through a second committee public review, though it isn't a final published standard yet.

The practical takeaway for owners and specifiers: treat your tagging convention as a contract deliverable, not an afterthought. And next time a vendor pitches you, ask one blunt question: can you ingest a standard data model, or are your people going to hand-map every point?

The value in a building's controls used to live in the wiring. Increasingly, it lives in whether the building can describe itself to the next tool that walks in the door.
How are you handling tagging on your portfolio spec requirement, or crossed fingers?

25/06/2026

Most buildings got their EV chargers the same way: bolted on after the fact, drawing off a switchboard that was sized years before anyone imagined a row of chargers — and running in a vendor portal that never talks to the BAS. That's how a sustainability "amenity" quietly becomes an electrical-capacity and OpEx problem.

A few things worth sitting with:

➡ A demand charge isn't a penalty or an energy bill. It's a capacity charge tied to your highest demand interval. A single bank of chargers ramping up together can define that peak — and the Smart Electric Power Alliance's example (a 350 kW peak at $20/kW) adds about $7,000 in a month.
➡ Dynamic load management (and ALMS) can let you add chargers without an expensive service upgrade — by keeping total draw under the capacity you already have. California's 2025 CALGreen provisions now recognise this approach.
➡ OCPP reduces vendor lock-in, but it's a charger-to-management-system protocol — not automatically a BMS interface. Specify that export separately.
➡ And the quiet one: EV fires are still relatively uncommon, but in an enclosed car park the consequence profile is different. Worth getting the mechanical and fire side in the room before install.

The shift is simple to say and harder to do: treat charging as a managed building load, not a bolt-on.

New episode out now. 🔌