---
sourceDocument: Brazil Telecommunications Service Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/telecom-service-ops

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Telecommunications Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Telecom data model

# Telecom data model {#ariaid-title1}

Release version: Brazil  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
The Telecom data model defines a structured framework for representing telecommunications networks within the CMDB. It extends the core configuration item (CI) model to describe telecom‑specific infrastructure, connections,
and relationships in a consistent and scalable way.

At its core, the Telecom data model organizes network elements such as equipment, interfaces, ports, sites, and connections, and defines how these elements relate to one another. The model captures both physical and logical
aspects of the network and uses containment and consumption relationships to represent how network components are assembled and interconnected. This structure enables accurate modeling of complex telecom environments while
remaining aligned with the standard CMDB architecture.

The Telecom data model is extensible and technology‑agnostic. It provides a common foundation that supports multiple telecommunications domains by reusing existing CMDB classes where possible and introducing new classes only when
telecom‑specific representation is required.

## Key components {#telecom-data-model__section_krx_ysx_1hc}

* Network equipment and hardware: Physical and logical equipment, along with the components they contain, such as interface cards and ports.
* Interfaces and ports: Network interfaces and ports that enable connectivity between devices and services.
* Sites and locations: Logical and physical locations used to group and organize network infrastructure.
* Links, circuits, and connections: Physical and logical connections that describe how network elements communicate and exchange data.
{#telecom-data-model__ul_qgg_1jh_1hc}

## Network equipment classes {#telecom-data-model__section_network_equipment_classes}

The Telecom data model includes network equipment classes that represent specialized telecommunications hardware as children of the Telco Equipment (`cmdb_ci_telco_equipment`) class. The following table describes these classes.
{#telecom-data-model__table_network_equipment_classes__entry__2}

| Class | Description |
|:-|:-|
| Network Packet Broker (`cmdb_ci_network_packet_broker`) | A specialized device that sits between network TAPs or SPAN ports and security and monitoring tools. A network packet broker aggregates, filters, and distributes traffic. Each connected tool receives only the data it needs, which optimizes monitoring performance across high-speed, complex, and hybrid cloud networks. Example devices include the Iris Packet Broker IPB220 and IPB420, and APCON IntellaFlex XR monitoring switches. This class is a child of the Telco Equipment (`cmdb_ci_telco_equipment`) class. |
[Table 1. Network equipment classes]

{#telecom-data-model__table_network_equipment_classes}

## Benefits {#telecom-data-model__section_msq_gjz_1hc}

By providing a consistent way to model telecom infrastructure and relationships, the Telecom data model enables accurate
network inventory, impact analysis, and operational insight. The shared structure supports integration across systems, improves data consistency, and simplifies analysis of network topology and dependencies. This common
modeling approach helps teams manage complex networks more effectively and supports use cases such as service visibility, operational monitoring, and lifecycle management.

## Domain‑specific data models {#telecom-data-model__section_tnz_lpv_l3c}

Domain‑specific data models build on the Telecom data model by refining and specializing its classes for particular network technologies. These models reuse the core structure of the Telecom data model while introducing domain‑specific attributes and relationships as needed. The SD‑WAN data model is one example of a domain‑specific data model. It focuses on the subset of Telecom data model concepts that are relevant to SD‑WAN environments. It applies them to represent SD‑WAN topology, services, and operations while remaining consistent with the broader Telecom data model.
**Related concepts**   

* [SD-WAN data model](https://www.servicenow.com/docs/Xgqod~_cpGCd8j2JdPW5VQ "The ServiceNow AI Platform uses a custom data model that defines how SD-WAN connectors discover and retrieve device information.")  
**Related topics**   

* [Data model](https://www.servicenow.com/docs/access?context=uses-for-network-inventory-data&version=brazil&pubname=brazil-telecom-network-inventory&ft:locale=en-US)