Display Data with Asset Hierarchies

Build displays that dynamically re-bind to any asset — one template, many assets. Instead of wiring components to fixed tags, you train them against an asset's attributes, so the same display works for every pump, heat exchanger, or unit in your hierarchy.

In this section

• Understanding Asset Hierarchies — how the AF / asset tree is structured and how IOTA navigates it.
• Training Components — make components asset-relative so displays work for any asset in the tree. Train vs. Train and Add explained.
• Actions & Interactions — triggers and interaction connections that let one component drive another (for example, a tree selection updating a chart).
• Navigation Between Displays — link fleet overviews to detail displays and pass the selected asset.
• Asset Groups — replicate one layout across a whole fleet of assets in a single component.

What's Next

Start with Understanding Asset Hierarchies, then train your first component. When your displays pull from more than one data source, see Merging Data Sources.

Related

• Understanding Asset Hierarchies — how asset models work
• Training Components — bind components to an asset
• Asset Groups — replicate a display across many assets