Posts Tagged ‘benefits of a service catalog’

Should IT Chargeback?

October 23rd, 2012

The Question: I learned early on with the IMF while facilitating a meeting that if I have a long phone call I need to make I should just ask the question “is IT Chargeback is a good idea?” I could then leave the room and be sure the discussion was still going when I returned an hour later. The particularly good news on this topic, as opposed to function points for example, is that most IT executives can argue both sides.

Increasingly of late, there seems to be some consensus that either IT Cost Charge Back or Look Back is a critical discipline to effectively run a world-class organization. Certainly the addition of Chargeback in ITIL version 3 about 5 years ago pushed many off the fence. Now most organizations have a services catalog so they can articulate cost to the business, and for good reason. A good IT service catalog serves three functions: helps the business make good decisions; makes IT accountable; and allows predictable budgeting.

Changing the Game from Defense to Offense: A good, transparent service catalog that includes external benchmark data can change the posture from reactive (defense) to proactive (offense). Often far too much time is spent defending and justifying charges to the user community when doing the job right upfront can alleviate so many hours of justification.  Granted, doing the job right is no simple task and requires a detailed understanding of cost and quality. However, the benefits will allow IT to effectively run IT as opposed to a never ending game of whack a mole justifying every expense to every department.

Never say Cost without Quality: It is important to remember that one can never discuss cost without quality. Low cost, low quality and high cost, high quality are two easy to maintain options. A good service catalog can also explain the additional components and costs needed to achieve high quality.

Benefits of Demand Management: In our benchmarking practice, we continually observe a direct coloration between low cost/high quality organizations and their ability to forecast demand accurately. This pertains to projects where poor forecasts can either leave budgeted money on the table, money that could have been used for other things, or cause budget shortfalls. It also pertains to hardware and software where emergency purchases can hike acquisition costs or conversely cause expensive over capacity situations. Additionally, it will completely eliminate the opportunity to time buys strategically to reap maximum discounts.

So the discussion continues November 1st in Denver with our IT Finance Managers at the Fourth Quarter ITFM Meeting. Members can register to attend by logging into The IMF website and visiting our Events page.

 

Tips For Your Service Catalog

November 5th, 2010

Service catalogs are nothing new to the IT community. The service catalog is an important tool for service strategy because it is the virtual projection of the service provider’s actual and present capabilities. It serves as a service order and demand channeling mechanism. It also acts as the acquisition portal for customers, including pricing and service-level commitments, and the terms and conditions for service provisioning. If your organization has a service catalog or is in the process of implementing one, here are some tips to ensure its success:

1. Skip the Service Catalog documentation project

        -Efforts to define services in a static document do not achieve results

2. Tie your Service Catalog program to a major initiative that delivers business value:

       -Provide visibility and IT financial transparency

       -Standardize and rationalize IT services to cut costs

       -Make it easier for users to request services

       -Improve operational efficiencies for request fulfillment

3. Secure executive support and build a proper team

4. Leverage best practice methods and tools

      -The Service Catalog is not simply a front-end to your Service Desk

      -The right tools can help ensure success – but not all tools are alike

To read more about the benefits and implementation of a service catalog, check out our report Managing IT Costs Through a Service Catalog.

Benefits of a Service Catalog

April 27th, 2010

By: Dave Burkett, Global Information Partners

In a previous Blog, we discussed the importance that Service Catalogs have in improving the relationship that IT has with the Business Units.  As well as this important benefit, Service Catalogs (and the resulting shift toward thinking of IT as a business entity), bring several additional benefits. 

Performance Measurement

After the implementation of a Service Catalog, an objective basis for measuring performance becomes available.  IT can now publish trends for the unit cost of each service, showing how it is able, in many cases, to take advantage of technology to reduce unit costs to the business unit.  This focus on unit cost is critical, as it shifts the discussion away from rising IT costs (which in most cases are due to increased consumption), and moves the discussion toward service delivery, measured by unit costs – IT is responsible for unit costs; the business units are responsible for managing consumption.  The added structure around budgets and costs will facilitate external benchmarks – always a powerful tool to facilitate discussions with the business units. 

A Basis for Planning and Decision Making

The implementation of a Service Catalog forces the manager of each product or service to develop (and hence, better understand) their “Pricing Model”.   In this model, the budgeted costs for the next year are inputted, together with the estimated volumes for that product – yielding the Product Price for next year.  This Pricing model becomes extremely useful in decision making.  The impact on product price for various scenarios (changes in staffing levels, hardware upgrades or software migrations) can quickly be examined.  Many IT organizations find that they begin to test all decisions against the pricing model to see the impact on product price.  If you think about IT operating as a business, then of course, product price becomes paramount in service delivery.

A Basis for Communication

Many IT departments have found that the basis for communication with the business units is significantly increased due to the rigor and structure demanded by a Service Catalog.  The existence of pricing models facilitates discussion such as “why does this product cost so much?”   The business unit can easily be shown the major cost components, Hardware, Software, Support, Premises, etc.  This information is essential in order to counter complaints such as “I can buy a desktop from DELL for $599, but you charge me $200 per month !”  When they are shown that the hardware component of your Desktop service is only 10% of total cost of the desktop product, then this conversation will take a positive turn. 

With the increased transparency available into cost and product makeup, the conversations around differing service levels can now be meaningful.  At some point a business unit will approach you saying, I see that you include “x” in this product – we don’t really want “x”.  Would you consider defining a product which excludes this?  The discussion around the true cost of “x” and the risks and other considerations is greatly facilitated with the information available with a well defined Service Catalog.

The structure provided by a Service Catalog enables the IT shop to operate as if it were an independent business, competing for the business unit’s IT dollars.  This shift toward a business relationship between IT and the business is a natural one for the business unit – all of its other dealings with vendors are on a very formal basis, why shouldn’t it deal with the internal IT department the same way.

About the Author:
David Burkett has a distinguished career in IT with roles ranging from Data Center Manager to CIO to heading an international consulting firm. Prior to joining IMF, Dave served as President of Compass North America and was responsible for the activities of the offices in the U.S. and Canada. He joined Compass in 1992, establishing the Canadian operation. Under his direction, the Company grew to become the largest of its kind in Canada. Dave became President of Compass America in 1998. He has 30 years of experience in all aspects of Information Technology. Dave is an expert in technology planning, systems management, achieving cost effective operations, IT trends and directions and IT outsourcing.

Before joining Compass, Dave was the Information Systems Executive with The Mutual Group. During his career, he has shared his expertise in regular speaking engagements, including IT Best Practices, IT Outsourcing and IT Trends and Directions.

Dave is a graduate of the Queen’s University Executive Business Program, and he earned his Bachelor’s Degree in Math from the University of Waterloo. Dave is a Fellow of the Life Management Institute.