---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Create an SLA definition for a CI or application service

# Create an SLA definition for a CI or application service {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can create SLA definitions for CIs and application services just as you can for
other task records in the instance.

## Before you begin

Role required: evt_mgmt_admin

## Procedure

1. Navigate to AllService Level ManagementSLASLA Definitions.
2. Click New.
3. Fill out the fields on the SLA Definition form.  
   For a description of each field, see [Create an SLA definition for a CI or application service](https://servicenow-prod.fluidtopics.net/lYro7oRf2KTr7iWPGCEWOQ "You can create SLA definitions for CIs and application services just as you can for other task records in the instance.").
4. For the Table field, select Event Management SLA \[em_ci_severity_task\].
5. Configure the Start condition filter by adding conditions, such as:  

   |-|-|-|
   | For all CIs where the Severity is Critical |||
   | Type | is | CI Note: Event Management SLAs work only on CI classes from Service Instance \[cmdb_ci_service_auto\]. |
   | Severity | is | Critical |
   | For a specific service, such as Email, when the Severity is Critical |||
   | Application Service | is | Email |
   | Severity | is | Critical |
   [Table 1. SLA filter conditions]

   {#t_EMCreateSLADefForCI_BS__table_rmj_xpg_y5}
6. Configure pause, stop and reset conditions.
7. Click Submit.

*[\>]: and then