Virginia Pai and Janet Dietz

June 2007

CIM Implementation at PacifiCorp

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 2

Agenda

– What is the CIM?

– Company Background

– PacifiCorp’s CIM “Scorecard”

– Four Case Studies

– Other Examples

– Lessons Learned

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 3

What is the CIM?

– Common Information Model sponsored by the International Electrotechnical commission A unified modeling language (UML) based information model Specific to the electric power industry Represents real-world objects and information entities

– Designed to enable integration of applications Provides a common model behind all messages exchanged among applications Provides definitions for common data classes

–

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 4

A view of the core CIM model

ControlHouseEquipmentCurveSchedData

CurveSchedFormula

CurveSchedule

0..n

0..1

+CurveScheduleDatas0..n

+CurveSchedule

0..1

0..n

0..1

+CurveScheduleFormula

0..n

+CurveSchedule

0..1

Naming

EquipmentContainer

Equipment

0..1

0..n

+MemberOf_EquipmentContainer

0..1

+Contains_Equipments0..n

CompanyPSRType

PowerSystemResource

0..n

0..n

+OperatedBy_Companies0..n

+Operates_PSRs

0..n

0..1

0..n

+PSRType

0..1

+PowerSystemResource 0..n

SubControlArea

Substation

0..1

1..n

+MemberOf_SubControlArea

0..1

+Contain_Substations1..n

Bay0..n

0..1

+Contains_Bays

0..n

+MemberOf_Substation

0..1

Terminal

BasePower

VoltageLevel

1

0..n

+MemberOf_Substation1

+Contains_VoltageLevels0..n

0..1

0..n

+MemberOf_VoltageLevel0..1

+Contains_Bays

0..n

ConductingEquipment

0..n

1

+Terminals0..n

+ConductingEquipment1

BaseVoltage

0..n

0..1

+BaseVoltage0..n

+BasePower

0..1

0..n

1+VoltageLevel

0..n +BaseVoltage

1

0..n

0..1

+ConductingEquipment

0..n

+BaseVoltage

0..1

CoreVersion

version = Core_v003date = 2004-07-02

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 5

How can CIM be used in the Utility Enterprise?

– The CIM is more than an information model standard in UML

– The CIM can be expressed in XML to create interface messages

– The CIM helps data preparation Provides common set of semantics and data representation regardless

of source of data Improves data quality and enables data validation

– The CIM promotes data exchange Provides a common language and format Provides a common set of services for sharing data

– The CIM enables application integration Provides the basis for a standards-based integration format

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 6

Why have standards-based integration?

– Improves the ability to integrate business processes with Commercial-Off-The-Shelf applications

– Provides a mechanism to leverage effort and lower risk by working on common functionality with other companies and vendors

– Positions a company to benefit from an evolving marketplace of conforming applications

– Lowers effort for integrating legacy systems with other enterprise systems

– Improves enterprise data quality and facilitates enterprise decision support processes

– Improves the consistency and reuse of data models and messages

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 7

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 is standard design practice PacifiCorp vendors are getting used to the idea PacifiCorp’s data warehouse is based on the CIM EMS/SCADA system (Ranger) uses a CIM-based data maintenance tool

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 8

Key Facts about PacifiCorp

– Headquarters in Portland, Oregon– 1.6 million customers in six states– Service area covers 136,000 square miles– 15,580 miles of transmission line – 59,510 miles of distribution line – 908 substations– Three divisions:

Pacific Power – Oregon, Washington and California Rocky Mountain Power – Utah, Wyoming and Idaho PacifiCorp Energy – generation and mining

• 69 generating plants across West; net capability of 8,470 MW– Owned by Mid-American Energy Holdings Company (MEHC)

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 9

PacifiCorp Service Area and Plants

CA

NV

AZ

UT

WY

IDOR

WA

MT

CO

PacifiCorp Service Territory

Thermal Plants

Gas-Fueled Thermal Plants

Wind Projects

Geothermal Plants

Coal Mines

Hydro Systems

Generation Developments

500 kV Transmission Lines

345 kV Transmission Lines

230 kV Transmission Lines

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 1

0

CIM Scorecard – Examples of CIM use

Business Units

Application/Project

Message(s) CIM Pct of message that is CIM

Power Delivery

Substation Measurements

IntervalRead, SubstationEquipment.Measurement MeasurementList 90%

