Spare Parts Data Glossary
Plain definitions of spare-parts data terms — supersession, crosswalk, form-fit-function, BOM variants, part status, applicability and more — with where each shows up in your catalog and what to read next.
The vocabulary of spare-parts data is deceptively familiar. Everyone on the team uses “supersession” and “crosswalk,” but when you look at the actual records, the same word means different things in different systems. This glossary gives each term one plain definition, shows where it appears in your data, and links to the deeper resource where it matters most. Claro treats every one of these terms as a typed, sourced relationship or attribute — not a free-text note someone typed into a spreadsheet five years ago.
| Term | Meaning | Where it shows up in your data | Read more |
|---|---|---|---|
| Supersession | A manufacturer replaces one part number with another | Price-list updates, ERP item-master status field, supplier discontinuation notices | What is supersession? |
| Crosswalk | A mapping between two identifier systems (old-to-new, OEM-to-aftermarket, supplier-to-internal) | Spreadsheet mapping tables, cross-reference databases, supplier portals | What is a crosswalk? |
| Form, fit, function (FFF) | Whether a part has the same shape, mounting and performance as another | Engineering change orders, equivalence reviews, substitution approvals | Form, fit and function |
| Exploded view | A diagram showing an assembly’s parts in their spatial relationships, with callout numbers | Parts books, OEM service manuals, PDF catalogs | Exploded view, parts list and BOM |
| Parts list | A table of part numbers, descriptions and quantities for one assembly, usually keyed by position number | Parts books, ERP BOMs, service documentation | Exploded view, parts list and BOM |
| BOM (bill of materials) | A structured list of every component in a product; variants include eBOM, mBOM and sBOM | ERP, PLM, MES | Exploded view, parts list and BOM |
| eBOM (engineering BOM) | The as-designed structure from engineering; defines what the product is | PLM, CAD, PDM | Exploded view, parts list and BOM |
| mBOM (manufacturing BOM) | The as-built structure; includes process steps, tooling and shop-floor sequences | MES, ERP production module | Exploded view, parts list and BOM |
| sBOM (service BOM) | The as-maintained structure; lists the replaceable parts a field technician needs | Service manuals, aftermarket catalogs | Exploded view, parts list and BOM |
| Position / callout number | The reference number on an exploded view that links a visual part to its row in the parts list | Parts-book diagrams, assembly drawings | Position number and callout number |
| Interchangeable | Two parts can replace each other with no modification; a strong claim requiring evidence | Engineering approvals, cross-reference databases | Interchangeable vs equivalent vs compatible |
| Equivalent | A part that meets the same specification from a different source, with varying degrees of evidence | Substitution lists, procurement alternatives | Interchangeable vs equivalent vs compatible |
| Compatible | A part that works alongside another without replacing it | Cross-sell lists, accessory tables, kit contents | Interchangeable vs equivalent vs compatible |
| Successor part | The new part number a manufacturer designates as the replacement for a discontinued one | Supersession tables, ERP replacement-item fields | What is supersession? |
| Last-time buy | A window before discontinuation during which the part can still be ordered | Manufacturer end-of-life notices, procurement alerts | Last-time buy and end-of-life |
| End-of-life (EOL) | The point after which a manufacturer no longer produces or supports a part | Product lifecycle notices, item-master status | Last-time buy and end-of-life |
| NLA (no longer available) | A status meaning the part cannot be sourced from the manufacturer | ERP status fields, distributor availability flags | NLA (no longer available) |
| Wear part | A component expected to degrade in normal use and be replaced on a maintenance schedule | Service BOMs, maintenance plans, wear-item lists | Wear part vs consumable vs kit |
| Consumable | A material used up in operation (lubricant, filter, wiper blade) | Maintenance schedules, consumable reorder lists | Wear part vs consumable vs kit |
| Kit | A pre-packaged set of parts sold and ordered as one unit | BOM kit structures, service-kit catalogs | Wear part vs consumable vs kit |
| OEM (original equipment manufacturer) | The company that designed or brands the finished equipment; usage varies by industry | Part-number prefixes, brand fields, equipment nameplates | OEM vs OES vs aftermarket parts |
| OES (original equipment supplier) | The supplier who manufactured a component for the OEM, sometimes selling the same part under its own brand | Supplier-origin fields, cross-reference tables | OEM vs OES vs aftermarket parts |
| Aftermarket | Parts made by third parties as alternatives to the OEM’s parts; evidence for equivalence varies | Aftermarket catalogs, cross-reference databases, “will-fit” lists | OEM vs OES vs aftermarket parts |
| Applicability | Which machines, models, serial ranges or configurations a part fits | Fitment tables, applicability databases, “fits” columns | Spare parts applicability data |
| Serial range | The production serial numbers between which a specific part version applies | Applicability tables, engineering change records | Spare parts applicability data |
Related
Glossary
What is supersession?
Manufacturer replaces one part number with another — shapes, direction and what to store.
Glossary
What is a crosswalk?
Mapping tables between identifier systems and why spreadsheet crosswalks fail.
Guide
Model supersession chains
Data model, chain resolution, splits, merges and what the old SKU should return.
Guide
Spare parts applicability data
Which machine, model and serial range a part fits.
Claro
See how Claro handles this in production
This concept is one piece of keeping a catalog trusted. See how Claro resolves identity, enriches missing attributes, and validates every update before it reaches your PIM or ERP.
Learn more