Objectives: Develop a solution to either enhance or replace the FasTrak tool Scope/Why is this important?: Increase the transparency for issues that are submitted via FasTrak Allow users to have improved access to the data Improve the reporting functionality Improve search functionality associated Improve monitoring and response capabilities Improve the usability Dependencies: Siebel upgrade – only if Siebel is chosen as the replacement tool for FasTrak – Removed SOA Integration - dependent on SOA MID project for integration framework components needed by API Objectives: Develop a solution to either enhance or replace the FasTrak tool Scope/Why is this important?: Increase the transparency for issues that are submitted via FasTrak Allow users to have improved access to the data Improve the reporting functionality Improve search functionality associated Improve monitoring and response capabilities Improve the usability Dependencies: Siebel upgrade – only if Siebel is chosen as the replacement tool for FasTrak – Removed SOA Integration - dependent on SOA MID project for integration framework components needed by API Project Objectives / Scope / Dependencies PR Enhancements to FasTrak As of September 8, 2005Page 1

Phase: Initiation – Completed in Feb 2005 Planning – March 14, 2005, scheduled to be completed in October 2005 Execution – October 2005 Implementation – May 2006 Recent: Executive Committee update/endorsement on product selection/purchase Board of Director approval of project to move forward Serena Team Track training for business and IT August 29th to September 2nd Serena contract negotiations underway Review/revision of project schedule given current scope, delivery approach, testing requirements, and resource availability Next steps: Finalize contract with vendor Human Factors staff to work with business and IT on screen designs Business to create DRAFT work flows IT to create conceptual system design Phase: Initiation – Completed in Feb 2005 Planning – March 14, 2005, scheduled to be completed in October 2005 Execution – October 2005 Implementation – May 2006 Recent: Executive Committee update/endorsement on product selection/purchase Board of Director approval of project to move forward Serena Team Track training for business and IT August 29th to September 2nd Serena contract negotiations underway Review/revision of project schedule given current scope, delivery approach, testing requirements, and resource availability Next steps: Finalize contract with vendor Human Factors staff to work with business and IT on screen designs Business to create DRAFT work flows IT to create conceptual system design Summary of Project Status PR Enhancements to FasTrak As of September 8, 2005Page 2

ISSUES: Schedule Change Team determined that longer duration was needed to adequately evaluate, demo, and select a product. Resulted in additional 8 weeks of evaluation/selection activities in Planning phase Contract negotiations with the software vendor taking longer than planned; ERCOT contract process/rules are adding time to vendor negotiations. Resulted in additional 4 weeks in Planning phase Net result is a 12 week extension to the schedule New launch timeframe is May 2005 (from February 2005) RISKS: Schedule is highly dependent on availability of development resources; ERCOT moving to quickly bring on outside resources to assist FY2006 Budget could be impacted. ERCOT is reviewing for potential impacts and expects to finalize 2006 project budget by end of Planning in October. ISSUES: Schedule Change Team determined that longer duration was needed to adequately evaluate, demo, and select a product. Resulted in additional 8 weeks of evaluation/selection activities in Planning phase Contract negotiations with the software vendor taking longer than planned; ERCOT contract process/rules are adding time to vendor negotiations. Resulted in additional 4 weeks in Planning phase Net result is a 12 week extension to the schedule New launch timeframe is May 2005 (from February 2005) RISKS: Schedule is highly dependent on availability of development resources; ERCOT moving to quickly bring on outside resources to assist FY2006 Budget could be impacted. ERCOT is reviewing for potential impacts and expects to finalize 2006 project budget by end of Planning in October. Project Issues/Risks PR Enhancements to FasTrak As of September 8, 2005Page 3

** All target dates will become firm after design is complete and project plan finalized in October Requirements – June 2005 Design (published document) – November 2005 Internal Testing – January 2006 – March 2006 External Testing – May 2006 Internal Training – January 2006 – February 2006 External Training – March 2006 – April 2006 Production (Go live) – May 2006 ** All target dates will become firm after design is complete and project plan finalized in October Requirements – June 2005 Design (published document) – November 2005 Internal Testing – January 2006 – March 2006 External Testing – May 2006 Internal Training – January 2006 – February 2006 External Training – March 2006 – April 2006 Production (Go live) – May 2006 High level timeline PR Enhancements to FasTrak As of September 8, 2005Page 4

Bus Lead: Scott Egger phone number: PPL: Source: Market Priority: 1.1 Rank: 9 Program Area: RO What prompted the project: SCR 732 SCR 738 Supporting business drivers: Practical usage feedback Bus Lead: Scott Egger phone number: PPL: Source: Market Priority: 1.1 Rank: 9 Program Area: RO What prompted the project: SCR 732 SCR 738 Supporting business drivers: Practical usage feedback Additional Information PR Enhancements to FasTrak As of September 8, 2005 Page 5