Industrial Data Glossary
The industrial data glossary
Clear, canonical definitions of the terms behind MRO, spare-parts, and equipment data — from data cleansing and SKU normalization to enrichment, governance, and the Industrial Data Utility model.
Core MRO data
The foundational records and concepts behind industrial parts data.
MRO data management
MRO data management is the discipline of turning fragmented maintenance, repair, and operations (MRO) parts data into one clean, standardized, and continuously governed source of truth.
It spans cleansing, standardization, enrichment, and governance of spare-parts, equipment, and material records spread across ERP, EAM, and spreadsheets — so the same part reads the same way in procurement, maintenance, and analytics. Done well, it eliminates duplicate spend and prevents downtime from incorrect orders.
Material master data
Material master data is the central record that defines every part, material, and SKU an organization buys, stocks, or maintains — its description, classification, units, and attributes.
It is the backbone of every ERP and EAM system. When the material master drifts — duplicates, blank descriptions, inconsistent units — every downstream process inherits the error. A canonical material master is the single reference each system points to.
Spare parts cataloging
Spare parts cataloging is the structured organization of maintenance spare-parts records into a consistent, searchable catalog with standardized descriptions, classifications, and manufacturer references.
A good catalog lets a technician find the part they already own instead of reordering it under a different description. Poor cataloging fragments the same item across records and sites, hiding true stock and inflating inventory.
Canonical record (golden record)
A canonical record, or golden record, is the single authoritative version of a part that every spelling, abbreviation, and supplier variant of that item resolves to.
Creating golden records is the goal of deduplication and entity resolution. Once a part has one canonical record, excess inventory and duplicate spend become visible because the part you already own finally shows up as one part.
Cleansing & matching
Removing duplicates and resolving messy records into clean, canonical parts.
Data cleansing
Data cleansing is the process of detecting and correcting errors, duplicates, and inconsistencies in part records to bring fragmented data back to order.
For MRO data, cleansing means profiling the mess, collapsing duplicates, and fixing malformed descriptions. Run as a one-off project it decays within a year; run as a continuous utility it stays clean as new parts and sites come online.
Deduplication
Deduplication is the identification and collapsing of multiple records that represent the same physical part into a single canonical record.
ERPs require near-exact text matches, so a single character or spacing difference hides a duplicate. Meaning-based matching catches linguistic variations, regional naming, and vendor inconsistencies that exact-match systems miss.
SKU normalization
SKU normalization is the standardization of part records into a consistent structure — uniform descriptions, naming conventions, units of measure, and classification — so the same item is represented the same way everywhere.
It converts entries like "pump, gear, 2hp" and "2 HP gear pump, cast iron" into one canonical, structured record aligned to standards such as UNSPSC, eCl@ss, or ISO 8000.
Entity resolution
Entity resolution is the technique of determining whether different records refer to the same real-world entity — here, the same physical part — and linking them together.
Instead of manual spreadsheet sorting, entity resolution uses machine learning and natural-language matching to recognize parts by meaning, specifications, and manufacturer references, returning confidence-scored matches rather than rigid yes/no results.
Standardization & classification
The naming conventions and schemes that make a part read the same way everywhere.
Noun-modifier format
Noun-modifier format is a structured naming convention that describes a part as a primary noun followed by ordered modifying attributes (for example, BEARING, BALL, 25MM BORE).
It replaces inconsistent free-text descriptions with a predictable, searchable structure, so procurement, maintenance, and analytics all parse the same record the same way.
UNSPSC classification
UNSPSC (United Nations Standard Products and Services Code) is a hierarchical, four-level taxonomy for classifying products and services with a unique code per category.
Classifying parts to UNSPSC (or eCl@ss) lets spend, inventory, and sourcing be analyzed consistently across plants and systems. It is one of the standard schemes records are aligned to during normalization.
Equipment taxonomy
An equipment taxonomy is a structured classification of assets and their components into a consistent hierarchy, often aligned to standards such as ISO 14224.
A shared taxonomy connects parts to the equipment they serve, enabling reliability analysis, criticality scoring, and a clean Master Equipment List (MEL). It is the structural backbone for asset-data work.
Short & long description
Short and long descriptions are the constrained and extended text fields that describe a part — the short for system display and search, the long for full specifications.
ERPs cap the short description, so critical attributes get truncated or dropped. Enrichment populates a complete long description while keeping a clean, standardized short description for search.
Enrichment & governance
Filling missing attributes and keeping the master clean over time.
Data enrichment
Data enrichment is the process of adding missing or incomplete attributes to a part record — manufacturer name, part number, specifications, units, and classification — so each item is fully described and orderable.
Enrichment draws from verified OEM catalogs, supplier libraries, and first-party sources like BOMs and work orders. A clean record is not the same as a complete one; enrichment is the step that makes data decision-ready.
Data governance
Data governance is the set of rules, validation, and ownership that keeps a data master clean and trustworthy as new parts, sites, and suppliers come online.
Without governance, a one-time cleanse degrades back to chaos within a year. Validation at the point of entry and continuous quality checks are what turn data quality from a project into a durable utility.
Knowledge graph
A knowledge graph is a structured reference that stores parts, manufacturers, specifications, classifications, and the relationships between them — not just isolated records.
Mōksana matches and enriches every record against a 3M+ SKU knowledge graph. Storing relationships — which manufacturer makes a part, which items are interchangeable, which successor replaces a discontinued SKU — powers smarter matching than a flat lookup table.
Obsolescence & lifecycle status
Obsolescence and lifecycle status is the current product state of a part — active, discontinued (EOL), or not-recommended-for-new-design (NRND) — along with its successor parts.
Surfacing lifecycle status lets buyers and planners see obsolescence risk before they order, and plan controlled transitions or last-time-buys for critical spares.
Systems & integration
How clean data connects into the systems of record that run the plant.
ERP / EAM / CMMS
ERP, EAM, and CMMS are the enterprise systems of record for finance and materials (ERP), physical assets (EAM), and maintenance work (CMMS) — the systems MRO part data lives in.
Examples include SAP, Oracle, and IBM Maximo. Rather than replacing them, a master-data layer harmonizes the part data flowing through them so each system references the same canonical record.
API-first data platform
An API-first data platform exposes its capabilities programmatically through an API, so other systems can normalize and enrich records on demand rather than through manual file exchanges.
Systems call the API at creation time to prevent new duplicates, or in bulk to remediate an existing master. This is how data quality is delivered as a continuous utility instead of a periodic project.
Bill of materials (BOM)
A bill of materials (BOM) is a structured list of the parts and components required to build, operate, or maintain a piece of equipment.
BOMs are a high-value first-party enrichment source: they tie parts to the assets they serve and often contain manufacturer references and specifications trapped in unstructured documents.
From definitions to a clean data master
Mōksana is the Industrial Data Utility that turns these concepts into practice — matching, enriching, and governing your MRO data against a 3M+ SKU knowledge graph. Book a data assessment to see it on your own records.
Book a data assessment