GridForge research

Research areas.

The smart-meter fleet sees a lot — voltages and powers at every customer, every few minutes — but the network behind it is largely undocumented. The areas below are how we work back from what the meters tell us to a usable model of the network. None of them is ever finished; cohorts revisit and improve them as new ideas, new data, and new failure modes show up.

Area 01

Topology estimation

Active

The connectivity of an LV network — which customers share conductors, where branches join, where the boundary lies — is rarely documented well. Utility GIS records are often incomplete, out-of-date, or simply absent for older sections.

We develop methods to infer the network tree from smart-meter data alone. The meters already record voltage and power at customer premises; the question is how to read the structure out of those signals without site visits or extra sensors.

Topology gets worked on the most because almost every other method here depends on it — load flow, loss accounting, fault location, and downstream phase or impedance estimation all assume a network you can trust.

Inputs
Voltage, real, and reactive power time-series at each customer meter. No additional sensors at the transformer or along the feeder.
Output
An adjacency / tree structure: which meter is downstream of which, and where branches diverge.
Why hard
Many topologies fit the data approximately; small mis-attributions propagate into every downstream method.

OpenVerifying topology estimates at scale without ground-truth GIS to compare against — and at the same time, building better methods that estimate better trees and work on larger networks.

Area 02

Phase grouping

Active

LV networks are three-phase, but each customer connects to just one. Which phase a customer is on affects load balance, voltage quality, and how their meter readings should be interpreted. Phase records in the field are frequently incomplete or wrong — particularly for older networks where connections have been changed and not redocumented.

We infer phase membership from the correlation structure of voltage time-series across the smart-meter fleet. Customers on the same phase exhibit a distinct correlation signature compared to customers on different phases, even without measurements at the substation. The "grouping" step clusters all customers simultaneously into three phase classes — no labels, no priors.

Inputs
Voltage time-series across the meter fleet for the same time window.
Output
A phase label (A, B, or C) per customer — assigned jointly, not one at a time.
Why hard
Real voltage signals are noisy and partially shared across phases via the transformer; clusters are not always clean.

OpenWe're implementing a variety of phase-grouping methods so they can be tested against each other — working out which approaches are most effective, and under what conditions.

Area 03

Impedance estimation

Planned

Distinct from topology, impedance estimation focuses on the electrical properties of the conductors themselves — specifically the resistance R and reactance X of each cable. These values determine how voltage drops across the network, how losses accumulate, and how power flows under varying load conditions.

As with topology, utility records of cable impedances are often unreliable or missing. We're developing methods to estimate impedance from smart-meter observations, either jointly with topology or as a follow-on step. Accurate impedances also act as a cross-check: they should be consistent with the topology that produced them.

Inputs
Voltage and power observations + a topology (typically from Area 01).
Output
Resistance and reactance for every edge in the network.
Why hard
Generating realistic synthetic data to evaluate against is difficult on its own. Working with real data is harder still: if we run impedance estimation on top of an estimated topology, we're building on something with potential errors; without a topology, we're estimating from even less.

OpenHow much of impedance is identifiable from meter data alone, vs. how much needs a prior over standard cable types — and whether joint topology + impedance estimation outperforms the two-step approach.

Area 04

Transformer monitoring

Planned

Distribution transformers sit between the medium-voltage grid and LV customers. Knowing how a transformer is loaded, what voltage it is presenting, and whether it's under thermal or operational stress is valuable for network management — but instrumenting transformers directly is expensive and impractical at scale.

Virtual sensing estimates transformer-level quantities from the smart-meter readings already collected at customers downstream. No hardware change at the transformer itself. The aim is to make transformer monitoring tractable for utilities where dedicated sensor deployment isn't economically viable.

Inputs
Smart-meter readings from customers downstream of a target transformer.
Output
Estimated transformer parameters — total loading, terminal voltage, thermal state, and other operational indicators.
Why hard
If we run this on top of an estimated topology, we're building on something with potential errors; aggregating customer-level estimates can amplify those, alongside missing meter coverage.

OpenDeveloping different methods to estimate different transformer parameters — total loading, voltage, thermal state — and characterising how each method holds up under typical LV measurement conditions.

Area 05

Situation analysis

Planned

Knowing the current state of a network is useful; knowing how it responds to change is essential for planning. Situation analysis is a tool for scenario exploration — taking the network model produced by the other methods and stress-testing it against hypothetical futures, so problems can be found and reasoned about before they arrive in the field.

Inputs
Network model (topology + impedance) + a scenario specification.
Output
Voltage and loading envelopes across the network under that scenario; flagged limit violations.
Why hard
This is effectively a last-stage analysis: it leans on topology, phase grouping, and impedance estimation all being in place and accurate. Errors anywhere upstream show up here.

Scenarios we want to support out-of-the-box:

Rooftop solar uptake
EV adoption + charging
Large-customer load shift
Reroute / re-feed customers

OpenHow operators want to interact with scenario results — single answer? envelope of outcomes? a sensitivity ranking of which assumptions move the needle most? The right output format is itself a research question.

See which methods each cohort owns.

Project pages map the work above onto the students currently doing it.

View Projects