{"links": [{"rel": "self", "href": "https://ukpowernetworks.opendatasoft.com/api/v2/catalog/datasets/ukpn-constraint-breaches-history"}, {"rel": "datasets", "href": "https://ukpowernetworks.opendatasoft.com/api/v2/catalog/datasets"}, {"rel": "attachments", "href": "https://ukpowernetworks.opendatasoft.com/api/v2/catalog/datasets/ukpn-constraint-breaches-history/attachments"}, {"rel": "reuses", "href": "https://ukpowernetworks.opendatasoft.com/api/v2/catalog/datasets/ukpn-constraint-breaches-history/reuses"}, {"rel": "static_exports", "href": "https://ukpowernetworks.opendatasoft.com/api/v2/catalog/datasets/ukpn-constraint-breaches-history/static_exports"}], "dataset": {"visibility": "domain", "dataset_id": "ukpn-constraint-breaches-history", "dataset_uid": "da_w3o4h0", "has_records": true, "features": ["analyze", "timeserie"], "attachments": [{"id": "data_triage_curtailment_history_xlsx", "title": "Data Triage - Curtailment History.xlsx", "mimetype": "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet", "url": "https://ukpowernetworks.opendatasoft.com/api/v2/catalog/datasets/ukpn-constraint-breaches-history/attachments/data_triage_curtailment_history_xlsx"}], "alternative_exports": [], "data_visible": false, "fields": [{"name": "scheme", "description": null, "annotations": {}, "label": "scheme", "type": "text"}, {"name": "start_time_utc", "description": "Start time of constraint breach in UTC", "annotations": {"facetsort": "-alphanum", "timerangeFilter": true, "timeserie_precision": "hour", "facet": true}, "label": "start_time_utc", "type": "datetime"}, {"name": "end_time_utc", "description": "End time of constraint breach in UTC", "annotations": {"facetsort": "-alphanum", "timeserie_precision": "hour", "facet": true}, "label": "end_time_utc", "type": "datetime"}, {"name": "start_time_local", "description": "Start time of constraint breach in local time", "annotations": {"facetsort": "-count", "sortable": true, "timeserie_precision": "hour", "timerangeFilter": true}, "label": "start_time_local", "type": "text"}, {"name": "end_time_local", "description": "End time of constraint breach in local time", "annotations": {"facetsort": "-count", "sortable": true, "timeserie_precision": "hour"}, "label": "end_time_local", "type": "text"}, {"name": "duration_hours", "description": null, "annotations": {}, "label": "duration_hours", "type": "double"}, {"name": "total_der_access_reduction_kwh", "description": "Total access reduction through curtailment (summed over all DERs) in kWh", "annotations": {}, "label": "total_der_access_reduction_kWh", "type": "double"}, {"name": "event_id", "description": null, "annotations": {}, "label": "event_id", "type": "text"}, {"name": "constraint_id", "description": null, "annotations": {}, "label": "constraint_id", "type": "text"}, {"name": "constraint_description", "description": "Description of constraint breached", "annotations": {"facet": true, "sortable": true, "facetsort": "alphanum"}, "label": "constraint_description", "type": "text"}, {"name": "constraint_voltage_kv", "description": null, "annotations": {}, "label": "constraint_voltage_kV", "type": "int"}], "metas": {"dcat": {"created": null, "issued": null, "creator": null, "contributor": null, "contact_name": null, "contact_email": null, "accrualperiodicity": null, "spatial": null, "temporal": null, "granularity": null, "dataquality": null, "publisher_type": null, "conforms_to": null, "temporal_coverage_start": null, "temporal_coverage_end": null, "accessRights": null, "relation": null}, "inspire": {"theme": null, "type": null, "file_identifier": null, "hierarchy_level": null, "hierarchy_level_name": null, "spatial_resolution": null, "topologic_consistency": null, "contact_individual_name": null, "contact_position": null, "contact_address": null, "contact_email": null, "identification_purpose": null, "extend_description": null, "extend_bounding_box_westbound_longitude": null, "extend_bounding_box_eastbound_longitude": null, "extend_bounding_box_southbound_latitude": null, "extend_bounding_box_northbound_latitude": null}, "default": {"title": "Constraint Breaches History", "description": "<h2>Introduction</h2>\n<p>This dataset records all curtailment events experienced by curtailable-connection customers.<br></p>\n<h2>About Curtailment</h2>\n<p>When a generation customer requests a firm connection\nunder a congested part of our network, there may be a requirement to reinforce\nthe network to accommodate the connection. The reinforcement works take time to\ncomplete which increases the lead time to connect for the customer.\nFurthermore, the customer may need to contribute to the cost of the\nreinforcement works.<o:p></o:p></p><p>UK Power Networks offers curtailable-connections as an alternative\nsolution for our customers. It allows customers to connect to the distribution\nnetwork as soon as possible<i>\u00a0</i>rather than waiting, and potentially paying,\nfor network reinforcement. This is possible because under a curtailable\nconnection, the customer agrees that their access to the network can be\ncontrolled when congestion is high. These fast-tracked curtailable-connections can\ntransition to firm connections once the reinforcement activity has taken place.\nCurtailable connections have enabled faster and cheaper connection of renewable\nenergy generation to the distribution network owned and operated by UK Power\nNetworks.<o:p></o:p></p><p>The Distribution System Operator (DSO) team has\ndeveloped the Distributed Energy Resource Management System (DERMS) that monitors\ncurtailable-connection generators as well as associated constraints on the\nnetwork. When a constraint reaches a critical threshold, an export access\nreduction signal may be sent to generators associated with that constraint so\nthat the network can be kept safe, secure, and reliable.<o:p></o:p></p><p>This dataset contains a record of curtailment actions\nwe have taken and the resultant access reduction experienced by our curtailment-connections\ncustomers. Access reduction is calculated as the MW access reduction from\nmaximum \u00d7 duration of access reduction in hours (MW\u00d7h). The dataset categorises\ncurtailment actions into 2 categories:</p>\n<ul><li>Constraint-driven curtailment: when a constraint is\nbreached, we aggregate the access reduction of all customers associated with\nthat constraint. A constraint breach occurs when the network load exceeds the\nsafe limit.</li> <br>\n<li>Non-constraint driven curtailment: this covers all\ncurtailment which is not directly related to a constraint breach on the\nnetwork. It includes customer comms failures, non-compliance trips (where the\ncustomer has not complied with a curtailment instruction), planned outages and\nunplanned outages</li></ul>\n<p>Each row in the dataset details the start and end\ntimes, durations and customer access reduction associated with a curtailment\nactions. We also provide the associated grid supply point (GSP) and nominal\nvoltage to provide greater aggregation capabilities.<br></p>\n<p>By virtue of being able to track curtailment across\nour network in granular detail, we have managed to significantly reduce curtailment\nof our curtailable-connections customers.<o:p></o:p></p>\n<h2>Methodological Approach</h2>\n<p></p><ul><li>A\nRemote Terminal Unit (RTU) is installed at each curtailable-connection site providing\nlive telemetry data into the DERMS. It measures communications status,\ngenerator output and mode of operation.<o:p></o:p></li>\n<li>RTUs\nare also installed at constraint locations (physical parts of the network,\ne.g., transformers, cables which may become overloaded under certain conditions).\nThese are identified through planning power load studies. These RTUs monitor\ncurrent at the constraint and communications status.<o:p></o:p></li>\n<li>The\nDERMS design integrates network topology information. This maps constraints to associated\ncurtailable connections under different network running conditions, including\nthe sensitivity of the constraints to each curtailable connection. In general,\na 1MW reduction in generation of a customer will cause &lt;1MW reduction at the\nconstraint. Each constraint is registered to a GSP.<o:p></o:p></li><li>DERMS\nmonitors constraints against the associated breach limit. When a constraint\nlimit is breached, DERMS calculates the amount of access reduction required\nfrom curtailable connections linked to the constraint to alleviate the breach.\nThis calculation factors in the real-time level of generation of each customer\nand the sensitivity of the constraint to each generator.\u00a0<o:p></o:p></li>\n<li>Access\nreduction is issued to each curtailable-connection\u00a0via the RTU until the\nconstraint limit breach is mitigated.\u00a0<o:p></o:p></li>\n<li>Multiple\nconstraints can apply to a curtailable-connection and constraint breaches can\noccur simultaneously. <o:p></o:p></li>\n<li>Where\nmultiple constraint breaches act upon a single curtailable-connection, we\napportion the access reduction of that connection to the constraint breaches\ndepending on the relative magnitude of the breaches.\u00a0<o:p></o:p></li>\n<li>Where\ncustomer curtailment occurs without any associated constraint breach, we categorise\nthe curtailment as non-constraint driven. <o:p></o:p></li>\n<li>Future\ndevelopments will include the reason for non-constraint driven curtailment.<o:p></o:p></li></ul>\n<h2>Quality Control Statement<br></h2>\n<p>The dataset is derived from data recorded by RTUs\nlocated at customer sites and constraint locations across our network. UKPN\u2019s Ops\nTelecoms team monitors and maintains these RTUs to ensure they are providing\naccurate customer/network data. An alarms system notifies the team of\ncommunications failures which are attended to by our engineers as quickly as\npossible. RTUs can store telemetry data for prolonged periods during\ncommunications outages and then transmit data once communications are\nreinstated. These measures ensure we have a continuous stream of accurate data\nwith minimal gaps. On the rare instances where there are issues with the raw\ndata received from DERMS, we employ simple data cleaning algorithms such as\nforward filling.<o:p></o:p></p>\n<p>RTU measurements of access reduction update on\nchange or every 30-mins in absence of change. We also minimise postprocessing\nof RTU data (e.g. we do not time average data). Using the raw data allows us to\nascertain event start and end times of curtailment actions exactly and accurately\ndetermine access reductions experienced by our customers.<o:p></o:p></p>\n<h2>Assurance Statement<br></h2>\n<p>The dataset is generated and updated by a script\nwhich is scheduled to run daily. The script was developed by the DSO Data\nScience team in conjunction with the DSO Network Access team, the DSO\nOperations team and the UKPN Ops Telecoms team to ensure correct interpretation\nof the RTU data streams. The underlying script logic has been cross-referenced\nwith the developers and maintainers of the DERMS scheme to ensure that the data\nreflects how DERMS operates. <o:p></o:p></p>\n<p>The outputs of the script were independently\nchecked by the DSO Network Access team for accuracy of the curtailment event\ntimings and access reduction prior to first publication on the Open Data Portal\n(ODP). The DSO Operations team conduct an ongoing review of the data as it is\nupdated daily to verify that the operational expectations are reflected in the\ndata.<o:p></o:p></p>\n<p>The Data Science team have implemented automated\nlogging which notifies the team of any issues when the script runs. This allows\nthe Data Science to investigate and debug any errors/warnings as soon as they\nhappen.<o:p></o:p></p>\n<h2>Other</h2>\n<p>Download dataset information:\u00a0<a href=\"https://ukpowernetworks.opendatasoft.com/explore/dataset/domain-dataset0/download/?format=json&amp;refine.identifier=ukpn-constraint-breaches-history\">Metadata (JSON)</a><br></p>\n<p>Definitions of key terms related to this dataset can be found in the Open Data Portal Glossary: <a href=\"https://ukpowernetworks.opendatasoft.com/pages/glossary/\" target=\"_blank\">https://ukpowernetworks.opendatasoft.com/pages/glossary/</a><br></p> To view this data please register and login.", "theme": ["Network Usage"], "keyword": null, "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "language": "en", "metadata_languages": ["en"], "timezone": ["UTC"], "modified": "2026-04-11T03:00:22.020000+00:00", "modified_updates_on_metadata_change": false, "modified_updates_on_data_change": true, "data_processed": "2026-04-11T03:00:22.020000+00:00", "metadata_processed": "2026-04-11T15:00:39.613000+00:00", "geographic_reference": null, "geographic_reference_auto": false, "territory": null, "geometry_types": null, "bbox": null, "publisher": "UK Power Networks, Company number 3870728", "references": null, "records_count": 24440, "attributions": null, "source_domain": null, "source_domain_title": null, "source_domain_address": null, "source_dataset": null, "shared_catalog": null, "federated": false, "parent_domain": null, "update_frequency": ["DAILY"]}, "dublin-core": {"title": "Constraint Breaches History", "alternative": null, "subject": ["Curtailment", "Generation", "Distribution System Operator (DSO)", "Network Constraint", "Flexibility Services"], "description": "<h2>Introduction</h2>\n<p>This dataset records all curtailment events experienced by curtailable-connection customers.<br></p>\n<h2>About Curtailment</h2>\n<p>When a generation customer requests a firm connection\nunder a congested part of our network, there may be a requirement to reinforce\nthe network to accommodate the connection. The reinforcement works take time to\ncomplete which increases the lead time to connect for the customer.\nFurthermore, the customer may need to contribute to the cost of the\nreinforcement works.<o:p></o:p></p><p>UK Power Networks offers curtailable-connections as an alternative\nsolution for our customers. It allows customers to connect to the distribution\nnetwork as soon as possible<i>\u00a0</i>rather than waiting, and potentially paying,\nfor network reinforcement. This is possible because under a curtailable\nconnection, the customer agrees that their access to the network can be\ncontrolled when congestion is high. These fast-tracked curtailable-connections can\ntransition to firm connections once the reinforcement activity has taken place.\nCurtailable connections have enabled faster and cheaper connection of renewable\nenergy generation to the distribution network owned and operated by UK Power\nNetworks.<o:p></o:p></p><p>The Distribution System Operator (DSO) team has\ndeveloped the Distributed Energy Resource Management System (DERMS) that monitors\ncurtailable-connection generators as well as associated constraints on the\nnetwork. When a constraint reaches a critical threshold, an export access\nreduction signal may be sent to generators associated with that constraint so\nthat the network can be kept safe, secure, and reliable.<o:p></o:p></p><p>This dataset contains a record of curtailment actions\nwe have taken and the resultant access reduction experienced by our curtailment-connections\ncustomers. Access reduction is calculated as the MW access reduction from\nmaximum \u00d7 duration of access reduction in hours (MW\u00d7h). The dataset categorises\ncurtailment actions into 2 categories:</p>\n<ul><li>Constraint-driven curtailment: when a constraint is\nbreached, we aggregate the access reduction of all customers associated with\nthat constraint. A constraint breach occurs when the network load exceeds the\nsafe limit.</li> <br>\n<li>Non-constraint driven curtailment: this covers all\ncurtailment which is not directly related to a constraint breach on the\nnetwork. It includes customer comms failures, non-compliance trips (where the\ncustomer has not complied with a curtailment instruction), planned outages and\nunplanned outages</li></ul>\n<p>Each row in the dataset details the start and end\ntimes, durations and customer access reduction associated with a curtailment\nactions. We also provide the associated grid supply point (GSP) and nominal\nvoltage to provide greater aggregation capabilities.<br></p>\n<p>By virtue of being able to track curtailment across\nour network in granular detail, we have managed to significantly reduce curtailment\nof our curtailable-connections customers.<o:p></o:p></p>\n<h2>Methodological Approach</h2>\n<p></p><ul><li>A\nRemote Terminal Unit (RTU) is installed at each curtailable-connection site providing\nlive telemetry data into the DERMS. It measures communications status,\ngenerator output and mode of operation.<o:p></o:p></li>\n<li>RTUs\nare also installed at constraint locations (physical parts of the network,\ne.g., transformers, cables which may become overloaded under certain conditions).\nThese are identified through planning power load studies. These RTUs monitor\ncurrent at the constraint and communications status.<o:p></o:p></li>\n<li>The\nDERMS design integrates network topology information. This maps constraints to associated\ncurtailable connections under different network running conditions, including\nthe sensitivity of the constraints to each curtailable connection. In general,\na 1MW reduction in generation of a customer will cause &lt;1MW reduction at the\nconstraint. Each constraint is registered to a GSP.<o:p></o:p></li><li>DERMS\nmonitors constraints against the associated breach limit. When a constraint\nlimit is breached, DERMS calculates the amount of access reduction required\nfrom curtailable connections linked to the constraint to alleviate the breach.\nThis calculation factors in the real-time level of generation of each customer\nand the sensitivity of the constraint to each generator.\u00a0<o:p></o:p></li>\n<li>Access\nreduction is issued to each curtailable-connection\u00a0via the RTU until the\nconstraint limit breach is mitigated.\u00a0<o:p></o:p></li>\n<li>Multiple\nconstraints can apply to a curtailable-connection and constraint breaches can\noccur simultaneously. <o:p></o:p></li>\n<li>Where\nmultiple constraint breaches act upon a single curtailable-connection, we\napportion the access reduction of that connection to the constraint breaches\ndepending on the relative magnitude of the breaches.\u00a0<o:p></o:p></li>\n<li>Where\ncustomer curtailment occurs without any associated constraint breach, we categorise\nthe curtailment as non-constraint driven. <o:p></o:p></li>\n<li>Future\ndevelopments will include the reason for non-constraint driven curtailment.<o:p></o:p></li></ul>\n<h2>Quality Control Statement<br></h2>\n<p>The dataset is derived from data recorded by RTUs\nlocated at customer sites and constraint locations across our network. UKPN\u2019s Ops\nTelecoms team monitors and maintains these RTUs to ensure they are providing\naccurate customer/network data. An alarms system notifies the team of\ncommunications failures which are attended to by our engineers as quickly as\npossible. RTUs can store telemetry data for prolonged periods during\ncommunications outages and then transmit data once communications are\nreinstated. These measures ensure we have a continuous stream of accurate data\nwith minimal gaps. On the rare instances where there are issues with the raw\ndata received from DERMS, we employ simple data cleaning algorithms such as\nforward filling.<o:p></o:p></p>\n<p>RTU measurements of access reduction update on\nchange or every 30-mins in absence of change. We also minimise postprocessing\nof RTU data (e.g. we do not time average data). Using the raw data allows us to\nascertain event start and end times of curtailment actions exactly and accurately\ndetermine access reductions experienced by our customers.<o:p></o:p></p>\n<h2>Assurance Statement<br></h2>\n<p>The dataset is generated and updated by a script\nwhich is scheduled to run daily. The script was developed by the DSO Data\nScience team in conjunction with the DSO Network Access team, the DSO\nOperations team and the UKPN Ops Telecoms team to ensure correct interpretation\nof the RTU data streams. The underlying script logic has been cross-referenced\nwith the developers and maintainers of the DERMS scheme to ensure that the data\nreflects how DERMS operates. <o:p></o:p></p>\n<p>The outputs of the script were independently\nchecked by the DSO Network Access team for accuracy of the curtailment event\ntimings and access reduction prior to first publication on the Open Data Portal\n(ODP). The DSO Operations team conduct an ongoing review of the data as it is\nupdated daily to verify that the operational expectations are reflected in the\ndata.<o:p></o:p></p>\n<p>The Data Science team have implemented automated\nlogging which notifies the team of any issues when the script runs. This allows\nthe Data Science to investigate and debug any errors/warnings as soon as they\nhappen.<o:p></o:p></p>\n<h2>Other</h2>\n<p>Download dataset information:\u00a0<a href=\"https://ukpowernetworks.opendatasoft.com/explore/dataset/domain-dataset0/download/?format=json&amp;refine.identifier=ukpn-constraint-breaches-history\">Metadata (JSON)</a><br></p>\n<p>Definitions of key terms related to this dataset can be found in the Open Data Portal Glossary: <a href=\"https://ukpowernetworks.opendatasoft.com/pages/glossary/\" target=\"_blank\">https://ukpowernetworks.opendatasoft.com/pages/glossary/</a><br></p> To view this data please register and login.", "abstract": null, "tableOfContent": null, "type": ["Dataset"], "language": ["eng"], "coverage": null, "spatial": "EPN= Eastern Power Networks; SPN= South Eastern Power Networks; LPN= London Power Networks", "temporal_start": null, "temporal_end": null, "relation": "https://ukpowernetworks.opendatasoft.com/explore/dataset/ukpn-curtailment-events-site-specific/", "source": "https://ukpowernetworks.opendatasoft.com/", "replaces": null, "references": null, "requires": null, "conformsTo": null, "hasFormat": null, "hasPart": null, "hasVersion": null, "isFormatOf": null, "isPartOf": null, "isVersionOf": null, "isReferencedBy": null, "isReplacedBy": null, "isRequiredBy": null, "contributor": null, "creator": "UK Power Networks, Company number 3870728", "publisher": "UK Power Networks, Company number 3870728", "rights": null, "accessRights": ["Open"], "license": "CC BY 4.0", "date_start": null, "date_end": null, "available_start": null, "available_end": null, "created": null, "dateAccepted": null, "dateCopyrighted": null, "dateSubmitted": null, "issued": "2024-02-21T00:00:00+00:00", "modified": "2026-04-11T03:00:22.020000+00:00", "valid_start": null, "valid_end": null, "format": ["text/csv", "application/vnd.ms-excel", "application/json"], "extent": null, "medium": null, "identifier": null, "bibliographicCitation": null, "rightsHolder": null, "accrualMethod": null, "accrualPeriodicity": null, "accrualPolicy": null, "audience": null, "educationLevel": null, "instructionalMethod": null, "mediator": null, "provenance": null}}}}