Download
slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
CIM in the Network Model Management System Joel Koepke Network Model Engineer, ERCOT PowerPoint Presentation
Download Presentation
CIM in the Network Model Management System Joel Koepke Network Model Engineer, ERCOT

CIM in the Network Model Management System Joel Koepke Network Model Engineer, ERCOT

250 Vues Download Presentation
Télécharger la présentation

CIM in the Network Model Management System Joel Koepke Network Model Engineer, ERCOT

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. CIM in the Network Model Management System Joel KoepkeNetwork Model Engineer, ERCOT EMS Users Conference 1 September 23rd – 26th

  2. AGENDA • About ERCOT • NMMS Overview • ERCOT CIM • Submission of Model Updates • Model Creation EMS Users Conference 2 September 23rd – 26th

  3. About ERCOT • Grid covers 75% of Texas’ land and serves 85% of Texas’ load • 38,000 miles of +60kV transmission lines • 750 miles of 345kV lines added since 1999 • 70,000 MW of total resources • 26,000MW of generation added since 1998 • 63,056 MW peak load (8/17/2006) • 5400 Bus Model ERCOT EMS Users Conference 3 September 23rd – 26th

  4. Market Redesign – Going Nodal! Zonal Market • Insufficient price transparency • Resources grouped by portfolio • Indirect assignment of local congestion • 5 CMZ Zones Nodal Market • Improved price signals • Improved dispatch efficiencies • Direct assignment of local congestion • 4000 Nodes EMS Users Conference 4 September 23rd – 26th

  5. ERCOT’s CIM Catalyst: The Network Model Management System EMS Users Conference 5 September 23rd – 26th

  6. CIM Common Information Model (CIM) • CIM is… • An information model that describes real-world objects and their interrelations within the electric power industry • A format for exchanging information • Why is it important? • Provides a standard way of depicting data • Enables the integration of multiple applications and vendors • Facilitates bulk and incremental model exchange EMS Users Conference 6 September 23rd – 26th

  7. ERCOT’s CIM Catalyst The Network Model Management System • What is it? • The system that will perform all modeling functions in the Nodal market • Submission of modeling changes • Storage and validation of the model data (Operations and Planning) • Creation of all required models for downstream applications • Why? • The Nodal Protocols contain requirements which significantly change ERCOT’s current modeling process • Need “Future” models • Modeling should be consistent (Operations vs. Planning) • Must accept CIM inputs and produce CIM outputs EMS Users Conference 7 September 23rd – 26th

  8. ERCOT’s CIM Catalyst NMMS - Key Requirements • Time-based modeling • A change that will happen in 5 months can be modeled today. • A model that represents 5 months in the future can be created today. • Generate all models for all processes (and Vendors) • Repository for all model information • Both full and incremental CIM files • Accept incremental modeling updates. • Submitted by the Market Participants (TSP, QSE, LSE) EMS Users Conference 8 September 23rd – 26th

  9. NMMS Overview EMS Users Conference 9 September 23rd – 26th

  10. ERCOT CIM – Namespaces and Profiles • Required non-CIM attributes must be added to a separate namespace • There are 3 namespaces that make ERCOT CIM • CIM • SPC – Siemens • ETX – ERCOT EMS Users Conference 10 September 23rd – 26th

  11. Submission of Modeling Changes All Modeling Changes Will be Made by The Market Participants (Not ERCOT) • Submitted Via a Web-Based User Interface • Actual modeling will be done by the MPs. • MPs can import CIM incremental files, but it is not required. • “But wait!” says the Market Participant • “We cannot export incremental CIM files.” • Several MPs are in the process of developing this capability. • “OK we can export CIM, but not ERCOT CIM.” • The extra attributes can be updated on import. • “We have different names than ERCOT.” • ERCOT will set up a naming registry EMS Users Conference 11 September 23rd – 26th

  12. Model Creation • Incremental Changes– All model updates are stored as a packet of database modification commands • Effective Date– Each incremental change is given an energization date • Future Models – Applying dated incremental changes to a base model creates a model representing a future date Time-BasedModeling EMS Users Conference 12 September 23rd – 26th

  13. Planning Models • Creating a Planning Model • An Operational model is created for the future date • This model is passed through a “topology processor” to change the breaker/switch model into a bus/branch Planning model • Planning incremental changes are then applied to the model to make it reflect the future date The NMMS Will Create All Planning Models From Operations Models EMS Users Conference 13 September 23rd – 26th

  14. NMMS Overview - Again EMS Users Conference 14 September 23rd – 26th

  15. Sending Data Downstream • All Operations models will be provided in ERCOT CIM/XML format • Full Operations Models will be sent to • EMS (AREVA) • MMS (ABB) • OS (ABB) • Postings • The AREVA EMS will also accept incremental modeling changes • Decrease import time • PSS/E cases will be sent to all Planning applications EMS Users Conference 15 September 23rd – 26th

  16. The End EMS Users Conference 16 September 23rd – 26th

  17. NMMS Overview EMS Users Conference 17 September 23rd – 26th