IDC Regional Congestion Management Training Plan. Revision 0.9. March 22, 2004

Transcription

1 IDC Regional Congestion Management Training Plan Revision 0.9 March 22, 2004

2 Change Record Version Person Date Change Record IDCWG IDCWG February 12, 2004 March 22, 2004 IDCWG Created Document Initial Release for Training 3/22/2004 Page 2 of 2

3 Table of Contents 1 INTRODUCTION AND PURPOSE REASON FOR CO IMPACT OF CHANGES NEW DATA SUMMARY MARKET FLOW Data MARGINAL ZONE Data and GENERATOR MOBILITY FACTOR Data IDC DATA AND CALCULATION CHANGES FLOWGATE DEFINITION Coordinated Flowgates Reciprocal Flowgates Use of Temporary Flowgates NEW IDC DATA INPUTS TDF CALCULATION UPDATES RTO TAG MAPPING TO MARGINAL ZONES RTO SPECIFIC GENERATOR POINTS NEW IDC DATA OUTPUTS TLR Notifications RTO Market Relief Responsibility Tag Dump IDC USER INTERFACE CHANGES NEW IDC MENU ITEMS Gen. Mobility Factors Screen MARGINAL ZONEs Screen MARKET FLOWs Screen Flowgate NNL UPDATED TLR SCREENS Issue TLR Screen Congestion Management Report Network and Native Load USER TLR ISSUANCE WALKTHROUGH TLR ISSUANCE Selecting a Flowgate for a TLR Issuance TLR Level TLR Level TLR Level 3A TLR Level 3B TLR Level TLR Level 5A TLR Level 5B TLR Level Confirming a TLR Issuance (Relevant to all TLR Levels) /22/2004 Page 3 of 3

4 4.2 TLR RELOADING TECHNICAL APPENDIX ZONAL TDF CALCULATIONS Generator Shift Factors (GSF) Transfer Distribution Factor Transfer Distribution Factors for RTOs REALLOCATION & RELOADING ALGORITHM Reallocation during TLR 3A & 5A Reloading for TLR Levels 1 and MARKET FLOW OVERVIEW Dynamic Schedules Other Tagged Exports MARGINAL ZONE PARTICIPATION FACTORS HOW MARKETS PROVIDE RELIEF NERC TAG DUMP FORMAT /22/2004 Page 4 of 4

5 Section Reason for CO INTRODUCTION AND PURPOSE This training document provides the user of the Interchange Distribution Calculator (IDC) with the changes made to the system to support market systems, as described in the IDC Change Order #114 (CO-114). It is assumed the reader is familiar with the IDC, its concepts, and he/she is a regular user of the system. This document is provided in support of hands-on training, and it is a reference document of the changes to support the IDC CO REASON FOR CO-114 At the request of PJM Interconnection and the Midwest ISO, CO-114 was created in order to address concerns related to the impacts of RTO expansion and intra-regional granularity. Considering the complexities of both the coordination of market-based congestion management with non-market areas and the future impact of the PJM/MISO joint and common market, the two companies created a proposal based on the work of the Parallel Flows Task Force. This proposal included several recommendations as to how an RTO could provide key data to the Interchange Distribution Calculator and improve the congestion management between entities regardless of internal business practices (Market and Non-Market). Change Order 114 is a direct response to the PJM and MISO proposal and provides the requested functionality to address various regional coordination concerns. For detailed information regarding the PJM/MISO proposal, please see the Managing Congestion to Address Seams whitepaper. Generally, the concerns MISO and PJM are trying to address within the whitepaper are referred to as problems with granularity. The term granularity is used to describe the two general problems below associated with Control Area and market expansion. Currently, the IDC is not provided adequate detail on Control Area generation dispatch and this has created problematic representations of flow impact data in various cases. Additionally, as regions have merged and Control Areas become larger, increased concern with granularity of the IDC model has been raised. In the simplest sense, the larger the Control Area, the less clear the transaction impacts are within the Control Area. This is illustrated in the diagram below: 3/22/2004 Page 5 of 5

6 Section Impact of Changes 3 Transactions 6 CAs Easily identified impacts Same Transactions Only 3 CAs Impacts are shifted due to CA Expansion Figure 1. CO114 Granularity Change An additional concern associated with Control Areas merging comes to light when transactions that used to be identified as point to point flows (and therefore tagged) become internal transactions utilizing network service. Under this structure, energy transfers that may have historically been considered non-firm are not necessarily tagged in the new Control Area configuration, and will by default be elevated to firm network status that is subject only to curtailment in TLR 5 or higher. The PJM and MISO proposal addressed these shortcomings primarily in two ways 1). Identifying and submitting in near real time the flow impact of the RTO generation dispatch serving native load (MARKET FLOW) on a Flowgate. 2). Identifying and submitting in near real time a refined representation of the generation dispatch serving interchange in the RTO (MARGINAL ZONE Data). Both of these resulted in special interfaces to the IDC being developed through which an RTO can supply information related to its internal dispatch. An overview of these two general processes follows below. 1.2 IMPACT OF CHANGES The IDC software was created as a tool to allow a Reliability Coordinator to utilize the NERC TLR procedure to receive relief on a congested Flowgate. This relief is assigned by evaluating the submitted real time point-to-point E-tag transactions and static Control Area generation to load responsibility based on the generation topology in an area. Up until this change order, all the real time impacts of a Market Entity that was configured as a single Control Area were invisible to the IDC for use in a non-firm TLR issuance and obtaining relief. With the inclusion of CO- 114 the real time MARKET FLOW of a market area will be visible and available for non-firm curtailment in the IDC. 3/22/2004 Page 6 of 6

7 Section New Data Summary In addition to this increased visibility, the IDC model has been made more granular for the market region to help identify more accurately where transactions Source and Sink. The market areas have been split into MARGINAL ZONEs to create a more granular look at the market area. Including a market relief responsibility and increasing the granularity of the model that feeds the TLR process has created the need for many screen changes and additional menu items in the IDC. Along these same lines since the Market is providing more near real time data to the IDC it has the needed data to calculate the Transfer Distribution Factors (TDFs) on a more frequent basis for those areas that are providing this additional data. These added features will allow the IDC user to track MARKET FLOW on a Flowgate and request relief from the market area on an identified Flowgate in a more accurate manner. 1.3 NEW DATA SUMMARY The new primary information streams to the IDC that provide critical near real-time information to address the above concerns are MARKET FLOW,MARGINAL ZONE, and GENERATOR MOBILITY FACTOR data. MARKET FLOW data provides information regarding a market dispatch contribution to the flow on a Flowgate. These contributions are by the RTO Markets at every LMP cycle (generally between 5 and 15 minutes). MARGINAL ZONE and GENERATOR MOBILITY FACTOR data are used to identify with finer granularity the source and sink points of tagged (point-to-point) transactions that source or sink in the Market footprint. Additional data covered by Change Order 114 is provided primarily for the Reliability Coordinators review and does not directly impact the IDC s key functions. A full description of all data sent to the IDC under this Change Order is listed in section 2.2. These three data flows will give the IDC the additional information necessary to prescribe the appropriate relief during a TLR event. MARKET FLOW data will be utilized to determine the amount of relief the RTO Market should provide through their LMP redispatch under the appropriate TLR levels. MARGINAL ZONE and GENERATOR MOBILITY FACTOR data will provide guidance in determining the impacts of tagged transactions and result in more effective curtailments of Point-to-Point service MARKET FLOW DATA MARKET FLOW data is provided to the IDC in order to address the lack of information regarding internal network flows that historically would have been tagged as point-to-point transactions. Since these transactions no longer require tags and are effectively equivalent to the internal economic dispatch of a traditional control area, a need exists to quantify these flows in order to make them eligible for equitable curtailment when under TLR. The RTO will provide this information by identifying its MARKET FLOWs and then quantifying them into various transmission priorities. PJM and MISO have agreed to classify service as one of three priorities: NNL equivalent Firm Network, or 7-FN Economic Dispatch 6 (ED6) equivalent Non-Firm Network, or 6-NN Economic Dispatch 2 (ED2) equivalent Non-Firm Hourly, or 2-NH 3/22/2004 Page 7 of 7

