The rules displayed below were developed under CEF and are not mandatory under DEP. They can serve as optional guidance for configuration management under DEP. |
Configuration Management is the Process responsible for maintaining information about Configuration Items required to deliver an IT Service, including their Relationships.
The goals of Configuration Management are to:
This process covers the organisation, management and protection of components of the IT infrastructure: the configuration items (software and documentation) which are delivering a service to the users.
The following artefacts are covered for all the CEF Building Blocks:
Planning
The Configuration Management Plan should cover in detail the next 3 to 6 months and should give an overview of the next 6 to 12 months. This plan should be reviewed at least twice a year.
Identification
The Configuration Identification includes the selection, identification labelling and recording of all CIs. CIs should be recorded at a level of detail justified by the business need.
Control
The Configuration Control ensures that only authorised and identifiable CIs are recorded from receipt to disposal. It ensures that no CI is added, modified, replaced or removed in the CMDB without appropriate controlling documentation.
Status Accounting
The Configuration Status Accounting concerns the reporting of all data about the history of each CI. It enables to track the changes in the state of a CI.
Verification and Audit
The Configuration Verification and Audit comprises a series of reviews that verify the physical existence of CIs and their correct recording in the CMDB.
They have to be performed before and/or after a major release and at random and regular intervals.
Harmonized and efficient Configuration Management brings benefits to the process, allowing to:
To be completed.