RE: [energyinterop] Is silence consent?

["Considine, Toby (Campus Services IT)" <Toby.Considine@unc.edu>]

A couple people asked for examples.

See chapter 4 of the last draft

tc


"If flies are allowed to vote, how meaningful would a poll on what to have for dinner be, and what would be on the menu?" -  Unknown

Toby Considine
Chair, OASIS oBIX Technical Committee
Co-Chair, OASIS Technical Advisory Board
Facilities Technology Office
University of North Carolina
Chapel Hill, NC
  
Email: Toby.Considine@ unc.edu
Phone: (919)962-9073 
http://www.oasis-open.org 
blog: www.NewDaedalus.com


-----Original Message-----
From: Girish Ghatikar [mailto:GGhatikar@lbl.gov] 
Sent: Monday, March 01, 2010 11:18 AM
To: Toby.Considine@gmail.com
Cc: energyinterop@lists.oasis-open.org
Subject: Re: [energyinterop] Is silence consent?

Toby,

Prior to consenting, I think we will need to elaborate and look at specific scenarios so that the opportunities are well articulated. Some examples would help (existing implementations vs. future considerations). My other thoughts below:


Toby Considine wrote:
>
> No comments on the proposal to re-cast enegyinterop into
>
>  
>
> (1)    Contracts offered, executed, mandatory (DR) -
>
Rish: Look into what could be used/needed above and beyond wat already exists in OpenADR v1.0. Need to understand the dynamics of the terminologies and concepts, which needs to be consistent.
>
> (2)    Bidding
>
> (2a) Block bidding
>
Rish: Not sure what this means and why are we considering only block bidding. Bidding should be generic with details on specific applications.
>
> (3)    Price Look-ahead
>
Rish: Do you mean price forecasting? If yes, then I think it's outside of EI scope. Our focus should be standardized DR (and DER) signals to/from the facility/ESI.
>
> Is this all the services? Is #3really pert of EMIX?
>
Rish: I would think so.
>
>  
>
> Separate specifications for instantiations of energyinterop
>
> -          WS
>
> -          FIX
>
> -          CAP
>
>  
>
> With this group probably only doing (1). (Note: CAP is inherently a 
> partial set of services, and is already used in soma CA markets, so 
> hat one might be straightforward)
>
Rish: Need to understand this better - Is FIX and CAP a technology or a communication protocol or information transmission medium (application layer)? Need to look at their relation to OSI model?

Thanks,
Rish
>
>  
>
>  
>
>  
>
> ----------------------------------------------------------------------
> --
>
> "Energy and persistence conquer all things." -- Benjamin Franklin
>
> ----------------------------------------------------------------------
> --
>
> Toby Considine
> TC9, Inc
>
> OASIS Technical Advisory Board
> TC Chair: oBIX & WS-Calendar
>
> TC Editor: EMIX, EnergyInterop
>
> 	
>
>   
>
> 	
>
> Email: Toby.Considine@gmail.com
>
> Phone: (919)619-2104
>
> http://www.tcnine.com/
>
> blog: www.NewDaedalus.com
>
>  
>
>  
>

--
Rish Ghatikar
Lawrence Berkeley National Laboratory
1 Cyclotron Road, MS: 90-3111, Berkeley, CA 94720 GGhatikar@lbl.gov | +1 510.486.6768 | +1 510.486.4089 [fax]

This email is intended for the addressee only and may contain confidential information and should not be copied without permission. If you are not the intended recipient, please contact the sender as soon as possible and delete the email from computer[s].



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php