SystemMetering & AMI Operations

Meter-to-Transformer Connectivity Validation

Meter-to-transformer connectivity validation that corrects the GIS from AMI voltage, and sends a technician only where voltage cannot decide

Meters relinked to the right transformer from voltage alone, with 87% fewer field checks.

See one case, screen by screen ↓
target99%of meters on the transformer they are really on, so outage predictions and planned-work notices reach the right homes
estimated$3.7Mof field visits not needed: 14,990 links settled from data instead of a truck, at $250 a visit, on Lumina's 412,600 meters
estimated52upgradesplanned transformer upgrades the corrected map shows are not needed, and 38 real overloads found that looked fine
demo2homeson Wren Close lost power in the 3 Oct planned work without a notice; the corrected list warns all 10
The problem

Why the GIS puts meters on the wrong transformer, and only a truck proves it

The GIS says which transformer each meter is on, and often it is wrong. The link was copied from the old meter's record at an exchange, taken from a design drawing for a new connection, or left behind after a rebuild that was never posted. Long rear-lane services run to the pole you would not expect. The usual check is a distance and orphan screen in the GIS, then a crew to trace the service, so the error stays until someone pays for a truck roll.

Every system downstream inherits it. The outage model rolls customer calls up under the wrong device and sends crews to the wrong place. Planned-work notices are built from GIS links, so homes that will lose power are not warned. Transformer loading studies count the wrong houses, missing real overloads and planning upgrades nobody needs. Energy-balance checks flag honest transformers as losses, and solar and EV hosting is assessed on the wrong secondary.

typical~5%of a large US utility's meters, about 193,000, were found in a first estimate to point to a wrong or non-existent transformer
typical$250–500for each utility truck roll, a conservative published figure — and a truck is how a link is checked in the field today
Where a feeder's connectivity review days goestimated
By hand14 days
With the solution1.5 days
  • Screening the GIS for distant and orphan meters1 → 0 d
  • Pulling meter voltage, outage records and install GPS3 → 0.1 d
  • Field visits to trace services and read transformer tags6 → 0.5 d
  • Deciding each link and writing up why2 → 0.5 d
  • Building, checking and approving the GIS edit1.5 → 0.3 d
  • Publishing to the outage model0.5 → 0.1 d

Estimated split for one feeder of about 1,200 meters with about 30 suspected links, in working days, by hand and with the solution.

How it works

How meter voltage corrects the map

Six specialist agents read the voltage, outages and locations and propose each correction; the GIS data steward moves the link.

What comes in
Data in4 sources · meter voltage, GIS, outages, SCADA
Agents at work
Voltage data checkerfit to compare
Then
Voltage correlation analyst
Phase identifier
Then
Outage event matcher
Location checker
Then
Correction packagerranked + GIS edit
A person decides
GIS data stewardmoves each link, approves the update
What comes out
Ranked corrections
Field checks only where needed
GIS update, published
One case, step by step

One feeder, from the overnight check to a published GIS update

