This process provides the base of your configuration management. It is usually executed first. The main results are
a) a configuration management plan where all relevant information (e.g. process description, CMS Architecture, mandatory attributes, naming conventions…) is described
b) an implementation plan for CIs/CI-Relationships their processes and the CMS within the scope
There is no process flow example in the ITIL Manuals for this CoM subprocess (unlike e.g. for change management) but in my experience the following 7 steps are essential:
- Determine the scope and objectives of Configuration Management
- Define and submit CoM Strategy
- Assign roles and responsibilities
- Elaborate on the five standard Configuration Management Processes (incl.KPIs)
- Design the architecture for Configuration Management System
- Plan interfaces (Interface Standards) with other ITSM-Processes
- Create an implementation plan
For all activities other than the implementation plan you should consider not only current requirements but also possible future extensions of the Configuration Management System. This because your CoM Base should not only be solid and sustainable but also extendible.
Yet another example from accounting: your chief accountant should make sure, that you are not forced to change your accouting system everytime your company decides to sell new products.
I will give some more insights on the 7 steps in a later entry.