1 / 24

Architectural Methodology

Architectural Methodology. IEC WG 19 Meeting Geneva, CH 2012/May/11. Joint NIST-SGAC / EU-M.490 RAWG Efforts. NIST SGAC Conceptual Architecture. Automation Technologies. Business. Input from strategy & context. Automation Architecture. Interaction Architecture. Technical Architecture.

kaloni
Download Presentation

Architectural Methodology

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. Interaction Messaging Artifact <Business Service Name> <Input> <Output> <Output> <Input> • Archetypical: • 20 Actors • 25 Message (interaction) • 213 Business Services <Actor> <Actor>

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

  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 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 System B Economic / Regulatory Policy Business Layer Business Objectives Function Layer Business Procedures Business Context Information Layer Semantic Understanding Syntactic Interoperability Communication Layer Network Interoperability Basic Connectivity Component Layer Function

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

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

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

  11. Methodology Results • 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 • Identify functions/services (in the functional layer, functions and services can be treated in the same manner) • Identify interactions of functions/services • 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 • 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 • Identify Canonical Data Model (CDM) that supports interfaces • Identify Canonical Data Model (CDM) that supports functions • Place CDMs on smart grid plane on appropriate domain and zone

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

  18. 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 controlablesetpoint 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 Example Use Case

  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 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 Electric Research, Engineering, and Consulting

More Related