Building BIOS Architecture

The Building BIOS shall retain essential functionality without internet, cloud, manufacturer-server, or external AI connectivity.

Offline operation shall support, as applicable:

Building ID access;

authorized local login;

active Configuration Baseline;

Component, Cartridge, and Interface Registries;

essential topology and dependency data;

state and fault management;

local alarms;

safety and emergency information;

local control permissions;

maintenance access;

event recording;

backup and recovery;

operation of approved local automation.

The BIOS shall identify which functions become unavailable offline, such as:

remote monitoring;

cloud analytics;

offsite backup synchronization;

manufacturer diagnostic services;

remote AI processing;

external Registry updates;

nonessential remote control.

Loss of external connectivity shall not automatically unlock, shut down, or disable physical building systems unless required by their safety architecture.

Offline events shall be recorded locally with sequence and time-quality information. They shall be synchronized after connectivity returns without overwriting local history.

Cached credentials and authorization shall have defined offline validity. High-risk remote credentials shall not remain usable indefinitely without revalidation.

The BIOS shall provide a local method to obtain essential emergency, isolation, and recovery information.

Prolonged offline operation shall generate maintenance advisories where certificate status, software support, external hazard information, or backup replication can no longer be verified.