<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=iso-8859-1"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><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:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
/* 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.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
{mso-style-priority:1;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Segoe UI","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@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="1026" />
</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='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'>Have any of you run into a review team telling you that you must model the baseline fan supply volume and baseline fan power the same in the proposed design? I have a project under review that is a distribution center primarily served by heating only make up air units. I have modeled cooling in both models and modeled the setpoint high enough that it would never turn on. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'>My interpretation of the requirement to model cooling the same in both models if cooling does not exist on the proposed design is just that, you only model the cooling the same. However, this is the response we received after our initial design comments review:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNoSpacing><i><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:#1F497D'>2. The response narrative to preliminary comment 5 states that the baseline case was modeled with a fan supply volume determined using Section G3.1.2.8 and a fan power determined using Section G3.1.2.9; however the proposed case must also be determined using these parameters. Per Table G3.1.10(d) in the proposed building column, where no cooling system exists, it must be modeled identically to the baseline case. <b>Because the fan supply volume and fan power are cooling driven, it is unacceptable to auto-size the baseline case fan supply volume and fan power and not auto-size the proposed case fan supply volume and fan power.</b> Currently, the baseline fan supply volume is sized to meet cooling needs and the proposed fan supply volume is sized to meet heating and ventilation needs. If appealing this credit, <b>revise the Proposed case fan supply volume and fan power so that they are determined using Section G3.1.2.8 and Section G3.1.2.9. Note that it is appropriate for the proposed fans to be modeled as VAV since HVAC System 7 applies</b>. Additionally, provide SV-A reports confirming the changes.<o:p></o:p></span></i></p><p class=MsoNoSpacing><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNoSpacing><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'>Another comment we received claimed that we must model the 0.4 CFM/SF requirement on the proposed model because the airflows are sized based on cooling and therefore, the airflow rules from System 7 apply (i.e. 20 delta T, min flow requirements, etc.)<o:p></o:p></span></p><p class=MsoNoSpacing><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNoSpacing><i><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:#1F497D'>3. The response narrative to preliminary comment 12 states that the full load equivalent hours are so high due to the 0.4 cfm/sq.ft flow rate; however the 0.4 cfm/sq.ft rate applies only when the building is occupied or when the interior fans are cycled on during unoccupied hours to meet heating or cooling loads. Based on the information provided in Section 1.2 of the Prerequisite form the occupied hours are only 40 per week. If appealing this credit, revise the schedules in both cases to reflect the actual anticipated schedules of the interior fans installed in the building. Additionally, revise the baseline case (and proposed case as necessary for equipment auto-sized per Table G3.1.10(d)) so that the 0.4 cfm/sq.ft minimum flow rate applies only when the building is occupied or when they are cycled on. <o:p></o:p></span></i></p><p class=MsoNoSpacing><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'>I already took care of the scheduling of the when the fans turned on. However, I honestly feel like the rest of both comments step over the line in terms of what we are suppose to model on the proposed design. The changes we would need to make (primarily forcing the airflows to be sized the same as the baseline and 0.4 cfm/sq ft) do not represent the design intent of the system shown on the drawings.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'>What do you guys think?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:12.0pt;font-family:"Segoe UI","sans-serif";color:#C75B12'>William Mak, LEED AP BD+C</span></b><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif";color:#1F497D'><br></span><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:black'>Mechanical Design Engineer</span><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif";color:black'><br></span><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif";color:#1F497D'><br></span><b><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:#C75B12'>EPSTEIN</span></b><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif";color:#1F497D'><br></span><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:black'>Architecture<br></span><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:#C75B12'>Interiors</span><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:black'><br>Engineering<br></span><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:#C75B12'>Construction</span><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:black'>Sustainability<br><br>600 West Fulton Street<br>Chicago, Illinois 60661-1259<br><br>D: (312) 429-8116<br>F: (312) 429-8800</span><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:black'>E:</span><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:#0070C0'> <a href="mailto:wmak@epsteinglobal.com"><span style='color:blue'>wmak@epsteinglobal.com</span></a></span><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:black'><br>W:</span><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:#C75B12'> <a href="http://www.epsteinglobal.com/"><span style='color:#C75B12'>www.epsteinglobal.com</span></a></span><span style='font-size:9.0pt;font-family:"Segoe UI","sans-serif";color:black'><br><br></span><span style='font-size:10.0pt;font-family:Webdings;color:#00B050'>þ</span><span style='font-size:8.0pt;font-family:"Segoe UI","sans-serif";color:black'> Epstein is a firm believer in sustainability. We ask that you please consider the environment before printing this e-mail.<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>