Master data is boring, until your schedule falls apart
Why messy asset data quietly wrecks planning and scheduling, the symptoms worth measuring, and what a proper clean-up actually involves.
Key takeaways
- Master data is reference data: every work order, cost and failure record attaches to it, so errors compound rather than cancel.
- The damage shows up downstream as slow planning, jobs that cannot be kitted, and analysis nobody believes.
- Measure before cleansing: duplicate and orphan rates, completeness and coding accuracy make both the case and the baseline.
- Governance decides whether the clean-up lasts: named owners, change control and rules the system enforces.
Nobody gets promoted for fixing master data. It is the least visible work in an operation and the easiest thing to defer, which is why almost every site carries a register that no longer matches the plant.
The damage does not announce itself. It shows up as planning that takes longer than it should, spares that cannot be found, and reliability analysis that produces answers nobody believes.
What master data means here
In a maintenance context it is the asset register and functional location hierarchy, the equipment attributes, bills of material, the materials catalogue, and the cost objects those records roll up to.
It is reference data, not transactional data. Every work order, every cost, every failure record attaches to it. Which is precisely why errors compound rather than cancel out.
How it breaks the schedule
- Work coded to the wrong level of the hierarchy, so history for a component ends up spread across a plant.
- No usable bill of materials, so jobs cannot be kitted and planned work waits at the gate for parts.
- Duplicate and orphan records, so a planner searching for equipment finds three versions and trusts none.
- Catalogue gaps, so a spare that exists in the store gets purchased again on express freight.
- Cost that rolls up to the wrong system, so the business optimises the wrong asset.
A schedule is only as good as the data under the jobs on it. Kitting fails quietly first, then compliance follows.
Symptoms you can actually measure
Data quality arguments go in circles until someone puts numbers on them. Useful measures include duplicate and orphan rates, attribute completeness against a defined standard, the share of work orders coded above or below the intended level, and stock-outs recorded against items the store is holding.
Measuring first also gives you a baseline. Without one, a clean-up is an act of faith that cannot be defended at the next budget cycle.
What a clean-up involves
Audit the current state against a defined standard before touching anything. Design the target taxonomy so failure data aggregates cleanly from maintainable item up to plant, using the operation own standard where one exists or a published taxonomy such as ISO 14224 where one does not. Cleanse and enrich with rules rather than judgement calls, keeping an auditable trail from old record to new.
Then the part that decides whether it lasts: governance. Named data owners, a change process for new equipment, and quality rules enforced by the system. Without that, a rebuilt register decays back to where it started within a couple of years.
A master data clean-up
Profile the current state
Measure duplicates, orphans, completeness and coding accuracy to create a defensible baseline.
Design the taxonomy
Target hierarchy and equipment classes, agreed with the site, internal or published.
Cleanse and enrich
Rule-based de-duplication and attribute completion with an auditable old-to-new trail.
Govern
Named owners, change control for new equipment, and quality rules the system enforces.
Migrate and embed
Staged migration with reconciliation, then train planners so daily habits match the structure.
Profile the current state
Measure duplicates, orphans, completeness and coding accuracy to create a defensible baseline.
Design the taxonomy
Target hierarchy and equipment classes, agreed with the site, internal or published.
Cleanse and enrich
Rule-based de-duplication and attribute completion with an auditable old-to-new trail.
Govern
Named owners, change control for new equipment, and quality rules the system enforces.
Migrate and embed
Staged migration with reconciliation, then train planners so daily habits match the structure.
Common questions
How do we build the business case for a data clean-up?
Measure the symptoms: stock-outs against items the store holds, work coded to the wrong level, duplicate rates, planning time per job. Priced against express freight and schedule breakage, the case usually writes itself.
Can we clean up master data while operating?
Yes, that is the normal mode. Cleansing runs against a copy with an auditable old-to-new trail, and migration lands in stages with reconciliation, so planners keep working throughout.
What stops the register decaying again?
Governance: named data owners, a change process for new equipment, and quality rules enforced by the system rather than goodwill. Without those, registers drift back within a couple of years.
Key terms
Plain-language definitions from our glossary for the concepts this article leans on.
Standards and further reading
- ISO 14224:2016 Collection and exchange of reliability and maintenance data for equipment (ISO)
- ISO 8000-110:2021 Data quality, master data exchange (ISO)
- DAMA Data Management Body of Knowledge (DMBOK) (DAMA International)
- ISO 55001:2024 Asset management system requirements (ISO)
- Best practices, metrics and guidelines for maintenance and reliability (SMRP)
Related case studies and tools
- Rebuilding asset hierarchies and maintenance master data (case study)
- Work management and scheduling uplift (case study)
- Schedule Compliance Calculator (tool)
Related reading
Working through something like this?
See how we approach these initiatives, or tell us what you are dealing with.