Outage Center Call Handing

TroubleCalls, TroubleReportAlerts, TroubleReportDetails, TroubleReportSummary, Customer Info, Customer Balance, Customer Account Balance

OutageManagement 80%

Retail Access Project

RegisterReadRequest, BillDeterminant, CustDrop, Enroll.DACust, EnrollmentChange, NonDACust, Reg.ESSRegister, Register.ESS, ESStatusChange, SESSESSRelationshipChange, RegisterReadResponse, CnIConsumption, DAEnrollConsumption, EnrollmentChange, NonDAEnrollConsumption, ESSStatusChange

CustomerMeterDataSet,CustomerServiceAgreement,MeasurmentList,Document, ActivityRecord, CustomerBilling, BillingDeterminant

80%

Pole Attachment System

FacilityPoint, JointUse.Agreement, JointUse.Attachment, JointUse.Notice, JointNoticeRequest, FacilityPoint

AssetList 70%

Transmission Transmission Planned Outages

PlannedOutage.Change PlannedOutageNotification 50%

Transmission Wholesale Billing System

TransmissionData, STLossData, LTLossData, Scheduling.LoadData,ConsumptionData, InvoiceData

Settlement and MarketClearing

70%

EMS SCADA WeatherData MeasurementList 100%

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 1

1

CIM Scorecard Cont’d

Business Units

Application/Project

Message(s) CIM Pct of message that is CIM

Power Supply/Generation

Availability Information System

GeoThermalPlantGeneration MeasurementList 60%

Hydro Information Website

FlowDisplay MeasurementList 100%

Generation Equipment Performance Work Management

SolutionNotification, Performance, SolutionProject, EquipmentGroupRepetitiveTasks, Inventory.StockingPlan, WorkHistoryDocument

WorkWorkHistory

90%

Commercial & Trading

CRS MarkToMarketData MarkToMarket (Not in CIM) 80%

California ISO interface

EDI810 Settlement 50%

Corporate Giving Campaign

EmployeeDetails, ContributionPayrollDetails Employee (erpPerson) 70%

Sarbanes Oxley Audit

ChangeAuditReport ChangeAudit (Not in CIM) 90%

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 1

2

CIM Implementation Examples

– Case Studies Discussed Today Handling Customer IVR and Outage Calls Managing Substation and Circuit Load History (OSIsoft PI) Ranger CIM data maintenance tool Billing Wholesale Transmission Transactions

– Other Implementation Examples Scheduling Single-Person Work (SPS) Providing Enterprise Reports (Data Warehouse) Integrating EMS/SCADA (ABB Ranger) Forecasting and Risk Management (K2) Managing Distribution Facilities Joint Use (PADMS - GIS) Monitoring Application Activity for SOX (TripWire) Retail Access

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 1

3

Model-driven integration process

– Step 1: define integration scenario according to business process needs

– Step 2: identify message types and their contents required to support integration scenarios

– Step 3: extend PacifiCorp’s information model to incorporate new types of information

– Step 4: define new or customize pre-defined message types based on the CIM

– Step 5: map message field names to application and database field names

 

Step 1: What data flow isneeded?

Reqirements Specs, withUse Cases,

Integration Scenarios,and/or Event Sequence

Diagrams

Step 2: What is in eachmessage?

Step 3: Re-use existingmessages where

possible, extend CIMwhere not

Identified CIMExtensions: Classes Attributes Relations

Begin Here For EachBusiness Process

Curre

nt IE

C TC

57CI

M (C

omm

onIn

form

atio

n M

odel

)

Paci

fiCor

pIn

form

atio

n M

odel

(CIM

Bas

ed)

Step 4: Define New OrCustomize Pre-Defined

Message Types

New MessageTypes Specified

in XML

Step 6: SupportImplementation

Team

Information ExchangeModeling Complete

Step 5: Map MessageField Names

TransformationMap

Pre-definedMessage Types: Internal IEC OAG

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 1

4

Outage Call and Customer Call Handling

– Automated handling of customer account balance check– Automated handling of remote customer meter reading – Automated handling of customer outage calls between call center

and dispatch applications– Used CIM-based messaging to integrate

Customer phone number recognition between IVR and customer directory

Outage detail lookup between IVR and CADOPS Outage detail lookup between GTx and CADOPS Outage creation between IVR, TroubleUP (also called DMS) and

