Common Information Model (CIM) accepted/implemented Globally- for operations, planning, markets, and throughout the Enterprise

Transcription

1 The Common Information Model (CIM) accepted/implemented Globally- for operations, planning, markets, and throughout the Enterprise David Becker, EPRI Presented at the 8 th International Workshop on Electric Power Control Systems Les Diablerets, Switzerland June 5-8, 2005

2 History of the Common Information Model (CIM) Late 1980 s-early 90 s- Informal meetings of Industry focused on How to achieve open system design for Control Centers 1993-Formation of EPRI led world 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 Expanded to ENTERPRISE Scope

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

4 CIM Packages Generation LoadModel Outage Protection SCADA Assets Documentation Wires Meas Financial Consumer Core2 Topology Energy Scheduling ERP Support OAG Messages Reservation Core Domain

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

6 Control Center Project PSS/E Included in Option C PSS/O (offline) UIB VDW/Substation Control Center Option C - PTLoad/Substation Existing - Future Power Models CIM Server Power System Models UIB PI Adapter EMS PI ICCP Archive Module Database CIM Not included in Option C

7 Results UIB EPRI PTLoad AMS/WMS (Maximo) OMS (TOTS) Others Utility Combined CIM/ Projects Equip & power Desktop Results Equipment Models GiA Power Models CIM Virtual Data Warehouse MMW Analysis Applications.. ODBC. ODBC Planning load flow (LF) Operations (LF) (offline) Power Models CIM Server Power System Models UIB PI Adapter PI EMS ICCP Archive Module Database CIM VDW/Substation Control Center Option C - PTLoad/Substation Existing - Future

8 Scope of CME Project Inter-ISO/RTO Messaging Intra-ISO/RTO Messaging Generators RTO A RTO A ISO B MIS Settlement Marketers ISO D RTO C SCUC SCED Loads 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)

9 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

10 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(?)

11 Main Conclusions The CIM/ Standards bring immediate value.choice of solutions; ability to migrate; proven by operations LOCAL REGIONAL ENTERPRISE Ems -Europe subs,distr,gen,custr -USA -Latin America -Asia Can NOT buy all systems from single vendor

12 Names of people to contact David Becker, EPRI Terry Saxton, Xtensible Solutions For general assistance: Angelica Kamau, EPRI

13 Additional Slides for Later The following slides will not be discussed at EPCC #8 but are provided for better understanding after conference.

14 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 1990 s. CCAPI calls them Component Interface Specs (CIS). Key to facilitating integration in a distributed environment Generic Interface Design () initial design submitted to IEC 12/2001 after 2 yrs technical debate and design SW developers create components w/o concern for underlying infrastructure guides standard API for an application to exchange/access data

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

16 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

17 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 ( 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) Site includes CIM 10,IOP s #1-6, CME reports downloadable

18 CIM and Interoperability Tests Interoperability Tests very important Test # 6 completed in 7/2004 Results: Exchange ICCP Object ID s, 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//CIS progress as STANDARDS

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