--- sourceDocument: zurich Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/delta-yokohama-zurich Release : - zurich ft:locale : - en-US ft:publication_title : - zurich Combined Product Files ft:clusterId : - delta3zy bundleId : - delta3zy --- # Combined Telecommunications Network Inventory release notes for upgrades from Yokohama to Zurich # Combined Telecommunications Network Inventory release notes for upgrades from Yokohama to Zurich {#ariaid-title1} Release version: Zurich Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 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 Combined Telecommunications Network Inventory release notes for upgrades from Yokohama to Zurich This document consolidates the release notes for Telecommunications Network Inventory (TNI) upgrades from the Yokohama release to the Zurich release. It provides essential information on new features, changes, upgrade prerequisites, activation, and additional requirements to help ServiceNow customers effectively plan and execute their upgrade process. Show full answer Show less ## Important Upgrade Information * **Yokohama Release:** Requires the Xanadu platform version to support the Design and Assign playbook feature. * **Zurich Release:** No specific upgrade notes, but preparation should include reviewing pre- and post-upgrade tasks to ensure a smooth transition. ## New Features Several significant features were introduced between Yokohama and Zurich releases that enhance network design, visualization, and operations: * **Design and Assign Playbook (Yokohama):** Step-by-step guidance to design and instantiate network services and logical connections, including creating equipment records and managing logical composites via change models. * **Visualization Enhancements (Zurich):** * Introduction of an L1 menu consolidating all network visualizations (site, floor, topology) into a single canvas. * Geo map enhancements to display sites and data centers, enabling direct access to detailed floor maps. * New floor map tools for datacenter layout visualization, supporting monitoring of power, thermal, and usage data alongside incidents and alerts. * **Datacenter Infrastructure Roles (Zurich):** Roles such as DC Floor Designer, DC Ops Agent, and DC Ops Viewer introduced for managing and viewing datacenter assets and workspace. * **Service Operations Workspace:** Provides a unified interface for agents to access incident/alarm details and network inventory information to improve operational efficiency. * **Capacity and Operational Data Management:** Ability to push operational data to REST endpoints, overlay time-series metrics on datacenter floor maps, and manually record configuration item operational values for performance tracking. * **Expanded Inventory Definitions:** Facilities, power circuits, and facility hardware models were added to represent physical and electrical infrastructure in datacenters. * **Network Interface and Equipment Model Updates:** New attributes such as Wavelength and Port position added to network interfaces and models for more granular inventory detail. ## Changes * **UI and Navigation:** Coral theme is now the default for portal, web, and mobile experiences, offering a refreshed user interface with a dark mode option. * **Menu and Terminology Updates:** * The Topology menu has been integrated into the Network Visualization L1 menu. * Network site map has been repositioned as a Geo map tab within Network Visualization. * Renaming of key entities for clarity: Network site to Site, xNF Instance to Service Instance, and xNF to Network Function. * **Improved Logical Interface Management:** Logical interfaces now automatically link to their parent cards or equipment, preventing duplicate configuration items and improving consistency between logical and physical interfaces. ## Activation and Installation * **Yokohama:** Telecommunications Network Inventory installed via ServiceNow Store; follow the installation procedures documented for Yokohama. * **Zurich:** Requires installation of the Network Inventory Advanced plugin (snniadv) from the ServiceNow Store. * ServiceNow Store remains the central source for requesting and managing Telecommunications Network Inventory apps and plugins. ## Additional Requirements * Zurich release requires the Telecommunications Alarm Management Open API (snindtmf642) and Customer Service Problem Management (snsprbmgmt) plugins to enable incident and alert viewing. * Indoor Mapping plugin (snmapcore) is required to create and manage datacenter floor maps. ## Practical Benefits for ServiceNow Customers * Enhanced guided workflows for network service design reduce errors and improve efficiency in inventory creation. * Improved visualization tools, including consolidated network views and datacenter floor maps, enable better infrastructure management and operational decision-making. * New roles and workspace integrations simplify collaboration and incident management across network and datacenter operations teams. * Expanded capacity and operational data handling supports proactive monitoring and performance tracking of network assets. * The updated UI and terminology harmonize user experience and align with modern ServiceNow design standards. Consolidated page of all release notes for Telecommunications Network Inventory from Yokohama to Zurich. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Telecommunications Network Inventory release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Zurich. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading Telecommunications Network Inventory to Zurich Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-telecommunicationsnetworkinventory-summary__entry__2} | Release | Release notes | |-|-| | Yokohama | Upgrade information : The Yokohama release needs the Xanadu platform version to support the Design and Assign playbook feature. | | Zurich | No updates for this release. | [ ] ## New features Between your current release family and Zurich, new features were introduced for Telecommunications Network Inventory. {#dfrn3-telecommunicationsnetworkinventory-summary__entry__8} | Release | Release notes | |-|-| | Yokohama | [Design and assign your network services](https://www.servicenow.com/docs/access?context=design-assign-playbook&family=yokohama&ft:locale=en-US) : Create and configure playbooks for design and assign a configuration item. The Design and Assign playbook provides step-by-step guidance for designing a network service. Use the playbook to complete guided activities to instantiate a network inventory record. [Design and Assign function for logical connections](https://www.servicenow.com/docs/access?context=design-logical-connection-design-assign-playbook&family=yokohama&ft:locale=en-US) : Use the Design and Assign playbook to instantiate a logical connection and its associated connection elements. Once each activity completes, view the circuit map to visualize the logical connection elements. [Visualization of geo map](https://www.servicenow.com/docs/access?context=visualization-map&family=yokohama&ft:locale=en-US) : Use the Network site map to view the geographical location of your network sites and the information such as site details, connectivity, and capacity. [Creating an inventory template for a logical composite](https://www.servicenow.com/docs/access?context=creating-inventory-template-logical-composite&family=yokohama&ft:locale=en-US) : Instantiate a logical composite record and associated equipment and racks using a logical composite template. [Add an equipment or rack to logical composite](https://www.servicenow.com/docs/access?context=add-equipment-rack-logical-composite&family=yokohama&ft:locale=en-US) : Add equipment or rack to a logical composite using a change model. [Remove an equipment or rack from logical composite](https://www.servicenow.com/docs/access?context=remove-equipment-rack-logical-composite&family=yokohama&ft:locale=en-US) : Remove a rack or equipment from a logical composite using a change model. [Create an equipment record by using design and assign](https://www.servicenow.com/docs/access?context=create-equipment-record-design-and-assign&family=yokohama&ft:locale=en-US) : Create a change request for an equipment record from the All Equipment list view using the Create equipment UI action. [Import models and templates in JSON format](https://www.servicenow.com/docs/access?context=import-models-templates-json&family=yokohama&ft:locale=en-US) : Create an import request to import your collection of models and templates in JSON format. [Export hierarchy of models and templates](https://www.servicenow.com/docs/access?context=export-hierarchy-of-models-and-template&family=yokohama&ft:locale=en-US) : Export the hierarchy and all related records of a model or inventory template in JSON format. [Managing your network functions](https://www.servicenow.com/docs/access?context=services&family=yokohama&ft:locale=en-US) : The xNF and xNF instances records are added in the Inventory menu and retained the Services menu for application services. [Create a telephone infrastructure](https://www.servicenow.com/docs/access?context=telephone_block_telephone_number_and_telephone_number&family=yokohama&ft:locale=en-US) : Supports all types of telephone numbers. | | Zurich | [Create logical connection record](https://www.servicenow.com/docs/access?context=create-logical-connection-record-design-assign-playbook&family=zurich&ft:locale=en-US) : Logical interfaces created are now automatically related to their corresponding cards or parent equipment. This enhancement ensures consistency across systems and helps prevent duplicate CI creation by improving the alignment between logical and physical interfaces. [Visualize your network infrastructure](https://www.servicenow.com/docs/access?context=data-center-inventory-management&family=zurich&ft:locale=en-US) : Use the new L1 menu that consolidates all network visualizations into a single canvas and include a tabular section for each view, such as site, floor, and topology. The following roles are introduced to manage datacenter infrastructure. * DC Floor Designer (sn_ni_core.dc_floor_designer) -- Design floor layout in Map Studio. * DC Ops Agent (sn_ni_core.dc_ops_agent) -- Oversee the operations of the data center floor. * DC Ops Viewer (sn_ni_core.dc_ops_viewer) -- View the Network Inventory Workspace and its components. [Floor map](https://www.servicenow.com/docs/access?context=visualization-floor-maps&family=zurich&ft:locale=en-US) : Use the floor map to view the layout of your datacenter infrastructure. View network asset placement and operational details to monitor power, thermal, and usage data. View the incidents and alerts and take appropriate action. [Geo map](https://www.servicenow.com/docs/access?context=visualization-map&family=zurich&ft:locale=en-US) : Use the geo map to view the geographical locations of your network sites and data centers. Geo map supports rendering data centers on the map, enabling the relevant persona, such as the DC Ops Viewer, to view connected data centers. You can open a data center floor map directly from the geo map for more detailed insights. [Manage datacenter floor map](https://www.servicenow.com/docs/access?context=create-floor-map-data-center&family=zurich&ft:locale=en-US) : Upload and manage your datacenter map objects using the Map Studio interface. Enable you to view respective floor plans for a selected building in a campus. [Service Operations Workspace](https://www.servicenow.com/docs/access?context=service-operations-workspace-network-inventory&family=zurich&ft:locale=en-US) : Provides a converged experience for agents to view both incident/alarm details and Network Inventory entities within a single Workspace. Enhances efficiency in retrieving information and significantly improves the overall user experience. [Capacity management](https://www.servicenow.com/docs/access?context=capacity-management-reporting&family=zurich&ft:locale=en-US) : Supports pushing operational data to REST endpoints through an exposed API and store it in the ClothoDB. Overlay time series metrics on the datacenter floor map to monitor overall health and take appropriate action. [Collect operational values for datacenter](https://www.servicenow.com/docs/access?context=enter-operational-values-data-center&family=zurich&ft:locale=en-US) : Manually record operational values of Configuration Items (CI) and store it in ClothoDB. Use this data for datacenter performance tracking. [Define the datacenter details](https://www.servicenow.com/docs/access?context=define-data-center-details&family=zurich&ft:locale=en-US) : Define your datacenter record to view the location-specific attributes for each datacenter, including the campus, buildings, and floors where your network asset is located. [Define the power circuit details](https://www.servicenow.com/docs/access?context=define-power-circuit-details&family=zurich&ft:locale=en-US) : Define the power circuit record to represent the electrical pathway that delivers power within a data center. [Define the facility hardware details](https://www.servicenow.com/docs/access?context=define-facility-hardware-details&family=zurich&ft:locale=en-US) : Define the facility hardware record to represent power, HVAC (Heating, Ventilation, and Air Conditioning), network representation, and their connectivity in a data center. [Create a facility model](https://www.servicenow.com/docs/access?context=create-facility-model&family=zurich&ft:locale=en-US) : Create a facility model to define the physical characteristics data of the facility record based on the product manufacturer's recommendations. [Create a equipment record](https://www.servicenow.com/docs/access?context=create-equipment-record-design-and-assign&family=zurich&ft:locale=en-US) : View datacenter records listed in the Equipment task attribute form. [Define the network interface details](https://www.servicenow.com/docs/access?context=define-tni-interfaces&family=zurich&ft:locale=en-US) : Add Wavelength attribute to the Network Interface form and Port position attribute to Interface Model form. [Create an equipment holder model](https://www.servicenow.com/docs/access?context=create-equipment-holder-models&family=zurich&ft:locale=en-US) : Added RU numbering direction attribute to define the numbering sequence of rack units in the Rack view. | [ ] ## Changes Between your current release family and Zurich, some changes were made to existing Telecommunications Network Inventory features. {#dfrn3-telecommunicationsnetworkinventory-summary__entry__14} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | Coral theme : Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. [Visualize your network infrastructure](https://www.servicenow.com/docs/access?context=data-center-inventory-management&family=zurich&ft:locale=en-US) : The Network Visualization L1 menu is added to the Telecommunications Network Inventory Workspace. The Topology L1 menu has been removed and is available as Topology tab within the Network Visualization view. [Geo map](https://www.servicenow.com/docs/access?context=visualization-map&family=zurich&ft:locale=en-US) : Network site map L1 menu is removed and repositioned as Geo map tab in the Network visualization view. [Define the power circuit details](https://www.servicenow.com/docs/access?context=define-power-circuit-details&family=zurich&ft:locale=en-US) : The Power Circuits inventory is added. [Define the facility hardware details](https://www.servicenow.com/docs/access?context=define-facility-hardware-details&family=zurich&ft:locale=en-US) : The All Facilities inventory is added. [Create a facility model](https://www.servicenow.com/docs/access?context=create-facility-model&family=zurich&ft:locale=en-US) : The Facility Models inventory model is added. [Lists view](https://www.servicenow.com/docs/access?context=network-inventory-workspace-list-view&family=zurich&ft:locale=en-US) : The Network site is renamed to Site. [Define network service instance details](https://www.servicenow.com/docs/access?context=create_application_services&family=zurich&ft:locale=en-US) : xNF Instance is renamed to Service Instance. [Define network function details](https://www.servicenow.com/docs/access?context=create_business_applications&family=zurich&ft:locale=en-US) : xNF is renamed to Network Function. | [ ] ## Removed Between your current release family and Zurich, some Telecommunications Network Inventory features or functionality were removed. {#dfrn3-telecommunicationsnetworkinventory-summary__entry__20} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Deprecations Between your current release family and Zurich, some Telecommunications Network Inventory features or functionality were deprecated. {#dfrn3-telecommunicationsnetworkinventory-summary__entry__26} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Activation information Review information on how to activate Telecommunications Network Inventory. {#dfrn3-telecommunicationsnetworkinventory-summary__entry__32} | Release | Release notes | |-|-| | Yokohama | Activation information : Install Telecommunications Network Inventory by requesting it from the ServiceNow Store. For details about the installation procedure, see [Install Telecommunications Network Inventory](https://www.servicenow.com/docs/access?context=installing-telecommunications-network-inventory&family=yokohama&ft:locale=en-US). Important: Telecommunications Network Inventory is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Zurich | Activation information : Install Network Inventory Advanced plugin (sn_ni_adv) by requesting it from the ServiceNow Store. For installation details, see [Install TNI](https://www.servicenow.com/docs/access?context=installing-telecommunications-network-inventory&family=zurich&ft:locale=en-US). 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). Important: Telecommunications Network Inventory is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Telecommunications Network Inventory we have noted them here. {#dfrn3-telecommunicationsnetworkinventory-summary__entry__38} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | Additional requirements : * You must install Telecommunications Alarm Management Open API (sn_ind_tmf642) and Customer Service Problem Management (sn_sprb_mgmt) plugin to view incident and alert details. * You must install the Indoor Mapping plugin (sn_map_core) to create and manage floor maps for data centers. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Telecommunications Network Inventory we have noted them here. {#dfrn3-telecommunicationsnetworkinventory-summary__entry__44} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Telecommunications Network Inventory, such as specific requirements or compliance levels. {#dfrn3-telecommunicationsnetworkinventory-summary__entry__50} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Telecommunications Network Inventory we have noted them here. {#dfrn3-telecommunicationsnetworkinventory-summary__entry__56} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Telecommunications Network Inventory we have noted them here. {#dfrn3-telecommunicationsnetworkinventory-summary__entry__62} | Release | Release notes | |-|-| | Yokohama | * View the geographical location and the details of your network site * Design and assign a configuration item using a playbook and add custom states to a Change model. * Define a logical composite to track and manage its CI. * Import and export your collection of models and templates in JSON format. * Enable Deny ACL to ensure the compliance with the enhanced security model. See [Telecommunications Network Inventory](https://www.servicenow.com/docs/access?context=telecom-network-inventory&family=yokohama&ft:locale=en-US) for more information. | | Zurich | * The Logical interfaces (such as VLANs) and physical interfaces (such as Gigabit Ethernet ports) are now related to their parent equipment or card to help prevent duplicate CI creation. * Get converged experience for Network Inventory workflows using Service Operations Workspace. * Upload and manage CAD/PNG of floor maps to view the datacenter layout with physical asset placements over the floor. * Ingest operational data and show time series metrics on the datacenter floor map to monitor health. * Capture an inventory of operational facilities and define their relationships to respective network hardware such as the power chain. See [Telecommunications Network Inventory](https://www.servicenow.com/docs/access?context=telecom-network-inventory&family=zurich&ft:locale=en-US) for more information. | [ ]