Configuration item (CI)

As IT environments grow more complex and need careful management, the concept of a configuration item (CI) becomes increasingly important. Every configuration item plays a key role in how the system works, linking different components and their characteristics.

Understanding this term helps you see how it can be used to improve the way a company operates. Below we explain what a configuration item is and how it differs from an asset. We also define CI types and attributes and look at how CIs are managed, so you can find your way around this area more easily.

A configuration item (CI) is a component of an IT system: software, hardware, documentation or other IT assets within its scope. A CI describes the functions and behavior of system elements and helps organize IT processes.

Here is an example. In IT service management, the following can be treated as configuration items:

• a server;
• the software installed on it;
• the software license;
• the technical documentation describing how the software works.

When these elements are recorded as CIs, IT teams can see how a given asset will work within the system as a whole.

Note: less visible elements can also be configuration items. These include network and server components and databases, which are often overlooked.

A simple example: take a microservice component in a cloud infrastructure. Each individual function related to that service can be recorded as a configuration item. This helps teams keep a close eye on changes and problems, which in turn supports a higher level of customer service.

Asset vs. configuration item

To understand configuration items better, let's distinguish them from assets. The two concepts are closely related, but they differ significantly in nature and in why they are managed.

Assets are an organization's valuable tangible and intangible items. Most often these are hardware, such as servers or PCs. Software licenses, patents, trademarks and so on are also assets.

The key differences between assets and configuration items:

Here is a simple example of the difference. A software license is an asset, while the version of that software installed on a server is a CI.

Configuration management should not be confused with asset management. Configuration management covers the technical side:

• identification;
• change control;
• configuration item audits.

Asset management is more focused on the financial side: tracking, depreciation and cost planning.

Configuration management activities include:

• Inventory of configuration items.
• Mapping the relationships between them.
• Change and version control.
• Keeping change documentation up to date.
• Audits: assessing the state of configurations.

Done properly, configuration management shows how the behavior of one component affects others. This makes the system as a whole stable and predictable.

Configuration item types and subtypes

There are many types of configuration items, and each has its own subtypes. The main CI classes are:

Hardware configuration items:

• Servers: physical or virtual machines that process data and deliver services over the network.
• Mobile devices: smartphones and tablets that can perform basic computing tasks and connect to networks.
• Network devices: routers, switches and access points that connect the different elements of the system.

Software configuration items:

• Operating systems: Windows, Linux, macOS. They define the environment applications run in.
• Applications: office and graphics software packages, specialized business applications.
• Database management systems: MySQL, Oracle, SQL Server. They store and process data.

Documentation configuration items:

• Technical specifications: documents describing how the system works.
• Policies and procedures: documents governing the use and management of IT resources.
• Installation and configuration guides: step-by-step instructions for administrators and users.

Each CI type gives a different level of insight into and control over system elements. This approach can improve maintenance and customer support. A clear view of relationships lets IT teams allocate resources and support time where they matter most.

Configuration item attributes

ITIL configuration item attributes are characteristics that uniquely identify components and describe their state. They are an essential part of configuration and asset management and make it possible to assess the system fully. Key CI attributes include:

• Identifier: a unique key that unambiguously identifies the CI, such as a serial number, name or UUID.
• Type: the category the configuration item belongs to, such as server, database or application.
• Version: the specific revision of the CI. This matters for software, where each new version brings changes.
• Status: the current state of the configuration item, such as "in operation", "unavailable" or "under repair".
• Owner: an individual or a company branch.

Together, these attributes provide a structured approach to configuration management. They keep information up to date in real time, which is essential for responding quickly to problems and changes.

Configuration item management

Configuration item management is a systematic process of identifying, tracking and controlling all CIs in an organization. Its main goal is to keep the IT infrastructure consistent and stable.

A typical CI management process looks like this:

1. Identify configuration items: list the CIs and describe their purpose and relationships.
2. Create a configuration baseline: define and document the current state of all CIs.
3. Control changes: set up approval processes for changes to CIs to avoid unexpected system behavior.
4. Monitor the state of CIs and check compliance with established standards.
5. Update documentation and track update deadlines.

Take a software update on a server as an example. When a new version arrives, the configuration management team first documents the current state, then approves and tests the update. Finally, it updates the documentation and monitors performance after the release.

Conclusion

ITIL configuration items play a critical role in managing IT systems effectively. They bring together information about different IT assets and show how those assets relate to each other.

A clear understanding of how assets differ from configuration items, of CI types and attributes, and of how to manage them lays a solid foundation for a reliable IT infrastructure. By taking an end-to-end approach to configuration management, organizations can work more efficiently, reduce risk and improve service quality. This builds customer trust and strengthens competitiveness.