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

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia IT 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}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

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 |
[Tabela 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}  
Nota:  
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}  
Importante:  
After a CI is marked as an OT entity, it can't be reverted to a non-OT entity.
**Conceitos relacionados**   

* [OT Asset Management licensing](https://www.servicenow.com/docs/AfXnpvxXnDnw6LTkZ7JXXg "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.")
* [OT Asset Workspace](https://www.servicenow.com/docs/z0vJDLQh9HJujFNM4bIKXA "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.")  
**Tarefas relacionadas**   

* [View the license report for the OT Asset Management application](https://www.servicenow.com/docs/FxaKdPJs9l04XP2Mf6ybFw "View details of the subscriptions consumed by your organization for the OT Asset Management application by using the ITAM License Report.")