Platform Overview

Entities #

In Controllino Cloud, there are several types of entities that we first need to understand before we can dive in deeper into the Cloud. This is the most important concept to understand and it is highly recommended to learn the concept of entities before starting to connect your devices to the Cloud.

The most important entities in Controllino Cloud are:

  • Users
  • Devices
  • Assets

Users #

Basically, there are two types of users: the user and customer.

A user has full control over the whole application. He can add or delete devices, create assets, dashboards and everything else that is possible in Controllino Cloud. If you are registered to Controllino Cloud, you are a user. Depending on what subscription license you purchased, you can also setup more users that have full control over everything, besides your own.

A customer can only see and manipulate the devices, assets, dashboards and more that he got access for by the user. This means, a customer could be an external company that should only have access to a specific dashboard that shows telemetry data of their devices, or an internal staff member that should only be able to control a special device group.

Each user can create an unlimited amount of customers.

Devices #

A device is basically any piece of hardware that will send some data to the cloud, or receive some data from the cloud. Your devices will be connected through some protocol like MQTT to Controllino Cloud.

Connections are possible through a wide variety of ways. If your device can transmit data over MQTT, HTTP or CoAP, through WiFi, Ethernet or similar, you can use it with Controllino Cloud out-of-the-box. Many Arduino boards with internet connectivity, ESP32, ESP8266, Controllino or industrial PLCs with internet connectivity have MQTT support packed into the hardware or it is addable through libraries or additional software.

Assets #

Assets are like “groups” that are related to other devices or even assets. For example, an asset could be “Factory Building”, which then again contains two assets called “Building A” and “Building B”, which then again can contain devices like temperature sensor devices, moisture sensor devices and so on.

Entity Data #

Each entity can have two types of data variables. It can have Attributes and Time-series data. Please see the explaination below to learn about the differences between these two types.

Attributes #

Attributes are values that don’t get updated often or don’t need to be “real-time” – for example the serial number of a device or the current firmware version.

Examples:

  • Serial Number: ABC12345
  • Firmware Version: 1.01B
  • Latest Update Date: 20.05.2021

So if you have any value that you would like to send to the Cloud that represents the above explaination, use Attributes.

Time-series data #

On the other hand, we have time-series data – this is the typical data that you want to want to send over to a cloud from a sensor or something similar.

Examples:

  • Temperature: 20,5 °C
  • Wind speed: 3 Knots
  • Battery level: 48%
  • Distance: 32m
  • GPS Coordinates: 10.39483, 28.39458

…and so on. Basically any data you would like to measure on a time scale (every minute, every hour, etc.) is considered time-series data.

Relationships between Entities #

Each entity can also have relations or “connections” to other entities.

Examples:

  • Entity A contains Entity B (e.g. Factory Building 1 contains Weather Sensor 42)
  • Entity A owns Entity B (e.g. John Doe owns Moisture Sensor 1)
  • …and more

This topic will also be detailed in other tutorials.