Section 94 of 102
93. Configuration Model
Stable section ID: S05-CON-007-SECTION-94 · 48 content blocks
A BDL Configuration is a versioned set of Entities, Properties, Relationships, Constraints, Profiles, and evidence representing the building at a defined lifecycle stage or decision point.
The Configuration Model shall include:
Configuration ID;
Building ID;
configuration type;
parent configuration;
effective time;
included Modules;
included Entity versions;
applicable Profiles;
change set;
approval status;
completeness status;
evidence status;
digital signature.
Example:
configuration House_001_AsDesigned_Rev08 {
id: "s05:configuration:house-001:design-r08";
building: @House_001;
type: as_designed;
parent: @House_001_AsDesigned_Rev07;
- includes: [
- @Architectural_Module_Rev08,
- @Structural_Module_Rev06,
- @Utility_Module_Rev04
];
applied_change_set: @ChangeSet_CS_008;
status: approved_for_coordination;
}
The configuration shall be interpreted as an engineering graph:
- Configuration =
- Entities
- + Properties
- + Relationships
- + Constraints
- + Profiles
- + Evidence
- + Status
BDL shall support:
complete configuration snapshots;
incremental change sets;
alternative branches;
temporary configurations;
Zone-specific configurations;
- historical configurations.
- Only explicitly coordinated Modules may form an authoritative configuration.
A configuration shall not combine an outdated structural Module with a newer architectural Module if their declared compatibility range is violated.
The active Building BIOS configuration shall be generated from a validated and authorized BDL configuration, while runtime states and events remain managed by BIOS.