Pole Risk Watch: Earthing and Leakage Risk for Distribution Networks

VERTICAL-DRIVEN ARCHITECTURES · ENERGY AND UTILITIES

Pole Risk Watch

A system design for heads of distribution engineering, earthing program offices, HSE investigators and the engineers who would build it. It shows how a coastal distribution utility can rank the poles most likely to cause harm before a monsoon storm, separate its own defects from private wiring, and give the regulator evidence it can verify.

THE CASE IN BRIEF

• Public electrocution risk on a distribution network peaks when rain meets a defect that was already there, such as a missing earth, a corroded down conductor or an open pole box.
• These defects are invisible in dry-season surveys and only become dangerous when the rain arrives.
• The data needed to see them is split across the geographic system, feeder telemetry, the enterprise system, rainfall feeds, audit photographs and paper case files.
• No system holds pole condition, rainfall and electrical consequence together at the moment the storm starts.
• Pole Risk Watch fuses these signals into one model the utility owns and gives field engineers a ranked list of the highest-risk poles before the rain.
• The system ranks, alerts and evidences, but never switches the network, and a named person decides every action.

WHY THIS MATTERS

Risk is seasonal and time-bound. The useful answer is which poles are most dangerous tonight, delivered before the rain, not a finding after an incident.

Responsibility must be attributable. Regulators ask whether an incident came from the utility's own network or from private premises wiring, and the answer depends on evidence that today sits in separate systems and paper files.

Surveys miss the condition that matters. Earthing checks are done in the dry, and audit photographs carry no rainfall context or electrical consequence.

And the evidence must belong to the utility. Case files, imagery and sensor series are read in regulatory proceedings, so they need to stay inside the operator's boundary on models it can hold.

This creates a structural exposure.

• Earthing surveys are clipboard exercises carried out in dry conditions.
• Feeder trips are recorded without the pole or span that caused them.
• Defects reach the work order system only after someone finds them, which in monsoon season means after the event.
• Investigation files sit as mixed-language paper scans that no system reads.
• Thousands of audit photographs are filed with no link to rainfall or electrical readings.
• The utility cannot readily separate its own leakage from neighboring illegal connections when the regulator asks.

Rank electrocution risk before the rain, not after an incident.

Every ranking carries its evidence, and every verdict, including undetermined, is signed by a named person.

WHAT YOU'LL LEARN

Inside the architecture, you'll find:

• Why the lethal condition on a distribution network appears only when rain meets a latent defect
• How seven systems each see one slice of the pole, and why none holds the join at the moment the rain starts
• The four constraints that bind a sovereign safety design
• Three scoping decisions and what each costs, including undetermined as a first-class attribution verdict
• What the design chose against for detection, evidence drafting, edge compute, the event backbone and sensing
• The layered stack from eight sources through four adapter families to three surfaces
• The sixteen-object model, with the distribution pole shown in its recorded form
• How status vocabularies place the human verdict inside the model rather than in side notes
• How adapters guarantee provenance, unit checks, ordering and buffering before anything reaches the model
• Why sensing belongs on the pole, detection beside the cameras and reasoning in-country, with the memory arithmetic
• The three open-weight models and why each license lets the utility hold its own fine-tunes
• How mixed Urdu and English case files become structured incident records
• How the rollout shadows the rankings through a full monsoon against a control zone
• The six named failure modes, the lessons the design draws from precedent and the questions still open
• How Praxis contextualized the requirement, read it through eight lenses and reasoned every choice in the design

DOWNLOAD THE ARCHITECTURE

Read the complete architecture, from the latent defects every system sees only part of, through the object model, ingestion, inference placement and model register, to a rollout judged on field-verified outcomes and the reasoning Praxis recorded for every choice.

A utility that measures its own earth through the storm can act before harm occurs and show the regulator exactly what happened when it does. That evidence is strongest when the utility produces and controls it.