Free Tool · CMDB

CMDB Health Scorecard

Thirteen questions across the four mechanisms that actually degrade a CMDB. Scored in your browser, nothing transmitted, no email required.

CMDB accuracy does not fail all at once. It decays through four standing process failures, and a cleanup project addresses none of them. This scorecard tests whether those four mechanisms are under control — not whether your data is clean today, which is a snapshot and tells you very little about next quarter.

Nothing you enter leaves your browser. There is no form submission, no analytics on your answers, and no email required to see the result. These questions are about the state of your platform, so that matters.

Class model

An extended class model with no maintenance behind it makes every query untrustworthy.

  1. Every CI class in active use has a named owner who would notice if it stopped being populated.

  2. Classes with no population source have been disabled or removed rather than left half-filled.

  3. The class model has been reviewed against actual use in the last twelve months.

Discovery coverage

An empty result and an unreachable target look identical downstream. Gaps have to be visible as gaps.

  1. You can state, with a number, what proportion of your estate discovery actually reaches.

  2. Credential failures are reported and triaged rather than silently retried.

  3. Cloud accounts are enumerated against an independent registry, not only discovered.

  4. Network segments discovery cannot reach are documented as known gaps.

Data authority

When authority is not declared explicitly, it is decided implicitly by whichever job ran last.

  1. For each key CI attribute, one source is formally declared authoritative.

  2. Identification and Reconciliation rules reflect that declaration in configuration, not just in a document.

  3. Import sets and manual edits cannot silently overwrite discovered data.

Retirement

Because retirement is invisible, the CMDB grows monotonically and every count drifts from reality.

  1. Decommissioning has a named owner and a defined trigger.

  2. CIs reach a Retired or Absent state within a defined window after the asset is switched off.

  3. Counts derived from the CMDB are periodically reconciled against an independent source.

0 of 13 answered

If the score was uncomfortable

We will tell you which findings are worth money.

Send us the result. We will say which gaps we would fix first, which we would leave alone, and whether you need outside help at all — including when you do not.

contact@tessivant.com