Proving alarm-path resilience
Alarm signalling is a promise that a signal will get through when it matters. The only way to trust that promise is to cause the failures it is meant to survive, under control, and record what happens.
Test the failures, not just the connection
A path that is up today proves very little about the day it is needed. A resilience test plan deliberately creates the conditions the design is meant to withstand and checks the system behaves. Remove one path and confirm the loss is detected, reported and that signalling continues on another. Remove local power and confirm what the design says should still work does. Restore each condition and confirm the system reports the recovery. Through all of it, confirm a test signal is actually received and actioned at the alarm receiving centre, because supervision of the path is not the same as delivery of the message.
Each test should state, in advance, what it proves and what it does not, and be run with the safeguards that keep a real monitored premises safe while it is tested.
Commission it, then keep testing it
Resilience is not a one-off. A path that was independent at commissioning can share a dependency later, after a site change or a network reconfiguration, so periodic re-testing is part of maintenance, not an optional extra. Keep the records, because the test history is the evidence behind the service you are providing.
Netavo provides signalling with up to four verified paths per site, which supports this kind of controlled testing. The portal shows each path's live status and fault history, and paths can be tested individually, so a commissioning or maintenance test leaves a clear record of what each path did.
Common questions
What should a resilience test actually do?
Deliberately remove a path and confirm the loss is detected, reported and that signalling continues; remove local power and confirm expected behaviour; restore each and confirm recovery; and confirm a test signal is received at the ARC.
Isn't supervision enough without testing?
Supervision watches the path continuously, but it does not prove the design survives a real failure or that a signal is actioned at the far end. Controlled failure tests prove those.
How often should resilience be re-tested?
Periodically, as part of maintenance, and after any site or network change. A design that was independent at commissioning can acquire a shared dependency later.
Related services
Proving your signalling works?
Tell us your sites and paths, and an engineer will help build a commissioning and maintenance test plan.
Work with us →