Technical Blog Post
From the Maximo Support Desk - Functionality of the Maintain Asset Hierarchy Checkbox
Anyone who is relatively new to Maximo has discovered that there are plenty of checkboxes and seemingly innocuous options to flag, and it's hard to keep track of all the robustness. Pretty sure that's not a word.
Well, here's one... you've probably noticed the Maintain Hierarchy checkbox on your Asset records. This is a very useful one...
The summary is that the Maintain Hierarchy checkbox is optionally used to preserve and manage an asset hierarchy, with regard to location, as well. The functional usage implied from the 3 points below is that you can use it to move a large hierarchy to different locations via the parent asset. Conversely, it can be toggled off for a scenario whereby a child asset, or subset of child assets need to be moved to a different location, or otherwise removed from the asset hierarchy.
- If the Maintain Hierarchy flag on a parent asset in a hierarchy is checked, the child assets cannot be removed from the asset hierarchy. The child assets cannot be moved to a new location.
- When the Maintain Hierarchy flag on a parent asset is unchecked, then the child assets can be removed from an asset hierarchy, and child assets can also be moved to different locations than the parent asset; the parent/child asset relationship remains intact.
- In both scenarios (Maintain Hierarchy flag on parent asset is either checked or unchecked), the child asset locations will be moved to the parent asset location when the parent asset is moved to a new location.
Tom Richardson is an IBM Maximo Support Engineer and frequent contributor to the Asset Management Blog community. For a complete index of links to his articles, visit
Index of articles by Tom Richardson, Support Engineer