« June 2005 | Main | December 2005 »

October 26, 2005

Re-Emergence of the Service Catalog

Boris By Boris Pevzner

I was recently at a meeting with fifteen Fortune 100 CIOs, discussing with them my vision for service delivery management around the Service Catalog.  Most of the heads in the room were nodding in agreement, but the CIO of one of the Big-Five accounting firms took issue with me: “Service Catalogs? – that’s noting new.  We’ve had a Service Catalog for the last ten years!”

After some quizzing, it became clear that what he was referring to was a list of available services, applications and capabilities delivered and supported by the IT organization.  It’s true that such “inventories of services” were quite popular with IT organizations 5-10 years back, as this gave IT shops an illusion of being in control of the services they were delivering.  However, these “inventories” (usually an Excel spreadsheet) quickly turned out to be not maintainable (falling out of sync with reality soon after their initial creation), not actionable (lacking service request and fulfillment mechanisms), isolated (usually merely a point of reference used primarily in the help desk function) – and thus ultimately destined to failure.

Enter the “IT-Business Alignment” imperative of the last three years: the need for IT organizations to become more “customer-centric” by aligning the services IT delivers with the most critical business functions of the organization.  This alignment has prompted a resurrection of the Service Catalog as a means to capture and communicate those linkages.  In fact, in many leading-edge companies today, the trend has been toward positioning the Service Catalog as the central element in the ITIL/ITSM service delivery models.  In the words of the CTO of a large Federal government agency, “The vendors and IT operations alike have recognized that continual state of change and agility are a way of life in today’s IT world and that the Service Catalog provides the basis from which these changes can be managed.”

Service Catalogs are now being offered (by vendors like my company, Lontra) as a robust capability that no longer simply capture a list of services but also facilitates:

  • Operational Level Agreements, Service Level Agreements (internal & external customer expectations)
  • Catalogs of supporting and underlying infrastructures and dependencies (including direct links into the CMDB)
  • Hierarchical service models
  • Process driven modeling and provisioning (workflow). 

This is a long way from the old “inventory of services” spreadsheet!   Unfortunately, the terminology can be confusing… even if you are the CIO of a Big-Five accounting firm!

Posted on October 26, 2005 | Permalink | Comments (2) | TrackBack