NMMS Overview Network Modeling using CIM John Moseley Ph.D., P.E. Principal Engineer, Model Architecture and Integration Wednesday, November 8, 2017

Transcription

1

2 NMMS Overview Network Modeling using CIM John Moseley Ph.D., P.E. Principal Engineer, Model Architecture and Integration Wednesday, November 8, 2017

3 The ERCOT Region The interconnected electrical system serving most of Texas, with limited external connections 90% of Texas electric load; 75% of Texas land 71,110 MW peak, August 11, 2016 More than 46,500 miles of transmission lines 570+ generation units ERCOT connections to other grids are limited to ~1,250 MW of direct current (DC) ties, which allow control over flow of electricity 30 MW with CFE at Eagle Pass 100 MW with CFE at Laredo 220 MW with SPP 600 MW with SPP 300 MW with CFE at McAllen 3

4 Current Records Peak Demand Record: 71,110 megawatts (MW) Aug. 11, 2016, 4-5 p.m. Recent Monthly Peak Demand Records Weekend Record: 68,368 MW Saturday, July 29, 2017, 4-5 p.m. Winter Peak Record: 59,650 MW Jan. 6, 2017, 6-7 p.m. Wind Generation Records (instantaneous) Output: 16,141 MW March 31, 2017, 8:56 p.m. Penetration (load served): 50% March 23, 2017, 3:50 a.m. Total Load = 28,780 MW 2017 January: 59,650 MW (Jan. 6, 6-7 p.m.) April: 53,486 MW (April 28, 4-5 p.m.) May: 59,264 MW (May 26, 4-5 p.m.) June: 67,633 MW (June 23, 4-5 p.m.) July: 69,496 MW (July 28, 4-5 p.m.)* 2016 August: 71,110 MW (All-time record) September: 66,949 MW (Sept. 19, 4-5 p.m.) October: 59,864 MW (Oct. 5, 4-5 p.m.) December: 57,932 MW (Dec. 19, 7-8 a.m.) *New records are preliminary, subject to change in final settlement 4

5 Evolution of the Network Model Management System

6 Operations Model ( Zonal Market ) SERVICE REQUEST GARF ERCOT Operations Model Database Real-Time and Future Analysis ERCOT Market and Registration Database Non-Temporal model, updated every two weeks, where modelers worked on a single common model in a single common work space No links to planning models, congestion revenue models, or other systems, all systems had independent data streams, mainly paper forms, Excel files, and .

7 Problems with the Previous Process Differences in Planning and Operation Model topologies, element attributes, and naming conventions. Single Operations Model was only valid for 2 weeks in advance and most current Planning Models were for following year leaving a study gap. Dynamic cases built from Planning Cases, but used to support decisions made in real-time. Market Information not integrated in Operations Model. Future one-lines and contingency files not available to support future studies in Outage Coordination. Change request interface used by Market Participants was very inefficient the best at the time was just a electronic form requiring manual entry by ERCOT. Market Participants had no access or visibility to the Model Database. Model database and Outage Scheduler had no dynamic link resulting in broken outages and no ability to outage future equipment.

8 Impetus for NMMS: In 2004, ERCOT began a complete system redesign to migrate from a zone-based market model to a node-based market model. This redesign necessitated by protocol requirement a high-level of model consistency between all applications used to control the grid. a centralized data warehouse with an all-encompassing model schema to contain, maintain and deliver consistent model data representative of the Texas electric grid for all model driven activities including, Energy Management Market Management System Planning Outage Scheduling Congestion Revenue Rights Auctions ERCOT Public 8

9 Vision of NMMS? In Short: One system manages all model data: <Manual Date> <Manual Filename> 9 Texas Nodal

10 Design of Network Model Management System

11 Design Objectives of NMMS? The Network Model Management System (NMMS) needed to be an umbrella of applications used used to manage, manipulate, prepare, validate, test, and provide consistent models to all model-driven ERCOT operational, market and planning systems. NMMS would serve as the single point of entry and maintenance for the network model topology used by external ERCOT market participants. Use temporal-based change methodology to track, with time, changes to the network models data and to project future conditions. Utilize Common Information Model (CIM) standards for integration.

12 Identified Data-Flows

13 NMMS Supports Temporal Based Modeling Understand that changes are constantly being made to the model data. These changes expressed as incremental CIM. Time Based Modeling Nov 8, :00 am Sep 30, :00 am Sep 1, :00 am Sep 1, :00 am Sep 1, :00 am Jul 20, :00 pm Jul 20, :00 pm Base Model

14 Data Flows EMS External UI XML envelopes using Incremental CIM Files JBOSS Incremental CIM Files RELATIONAL DATABASE APP Full CIM Models MODEL VALIDATAION Full CIM Models Full CIM Models MMS Full CIM Models Congestion Revenue Rights Model Topology Processor Bus-Branch Models System Planning

15 Functions for Model Types Downstream systems loaded with models Network Operations Model Planning Model CRR Model Dynamics Model Energy MS Market MS Steady State Analysis State Estimator Day Ahead Outage Coordination RT Voltage Stability Future Year Steady State Analysis Production Cost Analysis Voltage Stability Generation Interconnection screening studies Congestion Auction Derived from Steady State Model Future Stability Analysis

