- Configuration Management + Planning
- Configuration Identification
- Configuration Control
- Configuration Verification + Audit
- Configuration Status Accounting
Management + Planning
Planning and defining the purpose, scope, objectives, policies and procedures, and the organisational and technical context, for Configuration Management.
Identification
Selecting and identifying the configuration structures for CIs, including attributes, their allowed or mandatory interrelationships etc. It also includes allocating identifiers and version numbers for CIs, labelling each item, and how the processes of managing them are implemented for specific CI types.
Control
Ensuring that only authorised and identifiable CIs are accepted and recorded, from receipt to disposal. It ensures that no CI is added, modified, replaced or removed without appropriate controlling documentation, e.g. an approved Change request, and an updated specification. This means that formal, compliant change control is applied to every CI ! (Describes INSERT, UPDATE, DELETE for CIs).
Status Accounting
Includes all reporting on Cis. Most important the impact analyis but also the reporting of all current and historical data concerned with each CI throughout its life cycle. This enables Changes to CIs and their records to be traceable, e.g. tracking the status of a CI as it changes from one state to another for instance ‘under development’, ‘being tested’, ‘live’, or ‘withdrawn’. (Describes SELECT on CIs).
Verification and Audit
Guarantee correctness of CIs. A series of reviews and audits to check that they are correctly recorded in the Configuration Management System. For physical Cis this is normaly done via a comparison of the content of the CMS with what has been discovered with the discovery tool and discrepancies are listed. (Describes how QA is done for CI).
You can find more details including process flow examples on other articles in our blog. Have a look on our all entries Blog Page.
Tags: Configuration Mangement, Overview, Process