ERCOT Project Process Karen Farley COPS 3/22/05

Project Process  Overview of Project Requests  Process for Market Requests  Process for Internal ERCOT Requests  Program Area Teams (PATS)  Annual Prioritization Process  Questions

Overview of Project Requests ERCOT PMO ERCOT PMO ERCOT PM Process ERCOT PM Process PUCT Market Participants ERCOT Program Management Office Overall Management of: Project portfolio Project budgets, priorities and approvals Project Management Process Management of: Project delivery Project resources, costs, timelines Initiation of Project Requests PUCT Rulings System Change Requests (SCRs) Protocol Revision Requests (PRRs) Project Requests (PRs)

Process for Market Requests BoD TAC PRSCOPSRMSROS WG TF WG TF WG TF SCRPRR *Subcommittee will identify if this request requires a change to protocols. If no, then submitted via SCR *Any system change that does not require a change to the protocols will be submitted via SCR Note: SCRs – need to be submitted to TAC. They have to be submitted through a sub-committee. PRRs – need to be submitted to PRS. They can be initiated from sub-committees, working committees or submitted directly to PRS (ex: from ERCOT). Sub Committee Working Group or Task Force WMS WG TF

Internal ERCOT Requests  Is it an enhancement?  Improves operations  Fulfills regulatory obligations  Supports strategic goals/objectives  Positive cost benefit  Complete a project request?  Complete a request  Obtain manager or director sponsorship  Submit to CART for prioritization and rank  Is it a fix?  Addresses a system error Submit as a SIR/SPR Submit as a project request

Program Area Teams and Focus Areas Market Operations Data Agg Load Profiling Metering Statements/Billing WMS COPS Systems Operations POS MOS MMS WMS ROS Retail Operations Registration ESI ID TX SET RMS COPS IT Operations Data Warehouse Web Systems Trans Systems Hardware Network / SAN PRS TAC Corporate Operations Legal Finance HR Facilities Planning Strategy PRS TAC BOD Apps Areas Subcommittees & Communications

MO 2005 Release Plans Release A PR-40066_01 Lodestar 3.7 Upgrade (1.0 – 2004 carry) Settlements/Billing Load Profiling Data Aggregation Data Management Lodestar MV90 TCR/REC TGR StakeholdersSystems Q2 ‘05Q3 ‘05Q1 ‘05Q4 ‘04Q4 ‘05Q1 ‘06 Release “C” Release B1 PR SIR Enhancement (1.0 – 2004 carry) PRR488 PR EPS/RID Meter Data Extracts (1.0 – 2004 carry) EMMS Release 4 (4 MO projects) (1.0) PR TCR Report Enhancements (1.0 – 2004 carry) ER SIR Enhancement 5.2 (1.1) Release C PR SCR 740 Enhancements to SCR 727 (1.2) EMMS Release 5 (TBD projects) (1.1) ER SIR Enhancement 5.4 (1.1) MR Enhance ESI-ID Look- up Function (1.2) Release “A” Release “B1” & “B2” TCR/REC TGR Wholesale Client Relations Settlement Metering Release B2 PR SCR 727 Phase 2 (1.1) PR RMR Automation (1.0 – 2004 carry) MR PRR515 Disclosure of Local Congestion (1.0 – 2004 carry) PR Zero Charge Enhancements (1.0 – 2004 carry) ER SIR Enhancement 5.3 (1.1)

Retail Ops 2005 Release Plans Release RO 5.1 PR-40066_03 Siebel Upgrade (1.1) PR Retail Testing Website (1.1) Retail Transaction ProcessData Transparency and Rptg EDIMRetail Market Services Retail Client ServicesRetail Market Reporting ESI ID Retail – WS Sync Retail Market Testing Siebel EAI (SeeBeyond/TIBCO) TCH PaperFree Market Testing StakeholdersSystems Q2 ‘05Q3 ‘05Q1 ‘05Q4 ‘04Q4 ‘05Q1 ‘06 Release RO 5.3 Release RO 5.2 PR ERCOT.com (1.1) ER SIR Enhancements (1.2) PR Texas SET 2.1 (1.1) Release 5.3 PR SCR 738 (1.1) Enhancements to Fast Trak MR Potential Load Loss (1.2) Release RO 5.1 Release RO 5.2 Release RO 6.0 SOA Release RO 6.0 PR Service Oriented Architecture (1.1) Including sub-projects of PR PR-50121_03 Market Information Distribution

IT Ops 2005 Release Plans Release IO 5.1 PR 40042_01 EDW EMMS RSS (1.0) PR EDW L* ODS (1.0) PR EDW BI Foundation P2 (1.1) PR Storage to Support Ongoing Operations PUCT, Market, ERCOT EDW, EAI, & TML IT Infrastructure Facilities StakeholdersSystems Q3 ‘05Q4 ‘05Q1 ‘05 Release IO 5.2 PR 40042_06 EDW Std L* Extracts(1.0) PR EDW EMMS ODS (1.0) PR EDW BI Foundation P2 (1.1) PR Capacity True Up (1.1) PR Altiris DC Impl. (1.2) Release IO 5.3 PR Austin QA Build-out (1.1) PR EDW BI Foundation P2 (1.1) PR BI Reporting Tool (1.1) Release IO 5.1 Release IO 5.2 Q2 ‘05 Release IO 5.3 Release IO 5.4 Release IO 5.3 PR VeriSign (TML) (1.0) PR EDW BI Foundation P2 (1.1) PR EDW EMMS Reports (1.1) PR Disk Based Backup (1.2)

Annual Prioritization Process  Priority categories are high, medium, and low, with subcategories of high, medium, and low, which result in the following priorities:  High-High (1.1), High-Medium (1.2), High-Low (1.3), Medium-High (2.1), Medium-Medium (2.2), Medium-Low (2.3), Low-High (3.1), Low-Medium (3.2), Low-Low (3.3)  High – Critical to continued operations and reliability of the market, or in response to legal requirements. (Assumes that current services or functions provided are below acceptable level.)  Medium – Important to improve service or efficiency of operations of the market. (Assumes that the current services or functions provided are tolerable but not up to the desired state or target.)  Low – Recommended to further automate operations or improve efficiencies of services currently provided by the market. (Assumes that the current services or functions provided are acceptable but action is needed to prevent degradation of services.)  The subcategories (H/M/L) prioritized the projects within the category in terms of the value/impact to the market.

Thank You