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
Physical plant
Site, plant, area and unit: where things physically are.
Items in U-11
Every asset placed in this node, whichever hierarchy placed it.
| Tag | Description | Class | |
|---|---|---|---|
| V-1110 | Inlet separator | equipment | Unverified |
| K-1120 | Inlet booster compressor | equipment | Unverified |
| PT-1101 | Inlet separator pressure | instrument | Unverified |
| LT-1110 | Inlet separator level | instrument | Unverified |
| AT-1105 | Inlet gas H2S analyser | instrument | Unverified |
| PSV-1110 | Inlet separator relief valve | valve | Unverified |
| 11-NG-1101-300-B2B | Inlet gas to separator | line | Unverified |
U-11 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.
Commissioning systems
- not placed7 items
Test packs
- not placed7 items
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