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

Terry SaxtonTerry Saxton

Xtensible Solutions, Inc.Xtensible Solutions, Inc.

Minneapolis, MinnesotaMinneapolis, Minnesota

[email protected]@worldnet.att.net

CCAPI Project Status UpdateCCAPI Project Status UpdateEMS Users GroupEMS Users Group

Pittsburgh, PennsylvaniaPittsburgh, PennsylvaniaMarch 13, 2000March 13, 2000

CCAPI Project Report CCAPI Project Report Xtensible Solutions

TopicsTopics

Introduction and BackgroundIntroduction and Background

Objectives and ScopeObjectives and Scope

What’s ChangedWhat’s Changed

New Reference ModelNew Reference Model

CIM StatusCIM Status

Interface SpecificationsInterface Specifications

WG13 StatusWG13 Status

ConclusionsConclusions


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


CCAPI Task Force createdCCAPI Task Force created

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


IEC TC57 WG13 CreatedIEC TC57 WG13 Created

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


TopicsTopics










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


WorkManagement

CustomerInformation

Engineering

Planning

DistributionAutomation

Customer Interface

FacilitiesManagement

EMSControlCenter

The Integration Of Systems Is Complex...The Integration Of Systems Is Complex...


CustomerInformation

EngineeringMiddlewareDistribution

Automation

Customer Interface

WorkManagement

Planning


EMSControlCenter

...This Is Simpler......This Is Simpler...


Planning

CustomerInformation

EngineeringIntegration

BusDistributionAutomation

Customer Interface

= Standard Interface Specifications

WorkManagement


EMSControlCenter

Interface Standards are KeyInterface Standards are Key


Role of StandardsRole of Standards

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

Utility specificUtility specific


EPRICCAPIProject

WG14DMS

CoordinatingGroup

WG13EMS

ObjectMgmt.Group

Standards &Technology

____________ISO ODP

IEEECIRED

Open GISDistribuTECH

GITAT&D

Component ContainerTechnology

_________________CORBA (OMG)

Enterprise Java BeansDCOM (Microsoft)

WGs 10,11,12Substations

UtilityIntegration

Bus

TC57

OpenApplication

Group

Coordination Among Standardization ActivitiesCoordination Among Standardization Activities


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

Systems And MiddlewareSystems And Middleware


CCAPI Scope - OriginalCCAPI Scope - Original

Utility A Control Center Utility B Control Center

ICCP

Substation

•CASM•870-5•ICCP

Common Information ModelCIM

CIM

Message BusCDA

Message BusCDA


Utility A Control Center Utility B Control Center

ICCPWG07

Substation

•CASM/GOMSFE (WG 10-12)•870-5 (WG03)•ICCP (WG07)

Utility A Distribution Systems

Common Information ModelCIM (WG13 and 14)

Integration Bus

IEC Standards and CCAPI Scope TodayIEC Standards and CCAPI Scope Today

InterfacesWG13

InterfacesWG14


What Has Changed Since Early BeginningsWhat Has Changed Since Early Beginnings

Software industry undergone evolutionSoftware industry undergone evolution

Top-down modular designTop-down modular design

=> Object-oriented design=> Object-oriented design

=> Component-based architectures=> Component-based architectures Examples: Examples: OMG CORBA Component ModelOMG CORBA Component Model

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


Impact on CCAPI ProjectImpact on CCAPI Project

Guidelines document needed updating, specifically:Guidelines document needed updating, specifically:

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

Interface Specifications (MBI, CDA)Interface Specifications (MBI, CDA)

=>=> Component Interface Specifications (CIS) Component Interface Specifications (CIS)


TopicsTopics










Revised Reference ModelRevised Reference Model

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

EMS applications) embracing component-based EMS applications) embracing component-based architectures. Examples:architectures. Examples:

CORBA component modelCORBA component model Sun’s Enterprise Java BeansSun’s Enterprise Java Beans Microsoft COM/DCOMMicrosoft COM/DCOM

Key to plug-and-play in a distributed computing Key to plug-and-play in a distributed computing environmentenvironment

Focus is on definition/standardization of component Focus is on definition/standardization of component interfacesinterfaces

