<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* 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.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:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name: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;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1708142341;
mso-list-type:hybrid;
mso-list-template-ids:40805288 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">CNST at NIST has thought about this quite a bit, and we now have a ruleset that I think works pretty well to match reservation time with usage time. I work on the lab logistics
software for CNST, called NEMO, and I can describe the things we’ve implemented.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Up front training – all new users complete a tutorial that’s built into our lab management software, discussing reservation
policy<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">2 hours before their reservation, users are sent an email reminding them they have a reservation coming up<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Missed reservations<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Users are charged a fee for missed reservations – the fee varies per tool<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Users are informed automatically via email that they missed a reservation<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Automated “reservation abuse” reports are available to NanoFab managers<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Reservation abuse is defined as cancelling, moving, or extending a reservation shortly before the reservation would
have started<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">We have some code that will calculate a score for each user<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">NanoFab management can choose to do what they will with this information<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">When a user has finished using a tool, and they “disable” it through NEMO, any remainder of their reservation is relinquished.
This allows other users to see that the tool is available (when someone is done early) and pop in to make a reservation if they’d like<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">A set of reservation and usage parameters that can be tweaked for each tool:<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Reservation horizon – “Users may create reservations this many days in advance (but not beyond the horizon)”<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Minimum usage block time – “The minimum amount of time that a user must reserve this tool for a single reservation”<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Maximum usage block time – “The maximum amount of time that a user may reserve this tool for a single reservation”<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Maximum reservations per day<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Maximum future reservation time – The total maximum amount of time that a user may reserve from the current time onwards<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Missed reservation threshold – The amount of time that a tool reservation may go unused before it is automatically marked
as "missed" and hidden from the calendar. Usage can be from any user, regardless of who the reservation was originally created for<o:p></o:p></span></li></ul>
</li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I hope this helps.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">-- Dylan Klomparens<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> labnetwork-bounces@mtl.mit.edu [mailto:labnetwork-bounces@mtl.mit.edu]
<b>On Behalf Of </b>John D Shott<br>
<b>Sent:</b> Friday, July 14, 2017 9:08 PM<br>
<b>To:</b> Vito Logiudice <vito.logiudice@uwaterloo.ca><br>
<b>Cc:</b> labnetwork@mtl.mit.edu<br>
<b>Subject:</b> Re: [labnetwork] Equipment reservation efficiencies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Vito:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As I no longer am a practicing engineer, you are welcome to take my comments with a grain of salt. Nonetheless, I do have some comments based on prior experience with this topic. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">For starters, since 7x24 = 168 hours, if your evaporator was reserved for 192 hours in a week you have a different problem …<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Nonetheless, my guess is that many folks see "reservation challenges" on their high-demand tools. When a tool is used a lot, I think that folks begin to grab reservation time just in case they need it. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I don't know what reservation system you run, but do you have the ability to make tool-specific reservation rules?If so, things that can help include tinkering with the reservation horizon (how far in advance a reservation can be made),
maximum duration of one or all reservations over that horizon, maximum number of reservations for a single user over that horizon, etc. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Can you track when reservations were made and deleted in addition to the period for which the reservation was made? If so, I expect that you will see evidence of a "feeding frenzy" … many reservations are snapped up as far in the future
as legally allowed by your policies/software. We have seen the use of keystroke automation tools to snap up a reservation the second that a new time slot became available. Even if you don't intend to use it, having reservations on a high-demand tool can be
a useful bartering tool in many lab economies. You and your reservation policies need to help your users NOT get caught up in reservation gaming …<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">What is your reservation deletion/cancellation policy … or are people simply failing to cancel reservations? Along these lines, a frequent suggestion is to "charge them for unused reservations". While that is easy to say, I have yet to
see a reliable, automated means of determining that a reservation was not used. What is the evaporator was down? What if an upstream tool was down? What if, …<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Your lab users are smart: have they found a way to actually use the tool for longer than their usage records indicate? That becomes a question of what is actually interlocked on the tool, but if you interlock cooling water or things that
affect only the actual evaporation, for example, your users likely know that and may not be paying for all of their actual equipment time. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Of course, in a university research lab, a tool that is actually used more than 50% of the time should probable place that tool quite high on our "we'd like another X" list. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I certainly expect to see a lively discussion of this topic …<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Have a good weekend,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">John<o:p></o:p></p>
<div>
<p class="MsoNormal">Sent from my iPhone<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Jul 14, 2017, at 4:53 PM, Vito Logiudice <<a href="mailto:vito.logiudice@uwaterloo.ca">vito.logiudice@uwaterloo.ca</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class="MsoNormal">Dear Colleagues,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We have struggled for some time now with equipment reservations which tend to be much greater than equipment use times. This is especially problematic on some of our most popular tools. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">For instance, records for the past 7 day period show an enable (or use) time for our popular e-beam evaporator of 86 hours while the tool was reserved for a total of 192 hours during this period. This translates into a tool reservation
efficiency of 45%; this seems very poor to me. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I can appreciate that it can be difficult to estimate how much time one might need on any given tool. However, I’m inclined to think that a robust and well-maintained tool with well understood and documented processes (as is the case for
this particular deposition system) should allow our membership to plan their work accurately enough so that the tool’s reservation efficiency should remain consistently above 75% or so. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If this is a parameter that you happen track for your operations, I would appreciate hearing what your typical reservation efficiency range might be for some of your most popular tools. I would also appreciate hearing your thoughts on what
you might have done in the past to improve this performance parameter for these particularly popular tools.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you for any insights. All feedback is welcome.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Vito<o:p></o:p></p>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE">
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">--</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Vito Logiudice MASc, P.Eng.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Director, Quantum NanoFab</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">University of Waterloo</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Lazaridis QNC 1207</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">200 University Avenue West</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Waterloo, ON Canada N2L 3G1</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Tel.: (519) 888-4567 ext. 38703</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt">Email: <a href="mailto:vito.logiudice@uwaterloo.ca">vito.logiudice@uwaterloo.ca</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Website: </span><a href="https://fab.qnc.uwaterloo.ca">https://fab.qnc.uwaterloo.ca</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<br>
labnetwork mailing list<br>
<a href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a><br>
<a href="https://www-mtl.mit.edu/mailman/listinfo.cgi/labnetwork">https://www-mtl.mit.edu/mailman/listinfo.cgi/labnetwork</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</body>
</html>