<!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: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 = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.5848" name=GENERATOR>
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Garamond;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","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
}
SPAN.EmailStyle17 {
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="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 vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=196021119-07082009><FONT face=Arial
color=#0000ff size=2>Vikram,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=196021119-07082009></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=196021119-07082009> <FONT
face=Arial color=#0000ff size=2>In answer to your question - in the "space
properties" section, it asks for illuminance (footcandles), ceiling-to-luminary
distance (feet), and workplane height (feet). In the "lighting systems"
section, it asks for total lamp lumens and for the coefficient of
utilization.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=196021119-07082009> <FONT
face=Arial color=#0000ff size=2>That having been said, B. Fountain has kindly
addressed my question. The upshot is that the photometric data is not
necessary or relevant if use the "luminaire count" lighting data input method in
the "space properties" section and have properly defined the electrical power
used by each lighting system. The photometric data is relevant only if I
intend eQuest to calculate the quantity of fixtures necessary to enforce a
certain level of illumination.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=196021119-07082009> <FONT
face=Arial color=#0000ff size=2>As for your advising me to right-click for help
- thanks very much! Previously, I went to "help" through the menu
system, which gives me just about nothing.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=196021119-07082009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=196021119-07082009><FONT face=Arial
color=#0000ff size=2>Lars Fetzek, EI</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=196021119-07082009><FONT face=Arial
color=#0000ff size=2>Phoenix Engineering Group</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=196021119-07082009><FONT face=Arial
color=#0000ff size=2>Tampa, Florida</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Vikram Sami
[mailto:VSami@lasarchitect.com] <BR><B>Sent:</B> Thursday, August 06, 2009 5:18
PM<BR><B>To:</B> Lars Fetzek;
equest-users@lists.onebuilding.org<BR><B>Subject:</B> RE: [Equest-users] Data
Entry<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Lars,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I’m
intrigued by this – I’ve never had to input photometric data. What exactly was
it asking you for?<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">With
regards to your second question, you typically specify only one (either
cfm/person or cfm.ft2 or total cfm). If you have issues with any of these
commands try right clicking and going to either topic help, or item help for
more specific help. eQUEST has pretty good help files. For instance when
you go to item help under the Outside airflow, you get the text
below:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal
style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><B><SPAN
style="FONT-SIZE: 10pt">OUTSIDE-AIR-FLOW<o:p></o:p></SPAN></B></P>
<P class=MsoNormal
style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">The minimum flow
rate of outside ventilation air for the zone. Alternatively, or additionally,
outside air flow rate may be specified by the keywords OA-FLOW/PER and
OA-CHANGES (or by SYSTEM:MIN-OUTSIDE-AIR). The program calculates outside air
flow rate based on each entry and normally uses the larger value except if it
sees data entry for OUTSIDE-AIR-FLOW, which overrides other values. Note that
specifying outside ventilation air at the zone level takes precedence over
specifying it at the system level. Although the specified quantities may be
modified by the program for the sake of consistency, the flow of outside
ventilation air is an uninterrupted flow as long as the fans are operating. The
outside ventilation air quantity is not determined by the design space heating
or cooling demands except when an economizer is specified. Use either
OUTSIDE-AIR-FLOW or OA-FLOW/PER or OA-CHANGES.<o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Hope
this helps<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal style="mso-margin-top-alt: auto"><B><SPAN
style="COLOR: black; FONT-FAMILY: 'Garamond','serif'">Vikram
Sami,</SPAN></B><SPAN style="COLOR: #1f497d"> </SPAN><SPAN
style="COLOR: black; FONT-FAMILY: 'Garamond','serif'">LEED AP</SPAN><SPAN
style="COLOR: #1f497d"> <BR></SPAN><SPAN
style="COLOR: black; FONT-FAMILY: 'Garamond','serif'">Direct Phone 404-253-1466
| Direct Fax 404-253-1366</SPAN><SPAN style="COLOR: #1f497d">
<o:p></o:p></SPAN></P>
<P class=MsoNormal style="mso-margin-bottom-alt: auto"><B><SPAN
style="COLOR: maroon; FONT-FAMILY: 'Garamond','serif'">L</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: 'Garamond','serif'">ORD</SPAN></B><B><SPAN
style="COLOR: maroon; FONT-FAMILY: 'Garamond','serif'">, A</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: 'Garamond','serif'">ECK</SPAN></B><B><SPAN
style="COLOR: maroon; FONT-FAMILY: 'Garamond','serif'"> &
S</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: 'Garamond','serif'">ARGENT</SPAN></B><B><SPAN
style="COLOR: maroon; FONT-FAMILY: 'Garamond','serif'"> A</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: 'Garamond','serif'">RCHITECTURE</SPAN></B><B><SPAN
style="COLOR: #1f497d"><BR><BR></SPAN></B><SPAN
style="COLOR: #1f497d"><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><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'">
equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <B>On Behalf Of </B>Lars
Fetzek<BR><B>Sent:</B> Thursday, August 06, 2009 3:47 PM<BR><B>To:</B>
equest-users@lists.onebuilding.org<BR><B>Subject:</B> [Equest-users] Data
Entry<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Fellow
eQuesters,</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">
I'm sorry to continue posting such basic questions, but I am, as usual,
lost.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"> It
seems that entering data for lighting and for HVAC (in the detailed model)
involves hundreds of fields, many of which really don't seem relevant. For
example, the lighting fields include many questions about photometrics.
However, obviously, if I have a lighting time schedule and the lighting
systems defined, I should be able, using simple arithmetic, to calculate how
much energy it uses. However, eQuest wants a bunch of other
information (such as photometrics), which has taken me forever to
calculate. However, I dare not omit such data since I don't know what
eQuest's algorithms are.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"> I
am just starting to model the HVAC systems and things appear even worse. I
don't need eQuest to design the systems for me. The systems exist on
paper. How do I eliminate all of the irrelevant fields and just enter the
important stuff that actually describes my systems? I am especially
perplexed when there are three fields asking for A, B, and the ratio of A to
B. Why doesn't it just ask for two rather than all three such data?
What if a user enters conflicting data, such as A=2, B=3, and A/B=7?
Again, it is alot like the lighting: I don't care about CFM/person or
CFM/sq-ft. I have the CFM, the number of people, and the square feet for a
zone. How can avoid the hundreds of questions?</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">
Any ideas? How can I tell what fields eQuest will actually use in doing
the energy modeling so that I can ignore the rest?</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Lars Fetzek,
EI</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Phoenix Engineering
Group</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Tampa,
Florida</SPAN><o:p></o:p></P></DIV></DIV></BODY></HTML>