Asset Hierarchy

Every site in Fleetera contains a hierarchy of assets that mirrors the physical structure of your installation. Assets are organized in a tree where each asset can have child assets nested to any depth.

Structure

A site itself is the root of the tree. Under it, you build the hierarchy that represents your physical layout. The structure depends on your industry and installation. Here are examples from different industries:

Manufacturing facility:

Automotive Plant North (Site)
├── Production Line A
│   ├── CNC Machine 001
│   │   ├── Spindle Motor
│   │   └── Coolant System
│   ├── Robotic Welder 001
│   └── Conveyor System
├── Production Line B
│   ├── CNC Machine 002
│   └── ...
└── Utility Room
    ├── Air Compressor
    └── Chiller Unit

Renewable energy site:

Wind Farm Alpha (Site)
├── Turbine 001
│   ├── Generator
│   ├── Gearbox
│   └── Pitch System
├── Turbine 002
│   ├── Generator
│   ├── Gearbox
│   └── Pitch System
└── Substation
    └── Transformer

Water treatment facility:

Water Treatment Plant (Site)
├── Intake Station
│   ├── Raw Water Pump 001
│   └── Raw Water Pump 002
├── Filtration System
│   ├── Filter Bank A
│   └── Filter Bank B
└── Distribution Pump House
    ├── Distribution Pump 001
    └── Distribution Pump 002

There is no limit on nesting depth. You can structure the hierarchy to match your physical installation as closely as needed.

Tree view

The Asset Hierarchy page (under Model in the site sidebar) displays the tree as an interactive component. Assets with children show folder icons; leaf assets show file icons.

Key features of the tree view:

• Expand and collapse — click on any branch to show or hide its children. The first level is expanded by default when you open the tree.
• Search — type in the search field to filter assets by name. Matching assets and their parent branches are automatically expanded.
• Status indicators — small colored dots appear next to leaf assets: green for active, yellow for maintenance, gray for inactive.
• Category badges — each asset shows its category as a badge.
• Alias — displayed in monospace text next to the asset name.

Actions in the tree

Each asset in the tree has an actions menu (three-dot icon) with the following options:

Uniqueness rules

Asset names and aliases must be unique among siblings — that is, within the same parent. Two assets at different levels of the hierarchy can share the same name, but two assets under the same parent cannot.

• (tenant, parent, name) — unique
• (tenant, parent, alias) — unique

How hierarchy relates to other features

• Connectors — a connector attached to a parent asset is automatically inherited by all its descendants, unless a descendant has its own direct attachment. When an asset is moved to a new parent, its inherited connectors are recalculated from the new parent while direct attachments are preserved. See connector inheritance.
• Templates — you can instantiate an entire template hierarchy as a subtree of assets in one operation.
• Deletion — deleting an asset cascades to all its descendants. See managing assets.