<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)">
<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:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* 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;}
span.EmailStyle17
{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='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Lars,<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 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: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'>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:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><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:10.0pt'>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:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hope this 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'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto'><b><span style='font-family:
"Garamond","serif";color:black'>Vikram Sami,</span></b><span style='color:#1F497D'>
</span><span style='font-family:"Garamond","serif";color:black'>LEED AP</span><span
style='color:#1F497D'> <br>
</span><span style='font-family:"Garamond","serif";color:black'>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='font-family:"Garamond","serif";color:maroon'>L</span></b><b><span
style='font-size:10.0pt;font-family:"Garamond","serif";color:maroon'>ORD</span></b><b><span
style='font-family:"Garamond","serif";color:maroon'>, A</span></b><b><span
style='font-size:10.0pt;font-family:"Garamond","serif";color:maroon'>ECK</span></b><b><span
style='font-family:"Garamond","serif";color:maroon'> & S</span></b><b><span
style='font-size:10.0pt;font-family:"Garamond","serif";color:maroon'>ARGENT</span></b><b><span
style='font-family:"Garamond","serif";color:maroon'> A</span></b><b><span
style='font-size:10.0pt;font-family:"Garamond","serif";color:maroon'>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: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"'>
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:10.0pt;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:10.0pt;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:10.0pt;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:10.0pt;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:10.0pt;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:10.0pt;font-family:"Arial","sans-serif"'>Lars
Fetzek, EI</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Phoenix
Engineering Group</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Tampa,
Florida</span><o:p></o:p></p>
</div>
</div>
</body>
</html>