Wholesale Discussions

Missing NRSS Datasets

2025-09-09T01:47:19.6630000

Hi,

Does anyone know why NRSS is missing in August 2024?

https://www.emi.ea.govt.nz/Wholesale/Datasets/ForecastPrices/NRSS/2024

Cheers,

Isaac

Resources for understanding the electricity trading market

2025-08-12T09:10:48.6170000

Hi, I'm working on a project & need to fully understand how trading works. I can see the trading files available at https://www.emi.ea.govt.nz/ - wondering if anyone can point me to some documentation to understand how they relate to each other, the rules for trading etc. Basically any kind of "this is how the market works" technical resource. Help much appreciated, thank you.

Cleared energy and offer stacks

2025-08-21T21:55:10.7370000

2 Queries:

I looked at the Wholesale Price trend and the cleared offer stack for New Zealand on 21/08/2025. (Can't insert images because I get the message "This content is blocked. Contact the site owner to fix the issue."). For example, if I take a single TP, TP30, the demand has cleared in the $0-$10/MWh band for 5252.61MW demand. But, in the Wholesale Price trend, the price is $189.09/MWh. I find this difference in the cleared offers for every trading period, and I can't find the reason.
In the "Energy and Offer stack" 's More Information section, it is mentioned that I can drill down to the individual node level but can only work out the island-level data.

Full historical wholesale final prices for a single node

2025-08-18T01:02:12.1600000

I found that the dataset here covers dataset back to 2020 only.

Would you be able to guide me how to get full range datasets for historical wholesale prices?

Many thanks

Where did the spans go?

2025-08-11T02:34:37.1630000

Heya! I remember a couple of years ago I was able to get really detailed transmission line span data, I came back looking for it for a new project and i am not able to find it anywhere in the datasets or anywhere else - Am I looking in the wrong place or is this gone now? Thanks

I also remember data that had information on all the nodes, distrubtor etc - I belive this was in the same place but also cant find it

Generation - Pukenui Solar Farm

2025-08-14T21:47:48.1970000

Poking around the volumes, generation datasets, I can't seem to locate anything for Pukenui Solar Farm (Far North Solar Farm's latest - node KOE1101). Any advice if it is meant to be there or not?

UFE report not updated

2025-07-03T10:03:53.2930000

Seems the UFE dataset doesn't go beyond September 2024.

I've been tracking networks with negative UFE as this impacts Solarzero custmers charged for losses on a volumetric basis rather than within the energy kWh rate.

Branch Constraints

2025-07-10T01:20:01.2930000

I was looking through the vSDP outputs folder and found the excelsheet documenting the branch constraints. File is named BrConstraintResults_TP

The headers of the table are:

DateTime BranchConstraint LHS (MW) Sense (-1:<=, 0:=, 1:>=) RHS (MW) Price ($/MWh)

Am I correct in thinking that the branch constraints are the capacities of said branches and the LHS, RHS are the direction of power flow (i.e. from Huntly to Benmore and vice versa). So that we can calculate the change in capacity consumption given a change in demand.

Hydro storage information

2024-01-18T01:58:12.3700000

Hi, is there a dashboard with national hydro storage - ideally by island and then by catchment - relative to long run averages.

Thanks

Chris

Reconciled Injections and Offtake file is missing Island for HTU0331

2025-06-12T21:52:04.7800000

Hi,

the latest Reconciled Injections and Offtake file is missing the Island for PointOfConnection = HTU0331, are you able to supply new file?
https://www.emi.ea.govt.nz/Wholesale/Datasets/Volumes/Reconciliation/2025 file: ReconciledInjectionAndOfftake_202505_20250609_161909.csv.gz

Many thanks,

Mike

Reconciling differences in ClearedMW from Cleared Offers and offers obtained from SPD case files

2025-05-13T03:59:26.5300000

Hi team,

We've found a few instances of a plant having ClearedMW in the Cleared Offers file which is incompatible with the offers submitted for the plant for that given time period.

Example:

7/05/2025 12:00:00 pm
THI2201 THI1 cleared 59MW with an offer of one tranche of 25MW at 0.01 and 75MW at 5000.

Help with clarifying our misunderstanding here is much appreciated.

Regards,

Perry

GEM Mathematical Formulation

2025-05-16T00:33:23.6830000

Hello,

Kia Ora. I'm looking for the mathematical formulation document of GEM. Could someone please share or point to its location on the web?

Best Regards,

Naren

Final Price data for April 2025

2025-05-07T01:52:09.0970000

There doesn't appear to be any April 2025 final prices, March is there and May todate is there, just no April. Please see screen shot in attached file

Ashley Wall

Dispatch Notification Load

2025-04-27T23:23:00.0930000

I have some questions re Dispatch Notification Load (DNL):

Is anyone currently participating in the wholesale market via DNL?
If they are, would this appear in the 'Bids' wholesale dataset?
If so, is there any way to differentiate DNL vs DD in the bids data?

Thanks!

NodalPricesAndVolumes data - Missing latest

2025-05-01T01:10:47.8070000

The NodalPricesAndVolumes data is missing the last 2 days and some (last run seems to be on 30/4 for 29/4 data which is partially there). Can someone please advise if this is expected?

Bream Bay Node missing from Generation Trends report

2025-04-16T01:05:37.3830000

Kia ora,

The Generation Trends report looks to have not been updated to include the Bream Bay node, which with Meridian's new battery is a generation node once again. Could this be added to the report please?

Cheers, Keith

DST issue

2025-04-06T20:51:02.4400000

Hi team,

The data for the 06-04-2025 stops at TP6 in here https://www.emi.ea.govt.nz/Wholesale/Datasets/DispatchAndPricing/NodalPricesAndVolumes/2025

Could you please take a look and fix?

Regards,

Gislain

Unaccounted for Electricity

2019-05-13T08:41:20.3970000

I'm having another look into UFE allocation and would like to use publicly available information. The EA education portal advises that a total summary of UFE from 1 May 2008 by balancing area is available on email request to marketoperations, however this seems not to be the case. Please advise?

EDIT: link to Education portal content on UFE data availabiltiy: unaccounted-for-electricity-ufe

Offers data - IsLatestYesNo Column

2025-03-31T23:59:32.0300000

Hi team,

I'm currently looking at the offers data (https://www.emi.ea.govt.nz/Wholesale/Datasets/BidsAndOffers/Offers/) and am wondering how the IsLatestYesNo column is populated as I can find several instances where for a given plant/unit/TP combination there is no row with that column set to Y. Can someone advise how this works?

Regards,

Perry

Metered Data - General Info + Schema information

2025-02-02T18:41:28.4830000

Hello, new to the platform. Is there any intention to update the information that comes under Wholesale/Metered data?

Ideally I could get a bit of information about the schemas and how these datasets were created.

Water values

2025-01-29T20:47:33.2900000

I know I should embrace change but what happened to water values? Is it my imagination or did you start calculating and publishing them and then you just stopped doing them and removed them from the website? And can you tell me the story about them if you did?

Reconciled Injections and Offtake file is missing Island for WAI0331

2025-01-14T19:36:19.4470000

Hi,

