Routing is one of those topics that sounds straightforward until you actually try to implement it. For utility and infrastructure organizations, getting routing right in a network can mean the difference between responding to an outage in minutes and spending hours tracing the wrong path through a tangle of assets. Whether you manage water pipes, gas lines, electrical cables, or telecommunications infrastructure, understanding how to set up routing properly is worth your time.

This article walks through the key questions teams ask when approaching utility network routing—from the basics of what it is to the mistakes that quietly undermine even well-planned configurations. Each section gives you a direct answer and the context you need to act on it.

What is routing in a utility network? #

Routing in a utility network is the process of tracing a connected path through a network of assets—such as pipes, cables, or conduits—from one point to another. It uses the logical and physical connections between network elements to determine how flow, signals, or resources travel from a source to an endpoint, or to identify which assets are affected by a given event.

In practical terms, routing lets you answer questions like: Which customers lose water if this valve closes? Which sections of the electrical grid are fed by this substation? Which gas pipes connect back to this pressure regulation point? These are not abstract questions. They drive real operational decisions every day in field operations, outage management, and infrastructure planning.

Routing is distinct from simple map visualization. A map shows you where assets are. Routing shows you how they connect and what the consequences of changes or failures are. That distinction matters enormously when you are managing a network that spans hundreds of kilometers and serves thousands of end users.

Why does routing matter for utility and infrastructure management? #

Routing matters because utility networks are not collections of isolated assets. They are interdependent systems in which a single point of failure can cascade through dozens of connected elements. Without routing capability, you cannot quickly determine the scope of an outage, plan maintenance safely, or model the impact of infrastructure changes before they happen.

Consider outage management as a concrete example. When a pipe bursts or a cable fails, the first question is always: Who is affected? Answering that question manually—by tracing connections through paper records or static maps—takes time that customers and regulators do not have the patience for. Routing automates that trace and delivers the answer in seconds.

Beyond incident response, routing supports proactive operations as well. You can use it to model isolation zones before planned maintenance, ensuring field crews know exactly which valves to close and which customers to notify. You can analyze flow paths to identify bottlenecks or areas of vulnerability before they cause problems. In asset replacement planning, routing helps you understand which sections of your network are load-bearing in a logical sense, not just a physical one.

For organizations managing complex infrastructure, spatial analysis for infrastructure network intelligence built on solid routing logic is what transforms raw asset data into operational intelligence. Those insights only become useful when the underlying network connections are reliable and queryable.

What data do you need before setting up utility network routing? #

Before setting up utility network routing, you need three categories of data: accurate geometric data describing where assets are located, attribute data describing what each asset is and how it behaves, and connectivity data defining how assets physically and logically connect to one another. Without all three, your routing model will produce incomplete or incorrect results.

Geometric data #

Geometric data is your foundation. Every pipe segment, cable run, valve, fitting, junction, and endpoint needs a spatial representation that reflects its actual location. Positional accuracy matters here. If two pipes appear to connect on a map but their coordinates do not actually share an endpoint, the routing engine will not recognize the connection.

Attribute and connectivity data #

Attribute data tells the routing engine how each asset behaves. For a valve, this includes whether it is normally open or normally closed, and what its current operational state is. For a pipe, it includes flow direction, diameter, and material. For an electrical switch, it includes whether it is open or closed. These attributes are what allow routing to reflect real-world network conditions rather than just theoretical geometry.

Connectivity data is often the most labor-intensive to prepare, especially in older networks where records are incomplete or inconsistent. You need to know not just that two assets are geographically close, but that they are actually connected in the network model. This is where data quality work becomes important before you even begin routing configuration. Gaps in connectivity records will create breaks in your routing traces that lead to misleading results.

How does network topology affect routing accuracy? #

Network topology directly determines routing accuracy because routing algorithms depend entirely on the topological relationships between assets. Topology defines which elements are connected, the direction in which flow can travel, and where the network branches or terminates. If your topology is incorrect or incomplete, your routing traces will stop prematurely, skip sections, or follow paths that do not reflect reality.

