The building automation system (BAS) is the nervous system of a healthcare facility's mechanical plant — it executes the control sequences that hold the pressure relationships, air-change rates, temperature, and humidity that infection control and clinical operation depend on, and it provides the continuous monitoring, alarming, and trend records that prove those conditions held over time. In a hospital, the BAS is not merely an energy-management convenience; it is a patient-safety and regulatory-compliance instrument whose displays, alarms, and logs are inspected directly by accreditation surveyors.
A healthcare BAS — sometimes called a building management system (BMS) or, in its energy-focused role, an energy management system (EMS) — supervises and sequences the mechanical, and often the electrical and plumbing, infrastructure. Its scope typically includes:
Because these systems govern the air that surrounds vulnerable patients, the BAS is the practical enforcement layer for the ventilation requirements of ASHRAE Standard 170 (Ventilation of Health Care Facilities) as adopted by the FGI Guidelines for Design and Construction. When a surgeon, an infection preventionist, or a Joint Commission surveyor asks "how do we know this OR was positive to the corridor during that case," the answer comes from the BAS.
Modern healthcare BAS deployments use a layered, distributed-intelligence architecture so that local control survives network or server failure:
Communication protocols are predominantly open standards. BACnet (ASHRAE Standard 135) over IP and MS/TP is the dominant healthcare BAS protocol; Modbus is common for plant equipment, VFDs, and metering; LonWorks persists in older installations; and OPC UA, MQTT, or REST APIs increasingly bridge the BAS to enterprise analytics and the electronic health record environment. Specifying open protocols protects the owner from single-vendor lock-in over the 20-to-30-year life of the building and is a recurring point of contention worth resolving in the basis-of-design.
A critical resilience principle: local controllers must maintain life-safety-critical setpoints (OR pressurization, isolation-room direction, plant operation) independently of the supervisory network. A server reboot, a network switch failure, or a cybersecurity patch must never relax a pressure relationship. Failure modes for valves, dampers, and fans should be defined explicitly so that on loss of signal or power the system fails to the safe condition (for example, an isolation-room exhaust that fails on, or an OR that holds positive).
The sequence of operation (SOO) is the written and programmed logic that tells each piece of equipment what to do under every condition. In healthcare, the SOO is where ASHRAE 170 and FGI requirements become enforceable behavior, and where commissioning and TJC/CMS expectations are met or missed. Sequences that deserve careful authoring and review include: