The Energy Management Platform allows to create several types of alerts that will help you to detect some inefficiencies on your facility. In this article, you are going to learn all about the No Data alert. For more information about all types of alerts, click here.
First, here is a bit of context information:
Every reading that is inserted in the platform has two different and independent time concepts associated:
- Insertion-time: The time the reading is inserted in the platform.
- Reading-time: The tune related to the reading itself (ex: the temperature at 9:00h).
What is raw data?
Raw data is associated with a specific instant in time.
Ex: A reading was sent to the platform at 8:25, providing information about the electricity reading displayed in the meter at 8:15 h.
What is aggregated data?
Aggregated data is data that describes what happens during a time interval.
Ex: A reading was sent to the platform at 9:10, providing information about the energy consumption between 8:00 and 9:00.
What is a No Data alert?
The No Data alert is very useful to know when there's no data coming into the EMS from a specific device.
Generate a No Data alert
In order to create a No Data Alert, you must go to Alerts and click on New alert.
- Alert name: write a distinctive name for the alert
- Tolerance: Define after which time period without receiving any data you want to be notified (1h, 3h, 12h...)
- Applies to devices: select the devices for which the alert is going to be applied.
- Enabled?: the alert can be enabled or not.
- Notifications: select the frequency at which you want to be warned, daily, hourly etc.
- Email: Select if you want to receive the alert by mail and to which users you want them to be sent.
How does it work?
The alert takes the tolerance range you configured (X hours), and checks if there’s any data between now and in those previous hours (using the reading time).
The data taken into consideration for this analysis in the one that is inserted (not calculated) in the platform, and the reading-time (not inserted-time). Depending on the type of data:
- If raw data is inserted, the data timestamp is considered.
- If aggregated data is inserted, the final timestamp of the time interval is considered.
Example: Alerts triggered
There's no data in the alert tolerance range, so the alert is triggered both in the aggregated data and in the raw data examples.
Example: Alerts not triggered
There's data in the alert tolerance range, so the alert is not triggered.
- Aggregated data: even though the reading time interval starts before the alert tolerance range, it ends inside the range. Being this case, the data absence starts only at that point, and it's within the alert tolerance range.
- Raw data: there's a reading inside the tolerance range, and the exact timestamp is considered.
Forecast readings are disregarded in terms of the alert evaluation:
If there are only forecast readings in the alert tolerance range, the alert will be triggered anyway.
What is a forecast reading?
It is a reading that, at the moment the data is inserted in the platform, the reading-time is superior to the insertion-time.
A reading inserted in the past with a future reading-time.
A reading inserted now with a future reading-time.
A reading inserted in the past with a past reading-time, but that is superior to the insertion time.