Randy Rhodes and Janet Dietz December 6, 2006 CIM Implementation at PacifiCorp

© 2006 PACIFICORP | PAGE 2 Agenda –Company Background –CIM “Scorecard” –Two Case Studies –Other Examples –Lessons Learned

© 2006 PACIFICORP | PAGE 3 Key Facts about PacifiCorp –Headquarters in Portland, Oregon –1.6 million customers in six states –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)

© 2006 PACIFICORP | PAGE 5 PacifiCorp Service Area and Plants CA NV AZ UT WY ID OR 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

© 2006 PACIFICORP | PAGE 6 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

© 2006 PACIFICORP | PAGE 7 CIM Scorecard Business UnitsApplication/ Project Message(s)CIM% of Total in relation to CIM Power DeliverySchoolIntervalRead, SubstationEquipment.MeasurementMeasurementList60% OCHIP, IVRLog, IVR/CSS TroubleCalls, TroubleReportAlerts, TroubleReportDetails, TroubleReportSummary, Customer Info, Customer Balance, Customer Account Balance OutageManagement80% RAPRegisterReadRequest, 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% PADMSFacilityPoint, JointUse.Agreement, JointUse.Attachment, JointUse.Notice, JointNoticeRequest, FacilityPoint AssetList70% TransmissionCAPSOPlannedOutage.ChangePlannedOutageNotification50% TWBSTransmissionData, STLossData, LTLossData, Scheduling.LoadData, ConsumptionData, InvoiceData Settlement and MarketClearing70% EMSScadaWeatherDataMeasurementList100%

© 2006 PACIFICORP | PAGE 8 CIM Scorecard Cont’d Business UnitsApplication/ Project Message(s)CIM% of Total in relation to CIM Power Supply/ Generation AISGeoThermalPlantGenerationMeasurementList60% HIWSFlowDisplayMeasurementList EPWSolutionNotification, Performance, SolutionProject, EquipmentGroupRepetitiveTasks, Inventory.StockingPlan, WorkHistoryDocument Work WorkHistory Commercial & Trading K2SubstationEquipment.Measurement FwdPrcForecast, Trades, VolatilityForecast EnergyPriceCurve, EnergyTransaction VolatilityForecast(Not in CIM), Trade(Not in CIM), DeliveryPattern(Not in CIM), TradeStrategy(Not in CIM), Commondity(Not in CIM, 80% CRSMarkToMarketDataMarkToMarket (Not in CIM)80% CAISOEDI810Settlement50% CorporateGiving CampaignEmployeeDetails, ContributionPayrollDetailsEmployee (erpPerson)70% SOXChangeAuditReportChangeAudit (Not in CIM)90%

© 2006 PACIFICORP | PAGE 9 CIM Implementation Examples –Case Studies Discussed Today  Handling Customer IVR and Outage Calls  Managing Substation and Circuit Load History (OSIsoft PI) –Other Implementation Examples  Scheduling Single-Person Work (SPS)  Billing Wholesale Transmission Transactions  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

© 2006 PACIFICORP | PAGE 10 Outage Call and Customer Call Handling –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:  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.

© 2006 PACIFICORP | PAGE 11 OUTAGE/IVR: UML model for outage notification

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

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

© 2006 PACIFICORP | PAGE 14 Outage/IVR Architecture

© 2006 PACIFICORP | PAGE 15 SCHOOL (PI) - Substation and Circuit Historian –Successful implementation of CIM network model structure –CIM used in historical database for storing Subview, MV90, and SIGMA readings –CIM used in XML schemas for messaging among  Ranger EMS PI Servers  MVStar – Interval meter readings from Itron MV/90  Configuration Admin Utility Application –CIM quite complete in Power Systems resource area; few model extensions needed.

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

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

© 2006 PACIFICORP | PAGE 18 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 measurements used in T&D planning at PacifiCorp.

A Version of a Future Vision PB/DL Clients T&D Planning Model (PSS/E, MOD, ODMS) Time Series Data Sources Ranger EMS MV-90 ESRI GIS SCHOOL Config (Oracle CIM) SAP XFMR, LINE, GEN (MS-Access DB) Non Time-Series Sources Integration Bus = TIBCO + CIM Network Context (MDB/Foundation) T&D Operating Model (Ranger EMS)... OSIsoft RtPortal Web Client PTI Model-on-Demand Web Client Ranger IS500 Web Client Strategy: Combine these data repositories … and synchronize across core applications (Ranger EMS, SAP, and ESRI GIS) to create a virtual Asset Register

© 2006 PACIFICORP | PAGE 20 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  Processing time lessened  Complexity reduced  No reusability

© 2006 PACIFICORP | PAGE 21 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 format used for all interface messages  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  IVRCSS – sends phoned-in meter reading corrections  MVPBS – receives consumption data, meter readings, sends out invoices and accounts receivable  K2 – Trading, price curves, plant operations –Reused analysis from EDW (metering), Retail Access (customers), and SCHOOL project (interval readings)

© 2006 PACIFICORP | PAGE 22 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

© 2006 PACIFICORP | PAGE 23 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.

© 2006 PACIFICORP | PAGE 24 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

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

Questions?