<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:816729065;
mso-list-type:hybrid;
mso-list-template-ids:-471958890 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:38.25pt;
text-indent:-.25in;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hwakong,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>My experience with EnergyPro v5 is that the baseline
building is not correctly modeled. The envelope criteria are often applied
correctly, but HVAC-related metrics such as fan power are incorrectly
calculated. Compounding the problem are report-population errors; it is
sometimes impossible to tell if the simulation is correct but the auto-filled
report is wrong, or if the simulation and report are both wrong. I know
for certain that fan power is incorrect because it can be cross-checked with
the standard DOE2 SV-A reports in addition to the auto-filled LEED EAc1 report.
However, other baseline metrics such as those described in 90.1-2007 G3.1.3.4
(hot water reset schedule) and G3.1.3.8 (chilled water design temperatures) are
much more difficult to verify. I agree with your assessment that there is
virtually no control over the baseline and would add that there is insufficient
control over the proposed model, too. To summarize my major complaints:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoListParagraph style='margin-left:38.25pt;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]>Appendix G is incorrectly applied/report
mistakes are normal and there is no way to fix them<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:38.25pt;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]>There is very little customization available; it
is nowhere near the caliber of eQUEST, EnergyPlus, etc.<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:38.25pt;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]>There are no substantial self-training resources
(text- or video-based)<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:38.25pt;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]>The user group is focused almost exclusively on
issues pertaining to T24 compliance and T24 report errors<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:38.25pt;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]>EnergySoft’s support, while responsive, lacks
customer service skills and seems to operate under the assumption that all issues
lie with the user. I also suspect Support has misinformed me about EnergyPro’s
capabilities – I was told it can accurately model a DOAS with heat
recovery, but how can this be if it is built on the DOE2.1e engine? There’s
no way to verify accuracy if I cannot parse hourly reports. <o:p></o:p></p>
<p class=MsoNormal style='margin-left:2.25pt'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:2.25pt'>In short, the only value I see in
purchasing EnergyPro (outside of T24 compliance) is the incorporation of VRV
products. Once VRV is incorporated into other software, my firm plans to
discontinue using EnergyPro for the reasons above. <o:p></o:p></p>
<p class=MsoNormal style='margin-left:2.25pt'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:2.25pt'>Regards,<o:p></o:p></p>
<p class=MsoNormal style='margin-left:2.25pt'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:2.25pt'>Dakota Kelley<o:p></o:p></p>
<p class=MsoNormal style='margin-left:2.25pt'>Telios MEP Engineers<o:p></o:p></p>
<p class=MsoNormal style='margin-left:2.25pt'><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText>Message: 3<o:p></o:p></p>
<p class=MsoPlainText>Date: Tue, 30 Mar 2010 18:47:38 -0700<o:p></o:p></p>
<p class=MsoPlainText>From: Hwakong Cheng <hwakong@hotmail.com><o:p></o:p></p>
<p class=MsoPlainText>To: <bldg-sim@lists.onebuilding.org>,<o:p></o:p></p>
<p class=MsoPlainText> <bldg-rate@lists.onebuilding.org><o:p></o:p></p>
<p class=MsoPlainText>Subject: [Bldg-sim] 90.1 baseline in EnergyPro v5<o:p></o:p></p>
<p class=MsoPlainText>Message-ID:
<COL112-W57053ED36F1629FE11295DBC1E0@phx.gbl><o:p></o:p></p>
<p class=MsoPlainText>Content-Type: text/plain;
charset="windows-1252"<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>About a year ago, there was a posting asking about user
experiences with the new EnergyPro version 5, which is capable of automatically
generating a 90.1 baseline model, but there were no responses at the time. <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><a
href="http://www.energysoft.com/main/page_energypro_nonresidenital_modules.html">http://www.energysoft.com/main/page_energypro_nonresidenital_modules.html</a><o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Has anyone used it yet and have feedback to share on the
quality of its interpretation of Appendix G? I've used older versions of
EnergyPro before, but I'm specifically looking for feedback on the 90.1
compliance functionality. <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>My experience with EnergyPro for Title 24 compliance is
that, beyond specifying the details of your proposed building, there is very
limited control over how that is transformed in the baseline model and how the
T-24 ACM is interpreted (probably a good thing). It is what it is and there is
no way to explicitly edit the baseline model. eQUEST, on the other hand,
typically crashes during Title 24 compliance runs, but once it runs, there is
always the possibility of taking the auto-generated proposed and standard model
input files and "fixing them." <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Without the possibility of applying a human touch to the
interpretation of the nitty gritty in Appendix G and all of the particulars of
new building designs out there, I imagine it would be very difficult to create
a robust compliance engine that would work for every situation. On the other
hand, it might be nice not to *be able* to look at and, therefore, not *have
to* look at the details of the baseline building... but I haven't used it yet.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Thanks for any feedback.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Hwakong<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>