Telecom Discovery Builder framework

  • Release version: Australia
  • Updated March 12, 2026
  • 4 minutes to read
    • Summarize
    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 Builder framework

    The Telecom Discovery Builder framework ETL is a reusable, schema-aligned data ingestion component included in the Telecommunications Service Operations Management (TSOM) Core application. It streamlines and standardizes the process of importing telecom inventory data into the ServiceNow CMDB through multiple Service Graph Connectors (SGCs). By providing a generic, baseline ETL, it eliminates the need for connector teams to build data transforms from scratch and ensures consistent, compliant telecom configuration item (CI) data ingestion aligned with Telecommunications Network Inventory (TNI) standards.

    Show full answer Show less

    Once the TSOM Core plugin is activated, the generic ETL is auto-provisioned and accessible via Integration Hub ETL Studio, where it can be duplicated and customized to meet specific connector requirements without modifying core logic.

    When to Use the Telecom Discovery Builder framework

    • Deploying new telecom Service Graph Connectors while avoiding custom ETL development.
    • Maintaining schema-aligned consistency and TNI-compliant CI relationships across multiple connectors and instances.
    • Customizing ETL behavior within the SGC application scope via a UI-driven interface with validated JSON schema support and predefined mappings.

    Key Features

    • Auto-provisioned with TSOM Core: Immediately available for use across telecom connectors upon plugin activation.
    • Generic schema-based ingestion: Supports a unified telecom CI data model compliant with TNI.
    • Duplication and customization: Enables reuse and tailored extension of ETL logic for specific connectors through Integration Hub ETL Studio.
    • Flexible field-mapping interface: Allows configuration of import sets, data sources, targets, and transformation logic via an intuitive UI.

    Key User Roles

    The framework’s access is controlled through granular roles to ensure secure management within TSOM Visibility and Assurance scopes:

    • tsomvisibilityadmin: Manages operational tasks in TSOM Visibility applications.
    • tsomassuranceadmin: Provides full operational and administrative capabilities for TSOM Assurance applications.

    Additional roles support specific administrative functions such as import execution monitoring, connection management, CMDB administration, discovery configuration, usage tracking, ETL integration development, certification auditing, and MID Server management.

    Benefits for ServiceNow Customers

    • Ensures consistency and compliance when ingesting telecom CI data into the CMDB, reducing errors and fragmentation.
    • Accelerates deployment of telecom connectors by providing a reusable ETL foundation.
    • Facilitates tailored data transformations without compromising the underlying TNI-aligned schema.
    • Supports governance and security through role-based access control aligned with TSOM application scopes.

    Next Steps

    ServiceNow customers can configure and extend the Telecom Discovery Builder framework ETL within their connectors to support additional TNI entities or customize data ingestion processes. Leveraging this framework simplifies telecom inventory data management and integration across their ServiceNow environment.

    The Telecom Discovery Builder framework ETL (Extract, Transform, Load) is a reusable and schema-aligned component delivered with the Telecommunications Service Operations Management (TSOM) Core application. It provides a consistent and extensible method for ingesting telecom inventory data into the ServiceNow configuration management database (CMDB) across multiple Service Graph Connectors (SGCs).

    The Telecom Discovery Builder framework ETL serves as a baseline data ingestion utility to handle telecom-specific configuration item (CI) data. It enables connector development teams to avoid building ETLs from scratch by offering a standardized transform logic that can be duplicated and customized for each connector. It provides a standardized, reusable foundation that promotes consistency across implementations.

    Once the TSOM Core plugin is activated, the generic ETL is auto-provisioned and becomes available in the Integration Hub ETL Studio, ready to be reused and adapted to connector-specific needs.

    Why and when to use the Telecom Discovery Builder framework

    Use the Telecom Discovery Builder framework when you want to do the following:

    • Deploy a new Service Graph Connector in a telecom environment and want to avoid building the ETL from scratch.
    • Maintain schema-aligned consistency across multiple connectors and platform instances.
    • Discovery payloads and CI relationships compliant with TNI (Telecommunications Network Inventory). For more information, see Telecommunications Network Inventory.
    • Work within an SGC (Service Graph Connector) application scope and want to customize ETL behavior without modifying core logic.
    • Benefit from predefined mappings, validated JSON schema support, and a UI-driven configuration interface.

    Key capabilities and features

    • Auto-provisioned with TSOM core: Installs automatically and is ready to use across telecom connectors.
    • Generic schema-based ingestion: Supports a unified data schema for telecom CIs.
    • Supports duplication and customization: Duplicate the Telecom Discovery Builder ETL framework into your application scope using Integration Hub ETL Studio.
    • TNI support: Aligned to the TNI data model and the ETL logic can be extended to generate and link TNI entities.
    • Flexible field-mapping interface: Configure import sets, data sources, targets, and transformation logic through a UI-driven experience.

    Key user roles

    The tsom_visibility_admin and tsom_assurance_admin roles provide granular access control across TSOM Visibility and Assurance application scopes, supporting stronger security and compliance in line with the Granular admin directive.

    • The tsom_assurance_admin role provides full operational and administrative access to TSOM Assurance application scopes.
    • The tsom_visibility_admin role manages the operational tasks for the TSOM visibility application.
    These roles control access to the TSOM Visibility and Assurance application scopes listed in the following table.
    Table 1. TSOM Visibility and Assurance application scopes
    Scope name Description
    sn_tsom_core (Telecom Service Operations Core) Includes the audit application and various system properties within that app scope.
    sn_tsom_em_core(Event Management Core) Includes the monitoring and analysis of telecommunications network alerts and performance metrics from SD-WAN infrastructure.
    sn_tsom_em_connect(Event Management Connectors) Include push connectors and connector definitions used to ingest alerts from external telecommunications network sources.
    sn_tsom_patterns(Telecom Discovery Patterns ) Include the MID Server and system IP Service properties.
    sn_sgc_aliplano(Service Graph Connector for Nokia Altiplano) Includes the application properties.
    sn_sgc_meraki(Service Graph Conenctor for Cisco Meraki Telco SD-WAN) Includes the application properties.
    sn_sgc_fortinet(Service Graph Connector for Fortinet Telco SD-WAN) Includes the application properties.

    The following table lists the roles contained in the tsom_visibility_admin role.

    Table 2. Visibility granular admin roles
    Role name Description
    import_admin
    • Monitors scheduled data import executions, including viewing the hierarchy and flow of chained imports, accessing execution contexts, and diagnosing import issues.
    • Manages all aspects of import set records and imports.
    connection_admin
    • Responsible for managing connections and credentials, especially for Integration Hub.
    • Create and configure HTTP and HTTPS connections, which are used by custom actions or activities to connect to external endpoints. These actions include setting up connection details such as credentials, connection aliases, URLs, MID Server options, and additional attributes.
    sn_cmdb_admin
    • Highest-level administrative role for CMDB privileges.
    • Grants full access to CMDB data, tools, and user interfaces, and enables administrators to configure policies such as class management and application service requirements that aren’t available to editors.
    discovery_admin
    • Grants access to the tables in the Discovery application.
    • Essential for configuring and executing discovery in your network.
    • Includes setting up MID Servers, managing credentials, defining discovery schedules, and validating results.
    usage_admin
    • For instances using Discovery, this role enables users to track the number of active users and hardware configuration items (CIs) discovered.
    • Monitors instance usage through dashboards, providing information to help your organization understand application adoption and usage patterns.
    cmdb_inst_admin
    • Enables users to create and customize integrations using Integration Hub ETL, including integrating third-party data into CMDB or supported non-CMDB tables.
    • Necessary to use the Integration Hub ETL store app and access CMDB Integrations.
    certification_admin
    • Enables users to manage certification filters for auditing subsets of records.
    • Create, update, delete, and run certification audits, compare records against expected values, and assign follow-on tasks to remediate discrepancies.
    • Manage and reassign follow-on tasks from compliance audits and view all such tasks. Users with the certification role can access only tasks assigned to them.
    agent_admin
    • Responsible for downloading and administering the system's built-in MID Server agent.
    • Enables users to manage scripts and properties related to the MID Server.

    Key benefits

    Benefits of the Telecom Discovery Builder framework ETL include:
    • Consistency in how telecom configuration items (CIs) are structured and loaded into the CMDB.
    • Reusability through duplication and customization across connectors.
    • Compliance with TNI schemas and discovery model requirements.
    • Flexibility to extend and tailor data transformations without compromising the base schema.