Healthcare facility operations, compliant and online

Yes, and generator testing is the strongest example. Each emergency generator is registered as an asset, every run is detected automatically from the generator breaker closing or an ATS run request, and the platform writes one compliance report per run: whether the unit held its configured minimum load (30 percent by default, so a 750 kW generator has to hold 225 kW) for 30 continuous minutes, how long each transfer switch took against its required transfer time, and the specific reason when a test comes back incomplete. A separate runtime report splits engine hours into emergency and non-emergency time for EPA reporting, with an override workflow for runs logged as routine that were actually outages. Every report saves to PDF for the surveyor, reports regenerate from stored readings if data changes, and tests performed on Tuesday appear without anyone opening the page.

It works with what is already installed, and the BMS stays. ControlCom Connect reads building systems over BACnet IP/MSTP, generator controllers and switchgear over Modbus TCP/RTU, and newer equipment over OPC-UA and MQTT, alongside 4-20mA, RTD, thermocouple, and dry-contact points for refrigeration probes and status inputs. That covers the typical hospital mix: a BMS from one vendor, generator controllers from another, transfer switches from a third, and meters older than all of them. The platform sits on top as the monitoring, alerting, and reporting layer, so the local control logic in the BMS and the generator controllers keeps running exactly as before. There is no rip-and-replace project, and no per-tag licensing, so extending coverage from the central plant to pharmacy refrigeration and IT closets is configuration within the device and data allotment of your plan rather than a per-tag license purchase.

Most single sites are live within weeks. The edge agent installs on a small box on the facility network, makes outbound-only connections so no inbound firewall holes are opened, and pre-built protocol connectors start collecting from the BMS, generators, and meters in days. Multi-site healthcare networks then roll out facility by facility: the first hospital establishes the templates, and each subsequent site inherits the same asset structure, alarm thresholds, escalation paths, and report configurations rather than starting from scratch. The practical sequencing decision is which systems to onboard first; most networks start with emergency power and medical refrigeration because those carry the compliance exposure, then extend to chillers, air handling, and energy metering on the same platform. Each facility keeps its own view and its own alarm routing while leadership gets the roll-up across the network.

Healthcare customers typically see a 12-15% reduction in energy costs, and it comes from three places. First, scheduling: a hospital never closes, but not every air handler, pump, and sterilizer needs to run at full output around the clock, and continuous metering shows exactly which loads are running outside the hours that clinical operations require. Second, equipment: a chiller operating off its efficiency curve or a compressor degrading burns money for months before it fails, and trend data catches the drift early. Third, billing: utility-bill ingestion and load-factor reporting surface metering and billing errors that would otherwise be paid without question. None of this requires new equipment; the savings come from making the consumption of existing systems visible at a granularity the monthly utility bill cannot provide, then benchmarking facilities against each other across the network.

Facility managers, plant operations engineers, compliance officers, and energy or sustainability leads, each with a different slice of the same data. The plant engineer watches live dashboards for the central plant and gets paged on critical power alarms. The facility manager sees uptime, open alarms, and who is working on what across the building. The compliance officer pulls generator test reports and refrigeration logs when the surveyor asks, without involving engineering. The sustainability lead tracks energy per facility against the network benchmark. Role-based access keeps each of these views scoped: alarm subscriptions are managed per person and per channel, so the on-call engineer receives SMS for critical events while a director gets a daily email summary. Every account signs in with MFA or a magic link, and audit logging records who acknowledged which alarm and when.

Through alarm groups that route by response rather than by equipment. Each alarm belongs to a group, each group enables the channels it needs (SMS, push notification, email), and each person subscribes per channel, so a Critical Power group can page the on-call engineer by SMS while a Mechanical Systems group only sends email. Critical alarms reach phones within seconds of the threshold breach, and thresholds are evaluated on the edge agent at the facility, so alerting does not depend on the internet connection being up at that moment. Acknowledgement happens from the native iOS or Android app with the user and timestamp recorded, which is how the team sees what is already covered and how the audit trail shows who responded. The result healthcare teams measure: an average 15-minute faster response to critical events than panel-based annunciation.