CMDB Terminology

A Configuration Management Database, or CMDB, provides a centralized system of record for IT assets and services, along with the relationships between them. By capturing how systems connect and depend on one another, the CMDB enables better incident response, change management, impact analysis, and overall service visibility.

To work effectively with the CMDB, it’s important to understand several foundational terms that define how configuration data is structured and managed within the platform.

Key Service Catalog Terms

Configuration Item (CI)

A Configuration Item, commonly referred to as a CI, is the fundamental record stored in the CMDB.

A CI represents any component that needs to be managed in order to deliver an IT service. This can include physical hardware, virtual infrastructure, applications, databases, or even business services.

Examples of common CIs include:

• Servers
• Applications
• Databases
• Network devices
• Business services

Each CI contains attributes that describe the item, such as its name, owner, environment, lifecycle status, and other operational details.

CI Classes

CIs are organized into classes, which define the type of configuration item being tracked.

Classes allow the CMDB to group similar items and define the attributes that apply to them. For example, a server CI may include attributes like CPU count, operating system, and memory, while an application CI may include version information or vendor details.

ServiceNow provides a hierarchical class structure, where more specific CI types inherit attributes from broader parent classes. This structure helps maintain consistency while allowing flexibility for different types of infrastructure and services.

Relationships

One of the most powerful features of the CMDB is the ability to define relationships between configuration items.

Relationships describe how CIs interact or depend on one another. For example:

• An application runs on a server
• A database supports an application
• A business service depends on multiple applications

By mapping these dependencies, organizations can visualize service architecture and understand how different components work together.

These relationships are essential for tasks like impact analysis, where teams need to determine which systems might be affected by an incident or change.

CI Attributes

Each CI includes a set of attributes, which are the individual data fields that describe the configuration item.

Attributes provide detailed information about the CI, such as:

• Name
• Owner or support group
• Environment
• Version or model
• Operational status

The attributes associated with a CI are determined by its class, ensuring that each type of configuration item captures the information most relevant to it.

Maintaining accurate attributes is critical to ensuring the CMDB remains reliable and useful for operational processes.

CI Lifecycle

Configuration items move through a lifecycle as they are introduced, used, and eventually retired.

Typical lifecycle stages include:

• Planned
• In development
• In production
• Retired

Tracking lifecycle states helps teams understand the current status of infrastructure and services, and ensures outdated or decommissioned assets are clearly identified.

Lifecycle management also plays an important role in governance, auditing, and change management processes.

Service Mapping

Service mapping refers to the process of identifying and documenting the infrastructure and applications that support a business service.

By mapping these dependencies into the CMDB, organizations gain visibility into how services are delivered and which components support them.

Service mapping allows teams to quickly determine the potential impact of outages, incidents, or planned changes. It also improves collaboration across teams responsible for different parts of the technology stack.

Data Quality

The value of a CMDB depends heavily on data quality.

Incomplete, outdated, or inaccurate configuration data can reduce trust in the CMDB and limit its usefulness. For this reason, organizations often implement governance processes to ensure configuration data is properly maintained.

This may include clearly defined ownership for CI records, automated discovery tools to populate data, and regular audits to validate accuracy.

Maintaining high data quality ensures the CMDB remains a reliable foundation for IT operations and service management.

Lauren Filippo is a ServiceNow professional specializing in IT and HRSD, where she translates complex business needs into clearly defined, scalable solutions. She is passionate about driving efficiency through strong organization, documentation, and a deep understanding of the end-user experience. Outside of work, she enjoys coding video games in Python.