Alarms
Set rules so TCS-NET alarms when a value crosses a limit or a device drops offline, and follow each alarm until it is dealt with.
Alarm rules
Go to Alarm, Alarm Rules to add a rule. Each rule watches one tag, or watches whether one device is offline.
| Option | Meaning |
|---|---|
| Condition | Greater than, at least, less than, at most, equal, not equal (numeric tags); on or off (bool tags); offline (a device). |
| Severity | Info, warning or critical. |
| On-delay | How long the condition must hold before it becomes an alarm. |
| Off-delay | How long the condition must be gone before the alarm ends. |
| Buffer | A margin around the limit so a value hovering at it does not make the alarm chatter. |
| Require acknowledgement | On by default: an operator must confirm they have seen the alarm. |
Four states
Every alarm is in one of four states, depending on whether the condition is still there and whether an operator has acknowledged it.
| State | Meaning |
|---|---|
| Active, unacknowledged | The condition is there and nobody has acknowledged it. |
| Active, acknowledged | The condition is there but someone has taken it on. |
| Cleared, unacknowledged | The condition went away before anybody looked: it still asks for attention. |
| Cleared, acknowledged | Finished. |
Alarm Monitor
The Alarm, Alarm Monitor page lists the events for you to acknowledge. The sidebar shows how many are unacknowledged, and a notice pops up when a new alarm appears while the app is open. The history is kept, even after the rule, tag or device is deleted.
Alarms stay in the app
TCS-NET sends no e-mail, text message or webhook out. Your data stays on your machine.
Good to know
- A text tag cannot have an alarm rule.
- A locked tag or device (Standard edition) raises no alarm.