Skip to main content

Network Connections and Zone Divisions

  • Updated

Analyses Performed by PipeFusion

PipeFusion performs several analyses on datasets from the pipe database and work order systems with associated observations and operational data (e.g. maintenance reports, leakage reports, pipe inspection reports, etc.) and any other relevant data sources such as the subscriber database, and various types of sensor data and measurements (e.g. SCADA data, weather data, watercourse data).

Here are some examples of analyses and data generation that PipeFusion can perform. These are things generated based on input data and a set of rules, but which either actively differ from the source, or are generated beyond the basis available in the source:

Network Connections and Zone Divisions

Generating Missing Connections

PipeFusion identifies missing connections by building a graph model of the pipe network based on nodes and pipe elements, then testing connectivity, direction, and logical connections in the network.

The algorithm detects breaks in the structure — such as pipes that are close to each other but not connected, incorrect endpoints, or missing nodes. Based on spatial proximity and network logic, PipeFusion automatically suggests corrections that connect elements correctly. These corrections can be reviewed and validated before being used further in analyses.

Generating Missing Pipes

General

PipeFusion can generate new pipes by:

  • Adding short pipes where they are missing
  • Splitting existing pipes into multiple components at nodes, to maintain a hydraulically correct model

PipeFusion generates missing pipes by analysing the network structure and identifying logical breaks between nodes that should be connected but lack a registered pipe.

Service connections

The solution can also generate service connections from a municipal pipe to a loaded point indicating a subscriber (location of a water meter, registered subscriber, building, or other relevant geo-point). This is done by PipeFusion calculating an assumed route (which is logical for a machine — topography, physical obstacles, and practical constraints are not taken into account). In this case, the total pipe length in InfoTiles will be higher.

Missing pipes / connections

The example below shows PipeFusion flagging a possible missing connection or pipe between two points. The two points are marked with red circles. The distance between them is too large for the algorithm to automatically propose a correction.

To connect the two points, the correct solution must be entered in the source system (the Asset Database).

Map showing points where the machine learning algorithm flags a missing connection for specialist review

Figure 4: Map showing points where the machine learning algorithm leaves quality control and correction to a specialist.

Pipes Not Connected to the Network (Unconnected)

PipeFusion will «travel through» all valid paths through the network using a method called «traversal». To do this, there must be a valid node and valid pointer from a pipe to a node. Pipes that are connected to each other in groups of at least 20 pipes are assigned a value under «Group». However, some pipes are too far from anything to connect to, so they remain disconnected — meaning it is not possible from a data perspective to carry water to or collect water from these pipes. This map layer is designed to simplify searching for such pipes, as methods in Gemini such as parallel displacement or visual analysis in maps can make them difficult to detect.

Map layer showing pipes that are not connected to the main network

The unconnected pipes map layer highlights pipe segments that cannot be reached through network traversal — useful for identifying data quality issues.

Water Zone Divisions (DMAs)

Input data: Pipe database

In Norwegian, we often distinguish between two types of zone division for the drinking water network: measurement zones and pressure zones. In English, zones in the drinking water network are often called DMAs, an abbreviation also used in InfoTiles. The meaning is typically district metering areas, i.e. measurement zones, but can also mean district managing areas, which is a much broader concept. PipeFusion calculates 2 types of zones for water:

  • Pressure zones (Pressure). The zone type is bounded by:
    • Water treatment plants
    • Reservoirs
    • Pressure boosting stations
    • Closed valves
    • Pressure reducing valves
    • Check valves are classified as pressure reducing valves as they perform the same logic.
  • Consumption zones (DMA):
    • Uses the same main objects as above, but replaces pressure reducing valves with flow meters.
    • Note: The method for creating measurement zones always starts from «measurement point», unit type «MM» in table VA_LEQUIP in Gemini.
    • If an area is expected to be a measurement zone but has no value, check which objects define the boundary. Often the order of pipe equipment in Gemini can cause some zones to be omitted.

Wastewater Zone Divisions

Generating Wastewater Zones

Input data:

  • Pipes of types combined sewer (CS), wastewater (WW), and stormwater (SW) with subcategories
  • Stations (pumping stations for CS, WW, SW), treatment plants (TP), overflow weirs (OW), and outfalls (OF)

Different municipalities have different practices for defining zone divisions in wastewater. Some zone maps show the pipe network's catchment areas with separate and combined systems as drawing rules; others show pumping zones or overflow zones.

PipeFusion generates zones based on the network information (points and pipes) and does not assume or require that any zones exist beforehand. The algorithm only creates zones for point types that are specified — typically treatment plants, pumping stations, overflow weirs, and outfalls — but can also use flow meters to establish separate measurement zones for wastewater.

The algorithm starts at the treatment plant and travels backwards through the network until it stops at a node that is the starting point for a new zone (such as a pumping station). All pipes and nodes then receive the name pf_zone from the point where the algorithm started, e.g. «PS100».

After all pipes and all points have been analysed, an extra step is performed in which the network is traversed to map «ancestors» and «descendants» — i.e. objects that come before or after when travelling through the network in the flow direction.

For wastewater, the network is divided into zones by distributing it into contiguous wastewater zones sorted by the type of endpoint for each zone:

  • Pumping station / Pump
  • Overflow weir
  • Treatment plant
  • Outfall
  • «Ambiguous»: Areas that can drain in multiple directions due to cross-connections

You can also filter on different types of network in the map by toggling them on and off in the map menu:

  • Wastewater / combined sewer
  • Stormwater
  • Combined
  • Other

Outfall

Outfall zones are generated from outfalls, where water leaves the system to the receiving water body, and are linked to unit type UTS/UTL in Gemini VA. Ideally this should cover closed stormwater networks and allows users to see whether separation is correct.

Zone Naming

Zone naming is based on station name (pf_station). When Gemini VA is the source for the pipe database, this field is linked to the fields REF/EXREF/STATION where the structured name (such as PS100) is stored. If no value exists in the name field in the source system, the name in PipeFusion falls back to the ID (PSID for points, but often a negative number such as –132 for pipe equipment (the LEQUIP table in Gemini), as those IDs collide with PSID in Gemini).

If separate pipes share a manhole, a connection is created in the network. These cross-connection points appear as red triangles («Bifurcation»). Pipes upstream of such manholes have multiple possible routes and are of the type «ambiguous».

Visual Zone Boundaries as Polygons vs. Zone as a Pipe Property

If you filter on geometry in the map, you will get all pipes visible within the zone — but not all of them are necessarily connected to the network in that zone (e.g. independent stormwater networks without connection to the wider network). If you filter on zone name under the pipe's properties, you will only see the pipes that PipeFusion has linked to that zone.

Related Articles

Comments

0 comments

Please sign in to leave a comment.