Flexibility

HOW MUCH HV Zones

Last updated:
Total views:
0
Recent views (14 days):
0
File format: CSV

Dataset description:

Latest analysis tranche reference: T10A

Overview

We are looking to mitigate a range of constraints across multiple voltage levels on the network. As they involve different methods of assessment and operation, our Constraint Management Zones (CMZs) are split into HV Zones, covering constraints at 11kV and above, and LV Zones, covering constraints on our 230/400V networks.

Our HV Zones have Scheduled Availability, Operational Utilisation - Day Ahead product available. In LV Zones we are looking to procure __Scheduled Utilisation services from providers connected at lower voltages.

More information on all products can be found in our latest Procurement Statement. Information on all the constraints we have assessed can be found in the Distribution Network Options Assessment (DNOA).

We undertake flexibility analysis on a regular basis, and we will keep updating this data in line with the latest tranche of analysis.

Data

The data covers overall zonal requirements, including locational data.

Full information on HV Zones is available in the Flexibility_Database_and_Queries.zip. Some useful information has been extracted into csv data files, and the SQL queries used for this are available within the compressed zip file. However, some reports below have been manually edited to improve readability and reduce the number of files, so running queries may not always produce an exact match.

OVERVIEW_All_Zones.csv provides a list of all Constraint Management Zones (CMZs), both HV and LV, which are or will shortly be open for procurement. This file contains some basic information such as the main product and service type in the zone, and provides an indication of how many zones we have active in each Licence Area.

WHERE

Information on where we require flexibility services is contained in the following Postcodes and Polygons files, for combined HV and LV zones. These are updated with each tranche of analysis as zones change and as we improve our data accuracy over time.

As with all geographic data, the Postcodes and Polygons are indicative only and final mapping of assets to zones will be carried out on an asset by asset basis following their registration on Market Gateway. The list of postcodes is deliberately broad, to avoid excluding assets from participation. Wider work is being carried out to improve the accuracy of this data.

HOW MUCH and WHEN

We look to procure Scheduled Utilisation - Specific Periods services within our LV Zones, which is a simple and less targeted product compared to Scheduled Availability, Operational Utilisation - Day Ahead.

HOW_MUCH_and_WHEN_LV_Zones.csv provides information on how much (minimum and maximum kW) we look to procure, the maximum price we can pay (ceiling price), and the delivery periods, which can be Night, Morning, Afternoon or Evening.

The forecasts for our HV zones, such as the estimated peak capacity (MW), energy (MWh), and the ceiling prices, are presented in HOW_MUCH_HV_Zones.csv. Moving to ceiling prices means that the maximum price is now linked with the volume of flexibility required, therefore in most cases ceiling prices will decrease over time as the amount of flexibility required generally tends to grow.

As the requirements for our HV Zones are more complex, granular, and targeted, information regarding when we may need flexibility services is presented in two forms:

  • a simplified, monthly breakdown of potential needs over the years (WHEN_HV_Zones.csv), which should provide an overview of needs over time, and

  • as half-hourly peak MW profile data in WHEN_HV_Zones_MW_Profiles.csv for a year; full profile data is available in the database.

When procurement opens, each Trade Opportunity will contain details of final volumes and delivery periods. Trade Opportunity information is available on the Flexibility – Trades Data and Results page.

Disclaimer

While every effort has been made to ensure its accuracy, the data may contain inaccuracies, omissions, or may be out of date. Users are advised to independently verify any information before relying on it for decision-making or analysis. The creators of this dataset do not assume any liability for errors, inaccuracies, or omissions, nor for any actions taken based on the information contained herein.

Source: Flexibility – Forecasts

Download (CSV)
Fullscreen Embed

This resource view is not available at the moment. Click here for more information.

Download resource

Integrate this resource

Access this data via a web API. Further information in the CKAN API guide (opens in new tab).

Endpoints

The Data API can be accessed via the following actions of the CKAN action API.

