---
sourceDocument: Australia Telecommunications Service Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/telecom-service-ops

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Telecommunications Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Configure Telecom Discovery Builder

# Configuring the Telecom Discovery Builder framework ETL in a connector {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.

The Telecom Discovery Builder framework ETL provided with the Telecom Service Operations Management (TSOM) Core is a ready-to-use framework designed to streamline data ingestion into the CMDB across telecom connectors. Rather than
configuring it directly, as an administrator, you can duplicate the ETL into a connector's application scope and update the data source to align with the connector's discovery payload.

## Steps to use the Telecom Discovery Builder framework ETL in a connector {#configuring-the-telco-generic-schema-etl__section_m1l_5p4_ffc}

1. Create a temporary data source: Create a data source in your connector's application scope based on the Generic Schema multi source data source from TSOM Core. This enables you to run and test the duplicated ETL with schema-aligned placeholder data. For more information, see [Create a data source similar to Telecom core data source](https://servicenow-prod.fluidtopics.net/5Oa8UlBOcnKBSSe~pJrqoA "Set up a schema-compliant data source in the connector’s application scope to simulate telecom data and ensure successful testing and validation of the Telecom Discovery Builder framework ETL before integrating with live device data.")
2. Duplicate the Telecom Discovery Builder framework ETL: Access ETL Studio, locate the Telco Generic Schema ETL, and duplicate it into the connector's scope. During duplication: Provide a new name. Assign the temporary data source. Use importSet as the discovery source. For more information, see [Duplicate the Telecom Discovery Builder framework ETL into a connector scope](https://servicenow-prod.fluidtopics.net/7AVRK5Fms_hGjXImZtQwcQ "The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch.")
3. After duplication, open the new ETL and replace the temporary data source with the connector's actual discovery data source. For more information, see [Update the data source of the connector](https://servicenow-prod.fluidtopics.net/620Qp0bDzsuVn7AhohG7xw "Link the duplicated ETL to a valid data source for your specific connector.").
4. Test or deploy the service graph connector. For more information, see [Deploy a new service graph connector with existing ETL](https://servicenow-prod.fluidtopics.net/2mdB6p4uFI_d_RnebqSNBg "Associate a new Service Graph Connector (SGC) with an existing ETL.")
{#configuring-the-telco-generic-schema-etl__ol_uvh_vp4_ffc}