1. 1 PR70007 – MarkeTrak Ph2 ERCOT Project Strategy 07/30/2007

2. 2 PR70007 – MarkeTrak Ph2 ERCOT Project Strategy Objective: ERCOT Project Lifecycle Overview Discuss the Planning timeline Discuss the approach of the Workstreams at ERCOT Goal: Move from Initiation to Planning

3. 3 ERCOT Project Lifecycle

4. 4 Divisional Projects Organization Overall Management of:  Portfolio of Projects  Program Area Structure  Project, Priorities & Reporting and Monitoring Project Management Process Management of:  Budgets and Approvals  Project Delivery  Resources, Costs, Timelines Initiation of Project Requests:  PUCT Rulings  System Change Requests (SCRs)  Protocol Revision Requests (PRRs)  Nodal PRRs (NPRRs)  ERCOT Project Requests (PRs) ERCOT DPO / Executive Committee ERCOT DPO / Executive Committee ERCOT PM Process ERCOT PM Process PUCT Market Participants ERCOT Projects Pipeline Origin of Projects

5. 5 Project Phases and Deliverables **Note: All Consistent with PMI Standards

6. 6 ERCOT Initiation Phase Status Recommended to move to Planning to begin capitalizing effort and work in Planning Deliverables Requirements to move to Planning Phase: DeliverableStatus Project CharterComplete Planning ScheduleNeed defined milestone date for Requirement Baseline delivery Planning Resource PlanDependency on schedule Updated Cash Flow for PlanningDependency on Planning Schedule and Resource plan

7. 7 Project Timeline

8. 8 Actuals from PR50007: MarkeTrak Ph1 MilestoneDuration (days)Hours Requirements192 days402 hrs Conceptual Design36 days172 hrs Detail Design44 days156 hrs Technical Architecture186 days72 hrs **Note: Ph1 delivered new product, new functionality, and system hardware

9. 9 Timeline Options Option 1: 180 days Requirement Option 2: 90 days Requirement 2 nd Qtr 2007 Planning 7/11: RMS approves SCR 04/04: Begin Execution 3 nd Qtr 2007 4 nd Qtr 2007 1 st Qtr 2008 2 st Qtr 2008 3rd Qtr 2008 Timeline/ Milestones Initiation 08/01: Begin Execution Initiation Planning 04/07: Final Baseline Requirements 07/28: Approved Detail Design 11/23: Final Baseline Requirements 03/25: Approved Detail Design

10. 10 ERCOT Recommendation for Option 2 Benefits Begin Execution in Q108 Approved funding for 2008 Higher Potential to begin/complete implementation in 2008 Dependencies May require more brainstorming session Market SME Participation during requirements critical

11. 11 Approach to Workstreams

12. 12 Workstreams ERCOT recommends categorizing Requirements into workstreams Allows ease of prioritization Allows ease of packaging like system impacts Allows ease of release planning during Execution Allows further definition of each requirement into a deliverable DEV shops perform Impact Assessment of Use Case Questions addressed, Workstream Assigned Use Case Defined at Task Force

13. 13 Example – Workstreams from MIMO WorkstreamDescriptionReferenceUse CasesApplication ImpactEntity Impact Workstream A Restrict which Tran- Types are available by WF SCR749 Issue #X 1, 2Siebel TIBCO Marketrak GUI Marketrack API Workflow ERCOT TDSP CR Workstream B Default Submitter Vote to 'Agree' on IAS Workflow 2, 3Siebel TIBCO PaperFree ERCOT TDSP CR Workstream C MT Sub-type names consistently applied 4Siebel TML TIBCO PaperFree ERCOT TDSP CR Workstream D Add DEV parent to Projects 5Siebel TIBCO PaperFree ERCOT TDSP CR Workstream E Add required new field Total to IDR usage present MP not ERCOT Workflow Siebel SeeBeyond ERCOT TDSP CR

14. 14 Discussion