User guide

Chapter 3: Alarms

interrupted, or an event log or logger alarm condition is

present. Alarm emails can be sent repeatedly based on

how alarm properties have been set.

• An application can be launched or an external device

turned on. If configured, an external device (such as a light

or buzzer) or a computer application (such as batch file

which can page or phone a particular number) can be

triggered when an alarm condition occurs.

• All of the above. Your administrator may also set up a tree

alarm hierarchy, a method of notifying different individuals

of an alarm if the first notification is not acknowledged

within a specified time frame.

Alarms should be acknowledged in viewLinc and the

situation dealt with as soon as possible. All transactions are

recorded in the Event Log and Historical database and can

be viewed in an Event Log or Alarm report.

Acknowledging Alarms

All users can receive alarms, but only users with the correct

permission can acknowledge alarms.

If an alarm is set to require alarm acknowledgement, alarms

must be acknowledged. You must be logged in to viewLinc to

acknowledge alarms.

Acknowledgement information, such as the action taken and

any comments, is tracked in the Event Log and Historical

database. For more information, see Chapter 4: Events and

Chapter 5: Reports.

When an alarm is triggered, a new row appears in the Alarms

tab.

This section covers acknowledging alarms using the Active

Alarms tab. You can also acknowledge alarms from a large

channel view (see “Acknowledging Alarms from Large

Channel View” on page 14).

To acknowledge alarms from the alarms tab:

From Alarms | Active Alarms, select the active alarm,

then click

Acknowledge.