| \n\nYokohama\n\n | \n\n- **[Design and assign your network services](https://www.servicenow.com/docs/access?context=design-assign-playbook&family=yokohama&ft:locale=en-US)**\n\nCreate 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.\n\n- **[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)**\n\nUse 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.\n\n- **[Visualization of geo map](https://www.servicenow.com/docs/access?context=visualization-map&family=yokohama&ft:locale=en-US)**\n\nUse the Network site map to view the geographical location of your network sites and the information such as site details, connectivity, and capacity.\n\n- **[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)**\n\nInstantiate a logical composite record and associated equipment and racks using a logical composite template.\n\n- **[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)**\n\nAdd equipment or rack to a logical composite using a change model.\n\n- **[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)**\n\nRemove a rack or equipment from a logical composite using a change model.\n\n- **[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)**\n\nCreate a change request for an equipment record from the All Equipment list view using the **Create equipment** UI action.\n\n- **[Import models and templates in JSON format](https://www.servicenow.com/docs/access?context=import-models-templates-json&family=yokohama&ft:locale=en-US)**\n\nCreate an import request to import your collection of models and templates in JSON format.\n\n- **[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)**\n\nExport the hierarchy and all related records of a model or inventory template in JSON format.\n\n- **[Managing your network functions](https://www.servicenow.com/docs/access?context=services&family=yokohama&ft:locale=en-US)**\n\nThe xNF and xNF instances records are added in the Inventory menu and retained the Services menu for application services.\n\n- **[Create a telephone infrastructure](https://www.servicenow.com/docs/access?context=telephone_block_telephone_number_and_telephone_number&family=yokohama&ft:locale=en-US)**\n\nSupports all types of telephone numbers.\n\n\n |
| \n\nZurich\n\n | \n\n- **[Create logical connection record](https://www.servicenow.com/docs/access?context=create-logical-connection-record-design-assign-playbook&family=zurich&ft:locale=en-US)**\n\nLogical 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.\n\n\n - **[Visualize your network infrastructure](https://www.servicenow.com/docs/access?context=data-center-inventory-management&family=zurich&ft:locale=en-US)**\n\nUse 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.\n\n - DC Floor Designer \\(sn\\_ni\\_core.dc\\_floor\\_designer\\) – Design floor layout in Map Studio.\n - DC Ops Agent \\(sn\\_ni\\_core.dc\\_ops\\_agent\\) – Oversee the operations of the data center floor.\n - DC Ops Viewer \\(sn\\_ni\\_core.dc\\_ops\\_viewer\\) – View the Network Inventory Workspace and its components.\n- **[Floor map](https://www.servicenow.com/docs/access?context=visualization-floor-maps&family=zurich&ft:locale=en-US)**\n\nUse 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.\n\n- **[Geo map](https://www.servicenow.com/docs/access?context=visualization-map&family=zurich&ft:locale=en-US)**\n\nUse 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.\n\n- **[Manage datacenter floor map](https://www.servicenow.com/docs/access?context=create-floor-map-data-center&family=zurich&ft:locale=en-US)**\n\nUpload 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.\n\n- **[Service Operations Workspace](https://www.servicenow.com/docs/access?context=service-operations-workspace-network-inventory&family=zurich&ft:locale=en-US)**\n\nProvides 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.\n\n- **[Capacity management](https://www.servicenow.com/docs/access?context=capacity-management-reporting&family=zurich&ft:locale=en-US)**\n\nSupports 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.\n\n- **[Collect operational values for datacenter](https://www.servicenow.com/docs/access?context=enter-operational-values-data-center&family=zurich&ft:locale=en-US)**\n\nManually record operational values of Configuration Items \\(CI\\) and store it in ClothoDB. Use this data for datacenter performance tracking.\n\n- **[Define the datacenter details](https://www.servicenow.com/docs/access?context=define-data-center-details&family=zurich&ft:locale=en-US)**\n\nDefine your datacenter record to view the location-specific attributes for each datacenter, including the campus, buildings, and floors where your network asset is located.\n\n- **[Define the power circuit details](https://www.servicenow.com/docs/access?context=define-power-circuit-details&family=zurich&ft:locale=en-US)**\n\nDefine the power circuit record to represent the electrical pathway that delivers power within a data center.\n\n- **[Define the facility hardware details](https://www.servicenow.com/docs/access?context=define-facility-hardware-details&family=zurich&ft:locale=en-US)**\n\nDefine the facility hardware record to represent power, HVAC \\(Heating, Ventilation, and Air Conditioning\\), network representation, and their connectivity in a data center.\n\n- **[Create a facility model](https://www.servicenow.com/docs/access?context=create-facility-model&family=zurich&ft:locale=en-US)**\n\nCreate a facility model to define the physical characteristics data of the facility record based on the product manufacturer's recommendations.\n\n- **[Create a equipment record](https://www.servicenow.com/docs/access?context=create-equipment-record-design-and-assign&family=zurich&ft:locale=en-US)**\n\nView datacenter records listed in the Equipment task attribute form.\n\n- **[Define the network interface details](https://www.servicenow.com/docs/access?context=define-tni-interfaces&family=zurich&ft:locale=en-US)**\n\nAdd **Wavelength** attribute to the Network Interface form and **Port position** attribute to Interface Model form.\n\n- **[Create an equipment holder model](https://www.servicenow.com/docs/access?context=create-equipment-holder-models&family=zurich&ft:locale=en-US)**\n\nAdded **RU numbering direction** attribute to define the numbering sequence of rack units in the Rack view.\n\n\n |
| \n\nAustralia\n\n | \n\n- **[ServiceNow product tiers](https://www.servicenow.com/docs/access?context=ai-native-sku-overview&family=australia&ft:locale=en-US)**\n\nThe ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:\n\n - Foundation: AI basics to deliver insights\n - Advanced: AI to boost productivity across relevant use cases\n - Prime: Act autonomously with all AI assets, and create your own\nDepending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.\n\n\n - **[Remote Hands Request Management](https://www.servicenow.com/docs/access?context=remote-hands-request-management&family=australia&ft:locale=en-US)**\n\nEnable your customers to request services such as power usage enquiries, equipment installation, equipment restarts, and more by connecting with onsite operations agents at your facility. Securely store your customer requests in the Remote Hands Case table, with role-based access controls. View an auto-generated summary of your requests for quick reference.\n\n\n - **[Remote hands case record](https://www.servicenow.com/docs/access?context=summerizing-remote-hands-case&family=australia&ft:locale=en-US)**\n\nRemote Hands Request Summarization generates contextual summary of a Remote Hands case by combining current case data with insights from similar historical cases, using information submitted by the DCIM user through the CSM portal.\n\n\n - **[IP address management](https://www.servicenow.com/docs/access?context=ip-address-management&family=australia&ft:locale=en-US)**\n\nMulti-layer nested IP Subnetworks with CIDR validation: You can now create IP Subnetworks within IP Subnetworks, supporting recursive nesting for both IPv4 and IPv6. When creating a subnetwork at any level, the system validates that the CIDR is correctly formatted, falls within the parent's range, is more specific than the parent, and is unique within the parent.\n\n\n - **[Inventory template naming patterns](https://www.servicenow.com/docs/access?context=naming-patterns-in-inventory-templates&family=australia&ft:locale=en-US)**\n\nAuthor patterns from a variable library with real-time validation, verify resolved names across the full template hierarchy from a new Overview tab at design time, and add custom validation rules.\n\n- **[Roles](https://www.servicenow.com/docs/access?context=telecom-inventory-roles&family=australia&ft:locale=en-US)**\n\nStandard ServiceNow platform roles no longer have read access to specific TNI tables. This change affects both new installations and upgrades.\n\n\n - **[\\[Placeholder link text to key bundle-telmt.rack-allocation-workflow\\]](https://www.servicenow.com/docs/access?context=rack-allocation-workflow&family=australia&ft:locale=en-US)**\n\nThe rack allocation agentic workflow reserves rack unit space in a datacenter by evaluating placement policies, capacity metrics, and change request requirements to find suitable rack allocations.\n\n\n - **[TNI Data Model Navigator](https://www.servicenow.com/docs/access?context=data-model-navigator&family=australia&ft:locale=en-US)**\n\nA Data Model Navigator is a CMDB framework feature that presents a curated, domain-specific view of the CMDB. With TNI context, it organizes thousands of CMDB CI classes into a focused, hierarchical structure relevant to telecom operations.\n\n\n |
\n