model driven integration

8/11/2019 Model Driven Integration

1/38

Model Driven Integration

Using CCAPI Technologies

2002 EMS Users Conference

Ralph Mackiewicz, SISCO Inc.


2/38

Agenda

What is Model Driven Integration? Common Information Model

Model Driven Messaging Model Aware APIs

Utility Integration Bus (UIB)


3/38

What is Model Driven

Integration?

An integration architecture that incorporates

application independent information

modeling consistently throughout all aspects

of the integration infrastructure from

messaging, APIs, and data representation.


4/38

Application Independence

Models independent of specific applicationimplementations or functions

Models used for data exchange

No need to change the internal application

model


5/38

Models

Common Information Model (CIM)


6/38

Common Information Model (CIM)

IEC TC57

WG14 Scope:

Asset

Location

Work

IEC TC57

WG13

IEC61970

CIM was originally developed as part of

EPRIs Control Center API project (CCAPI)

and is now being adapted globally within IEC.


7/38

Some CIM Users

NERC

WAPA

WSCC

CAISO MISO

MAIN

ERCOT

NEPCO

BC Hydro

ComEd

ConEd

Consumers

DTE

Duke

Entergy

Southern

EGAT

Illinois Power


8/38

Switch

Measurements

Terminals

Breaker

ConductingEquip.

BaseVoltage

Bus

Measurements

XFMRWindingTAPChanger

CIM View of Power System

Substation

XFMR

VoltageLevel

Measurements


9/38

Traditional View Of SCADA Data

ClientFlat set of

tags

SCADA

Access by tag name


10/38

CIM View Of SCADA Data

ClientHierarchy changes

with network

model changes

SCADA

Bus

XFMR XFMR XFMR XFMR

Bus

Substation

Device or

other

system

relatedviews

supported

Access by Description


11/38

Accessing by Tag


12/38

Point-to-point Model

Transformations

SCADA

Asset

Management

EMS

CIS

OMS

Work

Management N*(N-1)transformations


13/38

Use of a Common

Data Exchange Model

SCADA

Asset

Management

EMS CIS

OMSWork

Management

common data exchange modelcommon data exchange model

N transformations


14/38

Model Mapping Example


15/38

Messaging


16/38

What is Messaging?

ApplicationApplicationBB

Message BusQueueQueue

11

22

55

3344

AppplicationAppplicationAA

Applications use messages to exchange data

Applications are

decoupled fromcommunications

Provides execution

time independence

Scaleable from

small to very large


17/38


18/38

Model Driven Message

Definition

Common Model using UML

Export and transform to XML Schema

Create Message Definitions

Import into messaging middleware

Message

Types


19/38

Model Driven Messages

Implementation independent Consistent across applications

Enables sharing of message processingamong applications

Reduces integration effort and maintenance


20/38

Directed Messaging

Asset

ManagementEMSOMS

Work

Management

Message BusMessage Bus

SCADA


21/38

Publish/Subscribe

SCADA

Asset

ManagementEMSOMS

Work

Management

Message BusMessage Bus

S U B S C R I P T I O N S

Publish


22/38

Benefits of Publish/Subscribe

Eliminates application dependency onspecific sources and destinations.

Lowers maintenance costseasier to

modify data flow.

Improved Scalability.


23/38

Application ProgrammingInterfaces (API)


24/38

Model Driven APIs

The Application Programming Interface(API) presents application data within the

context of a common model.

Data Access Facility (DAF)

Data Acquisition for Industrial Systems (DAIS)

Generic Interface Definition (GID).


25/38

DAF Standard interface to a model server for the

purpose of initializing applications. Ex: Topology processors

Archives

Other power system network model consumers such

as third party data management tools


26/38

DAF Interface Provides

Get/Set of model information Browsing of model to view relationships

and access data Ability to enunciate model changes


27/38


28/38

DAIS Data Access

Standard interface for accessingmeasurement data.

Based on OLE for process control (OPC).

Replaces Microsoft-specific programming idiom

of OPC.

Can be used as the basis for a high speed C++data access interface that is platform independent.


29/38

DAIS Browsing

Supports browsing a hierarchical tree tofind items.

DAIS Item = Data item with value, quality,

etc.

Example Functions:

node_home()

item_home()

find_by_parent()

find_by_type()

get_pathname()

get_ids()


30/38

DAIS Data Access Functions

Synchronous Read/Write: sync_read()

Asynchronous Read/Write: async_read()

Callback functions:

on_data_change() on_read_complete()

sync_write()

async_write()

on_write_complete()


31/38

DAIS Alarming & Eventing

Standard interface for alarms and events

Alarms may CIM elements

Events consist of CIM objects(e.G. Work order)

Example Functions

get_filter () set_filter () get_state()

set_state () query_available_filters ()

set_subscription ()


32/38


33/38



34/38


An integration platform that incorporatesmodeling concepts throughout:

Model awareness distributed across bus

Enforces common data exchange model

consistently.

Model aware APIs. Enables or provides high-level configuration,

management, and analysis tools.


35/38

UIBUIB

UIB Architecture

EAI MiddlewareEAI Middleware APIsAPIs CIMCIM

SCADASCADA

DMSDMS

GISGIS

WMSWMSOMSOMS


36/38

State

EstimatorSCADAODMS

VSA

UIB Use of APIs

DAF

DAIS DA

DAIS Eventing

Archive

UIB


37/38

Application BApplication A

Common Data Exchange Model

Model Driven Integration =

Interoperability

Client Process

Model Translation

API

Message Bus - Middleware

Messages

Server Process

Model Translation

API

Client Requests

Data from Server

Client Receives

Data from Server

Utility Integration

Bus


38/38

Thank You

Ralph MackiewiczSISCO, Inc.

6605 19 Mile Road

Sterling Heights, MI 48314 USA

Tel: +586-254-0020, Fax: +586-254-0053

E-Mail: [email protected]

URL: http://www.sisconet.com/uib.htm

The Standards Based Integration Company

model driven integration

Documents