---
sourceDocument: Xanadu Operational Technology Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/operational-technology

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Operational Technology Management

ft:clusterId :

    - optm

bundleId :

    - optm

workflow :

    - Technology


---

# Automatically convert your IT records to OT devices

# Automatically convert your IT records to OT devices {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Create a scheduled job that automatically converts your IT hardware to Operational Technology (OT) devices by using the Bulk Update Ruleset for Reassigning IT to OT feature. This scheduled job adds OT entity details to all
the IT hardware that you want to convert at once.

## Before you begin

Role required: admin

## About this task

You may have configuration items (CIs) classed as IT hardware that you want to create OT entity records for. Follow these general guidelines:

* Make sure that the fields you use apply to the filter criteria conditions in steps 3 to 4. Verify that the data set doesn't exceed 1 million records so that you can avoid performance-related issues.
* Create separate scheduled job definitions for the separate CI classes in steps 3 to 6. This way, you can filter each CI level and define the OT entity default values.
* Use the Class field in the filter to query only specific CI classes in step 3.  
  Note:  
  Only the hardware class and its extended classes are used in the source table.
* Use the Preview button to verify the records selected for further review in step 4.
* Verify the data in the OT Entity Default Configuration tab in step 5. The OT entity records are created using these default values.

{#automatically-convert-it-records-to-ot-devices__ul_acy_xgk_tzb}

You can also manually convert the IT hardware to the OT devices. For more information, see [Convert IT hardware to OT devices in a bulk edit](https://servicenow-prod.fluidtopics.net/KR9bw1dauyVGl~dI2O2sgQ "Choose multiple IT hardware devices and convert them to OT devices in a bulk edit so that you can edit your records more quickly and efficiently.").

## Procedure

1. Navigate to AllIndustrial Workspace AdminOT Manager AdminAutomated IT OT Bulk Conversion.
2. Select New.
3. On the Filter Criteria - OT Devices tab, set the source table and filter criteria to identify the CIs that you need to convert.  
   For example, if you want to add the OT entity details for all computers that are imported into the system that have a prefix of COMP, select the source table as cmdb_ci_computer and then add the
   filter criteria as \[Name\] \[starts with\] \[COMP\], \[Class\] \[is\] \[Computer\], and \[OT device details\] \[is empty\].

   You can also use CMDB groups to group IT CIs based on additional information, such as Software Installed, so that you can convert them to OT devices. For more information, see [Use CMDB groups to add OT context to IT CIs](https://servicenow-prod.fluidtopics.net/~SHZez~YgFtSLLIvC16DXQ "Use Configuration Management Database (CMDB) groups to group IT configuration items (CIs) based on additional information, like installed software. Then you can add Operational Technology (OT) context to the IT CIs.").
4. Verify the number of records that were chosen from the filter condition you set by selecting the Preview button.  
   The OT entity details are added for these records, such as OT Device Type and Device Criticality.
5. On the OT Entity Default Configuration tab, fill in the fields.  
   The fields in the following table provide the default values that are added to the OT entity records or the OT-related metadata.{#automatically-convert-it-records-to-ot-devices__table_ntp_yzn_qxb__entry__2}

   | Field | Description |
   |-|-|
   | OT Device Type | Category type that the OT device is classified as. The device type is also the function that the device plays on the OT network. For example, an IT device, such as a server, can be converted to an OT device, and the function it plays on the network is an HMI. Its class is server and its device type is HMI. Note: In some cases, OT devices have no OT function or the device type is unknown. Where the OT devices have no OT function, select No OT Function. Where the OT devices have an unknown device type, select Unknown. |
   | Device Criticality | Measure of the relative risk to the site process if the device fails: * 1 - Most critical * 4 - Not critical {#automatically-convert-it-records-to-ot-devices__ot-assets-form_ul_dxs_jrg_fsb} |
   | Purdue Level | Assigned Purdue level. The level ranges are 0--5. Note: To learn more about the Purdue levels in Industrial Control Systems, see <https://subscription.packtpub.com/book/networking_and_servers/9781788395151/1/ch01lvl1sec10/the-purdue-model-for-industrial-control-systems>. |
   | Zone | Area within the site location that the device is assigned to. |
   | Site | Top-level parent entity, or industrial site, where the device is located or assigned to. |
   [Table 1. OT Entity Default Configuration form]

   {#automatically-convert-it-records-to-ot-devices__table_ntp_yzn_qxb}
6. In the Run field, select a scheduled time for this job to run.
7. Select the check box next to the Active field.
8. Select Submit.

*[\>]: and then