Randy Rhodes
EMS User Group Conference
September 25, 2007
CIM as an Enterprise Tool at PacifiCorp
© 2
006
PA
CIF
ICO
RP
|
PA
GE
2
Agenda
– Company Background– Case Studies
Close to the Control Center Elsewhere in the Enterprise
– PacifiCorp’s CIM “Scorecard”– Lessons Learned– Future Plans
© 2
006
PA
CIF
ICO
RP
|
PA
GE
3
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
• 69 generating plants across West; net capability of 9,140 MW
– Owned by Mid-American Energy Holdings Company (MEHC)
© 2
006
PA
CIF
ICO
RP
|
PA
GE
4
PacifiCorp Service Area and Plants
CA
NV
AZ
UT
WY
IDOR
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
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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
Step 1: What data flow isneeded?
Reqirements Specs, withUse Cases,
Integration Scenarios,and/or Event Sequence
Diagrams
Step 2: What is in eachmessage?
Step 3: Re-use existingmessages where
possible, extend CIMwhere not
Identified CIMExtensions: Classes Attributes Relations
Begin Here For EachBusiness Process
Curre
nt IE
C TC
57CI
M (C
omm
onIn
form
atio
n M
odel
)
Paci
fiCor
pIn
form
atio
n M
odel
(CIM
Bas
ed)
Step 4: Define New OrCustomize Pre-Defined
Message Types
New MessageTypes Specified
in XML
Step 6: SupportImplementation
Team
Information ExchangeModeling Complete
Step 5: Map MessageField Names
TransformationMap
Pre-definedMessage Types: Internal IEC OAG
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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
© 2
006
PA
CIF
ICO
RP
|
PA
GE
10
Outage/IVR: Architecture
IVR Environment
Customers
CADOPS Environment
OCHIP EnvironmentMainfame
GTX Info
PhoneCalls (Outage, Check Acct Balance,Send Meter Read)
Corporate Environment
CSSDatabase
IVR System
CADOPS PDX
CADOPSSLC
CADOPS WYO
EAI Environment
EAI Servers
Outage Status Outage StatusOutage Status
DMS Database
PCC Call Center
Outage Info
Acct Balance,Outage Status
Dispatch
Web Environment
Web Server
Outage Info
Outage Info Via Trouble Viewer
WebPage
TFCC
PCC Call Center
Excess Outage calls go to vendor during a major storm
Outage Info
DMZ Environment
© 2
006
PA
CIF
ICO
RP
|
PA
GE
11
Outage/IVR: UML model for outage notification
OutageStep
OutageRecord
+OutageSteps
+OutageRecord1
1..n
1
1..n
ErpPerson(f rom ERP_Support)
Document(f rom DocumentInheritance)
0..n
0..n
+fromDocuments
0..n
+toDocuments0..n
+ErpPersons
+Documents0..n
0..n
0..n
0..n
CustomerAccount(f rom Consumers)
CustomerAgreement(f rom Consumers)
1
0..n
+CustomerAccount1
+CustomerAgreements0..n
OutageNotification(f rom TroubleTickets)
TroubleTicket(f rom TroubleTickets)
ServiceLocation
(from Locatio...0..11..n
+CustomerAreement
0..1
+ServiceLocations
1..n
© 2
006
PA
CIF
ICO
RP
|
PA
GE
12
Outage/IVR: CIM-based XML schema
© 2
006
PA
CIF
ICO
RP
|
PA
GE
13
Outage/IVR: CIM-based XML schema
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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
© 2
006
PA
CIF
ICO
RP
|
PA
GE
15
Control Center
Ranger Historian PDX
Ranger Historian SLC
SCHOOL PI Server
Hand Held Terminals
GridSense LineTrackers
Corporate Environment
Reports
<<RDAS>>PCC
Primary Ranger
AppServer
<<RDAS>>WCC
<<RDAS>>SCC
DMZRanger Corporate PI Servers
MV-STAR
Ranger Historian SLC
Ranger Historian PDX
`
PlanningTechnologies
`
AreaPlanning
`
Field Engineering
`
TransmissionPlanning
`
Regulation
`
GLOMESMaster Station
`
PI Manual Logger Workstations
SCHOOL Configuration
UtilityModel Config (Oracle
CIM)
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 measurementsused in T&D planning at
PacifiCorp.
© 2
006
PA
CIF
ICO
RP
|
PA
GE
16
SCHOOL: Integration Architecture
School Configuration DB and Audit Log DB
Tibco
SCC EMS PI
Web ApplicationServer
PI B-tree DB
TIBCO High Availability ApplicationServer in PDX
TIBCO Distater Recovery Application Server in SLC
School Config
JDBC
School UI via the Web
Web Frontend to access School Acmin
MVStar
Oracle DB
PCC EMS PI
PI B-tree DB
School PI
PI B-tree DB
Tibco Bus
© 2
006
PA
CIF
ICO
RP
|
PA
GE
17
SCHOOL: UML model for measurements
Equipment(f rom Core)
EquipmentContainer(f rom Core)
+Contains_Equipments
+MemberOf_EquipmentContainer
0..1
0..n
0..1
0..n
Substation(f rom Core)
PSRType(f rom Core)
ConductingEquipment(f rom Core)
PowerSystemResource(f rom Core)
0..n
0..1
+PowerSystemResource 0..n+PSRType
0..1
PowerTransformer(f rom Wires)
MeasurementType(f rom Meas)
MeasurementValueQuality(f rom Meas)
MeasurementValue(f rom Meas)
1
1
+MeasurementValueQuality1
1
MeasurementValueSource(f rom Meas)
+MeasurementValueSource1
0..n
1
0..n
Compensator(f rom Wires)
ACLineSegment(f rom Wires)
Line(f rom Wires)
0..1
0..n
+MemberOf_Line
0..1
+Contains_ACLineSegments0..n
RegulatingCondEq(f rom Wires)
Measurement(f rom Meas)
1
0..n
+MemberOf_PSR1
+Contains_Measurements
0..n0..n
1
+Measurements
0..n
+MeasurementType
1
AnalogValue(f rom Meas)
Analog(f rom Meas)
+Contain_MeasurementValues
+MemberOf_Measurement1
1..*
1
1..*
© 2
006
PA
CIF
ICO
RP
|
PA
GE
18
SCHOOL: CIM-based XML schema
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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
© 2
006
PA
CIF
ICO
RP
|
PA
GE
20
EMS: CIM data entry paths
Graphic courtesy of ABB
Tool accepts CIM XML as import
© 2
006
PA
CIF
ICO
RP
|
PA
GE
21
Ranger CIM tool example
Graphic courtesy of ABB
© 2
006
PA
CIF
ICO
RP
|
PA
GE
22
Ranger CIM measurement editor
Graphic courtesy of ABB
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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)
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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.
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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
© 2
006
PA
CIF
ICO
RP
|
PA
GE
28
CIM Scorecard
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%
Transmission CAPSO PlannedOutage.Change PlannedOutageNotification 50%
TWBS TransmissionData, STLossData, LTLossData, Scheduling.LoadData,ConsumptionData, InvoiceData
Settlement and MarketClearing 70%
EMSScada WeatherData MeasurementList 100%
© 2
006
PA
CIF
ICO
RP
|
PA
GE
29
CIM Scorecard Cont’d
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
WorkWorkHistory
Commercial & Trading
K2 SubstationEquipment.MeasurementFwdPrcForecast, Trades, VolatilityForecast
EnergyPriceCurve, EnergyTransactionVolatilityForecast(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%
Corporate Giving Campaign
EmployeeDetails, ContributionPayrollDetails Employee (erpPerson) 70%
SOX ChangeAuditReport ChangeAudit (Not in CIM) 90%
© 2
006
PA
CIF
ICO
RP
|
PA
GE
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
© 2
006
PA
CIF
ICO
RP
|
PA
GE
31
A Version of a Future Vision
T&D Planning Model
(PSS/E, MODweb)
ABB NMEMS D/E
(CIM)
MV-90ESRI GIS
SCHOOL (PI) Config
(CIM)
SAP
Integration Bus = TIBCO + CIM
T&D MeasurementModel
(Analysis Framework)
T&D Operating Model
(Ranger EMS)
OSIsoft RtPortal Web Client
PTI Model-on-DemandWeb Client
ABB NM IS500 Web Client
Synchronize these data repositories across core applications (ABB EMS, SAP, ESRI GIS, and OSIsoft) to create a virtual Asset Register
CISABB CADOPS