120 Views

Download Presentation
##### The EA’s 2-Hub FTR Market

**An Image/Link below is provided (as is) to download presentation**

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -

**The EA’s 2-Hub FTR Market**Roger Miller and Grant Read Presented to EPOC 2011 by Roger Miller**Disclaimer**• The Authority has just started an RFP process for the FTR manager, which runs till 31st October • RFP is on www.gets.govt.nz • Running a fair, open, competitive tender process • Information must be given to all potential bidders • My presentation will be placed on the Authority’s website • Any relevant Q & A’s will be posted on GETS • Specific questions can be emailed to tenders@ea.govt.nz • Any discrepancy with tender documents or Code amendment - those documents take precedence NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Overview**Hubs versus nodes Why use hubs and how do they work? “All inclusive” FTRs Why use full price difference vs loss exclusive definition Option vs Obligation FTRs Why we need options in a “tidal flow” situation Simplified Grid Model for 2 hub FTR Partitioning the Rental Pool for 2 hub FTR Appendix - Loss and Reserve Issues (if time?) NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**1. Hubs versus nodesWhy use hubs and how do they work?**NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Hubs**• Hubs are a grouping of one or more nodes • Nodes within a hub may have specified weights • Settled on the weighted average nodal price • FTR hub injections split into component nodal injections for feasibility testing and rental calculation • Trading between a few major hubs reduces market power concerns • Initial FTR “hubs” aligned with ASX futures reference nodes – BEN2201 and OTA2201 • May need to “expand” hubs slightly to handle flows NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**2. “All inclusive” FTRsWhy use full price difference vs**loss exclusive definition? NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**BEN-OTA Monthly Price Components**NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**BEN-OTA Monthly Loss Factors**Wet/North Flow Dry/South Flow NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**“All inclusive” FTRsWhy use full price difference vs**loss exclusive definition? Losses account for a large part of the price differential (especially during HVDC South Flow) Size and direction of loss price differential depends on generation pattern (unpredictable) Integrates with futures platform (ASX) better Simpler for participants to understand and value NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**3. Option vs Obligation FTRsWhy we need options in a**“tidal flow” situation NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Obligations - What are they?**Payout Payout • Pure swap • Positive or negative value • Symmetrical • Linear • Simple optimisation problem • Pure swap • Positive or negative value • Symmetrical • Linear • Simple optimisation problem Holder receives payment Holder receives payment Price Difference Price Difference Holder must pay Holder must pay NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012. NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Options - What are they?**Payout • Asymmetrical • Non-negative value • Non-Linear • More complex optimisation problem Holder receives payment Price Difference No requirement for holder to pay NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Why we need option FTRs**Direction of transmission flows depends on generation pattern (unpredictable) Direction of price differentials depends on direction of transmission flows Inter-island HVDC flow direction particularly important in NZ Depends on (SI) hydro inflows (seasonal pattern but unpredictable from year to year) (“Tidal Flow”) Less important for regions with little generation (e.g. Upper SI, Auckland? – flow always northward) NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Examples**Short/Importing Long/Exporting Price N-S Option S-N Option NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Exercise patterns**• Number of exercise patterns = number of permutations of hub orderings by price = n! (assuming options between all hubs, which may not be necessary) • For 2 hubs there are just 2 patterns: S-N, N-S NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Ob/Op Constraints**• S-N Op + S-N Ob – N-S Ob ≤ S-N Capacity • N-S Op + N-S Ob – S-N Ob ≤ N-S Capacity NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Obligation/Option relationship**Payout S-N Obligation S-N Option • PS-N Ob = PS-N Op – PN-S Op • PN-S Ob = PN-S Op – PS-N Op • PS-N Ob = – PN-S Ob Price Difference Applies to: • Auction clearing prices • Payouts • Ex-post scaling may distort these relationships -ve N-S Option NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**4. Simplified Grid Model for 2 hub FTR**NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Simplified Grid ModelFor 2 hubs**• Traditional approach is to ensure FTRs are simultaneously feasible on forecast FTR grid • For 2 hubs FTRs add or subtract algebraically • Establish a maximum flow in each direction • FTR grid reduces to a 2 node + 1 line model Ben-Ota Max Benmore Otahuhu Ota-Ben Max NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**5. Partitioning the rental poolFlow based decomposition for**2 hubs NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Motivation**• Ring fence intra-island rents for a possible future intra-island locational price risk solution • Not yet decided what this should be (if anything) • Avoid cross subsiding the inter-island FTR • Maintain consistent inter-island FTR rental stream if future FTRs hubs or some other intra-island solution are implemented NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Different approach used for:**• HVDC rents • AC rents HVDC - just collect all rent between Benmore and Haywards HVDC terminals = PricereceivedFlowreceived – PricesentFlowsent NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Approach for AC system rents**• Rents are generated by branch capacities, loss tranche limits, branch (“equation”) constraints, mixed constraints (if any) • Rent generated by constraint c = σcRHScwhereσc is the constraint shadow price • For each constraint we need to collect rent of σcAssignedCapacitycwhereAssignedCapacityc is the maximum LHS constraint loading implied by any feasible FTR flow pattern • Note that if the FTR flow pattern is feasible then AssignedCapacityc≤ RHScfor all c • For 2 hubs only need to consider 2 extreme flow patterns: BEN-OTA Max; and OTA-BEN Max NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**Allowing for differences between the FTR Grid and the “On**the Day” grid • Extreme injection patterns based on an over-estimated grid (no outages, no contingencies) • Use shift factors to deduce branch/constraint loadings on the “On the Day” grid for each extreme injection pattern • Shift factors avoid having to solve a full load flow for each injection pattern for each trading period • Still collect rent on constraints in series with “On the Day” bottlenecks • Simplified by using lossless shift factors and lossless injection patterns NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**FTR Injection Patterns**• Feasible flow pattern is unbalanced (lossy) • Approximate by a balanced (lossless) pattern • Lossless flow ≥ Lossy flow on each branch (over estimate) Balanced flow approximation Positive injection at source Negative injection at sink Unbalanced flows reduce progressively from source to sink due to losses leaking out at the end of each branch FTR source FTR flow FTR sink NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.**SPD uses a piece-wise linear loss approximation**LFj is loss factor of the jth tranche LFmarg is loss factor of the marginal tranche Capj is capacity of the jth tranche AssCapj is assigned capacity of the jth tranche Pr is price at scheduled flow receiving end node SPj is shadow price of the jth tranche = Pr (LFmarg - LFj) Loss Rentals Marginal Loss Factorx spot price Loss rent collected Pr LFmarg Pr LFmarg SP2 Pr LF2 SP1 Ass Cap2 Pr LF1 AssCap1 Cap1 Cap2 branch flow Assigned Branch Capacity Actual Flow NB: This presentation relates to the approved FTR Code Amendment, which comes into force on 1 Oct 2011. It is currently intended to be implemented from Oct 2012.