Asset Tree
An Asset Tree (or Asset Hierarchy) is a structured, parent-child taxonomy within a CMMS that organizes equipment from the site level down to individual maintainable components, mirroring physical cause-and-effect relationships to enable granular reliability data tracking.
In shop floor maintenance, an Asset Tree enables precise cost and failure attribution by tracking labor and MRO parts to the exact sub-assembly or component level, such as a specific bearing, rather than a generic top-level machine. This allows reliability engineers to extract and analyze failure codes at various levels, from specific assets to classes of equipment, identifying macro trends for reliability improvements. Work orders for corrective, preventive, or condition-based maintenance are raised against the specific component that failed, with failure modes assigned at that level to ensure engineering decisions tie directly to observable degradation behavior.
- Accounting-Driven Hierarchy: Defining sub-assets for accounting convenience rather than based on how components actually fail, disconnecting reliability analysis from physical reality.
- Over-Granularization of Parts: Treating non-maintainable items like seals or small fasteners as child assets instead of parts, stopping the hierarchy at maintainable items like motors or gearboxes.
- Lack of Serial Continuity: Failing to maintain lifecycle data integrity through removal, rebuild, and reinstallation of rotating components, rendering reliability modeling non-credible.
Where does the ISO 14224 standard define the hierarchy levels?
ISO 14224 defines a nine-level taxonomy: Levels 1–5 place assets by use and location (industry to section/system), while Levels 6–9 break down equipment (unit, subunit, component, part); practical implementations often start with a subset of these levels.
How should 'Phantom Assets' be handled in the tree?
Group non-maintainable items or routes into a 'Route Asset' to maintain hierarchy structure without creating unnecessary child records for items that are not independently maintained.
What is the distinction between a Functional Location and an Asset Record?
The Functional Location represents where maintenance is performed (e.g., a pump station), and the Asset Record represents the actual physical equipment; the hierarchy must distinguish assets at the same level from those in parent-child relationships to ensure accurate analytics.