<?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: EnergyGauge® Summit Premier 3.15 Saves Energy Modelers Time</title>
	<atom:link href="http://blog.floridaenergycenter.org/echronicle/2008/11/energygauge%c2%ae-summit-premier-315-saves-energy-modelers-time/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.floridaenergycenter.org/echronicle/2008/11/energygauge%c2%ae-summit-premier-315-saves-energy-modelers-time/</link>
	<description>A Newsletter of the Florida Solar Energy Center</description>
	<lastBuildDate>Fri, 03 Sep 2010 14:14:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nathan Beckman</title>
		<link>http://blog.floridaenergycenter.org/echronicle/2008/11/energygauge%c2%ae-summit-premier-315-saves-energy-modelers-time/comment-page-1/#comment-2416</link>
		<dc:creator>Nathan Beckman</dc:creator>
		<pubDate>Wed, 10 Mar 2010 04:16:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.floridaenergycenter.org/echronicle/?p=177#comment-2416</guid>
		<description>I agree with GravyCrank.  The data entry is a lot more difficult than it needs to be.  It seems to me the people writing the program have little  day to day experience in the arch / HVAC design process of a building.

1) The explanantion what the program is outputing is non-existant.  It would be nice to have an explanation of what energy cost are grouped into each category so the designer can make sense out of the results.
1a)  The results should show you what the baseline systems are, so deviations from the baseline are apparent.
2) Why does the lighting source and number of fixtures matter in the lighting calculations for each space?  It would be better if the only thing required for input was the total amount of lighting wattage for that particular space.  All of the other input just adds data input time.
3) A lot of the HVAC system types are the same.  A better description of each system is necessary.  
4) All of building envelope input should be in square footage and not width by height.
5) The building materials and constructs format is terrible.  I have never used a predefined wall or roof.  I not sure where these come from but the predefined walls do not even come close to modeling current construction practices in South Florida.
6) There should be a 100% Oustide air system type.
7) In general the program is trying to do more than is necessary to show code compliance.  I am for straight prescirptive measure to show energy code compliance.  This would take a lot of lying out of the game and code officals will be able to catch people tying to skirt by the energy code.  The current code officals have no idea what this sheet is printing and they are not going to see if you entered the data right.
8) I doubt any building has been accurately modeled with this software.</description>
		<content:encoded><![CDATA[<p>I agree with GravyCrank.  The data entry is a lot more difficult than it needs to be.  It seems to me the people writing the program have little  day to day experience in the arch / HVAC design process of a building.</p>
<p>1) The explanantion what the program is outputing is non-existant.  It would be nice to have an explanation of what energy cost are grouped into each category so the designer can make sense out of the results.<br />
1a)  The results should show you what the baseline systems are, so deviations from the baseline are apparent.<br />
2) Why does the lighting source and number of fixtures matter in the lighting calculations for each space?  It would be better if the only thing required for input was the total amount of lighting wattage for that particular space.  All of the other input just adds data input time.<br />
3) A lot of the HVAC system types are the same.  A better description of each system is necessary.<br />
4) All of building envelope input should be in square footage and not width by height.<br />
5) The building materials and constructs format is terrible.  I have never used a predefined wall or roof.  I not sure where these come from but the predefined walls do not even come close to modeling current construction practices in South Florida.<br />
6) There should be a 100% Oustide air system type.<br />
7) In general the program is trying to do more than is necessary to show code compliance.  I am for straight prescirptive measure to show energy code compliance.  This would take a lot of lying out of the game and code officals will be able to catch people tying to skirt by the energy code.  The current code officals have no idea what this sheet is printing and they are not going to see if you entered the data right.<br />
 <img src='http://blog.floridaenergycenter.org/echronicle/wp-includes/images/smilies/icon_cool.gif' alt='8)' class='wp-smiley' /> I doubt any building has been accurately modeled with this software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://blog.floridaenergycenter.org/echronicle/2008/11/energygauge%c2%ae-summit-premier-315-saves-energy-modelers-time/comment-page-1/#comment-2208</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Wed, 23 Sep 2009 07:57:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.floridaenergycenter.org/echronicle/?p=177#comment-2208</guid>
		<description>This post is looking very informative. It makes people aware from different type of constructions.</description>
		<content:encoded><![CDATA[<p>This post is looking very informative. It makes people aware from different type of constructions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GravyCrank</title>
		<link>http://blog.floridaenergycenter.org/echronicle/2008/11/energygauge%c2%ae-summit-premier-315-saves-energy-modelers-time/comment-page-1/#comment-2181</link>
		<dc:creator>GravyCrank</dc:creator>
		<pubDate>Thu, 17 Sep 2009 16:45:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.floridaenergycenter.org/echronicle/?p=177#comment-2181</guid>
		<description>FLARES is approaching an effective program.  This one needs work:

1.  More constructs for common wall and roof types would be useful.  Not sure why so many constructs for stone are in here.  I know we can make our own constructs, but overall statewide more accurate modeling would occur with common constructs in the master library.  Many folks without college engineering are using this program.  

2.  Ditto for master library materials.  More common insulation types would be helpful.

3.  An on-the-spot help button would be helpful, like on FLARES

4.  The questions asking for fan watts per CFM cause undue calculations.   How about asking for supply air, outdoor air, and fan horsepower?  Lets have the program do these calculations so users can concentrate on inputs.

5.  The efficiency entry for air conditioning is bulky.  For instance, if I have given the information that the system is an air cooled split system under 5 tons, why do I still have to choose between SEER and EER?  

6.  Many spaces are not rectangular.  It would be nice to have the option to enter total square feet as an option to length and width.  Same with roofs and floors and walls.

7.  The door input screen defaults to non-swinging.  Most doors are swinging type and that should be the default.

8.  Tilt angle for roofs would be easier to input if asked for as a pull down menu for 12:x pitches.

9.  Perhaps you are bound by code, but lighting catagories for areas that many buildings have would be great - break rooms, clubrooms, cyber rooms, inactive stairs, apartments

In general, many little annoyances make this program hard to use.  User interface overhaul is required to make this an effective tool.</description>
		<content:encoded><![CDATA[<p>FLARES is approaching an effective program.  This one needs work:</p>
<p>1.  More constructs for common wall and roof types would be useful.  Not sure why so many constructs for stone are in here.  I know we can make our own constructs, but overall statewide more accurate modeling would occur with common constructs in the master library.  Many folks without college engineering are using this program.  </p>
<p>2.  Ditto for master library materials.  More common insulation types would be helpful.</p>
<p>3.  An on-the-spot help button would be helpful, like on FLARES</p>
<p>4.  The questions asking for fan watts per CFM cause undue calculations.   How about asking for supply air, outdoor air, and fan horsepower?  Lets have the program do these calculations so users can concentrate on inputs.</p>
<p>5.  The efficiency entry for air conditioning is bulky.  For instance, if I have given the information that the system is an air cooled split system under 5 tons, why do I still have to choose between SEER and EER?  </p>
<p>6.  Many spaces are not rectangular.  It would be nice to have the option to enter total square feet as an option to length and width.  Same with roofs and floors and walls.</p>
<p>7.  The door input screen defaults to non-swinging.  Most doors are swinging type and that should be the default.</p>
<p>8.  Tilt angle for roofs would be easier to input if asked for as a pull down menu for 12:x pitches.</p>
<p>9.  Perhaps you are bound by code, but lighting catagories for areas that many buildings have would be great &#8211; break rooms, clubrooms, cyber rooms, inactive stairs, apartments</p>
<p>In general, many little annoyances make this program hard to use.  User interface overhaul is required to make this an effective tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: seattle architect</title>
		<link>http://blog.floridaenergycenter.org/echronicle/2008/11/energygauge%c2%ae-summit-premier-315-saves-energy-modelers-time/comment-page-1/#comment-2171</link>
		<dc:creator>seattle architect</dc:creator>
		<pubDate>Fri, 04 Sep 2009 14:49:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.floridaenergycenter.org/echronicle/?p=177#comment-2171</guid>
		<description>Seattle architects tend to have some of the most innovative sustainable design and green building projects in the country.  The rest of us should follow their example - The list is long!  This architect is one of them you should see..

http://www.seattle-architects.com/


There are many others...the AIA site from Seattle has more info. if you need it.  thanks.</description>
		<content:encoded><![CDATA[<p>Seattle architects tend to have some of the most innovative sustainable design and green building projects in the country.  The rest of us should follow their example &#8211; The list is long!  This architect is one of them you should see..</p>
<p><a href="http://www.seattle-architects.com/" rel="nofollow">http://www.seattle-architects.com/</a></p>
<p>There are many others&#8230;the AIA site from Seattle has more info. if you need it.  thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Me</title>
		<link>http://blog.floridaenergycenter.org/echronicle/2008/11/energygauge%c2%ae-summit-premier-315-saves-energy-modelers-time/comment-page-1/#comment-1869</link>
		<dc:creator>Me</dc:creator>
		<pubDate>Mon, 16 Mar 2009 17:23:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.floridaenergycenter.org/echronicle/?p=177#comment-1869</guid>
		<description>It sucks. Should not have been released yet. Way more difficult than previous version.</description>
		<content:encoded><![CDATA[<p>It sucks. Should not have been released yet. Way more difficult than previous version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fuel Saving Hydrogen</title>
		<link>http://blog.floridaenergycenter.org/echronicle/2008/11/energygauge%c2%ae-summit-premier-315-saves-energy-modelers-time/comment-page-1/#comment-498</link>
		<dc:creator>Fuel Saving Hydrogen</dc:creator>
		<pubDate>Thu, 18 Dec 2008 05:05:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.floridaenergycenter.org/echronicle/?p=177#comment-498</guid>
		<description>&lt;strong&gt;Fuel Saving Hydrogen...&lt;/strong&gt;

I couldn&#039;t understand some parts of this article, but I guess I just need to check some more resources regarding this, because it sounds interesting....</description>
		<content:encoded><![CDATA[<p><strong>Fuel Saving Hydrogen&#8230;</strong></p>
<p>I couldn&#8217;t understand some parts of this article, but I guess I just need to check some more resources regarding this, because it sounds interesting&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
