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
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 A-30
Every asset placed in this node, whichever hierarchy placed it.
Nothing is placed in A-30. A node with no items is ordinary: it may be a level in the structure rather than a place things sit.
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