CIS - DF CMDB Health, Governance, and Remediation

Aggregated view of CMDB data quality across selected KPIs and metrics.

Completeness, Correctness, and Compliance.

Measures whether expected CI fields are populated.

Measures data quality problems such as duplicate, stale, or orphan CIs.

Measures CI values against expected standards or audit rules.

A field that must be populated for the CI to meet the rule.

A field that improves data quality but may not be strictly mandatory.

A CI is missing required or recommended data.

A CI appears duplicated, stale, orphaned, or otherwise unreliable.

A CI has data that does not match the expected rule or standard.

A CI that has not been updated or validated within the expected timeframe.

A CI missing expected relationships or service context.

More than one CI represents the same real-world item.

Conflicting impact, ownership, relationship, and incident data.

Weak identification rules or multiple sources creating the same CI.

IRE helps prevent duplicates by matching incoming data to existing CIs.

Defines how a CI is uniquely recognized.

Controls which source can update which CI attributes.

A matching attribute that is not reliable enough to uniquely identify a CI.

The trusted source allowed to update specific CI data.

Two or more sources provide different values for the same CI attribute.

A trusted value is overwritten by a less authoritative source.

Keep CMDB data accurate, complete, compliant, current, and usable.

Turning CMDB governance into ongoing processes, reviews, and remediation.

The rules, roles, controls, and processes used to manage CMDB quality.

Ongoing responsibility for maintaining reliable CMDB data.

A review of CMDB data against expected quality or compliance criteria.

Confirming that CI data is accurate and meets expected rules.

Having accountable owners review and confirm data accuracy.

Corrective action taken to fix CMDB data quality issues.

The person or group accountable for fixing an identified CMDB issue.

A work item used to track and complete a data quality fix.

Usually process, ownership, source, or governance failure—not just bad records.

Fixes symptoms without preventing the issue from returning.

Remediate the duplicate and correct the cause of duplicate creation.

Guided tool for reviewing and remediating duplicate CI records.

Wizard used to reconcile duplicate CI records.

A task grouping duplicate CIs that need review and remediation.

A group of CIs suspected to represent the same real-world item.

Choosing which duplicate CI should survive as the authoritative record.

The CI retained after duplicate remediation.

A duplicate CI removed, merged, or retired after remediation.

Preserve relationships, history, and authoritative attributes when possible.

Keeping valid CI relationships attached to the surviving CI.

Improve identification, source control, process controls, and governance rules.

Workspace for viewing, managing, and remediating CMDB data issues.

Area used for governance tools such as Data Manager and de-duplication.

Workspace view for duplicate CI insights and remediation activity.

Dashboard for monitoring CMDB health KPIs and metric results.

Dashboard focused on foundational CMDB data quality and adoption metrics.

Opening metric details to identify affected records requiring action.

A measurable indicator used to track CMDB health or governance progress.

Critical Success Factor.

Key Performance Indicator.

A CSF is the goal; a KPI measures progress toward it.

Direction of quality over time, not just a single score.

The score or condition used to decide whether data passes or fails.

Choosing which KPIs, metrics, or classes are evaluated.

Removing records or classes from evaluation when appropriate and justified.

Defined set of records excluded from specific health calculations.

Hiding quality problems instead of remediating them.

A CI class important enough to monitor closely for CMDB health.

Focus health measurement on important operational CI classes.

Server, database, network device, or application service.

Creates noise and can dilute meaningful health governance.

Important CI quality issues may be missed.

CMDB health measured for a specific CI class.

Health score or issue status for a specific configuration item.

Aggregated health across configured CMDB scope.

Tool for creating, publishing, and managing CMDB governance policies.

A policy that automates or governs CI lifecycle and data operations.

A Data Manager policy not yet published for active use.

A Data Manager policy active for execution or scheduling.

When a Data Manager policy is evaluated or executed.

Criteria that determine which CIs the policy applies to.

The operation performed when CIs meet policy criteria.

Automating consistent CI lifecycle operations such as deletion or retirement.

Makes CMDB governance repeatable, auditable, and less manual.

A controlled action that changes a CI's lifecycle state or existence.

The states a CI moves through from creation to retirement or deletion.

Mark a CI as no longer active while preserving appropriate history.

Move inactive or obsolete CI data out of active operational use.

Deleting can remove history, relationships, and audit context.

Retire preserves context; delete removes the record.

A field representing the operational or lifecycle status of a CI.

Keeping CI state fields aligned with reality.

Field commonly used to indicate whether a CI is operationally active.

Field commonly used to track lifecycle or deployment state.

A CI has lifecycle fields that conflict with its real-world state.

No trusted source, no owner, no validation cycle, or broken integration.

Assign ownership and process controls for manually maintained CIs.

Can become stale or incomplete without ownership and review.

Define owner, source of truth, update process, and validation cadence.

Rules ensuring valid relationship types and directions between CI classes.

A CI relationship that violates expected model or governance rules.

A relationship missing valid context or a valid endpoint.

More than one relationship represents the same dependency or connection.

Quality of CI relationships, including validity, duplication, and compliance.

A recommended relationship pattern between specific CI types.

Governance rule for expected hosting relationships.

Governance rule for expected containment relationships.

The parent-child or dependency direction between related CIs.

Impact analysis and dependency maps can become misleading.

Requires accurate CI relationships to determine affected services.

Operational processes using CI-to-service relationships for better decisions.

Group that defines, reviews, and enforces CMDB rules and priorities.

Owns the configuration management process and governance approach.

Configures, monitors, and maintains CMDB platform capabilities.

Reviews and improves data quality for assigned CMDB scope.

Owns quality expectations and standards for a CI class.

Owns service context and service-related CI accuracy.

Ensures process use of CMDB data supports business outcomes.

Assigning clear ownership for fixing each data quality issue.

CMDB issues remain visible but unresolved.

Regular reviews, metrics, ownership checks, and remediation follow-through.

Identify affected records, assign remediation, fix root cause, and validate results.

Measure, analyze, remediate, prevent recurrence, and monitor trend.

Visibility without action.

Automation without accountability.

Measurement without a clear pass/fail expectation.

Temporary cleanup.

Rules that do not change CMDB behavior.

Better impact analysis, service operations, reporting, compliance, and decision-making.

It only matters if the evaluated scope and metrics are meaningful.

Identify missing fields by class and assign data owners.

Review duplicate sets and investigate identification/source causes.

Confirm ownership, source updates, and lifecycle state accuracy.

Review expected relationships and service context.

Expected values or audit rules are no longer being met consistently.

Accumulated bad data, custom shortcuts, weak integrations, and unmanaged exceptions.

Prefer configured platform capabilities over brittle custom cleanup logic.

Defines ownership, standards, rules, exceptions, and review cadence.

Controlled way to approve and track deviations from CMDB rules.

A common path to hidden CMDB quality erosion.

Who is accountable for this CI data being correct?

Which system should provide this CI attribute?

Which CMDB issues most affect operational outcomes?

Prioritize remediation and monitor improvement over time.

Improve foundational CMDB data quality and adoption.

Automate repeatable CMDB lifecycle governance.

Guided remediation of duplicate CI records.

Focus CMDB health on important CI classes.