Terry Saxton Terry Saxton Xtensible Solutions, Inc. Xtensible Solutions, Inc. Minneapolis, Minnesota Minneapolis, Minnesota [email protected][email protected]CCAPI Project Status CCAPI Project Status Update Update EMS Users Group EMS Users Group Pittsburgh, Pennsylvania Pittsburgh, Pennsylvania March 13, 2000 March 13, 2000
75
Embed
CCAPI Project Status Update EMS Users Group Pittsburgh, Pennsylvania March 13, 2000
Terry Saxton Xtensible Solutions, Inc. Minneapolis, Minnesota [email protected]. 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 - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Terry SaxtonTerry Saxton
Xtensible Solutions, Inc.Xtensible Solutions, Inc.
CCAPI Original ObjectivesCCAPI Original Objectives
Plug compatibilityPlug compatibility DefinitionDefinition: The ability to easily install, or “plug in”, : The ability to easily install, or “plug in”,
applications into different electric utility control center applications into different electric utility control center platforms.platforms.
Idealistic ViewIdealistic View: Enable shrink-wrap packages, as in : Enable shrink-wrap packages, as in personal computer marketplace.personal computer marketplace.
Realistic ViewRealistic View: Greatly reduce the costs to install an : Greatly reduce the costs to install an application into a control center platformapplication into a control center platform
End Result End Result Enable user to build EMS via plug-and-playEnable user to build EMS via plug-and-play
Create Guidelines or Standards to enable plug-Create Guidelines or Standards to enable plug-compatibilitycompatibility
Ensure that standards are compatible with Ensure that standards are compatible with developers’ productsdevelopers’ products i.e., standards support vendor’s data base and i.e., standards support vendor’s data base and
middleware technologymiddleware technology
Create Standards that address user needsCreate Standards that address user needs i.e., enable solutions to real user problemsi.e., enable solutions to real user problems
Create IEC standard interface specificationsCreate IEC standard interface specifications For plug-in applications in EMS or similar systemsFor plug-in applications in EMS or similar systems
Use EPRI CCAPI TF work as basis for standardsUse EPRI CCAPI TF work as basis for standards
Incorporate TC57 National Committee needs as Incorporate TC57 National Committee needs as wellwell
What Has Changed Since Early BeginningsWhat Has Changed Since Early Beginnings
New user needs as result of Utility restructuring and New user needs as result of Utility restructuring and network security initiativesnetwork security initiatives
Combine transmission and distribution into Wires Combine transmission and distribution into Wires GroupGroup Need to integrate legacy EMS/SCADA systems with Need to integrate legacy EMS/SCADA systems with
DMSDMS Leads to need for enterprise-wide integration strategyLeads to need for enterprise-wide integration strategy
Need to exchange information with other sites for Need to exchange information with other sites for security and open accesssecurity and open access Need common power system modelNeed common power system model Need common information exchange formatNeed common information exchange format
Minimizes effort required for interoperability between Minimizes effort required for interoperability between applications and systemsapplications and systems SemanticsSemantics
SyntaxSyntax
ServicesServices
Requires only one transformation at application Requires only one transformation at application interface to interoperate with multiple applications interface to interoperate with multiple applications
Two main types:Two main types: Software industrySoftware industry
IEC TC57 WG14: System Interfaces for IEC TC57 WG14: System Interfaces for Distribution ManagementDistribution Management
Provides message-based inter-application Provides message-based inter-application integration framework and interface standards for integration framework and interface standards for DMSDMS
Major effort to ensure requirements are compatible Major effort to ensure requirements are compatible with:with: CCAPI integration bus approachCCAPI integration bus approach
CIM with extensions for DMSCIM with extensions for DMS
Open Applications Group standardsOpen Applications Group standards
and complementary to WG13 standardsand complementary to WG13 standards
An Integration ArchitectureAn Integration ArchitectureIs Needed First Is Needed First
Provides For An Adaptable Utility InfrastructureProvides For An Adaptable Utility Infrastructure
Partitions Application Systems Based On:Partitions Application Systems Based On: Things That Are StableThings That Are Stable
– Standard Component InterfacesStandard Component Interfaces
Things That Can Be ControlledThings That Can Be Controlled– Middleware & Application ProductsMiddleware & Application Products
A Stable Basis For Enterprise-Wide Integration A Stable Basis For Enterprise-Wide Integration Transcends The Life Cycle Of Individual Application Transcends The Life Cycle Of Individual Application
Microsoft DCOMMicrosoft DCOMSun Enterprise Java BeansSun Enterprise Java Beans
CCAPI standards need to embrace and build on CCAPI standards need to embrace and build on these trends to support EMS vendor productsthese trends to support EMS vendor products
Reference model => Reference model => Build on component modelsBuild on component models Show role of CIM Show role of CIM
CIM => CIM => Object-oriented model in UMLObject-oriented model in UMLExtensions to support new scopeExtensions to support new scopeMinimal impact on contentMinimal impact on content
New model based on component technologyNew model based on component technology Software industry (including EMS vendors and suppliers of Software industry (including EMS vendors and suppliers of
Integration Bus Implementation StrategyIntegration Bus Implementation Strategy
Implement Integration Infrastructure That Meets IEC Implement Integration Infrastructure That Meets IEC 61968 and 61970 Requirements61968 and 61970 Requirements Use COTS middleware for bus technologyUse COTS middleware for bus technology
Incorporate process that brings in applicable models: Incorporate process that brings in applicable models: CCAPI/CIM, UCA/GOMSFE, OAG, and others.CCAPI/CIM, UCA/GOMSFE, OAG, and others.
For Interface Standards, Participate (Directly And For Interface Standards, Participate (Directly And Through Suppliers) In Utility Industry Standards Through Suppliers) In Utility Industry Standards ActivitiesActivities Gather information & influence the development of Gather information & influence the development of
The Common Information Model (CIM)The Common Information Model (CIM)
A Tool To Enable Integration In Any Domain Where A Tool To Enable Integration In Any Domain Where A Common Power System Model Is NeededA Common Power System Model Is Needed Model Includes Public Classes, Their Attributes, And Model Includes Public Classes, Their Attributes, And
Relationships to represent utility objectsRelationships to represent utility objects
The Classes (Objects) Are Abstract And May Be Used The Classes (Objects) Are Abstract And May Be Used In A Wide Variety Of ApplicationsIn A Wide Variety Of Applications
Useful:Useful: As Inspiration For Logical Data SchemasAs Inspiration For Logical Data Schemas To Define Information Exchange ModelsTo Define Information Exchange Models
Core (new)Core (new) Contains the core PowerSystemResource and Contains the core PowerSystemResource and
ConductingEquipment entities shared by all applications.ConductingEquipment entities shared by all applications.
Topology (new)Topology (new) Extension to the Core Package that models Topology Extension to the Core Package that models Topology
information independently of the other electrical information independently of the other electrical characteristicscharacteristics
WiresWires An extension to the Core and Topology package that An extension to the Core and Topology package that
models information on the electrical characteristics of models information on the electrical characteristics of Transmission and Distribution networks.Transmission and Distribution networks.
Business process related entities with associations Business process related entities with associations to the appropriate part 301 classes.to the appropriate part 301 classes.
FinancialFinancial Company and SubControlArea would be part of the Core Company and SubControlArea would be part of the Core
package in part 301.package in part 301. Sub-types of Company and SubControlArea and more Sub-types of Company and SubControlArea and more
associations defined hereassociations defined here Models for settlement and billing - legal entities in agreementsModels for settlement and billing - legal entities in agreements
61970 Part 303 and 61968 for DMS61970 Part 303 and 61968 for DMS
61970 Part 30361970 Part 303 SCADASCADA
Entities specific to SCADA and Alarm processor Entities specific to SCADA and Alarm processor applications that are not used by other applications.applications that are not used by other applications.
Harmonization with WG10-12 and othersHarmonization with WG10-12 and others
All Elements To Be Added To The CIM Data All Elements To Be Added To The CIM Data Dictionary Are Intended To Be Consistent With:Dictionary Are Intended To Be Consistent With: TC57 WG 10/11/12 Standards (Based On The TC57 WG 10/11/12 Standards (Based On The
UCA2/GOMSFE)UCA2/GOMSFE)
The OAG.The OAG.
It Is Recommended That Consideration Be Given It Is Recommended That Consideration Be Given For Generalizing The “WG13/WG14 CIM” To For Generalizing The “WG13/WG14 CIM” To Become The “TC57 CIM” Become The “TC57 CIM”
What Does CIM Compliance MeanWhat Does CIM Compliance Mean
The CIM is not a database - it is an information The CIM is not a database - it is an information model (I.e., meta data)model (I.e., meta data)
CIM compliance means that at the public interface CIM compliance means that at the public interface the data representation complies with the CIM in the data representation complies with the CIM in terms of terms of Semantics - Naming and meaning of dataSemantics - Naming and meaning of data
Symantics - data typeSymantics - data type
Relationships - relation to other parts of the CIM, so Relationships - relation to other parts of the CIM, so that the data relationships can be navigatedthat the data relationships can be navigated
CIM compliance does not mean:CIM compliance does not mean: There is a database organized exactly like the CIM There is a database organized exactly like the CIM
class diagramsclass diagrams
All aspects of the CIM are provided forAll aspects of the CIM are provided for
CIM StatusCIM Status Current Version u08bCurrent Version u08b
Rational ROSE for model definition, maintenanceRational ROSE for model definition, maintenance Rational SODA for MS Word documentationRational SODA for MS Word documentation
Part 301 sent to IEC as CDV on 11/23/99Part 301 sent to IEC as CDV on 11/23/99 Part 302 sent to IEC as CD on 12/10/99Part 302 sent to IEC as CD on 12/10/99 Part 303 SCADA being revisedPart 303 SCADA being revised Part 501 CIM SchemaPart 501 CIM Schema
CIM in XML with RDF SchemaCIM in XML with RDF Schema
WG14 developing new CIM packages for distribution WG14 developing new CIM packages for distribution systemssystems
Many projects based on CIMMany projects based on CIM
Level 1 Functional Requirements for Component Level 1 Functional Requirements for Component InterfacesInterfaces Describe events and messages to be supported by Describe events and messages to be supported by
component interfacescomponent interfaces Application orientedApplication oriented General requirementsGeneral requirements UML notation to describe message/event content and UML notation to describe message/event content and
business object (RWO) behaviorbusiness object (RWO) behavior
ManagementManagement Accounting SettlementsAccounting Settlements HISHIS Equipment Data DefinitionEquipment Data Definition Generic User InterfaceGeneric User Interface Dynamic SimulationDynamic Simulation Dispatcher Training Dispatcher Training
SimulatorSimulator External (External (i.e., sources/sinks of i.e., sources/sinks of
information for EMS applications information for EMS applications
that are not part of an EMS)that are not part of an EMS)
user roles with applications user roles with applications
identified identified Control Area OperatorControl Area Operator Transmission OperatorTransmission Operator Transmission AnalyzerTransmission Analyzer Operations PlannerOperations Planner System Planner (long term)System Planner (long term) Security CoordinatorSecurity Coordinator Settlement and BillingSettlement and Billing Scheduling CoordinatorScheduling Coordinator
Energy SchedulerEnergy Scheduler Maintenance SchedulerMaintenance Scheduler Wholesale Power MarkerWholesale Power Marker Transmission Marketer/CustTransmission Marketer/Cust Database Maintenance Database Maintenance
Engineer Engineer System AdministratorSystem Administrator Field OperatorField Operator Distribution AnalyzerDistribution Analyzer Plant OperatorPlant Operator Construction & MaintenanceConstruction & Maintenance
Level 2 Interface SpecificationsLevel 2 Interface Specifications Organized by interface serviceOrganized by interface service
Provides specific semantics/syntax in IDLProvides specific semantics/syntax in IDL Implementation-neutral languageImplementation-neutral language Specify events, methods, and propertiesSpecify events, methods, and properties
Coordination with OMG Utility Task ForceCoordination with OMG Utility Task Force
UML and IDL obtained via OMG Utility Task Force UML and IDL obtained via OMG Utility Task Force submittalssubmittals 2 RFPs now in process for Level 22 RFPs now in process for Level 2
Data Access Facility (DAF)Data Access Facility (DAF) Approved as OMG standardApproved as OMG standard Also version 7 of CIM in XML with RDF SchemaAlso version 7 of CIM in XML with RDF Schema
Data Acquisition from Industrial Systems (DAIS)Data Acquisition from Industrial Systems (DAIS) Three submittals now being evaluatedThree submittals now being evaluated
Formed to develop standards for interfaces Formed to develop standards for interfaces between applicationsbetween applications within Energy Management System (EMS)within Energy Management System (EMS)
external to EMS that supply/consume data in support external to EMS that supply/consume data in support of real-time operations in a control centerof real-time operations in a control center
Strategy is to accept EPRI Control Center Strategy is to accept EPRI Control Center Application Program Interface (CCAPI) work as Application Program Interface (CCAPI) work as draft proposals for WG13 standardsdraft proposals for WG13 standards
IEC 61970 series of standards for EMS-APIIEC 61970 series of standards for EMS-API Part 1: Guidelines and General RequirementsPart 1: Guidelines and General Requirements
Part 2: GlossaryPart 2: Glossary
Part 3: CIM (Common Information Model)Part 3: CIM (Common Information Model)
Part 4: CIS (Component Interface Specifications), Part 4: CIS (Component Interface Specifications), Level 1Level 1
Part 4 - Level 1 Functional Requirements for Part 4 - Level 1 Functional Requirements for Component InterfacesComponent Interfaces Organized by application categoryOrganized by application category
Driven by Use CasesDriven by Use Cases
Describe services and messages to be supported by Describe services and messages to be supported by component interfaces in UML and XMLcomponent interfaces in UML and XML
Generic Interface Definition (GID)Generic Interface Definition (GID) Provides generic set of API services for all Provides generic set of API services for all
Part 402 Common Data AccessPart 402 Common Data Access
CIS for applications to use to access publicly CIS for applications to use to access publicly available dataavailable data
API builds on the CIM for class definitions and API builds on the CIM for class definitions and navigationnavigation
Efficient access to large groups of related data Efficient access to large groups of related data (e.g., multiple instances of selected attribute values)(e.g., multiple instances of selected attribute values)
Independent of Independent of Data base technology for implementationData base technology for implementation
Supports access to data organized in a complex schema Supports access to data organized in a complex schema (e.g., CIM)(e.g., CIM)
– Multiple classes, different data types, reference and Multiple classes, different data types, reference and inheritance relationshipsinheritance relationships
Part 403 Generic Information ExchangePart 403 Generic Information Exchange Generic requirements for functionality needed in Level 2 Generic requirements for functionality needed in Level 2
specificationsspecifications
Lead to standard API for any application to exchange Lead to standard API for any application to exchange informationinformation
Leverages the CIM as a model or data dictionary for Leverages the CIM as a model or data dictionary for information exchangeinformation exchange Message content and business object behavior specified in Message content and business object behavior specified in
other CIS’sother CIS’s
Four types of users of GIDFour types of users of GID Developers of GID clientsDevelopers of GID clients Developers of infrastructure that supports GIDDevelopers of infrastructure that supports GID System integratorsSystem integrators End usersEnd users
Part 403 Generic Information ExchangePart 403 Generic Information Exchange Functionality supported:Functionality supported:
Operations for Phase 2 Common Data Access Operations for Phase 2 Common Data Access (request/reply)(request/reply)
Create, read, update, delete, schema modification, fine grained Create, read, update, delete, schema modification, fine grained notification of data changesnotification of data changes
Operations for event notification (send/receive)Operations for event notification (send/receive)
Operations for method invocationOperations for method invocation On components/applicationsOn components/applications
– Ex: run programEx: run program
On business objectsOn business objects– Ex: Trip breakerEx: Trip breaker
Does not specify specific data exchange patternDoes not specify specific data exchange pattern
Part 5 CISPart 5 CIS Part 5 - Level 2 Interface SpecificationsPart 5 - Level 2 Interface Specifications
IDL (obtained via submittals)IDL (obtained via submittals) Implementation-neutral languageImplementation-neutral language Specify events, methods, and properties for component Specify events, methods, and properties for component
interfacesinterfaces
May be different profiles for each technology mappingMay be different profiles for each technology mapping
CIS Part 5 - Document Structure (Preliminary)CIS Part 5 - Document Structure (Preliminary)
Part 501 - CIM Schema Part 501 - CIM Schema Part 502 - Common Data Access FacilityPart 502 - Common Data Access Facility Part 503 - Generic API Part 503 - Generic API Part 504 - Resource IdentificationPart 504 - Resource Identification Part 505 - Measurement Values Part 505 - Measurement Values Part 506 – Alarm EventsPart 506 – Alarm Events Part 507 - Parameter Update EventsPart 507 - Parameter Update Events Part 508 - Execution Control EventsPart 508 - Execution Control Events Part 509 - Data Set DocumentsPart 509 - Data Set Documents
ConclusionsConclusions Significant progress on several frontsSignificant progress on several fronts How to measure successHow to measure success Look at projects building on CCAPI resultsLook at projects building on CCAPI results CIM relatively stable and being used extensivelyCIM relatively stable and being used extensively
Converted to object-oriented approach with UMLConverted to object-oriented approach with UML Basis for common power system model within EMSBasis for common power system model within EMS
Application integrationApplication integration Legacy system integrationLegacy system integration Basis for information sharing between utilities and Basis for information sharing between utilities and
security coordinatorssecurity coordinators Defines classes and attributes for neutral model of dataDefines classes and attributes for neutral model of data Not necessary to have CIM-compliant data baseNot necessary to have CIM-compliant data base
CCAPI Task Force meetings and email provide CCAPI Task Force meetings and email provide forum for advancing integration conceptsforum for advancing integration concepts Achieved industry consensus on new component-Achieved industry consensus on new component-
based reference model supported by EMS suppliersbased reference model supported by EMS suppliers Providing key enabling standards for integrationProviding key enabling standards for integration
Basis for drafts to WG13Basis for drafts to WG13 Active participation by WG13 and WG14 member Active participation by WG13 and WG14 member
countries in processcountries in process Architecture concepts for TC57 and UCAArchitecture concepts for TC57 and UCA
First CIS documents in 1999First CIS documents in 1999
Need pilot projects to test component interfacesNeed pilot projects to test component interfaces
Ftp.kemaconsulting.com/epriapi/downloads/ as Ftp.kemaconsulting.com/epriapi/downloads/ as anonymous user or via browseranonymous user or via browser
Check in appropriate folder for documentsCheck in appropriate folder for documents
Folder “Document list” has list of recently submitted Folder “Document list” has list of recently submitted documents and the folder they are in.documents and the folder they are in.