TEC Register
The data file contains the latest version of the TEC Register including all changes up to publication. This file will be updated twice weekly on Tuesdays and Fridays.
Please note:
Project Nos: We plan to phase out the use of Project IDs in favour of Project Nos which are now found included in the Dataset - we will continue to include Project IDs until the end of this year. If there is more than one Stage the Project No will be followed by a dash and the relevant stage number.
Project IDs: are Case Sensitive i.e. a0l4L0000005iPb; a0l4L0000005ipb and a0l4L0000005ipB relate to different projects.
Staging: If a project includes staged TEC there will be an associated number in the Stage column. Some projects have two separate lines without numbers - this usually indicates that the project is already built and the Customer is perhaps adding a different type of generation or building new generation to be connected at a future date. Once built the second line will fall away and the TEC incorporated into the overall project.
CKAN Data API
Access resource data via a web API with powerful query support.
Further information in the main CKAN Data API and DataStore documentation.
The Data API can be accessed via the following actions of the CKAN action API.
| Query example (first 5 results) |
|---|
https://api.neso.energy/api/3/action/datastore_search?resource_id=17becbab-e3e8-473f-b303-3806f43a6a10&limit=5
|
| Query example (via SQL statement) |
https://api.neso.energy/api/3/action/datastore_search_sql?sql=SELECT * from "17becbab-e3e8-473f-b303-3806f43a6a10" LIMIT 5
|
A simple ajax (JSONP) request to the data API using jQuery.
var data = {
resource_id: '17becbab-e3e8-473f-b303-3806f43a6a10', // the resource id
limit: 5 // get 5 results
};
$.ajax({
url: 'https://api.neso.energy/api/3/action/datastore_search',
data: data,
dataType: 'jsonp',
success: function(data) {
alert('Total results found: ' + data.result.total)
}
});
A simple ajax (JSONP) request to the data API using jQuery.
import urllib2 url = 'https://api.neso.energy/api/3/action/datastore_search?resource_id=17becbab-e3e8-473f-b303-3806f43a6a10&limit=5' fileobj = urllib2.urlopen(url) print fileobj.read()
Data Explorer
Data Explorer
Table Information
Project Name
| Title | Project Name |
|---|---|
| Type | string |
| Description | Name of Generation Project |
| Comment | |
| Example | A'Chruach Wind Farm |
| Unit |
Customer Name
| Title | Customer Name |
|---|---|
| Type | string |
| Description | Name of Generator |
| Comment | |
| Example | A'Chruach Wind Farm Limited |
| Unit |
Connection Site
| Title | Connection Site |
|---|---|
| Type | string |
| Description | Name of Generation Connection Site |
| Comment | |
| Example | A'Chruach Wind Farm 275kV Substation |
| Unit |
Stage
| Title | Stage |
|---|---|
| Type | number |
| Description | Stage refers to Staged TEC – how much TEC the Customer will connect and when. The customer may choose to bring on capacity in chunks to align with their build /commissioning program. Staged contracts are also used when a customer may only be able to bring on a proportion of their total capacity at a particular point in time ahead of further reinforcement works being carried out, completion of which would allow the remaining TEC onto the system. |
| Comment | Field is only completed if the project is staged otherwise it will be empty |
| Example | 1 |
| Unit | number |
MW Connected
| Title | MW Connected |
|---|---|
| Type | number |
| Description | Amount of capacity currently connected to the National Grid |
| Comment | Field will state 0MW until the project is built and connected |
| Example | 43 |
| Unit | MW |
MW Increase / Decrease
| Title | MW Increase/Decrease |
|---|---|
| Type | number |
| Description | Amount of capacity contracted to connect or be removed at a future date |
| Comment | Field will state 0MW unless the TEC is due to increase or decrease |
| Example | 43 |
| Unit | MW |
Cumulative Total Capacity (MW)
| Title | Cumulative Total Capacity (MW) |
|---|---|
| Type | number |
| Description | Total amounty of capacity contracted across all Stages |
| Comment | |
| Example | 43 |
| Unit | MW |
MW Effective From
| Title | MW Effective From |
|---|---|
| Type | date |
| Description | Date on which Connection is contracted to be effective from |
| Comment | Field will only include dates for future connections or increase/decreases to TEC, otherwise this field will be empty |
| Example | 31/10/2032 |
| Unit | yyyy-mm-dd |
Project Status
| Title | Project Status |
|---|---|
| Type | string |
| Description | Indicates what stage the Project is at in it's build cycle |
| Comment | "The Status classifications are very much based on information we have either ascertained from the customer or from another source, i.e. government website. It’s important to note that we hold no authority on the Status classifications on Registers and are produced on an “as far as we are aware” basis. To this end we deem the classifications to mean: Scoping – we are not aware that a planning application has been made Awaiting Consents – we are aware (or the customer has told us) a planning application has been made Consents Approved – we are aware (or the customer has told us) the planning application has been approved" |
| Example | Scoping |
| Unit |
Agreement Type
| Title | Agreement Type |
|---|---|
| Type | string |
| Description | Indicates if the project is connecting directly to the National Grid or if the connection is embedded |
| Comment | Directly Connected or Embedded |
| Example | Directly Connected |
| Unit |
HOST TO
| Title | HOST TO |
|---|---|
| Type | string |
| Description | Indicates which TO is resposible for the connection |
| Comment | NGET, SHET, SPT or OFTO |
| Example | NGET |
| Unit |
Plant Type
| Title | Plant Type |
|---|---|
| Type | string |
| Description | Indicates the fuel type contracted to connect |
| Comment | |
| Example | Wind Onshore |
| Unit |
Project ID
| Title | Project ID |
|---|---|
| Type | string |
| Description | Unique Project Identifier |
| Comment | Please note this ID Reference is case sensitive |
| Example | a0l4L0000005ieS |
| Unit |
Project Number
| Title | Project Number |
|---|---|
| Type | string |
| Description | Unique Project Number |
| Comment | If there is more than one Stage the Project number will be followed by a dash and the relevant stage number. |
| Example | PRO-001136-1 |
| Unit |
Gate
| Title | Gate |
|---|---|
| Type | number |
| Description | Indicates which Gate the Project is contracted at |
| Comment | The value in this field is only completed once a signed Gate 1 or Gate 2 contract is countersigned - until that point all existing contracted projects will appear blank |
| Example | 1 |
| Unit | number |