CADOPS All communications between off-site third party provider (TFCC) and

PacifiCorp are handled through the message bus All IVR steps are stored in IVR log for performance analysis

– Much testing around performance and handling of large load.

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 1

5

Outage/IVR Architecture

IVR Environment

Customers

CADOPS Environment

OCHIP EnvironmentMainfame

GTX Info

PhoneCalls (Outage, Check Acct Balance,Send Meter Read)

Corporate Environment

CSSDatabase

IVR System

CADOPS PDX

CADOPSSLC

CADOPS WYO

EAI Environment

EAI Servers

Outage Status Outage StatusOutage Status

DMS Database

Outage Info

Acct Balance,Outage Status

Web Environment

Web Server

Outage Info

Outage Info Via Trouble Viewer

WebPage

TFCC

Excess Outage calls go to vendor during a major storm

Outage Info

DMZ Environment

TFCC Call CenterAll interfaces are

based on the CIM

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 1

6

OUTAGE/IVR: UML model for outage notification

OutageStep

OutageRecord

+OutageSteps

+OutageRecord1

1..n

1

1..n

ErpPerson(f rom ERP_Support)

Document(f rom DocumentInheritance)

0..n

0..n

+fromDocuments

0..n

+toDocuments0..n

+ErpPersons

+Documents0..n

0..n

0..n

0..n

CustomerAccount(f rom Consumers)

CustomerAgreement(f rom Consumers)

1

0..n

+CustomerAccount1

+CustomerAgreements0..n

OutageNotification(f rom TroubleTickets)

TroubleTicket(f rom TroubleTickets)

ServiceLocation

