Asset Identity for CMMS Integration
CMMS integration depends on stable asset identity. A work order has limited value when the asset reference cannot be matched to the building, floor, room, system, equipment, Inspector object, or digital twin context that operators use.
Use this guide to prepare MDM alignment before exposing CMMS records to operators or AI Agent workflows.
Identity Flow
Prerequisites
| Requirement | Why it matters |
|---|---|
| Source asset inventory | Each CMMS provider must expose asset IDs, names, locations, and parent relationships |
| Location hierarchy | Buildings, floors, rooms, zones, lines, or systems must be represented consistently |
| Alias strategy | Source IDs from CMMS, BMS, ERP, Inspector, and model assets need a shared matching plan |
| Steward owner | Ambiguous matches need review by a customer or project data owner |
| Retired asset policy | Historical work orders may reference retired, renamed, or replaced equipment |
| Confidence threshold | Automated matching must route low-confidence results to review |
Source Data Inputs
| Input | Use |
|---|---|
| CMMS asset table | Source asset ID, asset name, parent, location, equipment type, status |
| Work-order asset reference | Connects each work order to an asset, location, system, or functional location |
| BMS or historian tags | Links operational signals to the same equipment or system |
| Inspector records | Links inspections, alerts, stations, QR codes, and work orders |
| Model asset references | Links digital twin objects, BIM/CAD model elements, and scene context |
| Alias table | Stores cross-source identifiers for the same asset |
| Steward decisions | Records manual match, split, merge, re-point, and rejection decisions |
Identity Model
| Entity | Example use |
|---|---|
| Site | Campus, factory, plant, building group, or data center |
| Building | Building-level operations and reporting |
| Floor or zone | Space-level work routing and inspection planning |
| Room or area | Local work-order location and evidence context |
| System | HVAC, electrical, fire safety, water, compressed air, production support |
| Equipment | Pump, AHU, chiller, UPS, conveyor, tool support asset |
| Component | Motor, filter, valve, bearing, controller, sensor |
| Digital twin object | 3D, BIM, CAD, or scene object linked to operational identity |
Matching Procedure
- Import CMMS asset and location records into DFS or MDM staging.
- Import related BMS, Inspector, ERP, and model-asset references when available.
- Normalize names, location fields, equipment types, and source-system codes.
- Create deterministic rules for exact IDs and agreed aliases.
- Use fuzzy or semantic matching for names and descriptions that need review.
- Route low-confidence matches to the steward queue.
- Approve, reject, merge, split, or re-point records.
- Publish the reviewed golden asset and alias set.
- Re-run work-order fusion after identity changes.
Steward Review
| Review case | Action |
|---|---|
| One source asset maps to one golden asset | Approve the match |
| Multiple source assets describe one physical asset | Merge aliases into one golden asset after owner approval |
| One source asset represents several physical assets | Split into separate golden assets and re-point work orders where needed |
| Work orders point to retired equipment | Re-point to the replacement asset when the customer approves the rule |
| Location differs across systems | Review site hierarchy and preserve the source location in audit fields |
| Low confidence match | Hold for steward review before operational use |
Expected Output
The identity package should include:
- golden asset and location records;
- CMMS alias mapping;
- BMS and Inspector alias mapping where available;
- model-asset or digital twin binding where spatial context is needed;
- steward decision records;
- rejected or unresolved match list;
- refresh cadence for identity updates.
Validation Checklist
- Open and closed work orders resolve to the intended asset or location.
- Provider asset ID and common asset ID are both visible for audit.
- Retired and renamed assets have clear handling rules.
- Predictive Maintenance signals and CMMS work orders point to the same equipment identity.
- Inspector alerts and work orders can be joined through the reviewed asset identity.
- AI Agent answers cite the same asset identity used in operator views.
Troubleshooting
| Symptom | Check |
|---|---|
| Work orders appear under the wrong equipment | Alias mapping, parent hierarchy, retired asset rules, and steward decisions |
| Many records stay unmatched | Missing source asset table, inconsistent naming, absent location codes, or low confidence threshold |
| Duplicate assets appear | Merge rules, source-system aliases, equipment type normalization, and parent hierarchy |
| Digital twin view does not open from work order | Model asset binding, component geometry, tenant scope, and asset ID bridge |
| Predictive Maintenance cannot join work history | Equipment ID bridge, signal asset ID, work-order asset reference, and MDM publication state |