Delayed data insertion occurs when data from a particular sensor is inserted into the ViGIE platform later than what would be expected, according to its sampling time. In other words, the data for a sensor with a sampling time of 5 minutes is expected to be recorded on the platform every 5 minutes.

Therefore, it is necessary to understand at what point the data entered is considered to be delayed:

When the sampling is equal to or bigger than 2 minutes:
Is considered as delayed all the data that is inserted into the platform with a time equal to or greater than 1.2 times the sampling time. For example, for a sensor with a sampling time of 5 minutes, the data will be considered as delayed if it is entered 6 minutes after the last data point inserted.

When the sampling time is smaller than 2 minutes:
Is considred as delayed all the data that is inserted into the platform with a time equal to or greater than 2 times the sampling time. For example, for a sensor with a sampling time of 1 minute, the data will be considered as delayed if it is entered 2 minutes after the last data point inserted.

In both linear and binary graphs, data inserted with a delay is highlighted with a distinct colour, grey. 

Note: Real-time data is always presented in a graph with a coloured line, depending on the parameter.

This visual cue helps to identify instances where data was not received in real-time.

The grey line in these graphs indicates that the corresponding data points were inserted after their actual occurrence. This delay could be due to a variety of reasons, which may include poor signal strength, communication problems with the receiver, physical barriers, some setback in the organisation's network, etc.

Note that a delay in entering the data, represented by the grey lines in the graph, can compromise the alarms generated, since the data will be analysed with a delay.

By interacting with the graph, it is possible to access additional information about delayed data points. Clicking on any grey point along the graph reveals the specific hour and date when that data was inserted into the ViGIE system.

For example, a measurement was initially registered on April 11 at 02:34. However, due to a delay, it was only received and inserted into the ViGIE portal on April 11, 07:01.

This feature is very useful for analyzing time-sensitive data, as it provides transparency regarding the timing of data arrival and insertion, aiding in accurate interpretation.

How can delayed data influence the generation of alarms?

A delay in entering data can compromise the alarms generated as the data will not be analysed at the time it was recorded.

Example: a sensor with a sampling time of 5 minutes has been configured to generate an alarm 15 minutes after exceeding the established limits. Thus, it is expected that after 3 recordings outside the limits, an alarm will be generated. 

In case the data from this sensor is being entered into the platform with a delay of 2 minutes at each recording point, this means that the alarm will only be triggered 21 minutes, (5 min + 2 min) x 3 readings taken, after the limits have been exceeded and not the 15 minutes configured.

At what point do I stop receiving alarms about delayed data?

No alarm is triggered for data that is entered into the platform with a delay of more than 8 times the sampling time of the sensor in question.

Example: for a sensor with a sampling time of 5 minutes, if a data point is inserted into the platform 40 minutes after it has actually been recorded, it will not be counted towards the configured alarm and no alarm will be triggered even if this data point has recorded a value outside the established limits.

Nevertheless, as mentioned above, this data is displayed in grey on the graph.