Asset Hierarchy
The structured parent-child organization of assets, from site down to individual components, that gives maintenance data its context.
An asset hierarchy is the tree structure that organizes equipment records: site, building or area, system, asset, and sometimes component. A chilled-water pump might live under Site Riyadh → Utility Building → HVAC System → Chiller Plant → Pump CHW-P-02. The hierarchy determines how costs roll up, how failures are analyzed by system, and how quickly a technician can find the right record.
Good hierarchies mirror how people actually describe the facility, stay shallow — four or five levels is usually enough — and separate location (where something is) from asset (what it is), since equipment moves. Deep, over-engineered trees are a common implementation mistake: they look rigorous and make every search slower.
The hierarchy is also the backbone for analytics and AI. Cost-per-system reporting, criticality ranking, and failure pattern detection all depend on assets being placed consistently. A migration or new implementation should treat hierarchy design as a first-class deliverable, verified by a physical walk-down.
See your operations run themselves.
A 30-minute walkthrough with an operations engineer. Your assets, your workflows, your questions.