Role of CIM for Power System Model Exchange - ISO/RTO Exchanges with TOs

Transcription

1 Role of CIM for Power System Model Exchange - ISO/RTO Exchanges with TOs David Bogen Manager Transmission and Distribution Services Oncor Electric Delivery Presented By Margaret Goodrich, SISCO Practical Management and Implementation Guidelines for Common Information Model (CIM) Based Projects February 25-27, 2014 Melbourne, Australia

2 Who is Oncor Electric Delivery? About Oncor Oncor is a regulated electric distribution and transmission business that uses superior asset management skills to provide reliable electricity delivery to consumers. Oncor operates the largest distribution and transmission system in Texas, providing power to 3 million electric delivery points over more than 102,000 miles of distribution and 14,000 miles of transmission lines. While Oncor is a subsidiary of Energy Future Holdings, Oncor is a separate entity with a separate board that is comprised of a majority of independent directors. Facts and Figures Is the United States nation's sixth-largest transmission and distribution company, operating in a high-growth service area. Supplies electricity to approximately 7 million consumers, which is about one third of Texas s population. Operates in a service area in east, west and north central Texas with 401 incorporated municipalities and 91 counties. Serves cities that include the Dallas-Fort Worth area and surrounding cities, Odessa, Midland, Killeen, Waco, Wichita Falls and Tyler. Operates in the U.S.'s highest-growth region in electric demand, according to the North American Electric Reliability Council (NERC), with an underlying annual growth rate of 2.5 percent. Serves a steadily growing service area with an annual growth rate of 1.20% over the past five years in the number of premises served. 2

3 3

4 Who is ERCOT? The Electric Reliability Council of Texas (ERCOT) manages the flow of electric power to 23 million Texas customers - representing 85 percent of the state's electric load. As the independent system operator for the region, ERCOT schedules power on an electric grid that connects 40,500 miles of transmission lines and more than 550 generation units. ERCOT also performs financial settlement for the competitive wholesale bulk-power market and administers retail switching for 6.7 million premises in competitive choice areas. ERCOT is a membership-based 501(c)(4) nonprofit corporation, governed by a board of directors and subject to oversight by the Public Utility Commission of Texas and the Texas Legislature. ERCOT's members include consumers, cooperatives, generators, power marketers, retail electric providers, investor-owned electric utilities (transmission and distribution providers), and municipalowned electric utilities. 4

5 5

6 Oncor s ongoing projects implementing CIM Oncor s Smart Grid Mobile Work Force System Outage reporting Distribution Management System Meter Reading and Automation Oncor s Asset Management Equipment Management Historical Archives (i.e. load data) Oncor s Operations Network Model Manager Transmission Network Application Operator Training Simulator SCADA ERCOT S Network Model Manager Real-Time Network Model for SE, Security Applications, and Market applications (LMP) Transmission Planning data Contingency Database 6

7 So you want to. Coordinate Transmission Network Model exchanges between TOs and a ISOs/RTOs. You have been told that by implementing CIM you could do this. You have also heard that if you did this you would be entering a Jungle with many pitfalls and traps and would likely fail. 7

8 The Jungle 8

9 The story continues Well Oncor a TO and ERCOT an ISO started along this journey many years ago (about 2006) and managed put a CIM data exchange process into full production in 2009 that is supporting the ERCOT Nodal Market that went production in Oncor was not the only TO that participated in this, all TOs in the ERCOT region are required to submit Transmission Network Model changes to ERCOT using a CIM based solution. 9

10 How was this accomplished? With adequate planning and well defined process and requirements the Jungle can be groomed into a nice garden and the CIM exchange of large scale Transmission Network Models will work, even with many submitting entities. Now how was this accomplished? First decision is to agree that the ISO/RTO owns the model management process. Any other decision is prone for failure. The ISO/RTO must also acknowledge that without the support of the TOs the effort to achieve CIM based model exchange will fail. 10

