<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16981" name=GENERATOR><!--[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-face {
font-family: MS Mincho;
}
@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Stylus BT;
}
@font-face {
font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
P.MsoListParagraph {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 34
}
LI.MsoListParagraph {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 34
}
SPAN.BalloonTextChar {
FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
SPAN.EmailStyle20 {
COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle21 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="3074" />
</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 vLink=purple link=blue>
<DIV><FONT face=Arial color=#0000ff size=2></FONT><FONT face=Arial size=2>
<DIV><FONT face=Calibri color=#0000ff size=3><SPAN
class=243322313-30032010>Nick,</SPAN></FONT></DIV>
<DIV><FONT face=Calibri color=#0000ff size=3><SPAN
class=243322313-30032010></SPAN></FONT> </DIV>
<DIV><FONT face=Calibri><FONT color=#0000ff><FONT size=3><SPAN
class=243322313-30032010><SPAN class=415203915-30032010>Reverting back to your
original email, i</SPAN>f you are defining <SPAN
class=415203915-30032010>2</SPAN> sensors in reference to the same
space, <SPAN class=415203915-30032010>as seen in your screenshot,
</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Calibri><FONT color=#0000ff><FONT size=3><SPAN
class=243322313-30032010><SPAN class=415203915-30032010></SPAN>you should
get </SPAN><SPAN class=243322313-30032010>daylighting contribution
</SPAN></FONT></FONT></FONT><FONT face=Calibri><FONT color=#0000ff><FONT
size=3><SPAN class=243322313-30032010>calculated at both
sensors.</SPAN></FONT></FONT></FONT></DIV>
<DIV><SPAN class=243322313-30032010><FONT face=Calibri><FONT color=#0000ff><FONT
size=3>Which does not mean that the calculated values will be accurate<SPAN
class=415203915-30032010>. S</SPAN>ince the primary space is your north
zone, <SPAN class=415203915-30032010>the 2nd
sensor</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><FONT face=Calibri><FONT color=#0000ff><FONT size=3><FONT><SPAN
class=243322313-30032010>will only be<SPAN class=415203915-30032010>
</SPAN></SPAN></FONT><SPAN class=243322313-30032010>looking at the north
exterior windows <SPAN class=415203915-30032010>without any contribution
from</SPAN> the south<SPAN class=415203915-30032010> or any openings
on any intermediate </SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Calibri><FONT color=#0000ff><FONT size=3><SPAN
class=243322313-30032010><SPAN class=415203915-30032010>interior
walls</SPAN><SPAN
class=415203915-30032010>.</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Calibri color=#0000ff size=3><SPAN
class=243322313-30032010></SPAN></FONT> </DIV>
<DIV><FONT face=Calibri color=#0000ff size=3><SPAN class=243322313-30032010>I
think you get the LS-M for <SPAN class=415203915-30032010>just </SPAN>the
first reference point. LS-G and LV-L might be able to provide averaged numbers
though. If you do</SPAN></FONT></DIV>
<DIV><FONT face=Calibri color=#0000ff size=3><SPAN class=243322313-30032010>need
the LS-M for the other reference point, you could reverse number them<SPAN
class=415203915-30032010>, or define just the sensor you want</SPAN>, and
rerun the simulation.</SPAN></FONT></DIV>
<DIV><FONT face=Calibri color=#0000ff size=3><SPAN
class=243322313-30032010></SPAN></FONT> </DIV>
<DIV><FONT face=Calibri color=#0000ff size=3><SPAN class=243322313-30032010>Per
my past <SPAN class=415203915-30032010>trials</SPAN> with using daylighting
in eQUEST, footcandle levels will be calculated at reference points placed
outside</SPAN></FONT></DIV>
<DIV><FONT face=Calibri color=#0000ff size=3><SPAN class=243322313-30032010>the
primary space to be daylit, or for that matter even if they are placed outside
the building, as long as the primary space has</SPAN></FONT></DIV>
<DIV><SPAN class=243322313-30032010></SPAN><SPAN class=243322313-30032010><FONT
face=Calibri><FONT color=#0000ff><FONT size=3>one window on an exterior
wall<SPAN class=415203915-30032010>, and sensors are tied to this space. Outdoor
sensors in this case do not measure exterior
</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=243322313-30032010><FONT face=Calibri><FONT color=#0000ff><FONT
size=3><SPAN class=415203915-30032010>illumination though, which ideally would
be in 1000's of footcandles. </SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><FONT face=Calibri color=#0000ff size=3><SPAN
class=243322313-30032010></SPAN></FONT> </DIV>
<DIV><FONT face=Calibri color=#0000ff size=3><SPAN class=243322313-30032010>Even
if you have an interior wall (or more than 1 wall) separating 2 spaces, you will
get footcandle levels calculated at the other</SPAN></FONT></DIV>
<DIV><SPAN class=243322313-30032010></SPAN><FONT face=Calibri color=#0000ff
size=3><SPAN class=243322313-30032010>reference points. Again, the condition
seems to be that the sensors should be defined in relation to <SPAN
class=415203915-30032010>a</SPAN> primary space which has</SPAN></FONT></DIV>
<DIV><FONT face=Calibri><FONT color=#0000ff><FONT size=3><SPAN
class=243322313-30032010>to have an </SPAN><SPAN
class=243322313-30032010>exterior wall window opening. <SPAN
class=415203915-30032010>Since this does not reflect reality, I am not sure how
to approach this issue. I think all</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Calibri><FONT color=#0000ff><FONT size=3><SPAN
class=243322313-30032010><SPAN class=415203915-30032010>interior walls are
basically ignored for side-lighting
calculations.</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Calibri color=#0000ff size=3><SPAN
class=243322313-30032010></SPAN></FONT> </DIV>
<DIV><FONT face=Calibri><FONT color=#0000ff><FONT size=3><SPAN
class=243322313-30032010>This topic has <SPAN class=415203915-30032010>most
probably</SPAN> been discussed here in the past, but in
short, </SPAN><SPAN class=243322313-30032010>the recommendation would be to use
a separate daylighting </SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Calibri><FONT color=#0000ff><FONT size=3><SPAN
class=243322313-30032010>program </SPAN><SPAN class=243322313-30032010>(<SPAN
class=415203915-30032010>which you are trying to avoid using I gather</SPAN>) to
independently calculate daylighting levels in your spaces<SPAN
class=415203915-30032010>.</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Calibri color=#0000ff><SPAN
class=243322313-30032010></SPAN></FONT> </DIV>
<DIV><FONT face=Calibri color=#0000ff><SPAN
class=243322313-30032010></SPAN></FONT> </DIV></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><BR></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Nick Caton
[mailto:ncaton@smithboucher.com] <BR><B>Sent:</B> Tuesday, March 30, 2010 11:13
AM<BR><B>To:</B> Umesh Atre;
equest-users@lists.onebuilding.org<BR><B>Subject:</B> RE: [Equest-users]
Daylight sensor placement question<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Umesh – you are understanding
the layout correctly =). <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 could apportion some fraction
of the classroom’s LPD to the corridor, and then locate a sensor in the corridor
to control that resulting fraction of lighting. This workaround would be
perfect, though it’s a bit of extra work that I’m unsure is necessary… For
all I know, these photocells are working correctly, but I am not sure how to
verify that since the appropriate LS-M reports aren’t being
generated!<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">Ideally, I would like the energy
model to have the photocell in the corridor control a fraction of the lights in
the classroom – if only because it would be less work and match the true design
(open loop photocell controls). <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">Regardless of whether this is
actually working, I’d really like to know whether photocells outside of the
controlled zone, irrespective of any relative window locations (or even better,
outside of the building perimeter) can correctly measure and report daylight,
accounting for specified building/site shades. I understand this
would be bending the current intent of the photocells as defined in eQuest, as
they’re intended to vary light levels based on closed loop controls (measuring
ambient+daylighting at the work surface in question). This might help
bridge a gap between syncing measured/modeled daylight behavior to an energy
model to accurately approximate open loop design behavior.<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</SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><IMG id=_x0000_i1027 height=37
alt=cid:489575314@22072009-0ABB src="cid:415203915@30032010-0C95"
width=119></SPAN><B><SPAN
style="COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'"><o:p></o:p></SPAN></B></P>
<P class=MsoNormal><B><SPAN
style="COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'"><o:p> </o:p></SPAN></B></P>
<P class=MsoNormal><B><SPAN
style="COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'">NICK CATON,
E.I.T.</SPAN></B><B><SPAN
style="FONT-SIZE: 12pt; COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'"><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; COLOR: #cc9900; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">25501 west
valley parkway<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">olathe ks
66061<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">direct 913
344.0036<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">fax 913
345.0617<o:p></o:p></SPAN></P>
<P class=MsoNormal><I><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">Check out
our new web-site @ </SPAN></I><SPAN style="COLOR: #1f497d"><A
title=blocked::www.smithboucher.com href="www.smithboucher.com"><SPAN
style="FONT-SIZE: 10pt">www.smithboucher.com</SPAN></A></SPAN><U><SPAN
style="FONT-SIZE: 10pt; 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-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Umesh Atre
[mailto:umesh@innovativedesign.net] <BR><B>Sent:</B> Tuesday, March 30, 2010
9:26 AM<BR><B>To:</B> Nick Caton;
equest-users@lists.onebuilding.org<BR><B>Subject:</B> RE: [Equest-users]
Daylight sensor placement question<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt; COLOR: blue">If I may ask a
question:</SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt; COLOR: blue">It looks like you
have the 2nd sensor located in a corridor the south side of
which is a glass wall. If I understand this correctly,</SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt; COLOR: blue">why would you not
define the sensor as part of that corridor zone instead of the north
zone? </SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt; COLOR: blue">Maybe a section or
3d of this space would help.</SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"> <o:p></o:p></SPAN></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <B>On Behalf Of </B>Nick
Caton<BR><B>Sent:</B> Monday, March 29, 2010 11:58 AM<BR><B>To:</B>
equest-users@lists.onebuilding.org<BR><B>Subject:</B> [Equest-users] Daylight
sensor placement question</SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal>Hey all!<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Daylight sensor placement question (see highlighted space in
attached screengrab for an illustration):<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I have a classroom with North and South daylight transition
windows, and a corresponding North and South daylighting “zone.” The North
side is easy – those windows are on the envelope wall, so I’m sure the daylight
is correctly being measured/modeled within the space for the “North zone” sensor
to pick up on.<o:p></o:p></P>
<P class=MsoNormal>The south windows however are in an internal wall, and on the
other side is a “glass box” corridor. Rather than pursue the fuzzy route
of trying to model daylight transitioning between zones correctly (if anyone can
fully digest the help file for INSIDE-VIS-REFL I would really appreciate the
layman’s explanation), I’ve taken the “easy” route and located the daylight
sensor in the corridor. This happens to conveniently match the actual
design location of the photocell. <o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>My question has two parts:<o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN
style="FONT-FAMILY: Symbol">·</SPAN><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'">
</SPAN>Can a zone’s daylight sensor be located in another zone and measure light
in a remote location? If so, are any extra steps necessary?<o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN
style="FONT-FAMILY: Symbol">·</SPAN><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'">
</SPAN>I see my eQuest project is, on its own, generating an LS-M report for
each “Daylight Illuminance Ref Pnt 1.” What is the procedure to generate
the same reports for “Ref Pnt 2” where those occur? <o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>~Nick<o:p></o:p></P>
<P class=MsoNormal><IMG id=Picture_x0020_1 height=37
alt=cid:489575314@22072009-0ABB src="cid:415203915@30032010-0C95" width=119
border=0><B><SPAN
style="COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'"><o:p></o:p></SPAN></B></P>
<P class=MsoNormal><B><SPAN
style="COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'"><o:p> </o:p></SPAN></B></P>
<P class=MsoNormal><B><SPAN
style="COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'">NICK CATON,
E.I.T.</SPAN></B><B><SPAN
style="FONT-SIZE: 12pt; COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'"><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; COLOR: #cc9900; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">25501 west
valley parkway<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">olathe ks
66061<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">direct 913
344.0036<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">fax 913
345.0617<o:p></o:p></SPAN></P>
<P class=MsoNormal><I><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">Check out
our new web-site @ </SPAN></I><SPAN style="COLOR: #1f497d"><A
title=blocked::www.smithboucher.com href="www.smithboucher.com"><SPAN
style="FONT-SIZE: 10pt">www.smithboucher.com</SPAN></A></SPAN><U><SPAN
style="FONT-SIZE: 10pt; COLOR: blue"> </SPAN></U><SPAN
style="COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=MsoNormal><o:p> </o:p></P></DIV></BODY></HTML>