Configuration management is the process of tracking all Configuration Items (CI) in a given IT system. It falls within the IT service management categorization under ITIL (Information Technology Infrastructure Library) guidelines. The process can be relatively small in certain instances, sometimes involving just one CI. However, as often as not, the process can involve tracking entire IT departments. Most large organizations choose to delegate an employee as a configuration manager, charging this individual with the responsibility of monitoring and directing the configuration management process.
The primary aspect of configuration management is the maintenance of the CM database (CMDB), the location of all data pertaining to the system. It is used to track the relationships between various CI components and monitor their configuration, among other tasks. The information within the CMDB is utilized in five important manners.
Planning
The configuration management plan will cover the upcoming three to six months in detailed form, and give a rough outline of the next twelve months. It is updated a minimum of twice annually, and includes a review of the objectives, policies, strategies, scope, and relationships between configuration items and various third parties.
Identification
All CI’s are identified and labeled, resulting in a list comprised of every configuration item within the system’s reach. Included within this is the documentation of information pertaining to CI’s, such as hardware and software versions, compatibility, ownership, and documentation, amongst other criteria. CI’s are usually identified with a level of detail that correlates to the needs of the business which owns them.
Control
Since CI’s have to be in the configuration management database prior to being integrated into the system, business operators can be assured that only authorized and known CI’s are operating in their network. No configuration item can be added, replaced, removed or modified without documentation of all actions taken, and forms such as a request for change of a CI. This exclusion of foreign variables makes it easier to locate the source of a problem when or if it occurs.
Monitoring
The status of all CI’s is tracked within the CMDB for the duration of their life within the system. This allows changes to CI’s according to their status, such as “under repair”, “live”, and “on order”, to name a few. Any change in documentation relating to the device’s status is also monitored.
Verification
As with any system, and IT network must undergo various reviews and audits, which can verify the existence of CI’s, and ensure that the records in both the CMDB and parts list are accurate and up-to-date. Also included in this category is the verification of release management and CI documentation before any of the proposed changes go live on the system.
These five duties are fundamental to the efficient ongoing operation of any IT system. As the safeguard of a company’s network, a configuration manager has a considerable amount of responsibility in their hands. This responsibility, however, is absolutely invaluable, as it is difficult, if not impossible, for any business or organization to stay afloat if their IT department is functioning inefficiently. In this regard, proper configuration management is absolutely necessary for sustained profitability and relevance in today’s business world.
Related articles:
