Definition
Master data is the stable, foundational data describing the core objects a maintenance system operates on (asset specifications, locations, equipment classes, and spare-parts descriptions) that changes rarely and is referenced repeatedly by transactional records such as work orders and notifications, rather than being recreated each time.
Key facts
- Stable, foundational data (what an asset is), distinct from transactional data (what happened to it, when).
- Referenced repeatedly by other records rather than duplicated: a work order references an asset's master data rather than restating its specifications.
- Poor master-data quality (duplicate assets, inconsistent naming) undermines every process that depends on it, from reporting to spare-parts matching.
- Includes asset master data, but also location, vendor, and material master data as related categories.
How does Master data work in maintenance?
Master data covers the foundational, rarely changing information about the objects a maintenance system works with (an asset's specifications and location, an equipment class's standard attributes, a spare part's description and unit of measure) that other records reference rather than repeat.
What does Master data require?
Because transactional records like work orders and notifications reference master data rather than duplicating it, poor master-data quality (duplicate asset entries, inconsistent naming, missing specifications) propagates errors and inconsistency through every downstream process that relies on it, from reporting to spare-parts ordering.
FAQ
Frequently asked questions
What stable base data describes the operational objects of maintenance?
Master data: the stable, foundational information about assets, locations, equipment classes, and parts that transactional records like work orders reference repeatedly, rather than being recreated each time.
Last reviewed: