1. MarkeTrak Orientation July 30, 2008

2.  Antitrust Admonition  Introductions  MarkeTrak Flight Test Orientation  Why Do We Test?  Overview  API vs GUI Testing  Testing Business Day  Flight Administrator  Scripts  Checklist  Roles and Responsibilities  Go Live  Questions

3. Why Do We Test?  Identify issues within the tool itself  Identify issues within your company  Acquaint personnel with the MarkeTrak tool in a test environment  Build market confidence with the MarkeTrak tool  Eliminate/minimize downtime when starting up in production with the MarkeTrak tool

4. Overview  Market Participants have been sent a test bed of ESI IDs to use during testing  Test Flight is expected to last five (5) business days  Market Participants experiencing issues logging on (permission rights) would contact Flight Administrator  Market Participants are not sending EDI transactions in association with the MarkeTrak test scripts  Market Participants are not performing TEXAS SET validations on EDI transactions  For Example: Tran ID  Market Participants are expected to attend a daily conference call to discuss status of the test flight  Call is at 2:30 CPT  MPs should be prepared to present their status to the Flight Administrator

5. API Testing vs GUI Testing  There are two (2) interfaces a MP may use to test in the MarkeTrak flight  Market Participants who are using an Application Programming Interface (API) are required to test  Market Participants who are using a Graphical User Interface (GUI) voluntarily choose to test

6.  Dedicated resources are preferred  Testing business hours 8am-4pm CPT  All new MarkeTrak issues in scripts submitted by 10am CPT  Start and finish a script within the same day (When Possible)  MPs should update the checklist and email the appropriate testing partners when they have completed their step in the script  Market Participants are expected to attend a daily conference call to discuss status of the test flight  Call is at 2:30 CPT  MPs should be prepared to present their status to the Flight Administrator Testing Business Day

7. Flight Administrator  The Flight Administrator will act as a neutral facilitator throughout the testing effort.  Will send reminder about flight test start date  Gene Cervenka of ERCOT is the Flight Administrator for this flight  gcervenka@ercot.com gcervenka@ercot.com  (512) 248-3903

8. Scripts  Texas Test Plan Team in coordination with the MarkeTrak Task Force developed scripts to test the new functionality of MarkeTrak  There are 22 scripts in the test flight  Data Extract Variance Workflows  Inadvertent Gain Workflows  Day to Day Workflows

9. Scripts  Location  Retail Testing Website  HTTP://ETOD.ERCOT.com HTTP://ETOD.ERCOT.com  You will need a login to access these scripts  Contact  Contact RetailMarketTesting@ercot.com  Demo

10. Checklist  ERCOT maintains a password-secured section on the Texas Retail Testing website to track the progress of each entity through the testing process. Through the Checklist link on this site, the MPs have the capability to view overall progress of the Texas Retail Market testing on the Complete/Total Tasks by MP link. They are also expected to update their individual status with the most current information on their testing progress by selecting View Checklist by Partner or View Checklist by Custom Criteria.

11. Checklist Demo

12.  Contact list  Digital Certificates  Email updates  Update checklists  Attend conference calls  Dedicated resources  Log defects Roles and Responsibilities

13. Go Live  MarkeTrak Release 2 will go live on August 18 th, 2008  Issues opened prior to cutover will need to be completed under previous workflow  Any defects that MPs experience should be logged with the ERCOT Help Desk  Helpdesk@ercot.com Helpdesk@ercot.com

14. Questions