Air valve controls integration with BACnet

Critical airflow control systems for labs, hospitals and vivaria are usually supplied by specialist manufacturers. Each air valve has a controller, and rooms often have a dedicated room-level controller that coordinates supply, exhaust and fume hoods. The building automation system (BAS), meanwhile, runs air handlers, exhaust fans, plants and the operator interface. These two systems must share information reliably.

BACnet, the open protocol defined by ASHRAE Standard 135 and ISO 16484-5, is the most common way to connect them. This guide explains the typical architecture, the points worth exposing, and how to test that integration works. For BACnet fundamentals, see BACnet basics for building owners.

Typical architecture

Airflow control products are generally available in one of these arrangements:

• Native BACnet controllers at each valve or room: valve controllers communicate directly on BACnet MS/TP or BACnet/IP.
• Proprietary room network with a BACnet gateway: valve and room controllers communicate on the manufacturer's own network, and a gateway or router presents their data to the BAS as BACnet objects.
• Hybrid: room-level controllers are BACnet devices, while sub-devices such as hood monitors communicate locally.

Each can work well. What matters is how many points are exposed, how fast they update, and how failures are handled.

Divide control responsibility clearly

A key design decision is which system controls what. A common and robust division is:

Life-safety airflow functions should run locally in the airflow controllers and must keep working if the BACnet network fails. The BAS supervises, schedules and records, but a network outage should not change the face velocity of a fume hood or the pressure in an isolation room.

Points to expose

The point list should be defined in the design documents, not left to the integrator. Useful points include:

Per valve

• Flow setpoint and calculated flow.
• Actuator commanded and feedback position.
• Valve alarm status, such as failure to reach position or travel limit.

Per fume hood

• Face velocity or flow status.
• Sash position or open area.
• Hood alarm status and emergency purge status.
• Occupancy or user presence, where used.

Per room

• Total supply, total exhaust and offset.
• Room pressure, where monitored.
• Room temperature, setpoint and reheat valve position.
• Occupancy mode and source of the mode command.
• Room alarm summary.

For fan control

• A valve position or pressure demand signal to support static pressure reset.
• Total building or zone exhaust demand.

Commands written from the BAS to airflow controllers should be limited to what is needed, such as occupancy mode, temperature setpoints and schedules. Using BACnet priority arrays correctly ensures operator overrides and automatic commands do not conflict.

Network design

Lab buildings can contain hundreds of valve controllers. Network design affects performance:

1. Segment MS/TP trunks to keep device counts and traffic within manufacturer recommendations.
2. Use BACnet/IP for room controllers and gateways where large numbers of points must be read.
3. Avoid polling every point quickly. Use change-of-value subscriptions for status and alarms, and set trend intervals appropriate to each point.
4. Plan for growth, leaving capacity on each trunk and gateway.
5. Document device instances and addresses so they are unique across the site.

A BAS that polls thousands of points every few seconds can overload gateways and slow alarm delivery.

Alarms

Alarm design deserves care. A fume hood low-flow alarm is a local safety alarm first. The BAS alarm adds remote awareness for facilities staff. Good practice includes:

• Clear priorities that separate life-safety alarms from maintenance alerts.
• Time delays consistent with local alarms, to avoid duplicating nuisance alarms.
• Room and hood identification that matches signage in the building.
• Alarm routing to the right people, such as lab managers and facilities staff.

See alarm management in building automation for broader guidance.

Trending and analytics

Airflow data is valuable for energy management and safety audits. Useful trends include room air change rates, hood sash positions over time, offset stability and unoccupied mode compliance. Sash position trends support sash management programs, and offset trends reveal rooms where door or envelope changes have affected pressure. Trend logging and using BAS data covers how to set intervals and storage.

Cybersecurity

Airflow controllers in labs and hospitals are part of safety-critical infrastructure. Basic measures include separating the building network from corporate IT with firewalls, restricting write access to airflow controllers, changing default credentials on gateways, and considering BACnet Secure Connect (BACnet/SC) where the products support it. Owners should apply the same practices described in cybersecurity for building automation systems.

Testing the integration

Integration testing confirms data flows correctly in both directions. A typical sequence:

1. Verify every point in the point list is present, named consistently and has correct units.
2. Compare values at the BAS with values at the airflow controller's local interface.
3. Change a value locally, such as raising a sash, and confirm the BAS updates within the expected time.
4. Send commands from the BAS, such as occupancy mode, and confirm the room responds.
5. Trigger alarms and confirm annunciation, routing and acknowledgement.
6. Disconnect the network and confirm local control continues safely, then reconnect and confirm recovery.
7. Check that trends are recording at the specified intervals.

Integration testing is part of control system verification and should be completed before occupancy.

Frequently asked questions

Should valve controllers be BTL listed?

Specifying BACnet Testing Laboratories (BTL) listed devices gives some assurance of interoperability. It does not guarantee every point is exposed, so the point list still matters.

Can the BAS control the valves directly?

It can, but most designers keep fast airflow loops in dedicated controllers for speed and resilience, with the BAS supervising.

Key takeaways

• BACnet connects specialist airflow controllers with the building automation system, either natively or through gateways.
• Keep life-safety airflow control local so it continues during network outages.
• Define the point list in the design, covering valves, hoods, rooms and fan demand signals.
• Design networks, polling and alarms for the large point counts found in lab buildings.
• Test integration in both directions, including network failure and recovery.