Lead from the front Texas Nodal 1 EDS 4 Release 9.2 Outage Scheduler Kickoff Meeting March 27, 2008

Lead from the front Texas Nodal 2 Agenda Outage Scheduler EDS Overview: –Presentation Legend –Objectives –Audience Outage Scheduler EDS Timeline –Nodal Summary Release Schedule –Sandbox Testing –Test Cases –Sample Activity Timeline –Testing Windows Outage Scheduler EDS Testing –Testing Window –Basic Communications Test –Digital Certificates –Support Calls –Issue Management Tracking –Master Schedule –Preparation Checklist / Schedule –Dashboard Reference –QSE Activity Summary –Relevant Documents Q&A

Lead from the front Texas Nodal 3 Presentation Legend Note: Throughout this presentation, there are several references to activities required by QSEs with Resources and TSPs on the Web Services and MIS (RUI) For convenience and clarity, the following will apply: –All activities that apply only to users of the MIS (RUI) will appear in BLUE –All activities that apply only to users of the Web Services will appear in MAROON –Activities that apply to both the RUI and the Web Services will remain in BLACK

Lead from the front Texas Nodal 4 Outage Scheduler EDS 4.9.2: Audience AMERICAN ELECTRIC POWER SERVICE CORP AMERICAN ELECTRIC POWER SERVICE CORP (SQ3) ANP FUNDING I LLC BPTX (SQ1) BPTX (SQ2) BPTX (SQ3) BRAZOS ELECTRIC POWER CO OP INC (QSE) BTU QSE SERVICES INC BTU SQ1 CALPINE POWER MANAGEMENT LP CITY OF AUSTIN DBA AUSTIN ENERGY (QSE) CITY OF GARLAND (QSE) CITY OF SAN ANTONIO CITY PUBLIC SERVICE (QSE) CITY OF SAN ANTONIO CITY PUBLIC SERVICE CPS WIND (SQ1) CONSTELLATION ENERGY COMMODITIES GROUP INC (QSE) CONSTELLATION ENERGY COMMODITIES GROUP INC B (QSE) CONSTELLATION ENERGY COMMODITIES GROUP INC C (QSE) CORAL POWER LLC CORAL POWER LLC (SQ2) DIRECT ENERGY LP Contact You should not be on this list You should be on this list but are not DIRECT ENERGY LP WTU (SQ2) EAGLE ENERGY PARTNERS I LP (QSE) EXELON GENERATION COMPANY LLC FORMOSA UTILITY VENTURE LTD (QSE) FPL ENERGY POWER MARKETING FPL ENERGY POWER MARKETING INC (SQ3) FPLE PMI (SQ1) FPLE_WIND_FPL ENERGY POWER MARKETING INC.(SQ2) FULCRUM POWER SERVICES LP IPA MARKETING INC (SQ1) LOWER COLORADO RIVER AUTHORITY (QSE) NRG TEXAS POWER LLC (QSE) OCCIDENTAL POWER SERVICES INC RELIANT ENERGY ELECTRIC SOLUTIONS (QSE) RIO NOGALES POWER PROJECT LP (QSE) SCURRY COUNTY WIND LP (QSE) STEC - SOUTH TEXAS ELECTRIC COOP (QSE) SUEZ ENERGY MARKETING NA INC TENASKA POWER SERVICES CO TRQ1 (SQ1) QSEs

Lead from the front Texas Nodal 5 Outage Scheduler EDS 4.9.2: Audience TOPAZ POWER MANAGEMENT LP (QSE) TOPAZ POWER MANAGEMENT LP (SQ1) TXU PORTFOLIO MANAGEMENT COMPANY LP (QSE) TXU PORTFOLIO MANAGEMENT COMPANY LP (SQ1) WESTAR (SQ1) Contact You should not be on this list You should be on this list but are not AMERICAN ELECTRIC POWER SERVICE CORP AUSTIN ENERGY CITY OF GARLAND CPS CITY OF SAN ANTONIO BRAZOS ELECTRIC POWER CO OP BRYAN TEXAS UTILITIES MAGIC VALLEY ELECTRIC CO OP BROWNSVILLE PUBLIC UTILITY BOARD RAYBURN COUNTY ELECTRIC TEXAS NEW MEXICO POWER TEXAS MUNICIPAL POWER AGENCY SOUTH TEXAS ELECTRIC CO OP (1) LOWER COLORADO RIVER AUTHORITY CITY OF DENTON CITY OF COLLEGE STATION MEDINA ELECTRIC COOP ONCOR ELECTRIC DELIVERY COMPANY CENTERPOINT GREENVILLE ELECTRIC UTILITY SYSTEM SOUTH TEXAS ELECTRIC CO OP (2) TSPs

