enterprise information management at aep frank wilhoit, information architect 9 march 2011
TRANSCRIPT
Enterprise InformationManagement at AEP
Frank Wilhoit, Information Architect9 March 2011
Agenda
• AEP Overview• Technology Portfolio• EIM Philosophy• Implementation Approaches• Questions?
AEP Statistics
• AEP is an integrated utility with lines of business for Generation, Distribution, and Transmission.
• ~ 38 GW of generation capacity in the United States. • Largest transmission system (~ 39000 miles). • Serves > 5M customers in 11 states: OH, MI, IN, KY, VA,
WV, TN, OK, TX, AR, LA.• ~1.4M smart meters in TX, ~120K in OH, < 20K each in IN
and OK
Technology Portfolio• AMI: Landis+Gyr (TX) and Silver Spring (IN, OH, OK)• MDM: Oracle (ex Lodestar) • CIS: mainframe, homebrew (based on CustomerOne)• OMS: GE PowerOn• DMS: GE ENMAC GENe• Ventyx AssetSuite, Logica STORMS, Itron LD-PRO, etc. ad
infinitum• This slide and the preceding one came to data volume.
Hold That Thought.
ONTOLOGY
INFORMATION
CONTENT BEHAVIOR
REPRESENTATIONSEMANTICS LIFESPANINTERPRETATION
TYPE
PROCESS
EVOLUTION
PERSISTENTNORMALIZED
(~ “DATA”)
IN-FLIGHTDENORMALIZED
ASSOCIATIONCOMPOSITIONAGGREGATION
RESTRICTIONENUMERATION
SPECIALIZATIONGENERALIZATION
LEGEND--------------------
The colors don’t mean anything.
IN-MEMORY
PLATFORMREQUIREMENTS
CIM == Global Content Model• IEC 61968
– Published• Part 9 : metering• Part 3 : outage management• Part 4 : asset management / geospatial
– In-progress• Part 8 : customer
• IEC 62325 : Energy markets
Information is More Than Content• Why is data volume a problem?
– Because we don’t know how to manage it.• Why do we not know how to manage it?
– Because we haven’t modelled the behavior of the information that it represents.
• Behavior == Process• CIM doesn’t have this (yet?)
How Do You Model Process?• Ask people to tell/show you what they do.
– This did not work for us. It probably doesn’t matter why.OR• Follow your information.
– Trace object lifecycles from creation, through enrichment/evolution, to irrelevance.
– These are the processes that actually happen within your systems.
ONTOLOGY
INFORMATION
CONTENT BEHAVIOR
REPRESENTATIONSEMANTICS LIFESPANINTERPRETATION
TYPE
PROCESS
EVOLUTION
PERSISTENTNORMALIZED
(~ “DATA”)
IN-FLIGHTDENORMALIZED
ASSOCIATIONCOMPOSITIONAGGREGATION
RESTRICTIONENUMERATION
SPECIALIZATIONGENERALIZATION
LEGEND--------------------
The colors don’t mean anything.
IN-MEMORY
PLATFORMREQUIREMENTS
The Ontology is the Universal Enabler• Actionable metadata
– Content– Behavior
• Maintain as UML models (like CIM, but including behavior)• Generate all downstream artifacts
– Code (Java, C/C++, C#, whatever)– Database schema– Test cases– Documentation
• We’re not there yet
?