---
sourceDocument: Australia Asset Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-asset-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Asset and CI sync for OT assets

# Asset and Configuration Item (CI) synchronization for Operational Technology (OT) assets {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Asset and Configuration Item (CI) synchronization for Operational Technology (OT) assets

This feature ensures synchronization between assets and configuration items (CIs) specifically for Operational Technology (OT) assets in ServiceNow.
Unlike typical assets that rely on serial numbers for synchronization, OT assets often use MAC addresses.
This synchronization maintains accurate relationships and data consistency between the Asset \[almasset\], Configuration Item \[cmdbci\], and Network Adapter \[cmdbcinetworkadapter\] tables based on MAC addresses as well as serial numbers.
Show full answer Show less  

## Key Features

* **MAC Address Inclusion:** The Asset table includes a MAC address field (macaddr) to support OT assets without serial numbers.
* **Network Adapter Table:** Stores MAC addresses linked to CIs, enabling multiple MACs per CI and maintaining their relationships.
* **Synchronization from Asset to CI:** On asset creation or MAC address update, a new CI and associated Network Adapter record are created; existing MAC address records are not updated but new ones are created.
* **Synchronization from CI to Asset:** When a CI with a MAC address is created, the corresponding asset is created or updated to include the MAC address if missing.
* **CI Naming Rules:** CI names are generated based on availability of serial numbers and MAC addresses, combining these with model names. Updates to CI names occur only if the name is not manually modified and the CI is discovered from an asset.
* **System Property Control:** The synchronization via MAC address is controlled by the system property **snitamcommon.macaddresssync**, which defaults to false and must be enabled for MAC-based sync.
* **OT Entity Synchronization:** Both Asset and CI tables include OT entity fields. Creating or updating OT entities on either side ensures the corresponding record is marked and linked. Importantly, once a CI is marked as an OT entity, it cannot revert to non-OT status.

## Practical Benefits for ServiceNow Customers

* Enables accurate and automated synchronization between OT assets and their CIs even when serial numbers are absent.
* Maintains consistent and reliable asset and CI data by leveraging MAC addresses and network adapter relationships.
* Supports effective lifecycle and configuration management for OT environments through automated creation and update processes.
* Provides clear CI naming conventions to facilitate easier identification and management of OT assets and CIs.
* Allows controlled activation of MAC address synchronization to suit organizational requirements.
* Ensures OT entities are properly tracked and remain designated as OT assets within the CMDB, aiding governance and compliance.  
Maintain synchronization between asset and CI for OT assets through MAC address on the asset and the Network Adapter CI.

Synchronization between asset and CI is achieved using the Serial number
field. However, an OT asset need not necessarily have a serial number, but it's associated with a MAC address. Therefore, the asset-CI synchronization for OT assets includes the MAC address (mac_addr) field in the Asset \[alm_asset\] table in
addition to the
serial
number.

A CI can have multiple MAC addresses. The Network Adapter \[cmdb_ci_network_adapter\] table stores all the MAC addresses and also has a reference field to the CI \[cmdb_ci\] table. Therefore, the relationship between MAC address and CI
is maintained.

## Synchronization from asset to CI {#asset-ci-sync-ot-assets__section_gw4_yzl_5dc}

When an asset is created with a MAC address, synchronization happens as follows:

1. A CI is created.
2. A record for the corresponding MAC address is created in the Network Adapter \[cmdb_ci_network_adapter\] table with a reference to the CI.
{#asset-ci-sync-ot-assets__ol_h5s_h1m_5dc}

When the MAC address of an asset is updated, the existing record in the Network Adapter \[cmdb_ci_network_adapter\] table isn't updated. Instead, a new record is created in the Network Adapter \[cmdb_ci_network_adapter\] table.

## Synchronization from CI to asset {#asset-ci-sync-ot-assets__section_fnp_4bm_5dc}

When a CI is created with a MAC address, synchronization happens as follows:

1. An asset is created.
2. The MAC address of the CI is copied to the asset.
{#asset-ci-sync-ot-assets__ol_gnp_4bm_5dc}

If there's an existing CI, then the associated asset is updated with the MAC address only if the asset doesn't have it already.

## Rules for generating CI names {#asset-ci-sync-ot-assets__section_ugb_qcm_5dc}

A CI name follows a format that's based on the following conditions:
{#asset-ci-sync-ot-assets__table_swb_bdm_5dc__entry__2}

| Condition | CI name format |
|-|-|
| Asset has a Serial number | Concatenation of Serial number and Model name separated by hyphen. For example, SN123 - DemoModel. |
| Asset has a Serial number and a MAC address | Concatenation of Serial number and Model name separated by hyphen. For example, SN123 - DemoModel. |
| Asset has no Serial number but has a MAC address | Concatenation of MAC address and Model name separated by hyphen. For example, 88-22-33-66-888-AB - DemoModel. |
| Asset has no Serial number and MAC address | Model name |
[Table 1. Conditions and CI name]

{#asset-ci-sync-ot-assets__table_swb_bdm_5dc}  
Whenever there are updates to Serial number or MAC address fields, the CI name is synchronized only under the following conditions:

* CI name isn't updated manually.
* The Discovery source is SNassetmanagement, which means that the CI is created from an asset.
* CI name hasn't been modified by CMDB.
{#asset-ci-sync-ot-assets__ul_pvs_chm_5dc}  
Note:  
The sn_itam_common.mac_address_sync system property enables you to synchronize asset and CI using the Mac address. By default, this system property is set to false. To enable synchronization through the Mac address, set this system property to true by navigating to Enterprise Asset WorkspaceAdmin centerOther configuration.

## OT entity synchronization between asset and CI {#asset-ci-sync-ot-assets__section_xlv_ztq_5dc}

The CI \[cmdb_ci\] table has the OT entity \[cmdb_ot_entity\] field. Also, the Asset \[alm_asset\] has a corresponding OT entity \[ot_entity\] field. Synchronization of the OT entity happens as
follows:

* When a CI is created with the OT entity reference set on the CI, the OT entity \[ot_entity\] field in the Asset \[alm_asset\] table is set to true.
* When an asset with the OT entity set to true is created, a corresponding CI and an OT entity are created on the CMDB side. The OT entity reference is then set on the CI.

{#asset-ci-sync-ot-assets__ul_f1s_bwq_5dc}  
Important:  
After a CI is marked as an OT entity, it can't be reverted to a non-OT entity.
**Related concepts**   

* [Installing OT Asset Management](https://www.servicenow.com/docs/RHiBAo6NFYEXtocW1v1_bg "Install the OT Asset Management application so that you can manage the life cycles of your Operational Technology (OT) assets. You can install the application from either the ServiceNow Store or the Admin Home page.")
* [OT Asset Workspace](https://www.servicenow.com/docs/gRUo~wiEmUoI46RXZduGlw "The OT Asset Workspace is the intuitive and streamlined user interface of the OT Asset Management application to manage your Operational Technology (OT) and Operational Equipment (OE) assets.")
* [OT Asset Management licensing](https://www.servicenow.com/docs/11GAcOcIWLNkr7JVBJZp7A "The ServiceNow platform uses a licensing method where your organization is charged for using the OT Asset Management application. In this licensing model, all assets of the Industrial and Hardware model categories are charged based on the Subscription unit ratio.")  
**Related reference**   

* [Installed with OT Asset Management](https://www.servicenow.com/docs/5CxtNJqI6PQ01nWe7v0LSg "Several types of components are installed with activation of the com.sn_otam plugin, including user roles and applications.")

*[\>]: and then