Test alarm zones
Test alarm zones without generating alarms or sending monitoring messages.
When technicians are on site, you usually want to test alarm zones without generating alarms or sending messages to monitoring. Every alarm zone can be overridden into four states, but most sites only use the first two (Armed, Disarmed). Rename the third state to Testing in Server Properties and give it an action plan that produces a Message only with no Alarm Transmitter selected. A technician can then put the zone into Testing and work without raising alarms.
The four alarm zone states
Most people do not notice that every alarm zone can be overridden into four states; most sites only use the first two.

The names of the third and fourth states are set site-wide in Server Properties. You can change them to anything you like.

In this example the third state has been changed to "Testing".

Configure the Testing state
On an action plan you now see the change: a Testing option is present instead of "User1".



In both the Armed and Disarmed statuses there are alarms being generated and messages being sent to the IP Alarm Transmitter. But the Testing status has Message only and no Alarm Transmitter selected. This means a technician can put the alarm zone into the Testing state and carry out tests around the site without generating alarms in the system or sending messages to monitoring.
The third and fourth alarm zone states can only be overridden from Command Centre, not from a terminal.
Related links
Alarm Transmission - Monitoring. How action plans and the Alarm Transmitter send events to monitoring.
Last updated
Was this helpful?
