© A

BB

Ltd

. -

1 -

ABB Experience

Neela Mayur

CIM Users’ Group Meeting

June 12, 2008

© A

BB

Inc

. -

2 -

Agenda ABB participation in CIM Development

Definition of CIM

ABB Network Manager CIM Architecture

CIM support from ABB products

ABB customer experiences

Technology

Recommendations

Conclusions

© A

BB

Inc

. -

3 -

ABB participation in CIM Development ABB was involved from Day 1 when EPRI started the

CIM initiative in 1994

In 2001, ABB delivered a CIM based data engineering system

For more than 12 years, Lars – Ola Osterlund from ABB has been contributing to CIM model standardization within IEC

ABB has actively participated in the inter op tests since 2000

© A

BB

Inc

. -

4 -

What The CIM Is And Is Not What the CIM is

CIM is an interface definition

An information model including power system connectivity for data exchange

A suite of specifications from IEC TC57

An electronic model in UML

What the CIM is not Sometimes CIM is referred as a database

This is not correct

It is possible to use CIM as a database schema but this has consequences Performance impact because of inheritance in CIM

vulnerability to changes in the CIM standard

© A

BB

Inc

. -

5 -

Evolution of CIM CIM Changes And Will Continue To Do So

Support for new functions is continuously added DMS interfaces added by WG14

Energy market interfaces added by WG16

CIM for planning interfaces added by WG13

Utilities having projects using the CIM where results are feed back to IEC ERCOT

ELIA

Discovered issues and errors require changes Interoperability tests

Utilities making EAI projects using the CIM

© A

BB

Inc

. -

6 -

ABB Network Manager (EMS) CIM Architecture

Data Engineering/Modeler tool

CIMXMLModel Import

CIMXMLModel Data

CIMXMLModelExport

Online System

GraphicsGeneration

OracleCIMXML

Real time Export

CIMXMLReal time

Data

CIMXMLReal time

Import

DAIS/DAServer

DAIS/A&EServer

Run TimeRTDB

DAIS/DA API

DAIS/A&E API

© A

BB

Inc

. -

7 -

CIM support from ABB products Data Engineering Tool for EMS

CAISO specified support for CIM in 1999 Main Objective

Exchange network model in a standard format to improve efficiency Auto generated one-line diagrams

ABB delivered DE tool in 2001 to meet the objectives Based on ESRI GIS system Rich in Functionality (improved over last 6 years)

Auto generation of substation diagrams Import CIM xml file Graphical compare of new input with existing data Export CIM xml file Real time State Estimator data exchange in CIM format between EMS

and Market system Multi model maintenance

© A

BB

Inc

. -

8 -

CIM support from ABB products

Data Engineering Tool for EMS Full model export/import

Load Flow on imported models

Graphics generation from imported models

Incremental model export/import

On going maintenance to support the latest changes to the standard

Model data support real time data exchange DAIS/DA

ICCP

SE results Using MOM

ABB’s Market Applications support model initialization using CIM xml

ABB OMS Applications support model initialization using distribution CIM xml

© A

BB

Inc

. -

9 -

ABB customer Experience CAISO – Dual Model Maintenance (one for EMS and one for Market)

Exchange model between EMS and Market Applications Exchange real time State Estimator results in CIM format using MOM

NYISO – Exchange model between EMS and Market Applications Austin Energy – Model exchange ERCOT KCPL – Condition Based Maintenance Tri State – Import External Model from WECC, WAPA ERCOT – Initialize market Applications using CIM Com ED – Distribution CIM usage- extract data from Small World GIS and

exported in CIM format to be ABB DMS applications Serious performance problem

STANET – Exchange Data with Swedish Grid ELIA – Customer Developed CIM exporter for internal Application usage CENACE – Internal use PacificCorp – Internal use

© A

BB

Inc

. -

10 -

CIM is PacifiCorp’s Integration Strategy PacifiCorp is successfully using CIM to design both

interfaces and databases CIM was adopted in 1999 as PacifiCorp’s application

integration standard Used for both messaging and database design for new

projects Existing interfaces are reworked when the need arises

CIM-based integration viewed internally as “Best Practice” Having a common vocabulary reduces semantic

misinterpretation Reusing messages minimizes integration costs Minimal knowledge of internal application designs required

CIM is here to stay CIM model-driven integration is standard design practice PacifiCorp vendors are getting used to the idea

© A

BB

Inc

. -

11 -

Technologies Used

Importer XSLT with existing standard importer

Custom written translator

Exporter Oracle views and report generator

Custom written translator

© A

BB

Inc

. -

12 -

Experiences with different Technologies XSLT

Pros Leverage current functionality of CSV import

Powerful and high productivity

Easy to adapt to changing CIM standard

Cons Scalability and performance issues for complex transformations

For complex transformations incremental import is difficult

Oracle views and report generator Pros

Powerful and high productivity

Easy to adapt to changing CIM standard

Good scalability and performance

© A

BB

Inc

. -

13 -

Experiences with different Technologies Custom applications

Pros Easier (but not for granted) to get scalability and good performance

Cons High ongoing maintenance

© A

BB

Inc

. -

14 -

Recommendations Put complex transformations in RDBMS

Gives good performance and scalability

It is efficient to make complex transformations in RDBMS

Easy to support incremental CIM XML data exchange

Put simple transformations in XSLT Easiest way to process XML files

A single XML file scan in XSLT is efficient, no scalability or performance penalty

© A

BB

Inc

. -

15 -

Conclusions Network Manager data model is very close to the CIM

Makes transformations from CIM to Network Manager simple

Plan to change Network Manager Data Model where the difference in CIM and ABB model is significant