What Are Configuration Items (CIs) in ServiceNow?
Table of Contents
Recommended Learning Path
What Are Configuration Items (CIs) in ServiceNow?
Understanding Configuration Item’s concept in ServiceNow
Introduction
When an IT team investigates an application outage, it may need information about the application, server, database, network device, or other components involved in delivering that service.
In ServiceNow, many of these managed components can be represented as Configuration Items, commonly called CIs.
Understanding Configuration Items is one of the foundations of working with the ServiceNow CMDB because the CMDB is built around CI records, their attributes, and their relationships.
📈 New to Data Analytics? Follow Our Step-by-Step How to Become a ServiceNow Specialist
Quick Answer: What Is a Configuration Item in ServiceNow?
A Configuration Item (CI) is a component that an organization manages because it contributes to the delivery or operation of a service.
A CI might represent:
- a server,
- an application,
- a database,
- a router,
- a network switch,
- a virtual machine,
- a cloud resource,
- or a business/application service.
ServiceNow stores CI information in the CMDB and organizes different CIs into classes based on what they represent.
A useful beginner formula is:
CI = Managed Component + Attributes + Relationships
What Are Examples of Configuration Items?
Consider an online banking application.
The service might depend on several components:
Banking Application
↓
Application Server
↓
Database Server
↓
Virtual Machine
↓
Network Infrastructure
Each important component can be represented by its own CI.
Some common categories include:
CI Category | Examples |
Hardware | Server, computer, network device |
Software/Application | Application server, software application |
Network | Router, switch |
Infrastructure | Virtual machine, storage component |
Service | Application service, business-related service |
Organizations decide which components need configuration management based on their operational requirements.
What Information Does a CI Contain?
A CI record contains attributes that describe the component.
For example, a server CI might contain:
- Name
- Class
- Serial number
- IP information
- Operating system
- Operational status
- Location
- Support group
- Owner
- Manufacturer
- Model
The exact attributes vary according to the CI class.
A network device needs different information from a software application, which is why ServiceNow uses a structured class hierarchy rather than storing every type of CI in exactly the same format.
What Are CI Classes in ServiceNow?
A CI class groups Configuration Items that share similar characteristics.
At the base of the hierarchy is the Configuration Item table.
More specialized classes extend from broader parent classes.
A simplified example looks like:
Configuration Item
↓
Hardware
↓
Computer
↓
Server
↓
Windows Server
The important idea is inheritance.
A Windows Server can inherit common attributes from Server, Computer, Hardware, and the main Configuration Item class while also having attributes specific to Windows servers.
This structure helps ServiceNow represent many different technologies without treating every CI as the same type of object.
How Do CI Relationships Work?
CIs become more valuable when ServiceNow also knows how they are connected.
For example:
Customer Portal → Runs on → Application Server
Application Server → Connects to → Database
Database → Runs on → Linux Server
These are CI relationships.
Relationships can describe dependencies such as:
- Runs on / Runs
- Depends on / Used by
- Hosted on
- Connects to
- Contains
The exact relationship types depend on the ServiceNow configuration and data model.
Relationships help teams move from asking:
“Which server failed?”
to asking:
“Which applications and services could be affected if this server fails?”
FLM CI Learning Framework: C-A-R-I
Beginners can remember Configuration Items using four questions:
C — Class: What type of component is this?
A — Attributes: What information describes it?
R — Relationships: What other CIs are connected to it?
I — Identification: How does ServiceNow know whether this is an existing or new CI?
This C-A-R-I framework helps connect the main CI concepts without memorizing every CMDB table immediately.
How Are Configuration Items Created?
CIs can enter the CMDB through several mechanisms depending on the organization’s ServiceNow architecture.
Examples include:
- ServiceNow Discovery
- Service Graph Connectors
- Integrations
- Import processes
- Service Mapping
- Controlled manual creation
For a small lab environment, a learner may create a CI manually.
In an enterprise environment with thousands of changing infrastructure components, automated discovery and integration mechanisms become much more important.
How Does ServiceNow Identify a CI?
🎯 Preparing forServiceNow Interviews? Follow Our Step-by-Step ServiceNow Interview Guide →
Imagine a discovery tool reports a server called SERVER-01.
Before creating another record, ServiceNow needs to determine whether the server already exists in the CMDB.
This is where CI identification becomes important.
ServiceNow’s Identification and Reconciliation Engine (IRE) uses identification rules to compare incoming CI information with existing CMDB records.
At a beginner level, think of the process as:
Incoming CI data → Check identification rules → Find existing CI or create appropriate new CI
Reconciliation controls can also help determine which data sources are permitted or preferred for updating particular CI information.
This is important when multiple systems supply information about the same infrastructure.
How Are CIs Used in ITSM?
Configuration Items are not useful only to CMDB administrators.
They can provide context to several ITSM processes.
Incident Management
Suppose employees cannot access an internal application.
An incident can be associated with the affected CI.
Instead of recording only:
“Application unavailable”
the support team can identify the specific application or supporting component involved.
Correct CI association can also help teams understand dependencies and potential impact.
Change Management
Suppose an administrator plans to upgrade a production server.
If the CI has accurate relationships, teams can investigate which applications or services depend on that server before making the change.
Problem Management
When recurring incidents involve the same CI or related components, CI information can provide useful context during root-cause investigation.
A CI does not automatically solve the incident or problem. Its value comes from providing accurate operational context.
Configuration Item vs Asset
A common beginner mistake is assuming that an asset and a CI are always the same thing.
They serve different management purposes.
Configuration Item | Asset |
Operational focus | Financial/lifecycle focus |
Stored for configuration management | Managed through asset processes |
Tracks configuration and dependencies | Tracks ownership, cost, inventory and lifecycle |
Supports service operations | Supports asset management |
A laptop can potentially be both.
Its asset record may track procurement and financial information.
Its CI record may track its operational configuration and ServiceNow relationships.
An item can therefore qualify as both an asset and a CI when both financial tracking and operational support are needed.
What Does the CI Lifecycle Look Like?
A simplified CI lifecycle might look like:
Identify → Create → Maintain → Relate → Monitor → Update → Retire
Identify
Determine what component should be managed.
Create
Add or discover the CI in the appropriate class.
Maintain
Keep important attributes accurate.
Relate
Connect it to relevant infrastructure and services.
Monitor and update
Update the CI as its configuration changes.
Retire
When the underlying component is no longer operational, its CI should be handled according to the organization’s configuration-management policies.
Good CI management is therefore an ongoing process rather than a one-time data-entry task.
Common CI Management Mistakes
Creating everything as a CI
Not every item in an organization needs configuration management.
Choosing the wrong CI class
Placing a server in an overly generic or incorrect class can make reporting and automation less useful.
Ignoring CI relationships
A database with perfect attributes but no meaningful service relationships provides limited dependency context.
Creating duplicate CIs
Duplicate records can make incidents, changes, and reporting unreliable.
Updating CIs from uncontrolled sources
When many systems write different values into the same CI fields, data quality can become difficult to manage.
Treating CI data as permanent
Technology environments change. CI attributes and relationships need appropriate maintenance throughout their lifecycle.
Beginner Roadmap for Learning CIs
A practical sequence is:
- Tables and Records
Understand how ServiceNow stores data. - CMDB Fundamentals
Learn what the Configuration Management Database represents. - Configuration Items
Understand CIs, attributes, and classes. - CI Relationships
Practice connecting infrastructure components. - Incident and Change Management
Learn how CIs support ITSM processes. - Discovery
Understand automated CI identification and population. - IRE and Data Quality
Learn how duplicate and conflicting CI data is controlled.
After this foundation, learners can explore CSDM, Service Mapping, CMDB Health, and advanced Configuration Management.
Frequently Asked Questions
What does CI mean in ServiceNow?
CI stands for Configuration Item.
Where are Configuration Items stored?
Configuration Items are maintained within the ServiceNow CMDB.
What is the main Configuration Item table?
The core Configuration Item table is commonly represented as cmdb_ci, with specialized CI classes extending the hierarchy.
What are CI attributes?
Attributes are fields that describe a CI, such as name, class, operating status, location, or technical characteristics.
What is a CI relationship?
A CI relationship describes how one Configuration Item relates to another—for example, an application running on a server.
Can ServiceNow automatically discover CIs?
Yes. Depending on the organization’s licensed capabilities and configuration, ServiceNow Discovery and other data sources can identify and populate CI information.
Is every asset a CI?
Not necessarily. Assets and CIs serve different management purposes, although one item can be represented as both.
Why are duplicate CIs a problem?
Duplicate CIs can make it difficult to know which record contains the correct information and can reduce the reliability of incident, change, reporting, and dependency data.
Why do CI relationships matter?
They help teams understand dependencies between infrastructure components and the services they support.
What should I learn after Configuration Items?
Useful next topics include ServiceNow CMDB, Discovery, IRE, CSDM, Service Mapping, Incident Management, and Change Management.
Conclusion
Configuration Items in ServiceNow represent the components organizations need to understand and manage as part of their operational environment.
For beginners, four concepts matter most:
Class → Attributes → Relationships → Identification
The class tells ServiceNow what kind of component the CI represents. Attributes describe it. Relationships connect it to other components, and identification helps determine whether incoming information belongs to an existing or new CI.
Once these fundamentals are clear, broader CMDB concepts such as Discovery, IRE, Service Mapping, and Configuration Management become much easier to understand.
Learners building broader platform skills can explore the ServiceNow Course in Telugu while practicing ServiceNow tables, ITSM processes, CMDB concepts, Configuration Items, and automation.