Brookmere 12 is an 11 kV feeder out of Brookmere substation at Lumina Utilities: 1,184 meters and 96 transformers in 8 sections. At 02:10 on Tue 13 Oct 2026 the nightly check reads 28 days of 15-minute voltage. Here is what happens next, screen by screen, in the working solution.

  1. 0102:10

    A month of voltage, every meter, every night

    The six agents · nightly check

    The voltage data checker reads 3,182,592 reads for 1,184 meters — 99.6 % complete, 2 meters re-aligned for clock drift. The phase identifier matches the 96 transformer groups to the SCADA phase voltages at Brookmere and finds 4 recorded on the wrong phase. The correlation analyst compares every meter with every transformer within 380 m: 31 follow a different transformer from the one the GIS records. Outage events support 10 of the 31 and contradict none.

    Correction packager: “Ranked 31 proposals and 4 phase changes · 22 high · 6 medium · 3 need a field check · Nadia Okafor decides”

  2. 02Morning

    The feeder map shows each link that is in doubt

    Nadia Okafor · GIS data steward

    Nadia owns the connectivity model for 214 feeders, and Brookmere 12 is this week's review feeder. Section 3, Wren Close and Alder Row, has 148 meters, 12 transformers, 6 suspected links and 1 transformer on the wrong phase. 27 Wren Close, meter 20418836 with a 7.4 kW EV charger, is drawn with a dashed red link to T-1207 on Alder Row, behind the rear gardens.

    “Voltage follows T-1209 at 0.91 and its recorded T-1207 at 0.34”

  3. 03The evidence

    Its voltage moves with the transformer across the lane

    Voltage correlation analyst and Location checker

    Each dot is one 15-minute read, the meter's swing against the group's. Against T-1207 the dots are a round cloud at 0.34; against T-1209, a 25 kVA unit on Wren Close, they line up on a tight diagonal at 0.91. No other transformer within 380 m fits better than 0.36. Install GPS from the meter exchange on 14 Mar 2025 puts the meter 22 m from T-1209 and 214 m from T-1207: the old meter's link was copied.

    Location checker: location alone never moves a link — here it agrees with the voltage.

  4. 04Outages agree

    It stayed on when the old transformer's fuse blew

    Outage event matcher

    On 28 Sep at 14:12 the fuse on T-1207 operated (OE-58113): 8 of its 9 recorded meters sent a last-gasp, and 27 Wren Close kept reporting. On 3 Oct the cut-out on T-1209 was replaced (WO-774120): the notice went to 8 homes, and this meter lost power with the T-1209 group, along with 26 Wren Close, recorded on T-1212. A recloser trip on 21 Sep blinked every meter in sections 3 to 8 and is counted as neutral.

    “Every meter in section 3 blinked together. It says nothing about which transformer — the agent counts it as neutral.”

  5. 05One click

    Nadia moves the link, and the map redraws it

    Nadia Okafor · GIS data steward

    Nadia presses Move link to T-1209. The service link swings across the map to T-1209, the recorded T-1207 is struck through, and the change joins the GIS update with its evidence. Undo is one click away.

    “27 Wren Close linked to T-1209 · added to the GIS update”

  6. 06The rest of the feeder

    High-confidence links in bulk, medium ones one by one

    Nadia Okafor · GIS data steward

    Corrections ranks all 31 proposals on Brookmere 12 by how strongly the evidence agrees: address, meter, section, recorded and proposed transformer, the voltage match, what else supports it, and a confidence. Nadia accepts the high-confidence links in bulk. The 6 medium links, such as 26 Wren Close at 0.12 → 0.78, are reviewed one by one, and 3 go to the field — 25 Mill Lane fits T-1204 at 0.77 and T-1202 at 0.69.

    “Confidence joins voltage, outage and location evidence”

  7. 07Wed 14 Oct · 09:00

    A technician only where voltage cannot decide

    Owen Pryce · Metering field technician

    Owen's week has 18 stops across the network, three of them on Brookmere 12. At 25 Mill Lane the secondaries of T-1204 and T-1202 are tied through link box LB-77, so voltage cannot separate them. The job sheet says what to check: open LB-77, trace the service to its pole, read the tag. He finds LB-77 open and the service running to pole MP-4471 under T-1202, and records it with two photographs.

    “25 Mill Lane: fed from T-1202 · added to the GIS update”

  8. 08Seven checks

    The GIS edit, checked before anyone approves it

    Correction packager

    Edit version CONN-BRK12-1013 gathers 23 meter links, one of them from Owen's field check, each with its evidence and who decided it; 8 are still open on Brookmere 12. Seven checks run: one transformer per meter, every target in service, same feeder, phase against the primary tap, loading after the move, outage-model references and no open edits. The loading check flags T-1209 and sends it to planning.

    “T-1209 at 25 kVA goes to 112% of its rating — sent to Tom Hale in planning”

  9. 09Approved · 22:00

    One person approves, a second publishes

    Nadia Okafor and Grace Lindqvist

    Nadia approves the 23 changes with a note for the record: voltage correlation, 28 days to 12 Oct; outage evidence on 2; field check on 25 Mill Lane. They post to the GIS edit version. Grace Lindqvist, the outage model administrator, publishes it at the 22:00 outage-model build, so a second person signs every publish.

    “Published. Grace Lindqvist published version CONN-BRK12-1013 to the outage model at 22:00. 23 changes are live in the GIS.”

  10. 10Planning sees it

    The real load on T-1209, and an upgrade not needed

    Tom Hale · Distribution planner

    With the meters really on it, T-1209 runs at 112 % of its 25 kVA rating, not the 85 % the record showed, driven by the EV charger at 27 Wren Close. T-1120 goes the other way, from 103 % to 94 %, so its upgrade is not needed. Replaying the 3 Oct notice shows 8 homes warned and 10 that lost power; with the corrected map the list is the 10.

    “With the corrected map: the notice list is the 10 homes that lost power — nobody missed, nobody warned for nothing”

