1. May 20, 20031 TAC Report to the ERCOT Board May 20, 2003

2. 2Summary PRRs 362, 371, 381, 385, 386, 392, 393, 394, 396, 398, 400, 401, 403, 407PRRs 362, 371, 381, 385, 386, 392, 393, 394, 396, 398, 400, 401, 403, 407 –381: Update QSE Designation –396: RMR –371: Payment for Min Energy with OOMC –401: Partial Payments and Credit –407: Remove RBS Sunset 2004 CSCs and zones2004 CSCs and zones Load Profiling Guides RevisionLoad Profiling Guides Revision

3. May 20, 20033 PRR 362 – Load Profiling ID Type Correction Allows the load profiling ID type to be corrected in the billing system, not the registration systemAllows the load profiling ID type to be corrected in the billing system, not the registration system No computer system impactNo computer system impact Effective June 1, 2003Effective June 1, 2003 Related revisions to the Load Profiling Guides approved by TACRelated revisions to the Load Profiling Guides approved by TAC(LPGRR2003-002)

4. May 20, 20034 PRR 385 – DLC Implementation Provides clarification to an existing Direct Load Control projectProvides clarification to an existing Direct Load Control project Impacts ERCOT computer systemImpacts ERCOT computer system Effective upon system implementationEffective upon system implementation

5. May 20, 20035 PRR 386 – Scheduling Information Clarifies Protocol by indicating that not all services are deployed zonally and that zonally deployed services are reported zonallyClarifies Protocol by indicating that not all services are deployed zonally and that zonally deployed services are reported zonally No impact on ERCOT computer systemsNo impact on ERCOT computer systems Effective June 1, 2003Effective June 1, 2003

6. May 20, 20036 PRR 392 – Posting of Balancing Energy Forecast Removes the requirement for ERCOT (PIP 138) to post the balancing energy forecastRemoves the requirement for ERCOT (PIP 138) to post the balancing energy forecast No impact on ERCOT computer systemsNo impact on ERCOT computer systems Effective June 1, 2003Effective June 1, 2003

7. May 20, 20037 PRR 393 – Balancing Energy Bid Expiration Time Eliminates the expiration time for balancing energy bids (PIP 147)Eliminates the expiration time for balancing energy bids (PIP 147) No impact on ERCOT computer systemsNo impact on ERCOT computer systems Effective June 1, 2003Effective June 1, 2003

8. May 20, 20038 PRR 394 – Balancing Energy Ramps as Instructed Deviations Conforms Protocols to ERCOT system treatment of BE ramps outside of the target intervalConforms Protocols to ERCOT system treatment of BE ramps outside of the target interval No impact on ERCOT computer systemsNo impact on ERCOT computer systems Effective June 1, 2003Effective June 1, 2003

9. May 20, 20039 PRR 398 – CCGT Settlement Clarifies implementation of previously approved PRR 369 (combined cycle unit aggregation for settlement), so that system development is not delayedClarifies implementation of previously approved PRR 369 (combined cycle unit aggregation for settlement), so that system development is not delayed Impact on ERCOT computer systems integrated with PRR 369 ongoing workImpact on ERCOT computer systems integrated with PRR 369 ongoing work Priority same as PRR 369Priority same as PRR 369 Effective upon system implementationEffective upon system implementation

10. May 20, 200310 PRR 400 – Provisional Approval of LaaRs Allows LaaRs to obtain provisional approval once telemetry & calibration testing are complete – LaaR must still complete actual interruption testAllows LaaRs to obtain provisional approval once telemetry & calibration testing are complete – LaaR must still complete actual interruption test Impact on ERCOT computer system integrated with PIP 112Impact on ERCOT computer system integrated with PIP 112 Priority same as PIP 112Priority same as PIP 112 Effective upon system implementationEffective upon system implementation

11. May 20, 200311 PRR 403 – URC Update for New Smoothing Algorithm Clarifies changes to URC calculation related to HVDC tie schedules due to PRR 350.Clarifies changes to URC calculation related to HVDC tie schedules due to PRR 350. Impacts ERCOT computer systemsImpacts ERCOT computer systems Effective upon system implementationEffective upon system implementation

