Integrating Fume Hoods with Building Management Systems (BMS)

From standalone fume hoods to smart, connected labs

Think of the difference between a standalone smoke detector and a monitored fire alarm system. One just makes noise; the other calls the fire department. An integrated fume hood talks to the VAV box to balance air pressure. It tells the central plant to ramp down when the lab is empty. It creates a feedback loop.

Global trends and regional drivers

We see different motivations depending on where the project is located. In Europe, high energy costs (€0.30+/kWh) mean integration is purely an ROI calculation—BMS integration pays for itself in energy savings in 2 years. In the US, it is often driven by risk mitigation and insurance requirements.

In China and Southeast Asia, we are seeing a massive push for “Smart Campus” infrastructure. New universities demand that every asset, from the chiller to the fume hood sash, be visible on a central dashboard.

Elements of a BMS-integrated fume hood

Ideally, the BMS should see everything the local chemist sees on the display screen. This includes:

Integration architectures: point-to-point vs networked

We usually encounter three levels of integration complexity:

Our advice: Don’t rely on dry contacts for critical research labs. If a dry contact fails, it fails “silent.” A network connection will throw a “Device Offline” error immediately.

BACnet basics for lab environments

In BACnet terms, a fume hood is a “Device” populated with “Objects.” The sash position is an Analog Input Object. The alarm status is a Binary Input Object. This standardization allows any BMS integrator to “discover” our hoods on the network and pull the data points in minutes, rather than spending days writing custom drivers.

BACnet integration options for fume hoods

We see two main paths for getting hoods onto BACnet:

1. Native BACnet Controller (Recommended): The controller plugs directly into the network. This is cleaner and faster.
2. Gateway Solution: The hood speaks Modbus, and a separate box translates it to BACnet. Avoid this if possible. Gateways add latency and represent another point of failure.

Typical BACnet point list for a fume hood

This is what your integrator will ask for. These are the objects we expose on a standard Deiiang hood:

Core BMS functions in laboratories

How fume hoods fit into the lab BAS architecture

Imagine a chemical lab with 10 fume hoods.

In a VAV system, if all 10 researchers open their sashes simultaneously, the exhaust demand skyrockets. A networked BMS sees this surge instantly. It ramps up the supply air to match, maintaining negative room pressure. Without this integration, opening a sash could suck the door shut or cause air to whistle through ceiling tiles.

Safety and compliance improvements

• No More “Ghost” Alarms: Critical alarms are routed to security or maintenance immediately.
• Remote Diagnostics: Before entering a hazardous lab, a technician can check if the hood is actually exhausting or if it’s safe to enter.
• Spill Response: In a spill event, one button on the BMS can trigger “Emergency Purge” on all hoods, clearing the air faster than manual intervention.

Energy savings and sustainability

Fume hoods are energy hogs. A single 6-foot hood can cost $10,000/year to operate. Integration slashes this cost via VAV control and Night Setback.

Real World Math: If the BMS automatically lowers face velocity setpoints when the lab is unoccupied (Night Setback), you can save 15-20% on top of VAV savings. For a lab with 20 hoods, that is substantial.

Operational visibility and maintenance

Visibility kills downtime. If a BMS trend shows that “Hood 7” has had low flow alarms every morning at 9:00 AM, you know it’s likely a system pressure issue (e.g., competing with the office HVAC startup) rather than a broken hood. You can diagnose it without picking up a screwdriver.

Hardware and signal-level integration

This is the “old school” method using dry contacts. Pros: It’s cheap and reliable. Cons: It’s dumb. You get an alarm, but you don’t know *why*. We only recommend this for retrofits where running network cable is impossible.

Network-level integration (BACnet, Modbus, others)

Network integration is the modern standard.

Cybersecurity and IT considerations

This is the biggest hurdle in modern projects. IT departments do not want lab equipment on their network.

How we handle it:

• VLANs: Isolate the lab automation network on its own Virtual LAN.
• Read-Only Access: We often configure critical safety setpoints so they can be monitored by the BMS but not changed remotely. This prevents hacking risks.

Deiiang controller and interface options

The Deiiang E-Series controller isn’t just a display; it’s a gateway. We ship it pre-configured for your specific protocol (BACnet or Modbus) so your integrator doesn’t have to fiddle with DIP switches.

• Built-in Flexibility: We support BACnet/IP and MS/TP out of the box.
• Local Override: The user at the hood always has priority control over remote signals. Safety first.

Pre-engineered templates and documentation

Integration usually fails because of bad documentation. We solve this by providing:

Testing and commissioning support

We don’t just ship it and ghost you. We offer remote FAT (Factory Acceptance Testing) where we hook the hood up to a BMS simulator and prove to you—via video—that the points are reading correctly before the truck even leaves the factory.

Project background

Location: Shanghai University, New Materials Research Building
Scope: 42 fume hoods.
System: Siemens Desigo CC (BACnet/IP).
The Challenge: The old labs had no visibility. Facility managers were “flying blind,” leading to high energy bills and safety gaps.

Pain points before integration

• Blind Spots: Alarms were only audible if you were standing in the room.
• Waste: Hoods ran at max speed 24/7.
• No Data: Safety audits were manual and prone to error.

Deiiang’s integrated solution

We implemented 42 Deiiang VAV hoods with native BACnet/IP. The logic was simple but effective:

1. If a hood alarms for >2 minutes, email the supervisor.
2. If occupancy sensors show “Empty” after 8 PM, force hoods into “Night Setback” (50% velocity reduction).

Results and quantified benefits

One year later, the numbers spoke for themselves:

The key takeaway? Automation didn’t just save money; it made the facility manager’s job easier.

Customer feedback

Key specification items for designers and owners

Regional localization examples

Tailor your specs to your market:

• Europe: Cite EN 14175 and EPBD directives.
• North America: Cite ASHRAE 110 and UL listing.
• Asia: Ensure compatibility with local BMS brands (Siemens/Honeywell are common).

Working with Deiiang

We make it easy. Send us your BMS brand requirements, and we will send you a pre-configured solution.

Is BMS integration mandatory?

No, but it should be. For any lab with more than 3 hoods, the energy savings alone justify the cost. For critical research, the safety benefits are non-negotiable.

Dry Contact vs. BACnet: Which is better?

BACnet wins, hands down. Dry contact is like a “Check Engine” light—it tells you something is wrong, but not what. BACnet tells you exactly what failed and why.

Can I retrofit my old hoods?

Yes. We sell retrofit kits that replace your old controller with a smart, BACnet-ready unit. It’s a great way to upgrade your lab without buying new steel.

What about IT security?

Valid concern. We recommend keeping lab equipment on a separate VLAN. We also support Read-Only configurations to prevent remote tampering.

Does Deiiang work with my specific BMS?

If your BMS speaks BACnet or Modbus (which 99% do), then yes. We work with Siemens, Honeywell, Johnson Controls, Schneider, and more.