Checklist Service Portfolio

<seo metakeywords="service portfolio template, service portfolio checklist, service portfolio example" metadescription="Service Portfolio Template. The Service Portfolio represents a complete list of the services managed by the service provider. ..." />

DE - ES - Checklist Service Portfolio - Service Portfolio Template

ITIL Process: ITIL V3 Service Strategy - Service Portfolio Management

Checklist Category: Checklists ITIL V3 Service Strategy

Source: Checklist "Service Portfolio" from the ITIL Process Map V3

The Service Portfolio represents a complete list of the services managed by the service provider.

Some of these services are visible to the customers (Business Services, defined by SLAs), while others are not (Infrastructure Services, defined by OLAs or UCs).

The Service Portfolio contains present contractual commitments, new service development, and retired services. It also includes third-party Infrastructure Services which are an integral part of the service offerings to customers.

The Service Portfolio is divided into three sections: Service Pipeline, Active Services (Service Catalogue), and Retired Services. Services should be clustered according to Lines of Service based on common business activities they support. Only active services are visible to customers.

Rather than maintaining one single document, it is advisable to create a hierarchical structure of linked documents, or to use a dedicated database or application in order to manage the Service Portfolio. Ideally, the Service Portfolio is part of the CMS.

For each service the Service Portfolio defines:

1. Name
2. Current status (e.g. „Pipeline“, “Active (Service Catalogue)“, „Retired“)
3. Service Type
   1. Business Service (visible to the customer) or Infrastructure Service (invisible to the customer, used as a building block for Business Services)
   2. Internal/ external: Internally provided service or a service sourced from an external service supplier
4. Service Owner (responsibility for service provisioning)
5. Customers currently using this service
6. Contacts and procedures for signing up to the service
   1. e.g. contact details of the responsible Service Level Manager
   2. Procedure for signing up
7. Description/ desired customer outcome
   1. Business justification (value added from a business point of view)
   2. Business processes/ activities on the customer side supported by the service
   3. Desired outcome in terms of utility (example: “Field staff can access enterprise applications xxx and yyy without being constrained by location or time”)
   4. Desired outcome in terms of warranty (example: “Access is facilitated worldwide in a secure and reliable manner”)
8. Offerings and packages, variations
   1. e.g. different Service Level packages on offer
   2. e.g. different coverage of time zones
   3. e.g. different coverage of geographical regions
9. Costs and pricing
   1. Available pricing schemes for the service provision
   2. Rules for penalties/ charge backs
10. Dependencies
    1. Services
       1. Required Infrastructure Services (Infrastructure Services on which this service depends)
       2. Supported services (other services which depend on this service)
    2. Components/ Configuration Items (major CIs like on which this service depends)
11. Planned changes to the service (if any)
    1. References to relevant plans (e.g. Service Strategy Plan, Service Improvement Plan)
    2. Business case/ cost-benefit analysis
    3. Priority of the envisaged change
    4. Risks associated with the envisaged change
    5. Time schedule and status information
12. References to further documents
13. Glossary