<BODY><P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: 14.4pt"><SPAN style="FONT-SIZE: 12pt; COLOR: #333333; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial"><FONT face=Calibri>Attached are my views on the eQUEST program.<SPAN style="mso-spacerun: yes"> </SPAN>I tried to compare <FONT color=black>DOE2.1E and eQUEST using a one million square-foot high-rise mixed-use building with about 200 zones</FONT> and several types of systems.<SPAN style="mso-spacerun: yes"> </SPAN>Most of my eQUEST modeling time was spent in trying to get rid of the eQUEST decisions and assumptions made by the wizards so that it matched the DOE2.1E input (the actual project specifications) at every point.<SPAN style="mso-spacerun: yes"> </SPAN>You have to start with the wizard because the best feature of eQUEST – creating the building model, floor plans & zones by tracing AutoCAD drawings – is not available in detailed edit.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></SPAN></P><BR><BR>----- Original Message ----- <BR>From: Karen Walkerman <kwalkerman@gmail.com> <BR>Date: Wednesday, February 25, 2009 5:07 pm <BR>Subject: Re: [Bldg-sim] IES-VE Energy <BR>To: Varkie C Thomas <thomasv@iit.edu> <BR>Cc: Graham Carter & Megan Lyall <hamnmegs@ozemail.com.au>, Varkie Thomas <varkie.thomas@yahoo.com>, bldg-sim@lists.onebuilding.org <BR><BR>> Varkie, <BR>> <BR>> I disagree with your statement that eQuest is not appropriate for <BR>> largebuildings because you can't change space names to match <BR>> architectural names <BR>> in wizard mode, and the inputs created from the wizard aren't <BR>> appropriatefor all spaces. The wizards are called "Schematic <BR>> Design Wizard" and <BR>> "Design Development Wizard" for a reason. They aren't desinged <BR>> for detail, <BR>> they're designed to help you make big design decisions quickly. <BR>> If you want <BR>> the building to be modeled as closely as possible to the final <BR>> design, this <BR>> takes some extra work. Yeah, re-naming spaces is a pain, but at 5 <BR>> secondsper space, re-naming 1,000 spaces takes about 1.5 hours, <BR>> well worth the <BR>> effort. If you re-name zones too, maybe it's 3 hours total. <BR>> <BR>> Yeah, some things about eQuest are clumsy, like why does it create one <BR>> underground wall (and floor) consturction for each surface, when <BR>> only 4-5 <BR>> are needed for the whole model? Why does it re-create occupancy, <BR>> lightingand micellaneous equipment schedules for each shell, even <BR>> if the use is the <BR>> same? And why does it create tons of duplicate infiltration <BR>> schedules?BUT... this takes an hour or two to clean up, and then <BR>> you have a decently <BR>> flexible model that gives you reasonable results in a matter of <BR>> minutes.Versus a program that takes 1-2 hours to run. I've done a <BR>> few LEED projects <BR>> in Trace700 and it's painful modeling a design case and four <BR>> (rotated) base <BR>> cases at 1-2 hours each, especially if you then find you've left <BR>> anythingout. <BR>> <BR>> I definitely agree that there are some major things missing in all <BR>> modelingprograms, which is why I'm putting together a "Master Wish <BR>> List" of <BR>> modeler's desires. If you have things that you would like to be <BR>> able to <BR>> model, things you'd like to be able to model more easily, or <BR>> things that you <BR>> can do that you feel are very important, please send me your list. <BR>> I <BR>> currently have contact info for about 10 people representing various <BR>> simulation programs who want to know what we want! Now's our <BR>> chance to have <BR>> some input! <BR>> <BR>> -- <BR>> Karen <BR>> <BR>> <BR>> <BR>> On Wed, Feb 25, 2009 at 2:15 PM, Varkie C Thomas <thomasv@iit.edu> <BR>> wrote: <BR>> > Graham, <BR>> > <BR>> > The comment below stands out which might also be the reason for <BR>> not using <BR>> > EnergyPlus on large projects. <BR>> > <BR>> > - DOE-2.2 runs much quicker. For comparable 30,000 m2 buildings <BR>> I would <BR>> > say DOE-2 runs in 1 minute and IES VE with an APhvac network <BR>> probably 1-2 <BR>> > hours. If you through in Macroflo it probably adds another hour of <BR>> > simulation time. As a result *iterative trial and error <BR>> debugging* has to <BR>> > be done on a 1-2 week period. <BR>> > <BR>> > Large building projects (1 to 10 million sqft) with up to 1,000 <BR>> zones and <BR>> > 70 systems ranging in size from 10,000 to 200,000 cfm (pardon <BR>> the English <BR>> > units - the USA & the Bahamas are not going to switch to metric) <BR>> require> several iterative runs to get the input errors fixed. <BR>> Breaking up the <BR>> > project into small pieces is not a solution since it affects <BR>> demand costs, <BR>> > central plants and other components. I have worked on such <BR>> projects using <BR>> > DOE2.1E and TRACE600/700. <BR>> > <BR>> > eQUEST is not suitable for such projects either. One of its <BR>> limitations is <BR>> > that you cannot enter the space names shown on architectural <BR>> drawings.> Others include assuming all the input data and making <BR>> all the decisions for <BR>> > you when you enter the type of building. 1000 zones means 1000 <BR>> infiltration> schedules and multiples of other building <BR>> components. It is unrealistic to <BR>> > check all the input created by eQUEST for errors. Fixing <BR>> everything to match <BR>> > the exact project data has to be done in detailed edit. <BR>> Detailed edit means <BR>> > you lose access to the graphical method of creating the building <BR>> model from <BR>> > AutoCAD drawings which is the main benefit of this program. <BR>> > Varkie <BR>> > <BR>> > <BR>> </BODY>