Terry Saxton Xtensible Solutions, Inc. Minneapolis, Minnesota tsaxton@worldnet.att.net - PowerPoint PPT Presentation

Loading...

PPT – Terry Saxton Xtensible Solutions, Inc. Minneapolis, Minnesota tsaxton@worldnet.att.net PowerPoint presentation | free to download - id: 4bb058-NzEzM



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

Terry Saxton Xtensible Solutions, Inc. Minneapolis, Minnesota tsaxton@worldnet.att.net

Description:

EMS Users Group Pittsburgh, Pennsylvania March 13, 2000 Terry Saxton Xtensible Solutions, Inc. Minneapolis, Minnesota tsaxton_at_worldnet.att.net Topics Introduction and ... – PowerPoint PPT presentation

Number of Views:481
Avg rating:3.0/5.0
Slides: 76
Provided by: emmosOrgp
Learn more at: http://emmos.org
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: Terry Saxton Xtensible Solutions, Inc. Minneapolis, Minnesota tsaxton@worldnet.att.net


1
CCAPI Project Status Update
EMS Users GroupPittsburgh, PennsylvaniaMarch
13, 2000
  • Terry SaxtonXtensible Solutions,
    Inc.Minneapolis, Minnesotatsaxton_at_worldnet.att.n
    et

2
Topics
  • Introduction and Background
  • Objectives and Scope
  • Whats Changed
  • New Reference Model
  • CIM Status
  • Interface Specifications
  • WG13 Status
  • Conclusions

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

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 vendors data base and
    middleware technology
  • Create Standards that address user needs
  • i.e., enable solutions to real user problems

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

6
Topics
  • Introduction and Background
  • Objectives and Scope
  • Whats Changed
  • New Reference Model
  • CIM Status
  • Interface Specifications
  • WG13 Status
  • Conclusions

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

8
The Integration Of Systems Is Complex...
Customer Information
Customer Interface
EMS Control Center
Distribution Automation
Engineering
Work Management
Facilities Management
Planning
9
...This Is Simpler...
Customer Information
EMS Control Center
Customer Interface
Middleware
Distribution Automation
Engineering
Work Management
Facilities Management
Planning
10
Interface Standards are Key
Customer Information
EMS Control Center
Customer Interface
IntegrationBus
Distribution Automation
Engineering
Work Management
Facilities Management
Planning
Standard Interface Specifications
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

12
Coordination Among Standardization Activities
Standards Technology ____________ ISO
ODP IEEE CIRED Open GIS DistribuTECH GITA TD
OpenApplicationGroup
Component Container Technology _________________ C
ORBA (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
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

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

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
16
IEC Standards and CCAPI Scope Today
Common Information ModelCIM (WG13 and 14)
Utility B Control Center
Utility A Control Center
Utility A Distribution Systems
Integration Bus
ICCPWG07
InterfacesWG14
InterfacesWG13
  • CASM/GOMSFE (WG 10-12)
  • 870-5 (WG03)
  • ICCP (WG07)

Substation
17
What Has Changed Since Early Beginnings
  • Software industry undergone evolution
  • Top-down modular design
  • gt Object-oriented design
  • gt 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

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

19
Topics
  • Introduction and Background
  • Objectives and Scope
  • Whats Changed
  • New Reference Model
  • CIM Status
  • Interface Specifications
  • WG13 Status
  • Conclusions

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
  • Suns Enterprise Java Beans
  • Microsoft COM/DCOM
  • Key to plug-and-play in a distributed computing
    environment
  • Focus is on definition/standardization of
    component interfaces

21
CCAPI and IEC 61970 Reference Model
22
Data Access Services
23
CCAPI as an Integration Framework
24
Integration Framework for WG14
IEC 61968 Interface
Dist Wires Model
Trans Wires Model
DAC
VRU
Information Exchange Model
Outage Management
Distribution Automation
Planning
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
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

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)
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

28
Dedicated EAI solution vendors
  • Active Software
  • NEON
  • CrossWorlds Software
  • Vitria Technology
  • TIBCO

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

30
Vendors offering integration platforms
  • Oracle
  • SAP
  • PeopleSoft
  • Microsoft

31
Topics
  • Introduction and Background
  • Objectives and Scope
  • Whats Changed
  • New Reference Model
  • CIM Status
  • Interface Specifications
  • WG13 Status
  • Conclusions

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

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
..1
0
..1
1
..1
1
..1
HasA
HasA
HasA
TestedFrom
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
34
CIM (Common Information Model) Packages
ltltGlobalgtgt
Wires
LoadModel
Domain
SCADA
Topology
Core
Outage
Generation
Meas
Financial
Energy
Reservation
Protection
Scheduling
Asset
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

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.

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.

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

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

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 Model WG14
  • Company, jobs, people, authorities,vehicles
    ,computers, conducting equipment, work
    management, outage management to support
    real-time operations

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

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

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

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

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

