Working with Service Level Agreements

itil defines a service level agreement (sla) as an agreement between you (an it service provider) and an end user customer a service level agreement does the following describes the it services a single service level agreement can only cover one it service or customer documents the service level targets specifies the vendor and the customer's responsibilities service level agreement determines the level of service outlined in the service level package (constrained by service level targets) each organization has a service level agreement for all its published services a single service level agreement is attached to only one organization but a service and its corresponding service level package can be attached to one or more organizations if there is no service level agreement, requirements for handling incidents and service requests are covered by the default escalation schedules refer to default escalations docid\ nx511p1yft4c9v57akrq for example, a customer submits a service request against the data services organization the data services organization has a gold service level package defined for it per the agreements of the gold service level package, the sales organizational unit is defined when a service level agreement subscription is created for the data services service for the sales organizational unit, the targets defined in the gold package are copied over when an employee from the sales organizational unit submits a service request for data services, the service level agreement field shows the agreement for the organizational unit of the customer when a customer creates a service request from the service desk, the system populates the service level agreement field only if there is a service level agreement defined for that service if the customer's organization does not subscribe to the request offering, the system auto fills the service level agreement field with default service level agreement values (for example, for the entire corporate organization) if the customer's organization does subscribe to the request offering, the system auto fills the service level agreement field with the service level agreement value defined for the organizational unit creating a new service level agreements log in to the as a service owner navigate to the service tab and click new service the new record window appears in the details tab, enter the required service name, select production from the status drop down list, and enter the data in all mandatory fields, and click save click list view , then double click the newly created service to open it select the service desk category tab the service desk category tab appears click the link icon, select the appropriate category to assign, and click select you can view the assigned service level package under the service level package tab navigate more > service package the service package window appears to modify the service package name, double click the sla , edit the details, and click save click request offerings , in the application the request offerings window appears a click new > request offering b in the define request offering tab, select the created service from the service drop down list, enter data in the mandatory fields and click next c in the design request form tab, select the required tools from the form designer tools list and click next d in the plan request fulfillment tab, select the appropriate and click next e in the publish action access tab, click add , select published from the status drop down list, and click save refresh the application click sla subscription and then click create agreement in the select service tab, select created sla , click create agreement , choose required options for each tab and click save verifying the new service level agreement log in to as a click the configure icon the admin default window appears navigate to build > automation tools > escalation schedules to view the created sla, select the category assigned during its creation now you can view new sla for review and management within the ism application creating a service level agreement subscription before creating a service level agreement, you must create your request offerings and any optional service level packages includes various basic services that you can use or modify to fit your organization log in to as a service owner open the sla subscription workspace the system displays a list of agreements do either of the following click all services from the left pane to view all the service level agreements click on a service name to view agreements for a specific service click create agreement the system displays the select service page and displays selected next to the service that is currently selected click select next to a service to add it to the agreement the system adds the service to the agreement to see the service details, click more click next the system displays the service information page choose an organizational unit for this subscription from the select organizational unit pane if you select the top level, the agreement applies to all users under this organization from the select service level package section, select a service level package the system displays selected next to the package that is currently selected click next the system displays the customize service options page click customize to configure the service options for the service, then select the options, if any click next the system displays the review and save page review the service level package to modify any part of the package, click change next to an option and edit it click save the system lists the service level agreement that you created in the sla subscription workspace ## viewing service level agreements subscription log in to as a service owner open the sla subscription workspace the system displays a list of agreements sla subscription workspace click on an agreement to open and view its details deleting a service level agreement subscription when you delete a service level agreement, all the associated links to it in service, service level package, request offering, and delivery escalation will be removed log in to as a service owner open the sla subscription workspace the system displays a list of agreements select the agreement to delete and click the delete icon click yes in the prompt message you cannot delete a service level agreement if it is used in a service request in such a scenario, first delete the service request and then delete the sla adding request offerings to an existing sla subscription log in to as an administrator open the request offering workspace create a new request offering and select the name of the sla subscription from the service drop down list for more information, refer to creating a request offering docid\ onsxnvvfibkmacs g1jh6 change the role to service owner open the sla subscription workspace select an agreement from the list the request offerings created in step 3 are listed, with the text add to sla next to them, indicating that they need to be added to the selected sla the add to sla text is also visible for request offering when a new agreement is created select add all to published sla the request offerings are linked to the sla subscription select the sla subscription again to view all the request offerings that you just added the add to sla text is no longer visible once you add the request offerings to the agreement