ITIL Service Configuration Management and the CMDB: Configuration Items and Asset Management
When an incident hits, the first questions are always the same: what is affected, what does it depend on and what changed? Service configuration management ensures that accurate and reliable information about the configuration of services, and the configuration items that support them, is available when and where it is needed. The place where this information is usually kept is the configuration management database (CMDB).
Key Terms
| Term | Meaning | Example |
|---|---|---|
| Configuration item (CI) | Any component that needs to be managed to deliver a service | Server, application, database, switch, cloud account, contract |
| Attribute | A property of a CI | Owner, version, location, status, IP address |
| Relationship | A link between CIs | Application X runs on server Y and uses database Z |
| CMDB | A store of CIs, their attributes and relationships | The database behind your ITSM tool’s configuration module |
| Baseline | An agreed snapshot of a configuration | The approved build of a production server |
Why It Matters
- Faster incident diagnosis: see what a failing component supports and who owns it.
- Safer changes: assess impact by following relationships (see Change Enablement).
- Better problem management: link repeated incidents to the same CI.
- Cost and compliance: know what you have, where it is and whether it is supported or licensed.
- Service views: show which components deliver each service.
Service Maps
Relationships can be arranged into a service map that shows how a business service depends on applications, databases, servers, networks and suppliers. When a database server fails, the map shows which services are affected, helping you set priority and tell the right users.
Keeping the CMDB Accurate
An inaccurate CMDB is worse than none, because people trust it and make wrong decisions. Ways to maintain accuracy:
- Discovery tools that scan the network and cloud accounts and update CIs automatically.
- Change integration: every approved change updates the affected CIs.
- Ownership: every CI has an owner responsible for its record.
- Audits: regular comparison of the CMDB with reality, with discrepancies corrected.
- Scope control: track only what matters, at the level of detail you can maintain.
Start Small
Many CMDB projects fail by trying to capture everything. A better approach is to start with a few critical business services, map the CIs they depend on and define only the attributes you will really use. Expand as value is shown. This follows the principle “start where you are” (see ITIL Guiding Principles).
Configuration Management vs IT Asset Management
| Configuration management | IT asset management |
|---|---|
| Focus on relationships and the services CIs support | Focus on the financial and contractual life of assets |
| Question: what depends on what? | Question: what do we own, what does it cost and when does it expire? |
| Data: relationships, configuration, status | Data: purchase date, cost, warranty, licences, depreciation |
IT asset management plans and manages the full lifecycle of assets (procure, deploy, maintain, retire) to control costs, manage risks and support decisions. Software licence compliance is a major part: using more licences than purchased risks penalties, while owning unused ones wastes money. The two practices share data and are often linked in one tool.
Worked Example
At 2 p.m. the order system slows down. The service desk opens the service map for “Online Orders” and sees that it depends on an application cluster, a database server and a payment gateway supplier. Monitoring shows high load on the database server, and the CMDB shows that a patch was applied to it last night under change CHG-2041. The incident team rolls back the patch, performance recovers and the problem team opens a record to investigate the patch. Without the CMDB, the team would have spent an hour finding what depended on what.
Common Mistakes
- Trying to model every cable and screw in the first year.
- Loading data once and never updating it.
- Giving no CI an owner, so no one corrects the data.
- Confusing a CMDB with an asset register.
- Buying a discovery tool without defining which questions the data must answer.
- The CMDB stores configuration items, their attributes and relationships.
- Accurate configuration data speeds up incidents, makes change impact clearer and supports problem management.
- Start with critical services, assign owners, use discovery and link changes to updates.
- Configuration management focuses on relationships; asset management focuses on lifecycle, cost and licences.