ifference between revisions of "EMO:Reserves"
Jump to navigation
Jump to search
(3 intermediate revisions by 2 users not shown) | |||
Line 3: | Line 3: | ||
The inputs to the SPD solver are shown in the figure and table below (adapted from Transpower's Reserve Management Tool (RMT) functional specification). There are two broad categories of input: | The inputs to the SPD solver are shown in the figure and table below (adapted from Transpower's Reserve Management Tool (RMT) functional specification). There are two broad categories of input: | ||
#Energy and reserve offers from market participants | #Energy and reserve offers from market participants | ||
− | #Parameters that define the Reserves requirement are calculated mostly by | + | #Parameters that define the Reserves requirement are calculated mostly by the RMT software application. |
[[File:Reserves.PNG]] | [[File:Reserves.PNG]] | ||
Line 108: | Line 108: | ||
| | | | ||
:Calculated by RMT. Quantifies the maximum transient overload power that the HVDC link can transfer at the inverter after a Contingent Event, not taking any AC constraints into account. | :Calculated by RMT. Quantifies the maximum transient overload power that the HVDC link can transfer at the inverter after a Contingent Event, not taking any AC constraints into account. | ||
+ | |- | ||
+ | | | ||
+ | :''Halfpole Rampupmax'' | ||
+ | | | ||
+ | :Calculated by RMT. Quantifies the maximum transient overload power that the HVDC halfpoles can transfer at the inverter after a Contingent Event, not taking any AC constraints into account. | ||
+ | |- | ||
+ | | | ||
+ | :''Manual Risk'' | ||
+ | | | ||
+ | :Manually Entered Min. A fixed risk that cannot be optimised by the SPD solver. | ||
+ | |- | ||
+ | | | ||
+ | :''Clearing Price at Nodes'' | ||
+ | | | ||
+ | :Nodal Price | ||
+ | |- | ||
+ | | | ||
+ | :''Cleared Load'' | ||
+ | | | ||
+ | :Load that will be connected at a cleared price | ||
+ | |- | ||
+ | | | ||
+ | :''Rampup'' | ||
+ | | | ||
+ | :Internally calculated by SPD. Quantifies the steady state power that the HVDC link can transfer after a Contingent Event, taking Benmore bus constraints into account | ||
+ | |- | ||
+ | | | ||
+ | :''BEN P1ANMax'' | ||
+ | | | ||
+ | :The maximum MW north transfer on Benmore Pole 1A | ||
+ | |- | ||
+ | | | ||
+ | :''BEN P1BNMax'' | ||
+ | | | ||
+ | :The maximum MW north transfer on Benmore Pole 1B | ||
+ | |- | ||
+ | | | ||
+ | :''BEN P1ASMax'' | ||
+ | | | ||
+ | :The maximum MW south transfer on Benmore Pole 1A | ||
+ | |- | ||
+ | | | ||
+ | :''BEN P1BSMax'' | ||
+ | | | ||
+ | :The maximum MW south transfer on Benmore Pole 1B | ||
+ | |- | ||
+ | | | ||
+ | :''Cleared Reserve'' | ||
+ | | | ||
+ | :Reserves that will be connected at a cleared price | ||
+ | |- | ||
+ | | | ||
+ | :''Cleared Generation'' | ||
+ | | | ||
+ | :Generation that will be connected at a cleared price | ||
+ | |- | ||
+ | | | ||
+ | :''HVDC Bipole Transfer'' | ||
+ | | | ||
+ | :The MW transfer of the HVDC link | ||
+ | |- | ||
+ | | | ||
+ | :''HVDC Branch Limits'' | ||
+ | | | ||
+ | :Limits in the transfer on each HVDC pole and halfpole. May be reduced due to outages of equipment etc | ||
+ | |} | ||
+ | |||
+ | === Relationship between ''EMarketOffer'' and RMT === | ||
+ | ''EMarketOffer'' does not reproduce RMT functionality and must be provided with the RMT generated parameters to be used for final dispatch. The inputs required by ''EMarketOffer'' to model reserves appear in the table below. | ||
+ | |||
+ | {|class="wikitable" | ||
+ | ! Input Group !! Item !! Description | ||
+ | |- | ||
+ | ! rowspan="2" | Energy Offers | ||
+ | | | ||
+ | :''Price (bands 1-5)'' | ||
+ | | | ||
+ | :Offer Price in bands 1 to 5 for the Units | ||
+ | |- | ||
+ | | | ||
+ | :''Quantity (bands 1-5)'' | ||
+ | | | ||
+ | :Offer Quantity in bands 1 to 5 for the Units (always zero for Powerflow Case Data Sources) | ||
+ | |- | ||
+ | ! rowspan="3" | Reserves Offers | ||
+ | | | ||
+ | :''Price: PLSR/TWD/ILR (bands 1-3)'' | ||
+ | | | ||
+ | :Price offered by Reserve type for the Unit in bands 1 to 3 for the Unit | ||
+ | |- | ||
+ | | | ||
+ | :''Quantity PLSR/TWD/ILR (bands 1-3)'' | ||
+ | | | ||
+ | :Quantity offered by Reserve type for the Unit in bands 1 to 3 for the Unit | ||
+ | |- | ||
+ | | | ||
+ | :''Slope: PLSR (bands 1-3)'' | ||
+ | | | ||
+ | :Unit slope to be used for PLSR offers made by the Unit in bands 1 to 3 | ||
+ | |- | ||
+ | ! rowspan="9" | Reserves Settings | ||
+ | | | ||
+ | :''Reserve Region'' | ||
+ | | | ||
+ | :North/South Island | ||
+ | |- | ||
+ | | | ||
+ | :''DC Offset FR'' | ||
+ | | | ||
+ | :HVDC Fast Reserve Risk Offset | ||
+ | |- | ||
+ | | | ||
+ | :''DC Offset SR'' | ||
+ | | | ||
+ | :HVDC Sustained Reserve Risk Offset | ||
+ | |- | ||
+ | | | ||
+ | :''AC Offset FR'' | ||
+ | | | ||
+ | :AC Fast Reserve Risk Offset | ||
+ | |- | ||
+ | | | ||
+ | :''AC Offset SR'' | ||
+ | | | ||
+ | :AC Sustained Reserve Risk Offset | ||
+ | |- | ||
+ | | | ||
+ | :''Base Risk FR'' | ||
+ | | | ||
+ | :Fast Reserve Base Risk (Manual Risk) | ||
+ | |- | ||
+ | | | ||
+ | :''Base Risk SR'' | ||
+ | | | ||
+ | :Sustained Reserve Base Risk (Manual Risk) | ||
+ | |- | ||
+ | | | ||
+ | :''RAF FR'' | ||
+ | | | ||
+ | :Fast Reserve Risk Adjustment Factor | ||
+ | |- | ||
+ | | | ||
+ | :''RAF SR'' | ||
+ | | | ||
+ | :Sustained Reserve Risk Adjustment Factor | ||
+ | |} | ||
+ | |||
+ | NOTE: Some of the Reserve requirement data, particularly the AC Offsets, are not published in the data generally available to market participants. You will need to either estimate the value of these input data or obtain examples on request from the system operator. | ||
+ | |||
+ | |||
+ | [[Main Page|Home]] |
Latest revision as of 15:30, 12 February 2014
The Reserve Management Tool
The inputs to the SPD solver are shown in the figure and table below (adapted from Transpower's Reserve Management Tool (RMT) functional specification). There are two broad categories of input:
- Energy and reserve offers from market participants
- Parameters that define the Reserves requirement are calculated mostly by the RMT software application.
Term | Explanation |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Relationship between EMarketOffer and RMT
EMarketOffer does not reproduce RMT functionality and must be provided with the RMT generated parameters to be used for final dispatch. The inputs required by EMarketOffer to model reserves appear in the table below.
Input Group | Item | Description |
---|---|---|
Energy Offers |
|
|
|
| |
Reserves Offers |
|
|
|
| |
|
| |
Reserves Settings |
|
|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
NOTE: Some of the Reserve requirement data, particularly the AC Offsets, are not published in the data generally available to market participants. You will need to either estimate the value of these input data or obtain examples on request from the system operator.