Site icon Laurel Hill GIS

The Severity 5 Problem

Critical Business Rule Validations That Can’t Wait

Not every data error is created equal. A few of them will stop your Utility Network cold.

Run a full data assessment on a legacy utility geodatabase and you will get a number that looks alarming. Tens of thousands of errors. Sometimes hundreds of thousands. Some people will panic, and some will write the whole thing off as noise.

Neither reaction is right. Most of those errors are inconveniences such as a blank install date, a material code that fell out of the domain, or a manhole ten feet from where it should be. They matter, but they don’t break anything. A much smaller group of errors are violations of the business rules that a Utility Network depends on to function at all. When they exist, subnetworks don’t build, traces don’t run, and the systems downstream of your GIS start making decisions on bad information.

In our data assessment methodology, those errors sit at the top of the scale: Severity 5. Keep reading to find out what puts an error in that tier, why the four categories that live there are so damaging, and why they need to be fixed before anything else.

What makes an error Severity 5

Severity in a data assessment isn’t about how many times an error occurs or how ugly it looks on a map. It’s about consequence. We rank an error at the top of the scale when it meets any of these tests:

Four categories of error consistently meet these tests. Two are domain-specific, one for gas and one for electric. Two are universal.

Gas: pressure validation

A gas distribution network is organized around pressure. Every pipe belongs to a pressure system bounded by regulators, and every pressure system carries a maximum allowable operating pressure (MAOP) that governs what can be safely connected to it. In a Utility Network, the pressure system is a subnetwork and the regulator is its controller.

That structure only works if pressure attributes are consistent across every feature in the system. The errors that violate it look like this:

Why this is Severity 5: a pressure system that can’t build is a pressure system your GIS can’t reason about. Isolation planning, regulator station analysis, and MAOP reporting for regulators all depend on it. And the consequence of a wrong pressure boundary isn’t a bad report. It’s a crew isolating the wrong segment.

Electric: phase validation

The electric equivalent of pressure is phase. Every conductor, device, and transformer carries a phase designation, and the Utility Network enforces phase continuity: a single-phase B lateral cannot be fed from a conductor that only carries phase A, and a three-phase device can’t sit on a two-phase line.

Legacy Geometric Networks never enforced this. The phase field was just an attribute, and it drifted for years. When a Utility Network starts enforcing it, the drift becomes visible all at once. Typical Severity 5 phase errors:

Why this is Severity 5: phase errors don’t stay local. Because phase propagates through the subnetwork, one bad tie switch or one mis-phased riser can corrupt the phase designation of every feature downstream. Outage prediction, load balancing, and unbalanced-load studies all inherit that corruption.

Invalid geometry

Geometry errors are the least glamorous category on this list and the most likely to be a hard stop during migration. A Geometric Network tolerated a surprising amount of geometric garbage. A Utility Network does not.

Why this is Severity 5: Invalid geometry isn’t an error the network can work around. It’s a feature the network can’t load. Every one of these must be found and fixed and finding them by hand across a million features isn’t a realistic plan.

Logical connectivity

Geometry tells you where features are. Connectivity tells you whether they’re actually joined. The two frequently disagree, and the disagreement is invisible on a map.

Why this is Severity 5: connectivity is the network. A pressure system or a circuit is nothing more than a set of features that the topology says are connected to a controller. If that connectivity is wrong, the subnetwork is wrong, and every consumer of the subnetwork is wrong with it.

What this looks like in practice

Consider an illustrative mid-size combined gas and electric utility running an assessment: roughly 400,000 gas features and 900,000 electric features. The full assessment returns something on the order of 85,000 errors across all severity levels. That number is intimidating until it’s sorted by severity, at which point the picture changes:

That’s about 6,000 Severity 5 errors out of 85,000, or roughly 7 percent. Fixing those 6,000 is what stands between this utility and a Utility Network that builds subnetworks. The other 79,000 can be worked through methodically after go-live. The 6,000 cannot.

Two things stand out in that breakdown. First, Severity 5 errors cluster. They come from specific conversion projects, specific territories, specific field-collection efforts. That makes them tractable once identified. Second, a small number of root-cause errors (the 40 tie-switch mismatches) generate a large number of symptomatic ones. Fix the root, and the count collapses.

Why they can’t wait

They’re the errors that block everything else. You can’t validate a pressure system’s attributes until the pressure system builds. You can’t test phase-dependent business rules until phase propagates. Every lower-severity fix on a broken subnetwork is work you may have to redo.

They get more expensive the later you find them. A pressure mismatch found in a pre-migration assessment is a data edit. The same mismatch found after cutover is a Dirty Area in a production network, blocking edits in that area, with an operations team waiting on the fix.

They don’t stop appearing at go-live. Field crews will continue to snap service lines a fraction short. Contractors will continue to code phases from memory. A Severity 5 error introduced into a live Utility Network has the same consequences as one that was there from the start. This is why validation for these categories has to be continuous, not a one-time gate.

How GeoData Sentry approaches it

GeoData Sentry was built for exactly this problem: running the business-rule validations that a Utility Network depends on, automatically, across the entire geodatabase, and reporting results in a form a GIS team can act on.

The goal isn’t zero errors across the board. That’s not a realistic target for any utility geodatabase. The goal is zero errors in the categories that stop the network from working, verified continuously, so the rest of the cleanup can happen on a schedule that makes sense.

Start with the errors that matter

If your utility is fighting a persistent backlog of Dirty Areas, the first question to answer is simple: how many Severity 5 errors do you have, and where are they?

Laurel Hill GIS can run a data assessment against your geodatabase and give you that answer. Contact us to schedule an assessment or to see a demonstration of GeoData Sentry’s Utility Network validation tests.

Exit mobile version