the latest Reconciled Injections and Offtake file is missing the Island for PointOfConnection = WAI0331, are you able to supply new file?
https://www.emi.ea.govt.nz/Wholesale/Datasets/Volumes/Reconciliation/2024 file: ReconciledInjectionAndOfftake_202412_20250114_143228.csv.gz

Many thanks,

MIke

Are generation and demand on EA website forecast or actual?

2024-12-03T20:04:19.2530000

Hi,

In the nodal price and volume files at Electricity Authority - EMI (market statistics and tools), the rundatetime is usually one minute before the intervaldatetime. Does this mean that the generation and demand in a case are forecast instead of actual for the time period in the case?

Regards,

Ziming

Pre-dispatch quantities

2024-12-15T22:47:58.6800000

Hello,

I am trying to understand how to get pre-dispatch data.

If I understand correctly, pre-dispatch prices and quantities are obtained after running the SPD model using pre-dispatch offers and bids data. (and other information)

Pre-dispatch prices seem to be available here: ForecastPrices.

Is the data for pre-dispatch quantities available?

Thank you,

Erwann

Adding a new offer to the vSPD input data

2019-05-29T22:28:10.2070000

Hi all,

We were recently asked how to add a new offer to vSPD for testing purposes. To be clear, this question pertains to the standalone version of vSPD, and not vSPD-online.

Currently, we can easily modify the existing offer in vSPD but it is not straightforward to add a new (undeclared) offer into vSPD. In this topic, I will present some sample code that can be used to add a new offer ("ABC2201 XYZ0" ) to an existing location/pnode (e.g. HAM2201). I would recomend that this code snippet be inserted between code sections 4 and 5 of the vSPDSolve.gms file as follows:

*=====================================================================================

* 4. Input data overrides - declare and apply (include vSPDoverrides.gms)

*=====================================================================================

$ontext

- At this point, vSPDoverrides.gms is included into vSPDsolve.gms if an override file defined by the $setglobal vSPDinputOvrdData in vSPDSetting.inc exists.

- All override data symbols have the characters 'Ovrd' appended to the original symbol name. After declaring the override symbols, the override data is installed and the original symbols are overwritten.

- Note that the Excel interface permits a limited number of input data symbols to be overridden. The EMI interface will create a GDX file of override values for all data inputs to be overridden. If operating in standalone mode, overrides can be installed by any means the user prefers - GDX file, $include file, hard-coding, etc. But it probably makes sense to mimic the GDX file as used by EMI.

$offtext

$if exist "%ovrdPath%%vSPDinputOvrdData%.gdx" $include vSPDoverrides.gms

*--------- adding a new generation offer ---------------------------------------------

$onmulti

*1. Declare a new offer (Ex: "ABC2201 XYZ0")

set i_Offer 'Adding generation offer' / 'ABC2201 XYZ0' / ;

$offmulti

*2. Map the new offer to an existing pnode (Ex: "HAM2201")

i_tradePeriodOfferNode(tp, 'ABC2201 XYZ0', 'HAM2201') = yes ;

*3. Map the new offer to an existing trader (Ex: "38486") . You can use any trader in the i_trader list

i_tradePeriodOfferTrader(tp,'ABC2201 XYZ0','38486') = yes ;

*4. Adding offer paremeter data

i_tradePeriodOfferParameter(tp,'ABC2201 XYZ0','i_initialMW') = 0;

i_tradePeriodOfferParameter(tp,'ABC2201 XYZ0','i_reserveGenerationMaximum') = 10000;

i_tradePeriodOfferParameter(tp,'ABC2201 XYZ0','i_windOffer') = 0;

i_tradePeriodOfferParameter(tp,'ABC2201 XYZ0','i_FKbandMW') = 0;

i_tradePeriodOfferParameter(tp,'ABC2201 XYZ0','i_rampUpRate') = 9999;

i_tradePeriodOfferParameter(tp,'ABC2201 XYZ0','i_rampDnRate') = 9999;

i_tradePeriodRiskGenerator(tp,'ABC2201 XYZ0') = no ;

*5. Adding offer quantity and price

i_tradePeriodEnergyOffer(tp,'ABC2201 XYZ0','t1','i_generationMWoffer') = 100 ;

i_tradePeriodEnergyOffer(tp,'ABC2201 XYZ0','t1','i_generationMWofferPrice') = 0.01;

i_tradePeriodEnergyOffer(tp,'ABC2201 XYZ0','t2','i_generationMWoffer') = 100 ;

i_tradePeriodEnergyOffer(tp,'ABC2201 XYZ0','t2','i_generationMWofferPrice') = 1000;

*=====================================================================================

* 5. Initialise constraint violation penalties (CVPs)

*=====================================================================================

Please post any related questions below, new questions in a new discussion, or drop us an email via the emi email address.

Hope this helps,

Tuong Nguyen.

Energy shortfall and resolve in vSPD

2024-12-08T21:29:46.1000000

Hi,

In vSPD, if energy shortfall check fails then the model is resolved. Sometimes, after several resolves, the solver finds a solution but vSPD freezes when reading the solution. What is the purpose of the energy shortfall and what causes vSPD to freeze when reading the solution?

Regards,

Ziming

vSPD-online failing to create jobs

2024-07-23T14:10:09.8530000

Hello,

I tried twice to create a job in vSPD just for a couple of days without any override and both times the job failed to solve. I also noticed that this has been the case for all recent attempts from other users. Is there any particular reason for that?

Thank you in advance!

Output GDX files for vSPD

2024-11-17T20:34:57.6900000

Hi there

On the main vSPD page it says "vSPD output is generated as a collection of GDX and CSV files". However, when I run vSPD in GAMS Studio, it appears that only CSV files are added to the Output folder. I require GDX files for more efficient analysis of the output data. Can you please indicate where the GDX output files are, or provide instructions on how they can be created?

Thanks

GDX files for Oct 21 and 22, 2024 not available

2024-11-07T22:55:03.4070000

Hi,

The gdx files for Oct 21 and 22, 2024 are not available for download on the webpage at Electricity Authority - EMI (market statistics and tools) I wonder when they will be availabe. Thank you.

Regards,

Ziming

"Try it out" not working for me

2024-10-30T03:28:47.3970000

Hi there,

Newbie here, trying to wrangle these APIs using Python. I wasn't getting much luck with my Python code, so I went here to try it out there:

https://developer.electricityinfo.co.nz/WITS/documentation/market-prices#/Market%20Prices/get_nodes

At the top of that page I signed into the client_id and client_secret as per what I have registered for OAuth on the developer portal.

Though I note that I didn't fill in "redirect_uris" parameter - what should this be?

I was trying to get a list of Schedules, here is the response

401:

 cache-control: max-age=0, no-cache, no-store  content-length: 12  expires: Wed, 30 Oct 2024 03:25:03 GMT  pragma: no-cache

This is not using my code but on the "Try it out" button, no additional parameters needed.

Can sombody tell me what I'm doing wrong?

Best regards,

Hemon

Period 48 missing in Demand Trends

2024-10-23T01:19:54.8000000

HI there

It appears the 48th period 23.30 - 00.00 is consistently missing in this report:

Can it be looked it?

Expected Water Values: Reservoir levels data

