1 / 69

Market Readiness Seminar 6

Market Readiness Seminar 6. Remaining Market Trials and Cutover Activities. Sept 01, 2010. Antitrust Admonition. ANTITRUST ADMONITION

walter
Télécharger la présentation

Market Readiness Seminar 6

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 Readiness Seminar 6 Remaining Market Trials and Cutover Activities Sept 01, 2010 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 • Review of Phase 5 Activities • 168-Hour Test Breakdown of Activities • 168-Hour Measurements • Objective / Participation Requirements • Entry / Exit Criteria • Evaluation Criteria • Preparation Activities • Completed – Full System Market and Reliability Tests • Completed – Outage Scheduling Verification and Synchronization • Completed – CRR September Auction • Network Model Load • Data Used for 168-Hour Test • Nodal Production Environment • 168-Hour Test Execution • Schedule • Communications Plan • Post 168-Hour Testing Activities • Cutover and Market Readiness Activities http://nodal.ercot.com 3

  4. Review of Phase 5 Activities http://nodal.ercot.com 4

  5. Review of Phase 5 Activities Market Trials 2010 Roadmap http://nodal.ercot.com 5

  6. 168-Hour Test Measurements http://nodal.ercot.com 6

  7. 168-Hour Test Breakdown of Activities: Objective / Participation Requirements • Objective • Conduct a full rehearsal of the Nodal Day-Ahead Market (DAM), Reliability Unit Commitment (RUC), Real Time Market and Load Frequency Control (LFC) • Continuous seven day period of Market Systems and 48 hours of Closed Loop LFC • Components required and to be exercised during the 168-Hour test: • The Day Ahead functions including DAM, DRUC, HRUC and WRUC • The Real Time systems performing SCADA, Network Security Analysis, Transmission Constraint Management, SCED, and LFC • The Nodal support systems including Network Model Management, Outage Scheduler, Outage Evaluation tools • Credit Monitoring and Management (CMM) • Settlements and Billing • Posting of applicable Reports and Extracts • Participation Requirements • The value of the 168-Hour Test is dependent on participation by the Market. • The 168-Hour Test is required by all registered Market Participants intending to be involved in the Nodal Market • Participation data and metrics will be published and made readily available to the ERCOT Board, Independent Market Monitor and the related Market Participant Forums (NATF, TAC) • Metrics will also include comparisons of Zonal Resource Plans to Nodal COPs. • Participation should be reasonably reflective of post Go-Live behavior http://nodal.ercot.com 7

  8. 168-Hour Test Breakdown of Activities: Entry / Exit Criteria • Entry Criteria for the 168-Hour test will be as follows: • All defined Market Trials Testing up until the 168-Hr test has been completed in accordance with the Market Trials Handbooks published to the Nodal Readiness Center • ERCOT declares readiness for initiating the 168-Hour test to TAC and the Board and obtains director level sign off from ERCOT management. • Exit Criteria • 168 hours of continuous Nodal systems testing have been completed without encountering any major system issues that would prevent the Nodal Market from going live while maintaining system security and reliability as required by the ERCOT Protocols, Operating Guides, other binding documents, and NERC Reliability Standards. • ERCOT provides a test summary report to TAC and the Board outlining the successful testing processes. http://nodal.ercot.com 8

  9. 168-Hour Test Breakdown of Activities: Evaluation Criteria • Evaluation Criteria was agreed on in coordination with the Market at the NATF and TAC forums • Evaluation Criteria will be reviewed holistically in that no one issue from this list will necessarily constitute a failure of the test • Evaluation Criteria is included in the Appendix of this presentation and in the 168-Hour Handbook http://nodal.ercot.com 9

  10. 168-Hour Test Breakdown of Activities: Preparation Activities • Full System Market and Reliability Tests • The following tests have been completed prior to the start of the 168-Hour tests: • 2-Hour Test – Completed May 20, 2010 • 8-Hour Test – Completed June 17, 2010 • 5-Hour Test – Completed July 21, 2010 • 24-Hour Test 1 – Completed August 5, 2010 • 24-Hour Test 2 – Completed August 20, 2010 • 40-Hour Test – Completed August 28, 2010 • Total Full System Tests completed prior to the 168-Hour Tests: 103 • Outage Scheduling Transition Plan • 08/16/2010: ERCOT released the Outage Scheduler to be synchronized and verified by TSPs and QSEs for outages effective for the month of September • 08/30/2010: TSP and QSE deadline to complete synchronization and verification • Market Participants that have not yet completed this should: • Continue work on this activity • If there are questions or issues, contact ERCOT at martkettrials@ercot.com • Congestion Revenue Rights Auction • 08/27/2010: ERCOT posted the Auction Results for the September Monthly Auction http://nodal.ercot.com 10

  11. 168-Hour Test Breakdown of Activities: Preparation Activities • Network Model Load • 09/01/2010: Network model to be used during the 168-Hour test loaded to the Nodal Production Environment • Going forward the network model loads will generally follow the Zonal schedule • Data from Market Trials Phase 5 to be used in the 168-Hour test • To the extent necessary to support settlement and credit operations, ERCOT will use estimated and/or settled data from Operating Days in July and August from MT5 as well as the CRR inventory from the September CRR auction (see above) during the 168-hour test. http://nodal.ercot.com 11

  12. Nodal Production Environment http://nodal.ercot.com 12

  13. Nodal Production Environment • During the 168-Hour Test, applicable Nodal systems will be managed as if the systems were fully in production 7x24, exercising the same procedures used for Zonal production operations • Change Controls during and leading up to the test shall adhere to a similar SLA as Zonal Production • If an outage is required, a Market Notice will be issued and determination will be made if this will require a restart of the 168-Hour test http://nodal.ercot.com 13

  14. 168-Hour Execution http://nodal.ercot.com 14

  15. 168-Hour Execution: Schedule • September 8, 2010 - 168-Hour Test begins • Day ahead Market will run for Operating Day September 9, 2010 using the DAM ACL sent from CMM • DRUC and WRUC will run per protocol timelines starting the first day of the test • ERCOT will begin running hourly HRUC at 1800 when the Adjustment Period opens. • All Real Time telemetry, and Market Submission shall continue to be submitted by the Market • All postings delivered in previous Market Trials Phases delivered per Nodal Protocol timelines • Initial DAM / RTM statements posted per the Nodal settlements calendar • Production level support, including those systems that are supported 24x7, goes into effect for the duration of the 168-Hour Test • For the duration of the test, DAM, RUC, Settlements and Credit processes will run per Nodal Protocol guidelines in an open loop format. Zonal will continue to commit units using the RPRS processes and actual, binding settlements will execute per Zonal Protocols. • September 12 – September 14, 2010 – Full System Market and Reliability Test During the 168-Hour Test • September 12, 2010 at 2:00 PM, all generation will begin transitioning to Nodal control estimated to be completed by 3:00 PM • The ERCOT grid will run under Nodal Control through September 14, amounting to a total of 48 Hours of Full System Market and Reliability Testing during the 168-Hour Test • Day Ahead Market, RUC processes and SASM will continue to be executed per Nodal Protocols. • Zonal will continue to commit units using the RPRS and OOMC processes and actual, binding settlements will execute per Zonal Protocols. • September 14, 2010 all generation will transition back to Zonal starting at 1:00 PM, estimated to be completed by 2:00 PM • September 14, 2010 – September 15, 2010 • ERCOT will continue to run the remaining operating days of the 168-Hour test, executing DAM, RUC, settlements and credit processes • The final day of the 168-Hour test will be on September 15, 2010 • September 16 or 17, 2010 • Special NATF session will be held to review the DAM testing results of the 168-Hour test and determine remaining testing objectives for Market Trials. RT testing results will be evaluated once RT settlement statements are received. http://nodal.ercot.com 15

  16. 168-Hour Execution: Communications Plan • ERCOT will host a daily WebEx / Conference call • This will occur at 10am each day of the 168-Hour Test • Details will be posted to the ERCOT calendar at http://www.ercot.com/committees/nodal/mt/ • ERCOT will maintain a list of known issues to updated each day on these conference calls • This will be posted to the ERCOT Readiness Center on a daily basis • Additionally, this will also be posted to the ERCOT calendar instance for that day. • Issues Raised by the Market • Market Participants will continue to utilize the markettrials@ercot.com email address outside of the daily conference calls • Full System Market and Reliability Test • ERCOT will maintain a separate WebEx conference during the 48-Hour test • 9/12/2010: 12:00 PM – 12:00 AM • 9/13/2010: 6:00 AM – 12:00 AM • 9/14/2010: 6:00 AM – 2:30 PM • Details for this WebEx will be sent out by Friday 09/03/2010 http://nodal.ercot.com 16

  17. 168HR Supporting Materials http://nodal.ercot.com 17

  18. Evaluation Criteria • Validate ERCOT and Market Participants have the proper resources and expertise to manage a Nodal system for 7 days. This will be measured by the successful adherence to internal ERCOT procedures during the 168-Hour test to be validated by the ERCOT Training Department during the test and evidenced to the market within a report. Market Participant’s Nodal Accountable Executive will self attest to their criterion. • Credit – monitor credit exposures, create credit reports and accurately reflect each market participant’s credit position based on their activity during the 168-Hour test. • Validate data model accuracy between all systems including integration of the upstream NMMS system with downstream systems (e.g. DAM, MMS, EMS and CRR). This will be measured by existing ERCOT procedures. All issues observed regarding inaccurate modeling during the 168-Hour test will be reported on by ERCOT to the ERCOT Board, Independent Market Monitor, and the related Market Participant forums (NATF and TAC) as to the problem found, root cause of the error in the first place, and what process changes are being implemented to ensure that similar model accuracy issues do not reoccur going forward. ERCOT shall attest to the data model accuracy in and between all systems as a result of TSP and Resource Entity data passing the ERCOT validation rules. • Execute DAM, DRUC, HRUC and WRUC for 7 days within timelines set by Nodal Protocols. If any activities fall outside of expected timelines, procedures for handling such incident must be executed by ERCOT personnel in adherence with Nodal Protocols and internal ERCOT procedures. • Verify RT Operators can maintain system frequency to scheduled frequency, maintain ancillary obligations and resolve constraints during the period in which ERCOT will be performing Full System Market and Reliability tests during the 168-Hour Test. http://nodal.ercot.com 18

  19. Evaluation Criteria • Validate ERCOT can effectively and accurately manage all constraints in both DAM and RT (i.e. not constrain on invalid contingencies or inaccurate line ratings) and system will utilize full list of competitive constraints. • Validate that ERCOT can execute and manage all SPS, RAPs, PCAPs, MPs, and TOAPs to control congestion in the DAM, DRUC, HRUC, and RT as appropriate. • Validate that ERCOT is accurately reflecting all congestion mitigation measures (SPS, RAPs) in DAM. • The rolling CPS1 one minute average score must equal or exceed 100% during the Full System Market and Reliability test period. The target minimum is 125. • Note that the CPS1 average will not take into account the two one-hour periods when ERCOT is transitioning to Nodal and then back to Zonal and any periods in which ERCOT must deploy RRS in response to system contingencies. • Zonal Commercially Significant Constraints (CSCs) and Closely Related Elements (CREs). managed below thermal limits. • Local Congestion managed below thermal limits. • Stability limits managed below transfer limits. • No NERC Disturbance Control Standard (DCS) failure if applicable. • No LFC-SCED system issues that result in termination of the test. • The 168-Hour test will provide adequate data to set the GREDP/CLREDP performance. criteria variables X, Y, and Z. ERCOT shall produce appropriate reports that can be used to set these variables. • Bilateral trades are processed and flow through the market systems with results returned to MPS. • Outputs from the Day Ahead Market, Reliability Unit Commitment, and Real Time Market can be reasonably explained based on the inputs. http://nodal.ercot.com 19

  20. Cut-Over Milestones 9/16/2014 Market Readiness Seminar

  21. Nodal Cutover and Market Transition – Key Cut-Over Milestones Market Readiness Seminar

  22. Key Cutover Activities Thru December 2010 9/16/2014 Market Readiness Seminar

  23. Cut-Over Timeline – Thru December 2010 Market Readiness Seminar

  24. Cut-Over Monthly Outlook – August May June July Aug Sept Oct Nov Dec Key Cut-Over Activities for August 2010 • (08/01) Model: Begin network modeling timelines-Complete • (08/13) OS: Outage Scheduler Zonal to Nodal Import process run • (08/13) CRR: Last day to register for CRR December monthly auction • (08/16) OS: ERCOT releases Outage Scheduler to Market • (08/16-09/17) OS: Market Participants synchronize / verify outages in the Nodal Outage Scheduler to the Zonal Outage Scheduler for Outages effective during and after December 2010 • Network Model • Outage Scheduler • Congestion Revenue Rights Functional Area Functional Area • Task Plan • Data Prep • Decommission/Retirement Template • Contingency/Back-out Template • Entities Involved • ERCOT • TSP • REs • CRRAH • QSE • Impacts • TSPs/REs submit Transmission and Resource data for December model (05_Nodal_Load_transition_1_0.doc posted on 06/01 NATF Materials) • Resource outages will NOT be imported during Zonal to Nodal import into Outage Scheduler • CRRAH must register by deadline to be eligible to participate in the December Auction (Protocol 16.8.2) • TSPs/QSEs can begin entering outages in Outage Scheduler via Web Service or UI • TSPs/QSEs are responsible for verifying outages imported to Nodal Systems and correcting any missed outages or incorrect outages by 09/17/2010 Market Readiness Seminar

  25. Cut-Over Monthly Outlook – September May June July Aug Sept Oct Nov Dec Functional Area • Network Model • Outage Scheduler • Congestion Revenue Rights Key Cut-Over Activities for September 2010 • (09/01) Model: Network Model Go-Live • (09/01) Model: Deadline to submit Model changes for Month of December • (09/02) Model: Begin interim update process • (09/01) CRR: ERCOT publishes CRR Activity Calendar to MIS • (09/08) CRR: Deadline for PCRR NOIE Contract Eligibility • (09/17-12/01) OS: Outages are synched. Market Participants maintain outages in both the Zonal and Nodal Outage Scheduler for outages effective December and beyond. • Entities Involved • ERCOT • TSP • REs • CRRAH • QSE • Impacts • TSPs / REs that submit Model changes to ERCOT by 09/01 will be applied prior to Go-Live • From 09/02 forward until Go-Live any Model changes submitted to ERCOT for application prior to Go-Live will leverage the interim update process.   • MPs can retrieve the CRR Activity Calendar from MIS public with a valid Digital Certificate Market Readiness Seminar

  26. Cut-Over Monthly Outlook – October May June July Aug Sept Oct Nov Dec Key Cut-Over Activities for October 2010 • (10/01) CRR: CRR system data clean up for Go-Live • (10/01) Credit: ERCOT assesses each CPs credit worthiness for the Dec CRR Auction • (10/02) OS: First pull of December Outages for CRR Network Model (for PCRR Allocation) • (10/02) Model: Network Model built for CRR Allocation and Auction • (10/03-10/11) MIS UI and EWS Get Report function not available (ERCOT back end reconfiguration) • (10/13) OS:  Changes to December Outages considered for CRR Auction Model • (10/13) Model:  Changes to Model considered for CRR December Auction • Functional Area • Network Model • Outage Scheduler • Congestion Revenue Rights • Credit • MIS • Impacts • MIS UI and EWS Get Report unavailable from 10/03-10/11 for production reconfiguration** • CRRAH able to retrieve ACLs from CRR system each business day. • MPs can post additional collateral until 11/08/2010 for Dec 2010 CRR Auction • MPs able to start retrieving Go-Live postings on MIS. Refer to EMIL for dates per posting. • Dec 2010 CRR Model available on MIS • Dec 2010 Monthly Auction Notice available on MIS Market Readiness Seminar

  27. Cut-Over Monthly Outlook – October May June July Aug Sept Oct Nov Dec Key Cut-Over Activities for October 2010 • (10/14-10/19) CRR: ERCOT begins accepting PCRR Nominations for December Monthly Auction (updated) • (10/15-11/15) Model: Network Operations Model posted to TSP Citrix location and TSPs begin validation process • (10/26) CRR: ERCOT shall allocate PCRRs to NOIEs for the 2010 December Monthly Auction and publish to MIS • (10/26) CRR: ERCOT shall post CRR Network Model for the 2010 December Monthly Auction to MIS • (10/28-11/08) Credit: ERCOT posts ACLs daily for CRR December monthly auction to CRR • (10/29) CRR: ERCOT to post December 2010 Monthly Auction Notice to MIS • Functional Area • Network Model • Outage Scheduler • Congestion Revenue Rights • Credit • MIS • Impacts • CRRAH able to retrieve ACLs from CRR system each business day. • MPs can post additional collateral until 11/08/2010 for Dec 2010 CRR Auction • MPs able to start retrieving Go-Live postings on MIS. Refer to EMIL for dates per posting. • Dec 2010 CRR Model available on MIS • Dec 2010 Monthly Auction Notice available on MIS Market Readiness Seminar

  28. Cut-Over Monthly Outlook – October – MIS UI and EWS Get Report Reconfiguration Details MIS UI and EWS Get Report Reconfiguration Details (10/03/2010 – 10/11/2010) • Market Participants will not have access to the MIS UI and EWS Get Reports functionality. • Market Participants will need to use the direct links (listed on next slide) or Citrix to access system applications. • All other EWS will be left on and from 10/1 up until the First Run Date as defined in EMIL of the CDR report, the EWS will return ‘no reports found’ during that time. MIS UI and EWS Get Report Go-Live (10/12/2010) • Postings will be made available based on the EMIL posting date going forward. • Postings live prior to 10/12/2010 will continue to be made available at this time. • Market Participants will only have access to go-live posting data. Data from Market Trials activities is no longer available for download. Market Readiness Seminar

  29. Cut-Over Monthly Outlook – October – MISUI and EWS Get Report Reconfiguration Details URLs to be used during cutover activities: • Network Model via Citrix: • https://gateway.ercot.com/vpn/index.html • Market Manager User Interface: • https://mis.ercot.com/mmsui/mmsui/displayTradesLanding.action • Outage Scheduler Application: • https://mis.ercot.com/osrui/osrui/Summary.action • CRR Application (MUI): • https://mis.ercot.com/crr/mui/ListAllUserMessage.do - direct link for CRRAHs • https://mis.ercot.com/crr/mui/editSMPCreditLimit.do - direct link for CPs • Web Services Endpoint URL: • https://misapi.ercot.com/2007-08/Nodal/eEDS/EWS Market Readiness Seminar

  30. Cut-Over Monthly Outlook – November May June July Aug Sept Oct Nov Dec Key Cut-Over Activities for November 2010 • (11/8/2010 12:00pm) Credit: Collateral Posting Deadline (Dec Auction) • (11/8/2010 5:00pm) CRR: Credit Lock for Dec CRR Auction • (11/9/2010 – 11/11/2010) CRR: December CRR Auction Bid Open/Close • (11/12/2010) CRR: December CRR Auction Executes • (11/15/2010) CRR: December CRR Auction Results published • (11/16/2010) Settlements: December CRR Auction Invoice published • (11/16/2010) Disputes: Dispute submitted to ERCOT for CRR Invoice • (11/19/2010) Credit: Payment Due for December CRR Auction Invoices • (11/22/2010) Settlements: Payments to CRRAH (Dec Auction) • (11/23/2010) Credit: ERCOT to Release ACL (TPE and ACL Reports Available on MIS) • (11/23/2010) Market Submission Opens (Remaining Protocol Go-Live) • (11/24/2010) Model: Network Model Load • (11/29/2010) Credit: ERCOT to Publish ACL for the initial Day-Ahead Market execution by ERCOT • Functional Area • Settlements • Credit • Congestion Revenue Rights • Disputes • Market Management • Impacts • Available Credit Limit is locked for CRRAHs • CRRAHs can submit disputes against CRR Auction Invoice via the API or MIS • CRRAHs can receive postings on MIS • QSEs can begin DAM Bid submission (15 submission items) • Market checkpoint calls begin to facilitate issues and readiness • LFC testing in November will not include Settlements • Daily Market Conference Bridge starts 11/23 Market Readiness Seminar

  31. Cut-Over Monthly Outlook – Go-Live Sequence of Events Go-Live Sequencing Market Readiness Seminar

  32. Cut-Over Monthly Outlook – December May June July Aug Sept Oct Nov Dec Key Cut-Over Activities for December 2010 • (12/01/10) Nodal Program: Nodal Go-Live (Operating Day 1) • (12/3/2010) Settlements: Nodal Day Ahead Market Statement & Invoice Available • (12/3/2010) Disputes: Disputes submitted to ERCOT for DAM Invoice • (12/8/2010) Credit: Nodal Payment Due for OD12/01/2010 • (12/9/2010) Credit: Nodal Payout for OD12/01/2010 • (12/15/2010) Model: Network Model Load • (12/13/2010) Settlements: Nodal Real-Time Statement Available • (12/16/2010) Settlements: Nodal Real-Time Invoice Available • (12/27/2010) Credit: Nodal Payment Due for Real-Time Invoice 12/16/10 • (12/28/2010) Credit: Nodal Payout for Real-Time Invoice 12/16/10 • Functional Area • Network Model • Settlements • Congestion Revenue Rights • Credit • Market Management System • Impacts • Daily Market Calls continue for issue facilitation • MPs receive 1st Nodal Invoice for DAM and RTM via MIS • MPs can submit Disputes via MIS or API Market Readiness Seminar

  33. Nodal Cutover – Nodal System Readiness Criteria Nodal System Readiness Update Market Readiness Seminar

  34. Nodal Cutover Communications – Zonal Protocol 21.12.3 21.12.3 Notice to Market Participants of Effective Date for Nodal Protocol Provisions and Retirement of Zonal Protocol Provision No part of the nodal market design may start operation until all the Market Readiness Criteria for that part of the nodal market design have been met. Certification that all Market Readiness Criteria have been met must be made at least by each of the following: the Technical Advisory Committee (TAC), ERCOT and the ERCOT Board. Upon such certification, ERCOT shall issue two Notices alerting Market Participants to the effective date of Nodal Protocol sections and the retirement of Zonal Protocol sections, as applicable. ERCOT shall issue the first Notice no less than thirty (30) days prior to the effective date or retirement date, as applicable, and the second Notice no less than ten (10) days prior to the effective date or retirement date, as applicable. The Notice shall include: (1) The Nodal Protocol Sections to become effective; and (2) The Zonal Protocol Sections to be retired, if any Market Readiness Seminar

  35. Nodal Program Communications Market Readiness Seminar

  36. Readiness Methodology ERCOT will measure readiness by the following categories: • System Readiness – an evaluation of a particular system needed to support identified market activities • Process Readiness – an evaluation of the Processes and Procedures necessary to support identified market activities • People Readiness – an evaluation of ERCOT and Market Participant capabilities to support identified market activities ERCOT plans to review the Market Readiness Criteria at NATF and subsequently request a vote from TAC per Section 21.12.3, Notice to Market Participants of Effective Date for Nodal Protocol Provisions and Retirement of Zonal Protocol Provision Market Readiness Seminar

  37. Readiness Methodology System Readiness – evaluation of the Nodal system to support the market design • Core system functionality delivered • Protocol required system functionality available for market testing • System Integration delivered • System to system integration delivered to support Market Timeline and Business Processes • Known defects resolution plan • All ‘Must fix prior to go-live’ defects have a resolution plan in place • Active Readiness Metrics • Current status of Readiness Metrics Market Readiness Seminar

  38. Readiness Methodology Process Readiness – evaluation of the Processes and Procedures necessary to support the market design • Procedures complete • ERT project procedures to support business processes complete • System cutover transition plan established • ERCOT and Market Participant business activities required for transitioning into Go-Live have been established and communicated. • Market rules transition communicated • Nodal and Zonal Protocol effective / retirement dates identified and communicated for Market Participant review Market Readiness Seminar

  39. Readiness Methodology People Readiness – evaluation of ERCOT employee readiness and Market Participant knowledge to support the market design • ERCOT staff supporting Market Trials • ERCOT Business teams supporting system execution, problem resolution, and Market questions • ERCOT staff trained on System and Processes • ERCOT Business teams training status based on identified ERT training metrics • Market Participant Training delivered • ERT external training classes and web based training provided by the Nodal training project Market Readiness Seminar

  40. NMMS Overview Recommendation of Certification • Status / Other Issues: • Stability issue resolved as of July 1 (ERCOT continues to monitor production) • Navigation performance issues improved Aug 1st (43% reduction in response time measured) • Validation performance improvement patch was added on Friday, August 27th (expected a 20-40% reduction in validation time). Improvement on validation times were tested as follows: • Average: 45.18% • Median: 66.41% • Max: 97.46% Open Defects: Deferred Defects: 0 Sev 1 ! 11 Deferred ! 0 Sev 2 0 ! Sev 3-5 Technical Advisory Committee

  41. Network Operations Modeling – Go Live Status updated post ERCOT, TAC, BOD approval – in RED Market Readiness Seminar

  42. Network Operations Modeling – Go Live Status updated post ERCOT, TAC, BOD approval – in RED Market Readiness Seminar

  43. OS Overview Recommendation of Certification • Status / Other Issues: • No defects reported in the Outage Scheduler • Outage Scheduler transition tasks were completed on 8/13 and the system was ready for dual entry and validation on 8/16 • Market Notice for dual entry and validation was sent on August 16th • All Outage scheduler issues within the TSP Issues list have either been addressed or are resolved Open Defects: Deferred Defects: 0 Sev 1 ! 119 Deferred ! 0 Sev 2 0 ! Sev 3-5 Technical Advisory Committee

  44. Outage Scheduling – Go Live Market Readiness Seminar

  45. Outage Scheduling – Go Live Market Readiness Seminar

  46. CRR Overview Recommendation of Certification • Status / Other Issues: • Working with Siemens on automated processor fix. Expectation is to receive fix before Go-Live • Incorrect Loadzone Designation from Topology Processor Output file • Resource Nodes missing from Settlement Point output file produced by Topology Processor • Topology Processor cannot consume outages information for CRR modeling • CRR MUI requires a system reboot for Bid Limit to take effect (internal to ERCOT) workaround is nuisance -targeting 09/13/2010 resolution Open Defects: Deferred Defects: 0 Sev 1 ! 4 Deferred ! 0 Sev 2 ! 4 Sev 3-5 Technical Advisory Committee

  47. CRR Allocation and Auction – Readiness Update ** Red due to MPs registering but not working to get qualified. (inflated denominator) Market Readiness Seminar

  48. CRR Allocation and Auction – Go Live Market Readiness Seminar

  49. MMS – Day Ahead, Adjustment Period, RT Market Overview Recommendation of Certification • Status / Other Issues: • MMS currently has 58 Open defects in Test targeted to be fixed by September 3. • 21 DAM • 2 AS Mgr • 1 CIM, 1 SASM, 1 CCT, 1 Validation Rules • 9 Background Processing • 3 SCED • 6 RUC • 13 Market Infrastructure including 6 GUI • MMS currently has 24 Open defects in development targeted to be fixed by October 1. • 6 DAM, 4 RUC, 4 SCED, 3 MI, 7 GUI • MMS remaining 13 (7 performance, 3 MOI, 3 MI) defects are being reviewed by business for final disposition. Open Defects: Deferred Defects: 0 Sev 1 ! 44 Deferred ! 43 Sev 2 ! 52 Sev 3-5 Market Readiness Seminar

  50. MMS – Day Ahead, Adjustment Period, RT Market – Readiness Update Market Readiness Seminar

More Related