The webinterface alows users to create, configure and delete
alerts. An alert can be created on any type of dynamic data
data which is updated periodically. The most common example of a
dynamic data source is data
from sensors in wells or from weatherstations. Such data is typically
collected at discrete intervals (generally between 1 and 60 minutes),
and is then transmitted to the data management system where it is
imported into a database. Note that such data can be considered to be
near real-time, but should not be thought of as truly real time (or
even as data with a fixed
delay between acquisition and availability). There can be several hours
data acquisition and the actual availability of this data in the data
management system. The specific delay is
something which is inherent in the mode of data collection and
transmission (for instance, for many well sensors data collection
happens first to an in well logger, which then transmits data in blocks
of maybe two hours to a central server). What an alert will do is
notify a user when a specific condition occurs.
Currently this happens through an email to the email address associated
Currently only unary
and missing data alerts
alerts could be implemented relatively easy. Unary and missing data alerts apply to a
single datasource. Binary
alerts would apply to two datasources (for
instance, a ratio or a difference between two datasets). Other alerts
(e.g. alerts which would perform a statistical analysis on a dataset)
can be implemented in response to user requests.
A range alert is an alert which tells a user when a value from a datasource goes above or below a user defineable value.
Managing alertsAll alerts are user specific. A user can manage his/her own alerts through the web interface. This allows for the following actions:
- create alerts
- delete alerts
- edit alerts
- activate/deactivate alerts
Activating/Deactivating alertsIn addition to deleting alerts users can also deactivate alerts. An alert which is deactivated is not checked. Once the alert is activated the alert checking will commence when new data arrives.
Trigger actionsAssociated with each alert is a condition which determines what should be done when the alert is triggered. There are three options
- deactivate after trigger: In this case the alert will be deactivated untill the user activates it
- remain active: In this case the alert will remain active. Note that this might result in an email every time new data comes in
- daily digest after initial
trigger: In this case the alert will remain active, but emails
will only be sent on a daily basis.