Randy Rhodes EMS User Group Conference September 25, 2007

1. CIM as an Enterprise Tool at PacifiCorp Randy Rhodes EMS User Group Conference September 25, 2007

2. Agenda • Company Background • Case Studies • Close to the Control Center • Elsewhere in the Enterprise • PacifiCorp’s CIM “Scorecard” • Lessons Learned • Future Plans

3. Headquarters in Portland, Oregon 1.67 million customers in six states 15,622 miles of transmission line, 58,360 miles of distribution line, 900 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 9,140 MW Owned by Mid-American Energy Holdings Company (MEHC) Key Facts about PacifiCorp

4. PacifiCorp Service Area and Plants WA PacifiCorp Service Territory MT Thermal Plants OR Gas-Fueled Thermal Plants ID Wind Projects WY Geothermal Plants NV Coal Mines Hydro Systems CA CO UT Generation Developments 500 kV Transmission Lines 345 kV Transmission Lines AZ 230 kV Transmission Lines

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 needarises • 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

7. PacifiCorp Uses Model-Driven Integration • 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

8. CIM Implementation Examples • Case Studies Discussed Today • Handling Customer IVR and Outage Calls (ABB CADOPS) • Managing Substation and Circuit Load History (OSIsoft PI) • Managing EMS Network Model (ABB Network Manager) • Other Implementation Examples • Billing Wholesale Transmission Transactions (TWBS) • Scheduling Single-Person Work (SPS) • Providing Enterprise Reports (Data Warehouse) • Trading and Risk Management (K2) • Monitoring Application Activity for SOX (TripWire) • Retail Access

9. CIM for Outage-Related Customer Call Handling • Automated Call Handling • Customer account balance check • Remote customer meter reading entry • 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, 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

10. Outage/IVR: Architecture

11. Outage/IVR: UML model for outage notification

12. Outage/IVR: CIM-based XML schema

13. Outage/IVR: CIM-based XML schema

14. CIM for Managing Load Measurements • Challenge: • Create one data model for managing configuration of assets • State, Operating Area, Substation, Equipment, Measurement, Measurement ID • Combine historical substation measurement data from several older applications into one PI server • Integrate source systems with this new SCHOOL (PI) server • EMS PI Servers • MVStar – Interval meter readings from Itron MV/90 • Handheld Terminals for manual load readings • CIM Solution • Adopted the CIM network model structure for the configuration database • Used CIM for all messaging between applications

15. SCHOOL: CIM-Based 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.

16. SCHOOL: Integration Architecture

17. SCHOOL: UML model for measurements

18. SCHOOL: CIM-based XML schema

19. CIM for Managing the Operations Model ABB Network Manager CIM Data Engineering Toolkit • Implemented into full production – April 2007 • Product is based on the CIM • Not a translation from CIM to a proprietary data engineering schema • Graphic editor based on ESRI ArcGIS platform • 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 EMS model data • Imports and exports CIM XML for model exchange

20. EMS: CIM data entry paths Tool accepts CIM XML as import Graphic courtesy of ABB

21. Ranger CIM tool example Graphic courtesy of ABB

22. Ranger CIM measurement editor Graphic courtesy of ABB

23. 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)

24. 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

25. 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

26. 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.

27. 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

28. CIM Scorecard

29. CIM Scorecard Cont’d

30. 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

31. Integration Bus = TIBCO + CIM A Version of a Future Vision ABB NM IS500 Web Client OSIsoft RtPortal Web Client PTI Model-on-Demand Web Client T&D MeasurementModel(Analysis Framework) T&D Operating Model (Ranger EMS) T&D Planning Model (PSS/E, MODweb) SCHOOL (PI) Config (CIM) ESRI GIS ABB NM EMS D/E(CIM) SAP ABB CADOPS CIS MV-90 Synchronize these data repositories across core applications (ABB EMS, SAP, ESRI GIS, and OSIsoft) to create a virtual Asset Register

32. Questions? Randy.Rhodes@PacifiCorp.com