Short answer
A building management system answers building questions: is this chiller efficient, what is the fault code on that panel, what does the energy dashboard show. A hospital quality team asks clinical ones: is theatre two ready for surgery right now, was the NICU compliant last month, is the dialysis water safe today. The same sensors can answer both. What is missing is a layer that translates points into room level clinical verdicts, which is why this is an integration problem rather than a hardware one.
Two good systems, one missing translation
It is worth being clear that this is not a criticism of the BMS vendors. Johnson Controls, Honeywell, Siemens and Schneider build excellent smart building automation. Chillers, air handling units, lighting, fire systems and energy are handled well.
The issue is that a hospital asks a category of question those systems were never designed to answer, and the distance between the two is smaller than it looks.
| What the BMS answers | What the hospital asks | What has to be added |
|---|---|---|
| Is AHU-2 running within its operating envelope? | Is theatre two ready for surgery right now? | Room level scoring against clinical limits, rolled into a single readiness verdict |
| What is the fault code on this panel? | Was the NICU environment compliant for the whole of last month? | Continuous per room logging with a compliance ontology and an exportable period |
| What is the building consuming? | Is dialysis water safe today? | The water treatment train modelled as a clinical system rather than as plumbing |
| Which AHU has a filter alarm? | Which rooms are at risk because of it? | The mapping from plant to the rooms it serves, ranked by clinical impact |
| Is the generator in auto? | Is critical power ready for the loads that matter? | Readiness modelled against life safety loads rather than reported as equipment state |
The three things the translation layer has to do
1. Map plant to rooms
A BMS knows about air handling units. A clinical team thinks about rooms. Somebody, usually one long serving engineer, holds the knowledge of which unit serves which theatre. Until that mapping is in the system, a filter alarm cannot be expressed as a clinical risk and the two worlds cannot talk.
2. Hold the limits per room class
A theatre, a neonatal unit and an isolation room have different limits for the same parameters, and those limits differ between the ASHRAE 170 basis and NABH practice. The layer has to carry limits per room class per site, configured to the hospital protocol, so that in band means something specific to that room rather than something generic.
3. Produce a verdict, not a dataset
Seven parameters produce seven numbers, and the person who needs the answer is about to start a case. Scoring each parameter against its own limit and trend, then rolling them into a single readiness state with a recommendation, is what turns monitoring into something clinicians will actually use.
How it connects
aQ HospitalOps integrates with Metasys, EcoStruxure, Desigo CC, Honeywell EBI and Forge, plus SCADA and standalone IAQ and pressure sensors, reading BACnet, Modbus and vendor APIs. An on site edge gateway does the reading and buffers locally, so telemetry stays on your network and a connectivity interruption delays data rather than losing it.
Retrofit sensors are added only where a measurement genuinely does not exist, which on a hospital survey is usually differential pressure on room pairs and particulate monitoring in critical rooms, since those are the two most commonly absent from a general purpose BMS deployment.
Do we need to replace our building management system?
No. In most hospitals the required points already exist on a commissioned and trusted BMS. The translation layer reads it over BACnet, Modbus or vendor APIs and adds room mapping, clinical limits and readiness scoring on top.
Retrofit sensors are added only for measurements that genuinely do not exist, most often room pair differential pressure and particulates in critical rooms.
Which building management systems does aQ HospitalOps integrate with?
Metasys, EcoStruxure, Desigo CC, Honeywell EBI and Forge, along with SCADA systems and standalone IoT, IAQ and pressure sensors. The platform is hardware agnostic with support for more than 130 device types across any protocol.
Does telemetry leave our network?
An on site edge gateway reads the BMS and buffers locally, so data stays on your network and a connectivity gap delays rather than loses it. The platform itself is enterprise grade and AWS native with SOC 2 aligned security, role based access and audit logging.
It monitors the building environment and its utilities. It does not connect to clinical systems or patient records.
