1. MarkeTrak Enhancements MMWG March 23, 2007

2. 2 2 Roles and Responsibilities MMWG Responsible for the development of the SCR Task Force assigned by RMS Consolidate requirements identified by the Market into a Market Requirements Document. ERCOT Provide support to MMWG to develop SCR Work with Task Force to develop Market Requirements Document. Work with Market Participants to identify requirements. Identify additional ERCOT-related requirements

3. 3 3 ERCOT’s Participation Project Team Business Analyst – Jennifer Frederick (primary) Project Manager – Hope Parrish Technical Lead – Mike Taylor Business Lead – Dave Michelsen Client Services – TBD

4. 4 4 Retail Market Analysis Retail Market Services Retail Customer Choice Retail Market Testing Retail Client Services PUCT CODIA RMS Release RO 7.1 PR-50060 EIF Transition to EIS PR-50121_07 Retail Business Processes PR-50121_08 End Point Services, Phase II SiebelSerena Team Track EAI (TIBCO)Serena Collage PaperfreeMarket Testing ETSNAESB Q2 ’07Q3 ’07Q1 ’07Q4 ’06Q4 ’07Q1 ’08 Release RO 7.2 PR-40038 TX SET 3.0 PR-50059 EIS Siebel Transition PR-50061 EDW EAI Transition PR-70006 Website Enhancements for ERCOT Outages PR-70010 Transition of Production Reporting to EIS – Retail PR-70008 Exception Reporting / Monitoring Enhancements Release RO 7.3 PR-50088 ETS Transition to EDW PR 60008_01Terms and Conditions (new project) PR-70007 MarkeTrak Enhancements PR-60015 ESI ID Account Table Split – (this will impact across all Development areas) PR-70005 EIS Siebel to L* Data Comparison PR-70009 Systematic Exception Reprocessing Functionality PR-60028 Integration of Commercial Operations Data in EIS StakeholdersSystems Retail Ops CART (ROCART) 2007 Release Plans Release RO 7.3 Release RO 7.2 Release RO 7.1

5. 5 5 Draft Timeline & Delivery Approach PlanningInitiation 03/07 SCR Approved Mkt. Req. ERCOT Req. Mkt. Req. Approved ERCOT Req. Approved Design Concept. Design Doc. Mkt. Design Doc. (API) ERCOT Design Doc. (Incl. Technical and Security) Execution BuildiTestMarket Test Training ImplementationStabilizationContingency End – Late Q1 2008

6. 6 6 Market Requirements ERCOT will present Market Requirements Template for approval by Task Force Market Requirements will be compiled, revised, and approved by the Task Force. All Market Requested changes must be included in the Market Requirements Document.

7. 7 7 MarkeTrak Escalation Process Day to Day Issues: Cancellation: –Escalation after 7 days without transition Inadvertent Switch: –Escalation after 14 days without an acknowledgement by CR2 –Escalation after 28 days without transition out of VOTE state Escalation notices go to non-Voted parties All other D2D Sub Types: –Escalation after 28 days without transition All DEV Escalation after 75 days without transition

8. 8 8 MarkeTrak Escalation Process LPA Profile, Premise and Meter –Escalation after 30 days without transition Zip and Sub-Station –Escalation after 45 days without transition Weather Sensitivity –Escalation after 60 days without transition Weather Zone –Escalation after 90 days without transition

9. 9 9 ERCOT MarkeTrak SIRS SIRDESCRIPTION 10907RETL – MT ERCOT Initiated WF Complete Transition Requires Comments 10946RETL – MT Add Exception Code Field to Bulk Insert and API 10957RETL – MT Add 650_04 to Transition Type Drop Down 11063RETL – MT Circular Responsible MP Workflow Problem 11016RETL – MT Siebel Adapter Error Message Cleanup 11208RETL – MT Stop Time/Start Time Review 11055RETL – MT1 Second Subtracted From Stop Time After Every Redo Message 11205RETL – MT Auto Completed Issues Need to Show Closed 10969RETL – MT Add More Validation to Bulk Insert GUI 11279RETL – MT D2D IAS – Gaining/Losing Owner is clearing on “Select IAS Parties’ 11233RETL – MT Add Withdraw Transition to Bulk Insert Issues Type 11036RETL – MT Link to MT User’s Guide 11269RETL – MT Add Requested Resolution to DEV LSE (API Field) 10996RETL – MT ESI ID Min Length of 8 Validation 11193RETL – MT UIDESIID Numeric 11268RETL – MT E.I. GlobalID Defaults to “Auto”

10. 10 Lessons Learned Improvement AreaRecommended Future Action Improvement Area #1: Communications RMS to name project-related MP Steering Committee to provide Market leadership and oversight, to issue/review MP communications; to provide Market sign-offs as needed ERCOT will target project-related communications to appropriate business and technical contacts designated by MPs and/or MP Steering Committee Improvement Area #2: Project Management When initiating a Market-facing project, ERCOT will announce the Project Delivery contacts, inclusive of the PM, the Business Analyst, and Technical Contact (as appropriate) The project schedule needs to incorporate “project status” milestones where MPs are informed of the project schedule, scope, budget, and risks/issues (not RMS) ERCOT’s PM and project leads will meet with MP Steering Committee on a recurring basis to review project “health” In addition to the proposed MP Steering Committee, ERCOT will solicit business and technical MP groups to be assigned to the project for detailed reviews Improvement Area #3: Business & Technical Requirements ERCOT will conduct regularly scheduled check point meetings with MP Steering Committee to verify/validate requirements ERCOT will seek Market sign-off for Business and Technical Requirements ERCOT will share “draft” requirements documents with MP for their review/feedback before final versions are presented for sign-off ERCOT and MPs must consider the governance process timeline and intent of SCR process to minimize project impacts

11. 11 Lessons Learned Improvement AreaRecommended Future Action Improvement Area #4: Vendor/Product Selection ERCOT can provide more product demos earlier in the project process, where feasible, to allow MPs to gain a better understanding of the new product Early in the project lifecycle, ERCOT will conduct requirements validation sessions with MPs Improvement Area #5: Documentation Market and ERCOT will agree to all document templates ERCOT will leverage a document versioning system to readily identify most recent version and to highlight changes from the previous version ERCOT will continue to use a project webpage to make documents available to MPs Improvement Area #6: Training ERCOT will attempt to complete all testing prior to training start; milestones will be reflected and tracked via the project schedule ERCOT will attempt to ensure all product functionality is available and working for future training classes MP Steering Committee should define and implement “readiness” criteria to address minimum training required for MP to use a new tool (or revised tool) Improvement Area #7: Testing RMS (or MP Steering Committee) to engage TTPT and ERCOT Test Team in defining test action plan (scope, schedule, scripts), based on project complexity and timeline

12. 12 Questions?