Re: [energyinterop] RE: Initial Port of OpenADR to EnergyInterop

[Girish Ghatikar <GGhatikar@lbl.gov>]

Toby and Sharon,

That's the key distinction to make between intra-systems (EMCS or 
controls internal to buildings) and inter-systems (ESI and similar 
interfaces external to buildings) where inter-systems could use Web 
services (i.e., XML) and intra-systems would use the existing 
communication protocols (e.g., BACnet, Lon, etc.). This distinction will 
make the OpenADR communication protocol-independent and enable legacy 
systems and retrofits compatible. That's what we're doing currently with 
OpenADR.

Thanks,
-Rish

Dinges, Sharon wrote:
> Toby,
> I believe this is a fair assessment. The interactions between the EMS 
> and the external ESI are more appropriately communicated using XML and 
> web services.
> Then, at the EMS level, the systems would communicate using BACnet, 
> LonWorks, OPC, HAN, DALI, etc.
> Regards,
> Sharon
>
> ------------------------------------------------------------------------
> *From:* Considine, Toby (Campus Services IT) 
> [mailto:Toby.Considine@unc.edu]
> *Sent:* Monday, July 20, 2009 20:40
> *To:* 'Edward Koch'; 'energyinterop@lists.oasis-open.org'
> *Subject:* [energyinterop] RE: Initial Port of OpenADR to EnergyInterop
>
> In terms of the smart grid diagrams, outside communications should be 
> with Energy Services Interface (ESI), which is something different 
> than the Energy Management System (EMS). Makers of BACnet, LON, HAN, 
> DALI, et al will each figure out what the middle layer is. Oft times, 
> the enterprise will be in between the ESI and any EMS. It certainly 
> will be in any industrial environment…
>
> BACNET, LON and friends are out of scope…
>
> ------------------------------------------------------------------------
>
> "A man should never be ashamed to own that he has been in the wrong, 
> which is but saying ... that he is wiser today than yesterday." -- 
> Jonathan Swift
>
> ------------------------------------------------------------------------
>
> Toby Considine
>
> Chair, OASIS oBIX TC
> Facilities Technology Office
> University of North Carolina
> Chapel Hill, NC
>
> 	
>
> 	
>
> Email: Toby.Considine@ unc.edu <mailto:Toby.Considine@fac.unc.edu>
> Phone: (919)962-9073
>
> http://www.oasis-open.org
>
> blog: www.NewDaedalus.com
>
> *From:* Edward Koch [mailto:ed@akuacom.com]
> *Sent:* Monday, July 20, 2009 8:41 PM
> *To:* Considine, Toby (Campus Services IT); 
> 'energyinterop@lists.oasis-open.org'
> *Subject:* RE: Initial Port of OpenADR to EnergyInterop
>
> Enclosed is a pass on the document that Toby sent out. I mostly tried 
> to answer some of his questions and added some comments of my own.
>
> Here are some general comments:
>
> It looked like there is some material missing at the end.
>
> Clearly there needs to be some verbiage added concerning security 
> requirements.
>
> There needs to be some meat added for the interaction and data models. 
> Perhaps adding in some of the diagrams from the spec will fulfill this 
> requirement.
>
> We need to give some thought to what we are going to do with the 
> various interfaces, i.e. BACnet versus REST versus SOAP, etc.
>
> -ed koch
>
> The information contained in this message is privileged and intended 
> only for the recipients named. If the reader is not a representative 
> of the intended recipient, any review, dissemination or copying of 
> this message or the information it contains is prohibited. If you have 
> received this message in error, please immediately notify the sender, 
> and delete the original message and attachment..

-- 
Rish Ghatikar
Lawrence Berkeley National Laboratory
1 Cyclotron Road, MS: 90-4000, Berkeley, CA 94720
GGhatikar@lbl.gov | +1 510.486.6768 | +1 510.486.6996 [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].