12. May 20, 200312 Now it gets interesting…..

13. May 20, 200313 PRR 381 – Update QSE Designation (The Sequel) Board remanded to TAC to reconsider initially approved 30-day period from QSE notice to time when scheduling for the Resource or LSE endsBoard remanded to TAC to reconsider initially approved 30-day period from QSE notice to time when scheduling for the Resource or LSE ends TAC recommendation: shorten timeframe to 7 days from 30 daysTAC recommendation: shorten timeframe to 7 days from 30 days

14. May 20, 200314 PRR 381 – Update QSE Designation (The Sequel) Current Default QSE contract does not recognize a transfer of a resource or an LSE without the QSE being in default; also does not address the situation where an LSE fails to choose a new QSECurrent Default QSE contract does not recognize a transfer of a resource or an LSE without the QSE being in default; also does not address the situation where an LSE fails to choose a new QSE Effective June 1, 2003Effective June 1, 2003 TAC approved PRS recommendation by a vote of 23-6TAC approved PRS recommendation by a vote of 23-6

15. May 20, 200315 PRR 396 – Reliability Must- Run Units Incorporates the TAC-approved decision points from April Applicants must attest the unit is uneconomic to remain in serviceApplicants must attest the unit is uneconomic to remain in service Allow rejected applicants to continue market operations;Allow rejected applicants to continue market operations; ERCOT staff to develop options for RMR ‘exit strategy’ within 90 days of contract execution; andERCOT staff to develop options for RMR ‘exit strategy’ within 90 days of contract execution; and Provide for multi-year contractsProvide for multi-year contracts

16. May 20, 200316 PRR 396 – Reliability Must- Run Units Accept both seasonal and annual RMR concepts and reflect in pricingAccept both seasonal and annual RMR concepts and reflect in pricing Adopt “cost plus” methodology for both and reflect differences in risk (8%/2% of eligible costs)Adopt “cost plus” methodology for both and reflect differences in risk (8%/2% of eligible costs) Proposed effective date June 1, 2003Proposed effective date June 1, 2003

17. May 20, 200317 PRR 396 – Reliability Must- Run Units Section 6.8.3 (4) Eligible costs... are defined to be costs that would be incurred by the RMR Unit owner to provide the RMR Service, excluding fuel costs, above the costs the RMR Unit would have incurred anyway had it been mothballed or shutdown. Examples of eligible costs include: labor, materials, supplies and services necessary to operate the RMR Unit.

18. May 20, 200318 PRR 396 – Reliability Must- Run Units Eligible costs: Section 6.8.3 (4) continued Examples of costs not included as eligible costs are: depreciation expense, return on equity, debt and interest costs, administrative and general expenses, allocated general plant, property taxes and other taxes not attributable to operating the RMR Unit, security costs for the facility, and labor costs associated with other, non-RMR Generation Resources at the same facility and any other costs the Generation Entity would have incurred even if the RMR Unit had been mothballed or shutdown.

19. May 20, 200319 PRR 396 – Reliability Must- Run Units TAC approved PRS recommendation by a vote of 20-8-1TAC approved PRS recommendation by a vote of 20-8-1 Outstanding Issues:Outstanding Issues: –How RMRs are selected-- by the Resource or by ERCOT upon notice of retirement / mothballing –The event where a resource owner retires the unit when ERCOT needs the unit

20. May 20, 200320 PRR 371 – OOMC Update Review of OOMC completed in order to ensure proper economic tradeoff between RMR and OOM and to integrate PRR 371’s recognition of minimum energyReview of OOMC completed in order to ensure proper economic tradeoff between RMR and OOM and to integrate PRR 371’s recognition of minimum energy Likely to impact ERCOT computer systemsLikely to impact ERCOT computer systems Effective with system implementationEffective with system implementation

