What is Asset Hierarchy (Parent-Child)
An asset hierarchy is a parent-child structure that arranges assets in levels, from site to system to equipment to component, so each lower record has exactly one parent. It decides where cost, maintenance history, and risk roll up, and how far down a team can trace a failure.
TL;DR
An asset hierarchy links every asset record to the item or location above it, usually running from site through systems and equipment down to components. Teams use it to total maintenance spend or downtime at any level and to find the part behind a recurring failure. It’s a data structure, not an accounting policy, so it isn’t the same thing as component accounting.
How It Works
Each record stores a pointer to its parent. Reports then move in two directions: roll-ups add child values into the parent, and drill-downs open a parent to show what sits beneath it. Child records often inherit attributes such as site, cost center, or criticality from their parent.
Many plants separate the position from the physical item. A functional position, such as “Line 2 cooling pump A”, stays fixed in the structure while technicians install, remove, and swap physical pumps into it. The position keeps its operating history, and each pump carries its own history across every position it has occupied.
Reliability teams often borrow the taxonomy in ISO 14224, the standard for collecting reliability and maintenance data. It describes nine levels: the upper five place equipment by industry, installation, plant, and system, while the lower four break equipment into subunits, maintainable items, and parts. The standard targets petroleum, petrochemical, and natural gas facilities, but manufacturers adapt its structure widely.
Types
Organizations typically run more than one hierarchy over the same assets:
- Location hierarchy: Country, site, building, floor, and room. Verification and custody work run on this view.
- Functional hierarchy: Plant, process line, system, and functional position. Maintenance planning and criticality ranking run on this view.
- Equipment hierarchy: Equipment unit, subunit, component, and part. Failure recording and spare parts planning depend on it.
- Organizational hierarchy: Legal entity, business unit, and cost center. Financial reporting and budget ownership follow this view.
Why It Matters
A flat register can list assets but can’t answer structural questions. Nobody can total last year’s maintenance spend for Line 3, or list every asset inside a building scheduled for closure, without parent-child links. Teams end up rebuilding the structure in spreadsheets for each new question.
The bigger risk shows up when assets move. If a plant sells a parent machine and nothing links its child records, those children stay on the books with no physical counterpart and become ghost assets. The reverse also happens: an asset transfer moves the parent to a new site while its components still show the old location.
Maintenance data loses value without depth. When work order management records every job against the whole line, the team sees rising cost but can’t see which component drives it.
Example
All figures are illustrative. A packaging plant structures Line 2 as a parent with three child machines, and the labeller has two components of its own.
Level | Record | Maintenance spend last year |
|---|---|---|
| Line | Packaging Line 2 | $24,200 |
| Equipment | Filler | $14,200 |
| Equipment | Conveyor | $3,100 |
| Equipment | Labeller | $6,900 |
| Component | Labeller print head | $5,400 |
| Component | Labeller drive motor | $1,500 |
At line level, the spend looks like a general reliability problem. The drill-down tells a narrower story: $5,400 of the labeller’s $6,900 went on print heads. That points to one component, not the whole line, and it changes the replacement decision.
Asset Hierarchy vs Asset Componentization
The two overlap in the register but answer different questions. The hierarchy records how items relate physically and functionally. Asset componentization is an accounting decision under IAS 16 to depreciate significant parts separately because their useful lives differ.
Every separately depreciated component needs its own child record. The reverse isn’t true: a drive motor can sit as a child record for maintenance tracking while finance depreciates it as part of the parent machine. Mixing the two views is how registers fill up with small “assets” that nobody meant to capitalize.
Best Practices
- Define the levels before loading data: Agree what each level means and which record types can sit there, or sites will build incompatible structures.
- Separate positions from physical items where teams swap equipment: History then survives replacements, and each unit keeps its own record.
- Stop at the depth someone reports on: Levels that no report, work order, or depreciation rule uses add data entry effort without adding insight.
- Move and dispose of parents with their children: A transfer or disposal of a parent should prompt a decision on every child record beneath it.
- Keep one parent per record: Where an item serves two systems, record the second relationship as a reference, not as a second parent.
CA Falgun Shah
