Plant hierarchy

Four structures over the same assets. They deliberately do not line up, and the page keeps them apart.

Demonstration project - no figure here describes a real facilityChanges are not saved

Why

Each tree is built from the project's own hierarchy nodes, and the item counts are the assets actually placed in each node.

Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.

Physical plant

nodes

Commissioning systems

nodes

Test packs

nodes

Handover packages

nodes

Commissioning systems

System and subsystem: how the plant is commissioned, which does not follow the physical layout.

SYS-12Condensate export systemsystemno items
- SYS-12-01Export pumps and dischargesubsystem19 items
- SYS-12-02Export meteringsubsystem8 items
SYS-31Cooling water systemsystemno items
- SYS-31-01Cooling water circulationsubsystem9 items

Every asset placed in this node, whichever hierarchy placed it.

Assets in SYS-12-02
Tag	Description	Class	Unit	Test pack
E-1216	Condensate export cooler	equipment	U-12	—	Unverified
PT-1202	Condensate export header pressure	instrument	U-12	—	Unverified
TT-1203	Condensate export temperature	instrument	U-12	—	Unverified
FT-1204	Condensate export flow	instrument	U-12	—	Unverified
HV-1202	Condensate export header isolation	valve	U-12	ZRF-TP-001	Unverified
XV-1205	Condensate export shutdown valve	valve	U-12	—	Unverified
12-CD-1202-150-A1A	Condensate export header	line	U-12	ZRF-TP-001	Unverified
E-1217	Condensate export cooler B (register only, drawn on no sheet)	equipment	U-12	—	Unverified

The same items, placed by each hierarchy in turn. Where a node's items land in more than one place, the structures disagree about this node.

Physical plant

Test packs

Four structures, never merged

Ordinary, and the reason a single tree cannot express this project.

A drawn boundary is never an approved one. Why