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

Physical plant

Site, plant, area and unit: where things physically are.

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

Assets in U-31
Tag	Description	Class	Unit	Test pack
P-3101A	Cooling water pump A	equipment	U-31	ZRF-TP-002	Unverified
P-3101B	Cooling water pump B	equipment	U-31	ZRF-TP-002	Unverified
T-3110	Cooling water buffer tank	equipment	U-31	—	Unverified
PT-3101	Cooling water header pressure	instrument	U-31	—	Unverified
TT-3102	Cooling water supply temperature	instrument	U-31	—	Unverified
HV-3101	Cooling water pump A isolation	valve	U-31	ZRF-TP-002	Unverified
31-CW-3101-400-C1C	Cooling water supply header	line	U-31	ZRF-TP-002	Unverified
31-CW-3102-400-C1C	Cooling water return header	line	U-31	ZRF-TP-002	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.

Commissioning systems

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