Ed Skiba BpsCochairs Parallel Flow Visualization Overview 1 OVERVIEW Parallel Flow Visualization PFV Status Background Objectives NAESB Responsibility IDC Input Recommendation Scope Proposed Solution ID: 1030115
Download Presentation The PPT/PDF document "February 27, 2013 BY NARINDER K SAINI" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
1. February 27, 2013BYNARINDER K SAINIEd SkibaBps-Co-chairsParallel Flow VisualizationOverview1
2. OVERVIEWParallel Flow Visualization (PFV) StatusBackgroundObjectivesNAESB ResponsibilityIDC InputRecommendation ScopeProposed Solution Additional DocumentsNext Steps2
3. Background: IRO-006IRO-006 Transmission Loading ReliefEach Reliability Coordinator and Balancing Authority that receives a request pursuant to an Interconnection-wide transmission loading relief procedure (such as Eastern Interconnection TLR, WECC Unscheduled Flow Mitigation, or congestion management procedures from the ERCOT Protocols) from any Reliability Coordinator, Balancing Authority, or Transmission Operator in another Interconnection to curtail an Interchange Transaction that crosses an Interconnection boundary shall comply with the request, unless it provides a reliability reason to the requestor why it cannot comply with the request.3
4. Background: Interconnections4IRO-006-WECC Qualified Transfer Path Unscheduled Flow Relief (WECC)IRO-006-TRE IROL & SOL Mitigation in the ERCOT RegionIRO-006-EAST Transmission Loading Relief Procedures for the Eastern InterconnectionWEQ-008 Transmission Loading Relief (TLR) – Eastern Interconnection Tools – (IDC)Interchange Distribution Calculator (SDX )System Data eXchange
5. Background: Primary Players5IDCSDX
6. ObjectivesGeneration to load (GTL) impacts reported to the IDC on a real-time basis More accurate assignment of relief obligations to entities causing congestionNear real-time data using generator output provided by RC Include impacts of intra-BA generation-to-load and point-to-point transactionsDifferentiate between intra-BA firm and non-firm transmission serviceIDC has better data to perform calculations for TLR Levels 3 and 56
7. NAESB RESPONSIBILITYNAESB will establish methodology for assigning the generation to load flows into the appropriate buckets.7
8. IDC Input8Inter-BANetworkInterchangeCurrent IDCInter-BAPoint-to-PointInterchangeCurrent IDCIntra-BANetworkNAESBParallel Flow VisualizationIntra-BAPoint-to-PointNERCS‐ Ref 10132** http://www.nerc.com/docs/standards/sar/All_Directives_Report_2012-04-05.pdf
9. Recommendation ScopeDraft Standards Address Annual Plan Items:1.a Parallel Flow Visualization/Mitigation for Reliability Coordinators in the Eastern Interconnection – Permanent Solution1.b Perform consistency review of WEQ-008 Transmission Loading Relief Business Practice Standards and develop recommendation1.d Revise TLR level 5 to be treated similarly to TLR Level 3 in terms of treating the next hour allocation separately from that of current hour. (R11020)9
10. Proposed SolutionDraft Standards include:Transmission Loading Relief Process (WEQ-008)OASIS PostingsDefinitions (WEQ-000 and conforming changes)10
11. TLR Business Practice StandardsTransmission Loading Relief – WEQ-008Two Methods*Tag Secondary Network Transmission Service, orGenerator PrioritizationCoordination ArrangementsTwo-Tier Firm CurtailmentCredit for RedispatchDynamic Schedules/Pseudo-TiesSub-priorities Deletions*Assumes that all point-to-point transactions are tagged under NERC standards11
12. Methods for Intra-BA TransactionsTag Secondary Network Transmission Service Method A method used to submit to the IDC Transmission Service curtailment priority of the Secondary Network Transmission Service using e-Tags. Generator Prioritization MethodA method used to submit to the IDC Transmission Service curtailment priority of the generator output. Difference between what is reported and the real-time generator output is firm12
13. Methods for Intra-BA Transactions (cont.)Balancing Authority to choose either one but not both Methods Balancing Authority can switchSix month noticeLSE (or entity acting on their behalf) entersTags for Tag Secondary Network Transmission Service Method Generator Priority Schedules for Generator Prioritization MethodTransactions or generation-to-load impacting 5% or greater considered for assigning relief obligations13
14. Coordination ArrangementsCoordination Arrangements TypesCoordination AgreementsAn agreement between two or more Transmission Service Providers for coordination of: a) granting Transmission Service by honoring a set of Flowgate limits and b) managing real-time congestion through congestion management process. Unilateral Declarations allowed if Transmission Service Providers cannot agreeReciprocityA commitment by two Transmission Service Providers to provide Last-to-Curtail treatment of parallel flows on one another’s system without having a direct Coordination Agreement. Two-Tier Firm Curtailments – encourages Coordination Arrangements14
15. Two-Tier Firm CurtailmentTwo-Tier Firm CurtailmentFirst-to-CurtailThe Firm Transmission Service curtailment priority assigned by the IDC to parallel flows due to a lack of Coordination Agreement, Reciprocity, or unilateral declaration. Last-to-CurtailThe Firm Transmission Service curtailment priority assigned by the IDC to: a) on-path flows and b) parallel flows when a Coordination Agreement, Reciprocity, or unilateral declaration exists between the Transmission Service Provider experiencing congestion and (at least one of) the Transmission Service Provider(s) on the path of the transaction whose Transmission Service is contributing to the congestion.15
16. PFV: First-to Curtail/Last-to-CurtailTSP with Coordination Arrangements16 Last to Curtail TSPsSOCOTVADUKPJMMISOSPPEESCONGESTIONSOCOX X XTVA X XXX DUKX XX PJM XXXX MISO X XXX SPP X XXXEESX XXCongested TSP: TVA Last to Curtail if tag has TVA, PJM, MISO or SPP on pathCongested TSP: PJM Last to Curtail if tag has TVA, DUK, PJM or MISO on pathCongested TSP: SPP Last to Curtail if tag has TVA, MISO, SPP or EES on path
17. Credit for RedispatchUnder TLR level 3 and higher a BA may redispatch its system to meet the target GTL flow, which is the difference between the net GTL flow (net of the forward and reverse impacts) and the IDC calculated relief obligation. Meeting the target GTL flow may be accomplished by redispatching any generation that may either reduce forward flows or increase reverse flows. The IDC will determine if a Credit for the Redispatch was accomplished from the start of the redispatch time. If so, the Credit for Redispatch will be applied to the next hour relief obligation calculation by the IDC and will not result in a double counting of non-firm impacts. 17
18. Dynamic Schedules and Pseudo-TiesIf a transaction is identified as a Dynamic Schedule or a Pseudo-Tie: During TLR level 3 or higher the impact of this transaction will be determined on a pro-rata basis along with all other transactions and based on the transmission service priorities.The impact will be assigned as relief obligations to the Sink BA in lieu of curtailing the transaction.This transaction will not be subject to holding on any TLR level.18
19. Sub-prioritiesSub-priorities extended to TLR Level 5aS1 - GTL shortfall assigned to S4 will reduce the S1 amount in the same or higher curtailment categories, not to be reduced below zero. For S1, the GTL exceedance assigned to S4 will increase the S1 amount in higher curtailment categories, not to exceed their original amount prior to redispatch steps taken by the BA.S2 – Addresses Intra-BA Transactions, excluding GTL FlowsS3 – GTL flows are set to zeroS4 - GTL shortfalls or exceedances from relief obligations two hours prior shall be assigned to S4. A shortfall will be assigned to S4 of the same curtailment category that received the relief obligation. An exceedance will be assigned to S4 of the lowest curtailment category.19
20. Deletions in WEQ-008WEQ-008-1.1 and WEQ-008-1.2 (inconsistent with IRO-006-EAST and potential conflict)WEQ-008-1.3 (PFV eliminates need for special requirements for markets)WEQ-008-1.5 (double jeopardy with NERC Standards)WEQ-008-3.11 (PFV eliminates need for section)Appendix B (related to WEQ-008-3.11)Appendix C (appropriate to be moved to IDC Users Manual)20
21. OASIS Postings OASIS ChangesScheduleDetail template modified to identify firm tagged curtailments as First-to-Curtail or Last-to-Curtail. (CURTAILMENT_ORDER data element in WEQ-002, -003, and -013)Posting of Unilateral Declarations - WEQ-001-13.1.5If the BA declares the Generator Prioritization Method, the Transmission Service Provider (s) within the BAA shall specify the methodology for establishing the Transmission Service firmness of Generator Priority Schedules in its Business Practices that are posted in accordance with Business Practice Standard WEQ-001-13.1.4.21
22. DefinitionsNewIntra-BA TransactionGenerator Prioritization Method and Tag Secondary Network Transmission Service MethodGenerator Priority SchedulesCoordination Agreement and ReciprocityFirst-to-Curtail and Last-to-CurtailCredit for RedispatchTransmission Loading Relief Transaction DeadlineRemoveCurtailment 22
23. Additional DocumentationNERC Support Document Interchange Scheduling and Coordination (INT)Interconnection Reliability Operations and Coordination (IRO)IDC Related DocumentsIDC Users ManualSystem Data eXchange (SDX) Users Manual 23
24. Next StepsInformal Comment Period (February 18 – March 18)Recommendation (WEQ-000, 001, 002, 003, 008, 013)IDC User’s Manual (forwarded to IDC Working Group)SDX User’s Manual (forwarded to IDC Working Group)NERC supporting documentAddress informal comments (March – June)Post for formal comments by end of second quarter24
25. Next StepsMeetingsMarch 20-21 – Little Rock, AR (hosted by SPP)April 24-25 – Carmel, IN (hosted by MISO)May 22-23 – Valley Forge, PA (hosted by PJM)June 19-20 – Minneapolis, MN (hosted by OATI)25
26. QUESTIONS ?26