1 / 10

Texas Nodal Follow-up on Resource and Registration Data for TPTF April 2, 2007

Texas Nodal Follow-up on Resource and Registration Data for TPTF April 2, 2007. Resource and Registration Data.

barbaragriffith
Télécharger la présentation

Texas Nodal Follow-up on Resource and Registration Data for TPTF April 2, 2007

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 NodalFollow-up on Resource and Registration Data for TPTFApril 2, 2007 http://nodal.ercot.com 1

  2. Resource and Registration Data • Upon review of the Registration Approach document at the 3/22/07 TPTF meeting, ERCOT was requested by TPTF to provide an overview of which systems are receiving Resource data from the market • This next few slides provide a summary of how ERCOT plans to receive Resource data and the workflow through ERCOT systems http://nodal.ercot.com 2

  3. Registration • ERCOT Registration system will comprise of a combination of Application solutions • Siebel will be used to store the MP Registration information and business processes (as is today) • New Automated interfaces are being created to push information between systems for consistency and uniformity • NMMS will be used to store Resource Parameters, limits, and default value information • MMS will be used to change selected Resource Parameters (eg HSL, LSL, Ramp rates, etc) • MIS will be used to expose MMS displays to change Resource Parameters http://nodal.ercot.com 3

  4. Existing Registration Workflow • MP Submits GARF (Generation Asset Registration Form) through email or fax • Client Services manually inputs to Siebel MP Parameters (e.g. unit name, relationships, effective date, contact information) • All interfaces of data entry are manual • GARF resource parameters, limits, and default values input to Lodestar, EMS/MOS http://nodal.ercot.com 4

  5. Proposed Registration Workflow • MP Submits GARF (Generation Asset Registration Form) through email or fax • Client Services manually inputs to Siebel MP Parameters (e.g. unit name, relationships, effective date, contact information) • Automated interface passing MP Parameter information to downstream systems • GARF Resource parameters are passed to NMMS • NOMCR submitted by ERCOT to input Resource parameters, default values, and limits • Automated CIM/XML Model interface transfers resource parameter defaults, and limits to MMS • MMS exposes resource parameters to MPs through MIS pages • Updates to MMS resource parameters through MIS/Application interfaces http://nodal.ercot.com 5

  6. Resource and Registration Data • The following Resource data is to be stored in Siebel/Registration • Resource Name • High/Low Reasonability Limits • MW amounts provided by QSE or Resource Entity define an out-of-bounds value for ERCOT systems • Qualified Facility Status • Resource Type (Gen/Load) • Resource Sub-Type • For generic costs/caps- Nuclear, Hydro, Combined Cycle <90MW, Gas Steam Reheat Boiler, etc • Other info: • Resource Ownership and QSE • Status (Active/Inactive) • Certification dates • Sub-Type (Settlement types: <90MW Gas Turbine, etc) • Fuel Type, Alternative Fuel Type • Data is communicated to ERCOT through registration application process in GARF via Seibel eservice for uploading documents http://nodal.ercot.com 6

  7. Resource and Registration Data • Resource Parameter static data (initial GARF submission) will be stored in Network Model and Management System (NMMS) • Topological Location • Unit Parameter information • Resource Parameter data will be input to NMMS via the NOMCR process by ERCOT • Data will be transferred to MMS via CIM/XML Model file http://nodal.ercot.com 7

  8. Resource and Registration Data • The following Resource data is to be communicated and stored in the Market Management System (MMS) • COP submission elements as defined in 3.9.1(4), including • Resource Status (ONRUC, ONREG, etc) • HSL/LSL • HEL/LEL • A/S Capacities • etc • Resource Parameters (for Load and Generation Resources) • Normal and Emergency Ramp Rate Curves • Min On/Off-line Times • Hot/Cold/Int Start Times • Max Weekly Starts • Etc http://nodal.ercot.com 8

  9. Resource and Registration Data • For EMS, all ICCP data will be communicated electronically in accordance with protocol section 6.5.5, Real-Time telemetered data http://nodal.ercot.com 9

  10. Resource and Registration Data • Open Issues still being worked • Combined Cycle • Register combined cycle plant in Siebel • Store CC Configurations- MMS or NMMS • Store CC Elements- MMS or NMMS • Transitional Matrix for Configurations- MMS capability being assessed • Load Resources • Register site as single Resource • How to model different configurations? • Armed Breaker-> Load Resource • Unarmed Breaker-> Controllable Load Resource http://nodal.ercot.com 10

More Related