---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# IRE support for non-CMDB tables

# IRE support for non-CMDB tables {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Apply Identification and Reconciliation Engine (IRE) processes to supported non-CMDB
tables to ensure data integrity and health of those tables.  
Starting with the Australia release, IRE supports some non-CMDB tables. You can use all IRE features with some non-CMDB tables after creating identification rules (CI identifiers and identifier entries) for those tables. Non-CMDB tables supported for IRE features include:

* In an application-specific scope: All non-CMDB tables
* In the global scope: Only non-CMDB tables that are preset in the base system. In the Australia release for example, the Location \[cmn_location\], Department \[cmn_department\], Cost Center \[cmn_cost_center\], Building \[cmn_building\], User \[sys_user\], and Group \[sys_user_group\] non-CMDB tables are supported.
{#ire-support-non-cmdb-tables__ul_rvt_yq5_kvb}  
You can't use the [CI Class Manager](https://servicenow-prod.fluidtopics.net/_5oPzOtFh0tw7g3dNDSsVw "Use the CI Class Manager to centrally view, create, or edit basic class definitions, class settings for Identification and Reconciliation Engine (IRE), CMDB Health, and manage some Service Mapping definitions.") to manage any IRE-related rules for non-CMDB tables. Instead, you must work directly with the respective tables in list views to create and manage those rules as described in the following procedures:

* [Create an identification rule for a non-CMDB table](https://servicenow-prod.fluidtopics.net/84iqupzMNZC~Pl50kmlyhw "To use Identification and Reconciliation Engine (IRE) features with supported non-CMDB tables, you must first create identification rules that uniquely identify the table records. Each non-CMDB table can be associated with a single identification rule.")
* [Create a reconciliation rule for a non-CMDB table](https://servicenow-prod.fluidtopics.net/xUjzlmhvB~CX5tShPwiYow#create-reconciliation-rule-non-cmdb "Create a static or a dynamic CI reconciliation rule for a non-CMDB table.")
* [Create an IRE data source rule for non-CMDB tables](https://servicenow-prod.fluidtopics.net/JWsfibMxx0ZfgH9ol16omw "When using Identification and Reconciliation Engine (IRE), you can prevent a specific data source from inserting new records for a specific non-CMDB table. Create IRE data source rules for data sources that you don't trust in creating records but continue to trust in updating those records that exist.")
* [Create a data refresh rule for a non-CMDB table](https://servicenow-prod.fluidtopics.net/paujpUyver8QcZ_ehP56IA "To apply Identification and Reconciliation Engine (IRE) features to supported non-CMDB tables, create data refresh rules for those tables. Data refresh rules are used to determine if a record is stale for a specific data source. Such records can then be updated by a lower-priority authorized data source.")
* [Create an identification inclusion rule for a non-CMDB table](https://servicenow-prod.fluidtopics.net/BP7CVimDLR~_MJNsl0aFSA "Narrow the scope of records that are included in the identification process of non-CMDB records by creating an identification inclusion rule.")
* [Simulate payload execution using
  identification simulation](https://servicenow-prod.fluidtopics.net/sD36MHY810WTKICzlQYBuA#identification-simulation "Identification simulation is a central location for automatically constructing a payload that is guaranteed to be complete and valid. You can then simulate the processing of the payload by the Identification and Reconciliation Engine (IRE) and examine the results before actually submitting it for execution by IRE.")
* [Use partial payloads](https://servicenow-prod.fluidtopics.net/sjBf8XCF9ptVTurEi7FuQg "IRE is an underlying key component in Identification and Reconciliation, providing a centralized framework to perform identification and reconciliation processes across different data sources. IRE uses identification rules, reconciliation rules, and IRE data source rules when processing incoming data before inserting that data to the CMDB.")
* [Review and process de-duplication tasks](https://servicenow-prod.fluidtopics.net/nlGsVsAC4XQomS3Xpqmtkg "Duplicate CIs in the CMDB unnecessarily overload the system and interfere with the CMDB's integrity and reliability. It is therefore important to regularly use CMDB tools that detect and remediate duplicate CIs.")
{#ire-support-non-cmdb-tables__ul_dnf_jsf_lvb}  
You can use the following store apps with supported non-CMDB tables:

* [CMDB 360 in CMDB Workspace](https://servicenow-prod.fluidtopics.net/ZZb8FO69VEDrDKIGfBHBbQ "The CMDB 360 dashboard provides aggregations and analysis of CMDB 360 data. CMDB 360 collects data about all the discovery sources reporting attribute values for CIs. Use the CMDB 360 view in CMDB Workspace to track activities and identify potential issues of discovery sources. You can also create your own queries and associated schedules and reports to explore CMDB 360 data.")
* [IntegrationHub ETL](https://servicenow-prod.fluidtopics.net/o3eK_l0nhtAcQ_AgXuZ95Q "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.")
{#ire-support-non-cmdb-tables__ul_aw1_t5k_wvb}  
IRE processes are applied to supported non-CMDB tables with the following differences:

* IRE doesn't populate the discovery_source, last_discovered, and the first_discovered attributes if those attributes don't exist in the non-CMDB table.
* IRE uses the non-CMDB table's class name as sys_class_name if the table doesn't include a sys_class_name attribute.
* IRE payloads don't support relationships with non-CMDB tables.
{#ire-support-non-cmdb-tables__ul_gkt_kcv_kvb}  
Hinweis:  
Although IRE-related user interface and accompanying documentation might reference CMDB and CMDB elements, most of those references also apply to any supported non-CMDB tables.
* **[Create an identification rule for a non-CMDB table](https://servicenow-prod.fluidtopics.net/84iqupzMNZC~Pl50kmlyhw)**   
  To use Identification and Reconciliation Engine (IRE) features with supported non-CMDB tables, you must first create identification rules that uniquely identify the table records. Each non-CMDB table can be associated with a single identification rule.
* **[Create a reconciliation rule for a non-CMDB table](https://servicenow-prod.fluidtopics.net/xUjzlmhvB~CX5tShPwiYow#create-reconciliation-rule-non-cmdb)**   
  Create a static or a dynamic CI reconciliation rule for a non-CMDB table.
* **[Create a data refresh rule for a non-CMDB table](https://servicenow-prod.fluidtopics.net/paujpUyver8QcZ_ehP56IA)**   
  To apply Identification and Reconciliation Engine (IRE) features to supported non-CMDB tables, create data refresh rules for those tables. Data refresh rules are used to determine if a record is stale for a specific data source. Such records can then be updated by a lower-priority authorized data source.
* **[Create an identification inclusion rule for a non-CMDB table](https://servicenow-prod.fluidtopics.net/BP7CVimDLR~_MJNsl0aFSA)**   
  Narrow the scope of records that are included in the identification process of non-CMDB records by creating an identification inclusion rule.
* **[Create an IRE data source rule for non-CMDB tables](https://servicenow-prod.fluidtopics.net/JWsfibMxx0ZfgH9ol16omw)**   
  When using Identification and Reconciliation Engine (IRE), you can prevent a specific data source from inserting new records for a specific non-CMDB table. Create IRE data source rules for data sources that you don't trust in creating records but continue to trust in updating those records that exist.