Substation Scout
2Scoping

Substation Expansion Tracker

Feed of which substations are scheduled to change.

Why this exists

The substation dataset behind the Site Scanner is a snapshot. It tells you a substation exists, roughly where, and sometimes its maximum voltage. So far it cannot tell you that the utility has already filed to rebuild it, or that a planned upgrade two buses away changes what the local system can carry.

That information is public. It sits in PJM's Regional Transmission Expansion Plan and in the TEAC materials presented at stakeholder meetings... but these are hundreds of pages of slides, tables and prose published on a rolling basis. Nobody outside the process really reads them.

The intent here is to extract the substation-level items from those filings and attach them to the substations the report already names, so a screen can say "this substation appears in a planned upgrade, filed on this date, in this document" instead of implying the snapshot is the whole picture.

What the source actually is

PJM publishes the RTEP as board-approved baseline and supplemental projects, plus TEAC presentation decks. Items carry an upgrade ID, a described scope, a cost estimate and a target in-service window. The scope text is where the substation name lives, and it is prose. If PJM can be proven out, sister data pipelines can built-out for other grid operators.

Why it is hard

Substation names in planning documents rarely match the names in the HIFLD point dataset, and neither matches the point-of-interconnection strings in the queue. Matching them is the actual work, and a wrong match is worse than no match — it would attach a real upgrade to the wrong location.

What it will and will not claim

It will report that a named upgrade referencing a substation was filed, with the document and date. It will not assert that the upgrade makes capacity obtainable, or that a site near that substation can therefore be served — neither follows from a planning filing and no one can speak for a utility.

Current state

Parsing is in progress against PJM only. Nothing is published yet. When it is, matched items will appear on the substation pages this site already generates, plus a news feed of named-substation notifications.

Until this ships, the substation pages under PJM and ERCOT show queue activity at each substation, which is a different signal from planned transmission work.

The other pipelines

Same rule everywhere: a figure ships only when it traces to a named public source. Roadmap →

1 In progress

Queue Wire

Which interconnection queue projects are advancing and which are not? This is a weekly diff report on generation projects.

2 Scoping

Substation Expansion Tracker

Parsing PJM RTEP and TEAC filings for planned substation additions and upgrades.

3 Registry live · BPA

Large-Load Regulatory Tracking

The Large Load Registry is live for BPA — 291 live requests, 50.5 GW. The regulatory-docket piece is still taking shape.

Large Load Registry is live →