Section 59 of 101
PART V — States, Events & Core BIOS Services
Stable section ID: S05-CON-006-SECTION-59 · 46 content blocks
58. Building State Model
The Building State Model provides the authoritative representation of the building’s current verified condition.
The building shall not be represented by a single undifferentiated state. Its condition shall be described through a coordinated state vector containing, at minimum:
lifecycle state;
configuration state;
BIOS integrity state;
operational state;
safety state;
security state;
resource state;
communication state;
maintenance state;
emergency state.
Each state value shall include:
subject identity;
state category;
current value;
source;
timestamp;
verification level;
confidence where applicable;
effective configuration version;
active restrictions;
related events.
Building-wide state shall be derived from component, Interface, Cartridge, zone, service, and dependency states through explicit aggregation rules.
The BIOS shall distinguish among:
Declared State: reported by the entity or manufacturer;
Commanded State: state requested by a controller or user;
Observed State: condition detected through communication, sensing, or inspection;
Verified State: condition confirmed by an approved method;
Inferred State: condition calculated or estimated from indirect information;
- Desired State: state requested by an approved operating policy.
- These states shall not be silently treated as equivalent.
Building state examples include:
unconfigured;
under construction;
commissioning;
operational;
partially operational;
degraded;
maintenance;
isolated;
emergency;
recovery;
decommissioned.
A building may be Operational while one independent noncritical zone is Degraded. Aggregate-state rules shall therefore preserve zone and system detail rather than reducing the entire building to the worst isolated condition without justification.