Configuration Management Activities

Notice how management and planning are the central activities. Good, sound Service Asset and Configuration Management requires thorough planning for the operation of the process to work.

Planning:
* Defining the strategy, policy, scope, objectives, processes and procedures for Service Asset and Configuration Management
* Roles and responsibilities of involved staff and stakeholders
* Location of storage areas and libraries used to hold hardware, software and documentation
* CMDB Design
* CI naming conventions
* Housekeeping including license management and archiving of CIs.

Identification:
The selection, identification, labelling and registration of CIs. It is the activity that determines what CIs will be recorded, what their attributes are, and what relationships exist with other CIs. Identification can take place for:
* Hardware and Software – include OS
* Business systems – custom built
* Packages – off the shelf
* Physical databases
* Feeds between databases and links
* Configuration baselines
* Software releases
* Documentation.

Control:
Where the CMDB is utilized to store or modify configuration data. Effective control ensures that only authorized and identifiable CIs are recorded from receipt to disposal in order to protect the integrity of the CMDB. Control occurs anytime the CMDB is altered, including:
* Registration of all new CIs and versions
* Update of CI records and licence control
* Updates in connection with RFCs and Change Management
* Update the CMDB after periodic checking of physical items.

Status Accounting:
The reporting of all current and historical data concerned with each CI throughout its lifecycle. Provides information on:
* Configuration baselines
* Latest software item versions
* The person responsible for status change
* CI change/incident/problem history.

Verification and Audit:
Reviews and audits verify the existence of CIs, checking that they are correctly recorded in the CMDB and that there is conformity between the documented baselines and the actual environment to which they refer.
Configuration Audits should occur at the following times:
* Before and after major changes to the IT infrastructure
* Following recovery from disaster
* In response to the detection of an unauthorized CI
* At regular intervals.

Recommended For You

Leave a Reply