How should a plant reconcile duplicate asset identities between the CMMS and historian?
A duplicate tag can make one failure look like two assets or connect the wrong trend to a work order. Reconciliation needs a governed identity mapping and evidence from the field, not a bulk text replacement.
Establish an authoritative equipment boundary
Define the physical asset, functional location, maintainable unit and instrumentation points. Record which system owns each identity. A CMMS equipment number, engineering tag, historian point and PLC address are different identifiers that may refer to the same physical asset or different components.
Find collisions and ambiguous relationships
Export active and retired tags, descriptions, hierarchy paths, serial numbers, nameplate data and point metadata. Flag one to many and many to one mappings, duplicate serials, reused tags and historical aliases. Do not assume that matching names prove identity. Review drawing revisions, field photographs and loop or equipment schedules.
Approve a canonical crosswalk
Create a durable mapping with canonical asset ID, source system, native ID, effective dates, status, evidence and approver. Preserve original identifiers for audit and back references. Model parent child relationships explicitly so a pump vibration point is not mistaken for the entire pump train. Apply access controls when exposing the crosswalk to analytics or AI tools.
Example: pump train with two tag conventions
The CMMS records pump P 201 as one equipment object while the historian stores motor bearing and pump bearing tags under a common train label. The team validates drawings and nameplates, maps each point to the appropriate component and parent train, and keeps old tag aliases for historical searches.
Test before production cutover
Check representative work orders, trend links, alarm context and maintenance reports. Reconcile counts and exceptions, test asset retirement and replacement scenarios, and assign stewardship for future changes. Do not delete historical source IDs simply to make the mapping table appear clean.
Implementation checklist
- Define equipment and functional location boundaries
- Review collisions using drawings and field evidence
- Approve canonical mappings with effective dates
- Test work order and trend navigation before release
Explore KANE consulting
Discuss practical maintenance and reliability improvements for your facility.
Request a consultation →Related answers: related guidance · additional implementation guidance
Technical references
ISO 14224 equipment reliability data · NIST industrial control systems security guidance