Skip to main content
Guide menu

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.

OptionMeaning
ConditionGreater than, at least, less than, at most, equal, not equal (numeric tags); on or off (bool tags); offline (a device).
SeverityInfo, warning or critical.
On-delayHow long the condition must hold before it becomes an alarm.
Off-delayHow long the condition must be gone before the alarm ends.
BufferA margin around the limit so a value hovering at it does not make the alarm chatter.
Require acknowledgementOn 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.

StateMeaning
Active, unacknowledgedThe condition is there and nobody has acknowledged it.
Active, acknowledgedThe condition is there but someone has taken it on.
Cleared, unacknowledgedThe condition went away before anybody looked: it still asks for attention.
Cleared, acknowledgedFinished.

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.