---
sourceDocument: Australia Telecom Service Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/telecom-service-ops

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Telecom Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Control CI attribute updates

# Control CI attribute updates using Reconciliation rules {#ariaid-title1}

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

To prevent specific attributes of a configuration item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute
when multiple sources provide values.

## Before you begin

Role required: admin

## About this task

Reconciliation Rules are processed by the Identification and Reconciliation Engine (IRE) and are essential for maintaining data integrity in the CMDB.  
Use Case: You can prevent Discovery from updating specific attributes while allowing other sources to update them. Define a rule that excludes the Discovery source and permits updates from sources like SCCM or manual entry.  
Note:  
Only one Reconciliation Rule should be active for a specific CI class and attribute combination to avoid conflicts.

## Procedure

1. Navigate to AllCI Class Manager.
2. Select the target CI class (e.g., cmdb_ci_computer).
3. In the Reconciliation Rules tab, click New to create a rule.
4. Provide the rule name and select the Discovery source to apply the rule to.
5. Specify the attributes that this rule will govern.
6. Set the source precedence to allow only the selected sources to update the specified attributes.

## Result

Certain CI attributes will no longer be updated by untrusted or lower-priority data sources like Discovery. Only the sources defined in the rule (e.g., SCCM, manual updates) will be allowed to update those attributes.
**Related tasks**   

* [Configure attribute value discrepancy in CMDB 360](https://www.servicenow.com/docs/2cIz3JSUC~KaqY3c3DEMwA "Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.")

*[\>]: and then