Article Wrap Up (TL’DR)
Many organizations live with poor MRO spare parts support. Their master data foundation has unaddressed root causes. The first is not making record descriptions active structured elements of record identity. Second is relying solely on Manufacturer Part Number (MPN) values to determine duplicates. This leads to poor spare parts availability for Maintenance while simultaneously degrading MRO inventory turns and increasing cost. Spare parts support is improved by using a spare parts identity taxonomy for better consistent record identification leading to better asset performance
Introduction
Physical asset intensive companies large enough to use business software (ERP/CMMS) to organize Operations & Maintenance processes are commonly challenged by poor spare parts support. This means Maintenance suffers with low material availability, and lost productivity in both work planning and work execution. For the Supply and Logistics (SCM) side of Maintenance Repair & Operations (MRO) it is common for MRO inventory turns to be below one turn a year get worse over time. This shows more stuff regularly goes into inventory than comes out to support Maintenance & Operations. That this is common across many organizations and industries and has largely resisted improvement initiatives over time is a sure sign something foundational is wrong.
This article will investigate the reasons why Maintenance suffers with poor MRO material availability, while concurrently SCM effort to satisfy MRO demand is too often ineffective. Then I’ll share what I have learned from two full careers first living in complex industrial system operation & maintenance, then as functional consultant implementing, optimizing and supporting ERP systems. A broken MRO material master data foundation is the key observation that has driven poor spare part support for both Maintenance and SCM. Weak and inconsistently identified spare parts records is the root cause of poor MRO spare parts support. My insights and advice come from frontline MRO experience followed by extensive direct system implementation work, not software programming, marketing school, or a seat on the AI bandwagon. Finally, I’ll offer the first step to take on the road to real MRO performance improvement.
Who this article is for
Stakeholders from Maintenance, Reliability, Operations, Sourcing, Contracts, Procurement, Logistics, Warehouse, Finance, Master Data Governance and IT that should be concerned with MRO spare parts support
The signs of weak spare parts support
Which of these practices happen in your organization?
Maintenance & Reliability:
- Required parts are planned in work orders as non-stock free text items. This confirms the MRO material support process has failed. The process and master data failure is evident by the preference to use a plodding ad hoc reactive job by job, start from scratch each time approach to provision spare parts.
- Maintenance Planners spend significant time working with Suppliers, researching technical documentation or walking the warehouse to identify the correct items needed to perform jobs
- There is a backlog of work orders awaiting parts. A well functioning MRO system easily avoids parts availability being a routine source of delay in job scheduling
- Jobs in execution phase are often stopped or delayed for ‘parts’. This includes wrong parts issued, necessary parts not planned or not issued. This point brings in other causes than poor master data, but poor master data is a central cause
- Equipment failure root cause investigations come up with determinations of wrong spec items installed in previous work orders
SCM:
- The MRO inventory turns KPI is below 1 and shrinks lower as time goes by. This means working capital to support MRO grows while stock purchases are partially consumed. Poorly identified records with stock holdings are a central cause.
- Maintenance leaders and front-line workers are hostile or contemptuous of SCM MRO support
- MRO sourcing projects negotiate contract prices at broader category level discounts because item level data is not available or trusted
- Some parts are bought with multiple 100% mark-ups. These are items catalogued with an MPN for an EPC suggested preferred vendor, who buys parts from the OEM, who buys parts from an original component manufacturer. This is how you pay $400 for $100 parts
- Warehouse storage space demand grows prompting the need for expanded storage or more warehouses
MRO master data Governance
- Dozens to hundreds of new MRO material requests are processed monthly even when no new equipment or systems are deployed. Most of these requests are for items that have previously been catalogued, but the record was not found by end users or in the Data Governor’s duplicate check
- The MRO duplicate identification process rarely finds matches in new material requests. The same happens in building spares records for capital projects and merger consolidations. MPN checks find only perfect field content matches, ignoring existing records that have empty MPN fields, records with alternate numbers stored, as well as variations on spaces, dashes, prefixes, suffixes and fat fingered mistakes
- Every plant has its own independent MRO item catalogue. This is because item identities were too weak to see duplication when the catalogues were originally compiled into the ERP from previous sources. Items in every plant are created as if they are unique in the enterprise
- The MRO material master naming convention is weak and incomplete. The extent of many existing naming conventions are ‘start with a noun’, ‘use all capitals’, or call it what the requestor wants as they are the technical experts. Weak naming conventions do not consider or enable item descriptions to be useful elements of the record identity
Poor Spare Parts Record Identification is a Root Cause of Weak Spare Parts Support
The two observations that show that inconsistent and poorly identified spare parts records is a root cause of poor spare parts support are:
- MRO users, starting with Maintenance Planners, are challenged to the MRO material masters they need to do their jobs. Record short descriptions are the primary search tool to find spares records. Short description searches are ineffective when they are inconsistently formed record to record for similar items. Useful item descriptions are formed from values for identity attributes that are structured in the same order for similar items. That is all valve records have descriptions formed from a valve identity template, and the same for motors, etc.
- Master Data Governance has a goal of having a single MRO material master in the system to represent each real-world item needed. Ideally, this would be a global requirement for an entire organization. Often organizations do not achieve record uniqueness even at the plant level. Within a plant many MRO material masters often represent the same item. While nearly all Governance organizations have duplicate check processes, the common method in spares is a simple Manufacturer’s Part Number (MPN) field value comparison. The method is flawed and allows all but perfect MPN value matches to pass.
What are the outcomes of Weak Spare Part Record Identification?
Business performance suffers when spare part record identification is weak:
- Higher level cross functional business goals like safe and reliable production carry unnecessary avoidable risk caused by weak spare parts support. This is a huge unconsidered business risk
- Maintenance job productivity is harmed (lower tool time)
- Maintenance planning and job plan improvement are harmed. Planner time going into finding parts could go into higher value job plan improvements with future payoff. Identifying the right part does not carry over to fast successful search the next time the same part is needed
- SCM responsibilities to support MRO performance are harmed. Weak part identification causes sourcing lock in. Purchases are made with the previous source simply because the item’s identity is unclear. The past supplier knows what they supplied on the last PO that worked so they can provide it again, other potential suppliers don’t have that knowledge
- MRO inventory and its consumption of working capital continuously grows
- The Master Data Governance function is not seen as a value adding partner by Maintenance, Reliability, Operations, SCM and Finance. The data governance may or may not be blamed for poor MRO spare parts performance, but they clearly do not build business trust for their ability to be a valued business partner
- Regular and persistent spare part support weakness tears at cross functional teamwork. Frustration and finger pointing lends support to silo building and is corrosive to broader organizational success. Frustration is evident across local teams and in Head Office to plant relationships
The Waste from Poor Spare Parts Record Identification is Significant and Worth Fixing
Compiling a business case for the losses from the waste caused from the above bullet points likely carries an annual dollar value in the millions of dollars in multi-plant environments. The governing doctrine for MRO support says production downtime from parts non-availability is the most expensive outcome by orders magnitude, so needs to be avoided. Although a true statement, this allows toleration of waste in MRO spares support and may be a source of inattention to the utility of a solid master data foundation.
Buying extra versions of the same thing and storing quantities of each in inventory does not help protect uptime. In fact, the difficulty in finding the right record caused by weak inconsistent item descriptions adds to downtime risk and makes maintenance more inefficient.
Solutions suggested to improve MRO spare part support too often do not address the root cause of the problem
My consulting work and my interest in doing MRO better have sent me looking for ideas and solutions repeatedly. A striking finding is that most MRO support improvement ideas start by assuming the records an organization has, collectively known as their MRO item catalogue, are valid and supposed to be there. Since somebody created each record so they must be necessary. A primary contention I have is that current governance methods can not distinguish duplicate records and have no systematic method of declaring a record is insufficiently identified. Organizations seeking better MRO spares support too often start improvement efforts by working on follow on issues to weak item identification issue
MRO improvement methods found in online searches from serious MRO practitioners include:
- ABC Criticality Analysis
- Validate procurement lead times
- Optimize Min/Max and Reorder Points
- Leverage Technology and CMMS
- Centralize Storerooms and Share Spares
- Data-Driven Decision-Making
- Centralizing MRO Inventory Management
- Leveraging Vendor Partnerships
- Clean and Standardize Master Data
- Centralization & Standardization Across the Org
Of these 10 MRO improvement methods only clean and standardize master data and Centralize & Standardization Across the Org might cover the ground that is the record identity problem. The other methods only achieve their full utility when applied to a rational catalogue with well identified records. What I believe has been missing from the marketplace is a well thought out structured identity taxonomy that is implementable. There is no shortage of AI and AI enabled solutions in the market. However, until I see different, I expect these solutions will only get clients to the same post data cleanse frustration as old school data cleanses but get there faster. As I have said above, fixing the MRO material master data foundation requires making the item descriptions into proper elements of the item identity, and that the identity attributes that make up the descriptions are available to support item uniqueness comparison.
Record Identification Standards are missing in the MRO Master Data Foundation
The gap in the master data foundation for effective spare parts support is inadequate MRO material master record identification standards. Useful consistent item identification is necessary for people (or agents) to find records they need to do their jobs. Weak record identities are the difference between powerful reuseable records that populate important information in business transactions that enable needed spares to be ready and waiting on the shelf when needed and plodding limited or one time use records that annoy people trying to get their work done. For useful spare parts catalogue governance duplicate record prevention needs stronger methods than simple comparison of MPN field contents. Governance also needs explicit standards to prevent records with incomplete, unknowable and indeterminate descriptions from being created.
Weak MRO material identification has been a problem since the dawn of digital business systems. The poor business results have been lived with and are usually accepted as being a necessary cost of doing business. Attempts to improve performance often focus on data cleansing methods that did not address the root causes, so data cleanses were either ineffective or had limited useful lives.
The fundamental requirement is that item descriptions need to be essential elements of the record identity. They need to be built from standardized identity attribute values that are applied to all similar items. The solution is an identity taxonomy made up of a set of identity classes (similar items) that are mutually exclusive and collectively exhaustive of the MRO item universe. Each identity class has an identification template made with a set of defining identity attributes organized in a set order. Each attribute is either mandatory or optional. This gives the power to have minimum identity information rules in creating new records. The values assigned to identity attributes expand item comparability and duplicate determination beyond only exact matches in the MPN field being flagged
The ideal case for Spare Parts Support to Physical Asset Management
To clearly understand the shortcomings of current spare parts support, it is helpful to see what is lived with in comparison to an ideal case.
The ideal starts in the asset development capital project phase of the lifecycle.
• Design for reliability and design for maintainability are active concepts in the engineered design of the overall asset
• Operations & Maintenance staff are integrated into the project to develop the operational phase master data
• A structured process works through asset criticality, equipment maintenance strategies, required spares to support equipment maintenance strategies, application of the enterprise spare parts record identification standard to the needed items, determination of new spares records needed versus spares record extensions, determination of stocking strategy by item, maintenance bill of material creation, sourcing strategy determination, sourcing lead time evaluation for all spares, determination of reorder point parameters for stock items
• The above work is planned for completion and load into the production ERP for the start of the Set to Work phase
• If we were to bring only necessary, well thought out and identified spares records and maintenance BoMs into the operational lifecycle phase, parts are easy for workers in every function to find, inventories of hidden duplicates do not accumulate, new record requests to provision materials for open work orders do not happen, and the parts needed for new work orders in planning are likely available on the shelf or within the work order preparation lead time. If so, spare parts support hums instead of rattling, sputtering, failing and frustrating the people involved. MRO and asset KPIs that MRO supports improve, life is good.
Capital projects often are poorly integrated into the operations lifecycle phase. This causes a disruptive scramble for spares support at asset commissioning that necessitates reactive short-term solutions to spare parts needs that are harmful to effective well managed spare parts support. Typically, the scramble for useful spares support is ongoing and only ever partially resolved. Smooth operation even if at extra cost lasts only as long as the staff familiar with work arounds remain in current roles. Specifically with the poor record identification issue, maintenance planners come up with their own bread crumb trail methods to find parts they frequently use.
Of the steps listed above to have useful MRO support, a spare part record identity standard is a foundational requirement. When it is absent follow-on corrective response results remain diluted. For example, if the supply lead time for an item was not determined, investigation and entering the lead time on the record fixes the lead time issue. In the absence of a useful item identity standard, changing a records description does not achieve clarity of what the record represents. An identity standard is the foundation that is needed first to write consistent findable item descriptions
The Harm of Weak Spare Part Record Identities occurs across Functions, the Solution sits in No Man’s Land
Maintenance is not charged with making clear findable comparable spare part record identities
Reliability is not charged with making clear findable comparable spare part record identities
Operations are not charged with making clear findable comparable spare part record identities
Procurement is not charged with making clear findable comparable spare part record identities
The warehouse is not charged with making clear findable comparable spare part record identities
Engineering is not charged with making clear findable comparable spare part record identities
Finance is not charged with making clear findable comparable spare part record identities
Master Data Governance is responsible for master data quality and spare part record identification is a data quality issue. The Governance team has no inherent skill set regarding identification of spare parts to support this requirement. I have worked in many IT organizations (and data governance no matter that is a business support function comes from IT lineage), the answer to non-IT questions is invariably, that is a business issue. The business is seen as an amorphous non-IT blob referred to as “the business”. So, since the problem is a business problem and no function in the business owns it, nothing ever happens to start a correction. Also, since historically weak spare pare record identities have been lived with and accepted as a cost of doing business, Data Governance is the most unlikely source to raise a flag to correct the issue.
SMIT is a purpose-built solution to the Spare Part Identity Problem
SMIT (Structured Material Identity Taxonomy) was developed to solve what is discussed above. SMIT is a taxonomy made up of about 50 identity classes to cover all possible MRO item records. Each identity class has a template with a set of identity attributes to populate to form short and PO Text descriptions. It is not a software solution; it is not a business system. It is a way to form findable and comparable spare parts record identities that use the description fields as essential identity elements. SMIT is a solution to the missing master data foundational element in ERP/CMMS spare parts record governance. SMIT answers the question “what do we call this item?” and answers it in a consistent finable and governable manner.
SMIT can be used directly from its Excel delivered format to develop and generate consistently structured short and PO Text descriptions in your new MRO material master creation process in any ERP/CMMS. SMIT works with data load tools (like LSMW) or with manually entered new records. If your shop runs a Master Data Management (MDM) or Master Data Governance (MDG) solution you can build the SMIT rules into the system. The providers of these systems commonly declare their data quality rules engine can run whatever data quality rules you use and I understand that to be a credible statement.
SMIT is unlike other naming conventions:
- SMIT is not thousands of noun modifier templates that are ambiguous to users and data governors alike. Consider the identification challenges created by having a standard with templates for both Valve Gate and Valve Isolation. Abundant and overlapping templates leave end users still in the guessing game of what did they call it and the game starts with the end user guessing the noun modifier assigned at record creation.
- SMIT was designed from observing hundreds of thousands of item descriptions and seeing the frequency distribution of record nouns is highly skewed. A small number of nouns cover most items, followed by a long tail of increasingly infrequently used nouns. SMIT is designed with classes defined to usefully support identifying members of the long tail without giving each its own noun class. This makes identity class assignment feasible for non-experts and items findable for end users
Perfection can be the enemy of useful progress. Take the 1st step to a better MRO catalogue
I recommend physical asset intensive organizations that have lived with poor MRO material support to implement SMIT to support their new material master administration process now. MRO catalogue transformation to the SMIT standard enables rationalization of records and consolidation of duplicate inventory stocks.
SMIT is not a universal standard. It is enterprise configurable. Identity classes can be separated, or consolidated, the identity attributes per class can be modified, which attributes are set as mandatory can be adjusted, approved abbreviations and UoMs can be adjusted. Confirming the appropriateness of SMITs details to the enterprise is a set part of implementation.
Implementing SMIT in the new MRO material master creation process facilitates cross functional discussion and learning. The experience gained from using SMIT will help determine the best opportunities to transform existing records. Possible approaches could be plant based, or identity class based depending on business case evaluation.
Use of SMIT with new records is a low cost, low risk path to improve MRO spare parts support.
Why use of a Spare Part Record Identity Taxonomy matters
The two big reasons to use a Spare Parts Record Identity Taxonomy are item findability and item comparability. Findability and comparability drive improved spare parts support success.
Findability: Consistent item descriptions are made from identity attributes values structured consistently for similar items. This changes record search from a guessing game about what the item was called and what information was included in the description into predictable findable structures. That supports reusable spare parts records connected with the MRO support that has items ready on the shelf or for direct purchase items that have a supplier, price and lead time pre-planned. Inconsistently identified records cause search failures followed by either warehouse walkdowns or new record creation, sourcing and delivery wait time. If finding spares becomes bad enough, expensive alternatives to avoid material master use come into play, that is free text POs and squirrel pile inventory.
Comparability across all identity attributes. MRO item governance is improved when all the identity attribute values for similar items can be systematically compared in the duplication check process. This is a stark improvement on MPN checking that has proven to be ineffective.
Checklist
- How would you rate your organization’s MRO spare part support on a scale of 1 to 10? (with 1 being disastrous and 10 being flawless)
- Does your organization have a documented MRO spare part naming convention?
- Is the naming convention widely available to all MRO users so they know the naming structures in use?
- Do you feel like there is an invisible fence separating MRO stakeholders by function and or Head Office to Plant?
- If your answers to these questions point to spare part record identification being a foundational gap in MRO spares support, then it’s time to act. You can share this article with fellow stakeholders and discuss the weaknesses and challenges. You can message me and we can discuss your MRO

Leave a Reply
You must be logged in to post a comment.