Common Information Model

(CIM)

Component Adapter

Component Container API

Component Container

Middleware Services

Communication Profiles

CCAPI StandardsApplication Information Exchangeand Data Access Software

Component Adapter

Application 2Application 1

ComponentA

ComponentB

Legacy ApplicationAPI

Legacy Wrapper

Legacy Application

ComponentExecution

System(Example:Integration

Bus)

Persistent Storage

Applications& Components

Component Execution Services:

- Naming- Events- Transactions- Persistence- Security- Utility business object supportservices (Business ObjectReference Services, DirectoryService, and Business ObjectConfiguration Services)

Component InterfaceSpecifications

ComponentB Interfaces

ComponentA Interfaces

Component Interfaces

CCAPI and IEC 61970 Reference ModelCCAPI and IEC 61970 Reference Model


Data Access ServicesData Access Services

PublicData

DatabaseAdapter

DatabaseAdapter

EMSProprietaryDatabase

ICCPAdapter

CASMAdapter

SCADASystemAdapter

ICCPBlocks

1&2

CASMDiscovery/Reporting

SCADASystem

ControlCenter

Substation

Device Device

Substation

RTU

Bus Connector Bus Connector

Integration Bus

61970

69870-5, DNP, Proprietary

Proprietary6185060870-6


Component Execution Systemand Component Adapters (e.g., Integration Bus)

LegacyWrapper

Programs Programs Programs

AlarmProcessor

LoadManagement

GenerationControl

Accounting/Settlement

Programs

PublicData

ICCPNetwork

ICCP

SCADANetwork

UserPCs

Programs CIM Server

NetworkApplications

TopologyProcessor

PublicData

PublicData

PublicData

PublicData

PublicData

PublicData

Programs

PublicData

DistributionManagement

SystemsComponent

Interface

LegacySCADASystem

LegacySystem

Programs

CCAPI as an Integration FrameworkCCAPI as an Integration Framework


OutageManagement

Interface Adapter

DistWiresModel

EMS

TransWiresModel

DAC

Interface Adapter

CIS

VRU

EventHistory

HumanResources

DistributionAutomation

Maint. AnalysisDiagnostic Tools

Planning

Interface Adapter

IEC 61968 Compliant Middleware Services

InformationExchange

Model

WorkManagement

...

= IEC 61968 Interface

GIS Financial

Integration Framework for WG14Integration Framework for WG14


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

these standardsthese standards


WiringConfiguration

Transformer

IntegrationBus Client

Message Deliveryvia Integration Bus Server(s)

WrappedApplication

Co

nn

ecto

r

Localsupportedprotocol.

Adapts component model to integrationbus environment.

Transforms messages into thepublic information model.

Connects component instance to correctdestinations per wiring configuration.

Wrapper

Applicationbuilt as

Component"Component" presents itself as{properties, events, methods}

per a standard component model (EJB, CORBA, COM+)

with CIM-compliant semantics

Application Domain

Integration Domain

InformationExchange Mdl

BusAdministration

UnwrappedApplication

ComponentAdaptor

CustomAdaptoror

Adapts local protocoldirectly to integrationbus environment.

Integration Bus Connector ArchitectureIntegration Bus Connector Architecture


Enterprise Application IntegrationEnterprise Application Integration

EAI is not equal to Messaging (or MOM). EAI is not equal to Messaging (or MOM). Messaging is *only* the plumbing. Messaging is *only* the plumbing.

EAI framework description includes EAI framework description includes process automationprocess automation

state-managementstate-management

real-time decision supportreal-time decision support

connectors/adaptersconnectors/adapters

event channelsevent channels

content-based routingcontent-based routing


Dedicated EAI solution vendorsDedicated EAI solution vendors

Active SoftwareActive Software

NEONNEON

CrossWorlds SoftwareCrossWorlds Software

Vitria TechnologyVitria Technology

TIBCOTIBCO


Vendors offering parts of EAI solutionsVendors offering parts of EAI solutions

TSI (Mercator)TSI (Mercator)

STCSTC

BEA SystemsBEA Systems

Forte SoftwareForte Software

