# OLA standards

> [HTML Version](ola-level.html)

A [request](applications.md) of a specific type and priority may be processed by employees at different [levels of technical support](servicedesk-catalogs.md#support-level). In this case, the time for response, investigation, and approval of a resolution for the request must be regulated separately for each stage of its processing. For this purpose, the OLA standard is used.  

OLA is also used to define [service level agreement](sla-level.md) (SLA) conditions and [request processing workflows](application-route.md).  

To create a standard:  

1. Go to **Service Desk > OLA** and click the **+ OLA** button in the upper right corner of the page.

2. Fill in the basic information:  
**(ola-standards-1.png)**

- **Name\***. Enter the name of the standard.  

- **Responsible\***. Specify the employee responsible for ensuring the correct time calculation in the standard. If discrepancies or errors occur, operators may contact them for clarification.  

- **Work schedule\***. Select the operators' [work schedule](work-schedule.md) so that the standard applies only during their working hours. This ensures that a lack of response during non-working periods does not violate the standard.  

- **Executors\***. Indicate the support level whose operators will handle requests under the standard.  

- **Action starts on\***. Enter the date from which requests matching the selection criteria will be processed under this standard.  

- **Action stops on\***. Enter the planned end date for the standard.  

- **Dynamically calculate resolution time**. Switch the option to **Yes** to ensure that the total resolution time across multiple stages does not violate the [SLA terms](sla-level.md).  
  
For example, if multiple OLA standards apply at different stages of request processing and a delay occurs at any stage, it may affect the SLA. With dynamic calculation, the resolution time for subsequent stages is automatically reduced, ensuring the total processing time does not exceed the SLA deadline.

- **Description**. Enter additional information about the standard.

3. Set the allowable operator response time:  
**(ola-standards-2.png)**

- Define the period within which the operator should take the request into work, e.g., 1 hour or 3 days.  

- **Action in the event of a breach\***. Select the action to be taken if the standard response time is exceeded: **Not required**, **Notification in the system**, **Notification in the system and email alert**, or **Email alert and task in the system**.  

	- **To\***. If a notification is selected in the **Action in the event of a breach** field, specify who will receive it: responsible for the request, an arbitrary role, or both users.  

	- **To (Role)\***. If you selected an arbitrary role to receive the notification, specify it.

- **Reminder**. Enable this option and configure a reminder about the expiring response time for the request:  

	- **Reminder type\***. Specify where the reminder will be sent: to the system or via email.  

	- **Deadline\***. Set how many minutes before the response time expires the reminder should be sent.  

	- **To\***. Specify who will receive the reminder: responsible for the request, an arbitrary role, or both users.  

	- **To (Role)\***. If you selected an arbitrary role to receive the reminder, specify it.  

4. In the **Resolution Time** block, set the deadline by which the operator should find a solution and complete the request. The standard is configured similarly to the **Response Time** block.

5. **Time required to collect information**. Select **Yes** and, in the **Time for Collecting Information** block, specify the standard time the operator may spend searching for information to resolve the request. The standard is configured similarly to the **Response Time** block.

6.  Click **Save**.  

The standard item will then appear on the **OLA** app page.  

Users with [edit permissions](360007527512.md#assign) can modify existing OLA standards. To do this, open the standard page and click **Edit**.  

If the operators' [work schedule](work-schedule.md) changes, the OLA standard becomes inactive. You can schedule a work schedule change for a specific OLA to avoid re-entering data. To do this:  

- Open the OLA page and click **Schedule Rescheduling**.  

- Select the work schedule and specify its start date.  

A new standard item will appear on the **OLA** app page.