What is a building management system (BMS) for data centers?
A building management system (BMS) monitors and controls the building side of a data center: HVAC (CRAHs, chillers, cooling towers), fire suppression, lighting, access control, and emergency power. Its main job is to keep the room inside the ranges IT equipment is rated for, typically 18 to 27°C and 20 to 80 percent relative humidity under the ASHRAE guidelines.
In a data center most of that work is cooling, which accounts for 30 to 40 percent of facility energy. How well the BMS runs the cooling plant shows up directly in Power Usage Effectiveness (PUE) and on the power bill.
Why BMS matters for data center operations
The BMS runs the systems that keep IT equipment alive. Four reasons it matters:
- Cooling failures cause outages: HVAC failures are the second leading cause of data center downtime after power failures. The BMS is where the early signs show up: supply air drifting above setpoint, a chiller alarm, humidity outside the band.
- Energy waste from overcooling: When cooling output is not tied to IT load, most facilities overcool by 20 to 40 percent. That energy goes straight into PUE.
- Compliance requirements: Regulations such as the EU Energy Efficiency Directive 2023/1791 require you to monitor and report energy consumption, cooling included.
- High-density racks: GPU racks drawing 50 to 100 kW and up need tighter cooling control than a traditional BMS was designed for.
BMS integration with DCIM: why it matters
In most facilities the BMS and DCIM run as separate systems. The facilities team watches cooling and building plant in the BMS, and the IT team watches servers and network in DCIM. Neither side can see the other half:
Without integration
- BMS cannot see IT load changes
- DCIM cannot see cooling capacity
- Separate alert systems, separate dashboards
- Incidents correlated by hand across two consoles
- No coordinated capacity planning
With Aravolta integration
- Cooling adjusts as IT load changes
- One dashboard for power, cooling, and IT
- One alert stream, correlated across systems
- Automated incident workflows across both systems
- Power and cooling capacity planned together
How Aravolta integrates with BMS
Aravolta reads the BMS you already have over two standard protocols, with no proprietary gateway or middleware in the path:
| Protocol | Systems | Data collected |
|---|---|---|
| BACnet/IP | HVAC controllers, chillers, CRAHs, fire panels | Temperature, humidity, setpoints, alarm status, run hours |
| Modbus/TCP | Cooling towers, CDUs, meters, sensors | Flow rates, pressure, fluid temperatures, power readings |
Once connected, BMS points sit next to IT metrics in the same Aravolta dashboard. You can write alerts that span both, for example "rack temperature above 35°C AND CRAH supply air above setpoint", and watch power-to-cooling ratios in real time.
Key benefits of BMS-DCIM integration
Reduced PUE
Tying cooling output to IT load cuts overcooling and brings PUE down by 0.1 to 0.3 points.
Faster incident response
When a rack overheats, the alert already shows whether the cause is IT load, a cooling failure, or blocked airflow, so your on-call engineer is not opening two consoles to find out.
Consolidated alerting
One alert stream for IT and building events. Nobody has to watch a BMS console and a DCIM console at the same time.
Compliance reporting
Energy data for IT and cooling comes out of one system, which is what EU EED 2023/1791, DCOI, and corporate sustainability reporting ask for.
Frequently asked questions
What is a building management system (BMS) for data centers?
A building management system (BMS) monitors and controls the building side of a data center: HVAC, fire suppression, lighting, access control, and emergency power. In a data center most of its work is cooling (CRAHs, chillers, cooling towers) and holding the room inside the temperature and humidity ranges IT equipment is rated for.
Why should BMS integrate with DCIM?
Because cooling and IT load affect each other and neither system can see the other on its own. With BMS data in the DCIM you can see how cooling capacity tracks IT load, trim overcooling to bring PUE down, run incident response across both systems, and pull one compliance report instead of two. Without it, the facilities team and the IT team work from separate consoles and correlate by hand.
What protocols does Aravolta use to connect with BMS?
BACnet/IP and Modbus/TCP, the two most common standards in building automation. Aravolta reads HVAC controllers, chillers, CRAHs, cooling towers, fire panels, and environmental sensors over those protocols directly, with no proprietary gateway or middleware in between.
How does BMS integration reduce PUE?
By matching cooling output to actual IT load. When the DCIM sees IT load drop, it can signal the BMS to turn cooling down in proportion instead of running at the output the room needed at peak. Operators on an integrated BMS-DCIM platform typically see PUE improve by 0.1 to 0.3 points.
Can Aravolta monitor both air-cooled and liquid-cooled systems?
Yes. Air-cooled plant (CRAHs, chillers, cooling towers) comes in over BACnet/IP and Modbus/TCP. Liquid cooling (CDUs, rear-door heat exchangers) comes in with supply and return temperatures, flow rate, differential pressure, and leak detection. Both show up in the same dashboard.
Does BMS integration require replacing existing equipment?
No. Aravolta reads your existing BMS controllers over standard BACnet/IP and Modbus/TCP and shows that data next to your IT infrastructure metrics in one DCIM dashboard. The controllers stay where they are.
Last updated: September 2025