Section 86 of 105
83. Authoritative Configuration Baseline
Stable section ID: S05-CON-014-SECTION-86 · 27 content blocks
Every System05 building or controlled assembly shall maintain an Authoritative Configuration Baseline.
The baseline shall define the approved engineering configuration for a specified scope and point in time, including:
- Installed asset identities.
- Asset and Interface versions.
- Locations and orientations.
- Physical relationships.
- Functional allocations.
- Structural load paths.
- Utility connections.
- Approved capacities and limits.
- Safety classifications.
- Applicable Engineering Profiles.
- Authorized software and firmware.
- Approved exceptions and restrictions.
- Required evidence and certification status.
The configuration architecture shall distinguish among:
- As-designed configuration.
- As-manufactured configuration.
- As-delivered configuration.
- As-installed configuration.
- As-commissioned configuration.
- Current approved operational configuration.
- Observed physical condition.
- Proposed future configuration.
An observed condition shall not become an approved configuration merely because it exists physically. Similarly, an approved digital configuration shall not establish that the corresponding physical work has occurred.
Only one active Authoritative Configuration Baseline shall exist for the same scope and effective time. Historical baselines shall remain retrievable.
Changes shall occur through controlled authorization, impact assessment, implementation, verification, and baseline release. Unapproved physical or digital differences shall be treated as configuration drift rather than silently incorporated into the baseline.