46
EPRI API - Current Method of Interfacing
Security Applications
EMS Systems
Applications
ABB
DSA
Siemens
Landis
VSA
Harris
ESCA
TRACE
Bailey
Telegyr
OTS
47
On-line SecurityInterfaces with CIM
EMS Systems
Applications
CIM
ABB
DSA
Siemens
Landis
VSA
Harris
ESCA
TRACE
Bailey
Telegyr
OTS
...
48
Application Integration Using EPRI CIM
EMS Data Base
EMS
TRACE
DSA
VSA
Filter
BusBranch Model
BusBranch Model
BusBranch Model
Real time Data Link
Topology Processor
API Adapter
API Adapter
API Adapter
API Adapter
API Adapter
API Adapter
API Adapter
Wide Area Security Monitoring and Display
49
Topics
  • Introduction and Background
  • Objectives and Scope
  • Whats Changed
  • New Reference Model
  • CIM Status
  • Interface Specifications
  • WG13 Status
  • Conclusions

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

51
CCAPI CIS
  • Application categories
  • SCADA (includes data processing, supervisory
    control, data acquisition)
  • Alarm Processing
  • Topology Processing
  • Network Applications
  • Load Management
  • Generation Control
  • Load Forecast
  • Energy/Transmission Scheduling
  • Maintenance Scheduling
  • Transmission Resource Management
  • Accounting Settlements
  • HIS
  • Equipment Data Definition
  • Generic User Interface
  • Dynamic Simulation
  • Dispatcher Training Simulator
  • External (i.e., sources/sinks of information for
    EMS applications that are not part of an EMS)

52
CCAPI CIS
  • Use Cases to support key user roles with
    applications identified
  • Control Area Operator
  • Transmission Operator
  • Transmission Analyzer
  • Operations Planner
  • System Planner (long term)
  • Security Coordinator
  • Settlement and Billing
  • Scheduling Coordinator
  • Energy Scheduler
  • Maintenance Scheduler
  • Wholesale Power Marker
  • Transmission Marketer/Cust
  • Database Maintenance Engineer
  • System Administrator
  • Field Operator
  • Distribution Analyzer
  • Plant Operator
  • Construction Maintenance

53
CIS
  • Level 2 Interface Specifications
  • Organized by interface service
  • Provides specific semantics/syntax in IDL
  • Implementation-neutral language
  • Specify events, methods, and properties

54
Coordination with OMG Utility Task Force
  • UML and IDL obtained via OMG Utility Task Force
    submittals
  • 2 RFPs now in process for Level 2
  • Data Access Facility (DAF)
  • Approved as OMG standard
  • Also version 7 of CIM in XML with RDF Schema
  • Data Acquisition from Industrial Systems (DAIS)
  • Three submittals now being evaluated

55
Data Access Service
56
Topics
  • Introduction and Background
  • Objectives and Scope
  • Whats Changed
  • New Reference Model
  • CIM Status
  • Interface Specifications
  • WG13 Status
  • Conclusions

57
IEC TC57 WG13 - EMS API
  • Formed to develop standards for interfaces
    between applications
  • within Energy Management System (EMS)
  • external to EMS that supply/consume data in
    support of real-time operations in a control
    center
  • Strategy is to accept EPRI Control Center
    Application Program Interface (CCAPI) work as
    draft proposals for WG13 standards

58
Membership and Meetings
  • Membership
  • 14 Countries represented
  • Canada, China, Finland, France, Germany, Japan,
    Netherlands, Norway, Russia, Spain, Sweden,
    Switzerland, United Kingdom, United States
  • 25 members (8-15 active members)
  • Recent Meetings
  • Las Vegas, March 1999
  • Nice, June 1999
  • Stockholm, September 1999
  • Seattle, January 2000

59
WG13 Document Structure
  • IEC 61970 series of standards for EMS-API
  • Part 1 Guidelines and General Requirements
  • Part 2 Glossary
  • Part 3 CIM (Common Information Model)
  • Part 4 CIS (Component Interface Specifications),
    Level 1
  • Part 5 CIS, Level 2

60
Part 1 - Guidelines and General Requirements
  • IEC 61970 -1 draft rev 3 is available
  • 1. Scope
  • 2. Normative References
  • 3. Definitions
  • 4. EMSAPI Reference Model
  • 5. EMSAPI Standards Organization
  • 6. General Infrastructure Requirements
  • Incorporates CCAPI White Paper Version 2.2

61
Part 2 - Glossary
  • Draft Rev 1 available

