What is configuration item

The versions and changes of configuration items form a major part of any configuration audits. A configuration item can not only be at the most atomic level, but also can consist of a more complex assembly of other configuration items. In other words, a configuration item can be a primitive component or an aggregate of other configuration items.

In fact, the level at which a configuration item is considered as primitive or aggregate is often decided by the system in which it is created, maintained and managed. With the help of processes and tools, configuration management looks after the configuration items, especially with regards to change management, status accounting, identification and any audits.

Common configuration types include software, hardware, communications, location and documentation. Configuration items have specific attributes as well as relationships that are often unique for configuration items underneath them in the particular system. Configuration items help in identifying the components of a system. In configuration management it helps in tracking the granular changes and helps in system maintenance as well for any possible error detection.

By: Justin Stoltzfus Contributor, Reviewer. By: Satish Balakrishnan. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. CIs are controlled by the Configuration Management application. A CI can be any piece of equipment or component that is tracked through a device record in Configuration Management. CIs vary widely in complexity, size, and type. For example, any object or process within the Service Desk application is recorded as a CI.

This can include an entire system with all hardware, software, and documentation; a single software application; a software license; or a hardware device. Send Help Center feedback. To open the configured email client on this computer, open an email window. Otherwise, copy the information below to a web mail client, and send this email to ovdoc-ITSM hpe. Most ITSM solutions come with a CMDB, which is essential for correlating CI information with incidents, changes, requests, releases and deployments, plus supporting other practices such as information security and financial and systems audits.

While these solutions usually have myriad fields for each CI, at a bare minimum the ISO standards requires the following fields:. Collecting and recording CI information sounds simple, but the practical application is something else. Unless automated, diligently administered, and appreciated within your organization, chances are good that your staff views the act of recording, tracking, and correlating information on CIs as a laborious and low-value activity.

The discipline required is no small matter, and it takes a significant amount of governance to make this happen. Some organizations choose to delegate the role to the service desk or other roles, but, in my opinion, the practice should be owned by system administrators working hand in hand with other stakeholders involved in the service delivery activities.

Best practice: Automate configuration management and include several stakeholders in its upkeep. Almost all organizations keep CI information in separate repositories and, as a result, getting a common view of this information is extremely challenging. Even though hosting all your applications on the cloud might provide easy visibility, the management of up-to-date information remains a significant hurdle when there are other pressing needs, such as incidents and projects.

Governance helps in getting people to understand the need to constantly check the reliability of your CI data. This governance should include capturing baseline data and comparing with snapshots, which also support easier troubleshooting and implementing and tracking changes. Best practice: Establish CI governance for routine data checks, which trickle into easier troubleshooting and clearer change affects.

In determining the root causes of the Microsoft and New York City incidents, it is no surprise that both incidents could have been avoided if only someone took time to ensure that configurations were well validated and regularly reviewed at all levels.

Though configuration management may sound tedious, it is essential to successful and holistic ITSM. Other ITSM practices such as incident, problem, change, request, release, and deployment management can never be effective if configuration items are not properly recorded and the information shared visibly and accurately to all stakeholders. Understanding the value of CIs and the need to invest in CI management can go a long way in helping service providers meet the needs of customers and other stakeholders in more efficient and effective ways.

The Gartner Magic Quadrant for ITSM is the gold-standard resource helping you understand the strengths of major ITSM software vendors, insights into platform capabilities, integration opportunities, and many other factors to determine which solution best fits your needs.