Migrate the asset master correctly the first time. Maximo LOCATIONS, ASSET, ASSETSPEC, LINEAROBJECT translated to Fusion Functional Locations and Asset Groups with engineering-led hierarchy review. Linear assets, GIS linkage, criticality data all preserved.
Move the asset master wrong and every downstream system — WOs, PMs, meters, inventory — breaks. Move it right and the rest of the migration becomes routine.
In every EAM migration, asset migration is the load-bearing wall. Work orders attach to assets. PMs schedule against assets. Meter readings record against assets. Inventory reservations consume against assets. Get the asset master wrong — collapsed hierarchy, lost classification, missing spec values, broken parent-child — and every dependent migration fails in cascade.
Maximo asset migration is uniquely hard because Maximo's asset model is uniquely flexible. The two-tree structure (LOCATIONS + ASSET parent-child) plus ASSETSPEC sparse attributes plus LINEAROBJECT for linear assets plus GIS coordinates plus criticality scoring plus 15–25 years of organic growth produces an asset catalog that doesn't fit any modern EAM target out of the box. Each Maximo customer's asset model is, in practice, unique.
Syntra ETL's Maximo asset migration starts with hierarchy review — not extract. Before the first load, maintenance engineering, reliability, and operations review the proposed target asset structure side-by-side with the source Maximo structure, mark up changes, sign off the design. Only then does extract begin. The result: zero asset re-work post-cutover, and every dependent migration (WOs, PMs, meters, inventory) lands on a stable foundation.
The specific decisions and capabilities that separate a successful asset migration from a months-long rework cycle.
Maintenance engineering walks the proposed target hierarchy before extract. Levels that carry maintenance meaning preserved; administrative depth collapsed to attributes. Sign-off gates the migration.
CLASSSTRUCTURE/CLASSSPEC mapped to target Asset Group attributes. Sparse-spec rationalisation prevents 800 attributes used by 12 assets from polluting the catalog. Engineering reviews proposed mapping.
LINEAROBJECT, FEATURE, LRM coordinates migrated for transportation, pipeline, water-main customers. Fusion ALM linear asset support, SAP linear asset support, or warehouse-native preserved.
Esri ArcGIS feature-class linkages, ASSETLOCATION spatial references, and REL_GIS extensions maintained through migration. Post-cutover GIS integration resolves correctly.
Asset criticality scoring (PRIORITY, FAILURECLASS, custom criticality fields), Maximo Health reliability scores, and risk-based metadata preserved as standard or extended attributes.
Active retired assets migrated as inactive in target for reliability context; bulk retired assets routed to archive with full regulatory retention. Split configurable per asset class.
A practical workflow that puts engineering review before extract. Typical asset-only timeline: 6–10 weeks.
Discovery engine crawls LOCATIONS, LOCHIERARCHY, ASSET parent-child, CLASSSTRUCTURE, ASSETSPEC density distribution, LINEAROBJECT presence, GIS linkage extent. Output: a complete asset-model profile with proposed target hierarchy.
Maintenance engineering, reliability, and operations review proposed Fusion Functional Location hierarchy, asset attribute mapping, classification rationalisation, and criticality scoring approach. Mark-up integrated, final design signed off.
Pre-built extractors pull ASSET, ASSETSPEC, ASSETMETER, LOCATIONS, LOCHIERARCHY, CLASSSTRUCTURE, CLASSSPEC, LINEAROBJECT, FEATURE, plus all custom asset extensions. Staged as Parquet with row hashes and SITEID/ORGID partitions.
Hierarchy collapse applied, ASSETSPEC mapped to target attributes, sparse-spec rationalisation executed, linear and GIS extensions preserved. FBDI Functional Location and Asset Import payloads generated and submitted to Fusion ESS.
Row-level, structural, and operational reconciliation. Sample high-criticality asset side-by-side review with engineering. Asset register pack signed off; downstream WO, PM, meter migrations cleared to proceed.
The asset migration patterns Syntra ETL sees most often, by industry — and how the engine adapts.
Safety-related component classification (SR vs non-SR), 10 CFR 50.59 evaluation history, and lifetime PM compliance preserved per asset. Indefinite retention for SR assets configured by default.
Tail-number-level airframe structure, life-limited part (LLP) component tracking, AD/SB compliance state, configuration management snapshots — all preserved in Fusion ALM with full FAA traceability.
Linear track inventory (LRM-based), locomotive and rolling-stock asset structure, signaling/PTC asset classification. FRA-aligned PM compliance evidence preserved.
PSM-covered equipment tagging, mechanical integrity inspection program history, RBI (Risk-Based Inspection) classification, full FAILURECODE history per process unit. OSHA PSM retention default.
Generation asset fleet, transmission/distribution linear assets with GIS, BES cyber asset flagging for NERC CIP, capital asset register tied to FERC rate cases.
Water/wastewater main GIS linear assets, treatment plant equipment hierarchy, SCADA-tagged asset identifiers, state utility commission asset register continuity.
Maximo asset migration is the specific subset of EAM migration concerned with moving the asset master itself — ASSET, ASSETSPEC, ASSETMETER, LOCATIONS, LOCHIERARCHY, CLASSSTRUCTURE, and the relationships between them — from Maximo (MAM 7.6.x or MAS 8/9) into a target system (typically Oracle Fusion Asset Lifecycle Management, but also SAP Plant Maintenance, ServiceMax, or Infor EAM). Asset migration is the foundational layer of any EAM migration: without correct assets in place, work orders, PMs, meter readings, and inventory reservations all fail. Syntra ETL's Maximo asset migration is hierarchy-aware: it walks Maximo's two-tree structure (LOCATIONS plus ASSET parent-child) and produces a target asset structure that preserves operational meaning.
Broader Maximo data migration covers all data domains — assets, work orders, PMs, inventory, meters, vendors, labor. Maximo asset migration focuses narrowly on the asset master: the ASSET, ASSETSPEC, LOCATIONS, LOCHIERARCHY, CLASSSTRUCTURE, CLASSSPEC, ASSETMETER, and FAILURECODE tables. Some customers migrate assets only — for instance, when consolidating from Maximo to Fusion ALM but keeping work order execution in a third system (or starting work order history fresh in Fusion). Others use asset-only migration as a phase-one pilot before broader data migration. The asset migration engine ships separately so it can run standalone or as part of a larger Maximo to Fusion migration.
Maximo's asset model has two intersecting hierarchies. LOCATIONS form a top-down tree (site → operating area → unit → child location) with parent-child via LOCHIERARCHY. ASSETs hang off locations but also form their own parent-child structure (engine → gearbox → bearing → seal). Most modern EAM targets use a single Functional Location hierarchy with asset records hanging off leaf locations. Syntra ETL's Maximo asset migration walks both Maximo trees per site, identifies the operational dependency graph (which assets actually need to roll up to which location for cost rollup, criticality scoring, and reliability analytics), and produces a Fusion Functional Location design that preserves the meaningful relationships while collapsing administrative depth into asset attributes or DFFs. Maintenance engineering reviews and signs off the proposed hierarchy.
Yes. ASSETSPEC is the table that holds per-asset attribute values driven by CLASSSTRUCTURE/CLASSSPEC taxonomies. A pump asset might have spec values for impeller diameter, motor HP, suction pressure rating, and a hundred other fields. Syntra ETL's asset migration extracts ASSETSPEC, maps each spec to the target system's asset attribute model (Fusion Asset Group attributes, SAP Equipment classifications, ServiceMax product attributes), and applies sparse-spec rationalisation: spec attributes used by fewer than a few percent of assets typically get demoted to DFFs or extended attributes rather than core fields in the target. The result is a clean target asset catalog without inheriting Maximo's accumulated spec sprawl.
Yes. Asset criticality scoring (PRIORITY, FAILURECLASS, hazard-criticality codes via custom fields), reliability scoring, and asset health KPIs all migrate as either standard attributes or DFFs in the target. For customers using Maximo Health or Maximo APM's reliability scoring, the historical reliability score per asset moves to the target as a time-series attribute alongside the current asset record. This is critical for risk-based maintenance programs and for regulator inquiries that compare current asset condition to historical reliability trends.
Maximo's linear asset extension (LINEAROBJECT, FEATURE, FEATURECLASS, LRM coordinates) is widely used in transportation (rail, highway, pipeline) and utilities (transmission lines, water mains). Syntra ETL's asset migration extracts the linear-asset extension tables and maps them to Fusion ALM's Linear Asset support (or to the target system's equivalent — SAP PM linear assets, GE Digital APM line assets). GIS-linked assets (those tied to an Esri ArcGIS feature class via ASSETLOCATION coordinates or REL_GIS extension fields) preserve their GIS linkage; the spatial reference is migrated alongside the asset record so post-migration GIS integration continues to resolve correctly.
Retired assets (STATUS = DECOMMISSIONED or similar) typically still need to be migrated — both for regulatory retention (NRC, FAA, PSM) and for reliability engineering historical analysis. Syntra ETL's Maximo asset migration routes retired assets two ways: a subset (those needed for active reporting context against current operating assets) migrate to the target as inactive asset records; the bulk move to the Syntra archive where they're queryable for the full regulatory retention window. The split is configurable per asset class — for nuclear safety-related components, retired assets retain target visibility indefinitely; for routine non-critical retired assets, archive-only retention is typical.
Three layers of validation. Row-level: every ASSET, ASSETSPEC, LOCATIONS, LOCHIERARCHY record extracted is hashed at source and re-hashed post-load. Structural: the target hierarchy is walked and compared to the source LOCHIERARCHY and ASSET parent-child relationships — every parent-child relationship is preserved or its absence is explicitly documented. Operational: a sample of high-criticality assets is reviewed by maintenance engineering with side-by-side comparison of source Maximo asset detail and target system asset detail. Sign-off requires all three validations to pass with documented variance explanations. Maintenance engineering signs the asset register pack before WO migration is allowed to begin.
30-minute discovery call. We'll walk through your Maximo asset model — site count, hierarchy depth, classification taxonomy, linear/GIS use, criticality scoring — and design a target asset structure your engineering team will actually sign off on.