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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Feature adoption

# Feature adoption insights dashboard in Service Graph Workspace {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 9 minutes to read

Use the Feature adoption insights page in Service Graph Workspace to see and increase the level of adoption of key CMDB features and service instances to improve the overall health of the CMDB. Explore how tools and features can
maximize the health and efficiency of your CMDB and use direct links to install and start using features immediately.

## Access {#sg-workspace-insights-featadoption__section_wcs_25k_thc}

1. Navigate to WorkspacesService Graph Workspace.
2. In the navigation panel, select the Insights icon.
3. On the Insights page navigation pane, select Feature adoption.
{#sg-workspace-insights-featadoption__ol_l1d_rj2_thc}

Role required: Any role containing sn_cmdb_user (sn_cmdb_user, sn_cmdb_editor, sn_cmdb_admin)

## CMDB feature adoption {#sg-workspace-insights-featadoption__section_a35_l2l_wwb}

Shows dial charts for the overall adoption levels of all three categories of CMDB tools and features:

Data ingestion
:   Tools and features that support and ensure ingestion of high-quality data into the CMDB.

Data governance
:   Tools and features that let you manage the CMDB data after it has been ingested.

Search and analytics
:   Tools and features that provide meaningful and helpful insights into the CMDB data.

Select each dial chart in the tile to access its tab and associated cards with further details about the features in the category. Pay special attention to categories with low levels of adoption and those features that aren't yet
implemented in the instance and which you should consider for adoption.  
Each category tab shows cards for the features in the category and the following general cards:

* Overall adoption level for the tab: The calculated overall level of adoption for the tab. Calculations are specific for each tab, and can be based, for example, on the level of adoption of some or all the features in the tab.
* Adoption progress: Installation, activation, or usage status per feature in the tab. Select a feature link to access a relevant resource such as the feature's landing page with an overview dashboard or an installation location.
{#sg-workspace-insights-featadoption__ul_ly3_pzs_wwb}  
Depending on adoption level, a card might contain any of the following resource links:

* Learn more: Link to documentation to learn and explore the benefits and usage of the feature.
* View demo: Link to a short demo about the feature.
* Get started: Link to a landing page where you can start immediately utilizing the feature.
* Install app: Link to the ServiceNow Store where you can immediately install the app.
{#sg-workspace-insights-featadoption__ul_ffx_flk_wwb}  
Cards use different methods to examine the instance and determine if the card's feature is installed, activated, and being used. For example, some cards check for the installation status of plugins and some cards rely on data in the specific feature tables. Many counts and aggregation data that appear on cards is based on [Performance Analytics indicators](https://www.servicenow.com/docs/access?context=c_Indicators&version=australia&pubname=australia-now-intelligence&ft:locale=en-US) built on top of the Base Aggregate Data \[sn_cmdb_ws_base_aggregate_data\] table.

* If the result is that the card's feature is installed or being used, then the card shows charts and counts about the level of usage. In which case, the card's label might slightly adjust.
* If the result is that the card's feature isn't installed or isn't in use, then links are provided to resources where you can explore, install, and start using the feature.
{#sg-workspace-insights-featadoption__ul_fjd_hj3_fxb}

Most of the cards scheduled jobs run every 24 hours, therefore, depending on the type of data, some card data is based on recent but not current data. The Last updated timestamp in the cards reflects the collection time for the data
that was used for the card. Also, immediately after getting started with a feature, a card won't reflect on the latest status or usage of the feature, until up to 24 hours when the card's scheduled job runs (for the CIs processed by IRE
based on source card, the associated scheduled job, CMDB Workspace - Populate aggregates Monthly, runs monthly).

The following sections provide details for each card, including the calculation script used for the card.

## CMDB feature adoption: Data ingestion {#sg-workspace-insights-featadoption__section_r3g_dkk_wwb}

The overall adoption level for data ingestion maps to the following findings in the instance:

* Low (red): Less than 80% of CIs are processed by Identification and Reconciliation Engine (IRE)
* Moderate (amber): 80---90% of CIs are processed by IRE
* High (green): Over 90% of CIs are processed by IRE
{#sg-workspace-insights-featadoption__ul_pkq_bxz_wwb}  
Data ingestion contains the following features and aggregations:

CIs processed by IRE

:   Determines the percentage of CIs that are processed by [IRE](https://www.servicenow.com/docs/Z8diB6pYFbsGQMgZmJZYfg "The Identification and Reconciliation module provides a centralized framework for identifying and reconciling data from different data sources. It helps maintain the integrity of the CMDB and some non-CMDB tables when multiple data sources are used to create and update CI records."), by checking the Source \[sys_object_source\] table. CIs that aren't processed by IRE introduce a data integrity risk.

    The percentage of CIs that are being processed by IRE determines both, the level of adoption for this feature card and the overall adoption level for the entire data ingestion category.

Service Graph Connectors
:
    Determines the installation and usage status of [Getting started with Service Graph Connectors](https://www.servicenow.com/docs/llR5whccV6~8Oi~Q_e8~xQ "Service Graph Connectors, including API Service Graph Connectors, are predefined integrations that ingest third-party data and API data into the Configuration Management Database (CMDB) from various domains, such as security, servers, software or monitoring, Internet of Things (IoT), and cloud."), by checking:

    * If the ITOM Licensing plugin (com.snc.itom.license) is active
    * If there is at least one Service Graph Connector installed in the instance
    {#sg-workspace-insights-featadoption__ul_ngy_pnz_wwb}

    If Service Graph Connectors are installed and are in use, then the card shows a count of those connectors.

    Note:  
    The count of Service Graph connectors that appears on the card might be slightly different than the number of connectors that show on the ServiceNow Store site because the counting methods that are used are different.

IntegrationHub ETL

:   Determines whether the [IntegrationHub ETL](https://www.servicenow.com/docs/_zqPaqbG5vaxHRfrZ6bq7Q "Use the IntegrationHub ETL store app to create and manage ETL transform maps, which integrate third-party data into the CMDB or into non-CMDB tables without compromising the integrity of data. IntegrationHub ETL provides a simplified user interface that guides you through the integration process end-to-end, including a test integration run of sample data.") store app is installed and used, based on records in the CMDB Integration Studio Application Data Sources \[cmdb_inst_application_feed\] table. If IntegrationHub ETL is in use,
    then the card shows a count of ETL transform maps in IntegrationHub ETL (demo ETL transform maps aren't counted).

    Select View ETL transform maps to open IntegrationHub ETL where you can examine existing ETL transform maps and create new ones.

CIs processed by IRE based on source

:   Chart showing CIs processed by IRE, grouped by Service Graph Connectors, ServiceNow Discovery, a combination of both, and others, for the past six months.

    The following discovery sources are counted as ServiceNow Discovery:

    * ServiceNow
    * ServiceWatch
    * ACC-Visibility
    * AgentClientCollector
    * CredentiallessDiscovery
    {#sg-workspace-insights-featadoption__ul_shh_d5c_dxb}

    Point to the chart to show monthly aggregation data.

    This card is hidden if there are no CIs processed by IRE.

CMDB application for APIs and CLI

:   Determines whether the [CMDB application for APIs and CLI](https://www.servicenow.com/docs/access?context=cmdb-cli-commands&version=australia&pubname=australia-application-development&ft:locale=en-US) store app is installed.

    This card appears only if the store app isn't installed, providing helpful resources for exploration and adoption.

## CMDB feature adoption: Data governance {#sg-workspace-insights-featadoption__section_w2m_rkk_wwb}

The overall adoption level for data governance maps to the following findings in the instance:

* Low (red): Less than 33% of features are used
* Moderate (amber): 33---66% of features are used
* High (green): Over 66% of features are used
{#sg-workspace-insights-featadoption__ul_i3y_dxz_wwb}  
The overall level of adoption of data governance is based on whether [CMDB Data Manager](https://www.servicenow.com/docs/nWW2jub5w6Qoj6MA9JzZiw "The integrity and health of the CMDB is essential for the various features that depend on the data in the CMDB. As the CMDB grows and infrastructures change, the CMDB can accumulate stale, duplicate, or outdated CIs and therefore no longer accurately reflect the IT infrastructure and applications in the organization.") features are used.

CMDB Data Manager/CIs used in Data Manager policies
:
    Determines usage by checking if either of the following conditions is true:

    * There are any user-created Delete, Retire, or Archive policies (by searching table CMDB Data Manager Policy and Attributes \[cmdb_data_manager_policy_and_attributes\])
    * There are any CIs processed by these user-created Delete, Retire, or Archive policies, in the last 90 days (by searching table CMDB Data Management Policy Executions \[cmdb_data_management_policy_execution\])
    {#sg-workspace-insights-featadoption__ul_iyy_f4p_fxb} If CMDB Data Manager is in use, shows a chart with CIs that were processed by these policies in the past six months, by month, and by policy type.

Data attestation/CIs used in data attestation

:   Determines usage by checking if either of the following conditions is true:

    * There are any user-created [Attestation policies](https://www.servicenow.com/docs/5frqJY24lwmPr3hcMa8YQA "Verify the existence of actual IT infrastructure and applications that you own, systematically and in bulk. As CIs are continuously ingested into the CMDB from various data sources, ensure the integrity of the CMDB. Remove any stale CIs that are associated with IT infrastructure or applications that no longer exists.") (by searching table CMDB Data Manager Policy and Attributes \[cmdb_data_manager_policy_and_attributes\])
    * There are any CIs processed by these user-created Attestation policies, in the last 90 days (by searching table CMDB Data Management Policy Executions \[cmdb_data_management_policy_execution\])

    {#sg-workspace-insights-featadoption__ul_jf2_spp_fxb}

    If data attestation is in use, shows a chart with CIs that were processed by attestation policy tasks in the past six months, by month.

Data synchronization

:   Checks if there is at least one class for which the managed_by_group attribute is globally set so that all class CIs are synchronized on the same value.

    For information about synchronizing group assignment attributes using the CI Class Manager, see [Set the group for a CI or an entire class of CIs](https://www.servicenow.com/docs/clmqtvkMnhGsy19_nNzQEw "Synchronize group assignment attributes on entire CI classes and individual CIs using the CI Class Manager.") and [Synchronizing group assignment attributes](https://www.servicenow.com/docs/WfznvvwqKlAEMwUWgdV08g "To empower a particular user group to manage a collection of CIs or CI classes, set group assignment attributes through the Technology management offering or the CI Class Manager. The operation synchronizes the group attribute data across all CIs that belong to the specified CI class or groups of CIs.").

Principal classes

:   Checks if the Principal Class filter is configured with at least one principal class. The Principal Class filter limits the number of CIs that appear in list views, to show only CIs of principal classes. Reducing the amount
    of data in list views to only relevant data, improves performance and efficiency.

    For more information about Principal Class and how to manage the Principal Class filter in CI Class Manager, see [Principal Class](https://www.servicenow.com/docs/ENE4G2KZHXZ4qUyd2nyztg "A Principal Class is a designation for those CMDB classes that are most critical for foundational data health and governance in the organization. Those classes are then prioritized for tracking, health, certification, lifecycle management, and class list views.").

## CMDB feature adoption: Search \& analytics {#sg-workspace-insights-featadoption__section_krk_skk_wwb}

The overall adoption level for search \& analytics maps to the following findings in the instance:

* Low (red): Less than 33% of features are used
* Moderate (amber): 33---66% of features are used
* High (green): Over 66% of features are used
{#sg-workspace-insights-featadoption__ul_grw_2xz_wwb}  
Search \& analytics contains the following features and aggregations:

CMDB Query Builder/Query Builder queries
:
    Determines if the [CMDB Query Builder](https://www.servicenow.com/docs/uLyJjmkHqIHkDiHLMf8PGA "The CMDB Query Builder enables you to build complex infrastructure and service queries that span multiple CMDB classes, non-CMDB tables, and that involve many CIs that are connected by different relationships.") is in use, by checking if either of the following conditions is true:

    * There are any records in the Saved Queries \[qb_saved_query\] table in which Source is QB
    * There are any queries executed or queries executed with reports, in the last 90 days
    {#sg-workspace-insights-featadoption__ul_stw_jtd_dxb}If CMDB Query Builder is in use, shows a chart with counts of query executions and query executions in reports, for the past six months, by month.

    Point to the chart to see monthly aggregation data.

Intelligent search

:   Determines if [Intelligent Search for CMDB](https://www.servicenow.com/docs/OB6nz9XxyG05iE450g6zPQ "Use everyday natural language query (NLQ) in a search string to query for a set of CIs in the CMDB. Intelligent Search for CMDB, parses, resolves ambiguities, and converts your search string into a valid CMDB query. Complex search strings open fully constructed on a canvas of CMDB Query Builder where you can continue and refine, or run.") is in use by checking the NLQ Query Logs \[nlq_query_log\] table for any records where source is CMDB_WS, from the past 90 days. If Intelligent
    Search is in use, shows counts of Intelligent Search queries for the past six months, by month.

CMDB 360 --- Records in Multisource

:   Total number of raw [CMDB 360](https://www.servicenow.com/docs/6TnrO1Jdq53J2fKTHQJ0Jw "CMDB 360 retains complete history about discovery sources and proposed values, involved in updates of CI attributes. Use CMDB 360 data to track how the CMDB is populated by various discovery sources at the CI attribute level. Also, to revert CI updates from a specific discovery source, or to recompute attribute values using updated reconciliation rules.") records in the CMDB 360 data store that contains records for each discovery source report, per each CI attribute. This card is identical to the [Total CMDB 360 records](https://www.servicenow.com/docs/B~~fehpAl6JhCYIPGHppag "The CMDB 360 view in CMDB Workspace and in Service Graph Workspace provides aggregations and analysis of CMDB 360 data which you can use to track activities and identify Potential issues of discovery sources. You can also create different types of your own queries and associated schedules and reports to explore CMDB data.") card in the Discovery Sources tile in the CMDB 360 view.

    This card appears only if CMDB 360 is enabled, which is determined by checking the ITOM Discovery License (com.snc.itom.discovery.license) plugin and the system property [glide.identification_engine.multisource_enabled](https://www.servicenow.com/docs/lNCFb9l~KujYLKQiMwjgfg "Several types of components are related to CMDB 360 (included in the com.snc.cmdb plugin), such as tables and properties.").

CMDB 360 queries

:   Count of CMDB 360 queries that exist in the CMDB Multisource Queries \[cmdb_multisource_query\] table.

    This card appears only if CMDB 360 is enabled, which is determined by checking the ITOM Discovery License (com.snc.itom.discovery.license) plugin and the system property [glide.identification_engine.multisource_enabled](https://www.servicenow.com/docs/lNCFb9l~KujYLKQiMwjgfg "Several types of components are related to CMDB 360 (included in the com.snc.cmdb plugin), such as tables and properties.").

CMDB Data Foundation dashboard

:   Determines if the [CMDB and CSDM Data Foundations Dashboards](https://www.servicenow.com/docs/DGC~Pd2lgvAXiO21Rh3Asg "The ServiceNow CSDM and CMDB Data Foundations Dashboards store app contains dashboards with insights into the key foundational metrics of your CMDB and Common Service Data Model (CSDM). This app uses ServiceNow health benchmarks to provide recommendations to ensure that the CMDB and CSDM are properly configured for optimal usage and to mitigate any potential risks.") store app (which includes the CMDB Data Foundation dashboard) is installed.

    This card appears only if the store app isn't installed, providing helpful resources for exploration and adoption. However, the feature is still included in calculating the search \& analytics overall level of adoption.

CMDB Health Dashboard

:   Determines if [CMDB Health](https://www.servicenow.com/docs/5tTKNbvdNPz2l14jzwTV1g "A healthy CMDB, based on health benchmarks in an organization, is essential to an effective and continuous use of the product. Health indicators such as duplicate CIs, required CI fields, and audits are evaluated and aggregated into health scores at the class, health group, and service levels. CMDB Health also provides a framework for applying standardized CI remediation.") is in use by checking if at least one CMDB Health Dashboard job is enabled.

    This card appears only if the feature isn't in use, providing helpful resources for exploration and adoption. However, the feature is still included in calculating the search \& analytics overall level of adoption.

*[\>]: and then