1 / 28

Early Delivery Systems Status

Early Delivery Systems Status. Daryl Cote. Agenda. EDS 2 Release 3: State Estimator TSP Dashboard Load Status Wind QSE Dashboard SE results (March vs Feb) EDS 2 Release 4: NOMCR EDS 3 Release 5: SCED Release 6: LFC Release 7: CRR EDS 4 Release 8: Coms Release 9: DAM / RUC / SASM.

orar
Télécharger la présentation

Early Delivery Systems Status

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. Early Delivery SystemsStatus Daryl Cote TPTF

  2. Agenda • EDS 2 • Release 3: State Estimator • TSP Dashboard • Load Status • Wind • QSE Dashboard • SE results (March vs Feb) • EDS 2 Release 4: NOMCR • EDS 3 • Release 5: SCED • Release 6: LFC • Release 7: CRR • EDS 4 • Release 8: Coms • Release 9: DAM / RUC / SASM TPTF

  3. TSP Dashboard TPTF

  4. Convergence Rate MVAR tolerance remains at 30. Working to identify reactive curves that need to be adjusted so that MVAR can be set to 15 also TPTF

  5. Load Status TPTF

  6. EDS 2 – Wind Output from QSEs This data is required to support AWS TrueWind’s forecast tuning TPTF

  7. QSE Dashboard TPTF

  8. State Estimator 30 day Comparison TPTF

  9. State Estimator 30 day Comparison II TPTF

  10. Next Steps • Complete Telemetry Reporting • Remedy Application issues • ERCOT build redundant servers at Met Center TPTF

  11. Release 4 – NMMS / NOMCR Sep Oct Nov Dec Jan 2008 2007 Feb Network Model Verification NOMCR Checkout E2 R4 R4: NOMCR / Network Model verification • NMMS/NOMCR overview training has been completed by the market participants • Citrix connections and digital certificates have been successfully installed and validated for 100% of the market participants • Onsite NMMS training and scripted scenario execution completed by: • AEP, Rayburn, STEC, and College Station • Onsite training to occur week of 4/7 for: • CenterPoint & Greenville • Onsite training to occur week of 4/14 for: • Austin Energy, Garland, CPS San Antonio • All MP to complete onsite training week of 5/19 TPTF

  12. EDS SLA Metrics This data only describes HW. March number should include applications. Reports are posted at: http://nodal.ercot.com/readiness/index.htmlEDS - SLA Metrics Summary (February 2008) TPTF

  13. Release 5 - SCED Sep Oct Nov Dec Jan 2008 2007 Feb 6-month LMP Posting RT ICCP E3 R5 SCED R5.1 SCED R5.2 SCED R5.3: RT ICCP SCED R5.4: LMP Post Legend: % in parentheses are from the 2/22 TPTF update TPTF

  14. Recent Issues with LMPs 3 Market Participant • Poor quality of ICCP data will cause SE & TCM to not publish results to MMS; therefore stale LMPs & BPs or uniform LMPs • EMS – MMS interface shuts down daily (reported Oracle issue); therefore stale LMPs & BPs • COP / TPO / OS submissions to SCED are sufficient 1 EMS MMS 2 1 2 3 Starting in Mid-April, ERCOT will contact MPs Real-Time desks when data issues cause SE / TCM failures. This will be done 24x7 TPTF

  15. Release 6 - LFC Jan Feb Mar Apr May 2008 Jun E3 R6 R6.1: ACE & RLC R6.2: QSE Testing R6.3: TST Legend: % in parentheses are from the 2/22 TPTF update TPTF

  16. Release 6 - LFC Jan Feb Mar Apr May 2008 Jun E3 R6 R6.1: ACE & RLC R6.2: QSE Testing R6.3: TST ~ 50% of the AS schedules and responsibilities being provided accurately via ICCP. 6.3 testing can not commence without this data. QSEs wishing to accelerate their 6.2 test date are encouraged to do so. Legend: % in parentheses are from the 2/22 TPTF update TPTF

  17. LFC 6.3 pre-Test • Prior to R6.3 (total system test) the market desires an open loop test to validate SCED dispatch. Approach to accomplish this: • QSEs w/ Resources submit Excel files with EOC, OS, INC/DEC on 4/8 that deconstruct Zonal activities for Operating period 4/7 7-9am • Perform open loop test on 4/25 from 7-9am • Perform open loop test on 5/5 from 10-noon • Perform open loop test on 4/12 from 4-6pm • ERCOT to provide QSEs with settlement impact resulting from OOME and Local Balancing had units followed SCEB BP • Please refer to details provided during the 3/14 workshop: http://www.ercot.com/calendar/2008/03/20080314-EDS3-6.html TPTF

  18. Target Dates for 6.3 Tests • Week of June 16th – 2 hour test • Week of July 7th – 8 hour test • Week of July 28th – 48 hour test TPTF

  19. Release 7 - CRR Dec 07 Jan 08 Feb 08 Mar 08 Apr 08 May 08 Apr 08 Dec 07 Dec 07 Jan 08 Jan 08 Feb 08 Feb 08 Mar 08 Mar 08 Apr 08 May 08 May 08 CRR R7.4 CRR CRR – – R7.0 R7.0 CRR CRR – – R7.1 R7.1 CRR CRR – – R7.2 R7.2 CRR CRR – – R7.3 R7.3 CRR CRR – – R7.5 (TBD) R7.5 (TBD) Release 7.4 Scheduled to begin 4/7; possibility of delayed completion CRR team to discuss configuration limitations with TPTF on 4/2 Legend: % in parentheses are from the 2/22 TPTF update TPTF

  20. EDS 4 Release 9.1 Jan Feb Mar Apr May 2008 Jun E4 R9 R9.1: DAM/RUC Submission Testing R9.3: R9.4: DAM/ Adj Period, RT R9.2: Outage Scheduler Those not completed with 9.1 will be Red for Readiness Metric MP8 after 3/31. Legend: % in parentheses are from the 2/22 TPTF update TPTF

  21. Ambridge Energy* Aquila Citadel Energy Products Clearview Electric Glacial Energy Kansas City Power and Light National Power Company Sitara Energy Texpo Power Urban Energy Source WCW International EDS 4 Release 9.1 QSEs that have not signed up for a testing window for EDS4 (as of COB 3/28/08) TPTF

  22. EDS 4 Release 9.2 Jan Feb Mar Apr May 2008 Jun E4 R9 R9.1: DAM/RUC Submission Testing R9.3: R9.4: DAM/ Adj Period, RT R9.2: Outage Scheduler Release 9.2 Kickoff webex conducted on 3/27 Testing to occur from 4/15 through 6/13 Legend: % in parentheses are from the 2/22 TPTF update TPTF

  23. EDS 4 Release 9 timeline as showed in the approved handbook Jan Feb Mar Apr May Jun Jul Aug • MMS2 • DAM / RUC Submission Items • MMS2 • CIM Integration • EMS-MMS Integration 9.1 - DAM/RUC Submission testing 9.3 - Initial DAM/RUC Exec • MMS3 (MMS2 + SASM, CIM Imp) • MMS4 • Settlements integration • All Integration points addressed • MIS/EDW Integration 9.4 - Exec DAM, Adj Period, RT Ops • DAM/RUC database for MP EDS Activities • Verify QSEs ability to submit, modify, cancel, and retrieve submission items using MIS/User Interface and/or Web Services 9.5 - Pre-Test for 168 hour test • QSEs submit transactions to DAM/RUC • Post pre-DAM/RUC exec data (A/S Obligations, LF) • Execute DAM and RUC • Test MMS integration with NMMS and EMS • Communicate results to QSEs (MIS and notifications) • Test QSE ability to receive notifications, prices, awards • Stub in other data as needed • Begin Adj Period activities – SASM/HRUC • Submit all transactions for DAM, Adj Period and RT Ops • Download reports for DAM/DRUC/HRUC/SASM • Performance testing of DAM • Stub data as needed for DAM, Adj Period and RT activities • Execute market timeline for 7 consecutive days • Final assembly and testing of all deliveries, integration and functionality • Implement final MMS delivery to include Baseline 1 and 2 changes • Testing of relevant portions of MIS/EDW/Extracts • Test of EECP, DST, Compliance monitoring and tools • Execute DAM without any significant error of DAM for 7 consecutive days and provide settlement statements • Execute two Operating Days without interruption along the full market timeline with no critical failures • ERCOT and QSEs execute nodal timeline in parallel to zonal market TPTF

  24. Proposed revisions to EDS 4 Release 9 timeline Jan Feb Mar Apr May Jun Jul Aug • MMS2 • DAM / RUC Submission Items • MMS3 • CIM Data Stub 9.1 - DAM/RUC Submission testing • MMS4 • Settlements integration • All Integration points addressed • MIS/EDW Integration 9.3 - Exec DAM/RUC/SASM • DAM/RUC database for MP EDS Activities • Verify QSEs ability to submit, modify, cancel, and retrieve submission items using MIS/User Interface and/or Web Services 9.4 – Integration and Preparation for 168 hour test • Final assembly and testing of all deliveries, integration and functionality • Implement final MMS delivery to include Baseline 1 and 2 changes • Performance testing of DAM • Execute DAM, DRUC, HRUC, SASM • CIM Integration between NMMS, MMS and EMS • Test of EECP, DST, Compliance monitoring and tools • Testing of relevant portions of MIS/EDW/Extracts • Execute DAM without any significant error of DAM for 7 consecutive days and provide settlement statement • Execute two Operating Days without interruption along the full market timeline with no critical failures • ERCOT and QSEs execute nodal timeline in parallel to zonal market • QSEs submit transactions to DAM/RUC • Post pre-DAM/RUC exec data (A/S Obligations, LF) • Execute DAM and RUC • Communicate results to QSEs • Test QSE ability to receive notifications, prices, awards • Stub in other data as needed • Execute SASM/HRUC capabilities in May 08 MMS 3 and MMS 4 will be deployed earlier to the EDS environment to enable market testing TPTF

  25. What does it mean for ERCOT and MPs Jan Feb Mar Apr May Jun Jul Aug • Provide environment for uploading bids and offers • Execute DAM / RUC • Enable downloads of awards • Produce DAM settlement stmts • Execute DAM / RUC/HRUC/SASM • Produce DAM settlement stmts • Enable notifications • Execute DAM / RUC/HRUC/SASM • Implement B1 & B2 submission items • Settlements Integration • Conduct DAM performance test • Run market timeline for 7 consecutive days • Conduct 168 hour test of DAM • EECP • DST and Failover • Compliance monitoring ERCOT • MMS2 • EIP • MMS UI • MMS 3 • Stub CIM + other data • EIP Awards query • MMS UI upgrades • MMS 3 • EIP Notifications • UI Notifications • MMS-OS Integration • MMS 4 • EMS-MMS Integration • MMS - S&B Integration • MMS - NMMS integration • CSI • EMS-NMMS-MMS Integration • Implement last EMS delivery • MMS-CMM integration • MIS • CDR • Compliance monitoring 9.3 - Exec DAM/RUC/SASM 9.1 - DAM/RUC Submission testing 9.4 – Integration and Preparation for 168 hour test • Participate in DAM performance test • Verify new Day Ahead and RT reports • Extract support • Adapt to Baseline1/2 Market Submission changes in MMS4 • Submit, modify, retrieve, cancel bids and offers • Submit transactions to DAM and RUC • Download DAM Awards • Participate in DAM, Adj period and RT Ops testing • Receive DAM Award notifications • Validate Settlements stmts • Participate in DAM and settlement of 168 hour test • Participate in DST and Failover testing • Participate in EECP test Market Participant Current day reports and EDW extracts will be deployed according to the DAG schedule TPTF

  26. A Go-Live Plan is being developed that will encompass key activities/actions post the successful completion of the 168-Hr test • Key Elements of the plan include: • ERCOT and Market Participant engagement expectations • Communications and ongoing health checks during the go-live period • Phased staging of production submission during cut-over • Planned regression test of Nodal LFC • Software environment controls (migration freeze) • Contingency planning and guidelines for switch of control back to zonal TPTF

  27. EDS Deliverables  Legend: indicates completion TPTF

  28. Questions? TPTF

More Related