Administer > Module Configuration > Service Level Management > Service Level Management Lifecycle

Service Level Management Lifecycle

The following process is recommended for configuring Self Service and the Service CatalogHow customers order products and services from your organization. One or more IT systems enabling a business process.. Use the service owner or administrator role.

Service Level Management Lifecycle

1. Create a serviceA generally defined framework for actions or items that are provided to an end user. Specific actions, items, response times, and other details are not part of a service definition; those details are defined in service level packages, request offerings, and service level agreements. Instead, a service provides the basis for those detailed definitions. An example of a service is email. After a service is defined, end users do not see or request the service itself. Instead, they use the Service Catalog to view and submit request items, which are features that are based on the service and that you (as a service owner) define and make available to them. Multiple request offerings can be based on the same service.. Specify characteristics that define a service. These characteristics are inherited by all service level packages and offerings that are linked to the service. See Creating a Service.
2. Create request offerings and form offerings and assign each to a category. After a service is defined, end users do not see or request the service itself. Instead, they select from lists of offerings made available to them through the Service Catalog. See Working with Request Offerings.
3. Define service level packageThe level of service provided to a customer. A defined level of utility and warranty for a particular service package. Each service level package is designed to meet the needs of a particular pattern of business activity.s. Specify additional characteristics that define how a service is offered to subscribers. A service level package is based on one service, from which it inherits general characteristics such as owner, provider, and so on. See Service Level Packages.

A service can have multiple service level packages. For example, you could define service level packages named "Gold," "Silver," and "Bronze" for a service, each with a different price, response time, hours of operation, and so on.

The promises offered by a service level package are dependent on a number of factors: promises made by other groups within the organization (captured in a service level agreement) and promises made by outside vendors (captured in an underpinning contract). See Service Level Agreements and Underpinning Contracts.

The degree of compliance an organization can provide (and therefore can be offered to a customer), is defined as a service level target, and can also affect the service level package. Operational level agreements, underpinning contract, and service level agreements all have defined targets. See Service Level Targets.

4. Link request offerings to a service level package. After you define a service level package, you must link it to one or more request offerings. When a link is established, the request offering is included in the service level package. See Request Offering Link.
5. Publish service level packages. A service level package must be published to make it available for subscription. See Working with Request Offerings.
6. Subscribe to service level packages and create service level agreements. Request offerings are available to end users after you create a service level agreement by subscribing to a service level package. See Working with Request Offerings.