Section 93 of 102
PART VI — Configuration, Evidence & Traceability
Stable section ID: S05-CON-007-SECTION-93 · 56 content blocks
92. Building Manifest Representation
The Building Manifest shall be the top-level BDL declaration that identifies the building and binds together all Modules, Packages, Profiles, registries, configurations, evidence, and external resources required to interpret it.
The Manifest shall define:
Building ID;
Site ID;
document and configuration versions;
BDL Core version;
building type and intended use;
project and jurisdiction;
coordinate and unit systems;
applicable Engineering Profiles;
imported Modules and Packages;
available configuration states;
authoritative resources;
responsible organizations;
approval status;
integrity information.
Example:
building_manifest House_001_Manifest {
id: "s05:manifest:house-001";
building: @House_001;
site: @Vernon_Site_001;
bdl_version: "1.0";
manifest_version: "0.8.0";
active_configuration: @House_001_AsDesigned_Rev08;
- profiles: [
- @System05_Base_Profile,
- @US_NJ_Residential_Profile,
- @Light_Timber_Residential_Profile
];
- modules: [
- @Architectural_Module,
- @Structural_Module,
- @Cartridge_Module,
- @Utility_Module
];
status: design_development;
}
The Manifest shall distinguish:
referenced content;
embedded content;
mandatory content;
optional content;
unavailable content;
superseded content.
The Manifest shall not copy every detailed Entity into one file. It shall identify the authoritative source and exact version of each required Module.
A Manifest shall be reproducible. A tool shall be able to resolve the same versioned inputs used when the Manifest was approved.
The Manifest shall indicate whether it represents:
partial design;
complete design;
manufacturing release;
construction release;
As-Installed record;
As-Commissioned baseline;
current operational baseline;
archival lifecycle record.