AboutGetReadHelp

Some examples

This page is part of a set of pages: "IoCP Small Business Group (Bedrock) Technical Manual"
Turn the page:
Configuration Management
ITIL is supposedly entirely based on Configuration Management, the recording of all objects of interest and their inter-dependencies in some integrated repository that is used and maintained by the other processes. Two Hills have always regarded this concept with a jaundiced eye (having lived through previous magic cures such as relational database, corporate data model, meta-data repository, CASE, object oriented programming, Web Services…). The reality is that the majority of current ITIL implementations have very little Configuration Management at all: just whatever asset information is tracked by their service desk or monitoring tools with next to no processes in place. This does not seem to greatly impact the benefits they derive from the other processes. The general agreement, certainly in NZ but seemingly worldwide, is that Configuration Management is just too hard. 
With this in mind, Two Hills intend to omit Configuration management from the SME model, retaining only Asset Management as a subset of Financial Management. As ITIL is scaled down, it becomes more and more feasible that de-facto configuration management is conducted successfully in the head of the person or small number of persons responsible for IT. Once passed through our scaling and common sense filter (BSF) only Asset Management comes out the other side, a subset of Configuration Management (that some would argue is the only really useful bit even in corporate world)
Change Advisory Board
This is an essential component of ITIL Change Management. The BSF filter reveals that it is still essential in a SME, in fact it is one of the few parts of the process that remains. However, SMEs don’t have enough staff to provide people independent of the processes they are reviewing or managing. So the description of who should be on the CAB changes to be the most senior interested manager (i.e. the CEO or their delegate) and the person responsible for the impacted systems (no accountability without authority)
This page is part of a set of pages: "IoCP Small Business Group (Bedrock) Technical Manual"
Turn the page: