Generation & Storage Asset Registry

Overview

This page shows named, already-connected generation and storage assets — Elexon Balancing Mechanism (BM) units — the "what's already built and where" counterpart to the Generation & Storage Connection Queue (not-yet-connected projects). Each row is one BM unit, restricted to units that represent a single physical site (excluding supplier, interconnector, and other non-site BM unit types), coloured on the map by technology category.

This report has no reliable installed-capacity/MW figure for these assets yet. Elexon's BM unit register doesn't publish one, and a unit's matched connection queue project isn't a sound substitute: that link only exists for units matched to a queue project, and the figure recorded there is a queue-side planning value, not a metered/installed capacity for the operating asset.

Location is also incomplete: some units have no coordinate that could be resolved, so they don't appear on the map. A small share of units (roughly 6%) also has no technology classification and appears on the map as "Not classified", greyed out from the other technology categories.

Registered generation/storage assets (560 located)

Data sources

  • Generation/storage assets: Elexon's Balancing Mechanism (BM) unit register, which names each unit participating in the Balancing Mechanism along with its type and lead party. We classify each unit's technology category from the register's fuel-type codes; a small share of units (roughly 6%) has a fuel-type code we can't map to a category and is labelled "Not classified" on the map. We also restrict the register to units representing a single physical generation or storage site, excluding supplier, interconnector, and other BM unit types that don't.
  • Location and connection route: neither register publishes these directly. We match each named unit against several independent datasets — open mapping data, distribution network records, and NESO's connection queue — accepting a match only where the evidence is strong; candidates that fall short go through manual review. Units with no match by any of these methods have no location and don't appear on the map. Connection route is only populated for units matched to a connection queue project (see below) — it's blank otherwise.
  • Connection queue link: some units can additionally be matched to their originating project in NESO's Transmission Entry Capacity (TEC) register connection queue, by comparing unit and project names.