In Part 1 we established the core paradigm: in IBM Maximo Manage, locations are conceptually permanent while assets are conceptually transient.
Here's what happens when a register ignores that distinction - and what changes when it honours it.
The problems with asset-centric approaches
Many organisations, particularly in the utility sector, have historically taken an asset-centric approach to their register, with complex asset hierarchies. This creates several operational challenges.
1. Maintenance strategy fragmentation. When preventive maintenance (PM) schedules are tied to specific assets rather than locations, every asset replacement triggers administrative overhead. Planners must edit PM schedules, or disable and create new ones, risking gaps in maintenance coverage and increasing the likelihood of human error.
2. Loss of historical context. Asset-centric registers often lose valuable lifecycle data when assets are replaced. Reliability engineers need to see patterns across generations of assets at the same location to identify design issues causing premature failures or non-uniform degradation. When history follows the asset rather than the location, this critical insight disappears.
3. Integration complexity. BMS, SCADA systems and other operational technology typically reference P&ID tags that correspond to locations, not specific assets. When your asset register is asset-centric, integrations become needlessly complex and require constant updates as assets change.
4. GIS synchronisation issues. For utilities managing linear assets (pipelines, transmission lines) alongside point and polygon features (valves, substations), an asset-centric approach creates unnecessary work. Why should a GIS technician update spatial data every time a valve is replaced? The valve's location hasn't changed, only the specific asset installed there.
The location-centric solution
A location-centric asset register flips the script, providing numerous operational advantages.
Streamlined maintenance management. By tying PM schedules to locations rather than assets, maintenance strategies remain stable through asset changes. When you replace a pump, the maintenance schedule continues uninterrupted, you might adjust the next due date, but you don't recreate the entire strategy.
Complete lifecycle visibility. All maintenance history and performance data accumulate at the location level, giving reliability engineers complete visibility across multiple asset generations. This enables true root cause analysis and design optimisation.
Simplified integration architecture. With locations representing P&ID tags and other operational identifiers, integrations with IoT platforms become "set and forget", data flows to the right place regardless of asset changes.
Efficient rotable management. For organisations managing rotable assets (serialised components that rotate between repair and deployment), location-centric registers enable sophisticated swap planning. Maximo Manage's Move/Modify functions can plan asset swaps as part of work orders, automatically updating the register on work completion.
Part 3 turns these benefits into a practical build: the implementation requirements and the path to transition an existing register.