1 / 11

OpenADR SRS Draft 1 Review

This document reviews OpenADR System Requirements Specification (SRS) focusing on integration components, services definition, and business processes for scalable energy resource management. It covers data modeling, semantic interoperability, and security aspects.

conniei
Download Presentation

OpenADR SRS Draft 1 Review

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. OpenADR SRS Draft 1 Review UCAIug OpenADR Taskforce Face to Face Meeting May 6th, 2010

  2. OpenADR SRS Draft 1 Review • Objectives & Final Deliverables • System Requirements Specification • Per SG Systems SRS Guidelines • Main focus is Integration Components • Services Definition • Artifacts to define payload • XSD’s and Web Services

  3. SRS Components • Architecture Views (Components) • Business (Draft 1) • Use Case Driven (largely by these) • Open ADR Functional Requirements and Use Case Document (OpenSG) • Requirements Specifications for Retail Standard DR Signals - for NIST PAP09 • Defines Integration Requirements and Business Services • Data (Draft 2) • Technical requirements on how data the is modeled • Ensure Semantic Interoperability • Application & Technical (Draft 3) • Security • Service Patterns

  4. Draft Review Objectives • Confirm Scope & Structure • Business Processes • Business Process Flow • Business Roles • Business Processes • Integration Services • Logical Components • Entities that exchange information to carry out the business processes and implement the use cases • List of Services • Start from sequence diagrams in Use Case Documents • Map to sequence diagrams with Logical Components as actors • Define scope and priority (SRS Section 3.2.2.2)

  5. Business Process Flow Using Business Role

  6. Business Process Flow Using Logical Components

  7. Logical Components – Data Exchange

  8. DR Controlling EntityInstantiates the EPRI REC-VEN Concept?* • REC: Resource Energy Controller • Can receive and respond to messages. Examples: • Report what resources are available • Can effect changes in end use load/energy supply • Determine when to send specific grid messages to resources it manages • VEN: Virtual End Node • Generic reference to a logical load entity/device • Can manage DERs from a DR perspective * Concepts to enable advancement of Distributed Energy Resources: White Paper on DER, EPRI, Palo Alto, CA: 2010. 1020432

  9. Valid Configurations Building on REC-VEN Recursive Properties • All configurations appear identical from Grid perspective • Results in scalable, flexible, simple model that enables many possibilities for unforseen future configurations

  10. Example of Flexibility in Application of Concept • Can think of DR Controlling Entity as VEN-REC? DRControllingEntity

  11. Integration Services • Critical Deliverable to Begin Data Model • Review from SRS Section 3.2.2.2 • Scope • Priority • Traceability

More Related