11 The implementation process needs to be defined Joint activities between the TO and ISO Initial Planning, Design and Training Prototyping of data exchanges Testing of data exchanges (paper) Implementation of computer application Computer based testing of data exchanges during the implementation process. (early identification of issues) Written procedures (Parties must voluntary bind self's to the procedures) Training of data requirements Training of data validation rules Training for user interfaces (UI) Full System testing between all parties 11

12 Independent tasks at the TO and ISO Interface development Application testing Model Validation CIM Extensions to support internal data requirements This can impact the exchange between To and ISO 12

13 Initial Planning, Design and Training All parties must participate during the planning activity Training needs to be provide about project goals CIM standard training needs to be provide to all parties in the process Transmission Network Modelers Meta data modelers and designers IT support staff Vendors To provide a common understanding Project sponsors and management 13

14 Prototyping of data exchanges Define what data is being exchanged CIM Profile Design the interface(s) for the exchange of CIM data ERCOT has several to support all levels of users XML incremental RDF file exchange Using a UI provide by ERCOT to directly edit data Combination of the two. Develop Model validation rules 15

15 Testing of data exchanges (paper) Prior to start of coding and implementation, test the data exchange on paper. Many issues can be discovered during this process Reduces implementation cost by discovering data issues early. Clarifies what needs to be implemented. 16

16 Implementation of computer application Examples of implementation issues determined during planning phase Design process showed that a Time Base solution would be required. Each incremental data exchange will be treated as a time base project TO ownership is at the object level. Also needed to provide for joint ownership of objects Separate association for who operates the equipment. Can also be joint. Need to provide user interface to ERCOT s model manager for companies that are not implementing a CIM solution. Prototype implementation at every stage of the project. 17

17 Computer based testing of data exchanges during the implementation process. Test interfaces often and frequently during coding phase. This is critical to a successful implementation of the project. Early identification of issues allow for a painless resolution. Testing must include both the ISO and the TO. This provides for balance in the implementation process. Validation of the base-lined Transmission Network Model should be included during this phase of testing. 18

18 Don t forget training All parties involved in the modeling process or model exchange require training. Training of data requirements Training of data validation rules Training for user interface (UI) Training must be completed prior to allowing either the TO or ISO/RTO to submit model changes. 19

19 Full System testing between all parties This includes formal and in-formal testing of all features that provide TO and ISO exchange of data. Need a process in place to manage and track any reported defects. Some of the best testing occurs when the TOs actual start using the system to provide actual Transmission Network Model changes. Don t expect to subvert the working model. Fix any identified model issues as they are discovered Base line model should be valid before for system test occurs. 20

20 ERCOT had to develop more than one interface for external and internal exchange of models 21

21 TOs also need to design interfaces The TOs had many decisions to make that could impact internal process. 1. Adopt CIM to support internal transmission model development. 2. Only use the UI interface for submitting changes to ERCOT. 3. Implement a CIM Transmission Network Management application for developing the transmission model that would be submitted to ERCOT. 4. Do nothing and hire a consultant. 22

22 Oncor was already implementing a CIM Solution Oncor has installed a time-based CIM complaint Network Model Manager to support the Oncor s Advanced Application (State Estimation, Power Flow, and Contingency Analysis) network modeling requirements This system will produce the CIM-XML incremental files for each project that needs to be submitted to ERCOT and to support Oncor s internal real-time models. Will provide a single point for making changes to support both Oncor s and ERCOT s network model, It will support four different profiles: CPSM, Vendor s, Oncor s and ERCOT s. This system will be extended to support Oncor s Transmission Outage Application (TOA). 23

23 Oncor s tasks for implementation paralleled ERCOT s Because Oncor elected to implement fully compliant centralized CIM Transmission Network Model Manager, many of the steps that ERCOT followed during implementation also applied to Oncor. Oncor developed individual CIM profiles for the interface between ERCOT and internal applications. Required the ability to import the CIM incremental project files that ERCOT would be publishing. How to augment Oncor s centralized model with information that did not originate at ERCOT? Create a combined meta model (profile) that would support both ERCOT s and Oncor s modeling requirements and validation rules for all interfaces. 24

24 The Network Model Management System at both ERCOT and Oncor The Network Model Manger is an umbrella of applications used to manage, manipulate, prepare, validate, test, and provide consistent models to the all model-driven ERCOT operational, market and planning systems. Utilizes Common Information Model (CIM) standards for integration. Built around the Siemens EMA Information Model Manager (IMM) and Siemens PTI Model on Demand (MOD) Uses temporal based change methodologies to track time changes to the network models data and to project future conditions. Serves as the single point of entry and maintenance for the network model topology. 25

25 Can the Jungle become a Garden? 26

26 With planning and patience 27

27 Avoid the Pitfalls All parties must participate in the process with the objective of making the CIM Network Model exchange work. Be open when problems are discovered at either the TO or ISO/RTO. Work together to solve all common interface problems. Use profiles for defining the data that will cross each interface. Oncor does not need all of the information that ERCOT manages in their system and neither does ERCOT need all of the data that Oncor manages. 28

28 ERCOT depends on the Transmission and Resource Operators and Owners 29

29 Oncor also depends on ERCOT and the other TOs Oncor Expects ERCOT to: Publish the all network model changes applied to the ERCOT Transmission Network Model as incremental CIM projects. Manage the RDFIDs in a consistent manner. Not to change the meta model or validation rules without involving the TOs. 30

30 This is not a Fairly Tale.. 31

31 32