Configuration items are the individual components, assets, and relationships tracked within a configuration management system. Common examples include hardware devices (servers, laptops, routers), software applications, databases, network infrastructure, virtual machines, services, and documentation. Essentially, any element that supports the delivery of an IT service and needs to be tracked, managed, or related to other components can be a configuration item.
The scope of what qualifies as a configuration item varies depending on your organisation’s size, industry, and management goals. In practice, organisations define configuration items based on what they need to control, change, or report on. The sections below unpack the key questions around configuration items, from how they are categorised to what data they hold.
What types of assets count as configuration items?
A configuration item is any component that contributes to an IT service and requires management throughout its lifecycle. The most common types fall into five broad categories: hardware, software, network components, services, and documentation. Each type plays a distinct role in how infrastructure is tracked and maintained.
Hardware configuration items
Physical devices are among the most straightforward configuration items. These include servers, desktop computers, laptops, printers, storage devices, and mobile devices. Each piece of hardware is recorded individually so that its location, ownership, status, and relationships to other components can be tracked over time.
Software and service configuration items
Software configuration items include operating systems, licensed applications, middleware, databases, and cloud services. Beyond individual applications, entire IT services can be registered as configuration items, capturing the combination of hardware, software, and processes that deliver a specific business function. Virtual machines, containers, and API integrations increasingly fall into this category as infrastructure becomes more digital.
How are configuration items used in a CMDB?
A Configuration Management Database (CMDB) stores all configuration item records and, crucially, maps the relationships between them. This relational view allows IT teams to understand how components depend on one another, assess the impact of a change or failure, and support processes like incident management, problem management, and change control.
When an incident is raised, the CMDB allows support teams to quickly identify which configuration items are affected and which upstream or downstream services might be disrupted. During planned changes, teams query the CMDB to model the potential blast radius before making modifications. This reduces unplanned outages and supports more confident decision-making.
The CMDB also underpins compliance and audit processes. Because every configuration item has an owner, a status, and a history of changes, organisations can demonstrate control over their infrastructure to auditors and regulators. Without a well-maintained CMDB, this visibility is difficult to achieve at scale.
What’s the difference between a configuration item and an asset?
An asset is anything that has financial value to an organisation, while a configuration item is anything that needs to be managed because it supports an IT service. The two concepts overlap significantly but are not identical. A laptop is both an asset (it has purchase value) and a configuration item (it runs services and connects to the network). A software licence may be an asset but not necessarily a configuration item if it is not actively managed within the service infrastructure.
The key distinction lies in purpose. Asset management focuses on financial tracking, procurement, depreciation, and disposal. Configuration management focuses on operational relationships, service dependencies, and change impact. Many organisations run both processes in parallel, with the CMDB and asset register sharing data but serving different stakeholders and decisions.
In practical terms, not every asset becomes a configuration item. A piece of furniture in the office has financial value and may appear in an asset register, but it does not support IT services and would not typically be tracked in a CMDB. Conversely, some configuration items, such as virtual network segments or documentation files, may have no direct financial value but are critical to service management.
How do you decide what to include as a configuration item?
The decision comes down to whether managing the item improves your ability to deliver, change, or restore services. A useful test is to ask: if this item failed or changed unexpectedly, would it affect a service or make an incident harder to resolve? If yes, it belongs in your CMDB as a configuration item.
Organisations commonly use three criteria to guide inclusion decisions:
- Service impact: Does the item directly support a business or IT service?
- Change frequency: Is the item subject to changes that could affect other components?
- Relationship value: Does knowing its connections to other items improve decision-making?
Starting with a narrow, well-maintained scope is almost always more effective than attempting to capture everything at once. Over-populating a CMDB with low-value configuration items creates noise that undermines trust in the data. A phased approach, beginning with critical infrastructure and expanding gradually, produces more reliable and actionable records.
What attributes does a configuration item record contain?
A configuration item record contains the structured data needed to identify, manage, and relate that item to others. Core attributes typically include a unique identifier, a name or description, the item type or category, its current status (active, retired, in maintenance), the owner or responsible team, and the date it was added or last modified.
Beyond these basics, most organisations add attributes specific to the item type. A server record might include its operating system version, physical location, IP address, and hardware specifications. A software application record might include its version number, licence details, and the business process it supports. A service record might list its agreed availability targets and the configuration items it depends on.
Relationship attributes are equally important. Each configuration item record should document how it connects to other items, whether as a dependency, a component, a parent, or a child. These relationships are what transform a list of records into a genuine map of your infrastructure, enabling the impact analysis and change planning that make a CMDB genuinely useful.
How iONE360 helps with product configuration
While CMDB configuration items sit firmly in the IT domain, the concept of managing complex, interrelated configurations at scale has a direct parallel in the world of physical products. For manufacturers and retailers of customisable furniture and home furnishings, the challenge is equally real: how do you manage thousands of product variants, business rules, and visual outputs without losing control or consistency?
That is exactly where we come in. Our 3D product configurator is built to handle the full complexity of configurable products, from fabric and finish combinations to structural variants and pricing logic. Here is what we make possible:
- Unlimited configuration options managed within a single platform, including complex business rules and pricing structures
- ERP-aligned logic so that product configurations speak the same language as your existing enterprise systems
- Automated high-quality visuals generated for every configuration without manual effort per variant
- Seamless integration with PIM, ERP, CMS, and webshop environments
- Guided selling experiences that lead customers through even the most complex product choices step by step
The result is fewer errors, higher conversion rates, reduced returns, and consistent brand presentation across every sales channel. If you are ready to bring your configurable product range under control and present it with confidence, get in touch with us to see what iONE360 can do for your business.