Who it’s for

Built for everyone who relies on the connectivity model.

The same feeder, seen by the five people who keep the network model right — what their week looked like, and what it looks like now.

NO
Nadia OkaforGIS data steward, Network Records · approves connectivity changes
GIS data steward
Before
Owns the connectivity model for 214 feeders. Every doubtful link meant a distance screen, a pile of records and a truck. “I can't send a truck to every one.”
Now
Opens the feeder map with each suspect drawn, its voltage, outages and location a click away. “I can fix 31 links in an afternoon if I can see why each one is wrong.”
GL
Grace LindqvistOutage model administrator · publishes the outage model
Outage model administrator
Before
Builds and publishes the outage model every night at 22:00 from the GIS links. “If the GIS says nine homes, the outage model predicts nine homes. Then the calls come from ten.”
Now
Publishes an approved edit version that has passed seven checks, with the evidence for every change, as the second person on every publish.
TH
Tom HaleDistribution planner · transformer loading and solar connections
Distribution planner
Before
Sizes transformers for solar, EVs and heat pumps on measured peaks. “If the wrong houses are under it, the peak is fiction.”
Now
Receives every transformer a correction pushes over its rating, and sees each unit's peak loading as recorded against corrected.
OP
Owen PryceMetering field technician · Brookmere and Ashcombe
Metering field technician
Before
Traces services wherever the record is in doubt. “Send me where it's really ambiguous, like a tied link box, not to every street.”
Now
Gets a week of stops only where voltage cannot decide, each job sheet saying why and what to check, and records the result on his tablet.
RA
Ruth AbaraNetwork Records manager · rules and reports
Network Records manager
Before
Sets thresholds and reports to the asset director. “Show me the share of the network we trust, feeder by feeder.”
Now
Sees all 214 feeders on 38 substations coloured by the share of meters on a different transformer, and sets the thresholds the agents work to.
Built on the engine

6 agents. Each with one job, and hard limits.

Six specialist agents read the voltage, outages and locations and propose each correction; the GIS data steward moves the link.

Voltage data checker

Reads 28 days of 15-minute voltage for every meter from the head-end and checks it is fit to compare: drops meters with more than 20 % of reads missing, flat-lined or stuck values, and re-aligns meters whose clocks drift.

  • Never fills missing reads with estimates
  • Reports what was excluded and why
Voltage correlation analyst

Correlates each meter's read-to-read voltage changes with the median of every transformer group within 380 m, leaving the meter out of its own group, and proposes a move only when another group fits by the margin the steward sets.

  • Never proposes a move across feeders without a switching record
  • Never edits the GIS
  • Asks for a field check when two groups fit almost equally
Phase identifier

Correlates each transformer group's voltage with the SCADA phase voltages A, B and C at the feeder head, and flags a transformer whose recorded phase is not its best match by a clear margin.

  • Never changes a phase on a three-phase transformer
Outage event matcher

Lists the last-gasp and power-restore messages for every device operation and planned outage in the window. A meter that goes dark with a group supports a link to it; one that keeps reporting while its recorded transformer is off contradicts the record.

  • Counts feeder-wide events, such as a recloser trip, as neutral
Location checker

Compares install GPS and the address with transformer locations, the side of the street and rear-lane services.

  • Location alone never moves a link
Correction packager

Scores each proposal from voltage, outage and location evidence, books field checks where voltage cannot decide, builds the GIS edit version with the evidence for each change and runs the seven checks.

  • Never posts to the GIS without approval
  • Sends any transformer pushed over its rating to planning
GIS data steward

Decides each change; the outage model administrator publishes. The agents propose; a named person decides.

Ask in plain words

Ask about any meter, transformer or feeder

Ask in plain words about any meter, transformer or feeder — or say what to accept. Every answer points to its records.

Why does 27 Wren Close belong on T-1209?

Three things agree. Its voltage follows the T-1209 group at 0.91 and its recorded T-1207 group at only 0.34. On 28 Sep the fuse on T-1207 operated and 8 of its 9 meters went dark, but this one kept reporting; on 3 Oct it lost power with T-1209 during planned work. Its install GPS is 22 m from T-1209 and 214 m from T-1207. The GIS link was copied from the old meter's record.

Which links on Brookmere 12 still need a field check?

