--- 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 --- # Automated Mapping Across Zone-based IP Network Groups # Automated Mapping Across Zone-based IP Network Groups {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Automated Mapping Across Zone-based IP Network Groups The Automated Mapping Across Zone-based IP Network Groups (AMAZING) feature enables ServiceNow customers to automate the mapping of Operational Technology (OT) devices to production process equipment model entities. This automation is critical for OT managers to prioritize vulnerabilities and workflows by understanding how OT devices connect to the production processes they support. AMAZING uses IP subnet data to establish device-to-process relationships, minimizing ambiguity especially in environments where private IP ranges are reused across multiple sites. Show full answer Show less ## Key Features * **Automated Mapping:** Automatically assigns OT devices to ISA equipment model entities based on device IP addresses and OT subnets imported from authoritative sources like NetDB or Firewalls. * **Support for Subnet Types:** Supports mapping by IP network subsets, IP ranges in CIDR notation, and discovered subnets, with discovered subnet mapping supporting copy-paste networks to resolve device identification challenges. * **Discovered Subnet Utilization:** Leverages discovered subnets stored in the OT Discovered Subnets table to uniquely identify OT devices, even in complex network configurations where subnet ranges are shared by multiple equipment entities. * **Integration with ServiceNow Tables:** Uses IP address details (Netmask and Network partition identifier) stored in the cmdbciipaddress table to accurately determine subnet matches for mapping. * **Personas and Roles:** Supports system administrators, ISA administrators, and ISA editors with distinct responsibilities including data import, scheduling mapping flows, triggering mapping actions, and managing subnet mappings. * **Plugin Requirements:** Requires the Operational Technology Manager, Industrial Process Manager, and Industrial Core plugins to activate and utilize the mapping capabilities. * **Guided Setup and Workflows:** Provides guided setup within Industrial Process Manager for configuring automated mapping flows, managing OT discovered subnets, and triggering mapping processes. ## Practical Use and Benefits * **Enhanced Visibility:** Enables OT managers to view device-to-process relationships automatically, aiding in risk prioritization and operational decision-making. * **Accurate Device Identification:** Helps resolve ambiguities in identifying OT devices in copy-paste networks by using discovered subnet data to uniquely map devices. * **Efficient Management:** Automates and simplifies the assignment of OT devices to production equipment models, reducing manual effort and errors. * **Comprehensive Monitoring:** Allows users to view lists of unmapped OT devices, devices not assigned to sites, and OT subnet mappings for ongoing management and troubleshooting. * **Scalability:** Supports site-level subnet mapping, although multiple subnets of the same range within a single site are not supported, recommending manual mapping in those cases. ## Next Steps for ServiceNow Customers * Ensure required plugins (Operational Technology Manager, Industrial Process Manager, Industrial Core) are installed. * Use the guided setup in Industrial Process Manager to configure OT subnet mappings and automated mapping flows. * Import OT subnet data from authoritative sources to populate the OT subnet to Equipment Model Entity Mapping table. * Create or manage discovered subnets to improve mapping accuracy, especially in networks with overlapping IP ranges. * Utilize role-based actions to trigger and manage automated mapping and to review mapping statuses across OT devices and subnets. Automate mapping of Operational Technology (OT) devices to the production process using the Automated Mapping Across Zone-based IP Network Groups (AMAZING) feature.​ When OT managers experience vulnerabilities or must manage workflow involving OT devices, the context of how the OT device connects to the production process it automates is critical to prioritizing work.  Automatic mapping of OT devices to ISA equipment model entities enables the view of device-to-process relationships. Note: Only one subnet range according to site is supported. Two different sites can have the same subnet; for example, 192.168.101.0/24. But multiple subnets of the same range are not supported for the same site. It is recommended that you use manual mapping in this scenario. ## Key benefits {#automate-mappings-between-ot-assets-and-equipment-model-entity__section_ufr_fpp_mtb} * Upload and store OT subnets from authoritative sources (such as NetDB or Firewalls) as records in a ServiceNow instance. * Automate assignment of OT devices to ISA entity using IP addresses and OT subnet. * Minimize issues with reuse of private IP address ranges across multiple sites. * Use discovered subnets in copy-paste networks to help uniquely identify OT devices for mapping. {#automate-mappings-between-ot-assets-and-equipment-model-entity__ul_pg5_wjx_ktb} Industrial networks use subnets to divide the private IP address space with a single subnet often aligned to a part of the production process, or the equipment model entity. For example, a canning line runs on a 192.168.101.0/24 network in which all the equipment was programmed by the integrator. The IPs used by the control systems, or OT devices, are often hard-coded into the automation software used to run the line. If the subnet maps to the canning line in the Atlanta site, a manager can automatically map a detected PLC with IP 192.168.101.66 to the canning line. The mapping feature relates each subnet to an equipment model entity, enabling you to automatically map OT devices to the subnets associated with the equipment model entity based on the IP address that was reported upon import from an OT-certified integration or ServiceNow®'s [IT Discovery for Operational Technology (OT) Networks](https://www.servicenow.com/docs/M4bta4oyl05YoQUlCa06nA "You can use the IT Discovery for Operational Technology (OT) Networks function to discover IT class OT devices. These devices are located in designated Purdue levels within your Industrial Control System (ICS) networks. IT class items include switches, routers, and computers that exist both in data centers and in your factories.").​ ## Types of mapping {#automate-mappings-between-ot-assets-and-equipment-model-entity__section_tn2_2p2_h3c} The following types of mapping are supported in the AMAZING feature.{#automate-mappings-between-ot-assets-and-equipment-model-entity__table_ugv_pp2_h3c__entry__2} | Type | Description | |-|-| | IP Network | Subset of IP addresses in a subnet. Note: IP network mapping isn't supported in a copy-paste network. | | IP Range | Entire subnet, in CIDR notation Note: IP range mapping isn't supported in a copy-paste network. | | Discovered Subnet | Discovered subnet in your OT network. Note: Discovered subnet mapping is supported in a copy-paste network. | [Table 1. AMAZING mapping types] {#automate-mappings-between-ot-assets-and-equipment-model-entity__table_ugv_pp2_h3c} ## Using discovered subnets to uniquely identify devices {#automate-mappings-between-ot-assets-and-equipment-model-entity__section_b3j_w32_h3c} Copy-paste networks can make it difficult to uniquely identify OT devices and correctly map them to their equipment model entities. At some sites the same IP subnet range may be used for multiple equipment model entities, which can result in ambiguity about where to map your OT device. To more accurately map an OT device to its equipment model entity, you can configure the discovered subnet to identify the unique device and which equipment model entity it should be mapped to. By using discovered subnets with the AMAZING feature, you can uniquely identify OT devices in a copy-paste network. The logic is as follows: 1. When OT device data is populated from a Service Graph Connector, the subnet and managed network must be populated in the IP Address \[cmdb_ci_ip_address\] table using the Netmask and Network partition identifier fields. The Network partition identifier field is important to the mapping process because it's always unique to an OT device. 2. The Discovered subnet and Managed network fields must also be populated in the OT device data for mapping to continue. {#automate-mappings-between-ot-assets-and-equipment-model-entity__ol_wvf_kk2_h3c} The AMAZING feature retrieves all configuration items (CIs) associated with a particular site. The IP address details, including the Netmask and Network partition ID fields, are obtained. Using the IP address details, the feature determines the discovered subnet then checks if the selected subnet and the managed network match the discovered subnet. If a match is found, the Automated by :: Automates relationship is established between the CI and the equipment model entity to effectively map the OT device to the correct entity. The discovered subnets live in the OT Discovered Subnets \[sn_ot_discovered_subnet\] table available with the Industrial Core. This table leverages the following attributes to help refine OT device mapping accuracy: * CIDR * Discovered Managed Network * Site {#automate-mappings-between-ot-assets-and-equipment-model-entity__ul_upp_jj3_g3c} For more information about Industrial Core, see [Industrial Core plugin](https://www.servicenow.com/docs/LysP4jjvdLP8BS_zs5NEgA "The Industrial Core plugin contains the class mappings needed for the Operational Technology (OT) certified Service Graph Connectors."). You can also manually create a discovered subnet. For more information, see the [Create an OT discovered subnet](https://www.servicenow.com/docs/V0BWAWddA2tK_mich7WeCA "Create an Operational Technology (OT) discovered subnet to use during OT subnet mapping to help identify OT devices and assign them to the correct equipment model entity."). ## Automated mapping feature personas {#automate-mappings-between-ot-assets-and-equipment-model-entity__section_m41_drw_mtb} The automated mapping feature is aimed at the following personas.{#automate-mappings-between-ot-assets-and-equipment-model-entity__table_ivx_4nv_xbc__entry__2} | Persona | Description | |-|-| | System Admin | The System Administrator performs these tasks: * Imports data into the OT subnet to Equipment Model Entity Mapping table * Activates, schedules, or manually triggers the OT Subnet Mapping scheduled flow {#automate-mappings-between-ot-assets-and-equipment-model-entity__ul_hmz_pnv_xbc} | | ISA Admin | The ISA admin manually triggers the Map all OT devices UI action from the OT Subnet Mapping list view. | | ISA Editor | The ISA editor performs these tasks: * Manually creates and updates OT subnet mapping entries for specific sites * Maps individual OT devices to an equipment model entity from an OT device record * Maps multiple OT devices to an equipment model entity from an OT subnet mapping record {#automate-mappings-between-ot-assets-and-equipment-model-entity__ul_lmz_pnv_xbc} | [Table 2. Personas for automated mapping] {#automate-mappings-between-ot-assets-and-equipment-model-entity__table_ivx_4nv_xbc} ## Plugins {#automate-mappings-between-ot-assets-and-equipment-model-entity__section_g5x_sjv_mtb} Enabling the mapping feature requires the following plugins: * [Operational Technology Manager](https://www.servicenow.com/docs/1MVfNbKxG9cy_4aVyxPImA "The Operational Technology Manager application creates the foundational data and relationships that enable your organization to use the ServiceNow Operational Technology solution. Operational Technology Manager supports the use of the Configuration Management Database (CMDB), Service Graph Connectors, and Discovery applications in the ServiceNow AI Platform.") * [Industrial Process Manager](https://www.servicenow.com/docs/9Zf0CzRMffGJ032T~aqsEQ "Use the Industrial Process Manager application to create the ISA-95 Equipment Model data foundation that is required for the ServiceNow Operational Technology solution. The Industrial Process Manager enables you to create your own version of the equipment models in each of your sites.") * [Industrial Core](https://www.servicenow.com/docs/LysP4jjvdLP8BS_zs5NEgA "The Industrial Core plugin contains the class mappings needed for the Operational Technology (OT) certified Service Graph Connectors.") If the required plugins are installed, an ISA administrator can access the subnet mapping feature from the Industrial Process Manager application menu on the ServiceNow AI Platform. * **[Workflow for the automated mapping feature](https://www.servicenow.com/docs/u3Gd3sFhCsz8126bZZllJA)** The Industrial Process Manager includes an automated flow for the automated mapping feature. * **[Configure Automated Mapping of OT devices using guided setup](https://www.servicenow.com/docs/HUewE7DMQOOUJLleHNnpQw)** Use the Industrial Process Manager guided setup to automatically map OT devices to the ISA equipment model entity. * **[Configure the OT Subnet Mapping scheduled flow](https://www.servicenow.com/docs/I919vgCpy4t3VFBGC35JDg)** Configure the OT device mapping flow to automatically map OT devices to sites and equipment model entities. * **[Automatically map all OT devices to an equipment model entity](https://www.servicenow.com/docs/VFkr2qC5GQyUGS9GysG3bg)** An Operational Technology (OT) Amazing admin can trigger automated mapping of all OT devices to the appropriate ISA equipment model entity. * **[Create an OT discovered subnet](https://www.servicenow.com/docs/V0BWAWddA2tK_mich7WeCA)** Create an Operational Technology (OT) discovered subnet to use during OT subnet mapping to help identify OT devices and assign them to the correct equipment model entity. * **[View OT devices not assigned to a site](https://www.servicenow.com/docs/6cRADYLIKIwRGVKx3bhj4Q)** View the list of Operational Technology (OT) devices that aren't assigned to a site. * **[View unmapped OT devices](https://www.servicenow.com/docs/sVqXtxdcGi2s~_AIo_ObzA)** View a list of Operational Technology (OT) devices with IP addresses that aren't mapped to any equipment model entity. * **[View OT subnet mappings](https://www.servicenow.com/docs/5wr7XtsUWeoYPT0VSA18lA)** View all mapped OT subnets assigned to an equipment model entity. * **[View all mapped OT devices](https://www.servicenow.com/docs/OFK0j0Pb25Ei3yCtFvgZKQ)** View a list of all the Operational Technology (OT) devices that are mapped to an equipment model entity.