Subsystem management
Each subsystem, what it contains, which test packs it reaches, and what is missing before any of them could be executed.
Demonstration project - no figure here describes a real facilityChanges are not saved
Why
Membership and verification state are read from the project's own records. Readiness is reported as its three separate conditions rather than as a percentage.
Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.
Systems
2
Subsystems
3
Test packs
2
Subsystems fully verified
0
Readiness is three conditions, not a percentage
Every item verified, nothing in conflict, and the boundary confirmed.
Subsystems
| System | Subsystem | Name | Items | Verified | Test packs | Boundary |
|---|---|---|---|---|---|---|
| SYS-12 | SYS-12-01 | Export pumps and discharge | 19 | 1 of 19 | ZRF-TP-001 | Not confirmed |
| SYS-12 | SYS-12-02 | Export metering | 8 | none | ZRF-TP-001 | Not confirmed |
| SYS-31 | SYS-31-01 | Cooling water circulation | 9 | none | ZRF-TP-002 | Not confirmed |
Test packs and the units they reach
| Pack | Name | Items | Units | |
|---|---|---|---|---|
| ZRF-TP-001 | Condensate export discharge | 8 | U-12 | One unit |
| ZRF-TP-002 | Cross-unit utility tie-ins | 6 | U-31, U-12 | Spans 2 units |
A pack that spans units is ordinary. Why