Published:
February 03 2012, 02:33 PM
|
no comments
by
Eric Feldman
With the widespread adoption of cloud services, there is enormous effort to define offerings and align to market based pricing.
Let's face it. If you are going through a cloud transformation initiative, one of your business drivers is to reduce expenditures. In order to calculate your savings, you must have at least some basis of comparison of the service cost or value. And to calculate service costs, you must first define those services. This is a business exercise, yet I see many companies incorrectly focus their cloud initiative exclusively on their infrastructure.
But how does a Service Catalog help with an enterprise or MSP cloud initiative?
We can explain this better with a more familiar metaphor. When you are in a restaurant, you have no knowledge of the types of stoves, cooking utensils, or what brand of knives the chef uses. While you will see a waiter or server write your orders on a piece of paper, you are not aware of the ticketing system used - whether the paper is given to the kitchen staff, or the order is entered into software. In reality, what is in the kitchen is almost irrelevant.
What you are aware of is the menu and the descriptions of choices which can be written in elaborate or simplistic terms. You know the price, and how the food offerings are bundled. And you might know the approximate time your food will be delivered, either informally, or by explicit obligation. Remember the pizza guarantee, delivered in 30 minutes, or it is free?
Do you really care how your food is prepared in terms of the type of equipment used as long as it meets or exceeds your expectations, provides good value for the price, and service is appropriate? Does it matter how many burners are on the stove, or how many BTUs it consumes per dinner?
A similar environment exists for cloud services. When you request something from an enterprise catalog, you do not care what, if any, automation tools are employed, nor do you typically care about the process used to deliver the service. You do care that the service is delivered in the expected timeframe, is appropriate to your needs, and if being charged for its use, is priced competitively to market equivalents.
As a result, the Service Catalog becomes the central and primary component of a cloud initiative. In this regard, we refer to a Service Catalog as the "driving force to deliver the cloud." It provides the basis and environment for which cloud services can be defined and delivered.
The Service Catalog is not the actual service - regardless if it is cloud based, virtual, or with physical elements - but it provides a representation or abstraction of the various components and parameters. A Service Catalog is not the process, but provides seamless access to the process from an end user. A Service Catalog is not the infrastructure, but enables a pathway to leverage its use via the process. And a Service Catalog is not a specific entry to a general ledger, but it does publish the price, and can calculate and charge for the service usage.
When planning cloud service deployments, many IT organizations concentrate their efforts on infrastructure and tools. I refer to this as a bottom up approach - the equivalent of a new restaurant deciding upon the brand of stove, pots and pans, and refrigerator before the recipes or menu are prepared.
A better way may be the top down approach - beginning with a type of cuisine, recipes, pricing, and menu - and then building the appropriate kitchen. IT operations are really no different. Cloud service deployments should begin with the service portfolio, the service definition, and how they will be published in the service catalog, or the driving force to deliver the cloud.
For an example of how CA Technologies is leading the industry in providing agile and innovative cloud solutions, see our recent announcement for the CA Private Cloud Accelerator for VblockTM Platforms, a new solution to enable enterprises and managed service providers to offer automated self-service delivery of infrastructure as a service.
Menu image used under Creative Commons License courtesty of pellis.
By: Eric Feldman
Eric Feldman has more than 25 years of experience as a senior architect. With a focus on the areas of service level management and IT asset and financial management, Feldman has specialized in designing and implementing solutions based on CA Service Catalog and CA Service Accounting. He has spoken and...
Read More..