> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/alarm-viewers/notify-restoral.md).

# Notify Restoral

### Introduction

Notify Restoral can only be configured for those events that are considered stateful, and hence have "Return to Normal" events. Refer to [Events with Restorals](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/event-viewer/events-with-restorals.md) for a list. Notify Restoral causes an alarm to be raised on both the open and closed events for an Alarm Zone and is configured on the **Advanced** tab of an Alarm Zone. The Notify Restoral behaviour applies to all points within an Alarm Zone which may enter an alarm state, (e.g. door open too long, forced door, etc.).

### Overview

Points that are configured as Notify Restoral points support the alarm states shown in the following diagram and display in the Alarm Viewer as described. Each Notify Restoral alarm will be in one of the states shown at any time.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9f5c53c899a7e7e07052c87faef1237695fa7ee4%2Fnotifyrestoral.png?alt=media)

If a user configures an Alarm Zone with "Notify Restoral", then all points within the Alarm Zone will follow the alarm and other behaviour specified in the diagram on the previous page.

### Example of a Notify Restoral Input

#### ![AGforRAT](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-14b613ad3cf1395d29bb00d119bc4c9aceeea782%2Fno1.png?alt=media) 'Normal' state:

When Notify Restoral is configured for an input a new alarm instance is created in the Alarm Viewer in the following circumstances:

1. Alarm is in the Normal state and the input opens.
2. Alarm flooding is disabled. A 'Return to Normal' alarm exists. The input contacts open.
3. Alarm flooding is enabled and the next input open event is outside the Tolerance setting.

   In all other circumstances the attributes of the existing alarm in the Alarm Viewer window are updated.

#### ![AGforRAT](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-92bb135f2a334de3fc86a4bb974fb85ac753c540%2Fno2.png?alt=media) 'Active Alarm' state:

When a Notify Restoral alarm transitions from a Normal to an 'Active Alarm' state, the alarm displays in the Alarm Viewer with the following attributes:

* The date and time flash (until acknowledged by an operator).
* The beeper sounds (until all alarms are acknowledged by an operator).
* The bell icon is displayed (while the input contacts remain open).

#### ![AGforRAT](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f3069173713a1470d03a2d717111ce4814c760b5%2Fno3.png?alt=media) 'Acknowledge Active Alarm' state:

A Notify Restoral alarm in an 'Active Alarm' state can be acknowledged but not processed. This places the alarm in an 'Acknowledge Active Alarm' state.

When a Notify Restoral Active Alarm is acknowledged the alarm attributes in the Alarm Viewer window are updated as follows:

* The alarm date and time stops flashing.
* The beeper turns off (if there are no other unacknowledged alarms in the Alarm Viewer).
* The bell icon remains displayed.

#### 'Return to Normal' state:

![AGforRAT](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8c0e62ff3b582947bdd2a1de064954a0c6ad3e02%2Fno4.png?alt=media) When a Notify Restoral alarm transitions from an 'Active Alarm' state directly to a 'Return to Normal' Alarm state (due to the input contacts closing), and if the operator has not acknowledged the alarm, the attributes in the Alarm Viewer change as follows:

* The alarm displays at the same priority as specified in the Action Plan for the "Input open" event.
* The alarm date and time continues to flash.
* The beeper continues to sound (unless it has been muted by the operator).
* The bell icon is NOT displayed.

It is possible for an operator to acknowledge and process an alarm in the 'Return to Normal' Alarm state. Either action transitions the alarm to the 'Normal' state. When an operator processes a 'Return to Normal' Alarm, it is removed from the Alarm Viewer.

![AGforRAT](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9e4870d0d2ad68a0b20ccf980732a13f4dbe4b5f%2Fno5.png?alt=media) When a 'Return to Normal' Alarm is acknowledged, the alarm attributes displayed in the Alarm Viewer window change as follows:

* The alarm continues to display at the priority specified in the Action Plan for the "Input open" event.
* The alarm date and time does NOT flash.
* The beeper does NOT sound (unless other unacknowledged alarms exist in the Alarm Viewer window).
* The bell icon is NOT displayed.

![AGforRAT](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-dfb1c2ff36359fc84fbec6bb5a5f4e47c6484947%2Fno6.png?alt=media) When a Notify Restoral alarm is in a 'Return to Normal' Alarm state and the input contacts then open, the alarm transitions to the 'Active Alarm' state. If alarm flooding is disabled, or the input open event is outside the tolerance setting for alarm flooding, a new alarm is created and displayed in the Alarm Viewer window as follows:

* The alarm displays at the priority specified in the Action Plan for the 'Input open' event.
* The alarm date and time flash.
* The beeper sounds.
* The bell icon is displayed.

If the 'Input open' event is within the tolerance setting for alarm flooding, the alarm count is incremented by 1 and the alarm attributes in the Alarm Viewer window update as follows:

* The alarm continues to display at the priority specified in the Action Plan for the 'Input open' event.
* The alarm date and time continue to flash.
* The beeper continues to sound (unless it has previously been muted by the operator).
* The bell icon is displayed.

![AGforRAT](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0194410d5198970d5c427b7ab11b04d8d9dc2d27%2Fno7.png?alt=media) When a Notify Restoral alarm is in an 'Acknowledge Active Alarm' state and the input contacts then close, the alarm transitions to the 'Return to Normal' Alarm state. The alarm is returned to an unacknowledged state. The alarm attributes displayed in the Alarm Viewer window change as follows:

* The alarm continues to display at the priority specified in the Action Plan for the 'Input open' event.
* The alarm date and time flash.
* The beeper sounds.
* The bell icon is NOT displayed.

Command Centre handles alarm events and operator interventions differently when Notify Restoral is set, compared to when Notify Restoral is not set. The following table compares functionality as an Input item changes from the 'Open/Off' state to the 'Closed/On' state.

<table><thead><tr><th width="190">Event</th><th width="120">Notify Restoral</th><th>Alarm displays</th><th>Display flashes</th><th>Sound</th><th>Bell icon</th></tr></thead><tbody><tr><td rowspan="2">Open/off event</td><td>Set</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td>Unset</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td rowspan="2">Acknowledged (after the open/off event)</td><td>Set</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td>Unset</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td rowspan="2">Closed/on event</td><td>Set</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td>Unset</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td rowspan="2">Acknowledged (after the closed/on event)</td><td>Set</td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td>Unset</td><td><em>Not possible</em></td><td><em>Not possible</em></td><td><em>Not possible</em></td><td><em>Not possible</em></td></tr><tr><td rowspan="2">Processed</td><td>Set</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td>Unset</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/alarm-viewers/notify-restoral.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
