Smart GridSmart Grid(Enterprise) Architecture 101(Enterprise) Architecture 101

2012/Dec/042012/Dec/04

AgendaAgenda

• Architecture OverviewArchitecture Overview

• SGAC Conceptual ArchitectureSGAC Conceptual Architecture

• Semantics / VocabularySemantics / Vocabulary

• Maturity ModelsMaturity Models

• Summary/ResourcesSummary/Resources

Architecture as usually practicedArchitecture as usually practiced

ARCHITECTUREARCHITECTUREOR BUY A VENDOR’S OR BUY A VENDOR’S PACKAGEPACKAGE

(Apologies to Mr Adams and my fellow architects)

There is never enough time (or money) There is never enough time (or money) to do it right the first timeto do it right the first time

There is always enough time and There is always enough time and money to fix it over and over againmoney to fix it over and over again

-Anonymous-Anonymous

Siloed Implementation ApproachSiloed Implementation Approach

AMI

FieldAuto

ResDRDER PEVSubSta

AutoServProv

WASACore Utility Automation

SCADA

CISEMS/DMS

Mobile Field Mgt

GIS StateEstimate

Core Utility Automation

SCADA

CISEMS/DMS

Mobile Field Mgt

GIS StateEstimate

ESB

AMI Market

ESB

DR OMS

What is Architecture?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 approachArchitectural 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 experienceArchitectural 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 Enterprise Architecture is the process of translating business vision and strategy into effective organizational change.

Why We Need ArchitectureWhy We Need Architecture

ArchitecturalProcess

Input Output

First in first out/Priority of the day

Logical – but … ?

OR

Yes, it’s a Kitchen/

Bathroom

Different types of ArchitectureDifferent types of Architecture

Application/Solution – SpecificationsSource: Amsbary - client

Infrastructure – exchanges/workflowSource: Amsbary - client

Physical – systems/solution inventorySource: Amsbary - client utility

Logical –functions relationshipSource: Multispeak and Hydro One

Reference – Component (functions) make upSource: NIST SGIP and IEC TC57

Conceptual – General landscapeSource: NIST SGIP

Outage Management

Work Management CIS Call Center

Asset Management

SystemInventory

Data Warehouse

MDMS

Tactical Cubes

Web Services

Web Services

Web Services

Web Services

Web Services

Customers

EBT Systems

Regulators

Market Participants

Legacy C&I5/15m, 1hr interval,

outage demand, voltage, power quality

Meter Tech 1

Meter Tech 2

Meter Tech 3

Meter Tech 4

Head End 1

Head End 2

Head End 3

Head End 4

Installer Systems

1hr interval, T

OU

, voltage, th

eft, dem

and

, outag

e

UID Event managerMeter Directory

Advanced Functionality

Customer/Retailer/ Regulator

Presentment Portals

Smart Meters

LAN/SMRC/WAN

Telecom Downstream Processing Enterprise CIS / Billing External Participant

Warehouse Feed

ODS

Portal HTTP

Legend: To be developed UID Existing systems

BEA Weblogic Enterprise Integration Hub

MD

MS

Fe

ed

NetworkSource: SIU

Architecture uses FrameworksArchitecture 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 Architecture PhasesPhasesRather 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:

•PreliminaryPreliminary, What do you have & what are your organization’s drivers•VisionVision, what goals you trying to achieve•RequirementsRequirements, what needs do the goals impose•Business ServicesBusiness Services, what abstracted services are needed to support a requirement•Information (Information (or Automationor Automation) Services) Services, what sort of applications and information models are needed to support the abstracted service•Technical ServiceTechnical Service, what is actually performing the service

Don’t worry we’ll cover phases E H later

Architecture Architecture Service OrientationService OrientationOpen Group DefinitionOpen Group Definition

Process/Service

Input Output

Actor Actor

interfacesSimply put: Simply put: Services are “black boxes”, messages come into them, they work their magic, and resulting message are sent out

• 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.

(role an actor assumes)

Simple Building Architecture ExampleSimple Building Architecture Example

Vision

Comfort

Green

Budget

Require-mentsWaterHeat/AirLightOutside environSanitary

Energy EffMaterial Reuse

Op CostsInitial CostTimeframe

BusinessServicesHot WaterSourceTreatment

Rebates

Rate Incentive

ApplicationServicesSolarGasElectric

TechnicalServicesPanelsBatteriesInverter&c

Process/Service

Input Output

interfacesMagic in this case is the ability to infer the options

1. Build High Rise Complex

2. Dig drainage canal to prevent flooding

Why we need sequenceWhy we need sequence

Impact of no sequence

Sequence ensures the right thing is done in the right order & illuminates alternativesIt’s not as easy as it soundsIt’s not as easy as it sounds

Sequence changes based on the SituationSequence changes based on the Situation

BusinessBusinessRequirementRequirement

A.Sit-downRestaurant

B.Fast FoodChain

C.Buffet

BusinessBusinessServiceService

1.Order2.Eat3.Pay

1.Order2.Pay3.Eat

1.Pay2.Order3.Eat

* Courtesy of Doug Houseman

Simple restaurant* example

Smart Grid Architecture ProducesSmart 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 CasesUse CasesClarifies 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 layersTOGAF Iteration & Architecture layers

TOGAF cycle and corresponding Artifact level of detail

Contextual

ConceptualLogicalPhysical

ConceptualLogicalPhysical

Contextual/VisionContextual/Vision• What are the Goals• What is the current state

ConceptualConceptual• What it shall accomplish• What services are required

LogicalLogical• How it shall be accomplished• How is the architecture structured

PhysicalPhysical• What resources shall be required

ConceptualLogicalPhysical

TechnicalArchitecture

Automation Architecture

Information Architecture

Business Architecture

