1. February 5, 2009 Technical Advisory Committee Meeting Texas Nodal Program Implementation: Program Update Trip Doggett

2. 2 2 Nodal Program UpdateFebruary 5, 2009 Agenda Program Highlights Detailed Risk Status –Nodal Program Risks –ERCOT Enterprise Risks that Affect the Nodal Program

3. 3 3 Nodal Program UpdateFebruary 5, 2009 Program Highlights – 1 Since the schedule was replanned June 1, 2008, all tasks on the program critical path are currently on schedule –Of 16 scheduled tasks on the critical path (to date), the program has hit 16 –Of 2,575 total scheduled tasks (to date), the program has hit 2,262 Nodal leadership is preparing management action plans in response to Utilicast’s Report 8 (schedule and budget assessment) Efforts to renegotiate vendor contracts continue with interviews of 3 rd party negotiator candidates underway

4. 4 4 Nodal Program UpdateFebruary 5, 2009 Program Highlights – 2 Core projects and associated releases NMMS Delivered a validated model (v1.21 schema and data set) on Jan. 9. The delivery of the validated model ensures that data can be utilized from the new Nodal network model in downstream systems (MMS and EMS). Started functional acceptance test (FAT) for NMMS 6 release on Jan. 19; scheduled to complete by Mar. 17 EMS Started FAT on Release 6.1.1.1 (release to address several SIG issues and NPRRs 97 & 102) on Jan. 7; scheduled to complete by Feb. 6 MMS Completed FAT testing for MMS4 Patch6 (CIM importer additions, partial NPRR113, and partial SIG Rounding Paper) on Jan. 9 Received MMS4 Patch7 from ABB on Jan. 23; release is currently undergoing smoke testing to prepare for start of structured testing in FAT COMS Continue meetings with Data Extracts Working Group (DEWG) and API Subgroup to address extract/report and API technical questions. Identified dates for delivery of extract user guides and technical documentation to market participants (March 2009) Conducting FAT of COMS integration with MMS4P6, remaining billing determinants and smoke testing integration between Settlements and Billing and Credit Monitoring System, with target completion of Jan. 30

5. 5 5 Nodal Program UpdateFebruary 5, 2009 Nodal Program Risk: Integration Testing Strategy Needs Updating Risk: Integration Testing Strategy Needs Updating The existing integration testing strategy (e.g. planning approach, team structure, methodology) may not be adequate to successfully perform integration. Risk Life Cycle State DefinePlanManageWatch Mitigation PlansWhoTarget DateCurrent Status 1. Identify leader for the entire Enterprise Verification effort (interface and end-to- end testing, market trials and system cutover) J. Ply1/13/09Complete; Linda Clarke named as the Nodal Enterprise Verification Lead 2. Develop high level approach for Enterprise Verification. L. Clarke2/16/091/28/09 – Work is in progress. 3. Review and refine the leadership and staffing levels for Nodal Enterprise Verification. L. Clarke2/27/091/28/09 – Work is in progress, with target to have organization structure established by 2/6, with key positions filled by end of February.

6. 6 6 Nodal Program UpdateFebruary 5, 2009 Nodal Program Risk: Nodal Integration Test (iTest) and EDS Environments Risk: Nodal Integration Test (iTest) and EDS Environments Because the current iTest environment is set up in the EDS (passive) environment, and because it lacks all of the required platform software and permissions, the Nodal program cannot effectively conduct integration testing. Delays in integration testing threaten program delivery. Risk Life Cycle State DefinePlanManageWatch Mitigation PlansWhoTarget DateCurrent Status 1. Review current iTest environment and strategy. K. Meinen2/3/09Environment and approach under study and discussion Gap analysis of current environment to needs to complete 1/30 2. Establish a detailed plan and project schedule for key activities and milestones to establish and maintain the iTest environment. Include elements such as: –Ensure all technical architecture documents are current –Deploy all needed HW –Install all Nodal systems, with required components –Establish release procedures with appropriate controls –Ensure iTest environments match needs of integrated testing strategy K. MeinenTBD

7. 7 7 Nodal Program UpdateFebruary 5, 2009 ERCOT-Wide Risk: Zonal Resource Constraints for Nodal Program Risk: Zonal Resource Constraints for Nodal Program Because the Nodal go-live date has been delayed, there are a number of Zonal projects, PRRs, and IMM suggestions for Zonal improvements that may result in resource constraints for the Nodal Program. Risk Life Cycle State DefinePlanManageWatch Mitigation PlansWhoTarget DateCurrent Status 1. Manage list of PRRs and SCRs to a resource plan that uses a strategy to avoid impacting Nodal personnel resources when delivering additional Zonal enhancements. D. Troxtell T. Anderson ongoing1/30/09 – Complete review with TAC, PRS, and WMS on the current list of reconsidered and new PRRs and SCRs. No expected impact to Nodal. Updates will be provided to Nodal PMO as the list evolves. 2. Manage Project Priority List (PPL) with clear view of resources needed for any projects in flight or about to be launched, with a strategy to avoid impact on Nodal personnel resources. D. TroxtellOngoing1/28/09 – Current PPL shows no threat to Nodal personnel resource; updates to be provided to Nodal PMO as the PPL evolves.

8. 8 8 Nodal Program UpdateFebruary 5, 2009 ERCOT-Wide Risk: Database Refresh for Test Environments Risk: Database Refresh for Test Environments In order to keep the multiple database environments (DEV, iTest, PROD) at production level quality, a refresh of the associated databases must be completed. This includes EMS and commercial systems data in iTest. This must be done in a way that accommodates Nodal use of test data in Nodal test environments. Risk Life Cycle State DefinePlanManageWatch Mitigation PlansWhoTarget DateCurrent Status 1. Plan and execute the database refresh. H. Parrish3/30/091/28/09 – Plan is in work, with weekly meetings to synchronize activities across teams. No impact expected.

9. 9 9 Nodal Program UpdateFebruary 5, 2009 ERCOT-Wide Risk: Data Center Space Concerns Risk: Data Center Space Concerns Data center capacity, space, and power may be inadequate for Nodal Program go-live, unless plans for expansion are adequate. Risk Life Cycle State DefinePlanManageWatch Mitigation PlansWhoTarget DateCurrent Status 1. Establish an Information Lifecycle Management approach, to manage the life cycle of data being managed. R. HinsleyUnderwayERCOT project PR 90006_01 Commercial Systems Information Lifecycle Management: Project Manager has been named, SAIC is engaged to complete a roadmap for a strategy. 2. Expand current data center space, and build out new data center, to increase ERCOT data center capacity. R. HinsleyUnderwayERCOT project PR_80001 Planning is underway for identifying and managing data center capacity to meet the overall needs of ERCOT. 3. Validate and monitor Nodal data capacity assumptions J. FloydOngoingWork in progress, with a plan to be completed by 2/3/09 ERCOT-Wide Risk:

10. 10 Nodal Program UpdateFebruary 5, 2009 Questions?