Asset Hierarchy User Guide

Overview

The Asset Hierarchy module gives you a structured, top-down view of all your physical assets organised by location. It lets you explore your entire asset landscape — from high-level sites down to individual components — and take action directly from any level in the hierarchy.

Use the Asset Hierarchy to quickly understand the operational status of a site, asset, or subassembly, log defects, create work orders, and navigate to related records without leaving the page.

Where to Find It

The Asset Hierarchy is accessible from the main navigation menu. Click Asset Hierarchy in the left-hand sidebar to open the page.

Understanding the Hierarchy Structure

Assets are organised into four levels. Each level is nested inside the one above it:

Level	Description
Site	The top-level physical location (e.g. a wind farm or plant).
Asset	A major piece of equipment within a site (e.g. a turbine).
Subassembly	A functional group of parts within an asset (e.g. a gearbox). Subassemblies can be nested inside other subassemblies.
Component	The lowest-level item within a subassembly (e.g. a bearing). Components are leaf nodes — they do not have children.

Page Layout

The Asset Hierarchy page is split into two panels:

Left panel — Tree
Displays all sites and their nested assets in an expandable tree. This is your primary navigation tool.

Right panel — Detail view
Shows contextual information for the node you have selected in the tree, including statistics and a table of direct children.

Navigating the Tree

Expanding and collapsing nodes

Click the arrow icon next to any site or asset to expand it and load its children. Children are fetched on demand — the first time you expand a node, a brief loading indicator appears.

Selecting a node

Click a node's name in the tree to select it. The detail panel on the right updates immediately to show that node's information. The first node in the tree is selected automatically when the page loads.

Navigating up

From the detail panel header, click the Navigate Up button (chevron-left icon) to move the selection to the parent of the currently selected node. This is useful when you have drilled deep into the tree and want to step back one level.

Searching

A search field at the top of the tree filters nodes by name as you type. The search applies to the currently visible level.

Reading the Detail Panel

When you select a node, the right panel shows three sections:

Header

Displays the node name, its external ID, and its hierarchy level (Site, Asset, Subassembly, or Component). From the header you can:

Edit the node — opens the edit form for that asset or subassembly.
Create a defect — opens the defect form pre-filled with the node's location.
Create a work order — opens the work order form pre-filled with the node's location.
Navigate up — moves selection to the parent node in the tree.

Note: The Create Defect and Create Work Order options are only visible if you have the corresponding permissions (CREATE_DEFECT and CREATE_WORKORDER). Contact your administrator if these options are missing.

Statistics row

Below the header, a row of stat cards gives you an at-a-glance operational snapshot for the selected node. All counts include records linked to the node itself and all of its descendants.

Stat	What it shows
Permits	Total permits associated with this node.
Work Orders	Total work orders linked to this node. Clicking the card opens the Work Order list filtered to this node.
Defects	Total open defects on this node and its children.
Personnel	Number of personnel currently assigned to this node.
Planned Activities	Scheduled activities due today, tomorrow, and in the next 7 days.

Statistics load asynchronously. A loading indicator is shown in each card until the data is ready.

Child table

The child table lists the direct children of the selected node:

For a Site: lists its Assets.
For an Asset: lists its Subassemblies.
For a Subassembly: lists its child Subassemblies or Components.
For a Component: no children are shown (leaf node).

Each row in the table shows the child's name, type, and its own Open Defects count. You can sort by any column header.

Row actions

Each row in the child table has a context menu (three-dot icon) with the following actions:

Open — navigates to the full detail record for that child.
Edit — opens the edit form for that child.
New Defect — creates a defect pre-linked to that child.
New Work Order — creates a work order pre-linked to that child.

Creating a Defect from the Hierarchy

Select the relevant node in the tree (Site, Asset, Subassembly, or Component).
In the detail header, click the ⋮ Actions menu and select Create Defect.
The defect form opens with the location pre-filled. Complete the remaining fields and save.

You can also create a defect from a child row: hover over the child row, open its context menu, and select New Defect.

Creating a Work Order from the Hierarchy

Select the relevant node in the tree.
In the detail header, click the ⋮ Actions menu and select Create Work Order.
The work order form opens with the location pre-filled. Complete the remaining fields and save.

You can also create a work order from a child row using the same context menu approach described above.

Editing an Asset or Subassembly

Select the node you want to edit in the tree.
In the detail header, click the Edit button (pencil icon).
The edit form for that node opens. Make your changes and save.

Note: Editing Sites is managed separately in the Sites module. The edit action in the hierarchy is available for Assets, Subassemblies, and Components only.

Prerequisites and Limitations

Permissions required

Action	Required permission
View Asset Hierarchy	Standard user access
Create Defect	`CREATE_DEFECT`
Create Work Order	`CREATE_WORKORDER`
Edit Asset / Subassembly	Edit permission for assets or subassemblies

Data requirements

Sites, assets, subassemblies, and components must be created and configured in the system before they appear in the hierarchy.
Statistics (permits, work orders, defects, activities) are pulled live from the database each time you select a node. In large environments, a brief loading delay is normal.

Nesting depth

Subassemblies support recursive nesting (a subassembly can contain other subassemblies before reaching component level).
Components are always leaf nodes and cannot have children.

Performance

The tree loads children on demand (lazy loading). Very large sites with hundreds of assets may take a moment to expand fully.
Permit counts are cached for up to 60 seconds to reduce server load. Changes to permits may not reflect immediately.