<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: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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{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 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="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=WordSection1>
<p class=MsoNormal><span style='color:#1F497D'>Hi Jason,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>I really can’t comment on
the LEED process – but you can input frame conductance separately from a glass
package in eQUEST – which allows the software to calculate full-frame
values. Although you won’t be using NFRC certified numbers (as you point
out- for your glass/frame combo they don’t exist) – but I would say
that inputting frame conductance and glass performance separately and letting the
software area-weight them to get full-frame performance gets you pretty close
to a hypothetical NFRC number.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Here’s what I think the
process looks like:<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>You need to use Window5 to
determine what the frame conductance is – I would expect that the frame
conductance doesn’t vary too much in different sized windows. From an
energy modeling standpoint (not sure what LEED/NFRC would say) I would pick a
typical size window and model that in Window5 – making the assumption
that the calculated frame conductance is valid for the other sizes in your
building.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Going back to eQUEST- I would
think that you have your baseline (say double pane low-E in an aluminum frame).
To set up your “improved windows” case, create a parametric run
that first changes the glass to your better glass, and then changes the frame
conductance to match what Window5 outputs.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>This approach would let eQUEST
take care of calculating full-frame performance, and area-weighting the glass
and frame. The only problem with this approach is that you ignore the Edge-Of-Glass
performance that Window5 calculates, and eQUEST doesn’t take into
account. Not sure a way around that one yet.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Just an idea- good luck!<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Cheers,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Alex<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:#262F13'>Alex Krickx<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:gray'>Building Energy
Specialist<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;color:#1F497D'><img width=121
height=42 id="Picture_x0020_1" src="cid:image001.jpg@01CB5EED.10EF00F0"
alt="email_sig"></span><span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:#1F497D'>1250 Elko Dr,
Sunnyvale, CA 94089<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:#1F497D'>(t) 408.541.8124<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:gray'><o:p> </o:p></span></p>
<p class=MsoNormal><b><i><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#1F497D'>Warning:</span></i></b><i><span style='font-size:7.5pt;
font-family:"Arial","sans-serif";color:#1F497D'> The information contained
in this e-mail may be privileged attorney-client communications or attorney
work product and/or proprietary and confidential. If the reader of this
message is not the intended recipient then you have received it in error and
any review, distribution or copying of this message is prohibited and you are
to notify us immediately by reply e-mail and delete the original message
immediately.</span></i><span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='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>Jason
Wendel<br>
<b>Sent:</b> Tuesday, September 28, 2010 7:35 AM<br>
<b>To:</b> 'equest-users@lists.onebuilding.org'<br>
<b>Subject:</b> [Equest-users] Window Assembly U, SC Values<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>I got the review comment back
from LEED that I needed to use the window assembly U-Value and SC Value, not
the center of glass. Unfortunately we have the problem, and it sounds
like others do too on this forum, that the glass manufacturer gives values for
the center of glass values, and then sells their glass to the frame guys to get
the frames that the owner and architect want. Neither one is willing to
NFRC certify their product. So, my options are to use the values in
ASHRAE 90.1-2007 Table A8.2 which are horrible, or model the windows on LBNL
Window5. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>There are lots of windows and
lots of different sizes of windows in the model, so my plan is to find the area
(square feet) of each window, and then run Window5 on typical windows in 5
square foot increments (5, 10, 15, 20, etc. square foot windows) so that I can
run 10 windows instead of 150, and then put it all in a spreadsheet and solve
for the weighted averages.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>If I put the weighted average of
the window values into Equest, will they accept that? Has anyone ever
tried it? I’m in the process of doing another LEED certification
that will be using the same technique if it works, but I won’t know if it
was accepted in the first instance before I submit the second project.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Thanks,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='color:#1F497D'>-Jason<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
</div>
</body>
</html>