When implementing a configuration management system you usually start with the following steps:
- What is expected? submitted requirements catalogue has to be available
- Establish roles and responsibles
- Define measurement system (KPIs to control Critical Success Factors)
- Strong and stable CMS Architecture and Design (including Metamodel)
- Create standard configuration management processes (samples see here: www.dis.ch/blog/index)
- Determine CI-/ CI-Relation scope needed to meet customer requirements
- Define degree of control (accuracy) of Configuration data required
- and then you proceed with typical implementation activities such as evaluation, education, implementation, testing…
Key for your success are the following four factors:
- Configuration Control needs to be integrated into the Change Mangaement Process (this also is true for the tool in use).
- Identify Quick wins. e.g. consolidate data from different sources not yet complying with configuration Management processes and provide reports. Don’t forget to clearly state then level of accuracy of hits reports.
- Automate, whenever and whatever possible. e.g. generate predefined change requests / service requests for CI/CI-Relation changes. And dont forget another ITIL suggestion: Faciliation before Automation.
- Define requirements for your Configuration Management before buying and assure integration with existing Service Management Environment.
Tags: Best practices