Improving CMDB data quality for Data Foundations

  • Release version: Zurich
  • Updated February 25, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Improving CMDB Data Quality for Data Foundations

    The Remediation actions panel in the CMDB success advisor dashboard for Data Foundations offers targeted actions to improve the quality of your Configuration Management Database (CMDB). By addressing data quality issues, you enhance the accuracy, consistency, and usability of configuration items (CIs), ensuring better alignment with Data Foundations.

    Show full answer Show less

    Key Features

    • Guided Actions: Provides guided remediation steps to improve CMDB data quality.
    • Context-Aware Suggestions: Offers suggestions based on the specific data displayed in the chart.
    • Focus on Meaningful Tasks: Directs attention to significant issues that require immediate action.
    • Actionable Insights: The panel appears only when there are actionable insights available for the selected data.

    Key Outcomes

    By utilizing the Remediation actions panel, you can expect to resolve several common data quality issues, including:

    • CIs with Invalid or Unpopulated Names: Correct names to ensure proper data referencing.
    • CIs Missing Location: Assign locations to enhance incident routing and asset tracking.
    • CIs Missing Managed By Group: Assign ownership for effective incident and service request routing.
    • Stale CIs: Update or remove outdated records to maintain trust in your CMDB.
    • Duplicate CIs: Merge duplicates to prevent workflow errors and split incident histories.

    Specific tips include checking Discovery schedules for stale CIs and reviewing CMDB Identification and Reconciliation (IRE) rules for duplicates. Additionally, consider using CMDB enrichment rules to auto-populate missing location or owner fields from related records.

    The Remediation actions panel available for a chart in the CMDB success advisor dashboard for Data Foundations suggests targeted actions to address Data Foundations data quality issues and improve the overall quality of your Configuration Management Database (CMDB).

    Figure 1. Remediation actions panel
    Example actions in the remediation actions panel shown for stale CIs not updated within the selected time period.

    When remediation actions are available for a chart, the Remediation actions panel appears on the KPI Details page.

    You can perform the actions suggested within the Remediation actions panel to address Data Foundations data quality issues in the CMDB. These actions help improve the accuracy, consistency, and usability of configuration items (CIs), promoting better alignment with Data Foundations.

    The Remediation actions panel:
    • Improves CMDB data quality through guided actions
    • Suggests context-aware actions
    • Supports quick, informed remediation steps
    • Focuses attention on meaningful tasks
    • Appears only when actionable insights are available

    Accessing the Remediation actions panel

    To open the Remediation actions panel, select a segment or count on a chart in the CMDB success advisor dashboard for Data Foundations. The KPI Details page opens. If the remediation actions are available for the selected data, the panel appears on the details page suggesting various remediation actions.

    Available remediation actions

    The Remediation actions panel provides relevant suggestions and actions based on the information in the selected chart. For example, if the chart shows CIs that weren't updated recently, the panel suggests reviewing retirement policies.

    The remediation actions are available for the improvement of the following issues:

    CIs with invalid or unpopulated names
    Identify and correct CIs in your principal classes that lack a valid name. Accurate names are required to correctly reference data to the right configuration item.
    CIs missing location
    Resolve CIs in your principal classes that have no location assigned. Location data supports incident routing, asset tracking, and compliance reporting across your organization.
    CIs missing managed by group
    Assign a managed by group to CIs in your principal classes that are missing ownership. Ownership data is critical for routing incidents, changes, and service requests to the correct team.
    Stale CIs
    Remove or update CIs in your principal classes that have not been updated or discovered for an extended period. Stale records reduce trust in the CMDB and can cause incorrect assignments.
    Duplicate CIs
    Remove or merge duplicate records within your principal classes. Duplicates can cause split incident history and routing errors in workflows.

    Data Foundations specific remediation tips

    • For stale CIs in principal classes: check whether a Discovery schedule is running against the affected network segment or cloud account. Stale data often means a Discovery job is failing or out of scope.
    • For duplicate CIs: review the CMDB Identification and Reconciliation (IRE) rules for the affected CI class. Duplicates often signal that IRE rules need updating.
    • For missing location or owner: consider using a CMDB enrichment rule to auto-populate these fields from related records. For example, derive location from IP subnet.