Three, where voltage cannot separate two transformers: 25 Mill Lane, 25 Samphire Lane and 84 Harrow Road. At 25 Mill Lane the two secondaries are tied through link box LB-77, so Owen Pryce will open it and trace the service. The other 28 links are decided from data.

What changes for planning if we accept these?

On Brookmere 12, T-1209 (25 kVA) goes from 85 % to 112 % of its rating: it really carries 10 meters, not 8, and one has a 7.4 kW EV charger. T-1120 goes the other way, from 103 % to 94 %, so its upgrade is not needed. Across the network the corrected map finds 38 transformers over their rating and drops 52 planned upgrades. T-1211 also moves from phase B to C.

Accept the 22 high-confidence links on Brookmere 12

Done — the links moved to the transformer their voltage follows, each with voltage above 0.85. They are in the GIS update with the evidence for each. The 6 medium ones need your review one by one, and 3 wait for Owen Pryce. Nothing reaches the GIS until you approve and Grace Lindqvist publishes.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

The feeder mapThe feeder strip with open suspects in each section, the section map with every transformer, house and service link, and the selected meter's voltage against its recorded and proposed transformer.
The nightly checkEach agent's step in the overnight run on Brookmere 12, with its numbers: reads, phase matches, suspected links, outage support and the ranked proposals.
Meter evidenceVoltage swings against both groups, the two scatter plots, every transformer within 380 m ranked by voltage match, the install location and the agents' run.
Outages and planned workThe fuse operation, planned job and recloser trip behind this meter's link, each marked as supporting it or neutral, beside the activity trail.
The link moved27 Wren Close linked to T-1209 on the map, the recorded transformer struck through and the change added to the GIS update.
FeedersAll 214 feeders on 38 substations, coloured by the share of meters on a different transformer, with the network totals and one feeder's detail.
CorrectionsEvery proposed change ranked by how strongly the evidence agrees, filtered by confidence, with one button to accept the high-confidence links in bulk.
Field checksThe technician's week of stops only where voltage cannot decide, the job sheet with what to check, and the recorded result.
The GIS updateEdit version CONN-BRK12-1013: the change set with its evidence and who decided each change, and the seven checks before approval.
Approve the updateThe steward approves the changes with a note for the record; the outage model administrator publishes them.
Published to the outage modelThe update published at the 22:00 outage-model build by a second person, with earlier updates listed below.
Planning impactPeak loading of each affected transformer, recorded against corrected, the network effect, and the 3 Oct planned-work notice replayed.
Your rulesConfidence thresholds with a live preview on Brookmere 12, and the rules for bulk accept, second-person publish, overloads and holds.
Governance

Proposed by agents, decided by the steward, published by a second person.

Every proposal shows its evidenceEach change carries the voltage correlation with its window and read count, the outage records behind it (OE-58113, WO-774120), the meter exchange record with its GPS, and the SCADA phase voltages. Every answer to a question points to the same records.
The GIS data steward decides each changeAgents propose; the steward moves, keeps or sends each link for a field check. Bulk accept is allowed only for high confidence, and medium links are always reviewed one by one.
Two people on every publishNothing reaches the GIS without the steward's approval, and nothing reaches the outage model until a second person, the outage model administrator, publishes it.
Seven checks before approvalOne transformer per meter, every target in service, no move across a feeder without a switching record, phase against the primary tap, loading after the move, outage-model references and no open edits on the same features.
Limits the agents cannot crossThe agents never edit the GIS, never move a link on location alone, never fill missing reads with estimates and never change the phase of a three-phase transformer. Any transformer a correction pushes over its rating goes to planning.
Every decision on the activity trailEach acceptance, field result, approval and publish is recorded with the person and the time, and each agent run step by step. Keep as recorded asks for a reason, kept with the decision, and holds the link for 90 days unless the evidence changes.
Configuration

Your network records rules, not ours

How sure the agents must be, who decides, and where the data comes from are settings, chosen by Network Records. The preview shows what each would do on Brookmere 12 before it applies from tonight's check.

SettingDefaultChoose from
High confidence — voltage match with the proposed transformer at least0.85Stepped from 0.75 to 0.95
Medium confidence — reviewed one by one0.70Stepped from 0.60 to 0.84
Margin over the recorded transformer0.30Stepped from 0.10 to 0.60 — how much better the proposed transformer must fit
Send for a field check when two transformers fit within0.15Stepped from 0.05 to 0.30
Search radius and window380 m · 28 daysTransformers within 380 m, the last 28 days of 15-minute reads
Accept high-confidence links in bulkOnOn · Off — medium links are always reviewed one by one
Second person publishes to the outage modelOnOn · Off — the outage model administrator, after the steward approves
Do not propose again for 90 days after Keep as recordedOnOn · Off — unless the evidence changes
Connections

