<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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 12 (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:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 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;}
/* 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.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-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
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;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>John,<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'>At the moment, it’s up to the end-user to be sure your
baseline model is meeting the 90.1 minimum baseline criteria. If you
haven’t already checked it out, Appendix G explains how the model is to
be set up and calibrated to a level of performance (measured via unmet load
hours) that’s to be in the same ballpark as your proposed design.
If you apply all design criteria there into eQuest, then you’re following
90.1.<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'>I think you’re describing and hoping to find eQuest can behave
similarly to COMcheck and other “plug and chug” type compliance documentation
software. I had the same hopes when I first got into the program…
Over time though I’ve come to understand that 90.1 has so many
gray/interpretable areas that I’m not sure that a “push-button
baseline builder” is really a desirable thing for the task of energy
modeling. <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'>Until the day comes when software developers are producing “intelligent”
energy modeling software that makes evaluative decisions as effectively as a
human being, I don’t think the task of “generate a baseline energy
model per 90.1” is even a feasible concept. Even if such a (complex)
feature was around to use, you’d still have to do a complete proposed
model for the baseline to reference for geometries/occupancies/zoning/etc –
building the baseline after that is not a huge relative investment of time in
my experience… <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'>In summary, I don’t think effective/useful energy modeling
for 90.1-based compliance is conceptually possible without involvement from a
human that’s at least somewhat familiar with 90.1’s Appendix G –
it cannot be automated without a degree of accuracy loss that I think most
would find unacceptable. <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'>That’s not to say the process couldn’t be made
easier with eQuest (following is a suggestion with that in mind), and I
understand other “for-cost” energy modeling software do generate
compliance certificates of sorts for baseline/proposed LEED comparisons (or at
least the LEED template would lead me to believe this). My impression however
is that where the current evolution of eQuest can fall behind it’s “competition”
in cases regarding user-interface (though it’s definitely better than a
lot of what’s out there), it excels in breadth and depth of modeling
energy behaviors, and in a less measureable way because of the massive
community of professional energy modelers embracing and offering each other
support for the program through forums like this one. And of course, you
can’t beat free =).<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'>For the record, I do think a good “wishlist” item
for the coming versions of eQuest, to facilitate easier, more consistent and
less error-prone 90.1 baseline modeling for users of all experience levels, would
be to create a library of 8 systems for use during HVAC system wizard-level
definition (See attached screenshot/paint masterpiece for when/where/what I’m
thinking). These would define a set of defaults for one of the 8 standard
baseline systems, but would still require the end-user to determine project
specific wizard-level criteria (such as climate zone-specific economizer/high
limit requirements and such). I’ve noted that the recent 90.1-2007
and 90.1-2004 are identical in these definitions, so that lends some
consolation that such efforts would not become “out-of-date” for
some time to come.<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'>One last note: do be sure you’re using the latest version (3.63b)…
I’m observing after clicking ‘Help’ –> ‘About
eQUEST…’ my installation of 3.63b contains the line “eQUEST,
version 3.63, build 6510,” if that helps you to verify.<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'>Apologies for the wall of text – it’s a recurring
habit of mine…<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'>~Nick<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'><img width=119 height=37 id="Picture_x0020_1"
src="cid:image001.jpg@01CA6CE5.35272970" alt="cid:489575314@22072009-0ABB"></span><b><span
style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Calibri","sans-serif";
color:#CC9900'>PROJECT ENGINEER</span><span style='font-size:7.5pt;color:#CC9900'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>25501 west valley parkway<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>olathe ks 66061<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>direct 913 344.0036<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>fax 913 345.0617<o:p></o:p></span></p>
<p class=MsoNormal><i><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>Check out our new web-site @ </span></i><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a
href="www.smithboucher.com" title="blocked::www.smithboucher.com"><span
style='font-size:10.0pt'>www.smithboucher.com</span></a></span><u><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:blue'> </span></u><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'><o:p> </o:p></span></p>
<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>John
Wearstler<br>
<b>Sent:</b> Tuesday, November 24, 2009 7:24 AM<br>
<b>To:</b> Equest Forum<br>
<b>Subject:</b> [Equest-users] Equest Base Model vs. ASHRAE 90.1<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>Hello All,<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I am fairly new to using Equest. (version 3.63). In a 12
page overview, it indicates that future enhancements to Equest will include building
energy code compliance checking, initially: California Title 24 and later,
ASHRAE 90-1. When modeling the base building for comparisons, I think the goal
would be to enter data that allows the base to just pass the 90-1 criteria,
such as a minimum btuh/ square foot efficiency. This would permit the
greatest difference to be shown in a comparison. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>How does Equest control the base model to meet this
90-1 minimum? Is there a built-in data checking/ evaluation/ editing
mechanism or is it up to the user to enter the exact minimum value
data to show the base model just meeting 90-1? Are certain parts of the
Equest program calculating mechanism following 90-1? <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Thank you in advance,<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <br>
-- <br>
John Wearstler<br>
Senior Designer<br>
Larsen Engineering, Inc.<br>
4662 Larwell Drive<br>
Columbus, Ohio 43220<br>
<br>
614-459-4002 (voice)<br>
614-459-3124 (fax)<br>
<a href="mailto:jwearstler@larseneng.com">jwearstler@larseneng.com</a> (e-mail)<br>
<br>
This transmission may contain information that is privileged, confidential, or
exempt from disclosure under applicable law. If you are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution, or use of the information contained herein is strictly
prohibited. If you received this transmission in error, please contact
the sender and destroy the material in its entirety.<br>
<br>
Email transmission cannot be guaranteed secure or error-free. Computer viruses
can be transmitted via email - check email and any attachments for viruses.
Larsen Engineering Inc. does not accept liability for errors or omissions
resulting from transmission or any damage caused by a virus transmitted by this
email. <o:p></o:p></p>
</div>
</div>
</body>
</html>