Telecom data model
Summarize
Summary of Telecom data model
The Telecom data model provides a structured, scalable framework within the ServiceNow CMDB to represent telecommunications networks. It extends the core configuration item (CI) model to accurately capture telecom-specific infrastructure, including physical and logical network elements such as equipment, interfaces, ports, sites, and connections. By defining containment and consumption relationships, the model reflects how network components interconnect and operate together, aligning with standard CMDB architecture.
Show less
Key Features
- Extensible and technology-agnostic: Supports multiple telecom domains by reusing existing CMDB classes and introducing new ones only when necessary for telecom-specific needs.
- Comprehensive network representation: Covers physical and logical equipment, interfaces, ports, sites, locations, and connections, enabling detailed topology and infrastructure mapping.
- Specialized network equipment classes: Includes classes such as Network Packet Broker (cmdbcinetworkpacketbroker), a child of Telco Equipment (cmdbcitelcoequipment), which manages traffic filtering and distribution for monitoring tools across complex networks.
- Domain-specific data models: Builds on the core Telecom data model to specialize for technologies like SD-WAN, introducing relevant attributes and relationships while maintaining consistency.
Key Outcomes
- Enables accurate network inventory and operational insight through consistent modeling of telecom infrastructure and relationships.
- Supports impact analysis and simplifies understanding of network topology and dependencies.
- Facilitates integration across systems by providing a common structural foundation, improving data consistency and reliability.
- Enhances management of complex telecom networks, supporting use cases like service visibility, operational monitoring, and lifecycle management.
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
- 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.
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.
| 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 so that 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. |
Benefits
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
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 and applies them to represent SD‑WAN topology, services, and operations, while remaining consistent with the broader Telecom data model.