CIM Implementation at PacifiCorp

Virginia Pai and Janet Dietz June 2007

Agenda
What is the CIM? Company Background PacifiCorps CIM Scorecard Four Case Studies Other Examples Lessons Learned

2007 PACIFICORP | PAGE 2

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

2007 PACIFICORP | PAGE 3

A view of the core CIM model

N am in g C urve S c h ed F o rm u la 0 .. n PSRType +PSRType +PowerSystemResource 0..n 0..1 + C urve S c h e du le F o rm u la C om pa n y 0..n +OperatedBy_Companies 0..n +Operates_PSRs +MemberOf_EquipmentContainer EquipmentContainer 0..1 0..n +Contains_Equipments Equipment C on t ro lH ou s e E q u ip m e n t + C urve S c h e du le D at a s 0 .. n C urve S c h ed D at a + C urve S c h e du le 0 .. 1 C urve S c h ed u le 0 .. 1 + C urve S c h e du le

PowerSystemResource

C on d u c t ing E qu i p m e nt 0..n 1 + C on d u c t in g E q u ip m e n t + Te rm ina ls 0 .. n Te rm i na l +ConductingE qui pment CoreVersion version = Core_v003 date = 2004-07-02

S ub C on t ro lA re a 0 .. 1 + M e m be rO f_ S u b C o n tro lA re a

+ C on t a in_ S u bs t at io n s 1 .. n +MemberOf_Substation S ub s ta t io n 0..1 1 +MemberOf_Substation

Ba s e P o we r 0 .. 1 + B as e P o w e r

+BaseVoltage + B as e V o lt a g e +Contains_V oltageLevels 0 .. n 0..n 0..1 +VoltageLevel 1 VoltageLevel B as e V o lt a ge +BaseVoltage 0..n 0..1 +MemberOf_VoltageLevel +Contains_Bays 0..n 0..n Bay +Contains_Bays

2007 PACIFICORP | PAGE 4

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

 
2007 PACIFICORP | PAGE 5

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

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

2007 PACIFICORP | PAGE 6

CIM is PacifiCorps Integration Strategy

PacifiCorp is successfully using CIM to design both interfaces and databases


 

CIM was adopted in 1999 as PacifiCorps 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
2007 PACIFICORP | PAGE 7

CIM is here to stay

   

CIM is standard design practice PacifiCorp vendors are getting used to the idea PacifiCorps data warehouse is based on the CIM EMS/SCADA system (Ranger) uses a CIM-based data maintenance tool

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
2007 PACIFICORP | PAGE 8

Owned by Mid-American Energy Holdings Company (MEHC)

PacifiCorp Service Area and Plants

WA
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
2007 PACIFICORP | PAGE 9

MT OR ID WY NV CA UT CO

AZ

CIM Scorecard Examples of CIM use

Business Units Application/ Project Message(s) CIM Pct of message that is CIM 90% 80%

Power Delivery

Substation Measurements Outage Center Call Handing

IntervalRead, SubstationEquipment.Measurement TroubleCalls, TroubleReportAlerts, TroubleReportDetails, TroubleReportSummary, Customer Info, Customer Balance, Customer Account Balance RegisterReadRequest, BillDeterminant, CustDrop, Enroll.DACust, EnrollmentChange, NonDACust, Reg.ESSRegister, Register.ESS, ESStatusChange, SESSESSRelationshipChange, RegisterReadResponse, CnIConsumption, DAEnrollConsumption, EnrollmentChange, NonDAEnrollConsumption, ESSStatusChange FacilityPoint, JointUse.Agreement, JointUse.Attachment, JointUse.Notice, JointNoticeRequest, FacilityPoint PlannedOutage.Change

MeasurementList OutageManagement

Retail Access Project

CustomerMeterDataSet, CustomerServiceAgreemen t, MeasurmentList, Document, ActivityRecord, CustomerBilling, BillingDeterminant AssetList

80%

Transmission

Transmission Planned Outages Transmission Wholesale Billing System EMS SCADA

PlannedOutageNotification

50%

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

Settlement and MarketClearing

70%

MeasurementList

100%

2007 PACIFICORP | PAGE 10

Pole Attachment System

70%

CIM Scorecard Contd

Business Units Application/ Project Message(s) CIM Pct of message that is CIM 60%

Power Supply/ Generation

Availability Information System Hydro Information Website Generation Equipment Performance Work Management

GeoThermalPlantGeneration

MeasurementList

FlowDisplay

MeasurementList

100%

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

Work WorkHistory

90%

Commercial & Trading

CRS

MarkToMarket (Not in CIM)

80%

California ISO interface Corporate Giving Campaign Sarbanes Oxley Audit

EDI810

Settlement

50%

EmployeeDetails, ContributionPayrollDetails ChangeAuditReport

Employee (erpPerson) ChangeAudit (Not in CIM)

70% 90%

2007 PACIFICORP | PAGE 11

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

      

