| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nWashington DC\n\n | \n\nThe Industrial Process Manager application now has a dependency with the Operational Technology Service Management applications, which include Operational Technology Incident Management and Operational Technology Change Management. To install Industrial Process Manager on your instance, one of the following SKUs is required:\n\n- Operational Technology Visibility SKU\n- Operational Technology Service Management SKU\n- Any custom SKU that entitles Industrial Process Manager\n\n |
| \n\nXanadu\n\n | \n\nThe Industrial Process Manager application now has a dependency with the Operational Technology Service Management applications, which include Operational Technology Incident Management and Operational Technology Change Management. To install Industrial Process Manager on your instance, one of the following SKUs is required:\n\n- Operational Technology Visibility SKU\n- Operational Technology Service Management SKU\n- Any custom SKU that entitles Industrial Process Manager\n\n |
| \n\nYokohama\n\n | \n\nNo updates for this release.\n\n |
| \n\nZurich\n\n | \n\nNo updates for this release.\n\n |
| \n\nAustralia\n\n | \n\nNo updates for this release.\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nWashington DC\n\n | \n\n- **[Add OT devices to an equipment model entity by IP address](https://www.servicenow.com/docs/access?context=view-ot-assets-equipment-model-entity&family=washingtondc&ft:locale=en-US)**\n\nWhen you manually add OT devices to the Mapped OT Devices related list in the Equipment Model Manager on the Industrial Workspace, you can add an OT device by its IP address.\n\n- **[Update the entity name or parent of an equipment model entity](https://www.servicenow.com/docs/access?context=update-the-name-or-parent-equipment-model-entity&family=washingtondc&ft:locale=en-US)**\n\nUpdate the **Entity name** or **Parent** fields in an equipment model entity record as needed to help keep your equipment model information up to date.\n\n- **[Modifying the parent of an equipment model entity](https://www.servicenow.com/docs/access?context=managing-equipment-models-after-data-import&family=washingtondc&ft:locale=en-US)**\n\nUpdate the parent in one or more equipment model entity records after creating an equipment model entity.\n\n- **[Additional AMAZING roles to access and edit OT subnet-mapping records](https://www.servicenow.com/docs/access?context=components-installed-with-industrial-process-manager&family=washingtondc&ft:locale=en-US)**\n\nControl which users have access to and can edit OT subnet-mapping records by assigning the Amazing Reader \\(sn\\_ot\\_amazing\\_read\\), Amazing Writer \\(sn\\_ot\\_amazing\\_write\\), and Amazing Admin \\(sn\\_ot\\_amazing\\_admin\\) roles.\n\n- **[Automatically assigns all OT control modules to equipment model entities based on the Owns::Owned by relationship \\(sn\\_otsm.subnet\\_mapping.auto\\_assign\\_ot\\_control\\_modules\\) system property](https://www.servicenow.com/docs/access?context=system-properties-used-by-automated-mapping-feature&family=washingtondc&ft:locale=en-US)**\n\nEnable automatic assignments of OT control modules to equipment model entities based on the owns::owned by relationship the OT control module has with an OT control system \\(or extended class\\) device.\n\n- **[User Criteria security model](https://www.servicenow.com/docs/access?context=create-user-criteria-for-equipment-model-entity-site-users&family=washingtondc&ft:locale=en-US)**\n\nCreate and assign user criteria to control the view and edit the user access to your sites and equipment model entities with the new User Criteria security model. If you want to migrate from the site user configuration to the User Criteria security model, the ISAEntitySiteUser script was updated to query the ISA User Criteria table and calls the User Criteria API for all existing public APIs.\n\n**Note:** If your ISA Equipment Model application version is prior to 1.0.12, you can still use the site user configuration available for the ISA Equipment Model.\n\n\n |
| \n\nXanadu\n\n | \n\n- **[Capture the mapped equipment model entity for your OT devices](https://www.servicenow.com/docs/access?context=view-all-mapped-ot-devices&family=xanadu&ft:locale=en-US)**\n\nOrganize your OT device data efficiently by adding the primary equipment model entity for your OT devices. You can also automatically update the primary equipment model entity for your existing devices.\n\n- **[Use the Unified Map experience in the Industrial Workspace](https://www.servicenow.com/docs/access?context=unified-maps-experience-iw&family=xanadu&ft:locale=en-US)**\n\nView the relationships between OT devices and other CIs with the Unified Map experience. You can also view related items, such as OT incidents and change requests.\n\n- **[Map discovery detected devices using the Automated Mapping Across Zone-based IP Network Groups \\(AMAZING\\) feature](https://www.servicenow.com/docs/access?context=automatedly-map-all-ot-assets&family=xanadu&ft:locale=en-US)**\n\nMap Discovery detected devices that have an IP address on their Network Adapter record using the AMAZING feature.\n\n- **[Add OT devices to an equipment model entity by IP address](https://www.servicenow.com/docs/access?context=view-ot-assets-equipment-model-entity&family=xanadu&ft:locale=en-US)**\n\nWhen you manually add OT devices to the Mapped OT Devices related list in the Equipment Model Manager on the Industrial Workspace, you can add an OT device by its IP address.\n\n- **[Update entity name or parent entity](https://www.servicenow.com/docs/access?context=update-the-name-or-parent-equipment-model-entity&family=xanadu&ft:locale=en-US)**\n\nUpdate the **Entity name** or **Parent** fields in an equipment model entity record as needed to help keep your equipment model information up to date.\n\n\n |
| \n\nYokohama\n\n | \n\n- **[Set the operational status for equipment model entity sites](https://www.servicenow.com/docs/access?context=equipment-model-workspace&family=yokohama&ft:locale=en-US)**\n\nSet equipment model entity sites to not in use in the Industrial Workspace by selecting the **Not in use** value for the **Operational Status** field.\n\n- **[Filter out Not in use and Retired equipment model entities from view](https://www.servicenow.com/docs/access?context=filter-out-non-operational-equipment-model-entities&family=yokohama&ft:locale=en-US)**\n\nFilter out **Not in use** and **Retired** equipment model entities in the Industrial Workspace using the **Operational Status** field value for a site.\n\n- **[Add child equipment model entities to a Favorites view in the Industrial Workspace](https://www.servicenow.com/docs/access?context=favorite-child-equipment-model-entity&family=yokohama&ft:locale=en-US)**\n\nUse the Favorite icon \\(\\[Omitted image \"image.mark-as-favorite\"\\] Alt text:\\) to add a child equipment model entity as a favorite in the Equipment Model Manager on the Industrial Workspace. You can then use the **Show Favorites** toggle to display them.\n\n- **[Assign Processing Order to sort equipment model entities in a site](https://www.servicenow.com/docs/access?context=view-child-entities-equipment-model-entity&family=yokohama&ft:locale=en-US)**\n\nUse the **Processing Order** field to assign values to an equipment model entity that determines their functional importance in a site.\n\n- **[The Daily Activity tab in the Equipment Model view in the Industrial Workspace](https://www.servicenow.com/docs/access?context=view-ot-eme-daily-summary&family=yokohama&ft:locale=en-US)**\n\nView the list of previous day's activities on the **Daily Activity** tab of an OT device. The activities include adding an OT device and changing the field-level attributes for existing OT devices. For example, IP address, Device Criticality, and more.\n\n- **[Capture the mapped equipment model entity for your OT devices](https://www.servicenow.com/docs/access?context=view-all-mapped-ot-devices&family=yokohama&ft:locale=en-US)**\n\nOrganize your OT device data efficiently by adding the primary equipment model entity for your OT devices. You can also automatically update the primary equipment model entity for your existing devices.\n\n- **[Use the Unified Map experience in the Industrial Workspace](https://www.servicenow.com/docs/access?context=unified-maps-experience-iw&family=yokohama&ft:locale=en-US)**\n\nView the relationships between OT devices and other CIs with the Unified Map experience. You can also view related items, such as OT incidents and change requests.\n\n- **[Map Discovery detected devices using the Automated Mapping Across Zone-based IP Network Groups \\(AMAZING\\) feature](https://www.servicenow.com/docs/access?context=automatedly-map-all-ot-assets&family=yokohama&ft:locale=en-US)**\n\nMap Discovery detected devices that have an IP address on their Network Adapter record using the AMAZING feature.\n\n\n |
| \n\nZurich\n\n | \n\n- **[Discovered subnets supported by the AMAZING feature](https://www.servicenow.com/docs/access?context=automate-mappings-between-ot-assets-and-equipment-model-entity&family=zurich&ft:locale=en-US)**\n\nUse the AMAZING feature, which uses discovered subnets, to identify OT devices and assign them to the correct equipment model entity during OT subnet mapping.\n\n- **[Map OT devices from the Equipment Model Manager](https://www.servicenow.com/docs/access?context=map-ot-devices-in-iw&family=zurich&ft:locale=en-US)**\n\nMap OT devices to equipment model entities using the **Unmapped OT Devices** and the **All Devices** tabs in the Equipment Model Manager of the Industrial Workspace.\n\n- **[Generate a location hierarchy](https://www.servicenow.com/docs/access?context=create-location-hierarchy-isa&family=zurich&ft:locale=en-US)**\n\nGenerate a complete location hierarchy for an ISA equipment model entity tree when no locations exist to establish location references that match the ISA hierarchy.\n\n- **[Use the OT Network Map to visualize your OT network](https://www.servicenow.com/docs/access?context=utilizing-ot-network-map&family=zurich&ft:locale=en-US)**\n\nVisualize your OT network, subnets, and device-to-device connections with the OT Network Map in the Industrial Workspace.\n\n- **[Set the operational status for equipment model entity sites](https://www.servicenow.com/docs/access?context=equipment-model-workspace&family=zurich&ft:locale=en-US)**\n\nSet equipment model entity sites to not in use in the Industrial Workspace by selecting the **Not in use** value for the **Operational Status** field.\n\n- **[Filter out Not in use and Retired equipment model entities from view](https://www.servicenow.com/docs/access?context=filter-out-non-operational-equipment-model-entities&family=zurich&ft:locale=en-US)**\n\nFilter out **Not in use** and **Retired** equipment model entities in the Industrial Workspace using the **Operational Status** field value for a site.\n\n- **[Add child equipment model entities to a Favorites view in the Industrial Workspace](https://www.servicenow.com/docs/access?context=favorite-child-equipment-model-entity&family=zurich&ft:locale=en-US)**\n\nUse the Favorite icon \\(\\[Omitted image \"image.mark-as-favorite\"\\] Alt text:\\) to add a child equipment model entity as a favorite in the Equipment Model Manager on the Industrial Workspace. You can then use the **Show Favorites** toggle to display them.\n\n- **[Assign Processing Order to sort equipment model entities in a site](https://www.servicenow.com/docs/access?context=view-child-entities-equipment-model-entity&family=zurich&ft:locale=en-US)**\n\nUse the **Processing Order** field to assign values to an equipment model entity that determines their functional importance in a site.\n\n- **[The Daily Activity tab in the Equipment Model view in the Industrial Workspace](https://www.servicenow.com/docs/access?context=view-ot-eme-daily-summary&family=zurich&ft:locale=en-US)**\n\nView the list of previous day's activities on the **Daily Activity** tab of an OT device. The activities include adding an OT device and changing the field-level attributes for existing OT devices. For example, IP address, Device Criticality, and more.\n\n\n |
| \n\nAustralia\n\n | \n\n- **[Discovered subnets supported by the AMAZING feature](https://www.servicenow.com/docs/access?context=automate-mappings-between-ot-assets-and-equipment-model-entity&family=australia&ft:locale=en-US)**\n\nUse the AMAZING feature, which uses discovered subnets, to identify OT devices and assign them to the correct equipment model entity during OT subnet mapping.\n\n- **[Map OT devices from the Equipment Model Manager](https://www.servicenow.com/docs/access?context=map-ot-devices-in-iw&family=australia&ft:locale=en-US)**\n\nMap OT devices to equipment model entities using the **Unmapped OT Devices** and the **All Devices** tabs in the Equipment Model Manager of the Industrial Workspace.\n\n- **[Generate a location hierarchy](https://www.servicenow.com/docs/access?context=create-location-hierarchy-isa&family=australia&ft:locale=en-US)**\n\nGenerate a complete location hierarchy for an ISA equipment model entity tree when no locations exist to establish location references that match the ISA hierarchy.\n\n- **[Use the OT Network Map to visualize your OT network](https://www.servicenow.com/docs/access?context=utilizing-ot-network-map&family=australia&ft:locale=en-US)**\n\nVisualize your OT network, subnets, and device-to-device connections with the OT Network Map in the Industrial Workspace.\n\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nWashington DC\n\n | \n\n- **[Manage the Equipment Model section in the Industrial Process Manager Guided Setup](https://www.servicenow.com/docs/access?context=configuring-manufacturing-process-mgr&family=washingtondc&ft:locale=en-US)**\n\nThe Manage the equipment model section of the Industrial Process Manager Guided Setup has the following new enhancements:\n\n - The Assign Users task was removed.\n - The Create User Criteria for Site Users task was added.\n - The Assign Site Users - Can Read task was added.\n - The Assign Site Users - Can Edit task was added.\n- **[ISA Equipment Model enhancements](https://www.servicenow.com/docs/access?context=migrating-site-user-access-to-user-criteria-and-groups&family=washingtondc&ft:locale=en-US)**\n\nWhen you upgrade to version 1.0.12 of the ISA Equipment Model, the migration from site user access to user criteria and groups begins automatically and the following changes are made:\n\n - Improved site level access control to that uses user criteria to define read or write level user access to equipment model entity sites. With the additional assignment of OT viewer \\(cmdb\\_ot\\_viewer\\) or OT Editor \\(cmdb\\_ot\\_editor\\) roles, you can also have view or edit access to OT devices in the sites assigned accordingly.\n - When you upgrade to version 1.0.12 of ISA Equipment Model, existing site user records are migrated to an improved access control model using user criteria to preserve the same access permissions. For each site with ISA Entity Site User records, the following changes occur.\n - For users with viewer access:\n - A new user criteria record is created and named **Read User Criteria for <site name> Site \\[System Generated\\]**\n - A new user group with all site users from this site is created and named **Read Group for <site name> Site \\[System Generated\\]**\n - A new record in the new Equipment Model Entity View Access table \\(isa\\_entity\\_m2m\\_user\\_criteria\\_can\\_view\\) is created with the new user criteria and user group.\n - For users with editor access:\n - A new user criteria record is created and named **Edit User Criteria for <site name> Site \\[System Generated\\]**\n - A new user group with all site users from this site is created and named **Edit Group for <site name> Site \\[System Generated\\]**\n - A new record in the new Equipment Model Entity Edit Access table \\(isa\\_entity\\_m2m\\_user\\_criteria\\_can\\_edit\\) is created with the new user criteria and user group.\n - The Site User application menu and Site Users related list on the Equipment Model Entity record for a site is removed.\n - All site user \\(isa\\_entity\\_site\\_user\\) records are set to inactive.\n - The **Site User – Can Read** and **Site User – Can Edit** application menu items are added to the ServiceNow AI Platform.\n - The **Can Read Equipment Models** and **Can Edit Equipment Models** related lists are added to the Equipment Model Entity record for a site.\n\n |
| \n\nXanadu\n\n | \n\nNo updates for this release.\n\n |
| \n\nYokohama\n\n | \n\n- **[Viewing multiple records at once in the Equipment Model Manager](https://www.servicenow.com/docs/access?context=managing-equipment-models-after-data-import&family=yokohama&ft:locale=en-US)**\n\nIn the Equipment Model Manager of the Industrial Workspace, view multiple records and keep the record context available instead of only viewing one record at a time. When creating or opening multiple records, the records open in single row of tabs at the same level so you can navigate back to other opened records.\n\n\n |
| \n\nZurich\n\n | \n\n- **[Admin role dependency](https://www.servicenow.com/docs/access?context=granular-admin-roles&family=zurich&ft:locale=en-US)**\n\nSeveral new granular admin roles were added to enable developers to complete administrative configuration tasks without requiring the full admin role.\n\n- **[Viewing multiple records at once in the Equipment Model Manager](https://www.servicenow.com/docs/access?context=managing-equipment-models-after-data-import&family=zurich&ft:locale=en-US)**\n\nIn the Equipment Model Manager of the Industrial Workspace, view multiple records and keep the record context available instead of only viewing one record at a time. When creating or opening multiple records, the records open in single row of tabs at the same level so you can navigate back to other opened records.\n\n\n |
| \n\nAustralia\n\n | \n\n- **[Admin role dependency](https://www.servicenow.com/docs/access?context=granular-admin-roles&family=australia&ft:locale=en-US)**\n\nSeveral new granular admin roles were added to enable developers to complete administrative configuration tasks without requiring the full admin role.\n\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nWashington DC\n\n | \n\n- The Site Users menu item that contained the ISA Entity Site Users \\[isa\\_entity\\_site\\_user\\] table was removed from the Equipment Model - ISA module on the ServiceNow AI Platform.\n\n |
| \n\nXanadu\n\n | \n\nNo updates for this release.\n\n |
| \n\nYokohama\n\n | \n\nNo updates for this release.\n\n |
| \n\nZurich\n\n | \n\nNo updates for this release.\n\n |
| \n\nAustralia\n\n | \n\nNo updates for this release.\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nWashington DC\n\n | \n\nNo updates for this release.\n\n |
| \n\nXanadu\n\n | \n\nNo updates for this release.\n\n |
| \n\nYokohama\n\n | \n\nNo updates for this release.\n\n |
| \n\nZurich\n\n | \n\nNo updates for this release.\n\n |
| \n\nAustralia\n\n | \n\nNo updates for this release.\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nWashington DC\n\n | \n\nInstall Industrial Process Manager by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website 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/access?context=sn-store-release-notes&family=washingtondc&ft:locale=en-US).\n\n**Note:** Industrial Process Manager is automatically installed with Operational Technology Incident Management and Operational Technology Change Management.\n\n |
| \n\nXanadu\n\n | \n\nInstall Industrial Process Manager by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website 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/access?context=sn-store-release-notes&family=xanadu&ft:locale=en-US).\n\n**Note:** Industrial Process Manager is automatically installed with Operational Technology Incident Management and Operational Technology Change Management.\n\n |
| \n\nYokohama\n\n | \n\nInstall Industrial Process Manager by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website 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/access?context=sn-store-release-notes&family=yokohama&ft:locale=en-US).\n\n |
| \n\nZurich\n\n | \n\nInstall Industrial Process Manager by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website 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/access?context=sn-store-release-notes&family=zurich&ft:locale=en-US).\n\n |
| \n\nAustralia\n\n | \n\nInstall Industrial Process Manager by requesting it from the ServiceNow 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/access?context=sn-store-release-notes&family=australia&ft:locale=en-US).\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nWashington DC\n\n | \n\nNo updates for this release.\n\n |
| \n\nXanadu\n\n | \n\nNo updates for this release.\n\n |
| \n\nYokohama\n\n | \n\nNo updates for this release.\n\n |
| \n\nZurich\n\n | \n\nNo updates for this release.\n\n |
| \n\nAustralia\n\n | \n\nNo updates for this release.\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nWashington DC\n\n | \n\nNo updates for this release.\n\n |
| \n\nXanadu\n\n | \n\nNo updates for this release.\n\n |
| \n\nYokohama\n\n | \n\nNo updates for this release.\n\n |
| \n\nZurich\n\n | \n\nNo updates for this release.\n\n |
| \n\nAustralia\n\n | \n\nNo updates for this release.\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nWashington DC\n\n | \n\nNo updates for this release.\n\n |
| \n\nXanadu\n\n | \n\nNo updates for this release.\n\n |
| \n\nYokohama\n\n | \n\nNo updates for this release.\n\n |
| \n\nZurich\n\n | \n\n- **Dark theme**\n\nThe new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability.\n\n\n |
| \n\nAustralia\n\n | \n\nNo updates for this release.\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nWashington DC\n\n | \n\nNo updates for this release.\n\n |
| \n\nXanadu\n\n | \n\nNo updates for this release.\n\n |
| \n\nYokohama\n\n | \n\nNo updates for this release.\n\n |
| \n\nZurich\n\n | \n\nNo updates for this release.\n\n |
| \n\nAustralia\n\n | \n\nNo updates for this release.\n\n |
| \n\nRelease\n\n | \n\nRelease notes\n\n |
|---|---|
| \n\nWashington DC\n\n | \n\n- Add Operational Technology \\(OT\\) devices to an equipment model entity by using the IP address.\n- Change the **Entity name** and **Parent** fields of an equipment model entity to keep your equipment model entity information up to date after you create it.\n- Modify the parent of one or more equipment model entities after the equipment model entity record is created.\n- Use the new Automated Mapping Across Zone-based IP Network Groups \\(AMAZING\\) roles to control who has access to and can edit OT subnet-mapping records.\n- Control the view and edit the access to your sites and equipment model entities by using the new User Criteria security model.\n\n See [Manufacturing Process Manager](https://www.servicenow.com/docs/access?context=industrial-process-manager-overview&family=washingtondc&ft:locale=en-US) for more information.\n\n |
| \n\nXanadu\n\n | \n\n- Organize your Operational Technology \\(OT\\) device data by capturing the mapped equipment model entity for an OT device.\n- View the relationships between devices and other configuration items \\(CIs\\) with the Unified Map experience in the Industrial Workspace.\n- Add Operational Technology \\(OT\\) devices to an equipment model entity by using the IP address.\n- Change the **Entity name** and **Parent** fields of an equipment model entity to keep your equipment model entity information up to date after you create it.\n\n See [Manufacturing Process Manager](https://www.servicenow.com/docs/access?context=industrial-process-manager-overview&family=xanadu&ft:locale=en-US) for more information.\n\n |
| \n\nYokohama\n\n | \n\n- Identify sites on your equipment model entity that aren't in use with a new **Operational Status** field value in the Industrial Workspace.\n- Filter out **Not in use** or **Retired** equipment model entities in the Industrial Workspace using the **Operational Status** field value.\n- Sort equipment model entities for a Site using the new value **Processing Order**.\n- View the **Daily Activity** tab for a summarized version of the previous day's activities on Operational Technology \\(OT\\) devices.\n- Organize your OT device data by capturing the mapped equipment model entity for an OT device.\n- View the relationships between devices and other configuration items \\(CIs\\) with the Unified Map experience in the Industrial Workspace.\n\n See [Manufacturing Process Manager](https://www.servicenow.com/docs/access?context=industrial-process-manager-overview&family=yokohama&ft:locale=en-US) for more information.\n\n |
| \n\nZurich\n\n | \n\n- View both unmapped and all Operational Technology \\(OT\\) devices in separate tabs while mapping them to equipment model entities for an organized view of your OT devices.\n- Visualize your OT network using the OT Network Map.\n- Automatically create a location for equipment model entities to visualize your location hierarchy.\n- Use the updated Automated Mapping Across Zone-based IP Network Groups \\(AMAZING\\) feature to uniquely identify OT devices during equipment model entity mapping.\n- Identify sites on your equipment model entity that aren't in use with a new **Operational Status** field value in the Industrial Workspace.\n- Filter out **Not in use** or **Retired** equipment model entities in the Industrial Workspace using the **Operational Status** field value.\n- Sort equipment model entities for a Site using the new value **Processing Order**.\n- View the **Daily Activity** tab for a summarized version of the previous day's activities on the Operational Technology \\(OT\\) devices.\n\n See [Manufacturing Process Manager](https://www.servicenow.com/docs/access?context=industrial-process-manager-overview&family=zurich&ft:locale=en-US) for more information.\n\n |
| \n\nAustralia\n\n | \n\n- View both unmapped and all Operational Technology \\(OT\\) devices in separate tabs while mapping them to equipment model entities for an organized view of your OT devices.\n- Visualize your OT network using the OT Network Map.\n- Automatically create a location for equipment model entities to visualize your location hierarchy.\n- Use the updated Automated Mapping Across Zone-based IP Network Groups \\(AMAZING\\) feature to uniquely identify OT devices during equipment model entity mapping.\n\n See for [Manufacturing Process Manager](https://www.servicenow.com/docs/access?context=industrial-process-manager-overview&family=australia&ft:locale=en-US) more information.\n\n |