--- title: Operational Technology \(OT\) extension classes description: The CMDB CI Class Models app adds or updates classes for Operational Technology \(OT\). locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/servicenow-platform/cmdb-ci-class-models/cmdb-ci-class-models-operation-technology.html release: australia product: CMDB CI Class Models classification: cmdb-ci-class-models topic_type: concept last_updated: "2026-06-18" reading_time_minutes: 30 breadcrumb: [CMDB CI class models, Configuration Management Database \(CMDB\), Configuration Management, Extend ServiceNow AI Platform capabilities] --- # Operational Technology \(OT\) extension classes The CMDB CI Class Models app adds or updates classes for Operational Technology \(OT\). CMDB CI Class Models is a ServiceNow Store app that adds class models that extend the CMDB class hierarchy. The new or updated classes include class descriptions, identification rules, identifier entries, and, if applicable, dependent relationships. You can use the added classes just like any other CMDB class. Applications such as Discovery and Service Mapping Patterns can use the class extensions to populate CIs and discover technologies and software. See the release notes for all CMDB CI class models. ## Operational Technology \(OT\) data model The Operational Technology \(OT\) data model helps manage OT device data. Operational Technology that controls industrial equipment can be based on IT class hardware \(computers, servers, network gear, and so on\), or on specific hardware profiles not included in the ServiceNow IT class model \(PLCs, HMIs, Engineering Workstations, Historians, and so on\). Therefore, a single OT device in the OT data model includes two primary components: 1. A CI class record. This can be an IT or an OT class CI. 2. An OT device details record. This describes the OT device type \(function\) and other OT-specific attributes. Each OT device in the Configuration Management Database \(CMDB\) can be distinguished as having an **OT Device Details** \[cmdb\_ot\_entity\] reference to an OT device details \[cmdb\_ot\_entity table\] record. This is a bi-directional reference. The ot\_device reference on the cmdb\_ot\_entity table references the CI record. If the cmdb\_ot\_entity reference of a given CI record isn't empty, the CI is considered to be an OT device. A record in any CI class can be designated as an OT device. All OT device records include a record in the OT Entity \[cmdb\_ot\_entity\] table to store OT metadata. In the following example, HMI might be software installed on an IT class CI or might be a proprietary appliance similar to a POS device. - An HMI CI with an OT Device detail record describing its **OT Device type** also as HMI. - A computer CI with an OT Device detail record describing its **OT Device type** as HMI. \[Omitted image "ot-asset-ci-class.png"\] Alt text: OT Device records include a record in the cmdb\_ot\_entity table. You can use this to derive a list of HMIs and a list of all computers in an enterprise. For more information about the OT data model, see [Implementing the CSDM framework for Operational Technology](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/ot-use-case-product-view.md). You can use the added classes as any other CMDB class. Products and applications such as Discovery for OT and Service Graph Connector for Microsoft Excel use these class extensions to populate CIs and discover various technologies and software. To learn more, see the following: - [Operational Technology Discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/operational-technology-discovery-landing.md) - [Service Graph Connector for Microsoft Excel](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/service-graph-connector-for-OT-excel.md) **Note:** CIs used on an OT network to automate an industrial process are often referred to as  OT devices. This term shouldn’t be confused with a device record commonly used in Asset Management. ## Operational Technology \(OT\) schema structure​ \[Omitted image "ClassOperationTechnology.png"\] Alt text: Relationships and references in Operational Technology schema. ## Classes This section lists the classes that the CMDB CI Class Models app adds or updates. See the class columns table for further details about the columns added for each class. For the list of classes in the base system, including classes that this app might extend, see [CMDB tables descriptions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/cmdb-tables-details.md). CMDB CI Class Models: Release 1.69.0 adds the following classes for OT.
Class Description
Firmware Installation \[cmdb\_firmware\_install\] Firmware associated with the OT device.
Key Value \[cmdb\_key\_value\] Additional information related to the OT device that's populated with the available OT integrations and captured as Key value pairs.
Software Instance \[cmdb\_sam\_sw\_install\] Captures the software installed on the OT device if Software Asset Management isn't available. **Note:** If Software Asset Management is installed and entitled, the software installed data is available in the Software Installation related list.
CMDB CI Class Models: Release 1.59.0 adds the following classes for OT. |Class|Extends|Description| |-----|-------|-----------| |OT System Service \[cmdb\_ci\_ot\_system\_service\]|cmdb\_ci\_ot\_system|Category of technology and systems that are used to manage, control, and monitor physical processes, machinery, and industrial operations.| CMDB CI Class Models: Release 1.56.0 adds the following classes for OT. |Class|Extends|Description| |-----|-------|-----------| |Quality Inspection Control System \[cmdb\_ci\_ot\_qics\]|cmdb\_ci\_ot\_control|Control systems that assist specifically in quality and inspection functions.| CMDB CI Class Models adds the following classes for OT. |Class|Extends|Description| |-----|-------|-----------| |CNC \[cmdb\_ci\_ot\_cnc\]|cmdb\_ci\_ot\_control|Computer Numerical Control, used for automated control of machining tools such as drills, lathes, mills, and for 3D printers.| |DCS \[cmdb\_ci\_ot\_dcs\]|cmdb\_ci\_ot\_control|Distributed Control System. Achieves control using intelligence distributed about the controlled process, rather than by a centrally located single unit.| |DPU \[cmdb\_ci\_ot\_dpu\]|cmdb\_ci\_ot\_control|Distributed Processing Units. ICS on a dedicated network, with each DPU handling thousands of points of I/O.| |EWS \[cmdb\_ci\_ot\_ews\]|cmdb\_ci\_ot\_supervisory|Engineering Workstation. A computing platform for configuration, maintenance, and diagnostics of ICS applications and other control system equipment.| |Historian \[cmdb\_ci\_ot\_historian\]|cmdb\_ci\_ot\_supervisory|Data Historian. A centralized database supporting data analysis for industrial processes.| |HMI \[cmdb\_ci\_ot\_hmi\]|cmdb\_ci\_ot\_supervisory|Human-Machine Interface. Hardware or software through which an operator interacts with a controller.| |IED \[cmdb\_ci\_ot\_ied\]|cmdb\_ci\_ot\_control|Intelligent Electronic Device. Receives or sends data or control from or to an external source for power grids.| |Industrial Actuator \[cmdb\_ci\_ot\_industrial\_actuator\]|cmdb\_ci\_ot\_field\_device|Component of a machine that moves and controls a mechanism, such as opening a valve.| |Industrial Drive \[cmdb\_ci\_ot\_industrial\_drive\]|cmdb\_ci\_ot\_field\_device|Equipment used to control the speed of machinery. It can be a mechanical electromechanical, hydraulic, or electronic device.| |Industrial 3D Printer \[cmdb\_ci\_ot\_industrial\_3d\_printer\]|cmdb\_ci\_ot\_control|Device used in additive manufacturing for the construction of a three-dimensional object from a CAD model, or a digital 3D model.| |Industrial Robot \[cmdb\_ci\_ot\_industrial\_robot\]|cmdb\_ci\_ot\_field\_device|Robotic system used for manufacturing.| |Industrial Sensor \[cmdb\_ci\_ot\_industrial\_sensor\]|cmdb\_ci\_ot\_field\_device|Sensor device used to monitor the health of equipment.| |Network Gear \[cmdb\_ci\_netgear\]|cmdb\_ci\_hardware|Network gear is an electronic device that is required for communication and interaction between devices on a computer network.| |Operations Technology \[cmdb\_ci\_ot\]|cmdb\_ci\_hardware|Base class for Operational Technology, used for industrial control. For example, in manufacturing.| |OPC Client \[cmdb\_ci\_ot\_opc\_client\]|cmdb\_ci\_ot\_supervisory|Software module that enables applications to acquire data from an OPC Server or conduct supervisory control using an OPC Server.| |OPC Server \[cmdb\_ci\_ot\_opc\_server\]|cmdb\_ci\_ot\_control|Software module that enables applications to provide their data to the outside world using OPC.| |OT Control Module \[cmdb\_ci\_ot\_control\_module\]|cmdb\_ci\_ot\_control|Module such as a PLC or DCS connected to an OT Control System.| |OT Control System \[cmdb\_ci\_ot\_control\]|cmdb\_ci\_ot|Base Class for industrial control systems \(ICS\), usually at Purdue Model Level 1 or 2.| |OT Supervisory System \[cmdb\_ci\_ot\_supervisory\]|cmdb\_ci\_ot|Base class for supervisory systems, usually at Purdue Model Level 2 or 3.| |PLC \[cmdb\_ci\_ot\_plc\]|cmdb\_ci\_ot\_control|Programmable Logic Controller. Used to control OT Devices.| |Protocol Converter \[cmdb\_ci\_protocol\_converter\]|cmdb\_ci\_hardware\_network\_gear|Device used to convert standard or proprietary protocol of one device to the protocol suitable for the other device or tools to achieve the interoperability.| |RTU \[cmdb\_ci\_ot\_rtu\]|cmdb\_ci\_ot\_control|Remote Terminal Unit. Special purpose data acquisition and control unit that supports DCS and SCADA remote stations.| |SCADA Client \[cmdb\_ci\_ot\_scada\_client\]|cmdb\_ci\_ot\_supervisory|Supervisory Control and Data Acquisition. Client that enables an operator to manage a SCADA server.| |SCADA Server \[cmdb\_ci\_ot\_scada\_server\]|cmdb\_ci\_ot\_control|Supervisory Control and Data Acquisition. System capable of gathering and processing data and applying operational controls over long distance.| ## Class columns CMDB CI Class Models adds the following columns to the respective classes. |Added columns|Description| |-------------|-----------| |firmware\_version|​Firmware version reported by discovery source.| |hardware\_version|​Hardware version reported by discovery source.| |Added columns|Description| |-------------|-----------| |has\_module|​True or false value describing if the system has modules, such as chassis / blade architecture.| |backplane\_name|System-reported string name or number for the backplane.| |backplane\_id|System-reported unique ID for the backplane| |Added columns|Description| |-------------|-----------| |slot\_number|Reported slot in the control system this module is using.| |module\_type|Module type reported by the discovery source.| |Added columns|Description| |-------------|-----------| |device\_type|List that describes if the device provides input, output, or both to the parent control system.| |Added columns|Description| |-------------|-----------| |display\_name|Name of the OT system.| |isa\_entity\_site|Site where the OT system is located.| ## Form view All OT extension classes have a default form view that includes the **OT Device Details** attribute at the top of the form. The following table lists the other classes that have the **Operational Technology \(OT\)** view on their form context menu. This is the default form view for users with the cmdb\_ot\_viewer role for the following classes. |Class|Description| |-----|-----------| |base hardware \[cmdb\_ci\_hardware\]|Base class for hardware.| |base computer \[cmdb\_ci\_computer\]|An extension of the Hardware table, capturing computer properties.| |base server \[cmdb\_ci\_server\]|Base class for all types of servers.| |linux server \[cmdb\_ci\_linux\_server\]|Server running Linux software.| |windows server \[cmdb\_ci\_win\_server\]|A server running Microsoft Windows Server operating system.| |IoT Device base class \[cmdb\_ci\_iot\]|Parent table that contains Internet of Things \(IoT\) device types.| |IP Firewall and extended classes \[cmdb\_ci\_ip\_firewall\]|Contains all network firewalls.| |IP Router \[cmdb\_ci\_ip\_router\]|Specialization of the Network Gear \[cmdb\_ci\_netgear\] table.| |IP Switch \[cmdb\_ci\_ip\_switch\]|Specialization of the Network Gear \[cmdb\_ci\_netgear\] table.| |Protocol Converter \[cmdb\_ci\_protocol\_converter\]|Device used to convert standard or proprietary protocol of one device to the protocol suitable for the other device or tools to achieve the interoperability.| Classes not included in the table don't have the OT view by default. For any additional classes required, you can add the Operational Technology \(OT\) view to the form context menu. For more information about form context menu options, see [Form context menu](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/c_FormContextMenu.md). ## Roles and Access Control Logic \(ACLs\) The following roles are associated with the OT \[cmdb\_ci\_ot\] classes and associated tables that follow: - **Admin \(cmdb\_ot\_admin\)** Can create, read, update, and delete OT records. Can edit the OT Device Type on the OT Device form and manage specific configurations on the OT entity tables. Can't edit or delete IT CI records in related tables \(for example, IP Address or Network Adapter\). - **Editor \(cmdb\_ot\_editor\)** - Can create, read, update, and delete OT device records. Cannot edit or delete IT CI records in related tables. For example, IP Address or Network Adapter. - When the OT Enhanced Access Control plugin is enabled, edit or delete access to OT devices. The cmdb\_ot\_editor role should be granted only if the user meets the Can Edit Equipment Model User Criteria for the site referenced by the device. - Can create, update, or delete cmdb\_rel\_ci records only if they have access to either the record’s parent reference CI or its child reference CI. - **Viewer \(cmdb\_ot\_viewer\)** Can read OT device records. **Note:** For the cmdb\_ci\_ot and cmdb\_ot\_entity tables: - OT users must have one of these three OT roles to view OT devices. - IT users with an assigned itil role are restricted from viewing OT devices in the cmdb\_ci\_ot table, and records in the cmdb\_ot\_entity table. IT users are still able to see IT asset classes, such as Computer, Installed Software. OT users can restrict access to OT devices from users with an IT \(itil\) only role, including both a viewer role and an admin role. ## Key relationship structures Use the following key relationships when creating OT CIs: **OT Entity** Since any CI class may be found on an OT network, the OT Entity \[cmdb\_ot\_entity\] table captures additional attributes required in an OT environment:
Attribute Description
Business criticality Business criticality assigned in the discovery source.
OT Device Reference to the CI that is on the OT network.
OT Device type The function of the OT Device, regardless of CI class.- For a dedicated HMI appliance, the CI is in the cmdb\_ci\_ot\_hmi class, and the OT Device type should be HMI. - For a computer performing the function of an HMI, the CI is in the cmdb\_ci\_computer class and the OT Device type should be HMI
Purdue level Purdue level of the OT Device.
Zone Zone assigned to the OT Device, usually used in the context of a zone or conduit model.
IRE criterion attribute \(ire\_criterion\) Acts as a criterion attribute for an OT entity-related entry.
The OT Entity is a related list added to the Operational Technology \(OT\) \[cmdb\_ci\_ot\] table and extended tables. If you want to view OT entity metadata on an existing CI class, first add the related list to the form. **OT Entity Type** The OT Entity Type \[cmdb\_ot\_entity\_type\] table tracks the type of OT Device that an OT or non-OT CI is performing the function of. It is a necessary part of the Purdue level data model and extends the Application File \[sys\_metadata\] table. The ServiceNow AI Platform includes records representing common OT Device types of OT Device CIs. The OT Entity Type table attributes include: |Attribute|Description| |---------|-----------| |Label|Display name of a specific OT Device type.| |Name|Value used to identify a specific OT Device type.| |OT table|Value used for auto-populating the Type field for the OT entity record \[cmdb\_ot\_entity\] of an OT Class CI.| |Parent|Parent type of a specific type, which is a reference to a record in the same table \[cmdb\_ot\_entity\_type\].| **OT Class Mapping Template** The OT Class Mapping Template \[ot\_class\_mapping\_template\] table extends the Application File \[sys\_metadata\]. It's used by OT Service Graph Connectors \(SGCs\) to classify a device into the correct CI class based on the source data. Each SGC can extend the OT Class Mapping Template table and create a child class in the SGC application. Doing so defines the device classification details that are specific to SGC. For example, the Excel SGC Class Mapping \[excel\_sgc\_class\_mapping\] table is a child of the OT Class Mapping Template created in the Service Graph Connector for Microsoft Excel application scope, which stores the classification details specific for the Service Graph Connector for Microsoft Excel. **Note:** The OT Class Mapping Template doesn't store any classification detail records. The child tables specific to each SGC store the classification records for an SGC to use. With the template, you can also use the OT device naming strategy. An extension point is created in the Industrial Core plugin with the default device naming strategy, which is the device name and site name. For more information about the Industrial Core plugin, see [Industrial Core plugin](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/industrial-core-plugin.md). To implement the device naming strategy, you must do the following. - Identify the required naming strategies per device class and the available data for naming. - Implement naming strategies by creating script includes that implement the extension point's function. For more information about how to implement the device naming strategy, see the **Creating and using the OT device naming strategy** section in [Industrial Core plugin](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/industrial-core-plugin.md). The OT Class Mapping Template table attributes include:
Attribute Description
Source Class The class of the source CI.
Target CMDB class The expected ServiceNow class that for the CI.
OT Device type The 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. Therefore, its class is **server** and its Device type is **HMI**. **Note:** In some cases, there are OT Devices with no OT function or OT Devices where the Device type is unknown. For OT Devices with no OT function, select **No OT Function**. For OT Devices where the Device type is unknown, select **Unknown**.
Allow OS classification When set to **True**, if an operating system is found on the CI, the target is switched away from this table's target class to a ServiceNow class that matches its OS.For example, if Historian is the target class but Windows Server OS is found in the payload, the CI is classified as a Windows Server CI. And its OT device type is set to Historian.
Active When selected, the class mapping is set to **Active** and considered during device classification.
Allow Custom Device Naming When this field is enabled, you can define how the unique device names are generated for the **Device Naming Strategy** field.
Device Naming Strategy Defines the method used to generate unique device names when the **Allow Custom Device Naming** field is enabled.
**Serial number** During CI identification, the Identification and Reconciliation Engine \(IRE\) processes search for a serial number in two locations. One is the CI serial number attribute, and the other is the Serial Number \[cmdb\_serial\_number\] table, with reference back to the Operational Technology \(OT\) \[cmdb\_ci\_ot\] table. - It stores any serial number of any type other than system serial number, and only in the Serial Number table \(and not in the server CI attribute\). - If the system serial number is available, it stores it in both the Serial Number attribute of the CI and in the Serial Number table. - The Serial Number table is a many-to-one relationship, linking back to the Operational Technology \(OT\) CI. This table has a Type field for specifying the type of the serial number. - For Operational Technology \(OT\), use the string value **system** for the serial number type to promote proper reconciliation across various sources. **Network adapter** Use the Network Adapter \[cmdb\_ci\_network\_adapter\] class to store network adapters. 1. Set the MAC Address attribute to be the MAC address value. - Format the string with colon separators between octets and lower case hexadecimal characters with padded zeros. - For example, 'f8:f2:1e:00:d4:66'. 2. Set the Name attribute in the Network Adapter class to be the same as the MAC Address. 3. In the CI Relationship \[cmdb\_rel\_ci\] table, create an Owned By:Owns relationship to the associated Hardware CI. 4. Using the CI with a reference to the associated Hardware CI, specify a reference from the Network Adapter \[cmdb\_ci\_network\_adapter\] table. **IP Address** Use the IP Address \[cmdb\_ci\_ip\_address\] class to store IP addresses. 1. Store an IP address value in the IP Address attribute, and in the Name attribute to avoid empty Name attributes. - Store an IPv4 IP address value using the format 'NNN.NNN.NNN.NNN', with decimal-based octets and period separators. Non-conforming values should be considered invalid and cleansed to null values. - Store an IPv6 IP address value using lower case hexadecimal with colon separators. Non-confirming values should be considered invalid and cleansed to null values. 2. Set the Netmask attribute to the IP address. 3. Set the Network Partition Identifier attribute. 4. Set the Name attribute in the Network Adapter class to be the same as the MAC Address. 5. In the CI Relationship \[cmdb\_rel\_ci\] table, create an Owned By::Owns relationship to the associated Hardware CI. 6. For the IP address, specify a reference to the Network Adapter \[cmdb\_ci\_network\_adapter\] table, using the CI with a reference to the associated Hardware CI. 7. To promote that base-system identification rules work properly, also store the IP address in the associated Network Adapter class. **Network adapter and IP address** Use the IP Address \[cmdb\_ci\_ip\_address\] class to store IP addresses. 1. Store the MAC address of the network adapter installed on a server, in the Network Adapter \[cmdb\_ci\_network\_adapter\] class. 2. Store the IP address in the IP Address \[cmdb\_ci\_ip\_address\] class. **Note:** Don't store the MAC address or the IP address in the Operational Technology \(OT\) \[cmdb\_ci\_ot\] table. The default Operational Technology \(OT\) form is configured to display the IP address from the Network Adapter table. **Backup Storage Information** Use the Backup Storage Information \[cmdb\_backup\_storage\_information\] class to create backup records that identify the device in internal or external backup services. The Backup Storage Information table includes the following attributes: |Attributes|Description| |----------|-----------| |Backup Configuration Status|Indicates whether the CI has been configured in the backup service or appliance with relevant policies.| |Discovery Source|Discovery source of the backup record.| |Backup Service|Reference to the Common Service Data Model Technical Service hosting external and internal backup system, services, or appliances| |Managed By|Email ID of the user responsible for managing the backup.| |Latest Successful Execution|Date and time of the most recent data backup that was successfully executed for a device.| |Latest Execution Attempt|Date and time of the most recent data backup that was attempted for a device.| |Next Execution Attempt|Date and time when the next data backup is going to be attempted for a device.| |Latest Execution Log|Detailed log entries for all device data backup that were executed.| |Backup Source ID|Backup service record for a device, which identifies the device in external or internal backup services. Backup source id can include host\_id, vcenter\_id, instance\_id, db\_id.| |Job Definition ID|Identification number assigned to a data backup job.| |Recovery Point Objective|Amount of time that can elapse between backups and the amount of data lost.| |Execution Mode|Indicates whether the backup is configured to run automatically on a periodic basis, or if it is manually executed on an as-needed basis.| |Backup Source|Details of the backed up CI. This table holds the backup status details for the referenced CI.| |Job Definition Name|Name assigned to a data backup job.| |Managed By Group|Primary support group responsible for managing the backup.| |Domain|ID of the domain to which the instance belongs.| Use the Backup Job Execution History \[cmdb\_backup\_job\_execution\_history\] class to create a history of records for all backup executions. The Backup Job Execution History table includes the following attributes: |Attributes|Description| |----------|-----------| |Backup Job Information|Details of the backup job you created.| |Backup End Time|The time when the backup job ended.| |Completion Status|The current completion status of the backup job.| |Mark for Archival|Select to archive backup job execution history after 90 days.| For more information, see [Operational Technology Backup Management data model](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/ot-backup-management-data-model.md). ## Key reference structures Use the following key references when creating Operational Technology \(OT\) records: - When creating computer or server records for OT Devices that are running on computers or servers, see the following topics: - [Computer \[cmdb\_ci\_computer\] class](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/class-computer.md) - [Server \[cmdb\_ci\_server\] class](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/class-server.md) - The Manufacturer and Model ID attributes are reference attributes to the Company \[core\_company\] and Product Model \[cmdb\_model\] tables respectively. - The Owned By, Assigned To, Managed By, and Supported By attributes are reference attributes to the User \[sys\_user\] table. The Change Group and Support Group attributes are reference attributes to the Group \[sys\_user\_group\] table. ## Identification rules The ServiceNow AI Platform contains a predefined identification rule for the Operational Technology \(OT\) classes. That identification rule has the following key identifier entries, listed in priority order: 1. Identifier entry that uses the identification specified in Serial Number \[cmdb\_serial\_number\] as the lookup table. The Serial Number table is a many-to-one reference from the serial number back to the server CI​. Optional conditions to filter the records during identification and reconciliation. **Note:** For lookup identification rules, you must complete the mandatory conditions under **Advanced Configuration**. 2. Identifier entry that is specified in the Serial Number attribute in the CI. 3. Identifier entry that is specified in the Mac Address attribute in the Network Adapter table. Optional conditions to filter the records during identification and reconciliation. 4. Identifier entry for the Name attribute. - If Serial Number and MAC Address aren't available, then the Name \(which is usually the system reported hostname\) attribute is used. - If both Serial Number and Name aren't available, and only MAC Address is available, use MAC Address as the name of the CI. Using the MAC Address as the name of the CI helps to ensure that you don't create an empty CI. 5. Identifier entry that uses a product instance identifier \(PID\) on the CI. **Note:** To learn more, see [CMDB Identification and Reconciliation \(IRE\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/c_CMDBIdentifyandReconcile.md). **Reclassifying IT devices on your OT network** Beginning with the Xanadu release, you can create a Network Adapter identifier on the OT identification rule to reclassify IT devices on your OT network. Creating a Network Adapter identifier on the OT identification rule overwrites the Hardware identification rule's Network Adapter identifier entry. To do this, complete the following actions: 1. Navigate to **All** > **Configuration** > **CI Class Manager**. 2. Under **Hardware** in the **CI Classes** menu, select the **Operational Technology \(OT\)** class. 3. Under the **Class Info** menu, select **Identification Rule**. 4. Under **Identifier Entries**, select **Add**. 5. In the New Identifier Entry pop-up dialog box, choose **Use attributes from another table \(Lookup table\)** and select **Next**. 6. In the Create Identifier Entry dialog box, complete the following steps: 1. Select **Hardware table** from **Search On Table** drop-down list. 2. Enter **400** in the **Priority** field. 3. Select **Network Adapter** from the **LookUP Table** from drop-down list. 4. Select **Mac Address** from the **Criterion Attributes** drop-down list. 5. Select **Save**. **Note:** IT devices on an OT network aren't reclassified automatically. If you want to automatically reclassify IT devices to OT, you must upgrade to Xanadu or the latest ServiceNow AI Platform version with the latest CMDB CI Class Models. ## Related entries Related entries for OT identification rules enable OT Service Graph Connectors to create related records, such as OT Device records, backup records, and so on. The Operational Technology \[cmdb\_ci\_ot\] class rule contains the following related entries: - Backup Storage Information \[cmdb\_backup\_storage\_information\] - External system metadata \[cmdb\_key\_value\_v2\] - OT Device \[cmdb\_ot\_entity\] - Firmware Installation \[cmdb\_firmware\_install\] - Key Value \[cmdb\_key\_value\] - Software Instance \[cmdb\_software\_instance\] The OT Control Module \[cmdb\_ci\_ot\_control\_module\] rule contains the following related entries: - Backup Storage Information \[cmdb\_backup\_storage\_information\] - OT Device \[cmdb\_ot\_entity\] - Firmware Installation \[cmdb\_firmware\_install\] - Key Value \[cmdb\_key\_value\] - Software Instance \[cmdb\_software\_instance\] ## OT Device Network Connection data model The OT Device Network Connection data model uses the OT Device Network Connection \[sn\_ot\_device\_network\_connection\] table to identify source CIs and destination CIs. Identifying this data allows you to identify the device-to-device connections in your OT environment. **Note:** The OT Device Network Connection table is available with the Industrial Core plugin. For more information about the Industrial Core plugin, see [Industrial Core plugin](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/operational-technology/industrial-core-plugin.md). The OT Device Network Connection \[sn\_ot\_device\_network\_connection\] table references the CI relationships \[cmdb\_rel\_ci\] table with the Connects to :: Connected by relationship type. The device-to-device connections in CI relationships and the metadata of how the source and destination communicate are stored. **Note:** This data is populated with the available OT integrations and can't be manually created. The OT Device Network Connection table is populated using data from the following CMDB tables. **Note:** The OT Device Network Connection data model also includes a performance script that helps map IP addresses to managed networks and subnets, and creates records in each table. **Allocated IP Address \[cmdb\_ci\_allocated\_ip\_address\]** The following attributes in the Allocated IP Address \[cmdb\_ci\_allocated\_ip\_address\] table are populated by collected data: |Attribute label|Attribute name| |---------------|--------------| |IP Address|ip\_address| |Managed Network|managed\_network| |Is Broadcast|is\_broadcast| |Is Conflict|is\_conflict| |Is DHCP|is\_dhcp| |Is DNS|is\_dns| |Is Managed|is\_managed| |Is Reserved|is\_reserved| |Name|name| **IP Network Subnet \[cmdb\_ci\_ip\_network\_subnet\]** The following attributes in the IP Network Subnet \[cmdb\_ci\_ip\_network\_subnet\] table are populated by collected data: |Attribute label|Attribute name| |---------------|--------------| |Name|name| |Parent Pool|parent\_pool| |CIDR|cidr| |Managed Network|managed\_network| **Managed Network \[cmdb\_ci\_managed\_network\]** The following attributes in the Managed Network \[cmdb\_ci\_managed\_network\] table are populated by collected data: |Attribute label|Attribute name| |---------------|--------------| |Name|name| |Contained by CI|contained\_by\_ci| **** The OT Device Network Connection table also uses the following Identification Reconciliation Engine \(IRE\) rule. The IRE rule on the OT Device Network Connection table can help Service Graph Connectors align with a standardized way to create connection records. - Identifier name: OT Device Network Connection - Applies to: sn\_ot\_device\_network\_connection - Independent: true - Identifier entries: - Source IP Address - Destination IP Address - Destination Port - Source Managed Network - Destination Managed Network ## Checking the MID Server status The OT Service Graph Connectors require a connection to a MID Server to communicate with the external applications. The SGOTTroubleShootHelper \[sn\_cmdb\_ci\_class.SGOTTroubleShootHelper\] script validates the MID Server status and verifies the following cases. - The MID Server is up and running. - The MID Server is validated. - The MID Server user is assigned the mid\_server role. - The MID Server has a value in the ip\_address attribute. The SGOTTroubleShootHelper script includes the validateMIDSelection function, which contains the MID Server checks for the OT Service Graph Connectors. The following table describes the use cases for the validateMIDSelection function and the return messages you may see based on the outcome.
Use Case Message
The Connection and Credential Alias sys\_ids are missing, so the validation can't proceed. Provide Connection and Credential Alias sys\_id.
A Connection and Credential Alias aren't found for the sys\_id. No Connection and Credential Alias Found for the sys\_id.
The connection isn't configured to use a MID Server, so validation is skipped. Invalid MID selection choice for the Connection associated with the specified Connection and Credential Alias named\{Connection name\}
There's an invalid MID Server selection choice for the connection. Invalid MID selection choice for the HTTP connection associated with the specified Connection and Credential Alias named \{Connection name\}
The MID Server validation fails due to an error. Error occurred during MID Server selection validation: \{Error\}
The query for getting the associated username and its associated user account sys\_id based on the MID Server sys\_id.
The MID Server sys\_id is missing from the input, so validation can't proceed. Provide MID Server sys\_id.
If the username isn't populated in the mid.instance.username parameter. MID Server username is empty in mid.instance.username configuration parameter.
The MID Server username configuration parameter is missing for the specified MID Server. No mid.instance.username configuration parameter found for the MID Server with sys\_id: \{midServerId\}
**The query used to get the mid\_server user sys\_id based on the username.**
A user record isn't found for your given username. No user found for username: \{username\}
The MID Server username is found successfully. User found for username: \{username\}
Your sys\_id or username can't be retrieved due to an error. Exception occurred while fetching MID Server username or user sys\_id: \{error\}
A query runs to check that you're assigned the mid\_server role.
Your sys\_id is missing, so role validation can't proceed. The MID Server role validation failed as user is not found.
You aren't assigned the mid\_server role. The MID Server User does not have 'mid\_server' role.
The MID Server user is assigned the mid\_server role. The MID Server User has 'mid\_server' role.
The MID Server user role can't be checked because of an error. Error occurred while checking MID Server user role: \{error\}
The IP address, Running status, and Validation status are under validation.
The MID Server sys\_id is missing from the input, so validation can't proceed. Provide MID Server sys\_id.
The MID Server record is missing from the ServiceNow system. No MID Server record found for sys\_id:\{midServerId\}
The MID Server's IP address isn't set, so it can't be used for connections. IP Address field is not populated for the MID Server.
The MID Server isn't running. MID Server status is not 'Up'.
The MID Server isn't validated. MID Server is not validated.
The MID Server is active and validated. MID Server is active and validated.
The MID Server failed due to an error. Error occurred while validating MID Server status and IP address: \{error\}
You select a specific MID Server.
The Connection and Credential Alias details aren't found as part of the input parameter. No Connection and Credential Alias found for the sys\_id.
A MID Server isn't selected for the Connection. No MID Server selected for the Connection: \{connectionName\}
A MID Server agent record isn't found for the selected MID Server in the HTTP Connection. No MID Server agent record found for sys\_id:\{midServerId\}
All MID Server validation checks are successful. MID Server with name \{midServerName\} is validated and running.
The MID Server validation failed for the selected MID Server. The final message only includes the failed validation checks, separated by a new line. Validation checks failed for following MID Servers with reasons 1.Old Crucible MID Server \(153.113\): No mid.instance.username configuration parameter found for the MID Server with sys\_id: fc4a4cfe3b6f22909b96dfd0c5e45a6c Unable to retrieve the MID Server user sys\_id because the specified MID Server username is not found MID Server Role validation failed User sys\_id is null IP Address field is not populated for the MID Server MID Server status is not 'Up'
The MID Server validation failed due to an error. Error occurred during specific MID Server validation: \{error\}
The **Auto Select MID Server** field is selected.
The Connection and Credential Alias details aren't found as part of the input parameter. No Connection and Credential Alias found for the sys\_id.
A validated and running MID Server isn't found for the Connection.This excludes the role and ip\_address validation checks. No validated and running MID Server found for Connection:\{connectionName\}
The MID Server is running, validated, and passes all validation checks. Following MID Servers are in a running and validated state: with running and validated state: 1. \{midServerName\} MID Server is active and validated.
The MID Server validation failed for the selected MID Server. The final message only includes the failed validation checks, separated by a new line. Validation checks failed for following MID Servers with reasons 1.Old Crucible MID Server \(153.113\): No mid.instance.username configuration parameter found for the MID Server with sys\_id: fc4a4cfe3b6f22909b96dfd0c5e45a6c Unable to retrieve the MID Server user sys\_id because the specified MID Server username is not found MID Server role validation failed, user sys\_id is null IP Address field is not populated for the MID Server MID Server status is not 'Up'
The MID Server validation failed due to an error. Error occurred during auto-select MID Server validation: \{error\}
You select a specific MID Server cluster.
The Connection and Credential Alias details aren't found as part of the input parameter. No Connection and Credential Alias found for the sys\_id.
A MID Server cluster isn't associated with the Connection. No MID Cluster associated with the Connection:\{connectionName\}
A MID Server isn't associated with the MID Server cluster. No MID Server is associated with the MID cluster referenced to the Connection: \{connectionName\}
The MID Server is running, validated, and passes all validation checks. Following MID Servers associated with MID Cluster are in running and validated state: 1. \{midServerName\} MID Server is active and validated.
The MID Server validation failed for the selected MID Server. The final message only includes the failed validation checks, separated by commas. Validation checks failed for following MID Servers with reasons 1.Old Crucible MID Server \(153.113\): No mid.instance.username configuration parameter found for the MID Server with sys\_id: fc4a4cfe3b6f22909b96dfd0c5e45a6c Unable to retrieve the MID Server user sys\_id because the specified MID Server username is not found MID Server role validation failed User sys\_id is null IP Address field is not populated for the MID Server MID Server status is not 'Up'
The MID Server validation failed due to an error. Error occurred during MID Server cluster validation:\{error\}
## Deprecated classes CMDB CI Class Models: Release 1.30 soft deprecated \(not removed, but marked as follows\) with the release of the OT class model: |Class|Description| |-----|-----------| |Human Machine Interface \[cmdb\_ci\_hmi\]|OT Devices moved to cmdb\_ci\_ot to support broader use cases. Use cmdb\_ci\_ot\_hmi instead.| |Manufacturing Device \[cmdb\_ci\_manufacturing\]|OT Devices moved to cmdb\_ci\_ot to support broader use cases. Use cmdb\_ci\_ot as the base class or other generic child classes as appropriate.| |Programmable Logic Controller \[cmdb\_ci\_plc\]|OT Devices moved to cmdb\_ci\_ot to support broader use cases. Use cmdb\_ci\_ot\_plc instead.| A script has been provided to migrate records from these classes to the new class tables. The admin role is required to perform the following tasks: 1. Navigate to **System Definition** > **Script Includes** 2. Find the record named **OTDevicesMigrationUtils**. 3. Navigate to **Definition** > **Script Includes** > **.** 4. In the background window, copy and paste the provided script. 5. Select the appropriate scope and run the script. ## Resolving issues Tips: |Problem|Suggested resolution| |-------|--------------------| |Unable to see OT Device menu items|Confirm that the logged in user has been assigned the appropriate roles. To learn more, see the preceding Roles section.| |Error creating or updating an OT Device record|Provide only one OT Device record \(cmdb\_ot\_entity\) per CI.| ## Request apps on the Store Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html). The [CMDB CI Class Models app](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/cmdb-ci-class-models/cmdb-ci-class-models.md) app adds class models that extend the CMDB class hierarchy, including: - Class descriptions - Identification rules - Identifier entries - Dependent relationships, if applicable. **Related topics** [CMDB schema model](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/c_ConfigurationManagementDatabase.md)