--- sourceDocument: Brazil ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Dynamic IRE # Dynamic IRE {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Dynamic IRE The Dynamic Identification and Reconciliation Engine (Dynamic IRE) in ServiceNow automates and enhances the identification of Configuration Items (CIs) within the Hardware \[cmdbcihardware\] class and its descendants. Unlike Static IRE, which relies on manually maintained rules, Dynamic IRE uses advanced algorithms to score and match CIs more accurately and efficiently during data ingestion, reducing duplicate CIs and eliminating the need for manual rule configuration. Show full answer Show less ## Key Features * **Automated CI Identification:** Dynamic IRE dynamically updates identification rules while processing data, improving CI matching accuracy. * **Parallel Algorithm Processing:** Evaluates multiple conditions simultaneously to determine the best CI matches across data sources. * **Class Applicability and Exclusions:** Applies only to the Hardware class and its descendants, but specific classes can be excluded to maintain custom Static IRE rules. * **Operational Modes:** * **Simulation Mode:** Runs Dynamic IRE in parallel with Static IRE to compare outcomes and performance, storing differences for detailed analysis. * **Committed Mode:** Enables Dynamic IRE exclusively, turning off Static IRE, with the ability to revert back if needed. * **System Property Control:** The glide.identificationengine.dynamicireenabled property manages switching between Dynamic and Static IRE. * **Detailed Comparison Tools:** Includes parity scoring and visual bar charts to analyze differences in CI processing outcomes, enabling informed decision-making. ## Getting Started and Best Practices Dynamic IRE is enabled by default on zBooted instances running Zurich Patch 11 or later. For upgraded instances still using Static IRE, customers should: * Start with simulation mode on a non-production instance to evaluate Dynamic IRE's effectiveness against Static IRE. * Use the CI Class Manager to enable simulation, review detailed comparison results, and assess performance before committing. * Once satisfied, commit to Dynamic IRE on production instances, or revert back to Static IRE if necessary. * Exclude any Hardware-descendant classes that require custom Static IRE rules to ensure tailored CI identification. ## Benefits for ServiceNow Customers * **Improved Accuracy:** More precise CI identification reduces duplication and improves CMDB data quality. * **Reduced Maintenance:** Eliminates the need for ongoing manual creation and tuning of IRE rules. * **Risk Mitigation:** Simulation mode allows safe testing and validation before production implementation. * **Flexible Control:** Easy switching between Dynamic and Static IRE provides operational flexibility. Dynamic Identification and Reconciliation Engine (IRE) processes CI identification for maximum accuracy and efficiency and eliminates the requirement to manually create or maintain rules. When necessary to differentiate, the legacy, manually-driven IRE, is referred to as Static IRE. Dynamic IRE is a new engine that you can choose to use instead of Static IRE. Dynamic IRE identifies CIs using an improved identification dynamic process and automatically updates its IRE identification rules during ingestion of data payloads. Dynamic IRE evaluates various conditions within the payload simultaneously by running algorithms in parallel to do both: * Score potential matches * Accurately determine CI identity across multiple data sources Compared to Static IRE, on average, Dynamic IRE matches CIs using a larger combination of the CI attributes to improve the chances of finding an optimal match, and by so, reducing the chances for duplicate CIs. You can't alter any of the algorithms or operations of Dynamic IRE. Dynamic IRE is applicable only to the Hardware \[cmdb_ci_hardware\] class and its descending classes. However, you can configure the system to exclude from Dynamic IRE specific classes descending from the Hardware class. Key benefits of Dynamic IRE are: * Usually identifies CIs more accurately resulting in a reduction of duplicate CIs. * Eliminates manual configuration and continuous maintenance of IRE process rules. {#dynamic-ire__ul_uwr_yky_jhc} ## Getting started with Dynamic IRE {#dynamic-ire__section_gmf_d3l_vjc} Dynamic IRE is enabled by default on zBooted instances running Zurich Patch 11 or a later release. In this state the system property glide.identification_engine.dynamic_ire_enabled is set to true and Dynamic IRE is considered to be in a 'committed mode'. On upgraded instances running Zurich Patch 11 or a later release, that are using Static IRE, you can switch into using Dynamic IRE as described in this topic. For more information, see the respective release notes for the family release of your instance. ## Modes of operation {#dynamic-ire__section_iqg_5w2_khc} Dynamic IRE provides two modes of operation: Simulation mode : In simulation mode, Dynamic IRE and Static IRE run in parallel so you can experience and compare Dynamic IRE to Static IRE. In simulation mode, both Static IRE and Dynamic IRE process the payloads. Any differences in processing and outcome are stored in the CMDB IRE Output Comparison Items \[cmdb_ire_output_comparison_item\] table. Also, after some time of simulations, you can compare the performance of Dynamic IRE to Static IRE. Committed mode : In committed mode, only Dynamic IRE performs IRE processes and Static IRE is turned off. Once in a committed mode, you can switch back to Static IRE without implications. Typically, you should start with the simulation mode on a non-production instance to test effectiveness and performance, examine the outcome, and then commit to full usage of Dynamic IRE on your production instance. ## Exclude classes from Dynamic IRE {#dynamic-ire__section_nwv_ngj_nhc} There might be reasons for configuring child classes descending from the Hardware class, to be excluded from Dynamic IRE. For example, you might want to exclude a custom class with custom attributes, for which there are IRE rules that are based on those custom attributes. In this situation, it might not be beneficial to apply Dynamic IRE for that class and its descendants. So if Dynamic IRE is enabled, Static IRE is still being used for those excluded classes. For more information, see [Exclude classes from Dynamic IRE](https://www.servicenow.com/docs/q~Kt_T8tHkYINVmYD2Vr9w "Exclude specific classes, for which Dynamic IRE isn't beneficial, from Dynamic IRE. When a hierarchy branch (such as the Hardware class branch) is configured to use Dynamic IRE, you can configure specific classes within that branch, to be excluded from Dynamic IRE."). ## Simulate and commit to Dynamic IRE {#dynamic-ire__section_xwx_4t2_khc} To start using Dynamic IRE exclusively, a general guideline is to test it first by simulation on a non-production instance: 1. Use a user role that meets the user role requirement: sn_cmdb_user. 2. On a non-production instance, navigate to the CI Class Manager. 3. In CI Class Manager, select Hierarchy and then select the Hardware class. 4. In the Hardware navigation panel, select Identification Rule. 5. In the Dynamic IRE section, select Simulate Dynamic IRE. 6. Carefully review the Simulate Dynamic IRE dialog box: * If you're ready to start a simulation to test Dynamic IRE on a non-production instance, select Simulate Dynamic IRE without selecting 'I have simulated and assessed Dynamic IRE on a non-production instance, and am now prepared to implement Dynamic IRE on a production instance.'. The simulation runs IRE processes on the Hardware and any descending classes, and then shows a comparison in terms of effectiveness and performance, between Dynamic and Static IRE. Carefully examine this comparison, which can help you determine whether to commit to using Dynamic IRE. * If you have already completed a simulation, reviewed the results, and are ready to fully use Dynamic IRE with the Hardware class, on a production instance select the agreement and then select Commit to Dynamic IRE. {#dynamic-ire__ul_tvt_xqt_kjc} {#dynamic-ire__ol_u23_p4z_jhc} Alternatively, you can use the glide.identification_engine.dynamic_ire_enabled system property to enable or disable Dynamic IRE, and by so, switching between Dynamic and Static IRE. For more information about this property, see [Properties for Identification and Reconciliation](https://www.servicenow.com/docs/AY91c4KJgbxojkOwkv6EZQ "Use the Identification and Reconciliation properties to configure the Identification and Reconciliation Engine (IRE)."). ## Switch back to Static IRE {#dynamic-ire__revert-static-ire} When the system is using Dynamic IRE, you can switch back to Static IRE: 1. In CI Class Manager, select Hierarchy and then select the Hardware class. 2. In the Hardware navigation panel, select Identification Rule. 3. In the Dynamic IRE is enabled section, select Change to Static IRE. {#dynamic-ire__ol_y45_drt_kjc} ## Comparison of the results of Dynamic IRE and Static IRE {#dynamic-ire__section_qgk_kr2_khc} In simulation mode, you can see a comparison of the activities and outcome between Dynamic IRE and Static IRE, at a high level and at a record level. Examine the details in this comparison carefully, to help you evaluate the effectiveness of Dynamic IRE in your environment before committing to using it. This comparison calculates a parity score, which is the percentage of identical results between Dynamic IRE and Static IRE. Note: For a mature Static IRE implementation (with manually-created rules), the parity score is expected to be high. This indicates that Dynamic IRE is capable of producing similar results to Static IRE without requiring any manually-created rules or validations for accuracy. Bar charts show the difference in CI operations of inserting CIs, updating CIs, and CIs found to be incomplete, between the two methods. Select a bar to show the list of comparison records from the CMDB IRE Output Comparison Items \[cmdb_ire_output_comparison_item\] table, for the selected bar chart. Those records contain the details about CIs that were processed differently between Dynamic IRE and Static IRE. Select a record to open it and to review the comparison details (in JSON format). On a record form, you can select Summarize to show an organized and more user friendly presentation of the comparison results, generated by the ServiceNow Otto® for CMDB IRE comparison record summarization skill.