Section 99 of 102
98. As-Operated Configuration
Stable section ID: S05-CON-007-SECTION-99 · 32 content blocks
The As-Operated Configuration represents the authorized physical and logical configuration of the building during actual operation.
It shall be derived from the As-Commissioned baseline and updated through Building BIOS configuration management.
It may include:
active Component and Cartridge Instances;
active Interface connections;
current configuration version;
current capabilities;
operational restrictions;
approved temporary changes;
current Engineering Profiles;
active adapters;
unavailable or isolated systems;
authorized control relationships.
Example:
configuration House_001_AsOperated_2027_07_20 {
type: as_operated;
based_on: @House_001_AsCommissioned_Rev01;
effective_at: "2027-07-20T14:30:00Z";
- active_changes: [
- @Kitchen_Cartridge_Replacement_CS012,
- @Electrical_Load_Limit_CS013
];
- isolated_entities: [
- @Exterior_Sensor_Cartridge_03
];
bios_configuration:
@BIOS_Config_V3_03;
}
The As-Operated Configuration shall not attempt to store every rapidly changing sensor value directly. Operational telemetry and events may remain in BIOS and Digital Twin records while BDL represents the authoritative configuration context.
The Digital Twin shall be fed and updated from verified BIOS information associated with the As-Operated Configuration.
- A temporary operational state shall not automatically become an approved configuration change.
- Configuration drift detected by BIOS shall be represented separately until reconciled.