Business

Architecture roadmapArchitecture roadmap

Input from strategy &

context

Vision/Contextual Why?

Conc

eptu

alW

hat?

Logi

cal

How

?Ph

ysic

alW

ith

wha

t?

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

Which parts of the business will change

What manual & automated processes need to be linked

What packages & bespoke software

What Hardware, software & network component

Refinement

Refinement

Automation Technologies

The Rest of the StoryThe Rest of the StoryOk, now we understand what it takes to design a

Smart Grid. NowNow we have to implement it, migrate legacy procedures/systems, operate it, handle changes and ensure governance

YikesYikes …. 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

Logical & Physical Architecture

Conceptual Architecture

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

SGiP Smart Grid Goal:SGiP Smart Grid Goal:To support Business Specific SolutionsTo support Business Specific Solutions

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

EU & SGAC Architecture AlignmentEU & 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

SemanticsFlow

Services Operation: Operation: Grid Control

Enterprise: Enterprise: “back-office” (everything that’s not Power ops and Market)

Market:Market: Org and syst

Station: Station: physical substation

ZonesZonesFunctional` and physical

Field: protection and monitoring equipment

Process: Primary power delivery equipment

Interactions (messages),Automation Services SemanticsSemantics-CDMs

Use Cases, Business Services/Actors

Business goals & requirements

SyntaxSyntax &CommunicationsStandards

SGAC Conceptual SGAC Conceptual ArchitectureArchitecture

Hierarchy Hierarchy GWAC GWAC Stack Stack BasedBased

TechnicalArchitecture

Automation Architecture

Information Architecture

Business Architecture

Business

SGAC - Architecture roadmapSGAC - Architecture roadmap

Input from strategy &

context

Vision/Contextual Why?Co

ncep

tual

Wha

t?Lo

gica

lH

ow?

Phys

ical

With

w

hat?

What is the business

What are the info processing requirements

What type of applications are required

What technical ICT services are required

How is the business structured

How is information structured

How are these systems structured

How are the “boxes” structured

Which parts of the business will change

What manual & automated processes need to be linked

What packages & bespoke software

What Hardware, software & network component

Refinement

Refinement

Automation Technologies

NIST Conceptual ArchitectureNIST Conceptual Architecture

SGiP Architecture DevelopmentSGiP Architecture Development

SGAC* Architecture EffortsSGAC* 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 modelFacilitates common vocabulary and re-use of system level constructs across all Smart Grid business domainsRich knowledge base of national-level goal decomposition, business requirements, services and actionable vocabulary

* SGAC - Smart Grid Architecture Committee

Need for a Semantic VocabularyNeed 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 SemanticsVocabulary and Semantics

Information Challenges• Ambiguous Semantics

– 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

Success Factors• Well defined vocabulary

and semantics• Eliminate technology

dependencies/disparities• Precise Relations• Clear Expectations

Semantic ModelingSemantic Modeling LanguageLanguage

► Open Source managed by W3C a non-propriety 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)

Need for actionable vocabulary beyond model languages such as Universal Modeling Language (UML)

Three triplets

RDF ExampleRDF Example

URI

URI

URI

http://www.enernex.com/employees/stephan-amsbary/#!/

Steve Ray

EnerNexEnerNex

as

SteveSteve

StephSteph

Web Semantic Mash-up ExampleWeb Semantic Mash-up Example

DoE Smart Grid Clearinghousehttp://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 ModelsMaturity 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

30

SEI* Smart Grid Maturity ModelSEI* Smart Grid Maturity Model

* SEI - Carnegie Mellon Software Engineering Institute

31

SEI Smart Grid Maturity ModelSEI Smart Grid Maturity Model

GWAC* Smart Grid GWAC* Smart Grid Interoperability Maturity Model (IMM)Interoperability Maturity Model (IMM)

GWAC Context-setting Framework

SEI Smart Grid Maturity Model

NEHTA InteroperabilityMaturity Modelhttp://www.nehta.gov.au/connecting-australia/ehealth-interoperability

Level Title

5 Optimizing

4 Quantitatively Managed

3 Defined

2 Managed

1 Initial

* GWAC – DoE GridWise Architecture Council

Work In ProgressWork In Progress

The GWAC IMM StackThe 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 Level 5 IMM Maturity ExampleExample

ORGANIZATIONAL

INFORMATIONAL

TECHNICAL

LEVE

L O

F M

ATU

RITY

CONFIGURATION& EVOLUTION

OPERATIONSECURITY & SAFETY

CROSS CUTTING ISSUES

INTEROPERABILI

TY CATEGORIES

5 Optimizing

4 Quantitatively Managed

3 Defined

2 Managed

1 Initial

GWAC GWAC SG IMM Evaluation MatrixSG IMM Evaluation Matrix

Maturity level Metrics (questions)Interoperability Areas

Smart Grid Architecture SummarySmart 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:

Want to know moreWant 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

ReferencesReferencesNational Use-case repository:

http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/IKBUseCasesSGIP SGAC:

http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/SmartGridArchitectureCommittee

EU Commission Mandate M.490 Reference Architecturehttp://ps.kan.bg/wp-content/uploads/2012/01/ClC13-Sec2012-004_SGCG-

RAWG-Reference-Architecture-TR-v0-5.pdfEPRI IntelliGrid

http://intelligrid.epri.com/GridWise AC:

www.gridwiseac.orgUCA International (OpenSG):

http://osgug.ucaiug.orgSoftware 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?How does this work?

STEPHAN AMSBARYDirector, Utility Enterprise Architecture

Stephan@EnerNex.comPhone: +1.828.559.1110

FAX: 865.218.89991993 Grants Mountain Rd, Marion, NC, 28752-9513

Electric Research, Engineering, and Consulting