Open Smart Grid Reference Model TC
Mar 31, 2015
Open Smart Grid Reference Model TC
Widespread Industry Challenges
“Utilities need to prepare for an onslaught of data – as other industries have done. The challenge of upgrading IT systems accordingly is one of the reasons the Smart Grid is in its infancy” - Electric Power Research Institute
“Moving beyond the initial development stages is proving to be a challenge for utilities. There is an increased emphasis on architecture in the planning process as utilities transform their existing information systems and business operations as they implement the Smart Grid” –NIST Smart Grid Advisory Committee
“AMI, CIS and OMS integration ease are issues when it comes to satisfaction ratings with current MDM solutions” – Sierra Energy Group, Preparing for the Meter Data Deluge
Copyright 2011BRIDGE Energy Group, Inc.
Copyright 2010 BRIDGE Energy Group, Inc. 3
Open SGRM• What is it?
– A Smart Grid Reference Model and Blueprint for Utilities to execute Smart Grid initiatives
• What will it provide?– Blueprint:
• Approach to Assessment of Current State• Definition of Understanding of Business Needs• Define Challenges
– Smart Grid Reference Model:• Identify Future State through a Smart Grid Reference Model• Description of Services in the model
• How can it be used?– Utilities can leverage the blueprint and reference model to develop their
roadmap– Vendors can leverage the Reference Model to develop open and
interoperable products & Solutions
Copyright 2010 BRIDGE Energy Group, Inc. 4
Open SGRM – How does it relate to existing work• Leverages all previous work
– E.g. Conceptual Architecture, P2030– GWAC Stack etc.
• Leverages any and all standards– PAP standards– Interoperability– CIM etc.
• Leverages IT standards– SOA– ESB etc.
The Integration Challenges
1. Accidental Architecture
2. Point to Point
3. Complex
4. Proprietary Interfaces
5. Ripple Effect
6. MDM Transaction Volume
7. Need for Real-time Data
8. End to End Integration
9. Security Issues
10. Integrate Distributed Generation
11. Integrate PHEVs
12. Settlement & Billing
Tony Giroti 5
Adele Mapping System
Banner CIS(Customer Information System)
EMS - ESCA (Energy
Management System)
Lodestar Billing
Expert - TASC
Rates Data Mart
CMS(ConstructionManagement
System)
STS (Services Tracking System)
Compatible Units
WMS(Work
Management System)
UDS(Utilty Design
System)
OMS - ABB (Outage
Management System)
Energy Accounting Sys
& Gas
Managment Sys
ITRON Meter
Reading
EnterpriseSystem
SPPC System
NPC System
Legend
ECAS
MapGuide(iConnect)
Pension Calc. Sys.
Paybase Check Print
DBM ARCS
Lodestar Client/ Server
Deposit/Refund Checks
AMS Meter Inventory
Bill Print (Opencsf)
Mobility
CheckFree
Landbase Processing
Microsoft Exchange/
Outlook
Capital Budget
Sys.
Description Now (Job
Desciption)
Career Architect
Auto Affirmative
Action Planning
Fleet Anywhere
CascadePI
(Substation Reads)
Mobile Dispatch
Paris
Enterprise Systems Diagram
Open Systems
Mainframe
· Reno (Mail pymts (SP)· EDS (SP)· Bill Matrix (NP)· Ready Pay (NP)· FEDS (SP)· STORES (SP)· Collection Agency (NP)· LIHEA Pymts (NP)
Remittances(Docutran)
· CIS INQ· SCIS INQ· Call-in
Priviledge· Equifax
Load Mgmt
ERP Peoplesoft
Human Capital Managment
FinancialsSupply Chain
OMS (Outage
Management System)
IVR / VRU
IVR / VRU
Loadstar
CQenceMail
Processor
MV90
ORCOM CIS
TMWA CIS
ERP
Primavera
HenwoodBook-
RunnerRisk / Credit
Oracle Historical
Data Tables
PowerPlant(Generation Fixed Asset Accounting)
TEA (Time Entry
Application)
eTrak
ERP
INDUS Passport· Purchasing· Inventory· Work Mngmnt· Tag Out
Oracle Spatial
ShareholderSystem
OutSourced
HR Logix
COURTESY: A Utility. Name Intentionally Withheld
1. The Accidental Architecture 3. Ripple Effect2. P2P Interfaces
1. REVIEW
2. ASSESS
3. STRATEGY & ROADMAP
4a. DESIGN– Open SG Reference Architecture
4b. DESIGN– Integration Architecture
5. COE: Technical Design Reviews, Workshops, Implementation, End to End Testing
8/19/2010
Copyright 2010 BRIDGE Energy Group, Inc. 6
How to Measure the Challenges
• The Integration Complexity Challenge– With P2P architecture, the
integration complexity will increase over time.
– Integration complexity for every organization is different and provides an indication of (a) the scope (investment required) and (b) if a strategic approach to integration is needed.
– Utilities need a tool to determine if a strategic integration architecture is needed.
• BRIDGE Index
• Third party tools– CMU– SEI
• GWAC Interoperability Context-Setting Framework
Copyright 2010 BRIDGE Energy Group, Inc. 7
Integration Issues mapped to DOE and NIST’s GWAC Stack
Integration Challenges across GridWise Interoperability Framework Categories
1 Organizational Challenge x x x x x2 Lack of IT Maturity x x x x x x3 Evolving Technical Standards x x x4 New Models - PHEV & Dist Gen. x x x5 Centralized vs Decentralized x x x x x x x x x x x x6 IT, Service, Data Governance x x x x x x7 Ripple Effect x x x x x x8 Integration Complexity x x x x x x x x x x x x x9 Transformation Challenge x x x x10 Lack of SOA Experience x x x x x x x x x x11 Reporting & DW Issues x x x x12 Data Volume x x x x x13 Performance & Throughput x x x x14 Transaction Processing Issues x x x x x x x15 Common Security Model x x x x x x x16 Point to Point Accidental Arch. x x x x x x x x x x x x x x x
Custom Code Issues x x x x x x x x x x xNo Reusability x x x x x x x x x x x Different Payloads x x xDifferent Protocols x x xDifferent Logging x xUnpredictable QoS x xNo Runtime for scalability x x xNo Common Vocabulary x xNo Distributed Transaction x x x x x xUnreliable Security x x x x x xNo Centralization x x x x x x x x x x x x xNo Standard way of Integrating x x x x x x x
Cross Cutting IssuesTechnical Informational Organizational
Open Smart Grid Reference Architecture
- Service Oriented Architecture- Real Time Architecture- Loosely Coupled Architecture- Complex Event Processing- Centralized versus Federated
Model- Enterprise Data Warehouse
Tony Giroti 8
Service Oriented Architecture (SOA)Service Oriented Architecture (SOA)
Application ArchitectureApplication Architecture
Business ArchitectureBusiness Architecture
Service / Process OrchestrationService / Process Orchestration
SOA Tool or CapabilitySOA Tool or Capability
Data ArchitectureData Architecture
Real-Time Integration ArchitectureReal-Time Integration Architecture
ESB, Transport & MessagingESB, Transport & Messaging
PortalPortal
Real-Time Integration ArchitectureReal-Time Integration Architecture
RegistryRegistry CEPCEP RoutingRouting
Event Driven ArchitectureEvent Driven Architecture
Loosely Coupled Architecture
Loosely Coupled Architecture
Technical ServicesTechnical Services
Canonical Data Model
Canonical Data Model
Workflow / Human TasksWorkflow /
Human TasksBusiness ServicesBusiness Services Enterprise
ServicesEnterprise Services
Semantic Data Model
Semantic Data Model
Master Data ManagementMaster Data
Management Meta DataMeta Data
Application Integ Modules
Application Integ Modules
Cross Cutting Modules
Cross Cutting Modules
B2B Integra-tion Modules
B2B Integra-tion Modules
Real-Time ArchitectureReal-Time
ArchitectureTransaction
Processing -OLTPTransaction
Processing -OLTP
Development SDKDevelopment SDK
Common Services
Common Services
Customer / HAN Modules
Customer / HAN Modules
Transformation
Transformation
DatabaseDatabase
Infrastructure ArchitectureInfrastructure ArchitectureHardware, OS, VirtualizationHardware, OS, Virtualization
Compl I ance
Archi tecture
Compl I ance
Archi tecture
Secure i ty
Archi tecture
Secure i ty
Archi tecture
Command & ControlCommand & Control OA&MOA&MSG & DR Applications
SG & DR Applications
Admin InterfaceAdmin Interface
Data Warehouse Infrastructure
Data Warehouse Infrastructure
Data Warehouse Data Warehouse
Extraction Transformation &
Load
Extraction Transformation &
Load
Domain Specific Data Marts
Domain Specific Data Marts
Reporting ArchitectureReporting
Architecture
Reporting, Analytics & BI
Reporting, Analytics & BI
Star/Snowflake Data WarehouseStar/Snowflake
Data Warehouse
Source DBsSource DBs
ETL ToolETL Tool
ETL ArchitectureETL Architecture
Reporting ToolReporting Tool
Data MartData Mart
Data MartData Mart
Remote Connect /
Disconnect
Remote Connect /
Disconnect
Outage DetectionOutage
DetectionSelf Healing
GridSelf Healing
GridAdvance
BillingAdvance
BillingOthersOthers
Example:CIM to Multi Speak
Smart Grid
Applications
1. REVIEW
2. ASSESS
3. STRATEGY & ROADMAP
4a. DESIGN– Open SG Reference Architecture
4b. DESIGN– Integration Architecture
5. COE: Technical Design Reviews, Workshops, Implementation, End to End Testing8/19/2010
Copyright 2010 BRIDGE Energy Group, Inc. 9
The Case for OpenSGRMProblem• Traditionally, general models or
"on-ramps" for the gradual implementation of systems are offered by large analyst or service integrator consultancies.
• Many existing and new market participants may instead elect a self-designed, "DIY" approach, which may be made significantly easier by freely-available, general exemplar service models and design principles consistent with the higher-level SGIP architectures.
Solution• The OpenSGRM TC will draw
together a common set of services and interactions in the electric power supply information chain, based on industry examples and available industry-wide open models, and publish an open Smart Grid Reference Model to fulfill that need, by providing guidance to implementers in various information chain roles on how to:– Quantify the technical complexity,– Identify the business need– Encapsulate and widely reuse
commonly-recurring data services and functions.
Copyright 2010 BRIDGE Energy Group, Inc. 10
Outputs
• Means to understand the complexity of the IT ecosystem and Smart Grid maturity model
• Understanding of what the business needs are
• Mechanism or tool set to measure complexity of the ecosystem
• Development of a reference model for a utility– The components needed to achieve that
objective
• Granular definition of components down to a service level– Common services
How can it be used?• Utilities can leverage
the blueprint and reference model to develop their roadmap
• Vendors can leverage the Reference Model to develop open and interoperable products & Solutions
Copyright 2010 BRIDGE Energy Group, Inc. 11
Scope of the OpenSGRM TC
• The committee will develop an open, freely-usable Open Smart Grid Reference Model (RM), and supporting information, for information transactions by parties in the information chain for energy generation, control, transmission, distribution, and consumption.
Copyright 2010 BRIDGE Energy Group, Inc. 12
TC Deliverables
• 12-18 months from the TC’s first meetingAn Open SmartGrid Reference Model base document, as its first output, which will describe an archetypal message and data structure that encompasses relevant information systems and transactions in electrical energy markets. The committee intends that this base document will become an OASIS Standard.
• 6 months after the completion of deliverable #1A profile and/or reference architecture for web services implementation of the reference model.
Copyright 2010 BRIDGE Energy Group, Inc. 13
Time Commitment
• Date & time of first meetingThe first meeting of the TC will be held approximately 3 weeks after the official call for participation during the first week of November.
• Ongoing meeting scheduleTo be decided by the committee. Biweekly or monthly teleconferences and the occasional (semi-annual) face to face work session may be appropriate.