Building Automation Failover: What Happens When the Integration Layer Goes Down

A badly designed integration can accidentally become a single point of failure for systems that used to work independently — if the middleware bridging security, HVAC and lighting goes down, and every one of those systems was reconfigured to depend on it for basic operation, a single software failure now affects everything.

Each underlying system should retain its own basic, local functionality even if the integration layer connecting it to others is temporarily unavailable — a security panel should still arm and disarm locally, HVAC should still respond to its own thermostat, even if the unified dashboard and cross-system rules are briefly offline. The integration layer adds coordination on top, without becoming a required dependency for basic operation.

It's reasonable to ask directly, during an integration project: 'if this middleware goes down, what still works?' A vendor unable to give a clear answer is a signal the failure mode hasn't been properly considered — and that's worth resolving before go-live, not discovering during an actual outage.