Hand off the asset register to a CMMS.
From the project equipment list to a CMMS asset hierarchy ready for owner operations
Handing off the asset register to a CMMS or EAM (Maximo, SAP PM, Infor EAM, Oracle EAM) is the engineering process of restructuring the project equipment list and instrument index into the asset hierarchy the receiving system imports. The CMMS asset hierarchy is typically a 4-to-6-level tree: site, facility, system, sub-system, equipment, sub-equipment. Engineering documents ship flat (one row per tag); the receiving system expects the hierarchy. The handoff is the last engineering document before owner takeover.
Inputs.
- +Master equipment list
- +Master instrument index
- +Vendor datasheet binder
- +CMMS site / facility / system code structure (from the receiving system)
Outputs.
- →CMMS asset hierarchy in the import format the receiving system reads
- →Per-asset attribute set populated from extraction
- →Document-attachment manifest (datasheet PDFs linked by asset GUID)
- →Per-asset classification code mapped from extraction type
- →Validation report: assets requiring manual classification before import
| Aspect | Engineering format | CMMS import format |
|---|---|---|
| Asset row | Flat: one row per tag | Hierarchical: parent / child tree |
| Tag attributes | All columns mixed | Required attributes per system schema |
| Equipment classification | Free text on type | System-specific classification code |
| Datasheet linkage | PDF reference column | Document attachment by GUID |
| Parent-skid grouping | Optional column | Required parent reference |
| Spare parts | Not in engineering scope | Manufacturer parts list per asset |
Step by step.
- 01
Establish the CMMS code structure
Upload the receiving system's site / facility / system code structure. Each engineering asset maps to a leaf in the structure.
- 02
Map extraction type to CMMS classification
Each equipment type (pump, vessel, exchanger, column, tank, blower, compressor) maps to a CMMS classification code (Maximo PM EQTYPE, SAP PM Equipment Category, Infor EAM Class).
- 03
Build the asset hierarchy
Project equipment list rebuilds into the parent / child hierarchy. Package skids become parent assets; sub-equipment becomes child assets. Loose instruments roll up to their connected-equipment parent.
- 04
Link datasheets to assets
Per-equipment datasheet PDF linkages preserve as document attachments. The CMMS import carries the document-attachment manifest.
- 05
Validate before import
Validation report surfaces assets requiring manual classification (no matching CMMS code), assets with no parent (orphans), and assets with conflicting attributes (typically vendor disagreement).
- 06
Ship the import package
Format-specific export: Maximo MIF, SAP PM BAPI, Infor EAM XML. Custom format support through the API for in-house CMMS tooling.
Common questions.
Does this support Maximo MIF format directly?
Yes. Maximo MIF (Migration Integration Format) is one of the export targets. The export carries the asset hierarchy, attributes, and document-attachment manifest in the column shape Maximo imports through the MEA (Maximo Enterprise Adapter) load.
What if the engineering scope doesn't map cleanly to the CMMS classification?
The validation report surfaces unmapped assets. The mechanical engineer and the CMMS administrator review the unmapped set together; the canonical mapping table extends to cover the gaps. Custom mappings persist across future projects.
Is spare-parts data in scope?
Spare-parts data is not in the engineering scope and is not extracted from drawings. The CMMS administrator typically populates spare-parts data from vendor recommended-spares lists after the asset import completes.
Start a workspace.
Upload the source documents, run the workflow, ship the document in the column shape the next consumer expects.