Click here for a high level overview of the steps required to create a Service Catalogue, from the art of service. The steps mentioned in the pdf are :
- Definition of Service Families
- Definition of Services within Service Families
- Mapping Services to existing customers
- Mapping expectations and dependencies to services
- Establish Operational Level Agreements
- Establish Service Level Agreements
- Establishment of Cost of Services
- Steady Stage
By the looks of it, these sound very logical steps, however in my opinion these are very very high level steps and tell you what to do, but honestly not in its complete entirety…
I like the fact that ITIL V3 differentiates between a Technical Services Catalogue and a Business Service Catalogue, however what I do not like is that it uses IT Services in both the definitions. In my opinion, Business Services Catalogue would be for only business services, things which do not have IT Users in its audiences, and IT Services Catalogue would purely focus on those services which are used by IT Users (including Business Users)
BSC could have services related to business applications or similar, services that lead to generation of money for the company
TSC could have services related to IT applications or similar, services that facilitate the use of IT in the organization.
More on this sometime later…
So I had something on 6, 7, and 8 yesterday. Today is the turn of 9.
Hank in this version of the newsletter from DITY, talks about how many 9s do the customers actually need when it comes to availability.
Cost of Downtime (Source : DITY Newsletter)
What this newsletter talks about is three things
- Why should an organization care about availability and has some interesting statistics on CoD (Cost of Downtime)
- How to measure availability, and
- Translating business needs into 9s