Alarm Settings for Inputs
Note: These features can only be accessed by Client Admin users. Your Wildeye devices may be managed by a third party as a service.
Accessing
Input Alarms are accessed by clicking on the Alarms link in any Input Row in the Input Settings page.
Add an Alarm
Alarms can be added from the Input Alarms page. Inputs can have multiple alarms set up on each Input.
The most common Alarm Type is a High or Low Alarm. Accumulation Inputs such as Pulse Counters have additional Alarm types available such as 'Daily Total' alarms.
High/Low Alarm
Condition: "Send alarm if <Input> measures <above/below> <threshold Value> <convert to rate?> in <consecutive number of logging intervals>
eg. Send alarm if Water Level measures above 3 meters in 2 consecutive logging intervals
<Input> Is already populated with the Input Name of the Input you are adding the alarm to.
<above/below> A select box that determines if you are adding a high or a low alarm.
<threshold Value> The threshold value at which the alarm will be triggered. (depending on reset condition)
<convert to rate?> This option is only available for Accumulation Inputs such as pulse counters. For example, a pulse counter that is set to measure gallons of water at a logging interval of 15 minutes. The alarm threshold value is calculated on the measured value. In the aforementioned example, it would be the gallons measured in 15 minutes. The convert to rate option allows the user to select a threshold value as a more intuitive rate in gallons per minute. This also allows the logging frequency to be changed without needing to change the alarm settings.
<consecutive number of logging intervals> Typically set to 1. This setting can be used if there is some noise in the measured value and the user would like multiple consecutive readings to be at the alarm threshold value before triggering the alarm.
Reset Type: Value based (hysteresis) or Time based. Once the alarm threshold value has been triggered then no further alarms will be triggered until the reset condition has been satisfied. If Value type then the measured value will need to be reached. If Time based then the selected time will need to pass.
Recipient List: An optional Recipient List to send an alarm to, as managed in the Client Settings section.
SMS recipients: A comma-separated list of mobile phone numbers to deliver alarms to. If a phone number is surrounded in parenthesis () then the alarm will be delivered as a phone call and the alarm message will be spoken using Alexa text to speech.
Email recipients: A comma-separated list of email addresses to deliver alarms to.
Alarm Message: The custom message to be delivered with the alarm. The following tags can be used to insert site/alarm details into the alarm message.
eg “Flow over #alarmvalue L/m for site #sitename”
Tags
Tag | Description |
|---|---|
#sitename | Name of site |
#inputname | Name of Input |
#projectref | Project Reference |
#unit | Unit |
#scadatagid | Scada Tag ID |
#trackerguid | Alarm History Tracker Guid |
#alarmlevel | Alarm level (L1 or L2) |
#alarmdate | When the alarm occurred |
#alarmvalue | Triggering Value |
#alarmsetvalue | Threshold Value |
#alarmsentdate | When the alarm was sent |
#alarmname | Alarm Type |
Disabled?: If selected then the alarm will be disabled. The alarm won’t trigger, and no messages will be sent to any recipient.
Note:
Alarms have the following characteristics and limitations:
A newly configured alarm will be in the reset state initially, i.e., it does not need to cross the reset threshold before it can be triggered.
A newly configured alarm will be triggered if the next data point uploaded is above/below the threshold level, irrespective of whether it was already above/below the alarm threshold when the alarm is configured, i.e., the signal does not have to cross the threshold level.
An existing alarm will only trigger if it is in the reset state and it crosses the alarm threshold.
An existing alarm will only trigger once after each reset.
An existing alarm will be reset when it crosses the reset threshold.
Changing an alarm's configuration will cause the alarm to re-evaluate historical data up to three days ago or the last alarm that has been logged, whichever is the latest.
The alarm process assumes the latest configuration applies to all data, including older data that were logged using the older configuration, including the current log interval setting is used to calculate rates for all logged samples, irrespective of what the actual log interval was; the actual log interval might be different because a swipe triggered an extra log, or the log interval setting was changed. This could cause false alarms after changing configurations.
Alarms are evaluated based on a single log sample at a time only.