Maximo Asset Hierarchy BIRT Report

Asset Hierarchy is used to define the physical or functional parent-child relationship of assets created within the Location application. 

The real advantage of developing such location/asset hierarchy is to easily locate an asset to perform work orders, grouping of assets under a location to represent plant systems, etc.,

OOB Maximo has Location Hierarchy by system report, but it doesn't have similar report to display the Asset Hierarchy. 

A report for asset hierarchy using ASSET and ASSETANCESTOR tables is available in the link asset_hierarchy.rptdesign

The flowchart describes the nested table structure used to design the hierarchy report.

                                               

Configure the dataSet with a Parameter to accept the value from the parent table design

Parent parameter should be linked to the assetnum of parent table

Always use - Auto Layout - Fixed Layout would cause the results go in separate pages.

Report Parameters need to be filled with attribute (siteid,location,assetnum) and lookup values (site,locations,asset) to let the user choose values from the lookup.

 

Report Output:

2) We can also build an Asset Hierarchy Data structure using a SQL query 

SELECT

    level,  assetnum,  parent,  lpad (' ', level * 4, ' ') || assetnum,

    description,  location,  siteid

FROM asset

WHERE  siteid = 'BEDFORD'

START WITH siteid = 'BEDFORD'  AND parent IS NULL AND children = 1 

CONNECT BY PRIOR assetnum = parent

References:

maximo-asset-hierarchy-sql

ibmtechexchange_community_post

designfile_asset_hierarchy.rptdesign

importance-of-asset-location-hierarchies/