--- sourceDocument: Yokohama Telecommunications Service Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/telecom-service-ops Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Telecommunications Service Operations Management ft:clusterId : - tsom bundleId : - tsom workflow : - Customer and Industry --- # Telecom Discovery using Service Graph Connectors (SGC) # Telecom Discovery using Service Graph Connectors (SGC) {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](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 Telecom Discovery using Service Graph Connectors (SGC) Telecom Discovery using Service Graph Connectors (SGC) enables ServiceNow customers to integrate network data from telecom-specific third-party sources into the Configuration Management Database (CMDB). These predefined connectors collect and structure data from various network domains, such as EMS/NMS/Controllers managing xNFs, providing a telecom-model-aligned view of network resources and services. SGCs complement existing connectors for other domains like security, servers, software, IoT, and cloud. Show full answer Show less ## Key Components and Architecture * **IntegrationHub ETL:** A ServiceNow Store app that simplifies creating and managing ETL transform maps. It helps import third-party data into the CMDB or other tables with guided integration workflows and test runs. * **Robust Transform Engine (RTE):** Transforms raw staging table data into CMDB-compliant records using ETL transform maps. * **MID Server:** A Java application running inside the customer's network that facilitates secure data transfer between ServiceNow and external telecom systems. * **Identification \& Reconciliation Engine (IRE):** Centralizes data identification and reconciliation from multiple sources to maintain CMDB integrity. * **CMDB Compliance Certification Audits:** Used to validate CMDB data accuracy, identify discrepancies, and trigger remediation workflows for telecom-specific data. * **TNI Entity Creation Logic:** Automatically creates TNI entity records for network data if the Telecom Network Inventory (TNI) plugin is installed, linking discovered CIs across related tables. ## Supported Service Graph Connectors and Versions Telecom SGCs currently include the Service Graph Connector for Nokia Altiplano, which integrates data from Nokia Altiplano Access Network SDN Controllers via REST APIs. This connector supports ServiceNow Yokohama and later releases. The guided setup streamlines configuration, including authentication and scheduling, to pull network resource data into the CMDB. ## Practical Benefits for ServiceNow Customers * Automates and standardizes telecom network data ingestion into the CMDB, improving data accuracy and consistency. * Supports integration with diverse network domains while maintaining a structured, telecom-aligned data model. * Enables comprehensive CMDB integrity checks and discrepancy remediation through certification and reconciliation tools. * Offers extensibility to include TNI data, enhancing network inventory visibility within ServiceNow. * Facilitates faster and more reliable network discovery and service mapping, critical for telecom operations and service management. Service Graph Connectors are predefined integrations that ingest data into the Configuration Management Database (CMDB) from third-party sources (for example, northbound APIs of EMS/NMS/Controllers, which manage various xNFs) across different network domains, while enabling a structured, telecom-model-aligned view of network resources and services. They can be used alongside any existing Service Graph Connectors, such as those for security, servers, software, monitoring, internet of Things (IoT), and cloud. ## Architecture using Telecom Service Graph Connectors {#telecom-discovery-using-service-graph-connector__section_axl_zrf_12c} This is an example of the implementation for the Nokia Altiplano Service Graph Connector. The architecture of other connectors may vary. ## IntegrationHub ETL (3.2) {#telecom-discovery-using-service-graph-connector__section_ejw_2sf_12c} This store app to create and manage ETL transform maps, which integrate third-party data into the CMDB or into non-CMDB tables without compromising the integrity of data. IntegrationHub ETL provides a simplified user interface that guides you through the integration process end-to-end, including a test integration run of sample data. For more information, see [IntegrationHub ETL](https://www.servicenow.com/docs/access?context=integrationhub-etl&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). ## Robust Transform Engine (RTE) {#telecom-discovery-using-service-graph-connector__section_sdr_msf_12c} This plugin is used to transform raw source data that is stored in staging tables, into the data that is mapped and integrated into the CMDB. RTE uses ETL transform maps that were created for integration during data transformation. For more information, see [Create a robust import set transformer](https://www.servicenow.com/docs/access?context=create-robust-import-set-transformer&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US). ## MID Server {#telecom-discovery-using-service-graph-connector__section_ip3_psf_12c} MID Server is a Java application that runs as a Windows service or UNIX daemon on a server within your local network. The ServiceNow® MID Server facilitates communication and data transfer between a ServiceNow instance and external applications, data sources, and services. For more information, see [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). ## Identification \& Reconciliation Engine (IRE) {#telecom-discovery-using-service-graph-connector__section_tql_ssf_12c} IRE offers a centralized framework for identifying and reconciling data from multiple sources. It confirms the integrity of the CMDB and some non-CMDB tables when various data sources are used to create or update CI records. For more information, see the [CMDB Identification and Reconciliation (IRE)](https://www.servicenow.com/docs/access?context=c_CMDBIdentifyandReconcile&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). ## CMDB Compliance Certification Audits for Telecom Discrepancy Identification \& Reconciliation {#telecom-discovery-using-service-graph-connector__section_pf1_vsf_12c} [CMDB Compliance](https://www.servicenow.com/docs/access?context=c_Compliance&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) is a toolset that enables administrators to certify CMDB data for accuracy and resolve any discrepancies found. In Telecom Discrepancy Identification \& Reconciliation, we use the [Certification audits](https://www.servicenow.com/docs/access?context=c_CertificationAudits&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) feature to discover and analyze discrepancies in the CMDB, generate [Certification follow-on tasks](https://www.servicenow.com/docs/access?context=c_CertificationFollowOnTasks&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US), and enable remediation workflows. For more information on how it's used for Discrepancy Identification \& Reconciliation, see [Telecom Discrepancy Identification and Reconciliation](https://www.servicenow.com/docs/SOGZrFfCJ5tSkJGZlOLDSA "Telecom Discrepancy Identification & Reconciliation confirms that ServiceNow’s CMDB/TNI accurately reflects the updated state of the network and remains synchronized with planned or designed inventory resources."). ## TNI Entity Creation Logic {#telecom-discovery-using-service-graph-connector__section_v2r_zsf_12c} Whenever the system identifies that the customer has TNI installed, it will automatically create a TNI entity record for all network data discovered. If TNI is installed, a payload like the following one will be added to the IRE payload for each item (with inventory_category populated based on the className): related = [{ "className": "tni_entity", "values": { "inventory_category": "" } }]; As a result, the discovered CI is in both the cmdb_ci and tni_entity tables. ## Telecom Service Graph Connectors supported {#telecom-discovery-using-service-graph-connector__Toc185821020} [Service Graph Connector for Nokia Altiplano](https://www.servicenow.com/docs/~M5JbLrlXndnkWKa6rg8gw#service-graph-connector-for-nokia-altiplano "Use the Service Graph Connector for Nokia Altiplano Access Network SDN Controller to pull in data from the Nokia Altiplano software into your ServiceNow instance using REST APIs."). See other available [Service Graph Connectors](https://www.servicenow.com/docs/access?context=cmdb-sgc-available&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). ## Supported versions {#telecom-discovery-using-service-graph-connector__section_pd4_h3g_g2c} Supported ServiceNow® versions: Yokohama and beyond. * **[Service Graph Connector for Nokia Altiplano](https://www.servicenow.com/docs/~M5JbLrlXndnkWKa6rg8gw#service-graph-connector-for-nokia-altiplano)** Use the Service Graph Connector for Nokia Altiplano Access Network SDN Controller to pull in data from the Nokia Altiplano software into your ServiceNow instance using REST APIs. * **[Configure Service Graph Connector for Nokia Altiplano](https://www.servicenow.com/docs/apjvQ1LaZ1EysUpIAFG59Q#configuring-service-graph-connector-nokia-altiplano)** Configure the Service Graph Connector for Nokia Altiplano using Guided setup to integrate network resource data from the Nokia Altiplano Access Controller (REST API) into the ServiceNow CMDB. The setup includes authentication and scheduling steps.