> 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/working-with-viewers/alarm-viewer.md).

# Alarm Viewer

The Viewers that display are determined by your privileges. Select the **Viewers** tab on the Command Centre title bar, and then click the **Alarm Viewer** button on the toolbar. The Alarm Viewer opens.

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

The Navigation Panel for an Alarm Viewer is a list of Alarms. The columns displayed are dependent on the configuration for the Viewer. However, the first two columns (which do not have column titles) are always **Priority** and **Alarm State**, and cannot be resized or reordered. All other columns can be resized and reordered, with the exception of the the **Occurrence Time** column which can only be resized, (i.e. it cannot be reordered).

The Tiles that have been configured for this Viewer only populate the Viewer Panel once an alarm is selected. Tiles can be maximised (made larger) so all the content is visible without scrolling. See [Minimising/Maximising Tiles](https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/working-with-viewers/minimising-maximising-tiles.md) for further detail.

If 'Filtering by Alarm State' was configured for this Viewer the Filter options, (i.e. **All Alarms**, **Unacknowledged** and **Acknowledged** ) will display. These options allow you to select the filter you require for the Viewer. If you select one of these filters the selected filter button will be highlighted to show that a filter has been applied to the visible alarms.

**Note:** The count at the bottom of the panel *"# Alarm(s), # Unacknowledged"* will reduce as will the count on the coloured priority buttons on the panel.

### Hints

{% hint style="info" %}
When an alarm is selected it becomes 'locked' so that it remains visible in the Navigation Panel, (i.e. it will not be pushed off the display by incoming alarms), until either you scroll the display or select another alarm. If multiple alarms are selected, the 'locked' alarm is the last one selected.
{% endhint %}

{% hint style="info" %}
Alarm Viewers can be configured to pop to the front when a new alarm occurs.

With this configuration, if no Alarm Viewer is currently displayed, and there are multiple Alarm Viewers that meet the alarm criteria when either a *Priority Block\** on the Status bar is clicked, or an alarm occurs for a 'Pop to front' Viewer, the system will display the 'first' Alarm Viewer returned from the server that contains the new alarm.

{% hint style="info" %}
**\*Priority Block**

One of the coloured blocks (either on the Status bar at the bottom, or above the Alarm List on an Alarm Viewer) that provides a summary of the number of alarms of a particular priority.
{% endhint %}
{% endhint %}

{% hint style="info" %}
If you view an alarm for 10 seconds or more the alarm history will be updated.
{% endhint %}

{% hint style="info" %}
The size of the text can be adjusted by clicking on ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-23f64398526e9351c6ffac93a84270dd8fb2b896%2Ftextsize.png?alt=media) and then dragging the indicator that displays as necessary.
{% endhint %}

{% hint style="info" %}
An online help file listing all the event/alarm messages can be accessed via the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-21696e72ec0a06324b205d044b43d8eb573a6bd7%2Fsystemoperatorbutton.png?alt=media) button on the Command Centre toolbar, and provides explanations of what each message means.
{% endhint %}

{% hint style="info" %}
There are a number of keyboard shortcuts available for performing activities on the Alarm Viewer. See [Using keyboard shortcuts](https://help.security.gallagher.com/knowledge-hub/command-centre-client/getting-started/using-keyboard-shortcuts.md) for further detail.
{% endhint %}

{% hint style="info" %}
The ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-1917d0a2636ac19bbf408180779ffc8b8ea0cc89%2Fquicktipsbutton.png?alt=media) button can be clicked to provide [quick tips for using the Alarm Viewer](https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/working-with-viewers/alarm-viewer/quick-tips-for-using-the-alarm-viewer.md).
{% endhint %}

{% hint style="info" %}
It is recommended that the system not be operated with large quantities of alarms.
{% endhint %}

{% hint style="info" %}
The **Count** column (if configured to display), indicates either:

* the flood count for an alarm flood. Only one instance of an alarm flood will display, with the flood count for each alarm flood, or
* the number of times a stateful alarm has occurred.

An operator should be able to distinguish these two scenarios by looking at the event history in the Alarm Details Tile.
{% endhint %}

{% hint style="info" %}
Icons can populate the **Alarm State** column to indicate the current state of an alarm, as follows:

