There is no clause in ISO 55001 that names a tagging technology or a numbering convention. What the standard requires is that you define your asset attributes and their quality — identification is an enabling practice, not a checklist item. Here's how to build an identification scheme that actually satisfies that requirement.
Barcode, QR code, or RFID: the real trade-offs
| Technology | Durability | Relative cost | Read range / mode | Best for |
|---|---|---|---|---|
| Barcode label | Vulnerable to damage, dirt, misalignment | Very low | Short, line-of-sight, one item at a time | Large populations of lower-value assets |
| QR code | Same as barcode | Very low | Short, line-of-sight, links to full digital records | Assets where richer linked data matters |
| RFID tag | Durable, surface-independent designs available | Higher (tag + reader infrastructure) | No line-of-sight, bulk/simultaneous scanning | Large mobile fleets, rapid audits, high-value assets |
| Metal serial plate | Highest — resists heat, impact, corrosion | Higher unit cost | Visual only, no automated scanning alone | Heavy industrial machinery, harsh environments |
The right choice is risk-based: high-criticality assets warrant durable metal tags combined with RFID; lower-criticality assets can be adequately served by barcode or QR, provided data-quality controls keep labels legible and correctly linked.
Functional location, equipment number, and finance asset number
Coherent asset management requires three distinct but linked identifiers: the functional location (where maintenance is performed), the equipment number (the specific maintainable item installed there), and the finance fixed-asset number (the accounting entity for depreciation, usually living in the ERP system, not the CMMS). A common practical convention uses a three-part format — system code, equipment type, sequential number — such as "CH-01" for Chiller 01 or "AHU-04" for Air Handling Unit 04, with system codes ideally aligning to engineering drawings so the register cross-references design documentation.
Standard taxonomies can reduce ambiguity: ISO 14224 is a nine-level hierarchical equipment classification used heavily in oil & gas, petrochemical, and power generation, while Uniclass serves the UK built-environment/construction sector. Neither is mandatory for ISO 55001 — what matters is that whatever scheme you adopt is applied consistently.
Cleaning up a dirty register before an audit
The most common failure modes: duplicate records for the same physical asset, orphaned assets with no parent hierarchy, misplaced assets at the wrong hierarchy level, incomplete attributes, and — critically — misalignment between the technical register and the financial fixed-asset register. A practical five-phase remediation: (1) export and flag duplicates/orphans without making changes yet, (2) classify each record by status, (3) standardize naming conventions, (4) merge duplicates while preserving maintenance history, retire orphaned assets with decommission dates, and reparent misplaced ones, (5) validate results against cost-per-asset and maintenance-schedule reports. This is exactly the kind of population-wide cleanup a wall-to-wall count and re-tag program produces as a natural byproduct.
Where CPCON fits — and where the client decides
RFID/barcode tagging and wall-to-wall physical counts are how an organization builds and validates the attribute data (unique ID, location, condition, hierarchy position) that ISO 55001's information/data clauses call for — see the full clause detail in Information Requirements & Documented Information. CPCON does not decide which taxonomy the client should adopt and does not configure the CMMS/EAM — that's the client's engineering or IT decision. Explore CPCON's asset tagging services or return to the ISO 55001 pillar guide.
Frequently Asked Questions
Does ISO 55001 require RFID or barcode tagging?
No. ISO 55001 requires that the organization define its asset information attributes and quality requirements — it does not prescribe a specific identification technology. The choice between barcode, QR, and RFID is a risk-based decision the organization makes.
What is the difference between a functional location and an equipment number?
A functional location represents where maintenance is performed — a spatial or system position. An equipment number identifies the specific maintainable item installed there. Both are distinct from a finance fixed-asset number, the accounting entity used for depreciation, which typically lives in the ERP system.
How do I clean up a dirty CMMS asset register before an ISO 55001 audit?
Export the full register and flag duplicates and orphaned assets first, without making changes. Then classify each record, standardize naming, merge duplicates while preserving history, retire orphaned assets with decommission dates, and reparent misplaced assets — validating results against cost and maintenance-schedule reports.
What is ISO 14224 and does my organization need it?
ISO 14224 is a taxonomy standard for reliability and maintenance data, organizing equipment into hierarchical classification levels. It is heavily used in oil & gas, petrochemical, and power generation, but is not mandatory for ISO 55001 — organizations can adopt any consistent taxonomy.
Can CPCON tell us which asset numbering scheme to use?
No — the taxonomy decision (ISO 14224, Uniclass, or a custom scheme) belongs to the client's engineering or IT function. CPCON executes the physical identification, tagging, and reconciliation work within whatever scheme the client has chosen.
Put a durable, ISO 55001-ready identification scheme on the floor
CPCON tags industrial, healthcare, and government asset fleets at scale — durable RFID and barcode identification, reconciled against your register, within whatever taxonomy your organization has chosen.
Explore CPCON's fixed-asset count & tagging services
