become-itil-foundation-certified-abhinav-kaiser(www.ebook-dl.com)
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 4 ■ Service Strategy<br />
is ready to be launched. That’s when the <strong>com</strong>petitors would learn about it as well, most<br />
likely too late for them to react and start matching services.<br />
For this example, the mobile phone service provider needs to create new services<br />
fairly regularly to stay <strong>com</strong>petitive. This is perhaps true for all service providers in other<br />
areas of IT as well. Every <strong>com</strong>pany must apportion some of their budget toward creating<br />
new services and improving existing services. If new services fail to kick off on a regular<br />
basis, the service provider will soon find itself in the back of the line and playing catch up<br />
for the rest of its lifetime. This showcases the importance of the service pipeline and the<br />
criticality it brings to the table.<br />
What are some of the triggers for creating new services or improving existing<br />
services? Here are some:<br />
• Feedback regarding existing service<br />
• Customer requests for a new service<br />
• Competitors launching a new service<br />
• Service provider has new strategic objectives<br />
• New technological advancements<br />
• Lack of out<strong>com</strong>e from existing services<br />
4.8.1.1.2 Service Catalog<br />
The service catalog is the database of all services that are currently available. The service<br />
catalog is visible to the customer, in fact, the service provider will showcase it every time<br />
he sits down with the customer in order to get new business.<br />
Service catalog is discussed at length in Chapter 5. Service catalog management is<br />
a process that resides in the service design phase. However, as the service catalog is an<br />
integral part of the service portfolio, I will discuss the topic here and connect it to the<br />
interfacing databases.<br />
A service catalog is like a restaurant menu. It has all the live services listed, including<br />
the ones that are going to be live in the near future. For every listed service, there a brief<br />
description of what the service delivers, how to request it, who to contact, and, most<br />
importantly, the cost of availing the service.<br />
The services listed in the service catalog are in the operational phase, in the sense<br />
that the service has been fully developed and is working as per the design. There could<br />
be improvements to the service, but they are not made public unless they are ready for<br />
deployment.<br />
Imagine you head to a restaurant and glance through the menu items: appetizers,<br />
entrees, soups, meals, desserts, etc. All the items listed are available for delivery. They<br />
would not list items in there that are not delivered, right?<br />
It is <strong>com</strong>mon for a service provider to maintain multiple service catalogs, depending<br />
on the customers and market spaces. For example, a service provider may rank the<br />
customers as gold, platinum, or diamond and provide varied services, with differentiating<br />
SLAs and cost points.<br />
56