Asset Reconciling with CI

[Rajanmehta]

Hello Team,

I want to understand how OOB CI gets sync with previously created asset? 

As per my understanding we get the asset first and it is recorded in the stockroom. After that asset is assigned to an user and once it comes on network it gets discovered by discovery and it should merge with the previously created asset based on serial number. 

So my question is, is there BR, scheduled job or anything else for the above logic? 

Thanks,

Rajan

[Selva Arun · Accepted solution]

Hi,

The synchronization between Asset and Configuration Item (CI) is managed through two key business rules in ServiceNow:

1. Update CI fields on change (on the Asset [alm_asset] table)
2. Update Asset fields on change (on the Configuration Item [cmdb_ci] table)

This ensures that updates made to one record (asset or CI) automatically reflect on the corresponding record, keeping them synchronized. These updates occur when the asset and CI are logically mapped based on specific identifiers, like the serial number.

To address your question:

• The synchronization logic doesn’t rely on a specific scheduled job or a Business Rule (BR) directly for merging an asset with an existing CI. However, it uses the Identification and Reconciliation Engine (IRE), which ensures that CIs are created or updated based on asset records, particularly when a serial number is involved.

• The Asset to CI synchronization happens when the asset’s state changes (for example, moving from stock to in use), and the CI status is updated accordingly. Similarly, changes in CI status (e.g., Install or Retired) also trigger updates on the asset.

The system property glide.create_alm_asset.async is responsible for controlling asset creation delays, which impacts the timing of asset synchronization with CIs. If set to true, assets are created by the scheduled job every 15 minutes, ensuring large volumes of CIs are handled efficiently. If set to false, assets are created immediately from CIs.

Additionally, Asset-CI mapping and synchronization are impacted by the sn_itam_enable_cache_for_asset_ci_mapping property, which can improve performance by caching certain mappings.

If you're looking to merge the asset with an existing CI upon discovery, the serial number plays a key role in this process. Discovery will match the serial number with the existing asset in the stockroom and ensure the CI is merged accordingly.

The above has been summarized from Asset and CI management

If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'** and **'Accept it as a Solution'**? This will help other community members who might have the same question find the answer more easily.

Thank you for your consideration.

Selva

[Rajanmehta]

Perfect. Thanks Arun.