Search your inventory system for "bearing SKF 6205." What do you get?
One entry called "BRG-6205-SKF." Another called "Bearing 6205." A third called "SKF 6205-2RS." And a fourth one, simply labeled "bearing kecil." All four are the same part. Nobody knows how many are actually in stock. Procurement just ordered 20 more because "the system said we had zero."
This is not a software problem. It's a naming problem. And it costs plants real money โ in duplicate purchases, production downtime while someone hunts for a part, and inventory carrying costs bloated by phantom stock.
What is Canonical Spare Part Naming?
Canonical naming means every spare part in your inventory has exactly one official name. Not two. Not "whichever name the technician used when they created the entry." One name. One record. One source of truth.
It sounds simple. In practice, it's one of the hardest things to implement in maintenance management โ and one of the highest-ROI things you can do before rolling out a CMMS.
Why Spare Part Naming Goes Wrong
The root cause is simple: most plants don't have a naming standard. Parts get added to the system by whoever happens to receive them, in whatever terminology they use:
- The purchasing department uses the supplier catalog name: "SKF Deep Groove Ball Bearing 6205-2RS"
- The maintenance technician uses the shorthand: "bearing 6205"
- The storekeeper uses a storage location code: "R3-S2-B bearing"
- The engineer uses the equipment BOM reference: "Pump-12-Bearing-Drive-End"
Same part. Four names. Each one looks correct to the person who created it. Together, they're a disaster.
The Real Cost of Bad Naming
Duplicate Inventory
The most obvious cost. When a part exists under multiple names, your inventory system thinks you have multiple distinct parts. Total stock might be correct, but the system shows zero for this entry and 10 for that one. Procurement sees zero and orders more. Now you have 20 when you needed 10 โ and the carrying cost of the extra 10 compounds every month.
Extended Downtime
A machine goes down. The technician searches for the replacement part. They search by the name they know โ "seal 45x55x7" โ and get no results. The part exists in the system, but it's listed as "TC seal 45-55-7 NBR" because the storekeeper catalogued it differently. The technician spends 45 minutes hunting through the warehouse before someone says "oh, you mean the TC seal?" Downtime costs for a mid-size production line: $500-2,000 per hour. That 45 minutes cost more than the seal itself.
Failed CMMS Implementation
A CMMS rollout is the moment of truth for your parts data. When you migrate inventory from spreadsheets (or worse, from institutional memory) into a structured system, every naming inconsistency becomes visible. Suddenly the CMMS shows 4 entries for the same bearing and zero stock for what the PM work order needs. Technicians lose trust in the system on day one. They revert to the old ways โ asking the storekeeper, checking the shelf directly, or just ordering new parts.
Bad Procurement Decisions
When you can't trust your inventory data, you can't make good procurement decisions. You order parts you already have. You miss parts you're about to run out of. You can't negotiate volume discounts because you don't know your true annual consumption of any given part. The purchasing team gets blamed for "not knowing what we need" when the real problem is nobody can agree on what anything is called.
Building a Naming Convention
A canonical naming system needs a structure. Here's a practical framework:
The Format
[NOUN] [MODIFIERS] [SPECIFICATIONS]
Where:
- Noun is what the part is (Bearing, Seal, Motor, Valve, Sensor, Belt, Filter)
- Modifiers describe the type (Deep Groove Ball, Hydraulic, Centrifugal, Pneumatic)
- Specifications are the defining dimensions or parameters (6205, 45x55x7, 5HP, DN50)
Examples
| Bad Name | Good Name (Canonical) |
|---|---|
| bearing kecil | Bearing, Deep Groove Ball, 6205-2RS |
| seal gede yang di pompa | Seal, Mechanical, 45x55x7, NBR |
| motor conveyor | Motor, Electric, 5.5kW, 4P, B3 |
| selang angin | Hose, Compressed Air, ID 12mm, WP 10bar |
Rules
- Always start with the noun. Bearing, not 6205 Bearing. Motor, not 5HP Motor. This makes sorting, searching, and grouping consistent.
- Use standard separator characters. Commas are clean. Avoid spaces as separators because they're ambiguous.
- Specifications follow a fixed order. For bearings: type, dimension series, bore diameter. For seals: type, ID, OD, width. The order should be the same across all parts of the same type.
- No abbreviations without a glossary. "BRG" might be obvious to a technician but not to a new hire. If you use abbreviations, publish a glossary. Better yet: don't use abbreviations.
- No location information in the name. "Bearing Line 3" becomes wrong the moment you move the bearing. Location belongs in the inventory management fields, not the part name.
- No supplier names in the part name. "SKF Bearing 6205" assumes SKF is the only acceptable supplier. The part name should describe the part, not who made it. Supplier info goes in a separate field.
The Cleanup Process
If you already have a messy inventory, here's how to fix it:
Step 1: Export Everything
Pull your entire spare parts list into a spreadsheet. All columns: part number, description, quantity, location, supplier, unit cost, everything.
Step 2: Group by Part Type
Sort the list by your best guess at part type. All bearings together. All seals together. All motors together. This makes duplicates visible โ identical parts with slightly different descriptions will cluster near each other.
Step 3: Identify Duplicates
Within each group, look for parts that might be the same. Same specifications with different names. Similar descriptions with matching quantities in different locations. If you're unsure, check the physical part.
Step 4: Assign Canonical Names
For each group of duplicates, choose the canonical name using your naming convention. For unique parts, simply reformat the existing name to conform to the convention.
Step 5: Merge and Consolidate
In your inventory system (or CMMS), merge duplicate part records into the canonical record. Combine quantities. Update stock locations. Delete or archive the old duplicate entries.
Step 6: Enforce Going Forward
The hard part: making sure new parts follow the convention. This requires:
- A written naming standard that's accessible to everyone who enters parts
- Training for storekeepers, procurement, and anyone who creates part records
- Validation in the CMMS โ the system should check that new entries follow the naming convention
- A gatekeeper โ one person (or small team) who reviews and approves new part entries before they go live
Canonical Naming and Your CMMS
This is why naming standards matter so much before a CMMS rollout. A CMMS is designed around the idea that "one part = one record." When you import a messy parts list into a CMMS, you're importing chaos โ and the software can't fix it. It just displays the chaos in a nicer interface.
The sequence matters:
- Clean and standardize your part names first
- Then import into the CMMS
- Then build your PMs, work orders, and BOMs on top of clean data
Do it in reverse โ implement CMMS first, then try to clean the data โ and you'll spend months fighting the system while your technicians lose faith in it.
The Payoff
A canonical naming system isn't exciting. Nobody will congratulate you for it. But the payoff is real:
- Inventory accuracy goes from "approximately sort of" to something you can actually trust
- Search time drops from 10-30 minutes to under 30 seconds
- Duplicate purchases drop by 50-80%
- Downtime from "can't find the part" becomes rare instead of routine
- CMMS adoption improves because the system gives accurate answers
- Procurement can analyze true consumption and negotiate better deals
- New hires can find parts without asking the veteran technician who's been here 15 years
Standard spare part nomenclature is not glamorous. It's the kind of unsexy foundational work that nobody budgets for and everybody needs. But if you're serious about maintenance management โ if you're investing in a CMMS, if you're trying to move from reactive to planned โ clean parts data is not optional. It's the foundation.
See how OpexMX helps you manage spare parts with structured naming and inventory control. Built to turn your parts data from a liability into an asset.