1. IEC WG 19 Meeting Geneva, CH 2012/May/11 Architectural Methodology Joint NIST-SGAC / EU-M.490 RAWG Efforts

2. NIST SGAC Conceptual Architecture Technical Architecture Interaction Architecture Automation Architecture Business Architecture Business Input from strategy & context Goals/ Contextual Why? Conceptual What? What services does the business fulfill What types of applications are required What information must be exchanged What ICT services are required Automation Technologies B Business Prelim A Prelim & AC IT SysTOGAFPhase C Data

3. Interaction Messaging Artifact Archetypical : 20 Actors 25 Message (interaction) 213 Business Services

4. Example: Iteration Services for Forecast Intermittent Generation Forecast Intermittent Generation Market Manager Measurement Environment Forecast

5. Suggested Methodology Alignment Semantics relating to EU M490 RAWG Apply Conceptual Architecture elements to DEWG DER use cases Integrate EU and DEWG Point-of-View Use Cases Business Services Business Processes (Interactions)

6. Suggested Methodology Alignment Cross-Cutting Cross-Cutting Requirements Define/create fundamental Solution Blocking Blocks (SBB)  Example: adopt/modify Open Group SOA practices Leverage common Smart Grid messaging and Cross- cutting requirements as SBB) Open Group SOA Quality of Service Building Block

7. Refinement of GWAC stack to SGAM layer associations Before: Business context associated to Function Layer After: Business context associated to Information Layer Reason:Business context deals with information used in specific context System A Business Context Semantic Understanding Network Interoperability Syntactic Interoperability Basic Connectivity Business Procedures Business Objectives Economic / Regulatory Policy Function System B Business Layer Function Layer Information Layer Communication Layer Component Layer

8. Methodology Alignment Activities Map EU’s Smart Grid Architectural Methodology to NIST Conceptual Architecture & CSWG approach Interactions, Semantics Automation Services Semantics-CDMs Use Cases, Business Services/Actors Business goals & requirements GWAC Stack Based Syntax Syntax & Communications Standards

9. Ongoing Work Aligning Processes 9 What services, standards semantics and interoperability requirements are needed support Smart Grid? Result Traceable architecture Set of architecture templates identified EG1 Report 6 High level services 2. Step Create Architectures Map onto Architecture Model Architecture Model 3. Step Locate standards usage 4. Step Identify common standards First set of standards Sources Expected outcome WG-RA Architecture Model t.b.d US Laws & Regulations Technical Architecture Interaction ArchitectureAutomation Architecture Business Architecture Business Input from strategy & context Goals/ Contextua l Why? Conceptual What? What services does the business fulfill What types of applications are required What information must be exchanged What ICT services are required Automation Technologies

10. Ongoing Work Aligning Processes 10 Result Identify “new” gaps Systematically investigate need for new standards How to systematically identify future gaps? Further findings: R&D, Pilots, Implementation 3. Step Locate require- ments for standards 4. Step Identify new gaps NEW Gap List (follow process 2. from here) Source Expected outcome t.b.d Target date from 2013 SGAM GAP 2. Step Create Architectures Map onto Architecture Model Technical Architecture Interaction ArchitectureAutomation Architecture Business Architecture Business Input from strategy & context Goals/ Contextu al Why? Conceptual What? What services does the business fulfill What types of applications are required What information must be exchanged What ICT services are required Automation Technologies

11. Methodology Results 11 Provide base architecture and process to vet future Smart Grid requirements Identify gaps in Smart Grid standardization Compare different architectures Identify Cross-cutting requirements Map regional differences Identify new services and interoperability requirements Coordinate work between different TCs and stakeholders

12. Next steps  Continue on term definitions  Continue on SGAM mapping process definition  Review of SGAC comments on RAWG document  Prioritize crosscutting requirements  Refine processes for semantic mapping and business context mapping  Gain more exercise with SGAM mapping (DER management UC)

13. Refinement of SGAM mapping process / 1 Required Input  UC including actors, roles, functions/services (acc. definition), sequence diagrams, func. and non-func. requirements

14. Refinement of SGAM mapping process / 2 Function Layer Develop Function Layer 1. Identify functions/services (in the functional layer, functions and services can be treated in the same manner) 2. Identify interactions of functions/services 3. Place functions/services on appropriate domain and zone

15. Refinement of SGAM mapping process / 3 Information Layer Need for business context and canonical data model (CDM) views to cover both instances and data model aspects of information Develop Business Context Layer 1. Place sequence of exchanged information between functions/services on smart grid plane on appropriate domain and zone

16. Refinement of SGAM mapping process / 4 Information Layer cont. Develop Canonical Data Model (CDM) Layer 1. Identify Canonical Data Model (CDM) that supports interfaces 2. Identify Canonical Data Model (CDM) that supports functions 3. Place CDMs on smart grid plane on appropriate domain and zone

17. Refinement of SGAM mapping process / 5 Communication Layer Tbd.

18. Example Use Case UC: DMS System controls reactive power of DER unit Business Service: Voltage control in distribution system  Service: RTU Data-acquisition  Service: Voltage/Var control  Service: Control/Supervision of DER  Service: Audit of control actions Precondition:  Data-acquisition is running  Feeder electric models are current Sequence of events :  RTU sends measurement to DMS  Voltage/Var-Control is triggered by event  Voltage/Var-Control calculates control value  Voltage/Var-Control sends control value to DMS  DMS sends controlable setpoint to DER  DER receives setpoint and acknowledges  DER adjusts reactive power injection  DMS posts DER control action to audit of control actions  CRM system obtains audit actions

19. Component Layer

20. Business Layer / Function Layer

21. Information Layer Business Context (Message) View Can. Data Model View

22. Communication Layer

23. Questions ? How does this work?

24. Back-up Slides 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