<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:"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: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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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="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=Section1>
<p class=MsoNormal><span style='color:#1F497D'>The straight answer is “yes” you
may model light shelves as external building shades for your proposed model and
not get into trouble with regard to 90.1. You would probably not be
taking credit for the full amount of daylight incident in your spaces on an
hourly basis however – you may or may not be able to sleep at night =).<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'>eQuest does not accurately model
interreflected daylight, so you are correct to assert such a model will not in
and of itself accurately account for the effects of light shelves upon your
daylighting systems. Note the values entered for surface/ground
reflectance may still alter the amount of light incident on a given window
through their effects. The effects of those shelves with regard to
shading is something you can be more confident of, however.<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'>If you’d like to take better
credit for light incident on your daylit spaces, I understand some have pursued
using a combination of daysim/SPOT/excel to generate custom scheduling for use
within eQuest. I haven’t traveled this road yet, but I’ve copied what
would probably be a worthwhile discussion below from last Janurary if you’d
like to pursue ;).<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'>~Nick<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'><img width=119 height=37
id="Picture_x0020_1" src="cid:image001.jpg@01CB42E8.3C7C3510"
alt="cid:489575314@22072009-0ABB"></span><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><b><span style='font-size:12.0pt;
font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</span><span
style='font-size:7.5pt;font-family:"Times New Roman","serif";color:#CC9900'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>25501 west
valley parkway<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>direct 913
344.0036<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>fax 913
345.0617<o:p></o:p></span></p>
<p class=MsoNormal><i><span style='font-size:10.0pt;color:#2D4D5E'>Check out
our new web-site @ </span></i><span style='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;color:blue'> </span></u><span style='color:#1F497D'><o:p></o:p></span></p>
</div>
<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"'> Nilay R. Desai
[mailto:ndesai@ttgcorp.com] <br>
<b>Sent:</b> Monday, August 23, 2010 4:50 PM<br>
<b>To:</b> Nick Caton<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><span style='color:#1F497D'>Regarding day lighting
simulation, unfortunately we do not have a separate program that gives us
hourly results, we are just using Ecotect to simulate the behavior of different
shading devices and light shelves. I thought Equest might take into account the
reflective properties of an external shading device when calculating day
lighting, but as I’ve seen stated in the help files and archives, it doesn’t
look like the day lighting benefits of light shelves can be “accurately”
accounted for in Equest. <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'>What I should have asked originally
was would it be ok to model light shelves as external building shades in
reference to ASHRAE 90.1? I know 90.1 allows modeling of light shelves in the
proposed model, but given Equest’s admittance to its inability to <i>properly</i>
model light shelves, would this method of modeling light shelves still be seen
as legitimate given the modeling limitations terminology on pg. 179 of 90.1 –
2007 (if not for the day lighting benefits, at least the shading benefits)?<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><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"'> Otto Schwieterman
[mailto:oschwieterman@fhai.com] <br>
<b>Sent:</b> Friday, January 08, 2010 8:24 AM<br>
<b>To:</b> John Aulbach; Matutinovic, Luka; Nick Caton; R B<br>
<b>Cc:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> RE: [Equest-users] How does eQuest know
initialFootcandlesforDaylighting Calc?<o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Here is an alternate method to
eQUEST’s daylighting strategies:<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'>From my experience (and training
from Marlin Addison), I believe that eQUEST does not model daylighting with
much accuracy. I believe that the best method to handle daylighting is to run
models on independent software (DAYSIM is free) and insert the results
into lighting schedules. My general practice with lighting schedules is to
force 100% of the lights to be on when the room is occupied and during the same
occupied times, create a new schedule that shows the fraction of lights on from
the DAYSIM output. <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 method gives the modeler
more control and flexibility with the model and daylighting strategies. Many
times we have 3 rows of lights in a classroom and we typically force the row
furthest from the window always on when occupied so the minimum percentage of
lights on during daylighting is 33% (1/3). <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<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"'> John Aulbach
[mailto:jra_sac@yahoo.com] <br>
<b>Sent:</b> Thursday, January 07, 2010 12:02 PM<br>
<b>To:</b> Matutinovic, Luka; Nick Caton; R B<br>
<b>Cc:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Equest-users] How does eQuest know
initialFootcandlesforDaylighting Calc?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<p class=MsoNormal>Luka:<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>That was my hope, but eQuest isn't that smart. As I was so
directed by an "unimpeachable source", there IS no footcandle level until
you set it in the Daylighting mode. eQuest then assumes that this is the level
100% of the lights emit. Then when you allow the Daylighting mode to run,
eQuest lowers the % lighting based on how much you can gain from the skylights,
side daylighting, etc.<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>Crude but straight forward.<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>Others can add or correct..<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>John R. Aulbach, PE, CEM<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Senior Energy Engineer<o:p></o:p></span></p>
<div>
<div class=MsoNormal><span style='color:#17365D'>
<hr size=2 width="30%" noshade style='color:#17365D' align=left>
</span></div>
</div>
<p class=MsoNormal><b><span style='font-variant:small-caps;color:navy'>Partner</span><span
style='font-variant:small-caps;color:green'> </span><span style='font-variant:
small-caps;color:#006600'>Energy</span><span style='font-variant:small-caps;
color:navy'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='color:#1F497D'>1990 E. Grand Avenue, El
Segundo, CA 90245<br>
W: 888-826-1216, X254| D: 310-765-7295 | F: 310-817-2745<o:p></o:p></span></p>
<p class=MsoNormal><a href="http://www.ptrenergy.com/"><span style='color:purple'>www.ptrenergy.com</span></a><span
style='color:#1F497D'> </span><a href="mailto:%7C%20jaulbach@ptrenergy.com">|
jaulbach@ptrenergy.com</a><span style='font-family:"Times New Roman","serif";
color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=1 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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"'> "Matutinovic, Luka"
<LMatutinovic@halsall.com><br>
<b>To:</b> Nick Caton <ncaton@smithboucher.com>; R B
<slv3sat@gmail.com>; John Aulbach <jra_sac@yahoo.com><br>
<b>Cc:</b> equest-users@lists.onebuilding.org<br>
<b>Sent:</b> Thu, January 7, 2010 6:09:14 AM<br>
<b>Subject:</b> RE: [Equest-users] How does eQuest know initial
FootcandlesforDaylighting Calc?<br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
Nick,<br>
<br>
Does this mean that there is some "baseline" fc that is provided by
the<br>
electrical lighting? That is to say, eQuest will determine how many fc<br>
daylight provides and satisfy the rest with some fraction of the<br>
installed LPD? This implies that there is a relationship between LPD<br>
and fc, is that true and if so what is it or where could I find it?<br>
Thanks,<br>
<br>
Luka Matutinovic, B.A.Sc., LEED(r) AP<br>
Green Building Consultant <br>
<br>
T. 416.644.0649<br>
F. 416.487.9766 <br>
Toll Free 1.888.425.7255<br>
<a href="http://www.halsall.com/" target="_blank">www.halsall.com</a> <br>
<br>
HALSALL ASSOCIATES LTD. <br>
Toronto Richmond Hill Ottawa Sudbury <br>
Burlington Calgary Vancouver Dubai <br>
<br>
'50 Best Workplaces in Canada' <br>
2009 Globe and Mail<br>
P Please consider the environment before printing this e-mail<br>
<br>
<br>
-----Original Message-----<br>
From: Nick Caton [mailto:<a href="mailto:ncaton@smithboucher.com">ncaton@smithboucher.com</a>]
<br>
Sent: Wednesday, December 30, 2009 10:27 AM<br>
To: R B; John Aulbach<br>
Cc: <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br>
Subject: Re: [Equest-users] How does eQuest know initial<br>
FootcandlesforDaylighting Calc?<br>
<br>
The DOE2 help files suggest, if not directly, that the sensor you are<br>
placing is measuring ONLY "illuminance due to daylight," in isolation
of<br>
any electrical lighting in the project. When you define a
"target"<br>
illumation level (say 30fc) at a specific point/orientation, that sensor<br>
will plot the daylight measured in the same vector against a curve<br>
(specified when you select dimming control options) to determine a<br>
factor to apply to the zone's Lightig Watts/SF.<br>
<br>
To my knowledge, eQuest in no manner whatsoever is attempting to perform<br>
the operations of photometric software (AGI32/Visual/LightPRO/etc).<br>
<br>
~Nick<br>
<br>
NICK CATON, E.I.T.<br>
PROJECT ENGINEER<br>
25501 west valley parkway<br>
olathe ks 66061<br>
direct 913 344.0036<br>
fax 913 345.0617<br>
Check out our new web-site @ <a href="http://www.smithboucher.com/"
target="_blank">www.smithboucher.com</a> <br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a><br>
[mailto:<a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a>]
On Behalf Of R B<br>
Sent: Monday, December 28, 2009 4:44 PM<br>
To: John Aulbach<br>
Cc: <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br>
Subject: Re: [Equest-users] How does eQuest know initial Footcandles<br>
forDaylighting Calc?<br>
<br>
My guess is that the tool assumes the lighting wattage that you have<br>
gives the amount of footcandles specified. If 50% of this is from<br>
daylight, then remaining is from 50% of the installed lighting<br>
(translating into 50% wattage usage).<br>
-Rohini<br>
<br>
On 12/28/09, John Aulbach <<a href="mailto:jra_sac@yahoo.com">jra_sac@yahoo.com</a>>
wrote:<br>
> LIke the Phantom of the Opera.."A mystery never fully explained.."<br>
><br>
> I have performed Daylighting savings EEMs in eQuest, where one places<br>
a<br>
> sensor in the space, one deliniates a minimum footcandle requirement,<br>
and<br>
> runs a Parametric run to determine how much lighting energy may be<br>
saved.<br>
><br>
> What is NOT clear to me is how eQuest determines what the inital<br>
footcandle<br>
> level is. It obviously knows the lighting fixture height (Ceilling or<br>
> syspended) and the geometry of existing windows, etc. But I cannot<br>
find<br>
> where the information lies that says "eQuest assumes so many<br>
lumens/watt of<br>
> certain lighting."<br>
><br>
> Can anyone "ILLUMINATE" me, please?<br>
><br>
> Hope all had a great Christmas.<br>
><br>
> John Aulbach<br>
><br>
><br>
><br>
_______________________________________________<br>
Equest-users mailing list<br>
http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org<br>
To unsubscribe from this mailing list send a blank message to<br>
<a href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<pre>________________________________________________________________________________________<o:p></o:p></pre><pre>Fanning/Howey Associates, Inc. intends to send this transmission (including any attachments) only to the<o:p></o:p></pre><pre>designated individual or entity. If you received this message in error, please notify the sender by replying<o:p></o:p></pre><pre>to the electronic mail (if electronic) or by telephone at the number indicated on this document.<o:p></o:p></pre><pre>Fanning/Howey Associates, Inc. has taken reasonable precautions to ensure no viruses are present in the<o:p></o:p></pre><pre>electronic mail. Fanning/Howey Associates, Inc., will not accept responsibility for any loss or damage arising<o:p></o:p></pre><pre>from the use of this electronic mail or attachments. Use, disclosure, dissemination, distribution, or reproduction<o:p></o:p></pre><pre>of this message by unintended recipients is not authorized and maybe unlawful. Any information included in<o:p></o:p></pre><pre>this transmission that is not related to contracts with our authorization, verbal or written, by Fanning/Howey<o:p></o:p></pre><pre>Associates, Inc. may not be covered by our professional liability insurance. <o:p></o:p></pre><pre><o:p> </o:p></pre>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>