|
43.What are the Chargback or Charging models?
44.Why is Charging for IT Services optional?
45.What are the funding model alternatives?
46.Service Capability Short Names
47.What is Blooms Taxonomy?
48.ITIL Change and Release Management
43. What are the Chargback or Charging models?
There are five defined charging models that can be used to allocate the costs of service delivery amongst the business units. Each one has its strengths and weaknesses and the selection will be based on many factors (but primarily a decision from the organization finance department).
- Notional –whether actual money will be transferred (real cash or a journal entry) or simply an indication of what would have been paid if charging was in place. The two book method allows for the actual company records to reflect the financial aspects (in one book), but a second (unofficial) book is kept to help demonstrate potential chargeback units and help to influence behaviors.
- Tiered – this model creates layers of service delivery; each at different pricing and performance levels. Typically used in a Gold, Silver, Bronze scenario this model does little to actually change consumer patters and can lead to disputes.
- Metered – the ability to capture real time usage information and translate that into a pre-defined factor (e.g. hours worked, disc storage used).
- Direct Plus – directly attributable costs are allocated to their respective business unit (and the ‘plus’ element is the share of the indirect costs that are spread amongst all business units.
- Fixed (or user cost) – where all costs incurred for the delivery of all IT Services are allocated amongst all the chargeable business units using some pre-defined denominator (the best example used in this case is the number of actual users by business unit (but beware of business unit managers making claims to ‘downsize’ their number of users.
Which ever method is selected the importance of "perception", simplicity and 'understandability' cannot be understated.
Top ˆ
44. Why is Charging for IT Services optional?
The decision to charge will be based on the organizations attitude, history and capability to charge – NOT JUST FOR INFORMATION TECHNOLOGY – for shared services that are delivered (e.g. human resources, information technology, finance and accounting).
It will be natural for cost recovery or profit centers to look for charging mechanisms, whereas a ‘cost center’ IT department by have no drive to charge anything.
Charging for IT Services can have a positive effect on influencing customer behavior.
QUESTION: How much of something do you use if it’s free? ANSWER: Generally, as much as you possibly can!!
QUESTION: How much of something do you use if you have to pay? ANSWER: Generally, only as much as you need!!
Whatever decision is made with regard to charging the method selected needs to provide visibility, accountability and transparency – all critical elements for good corporate governance.
Top ˆ
45. What are the funding model alternatives?
There are three defined methods of funding for IT services. The first “rolling plan funding” is an ideal method if the service provider seeks entire lifecycle funding. That is, as one phase of the lifecycle ends for a service (e.g. Service Design ends), then funding for the next phase of the lifecycle is submitted. This means that the funding cycle is not determined by the calendar, rather the progression of a service through its lifecycle.
Trigger-based plans are funding requests made at defined points in time. These defined points in time are not particular dates, but are triggers for funding activity. The approval of a change; identification of capacity related issues; failure external audit for Continuity site.
Finally, zero based funding – this is the most common method and represents the easy choice for most managers. The amount of funding sought is sufficient to cover costs of service deliver for a given period of time (typically 12 months). This funding method must make allowance for changes in business strategy or unforeseen circumstance.
Top ˆ
46. Service Capability Short Names
With the announcement of the ITIL service capability programs there are also new short names that we need to get used to.
So by way of short summary:
- PP&O = Planning, Protection and Optimization
- SO&A = Service Offerings and Agreements
- OS&A = Operational Support and Analysis
- RC&V = Release, Control and Validation
Top ˆ
47. What is Blooms Taxonomy?
In simple terms a taxonomy is a way to classify, order and/or categorize "things".
Any "things" can be subject to a taxonomy. However, most common is living organisms. For example the following breakdown applies to Biological classification of of organisms.
Kingdom Subkingdom Phylum Subphylum Class Subclass Order Family Genus Species
Needless to say that in the world of Service Management life is not quite as complex. The official accreditor - the APM Group - has elected to follow a six level taxonomy - BLOOMS TAXONOMY - as a way to categorize different levels of ITIL courses and certification.
The six levels are:
- Remembering (recalling information)
- Understanding (explaining ideas or concepts)
- Applying (using information in a familiar situation)
- Analyzing (breaking information into parts to explore relationships)
- Evaluation (justifying a decision or course of action)
- Creating (generating new ideas, products or ways of viewing things)
When applied to ITIL certification the following breakdown starts to make more sense.
- ITIL Service Capability = Blooms Level 3 & 4)
- ITIL v2 to v3 Managers Bridge = Blooms Level 3 and Level 4 for key areas
- In house developed ITIL awareness = Blooms Level 1
- ITIL v3 Foundation = Blooms Level 2 & 3
Top ˆ
48. ITIL Change and Release Management
Change and Release management are often talked about in the same context when discussions are being held about Service Management processes. However, it is important to understand the relationship between the two processes and the fundamental differences.
The change management process takes ownership of change assessment and change approval. Whereas Release Management is responsible for the building (or even purchase) of a solution, testing, deployment and installation.
The most talked about group of people in these process areas is the Change Advisory Board (CAB). This is a group of people who collect to give advice to the Change Manager regarding a particular change. The Release Manager should have a permanent seat on the CAB.
In ITIL v2 the change and release process form part of a natural progression of activities.
- Call received by Service Desk staff
- Incident raised
- Workaround provided
- Problem management analyzes incident
- Root Cause found
- Request for Change raised to rectify the cause
- Change approved
- Release built and tested
- Release deployed and installed.
ITIL version 3 - purchase direct from the publisher and SAVE
ITIL v3 MANUALS
Top ˆ
|