CMDB

You own ServiceNow. You still don't trust the CI data.

A CMDB is a model of your estate. It is accurate on the day it is loaded and drifts every day after that, because the systems doing the actual work — MDM, HR, endpoint, procurement — keep changing without telling it.

Why CIs go stale

Drift has four ordinary causes

Discovery misses what is off the network

Remote laptops that never touch a corporate subnet do not get scanned, so their CI freezes at its last known state.

People move faster than imports

A transfer changes the cost center in Workday on Monday. The CI still carries the old one until the next load.

Swaps are recorded once

A replacement laptop is issued at the desk. The ticket closes. The CI still points at the returned machine.

Spreadsheets get one-way loaded

A bulk import fixes a hundred records and creates a new snapshot that starts aging immediately.

The bridge

Reconcile beside the CMDB, not on top of it

AssetView reads your CI table like any other source. It matches CIs against the reconciled record, then produces a difference list: CIs whose owner, cost center, location, or status no longer matches what the operating systems of record say.

Read-only by default

Nothing is written to ServiceNow unless you explicitly enable a scoped write-back for named fields.

Difference list, not a merge

You see the CI value, the reconciled value, the source behind it, and the age of each before anything changes.

Attributed write-back

If you do enable it, each update records the source, rule, and timestamp in the CI's own history.

Orphan and duplicate CIs

CIs matching no live asset, and multiple CIs matching one physical machine, are listed separately.

Side by side

What a difference row looks like

FieldCMDB CIReconciledSourceAge of CI value
Assigned toM. OkaforPriya NatarajanWorkday214 days
Cost centerEng — InfraEng — PlatformWorkday214 days
SerialC02FX3QUQ6LRC02FX3QUQ6LRJamfcurrent
LocationAustin — Floor 2Austin — Floor 4Jamf97 days
StatusIn useIn useJamfcurrent

Illustrative row from a modeled fleet. Not customer data.

The reconciled side

What the CI is compared against

Each field in the reconciled record carries the system that supplied it and the rule that settled any disagreement.

LT-04821

MacBook Pro 14", M3 Pro

Active
Owner
Priya Natarajan
Workday
Serial
C02FX3QUQ6LR
Jamf
Location
Austin — Floor 4
Jamf
Endpoint protection
Not reporting since Jun 14
CrowdStrike
Purchase date
2024-02-11
Coupa
Cost center
Eng — Platform vs Eng — Infra
Coupa, Workday

Resolution

Cost center conflict: Workday reflects current team assignment; Coupa reflects the purchasing team at time of order. Precedence rule for this field favors Workday. Coupa's value is kept as history, not discarded.

Next step

Find out how far apart your systems are.

We run a read-only reconciliation across your MDM, HR system, endpoint agent, and procurement records, then walk you through where they disagree and why.

Request a data accuracy assessment

Read-only access. No agent to deploy. Nothing written back to your systems.