Asset Type Tree Structure

Identify and build the asset types in the asset type tree before building the asset tree.

The asset type tree is structured with folders for the following basic groups of asset types:

  • Functional units, which are used to build sub assemblies but can operate on their own.
  • Sub assemblies, which are used to build machines.
  • Machines, which are used to build production lines.
  • Production lines

Use one of two methods to build the asset type tree: top-down or bottom-up.

Top-down method

Build the asset types in this sequence if using the top-down method:

  1. Production lines or offices.
  2. Machines or office equipment found in the production lines or offices.
  3. Sub assemblies or assemblies that make up the machines or office equipment.
  4. Functional units or units that make up the sub assemblies or assemblies.

Keep in mind

Create the asset types for reusable items (functional units or units) as the construction of the higher-level asset types are broken down, and then return to the higher-level asset types to complete their development.

Bottom-up method

Build the asset types in this sequence if using the bottom-up method:

  1. Functional units or units that make up the sub assemblies or assemblies.
  2. Sub assemblies or assemblies that make up the machines or office equipment.
  3. Machines or office equipment found in the production lines or offices.
  4. Production lines or offices.

Keep in mind

  • Configure the smallest asset type building blocks (functional units or units) first and then use them to create bigger asset type building blocks, until the asset types (on which assets will be based in the asset tree) are created.
  • The properties and components of an asset type building block are inherited by the asset types that use the building block.
  • The development of the asset type building blocks can be confirmed as their configuration is completed.

Elements in the asset type tree

The asset type tree comprises of these elements:

  • asset type folders
  • regular asset types
  • in-place asset types
  • placeholder asset types
  • regular asset type components
  • placeholder asset type components
  • regular asset type tasks
  • auxiliary asset type tasks.

Nodes in the tree structure

A node is a point that gives structure to the asset type 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 type, regular asset type component or regular asset type task. The node icons in a tree structure are always displayed.

Inheritance in the asset type tree

In the asset type tree, inheritance occurs when an asset type is re-used to create a sub item of the asset type or an asset type component of another asset type.

An ancestor is an item higher up in the hierarchy of the asset type tree structure. A descendant item inherits properties and sub items that are configured in the ancestor’s asset type model. So, the ancestor item determines the properties of the descendant item, and the descendant inherits its properties and sub items from its ancestor.

When an asset type has descendant sub asset types, then the sub asset types inherit the properties and items in the asset type model of their ancestor asset type. When an asset type is used to create an asset type component, then the asset type component inherits the properties and items in the asset type model for the asset type.

Keep in mind

An item in the asset type model for a descendant asset type cannot be deleted; it must be deactivated if it is not required.

Guidelines

Keep the asset type tree structure as simple as possible by following these guidelines:

  • Building the structure so that information is updated in a single place.
  • Incorporating the relationship between child asset types that inherit everything from the parent asset type.
  • Incorporating the relationship between parents, their respective child regular asset type components and placeholder asset type components.
  • Avoiding having too many asset type tree levels, such as folders, asset types and asset type components.