RSMUS.comTake a laptop.
The endpoint tool says it checked in this morning from a home network. The configuration item says it is installed and connected to the services that depend on it. The asset record says it is assigned to an employee, covered by a warranty, and due for refresh next year.
Which record is correct?
Potentially all three.
A common ITAM mistake is treating “single source of truth” as though one record should own every fact about a device. That sounds clean, but it ignores why the records exist. The better approach is to decide which source is authoritative for each purpose and each important attribute.
The source record: what was observed
The source record may come from ServiceNow Discovery, an endpoint management platform, a procurement system, or a cloud provider. It captures facts that the source can reliably observe or report, such as a serial number, operating system, IP address, processor, last-seen date, or purchase order.
That information is valuable, but observation is not the same as governance. A tool may know who last signed in to a laptop without knowing who is accountable for returning it. It may know that a server is online without knowing whether the organization has approved it for continued use.
The CI: how the item operates
A configuration item belongs in the CMDB because it is under configuration management. The CI provides the operational view: what the item is, its technical status, how it relates to other CIs, and how it supports services and operational processes.
ServiceNow Discovery compares what it finds with CIs in the CMDB, updates matching CIs, and creates a CI when it does not find a match. The Identification and Reconciliation Engine helps prevent duplicate CIs and controls which data sources are authorized to update specific CI attributes.
The asset record: how the organization manages ownership and lifecycle
The asset record supports the financial, contractual, custodial, and lifecycle view. It can track when an item was ordered, received, stocked, assigned, refreshed, retired, or disposed of, along with information such as cost, warranty, lease, and stockroom.
ServiceNow can link an asset with its corresponding CI and synchronize selected fields between them. Model-category configuration helps determine when an asset should be created from a CI and which asset class applies.
But linked does not mean interchangeable.
Decide truth by attribute, not by table
Instead of asking, “Which system is the source of truth?”, ask five more useful questions:
- What business question does this field answer?
- Which source can establish that fact reliably?
- Who owns the definition and correction process?
- How frequently should it be updated?
- What happens when two sources disagree?
The answer will vary. Technical attributes may come from Discovery or another operational source. Purchase, warranty, contract, stockroom, and disposal information generally belongs with asset and procurement processes. Service relationships and operational impact belong in the CMDB. Custody should be driven by the organization’s fulfillment and asset controls, not assumed from a technical observation.
The maturity path is straightforward.
- Crawl — Define which items require asset records, CIs, or both, and establish a minimum authoritative data set.
- Walk — Configure model categories, asset-CI linkage, field mappings, identification rules, reconciliation rules, and clear data ownership.
- Run — Actively manage duplicates, stale CIs, orphan records, incomplete data, and broken process handoffs.
- Fly — Use the combined asset and configuration context to support stronger automation, security prioritization, investment decisions, and AI-enabled workflows.
Trust does not come from forcing every fact into one record.
It comes from giving each record a clear job, governing how information moves between them, and knowing who is accountable when the data disagrees.
Mike Lavengood
Manager, ServiceNow Practice, RSM. Mike is an Engagement Manager in RSM US LLP’s ServiceNow practice, specializing in IT Asset Management, including Hardware Asset Management, Software Asset Management and Enterprise Asset Management. He helps organizations turn complex asset and process challenges into practical strategies that improve governance, data quality, operational efficiency and business outcomes. Mike brings a blend of technical, functional and program leadership experience to his work. He leads complex ServiceNow implementations, advises clients on ITAM maturity and operating models, and helps project teams connect platform capabilities to measurable business value. His approach emphasizes transparency, strong delivery discipline and solutions that clients can successfully sustain after implementation. Mike holds a bachelor’s degree in computer science and an MBA. His professional credentials include PMP, ServiceNow Certified System Administrator, and ServiceNow certifications in IT Service Management, Hardware Asset Management and Software Asset Management.