Hand off the asset register to a CMMS.
From the project equipment list to a CMMS asset hierarchy ready for owner operations
What this covers.
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.
By Tagsight Team·Published Aug 4, 2026
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
- Validation report. Assets requiring manual classification before import
Engineering document vs. CMMS import shape
| 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 |
The procedure.
- 01Establish the CMMS code structureUpload the receiving system's site, facility, system code structure. Each engineering asset maps to a leaf in the structure.
- 02Map equipment to CMMS classesEach equipment type maps to a classification code in the receiving CMMS.
- 03Build the asset hierarchyProject 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.
- 04Link datasheets to assetsPer-equipment datasheet PDF linkages preserve as document attachments. The CMMS import carries the document-attachment manifest.
- 05Validate before importValidation report surfaces assets requiring manual classification, no matching CMMS code, assets with no parent, orphans, and assets with conflicting attributes, typically vendor disagreement.
- 06Ship the import packageThe asset register exports for IBM Maximo and SAP PM. Integration with in-house CMMS tooling is set up with you.
Common questions
Does this export for IBM Maximo.
Yes. The asset register exports for IBM Maximo and SAP PM. How it loads into your system is set up with you.
What if the engineering scope doesn't map cleanly to the CMMS classification.
Assets that do not map cleanly are listed for review. The mechanical engineer and the CMMS administrator resolve them together before import.
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.
Related.
Upload a drawing.
Upload the source documents, run the workflow, ship the document in the column shape the next consumer expects.