Many industrial operators stay on an aging Inspection Data Management System (IDMS) or spreadsheet patchwork simply because they fear losing twenty years of ultrasonic thickness history and corrosion-rate trends during a migration. When tag names differ between SAP or Maximo, the IDMS, and P&IDs, a naive import creates duplicate equipment and breaks remaining-life calculations.
Current state before intelliSPEC
- Three versions of the equipment register: The EAM (SAP/Maximo) held functional locations for work orders, the legacy IDMS held corrosion circuits and CMLs, and unit folders held PDF inspection reports and isometric drawings that had never been digitised.
- Inconsistent CML and point numbering: Over decades, contractors had added CMLs with conflicting naming conventions (
,,,), making automated corrosion-rate calculation unreliable. - Fear of multi-quarter downtime: Previous software transitions had stalled in 12-month data-cleaning projects with no working field tool.
Configured path
The operator executed a phased migration into intelliVISION, intelliNDT, and intelliINTEGRITY, while keeping two-way work-order integration with its existing EAM.
- ISO 14224 and CFIHOS tag resolution: Equipment tags, piping circuits, and CML hierarchies were mapped into
with deduplication keys and preview validation before commit. - Historical UT reading and baseline verification: Prior thickness surveys were imported into
, which recomputed short-term, long-term, and governing corrosion rates alongside the legacy values so engineers could verify every variance. - Assisted P&ID and PDF extraction: Historical baseline thicknesses (
), design pressures, and materials of construction were extracted from legacy datasheets and P&IDs into structured fields, with each value held for engineer review.
Measured outcome
- Zero lost thickness history: Every historical UT reading, date, and inspector attribution transferred intact, preserving multi-decade corrosion trend lines.
- Reconciled EAM and IDMS spine:
maintains the cross-reference to SAP/Maximo functional locations so findings generate work requests without duplicate asset trees. - Live in weeks, not quarters: Units went live progressively as each area's register passed engineering reconciliation.