Configuration Item (CI)

Updated at: 24 January 2025

In the modern world, where information technologies prevail, the concept of configuration unit (CU) becomes relevant. This is due to the growing complexity of IT structures and the need for competent management of them. Each configuration unit plays a key role in the functioning of the system, providing the connection between different components and their characteristics.

It is important to understand the meaning of this term to learn how it can be used to optimize the work of companies. Let's consider what a configuration unit is, what are the main differences between it and assets. In this regard, we will define the types and attributes of configuration units, pay attention to their management - this will help the reader to better navigate in this area.

## What is a configuration unit (CU)?

**Configuration unit**

(KE) is a component of an information system: software or hardware, documentation, other IT assets related to this slice. KE describes functionality, behavior of system elements, helping to organize IT processes.

Let's consider an example. So, in the context of IT service management, a configuration unit can be considered to be:

¨NBSP;

server;

software installed on it;

software license;

technical documentation describing software activity.

Being united in a KE, the mentioned elements allow IT specialists to understand how a certain asset will function within the overall holistic system.

Important: Configuration units can also include elements that are not visible enough. These can be networking, server components, databases - they are often overlooked.

A simple example: take the service component of a microservice in a cloud infrastructure. Each individual function associated with said service can be formalized as a configuration unit. This allocation helps teams to be vigilant about changes, issues. This approach contributes to a higher level of customer service.

Asset versus configuration unit

To better understand configuration units, let's distinguish between assets and configuration units. Initially, the two concepts are closely related. However, they differ significantly in their essence, management objectives.

Assets are valuable physical and non-physical elements of an organization. Most often they are equipment - for example, servers or PCs. Software licenses, patents, trademarks, etc. should also be considered as assets.

Let's highlight the key differences between assets and configuration units:

Definition:

An asset is an item with economic value.

A configuration unit is any component of an IT object.

Objective:

Asset accounting aims to monitor, manage the value of assets.

KE management aims to understand, manage relationships and configurations.

Management:

Asset management encompasses the life cycle of assets: procurement, accounting and disposal.

KE management includes modeling, version control, and change management.

Here is a simple example aimed at identifying the differences between the concepts under consideration. Thus, software in the form of a license is an asset. But the version of the same software installed on the server is already a QE.

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

identification;

change control;

auditing of configuration units.

Asset management is more focused on the financial aspect: accounting, depreciation, cost planning.

The following is a list of configuration management activities:

Inventorying configuration units.

Determining the relationships between them.

Controlling changes, versions.

Maintaining up-to-date documentation of changes.

Performing audits: assessing the state of configurations
.

The result of proper configuration management is an understanding of how the behavior of one component affects others. This forms the stability, predictability of the system as a whole.

Types and subtypes of configuration units

There are many types of configuration units - each of them also has its own subtypes. The main classes of configuration units include:

Hardware configuration units:

Servers: physical or virtual - process data, providing services over the Internet.

Mobile devices: smartphones and tablets, capable of performing minimal computing, network connectivity functions.

Network devices: routers, switches, access points
.
They provide connectivity between the various elements of the system.

Program configuration units:

Operating systems: Windows, Linux, macOS - define the application execution environment.

Applications: office, graphics software packages; specialized business solutions.

Database management systems: MySQL, Oracle, SQL Server - provide data storage and processing.

Configuration units of documentation:

Specifications: documents describing system operation.

Policies and Procedures: documents governing the use, management of IT resources.

Installation/Customization Instructions: step-by-step guides for administrators/users.

The types of KEs presented provide different levels of understanding, management of system elements. This approach has the potential to improve maintenance and customer support. A deep understanding of interconnectivity allows IT professionals to optimally allocate resources and time to support them.

Attributes of configuration units

ITIL configuration unit attributes are characteristics that uniquely identify components and describe their states. They are an important element within configuration/asset management, providing the ability to fully evaluate a system. Key attributes of a KE include:

Identifier: a unique key that uniquely identifies a KE - series number, name, UUID, etc.

Type: indicates to which category this configuration unit belongs - server, database, application.

Version: indicates the specific modification of this KE
.
Relevant for software, each new version of which contains improvements.

State: current status of the configuration unit - "in operation"/"unavailable"/"under repair".

Owner: individual/branch of the company.

Each of these attributes provides a structured approach to configuration management. It is a guarantee of real-time information updates, which is crucial for quick response to problems, changes.

Configuration unit management

Configuration Unit Management is a systematic process that involves tracking, identifying, controlling all KEs in an organization. The main goal is to ensure the integrity, stability of the IT infrastructure.

Thus, the KE management algorithm can look as follows:

Identification of configuration units: making a list of KEs with a description of their purpose, interrelationships.

Creating a base configuration (BC): defining and documenting the current state of all KEs
.

Change control.
This involves setting up processes to approve changes made to the KE to avoid unexpected behavior of alcoholic beverages.

Monitoring the state of the KE, checking compliance with established standards.

Updating documentation, due dates for updates.

An example would be the software update process on a server. So, when a new version is received, the configuration management team first documents the current state, then approves and tests the update. The final step is to update the documentation, and monitor performance post-release.

Conclusion

Itil configuration units play a crucial role in the effective management of information systems. They allow you to systematize information about various IT assets, ensuring their interconnection.

A clear understanding of the differences between assets and configuration units, knowledge of the types and attributes of KEs, algorithms for their management create a strong foundation for the successful functioning of IT infrastructure. By approaching configuration management in an integrated manner, organizations can significantly increase efficiency, reduce risks, and improve the quality of services provided. This approach leads to an increase in customer confidence and competitiveness.