[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [energyinterop] RE: Initial Port of OpenADR to EnergyInterop
Hi David, I really do wish we could iron
out terminology. When you say “in my mind”, does the definition you
provided is your personal view? Also, when you mention
firewalling and routing to appropriate box, are you talking at the IP
addressing level? If not, what’s the addressing scheme? Have we agreed on
it? With kind regards, ******************************** Michel Kohanim,
C.E.O Universal
Devices, Inc. (p)
818.631.0333 (f)
818.708.0755 http://www.universal-devices.com ******************************** From: Holmberg, David
[mailto:david.holmberg@nist.gov] Toby, Sharon, I believe Ed’s reference
to BACnet was to the use of BACnet web services in the OpenADR spec as one of
the options between DRAS and DRAS Client. Thus BACnet WS is in scope, but
otherwise I agree. So, what is the ESI? In my mind it is an external gateway
for access to the facility network, often owned by the IT dept (if there is
one), with the purpose of firewalling and routing to appropriate box on the
inside (like the EMS). David From: Dinges, Sharon
[mailto:sdinges@trane.com] 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] 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
From: Edward Koch
[mailto:ed@akuacom.com] 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.. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]