Asset Hierarchy

Ownership Boundary#

This topic owns functional-location, system, equipment, and parent-child structure. Asset Register Development owns individual asset records; Failure Coding & Asset Taxonomy owns failure classification rather than hierarchy design.

Plain-English Definition#

Asset hierarchy is the structured relationship between locations, systems, assets, components, and parts.

It shows where equipment belongs, how it supports operations, and how maintenance work, costs, failures, and reliability history should roll up for decision-making.

A simple hierarchy may look like:

1. Company
2. Site
3. Area
4. Process or line
5. System
6. Asset
7. Component
8. Part

Not every organization needs every level. The structure should be detailed enough to support maintenance decisions without becoming too complex to maintain.

Scope Boundary#

This record covers hierarchy design.

It depends on, but does not replace:

• Assets and Asset Classification, which defines asset taxonomy, naming, and classification language.
• Asset Register Development, which defines the governed master asset data set.

Why It Matters#

A useful asset hierarchy allows maintenance teams to find equipment, assign work, track cost, analyze reliability, and report performance at the right level.

A weak hierarchy creates familiar problems:

• technicians cannot find the right equipment record;
• work orders are charged to the wrong asset;
• history is scattered across duplicate records;
• system-level problems are hidden;
• cost reports do not match operational reality;
• PMs are assigned too high or too low in the structure;
• spare parts and BOMs are hard to connect.

When to Use It#

Design or redesign the hierarchy when:

• implementing or cleaning up a CMMS;
• building an asset register;
• creating PM programs;
• standardizing work order coding;
• improving equipment history;
• performing asset criticality analysis;
• building reliability reports;
• consolidating sites into a common asset model;
• preparing capital or lifecycle plans.

Core Principles#

1. Match how work is performed#

The hierarchy should reflect how technicians, planners, operators, and supervisors think about the equipment in daily work.

2. Separate location from equipment#

A location is where something is installed. An asset is the maintained equipment. A component is a maintainable subpart of an asset.

3. Use parent-child relationships intentionally#

Parent-child relationships should help people understand system function, work history, cost rollups, and reliability impact.

4. Avoid unnecessary depth#

A hierarchy with too many levels becomes hard to understand and maintain. A hierarchy with too few levels hides useful history and cost.

5. Design for reporting and analysis#

The hierarchy should support KPI reporting, asset criticality, bad-actor analysis, downtime rollups, and lifecycle planning.

Step-by-Step Implementation#

Step 1: Define hierarchy levels#

Choose the levels that fit the business.

Common levels include:

• Enterprise
• Site
• Area
• Line or process
• System
• Asset
• Component
• Part

Small organizations may only need site, area, asset, and component.

Step 2: Define maintainable boundaries#

Decide where work should be charged.

For a conveyor system, the conveyor line may be the system, each conveyor may be an asset, and motors, gearboxes, bearings, belts, and sensors may be components.

Step 3: Build the initial structure#

Map each area, process, system, asset, and component in a visible draft before loading records into the CMMS.

Step 4: Validate in the field#

Walk the hierarchy with maintenance and operations. Confirm that the structure matches how equipment is installed, operated, isolated, maintained, and reported.

Step 5: Assign hierarchy relationships in the register#

Each asset record should have a clear parent relationship or functional location. Avoid orphan records and duplicate structures.

Step 6: Govern changes#

Create rules for adding assets, moving assets, retiring assets, replacing equipment, and changing system relationships.

Examples#

Manufacturing Example#

• Site: Plant 1
• Area: Packaging
• System: Case Conveyor System
• Asset: Conveyor 1
• Component: Drive Motor
• Component: Gearbox
• Component: Belt
• Component: Photo Eye

Laundromat Example#

• Site: Main Street Laundromat
• Area: Laundry Room
• System: Washer Bank A
• Asset: Washer 01
• Asset: Washer 02
• Asset: Washer 03
• System: Dryer Bank A
• Asset: Dryer 01
• Asset: Dryer 02
• Area: Utility Room
• Asset: Water Heater 01
• Asset: Electrical Panel 01

Commercial Facility Example#

• Site: Office Building 1
• Area: Roof
• System: Building HVAC
• Asset: Rooftop Unit 01
• Asset: Rooftop Unit 02
• Area: Electrical Room
• System: Electrical Distribution
• Asset: Main Switchboard
• Asset: Panel A

Common Mistakes#

• Building the hierarchy from accounting records only.
• Making the hierarchy too deep for technicians to use.
• Charging all work to a parent line instead of maintainable assets.
• Creating components as assets when no one will manage history at that level.
• Mixing buildings, systems, equipment, and parts in the same field.
• Copying another company's hierarchy without adapting it to local operations.
• Changing hierarchy rules without governance.

Best Practices#

• Start with a simple model and add detail only where it improves decisions.
• Use field validation before import.
• Keep naming, taxonomy, and hierarchy standards connected.
• Design the hierarchy before assigning PMs at scale.
• Preserve retired assets and history.
• Review hierarchy quality during CMMS audits.
• Align hierarchy with cost, downtime, criticality, and spare-parts reporting needs.

KPIs and Measures#

Useful hierarchy-quality measures include:

• percent of active assets with a valid parent relationship;
• number of orphan asset records;
• number of duplicate hierarchy branches;
• percent of work orders charged to correct asset level;
• percent of PMs assigned to maintainable assets;
• number of hierarchy changes without approved governance;
• percent of critical systems with complete asset/component structure.

Related Topics#

• Assets and Asset Classification
• Asset Register Development
• Equipment Master Data
• Asset Information Management
• Asset Criticality Analysis
• Failure Coding and Asset Taxonomy
• Maintenance Planning

Product Opportunities#

Templates#

• Asset Hierarchy Template
• Functional Location Worksheet
• CMMS Hierarchy Import Template

Calculators#

• Asset Criticality Calculator
• Replacement Cost Estimator

AI Tools#

• Asset Hierarchy Builder
• Asset Classification Assistant
• CMMS Data Cleanup Assistant

Facility Manager Features#

• Parent-Child Hierarchy Manager
• Asset Register
• Equipment History
• Criticality Rollups

References#

• ISO 55000 — Asset Management Overview, Principles, and Terminology
• ISO 14224 — Collection and Exchange of Reliability and Maintenance Data for Equipment
• SMRP Body of Knowledge — Maintenance, Reliability, and Physical Asset Management

Revision History#