Скачать презентацию CIM Implementation at Pacifi Corp Virginia Pai and Скачать презентацию CIM Implementation at Pacifi Corp Virginia Pai and

66e9a3f67ebb2bca185ef7589a18d0d3.ppt

  • Количество слайдов: 34

CIM Implementation at Pacifi. Corp Virginia Pai and Janet Dietz June 2007 CIM Implementation at Pacifi. Corp Virginia Pai and Janet Dietz June 2007

Agenda – What is the CIM? – Company Background – Pacifi. Corp’s CIM “Scorecard” Agenda – What is the CIM? – Company Background – Pacifi. Corp’s CIM “Scorecard” – Other Examples – Lessons Learned © 2007 PACIFICORP | PAGE 2 – Four Case Studies

What is the CIM? – Common Information Model sponsored by the International Electrotechnical commission What is the CIM? – Common Information Model sponsored by the International Electrotechnical commission 4 4 4 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 4 Provides a common model behind all messages exchanged among applications Provides definitions for common data classes © 2007 PACIFICORP | PAGE 3 4

© 2007 PACIFICORP | PAGE 4 A view of the core CIM model © 2007 PACIFICORP | PAGE 4 A view of the core CIM model

How can CIM be used in the Utility Enterprise? – The CIM is more 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 4 4 Provides common set of semantics and data representation regardless of source of data Improves data quality and enables data validation 4 4 Provides a common language and format Provides a common set of services for sharing data – The CIM enables application integration 4 Provides the basis for a standards-based integration format © 2007 PACIFICORP | PAGE 5 – The CIM promotes data exchange

– Improves the ability to integrate business processes with Commercial-Off-The-Shelf applications – Provides a – 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 Why have standards-based integration?

CIM is Pacifi. Corp’s Integration Strategy – Pacifi. Corp is successfully using CIM to 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 Having a common vocabulary reduces semantic misinterpretation Reusing messages minimizes integration costs Minimal knowledge of internal application designs required – CIM is here to stay 4 4 CIM is standard design practice Pacifi. Corp vendors are getting used to the idea Pacifi. Corp’s data warehouse is based on the CIM EMS/SCADA system (Ranger) uses a CIM-based data maintenance tool © 2007 PACIFICORP | PAGE 7 4

Key Facts about Pacifi. Corp Headquarters in Portland, Oregon 1. 6 million customers in Key Facts about Pacifi. Corp 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: 4 4 4 Pacific Power – Oregon, Washington and California Rocky Mountain Power – Utah, Wyoming and Idaho Pacifi. Corp Energy – generation and mining • 69 generating plants across West; net capability of 8, 470 MW – Owned by Mid-American Energy Holdings Company (MEHC) © 2007 PACIFICORP | PAGE 8 – – – –

Pacifi. Corp Service Area and Plants WA Pacifi. Corp Service Territory MT Thermal Plants Pacifi. Corp Service Area and Plants WA Pacifi. Corp Service Territory MT Thermal Plants OR Gas-Fueled Thermal Plants ID Wind Projects WY Geothermal Plants NV Hydro Systems CA UT Generation Developments 500 k. V Transmission Lines 345 k. V Transmission Lines 230 k. V Transmission Lines AZ CO © 2007 PACIFICORP | PAGE 9 Coal Mines

CIM Scorecard – Examples of CIM use Application/ Project Message(s) CIM Pct of message CIM Scorecard – Examples of CIM use Application/ Project Message(s) CIM Pct of message that is CIM Power Delivery Substation Measurements Interval. Read, Substation. Equipment. Measurement. List 90% Outage Center Call Handing Trouble. Calls, Trouble. Report. Alerts, Trouble. Report. Details, Trouble. Report. Summary, Customer Info, Customer Balance, Customer Account Balance Outage. Management 80% Retail Access Project 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 System Facility. Point, Joint. Use. Agreement, Joint. Use. Attachment, Joint. Use. Notice, Joint. Notice. Request, Facility. Point Asset. List 70% Transmission Planned Outages Planned. Outage. Change Planned. Outage. Notification 50% Transmission Wholesale Billing System 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 © 2007 PACIFICORP | PAGE 10 Business Units

CIM Scorecard Cont’d Application/ Project Message(s) CIM Pct of message that is CIM Power CIM Scorecard Cont’d Application/ Project Message(s) CIM Pct of message that is CIM Power Supply/ Generation Availability Information System Geo. Thermal. Plant. Generation Measurement. List 60% Hydro Information Website Flow. Display Measurement. List 100% Generation Equipment Performance Work Management Solution. Notification, Performance, Solution. Project, Equipment. Group. Repetitive. Tasks, Inventory. Stocking. Plan, Work. History. Document Work. History 90% CRS Mark. To. Market. Data Mark. To. Market (Not in CIM) 80% California ISO interface EDI 810 Settlement 50% Giving Campaign Employee. Details, Contribution. Payroll. Details Employee (erp. Person) 70% Sarbanes Oxley Audit Change. Audit. Report Change. Audit (Not in CIM) 90% Commercial & Trading Corporate © 2007 PACIFICORP | PAGE 11 Business Units

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

