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


---

# Using Service Reliability Management

# Using Service Reliability Management {#ariaid-title1}

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

SRM enables you to register services, monitor service health, respond to service degradations with on-call shifts and escalation policies and triggers, and onboard distributed teams with minimal
governance from central IT.

## Basic Tasks in SRM {#using-service-reliability-management__cf-using-parent-steps}

1. [Working with SRM services](https://servicenow-prod.fluidtopics.net/Bh9oV5ilIpogAFSsvfgB9Q)  
   A service represents a functional outcome like networking, payments, or HR services, that is owned by a team. To deliver that outcome, a service can contain one or more technical components like a user authentication service, or a piece of shared infrastructure like a database.
2. [Working with SRM teams](https://servicenow-prod.fluidtopics.net/q14ZUToJwTPwK6Z03rL06w)  
   Manage schedules and define escalation policies for your team. That way, your team sees who is on call and accountable and can have the confidence that critical alerts or incidents are acknowledged in a timely manner.
3. [Working with SRM reliability tasks](https://servicenow-prod.fluidtopics.net/tgAkAyKZ2~uKjvQWIo7DCw)  
   Alerts, incidents, and change requests are reliability tasks. From creation to resolution, SRM helps you manage your alerts throughout the response life cycle.