1 / 75

CCAPI Project Status Update EMS Users Group Pittsburgh, Pennsylvania March 13, 2000

Terry Saxton Xtensible Solutions, Inc. Minneapolis, Minnesota tsaxton@worldnet.att.net. CCAPI Project Status Update EMS Users Group Pittsburgh, Pennsylvania March 13, 2000. Topics. Introduction and Background Objectives and Scope What’s Changed New Reference Model CIM Status

hisa
Download Presentation

CCAPI Project Status Update EMS Users Group Pittsburgh, Pennsylvania March 13, 2000

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Terry SaxtonXtensible Solutions, Inc.Minneapolis, Minnesotatsaxton@worldnet.att.net CCAPI Project Status Update EMS Users GroupPittsburgh, PennsylvaniaMarch 13, 2000

  2. Topics • Introduction and Background • Objectives and Scope • What’s Changed • New Reference Model • CIM Status • Interface Specifications • WG13 Status • Conclusions CCAPI Project Report

  3. CCAPI Original Objectives • Plug compatibility • Definition: The ability to easily install, or “plug in”, applications into different electric utility control center platforms. • Idealistic View: Enable shrink-wrap packages, as in personal computer marketplace. • Realistic View: Greatly reduce the costs to install an application into a control center platform • End Result • Enable user to build EMS via plug-and-play CCAPI Project Report

  4. CCAPI Task Force created • Create Guidelines or Standards to enable plug-compatibility • Ensure that standards are compatible with developers’ products • i.e., standards support vendor’s data base and middleware technology • Create Standards that address user needs • i.e., enable solutions to real user problems CCAPI Project Report

  5. IEC TC57 WG13 Created • Create IEC standard interface specifications • For plug-in applications in EMS or similar systems • Use EPRI CCAPI TF work as basis for standards • Incorporate TC57 National Committee needs as well CCAPI Project Report

  6. Topics • Introduction and Background • Objectives and Scope • What’s Changed • New Reference Model • CIM Status • Interface Specifications • WG13 Status • Conclusions CCAPI Project Report

  7. What Has Changed Since Early Beginnings • New user needs as result of Utility restructuring and network security initiatives • Combine transmission and distribution into Wires Group • Need to integrate legacy EMS/SCADA systems with DMS • Leads to need for enterprise-wide integration strategy • Need to exchange information with other sites for security and open access • Need common power system model • Need common information exchange format CCAPI Project Report

  8. The Integration Of Systems Is Complex... Customer Information EMS Control Center Customer Interface Distribution Automation Engineering Work Management Facilities Management Planning CCAPI Project Report

  9. ...This Is Simpler... Customer Information EMS Control Center Customer Interface Middleware Distribution Automation Engineering Work Management Facilities Management Planning CCAPI Project Report

  10. Interface Standards are Key Customer Information EMS Control Center Customer Interface IntegrationBus Distribution Automation Engineering Work Management Facilities Management Planning = Standard Interface Specifications CCAPI Project Report

  11. Role of Standards • Minimizes effort required for interoperability between applications and systems • Semantics • Syntax • Services • Requires only one transformation at application interface to interoperate with multiple applications • Two main types: • Software industry • Utility specific CCAPI Project Report

  12. Coordination Among Standardization Activities Standards & Technology ____________ ISO ODP IEEE CIRED Open GIS DistribuTECH GITA T&D OpenApplicationGroup Component Container Technology _________________ CORBA (OMG) Enterprise Java Beans DCOM (Microsoft) TC57 Coordinating Group WG14 DMS WGs 10,11,12 Substations WG13 EMS Utility Integration Bus EPRI CCAPI Project Object Mgmt. Group CCAPI Project Report

  13. IEC TC57 WG14: System Interfaces for Distribution Management • Provides message-based inter-application integration framework and interface standards for DMS • Major effort to ensure requirements are compatible with: • CCAPI integration bus approach • CIM with extensions for DMS • Open Applications Group standards • and complementary to WG13 standards CCAPI Project Report

  14. An Integration ArchitectureIs Needed First • Provides For An Adaptable Utility Infrastructure • Partitions Application Systems Based On: • Things That Are Stable • Standard Component Interfaces • Things That Can Be Controlled • Middleware & Application Products • A Stable Basis For Enterprise-Wide Integration • Transcends The Life Cycle Of Individual Application Systems And Middleware CCAPI Project Report

  15. CCAPI Scope - Original Common Information ModelCIM CIM Utility B Control Center Utility A Control Center ICCP Message BusCDA Message BusCDA • CASM • 870-5 • ICCP Substation CCAPI Project Report

  16. IEC Standards and CCAPI Scope Today Common Information ModelCIM (WG13 and 14) Utility B Control Center Utility A Distribution Systems Utility A Control Center Integration Bus ICCPWG07 InterfacesWG14 InterfacesWG13 • CASM/GOMSFE (WG 10-12) • 870-5 (WG03) • ICCP (WG07) Substation CCAPI Project Report

  17. What Has Changed Since Early Beginnings • Software industry undergone evolution Top-down modular design => Object-oriented design => Component-based architectures • Examples: OMG CORBA Component Model Microsoft DCOM Sun Enterprise Java Beans • CCAPI standards need to embrace and build on these trends to support EMS vendor products CCAPI Project Report

  18. Impact on CCAPI Project • Guidelines document needed updating, specifically: • Reference model => Build on component models Show role of CIM • CIM => Object-oriented model in UML Extensions to support new scope Minimal impact on content • Interface Specifications (MBI, CDA) => Component Interface Specifications (CIS) CCAPI Project Report

  19. Topics • Introduction and Background • Objectives and Scope • What’s Changed • New Reference Model • CIM Status • Interface Specifications • WG13 Status • Conclusions CCAPI Project Report

  20. Revised Reference Model • New model based on component technology • Software industry (including EMS vendors and suppliers of EMS applications) embracing component-based architectures. Examples: • CORBA component model • Sun’s Enterprise Java Beans • Microsoft COM/DCOM • Key to plug-and-play in a distributed computing environment • Focus is on definition/standardization of component interfaces CCAPI Project Report

  21. CCAPI and IEC 61970 Reference Model

  22. Data Access Services CCAPI Project Report

  23. CCAPI as an Integration Framework CCAPI Project Report

  24. Integration Framework for WG14 = IEC 61968 Interface Trans Wires Model Dist Wires Model DAC VRU Information Exchange Model Planning Outage Management Distribution Automation EMS CIS Interface Adapter Interface Adapter Interface Adapter ... IEC 61968 Compliant Middleware Services Event History Human Resources Maint. Analysis Diagnostic Tools Work Management GIS Financial CCAPI Project Report

  25. Integration Bus Implementation Strategy • Implement Integration Infrastructure That Meets IEC 61968 and 61970 Requirements • Use COTS middleware for bus technology • Incorporate process that brings in applicable models: CCAPI/CIM, UCA/GOMSFE, OAG, and others. • For Interface Standards, Participate (Directly And Through Suppliers) In Utility Industry Standards Activities • Gather information & influence the development of these standards CCAPI Project Report

  26. Integration Bus Connector Architecture Wrapped Application Application Local built as supported Unwrapped Component "Component" presents itself as protocol. Application {properties, events, methods} Wrapper per a standard component model (EJB, CORBA, COM+) with CIM-compliant semantics Application Domain Adapts local protocol directly to integration Integration Domain bus environment. Adapts component model to integration Component Custom or bus environment. Adaptor Adaptor Bus Administration Transforms messages into the Connector Transformer public information model. Information Exchange Mdl Integration Connects component instance to correct Wiring Bus Client destinations per wiring configuration. Configuration Message Delivery via Integration Bus Server(s) CCAPI Project Report

  27. Enterprise Application Integration • EAI is not equal to Messaging (or MOM). Messaging is *only* the plumbing. • EAI framework description includes • process automation • state-management • real-time decision support • connectors/adapters • event channels • content-based routing CCAPI Project Report

  28. Dedicated EAI solution vendors • Active Software • NEON • CrossWorlds Software • Vitria Technology • TIBCO CCAPI Project Report

  29. Vendors offering parts of EAI solutions • TSI (Mercator) • STC • BEA Systems • Forte Software • IBM • SISCO • CES CCAPI Project Report

  30. Vendors offering integration platforms • Oracle • SAP • PeopleSoft • Microsoft CCAPI Project Report

  31. Topics • Introduction and Background • Objectives and Scope • What’s Changed • New Reference Model • CIM Status • Interface Specifications • WG13 Status • Conclusions CCAPI Project Report

  32. The Common Information Model (CIM) • A Tool To Enable Integration In Any Domain Where A Common Power System Model Is Needed • Model Includes Public Classes, Their Attributes, And Relationships to represent utility objects • The Classes (Objects) Are Abstract And May Be Used In A Wide Variety Of Applications • Useful: • As Inspiration For Logical Data Schemas • To Define Information Exchange Models CCAPI Project Report

  33. Example of CIM Class Diagram and Use of Unified Modeling Language (UML) PowerSystemResource ( from Core) HasA MemberOf PowerTransformer TapChanger HasA HeatExchanger 0 0 ..* ..* Contains HasA 1 1 ..1 ..1 0 0 ..1 ..1 1 1 ..1 ..1 HasA HasA TestedFrom HasA 1 1 ..1 ..1 Tested TestedFrom WindingFor 1 1 ..* ..* 1 1 ..1 ..1 TransformerWinding 0 0 ..* ..* WindingTest ConductingEquipment TestedTo ( from Core) 0 0 ..* ..* 1 1 ..1 ..1 Tested TestedTo CCAPI Project Report

  34. CIM (Common Information Model) Packages <<Global>> Wires LoadModel Domain SCADA Topology Core Outage Generation Meas Financial Energy Reservation Protection Scheduling Asset CCAPI Project Report

  35. Package Definitions • IEC 61970 Part 301 • Core • Domain • Topology • Wires • LoadModel • Measurement • Generation/Production • Generation/GenerationDynamics • Outage • Protection • IEC 61970 Part 302 • Financial • EnergyScheduling • Reservation • IEC 61970 Part 303 • SCADA CCAPI Project Report

  36. 61970 Part 301 • Core (new) • Contains the core PowerSystemResource and ConductingEquipment entities shared by all applications. • Topology (new) • Extension to the Core Package that models Topology information independently of the other electrical characteristics • Wires • An extension to the Core and Topology package that models information on the electrical characteristics of Transmission and Distribution networks. CCAPI Project Report

  37. Part 301 (Cont.) • Measurement (new) • Entities that describe dynamic data exchanged between applications • Outage (new) • Extension to the Core and Wires packages that models information on the current and planned network configuration. • Protection (new) • Extension to the Core and Wires packages that models information for protection equipment including relays. CCAPI Project Report

  38. Part 301 (Cont.) • LoadModel (no change) • Generation (no change) • Production (no change) • GenerationDynamics (no change) • Domain • Definitions of primitive data types, used by all CIM packages and classes CCAPI Project Report

  39. 61970 Part 302 • Business process related entities with associations to the appropriate part 301 classes. • Financial • Company and SubControlArea would be part of the Core package in part 301. • Sub-types of Company and SubControlArea and more associations defined here • Models for settlement and billing - legal entities in agreements • EnergyScheduling • Reservation CCAPI Project Report

  40. 61970 Part 303 and 61968 for DMS • 61970 Part 303 • SCADA • Entities specific to SCADA and Alarm processor applications that are not used by other applications. • 61968 Assets ModelWG14 • Company, jobs, people, authorities,vehicles ,computers, conducting equipment, work management, outage management to support real-time operations CCAPI Project Report

  41. Harmonization with WG10-12 and others • All Elements To Be Added To The CIM Data Dictionary Are Intended To Be Consistent With: • TC57 WG 10/11/12 Standards (Based On The UCA2/GOMSFE) • The OAG. • It Is Recommended That Consideration Be Given For Generalizing The “WG13/WG14 CIM” To Become The “TC57 CIM” CCAPI Project Report

  42. What Does CIM Compliance Mean • The CIM is not a database - it is an information model (I.e., meta data) • CIM compliance means that at the public interface the data representation complies with the CIM in terms of • Semantics - Naming and meaning of data • Symantics - data type • Relationships - relation to other parts of the CIM, so that the data relationships can be navigated CCAPI Project Report

  43. CIM Compliance • CIM compliance does not mean: • There is a database organized exactly like the CIM class diagrams • All aspects of the CIM are provided for CCAPI Project Report

  44. CIM Status • Current Version u08b • Rational ROSE for model definition, maintenance • Rational SODA for MS Word documentation • Part 301 sent to IEC as CDV on 11/23/99 • Part 302 sent to IEC as CD on 12/10/99 • Part 303 SCADA being revised • Part 501 CIM Schema • CIM in XML with RDF Schema • WG14 developing new CIM packages for distribution systems • Many projects based on CIM CCAPI Project Report

  45. Utilities Implementing CIM/CCAPI Standards • Illinois Power • Kansas City Power and Light • Florida Power and Light • SCE • Duquesne Power • NERC Security Coordinators • Power System Model data exchange • Based on CIM XML and RDF Schema • Many others in limited form CCAPI Project Report

  46. EPRI API - Current Method of Interfacing Security Applications EMS Systems Applications ABB DSA Siemens Landis VSA Harris ESCA TRACE Bailey Telegyr OTS CCAPI Project Report

  47. On-line SecurityInterfaces with CIM EMS Systems Applications CIM ABB DSA Siemens Landis VSA Harris ESCA TRACE Bailey Telegyr OTS ... CCAPI Project Report

  48. EPRI Common Information Model Database and Messaging Infrastructure Application Integration Using EPRI CIM EMS Data Base EMS VSA DSA TRACE Filter Real time Data Link BusBranch Model BusBranch Model BusBranch Model Topology Processor API Adapter API Adapter API Adapter API Adapter API Adapter API Adapter API Adapter Wide Area Security Monitoring and Display CCAPI Project Report

  49. Topics • Introduction and Background • Objectives and Scope • What’s Changed • New Reference Model • CIM Status • Interface Specifications • WG13 Status • Conclusions CCAPI Project Report

  50. Component Interface Specifications (CIS) • Level 1 Functional Requirements for Component Interfaces • Describe events and messages to be supported by component interfaces • Application oriented • General requirements • UML notation to describe message/event content and business object (RWO) behavior CCAPI Project Report

More Related