8 Section New Data Summary In general, PJM and MISO will report the estimated impact of their Network Designated Resources serving Native Load as Priority 7. This service will be curtailed equitably with other Firm service when under a TLR 5A or 5B. Impacts of other generators participating in interchange and/or system load (or effectively any impacts based on generation deviations from the dispatch considered in calculating the Firm Network impacts) will be considered Economy Energy and treated as non-firm. PJM and MISO have determined specific rules for how to identify impacts as priority 2 or 6 more details regarding these rules can be found in the Managing Congestion to Address Seams whitepaper and the Section 0 of this document MARGINAL ZONE DATA AND GENERATOR MOBILITY FACTOR DATA MARGINAL ZONE data is submitted to the IDC to provide a refined representation of the generation dispatch serving interchange in the RTO. The RTO is responsible for supplying three pieces of information to the IDC regarding MARGINAL ZONEs. These are: 1). MARGINAL ZONE Model Representation 2). GENERATOR MOBILITY FACTORS for each Zone 3). MARGINAL ZONE Participation Factors MARGINAL ZONE MODELING The NERC Distribution Factor Working Group has been charged with monitoring the creation of the MARGINAL ZONES for the IDC base case model. The group has identified a series of parameters and criteria to determine if a MARGINAL ZONE is appropriate in nature or needs to be adjusted. In the IDC PSS/e base case a MARGINAL ZONE is defined as a reasonably sized group of generators, which have similar Flowgate impacts. The MARGINAL ZONE size should be manageable and consistent within reasonable parameters and computational tools, not too big or too small GENERATOR MOBILITY FACTORS This data will indicate on a per-generator basis the anticipated availability of a generator to participate in the interchange of the MARGINAL ZONE. It is used to help calculate the TDF for each of the MARGINAL ZONES. For more information on how the TDFs are calculated for each MARGINAL ZONE see Section 5.1 of this document MARGINAL ZONE PARTICIPATION FACTORS This set of data used to help calculate the TDFs for the RTO area. This data will describe how much each defined zone within the RTO is contributing to serving exports/sinking imports. For more information on how the TDFs are calculated for each MARGINAL ZONE see Section 0 of this document. 3/22/2004 Page 8 of 8

9 Section Flowgate Definition 2 IDC DATA AND CALCULATION CHANGES 2.1 FLOWGATE DEFINITION The Market-Based Operating Entity conducts sensitivity studies to determine which flowgates are significantly impacted by its MARKET FLOWS. The sensitivity studies that are conducted are further defined in the Managing Congestion to Address Seams whitepaper that can be found at NERC COORDINATED FLOWGATES The flowgates that existed in the NERC Book of Flowgates (BoF) in January 2003 were used in the initial studies for the MISO and PJM sensitivity analysis studies. As new Flowgates are defined in the NERC BoF and associated processes, MISO and PJM will conduct these same sensitivity studies to determine whether or not the entities have significant impact on the defined elements. A flowgate selected by one of these studies will be considered a Coordinated Flowgate (CF) for an entity and may be internal to or external to the Market-Based Operating Entity s footprint. The Market-Based Operating Entity will upload NNL and MARKET FLOW values for these Coordinated Flowgates to the IDC to be used during a TLR. There are two main types of sensitivity studies that are conducted to determine the Coordinated Flowgates for an entity. 1). Any flowgate found in the current BoF that is impacted by any generator within the Control Areas joining the market by a Generation to Load impact of +/- 5% or greater will be considered a Coordinated Flowgate. 2). Any flowgate found in the BoF that is impacted by the simulated transfer between the CA joining the existing market, as well as between each CA/CA permutation (if more than one CA is moving into the market) by +/- 5% or greater will be considered a Coordinated Flowgate RECIPROCAL FLOWGATES Reciprocal Flowgates are identified as Flowgates that are common to more than one Coordinated Flowgate List. Designating a flowgate as reciprocal does not have an impact on current IDC operation, but does impact other Reliability coordination between some Eastern Interconnect entities USE OF TEMPORARY FLOWGATES In the IDC, Flowgates can be dynamically created as temporary Flowgates (or on-the-fly Flowgates) to assist the Reliability Coordinator in managing congestion on transmission elements where congestion was not anticipated. The creator will be required to notify entities with Coordinated Flowgate lists if the temporary Flowgate might meet the requirements of a Coordinated Flowgate. Once notified of the new Flowgate, the entity(s) will conduct the series of sensitivity analysis studies to identify if the new interface should be included on the Coordinated Flowgate list for the entity. If so, the Market-Based Operating Entity will begin reporting MARKET FLOW data within no more than two business days. 8/10/2005 Page 9 of 9

10 Section New IDC Data Inputs Until the studies can be completed the on-the-fly flowgate will be treated as any other Flowgate that is not a Coordinated Flowgate and will not require the MARKET FLOW impacts to be submitted to the IDC by the Market Based entities. 2.2 NEW IDC DATA INPUTS Under Change Order 114, an RTO must upload several key pieces of data to the IDC to address various reliability needs. Following is a list of inputs that will be provided: Hourly Day-Ahead expected NNL contribution on every coordinated flowgate in both directions. This will identify an RTO s expected impact on flowgates due to the flows associated with native load being served by designated resources. This data will be provided to the IDC at least once a day but no more frequent than once an hour. Market contributions on coordinated flowgates. PJM and/or MISO will provide the IDC the current and next hours projected MARKET FLOW contributions from each service priority (priorities 7 (NNL), ED 6 and ED 2) on every coordinated flowgate, and the estimated unconstrained MARKET FLOW contributions on the coordinated flowgates to be used as reload values for these priorities. These MARKET FLOW contributions will be provided bidirectionally (i.e., in both the forward and the reverse direction). This data will be provided to the IDC at most every 5 minutes and no less than every 15 minutes. Marginal generators for the IDC distribution factor calculation. Two sets of data will be provided to support this calculation: o Individual GENERATOR MOBILITY FACTORS (GMF). This data will indicate on a pergenerator basis the anticipated availability of a generator to participate in interchange in the MARGINAL ZONE. This data will be provided to the IDC no less than once an hour. o MARGINAL ZONE PARTICIPATION FACTORS. This data will describe how much each defined zone within the RTO is contributing to serving exports/sinking imports. This data will be provided to the IDC at most at every 5 minutes but no less than 15 minutes. The RTOs will provide the IDC with their control zone forecast load and inter-zone interchange for the next day. This data will be disseminated through the IDC Tag Dump for the Control Areas. Reliability Coordinators will use this information to perform contingency analysis studies for the next day. This data will be provided to the IDC once a day. The RTO will provide their next day hourly control zone load forecast and net interchange amounts at 12 PM CST and will be updated as more accurate data is available for the next day. This data will be disseminated through the IDC Tag Dump for the Control Areas. Reliability Coordinators will use this data to perform contingency analysis. The current day net interchange and load forecast amounts should be sent no later than 12 AM CST and will be updated as more accurate data is available. This data will be disseminated through the IDC Tag Dump for the Control Areas. Reliability Coordinators will use this data to perform contingency analysis. 8/10/2005 Page 10 of 10

