Nodal Update for: Single Entry Model (SEM) Go-Live Transition

1. Nodal Update for:Single Entry Model (SEM)Go-Live Transition NDSWG April 21, 2009 Matt Mereness http://nodal.ercot.com 1

2. SEM Go-Live Transition Update General review of SEM Transition Communications with stakeholders SEM Go-Live Criteria Processes/Submissions during June-Aug’09 transition Training Update Metric Discussion (NOMCR training & submission) RARF Discussion http://nodal.ercot.com 2

3. General Review of SEM Transition 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 TSP Current Activity TSP Aug 31, 2009 Submit Modeling Change via Service Request Submit Modeling Change via NOMCR/NMMS Tool (includes ICCP) ERCOT Uploads Svc Request into Zonal Genesys Model ERCOT Copies/Converts Zonal Model “seed” Into Nodal NMMS Model ERCOT Incrementally Converts NOMCR Into Svc Req Uploads into Zonal Genesys Model ERCOT uploads NOMCR Into Nodal NMMS Model Full Copy Incr. NOMCR Data Consistency Checks are run to ensure model synchronization/fidelity Periodic checks are run to ensure model synchronization/fidelity http://nodal.ercot.com 3

4. General Review of SEM Transition (cont’d) The processes and approvals leading up to this activity were outlined in the SEM Go-Live Procedure approved by TPTF and TAC in Aug/Sep 2008 http://nodal.ercot.com/readiness/golive/index.html In the coming months ERCOT will continue to provide updates to NDSWG and ROS on details of the implementation and switchover activities. All nodal presentations to NDSWG continue to be consolidated and posted on Nodal Readiness Center: http://nodal.ercot.com/readiness/eds2/documents/index.html http://nodal.ercot.com 4

5. General Review of SEM Transition (cont’d) • ERCOT is utilizing NDSWG forum to update and communicate TSP activities for Single Entry Model (SEM) Go-Live http://nodal.ercot.com 5

6. Communications with Stakeholders http://nodal.ercot.com 6

7. Communications with Stakeholders (cont’d) http://nodal.ercot.com 7

8. SEM Go-Live Criteria • SEM Go-Live Criteria defined in the SEM Go-Live Procedurehttp://nodal.ercot.com/readiness/golive/index.html • Section 4- The following entry criteria shall be met for SEM Go-Live • TSPs & ERCOT complete EDS 2 Release 4 activities (next page) • Nodal network model validated and approved as baseline for SEM Go-Live by ERCOT System Ops and Market Ops Directors • ERCOT publishes CIM model to be used for SEM Go-Live • ERCOT sufficiently staffed for maintenance of nodal & zonal systems • Nodal EMS is capable of consuming NMMS CIM files through the EMS CIM importer for use in the Nodal EMS application suite • SEM Go-Live readiness approved by TPTF, TAC and ERCOT BOD • presume ROS approval in place of TPTF • ERCOT publishes the following documents for TSPs • ERCOT Network Operations Model validation whitepaper • ERCOT Network Operations Model validation results • NMMS Modeling Guidelines / Validation Rules document • Latest CIM data dictionary and schema http://nodal.ercot.com 8

9. SEM Go-Live Criteria (cont’d) • All TSPs complete EDS 2 Release 4 activities • MPs have enrolled and can access the ERCOT MIS portal • MPs have been trained on the NOMCR process • TSPs can electronically submit data changes utilizing the NOMCR user interface and CIM compliant format for data exchange or via the manual MIS NOMCR process • QSEs can submit data changes utilizing the registration submission and subsequent ERCOT NOMCR process • MPs can receive NOMCR acknowledgement of submittals, verifications, and confirmation of data posting • ERCOT completes EDS 2 Release 4 activities • ERCOT is ready to fully utilize the NOMCR process for all TSP/QSE data change requests • TSP MPs can successfully submit data changes via the CIM compliant electronic NOMCR process. • QSE can successfully submit data changes through registration submissions (and updated in the Network Operations Model via the NOMCR process) • ERCOT has processes in place to use a “single entry point” to maintain both Nodal and Zonal network model databases when MPs submit changes via the NOMCR process • NMMS is the database of record for the Network Operations Model including the ICCP modeling point database and operatorship / ownership information • NMMS database is under full change control by ERCOT Network Model Group • ERCOT discontinues the use of Service Requests for data changes and change control • ERCOT begins the use of the NOMCR process for data changes and change control http://nodal.ercot.com 9

10. Processes/Submissions during June-Aug’09 transition • Currently no limits on submissions (Market Notice sent March 5) “… to clarify that there are no restrictions or “freezes” currently in place limiting network model change submissions via the service request process.” • Transition periods: • June 1- Aug 30, 2009 (objective to minimize SvcReq during this period) • No equipment name changes (defer until after SEM Go-Live 8/31/09) • Submit changes as far in advance as possible • Aug 15-30, 2009 • Two weeks no submissions, except for emergency changes • Aug 31, 2009 - Feb 2010 (NOMCRs for any/all network changes) • Initially the NOMCR timeline will align with zonal timeline • NOMCRs received and translated to zonal model change • 30-day lead-time, compliant with current zonal database schedule • Status is tracked and communicated via system emails • SRs that did not go into zonal production will be converted to NOMCRs for verification and submission by TSPs in Sept • TSP gradually transitions to NodalProtocols(3.10) 90-day reqts http://nodal.ercot.com 10