2024-10-02T21:26:11.2830000

Hi,

I am intested in the units for data in the "reservoirs.csv" file in the Expected water values dataset. The file itself does not detail any units, the dataset description (here) does note "reservoir levels"/"observed reservoir levels" , however it does not specifically mention any units in particular. (I have added some screenshots of the file I am refering to below).

I was wondering if you would be able to provide the units for the reservoir levels?

Additionally any context you can provide around the sourcing and nature of the reservoir levels data would also be much appreciated.

Cheers,

Matthew

Bids/Offers and Final Energy Prices

2024-07-23T08:51:12.6200000

Hello,

I try to understand how the demand and supply schedule, hence the price formation, are related to the Bids and Offers files found at this link: Electricity Authority - EMI (market statistics and tools) (ea.govt.nz)

What puzzles me is that while for each trading period of each day a final price for every node (242 nodes) is calculated (as can be seen at Electricity Authority - EMI (market statistics and tools) (ea.govt.nz)), the respective Bids and Offers files do not contain buy and sell orders for all the nodes for the same day.

Moreover, the Bids and Offers files do not contain the same nodes, I assume this happens because generators submit offers for Grix Injection Points while buyers submit bids for Grid Exit Points. However, even if this is the case, how are prices formatted if we do not have both supply and demand for each node?

Thanks in advance.

Wholesale category / Datasets Wholesale market volumes Reconciled injections and offtake

2024-07-10T21:19:39.0400000

The file ReconciledInjectionAndOfftake_202406_20240706_121016.csv contain missing value for Island for PointOfConnection: TAB0331, Network: HAWK. Can you take a look and resolve?

Thanks.

Pricing 20240417 and 29 gdx file not available

2024-05-14T20:26:55.5700000

Hi Phil,

I wonder when the pricing 20240417 and 20240429 gdx files will be made available.

Regards,

Ziming

Data missing from reserve prices

2024-05-06T22:34:57.6400000

Hi,

I noticed this dataset is missing 4 datapoints.

Date                            Interval Number
Sunday, 2 April 2023            7
Sunday, 2 April 2023            8
Sunday, 24 September 2023       47
Sunday, 24 September 2023       48

cheers

jamie

Pricing 20240312 gdx file not available

2024-03-25T23:10:39.4570000

Hi EA,

The Pricing gdx file for 20240312 is not available for download. I wonder when it will be available.

Regards,

Ziming

GAMS cloud service and Gurobi to solve vSPD 5.0

2024-03-27T19:45:50.3670000

Hi,

GAMS provides a cloud service Engine SaaS but it is a Linux system. Has anyone used this cloud service to solve vSPD 5.0? Also, has anyone used Gurobi solver instead of Cplex solver in solving vSPD 5.0?

Regards,

Ziming

Trading: Spot verses Forward Contract

2024-03-18T21:33:21.8870000

Hello,

Is there anywhere where I can see what percentage of supplied power is purchased as a forward contract and what percentage is purcahsed on the spot market?

Data Dictionary - description of data available

2024-03-15T07:40:59.4900000

Hi,

Do you have a data dictionary / document describing what data you have available including a description of each of the data elements and their data types? Also the frequency of when the data is updated and made available would be useful. We are interested in both actual/historical data and forecasts. Looking for a description of the data you have available in the wholesale datasets and also any other data you would have available that we'd be able to access automatically via a download script or via a tool such as Azure Storage Explorer.

Thanks in advance for anything you can provide.

Regards

Mark

Data missing in Aug 9, 2021 gdx file final version

2024-02-19T02:56:28.2670000

Hi,

In the Aug 9, 2021 gdx file final version, the data after 6pm is missing. Will this file be updated?

Regards,

Ziming

access issues with EMI datasets

2024-01-28T20:11:22.7500000

Morning,

I'm having issues accessing EMI datasets using the latest SAS key in the below post ...

New access arrangements to EMI datasets (retirement of anonymous FTP) (ea.govt.nz)

"https://emidatasets.blob.core.windows.net/publicdata?sv=2021-10-04&si=exp2024-03-31&sr=c&sig=fH6rIJPLMPtmt37cC6CZk44UDLs0E0C9Sy695KQCxlo%3D"

am getting ...

{"The remote server returned an error: (400) Bad Request."}

Has been working fine for a long time until Wenesday last week.

Could you advise ?

Thanks in advance

2023 PowerFactory cases have been uploaded

2023-12-12T02:42:13.0100000

The Power Systems Engineering team at Transpower have supplied new 2023 PowerFactory case files. The updates are described in the 202311 PDF file.

Report Q - Generation output by plant - how to identify unique plant, understand duplicates?

2023-12-04T03:47:25.4630000

