Configuration Item vs Asset vs Discovery.

Operation, ownership and population

Configuration Item: operational context in the CMDB

A configuration item is a row in a CMDB class representing an actual infrastructure item or service. The base cmdb_ci class provides shared attributes, while child classes such as Computer, Server and Database add specialized fields.

• CIs hold operational attributes such as name, class, location, support group and lifecycle status.
• Typed relationships connect CIs—for example, an application Runs on a server.
• Incident and change processes can reference CIs for troubleshooting and impact analysis.
• The class hierarchy provides consistent fields while preserving type-specific details.
• CMDB Health, identification and reconciliation help maintain reliable configuration data.

A static inventory list is not the same as a CMDB. The operational value comes from accurate classes, attributes and relationships that explain how a service is assembled.

Asset: financial, contractual and ownership lifecycle

Asset Management tracks company property from planning and procurement through stock, assignment, maintenance and disposal. Asset fields answer ownership questions that do not belong in a purely operational service model.

Some physical hardware needs both records because it has both financial value and operational impact. A consumable may be an asset without becoming a CI. A logical application service may be a CI without representing purchased property.

Discovery: find, classify and update

ServiceNow Discovery finds supported computers, servers, printers, IP-enabled devices and running applications, then updates the CMDB with collected information. Horizontal discovery scans infrastructure and can build direct relationships such as an application running on a computer.

1. A schedule and target range determine where discovery runs.
2. Discovery finds a device and classifies what it is.
3. Credentials and patterns or supported discovery logic collect attributes.
4. The Identification and Reconciliation Engine identifies an existing CI or permits creation of a new one.
5. Authorized source data updates attributes and relationships.

Important distinction: Discovery is not the CMDB and it is not an asset record. It is one supported source that populates and maintains CMDB data. Imports, Service Graph Connectors and other integrations can also supply CI data.

One device can have linked CI and asset records

For a managed laptop, the CI represents the device in operational processes while the asset represents purchase, assignment and disposal. ServiceNow can synchronize selected mapped fields between linked CI and asset records through business rules.

Synchronization depends on logical mapping and records that reference each other. Do not create an asset and CI independently and expect matching serial numbers alone to maintain a permanent link. Review model categories, reference fields and synchronization rules when values drift.

Worked scenario: deploy and support a new server

1. Procurement creates an asset to track vendor, cost, ownership, warranty and receipt.
2. The server is installed and Discovery scans the approved network range.
3. Discovery classifies the device and uses identification rules to find or create its server CI.
4. The CI is linked to the asset so mapped lifecycle and assignment information can remain coordinated.
5. Discovery records supported relationships, such as applications running on the server.
6. Incident and change teams select the CI to understand support ownership and potential service impact.
7. At retirement, asset disposal and CI operational retirement are coordinated without treating them as the same lifecycle record.

This separation lets Finance manage property while Operations manages service reliability, with the link preventing the two views from becoming disconnected.

Troubleshoot duplicates, stale CIs and broken links

1. Confirm the class: a device placed in the wrong class may use different identification rules.
2. Review identifiers: verify serial number, correlation identifiers and other class-specific identification entries.
3. Trace the source: inspect Discovery results, imports, connectors and manual updates that touched the record.
4. Use IRE: ensure integrations send data through the Identification and Reconciliation Engine instead of inserting uncontrolled duplicates.
5. Check reconciliation: confirm the source is authorized to update the affected attributes.
6. Inspect Discovery: schedule, target range, credentials, classification, pattern and error logs.
7. Inspect the CI–asset link: both references, model category and logical field mappings must be correct for synchronization.
8. Handle stale records deliberately: verify discovery coverage and lifecycle rules before deleting or retiring a CI.

Do not merge by appearance: two similar names do not prove records are duplicates. Compare class, identifiers, source history and relationships before remediation.

ServiceNow CSA practice checks

Frequently asked questions

Official ServiceNow references

Validate implementation against current ServiceNow documentation for the CMDB glossary, CMDB record types, Asset Management, asset and CI management and Discovery. Features vary by release, licensing and instance configuration.