Configure Timed Parent State Alarm Suppression

Note: For information on overriding default configuration settings, refer to Modify configuration settings.

To configure timed parent state alarm suppression

1. Navigate to the Main tab in the almsuppression Row Details dialog box.

   

2. In the Suppression Method field, select Parent Alarm.

3. To inhibit the system from re-generating an alarm when the timeout expires for a child point that, depending on the point, either goes into alarm or undergoes an uncommanded change of state during the period of alarm suppression, select Inhibit Re-Generate Alarm.

4. In the Parent Alarm/Control field, enter the suppression time in seconds.

5. In the Parent Return to Normal field, enter 0.

6. In the Alarm Holdoff field, enter 0.

7. Select Valid for Specified Parent State.

   Note: If Valid for Specified Parent State is not selected, default parent state alarm suppression remains in place.

8. In the Alarm State field, enter the parent alarm state for in-alarm suppression.

   For analog and rate records, valid entries are as follows:

   • normal

   • hi

   • lo

   • hi-hi

   • lo-lo

   • uhi (only if the "RealTime" > "HILO_INTEGRATED_USER_ALARMS" AVEVA Enterprise SCADA key value in the RealTime_HiLoIntegratedUserAlarms.json file is set to TRUE)

   • ulo (only if the "RealTime" > "HILO_INTEGRATED_USER_ALARMS" AVEVA Enterprise SCADA key value in the RealTime_HiLoIntegratedUserAlarms.json file is set to TRUE)

     Notes: All the above entries, except for uhi and ulo, are case-insensitive.
     
     Setting the "RealTime" > "HILO_INTEGRATED_USER_ALARMS" AVEVA Enterprise SCADA key value in the RealTime_HiLoIntegratedUserAlarms.json file to TRUE causes uhi/ulo to act as one of the hilo limits.
     
     If you change the AVEVA Enterprise SCADA key value in the RealTime_HiLoIntegratedUserAlarms.json file, re-start the RealTime service for the change to take effect.

     For multistate records, the valid states depend on the input message set associated with the record. For example, if a multistate record’s input message set is defined as "multistateInput5", then the valid states are the state names in the "multistateInput5" message set. The Alarm State field is case-sensitive for multistate records.

     For status records, the rules for valid entries are similar to those for multistate records. The valid states are the state names in a status record's base message set. The Alarm State field is case-sensitive for status records.

9. To suppress alarms on the child point anytime the parent point changes to an abnormal state, regardless of whether or not the state to which it changes is the Alarm State, select Suppress child on parent abnormal state change.