---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/servicenow-platform

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Improve foundational data quality

# Improving CMDB data quality for Data Foundations {#ariaid-title1}

Release version: Australia  
Updated September 30, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 helps ServiceNow customers improve the quality of their Configuration Management Database (CMDB).
It provides targeted, context-aware suggestions and guided actions to address common data quality issues, enhancing the accuracy, consistency, and usability of configuration items (CIs) aligned with Data Foundations principles.
Show full answer Show less  

## Key Features

* **Remediation actions panel:** Appears on the KPI Details page when actionable insights are available, enabling quick and informed remediation.
* **Ask Otto action:** Allows starting an agent conversation immediately from KPI cards to expedite issue resolution.
* **Targeted suggestions:** Actions are tailored based on the selected chart data, such as reviewing retirement policies for outdated CIs.
* **Issue-specific remediation:** Addresses problems like invalid CI names, missing location, missing managed by group, stale data, and duplicate CIs.
* **Role-based controls:** Some actions, like turning on sync settings, are restricted to users with CMDB admin roles.
* **Integration with tools:** Links to CI Class Manager and CI lists enable efficient remediation steps, such as adding missing fields or reviewing affected CIs.

## Practical Remediation Guidance

* **Invalid or missing CI names:** Identify and correct CIs lacking valid names to ensure proper data referencing.
* **Missing location data:** Assign locations to support incident routing, asset tracking, and compliance reporting.
* **Missing managed by group:** Assign ownership groups to ensure correct routing of incidents, changes, and service requests.
* **Stale CIs:** Remove or update CIs not updated or discovered recently to maintain CMDB trustworthiness.
* **Duplicate CIs:** Remove or merge duplicates to avoid split incident histories and routing errors.

## Additional Tips for Data Foundations Customers

* Verify Discovery schedules to resolve stale CI issues, as failures or out-of-scope Discovery jobs often cause stale data.
* Review and update Identification and Reconciliation (IRE) rules to address duplicate CI problems.
* Use CMDB enrichment rules to auto-populate missing location or ownership fields from related records, such as deriving location from IP subnet data.  
The Remediation actions panel available for a chart in the CMDB success advisor dashboard for Data Foundations displays suggestions for targeted actions to address Data Foundations data quality issues and improve the overall quality of your Configuration Management Database (CMDB). Select the Ask Otto action on a KPI card to start an agent conversation without waiting for the next scheduled agent run.
Figure 1. Remediation actions panel

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
* Displays context-aware action suggestions
* Supports quick, informed remediation steps
* Focuses attention on meaningful tasks
* Appears only when actionable insights are available
{#cmdb-sa-df-remediation__ul_ugk_vc2_ngc}

## Accessing the Remediation actions panel {#cmdb-sa-df-remediation__section_s4n_d5m_k3c}

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 displaying suggestions for various remediation actions.

## Available remediation actions {#cmdb-sa-df-remediation__section_zl5_vc2_ngc}

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 displays a suggestion to review
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.  
    The remediation actions depend on the cause:

    * Turn on sync setting: appears when the sync setting is turned off. Shown only to users with the CMDB admin role. For more information, see [Principal class sync in Data Foundations advisor](https://www.servicenow.com/docs/82sDnvJOiWKIBVgHoGMRCQ "When other tools or processes add or remove principal classes outside the advisor scope, the Data Foundations advisor displays a notification prompting you to review and update the scope.").
    * Managed by group setting: opens CI Class Manager so you can add the managed by group field to the affected classes. Appears when at least one contributing class is missing the field.
    * View CIs: opens the list of CIs missing managed by group. Appears in place of the Managed by group setting action when you can't access that setting.

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.

The Stale CIs card and the Duplicate CIs card on the Data Foundations advisor dashboard each display their own Ask Otto action, separate from this panel. For more information, see [Monitoring CMDB data quality using dashboard metrics in CMDB success advisor for Data Foundations](https://www.servicenow.com/docs/0LfgpANAVJFFuKuyyr1l_g "The CMDB success advisor for Data Foundations dashboard enables CMDB administrators to identify and address data quality issues specific to principal classes in the Configuration Management Database (CMDB).").

## Data Foundations specific remediation tips {#cmdb-sa-df-remediation__section_qs4_w5m_k3c}

* 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 require 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.
{#cmdb-sa-df-remediation__ul_dwh_w5m_k3c}

