1 / 14

Report Inventory

Update on NPRR102 Impacts and Implementation of PUCT Rule 25.505 Posting Requirements July 23, 2008 Matt Mereness mmereness@ercot.com. Report Inventory. Total inventory of 84 reports (40 unique, plus 44 for Disclosure Area). TPTF discussion.

dmarquez
Download Presentation

Report Inventory

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. Update on NPRR102 Impacts and Implementation of PUCT Rule 25.505 Posting RequirementsJuly 23, 2008Matt Merenessmmereness@ercot.com http://nodal.ercot.com 1

  2. Report Inventory Total inventory of 84 reports (40 unique, plus 44 for Disclosure Area) http://nodal.ercot.com 2

  3. TPTF discussion • Disclosure Area discussion for TPTF value-engineering • PUCT Language in 25.505 applicable to zonal and nodal disclosure “The following information in aggregated form, for each settlement interval and for each area where available, shall be posted two calendar days after the day for which the information is accumulated.“ • PUCT staff has been (and remains neutral) on the need for aggregate data to be disclosed by 2003 CM Zones • Nodal team is trying to minimize additional requirements • Focus is on integrated schedule and delivery • Additional 44 reports have an initial cost of $600-700k which does not include on-going O&M and storage costs • All aggregate data provided in 60-day disclosure • By QSE and by Resource/Settlement Point • TPTF recommendation to return to July 7th TPTF with NPRR102 comments form to remove Disclosure Area and draft NPRR to add Disclosure Area in separate NPRR • Consensus to re-consider at July 21, 2008 TPTF with any input from QSEs http://nodal.ercot.com 3

  4. Real-Time Market: Offers- 500 Resource-specific offers Settlement by 13 Nodal Load Zones 2003 Zones (4) + NOIE Load Zones (4) + DC Tie Load Zones (5) NPRR102 will aggregate 500 Resource Offers into 4 zones DC Ties North East Brazos LCRA AEN DC Ties Laredo EaglePass CPS http://nodal.ercot.com 4

  5. Day-Ahead Market: Bids, Offers, and Settlement at 500+ Nodal Settlement Points 500 Resource Nodes, 13 Load Zones 6 Hubs (N, S, W, H, HubAvg, BusAvg) NPRR102 will aggregate all Settlement Point offers into 4 zones DC Ties North East NorthHub Brazos WestHub LCRA AEN HoustonHub CPS DC Ties Laredo EaglePass SouthHub http://nodal.ercot.com 5

  6. Next Steps • Jim Reynold’s comments on business case • Reliant proposal of NPRR102 language to codify in protocols six-months after go-live requirement: • As of the Texas Nodal Market Implementation Date (TNMID) no Disclosure Areas shall be applicable until 180 days following the TNMID at which time the 2003 ERCOT Congestion Management Zones shall become applicable as Disclosure Areas.  Posting requirements will be applicable to Generation Resources for the ERCOT System and those Generation Resources physically located in the defined Disclosure Area as applicable.  The information posted by ERCOT shall include: … • Based on TPTF discussion, ERCOT to update protocol language • If reporting deemed necessary by TPTF, ERCOT will be requesting change the reporting by “Disclosure Areas” to be the 2003 Congestion Management Zones. • Questions? http://nodal.ercot.com 6

  7. Appendices • Appendix 1- Rulemaking History • Appendix 2- Protocol Development History • Appendix 3- Conceptual View of Data Flow • Appendix 4- Discussion of Source Data for Reporting • Appendix 5- Impact/Cost estimate • Appendix 6- List of 2-day Reports http://nodal.ercot.com 7

  8. Appendix 1- Rulemaking History History of Rulemaking and impacts to PUCT Rule 25.505: - PUCT 31972 was adopted in August 10, 2006 - Court appeal was filed and emergency stay was put into place to not disclose all QSE-specific data - PUCT 33490 was adopted August 16, 2007 and changed postings - September 21, 2007 Court Stay removed and all of Rule 25.505 came into effect for zonal and forthcoming nodal systems http://nodal.ercot.com 8

  9. Appendix 2- Protocol Development History Steps to incorporate into nodal protocols (and ERCOT systems) • November and December 2007- ERCOT worked with small group from Commission Staff, Independent Market Monitor, and MPs to draft NPRR to effectuate the disclosures in nodal. • February 6, 2008- TPTF modified and approved NPRR102 • March 5, 2008- TPTF approved redlines to MMS Reqts • “Motion to approve TPTF changes to the Requirements documents: MMS Overall Processes; MMS DAM and SASM; and MMS SCED and Real-Time Processes as submitted on March 5, 2008. TPTF requests ERCOT to provide an impact analysis on the project schedule and cost to make these changes and report back to TPTF.” • March 20, 2008- PRS approved NPRR102 • March 20, 2008- TPTF did not pass Data Reporting Requirements • Concern with MMS being responsible for all reporting • ERCOT committed to returning with update from ABB on approach and costs http://nodal.ercot.com 9

  10. Appendix 3- Conceptual View of Data Flow Data moves from source systems to ISM Data calculation and translation in ISM to create reports http://nodal.ercot.com 10

  11. Appendix 3- Conceptual View of Data Flow • Identified grouping of source system and data elements: • MMS Data: • Most of the reporting data is from MMS • All market submitted data and market results • Bids, Offers, Awards in markets • Many cases of needing additional calculations (eg. aggregation) • EMS Data: • Telemetry at point in time of SCED execution • All to-be-reported EMS telemetry is part of SCED calculations • Lodestar/DataAggregation Data: • One data element for actual metered generation output http://nodal.ercot.com 11

  12. Appendix 4 - Discussion of Source Data for Reporting • Approach being taken for Identified grouping of source system and data elements: • MMS Data: • Most of the reporting data is from MMS • All market submitted data and market results • Bids, Offers, Awards in markets • Many cases of needing additional calculations (eg. aggregation) • OPEN ISSUE OF TIME CONSTRAINTS FOR SCED TO EXECUTE • If too long, evaluate running development of Save Case extracts/reporting • EMS Data: • Telemetry at point in time of SCED execution • All to-be-reported EMS telemetry is part of SCED calculations • Lodestar/DataAggregation Data: • One data element for actual metered generation output http://nodal.ercot.com 12

  13. Appendix 5 Impact cost summary http://nodal.ercot.com 13

  14. Appendix 6- List of 2-Day Aggregate Reports Notes- - NPRR102 excludes Load related data from Disclosure Area reporting - Ancillary Services are system-wide and not part of Disclosure Area reporting - All of this data is reported in 60-day reports by QSE and Resource/Settlement Point http://nodal.ercot.com 14

More Related