Purpose
Consistent naming is the foundation of reliable master data. This standard defines how Object Types and their components are named so identical assets carry identical descriptions no matter who created the record or which site loaded it.
Scope
- All Object Types (asset families) in the CMMS
- All component descriptions attached to Object Types
- Class + Characteristic values used for technical spec
- Applies to greenfield loads, migrations and ongoing maintenance
Key Terms
| Term | Meaning |
|---|---|
| Object Type | Classifier that groups assets with the same technical function (e.g. Pump — Centrifugal Overhung). |
| Component | A repairable/replaceable part of the object (e.g. Bearing, Seal, Coupling). |
| Modifier | Attribute that distinguishes similar components (position, orientation, material). |
Sections
- 01
Object type naming pattern
IntentForce a consistent word order so lists sort and search cleanly.
Actions- Pattern: NOUN — SUBTYPE — DUTY (e.g. PUMP — CENTRIFUGAL — SLURRY).
- Noun always singular, always uppercase.
- Subtype describes the mechanical class (centrifugal, positive-displacement, gear).
- Duty describes the service (slurry, clean water, process, dosing).
What Good Looks Like- Run a naming compliance dashboard monthly — flag any drift immediately.
What Bad Looks Like- Free-text descriptions — one asset appears three different ways.
- Site-specific abbreviations creeping into descriptions — reporting across sites becomes impossible.
- 02
Component naming pattern
IntentStandardise the sub-assembly nouns so BOMs and RCFAs align.
Actions- Pattern: NOUN — MODIFIER (e.g. BEARING — DRIVE END).
- Use the ISO 14224 component list as the master noun catalogue.
- Modifiers are drawn from a controlled list: DRIVE END / NON-DRIVE END, INBOARD / OUTBOARD, UPPER / LOWER, LH / RH.
- No embedded part numbers or serials in the description — those belong on the material master.
What Good Looks Like- Run a naming compliance dashboard monthly — flag any drift immediately.
What Bad Looks Like- Free-text descriptions — one asset appears three different ways.
- Site-specific abbreviations creeping into descriptions — reporting across sites becomes impossible.
- 03
Language & punctuation rules
IntentRemove ambiguity from search and reporting.
Actions- UK English spelling (analyse, colour, tonne).
- En-dash (—) separates the segments; no commas, slashes or ampersands.
- No abbreviations except an approved list (HV, LV, DC, AC, PLC, VSD).
- No trailing spaces, tabs or hidden characters.
What Good Looks Like- Publish the approved noun and modifier catalogue on the site intranet.
- Run a naming compliance dashboard monthly — flag any drift immediately.
What Bad Looks Like- Site-specific abbreviations creeping into descriptions — reporting across sites becomes impossible.
- 04
Governance
IntentKeep the standard alive after the initial load.
Actions- The Data Steward owns the noun catalogue and approved abbreviation list.
- New object types are proposed via a data change request, not created directly by end users.
- Master data audits reject records that fail the pattern; they are corrected, not deleted.
What Good Looks Like- Publish the approved noun and modifier catalogue on the site intranet.
- Run a naming compliance dashboard monthly — flag any drift immediately.
What Bad Looks Like- Free-text descriptions — one asset appears three different ways.
- Site-specific abbreviations creeping into descriptions — reporting across sites becomes impossible.
Best Practices
- Publish the approved noun and modifier catalogue on the site intranet.
- Run a naming compliance dashboard monthly — flag any drift immediately.
- Train new planners and reliability engineers on the standard in their first week.
Common Pitfalls
- Free-text descriptions — one asset appears three different ways.
- Site-specific abbreviations creeping into descriptions — reporting across sites becomes impossible.
- Editing existing descriptions in bulk without a change record — history is broken.