> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/infraon-configuration/it-operations/maintenance.md).

# Maintenance

Maintenance refers to the ongoing process of inspecting, repairing, and optimizing equipment or software to ensure reliability, performance, and longevity. Thus, maintenance minimizes downtime and prevents potential issues. &#x20;

Maintenance involves the deliberate shutdown of a device for a specific purpose or action, often driven by a scheduled event or a particular requirement. During maintenance, alarms are suspended, and polling operations are halted on the device undergoing maintenance. This measure is undertaken to prevent the occurrence of extraneous alerts and to ensure that any unnecessary activities are averted, enhancing the overall efficiency of the maintenance operation. &#x20;

## **What you see on the screen**&#x20;

Refer to the following table for more information: &#x20;

| **Label**           | **Description/ Example**                         |
| ------------------- | ------------------------------------------------ |
| Reason              | Mention the reason for the maintenance           |
| No. Of Assets       | Mention the number of assets for maintenance     |
| Status              | Status is changed as per the maintenance.        |
| Maintenance Window  | The date will be displayed i.e. To – From date.  |

Click on the ‘action’; tab and click the ‘edit’ or ‘delete’ icon. &#x20;

In Edit, there are two tabs mentioned below: &#x20;

**Asset Details** | Schedule &#x20;

* Write the reason for the maintenance. &#x20;
* Select ‘Mask Alarm’ or ‘Stop polling’ and click ‘Next’ &#x20;

**Mask Alarm**: A mask alarm is a condition where no alarm signals are intended to activate. This implies that the system operates under circumstances that prevent any alarm triggers. &#x20;

**Stop Polling:** Stop polling refers to an elective intermediary action positioned between the "mask alarm" and itself. When the verification is selected, polling operations are suspended; however, if the checkbox remains unmarked, polling continues, though an alarm won't be generated even if it aligns with the threshold. &#x20;

Asset Details | **Schedule** &#x20;

* Click on the ‘Calendar’ icon to select the start time and select the time. &#x20;
* Click on the ‘Calendar’ icon to select the end Time and select the time. &#x20;
* Click ‘Submit’  &#x20;

Maintenance can be deleted by clicking the ‘delete’ icon from the action tab.  &#x20;

{% hint style="info" %}
**Note**: A corresponding maintenance icon becomes visible on the device interface when a device enters a maintenance state. Selecting the maintenance icon cesses polling operations; if the checkbox is activated, polling is suspended, and data remains empty. &#x20;
{% endhint %}


---

# 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://docs.infraon.io/infinity/user-guide/infraon-configuration/it-operations/maintenance.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.
