<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:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
@font-face
{font-family:"Stylus BT";
panose-1:2 14 4 2 2 2 6 2 3 4;}
@font-face
{font-family:"Franklin Gothic Medium Cond";}
/* 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.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.msolistparagraph0, li.msolistparagraph0, div.msolistparagraph0
{mso-style-name:msolistparagraph;
mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:navy;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:603536315;
mso-list-type:hybrid;
mso-list-template-ids:1500158270 345538002 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F02D;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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: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'>Table G3.2 by itself also has to cover all possible situations,
but it is also only to provide credit for controls in addition to the mandatory
provisions. I’ll explain my view on those two issues separately. <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'>The intent of 9.4.1.1 from the 90.1 Users Manual is to ensure all
buildings “have an automatic control device that is capable of turning
off lighting in all spaces without human intervention.” This
ensures energy savings when the building is unoccupied. Since occupants
leave a space during the day for various reasons, 9.4.1.2 exists to ensure that
unoccupied spaces during occupied hours have a means to save energy by turning
off the lights, either automatically or manually. In addition, that same
device (if capable) can serve as the override (for safety reasons) to turn
lighting on in the space during unoccupied hours – another mandatory
provision of 9.4.1.2. The way I read it, an occupancy sensor alone cannot
comply with both mandatory provisions because 9.4.1.2 requires an override to
the automatic controls required by 9.4.1.1. If the occ sensor is
installed to comply with 9.4.1.1 and no means is provided to override the
control (such as a manual switch), then compliance with 9.4.1.2 has not been
demonstrated. Once I have satisfied 9.4.1.1 and 9.4.1.2 and only then can
I look to Table G3.2 for credit for automatic controls. That is what
Table G3.1(6)(g) says.<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'>G3.2(1) only applies to buildings less than 5,000SF and non-24-hour
operations and gives 0% credit to larger buildings. This is in line with
9.4.1.1 that requires whole building control for buildings larger than 5,000SF
but not for those smaller. G3.2(2) and G3.2(3) provide the exact same
credit for only an occ sensor or for an occ sensor and programmable timing
device (15% for buildings less than 5,000SF and non-24-hr, 10% for
others). This “estimates” the savings from compliance with
9.4.1.1 at approximately 5% for buildings larger than 5,000SF. The
24-hour operation comment in G3.2 is due to exception (a) to 9.4.1.1 since
whole building control is not required for 24-hour operations.<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'>A situation I could see using G3.2(3) would be one of the more
high-tech security systems. If the security system is tracking occupancy
via security card swipe-in/out records, then it would be capable of determining
that the building is unoccupied. It could send a signal to a relay panel
to turn of the lighting. That would comply with 9.4.1.1(c). At that
point, if every space were designed with manual controls (except the three that
require automatic controls) then the manual controls would comply with 9.4.1.2.
If a time clock and occupancy sensor were installed in addition, that would
allow the credit from G3.2; however, as you pointed out, no additional
efficiency would be gained by the combination of the two that was not achieved
by the occ sensor alone and indeed, Table G3.2 does not provide any additional credit
for installing both in this case where neither would be required for compliance
with the mandatory provisions.<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 it is an order of reading the code issue – since
the mandatory provisions come first, both 9.4.1.1 and 9.4.1.2 must be satisfied
before credit can be taken. If the building only has a time clock, in
that typical office – there needs to be a local control for compliance
with 9.4.1.2. If that office has a switch that can function as an
override to the time clock AND a local control device, then that occ sensor would
indeed be eligible for the 10% credit. But if the office just has the
time clock and the occ sensor – no other devices, then I don’t see
any other way that 9.4.1.2 is satisfied except by the occ sensor, meaning it is
part of the mandatory provisions and not eligible for credit under Table G3.2.<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'>A single occ sensor with no other controls for the lighting in a
space (in buildings larger than 5,000SF) cannot comply with 9.4.1.1, 9.4.1.2
and earn credit under Table G3.2 since table G3.2 is for controls in addition
to the minimum. Going back to the original question, I think the issue
arises somewhat from reviews only recently “cracking down” on this
part of the code…<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'>Thoughts?<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'>Separately, I also agree with the last comments – Baseline
LPD is left alone, always. Table G3.2 only applies to the proposed design
and is a prescriptive alternative to having to use G2.5 Exceptional
Calculations.<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>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#C75B12'>JEREMY R. POLING, PE, LEED AP</span></b><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><br>
</span><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:gray'>Associate Vice President,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:gray'>Senior Sustainability Analyst<br>
Strategic Services<br>
<i>Site Solutions | Operations | Sustainability</i></span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><br>
<br>
</span><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#C75B12'>EPSTEIN</span></b><span style='font-size:10.0pt;font-family:
"Arial","sans-serif";color:#1F497D'><br>
</span><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:gray'>Architecture<br>
Interiors<br>
Engineering<br>
Construction</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><br>
</span><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><br>
</span><b><i><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:green'>Epstein is a firm believer in sustainability. We ask that you
please consider the environment before printing this e-mail.</span></i></b><span
style='font-size:8.0pt;font-family:"Arial","sans-serif";color:gray'><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"'> Nick Caton
[mailto:ncaton@smithboucher.com] <br>
<b>Sent:</b> Wednesday, October 06, 2010 9:48 AM<br>
<b>To:</b> Bishop, Bill; Jeremy Poling; R B<br>
<b>Cc:</b> bldg-sim@lists.onebuilding.org<br>
<b>Subject:</b> RE: [Bldg-sim] Automatic Lighting Shutoff
MandatoryProvisionQuestion<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Jeremy, <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'>Bill’s condensed my thoughts very well. This logic
is further supported by Table G3.2:<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'>If, for your “typical office” case, one needs both a
local occupancy sensor <u>and</u> a timeclock on the circuit to demonstrate a
savings in the proposed model, why would table G3.2 have distinct lines for
“occupancy sensor and programmable timing control” as well as
simply “occupancy sensor?” As you’ve noted, this table
exists for the sole purpose of doling out credit for proposed models, so
there’s no answer other than one may be able to claim credit for occ.
sensors without timer control.<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'>More to the point, and as Bill notes – there’s no
savings gained with a timeclock in combination with an occ. sensor that
can’t be achieved by an occ. sensor alone (that’s how I think of it
anyway). An occ. sensor will however save you energy over a timeclock
alone as you’ll achieve shutoff periods during working hours.
That’s probably why the LPD reductions in the two lines mentioned above
are identical. For these reasons, I think we can consider occ. sensors
alone to be “in addition to” the minimum automatic shutoff requirements
– inferred to be a timeclock alone. I reckon you can take the LPD
credit in those spaces.<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'>To your classroom example: Yes, I’ve regularly
interpreted spaces like classrooms with automatic shutoff <u>and</u>
multi-scene controls to be qualified for a LPD reduction due to the corresponding
exemption in 9.4.1.2.<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'>Hope that helps!<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@01CB6573.57A02AB0" 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"'> Bishop, Bill
[mailto:wbishop@pathfinder-ea.com] <br>
<b>Sent:</b> Wednesday, October 06, 2010 8:56 AM<br>
<b>To:</b> Jeremy Poling; Nick Caton; R B<br>
<b>Cc:</b> bldg-sim@lists.onebuilding.org<br>
<b>Subject:</b> RE: [Bldg-sim] Automatic Lighting Shutoff
MandatoryProvisionQuestion<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Jeremy,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>I agree with Nick’s explanation to Jaigath, below. A 10% LPD
credit can be taken in spaces that have occupancy sensors, except where occupancy
sensors are required (classrooms etc. per 9.4.1.2). It would make no sense to
allow energy savings only for spaces that have both time clock and occupancy
controls, since a space with both controls would provide no additional energy
savings over an occupancy sensor alone.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>I also agree with Nick’s comment to Rohini. Leave the
baseline LPD alone (turning lights off during unoccupied hours using the same
schedule in baseline and proposed) and take the 10% credit in the proposed
where applicable.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Bill<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Franklin Gothic Medium Cond";
color:black'>William Bishop, PE, BEMP, LEED<sup>®</sup> AP </span></b><b><span
style='font-size:10.0pt;font-family:"Franklin Gothic Medium Cond";color:#006600'>|</span></b><b><span
style='font-size:10.0pt;font-family:"Franklin Gothic Medium Cond";color:black'>
Pathfinder Engineers & Architects LLP<o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:black'>Mechanical Engineer<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:5.0pt;font-family:"Arial","sans-serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:navy'>134 South Fitzhugh Street</span><span style='font-size:9.0pt;
color:navy'><br>
</span><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:navy'>Rochester, NY 14608</span><span style='font-size:9.0pt;color:navy'><br>
</span><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:navy'>T: (585) 325-6004 </span><span style='font-size:9.0pt;font-family:
"Arial","sans-serif";color:black'>Ext. 114</span><span style='font-size:9.0pt;
color:navy'><br>
</span><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:navy'>F: (585) 325-6005</span><span style='font-size:9.0pt;font-family:
"Arial","sans-serif";color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:black'>wbishop@pathfinder-ea.com<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:black'>www.pathfinder-ea.com</span><span style='color:navy'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:18.0pt;font-family:Webdings;
color:green'>P</span><span style='color:green'> </span><span
style='font-size:7.5pt;color:green'>Sustainability – the forest AND the
trees.</span><span style='font-size:18.0pt;font-family:Webdings;color:green'> P</span><span
style='color:green'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<div>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<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"'> bldg-sim-bounces@lists.onebuilding.org
[mailto:bldg-sim-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Jeremy
Poling<br>
<b>Sent:</b> Wednesday, October 06, 2010 12:52 AM<br>
<b>To:</b> Nick Caton; R B<br>
<b>Cc:</b> bldg-sim@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Bldg-sim] Automatic Lighting Shutoff
MandatoryProvisionQuestion</span><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>We just had a pretty in-depth discussion on this internally also
– local implementations of the code (for example, Chicago Building Code)
have added some confusion. To add to what Nick said, the credits in table
G3.2 are only referenced in the lighting requirements in Table G3.1 and are
specifically listed for use in the proposed model for controls that are not
already required by the mandatory provisions of Section 9. I’ve
always found it ironic that a Section G3.2 doesn’t exist even though a
Table G3.2 does…but I digress…here is where we arrived internally:<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'>Section 9.4.1 has 4 main parts – Whole building control,
individual space control, exterior lighting control and additional mandatory
controls.<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=msolistparagraph0 style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>9.4.1.1 requires an automatic whole building control capable of
shutting off lighting (with override capabilities allowed) for the entire
building based on either (a) time clock signal, (b) occupancy sensors, or (c)
some other control signal (like a BMS). This applies to all buildings
over 5,000 SF.<o:p></o:p></span></p>
<p class=msolistparagraph0 style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>9.4.1.2 requires an individual control for all spaces, either
manual or automatic. For specific space types, automatic controls are
required: classrooms (except shop classrooms, laboratory classrooms, and
preschool – 12th grade classrooms), conference/meeting rooms, and
employee lunch and break rooms UNLESS those rooms have multiscene control in
which case they are also exempt from the automatic requirement. All other
spaces are not required to have automatic controls and can have either manual
or automatic controls. In addition, those spaces where automatic controls
are mandatory are NOT required to be connected to other automatic lighting
shutoff controls (i.e. the whole building controls required by 9.4.1.1)<o:p></o:p></span></p>
<p class=msolistparagraph0 style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>9.4.1.3 requires photocell or astronomical time clock control of
site lighting (with some nuances, but this is a safe simplification of the
requirements).<o:p></o:p></span></p>
<p class=msolistparagraph0 style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>9.4.1.4 requires a number of specialty lighting installations to
have controls – most applicable to LEED is the requirement for all task
lighting to have an individual control.<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'>The way I simplified this for our engineers is the following:
any and all spaces will have 2 levels of code-required control. The first
will comply with 9.4.1.1 and the second will comply with 9.4.1.2. As an
example, for a typical private office our engineers have been using wall
devices that have an occ sensor with a manual control. If that is the
only controls that cover the private office, then the occ sensor complies with
9.4.1.1 and the manual switch complies with 9.4.1.2; no credit from Table G3.2
would be allowed since both control methods are required by 9.4.1. Now,
if there is a time clock in the building and the private office were connected
to the time clock with the same wall device the situation would be different:
the time clock would comply with 9.4.1.1 and the manual switch would comply
with 9.4.1.2 leaving the occupancy sensor as an additional control, eligible in
Table G3.2 for a 10% LPD credit against the PROPOSED LPD factors. For a
classroom in a community center, if the lighting is setup for multiple purposes
and the space is on the building time clock, then you just have compliance with
9.4.1.2 and 9.4.1.1 respectively. If you put in an occ sensor (some
control logic required due to the multiscene) then you can take credit for that
sensor in Table G3.2.<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 curious what you two think of this interpretation?<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'>We even went so far in our discussion to look literally at the
way 9.4.1.1 is worded and I believe that since the word “either”
does not imply mixed compliance then any given building must comply entirely
with one of the three options, not a mix of two. Say a time clock for
common spaces with occ sensors for tenant leased space, for example, would not
comply with the most strict reading of the code. That is quite literal,
but I’ve had code reviewers who have read other codes that literally
before…<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>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#C75B12'>JEREMY R. POLING, PE, LEED AP</span></b><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><br>
</span><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:gray'>Associate Vice President,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:gray'>Senior Sustainability Analyst<br>
Strategic Services<br>
<i>Site Solutions | Operations | Sustainability</i></span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><br>
<br>
</span><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#C75B12'>EPSTEIN</span></b><span style='font-size:10.0pt;font-family:
"Arial","sans-serif";color:#1F497D'><br>
</span><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:gray'>Architecture<br>
Interiors<br>
Engineering<br>
Construction</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><br>
</span><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><br>
</span><b><i><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:green'>Epstein is a firm believer in sustainability. We ask that you
please consider the environment before printing this e-mail.</span></i></b><span
style='font-size:8.0pt;font-family:"Arial","sans-serif";color:gray'><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"'>
bldg-sim-bounces@lists.onebuilding.org [mailto:bldg-sim-bounces@lists.onebuilding.org]
<b>On Behalf Of </b>Nick Caton<br>
<b>Sent:</b> Tuesday, October 05, 2010 10:40 AM<br>
<b>To:</b> R B<br>
<b>Cc:</b> bldg-sim@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Bldg-sim] Automatic Lighting Shutoff Mandatory
ProvisionQuestion<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Rohini,<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'>While it’s a minor point, I’d only caution that my
“hard and fast rule” is pretty much a directly from Table
G3.1.6: “No automatic lighting controls … shall be modeled in
the baseline building design…” That said, if I were a
reviewer I wouldn’t have a problem with your approach.<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'>While modeling occ. sensors in both cases would help the EUI of
the proposed model, not modeling occ sensors in both cases will mean your
baseline and proposed HVAC systems have to deal with extra internal
loads, so presuming you have a better HVAC system in the proposed model,
I’d intuitively assume if anything a classroom-heavy school/university
might do better to not model occ. sensors in each model… I guess if the
results bear it out, go with the flow though =).<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'><img border=0 width=119 height=37 id="Picture_x005f_x0020_1"
src="cid:image001.jpg@01CB6573.57A02AB0" 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"'> R B
[mailto:slv3sat@gmail.com] <br>
<b>Sent:</b> Tuesday, October 05, 2010 10:23 AM<br>
<b>To:</b> Nick Caton<br>
<b>Cc:</b> Jaigath Chandraprakash; bldg-sim@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Bldg-sim] Automatic Lighting Shutoff Mandatory Provision
Question<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>I actually take the credit for
occ. sensor in both the baseline and proposed case for such spaces that have a
mandatory requirement for occupancy sensor (e.g. classroom). The advantage is
your total energy consumption is slightly less, so when you are in border line
cases where you are ever so slightly less than the required percentage points
for the next level of points it helps. Much more advantageous to do it this way
when you are doing a school/university building.<br>
-Rohini<br>
<br>
Rohini Brahme, Ph.D, LEED AP<br>
Building energy analysis, tool development, and training<br>
Dallas/Fort Worth, TX <o:p></o:p></p>
<div>
<p class=MsoNormal>On Tue, Oct 5, 2010 at 9:06 AM, Nick Caton <<a
href="mailto:ncaton@smithboucher.com">ncaton@smithboucher.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>The hard and fast rule I follow is that
baseline LPD’s are never to be messed with. Any and all credit
taken for lighting controls is a deduction of LPD (or sufficiently documented
schedule adjustment, I suppose) in the proposed case. </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>It can get confusing, but in specific
spaces (i.e. classrooms), 9.4.1.2 may require occ. sensors. In such a
case, I don’t take a credit in the baseline (see hard/fast rule above),
but instead remove the credit otherwise taken for that space in the proposed
case. </span><o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>~Nick</span><o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'><img border=0 width=119 height=37
id="_x0000_i1027" src="cid:image001.jpg@01CB6573.57A02AB0"
alt="cid:489575314@22072009-0ABB"></span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:11.0pt;color:#2D4D5E'> </span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:11.0pt;color:#2D4D5E'>NICK CATON, E.I.T.</span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>25501 west valley parkway</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>direct 913 344.0036</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>fax 913 345.0617</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><i><span
style='font-size:10.0pt;color:#2D4D5E'>Check out our new web-site @ </span></i><span
style='font-size:11.0pt;color:#1F497D'><a href="http://www.smithboucher.com"
target="_blank" title="blocked::www.smithboucher.com"><span style='font-size:
10.0pt'>www.smithboucher.com</span></a></span><u><span style='font-size:10.0pt;
color:blue'> </span></u><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color -moz-use-text-color'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'>
Jaigath Chandraprakash [mailto:<a href="mailto:cjaigath@yahoo.com"
target="_blank">cjaigath@yahoo.com</a>] <br>
<b>Sent:</b> Monday, October 04, 2010 8:32 PM<br>
<b>To:</b> Nick Caton; <a href="mailto:bldg-sim@lists.onebuilding.org"
target="_blank">bldg-sim@lists.onebuilding.org</a><br>
<b>Subject:</b> Re: [Bldg-sim] Automatic Lighting Shutoff Mandatory Provision
Question</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thank
you very much Nick. I really appreciate your help on this.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <br>
I really got confused with this when I got a commnet recently saying that the
"baseline case per section 9.4.1.2 were not modeled" and was asked to
revised the baseline. So I ended up with no savings. This is in conflict with
Table G3.1.6 that you have pointed out which says that No automatic lighting
controls shall be modeled in the baseline building design. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Does
it mean that I am wrong when I applied also 10% savings to my baseline? This is
where I got confused since 9.4.1.1.b also mentions occupant sensor
that shall turn lighting off within 30 mins of occupant leaving the
space. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div>
<div>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt'>
<hr size=1 width="100%" align=center>
</span></div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> Nick
Caton <<a href="mailto:ncaton@smithboucher.com" target="_blank">ncaton@smithboucher.com</a>><br>
<b>To:</b> Jaigath Chandraprakash <<a href="mailto:cjaigath@yahoo.com"
target="_blank">cjaigath@yahoo.com</a>>; <a
href="mailto:bldg-sim@lists.onebuilding.org" target="_blank">bldg-sim@lists.onebuilding.org</a><br>
<b>Sent:</b> Mon, October 4, 2010 10:38:08 PM<br>
<b>Subject:</b> RE: [Bldg-sim] Automatic Lighting Shutoff Mandatory Provision
Question</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Jaigath,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Appendix G allows us to take credit for
automatic controls <u>in addition to</u> (beyond) what’s required in
9.4.1 for minimum compliance. One of the options here is to have
programmable (time-of-day) shutoff for interior lighting circuits, and you can
infer from between Table G3.1 and G3.2 of Appendix G that baseline models are
taken to feature only such timeclock controls for automatic shutoff.
Further, it’s taken that the lighting scheduling being kept identical
between the proposed and baseline adequately reflects the minimum requirements,
so you aren’t supposed to try to explicitly model the programmable
shutoff. </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>If you have occupancy sensors throughout
a building which only requires programmable shutoff, that’s an example of
having automatic controls beyond what 9.4.1 requires – and you’d
get to take 10% off your proposed LPD in all spaces where such short-term
shutoff isn’t already required (per following section 9.4.1.2).</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Note Table G3.2 also has a corresponding
distinction between building smaller than and larger than 5,000ft2 –
offering more credit for buildings using a means of automatic shutoff where no
such controls are even minimally required.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>~Nick</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:11.0pt;color:#1F497D'>Error! Filename not specified.</span></b><o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:11.0pt;color:#2D4D5E'> </span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:11.0pt;color:#2D4D5E'>NICK CATON, E.I.T.</span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>25501 west valley parkway</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>direct 913 344.0036</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>fax 913 345.0617</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><i><span
style='font-size:10.0pt;color:#2D4D5E'>Check out our new web-site @ </span></i><span
style='font-size:10.0pt;color:blue'><a href="http://www.smithboucher.com"
target="_blank">www.smithboucher.com</a><u> </u></span><o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color -moz-use-text-color'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a
href="mailto:bldg-sim-bounces@lists.onebuilding.org" target="_blank">bldg-sim-bounces@lists.onebuilding.org</a>
[mailto:<a href="mailto:bldg-sim-bounces@lists.onebuilding.org" target="_blank">bldg-sim-bounces@lists.onebuilding.org</a>]
<b>On Behalf Of </b>Jaigath Chandraprakash<br>
<b>Sent:</b> Monday, October 04, 2010 9:01 AM<br>
<b>To:</b> <a href="mailto:bldg-sim@lists.onebuilding.org" target="_blank">bldg-sim@lists.onebuilding.org</a><br>
<b>Subject:</b> [Bldg-sim] Automatic Lighting Shutoff Mandatory Provision
Question</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hello
All,<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I
am confused on the mandatory provision 9.4.1.1 which states that building
larger than 5000 ft2 shall have automatic control device. Does it mean
that mid-rise and high rise building cannot claim for credit in
occupancy sensors shown in Table G3.2 because their GFA is more than 5000 ft2
and only small office can claim for this credit? I am sure I am not
interpreting this section correct since from what I read, other modelers
are claiming for savings for buildings with more than 5000 ft2 area for
occupancy sensors even if mandatory requirements states that this is required
which means baseline building will also have occupancy sensors.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Can
someone correct me on this? <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thank
you,<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>C. Jaigath <o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
_______________________________________________<br>
Bldg-sim mailing list<br>
<a href="http://lists.onebuilding.org/listinfo.cgi/bldg-sim-onebuilding.org"
target="_blank">http://lists.onebuilding.org/listinfo.cgi/bldg-sim-onebuilding.org</a><br>
To unsubscribe from this mailing list send a blank message to <a
href="mailto:BLDG-SIM-UNSUBSCRIBE@ONEBUILDING.ORG">BLDG-SIM-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>