11. Training Update • TSP Testing and Training environments will be the same • Testingsystem access • Available June 8 – Aug 10 • NOMCR testing system will be on-line and available to all TSPs • ERCOT will establish dedicated email and have staff available to support questions (nomcrhelp@ercot.com) • Existing “NMMS Sandbox” will be replaced in coming weeks • Trainingto be hosted in Taylor • Pre-SEM classes June 22 – Aug 3 • Current plans for at least six 2-day sessions • Planning for 12-18 seats for each class • Large dedicated training room • Post-SEM classes Sept 23- Oct 20 • Fewer sessions and smaller classes (tbd) • Make-up classes, not just-in-time training for all staff after go-live http://nodal.ercot.com 11

12. Training Update (continued) • Training content outline has not changed significantly and is in the Appendix • Invitation to contribute to content ideas/scenarios • email astorey@ercot.com with suggested attributes for modeling training • Market Notice to be sent in April to all TSPs (70+) for training engagement • TSP responses being requested for: • Confirmation of notice • Estimated number of trainees (pre-SEM and post-SEM classes) • Alternative arrangements (agency or consulting arrangements) http://nodal.ercot.com 12

13. Metric Discussion For MPs, two metrics will be assessed during SEM Go-Live: MP14 – B – MP EDS-2, Release 4 Trials Participation Metric inventory posted at: http://nodal.ercot.com/readiness/metrics/index.html http://nodal.ercot.com 13

14. Metric Discussion (continued) MP13 – MP Completes Nodal Operations Related Training http://nodal.ercot.com 14

15. RARF Discussion • NDSWG and ROS discussion regarding access to RARF data • Resource Asset Registration spreadsheet files are submitted by Resource Entities via a Service Request (this will not change in Nodal) • Concern expressed in ensuring RARF data is properly in ERCOT systems • At ERCOT the RARF data is entered into a Database “Hub”, and sourced to zonal and nodal downstream systems: • Registration / Network Models / EMS / MMS / others. • Resource Entities: • RE can request that ERCOT reproduce the RARF from the “Hub” system and send to RE’s to reflect what data ERCOT has on file • RE (and all MPs) will be able to download the Nodal Network Operations Model / CIM file which includes Resource Entity RARF data • Network Operations Model - A representation of the ERCOT System providing the complete physical network definition, characteristics, ratings, and operational limits of all elements of the ERCOT Transmission Grid and other information from TSPs, Resource Entities, and QSEs. • RE’s will not have access to NMMS modeling tools http://nodal.ercot.com 15

16. Questions Questions or comments can be submitted to: eds2@ercot.com mmereness@ercot.com http://nodal.ercot.com 16

17. Appendix APPENDIX (Training Outline from March NDSWG) http://nodal.ercot.com 17

18. General Information • What: NMMS Application training • Who: TSPs who submit model data changes • When: June 22, 2009 – Aug 3, 2009 • Where: ERCOT Taylor • How long: Estimated 2 days

19. Course Objectives: • To give course participants: • … a working level understanding of the time-line, participants, transition tasks, roles and responsibilities associated with the SEM go-live • … a review of the basics of the ERCOT modeling process Cont…

20. Course Objectives cont.: • … proficiency in the handling of the “life of a NOMCR / SAMR” – understanding the process. This involves: • Project Tracker & Coordinator entry • NOMCR creation • Model updates • IMM changes • Upload CIM XML • Validations & submissions • Status notifications • Additional features (history, archive, comments, filter, name mapping)

21. Course Agenda Section 1: Introduction – Basics Review Section 2: SEM highlights for transition Section 3: NOMCR Creation (PTC) Section 4: Modeling Overview Section 5: A day in the life of a NOMCR Section 6: Modeling Exercises Section 7: Wrap Up

22. Section 1: Introduction – Basics Review • Course Openers – Welcome, Objectives, Course Structure • ERCOT Models – General, What gets modeled, Typical Attributes, The Network Operations Model, Derivative Models (Planning & CRR) • The Operations Model: What’s Changing & Why it’s Changing. Roles and Responsibilities. The SEM Process – basics. • Overview of the Change Submittal Process: The NOMCR & The SAMR • Overview of the Change Submission User Interfaces: PTC and IMM

23. Section 2: SEM highlights for transition • What is SEM? • SEM Transition and Schedule • SEM Pre Go-Live– Objectives and responsibilities • SEM Go-Live– Actions during process • SEM Post Go-Live - Actions

24. Section 3: NOMCR Creation (PTC) • Project Tracker & Coordinator login and interface – Log-in, NOMCRs, SAMRs, the interface, Visibility states (public or private) • Hands-on exercise: NOMCR Creation

25. Section 4: Modeling Overview • Background on (ERCOT CIM) Network Operations model • Overview of Modeling • Validation Rules/Process • Small hands-on activity (create, validate, and submit NOMCR)

26. Section 5: A day in the life of a NOMCR • State Diagram Introduction – What it is and how to use it • Definition of Terms - Walk-through of terms MPs will see: • Explanation of the Status Table • NOMCR Timelines – Including Interim Update provisions • Walk through State Diagram – from a TSP and ERCOT perspective • Exercise – based on flow process

27. Section 6: Modeling Exercises • The entry of a NOMCR using scripted scenarios • Usage of the Modeling Guidelines document • Additional topics, as identified by course participants

28. Section 7: Wrap Up • Discussion of any remaining items. Closing comments