1 Single Entry Model (SEM) Weekly Market Call September 3, 2009 Matt Mereness

2 Antitrust Admonition ANTITRUST ADMONITION ERCOT strictly prohibits Market Participants and their employees who are participating in ERCOT activities from using their participation in ERCOT activities as a forum for engaging in practices or communications that violate the antitrust laws. The ERCOT Board has approved guidelines for members of ERCOT Committees, Subcommittees and Working Groups to be reviewed and followed by each Market Participant attending ERCOT meetings. If you have not received a copy of these Guidelines, copies are available at the Client Relations desk. Please remember your ongoing obligation to comply with all applicable laws, including the antitrust laws. DISCLAIMER All presentations and materials submitted by Market Participants or any other Entity to ERCOT staff for this meeting are received and posted with the acknowledgement that the information will be considered public in accordance with the ERCOT Websites Content Management Operating Procedure.

3 SEM Weekly Market Call Agenda Antitrust Admonition SEM Go-Live Update Reference only- –Market Testing Update –Readiness Dashboards –SEM Go-Live Criteria and Approval –FAQ/ Open Issues –Appendix/Supporting Info –What is SEM? –Go-Live timeline and activities –Training overview and sign-up –Readiness metrics related to training and testing –Communication mailbox and SEM Market Call Schedule

4 Day 4 77 NOMCRs submitted from 6 TSPs –Most concurrent users thus far is 13 –ERCOT tested over 50 concurrent connection 25 NOMCRHelp tickets opened –Most access issues resolved 1-2 days USA or MP can re-set passwords ERCOT on the phone (opt 3) –CIM File download issue Issue for at least one company to download large file ERCOT can FedEx –Ownership issues Global list sent to TSPs for changing ownership ERCOT can provide quick turnaround for certain equipment as needed –Validation Rule Questions Responding to questions Some may need to be discussed at NDSWG –Two companies had application disconnects ERCOT released patch last night, Sept 2 at 7pm Continuing to monitor

5 Training Update Training –Reminder of one make-up class scheduled so far – Sept 29-Oct 1 –Sign up using LMS - – if problems with signing up for second

6 Market Testing Update Test Sandbox Environment Update: Remains off-line during at least the first week of production Test/Sandbox system will come back for training later in September –Final date TBD

7 FAQ- Access questions Reminder- TSP USA initiates creation of NMMS account. User will receive a new user name and initial password. Please use caution when typing the new password (or removing the trailing space when pasting.) You will be prompted to change your password. If there are any issues with this initial log in, you will receive an error message. At this point, you must request a password reset. –The password can be reset by: 1) ing the ERCOT Helpdesk, or calling at option 2)Or contacting your USA – they can reset your password. To reset: in MPIM, select modify to the individual account. There is a check box to reset password. Select the box and will be sent with new password. USAs were contacted directly with instructions on how to assign the roles for SEM Go-Live Two roles are applicable for NMMS: –NMMS Remote Users (access to production environment to submit NOMCRs) –NMMS_SEMFILE_DOCS (to allow the ability for certain TSP users to download the full network CIM file)

8 NMMS Access on Aug 31, 2009 TSP TML 1)NOMCRs / SAMRs (Report Explorer) 2) CIM network file download capability 3)NMMS Production (also SOTE / MOTE) (links to Citrix Gateway) Citrix Gateway NMMS Production (also SOTE / MOTE) Each TSP Company Folder will contain all Network Model Changes Daily zip files

9 NMMS Access on Aug 31,

10 Roll-call and Q&A Roll-call Production environment URL –URL- Important Reminder(s): –Production issues should be sent to and –Re-set password can come from HelpDesk or your USA –Make up training class Enroll at –Populated CIM file request (8/31/09 Go-Live Model) Posted in TML Production 8/31 Questions and Answers Next Weekly Market Call- Sep 10, 2009

11 Appendix/Supporting Info –What is SEM? –Readiness Criteria –Go-Live timeline and activities –Training overview and sign-up –Dates/ methods to test submissions of NOMCRs

12 SEM Go-Live Overview Single Entry Model (SEM) Go-Live is the switchover on Aug 31, 2009 for TSP submissions of network operations model change requests –from “Service Request” submissions via TML –to “NOMCR” submissions via the NMMS System of record for model changes becomes NOMCRs on 8/31//09 System of record for Network operations Model for reliability and dispatch remains Zonal/Genesys system until Dec 2010 TSP Current Activity Submit Modeling Change via Service Request ERCOT Uploads Svc Request into Zonal Genesys Model ERCOT Copies/Converts Zonal Model “seed” Into Nodal NMMS Model TSP Aug 31, 2009 Submit Modeling Change via NOMCR/NMMS Tool (includes ICCP) ERCOT Incrementally Converts NOMCR Into Svc Req Uploads into Zonal Genesys Model ERCOT uploads NOMCR Into Nodal NMMS Model to support nodal testing Data Consistency Checks are run to ensure model synchronization/fidelity Periodic checks are run to ensure model synchronization/fidelity Full Copy Incr. NOMCR

