Skip to content
Video · 2:45 · or five short clips

The AI is ready. Your data isn’t.

Your CMDB health dashboard says 87%. When we measured that same instance properly, the real score was 34 out of 100. Nobody lied — the staleness threshold had been relaxed to 360 days and no compliance rules existed. The dashboard was grading its own homework.

If you have licensed Now Assist, AI Agents or ITOM and they are not in production yet, the data underneath them is the first thing to check.

Datum CMDB · ServiceNow Store · Read-only · Zero CMDB writes

Fix the datum first2:45
Short on time

The same story in five clips, each under 40 seconds.

Start with the one closest to your problem, or share one with the person who owns the CMDB.

Clip 1 · 0:36

Your dashboard is grading its own homework

Why a CMDB dashboard can read 87% when the instance measures 34 out of 100.

Clip 2 · 0:39

Why your AI isn’t in production

Now Assist, AI Agents and ITOM licensed, none of it live. The model isn’t the problem.

Clip 3 · 0:35

What Datum CMDB checks in 30 minutes

Read-only, zero writes, six dimensions, 40+ system tables, evidence behind every finding.

Clip 4 · 0:27

Where bad CMDB data comes from

Integrations that skip reconciliation, CIs with no owner, thresholds tuned to look good.

Clip 5 · 0:28

How to keep it clean

The rules a remediation should leave behind, and why you keep measuring.

87%
What the dashboard said
34/100
Actual operational health
462K
of 577K CIs with no owner
~28K
Duplicates from 11 integrations
~30 min
To measure it properly
Two editions on the ServiceNow Store

Free tells you how bad it is and where. Pro tells you what to do about it.

Datum CMDB · Free

How bad is it, and where

  • A 0–100 CMDB health score with a breakdown across six dimensions
  • Findings with severity and confidence, plus an executive summary
  • What your CMDB dashboards say versus what the data shows
  • Read-only. Only aggregate structural metadata leaves the instance — no CI contents, no personal data
Datum CMDB · Pro

Now what

  • Findings grouped into root causes, each with business impact and a recommended approach — five things that are actually wrong instead of forty findings
  • Evidence trails down to the specific CIs, classes, scripts and integrations affected
  • A phased remediation campaign with a business case and gate criteria
  • Actions created as native ServiceNow tasks you can assign, track and report on
  • Scheduled polling and a dedicated analysis environment for your organization
Fix the datum first

Four rules the remediation leaves behind.

01

Reconcile every integration

Every integration writes through the Identification and Reconciliation Engine. No side doors, no duplicates.

02

Owner at creation

Every configuration item needs an accountable owner the moment it is created, not after an audit finds it.

03

Honest thresholds

Health thresholds are locked to real standards and backed by compliance rules, so the dashboard tells the truth.

CS

CSDM is the contract

Between the platform team and everyone who feeds the CMDB.

RO

Read-only diagnostic

Datum CMDB connects read-only and makes zero writes to your CMDB.

EV

Evidence per finding

Labeled fact or inference, with an evidence chain and a confidence score.

40+

System tables

It sees why the data went bad, as well as what’s bad now.

Your turn

What does your dashboard say? What’s the real number?

The gap between those two answers is where stalled AI and ITOM projects live. Datum CMDB measures it in about thirty minutes — read-only, zero writes — complimentary for qualified organizations.

Figures are from a representative enterprise assessment of 577,000 CIs. Your results will differ. ServiceNow, Now Assist and CSDM are trademarks of ServiceNow, Inc.