Presentation is loading. Please wait.

Presentation is loading. Please wait.

International Standards Common Information Model (CIM) CIM for Market Extensions (CME) and Oasis David Becker, EPRI Presented at the NERC/NAESB Future.

Similar presentations


Presentation on theme: "International Standards Common Information Model (CIM) CIM for Market Extensions (CME) and Oasis David Becker, EPRI Presented at the NERC/NAESB Future."— Presentation transcript:

1 International Standards Common Information Model (CIM) CIM for Market Extensions (CME) and Oasis David Becker, EPRI Presented at the NERC/NAESB Future of Oasis Conference Washington DC 3/29/2005

2 Outline for CIM/Oasis II What is CIM? Why are Standards important? For Oasis? CIM Extensions for Market Operations (CME)

3 History of the Common Information Model (CIM) Late 1980s-Early 90s- Informal meetings of Industry focused on How to achieve open system design 1993-Formation of EPRI led CCAPI Task Force: One vendor did not have all solutions for a customer. Need for integration Initial Goals of CCAPI: –Provide common information model to facilitate information exchange –Enable use of plug in applications –Protect application investment –Framework for integration of legacy systems

4 Generator Load AC Line Company The Common Information Model Defines Power System Resources, Attributes and Relationships Control Area Operates Owns Company Supplies Energy for Busbar Connects to Provides Transmission for Controls

5 Changing Design of CCAPI in 90s Design focus changed from EMS control computer systems to Enterprise data exchange Expand to use new applications with plug and play USA technical team expanded with all world experts Standards Org (IEC) WGs of control centers, substations, distribution ALL adopt CIM as base

6 Important Milestones 9/1996: CIM initially submitted to IEC; CIM 10 final version accepted for standard in First major CIM Installation 1998 Component technology emerged in late 1990s. CCAPI calls them Component Interface Specs (CIS). Key to facilitating integration in a distributed environment Generic Interface Design (GID) initial design submitted to IEC 12/2001 after 2 yrs technical debate and design –SW developers create components w/o concern for underlying infrastructure –GID guides standard API for an application to exchange/access data

7 CIM Packages Domain Core Topology Energy Scheduling Reservation Core2 Financial Generation Wires LoadModel Meas Outage Protection SCADA Assets Documen- tation Consumer OAG Messages ERP Support

8 Concepts : Generalization/Inheritance Breaker: Specialization of Switch Switch: Specialization of Conducting Equipment ConductingEquipment: Specialization of PowerSystem Resource Breaker ConductingEquipment (from Core) PowerSystemResource (from Core) Switch PowerTransformer Naming ( from Core) ConductingEquipment (from Core) PowerSystemResource (from Core) Switch PowerTransformer Naming ( from Core)

9 Equipment Inheritance Hierarchy

10 CIM Class Model

11 Planning Customer Information Engineering Middleware (Integration Bus) CIM 10 Distribution Automation PI Historian Load Forecaster Dynamic Circuit Ratings GID GID GID GID GID = Standard Interface Specifications ENTERPRISE CAPABILITY Standards Position A Utility To Capitalize On Best Fitting Off-The-Shelf Products Transmission Grid Facilities Management GID GID EMS Control Center GID

12 Integration Bus Legacy Wrapper Programs Public Data ICCP Network ICCP SCADA Network User PCs CIM Server Public Data Public Data Legacy SCADA System Legacy System Programs OASIS? Control Center Application Program Interface (CCAPI ) as an Integration Framework (start out)

13 Component Execution System and Component Adapters (e.g., Integration Bus) Legacy Wrapper Programs Alarm Processor PI-Historian Generation Control Accounting/ Settlement Programs Public Data ICCP Network ICCP SCADA Network User PCs ProgramsCIM Server Network Applications Topology Processor Public Data Public Data Public Data Public Data Public Data Public Data Programs Public Data Distribution Management Systems Component Interface Legacy SCADA System Legacy System Programs Control Center Application Program Interface (CCAPI ) as an Integration Framework This buscan be spread across multiple entities

