Article
News
2
min read
Brad Bonavida

Why Occupancy-Based HVAC Control in a NYC High-Rise Required Sensors, Gateways, VLANs, and a FieldServer Before Touching the BMS

August 13, 2026

The complexity of occupancy-based ventilation control runs well beyond installing sensors and writing new sequences. For the approach to work and be accepted by the people who operate the building, the occupancy data must first be transmitted safely into the building automation system.

At NexusCon 2025, Elizabeth Redmond, head of strategic accounts at R-Zero, and John Villani, a vice president at Grumman Butkus and the building's consulting engineer, walked through what it took to run demand-controlled ventilation off measured occupancy in a Manhattan tower of more than a million square feet. Because the upper floors share large headered air handlers on common risers rather than floor-by-floor units, the team pushed control down to individual HVAC zones.

The were not allowed to communicate directly with the building management system. R-Zero's devices connect to a hub over Bluetooth, which then hands off to a BACnet gateway that communicates with the BMS over BACnet. "So we have a piece of infrastructure in the middle here that's another communication arm," Redmond said. All of it rides on a dedicated VLAN through the building's existing Montgomery Technology firewall, keeping the R-Zero-supplied occupancy sensors off the wider operational network.

Then the owner added a requirement most sensor deployments skip: an MSA FieldServer as "our last gate between your devices that could be unruly" and the building systems. The FieldServer "is essentially the last security gate," Redmond said. Behind it, control stays local in the Siemens Desigo BMS while R-Zero's analytics run in a Google Cloud instance, separating what watches the building from what actuates it. Only then did Villani's team map the sensors to zones and write new operating sequences.

Villani's framing was blunt. "When you're going to deploy a technology solution, this is the level in the weeds you need to get to." The occupancy sensor is a commodity. The networking, the security gate, and the sequence work are the project.

Watch the full recording.

Register for the next Nexus Labs event.

Sign up for the newsletter to get 5 stories like this per week:

Sign Up for Access or Log In to Continue Viewing

Sign Up for Access or Log In to Continue Viewing

The complexity of occupancy-based ventilation control runs well beyond installing sensors and writing new sequences. For the approach to work and be accepted by the people who operate the building, the occupancy data must first be transmitted safely into the building automation system.

At NexusCon 2025, Elizabeth Redmond, head of strategic accounts at R-Zero, and John Villani, a vice president at Grumman Butkus and the building's consulting engineer, walked through what it took to run demand-controlled ventilation off measured occupancy in a Manhattan tower of more than a million square feet. Because the upper floors share large headered air handlers on common risers rather than floor-by-floor units, the team pushed control down to individual HVAC zones.

The were not allowed to communicate directly with the building management system. R-Zero's devices connect to a hub over Bluetooth, which then hands off to a BACnet gateway that communicates with the BMS over BACnet. "So we have a piece of infrastructure in the middle here that's another communication arm," Redmond said. All of it rides on a dedicated VLAN through the building's existing Montgomery Technology firewall, keeping the R-Zero-supplied occupancy sensors off the wider operational network.

Then the owner added a requirement most sensor deployments skip: an MSA FieldServer as "our last gate between your devices that could be unruly" and the building systems. The FieldServer "is essentially the last security gate," Redmond said. Behind it, control stays local in the Siemens Desigo BMS while R-Zero's analytics run in a Google Cloud instance, separating what watches the building from what actuates it. Only then did Villani's team map the sensors to zones and write new operating sequences.

Villani's framing was blunt. "When you're going to deploy a technology solution, this is the level in the weeds you need to get to." The occupancy sensor is a commodity. The networking, the security gate, and the sequence work are the project.

Watch the full recording.

Register for the next Nexus Labs event.

Sign up for the newsletter to get 5 stories like this per week:

⭐️ Pro Article

Sign Up for Access or Log In to View

⭐️ Pro Article

Sign Up for Access or Log In to View

Are you interested in joining us at NexusCon 2026? Register now so you don’t miss out!

Join Today

Are you a Nexus Pro member yet? Join now to get access to our community of 600+ members.

Join Today

Have you taken our Smart Building Strategist Course yet? Sign up to get access to our courses platform.

Enroll Now
Conversation
Comments (-)
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Guest
6 hours ago
Delete

This is a great piece!

REPLYCANCEL
or register to comment as a member
POST REPLY
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Guest
6 hours ago
Delete

I agree.

REPLYCANCEL
or register to comment as a member
POST REPLY
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Get the renowned Nexus Newsletter

Access the Nexus Community

Head over to Nexus Connect and see what’s new in the community. Don’t forget to check out the latest member-only events.

Go to Nexus Connect

Upgrade to Nexus Pro

Join Nexus Pro and get full access including invite-only member gatherings, access to the community chatroom Nexus Connect, networking opportunities, and deep dive essays.

Sign Up