Checklist Service Portfolio: Difference between revisions
m (→Overview) |
m (→Glossary) |
||
Line 8: | Line 8: | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
<p> </p> | |||
'''ITIL Process''': [[ITIL | '''ITIL Process''': [[ITIL Service Strategy|ITIL 2011 Service Strategy]] - [[Service Portfolio Management]] | ||
'''Checklist Category:''' [[ITIL-Checklists#ITIL 2011 Templates|Templates ITIL 2011]] - Service Strategy - [[ITIL-Checklists#Most popular ITIL Templates|Most popular ITIL Templates]] | '''Checklist Category:''' [[ITIL-Checklists#ITIL 2011 Templates|Templates ITIL 2011]] - Service Strategy - [[ITIL-Checklists#Most popular ITIL Templates|Most popular ITIL Templates]] | ||
Line 17: | Line 17: | ||
<p> </p> | <p> </p> | ||
===<span id="Service Portfolio Template">Overview</span>=== | |||
The ''Service Portfolio'' represents a complete list of the services managed by the service provider. | The ''Service Portfolio'' represents a complete list of the services managed by the service provider. | ||
Line 31: | Line 33: | ||
__TOC__ | __TOC__ | ||
== Service Portfolio - Contents == | ==Service Portfolio - Contents== | ||
''For each service the Service Portfolio defines:'' | ''For each service the Service Portfolio defines:'' | ||
Line 37: | Line 39: | ||
<p> </p> | <p> </p> | ||
====Name==== | |||
====Current lifecycle status of the service==== | |||
(e.g., "Proposed", "Defined", "Chartered", "Designed", "Built", "Tested", "Released", "Operational", "Retired") | (e.g., "Proposed", "Defined", "Chartered", "Designed", "Built", "Tested", "Released", "Operational", "Retired") | ||
====Service Type==== | |||
# Customer-facing service (services delivered to the customers) or supporting/technical service (invisible to the customers, used to underpin customer-facing services) | # Customer-facing service (services delivered to the customers) or supporting/technical service (invisible to the customers, used to underpin customer-facing services) | ||
# Internal/ external: Internally provided service or a service sourced from an external service supplier | # Internal/ external: Internally provided service or a service sourced from an external service supplier | ||
====Service Owner==== | |||
(responsibility for service provisioning) | (responsibility for service provisioning) | ||
====Customers==== | |||
(customers currently using this service) | (customers currently using this service) | ||
====Contacts and procedures for signing up to the service==== | |||
# e.g. contact details of the responsible [[Roles | # e.g. contact details of the responsible [[ITIL Roles#Service Level Manager|Service Level Manager]] | ||
# Procedure for signing up | # Procedure for signing up | ||
====Description/ desired customer outcome==== | |||
# Business justification (value added from a business point of view) | # Business justification (value added from a business point of view) | ||
# Business processes/ activities on the customer side supported by the service | # Business processes/ activities on the customer side supported by the service | ||
Line 62: | Line 64: | ||
# Desired outcome in terms of warranty (example: "Access is facilitated worldwide in a secure and reliable manner") | # Desired outcome in terms of warranty (example: "Access is facilitated worldwide in a secure and reliable manner") | ||
====Offerings and packages, variations==== | |||
# e.g. different Service Level packages on offer | # e.g. different Service Level packages on offer | ||
# e.g. different coverage of time zones | # e.g. different coverage of time zones | ||
# e.g. different coverage of geographical regions | # e.g. different coverage of geographical regions | ||
====Costs and pricing==== | |||
# Available pricing schemes for the service provision | # Available pricing schemes for the service provision | ||
# Rules for penalties/ charge backs | # Rules for penalties/ charge backs | ||
====Dependencies==== | |||
# Services | # Services | ||
## Required Infrastructure Services (Infrastructure Services on which this service depends) | ## Required Infrastructure Services (Infrastructure Services on which this service depends) | ||
Line 77: | Line 79: | ||
# Components/ [[Checklist CMS CMDB|Configuration Items]] (major CIs like on which this service depends) | # Components/ [[Checklist CMS CMDB|Configuration Items]] (major CIs like on which this service depends) | ||
====Planned changes to the service==== | |||
(if any) | (if any) | ||
# References to relevant plans (e.g. Service Strategy Plan, Strategic Action Plans, entries in the [[Checklist Service Improvement Plan SIP|CSI Register]]) | # References to relevant plans (e.g. Service Strategy Plan, Strategic Action Plans, entries in the [[Checklist Service Improvement Plan SIP|CSI Register]]) | ||
Line 85: | Line 87: | ||
# Time schedule and status information | # Time schedule and status information | ||
====References to further documents==== | |||
====Glossary==== | |||
<p> </p> | <p> </p> | ||
<html><a rel="author" href="https://plus.google.com/111925560448291102517"><img style="margin:0px 0px 0px 0px;" src="/skins/Vector/images/itpm/bookmarking/gplus.png" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a></html> | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> |
Revision as of 15:27, 3 August 2013
<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. ..." />
ITIL Process: ITIL 2011 Service Strategy - Service Portfolio Management
Checklist Category: Templates ITIL 2011 - Service Strategy - Most popular ITIL Templates
Source: Checklist "Service Portfolio" from the ITIL Process Map
Overview
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, whose level of service is defined by SLAs), while others are not (Infrastructure Services, whose level of service is 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.
Service Portfolio - Contents
For each service the Service Portfolio defines:
Name
Current lifecycle status of the service
(e.g., "Proposed", "Defined", "Chartered", "Designed", "Built", "Tested", "Released", "Operational", "Retired")
Service Type
- Customer-facing service (services delivered to the customers) or supporting/technical service (invisible to the customers, used to underpin customer-facing services)
- Internal/ external: Internally provided service or a service sourced from an external service supplier
Service Owner
(responsibility for service provisioning)
Customers
(customers currently using this service)
Contacts and procedures for signing up to the service
- e.g. contact details of the responsible Service Level Manager
- Procedure for signing up
Description/ desired customer outcome
- Business justification (value added from a business point of view)
- Business processes/ activities on the customer side supported by the service
- Desired outcome in terms of utility (example: "Field staff can access enterprise applications xxx and yyy without being constrained by location or time")
- Desired outcome in terms of warranty (example: "Access is facilitated worldwide in a secure and reliable manner")
Offerings and packages, variations
- e.g. different Service Level packages on offer
- e.g. different coverage of time zones
- e.g. different coverage of geographical regions
Costs and pricing
- Available pricing schemes for the service provision
- Rules for penalties/ charge backs
Dependencies
- Services
- Required Infrastructure Services (Infrastructure Services on which this service depends)
- Supported services (other services which depend on this service)
- Components/ Configuration Items (major CIs like on which this service depends)
Planned changes to the service
(if any)
- References to relevant plans (e.g. Service Strategy Plan, Strategic Action Plans, entries in the CSI Register)
- Business case/ cost-benefit analysis
- Priority of the envisaged change
- Risks associated with the envisaged change
- Time schedule and status information
References to further documents
Glossary