OpenADR SRS Draft 1
Review
UCAIug OpenADR Taskforce
Face to Face Meeting
May 6th, 2010
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
2
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
3
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)
4
Business Process Flow Using Business Role
act ADR Ov erv iew
Load Serving Entity
DR Administration
Create DR Program
Post DR Event / Reconciliation
Register Customer for a
DR Program
Billing
Administer DR Program
includes Register,
Update, Remove from
Program.
Start
Electicity Consumer
Register for a DR Program
Bill
Demand Response Provider
Billing
Register for a DR Program
Energy Service Provider
Register Customer for a
DR Program
DR Bidding
Bid to Supply or Buy
DR Asset Owner
Register DR
Resource/Asset
DR Controlling Entity
DR Resource/Asset
Registration
Request for Bids
Accept/Rev ise/Rej ect Bid
Execute DR Ev ent
Varies by Market
DR Asset/Resource
Opt In/Out and
Acknow ledge
Meter Read
5
Business Process Flow Using Logical Components
act ADR Ov erv iew
DR Controlling Entity
DR Administration
Register Customer for a
DR Program
Post DR Event / Reconciliation
Execute DR Ev ent
DR Resource/Asset
Registration
Billing
Start
Electicity Consumer
Bill
Register for a DR Program
DR Asset Owner
Administer DR Program
includes Register,
Update, Remove from
Program.
DR Bidding
Register DR
Resource/Asset
Bid to Supply or Buy
DR Asset/Resource
Request for Bids
Accept/Rev ise/Rej ect Bid
Opt In/Out and
Acknow ledge
Meter Read
6
Logical Components – Data Exchange
dfd Domain Diagram
Electricy Consumer
DR Asset(s)
DR Resource
Register for DR Program
Execute Event
Execute Event
1..*
DR Asset Owner
Meter Read for Reconcilliation
Register DR Resource/Asset
DR Controlling
Entity
Bidding
DR Dispatch
System and Market
Operator
7
DR Controlling Entity
Instantiates 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
8
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
9
Example of Flexibility in Application of
Concept
DR
Controlling
Entity
• Can think of DR
Controlling Entity as
VEN-REC?
10
Integration Services
• Critical Deliverable to Begin Data Model
• Review from SRS Section 3.2.2.2
– Scope
– Priority
– Traceability
11