Smart Grid
(Enterprise) Architecture 101
2012/Dec/04
Agenda
• Architecture Overview
• SGAC Conceptual Architecture
• Semantics / Vocabulary
• Maturity Models
• Summary/Resources
Architecture as usually practiced
ARCHITECTURE
OR BUY A VENDOR’S PACKAGE
(Apologies to Mr Adams and my fellow architects)
There is never enough time (or money) to do it right the first time
There is always enough time and money to fix it over and over again
-Anonymous
Siloed Implementation Approach
Field
Auto
DER
Serv
Prov
SubSta
Auto
PEV
Res
DR
AMI
Core Utility Automation
WASA
Mobile
Field
Mgt
Field Mgt
SCADA
SCADA
EMS/
DMS
CIS
ESB
ESB
GIS
GIS
State
State
Estimate
Estimate
AMI
Market
DR
OMS
What is Architecture?
IEC 42010-2007: The formal organization of a system embodied in its
components, their relationship to each other and the environment and
the principles governing it’s design and evolution
– Architectural process is a phased approach. It documents with
every increasing levels of granularity and specificity, the
requirements, relationships, services and sequence necessary to
realize those goals
– Architectural art is intuition tempered by experience; it usually
takes practice to master. Artistry is needed to define the
appropriate levels of component ontological abstraction for each
phase
– Enterprise Architecture is the process of translating business
vision and strategy into effective organizational change.
Why We Need Architecture
Yes, it’s a
Kitchen/
Bathroom
Logical – but … ?
First in first out/
Priority of the day
OR
Output
Input
Architectural
Process
Different types of Architecture
Conceptual – General landscape
Network
Physical – systems/solution inventory
Source: NIST SGIP
Source: SIU
Source: Amsbary - client utility
Reference – Component (functions) make up
Source: NIST SGIP and IEC TC57
Infrastructure – exchanges/workflow
Source: Amsbary - client
Application/Solution – Specifications
Logical –functions relationship
Source: Amsbary - client
Source: Multispeak and Hydro One
Legacy C&I
5/15m, 1hr interval,
outage demand, voltage,
power quality
Head
End 1
Meter
Tech 2
Head
End 2
Meter
Tech 4
Head
End 3
Work
Management
CIS
Call Center
Installer
Systems
UID
Regulators
BEA Weblogic Enterprise Integration Hub
Event manager
Meter Directory
Advanced
Functionality
EBT
Systems
MDMS Feed
Meter
Tech 3
Outage
Management
1hr interval, TOU, voltage, theft, demand, outage
Meter
Tech 1
ODS
Tactical
Cubes
Warehouse Feed
Portal HTTP
MDMS
Head
End 4
Inventory
Asset
Management
System
Data
Warehouse
Web Services
Market
Participants
Customers
Web Services
Web Services
Web Services
Web Services
Customer/Retailer/
Regulator
Presentment Portals
LAN/SMRC/WAN
Smart Meters
Legend:
Telecom
Downstream Processing
To be developed
UID
Enterprise CIS / Billing
Existing systems
External Participant
Architecture uses Frameworks
• Including TOGAF*, DoDAF,
MoDAF, FEA, Zachman, &c
• They have their own
Methodology, Techniques
and Tools
• Incorporate Lifecycle maps
for Project Management
(PMO) and Systems
Engineering lifecycles (ITIL)
* The Open Group Architecture Framework
Architecture Phases
Rather then trying to “eat an elephant all at once”, architecture
identifies goals and decomposes them into services that
ultimately relate to the physical entities
This breaks-down into:
• Preliminary, What do you have & what are
your organization’s drivers
• Vision, what goals you trying to achieve
• Requirements, what needs do the goals
impose
• Business Services, what abstracted services
are needed to support a requirement
• Information (or Automation) Services, what
sort of applications and information models
are needed to support the abstracted service
• Technical Service, what is actually performing
the service
Don’t worry we’ll cover phases E H later
Architecture Service Orientation
Open Group Definition
• Service orientation is a way of thinking in terms of services
and service-based development and the outcomes of services
• A service:
Is a logical representation of a repeatable business activity that has a specified
outcome (e.g., provide weather data, locate fault, dispatch DER)
– Is self-contained
– May be composed of other services
– Is a “black box” to consumers of the service
– An architectural style is the combination of distinctive features in which
architecture is performed or expressed.
Simply put:
Services are “black boxes”,
messages come into them,
they work their magic, and
resulting message are sent out
interfaces
Output
Input
Process/
Service
Actor
Actor
(role an actor
assumes)
Simple Building Architecture Example
Magic in this case is the
ability to infer the options
interfaces
Input
Output
Process/
Service
Vision
Business
Services
Application
Services
Technical
Services
Water
Heat/Air
Light
Outside environ
Sanitary
Hot Water
Source
Treatment
Solar
Gas
Electric
Panels
Batteries
Inverter
&c
Green
Energy Eff
Material Reuse
Rebates
Budget
Op Costs
Initial Cost
Timeframe
Rate
Incentive
Comfort
Requirements
Why we need sequence
Sequence ensures the right thing is done in the
right order & illuminates alternatives
It’s not as easy as it sounds
Impact of no
sequence
1. Build High Rise Complex
2. Dig drainage canal to
prevent flooding
Sequence changes based on the Situation
Simple restaurant* example
Business
Requirement
A. Sit-down
Restaurant
1. Order
2. Eat
3. Pay
B. Fast Food
Chain
1. Order
2. Pay
3. Eat
C. Buffet
* Courtesy
of Doug Houseman
Business
Service
1. Pay
2. Order
3. Eat
Smart Grid Architecture Produces
• Strategic Plans
• Technical Road Maps
• Use Cases
• Reference Models
• Recommended standards
• Migration Plans
• Change Management
• Security and Governance
In short what is required to move from today’s
state to the stakeholder’s goal
Use Cases
Clarifies how a Smart Grid requirement is
envisioned to work and provides the overarching:
•
•
•
•
•
Functional requirements
Non-Functional requirements
Interfaces
Sequence
Actors (roles)
They are used and
refined throughout
the architectural
process
TOGAF Iteration & Architecture layers
TOGAF cycle and
corresponding Artifact
level of detail
Contextual/Vision
Contextual
Conceptual
Logical
Physical
Conceptual
Logical
Physical
Conceptual
Logical
Physical
• What are the Goals
• What is the current state
Conceptual
• What it shall accomplish
• What services are required
Logical
• How it shall be accomplished
• How is the architecture structured
Physical
• What resources shall be required
Architecture roadmap
Automation Technologies
Business
Logical
How?
Vision/
Contextual
Why?
Physical
With
what?
Conceptual
What?
Input from
strategy &
context
Business
Architecture
Information
Architecture
Automation
Architecture
What is the
business
What are the
info processing
requirements
What type of
applications
are required
What technical
IT services are
required
How is the
business
structured
How is
information
structured
How are these
systems
structured
How are the
“boxes”
structured
What
packages &
bespoke
software
What Hardware,
software &
network
component
Which parts
of the
business will
change
What manual
& automated
processes need
to be linked
Technical
Architecture
The Rest of the Story
Ok, now we understand what it takes to design a
Smart Grid. Now we have to implement it,
migrate legacy procedures/systems, operate it,
handle changes and ensure governance
Yikes …. Remember the other
half of the cycle?
That’s where those areas are handled
This ensures the architecture
stays viable instead of stale
 Think of this as your “honey-do” list
