<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:"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;}
@font-face
{font-family:"Copperplate Gothic Bold";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{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;}
/* List Definitions */
@list l0
{mso-list-id:1060058925;
mso-list-type:hybrid;
mso-list-template-ids:196898644 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>Stephen,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>In a word, yes – and
suggesting you do it in the detailed mode. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>As a simplified approach for
your example (you might want to define more detail), you might start with 3 fractional
occupancy “Day” schedules:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Regular Day (7-9 only)<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Evening Day (7-9 and
6-8)<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Sunday Day (Sunday
worship hours)<o:p></o:p></span></p>
<p class=MsoListParagraph><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Then, create 1 week schedule and
assign the above day schedules to each day of the week/holidays as may be appropriate:<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Mo – Regular Day<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Tu – Regular Day<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>We – Evening Day<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Th – Regular Day<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Fr – Evening Day<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Sa – Regular Day<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Su – Sunday Day<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Holidays – Sunday Day<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>For the annual occupancy schedule,
assign the same week schedule to every week in the year.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Wrap up by assigning your new
annual occupancy schedule to the appropriate space(s) (right click any space in
the Component Tree/2D view/3D view under the Internal Loads tab).<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>When you have many custom
schedules to define, I think the best approach is to use the wizards to set up your
holidays and seasonal building operating schedules as appropriate, then use the
detailed mode to create/assign new schedules in a way that helps you to find/keep
track of your work. It’s technically possible to define a
fractional occupancy schedules for every zone for every hour of the year (limited
only by the user’s time/sanity, of course). <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Occupancy schedules can be
handled entirely in the wizards if you have one schedule per shell. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>A BIG caution: I made the
mistake once of creating many small shells (>12 - large project) in the
wizards for the express purpose of avoiding dealing with custom schedules in
detailed mode (as I hadn’t done it before) – this was a bad move!
The time “saved” by this approach was completely engulfed by the
time lost wrangling in the detailed mode with the resulting overly-complex
model. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Best of luck,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>~Nick<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='color:#1F497D'><img width=119 height=37
id="Picture_x0020_1" src="cid:image001.jpg@01CADB1E.98BE9890"
alt="cid:489575314@22072009-0ABB"></span><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><b><span style='font-size:12.0pt;
font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</span><span
style='font-size:7.5pt;font-family:"Times New Roman","serif";color:#CC9900'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>25501 west
valley parkway<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>direct 913
344.0036<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>fax 913
345.0617<o:p></o:p></span></p>
<p class=MsoNormal><i><span style='font-size:10.0pt;color:#2D4D5E'>Check out
our new web-site @ </span></i><span style='color:#1F497D'><a
href="www.smithboucher.com" title="blocked::www.smithboucher.com"><span
style='font-size:10.0pt'>www.smithboucher.com</span></a></span><u><span
style='font-size:10.0pt;color:blue'> </span></u><span style='color:#1F497D'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='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>Stephen
Sorensen<br>
<b>Sent:</b> Tuesday, April 13, 2010 3:10 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] daily occupancy schedules<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi everyone,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Does e-Quest allow for multiple usage schedules per day. For
example, a particular religious worship building is primarily used on Sundays,
so, that schedule is easy to enter, however, during the week, the building is
used every day from 7am-9am. The difficult part comes from the fact that two
nights a week it is used from 6p-8p. how can I get e-quest to show this
schedule irregularity?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><span style='font-size:14.0pt;font-family:"Copperplate Gothic Bold";
color:#948A54'>Stephen Sorensen<o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-family:"Copperplate Gothic Bold";
color:#632423'>Hansen Engineering<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Copperplate Gothic Bold";
color:#632423'>Friendsville, PA<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Copperplate Gothic Bold";
color:#632423'>P: 570-553-4284<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Copperplate Gothic Bold";
color:#632423'>F: 570-553-0234<o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>