21. May 20, 200321 PRR 371 – OOMC: Addition of Resource Categories Combined Cycle, the largest CT in the train is:Combined Cycle, the largest CT in the train is: –Less than 90 MW –Greater than or equal to 90 MW Gas SteamGas Steam –Supercritical boiler –Reheat boiler –Non-reheat or boiler without air pre-heater Simple CycleSimple Cycle –Less than 90 MW –Greater than or equal to 90 MW

22. May 20, 200322 PRR 371 – OOMC: Modified/Added/Deleted Costs for Some Resource Categories Resource Category Generic Fuel CostsResource Category Generic Fuel Costs –Upward instructions –Downward instructions Resource Category Generic Startup CostsResource Category Generic Startup Costs Resource Category Generic Minimum Energy Costs – AddedResource Category Generic Minimum Energy Costs – Added Resource Category Generic Operational Costs – DeletedResource Category Generic Operational Costs – Deleted

23. May 20, 200323 PRR 371 – OOMC: Generic OOMC Payment OOMC Payment = Price for unit start, provided the unit is not connected to the gridPrice for unit start, provided the unit is not connected to the gridPLUS Price for operating a unit to provide “minimum” energy at its Low Sustainable LimitPrice for operating a unit to provide “minimum” energy at its Low Sustainable Limit

24. May 20, 200324 PRR 371 – OOMC: Generic OOMC Startup Cost Each Resource Category has an associated startup cost which includes:Each Resource Category has an associated startup cost which includes: –Startup fuel cost –Ramp fuel cost (for Combined Cycle only) –These fuel costs are based on the Resource’s capacity MPCE paid/charged for ramp energy is credited back to ERCOT via the formula for startup costMPCE paid/charged for ramp energy is credited back to ERCOT via the formula for startup cost

25. May 20, 200325 PRR 371 – OOMC: Generic OOMC Min Energy Cost Each Resource Category has an associated minimum energy cost per MWEach Resource Category has an associated minimum energy cost per MW During the instruction interval:During the instruction interval: –The cost per MW is multiplied by the lesser of the Low Sustainable Limit or the metered output of the Resource –MPCE paid/charged for the minimum energy is credited back to ERCOT via the formula for minimum energy cost

26. May 20, 200326 PRR 371 – OOMC: OOMC Instruction –Clarification ERCOT will not issue an OOME Up instruction for energy associated with the Low Sustainable LimitERCOT will not issue an OOME Up instruction for energy associated with the Low Sustainable Limit The QSE may maintain a Balanced Schedule during instruction interval by:The QSE may maintain a Balanced Schedule during instruction interval by: –Scheduling energy –Being selected to provide Balancing Energy Service

27. May 20, 200327 PRR 371 – OOMC: OOMC Instruction –Clarification Issue: How to treat the energy provided when complying with an OOMC instruction.Issue: How to treat the energy provided when complying with an OOMC instruction. –QSE cannot maintain a Balanced Schedule if OOMC instruction received less than 1.5 to 2 hours in advance of instruction interval TAC revision: Actions to comply with OOMC instruction won’t result in URC.TAC revision: Actions to comply with OOMC instruction won’t result in URC. ERCOT staff proposal: Actions to comply with OOMC instruction given within 30 minutes of operating period won’t result in URC.ERCOT staff proposal: Actions to comply with OOMC instruction given within 30 minutes of operating period won’t result in URC.

28. May 20, 200328 PRR 371 – OOMC: Disclosure TAC recommendation to postTAC recommendation to post –Units receiving an OOMC instruction –Intervals for which a unit received an OOMC instruction –Intervals and energy requested from each unit receiving an OOMC instruction

29. May 20, 200329 PRR 371 – OOMC: Verifiable Incremental Costs Deleted requirement that ERCOT BOD review and approve compensation for cost types except for fuelDeleted requirement that ERCOT BOD review and approve compensation for cost types except for fuel Future Action Item: Describe other verifiable cost types and documentation requiredFuture Action Item: Describe other verifiable cost types and documentation required