2007 PACIFICORP | PAGE 12

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

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 PacifiCorps information model to incorporate new types of information Step 4: define new or customize predefined message types based on the CIM Step 5: map message field names to application and database field names

2007 PACIFICORP | PAGE 13

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


  

Much testing around performance and handling of large load.

2007 PACIFICORP | PAGE 14

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

Outage/IVR Architecture
CADOPS Environment TFCC

Outage Info Via Trouble Viewer WebPage

All interfaces are based on the CIM

TFCC Call Center

CADOPS SLC

CADOPS PDX

CADOPS WYO DMZ Environment Excess Outage calls go to vendor during a major storm

Outage Status Outage Status Outage Status

Web Environment Outage Info

EAI Environment

Outage Info Customers IVR Environment

IVR System Outage Info Web Server EAI Servers Phone Calls (Outage, Check Acct Balance, Send Meter Read)

DMS Database GTX Info Acct Balance, Outage Status

CSS Database

Mainfame OCHIP Environment Corporate Environment

2007 PACIFICORP | PAGE 15

OUTAGE/IVR: UML model for outage notification

ErpPerson
(f rom ERP_Support)

OutageRecord 0..n +OutageRecord 1 +ErpPersons 0..n +Documents Document

(f rom DocumentInheritance) 0..n

+toDocuments

TroubleTicket
(f rom TroubleTickets)

0..n

1..n +OutageSteps OutageStep OutageNotification

(f rom TroubleTickets)

+fromDocuments Custome rAccount

(f rom Consumers)

+CustomerAccount

Servi ceLocatio n
(from Locatio...

1..n +ServiceLocations

0..1

+CustomerAgreements 0..n CustomerAgreement

(f rom Consumers)

+CustomerAreement

2007 PACIFICORP | PAGE 16

Outage example: CIM-based XML schema

2007 PACIFICORP | PAGE 17

Outage example: CIM-based XML schema

2007 PACIFICORP | PAGE 18

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
  

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

2007 PACIFICORP | PAGE 19

Ranger EMS PI Servers MVStar Interval meter readings from Itron MV/90 Configuration Admin Utility Application

SCHOOL: UML model for measurement data

Measurement
(f rom Meas)

Analog
(f rom Meas)

RegulatingCondEq
(f rom Wires)

Compens ator
(f rom Wires)

0..n +Contains_Measurements

+Measurements 0..n +MeasurementType 1 MeasurementType

(f rom Meas)

1 +MemberOf_Measurem ent

+MemberOf_PSR 1 PowerSystemResource
(f rom Core)

+PowerSystemResource ConductingEquipment
(f rom Core)

0..n +PSRType 0..1PSRType MeasurementValueSource

(f rom Meas)

Equipment
(f rom Core)

0..n +Contains_Equipments 0..1 PowerTransformer

(f rom Wires)

(f rom Core)

1 +MeasurementValueSource

+Contain_MeasurementValues 1..*
(f rom Meas)
2007 PACIFICORP | PAGE 20

Line
(f rom Wires)

EquipmentContainer
(f rom Core)

0..n MeasurementValue
(f rom Meas)

AnalogValue

+MemberOf_Line +MemberOf_EquipmentContainer 0..1 +Contains_ACLineSegments 0..n Substation ACLineSegment

(f rom Wires) (f rom Core)

1 +MeasurementValueQuality 1 MeasurementValueQuality
(from Meas)

SCHOOL Example: CIM-based XML schema

2007 PACIFICORP | PAGE 21

SCHOOL Configuration Utility

Hand Held

GridSense

Reports

2007 PACIFICORP | PAGE 22

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 measurements used in T&D planning at PacifiCorp.

Ranger CIM data maintenance tool

CIM Data Engineering Toolkit
  

 

2007 PACIFICORP | PAGE 23

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

Ranger CIM data entry paths (ABB)

Tool accepts CIM XML as import

2007 PACIFICORP | PAGE 24

Graphic courtesy of ABB

Ranger CIM tool example

Graphic courtesy of ABB

2007 PACIFICORP | PAGE 25

Ranger CIM measurement editor

Graphic courtesy of ABB

2007 PACIFICORP | PAGE 26

Transmission Wholesale Billing System

TWBS produces invoices for PacifiCorps 34 largest wholesale customers (collects over $30 Million of the companys revenue per year). CIM used for all interface messages
       

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

2007 PACIFICORP | PAGE 27

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

Transmission Billing interface to SAP

2007 PACIFICORP | PAGE 28

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
   

2007 PACIFICORP | PAGE 29

Used CIM attribute names, but not relationships Processing time lessened Complexity reduced No reusability

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

2007 PACIFICORP | PAGE 30

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

Retail Access
Oregons 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
2007 PACIFICORP | PAGE 31

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

2007 PACIFICORP | PAGE 32

ChangeAuditReport XSD created to publish changes to operating system and database.

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

2007 PACIFICORP | PAGE 33

More information at www.cimuser.org

Questions?
Virginia.Pai@PacifiCorp.com Janet.Dietz@PacifiCorp.com