Device Models
A Device Model (also called a Digital Twin Template) is the blueprint that describes an asset type - what telemetry it sends, what thresholds trigger alerts, what commands it accepts, and how its data should be visualised.
Once a model is defined, every device of that type automatically inherits its configuration. One change to a model propagates instantly across the entire fleet.
What You Can Define
Telemetry Properties
Define the full data schema for each asset type:
- Property names, data types, and engineering units (°C, RPM, bar, kWh)
- Display names and value ranges
- Export and import property definitions via Excel for rapid configuration
- Override model-level properties at individual asset level when needed
Alert Thresholds
Set the conditions under which an alert fires:
- Severity levels (info, warning, critical)
- Trigger operators (greater than, less than, equals, etc.)
- Threshold values per property
- Custom acknowledgement reasons to standardise resolution workflows
- Per-asset threshold overrides for fine-grained control
Dashboard Widgets
Bind telemetry properties to visual components:
- Live chart widgets - real-time line/gauge views
- Historical trend widgets - time-series analysis
- Control widgets - buttons and sliders to send commands
- Configuration widgets - read and write device parameters inline
OTA & Reference Documents
- Attach firmware and software packages to a model for over-the-air deployment
- Link reference documents (manuals, datasheets, safety certificates) to any model
Master–Slave Topology
For complex hardware with parent-child relationships (e.g., a main controller + sensor modules):
- Model master and slave positions
- Define slave categories and positional mappings
- Manage slave device registries linked to parent models
Model Lifecycle
| State | Description |
|---|---|
| Draft | Model is being built; changes allowed |
| Frozen | Model is locked for production use; prevents accidental changes |
| Unfrozen | Model re-opened for updates |
| Reset | Model returned to baseline state |
Key Benefits
- Single source of truth - define once, apply everywhere
- Template inheritance - all assets of a type share the same config
- Per-asset overrides - individual devices can override model defaults
- Bulk import - configure device types from Excel in minutes
See also: Real-Time Telemetry to understand how device model properties drive the data pipeline.