11 Section TDF Calculation Updates Every hour, the RTOs will provide the IDC with the current and next hour control zone forecasted load and net interchange. This data will be disseminated through the IDC Tag Dump for the Control Areas. Reliability Coordinators will use this data to perform contingency analysis. This data will be provided to the IDC once every hour. 2.3 TDF CALCULATION UPDATES The IDC software introduces a new method for calculating Transfer Distribution Factors for the Market entities that are participating in the CO-114 changes. This methodology identifies more clearly where exported energy is being generated and where imported generation is being consumed. A system of using real-time MARGINAL ZONE PARTICIPATION FACTORS and GENERATION MOBILITY FACTORS will be utilized to come up with two separate TDF values for each Market Area. One will be based on the Import capabilities of the area and the other will be based on the Export capabilities of the area. These new TDFs will be used to better identify the impacts of the transactions Sourcing or Sinking in the Market Area, and to provide a more detailed representation of the generating units which are affected by the curtailment of tagged transactions. Nevertheless, there will be cases which are explained later in the document, that utilize the TDF factors calculated from historical control area footprints for assigning impacts to specific transactions. The Market entities will provide the MARGINAL ZONE WEIGHTING FACTORS and the GENERATION MOBILITY FACTORS to the IDC every 15 minutes. The IDC will update the TDF matrices associated with the Market areas when it receives updated factors; thus providing a more accurate representation of the Market response to TLR actions. Control Areas that are not part of the Market Entity will not provide this additional real-time data to the IDC, and recalculation of their TDF values will continue to be performed at the top of the hour.details of the Market Areas import and export TDF calculations are described further in Section of this document. 2.4 RTO TAG MAPPING TO MARGINAL ZONES The MARGINAL ZONE concept is used in order to more accurately identify the set of generators whose schedules change in response to point-to-point transaction curtailments. The RTO will provide the IDC with sets of export and import MARGINAL ZONE weighting factors. The Export factors will be utilized to assess the impact of transactions which source in the RTO. The Import factors will be utilized to assess the impact of transactions which sink in the RTO. These weighting factors will be used by the IDC to weight and scale the RTOs zonal TDFs, and calculate the RTO TDF. Special situations like the pathway between ComEd and PJM through AEP, or the use of RTO specific Generator Points may be excepted from this rule. This is further discussed in Section 2.5. With regard to tagged transactions between PJM and ComEd, it is possible that the net effect of the transaction can be considerably skewed. If all the marginal export generation is in ComEd and all the marginal import generation is also in ComEd, the IDC will effectively treat the tag as transferring energy from ComEd to ComEd. This tag will have a 0% affect on all flowgates and never be curtailed. To address this unique situation, the tags that model energy transfer between PJM and ComEd (i.e., where one is the source and the other the sink) will use the historical model of these control area TDFs, rather than the adjusted TDFs described in section /10/2005 Page 11 of 11

12 Section RTO Specific Generator Points 2.5 RTO SPECIFIC GENERATOR POINTS Certain schedules may always come from a specific generator. To the extent that these sources are known, the RTO may elect to request that these sources be modeled as specific pseudo- Control Areas. For each of these Pseudo-Control Areas, a specific TDF will be generated to ensure transaction impact is modeled appropriately. Pseudo-Control Areas must be approved by the NERC ORS before implementation. 2.6 NEW IDC DATA OUTPUTS The IDC user interface has been modified to support the usage and information display of MARKET FLOW. The changes to the user interface are: Main IDC toolbar: Four new buttons are added to the IDC toolbar to support the additional data the IDC receives from the markets. These buttons provide links to the GENERATOR MOBILITY FACTORS display, MARKET FLOW display, MARGINAL ZONE display, and Day-Ahead Flowgate NNL display. TLR Issuance: At the TLR issuance page, in addition the tagged transaction contributions to the flow on the flowgate, the MARKET FLOW on the coordinated flowgates are displayed as well. This enables the user to make decisions on TLR curtailment amounts taking the MARKET FLOW into consideration. Congestion Management Report: The Congestion Management Report has been modified to include the IDC calculations on the MARKET FLOW on the summary section. In addition, a new section on the page covering the MARKET FLOW in a TLR has been added. Whole Transaction List: The MARKET FLOW information has been added to the Whole Transaction List display. This enables the user to identify the level of flow on each transmission priority level that also includes the Market. In addition to the changes to the IDC Graphical User Interface, the IDC suggested changes to the RTO Market contributions is communicated to the RTO Markets using message exchange mechanisms TLR NOTIFICATIONS The IDC will send a message to the RTO when a TLR is initiated or when the level of the TLR changes. This will be used by the RTO to respond proactively to congestion as appropriate. This data will be sent on demand as TLR events occur and change level RTO MARKET RELIEF RESPONSIBILITY When the appropriate TLR level is called, the IDC will send a relief request to the RTO. The relief request will contain the necessary information for the RTO to curtail the MARKET FLOW on the impacted flowgate to the requested limits. This data will be sent on demand as TLR events occur and relief on a flowgate is necessary. 8/10/2005 Page 12 of 12

13 Section New IDC Menu Items TAG DUMP The IDC creates a text file each hour containing all of the E-Tags in the IDC database. This file, called the NERC Tag Dump is posted to a NERC FTP site and is used by several Reliability entities in the Eastern Interconnect for system studies and reliability analysis. When a Control Area footprint or Market expands, tags are eliminated between areas which have become part of the same footprint. As a result, the Tag Dump data cannot be used to determine interchange between these areas. Each entity that is expanding its Control Area boundary or expanding its Market Area is responsible to provide a Net Interchange and Load value for the areas in which are no longer visible in the Tag Dump. These values will be uploaded to the IDC at least hourly to be included in the NERC Tag Dump. The changes to the NERC Tag Dump format to accommodate this additional information can be found in Section 0 of this document. 3 IDC USER INTERFACE CHANGES 3.1 NEW IDC MENU ITEMS The changes associated with the CO-114 include the addition of four new menu buttons to the IDC Main page. These new items reflect the additional Market Area information for calculation of TDFs and assignment of Relief Responsibility to the Market Areas. These screens will be described in detail in the next few sections of the document. 8/10/2005 Page 13 of 13

14 Section New IDC Menu Items Figure 2. New IDC Menu Items GENERATOR MOBILITY FACTORS SCREEN This screen allows any IDC user to view the GENERATOR MOBILITY FACTORs (GMF) for each generator defined in the MARGINAL ZONEs. See Section for the definition of GMF. The GMFs are automatically updated and sent to the IDC by the Market Area. This screen also allows the RC with generators in a MARGINAL ZONE to manually update the GMFs and schedule a TDF matrix calculation for all CA and MARGINAL ZONE factors. 8/10/2005 Page 14 of 14

15 Section New IDC Menu Items Figure 3. GENERATOR MOBILITY FACTORs Display The Zone/CA: pull down menu allows the user to view the Mobility Factors for every generator in the MARGINAL ZONE selected. The Edit button allows the RC whose responsibility it is to send the GMFs the ability to manually update the Mobility Factor for any generator defined in the selected MARGINAL ZONE. An entity that does not have a responsibility to send the GMFs to the IDC will not have the Edit button available. The Schedule TDF Recalculation button works the same as today on other IDC screens. If this button is selected, the IDC will recalculate the entire TDF matrix using the updated GMFs at xx:20, xx:40, or top of the hour, whichever comes first. A GENERATOR MOBILITY FACTOR can be a value between 0 and 1 (representing a percentage of mobility). To further explore how the GENERATOR MOBILITY FACTORs are used in the calculation of the TDFs for the Market Area please see Section 5.1 of this document MARGINAL ZONES SCREEN This screen allows any user to view the Marginal Zone Factors (MZFs) for each MARGINAL ZONE (with respect to either import or export capability) in the Market Areas. See Section /10/2005 Page 15 of 15

16 Section New IDC Menu Items for the definition of MARGINAL ZONE Factors and Section 5.1 for a more detailed explanation of how the MZFs are used. The MZFs are automatically updated and sent to the IDC every 15 minutes by the Market entity for the current hour TDF calculation, and once an hour for the next hour TDF calculation. The current and next hour TDFs for the Markets are updated automatically every time new MARGINAL ZONE Factors are received. This screen also allows the RC responsible for a MARGINAL ZONE to manually update the factors in that zone. However, in order for the IDC to use the MARGINAL ZONE Factors the user must request its update through the user interface. Figure 4. MARGINAL ZONEs Display The Market: pull down menu allows the user to view the MARGINAL ZONE factor for every MARGINAL ZONE in the Market Area selected (with respect to import or export capability). The Edit button allows the RC whose responsibility it is to send the MZFs the ability to manually update the participation factor for any MARGINAL ZONE on the fly in the Market Area (import or export) selected. An entity that does not have a responsibility to send the MZFs to the IDC will not have the Edit button available. The Update MZF button requests the IDC to recalculate the TDFs for only the Market Area (import and export) using the updated MARGINAL ZONES. The recalculation will occur at the 8/10/2005 Page 16 of 16

