on April 29, 2026 Three Domains, Zero Handshakes The liquid cooling stack in a modern AI data center spans three distinct control domains. The IT layer manages GPU thermals and compute load. The CDU manages the immediate liquid loop: supply and return temps, flow rates, local pressure. The facility layer manages bulk heat rejection, whether that's chilled water, dry coolers, or cooling towers. Each domain generally manages itself competently in isolation. The problem is at the seams. When a training job launches, the load does not ramp gracefully. In moderately sized clusters, synchronized GPU activity can produce sudden, millisecond-speed changes in power draw ranging from several hundred kilowatts to a few megawatts. In a direct-to-chip system, the thermal load tracks the electrical load closely, so the heat arrives on that same timescale. Built for Buildings, Not Factories This is where commercial BMS architectures often hit their limits. Traditional BMS platforms were built for building automation, not for sub-second industrial control loops or integration with a unified data plane at scale. BACnet and its Change of Value subscriptions can move data faster than legacy polling, but the platform architecture above the protocol was designed for a different problem. If your control stack is updating state on intervals measured in seconds, it does not have a real-time digital twin. It has a historical record. The Event-Driven AI Factory You cannot optimize a physical process that you cannot monitor in real time. Managing these dynamic thermal and electrical loads requires an event-driven, edge-native architecture: a publish-and-subscribe framework using MQTT or similar lightweight messaging protocols. In this architecture, the fluid distribution controls, the electrical power management system (EPMS), and the digital twin all subscribe to the same real-time data stream. This eliminates point-to-point integrations. What replaces them is a single, instantaneous source of truth that supports real data center energy management . The control system reacts to a GPU compute spike in real time, matching cooling output precisely to the thermal load without energy-wasting safety margins. An industrial SCADA platform like Ignition is what ties this together. It connects BMS, EPMS, and the broader data plane into a single environment where power draw, thermal state, and cooling response are visible together, alert logic is buildable without custom integration work, and conditions surface as they develop rather than after they escalate. That is the difference between data center energy management and data center energy monitoring. Monitoring is passive. DCIM software is active. Fragmented Intelligence and the Procurement Gate The industry actively purchases its own operational bottlenecks. Fragmented intelligence is rarely an accident. Every time a facility procures a cooling block, an intelligent PDU, or rack monitoring equipment with its own proprietary dashboard, the design team is building a new silo. The individual decisions make sense in isolation. The aggregate result is a facility where BMS, EPMS, and IT telemetry cannot talk to each other in real time. AI-focused data center builds are heavy manufacturing plants. They need to be procured that way. No engineer would design a production facility where the power systems cannot inform the assembly line. Yet that disconnected approach is standard practice in data centers today, and it is a significant driver of unnecessary data center energy consumption across the industry. Interoperability has to be a hard gate in the procurement process. Leadership needs to stop treating open standards as an optional feature at the RFP stage. The culture shift is straightforward: mandate that every physical asset on the floor is a live, communicating node in a central control platform. That means a documented interface that the platform can reach, with real-time capability wherever the control loop requires it. MQTT, OPC UA pub/sub, and Sparkplug B are the protocols built for event-driven architectures. BACnet, Modbus, and polled APIs can be brought into the UNS, but the data only moves as fast as the poll. That tradeoff belongs in the specification, not in the integration team's punch list. The contextualization, tag naming, and unit standardization are the platform's job, not the vendor's. What the platform cannot do is reach data that only exists behind a proprietary dashboard or a vendor cloud portal with no other path out. The counterargument is that most industrial and electrical vendors already support open protocols. That's largely true. BACnet, Modbus, and OPC UA have been table stakes for decades, and a well-architected SCADA platform can contextualize almost anything that arrives through them. There are exceptions. Certain high-end instrumentation is only fully accessible through the vendor's own software stack, and those tradeoffs should be made consciously at the specification stage rather than discovered at commissioning. The real problem is specification discipline. Equipment enters the facility through an RFP. If the RFP doesn't require documented, open access to every telemetry point that the platform will need, the integration team inherits a problem that should have been solved in procurement. Industrial Plants, Not Buildings The industry has been treating data centers simply as buildings with servers in them: managed by building automation, monitored by dashboards, commissioned as real estate. The physics of the AI workloads say otherwise. Liquid cooling loops, megawatt step changes, two-ton racks, 800-volt buses: these are industrial plants that happen to produce tokens instead of steel or chemicals. Running them that way means event-driven control, a unified data plane, and specification discipline that treats every asset as part of a single operational environment. None of this is exotic. It is how modern factories are being built. Pretending AI data centers are anything else is actually the more exotic position. The industry can keep procuring these facilities as office buildings. They will still be factories. Tags / Inductive Automation All rights reserved