IBMIBM

SISCOSISCO

CESCES


Vendors offering integration platformsVendors offering integration platforms

OracleOracle

SAPSAP

PeopleSoftPeopleSoft

MicrosoftMicrosoft


TopicsTopics










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


Example of CIM Class Diagram and Use of Example of CIM Class Diagram and Use of Unified Modeling Language (UML)Unified Modeling Language (UML)

MemberOf

PowerSystemResource( from Core)

ConductingEquipment(from Core)

Contains0..*

TapChanger

HasA1..1 Tested

1..1TestedFrom

0..*

TestedTo1..1

WindingTest

Tested0..*

WindingFor 1..*TransformerWinding

0..*

1..1

HasA

1..10..*

TestedFrom

1..10..*TestedTo

HasA 1..10..1

HeatExchanger

HasA

1..1

PowerTransformer

1..*

1..1

HasA

0..1 1..1

HasA


CIM (Common Information Model) PackagesCIM (Common Information Model) Packages

Generation

SCADA

Domain<<Global>>

Wires LoadModel

Core

Meas

Topology

Outage

Protection Financial EnergyScheduling

Reservation

Asset


Package DefinitionsPackage Definitions

IEC 61970 Part 301IEC 61970 Part 301 CoreCore DomainDomain TopologyTopology WiresWires LoadModelLoadModel MeasurementMeasurement Generation/ProductionGeneration/Production Generation/GenerationDynamicsGeneration/GenerationDynamics OutageOutage ProtectionProtection

IEC 61970 Part 302IEC 61970 Part 302 FinancialFinancial EnergySchedulingEnergyScheduling ReservationReservation

IEC 61970 Part 303IEC 61970 Part 303 SCADASCADA


61970 Part 30161970 Part 301

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.


Part 301 (Cont.)Part 301 (Cont.)

Measurement (new)Measurement (new) Entities that describe dynamic data exchanged between Entities that describe dynamic data exchanged between

applicationsapplications

Outage (new)Outage (new) Extension to the Core and Wires packages that models Extension to the Core and Wires packages that models

information on the current and planned network information on the current and planned network configuration.configuration.

Protection (new)Protection (new) Extension to the Core and Wires packages that models Extension to the Core and Wires packages that models

information for protection equipment including relays.information for protection equipment including relays.


Part 301 (Cont.)Part 301 (Cont.)

LoadModel (no change)LoadModel (no change)

Generation (no change)Generation (no change)

Production (no change)Production (no change)

GenerationDynamics (no change)GenerationDynamics (no change)

DomainDomain

Definitions of primitive data types, used by all CIM Definitions of primitive data types, used by all CIM packages and classespackages and classes


61970 Part 30261970 Part 302

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

EnergySchedulingEnergyScheduling

ReservationReservation


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.

61968 Assets Model61968 Assets Model WG14WG14 Company, jobs, people, authorities,vehicles ,computers, conducting Company, jobs, people, authorities,vehicles ,computers, conducting

equipment, work management, outage management to support real-time equipment, work management, outage management to support real-time

operationsoperations


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 ComplianceCIM Compliance

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


Utilities Implementing CIM/CCAPI StandardsUtilities Implementing CIM/CCAPI Standards

Illinois PowerIllinois Power

Kansas City Power and LightKansas City Power and Light

Florida Power and LightFlorida Power and Light

SCESCE

Duquesne PowerDuquesne Power

NERC Security CoordinatorsNERC Security Coordinators Power System Model data exchangePower System Model data exchange

Based on CIM XML and RDF SchemaBased on CIM XML and RDF Schema

Many others in limited formMany others in limited form


EPRI API - EPRI API - Current Method of Interfacing Security ApplicationsCurrent Method of Interfacing Security Applications

Siemens

Landis

Harris

ESCA

Bailey

Telegyr

ABBDSA

VSA

TRACE

OTS

Applications EMS Systems


On-line SecurityOn-line SecurityInterfaces with CIMInterfaces with CIM

Siemens

Landis

Harris

ESCA

Bailey

Telegyr

ABBDSA

VSA

TRACE

OTS

CIM

Applications EMS Systems

