---
sourceDocument: Australia Operational Technology Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/operational-technology
Release :
- australia
ft:locale :
- en-US
ft:publication_title :
- Australia Operational Technology Management
ft:clusterId :
- optm
bundleId :
- optm
workflow :
- Technology
---
# Operational Technology and CSDM tables
# Operational Technology and CSDM tables {#ariaid-title1}
Release version: Australia
Updated March 12, 2026
 5 minutes to read
Summarize
 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 Operational Technology and CSDM tables
Operational Technology (OT) in ServiceNow manages and leverages Common Service Data Model (CSDM) tables to represent and control industrial and production environments.
OT organizes configuration items (CIs) related to industrial control systems, equipment models, and OT system services, providing a structured view of OT infrastructure and processes.
This integration supports multiple ServiceNow products, enhancing operational visibility, security, and management of OT environments.
Show full answer Show less
## Key Features
* **OT Device Management:** OT devices are represented as extended hardware CIs (cmdbciot) with detailed OT-specific attributes such as Purdue Level and device type, stored in the OT Device Details table (cmdbotentity). Each OT device may be represented by multiple records across several tables to capture complex details like multiple IPs or MAC addresses.
* **Equipment Model Entities:** These entities extend the Calculated Application Service class to model industrial process components and sites. Equipment model templates, hierarchical levels (isaentitylevel), and types (isaentitytype) help describe and organize production processes following ISA-95 standards.
* **OT System Services:** These extend Calculated Application Service to define OT system services (e.g., distributed control systems) that manage OT devices and equipment model entities, establishing clear relationships within OT environments.
* **Relationship Types:** Specific CSDM relationship types tailored for OT clarify interactions such as production flow, hierarchy, automation links between devices and equipment, detection by network intrusion systems, and ownership of control modules.
## Integration and Value-Added Products
When combined with other ServiceNow products, OT data empowers enhanced operational capabilities:
* **Discovery for Operational Technology:** Automatically discovers OT devices and enriches them with contextual information like Purdue Level and site details, aiding accurate asset inventory.
* **Industrial Process Manager:** Facilitates linking OT devices to equipment model entities, either manually or through automated subnet mapping, enabling visibility into automation relationships.
* **Operational Technology Vulnerability Response:** Associates vulnerabilities with OT devices and calculates risk based on equipment criticality, streamlining remediation assignments via site-based groups.
* **Incident, Change, Knowledge, and Request Management for OT:** Provides dedicated workflows for OT incidents, changes, knowledge articles, and service requests, supporting site-based access and consistent cross-functional processes.
## Benefits for Other ServiceNow Domains
* **IT Service Management (ITSM):** Gains enhanced context by incorporating OT site and production process information into service records.
* **Information Technology Operations Management (ITOM):** Understands business context and manages OT device hardware and software effectively.
* **Security Operations:** Leverages production context for improved security posture across OT environments.
* **Governance, Risk, and Compliance (GRC):** Uses production process data to scope audits, assess risks, and conduct audit activities with improved accuracy.
* **Asset Management:** Manages lifecycle impacts of OT hardware and software on production processes.
Operational Technology manages and uses CSDM tables. Several ServiceNow products benefit from and add value to Operational Technology.
## CSDM tables managed by Operational Technology {#ot-use-case__section_nwq_wh4_rmb}
There are three primary categories of tables managed by Operational Technology (OT):
* Operational Technology devices: Configuration items found on an OT (ICS or PCN) network.
* ISA equipment model entity: Industrial process automated by OT devices.
* OT system service: Creates other control systems, such as a distributed control system (DCS).
{#ot-use-case__ul_xxl_4s5_x5b}
The numbers in this figure correspond to the CSDM tables managed by Incident Management.
## CSDM tables used by Operational Technology {#ot-use-case__section_a5s_n5r_bvb}
1. OT devices:
1. Configuration Item classes were created for Operational Technology hardware classes (cmdb_ci_ot) by extending hardware. See [Operational Technology (OT) extension classes](https://www.servicenow.com/docs/access?context=cmdb-ci-class-models-operation-technology&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) for details.
2. Any CI Class (any relevant existing hardware class as well as new OT classes can be designated as OT devices by adding OT device details using the OT Device Details (cmdb_ot_entity) reference to the cmdb_ot_entity table. OT Device Details include OT-specific characteristics like Purdue Level and OT device type.
3. OT device types describe the function of any CI that automates an industrial or production process. The cmdb_ot_entity_type table describes these functions or roles.As shown here, a single OT device is represented
by at least two records: one CI and one OT entity record. The device can contain six or more records in up to six tables (for example, if the CI has more than one IP and MAC address).
{#ot-use-case__ol_mwf_55r_bvb}
2. Equipment model entities:
1. The equipment model entity class extends the Calculated Application Service and is used to:
1. Represent the site of any OT device or equipment model entity. A record in the Equipment Model Entity table (cmdb_ci_ot_isa_entity) without a parent is considered a site.
2. Represent the ISA equipment model entity for a part of the production process.
{#ot-use-case__ol_ag5_scs_bvb}
2. You can use equipment model templates (isa_entity_template) to further describe the relationships between equipment model entities found in an industrial environment.
1. Levels (isa_entity_level) describe the hierarchical level of the equipment model entity. For the default ISA-95 template, the levels shown here (area, work center, and work units) are included in the base system.
2. Level types (isa_entity_type) describe the type of process represented by the equipment model entities at a given level. For the default ISA-95 template, the types shown here (process cell, production unit, production line, and storage zone) are included in the base system.
{#ot-use-case__ol_xxn_wcs_bvb}
{#ot-use-case__ol_hsb_qyr_bvb}
3. OT system service:
1. The OT system service class extends the Calculated Application Service and is used to create the OT system service
2. The OT system service can then be associated with equipment model entities.
3. The OT system service can be related to the following items:
* OT devices that are part of the OT system service
* Equipment model entities that the OT system service manages
{#ot-use-case__ul_qpr_cgb_4fc}
{#ot-use-case__ol_zky_f3k_mfc}
{#ot-use-case__ol_oby_s5r_bvb}
CSDM includes relationship types (specific to Operational Technology) that more accurately distinguish how OT devices and equipment model entities relate to each other:
* Producer for::Consumer of: Describes the production process (material flow) between equipment model entities.
* Contains Element::Element of: Describes the hierarchical relationship between equipment model entities.
* Automated by::Automates: Describes the relationship between an OT device and an equipment model entity that the OT device automates.
* Detects::Detected by: Describes which Network Intrusion Detection System (NIDS) class (cmdb_ci_nids) detected an OT device on an OT network.
* Owns::Owned by: Describes the relationship when an OT Control Module is owned by an OT Control System (PLC, DCS, and so on)
{#ot-use-case__ul_s43_nxy_bvb}
The following dependency maps show the relationships between OT devices and equipment model entities:
## Products that add value to Operational Technology {#ot-use-case__section_qnx_5bz_bvb}
When you use OT with any of the following ServiceNow products, you increase the value you get from OT.
Discovery for Operational Technology
: Discovery for Operational Technology provides details about IT-classed hardware and software CIs and can be configured to provide additional OT device context like Purdue Level and Site on a
per-OT schedule basis. Discovery for OT is part of the Operational Technology Manager product.
Industrial Process Manager
: When OT devices are assigned to an equipment model entity, automated by::automates relationships are created between them. This can be done manually in the Industrial
Workspace or using the relationship between OT subnets and equipment model entities using the Automatic Mapping Across Zone-based IP Network Groups (AMAZING) feature in the OT
Subnet Mapping menu item.
Operational Technology Vulnerability Response
: When vulnerable item (VIT) records are created by importing records from an OT-certified integration with a third-party security platform, OT devices are associated with the VIT. This enables both of the following capabilities:
* Risk calculation based on the criticality of the mapped equipment model entity.
* Assignment of VITs to the appropriate local team for remediation via site-based assignment groups.
{#ot-use-case__ul_y1g_qmw_tvb}
Operational Technology Incident Management
: Incident Management for OT runs separately from IT for most OT devices. OT incident records enable site-based access and views to issues that are related to OT devices.
Operational Technology Change Management
: OT change requests enable changes to OT devices or industrial equipment configurations.
Operational Technology Knowledge Management
: Operational Technology Knowledge Management enables you to capture information about your OT system in knowledge articles that are related to OT incidents.
Operational Technology Request Management
: Enables you to access the OT Service Catalog to request OT catalog items and fulfill them based on the defined flows. OT workers can then create and submit an OT request from a catalog item, which helps provide a
consistent experience and facilitates cross-functional requests.
## Products that benefit from Operational Technology {#ot-use-case__section_xhr_gdz_bvb}
IT Service Management (ITSM)
: Services have the context of the site, production process, and OT devices, along with the information and technologies layered beneath them.
Information Technology Operations Management (ITOM)
: Understands the business context for the production processes along with the OT device hardware and software being managed.
Security Operations
: Understands the business context for the production processes as well as OT device hardware and software being secured.
Governance, Risk, and Compliance (GRC)
: Auditors can better leverage production process flows and related Information objects. This helps auditors understand the design-time data sensitivity for scoping audits, measuring risks, and managing audit
activities.
Asset Management
: Manages the impact of the software and hardware life cycle process on the production processes.