Creating and Updating Services › Request SLAs and Calendars › How to Create Request SLAs

How to Create Request SLAs

As an administrator, you optionally create request SLAs to monitor whether service options in a service option group are processed within the time period that you specify. Your SLAs specify time to warning and time to violation for the selected service option. To create SLAs, follow this process:

Note: Request Service Level Agreements (SLAs) are a feature of CA Service Catalog, while Quality of Service (QoS) SLAs are available only if CA Service Catalog is integrated with CA Business Service Insight. The terms request SLA and QoS SLA are used when needed in the documentation to distinguish between the two types of SLAs.

1. Select Catalog, Service Offerings.
2. Expand the tree and select the service to which you want to add the SLA.
3. Click the Definition tab of the service.
4. Click the expand sign on the header next to the service option group name to expand and display the service options.
5. Locate the service option to which you want to add the SLA.
6. Click the SLA icon.

   The SLA Definition dialog appears.

7. Click Add to create the SLA.

   A new SLA definition appears.

8. For each SLA, specify the following:
   • Starting and ending statuses to monitor. A sample starting status is Submitted, and a sample ending status is Approved.
   • Length of time, in days, hours, and minutes, to reach warning status.
   • Length of time, in days, hours, and minutes, to reach violation status.
   • A meaningful descriptive name; for example, a name that summarizes the starting status, ending status, and duration. Examples include Submitted-to-Approval Done--Warning--4 Hours, Submitted-to-Approval Done--Violation--4 Hours, and so forth.
   • The Expectation Level, the percentage of SLAs that you expect to be completed without warnings or violations, for example, 80, 90, or 100.
9. If you create multiple SLAs, select one of them as the primary SLA by clicking the option button in the Primary column. If a service option contains only one SLA, then that SLA is the primary SLA.

   When a service option has multiple SLAs, the status of the primary SLA determines the status of the service option as a whole, regardless of the status of the other SLAs. For example, suppose you create four SLAs for a service option. If the primary SLA has not reached a warning or violation when the request containing the service option is completed, then the SLA for that service option is satisfied, even if all of the other three SLAs did reach a warning or violation.

   Conversely, if three of the four SLAs have no warning or violation, but the primary SLA has a warning or violation, then the service option as a whole has a warning or violation. With this information in mind, choose the primary SLA with special care.

   Both warnings and violations are reflected in SLA Reports.

Note: You can optionally set up automated email alerts to be triggered if an SLA reaches warning or violation status, as explained in How to Configure Automated Email Alerts for SLA Warnings and Violations.