Transcript emmos.org
CIM as an Enterprise Tool at PacifiCorp Randy Rhodes EMS User Group Conference September 25, 2007 Agenda – Company Background – Case Studies Close to the Control Center Elsewhere in the Enterprise © 2006 PACIFICORP | PAGE 2 – PacifiCorp’s CIM “Scorecard” – Lessons Learned – Future Plans Key Facts about PacifiCorp – 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 – Owned by Mid-American Energy Holdings Company (MEHC) © 2006 PACIFICORP | PAGE 3 • 69 generating plants across West; net capability of 9,140 MW PacifiCorp Service Area and Plants WA PacifiCorp Service Territory MT Thermal Plants OR Gas-Fueled Thermal Plants ID Wind Projects WY Geothermal Plants Coal Mines Hydro Systems NV CA UT CO 500 kV Transmission Lines 345 kV Transmission Lines 230 kV Transmission Lines AZ © 2006 PACIFICORP | PAGE 4 Generation Developments 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 6 PacifiCorp Uses Model-Driven Integration Begin Here For Each Business Process Step 4: Define New Or Customize Pre-Defined Message Types Step 5: Map Message Field Names Step 6: Support Implementation Team Information Exchange Modeling Complete Identified CIM Extensions: Classes Attributes Relations Pre-defined Message Types: Internal IEC OAG New Message Types Specified in XML Transformation Map © 2006 PACIFICORP | PAGE 7 Step 3: Re-use existing messages where possible, extend CIM where not PacifiCorp Information Model (CIM Based) Step 2: What is in each message? Reqirements Specs, with Use Cases, Integration Scenarios, and/or Event Sequence Diagrams Information Model) Step 1: What data flow is needed? Current IEC TC57 CIM (Common – 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 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) 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 © 2006 PACIFICORP | PAGE 8 – Other Implementation Examples 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 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 © 2006 PACIFICORP | PAGE 9 – Used CIM-based messaging to integrate: Outage/IVR: Architecture CADOPS Environment TFCC Dispatch Outage Info Via Trouble Viewer WebPage PCC Call Center CADOPS SLC Outage Status CADOPS WYO CADOPS PDX Outage Status DMZ Environment Outage Status Excess Outage calls go to vendor during a major storm Web Environment Outage Info EAI Environment Customers Outage Info IVR Environment IVR System Web Server EAI Servers DMS Database Acct Balance, Outage Status GTX Info CSS Database PCC Call Center Mainfame OCHIP Environment Corporate Environment © 2006 PACIFICORP | PAGE 10 Phone Calls (Outage, Check Acct Balance, Send Meter Read) Outage Info Outage/IVR: UML model for outage notification ErpPerson (f rom ERP_Support) OutageRecord 0..n +OutageRecord 1 +ErpPersons 0..n +Documents Document (f rom DocumentInheritance)0..n +toDocuments TroubleTicket (f rom TroubleTickets) 0..n 1..n +OutageSteps OutageStep +fromDocuments CustomerAccount OutageNotification (f rom TroubleTickets) (f rom Consumers) ServiceLocation 1..n 0..1 +CustomerAgreements 0..n CustomerAgreement (f rom Consumers) (from Locatio... +ServiceLocations +CustomerAreement © 2006 PACIFICORP | PAGE 11 1 +CustomerAccount © 2006 PACIFICORP | PAGE 12 Outage/IVR: CIM-based XML schema © 2006 PACIFICORP | PAGE 13 Outage/IVR: CIM-based XML schema 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 – CIM Solution Adopted the CIM network model structure for the configuration database Used CIM for all messaging between applications © 2006 PACIFICORP | PAGE 14 • EMS PI Servers • MVStar – Interval meter readings from Itron MV/90 • Handheld Terminals for manual load readings SCHOOL: CIM-Based Configuration Utility <<RDAS>> SCC <<RDAS>> WCC Control Center <<RDAS>> PCC Primary Ranger AppServer Ranger Historian Ranger Historian SLC PDX DMZ Corporate Environment Ranger Corporate PI Servers Hand Held Terminals Ranger Historian PDX Ranger Historian SLC ` PI Manual Logger Workstations ` SCHOOL Configuration Utility GLOMES Master Station Model Config (Oracle CIM) SCHOOL PI Server Reports ` Planning Technologies ` ` Area Planning ` ` Field Engineering Transmission Planning Regulation © 2006 PACIFICORP | PAGE 15 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. GridSense LineTrackers MV-STAR SCHOOL: Integration Architecture School PI SCC EMS PI PCC EMS PI School UI via the Web PI B-tree DB PI B-tree DB PI B-tree DB MVStar Oracle DB School Configuration DB and Audit Log DB Web Application Server School Config Web Frontend to access School Acmin Tibco JDBC TIBCO Distater Recovery Application Server in SLC TIBCO High Availability Application Server in PDX © 2006 PACIFICORP | PAGE 16 Tibco Bus SCHOOL: UML model for measurements RegulatingCondEq Compensator (f rom Wires) (f rom Wires) Measurement Analog (f rom Meas) (f rom Meas) +Measurements 0..n 0..n +Contains_Measurements 1 +MemberOf_Measurement +MeasurementType +MemberOf_PSR 1 PowerSystemResource +PowerSystemResource 1 MeasurementType (f rom Meas) (f rom Core) 0..n +PSRType Equipment (f rom Core) (f rom Core) 0..1PSRType MeasurementValueSource (f rom Meas) (f rom Core) 0..n 1 +MeasurementValueSource +Contains_Equipments 0..1 PowerTransformer Line EquipmentContainer (f rom Wires) (f rom Wires) (f rom Core) +MemberOf_Line +MemberOf_EquipmentContainer 0..1 +Contains_ACLineSegments 0..n Substation ACLineSegment (f rom Wires) (f rom Core) +Contain_MeasurementValues 1..* 0..n MeasurementValue AnalogValue (f rom Meas) (f rom Meas) 1 +MeasurementValueQuality 1 MeasurementValueQuality (f rom Meas) © 2006 PACIFICORP | PAGE 17 ConductingEquipment © 2006 PACIFICORP | PAGE 18 SCHOOL: CIM-based XML schema 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 » 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 © 2006 PACIFICORP | PAGE 19 • ArcMap – main graphical editing client application Tool accepts CIM XML as import Graphic courtesy of ABB © 2006 PACIFICORP | PAGE 20 EMS: CIM data entry paths Graphic courtesy of ABB © 2006 PACIFICORP | PAGE 21 Ranger CIM tool example Graphic courtesy of ABB © 2006 PACIFICORP | PAGE 22 Ranger CIM measurement editor Transmission Wholesale Billing System 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 23 – 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 Single Person Scheduling Processing time lessened Complexity reduced No reusability © 2006 PACIFICORP | PAGE 24 – 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 implemented that made particular use of the CIM include the following: Customer information from CSS Distribution work management from RCMS Customer metering Project financials © 2006 PACIFICORP | PAGE 25 – 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 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 ChangeAuditReport XSD created to publish changes to operating system and database. © 2006 PACIFICORP | PAGE 26 – SOX 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 – XML schema developed used explicit structure names rather than repeating groups with type codes © 2006 PACIFICORP | PAGE 27 – 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 IntervalRead, SubstationEquipment.Measurement MeasurementList 60% OCHIP, IVRLog, IVR/CSS TroubleCalls, TroubleReportAlerts, TroubleReportDetails, TroubleReportSummary, Customer Info, Customer Balance, Customer Account Balance OutageManagement 80% RAP RegisterReadRequest, 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% PADMS FacilityPoint, JointUse.Agreement, JointUse.Attachment, JointUse.Notice, JointNoticeRequest, FacilityPoint AssetList 70% CAPSO PlannedOutage.Change PlannedOutageNotification 50% TWBS TransmissionData, STLossData, LTLossData, Scheduling.LoadData, ConsumptionData, InvoiceData Settlement and MarketClearing 70% EMSScada WeatherData MeasurementList 100% Transmission © 2006 PACIFICORP | PAGE 28 CIM Scorecard Business Units Application/ Project Message(s) CIM % of Total in relation to CIM Power Supply/ Generation AIS GeoThermalPlantGeneration MeasurementList 60% HIWS FlowDisplay MeasurementList EPW SolutionNotification, Performance, SolutionProject, EquipmentGroupRepetitiveTasks, Inventory.StockingPlan, WorkHistoryDocument Work WorkHistory K2 SubstationEquipment.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% CRS MarkToMarketData MarkToMarket (Not in CIM) 80% CAISO EDI810 Settlement 50% Giving Campaign EmployeeDetails, ContributionPayrollDetails Employee (erpPerson) 70% SOX ChangeAuditReport ChangeAudit (Not in CIM) 90% Commercial & Trading Corporate © 2006 PACIFICORP | PAGE 29 CIM Scorecard Cont’d – 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 30 Lessons Learned A Version of a Future Vision ABB NM IS500 Web Client OSIsoft RtPortal Web Client PTI Model-on-Demand Web Client T&D Operating Model (Ranger EMS) T&D Measurement Model (Analysis Framework) T&D Planning Model (PSS/E, MODweb) SCHOOL (PI) Config (CIM) ABB NM EMS D/E (CIM) SAP ESRI GIS 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 © 2006 PACIFICORP | PAGE 31 Integration Bus = TIBCO + CIM Questions? [email protected]