Lead from the front Texas Nodal 6 EDS Sandbox testing timeline Nodal Sandbox contains External Web Services pertinent to Outage Scheduler. If you will be using the Web Services to connect to Outage Scheduler, please use the Sandbox to verify connectivity and XML structures All Outage Scheduler web services currently conform to External Interface Specification V1.10 Changes to the following services will be deployed to Sandbox on 4/1 Outage Creation Outage Cancellation Outage Query If you have any questions, please contact EDS 4 team – FebMarAprMayJun 6/13 OS Connectivity and Submission Testing 4/15 4/21 – V1.11 (approved) Nodal Sandbox - Loopback 3/21 - V1.10 4/1 - V1.11 (unapproved) Application Components EWS RUI Application Components Outage Creation Outage Cancellation Outage Query Outage Creation Outage Cancellation Outage Query EWS & RUI

Lead from the front Texas Nodal 7 EDS RUI timeline MPs will be able to perform all EDS test scenarios using the RUI starting 4/15/2008 If you have any questions, please contact EDS 4 team – FebMarAprMayJun 6/13 OS Connectivity and Submission Testing 4/15 EWSRUI Application Components Outage Creation Outage Cancellation Outage Query EWS & RUI Outage Creation (all outage types) Grouped outages Recurring Outages View Summary Edit Outage (Simple / Group) Remove items from Group Forced & Unavoidable extensions Advanced filtering Pagination Export RUI 4/156/26 Print Help Warnings Copy Outage RUI Application Components

Lead from the front Texas Nodal 8 Outage Scheduler Timeline EDS will now start on 4/15 The focus of this presentation will be primarily on EDS – OS Connectivity and Submission Testing

Lead from the front Texas Nodal 9 Outage Scheduler EDS 4.9.2: Objectives EDS Phase DescriptionPhase Objectives 9.2.1Forced Outage DetectionVerify the ability of the EMS to receive outage list from OS Verify the automation and timing of information from the OS to the EMS Verify the FOD capability of the EMS 9.2.2Connectivity / Submission test Verify MIS connectivity (if applicable) Verify EWS connectivity (if applicable) Verify MP’s ability to enter outages Verify ERCOT’s ability to approve single and group outages Verify QSE/TSP ability to receive updates on outage status 9.2.3Validation of PerformanceVerify OS ability to receive a specified quantity of data from multiple sources simultaneously via both the RUI and the EWS Verify OS data available for real-time reports 9.2.4Validation of Outage Evaluation in EDS Verify OS ability to send outage requests for the time period defined by the EMS user. Verify OS ability to receive outage status changes from the OE 9.2.5Validation of Outage Scheduler Interfaces Verify outage transfers from the OS into the DA TSA Verify outage transfers into RUC Verify outage transfers to all other uses of OS information 9.2.6Validation of Outage Postings in MIS Verify outage transfers from the OS into the MIS Validate MIS Secure Area access to Market Participants with the appropriate Digital Certificate Verify performance