17 Section New IDC Menu Items time of the request (for example, if the operator believes system topology has changed significantly since the most recent update of MARGINAL ZONE information). Otherwise, the MARGINAL ZONE TDF calculation will occur automatically every time the IDC receives the MARGINAL ZONE factors from the Market Entity. The MARGINAL ZONE Factors are scaled by the IDC so that their sum equals to 1.0. Negative MARGINAL ZONE Factors are assumed zero and are ignored by the IDC MARKET FLOWS SCREEN The MARKET FLOWs screen allows any user to view the MARKET FLOW (MF) values (ED-2, ED- 6, and Firm-7) for any Coordinated Flowgate for a user-specified time range. The MF values are submitted by the Market Entity on at least a fifteen-minute basis to the IDC for each Coordinated Flowgate. The user can view the current and the next hour MF values that have been submitted by the Market entity in order of submittal time. The MF value for each priority will be shown in both the normal (normal refers to the defined From-To direction of the Coordinated Flowgate) and reverse direction (reverse refers to the To-From or opposite of the defined direction of the Coordinated Flowgate) as well as the total Net MF for the Flowgate. There is also additional graphical capability available in this screen to allow the IDC user to have a visual representation of the MARKET FLOW on a Flowgate for the selected time period. The Time Range section is the user-defined time range (Start and Stop) in which the MF values will be shown per the selections in the MF query. Actual measurements received during the hour have their start times set to the time the data is sent by the Markets to the IDC. Future measurement values represent best estimates from the Markets. The Submittal Time section is the time the MF values were submitted to the IDC by the Market Entity. The Measurement Type section is the type of MF being displayed. Note that multiple MF values may be displayed. The MF value with the latest time stamp is the most accurate. The Next Hour MF value is sent once an hour prior to xx:25 that projects the aggregate MF value for the next hour. The Measurement Type indicates the market measurement that was submitted. Current indicates the current hour market value that is being submitted Next Hour indicates the next hour market value that is being submitted The Direction section breaks the MF value in the normal and reverse direction. All components of the MF will be designated. The ED-2 section is the portion of MF that has the same priority as a bucket level 2 transactions and represents a portion of the Non-Firm MWs flowing on the Flowgate. The ED-6 section is the portion of MF that has the same priority as a bucket level 6 transactions and represents a portion of the Non-Firm MWs flowing on the Flowgate. The FIRM-7 section is the portion of MF that has the same priority as a bucket level 7 transactions and represents the Firm and NNL flowing on the Flowgate. 8/10/2005 Page 17 of 17

18 Section New IDC Menu Items The Total section is the sum of ED-2, ED-6, and FIRM-7 for the normal and reversed direction. The Total Net Flow is the net value of the total MF for the normal and reversed direction. The SDX Status is an indication of whether or not any part of the Flowgate is marked out of service by the SDX submittals. Figure 5. MARKET FLOW Display The View Unconstrained button toggles the Unconstrained section of the report into and out of view. When the Unconstrained section is in view the button reads Hide Unconstrained and when selected removes the Unconstrained section from view. The Unconstrained section represents the predicted unconstrained MF value on the Coordinated Flowgate in both the normal and reverse direction. This will give an indication of what the MFs would be if the Flowgate were to be Unconstrained by TLR. This value is similar to the Scheduled value on a transaction and is used for TLR events where Reloading is taking place. The View Graph button shows the all MF values that were submitted for the user-specified time range in a tabular or graphical format. For each time listed, the most up to date MF value the IDC had at that time will be displayed. 8/10/2005 Page 18 of 18

19 Section New IDC Menu Items Figure 6. MARKET FLOW Display with Unconstrained Values The Show Table button displays the MF values in tabular format (as seen above in the screen shot). This displays the same information as the MARKET FLOW screen (MFs broken up into priorities and direction as well as the net MF value) for the selected time frame. The Show Graph button displays the MF values in graphical format. This displays the same information as the MARKET FLOW screen (MFs broken up into priorities and direction as well as the net MF value). You can The graph will illustrate the submitted MARKET FLOW components and the breakdown based on each of the priorities for the Flowgate in the defined direction. A net of both the positive and negative MARKET FLOW is also listed. This is a printable screen. The FIRM-7 ED-6 ED-2 MW line indicates the sum of the total MARKET FLOW (including all three components) on the Flowgate in the defined direction. The color of the text is the line that indicates this sum. 8/10/2005 Page 19 of 19

20 Section New IDC Menu Items Figure 7. Graphical Display of MARKET FLOW over a period of time The FIRM-7 line indicates the sum of the FIRM MARKET FLOW on the Flowgate in the defined direction. The color of the text is the line that indicates this sum. The Net MW line indicates the sum of the positive and negative MARKET FLOW on the Flowgate in the defined direction. The color of the text is the line that indicates this sum. The user will have two configurable settings to adjust the scale of the graph and to show data points on the graph to make it useful for printing and viewing. The Show Points radio box can be selected to show the individual data points on the linear graph. The Scale button can be selected to adjust the MW scale for the shown graph. This allows the user to set the vertical MW scale of the graph only as the Timeframe selected was chosen in a previous menu. Once the desired vertical MW scale is chosen the Set Scale button should be selected to apply the changes to the shown graph. The Auto button can be selected to have the graph automatically scale the vertical MW of the graph for optimal viewing. By selecting this button the shadow box is removed from the screen leaving only the Scale button on the screen. 8/10/2005 Page 20 of 20

21 Section New IDC Menu Items FLOWGATE NNL The Flowgate NNL screen provides the IDC user the ability to view the submitted Next Day NNL values on the Coordinated Flowgates by the Market Areas. This value represents what the market is predicting as flow on the Flowgate for the following day. These values are sent by the Market Area by noon the previous day to the IDC for use in the viewer. These values are not used in any TLR processes and are just for informational purposes. Updated market FIRM-7 values will be sent to the IDC current day for all Coordinated Flowgates to be used in the TLR process. Figure 8. Day-Ahead NNL (Firm Market Impact) The RTO pull down menu allows the user to filter the list of Coordinated Flowgates to display only those that are associated with the specified RTO. The Coordinated Flowgate pull down menu allows the user to specify a particular flowgate for which they would like to view RTO-reported information. The Start Time and Stop Time pull down menus allow the user to specify a particular range of time for which they would like to view NNL impacts. The Time Range indicates the duration for which the reported data applies. 8/10/2005 Page 21 of 21

22 Section Updated TLR Screens The Submittal Time indicates the time at which the RTO submitted the NNL data to the IDC. The Normal NNL Flow indicates the positive (forward) NNL impacts on the specified flowgate. The Reverse NNL Flow indicates the negative (counterflowing) NNL impacts on the specified flowgate. 3.2 UPDATED TLR SCREENS ISSUE TLR SCREEN Figure 9. Issue TLR Display Once a flowgate is chosen for TLR, the Issue TLR screen is presented. Field(s) have been added to indicate the total MARKET FLOW contribution to this flowgate across all priorities. There may be entries for Current Hour and Next Hour, depending on the TLR Level. A negative number for MARKET FLOW simply indicates that the magnitude of the counterflow is greater than the contributing flow. The MARKET FLOW contribution is supplied by the RTO. The Tag Contribution is determined by the IDC based on information from Etag. As today, the Next Hour INC / DEC column, if present, indicates the MW change at the top of the hour for which the IDC has received notification. The number includes both Market and Tag flow changes and provides a reference for how much relief to request. Once the amount of relief is chosen and the Issue TLR button is pressed, the Congestion Management Report is presented. The Direction indicates whether the TLR is being called in the conventional direction in which the flowgate was defined or in the reverse direction. The Current Active Flow MW shows the total impact on the flowgate for the current hour, as well as the portion due to tags and the portion due to market activity. The Next Hour Scheduled MW shows the total anticipated impact on the flowgate for the next hour, as well as the portion due to tags and the portion due to market activity. 8/10/2005 Page 22 of 22

