Plant hierarchy
Four structures over the same assets. They deliberately do not line up, and the page keeps them apart.
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
11
nodes
Commissioning systems
5
nodes
Test packs
2
nodes
Handover packages
2
nodes
Test packs
What is pressure tested together. A pack routinely spans units.
Items in ZRF-TP-002
Every asset placed in this node, whichever hierarchy placed it.
| Tag | Description | Class | |
|---|---|---|---|
| P-3101A | Cooling water pump A | equipment | Unverified |
| P-3101B | Cooling water pump B | equipment | Unverified |
| HV-3101 | Cooling water pump A isolation | valve | Unverified |
| 12-CW-1210-100-C1C | Cooling water supply to condensate export cooler | line | Unverified |
| 31-CW-3101-400-C1C | Cooling water supply header | line | Unverified |
| 31-CW-3102-400-C1C | Cooling water return header | line | Unverified |
ZRF-TP-002 in the other structures
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.
Four structures, never merged
Test packs that span units
Ordinary, and the reason a single tree cannot express this project.
- ZRF-TP-002U-31, U-12
Where a boundary comes from
A drawn boundary is never an approved one. Why