14 CIM today CIM 10 is ready for use. Has Widespread acceptance CIM for Asset Mgmt also robust and ready for your use Deployment of CIM Projects now ongoing worldwide Integration of CCAPI into Substations Integration of CIM for Market Extensions

15 Why International Standards Global world. Many vendors international Vendors willing to build products to STANDARDS Allows multiple designs to compete New applications can be installed Migration path more robust & flexible Lower vendor costs to produce and sell

16 TC 57 Slide Organization Standards & Technology ___________ ISO ODP ISO Security & Metadata Repository Stds IEEE ebXML IETF Internet Services W3C Web Services CIRED Open GIS DistribuTECH GITA T&D OPC Foundation EPRI CCAPI Project WG14 DMS SPAG WG13 EMS Object Mgmt. Group Component Container Technology _________________ CORBA (OMG) Enterprise Java Beans DCOM (Microsoft) WGs 3 & 10 Substations OAG Important Standardization Activities WG7 Control Centers TC57 WG9 Distribution Feeders EPRI UCA2 Project WG3 RTUs WG18 WG17 WG16 Market Ops WG15 Security

17 Initiative of CIM for Market Extensions (CME) Project FERC requested EPRI to extend the CIM architecture to support the SMD and facilitate markets EPRI initiated CIM for Market Extensions (CME) project with ISOs/RTOs,vendors –Made up of utility and industry organizations to support this initiative –Managed by Xtensible Solutions for EPRI –Focus on the Day-Ahead and Real-Time Market Processes to define extensions needed for the CIM data model to support these processes Goal of CME –Standardize information format and application interfaces to make the North American wholesale electricity market run efficiently, reduce seams issues and save substantial costs in the development of applications for each RTO Will allow RTOs to buy best-of-breed applications and communicate with Independent Transmission Organizations (ITOs) or other ISOs and RTOs in a standard information format Will allow marketers, Load Serving Entities (LSE), and Generator Serving Entities (GSE) to access information and bid into the RTOs preferred format

18 Scope of CME Project RTO A ISO DRTO C ISO B Generators Loads Marketers CIM extensions in scope for CME XML information exchange model and terms database – message standards to be developed as part of RTO/ISO Data Initiative Market, Load, Generation Participants CIM extension and information exchange model – Other Initiatives and/or Future Phase(s) Inter-ISO/RTO Messaging MIS SCUCSCED Settlement Intra-ISO/RTO Messaging RTO A

19 CME Phase 1 Deliverables EPRI Technical Report: CIM Extensions to Support Market Operations Phase 1: Day Ahead and Real Time Scheduling Applications ( TR ) –CIM representation of data requirements in table format with mapping to existing applications –Extended CIM UML model to support the SCUC/ED/LMP data requirements New Market Operations package Updates to existing CIM Packages Reuse of existing IEC and Packages –Created XML Schema for the Input/Output data Basis for the message standards defined for the SCUC application by the ITC Standards Collaborative

20 Phase 1 CIM UML Extensions New CIM Package created for Market Operations –Bid –Resource –RTO –Security Constraints –Clearing Results Updates to existing CIM Packages –Energy Scheduling –Financial Reuse of existing IEC and Packages –61970 – Core, Generation/Production, Measurements, others – Core2/Top Level and Activity Record

21 CME Phase 2 Deliverables EPRI Technical Report: CIM Extensions to Support Market Operations Phase 2: Day Ahead and Real Time Scheduling Applications (TR ) –Extended CIM UML model to support the SCUC/ED/LMP data requirements Network Analysis applications (e.g., State Estimator, Security Analysis, OPF, etc.) Ex-Post LMP Financial Transmission Rights (i.e., Congestion Reservation Rights) Facilitated Checkout (FCO) Updates to the CIM UML Rose model for Market Operations

