Section 95 of 102
94. As-Designed Configuration
Stable section ID: S05-CON-007-SECTION-95 · 49 content blocks
The As-Designed Configuration represents the intended building configuration approved at a defined design stage.
It may contain:
spatial definitions;
geometry;
required Component Types;
planned Nodes and Interfaces;
selected Cartridge Types;
required capabilities;
load and performance requirements;
utility topology;
dependencies;
Engineering Profiles;
unresolved design decisions;
design evidence.
Example:
configuration House_001_AsDesigned_Rev08 {
type: as_designed;
design_stage: detailed_design;
- entities: [
- @House_001,
- @Primary_Structural_System,
- @Building_Envelope_System,
- @Utility_Systems,
- @Planned_Cartridges
];
- unresolved_items: [
- @TBD_Final_HVAC_Cartridge_Instance,
- @TBD_Foundation_Soil_Parameter
];
}
The As-Designed Configuration may reference Types before specific manufactured Instances exist.
Example:
requires cartridge_type @KitchenServiceCartridge_Type_02
at @Kitchen_Cartridge_Bay_01;
The As-Designed model shall distinguish:
design requirement;
selected solution;
approved substitution class;
optional alternative;
unresolved selection.
Design approval shall identify the purpose of approval, such as:
coordination;
permit submission;
procurement;
manufacturing;
construction;
- prototype testing.
- An approved design shall not be represented as physically installed or commissioned.
Changes arising during manufacturing or construction shall remain deviations until formally reconciled with the design configuration.