---
title: "How to create monitorings?"
slug: "1723138792"
tags: ["Assets"]
updated: 2026-11-04T11:53:55Z
published: 2026-11-04T11:53:55Z
canonical: "help.ila.cegid.com/1723138792"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.ila.cegid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to create monitorings?

- [x] PT
- [x] ES

---

Monitorings allow you to monitor and regulate the operation of assets by tracking a preset value, and to trigger **corrective maintenance** actions based on the positive or negative variation of that value.

---

## Create a monitoring

To create a monitoring, follow these steps:

1. Go to **Assets | Measurements | Monitorings**;
2. In the list of monitorings, click on **Create**;
3. On the creation screen, fill in the monitoring details:
  - **Monitoring**;
  - **Description** (required);
  - **Unit** (required);
  - **Asset** section: associate the monitoring with an element, through the **Location Function**, **Family**, **Brand**, **Model** and **Asset Type** fields;
  - **Upper Limits** section: fill in the **Action** and **Warning** values, the **Trigger Events** field and, if desired, the **Create Request** and **Create Work Order** options;
  - **Lower Limits** section: fill in the same fields as in the **Upper Limits** section;
  - **Average** section: fill in the **Window**;
  - **Characteristics** section: in each row, fill in the **Characteristic**, **Value Type**, **Value**, **Unit** and **Enum Value** columns. If more rows are needed, click on the **+** icon;
  - **Remarks**;
4. Click on:
  - **Save and New**, to save the monitoring and start a new record;
  - **Save**, in the arrow next to the **Save and New** button, to save only the monitoring.

---

## Associate a monitoring with an element

When creating a monitoring, you must associate it with one of the following elements. The element defines the assets for which monitoring values can be recorded:

| Element | Value recording |
| --- | --- |
| Location function | You must select a location that has that location function. |
| Family | You must select equipment or a tool of that family. |
| Brand | You must select equipment or a tool of that brand. |
| Brand and model | You must select equipment or a tool of that brand and that model. |
| Location | You can only record for that location. |
| Equipment | You can only record for that equipment. |
| Tool | You can only record for that tool. |

---

## Define the limits and the average

In the **Upper Limits** and **Lower Limits** sections, the **Trigger Events** field defines the number of consecutive values required to trigger a **warning** or an **action**.

If the **action** and **warning** fields are filled in, they must follow the order **Upper Action** > **Upper Warning** > **Lower Warning** > **Lower Action**:

- The **upper action** limit must be **greater than the upper warning limit**;
- The **upper warning** limit must be **greater than the lower warning limit**;
- The **lower warning** limit must be **greater than the lower action limit**.

In the **Average** section, the **Window** field indicates the **number of records** of monitoring values used to **calculate the average**. To learn more about the average calculation, see the article [How is the average of meters and monitorings calculated?](/valuekeep/docs/en/1723138798).

---

## Assign characteristics

In the **Characteristics** section, you can assign one or more characteristics to the monitoring. The characteristics can be of the following types:

- Number;
- Text;
- Date/Time;
- Boolean;
- Enum.

When saving the record, the following validations are performed:

- No repeated characteristics can exist;
- **Number**: checks if the text entered in the **Value** field is a number, if the **number of decimal places** matches the characteristic's **unit**, and if the **separator** matches the user's **language**;
- **Date/Time**: checks if the text entered in the **Value** field is a **date**, a **time**, or **both**;
- **Boolean**: checks if the value entered in the **Value** field is **0 (False)** or **1 (True)**;
- **Enum**: checks if the **Enum Value** matches the **values of the selected characteristic**.