CIM Implementation at Pacifi Corp Randy Rhodes CIM

CIM Implementation at Pacifi. Corp Randy Rhodes CIM for Planning Project Meeting April 11, 2007

CIM is Pacifi. Corp’s Integration Strategy – Pacifi. Corp is successfully using CIM to design both interfaces and databases 4 4 4 CIM was adopted in 1999 as Pacifi. Corp’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” 4 4 4 Having a common vocabulary reduces semantic misinterpretation Reusing messages minimizes integration costs Minimal knowledge of internal application designs required 4 4 CIM is in use across the company (Power Supply, Customer Service, Power Delivery, Commercial & Trading, Corporate) 37 of 144 applications used in Power Delivery are exchanging CIM-based messages © 2006 PACIFICORP | PAGE 2 – CIM is here to stay

© 2006 PACIFICORP | PAGE 3 Effect of CIM on Power Delivery Systems

Power Delivery IT Strategy Overview CSS SAP Integration Bus = TIBCO + CIM Network Mgmt CADOPS & Ranger – Leverage Corporate and Power Delivery Core Applications: Simplify the IT environment – Deliver Effective Enterprise Application Integration (TIBCO/CIM): Asset Data Synchronization – Realign IT Resources to Deliver GIS & Work Mgt Initiatives – Renovate Disparate Legacy Applications into Core © 2006 PACIFICORP | PAGE 4 ESRI

CIM Implementation Examples 4 4 4 4 Scheduling Single-Person Work (SPS) Billing Wholesale Transmission Transactions Providing Enterprise Reports (Data Warehouse) Integrating EMS/SCADA (ABB Ranger) Forecasting and Risk Management (K 2) Managing Distribution Facilities Joint Use (PADMS - GIS) Monitoring Application Activity for SOX (Trip. Wire) Retail Access © 2006 PACIFICORP | PAGE 5 – Handling Customer Outage Calls (CADOPS, IVR) – Managing Substation and Circuit Load History (OSIsoft PI) – Other Implementation Examples

Outage Call and Customer Call Handling 4 4 4 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, Trouble. UP (also called DMS) and CADOPS All communications between off-site third party provider (TFCC) and Pacifi. Corp are handled through the message bus All IVR steps are stored in IVR log for performance analysis – Extensive testing of performance under high loads. © 2006 PACIFICORP | PAGE 6 – Automated handling of customer account balance check – Automated handling of remote customer meter reading entry – Automated handling of customer outage calls between call center and dispatch applications – Used CIM-based messaging to integrate:

© 2006 PACIFICORP | PAGE 7 Outage/IVR Architecture

© 2006 PACIFICORP | PAGE 8 Outage/IVR: UML model for outage notification

© 2006 PACIFICORP | PAGE 9 Outage example: CIM-based XML schema

SCHOOL (PI) - Substation and Circuit Historian – SCHOOL is an acronym for “Substation and Circuit History Of Operation Load” – our PI historian for T&D planning – Used CIM network model to integrate and manage measurements from several sources 4 4 4 EMS/SCADA – Ranger PI Tags MV/90 – Interval Meter Reads Manual Reads 4 4 Ranger EMS – for PI tags MVStar – for MV/90 reads SCHOOL PI Server SCHOOL Configuration Utility Application – Few model extensions needed; CIM quite complete in Power Systems resource area © 2006 PACIFICORP | PAGE 10 – Used CIM in XML schemas for messaging among

© 2006 PACIFICORP | PAGE 11 Outage example: CIM-based XML schema

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 Pacifi. Corp. © 2006 PACIFICORP | PAGE 12 SCHOOL Configuration Utility

© 2006 PACIFICORP | PAGE 13 SCHOOL: UML model for measurement data

© 2006 PACIFICORP | PAGE 14 SCHOOL Example: CIM-based XML schema

Single Person Scheduling 4 4 4 Processing time lessened Complexity reduced No reusability © 2006 PACIFICORP | PAGE 15 – 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

Transmission Wholesale Billing System 4 4 4 4 4 OASIS – sends transmission readings and short-term losses MVStar – receives interval meter readings Envision – scheduling data from KWH system BPA – sends interval meter readings SAP – gets accounts receivable information CSS – sends consumption data IVR/CSS – sends phoned-in meter reading corrections MVPBS – receives consumption data, meter readings, sends out invoices and accounts receivable K 2 – Trading, price curves, plant operations – Reused analysis from EDW (metering), Retail Access (customers), and SCHOOL project (interval readings) © 2006 PACIFICORP | PAGE 16 – TWBS produces invoices for Pacifi. Corp’s 34 largest wholesale customers (collects over $30 Million of the company’s revenue per year). – CIM format used for all interface messages

