Confirm the correct settings in the configuration file

You must confirm the configuration file has the correct settings before you can configure re-alarming for analog, status, rate, multistate, or remote points.

To confirm the correct settings in the configuration file

1. Navigate to the following directory and open the RealTime_realarm.json file:

   %DNADataRoot%\RealTime\config\Settings

2. Locate the following text, and update it if required: REALARM_STRING_LOCATION_PREFIX.

   Note: REALARM_STRING_LOCATION_PREFIX is set to No by default.

   If the REALARM_STRING_LOCATION_PREFIX configuration setting is set to No, the text used in the RE_ALARM_SUFFIX field in the DNADataRoot%\RealTime\sdk\resx\libappResources\realarmStrings.resx file will be used in the re-alarm message after the text of the original alarm.

   If the REALARM_STRING_LOCATION_PREFIX configuration setting is set to Yes, the text used in the RE_ALARM_PREFIX field in the DNADataRoot%\RealTime\sdk\resx\libappResources\realarmStrings.resx file will be used in the re-alarm message as a prefix of the message of the original alarm.

3. Locate the following text, and update it if required: REALARM_TIME_STAMP_EXCLUDE.

   Note: REALARM_TIME_STAMP_EXCLUDE is set to No by default.

   If you change the configuration setting to Yes, the original timestamp will be excluded in the re-alarm messages.

4. Locate the following text, and update it if required: REALARM_BASED_ON_CREATION.

   Note: REALARM_BASED_ON_CREATION is set to false by default.

   If the REALARM_BASED_ON_CREATION configuration setting is set to false, the re-alarm time period starts counting down after a Controller acknowledges the alarm.

   If the REALARM_BASED_ON_CREATION configuration setting is set to true, the re-alarm time period starts counting down immediately after the system creates the alarm.

5. Locate the following text, and update it if required: REALARM_APP_EXEC_CYCLE_IN_SECONDS.

   Note: REALARM_APP_EXEC_CYCLE_IN_SECONDS is set to 20 by default.

   The REALARM_APP_EXEC_CYCLE_IN_SECONDS configuration setting defines the interval at which the Re-Alarming application checks if there are any existing alarms configured for re-alarming. The Re-Alarming application will then re-annunciate the appropriate alarms (with a new timestamp) within the window of time equal to REALARM_APP_EXEC_CYCLE_IN_SECONDS divided by 2. Re-alarming uses the new timestamp when determining if it needs to re-annunciate an alarm.

   For example, as per the default value of 20, Re-Alarming checks if there are any alarms in the past 10 seconds or the next 10 seconds that it needs to re-annunciate.