Configure alarms

Alarming capabilities are a part of object templates, but they are not implemented until you configure the object in the IDE. After alarms are configured, you can view Application Server alarms in a client visualization application like InTouch HMI or the AVEVA OMI Alarm App.

You can add latched alarms as an additional alarm state for the Galaxy to provide an extra level of visibility and oversight to alarm conditions. See Alarm latching for more information.

Configuring an object to be an alarm provider includes the following general sequence of steps:

1. Decide whether alarm notification is needed for each possible alarm condition of an object. For example, a command time-out alarm for a valve if the output command fails to move the valve.

2. Edit the object and set an attribute that specifies alarming.

3. Edit the object from the IDE and assign values to alarm attributes.

4. Configure the alarm properties. Typically, the fields that require configuration are Category, Priority and Description.

5. Configuring any limit fields to set an alarm. For example, the feedback time-out time limit.

You can add alarm detection and reporting capabilities to objects that were not originally developed to detect alarms. You do this by configuring alarm features for the object’s attributes.