[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [energyinterop] Groups - DR Programs (DR-Program-DRRC_20090914SK edits.doc) uploaded
OpenADR defines an architecture with a DRAS server in the
cloud. The DRAS server can send rich info to the smart DRAS client, or more
DLC-like info (I may be off base here, please correct) to the simple clients.
The simple client can't think so well, so the server does more thinking and
directing. It seems there is a full spectrum of communications that span the
collaborative pure price approach to the "shut off the water heater"
DLC approach. We are defining the information and messages for energy
interoperation at the facility interface (no?). We have said that we would
include the CA DR program messages that form the meat of OpenADR--that is, "go
to level 2, start time, duration". We are not specifying how to talk to a
specific device to make it act in a certain way, as is the case for SEP--we are
not defining messages for raising the set-point temp, shutting off the water
heater, etc. That is, such commands are DLC, and the EMS handles that (even if,
as in the case of AMI, the EMS is in the utility backend system). So, EIX
(Energy Info eXchange protocol) will not compete with SEP for DLC, although SEP
has price communications. A utility can keep the current “SEP from the back-end”
approach, or stick an ESI on the building that understands EIX messages and
then translates that to SEP commands (assuming that is in use on the HAN). Does this make sense? Thanks, -----Original Message----- Thanks Toby. I totally agree. With kind regards, ******************************** Michel Kohanim, C.E.O Universal Devices, Inc. (p) 818.631.0333 (f) 818.436.0702 http://www.universal-devices.com ******************************** -----Original Message----- From: Considine, Toby (Campus Services IT)
[mailto:Toby.Considine@unc.edu] Sent: Wednesday, December 02, 2009 10:59 AM To: 'energyinterop@lists.oasis-open.org' Subject: RE: [energyinterop] Groups - DR Programs
(DR-Program-DRRC_20090914 SK edits.doc) uploaded I think the simple answer is no. Legacy systems work with
legacy communications. Some people will have a temporary business of putting
shims on old systems, whether they worked with OpenADR, or with SEP 1.0, or
even with a 3rd party such as ENERNOC. Our work should be informed by legacy systems, but not
limited or dictated by them... tc "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 Phone: (919)962-9073 http://www.oasis-open.org blog: www.NewDaedalus.com -----Original Message----- From: Michel Kohanim
[mailto:michel@universal-devices.com] Sent: Wednesday, December 02, 2009 1:36 PM To: energyinterop@lists.oasis-open.org Subject: RE: [energyinterop] Groups - DR Programs
(DR-Program-DRRC_20090914 SK edits.doc) uploaded Hi Sila, thanks. That makes perfect sense. The next question is the scope of our efforts: do we
foresee supporting vintage systems? With kind regards, ******************************** Michel Kohanim, C.E.O Universal Devices, Inc. (p) 818.631.0333 (f) 818.436.0702 http://www.universal-devices.com ******************************** --------------------------------------------------------------------- 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
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]