16 Where we were and where we are: Since 9/1/2009 NMMS (Utilizing the CIM Standard) is the primary front end to enter network model changes by ERCOT s Market Participants and by ERCOT staff to manage, validate, build & provide models downstream Since 6/1/2012 NMMS is the source of record for planning models and planning model changes used by ERCOT s Market Participants and by ERCOT staff to build future planning cases (Utilizing the CIM Model with ERCOT extensions for Topology Processing). Planners are now using NMMS to build base models for 5-year studies The NMMS 2.0 went live 5/9/2017 and has been in stabilization since then, with the final patch related under the upgrade project pushed into production last week. 16

17 NMMS Upgrade Project just completed Rebuild Project Tracker and Coordinator (PTC) utilizing a CIM-like Structure Incorporate more of ERCOT processes into SGEM Enhance CR tracking, notification, and add new messaging system NEW - SGEM Graphics Model Editor utilizing the Incremental CIM standard New graphical editor to allow modeling and one-line creation/maintenance Includes current tree view NEW - Validation Editor UI Allow easier modification and viewing of Level 1 validation rules Adds Sanity and Fidelity rule editing All validation rules are written against the CIM model NEW - Model Builder UI New method to export model data into CIM-XML format Replaces functionality that is part of current PTC Separated Topology Processor Independent application, will read CIM-XML file instead of using the relational database Makes use of Siemens ODMS product Integrated One-Line Maintenance into IMM One-line Maintenance in NMMS using the CIM standard Enhanced Contingency Creation Process All contingencies are explicit defined using the CIM standard Storage of all contingencies changes as incremental CIM changes. ERCOT Public 17

18 Fun Facts NMMS 1.0 (fun is a subjective term): Our first submission on 1.0 was at 8/30/2009 9:48 AM from re-rate a 345kV line. The last submission on 1.0 was at 5/3/ :37 AM to re-rate a 69kV line. During the 2,805 days of operation, we fully processed 30,747 initial CR submissions that resulted in 24,910 finalized NOMCRs containing model changes. The total number of instances of data (lines, breakers, transformers, etc.) at NMMS 1.0 Go-Live was 2,245,540, at the end it was 2,688,231. But that doesn t tell the whole story. Of those original 2,245,540 data instances, 322,914 were modified or changed, 672,576 were completely removed, and 1,115,268 new instances of data were added. This means that only 55% of the instances of data in the original model are still there, and when you add in all of the modeling since go-live, less than 45% of the current model is original. With NMMS 2.0, primarily because of housing the one-lines in the NMMS, we are going live with 3,577,618 instances of data in NMMS 2.0 or about a 60% increase vs. the NMMS 1.0 go-live. Since NMMS became the date source for EMS and MMS (December 2010), we have provided roughly 715 models (339 Production Models, 288 Market Models, 88 Other) All of this was done in on CIM-based system. The database, the files, the changes. All expressed as CIM 18

19 CR Process

20 CR State Diagram Updated 08/22/2017 CAMR Start Proposal Withdrawn T25 T27 T36 Archived T42 In Production Starting Point Ending Point T9 T10 T1 CAMR Saved T2 T12 CAMR Response Received T13 Supplemental Instruction Requested XXX T24 Rejected ICR Accepted T26 Withdrawn T41 Approved for Production T40 Full Model Processing NOMCR Processing CAMR Processing System Action MP Action ERCOT Action IM Messaging Proposed XXX T11 T14 T35 T44 T46 T8 T3 Accepted for Modeling T7 XXX T15 T6 Deleted Submission T29 Additional Action Required XXX Additional Action Requested Testing Complete T38 T33 Submitted Resubmitted T47 T4 Modeling Completed T5 T16 T19 T18 T20 T3 T21 T28 T47 T32 T48 T34 Incorporated Model Build T31 XXX NOMCR/ ICR Start T17 Saved Received T30 Approved For Testing 20

21 IMM modeling of State Diagram Process is Modeled in IMM as series of states, transitions and tasks. Basic function for State Change: Model Coordinator (MC) looks at the current state, and assigns a Action Plan Action Plan consists of a number of tasks linked to a notification mechanism to notify the assigned personal. Upon Notification, Assigned personal logs in, performs task and marks task as complete When all tasks are complete, MC receives notification and process completes until tasks are complete. 21

22 IMM communications Tasks are assigned to Assignee Groups People that are associated with those groups will receive notifications for assignments As state changes occur, notification are sent out to the equipment owners and operators 22

23 5 Levels of Validation Prior to data Submission: 1. Automatic Validation -- Automatically by NMMS (approx. 2,000 CIM-Based Rules) CR Submission 2. Sanity Check and Visual Inspection 3. Single NOMCR check for Power Flow Readiness 4. Power Flow and Contingency Analysis 5. LMP (Locational Marginal Price) Verification Production Model Slide 23

24 Summary Historical Method Proprietary internal format Proprietary internal format Proprietary internal format Proprietary internal format Proprietary internal format

25 Summary Current Method Every vendor looks at the CIM standard, maps it to their internal data structures and writes a CIM Importer that conforms to the CIM standard. Network Model Management System Page - 25

26 Add Schema Summary Model Extensions CIM is extendable Vendor can program to standard Integration costs are less Industry can move forward rapidly Requirements for Solar Modeling Solar Forecaster Vendor supplies Network Model Management System

27 Q/A 27 27