<table><thead><tr><th width="126">Icon</th><th>Indicates that an alarm....</th></tr></thead><tbody><tr><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-931bc80e8e078e60556e6e6ba8bf6008dbc3fc05%2Falarmbell_icon.png?alt=media" alt=""> Alarm Bell</td><td>is active, (i.e. the problem has not yet been resolved). Alarms in this state can be acknowledged but not processed.</td></tr><tr><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7d2092c38b5a0c6482188d489d07632d9a700279%2Ffilmstrip_icon.png?alt=media" alt=""> Film Strip</td><td>has images associated with it.</td></tr><tr><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-127bfcb4a194f62928e20098787d87c5ad241d9b%2Fyellowarrow.png?alt=media" alt=""> Yellow Arrow</td><td>is escalated. The yellow arrow appears as an overlay over both Film Strip and Alarm Bell icons.</td></tr><tr><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-cec952191a264d38ed93df4b2106958a59308c13%2Fcrossedcircle.png?alt=media" alt=""> Crossed Circle</td><td>comes from a remote server that is currently offline, and the operator will be unable to process the alarm.</td></tr></tbody></table>
{% endhint %}

<details>

<summary>Determining alarm priorities</summary>

The priority of each Alarm is indicated by the colour of the bar that appears at the beginning of each row. The priority of an alarm can be determined by either:

* hovering over the coloured bar beside the alarm.

  A pop-up displays indicating the Event Priority of the alarm. This example shows a **Medium High Priority** alarm.

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

OR

* clicking on an alarm in the list (so it becomes highlighted).

  The corresponding coloured block (in the set of coloured blocks above the Alarm List) expands to display the Event Priority of the alarm selected, along with the number of alarms of that priority.

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

The set of coloured blocks above the Alarm List provides a summary of the number and priority of the alarms in the Viewer. There is a block for every Event Priority, (i.e. even if there are no alarms of a particular priority, the outline of the block still displays in priority order).

**Note:** If you click on one of the coloured blocks, the system scrolls the list so the most recent unacknowledged alarm of that priority is selected and becomes visible.

</details>

<details>

<summary>Acknowledging alarms</summary>

The coloured bar at the beginning of an alarm flashes if the Alarm is unacknowledged. Acknowledge an alarm by either:

* clicking anywhere on the coloured bar at the beginning of the alarm you want to acknowledge, OR
* clicking on the alarm in the list that you want to acknowledge (so it becomes highlighted), and click the **Acknowledge** button.

  **Note:** The Tiles configured for this Alarm Viewer display in the Viewer Panel below the Alarm List. Any Cardholder Tiles are not editable from this Viewer.

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

* The coloured bar at the beginning of the alarm stops flashing and reduces in size, so it is easy to identify which alarms are still unacknowledged.
* The corresponding coloured block above the Alarm List is selected and expanded.
* An entry is written to the alarm's history.
* The number of unacknowledged alarms changes below the alarm. In this example, it now states *3 Alarm(s), 2 Unacknowledged*.

</details>

<details>

<summary>Acknowledging multiple alarms</summary>

Multiple alarms can be acknowledged at once, as follows:

1. Hold down the < **Ctrl** > key while you click on each row of the alarms to be acknowledged.

   Each row selected becomes highlighted.

   **Note:** As soon as more than one alarm is selected, any Tiles populating the Viewer Panel disappear.
2. Click the **Acknowledge** button.

   The coloured bars at the left hand side of each selected alarm stops flashing and reduces in size, and an entry is written to the alarm's history.

</details>

<details>

<summary>Processing alarms</summary>

Use the following procedure to process an alarm:

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

   The alarm disappears from the alarm list, and an entry is written to the alarm's history. The next alarm in the list is selected automatically.

</details>

<details>

<summary>Force Processing alarms</summary>

Under normal circumstances only inactive alarms should be processed, however sometimes the state of an alarm does not change to inactive even after the cause of the alarm has been dealt with. In these instances an operator with the "Edit Alarm" and "Force Process" privileges in the division of the alarm can force process one or more active alarms, as follows:

1. Click on the row of the alarm you want to process, so it becomes highlighted.
2. Right click and select **Force Process**.

   The alarm disappears from the alarm list, and an entry is written to the alarm's history.

</details>

<details>

<summary>Entering an Alarm Note</summary>

Alarm notes can be entered when acknowledging or processing alarms, using the following procedure:

**Note:** Alarm notes default to voluntary, but they can be compulsory for "process only" or "acknowledge and process" if the Operator Groups are configured that way in Configuration Client. In this case, the Enter an Alarm Note pop-up will automatically appear depending on the configuration.

1. Click on the row of the alarm you want to add a note to, so it becomes highlighted.
2. Click the **Add Note** button.

   The Enter an Alarm Note pop-up displays.

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

   **Notes:**

   * The buttons that appear on the Enter an Alarm Note pop-up depends on what action has already been taken, e.g.
     * If the alarm has already been acknowledged only a **Process** button appears.
     * If the alarm has been acknowledged and is active, neither the **Acknowledge** or **Process** buttons appear.
     * If the alarm is active but has not been acknowledged only an **Acknowledge** button appears.
   * If multiple alarms are selected the number of alarms selected will appear in brackets beside the title of the 'Enter an Alarm Note' pop-up.