Works with the systems your connectivity model already runs on

Meter head-end15-minute voltage, last-gasp and power-restore messages
GISservice points, transformers and phases, read and edit versions
Outage managementdevice operations, outage events and planned work
SCADA historianphase voltages at the feeder head of every substation
Field install recordsGPS at meter exchange and new connection
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
99%
of meters on the transformer they are really on, so outage predictions and notices reach the right homes
estimated
87%
fewer field checks: an estimated $3.7M of visits not needed at $250 each
Visit every doubt17,240 visits
Only where voltage can't decide2,250 visits
estimated
52
planned transformer upgrades the corrected map shows are not needed, and 38 real overloads found

“demo” = seen in the working solution, on its sample utility data · “target” = the design goal, measured in the live solution · “estimated” = our arithmetic, inputs shown: $3.7M = 14,990 links settled from data × $250 a visit, on the demo network of 412,600 meters; 87 % fewer field checks = 2,250 of 17,240 suspected links still needing a visit; 52 and 38 = the demo network after one nightly check, loading recomputed with corrected links; the feeder's day split is our estimate · “typical” = published figures: T&D World (2016) — a first estimate of about 193,000 meters, nearly 5 %, at a large US utility pointing to a wrong or non-existent transformer; S&C Electric via Ventavid (truck roll $250–$500). Method: T. A. Short, IEEE Transactions on Smart Grid 4 (2013); EPRI, Meter Connectivity (Phase ID). Lumina Utilities and the people, streets, substations, feeders, meters and records named on this page are fictional — characters and sample data in the working solution.

Questions

What GIS and network records teams ask us.

What is meter-to-transformer connectivity validation?

It checks that the GIS links each meter to the transformer it is really on, and corrects the links that are wrong. Meter-to-Transformer Connectivity Validation does it from AMI voltage: six agents compare each meter's 15-minute voltage with every nearby transformer group each night, confirm it with outage events and install GPS, and propose the correction. The GIS data steward decides.

How does meter-to-transformer mapping from AMI voltage work?

Meters on the same transformer see the same voltage swing whenever that transformer's load changes. The voltage correlation analyst correlates each meter's read-to-read changes with the median of every transformer group within 380 m, leaving the meter out of its own group, and proposes a move when another group fits by the margin you set. In the sample case, 27 Wren Close follows T-1209 at 0.91 and its recorded T-1207 at 0.34.

Can it find transformers recorded on the wrong phase?

Yes. The phase identifier correlates each transformer group's voltage with the SCADA phase voltages A, B and C at the feeder head. On Brookmere 12 it found 4 transformers recorded on the wrong phase, such as T-1211 on Fenn Street, recorded on phase B but following phase C. It never changes the phase of a three-phase transformer.

How many field checks does it save?

A technician goes only where voltage cannot decide, such as two secondaries tied through a link box. On Lumina's 412,600 meters, 14,990 of 17,240 suspected links are settled from data, so 87 % fewer field checks than visiting every suspect — an estimated $3.7M of visits at $250 each.

Does it replace our GIS, outage management system or head-end?

No. It reads the meter head-end, the GIS, outage management, the SCADA historian and field install records, and writes corrections to a GIS edit version. Your GIS stays the system of record, and the outage model administrator publishes the approved update to the outage model.

Do people stay in control of GIS edits?

Yes. The agents propose and never edit the GIS. The GIS data steward accepts, keeps or sends each change for a field check, bulk accept is allowed only for high confidence, seven checks run before approval, and a second person publishes every update to the outage model.

How does it help planning and planned-work notices?

Once each meter is on the right transformer, loading is counted on the meters really on it. In the sample, T-1209 runs at 112 % of its rating, not 85 %, and T-1120 drops from 103 % to 94 %, so its upgrade is not needed. Planned-work notices built from corrected links reach the 10 homes that lose power, not the 8 the GIS recorded.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your connectivity rules, GIS data standard, thresholds and a month of meter voltage — and it goes live once every quality gate has passed. We will walk you through it on your own feeders first.

See it on
your feeders.

We'll run Meter-to-Transformer Connectivity Validation on a month of your own meter voltage and GIS links.