> For the complete documentation index, see [llms.txt](https://docs.tricloudnexus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tricloudnexus.io/management-portal/operations/alarms/alarm-lifecycle.md).

# Alarm Lifecycle

The Nexus Platform alarm management system adheres to the ANSI/ISA-18 standard for alarm management. This standard defines a lifecycle for alarm states to ensure consistent handling, visibility, and operator response.

Each alarm follows a well-defined sequence of states from activation to resolution, enabling operators to track both the current status and the history of an alarmed condition. Understanding this lifecycle is essential for effective alarm handling, acknowledgment workflows, and system reliability.

***

## Alarm States

Each alarm follows a four-state model:

<table><thead><tr><th width="130">Alarm state</th><th width="222">Acknowledged</th><th>Description</th></tr></thead><tbody><tr><td>IN <strong>ALARM</strong></td><td><strong>NOT ACKNOWLEDGED</strong></td><td>A condition has entered an alarm state and has not yet been acknowledged by an operator.</td></tr><tr><td>IN <strong>ALARM</strong></td><td><strong>ACKNOWLEDGED</strong></td><td>The alarm condition is still active, but has been acknowledged by an operator.</td></tr><tr><td><strong>NORMAL</strong></td><td><strong>NOT ACKNOWLEDGED</strong></td><td>The condition has returned to normal, but the alarm has not yet been acknowledged by an operator.</td></tr><tr><td><strong>NORMAL</strong></td><td><strong>ACKNOWLEDGED</strong></td><td>The alarm condition has cleared and has been acknowledged. The alarm is considered resolved.</td></tr></tbody></table>

***

## Alarm Transitioning State Model

The alarm lifecycle and its transitions are illustrated below:

<figure><img src="/files/YkKhzNS9f1XMWNbTHw6T" alt=""><figcaption><p>Transitions between alarm states</p></figcaption></figure>

These states are visually represented in the UI using color-coded labels and badges.

***

## Acknowledgement of Alarms

Initially, all alarms are in the **Normal Acknowledged** state (`RTNxACK`). This state indicates that the alarm is not currently active and has not been active since it was last acknowledged by an operator. In this state, the alarm is not visible in the alarm list.

When an alarm condition occurs, the state moves to the Alarm Unacknowledged state (`ALARMxUNACK )` making is visible in the alarm list.

<figure><img src="/files/SpFuKQ35jzdQOdh53J43" alt=""><figcaption><p>Active alarm, that has not been acknowledged</p></figcaption></figure>

From here, the alarm condition can either disappear, moving to state (`RTNxUNACK`) or the operator can acknowledge the alarm, moving to state (`ALARMxACK`).

<figure><img src="/files/lJGbxOiI4SeM3smEjQ53" alt=""><figcaption><p>Example of unacknowledged alarm returning to normal, and active alarm that is acknowledged.</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tricloudnexus.io/management-portal/operations/alarms/alarm-lifecycle.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.