--- sourceDocument: Australia Telecommunications Network Inventory sourceDocumentLink: https://www.servicenow.com/docs/r/australia/telecom-network-inventory Release : - australia ft:locale : - en-US ft:publication_title : - Australia Telecommunications Network Inventory ft:clusterId : - telninv bundleId : - telninv workflow : - Customer and Industry --- # TNI Data Model Navigator # TNI Data Model Navigator {#ariaid-title1} Release version: Australia Updated November 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 TNI Data Model Navigator The TNI Data Model Navigator is a specialized feature within the CMDB framework designed to provide a curated, domain-specific view of telecom-related configuration items (CIs). It organizes thousands of CMDB CI classes into a hierarchical structure tailored to telecommunications network inventory management. This focused view simplifies navigation and enables telecom operations teams to efficiently access and manage relevant infrastructure data. Show full answer Show less ## Key Features * **Contexts:** Hierarchical groupings that define operational domains, starting from broad parent contexts to more focused child contexts. Each context includes mapped tables, fields, and relationships specific to telecom infrastructure layers. * **Telecom Network Inventory (TNI) Context Hierarchy:** The parent TNI context contains child contexts representing telecom infrastructure layers such as Physical (fiber cables, splice closures), Logical (PON paths, VLAN circuits), Services (service instances), Site (containers and racks), Facilities (power, cooling), and Topology (network views). * **Tables (CI Class Descriptions):** Metadata defining what each CMDB CI class tracks, its purpose, and how it varies across contexts. For example, the Optical Fiber Cable table describes physical cables containing fiber strands and their role in telecom transmission. * **Fields (Critical Attributes):** Detailed metadata on important attributes within each CI class, explaining their significance in different use cases (e.g., GPON planning, inventory management) and providing sample values. For instance, the "strandcount" field indicates the number of fiber strands, critical for capacity planning. * **Relationships:** Metadata describing how CI classes interconnect, the rationale behind these connections, and their relevance to various use cases. Examples include services containing logical paths and logical paths riding over physical fiber links, which are essential for service mapping, billing, topology mapping, and troubleshooting. ## Key Outcomes * Enables ServiceNow customers in telecom operations to navigate a complex CMDB more efficiently by focusing only on relevant data for their domain. * Supports accurate modeling of telecom infrastructure layers and their interconnections, facilitating comprehensive end-to-end service mapping and network topology understanding. * Improves decision-making by highlighting critical attributes and relationships, ensuring users know which data points impact planning, provisioning, and inventory management. * Provides agents and users with realistic examples and clear metadata, enhancing usability and reducing errors in telecom network inventory management. A Data Model Navigator is a CMDB framework feature that presents a curated, domain-specific view of the CMDB. With TNI (Telecommunications Network Inventory) context, it organizes thousands of CMDB CI classes into a focused, hierarchical structure relevant to telecom operations. Data Model Navigator framework stores and organizes metadata in four interconnected components: * Contexts: Hierarchical Organization * Tables: CI Class Descriptions * Fields: Critical Attributes * Relationships: How tables connect with one another {#data-model-navigator__ul_j25_pry_5jc} ## Context {#data-model-navigator__section_nxm_3ny_5jc} A model context is a curated view of the Configuration Management Database (CMDB) that organizes CI classes, fields, and relationships around a specific operational domain. Instead of requiring you to navigate thousands of CI classes in the full CMDB hierarchy, a model context shows only the data relevant to your work. Contexts are hierarchical. A parent context defines the broadest domain grouping. Child contexts subdivide it into focused subdomains, each carrying its own mapped tables, documented fields, and defined relationships. ## Telecom Network Inventory (TNI) Context Hierarchy {#data-model-navigator__section_iqc_rhw_zjc} The Telecom Network Inventory is a parent context containing the following child contexts, each representing a layer of telecom infrastructure: * TNI Physical: Fiber infrastructure (cables, strands, splice closures, cross-connect panels) * TNI Logical: Logical paths that ride over physical (PON paths, VLAN circuits, MPLS LSPs) * TNI Services: Service instances that contain logical paths * TNI Site: Site-level containers and racks * TNI Facilities: Power, cooling, physical plant infrastructure * TNI Topology: Network topology views and relationships {#data-model-navigator__ul_c4n_f4y_5jc} ## Tables --- CI Class Descriptions {#data-model-navigator__section_ohj_y4y_5jc} Metadata describing what each CMDB CI class tracks, its purpose, and variations across contexts. Example: Optical Fiber Cable Table. {#data-model-navigator__table_uk3_mpy_5jc__entry__2} | Field | Description | |-|-| | Table name | cmdb_ci_optical_fiber_cable | | Purpose | Physical cable containing individual fiber strands for telecom transmission. Cables bundle multiple fibers for protection and routing through infrastructure. | | Context | TNI Physical layer | | GPON Planning use case | Determines splitter capacity and service provisioning | | Inventory Management use case | Tags equipment and tracks deployment | | Capacity Planning use case | Aggregates service capacity by cable | [ ] {#data-model-navigator__table_uk3_mpy_5jc} ## Fields --- Critical Attributes {#data-model-navigator__section_d4y_qpy_5jc} Field-level metadata describing critical attributes, their importance across use cases, and sample values. Example: Fiber Cable Fields. Field 1: strand_count. {#data-model-navigator__table_dff_cqy_5jc__entry__2} | Aspect | Details | |-|-| | Description | Number of individual fiber strands contained in this cable | | GPON Planning (CRITICAL) | Determines how many circuits this cable can support | | Inventory (INFORMATIONAL) | Tags equipment specification | | Sample data | "24", "48", "96" | [ ] {#data-model-navigator__table_dff_cqy_5jc} Field Metadata = Describes individual fields within a CI class table, their purpose across use cases, and sample values. Field metadata are important because it enables the agent to know which fields matter for which decisions and to provide realistic examples to users. ## Relationships {#data-model-navigator__section_xz1_lqy_5jc} Metadata describing how CI classes relate to each other, why those relationships exist, and their importance in different use cases. Relationship 1: Service Contains Logical. {#data-model-navigator__table_zxp_5qy_5jc__entry__2} | Field | Value | |-|-| | Source | cmdb_ci_connection_service_instance (service layer) | | Target | cmdb_ci_nl_logical_path (logical layer) | | Modeling reason | Customer services ride over logical connectivity paths | | Critical for | End-to-end service mapping, customer billing | [ ] {#data-model-navigator__table_zxp_5qy_5jc} Relationship 2: Logical Rides Over Physical. {#data-model-navigator__table_z3g_wqy_5jc__entry__2} | Field | Value | |-|-| | Source | cmdb_ci_nl_logical_path (PON path) | | Target | cmdb_ci_nl_physical_link (fiber span) | | Modeling reason | Logical connectivity requires physical fiber to carry signals | | Critical for | Network topology mapping, troubleshooting, capacity planning | [ ] {#data-model-navigator__table_z3g_wqy_5jc} Relationship Metadata: Describes how CI classes connect across TNI layers and why those relationships matter. Understanding Relationship Mapping: An agent understands how to traverse the data model (Service → Logical → Physical → Equipment) to answer complex questions. **Related tasks** * [Access the TNI data model navigator](https://www.servicenow.com/docs/X7dOt40U~zUPGDNvETu5ww "Access the TNI data model navigator to view the contextually organised CMDB CI classes into a focused, hierarchical structure relevant to telecom operations.")