This article introduces the major concepts involved in EnOS IoT Hub.


A model, or thing model, is the abstraction of the features of an object that is connected to IoT. The model defines the features of the object’s attributes, measure points, services, and events. For more information, see Thing Model. A model can be associated to multiple products.


A product, is a collection of devices with the same features. The product enables you to manage collection of devices that derive from the same model while differ in terms of deployment. For example, smart bulbs product A and B.

On the basis of the model, a product further defines the communication specifications for the device to connect to the internet of things, such as the secure authentication mechanism and data format. For example, collection A and collection B might be deployed in different network environment, therefore, requires the device telemetry to be transmitted in different format. Binary data can save up to 75% bandwidth than JSON.


A device is the instance of a product. A device is created from a product so that it inherits not only features defined by the model, but also the communication features, aka the device key-secret pair and device certificate used for secure communication.


An asset is the instance of a model. An asset is created from a model so that it inherits features defined by the model.

An asset can be:

  • A single device, such as an inverter.
  • A group of devices, such as a wind farm. The model of a wind farm might define the overall active power and cumulative power generation of the site. However the data of the 2 measure points are not directly from “connection” as single devices do, but the aggregation of all devices in the site. In this case, the site does not need to have device key-secret pair for site-level connection.

A device is an asset, but an asset is not necessarily a device. For more information, see Asset Tree.