<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)">
<!--[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: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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-believe-normal-left:yes;}
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";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
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;
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 mso 9]>
<style>
p.MsoNormal
{margin-left:3.0pt;}
</style>
<![endif]><!--[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]-->
</head>
<body lang=EN-US link=blue vlink=purple style='margin-left:3.0pt;margin-top:
3.0pt;margin-right:3.0pt;margin-bottom:.75pt'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I agree with Mr. Walkes, we use HAP support when needed.<o:p></o:p></span></p>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#333333'>If
you have any questions, please do not hesitate to contact me. <o:p></o:p></span></p>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><span
style='font-size:10.5pt;font-family:"Arial","sans-serif";color:#333333'>Larry
Schultz, PE, LEED AP</span></b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#333333'><br>
</span><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:#333333'>Sr. Mech. Engineer </span><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#333333'><o:p></o:p></span></p>
</div>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 align=left
width=600 style='width:6.25in'>
<tr>
<td style='border:none;border-top:solid #99CCE6 1.0pt;padding:0in 0in 0in 15.0pt'>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;line-height:11.25pt;
mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;
mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;
mso-height-rule:exactly'><b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#333333'>Work:</span></b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#333333'> 410-316-7800 ext. 1511 </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#333333'>KCI
Technologies, Inc. </span><span style='font-size:8.5pt;font-family:
"Arial","sans-serif";color:#333333'><o:p></o:p></span></p>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;line-height:11.25pt;
mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;
mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;
mso-height-rule:exactly'><b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#333333'>Fax</span></b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#333333'>: 410-316-7868 936
Ridgebrook Rd<br>
<b>Mobile:</b> 410-746-6768 Sparks, MD
21152 USA<br>
<b>Email:</b> <a href="mailto:Larry.Schultz@kci.com" target=nw><span
style='color:#333333;text-decoration:none'>Larry.Schultz@kci.com</span></a><br>
<img border=0 width=14 height=14 id="Picture_x0020_1"
src="cid:image001.gif@01CAAEF2.D3A16990"
alt="http://www.linkedin.com/img/signature/icon_in_blue_14x14.gif"> <b><a
href="http://www.linkedin.com/pub/12/251/677" target=nw>Professional Profile</a><o:p></o:p></b></span></p>
</td>
</tr>
</table>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#333333'><br>
</span><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:red'>CONFIDENTIALITY NOTICE:</span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:8.0pt;font-family:"Arial","sans-serif";color:red'>This email
may contain confidential information that is legally privileged.
This information is intended for the use of the named recipient(s). The
authorized recipient of this information is prohibited from disclosing this
information to any party unless required to do so by law or regulation and is
required to destroy the information after its stated need has been
fulfilled. If you are not the intended recipient, you are hereby notified
that any disclosure, copying, distribution, or action taken in reliance on the
contents of this email is strictly prohibited. If you receive this e-mail
message in error, please notify the sender immediately to arrange disposition
of the information.</span><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 style='margin:0in;margin-bottom:.0001pt'><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"'>
hap-users-bounces@lists.onebuilding.org
[mailto:hap-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Stirling
Walkes<br>
<b>Sent:</b> Tuesday, February 16, 2010 10:26 AM<br>
<b>To:</b> hap-users@lists.onebuilding.org; Jason Humbert<br>
<b>Subject:</b> Re: [Hap-users] Hap-users Digest, Vol 11, Issue 2<o:p></o:p></span></p>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>I tend to use HAP
support when required.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> V. Stirling
Walkes, P.Eng., LEED AP<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Partner<br>
SMS Engineering Ltd.<br>
770 Bradford Street <br>
Winnipeg MB R3H 0N3 Canada<br>
p: 204.775.0291<br>
f: 204.772.2153<br>
e: <a href="mailto:swalkes@smseng.com">swalkes@smseng.com</a><o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br>
<br>
>>> "Jason Humbert" <jhumbert@sesnet.com> 2/16/2010
8:28 AM >>><br>
Does anyone ever have questions or problems with HAP or does everyone<br>
use the HAP support. <br>
<br>
Jason Humbert<br>
<br>
4000 W. Eleven Mile Rd.<br>
Berkley, MI 48072<br>
p: 248.399.1900 ex. 215 <br>
f: 248.399.1901<br>
jhumbert@sesnet.com<br>
<br>
-----Original Message-----<br>
From: hap-users-bounces@lists.onebuilding.org<br>
[mailto:hap-users-bounces@lists.onebuilding.org] On Behalf Of<br>
hap-users-request@lists.onebuilding.org<br>
Sent: Wednesday, January 27, 2010 3:03 PM<br>
To: hap-users@lists.onebuilding.org<br>
Subject: Hap-users Digest, Vol 11, Issue 2<br>
<br>
Send Hap-users mailing list submissions to<br>
hap-users@lists.onebuilding.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<br>
<a href="http://lists.onebuilding.org/listinfo.cgi/hap-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/hap-users-onebuilding.org</a><br>
or, via email, send a message with subject or body 'help' to<br>
hap-users-request@lists.onebuilding.org<br>
<br>
You can reach the person managing the list at<br>
hap-users-owner@lists.onebuilding.org<br>
<br>
When replying, please edit your Subject line so it is more specific than<br>
"Re: Contents of Hap-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. CfP: Workshop on Collaborative Modeling and Simulation<br>
(CoMetS) (Daniele Gianni)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 27 Jan 2010 20:10:44 +0100<br>
From: Daniele Gianni <daniele.gianni@gmail.com><br>
To: hap-users@lists.onebuilding.org<br>
Subject: [Hap-users] CfP: Workshop on Collaborative Modeling and<br>
Simulation(CoMetS)<br>
Message-ID:<br>
<7fc6c6431001271110u2689c1acmf18edf0e25138643@mail.gmail.com><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
#################################################################<br>
IEEE WETICE 2010<br>
1st International Workshop on<br>
Collaborative Modeling and Simulation<br>
CALL FOR PAPERS<br>
#################################################################<br>
<br>
June 28 - June 30, 2010, Larissa (Greece) *<br>
**http://www.sel.uniroma2.it/CoMetS10*<br>
<<a href="http://www.sel.uniroma2.it/CoMetS10">http://www.sel.uniroma2.it/CoMetS10</a>><br>
<br>
#################################################################<br>
# Papers Due: *** March 2, 2010 ***<br>
# Accepted papers will be published in the conference proceedings # by<br>
the IEEE Computer Society Press and indexed by EI.<br>
#################################################################<br>
<br>
Modeling and Simulation (M&S) is increasingly becoming a central<br>
activity in the design of new systems and in the analysis of existing<br>
systems because it enables designers and researchers to investigate<br>
systems behavior through virtual representations. For this reason, M&S<br>
is gaining a primary role in many industrial and research fields, such<br>
as space, critical infrastructures, manufacturing, emergency management,<br>
biomedical systems and sustainable future. However, as the complexity of<br>
the investigated systems increases and the types of investigations<br>
widens, the cost of M&S activities increases because of the more complex<br>
models and of the communications among a wider number and variety of M&S<br>
stakeholders (e.g., sub-domain experts, simulator users, simulator<br>
engineers, and final system users). To address the increasing costs of<br>
M&S activities, collaborative technologies must be introduced to support<br>
these activities by fostering the sharing and reuse of models, by<br>
facilitating the communications among M&S stakeholders, and more<br>
generally by integrating processes, tools and platforms.<br>
<br>
Aside from seeking applications of collaborative technologies to M&S<br>
activities, the workshop seeks innovative contributions that deal with<br>
the application of M&S practices to the design of collaborative<br>
environments. These environments are continuously becoming more complex<br>
and therefore their design requires systematic approaches to meet the<br>
required quality of collaboration. This is important for two reasons: to<br>
reduce rework activities on the actual collaborative environment, and to<br>
maximize the productivity and the quality of the process the<br>
collaborative environment supports. M&S offers the methodologies and<br>
tools for such investigations and therefore it can be used to improve<br>
the quality of collaborative environments.<br>
<br>
A non-exhaustive list of hi-level topics includes:<br>
<br>
* collaborative environments for M&S<br>
* agent-based M&S<br>
* collaborative distributed simulation<br>
* net-centric M&S<br>
* web-based M&S<br>
* model sharing and reuse<br>
* model building and evaluation<br>
* modeling and simulation of business processes<br>
* modeling for collaboration<br>
* simulation-based performance evaluation of collaborative<br>
networks<br>
* model-driven simulation engineering<br>
* domain specific languages for the simulation of collaborative<br>
environments<br>
* domain specific languages for collaborative M&S<br>
<br>
To stimulate creativity, however, the workshop maintains a wider scope<br>
and invites interested researchers to present contributions that offer<br>
original perspectives on collaboration and M&S.<br>
<br>
+++++++++++++++++++++++++++++++++++<br>
On-Line Submissions and Publication<br>
+++++++++++++++++++++++++++++++++++<br>
<br>
CoMetS'10 intends to bring together researchers and practitioners to<br>
discuss key issues, approaches, open problems, innovative applications<br>
and trends in the workshop research area.<br>
<br>
Papers should contain original contributions not published or submitted<br>
elsewhere. Papers up to six pages (including figures, tables and<br>
references) can be submitted. Papers should follow the IEEE format,<br>
which is single spaced, two columns, 10 pt Times/Roman font. All<br>
submissions should be electronic (in PDF) and will be peer-reviewed by<br>
at least three program committee members.<br>
<br>
Full papers accepted for the workshop will be included in the<br>
proceedings, published by the IEEE Computer Society Press (IEEE approval<br>
pending). Note that at least one author from each accepted paper should<br>
register to attend WETICE 2010 to get the paper published in the<br>
proceedings.<br>
<br>
Authors may contact the organizers for expression of interests and<br>
content appropriateness at any time. Papers can be submitted in PDF<br>
format at the submission site<br>
(*http://www.easychair.org/conferences/?conf=comets10*<<a
href="http://www.easych">http://www.easych</a><br>
air.org/conferences/?conf=comets10>),<br>
which is<br>
supported by the EasyChair conference management system. Please contact<br>
the workshop chairs (*comets10@easychair.org*<comets10@easychair.org>)<br>
if you<br>
experience problems with the EasyChair Web site.<br>
<br>
+++++++++++++++<br>
Important Dates<br>
+++++++++++++++<br>
<br>
* Submission Deadline: March 2, 2010<br>
* Decision to paper authors: April 2, 2010<br>
* Final version of accepted papers due to IEEE: April 14, 2010<br>
* Conference dates: June 28 - June 30, 2010<br>
<br>
++++++++++++++++++++<br>
Organizing Committee<br>
++++++++++++++++++++<br>
<br>
* Andrea D'Ambrogio, University of Roma TorVergata, Italy<br>
* Daniele Gianni, European Space Agency, Netherlands<br>
* Joachim Fuchs, European Space Agency, Netherlands<br>
* Giuseppe Iazeolla, University of Roma TorVergata, Italy<br>
<br>
+++++++++++++++++<br>
Program Committee<br>
+++++++++++++++++<br>
<br>
* Michele Angelaccio, University of Roma TorVergata, Italy<br>
* Olivier Dalle, University of Nice Sophia Antipolis, CNRS & INRIA,<br>
France<br>
* Steve McKeever, University of Oxford, UK<br>
* Alessandra Pieroni, University of Roma TorVergata, Italy<br>
* Andrew Rice, University of Cambridge, UK<br>
* Jos? L. Risco-Martin, Universidad Complutense de Madrid, Spain<br>
* Helena Szczerbicka, University of Hannover, Germany<br>
* Hans Vangheluwe, McGill University, Canada<br>
* Gabriel Wainer, Carleton University, Canada<br>
* J.Chris White, ViaSim Solutions, USA<br>
* Quirien Wijnands, European Space Agency, Netherlands<br>
* Heming Zhang, Tsinghua University, China<br>
<br>
*** Contact Information ***<br>
Andrea D'Ambrogio (workshop co-chair)<br>
Email: *dambro@info.uniroma2.it* <dambro@info.uniroma2.it><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL:<br>
<<a
href="http://lists.onebuilding.org/pipermail/hap-users-onebuilding.org/attach">http://lists.onebuilding.org/pipermail/hap-users-onebuilding.org/attach</a><br>
ments/20100127/a857252c/attachment.html><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Hap-users mailing list<br>
Hap-users@lists.onebuilding.org<br>
<a href="http://lists.onebuilding.org/listinfo.cgi/hap-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/hap-users-onebuilding.org</a><br>
<br>
<br>
End of Hap-users Digest, Vol 11, Issue 2<br>
****************************************<br>
_______________________________________________<br>
Hap-users mailing list<br>
<a href="http://lists.onebuilding.org/listinfo.cgi/hap-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/hap-users-onebuilding.org</a><br>
To unsubscribe from this mailing list send a blank message to
HAP-USERS-UNSUBSCRIBE@ONEBUILDING.ORG<o:p></o:p></span></p>
</div>
</div>
</body>
</html>