<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:st1="urn:schemas-microsoft-com:office:smarttags" 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 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";
mso-believe-normal-left:yes;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<![if mso 9]>
<style>
p.MsoNormal
{margin-left:3.0pt;}
</style>
<![endif]>
</head>
<body lang=EN-US link=blue vlink=blue style='margin-left:3.0pt;margin-top:3.0pt;
margin-right:3.0pt;margin-bottom:.75pt'>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Ellen,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>We have bumped into bugs and hiccups doing
Title 24 compliance runs in eQUEST too. Two suggestions that I can offer:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>If the compliance run completes normally
and shows savings over the standard but yet the building inexplicably does not
comply, try reviewing the hours out of throttling range in the standard run. It’s
likely that the system in your base model meets the loads fine with few hours
out of throttling but that the model of the standard building has excessive
hours out of throttling range due to the translation of the ruleset. Make sure
to select the option for full reporting before you start the compliance run so that
you can identify where the loads are not met (SS-R is a good place to look). You
can also open the .INP for the standard run, create a new .PD2 for it, and then
dig into what the underlying problem is. The trick is to change your original
model so that it still reflects your proposed building, but also limits the
hours of throttling in the standard run. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Also, look for the .CAL file that is
generated when you do T24 compliance runs in eQUEST. If there are errors, they
should be reported in there. Supposedly there is a toggle in one of the INI
files in the eQUEST program file directory that can increase the level of reporting
to this .CAL file too.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Best of luck.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hwakong <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='margin:0in;margin-bottom:.0001pt;
text-align:center'><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
bldg-sim-bounces@lists.onebuilding.org
[mailto:bldg-sim-bounces@lists.onebuilding.org] <b><span style='font-weight:
bold'>On Behalf Of </span></b>Ellen Franconi<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, January 24, 2008
9:21 AM<br>
<b><span style='font-weight:bold'>To:</span></b> Bldg-sim@lists.onebuilding.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [Bldg-sim] Title-24
modeling w/ eQUEST</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>We haven't had
much success using the Title-24 wizard within eQUEST. We get errors that we
can't track that prevent the proposed design from demonstrating compliance.
We've gotten simple buildings to work but none of the more complex ones that we
usually construct. While we have contacted the eQUEST developers, we have not
received any support to aid us in trouble shooting the errors. As a result, we
have had to build a second model in EnergyPro so that we could demonstrate
compliance.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>What has other
people's experience been? Have other firms also had problems with the Title-24
wizard? If so, do you use eQUEST in conjunction with EnergyPro? Do
you do all the design assistance analysis AND the compliance analysis in
EnergyPro? And then for CA projects there may also be a need to do
Savings-By-Design calculations? Are people running into the same problem there
with eQUEST?<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>Thanks for any
insights you can provide.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>Ellen<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>Ellen Franconi,
Ph.D., LEED AP<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>Energy Analysis
Group Manager<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>Architectural
Energy Corporation<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><st1:Street w:st="on"><st1:address
w:st="on"><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:
Tahoma'>2540 Frontier Avenue</span></font></st1:address></st1:Street><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><st1:place w:st="on"><st1:City
w:st="on"><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:
Tahoma'>Boulder</span></font></st1:City><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>, <st1:State w:st="on">CO</st1:State>
<st1:PostalCode w:st="on">80301</st1:PostalCode></span></font></st1:place><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>tel. 303-444-4149<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>fax 303-444-4303<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'><a
href="mailto:efranconi@archenergy.com">efranconi@archenergy.com</a><o:p></o:p></span></font></p>
</div>
</div>
</body>
</html>