7NOX

7NOX 7NOX is an after-hours HVAC scheduling and billing app.

04/06/2026

Most building owners are treating the refrigerant transition as a mechanical swap. It's quietly become a controls problem.
Here's the part that doesn't show up on the equipment quote: a lot of new A2L equipment ships with refrigerant leak detection and a mitigation sequence — fans, dampers, compressor shutdowns, all on defined timers. Sometimes that lives entirely inside the unit's factory controls. But when the detection has to trigger external fans, open remote dampers, raise alarms, or get monitored centrally, it becomes a BAS integration job. New points, new sequences, new commissioning.
And that line item rarely makes it into the replacement budget until install day.
Our latest NOXtalks episode connects the regulatory clock — the AIM Act, the EPA's reconsidered Technology Transitions rule, ASHRAE 15, UL 60335-2-40 — to what actually changes in your control sequences and your capital plan.
Three moves before your next chiller or RTU replacement:
1. Inventory what's coming due and ask what refrigerant and safety class the replacement uses, and whether its detection has to interlock with your BAS.
2. Budget the controls integration now, not at install.
3. Go by the current EPA table, not last year's deadline summary.
Five minutes, no fluff. Link in comments.

21/05/2026

Your BAS tracks temperature in 40 zones. It trends CO2 in real time. It escalates an alarm when a filter clogs.

So why does it go completely silent when a pipe fails over the weekend?
Here's the uncomfortable truth: most commercial buildings manage water about two decades behind the way they manage air. We treat air like an instrumented, controllable system — dozens of zones, real-time trending, escalating alarms. Then we treat water like a homeowner with one shutoff valve in the basement.
And the loss numbers don't justify that gap:

→ FM Global describes liquid damage as more than twice as likely to harm a business as fire
→ Chubb notes offices are more likely to experience water damage than fire
→ The losses escalate fast once you add business interruption, tenant disruption, electrical damage, and mold remediation.

The technology isn't the bottleneck anymore. Flow-signature analysis can catch a slow leak at 3 a.m. that doesn't match normal occupancy. Acoustic sensors can hear a leak before it stains a ceiling. Motorized isolation valves can shut a riser automatically — all integrated into the BAS you already own, over BACnet or Modbus.

Attention is the bottleneck.

Three things to put on your list this quarter:

1. Put water on the same dashboard as air. If you can pull up CO2 by zone, you should be able to pull up flow rate by floor.
2. Meter and isolate at the riser, not just the street. The cost of valving one floor is small next to the cost of flooding one floor.
3. Call your broker before you spend a dollar. Some insurers offer credits for qualifying leak detection and automatic shutoff — worth knowing if you're installing it anyway.

Your building manages air like a surgeon and manages water like it's 2005. Time to give water a voice on the dashboard — before it finds one of its own.

14/05/2026

Your retrocommissioning project delivered. The savings showed up. Eighteen months later... they're gone. That's sequence drift — and Lawrence Berkeley National Laboratory has been clear about how it happens.

Their Open Building Control research found that best-practice control sequences in large commercial buildings are often not implemented correctly, or not implemented at all. That gap alone can create 10–30% energy waste — before any degradation even begins.

Then comes the slow part. A comfort complaint on a Tuesday. A manual override. A flattened reset schedule. Six months later, dozens of points are sitting in manual that no one remembers touching.

The fix isn't more commissioning. It's MBCx — monitoring-based commissioning — owned as an operating discipline, not a project.

In the latest episode, we walk through:

→ The three distinct number buckets LBNL has actually quantified
→ Why "the playbook exists, it's just not owned" is the real problem
→ A monthly, quarterly, and semi-annual cadence facility teams can actually run

For FMs, building owners, and engineers who are tired of watching savings evaporate.

Listen here: https://youtu.be/0T223KZDOzc

30/04/2026

Cloud BMS is becoming mainstream. That’s not the problem. The problem is that many building owners and operators are moving into cloud-based building management platforms without a clear exit plan.

In the latest NOXTalks episode, we look at four questions that should be in every cloud BMS procurement or renewal conversation:

➡ Who owns the historical trend data?
➡ If you leave, can you export that data in a usable format?
➡ What happens if the vendor gets acquired, changes direction, or sunsets the platform?
➡ And during a cloud outage, what still works locally at the edge?

Cloud platforms can offer huge benefits: remote access, portfolio visibility, analytics, AI-readiness, and faster rollout across sites. But the contract matters.

A CSV dump with cryptic point names is not the same as usable operational history. Semantic models like Project Haystack, Brick Schema, and the proposed ASHRAE 223 standard can help make building data more portable, but only if the contract also confirms that historical trend values come with the export.

And from a controls perspective, the most important rule is still simple: The cloud can optimise the building. It should not own the building’s safe state.

For facility managers, building owners, and engineers, the best time to ask these questions is before signing. The second-best time is at the next renewal.

24/04/2026

If you replaced a rooftop unit in 2025, your building automation system just inherited a life-safety job it didn't have before — and most facility teams don't know it yet.

On January 1, 2025, the EPA's Technology Transitions Rule under the AIM Act effectively ended R-410A in new comfort-cooling equipment. The replacements — A2L refrigerants like R-454B and R-32 — are mildly flammable. That one word changes everything about how your BAS handles a rooftop swap.

In this 5-minute episode, we break down what A2L actually means for your controls scope, why ASHRAE 15-2024, ASHRAE 34-2024, UL 60335-2-40, and the 2024 International Mechanical Code now pull your BAS into the life-safety response chain, and what to do on Monday morning to make sure your next equipment replacement doesn't ship with a refrigerant sensor wired to nothing.

Three practical takeaways inside: the A2L sequence audit every replacement needs, the point-list and sequence-of-operation updates your team should already be making, and why your next phone call should be to your AHJ — not your distributor.

