<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
i typically just do screen caps when setting up my baseline model.
it's quick, painless, and makes mothers very happy ... and is done
early ...<br>
<br>
yeah, one would think there would be a details of hvac systems
output report showing the direct inputs, but there's not. unless
you're good at creating custom reports & can create one that
pulls input data from the hvac section? if that's even data
possible for equest to pull ...<br>
<br>
or you could parse the info from the .sim file keying on just the =
system name, heat-sizing-rati & cool-sizing-rati variables.<br>
<br>
"PSZ-1" = SYSTEM <br>
TYPE = PSZ<br>
HEAT-SOURCE = FURNACE<br>
ZONE-HEAT-SOURCE = NONE<br>
BASEBOARD-SOURCE = NONE<br>
SIZING-RATIO = 1.15<br>
HEAT-SIZING-RATI = 1.25<br>
COOL-SIZING-RATI = 1.15<br>
etc ........<br>
<br>
<br>
On 4/10/13 1:04 PM, Nick Caton wrote:
<blockquote
cite="mid:ECDF361A89E5FA479BE7E64C658B520512532A85@SANDBINC4.sbi.smithboucher.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (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]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 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:"Stylus BT";
panose-1:2 14 4 2 2 2 6 2 3 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 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.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";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
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;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal">Hi folks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have a seemingly simple LEED comment
which has been causing me to chase my tail this afternoon. I
feel like this should be really easy to document in a
crystal-clear fashion, but I must be missing something:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>The Task: <o:p></o:p></b></p>
<p class="MsoNormal">Document with clarity that the baseline
system cooling and heating capacities are using the 1.15 and
1.25 (respectively) capacity sizing ratios as prescribed in
90.1 Appendix G.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Intuitively, I have a sense we should be
able to simply and directly reference one or a series of the
*.SIM reports to substantiate the systems are oversized by the
appropriate factors. After spending some time digging through
the reports and associated help documentation however, I’m
empty-handed and do not think the actual ratio inputs
(COOL-SIZING-RATI / HEAT-SIZING-RATI) are reported.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Further, I tried <u>deriving</u> the
oversizing ratio between a system’s annual PEAK (re: report
SS-P) and calculated system capacity (report SV-A) as
reported… but the math doesn’t quite work out! It’s the right
ballpark, but I don’t think I can write the difference off as
a rounding error…<o:p></o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>The Solution(?): <o:p></o:p></b></p>
<p class="MsoNormal">For now, I can just provide screen grabs
illustrating the inputs in eQuest’s spreadsheet view with
relative ease, but if this is possible to document by
assembling/referencing one or more additional reports for
future models I’d prefer to adopt that in practice and avoid
the same question down the road. If I have some
misunderstanding or new nuance to learn about the reports that
would be worthwhile as well =).<i><o:p></o:p></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Any suggestions/experience?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks in advance!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">~Nick<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><img
id="Picture_x0020_1"
src="cid:part1.05090907.05080708@gmail.com"
alt="cid:489575314@22072009-0ABB" height="37" width="119"></span><b><span
style="font-family:"Stylus
BT","sans-serif";color:#2D4D5E"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-family:"Stylus
BT","sans-serif";color:#2D4D5E"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-size:12.0pt;font-family:"Stylus
BT","sans-serif";color:#2D4D5E">NICK CATON,
P.E.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900">SENIOR
ENGINEER<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;color:#2D4D5E">Smith & Boucher
Engineers</span><span
style="font-size:7.5pt;font-family:"Times New
Roman","serif";color:#CC9900"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;color:#2D4D5E">25501 west valley
parkway, suite 200<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;color:#2D4D5E">olathe, ks 66061<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;color:#2D4D5E">direct 913.344.0036<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;color:#2D4D5E">fax 913.345.0617<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a
moz-do-not-send="true" href="www.smithboucher.com"
title="blocked::www.smithboucher.com"><span
style="font-size:10.0pt;color:blue">www.smithboucher.com</span></a></span><u><span
style="font-size:10.0pt;color:blue">
</span></u><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Equest-users mailing list
<a class="moz-txt-link-freetext" href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a>
To unsubscribe from this mailing list send a blank message to <a class="moz-txt-link-abbreviated" href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a>
</pre>
</blockquote>
<br>
</body>
</html>