Asset Tree Structure

The asset tree is a hierarchical breakdown of an asset's structure and it contains all the technical information about the asset.

If constructed correctly, the asset tree can be a powerful tool to analyse history, analyse failures, produce budgets and many other reports. To support effective reporting, the tree structure must be developed to complement the following items:

  • assets
  • locations
  • cost centres
  • responsible sections
  • asset attributes.

Methods to develop the tree structure

There are three basic methods used to develop an asset tree structure:

  • process driven
  • location driven
  • responsibility driven.

Typically, the design of the asset tree structure will be a combination of a few of the methods discussed below.

Process driven tree structure

This tree structure is also referred to as a functional driven tree structure. Assets within the same process are grouped together, irrespective of their location. This structure works well in smaller installations, as the user needs to know the process well to locate the assets.

Use process driven tree structures in combination with locations for mining, manufacturing and packaging industries.

Location driven tree structure

Assets are grouped according to their physical location. This is the preferred method in most cases as it is logical and intuitive as to where to find assets. Grouping assets per location makes navigation more user-friendly by reducing the number of assets in the lookup lists. This structure caters for a variety of reporting scenarios.

The main driver for using this method is the number of assets required on the lowest level. The lower levels of the tree can vary according to the situation.

If there are several assets on the same level, consider grouping them together to make navigation more user-friendly.

Responsibility driven tree structure

Assets are grouped according to the maintenance section that is responsible for maintaining them. This grouping is similar to the location driven method.

The main driver for using this method is the type of organisational structure. The responsible section divisions may be due to:

  • Large distances between locations.
  • Use of cross-functional, stand-alone maintenance teams.
  • A complex engineering structure with multiple supervisors and mixed work teams.
  • Maintenance sections that are dedicated per process or groups of similar processes.

Elements in the asset tree

The asset tree comprises of these elements:

  • regular assets
  • in-place assets
  • placeholder assets
  • regular asset components
  • placeholder asset components
  • regular asset tasks
  • auxiliary asset tasks.

Nodes in the tree structure

A node is a point that gives structure to the asset tree. Each point in the hierarchical structure is a node. Each level in the hierarchy has an icon that identifies the item that is associated with the node, for example as a regular asset, regular asset component or regular asset task. The node icons in a tree structure are always displayed.

Inheritance in the asset tree

In the physical asset tree, inheritance occurs through instances of an asset type. An asset, its asset components and asset tasks inherit items from the asset type model for the asset type on which the asset is based. So, the asset inherits the properties and items from the asset type on which it is based. Unless otherwise stated, these items are referred to as inherited items.

An item in the asset type model is an ancestor of the corresponding inherited item in the asset model. The ancestor item determines the properties of the descendant item, and the descendant inherits its properties and sub items from its ancestor.

Inheritance is an automatic process in the asset tree. The user has a certain degree of control over what is inherited from the asset type, based on the options and rules that are specified for the asset type in the asset type tree.

Keep in mind

  • Physical assets inherit properties and asset type model items from asset types.
  • Physical assets cannot inherit properties and asset model items from other physical assets.

Ancestors

An ancestor is an item in an asset type model from which other items are inherited in the asset type tree and the asset tree. The ancestor item determines the properties of the descendant item, and the descendant inherits its properties and sub items from its ancestor.

In the asset type tree, an ancestor is an item higher up in the hierarchy of the asset type tree structure from which a descendant item inherits properties and sub items that are configured in the ancestor’s asset type model.

In the asset tree each asset is based on an asset type and the asset inherits properties and sub items configured in the asset type model. An item in the asset type model is an ancestor of the corresponding inherited item in the asset model.

Descendants

A descendant item inherits its properties, sub items and linked detail records from its corresponding ancestor item in the asset type model for its ancestor asset type in the asset Type tree.

In the asset type tree a descendant item inherits properties, sub items and linked detail records from its ancestor item higher up in the hierarchy of the asset type tree structure.

In the asset tree each asset is based on an asset type and the asset inherits properties, sub items and linked detail records that are configured in the asset type model. An inherited item in the asset model is a descendant of its corresponding ancestor item in the asset type tree.

Parent items

A parent item is the node immediately above another node in the hierarchical tree structure of the asset type tree or asset tree. A parent item may also be an ancestor.

Example

The “Pumps” asset type is the parent and ancestor of the “Steam Pumps” and “Kinetic Pumps” asset types, but it is only the parent of the “Casing” component, not an ancestor because a component cannot inherit from an asset type.

Child items

A child item is the node immediately below another node in the hierarchical tree structure of the asset type tree or asset tree. A child item does not inherit anything from its parent item; it inherits everything from its ancestor. A child item may be a descendant but it is not always a descendant.