Asset Hierarchy Configuration

Asset Hierarchy Configuration

APM is built on the premise that, within your company, there are multiple records that can be organized into a hierarchy. This organization relies on the parent-child relationship between records to represent the fact some records can belong to other records.

The Hierarchy can be modified to reflect custom asset families. However, the baseline configuration relies on the Functional Location family and the fields in each Functional Location record to define which location each represents. Because there is only one Functional Location family, it is used to store data about all of your locations, where the values in each Functional Location record identify which type of location it is.

The baseline configuration assumes that Functional Locations have Functional Locations and that Equipment is found at the lowest levels of Functional Locations. For example, the top level of Functional Locations might represent different sites within the organization; the second level might represent different areas within each site; the third level might represent specific machines within each area. A location representing a machine could be comprised of three pieces of equipment that make up the machine. In this example, equipment would not be directly related to locations that represent sites or areas; equipment would only be directly related to locations representing machines.
Note: You can now set the number of assets to be displayed in asset hierarchy. The Page Size field added in the Asset Hierarchy Configuration workspace defines how many assets should be displayed in the asset hierarchy page. You can set from 100 to 2500 assets to be displayed. By default, the page size is set to 500.

More Details: Baseline Configuration

In the baseline configuration, there are two levels reflected in the Asset Hierarchy: the Root and a secondary level. The primary level of the Hierarchy, the Root, reflects the Functional Location relationships. The second level of the hierarchy reflects Equipment related to Functional Locations. The hierarchy first displays the Root Functional Location, and drills down to child Functional Locations based on your selections. The hierarchy will continue to do so until there are no child relationships for the selected Functional Location. Then, using the criteria defined in the second level, the hierarchy will display Equipment records related to the selected Functional Location.

The baseline configuration is as follows:

  • Root: The primary level of the hierarchy.
    • Parent Family: Functional Location
    • Relationship: Functional Location Has Functional Location(s)
    • Child Family: Functional Location
    • Parent Priority: 0
    • Display Field: ENTY_ID
    • Taxonomy Category: Taxonomy Category
    • Taxonomy Class: Taxonomy Class
    • Taxonomy Type: Taxonomy Type
  • Secondary Level: The second level of the hierarchy.
    • Parent Family: Functional Location
    • Relationship: Functional Location Has Equipment
    • Child Family: Equipment
    • Parent Priority: 0
    • Display Field: ENTY_ID
    • Taxonomy Category: Taxonomy Category
    • Taxonomy Class: Taxonomy Class
    • Taxonomy Type: Taxonomy Type
Important: Equipment or Functional Location records with multiple parent records are not supported in Asset Hierarchy, except when both the following conditions are satisfied:
  • The link to each parent uses a different relationship family.
  • A priority has been defined for each relationship family in the Asset Hierarchy configuration.

To find the duplicate keys, run the below query in APM:

SELECT MV_AST_HRCY_DUP.parent_enty_key
, PAR_FMLY.FMLY_CAPTION_TX "PARENT_FMLY"
, MV_AST_HRCY_DUP.enty_key "CHILD_ENTY_KEY"
, CHILD_FMLY.FMLY_CAPTION_TX "CHILD_FMLY"
, MV_AST_HRCY_DUP.enty_id "CHILD_ENTY_ID"
, MV_AST_HRCY_DUP.the_level
, MV_AST_HRCY_DUP.path
FROM MIV_MI_AST_HRCY_MV_DUP MV_AST_HRCY_DUP
 JOIN MI_FAMILIES PAR_FMLY ON PAR_FMLY.FMLY_KEY = MV_AST_HRCY_DUP.parent_fmly_key
 JOIN MI_FAMILIES CHILD_FMLY ON CHILD_FMLY.FMLY_KEY = MV_AST_HRCY_DUP.fmly_key
ORDER BY MV_AST_HRCY_DUP.enty_key Asc

Access the Asset Hierarchy Configuration Page

Procedure

Access the Operations Manager page, and then select Asset Hierarchy Configuration.
The Asset Hierarchy Configuration page appears, displaying the Asset Hierarchy configuration.

Modify the Asset Hierarchy Configuration

About This Task

Note: You only need to modify the Asset Hierarchy if you want to change the baseline configuration.

Procedure

  1. Access the Asset Hierarchy Configuration page.
  2. For the section you want to use as the primary level of the hierarchy, select Root.
  3. In the Root section, select a value for the following as necessary:
    • Parent Family: The list of all entity families in the database.
    • Relationship: The list of relationship families in the database for the selected parent family.
    • Child Family: The list of entity families in the database that are linked to the selected parent family through the selected relationship family.
    • Parent Priority: The number that defines which relationship is used to determine the parent record that is displayed in the Asset Hierarchy for a child record with multiple parent records.
      For example, suppose an Equipment record satisfies the following conditions:
      • It is a child to a Functional Location record using the Functional Location Has Equipment relationship family.
      • It is a child to another Equipment record using the Equipment Has Equipment relationship family.
      In this case, if the Equipment Has Equipment relationship family has the highest Parent Priority in the Asset Hierarchy configuration, the Equipment record will be displayed as the child to the parent Equipment record, but not as a child to the Functional Location record.
    • Display Field: The list of fields from child families.
    • Taxonomy Category: A list of equipment categories (for example, electrical is a category of equipment).
    • Taxonomy Class: A list of types of equipment classifications (for example, capacitor is a class of electrical equipment).
    • Taxonomy Type: A list of types of equipment (for example, series capacitor is a type of capacitor).
      Tip: In APM, taxonomy refers to the classification systems used for identifying equipment. Equipment taxonomy is broken down into three sections: Category, Class, and Type.
  4. If you want to add another level to the Asset hierarchy, select , and then configure the settings as described in the previous step.
  5. To save the changes (but not apply them), select .
    The changes are saved.
  6. To apply the changes, select , and then select Build Hierarchy.
    The changes are applied and are reflected on the Assets page when the build is complete. Select to view the latest build status.

Schedule an Asset Hierarchy Rebuild

About This Task

You can schedule an Asset Hierarchy rebuild to occur on a one-time or recurring basis. When you schedule the rebuild, the Asset Hierarchy is rebuilt based on the schedule. If you have scheduled jobs to import asset data from an external system, we recommend that you schedule the rebuild. Otherwise, the Asset Hierarchy will be updated every time a record in an entity or relationship family in the Asset Hierarchy is created, updated, or deleted.

For information on scheduling a job, refer to Schedule a Job.

Procedure

  1. In the Applications menu, navigate to ADMIN > Operations Manager > Asset Hierarchy Configuration.
  2. Select the Enable Schedule check box.
    A message appears, stating that the schedule configuration is not found.
  3. Select .
    The Edit Schedule window appears.
  4. Provide values in the available fields.
  5. Select Save.
  6. In the Asset Hierarchy Configuration page, select Save.

Results

The Asset Hierarchy rebuild is scheduled. In the Asset Hierarchy Configuration page, the status of the most recent Asset Hierarchy rebuild appears.