CIM Implementation at PacifiCorp: Integration Strategy and Case Studies

1. CIM Implementation at PacifiCorp Virginia Pai and Janet Dietz June 2007

2. Agenda • What is the CIM? • Company Background • PacifiCorp’s CIM “Scorecard” • Four Case Studies • Other Examples • Lessons Learned

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

4. A view of the core CIM model

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

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

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 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 • PacifiCorp’s data warehouse is based on the CIM • EMS/SCADA system (Ranger) uses a CIM-based data maintenance tool

8. 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) Key Facts about PacifiCorp

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

10. CIM Scorecard – Examples of CIM use

11. CIM Scorecard Cont’d

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

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

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

15. Outage/IVR Architecture All interfaces are based on the CIM

16. OUTAGE/IVR: UML model for outage notification

17. Outage example: CIM-based XML schema

18. Outage example: CIM-based XML schema

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

20. SCHOOL: UML model for measurement data

21. SCHOOL Example: CIM-based XML schema

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

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

24. Ranger CIM data entry paths (ABB) Tool accepts CIM XML as import Graphic courtesy of ABB

25. Ranger CIM tool example Graphic courtesy of ABB

26. Ranger CIM measurement editor Graphic courtesy of ABB

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

28. Transmission Billing interface to SAP

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

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

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

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

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

34. More information at www.cimuser.org Questions? Virginia.Pai@PacifiCorp.com Janet.Dietz@PacifiCorp.com