Protocol Revision Requests (PRRs)
# Title Description Date Posted Urgent Protocol Sections Current Status Effective Date(s)
PRR211Balancing Energy Bid Curves for RPRSSoftware unable to support unit specific BE bid curves by June 1, 2001. The software can support 1 UBES bid curve per zone per QSE & 1 DBES bid per zone per QSE. There is no manual work-around.03/12/2001No4.4.16(3)Approved
PRR212Surety BondRequired by PUCT. Allows a QSE to post a surety bond as an alternative to meeting ERCOT creditworthiness requirements.03/12/2001No16.
PRR213Dynamic Schedules GenerationRequests that a QF have a choice of QSE to maintain dynamic flexibility.03/28/2001Yes4.9.2Withdrawn
PRR214EPS Meter CommunicationAllows a TDSP to provide other ERCOT approved communication technology for ERCOT to use in acquiring data from EPS Meters.03/28/2001Yes10.12.1(2)Approved
PRR215Revision of Availability for Responsibility TransfersPIP151, Responsibility Transfers will be available on January 1, 2002.03/29/2001Yes4.9.4Approved
PRR216Bid ClearingClarifies that unselected bids are cleared when a market closes & specifies that bids must be resubmitted if reconsideration is desired.04/06/2001Yes4.4.11Approved
PRR217Distribution Loss "K" FactorsRevises the K-factor range from 0.0-0.1 to 0.0-1.2.04/10/2001Yes13.3.1.1Approved
PRR218Responsibility Assignment for RPC & AVRChange the responsibility for reactive power capability & automatic voltage regulator (AVR) testing from the QSE to the Generation Entity.04/16/2001No6.10.3.5Approved
PRR219Frequency Level DeviationChange the level of frequency deviation at which ERCOT measures & records various system operating data from 0.375 to 0.175 Hz.04/16/2001No6.10.5.4Approved
PRR220Section 17 Language ClarificationChange a description of the Protocols as including the Operating Guides.04/16/2001No17.6Approved
PRR221Responsive Reserve Resources (Hydro)Required by PUCT. Removes the limits the limits on the provision of Responsive Reserve Service by hydroelectric resources.04/16/2001Yes6.1.4Approved
PRR222Amend Market Solution DefinitionRequired by PUCT. Amends the "Market Solution" definition.04/16/2001Yes2.1Approved
PRR223Agreements & Protocols DeviationsRequired by PUCT. Establishes the requirement that "known" deviations between Agreements & the Protocols are to be expressly stated & terms are effective only upon ERCOT BOD approval.04/16/2001Yes1.1Approved
PRR224Changes to Load Profiles Based on DisputesRequired by PUCT. Requires TDSPs to change the assignment of a Load Profile or Weather Zone based on the outcome of a dispute.04/16/2001Yes18.4.4.1Approved
PRR225TOU MeteringRequired by PUCT. Language addition: "within ever investor-owned TDSP territory, additional TOU schedules may be implemented if approved by the PUCT."04/16/2001Yes18.7.1.4(2)Approved
PRR226Interim Manual Switching DeadlinesRequired by the PUCT. Clarifies that deadlines for the interim manual switching process are the same as those for the automated process.04/16/2001Yes11.1.10Approved
PRR227ERCOT Sole DiscretionRequired by PUCT. Clarifies the extent of ERCOT's sole discretion.04/17/2001Yes1.2Approved
PRR228Non-ERCOT LSE FeeClarifies the application of the Non-ERCOT LSE fee by replacing the CR reference with LSE.04/16/2001Yes9.7.3Approved
PRR229Pre-Assigned TCRsRequired by PUCT. Establishes that pre-assigned TCRs are subject to change or elimination upon ERCOT BOD approval or PUCT order.04/16/2001Yes7.5.4.4Approved
PRR230REC Administrative FeeRequired by PUCT. Deletes paragraph 9.7.2 & designates as "reserved."04/16/2001Yes9.7.2Approved
PRR231Sect 9.5.5 Language ClarificationRequired by PUCT. Replaces "proven" with "alleged."04/16/2001Yes9.5.5Approved
PRR232PUCT NotificationRequired by PUCT. Establishes that ERCOT is to notify the PUCT if a TDSP fails to meet its customer switch responsibilities.04/16/2001Yes15Approved
PRR233Balancing Energy Offer CapRequired by PUCT. Establishes an offer cap on Balancing Energy of $1,000.04/17/2001Yes6.5.2Approved
PRR234RMRRequired by PUCT. This revision gives the RMR unit owner the option of receiving 10% of positive margins for energy generated in excess of the amount that the unit is obligated to produce under its RMR contract. The RMR owner has the choice of selecting 1 of 2 options no more frequently than on a yearly basis, prior to the time in which the selected option will be in effect.04/17/2001Yes6.8.3.7, 22FApproved
PRR235Adj. Of Unselected AS bidsRequired by PUCT. Defines an activity rule that permits only downward adjustments of unselected Ancillary Service bids & allows unselected bids by a QSE to be withdrawn only in descending order of bid price.04/17/2001Yes4.5.9, 6.6.2Approved
PRR236Loss Compensation Outside the IDR Meter PermittedProvides a mechanism to perform distribution loss compensation outside the IDR meter.04/16/2001Yes13.1.1Approved
PRR237Federal ResourcesRequired by PUCT. Gives ERCOT the authority to grant waivers to federally owned & operated hydroelectric facilities from registration requirements & execution of Resource Agreements.04/20/2001Yes4.4.5,
PRR238Meter Read DataRequired by PUCT. Provides a deadline for ERCOT to present meter-read data to CRs for the interim period before the system vendor can ensure meeting deadlines.04/17/2001Yes15.1.1.10Approved
PRR239Reg. Of Texas Non-ERCOT TDSPsRequires Non-ERCOT TDSPs operating in the state of Texas where Customer Choice is in effect to register with ERCOT.04/20/2001Yes16.4Approved
PRR240Trans. Billing Determinant CalcEntirely removes Section 9.8.2 - Monthly Determinant Data From ERCOT & clarification edits to 9.8.1 - item#3.04/24/2001Yes9.8Approved
PRR241UFE Analysis1) Revises the beginning date for UFE analysis in Section 11.5.1 to January 2002. 2) Modifies the language in to accommodate a December 1, 2001 implementation timeline. 3) Adds language in to require TDSPs to leave "old control area" boundary meters in place until UFE analysis zones are defined. Definition of zones to take place after June 1, 2001 but supporting December 1, 2001 deadline.04/24/2001Yes11.5Approved
PRR242Waiver for Existing ContractsTNMP requests that Protocol Section be amended for existing netting agreements which terminate between June 1, 2001 & December 31, 2001 by allowing an exception for generation netting which TNMP states does not otherwise affect ERCOT or competition.04/27/2001Yes10.3.2.3Withdrawn
PRR243Acceptance of Non-ERCOT TransactionsAn impact analysis was done by Accenture and it was determined that it would be costly and time consuming (in terms of system performance) to validate and reject pass through usage transactions for Non-ERCOT TDSP 867_03 transactions. Therefore, the systems will not reject transactions from Non-ERCOT TDSPs who choose to send the 867_03 to ERCOT.05/03/2001Yes15.1Approved
PRR244Provisional Qualification for AS ProvidersAllows ERCOT to grant a ninety (90) day Provisional Qualification period during which additional testing may be rescheduled for QSEs that have encountered non-critical technical issues during Ancillary Services testing.05/11/2001Yes6.10.3Approved
PRR245Ratcheting Down of OOME Up PaymentsApply a ratcheting down mechanism for OOME Up energy payment.05/17/2001Yes6.8.2.2Approved
PRR246Protocol Effective DateChange the effective date so that it reflects the actual start of the market.05/22/2001Yes1.7Approved
PRR247Ratcheting of OOME PaymentsApply a ratcheting down mechanism for OOME Up energy payment and a ratcheting up mechanism for OOME Down energy payments.05/25/2001No6.8.2.2Approved
PRR248TX Non-ERCOT LSE RegistrationCreates new Protocol Section 16.11 to require Non-ERCOT Load Serving Entities operating in the state of Texas to register with ERCOT.05/31/2001Yes16.11 (new)Approved
PRR249QSE Creditworthiness MonitoringUpdate creditworthiness monitoring requirements.06/13/2001Yes16.2.8Approved
PRR250NOIE Consumption by ESI-IDAllows the QSE for a NOIE to see the consumption data for an ESI-ID for that NOIE.06/20/2001No15.2 & 15.3Withdrawn
PRR251Update Texas SETsUpdate the Protocols to match SET transactions. These are Non-ERCOT transaction updates.06/29/2001No19.3.1Approved
PRR252Protocol Effective DateRevise the Protocols to reflect the actual single control area operation start date of the market.07/03/2001Yes1.7Approved
PRR253EPS Meter Clock Time MaintenanceThe proposed language allows TDSP and EPS Meters to stay on another time reference with the meter data adjusted to Central Prevailing Time.07/06/2001No10.9.1(7), 10.9.2(5)Approved
PRR254New Protocol Chapter - Texas Test Plan Team Market TestingTo define the Market Testing Process.07/06/2001No23 [new]Approved
PRR255VEE Standard for TDSP Metered EntitiesThe Metering Subcommittee is requesting a language modification to section 10.11.3. The language modification will incorporate a specific reference to the Uniform Business Practices standard for Validation, Estimation, and Editing.07/09/2001No10.11.3Approved
PRR256REC Protocols Revisions from PUCT Order in Docket N. 23802The PUCT ordered these changes in its final order issued in Docket No. 23802, Proceeding to Consider Section 14 of the ERCOT Protocols (Severed From Docket No. 23220).07/10/2001No14.9, 14.10.2Approved
PRR257Provision of passwords to the Resource Entity for EPS metered FacilitiesProvision of passwords to the Resource Entity for EPS metered Facilities07/10/2001No10.1Approved
PRR258Notification Automation if Permit RequiredTo facilitate Move-ins where a permit is required.07/13/2001Yes15.1.1.2,,
PRR259Process Automation for Un-executable Move-insTo facilitate completion of Move-ins that are unexecutable.07/13/2001Yes15.1.4.5Approved
PRR260Auto Purge Process If Permits Not ReceivedTo facilitate purging of Move-ins that require a permit, but the permit is not received by the TDSP.07/13/2001Yes15.1.1.7,
PRR261CR NotificationAdd a notifying element for the CRs to identify when date changes have created a gap in time.07/13/2001Yes15Approved
PRR262CSA CR Continuity of ServiceTo provide the CSA CR with continuity of service.07/13/2001Yes15.1.5.1Approved
PRR263Update Move-in Reject ReasonsAdd new rejection for following reason: "There is already a move in request in progress, not first in for the same requested date."07/13/2001Yes15.1.4.9Approved
PRR264Move-in W/O Meter InstalledAllows the TDSP to return as much premise info as possible to the CR in the 2 day window.07/19/2001Yes15.1.4.5,
PRR265Priority Move-inTo facilitate passing critical info to the TDSP so the Move-in can be expedited and scheduled as requested.07/19/2001Yes15.1.4.1,,,
PRR266Concurrent ProcessingUpdate Concurrent Processing procedures.07/20/2001Yes15.1.1.9, 15.1.3,
PRR267Black Start Basic Startup Test IntervalClarifies requirements for annual testing of black start units.07/26/2001No6.10.3.6Approved
PRR268Day Ahead Scheduling Process Time Line Change RequestExtends the time line for Day Ahead Scheduling Process to 1830 from 1630. The extension to start at 1400.07/26/2001Yes4.1.1, 4.4.14 to 4.4.17Approved
PRR269Small Renewable Production Facilities Metering RequirementRelax the requirement for IDR meters and the provision of generation meter data to ERCOT for renewable energy production facilities that are less than 50 kW and are interconnected to operate in parallel with a NOIE TDSP distribution system.07/30/2001No10.2.2, 10.9Approved
PRR270Unit Specific Dec PremiumsRevise the Protocols to reflect that the system selects and deploys Resources for unit-specific deployments based on the price that results from subtracting the premium from the MCPE.08/02/2001Yes6.7.1.2 (5)Approved
PRR271Local CongestionRevise the Protocols to reflect that ERCOT is using OOME Up and OOME Down for settlement of energy deployed to relieve Local Congestion.08/02/2001Yes6.7.1.2 (10)Approved
PRR272Add Distribution Zone to Data QueryThe addition of the Distribution Zone (DZ) field is needed to identify which power pool an ESI ID is located.08/17/2001No15.2Approved
PRR273Post MCPC at Award TimeRemove no earlier than 1430 from
PRR274Remove Expiration Time for BES & Unit Premium BidsRemove expiration time of bids for hourly BES bid curves and unit specific bid premiums entered in the hourly resource plan.08/20/2001Yes4.5.3(5),
PRR275AS Mismatch Language RevisionRevise to reflect that AS mismatches will be adjusted to match the Resource. Software acquires AS based on AS scheduled by Resource and is unable to adjust to match the Obligation because of multiple inter-QSE trades.08/20/2001Yes4.7.2(3)(b)Approved
PRR276Adjust BENA ComputationAdjust the computation of the Balancing Energy Neutrality Adjustment to more accurately assign the payments and charges to Load Serving Entities.08/20/2001Yes9.6.1Withdrawn
PRR277Clarify SCF Fee DeterminationSec. of the ERCOT Protocols states that Any shortages, not covered by ERCOTs line of credit, will be uplifted to all QSEs representing Load on a Load Ratio Share. This PRR clarifies that such uplift should occur by adjusting the Forecasted Fee in the System Congestion Fund calculation, rather than uplifting congestion costs in excess of congestion fund revenues through the Balancing Energy Neutrality Adjustment, as is current practice by ERCOT.08/20/2001Yes7.3.3.1Withdrawn
PRR278RMR, Synchronous Condenser, Black Start RevisionsResolve conflicts between Protocol language and contract language. Revise Protocol formulas to be consistent with contract language and add clarifying language to the Protocols.08/28/2001Yes6.8.3 & 6.8.5Approved
PRR279Responsibility Transfers for Capacity Auction ProductsThe PUCT has required IOUs to sell at auction 15% of their capacity in 25 mw blocks. One of the products from these blocks is balancing energy through the use of a Responsibility Transfer. Over 200 possible RspT will place a burden on ERCOT as well as the seller. This is a simpler method for the buyer to bid in the balancing energy market but have the seller receive a message rather than a continuous signal.08/28/2001Yes4.9.5Approved
PRR280Zonal Congestion CostsClarification that costs for resolving Zonal Congestion should be counted toward the $20 million threshold for the transition for the direct assignment of CSC Congestion resolution costs.08/31/2001Yes7.3Approved
PRR281Allowance for Aggregated Site-Specific Resource Dispatch Instructions (v2)This is version 2 of the original PRR submitted on 9/10/2001. This revision is intended to allow for site-specific dispatch of resources & would not be mandatory for all resource owners. V2 redefines sections of the Protocols where change is necessary & requests a Normal timeline for implementation. This PRR was originally entitled, Change ERCOT Deployment Instructions to Settlement Meter Specific. Due to the emergence of split metering, netting behind meters, & other factors the reference to instructions to the settlement meter was dropped in favor of the more accurate description of aggregated site-specific dispatch of resources.05/24/2002NovariousWithdrawn
PRR282Define OOME as an Instructed Deviation09/11/2001YesWithdrawn
PRR283ERCOT Read Meter DataChanges PIP 204 to provide Market Participants Data for ERCOT Populated ESI IDS via a data extract instead of 867_03 EDI transactions and adds the requirement to provide Market Participants EPS Meter Recorder (RIDs) level data via a data extract.09/06/2001Yes11.1.10Approved
PRR284Adjusted Computation of BENAAdjust the computation of the Balancing Energy Neutrality Adjustment to more accurately assign the payments and charges to Load Serving Entities. This PRR, combined with PRR277 (to be modified consistent with PRR280 such that all zonal congestion is collected via the SCF) will be effective during the CSC uplift period.09/12/2001Yes9.6.1Withdrawn
PRR285OOMC PremiumClarify the language regarding payment when the OOMC payment is not sufficient to cover the cost of providing RPRS service and provide a reasonable premium. The proposed language will make the form of the OOMC language consistent with the form of the OOME payment.09/12/2001Yes6.8.2.1(6)Approved
PRR286Smoothing AlgorithmThis revision will change the calculation of the Schedule Control Error equation.09/12/2001No6.10.4.2Withdrawn
PRR287Responsibility Transfers (Dynamic Scheduling)These revisions clarify that dynamic scheduling of resources between QSEs is to be allowed, as well as clarify details of responsibility transfers to conform with ERCOT systems capability.01/25/2002No4.9Approved
PRR288TDSP Metered EntitiesThis PRR is similar to PRR269. It modifies 269PRR as follows, Relax the requirement for IDR meters and the provision of generation meter data to ERCOT for renewable energy production facilities that are less than 50 kW & not wanting compensation for net output. These customers are interconnected to operate in parallel with a NOIE or OIE TDSP distribution system. Resource facilities wanting compensation will need to follow standard protocol requirements of generation entities (IDR metering, an assigned Resource Identifier (RID), need to complete a Resource Application, etc.).09/24/2001No10.2.2; 10.9Approved
PRR289Block Load TransfersSimplify the way ERCOT protocols accommodate Block Load Transfers and make the treatment of ERCOT and Non-ERCOT loads similar. Removed boxed text (pip 209) as the language should be capable of being implemented immediately with no changes to the system design.11/05/2001Yes5.7Approved
PRR290Balancing Energy Down BidsAn across-the-board mandatory balancing down requirement can prevent QFs such as Gregory from providing contracted service to their thermal host. This reduces the reliability of QF service, threatens the thermal hosts service, potentially violates PURA §39.151 (l) by interrupting an internal process operation associated with an industrial generation facility, and is opposed to federal policies favoring QF development.10/04/2001No4.4.5Withdrawn
PRR291Section 16 Testing RequirementsAdds language for Retail Market testing.10/09/2001No16.2.1, 16.3.1, 16.4 & 16.6Approved
PRR292Revise Resource Specific Payment FormulaRevise the formulas to reflect the language.10/10/2001Yes7.4.3.1 &
PRR293Uncontrollable Renewable ResourcesRequest Boxing of Existing Language since functionality does not exist to provide for this functionality and there is no viable manual work-around.10/10/2001Yes6.
PRR294Clarify LSE Load Ratio Share Data RequirementsClarifies the requirements of PIP 144.10/12/2001No6.3.1 & 4.4.4Approved
PRR295Obligation Default ChargesProvide formulas to reflect the language for the treatment of default QSE financial responsibility.10/15/2001Yes6.9.1Approved
PRR296Zonal Congestion Implementation DateThe BOD voted to approve a date of 2/15/02 for the implementation of direct assignment of zonal congestion costs. The availability of auctioned and pre-assigned TCRs may be on or after January 1, 2002.10/19/2001Yes7.3.3; 7.3.4; 7.5.1 &
PRR297LaaR & BULs Provisional QualificationThis revision provisionally qualifies certain loads that were served on an interruptible tariff, participated in a group load curtailment tariff, or participated in a direct load control program on August 1, 2001 to act as a load acting as a resource (LaaR) or a balancing up load (BUL), provided the load can meet the metering and performance criteria outlined in the Protocols.10/25/2001YesNew language to be added after 6.10Approved
PRR298Revise Settlements CalendarThis PRR requests changes to the Settlement Payment Calendar for Initial Statements and Final Statements only. The payment dates are kept the same according to the settlement calendar by changing the due dates of invoices from net-30 to either net-16 or net-9, depending on the preferred 2 or 3-week change approved.10/29/2001Yes9.2.3; 9.2.4; 9.2.5; 9.3Approved
PRR299TCR Congestion ManagementChanges the 60-day notice requirement to 30-days for the initial annual TCR auction only.11/06/2001Yes7.
PRR300TCR Congestion ManagementEstablish Congestion Management guidelines and requirements for February 15, 2002. Strike System Congestion Fund upon conversion to direct assignment of Zonal Congestion costs. Strike Zonal Congestion Tracking upon conversion to direct assignment of Zonal Congestion costs.11/15/2001Yes2; 6; 7; 9; 16Approved
PRR301Over scheduling Load Imbalance LimitsProvides an upper limit for Load Imbalance credits to QSEs when the QSEs load is significantly overscheduled.11/28/2001No6.9.5.2Withdrawn
PRR302BUL Capacity Payment CalculationThis revision establishes a baseline approach for calculating the BUL capacity payment based on historical data. The baseline would be based on a 10-day average of actual metered load. The baseline will be adjusted to actual load in the two hours prior to notice to reflect temperature sensitive load and to address gaming concerns.11/29/2001No6.8.1.14 &
PRR303Move-in RejectionsThe stacked move in resolution modified the Not First In validation to allow a Move In when another Move In is pending, but only when the requested Move In is LATER than the pending Move In.12/07/2001Yes15.1.4.9Approved
PRR304Unexecutable Move-inThe new 814_28 and 814_29 notification request/response will be used to communicate that the service order is unexecuted. The header will include the permit flag, the un-executable flag, and the same Reason codes as on the 650_02.12/10/2001Yes15.1.4.5; [new]Withdrawn
PRR305Inter-QSE Trades Under DA Cost AllocationClarifies language and formulae in Section 7.3.4 to indicate the recognition of Inter-QSE trades12/19/2001Yes7.3.4Approved
PRR306TCR Ownership LimitationMinor revision to existing Protocol 7.5.7 referencing new section 7.5.9 regarding limitation and ownership of TCRs to create an effective market for TCRs and adding new Section 7.5.9 to limit TCR ownership.01/14/2002No7.5.9Approved
PRR307Controllable ResourcesThis revision defines Load which can provide Regulation Service.01/03/2002No2.1, 5.6.7, 6.1.2, 6.1.3, 6.1.4,, 6.5.2, 6.5.3 6.5.4, 6.5.6, 6.7.3,,
PRR308Settlements Calendar RevisionThis Protocol revision is written to request changes to the Settlement Payment Calendar for Initial Statements and Final Statements only. The payment dates are kept the same according to the settlement calendar by changing the due dates of invoices from net-30 to either net-16 or net-9, depending on the preferred 2 or 3-week change approved.01/09/2002Yes9.2.3, 9.2.4, 9.2.5 & 9.3Approved
PRR309TDSP Demand Reporting RequirementWording changes in demand reporting requirements that better reflect the intent of the current Protocol language.01/07/2002No10.3.3.1(3); 18.6.6Approved
PRR310Estimating Usage Applied to ProfilesRevise formulas to estimate usage when no actual meter read data is available for the day being estimated.01/07/2002Yes11.3.2 &
PRR311DLC to BUL TransitionPermits load control or load management programs involving small energy consumers (under 1 MW) to provide a balancing-up load (BUL) without the requirement that interval data recorders (IDRs) be installed on all of the participating energy consumers. A sampling approach, consistent with ERCOTs load profiling requirements for direct load control programs, shall suffice.01/08/2002No6.10.5.2, 6.10.2, &
PRR312Enhance ESI ID Look-up FunctionProvide additional information for an ESI ID to include Station ID, Power Region, Premise Type, status (active/de-energized/inactive) for an ESI ID.01/14/2002No15.2Approved
PRR313TCR Transfer DeadlineThis revision specifies a time limit on the transfers of TCRs in the ERCOT TCR database.01/14/2002Yes7.5.7Approved
PRR314Minimum Time Unit for Resource AvailabilityXML documentation states that the LEAD-TIME value has to be entered in minutes. Protocols need to be revised to state the correct time interval, currently "hours."01/23/2002Yes4.4.16 (6)Approved
PRR315Cost Recovery for OOM Down(1) Allow for the recovery of Production Tax Credits. This is particularly important for Wind resources since the provision of energy at no cost, as is provided by the current pricing structure, does not provide the ability to recover the lost production tax credits that would have been earned had the Wind resource generated the electricity. (2) Clarify RODP for Wind Resources,. the change will clarify that the RODP found in paragraph (4) for Wind Resources will be zero (same as Nuclear & Hydro).02/04/2002Yes6.8.2.2Rejected
PRR316CR Switch CancellationAdd language in section of the protocols to say specifically that a CR does have the ability to cancel a pending switch.02/04/2002Yes15.1.1.4Approved
PRR317Revise Computation Procedure for TCRsClarify and modify determination of CSC limits and TCRs.02/05/2002Yes7.5.2,,
PRR318Two Zone AdjustmentAdd methodology to alleviate the situation of one station having transmission busses assigned to two different transmission congestion zones.02/22/2002No7.2.1.2Approved
PRR319Load Ratio Share Used to Determine AS ObligationRevised the language in Section 6.3.1 to reflect that the Load Ratio Share used to determine AS Obligation will be for the same hour and day of the week and from the initial settlement data that is available.02/28/2002Yes6.3.1Approved
PRR320Loads Participation in AS MarketThe testing and monitoring requirements for responsive reserves and non-spinning reserves prohibit a QSE from delivering such services at levels above defined limits. For testing, the QSE cannot deliver more than 105% of the requested reserves. For monitoring, the QSE cannot deliver more than 120% of the requested reserves. The proposed revisions eliminate these upper limits on testing and deployment for loads acting as a resource.03/01/2002Yes6.10.3.2(4);; &
PRR321Uninstructed Resource Charge ProcessStates that a QSE is subject to the uninstructed charge for over-generation when the MCPE is positive, when regulation is determined to be over or under the defined bandwidth.03/14/2002Yes6.8.1.15;
PRR322RPRS Award PerformanceCurrent Protocols language potentially could allow a QSE receiving an RPRS award/ deployment to be paid without starting the awarded unit. This is possible because the performance measures only require that the QSE submit balancing bids in an amount equal to the RPRS award and do not specifically require that the QSE start the unit.03/21/2002No6.10.8Approved
PRR323TCR Creditworthiness MonitoringUpdate creditworthiness language to match the TCR Agreement.03/22/2002Yes16. &
PRR324EPS Meter Polling TimelineRevises requirements for polling of EPS meters based upon change in timeline for initial settlement.03/26/2002Yes10.3.2; 11.1.1; 11.1.2; 11.1.4Approved
PRR325Sub-QSEs Partition LimitRevise the Protocols to increase the maximum number of Sub-QSEs an Entity can implement from three to ten.04/15/2002Yes16.2.1Approved
PRR326Day Ahead ScheduleUpdate the definition for the Day Ahead Scheduling Process to end at 1800 instead of 1630.04/19/2002No4.4.1Approved
PRR327Confidentiality(1) Revise the definition of "Protected Information" and conform the provisions of § to reflect changes made to the definition of "Protected Information." (2) Impose a time limit on confidentiality of information. (3) Clarify that the PUCT, after notice and opportunity for hearing, may declassify information.04/24/2002No1.3;;; & 1.3.7 [new]Approved
PRR328Customer Service Establishment NoticeEliminates the protocol language requiring that Move-In service establishment notices be sent to all Customers.04/29/2002Yes15.1.4.3Approved
PRR329TCR Simultaneous Combinatorial AuctionThis revision was drafted by the Congestion Management Working Group of the Wholesale Market Subcommittee to implement the Public Utility Commission of Texas order to convert the simple auction to a combinatorial auction of TCRs (Transmission Congestion Rights).05/07/2002Yes7.5.3.2 &
PRR330IDR meter data for True-Up settlementRequire that 95% of the IDR meter data be available for true-up settlement to take place.05/06/2002Yes9.2.6Approved
PRR331OOMC Floor PriceRevise OOMC Payment calculations so that such deployments are not pay as bid & establish the OOMC floor payment as discussed in the PRS recommendation of PRR285.05/06/2002Yes6.8.2Withdrawn
PRR332Unit Resource TestingThis revision recognizes prudent operating practices by prohibiting the ISO from issuing resource-specific dispatch instructions while the resource is in the process of pre-COD testing, required seasonal real and reactive testing, and testing necessary prior to and returning from annual planned maintenance05/13/2002No4.5.2; 5.4.3; 5.6.7; 6.10.2 & 6.10.3Approved
PRR333OOM Down Cost RecoveryDevelop a methodology for compensating uncontrollable renewable Resources that incur costs greater than the OOME Down payment.05/23/2002Yes6.8.2Approved
PRR334Generator Ratio ShareThis PRR is one of a group of PRRs [#s 334-340] that the submitter requested be considered as a single vote. Specifically, this PRR modifies the process of uplifting local congestion charges so that generators pay for local congestion costs.05/20/2002Yes2.1 & 6.9.7Rejected
PRR335Generic CostsThis PRR is one of a group of PRRs [#s 334-340] that the submitter requested be considered as a single vote. Specifically, this PRR adds a new section to incorporate generic costs associated with resources that will be used to calculate payments when a resource provides Out-of-Merit Service. The generic resource costs added are: generic fuel cost, generic startup costs, and generic operating costs.05/20/2002Yes6.8.2Approved
PRR336OOM DownThis PRR is one of a group of PRRs [#s 334-340] that the submitter requested be considered as a single vote. Specifically, this PRR revises the OOME Down pricing to a cost-based mechanism.05/20/2002Yes2.1 &
PRR337OOM Up Pricing MethodThis PRR is one of a group of PRRs [#s 334-340] that the submitter requested be considered as a single vote. Specifically, this PRR revises the OOME Up pricing to a more conservative cost-based pricing mechanism.05/20/2002Yes2.1 &
PRR338OOMC Pricing MethodThis PRR is one of a group of PRRs [#s 334-340] that the submitter requested be considered as a single vote. Specifically, this PRR revises the OOMC from bid/premium-based pricing to cost-based pricing.05/20/2002Yes2.1, &
PRR339REC for OOM DownThis PRR is one of a group of PRRs [#s 334-340] that the submitter requested be considered as a single vote. To be fair to renewable resources without increasing the costs of Local Congestion, this PRR credits renewable resources that provide OOME Down service by awarding the resource RECs for energy not generated by the renewable resource due to providing the OOME Down service. This solution will also require an amendment to PUCT Substantive Rule 25.173.05/20/2002Yes14.7Withdrawn
PRR340Remove Market Solution DefinitionThis PRR was originally part of a group of PRRs [#s 334-340] that the submitter requested be considered as a single vote. Remove the Market Solution concept as part of the mechanism for resolving Local Congestion. Renamed: Define OOME as an Instructed Deviation. The revised PRR allows for the deployment of dispatch instructions for OOME and does not remove the Market Solution definition.05/20/2002Yes2.1, 4.1.2, 4.5.3, 6.1.10, 6.1.11, 6.3.1, 6.4.2,,,, 6.7.8,, 7.1,, 7.3.2, 7.4.2,,,, 7.4.4, & 7.6Withdrawn
PRR341Transmission Facility Status Change NotificationAdd language that allows flexibility in maintaining specific equipment that currently does not exist with ERCOT Outage Coordination efforts.05/23/2002Yes5.5.2Approved
PRR342AS Simultaneous SelectionModification of ancillary service bid selection process to allow simultaneous occurrence of Regulation Up, Responsive Reserve and Non-Spinning Reserve.05/24/2002No4.4.11; 4.4.12; 6.6.2 & 6.6.3Approved
PRR343BES Ramp RateAdd language to describe a typical ramp duration & clarify the deployment period as the operating interval. WMS requested clarification of the current Protocol text.06/04/2002Yes6.5.2(18)Approved
PRR344Bid ClearingRevises language to comply with the implementation of PIPs 147 & 148; bids will be carried over to the next market if there is one.06/13/2002Yes4.4.11Approved
PRR345Multi-SettlementThis revision pays all providers the highest clearing price for the market they were awarded and all subsequent markets. Thus if a subsequent market cleared lower than an earlier market, the providers in the subsequent market will not get the benefit of the earlier clearing price.06/20/2002Yes6.6.3 & 6.8Approved
PRR346MVA Data Calculation ResponsibilityEliminate redundant requests for data, specifically MVA.07/01/2002No12.
PRR347OOMC Pricing Formula ClarificationThis PRR clarifies the equations originally proposed by PRR338.07/02/2002Yes6.8.2.1(5)Approved
PRR348Confidentiality CleanupLimits the time that REC account information is protected from disclosure to 1 year after the end of the applicable Compliance Period.07/25/2002Yes1.3.3(1)(c)Approved
PRR349UBES-DBES Ramp RatesIncorporates the QSE's bid ramp rates when ERCOT issues instructions for a QSE to change its Balancing Energy service deployment from the previous Settlement Interval to the target Settlement Interval.07/25/2002Yes6.5.2(16), (17), (18), (19) & add new (22)Approved
PRR350Smoothing Algorithm RevisionThis revision will change the calculation of the Schedule Control Error equation in real time.07/31/2002No6.10.4.2Approved
PRR351Load Imbalance Balancing Energy SettlementRevises load unit from MW to MWh.08/06/2002Yes6.9.5.2Approved
PRR352Proxy Day Determination ExtensionThis PRR changes the Non-Weather Sensitive (NWSIDR) Proxy Day determination method to use the most recent historical ESI-ID interval data from the last 12 months.08/07/2002Yes11.3.3.3Approved
PRR353Change Control Classification UpdateEliminates the Transaction Inventory from Section 19. The Transaction Inventory is maintained on the Texas SET website. Updates the change control classification to reflect the current priority classification used by the Texas SET Working Group.08/13/2002No19Withdrawn
PRR354Amend POLR ProcessReplaced references to POLR with Affiliate REP where appropriate in 15.1.2, 15.1.3, and 19.3.1. Added language to 15.1.2 for process used when dropping a customer to the POLR for contract non-renewal. Added language to for ERCOT process of notifying the POLR to submit switches on mass drop in the event of a CR default.08/16/2002Yes15.1.2, 15.1.3 & 19.3.13Approved
PRR355OOME BLT Generic CostsEstablishes Resource Category Generic Cost for Block Load Transfers. Correct the payment equation for start up operational cost. Insert protocols reference to complete the sentence found in protocols section (4) (a) (iv).08/21/2002No6.8.2Approved
PRR356SCE Performance RequirementTo cause QSEs to make better efforts to follow their Resource schedule so that ERCOT can accurately procure Balancing Energy, and to change the allocation of Ancillary Service capacity costs from pure load ratio share to a method that assigns costs to causation. Both reasons are currently of increased importance to assure the operationally smooth implementation of Relaxed Balanced Schedules.08/22/2002No6.10.5.1,,,,,
PRR357Market Solution Definition RevisionThe current definition requires that at least three unaffiliated resources be available for solving a circumstance of local congestion. It is possible to have bids from three unaffiliated bidders that could independently solve an instance of local congestion, except for the fact that one or more of these solutions may not be feasible because of constraints that do not permit the physical dispatch of the resources to resolve the congestion. The proposed definition corrects this by specifying that a market solution only exists when each of the required three bids from unaffiliated bidders has sufficient capacity available to physically solve the congestion.09/03/2002No2.1Approved
PRR358Negative Impact SCEReplaces the Uninstructed Deviation settlement scheme with a new methodology, called Negative Impact Schedule Control Error Charges (NISCE) that penalizes QSEs that fail to adhere to their schedules, which cause additional Schedule Control Error (SCE) and rewards QSEs that are dispatched to compensate for the SCE caused by non-performing QSEs.09/03/2002No2.1, 2.2,,
PRR359Improve Resource PlanRequires the provision of additional information in the Resource Plan and allows updates after the Adjustment Period.09/06/2002No2.1, 4.4.15, 4.5.10 &
PRR360Relaxed Balanced SchedulesAllows for the use of relaxed Balanced Schedules.09/06/2002Yes2.1, 4.1.1, 4.3.2, 4.4.15, 6.4.2, 6.5.10, & 6.10.8Approved
PRR361Section 15 UpdateUpdates Section 15: (1) to use the 814_82/29 for both Unexecutable and permit Required for move-ins and move-outs only; (2) Special Needs Indicators; and (3) to reflect Implementation Guide language.09/13/2002NoSection 15 [several]Approved
PRR362Load Profiling Guide - Correction Procedure to Profile ID TypeRemove procedural details from Protocols and refer Market Participants to Load Profiling Guides.09/17/2002No18.4.4.2Approved
PRR363IDR Data Start-Stop TimesAdd language to require TDSPs (and future Meter Reading Entities) to send only whole days of data for all IDR ESI IDs.09/20/2002Yes10.9.2Approved
PRR364RPRS Payment and Charge CalculationsModify the RPRS settlement calculations to assure proper performance.09/23/2002No6.8.1.10,
PRR365Replace Resource Specific Premium Bid with Price BidReplace resource specific bid premium with a single resource specific bid price.09/25/2002Yes4.1.2, 4.5.3, 6.1.11,,, 6.7.9,,,
PRR366Changes to Pre-Assigned TCRsThese changes are intended to reflect the changes ordered by the PUCT in its Order No. 15 in Docket No. 24770.10/09/2002Yes4.1.2,, Section 7 [several]Approved
PRR367IDR Installation & UseRe-word Section 18.6.1(4) to address two substantive changes:1) Change wording to reflect, IDRs installed at the request of ERCOT, a TDSP, , instead of IDRs installed by ERCOT, a TDSP, .2) Change demand calculation to coincident demand calculation10/14/2002No18.6.1Approved
PRR368Section 18 ReferencesDelete the word Operating (and the following space) from all occurrences of Load Profiling Operating Guides in all of Section 18. In Section 18.5.1, replace as set forth in the Operating Guides to as set forth in the Load Profiling Guides.10/14/2002No18.5.1Approved
PRR369Proposal to Address Dispatching Issues for Combined Cycle Units Through Settlement AggregationChange the way instructions to combined cycle plants are settled to more accurately reflect the operational interdependencies of these plant technologies.10/17/2002Yes6.5.10, & [new]Approved
PRR370Process for Application and Approval of RMR ContractsFormalizes the process for application and approval of RMR contracts, including requirement for notice, opportunity for comment, availability of data, and approval by ERCOT Board. These provisions reflect that RMR is essentially a regulated service provided to the market and therefore calls for greater market scrutiny than other services provided to ERCOT. The PRR is intended to maximize the information available to market participants, while minimizing the constraints on ERCOTs ability to enter into RMR Agreements it determines are needed.10/17/2002Yes1.3.1.2, 6.5.9, [new]Approved
PRR371Minimum Energy OOME When OOMC IssuedLanguage implements a mandatory minimum OOME instruction for the same intervals that OOMC instructions are issued to a unit.10/28/2002No6.8.2.1 &
PRR372Backup Plan RequirementThis revision adds the requirement for a backup plan in the event of a loss of the QSEs or Transmission Operators scheduling center.10/30/2002No16.2.1; 16.2.2 & 16.4Approved
PRR373OOME as Instructed DeviationThis PRR provides a method to define Out Of Merit Energy Service as Instructed Deviation.10/31/2002Yes6.7.7 and new sections &
PRR374RMR Text ChangesReflects previous changes in the Day Ahead timeline, clarifies the use of RMR energy & corrects typos.12/09/2002No4.5.11.1;; 6.7.8, 22F.1.H & 22F.8Approved
PRR375AS Schedule TimesClarifies when AS schedules may be modified.12/23/2002No4.3.5; 4.4.8 & 4.4.14Withdrawn
PRR376Procure Total AS from ERCOTAllows a QSE to purchase ancillary services to cover both their ERCOT allocated ancillary service obligation as well as obligations scheduled to other Sub-QSEs or QSEs.12/23/2002Yes4.7.1Approved
PRR377ERCOT Canceled RMR Unit StartProvides that RMR units are to be partially compensated for start up expenses when ERCOT request a start and then subsequently cancels the start after start up has been initiated.01/03/2003No6.8.3.5Approved
PRR378RMR Units Mandatory Down Balancing BidsExclude energy schedules from RMR units from the requirement to provide mandatory down balancing bids.01/03/2003Yes4.4.5 & 4.5.2Approved
PRR379BLT Waiver [renamed]Provides that resources receiving a waiver from signing the Resource agreement must designate a load serving entity to serve their auxiliary load when the generator is not operating. And adds a new section giving ERCOT the ability to grant a waiver for Block Load Transfer point Resources.01/03/2003No16.5.1.1 & [new]Approved
PRR380Black Start Service(1) Provides RFP evaluation criteria as an appendix to the RFP; (2) Clarifies that the procurement of Black Start Services are annual and that testing is a simulation and not an actual event; (3) Adds criteria for revocation of certification for actual event default; and (4) Defines an additional default criterion.01/13/2003Yes6.5.8, 6.6.2;; 22.7 & 22.10.A.2.eApproved
PRR381Update QSE DesignationOutlines the steps necessary for an LSE or Resource Entity to designate a new QSE when their existing QSE terminates its commercial relationship with the Entity.01/14/2003No16.2.5.1, 16.3.2, 16.5.3, [new], 16.2.13 [new]Approved
PRR382Settlement Statement SuspensionAllows the Board to direct ERCOT to suspend the issuance of Settlement Statements.01/31/2003No9.2.7 [New]Approved
PRR383RMR Resource Maintenance Outage ApprovalAdds a requirement for ERCOT to respond within a specific time period on maintenance outage requests for RMR units.01/21/2003No8.1.4.1; 22-F.8Approved
PRR384Protocol Preamble and Process for Advisory OpinionThe first revision creates a preamble to the Protocols that outlines the expectations of market participants as they apply Protocols in the course of their wholesale activities. The second creates an opportunity for market participants to seek guidance regarding potential ambiguities or uncertainties in the application of the Protocols to wholesale activities by obtaining an opinion from an ERCOT Director. The opinion would be binding and could be relied upon unless or until the PUC or an ERCOT TAC or Board action dictated otherwise.02/06/2003YesPreamble [new],1.5 [new], 1.6, 1.7, 1.8Withdrawn
PRR385DLC ImplementationThis PRR will allow the DLC programs to be appropriately profiled and ERCOT systems to properly process DLC programs.02/05/2003No18.7.2.1;
PRR386Scheduling InformationAdds text where applicable to indicate that not all services are deployed by zone and the services that are deployed by zone will be reported by zone.02/07/2003No12.4.1(3)Approved
PRR387Mismatch Inter QSE Schedules SettlementClarifies, automates & simplifies the settlement of Mismatched Inter-QSE Schedules. Inserts formulas in the Protocols that are needed to settle mismatches.02/12/2003Yes4.7.2; 6.9.8 [new]; 9.6.1Approved
PRR388BUL Capacity PaymentRevise the i variable for the formula calculation from an interval equal to one hour to interval. Make two cleanup changes to references to Load Ratio Share in 6.9.6 and
PRR389Winter Weather Events RequirementIncorporates revisions that require QSEs to project actual interval Obligations during winter weather events that impact resources and can jeopardize the reliability and/or security of the ERCOT System.02/18/2003No2.1; 4.1.1; 4.3.2; 4.3.5Approved
PRR390Transmission Interconnect Notification RequirementsCreates transmission interconnection notification requirements that will establish a timetable for addressing the risks associated with local transmission congestion.02/19/2003No6.8.2.3Rejected
PRR391Waiver Recipients Must Designate an LSEClarifies that resources receiving a waiver from signing the resource agreement must designate a Load Serving Entity to serve their auxiliary load when the generator is not operating.02/21/2003No16.5.1.1(3) [New]Approved
PRR392Posting BE Forecast-PIP138Deletes the box for PIP138 which requires the Posting of BE Forecast.02/21/2003No6.7.1.1(6)Approved
PRR393Balancing Energy Bid Expiration Time-PIP147Deletes the PIP147 box, which allows for expiration time of balancing energy bids.02/21/2003No4.5.2(5)Approved
PRR394Balancing Energy Ramps as Instructed DeviationsRevise Subsection 6.5.2(17) to state that, Energy provided outside of the target Settlement Interval as a result of ramping at the specified rate will be considered an Instructed Deviation.02/27/2003No6.5.2(17)Approved
PRR395Declare Backup Plans Protected InformationClarifies that QSE and TO backup plans are Protected Information.02/28/2003Yes1.3.1.1Approved
PRR396RMR IssuesThis PRR revises the guidelines and compensation of Reliability Must Run Service.04/11/2003Yes6.5.9;; 6.7.8; 6.8.3; 22F; 22IApproved
PRR397McCamey Area Congestion ManagementThis revision is designed to minimize uplifted congestion costs while attempting to reliably maximize the use of the transmission system in the McCamey area where numerous wind turbine generators are currently located and additional wind generators may be constructed.03/19/2003No7.8 [new]; 7.8.1-10Approved
PRR398Combined Cycle SettlementAmends the equations originally revised by 369PRR - Proposal to Address Dispatching Issues for Combined Cycle Units Through Settlement Aggregation, to clarify how the ERCOT system will process this functionality.04/11/2003Yes6.8.2.3; &
PRR399IDR Replacement with Non-IDR Meter RequirementsThis revision allows 1) IDR installations where they are needed or required and provide the most effective utilization of this type of reporting to ERCOT; and 2) Removal of IDR installations that are no longer valid for a premise or ESI ID because of reduced load or consumption based upon 12-month consecutive usage data.04/15/2003Yes18.6.1 & 18.6.6Withdrawn
PRR400LaaR Provisional QualificationAllows loads to begin participating in the market as soon as their loads meet all telemetry and calibration testing until such time as an actual load interruption test can be scheduled with ERCOT and the load facilities.04/15/2003Yes6.10.1Approved
PRR401Partial Payments & CreditUpdates ERCOTs calculation of each QSEs Total Estimated Liability and Estimated Aggregate Liability; and clarifies that ERCOT has the ability to offset amounts owed to and from a QSE that does not remit a payment in a timely manner.04/16/2003Yes9.4.4; 16.2.5-9Approved
PRR402Delete Good Friday HolidayThis PRR deletes Good Friday from the list of observed holidays in the definition of a Business Day.04/17/2003No2.1Approved
PRR403URC Update Due to Smoothing Algorithm RevisionClarifies and describes in detail the changes to the URC equation as a result of the implementation of PRR 350. Specifically describes how to treat DC Tie Schedules when calculating the schedule to be used in the URC calculation.04/16/2003Yes6.8.1.15Approved
PRR404Energy Procured from ERCOTExpands the functionality of Relaxed Balanced Schedules by allowing Market Participants to schedule up to 500MW of generation from ERCOT.04/17/2003No4.3.2Approved
PRR405RPRS Under Scheduled Capacity (PIP132)This PRR inserts the boxed text in to reflect the implementation of PIP132, which was implemented on May 23, 2002, and revises text in to match wording changes made by PRR394.04/17/2003No6. &
PRR406Two Year CSC & Zone SelectionRevises the current one year forward establishment of CSCs and zones to a two year forward approach.04/18/2003Yes7.2Withdrawn
PRR407Sunset Date Removal for RBSThis change removes the sentence that would restrict ERCOT from initiating a limitation or suspension of relaxed Balanced Schedules and clarifies that ERCOT may consider financial integrity issues in such limitation or suspension.04/24/2003Yes4.3.5Approved
PRR408HVDC Tie Schedule DataClarifies that ERCOT is responsible for the accurate accounting of all generation produced and delivered within ERCOT; clarifies that in addition to providing the necessary data for the 4CP calculation, ERCOT must provide the necessary data for TDSP billing under FERC tariffs as they apply to the HVDC interconnections.04/24/2003No1.2(4);; 9.1; 9.8.2 [new]Approved
PRR409Voltage Support ServiceThe current Protocols allow for excessive reactive dispatching on the part of TSPs without compensation to generation owners. This PRR changes the power factor envelope from +-.95 to +-.98, and allows for payment to generators.04/28/2003No6.5.7, 6.8.4Approved
PRR410Resource Obligations During BLTSpecifically addresses generators' right to decide availability based on concerns of Jurisdiction, tariffs, or increase risk of assets when the transmission area the resource is connected to, is tied to a non-ERCOT system other than through a D.C. Tie.04/28/2003No5.7.3Approved
PRR411Protocol Clarification Process (original title: Advisory Opinion)Provides a clarification process for interpretation of the Protocols. This PRR was severed from PRR384 Code of Conduct & Advisory Opinion.04/29/2003No21.1Approved
PRR412Distributed Generation With No Energy ExportThe revision would clarify that, for distributed generation resources that do not export energy to the ERCOT System, and are located on the Customers side of the Service Delivery Point of the retail customer of a NOIE or on the Customers side of the Service Delivery Point of a Premise with an IDR meter, separate resource metering, scheduling, data submission and settlement is Not required04/01/2003No10.2.2Withdrawn
PRR413Optimization for the whole operating day in RPRS procurement processModify RPRS procurement process so that RPRS procurement process is an optimum solution for the whole operating day.05/13/2003No4.4.16, 6.3.1, 6.5.9,, 6.7.8,,,, 7.4.2Approved
PRR414Sunset Date on BE Bid CapRemove July 4, 2003 sunset date for Balancing Energy bid caps per PUCT order.05/15/2003Yes4.4.11, 6.5.2Approved
PRR415Establish 50% as Limit for LaaRs Providing RRS and NSRSRemoves reference to Operating Guides and establishes 50% as the maximum limit for the quantity of Loads acting as Resources that can provide Responsive Reserve Service (RRS) and also allows ERCOT to adjust the 50% limit monthly on a planned basis and daily on an emergency basis if such a limit could adversely impact reliability or deployment of Regulation. This PRR also specifies how the total ERCOT quantity would be divided among QSEs.05/21/2003Yes4.4.3, 4.5.2, 6.4.1, 6.5.4(8),, 6.7.4(11)Approved
PRR416Amendment to Posting of Balancing Energy InformationNew subsection establishes reporting requirements for QSEs that posts the name of any QSE submitting bid for Up Balancing Energy Service with the last price/volume bid being a volume less than three (3%) of the QSE's total volume in that bid curve and is greater than three times the price of the immediately preceding price/volume pair included in that bid curve.05/21/2003Yes1.3.3(2)(c)Approved
PRR417Changes to 814_06, Handling Move InsChanges to transmission of 814_06, New handling of Move-Ins that reject for ESI ID invalid, Change in requirement for Start and Eligibility dates, and reference to new 'Ignore CSA' flag.05/22/2003Yes15.1.1.9,,,,,,
PRR418Creation of New CSCModify Section, create new section, Approval Process and add language related to a new CSC effective July 1, 2003 through the remainder of 2003.05/23/2003Yes7.2.1.3Withdrawn
PRR419Transfer of BUL Qualification Testing Responsibility from ERCOT to QSEsThis revision transfers the responsibility for qualification testing for BUL from ERCOT to the QSE representing the BUL.05/23/2003Yes6.10.2,
PRR420MCSMImplements PUCT's order to ERCOT to adopt an interim automatic mitigation procedure for balancing energy prices.05/23/2003Yes6.5.2.(22) [new], [new]Approved
PRR421Conformance with New PUCT Substantive Rule 25.362Revise Protected Information requirements to conform with new P.U.C. SUBST. R. 25.362.05/27/2003No1.3.4, 1.3.5, 1.3.6, 1.3.8Approved
PRR422OOM Zonal Dispatch InstructionsProvides detail on deployment and settlement of Zonal OOME Dispatch Instructions in command and control conditions05/29/2003Yes6.1.12, 6.2.1, 6.3.1, 6.5, 6.5.9, 6.5.11, 6.6.5,,,, 6.7.8, 6.8.2,,
PRR423Dispatch of QFs Below Minimum Generation LevelsThis PRR would limit ERCOT's ability to dispatch QFs to a value no lower than their Minimum Generation Level, except in the case of an imminent Emergency.06/06/2003Yes4.4.15Approved
PRR424Elimination of Resource Specific Deployment Used for Energy Balance PurposeThis PRR will eliminate the Resource specific deployments for energy balance purposes and will reduce the cost of Local Congestion that is currently uplifted to all Loads.06/13/2003Yes6.7.1.2, 7.3.2,,
PRR425Section 8 Outage CoordinationIt moves subsections pertaining to Transmission so they are together and makes minor changes to Transmission Outage requirements. Adds some requirements for RMR and Black Start Outages.06/13/2003No2.1,, 8Approved
PRR426URC for Uncontrollable ResourcesDefines an Uncontrollable Renewable Resource and allows wind resource to elect to use their Renewable Production Potential in lieu of their schedule as the basis for URC charges and OOME Down payments.06/13/2003No2.1,
PRR427RMR General ClarificationsThis PRR would clarify the changes to the RMR provisions adopted in May by the ERCOT Board.06/17/2003No6.8.3.1,, 9.4.4Approved
PRR428RMR Scheduling ClarificationsThis PRR would document/clarify the scheduling process for energy from RMR Units.06/17/2003Yes4.,,
PRR429ERCOT Disclosure of Information to TDSPsThis PRR would add instructions to ERCOT to disclose and share with a TDSP any confidential information it has received or has knowledge of that would affect the operation and security of a TDSP.06/18/2003Yes1.3.6Approved
PRR430Historical UsageThis PRR would add language that specifies usage provided for conversion/opt-in be reported in time intervals no longer than thirty-eight days.06/18/2003No19.3.1Withdrawn
PRR431Collateral Requirements for RBS and EALThis PRR would add a new section to calculate additional collateral requirements for QSEs intending to utilize the Balancing Energy Service more than 20%; excludes certain portions of the EAL calculation from the 60-day "look back" provision; reduces the number of days in which collateral must be posted from 3 to 2; and allows ERCOT to accelerate the due date on all outstanding amounts owed in the event of a late payment.06/19/2003Yes16.2.7, 16.2.8, 16.2.9Approved
PRR432Liability for LSE DefaultThis PRR would allocate responsibility for LSE default among Generation Entities, LSEs, and TDSPs.06/19/2003No2.1, 9.4.4Withdrawn
PRR433Change Percent Deficit Banking of Renewable Energy CreditsThis PRR would change the deficit banking amount from 5% to 10% for the first two compliance periods.06/25/2003No14.11.1, 14.11.3Approved
PRR434Adjustment to Allocation of REC Purchase RequirementThis PRR would make adjustments to the annual allocation of REC purchase requirements to reflect changes in retail energy sales for a Competitive Retailer resulting from a final true-up or resettlement completed after the ERCOT notification deadline.06/25/2003No14.1Withdrawn
PRR435Confidentiality of LSE Transaction DataThis PRR would add transaction information submitted by an LSE to ERCOT or received by an LSE from ERCOT as a new category of protected REP specific information06/30/2003No1.3.1Withdrawn
PRR436Enhance LaaR/BUL Ability to Participate in Balancing Energy Up Service, Non-Spinning Reserve Service, and Responsive Reserve Service MarketsThis PRR would include the changes proposed by the Demand Side Working Group to clarify the role of Loads in the Ancillary Service and BUL markets.06/30/2003Yes6.5.2, 6.5.4,,,,,, 6.10.8Approved
PRR437867_03 Timeline ChangeERCOT Protocols Chapter 15, Section 3, Monthly Meter Reads contains no timeline for the TDSP to send the 867_03 to ERCOT. Add verbiage to the first paragraph to add 867_03 TDSP to ERCOT timeline verbiage.07/01/2003No15.3Approved
PRR438REC TimelinesRevises reporting, issuing and mandated retirements requirements based upon change for final settlement.07/02/2003No14.2, 14.4.2, 14.6.2, 14.7, 14.10, 14.10.5, 14.11.1, 14.13, 14.14Withdrawn
PRR439Clarification on Defining OOME as Instructed DeviationTo clarify two exceptions on defining OOME as Instructed Deviation for the implementation of 373PRR.07/08/2003Yes6.7.7Approved
PRR440Interim Removal of Market SolutionThis PRR would remove the consideration of a Market Solution for local congestion under any circumstance on an interim basis until December 31, 2003.07/16/2003Yes7.4.3Approved
PRR441Protocol Revision ImplementationRequires estimated implementation dates to be developed for PRRs that are approved by the PRS.07/22/2003No21.4.5, 21.6 [New]Approved
PRR442Profile Development Cost Recovery Fee/Approval of a Profile Segment Change RequestThis is a new section to specify the reimbursement process required per the PUCT related to a Non-ERCOT Sponsored Load Profile and to implement a procedure to allow provisional approval of a profile segment change request.07/22/2003Yes9.9 [New]; 18.2.9Approved
PRR443Competitive Metering Ownership ImplementationDefine the requirements of Competitive Meter Ownership and establish a reference to the fact that Competitive Metering Guides will exist.07/23/2003Yes10.1Approved
PRR444Move In Move Out (MIMO) StackingMarket Participant solution for handling multiple non-sequential transactions on a single ESI ID.07/30/2003No15.1Approved
PRR445Amendment to Protocol Revision Request Designation and Review Time Period for those PRR’s deemed as “Urgent” and the Urgent Review TimelineEstablishes new Protocol 21 guides under sections 21.4.3 and 21.5 regarding the Protocol Revision Request Designation for those PRRs deemed as Urgent, minimum Urgent Review Timeline in relation to those PRRs initiated by the market or by PUC activity to allow adequate review and comment time for market participants and justification requirements for those PRRs being submitted for "Urgent" status.07/31/2003No21.4.3; 21.5Rejected
PRR446Disclosure of OOMC DeploymentsProvides for disclosure on the date of Initial Settlement, but no sooner than day 14, of each unit receiving an OOMC Dispatch Instruction, intervals for which the instruction was received, intervals for which and quantity of energy deployed by ERCOT from units receiving an OOMC Dispatch Instruction.07/31/2003Yes1.3.1.1; 6.5.10Approved
PRR447TCR Credit Limit Constraint Based on Clearing PricesThe first revision (Change wording in ( c ) to express Credit Limit constraints) reflects the enhancement to the TCR auction engine design to apply credit limit constraints based on auction clearing prices instead of bid prices. This revision becomes effective on December 1, 2003. The other revisions are representing corrections and/or embellishments to existing wording.07/31/2003No7.; 7.5.6Approved
PRR448Changes to implement Balancing Up Loads (BULs) and Block Deployment of LaaRsClarification of Balancing Up Load (BUL) calculations, removal of BUL Resource Plan language, and inclusion of BUL capacity payment calculations in Section 6.8.08/05/2003Yes6.8.1.14;;
PRR449Successful Data Validation Response for 867sERCOT will provide a response to TDSPs when data has been loaded or cancelled successfully based on system changes in PR-30125 (Data Loading Project).08/05/2003No11.2.2Approved
PRR450BLT Generic Cost Fix AgainDuring the course of approving 371 the resource generic cost for Block Load Transfers were inadvertently omitted. This simply maintains the BLT category generic fuel cost that is currently in effect when the language from 371 is removed from the box.08/07/2003No6.8.2.1Approved
PRR451Clarification of Ancillary Services Obligation CalculationClarification that ERCOTs calculated AS Obligations for its Day Ahead Operating Day Ancillary Services are based on Initial Settlement data only for the purpose of setting up the Day Ahead plan. After the Operating Day, the AS Obligation calculations are to be adjusted according to actual Metered Load Ratio Share throughout the entire settlement process, in the same manner as Load Imbalance, BENA, etc.08/12/2003No6.3.1, 6.9.1,,,,
PRR452Unavailable Units and RMR AgreementsAdds requirement for ERCOT to follow the RMR evaluation and notice requirement for units unavailable for an extended period due to non-Outage reasons. Adds requirement for Resources to remain available during RMR Agreement negotiations.08/18/2003Yes8.1.4.1Approved
PRR453Black Start Service Voice CommunicationChanging the Black Start Service Bid date from October to June of each year conforms current expectations of Black Start Services bidding. Provides ERCOT an avenue to assess and possibly specify certain communication facilities deemed necessary to restore the ERCOT System during a blackout.08/18/2003No6.4.2; 6.5.8Approved
PRR454OOME Off-lineWhen a generation unit receives an OOME instruction that would force it off-line, ERCOT must provide OOME instructions until the unit was scheduled to come off-line, or an OOMC instruction when the unit is requested to return.08/18/2003Yes2.1, 6.5.10, [new], [new]Approved
PRR455Liability for QSE default on obligations to ERCOT and Responsibility for ERCOT Administration FeeSpreads risk of default of a QSE and ERCOT costs among both Loads and Resources.08/25/2003No9.4.4; 9.7.1Withdrawn
PRR456Disclosure of Identity of Short Paying QSEsRequires disclosure of the identity of short paying QSEs.08/25/2003No9.4.4Approved
PRR457Balancing Energy Down Requirement RevisionPRR will change the Balancing Energy Down Requirement to apply to MWh capability above the QSEs Low Operating Limit for the units in operation in their portfolio.08/25/2003No6.5.2Approved
PRR458LaaR OOMC and OOME Deployment and PaymentsThe purpose of this PRR is to clarify how ERCOT is currently handling OOME and OOMC with regards to LaaRs.08/26/2003No4.4.15; 6.5.10;;; [new]Rejected
PRR459EPS Meter Data TransmittalERCOT has implemented some of the requirements of PIP204 and PRR283; as a result the content and the order of some of the text previously shown as boxed has been altered. This PRR clarifies the features currently implemented and identifies within the boxed Protocol language those features which are still pending implementation.08/27/2003No11.1.10; 11.1.11Approved
PRR460CSC Exemption CriteriaCurrently, requests are made for exemption; however, there is no criterion in the protocols for evaluation of the request. This revision provides criteria for TAC and the Board to consider when evaluating the merits of an exemption request.08/29/2003Yes7.2.1.1Approved
PRR461Confidentiality Exceptions for Reliability AnalysisRevises the exception of 1.3.6(9) to allow Market Participants Protected Information for the purposes of developing analysis of system events; Adds an exception for limited public reporting of the status of facilities in significant events09/02/2003No1.3.6Approved
PRR462Market Solution DefinitionRevises the definition of Market Solution to allow for submittal of bids in circumstances including reliability needs other than local Congestion.09/04/2003No2.1Rejected
PRR463PCR Allocation Regarding the 25% TCR Ownership LimitClarifies that the allocation of PCRs shall not exceed 25% of the total available TCRs on any CSC for any single direction. Also, clarifies that the 25% ownership limitation applies to TCRs and/or PCRs at a CSC interface.09/04/2003Yes7.5.6; 7.5.9Approved
PRR464Confidentiality of LSE Transaction DataThis PRR would add transaction information submitted by an LSE to ERCOT or received by an LSE from ERCOT as a new category of protected REP specific information09/05/2003No1.3.1.1Approved
PRR465Customer Service Satisfaction SurveyRequires ERCOT Staff to perform a survey of Market Participants to gain feedback on their performance.09/10/2003No17.7 [new]Rejected
PRR466Extension of No Market SolutionThis revision would extend the current expiration date for the suspension of Market Solution from December 31, 2003 to July 1, 2004.09/15/2003No7.4.3Approved
PRR467Elaboration on the Notice of ResettlementThis PRR would request ERCOT to elaborate on the Notice of Resettlements and provide formality and structure to the Notices.09/15/2003No9.2.5.1Approved
PRR468Frequency Response Requirements and MonitoringAdds Section 5.8, establishing requirements for QSE portfolio generator governor response, and establishing performance monitoring criteria.09/22/2003No5.8, 5.8.1,,, 5.8.2,,,, 5.8.3,, [all sections new]Approved
PRR469Compliance for Competitive Metering and 25516 Rulings to Load ProfilingChanges to address responsibilities of TDSPs, ERCOT and Competitive Retailers related to sampling, TOU schedules and DLC. Additionally, some out of date wording has been updated or removed.09/26/2003No18.2.5,,,, 18.3.3, 18.4.2, 18.4.3, 18.5.1, 18.5.3, 18.6.3,,,,,,,, 18.8 [new]Approved
PRR470System Fuel AvailabilityInserts new wording to the existing language in Section 5 to include fuel availability as a concern for an emergency condition..10/03/2003No5.6.3, 5.6.4, 5.6.6Approved
PRR471NIDR to IDR Default Profile ScalingWhen an ESI ID changes meters and profile ID assignment when changing from a NIDR to IDR meter, the IDR data is likely to be unavailable for at least the Initial Settlement. Currently the IDR default profile would be used and is likely to be an over statement of the Load for the ESI ID. By scaling the IDR default profile based on the Load of the last NIDR readings would greatly reduce the variance.10/08/2003No11.3.3.3Approved
PRR472ERCOT Meter Read Transaction Validation ReinstatementEnsures that meter read transactions received by ERCOT from the TDSP or any 3rd party service provider have been completely validated for technical, business and data set points prior to ERCOT's submittal of the transaction to the Market Participant(s) designated to receive the information10/29/2003No10.12.1, 15.3Rejected
PRR473Reactive StandardsThis PRR is intended to make the Protocols conform to the Reactive Standards adopted by TAC. Those portions of the standards that are most appropriately contained in the Protocols are included while other sections are judged to be best located in the Operating Guides. The PRR also includes a specific payment mechanism for induction generators that elect to make a payment in lieu of meeting the installed standard.10/30/2003No2.1, 5.1.3, 5.2, 5.2.1 [new], 5.2.2, 5.2.3, 5.5.1, 5.5.2, 6.1.7, 6.4.2, 6.5.7, [new], 6.7.6, 6.8.4,, 6.10.9, 12.4.3Approved
PRR474Short Pay Payment PlanThe knowledge of short payment plans are essential for QSE(s) and the Entities they represent to ensure proper allocation and tracking of funds owed. Without this knowledge it is extremely difficult for QSE(s) to manage their respective accounting processes. Urgent status is requested due to this information being essential to year-end account book closing and therefore the plans must be made available to QSEs by the end of the year.11/10/2003Yes9.4.4Approved
PRR475Unit Specific Deployment based on Generic CostsCurrently, units are deployed based on the up and down bid premiums submitted in the Resource Plan. With the removal of Market Solution, units are paid based on generic cost for all instructions. Implementing this PRR would bring deployment in line with settlement, deploy the more economical units in instances of Local Congestion, and result in lower Uplift cost.11/13/2003Yes4.4.20 [new],
PRR476Ramp Rate Adherence During Local CongestionCurrently, the ramp rates on individual resources are ignored during Local Congestion. This leads to Dispatch Instructions that are impossible to adhere to, especially when every unit running for a QSE is getting a unit specific instruction. Although a QSE may ignore category 4 instructions, they must still follow the category 1. In the event that every unit running for a QSE in a zone is getting a category 4, they all make up the category 1. As a result of the ramp rates being violated, SCE cannot be followed, which puts a strain on frequency which leads to regulation and balancing instructions. Further, the QSE can potentially be penalized with imbalance charges for not keeping SCE at 0.11/13/2003Yes6.7.1.2, 6.10.7Withdrawn
PRR477Section 19 Texas Standard Electronic Transaction (SET)Updated verbiage to better understand the transactions and bring Section 19 inline with the current ERCOT change control release for new transactions and transaction that were removed.11/19/2003No19Approved
PRR478Use of Lagged Dynamic Samples for New Load ProfilesThis is a change to the method for creating Load Profiles allowing for the use of lagged dynamic samples for new profiles adopted subsequent to market open.11/19/2003No18.2.2, 18.2.7Approved
PRR479IDR Optional Removal ThresholdAllow the removal of an IDR meter for settlement under certain conditions when load drops below a minimum threshold.12/04/2003No18.6.1, 18.6.7 [new], 18.6.8 [new]Approved
PRR480Reporting of Switch and Move-In DataThis PRR would require ERCOT to post on a monthly basis the number of residential and commercial customers served by the AREP and by all CRs combined, as well as the levels of switches and move-ins completed during the month by the AREP and CRs for residential and commercial customers.12/04/2003No15.6 [new]Withdrawn
PRR481Liability for QSE default on Obligations to ERCOTThis revision would allocate responsibility for default of a QSE among Resources and Loads. Currently, only Loads bear the risk for default of an a QSE. This provision would allocate liability across both the generation and load sectors of the market in recognition of the fact that both load and generation engage in market behaviors and make decisions and policies that affect the viability of LSEs in the market. This broader sharing of risk of default of a QSE is a feature of the PJM market and will likely be a feature of the MISO market. Both of these markets have recognized the need to ensure that Market Participants have an incentive to behave in a manner and to promote decisions and policies that are in the best interests of the market as a whole.12/22/2003Yes9.4.4Rejected
PRR482Responsibility for ERCOT Administration FeeThis revision would allocate the ERCOT administrative charge equally between Resources and Loads consistent with the requirements of PURA §39.151(e). This allocation is appropriate because both Load and Generation impact ERCOT costs.12/22/2003Yes9.7.1Rejected
PRR483Interruptible LaaR Response to InstructionsThe Load Response to Instructions has always been a requirement from LaaRs, so this just adds it to the list. For reliability reasons, ERCOT feels the Load Resource Response to Instructions should be a Real Time signal telemetered from the QSE and not a calculation based on information provided in the Resource Plan.12/24/2003No6.5.1.1,
PRR484Changes for Implementation of Direct Load Control (DLC)The requested changes will facilitate and specify how DLC programs participate in the BUL market.12/29/2003Yes6.10.2,
PRR485Revision to Unit-Specific Deployment Based on Generic CostThis revision includes RMR Units in the list of exceptions and would avoid the bids for certain types of units exceeding the $1,000/MW bid cap.01/13/2004Yes4.4.20Approved
PRR486Fuel Oil Inventory ServiceThis PRR adds Fuel Oil Inventory Service as an Ancillary Service that can be provided by Generating Resources.01/14/2004No1.3.1.2, 2.1, 4.5.11,,, [new], 5.6.1, 5.6.7, 6.1.13 [new], 6.2.1, 6.3.1, 6.4.2, 6.5.12 [new], 6.6.2, 6.8.6 [new], 6.9.4, [new], [new], 12.4.2, 12.4.4Rejected
PRR487Black Start ResourcesChanges Black Start Ancillary Services language to allow an ERCOT Resource with a firm standby supply contract with an adjacent power pool supplier to bid as an ERCOT Black Start Resource.01/15/2004No6.1.8,
PRR488Weather Responsiveness DeterminationAmend the weather responsiveness determination to reflect the requirement for TDSPs to submit profile code changes, to prevent changing the weather responsiveness based on missing data, to establish a threshold for the amount of missing data and to set up a process to re-test ESI IDs with insufficient data.01/15/2004No11.3.3.1Approved
PRR489Ancillary Service Deployment Performance ConditionsRevises the requirement that ERCOT remove from consideration of average performance of a QSE any interval or group of intervals in which any one of several specific events (e.g., OOME deployments to the QSE) has occurred.01/19/2004No6.10.6Approved
PRR490LaaR Annual Testing DescriptionThis revision changes LaaR seasonal testing to an annual test consisting of a telemetry check and includes a biennial test of the under frequency relay for LaaRs providing Responsive Reserve Service.01/19/2004No6.10.2Approved
PRR491Clarification to PRR 413 RPRS MarketThis PRR separates the RPRS bid price used to resolve Local Congestion from that used to resolve Zonal Congestion and capacity insufficiency. For procurement of local capacity, the solution uses the Resource Category Generic Cost. For procurement of zonal or system capacity, the solution uses the submitted RPRS bids. The Market Solution concept is removed. PRR 466 has extended the current expiration date for the suspension of Market Solution for Local Balancing Energy from December 31, 2003 to February 1, 2005.01/22/2004Yes6.,, 7.4.2Approved
PRR492Plan to Alleviate Chronic Local CongestionThe PRR requires ERCOT and the associated TDSP to identify and implement feasible alternatives to local transmission once certain dollar thresholds are met.01/29/2004Yes7.4.5 [new]Approved
PRR493Induction Generator ExemptionRevise section to clarify the mechanism an induction generator may use to receive an exemption from the generator and the level of the payment to be made.02/12/2004Yes6.5.7.1Approved
PRR494Revise Forecasted Load Profile Post timeERCOT will publish forecasted Load Profiles for the next three business days no later that 5:30 a.m. in addition to there current posting at 10:00 a.m. This PRR also Clarifies that ERCOT will provide historical Load Profile data for up to the previous two years.02/24/2004No18.3.3Withdrawn
PRR495Effect of Short Payments Owed on Estimated Aggregate Liability (EAL)Modify the determination of Estimated Aggregate Liability (EAL) to include the effects of short payment amounts owed to QSEs by ERCOT.03/03/2004Yes16.2.7.3Rejected
PRR496Block Bidding and Deployment of LaaRs providing Responsive Reserve Service and Non-Spinning Reserve ServiceInclude provisions for LaaRs to have the option to bid Responsive Reserve Service and Non-Spinning Reserve Service as a block.03/03/2004No4.4.11,, 6.7.3, 6.7.4Approved
PRR497Unavailable Units and RMR AgreementsRestores the evaluation and notice requirement until alternate Protocol language can be developed. The language included in this PRR is identical to the language in PRR452 approved by the Board in October 2003. The March 31, 2004 expiration date of the PRR452 language was intended to allow time for a new PRR that enhances the process in the PRR452 language. Good progress has been made on a new PRR. The RMR Task Force has almost finalized a draft for PRS consideration. Failure to reinstate the language from PRR452 that expires on March 31 could adversely impact ERCOTs ability to prevent critical generation units from exiting the system.03/04/2004Yes8.1.3.2Approved
PRR498Exclusion of Payment For Black Start Service from Short Payment ObligationRevise Section 9.4.4, Partial Payments, to exclude payments for Black Start Service from the calculation of reduced payments to Invoice Recipients when ERCOT incurs short payments.03/11/2004No9.4.4Rejected
PRR499Eliminate Fuel Shortage NoticeEliminates the requirement for ERCOT to issue an Emergency Notice for fuel shortage.03/15/2004No5.6.3, 5.6.4, 5.6.6Approved
PRR500OOME Down Payments - Verifiable CostsThe OOME Up payment mechanism provides for verifiable costs in excess of normal OOME Up payment. Having this same mechanism in the OOME Down payment structure provides fairness to Market Participants.03/17/2004No6.8.2.3Withdrawn
PRR501A/S Revision to Down Balancing RequirementRevise the Down Balancing Requirement to account for Regulation Down obligations.03/17/2004No4.5.2, 6.5.2Approved
PRR502Aggregation of Combined Cycle Units Providing RRSAllows RRS obligations awarded to combined cycle plants to be aggregated for all units in a block for consideration of compliance.03/17/2004Yes6.10.5.4Approved
PRR503Section 8 Coordination of Resource Outage Due to TSPResource Entities that have arranged for redundant interconnection onto the ERCOT Transmission Grid, during the construction and interconnection phase, shall not be exposed to interruption of both interconnections at the same time, without the TSP arranging for station service and ERCOT taking on the responsibility of serving the Resource Entitys obligations.03/19/2004No8.2.4Withdrawn
PRR504Resource Derating ClarificationProvides an explanation of what constitutes a Resource deration.03/23/2004No8.6.3Approved
PRR505Elimination of OOME Down PaymentsThis revision would eliminate the compensation currently provided for all Resources called upon for OOME Down and/or Local Balancing Energy Down (generic costs or generic bid limits would still be used as a deployment selection criteria, but not for settlement). Because the language changes desired for this PRR are in the same subsections of Section 6 & 7 as changes currently proposed in PRR485, a request currently in-flight, specific Protocol Section edits are not provided at this time (see Protocols Section 21.4.1(5), providing that suggested language for requested revisions is optional). Once PRR485 is considered by TAC and the BOD, the applicable baseline language will be redlined and submitted as comments to this PRR.03/24/2004No6 & 7Withdrawn
PRR506Revision to Short Payment ProcessRevises the timeline for uplift of partial payments.03/29/2004No9.4.4Withdrawn
PRR507RMR Process enhancementsThe proposed revisions to Sections 2,,, and 22(I) streamline and clarify the RMR initiation process timeline and add incentives for Resource Owners to negotiate RMR agreements.03/30/2003No6.5.9.1,,, 22(I)Approved
PRR508Date of Congestion Zone ChangesCurrently, the Protocols require that changes to CSCs and Congestion Zones are effective on January 1st. This PRR proposes to modify the date that changes to CSCs and Congestions Zones will become effective on April 1st, if required. It also proposes a modification to the monthly TCR auction for the months of January through March 2005, the annual auctions for 2005 and 2006.04/01/2004No7.2.1.1,, 7.5.1, 7.5.2,,
PRR509Initiation, Procedure, and Settlement of Disputes through ADRThe changes describe the process for initiating the ADR process, deadlines for prosecuting ADRs, and implementing ADR resolutions in the Settlement process.04/01/2004No20.1; [new] 20.1.1; [new] 20.1.2; 20.2; [new] 20.6; [new] 20.6.1; [new] 20.6.2; [new] 20.7; [new] 20.8; [new] 20.8.1; [new] 20.8.2; [new] 20.8.3Approved
PRR510Remove PIP134 and PIP158 Boxed LanguageThis PRR removes changes due to PIP134 and PIP158, which will not be supported. PIP134 required ERCOT System and Zonal Load forecasts to be distributed through the Message System and PIP158 added information contained in Dispatch Instructions.04/01/2004No5.4.2.2; 6.4.2Approved
PRR511Clarification of PCR EligibilityThe change is a forward-looking clarification of the eligibility for PCRs. The existing language is ambiguous regarding contractual changes between NOIEs and full requirement suppliers. The new wording has been vetted through the TNT Congestion Management Concept group and approved for inclusion in the CRR Whitepaper by the full TNT.In no case will the proposed change create new PCR eligible transactions.04/05/2004No7.5.6Withdrawn
PRR512OOMC and OOME of LaaRsThis PRR clarifies that LaaRs will not be given OOMC and will be limited to a capped amount of verifiable cost recovery.04/16/2004Yes6.1.10, 6.5.10,,,, 6.10.8Approved
PRR513Verification of Operational Model after Recurring Local Congestion EventThis PRR makes it mandatory for ERCOT to verify the transmission model after Local Congestion occurs repeatedly.04/16/2004Yes7.4.1Approved
PRR514Twelve Month Window for Non-IDR ScalingChange the window used in data aggregation for estimating non-IDR meter reads when data for a trade day is not present in ERCOT systems.04/16/2004No11.3.2Approved
PRR515Disclosure of Local CongestionThis PRR provides for the disclosure of information on each unit receiving OOMC/OOME, the intervals and amount of OOMC/OOME provided as well as the transmission studies that lead to OOMC/OOME/RMR deployments. This PRR also provides for disclosure of the contingency and/or overloaded element(s) causing the Local Congestion deployments ASAP.04/29/2004No1.3.1.1,, 6.5.10, 6.7.8Approved
PRR516Curtailment Prioritization for Wind Generators Introduces the concept of using in-service date to determine curtailment priority in situations where only wind generators are needed to resolve local congestionRequires new WPGRs locating in the McCamey area to install Special Protection Schemes to limit their output.04/30/2004No7.4.2, 7.8.8Withdrawn
PRR517Reduce the Number of Annual TCRs Sold to 40% from 60%This PRR wants to reduce the number of annual TCRs being sold from 60% to 40%.05/17/2004No7.5.3.1Approved
PRR518Clarification of Requirements Relating to Retail TransactionsImprove retail market transaction processing by clarifying requirements and timelines.05/18/2004No2, 15Approved
PRR519ERCOT and TDSP Acceptance of Customer Cancellation of Switch RequestRevise current Protocol language to clarify that ERCOT and the TDSP will accept cancellations (814_08s) until five (5) Business Days preceding the effectuating meter read date.05/18/2004Yes15.1.1.4Approved
PRR520Resource Plan Performance MetricsEstablishes Resource Plan performance metrics which are needed for ERCOT to accurately monitor compliance with the Protocols. This revision also defines acronyms for High/Low Operating Limit and High/Low Sustainable Limit.05/24/2004No2.1, 2.2, 4.4.15, 4.10 [new]Approved
PRR521Add Fleet/Zonal OOME instruction to SCE CalculationFor Release 4, ERCOT is planning on partially implementing PRR 422. It is not within the scope of Release 4 to include Fleet/Zonal OOME instructions in market clearing, thus an addition to the SCE equation is necessary to aid a QSE who receives a fleet deployment in following its SCE.05/25/2004No6.10.4.4,
PRR522Collateral Requirements and Credit ChangesChanges are proposed to strengthen ERCOTs ability to enforce collateral and offset appropriately in bankruptcy situations. Changes also will adjust collateral requirements for known or estimated potential liability, Other clean up language is also incorporated.06/01/2004No2.1, 9.4.1, 9.4.2, 9.4.3, 9.4.4, 9.4.5, 16.1, 16.2Approved
PRR523Revisions to Protocol Section 21This PRR modifies the process for revising the Protocols, including: establishing timelines for ERCOT to complete Impact Analyses for all PRRs submitted, standardizing certain provisions, correcting grammatical errors; and formalizing the process for submitting and approving System Change Requests.06/02/2004No21Approved
PRR524Clarification of Timeline for Cost SubmissionMost disputes of the Initial Settlement Statements must be initiated, negotiated and resolved by the issuance of Final Settlement Statements. This PRR will extend the same requirements to the submission of verifiable costs.06/07/2004No6.8.1.11,,,,
PRR525SCE Performance and MonitoringFrequency control has been an on-going issue and concern with Market Participants and ERCOT. PRR 356 (SCE Performance Requirement) and PRR 358 (Negative Impact Schedule Control Error) were submitted, respectively, in August and September of 2002 with the intent of providing incentives to QSEs to more closely follow SCE, thereby resulting in improved frequency control and reliability. These two PRRs have been languishing for nearly two years, with no resolution expected.06/10/2004No6.10.4,, 6.10.5,,,, 6.10.6Approved
PRR526OOMC Verifiable Cost DocumentationSection requires that for recovery of actual cost associated with OOMC instructions specific documentation standards be outlined in the protocols. This new section defines the documentation standards required when ERCOT cancels or delays units planned & approved maintenance outage via an OOMC instruction, with insufficient time to avoid additional costs.06/15/2004No6.8.2.2Approved
PRR527Clarify OOM DefinitionCurrent interpretation is that OOM only includes operator manual entry of unit specific deployment.06/21/2004Yes2.1Approved
PRR528Deadline for Filing ADR ClaimsAmends the deadline for filing an Alternative Dispute Resolution (ADR) claim for denied settlement and billing disputes from thirty (30) to forty-five (45) days.06/29/2004No9.5.4Approved
PRR529Calculating Final REC Purchasing RequirementsRevises Section 14 to reflect REC Program software changes that (1) allow for recalculation of previous years Final REC Requirements for all Competitive Retailers and (2) change the way the Final REC Requirements are calculated.06/30/2004Yes14Approved
PRR530Short Pay Uplift to LSEsRequire the uplift of and short payment to Load on a more timely basis.06/30/2004No9.4.4Rejected
PRR531Load ClarificationMake modifications necessary to clarify the registration and treatment of loads associated with Block Load Transfers. Clarifies BLT load points of delivery are wholesale loads that are not subject to Texas retail choice and that should be treated similar to NOIE loads.07/07/2004No2.1, 5.7, 5.7.2, 16.3Approved
PRR532Implementation of Non-Transmission Alternatives to RMR and OOM ServicesRevisions to allow ERCOT to implement non-transmission alternatives to Reliability Must-Run (RMR) and Out-Of-Merit (OOM) Services to reduce uneconomic uplift.07/20/2004No2.1, 6.1.9, 6.3.1,, 6.7.8, 6.8.3,, 7.4.5Approved
PRR533Definition of Transmission Facility OwnerResponsibility associated with providing model data is not clearly defined in the Protocols. The use of TDSP has not provided clear direction for owners, operators, and ERCOT regarding model data submission. Suggested removal of responsibilities associated with Outage Scheduling provides a streamline appropriate flow of information.07/29/2004No2, 8.3.8,,,,,,,
PRR534Temporary Modifications to the Annual Load Profile ID Assignment and Validation ProcessInserts language in Protocols to allow temporary modifications applicable to the process for annual Load Profile ID Assignment and Validation to be established and approved by the ERCOT Board.08/02/2004Yes18.4.3Approved
PRR535Reactive TestingThis PRR is to clarify this section and to minimize the possibility of misinterpretation of the time period between testing of a generators reactive capability.08/02/2004No6.10.3.5Approved
PRR536Mandatory IDR Threshold ReductionLower the mandatory threshold for IDR mandatory installation to 700 kW (or kVA) and be complete by January 30, 2006.08/17/2004No18.6.1; 18.6.6Approved
PRR537Increased Congestion Management FlexibilityThis PRR provides ERCOT with additional options to use in the management of congestion both in day-ahead and real-time operations.08/23/2004Yes1.3.1.1; 6.5.10Approved
PRR538OOMC Generic Cost for CoalEstablish generic cost for coal plants for use when they receive OOMC Instructions. This same logic would apply to Nuclear & Hydro units.09/01/2004No6.8.2.1Approved
PRR539OOMC Claw Back CorrectionPrevents payments for OOMC service from being negative (a charge)09/01/2004No6.8.2.2Withdrawn
PRR540OOM Cost Recovery Process ClarificationClarify the process ERCOT is to use when making payments for cost recovery request associated with OOMC & OOME instructions. Clarify payments for cost categories approved in an executive session of the Board are to occur on a Resettlement Statement rather than waiting for the True Up Statement.09/01/2004No6.8.2.2;
PRR541Regulation Deployment Ramp RateEliminates implied ramp rate limitation on Regulation Service deployments and clarify that the limitations outlined for performance purposes are not intended to limit ERCOTs ability to fully deploy regulation at any time.09/01/2004No6.7.2;
PRR542Clarifying the LaaR Three Hour LimitClarify that QSEs are allowed to replace LaaR Responsive Reserve with Responsive Reserve from a Generating Resource or other uncommitted LaaR following a deployment of Responsive Reserve Service.09/08/2004No6.10.5.4Approved
PRR543Schedules and Emergency Assistance Over CFE-ERCOT DC TiesIncorporates the use of DC ties with CFE for commercial and emergency services.09/14/2004No4.4.18.1,, 5.6.7, 5.6.8, 5.8,
PRR544Twelve Month Window for Scaling NIDR to IDR ESI IDsModifies the window for Non-Weather Sensitive Proxy Day selection from 6 months to 12 months.09/20/2004No11.3.3.3Approved
PRR545Retail Market ExtractsInclude in Section 11 a new 11.3 that addresses ESI ID-level extract information provided to LSEs09/21/2004No11.3 [new]Approved
PRR546PCR Treatment for Federal Hydropower ResourcesTex-La and Rayburn propose to revise Protocols Section 7.5.6 to provide that long-term power purchase agreements for federal hydropower are eligible for PCR treatment if a long-term allocation was in place prior to September 1, 1999.10/01/2004Yes7.5.6Approved
PRR547Trading HubsThis PRR creates a new section that establishes a definition of a trading hub and specifically identifies the transmission buses that make up each trading hub.10/01/2004No7.9Approved
PRR548Settlement for Mismatched Inter-QSE Energy SchedulesThis PRR proposes to reduce the quantities of energy scheduled by ERCOT into or from the Balancing Energy market during intervals in which Inter-QSE trades do not match. This will reduce ERCOT and Market Participants credit exposure to entities which submit mismatched inter-QSE trades.10/04/2004No4.7.2, 6.9.8Rejected
PRR549Regulation Control During Abnormal Frequency EventsThis PRR revises Sections 6.5.3,, and 6.10.6 to establish an ERCOT frequency deadband of +/- 0.03Hz to aid in regulation control during abnormal frequency events. When ERCOT frequency is outside the deadband, any Qualified Scheduling Entity (QSE) that has a System Control Error (SCE) that is acting to return frequency to a level that is within the deadband will continue to send Dispatch signals to their Resources until the ERCOT frequency returns to a level that is within the deadband. However, in the case when ERCOT frequency is outside the deadband and, any QSE has an SCE error that is acting to move frequency further outside the deadband, that QSE will temporarily suspend sending signals to its Resources until ERCOT frequency returns to a level that is within the deadband.10/08/2004No6.5.3,, 6.10.6         Withdrawn
PRR550Pace of Short Pay Uplift to LSEsThis revision sets a rate at which money due from QSEs representing load is collected.10/13/2004Yes9.4.4Approved
PRR551Security InterestThis PRR adds additional language to the Protocols to greater protect ERCOT Market Participants in the event of a bankruptcy.10/15/2004No16.
PRR552Clarification of Relaxed Balanced SchedulesClarifies section 4.3.2 Schedule Components to ensure that QSEs may schedule Load or generation, even though they may not physically represent Load or generation.10/18/2004No4.3.2Withdrawn
PRR553Scheduling Trading HubsModify ERCOTs scheduling requirements to accommodate transactions involving ERCOT Trading Hubs.10/20/2004No4.2, 4.3.1, 4.4.8, 4.7.2,
PRR554ERCOT Approval of Transmission System OutagesChanges language to allow ERCOT to approve requested outages that may interrupt provision of a required reliability service such as Black Start service or RMR service if an alternate supplier is available.10/29/2004No8.3.1Withdrawn
PRR555Modify Number of Sub-QSEs a Single Entity Can PartitionRevise the Protocols to increase the maximum number of Sub-QSEs an Entity can implement from three to twenty.11/09/2004No16.2.1Approved
PRR556Elimination of ERCOT-wide Uplift of Costs Related to OOMC, OOME, LBES and RMR PaymentsChanges the allocation of OOMC, OOME, LBES and RMR costs from ERCOT-wide LRS to Congestion Zone LRS.11/12/2004No6.9.4.2,,
PRR557Late Fees and Late Fee RecoveryClarifies how late fees are calculated and distributed.11/23/2004No9.4.4, 9.4.6Approved
PRR558Market Notice of LaaR ProrationAllow market participants to be notified when LaaRs awards for Responsive Reserve are prorated by ERCOT.11/23/2004No4.4.13,
PRR559Regulation E10 Update and SCPS1/SCPS2 ReferencesChange E10 to the current value being used. Add references to call measures SCPS1 and SCPS2 as they are commonly referred to.11/23/2004No6.10.5.3Approved
PRR560QSE Qualification Using LaaRsAdd Protocol Language what describes how a QSE can qualify to provide Ancillary Services by using only LaaR Resources11/23/2004No6.10.3,,,
PRR561Remove Nuclear and Hydroelectric Generators from Automatic Deployment SoftwareThis revision directs ERCOT to remove Nuclear and Hydro Electric generation from any software driven automatic solution to resolve congestion. ERCOT retains the right to provide verbal dispatch instructions during an ERCOT emergency when it is deemed that the Hydro or Nuclear unit in question is uniquely qualified to resolve the problem.12/09/2004No4.4.20,
PRR562Permanent Elimination of Market Solution for Local CongestionSection 7.4.3 regarding the prohibition of the use of a Market Solution for Local Congestion payment is scheduled to expire Feb. 1, 2005. This revision would eliminate the date of such expiration.12/16/2004Yes7.4.3Approved
PRR563Standard Form Black Start Agreement - PaymentWith PRR487 (Black Start Resources) approval, Black Start resources, within close proximity of another power pool, which are capable of starting from such power pool via a firm standby power supply contract, are available if the resources and the transmission line(s) connecting the Black Start resource and the external power pool are both in service.12/17/2004NoSection 22 Attachment A Section 9 B. (1)Approved
PRR564Clarification of OOME DefinitionWhile the protocols implicitly indicate that an SPS actuation as an OOME dispatch they do not explicitly include an SPS in its definition in section 6.12/17/2004No6.1.11Approved
PRR565Calculation of Losses for SettlementModify the way distribution losses are calculated to be based on actual rather than forecasted ERCOT load.12/22/2004No13.1.1, 13.1.2, 13.3.1,,
PRR566Implementation of IDR Optional Removal ThresholdAllow the removal of an IDR meter for settlement under certain conditions when load drops below a minimum threshold. The language to allow a customer to request removal of an IDR meter under certain conditions was approved in PRR479. However, the language was boxed until the report required by Section 18.6.2 was modified to indicate whether a customer was eligible to request removal of the IDR meter. Based on discussions between Market Participants, OPUC, the PUCT and ERCOT staff, the PRR 479 language changes were not intended to require changes to the report specified in 18.6.2. This PRR modifies the language in 18.6.2 so that the report does not need to be modified and the language allowing the customer to request removal of the IDR meter can be unboxed. This PRR modifies the reporting requirement in Section 18.6.2 and unboxes the language that allows the customer to request removal of an IDR meter under such circumstances.01/12/2005Yes18.6.2, 18.6.7Approved
PRR567Block Bidding of Ancillary ServicesRevision would allow QSEs to link ancillary service bids across consecutive hours and establish minimum block values that must be selected to clear the bid.01/19/2005No4.4.11Rejected
PRR568Change Initial Settlement from 17 days to 10 daysChange Initial Settlement from 17 days to 10 days.01/19/2005No9.2.3Approved
PRR569Revision to Balancing Energy Payments from a Specific ResourceRevision modifies the payment for Resource-specific deployments to use the fuel index for the current Operating Day.01/21/2005No7.4.3.1,
PRR570Clarification of Settlements of Local Congestion CostsClarify wording to specify that resources deployed by the Balancing Market will be paid the difference between MCPE and the Up/Down Premium Bid.01/21/2005No7.4.3.1,
PRR571Balancing Energy Bid CapRevises the definition of Balancing Energy Bid Cap by clarifying that Balancing Energy Service bids shall be between -$1,000 per MWh and $1,000 per MWh, inclusive, for all Resources.01/21/2005No6.5.2Approved
PRR572Weather Sensitivity ClassificationIncludes language regarding procedures to determine weather sensitivity classifications when an ESI ID is inactive or de-energized.02/09/2005No11.4.3.1Approved
PRR573Mothballed Generation Resource Definition and Time to Service UpdatesThis defines mothballed units and requires the responsible Generation Entity to report to ERCOT, twice annually, the lead time required to reliably return the unit to service. The Generation Entity would be required to document its claim to ERCOTs satisfaction. Time to service updates and supporting documentation would be considered Protected Information.02/09/2005Yes1.3.1.1, 2.1,
PRR574Specify Effective Date for PRRsRevise Section 21.1 to replace the terms ... additions, edits, deletions, revisions or clarifications with the term revise, and make it clear in Section 21.6 that all PRRs are effective only on a prospective basis from the date of implementation.02/10/2005No21.1, 21.6Withdrawn
PRR575Mandatory Down Balancing Ramp RateProposes new subsection (4.5.2(3)) that would clarify that the Mandatory Down Balancing Bid amount should be deployable within one interval.02/11/2005No4.5.2Approved
PRR576Disclosure of OOME, OOMC, and RMR ServiceThis changes Protocol Sections which require that ERCOT post on the MIS Resource-specific information for OOMC, OOME and RMR Services. Also, a definition for Off-line has been added for consistency.02/18/2005No6.5.10, 6.7.8, 2.1Approved
PRR577Availability of Aggregated Load Data by TDSPReceive aggregated TDSP Load data from ERCOT for the purposes of accurately identifying TDSP system peaks required for FERC filings.02/28/2005No11.5.1.1Approved
PRR578Emergency Fuel Supply Resource ServiceThis PRR adds Emergency Fuel Supply Resource Service as an Ancillary Service that can be provided by Generating Resources or Load Resources.03/07/2005No1.3.1.2, 2.1, 4.5.11,,, 5.6.1, 5.6.7, 6.2.1, 6.3.1, 6.4.2, 6.6.2, 6.9.4, 12.4.4Rejected
PRR579Trading Hubs Language CorrectionModifies language in Section for the calculation of the North 345 kV Trading Hub to be consistent with the calculation of the other three regional trading hubs by removing the 90% / 10% language that was originally applied to the North 345 kV Trading Hub only; Replaces the specific minimum scheduling increments by hub specified in Section (2) with a Trading Hub to 2005 Congestion Zone conversion matrix.03/07/2005Yes7.9.2.1,
PRR580Modify RMR EvaluationRemoves localized restriction on transmission constraints for consideration of RMR Units.03/08/2005No6.1.9Rejected
PRR581Update RMR Language Due to PUC Rule 25502. Changes the RMR language to be consistent with PUC Substantive Rule 25.502, Pricing Safeguards in Markets Operated by the Electric Reliability Council of Texas, which became effective Jan. 9, 2005.03/08/2005No6.5.9.1(7) & (8)Approved
PRR582Initiate RMR NegotiationsA new section that allows ERCOT to re-activate RMR negotiations with Generation Resource that has Mothball status and for which ERCOT has previously indicated no need for RMR Service03/08/2005No6.5.9.4 (New)Rejected
PRR583Responsive Reserve DeploymentRevise Section 6.7.3 to distinguish Responsive Reserve deployments for frequency restoration from conditions that require EECP to be declared.03/11/2005No6.7.3Approved
PRR584Extending Black Start Service Bid TimelineChange Black Start Service Bids to a two year process03/25/2005No6.5.8Rejected
PRR585Settlement Obligation Formula for Balancing Energy ServiceAdds the sum function in the Imbalance Ratio Share (IRSiq) settlement equation.03/25/2005No6.9.5.1Approved
PRR586SCE Performance and Regulation Cost Re-allocationReplaces monitoring of QSEs adherence to their base power schedules, Balancing Energy Dispatch Instructions, and Ancillary Service Dispatch Instructions with a single metric that motivates QSEs to stay on schedule and perform their obligations.04/01/2005No6.10.5, 9.6.1Rejected
PRR587Midyear Modification of CSC or CRE definitionsAllow ERCOT staff the authority to modify CSC and CRE definitions midyear04/01/2005Yes7.2.2 (New)Approved
PRR588Testing of Quick Start Units in the Balancing Energy MarketThis PRR establishes a test by which a quick start unit can demonstrate its ability to perform in the BES market.04/01/2005No6.10.3.4Approved
PRR589CSC and Zone DeterminationThis PRR is intended to strengthen ERCOT staffs role in the CSC and zone determination process.04/01/2005Yes7.2Approved
PRR590Update Unit Telemetry RequirementThis revision proposes to add a requirement for QSEs to submit real-time AGC status and Ramp Rate for all online units in their portfolio.04/01/2005No6.5.1.1Approved
PRR591Switchable Unit DeclarationThis PRR defines switchable units and requires the responsible Generation Resource to report to ERCOT whether the unit is committed to another grid outside of ERCOT that would make it unavailable for capacity in the ERCOT market during the summer months. Unit availability reporting is considered Protected Information04/05/2005Yes1.3.1.1., 2.1, 6.3.2Approved
PRR592Modify Shift Factor Calculation to Exclude Fixed Output GeneratorsModifies the calculation of the monthly zonal Shift Factors used to manage and settle zonal congestion.04/05/2005Yes7.1,,,
PRR593Behind the "Fence" Reporting of LoadThe GATF has recommended that a PRR be drafted that would add more resolution to the total actual ERCOT and projected Load. Due to generation netting, there could be a significant amount of Load that never gets reported to ERCOT04/13/2005Yes1.3.1.1,
PRR594Replacement Reserve Service Payment FormulasCorrects the Resource Replacement Reserve Service payment formula to result in negative amounts. Modifies Protocol language to match or refer to the formulas in and,,
PRR595ERCOT Protocol Section 10The revision to Section 10 proposes clarity and consistency with current Market and ERCOT processes.04/19/2005NoEntire Section 10Approved
PRR596Mothballed Generation Resource Estimated Return to Service DatesThis revision requires owners of Mothballed Generation Resources to provide annually to ERCOT projections of the MW of generation capacity of currently Mothballed Generation Resources that will return to service over the next five years.04/19/2005Yes6.5.9.3Approved
PRR597Texas Test Plan TeamTTPT is revising all market place documentation (Section 23 in ERCOT Protocols, Section in Retail Market Guide [RMGRR024], and TTPT Procedures) to keep all information uniform, consistent, and current.04/20/2005No23Approved
PRR598Extension of Credit Against OOM Start UpIf MCPE is greater than Resource Category Generic Minimum Energy Cost, the difference will be credited against Startup Cost. This credit against Startup Cost shall continue until the earlier of: a) the end of the calendar day; or b) the credit has completely covered the startup payment04/22/2005No6.8.2.2Approved
PRR599Notification for Mismatched Inter-QSE Energy SchedulesThis PRR requires that notice be provided to both QSEs involved in a mismatch in the event that ERCOT remedies a mismatch as prescribed in PRR 548. The effective date for this PRR should be upon the implementation of PRR 548.05/02/2005No4.7.2Approved
PRR600Align BES Bids with Resource Plan Capability and Resource ScheduleThis documents the current ERCOT practice of limiting BES bids by the difference in Capacity in the Resource Plan and resource obligations and proposes language that is responsive to Potomac Economics recommendation number 8.05/04/2005No6.5.2Approved
PRR60115 Minute Ramping for BES and Base Power ScheduleThe ramping period for BES deployment and for Base Power Schedule changes is changed from 10 minute to 15 minute05/04/2005No6.5.2,,
PRR602Ancillary Service Obligation for DC Tie ExportsThis revision removes the allocation of Ancillary Service to DC Tie exports and provides for curtailment of DC Tie exports at Step 2 of EECP05/18/2005No4.4.18.2,,, 5.6.7Withdrawn
PRR603Defaulting QSEs Cost Obligation in Second AS MarketThis PRR removes a duplicate sentence in Section of the current Protocols. It also removes Section because such subsection is unnecessary in light of Section and modifies Section (3) to remove other unnecessary language.05/23/2005No6.6.3.2,
PRR604Replacement Reserve Service Bid CapThis revision adds bid limit language for Generation Resources offering to provide Replacement Reserve Service (RPRS).05/25/2005No4.4.11, 4.4.16Approved
PRR605SCE Performance Monitoring for Combined Cycle Resources 052705Revise Sections and subsections to change the SCE performance standard for combined cycle resources from 90% to 80%.05/27/2005No6.10.5.3Withdrawn
PRR606User Security Administrators and Digital CertificatesCreation of new Section 16.11 defining User Security Administrators (USAs) and Digital Certificates; outlining responsibilities of the USAs; and requiring Market Participants to report results of their annual audits of their Digital Certificates to ERCOT.05/27/2005Yes16.11 (New)Approved
PRR607One-Minute Ramp SchedulesAllows QSEs representing Resources to submit one-minute schedules for the ramping period associated with unit start up and shut down. Requires ERCOT to accept these one-minute ramp schedules for operations, compliance, and settlement purposes.05/27/2005No4.4.15, 4.10.4, 4.10.7Rejected
PRR608Improve Ancillary Service Performance ConditionsRevise section 6.10.6 of the protocols to include the impact of different ramp rates on the calculation of a QSEs SCE Performance Metric.06/01/2005No6.10.6Withdrawn
PRR609Smooth 15-minute Resource SchedulesIntroduce explicit language that encourages QSEs to make use of Relaxed Balanced Schedules so that Resource Schedules are within the capability of the generating unit and make reasonable transitions between the 15-minute intervals.06/01/2005No4.3.5Rejected
PRR610Reduction of OOME Down PaymentsThis revision would introduce further Resource Plan analysis by ERCOT between 1600 and 1800 prior to the Adjustment Period. It will require ERCOT to evaluate whether the scheduled capacity from the QSEs Generation Resources may cause transmission security violations during the Operating Day. If the potential for a transmission security violation exists, ERCOT would notify the QSE of the potential issue and the amount of MW in question with the understanding that the QSE, if it receives an OOME DN instruction, would not be paid to back down. This is intended to reduce the Uplift cost caused by a QSE that schedules more output in the Resource Plan than may be possible for the transmission system to absorb without causing a transmission security problem. The PRR does not change the Protocols that compensate generators for OOME Down instructions issued by ERCOT in Real-Time.06/10/2005No4.1.1, 4.4.16 (New),
PRR611Reporting of Operation Reserve Capability Under Severe Gas CurtailmentsAdds a requirement that Resources provide additional data describing their alternative fuel capability during the winter months. Adds information submitted under Section 12.4.7 to the list of items considered Protected Information in Section, 12.4.7 (New)Approved
PRR612Ancillary Service Procurement During the Adjustment PeriodThis revision allows for the update of Ancillary Service bids after Notice of ERCOTs intent to procure Ancillary Services during the Adjustment Period.06/17/2005No4.5.8,
PRR613Replacement Reserve Under Scheduled Capacity DelineationUpdates To he Replacement Reserve Under Schedule Capacity section to reflect current Bill Determinants and their corresponding processes.06/27/2005Yes6.
PRR614Balancing Bids for Replacement CapacityRequests information on Load Management Standard Offer and Direct Load Control program Load reduction capability to allow ERCOT to determine if the programs meet the DLC criteria06/30/2005Yes6.
PRR615Direct Load Control ProgramsRequests information on Load Management Standard Offer and Direct Load Control program Load reduction capability to allow ERCOT to determine if the programs meet the DLC criteria07/07/2005No6.3.2, 18.7.2Withdrawn
PRR616Interim Solution for the Direct Assignment of Replacement Costs for System-wide Capacity InsufficiencyProvides for an interim solution for the procurement and cost assignment for RPRS for the purpose of system insufficiency as already required by the Protocols until such time as EMMS 4.0 is implemented.07/13/2005Yes6.1.6, 6.1.10,,
PRR617IDR Optional Removal ThresholdThis PRR will alleviate conflicting language and provide clarity on the original intent of Sections 18.6.1(2) and 18.6.7 as these sections relate to the process for an optional IDR removal and re-installation. This PRR also makes non-substantive changes to Sections 18.6.1 and, 18.6.7Approved
PRR618Balancing Energy Up from a Specific LAAR ResourceThese proposed revisions provide an equation that describes how a QSE representing a LaaR receives compensation when a LaaR it represents provides Balancing Energy Up, and clarifies that only Generation Resources will provide Balancing Energy Down to resolve Local Congestion.07/28/2005No7.4.3.1,
PRR619Day Ahead Procurement of LaaR for RRSAll bids to provide Responsive Reserve Service (RRS) from Loads Acting as Resources (LaaR) submitted in the Day Ahead Market, with bid prices equal to or less than the applicable Market Clearing Price for Capacity (MCPC), will be awarded proportionally, using existing ERCOT procedures for handling multiple bids which have the same price.07/28/2005No6.6.3.1Rejected
PRR620Notifying QSEs of their DBES PercentagesThis proposed revision would change the requirement for ERCOT to notify QSEs (via the web listener) concerning their mandatory Down Balancing Energy Service (DBES) percentages. ERCOT would only send notifications to QSEs if there is any change in the percentages of the mandatory Down Balancing Energy Service. This proposed revision would require ERCOT to always post the QSEs mandatory Down Balancing Energy Service percentages.08/19/2005No4.4.5Approved
PRR621QSE Qualification Using Renewable ResourcesSpecifies QSEs representing only Uncontrollable Renewable Resources may qualify to provide Balancing Down Energy Service. The proposed language also clarifies that ERCOT may only request DBES in an amount actually deliverable from the Uncontrollable Renewable Resource based upon energy production at the time of the qualification.08/25/2005No6.10.3.4Approved
PRR622Calculation of Marginal Heat Rate for Resources Receiving OOME Up InstructionsDuring the process of drafting language for PRR 540 (OOM Cost Recovery Process Clarification) a sentence was inadvertently left in the Protocols which is not consistent with the intent or scope of other Sections describing how to calculate a Generation Resource Marginal Heat Rate. In particular, under Section (4)(b)(ii), the Protocols state; ERCOT will use the heat rate of the Resource at the deployed level. This is not consistent with the rest of the subparagraph describing Marginal Heat Rates and should be removed.08/25/2005No6.8.2.3Approved
PRR623Resource Plan Use for OOME Instructed DeviationThis PRR would align the Protocols with current EMMS system functionality by specifying that the most current Resource Plan available at the time of Real Time Balancing (RTB) Market Clearing be used for RTB calculations.08/25/2005No6.7.7.2Approved
PRR624Clarification of Market Participant Default LanguageThis PRR is the result of meetings of the WMS group within the TAC Joint Task Force formed to address market concerns resulting from recent market defaults. This PRR proposes changes that strengthen or clarify Protocol language that address default situations. Much of this language is based on language drafted for the TNT Protocols.08/26/2005No16.2.8, 16.2.9, 16.2.10, 16.2.12, 16.2.14,,,,,
PRR625Clarification of Emergency QSE LanguageThis PRR is the result of meetings of the WMS side of the TAC Joint Task Force formed to address market concerns after recent market defaults. This PRR proposes changes that strengthen or clarify Protocol language that address when and how Emergency QSEs may be used.08/26/2005No2.1,, 16.2.13Approved
PRR626Monthly RMR Status ReportAdds a requirement for ERCOT to post on the Market Information System (MIS) a monthly report on the status of Reliability Must-Run (RMR) contracts and exit strategies (e.g., Must-Run Alternative (MRA) contracts) including an explanation of any changes in RMR or MRA information from the previous months posting.08/26/2005No6.5.9.2Withdrawn
PRR627RMR Transmission Issues and RMR Contract ExtensionEstablishes reporting requirements for TDSPs responsible for construction of transmission system upgrades associated with an RMR and/or MRA exit strategy. Also provides ERCOT with additional flexibility to deal with potential delays in the completion of transmission system upgrades associated with an RMR and/or MRA exit strategy. ERCOT will be able to extend an RMR and/or MRA contract for limited time periods as necessary to allow for planned transmission system upgrades to be completed. ERCOT will also be able to require reporting of project status from the responsible TDSP.08/26/2005No6.5.9.4 (new), (new), (new), 22FApproved
PRR628ERCOT Operation Performance - Non-Spinning Reserve Service DeploymentsAdds a requirement for ERCOT to publish on the MIS the percentage of Balancing Energy Service (BES) bids awarded in every interval that includes deployment of Non-Spinning Reserve Service (NSRS). Also adds a requirement for ERCOT to publish a monthly report showing the average percentage of BES bids awarded when NSRS was deployed in the month. Adds a performance metric for ERCOT that reports when deployment of NSRS (in accordance with Section 6.7.4 (1)) leads to excessive replenishment of the BES Up Bid Stack, which is defined to be 90% or less depleted.08/26/2005No6.10.11Approved
PRR629Proper Pricing of Non-Spinning Reserve Service EnergyAdjusts the Market Clearing Price of Energy (MCPE) for the deployment of Non-Spinning Reserve Service (NSRS) to provide correct price signals to the market by using the MCPE of the appropriate zone for the interval before deployment or the interval of deployment (whichever is higher) for pricing of Balancing Energy associated when Non-Spinning Reserve Service is used by ERCOT.08/26/2005No6.8.1.12,
PRR630Private Use NetworksAdds a requirement for private use networks (i.e., those networks that are connected to the ERCOT System that may include both generation and Load behind the meter) to maintain and report appropriate watt/VAR metering at each substation identical to the requirements of Distribution Service Providers (DSPs) and reporting of the addition or deletion of Load points.08/26/2005No2.1, 5.2.1, 5.2.2Approved
PRR631Black Start Bid Procedures and Compensation for TestingThis PRR establishes a process that requires ERCOT to perform the simulation studies (the cost of which will be uplifted to the entire market through the ERCOT Administrative Fee) of Black Start Resources called for in Protocol Section, rather than require the simulation to be done by the prospective Black Start Resource owner before the final Black Start Service awards are made by ERCOT. In addition, this PRR establishes a payment mechanism to reimburse Resource Owners for costs incurred in the qualification and/or testing of Black Start Resources.09/06/2005No6.10.3.6Withdrawn
PRR632Clawback Mechanism for Generating Resources at a Site with an RMR UnitEstablishes a clawback mechanism applicable to RMR Standby Cost to prevent improper subsidization of Generation Resources located at the same physical location as an RMR Unit. Such Resources are called RMR Companion Unit(s). The clawback mechanism reduces the hourly Standby Price paid for RMR Service by the profits earned by operation of any RMR Companion Units located at the same site as the RMR Unit up to the cumulative total hourly Standby Cost incurred. The profits of the RMR Companion Unit(s) are defined as the difference between the MCPE for each interval that the Companion Unit(s) operate and the Resource Category Generic Fuel Cost (RCGFC) for the Companion Unit(s) less the Resource Category Generic Start Cost of the RMR Resource if started during the period in which the RMR Companion Unit(s) operated.09/09/2005No2.1,
PRR633TSP Data Information RequirementsUpdate and clarify high level data requirements required by ERCOT from TSPs for modeling transmission grid modifications. Specifically require an energize date, ratings, the Entities responsible for proposed element ratings, and ERCOT specified data requirements. Also removed requirements for reporting work accomplished procedures, description of method to energize and test facilities, and in service testing.09/20/2005No8.8.2.1,
PRR634ESI IDs Incorrectly Placed Into Inactive StatusProvide the ability for ERCOT to re-instate ESI IDs incorrectly placed into an inactive status09/22/2005No15.4,
PRR635Resource Plan Performance Metrics UpdateExclude units undergoing required testing from having to bid down balancing. Exclude units with physical and/or mechanical issues from having to show an inaccurate LSL and/or HSL. Exclude hours where the QSE updated their Resource Plan after the close of the Adjustment Period and failed to pass the Adjustment Period Zonal Schedule Measure for those hours. Clarify that the Down Bid & Obligation Measure is done by Congestion Zone when possible. Update the Resource Plan Performance Metrics to include improvements being made to the Resource Plan as part of Release 4.09/22/2005No4.5.2, 4.10.4, 4.10.6, 4.10.7Approved
PRR636Texas SET Version 2.1-Customer RegistrationUpdated and Added Sections to comply with Texas SET Version 2.1 changes to transaction and business processing.10/12/2005No15.1.2.1,,, 15.1.6, 15.1.9 (new)Approved
PRR637Texas SET Version 2.1- Retail Point to Point CommunicationsModifications and Additions to support the Texas SET Version 2.1 Implementation.09/23/2005No24.1.1,, 24.2.1, 24.3, 24.3.3, 24.5, 24.5.2Approved
PRR638Change Settlement Invoice Due Date from 16 Calendar Days to Five Business DaysChanges the Settlement Invoice Due Date from sixteen (16) calendar days to five (5) Business Days. NOTE: There is no change to Protocol Sections 9.4.1 (2) and 9.4.3; that is, ERCOT payments occur on the next Business Day following the QSE payment date.10/04/2005No9.3Approved
PRR639Notification of Repairs to EPS Meter Facilities Under Emergency ConditionsThis revision would allow, in emergency situations, the TDSP to repair its EPS metering without first having to notify ERCOT.10/21/2005No10.8.1.2Approved
PRR640Payments for RMR Service and Agreement for Synchronous ServiceThis PRR revises portions of Section 6 and the RMR Agreement to provide consistency between the two. Additionally, in the RMR Agreement, portions specific to synchronous condensers have been removed and a new Agreement (in Attachment J) created for Synchronous Condenser service. Attachment J is based on language in Attachment F.10/21/2005No6.8.3, 22F, 22JApproved
PRR641Clarifying RPRS Scheduling LanguageSection 6.4.2 (5) states that after a RPRS deployment, a QSE needs to adjust their BES bids based on the LSL and HSL of the deployed unit. Section 6.7.5 (2) states that after a RPRS deployment, a QSE needs to adjust their BES bids based on €¦ the full megawatt quantity of capacity accepted by, and purchased by, ERCOT in the Replacement Reserve markeâ€? This PRR would change the language of Section 6.7.5 (2) to match the language of Section 6.4.2 (10/27/2005Yes6.7.5Approved
PRR642Lower Limit to IDR Meters in MRE for True-Up Settlement IDR ThresholdSets a lower limit to the number IDR meters within a Meter Reading Entity (MRE) that would be considered when determining whether the IDR threshold requirement is met or not for true-up settlement.11/10/2005NoCurrent Protocols: 9.2.6 Nodal Protocols: 9.5.8Approved
PRR643Shorten Payment Default TimelinesThis PRR proposes to: 1) Reduce the number of days allowed to cure a breach before it becomes a Default under the LSE, QSE and TCR Agreements from 3 days to 2 days; and 2) Make collateral payments due by 3:00pm on the second day after notification rather than by 5:00 pm on that day.12/14/2005Yes16.2.8, 16.2.9, Sec 8 and 11 of 22B, 22C, and 22H Nodal Protocols: 16.11.5, 16.11.6, Sec 8 and 11 of Standard Form MP AgreementApproved
PRR644Ancillary Service Re-qualificationAllows QSEs to re-qualify as provider(s) of Responsive Reserve Service, Balancing Energy Service, Regulation Service, and Non-Spinning Reserve Service based upon demonstrated historical performance in lieu of repeating the qualification test(s).11/14/2005Yes6.10.3 Nodal Protocols:
PRR645Customer Information RepositoryThis PRR documents the responsibilities of Competitive Retailers to provide Customer information to the third party for maintaining the Customer Information Repository. (An RMGRR will be submitted to document the details of the process in Section 7, Market Processes of the Retail Market Guide (RMG) if this PRR is approved.)11/18/2005No15.1.2.9Withdrawn
PRR646Establish a Floor for Responsive Reserve Service BidsRevise 4.4.11 so that all bids to provide Responsive Reserve Service (RRS), have bid prices equal to or greater than $0.11/29/2005Yes4.4.11Approved
PRR647Gross and Net MW/Mvar Data ReportingAdds a requirement for a QSE representing a Resource to supply both gross and net MW and Mvar data to ERCOT for use in the operations model.12/05/2005No6.5.1.1Approved
PRR648Prevent IDR Removal from Customers Served at Transmission VoltageThis PRR introduces language to clarify that IDRs may not be removed from Premises served at transmission voltage.01/16/2006No18.6.7Approved
PRR649Correct "K" Factor in Compliance SCE FormulaThis PRR revises the œ€? factor in the compliance formula from 0.81 to 1.02/22/2006Yes6.10.5.3Rejected
PRR650Balancing Energy Price Adjustment Due to Non-Spinning Reserve Service Energy DeploymentAdjusts the Market Clearing Price of Energy (MCPE) when the deployment of Non-Spinning Reserve Service (NSRS) occurs to provide correct price signals via a post-deployment adjustment to separate the pricing solutions from the deployment on NSRS. This adjustment will still be subject to MCSM, if the Balancing Energy Service Up bids are depleted and no zonal congestion occurs, as detailed in Protocol Section ERCOT will provide a notice to all market participants that highlights the interval beginning the NSRS deployment and another notice when NSRS deployment is being discontinued. The adjusted MCPE price signal would remove NSRS deployments and manually re-run SPD, sending accurate price signals in an energy-only market design.02/24/2006No6.7.4,,
PRR651RPRS Cost Recovery Process ClarificationClarify the process ERCOT shall use when making payments for cost recovery request associated with Replacement Reserve Service (RPRS) instructions.02/24/2006Yes6.8.1.11Approved
PRR652Customer Information RepositoryThis PRR documents the responsibilities of Competitive Retailers to provide Customer information to ERCOT or a designated third party for maintaining the Customer Information Repository. (An RMGRR will be submitted to document the details of the process in Section 7, Market Processes of the Retail Market Guide (RMG) if this PRR is approved.)03/08/2006No15.1.2.9, (new)Withdrawn
PRR653OOME Ramp Rate AdherenceThis PRR would allow QSEs to request Verbal Dispatch Instructions when being undeployed from OOME instructions that would exceed the QSEs ramp rate.03/09/2006No6.5.10Approved
PRR654Remove Market Solution ReferencesThis revision removes references to the term "Market Solution" within the Protocols.03/14/2006No2.1,,, 6.1.9, 6.1.10, 6.1.11, 6.7.8,, 7.4.2, 7.6Approved
PRR655Approval of Temporary Modification to Annual ValidationAllow approval to grant a temporary modification to the Annual Validation process by the Technical Advisory Committee (TAC).03/14/2006No18.4.3 Load Profile ID AssignmentApproved
PRR656SCE Performance ChargeThis creates an SCE Performance Charge to replace SCE Performance monitoring.03/15/2006No6.8.6, 6.9.9,,, 6.10.6Rejected
PRR657Process for Protocol Revisions During the Transition to a Nodal MarketThis PRR introduces a more streamlined procedure for processing revision requests relating the Nodal Protocols during the period prior to implementation of the Nodal market. This PRR shortens the comment period and limits the Impact Analysis requirements to only those revision requests that may affect a Requirements Document. The new procedure would be outlined in new Section 21.11, Process for Nodal Protocol Revisions During the Transition to a Nodal Market, and this process would only be applicable until the day of full implementation of the Texas Nodal market03/24/2006YesSection 21.1, Introduction, and Section 21.11, Process for Nodal Protocol Revisions during the Transition (New).Approved
PRR658Requirements for Entities Re-entering the ERCOT MarketThis PRR proposes revisions to Section 16.1 and; creates a new Section 16.1.1, to establish requirements for Entities who wish to re-enter the ERCOT Market as a qualified Market Participant.03/31/2006No16.1, 16.1.1Approved
PRR659Reporting of ERCOT Replacement Reserve Service ProcurementsThis PRR requires reporting on the classification and amounts of ERCOT™s procured Replacement Reserve Service (RPRS), as well as a comparison of actual procurements of RPRS for system capacity to a theoretical amount of RPRS procurement for system capacity04/03/2006Yes1.3.1.1, 6.10.11Approved
PRR660Texas SET Transactional Solution for a Mass Transition EventThis PRR introduces a transactional solution for reducing mass transition timelines and documents the process for parties involved in a Mass Transition event.04/06/2006Yes15.1.2.9Approved
PRR661SCE Performance Enforcement CriteriaThis revision creates the criteria for SCE Performance Enforcement.04/07/2006Yes6.10.5.3, (new)Approved
PRR662Modify Ancillary Service Deployment Performance ConditionsClarifies current language exempting the intervals following a Forced Outage from the Schedule Control Error compliance measure and adds additional exemptions to address infeasible portfolio instructions, Responsive Reserve Service ramping, unit testing, and the scheduling of Uncontrollable Renewable Resources.04/10/2006Yes6.10.6Approved
PRR663Payment When a Resource Receives an OOME Down to Zero (0) MW Dispatch InstructionConforms OOME down to zero Dispatch Instruction cost recovery process to that used for OOMC (e.g. verifiable costs).04/18/2006No6.8.2.6Approved
PRR664Revise Non-Spinning Reserve Services Performance Monitoring CriteriaRevise the Non-Spinning Reserve Service (NSRS) Performance Monitoring Criteria.04/21/2006No6.10.5.5, Non-Spinning Reserve Services Performance Monitoring Criteria; 6.10.3, Ancillary Services Qualification Criteria and Portfolio Test MethodsApproved
PRR665Revise Responsive Reserve Service Performance Monitoring CriteriaCorrect the Schedule Control Error (SCE) to reflect Loads acting as Resource (LaaR) obligation when it is deployed. Revise the Responsive Reserve Service (RRS) Performance Monitoring Criteria to accurately reflect compliant performance by Qualified Scheduling Entities (QSEs). Moved language regarding LaaRs and bids from Combined Cycle plants from Section to Section 6.5.4 since this is a more appropriate place for this language. Revised Section 6.10.3 to update Ancillary Service (AS) Re-Qualification language to reflect new criteria.04/21/2006No6.10.4.4, Schedule Control Error;, Responsive Reserve Services Performance Monitoring Criteria; 6.5.4, Responsive Reserve Service; 6.10.3, Ancillary Services Qualification Criteria and Portfolio Test MethodsApproved
PRR666Modification of RPRS Under-Scheduled Capacity Charge CalculationThe PRR revises Section, Replacement Reserve Under Scheduled Capacity, to charge QSE™s for ERCOT-wide RPRS based on their net ERCOT-wide position. A clarification is also included for Section 4.7.2(2) which refers to sections of the Protocols that use the Schedule Mismatch amount05/22/2006Yes4.7.2 (2),
PRR667RPRS Uplift Charge and Under Scheduled Charge CorrectionThis PRR will correct an over collection and inequitable negative uplift charge, aligning RPRS payments with RPRS procurement costs.05/22/2006Yes6., Specific Procurement Process Requirements for Replacement Reserve Service in the Adjustment Period;, Settlement for RPRSRejected
PRR668Distribution Loss Factor CalculationsModify the Settlement Interval Distribution Loss Factor (SILF) to better represent the non-linear relationship between the loss factor and Settlement Interval ERCOT System Load (SIEL).05/24/2006No13.3Approved
PRR669Timing of Calculation of RPRS Under Scheduled ChargesThis PRR revises the timing of schedules that ERCOT uses for determining the quantity of under scheduled energy from 1300 to 1600 in the day ahead period. The PRR also revises the timing of the load forecast that ERCOT uses from 1100 to 1600.05/24/2006Yes4.4.17,
PRR670First Available Switch Date (FASD) for Switch RequestsThis PRR introduces revisions to Section 15, Customer Registration. Specifically this PRR: Adds language to reflect the First Available Switch Date (FASD) for a Switch Request in situations where: · Customer notification is required; · Customer notification has been waived; or · Drop to AREP request Statements were removed that are no longer accurate based upon current business and system processes. Relocated some of the existing language to make the document flow easier to understand for the reader.05/31/2006Yes15, Customer RegistrationApproved
PRR671Remove Sunset Date on Floor for Responsive Reserve Service BidsRevise 4.4.11 to remove sunset date of January 1, 2007.06/15/2006No4.4.11 Ancillary Services Bid SubmittalApproved
PRR672Retail Market Timing Necessary for PUCT Project 29637Revise the transaction timings in Section 15 for retail processes in order to comply with PUCT Project 29637 and Mass Customer Transition Requirements. Create a new defined term in Section 15, œRetail Business Hou€?.06/19/2006Yes15Approved
PRR673Adjust SCE Performance Charge Scale FactorThe Scale Factor value in the SCE Performance Charge calculation is currently fixed at 1. This PRR would modify the Scale Factor monthly based on ERCOT™s CPS_1 score. This PRR also sets maximum and minimum values for the Scale Factor07/14/2006No6.10.12.1 SCE Performance ChargeApproved
PRR674Temporary Alteration of Settlement Equations Related to the RPRS Under Scheduled ChargeThis PRR temporarily alters the settlement equations for the RPRS Under Scheduled charge.07/19/2006Yes6.,
PRR675Multiple Ramp RatesRevises Sections 4.5.2 and 6.5.2 to allow QSEs to submit a ramp rate curve to ERCOT that would be used to calculate an equivalent ramp rate for clearing the balancing energy market.07/21/2006No4.5.2 Receipt of QSE's Balancing Energy Bid Curves; 6.5.2 Balancing Energy ServiceApproved
PRR676RPRS Solution with Nodal RUC-Type Procurement and Cost AllocationThis PRR modifies the current day ahead capacity procurement and cost allocation methods to be consistent with the procurement and cost allocation methods for the Reliability Unit Commitment that is contained in the Nodal Protocols as approved by the PUCT. The PRR also removes the provisions related to the direct assignment of zonal capacity procurements.07/25/2006Yes4.1.1 Day Ahead Scheduling Process; 4.1.2 Adjustment Period Scheduling Process; 4.4.16 ERCOT Receipt of Replacement Reserve Service Bids; 4.4.17 ERCOT Procurement of Replacement Reserve Service As Needed; 4.5.6 ERCOT Notice of Need to Procure Replacement Reserve Service Resources; 4.5.7 Available Bids for RPRS; 6.4.2 Determination of ERCOT Control Area Requirements; 6.5.6 Replacement Reserve Service; Specific Procurement Process Requirements for Replacement Reserve Service in the Adjustment Period; Payments for Ancillary Service Capacity; Zonal or System Wide Replacement Reserve Service Capacity Payment to QSE.; Local Congestion Replacement Reserve Payment to QSE When Market Solution Exists; Capacity and Minimum Energy Payments; Settlement for RPRS Procured for System-wide Capacity Insufficiency; Replacement Reserve Under Scheduled Capacity; Replacement Reserve Uplift Charge; 6.9.7 Settlement Obligations for Premiums for Individual resource Dispatch Payments; OOM Capacity Charge; 7.1 Overview of ERCOT Congestion Management ; Replacement Reserve Service Zonal Congestion Charge; 7.4.2 Resolution of Local CongestionApproved
PRR677Substitute Source For Fuel Index Price (FIP)This PRR establishes that, in the event the periodical noted fails to publish a daily FIP, the ERCOT Board of Directors will direct ERCOT Settlements on the use of an alternative index.07/26/2006No2Approved
PRR678Allocation of RPRS Over-Collection to QSEsThis PRR allocates any over-collection of funds caused by ERCOT deployment of RPRS to QSEs that are scheduling the excess capacity that offset the requirement for RPRS.07/28/2006Yes6.8.1.16 – Settlement of NSRS Over-Collection (New); – Replacement Reserve Uplift ChargeWithdrawn
PRR679Revision to NLRI Formula and Other Credit RequirementsSeveral changes are proposed, with the three primary changes being: (1) Change the formula for Net Load Imbalance Liability and Net Resource Imbalance Liability (NLRI) to better match with Nodal formula “ perform calculation on a more detailed level using entity specific pricing rather than WA_MCPE pricing (2) Require/allow ERCOT to withhold payment from entities that have exceeded their EAL or NLRI. (3) Address request by RMS/Texas Set to add requirement that QSEs (that are LSEs) and are in Payment Default to provide ESID information on their customers08/01/2006No16.2.7.4, 16.2.8, 16.2.9,,,,,,Approved
PRR680Procurement of Capacity for Load Forecast UncertaintyERCOT presently procures an 1800 MW Mulligan and RPRS using the same process. This revision separates out the load forecast uncertainty procurement process from the RPRS procurement. Capacity for Load Forecast Uncertainty is procured from the Ancillary Services markets.08/02/2006Yes5.6.5 AlertRejected
PRR681Discontinuation of Interest Charge for Defaulting Entities at Time of UpliftThis PRR allows ERCOT to cease the calculation of interest (Late Fees) for defaulting entities when the conditions initiating uplift are met. Late Fee calculations will continue for Short paying entities until uplift conditions are met.08/10/2006No9.4.4, 9.4.6Approved
PRR682Emergency Electric Curtailment Plan (EECP) Event RealignmentThese revisions conform the Protocols with revisions to the Operating Guide proposed in OGRR186, Emergency Electric Event Curtailment Plan (EECP) Event Realignment, to set forth the necessary sequence for ERCOT to process EECP related items, thereby allowing ERCOT to be more proactive in communicating system conditions during certain events.08/14/2006Yes5.6.6.1, 5.6.7,
PRR683Reduce Timeline for Notice and Cure and Create a Working Credit Limit“ Reduces time to post collateral from two Bank Business Days to one - Creates a working credit limit which allows an entity to utilize up to 85% of posted collateral + unsecured credit limit (rather than 10008/16/2006No22 Attachments B, C and H; 16.2.8, 16.2.9Rejected
PRR684Mass Transition Process Necessary for PUCT Rule 31416This Protocol Revision Request (PRR) introduces revisions to Section, Mass Transition and adds a new Section, Customer Billing Contact Information to comply with the PUCT rulemaking for Project 31416. (An RMGRR will be submitted to document the details of the process in Section 7, Market Processes of the Retail Market Guide (RMG).08/16/2006No2. 1, Definitions, Mass Transition, Customer Billing Contact Information (New)Approved
PRR685TCRs and PCRs Payment Due DateThis PRR documents the requirements for both Transmission Congestion Rights (TCRs) and Pre-assigned Congestion Rights (PCRs) payment period due date to three (3) Bank Business Days after being invoiced.08/21/2006Yes7., AuctionApproved
PRR686Black Start Testing RequirementsSpecifies the requirements for starting the next start Resource; Specifies which tests are allowed to be run simultaneously.08/23/2006No6.10.3.6Approved
PRR687Replacement Reserve Under-Scheduled Capacity DelineationThis PRR corrects discrepancies in the Replacement Reserve Under-Scheduled Capacity charge equation.08/24/2006Yes6.9.2.1Approved
PRR688ERCOT Nodal Implementation SurchargeThis PRR documents how ERCOT shall calculate the Nodal Implementation Surcharge (NIS) to comply with the Final Order issued in Public Utility Commission of Texas (PUCT) Docket No. 32686, Application of the Electric Reliability Council of Texas for Approval of a Nodal Market Implementation Surcharge and Request for Interim Relief, to fund implementation of the nodal market redesign.08/28/2006Yes9.7.7Approved
PRR689Down Balance Qualification for Renewable ResourcesModifies the Balancing Down Energy Service qualification for QSEs representing only Uncontrollable Renewable Resources to at or below the deployment level requested by ERCOT.08/28/2006No6.10.3.4 Balancing EnergyApproved
PRR690Termination of the Modified Competitive Solution MethodConsistent with the Commission™s Substantive Rules, this proposed revision eliminates the references to the MCSM08/28/2006Yes6.5.2, Balancing Energy Service;, Balancing Energy Clearing PriceApproved
PRR691Nodal Implementation Surcharge Verifiable CostsThis PRR adds nodal implementation surcharges as a verifiable cost for resources called on for reliability purposes. The changes proposed in this PRR are contingent on the passage of PRR688, ERCOT Nodal Implementation Surcharge.09/14/2006No6.8.1.11,,,
PRR692Corrections to Replacement Reserve ServiceRemoves costs related to capacity procured for system security from the costs that are solely assigned to under-scheduled Qualified Scheduling Entities (œQS€?), provides incentives for more accurate resource plans and eliminates the RPRS over-collection by compensating QSEs representing unscheduled resource09/19/2006No2.1, Definitions; 2.2, Acronyms; 4.4.16, ERCOT Receipt of Replacement Reserve Service Bids; 6.4.2, Determination of ERCOT Control Area Requirements; 6.5.6, Replacement Reserve Service;, Local Congestion Replacement Reserve Payment to QSE;, Replacement Reserve Under Scheduled Capacity;, Replacement Reserve Uplift ChargeRejected
PRR693Update Transactions for Texas SET 3.0 Implementation and Timing for Processing Priority/Standard Move- In TransactionsThis PRR: Revises the transaction timings in Section, Move-In Request to Begin Electric Service and Section, Notification to TDSP of Move-In to reflect the language approved by the ERCOT Board with PRR672 for the TX SET 3.0 implementation as it relates to priority move-in transactions and clarified requirements for standard move-ins. Renames the TX SET transactions for 814_11, 814_14 and 814_15 due to new functionality introduced by TX SET with the long term solution for Mass Transition (see RMGRR042). Revises language as it relates to transaction functionality and brings all processes for each transaction current with TX SET version 3.0 implementation. Reformats and corrects terminology throughout Sections 15, 19 and 24.09/22/2006NoSection 15, Customer Registration Section 19, Texas Standard Electric Transaction Section 24, Retail Point to Point CommunicationApproved
PRR694Modification of Certain Board ApprovalsIn keeping with the activities of the TAC Board Action Items Subgroup addressing this issue, TAC resolution and the Board™s discussion, the PRR proposes refinements as set forth in the TAC resolution of June 1, 2006. 09/25/2006No10.14.1, 18.2, 18.2.2, 18.2.9, 21.4.6, 21.4.7, 21.4.8, 21.8.6, 21.8.7, 21.8.8, 21.9Approved
PRR695Unaccounted For Energy (UFE) AnalysisThis PRR eliminates outdated sections pertaining to UFE analysis and provides a more meaningful approach to annual UFE analysis reporting.10/11/2006No11.6, 11.6.1, 11.6.2, 11.6.2, 11.6.3Approved
PRR696MAPE PublicationThis PRR would amend current Protocols to include the measure of forecast error (i.e., ERCOT™s Mean Absolute Percent Error, or MAPE). Current protocols require ERCOT to provide a load forecast and the actual load. This PRR would isolate the forecast for the Day Ahead market at 1600 hours and at midnight. Additionally, the PRR would require ERCOT to post and maintain an up-to-date historical series for the monthly average MAPE data. Lastly, this PRR would require ERCOT to segregate the weather forecast error from the overall load forecast error10/17/2006No4.2, Scheduling-Related Duties of ERCOTWithdrawn
PRR697Posting Requirement ChangesThis PRR incorporates changes resulting from P.U.C. Subst. R. 25.502, Pricing Safeguards in Markets Operated by the Electric Reliability of Texas Power Region and new P.U.C. Subst. R. 25.505, Resource Adequacy in the Electric Reliability of Texas Power Region, adopted under P.U.C. Project No. 31972, Rulemaking Concerning Resource Adequacy and Market Power in the Electric Reliability Council of Texas Power Region.10/20/2006No1.3.1.1, Items Considered Protected Information;, Items Not Considered Protected Information; 1.3.3, Expiration of Confidentiality; 8.7, Analysis of Resource Adequacy (deleted); 12.3.5, Analysis of Resource Adequacy (new); 12.4.2, Ancillary Service -Related Information;, Public ERCOT Posting;, Public Posting of Standard QSE-Specific Market ReportsApproved
PRR698Remove Default QSE ProvisionsThis PRR revises provisions for the Emergency and Virtual Qualified Scheduling Entity (QSE) to allow them to provide for Resource Entities and Load Serving Entities (LSEs) in the event that their QSE defaults. This PRR also removes the Default QSE concept, including all references to a Default QSE.11/07/2006Yes2.1, 16.2.1, 16.2.8,, 16.2.12,,,,,,
PRR699Removal of the Northeast Congestion Zone in Trading Hub Transaction ConversionsThis PRR Synchronizes the ERCOT Protocols to reflect the removal of the Northeast Congestion Zone in the Trading Hub calculations beginning January 1, 2007. As such, reference to the Northeast Congestion Zone in the Protocols is removed, and the calculation for converting transactions at Trading Hubs to existing Congestion Zones is revised. In addition, the calculation is adjusted to account for the fact that a transmission bus that was previously in the West Congestion Zone will be in the North Congestion Zone in 2007 (bus number 6096).11/13/2006Yes7.9.2.6, ERCOT Bus Average 345 kV Trading Hub;, Scheduling of Transactions Using ERCOT Trading HubsApproved
PRR700Creation of Interim Measure for Collecting the ERO/TRE FeeRevise the ERCOT System administration fees to include the FERC-mandated fee for the ERCOT Region™s share of the new Electric Reliability Organization (ERO) and the new Texas Regional Entity (TRE) for the ERCOT Region. The ERO/TRE fee will be $0.0169 per MWh. FERC approved a ERO/TRE budget for the ERCOT Region which results in a fee of $0.021 per MWh; however, a portion ($900, 000) of the ERO/TRE fee will be collected via the PUCT-approved ERCOT System administration fee of $0.4171 per MWh.11/15/2006Yes2.1, 9.7.1Approved
PRR701Enabling of Stranded Capacity During AlertsThis Protocol Revision Request will provide ERCOT with a tool that will enable incremental online capacity upon ERCOT issuing an Alert due to a capacity short supply situation. This Protocol change will also allow QSEs to represent their previously stranded capacity as available and capable of being loaded to their full real-time capability during an Alert due to a capacity short supply situation.11/20/2006Yes5.6.5, 5.6.6,, 5.6.8Approved
PRR702Emergency Interruptible Load ServiceModify the Zonal Protocols to allow for the use of an Emergency Interruptible Load Service (EILS) when an Emergency Electric Curtailment Plan (EECP) is declared and all available Generation and Loads acting as Resources (LaaR) have been deployed.12/19/2006YesSection 2, Definitions and Acronyms; Section 4, Scheduling; Section 5, Dispatch; Section 6, Ancillary Services; Section 9, Settlements; Section 12, Market Information System; and Section 16, RegistrationRejected
PRR703Emergency Interruptible Load Service (EILS)This PRR changes the Protocols Sections noted above and institutes an Emergency Interruptible Load Service (EILS) as a load interruption emergency backstop for use only during Emergency Electric Curtailment Plan (EECP) Step 3. EILS would be a merit order of loads that have voluntarily offered to interrupt at an offer price and would be dispatched to interrupt in the EECP step just prior to the Independent System Operator™s (ISO) dispatch order to Transmission and Distribution Service Provider/Distribution Service Providers (TDSP/DSPs) to shed firm load in order to preserve the syste€™s frequenc12/28/2006YesSection 2, Definitions and Acronyms; Section 4.1.1, Day Ahead Scheduling Process; Section 4.1.3, Month Ahead Scheduling Process (New); Section 4.4.8, Submittal of Day Ahead Schedules and Ancillary Services Schedules; Section 4.11, Month Ahead Scheduling Process (New); Section 5.6.7, EECP Steps; Section 5.6.8, Emergency Compensation; Section, Data Collection; Section 6.1.13, Emergency Interruptible Load Service (EILS) (New); Section 6.2.1, Ancillary Services Solely by ERCOT; Section, Requirement for Operating Period Data for System Reliability and Ancillary Service Provision; Section 6.5.12, Emergency Interruptible Load Service (EILS) (New); Section 6.6.2, Competitive Procurement of Ancillary Service Resources by ERCOT; Section 6.7.9, Deployment and Recall of EILS (New); Section 6.10.2, General Capacity Testing Requirements; Section 6.11, (Emergency Interruptible Load Service Qualification, Testing and Performance Standards (New); Section 12.4.2, Ancillary Service – Related Information; and Section 16.2, Registration of Generation Resources and Loads Acting as a Resource.Rejected
PRR704Emergency Interruptible Load Service (EILS)This PRR changes the Zonal Protocols sections noted above and upon approval institutes an Emergency Interruptible Load Service (EILS) as a load interruption emergency backstop during Emergency Electric Curtialment Plan (EECP) Step 3. EILS would provide ERCOT with a pool of loads that have voluntarily offered to interrupt at an offer price and would be dispatched to interrupt in the EECP step just prior to the Independent System Operator™s (ISO) dispatch order to Transmission and Distribution Service Provider/Distribution Service Providers (TDSP/DSPs) to shed firm load in order to preserve the syste€™s frequency.01/10/2007YesSection 2, Definitions and Acronyms; Section 4.1.3, Month Ahead Scheduling Process (New); Section 4.2, Scheduling-Related Duties of ERCOT Section; 4.8, Temporary Deviations from Scheduling Procedures; Section 4.11, Month Ahead Scheduling Process (New); Section 5.6.7, EECP STEPS; Section, Restoration of Market Operations; Section 6.1.13, Emergency Interruptible Load Service (New); Section 6.2.2, Ancillary Services Provided in Part by ERCOT and in part by Qualified Scheduling Entities; Section 6.3.1, ERCOT Responsibilities; Section 6.4.2 Determination of ERCOT Control Area Requirements; Section 6.5, Technical Requirements for Providers of Ancillary Services; Section, Requirement for Operating Period Data for System Reliability and Ancillary Service Provision; Section, Requirement for Operating Period Data for Emergency Interruptible Load Service Provision (New); Section 6.5.12, Emergency Interruptible Load Service (New); Section 6.6.1, Qualified Scheduling Entity Rights and Obligations to Self-Arrange Ancillary Service Resources; Section 6.6.2, Competitive Procurement of Ancillary Service Resources by ERCOT; Section 6.6.8, ERCOT Month-Ahead Ancillary Service Procurement Process (New); Section 6.8.6, Capacity Payments for Emergency Interruptible Load Service (New); Section, Payments for Emergency Interruptible Load Service Capacity (New); Section, Emergency Interruptible Load Service Payment to QSE (New); Section 6.9.9, Settlement for ERCOT Emergency Interruptible Load Service Procured for the Operating Month (New); Section, Emergency Interruptible Load Service Charge (New); Section 6.10.2, General Capacity Testing Requirements; Section 6.11, Emergency Interruptible Load Service Qualification, Testing and Performance Standards (New); Section 9.2.2, Settlement Statement Data; Section 16, Registration and Qualification of Market Participants; Section 16.5, Registration of Generation Resources, Loads Acting as a Resource, and Emergency Interruptible Load ResourcesRejected
PRR705Emergency Interruptible Load Service (EILS) - Interim OptionThis PRR would modify the ERCOT Protocols to allow for the use of an Emergency Interruptible Load Service (EILS) when an EECP is declared and all available Generation and Loads acting as Resources (LaaRs) have been deployed.01/10/2007YesSection 2, Definitions and Acronyms; Section 5.6.7, EECP STEPS; Section 5.9.3, ERCOT Data Collection; Section 6.1.13, Emergency Interruptible Load Service (New); Section 6.2, Providers of Ancillary Services; Section 6.5, Technical Requirements for Providers of Ancillary Services; Section 6.5.12, Emergency Interruptible Load Service (New); Section 6.7.9, Deployment of Emergency Interruptible Load Service (New); Section 6.8.6, Capacity Payments for Emergency Interruptible Load (New); Section 6.9.4, Settlement Obligation for Black Start Service, RMR Standby Service, and Synchronous Condenser Service; Section 6.10.2, General Capacity Testing Requirements; Section 6.10.13, Emergency Interruptible Load Service Qualification, Testing and Performance Standards (New); Section 16.5, Registration of Generation Resources and Loads acting as Resources; Section 22 -- Attachment K, Standard Form Emergency Interruptible Load Service Agreement (New)Approved
PRR706Provisional Qualification for Ancillary ServicesProvide for a provisional qualification time period for the provision of Ancillary Services (AS) and discontinue the practice of œborrowin€? units for AS qualificatio01/10/2007No6.10.3, Ancillary Services Qualification Criteria and Portfolio Test Methods NormalApproved
PRR707Prioritization and Timing of Transactions Based Upon PRR672 Collaborative Analysis and Retry Process for 814_20s.This PRR proposes the following revisions which are recommended by ERCOT: 1) Add paragraph to outline the prioritization of transactions at ERCOT. 2) Revise transaction timings for Off-Cycle Switches and Off-Cycle Drops to AREP. a) Off-Cycle Switches should be added to Level 4 Transactions to be processed within one (1) Retail Business Day. b) Off-Cycle Drops to AREP should be added to the Level 4 Transactions to be processed within one (1) Retail Business Day. 3) Add language in Section for New ESI ID Creation that explains a retry process for 814_20s.01/18/2007No15, Customer Registration, Switch Registration Notification Request to TDSP, Response to Valid Switch Request, Rejection of Switch Request, Response to Drop to Affiliate Retail Electric Provider Request, Notification to TDSP of Drop to Affiliate Retail Electric Provider, New ESI ID CreationApproved
PRR708Data Provided by ERCOT to TDSPsThe proposed protocol revision requires ERCOT to provide adjusted interval meter data for load and generation to a TDSP involved in system planning and operation activities. Any information provided pursuant to this revised provision will retain its protected status pursuant to Section 1.3, Confidentiality, of the Protocols, and will be subject to all applicable codes of conduct, including the PUCT code of conduct restricting the internal sharing of transmission information by employees of the TDSP.01/29/2007No12.
PRR709Scarcity Pricing MechanismThis PRR revises the ERCOT Protocols to provide for a scarcity pricing mechanism as required by subsection (g) of P.U.C. Subst. R. 25.505, Resource Adequacy in the Electric Reliability Council of Texas Power Region. ERCOT is already performing the calculations and postings required by this rule. This PRR synchronizes the Protocols with this rule.01/31/2007NoSection 4.4.11, Ancillary Services Bid Submittal; Section 4.4.16, ERCOT Receipt of Replacement Reserve Service Bids; Section 6.5.2, Balancing Energy Service; and Sections 6.11, System-Wide Offer Caps (New).Approved
PRR710Validation Tests UpdateThis PRR removes the requirement to post exception reports from the Load Profile Type and Weather Zone validation tests to the ERCOT MIS.01/31/2007No18.4.4.1Approved
PRR711Update of ERCOT Protocols to Comply with NERC Name ChangeThis Protocol Revision Request (PRR) updates ERCOT Protocol References to reflect the recent NERC name change from North American Electric Reliability Council to North American Electric Reliability Corporation.02/12/2007No2.1, 2.2,, 5.1.2, 5.2, 5.6.1, 6.1Approved
PRR712Local Congestion Replacement Reserve Payment MethodologyThis PRR modifies the Local Congestion Replacement Reserve Service (RPRS) payment methodology to be identical to that of the Out-of-Merit Capacity (OOMC) payment methodology, as described in Section 6.8.2 .2, Capacity and Minimum Energy Payments. This PRR also includes a "Max" function in the equation of startup payments in case there is a delay in the implementation of PRR676, RPRS Solution with Nodal RUC-Type Procurement and Cost Allocation.02/19/2007No6., Specific Procurement Process Requirements for Replacement Reserve Service in the Adjustment Period;, Local Congestion Replacement Reserve Payment to QSE;, Capacity and Minimum Energy PaymentsWithdrawn
PRR713Resource Outage NotificationThis PRR clarifies and further details the long-term outage notification submission process for resources.02/21/2007No6.5.9, Reliability Must-Run Service;, Initiation and Approval of RMR Agreements;, Mothballed Generation Resource Time to Service Updates; 8.4, Acceptance of Proposed Planned Outages of Resources other than Reliability Resources; Section 22, Attachment I: Notification of Suspension of Operations; Section 22, Attachment F: Standard Form Reliability Must-Run Agreement; Section 22, Attachment K: Notification of Change of Generation Resource Designation (New)Approved
PRR714Qualification and Periodic Testing of Loads acting as Resources (LaaRs)This revision request tightens the requirements for initial qualification; introduces periodic testing requirements; and provides for more clearly defined conditions that would disqualify a Load acting as Resource (LaaR) for under/non-performance.03/06/2007No6.10.2, General Capacity Testing Requirements; and 6.10.12, Non-Compliance Actions of ERCOTApproved
PRR715Simplifying the Dispute ProcessThis Protocol Revision Request (PRR) removes the concept of œlat€? disputes that can still be worked by ERCOT, and removes the concept of disputing settlement statements. Instead, disputes that are filed with enough time for ERCOT to work them, as defined in the Protocols modified by this revision, will be worked and included in the next settlement statement if grante03/27/2007No6.8.2.6, 9.1.2, 9.2.5, 9.5, 9.5.2, 9.5.3, 9.5.4, (new), (new)Withdrawn
PRR716NOIE Self-Provision of Emergency Interruptible Load ServiceThis PRR proposes the following revisions: · Section 2.1: The addition of a Definition for EILS Self-Provision by NOIEs · Section 6.5.12(3): The addition of steps to allow for NOIE Self-Provision and at the same time inform ERCOT of how much EILS it needs to purchase in order to reach its desired goal.. · Section 6.5.12(7)(e): Stating that EILS Self-Provision does not require a MW price. · Section 6.5.12(7)(i): Requiring NOIEs to inform ERCOT of the Maximum amount of EILS Self-Provision they are willing to provide. · Section 6.5.12(7)(j): Allowing NOIEs the option of bidding into the EILS program in the same manner as other loads. · Section 6.5.12(8): Requiring ERCOT to reduce its EILS Budget by the amount of EILS that is Self-Provided. · Section 6.5.12(13): Stating that EILS Self-Provision does not involve payment by ERCOT to NOIEs. · Section 6.8.6: Adding a calculation and description for summing the total MW of capacity purchased by ERCOT for the purposes of EILS. This number does not include EILS capacity that is secured through self-provision. · Section 6.9.4: Adding EILS to Settlement Obligations. · Section Description and changes to the settlement calculations to accommodate NOIE Self-Provision. Section and Describing the way a NOIE Self-Providing EILS is treated if it fails to perform.04/11/2007Pending2, Definitions and Acronyms; 6.5.12, Emergency Interruptible Load Service; 6.8.6, Capacity Payments for Emergency Interruptible Load;, Settlement Obligation for Emergency Interruptible Load Service; 6.10.13, Emergency Interruptible Load Service Qualification, Testing and Performance Standards;, Performance Criteria for EILS Resources; and, Revocation of Qualification of EILS Resources and/or their QSEsApproved
PRR717EILS Disputes and ResettlementsThis PRR adds a definition for EILS Contract Period to Section 2.1; revises Section 6.5.12 to reflect the addition of the definition; adds new Section 9.5.5 to describe a process for disputing and resettling the EILS Service; and renumbers former Section 9.5.5 to Section Definitions; 6.5.12, Emergency Interruptible Load Service (EILS); 9.5.5, Resettlement of Emergency Interruptible Load Service (NEW); and 9.5.5, Disputes for Operational Decisions or Market Rules (RENUMBERED)Approved
PRR718Authority for Determination of Urgency for a SCRThis PRR replaces "PRS" with the "Assigned TAC Subcommittee" as the proper entity to grant a request for Urgent status for a SCR in Section 21.8.11 and revises the requirements for Urgent status designation to mirror those for a Protocol Revision Requests (PRR).04/16/2007No21.8.11Approved
PRR719Texas Regional Entity/NERC/FERC Penalties or AssessmentsAs an ISO, ERCOT is subject to the risk of monetary and/or non-monetary penalties assessed by the Federal Energy Regulatory Commission (FERC) and/or by North American Electric Reliability Corporation (NERC) or any regional entity to which NERC may delegate enforcement authority, in accordance with FERC Order Nos. 672 and 672-A1 for violations of mandatory Reliability Standards. This Protocol Revision Request (PRR) allows for recovery of the costs of paying or complying with any such penalties.04/16/2007No2.1, 2.2, 9.7.9 (new), (new), (new)Withdrawn
PRR720Texas Regional Entity Fee Methodology RevisionThis Protocol Revision Request (PRR) changes how ERCOT will issue invoices to collect the Texas Regional Entity Fee (TREF).05/01/2007NoSection 2.1, 2.2, 9.7.1, and 9.7.8 (new)Approved
PRR721Provision of Customer Billing Information to TDSPsThis Protocol Revision Request (PRR) revises Section, Customer Billing Contact Information, so that ERCOT is required to provide Customer contact information to the Transmission and /or Distribution Service Providers (TDSPs). This PRR will allow ERCOT to take the Customer Billing Contact Information file provided by the defaulting CR, remove all information except for ESI ID, Customer Name, and Customer Phone Number from the file and then pass that file to the TDSPs.05/10/2007No15. Customer Billing Contact InformationApproved
PRR72248 Hour RestorationThis Protocol Revision Request (PRR) proposes language so that in the unlikely event of an ERCOT System shut down, ERCOT will return 90% of ERCOT peak load to pre-disturbed condition at or near 48 hours if a viable solution is available.05/14/2007No6.5.8, Black Start ServiceRejected
PRR723Conform EECP (formally titled "Emergency Interruptible Load Service Formula Correction")This Protocol Revision Request (PRR) proposes technical corrections to the progression of the Steps during an EECP event in Protocol Section
PRR724Removal of the Drop to AREP ReferencesThis Protocol Revision Request (PRR) removes references to the Drop-to-AREP transaction.05/18/2007No2.2, Acronyms 15, Customer Registration, Switching to Provider of Last Resort (delete) 15.1.2, Drop to Provider of Last Resort or Affiliate Retail Electric Provider (delete), Drop Request by CR (delete), Response from ERCOT to Drop to Affiliate Retail Electric Provider, Notification to Customer of Drop to Affiliate Retail Electric Provider (delete), Notification to TDSP of Drop to Affiliate Retail Electric Provider (delete), Response from TDSP to Registration Notification Request(delete), Response from the TDSP to the Drop to Affiliate Retail Electric Provider Request (delete), Notification of Affiliate Retail Electric Provider of Drop to Affiliate Retail Electric Provider, Completion of Drop Affiliate Retail Electric Provider Request and Effective Drop Date, Mass Transition, Rejection of Drop to Affiliate Retail Electric Provider Request (delete) 15.1.5, Concurrent Processing, Drop Date After or Equal to Switch Date (delete), Drop Date Prior to Switch Date (delete), Move-In Date Prior to or Equal to Drop Date (delete), Move-In Date after Drop Date, Move-Out Date Prior to or Equal to Drop date (delete), Move-Out Date After Drop Date, Multiple Drop to Affiliate Retail Electric Providers (delete) 15.1.7, Cancellation of Registration Transactions, Notice to CSA Competitive Retailer of Drop Due to Move-In, Notice to CSA Competitive Retailer of Drop Due to Move In 19.3.1, Defined Texas SET Transactions.Approved
PRR725Emergency Interruptible Load Service Formula & Standard Form CorrectionThis Protocol Revision Request (PRR) proposes technical corrections to the Protocols relating to Emergency Interruptible Load Service (EILS).05/24/2007No6.10.13.3, Performance Criteria for EILS Resources; 22, Attachment K, Standard Form Emergency Interruptible Load Service (EILS) AgreementApproved
PRR726DC Tie Scheduling ClarificationsThis Protocol Revision Request (PRR) clarifies language related to DC Tie scheduling and eliminates the use of the term œBack to Back Ti€? (BtB Tie) in the Protocols since the definition o“DC eâ€? captures any asynchronous tie. This PRR also modifies Protocol language regarding scheduling to reflect the manner in which ERCOT Operations actually treats DC Tie schedu05/25/2007No2.1, 2.2,,, 5.6.7, 5.6.8, 5.7.3, 5.8,
PRR727Process for Transition to Nodal Market Protocol SectionsThis PRR authorizes an orderly transition from the zonal Protocols to the nodal Protocols. This PRR provides a transparent mechanism to retire zonal Protocol sections and implement nodal Protocol sections. This PRR also requires two notices to Market Participants: the first market notice thirty days prior to the retirement or effective date and the second market notice no less than ten days prior to the retirement or effective date.05/25/2007No21.12Approved
PRR728Proposal to Allow ERCOT Discretion When Processing Renewable Production ValuesThis PRR modifies paragraph (3) of Section to allow ERCOT the discretion to process Renewable Production Potential values when submitted by Qualified Scheduling Entities (QSEs) representing only Uncontrollable Renewable Resources.05/25/2007No6., Uninstructed Resource Charge ProcessApproved
PRR729Conforming Section 16 to New Section 22 Standard Form MP AgreementsOnly one Standard Form Market Participant Agreement can be in place at a given point in time. To accommodate this, the following PRR conforms zonal Section 16 to match the updated Standard Form MP Agreement in the Nodal Protocols reflecting a single Standard Form Market Participant Agreement, as well as language applicable to the Independent Market Monitor (IMM), as required by P.U.C. SUBSt. R. 25.365, relating to the Independent Market Monitor (IMM). Modification of Section 22, adds Standard Form Market Participant Agreement.05/25/2007Yes16.1, 16.2, 16.3, 16.4, 16.5, 16.6, 16.7, 16.9, 16.10, 22L (new)Approved
PRR730Balancing Energy Price Adjustment for Deployment of Replacement Reserve ServiceThis PRR adjusts the Market Clearing Price for Energy (MCPE) when Replacement Reserve Service (RPRS) is deployed. This PRR is intended to be similar to PRR 650, Balancing Energy Price Adjustment Due to Non-Spinning Reserve Service Energy Deployment, which removes non-spin deployments from the bid stack before calculating the MCPE.06/19/2007No6.8.1.12, Payments for Balancing Energy Provided from Ancillary Services During the Operating Period and, Balancing Energy Clearing PriceRejected
PRR731Fuel Oil Index Price (FOIP)This Protocol Revision Request (PRR) adds Fuel Oil Index Price (FOIP) definition in Protocol Section 2 and revises language in Sections, Section and Section to allow the use of FOIP to meet verifiable cost documentation requirements.07/02/2007No2,,,
PRR732Automatic Voltage Regulator (AVR) Status -- Compliance with NERC Reliability StandardsThis PRR adds a requirement for telemetry of Generation Resource AVR status to comply with NERC Reliability Standards.07/09/2007No6.5.7.2Withdrawn
PRR733Remove 168-Hour Generation Testing RequirementThis PRR will remove the 168 hour requirement and the need to utilize the observed actual output in the first 168 hours, if test data is not provided.07/09/2007No6.10.2, General Capacity Testing RequirementsApproved
PRR734Revisions to Congestion Management in McCamey Area ProvisionsThis PRR eliminates the 0600 hour timeframe by which ERCOT must post the Tradeable Generation Right (TGR) limits in Section 7.8.2, deletes the requirements in Section 7.8.7, and revises the spelling of "Tradeable" to "Tradable" in Section 2.2 and Section, Acronyms; 7.8.2, Determination of Generation Limits; 7.8.4, Determination of Tradeable Generation Rights; and 7.8.7, Trading or Other Uses of TGRsApproved
PRR735Incorporating the ERCOT Internal Audit Department and Other ClarificationsThis PRR incorporates the ERCOT Internal Audit Department into the Protocols, clarifies the audits to be performed, and the treatment of audit results. Responsibility for performing the annual operational or "settlements" audit, otherwise commonly known as the Statement on Auditing Standards (SAS) No. 70 ("SAS 70"), Type II report, will continue to be performed by an external independent certified public accounting firm. Upon approval of this PRR, responsibility for performing the other audits referenced in Protocol Section 1.4, Operational Audit, will transition to the Internal Audit Department.08/07/2007No1.4.2,,, 1.4.4, 1.4.5, 1.4.6Approved
PRR736Demand Response RevisionsThis Protocol Revision Request (PRR) revises existing Protocol language to facilitate Demand Response (DR) program(s) implementation.08/21/2007No2, 18Withdrawn
PRR737Direct Assignment of RPRS CostsThis PRR modifies the cost allocation methods for RPRS to be exactly the same as PRR676, RPRS Solution with Nodal RUC-Type Procurement and Cost Allocation, with one exception: the cap on the RPRS and Out-of-Merit Capacity (OOMC) charges is a multiple of one times the megawatts that a Qualified Scheduling Entity (QSE) is short. In PRR676, which was approved by the ERCOT Board of Directors and subsequently overturned by the Public Utility Commission (PUCT), the cap on the OOMC and RPRS charges was two times the megawatts that a QSE is short.09/05/2007Yes6., Specific Procurement Process Requirements for Replacement Reserve Service in the Adjustment Period;, Capacity and Minimum Energy Payments; 6.9.2, Obligations for Capacity Services Obtained in the Adjustment Period;, OOM Capacity ChargeRejected
PRR738Remove Old Versions of Standard Form AgreementsThis revision deletes old versions of Standard Form Market Participant Agreements.09/24/2007NoSection 22 Attachment B, Standard Form Load Serving Entity Agreement (delete) Section 22 Attachment C, Standard Form Qualified Scheduling Entity Agreement (delete) Section 22 Attachment D, Standard Form REC Account Agreement (delete) Section 22 Attachment E, Standard form Resource Entity Agreement (delete) Section 22 Attachment G, Standard Form Transmission and/or Distribution Service Provider Agreement (delete)Approved02/01/2008
PRR739Administrative Price AdjustmentsThis proposal revises that calculation to include administrative price adjustments under certain conditions. By modifying the calculation of MCPE in Section, all other Protocol reference to MCPE should be correct without further modification. Note that acceptance of this revision request negates the need for revisions to Protocols as passed under PRR650.10/03/2007No6.3.1, ERCOT Responsibilities, Payments for Balancing Energy Provided from Ancillary Services During the Operating Period, Balancing Energy Clearing PriceRejected
PRR740Creating Amendment to Standard Form Market Participant AgreementThis adds a new form, Amendment to Standard Form Market Participant Agreement, to the ERCOT Protocols.10/23/2007No22NApproved
PRR741Revision of Digital Certificate ProceduresThis PRR documents, in Section 16.11.3, Market Participant Audits of User Security Administrators and Digital Certificates, the requirement that Market Participants generate their own list of USA and Digital Certificate holders for audit purposes and use an automated process to manage (i.e., enroll, renew, revoke, and audit) their Digital Certificates. This PRR also clarifies the language describing the responsibilities of the Market Participant, its USA and ERCOT.10/24/2007Yes16.11Approved
PRR742Balancing Energy Price Adjustment Due to OOMC, OOME and RRS Deployments During Alert and Emergency Notice ConditionsThis PRR is an alternative to PRR 739. It adjusts the Market Clearing Price of Energy (MCPE) when the deployment of Out of Merit Capacity (OOMC), or Out of Merit Energy (OOME) or Responsive Reserve Service (RRS) occurs during an Alert or Emergency Notice condition. This adjustment is similar to that applied to Non-Spin Reserve Service as described in PRR 650, Balancing Energy Price Adjustment Due to Non-Spinning Reserve Service Energy Deployment, which was approved by the ERCOT Board on August 15, 2007. However, in this PRR, these adjustments are effective only during intervals in which an ERCOT-declared Alert or Emergency Notice condition exists. Although ex-post pricing is not a perfect solution, it does allow the market to establish prices during emergency conditions rather than an administratively-set price.10/25/2007No6.8.1.12 -- Payment for Balancing Energy Provided from Ancillary Services During the Operating PeriodRejected
PRR743TCR Transition to CRRThis Protocol Revision Request (PRR) inserts Section 7.5.10, referring to the Transmission Congestion Rights (TCR) to Congestion Revenue Rights (CRR) Transition Plan. Section 7.5.10 allows the TCR to CRR Transition Plan to modify or supplement certain aspects of TCRs as documented in Section 7.5, Transmission Congestion Rights. The TCR to CRR Transition Plan is approved by TAC10/29/2007No7.5.10, Transition of Transmission Congestion Rights to Congestion Revenue Rights (new)Approved
PRR744Revision to 16.2.8, Monitoring of Creditworthiness by ERCOTThe revision ensures that ERCOT will receive and accept as sufficient from the QSE, financial statements of the QSE or a guarantor if a guarantee is being provided for the purpose of determining the QSE’s creditworthiness.10/31/2007Yes16.2.8Approved
PRR745NERC-TRE Terminology UpdateThis PRR updates the Protocols to reflect changes in NERC terminology and governance and contains other conforming changes.11/05/2007No1.3.6, Exceptions; 2.1, Definitions; 4.4.18, Direct Current Tie Interconnection Day Ahead Scheduling Process; 5, Dispatch; 6.1, Ancillary Services Required by ERCOT; 6.4, Standards and Determination of the Control Area Requirements for Ancillary Services; 6.4.1, Standards for Determining Ancillary Services Quantities; 6.4.2, Determination of ERCOT Control Area Requirements; 6.5.3, Regulation Service (RGS) 6.5.8, Black Start Service; 6.5.11, Zonal Out-of-Merit Energy Service; 6.7.3, Deployment of Responsive Reserve Service;, Resource Category Generic Costs;, Regulation; 6.10.4, Ancillary Service Deployment Performance Measures;, SCE Monitoring Criteria; 6.10.9, Reactive Power Supply from Generation Resources Required to Provide VSS Performance Criteria; 6.10.11, ERCOT Operations Performance;, Settlement Timeline and Dispute Process; and 9.8.2, Direct Current Tie Schedule InformationWithdrawn
PRR746Revisions to EILS Provisions to Conform to Amended P.U.C. Subst. R. 25.507This PRR amends various Protocols related to EILS. The specific amendments are as follows: · Section 2.1 is modified to eliminate the definitions of EILS Business Hours and EILS Non-Business Hours and to redefine the term "Time Period" consistent with the amended Rule. The Rule has eliminated the terms "Prime" and "Non Prime" hours and has provided ERCOT with flexibility to modify EILS Time Periods within a Contract Period. This amendment would permit ERCOT to establish EILS Time Periods by defining the hours in the Request for Proposal specific to a Contract Period. It would also allow ERCOT to restructure the EILS Contract Periods, consistent with the Rule, and would require ERCOT to post the restructured hours on its website at least 90 days prior to the start of the Contract Period. · Section 6.5.12(2) is amended to eliminate a requirement that was specific to the initial EILS bid solicitation in April 2007. · Section 6.5.12(5) is amended to clarify that ERCOT solicits EILS bids and that the bids are submitted by QSEs. · Section 6.5.12(6) is amended to eliminate the requirement that all members of an aggregated EILS Resource must have a peak demand of at least 500 kW. · Section 6.5.12(8) is amended to conform the EILS Cost Cap to the $50 million cost cap established by the Rule. This provision also conforms the Protocols to the Rule by clarifying that the Cost Cap applies to the 12 months from February through January, instead of a "rolling 12-month period." This provision also clarifies that ERCOT may reject any bid that it finds unreasonable or outside the parameters of an acceptable bid. This provision also moves the current Protocol language relating to how the Cost Cap is adjusted for Self-Provided EILS to its own subparagraph (9), and renumbers the existing (9) to (10). · Section 6.5.12(10), which established a 500 MW procurement minimum for the EILS service, is eliminated. · Section 6.5.12(17)(a) is amended to add clarity to the meter data requirements for any EILS Resource that does not have a dedicated ESI ID. This may include Loads within a NOIE area or within a Private Use Network. · Section 6.5.12(17)(b) is amended to clarify that an EILS Resource may return to service only after being released by ERCOT and to correct a typographical error. · Section 6.5.12(20), relating to sunset provisions for EILS, is eliminated. · A new Section 6.5.12(20) is added to prescribe ERCOT’s EILS reporting requirements. · Section 6.8.6 is amended to eliminate all subscript references to the terms "b" (business hours) and "nb" (non-business hours) in the equations used to calculate EILS Capacity Payments and convert them to a single reference term "tp" (time period). This amendment reaffirms that each EILS Time Period will be clearly defined by ERCOT in the Request For Proposal (RFP) specific to the EILS Contract Period. · Section is amended to eliminate all subscript references to "b" (business hours) and "nb" (non-business hours) in the EILS settlement equations and convert them to a single reference of "tp" (time period). This amendment reaffirms that each EILS Time Period will be clearly defined by ERCOT in the RFP specific to the EILS Contract Period. · Section is amended to eliminate all subscript references to "b" (business hours) and "nb" (non-business hours) in the equations used to calculate EILS Resources’ performance criteria and convert them to a single reference of "tp" (time period). This amendment reaffirms that each EILS Time Period will be clearly defined by ERCOT in the RFP specific to the EILS Contract Period. · Section is amended to clarify procedures for ERCOT-administered penalties applied to QSEs and/or EILS Resources that fail to meet their availability or performance obligations and to make the Protocols consistent with the Rule. Specifically, the Rule requires a six-month suspension for failure to perform. This provision clarifies that the suspension may apply to the EILS Resource’s ability to participate and/or its QSE’s ability to offer EILS; clarifies when the six-month suspension period shall commence; and requires that a suspended EILS Resource may be reinstated only after successfully completing a load-shedding test. The provision also eliminates references to "revocation" of participation privileges for an EILS Resource or a QSE, as such is not provided for in the Rule. This amendment also retitles this Section to replace the word "Revocation" with the word "Suspension." · Section 16.5 is amended to clarify that EILS Resources are not required to register as Resource Entities, but rather are required to register via Appendix A of the QSE’s Standard Form EILS supplemental agreement with ERCOT. Appendix B of Section 22K, Supplement to QSE Agreement, is amended to provide flexibility to accommodate differing Time Periods. Appendix B is the "Term Sheet" representing the actual contractual obligation of a QSE and its EILS Resources for a specific Contract Period. Future Time Periods defined in Appendix B may vary by Contract Period, mirroring those set forth in the Registration/Proposal Form that accompanies the RFP and is the form used by the QSE and its EILS Resources to submit Bids or Self-Provision offers.11/07/2007Yes2.1, 6.5.12, 6.8.6,,,, 16.5, 22K-AppBApproved
PRR747IDR Requirement ChangeThis Protocol Revision Request (PRR) removes obsolete language covering the IDR threshold change to 700 KW and refers to the Retail Market Guide for specific installation procedures.12/05/2007No18.6.1, Interval Data Recorder (IDR) Installation and Use in SettlementApproved
PRR748Settlement During EDS 3 LFC TestingThis PRR modifies Out Of Merit Energy (OOME) and Local Balancing Energy (LBE) payment formulas for Early Deliver System (EDS) 3 R6.3 Load Frequency Control (LFC) (Total System) test. It also contains "clean up" items to correct terminology and capitalize terms that ought to be capitalized.12/10/2007Yes6.8.2.3, and
PRR749Rule Changes to the REC Trading ProgramThis Protocol Revision Request (PRR) provides changes in wording, REC account qualification, REC award formulas and the introduction of compliance premiums to comply with . P.U.C. Subst. R. 25.173.12/10/2007Yes2, 14Approved
PRR750Unannounced Generation Capacity TestingThis PRR replaces the seasonal testing requirement with unannounced Generation Resource testing and adds a requirement for Qualified Scheduling Entities (QSEs) to seasonally update their Resources’ High Sustainable Limits (HSLs).12/11/2007Yes6.10.2Approved
PRR751Clarification to Definition of DUNS Number; Section 2, Definitions and AcronymsThis PRR revises and clarifies the definition of "DUNS Number" in Section 2 of the ERCOT Protocols.12/14/2007No2.1Withdrawn
PRR752Update to Posting Requirements of Standard QSE-Specific Market ReportsThis PRR incorporates requirements in P.U.C. Subst. R. 25.505, Resource Adequacy in the Electric Reliability of Texas Power Region, adopted by the Public Utility Commission of Texas (PUCT) in its Order Adopting Amendment to §25.505 as Approved at the August 16, 2007, Open Meeting, in P.U.C. Project No. 33490, Rulemaking Proceeding to Address Pricing Safeguards in Markets Operated by the Electric Reliability Council of Texas. Specifically, this PRR removes language from boxes, revises the disclosure dates from 30 to 60 days after the Operating Day and adds language requiring disclosure of certain information if the Market Clearing Price for Energy (MCPE) or the Market Clearing Price for Capacity (MCPC) exceeds a certain level.12/17/2007No12.
PRR753PRR Appeals ProcessThis Protocol Revision Request (PRR) provides for a more structured process for parties to appeal the decisions pertaining to PRRs made by the Protocol Revision Subcommittee (PRS) and the Technical Advisory Committee (TAC). This proposal also provides timelines for appealing PRS and TAC decisions and makes accommodating provisions for PRRs on an Urgent timeline.02/04/2008No21.4.11, Appeal of DecisionApproved
PRR754Resource Settlement Due To Forced Transmission OutageClarifies Qualified Scheduling Entities (QSEs) scheduling generation Resources will receive Out of Merit Energy (OOME) Down to zero (0) Verbal Dispatch Instructions (VDIs) when a Transmission Facility Forced Outage trips a generation unit offline.02/04/2008No6.5.11, Zonal Out-of-Merit Energy ServiceRejected
PRR755Demand Response ProgramTo revise existing Protocol language to provide a short-term solution for the settlement of DR program(s).02/13/2008No2.1, Definitions, 2.2, Acronyms, and 9.6, Settlement ChargesWithdrawn
PRR756Distributed Renewable Generation ModificationsThese changes allow for Load Profiling and Data Aggregation methodology to better represent the output of distributed renewable generation Resources with a capacity of less than 50 kW.02/29/2008Yes2.1, 2.2, (new), (new), 18, 18.2, 18.2.3 (new), 18.2.9Approved
PRR757Emergency Interruptible Load Service Formula CorrectionThis Protocol Revision Request (PRR) proposes the following changes: Revise the equation in Section 6.8.6(1) to eliminate subscript references to the term "b" (business hours) and replace it with reference term "tp" (time period) and delete a duplicate term in the variable definitions. Revise the equation in subsection to delete the undefined term "EILS Business Hours;" provide a definition for the subscript term "i"; and revise subscript term "n" from upper case to lower case to match its use in the equ03/07/2008No6.8.6, Capacity Payments for Emergency Interruptible Load Service (EILS); and, Settlement Obligation for Emergency Interruptible Load ServiceApproved
PRR758Clarification of Language Related to Generation Netting for ERCOT Polled Settlement MetersThis PRR makes a minor change in wording to make clear intent of Protocol Section, i.e., that metering may net the generation and the Load associated with such generation for the purposes of settlement.03/14/2008Yes10.3.2.3, Generation Netting for ERCOT Polled Settlement MetersApproved
PRR759Changes to Notification to Customer of Service EstablishmentThis Protocol Revision Request (PRR) deletes Section from the ERCOT Protocols and renumbers subsequent subections.03/19/2008No15.1.4.3, Notification to Customer of Service EstablishmentApproved
PRR760Emergency Interruptible Load Service (EILS) Availability Factor ClarificationThis Protocol Revision Request (PRR) clarifies a settlement and compliance provision relating to availability requirements for Emergency Interruptible Load Service (EILS) Resources assigned to the alternate baseline.03/24/2008No6.10.13.3 Performance Criteria for EILS ResourcesApproved
PRR761Inadvertent Energy Account RevisionThis Protocol Revision Request corrects the definition for an Inadvertent Energy Account04/16/2008No2.1, Definitions; and, Inadvertent Energy AccountApproved
PRR762West Zone SCE Performance ConditionsThe PRR revises Section 6.10.6 to exclude from consideration of performance periods where Qualified Scheduling Entities (QSEs) operating controllable units in the West zone are called upon to deploy and recall Balancing Energy in response to high wind production and Congestion in the area.04/21/2008Yes6.10.6, ancillary service deployment performance conditionsApproved
PRR763Use of WGRPP as Planned Operating Level in Day-Ahead Resource Plan for WGRsThis Protocol Revision Request (PRR) allows Qualified Scheduling Entities (QSEs) representing Wind-powered Generation Resources (WGR) to use an ERCOT provided Wind-powered Generation Resource Power Potential (WGRPP) forecast as the planned operating level in the Resource Plan.05/16/2008Yes2.1, Definitions, 2.2, Acronyms and 4.4.15, QSE Resource PlansApproved
PRR764Zonal Congestion and CSCs/CREsThis Protocol Revision Request (PRR) provides that zonal constraints are only those constraints for which a Commercially Significant Constraint (CSC) or Closely Related Elements (CRE) is the base case or post-contingency limiting element.05/29/2008Yes7.3.2, 7.5.2Approved
PRR765Time Of Use RevisionsThis Protocol Revision Request (PRR) revises existing Protocol language to comply with the latest Public Utility Commission of Texas (PUCT) Ruling on approval of Time Of Use Schedules (TOUS).06/10/2008No18, Load ProfilingApproved
PRR766Interim Solution for 15-Minute Settlement of Advanced MetersImplementing this Nodal Protocol Revision Request (NPRR) will support the interim settlement of all provisioned Advanced Meters using actual fifteen minute data, the same way Interval Data Recorder (IDR) meters are settled today, until the long-term solution developed by Project 34610, Implementation Project Relating to Advanced Metering or future rulemakings is implemented.ERCOT and the Public Utility Commission of Texas (PUCT) have developed an Request For Information to investigate the long-term solution to advanced meter settlement and data transport. The PUCT unanimously approved the "Scope of Work" of the long-term study on May 22, 2008. See P.U.C. SUBST. R. 25.130(h), Advanced Metering.06/20/2008Yes9.2.6,,, 10.12.3, 11.2.2, 18.2, 18.6.7, 18.7.2, 19.7 (new)Approved
PRR767Issuance of Alerts for Certain Uses of Balancing EnergyThis Protocol Revision Request (PRR) proposes a revision that allows ERCOT to issue an Alert pursuant to Section 5.6.5, Alert, instead of declaring an Emergency Condition when using zonal Balancing Energy to resolve flow limit violations for base case or post-contingency limiting elements that are not Commercially Significant Constraints (CSCs) or CREs.07/14/2008No7.3.2Rejected
PRR768TSP Energy Storage for Reliability (formerly "TDSP Energy Storage for Reliability")This Protocol Revision Request (PRR) inserts new paragraph (6)(c) in Section which clarifies that energy flows, from Transmission Service Provider (TSP) owned battery storage technology, will be treated similarly as substation equipment and therefore the measurement of such flows are not required for settlement. This new paragraph will be limited to ERCOT Board endorsed TSP reliability projects.07/21/2008Yes10.3.3.1Approved
PRR769EECP Media Appeal ChangeThis Protocol Revision Request (PRR) removes required energy conservation media appeal from EECP Step Two and allows ERCOT management to issue a media appeal for energy conservation at management’s discretion, without requiring ERCOT CEO authorization.07/22/2008No5.6.6.1,, 5.6.7Approved
PRR770Deletion of UFE Analysis Zone LanguageThis Protocol Revision Request (PRR) deletes an outdated section pertaining to Unaccounted for Energy (UFE) analysis.07/24/2008No13.4.2Approved
PRR771Ramp Rate Limitation of 10% per minute of On-Line Installed Capability for Wind-powered Generation ResourcesThis Protocol Revision Request (PRR) proposes a requirement for Wind-powered Generation Resources (WGRs) to limit the ramp rate to 10% per minute of On-line installed capability.07/25/2008No6.5.13(new), 6.6, 6.6.1Approved
PRR772Description of MCPE Cap and Shadow Price Cap MethodologyThis PRR clarifies ERCOT’s authority to take action to ensure that the Market Clearing Price of Energy (MCPE) does not exceed the system-wide offer cap established by the Public Utility Commission of Texas (PUCT) in PUC Subst. R. 25.505, Resource Adequacy in the Electric Reliability Council of Texas Power Region. This PRR also proposes that the methodology to make the price adjustments be described in a separate document and that Market Participants be notified of any changes in the Shadow Price caps. In addition, this PRR proposes to change the section title in Section 6.11.1, Balancing Energy Offer Cap Floor, to Balancing Energy Offer Floor, to avoid confusion. A similar change is proposed for Section, Balancing Energy Offer Cap Floor; 6.11.2, Responsive Reserve Service (RRS) Offer Cap Floor; and 7.1, Overview of ERCOT Congestion ManagementApproved
PRR773Setting the LSL Requirement for WGRsThis Protocol Revision Request (PRR) requires that a Wind-powered Generation Resource (WGR) Low Sustainable Limit (LSL) to be set at 10% of the name plate rating of the WGR.07/28/2008No4.10.4, Resource Low Sustainable Limit as a Percent of High Sustainable Limit MeasureApproved
PRR774Treatment of Financial Information as ConfidentialThis Nodal Protocol Revision Request (NPRR) clarifies that non-public financial information provided to ERCOT is to be treated as Protected Information.08/15/2008No1.3.1.1Approved
PRR775Change the name of Emergency Electric Curtailment Plan (EECP) to Energy Emergency Alert (EEA)This Protocol Revision Request (PRR) changes the name of the Emergency Electric Curtailment Plan (EECP) to Energy Emergency Alert (EEA).08/22/2008No2.1, 2.2,,, 5.6.7,, 5.6.8, 5.7, 5.8, 6.1.13, 6.5.2, 6.5.12, 6.7.3, 6.7.9, 6.10.2,, 6.10.6,
PRR776Automatic MCPE Adjustment During Intervals of Non-Spinning Reserve Service DeploymentThis Protocol Revision Request (PRR) adjusts the Market Clearing Price of Energy (MCPE) when the deployment of NSRS occurs to provide accurate prices in Real Time through an automatic $100/MWh upward adjustment. The $100 MCPE adjustment would replace the current PRR650, Balancing Energy Price Adjustment Due to Non-Spinning Reserve Service Energy Deployment, method of removing NSRS deployments and manually re-running Scheduling, Pricing, and Dispatching (SPD). The $100 adjustment is based on the average MCPE adjustment during NSRS deployments since 01/01/07.08/25/2008Yes6.8.1.12,
PRR777WGR QSE Metric CorrectionThis Protocol Revision Request (PRR) exempts Wind-powered Generation Resource (WGR) Qualified Scheduling Entities (QSEs) from the Resource Plan metric that compares Day Ahead and Adjustment Period Schedules to Resource Plans.09/18/2008No4.10.5, 4.10.6Approved
PRR778Clarification of Authorized RepresentativeThis Protocol Revision Request (PRR) codifies the definition of "Authorized Representative" in Section 2, Definitions and Acronyms, and clarifies the need to designate "Authorized Representatives" for registration for all registered Entities.09/19/2008No2.1,,,,, 16.2.8, 16.2.9,,,,,, 16.3, 16.4, 16.5Approved
PRR779Transparency for PSS and Full Interconnection StudiesUpdates to Section 1 to provide transparency to status of Power System Stabilizer Equipment and interconnection requests.09/19/2008No1.3.1.1, Items Considered Protected Information, Items Not Considered Protected Information 12.2, ERCOT Obligation to Provide Information 12.3, Transmission-Related InformationApproved
PRR780Extending Black Start Service Bid TimelineThis Protocol Revision Request (PRR) changes the Black Start Service bids from a one (1) year period to a two (2) year period.09/23/2008No6.5.8, Black Start Service 22, Attachment A, Standard Form Black Start AgreementApproved
PRR781EILS Self-Provision Formula Correction and ClarificationsThis Protocol Revision Request (PRR) proposes to correct terms contained in the settlement equations related to EILS Self-Provision to make the formulas consistent with the verbal description of EILS Self-Provision settlement and the author’s stated original intent. Specifically, the formula correction applies to the uplifted costs of EILS as defined in paragraph (3) of Section, as follows: · Clarifies that uplifted EILS costs are based on final adjusted EILS obligations after accounting for any self-provided EILS. This is accomplished by establishing and defining a new formula term, EILOF. · Adjusts other related formula terms accordingly. · Adds a missing subscript term definition that appears in numerous places elsewhere in the Protocols. · Adds clarity to certain other equation term definitions.This PRR also makes clarifications in language contained in paragraph (3)(d) of Section 6.5.12 related to Qualified Scheduling Entities’ (QSEs’) EILS Self-Provision options in cases where less than 1,000 MW of EILS has been offered, and adds copies of definitions that are applicable to both equations in this Section.09/23/2008No6.5.12,
PRR782Clean-up and Corrections to Terminology and Transaction Timings in Protocol Section 15, Customer RegistrationThis Protocol Revision Request (PRR) corrects and clarifies the transaction timing descriptions to make them consistent with current processes and Appendix D, Transaction Timing Matrix, in the Retail Market Guide.10/02/2008No2.1, 2.2, 15Approved
PRR783Elimination of the Non-ERCOT LSE FeeEliminate language within protocol Section 9.7.3 which describes the Texas Non-ERCOT LSE fee.10/02/2008Yes9.7.3, Texas Non-ERCOT Load Serving Entity FeeApproved
PRR784Delete Use of Boundary Generation Resources to Resolve CRE CongestionThis Protocol Revision Request (PRR) removes language regarding resolution of Congestion on a Closely Related Element (CRE) by Boundary Generation Resources from Protocol Section 7.3.2, Resolution of Zonal Congestion.10/28/2008No7.3.2Approved
PRR785Timing for Required Black Start Unit Load Carrying Test.This Protocol Revision Request (PRR) changes the required Black Start Unit Load Carrying Test from once every six (6) years to once every five (5) years.11/20/2008No6.10.3.6Approved
PRR786Modifications to EILS SettlementThis Protocol Revision Request (PRR) revises language to: · Clarify that the first settlement of the Emergency Interruptible Load Service (EILS) Contract Period shall utilize a Qualified Scheduling Entity (QSE) Load Ratio Share (LRS) which is based upon the Final Load for each Operating Day in the EILS Contract Period; · Introduce a resettlement of EILS Contract Period settlement utilizing a QSE LRS which is based upon the True-Up Load for each Operating Day in the EILS Contract Period; · Remove conflicting language about EILS disputes; · Clarify the timing by which EILS settlement disputes must be submitted; and · Move all language related to the timing of the EILS settlement process to Section 9.5.5, Resettlement of Emergency Interruptible Load Service.11/21/2008No6.8.6 Capacity Payments for Emergency Interruptible Load Service (EILS), Settlement Obligation for Emergency Interruptible Load Service, 9.5.5, Resettlement of Emergency Interruptible Load ServiceApproved
PRR787Add Non-Compliance Language to QSE Performance Standards (formerly "Add Violation Language to QSE Performance Standards")This Protocol Revision Request (PRR) adds language to Section which clearly defines if and when a violation of the Protocols occurs for failure to comply with performance standards. The proposed language adds clarity to Section that is found in other Protocol Sections associated with Qualified Scheduling Entity (QSE) performance metrics.12/03/2008No6.10.5.3, 6.10.6, 6.10.12,,,, (new)Approved
PRR788Ramp Rate Limits for Existing WGRsThis PRR proposes a requirement that certain existing WGRs limit the unit ramp rate to ten percent (10%) per minute of their nameplate capacity ratings as registered with ERCOT.12/09/2008Yes6.5.13Approved
PRR789Removal of Grey Box Language Related to Lagged Dynamics Load Profiling Due to Unfunded ProjectsThis Protocol Revision Request (PRR) removes grey box language related to the use of lagged dynamic samples for new profiles.12/09/2008No18.2.1, Guidelines for Development of Load Profiles 18.2.2, Load Profiles for Non-Interval Metered Loads 18.2.6, Daily Profile Creation ProcessApproved
PRR790Load Profile ID Annual Validation Change RequestThis Protocol Revision Request (PRR) allows for changes in the Annual Validation process timeline due to extreme events.12/09/2008No18.4.2, Load Profile Id assignmentApproved
PRR791Shortage Pricing MechanismThis PRR creates "Virtual QSEs" that can establish pricing during periods of energy shortage.12/10/2008Yes6.5.2.2Withdrawn
PRR792Revised Renewable Portfolio Standards Allocation Process, Pursuant to P.U.C. Subst. R. 25.173This PRR modifies the Protocols to comply with PURA § 39.904(m-1) and P.U.C. Subst. R 25.173.12/15/2008Yes1.3.1.1, 14.2, 14.5.2, 14.5.3 (new), and 14.9.5Approved
PRR793WGR QSE Scheduling MetricThis Protocol Revision Request (PRR) provides specific details for WGR-only QSEs such that the scheduling metric will apply to more Operating Hours.12/24/2008Yes4.10.6, 5.5.1, 7.3.2Approved
PRR794Meteorological Data Required from QSEs Representing Wind-powered Generation ResourcesThis Protocol Revision Request (PRR) will require a Wind-powered Generation Resource (WGR) Entity to provide Real Time meteorological information to ERCOT through its selected Qualified Scheduling Entity (QSE). It will also require ERCOT to establish procedures specifying the accuracy requirements of WGR meteorological information telemetry.12/24/2008Yes6.5.1.1Approved
PRR79590-Day Transmission Outage Scheduling TimelineThis Protocol Revision Request (PRR): 1) Adds a new Outage response timeline that will place a requirement on ERCOT to coordinate Outages submitted with more than ninety (90) days notice at least seventy-five (75) days prior to the start of the proposed Outage; and 2) Provides clarification of three (3) to eight (8) day timeline to eliminate an overlap in requirements.01/05/2009Yes8.3.3Approved
PRR796Resource Plan Performance Metrics RevisionWith this Protocol Revision Request (PRR), ERCOT shall determine the performance of providers of Qualified Scheduling Entities (QSEs) Schedule Control Error (SCE) performance under normal operating conditions. ERCOT shall remove from consideration of average performance of a QSE any period during which an abnormal or unusual event(s) has occurred and which does not have a passing score.01/07/2009No4.10.2.1 (new)Approved
PRR797Removal of Reference to ERCOT Business ProcessesThis Protocol Revision Request (PRR) revises the term "Generation Resource Asset Registration Form" in Section, LSL Requirements for WGRs, to a generic phrase "as registered with ERCOT".01/12/2009No4.10.4.1, LSL Requirement for WGRsApproved
PRR798Update Trading Hub ConversionThis Protocol Revision Request (PRR) synchronizes the ERCOT Protocols to reflect the 2009 Commercially Significant Constraint definitions, approved by the ERCOT Board on October 21, 2008, as it affects the Trading Hub calculations for 2009 (several transmission buses moved between Congestion Zones). As such, the calculation for converting transactions at Trading Hubs to existing Congestion Zones is revised.01/12/2009Yes7.9.2.6,
PRR799ERCOT CEO Approval of NPRRs and SCRs Prior to Posting on MISThis Protocol Revision Request (PRR) mandates ERCOT CEO approval before NPRRs may be posted to the Market Information System (MIS). This PRR also mandates ERCOT CEO approval for System Change Requests (SCRs) that impact system functionality for the Nodal market. This PRR also allows an appeal mechanism for the submitter of the NPRR or SCR if the ERCOT CEO’s decision is to reject the NPRR or SCR.01/19/2009Yes21.8.1,
PRR800QSE Day Ahead MetricThis Protocol Revision Request (PRR) re-defines the Day Ahead metric for both Wind-powered Generation Resource (WGR) Qualified Scheduling Entities (QSEs) and non-WGR QSEs to ensure that both categories of QSEs schedule enough capacity in the Day Ahead market to meet their planned energy schedules plus Ancillary Service (AS) Obligations. This PRR removes the WGR QSEs exemption established in PRR 777, WGR QSE Metric Correction.01/20/2009Yes4.10.5Approved
PRR801Manual TCR AdjustmentsThis Protocol Revision Request (PRR) revises Section, Annual and Monthly Auction Summary, to provide a description of the process used by ERCOT to achieve revenue neutrality in the monthly TCR auction.02/09/2009No7.5.3.1Approved
PRR802TCR Transition to CRR Refund RevisionThis Protocol Revision Request (PRR) revises Section 7.5.10 methodology, providing flexibility in the event monthly Transmission Congestion Rights (TCR) are awarded and require refund for the subsequent month after Nodal Go-Live.02/19/2009No7.5.10, Transition of Transmission Congestion Rights to Congestion Revenue RightsApproved
PRR803Revised Implementation Approach for PRR 601This PRR changes the ramping period for BES deployment for Base Power Schedule Calculation and Balancing Energy Power Schedule from ten (10) minutes to fourteen (14) minutes.02/20/2009Yes6.5.2, Balancing Energy Service, Uninstructed Charge Methodology and Equation, Base Power Schedule Calculation, Balancing Energy Power ScheduleApproved
PRR804Revisions to Section 21 Appeal ProcessThis Protocol Revision Request (PRR) revises Section 21, Process for Protocol Revision, to provide that if a motion to approve a revision request fails, the revision request shall be deemed rejected by the body considering it and subject to appeal, unless at the same meeting that body later votes to recommend approval, remand, or refer the revision request.02/20/2009Yes21.4.3, 21.4.4, 21.4.6, 21.4.7, 21.4.9, 21.4.10,,, 21.8.3, 21.8.4, 21.8.7, 21.8.8, 21.8.9, 21.8.10, 21.8.12,,,,,,,,,,
PRR805Adding POLR Customer Class and AMS Meter Flag to the Database Query Function on the MISThis Protocol Revision Request (PRR) will add Provider of Last Resort (POLR) Customer class and the Advanced Metering System (AMS) meter flag to the database query function on the Market Information System (MIS).03/06/2009No15.2Approved
PRR806Re-Registration of Market Participant due to Mass Transition of ESI IDsThis Protocol Revision Request (PRR) requires re-registration as a Market Participant (MP) if they transfer Electric Service Identifiers (ESI IDs) from one Competitive Retailer (CR) to another using the Mass Transition process.03/06/2009No15.1.3 and 16.1.1Approved
PRR807Clarify Definition of Messaging SystemThis Protocol Revision Request (PRR) revises the definition of "Messaging System" to include a process that makes Real Time messages available to "bidding QSEs" without Resources.03/26/2009No2.1Approved
PRR808Clean-up and Alignment of RECs Trading Program Language with PUCT RulesThis Protocol Revision Request (PRR) cleans up and aligns the language in Section 14, State of Texas Renewable Energy Credit Trading Program, with P.U.C. Subst. R. 25.173, Goal for Renewable Energy. This PRR also updates references to the Renewable Energy Credit (REC) Trading Program throughout the Protocols.03/26/2009No14Approved
PRR809OOMC Startup Costs Clarification & ModificationThis Protocol Revision Request (PRR) modifies Section, Capacity and Minimum Energy Payments, to explicitly state the criteria currently used to determine eligibility for Out of Merit Capacity (OOMC) startup costs, as well as clawback of startup costs. This PRR also incorporates ‘max zero’ logic into the settlement formula that calculates the price for the startup costs (PSui).03/27/2009Yes6.8.2.2, Capacity and Minimum Energy PaymentsApproved
PRR810Remove McCamey Congestion ManagementThis Protocol Revision Request (PRR) removes the unique congestion management procedures for the McCamey Area.04/01/2009No2.2, 7.8Approved
PRR811Real Time Production PotentialThis Protocol Revision Request (PRR) establishes a requirement for Wind Generation Resources (WGRs) to telemeter a Real Time signal indicating the Real Time Production Potential which will be a function of wind and turbine availability at the time.04/17/2009No2.1, 2.2,
PRR812Wind Generator Forecast Scheduling (formerly "Wind Generator Forecast for Scheduling Metric")This Protocol Revision Request (PRR) specifies the process for Wind-powered Generation Resources (WGRs) to update Resource Plans and schedules every hour using the ERCOT provided most likely Short-Term Wind Power Forecast (STWPF) as the standard for accuracy. [Note - It is expected that AWS Truewind will be providing a forecast adjusted for turbine availability as a result of other pending Protocol changes.]04/24/2009No2.1, 2.2, 4.5.1, 4.5.10, 4.5.12 (new)Approved
PRR813FIP Definition RevisionThis Protocol Revision Request (PRR) revises the definition of Fuel Index Price (FIP) to correctly account for the timing difference between ERCOT’s application of the FIP in its systems (midnight to midnight) and the timing of natural gas prices reflected by the index (i.e., 10 AM to 9 AM). The fuel price index published in Gas Daily, in the Daily Price Survey, under the heading "East-Houston-Katy, Houston Ship Channel" for any particular day reflects natural gas prices available to users from hour ending 10 AM of the particular day to hour ending 9 AM of the next day (i.e., the normal "gas day"). This PRR also adds a new definition for the term "Gas Day."This PRR also proposes non-substantive administrative changes, such as correcting acronym and defined term usage and section references. These are shown below with the author "ERCOT Market Rules."05/29/2009No2.1,,
PRR814NOx Emissions Allowance Index Price (NOxEAIP)This Protocol Revision Request (PRR) establishes a definition for NOx Emissions Allowance Index Price (NOxEAIP) that relies on a published cost index for NOx emissions allowances. The PRR provides Qualified Scheduling Entities (QSEs) with an option to either provide detailed documentation of the actual cost of NOx emissions allowances as part of the verifiable cost process or to rely on the NOxEAIP. Specifically, this PRR allows QSEs to recover the cost of emissions allowances when providing Replacement Reserve, Out of Merit Capacity (OOMC) or Out of Merit Energy (OOME) Service as directed by ERCOT if the costs of those emissions allowances are less than one hundred ten percent (110%) of the NOxEAIP. This is the same concept that is applied to the documentation requirements of natural gas prices and fuel oil prices for verifiable cost purposes. This PRR also adds language to clarify how QSEs can recover any emissions-related costs for both startup and operations when providing Replacement Reserve, OOMC or OOME Service. This PRR also proposes non-substantive administrative changes, such as correcting acronym and defined term usage and section references. These are shown below with the author "ERCOT Market Rules."06/01/2009Yes2.1,,,
PRR815CSC Process ClarificationThis Protocol Revision Request (PRR) clarifies the process used to determine Commercially Significant Constraints (CSCs). This PRR also proposes non-substantive administrative changes, such as correcting acronym and defined term usage and section references. These are shown below with the author "ERCOT Market Rules."06/10/2009Yes7.2, 7.2.1, 7.2.2, 7.2.3Approved
PRR816CRE Determination CriteriaThis Protocol Revision Request (PRR) establishes a set of four criteria for determining if a candidate contingency/limiting element pair qualify as a Closely Related Element (CRE).06/22/2009Yes7.2.3, (new), (new), (new), (new), (new), (new)Approved
PRR817Cease Late Payment Charges for Defaulted EntitiesThis Protocol Revision Request (PRR) modifies language to: 1) Enable ERCOT to cease charging late fees to defaulting Entities prior to the initiation of the Uplift process, provided that ERCOT has determined that the recovery of late fees from the defaulting Entity is unlikely; and 2) Clarify how much security may be held back to be used to pay minor Final, True Up and other Invoices as they come due to reduce the administrative burden to the ERCOT market of processing short payments.06/25/2009No9.4.4, Partial PaymentsApproved
PRR818OOMC for Quick Start UnitsThis Protocol Revision Request (PRR) provides that a Quick Start Unit that is not synchronously interconnected to the ERCOT System that receives an Out of Merit Energy (OOME) Dispatch Instruction or Local Balancing Energy Instruction will be settled as providing Out of Merit Capacity (OOMC) Service.06/26/2009Yes6.5.2,,
PRR819Changes to Support Revisions to the PUCT POLR and Expedited Switch RulesThis Protocol Revision Request (PRR) provides that ERCOT shall identify, for 60 days, Electric Service Identifiers (ESI IDs) acquired in a Mass Transition to a Provider of Last Resort (POLR) so that Customers that switch from the POLR are not charged for an out-of-cycle meter read. This PRR also implements changes necessary to expedite the customer switching process. This PRR also proposes non-substantive administrative changes, such as correcting acronym and defined term usage and section references. These are shown below with the author "ERCOT Market Rules."06/29/2009Yes2.1, 15, 15.1.1,,,,,,,,,,,, 15.1.3,,,,, 15.1.8, 15.1.10Approved
PRR820Definition for Transmission and/or Distribution Service ProviderThe PRR modifies the definition for Transmission and/ or Distribution Service Provider (TDSP) to include Entities that were selected to own and operate Transmission Facilities listed in the PUCT Order for Docket 35665, Commission Staff’s Petition for the Selection of Entities Responsible for Transmission Improvements Necessary to Deliver Renewable Energy from Competitive Renewable Energy Zones.07/10/2009Yes2.1, DefinitionsApproved
PRR821Update of Section 21, Process for Protocol RevisionThis Protocol Revision Request (PRR) updates Section 21 to more effectively align with the current stakeholder process. Changes were made to bring consistency between the PRR, System Change Control (SCR), and Nodal Protocol Revision Request (NPRR) processes, where applicable; remove arbitrary or conflicting timelines; clarify commenting process; expand on a revision request being deemed rejected to include email voting for the Technical Advisory Committee (TAC); and include administrative changes and clean up.07/13/2009No21Approved
PRR822Removing Access to Restricted Computer Systems, Control Systems and FacilitiesThis PRR defines the requirement for all Market Participants to have processes in place for removing access to restricted computer systems, control systems, and Facilities upon termination. This PRR also defines the reporting requirement for incidents where improper access by terminated employees, contractors, consultants and affiliates has occurred.07/14/2009Yes16.12, Improper Access to Restricted Computer Systems, Control Systems and Facilities (new)Approved
PRR823Clarifying Language for Resource 12-Month Rolling Planned Outage Schedule Format and Reporting RequirementThis Protocol Revision Request (PRR) clarifies language regarding the requirement for Resource Entities to input a 12-month rolling schedule for Outages in the Outage Scheduler application.07/14/2009No8.1.3.2Approved
PRR824Primary Frequency Response from WGRsThis Protocol Revision Request (PRR) adds a requirement for wind generator control systems to be programmed to respond to frequency deviations by controlling WGR real power output in a way that is similar to governor response for conventional generators.07/21/2009No2.1,, (new)Approved
PRR825Distributed Energy Resource Participation in Responsive Reserve Service MarketsThis Protocol Revision Request (PRR) allows Distributed Energy Resources (DERs) to participate in Responsive Reserve Service (RRS) markets subject to the restrictions provided in the Protocols and Operating Guides. The sponsor of this PRR anticipates that changes to the Operating Guides would also need to be made to define the set points for the under-frequency relays. The sponsor proposes setting these values at 59.7 to parallel the action of under-frequency relay breakers in Loads acting as a Resource (LaaR).07/24/2009No2.1, 2.2,, 6.5.4, 6.7.3, 6.10.1, 6.10.2,, 6.10.12Rejected
PRR826Clarification of Resource Definitions and Resource Registration of Self-Serve Generators for Reliability PurposesThis Protocol Revision Request (PRR) adds language to acknowledge the existence of Generation Resources that have no or minimal injection onto the ERCOT System that qualify either as distributed generation or are registered with the Public Utility Commission of Texas (PUCT) according to P.U.C. Subst. R. 25.109, Registration of Power Generation Companies and Self-Generators, as a self-generator but yet are required to participate with ERCOT for reliability purposes.07/24/2009No2.1, 2.2, 5.3,, 5.4.3,,, 8.1.1, 8.1.2,, 8.2.1, 8.2.3, 8.2.4, 8.2.5, 8.4.1, 8.4.3, 8.4.7, 8.8.2, 16.5, 16.5.1, 16.5.2,
PRR827Find Transaction and Find ESI ID Functions on the MISThis Protocol Revision Request (PRR) updates the Protocols to reflect current options that Market Participants have to obtain information from ERCOT in order to determine or to verify the Electric Service Identifier (ESI ID) for a Service Delivery Point (SDP).08/20/2009No15.2, 15.2.1 (new), 15.2.2 (new), 15.2.3, (new)Approved
PRR828Remove QSE SCE Performance Exemption for QSEs with only Uncontrollable Renewable Resources On-lineStakeholders participating in the special task force on steady state performance metrics for Resources in response to the Public Utility Commission of Texas (PUCT) Staff’s draft Protocol Revision Request (PRR) 586, SCE Performance and Regulation Cost Re-allocation, purposely and temporarily exempted Wind-powered Generation Resource (WGR)-only Qualified Scheduling Entities (QSEs) from the metric they developed in order to focus on the task of building a meaningful metric for all other Resource technologies. This PRR would eliminate that exemption and place WGR-only QSEs on an even playing field with other technologies based on their impact to the system’s reliability and Ancillary Services procured and in recognition of the maturity of the technology to date as evidenced in select white papers promoting WGR provision of Ancillary Services.09/01/2009Yes6.10.6Rejected
PRR829Total Transmission Capacity CorrectionThis Protocol Revision Request (PRR) replaces the acronym Total Transfer Capability (TTC) with Total Transmission Capacity (TTC), defined in Section 2.2.09/03/2009Yes2.2, 4.4.2, 12.1Approved
PRR830Reactive Power Capability RequirementThis PRR clarifies the Reactive Power capability requirement for all Generation Resources, including existing WGRs who are not able to meet the 0.95 lead/lag requirement with the Generation Resource’s Unit Reactive Limit (URL). WGRs that commenced operation on or after February 17, 2004, and have a signed Standard Generation Interconnection Agreement (SGIA) on or before November 1, 2009 may met the Reactive Power requirements through a combination of the WGR’s URL and/or automatically switchable static VAR capable devices and/or dynamic VAR capable devices.09/08/2009Yes2.1, 2.2, 6.5.7,, 6.7.6Approved
PRR831Annual Transmission Congestion Rights (TCR) Auction AmountThis PRR revises the amount of TCRs sold in the annual TCR auction from 40% to 30%.09/09/2009Yes7.5.3.1, Annual and Monthly Auction SummaryApproved
PRR832Deletion of Schedule Control Error (SCE) Posting RequirementThis Protocol Revision Request (PRR) removes the language that requires ERCOT to post the Schedule Control Error (SCE) report seven days after the Operating Day to the Market Information System (MIS).09/15/2009No12., Public Posting of Entity-Specific Market ReportsApproved
PRR833Primary Frequency Response Requirement from Existing WGRsThis Protocol Revision Request (PRR) places a Primary Frequency Response requirement on WGRs that were not covered by PRR824, Primary Frequency Response from WGRs.09/22/2009No5.9.1.3 (new)Approved
PRR834ERCOT Load Forecast AccuracyThis Protocol Revision Request (PRR) proposes revisions that are intended to monitor and establish performance standards for ERCOT’s Load forecasting of the ERCOT Region and ERCOT Congestion Zones.This PRR also proposes non-substantive administrative changes, such as correcting acronym and defined term usage and section references. These are shown below with the author "ERCOT Market Rules."09/24/2009Yes2.2, (new), (new), (new), 6.4.2Withdrawn
PRR835Reactive Capability RequirementThis PRR clarifies the Reactive Power capability requirement for WGRs by specifying +/- 0.95 power factor criteria as the minimum requirement, and the Generation Resources Unit Reactive Limit (URL) criteria as the maximum requirement contingent upon a System Impact Study by the TSP.09/30/2009Yes2.1, 2.2, 6.5.7,, (new), 6.7.6Rejected
PRR836Revised Minimum Ramp Rate for Balancing Energy Service Down to Comport with PRR803This Protocol Revision Request (PRR) changes the divisor for the minimum ramp rate required for a Balancing Energy Service Down bid from 40 to 56 to reflect the change resulting from the implementation of PRR803, Revised Implementation Approach for PRR 601, as it relates to the number of minutes of Balancing Energy Service ramping over a one-hour time period.10/14/2009Yes4.5.2Approved
PRR837Load Used in RMR StudiesThis Protocol Revision Request (PRR) would provide guidance to ERCOT to use the peak Load forecast posted pursuant to P.U.C. Subst. R. 25.505, Resource Adequacy in the Electric Reliability Council of Texas Power Region, for the next 12 months for the Reliability Must-Run (RMR) study, except with respect to the Load in the RMR local area. This aligns the Load forecast period with the RMR contract period and ensures that the Load forecast used for the analysis is one with a reasonable probability of occurrence.This PRR also proposes non-substantive administrative changes, such as correcting acronym and defined term usage and section references.10/16/2009No6.5.9.1Approved
PRR838Fast Response Distributed Energy Resource (DER)This Protocol Revision Request (PRR) allows for participation of Distributed Energy Resources (DERs) in Responsive Reserve Service (RRS) on an equivalent basis with synchronous condenser fast-response hydro.10/22/2009No2.1, 2.2, 6.5.4Withdrawn
PRR839Revised Resource Category Generic Fuel CostsThis Protocol Revision Request (PRR) revises the Resource Category Generic Fuel Cost (RCGFC) for Direct Current (DC) Tie with non-ERCOT Control Area and Block Load Transfer (BLT) Resources to synchronize with the Nodal Protocols and to allow cost recovery for supplying this service.10/23/2009Yes6.8.2.1,
PRR840Update Trading Hub Conversion for 2010 Congestion ZonesThis PRR synchronizes the ERCOT Protocols to reflect the 2010 Commercially Significant Constraint (CSC) definitions, approved by the ERCOT Board on September 15, 2009, as ot affects the Trading Hubs to existing Congestion Zones is revised. A similar PRR for 2009, PRR798, was approved by the ERCOT Board on February 17, 2009.11/12/2009Yes7.9.2.6, ERCOT Bus Average 345 kV Trading Hub, Scheduling of Transactions Using ERCOT HubsApproved
PRR841Revise Total ERCOT Wind Power Forecast (TEWPF)This Protocol Revision Request (PRR) revises the probability of exceedance percentage applicable to the Total ERCOT Wind Power Forecast (TEWPF) from 80% to 50% to better reflect the total ERCOT Wind-powered Generation Resource (WGR) production that has been historically experienced.11/30/2009No2.1, 2.2, 4.4.15, 4.5.12Approved
PRR842Addition of Generic Startup Cost and Minimum Energy Cost for DieselThis Protocol Revision Request (PRR) adds generic costs for the Diesel Resource Category, which also includes other gas-fired Resources (including reciprocating engines). This PRR makes the minimum energy costs for diesel consistent with what is currently in the Nodal Protocols.12/10/2009Yes6.8.2.1Approved
PRR843Add Regional Planning Section to ProtocolsThis Protocol Revision Request (PRR) adds the entirety of the RPG Charter and Procedures (Charter) document, as it was recently approved by the ERCOT Board, to the Protocols.12/18/2009No1.1, 2.1, 2.2, 3.5, 25 (new)Withdrawn
PRR844Transmission and/or Distribution Service Provider (TDSP) Definition RevisionThis Protocol Revision Request (PRR) revises the definition of Transmission and/or Service Provider (TDSP) to include Entities that have been selected to own and operate Transmission Facilities and have a code of conduct approved by the Public Utility Commission of Texas (PUCT).01/15/2010No2.1, DefinitionsApproved
PRR845Definition for IDR Meters and Optional Removal of IDR Meters at a Premise Where an Advanced Meter Can be ProvisionedThis Protocol Revision Request (PRR) clarifies the meaning of Interval Data Recorder (IDR) Meter and provides for optional removal of IDR Meters under certain conditions for Premises where an Advanced Meter can be provisioned by the Transmission and/or Distribution Service Provider (TDSP). In addition, due to the proposed definition of an IDR Meter, Protocol references to IDR and/or IDR Meter are being updated to ensure appropriate understanding and usage of the terms. This PRR also proposes non-substantive administrative changes, such as correcting acronym and defined term usage and section references.01/22/2010No2.1, 2.2, 6.5.12,,,, 9.2.5, 9.2.6,, 9.9, 10.2.2,,, 10.9, 10.9.1,10.9.2, 10.9.3, 18.6, 18.6.1, 18.6.2, 18.6.3, 18.6.4, 18.6.5, 18.6.6, 18.6.7Approved
PRR846Deadlines for Initiating Alternative Dispute ResolutionThis PRR amends Section 20.3 to establish deadlines for the ADR procedures.02/15/2010No20.3, Informal Dispute Resolution 20.4, Mediation Procedures 20.5.2, Selection of ArbitratorsApproved
PRR847Additional Exemptions for Uninstructed Resource ChargeThis Protocol Revision Request (PPR) proposes two changes to Section as follows: 1. When a Qualified Scheduling Entity (QSE) is given a verbal Dispatch Instruction from ERCOT, the QSE shall be exempt from any Uninstructed Resource Charge during the specified verbal Dispatch Instruction time period, provided that the QSE followed instructions to within the Schedule Control Error (SCE) of the verbal Dispatch Instruction given. 2. After a Load acting as a Resource (LaaR) has been activated, the QSE representing the LaaR can request a three hour extension for scheduling under paragraph (11) of Section 6.10.6, Ancillary Service Deployment Performance Conditions, and during this rescheduling time, a Private Use Network shall not incur Uninstructed Resource Charges for three hours as the Load returns back to service. Additional non-substantive administrative revisions, such as correcting defined term usage, number usage and paragraph references, are shown with the author "ERCOT Market Rules."03/15/2010No6.
PRR848Allow ERCOT Option to Cancel RPRS Capacity CommitmentsThis Protocol Revision Request (PRR) adds statements allowing ERCOT the option of canceling capacity commitments made by Replacement Reserve Service (RPRS). Additional non-substantive administrative revisions, such as correcting acronym usage, are shown with the author "ERCOT Market Rules."03/22/2010No6.5.6Rejected
PRR849Suspension of Annual CSC DeterminationThis Protocol Revision Request (PRR) revises Section 7.2.1 to suspend Commercially Significant Constraint (CSC) analyses for 2010.05/11/2010Yes7.2, 7.2.1, 7.2.2, 7.2.3, 7.5Approved
PRR850Weather Responsiveness Determination for Interval Data RecordersThis Protocol Revision Request (PRR) limits the applicability of the weather responsiveness test to Interval Data Recorder (IDR) Meters.08/11/2010Yes11.4.3,