Lead from the front Texas Nodal 10 Outage Scheduler EDS 4.9.2: MP Involvement EDS Phase DescriptionStartEndMP participation 9.2.1Forced Outage DetectionApr 15, 2008 May 23, 2008 Not required 9.2.2Connectivity / Submission testApr 15, 2008 Jun 13, 2008 Yes – 2 hour testing window per MP 9.2.3Validation of PerformanceJun 16, 2008 Jun 27, 2008 Yes - submit outages from 9AM – 11AM for up to 2 weeks 9.2.4Validation of Outage Evaluation in EDS Jun 02, 2008 Aug 01, 2008 Not required 9.2.5Validation of Outage Scheduler Interfaces Apr 29, 2008 Aug 01, 2008 Not required 9.2.6Validation of Outage Postings in MIS May 02, 2008 Aug 01, 2008 Yes - MPs are required to download and validate Outage Scheduler reports posted on MIS

Lead from the front Texas Nodal 11 Outage Scheduler Testing: Support Call Test Cases for Connectivity and Submission testing Create / Query / Update / Cancel Planned Outage Unavoidable extension Recurring outage Planned Outage Group Unavoidable extension Recurring outage Remedial Switching Action Forced Outage on an equipment Forced extension Opportunity Outage Maintenance Level (1, 2, or 3) on a single piece of equipment Unavoidable extension Simple Outage on an equipment Unavoidable extension Each of the outage types may require multiple outage entries to ensure we can test the entire workflow OS Submissions Test Scripts document to be posted on Readiness Center on 4/2/08 will provide further details Create / Query / Update / Cancel Planned Non-Reliability Generation Outage Unavoidable extension Planned Non-Reliability Generation Outage Group Unavoidable extension Opportunity Outage Planned Reliability Generation Outage Unavoidable extension Planned Load Resource Outage Unavoidable extension Forced Outage Unavoidable extension TSPs QSEs with Resources

Lead from the front Texas Nodal 12 Outage Scheduler Timeline: Example Activity Timeline EDS TIMELINE Example Activity Timeline

Lead from the front Texas Nodal 13 Outage Scheduler Testing: Testing Window QSEs and TSPs are required to sign up via for a testing window –This will initiate a number of events that will occur before the Testing Window (detailed in a later slide) –Testing Window includes: 2 hour support and scripted testing call Resolution of issues during the 2 hour support call 7 calendar days testing window for prioritized support and self guided testing Optional self guided testing are test scenarios that the QSEs and TSPs have defined and execute independently in the EDS environment –Scheduling your testing window early allows more time for self guided testing, make-up windows and issue resolution

Lead from the front Texas Nodal 14 Outage Scheduler Testing: Testing Window Sign-up Content The sign-up from QSEs and TSPs should include: Support Window Date and AM or PM preference –Provide primary contact details –Provide top three preferred dates with AM / PM preference –ERCOT may still need to coordinate a date outside of these 3, but will make every effort to be on one of these dates DUNS number of QSE or TSP If using Web Services, confirm that you the QSE/TSP will be engaged in testing and not your 3 rd Party Service Provider: Yes/No If using Web Services the URL where notifications will be sent Note: If this is unavailable at the time of sign up, this must be received 2 weeks prior to your scheduled testing window Send sign-up to April 4 th, 2008

Lead from the front Texas Nodal 15 Outage Scheduler Testing: Basic Communications Test (“Ping” Test) MPs testing on the Web Services for the first time will be Scheduled for a 1 Hour Basic Communications test –This test typically takes minutes if no issues are found –1 hour is allocated to address any issues –Tests performed on the call will be as follows: ERCOT performs a telnet to QSEs and TSPs Listener QSEs and TSPs performs telnet to ERCOT External Web Services Listener QSEs and TSPs send a sample transaction to ERCOT External Web Services Listener Prior to this test MPs using External Web Services will need to have their network and security teams make the following changes: –QSE and TSP Listener must be on port 443 using one of the following Certificate Authorities Verisign Thawte Entrust Equifax

Lead from the front Texas Nodal 16 Outage Scheduler Testing: Basic Communications Test (“Ping” Test) (continued….) Prior to this test QSEs and TSPs using External Web Services will need to have their network and security teams make the following changes: –QSE’s / TSP’s Outage Scheduler system must be able to access: NOTE: this SSL URL is on port 80 –Market Participants must be able to receive / send transactions to/from the following IP ranges: / / /24

