1 / 8

Interaction for EITC

This document focuses on the interaction model for event distribution among participants and aggregators in the context of MicroGrids. It highlights the recursive pairwise relationships and the implementation of aggregator interfaces for effective communication. The importance of security, reliability, and notification paths tailored to each interoperation link is emphasized. Key issues regarding ISO standards, delivery requirements, and the nuances of price communication are examined, with the aim of developing a consistent approach to event distribution.

jason-forbes
Télécharger la présentation

Interaction for EITC

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. Interaction for EITC W. T. Cox 2010-05-04 Draft 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 DREvents Aggregator- Operator Signals and responses Participant- Operator

  3. A Slice Through the Notification Tree DREvent Participant- Operator Participant- Operator Participant- Operator Participant- Operator Aggregator- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator ISO Aggreg Agg Client Industrial Pk Tenant

  4. Protection and Reliability Less Protected More Protected Fewer Per Layer More Per Layer DREvent Participant- Operator Participant- Operator Participant- Operator Participant- Operator Aggregator- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator Participant- Operator ISO Aggreg Agg Client Industrial Pk Tenant

  5. ISO Issues and Resistance • 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 ISOs • Price quote/closing price stream is important and done today • EMIX as the price quote stream

  6. Participant/Real Estate Notes • Want a way to distribute events to tenants or separate owned properties • Price distribution appears to be a requirement • Needs discussion/analysis • Consistency of approach allows application to recursive ownership and notification

  7. MicroGrid Notes • Each ParticipantOperator is a MicroGrid control access point (a la ESI) • Fit nested/overlapping MicroGrids into the picture on slide 3 • Notification to MicroGrid-contained participants has differing security/reliabilty requirements

  8. 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)

More Related