ENTERGY SERVICES, INC
OPEN ACCESS TRANSMISSION TARIFF
BUSINESS PRACTICES
Updated December 26, 2012
The following provides additional detail relative to Transmission Service under the Entergy Open Access Transmission Tariff presently filed with FERC.
The Entergy Transmission Security Center's (TSC) goal is to blend the sale of transmission services and interconnection reliability while promoting the security of the Eastern Interconnection as a prime importance.
Historical revisions to these Business Practices are available on Entergy’s Special Notices page: http://www.oasis.oati.com/woa/docs/EES/EESdocs/special2.html.
1. Relationship to Transmission Provider’s Open Access Transmission Tariff
II. TRANSMISSION SERVICE PRODUCTS
1.1. Long-Term Firm Transmission Service
1.2. Short-Term Firm Transmission Service
2. Non-Firm Transmission Products
2.1. Monthly Non-Firm Transmission Service
2.2. Weekly Non-Firm Transmission Service
2.3. Daily Non-Firm Transmission Service
2.4. Hourly Non-Firm Transmission Service
3.2. Rates, Terms, and Conditions
III. TRANSMISSION RATES AND PAYMENT
2. Non-Firm Transmission Rates
3. Posted Rates Do Not Include Ancillary Services or Losses
IV. GENERAL RESERVATION/SCHEDULING PRACTICES
1. Practices for Submitting and Responding to TSRs
3. Requirements For Submitting Schedules
4. Arranging for Emergency Assistance
6.2. Preemption Actions After Capacity is Granted to the Challenger
6.3. Preemption Actions After Confirmation of the Challenger
V. POINT-TO-POINT TRANSMISSION SERVICE
1. General Practices Related to PTP Service
3.1. Modifications to PTP Service
3.2. Modification of PTP Service On A Firm Basis
3.3. Modification of PTP Service On A Non-Firm Basis
VI CONDITIONAL FIRM SERVICE AND PLANNING REDISPATCH SERVICE
2. Conditional Firm Transmission Service
3. Planning Redispatch Service
3.1. Planning Redispatch Service From Transmission Provider Resources
3.2. Planning Redispatch Service From Third-Party Provider Resources
4. Limitations on Availability
5. Conditional Firm Service and Planning Redispatch Service TSR Application and Study Process
5.1. Execution of the System Impact Study Agreement
5.2. Tender of the System Impact Study and Customer Options
5.3. Management of Conditional Firm Service/Planning Redispatch Service Options on OASIS
5.4. Following Tender of the FS
VII. NETWORK INTEGRATION TRANSMISSION SERVICE
1. Interim Procedures For Providing Attestations For Network Resources
2. Procedures for Notifying ICT of Changed Circumstances
3. Interim Procedures for Undesignating Network Resources
Non-Simultaneous Undesignation Requests
Priority Rights and Capacity Release (Simultaneous Requests)
3.1. Undesignation of a Short-Term Network Resource
3.2. Undesignation of a Long-Term Network Resource
3.3. Evaluation of Long-Term Request Coupled with a Related Request for Transmission Service
3.4. Requests Subject to the AFC Process
4. Requesting Network Service from an NRIS Generator
4.1. Identifying NRIS-Qualified Generators
4.2. Long Term Requests for Network Service from an NRIS-qualified Generator
4.3. Short Term Requests for Network Service from an NRIS-qualified Generator
5. Removing Conditions from Long Term Network Service
1. Software Applications Used in AFC Process
2. Frequency of Resynchronizations
3. Submission Of Load and Generation Forecast Data for Operating and Planning Horizons
4. Submission Of Generation Forecast Data for the Study Horizon
4.1. Network Customers/LSEs that do not own generation capacity equal to or in excess of their load
4.2. LSEs/Network Customers with generating capacity equal to or in excess of their Network Load
5. Generating Facility Operating Characteristics
6. Transmission Projects Not Currently-In Service
7. Zonal Import Limits (Study Horizon)
8.1. Operating and Planning Horizons
9. Maintaining Sources and Sinks
9.2. AFC Source Maintenance Methodology
9.2.1. New Generator Interconnection
9.2.2. New Embedded or External Control Area (Excluding Control Areas with no Generating Resources)
9.2.3. Modifications to Source Definitions
9.2.4. Removal of Active Source from the AFC Process
9.3. AFC Sink Maintenance Methodology
9.3.1. New Transmission Customer
9.3.2. Existing Transmission Customer
9.3.3. New Load-Only Control Area
9.3.4. Modifications to External Sink Definitions
9.3.5. Removal of Active Sink from the AFC Process
10. Subsystem Definition and Participation Factor Calculation Methodology
11. OATT Attachment C Business Practice Cross References
1. Information Regarding Denials of Service
2. Information Supporting Reason for Denials of Service
3. Data Used to Calculate AFC Values
4. System Impact and Facilities Studies
6. List of Other AFC-Related Information Posted on OASIS
7. Transmission Facility Ratings Methodology
7.3. Transmission Line Rating Methodology
7.5. Transmission Line Equipment Rating Methodology
7.6. Transmission Substation Rating Methodology
7.7. Power Transformer Rating Methodology
7.8. Transmission Reactive Equipment Rating Methodology
ATTACHMENT 1 Examples of Loss Compensation
ATTACHMENT 2 List of AFC Software Applications
TRANSMISSION SERVICE REQUEST BUSINESS PRACTICES
I. GENERAL PROVISIONS
1. Relationship to Transmission Provider’s Open Access Transmission Tariff
These Transmission Service Request (“TSR”) Business Practices (“TSR Business Practices”) contain the standards, rules and business practices the Transmission Provider uses to administer its Open Access Transmission Tariff (“Tariff”). The TSR Business Practices provide additional detail and information that supplements the filed and accepted Tariff. For all Business Practices described herein, the Tariff is the governing document rather than the TSR Business Practices. In the event of a conflict between this document and the Tariff, the Tariff will control, and nothing in this document shall be interpreted to contradict, amend, or supersede the Tariff.
If not otherwise defined herein, all capitalized terms in the TSR Business Practices have the meaning identified in Section 1 of the Tariff and in Attachments C, D, and E to the Tariff.
The TSR Business Practices are subject to Section 4 of the Tariff and Section 5 of the Transmission Service Protocol of Attachment S of the Tariff. Consistent with those provisions, the TSR Business Practices are posted on the public portion of the Transmission Provider’s Open Access Same-Time Information System (“OASIS”) and are located at the following link:
http://www.oasis.oati.com/EES/EESDocs/bus_prac.html.
The North American Energy Standards Board (“NAESB”) business practices relied on by the Transmission Provider are copyrighted. Interested parties may access the copyrighted material as indicated on NAESB’s public website located at http://www.naesb.org/. The Transmission Provider relies on the NAESB WEQ Business Practice Standards specified in Section 4.2 of the Tariff (“NAESB Business Practices”).
As required under Section 4 of the Tariff, the Transmission Provider has developed a transparent process for amending rules, standards, and practices previously contained in the TSR Business Practices included herein. The Transmission Provider follows the amendment procedures specified in Attachment S of the Tariff, at Section 5 of the Transmission Service Protocol as supplemented:
As part of this process, the Transmission Provider provides reasonable notice of any proposed changes to the TSR Business Practices and the respective effective date of such change. Please refer to supplemental procedures at:
http://www.oasis.oati.com/EES/EESDocs/EntergyPractices.html
for additional details on notice, posting, and effective dates. It is the reader’s responsibility to ensure the most recent version posted on the Transmission Provider’s OASIS is being used by the reader.
II. TRANSMISSION SERVICE PRODUCTS
This Section II describes the different Transmission Service products offered by the Transmission Provider under the Tariff. The Transmission Provider offers both Firm and Non-Firm Point-To-Point (“PTP”) Service (“PTP Service”) and Network Integration Transmission Service (“Network Service”) under terms and conditions that are consistent with NAESB Business Practices (WEQ-001). Please see Attachments C and D of the Tariff for a description of the study processes that the Transmission Provider applies when evaluating TSRs for PTP Service and Network Service.
The Transmission Provider offers Firm PTP Service in yearly, monthly, weekly, and daily increments and Network Service in yearly, monthly, weekly, daily, and hourly increments. All increments of Network Service are considered Long-Term Firm Transmission Service for purposes of the evaluation of Transmission Service availability and “bumping” priority under Section 13.2 of the Tariff. All TSRs for Firm Transmission Service must be submitted using the Transmission Provider’s OASIS.
1.1. Long-Term Firm Transmission Service
The Transmission Provider offers “sliding” yearly PTP Service and Network Service, which will start at 00:00 on the first date of any calendar month and end at 00:00 on the first date of the same month during the next year, or any year thereafter. All Long-Term Firm Transmission Service is available on a “first-come, first served” basis.
Customers seeking to reserve Long-Term Firm Transmission Service must submit a TSR via the Transmission Provider’s OASIS at least 60 days before the calendar month in which the service sought is to commence. However, as TSRs for Long-Term Firm Transmission Service must be evaluated through the System Impact Study (“SIS”) Process set forth in Attachment D of the Tariff, it is advisable for Customers seeking to reserve Long-Term Firm Transmission Service to submit their TSRs at least 90 days in advance of the calendar month in which the service sought is to commence. Due diligence will be utilized to complete the required SIS for TSRs submitted less than 90 days prior to the start of service; Customers should note that service will not commence until the SIS Process is complete, and that a deposit must be paid to the ICT for completion of all required Studies, any unused portion of which shall be returned to the customer at the conclusion of the study.
Please see Sections 19 and 29 of the Tariff, as well as Attachment E, for a more detailed description of the information that must be included in a TSR for Long-Term Firm Transmission Service and the processes that will apply when a TSR is incomplete or deficient.
Once a Completed Application has been received and the Independent Coordinator of Transmission (“ICT”) has tendered the SIS report to the Customer, the ICT will respond to the Customer with: (i) an acceptance; (ii) a counteroffer for partial service; or (iii) if no service is available, a Facilities Study Agreement (“FS Agreement”), issued to the Customer within 30 days of tendering the SIS Report, if the Customer has not withdrawn the request. If the FS Agreement is not executed by the Customer and returned to the ICT within 15 calendar days of its issuance, the TSR will be DECLINED. In accordance with NAESB Business Practice Standards WEQ001-4.13 Table 4-2, if an ACCEPTED TSR was not pre-confirmed, or for a COUNTEROFFERED TSR, the Customer must CONFIRM or WITHDRAW their request within 15 calendar days after receiving a response; otherwise, the request will be deemed WITHDRAWN and the status of the TSR on OASIS will be changed to RETRACTED.
Once a TSR has been ACCEPTED by the ICT and CONFIRMED by the Customer, that Customer can schedule for less than the term of the Reservation; however, such Customers will be required to pay for the entire term of the confirmed Reservation.
1.2. Short-Term Firm Transmission Service
1.2.1. Monthly Firm Transmission Service
The Transmission Provider offers “fixed” monthly Firm PTP Service and Network Service. This service starts at 00:00 on the first date of a calendar month and stops at 24:00 on the last date of the same calendar month (same as 00:00 of the first date of the next consecutive month). When requesting these services, the service duration may be in monthly increments, but the total Reservation duration must be 11 months or less.
Customers seeking to reserve Monthly Firm Service must submit a TSR via the Transmission Provider’s OASIS no later than 12:00 noon the day before the service is to begin. Once a Completed Application has been received, the ICT will respond to the Customer within 30 days with: (i) an acceptance; or (ii) a counteroffer for partial service; or (iii) if no service is available, the TSR will be REFUSED. In accordance with NAESB Business Practice Standards WEQ001-4.13 Table 4-2, if an ACCEPTED TSR was not pre-confirmed, or for a COUNTEROFFERED TSR, Customers must CONFIRM or WITHDRAW their request within 4 calendar days after receiving a response; otherwise, the request will be deemed WITHDRAWN and the status of the TSR on the Transmission Provider OASIS will be changed to “RETRACTED”.
SISs are generally not performed for monthly TSRs. However, a SIS will be performed for monthly TSRs when: (i) the TSR is for Firm PTP Service or to designate a new Network Resource in monthly increments and the service is to take place beyond the horizon for which Available Flowgate Capability (“AFC”) values are calculated through the Transmission Provider’s AFC process (“AFC Process”); or (ii) the AFC Process has denied a short-term TSR and the Customer has requested a SIS to evaluate solely the potential for Transmission System upgrades to increase the applicable AFC values.
Once a TSR has been ACCEPTED by the ICT and CONFIRMED by the Customer, that Customer can schedule for less than the term of the Reservation; however, such Customers will be required to pay for the entire term of the confirmed Reservation.
1.2.2. Weekly Firm Transmission Service
The Transmission Provider offers a “sliding” weekly Firm PTP Service and Network Service. This service starts at 00:00 of any date and stops exactly 168 hours later at 00:00 on the same day of the next week. When requesting weekly service, the service duration can be in weekly increments, but the total Reservation duration must be 3 weeks or less.
Customers seeking to reserve weekly Firm Service must submit a TSR via the Transmission Provider’s OASIS no later than 12:00 noon the day before the service is to begin. Once a Completed Application has been received, the ICT will respond to the Customer within 30 dyas with: (i) an acceptance; or (ii) an offer for partial service; or (iii) if no service is available, the TSR will be REFUSED. In accordance with NAESB Business Practice Standards WEQ001-4.13 Table 4-2, if an ACCEPTED TSR was not pre-confirmed, or for a COUNTEROFFERED TSR, Customers must CONFIRM or WITHDRAW their request within 48 hours after receiving a response; otherwise, the request will be deemed WITHDRAWN and the status of the TSR on the Transmission Provider’s OASIS will be changed to “RETRACTED”.
SISs are generally not performed for weekly TSRs. However, a SIS will be performed for weekly TSRs if the AFC Process has denied a short-term TSR and the Customer has requested a SIS to evaluate solely the potential for transmission system upgrades to increase the applicable AFC values.
Once a TSR has been ACCEPTED by the ICT and CONFIRMED by the Customer, that Customer can schedule for less than the term of the Reservation; however, such Customers will be required to pay for the entire term of the Reservation.
1.2.3. Daily Firm Transmission Service
The Transmission Provider offers “fixed” daily Firm PTP Service and Network Service. The service starts at 00:00 and stops at 24:00 of the same calendar date (same as 00:00 of the next consecutive calendar date). The requested service duration can be in daily increments, but the total Reservation duration must be 6 days or less.
Customers seeking to reserve daily Firm Transmission Service must submit a TSR via the Transmission Provider’s OASIS no later than 12:00 noon the day before the service is to begin. After confirming that the TSR does not contain deficiencies, for TSRs received 24 hours or more ahead of the start time, the ICT will respond within 30 days with: (i) an acceptance; or (ii) an offer for partial service; or (iii) if no service is available, the TSR will be REFUSED. In accordance with NAESB Business Practice Standards WEQ001-4.13 Table 4-2, if an ACCEPTED TSR was not pre-confirmed, or for a COUNTEROFFERED TSR, Customers must CONFIRM or WITHDRAW their request within 24 hours after receiving a response; otherwise, the request will be deemed WITHDRAWN and the status of the TSR on the Transmission Provider OASIS will be changed to “RETRACTED”.
The ICT will make best efforts to respond to a TSR for daily Firm Transmission Service received less than 24 hours ahead of the service start time with: (i) an acceptance; or (ii) an offer for partial service; or (iii) if no service is available, the TSR will be REFUSED. In accordance with NAESB Business Practice Standards WEQ001-4.13 Table 4-2, if an ACCEPTED TSR was not pre-confirmed, or for a COUNTEROFFERED TSR, Customers must CONFIRM or WITHDRAW their request within 2 hours after receiving a response; otherwise, the request will be deemed WITHDRAWN and the status of the TSR on the Transmission Provider OASIS will be changed to “RETRACTED”.
Once a TSR has been ACCEPTED by the ICT and CONFIRMED by the Customer, that Customer can schedule for less than the term of the Reservation; however, such Customers will be required to pay for the entire term of the Reservation.
2. Non-Firm Transmission Products
The Transmission Provider offers Non-Firm PTP Service in monthly, weekly, daily, and hourly increments and as Secondary Network Service. The Customer may reserve a sequential term of service so that the total time period for which the Reservation applies is greater than the initial time period. All requests for the Non-Firm Transmission Service should be submitted over the Transmission Provider’s OASIS.
In accordance with FERC policy, Transmission Provider undertakes no obligation under the Tariff to plan its Transmission System in order to provide sufficient capacity for Non-Firm Transmission Service. Parties requesting Non-Firm PTP Service for the transmission of firm power must recognize that such service is subject to availability and to Curtailment or Interruption under the terms of the Tariff.
2.1. Monthly Non-Firm Transmission Service
The Transmission Provider offers fixed monthly Non-Firm PTP Service. This service starts at 00:00 on the first date of a calendar month and stops at 24:00 on the last date of the same calendar month (same as 00:00 of the first date of the next consecutive month). The requested service duration can be in monthly increments, but the total Reservation duration must be 11 months or less.
Customers seeking to reserve Monthly Non-Firm Service must submit a TSR via the Transmission Provider’s OASIS no earlier than 60 days before the service is to begin and no later than 14:00 day before the service is to begin. Once a Completed Application has been received, the ICT will respond to the Customer with within 2 days: (i) an acceptance; or (ii) an offer for partial service; or (iii) if no service is available, the TSR will be REFUSED. In accordance with NAESB Business Practice Standards WEQ001-4.13 Table 4-2, if an ACCEPTED TSR was not pre-confirmed, or for a COUNTEROFFERED TSR, Customers must CONFIRM or WITHDRAW their request within 24 hours after receiving a response; otherwise, the request will be deemed WITHDRAWN and the status of the TSR on the Transmission Provider’s OASIS will be changed to “RETRACTED”.
Once a TSR has been ACCEPTED by the ICT and CONFIRMED by the Customer, that Customer can schedule for less than the term of the Reservation; however, such Customers will be required to pay for the entire term of the Reservation.
2.2. Weekly Non-Firm Transmission Service
The Transmission Provider offers sliding weekly Non-Firm PTP Service. The service starts at 00:00 of any date and stops exactly 168 hours later at 00:00 on the same day of the next week. The requested service duration may be in weekly increments, but the total Reservation duration must be 3 weeks or less.
Customers seeking to reserve Weekly Non-Firm Service must submit a TSR via the Transmission Provider’s OASIS no earlier than 14 days before the service is to begin and no later than 14:00 day before the service is to begin. As TSRs for Weekly Firm Service are evaluated through the AFC Process, once a Completed Application has been received, within 4 hours the ICT will respond to the Customer with: (i) an acceptance; or (ii) an offer for partial service; or (iii) if no service is available, the TSR will be REFUSED. In accordance with NAESB Business Practice Standards WEQ001-4.13 Table 4-2, if an ACCEPTED TSR was not pre-confirmed, or for a COUNTEROFFERED TSR, Customers must CONFIRM or WITHDRAW their request within 24 hours after receiving a response; otherwise, the request will be deemed WITHDRAWN and the status of the TSR on the Transmission Provider OASIS will be changed to “RETRACTED.”
Once a TSR has been ACCEPTED by the ICT and CONFIRMED by the Customer, that Customer can schedule for less than the term of the Reservation; however, such Customers will be required to pay for the entire term of the Reservation.
2.3. Daily Non-Firm Transmission Service
The Transmission Provider offers fixed daily Non-Firm PTP Service. The service starts at 00:00 and stops at 24:00 of the same calendar date (same as 00:00 of the next consecutive calendar date). The service duration can be in daily increments, but the total Reservation duration must be 6 days or less.
Customers seeking to reserve Daily Non-Firm Service must submit a TSR via the Transmission Provider’s OASIS no earlier than 2 days before the service is to begin and no later than 14:00 day before the service is to begin. As TSRs for Daily Firm Service are evaluated through the AFC Process, once a Completed Application has been received, the ICT will respond to the Customer within 30 minutes with: (i) an acceptance; or (ii) an offer for partial service; or (iii) if no service is available, the TSR will be REFUSED. In accordance with NAESB Business Practice Standards WEQ001-4.13 Table 4-2, if an ACCEPTED TSR was not pre-confirmed, or for a COUNTEROFFERED TSR, Customers must CONFIRM or WITHDRAW their request within 2 hours after receiving a response; otherwise, the request will be deemed WITHDRAWN and the status of the TSR on the Transmission Provider’s OASIS will be changed to “RETRACTED”.
Once a TSR has been ACCEPTED by the ICT and CONFIRMED by the Customer, that Customer can schedule for less than the term of the Reservation; however, such Customers will be required to pay for the entire term of the Reservation.
2.4. Hourly Non-Firm Transmission Service
The Transmission Provider offers a fixed hourly Non-Firm Transmission Service. This service starts at the beginning of a clock hour and stops at the end of a clock hour. The service duration can be in hourly increments, but the total Reservation duration must be 23 hours or less.
Customers seeking to reserve Hourly Non-Firm Service must submit a TSR via the Transmission Provider’s OASIS no earlier than 12:00 noon the day before the service is to begin. The ICT will respond, within 30 minutes assuming that the TSR is received more than 1 hour prior to the time the service is to commence, with: (i) an acceptance; or (ii) an offer for partial service; or (iii) if no service is available, the TSR will be REFUSED. In accordance with NAESB Business Practice Standards WEQ001-4.13 Table 4-2, if an ACCEPTED TSR was not pre-confirmed, or for a COUNTEROFFERED TSR, Customers must CONFIRM or WITHDRAW their request within 30 minutes after receiving a response for service that is requested more than 1 hour from the start of service and within 5 minutes for service that is requested less than 1 hour from the start of service, otherwise, the request will be deemed WITHDRAWN and the status of the TSR on the Transmission Provider’s OASIS will be changed to “RETRACTED”.
The ICT will make best efforts to respond to a TSR for Hourly Non-Firm service received less than 1 hour prior to the commencement of the service.
Once a TSR has been ACCEPTED by the ICT and CONFIRMED by the Customer, that Customer can schedule for less than the term of the Reservation; however, such Customers will be required to pay for the entire term of the Reservation. Note that hourly Non-Firm service is only sold as fixed PTP Service. The Point of Receipt (“POR”) and the Point of Delivery (“POD”) are not changeable.
Customers must indicate all elections for Ancillary Services associated with Transmission Service on the Transmission Provider’s Transmission System on the Transmission Provider’s OASIS.
For Schedules 1 and 2 (the two Ancillary Services that must be taken from the Transmission Provider), Customers need not make a selection as the Ancillary Services Requirement link for each TSR will be pre-populated with “Request,” which indicates that those services will be provided by the Transmission Provider.
For Transmission Service with a POD of “EES,” Customers need not commit to Ancillary Services for Schedules 3 through 6 at the time that they submit a TSR on OASIS. At the time of submission, if the Customer knows how it will meet the Ancillary Service requirements for Schedules 3 through 6 for services sinking into the Transmission Provider’s Control Area, the Customer should indicate those arrangements in the Ancillary Services requirement link in the Customer’s TSR on OASIS. Accordingly, Customers will be prompted to select “Request,” “Future Time,” “Self-Supply,” or “Third Party” Ancillary Services Requirement link for each TSR. Customers must then validate their elections prior to submitting the TSR.
Should a Customer elect any selection of Ancillary Services for Schedules 3 through 6 other than “Request”, documentation of the Customer’s ability to provide such Ancillary Services MUST be provided to the Transmission Provider’s Transmission Services group for inclusion in the Customer’s Transmission Service Agreement (“TSA” or “Service Agreement”). Such arrangements must be completed prior to scheduling service, or all elections will default to Entergy as the provider, and Customers will be billed for Ancillary Services for Schedules 1 through 6.
If elections for Ancillary Services for Schedules 3 through 6 are unknown at the time of the submission of a TSR, the TSR will be accepted subject to confirmation from the Customer that the required ancillary services have been arranged. The Customer must, however, confirm any Ancillary Services on OASIS prior to scheduling on CONFIRMED TSRs. If the Customer fails to confirm arrangement of Ancillary Services prior to scheduling on CONFIRMED TSRs, all elections will default to the Transmission Provider as the provider and Customers will be billed for Ancillary Services for Schedules 1 through 6.
Any alternate arrangements for Ancillary Services for Schedules 3 through 6 that are elected by a Customer, including performance standards and when charges may apply, shall be set forth in the TSA and/or Network Operating Agreement (“NOA”). Customers will be charged for all Ancillary Services unless the Customer has made alternate, comparable arrangements to provide for the Ancillary Services described in Schedules 3 through 6 of the Tariff and such arrangements are explicitly defined in the TSA and/or NOA.
In addition to the rates, terms, and conditions detailed in the Tariff, Customers should be aware of the following concerning Ancillary Services when submitting their TSRs on OASIS:
Schedules 1 and 2: Customers reserving “through” service (i.e., Reservations for service that both enter and exit Entergy’s Control Area) are only required to purchase Schedules 1 and 2 from the Transmission Provider. Customers that are wheeling out of the Transmission Provider’s Control Area need only purchase Schedules 1 and 2 from the Transmission Provider.
Schedule 3 and 5: Schedules 3 and 5 must be provided by the Control Area in which the load resides when the Customer serving that load is purchasing Transmission Service for energy that is generated by ENTERGY/EMO generators or other generators connected to the Transmission Provider’s transmission system, but that energy exits the Transmission Provider’s Control Area in order to serve the load.
Schedules 3 through 6: For Customers within the Transmission Provider’s Control Area that are purchasing energy/capacity from an external resource, Schedules 3 through 6 must be: (1) purchased from the Transmission Provider; (2) arranged for from another Control Area; or (3) self-supplied by the Customer and metered into the Transmission Provider’s Control Area.
3.2. Rates, Terms, and Conditions
Please see the following provisions of the Tariff for an explanation of the rates, terms, and conditions pursuant to which Ancillary Services are offered by the Transmission Provider.
· Schedule 1 - Scheduling, System Control and Dispatch Service
· Schedule 2 - Reactive Supply and Voltage Control From Generation Sources Services
· Schedule 3 - Regulation and Frequency Response Service
· Schedule 4 - Energy Imbalance Service
· Schedule 5 - Operating Reserve-Spinning Reserve Service
· Schedule 6 - Operating Reserve-Supplemental Reserve Service
· Attachment P - Generator Imbalance Service and Generator Regulation Service
III. TRANSMISSION RATES AND PAYMENT
The Customer shall compensate the Transmission Provider each month for reserved Long-Term Firm PTP Service based on the rates posted on OASIS. The Customer will compensate the Transmission Provider for reserved Network Service based on the Customer’s load ratio share as calculated pursuant to Attachment H of the Tariff. Note that the Transmission Service prices posted on OASIS do not include the costs of Ancillary Services or losses (or applicable taxes).
The total maximum charge for hourly service will not exceed the rate for daily service, using the highest amount of hourly service reserved during any hour of the day. Likewise, the maximum charge for daily service will not exceed the rate for weekly service using the highest amount of hourly or daily reserved in any hour during the week.
PTP Service Customers are subject to a 1.03 loss factor and Network Customers are responsible for losses as agreed-upon in their respective NOAs.
2. Non-Firm Transmission Rates
Customers shall compensate the Transmission Provider each month for reserved Non-Firm PTP Transmission Service based on the rates posted on OASIS. Secondary Network Service can be taken on an “as-available” basis, at no additional charge upon the rate paid by the Customer under Attachment H.
The total maximum charge for hourly service will not exceed the rate for daily service using the highest amount of hourly service reserved during any hour of the day. Likewise, the maximum charge for daily service will not exceed the rate for weekly service using the highest amount of hourly or daily service reserved in any hour during the week.
PTP Service Customers are subject to a 1.03 loss factor and Network Customers are responsible for losses as agreed-upon in their respective NOAs.
3. Posted Rates Do Not Include Ancillary Services or Losses
Please note that the Transmission Service prices posted on OASIS do not include the costs of Ancillary Services or losses (or applicable taxes). Under FERC policy, two Ancillary Services must be taken from the Transmission Provider: (i) Scheduling, System Control and Dispatch Service; and (ii) Reactive Supply and Voltage Control from Generation Sources Services. The rates for these Ancillary Services are stated in Schedules 1 and 2 of the Tariff.
Please see Section II.3 above and the following provisions of the Tariff for an explanation of the rates, terms, and conditions pursuant to which Ancillary Services are offered by the Transmission Provider:
· Schedule 1 - Scheduling, System Control and Dispatch Service
· Schedule 2 - Reactive Supply and Voltage Control From Generation Sources Services
· Schedule 3 - Regulation and Frequency Response Service
· Schedule 4 - Energy Imbalance Service
· Schedule 5 - Operating Reserve-Spinning Reserve Service
· Schedule 6 - Operating Reserve-Supplemental Reserve Service
· Attachment P - Generator Imbalance Service and Generator Regulation Service
Currently, the Transmission Provider does not offer discounts on its offered Transmission Services. The prices are as posted on the Transmission Service Rates page on OASIS.
Losses occur when the Transmission Provider delivers electricity across its transmission facilities for a Customer. PTP Service Customers are subject to a 1.03 loss factor arithmetically rounded to the nearest whole MW. All PTP transactions require losses regardless of the accumulated energy amount. Network Customers are responsible for losses as agreed-upon in their respective NOAs. Attachment 1 to these business practices provides examples of how the Transmission Provider will address losses for Network Service or PTP Service provided under the Tariff. Responsibility for losses is governed by Sections 15.7, 28.5, Schedules 7 and 8, and Attachments E and H of the Tariff.
Uncreditworthy Customers must follow the procedures described in this Section III.7 when prepaying for Transmission Service in accordance with Section 11.3 and Attachment L of the Tariff. Transmission Provider’s prepayment process assumes that a valid TSR is one that has been ACCEPTED by the ICT and CONFIRMED by the Customer.
The Transmission Provider is unable to accommodate Daily Non-firm and Hourly Non-firm service under the FERC approved prepayment provisions. For all other services, a minimum of 30 days notice of the election of prepayment status is required, and the election must be made on a calendar-month basis. Upon election of prepayment status, the Customer must immediately provide the following information to the Transmission Provider’s Transmission Services group in order to facilitate the necessary exchange of invoice data and remittance of funds: (i) phone number; (ii) fax number; (iii) primary contact name, and (iv) email address.
Any outstanding Transmission Service charges, including charges for the current month’s service, will be invoiced at the end of the current month pursuant to the normal Transmission Service customer billing cycle.
Prepayment charges must be paid by the due date, which will be the earlier of the normally calculated due date or five (5) business days prior to the beginning of the next month. If the prepayment is not received by the invoice due date, the Reservation will be ANNULED. Payments made after the Reservation has been ANNULED will be refunded without interest.
For Reservations of a month or less and for the initial month of monthly Transmission Service, the invoice due date for prepaid Transmission Service will be 2 business days following the date of the invoice and no later than 5 business days prior to the start of service. For subsequent months of pre-paid monthly Transmission Service, the invoice due date will be 5 business days prior to the beginning of each month.
Prepayment invoices will reflect an estimated charge for Ancillary Services Schedules 1 and 2. Variance between the estimate and actual charges (including any applicable price cap credits, Transmission Loading Relief (“TLR”) credits, penalties, and interest) will be reconciled at the end of the month. Interest on prepayments will be calculated, based on 18 CFR 35.19a(a)(2)(iii), from the date payment is received until the earlier of the end date of the Reservation or the end of the month. Interest due to the Customer will be calculated at the end of the month.
In accordance with Section 11.4 of the Tariff, the Transmission Provider may suspend Transmission Service if the Customer fails to provide financial assurances in accordance with Section 11.3 of the Tariff. Suspension of Transmission Service means, once the Transmission Provider has notified the ICT, all CONFIRMED Reservations will be RECALLED and associated capacity will be returned to the market.
Once the Transmission Provider has suspended Transmission Service, all new TSRs submitted by a suspended Customer will be DECLINED by the ICT on OASIS until the Customer’s financial assurance requirements are met. The suspension of service shall continue only for as long as the circumstances that entitle the Transmission Provider to suspend service continue.
The Transmission Provider will manage suspension of service on a weekly basis to allow the suspended capacity to be returned to the market. Service suspended on or after Monday of any week will not be restored until the next Monday following the time the Transmission Customer’s financial assurance requirements are met. If a Customer wishes to have its capacity restored during the week of its suspension, it must submit a new TSR on the Transmission Provider’s OASIS after providing the required financial assurance. The ICT will ACCEPT the new TSR only if capacity is available. Once the Transmission Provider has suspended Transmission Service, reservations of greater than one week will be RECALLED by the ICT on OASIS for the balance of the current week and on a weekly basis until the Customer provides the required financial assurance.
For Customers not in default, the Transmission Provider will wait thirty-five (35) calendar days after providing written notice of the need to provide financial assurances before suspending service. For Customers in default, the Transmission Provider will wait five (5) business days after providing a Customer written notice of the need to provide financial assurances before suspending service. Prior to suspending service, the Transmission Provider will provide five (5) calendar days written notice to the Commission.
The Transmission Customer will not be billed for Transmission Service that has been suspended for failure to provide the required financial assurance.
IV. GENERAL RESERVATION/SCHEDULING PRACTICES
1. Practices for Submitting and Responding to TSRs
1.1 The time limits for Customers to submit and confirm TSRs and for the Transmission Provider to evaluate such TSRs are contained in the NAESB Business Practices, to the extent applicable, and otherwise defined in these TSR Business Practices.
1.2 When a short term TSR begins within the model horizon for the AFC process, and extends beyond the model horizon for the AFC process, the TSR will automatically be counteroffered for the amount available as firm within the AFC model horizon. The customer has the following options in responding to the counteroffer:
1.2.1 Accept the Counteroffer, and if desired, submit a new TSR for the portion beyond the AFC horizons for evaluation under the SIS Process
1.2.2 Contact the ICT TA desk to coordinate the submission of a request for study under OATT Attachment D.
1.2.3 Withdraw the Counteroffer
In accordance with FERC Order 676e, Entergy’s OASIS website will utilize the REBID functionality.
For a Transmission Reservation in ACCEPTED or COUNTEROFFER status, the Transmission Customer may CONFIRM, DECLINE, or REBID a Transmission Service Request. This functionality allows the Transmission Customer the opportunity to change capacity only.
Entergy’s Tariff Rate is non-negotiable, and represents the prevailing FERC Filed Transmission Service Rate. Therefore, Entergy’s OASIS will not utilize functionality to allow a Transmission Customer to rebid on price. All fields populated by the customer for price must reflect that of the appropriate prevailing Tariff Rate for the Transmission Service requested.
3. Requirements For Submitting Schedules
Entergy Transmission implemented a program that updates the posted numbers for non-firm ATC based on actual schedules received on firm reservations during the Operating Horizon. The Operating Horizon currently begins at 4:00 P.M. each day for the upcoming day. The program ingests NERC E-tags as they are implemented and updates the non-firm ATC figures accordingly. These updates usually occur within five minutes from when the E-tag is implemented. Entergy allows for the release of unscheduled ATC held under firm reservations to the non-firm market as follows:
· The Planning Horizon for a given day is defined as anytime before Noon on the prior day. The Operating Horizon for a given day will begin at Noon on the prior day.
· In the Planning Horizon, non-firm ATC will be equal to the TTC less all OASIS reservations.
· In the Operating Horizon, posted non-firm ATC numbers will be equal to the TTC less schedules under firm reservations and less non-firm reservations.
· Entergy will not release any non-firm capacity held under firm reservations until the Operating Horizon.
Entergy has chosen Noon prior day as the beginning of the Operating Horizon in order to make additional non-firm ATC available to the market when Daily Non-Firm as well as Hourly Non-Firm capacity can be purchased. Entergy will continue the practice of accepting schedules under firm reservations up to twenty minutes prior to the start of the schedules. However, please be aware that this increases the chance that non-firm schedules may be curtailed as firm schedules are submitted. Curtailments of non-firm transmission service will be based on NERC curtailment priorities.
Sections 4.1 and 4.2 of Attachment E describe the requirements related to scheduling service and the practices related to changes in PODs/PORs and Sources/Sinks
4. Arranging for Emergency Assistance
Section 4.3 of Attachment E describes the requirements related to arranging for Emergency Assistance.
Requests to exercise “rollover” rights under Section 2.2 of the Tariff for the continuation of Firm PTP Service and Network Service must be submitted over OASIS with a request type of “RENEWAL.” Rollover requests must be submitted in accordance with the Tariff, these Business Practices and all applicable NAESB Business Practices. Any request to change PORs or PODs for a Reservation for PTP Service must be requested separately from rollover requests and will be studied as a new TSR pursuant to Section 22.2 of the Tariff. Requests for renewal generally will not be restudied, subject to the exceptions described in Attachment D of the Tariff.
This Section IV.6 describes the Transmission Provider’s implementation of the provisions of its Tariff that govern Reservation Priority (Sections 13.2 and 14.2) when competing bids for constrained resources on the Transmission Provider’s transmission system (“Preemption”) are submitted through the AFC Process. The Transmission Provider’s implementation of Preemption also applies the NAESB Business Practices. All actions described below are actions taken via OASIS, unless specifically noted otherwise.
Each valid TSR is evaluated in accordance with FERC policies, represented in NAESB Business Practices (WEQ 001-4.16 through 001-4.25 Table 4-3, “Priorities For Competing Requests”), and Sections 13.2 and 14.2 of the Tariff, as applicable.
Preemption evaluations will be conducted in all TSR evaluations where AFC is insufficient to ACCEPT the TSR. All preemptable TSRs or Reservations of lower priority (“Defenders”) submitted for evaluation through the AFC process will be identified by the OATI software, unless such Reservation is subject to unconditionality and has become unconditional as defined in Section 13.2 of the Tariff. The OATI software will provide the ICT with an evaluation of the request, which identifies the capacity of all Defenders that are necessary to accommodate the TSR being evaluated for acceptance (“Challenger”) and the specific actions to be taken by the ICT to manage the competition. In order to be identified as a valid Challenger, a TSR must be Preconfirmed. For preemption processing purposes, priority will be determined by the number of segments with a non-zero MW Available value. Non-Firm Redirects will not impact the priority of the parent. The ICT will determine whether the Challenger can be ACCEPTED or COUNTEROFFERED based on the OATI software evaluation. When the Challenger is pre-confirmed, and no right-of-first-refusal (“ROFR”) exists on one or more Defenders, the Challenger will be ACCEPTED or COUNTEROFFERED (where preemption of the Defender will improve the counteroffer), and Preemption actions will be taken as appropriate. If the Challenger was COUNTEROFFERED, the Challenger will then have the opportunity to CONFIRM the service during the confirmation time limit. When the Challenger is not pre-confirmed, the ICT will ACCEPT the Challenger or extend a counteroffer to the Challenger, noting the terms of the offer in the seller comment field. The Challenger will then have the opportunity to CONFIRM the service offered within the confirmation time limit. Once an evaluation is selected for processing a TSR the ICT is not obligated to consider subsequent evaluations. The ICT may take any actions which are not indicated by the OATI software, should the evaluation be inconsistent with NAESB or OATT standards.
6.2. Preemption Actions After Capacity is Granted to the Challenger
When the Challenger has been ACCEPTED or COUNTEROFFERED (where preemption of the Defender will improve the counteroffer), preemption actions will be taken as appropriate. If the Challenger was COUNTEROFFERED, the Challenger will have the opportunity to CONFIRM the service during the confirmation time limit.
At the time the Challenger is ACCEPTED or COUNTEROFFERED, where Defenders are still pending, the ICT will initiate preemption, and the OATI software will SUPERSEDE Defenders as required to accommodate the Challenger. The OATI software will indicate the Assignment Reference (“ARef”) of the Challenger in the seller comments to the Defender(s).
6.3. Preemption Actions After Confirmation of the Challenger
When Defenders are ineligible for the ROFR, the ICT will initiate preemption, and at the time the Challenger is CONFIRMED, the OATI software will RECALL partial or full capacity from the Defenders to accommodate the Challenger. The Challenger’s ARef will be indicated in the seller comments of the Recall TSRs impacting the Defender(s), and in the seller comments of the Defender TSRs.
When any Defender is eligible for ROFR, the ICT will initiate preemption and, at the time the Challenger is CONFIRMED, the OATI software will RECALL partial or full capacity from the Defenders to accommodate the Challenger. The Challenger’s ARef will be indicated in the seller comments of the Recall TSR(s) impacting the Defender(s) TSR and in the seller comments of the Defender TSR(s). At the time the Challenger is CONFIRMED, the OATI software will simultaneously extend the ROFR to those Defenders which are eligible for ROFR, by setting the Competing Request Flag on the Defenders, and submitting Matching TSRs on behalf of the Defender TSRs. In order to accommodate scheduling deadlines of both the Challenger and the Defender, Defenders have the lesser of: (i) the Customer Confirmation Time Limit defined in the NAESB Business Practices (Table 4-2, Reservation Timing Requirements); or (ii) 24 hours, to CONFIRM the Matching TSR(s) submitted by the OATI software.
When the first Match is received from CONFIRMED by any Defender, the Challenger’s capacity will be RECALLED in part or full, as the Defender’s Match assumes the highest priority. Where a Challenger is RECALLED in part or full due to a Match, the OATI software will update the Seller Comments on the Recall TSR to indicate that the Recall was submitted to accommodate the Matching TSR. Any remaining capacity on the Defender TSR will be RECALLED in full, and the OATI software will update the Seller Comments on the Recall TSR to indicate the Recall was submitted to accommodate the Matching TSR. After receipt of the first Match, subsequent Matches will be evaluated by the OATI software for feasibility. The OATI software will set the status of any Matching TSRs that can no longer be supported by setting the status of the Matching TSR to DISPLACED after customer CONFIRMATION.
Customers whose Reservations, excluding Redirects, are RECALLED for some, but not all, of their MW capacity may contact the ICT (at the Tariff Administration Desk) at 317-249-5037 to request annulment or levelization of the profile of the affected Reservation. All such communications MUST occur prior to the scheduling deadline for the affected service. Any requests for annulment or levelization of the profile of the affected Reservation conveyed to the ICT AFTER the scheduling deadline will be accommodated by the ICT, when practicable.
Customers whose Redirect Reservations are RECALLED for some, but not all, of their MW capacity may contact the ICT (at the Tariff Administration Desk) at 317-249-5037 to request an additional Recall to zero out capacity or levelization of the profile of the affected Reservation. All such communications MUST occur prior to the scheduling deadline for the affected service. Any requests for an additional recall to zero out capacity or levelization of the profile of the affected Reservation conveyed to the ICT AFTER the scheduling deadline will be accommodated by the ICT, when practicable.
Once notified of a Competition or Preemption, Defenders may not redirect to avoid being preempted. Where a Defender is redirected or resold after notification, the Original and Redirect/RESALE capacities will be RECALLED in part or full, as required to accommodate the Challenger.
To adequately respect timing requirements set forth in the NAESB Business Practices and the Tariff, the Transmission Provider will not commence any Preemption process unless the submission time of the Challenger (prior to its start time) exceeds a time period that includes the Defender’s unconditional time period, any time period in which ROFR is to be exercised, and the time period of the Customer confirmation time limit. See Table 5-1. More specifically, preemption with the ROFR will NOT occur if any of the aforementioned time limitations would be violated.
TABLE 5-1
|
Challenger Service |
Defender Service |
Challenger Queued In Advance Of The Start Time Of Defender |
|
|
|
|||
|
Tier 1 Services - Short-Term Firm Network |
|||
|
FIRM MONTHLY NETWORK |
FIRM MONTHLY PTP |
35 |
Day(s) |
|
|
FIRM WEEKLY PTP |
11 |
Day(s) |
|
|
FIRM DAILY PTP |
5 |
Day(s) |
|
FIRM WEEKLY NETWORK |
FIRM MONTHLY PTP |
33 |
Day(s) |
|
|
FIRM WEEKLY PTP |
9 |
Day(s) |
|
|
FIRM DAILY PTP |
3 |
Day(s) |
|
FIRM DAILY NETWORK |
FIRM MONTHLY PTP |
32 |
Day(s) |
|
|
FIRM WEEKLY PTP |
8 |
Day(s) |
|
|
FIRM DAILY PTP |
2 |
Day(s) |
|
Tier 2 Services - Short Term Firm PTP |
|
|
|
|
FIRM MONTHLY PTP |
FIRM MONTHLY PTP |
36 |
Day(s) |
|
|
FIRM WEEKLY PTP |
12 |
Day(s) |
|
|
FIRM DAILY PTP |
6 |
Day(s) |
|
FIRM WEEKLY PTP |
FIRM WEEKLY PTP |
10 |
Day(s) |
|
|
FIRM DAILY PTP |
4 |
Day(s) |
|
FIRM DAILY PTP |
FIRM DAILY PTP |
3 |
Day(s) |
|
Tier 3 Services - Non-Firm Network |
|
|
|
|
NF MONTHLY NETWORK |
NF MONTHLY PTP |
25 |
Hour(s) |
|
|
NF WEEKLY PTP |
25 |
Hour(s) |
|
|
NF DAILY PTP |
25 |
Hour(s) |
|
|
NF HOURLY PTP |
25 |
Hour(s) |
|
|
NF HOURLY REDIRECT |
24 |
Hour(s) |
|
NF WEEKLY NETWORK |
NF MONTHLY PTP |
25 |
Hour(s) |
|
|
NF WEEKLY PTP |
25 |
Hour(s) |
|
|
NF DAILY PTP |
25 |
Hour(s) |
|
|
NF HOURLY PTP |
25 |
Hour(s) |
|
|
NF HOURLY REDIRECT |
24 |
Hour(s) |
|
NF DAILY NETWORK |
NF MONTHLY PTP |
3 |
Hour(s) |
|
|
NF WEEKLY PTP |
3 |
Hour(s) |
|
|
NF DAILY PTP |
3 |
Hour(s) |
|
|
NF HOURLY PTP |
3 |
Hour(s) |
|
|
NF HOURLY REDIRECT |
3 |
Hour(s) |
|
NF HOURLY NETWORK |
NF MONTHLY PTP |
2 |
Hour(s) |
|
|
NF WEEKLY PTP |
2 |
Hour(s) |
|
|
NF DAILY PTP |
2 |
Hour(s) |
|
|
NF HOURLY PTP |
2 |
Hour(s) |
|
|
NF HOURLY REDIRECT |
1 |
Hour(s) |
|
NF DAILY TSUSD |
NF MONTHLY PTP |
3 |
Hour(s) |
|
|
NF WEEKLY PTP |
3 |
Hour(s) |
|
|
NF DAILY PTP |
3 |
Hour(s) |
|
|
NF HOURLY PTP |
3 |
Hour(s) |
|
|
NF HOURLY REDIRECT |
2 |
Hour(s) |
|
NF HOURLY TSUSD |
NF MONTHLY PTP |
2 |
Hour(s) |
|
|
NF WEEKLY PTP |
2 |
Hour(s) |
|
|
NF DAILY PTP |
2 |
Hour(s) |
|
|
NF HOURLY PTP |
2 |
Hour(s) |
|
|
NF HOURLY REDIRECT |
1 |
Hour(s) |
|
Tier 4 Services - Non-Firm PTP |
|
|
|
|
NF MONTHLY PTP |
NF MONTHLY PTP |
49 |
Hour(s) |
|
|
NF WEEKLY PTP |
49 |
Hour(s) |
|
|
NF DAILY PTP |
27 |
Hour(s) |
|
|
NF HOURLY PTP |
26 |
Hour(s) |
|
|
NF HOURLY REDIRECT |
24 |
Hour(s) |
|
NF WEEKLY PTP |
NF WEEKLY PTP |
49 |
Hour(s) |
|
|
NF DAILY PTP |
27 |
Hour(s) |
|
|
NF HOURLY PTP |
26 |
Hour(s) |
|
|
NF HOURLY REDIRECT |
24 |
Hour(s) |
|
NF DAILY PTP |
NF DAILY PTP |
5 |
Hour(s) |
|
|
NF HOURLY PTP |
4 |
Hour(s) |
|
|
NF HOURLY REDIRECT |
2 |
Hour(s) |
|
NF HOURLY PTP |
NF HOURLY PTP |
2 |
Hour(s) |
|
|
NF HOURLY REDIRECT |
1 |
Hour(s) |
|
|
|
|
|
V. POINT-TO-POINT TRANSMISSION SERVICE
1. General Practices Related to PTP Service
TSRs for Firm Transmission Service for next day business must be queued in the Transmission Provider’s OASIS by 12:00 PM CPT current day. TSRs for Daily Non-Firm Transmission Service must be queued into the Transmission Provider’s OASIS by 2:00 PM.
The Transmission Provider’s OASIS requires that the Customer specify the POR and POD. Source and Sink information must be provided in accordance with the requirements of Attachment M of the Tariff. Current lists of valid Sources and Sinks on the Transmission System are posted on the Transmission Provider’s OASIS at the following link:
http://www.oasis.oati.com/EES/EESDocs/SourceSinkPractices.html
The amount of transmission capacity specified at the POR in a Reservation applies for the entire time period reserved. The amount of transmission capacity actually scheduled does not have to equal the amount of reserved transmission capacity; however, the amount of transmission capacity scheduled cannot exceed the actual amount of reserved transmission capacity.
Charges for PTP Service are based on the amount of transmission capacity reserved at the POR, as indicated in the Reservation. Invoiced charges will not be adjusted as a result of any curtailment of Transmission Service on the Transmission Provider’s Transmission System.
In accordance with FERC Order 676e, Entergy’s OASIS website will utilize the REBID functionality.
For a Transmission Reservation in ACCEPTED or COUNTEROFFER status, the Transmission Customer may CONFIRM, DECLINE, or REBID a Transmission Service Request. This functionality allows the Transmission Customer the opportunity to change capacity only.
Entergy’s Tariff Rate is non-negotiable, and represents the prevailing FERC Filed Transmission Service Rate. Therefore, Entergy’s OASIS will not utilize functionality to allow a Transmission Customer to rebid on price. All fields populated by the customer for price must reflect that of the appropriate prevailing Tariff Rate for the Transmission Service requested.
3.1. Modifications to PTP Service
Modifications to PTP Service pursuant to Sections 22.1 and 22.2 of the Tariff must be submitted via OASIS using the Redirect function. The procedures governing service modifications are described below:
i. Only Confirmed, Firm PTP Service Reservations may be redirected.
ii. Redirect TSRs may not extend beyond the start and end times of the original (parent) Reservation.
iii. The new TSR must:
▪ be assigned either the Firm or Non-Firm service type;
▪ be assigned the Redirect request type; and
▪ include the ARef of the original Reservation.
iv. Redirect TSRs for alternate path service which are submitted with Request_Type=Original are not valid.
v. Only Original, Matching, Renewal, Resale, Deferral, and Firm Redirect Reservations may be redirected. Reservations that have been redirected on a Non-Firm basis may not be redirected.
vi. Multiple Reservations cannot be combined into a single redirected Reservation.
3.2. Modification of PTP Service On A Firm Basis
As available, Customers may modify the POR /POD of Confirmed, Firm PTP Service on a Firm basis at no additional cost per Section 22.2 and Attachment M of the Tariff:
i. Requests to redirect a Confirmed, PTP Service Reservation on a Firm basis will be treated as a new TSR for Firm PTP Transmission Service.
ii. Requests to redirect Firm PTP Service on a Firm basis (both short-term and long-term service) must be submitted via OASIS using the Redirect function in accordance with the timing requirements described in Section II.1 of this Business Practice as these will be processed as new requests.
iii. A Redirect TSR must include the ARef of the original Reservation in the related reference field.
iv. Requests to modify on a Firm basis will be declined to the extent that the capacity of the original Reservation has already been scheduled or redirected for the same period of time as the Redirect.
v. Requests to modify on a Firm basis may be submitted in daily, weekly, monthly, or yearly service increments.
vi. Requests to modify on a Firm basis must be within the time interval of the original Reservation (the Redirect cannot start before the original start date or end after the original end date).
vii. The Customer will lose the rights to the redirected portion of the original Reservation for the same period of time as the Redirect when the Redirect TSR is Confirmed by the Customer. However, the redirected reservation remains conditional for the purposes of preemption until it passes the conditional reservation deadline under section 13.2 of the OATT.
viii. Transmission capacity “rollover” rights under Section 2.2 of the Tariff will only apply to the redirected Reservation where: (a) the original Reservation was entitled to such rights; (b) the original Reservation was redirected for the entire remaining term; and (c) where rollover capacity has been determined to be available pursuant to Attachment D to Tariff.
3.3. Modification of PTP Service On A Non-Firm Basis
As available, Customers with Confirmed, Firm PTP Service Reservations may take service over secondary PORs and/or PODs on a Non-Firm basis per Section 22.1 of the Tariff.
i. Requests to take service over secondary PORs and/or PODs on a Non-Firm basis should be submitted via OASIS using the Redirect function.
ii. The sum of all Firm schedules and redirected secondary Reservations shall not exceed the capacity of the original Firm Reservation.
iii. The Customer retains rights to Firm PTP Service at the POR and POD of the original Reservation, but may only schedule on the original path provided that the Customer has RELINQUISHED or lost through preemption capacity on the secondary path.
iv. The Redirect TSR must include the ARef of the original Reservation in the related reference field.
v. Redirect TSRs may be submitted in an hourly service increment.
This Section V.4 provides Customers with guidance for posting of resold and transferred Transmission Service reservations and agreements.
A Customer (“the Assignor”) may sell, assign, or transfer all or a portion of its Long- and Short-Term Firm or Non-Firm PTP Service rights under an existing TSA to another Customer (“the Assignee”) as defined in the Transmission Provider’s Tariff. When reselling, assigning, or transferring Transmission Service, the Assignor and the Assignee must allow the Transmission Provider sufficient time to evaluate the Assignee’s eligibility to become a Customer under the Transmission Provider’s Tariff before implementing a resale or transfer, which evaluation includes ensuring that the Assignee is creditworthy under the Transmission Provider’s Tariff. Assignees that are not existing Customers should utilize the existing procedures under the Tariff to become a Customer prior to executing the necessary agreements for resold or transferred Transmission Service. The sale, assignment, or transfer of Long and Short Term Firm or Non-Firm PTP Transmission Service rights must occur in whole MWs and must comply with the NAESB Business Practices.
To resell PTP Service, the Assignee must execute, or already be a signatory to an existing, Form of Service Agreement for the Resale, Assignment or Transfer of Point-to-Point Service under the Transmission Provider’s Tariff before resold service commences. This agreement is Attachment A-1 (“Form A-1”) to the Transmission Provider’s Tariff and is posted on OASIS under the “FAX FORMS” link.
If the Transmission Service to be resold is Short-Term Firm or Non-Firm PTP Service, pages 1 through 2 of Form A-1 must be completed by the Assignee and provided to the Transmission Provider, which agreement can then be used by existing Customers as an umbrella TSA for the future resale of Short-Term Firm and Non-Firm PTP Service. When transacting under an umbrella Form A-1, transaction specifications on OASIS (i.e., price, term, POD, POR) are made part of the TSA and, thus, contractually binding on the parties by inputting them into the resale posted on OASIS, as discussed below. All resales of Transmission Service MUST BE POSTED ON THE TRANSMISSION PROVIDER’S OASIS in accordance with the NAESB Business Practices (WEQ 001-11) before the resold Transmission Service commences.
If the Transmission Service to be resold is Long-Term Firm PTP Service, all pages of Form A-1 must be completed by the Assignee and provided to the Transmission Provider, which agreement will be a discrete agreement for that particular resale. Assignees that are existing Customers will be required to execute a discrete Form A-1 for every resale of Long-Term Firm PTP Transmission Service. All resales of Transmission Service MUST BE POSTED ON THE TRANSMISSION PROVIDER’S OASIS in accordance with the NAESB Business Practices (WEQ 001-11) before the resold Transmission Service commences. Any additional transaction specifications (i.e., price, term, POD, POR) that are input into the resale posted on OASIS as discussed below are made part of the TSA, and thus are contractually binding on the parties.
Once the Assignee has completed and executed a Form A-1 in accordance with the requirements set forth above, the Assignee must fax the executed Form A-1 to the Transmission Provider’s Transmission Services Group at 601-985-2923, attention Wayne Warren.
4.1.1. OASIS Posting of Resales
Resales may be posted to the Transmission Provider’s OASIS using the following methods:
4.1.1.1 Resale Posted by Assignor Using Existing TSR Detail
4.1.1.1.1 Assignor opens Confirmed TSR to be resold and clicks “TransAssign” to open Reservation Entry form of Populated TSR.
4.1.1.1.2 Assignor clicks “Add/Edit Reassign” to open the Assigned Transmission Reservation Profile.
4.1.1.1.3 Assignor selects the ARef in the “Reassigned Ref” field.
4.1.1.1.4 Assignor modifies the Capacity, Start_Time, Stop_Time, Bid Price, Offer Price, fields, etc. as necessary to accurately reflect the resale.
4.1.1.1.5 Assignor “Submits” the characteristics of the resale, once finished.
4.1.1.1.6 On the Reservation Entry Form, the Assignor will choose the Assignee to whom it is selling the Transmission Service in the Customer field on the Reservation Entry Form.
4.1.1.1.7 Assignor will change the Status of the resale from QUEUED to CONFIRMED.
4.1.1.1.8 Assignor will create a Reservation Profile to match the Assigned Transmission Reservation Profile.
4.1.1.1.9 Assignor “submits” the resale.
4.1.1.2 Resale Posted by Assignor From Reservation Summary Page
4.1.1.2.1 On the Reservation Summary page, the Assignor clicks the “TransAssign” button.
4.1.1.2.2 The Assignor then selects the POR, POD, Source, Sink, Service, Start Time, and Stop Time of the Parent TSR.
4.1.1.2.3 On the “Reservation Entry Form”, in the field entitled “Customer,” the Assignor selects the entity that will be the purchaser of the Transmission Service being resold.
4.1.1.2.4 On the “Reservation Entry Form”, in the field entitled “Seller,” the Assignor selects itself (the entity that currently owns the service being resold).
4.1.1.2.5 Assignor selects “Add/Edit Reassign” to open the Assigned Transmission Reservation Profile.
4.1.1.2.6 Assignor selects the ARef in the “Reassigned Ref” field.
4.1.1.2.7 Assignor modifies the Capacity, Start_Time, Stop_Time, Bid Price, Offer Price, fields, etc. as necessary to accurately reflect the resale.
4.1.1.2.8 Assignor will change the Status of the resale from QUEUED to CONFIRMED.
4.1.1.2.9 Assignor will create a Reservation Profile to match the Assigned Transmission Reservation Profile.
4.1.1.2.10 Assignor “submits” the resale.
4.1.1.3 A Resale can also be initiated by posting the following information on OASIS via the transrequest template:
4.1.1.3.1 REQUEST_TYPE Must be RESALE
4.1.1.3.2 SELLER_CODE Must identify the Reseller (registered entity other than the Primary Provider)
4.1.1.3.3 SELLER_DUNS Must identify the Reseller
4.1.1.3.4 PATH, POINT_OF_RECEIPT, POINT_OF_DELIVERY, SOURCE, and SINK must represent the transmission service points being requested
4.1.1.3.5 SERVICE_INCREMENT, TS_CLASS, TS_TYPE, PERIOD, TS_WINDOW, TS_SUBCLASS Must represent a set of valid transmission service attributes offered by the Primary Provider and being requested from the Reseller
4.1.1.3.6 START_TIME Must specify the requested start of transmission service
4.1.1.3.7 STOP_TIME Must specify the requested stop/end of transmission service
4.1.1.3.8 CAPACITY_REQUESTED Must specify the amount of transmission capacity being requested
4.1.1.3.9 BID_PRICE Must specify the price being requested in $/MW-Hour
4.1.1.4 If a Resale has been initiated by posting the following information on OASIS via the transrequest template, it is the Reseller’s obligation to respond to RESALE requests submitted to them on OASIS. The Reseller may act on the RESALE request using any of the processes defined in WEQ 013-2.3 “Basic OASIS Transaction Handling,” WEQ 013-2.6.1.1 “Offering of Partial Service,” and/or Section WEQ 013-2.6.1.2 “Negotiation of Price.” At some point in this process, the Reseller must identify those transmission service reservations whose scheduling rights are to be conferred to the Assignee as described in WEQ 013-2.6.7.1.
Where the Assignor and Assignee agree that the Assignee will replace the Assignor as the financially obligated Customer and will contractually undertake all of the Assignor’s liabilities associated therewith, a non-conforming TSA must be completed, executed between the Assignee, Assignor, and the Transmission Provider, and filed with FERC. The ICT will not approve a transfer request without confirmation from Entergy that a non-conforming form A-1 has been executed by the Transferor and the Transferee Customers contemplating the transfer of a TSA must contact the Transmission Provider at 601-985-2923 (Wayne Warren) to initiate the preparation and execution of a non-conforming agreement. Transfers MUST BE POSTED ON THE TRANSMISSION PROVIDER’S OASIS in accordance with the NAESB Business Practices (WEQ 001-12) before the transferred service commences. The process for posting a transfer on OASIS will be provided to the Assignor when the non-conforming TSA has been completed, executed between the Assignee, Assignor, and the Transmission Provider, and filed with FERC.
4.1.3 Billing of Resales/Reassignments and Transfers
All resales or transfers of Long-Term Firm, Short-Term Firm, and Non-Firm PTP Service must be conducted on OASIS to ensure that the proper entity is billed and, where applicable, the proper entity is credited. The above procedures for resales and transfers MUST BE FOLLOWED AND PERFORMED prior to commencement of the resold or transferred Transmission Service in order to ensure that a resale or transfer is properly implemented.
4.1.3.1 Invoicing of Resold or Assigned Transmission Service
Customers MUST post the offer price of the resale in $/MW-HR. If the OFFER_PRICE is blank, the Transmission Provider will invoice the resale at the Tariff rate. If the OFFER_PRICE is completed by the Customer, regardless of the amount shown, the Transmission Provider will invoice the resale at the amount provided by the Customer in the OFFER_PRICE field, at a rate of ($/MW-HR). If the procedures outlined above for resold Transmission Service are followed (including the execution of Form A-1), the Transmission Provider will invoice the Assignee for the resold Transmission Service and credit or debit the Assignor any amounts due based on the difference between the rate negotiated with the Assignee and the Assignor (the “offer price” field) and the Tariff rate after payment has been received from the Assignor subject to the following:
1. If the negotiated rate is less than the original rate specified in the Assignor’s TSA, the Assignor remains liable for the difference between the negotiated rate and the original rate;
2. If the negotiated rate is more than the original rate specified in the Assignor’s TSA, the Transmission Provider will credit the Assignor the difference between the negotiated rate and the original rate only after payment has been received from the Assignee.
An example of the calculation of the credit or debit to be applied to the Assignor using the 2009 Tariff rates is provided for reference below.
TABLE 3-1
|
Transmission Service |
Capacity Resold |
Tariff Rate ($/MW-HR) |
Total Cost of Capacity ($/MW-HR) |
Offer Price ($/MW-HR) |
Total Cost of Capacity ($/MW-HR |
Difference ($/MW-HR) |
|
Yearly Firm PTP |
100 |
1.85 |
185.00 |
2.00 |
200.00 |
15.00 |
|
Monthly Firm PTP |
100 |
1.99 |
199.00 |
1.00 |
100.00 |
99.00 |
|
Weekly Firm PTP |
100 |
1.99 |
199.00 |
2.50 |
250.00 |
51.00 |
|
Daily Firm PTP |
|
|
|
|
|
|
|
On-Peak |
100 |
2.79 |
279.00 |
3.00 |
300.00 |
21.00 |
|
Off-Peak |
100 |
2.00 |
200.00 |
1.50 |
150.00 |
50.00 |
4.1.3.2 Invoicing of Transferred Transmission Service
If Transmission Service is transferred and a non-conforming TSA is completed, executed, filed, and accepted by FERC, the Transmission Provider will invoice the Assignee directly for all costs associated with the resold or transferred service and will not be responsible for any credits, debits, or other costs or expenses other than as agreed by all parties in the non-conforming TSA.
VI CONDITIONAL FIRM SERVICE AND PLANNING REDISPATCH SERVICE
In accordance with Attachment D of the Tariff, Long-Term Firm PTP Transmission Service is evaluated pursuant to the SIS process in order to ensure that the service can be reliably accommodated. To the extent that a SIS identifies violations of the criteria specified in Attachment D, and at the request of the Customer, the study will also evaluate mitigation options that may eliminate the violations and/or allow the TSR to be ACCEPTED. The mitigation options, which may allow the TSR to be ACCEPTED with or without the need for transmission upgrades, are Conditional Firm Transmission Service (“Conditional Firm Service”) and Planning Redispatch Service. When requested by the customer in the SIS Agreement, these options are fully studied when the initial reliability screen and limitations on availability described in Section 4 are not indicated.
An Eligible Customer may request study of Conditional Firm Service, Planning Redispatch Service, both, or neither as part of the SIS process. The ICT will use the procedures in Attachment D to study a TSR that includes a request for Conditional Firm Service or Planning Redispatch Service. Section 4.2 of Attachment D describes the curtailment criteria that will be identified in the SIS, including: (i) the specific System Condition(s) when curtailment may apply using a Secondary Network Service curtailment priority, including, but not limited to, designation of limiting transmission elements, such as a transmission line, substation, or flowgate (“Conditions Option”); and/or (ii) the annual number of hours (i.e., the total number of hours for a calendar year) when curtailment using a Secondary Network Service curtailment priority may apply (“Hourly Cap Option”). Designation of system load levels, standing alone, does not qualify as an acceptable system condition; such load levels must be linked to a specific constraint or transmission element that is associated with the TSR.
As explained below in Section VI.5, if some portion of the TSR for which Conditional Firm Service and/or Planning Redispatch Service has been requested may be accommodated as firm Transmission Service, a counteroffer will be made for the amount of Transmission Service that can be provided as firm. The counteroffer for each year of the requested Transmission Service will be for the lowest MW amount of Firm Transmission Service that is available as firm in any month of the year of service. If Conditional Firm Service or Planning Redispatch Service is available to accommodate the remainder of the capacity requested for Transmission Service, the customer will be allowed to submit a new TSR for that portion of the requested capacity that is available as Conditional Firm Service or Planning Redispatch Service.
· If no portion of the requested capacity can be accommodated as firm, but Conditional Firm Service or Planning Redispatch Service is available to accommodate all of the TSR, the request will be ACCEPTED subject to the conditions or redispatch requirements identified through the SIS Process.
· If no portion of the requested capacity can be accommodated as firm, but Conditional Firm Service or Planning Redispatch Service is available to accommodate some, but not all, of the TSR, a counteroffer will be made for the amount of Transmission Service that can be provided with the inclusion of Conditional Firm Service or Planning Redispatch Service. The counteroffer for each year of the requested Transmission Service will be for the lowest MW amount of Firm Transmission Service that is available in any month of the year. The ICT will assess partial Conditional Firm Service and Planning Redispatch Service solutions that are determined by the ICT to be reasonable.
· If none of the TSR can be accommodated even with the inclusion of Conditional Firm Service or Planning Redispatch Service options, the SIS will provide a high-level cost estimate of the upgrades required to provide the Transmission Service.
2. Conditional Firm Transmission Service
Conditional Firm Service is Long-Term Firm PTP Service, provided that, at certain times, the service may be curtailed using a Secondary Network Service curtailment priority to maintain reliability. The rate for Conditional Firm Service is the Long-Term Firm PTP Service rate. Per the notice posted on the Transmission Provider’s OASIS on December 31, 2009, Transmission Provider does not credit customers for long-term firm service that is curtailed to maintain reliability because of a TLR. Consistent with this notice, Transmission Provider does not credit Conditional Firm Service Customers when service is curtailed during conditional hours or when curtailment conditions occur.
When an Eligible Customer requests evaluation of Conditional Firm Service, the SIS will identify: (i) the specific System Condition(s) when curtailment may apply using a Secondary Network Service curtailment priority (“Conditions Option”); and (ii) the annual number of hours (i.e., the total number of hours for a calendar year) when curtailment using a Secondary Network Service curtailment priority may apply (“Hourly Cap Option”). To Confirm the Conditional Firm Service, the Customer must select either the Conditions Option or the Hourly Cap Option.
Conditional Firm Service will only be curtailed for reliability reasons. The reservation will be downgraded from “7-F” curtailment priority to “6-CF” curtailment priority during periods of congestion when the conditions identified in the Customer’s TSA are in effect or until the number of conditional hours are exhausted. 6-CF priority is equal to Secondary Network Service for curtailment purposes.
When the Hourly Cap Option is chosen by the Customer, the TSA will specify the number of conditional curtailment hours available for curtailment in each year of service. Beginning on the date that service commences each year, the Transmission Provider may curtail the service at the Secondary Network Service curtailment priority in response to system congestion until the service has been curtailed for the number of hours specified in the TSA for that year of service.
Per WEQ 001-11.3.2, Conditional Firm reservations may not be aggregated with any other reservation in a resale. Any resale submitted by a Transmission Customer that includes any other reservation will be ANNULLED in accordance with WEQ 013-2.2, and the resold capacity will revert to the parent reservation.
3. Planning Redispatch Service
Planning Redispatch Service is a mitigation option used to grant Long-Term Firm PTP Service through redispatch of either the Transmission Provider’s existing generating resources or the generating resources of a third-party. One Planning Redispatch Service solution can include a combination of up to four generation resources. A Customer, however, may not mix generation pairs, i.e., include a Transmission Provider resource and a third party resource as a generator pair; nor may it use a third-party generator pair and a Transmission Provider generator pair when necessary to resolve multiple overloads associated with one TSR. Planning Redispatch Service must be incremental to the system, e.g., existing arrangements that may provide counterflows cannot be used for third-party redispatch. The ICT will determine on a case-by-case basis whether identified Planning Redispatch Service options are considered to be incremental. Furthermore, the constraint caused by the TSR under review for mitigation will be resolved by the Planning Redispatch Service and all existing TSRs under review (and their corresponding generators) will not be used for alleviating the constraint even if they provide counterflows. Existing TSRs (and their corresponding generators) will be included in the Base Case Model before evaluating new TSR for Planning Redispatch Service.
For example, the dispatch of Generator 1 is necessary (but not sufficient) to provide Planning Redispatch Service to grant TSR “B” because of a constraint. The dispatch of Generator 2 for an existing Reservation A provides unintended counterflows that mitigate the constraint necessitating the use of Planning Redispatch Service to serve TSR B. A third generator, Generator 3, must be redispatched to grant TSR B because the dispatch of Generator 1 is not sufficient to grant TSR B. The dispatch of Generator 2 is already committed for TSR A and cannot be tied to TSR B and therefore it cannot be used to provide Planning redispatch for new TSR B under evaluation. In other words, the dispatch of Generator 1 and 3 are required to mitigate the constraint otherwise precluding Entergy from granting TSR B, i.e., the Planning Redispatch Service solution using Generator 1 and 3 is incremental to the system for purposes of granting TSR B.
3.1. Planning Redispatch Service From Transmission Provider Resources
3.2. Planning Redispatch Service From Third-Party Provider Resources
The Transmission Provider will not make purchases from third-parties in order to provide Planning Redispatch Service. Instead, the Customer must either arrange for the use of its own resources or contract with other parties in advance of completing the TSA for Planning Redispatch Service. For Planning Redispatch Service granted based on third-party redispatch, the Customer will be charged the rate for annual PTP Service under the Tariff. The Customer will be responsible for: (i) making all contractual arrangements for the redispatch from third-party generation; and (ii) all costs charged by the third-party generator. The Customer will directly compensate the third-party generator for the third-party redispatch.
The Customer must provide to the ICT all information necessary for the study of the third-party redispatch solution. In the event that the Customer does not provide the information regarding potential third-party redispatch solutions prior to signing the SIS Agreement, the SIS Report will notify the Customer that it has 15 days to submit any proposed third-party redispatch solutions. Any proposed third-party redispatch solutions provided by the Customer within those 15 days will be evaluated by the ICT as a continuation of the SIS process.
Firm Transmission Service is required to implement the third-party redispatch. Existing transmission arrangements may be used to satisfy this requirement; however, the Transmission Service used to implement the third-party redispatch must cover the entire term of the Transmission Service being granted based on the third-party redispatch.
4. Limitations on Availability
Sections 4.2 and 4.3 of Attachment D provide that Conditional Firm Service or Planning Redispatch Service will not be available in response to a TSR if the service otherwise will: (i) degrade or impair the reliability of service to Native Load Customers, Network Customer, or PTP Service Customers; or (ii) interfere with the Transmission Provider’s ability to meet prior firm contractual commitments.
Prior to implementing enhanced congestion management software related to Conditional Firm Service and Planning Redispatch Service, the Transmission Provider has determined that it can accept no more than Five (5) Reservations involving Conditional Firm Service or Planning Redispatch Service for a particular time period, which service must result in no more than six constrained elements being impacted (by 3 percent or more), during the relevant time period. After implementation of the enhanced congestion management software and development of NAESB Business Practices, the Transmission Provider will reevaluate the limitations on Reservations and flowgates set forth in this section and establish new limitations applicable to Conditional Firm Service and Planning Redispatch Service based on the modified software and new NAESB Business Practices. The initial reliability screen described below will, however, be retained.
In order to determine that the provision of Conditional Firm Service or Planning Redispatch Service will not: (i) degrade or impair the reliability of service to Native Load Customers, Network Customers, or PTP Customers; or (ii) interfere with the Transmission Provider’s ability to meet prior firm contractual commitments, the ICT will apply the following reliability criteria:
· The new service shall not result in a violation of any regulatory requirements, including but not limited to: (i) the minimum offsite power requirements of NUC-001 as they pertain to offsite power requirements for Transmission Service to nuclear plants; and (ii) NERC Reliability Standards TPL-001 – TPL-004 and any successor standards thereto.
· Where the service impacts interconnecting tie-lines, regardless of the voltage of the facilities, including interfaces with neighboring balancing authorities, the service will be studied for Conditional Firm Service or Planning Redispatch Service through the SIS and will be subject to the terms and conditions of the Transmission Provider’s Tariff applicable to third party constraints. For purposes of this business practice, interconnecting tie-lines are not interconnections: (i) solely to transmission-dependent generators; (ii) to non-Entergy owned facilities that are within the Transmission Provider’s Control Area; or (iii) between Entergy Operating Companies and the impact is defined as violating the thermal or voltage limit on the interface facilities, e.g., a TPL-002 violation.
· Conditional Firm Service and Planning Redispatch Service are not available to resolve a constraint on a third party’s system. To the extent the SIS identifies an impacted constraint on a third party’s system, the terms and conditions of the Transmission Provider’s Tariff applicable to third party constraints will apply.
If any of these requirements are not met, Conditional Firm Service or Planning Redispatch Service will not be offered.
5. Conditional Firm Service and Planning Redispatch Service TSR Application and Study Process
When the ICT receives a TSR for Long-Term PTP Service that is for a duration of one year or longer, the ICT will provide the eligible customer with a SIS Agreement containing Conditional Firm Service and Planning Redispatch Service study options within 30 days from the date of a completed application submitted on OASIS (clocked by the ICT as the QUEUED time).
5.1. Execution of the System Impact Study Agreement
Within 15 days of receipt of the SIS Agreement, the Customer must execute the agreement and indicate whether it desires the study of Conditional Firm Service, Planning Redispatch Service, or both. This is the only opportunity that the Customer has to request the study of Conditional Firm Service and/or Planning Redispatch Service.
When a customer executes the SIS Agreement and indicates that it desires to have either or both Conditional Firm Service or Planning Redispatch Service studied, the ICT has 60 days from the date of execution of a completed SIS Agreement (the clock starts when the ICT receives the SIS Agreement by fax or by email if fax is unavailable to the customer) to provide a completed SIS to the Customer.
5.2. Tender of the System Impact Study and Customer Options
If the SIS provided to the Customer indicates that the full amount of the requested service is available as FIRM service, then the request will be ACCEPTED and the Customer may CONFIRM or WITHDRAW that request for service.
If the SIS provided to the customer indicates that not all of the service requested is available as FIRM service, the SIS will include the amount of FIRM service available as well as any Conditional Firm Service or Planning Redispatch Service that is available to the Customer. The ICT will then contact the Customer and present the following options for service are presented in the SIS.
The Customer has the following options (described in greater detail below):
Option 2 take all FIRM service that is available and take either of the Conditional Firm Service options or Planning Redispatch Service subject to Biennial Reassessment (with the ability to convert to bridge service after completion of a FS);
Option 3 take all FIRM service that is available and reject the Conditional Firm Service options and Planning Redispatch Service; or
Option 4 withdraw the request.
5.3. Management of Conditional Firm Service/Planning Redispatch Service Options on OASIS
· If the Customer chooses Option 1 following the results of the SIS, the ICT will not COUNTEROFFER the TSR for the amount of FIRM service available; rather the request will remain in STUDY status, and the ICT will present the customer with a FS Agreement under the normal timing requirements and process. In other words, the customer will not be allowed to take partial firm service and proceed to FS for the full amount of the original service request.
· In the event that a FS Agreement is not executed, the Conditional Firm Service and Planning Redispatch will be provided under the terms of the TSA filed with the Commission until its term ends.
· Upon completion of the FS, the only service that will be offered will be FIRM service for the entire capacity originally requested under the conditions of the upgrades stated in the FS. Once the FS is tendered to the Customer, the ICT will set the status to ACCEPT, and the Customer response proceeds under the normal timing and process.
· If Conditional Firm Service or Planning Redispatch is provided to a bridge customer, such service is not subject to a biennial reassessment
· Option 2:
· If the customer chooses Option 2, the ICT will COUNTEROFFER the original request with the amount of FIRM service that is available. The ICT will then instruct the Customer to submit a new TSR on OASIS for the remaining capacity that was requested and identified in the SIS as available Conditional Firm Service or Planning Redispatch Service, but otherwise identical to the original request, and referencing the Assignment Reference (ARef) of the original request in the Customer Comment field. The ICT will then ACCEPT the second request using the CCO template if the customer has selected the Conditional Firm Service option. If the Customer has selected Planning Redispatch Service, the ICT will ACCEPT the new TSR with Seller Comments noting that it is Planning Redispatch Service.
Prior to confirmation, the Customer may reject either or both TSRs by setting the status to WITHDRAWN or by failing to CONFIRM either TSR within the response time limit following the TSR being set by the ICT to COUNTEROFFERED or ACCEPTED.
If no FIRM service is available, the ICT, following specific customer affirmation, will COUNTEROFFER the original request with the capacity available as Conditional Firm Service or Planning Redispatch Service if the capacity available is less than MWs requested by the Customer, or ACCEPT the TSR if the entire capacity requested is available as Conditional Firm/Planning Redispatch Service, noting the limitations on the service through either the completion of the CCO template if the Customer has selected Conditional Firm Service, or the inclusion of Seller Comments if the Customer has selected Planning Redispatch Service.
Prior to confirmation, the Customer may reject the counteroffered TSR by setting the status to WITHDRAW or by failing to CONFIRM the counteroffer within the response time limit.
After confirming an offer of Conditional Firm Service or Planning Redispatch Service, the Customer will be required to execute a TSA for that service with the biennial reassessment terms, regardless of whether the Customer is interested in securing the service as “bridge” service .
Consistent with Section 4 of Attachment D, after reviewing the SIS in which Conditional Firm Service and/or Planning Redispatch Service was studied, the Customer may desire to take Conditional Firm Service or Planning Redispatch Service as a “bridge” product until certain facilities are constructed. In this case, the customer will be required to CONFIRM the amount of Conditional Firm Service or Planning Redispatch Service available and execute a TSA for that service that includes biennial reassessment terms. The ICT then will instruct the Customer to submit a new TSR (hereafter the “FS TSR”) for the amount of capacity that was not available as firm, but otherwise identical to original TSR, which shall be referenced in the Customer Comment field. The ICT will then offer a FS Agreement to the Customer based on the SIS associated with the original TSR, but otherwise under the normal timing requirements and process. The FS Agreement must be executed by the Customer under the normal timing requirements, and the request will remain in STUDY status until the FS is tendered to the Customer.
Once the FS has been completed and tendered, the ICT will ACCEPT the TSR and complete the CCO template of the FS TSR accordingly.
If the Customer elects to fund the upgrades identified in the FS and become a bridge customer, the Customer shall CONFIRM the FS TSR, and the ICT will RECALL the Conditional Firm Service/Planning Redispatch Service TSR if the service has commenced, or ANNUL the Conditional Firm Service/Planning Redispatch Service TSR if the service has not commenced. The TSA then will be amended to reflect the agreed-upon terms of the upgrades and all terms of the bridge service pending the completion of the facility upgrades.
· If the Customer does not elect to fund the upgrades, it shall retain its Conditional Firm Service/Planning Redispatch Service by either setting the FS TSR to WITHDRAWN or failing to CONFIRM the FS TSR within 15 days of it being set to ACCEPTED.
· Once upgrades agreed to by the Customer are in service, the ICT will work with the customer to manage the TSR(s) on OASIS.
· Option 3:
· If the Customer chooses Option 3, the ICT will COUNTEROFFER the original request for the amount of FIRM service that is available, and the TSR will proceed as any long-term firm PTP Service.
5.4. Following Tender of the FS
If all of the capacity requested is available as Conditional Firm Service/Planning Redispatch Service and eligible for bridge service, the ICT will ACCEPT the TSR and complete the CCO template of the FS TSR accordingly. If the Customer elects to fund the upgrades identified in the FS and become a bridge customer, the Customer shall CONFIRM the FS TSR, and the ICT will RECALL the Conditional Firm Service/Planning Redispatch Service TSR if the service has commenced, or ANNUL the Conditional Firm Service/Planning Redispatch Service TSR if the service has not commenced.
· If the Customer elects to fund the upgrades, the TSA will be amended to reflect the agreed-upon terms of the upgrades and all terms of the bridge service pending the completion of the facility upgrades.
· If the Customer does not elect to fund the upgrades, it shall retain its Conditional Firm Service/Planning Redispatch Service by either setting the FS TSR to WITHDRAWN or failing to CONFIRM the FS TSR within 15 days of it being set to ACCEPTED.
If only a portion of the capacity requested is available as Conditional Firm Service/Planning Redispatch Service and eligible for bridge service, the ICT will COUNTEROFFER the MW profile of the FS TSR to indicate any portion of the requested capacity that is not available as Conditional Firm Service/Planning Redispatch Service until the expected in-service date of the facilities required, and complete the CCO template of the FS TSR accordingly for the capacity available for Conditional Firm Service or adding a note to the Seller’s Comments for Planning Redispatch Service. If the Customer chooses to fund the upgrades identified in the FS and become a bridge customer, it shall CONFIRM the FS TSR, and the ICT will RECALL the Conditional Firm Service/Planning Redispatch Service TSR if the service has commenced, or ANNUL the CF/PR TSR if the service has not commenced.
○ If the Customer agrees to fund the upgrades, the TSA will be amended to reflect the terms of the upgrades agreed-upon and terms of the bridge service pending the completion of the facility upgrades.
○ If the Customer elects not to fund the upgrades, it shall retain the Conditional Firm Service/Planning Redispatch Service by setting the FS TSR to WITHDRAWN or by failing to CONFIRM it within 15 days of the FS TSR being set to ACCEPTED.
Once upgrades agreed to by the Customer are in service, the ICT will work with the customer to manage the TSR(s) on OASIS.
In the biennial reassessment, the ICT, on behalf of the Transmission Provider, may adjust the conditions or number of hours during which Conditional Firm Service will be conditional or amount of redispatch required to continue Planning Redispatch Service in order to ensure that the continued provision of the service does not impair reliability. This adjustment applies to all flowgates, conditions, hours, and/or amount of redispatch required and is not constrained to the flowgates, conditions, hours, and/or amount of redispatch previously identified for the particular service at issue.
The ICT shall provide the Customer notice of any changes to the curtailment conditions or redispatch obligations no less than 90 days prior to the date for imposition of the new requirements or 30 days prior to the relevant rollover deadline, whichever is earlier. Concurrent with such notice, the ICT will provide the Customer with the biennial reassessment study report, which includes a narrative description of the study, any identified affected third party systems, and the reasons for changes to the number of hours per year or system conditions under which conditional curtailment may occur or the reasons for the changes to the redispatch obligations. The issuance of a biennial reassessment and any associated notifications will occur through the same methods utilized for the issuance and notification of any SIS and/or FS performed in accordance with Attachment D, i.e., the biennial reassessment study report is posted on OASIS utilizing the OASIS ARef of the original TSR as its reference number, and an email notification of the posting is provided to the Customer.
If the Transmission Provider or its ICT determines through its biennial reassessment that the service can no longer be provided reliably, including for failure to meet the requirements of the initial reliability screen, such service will be terminated at the end of the then-current two-year term per section 15.4 of Entergy’s OATT.
If the biennial reassessment identifies an affected third-party system, the immediately subsequent two-year term of service cannot commence until an affected system study is conducted by the third party. If the constraints identified on a third-party affected system cannot be resolved through an affected system study and/or the Customer has not communicated the status of the resolution of such third-party constraints to the Transmission Provider or the ICT within 30 days of the start of service, the Transmission Provider or its ICT will deem that the service can “no longer be reliably provided” and the service will be terminated at the end of the current two-year term. Alternatively, where the Customer communicates that there is reasonable certainty that the third-party constraints will be resolved or that he is diligently working to resolve such constraints at least 30 days prior to the start of service, the Transmission Provider will file an unexecuted TSA to allow the Customer to retain the Transmission Service. The service will not, however, be available for scheduling until all third-party constraints have been resolved.
The Customer may withdraw from the biennial reassessment process, upon receiving the results of its biennial reassessment. If the Customer withdraws from the biennial reassessment process after issuance of the biennial reassessment study report, it may base any decision to continue or terminate service on the results of the biennial reassessment issued prior to the time of their withdrawal.
If the biennial reassessment results show that the specific conditions, hours, or redispatch obligations applicable to the service have changed, the Customer may choose to discontinue the service. The Customer wishing to terminate the service must provide written notice to the ICT and the Transmission Provider at least 30 calendar days prior to the date upon which the specific conditions, hours, or redispatch requirements could change based on the results of the biennial reassessment. The Customer may not terminate the service, however, if one of the following conditions are met:
· The results of the biennial reassessment have “firmed up” the service for the immediately subsequent 2-year term of service assessed.
· The results of the biennial reassessment have “firmed up” the service for the remainder of the term of service.
If the Customer does not provide notice of termination prior to the deadline discussed above, the TSA will be amended to reflect the specific conditions, hours, or redispatch requirements identified through the biennial reassessment and filed with FERC, and the service will continue for the next two-year period subject to the new conditions, hours, or redispatch requirements identified in the biennial reassessment.
During the biennial reassessment, when results indicate that no conditions or constraints exist during the immediately subsequent two-year term of service being assessed, the ICT will utilize the yearly models to determine if the service may become firm for the remaining term of the service (including rollover rights, if applicable). Biennial reassessments will not occur every two years, if, during the last biennial reassessment, no conditions existed for the entirety of the term of service. In accordance with the results of the biennial reassessment, Conditional Firm Service and/or Planning Redispatch Service may be firm on a long-term basis provided both of the following conditions are met:
· The biennial reassessment identifies no additional constraints or conditions for the provision of that service for the immediately subsequent two-year term of service that is being assessed; and
· The biennial reassessment identifies no additional constraints or conditions for the remainder of the service at issue.
· Entergy and its ICT may decide to waive a biennial reassessment in which case the customer will be notified of such waiver at least 90 calendar days prior to the commencement of the immediately subsequent two-year term of service. Any waiver of biennial reassessment will be applied consistently to similarly situated services. “Similarly situated services” are services that meet the following conditions: (1) both services are subject to biennial reassessments within 6 months of each other; (2) both services impact only identical flowgates; and (3) either both services have rollover rights or both services do not have rollover rights.
VII. NETWORK INTEGRATION TRANSMISSION SERVICE
This Business Practice describes the requirements for designating Network Resources pursuant to the Tariff. As required under Section 3.2.2.2 of Attachment D and Section 7.3 of Attachment E, this Business Practice includes interim procedures describing: (i) the process for providing the necessary attestation when designating a Network Resource; (ii) the process for evaluating requests to undesignate Network Resources; (iii) the treatment of any additional capacity made available when a Network Resource is undesignated pending implementation of the relevant NAESB requirements; and (iv) instructions for submitting requests to undesignate existing Network Resources.
1. Interim Procedures For Providing Attestations For Network Resources
Network Customers must attest that a resource can qualify for designation under Part III of the Tariff (“Network Resource” or “DNR”). In order to facilitate fulfillment of this requirement, the Transmission Provider has provided an OASIS template for Network Customers to utilize in providing their attestation as well as additional information about the resource being requested for designation as a Network Resource as required by the Transmission Provider’s Tariff (“OASIS DNR Attestation Template”).
Prior to the implementation of relevant NAESB standards related to submitting Network Resource information and attestations over OASIS, the following procedures will govern how Customers submit the operational information and attestations required under Section 29 and 30 of the Tariff when designating a generation facility or Power Purchase Agreement (“PPA”) as a Network Resource under the Tariff. As explained below, this process requires the completion of the Transmission Provider’s “OASIS DNR Attestation Template”. The OASIS DNR Attestation Template provides: (i) the exact language required when attesting that a particular generation facility or PPA qualifies as a Network Resource under Sections 29.2(viii) and 30.2 of the Tariff; and (ii) fields within which Customers can provide additional operational information required by the Tariff.
Pursuant to Section 7.4 of Attachment E, Customers must provide their attestation through the OASIS DNR Attestation template at the time the TSR is submitted over OASIS. Failure to provide the attestation at the time required will result in the TSR being considered deficient under Section 29.2 of the Tariff.
ATTESTATIONS CANNOT BE SUBMITTED USING THE CSV UPLOAD FUNCTION OF THE OATI WebOASIS. ACCORDINGLY, ALL DNRS SHOULD BE SUBMITTED THROUGH THE USER INTERFACE.
The OASIS DNR Attestation Template is an additional template and screen that links an attestation to a Customer’s individual TSR on OASIS and provides: (i) the exact language required when attesting that a particular generation facility or PPA qualifies as a DNR under Sections 29.2(viii) and 30.2 of the Transmission Provider’s Tariff; and (ii) fields within which Customers can provide additional information required by the Transmission Provider’s Tariff.
Once a “Network” service type is selected in the TransRequest template, that template activates the OASIS DNR attestation template. Once the TSR form is completed, the OATi WebOASIS will provide a “DNR Attestation” button. Network Customers should select this button and complete all of the fields in the OASIS DNR attestation Template in accordance with the following procedures:
· The Network Customer’s representative should enter his/her name into the field entitled “Attestor’s Name”.
· The Network Customer’s representative should then check the “I Attest” box to indicate that he/she is certifying the validity of the attestation provided, which attestation is described in sections 29.2(viii) and 30.2 of the Entergy Tariff.
· The OASIS DNR attestation template automatically populates the “Resource Type” field based on the POR/POD combination of the DNR. Customers should verify that this information was populated correctly.
· For On-System Resources, Network Customers must supply information in the following fields: “Approx. Var. Generating Cost for Redispatch ($/MWH)” and “Resource operating restrictions”. They may then “Submit” the DNR Attestation.
· For Off-System resources, Network Customers must supply the following information indicated on the OASIS DNR Attestation Template:
○ The “Resource Type” field will default to “Off-System Customer-Owned generator facility”. If the DNR is a PPA, the Network Customer should select the drop down arrow on the “Resource Type” field and, from the menu displayed, select “Off-System Order 890 Compliance Power Purchase Agreement”.
○ The “Generating Balancing Authority/Originating Control Area” field must be populated with the control area from which the power will originate.
Information must also be supplied in the “Approx. Var. Generating Cost for Redispatch ($/MWH)” and “Resource operating restrictions” fields.
· External transmission arrangements MUST be indicated at the time of submission of the DNR.
○ Where a Network Customer is taking title to purchased power at the Interface of the Transmission Provider’s Transmission System, the Network Customer must check the box above “Row 1”.
○ Where the Network Customer has Off-System TSR Numbers for transmission arrangements to submit, the box below “row 1” must be checked and “Off-System OASIS Provider” and “Off-System OASIS AssignRef” fields should be completed such that a complete path from the originating control area indicated to the Transmission Provider’s Transmission System is indicated. The ICT shall verify, through OASIS, that the transmission arrangements on the external transmission system are firm in accordance with the Transmission Provider’s Tariff.
· The Network Customer may then “Submit” the DNR Attestation.
The Transmission Provider and the ICT will treat the following information regarding Network Resource designations as Confidential Information under Attachment S of the Tariff: operating restrictions, approximate variable generating costs, and arrangements governing the sale and delivery of power to third parties. The procedures described in Section 6 of Attachment S will be followed to prevent the disclosure of commercially sensitive information outside of the ICT, the Transmission Provider’s Energy Delivery Business Unit, and Interested Government Agencies.
2. Procedures for Notifying ICT of Changed Circumstances
Under Sections 7.5.5 and 7.6.3 of Attachment E to the Tariff, Customers must notify the ICT of the following changed circumstances which impact a Customer’s designation of a Network Resource:
· After a TSR to designate an Off-System Network Resource has been CONFIRMED over OASIS, the Customer is obligated to notify the ICT if the OASIS numbers provided by the Customer pursuant to Section 7.5 of Attachment E do not result in CONFIRMED Firm or Conditional Firm PTP Transmission Service or Network Service Reservations sufficient to create a Firm path from the necessary external transmission systems to the Transmission System.
· After a TSR to designate a PPA as a Network Resource is CONFIRMED, the Customer is obligated to notify the ICT if execution of the PPA fails to occur by the deadlines specified in Section 7.6.2 of Attachment E.
Notification to the ICT of the circumstances identified above shall be provided by Network Customers using the “Form to Undesignate or Cluster (Alternate Network Resource Designation) Network Resources.” The form should be faxed to the ICT Tariff Administration Desk at the fax number provided on the form. The Customer must provide such notification to the ICT by the deadlines specified in Sections 7.5.5 and 7.6.3 Attachment E. For convenience purposes, this form is attached as Attachment 7.
3. Interim Procedures for Undesignating Network Resources
Customers may terminate Network Resource designations, either on a “permanent” or “temporary” basis, in accordance with Sections 30.2 and 30.3 of the Tariff, Section 3.2.2 of Attachment D, and Section 10 of Attachment E of the Tariff. Prior to the implementation of NAESB standards related to undesignating Network Resources in accordance with Order No. 890-A and 890-B, the following provisions will govern how customers: (i) submit a request to undesignate an existing Network Resource; (ii) identify whether an undesignation is permanent or temporary; (iii) submit a request to undesignate an existing Network Resource and a request to evaluate it with a new Network Resource (“Alternate Network Resource”) simultaneously; (iv) request that the undesignation of an existing Network Resource and a request for Point to Point or Network Transmission Service be studied concomitantly; and (v) identify the amount of capacity from each existing Network Resource to be evaluated for undesignation in order to accommodate the related request(s).
Non-Simultaneous Undesignation Requests
Requests to undesignate a Network Resource may be submitted on a “stand-alone” basis, i.e. without being simultaneously submitted with a request to designate an Alternate Network Resource. Consistent with FERC Order 890-A, stand-alone requests to undesignate a Network Resource are not studied by the ICT on behalf of the requesting Customer. Long term stand-alone requests to undesignate a Network Resources, are studied for reliability impacts. The costs of the study are not directly assigned to the requesting Customer. Stand-alone requests will be ACCEPTED upon submission. If the Customer elects not to CONFIRM the stand-alone undesignation request, the Customer may WITHDRAW the request prior to the applicable deadline or the request will be RETRACTED and the generating facility will retain its Network Resource status. If the Customer CONFIRMS the stand-alone undesignation request, the request will go into effect on the date specified.
Priority Rights and Capacity Release (Simultaneous Requests)
Prior to the implementation of NAESB standards addressing the processing of undesignation requests and how additional capacity released by undesignation requests should be made available to the market, the following procedures will be followed to ensure that priority rights of competing TSRs are honored and that additional capacity released by undesignation requests is made available to the market based on the priority rights in the Tariff.
The undesignation of a DNR does not result in capacity being released to the market unless and until the Customer CONFIRMS the undesignation request (in the case of a stand-alone undesignation request) or CONFIRMS both the undesignation request and the Alternate Network Resource request (in the case of simultaneously submitted requests). If the undesignation was accompanied by a simultaneous request to redesignate the existing DNR in the future, the capacity release will be temporary, unless the resource is undesignated to the end of the term on the NITSA.
3.1. Undesignation of a Short-Term Network Resource
In order to undesignate all or a portion of a short-term DNR, the Customer shall utilize the following process:
Step 1: Fax Request Form to ICT
The Customer must first provide written notice of its intent to undesignate an existing DNR via facsimile to the ICT Tariff Administration Desk at (317) 249-7992, using the standard form Un-Designation of Designated Network Resources. The form is available at:
http://www.oasis.oati.com/EES/EESdocs/FAXForms%2Ehtm
On the form, the Customer shall:
· identify the DNR to be undesignated by providing the ARef of the parent reservation(s) granting the DNR;
· indicate the capacity of the DNR that will be undesignated; and
· indicate the date and time on which the permanent undesignation should become effective, or the START_TIME and STOP_TIME during which the temporary undesignation should be effective.
Step 2: Confirmation of Receipt Of Request
After sending the facsimile notice form referenced above, the Customer must contact the ICT Tariff Administration Desk to confirm that the ICT has received undesignation form, and review the information provided therein with the ICT.
Step 3: ICT Annulment or Recall
Within the Transmission Provider response time limits described in Section IV.1 of these business practices, the ICT will ANNUL or RECALL the existing DNR in accordance with information provided by the Customer in the facsimile notice form.
Short-term requests for transmission service related to a request for undesignation of a network resource cannot be simultaneously evaluated under the current AFC Process.
3.2. Undesignation of a Long-Term Network Resource
In order to undesignate all or a portion of a long-term DNR, the Customer should conform to the following process:
Step 1: Enter Request(s) on OASIS
In order to indicate to the ICT that the Customer wants to undesignate a long-term DNR permanently or temporarily, the Customer shall submit a 1 MW “proxy” request as a Network Service Request on OASIS.
The 1 MW “proxy” request shall:
· indicate the date and time on which the permanent undesignation should become effective, or the START_TIME and STOP_TIME during which the temporary undesignation should be effective;
· include the following statement in the OASIS customer comment field, “Undesignation information to follow via email to EntergyTariffAdministration@misoenergy.org..”
To request simultaneous designation of an Alternate Network Resource, the Customer must enter such request on OASIS immediately after entering the request to undesignate the existing Network Resource. The request for alternate designation must include: (i) an attestation in accordance with Section 30.2 of the Tariff (ii) the ARef of the 1 MW proxy request in the customer comment field, along with the following statement, “Undesignation information to follow via email to EntergyTariffAdministration@misoenergy.org.,” and (iii) all other necessary information required under Section 29.2 of the Tariff.
Requests for a clustered study of a permanent undesignation and any other request(s) for transmission service, will be evaluated per OATT Attachment D, Section 7, and must be submitted proximately in the queue. The 1 MW “proxy” request shall include (i) an attestation in accordance with Section 30.2 of the Tariff (ii) the ARef(s) of the related transmission service request(s) being clustered in the customer comment field along with the following statement, “Undesignation information to follow via email to EntergyTariffAdministration@misoenergy.org.,” and (iii) all other necessary information required under Section 29.2 of the Tariff.
To request a concomitant study of a temporary undesignation and any other request(s) for transmission service, the 1 MW “proxy” request shall include (i) an attestation in accordance with Section 30.2 of the Tariff (ii) the ARef(s) of the related transmission service request(s) being studied concomitantly in the customer comment field along with the following statement, “Undesignation information to follow via email to EntergyTariffAdministration@misoenergy.org.,” and (iii) all other necessary information required under Section 29.2 of the Tariff.
Following the CONFIRMATION of all related TSRs, the ICT will update the seller comments to include each related TSR with all related ARefs in , including updating the comments on the 1 MW “proxy” request to identify the actual ARef being undesignated.
Step 2: Email Request Form to ICT
The Customer must email “Form to Undesignate or Cluster (Alternate Network Resource Designation) Network Resources” to EntergyTariffAdministration@misoenergy.org.. The form is available at:
http://www.oasis.oati.com/EES/EESdocs/FAXForms.htm
On the form, the Customer shall:
· identify the DNR to be undesignated by providing its ARef;
· indicate that it is requesting an undesignation of the relevant DNR in the appropriate column;
· indicate the capacity of the DNR that will be undesignated; and
· indicate the date and time on which the permanent undesignation should become effective, or the START_TIME and STOP_TIME during which the temporary undesignation should be effective.
· If an Alternate Network Resource designation or a clustered or concomitant study of the undesignation request and related request(s) for transmission service is desired by the Customer, the ARef(s) of the related transmission service request(s) must also be provided.
Step 3: Confirmation of Receipt of Request
After providing the facsimiled or emailed form referenced above to the ICT, the Customer must contact the ICT to confirm that the ICT has received the request to undesignated or cluster, and review the information provided therein with the ICT.
Step 4: Processing the Request(s)
For undesignation requests without a simultaneously submitted request for transmission service, the ICT will set the 1 MW stand-alone undesignation to ACCEPTED, and the Customer will have 15 days to CONFIRM or the request will be RETRACTED. Once the request is CONFIRMED, the ICT will then RECALL the 1 MW “proxy” request, as well as the requested DNR in accordance with the information provided by the Customer. Once CONFIRMED, the ICT will update the seller comments be updated on all related TSRs to reflect the [ARef] of the request represented by the 1 MW “proxy” request.
For undesignation requests with a simultaneously submitted request for transmission service, the ICT will issue a SIS Agreement to the Customer in accordance with the Tariff. If the SIS Agreement is executed by the Customer and returned to the ICT within the time limits specified in the Tariff, Section 3.3 below will apply. If the SIS Agreement is not executed by the Customer within the time limits specified in the Tariff, the ICT will DECLINE the request.
3.3. Evaluation of Long-Term Request Coupled with a Related Request for Transmission Service
3.3.1. Simultaneous Designation of an Alternate Network Resource and an Undesignation Request
For requests to simultaneously request designation of an Alternate Network Resource and undesignation of an existing Network Resource, per OATT Attachment D, the designation will be studied both with the undesignation and without. The Customer will receive two (2) System Impact Study Agreements.
If the Customer email notification under Section 3.2 above includes a request to study the Alternate Network Resource request with undesignation of the existing DNR request, the ICT will evaluate the requests in a coordinated manner. The SISs will be conducted in accordance with Section 3.2.2.2 of Attachment D of the Tariff.
If the SIS indicates that the Alternate Network Resource designation request can be accommodated, in whole or part, without the undesignation of the existing Network Resource and without the need for transmission upgrades, the Customer may elect to CONFIRM only the request to designate the Alternate Network Resource to obtain service. If the Customer fails to CONFIRM any related request by the applicable deadline, unconfirmed requests will be RETRACTED at the end of the deadline.
If the SIS indicates that the Alternate Network Resource designation request can only be accommodated, in whole or part, with the undesignation of the existing resource, but without the need for transmission upgrades, the Customer must CONFIRM both: (i) the request to undesignate the existing DNR; and (ii) the request to designate the Alternate Network Resource to obtain service. If the Customer fails to CONFIRM both requests by the applicable deadline, both requests will be RETRACTED at the end of the deadline, and the DNR will retain its designated Network Resource status.
If the SIS indicates that transmission upgrades are necessary to accommodate the requests, the ICT will provide the Customer with a Facilities Study Agreement (FSA) within the deadlines specified in Entergy’s OATT. If the FSA is not executed by the Customer by the applicable deadline, the requests will be DECLINED by the ICT, and the DNR will retain its designated Network Resource status.
3.3.2. Clustered Evaluation of a Permanent Undesignation Request with any other Transmission Service Request(s)
For requests to cluster a permanent undesignation request with any other transmission service request(s), the requests will be considered as a “Queue Cluster” pursuant to Section 7 of Attachment D.
If the Customer email notification under Section 3.2 above includes a request to cluster the permanent undesignation request with any other transmission service request(s), the ICT will perform a single SIS to evaluate the requests in a coordinated manner.
If the SIS indicates that the clustered requests can be accommodated, in whole or part, without the need for transmission upgrades, the ICT will set the requests to ACCEPTED or COUNTEROFFERED, and the Customer must set the status to CONFIRMED or REBID: (i) the request to undesignate the existing DNR; and (ii) any of the desired related transmission service request(s). If the Customer fails to ultimately confirm the requests by the applicable deadline(s), the requests will be RETRACTED at the end of the deadline(s), and the DNR will retain its designated Network Resource status.
If the SIS indicates that transmission upgrades are necessary to accommodate the requests, the ICT will provide the Customer with a Facilities Study Agreement (FSA) within the deadlines specified in Entergy’s OATT. If the FSA is not executed by the Customer by the applicable deadline, the requests will be DECLINED by the ICT, and the DNR will retain its designated Network Resource status.
3.3.3. Concomitant Evaluation of a Temporary Undesignation Request with any other Transmission Service Request(s)
Requests to concomitantly evaluate any other transmission service request(s) with a temporary undesignation request will be studied pursuant to Section 30.3 of the OATT.
If the Customer email notification under Section 3.2 above includes a request to concomitantly evaluate any other transmission service request with the temporary undesignation request, the ICT will perform a single SIS to evaluate the requests in a coordinated manner. The SIS is conducted in accordance with Section 3.2 of Attachment D and Section 10 of Attachment E (TSR Business Practices).
If the SIS indicates that the requests can be accommodated, in whole or part, without the need for transmission upgrades, the Customer must CONFIRM: (i) the request to undesignate the existing DNR; and (ii) any of the desired related transmission service request(s). If the Customer fails to CONFIRM the requests by the applicable deadline, the requests will be RETRACTED at the end of the deadline, and the DNR will retain its designated Network Resource status.
If the SIS indicates that transmission upgrades are necessary to accommodate the requests, the ICT will provide the Customer with a Facilities Study Agreement (FSA) within the deadlines specified in Entergy’s OATT. If the FSA is not executed by the Customer by the applicable deadline, the requests will be DECLINED by the ICT, and the DNR will retain its designated Network Resource status.
3.4. Requests Subject to the AFC Process
After the relevant requests are CONFIRMED by the Customer, any additional capacity released by the undesignation is made available to other Customers through the Base Case Model updating process for FSs, SISs, and AFC calculations. The TSRs with the highest priority right to capacity released by the undesignation request are the Long-Term PTP Service TSRs and requests to designate Network Resources on an annual basis that were submitted prior to the undesignation request but remaining pending in the FS queue. The TSRs with the next highest priority are the Long-Term Firm PTP Service and Network Service TSRs that were submitted after the undesignation request and pending in the SIS and the AFC Process. The TSRs with the lowest priority are the Short-Term Firm PTP Service TSRs and Non-Firm TSRs that were submitted after the undesignation request and are pending in AFC Process queue.
Additional capacity released by an undesignation request is made available to each group of TSRs consistent with these priority rights by: (i) updating AFC calculations and the Base Case Models used in FSs and SISs to reflect undesignation requests and higher priority TSRs; (ii) evaluating the TSRs in each queue in the order requests were submitted; and (iii) respecting the preemption rights of higher priority TSRs.
4. Requesting Network Service from an NRIS Generator
This Section VII.X governs requests for service from NRIS-qualified generators.
All sources available for transmission service are currently listed on the “Valid Source List” at http://www.oasis.oati.com/EES/EESDocs/SourceSinkPractices.html. Once a generator is qualified for NRIS status, that status, along with the date that the generator qualified for that status, will be posted in the “Valid Source List” page.
Requests for network service of one or more years from an NRIS generator must be submitted using the NRIS Firm Yearly Network service type, and are subject to study under Attachment D of Entergy’s OATT. The customer copy of the System Impact Study Report, provided to the Customer by email from the ICT, provides any limiting element/constraining element pairs identified in the study. The customer copy of the report will also provide the Outage Transfer Distribution Factor (OTDF) for each of the identified limiting element/constraining element pairs. The OTDF is the percentage of generation that would flow on a limiting element after a contingency occurs. The limiting element/constraining element pairs identified in the customer copy of the System Impact Study Report and their corresponding OTDFs will provide the basis for any congestion management charges to be billed to the Customer if any such charges are incurred to accommodate a confirmed request for network service from an NRIS-qualified generator.
If the System Impact Study determines that full amount of requested capacity is available as firm Network Service, the ICT will ACCEPT the request pursuant to Attachment D of Entergy’s OATT. The Customer will not be subject to any congestion management charges.
If the System Impact Study determines that full amount of requested capacity is not available as firm Network Service, the ICT will contact the Customer and offer two (2) options:
SIS Option 1: Have the ICT COUNTEROFFER the TSR for the full amount of requested capacity
SIS Option 2: Proceed to a Facilities Study and leave the TSR in STUDY status
If the Customer selects SIS Option 1, the Customer may then (1) REBID for only the amount of capacity determined by the System Impact Study to be available as firm service and, therefore, not subject to congestion managements charges, or (2) confirm the COUNTEROFFER or REBID for an amount of capacity greater than determined by the System Impact Study to be available as firm service up to the total amount of the COUNTEROFFER and, with the MW amount over the COUNTEROFFER amount being subject to congestion management charges, based on the limiting element/constraining element pairs and corresponding OTDF identified in the System Impact Study.
If the Customer elects to REBID for capacity that would be subject to congestion management charges, the Customer will be required to sign a Long Term Firm Network Integration Transmission Service Agreement (NITSA) providing for billing congestion management charges based on the results of the System Impact Study. In addition to charges for Network Service based on load ratio, the service will be subject to associated congestion management charges, calculated after-the-fact, and billed to the Customer on a monthly basis. The NITSA will be filed with FERC as a non-conforming agreement.
If the Customer selects SIS Option 2 and proceeds to a Facilities Study, the ICT will provide the Customer with a Facilities Study Agreement no later than 30 days after the System Impact Study Report was posted. To proceed to Facilities Study, the Customer must execute and return the Facilities Study Agreement within 15 days of its issuance. If the Facilities Study Agreement is not executed by the Customer and returned to the ICT within 15 calendar days of its issuance, the TSR will be DECLINED by the ICT.
The ICT will post completed Facilities Study Reports on OASIS and notify the requesting Customer that the report is available. The ICT will also provide the Customer with a document that provides (1) a listing of the limiting element/constraining element pairs, if any, determined in the Facilities Study and (2) the OTDF for each of the limiting element/constraining element pairs determined in the Facilities Study. The limiting element/constraining element pairs and their corresponding OTDFs identified in the Facilities Study will provide the basis for any congestion management charges incurred to accommodate network service from the NRIS generator to the Network Customer’s designated Network Load.
If the Facilities Study determines that the full amount of requested capacity is not available as firm service, the ICT will send a form via facsimile and email to the Customer and offer three (3) options:
FS Option 1: Build upgrades to accommodate all requested service as firm service, free from congestion management charges.
FS Option 2: Take service, or portion thereof, subject to any applicable congestion management charges based on the Facilities Study.
FS Option 3: Withdraw the request.
The Customer has 15 days to execute and return the form to the ICT or the TSR will be REFUSED.
If the Customer selects FS Option 1, the Customer should refer to Attachment D of the Entergy OATT regarding TSR processing.
If the Customer selects FS Option 2, the ICT will COUNTEROFFER the TSR for the full amount of requested capacity. The Customer will then have the option to (1) REBID for only the capacity determined by the Facilities Study to be available as firm service and, therefore, not subject to congestion managements charges, or (2) REBID for an amount of capacity greater than determined by the Facilities Study to be available as firm service, up to the total amount requested on the original TSR, with the amount over the COUNTEROFFER being subject to congestion management charges based on the limiting element/constraining element pairs and corresponding OTDF identified by the Facilities Study.
If the Customer elects to REBID for capacity subject to congestion management charges, the Customer must sign a revised NITSA providing for the billing of any congestion management charges associated with accommodating the service, based on the results of the Facilities Study. In addition to charges for Network Service based on load ratio, the service will be subject to associated congestion management charges, calculated after-the-fact, and billed to the Customer on a monthly basis. The NITSA will be filed with FERC as a non-conforming agreement.
If Supplemental Upgrade(s) are agreed to by the Network Customer per the results of a Facilities Study Report, and as reflected in its NITSA, congestion management charges will not be associated with network service for that Network Customer that impacts such upgrades.
If the Customer selects FS Option 3, the Customer will withdraw the request.
Requests for network service of less than one year from an NRIS-qualified generator using the NRIS Firm Daily, Weekly or Monthly Network service type will be granted by the ICT, subject to charges for all congestion management necessary to maintain that service. Such requests will not be COUNTEROFFERED for the amount of service available as firm service and not subject to congestion management charges.
Any congestion management charges associated with accommodating Network Service from an NRIS generator will be based on the capacity available at the time the request is evaluated, as indicated in the Request Evaluation Detail available on OASIS. The Request Evaluation Detail will list all flowgates for which there was insufficient AFC and the amount of AFC unavailable for each of those flowgates.
To secure capacity from an NRIS-qualified generator not subject to congestion management charges, the Customer should submit a standard request for Firm Daily, Weekly and Monthly Network Service from the NRIS-qualified generator, i.e., a request that does not use the “NRIS Network Service” type. Such a request will be COUNTEROFFERED by the ICT for the portion of the service that is available as firm service. To receive the remaining portion of service subject to congestion management charges, the Customer may then submit a request for NRIS Firm Daily, Weekly or Monthly Network. Customers are encouraged to use Scenario Analyzer prior to submitting service requests to evaluate the amount of capacity that may be available without congestion management charges in addition to the charges for Network Service attributable to service the Network Customer’s designated Network Load.
Any Customer that desires NRIS Firm Daily, Weekly or Monthly or Yearly Network Service from an NRIS-qualified generator subject to congestion management charges is required to contact Wayne Warren in the Transmission Provider’s Transmission Services Group, at 601-985-2626 and execute a NITSA NRIS Pricing Addendum to its NITSA to memorialize the Customer’s agreement to pay all charges for congestion management necessary to accommodate its service from an NRIS-qualified generator. The revised NITSA will be filed with FERC as a non-conforming agreement.
5. Removing Conditions from Long Term Network Service
Customers with confirmed requests for designation of a Network Resource subject to conditions listed in the service agreement may request that the conditions be removed. Such request is made by submitting a request to undesignated the Network Resource and then designate the same resource, using the cluster study request process outlined in section VII.3.2 of these Business Practices, with the addition of the following customer comment “Request to remove conditions on Network Service.” The two requests will be evaluated as a clustered study.
The portion of the Network Resource subject to the redispatch conditions will be evaluated only for the contingencies identified in the original SIS. It is assumed that for all other contingencies, the Network Resource has firm service not subject to other redispatch condition.
· Base Case has unit at DNR level only for the portion not subject to redispatch.
· Change Case has unit at full, requested DNR level.
· The contingency list contains only those contingencies listed in the original DNR System Impact Study requiring the conditions to be placed on the Network Resource.
· All other technical aspects of the study will be the same as any other study
VIII. AFC BUSINESS PRACTICES
1. Software Applications Used in AFC Process
A list of the software applications used in the AFC Process is included as Attachment 2 to this document.
2. Frequency of Resynchronizations
Entergy's ATCID describes the minimum resynchronization frequency for AFC values in the Operating, Planning and Study Horizons. To the extent the Transmission Provider conducts more frequent resynchronizations on a regular basis, this Business Practice describes that frequency. Currently, the only more frequent resynchronizations being conducted on a regular basis are those in the Planning Horizon and Study Horizon. Planning Horizon AFC values are currently resynchronized four times every day. Study Horizon AFC values are currently resynchronized twice per month. More frequent resynchronizations may also be conducted for, among other reasons, requests by the ICT, database or software or server maintenance and troubleshooting for powerflow solution divergence.
3. Submission Of Load and Generation Forecast Data for Operating and Planning Horizons
This Section VIII.3 and the documents incorporated by reference herein provide guidelines for the submission of Load and Generation Forecast data for the Operating and Planning Horizons of the AFC Process pursuant to AFC Process pursuant to Entergy's ATCID.
The Transmission Provider maintains a “Load Customer Upload” website to allow Customers, or their designated agent using the Customer’s OASIS certificate or DBA function, the ability to upload the required data files into the AFC Process. The site is accessible via OASIS, using the link for “Entergy Load Customer Upload” provided under Entergy Information Links (INFO.HTM) on the OASIS General Information Page. The Load Customer Upload website can also be accessed using the following link:
https://wpp.entergytransmission.com/LCU
Detailed instructions and guidance for using the Load Customer Upload website are provided in the “Load Customer Upload User’s Manual,” which is posted on OASIS and can be accessed using the following link:
http://www.oasis.oati.com/woa/docs/EES/EESdocs/LCU_UsersManual.doc
Long Term Firm Point to Point and Network Service reservations may be included in UC Format Files. Specific format requirements for uploaded all data files is provided in the “Functional Specifications Document,” which is posted on OASIS and can be accessed using the following link:
http://www.oasis.oati.com/woa/docs/EES/EESdocs/NC_LF_UC_DataInputFunctionalSpecification.doc.
4. Submission Of Generation Forecast Data for the Study Horizon
This Section VIII.4 governs the submission of generation forecast data for the Study Horizon under Entergy's ATCID.
4.1. Network Customers/LSEs that do not own generation capacity equal to or in excess of their load
Network Customers/Load Serving Entities (“LSEs”) that do not own generation capacity equal to or in excess of their respective loads must submit a Reservation priority order stack for all Firm Network Resource Reservations (including Reservations for the Network Customer’s/LSE’s own generating resources and PPAs) for inclusion in the AFC Study Horizon models. The priority order stack provided by the Network Customer/LSE will be implemented in the monthly powerflow models developed for the calculation of Study Horizon AFC values during each update to the powerflow models. Once a Reservation stack is provided, it will be utilized in all subsequent updates to the monthly powerflow models until updated information is provided by Network Customer/LSE. Additionally, any Reservation priority order stack that is provided will be implemented in all monthly powerflow models developed for the entire Study Horizon.
Network Customers and LSEs should submit a priority order stack for Firm Resource Reservations in the following format:
· A list of all Firm Resource Reservations in sequential order with the following data identified for each Firm Resource Reservation listed:
TABLE 4-1
|
Load Serving Entity |
||||||||||
|
OASIS ID Number |
Customer |
POR |
POD |
Source |
Sink |
Service Name |
Capacity |
Begin Time |
End Time |
Segment Information (Capacity, Begin Time, End Time) |
|
Resource Reservation #1(Highest Priority): |
|
|
|
|
|
|
|
|
|
|
|
Resource Reservation #2 (Second Highest Priority): |
|
|
|
|
|
|
|
|
|
|
|
Resource Reservation #N (Lowest Priority): |
|
|
|
|
|
|
|
|
|
|
Network Customers or LSEs that do not own generation capacity equal to or in excess of their load that fail to submit a Reservation priority order stack for Firm Resource Reservations are subject to the modeling practices defined in Entergy's ATCID.
4.2. LSEs/Network Customers with generating capacity equal to or in excess of their Network Load
Service to loads for Network Customers or LSEs that own generation capacity equal to or in excess of their respective load is represented in AFC Study Horizon powerflow models by: (i) modeling all PPAs designated as Network Resources in monthly or yearly increments or for which Secondary Network Service has been obtained in monthly increments; and (ii) dispatching owned generating facilities that are Network Resources for that Network Customer or LSE to meet any shortfall between those PPAs and load plus losses.
Network Customer or LSEs that own generation capacity equal to or in excess of their load must submit a generator merit (priority) order stack for owned Firm resources for inclusion in the AFC Study Horizon models. This merit (priority) order stack will be utilized to determine the commitment and dispatch of the Network Customer’s or LSE’s owned generating facilities that are Network Resources to meet any capacity shortfall. These resources will be incorporated in the monthly powerflow models during each update of the AFC Study Horizon. Once a generator merit (priority) order stack is provided by a Network Customer or LSE, the stack will be utilized in the commitment and dispatch of the Network Customer’s or LSE’s owned generating resources in all subsequent updates of the monthly powerflow models until the Network Customer or LSE provides updated information. Additionally, the generator merit (priority) order stack that is provided by the Network Customer or LSE will be implemented in all monthly powerflow models developed for the entire Study Horizon.
Data requirements for submission of a generator merit (priority) order stack file are as follows:
· The generator merit (priority) order stack file defines the order in which owned generating units shall be committed and dispatched to satisfy the amount of generation needed by the Network Customer or LSE in a particular powerflow model. All generating units included in the generator merit (priority) order stack file will be committed and dispatched between the defined machine limits (generator Pmin and Pmax values in the powerflow model) in the order that the units are listed in the file.
· The generator merit (priority) order stack cannot include Firm Resource Reservations that source from generating facilities not owned by the Network Customer or LSE.
· Each generating unit included in the AFC Study Horizon models and owned by the Network Customer or LSE can only be included once in the generator merit (priority) order stack file. A Network Customer or LSE may not elect to dispatch portions of generating units or specify maximum dispatch of generating units in the generator merit (priority) dispatch file. A Network Customer or LSE, however, can dispatch a PPA to the extent that the Network Customer or LSE is contractually entitled to the full output of the relevant generation facility.
· The generator merit (priority) order stack shall contain all owned generating units that are included in the AFC Study Horizon models. Each generating unit at a facility owned by the Network Customer or LSE shall be listed separately.
· File format for the generator merit (priority) dispatch file is as follows:
TABLE 4-2
|
Network Customer or Load Serving Entity Name |
||||
|
Unit Common Name |
Unit PSS/E Name |
PSS/E Bus Number |
PSS/E Machine ID |
TSR OASIS ID Number(s) |
|
Priority #1 Unit: |
|
|
|
|
|
Priority #2 Unit: |
|
|
|
|
|
Priority #3 Unit: |
|
|
|
|
|
Unit with Last Priority: |
|
|
|
|
Network Customers or LSEs that own generation capacity equal to or in excess of their respective loads that fail to submit a generator merit order stack for owned Firm resources are subject to the modeling practices defined in Entergy's ATCID.
Pursuant to Entergy's ATCID, all customers with generating facilities (“Generating Facility Owners”) are required to provide notification of a planned/unplanned generating facility outage or generating facility de-rate.
The ICT Tariff Administration Group will review and validate the Reservation priority order or generator merit (priority) order stack provided by the Network Customer or LSE and may contact the Customer providing the data with questions or comments. All information provided by Customers and SPO will be incorporated in the next regularly scheduled AFC Study Horizon update greater than one week in the future following receipt, review and approval of the information by the ICT Tariff Administration Group.
All data and information required by this Section 4 must be submitted via email to ICT:
5. Generating Facility Operating Characteristics
Pursuant to Entergy's ATCID, Generating Facility Owners are required to provide certain information concerning generator operating characteristics and generator availability in the AFC Process. This Section VIII.5 sets forth both the timing requirements and the submittal process for such information.
The Transmission Provider has created a template for submitting generating facility operating characteristics and availability. This template is included as Attachment 3 to these TSR Business Practices. Generating Facility Owners are required to complete this template for each unit located at a specific generating facility and should provide updated information at least annually. In the event of a change to a generating facility’s operating characteristics or availability, Generating Facility Owners are required to provide a completed template at least 30 days prior to the change (for future changes) and within 15 days after an unforeseen change in a generator’s capability or availability.
The ICT will review and validate the generator operating characteristics data provided by the Generating Facility Owner and may contact the Customer providing the data with questions or comments. All data supplied by Generating Facility Owners will be incorporated in future AFC Operating Horizon, Planning Horizon, and Study Horizon powerflow models if applicable, following receipt and review of the information by the ICT. Generator operating characteristics will be implemented in all subsequent updates to AFC Operating Horizon, Planning Horizon, and Study Horizon models if applicable until updated information is provided
Generating Facility Owners interconnected to the Transmission System must use the template provided to supply generating facility operating characteristics and other data for use in the AFC process. Completed templates must be provided via email to ICT:
6. Transmission Projects Not Currently-In Service
Entergy's ATCID provides that these TSR Business Practices will describe how transmission construction projects not currently in-service are treated for purposes of the EMS-Based Models and the Monthly Base Case Models used in the AFC Process. Transmission service granted through the SIS process conditional on a prospective transmission facility addition or upgrade will be included in the AFC Study Horizon powerflow models.
Under the AFC Process, prospective transmission projects are modeled “out of service” in these Base Case Models until construction is complete and the facilities are placed into service. These transmission projects include the following:
· Transmission upgrades that have been determined in a FS as necessary to accommodate a Network Resource or PTP Service Reservation;
· Transmission upgrades that have been determined in a FS as necessary to accommodate a request to interconnect a generating facility; and
· Transmission upgrades in the Transmission Provider’s Construction Plan.
Transmission upgrades required to physically interconnect a prospective generator to the Transmission System (e.g., new substations required for generator interconnection and new radial transmission facilities required to interconnect the new generator) will be included in the AFC Base Case Models starting in the month in which the generating facility is added to the AFC process, provided that the generating facility has executed a Large Generator Interconnection Agreement (“LGIA”) or Small Generator Interconnection Agreement (“SGIA”).
7. Zonal Import Limits (Study Horizon)
This Section VIII.7 sets forth the methodology used by the Transmission Provider to enforce zonal import limits in the AFC Process as referenced in Entergy's ATCID. The Transmission Provider only applies a zonal import limit for Amite South in the Study Horizon; no zonal import limited is applied for WOTAB.
An import limit for the Amite South load pocket is enforced in all AFC Study Horizon powerflow models. In order to calculate this import limit, the Transmission Provider performs a simulated power transfer from outside the Amite South load pocket into the region. The Amite South import limit is established at the power transfer level into the region with all transmission facilities in the region loaded at or below the rating of the facility under contingency. Next, each Monthly Base Case Model of the Study Horizon is analyzed using a zonal reporting function of PSSE to determine the Amite South’s import level within the model after all generation in the Transmission Provider’s Control Area is dispatched based on a Priority Dispatch file.
The Monthly Base Case Models will be re-dispatched to enforce the import limit in the Amite South load pocket rather than on a Control Area basis depending on the following criteria:
· If the Amite South load pocket import level in the Monthly Base Case Model is less than or equal the calculated import limit, no dispatch adjustments are made.
· If the import level in the Monthly Base Case Model is greater than the Amite South import limit, committed generation in the Amite South load pocket is scaled up based on merit order until the import into the area is equal to the import limit. The dispatch of generation resources in the Transmission Provider’s Control Area located outside the Amite South load pocket is then adjusted down based on merit order to ensure that the total generation dispatch in the Transmission Provider’s Control Area is balanced.
This Section VIII.8 sets forth the methodology the Transmission Provider will use to determine the counterflow percentages used in AFC calculations as indicated in Entergy's ATCID.
8.1. Operating and Planning Horizons
The counterflow percentage utilized in the Operating Horizon and Planning Horizons is at 100% (0% removal from the baseflow).
The Transmission Provider reviews scheduling data and other operational experience to determine counterflow percentages and evaluates the reasonableness of the established counterflow percentages through a biennial review. The Transmission Provider then provides the results of this biennial review to the ICT for evaluation. The methodology utilized during this biennial review to determine the percentage of counterflow includes: (i) a comparison of Reservations to schedules; and (ii) a determination of the percent of Reservations that are scheduled. This comparison and percentage calculation will be as shown below in support of the current counterflow percentage for the Study Horizon.
Reservations included in this analysis will be all Reservations from the previous year that impact the Hour Ending 1600, excluding Reservations that do not require scheduling (such as Network Service) from native generation used to serve the Customer’s own load. Firm Redirects and Resales are included in the Reservations, but their impact is removed from the parent Reservations to ensure accuracy. All schedules from the previous year are then cross-referenced to determine the Megawatt Hours (MWhs) scheduled for each Reservation. The results of the Reservation query and the cross-referencing of the previous year’s schedules are then organized by type of service (Network vs. PTP), Class (Firm, Non-Firm), and service increments (hourly, daily, weekly, monthly, and yearly) as depicted above. The results are then analyzed to determine the percentage of counterflows by comparing the percentage of MW scheduled for Firm PTP Service and Non-Firm PTP Service by service increment and setting the counterflow percentage accordingly.
The Study Horizon is primarily comprised of monthly and yearly Firm Reservations; therefore, only the data for Firm monthly PTP Service and Firm yearly PTP Service Reservations will be used to set the PTP Service counterflow percentage for the Study Horizon. In accordance with the data presented below, counterflows for Firm PTP Service Reservations in the Study Horizon will be set at 63% (37% removal from the baseflow). The percentage was calculated by dividing the aggregate monthly and yearly PTP Service capacity scheduled by the aggregate monthly and yearly MW reserved. This data will be updated in accordance with Entergy's ATCID.
|
Study Horizon |
|||
|
Firm Point to Point |
MW Reserved |
Capacity Scheduled |
% Scheduled |
|
MONTHLY |
493,145 |
343,614 |
70% |
|
YEARLY |
535,191 |
302,033 |
56% |
|
TOTAL |
1,028,336 |
645,647 |
63% |
9. Maintaining Sources and Sinks
This Section VIII.9 is applicable to all generating facilities interconnected to the Transmission System and border generating facilities interconnected to neighboring transmission systems which have a valid Interconnection and Operating Agreement (“Interconnection Agreement”), LGIA, or SGIA and all Customers, including Network Customers under the Tariff and grandfathered Customers. This Section VIII.9 is also applicable to all Embedded Control Areas and External Control Areas, including generation-only and load-only Control Areas. For purposes of this business practice, any border generating facility as defined in Attachment C to the Tariff is treated as a generating facility directly interconnected to the Transmission System.
9.2. AFC Source Maintenance Methodology
9.2.1. New Generator Interconnection
New generation interconnection requests for generating facilities received via the Large Generator Interconnection Process (“LGIP”) or Small Generator Interconnection Process (“SGIP”) will be included in AFC Process powerflow models and added as a Source definition in the AFC process following the execution of the LGIA or SGIA or the filing of such agreements on an unexecuted basis at FERC. If the in-service date indicated in the LGIA or SGIA is beyond the current AFC horizon, then the new Source will be added in the AFC Process before the in-service date enters the current AFC horizon timeframe. Prospective generators will be modeled “offline” in all active Operating, Planning, and Study Horizon powerflow models that precede the in-service date indicated in the LGIA or SGIA. The new generation facility will be dispatched according to the generation dispatch rules specified in Entergy’s ATCID in AFC Base Case Models following the in-service date indicated in the LGIA or SGIA. If the in-service date of a new generation facility with an executed LGIA or SGIA is after the first day of the month within the current Study Horizon timeframe, any Transmission Service originating from the new generating facility will be modeled in the next available monthly powerflow model and in all remaining powerflow models active within the current AFC Horizons and during which Transmission Service is reserved. Once the new generation facility is added as a valid AFC Source, a new proxy flowgate (generator Pmax flowgate) will be included in the AFC Process reflecting the total capability of the new source.
Unit parameter data and interconnection data provided by the Customer in the LGIA or SGIA will be utilized for modeling purposes, until such time as that information is updated through the updating process described in Section VIII.5 of these TSR Business Practices.
9.2.2. New Embedded or External Control Area (Excluding Control Areas with no Generating Resources)
Any new generation-only Embedded Control Area or External Control Area will be included in AFC powerflow models and corresponding processes no sooner than the entity commences certified control area operations and as soon as reasonably possible afterwards. In addition, all terms and conditions detailed under Attachment E to the Tariff addressing ‘Control Area Designation Requirements’ must be satisfied in order for an Embedded Control Area or External Control Area to be included as a Source in the AFC process. When the new Embedded Control Area or External Control Area is added as a source in the AFC process, a corresponding proxy flowgate (tie-cap flowgate) will also be included in the AFC process. The limit of this tie cap proxy flowgate will be derived from one of the following: (i) the thermal capability of all transmission facilities that define the interface; or (ii) prevailing contractual agreement between the parties or mutually agreed upon value between the parties.
Milestones that must be achieved in order for a new or existing generator to be included in the AFC Process as a generator-only Embedded Control Area or External Control Area include, but may not be limited to, the following: receipt of balancing authority certification from the regional reliability organization, implementation of all required metering and telemetry, implementation of required updates to the Transmission Provider’s Energy Management System (EMS), and execution of a Balancing Authority Area Operating Procedure agreement with the Transmission Provider.
9.2.3. Modifications to Source Definitions
Generation facility total plant output up-rate requests submitted via the LGIP or SGIP will be included in the AFC Process powerflow models and corresponding processes after the earlier of when the LGIA or SGIA is: (i) executed; or (ii) the unexecuted agreement is filed with FERC for approval. If the in-service date indicated in the LGIA or SGIA for the existing plant total output increase is beyond the current AFC horizon, then the new Source definition will be added to the AFC Process when the in-service date enters the current AFC horizon timeframe.
Unit parameter data and interconnection data provided by the Customer in the LGIA or SGIA will be utilized for modeling purposes, until such time as that information is updated through the updating process described in Section VIII.5 of these TSR Business Practices. In addition, the existing generator Pmax proxy flowgate rating included in the AFC Process will be altered to reflect the total capability of the generation facility.
Any modification to an existing Embedded Control Area or External Control Area definition to include a new generating resource moving from the Transmission Provider’s Control Area to that Embedded Control Area or External Control Area will be modeled no sooner than the generator commences operation in the new Control Area and as soon as reasonably possible afterwards. In addition, all conditions detailed under Attachment E related to Control Area Designation Requirements must be satisfied in order for an Embedded Control Area or External Control Area (excluding load-only Control Areas) to be included as a Source in the AFC Process. Any modifications made to an existing Source definition may result in AFC proxy flowgate (tie-cap flowgate) rating changes.
9.2.4. Removal of Active Source from the AFC Process
Generators currently interconnected to the Transmission System must have a valid Interconnection Agreement, LGIA, or SGIA to retain an active Source definition in the AFC Process. Any generator interconnected to the Transmission System without a valid Interconnection Agreement, LGIA, or SGIA will be removed as a Source from the AFC Process effective on the date that the applicable interconnection agreement, LGIA, or SGIA is terminated (or as soon as reasonably possible afterwards). Likewise, any Embedded Control Area or External Control Area without all required documentation will be removed as a Source from the AFC Process. The required documentation includes, but is not limited to, the following: balancing authority certification from the regional reliability organization and a current Balancing Authority Area Operating Procedure agreement with the Transmission Provider. Generator interconnections and LSEs subject to grandfathered agreements must be evaluated on a case-by-case basis.
9.3. AFC Sink Maintenance Methodology
9.3.1. New Transmission Customer
In the event a LSE seeks to become a Network Customer for the first time and wishes to designate a Network Resource on a short-term basis (e.g., on a daily, weekly or monthly basis), a new Sink definition will be incorporated in the AFC Process for that Customer as soon as reasonably possible after a SIS has been performed for the new Sink, the LSE has executed a Service Agreement, all metering, telemetry and necessary equipment is in-service, and the Customer has satisfied the additional requirements listed below. Until a Service Agreement for Network Service has been executed, the Customer has the option to serve the new Sink on an interim basis using either short-term firm or non-firm PTP Service under a valid Service Agreement.
· The requirements for a new Network Customer to add a Sink to the AFC process under this Section 9.3.1 are as follows:
· Confirmation of at least one year of Transmission Service;
· Provision of all information required under Sections 28, 29 and 30 of the Tariff;
· Provision of a list of generators/PPA which are long-term Network Resources for the Customer; and
· Provision of actual or projected hourly load data for the sink for at least one year.
9.3.2. Existing Transmission Customer
Existing Network Customers under the Tariff may elect to create an additional Sink in the AFC Process for a new delivery point under their existing Service Agreements and may elect to create a new AFC Sink definition for current delivery point(s). The new AFC Sink will be incorporated in the AFC Process as soon as reasonably practical after: (i) a SIS has been performed for the new Sink; (ii) the Customer has amended its existing Service Agreement; (iii) all metering, telemetry and other necessary equipment is in-service; and (iv) the Customer has satisfied the requirements listed below necessary to add a new Sink to the AFC Process. Until a Service Agreement for Network Service has been executed or amended, the Customer has the option to serve the new Sink on an interim basis using either short-term firm or non-firm PTP Service under a valid Service Agreement.
The requirements to add a new Sink to the AFC process under this Section 9.3.2 are as follows:
· Confirmation of at least one year of Transmission Service for the new Sink;
· Provision of all information required under Sections 28, 29 and 30 of the Tariff;
· Provision of a list of generators/PPAs which are long-term Network Resources for the Customer; and
· Provision of actual hourly load data for the sink for at least one year.
Customers taking service under grandfathered agreements may also request for a new Sink. Such a request, however, will be evaluated on a case-by-case basis.
9.3.3. New Load-Only Control Area
Any current Customer (including grandfathered Customers), that wishes to form a new load-only Embedded Control Area or External Control Area will be included in the AFC powerflow models and corresponding process as such pending certain certification. New load-only Embedded Control Areas or External Control Areas will be included in the AFC powerflow models and corresponding processes no sooner than the entity commences certified balancing authority area operations and as soon as reasonably practical afterwards. Milestones that must be achieved for a new load-only Embedded Control Areas or External Control Area to be included in AFC powerflow models and corresponding processes include the following: receipt of balancing authority certification from the regional reliability organization, implementation of all required metering and telemetry, implementation of any required changes to the Transmission Provider’s EMS, and execution of a Balancing Authority Area Operating Procedure agreement with the Transmission Provider. When the new Embedded Control Area or External Control Area is added as a Sink in the AFC process, a proxy flowgate (tie-cap flowgate) will be included in the AFC Process. The limit of this tie cap proxy flowgate will be derived from the total projected load in the load-only control area.
9.3.4. Modifications to External Sink Definitions
LSEs interconnected to the Transmission System that are not located in the Transmission Provider’s Control Area may elect to modify AFC Sink definitions and will be subject to the same requirements as Sections 9.3.1. and 9.3.2. The new AFC sink will be incorporated in the AFC Process following execution of the applicable Service Agreement and after notification from the applicable balancing authority or as soon as reasonably possible afterwards. LSE’s subject to grandfathered agreements must be evaluated on a case-by-case basis.
9.3.5. Removal of Active Sink from the AFC Process
All Network Customers and grandfathered Customers must have an active Service Agreement/NOA or grandfathered agreements for load delivery points to retain active sink definitions in the AFC process. Any load delivery point without a grandfathered agreement or a Service Agreement/NOA will be removed as a sink from the AFC Process effective on the date that the applicable agreement(s) is terminated (or as reasonably possible afterwards). Likewise, any Embedded Control Area or External Control Area without all required documentation will be removed as a Sink from the AFC Process. The required documentation includes, but is not limited to, the following: balancing authority certification from the regional reliability organization and a current Balancing Authority Area Operating Procedure agreement with the Transmission Provider (or applicable third party).
10. Subsystem Definition and Participation Factor Calculation Methodology
Attachment 4 to these Business Practices provides a summary of subsystem definitions and the Participation Factor calculation methodology applied to Sources and Sinks in the AFC Process for calculating Response Factors.
11. OATT Attachment C Business Practice Cross References
|
Attachment C Business Practice References |
Current Business Practice Section |
|
|
14.i |
i. Software Applications Used in the AFC Process (Section 1.2) |
VIII.1 |
|
14.ii |
ii. Frequency of Resynchronizations (Section 3.6) |
VIII.2 |
|
14.iii |
iii. Facility Ratings (Section 4.2) |
VIII.2 |
|
14.iv |
iv. Load Data Submission–Operating/Planning Horizons (Section 6.2.1) |
IX.7 |
|
14.v |
v. Generation Dispatch Data Submission–Operating/Planning Horizons (Section 6.3.1) |
VIII.4 |
|
14.vi |
vi. Generation Dispatch Data Submission–Study Horizon (Section 6.3.2) |
VIII.4 |
|
14.vii |
vii. Generating Facility Operating Characteristics (Section 6.5) |
VIII.5 |
|
14.viii |
viii. Transmission Construction Projects Not Currently-In Service (Section 6.6) |
VIII.6 |
|
14.ix |
ix. Zonal Import Limits (Section 7.1.2) |
VIII.7 |
|
14.x |
x. Counterflows (Section 8) |
VIII.8 |
|
14.xi |
xi. Adding New Sources and Sinks (Section 9.1) |
VIII.9 |
|
14.xii |
xii. Calculation of Response Factors (Sections 9.1 and 9.2) |
VIII.10 |
|
14.xiii |
xiii. Data Regarding the AFC Process (Section 13) |
Business Practices Attachment 6 (AFC Related Data) |
|
14 ¶2 |
The TSR Business Practices, including the practices listed above, are subject to the requirements of Section 4 of the Tariff and Section 5 of the Transmission Service Protocol. |
Section 4 |
This Section IX implements Section 13 of Attachment C and Section 8 of Attachment D of the Tariff. It provides a list of the AFC-related data that is either posted on OASIS or supplied upon request, including a description of any applicable confidentiality requirements and procedures. The list identifies: (i) the data used to calculate AFC values; (ii) information and supporting data used to explain the reason(s) TSRs are REFUSED or COUNTEROFFERED; (iii) other AFC-related information provided by the Transmission Provider; and (iv) whether the information referenced in (i)-(iii) is posted on OASIS on a regular basis or is provided upon request. It also provides a list of the SIS and FS data that are either posted on OASIS or supplied upon request, including a description of any applicable procedures and confidentiality requirements. The list identifies the same information regarding SIS and FS data as described for AFC-related data in (i)-(iv) above.
This Section IX applies only to the information and obligations described below and is not intended to describe all of the information made available upon request or posted on OASIS under other provisions of 18 CFR § 37.6 not discussed below.
To the extent a Customer requests data related to AFC calculations, SISs or FSs that have been supplied by a different Customer or LSE or that qualifies as Critical Energy Infrastructure Information (“CEII”), the provisions of Section 9 of Attachment K shall apply. For data supplied at the request of a Customer, any costs associated with reproduction of materials shall be the responsibility of that Customer.
1. Information Regarding Denials of Service
Under 18 C.F.R. § 37.6(e)(2)(i) of the FERC’s regulations, the Transmission Provider provides the reason for the denial of a TSR in whole or part (i.e., REFUSED or COUNTEROFFERED TSRs) as part of the response to the TSR. To comply with this obligation, when a TSR is denied in whole or part for insufficient transfer capability, the Transmission Provider responds to the TSR by changing the final status of the TSR to REFUSED or COUNTEROFFERED. The AFC evaluation for each TSR is posted on OASIS with the other data points for the TSR. If the TSR was evaluated through the SIS and FS Processes, the Study reports contains the information specified in Attachment D, Sections 5 and 6. This information is posted on OASIS and is also available upon request.
2. Information Supporting Reason for Denials of Service
Under 18 C.F.R. § 37.6(e)(2)(ii) of the FERC’s regulations, the Transmission Provider retains for 5 years information to support the reason for denials of service in whole or part (i.e., REFUSED or COUNTEROFFERED TSRs). The Transmission Provider provides this information upon the request of any Customer, not just the Customer whose service request was denied.
If the TSR was evaluated through the AFC Process, the Transmission Provider retains the following data sets for TSRs that are REFUSED or COUNTEROFFERED: (1) the AFC evaluation for the TSR that identifies the flowgate with the lowest AFC value; (2) the AFC Impact Log for the TSR that, among other things, contains a record of the AFC values at the time the TSR was REFUSED or COUNTEROFFERED; and (3) the data inputs used in the power flow models upon which the decision to Refuse or Counteroffer is based and that reflect the operating status of relevant generating and transmission facilities.
If the TSR was evaluated through the SIS or FS Process, the Transmission Provider retains the following data sets for TSRs that are REFUSED or COUNTEROFFERED: (1) the SIS and FS reports; and (2) the data inputs used in the power flow models upon which the decision to Refuse or Counteroffer is based and that reflect the operating status of relevant generating and transmission facilities. A list of SIS and FS reports is posted on OASIS by the ICT. Actual Study reports are available upon request to the extent such reports are not already accessible on OASIS through the hyperlinks included with the list.
3. Data Used to Calculate AFC Values
Under 18 C.F.R. § 37.6(b)(2)(ii) of the FERC’s regulations, Transmission Provider retains all data used to calculate ATC, TTC, Capacity Benefit Margin (“CBM”) and Transmission Reliability Margin (“TRM”) for constrained posted paths for a period of six months after the applicable posting period. This data is provided on request within one week of the posting in the electronic format in which it was created, along with any necessary decoding instructions. The requesting Customer is responsible for the cost of reproducing the material. Although the entire data set is not posted on OASIS as such, portions of this data are posted on OASIS as discussed elsewhere in this Business Practice and may be downloaded for no charge. Attachment 5 hereto includes a list of the specific data used to calculate AFC and TFC and identifies whether the data is periodically posted on OASIS or is only available upon request. Currently, the Transmission Provider does not use TRM or CBM in AFC calculations and, therefore, no such data is available.
4. System Impact and Facilities Studies
Under 18 C.F.R. § 37.6(b)(2)(iii) of the FERC’s regulations, the Transmission Provider retains all SISs and FSs. This data is provided upon request in the electronic format in which it was created, along with any necessary decoding instructions. The requesting Customer is responsible for the cost of reproducing the material. The studies are comprised of the study report, the load flow base case model and all data inputs.
Per Section 8 of Attachment E data that used to perform the SIS and FS, which shall be posted on OASIS in SIS FS Reports or provided upon request includes:
· System Impact Study Reports posted on OASIS contain the information detailed in Section 5 of Attachment D.
· Facility Study Reports posted on OASIS contain the information detailed in Section 6 of Attachment D.
· Load flow models with confirmed transactions included, proposed upgrade files (idev), monitored element and contingency element file(s), and a list of POD and POR for prior transactions still in STUDY status used to evaluate the request shall be made available upon request.
Data provided subject to confidentiality procedures under Section 9 of Attachment K includes:
· Load flow models with prior transactions included.
· Load flow models with the requested transmission service included.
· Transfer Distribution Factor on each limiting element.
The Transmission Provider also supplies to the ICT a monthly peak Base Case Model for each month of the Study Horizon. The ICT posts the models on OASIS in RAWD or other commercially available format. The posted monthly models will be refreshed at least monthly to maintain a rolling 20 month posting.
The Transmission Provider posts its methodology for determination of CBM and TRM for the Transmission Provider’s Transmission System on the INFO.HTM webpage on the Transmission Provider’s OASIS. The methodology can be accessed by selecting the link on that webpage entitled “CBM/TRM on the Entergy Transmission System” or by selecting the below link:
http://www.oasis.oati.com/EES/EESDocs/Entergy_ATC_Information.htm.
A customer wishing to request CBM may do so by sending an email to: EntergyICTAFC@misoenergy.org..
6. List of Other AFC-Related Information Posted on OASIS
This list identifies the AFC-related information that Entergy voluntarily posts on OASIS.
· Subsystem files that define all Sources and Sinks used to calculate Study Horizon AFC values;
· Monitored element file containing the flowgate definitions used to calculate Study Horizon AFC values;
· A file containing Response Factors of up to the top 15 flowgates per path and base flows for each flowgate for the Study Horizon;
· A file containing Response Factors of up to the top 15 flowgates per path and base flows for each flowgate for the Operating and Planning Horizons;
· A revision log documenting all changes made to the AFC flowgate list;
· Files containing the Hourly Effective ATC values, Daily Effective ATC values, Weekly Effective ATC values, and Monthly Effective ATC values;
· Converted versions of selected Operating and Planning Horizon powerflow models (see below);
· All current Study Horizon powerflow models (RAWD format);
· A file containing the list of generators that define the Transmission Provider Control Area Sink for Response Factor calculation (the file also lists the participation factors for these generators); and
· List of AFC Sources by Zone.
In addition to the information identified above, the Transmission Provider posts other information related to the AFC Process pursuant to other provisions of Attachment C or specific FERC regulations. This additional information includes the following:
· A list of all flowgates utilized in the AFC Process (Master List of Flowgates);
· Information regarding service denials (Most Limiting Flowgate) for each REFUSED/COUNTEROFFERED TSR;
· All Flowgate TFC changes greater than 10%; and
· A listing of Study Horizon ATC values limited to a Zero Value for Six Months or Longer.
The Transmission Provider also converts the following EMS-based Base Case Models into a different electronic format (RAWD) that is commercially available:
· A daily peak model for each day of the Day 1- 31 time frame.
· Four (4) hourly models for each day for the Day 1-7 time frame.
The hourly models are randomly selected and represent an hour within a six-hour window of each day. Model 1 represents any hour between hour 0000 and hour 0600, model 2 represents any hour between hour 0700 and 1200, model 3 represents any hour between hour 1300 and 1800, and model 4 represents any hour between 1900 and 2300. Only the six-hour window of the model is disclosed, not the exact hour of the model. These converted models are posted on OASIS by the Transmission Provider. The converted and posted models will be refreshed at least daily to maintain a rolling 31-day posting.
7. Transmission Facility Ratings Methodology
In accordance with Section 2.3.1.2 of Attachment D and Section 4.2 of Attachment C, this Section IX.7 describes the basis for the Transmission Provider’s facility ratings. This section describes the Transmission Provider’s current methodology and makes no assumptions as to the design criteria of legacy equipment and facilities.
This Section IX.7.1 is applicable to transmission facilities as defined in this document. A transmission facility consists of one or more elements carrying load between buses. The elements operate together with the limiting facility rating being derived from the individual equipment ratings. The facility rating will be limited by the most limiting equipment rating. The facility rating will not exceed the most limiting rating of any equipment that comprises the facility. Transformers with both primary and secondary windings energized at 69 kV or above are subject to these criteria. In addition to the power transformers, the Transmission Provider will also rate other transmission facilities, including lines, substations and reactive equipment in accordance with this Business Practice.
Transmission Provider’s facility ratings are established in accordance with NERC Reliability Standard FAC-008 and FAC-009 (or any successor standards) and applicable ANSI/IEEE Standards. Pursuant to Section 2.3.1.2 of Attachment D and Section 4.2 of Attachment C, the Transmission Provider uses the normal rating (as defined by NERC Reliability Standards) for purposes of TFC calculations in the AFC Process and facility ratings used in SISs and FSs.
All circuit ratings are computed with the system operated in its normal state (all lines and buses in-service, all breakers with normal status, and all loads served from their normal source). In all instances, the rating of a transmission circuit does not exceed the rating of the most limiting element in the circuit, including terminal connections and associated equipment.
7.3. Transmission Line Rating Methodology
The Transmission Provider’s ratings of vintage lines, i.e., those constructed before the use of a Transmission Provider System-wide standard as discussed below, are rated based on the prevailing system standard at the time of construction and the original design specifications. Otherwise, the Transmission Provider’s conductor ratings are based on the “IEEE Standard for Calculation of Bare Overhead Conductor Temperature and Ampacity under Steady-State Conditions,” ANSI/IEEE Standard 738-1993. The ANSI/IEEE standard uses, as inputs to the calculation, several company-chosen assumptions about ambient and operating conditions. The Transmission Provider’s inputs into the system-wide standards calculation for ambient and operating assumptions include the following:
TABLE 7-1
|
Input |
Assumption |
|
Line Altitude |
0 feet mean sea level |
|
Line Latitude |
30 degrees North Latitude |
|
Line Orientation |
East-West |
|
Coefficient of Emissivity |
0.5 |
|
Coefficient of Absorption |
0.5 |
|
Atmospheric Quality |
Clear |
|
Time of Day |
12 noon |
|
Ambient Temperature |
40°C (104°F) |
|
Ambient Wind Speed |
2 fps |
|
Wind-conductor Angle |
90 degrees |
|
Bundled conductor |
Transmission Provider assumes the rating of the bundle is the rating of each sub-conductor times the number of sub-conductors in the bundle |
|
Underground Cable |
Transmission Provider has very few underground cables. The manufacturers’ rating for the cables is used. The rating assumptions used will vary by project. |
|
|
|
The selection of a maximum conductor operating temperature affects both the operation and design of transmission lines. Existing transmission lines were designed to meet operating standards in effect at the time the line was built. Over time, these standards have been modified, as reflected in revisions to the National Electric Safety Code (“NESC”). For those existing lines that were designed to meet an earlier standard, the Transmission Provider will apply a rating that is consistent with the NESC design standards being practiced at the time the line was built. Otherwise, the Transmission Provider’s current maximum conductor operating temperatures are as follows:
TABLE 7-2
|
ACSR |
100°C |
|
ACAR |
80°C |
|
AAC |
80°C |
|
Cu |
80°C |
|
ACSS |
175°C |
|
|
|
Although the Transmission Provider plans to utilize the above criteria when rating circuits, there may be instances when the flow on a transmission circuit is limited by factors other than the thermal capacity of its elements. The limit may be caused by other factors such as stability, phase angle difference, relay settings, or voltage limitations. When limitations by other such factors exist, the Transmission Provider will establish the circuit rating in accordance with established industry practices. Additionally, there may be instances when de-rating of a transmission line element is required due to damaged equipment. The limit may be caused by such factors as broken strands, damaged connectors, failed cooling fans, or other damage reducing the thermal capability. When such de-rating is indicated, the Transmission Provider will establish the new circuit rating in accordance with established industry practices.
Coordination of facility ratings data with neighboring systems is done through the SERC Long Term Study Group (“LTSG”) and SERC Near Term Study Group (“NTSG”) where ratings are coordinated, maintained and updated by the Transmission Provider representative and the representatives of the neighboring systems.
Additionally, the Transmission Provider may have a contractual interest in a joint-ownership transmission line whereby the capacity of the line is allocated among the owners. The allocated capacity may be based upon the thermal capacity of the line or other considerations. The Transmission Provider will coordinate the rating of the tie line with the co-owner such that the lowest rating determined in coordination with the co-owners of the transmission line is used.
7.5. Transmission Line Equipment Rating Methodology
Rating methodologies for line switches, line jumpers, and hardware are in accordance with applicable industry standards for this equipment.
TABLE 7-3
|
Equipment |
Applicable Standard |
|
Line Switches |
IEEE C37.30 |
|
Line Jumpers |
IEEE 738 |
|
Hardware |
NEMA standard publications CC (all), ANSI C119.4-1976 and U.L.486 |
|
|
|
7.6. Transmission Substation Rating Methodology
Rating methodologies for circuit breakers, circuit switchers, bus conductors, current transformers, disconnect switches, and line traps are in accordance with applicable IEEE standards for this equipment.
TABLE 7-4
|
Equipment |
Applicable Standard |
|
Circuit Breakers |
IEEE 37.04, IEEE 37.06 |
|
Circuit Switchers |
IEEE C37 |
|
Bus Conductors |
IEEE 738 |
|
Current Transformers |
IEEE 57.13 |
|
Disconnect Switches |
IEEE C37.30 |
|
Line Traps |
IEEE C93.3 |
|
|
|
7.7. Power Transformer Rating Methodology
The normal circuit rating for a power transformer under the Transmission Provider’s methodology is its highest nameplate rating. The nameplate rating includes the effects of forced cooling equipment, if it is available. For multi-rated transformers (ONAN/ONAF, ONAN/ONAN/ONAF, ONAN/OFAF/OFAF, ONAN/ONAF/OFAF, etc.) with all or part of forced cooling inoperative, the nameplate rating used is based upon the maximum cooling available. Normal thermal life expectancy will occur with a transformer operated at its continuous nameplate rating.
The rating methodology for power transformers is in accordance with IEEE C57.12. Bushing loading/rating is in accordance with IEEE C57.19.00. The general methodology used to determine loading capability of transformers is outlined in IEEE C57.91.
7.8. Transmission Reactive Equipment Rating Methodology
Rating methodologies for reactors, shunt capacitors, superconducting magnetic energy storage (“SMES”), series capacitors, static var compensator (SVC”) and other reactive equipment are in accordance with applicable IEEE and industry standards.
TABLE 7-5
|
Equipment |
Applicable Standard |
|
Reactors |
IEEE C57.16, IEEE C57.21 |
|
Shunt Capacitors |
IEEE Std. 18 |
|
SMES |
Per all applicable standards |
|
Series Capacitors |
IEEE 824 |
|
SVC |
IEEE 1031, IEEE 1303 |
ATTACHMENT
1
Examples of Loss Compensation
Losses occur when the Transmission Provider delivers electricity across its transmission facilities for a Customer. This Attachment 1 provides examples of describes how the Transmission Provider will address losses for Network Service or PTP Transmission Service provided under the Tariff. Responsibility for losses is governed by Sections 15.7 and 28.5 of the Tariff, and Section 2 of Attachment H.
The tables below are provided for illustrative purposes as examples of valid and invalid NERC e-tags.
Example 1:
VALID TAG
|
Hr Index |
POR MW |
POD MW |
Accumulated POD MW |
1.03 x Accumulated POD MW (Rounded) |
Losses Specified by Customer |
Accumulated Losses Specified by Customer |
|
1 |
52 |
50 |
50 |
52 |
2 |
2 |
|
2 |
51 |
50 |
100 |
103 |
1 |
3 |
|
3 |
52 |
50 |
150 |
155 |
2 |
5 |
|
4 |
51 |
50 |
200 |
206 |
1 |
6 |
|
5 |
52 |
50 |
250 |
258 |
2 |
8 |
|
6 |
51 |
50 |
300 |
309 |
1 |
9 |
|
7 |
52 |
50 |
350 |
361 |
2 |
11 |
|
8 |
51 |
50 |
400 |
412 |
1 |
12 |
|
|
|
|
|
|
|
|
Example 2:
INVALID TAG: insufficient losses provided on first segment (must supply losses
on first segment).
|
Hr Index |
POR MW |
POD MW |
Accumulated POD MW |
1.03 x Accumulated POD MW (Rounded) |
Losses Specified by Customer |
Accumulated Losses Specified by Customer |
|
1 |
9 |
9 |
9 |
9 |
0 |
0 |
|
2 |
9 |
8 |
17 |
18 |
1 |
1 |
Example 3:
INVALID TAG: insufficient losses provided on second segment.
|
Hr Index |
POR MW |
POD MW |
Accumulated POD MW |
1.03 x Accumulated POD MW (Rounded) |
Losses Specified by Customer |
Accumulated Losses Specified by Customer |
|
11 |
103 |
100 |
100 |
103 |
3 |
3 |
|
12 |
100 |
100 |
200 |
206 |
0 |
3 |
|
13 |
103 |
100 |
300 |
309 |
3 |
6 |
|
14 |
103 |
100 |
400 |
412 |
3 |
9 |
|
|
|
|
|
|
|
|
Example 4:
INVALID TAG : insufficient losses provided on third segment.
|
Hr Index |
POR MW |
POD MW |
Accumulated POD MW |
1.03 x Accumulated POD MW (Rounded) |
Losses Specified by Customer |
Accumulated Losses Specified by Customer |
|
14 |
21 |
20 |
20 |
21 |
1 |
1 |
|
15 |
10 |
10 |
30 |
31 |
0 |
1 |
|
16 |
20 |
20 |
50 |
52 |
0 |
1 |
|
|
|
|
|
|
|
|
Example 5:
VALID TAG
|
Hr Index |
POR MW |
POD MW |
Accumulated POD MW |
1.03 x Accumulated POD MW (Rounded) |
Losses Specified by Customer |
Accumulated Losses Specified by Customer |
|
1 |
39 |
38 |
38 |
39 |
0 |
0 |
|
2 |
40 |
38 |
76 |
78 |
2 |
2 |
|
3 |
39 |
38 |
114 |
117 |
1 |
3 |
|
|
|
|
|
|
|
|
ATTACHMENT
2
List of AFC Software Applications
|
Application |
Purpose |
|
AFC SFD |
Application used to retrieve and compile planned and unplanned outages for AFC process. This software is used in the Operating Horizon and Planning Horizon only. |
|
AORS |
This application is used within the TRANSMISSION Outage Planning Process. This software contains all planned “Branch/Section” and “Equipment Outages” for the Transmission System. |
|
COS |
This application is used to report all outages on the Transmission System. |
|
RFLOADER |
This application collects the generation dispatch, load forecast and outage data from various sources and, after validation and processing, creates the inputs for AFC process in the Operating Horizon and Planning Horizon. |
|
RFARCHIVE |
This application is used to archive the inputs and outputs of RFCALC for the Operating Horizon and Planning Horizon of the AFC process. |
|
EMS OUTAGE SCHEDULER |
This application is used to store Outage data used by RFCALC in Operating Horizon and Planning Horizon calculations for the AFC process. |
|
RFCALC |
This application calculates flowgate Base Flows, Response Factors and the Fifteen Most Limiting Flowgates per transfer path for the AFC process within the Operating Horizon and Planning Horizon. |
|
EMS NETWORK MODEL |
The Base Case Models derived from the Transmission Provider’s EMS State Estimator and is used to calculate AFC values in the Operating and Planning Horizons. |
|
LCU |
The Secure Web Portal utilized by Network Customers to upload generation dispatch and load data to be used in AFC calculations for the Operating Horizon and Planning Horizon. |
|
SWMS |
Substation Work Management System. The data contained in this system is used while creating outage list for the AFC process in the Operating Horizon and Planning Horizon. |
|
SDX |
NERC System Data Exchange - NERC approved method for submitting operational planning horizon reliability data for use throughout the Eastern Interconnection, including load forecast information, transmission facility status, and generating facility status. |
|
ROBOTAG |
The Transmission Provider’s application for managing the NERC Tagging Processes. This application provides the scheduling information against firm Reservations. |
|
WEBTRANS/ |
The Transmission Provider’s software application used to process TSRs and calculate AFC values, including any successor software. |
|
SCENARIO ANALYZER |
The application marketers use to view AFC availability on the Transmission System prior to submitting a TSR and the Transmission Provider uses to assist in evaluations. |
|
WEBOASIS |
The application marketers use to receive information on the Transmission System and submit TSRs. |
|
PTI PSS/E |
The Power Flow Modeling application used to create power flow models for the AFC Study Horizon. |
|
UC AUTO |
The application that prepares the zonal import limit file used by the AFC process in Operating Horizon and Planning Horizon. |
|
PAAC OFFLINE CALCULATOR |
Uses PTI PSS/E solved power flow models to produce base flows and response factors for the AFC Study Horizon |
ATTACHMENT
3
Generating Facility Operating Characteristics Data Submission Template
Note: Individual
templates should be completed for each unit at a generating facility
|
|
General Information |
|
|
1.1 |
Company Name |
|
|
1.2 |
Plant/Station Name |
|
|
1.3 |
Data Submitted by, Name |
|
|
1.4 |
Phone Number/Fax Number |
|
|
1.5 |
Electronic Mail Address |
|
|
1.6 |
Date Data was submitted |
|
|
|
|
|
|
|
Unit Information |
|
|
2.1 |
Unit ID/Machine # |
|
|
2.2 |
Generator Base MVA |
|
|
2.3 |
Generator Real Power Capability |
|
|
2.4 |
Rated Voltage |
|
|
2.5 |
Rated Power Factor |
|
|
2.6 |
Generator Reactive Power Capability (Qmax and Qmin) |
|
|
2.7 |
Generator Capability Curve (if available) |
|
|
|
|
|
|
|
Outage Information |
|
|
3.1 |
Unit Impacted by Planned Outage |
|
|
3.2 |
Unit Impacted by Unplanned Outage |
|
|
3.3 |
Total Plant Capability During Outage |
|
|
3.4 |
Planned Outage Date Range |
|
|
3.5 |
Unplanned Outage Date Range |
|
|
|
|
|
|
|
De-rate Information |
|
|
4.1 |
Unit Impacted by De-rate |
|
|
4.2 |
De-rate Total Amount |
|
|
4.3 |
Total Plant Capability with De-rate |
|
|
4.4 |
Date Range for De-rate |
|
ATTACHMENT
4
Subsystem Definitions And Participation Factor Calculation Methodology Applied
To Sources And Sinks In The AFC Process For Calculating Response Factors
Study Horizon Source Subsystem Definition and Participation Factor Methodology
|
Source Type |
Subsystem
Definition |
Participation Factor Calculation Methodology (AFC Study Horizon) |
|
Generators directly interconnected to the Transmission System. |
|
|
|
Note: Also includes border generating facilities as defined by Section 9.2 of Attachment C to the Tariff. |
All units at the generation facility. |
The output of all units in the subsystem definition are increased on a pro-rata basis. |
|
Note: Generating facilities with dual or multiple owners may be designated with multiple source definitions. |
|
|
|
Embedded and External Control Areas. |
|
|
|
Note: Excludes embedded load-only balancing authority areas. |
All generators located in the Control Area. |
The output of all units in the subsystem definition are increased on a pro-rata basis. |
|
SMEPA Excess. |
|
|
|
Note: As defined by grandfathered arrangement with SMEPA. |
Batesville Unit 3 and Silver Creek. |
Mbase of each machine in subsystem definition. |
AFC Study Horizon Sink Subsystem Definition and Participation Factor Methodology
|
Sink Type |
Subsystem
Definition |
Participation Factor Calculation Methodology (AFC Study Horizon) |
|
External Control Areas. |
|
|
|
Note: Excluding LAGN. |
All generators located in the Control Area. |
The output of all units in the subsystem definition are decreased on a pro-rata basis. |
|
Embedded Control Areas (excluding ‘generator only’ control areas). |
Long-term firm resources. |
|
|
|
Note: In the absence of long-term resources, ‘ENTEMO’ subsystem definition will be utilized. Refer to the participation factor calculation methodology for Entergy SPO. |
The output of all units in the subsystem definition are decreased on a pro-rata basis. |
|
Entergy SPO and LAGN. |
All online, owned Network Resources except for nuclear and coal-fired generators. |
Mbase of each machine in subsystem definition. |
|
External load delivery points not located in the Transmission Provider’s Control Area. |
Long-term firm resources. |
When individual generators are defined, Mbase of each machine in subsystem definition is utilized. When all generation within a specific BA is defined, all units in the BA are decreased on a pro-rata basis. |
|
Load delivery points located in the Transmission Provider Control Area. |
Long-term firm resources. |
The output of all units in the subsystem definition are decreased on a pro-rata basis. |
|
Richard Losses. |
|
|
|
Note: As defined by grandfathered agreement with Cleco. |
All generators located in the Cleco Control Area. |
The output of all units in the subsystem definition are decreased on a pro-rata basis. |
ATTACHMENT
5
AFC Operating and Planning Horizon Subsystem Definition and Participation
Factor Methodology
Note: For all Source/Sink definitions defined in the below, only units that are considered online in AFC Process are used to calculate Response Factors.
|
Source/Sink Type |
Subsystem Definition (AFC Operating and Planning Horizon) |
Participation Factor Calculation Methodology (AFC Operating and Planning Horizon) |
|
The Source/Sink is defined as collection of discrete generators. |
All units defined within the source/sink. |
If the generator is in Unit Commitment file supplied by the Customer, then the fix user defined participation factor as calculated by Transmission Provider or Customer is used. If the generator is not defined in UC file then participation factor supplied by State Estimator are used. |
|
External Control Area Source/Sink. |
All AGC generators located in the Balancing Authority Area. |
Participation factors are calculated using MW reserve margin of units. |
|
Embedded Control Area (load only) Sink (Buba, CWAY, WMU). |
.Designated long-term resources Note: In absence of long-term firm resources all oil and gas units in Entergy control area will be utilized. |
If the generator is in Unit Commitment file supplied by the Customer, then the fix user defined participation factor as calculated by Transmission Provider or Customer is used. If the generator is not defined in UC file, then participation factor supplied by State Estimator is used. |
|
Entity Responsible for Serving the Transmission Provider’s Native Load Customers Sink. |
Designated oil and gas units in the control area. |
Three sets of participation factors are calculated to account for transactions originating from the sources located in Amite South, WOTAB or outside these load pockets. Participation to be used for a response factor calculation is determined based on the location of the source. |
This attachment provides a list of: (1) the data used to calculate AFC and TTC; (2) information and supporting data used to explain the reason(s) TSRs are REFUSED or COUNTEROFFERED; (3) other AFC-related information provided by the Transmission Provider; and (4) whether the information referenced in (1)-(3) is posted on OASIS on a regular basis or is provided upon request.
|
Description of Data |
Used in |
On Request or Posted |
|
AFC Powerflow models. |
Yes |
The following information is posted on the OASIS: Four hourly models for each day for the Day 1-7 time frame; A daily peak model for each day of the Day 1-31 time frame; and A monthly peak model for each month of the Month 2-18 time frame. |
|
Generation Dispatch Methodology. |
Yes |
Included in the Attachment C posted on OASIS and Business Practices. |
|
Contingency, subsystem, monitoring, change files and accompanying auxiliary files. |
Yes/No |
Not used in Operating and Planning Horizon; Posted on OASIS for Study Horizon. |
|
Transient and dynamic stability simulation data and reports on flowgates which are not thermally limited. |
Yes |
Stability study information available on OASIS. |
|
List of transactions used to update the base case for Transmission Service request study. |
Yes |
Upon request. |
|
Special protection systems and operating guides, and specific description as to how they are modeled. |
No |
Not utilized in the AFC Process. |
|
Model configuration settings. |
Yes |
Contained in load flow cases. |
|
Dates and capacities of new and retiring generation. |
Yes |
Capabilities included in load flow cases. Dates are not included, can be provided upon request. |
|
New and retired generation included in the model for future years. |
Yes |
New generators contained in load flow cases as discussed in 9.2.1 of this business practice. Retired generators are removed from load flow cases. |
|
Production cost models (including assumptions, settings, study results, input data, etc.), subject to reasonable and applicable generator confidentiality limitations. |
No |
Information not utilized in the AFC Process. |
|
Searchable transmission maps, including PowerWorld or PSSE diagrams. |
No |
May be provide upon request, if available, and subject to certain confidentiality requirements. |
|
OASIS names to Common Names table and PTI bus numbers. |
Yes |
Provided upon request. |
|
Response Factors for up to the top 15 Flowgates per path and base flows for each Flowgate for the Operating, Planning and Study Horizon. |
Yes |
Posted after every resynchronization. |
|
Hourly Effective ATC values, Daily Effective ATC values, Weekly Effective ATC values, and Monthly Effective ATC values. |
No |
Posted and updated approximately every 15 minutes. |
|
A list of generators that define the Transmission Provider Control Area sink for response factor calculation. The file also lists the participation factors for these generators. |
Yes |
Posted on OASIS. |
|
On a one time basis (March 4, 2009), the most limiting component of a limiting element (e.g., specific transmission line and substation equipment). |
No |
Posted on OASIS. |
|
AFC Flowgate definitions and limits (including limit description). |
Yes |
AFC Master List of Flowgates posted on OASIS. |
|
A revision log documenting all changes made to the AFC Master List of Flowgates (“Master List”). |
Yes |
Revision Log of AFC Master List of Flowgates posted on OASIS. |
|
Location of AFC Sources. |
Yes |
Posted on OASIS. |
|
Subsystem and Participation Factor Methodology. |
Yes |
Provided in Business Practices, Attachment 4. |
|
Data inputs used in load flow Base Cases. |
Yes |
On Request. |
ATTACHMENT
7
Form to Undesignate or Cluster (Alternate Network Resource Designation)
Network Resources
ICT Tariff Administration (Undesignations less than one year): Fax form to ICT Tariff Admin at 317-249-7992.. Afterwards, call the ICT Tariff Administration Desk at 317-249-5037 so your request can be processed.
ICT Long Term Group (Undesignations for one year or more): Attach form to an email and send to EntergyTariffAdministration@misoenergy.org.
Customer Information:
|
Name: |
Phone: |
|
Company: |
Fax: |
|
Comments: |
UNDESIGNATION
|
Reference Number |
Sink |
Perm/Temp* |
Date Begin |
Time Begin |
Date End |
Time End |
Capacity Reduction |
Capacity Remaining |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Indication of Perm/Temp Required For Use When Submitting Long-Term Undesignation Only
Request Clustering (Long-Term Only): Yes_____ No____
CLUSTER DESIGNATION
|
Reference Number |
Sink |
Date Begin |
Time Begin |
Date End |
Time End |
Total Capacity |
Capacity Designated |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|