13 Current Network Operations Model Maintenance for TSPs ERCOT Zonal EMMS Model (system of record through 12/1/2010) Submits Service Request to Change Model ERCOT Nodal NMMS Model (nodal testing model- CIM file for EMS/MMS/etc) Periodic full copy and conversion of model (zonal seed used for nodal systems) TSP

14 After 8/31/2009: SEM Go-Live Network Operations Model Maintenance for TSP ERCOT Zonal EMMS Model (system of record through 12/1/2010) ERCOT Nodal NMMS Model (nodal testing model- CIM file for EMS/MMS/etc) ERCOT enters NOMCRs into zonal model ERCOT runs consistency checks to ensure models are aligned and maintained Submits Model Change Request (NOMCR) TSP NMMS Model System of Record Nodal Go-Live 12/1/2010

15 Network Operations Model Maintenance for Resource & QSE (today and post 8/31/09) ERCOT Zonal EMMS Model (system of record through 12/1/2010) ERCOT Nodal NMMS Model (nodal testing model- CIM file for EMS/MMS/etc) ERCOT enters into zonal model NMMS Model System of Record Nodal Go-Live 12/1/2010 Submits RARF (Resource Asset Reg Form) via Service Request Submits ICCP Change via Service Request ERCOT process QSE RE

16 SEM Go-Live Market Engagement Dashboard (as of 8/27/2009) Notes- ERCOT working one TSP to catch-up on final testing/training - TSP has signed up for Sep 29 th make-up training - ERCOT will support this TSP (and any other TSP) with assistance in submission of NOMCRs

Overall SEM Go-Live ERCOT/Market Criteria Dashboard Summary of Criteria from TAC-approved SEM Go-Live Procedure ( )

18 Go-Live timeline and activities (continued) Communication –May 6 th ERCOT began TSP outreach through Wholesale Client Services TDSP/TO associations sent to 23 TOs Solicit training headcount from TOs (pre and post Go-Live) Good response from TOs

19 Go-Live timeline and activities (continued) Communication and Calendar –May 15- Market Notice sent for SEM Kick-off call to occur –May 28- SEM Kick-off WebEx 10:00-11:30am Go-Live timelines and activities for June - August 2009 Training overview and sign-up Dates and access methods to test submissions of NOMCRs Readiness metrics related to training and testing Communications mailbox and SEM market call schedule –June 4- Start weekly Thursday SEM Calls at 2-3pm (through go-live/August) Company attendance is recorded ERCOT provide updates on testing and training Highlight issues or Frequently Asked Questions Open Question/Answer session for TSPs Meetings will be posted on ERCOT calendar at –June 8- Testing environment available to TSPs (through Aug 10) –June 22- Weekly classroom training for 6-weeks (through July 30)

20 Training Overview and Sign-Up (continued) Classroom schedule for the 3-day class One class per week for 6 weeks Start 1pm Tuesday / End noon Thursday Trainees can stay in Lab Thursday afternoon for Q&A If schedule fills up, ERCOT will shorten class to 2-days for the overbooked weeks June 23-25, June 30- July 2 July 7- 9, 14-16, 21-23, Next 4 slides show summary of training format and equipment Full training outline in Appendix (no change from last month) Note that testing/training will only include Level 1 Validation Level 1 – Automatic by the system upon submitting. Level 2 – Visual by the N/W Model Coordinator Level 3 – Power flow run on the one NOMCR. Level 4 – Power flow run on all NOMCRs for that day. Level 5 – Power flow run on the AREVA system.

Training (continued)

25 Training Overview and Sign-Up (continued) Sign-up for access to test environment starts today System access begins June 8 th request to Test environment requires a valid digital certificate (production or nodaltest) -Digital certificates are to be coordinate with your company’s USA -Include in Employee Name- TSP/Company Name- DUNS- address- Alternate/Centralized address for status change- Primary phone- Alternate phone-

26 Open Issues / Responses How can I configure Citrix to allow me to export/import CIM files? Steps: 1)While Citrix and the application are open, there should be a Citrix icon in your taskbar (the ‘Citrix Connection Center’) 2)Double click the icon 3)Click ‘File Security’ 4)Click ‘Full Access’

27 Go-Live timeline and activities (continued) –Transition periods: June 1- Aug 30, 2009 (objective to minimize SvcReq during this period) –Submit changes as far in advance as possible –No equipment name changes (defer until after SEM Go-Live 8/31/09) Aug 15-30, 2009 –Two weeks no submissions, except for emergency changes Aug 31, Feb 2010 (NOMCRs for any/all network changes) –After 8/31/09 TSPs will work to validate the network model and align to their in-house systems –Initially the NOMCR timeline will align with zonal timeline »30-day lead-time, compliant with current zonal database schedulezonal database schedule »Status is tracked and communicated via system s –Any SRs that did not go into zonal production will be converted by ERCOT to NOMCRs for verification/submission by TSPs in Sept –In 2010 TSPs gradually transition to NodalProtocols(3.10) 90-day timeline submission requirements