<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 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: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:Verdana;
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:12.0pt;
font-family:"Times New Roman","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
{mso-style-priority:99;
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","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I understand the whole ‘nothing to hide’ mentality but I have a few cautions. While GBCI has been doing most reviews in house, I expect they still reserve the right to contract for review which opens the possibility that a submitted model could be forward to a direct competitor. On my first LEED submission the reviewers took issue with some of the modeling aspects, declared a lower savings percentage and made the project appeal. If the reviewers had the model in hand they might have “fixed it” themselves to determine the savings and not entertained any appeal. Since the USGBC will have utility bills from the first few years of a project’s life providing them with a model is just asking from them to use it for a third party M&V exercise on what your project really saved. These might be farfetched but why risk it, just send them the reports that they request and be done. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,<o:p></o:p></span></p><div><p class=MsoNormal style='text-autospace:none'><b><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";color:#5F574F'>Paul Riemer, PE, LEED AP BD+C</span></b><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:#5F574F'>Associate / Mechanical</span><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;font-family:"Verdana","sans-serif";color:#5F574F'>Direct: 612-465-7696</span><span style='font-size:8.5pt;font-family:"Verdana","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#5F574F'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-family:"Verdana","sans-serif";color:#C00000'>DUNHAM</span></b><span style='font-size:11.0pt;font-family:"Verdana","sans-serif";color:#C00000'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>James Hess<br><b>Sent:</b> Thursday, April 11, 2013 2:16 PM<br><b>To:</b> equest-users@lists.onebuilding.org<br><b>Subject:</b> Re: [Equest-users] Cooling/Heating Capacity Ratios - LEED Report?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>FYI, I never said that uploading the eQuest .inp and .pd2 files should be required, just that it should be considered, because it’s easier to upload these files to facilitate the review versus uploading 1000+ pages of inputs. It’s much faster to look at the actual model than reports, so I guess I don’t understand why submitting the models would be considered bad precedent. I have done that on every LEED project I have submitted, which is ~ 30 +/-.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>From another angle, if I was a reviewer, I would want the ability to be able to run the energy model to verify that the results being generated match the results in the EAp2 form.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Currently, I think there is a loophole here that could be exploited. One could easily submit a Table 1.4 spreadsheet and input reports that do not match the results in the EAp2 form, or the output reports. Submitting the actual energy modeling files closes this potential loophole because the inputs and results can be verified at the same time.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>That may be going too far, and this is basically all on the honor system I realize, but I think it would be a good idea.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><o:p> </o:p></b></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>JAH<o:p></o:p></b></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><o:p> </o:p></b></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><i>James A. Hess, PE, CEM, BEMP</i></b><br>Energy Engineer<br>TME, Inc.<br>Little Rock, AR<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Mobile: (501) 351-4667<o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Bishop, Bill<br><b>Sent:</b> Thursday, April 11, 2013 12:42 PM<br><b>To:</b> Nick Caton<br><b>Cc:</b> equest-users@lists.onebuilding.org<br><b>Subject:</b> Re: [Equest-users] Cooling/Heating Capacity Ratios - LEED Report?<o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Nick,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I agree with the others that the LEED reporting should be kept as simple as possible. I also agree with James Hansen that submitting model files sets a bad precedent.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regarding the autosizing of cooling capacity:<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I did two runs on a sample model – one with COOL-SIZING-RATI = 1.0 and one with 1.15, to confirm that the COOLING-CAPACITY shown on SV-A at 1.15 is in fact 115% of the capacity at 1.0 when the COOLING-CAPACITY is not specified.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I believe the reason that the autosized COOLING-CAPACITY as reported on SV-A is not matching the peak cooling load from SS-A (or SS-J) is that the correction factor from the COOL-CAP-FT curve is applied during the sizing routine. The peak cooling load is not likely to coincide with the rating conditions at which the curve is normalized. For instance, the DX-COOL-Cap-fEWB&OAT curve is normalized at 67F Ewb and 95Fdb OAT. The curve accounts for the fact that DX cooling capacity increases when the OAT decreases. If the OAT at peak cooling load is less than 95F, the autosized capacity will be less than the peak load. The COOL-CAP-FT curve causes the hourly cooling capacity to be higher at lower OAT.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Bill<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>William Bishop, PE, BEMP, LEED AP | Pathfinder Engineers & Architects LLP<o:p></o:p></b></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Senior Energy Engineer<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>134 South Fitzhugh Street Rochester, NY 14608<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>T: (585) 325-6004 Ext. 114 F: (585) 325-6005<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a href="mailto:wbishop@pathfinder-ea.com">bbishop@pathfinder-ea.com</a> <a href="http://www.pathfinder-ea.com/">www.pathfinder-ea.com</a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>P Sustainability – the forest AND the trees. P <o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> <a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a> [<a href="mailto:equest-users-bounces@lists.onebuilding.org">mailto:equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>Nick Caton<br><b>Sent:</b> Thursday, April 11, 2013 12:43 PM<br><b>To:</b> James Hess; <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br><b>Subject:</b> Re: [Equest-users] Cooling/Heating Capacity Ratios - LEED Report?<o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks fellas!<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I’ve done screengrabs often in the past and am comfortable that will satisfy the reviewer’s concerns in this case, it just bugs me that where I’m confident the inputs are correct, the output reports aren’t backing me up as expected… <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I’ve also tried summing together space peak loads from the LS reports for a given system (shaky proposition anyway as they occur at different times), and still cannot find the calculated sizing to line up with my input ratios. I guess this boils down to something I don’t understand yet about how the oversizing ratios are applied to arrive at the calculated system capacities... Further digging in the help files when I get time I suppose. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I don’t anticipate having a problem with this review, but if anyone can fill in the gaps that would be much appreciated =)!<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>~Nick<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>PS: I didn’t know others are uploading their entire models… In the reviewer’s shoes, I wonder if that makes any combination of specific reports/information look suspect in comparison?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><img border=0 width=119 height=37 id="_x0000_i1025" src="cid:image001.jpg@01CE36C2.66F09040" alt="cid:489575314@22072009-0ABB"><b><o:p></o:p></b></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><o:p> </o:p></b></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>NICK CATON, P.E.<o:p></o:p></b></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>SENIOR ENGINEER<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Smith & Boucher Engineers<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>25501 west valley parkway, suite 200<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>olathe, ks 66061<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>direct 913.344.0036<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>fax 913.345.0617<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a href="www.smithboucher.com">www.smithboucher.com</a><u> </u><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> <a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a> [<a href="mailto:equest-users-bounces@lists.onebuilding.org">mailto:equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>James Hess<br><b>Sent:</b> Thursday, April 11, 2013 10:52 AM<br><b>To:</b> <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br><b>Subject:</b> Re: [Equest-users] Cooling/Heating Capacity Ratios - LEED Report?<o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Same here regarding the screen shots, but I only provide if asked to specifically document something via review comments. On every submitted project, however, I always upload the eQuest .inp and .pd2 files so that the reviewers can just open the files and look at whatever they need to. That beats submitting reams of “input reports” which really isn’t practical. I’m assuming the reviewers know eQuest enough such that if they want to verify the Cool Sizing Ratio or Heat Sizing Ratio, they know exactly where to go in eQuest to find the answers, in a matter of seconds. That seems like a pretty reasonable assumption to me. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><o:p> </o:p></b></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>JAH<o:p></o:p></b></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><o:p> </o:p></b></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><i>James A. Hess, PE, CEM, BEMP</i></b><br>Energy Engineer<br>TME, Inc.<br>Little Rock, AR<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Mobile: (501) 351-4667<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> <a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a> [<a href="mailto:equest-users-bounces@lists.onebuilding.org">mailto:equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>Neil Bulger<br><b>Sent:</b> Wednesday, April 10, 2013 6:02 PM<br><b>To:</b> Patrick J. O'Leary, Jr.<br><b>Cc:</b> <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br><b>Subject:</b> Re: [Equest-users] Cooling/Heating Capacity Ratios - LEED Report?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I second Patrick, typically I just provide screen grabs of the baseline model and send it off.<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><div><div><p><b>Neil Bulger </b>| CEPE | Project Engineer<o:p></o:p></p><p><b>Integral Group </b>| 427 13th Street | Oakland CA USA 94612<br>T 510.663.2070 x235<o:p></o:p></p><p><a href="http://www.integralgroup.com/">integralgroup.com</a> | <a href="mailto:nbulger@integralgroup.com">nbulger@integralgroup.com</a><o:p></o:p></p><p> <b>Trust</b> | <b>Nurture </b>| <b>Inspire</b><o:p></o:p></p><p>Please consider the environment before printing this email.<o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Wed, Apr 10, 2013 at 1:19 PM, Patrick J. O'Leary, Jr. <<a href="mailto:poleary1969@gmail.com">poleary1969@gmail.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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 ........<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br><br><br>On 4/10/13 1:04 PM, Nick Caton wrote: <o:p></o:p></p></div></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi folks,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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 style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>The Task: </b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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 style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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 style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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 style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b> </b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>The Solution(?): </b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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 =).<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Any suggestions/experience?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks in advance!<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>~Nick<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b> </b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>NICK CATON, P.E.</b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>SENIOR ENGINEER<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Smith & Boucher Engineers<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>25501 west valley parkway, suite 200<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>olathe, ks 66061<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>direct <a href="tel:913.344.0036">913.344.0036</a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>fax <a href="tel:913.345.0617">913.345.0617</a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a href="http://www.smithboucher.com">www.smithboucher.com</a><u> </u><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p></div></div><pre>_______________________________________________<o:p></o:p></pre><pre>Equest-users mailing list<o:p></o:p></pre><pre><a href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><o:p></o:p></pre><pre>To unsubscribe from this mailing list send a blank message to <a href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></pre></blockquote><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>_______________________________________________<br>Equest-users mailing list<br><a href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><br>To unsubscribe from this mailing list send a blank message to <a href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p></div></div></div></div></body></html>