<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Difference between HEMS and HANS</title>
	<atom:link href="http://www.smartgridlibrary.com/2009/12/14/the-difference-between-hems-and-hans/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.smartgridlibrary.com/2009/12/14/the-difference-between-hems-and-hans/</link>
	<description>Information Generation &#124; Transmission &#124; Distribution</description>
	<lastBuildDate>Mon, 19 Jul 2010 21:15:26 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tomm Aldridge</title>
		<link>http://www.smartgridlibrary.com/2009/12/14/the-difference-between-hems-and-hans/comment-page-1/#comment-215</link>
		<dc:creator>Tomm Aldridge</dc:creator>
		<pubDate>Thu, 11 Feb 2010 19:18:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.smartgridlibrary.com/?p=344#comment-215</guid>
		<description>IP based home WiFi (802.11b/g/n) appears to me to be ubiquitous and secure (WEP, etc.) in the demographic that would be purchasing HEMS equipment.  To add additional networking technologies when low cost and highly capable WiFi is already in the home and easily integrated into new HEMS products allowing them to seamlessly join a secure network seems to add unnecessary complexity and cost.  I would like to see a cogent argument based on either cost or technical requirements as to why HEMS cannot converge on the same 802.11 network the home already uses.

Tomm Aldridge
Director, Energy Systems Research
Intel Labs</description>
		<content:encoded><![CDATA[<p>IP based home WiFi (802.11b/g/n) appears to me to be ubiquitous and secure (WEP, etc.) in the demographic that would be purchasing HEMS equipment.  To add additional networking technologies when low cost and highly capable WiFi is already in the home and easily integrated into new HEMS products allowing them to seamlessly join a secure network seems to add unnecessary complexity and cost.  I would like to see a cogent argument based on either cost or technical requirements as to why HEMS cannot converge on the same 802.11 network the home already uses.</p>
<p>Tomm Aldridge<br />
Director, Energy Systems Research<br />
Intel Labs</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Home Energy Management Systems: Sifting Through the Confusion &#171; PowerHouse dynamics</title>
		<link>http://www.smartgridlibrary.com/2009/12/14/the-difference-between-hems-and-hans/comment-page-1/#comment-206</link>
		<dc:creator>Home Energy Management Systems: Sifting Through the Confusion &#171; PowerHouse dynamics</dc:creator>
		<pubDate>Fri, 22 Jan 2010 15:17:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.smartgridlibrary.com/?p=344#comment-206</guid>
		<description>[...] a recent blog posting, Christine Hertzog (Smart Grid Library) does a great job addressing the issue that, while the terms [...]</description>
		<content:encoded><![CDATA[<p>[...] a recent blog posting, Christine Hertzog (Smart Grid Library) does a great job addressing the issue that, while the terms [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Flusberg</title>
		<link>http://www.smartgridlibrary.com/2009/12/14/the-difference-between-hems-and-hans/comment-page-1/#comment-193</link>
		<dc:creator>Martin Flusberg</dc:creator>
		<pubDate>Thu, 24 Dec 2009 14:46:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.smartgridlibrary.com/?p=344#comment-193</guid>
		<description>Thanks for this posting!  There is definitely widespread confusion between HAN and HEMS.  The HAN term is regularly used to imply a system that actively manages energy use, which as you point out is not really the case.  In fact, it is unclear to me whether HANs actually exist as entities, or whether the term is really conceptual relating basically to a set of communications protocols.  HEMS from different vendors will use different protocols, including ZigBee® and Z-Wave®, as well as WiFi or Ethernet connections to the home network, but that is quite different from a stand-alone “HAN”.  Of course, there is a lot of talk about the goal of plug &amp; play between different vendor components, but we are still far from seeing that happen, even with the emerging standards.  I was also pleased to see you point out the limitations of in-home displays, which are also being heavily hyped.  Does telling the average consumer that they are currently using 2300 watts help them manage their energy use?  They really need to know where they are using electricity, whether that usage is reasonable, and what actions might lead to what level of savings.</description>
		<content:encoded><![CDATA[<p>Thanks for this posting!  There is definitely widespread confusion between HAN and HEMS.  The HAN term is regularly used to imply a system that actively manages energy use, which as you point out is not really the case.  In fact, it is unclear to me whether HANs actually exist as entities, or whether the term is really conceptual relating basically to a set of communications protocols.  HEMS from different vendors will use different protocols, including ZigBee® and Z-Wave®, as well as WiFi or Ethernet connections to the home network, but that is quite different from a stand-alone “HAN”.  Of course, there is a lot of talk about the goal of plug &amp; play between different vendor components, but we are still far from seeing that happen, even with the emerging standards.  I was also pleased to see you point out the limitations of in-home displays, which are also being heavily hyped.  Does telling the average consumer that they are currently using 2300 watts help them manage their energy use?  They really need to know where they are using electricity, whether that usage is reasonable, and what actions might lead to what level of savings.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