Topology errors come in several common forms. Gaps between asset endpoints that should be connected are among the most frequent. A pipe segment that ends one meter short of a junction will break the routing trace at that point, even though the physical connection exists. Duplicate geometries—where two assets occupy the same space without being logically connected—create similar problems. Incorrect flow-direction assignments on directed networks, such as pressurized water systems, will cause routing to travel in the wrong direction entirely.

Maintaining clean topology is an ongoing process, not a one-time setup task. Every time a new asset is added, modified, or retired, the topological relationships need to be verified. Organizations that treat topology as a data-quality issue to solve once and then ignore tend to find their routing results drifting from reality over time as the network evolves but the model does not.

Investing in automated topology validation—where the system flags connectivity breaks or inconsistencies as data is edited—pays off significantly in the long run. It keeps the routing model aligned with the physical network without requiring manual audits after every change.

What tools and platforms support utility network routing? #

Utility network routing is supported by GIS platforms with network analysis capabilities, dedicated network modeling software, and integrated geospatial solutions built specifically for infrastructure management. The right choice depends on your network type, data environment, and the operational workflows you need to support.

GIS platforms with built-in network analysis functions allow you to build topological network models on top of your existing spatial data. These platforms typically offer trace analysis, isolation analysis, and upstream or downstream tracing as standard capabilities. They work well when your team already manages spatial data in a GIS environment and you want routing to sit alongside your existing visualization and data management workflows.

For organizations with more specialized needs, purpose-built tools extend these capabilities with industry-specific logic. Water utilities, for example, often need routing that accounts for hydraulic flow direction and pressure zones. Gas network operators need routing that respects segment pressures and valve states. Telecommunications providers need to trace logical connectivity through physical infrastructure layers simultaneously.

Our Spatial Workshop platform includes spatial analysis functions that support routing, topology, and spatial relationship analysis natively. This means you can perform network traces directly on your connected data without extracting it to a separate modeling environment, keeping your analysis current and your workflows efficient.

Integration capability is also worth evaluating when selecting a platform. Your routing tool needs to connect to the data sources where your network records actually live, whether that is an asset management system, a SCADA platform, or a GIS database. Tools that require you to export and re-import data for every routing session introduce delays and version-control problems that erode the value of the capability.

What are the most common mistakes when configuring utility network routing? #

The most common mistakes when configuring utility network routing are poor data preparation, ignoring asset states, misconfigured network rules, and treating routing as a one-time setup rather than an ongoing process. Each of these mistakes produces results that look plausible but are wrong in ways that are difficult to detect without field verification.

• Skipping data quality checks before building the network model. Routing will faithfully follow whatever topology you give it, including any errors. If your source data has connectivity gaps, duplicate assets, or incorrect coordinates, your routing model inherits all of those problems. Cleaning data after the model is built is far more difficult than cleaning it beforehand.
• Not accounting for asset operational states. A routing model that ignores whether valves are open or closed, or whether switches are energized, traces theoretical paths rather than real ones. Operational state data needs to feed into the routing engine dynamically, not just at the time of initial configuration.
• Applying incorrect network rules for flow direction. Directed networks require rules about the direction in which flow can travel through each segment. Applying those rules incorrectly—or omitting them entirely—causes routing to produce paths that violate the physical behavior of the network.
• Failing to update the network model when the physical network changes. New assets added in the field need to be reflected in the network model with correct connectivity. Organizations that allow a gap to grow between the physical network and the data model find that routing accuracy degrades steadily over time.
• Treating routing as a standalone function rather than integrating it with operational workflows. Routing is most useful when it is accessible to the people who need it at the moment they need it: field crews, operations teams, and network planners. Routing capability locked inside a specialized desktop tool that only GIS analysts can use delivers only a fraction of its potential value.

Avoiding these mistakes is largely a matter of discipline around data governance and a clear understanding of what your routing model is actually doing under the hood. When routing results feel unreliable, the problem is almost always in the data or the configuration, not the routing algorithm itself.

At Spatial Eye, we help utilities and infrastructure organizations build routing capabilities that connect directly to their operational data, stay current as networks evolve, and deliver results that field teams and planners can trust. If you want to explore what solid spatial analysis and network routing can do for your organization, we would be happy to show you.