{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":46898,"path":"servicenow-platform/configuration-management-database-cmdb/configuring-ire.md","title":"Configuring CMDB Identification and Reconciliation","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configuring CMDB Identification and Reconciliation\n\nConfigure the necessary rules for CMDB Identification and Reconciliation \\(IRE\\) to function effectively.\n\n## Configuration overview\n\n-   [Create identification rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/c_IdentificationRules.md)\n\n    Identification rules are essential in correctly identifying CIs in the CMDB to prevent the creation of duplicate CIs. Effective identification rules help determine whether an incoming CI is added to the CMDB or used to update and existing CI.\n\n-   [Create reconciliation rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/r_ReconciliationRulesPrinciples.md)\n\n    Static and dynamic reconciliation rules determine which discovery source is authorized to update which CI attributes. Reconciliation rules are important in preventing discovery sources from overwriting each other's updates to the same attribute values.\n\n-   [Create data source rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/create-ire-data-source-rule.md)\n\n    Data source rules prevent discovery sources from inserting new CIs for a specific class. Data source rules are useful in preventing untrusted discovery sources from creating new CIs while continuing to trust these discovery sources in updating existing CIs.\n\n-   [Create dependent relationship rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/c_ServiceRulesMetadata.md)\n\n    Dependent relationship rules define the dependency structure of the CI types and the relationship types in service definitions, which help in CI identification and in the construction of business service maps.\n\n\n-   **[Identification rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/c_IdentificationRules.md)**  \nThe CMDB identification process relies on identification rules to uniquely identify CIs.\n-   **[Reconciliation rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/r_ReconciliationRulesPrinciples.md)**  \nReconciliation rules determine which discovery sources can update CI attributes.\n-   **[Exclude classes from Dynamic IRE](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/dynamic-ire-exclude-class.md)**  \nExclude 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.\n-   **[Configure CI reclassification during IRE processing](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/c_CIReclassification.md)**  \nDuring the Identification and Reconciliation Engine \\(IRE\\) CI identification process, a CI might need to be reclassified to a different sys\\_class\\_name type. By default, CIs are reclassified automatically. If automatic reclassification is disabled, then the CI is not reclassified and the system generates a reclassification task for your review.\n-   **[Create an IRE data source rule](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/create-ire-data-source-rule.md)**  \nWhen using Identification and Reconciliation Engine \\(IRE\\), you can prevent a specific discovery \\(data\\) source from inserting new CIs for a specific class. Create IRE data source rules for discovery sources that you don't trust in creating CIs but continue to trust in updating those CIs that exist.\n-   **[CMDB dependent relationship rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/c_ServiceRulesMetadata.md)**  \nService definitions consist of CI types and relationship types. Dependent relationship rules define the dependency structure of the CI types and the relationship types in these service definitions, helping in CI identification and in the construction of business service maps.\n\n**Parent Topic:**[CMDB Identification and Reconciliation \\(IRE\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/c_CMDBIdentifyandReconcile.md)\n\n"}}