[Equest-users] Baseline or Proposed? Chicken or the egg?

[Paul Diglio]

Pasha:

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.

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.

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?

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.

What is your experience?  Can you create a baseline model from a unusual 
proposed model using the compliance tool?

Paul Diglio

 




________________________________
From: Pasha Korber-Gonzalez <pasha.pkconsulting at gmail.com>
To: Paul Diglio <paul.diglio at sbcglobal.net>
Cc: eQUEST Users List <equest-users at lists.onebuilding.org>
Sent: Tue, October 26, 2010 11:06:44 PM
Subject: Re: [Equest-users] Baseline or Proposed? Chicken or the egg?


A couple of further questions then:
 
	* if you are doing a LEED (or other) compliance model (without design analysis) 
then do you build the proposed or baseline model first?
	* 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?
pkg
 
On Tue, Oct 26, 2010 at 7:44 PM, Paul Diglio <paul.diglio at sbcglobal.net> wrote:

Pasha:
>
>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.
>
>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.
>
>Paul Diglio
>
>
>
>
________________________________
 From: Pasha Korber-Gonzalez <pasha.pkconsulting at gmail.com>
>To: eQUEST Users List <equest-users at lists.onebuilding.org>
>Sent: Tue, October 26, 2010 8:27:55 PM 
>
>Subject: [Equest-users] Baseline or Proposed? Chicken or the egg?
> 
>
>
>Out of curiosity do you build your proposed model first or your baseline model 
>first?
> 
> 
>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.
> 
>What's your approach?
> 
>pkg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20101026/910bf58f/attachment.htm>