Sie sind auf Seite 1von 5

Defining an SLA - ServiceNow Wiki

8/7/12 11:56 AM

Wiki home

Community

Training

Support

Company home

Demo
Search

Defining an SLA
Home > Deliver > Planning and Policy > Service Level Management > Defining an SLA Functionality described here requires the Admin role. Functionality described here requires the SLA plugin. ITIL Service Level Management Service Level Agreements Getting Started with SLAs Defining an SLA Creating an SLA Workflow Defining a Schedule for an SLA Defining Service Levels for Catalog Fulfillment Reporting on SLAs Modifying SLA Condition Rules

Contents
1 Overview 1.1 OLAs and Underpinning Contracts 2 Defining an SLA 3 Example 3.1 Defining the SLA 3.2 Testing the Service Level Agreement

1 Overview
Service Level Agreements (SLAs) allow the service desk to track whether or not their representatives are providing a certain level of service. The most common use of SLAs is to ensure that incidents are resolved within a certain amount of time. A Service Offering SLA is an SLA that applies only to service offerings for business services (requires Service Portfolio Management plugin and Service Portfolio Management - SLA Commitments plugin). To define a service offering SLA, navigate to Business Services > Service Offering SLAs > SLAs.

SLA Contract Add-on Defining a Service Contract Related Topics Introduction to Tasks Task Administration Workflow Approvals and Assignments Scripting Approvals and Assignments Service Portfolio Management - SLA Commitments

1.1 OLAs and Underpinning Contracts


The Task SLA engine provided by the plugin can also be used to define OLAs or Underpinning Contracts in exactly the same way as SLAs. The only difference between SLAs, OLAs, and Underpinning Contracts is the Type field on the Task SLA form. Changing the type field does not change the behavior of the Task SLA. For an example of an OLA, see Defining an OLA for Catalog Fulfillment.

2 Defining an SLA
To define an SLA, navigate to Service Level Management > SLA Definitions and click New. Populate the form as follows: Field Name Type Input Value An identifying name for the SLA. The type of agreement being defined. This is used for informational purposes and does not change the behavior of the SLA. Choices are: SLA OLA Underpinning Contract Table Workflow Duration Type Duration The task table (table extending Task Table) whose records will be tracked by this SLA. The SLA workflow that determines what activities occur in response to the SLA. For more information, see Creating an SLA Workflow. Determines how the duration of the SLA will be calculated. This can be a User Defined Duration, or a Relative Duration (e.g. "end of next business day."). If Duration Type is User Defined Duration, this is the length of time the SLA will run before it is marked Breached. Note: The number of days specified in this field are converted into 24 hours. Thus, if a schedule is used (see next field) that has eight hour days, the duration 1 Day will set the SLA to breach three business days later. Schedule The hours during which the SLA should time. This allows SLAs to be defined which only count during business hours. For more information, see Using Schedules.
Pgina 1 de 5

http://wiki.servicenow.com/index.php?title=Defining_an_SLA

Defining an SLA - ServiceNow Wiki

8/7/12 11:56 AM

Timezone

If the SLA is defined in the SLA Properties (Service Level Management > SLA Properties) as using the SLA Definition's time zone, this field determines what time zone the SLA will use. For more information, see Using Time Zones.

Retroactive Start

Retroactive Start determines the SLA's behavior if it is attached to the task at a point later than the task's creation. If Retroactive Start is true, then the SLA will time from the task's Created On date and time. If Retroactive Start is false, then the SLA will time from the date and time that it was attached to the SLA. For example, if an Incident's Priority is changed to 1 - Critical and a Priority 1 SLA is attached at that time, Retroactive Start means that the SLA will count from when the incident was first created, rather than from when the Incident's Priority changed.

Start Conditions Pause Conditions End Conditions

Defines conditions (using the Condition Builder) which, if met, attach an SLA to a task on the table specified in the Table field and begins the timing. Defines conditions (using the Condition Builder) which, if met, pauses the SLA's timer. Once the conditions are no longer met, the SLA will resume. Pause conditions are not compatible with Relative Durations. Defines conditions (using the Condition Builder) which, if met, ends the SLA's timer. If these conditions are met before the end of the duration defined in the Duration Type and Duration fields has elapsed, the SLA's state will be set to Achieved. If these conditions are no longer met, the SLA will not resume. However, if the Start Conditions are met again, a new SLA will attach.

Fields which can be added by personalizing the form: Condition class Since June 2011 Preview 2 - Accepts the string value of an SLA Condition Rules record to use instead of the global Condition Rules. If blank, the global rules will be used. For more information, see Modifying SLA Condition Rules.

3 Example
This example will demonstrate how to use the SLA Plugin to create a Service Level Agreement to ensure that critical incidents logged in Paris are handled within 1 business day. This example uses the demo data within the system.

3.1 Defining the SLA


To define the SLA, navigate to Service Level Management > SLA Definitions, and click new. Populate the fields with the following: Name - Name the incident Priority 1 Paris Incident. Type - Specify the type as SLA. Although the type does not change the behavior of the SLA, the type will help distinguish between agreements with customers, vendors, and internal departments. Workflow - Select Default SLA Workflow. To learn how to create a custom Workflow for SLAs, click Creating a Service Level Management Workflow. Duration Type - Select End of next business day. This means that, regardless of when the ticket is opened, the SLA will calculate the end of the next business day and set that as the deadline for the SLA. Schedule - Select 8-5 weekdays. This means that the timer will run between the hours of 8 and 5 on weekdays. Once those fields are populated, it is important to populate the condition fields: Start Condition - Set the following conditions: Location is Paris, Priority is 1 - Critical, and Active is True. Now the SLA will attach to any active Priority 1 incidents in Paris. Stop Condition - Set the condition Active is False. This means that once the incident is closed or resolved, the SLA will stop tracking time. Pause Condition - Set the conditions Incident is one of Awaiting Problem, Awaiting User Info, or Awaiting Evidence. This will avoid tracking time while the service desk is waiting for outside events. The form should look like this:

http://wiki.servicenow.com/index.php?title=Defining_an_SLA

Pgina 2 de 5

Defining an SLA - ServiceNow Wiki

8/7/12 11:56 AM

The result is that whenever an incident is listed as being Priority 1 incident in Paris, the following workflow will be launched:

The workflow will run, pausing if the incident is awaiting user info or evidence, and will be completed if the incident becomes inactive.

3.2 Testing the Service Level Agreement


To test the new SLA: 1. Navigate to Incident > Create New. 2. Set Priority to 1 - Critical, and Location to Paris. 3. Save the incident. 4. Reload the form.

http://wiki.servicenow.com/index.php?title=Defining_an_SLA

Pgina 3 de 5

Defining an SLA - ServiceNow Wiki

8/7/12 11:56 AM

Once the incident is saved, a related list of Task SLAs will appear at the bottom, with both the Priority 1 Paris Incident SLA and the out-of-box Priority 1 Response SLA:

Clicking on the Priority 1 Paris Incident SLA will display information about this instance of the Task SLA:

Clicking the Show Workflow link will display the workflow attached to the SLA's progress:

http://wiki.servicenow.com/index.php?title=Defining_an_SLA

Pgina 4 de 5

Defining an SLA - ServiceNow Wiki

8/7/12 11:56 AM

Category: Service Level Management

Contents > Deliver > Planning and Policy Service Level Management > Service Level Management
This page was last modified 20:42, 16 January 2012. This page has been accessed 10,836 times.

http://wiki.servicenow.com/index.php?title=Defining_an_SLA

Pgina 5 de 5