1. Smart Grid (Enterprise) Architecture 101 2012/Dec/04

2. Agenda Architecture Overview Architecture Overview SGAC Conceptual Architecture SGAC Conceptual Architecture Semantics / Vocabulary Semantics / Vocabulary Maturity Models Maturity Models Summary/Resources Summary/Resources

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

4. Siloed Implementation Approach AMI Field Auto Res DR DER PEV SubSta Auto Serv Prov WASA Core Utility Automation SCADA CIS EMS/ DMS Mobile Field Mgt GIS State Estimate Core Utility Automation SCADA CIS EMS/ DMS Mobile Field Mgt GIS State Estimate ESB AMIMarket ESB DROMS

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

6. Why We Need Architecture Architectural Process Input Output First in first out/ Priority of the day Logical – but … ? OR Yes, it’s a Kitchen/ Bathroom

7. Different types of Architecture Application/Solution – Specifications Source: Amsbary - client Infrastructure – exchanges/workflow Source: Amsbary - client Physical – systems/solution inventory Source: Amsbary - client utility Logical –functions relationship Source: Multispeak and Hydro One Reference – Component (functions) make up Source: NIST SGIP and IEC TC57 Conceptual – General landscape Source: NIST SGIP Network Source: SIU

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

9. 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 Preliminary, What do you have & what are your organization’s drivers Vision Vision, what goals you trying to achieve Requirements Requirements, what needs do the goals impose Business Services Business Services, what abstracted services are needed to support a requirement Information (or Automation) Services Information (or Automation) Services, what sort of applications and information models are needed to support the abstracted service Technical Service Technical Service, what is actually performing the service Don’t worry we’ll cover phases E H later

10. Architecture Service Orientation Open Group Definition Process/ Service Input Output Actor interfaces 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)

11. Simple Building Architecture Example Vision Comfort Green Budget Require- ments Water Heat/Air Light Outside environ Sanitary Energy Eff Material Reuse Op Costs Initial Cost Timeframe Business Services Hot Water Source Treatment Rebates Rate Incentive Application Services Solar Gas Electric Technical Services Panels Batteries Inverter &c Process/ Service Input Output interfaces Magic in this case is the ability to infer the options

12. 1.Build High Rise Complex 2.Dig drainage canal to prevent flooding Why we need sequence Impact of no sequence Sequence ensures the right thing is done in the right order & illuminates alternatives It’s not as easy as it sounds

13. Sequence changes based on the Situation BusinessRequirement A.Sit-down Restaurant B.Fast Food Chain C.BuffetBusinessService 1.Order 2.Eat 3.Pay 1.Order 2.Pay 3.Eat 1.Pay 2.Order 3.Eat * Courtesy of Doug Houseman Simple restaurant * example

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

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

16. TOGAF Iteration & Architecture layers TOGAF cycle and corresponding Artifact level of detail Contextual Conceptual Logical Physical Conceptual Logical Physical Contextual/Vision What are the Goals What is the current stateConceptual What it shall accomplish What services are requiredLogical How it shall be accomplished How is the architecture structuredPhysical What resources shall be required Conceptual Logical Physical

17. Technical Architecture Automation Architecture Information Architecture Business Architecture Business Architecture roadmap Input from strategy & context Vision/ Contextual Why? Conceptual What? Logical How? Physical With what? 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 Automation Technologies

18. The Rest of the Story Now 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  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

19. 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: To 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

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

21. Methodology Alignment Activities EU’s Smart Grid Architectural Methodology maps to SGAC Conceptual Architecture & GWAC IMM Stack Semantic s Flow 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 substationZones Functional` and physical Field: protection and monitoring equipment Process: Primary power delivery equipment Interactions (messages), Semantics Automation Services Semantics-CDMs Use Cases, Business Services/Actors Business goals & requirements Syntax Syntax & Communications Standards SGAC Conceptual Architecture Hierarchy GWAC Stack Based

22. Technical Architecture Automation Architecture Information Architecture Business Architecture Business SGAC - Architecture roadmap Input from strategy & context Vision/ Contextual Why? Conceptual What? Logical How? Physical With what? 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 Automation Technologies NIST Conceptual Architecture SGiP Architecture Development

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

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

25. Vocabulary 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

26. Semantic ModelingLanguage Semantic Modeling Language ► 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)

27. Three triplets RDF Example URI http://www.enernex.com/employees/stephan- amsbary/#!/ Steve Ray EnerNex as Steve Steph

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

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

30. 30 SEI* Smart Grid Maturity Model * SEI - Carnegie Mellon Software Engineering Institute

31. 31 SEI Smart Grid Maturity Model

32. GWAC* Smart Grid Interoperability Maturity Model (IMM) GWAC Context-setting Framework SEI Smart Grid Maturity Model NEHTA Interoperability Maturity Model http://www.nehta.gov.au/connecting- australia/ehealth-interoperability http://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 Progress

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

34. Level 5 IMM Maturity Example ORGANIZATIONAL INFORMATIONAL TECHNICAL LEVEL OF MATURITY CONFIGURATION & EVOLUTION OPERATION SECURITY & SAFETY CROSS CUTTING ISSUES INTEROPERABILITY CATEGORIES 5Optimizing 4 Quantitatively Managed 3Defined 2Managed 1Initial

35. GWAC SG IMM Evaluation Matrix Maturity level Metrics (questions)Interoperability Areas

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

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

38. References National Use-case repository: http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/IKBUseCases SGIP SGAC: http://collaborate.nist.gov/twiki- sggrid/bin/view/SmartGrid/SmartGridArchitectureCommittee EU Commission Mandate M.490 Reference Architecture http://ps.kan.bg/wp-content/uploads/2012/01/ClC13-Sec2012-004_SGCG- RAWG-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/

39. Questions ? How does this work? S TEPHAN A MSBARY Director, Utility Enterprise Architecture Stephan@EnerNex.com Phone: +1.828.559.1110 FAX: 865.218.8999 1993 Grants Mountain Rd, Marion, NC, 28752-9513 Electric Research, Engineering, and Consulting