23 Section Updated TLR Screens The Next Hour Inc/Dec (+/-) indicates the change between current hour total MW and next hour total MW. The Current Flow Inc/Dec (+/-) Request indicates the current amount for relief being requested under the TLR CONGESTION MANAGEMENT REPORT SUMMARY SECTION Figure 10. Congestion Management Summary The summary section at the top of the Congestion Management Report now contains additional data reflecting the changes to the IDC to support the markets. The Transactional and NNL Impact Relief Summary has been expanded to include the current and next hour MARKET FLOW, and market relief required by the TLR actions MARKET FLOW RELIEF Underneath the Summary section in the Congestion Management Report, there will be a section with information on the MARKET FLOW results from the IDC, entitled Current Hour Market Flow Responsibility or Next Hour Market Flow Responsibility, depending on the TLR level CURRENT HOUR MARKET FLOW RESPONSIBILITY EXAMPLE 1 8/10/2005 Page 23 of 23

24 Section Updated TLR Screens Figure 11. Current Hour MARKET FLOW Example 1 The Current Hour MARKET FLOW Responsibility section provides the RC with information on how the generation dispatch in the market area is contributing to loading on the flowgate. In the past, this information was only available during TLR5x and was estimated based on a generic dispatch. The Current MARKET FLOW is broken down into a number of pieces. The TLR Direction column contains the priority levels provided by the RTO at the time the MW amounts were uploaded to the IDC. The IDC does not validate these priorities. The Total is the sum of all contributing MARKET FLOW. The Counter Flow indicates the amount of MARKET FLOW which is in the opposite direction of the TLR. This number is also supplied by the RTO. The Net amount is simply the subtraction of the contributing (forward) flow and the counter (reverse) flow. This number may be negative if the counterflow is greater in magnitude than the total contributing flow. The Target Net MARKET FLOW column is simply the Net minus the Market Relief Required NEXT HOUR MARKET FLOW RESPONSIBILITY The Next Hour MARKET FLOW Responsibility provides the RC with information on how the generation dispatch in the market is anticipated to contribute to loading on the flowgate at the top of the hour. The Next Hour MARKET FLOW information is provided in identical form as the Current Hour MARKET FLOW, however for different TLR levels. Please refer to the explanations in that section MARKET FLOW DETAIL The IDC user can select the underlined Market to access the details of the MARKET FLOWs provided by the RTO for the Flowgate in TLR. This screen presents details for the MARKET FLOW data on an hourly basis for the Current and Next hour that are active for the TLR. If this screen is accessed for a TERMINATED TLR or a TLR that was issued in the past it will always access the MARKET FLOW data that was active for the TLR that is being viewed. Therefore the data could be in the past depending on the TLR Congestion Management Report that is accessed. 8/10/2005 Page 24 of 24

25 Section Updated TLR Screens For a more complete and up-to-date list of the MARKET FLOW on a Flowgate the MARKET FLOW screen described in Section should be utilized. Figure 12. MARKET FLOW Detail in response to a TLR The Time Range indicates the period within which the Market Flow is effective. Each submittal is considered the Active MW on the Flowgate for the hour until the next MARKET FLOW value is submitted. Within the Time Range, the entries are ordered by submittal time, with the most recent submission on the top. The Submittal Time shows when the data was received by the IDC from the Market entity. Note that there may be multiple entries for the same Time Range, but with different Submittal Times. This is because the MARKET FLOW may be updated as frequently as every 15 minutes. 8/10/2005 Page 25 of 25

26 Section TLR Issuance The Measurement Flow is presented in the TLR Direction, which indicates MWs that are contributing to the flowgate flow based on the defined Direction of the TLR in the yellow summary box at the top of the screen. Along with this the Reverse Direction is displayed which indicates MWs that are reducing the flowgate flow based on the defined Direction of the TLR in the yellow summary box at the top of the screen. The Net value is the summation of the TLR Direction and Reverse Direction NETWORK AND NATIVE LOAD For a Coordinated Flowgate in TLR 5, the market area must have its impact removed from the from the NNL responsibility because the MARKET FLOW MW already includes the generation to load impacts for the area. If the impact is not removed, the market area would be providing twice the amount of relief they are responsible for. However, the market area will be included in the NNL Responsibility if the MARKET FLOW data is normally submitted but unavailable, or if the flowgate is not a Coordinated Flowgate (which means MARKET FLOW data is not submitted for it). 4 USER TLR ISSUANCE WALKTHROUGH 4.1 TLR ISSUANCE This section provides a brief description of all TLR Levels (See Table 1 1 ) as well as a short screen shot walk through. This is not intended to be an all encompassing How to Issue a TLR guide rather it is meant to highlight changes in the TLR processes due to CO-114. Additional detail on TLR Issuances can be found in alternate TLR training documents. Table 1 below describes each TLR Level as currently described by the NERC Operating Manual. Note this table may be superseded by changes or updates to the Operating Manual. 1 NERC Operating Policy 9, Appendix 9C1 8/10/2005 Page 26 of 26

27 Section TLR Issuance TLR Level RELIABILITY COORDINATOR Action Comments 1 Notify RELIABILITY COORDINATORS of potential OPERATING SECURITY LIMIT violations 2 Hold INTERCHANGE TRANSACTIONS at current levels to prevent OPERATING SECURITY LIMIT violations 3a 3b Reallocation Transactions using Non-firm Point-to- Point Transmission Service are curtailed to allow Transactions using higher priority Point-to-Point Transmission Service Curtail Transactions using Non-firm Point-to-Point Transmission Service to mitigate Operating Security Limit Violation Of those transactions at or above the CURTAILMENT THRESHOLD, only those under existing Transmission Service reservations will be allowed to continue, and only to the level existing at the time of the hold. Transactions using Firm Point-to-Point Transmission Service are not held. See Section B.1. Curtailment follows Transmission Service priorities. Higher priority transactions are enabled to start by the REALLOCATION process. See Section B.3. Curtailment follows Transmission Service priorities. There are special considerations for handling Transactions using Firm Point-to-Point Transmission Service. See Section B.4. System Secure Security Limit Violation 4 Reconfigure transmission system to allow Transactions using Firm Point-to-Point Transmission Service to continue 5a 5b Reallocation Transactions using Firm Point-to-Point Transmission Service are curtailed (pro rata) to allow new Transactions using Firm Point-to-Point Transmission Service to begin (pro rata). Curtail Transactions using Firm Point-to-Point Transmission Service to mitigate Operating Security Limit Violation There may or may not be an OPERATING SECURITY LIMIT violation. There are special considerations for handling Transactions using Firm Point-to-Point Transmission Service. See Section B.5. Attempts to accommodate all Transactions using Firm Point-to-Point Transmission Service, though at a reduced ( pro rata ) level. Pro forma tariff also requires curtailment / REALLOCATION on pro rata basis with Network Integration Transmission Service and Native Load. See Section B.6. Pro forma tariff requires curtailment on pro rata basis with Network Integration Transmission Service and Native Load. See Section B.7. 6 Emergency Action Could include demand-side management, redispatch, voltage reductions, interruptible and firm load shedding. See Section B.8. 0 TLR Concluded Restore transactions. See Section B.9. System Secure Security Limit Violation System Secure Table 1 Summary of TLR Levels SELECTING A FLOWGATE FOR A TLR ISSUANCE This sequence of screens applies to all TLR Levels to prepare the software for a TLR issuance on a Flowgate INITIATING A TLR 8/10/2005 Page 27 of 27

