<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:10pt"><div>Pasha:<br><br>I have not had the opportunity yet to create a model in 3.64. I tried the 90.1 compliance on a few 3.63 projects and came up with all kinds of odd errors that I did not research.<br><br>The models that I tried were very unusual, for example two sources of exhaust air and three sources of heating per zone. Naturally, I had to fudge the systems to model a thermally equivalent mechanical system and work up exceptional calculations for GBCI.<br><br>Perhaps the compliance works well with standard type systems. Do you know if the compliance in 3.64 will accept a 3.63 project seamlessly?<br><br>You might be correct that 3.64 is intended to create a baseline from the proposed. My initial take was that the compliance tool would compare the baseline that I create to
90.1 specs and verify if I have modeled this correctly.<br><br>What is your experience? Can you create a baseline model from a unusual proposed model using the compliance tool?<br><br>Paul Diglio<br><br> <br></div><div style="font-family: times new roman,new york,times,serif; font-size: 10pt;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Pasha Korber-Gonzalez <pasha.pkconsulting@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> Paul Diglio <paul.diglio@sbcglobal.net><br><b><span style="font-weight: bold;">Cc:</span></b> eQUEST Users List <equest-users@lists.onebuilding.org><br><b><span style="font-weight: bold;">Sent:</span></b> Tue, October 26, 2010 11:06:44 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Equest-users] Baseline or Proposed? Chicken or the
egg?<br></font><br>
<div>A couple of further questions then:</div>
<div> </div>
<ul>
<li>if you are doing a LEED (or other) compliance model (without design analysis) then do you build the proposed or baseline model first?</li>
<li>With eQuest 3.64 doesn't it create a baseline model file based on building your proposed model in eQuest first? I thought that was the function/convenience of the compliance tool. Of course the baseline model file needs to be checked and calibrated but the general intent was to streamline the creation of a baseline model file in response to the inputs for the proposed design. Is this correct logic?</li>
</ul>
<div>pkg</div>
<div> </div>
<div class="gmail_quote">On Tue, Oct 26, 2010 at 7:44 PM, Paul Diglio <span dir="ltr"><<a rel="nofollow" ymailto="mailto:paul.diglio@sbcglobal.net" target="_blank" href="mailto:paul.diglio@sbcglobal.net">paul.diglio@sbcglobal.net</a>></span> wrote:<br>
<blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;" class="gmail_quote">
<div>
<div style="font-family: times new roman,new york,times,serif; font-size: 10pt;">
<div>Pasha:<br><br>I always start with the baseline model because I am usually hired to provide design suggestions. By modeling the baseline first I become familiar with the 90.1 requirements for the type of building and systems we are working on and I can make suggestions that will increase the efficiency of the facility above and beyond the 90.1 standard.<br>
<br>For example, if my total exhaust air for a zone is less than 5,000 CFM, 90.1 does not require exhaust energy recovery, but by implementing this option in the proposed model we can achieve a greater reduction compared to the 90.1 baseline.<br>
<br>Paul Diglio<br></div>
<div style="font-family: times new roman,new york,times,serif; font-size: 10pt;"><br>
<div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font face="Tahoma" size="2">
<hr size="1">
<b><span style="font-weight: bold;">From:</span></b> Pasha Korber-Gonzalez <<a rel="nofollow" ymailto="mailto:pasha.pkconsulting@gmail.com" target="_blank" href="mailto:pasha.pkconsulting@gmail.com">pasha.pkconsulting@gmail.com</a>><br><b><span style="font-weight: bold;">To:</span></b> eQUEST Users List <<a rel="nofollow" ymailto="mailto:equest-users@lists.onebuilding.org" target="_blank" href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a>><br>
<b><span style="font-weight: bold;">Sent:</span></b> Tue, October 26, 2010 8:27:55 PM
<div class="im"><br><b><span style="font-weight: bold;">Subject:</span></b> [Equest-users] Baseline or Proposed? Chicken or the egg?<br></div></font>
<div>
<div></div>
<div class="h5"><br>
<div>Out of curiosity do you build your proposed model first or your baseline model first?</div>
<div> </div>
<div> </div>
<div>I build my proposed model first. This is the way that I was taught and the way I learned that makes sense to me in terms of "backing-off" the performance values to that equal of the baseline values. Or in the case of different types of HVAC systems I prefer to build the proposed model first and then do a "save as" to a baseline file to make all the appropriate baseline input adjustments. This just seems most efficient for my modeling approach.</div>
<div> </div>
<div>What's your approach?</div>
<div> </div>
<div>pkg</div></div></div></div></div></div></div></blockquote></div><br>
</div></div>
</div></body></html>