Create
https://connecteddata.nationalgrid.co.uk/api/3/action/datastore_create
Update / Insert
https://connecteddata.nationalgrid.co.uk/api/3/action/datastore_upsert
Query
https://connecteddata.nationalgrid.co.uk/api/3/action/datastore_search
Querying
First 5 results:
https://connecteddata.nationalgrid.co.uk/api/3/action/datastore_search?resource_id=4e0e6ddf-9721-4c19-bc68-274eeb460381&limit=5
Results containing 'jones':
https://connecteddata.nationalgrid.co.uk/api/3/action/datastore_search?resource_id=4e0e6ddf-9721-4c19-bc68-274eeb460381&q=jones
Examples
  
    curl -X POST 'https://connecteddata.nationalgrid.co.uk/api/3/action/datastore_search' \
      -H "Content-Type: application/json" \
      -d '{
        "resource_id": "4e0e6ddf-9721-4c19-bc68-274eeb460381",
        "limit": 5,
        "q": "jones"
      }'
  

  
    using System;
    using System.Net.Http;
    using System.Text;
    using System.Text.Json;
    using System.Threading.Tasks;

    var data = new {
      resource_id = "4e0e6ddf-9721-4c19-bc68-274eeb460381", // the resource id
      limit = 5, // get 5 results
      q = "jones" // query for 'jones'
    };

    var url = "https://connecteddata.nationalgrid.co.uk/api/3/action/datastore_search";

    using var client = new HttpClient();
    var json = JsonSerializer.Serialize(data);
    var content = new StringContent(json, Encoding.UTF8, "application/json");

    try {
      var response = await client.PostAsync(url, content);
      response.EnsureSuccessStatusCode();
      var responseBody = await response.Content.ReadAsStringAsync();
      var result = JsonSerializer.Deserialize<JsonElement>(responseBody);
      Console.WriteLine($"Total results found: {result.GetProperty("result").GetProperty("total")}");
    } catch (HttpRequestException e) {
      Console.WriteLine($"Error fetching data: {e.Message}");
    }
  

  
    const data = {
      resource_id: '4e0e6ddf-9721-4c19-bc68-274eeb460381', // the resource id
      limit: 5, // get 5 results
      q: 'jones' // query for 'jones'
    };

    const url = new URL('https://connecteddata.nationalgrid.co.uk/api/3/action/datastore_search');
    Object.keys(data).forEach(key => url.searchParams.append(key, data[key]));

    fetch(url)
      .then(response => response.json())
      .then(result => {
        console.log('Total results found: ' + result.result.total);
      })
      .catch(error => {
        console.error('Error fetching data:', error);
      });
  

  
    import urllib.request
    import urllib.error
    import json

    url = 'https://connecteddata.nationalgrid.co.uk/api/3/action/datastore_search?resource_id=4e0e6ddf-9721-4c19-bc68-274eeb460381&limit=5&q=title:jones'  
    
    try:
        with urllib.request.urlopen(url) as response:
            data = json.loads(response.read().decode('utf-8'))
            print(f"Total results found: {data['result']['total']}")
    except urllib.error.URLError as e:
        print(f"Error fetching data: {e}")
  

  
    $data = [
      'resource_id' => '4e0e6ddf-9721-4c19-bc68-274eeb460381', // the resource id
      'limit' => 5, // get 5 results
      'q' => 'jones' // query for 'jones'
    ];

    $url = 'https://connecteddata.nationalgrid.co.uk/api/3/action/datastore_search';

    $ch = curl_init($url);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    curl_setopt($ch, CURLOPT_POST, true);
    curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode($data));
    curl_setopt($ch, CURLOPT_HTTPHEADER, ['Content-Type: application/json']);

    $response = curl_exec($ch);
    $httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    curl_close($ch);

    if ($httpCode === 200) {
      $result = json_decode($response, true);
      echo "Total results found: " . $result['result']['total'];
    } else {
      echo "Error fetching data: HTTP " . $httpCode;
    }

Data Dictionary

Data Dictionary: Column definitions and metadata for this resource
Column Type Label Description Example
Availability ceiling price [£/MW/h] numeric £/MW/h Not provided- 48.2
CMZ Code text nan

Unique Constraint Management Zone code

 CMZ_T10A_WM_0025
Estimated availability energy [MWh] numeric MWh

Estimated availability MWh energy required in the year

 3907.74
Estimated utilisation energy [MWh] numeric MWh

Estimated utilisation MWh energy required in the year

 153.23
Financial Year numeric Not provided-

Year captured in financial year, as an example a financial year of 2027 would represent a calendar month and year range of April 2026 to March 2027 inclusive.

 Not provided-
Main flexibility product text nan

Main flexibility product

 Scheduled Availability, Operational Utilisation - Day Ahead
Peak capacity required [MW] numeric MW

Maximum capacity required in the zone throughout the year

 21.3
Scenario text nan

Load data set scenario

 Holistic Transition
Utilisation ceiling price [£/MWh] numeric £/MWh

Maximum price for utilisation

 2893.6
Zone name text nan

Zone name

 Albrighton Primary