28 Section TLR Issuance Figure 13. Initiating a TLR Select the Issue TLR menu item from the Main Menu screen as shown below. 8/10/2005 Page 28 of 28

29 Section TLR Issuance Figure 14. Choosing TLR Flowgate Select the Reliability Coordinator and Control Area where the Flowgate resides to query for a list of possible Flowgates. Select the desired Flowgate from the designated Control Area. Verify and select the direction of flow for the Flowgate to ensure relief in the proper direction is calculated. 8/10/2005 Page 29 of 29

30 Section TLR Issuance Figure 15. Choosing TLR Level Select the TLR Level that is desired for the event on the Flowgate per the descriptions in Table 1. The details in the following sections describe the individual TLR levels and their specific attributes TLR LEVEL 1 This TLR Level is requested by an Operator to Notify RELIABILITY COORDINATORS of a potential for an OPERATING SECURITY LIMIT violation on a Flowgate. This TLR will give the operator an opportunity to review the existing Market and Transaction Flow on the selected Flowgate before the TLR Level 1 is issued and broadcasted to the other IDC Users. No curtailments will take place in this TLR Level. The Reloading of a transaction to its scheduled MW can take place in this TLR Level if the TLR sequence of events has included a TLR Level 2 or higher in which curtailments were made. The reloading will be done by sending a MW Cap request to the Source and Sink Control Areas on the transaction and/or a Relief Responsibility Request to the RTO. These messages are initiated when the Reliability Coordinator assigned to the Sink of each transaction Acknowledges the MW Cap request and/or Relief Responsibility for the TLR event. 8/10/2005 Page 30 of 30

31 Section TLR Issuance Figure 16. Issue TLR Level 1 Once the TLR Level 1 is designated from the drop down menu the Issue TLR Level 1 button should be selected. Figure 17. TLR 1 Congestion Management Report This will prompt the IDC software to bring up the Congestion Management Report for the TLR Level 1. Once the information in the report is reviewed the Confirm button can be selected to send the TLR issuance to the other Reliability Coordinators and the NERC RCIS (See Section for direction Confirming a TLR Issuance). 8/10/2005 Page 31 of 31

32 Section TLR Issuance TLR LEVEL 2 This TLR Level is requested by an Operator to Hold INTERCHANGE TRANSACTIONS at current levels to prevent OPERATING SECURITY LIMIT violations. This TLR will give the operator an opportunity to review the existing Market and Transaction Flow on the selected Flowgate before the TLR Level 2 is issued and broadcasted to the other IDC Users. The IDC will hold all NON-FIRM transactions at the current hour scheduled values for the next hour by sending a MW Cap request to the Source and Sink Control Areas on the tag. The IDC will hold the Non-Firm MARKET FLOW impacts (i.e. ED-2 and ED-6) on the Flowgate to their current hour scheduled value for the next hour by sending a Relief Responsibility Request to the RTO. These messages are initiated by the Reliability Coordinator assigned to the Sink of each transaction by Acknowledging the MW Cap request and/or Relief Responsibility for the TLR event. Figure 18. Issue TLR 2 Once the TLR Level 2 is designated from the drop down menu the Issue TLR Level 2 button should be selected. 8/10/2005 Page 32 of 32

33 Section TLR Issuance Figure 19. TLR 2 Congestion Management Report This will prompt the IDC software to bring up the Congestion Management Report for TLR Level 2. Once the information in the report is reviewed, the Confirm button can be selected to send the TLR issuance to the other Reliability Coordinators and the NERC RCIS (See Section for directions in confirming a TLR Issuance) TLR LEVEL 3A This TLR level will be effective at the beginning of the next hour to prevent an OSL violation. It provides for reallocation of NON-FIRM transactions to hold flowgate loading at or below the OSL. In TLR Level 3A, transactions will be allowed to start or increase only by curtailing existing lower priority transactions. Transactions starting or increasing in the next hour may be partially loaded along with the curtailment of lower priority transactions, but may not cause the curtailment of equal priority existing transactions. 8/10/2005 Page 33 of 33

34 Section TLR Issuance MARKET FLOW on the Flowgate that is in TLR Level 3A will be placed in the appropriate Non- Firm buckets (i.e. ED-2 and ED-6) and assumed to have the highest sub priority S1 (See Appendix 5.2.1) during the curtailment prescription and reload. This may be a persistent TLR Level. To remain in a TLR Level 3A, the TLR must be reissued hourly to recognize new transactions and topology. This TLR will give the operator an opportunity to review the Current and Next Hour Market and Transaction Flow on the selected Flowgate before the TLR Level 3A is issued and broadcasted to the other IDC Users. Figure 20. Issue TLR 3A Once the TLR Level 3A is designated from the drop down menu the Issue TLR Level 3A button should be selected. 8/10/2005 Page 34 of 34

35 Section TLR Issuance Figure 21. TLR 3A Congestion Management Report This will prompt the IDC software to bring up the Congestion Management Report for the TLR Level 3A. Once the information in the report is reviewed the Confirm button can be selected to send the TLR issuance to the other Reliability Coordinators and the NERC RCIS (See Section for directions in confirming a TLR Issuance) TLR LEVEL 3B This TLR level can be issued at any time to mitigate an OSL violation. This TLR level will be effective at an operator specified time during the current hour to mitigate an OSL violation. For the next hour it provides for reallocation of NON-FIRM transactions to return the flowgate loading below the OSL CURRENT HOUR When a TLR Level 3B is issued, a curtailment list for the current hour will be generated. This curtailment list will not contain any FIRM transactions and will only include NON-FIRM transactions that impact the Flowgate by greater than or equal to its TDF cutoff in the overloading direction of the flowgate. 8/10/2005 Page 35 of 35

36 Section TLR Issuance MARKET FLOW on the Flowgate will be curtailed using the current hour scheduled values for the Non-Firm portions of the flow (i.e.ed-2 and ED-6) NEXT HOUR An additional curtailment list for the next hour will also be generated to further mitigate loading on the constrained Flowgate. This curtailment list will not contain any FIRM transactions that have met the timing requirements specified in the Operating Policy and will only include NON- FIRM transactions that impact the Flowgate by greater than or equal to the TDF cutoff in the direction of the flowgate. This curtailment list allows transactions to start or increase only by curtailing existing lower priority transactions. Transactions starting or increasing in the next hour may be partially loaded along with the curtailment of lower priority transactions, but may not cause the curtailment of equal priority existing transactions. MARKET FLOW on the Flowgate that is in the next hour curtailment list for the TLR Level 3B will be placed in the appropriate Non-Firm buckets (i.e. ED-2 and ED-6) and assumed to have the highest sub priority S1 (See Appendix 5.1.3) during the curtailment prescription and reload. A TLR Level 3B is a transient state; the intent is to leave the TLR Level 3B as soon as possible. Figure 22. Issue TLR 3B This will prompt the IDC software to bring up the Congestion Management Report for the TLR Level 3B. Once the information in the report is reviewed, the Confirm button can be selected to send the TLR issuance to the other Reliability Coordinators and the NERC RCIS (See Section for direction Confirming a TLR Issuance). 8/10/2005 Page 36 of 36

37 Section TLR Issuance TLR LEVEL 4 Figure 23. TLR 3B Congestion Management Report This TLR Level is requested by an Operator to Reconfigure the transmission system to allow Transactions using FIRM Point-to-Point Transmission Service to continue. This TLR will give the operator an indication of any existing Market and Transaction Flow on the selected Flowgate before the TLR Level 4 is issued and broadcasted to the other IDC Users. 8/10/2005 Page 37 of 37

38 Section TLR Issuance The IDC will curtail all NON-FIRM transactions to zero by sending a MW Cap request to the Source and Sink Control Areas on the tag. The IDC will curtail the NON-FIRM MARKET FLOW impacts (i.e. ED-2 and ED-6) on the Flowgate to zero by sending a Relief Responsibility Request to the RTO. These messages are initiated when the Reliability Coordinator assigned to the Sink of each transaction Acknowledges the MW Cap request and/or Relief Responsibility for the TLR event. Figure 24. Issue TLR 4 Once the TLR Level 4 is designated from the drop down menu the Issue TLR Level 4 button should be selected. 8/10/2005 Page 38 of 38

