1 / 15

Texas Nodal NMMS/RARF Data Discussion By John Moseley, ERCOT, Network Modeling Group

Texas Nodal NMMS/RARF Data Discussion By John Moseley, ERCOT, Network Modeling Group. Background- Protocol requirements for model-related postings. Nodal Protocol references: Section 3.10.1 (3) , Time Line for Network Operations Model Change Requests [footnotes to table]

bennettb
Télécharger la présentation

Texas Nodal NMMS/RARF Data Discussion By John Moseley, ERCOT, Network Modeling Group

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. Texas NodalNMMS/RARF Data Discussion By John Moseley, ERCOT, Network Modeling Group 1 Texas Nodal

  2. Background- Protocol requirements for model-related postings Nodal Protocol references: Section 3.10.1 (3), Time Line for Network Operations Model Change Requests [footnotes to table] 2. Network Operations Model data changes and preliminary fidelity test complete by using the Network Operations Model test facility described in paragraph (3) of Section 3.10.4, ERCOT Responsibilities. The test version of the Network Operations Model will be available for market review and further testing by Market Participants. Section 3.10, Network Operations Modeling and Telemetry (8) ERCOT shall track each request received from TSPs and Resources via the NOMCR process, through implementation and final testing of the change. ERCOT shall notify each NOMCR requestor when the requested change is processed and implemented in accordance with Section 3.10.1, Time Line for Network Operations Model Change Requests, and ERCOT shall also provide the submitting TSP a link to a network model containing the change for verifying the implementation of the NOMCR and associated one-line displays. ERCOT shall post all NOMCRs on the MIS Secure Area within five Business Days following receipt of the NOMCR, consistent with Critical Energy Infrastructure Information (CEII) standards. Section 4.2.3, Posting Forecasted ERCOT System Conditions No later than 0600 in the Day-Ahead, ERCOT shall post on the MIS Secure Area, and make available for download, the following information for the Operating Day: (a) The Network Operations Model topology that includes known transmission line and other Transmission Facilities outages in the Common Information Model (CIM) format for the minimum Load hour and the peak Load hour; http://nodal.ercot.com 2

  3. Background (continued)-Posting of Network Operations Model Nodal Protocol references (cont’d) Section 3.10.4, ERCOT Responsibilities (4) …. ERCOT shall acquire model comparison software that will show all differences between the next production model and production environment model and shall post this information on the MIS Secure Area within one week following test completion. This comparison shall indicate differences in device parameters, missing or new devices, and status changes. (8) ERCOT shall make available to TSPs and other Market Participants, consistent with applicable policies regarding release of CEII, the full transmission model used to manage the reliability of the transmission system as well as proposed models to be implemented at a future date. ERCOT shall provide model information through the use of the EPRI and NERC-sponsored CIM and web-based XML communications. Section 3.10.7.1Modeling of Transmission Elements and Parameters (2) … ERCOT shall provide all names and parameters of all Transmission Elements to Market Participants posted on MIS Secure Area by 0600 each day. Section 3.10.7.1.4, Transmission and Generation Resource Step-Up Transformers (5) ERCOT shall post to the MIS Secure Area information regarding all transformers represented in the Network Operations Model. Protocol reference related to confidentiality Section 1.3.1.1, Items Considered Protected Information “Protected Information” is information containing or revealing any of the following: […] (k) Resource-specific costs, design and engineering data http://nodal.ercot.com 3

  4. NMMS RARF Discussion • Overview: • There has been much discussion about the RARF information that has been integrated into the ERCOT CIM Network Model. These issues have to do with the confidentially of some of the RARF Data. • The purpose of this discussion is to identify which pieces of RARF data concerning the resources should be considered protected. • The data presented on spreadsheet represents all of the ERCOT Network Model data currently pulled from the RARF for generation, it is currently assumed that transmission connectivity data is public (Line Data, Breaker/Switch Data, Capacitor/Reactor Data, Transformer Data, SVC Data, Series Device Data, Load Data (Station Supply), etc) <Manual Date> – <Manual Filename> 4 Texas Nodal

  5. NMMS RARF Discussion • Overview continued: • There are 92 items that ERCOT model uses from the RARF • 32 – General Resource Information • 15 – Non-Combine Cycle Plant specific (15 overwritten by Resource Parameter updates in MMS) • 24 – Combine Cycle Plant (15 overwritten by Resource Parameter updates in MMS) • 19 – Load Resource Related (10 overwritten by Resource Parameter updates in MMS) • 2 – Private Area Network <Manual Date> – <Manual Filename> 5 Texas Nodal

  6. NMMS RARF Discussion - General Resource Information <Manual Date> – <Manual Filename> 6 Texas Nodal

  7. NMMS RARF Discussion - General Resource Information <Manual Date> – <Manual Filename> 7 Texas Nodal

  8. NMMS RARF Discussion - General Resource Information <Manual Date> – <Manual Filename> 8 Texas Nodal

  9. NMMS RARF Discussion - Non-Combine Cycle Plant specific <Manual Date> – <Manual Filename> 9 Texas Nodal

  10. NMMS RARF Discussion - Combine Cycle Plant <Manual Date> – <Manual Filename> 10 Texas Nodal

  11. NMMS RARF Discussion - Combine Cycle Plant <Manual Date> – <Manual Filename> 11 Texas Nodal

  12. NMMS RARF Discussion – Load Resource <Manual Date> – <Manual Filename> 12 Texas Nodal

  13. NMMS RARF Discussion – PUN • Generating Units Part Of Private Area Network: • All units listed as part of the PUN are flagged as part of Private Area Network instance. • Loads Part Of Private Area Network: • All loads identified as PUN Loads are flagged as part of the Private Area Network instance. • The load schedules contain representative hourly weighted average of power consumption over a week long period. This data serves as an initialization values for the real time load adaptation performed in EMS. The values are then refreshed in the NMMS every 3 months based on the weighted averages of the same 3 month period 1 year ago. 13 Texas Nodal

  14. Considerations: • Consider Assumptions • TSPs will continue to receive the entire NMMS CIM model file • Recognition that the NMMS model does not give the next day load and resource plans for a power flow • For non-TSPs, is all RARF data deemed confidential by NATF? • Consider Options for Section 4 requirement: • Option 1- • Post entire NMMS CIM file (as is done for TSPs) • Option 2- • Post topology-only version of model (wires, ratings, connectivity- no resources data) • Option 3- • Filter out certain RARF data from NMMS CIM file 14 Texas Nodal

  15. Questions? 15 Texas Nodal

More Related