
An asset hierarchy is a structured, hierarchical classification of physical assets within a facility — from the highest level (site, facility, or plant) down through systems, subsystems, and individual equipment items to maintainable components. It provides the organisational backbone for maintenance management, reliability analysis, cost allocation, and performance reporting.
In oil and gas, energy, and process industries, the asset hierarchy is typically implemented in the CMMS (SAP PM, IBM Maximo, IFS, or similar) as a functional location structure, and in engineering systems as a tag-based equipment breakdown. Aligning these two representations is one of the most important — and most frequently problematic — aspects of the project-to-operations handover.
A typical asset hierarchy for an oil and gas facility has the following levels:
The most widely used standard for asset hierarchy structuring in oil and gas is ISO 14224, which defines a taxonomy of equipment classes and subclasses for reliability and maintenance data collection. ISO 14224 alignment ensures that maintenance and reliability data can be benchmarked across facilities and against industry databases.
Owner-operators typically combine ISO 14224 with their own site-specific functional location conventions in CMMS, and with CFIHOS equipment class definitions for structured technical data.
A well-designed asset hierarchy enables:
How deep should an asset hierarchy go?
Depth is determined by maintenance strategy. Most facilities maintain equipment-level tracking as standard; component-level tracking is added where component failure modes drive separate maintenance tasks (e.g., bearing replacement tracked separately from pump overhaul). Overly deep hierarchies create administrative burden without analytical benefit.
Who defines the asset hierarchy on a capital project?
Typically the owner-operator, since the hierarchy must align with their CMMS structure and maintenance management approach. On greenfield projects, the functional location structure should be defined early in FEED to ensure that engineering tag numbers are consistent with the planned CMMS hierarchy from the outset.