Configuration Management Process
1 Introduction 1.1 Purpose The purpose of this document is to set out in detail the [Organization Name] process in the area of configuration management. As such, this document will represent an initial design for the enhancement of existing configuration management processes and will be updated on at least an annual basis thereafter as [Organization Name] and its IT service management needs develop. The overall goal is to define and control the components of services and infrastructure and maintain accurate configuration information on the historical, planned and current state of the services and infrastructure. The achievement of this goal will require the population of a repository of configuration information (the Configuration Management System or CMS) which is verified and kept up to date using an appropriate mix of technical and procedural controls.
1.2 Objectives The objectives of the configuration management process are to: • • • •
Identify, record and control information about configuration items that have value to the organization Create and maintain a configuration management system (CMS) that holds useful information about CIs and their relationships e.g. baselines and snapshots Ensure that the CMS stays up to date in the face of change by working closely with the change management process Provide useful information about the status, attributes and relationships of CIs to other processes such as release and deployment management, change management and capacity management
1.3 Scope The scope of this process is defined according to the following parameters: • • •
Organizational o [List organizations and parts of those organizations covered] Geographical o [List locations from which requests for change will be accepted and managed] Services o [Define the services covered by the process]
Version 1
Page 9 of 26
[Insert date]