SGiP Smart Grid Goal:
To support Business Specific Solutions
Conceptual Architecture
Logical & Physical Architecture
Community-Serving Architecture
Deliverables
• Foundational Smart Grid services to
accelerate business specific implementations
• Concepts
• Requirements
• Business and Automation Services
• Domain Interactions
• Use-Cases
• Semantics/Vocabulary, Terminology
Business-Focused Solution Architecture
• Business specific requirements
• Business specific processes
• Business specific logical model design
• Physical interface schema design and
Standard requirements
• Solution specifications and development
• Project validation, testing & migration
• Deployment & Architecture Governance
EU & SGAC Architecture Alignment
SGAC
• Initially kept at Conceptual
level to avoid being prescriptive
• Organizationally focused
• Bulk Generation and DER
merged
EU M490 RAWG
• Logical architecture leveraging
SGAC Conceptual & GWAC IMM
• Functionally focused
• DER -No interfaces to
Transmission or Customer
Methodology Alignment Activities
EU’s Smart Grid Architectural
Methodology maps to SGAC Conceptual
Architecture & GWAC IMM Stack
Services
Hierarchy
GWAC
Stack
Based
SGAC Conceptual
Architecture
Zones
Functional` and physical
Business goals &
requirements
Market: Org and syst
Use Cases, Business
Enterprise: “back-office”
Services/Actors
(everything that’s not
Power ops and Market)
Interactions
Operation: Grid Control
(messages),
Automation
Services
Station: physical
Semantics-CDMs
substation
Field: protection and
Syntax &
monitoring equipment
Communications
Process: Primary power
Standards
delivery equipment
SGAC - Architecture roadmap
NIST Conceptual Architecture
Automation Technologies
Business
What?
Physical
With
what?
Logical
How?
Conceptual
Input from
strategy &
context
Vision/
Contextual
Why?
Business
Architecture
Information
Architecture
Automation
Architecture
What is the
business
What are the
info processing
requirements
What type of
applications are
required
What technical
ICT services are
required
How are these
systems
structured
How are the
“boxes”
structured
What
packages &
bespoke
software
What Hardware,
software &
network
component
How is the
business
structured
Which parts
of the
business will
change
How is
information
structured
What manual &
automated
processes need
to be linked
Technical
Architecture
SGiP Architecture Development
SGAC* Architecture Efforts
 Unification/alignment with other Smart Grid Efforts
(currently: EU Smart-Grid Coordination-Group and IEC TC-57 WG-19)
 Recognizes many strategic initiatives fail because new
technologies are viewed in isolation
• Addresses a holistic view of the power system and business domains
 Provides context allowing business stakeholders to prioritize and
justify often conflicting technology decisions based on a robust
conceptual model
 Facilitates common vocabulary and re-use of system level
constructs across all Smart Grid business domains
 Rich knowledge base of national-level goal decomposition,
business requirements, services and actionable vocabulary
* SGAC - Smart Grid Architecture Committee
Need for a Semantic Vocabulary
► Natural Language is Ambiguous
– One Reality, Multiple Views of It
– Meaning is Relative to a
Perception
– Perception is Contextualization
► Ambiguity can be eliminated
with Contextualization
► Contextualization can be
defined through Relations
Vocabulary and Semantics
Information Challenges
Success Factors
• Ambiguous Semantics
• Well defined vocabulary
and semantics
• Eliminate technology
dependencies/disparities
• Precise Relations
• Clear Expectations
– Inter-domain
communications
• Multiple Technologies
– Consistency
• Partially Known Value-Chain
– Cross Business-Unit
Operational implications
• Low Data Quality
– Decisions/Trust-Risk
• Poor Data Specification
– Expectations
Semantic Modeling Language
Need for actionable vocabulary beyond model languages such as
Universal Modeling Language (UML)
► Open Source managed by W3C a nonpropriety file format
► Ontology Web Language (OWL) is more
expressive than UML
Actionable
► Simple Structure
•
•
Subject, Verb, Object (triple) which is stored in a
Resource Description Framework (RDF) for
access
Triplets can be transparently merged across data
sources
► Provides formal verification across diverse
vocabularies
► If it’s Web addressable, its available for
use
► Analysis/query (SPARQL)
RDF Example
Three triplets
as
URI
Steve Ray
Steve
URI
Steph
EnerNex
URI
http://www.enernex.com/employees/stephanamsbary/#!/
Web Semantic Mash-up Example
DoE Smart Grid Clearinghouse
http://www.sgiclearinghouse.org/?q=node/13
With no programming – just
a RFS definition
Each project has dissimilar
• Location information
• Labels
• Project details
Google recognizes as such
• Maps each project
location
• Labels each by it’s type
(AMI, CS, DS, &c.)
• Links to project details
Maturity Models
Maturity Models are strategic frameworks to
identify opportunities for improvement
• They create a roadmap identifying activities, best practices and
investments leading to the desired state
• Provides maturity characteristics expected for each stage of
maturity
• Provide an assessment of the current state and help bridge the
gaps to the future state
• Observable indicators of progress – measurable outcomes that
improve with each stage of maturity
SEI* Smart Grid Maturity Model
* SEI - Carnegie Mellon Software Engineering Institute
30
SEI Smart Grid Maturity Model
31
GWAC* Smart Grid
Interoperability Maturity Model (IMM)
Work In Progress
GWAC Context-setting Framework
SEI Smart Grid
Maturity Model
Level Title
5
Optimizing
4
Quantitatively
Managed
3
Defined
NEHTA Interoperability
Maturity Model
2
Managed
http://www.nehta.gov.au/connecting-
1
Initial
australia/ehealth-interoperability
* GWAC – DoE GridWise Architecture Council
The GWAC IMM Stack
• 1 Framework (GWAC Stack)
– 8 interoperability categories
consolidated into 3 layers
• 10 Cross -Cutting issues – 3 layers
• 9 Interoperability Areas
– Combining the interoperability and
cross cutting categories provides a
two dimensional matrix that helps
simplify the conceptual landscape
Slide courtesy of Mark Knight
Level 5 IMM Maturity Example
CROSS CUTTING ISSUES
5 Optimizing
Quantitatively
Managed
3 Defined
LEVEL OF MATURITY
4
2 Managed
ORGANIZATIONAL
INFORMATIONAL
TECHNICAL
1 Initial
OPERATION
CONFIGURATION
& EVOLUTION
SECURITY
& SAFETY
GWAC
SG IMM Evaluation Matrix
Interoperability Areas
Maturity level Metrics (questions)
Smart Grid Architecture Summary
► Affects the entire organization, not just computer techies
► A process that minimizes risk and gives insight into how the
business operates today and what changes are needed to
achieve the business’ grid modernization objectives
► A means to:
• Gain operational efficiencies
• Maximize assets and personnel
• Bring order to IT delivery - aligning Business Services with the
underlying automation Services-Oriented (SOA) foundation
► SGAC efforts are performing the heavy lifting to define Smart
Grid’s foundation
► Several Utilities are using EA (and TOGAF)
Notable examples:
Southern California Edison
Consumers Electric
Duke Energy
Florida Power and Light
National Grid
Pacific Gas & Electric
Most Smart Grid software
vendors
Want to know more
► SGAC Conceptual Architecture Session
– Monday at 2:30 – 4:00PM
► Current status of SGAC activities
• Wednesday at 3:30-5:00PM
► Smart Grid Interoperability Maturity (SG-IMM)
– Wednesday at 3:30-15:00AM
► Demand/Response Architecture
– Thursday at 8:00-10:00AM
► SG-IMM Work Shop
– Thursday at 1:00-2:30P
References
National Use-case repository:
http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/IKBUseCases
SGIP SGAC:
http://collaborate.nist.gov/twikisggrid/bin/view/SmartGrid/SmartGridArchitectureCommittee
EU Commission Mandate M.490 Reference Architecture
http://ps.kan.bg/wp-content/uploads/2012/01/ClC13-Sec2012-004_SGCGRAWG-Reference-Architecture-TR-v0-5.pdf
EPRI IntelliGrid
http://intelligrid.epri.com/
GridWise AC:
www.gridwiseac.org
UCA International (OpenSG):
http://osgug.ucaiug.org
Software Engineering Institute Smart Grid Maturity Model
http://www.sei.cmu.edu/smartgrid/
The Open Group (TOGAF):
http://www.opengroup.org/togaf/
Questions ?
How does this work?
Electric Research, Engineering, and Consulting
STEPHAN AMSBARY
Director, Utility Enterprise Architecture
Stephan@EnerNex.com
Phone: +1.828.559.1110
FAX: 865.218.8999
1993 Grants Mountain Rd, Marion, NC, 28752-9513