<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Times New Roman, Times, serif"> I just wanted to add my
2 cents worth on the Trace HAP issue and Nick's comment they should add
compatibility to </font>eQuest. I fully agree they should. More and
more of my specifying work is required to be generic. I refuse to pay
either Carrier or Trane to use their program and do all their work for
them. Both programs are very good but they are basically an auto-size
program for either Carrier or Trane products. You have to admire the
marketing aspect but with eQuest being a free generic program both
companies have lost the war. The specifying engineer pays good money
to use their proprietary program, does all the work getting the project
model built and working, sends the model to them, they press the button
and the whole job is itemized and costed, they just have to fill out
the bid forms. The company which lost has to take the paper spec,
build the model in their proprietary program, get it running and then
output the job with their units. I'm not sure how a lot of this works
now as I'm mostly in the generic world but in decades past Trane and
Carrier would battle to be the named manufacturer on a job. There was
major assistance from their engineers in doing the spec. In
recognition of the assistance, if you were willing to load their
auto-size program for them you could/would receive a free seat. Your
recognition for them is their name on the project units and the job
input handed to them on a platter. The downside of this system is both
companies know each others units intimately. Some jobs can be
configured/manipulated to put the other company at a disadvantage,
sometimes to the detriment of the owners system. As software, eQuest
does compete with HAP and Trace. But the money for a modelling program
pales compared the the real work of winning a job. This is why both
Trane and Carrier will give their program away free to their favourite
specifying engineers. They just off loaded a major part of the work to
be able to bid a job. Their major competitor is behind the 8 ball
because they are starting from scratch to bid the job (and every other
smaller company). eQuest could actually make everyones job easier,
maybe Carrier and Trane could throw some money or expertise into eQuest
to help make it better and compatible with their programs. The
modelling job would only get done once, each company could take the
file and convert it to their program, press the button and be ready to
bid the job. It would also get the owner a better job. Both Carrier
and Trane can easily check and tweak the job, probably provide some
very good ideas to make the project better. Face it both those
companies have some major engineering horsepower, and can provide
valuable input. They would lose a marketing device but in the end I
believe it would save them a lot of money reworking jobs they didn't
get the specification on. Ultimately they would be able to bid more
jobs, sell more units, make more money. The customer would get a
better system as well because money wasted on the dance could be
applied to making the job better. Equest could be made better faster
with their help. I think everyone would benefit.<br>
Nice shot Carol<span class="moz-smiley-s1"><span> :-) </span></span>.<br>
Bruce Easterbrook P.Eng.<br>
Abode Engineering<br>
<br>
On 16/07/2010 10:54 AM, Nick Caton wrote:
<blockquote
cite="mid:FCEBC0C28321F7479789B25A13030F6901356E99@sandbinc2.sbi.smithboucher.com"
type="cite">
<meta http-equiv="Content-Type"
content="text/html; charset=ISO-8859-1">
<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: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;}
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";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@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="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Carol
I think I can fill in a response:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">More
often than not, big complicated energy modeling projects
typically result in another individual doing the HVAC design. When
that
other person regularly uses HAP and/or Trace to run sizing loads, we
ultimately
have to butt heads to be sure eQuest is arriving at similar answers,
and it usually
is off in one zone or another by a big factor. Quirks like
unexpectedly
huge people densities or particular OA requirements get missed by
eQuest’s
occupancy libraries.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">The
concept of being able to get to a certain point of the
energy model, avoiding inputting any system sizing parameters
(Auto-size CFM’s,
capacities, etc), and then import such information from another’s work
(rather than doing it by hand from cryptic output reports), is really
appealing
as that’s a part of the job that’s both un-fun and drawn out.
It does encourage using the model to tweak the HVAC design process to a
more
intimate degree than we might otherwise, once the two sets of results
are
calibrated to each other, which I think is great.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Envisioning
this, I think it would manifest as an option in
Trace or HAP (or similar loads program) to create a text file (*.inp)
containing the variables you’d want to import located under the
respective zones/systems. There would have to be some graphic/visual
means of telling Trace/HAP the cryptic zone/system names generated by
eQuest to
make this a time-efficient feature.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">To
Matthew’s question, I’m afraid this concept will
be remaining in perpetual la-la-land unless Trane or Carrier
decide/realize
they might get a lot more business by assigning this interoperability
feature to
their respective software developers. As they both perceive their
software packages as “competitors,” to eQuest, I don’t see it
happening anytime soon, but I’ve been wrong before!<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">I
have heard scattered reports (and even seen a few screenshots)
of people in the “real world” managing to get GBS/Revit to
interface via export into eQuest – but my personal attempts (3 times)
have all failed along the way… it seems rooted to model manipulations
that Revit MEP cannot do, which Architectural can (and we don’t have
the
budget for) that are required for a clean export. To my limited
understanding, with this process you’re getting geometries (polygons,
surfaces) defined, and possibly spaces/zones and constructions, but
beyond that
you’re left to do everything else without the wizards.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">~Nick<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">PS:
If any man wants to contribute woman-hours (or vice versa, I
won’t judge!) to making that eQuest-wiki concept happen, then make it
known =). By contributing, I’m explicitly suggesting being willing
to write up one or more articles, mini-guides, or how-to’s.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><img
id="Picture_x0020_1" src="cid:part1.01080501.06020300@bellnet.ca"
alt="cid:489575314@22072009-0ABB" height="37" width="119"></span><b><span
style="font-size: 11pt; font-family: "Stylus BT","sans-serif"; color: rgb(45, 77, 94);"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-size: 11pt; font-family: "Stylus BT","sans-serif"; color: rgb(45, 77, 94);"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-size: 11pt; font-family: "Stylus BT","sans-serif"; color: rgb(45, 77, 94);">NICK
CATON, E.I.T.</span></b><b><span
style="font-family: "Stylus BT","sans-serif"; color: rgb(45, 77, 94);"><o:p></o:p></span></b></p>
<p class="MsoNormal"><span
style="font-size: 7.5pt; font-family: "Calibri","sans-serif"; color: rgb(204, 153, 0);">PROJECT
ENGINEER</span><span style="font-size: 7.5pt; color: rgb(204, 153, 0);"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: rgb(45, 77, 94);">25501
west valley parkway<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: rgb(45, 77, 94);">olathe
ks 66061<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: rgb(45, 77, 94);">direct
913 344.0036<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: rgb(45, 77, 94);">fax
913 345.0617<o:p></o:p></span></p>
<p class="MsoNormal"><i><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: rgb(45, 77, 94);">Check
out our new web-site @ </span></i><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><a
moz-do-not-send="true" href="www.smithboucher.com"
title="blocked::www.smithboucher.com"><span style="font-size: 10pt;">www.smithboucher.com</span></a></span><u><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: blue;">
</span></u><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<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";">
<a class="moz-txt-link-abbreviated" href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a>
[<a class="moz-txt-link-freetext" href="mailto:equest-users-bounces@lists.onebuilding.org">mailto:equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>Carol
Gardner<br>
<b>Sent:</b> Thursday, July 15, 2010 10:05 PM<br>
<b>To:</b> Matthew W. Higgins<br>
<b>Cc:</b> eQuest user forum<br>
<b>Subject:</b> Re: [Equest-users] eQuest Wiki & Other Question<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom: 12pt;">Sorry, Matthew, but
I can't
resist this: if they were "woman-hours" at stake there would be fewer
and the outcome better. You left yourself wide open for that one!<br>
<br>
Related to your second paragraph, can you give me an example of why you
would
want to go from eQUEST to XML/Trace? I am stumped as to why you want to
do such
a thing.<br>
<br>
Carol<o:p></o:p></p>
<div>
<p class="MsoNormal">On Thu, Jul 15, 2010 at 1:51 PM, Matthew W.
Higgins <<a moz-do-not-send="true" href="mailto:MWHiggins@bpce.com">MWHiggins@bpce.com</a>>
wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="">Seems
like a lot of the traffic lately (past month or so) could be lightened
by the
eQuest Wiki that was mentioned. Anything come of that? Of course,
keeping
respectful of the fact that these are man-hours at stake to create it
all.<o:p></o:p></p>
<p class="MsoNormal" style=""> <o:p></o:p></p>
<p class="MsoNormal" style="">Also,
unrelated, I’m aware of the workflow using GreenBuilding Studio to go
from Revit to eQuest and the ability to bring XML into Trace, but is
there a
workflow to go from eQuest BDL to Trace or back out to an XML, file
then into
Trace? Seems like GBS could go from eQuest to XML/Trace, primarily for
time
savings when creating geometries.<o:p></o:p></p>
<p class="MsoNormal" style=""> <o:p></o:p></p>
<p class="MsoNormal" style="">Thoughts?
Thanks.<o:p></o:p></p>
<p class="MsoNormal" style=""> <o:p></o:p></p>
<p class="MsoNormal" style="">Matthew
Higgins, ASHRAE-HBDP, LEED-AP<o:p></o:p></p>
<p class="MsoNormal" style=""><i>Energy
Engineer</i><o:p></o:p></p>
<p class="MsoNormal" style=""><b><span
style="color: rgb(15, 15, 101);"> </span></b><o:p></o:p></p>
<p class="MsoNormal" style=""><b><span
style="color: rgb(15, 15, 101);">Bridgers & Paxton Consulting
Engineers, Inc.</span></b><o:p></o:p></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; color: rgb(15, 15, 101);">4600-C Montgomery
Blvd. NE</span><o:p></o:p></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; color: rgb(15, 15, 101);">Albuquerque, NM
87109</span><o:p></o:p></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; color: rgb(15, 15, 101);">505-883-4111</span><o:p></o:p></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; color: rgb(15, 15, 101);">505-888-1436 Fax</span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: rgb(0, 32, 96);"><a
moz-do-not-send="true" href="mailto:mwhiggins@bpce.com" target="_blank">mwhiggins@bpce.com</a>
</span><o:p></o:p></p>
<p class="MsoNormal" style=""> <o:p></o:p></p>
<p class="MsoNormal" style=""><b><span
style="color: rgb(79, 129, 189);"><a moz-do-not-send="true"
href="http://www.bpce.com" target="_blank">www.bpce.com</a></span></b><o:p></o:p></p>
<p class="MsoNormal" style=""> <o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><br>
_______________________________________________<br>
Equest-users mailing list<br>
<a moz-do-not-send="true"
href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org"
target="_blank">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><br>
To unsubscribe from this mailing list send a blank message to <a
moz-do-not-send="true"
href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <br>
Carol Gardner PE<o:p></o:p></p>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Equest-users mailing list
<a class="moz-txt-link-freetext" href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a>
To unsubscribe from this mailing list send a blank message to <a class="moz-txt-link-abbreviated" href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a>
</pre>
</blockquote>
</body>
</html>