What's actually behind that transformer? A look at grid traceability

A transformer is running hot. Before an operator can act, she needs to know what sits behind it. Why tracing the grid beats modeling it.

Nicholas Brown, Co-founder and CPO
2 minute read
What's actually behind that transformer? A look at grid traceability

A transformer on Feeder 7 has been running hot for the last ten minutes. The operator has been alerted. But before she can decide to shed load or dispatch a crew, she needs to understand:

What's actually sitting behind this transformer right now?

Has a battery been discharging for the last twenty minutes? Was an EV plugged in an hour ago? Has solar been exporting straight through the afternoon peak?

And is any of it pushing the transformer past its limit?

Texture site detail page showing the grid hierarchy for 263 Bridle Path, tracing from the site through its meter, two transformers, overhead line segments and a bay up to Marshwel Substation.

This is a hard question. Meter data lives in one system, device telemetry sits in another, and asset records with transformer ratings are filed in a third. All three systems are siloed from each other, which makes finding answers to basic grid questions time-consuming and difficult.

Texture takes utility data and connects it into a single operational view. Every device on the platform knows its exact place in the grid — which meter it sits behind, which transformer feeds it, which feeder that transformer connects to, which substation that feeder runs out of. With one click, the full grid hierarchy is visible.

A "Downstream devices" panel in Texture listing the Aclara meters connected below a selected piece of grid equipment, each tagged as a consumer.

Operational questions that would normally take three system exports and a prayer become single-prompt lookups.

  • Which devices sit downstream of this recloser?
  • What was the load on this feeder five minutes ago, and what is it now?
  • How many EVs have started charging behind this overloaded transformer in the last hour?

A transformer loading chart in Texture plotting measured load in kVA over the past week against the transformer's rated limits of positive and negative 15 kVA.

The roll-up scales in both directions. A transformer view shows every device behind it and its real-time contribution to load. Zoom out to the feeder and that same view aggregates everything below it. Zoom out again to the substation and it shows the whole downstream picture. Every layer answers its own question, without an export, a spreadsheet, or a wait on some batch job to reconcile what's connected to what.

Modeling the pieces is table stakes: a list of assets, a list of meters, a list of devices.

Modeling the connections, making it possible to trace anything up or down the chain without leaving the platform? That's the difference between a data model that describes the grid and a data model you can operate on.

That's Texture.

Nicholas Brown
Nicholas BrownCo-founder and CPO

Nicholas Brown is the co-founder and CPO of Texture, an energy data platform in New York. With over 15 years of product leadership experience, he specializes in bringing innovative solutions to market in the energy and climate tech space

Built for the people keeping the grid running.

Book a demo and see Texture in action, on your system with your data.

What's actually behind that transformer? A look at grid traceability | Texture