39 Section TLR Issuance Figure 25. TLR 4 Congestion Management Report This will prompt the IDC software to bring up the Congestion Management Report for the TLR Level 4. Once the information in the report is reviewed the Confirm button can be selected to send the TLR issuance to the other Reliability Coordinators and the NERC RCIS (See Section for directions in confirming a TLR Issuance) TLR LEVEL 5A This TLR level is intended to be effective at the beginning of the next hour to prevent an OSL violation. It provides for reallocation of FIRM transactions to hold the flowgate loading at or below the OSL. This level shares some similarities with the TLR Level 3A because they both have the same next hour timing requirements for transaction curtailments. A TLR Level 5A affects all transactions impacting the flowgate by more than the TDF cutoff for the flowgate, including FIRM transactions on a pro-rata basis. All NON-FIRM 8/10/2005 Page 39 of 39

40 Section TLR Issuance transactions will be curtailed by capping the MW value at 0. FIRM transactions are reallocated on a pro-rata basis. In addition to the FIRM transactional impact, each Control Area with a Network to Native Load (NNL) responsibility on the Flowgate will be assigned an NNL amount. The Control Area will be required to reduce their generator to load contribution on the Flowgate by the assigned amount. For more information on this calculation of responsibility, please refer to the NERC Parallel Flows Reference document. The FIRM-7 MARKET FLOW on the Flowgate will also be assigned a portion of the relief responsibility based on its percentage of impact on the Flowgate. IDC will generate a list of all next hour transactions that impact the flowgate by more than the TDF cutoff for the flowgate. All NON-FIRM Transactions in the list will be fully curtailed. In the case that FIRM curtailments are not needed, the SC will be notified that a 5A is not required and that if it proceeds, all NON-FIRM transactions will be adjusted to 0, but no FIRM curtailments will be issued. For example: If the Operator issuing the TLR Level 5A Event is asking for 150 MW of relief on a Flowgate the IDC will query the existing transactions, MARKET FLOW and available NNL impact on the constrained Flowgate. NonFirm Transactions = 50 MW Firm Transactions = 150 MW MARKET FLOW = 165 MW CA NNL = 315MW The software will determine the overall percentage of impact for each Firm category for the Flowgate. FirmTransactions = Firm Firm + MarketFlow + NNL = = 20% MARKET FLOW = MarketFlow Firm + MarketFlow + NNL = = 30% CA NNL = NNL Firm + MarketFlow + NNL = = 50% The IDC will then assign the subsequent amount of relief to each of the categories and prescribe the curtailments. FirmCurtailments = (Requested Relief) (NonFirm Transactions) = 100 MW Firm Transaction Curtailments = 20MW MARKET FLOW Responsibility = 30MW CA NNL Responsibility = 50 MW 8/10/2005 Page 40 of 40

41 Section TLR Issuance Figure 26. Issue TLR 5A Once the TLR Level 5A is designated from the drop down menu the Issue TLR Level 5 button should be selected. This will prompt the IDC software to bring up the Congestion Management Report for the TLR Level 5A. Once the information in the report is reviewed the Confirm button can be selected to send the TLR issuance to the other Reliability Coordinators and the NERC RCIS (See Section for direction Confirming a TLR Issuance). 8/10/2005 Page 41 of 41

42 Section TLR Issuance TLR LEVEL 5B CURRENT HOUR Figure 27. TLR 5A Congestion Management Report This TLR level is intended to be effective during the current hour to mitigate an OSL violation, although a TLR Level 5B also prescribes a Next Hour Curtailment list to help mitigate loading on the constrained Flowgate the next hour. It does not provide for reallocation of new or increasing transactions. 8/10/2005 Page 42 of 42

43 Section TLR Issuance A TLR Level 5B affects all transactions impacting the flowgate by more than the TDF cutoff for the flowgate, including FIRM transactions on a pro-rata basis. All NON-FIRM transactions will be curtailed by capping the MW value at 0 and firm transactions are reallocated on a pro-rata basis. In addition to the FIRM transactional impact, each Control Area with a Network to Native Load (NNL) responsibility on the Flowgate will be assigned an NNL amount. The Control Area will be required to reduce their generator to load contribution on the Flowgate by that amount. For more information on this calculation of responsibility please refer to the NERC Parallel Flows Reference document. The FIRM-7 MARKET FLOW on the Flowgate will also be assigned a portion of the relief responsibility based on its percentage of impact on the Flowgate. IDC will generate a list of all current hour transactions that impact the flowgate by more than the TDF cutoff for the flowgate. All NON-FIRM Transactions in the list will be fully curtailed. In the case that FIRM curtailments are not needed, the SC will be notified that a 5B is not required and that if it proceeds, all NON-FIRM transactions will be adjusted to 0, but no FIRM curtailments will be issued. For example: If the Operator issuing the TLR Level 5B Event is asking for 125 MW of relief on a Flowgate the IDC will query the existing transactions, MARKET FLOW and available NNL impact on the constrained Flowgate. NonFirm Transactions = 25 MW FirmTransactions = 150 MW MARKET FLOW = 165 MW CA NNL = 315MW The software will determine the overall percentage of impact for each Firm category for the Flowgate. FirmTransactions = Firm 150 = Firm + MarketFlow + NNL = 20% MARKET FLOW = MarketFlow Firm + MarketFlow + NNL = % CA NNL = NNL Firm + MarketFlow + NNL = = 50% The IDC will then assign the subsequent amount of relief to each of the categories and prescribe the curtailments. FirmCurtailments = (Requested Relief) (NonFirm Transactions) = 100 MW Firm Transaction Curtailments = 20MW MARKET FLOW Responsibility = 30MW CA NNL Responsibility = 50 MW 8/10/2005 Page 43 of 43

44 Section TLR Issuance NEXT HOUR Additionally, at the time the TLR 5B is issued or xx:25, whichever is later, the IDC will create a list of FIRM Curtailments for the next hour in an attempt to hold the flowgate loading at the level of the Current Hour Curtailments. Figure 28. Issue TLR 5B This will prompt the IDC software to bring up the Congestion Management Report for the TLR Level 5B. Once the information in the report is reviewed the Confirm button can be selected to send the TLR issuance to the other Reliability Coordinators and the NERC RCIS (See Section for direction Confirming a TLR Issuance). 8/10/2005 Page 44 of 44

45 Section TLR Issuance TLR LEVEL 6 Figure 29. TLR 5B Congestion Management Report This TLR Level is requested by an Operator to declare an Emergency Action on a Flowgate. This TLR will give the operator an indication of any existing Market and Transaction Flow on the selected Flowgate before the TLR Level 6 is issued and broadcasted to the other IDC Users. 8/10/2005 Page 45 of 45

46 Section TLR Issuance The IDC will curtail all NON-FIRM and FIRM transactions to zero by sending a MW Cap request to the Source and Sink Control Areas on the tag. The IDC will curtail the Non-Firm MARKET FLOW impacts (i.e. ED-2 and ED-6) on the Flowgate to zero by sending a Relief Responsibility Request to the RTO. These messages are initiated when the Reliability Coordinator assigned to the Sink of each transaction Acknowledges the MW Cap request and/or Relief Responsibility for the TLR event. Figure 30. Issue TLR 6 Once the TLR Level 6 is designated from the drop down menu the Issue TLR Level 6 button should be selected. 8/10/2005 Page 46 of 46

