What a Template is and what it's made of
A Template (Asset Template) is the blueprint every asset of a given type is created from. If you manufacture or manage multiple units of the same product (e.g. an industrial fridge model, a line of sensors, a standard plant), you define the template once and then create one asset for every real-world unit.
On the template page the main settings are split into distinct sections. A template is made up of:
1. Information
In the Information (or Template information) section you configure the product type identity:
| Field | Required | Effect |
|---|---|---|
| Name | Yes | Template name (e.g. "Industrial fridge"), used in lists and when choosing the type to create an asset |
| Description | No | Free-text explanation of what the template is for |
| Image URL | No | Product preview image (public URL); shown in template lists and as a visual reference |
2. IoT connectivity
IoT connectivity defines how physical devices communicate with Trackle Spaces. Three types are supported:
| Type | When to use it |
|---|---|
| Trackle | Devices using the native Trackle module/SDK. |
| MQTT | Devices that publish/subscribe to MQTT topics. Under MQTT you pick a profile: Generic, Seneca, Siemens Logo or Teltonika RutOS. The profile changes downlink behaviour and the options on telemetry fields. |
| HTTP | Devices that periodically call the Trackle Spaces HTTP APIs (also lets you configure an "offline" timeout). |
The connectivity type is a property of the template: every asset created from that template communicates the same way. Learn more in IoT connectivity.
3. Metadata
Metadata is static information defined at template level and filled in on every asset (e.g. serial number, site, install date). It does not come from the device: you enter it. Learn more in Metadata.
4. Telemetry variables
Telemetry variables (the Telemetry tab) define which data an asset of this template will expose: each variable has a key, a data type, an optional unit of measure, and a flag indicating whether it's writable (i.e. whether you can send commands to the device, not just read values).
Example: an "Industrial fridge" template might have the variables temperature (numeric, °C, read-only), compressor_active (boolean, read-only) and setpoint (numeric, °C, writable).
Learn more in Telemetry variables.
5. Alarm rules
Alarm rules are one or more AND conditions on the template's telemetry variables (e.g. "temperature > 8°C" and "humidity < 40%", for more than 10 minutes) that, when they occur on an asset, generate an alarm in that specific asset's history. Rules are configured at the template level and automatically apply to every asset using it. Learn more in Alarm rules.
6. Template dashboards
Every template can have one or more shared dashboards, visible on every asset using that template. You can also set one dashboard as the "home dashboard": it will be shown first when you open an asset's detail page. Learn more in Dashboard.