I am seeking some clarification in how to analyse the generation output by plant datasets (https://www.emi.ea.govt.nz/Wholesale/Datasets/Generation/Generation_MD). Which columns need to be combined to uniquely identify the singular plants data?

Is it the unique combinations of a Network code, generator code, and POC? Ive included some example combinations below from looking at the dataset 202310_Generation_MD to which I was hoping to get clarification around please.

1. at TWC2201, there is one NW code TRPG, and a dataset for each gen code te_rere_hau, and twf_3. This looks to example that the POC cannot be the sole identifier and that this is therefore two different generation plants that inject as the same NSP?

2. at LTN2201, there is one NW code MRPL, but two data sets for the same gen code turitea. One with a fuel/tech type of wind, one with fuel/tech blank. The kWh data for each set appears identical - is this an error, or is this correct and the two datasets should be combined for the turitea total? (Is one of the sets for turitea north and one for turitea south?)

3. at ARI1102, there is one gen code arapuni, that has two network codes MRPL and POCO. One of which data set appears to be all 0 kWh. Is this the same generation plant and can inject across two networks at the same POC? Or is this a case of a change in network company historically, the old remains and will report as zero?

Much appreciated

Laura

Missing wind farms from Generation output by plant: YYYYmm_Generation_MD.csv files

2023-12-01T00:56:58.7930000

The files YYYYmm_Generation_MD.csv files are missing generation data from the following wind farms:

GOR0331_KWD0 HRP2201_HRP0 WIL0331_MCK0 HWB0331_MAH0

The em6 API is returning SCADA for these wind farms yet they do not appear in the EA EMI .csv files.

Real-time pricing on 1 November 2022 - impact on EMI reports and datasets

2022-10-13T01:53:53.3330000

Real-time pricing (RTP) goes live on 1 November 2022. The implementation of RTP will necessitate changes to a lot of the data received, processed, and published by the EMI team. If you are a regular user of Wholesale reports or Wholesale datasets, you might want to keep an eye on this discussion for regular updates over the next few weeks.

Changes are going to be made with very little notice. Some reports or datasets may be stopped altogether on 1 November and restored in the following days or weeks.

vSPD and GDX files

The vSPD model is undergoing substantial change and testing in readiness for real-time pricing. A new version of vSPD will very soon be made available. It will not be backward compatible with the current version. After 1 November 2022, if you want to run simulations that span 30 Oct / 1 Nov 2022, you’ll need to use both versions of vSPD, i.e. the current and the new versions.

GDX files are currently produced from the ex post final pricing (FP) SPD cases. FP GDX files will cease to exist after 1 November and in their place GDX files will be produced from the real-time dispatch (RTD) cases. There will be an indeterminate number of these per day but typically there will be well over 200. These new RTD GDX files will be published beginning 1 Nov. At some point after 1 November 2022, we will change the GDX processing to package all RTD GDXs for a day (midnight to midnight) into a single GDX file, which will be published early in the morning (2-3am’ish) of the following day. The daily RTD GDX file, when we start publishing it, will be approximately six times larger than the current FP GDX files.

Dispatch and pricing

A new wholesale dataset folder will be created called DispatchAndPricing. Beginning on 1 November, the following datasets will be published into subfolders of this new folder as follows:

DispatchEnergyPrices – Dispatch energy prices: the ‘new’ real-time energy prices that will replace the current real-time (or 5-min) prices published here. The current real-time prices will cease to be produced from 1 Nov.
DispatchReservePrices – Dispatch reserve prices: the 'new' real-time reserve prices.
GDX: the RTD GDX files as described above.
CaseFiles – RTD case files: the RTD case files.
InterimPrices – Interim prices: from 1 November 2022, interim prices will be calculated as a time-weighted average of the 'new' real-time prices. Interim prices will pertain to the entire trading period.
FinalPrices – Final prices: if no pricing error claim is lodged pertaining to interim prices, then interim prices will be declared final by 2pm the following business day. Whereas interim prices will be published by trading period, i.e. one file per trading period, final prices will be published by day, i.e. one file per day containing prices for all trading periods from the previous day.

vSPD online

vSPD online will be disabled on 1 November until such time as we get it rebuilt to work with both the new and old versions of vSPD.

Final pricing dataset

The final pricing dataset will cease to be populated beginning on 1 November 2022. The entire folder will likely be archived within the Dispatch and pricing folder described above.

New version of vSPD and new daily GDX files

2023-10-09T23:58:28.8200000

Today we are starting the roll out of a substantial update to vSPD and its associated GDX files.

Since the advent of real-time pricing on 1 November 2022, a time-weighted average of the dispatch prices is used to calculate the price that each trading period is settled on. This occurs for both energy prices by node and reserve prices by island. Dispatch prices are typically derived from the RTD SPD schedules. But the PRSS schedule can also be the source of dispatch prices, especially for the first few minutes of a trading period.

Post 1 Nov 2022 daily GDX files

We currently produce and publish a GDX file for all PRSS and RTD case files. But not all PRSS and RTD schedules give rise to prices that are published as dispatch prices, which then go into the calculation of final prices. When we learn which schedules feed into final prices, we merge them into a single, daily GDX file and, starting today, are publishing them in folders by year going back to 1 November 2022. The daily GDX files will be published early each morning and will pertain to all trading periods from the preceding day, ie the file called Pricing_20231020.gdx will pertain to 20 October 2023 and will be published early on 21 October.

In a few weeks' time, we'll stop publishing the RTD and PRSS GDX files but will continue to publish all RTD and PRSS case files.

The new daily GDX files will only work with vSPD v5.0.0.

vSPD v5.0.0

In the next day or two, we will publish version 5.0.0 of vSPD. This release will represent a major update of vSPD that features many new innovations to simplify the replication of prices post real-time pricing and the undertaking of counterfactual analyses. Version 5.0.0 will only work with the daily GDX files dating back to 1 November 2022.

Version 4.0.0 will be deprecated as it will no longer serve any useful purpose. We made it available for users that wanted to solve vSPD following the start of real-time pricing but couldn't wait until we released v5.0.0. Version 4.0.0 requires the individual RTD or PRSS schedules, which, as noted above, we are soon going to stop publishing.

For analysis of dates preceding 1 November 2022, vSPD v3.1.0 should be used along with the old final pricing GDX files.

In the coming weeks, we will publish some Python code that allows an override GDX file to be created so that counterfactual experiments can be run using vSPD v5.0.0. Thereafter, we will work on a publicly available tool to replace vSPD online for dates since 1 November 2022.

Generation output by plant and capacity factors

2023-10-16T00:50:46.0770000

Hey all,

I am working with the wholesale dataset "Generation output by plant". Right now I am trying to calculate a capacity factor for the geothermal generation. For that I am also using the data provided by the MBIE on the amount of capacity installed. For different years this gives me a capacity factor of about 82%. However, it should be more like 90-95%, shouldn't it?

Is the discrepency coming from curtailed geothermal production or what am I missing? Could someone point me in the right direction or explain the dataset to me?

Cheers,
David

Sensitivity of price to changes in load

2023-10-12T00:29:01.9730000

Hi EMI team,

Recently you have released new Wholesale report "Sensitivity of price to changes to load", https://www.emi.ea.govt.nz/Wholesale/Reports/O5XQOI?_si=v|3

It is a great piece of information but I couldn't find a way to download historic dataset, only data for one day.

Can you please help to get access to historical dataset? Is there a way to download it through Azure Storage Explorer?

Thanks, Olga

Open source alternative to GAMS/vSPDonline

2023-08-28T23:01:07.4930000

Hi,

I've been using vSPD-online in recent weeks. Whilst it is a useful tool and allows running of simple counter-factuals, I find that the interface is a little limited and it is also hard to automate market simulations. I understand you make all the GDX files available which allows you to "self-host" and run models yourself. However, this relies on having the propietary tool GAMS, which costs several thousand $ for a commercial license.

Anyway, is there a way to run GDX files and SPD models using an open source alternative? This would be very beneficial to industry consumers.

Power ratings of transmission network in NZ

2023-09-15T09:33:22.4670000

Is there a consolidated document which enlists the power ratings of various transmission lines (all voltages or atleast 220kV and above) as shown below for both North and South Islands?

Best,
Ashish

Data on bidding price by various generators - daily offer stack

2023-09-14T09:39:34.5600000

Hello Community admins and members,

Where can I find the daily offer stacks with price bands (with technology type) by trading periods as shown in the EA trading conduct report on Figure 14, Page 10 here

Thank you

Best,

Ashish

Units of embedded generation

2023-08-07T13:41:06.1200000

Hello everyone,

I have just started querying EMI data.

Specifically I'm looking at the embedded generation data set

I only have a basic understanding of power markets so I am wondering what are the units for the values shown?

Is there any place where I can find this kind of information (i.e. metadata about the data sets) for future data sets?

Thanks in advance and kind regards

PS: Congrats to the team who built the data access system. It's great compared to what you find in other countries

Cleared offers - energy, FIR and SIR - now available on EMI

2023-06-22T03:35:11.8730000

Cleared offers extracted from RTD SPD case files are now available on EMI.

A new file will be published at about 7:00am each morning containing all of the RTD cleared offers from the preceding day, midnight to midnight.

Adding RunDateTime to nodal price and volume data files

2023-06-14T20:48:27.1530000

Next week we will modify the nodal price and volume CSVs published on EMI datasets by adding the SPD case RunDateTime.

The new column will appear following IntervalDateTime and before CaseTypeCode.

This is necessary because there is no other way to know the chronological order of the cases when there is more than one RTD case per 5-minute interval.

Please let us know if you have automated processes to handle these files and therefore require a greater lead time before we make this change.

Current generation fleet dataset

2023-05-29T22:51:27.4430000

Kia ora koutou,

I was looking for the most recent, up-to-date xls of the generation fleet. I used to be able to find it on the EA website via google. I think the version on EMI is from pre-2020:

https://www.emi.ea.govt.nz/Wholesale/Datasets/Generation/Generation_fleet/Existing/

Please could you update with the current version?

Thanks!

NodalPricesAndVolumes - Data issue

2023-05-03T20:47:48.7100000

It looks like we only got half a day of data for 02/05/2023 and no data for 03/05/2023 with this dataset. Is there an ongoing issue here?

New EMI report: scheduled generation outages

2023-05-07T23:46:05.6430000

We've published a new report that shows scheduled generation outages by generation type, participant and island. See also the news item here.

Network Pricing Schedules

2023-03-26T21:52:55.1370000

I would like to access nationwide pricing schedules but it seems this is not published in a centralised format.

Is the only way to get this information to go to individual EDB's and extract from their website disclosures or are these all filed and accessible somewhere?

Thanks

Clive

Wholesale Price Trends data

2022-03-27T17:12:56.3170000

Hi,

There seems to be missing the Wholesale Price Trend data starting from March 24th. Would it be possible to upload it please?

Thanks a lot,

Mathieu

Where and how to source comprehensive price, dispatch, CO2 intensity and reservoir data?

2023-02-09T01:37:20.3830000

Hi everyone
I am very new to New Zealand electricity grid and wholesale market and was tasked to collect and analyse as much as possible NZ spot/forward price, dispatch, carbon intensity and hydro reservoir data without having to use paid data suppliers and leveraging as much as possible of public domain and real time and up to date information.
Would anyone be able to help poiting me to the exsiting datasets, tools and/or dashboards within or outside EMI's portal?
Thank you so much in advance for your attention and help!
Kind regards,
Gabriel

Data on daily offer stack

2023-01-31T07:58:16.5470000

Hello Community admins and members,

Where can I find the daily offer stacks with price bands (with technology type) by trading periods as shown in the EA trading conduct report on Figure 14, Page 10 here

Thank you

Best,

Ashish

Industrial gas price vs Wholesale gas price

2023-01-30T02:03:28.8130000

Hi Community admins and members, May I understand the key difference between industrial and wholesale gas price data published by MBIE? Also, what gas price typically applies to large end users/industrial end users? Is it wholesale or industry gas price? Thank you Best, Ashish

New report - carbon emissions from generation?

2022-09-27T03:41:24.4900000

Hi team,

I see EMS publishes total carbon emissions from generation, and average emissions per MWh every half hour. I would have thought this was something you could calculate and offer for free in a report, using some constant, generic emissions factors like those in GEM (Rankine gas/coal fuel switching makes things a bit trickier).

Is this something you've considered, or that is available somewhere already?

Thanks!

James

data availability for historic demand

2022-12-01T01:36:47.8230000

Hi there,

I have found the monthly historic pricing data for each island particularly useful - thanks. This is the link I was using :

https://www.emi.ea.govt.nz/Wholesale/Datasets/DispatchAndPricing/DispatchEnergyPrices/2022

I am after the demand data which matches the pricing data. Is that available in the datasets ?

thank you

Matt

Programmatic access to Wholesale Generation data

2022-08-11T23:34:02.4330000

Hi,

I'm trying to figure out how to access the wholesale generation by plant data through a python programmatic interface, but the link referring to python getting started appears to be broken on this page.

Any chance someone could post a simple example of how to access the data with python?

Cheers

Jeff

accumulated north island and south island data

2022-12-05T10:11:10.2170000

Hi there again,

Is there accumulated north and south island pricing data available in one file per month or day ?

If not, then what is the best way to generate this data from the datasets ?

New DIgSILENT PowerFactory case files now available

2022-11-03T03:04:36.3300000

The Power Systems Engineering team at Transpower have supplied updated PowerFactory case files. The updates are summarised in the 202210 PDF file.

Three wholesale market price APIs to be decommissioned on 21 October 2022

2022-09-20T20:19:30.5100000

Please be advised that three of the four Wholesale market price APIs are to be removed from service on 21 October 2022. Specifically, the three APIs to be decommissioned are:

Forecast NRSS prices
Forecast PRSS prices
Real-time prices.

The Real-time dispatch API and the ICP connection data v2 API will continue to operate just as they do today.

Users interested in obtaining wholesale market prices via an API can sign up to the WITS APIs at https://developer.electricityinfo.co.nz/WITS.

NZX is contracted by the Electricity Authority to be the Wholesale Information Trading System (WITS) manager. Earlier this year, the WITS manager stood up several APIs that make the EMI APIs somewhat redundant. Indeed, the only reason the EMI team at the Authority released its wholesale price APIs several years ago was because users were demanding such tools and none existed elsewhere. That is no longer the case.

The timing of this API decommissioning coincides with a programme of work we are currently undertaking to refactor our data ingestion processes to align with the system changes being introduced with the go-live of real-time pricing on 1 November 2021.

Generation output by plant

2022-07-20T08:37:11.3930000

Hi, I'm wondering when the Generation output by plant dataset for June will become available:

https://www.emi.ea.govt.nz/Wholesale/Datasets/Generation/Generation_MD

Wholesale price APIs to be decommissioned

2022-06-13T06:06:04.1770000

Hi all

This is a heads up that our wholesale market price APIs will soon be decommissioned. The WITS team have announced that they are going live with publicly available APIs - see announcement below.

We will take a good look at the WITS offering and make sure that everything we pump out via our APIs is available via the WITS API. If it is not, we will keep ours going. We will email all of our API subscribers and draw their attention to this announcement. We will give plenty of time for subscribers to our wholesale price APIs to transition over to WITS.

Announcement from WITS

All development, testing and UAT for the WITS API Project has been completed and the API has been deployed to the production environment. We would like to thank those who participated in the beta testing, we appreciate you taking a moment to provide feedback.

We’re now ready to share the API with the wider energy market. Participants and interested public parties can access the API here: https://developer.electricityinfo.co.nz/WITS

The public data that is available via this API includes data that can be found on the WITS website under market prices, energy quantities and reserve quantities. Information on how to call our APIs is available on the portal.

If you would like to receive a short user guide to navigate access to the API, require any support or have any suggestions for improvements please contact our WITS Support Service – wits@nzx.com or 0800 426 648. Please note: The API is currently only supported during business hours 8:30am-5pm.

Further API development will be planned for our future work programmes. We would like to hear what future API’s participants would find most useful, please email your suggestions to us.

Bids and offers published on EMI - file structure to be modified

2021-12-01T03:35:53.5500000

Please be advised that structure of the bids and offers files that we publish on EMI datasets is about to change.

The current structure will continue to be published in the folders called Bids and Offers, respectively, for a couple more weeks. The new structure is already available in the folders called BidsNew and OffersNew, respectively.

On 14 December 2021, the following will occur:

the folder currently called Bids will be renamed BidsOld
the folder currently called Offers will be renamed OffersOld
the folder currently called BidsNew will be renamed Bids
the folder currently called OffersNew will be renamed Offers

Then on 21 December 2021, the folders called BidsOld (i.e. currently called Bids) and OffersOld (i.e. currently called Offers) will stop being updated and will be be deleted.

In other words, users of the Bids and Offers data need to tweak their systems to accomodate the schema changes within the next two weeks.

This modification has been made as part of our data migration from a SQL Server instance to a Databricks-based Delta Lake, and to bring the schema nomenclature into line with that used

throughout our Delta Lake and other EMI datasets.

The old and new schemas can be seen in the attached file.

Constrained on/off files

2022-06-02T09:10:52.7670000

Hi,

Just checking if you're aware that the constained on/off amounts files have not been published since March (feb data)?

If you are aware, have they been deprecated and if not when do you expect them back?

Thanks

Changes in Tech Codes for Generation MD Files causing Automation Errors

2022-06-06T22:04:15.1370000

We're getting file validation errors when trying to process the generation md files.

Root cause looks to be changes made to the values in the tech_code column when the files were regenerated under the post relating to Turitea missing from Generation_MD CSV files.

Is it possible to regenerate the files again and set the tech codes back to the codes used in the rest of the datasets for that library for consistancy?

Tech_Code(New files) Tech_Code(Existing Files) Hydro Hydro Wind Wind Cogeneration Cogen Thermal Thrml Geothermal Geo

Turitea missing from Generation_MD CSV files

2022-05-25T02:58:49.4600000

The monthly half-hourly files are great (https://www.emi.ea.govt.nz/Wholesale/Datasets/Generation/Generation_MD/{yyyymm}_Generation_MD.csv) but Turitea wind farm is missing. Anybody know when this might be fixed, and if there is another way to extract generator metering info in the mean time?

Has Price Map been removed from EMI

2022-05-03T05:18:28.7630000

Has the heat map showing average spot prices across the country been removed as a report? I had it as a dashboard and seems to have disappeared and I can't find it now under the standard reports.

Generator names and unit codes

2019-02-13T04:13:43.8900000

Hi,

While looking at the datasets on the EMI website, I had some trouble reconciling the generator names in the “Generation Fleet” file with the four-character unit codes contained in the “Offer” files.

I assume there is a list of generators with their codes somewhere and if you could point me to that direction, it’d be very much appreciated.

Hai

Frequency keeping offers published on EMI datasets

2022-03-08T07:28:27.3200000

On Monday 14 March 2022 we will be deploying a new process to publish daily the frequency keeping offers and frequency keeping dispatched offers files. The files from the new process will first appear on 15 March for data pertaining to 14 March.

The structure of the files - column names, column order, data types, etc - will be identical to the current files, except for one minor aspect; in columns containing an alphanumeric data type, an empty cell will contain two double quotes whereas currently the quotes are not used.

For example, instead of appearing like this:

CTCT,1,11/02/2022,1,09/02/2022,00:10:33,08/02/2022,11:10:33,,,CLU,Y,5.00,175.00,668.00,74.00

CTCT,2,11/02/2022,1,09/02/2022,00:10:33,08/02/2022,11:10:33,,,CLU,Y,10.00,175.00,668.00,148.00

records will appear like this:

CTCT,1,11/02/2022,1,09/02/2022,00:10:33,08/02/2022,11:10:33,"","",CLU,Y,5.000,175.000,668.000,74.00

CTCT,2,11/02/2022,1,09/02/2022,00:10:33,08/02/2022,11:10:33,"","",CLU,Y,10.000,175.000,668.000,148.00

We trust this does not impact your data ingestion processes, or if it does, it's a straightforward fix.

We are making this change as part of our data migration from SQL databases to a Databricks Delta Lakehouse.

Monthly energy file for January 2022 incomplete

2022-03-10T05:36:26.6700000

Hello

A quick query, I noticed the monthly energy file for January 2022 is incomplete. It only goes up to 17th January.

202201_FinalEnergyPrices_incomplete.csv

Will this be replaced with a complete file? If yes, when will this happen?

Also, when will you be publishing a monthly file for February 2022?

Thanks,

Tim.

GDX file for March 28, 2019

2022-02-16T01:56:13.8630000

Hi,

There are three final pricing GDX files for March 28, 2019. FP_20190328a_F.gdx and FP_20190328_F.gdx are for trading period 1-25, and FP_20190328b_F.gdx is for trading period 26-48 but TPs are TP1-TP23. I wonder if a GDX file for all 48 trading periods, or a GDX file identical to FP_20190328b_F.gdx but TPs set to TP26-TP48 is made available.

Regards,

Ziming Guan

New API release – Wholesale real-time and forecast prices

2020-11-10T02:13:57.2770000

We have published a new API product called wholesale market prices. Subscribing to this product will enable users to receive a key to use one of four new APIs:

Forecast NRSS prices
Forecast PRSS prices
Real-time prices
Real-time dispatch

Each of these APIs provides a GET action that can be tested or accessed from our APIs page. A list of the returned fields and a brief description of each API is also provided on the APIs page, as are examples of the various ways the GET calls can be filtered.

Please note that the Real-time prices and Real-time dispatch APIs are new APIs and should not be considered revised versions of the existing EMI | Real-time prices and EMI | Real-time dispatch APIs, respectively. The EMI | Real-time prices and EMI | Real-time dispatch APIs will be decommissioned on 21 December 2020.

We understand that WITS will create APIs to disseminate price and other data at some future date. We have published these APIs now because the WITS APIs are still some time away and these four new wholesale price APIs will make the data available much sooner after it has been generated than is the case with the existing APIs. In addition to the reduced data latency, we also expect much improved reliability from the new APIs.

The database underlying these new APIs holds data for the most recent 30 days. If historical data is required, users can download it from our Forecast prices and Real-time prices EMI datasets.

Access to forecast prices and real-time or indicative prices via APIs will assist in enabling better informed decisions to be made. Users of real-time prices should be aware that these prices are not the final prices on which the market is settled. See the discussion here and the links therein for more information about wholesale prices.

Corrected prices - 2019 Undesirable Trading Situation

2021-09-09T04:58:28.2400000

An Undesirable Trading Situation (UTS) was alleged in late 2019. The UTS was upheld and the action to correct involved resetting prices for the period 3-27 December 2019.

The pricing manager recently published the corrected prices.

The correction entailed capping offers at $13.70/MWh for all trading periods during 3-27 December at the following nodes:

AVI2201 AVI0
BEN2202 BEN0
CYD2201 CYD0
MAN2201 MAN0
OHA2201 OHA0
OHB2201 OHB0
OHC2201 OHC0
ROX1101 ROX0
ROX2201 ROX0
WTK0111 WTK0

The attached spreadsheet contains the original and the reset final energy and reserve prices for the impacted days. EMI shows only the reset prices.

Expected generation to be commissioned data

2021-11-17T05:36:25.2630000

I am looking for a database that can tell what new projects have been comissioned or what new projects are in the planning to understand how much capacity can be expected by a specific time in future.

I have been looking at a couple of links but they dont seem updated.

https://www.windenergy.org.nz/proposed-wind-farms

Is there any other source I can use? Does EA maintain any database for expected capacity?

Publishing of wholesale energy and reserve prices

2021-11-11T00:52:40.2400000

We are making a couple of changes to the way we publish energy and reserve prices on EMI datasets.

Energy and reserve prices are currently published here on a monthly basis. Effective immediately, this folder will no longer be updated and it will soon be removed from EMI in its entirety.

Energy prices are now being published here and reserve prices here. In both cases the price files will be made available on a daily basis. The file names will also indicate the price status – provisional, interim or final.

Following the end of each calendar year, and once all prices for that year are no longer interim, the daily price files, both energy and reserves, will be accumulated into monthly files and moved into the respective ‘By month’ subfolders.

Users seeking to download prices for just a single node can make use of our new data report - just select the node of interest, specify a date range, and a CSV file available for download will be created.

December 2019 UTS - SPD case and GDX files

2021-10-10T23:54:55.5200000

An undesirable trading situation (UTS) was found to exist from 3-27 December 2019. Prices were declared to be final by the pricing manager before this UTS was resolved and the resolution led to final prices being reset. This has had implications for the SPD case and GDX files that we publish.

SPD case files

For each of the days from 3-27 December 2019, we have published two SPD case files that are associated with final prices whereas we usually only publish one. The case file associated with the pre-UTS final prices is published with the name as per the usual file naming procedure. The second, post-UTS, case file has the last three digits of the case ID replaced with 999. For example, the original SPD case file associated with 20 December 2019 is called MSS_191112019121100791_0X.zip whereas the post-UTS case file is called MSS_191112019121100999_0X.zip. Note that the day portion of the SPD case file name refers to the UTC day.

GDX files

Similarly, the GDX file associated with the original final prices is named as per the usual process. The second or post-UTS GDX file has a UTS suffix added to the file name. For example, the original GDX file associated with 20 December 2019 is called FP_20191220_F.gdx whereas the post-UTS GDX file is called FP_20191220_F_UTS.gdx.

Real-time prices API no data daily from 00:00 through 01:00

2021-10-02T11:40:47.9200000

Hi there, I have just noticed my curl based https://emi.azure-api.net/real-time-prices/ requests come back empty from midnight to 1am daily.

Tested separately using the https://emi.portal.azure-api.net/docs/services API page with my API key entered / no filter applied and get the same emtpy result:

Request URL

https://emi.azure-api.net/real-time-prices/

HTTP request

GET https://emi.azure-api.net/real-time-prices/ HTTP/1.1
Host: emi.azure-api.net
Ocp-Apim-Subscription-Key: ••

Response status

200 OK

Response latency

51 ms

Response content

Pragma: no-cache
Arr-Disable-Session-Affinity: True
X-Content-Type-Options: nosniff
X-Frame-Options: deny
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-XSS-Protection: 1; mode=block
Content-Security-Policy: script-src 'self'
Cache-Control: no-store
Date: Sat, 02 Oct 2021 11:28:19 GMT
Content-Length: 2
Content-Type: application/json
Expires: -1

[]

Missing Unit Level Generation Data - 202009

2021-09-27T21:53:01.9430000

Hi,

In Unit Level Generation data for 202009, it seems that a number of generators (list below) were not operating - Is this correct?

Generation: Huntly, Rangipo, Tekapo B and Tokaanu

Cross checking against the Generation_MD data for that month, they all appear to be generating.

Cheers, Luke

Reconciled Demand and Generation Reports

2020-09-20T20:54:46.1130000

Re: Reconciled demand and generation reports

Reconciled demand and generation data is our most complete source of data and refers to all purchases and sales on the wholesale market that are cleared through the clearing manager. This data becomes available around the middle of the following month. More specifically, reconciled demand and generation refers to loss-adjusted purchases and sales, and represents the purchase and sale quantities upon which money changes hands between participants and the clearing manager. The loss-adjustment means that the actual consumption data submitted to the reconciliation manager by retailers and other purchasers is grossed up to account for losses in the distribution networks.

is this data just month0 version or does it get updated over time as say washup files get loaded ?

Thanks in advance ....

Generation data

2021-06-11T05:22:07.5030000

Can anyone please walk me through how can I access the generation data such as wind, hydro and thermal etc on a daily resolution.

If generation mix is not available, can i have access to daily generation from individual power stations and than I can map them accordingly.

Thanks for your help

Cheers

Sara

Decomposition of spot price into underlying components

2019-12-15T22:22:37.5070000

Hello EMI guys,

In some other jurisdictions spot prices are presented in 3 components - the underlying spot price from generator offer, then the losses, and then the congestion elements. Are we able to do that here?

Thanks

Lana

EMI dataset update – New DIgSILENT PowerFactory case files now avaliable

2021-05-03T01:51:27.0530000

The Power Systems Engineering team at Transpower have supplied updated PowerFactory case files. The updates are summarised in the 202105 PDF file.

EMI dataset changes – Three wholesale datasets get a makeover

2021-04-07T04:02:25.2000000

Three of our wholesale datasets have been revamped and published in a new location:

Binding constraints are currently published here but can now be found here.
Cleared offers are currently published here but can now be found here.
Load/Generation/Price files are currently published here but can now be found here.

In all three cases, the contents and structure of the newly revamped files is explained on their respective pages.

The files containing binding constraints are now published daily and contain near-binding constraints as well as binding constraints. The Load/Generation/Price files have been renamed NodalPricesAndVolumes.

The legacy versions of these three datasets will cease being published in their current locations on 27 April 2021. At some point in the future we will backfill the new locations with a complete time series of files formulated as per the new structure. In the meantime, we have simply dumped all of the legacy files in a folder within each of the new locations.

The reason for making this change is to provide more useful information and to make the publication process more reliable.

Wholesale data - dataset definitions

2021-03-31T22:58:39.5530000

Hi,

Is there are document or file anywhere describing the definitions and schema of EMI's wholesale datasets? Data types, uniqueness of rows etc. I'm trying to import some data into a database and this would be very helpful.

Cheers,

Tom

Interconnect Loss Factors

2021-03-26T22:45:32.9670000

Recently been looking into the reconciliation of volume between networks with interconnection NSPs. Are the loss factors available for each interconnect NSP? It would be helpful for traders developing pricing assumptions to know their exposure to interconnect losses so that accurate pricing assumptions can be maintained.

It would also be good to have interconnect NSPVOLS (AV130) data published to support this.

vSPD-online: Getting started and fundamentals

2016-05-18T00:17:07.2930000

vSPD-online is a web-based implementation of the Authority’s vectorised Scheduling, Pricing and Dispatch (vSPD) model.

Unlike the standalone vSPD, users do not require a GAMS license to operate vSPD-online. Behind the scenes, vSPD-online employs exactly the same model codes and solution algorithms as the standalone vSPD, and it calls upon the same collection of input data files. In other words, vSPD-online is mathematically identical to standalone vSPD.

However, the data inputs that vSPD-online users are able to modify are restricted compared to standalone vSPD. Initially, only the demand parameters can be changed. Once users have gained a little familiarity with vSPD-online, we will enable the various offer parameters to be modified as well.

Registration

Users must first register in order to use vSPD-online. A single sign-on facility enables access to all parts of the EMI website that require sign-on. This is a one-time task and requires users to provide a username, an email address, and an affiliation. In the interests of openness and transparency, we would encourage users to use their actual first and last names as their username, and current workplace for affiliation. You can edit your user profile details at any time after you've registered.

vSPD-online concepts

There are really only two actions users need to undertake in order to use vSPD-online:

- Create an override

- Create a job.

Create an override

An override is a named collection of user-specified data values that defines an experiment, or counterfactual scenario. It is called an override because the specified data values literally 'override' the existing or base case values in the model. In other words, creating an override is the mechanism by which a vSPD-online user implements a ‘what if’ question, e.g. what if North Island demand increased by 10%?

An override may contain one or more components. For example, one component may be to increase North Island demand by 10% in all trading periods of the day whereas a second component might decrease South Island demand by 3% in trading periods 30-36. Users add components one at a time until they’ve finished building the override, and then they submit it. After an override has been submitted it is stored in the system and is then available for all vSPD-online users to make use of.

Three ways to modify input data

When specifying how the base case input data is to be modified, three methods are available:

- Scale – scale the existing base case data by some scalar, e.g. 0.95 to reduce by 5% or 1.1 to increase by 10%.

- Increment – increase or decrease the existing base case data by some specified amount, e.g. 7.3 to increase demand by 7.3MW or -5 to decrease demand by 5MW.

- Replace – replace the existing base case data with a new value.

Three ways to create an override component

Three approaches to adding a new component to an override are available:

- Create a new component from scratch.

- Use an existing override as a starting point and edit it to create new override components for the current override.

- Upload the required data from a CSV or an Excel file – this first requires first downloading an override component so that a file template is available for editing. An opportunity to download an override component as a CSV or an Excel file exists during the process of adding components to an override.

Create a job

Activating the 'create a job' function causes the vSPD-online user to be stepped through the process of configuring an instance of the vSPD model to be solved.

The job must be given a name and description – users should try to make these as meaningful as possible, as the name and description will appear in the vSPD dashboard for all to see. If an override is to be applied, then the relevant override must be selected.

Solving vSPD without using an override simply causes the base case for the selected days and trading periods to be solved. In other words, the prices, dispatch, branch flows etc that actually occurred in the final pricing run of SPD for the day and trading periods selected will be reproduced. It is reasonable to do this if you want to compare the base case solution with one or more counterfactual solutions.

vSPD-online users are restricted to solving no more than seven contiguous days in one job. Within that 7-day interval, users may select any or all of the trading periods to be solved on any or all of the days.

Once the job has been submitted, it will appear as a record in the vSPD dashboard. When the job is finished, the user will receive an email containing a link to the vSPD output files, which can then be downloaded. Any other user can download the output files as well, directly from the vSPD dashboard.

EMI real-time data: 401 return code

2021-02-05T05:32:56.5730000

Hi all,

Starting from this afternoon at around 16:50, I've been getting "401" status codes when trying to use the EMI real-time data API endpoint.

This is the exact returned value:

{ "statusCode": 401, "message": "Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription." }

I've successfully been using this API endpoint, with my subscription key, since the middle of last year.

The Profile page's Subscriptions section (https://emi.portal.azure-api.net/developer) indicates the subscription is active.

I've tried both Primary and Secondary key, with the same result.

I've also tried refreshing a key, with the same result.

For reference, here is the API in question:

https://emi.portal.azure-api.net/docs/services/5f98fa890cf73b31bad09e10/operations/5f98fa8b243aa88e0dbe9741

I realise there have been some policy changes to the ICP API endpoint (as per this discussion: https://forum.emi.ea.govt.nz/thread/api-management-policy-change-icp-connection-data-api/ ), but the message described there (essentially throttling call rates ) is different to the return code and message I'm experiencing (access denied due to invalid key).

Is there an API change that I'm not aware of?

Has anyone else been experiencing the same 401 issue?

Is this a known issue, and is there an eta on resolution?

Many thanks and kind regards,

Duncan.

OTA22002 Spot Data missing from 15th Jan 2021 to 17th Jan 2021

2021-01-31T21:43:50.2370000

Hi, Spot data appears to be missing from 15th Jan 21 to 17th Jan 21.

Thank You

Wholesale price trends

2021-01-25T13:03:51.3100000

Hi,

Is there a specific reason why the wholesale price trends data has not been updated since Jan 19th?

Thanks,

Mathieu

Historical generation (grid import) data before August 1997

2020-07-09T02:40:29.8100000

Hi there,

Is it possible to get earlier data on generation (grid import) before August 1997?

I've looked at the following.

https://www.emi.ea.govt.nz/Wholesale/Datasets/Generation/Generation_MD

https://www.emi.ea.govt.nz/Wholesale/Datasets/Metered_data/Grid_import

These data sets are great, thank you for all the work you do.

Thanks

Morgan

Final pricing SPD case and GDX files - heads up re: forthcoming changes

2020-10-22T22:32:25.6100000

We are in the midst of modifying the GDX creation process as well as the process for publishing both final pricing GDX and SPD case files to EMI datasets. The following locations are where case files and GDX files are being published via the new process:

https://www.emi.ea.govt.nz/Wholesale/Datasets/FinalPricing/CaseFiles_NEW
https://www.emi.ea.govt.nz/Wholesale/Datasets/FinalPricing/GDX_NEW

There is no need for users of either SPD case files or GDX files to do anything just yet.

Once we have finished implementing and testing the new processes, we will announce the date on which the current processes will be terminated. Plenty of time will be allowed for users to modify scripts and automated processes used to obtain GDX and case files. But if this is going to affect you, you might want to start thinking about it now.

On the yet-to-be announced day that we turn off the current process, two things will happen:

the contents of ../FinalPricing/CaseFiles will be moved into ../FinalPricing/CaseFiles_NEW, ../FinalPricing/CaseFiles will be deleted, and ../FinalPricing/CaseFiles_NEW will be renamed ../FinalPricing/CaseFiles
the contents of ../FinalPricing/GDX will be moved into ../FinalPricing/GDX_NEW, ../FinalPricing/GDX will be deleted, and ../FinalPricing/GDX_NEW will be renamed ../FinalPricing/GDX.

The GDX file naming convention has been modified relative to what's being done at present. As can be seen from time to time in ../FinalPricing/GDX_NEW/2020, newly published GDX files will initially have a name something like: FP_20201021_201112020101100806_20201022074928.gdx. This file name is made up of three components:

the trading date to which the GDX file pertains, e.g. 20201021 in the example above
the SPD case ID from which the GDX file was created
the run date and time at which the case file was created, e.g. 07 hrs, 49 mins and 28 secs on 22 Oct 2020 in the example above.

Once we learn the price type associated with the SPD case file and the commensurate GDX file, i.e. provisional or interim, the _P or _I suffix will be added. Eventually prices will go final and the _F suffix will be added. At that time, the GDX file will be named as described here and all other GDX files pertaining to that day will be deleted, i.e. once final prices have been declared and published, there will only be a single GDX file available for that day from EMI datasets.

All of the steps in the new process are driven by event triggers in the Azure environment so in addition to a general reliability improvement, we expect the new process to reduce the time it takes to make GDX and case files available.