1. COPS – ERCOT PROJECTS UPDATE WHOLESALE MARKET DEVELOPMENT Paula Feuerbacher February 22, 2005

2. PROJECTS:  PR40075 – PRR-488 – Weather Responsiveness  Estimated Deployment: March, 2005  PR30026 – EPS Meter Data Extract  Estimated Deployment: April, 2005  PR40104 – Zero Charge Elimination  Estimated Deployment: 3 rd Quarter of 2005  This project has been placed on-hold by ERCOT until the Lodestar 3.7 Upgrade project deploys to the Production Environment.  Once the project is removed from on-hold status, ERCOT will begin the process of gathering requirements and exploring several options with which this effort may be deployed without impacting Market Participants. Those options will be presented at future COPS meetings. Those options will be presented at future COPS meetings.

3. Lodestar Upgrade Status  Estimated Deployment: mid March, 2005  Test Plan:  Execute full batch baseline versions in 2.25  Rerun baselines in 3.7 (perform comparison to 2.25) Included: Daylight Savings Days, year crossover, weekend/holiday, reports, back-out functionality. Included: Daylight Savings Days, year crossover, weekend/holiday, reports, back-out functionality.  Comparison of baselines between various testing environments (P-Test and I-Test; must match)  Database User Functionality  Interfaces to other packages  Production Simulation – full batch runs across all packages including user macros, reporting, etc.  Reports supplied to the Market (data/format) will not be impacted by this upgrade.

4. Lodestar Upgrade Schedule Status Baseline 2.25 to 3.7 Compare Complete (successful) User functionality In Progress Siebel to Lodestar In Progress 867 Upload (NIDR and IDR) In Progress 867 Outbound (ERCOT read meters) Complete (successful) Statements Posting Complete (successful) Invoice Posting In Progress EMMS/MOS Interface In Progress NDAuto Complete (successful) MV90 Lodestar to Lawson Complete (successful) Siebel to Lodestar Synch Complete (successful) Data Archive Not Started Enterprise Data Warehouse Not Started 814_20 Payment Posting Complete (successful) TCR Conversion Validation Complete (successful) Load Research Sampling Complete (successful) Production Simulation Not Started

5. PROJECTS: EMMS R4  Estimated Deployment: mid May, 2005  PR30131_02 – Resource Plan Improvements  PR30093 – Replacement Reserve  PR40050 – Resource Specific Bid Limits  PR30163 – OOM Tool

6. PR30131_02 – Resource Plan  New Bill Determinants  HSL_zone_qse_unit: 96 hourly interval cut in the Settlement and Billing Extract. High Sustainable Limit whose value can change every 15 minutes. High Sustainable Limit whose value can change every 15 minutes.  OOMCFLAG_zone_qse_unit: 24 hourly interval cut in the Settlement and Billing Extract when utilized. A binary (0,1) flag that indicates if a unit has been procured for OOMC A binary (0,1) flag that indicates if a unit has been procured for OOMC  0 value indicates the unit was not deployed for OOMC  1 value indicates the unit was deployed for OOMC  Impacted Bill Determinants  RP_zone_qse_unit: 96 hourly interval cut in the Settlement and Billing Extract Currently reported as 24 hourly interval cut Currently reported as 24 hourly interval cut  RPAGG_zone_qse_unit: 96 hourly interval cut in the Settlement and Billing Extract Currently reported as 24 hourly interval cut Currently reported as 24 hourly interval cut  LSL_zone_qse_unit: 96 hourly interval cut in the Settlement and Billing Extract Currently reported as 24 hourly interval cut Currently reported as 24 hourly interval cut