(from Locatio...0..11..n

+CustomerAreement

0..1

+ServiceLocations

1..n

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 1

7

Outage example: CIM-based XML schema

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 1

8

Outage example: CIM-based XML schema

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 1

9

SCHOOL (PI) - Substation and Circuit Historian– Successful implementation of CIM network model structure for

managing substation measurements – both interfaces and database design

– System combines several older applications for storing substation measurements

– CIM used to design configuration database that shows configuration of substations and measurements

– CIM used in XML schemas for messaging among Ranger EMS PI Servers MVStar – Interval meter readings from Itron MV/90 Configuration Admin Utility Application

– Reused interface from legacy system when we moved to Ranger– CIM quite complete in Power Systems resource area; few model

extensions needed– System not used for network modeling

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 2

0

SCHOOL: UML model for measurement data

Equipment(f rom Core)

EquipmentContainer(f rom Core)

+Contains_Equipments

+MemberOf_EquipmentContainer

0..1

0..n

0..1

0..n

Substation(f rom Core)

PSRType(f rom Core)

ConductingEquipment(f rom Core)

PowerSystemResource(f rom Core)

0..n

0..1

+PowerSystemResource 0..n+PSRType

0..1

PowerTransformer(f rom Wires)

MeasurementType(f rom Meas)

MeasurementValueQuality(f rom Meas)

MeasurementValue(f rom Meas)

1

1

+MeasurementValueQuality1

1

MeasurementValueSource(f rom Meas)

+MeasurementValueSource1

0..n

1

0..n

Compensator(f rom Wires)

ACLineSegment(f rom Wires)

Line(f rom Wires)

0..1

0..n

+MemberOf_Line

0..1

+Contains_ACLineSegments0..n

RegulatingCondEq(f rom Wires)

Measurement(f rom Meas)

1

0..n

+MemberOf_PSR1

+Contains_Measurements

0..n0..n

1

+Measurements

0..n

+MeasurementType

1

AnalogValue(f rom Meas)

Analog(f rom Meas)

+Contain_MeasurementValues

+MemberOf_Measurement1

1..*

1

1..*

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 2

1

SCHOOL Example: CIM-based XML schema

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 2

2

Control Center

Ranger Historian PDX

Ranger Historian SLC

SCHOOL PI Server

Hand Held Terminals

GridSense LineTrackers

Corporate Environment

Reports

<<RDAS>>PCC

Primary Ranger

AppServer

<<RDAS>>WCC

<<RDAS>>SCC

DMZRanger Corporate PI Servers

MV-STAR

Ranger Historian SLC

Ranger Historian PDX

`

PlanningTechnologies

`

AreaPlanning

`

Field Engineering

`

TransmissionPlanning

`

Regulation

`

GLOMESMaster Station

`

PI Manual Logger Workstations

SCHOOL Configuration

UtilityModel Config (Oracle

CIM)

SCHOOL Configuration Utility

This is the SCHOOL Configuration Utility application, used to maintain the SCHOOL

Configuration Database. This is an Oracle CIM database used to

manage all load measurementsused in T&D planning at

PacifiCorp.

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 2

3

Ranger CIM data maintenance tool

– CIM Data Engineering Toolkit Based on the CIM, not on not a translation from CIM to a proprietary

data engineering schema Based on ESRI ArcGIS technology ArcSDE – Spatial Database Engine

• Oracle application• Multi-user, versioned database server

ArcCatalog – GDB schema maintenance• Schema generation based on UML created in Visio• Schema maintenance of attributes, classes, relationships

ArcMap – main graphical editing client application• Graphical/tabular data engineering environment• Many ABB custom add-ins

Multi-user database manager, supporting maintenance of all RANGER configuration data

Imports and exports CIM XML for model exchange

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 2

4

Ranger CIM data entry paths (ABB)

Graphic courtesy of ABB

Tool accepts CIM XML as import

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 2

5

Ranger CIM tool example

Graphic courtesy of

ABB

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 2

6

Ranger CIM measurement editor

Graphic courtesy of

ABB

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 2

7

Transmission Wholesale Billing System

– TWBS produces invoices for PacifiCorp’s 34 largest wholesale customers (collects over $30 Million of the company’s revenue per year).

– CIM used for all interface messages OASIS – sends transmission readings and short-term losses MVStar – receives interval meter readings (reused) Envision – scheduling data from KWH system BPA – sends interval meter readings SAP – gets accounts receivable information CSS – sends consumption data (reused) IVRCSS – sends phoned-in meter reading corrections MVPBS – receives consumption data, meter readings, sends out

invoices and accounts receivable (reused) K2 – Trading, price curves, plant operations

– Reused analysis from EDW (metering), Retail Access (customers), and SCHOOL project (interval readings)

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 2

8

Transmission Billing interface to SAP

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 2

9

Single Person Scheduling

– A single person scheduling (SPS) system facilitates improved management of short duration, high volume single person work assignments.

– CIM attribute names used for data attributes in repository data base

– CIM attribute names used for data elements in simplified XML schema

– Full CIM XML structure rejected by project Used CIM attribute names, but not relationships Processing time lessened Complexity reduced No reusability

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 3

0

Enterprise Data Warehouse

– CIM is the foundation for warehouse data structures– Areas implemented that made particular use of the CIM include

the following: Customer information from CSS Distribution work management from RCMS Customer metering Project financials

– Generic CIM names for entities and attributes should make integration with multiple source systems and replacement systems easier

– Project issues around dates, other attributes– Director of Warehouse project said “we would never have

achieved as much as we did in so short a time without the CIM”

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 3

1

Retail Access

– Oregon’s electric restructuring bill (SB 1149) for investor-owned utilities, implemented March 1, 2002

– PacifiCorp used CIM messaging for interfaces between PacifiCorp's Customer Information System and Itron interval meter reading system

– Extended CIM structure to include details of customer billing and energy service supplier

– XML schema developed used explicit structure names rather than repeating groups with type codes

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 3

2

Other Areas

– Trading and Risk Management Extensions were created for trading applications using both

CIM and Financial Products Markup Language (FPML) All new trading application interfaces are designed with CIM

and extensions• Forecasting (River, Plant Generation, etc...)• Risk Management (Mark to Market)• Gas Management extensions will be next

– SOX ChangeAuditReport XSD created to publish changes to operating

system and database.

© 2

00

7 P

AC

IFIC

OR

P |

PA

GE 3

3

Lessons Learned

– CIM integration works well, especially for Power Delivery– Project work is reduced when the CIM data entities and

relationships are mapped before detailed attribute modeling begins

– Messages in XSD format are accessible and reusable– Project management: additional data modeling cost of CIM

needs to be understood at PM level– Actual savings come from reuse, data clarity, and quality– CIM expertise currently resides in our EAI group– Projects need modelers through unit testing– CIM compromises come back to haunt you– Abstract thinking in projects remains a challenge

Questions?

Virginia.Pai@PacifiCorp.com

Janet.Dietz@PacifiCorp.com

More information at www.cimuser.org