Lead from the front Texas Nodal 17 QSEs and TSPs using MIS (RUI) will need to have their network and security teams make the following changes: –Market Participants must be able to receive / send transactions to/from the following IP ranges: / / /24 Outage Scheduler Testing: Basic Communications Test (“Ping” Test) (continued….)

Lead from the front Texas Nodal 18 Outage Scheduler Testing: Digital Certificates 1 digital certificate w/ a Generic Userid (NODALTEST) will be Generated for Each QSE and TSP –The MP’s USA does not need to take any action –This is the only certificate that will work in the EDS environment –This certificate will also work in the Nodal Sandbox environment –It will not work in production, MOTE, or any other ERCOT environment –The Digital Certificate will be sent to the MP USA Distribution will occur after the MP signs up for a Testing Window and Just Prior to the Support Call –(for those requiring the basic communications test, it will be sent prior to that session) All valid ERCOT issued digital certificates will continue to work in the Nodal Sandbox

Lead from the front Texas Nodal 19 Outage Scheduler Testing: Support Calls Support Calls will be held Monday – Thursday Every Week Support Calls Have 2 Time Slots available 9am – 11am and 1pm – 3pm Fridays are reserved for: –Issue Resolution –Follow-up calls –Market wide status calls Each Testing Date has up to 2 slots Available MPs must have their Outage coordinator / Operator participating in the support call. MP IT personnel should be available for support Calendar will be Posted Weekly on the Readiness Center / EDS 4 / Documents:

Lead from the front Texas Nodal 20 Outage Scheduler Testing: Support Calls (continued…) QSEs and TSPs using Web Services –Will perform all test scenarios on the web services during support call –Will perform a subset of scenarios on the RUI during the support call –Remainder of the scenarios can be tested independently by the MP through the RUI after the support call is complete –MPs must communicate to ERCOT once all test scenarios are complete –ERCOT will validate RUI submitted transactions QSEs and TSPs using the RUI –Will perform all test scenarios on RUI during the support call –Validation will take place on the support call

Lead from the front Texas Nodal 21 Outage Scheduler Testing: Issue Management Issues encountered on the Support Call will have a high priority Issues encountered during the remainder of the 7 day Test Window should be reported via the ERCOT EDS Issue Submission Form –Form is located at: –Submit form to –Internal testing will occur in parallel with all EDS activities MP issues will be logged when submitted MP submitted issues will be compared to internal defects and addressed in parallel –When completing the Issue form, provide: Web Services: the XML files used MIS User Interface: Screen Shots and/or error message Both: The detailed scenario to reproduce the issue

Lead from the front Texas Nodal 22 Outage Scheduler Tracking: Master Schedule (example)

Lead from the front Texas Nodal 23 Outage Scheduler Tracking: Preparation Checklist / Schedule This Checklist will be completed by the ERCOT PM and consolidated to the Readiness Scorecard

Lead from the front Texas Nodal 24 Outage Scheduler Tracking: Dashboard

Lead from the front Texas Nodal 25 Outage Scheduler Reference: MP Activity Summary with the information on slide 12 “Sign-up ” by April 4 Use the Nodal Sandbox functionality Download and review the Outage Scheduler Test Package –Send sample XML to ERCOT no less than 2 weeks prior to Testing Window –Make Modifications (if any) to XML’s that ERCOT provides –Prepare final XML files for Support Call Read and be Familiar with Documents on Next Slide First Friday call will take place on Apr 18 th. Refer to the ERCOT Calendar for log-in info and times. Send all questions to

Lead from the front Texas Nodal 26 Outage Scheduler Reference: Relevant Documents ERCOT Nodal Transition Plan Plan_ doc EDS 4 Approach v1.0http://nodal.ercot.com/readiness/eds4/documents/index.html EDS 4 – Outage Scheduler Handbook v1.0 EDS – Outage Scheduler Test Package (note document (s) to be posted by EOB 4/2/08) Outage Scheduler System User Guide (note document to be posted by EOB 4/2/08) EIP External Interface Specification s_specification_v1_10.zip EDS Issue Submission Form sue_submission_form.xls

Lead from the front Texas Nodal 27 Q&A / Open Forum