Semantic Modeling atSemantic Modeling atSempra Utilities:
Creating a Common Information Foundationg
CIMug October 2010October 2010
Angela White-Parker, IT Project Lead
© 2005 San Diego Gas and Electric Company and Southern California Gas Company. All copyright and trademark rights reserved
Sempra Energy Utilities
Southern California Gas Company - 6,600 Employees
• 5 6 million natural gas meters5.6 million natural gas meters• 23,000 square miles, from San Luis Obispo to the Mexican border and 535 cities.
• USA’s largest natural gas distribution utility
• Serving over 20 million consumers in 20,000 square mile service territory
California
g , q y
San Diego Gas & Electric - 4,500 Employees
• 1.4 million electric meters & 800,000 natural gas meters
Southern CaliforniaGas Company
, g• 4,100 square miles, covering two counties and 25 cities.
• Serving 3.4 million consumers in San Diego region
San Diego Gas & Electric
Combined Utilities
• Regulated by the California Public Utilities Commission
2
Key Business Efforts
SDG&E Smart Metering program • Meter installations began Q4 2008
• Mass deployment nearing completion
SCG AMI program SCG AMI program
• Approval granted, will touch 5M meters
Sunrise Power link 500 kV
OpEx 20/20 Initiative
• Field Force M&I and Construction work• OMS/DMS/GIS CBM A t M t• OMS/DMS/GIS, CBM, Asset Management
SmartGrid Initiatives
• Gridcomm, HAN, Regulatory planning responses, …Gridcomm, HAN, Regulatory planning responses, …
3
Enterprise Information Management Key Business Driver
Requirement to Share Information• Creating a shared structure and terminology involves an upfront investment.Creating a shared structure and terminology involves an upfront investment.
• Simplify integration, increase interoperability and most importantly expose the information the business manages.
ProvisioningBillingCRM1 CRM2
ProvisioningBillingCRM1 CRM2Provision
-ingBillingCRM1 CRM2
Common Data Model
P t
Inventory TTCall
Center
DataW/house Inventory TT Call
CenterData
W/house Inventory TT CallCenter
C t F tPast Current FutureNo one can figure outWho is talking to whom?
Great! You are using SOA but,Can we reuse this investment?
We know what investments we havemade in automating the business andwe know what we can reuse to buildfuture applications cheaper
4
future applications cheaper.
4
Enterprise Architecture Group has Identified EIM as a key going forward domainforward domain
A
Data Integ
Data M
anag
Analytics and PM
anageme
Data Acqu
Informat
Deliver
Enterprise C
Managemgration
gement
erformance
ent (BI)
isition
ionand D
ata Go
ry and Implem
e
Content
ment
Information Modeling
Data Quality
Metadata Management
Master Data Management
Data Standards, Guidelines, Methodology
overnance
entation
Database ManagementThe Information Management team is a key enabler of this commitment and provides leadership in the strategy and
5
provides leadership in the strategy and adoption of these capabilities for major projects and across the Enterprise.
Information Management Concentrations…to date
Data Integration: Domain for the alignment of data E
g
Data
Data M
Analytics a
Mana
Data
Info D
interactions among various integration scenarios such as web services, EDIX, ETL. Links to business process information exchanges.(internal and external)
Enterprise C
oIntegration
Managem
ent
and Perform
angem
ent (BI)
Acquisition
ormation and
Delivery and
ontent Managnce
M d M
Data Standards, Guidelines, Methodology
Data G
overn
Implem
entatio
Information Modeling: Semantically reconcile and model information exchanges, integrations and
ti f th E t i D tem
ent
Information Modeling
Data Quality
Metadata Management
Master Data Management
ance
on aggregations for the Enterprise. Document transformations, link to an enterprise model, create enterprise models to support different consumers from transactional to BI.
6
Database Management
Semantic Modeling Information Efforts: Background
Vision:Provide a common view of enterprise dataUnderstood by business as well as technical usersEnable a common vocabularyEnable a common vocabulary
Realities:Challenging to understand … needs to be “summarized”
Need business involvementNeed diverse IT involvementNeed diverse IT involvementThe results must be easily understood
7
Project Goals & Objectives
Goals:
Create broad communication of Information Assets (Awareness)
Facilitate discussions of what is being captured for validation (i.e. in-use and planned) (Understanding)use and planned) (Understanding)
Support different “views” of Sempra Information Model. (Management)
Objectives:
Deliver a consistent enterprise approach for modeling & metadata
Develop a baseline integrated EIM solutionDevelop a baseline integrated EIM solution
Enable the ability to exchange data in a consistent manner
Leverage external as well as internal standardsg
8
Why is this important?
Enables ownership, responsibility and accountability for the improvement
Why is this important?
of data quality and information accuracy and consistency
Establishes and promotes a single version of truth for data over time.
Reduces the number and effort of integrations over time
Enables the control of unnecessary data duplication and proliferationy p p
Improves data quality, consistency, availability, and accessibility over time.
Maximizes the return on investment in SOA technologiesMaximizes the return on investment in SOA technologies
Needed for Smart Grid deployment objectives (industry-accepted inventory
of terms and definitions)
9
Influencing factors in Information Standards
Industry standards, best practices, and frameworks were reviewed to evaluate their value and applicability.
Results:• Evaluate and reference relevant industry
standards or open models:– IEC TC57 CIM Coordination
WG19
OpenApplication
Group
TC57WG9
DistributionW3C
UCA : User groups
MultiSpeak(NRECA)
MultiSpeak(NRECA)IEC TC57 CIM
– NRECA MultiSpeak– OGC GML– PODS
O
WG14DMS
WG19
WGs 10Substations
WG7ControlCenters
Feeders
EPRI
CIM/61850 WG17
WG18
(NRECA)(NRECA)
– Open ADE (automated data exchange)
• Adopt Model-Driven principles and approach for information modeling, management and services. Look for references in MDA and SOA standards
OLEProcessControl
WG13EMS
EPRIUCA2ProjectEPRI
CCAPIProject
ebXMLObjectMgmt.
WG16CIM
SOA standards.• Adopt semantic data modeling approach for
enterprise information model development.• Adopt a SOA reference model for data and
i f ti hit t d t
(OPC)Mgmt.Group OASIS
information architecture and management.
10
Model Development Steps and Phase Deliverablesp p
Requirements Design Construct/Build
Reference Base Model ( )
Reference Base Context(Native Model)
Work StreamNative
Implementation Model ( )
NativeXML Schema
(XSD)Reference
ModelRICEFRICEF
“I”
RICEF“I”
Sempra
Mapping
SpecificationsIndustry & Sempra
InformationModel(SIM)
InformationArchitects
Implementation Model
Semantic Base Context
XML Schema (XSD)
Industry & Sempra
Standard Models
(i.e. IEC-CIM)
ServiceDesign Team
Service Design ContractService
Identification
ServiceIdentificationRefinement
12
12
Refinement
Information Management is a team effort…
Enterprise focused….Information Architects• Facilitate cross-domain discussions and groups• Facilitate cross domain discussions and groups
• Maintains Enterprise Views
• Incorporates industry standards
• Maintains data ownership roster
Smart Meter OpEx
• Maintains data ownership roster
• Maintains master data and metadata strategy
• Key EIM enablerOther
(Dynamic Pricing;VMS2)
Gas AMI
Business Domain Focused…Application Data Architects• Assists in developing Enterprise Model for domain
• Can speak on behalf of Data Owner of subject area
• Project(s) data architect
Managing how key information is exchanged regardless of the IT ApplicationApplication.
Smart Meter OpEx
Other (Dynamic
Pricing;VMS2)
Gas AMI
What is our approach?
Subject areas are defined as: A related group of data
“summarized” from the detailed Sempra Information
Sempra Information Model (SIM)
summarized from the detailed Sempra Information
Model (SIM). Development of subject areas are needed
in order to quickly understand and manage the SIM.
What does the SIM contain?
Example Subject Area
What does the SIM contain?
Defined as data passed around the Enterprise.
Industry Standard Utility Modeled data.
What is the value of the SIM and Subject Areas?
Use common data exchanges in SOA payloads to
reduce software development costs. Consumer A li ti Provider
RICEreduce software development costs.
Quickly assess data/information scope of projects in
order to facilitate reuse opportunities.
Application
Consumer Application
Consumer Application
ProviderApplication
ProviderApplication
F_I Requiremen
ts
EMF
15
Subject Area Levels
Level 0 - These are the Enterprise Subject AreasLevel 0 These are the Enterprise Subject AreasUseful Overview for Management and Business UsersStarting point to understand the contents of each Subject Area
Level 1- This next level of detail is one specific Subject Area –Work. Represents main related subject areas and Entity
Groups. This level is useful for deciding if you need the semantic models in the next level to design new applications and interfaces
Level 2 - Here you can see the Semantic Model for the Subject area as well as the Metadata Entity Definitions Metadata Entity Definitions
There may be additional levels of detail below that can be displayed, for each attribute
Metadata Entity Definitions
16
Subject Area Management / Governance
Enhance and maintain the subject area models and ensure that it is easily j yaccessible by those that need the information.
Ensure that we are treating information as a shared business asset
Collaborate with the following groups to ensure the validity and integrity of its contents:
• Data Owners and Stewards
• IT Data Architects
• Data Warehouse
• Business Process Owners
• Others?
20
• Others?
Have We Arrived?
No, but our Vision is much clearer…Our roadmap:
S t D t G i iti tiSupport Data Governance initiative
Acquire Metadata tool to extend subject area portal
Develop Master data management for subject areasDevelop Master data management for subject areas
Assess emerging information ‘standards’ affecting Smart Grid objectives
Enterprise Information Management Models evolves incrementally and iteratively. It’s a journey, rather than a destination.y j y
21
Top Related