30. May 20, 200330 PRR 371 – OOMC: Fallout for RMR Task Force Verifiable incremental costs – Section 6.8.2.2(5)(b)Verifiable incremental costs – Section 6.8.2.2(5)(b) Optimization of OOMC instructionsOptimization of OOMC instructions –Economic optimization –Honor physical characteristics of OOM Resource QSE Resource Plan – Section 4.4.15QSE Resource Plan – Section 4.4.15 –Need to require additional data in plan Review definition of Low Sustainable LimitReview definition of Low Sustainable Limit Determine other verifiable costs/documentationDetermine other verifiable costs/documentation

31. May 20, 200331 PRR 401 – Partial Payments & QSE Credit Requirements Partial payments (short pays) uplifted to loads on LRS basis if not collected within 120 days and the QSE is not in compliance with payment planPartial payments (short pays) uplifted to loads on LRS basis if not collected within 120 days and the QSE is not in compliance with payment plan Modifies Estimated Aggregate Liability (EAL) calculationModifies Estimated Aggregate Liability (EAL) calculation Allows ERCOT to offset against amounts owed by short-pay QSEAllows ERCOT to offset against amounts owed by short-pay QSE

32. May 20, 200332 PRR 401 – Partial Payments & QSE Credit Requirements Proposed EAL CalculationProposed EAL Calculation –Reduces EAL ratchet from 90 days to 60 days –Uses average of 2 initial invoices to calculate ADT – smooths collateral spikes –Includes TCR credits for ownership and auction revenues –Formalizes terms of “early pay”

33. May 20, 200333 PRR 401 – Partial Payments & QSE Credit Requirements Proposed EAL CalculationProposed EAL Calculation –Changes calculation to include OUT Outstanding invoices plus estimated unbilled itemsOutstanding invoices plus estimated unbilled items –Allows ERCOT to make downward adjustments in EAL outside ratchet period –Fixes SAF at factor of 1 until ERCOT gains more history on seasonal credit requirements

34. May 20, 200334 PRR 401 – Partial Payments & QSE Credit Requirements Proposed EAL CalculationProposed EAL Calculation –Allows estimation of balancing energy and ancillary service usage –Estimation of finals and true-ups based on three week average Mulitply final average by 9 weeksMulitply final average by 9 weeks Multiply true-up average by 48 weeksMultiply true-up average by 48 weeks

35. May 20, 200335 PRR 401 – Partial Payments & QSE Credit Requirements No impact on ERCOT computer systems; manual processesNo impact on ERCOT computer systems; manual processes Effective June 1, 2003Effective June 1, 2003 TAC approved PRS recommendation by a vote of 25-1-4TAC approved PRS recommendation by a vote of 25-1-4

36. May 20, 200336 PRR 407 – Removal of RBS Sunset Date PRR submitted to delete sentence:PRR submitted to delete sentence: –ERCOT will not initiate limitation or suspension of relaxed Balanced Schedules after May 1, 2003. PRS recommended rejectionPRS recommended rejection TAC recommends deleting entire paragraph by a vote of 27-1-1.TAC recommends deleting entire paragraph by a vote of 27-1-1.

37. May 20, 200337 PRR 407 – Removal of RBS Sunset Date Section 4.3.5

38. May 20, 200338 2004 CSCs and zones Same CSCs as 2003Same CSCs as 2003 –STP - Dow (Velasco) –Sandow - Temple –Graham - Parker /Graham - Benbrook Resulting 4 zonesResulting 4 zones –North2004 –South2004 –West2004 –Houston2004

39. May 20, 200339 Final Recommended ERCOT 2004 Congestion Management Zones WEST HOUSTON SOUTH NORTH

40. May 20, 200340 Recommended Exceptions STEC requested 3 busses (2 with total load ~11 MW) be designated in the South zone, rather than the clustering resulted Houston zone.STEC requested 3 busses (2 with total load ~11 MW) be designated in the South zone, rather than the clustering resulted Houston zone. Bryan Texas Utilities requested the Dansby generator (110MW) be designated in the North zone, rather that the clustering resulted Houston zone.Bryan Texas Utilities requested the Dansby generator (110MW) be designated in the North zone, rather that the clustering resulted Houston zone.

41. May 20, 200341