1 / 16

Flowgate Allocation Option Parallel Flow Visualization

Flowgate Allocation Option Parallel Flow Visualization. Business Practices Subcommittee Meeting June 24 - 25, 2010. Flowgate Allocation Process Overview. Allocates the total capacity of the flowgate based on day-ahead and hour-ahead predicted firm usage.

jamesjensen
Télécharger la présentation

Flowgate Allocation Option Parallel Flow Visualization

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Flowgate Allocation OptionParallel Flow Visualization Business Practices Subcommittee Meeting June 24 - 25, 2010

  2. Flowgate Allocation Process Overview • Allocates the total capacity of the flowgate based on day-ahead and hour-ahead predicted firm usage. • Predicted firm usage includes GTL impacts from generators with firm transmission service and firm PTP impacts.  • Day-ahead impacts based on firm reservations, hour-ahead impacts based on firm schedules. • Need to have the set of generators with firm transmission service and the set of firm PTP reservations/schedules for the period under review.

  3. Day-Ahead Flowgate Allocation Process • 24 hourly allocations will be performed to determine firm rights in the forward and reverse directions. • Based on predicted load, topology of the system and transactions. • Load will be reduced for imports to avoid double counting the impact of reservations. • Merit order/block loading files will be used to dispatch generators. • Since hourly allocations only consider firm generators, this does not represent an actual dispatch expected to occur in real-time (ramp rates will not be applied).

  4. Hour-Ahead Flowgate Allocation Process • Will use schedules in place of reservations and will use the latest information on loads and outages to make a next-hour allocation. • Both the day-ahead and the hour-ahead allocations follow a similar process to determine firm allocations assigned to each Aggregate Entity. • Single allocation based on firm GTL and firm PTP impacts down to 0% in the forward and reverse directions. • All Aggregate Entities receive their 5% and greater impacts. • If flowgate is not over-allocated, all Aggregate Entities will receive either a portion or their full impacts down to 0%. • If there is still flowgate capacity remaining, excess capacity will be assigned to all Aggregate Entities on a proportional basis (based on total impacts down to 0%). • To obtain 5% allocations, impacts between 0% and 5% will be removed from the down to 0% allocation. • The higher-of logic will be applied between the day-ahead allocation and the hour-ahead allocation.

  5. Pro-Rata Curtailments - Firm PTP & Firm GTL • When real-time firm GTL impacts and firm PTP impacts exceed the firm allocation, OATI has proposed to make pro-rata curtailments where proportional amounts of firm PTP impacts and firm GTL impacts will be placed into the lowest level of firm bucket to be curtailed during TLR 5. • The following process will be used when real-time firm PTP impacts and firm GTL impacts exceed the firm allocation. • The Aggregate Entities firm allocation from the higher-of process will be compared with the summed hour-ahead GTL impacts and PTP impacts down to 0%. • If the firm allocation is greater than the summed value, there is no pro-rata assignment of curtailments between firm PTP impacts and firm GTL impacts. • If the firm allocation is less than the summed value, the short-fall is made-up by providing a first to be curtailed allocation. • GTL flow in real-time will first be assigned to the Aggregate Entity’s firm allocation bucket and then to its first to be curtailed allocation bucket. Any remaining GTL flows will then be assigned to the highest priority non-firm bucket (6 NN).

  6. Firm Reservation/Schedules Impacts in Allocation Process • For the assignment of reservation impacts in the day-ahead allocation: • Reservations will go through a filtering process to remove duplicate reservations and will then have their impacts split among TSPs on the reservation path. • Where there are multiple TSPs involving a single reservation, there will be a splitting of the impacts among these TSPs. • For the assignment of schedule impacts in the hour-ahead allocation: • Filtering rules are no longer needed because there are no duplicate tags. • Where there are multiple TSPs involving a single tag, there will be a splitting of the impacts among the TSPs. • For the assignment of real-time schedule impacts: • The same splitting of impacts among the TSPs will occur when determine how much firm allocation and first to curtail allocation will be utilized by PTP impacts. • Where an Aggregate Entity does not sell firm transmission service, special arrangements will be made to assign these transmission service impacts to another Aggregate Entity. • Need to have a mechanism to assign impacts from PTP transactions internal to the BA.

  7. Firm GTL Impacts in Allocation Process • Have identified three scenarios if there is not sufficient firm generation to serve the adjusted firm load. If this option is selected, the NAESB BPS will decide which scenario to include. • Scenario 1 (with prioritized order) • Ramp online generation with firm transmission service • Ramp offline non-outage generation with firm transmission service • Curtail load • Scenario 2 (with prioritized order) • Ramp online generation with firm transmission service • Ramp offline non-outage generation with firm transmission service • Ramp generation with non-firm transmission service • Scenario 3 (with prioritized order) • Ramp online generation with firm transmission service • Ramp offline non-outage generation with firm transmission service • Ramp above pmax • Merit order/block loading files will be updated during monthly IDC model updates or with approvals from by IDCWG. • Hourly generator dispatch files can be used but only include generation with firm transmission service usage.

  8. Firm GTL Impacts in Allocation Process – (cont.) • Since the day-ahead and hour-ahead allocations are based on firm GTL impacts, still need to know which generators have firm transmission service usage to make the allocation.

  9. Assumptions • Any generating resources in the EMS model have to be reported. If a generator is in the EMS model it should also be in the IDC model. This will include pseudo-ties. • NERC will approve INT-012-1 requiring intra-BA transactions to be tagged for point-to-point transactions. These transactions will be recognized by the IDC and subject to curtailment based on the tag transmission service priority and will not be included in the gen-to-load impacts.

  10. Benefits/Drawbacks • Benefits • Provides a better overall economic solution to congestion management in that once firm allocations have been established, can use either firm or non-firm generation to serve load without risk of curtailment during TLR 3 as long as do not exceed firm allocation. • No longer have an issue of not receiving credit for firm redispatch or not receiving credit for redispatch that was done for a first TLR event once you have a second TLR event. • Treat firm GTL flows and firm PTP impacts on an equal basis and does not make one subordinate to the other. • Does not disrupt the priority of firm PTP service in that it still does not get curtailed until a TLR 5 is issued. • Reduces the effects of non-jurisdictional entities that classify all of its generation as firm. With an allocation process, some of that generation having firm transmission service may now be classified as first to be curtailed firm service (even on the non-jurisdictional entity’s own flowgates).

  11. Benefits/Drawbacks • Drawbacks • Requires additional change orders for impact calculation and allocation calculation. OATI already has significant experience doing both. • There is no requirement for non-FERC jurisdictional entities in the Eastern Interconnection to follow the NAESB business practices. • NERC has not yet committed to implement Change Order 310, secured funding or established an implementation timeline. • INT-012-1 has not been approved. • A situation can occur where an Aggregate Entity with only generation that has firm transmission service finds that some of its GTL flows are non-firm. This could be caused by the load forecast and merit order/block loading file used in the hour-ahead allocation calculation and not due to GTL impacts being treated subordinate to PTP impacts. Also, the decision on how we will determine GTL impacts when we run out of generation with firm transmission service in the impact calculation of the allocation process (see Outstanding Issue 3 below) will affect the size of the firm GTL impacts down to 0% and the first to be curtailed firm allocation for GTL flows.

  12. Outstanding Issues • Firm PTP reservations internal to the BA will have their impacts determined in the day-ahead allocation process. How do we determine these impacts if the reservation granularity is at the BA level. • A question has been raised on the load/generation adjustments that are needed for import/export transactions. Need to run through an example that shows there is no double counting. • We have three scenarios that describe what to do when do not have enough generation with firm transmission service to serve adjusted load during the impact calculation of the allocation process. If this option is selected the NAESB BPS will need to reach agreement of which scenario will be applied. • We still have to resolve any issues on when NYISO and IESO schedules are available for the day-ahead and hour-ahead allocations (these two entities do not have firm transmission service reservations). Also need to check on when day-ahead firm reservations are available for all other entities. • Is there still a need to have Midwest ISO and PJM assigned 100% of reservation/schedule impacts involving IESO and NYISO, respectively?

  13. Outstanding Issues - (cont.) • Study Criteria needs to be developed to establish firm transmission usage of generators that will be used in the allocation process.

  14. Other Issues • TVA Issues • I think we should include an explanation of what exactly would happen when a TLR 5 is called. I think it would provide useful clarification. • When assigning allocations down to 0%, if I am an entity with 3% impact will I get any allocation? • If I am reciprocally coordinated on a FG due to one unit with >5% impact, am I required to provide relief on that FG if in real-time I don’t have any Gens online that impact >5%?  (This needs to be stated in the document.) • NYISO Issues • What happens when PJM/MISO schedules do not match firm transmission sold? For example, MISO receives a GTL allocation of 200MWs and a P2P allocation of 300MWs (due to firm reservations) on a NYISO flowgate, then only 100MWs of P2P schedules come in RT, where does the extra 200MWs of P2P allocation go?

  15. Other Issues – (cont.) • NYISO Issues – cont. • If this is the logic, then the Day Ahead is no longer a back stop, but is required for the higher of logic. If the Day Ahead was a back stop, then Hour Ahead would always be used unless it wasn’t available, and then the Day Ahead would be used. • Who are the ‘other entities’? Need to describe them. • Are we proposing to use the Generation Priority Method to fill this gap? • If a non-jurisdictional (or any) entity chooses not to follow this standard (assuming it is the one that is voted for), does that entity receive zero allocation, and therefore all of their GTL is non-firm?

  16. Questions ?

More Related