---
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


---

# Exploring SLO Management

# Exploring SLO Management {#ariaid-title1}

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

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Exploring SLO Management

Service Level Objective Management (SLO Management) in ServiceNow Yokohama release enables organizations to set clear expectations and measure IT service performance to ensure consistent delivery that meets customer needs.
It focuses on defining target service levels (SLOs) for critical services such as incident resolution and service request fulfillment, monitoring these targets through Service Level Indicators (SLIs), and driving continuous improvement.
Show full answer Show less  

## Key Features

* **User Roles and Responsibilities:** SLO Management involves distinct roles with specific permissions:
  * **Administrators:** Manage platform configurations, integrations (including Application Performance Monitoring tools), reliability indicators, and error budget policies.
  * **Managers:** Oversee Site Reliability Engineering (SRE) teams, manage schedules, users, and team-specific configurations, and ensure resilience in systems and DevOps workflows.
  * **Responders (SREs):** Handle incident diagnosis and remediation within their authorized scope, accessing relevant alerts and configurations.
* **SLO Management Workflow:** The process includes defining SLOs based on business needs, establishing SLIs to measure performance, monitoring and analyzing data, identifying gaps, implementing improvements, and regularly reviewing SLOs for refinement.

## Benefits for ServiceNow Customers

* **Improved Service Quality:** Ensures IT services align with customer expectations, enhancing satisfaction and loyalty.
* **Increased Transparency:** Provides clarity and shared understanding of service commitments between IT teams and customers.
* **Better Resource Allocation:** Enables prioritization of efforts and resources toward areas requiring improvement.
* **Enhanced Collaboration:** Fosters teamwork between IT and customer stakeholders to achieve service goals.
* **Data-Driven Decisions:** Uses performance data to guide continuous service improvement initiatives.  
Service Level Objective Management (SLO Management) is a crucial aspect of IT service management that ensures IT services meet customer expectations.

## SLO Management overview {#exploring-service-level-objective-management__cf-exploring-parent-overview}

SLO Management is a framework for setting clear expectations and measuring the performance of IT services. It helps organizations ensure consistent service delivery and identify areas for improvement.
SLOs define the target service level for a specific service, such as incident resolution or service request fulfillment. Effective SLO management involves setting realistic objectives, monitoring performance, and continuously improving
services to meet customer needs.

## SLO Management users {#exploring-service-level-objective-management__cf-exploring-parent-users}

{#exploring-service-level-objective-management__table_ayk_qqd_pwq__entry__3}

| Users | Description | Contains Roles |
|-|-|-|
| admin | A ServiceNow administrator is responsible for the administration, development, operation, education, and maintenance of the ServiceNow platform. Responsible for installation and can perform Service Operations Workspace Admin Center configuration of SRM. | All |
| Administrator \[srm_admin\] Note: Not the ServiceNow admin role | SRM Administrators can manage account settings, configurations, and users. Administrators can perform the following actions: * Access, create, edit, or delete all SRM configurations. * Add or manage integrations. * Create Integrations with Application Performance Monitoring (APM) tools * Set up and maintain Reliability Indicators. * Set up and maintain Error Budget Policies. {#exploring-service-level-objective-management__ul_byk_qqd_pwb} | * Manager * Responder {#exploring-service-level-objective-management__ul_cyk_qqd_pwb} |
| Manager \[srm_manager\] | Managers oversee a team of SREs. Managers assign SREs to the team on-call schedule, monitor their performance, create procedures to deal with incidents, and develop solutions. Managers ensure resilience across all the systems and the DevOps workflows. Managers can perform the following actions within the context of their teams: * Define and set up and teams, on-call schedules, and services. * Add and delete users such as responders, and managers for the teams the are a part of. * Add or manage integrations. * Create Integrations with Application Performance Monitoring (APM) tools * Set up and maintain Reliability Indicators. * Set up and maintain Error Budget Policies. {#exploring-service-level-objective-management__ul_dyk_qqd_pwb} | Responder |
| Responder \[srm_responder\] | A Service Reliability Engineer (SRE) that uses SRM to perform everyday tasks. Responders are the individuals who are on call and diagnose and remediate incidents. Responders can only access configurations that they're a part of. They can only access the alerts or incidents for which they have permissions. SREs can perform the following actions, within the context of their teams: | Inherits 17 roles including the following: * cmdb_read * sn_sow.sow_user * sn_sow_srm.srm_responder * workspace_user * slo_operator {#exploring-service-level-objective-management__ul_fyk_qqd_pwb} |
[Table 1. Users]

{#exploring-service-level-objective-management__table_ayk_qqd_pwq}  
Note:  
Users of the SLO plugin without SRM should ensure that the required alert and cmdb_ci read access is granted to their team members.

## SLO Management workflow {#exploring-service-level-objective-management__cf-exploring-parent-workflow}

1. Define SLOs - Identify critical services and define SLOs based on customer expectations and business requirements.
2. Establish SLIs - Develop Service Level Indicators (SLIs) to measure SLO performance.
3. Monitor and analyze - Track SLI data and analyze performance against SLO targets.
4. Identify gaps and improve - Determine areas where SLOs are not being met and implement changes to improve service performance.
5. Review and refine - Regularly review SLO performance and refine SLOs as needed.
{#exploring-service-level-objective-management__cf-exploring-parent-workflow-ol}

## SLO Management benefits {#exploring-service-level-objective-management__cf-exploring-parent-benefits}

* Improved service quality - SLOs ensure IT services meet customer expectations, leading to increased satisfaction and loyalty.
* Increased transparency - Clear SLOs provide a shared understanding of service expectations between IT and customers.
* Better resource allocation - SLOs help prioritize resources and focus on areas that need improvement.
* Enhanced collaboration - SLO management encourages collaboration between IT teams and customers to achieve common goals.
* Data-driven decision making - SLO performance data informs decisions and drives continuous service improvement.
{#exploring-service-level-objective-management__ul_mct_vfk_ybc}