<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 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:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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;}
@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: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";}
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.EmailStyle18
{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;
font-size:10.0pt;}
@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'>It’s not my intent to “take sides” or
anything, but a curious reader (me) might ask “What do you use, Chris?”
<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'>As I’m pointing out – a saving grace of
eQuest/DOE2.2 is that you can spoon-feed whatever scheduling you may have
generated in an outside program if you don’t like what you’re
seeing. I understand some distrust eQuest’s results enough to
regularly use DAYsim to generate custom scheduling. In my practice, I’ve
found it more time-efficient to work within and around the known limitations of
eQuest, for the sort of energy modeling I’m regularly tasked with. I
also prefer to use other software packages to model instantaneous daylighting
behavior – anyone interested, see archives.<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 do think it’s a bit of a stretch however to claim the
hourly modeled daylighting behavior of eQuest is comparably dumbed-down as a
blanket percentage reduction, as we do with LPD’s for occupancy sensors under
90.1 (I think that’s what you’re referencing) – eQuest’s
current capabilities do allow an end-user to effectively compare multiple
custom daylighting control strategies and their resultant effects on the rest
of a building’s systems (i.e. heating/cooling) in a time-efficient
fashion.<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’m not disagreeing the DOE2.1e algorithms aren’t
the best for figuring how many fc are incident in a given space for a given
hour, but statements that boil down to “eQuest sucks for daylighting”
(for LEED modeling or otherwise) can certainly be misleading. If you can
take what’s known to be inaccurate into account, you can realize eQuest
as a pretty useful tool for designing with daylighting.<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>
<div>
<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@01CB42E1.522DD000" 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>
</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"'> Chris Jones
[mailto:cj@enersave.ca] <br>
<b>Sent:</b> Monday, August 23, 2010 4:03 PM<br>
<b>To:</b> Nick Caton; equest-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Equest-users] Modeling Light Shelves for Reduction
inCooling/Heating Load?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Equest, like DOE2.1e before it provides very generous
estimates of the lighting energy saved using daylighting controls. I
believe that taking equest predictions at face value for LEED models would be
inaccurately providing more benefit than warranted. The Appendix G power
factor ratings are likely not conservative in some cases. I wouldn't
expect to see any more benefit using equest's daylighting than I would using
the Appendix G power factor adjustments.<br>
<br>
A paper that attempted to explore various daylighting energy reduction savings
modelling strategies. DOE2.1e and Daysim are the two programs used for
the analysis.<br>
<a href="http://www.nrc-cnrc.gc.ca/obj/irc/doc/pubs/nrcc46761/nrcc46761.pdf">http://www.nrc-cnrc.gc.ca/obj/irc/doc/pubs/nrcc46761/nrcc46761.pdf<br>
<br>
<br>
</a>At 03:49 PM 23/08/2010, you wrote:<br>
<br>
<o:p></o:p></p>
<p class=MsoNormal>Content-class: urn:content-classes:message<br>
Content-Type: multipart/related;<br>
boundary="----_=_NextPart_001_01CB42FC.41DFF80A";<br>
type="multipart/alternative"<br>
<br>
Perhaps these are the answers you’re seeking:<br>
1. Building shades and their respective
reflectance properties do affect the modeled behavior of space daylighting
systems in eQuest models. Be sure to pay close attention to all three
values (and their associated help files) on the right of the following image
– they may all play a part depending on what exactly you’re trying
to model.<br>
<img border=0 width=592 height=441 id="_x0000_i1025"
src="cid:image002.png@01CB42E1.522DD000" alt="[]"><br>
2. Based on your query, a caution:
eQuest’s results do not have any inherent degree of accuracy/in-accuracy
with regard to the modeled energy consumption resulting from daylighting
controls – that depends pretty much entirely on how closely you define
the daylighting systems’ behavior to reality. If you have a program
which you perceive to be producing more accurate hourly percentage consumptions
for your spaces, then by all means – there’s nothing stopping you
from defining a schedule in eQuest to match the other program’s
results. <br>
<br>
I expect you mean to say you’re utilizing another program to accurately
determine the behavior of daylight in response to adding/modifying light
shelves, but if you are indeed using another program to determine annual hourly
behavior with a weather file, I’d be very interested to hear more about it!<br>
<br>
Best of luck,<br>
<br>
~Nick<br>
<br>
<img border=0 width=119 height=37 id="_x0000_i1026"
src="cid:image001.jpg@01CB42E1.522DD000" alt="cid:489575314@22072009-0ABB"><br>
<b> <br>
NICK CATON, E.I.T.<br>
</b>PROJECT ENGINEER<br>
25501 west valley parkway<br>
olathe ks 66061<br>
direct 913 344.0036<br>
fax 913 345.0617<br>
<i>Check out our new web-site @ </i><a href="www.smithboucher.htm">www.smithboucher.com</a><u>
<br>
</u> <br>
<b>From:</b> equest-users-bounces@lists.onebuilding.org [<a
href="mailto:equest-users-bounces@lists.onebuilding.org">
mailto:equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>Nilay
R. Desai<br>
<b>Sent:</b> Monday, August 23, 2010 11:35 AM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] Modeling Light Shelves for Reduction
inCooling/Heating Load?<br>
<br>
E.G. Would it be accurate to model an external light shelve as a horizontal
building shade with a high reflectance value on the skyward facing surface? I
understand the day lighting benefit in Equest would be inaccurate, but we are
using separate software to obtain accurate day lighting results. Thanks!<br>
<br>
<br>
Nilay Desai<br>
P 626.351.8881 Ext. 237<br>
<a href="mailto:klowe@tmadtg.com">ndesai@ttgcorp.com</a><br>
<br>
<br>
<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
EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG<o:p></o:p></p>
<p style='margin-bottom:12.0pt'><br>
Chris Jones<br>
14 Oneida Avenue<br>
Toronto, ON M5J 2E3.<br>
Tel. 416-203-7465<br>
Fax. 416-946-1005<o:p></o:p></p>
</div>
</body>
</html>