> 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/command-centre-client/using-command-centre/licensable-features/advanced-alarm-management-feature.md).

# Advanced Alarm Management feature

Select the item that you require further detail on:

<details>

<summary>Manually Escalating Alarms</summary>

Operators can manually escalate alarms to a higher-level operator.

**Note:** If the **Require acknowledgement of alarms before other actions** option (on the 'Viewers & Reports' tab of the Operator Group) is selected, alarms must be **Acknowledged** before they can be Escalated or Processed. If there are automatic escalations set these will still occur.

Perform the following procedure to manually escalate an alarm:

1. Click on the row of the alarm you want to escalate, so it becomes highlighted.
2. Click the **Escalate** button.

   **Note:** The **Escalate** button will only appear if the "Allow manual escalation of alarms" option has been selected for the Operator Group (on the **Viewers & Reports** tab).

   ![Edit section](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-8ffd99f375a80c768dd40112b1dcae7e5c27fc08%2Falarmviewer_escalatebutton.png?alt=media)

   The alarm is removed from the list, and an "Operator Escalated Alarm" event is generated. The details of the event shows the name of the operator who escalated it.

   **Note:** If an alarm is auto-escalated the details show the operator who escalated it as "system".

   The escalated alarm now displays in the Escalated Alarm Viewer:

   ![Edit section](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-3abdc2d4a6eee41027fff7e2263ff9ee4beea882%2Falarmviewer_escalatedby.png?alt=media)

   * The alarm shows the state that is set in the Action Plan.
   * An "Up" arrrow displays beside the alarm indicating that the it has been escalated.
   * The Escalated Output goes on if one has been assigned in the Action Plan.
   * The alarm is unacknowledged again.
   * The "Acknowledged By" column is blank.
   * The "Escalated By" column shows the operator who escalated the alarm.
   * Active alarms will remain active.

</details>

<details>

<summary>Reactivation/Restoral behaviour with new triggers</summary>

Alarm restorals and reactivations do not originally factor into notifications with triggers of 'before acknowledgement' and 'after acknowledgement', as only acknowledgement and process alarm actions affect its timers.

If the **Include Alarm Restorals** checkbox is ticked on the **Triggers** tab of the Notification Filter properties, an alarm that has its timer activated for "not acknowledged" will have no behaviour changes. However, if this notification has already been sent, and the alarm changes states without being acknowledged still, the timer will restart.

The intention of this is to send a reminder message if the alarm is still 'active' and changing states but have not been addressed. A similar behavior happens if the alarm is acknowledged for too long.

</details>

<details>

<summary>Alarm Distribution/Assignment</summary>

Alarms are assigned fairly amongst active operators, taking into consideration the permissions of the operator, and are redistributed if an operator logs off.

### Operator availability

Operators will have the option to start and stop receiving alarms if they:

* are a member of an Operator Group that has the allow alarm assignments setting enabled, and
* have the permission to edit alarms.

Operators can change their availability by selecting the appropriate option from the **Operator Status** drop-down on the Alarm List toolbar, (i.e. either 'Available' or 'Unavailable').

![Edit section](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-3fabd3d8f989926984750451c3bfe7f34f5d534f%2Falarmviewer_operatoravailability.png?alt=media)

Upon first recognising a session, the operator availability service registers operators in the system.

<table><thead><tr><th width="216">When an operator is...</th><th>the operator availability service will...</th></tr></thead><tbody><tr><td>Available,</td><td><ol><li>Add the operator to the alarm queue, and perform alarm assignments.</li><li>An event will be generated when an operator changes their status to Available.</li></ol></td></tr><tr><td>Unavailable,</td><td><ol><li>Remove the operator from the alarm queue.</li><li>Remove any unacknowledged alarms from their assignments, and place those unacknowledged alarms into the alarm queue, and perform alarm assignments.</li><li>An event will be generated to show an operator has changed their status to Unavailable.</li></ol></td></tr><tr><td>Gone from the system in some manner, (e.g. operator logged out of Command Centre without changing their status to Unavailable),</td><td><ol><li>Remove the operator from the alarm queue.</li><li>Un-acknowledge any acknowledged alarms, and unassign all alarms.</li><li>Place the alarms back into the alarm queue, and perform alarm assignments.</li></ol></td></tr></tbody></table>

</details>

<details>

<summary>Operator Permissions on Alarms</summary>

Operator permissions on alarms are determined by the following:

* **Divisions**

  (refer to the "System Division" chapter in the *Configuration Client Help File* for further detail)
* **Privileges**

  (refer to the "Operator Privileges" chapter in the *Configuration Client Help File* for further detail)
* **Workstation restrictions**

  (refer to the following topics in the *Configuration Client Help File* for further detail:

  * "Operator Defaults" topic in the Server Properties chapter, and
  * "Creating a new Workstation Item" topic in the Services and Workstations chapter)

</details>

<details>

<summary>Acknowledge to re-assign</summary>

Alarms are reassigned to operators that utilise alarm assignments (see [Alarm Assignment](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/advanced-alarm-management/alarm-assignment.md)).

Operators that don't utilise alarm assignments, (e.g. an admin operator) may acknowledge an alarm that is assigned to another operator. When they do, the alarm will become unassigned. It will remain unassigned even if the operator who acknowledged it logs off.

</details>

<details>

<summary>System restart behaviour</summary>

### Command Centre goes offline

If the Command Centre goes offline while there are alarms assigned to operators, when operators log back in:

* Alarms will no longer be assigned to operators, and
* Acknowledged alarms remain acknowledged and still appear in the original operator's viewer. These don't get reassigned.

### Command Centre Client crashes

If the Command Centre Client crashes while there are alarms assigned to operators, when operators log back in:

* Alarms will no longer be assigned to operators, and
* Acknowledged alarms will now be unacknowledged.

</details>

<details>

<summary>Recommendation</summary>

When there are workstation restrictions in place, and operators are expected to work on multiple workstations, it is recommended to set automatic logoff (on the **Operator Defaults** tab in the Server properties) as per the procedure in "Operator Defaults" in the *Configuration Client Help File*.

</details>


---

# 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/command-centre-client/using-command-centre/licensable-features/advanced-alarm-management-feature.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.
