Building BIOS Architecture

Controlled Shutdown places BIOS services and affected building systems into defined states before power removal, maintenance, restart, migration, or emergency isolation.

A shutdown request shall identify:

scope;

initiating authority;

reason;

affected entities;

dependencies;

desired shutdown state;

planned restart condition;

expected duration.

The shutdown sequence shall:

validate authority;

identify dependent systems;

determine whether shutdown is permitted;

notify affected services and users;

stop accepting nonessential configuration changes;

complete or abort active transactions safely;

preserve state and event records;

transfer or stop control functions;

isolate affected physical resources where required;

stop services in dependency order;

write a validated shutdown checkpoint;

confirm shutdown completion.

The BIOS shall distinguish:

service restart;

component restart;

zone restart;

complete BIOS restart;

planned power shutdown;

If normal shutdown cannot complete, the BIOS shall preserve the most recent valid configuration and record incomplete operations for recovery.

Restart shall not blindly restore every preceding command. Commands, overrides, temporary permissions, and operating modes shall be evaluated for current validity.

After restart, the BIOS shall:

verify integrity;

recover incomplete transactions;

rediscover affected entities;

reconcile physical and stored states;

validate configuration;

restore services in dependency order;

recommission affected functions where required;

record the restart outcome.