Back to Articles

An alarm can take a number of different paths during its lifecycle. The lifecycle consists of four states and two soak periods. A soak period is a period of time during which more data is gathered to determine whether the alarm persists.

The picture below illustrates generally the paths that an alarm can take, moving from one state to another when both soak periods are enabled.

The alarm lifecycle has two possible soak periods: Alarm Soak Period and Clear Soak Period.

When an alarm is first detected, ServAssure NXT imposes a soak period called the Alarm Soak Period during which the alarm waits or soaks for a configurable amount of time. During the Alarm Soak Period, additional data is gathered from the network to verify whether the alarm persists (still exists). At the end of this soak period, if data indicates that the condition persists, the alarm is verified.

NOTE: The Alarm Soak Period can be disabled by your ServAssure NXT administrator, in which case, the alarm moves directly to the Verified state.

During the Alarm Soak Period (or at any time), if new data indicates that the condition no longer exists, the alarm moves to a Pending Cleared state, and a second soak period called the Clear Soak Period follows. After the Clear Soak Period, if the condition no longer exists, the alarm moves to a Cleared State.

NOTE: The Clear Soak Period can be disabled by your ServAssure NXT administrator, in which case, the alarm moves directly to the Cleared state.
An alarm can have any of these states:
  • Detected
  • Verified
  • Pending cleared
  • Cleared