The hierarchy levels
The ISO 14224 equipment taxonomy organises reliability and maintenance data into nine levels. Levels 1 to 5 describe where equipment is used: industry, business category, installation, plant/unit and section/system. Levels 6 to 9 break the equipment down: equipment unit, subunit, component/maintainable item and part.
Level 6 is the pivot. It is where reliability data is normally collected and compared, so a consistent definition of the equipment unit matters more than any other choice in the structure. This page describes the structure in general terms. For the normative definitions and equipment class tables, refer to the published standard.
ISO 14224 asset hierarchy example: a centrifugal pump
This is an illustrative example of one seawater lift pump on a fictional platform, from installation down to part.
| Level | Example | What it represents |
|---|---|---|
| Installation | Platform Alpha | The whole offshore facility |
| Plant/unit | Utilities | A major processing or utility area of the facility |
| Section/system | Seawater lift system | The system that delivers one function |
| Equipment unit | Seawater lift pump P-4101A, centrifugal | The item you maintain and report reliability against |
| Subunit | Pump unit | A major assembly within the equipment unit |
| Component/maintainable item | Mechanical seal | What is normally repaired or replaced as one item |
| Part | Seal face | An individual piece of the maintainable item |
Equipment boundary guidance
A boundary states what belongs to an equipment unit and what does not. Without one, two sites can report the same failure against different equipment, and their data stops being comparable. Use the boundary definitions in the standard for each equipment class where they exist, and record any local decisions.
- Driver: motors and turbines are normally treated as separate equipment units from the pump. Follow the standard's boundary for the equipment class, and apply it to every pump in the class.
- Support systems: state whether lubrication and seal support systems sit inside the boundary.
- Instruments and controls: separate instruments local to the machine from the wider control system.
- Connections: define where the boundary ends on piping, power and signal connections, for example at the inlet and outlet flanges.
- Shared utilities: keep shared supplies, such as cooling water, outside the boundary of the equipment that consumes them.
How the levels map to Maximo and SAP PM
These are typical patterns rather than fixed rules. The right mapping depends on how you plan, report and hold spares.
| ISO 14224 level | Typical Maximo structure | Typical SAP PM structure |
|---|---|---|
| Installation | Site, or top-level location | Plant, or top-level functional location |
| Plant/unit | Location | Functional location |
| Section/system | Location, within a system | Functional location |
| Equipment unit | Asset installed at a location | Equipment installed at a functional location |
| Subunit | Child asset, where tracked separately | Sub-equipment or assembly, where tracked separately |
| Component/maintainable item | Child asset, or item on the spare parts list | Assembly or material on the equipment BOM |
| Part | Item on the spare parts list | Material on the equipment BOM |
Common mistakes when loading a hierarchy into a CMMS
- Inconsistent equipment units: a pump package is one record at one site and three at another.
- Parts loaded as assets: seals and bearings fill the register with records nobody maintains individually.
- Function and physical item merged: the position and the unit installed there share one record, so history is lost when the unit is swapped.
- Undefined boundaries: failures land on the driver at one site and the pump at another.
- Wrong load order: children are loaded before their parents, or assets before their classifications.
- Classification added later: records go live without an equipment class, and retrospective classification is far harder.
Free ISO 14224 Implementation Cheat Sheet
A quick reference to keep beside you when setting up equipment taxonomy and failure coding in a CMMS.
Download the Cheat SheetApplying the structure across thousands of assets
One pump is easy to place in the hierarchy. Thousands of records from spreadsheets, vendor documents and old CMMS exports are not. AssetStage is a data staging workspace where you build the hierarchy visually and validate it for duplicates, missing fields, hierarchy violations and standards compliance. Validated data is then exported for your CMMS with a full audit trail.
See how asset register preparation works, or take the hierarchy into reliability centred maintenance.