> For the complete documentation index, see [llms.txt](https://move-solutions.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://move-solutions.gitbook.io/untitled/getting-started/how-to-set-up-alarms.md).

# How to set up alarms?

**Guide to configuring sensor alarm thresholds on MyMove**

Setting up alarms correctly in your structural monitoring platform is a crucial step in ensuring infrastructure safety and maximizing the effectiveness of the monitoring system. Before proceeding with configuring alarm levels for each sensor, it is strongly recommended to follow the instructions provided in the [Device Management](/untitled/getting-started/how-to-configure-device-operation.md) section and allow for an initial monitoring period.

Properly configuring alarm thresholds is essential to avoid both false alarms and potential unreported risk situations. By adopting this approach, you will not only strengthen the overall safety of the structure but also enhance the monitoring effectiveness, allowing the system to accurately detect anomalies and alert you promptly to significant issues.

{% hint style="info" %}
Learn more about the [**Alarms page**](/untitled/mymove-manual/alarms.md).
{% endhint %}

***

## Alarm Severity Levels

Through the Settings page, users can configure three distinct alarm thresholds for each sensor, allowing for different levels of severity:

* <mark style="color:yellow;">**Alert**</mark>**&#x20;- Low Severity**: Indicates events that may require immediate attention but do not pose an immediate threat to safety. For example, it might be triggered by a slight exceedance of a reference parameter.
* <mark style="color:orange;">**Warning**</mark>**&#x20;- Medium Severity**: Indicates an event that requires more significant attention than an Alert but does not yet represent a critical emergency. It could be activated by situations requiring detailed analysis to prevent more severe structural damage.
* <mark style="color:red;">**Critical**</mark>**&#x20;- High Severity**: Represents the most critical level of the scale, reserved for events that pose an immediate threat to safety, structural integrity, or the surrounding environment. It might be triggered in emergency situations or hazardous conditions requiring immediate intervention.

## How to setup the Alarm thresholds

1. **Understand sensor characteristics**: Familiarize yourself with the technical specifications of the sensor, including its operating and acquisition methods, the nature of the parameters measured, accuracy, and range.
2. **Analyze requirements**: Understand the specific needs of your monitoring project. Identify critical parameters to monitor for each sensor and the structural element on which it is installed. Determine the threshold levels that indicate alarm situations.
3. **Create a reference database**: Begin with an initial monitoring period to gather real data on the structure's dynamics, creating a reference database. This allows for understanding average movements and typical variations. Once analyzed, you can set customized alarm thresholds to differentiate between normal events and those needing immediate attention.
4. **Configure sensor alarm thresholds**: After understanding the average structural movements, divide the sensor measurement range into three alarm levels — <mark style="color:yellow;">**Alert**</mark> (low), <mark style="color:orange;">**Warning**</mark> (medium), and <mark style="color:red;">**Critical**</mark> (high)—by assigning specific values for each. To configure these thresholds, access the main menu, select Settings, then [Device Settings](/untitled/mymove-manual/settings/device-settings.md). For each device, click “Edit settings” to adjust alarm thresholds, activating or deactivating alarms as needed.
5. **Validate results**: After configuring the alarms, it is crucial to verify that the set levels are correctly calibrated to reliably signal abnormal conditions while avoiding false alarms from ordinary events. Careful adjustment of alarm thresholds will ensure that the system only reacts to significant structural changes, minimizing interruptions caused by unnecessary notifications.
6. **Constant monitoring**: Continuously monitor the alarm notifications generated by the system. Make any necessary adjustments to alarm settings based on practical experience and changes in operating conditions.

{% hint style="info" %}
Ensure you understand how alarms function for each type of sensor.
{% endhint %}

<figure><img src="/files/sQpZxabuJ4wTUPYZ8sf9" alt=""><figcaption><p>Device Settings - Alarms</p></figcaption></figure>

## Alarm Notifications

Whenever a new event is classified as an alarm, the user receives an **immediate notification** detailing its severity and specifics.

<figure><img src="/files/0k64oVJr7vlCdTL8Pgsg" alt=""><figcaption><p>Example of an Alarm notification via email</p></figcaption></figure>

## Alarms page

Every alarm event is recorded and saved. Access the Alarms page from the main menu to view the complete history of alarms for all sensors. The system can be configured to send email notifications for each alarm event, providing immediate alerts to emergencies.

{% hint style="info" %}
For further details and information, please refer to the [Alarms](/untitled/mymove-manual/alarms.md)[ page](/untitled/mymove-manual/alarms.md).
{% endhint %}

<figure><img src="/files/Ahrlz1KPNz20nRKaXkbf" alt=""><figcaption><p>Alarms page</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, and the optional `goal` query parameter:

```
GET https://move-solutions.gitbook.io/untitled/getting-started/how-to-set-up-alarms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.