---
title: "How to configure the background services?"
slug: "1723138863"
tags: ["Settings"]
updated: 2026-10-23T15:49:11Z
published: 2026-10-23T15:49:11Z
canonical: "help.ila.cegid.com/1723138863"
---

> ## 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 configure the background services?

- [x] PT
- [x] ES

---

Some Cegid Valuekeep calculation operations are performed in the background, so they do not interfere with daily work.

To configure the background services, follow these steps:

1. Go to **Settings | Work | Background Services**;
2. In the list of configurations, click on **Create** to create a configuration, or select an existing configuration to edit it;
3. For an existing configuration, click on **Edit**;
4. Configure the options of the **KPIs**, **Up Time**, **Preventive Maintenance** and **Automatic Closing** services;
5. Click on **Save**.

---

## Configure the services

The screen has a section for each service. Each section shows the **next execution date** and the **last execution** log:

****KPIs****

Operation responsible for calculating the **asset indicators**, with the **Enable MTTR** option.

****Up Time****

Operation responsible for making assets **available** when the **unavailability date** has ended and the unavailability has no associated work order, with the **Enable Up Time** option.

****Preventive Maintenance****

Operation responsible for the **rescheduling** of preventive maintenance events, with the **Enable Events Rescheduling** option.

****Automatic Closing****

Operation responsible for moving requests or work orders to the **Final** state, with the **Enable Closing Requests** and **Enable Closing Work Orders** options. For this operation to run, you must fill in the following fields:

- **Close Requests After (days)**: number of days to wait before **requests** move to the **Final** state. For the state to be changed by the service, requests must have been in a state prior to **Final** for at least that number of days;
- **Close Work Orders After (days)**: number of days to wait before **work orders** move to the **Final** state. For the state to be changed by the service, work orders must have been in a state prior to **Final** for at least that number of days.

If there is more than one **Final** state in the state transitions, the service moves **requests** and **work orders** to the **first non-canceled** **Final** state configured in the transition. If there is none, the service **does not close any request or work order**.

> [!WARNING]
> Automatic closing of requests and work orders has a **maximum of 20 records per hour**. Closing the 20 records with the **oldest transition date** takes priority.