<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 15px; font-family: Calibri, sans-serif;">
<div>
<div>Hi John,</div>
<div><br>
</div>
<div>Thanks very much for piping in.</div>
<div><br>
</div>
<div>You’re of course correct about my error. We’re running Badger and the equipment reservation efficiency report in question was for the period 2017-07-04 to 2017-07-13 which translates to a 10 day period rather than the 7 days I mentioned in my email. Sorry
about that.</div>
<div><br>
</div>
<div>Since we’re running Badger you already know that we do have the ability to make tool-specific reservation rules. Right now, this particular tool has a 14-day reservation horizon, a 3hr maximum single reservation duration and a 12hr total reservation maximum
for the 14-day horizon. We’ve thought about tweaking these but I was curious to hear what others in the community might be doing before heading in that direction.</div>
<div><br>
</div>
<div>Along the same lines, the good folks at Badger have recently created a new “fair play protocol” for us that reduces the total 14-day reservation horizon for a tool on a per-user basis based on their behaviour. Specifically, anyone who does not cancel an
unneeded reservation within the 24 hour grace period will see their 14-day reservation horizon maximum reduced by the duration of the cancelled reservation(s). We recently rolled out this new protocol on another single tool but have not yet accumulated enough
data to extract anything meaningful as of yet. Maybe this will be the way to go with the evaporator as well if we see an improvement on this other tool (e-beam litho system). Time will tell.</div>
<div><br>
</div>
<div>Thanks again for sharing your insights. Always appreciated.</div>
<div><br>
</div>
<div>Best,</div>
<div>Vito</div>
<div>
<div id="">
<div><br>
</div>
</div>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>John D Shott <<a href="mailto:shott@stanford.edu">shott@stanford.edu</a>><br>
<span style="font-weight:bold">Date: </span>Friday, July 14, 2017 at 9:07 PM<br>
<span style="font-weight:bold">To: </span>Vito Logiudice <<a href="mailto:vito.logiudice@uwaterloo.ca">vito.logiudice@uwaterloo.ca</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a>" <<a href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [labnetwork] Equipment reservation efficiencies<br>
</div>
<div><br>
</div>
<div>
<div dir="auto">
<div>Vito:</div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>For starters, since 7x24 = 168 hours, if your evaporator was reserved for 192 hours in a week you have a different problem …</div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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 …</div>
<div><br>
</div>
<div>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, …</div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>I certainly expect to see a lively discussion of this topic …</div>
<div><br>
</div>
<div>Have a good weekend,</div>
<div><br>
</div>
<div>John<br>
<br>
<div>Sent from my iPhone</div>
</div>
<div><br>
On Jul 14, 2017, at 4:53 PM, Vito Logiudice <<a href="mailto:vito.logiudice@uwaterloo.ca">vito.logiudice@uwaterloo.ca</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div>
<div>
<div>Dear Colleagues,</div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Thank you for any insights. All feedback is welcome.</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Vito</div>
<div>
<div id="">
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri" style="font-size: 14px; "><font face="Calibri,sans-serif">--</font></font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri" style="font-size: 14px; "><font face="Calibri,sans-serif">Vito Logiudice MASc, </font>P.<font face="Calibri,sans-serif">Eng.</font></font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><font face="Calibri,sans-serif" style="font-size: 14px; ">Director, Quantum NanoFab</font></font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><font face="Calibri,sans-serif" style="font-size: 14px; ">University of Waterloo</font></font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><font face="Calibri,sans-serif" style="font-size: 14px; ">Lazaridis QNC 1207</font></font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><font face="Calibri,sans-serif" style="font-size: 14px; ">200 University Avenue West</font></font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><font face="Calibri,sans-serif" style="font-size: 14px; ">Waterloo, ON Canada N2L 3G1</font></font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><font face="Calibri,sans-serif" style="font-size: 14px; ">Tel.: (519) 888-4567 ext. 38703</font></font></font></div>
<div><span style="font-size: 14px; ">Email: <a href="mailto:vito.logiudice@uwaterloo.ca">vito.logiudice@uwaterloo.ca</a></span></div>
<div><span style="font-size: 14px; "><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><font face="Calibri,sans-serif">Website: </font></font></font></span><a href="https://fab.qnc.uwaterloo.ca">https://fab.qnc.uwaterloo.ca</a></div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>labnetwork mailing list</span><br>
<span><a href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a></span><br>
<span><a href="https://www-mtl.mit.edu/mailman/listinfo.cgi/labnetwork">https://www-mtl.mit.edu/mailman/listinfo.cgi/labnetwork</a></span><br>
</div>
</blockquote>
</div>
</div>
</span>
</body>
</html>