Assets
An Asset represents the thing you actually care about — a generator, an HVAC unit, a utility service, a pump, a facility — independent of the Device that happens to be measuring it. Assets let you organize data by business meaning, not by which Device collects what.
Overview
A single Asset can pull data from multiple Devices and Variables. A single Device can serve multiple Assets. The Asset model is the layer that decouples the physical instrumentation from the operational view.
Typical Asset shapes:
- Physical equipment (generators, HVAC, pumps, motors)
- Utility connections (electrical, water, gas)
- Logical groupings of related equipment
- Spaces (buildings, rooms)
- Infrastructure (panels, distribution systems)
Properties
| Field | Type | Notes |
|---|---|---|
| Name | string | Required. |
| Description | string | Optional. |
| Classification | enum | Optional. Unlocks classification-specific features. |
| Attributes | key-value | Custom metadata. |
| Devices / Variables | references | The data sources backing this Asset. |
| Location | reference | Optional. See Locations. |
| Parent / children | references | For hierarchical groupings. |
| Tags | string[] | For flexible filtering. |
Creating an Asset
- Open the Assets section.
- Click Add Asset.
- Enter a name and an optional description.
- Optionally pick a Classification and fill in custom attributes.
- Attach the Devices and Variables that report on this Asset.
- Save.
Organizing Assets
Four ways to structure your Asset library:
- Location — assign each Asset to a Location for site-based filtering and map views.
- Hierarchy — parent-child relationships for facility → equipment → component drilldowns.
- Tags — flexible, overlapping groupings (e.g.
critical,q4-maintenance,tenant-A). - Classification — pick an Asset type that unlocks type-specific monitoring widgets and reports.
Monitoring an Asset
Each Asset has its own detail page that surfaces:
- The Variables it's tied to, live and historical.
- An Asset Dashboard (Asset-level view; the default can be set on the parent Location).
- Active Alarms tied to the Asset.
- Reports generated against this Asset.
- A notification log of recent alerts.
Alarms can fire on threshold crossings (numeric Variable above/below a value) or state changes (Boolean Variable flips). They route to email, SMS, or in-app notifications, configured per user.