47 Section TLR Issuance Figure 31. TLR 6 Congestion Management Report This will prompt the IDC software to bring up the Congestion Management Report for the TLR Level 6. Once the information in the report is reviewed the Confirm button can be selected to send the TLR issuance to the other Reliability Coordinators and the NERC RCIS (See Section for directions in confirming a TLR Issuance) CONFIRMING A TLR ISSUANCE (RELEVANT TO ALL TLR LEVELS) Once the Confirm button is selected on the TLR Issuance Congestion Management Report it will bring up a secondary confirmation screen in which the Operator can add comments about the TLR issuance and initiate the final confirmation of the TLR. Once the Confirm button is selected in this TLR Confirmation screen the TLR curtailment and/or reload prescriptions will be sent out to all IDC users and initiate a TLR Event notification on the NERC RCIS and CRC sites. The TLR Event will move from the Pending to Active state in the TLR Log Screen. It is the responsibility of each Sink Reliability Coordinator to Acknowledge all TLR prescriptions in order to initiate the electronic communication of the TLR prescriptions to the appropriate entities. If the acknowledgement does not take place the Control Area entities will not be automatically updated about the upcoming prescriptions. 8/10/2005 Page 47 of 47

48 Section TLR Reloading 4.2 TLR RELOADING Figure 32. Confirm TLR The reloading of a curtailments can occur in a TLR Level 0, 1, 3A, 3B, and 5A. The TLR logic assigns the transaction, MARKET FLOW or NNL responsibility to the appropriate level based on TLR rules and reallocation guidelines. For more information on the IDC Reloading algorithm see the technical appendix Section If the MARKET FLOW for an RTO is prescribed to allow more MWs of flow on a Flowgate in TLR the IDC will indicate the amount of MWs the RTO must change on the Flowgate. The IDC User interface screens will indicate the amount of change the RTO has to implement on the Flowgate in TLR (i.e. Reduce flow by 50 MW or increase flow by 25 MW). The IDC will electronically send the RTO the Net MARKET FLOW cap on the Flowgate (i.e. 850 MW of flow in the positive direction). 5 TECHNICAL APPENDIX The following technical appendices are intended to provide specific detail that is useful to know, but not explicitly required to use the IDC. 8/10/2005 Page 48 of 48

49 Section Zonal TDF Calculations 5.1 ZONAL TDF CALCULATIONS GENERATOR SHIFT FACTORS (GSF) A Generator Shift Factor (GSF) is defined as the change in flow on a transmission facility (or flowgate) due to a 1 MW injection on a given generator and a corresponding 1 MW withdrawal at the swing bus. Figure 33 depicts GSF k i-swing, the GSF of generator i on flowgate k with respect to the swing bus. Figure 33. GSF Graphic The linear model representation of the Eastern Interconnection allows the IDC to apply the principles of superposition, thus enabling to compute shift factors from any two generators. Figure 34 shows GSF k i-j, the change in flow on flowgate k due to a 1 MW increment in generation in generator i and a 1 MW decrement in generation in generator j. Figure 34. TDF Graphic 8/10/2005 Page 49 of 49

50 Section Zonal TDF Calculations TRANSFER DISTRIBUTION FACTOR The Transfer Distribution Factor (TDF) is a generalization of the generator GSFs where all generators in a set increment their total MW output by 1 MW. The amount of generation output of each generator in the set is scaled according to generator weighting factors. The TDFs are mathematically represented by TDF k A = ( Σ i W Ai GSF k Ai ) / ( Σ i W Ai ) W Ai is the weighting factor of generator i in set A, GSF k Ai is the GSF of generator i in set A on flowgate k with respect to the swing bus, and TDF k A is the Transfer Distribution Factor of the set of generators in A on flowgate k, with respect to the swing bus. The weighting factors used in the IDC are determined by the base-case MBASE values. These factors are dynamically adjusted for derated generators. The weighting factor of a generator is a number between 0 and 1. A weighting factor of zero indicates the generator is out of service, or outaged. A weighting factor of 1 indicates the generator is fully operational. Figure 35 depicts a set of generators and their TDF values, which are calculated using the equation below: TDF k A = ( Σ i D Ai W Ai GSF k Ai ) / ( Σ i D Ai W Ai ) D Ai is the derating factor of generator I in set A, provided form the NERC SDX. The IDC computes TDFs for every control area defined in the base case model, which includes NERC registered control areas in the Eastern Interconnection as well as pseudo-control areas used for modeling of phase shifters and DC lines, and special treatment of specific generators that may be tagged individually. In addition to the control area TDFs, the IDC also computes Load Shift Factors (LSF) used in NNL calculations. The IDC calculates the individual load bus shift factors similarly to the GSFs, and the control areas LSFs through the weighted sum of the load bus shift factors. Figure 35. RTO TDF Graphic 8/10/2005 Page 50 of 50

51 Section Zonal TDF Calculations TRANSFER DISTRIBUTION FACTORS FOR RTOS The large footprint RTOs, such as PJM or MISO present additional challenges to the calculation and accurate representation of the TDFs for inter-control area transfers. In any area, the generators that participate in interchange transaction can vary quite often, and the use of semistatic base case MBASE values does not accurately represent the electrical behavior of the system. This becomes a bigger problem when areas are expanded and some interchange transactions become internal to the new area. To address this problem, the IDC has been modified to utilize dynamic weighting factors of market generators through a multi-tier TDF calculation approach. The control areas in the RTO footprint have been partitioned (by the RTOs and the DFWG) into electrically coherent zones, called MARGINAL ZONEs, where each zone consists of a group of generators that have historically behaved similarly under TLR conditions, or have similar GSFs. The IDC computes TDFs for each zone, and computes the RTO control areas TDFs as the weighted sum of the MARGINAL ZONE TDFs. The weighting factors for the MARGINAL ZONEs are dynamic and provided to the IDC every 15 minutes by the RTO. To determine the amount each generator contributes to the total generation in the MARGINAL ZONE, the IDC uses the GENERATOR MOBILITY FACTORs (GMF) multiplied by the MBASE. These GMFs are values between 0 and 1, and are provided to the IDC once a day for individual hours of the day. The following describes the process for calculating the RTO control areas TDFs: 1. Compute the GSFs for each generator in the control area 2. Compute the control areas zonal-tdf: ZTDF n = ( Σ i MF i D i W i GSF i ) / ( Σ i MF i D i W i ) Where: ZTDF n is the zonal-tdf for zone n, MF i is the mobility factor of generator i in zone n, D i is the generator i derating factor, W i is the generator i weighting factor (MBASE), and GSF i is the generator i GSF. 3. Compute the control areas TDF: TDF m = ( Σ n MZF n ZTDF n ) / ( Σ n MZF n ) Where: TDF m is the control area TDF for area m, MZF n is the MARGINAL ZONE factor of zone n, and ZTDF n is the zone n TDF. Figure 36 depicts the zonal breakdown of a control area. 8/10/2005 Page 51 of 51

52 Section Reallocation & Reloading Algorithm Figure 36. Zonal TDF Graphic 5.2 REALLOCATION & RELOADING ALGORITHM REALLOCATION DURING TLR 3A & 5A The NERC Transmission Loading Relief process has been set up to provide equitable curtailment and reload (reallocation) of transactions. During the reallocation process, there are additional priorities (called sub-priorities ) that transactions and MARKET FLOW components are assigned in addition to their OASIS transmission priority. These sub-priorities help the IDC determine in what order transactions should be curtailed/reloaded inside a transmission priority bucket. It is the intent of this section to describe what the sub-priorities are and how they are used in the reallocation process. Please refer to the Interchange Transaction Reallocation During TLR Levels 3a and 5a Reference Document (Version 1, Draft 6) on the NERC web site for a more complete description of the TLR reallocation process. At the time a TLR report is processed, the IDC will use all candidate INTERCHANGE TRANSACTIONS and MARKET FLOW components for REALLOCATION that met the Approved-Tag Submission Deadline for Reallocation plus those INTERCHANGE TRANSACTIONS that were curtailed or halted on the previous TLR action of the same TLR event. The IDC will calculate and present an INTERCHANGE TRANSACTIONS Curtailment list that will include reload and REALLOCATION of INTERCHANGE TRANSACTIONS AND MARKET FLOW COMPONENTS. 8/10/2005 Page 52 of 52