3. Select the appropriate **Alarm Note(s)**, and optionally enter details of what action you have taken in the **Comments** field.

   **Notes:**

   * As soon as one Alarm Note is selected, or you begin typing in the **Comments** field, the **Process** button changes to **Process with Note**, or if the **Acknowledge** button is displayed, it will change to **Acknowledge with Note**.
   * Alarm Notes can be selected either by checking the checkbox beside the Note, or via function keys. By default, < **F1** > to < **F8** > are assigned to match the first eight alarm notes.

     If a function key that has no matching Alarm Note is pressed, then nothing happens.
4. Click the appropriate button, as follows:

   <table><thead><tr><th width="202">If you click the...</th><th>then...</th></tr></thead><tbody><tr><td><strong>Add Note</strong> button</td><td><ul><li>the Enter an Alarm Note pop-up closes,</li><li>the Note is added to the alarm, and</li><li>the alarm remains in the Alarm List.</li></ul></td></tr><tr><td><strong>Acknowledge with Note</strong> button</td><td><ul><li>the Enter an Alarm Note pop-up closes,</li><li>the Note is added to the alarm, and</li><li>the coloured bar at the beginning of the alarm stops flashing and reduces in size, indicating that the alarm is acknowledged.</li></ul></td></tr><tr><td><strong>Process with Note</strong> button</td><td><ul><li>the Enter an Alarm Note pop-up closes,</li><li>the Note is added to the alarm, and</li><li>the alarm is processed and disappears from the Alarm List.</li></ul></td></tr></tbody></table>

   **Note:** Manually entered Alarm Notes are shown as bold in the **Alarm History** on the Alarm Details Tile.

</details>

<details>

<summary>Expanding the Alarm List</summary>

Configuring the Alarm list at the top or bottom of the Viewer allows you to see a reasonable number of columns for each alarm but not many Alarms in one go, which could be frustrating for sites with a lot of Alarms. Therefore, it is possible to expand the Alarm List (either automatically or manually).

### Automatically expanding the Alarm List

Regardless of the dock position of the Alarm List, multi-selecting Alarms automatically expands the Alarm List to fill the Viewer. As there is no Panel to display, nothing will be hidden. Having no Alarm selected will **not** auto expand the Alarm List.

If the Alarm List is expanded due to multi-selection, moving to a position where a single Alarm is selected, either because the user has de-selected all but one Alarm or because the multi-selected Alarms have been processed, the Alarm List will return to normal size.

### Manually expanding the Alarm List

To allow an operator to manually expand/maximise the Alarm List, a button in the middle of the Panel facing edge of the Alarm List Navigation Panel (see example below) has been provided.

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

When the List is maximised the button will change to point in the other direction to indicate the Alarm List can be returned to its original size.

Whether the 'maximise/return to normal size' button appears depends on the configuration for the Viewer. There will be an **Allow Alarm List to be expanded** checkbox available on the Alarm Viewer General Configuration pop-up.

If the Alarm List has been expanded manually, it will only return to normal size when you click the button to revert to normal size. When the list reverts to normal size the button will change back to its expand/maximise state. If a single Alarm is selected it will appear at the top of the list.

</details>

<details>

<summary>Alarm Sounds</summary>

Audio feedback is an option for when an alarm message is generated. A sound (configurable via the Server Properties in Configuration Client), is played when there are unacknowledged alarms within either the Alarm Viewer or the Escalated Alarm Viewer.

### Recommendation

If two alarms occur and the lower priority alarm has an alarm sound configured, but the higher priority alarm has "No Sound" configured for that event priority, then no alarm sound will play. Therefore, we recommend that you do NOT turn off alarm sounds for an event priority if there are lower event priorities that have an alarm sound configured.

### Which alarm sound plays

In the Alarm Viewer, the alarm sound that plays is the alarm sound selected for the highest priority, unacknowledged alarm, provided that this alarm occurred, or was escalated, since the last time the operator muted alarm sounds.

Once the operator has muted the alarm sounds, no alarm sound plays until:

* the next new alarm occurs,
* the next existing alarm is escalated, or
* a new instance of a flood alarm occurs that is outside the "Forget Flood Interval".

### What stops alarm sounds from playing

Any of the following actions stops an alarm sound from playing at an operator's workstation:

* The operator mutes alarms (via \<F9>).

  In this case, no alarm sound plays.
* A new, higher priority alarm occurs (than the alarm that is currently the cause of the alarm sound).

  In this case, the alarm sound for the new, higher priority alarm is played (if any).
* All alarms in the operator's Alarm Viewer are acknowledged.

  In this case, no alarm sound plays.

All unacknowledged alarms of the priority currently triggering the alarm sound, are acknowledged. In this case, the standard rules determine which alarm sound plays (if any).

</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/working-with-viewers/alarm-viewer.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.
