How to Model Fiber in ArcGIS Inside Esri's New Telecom Domain Network (TDN)

A fiber cable appears as one line on a map. Inside the single cable are dozens or hundreds of strands that pass through splices, connectors, splitters, hubs, and other equipment.

This level of detail creates a common telecom GIS challenge of representing the network accurately for modeling and analysis without cluttering the map or creating hundreds of individual database records. Esri's new Telecom Domain Network (TDN) addresses this problem through three core concepts: nonspatial objects, grouping, and circuit management.

Fiber Network Modeling Challenges in GIS

Traditional approaches to fiber modeling produce excessive numbers of records and cluttered, difficult-to-read maps. A 288-strand cable may require a separate record for each strand, and those records multiply quickly across a network. Displaying every strand, splice, port, and equipment component spatially can also overwhelm the map, especially for field users who need a clear view of the network.

Tracing the network presents a different challenge. Traditional domain ArcGIS® Utility Networks such as water, gas, and electric commonly use subnetworks to organize and trace operational systems, such as pressure zones. Telecom networks do not have the same asset organization and depend on discrete signal paths that pass through specific strands, ports, splices, and equipment. The Telecom Domain Network reflects this difference by using circuits instead of subnetworks to support end-to-end telecom tracing.

How the Telecom Domain Network Organizes Data

The TDN retains familiar Utility Network classes for assets that belong on the map. Devices and junctions represent equipment or connection locations, lines represent cables, and assemblies serve as visible containers for detailed equipment.

Data modeling in the Telecom Domain Network utilizes the non-spatial objects tables (Edge and Junction Object) to keep the map easy to understand while retaining the detail needed for connectivity and tracing. 

Individual telecom components are stored in non-spatial tables. Junction objects represent items such as connectors, ports, switches, and splice cases. Edge objects represent individual fiber strands. The model also includes Circuit, CircuitSection, and Subcircuit tables for circuit management.

Grouping High-Count Fiber Cables

Grouping is a major change in how fiber data is stored. Instead of creating one row for every strand, one edge-object record can represent a contiguous range.

For example, a 288-strand cable can contain an edge object with a First Unit of 1 and a Last Unit of 288. This one row of data represents all 288 strands. When strands 1 through 12 are spliced to a different cable, the range divides into two records: one record representing strands 1 to 12 and another record representing strands 13 to 288.

Each strand keeps its identity as the individual strand, or unit identifier. Grouping simply reduces the number of database records that staff maintain, thereby reducing data volume.

Tracing Individual Strands and Circuits

Grouping does not remove strand-level tracing. In ArcGIS® Pro, a user selects the underlying object and identifies a specific unit as the starting point. A connected trace then follows that strand through the network. For example, a trace can follow strand 1 from a residential network interface unit back to the regional hub.

In addition to tracing an individual fiber strand, the TDN allows users to work with defined circuits. In ArcGIS Pro, a user selects a feature or object and uses Find Circuits to identify the circuits that pass through it. From there, the Trace Circuit tool selects the features and objects that make up the circuit, providing a clear view of its path and boundaries across the network. 

In addition to tracing an individual fiber strand, the TDN allows users to work with defined circuits. In ArcGIS Pro, a user selects a feature or object and uses Find Circuits to identify the circuits that pass through it. From there, the Trace Circuit tool selects the features and objects that make up the circuit, providing a clear view of its path and boundaries across the network. 

Telecom Domain Network Deployment Requirements

To deploy the initial TDN, the following is required:

• ArcGIS® Enterprise 12.1 or later

• ArcGIS Pro 3.7 or later

• Utility Network Version 8

  
  

As of August 2026, the TDN is in Esri’s early release program, with anticipated general availability in late 2026.

Frequently Asked Questions (FAQs)

Can the Telecom Domain Network be deployed in ArcGIS® Online?

No, the Telecom Domain Network and traditional ArcGIS Utility Networks require ArcGIS Enterprise and cannot be deployed to ArcGIS Online. 

Does grouping prevent users from working with individual fiber strands?

No, each strand retains a unit identifier. Users select a specific unit or range for editing, connectivity, and tracing even when one row stores the grouped strands.

What does the TDN store as a nonspatial object?

Junction objects represent internal items such as ports, connectors, splice cases, and equipment components. Edge objects represent individual fiber strands. These objects remain logically connected to the spatial assets that contain them.

How are circuits different from subnetworks?

Subnetworks organize traditional utility systems around subnetwork controllers and tiers. Telecom Domain Network circuits represent telecom paths between defined locations. Circuit tools allow users to find, trace, and manage those paths.

Need expert guidance on implementing the Telecom Domain Network or upgrading your Utility Network?

Cloudpoint's team of GIS experts is ready to help. Contact us today to learn more!