1 / 3

OpenADR v2.0 DBP

OpenADR v2.0 DBP. Rish Ghatikar. Existing v1.0 DBP Sequence. Utility Information System/ OpenADR Server/ VTN. Participant/ Customer. Revise Bids (H2M): If not revised during the RFB window, the standing bids are automatically submitted by the OpenADR server (Auto-bid, auto-shed).

kalyca
Download Presentation

OpenADR v2.0 DBP

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 v2.0 DBP Rish Ghatikar

  2. Existing v1.0 DBP Sequence Utility Information System/ OpenADR Server/ VTN Participant/ Customer Revise Bids (H2M): If not revised during the RFB window, the standing bids are automatically submitted by the OpenADR server (Auto-bid, auto-shed) Submit Standing Bid (H2M) Request for Bids/ Notification (M2H) OpenADR Client/ VEN Bid Acceptance/ Automation Event (M2M) OpenADR v1.0: DR Event (EventState)

  3. OpenADR v2.0 DBP Sequence: Potential Utility Information System/ OpenADR Server/ VTN Aggregator/Participant/ Third-party/ VTN Customer (1-n)/ VEN Submit Standing Bid (H2M) Revise Bids (H2M) Request for Bids (M2H) Submit Standing Bid (M2M: Auto-bid, auto-shed) OpenADR Client/ VEN Bid Acceptance/ Event (M2M) DR Event (M2M) OpenADR v2.0: EiEvent OpenADR v2.0: EiEvent OpenADR v2.0 Standardization Needed: Another VTN may break the customer link if not standardized, which a DR service-provider then need to rely upon

More Related