Utility Network Analysis and Tracing
This domain tests trace types, trace configuration, barriers, filters, functions, subnetwork tracing, and isolation analysis. The exam expects you to choose the correct trace for an operational question and to explain why a trace returns too much, too little, or stale data.
Trace types and configuration
- Trace types include Connected, Upstream, Downstream, Loops, Shortest Path, Subnetwork, and Isolation.
- A trace requires enabled and validated network topology. Starting points define where traversal begins; barriers stop traversal. Barriers can be selected features or defined by attribute conditions.
- Filters restrict traversability by asset type, category, or network attribute. Functions can add results to the selection, aggregate results, propagate values, or apply filters.
- Upstream and downstream are relative to flow direction and sources, not to screen direction. Edge flow direction must be set correctly for directional traces.
- A Subnetwork trace requires a subnetwork controller and typically a subnetwork name. It returns features in that subnetwork.
- An Isolation trace uses isolation barriers, such as valves or switches, to find the devices that must be operated to isolate a starting point.
Worked example
A water main leak must be isolated. Place a starting point on the leaking main and run an Isolation trace with valves configured as isolation barriers. The trace returns the valves that bound the affected section. The reasoning is that the trace traverses until it encounters closable isolation barriers, so valve asset types and their barrier role must be modeled correctly. If a valve is missing from the trace, check its asset type, category, and whether it is configured as an isolation barrier.
Traps that cost marks
- Running a directional trace when flow direction is unset or reversed, then misreading upstream and downstream.
- Using filters that exclude the very asset types needed for the answer.
- Expecting a Subnetwork trace to work without a subnetwork controller.
- Treating a trace selection as a permanent edit; it is an analysis result unless you export it.
- Tracing on dirty or unvalidated topology and trusting stale connectivity.