62
Part 3 - CIM (Common Information Model)
  • Part 3 - Organized by layer
  • Part 301 CIM CORE (CDV)
  • Part 302 Financial, Energy Scheduling,
    Reservations (CD)
  • Part 303 SCADA (Draft)
  • Part 30x Future CIM additions

63
Part 4 - CIS Level 1
  • Part 4 - Level 1 Functional Requirements for
    Component Interfaces
  • Organized by application category
  • Driven by Use Cases
  • Describe services and messages to be supported by
    component interfaces in UML and XML
  • Generic Interface Definition (GID)
  • Provides generic set of API services for all
    applications

64
Part 4 CIS - Document Structure
  • Part 401 - CIS Framework (Draft Rev 1)
  • Part 402 - Common Data Access (CDA)
  • Part 403 - Generic Interface Definition (GID)
  • Part 404 - SCADA
  • Part 405 - Alarm Processing
  • Part 406 - Network Applications
  • Part 407 - Generation Control
  • Part 4xx - Future parts
  • Technical Report EMS-API Use Cases (Draft)

65
Part 401 CIS Framework
  • Draft Revision 2 available
  • 1. Scope
  • 2. Normative References
  • 3. Definitions
  • 4. Interface Class Definition Process
  • 5. Application Categories
  • 6. CIS Document Structure

66
Part 402 Common Data Access
  • CIS for applications to use to access publicly
    available data
  • API builds on the CIM for class definitions and
    navigation
  • Efficient access to large groups of related data
    (e.g., multiple instances of selected attribute
    values)
  • Independent of
  • Data base technology for implementation
  • Programming language

67
Part 402 Common Data Access
  • Functions supported
  • Read access
  • Supports access to data organized in a complex
    schema (e.g., CIM)
  • Multiple classes, different data types, reference
    and inheritance relationships
  • Schema query
  • Change notification events
  • Interrogation service to determine support for
    services
  • Read transaction spanning multiple operations

68
Part 403 Generic Information Exchange
  • Generic requirements for functionality needed in
    Level 2 specifications
  • Lead to standard API for any application to
    exchange information
  • Leverages the CIM as a model or data dictionary
    for information exchange
  • Message content and business object behavior
    specified in other CISs
  • Four types of users of GID
  • Developers of GID clients
  • Developers of infrastructure that supports GID
  • System integrators
  • End users

69
Part 403 Generic Information Exchange
  • Functionality supported
  • Operations for Phase 2 Common Data Access
    (request/reply)
  • Create, read, update, delete, schema
    modification, fine grained notification of data
    changes
  • Operations for event notification (send/receive)
  • Operations for method invocation
  • On components/applications
  • Ex run program
  • On business objects
  • Ex Trip breaker
  • Does not specify specific data exchange pattern

70
Part 5 CIS
  • Part 5 - Level 2 Interface Specifications
  • IDL (obtained via submittals)
  • Implementation-neutral language
  • Specify events, methods, and properties for
    component interfaces
  • May be different profiles for each technology
    mapping

71
CIS Part 5 - Document Structure (Preliminary)
  • Part 501 - CIM Schema
  • Part 502 - Common Data Access Facility
  • Part 503 - Generic API
  • Part 504 - Resource Identification
  • Part 505 - Measurement Values
  • Part 506 Alarm Events
  • Part 507 - Parameter Update Events
  • Part 508 - Execution Control Events
  • Part 509 - Data Set Documents

72
Topics
  • Introduction and Background
  • Objectives and Scope
  • Whats Changed
  • New Reference Model
  • CIM Status
  • Interface Specifications
  • WG13 Status
  • Conclusions

73
Conclusions
  • Significant progress on several fronts
  • How to measure success
  • Look at projects building on CCAPI results
  • CIM relatively stable and being used extensively
  • Converted to object-oriented approach with UML
  • Basis for common power system model within EMS
  • Application integration
  • Legacy system integration
  • Basis for information sharing between utilities
    and security coordinators
  • Defines classes and attributes for neutral model
    of data
  • Not necessary to have CIM-compliant data base

74
Conclusions
  • CCAPI Task Force meetings and email provide forum
    for advancing integration concepts
  • Achieved industry consensus on new
    component-based reference model supported by EMS
    suppliers
  • Providing key enabling standards for integration
  • Basis for drafts to WG13
  • Active participation by WG13 and WG14 member
    countries in process
  • Architecture concepts for TC57 and UCA
  • First CIS documents in 1999
  • Need pilot projects to test component interfaces

75
CCAPI FTP site
  • Ftp.kemaconsulting.com/epriapi/downloads/ as
    anonymous user or via browser
  • Check in appropriate folder for documents
  • Folder Document list has list of recently
    submitted documents and the folder they are in.
About PowerShow.com