1. ERCOT PMO Update Robert Connell Director Program Management March Board of Directors March 8, 2005 (Through 2/28/05)

2. Feb. 2005 2005 YTD Project Performance Project Process Improvements In 2005  4 completed, 4 YTD  9 in Initiation  20 in Planning  21 in Execution  Institute Managed Time Periods  Establish sound schedule management  Expand on Project Metrics – EVM  Establish Risk Management Methodology Project Activity Project Performance First Quarter Results (to 2/28)

3. Feb. 2005 Major ERCOT Projects Summary ProjectTotal BudgetActual 10/31Metrics Duration/Information (Sponsor)Phase/Scheduled CompletionScheduleBudget Taylor Building (2004-2005)$12.9M$12.3M Construction Nearing Completion (S Jones)Execution Phase/1st Qtr 2005 EMMS Release 3 (2003-2004)$8.3M 17 separate projects over 14 mos. (S Jones)Implementing in February EMMS Release 4 (2004-2005)$9.5M$6.6M 20 separate projects over 14 mos. (S Jones)Planning Phase/2 nd Qtr 2005 Service Oriented Architecture (2004 -2006)$5.8M$4.3M 8 Architecture projects over 30 months (R Giuliani)Planning Phase/4th Qtr 2006 Commercial System Upgrade (2003-2005)$4.7M$3.9M separate upgrade projects. (R Giuliani)Execution Phase/3rd Qtr 2005 Market Oversight Monitoring System (2003-2005)$1.9M$1.0M 2 separate projects over 12 mos. (S. Jones) Execution Phase/3rd Qtr 2005 ERCOT.com Improvements$1.1M$196K Project to establish Search Engine, improve on Content Management, Navigation, and content organization (R. Guiliani) Initiation Phase/4 th Qtr 2005

4. Feb. 2005 Projects Completed 1 st Quarter  Projects Completed in January  40102 REC Enhancements  30099 Taylor Expansion  Projects Completed in February  40042_01 EDW EMMS RSS  30144 EMP 2.2 Upgrade  Projects Completed in March

5. Feb. 2005 REC Enhancements  Scope: REC Enhancement project was completed to satisfy PUCT Project No. 28407 – Order Adopting Amendments to Subs. Rule 25.173. The Order calls for changes in the REC Final REC Purchasing Requirements (FRRs) and allows for recalculations of previous year’s Final REC Requirement for Competitive Retailers. Requirement 1: Update the methodology and calculation for FRR Requirement 2: Update the methodology and calculation for Final REC Requirement 3: Update the statewide and individual REC requirement reports Requirement 4: Add commas in all numeric fields where needed Requirement 5: Update the CCF calculation to be “As Needed”  Features and Deliverables: Requirements 1-4 listed above were completed Requirement 5 deferred into O&M activity in 2005 based on additional changes in the calculation from PUCT  Current Activity Closed out REC Enhancement project in 1/2005 Business team working with PUCT to improve design of the REC functionality. It is planned to be a 2006 capital project 7/04 8/04 InitiationPlanningExecution Closeout 10/0412/041/05

6. Feb. 2005 PR-30099 Taylor Expansion  Scope:  Design facilities for short-term, mid-term and long term growth needs. Construct Short-term and mid-term facilities.  Features and Deliverables:  Construct a facility of similar quality and appearance to the MET center and the TCC located in close proximity to the TCC.  Construction of mobile units which will accommodate expected short term growth in 2003 and also provide a buffer prior to building of phase III when and if it becomes necessary.  The relocation of employees, contractors and vendors from outlying areas by 2004  Design Plans which take into account a longer projected growth rate  Design plans which accommodate both security factors and human factors Ensure availability of reliable, accurate and timely information  Current Activity In Closure 9/2003 – 2/2004 Planning 5 Months Execution 12 months Close 1.5 months 2/2004 -2/20052/2005 – 3/2005

7. Feb. 2005 PR-40042_01 EDW EMMS RSS  Scope: Implementation of the EDW EMMS RSS (Replicated Source System) to support the ability to capture intra-day transactions from the EMMS source databases, as well as support the ability to capture information to support point-in-time reporting. The EMMS RSS is a replicated database copy of the source system that will be used to transfer information into the EDW EMMS ODS (Operational Data Store). The EDW EMMS ODS is a separate subproject – 40042_07.  Features and Deliverables: Ensure availability of reliable, accurate and timely information Provide the ability to capture intra-day transactions that will ensure all EMMS data is being captured (and not just a snapshot of data at the end of the day), as well as near real-time data that can then be used to support market monitoring reporting Store the data using point-in-time fields that will allow reporting of historical periods.  Current Activity In production 1/5/04-5/19/04 Planning 4 Months Server/Environment Setup - 4 Months Development 2 Months Int & Test 1 Month Production Go-Live and Stabilization 5/19/04-9/8/049/8/04-10/27/0410/27/04-12/3/0412/3/04-2/16/05

8. Feb. 2005 Implement SMP/EMP2.2 for EMMS  Scope: Implement the SCADA Management Platform and Energy Management Platform 2.2 from AREVA. Scope includes the following set of approved deliverables: 1.PR20159 Load Rollover 2.PR30050 EMS Front-End Replacements (Replace obsolete technology) 3.PR30074 Enhance STNET Multiple Selected Time Ranges 4.PR30094 DCP Enhancement (VSAT/TSAT Enhancements) 5.PR30096 Move PTI Bus Translation to Genesys 6.PR30170 Implement a selected contingency into Power Flow 7.PR40099 CTGS Import/Export Dump Utility (ERCOT development) 8.PR40094 Constraint Activity Manager (CAM v2.2 – ERCOT development)  Features and Deliverables: The SMP product allows ERCOT to retire obsolete technology that is no longer supported by the manufacturer of key communications software that is used to control Frequency. The EMP2.2 product implements new AREVA software releases that includes enhancements in EMS Network Applications that help ERCOT improve reliable grid operations. The ERCOT developed deliverables provides features that help reduce congestion costs.  Current Activity Fully in production as of 2/10/05. Seeking funding approval for missed closing requirements such as retirement of obsolete technology and software issues identified during final User Acceptance Testing. 4/1/03-11/30/03 Planning 8 Months Development 8 Months Int & Testing 4 Months Go-Live and Stabilization 12/1/03-8/20/049/23/04-1/13/051/24/05-Present