– – – Step 1: define integration scenario according to business process needs Step – – – 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 Pacifi. Corp’s 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 Model-driven integration process

Outage Call and Customer Call Handling 4 4 4 Customer phone number recognition between 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 – Much testing around performance and handling of large load. © 2007 PACIFICORP | PAGE 14 – 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

Outage/IVR Architecture © 2007 PACIFICORP | PAGE 15 All interfaces are based on the Outage/IVR Architecture © 2007 PACIFICORP | PAGE 15 All interfaces are based on the CIM

© 2007 PACIFICORP | PAGE 16 OUTAGE/IVR: UML model for outage notification © 2007 PACIFICORP | PAGE 16 OUTAGE/IVR: UML model for outage notification

© 2007 PACIFICORP | PAGE 17 Outage example: CIM-based XML schema © 2007 PACIFICORP | PAGE 17 Outage example: CIM-based XML schema

© 2007 PACIFICORP | PAGE 18 Outage example: CIM-based XML schema © 2007 PACIFICORP | PAGE 18 Outage example: CIM-based XML schema

SCHOOL (PI) - Substation and Circuit Historian 4 4 4 Ranger EMS PI Servers SCHOOL (PI) - Substation and Circuit Historian 4 4 4 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 © 2007 PACIFICORP | PAGE 19 – 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

© 2007 PACIFICORP | PAGE 20 SCHOOL: UML model for measurement data © 2007 PACIFICORP | PAGE 20 SCHOOL: UML model for measurement data

© 2007 PACIFICORP | PAGE 21 SCHOOL Example: CIM-based XML schema © 2007 PACIFICORP | PAGE 21 SCHOOL Example: CIM-based XML schema

This is the SCHOOL Configuration Utility application, used to maintain the SCHOOL Configuration Database. 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. © 2007 PACIFICORP | PAGE 22 SCHOOL Configuration Utility

Ranger CIM data maintenance tool 4 4 4 4 Based on the CIM, not Ranger CIM data maintenance tool 4 4 4 4 Based on the CIM, not on not a translation from CIM to a proprietary data engineering schema Based on ESRI Arc. GIS technology Arc. SDE – Spatial Database Engine • Oracle application • Multi-user, versioned database server Arc. Catalog – GDB schema maintenance • Schema generation based on UML created in Visio • Schema maintenance of attributes, classes, relationships Arc. Map – 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 © 2007 PACIFICORP | PAGE 23 – CIM Data Engineering Toolkit

Ranger CIM data entry paths (ABB) Graphic courtesy of ABB © 2007 PACIFICORP | Ranger CIM data entry paths (ABB) Graphic courtesy of ABB © 2007 PACIFICORP | PAGE 24 Tool accepts CIM XML as import

Graphic courtesy of ABB © 2007 PACIFICORP | PAGE 25 Ranger CIM tool example Graphic courtesy of ABB © 2007 PACIFICORP | PAGE 25 Ranger CIM tool example

Graphic courtesy of ABB © 2007 PACIFICORP | PAGE 26 Ranger CIM measurement editor Graphic courtesy of ABB © 2007 PACIFICORP | PAGE 26 Ranger CIM measurement editor

Transmission Wholesale Billing System 4 4 4 4 4 OASIS – sends transmission readings Transmission Wholesale Billing System 4 4 4 4 4 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) K 2 – Trading, price curves, plant operations © 2007 PACIFICORP | PAGE 27 – TWBS produces invoices for Pacifi. Corp’s 34 largest wholesale customers (collects over $30 Million of the company’s 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 28 Transmission Billing interface to SAP © 2007 PACIFICORP | PAGE 28 Transmission Billing interface to SAP

Single Person Scheduling 4 4 Used CIM attribute names, but not relationships Processing time Single Person Scheduling 4 4 Used CIM attribute names, but not relationships Processing time lessened Complexity reduced No reusability © 2007 PACIFICORP | PAGE 29 – 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

Enterprise Data Warehouse – CIM is the foundation for warehouse data structures – Areas 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 4 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” © 2007 PACIFICORP | PAGE 30 4

Retail Access – Oregon’s electric restructuring bill (SB 1149) for investor-owned utilities, implemented March Retail Access – Oregon’s electric restructuring bill (SB 1149) 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 – Extended CIM structure to include details of customer billing and energy service supplier © 2007 PACIFICORP | PAGE 31 – XML schema developed used explicit structure names rather than repeating groups with type codes

Other Areas – Trading and Risk Management 4 Extensions were created for trading applications Other Areas – Trading and Risk Management 4 Extensions were created for trading applications using both CIM and Financial Products Markup Language (FPML) 4 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 Change. Audit. Report XSD created to publish changes to operating system and database. © 2007 PACIFICORP | PAGE 32 – SOX

– CIM integration works well, especially for Power Delivery – Project work is reduced – 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 Lessons Learned

More information at www. cimuser. org Questions? Virginia. Pai@Pacifi. Corp. com Janet. Dietz@Pacifi. Corp. More information at www. cimuser. org Questions? Virginia. [email protected] Corp. com Janet. [email protected] Corp. com