22 Benefits Derived From CME Project Basis for defining standard messages for exchange of market operations data in support of SMD –Provides semantic layer for ensuring consistency in meaning and use of information exchanged to support market operations and reliability Facilitates implementation of market business processes –Provides architectural layer to map business terms to data definitions used in message payloads Basis for new RTO/ISO SMD development efforts –Ex: CAISO is using CME extensions on Market Redesign project as starting point for developing message payloads for information exchange between systems and applications Submitted to IEC for consideration as international standard –Could lead to adoption by European Transmission Operators

23 CME Phase 3 Prioritized Activities High Priority Standard message definitions –SCED and Ex-Ante LMP message standards –FCO – revisit other ISO/RTO requirements –Network Analysis and Ex-Post LMP –Financial Transmission Rights Market participant interaction - Upload electronic bids to RTO/ISO and download results. Market participant interaction - Settlement data exchange and True-Ups Plan and conduct a Workshop or Webinar on CME results for interested users (after Phase 2 message definition complete) High to Medium Priority Control Area seams-related data exchange –Applications include ramp data, Total Transmission Capacity (TTC), ATC, Available Flowgate Capacity (AFC), etc. that are exchanged among control areas

24 CME Phase 3 Prioritized Activities Medium Priority Network model maintenance component (i.e., complete model transfers, incremental model updates, and partial model transfers) Intelligent Alarming –Sharing relaxant relevant alarms with neighbors electronically Visualization –Information exchange to enable display of Market and Reliability data in a graphical form that will assist in decision making Low Priority Market monitoring information Plan for and conduct an Interoperability test in 2006 for CME standard messages developed on the extended CIM Market participant interaction – Outage reporting Develop a User Guide on how to use the CIM for market operations messaging.

25 CIM XML Interoperability Tests EPRI has sponsored six interoperability tests based on the CIM XML standards: –Six interoperability tests successfully completed exchanging real-world large scale models (12,000 bus) and several sample models (40 to 100 bus) December 2000: Orlando, Florida April 2001: Las Vegas, Nevada September 2001: Monterey, California July 2002: San Francisco, California November 2003: Cleveland, Ohio July 2004: Folsom,California –Validated the use and acceptance of this standard by suppliers who provide products to the electric utility industry –Test reports available from EPRI

26 CIM and Interoperability Tests Interoperability Tests very important Test # 6 completed in 7/2004 Results: Exchange ICCP Object IDs, Full model, Incremental updates, partial model, new validator tools, clean up items, etc –Include all transmission grid power system model (NERC) Requirements –Actual testing between vendors –Added distribution application plus applications from Control Centers, Substations, etc –CIM/GID/CIS progress as STANDARDS

27 CIM Status and Access Information CIM exists as ROSE model and IEC standard (MS Word) Complete CIM (61968, 61970, and Market Operations packages in UML) available on IEC CIM User Web site (www.cimuser.com)www.cimuser.com Also available for download Current CIM model (cim10_ mdl) RDF Schema Version for CIM Version 10 XML Message Schemas for messages EPRI published reports on Control Center Application Program Interface (CCAPI)Control Center Application Program Interface (CCAPI) Site includes CIM 10,IOPs #1-6, CME reports downloadable

28 CIM Status and Access Information Survey ( 2 years old) shows over 47 CIM installations in US and over 55 applications delivered. New survey to be done in 2005.( How do you count rabbits?) USA started 2+ years ahead of other countries Globally accepted now. Known implementations in process or done in Belgium, Brazil, China, France, Ireland, Jordan, Russia, Slovenia, South Africa, Spain, others(?)

29 New names of people to contact David Becker, EPRI Terry Saxton, Xtensible Solutions For general assistance : Angelica Kamau, EPRI


Download ppt "International Standards Common Information Model (CIM) CIM for Market Extensions (CME) and Oasis David Becker, EPRI Presented at the NERC/NAESB Future."

Similar presentations


Ads by Google