7. PR30093 – Replacement Reserve  New Bill Determinants  LCFLAG_zone_qse_unit: 24 hourly interval cut in the Settlement and Billing Extract 0 value indicates zonal RPRS was awarded 0 value indicates zonal RPRS was awarded 1 value indicates local RPRS was awarded 1 value indicates local RPRS was awarded 2 value indicates no instruction awarded 2 value indicates no instruction awarded  ZRPHR_zone_qse_unit: 24 hourly interval cut in the Settlement and Billing Extract Number of hours a generating unit is continuously procured for zonal RPRS to allow the payment to be spread across the number of hours the generating unit was procured. Number of hours a generating unit is continuously procured for zonal RPRS to allow the payment to be spread across the number of hours the generating unit was procured.  LRPHR_zone_qse_unit: 24 hourly interval cut in the Settlement and Billing Extract Number of hours a generating unit is continuously procured for local RPRS to allow the payment to be spread across the number of hours the generating unit was procured. Number of hours a generating unit is continuously procured for local RPRS to allow the payment to be spread across the number of hours the generating unit was procured.  LPS_zone_qse_unit: 24 hourly interval cut in the Settlement and Billing Extract Start-up price of a unit selected for local RPRS. Start-up price of a unit selected for local RPRS.  LPO_zone_qse_unit: 24 hourly interval cut in in the Settlement and Billing Extract Operating price of a unit selected for local RPRS. Operating price of a unit selected for local RPRS.  ZRPADJ_zone_qse_unit: 24 hourly interval cut in the Settlement and Billing Extract when utilized. Manual adjustment imported by Settlements & Billing for dispute issues. Manual adjustment imported by Settlements & Billing for dispute issues.  LRPADJ_zone_qse_unit: 24 hourly interval cut in the Settlement and Billing Extract when utilized. Manual adjustment imported by Settlements and Billing for dispute issues. Manual adjustment imported by Settlements and Billing for dispute issues.  HSL_zone_qse_unit: 96 hourly interval cut in the Settlement and Billing Extract. High Sustainable Limit whose value can change every 15 minutes. High Sustainable Limit whose value can change every 15 minutes.  ZRPHRBP_zone_qse_unit: 24 hourly interval cut in the Settlement and Billing Extract. Hourly bid price used in zonal RPRS payment calculation. Hourly bid price used in zonal RPRS payment calculation.  ZRPSUBP_zone_qse_unit: 24 hourly interval cut in the Settlement and Billing Extract. Start-up bid price used in zonal RPRS payment calculation Start-up bid price used in zonal RPRS payment calculation  OOMCFLAG_zone_qse_unit: 24 hourly interval cut in the Settlement and Billing Extract. A binary (0,1) flag that indicates if a unit has been procured for OOMC A binary (0,1) flag that indicates if a unit has been procured for OOMC  0 value indicates the unit was not deployed for OOMC  1 value indicates the unit was deployed for OOMC

8. PR40050 – Resource Specific Bid Limits  LEIOL_zone_qse_unit: 96 interval cut in the Settlement and Billing Extract  Returns to extract – no format change

9. PR30163 – OOM Tool  New Bill Determinants  OOMEVDI_zone_qse_unit: 96 interval cut in the Settlement and Billing Extract A VDI OOME instruction that is sent to a unit. A VDI OOME instruction that is sent to a unit.  OOMEFLT_qse: 96 interval cut in the Settlement and Billing Extract An OOME instruction that is sent to a QSE to move any units ERCOT wide a certain amount An OOME instruction that is sent to a QSE to move any units ERCOT wide a certain amount  OOMEZNL_zone_qse: 96 interval cut in the Settlement and Billing Extract An OOME instruction that is sent to a QSE to move any units within a particular Zone a certain amount An OOME instruction that is sent to a QSE to move any units within a particular Zone a certain amount  OOMCVDIFLAG_zone_qse_unit: 24 hourly interval cut in the Settlement and Billing Extract when utilized. A binary (0,1) flag that indicates if a unit has been procured for OOMC via a VDI. A binary (0,1) flag that indicates if a unit has been procured for OOMC via a VDI.  INTERVALHOLD: 96 hourly interval cut in the Settlement and Billing Extract. A flag that indicates if an interval hold instruction has been issued. A flag that indicates if an interval hold instruction has been issued.  Each hold instruction is assigned a unique and sequential identifier (1, 2, 3) per trade day for the length of the instruction.

10. EMMS R4 TRAINING  Discuss Market training options:  Market Bulletins are currently being drafted and scheduled to send by mid March  Should ERCOT schedule Market Training meetings to… Piggy-back with Operations Training Piggy-back with Operations Training  Different audience? Piggy-back to a COPS meeting Piggy-back to a COPS meeting  Settlement focused Other suggestions… Other suggestions…