...


API Adapter

EMSData Base

Filter

TRACE

BusBranchModel

DSA

BusBranchModel

VSA

BusBranchModel

TopologyProcessor

EMS

Real timeData Link

EPRI Common Information Model

Database and Messaging Infrastructure

API Adapter API Adapter API Adapter API Adapter API Adapter API Adapter

Application Integration Using EPRI CIM

Wide Area Security Monitoring and Display


TopicsTopics










Component Interface Specifications (CIS)Component Interface Specifications (CIS)

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


CCAPI CISCCAPI CIS

Application categoriesApplication categories SCADA (includes data SCADA (includes data

processing, supervisory processing, supervisory control, data acquisition)control, data acquisition)

Alarm ProcessingAlarm Processing Topology ProcessingTopology Processing Network ApplicationsNetwork Applications Load ManagementLoad Management Generation Control Generation Control Load ForecastLoad Forecast Energy/Transmission Energy/Transmission

SchedulingScheduling

Maintenance SchedulingMaintenance Scheduling Transmission Resource Transmission Resource

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)


CCAPI CISCCAPI CIS

Use Cases to support key Use Cases to support key

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


CISCIS

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


PublicData

DatabaseAdapter

DatabaseAdapter

EMSProprietaryDatabase

ICCPAdapter

CASMAdapter

SCADASystemAdapter

ICCPBlocks

1&2

CASMDiscovery/Reporting

SCADASystem

ControlCenter

Substation

Device Device

Substation

RTU

Bus Connector Bus Connector

Integration Bus

61970

69870-5, DNP, Proprietary

Proprietary6185060870-6

Data Access ServiceData Access Service


TopicsTopics










IEC TC57 WG13 - EMS APIIEC TC57 WG13 - EMS API

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


Membership and MeetingsMembership and Meetings MembershipMembership

14 Countries represented14 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


WG13 Document StructureWG13 Document Structure

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 5: CIS, Level 2Part 5: CIS, Level 2


Part 1 - Guidelines and General RequirementsPart 1 - Guidelines and General Requirements

IEC 61970 -1 draft rev 3 is availableIEC 61970 -1 draft rev 3 is available

1. Scope1. Scope

2. Normative References2. Normative References

3. Definitions3. Definitions

4. EMSAPI Reference Model4. EMSAPI Reference Model

5. EMSAPI Standards Organization5. EMSAPI Standards Organization

6. General Infrastructure Requirements6. General Infrastructure Requirements

Incorporates CCAPI White Paper Version 2.2Incorporates CCAPI White Paper Version 2.2


Part 2 - GlossaryPart 2 - Glossary

Draft Rev 1 availableDraft Rev 1 available


Part 3 - CIM (Common Information Model)Part 3 - CIM (Common Information Model)

Part 3 - Organized by layerPart 3 - Organized by layer Part 301: CIM CORE (CDV)Part 301: CIM CORE (CDV)

Part 302: Financial, Energy Scheduling, Reservations Part 302: Financial, Energy Scheduling, Reservations (CD)(CD)

Part 303: SCADA (Draft)Part 303: SCADA (Draft)

Part 30x: Future CIM additionsPart 30x: Future CIM additions


Part 4 - CIS Level 1Part 4 - CIS Level 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

applicationsapplications


Part 4 CIS - Document StructurePart 4 CIS - Document Structure

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


Part 401 CIS FrameworkPart 401 CIS Framework

Draft Revision 2 availableDraft Revision 2 available1. Scope1. Scope2. Normative References2. Normative References3. Definitions3. Definitions4. Interface Class Definition Process4. Interface Class Definition Process5. Application Categories5. Application Categories6. CIS Document Structure6. CIS Document Structure


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

Programming languageProgramming language


Part 402 Common Data AccessPart 402 Common Data Access

Functions supported:Functions supported: Read accessRead access

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

Schema querySchema query

Change notification eventsChange notification events

Interrogation service to determine support for servicesInterrogation service to determine support for services

Read transaction spanning multiple operationsRead transaction spanning multiple operations


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


TopicsTopics










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


CCAPI FTP siteCCAPI FTP site

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.