The effect of modifying the hold off period

When you re-configure the hold off period to a different value, the effect of this change depends on what state the term is in at the time.

If the term is not in alarm, a change in the hold off period value has no effect until the next time the term goes into alarm, regardless of whether the hold off period is being added, removed, or modified.

However, if a term is in alarm, the following is expected:

• Adding a hold off period to a term alarm has no effect until the next time the term goes into alarm.

• Removing a hold off period for a term that is in alarm, but whose alarm is not held, clears the hold off period. The clearing of the hold off period results in the generation of an event indicating the end of the hold off period.

• Changing the length of a hold off period for a term that is in a non-held alarm state will not cause the hold off period to restart. Each cycle, the system uses the same start time to see if the period has expired. If the end of the updated hold off period is still in the future, the hold off period expires after the updated hold off period ends. If the hold off period has been shortened such that the end is now in the past, the hold off period will end in the next processing cycle. For a term in alarm where the alarm is held, configuring the hold off period to zero will end the hold off period and cause the system to re-announce the alarm. If the length of the hold off period has changed such that the end of the hold off period is still in the future, the hold off period expires after the updated hold off period ends. If the length of the hold off period changes such that the end of the current hold off period is now in the past, then the hold off period will end when the next processing cycle occurs and the system will re-announce the alarm and start a new hold off period.