Interaction Architecture for EITC W. T. Cox 2010-05-04 Version 4.

Slides:



Advertisements
Similar presentations
REST Introduction 吴海生 博克软件(杭州)有限公司.
Advertisements

Enhancing Demand Response Signal Verification in Automated Demand Response Systems Daisuke Mashima, Ulrich Herberg, and Wei-Peng Chen SEDN (Solutions for.
Ulrich Herberg(*), Daisuke Mashima, Jorjeta G. Jetcheva, and Sanam Mirzazad-Barijough Fujitsu Laboratories of America, Inc. (* Currently with Panasonic)
Software Connectors Software Architecture. Importance of Connectors Complex, distributed, multilingual, modern software system functionality and managing.
SOA and Web Services. SOA Architecture Explaination Transport protocols - communicate between a service and a requester. Messaging layer - enables the.
Chapter 19: Network Management Business Data Communications, 4e.
2-1 © Prentice Hall, 2007 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Software Connectors. Attach adapter to A Maintain multiple versions of A or B Make B multilingual Role and Challenge of Software Connectors Change A’s.
1 ITC242 – Introduction to Data Communications Week 12 Topic 18 Chapter 19 Network Management.
Architecture & Data Management of XML-Based Digital Video Library System Jacky C.K. Ma Michael R. Lyu.
Architectural Design Principles. Outline  Architectural level of design The design of the system in terms of components and connectors and their arrangements.
Hands-On Microsoft Windows Server 2003 Administration Chapter 5 Administering File Resources.
DiffIE: Changing How You View Changes on the Web DiffIE: Changing How You View Changes on the Web Jaime Teevan, Susan T. Dumais, Daniel J. Liebling, and.
Demystifying Architectural Styles Nikunj Mehta 3/11/02Demystifying Architectural Styles2 Architectural Styles Characterize –Structure, i.e. external.
1 © 1999 Citrix Systems Inc Java on Nemesis Tim Harris.
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
Service Broker Lesson 11. Skills Matrix Service Broker Service Broker, provides a solution to common problems with message delivery and consistency that.
SOA Reference Model Generic Presentation DRAFT: Not approved by the OASIS SOA RM TC.
Secure Systems Research Group - FAU Web Services Standards Presented by Keiko Hashizume.
Client/Server Software Architectures Yonglei Tao.
Objectives Design Class Diagrams Issues in system design Generalization Review UML papers.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
Network Architecture and Protocol Concepts. Network Architectures (1) The network provides one or more communication services to applications –A service.
Page 1 May 2009 SOS Concepts in DM2 – SoaML Example The purpose of this is to refine SOA concepts in DM2 –It is a summary for the DM2/SOA team –Based on.
Connector Types Interaction services broadly categorize connectors Many details are left unexplained. They fail to provide enough detail to be used in.
Presentation on Osi & TCP/IP MODEL
An Object-Oriented Approach to Programming Logic and Design
1 CS 456 Software Engineering. 2 Contents 3 Chapter 1: Introduction.
Department of Electronic Engineering City University of Hong Kong EE3900 Computer Networks Introduction Slide 1 A Communications Model Source: generates.
Wireless Access and Terminal Mobility in CORBA Dimple Kaul, Arundhati Kogekar, Stoyan Paunov.
#ConnWeekSanta Clara, CA May 22-24, OpenADR 2.0 Signaling over Tropos Network  Architecture, Communications and Security May Jim Compton.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 09. Review Introduction to architectural styles Distributed architectures – Client Server Architecture – Multi-tier.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
XML Web Services Architecture Siddharth Ruchandani CS 6362 – SW Architecture & Design Summer /11/05.
© 2005 Prentice Hall10-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Design Analysis builds a logical model that delivers the functionality. Design fully specifies how this functionality will be delivered. Design looks from.
SMash : Secure Component Model for Cross- Domain Mashups on Unmodified Browsers WWW 2008 Frederik De Keukelaere et al. Presenter : SJ Park.
1 Integrating security in a quality aware multimedia delivery platform Paul Koster 21 november 2001.
2007/03/26OPLAB, NTUIM1 A Proactive Tree Recovery Mechanism for Resilient Overlay Network Networking, IEEE/ACM Transactions on Volume 15, Issue 1, Feb.
© 2015 Electric Power Research Institute, Inc. All rights reserved. Ameen H. Hamdon, P.Eng President, SUBNET Solutions Inc. EMMOS 2015 September 22, 2015.
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Database Design Some of these slides are derived from IBM/Rational slides from courses on UML and object-oriented design and analysis. Copyright to the.
Introduction to Grids By: Fetahi Z. Wuhib [CSD2004-Team19]
Types of Operating Systems 1 Computer Engineering Department Distributed Systems Course Assoc. Prof. Dr. Ahmet Sayar Kocaeli University - Fall 2015.
Architecture for Context-Aware Services in Gaia Anand Ranganathan.
FIPA Abstract Architecture London FIPA meeting January 24-29, 2000 from: TC-A members.
Slide 1 Service-centric Software Engineering. Slide 2 Objectives To explain the notion of a reusable service, based on web service standards, that provides.
© Drexel University Software Engineering Research Group (SERG) 1 The OASIS SOA Reference Model Brian Mitchell.
GRID ANATOMY Advanced Computing Concepts – Dr. Emmanuel Pilli.
Implementing The SOA Reference Model An ESB Developer’s Perspective David Millman Principal Architect 9/8/2008.
2.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition System Programs (p73) System programs provide a convenient environment.
Slide 1 2/22/2016 Policy-Based Management With SNMP SNMPCONF Working Group - Interim Meeting May 2000 Jon Saperia.
Interaction Architecture for EITC W. T. Cox Version 3.
Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.
Software Connectors. What is a Software Connector? 2 What is Connector? – Architectural element that models Interactions among components Rules that govern.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
4WARD Networking of Information 4WARD WP6. © 4WARD Consortium Confidential Networking of Information Telephony Interconnecting wires 4WARD Future Internet.
DOTS Requirements Andrew Mortensen November 2015 IETF 94 1.
Enabling Standards for Demand Side Management
NSI Topology Thoughts on how topology fits into the NSI architecture
Software Connectors.
Recipe for a Transactive Energy Implementation for Microgrids

What is an Architecture?
Interaction for EITC W. T. Cox Draft 4.
OpenADR SRS Draft 1 Review
What is an Architecture?
Presentation transcript:

Interaction Architecture for EITC W. T. Cox Version 4

2 Zoom in on Interoperation Recursive pairwise relationship Participant implements aggregator interface to distribute events to its own participants Compose appropriate security, reliability, and interaction model as appropriate for each interoperation link Names are not set; intended to be more evocative than Gale Horst’s Virtual End Node and Resource Energy Controller (VEN and REC) but the concept is the same. Aggregator- Operator Participant- Operator DREvents Signals and responses

3 Abstract to Concrete(1) ISO Aggregator Store HQ Store Location Store Location Store Equipment

4 Abstract to Concrete(2) ISO Aggregator Industrial Microgrid Industrial Microgrid Industrial Facility Industrial Facility Process Control

5 DR Event Services The direction shown is from initiator to service. Response or ACKs not shown NOTE: OpenADR names assume an intermediary, the DRAS, where information is stored Aggregator- Operator Participant- Operator Determination of nature and details of DR Event InitiateDrEvent ModifyDrEvent GetDrEventInformation CancelDrEvent SetDrEventFeedback… CreateResponseSchedule… SubmitDrStandingBid… GetAggregatorDrEventStatus…

Changes in This Version Internal-only services have been deleted –From D1 –DrEvent services kept See Spreadsheet Tab D3 Total 25 services so far –5 invoked by Aggregator on Participant –21 invoked by Participant on Aggregator 6

Aggregator on Participant 5 invoked by Aggregator on Participant –Initiate, Modify, Adjust, CancelDrEvent, GetDrEventInformation –Explicit, not implicit, reliability signals –Which invocations send price/product? –Naming needs work—not all are DR Some will be price Some will be (e.g.) usage/load information (2 way) 7

Participant on Aggregator 21 invoked by Participant on Aggregator –2 Event Feedback –3 Response Schedule –5 DR Bid Services –2 Status Services –1 DR Program Services –2 Participant Management Services –3 Program Constraints Services –3 OptOut State Services 8

Next Steps (1) Names that are more indicative of content Detailed message content Application ACK and Reliable Messaging Consider using WS-Addressing, WS- Context Delivery of other messages via EI? –Text messages as in some designs? 9

Next Steps (2) Factor into type of communication/interoperation –DR (reliability signal-related) –Price+Product Def communication –Other Communications, e.g. Load (History, Present, Future) Usage (History Present, Future) Details on each service family –Location of information –Operations 10

Previous Slides Not changed in this version 11

12 A Slice Through the Notification Tree Aggregator- Operator DREvent Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator ISOAggregAgg Client Industrial PkTenant

13 Protection and Reliability Aggregator- Operator DREvent Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator ISO Aggregator Aggretator Client Industrial Park Tenant More ProtectedLess Protected Fewer Per LayerMore Per Layer More ReliableLess Reliable

14 ISO Issues and Requirements (1) ISO issues with varying security and reliability/confirmation of delivery requirements Application to non-California markets and interactions Factor out tariffs/contracts –Notification of reliability events is key to ISOs –Distribution is also key to ISOs Price communication is relatively unimportant to some ISOs –Price quote/closing price stream is important and done today (with no standard format/delivery mechanism) –EMIX as the price quote stream

15 Requirements & Conclusions Factor out tariffs/contracts Price communication must be in the spec Price communication is not only via the spec –EMIX as price quote stream, various transports Need requirements in citable format for detailed analysis –IRC, NAESB, EIS Alliance

16 Participant/Real Estate Notes Real estate managers and landlords want a way to distribute events to tenants and/or separate owned properties Price distribution appears to be a requirement –Needs discussion/analysis –Part of signaling is simplest, allow for other delivery Consistency of approach allows application to recursive ownership and notification –Developer/REIT owns 100 office parks. Each office park gets signal, distributes to tenants. –Tenants or office park manager can distribute to ESIs at all levels

17 MicroGrid Notes Each ParticipantOperator is a MicroGrid control access point (associated with MicroGrid ESI) Fit nested or unions of MicroGrids into the picture on slide 3 Notification to MicroGrid-contained participants has differing security/reliabilty requirements

18 Summary of Application of EI Signal notification paths have varying requirements Must be able to apply/compose additional configured solutions –Compose WS-Reliable Messaging –Compose WS-Security components –Compose other needed technologies (undetermined) Factor –Price Signals (with multiple delivery paths) –Reliability Signals (single secure and reliable path) –Environmental Signals (similar to Price) All need individual links to have specific characteristics –Non-repudiation, privacy, confirmed/signed source –Reliability, app-level or transport-level ACK –Probably the same at each level (for each Aggregator-Operator instance)