Rebuilding asset hierarchies and maintenance master data

The challenge

Asset registers commonly grow through acquisitions, brownfield projects, vendor imports and local workarounds, with equipment sitting at inconsistent levels, duplicates and orphans accumulating, and functional locations that no longer match the plant that was actually built.

The information this creates is disjointed and hard to trust. Work gets coded against the wrong asset, history cannot support reliability analysis, spares cannot be found and maintenance cost will not roll up by system. Planners, reliability engineers and supervisors require a register that reflects the plant, and governance that keeps it that way.

When it's time to act

The signs we commonly see when this initiative is due.

• Planners find three versions of the same pump and trust none of them.
• Work orders coded to whatever level was easiest, so history will not aggregate.
• Spares bought on express freight while the same item sits in the store under another number.
• Maintenance cost that will not roll up by system when the budget review asks for it.
• Reliability analysis abandoned because the failure data cannot be grouped.

Our approach

• Understand the issues first-hand with the planners, supervisors and reliability engineers who work around them daily, so the rebuild targets what actually breaks rather than what looks untidy.
• Audit the existing register and measure it: duplicates, orphans, attribute completeness and coding accuracy, benchmarked against your own data standard and, where relevant, published taxonomies. That gives a maturity baseline you can defend at the next budget cycle.
• Design the target hierarchy so failure data aggregates cleanly from maintainable item up to plant. Where a client has an internal standard we work to it; where they do not, a published taxonomy such as ISO 14224 gives a well tested starting point.
• Cleanse and enrich records with rule-based checks, keeping an auditable trail from old to new. Data quality references such as ISO 8000 are useful for framing the rules, and are applied where they add value rather than by default.
• Establish data governance: named owners, a change process for new equipment, and quality rules checked by the system rather than by goodwill.
• Migrate in stages with reconciliation at each step, then train planners so day-one habits match the new structure.

Tools and methods

The value it creates

• Planning, scheduling and spares all get faster and more accurate when the register matches the physical plant.
• Failure history aggregates cleanly at every taxonomy level, which is the precondition for defensible reliability engineering and strategy work.
• Maintenance cost rolls up accurately by system, and every later initiative, from condition monitoring to analytics, starts from a foundation that holds.

What changes

Where these initiatives fail

The failure modes we design against.

• Cleansing without governance, which rebuilds the register and then watches it decay again.
• Designing the taxonomy in isolation from the planners who will code against it every day.
• Migrating everything instead of what the operation actually maintains.
• Treating the rebuild as an IT project when the hard decisions are maintenance decisions.

Common questions

Key terms

Plain-language definitions from our glossary for the concepts this page leans on.

Standards and further reading

Reference points we draw on where they suit the work. We also work to client internal standards and established site practice.

• ISO 14224:2016 Collection and exchange of reliability and maintenance data for equipment (ISO)
• ISO 8000-110:2021 Data quality, master data exchange (ISO)
• ISO 55001:2024 Asset management system requirements (ISO)
• The Asset Management Landscape, third edition (GFMAM)
• DAMA Data Management Body of Knowledge (DMBOK) (DAMA International)
• Asset Management Council, Australian asset management community (Asset Management Council)

Further reading

Articles and calculators on the methods behind this work.

• ISO 14224, and building an asset hierarchy that holds up (article)
• The asset management plan, and the strategy it comes from (article)
• Operational readiness for new assets: methods, standards and the CMMS build (article)
• Master data is boring, until your schedule falls apart (article)
• Mining solutions (solution)
• Rail solutions (solution)

Related projects