Built for facility managers, building owners, property managers, building engineers, and BAS systems integrators who'd rather find out about this now than at commissioning.

NOXtalks is a short-format podcast covering the commercial building trends, technology, and operational realities that matter to the people actually running buildings. New episodes regularly. Subscribe so you don't miss the next one.

26/03/2026

Episode 26: Your BAS Runs on Networking.
Most BAS problems don’t show up looking like network problems.
They show up as frozen graphics. Offline controllers. Intermittent alarms. Remote connections that worked yesterday and fail today.

That’s exactly why networking is no longer optional knowledge for BAS teams.
In this episode, we dig into why IP plans, VLANs, NTP, certificate management, and remote access paths now sit at the center of BAS uptime and troubleshooting. We also get practical about what teams should actually do: maintain one authoritative network map, track certificate renewals like any other maintenance item, and review every remote connection path with facilities and IT together.

For FMs, building owners, and engineers, this one is less about “learning IT” and more about reducing downtime, speeding up root-cause analysis, and avoiding blind outages.

Listen here: https://youtu.be/ofwSHRb023g

20/03/2026

Everyone wants the dashboard. Everyone wants the AI layer. Almost nobody wants to talk about the labeling, tagging, and metadata work underneath it.

But that’s exactly where many smart building projects break down.

In this episode, we dig into a problem that’s still underestimated across the industry: dumb data.

When point names are inconsistent, units are missing, equipment relationships are unclear, or location context isn’t there, teams end up spending time and money cleaning data before analytics, FDD, enterprise dashboards, or centralized BMS workflows can even begin.

That’s why semantic structure is becoming a practical requirement, not an optional extra. Standards and frameworks like Project Haystack, Brick, and ASHRAE 223P all point in the same direction: usable building data needs meaning, not just volume.

A few practical takeaways from the episode:

Audit 50 critical points first

Check names, units, equipment references, and location context

Put semantic tagging requirements into specs and submittals

Require exportable tagged data at handover, not mappings locked inside one platform

Clean metadata may not be flashy, but it leads to faster onboarding, cheaper integrations, better analytics, lower engineering hours, and a much cleaner path from project delivery into operations.

New episode: “Dumb Data Is Killing Smart Buildings”

12/03/2026

Everyone wants AI, analytics, and portfolio visibility.
But a lot of buildings still have broken resets, drifting sensors, stale overrides, and sequences that were never truly verified in the field.
That gap has a cost.
In the latest NOXTalks episode, I unpack the hidden cost of commissioning debt and why it’s still one of the most overlooked issues in commercial buildings.
Before adding another software layer, it’s worth asking:
Can the building actually tell the truth?
We cover:
• why poor BAS fundamentals weaken analytics
• where commissioning debt typically hides
• how bad sequences drive energy waste and comfort issues
• what FMs, engineers, and owners should prioritise first
The practical takeaway is simple:
Fix the resets.
Validate the sensors.
Clear the overrides.
Prove the sequence.
Then scale the intelligence.
Listen here: https://youtu.be/MIJ-yF4Y6tE

10/02/2026

Who owns the “brain” of your building? Not the plant. Not the controllers. The brain is the operational history that makes analytics possible: trend logs, alarms, tags, asset IDs, equipment hierarchies, and maintenance context.
Here’s the problem: a lot of contracts say “you own your data”… but don’t guarantee you can actually leave with it in a usable form. Then, when you want to add a second analytics tool or switch providers, you discover the export is a pile of numbers with no context, no tags, and no structure — and suddenly switching costs are measured in months.

In our latest episode, we break down data rights in plain English:
The 6 questions that define real data control
Red flags like vague “improve services” clauses (often used to justify model training)
Who owns “derived” work like tagging maps and fault rules
A simple “data fire drill” to test portability before it’s urgent
What a one-page data charter should include in every deal
If you manage building platforms, we’d love your take:
What’s the worst “export/offboarding” experience you’ve seen — and what would you put in the contract next time?

23/01/2026

Alarm fatigue is an operations problem—not a software problem.
If your BAS alarm console feels like a slot machine, you’re not monitoring the building. You’re managing noise. And when alarm storms hit, the root cause gets buried under hundreds of downstream symptoms.

We just published a practical 90-day BAS alarm cleanup plan for commercial facilities. It’s designed to be implemented with your SI and internal team using the tools you already have—no major capex required.

The plan is four phases:
• Days 1–14: Export 30–90 days of alarm history. Identify top offenders, standing alarms, after-hours alarms, and storm patterns.
• Days 15–30: Write a one-page Alarm Philosophy (priorities, routing, escalation, suppression with audit trail, change control).
• Days 31–60: Fix the Top 20 (deadbands, delays, instrumentation/comms/schedules) and implement root-cause grouping so symptoms don’t flood the console.
• Days 61–90: Operationalize: escalation logic, maintenance modes, work-order linkage, and a weekly “alarm hygiene” review.
Three actions you can do this week:
1. Pull the alarm export and identify your top 20 offenders
2. Draft the one-page alarm philosophy
3. Pick your worst alarm storm and redesign it so the root cause rises
Read the article: https://7nox.com/stop-the-alarm-storm-90-day-alarm-cleanup-plan-for-commercial-facilities/

Address

PO Box 8644 Symonds Street
Auckland
1150

Opening Hours

Monday 6am - 6pm
Tuesday 6am - 6pm
Wednesday 6am - 6pm
Thursday 6am - 6pm
Friday 6am - 6pm

Telephone

+6499729163

Website

https://opsyssolutions.com/

Alerts

Be the first to know and let us send you an email when 7NOX posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to 7NOX:

Shortcuts

Featured

Share

Category