1 / 70

Market Trials Release 2.1 Market Participant Connectivity Testing

Market Trials Release 2.1 Market Participant Connectivity Testing. Kick Off Meeting. October 8, 2009. Antitrust Admonition. ANTITRUST ADMONITION

henrysmiller
Download Presentation

Market Trials Release 2.1 Market Participant Connectivity Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Market Trials Release 2.1 Market Participant Connectivity Testing Kick Off Meeting October 8, 2009 http://nodal.ercot.com 1

  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. http://nodal.ercot.com 2

  3. Agenda • Nodal Release 2.1 Kick-Off • Release 2.1 Connectivity Testing Objective and Scope • Nodal Production Environment • ERCOT Support • Access / Location • Common Information Model / Data Set • Communications Plan / Issue Management • Handbook Overview • Market Participant Web Service and User Interface Qualification • Voluntary, Early Re-Qualification • Mandatory Qualification Window • New Participant Qualification • Dashboard • Overview of the Market Manager User Guide • Overview of the EIS (External Interfaces Specification) • Focused Input Testing (FIT) Windows and Telemetry Data Quality • Market Trials 2010 Roadmap http://nodal.ercot.com 3

  4. Schedule Overview 2009 2010 MAR APR MAY JUN JUL AUG SEP OCT NOV DEC JAN FEB MAR Telemetry and SE Focused Input Testing (Telemetry and SE) Sandbox v1.19 Submission Testing SCED & DAM Release 2.1 QSE Connectivity Testing Publishv1.19 Limited Nodal ProductionReleased to Market MP Nodal Re-qualification Remaining RE’s Transmission asset registration Resource Registration PUNS Transmissionasset registration Integrated Market Trials Roadmap Verifiable Costs Submission of Verifiable Costs for Resources (different dates for technologies) Training on NOMCR Make-up sessions Network Model SEM Go-Live Milestone TSP model synchronization COMS Extracts User Guide release Reporting NDSML and extract supporting documentation updates http://nodal.ercot.com 4 http://nodal.ercot.com 4

  5. Release 2.1 Connectivity Testing Objective and Scope On October 28, 2009, ERCOT will perform a limited release of the Nodal Production environment to support the defined scope of Market Trials 2.1 Market Participant Connectivity Testing • Objective of Release 2.1 • Provide an environment for Market Participants to test core submissions over the ERCOT web services and Market Manager User Interface • Allow ERCOT to perform an incremental build-out of the Nodal Production environment in preparation for full Market Trials in 2010 • Continued improvement of established QSE and TSP telemetry data quality http://nodal.ercot.com 5

  6. Release 2.1 Connectivity Testing Objective and Scope • Scope of the 2.1 MMS (Market Management System) release will be limited to the following transactions and Phase 1 validations (which are detailed in the Explanation of Market Submission Items document found at http://nodal.ercot.com/readiness/mt21/index.html): • Real-Time • Current Operating Plan • Energy Offer Curve • Output Schedules • Incremental/Decremental Offer Curves • Day-Ahead / Other submission • Three Part Offers • Ancillary Service Offers • Energy-only Offers and Bids • Trades (Energy, Ancillary Service, Capacity) • Self-Arranged Ancillary Services • CRR Offers • PTP Obligation Bids • Self Schedules • DC Tie Schedules • Resource Parameters http://nodal.ercot.com 6

  7. Release 2.1 Connectivity Testing Objective and Scope (continued) • Continued support for 2.1 release are the bi-weekly (FIT) Focused Input Testing windows • These will continue along with the Nodal Telemetry Outreach program • The Nodal Telemetry Outreach program’s objective is to continue to resolve issues and improve data quality for State Estimator and, eventually, SCED solutions http://nodal.ercot.com 7

  8. Release 2.1 Connectivity Testing Objective and Scope (continued) • Out of Scope (not limited to the following) : • Other functionality (e.g. outage scheduling, getReports, etc) • Although other systems and features may be included in the release, ERCOT continues to perform testing on these and will not be supported • MMS generated notices (e.g. Phase 2 validation notices) • ERCOT may release some MMS generated notices to the environment. These should be ignored by MP’s until ERCOT attests that they are supported • Real Time Market (SCED) and Day Ahead Market: • The Nodal Production environment may be leveraged on unsupported days* to run markets in test mode only, however, these will not be run in a supported or market facing capacity. • Note that in cases where one or both of these markets are run during 2.1, ERCOT will likely use system generated inputs from lower testing environments. • To avoid market timeline limitations associated with DAM/Phase 2 validation, ERCOT recommends that all test submissions be for current day +2 (e.g. submissions made on a Tuesday shall be for Thursday’s trade date) http://nodal.ercot.com 8

  9. Nodal Production Environment - ERCOT Support • Nodal Production Environment Status • Release 2.1 is an early release of the Nodal Production Environment • ERCOT continues to perform Integration and Performance Testing • It is expected that issues will be found during 2.1 by both, ERCOT and the Market Participants The following bullets detail ERCOT’s support plan for this phase, recognizing the primary environment goal of this phase of Market Trials is system connectivity for Market Participant’s development and testing, not performance or data retention • Support Windows • The Market Trials 2.1 environment will be actively supported Tuesday through Thursday, from 9:00 am to 6:00 pm • The Nodal Production environment will remain accessible outside of these support windows, however there is no guarantee of system stability or accessibility • ERCOT will utilize unsupported time periods to perform system maintenance, planned / unplanned releases as well as performance testing • Transactions submitted to ERCOT may be periodically deleted outside of supported windows http://nodal.ercot.com 9

  10. Nodal Production Environment - ERCOT Support • Outage and Restoration • In the event of an outage or significant degradation in performance during an active support window, ERCOT will send a market notice followed by periodic status updates as they are available. • The expected restoration time for outages will be on a ‘as soon as possible’ basis Note that planned outages outside the active support window will be communicated as appropriate on a bi-weekly basis during the Friday Market Participant calls. http://nodal.ercot.com 10

  11. Nodal Production Environment – Access / Location • Following are the URL’s to be used during Connectivity Testing • Market Manager User Interface:https://mis.ercot.com/mmsui/mmsui/displayTradesLanding.action • Web Services Endpoint:https://misapi.ercot.com/2007-08/Nodal/eEDS/EWS • Authentication • Users that currently have an ERCOT production digital certificate, will continue to use this certificate in the Nodal Production Environment • Users that do not have an ERCOT production digital certificate should request one from their company’s USA (User Security Administrator) • New Market Participants will obtain certificates via the ERCOT registration process • Authorization (Roles) • On August 28th, 2009, ERCOT released Nodal Roles to the production MPIM (Market Participant Identity Management) system • Market Participant USA’s must assign the appropriate role to users that will be testing in the Nodal Production environment • See next slide for a list of Nodal Roles http://nodal.ercot.com 11

  12. Nodal Production Environment – Access / Location • Authorization (Roles) – continued • Listing of Nodal Roles (green = required for 2.1 connectivity testing): • Note that certificates to be used for the Web Services Interface need to have the API Certificate checkbox checked http://nodal.ercot.com 12

  13. Nodal Production Environment – Common Information Model / Data Set • Release 2.1 Network Model / Common Information Model (CIM) • ERCOT will update the CIM for the 10/28 release • This version of the CIM will reflect data as of 9/14/09 • Settlement Points and Market Participant Short Names extracted from the 9/14 CIM have been posted to the Release 2.1 readiness center:http://nodal.ercot.com/readiness/mt21/index.html http://nodal.ercot.com 13

  14. Communications Plan / Issue Management • Bi-weekly Conference Calls: • ERCOT’s primary tool for communicating updates, status and general information will occur on the bi-weekly Friday Market Trials Market Call. • Information on how and when to attend these conference call / WebEx sessions is posted here: http://www.ercot.com/committees/nodal/eds/ • Emails / Phone Calls to Individual Market Participants: • All communication regarding Market Participant – specific information will be routed through the Nodal Project Manager as identified in the Nodal Market Contacts spreadsheet • A copy of that spreadsheet may be found at: http://nodal.ercot.com/readiness/notices/2009/09/11/09112009_nodal_updating_nodal_contact_information.doc • If you wish to view what contacts are currently on file, please send an email to nodalmarkettransition@ercot.com to request populated version of the spreadsheet. http://nodal.ercot.com 14

  15. Communications Plan / Issue Management • Emails to ERCOT: • At any point during the testing questions can be emailed to eds3@ercot.com • Release 2.1 Readiness Center Website • The Nodal Readiness Center will continue to be leveraged for any required documents MP’s will need to reference • Currently posted to the Release 2.1: • MMS - Explanation of Market Submission Items v0.26 • Market Participant Short Names • Settlement Points as of 9/14/2009 • Market Connectivity Testing MP Handbook • Market Manager User Guide • Phase 2.1 Testing – Known Issues • Release 2.1 Readiness Center URL:http://nodal.ercot.com/readiness/mt21/index.html http://nodal.ercot.com 15

  16. Communications Plan / Issue Management • Issue Management – Market Participant Discovered Issues • Market Participants will report all issues using the eds3@ercot.com distribution • ERCOT will perform triage and determine root cause • If determined to be a variance / defect, ERCOT will leverage our existing defect management process to estimate, analyze and prioritize the resolution • Additionally, for Release 2.1, ERCOT will maintain a known issues spreadsheet on the Nodal Readiness center • Will be updated every Friday by EOB (note that if no new known issues are discovered, the spreadsheet will remain static) • Will only detail those issues affecting the scope of Release 2.1 and any work-arounds available to avoid issues • Will be posted and maintained at: http://nodal.ercot.com/readiness/mt21/index.html • Known issues will be added as a standing agenda item on the bi-weekly Market Trials Market Call http://nodal.ercot.com 16

  17. Communications Plan / Issue Management • Issue Management – ERCOT Discovered Issues • Issues discovered by ERCOT will follow the same process • As previously stated, ERCOT will only communicate those issues affecting the scope of 2.1 • As we near the next major release, ERCOT will begin to report on issues affecting that scope as well http://nodal.ercot.com 17

  18. Market Participant Web Service and User Interface Qualification • ERCOT will qualify QSEs based on their proven ability to submit, query and cancel the specified market transactions • QSE w/ Resources: Web Services • QSE w/o Resources: Web Services or Market Manager • Voluntary, early re-qualification / qualification • QSEs may elect to qualify early from Oct 28 – Dec 04 • If interested, send an email to eds3@ercot.com • Mandatory qualification will take place between Jan. 4, 2010 and Jan. 28, 2010 http://nodal.ercot.com 18

  19. Market Participant Web Service and User Interface Qualification • QSEs who completed qualification during the 2007/2008 market trials: • Will self-qualify and are not required to conduct a two-hour conference call with a member of the Market Trials testing team. • Self-qualification will consist of completing a transaction checklist (see sample – next slide) stating the date / time of each submittal • Send completed checklists to eds3@ercot.com for verification • New QSEs (since 2008) • Will qualify during a conference call with the Market Trials team • These QSE’s will be able to pose questions and be supported through the conference call • Typical conference call will last 1 – 2 hours • QSEs that have qualified previously may exercise this conference call as an option http://nodal.ercot.com 19

  20. Market Participant Web Service and User Interface Qualification • Sample checklist: • Note that the far right column details who that transaction applies to • Blank cells indicate that transaction applies to all QSE’s • Qualification will be tracked via a dashboard posted weekly tohttp://nodal.ercot.com/readiness/mt21/index.html • Note that CRR and Outage Scheduling qualification will be tracked separately • These will be detailed in the applicable handbooks. http://nodal.ercot.com 20

  21. Market Manager User Guide Walk-Through • Market Manager has been completely redesigned since 2008 Highlights: • Client side validation • Submission success message displayed on screen (do not have to retrieve on the notices tab) • Additional features such as ‘query for existing submission’ prior to creating new submission • Read-only role available • New copy/paste functionality • Wild-card search • User Guide has been posted: http://nodal.ercot.com/readiness/mt21/index.html http://nodal.ercot.com 21

  22. This version of the User Guide will cover: System Requirements Common System Features General Navigation Refresh Button Copy Tool Trades Confirmed/unconfirmed Trades Create, update cancel or confirm Energy, Capacity and AS Trades Resource-Specific Submissions Create and update a COP Create, update and cancel a Three-Part Offer Create, update and cancel an Output Schedule Create, update and cancel an AS Offer Create, update and cancel an Inc or Dec Energy Offer Curve Bids and Offers Create, update and cancel DAM Energy-Only Offer Create, update and cancel a CRR Offer Create, update and cancel a DAM Energy Bid Create, update and cancel a PTP Obligation Bid Schedules Create, update and cancel Self Schedule Self-Arranged AS Create, update and cancel Self-Arranged AS Resource Parameters Notices * Verbal Dispatch Instructions (VDIs) * Market Manager User Guide Walk-Through * NOTE: These items, while covered in the User Guide, will not be supported during this phase of market trials. http://nodal.ercot.com 22

  23. Market Manager User Guide Walk-Through • Market Manager defaults to the Trades landing page, where you can query for trades or create new ones http://nodal.ercot.com 23

  24. Market Manager User Guide Walk-Through If there are initial errors with your submission, you will be informed in red on the page. Correct and resubmit. http://nodal.ercot.com 24

  25. Market Manager User Guide Walk-Through After submitting, the status is displayed and highlighted on the page. http://nodal.ercot.com 25

  26. External Interfaces Specification External Interfaces Specification document describes how to interact with ERCOT using machine-to-machine interface • v1.19 posted on the Readiness Center at http://nodal.ercot.com/readiness/sandbox/documents/index.html • Content/organization of document • Services Organization • Market Transaction Service • Market Information • Notifications • Acknowledgement of Alerts • Outage Scheduling Interfaces • Utility Interfaces • Reports • Resource Parameter Transaction Service • Registration Interfaces • Verbal Dispatch Instructions http://nodal.ercot.com 26

  27. Focused Input Testing (FIT) Windows and Telemetry Data Quality 1/6/2020 http://nodal.ercot.com 27

  28. Focused Input Testing (FIT) Windows and Telemetry Data Quality • Discussion Topics: • FIT Windows • Background / Recent Changes / Remaining FIT Windows • Nodal Telemetry Outreach • Background • FAQ • The ERCOT timeline for requesting telemetry • Telemetry Resources and Links • Appendix Section • Examples of TSP/QSE reports for Nodal Telemetry Outreach emails • A breakout of SE and SCED telemetry as required by the ICCP Handbook • Telemetry Issue Resolution and ICCP Change Process Diagrams 1/6/2020 http://nodal.ercot.com 28

  29. FIT Windows • FIT Windows – Background: • The FIT III series provides bi-weekly testing windows featuring support during Business Hours to evaluate overall telemetry quality and State Estimator (SE) convergence rates. The objective of FIT windows is to measure the ability of ERCOT and Market Participants (MP) to maintain the quality of telemetry achieved to date and to carry it forward into Market Trials. • The current FIT III Series of tests began in February 2009 and is currently scheduled to run through December 2009. • Market Notices are distributed prior to each FIT window to confirm upcoming test dates and telemetry requirements. 1/6/2020 http://nodal.ercot.com 29

  30. FIT Windows • FIT Windows – Recent Changes to FIT Testing: • ERCOT discontinued making ERCOT-side Manual Replacements (MRs) on September 10 during the FIT III Week 15 window (Sept 8 – 10). • The ERCOT SE continued to solve during the testing hours with convergence rates comparable to those achieved during previous FIT windows. Factors contributing to this success included: • SE code enhancements • ICCP updates submitted by MPs • Robustness of the SE software • The SE convergence performance on Sept 10 promotes confidence that the SE software has matured to a point that ERCOT may continue to conduct future FIT windows without the need to facilitate SE solutions via ERCOT-side MRs. 1/6/2020 http://nodal.ercot.com 30

  31. FIT Windows No ERCOT-side Manual Replacements were made on these test days. 31 1/6/2020 LFC

  32. FIT Windows • FIT Windows – Remaining 2009 Dates: • The current FIT III Series is scheduled to run through Dec 2009. • In January 2010, daily telemetry support during Business Hours begins. * Note: FIT III, Wk 22, was cancelled (previously scheduled for Dec 15 – 17). http://nodal.ercot.com 32

  33. Nodal Telemetry Outreach • Nodal Telemetry Outreach – Background: • ERCOT began a Nodal Telemetry Outreach on August 31, 2009 to help MPs to correct Nodal telemetry issues in time for 2010 integrated Market Trials. • Regularly occurring email communications began the week of Oct 5. • Emails being sent to MP Technical Contacts and Nodal Accountable Executives: • Email distributions will be announced via nodal market notices. • Email distributions will be coordinated to align with FIT windows through Dec 2009. In 2010, emails will continue to be distributed on a regular basis and coordinated around nodal production-environment loads and Readiness Scorecard refreshments. • Emails will initially focus on missing nodal telemetry but will eventually address data-quality issues as well. http://nodal.ercot.com 33

  34. Nodal Telemetry Outreach • FAQ: What is included in a Nodal Telemetry Outreach email? • For QSEs, emails include: • A report of the remaining analog and status values that need to be provided for nodal • For TSPs, emails include: • A report of the remaining analog and status values that need to be provided for nodal • One lines as needed to communicate critical measurements required for observability • Examples have been provided in the Appendix section. http://nodal.ercot.com 34

  35. Nodal Telemetry Outreach • FAQ: What telemetry is being requested? • Nodal Telemetry Outreach emails will request TSPs/QSEs to submit all nodal telemetry as required by the ERCOT Nodal ICCP Communication Handbook. • FAQ: When is this telemetry required? • Although all nodal telemetry identified in the ICCP Handbook is required and MPs are encouraged to submit it as soon as possible, ERCOT will take a phased approach in requesting it. • Through Dec 31, 2009, ERCOT will request that MPs send the telemetry that is required to support State Estimator testing during FIT windows. • Starting in Jan 2010, ERCOT will request that MPs send all other required telemetry in support of SCED. • For any MPs who are able to send ICCP data early for SCED, ERCOT is requesting that they provide it during the remaining 2009 FIT windows so that it may be used in ERCOT’s nodal ITEST environment to better assess the quality of the SCED solution prior to Market Trials. http://nodal.ercot.com 35

  36. Nodal Telemetry Outreach FAQ: Which telemetry is required for SE and which is required for SCED? • For QSEs, the telemetry required for SE includes: • Gross & Net Power Flow (MW/MV) • Breaker & AVR Status • All other telemetry required from QSEs will be requested to support SCED. • For TSPs, the telemetry required for SE includes: • All TSP telemetry identified in the ICCP Handbook. • A breakout of SE and SCED telemetry required by the ICCP Handbook has been provided in the Appendix Section. http://nodal.ercot.com 36

  37. Nodal Telemetry Outreach • FAQ: Which additional SCED telemetry is being requested for nodal ITEST prior to Jan1? • ERCOT is requesting additional ICCP data from any MPs who are able to provide it early (i.e., prior to Jan 1) to support SCED testing in ERCOT’s ITEST environment, including: • This data will be used to support SCED testing, although it is being requested during FIT windows to leverage existing times when ERCOT and MP staff are known to be available to vet telemetry issues. http://nodal.ercot.com 37

  38. Nodal Telemetry Outreach Nodal Telemetry Outreach – The ERCOT timeline for requesting telemetry: • NTO Emails Begin • Week of Oct 5: • ERCOT will begin email distributions to support the Nodal Telemetry Outreach. • SCED Telemetry is Required: • Starting Jan 2010: • MPs will submit SCED telemetry. • ERCOT will use SCED telemetry for metric measurement on the Readiness Scorecard. • Remaining issues are addressed: • From Feb 2010 forward: • ERCOT will continue the Nodal Telemetry Outreach as needed to help address remaining telemetry issues. • SE Telemetry is Required: • From Nov to Dec 2009: • MPs will send SE telemetry to meet FIT requirements and will send SCED telemetry if able. • ERCOT will use SE telemetry for metric measurement on the Readiness Scorecard and will use any available SCED telemetry to support ITEST. http://nodal.ercot.com 38

  39. Nodal Telemetry Outreach • Nodal Telemetry Outreach – Final Points: • The ERCOT Advanced Network Applications, ICCP, Client Services, and EDS teams have scheduled a series of weekly internal meetings through the end of 2009 to continually discuss outreach progress and coordinate follow-ups with MPs. • As the telemetry outreach effort progresses, the quality of measurements used in each SE solution is expected to improve, along with overall confidence in SE solutions. • Information regarding the outreach effort and upcoming FIT windows will continue to be communicated via market notices, stakeholder meetings, and the regularly scheduled EDS market calls (http://www.ercot.com/committees/nodal/eds/). http://nodal.ercot.com 39

  40. Telemetry Resources and Links • Telemetry Resources and Links: • The ERCOT Nodal ICCP Communication Handbook is posted at http://nodal.ercot.com/readiness/eds1/documents/index.html • MPs may submit questions about the Nodal Telemetry Outreach effort to EDS3@ercot.com with “Nodal Telemetry Outreach” in the subject line. • The 2009 FIT III Calendar and FIT III Assessment reports are posted at:http://nodal.ercot.com/readiness/eds3/documents/index.html • The TML process for QSE ICCP Service Requests and an example of the ICCP Change Request Form are posted at: http://nodal.ercot.com/readiness/eds1/documents/index.html http://nodal.ercot.com 40

  41. Market Trials 2010 Roadmap 1/6/2020 http://nodal.ercot.com 41

  42. Market Trials Roadmap for 2010 • Market Trials 2010 discussion outline • History of EDS • Market Trials Approach • Detailed view of 2010 Market Activities as Roadmap http://nodal.ercot.com 42

  43. History of EDS • What EDS execution occurred in 2007/2008 • Nodal 2-hour LFC test • Real-Time systems controlled ERCOT system grid (2-hour LFC test) • CRR Auctions executed • Annual and Monthly Auctions executed with market • DAM/DRUC/HRUC/SASM executed 2x/week for 2 months • Outage Scheduler submission testing conducted • Subset of Settlements Invoices produced • Trials stopped due to lack of integration readiness • Most significant issue was no common network model in NMMS/EMS/MMS http://nodal.ercot.com 43

  44. Current Market Trials Approach • Project focus and milestones are aligned to track to integration and subsequent market trial milestones • Dedicated/Integrated environment in place • Execution of core systems and integration scripts being tested across upstream/downstream systems • Managing inter-related activities in single view of dependencies for each release including: • Systems and specific functionality required • List of each distinct interface and discrete data flows • Process/Procedures to support data and trials • Scope includes list of applicable reports/extracts to support testing • Operational Readiness plans are included http://nodal.ercot.com 44

  45. TAC Slide Excerpt from Oct 1 Reflecting program activities/issues being managed for milestone • Program Milestones • Phase 2.1: Market Connectivity • Project Milestones (30-day look-ahead) • Integration/Connectivity Testing/Integration Testing • MMS UI: initial test cycle 100% complete • MMS EWS: initial test cycle 100% complete • 33 open defects (no Sev 1s) in regression test: 92% complete • Market Trials/Connectivity Testing/Market Trials External Testing • Kickoff meeting Oct. 8 • External interface specification document posted • Phase 2.1 Market Connectivity Handbook to be posted Oct. 2 • Readiness/Market Readiness/External Outreach & Training • Market Readiness Seminar Oct. 8 • MP site visits begin Oct. 9 (LCRA) • Readiness/Market Readiness/Metrics Tracking & Assessment • Phase 2.1 Commencement Criteria met (environment built and validated) • Readiness/Operational Readiness/Environment Configuration & Management • Nodal Production environment build-out (installation, verification of 2.1 code sets): 100% (hardware installed, baseline code set on schedule); final build scheduled Oct. 16 • Readiness/Operational Readiness/Security Testing • Performance testing: 50% (web service stability and loading, UI stability and loading) • Security testing underway this week TAC Slide Excerpt Technical Advisory Committee

  46. 2010 Market Trials Roadmap • What has been done to create 2010 Market Trials Roadmap • Recognized durations and execution activities from 2008 trials • Aligned market trials sequence with Integrated Program Schedule • Developed in alignment with PMO delivery plans for phases 2.1, 3, 4, 5 • Objective of 2010 Market Trials Roadmap is to provide next level of detail for program/market engagement • Details to be developed in subsequent Market Trials Handbooks http://nodal.ercot.com 46

  47. Nodal 2010 Roadmap through Go-Live http://nodal.ercot.com 47

  48. Nodal 2010 Roadmap - 8 month view http://nodal.ercot.com 48

  49. Sequencing and focus in 2009 to align to integrated Market Trials Reminder of Ongoing 2009 activities RE-RARF Transmission data submission Underway to end of 2009 TSP Validation of Network Model Underway with SEM Go-Live and goes into early 2010 TSP/QSE Telemetry Outreach/Ramp-up Started early October, forthcoming metrics for State Estimator and SCED related telemetry QSE Verifiable Costs filings Underway, different deadlines for technology types QSE MMS Market Submission Testing (Market Trials Phase 2.1) Starts Oct 28, Qualification and metrics January 2010 Next Steps http://nodal.ercot.com 49

  50. Targeted Market Activities for January 2010 SCED/DAM submission qualification CRR Account Holders qualify on CRR submission ERCOT posts CRR Network Model January 2010 Market Activities http://nodal.ercot.com 50

More Related