Telecom Discovery Builder framework
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.
| 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) |
Includes the application properties. |
sn_sgc_fortinet(Service Graph Connector for Fortinet) |
Includes the application properties. |
The following table lists the roles contained in the tsom_visibility_admin role.
| Role name | Description |
|---|---|
import_admin |
|
connection_admin |
|
sn_cmdb_admin |
|
discovery_admin |
|
usage_admin |
|
cmdb_inst_admin |
|
certification_admin |
|
agent_admin |
|
Key benefits
- 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.