Enterprise Data Warehouse – CIM is the foundation for warehouse data structures – Areas implemented that made particular use of the CIM include the following: 4 4 Customer information from CSS Distribution work management from RCMS Customer metering Project financials © 2006 PACIFICORP | PAGE 17 – Generic CIM names for entities and attributes should make integration with multiple source systems and replacement systems easier – Project issues around dates, other attributes

Other Areas – Trading and Risk Management 4 4 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 4 Pole Attachment Data Management System (PADMS) – SOX 4 Change. Audit. Report XSD created to publish changes to operating system and database. © 2006 PACIFICORP | PAGE 18 – Joint Use Tracking

Retail Access – Oregon’s electric restructuring bill (SB 1149) mandated retail access for investor-owned utilities; implemented March 1, 2002 – Pacifi. Corp used CIM messaging for interfaces between Pacifi. Corp's Customer Information System and Itron interval meter reading system – XML schema developed used explicit structure names rather than repeating groups with type codes © 2006 PACIFICORP | PAGE 19 – Extended CIM structure to include details of customer billing and energy service supplier

Business Units Application/ Project Message(s) CIM % of Total in relation to CIM Power Delivery SCHOOL (PI) Load Historian Interval. Read, Substation. Equipment. Measurement. List 60% Outage/Interactive Voice Response Trouble. Calls, Trouble. Report. Alerts, Trouble. Report. Details, Trouble. Report. Summary, Customer Info, Customer Balance, Customer Account Balance Outage. Management 80% Retail Access Register. Read. Request, Bill. Determinant, Cust. Drop, Enroll. DACust, Enrollment. Change, Non. DACust, Reg. ESSRegister, Register. ESS, ESStatus. Change, SESSESSRelationship. Change, Register. Read. Response, Cn. IConsumption, DAEnroll. Consumption, Enrollment. Change, Non. DAEnroll. Consumption, ESSStatus. Change Customer. Meter. Data. Set, Customer. Service. Agreement, Measurment. List, Document, Activity. Record, Customer. Billing, Billing. Determinant 80% Pole Attachment Data Management & GIS Facility. Point, Joint. Use. Agreement, Joint. Use. Attachment, Joint. Use. Notice, Joint. Notice. Request, Facility. Point Asset. List 70% Outage Scheduling Planned. Outage. Change Planned. Outage. Notification 50% Wholesale Billing Transmission. Data, STLoss. Data, LTLoss. Data, Scheduling. Load. Data, Consumption. Data, Invoice. Data Settlement and Market. Clearing 70% EMS/SCADA Weather. Data Measurement. List 100% Transmission © 2006 PACIFICORP | PAGE 20 CIM Usage Details

Business Units Application/ Project Message(s) CIM % of Total in relation to CIM Power Supply/ Generation Availability Information System Geo. Thermal. Plant. Generation Measurement. List 60% Hydro Information Water System Flow. Display Measurement. List 60% Equipment Planning Work. Station Solution. Notification, Performance, Solution. Project, Equipment. Group. Repetitive. Tasks, Inventory. Stocking. Plan, Work. History. Document Work. History 50% K 2 Substation. Equipment. Measurement Fwd. Prc. Forecast, Trades, Volatility. Forecast Energy. Price. Curve, Energy. Transaction Volatility. Forecast(Not in CIM), Trade(Not in CIM), Delivery. Pattern(Not in CIM), Trade. Strategy(Not in CIM), Commondity(Not in CIM, 80% Central Reporting System Mark. To. Market. Data Mark. To. Market (Not in CIM) 80% California ISO EDI 810 Settlement 50% Giving Campaign Employee. Details, Contribution. Payroll. Details Employee (erp. Person) 70% Tripwire Change. Audit. Report Change. Audit (Not in CIM) 90% Commercial & Trading Corporate © 2006 PACIFICORP | PAGE 21 CIM Usage Details

– 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 EAI group – Projects need modelers through unit testing – CIM compromises come back to haunt you – Retaining OO-savvy staff is a challenge © 2006 PACIFICORP | PAGE 22 Lessons Learned

Questions? Randy. Rhodes@Pacifi. Corp. com Janet. Dietz@Pacifi. Corp. com