<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;" class="">Hi Vito,<div class=""><br class=""></div><div class="">We began investigating this issue in 10/2016. We use a commercial scheduling system, Booked Scheduler, that generates a report for created and deleted reservations. After analyzing the cancellation rates for each tool and each user, it was quite clear that it was a user behavior problem. In December, we made an announcement describing average cancellation rates, specified that we are aware of 9 abusers, and we're considering fines for canceled time. In March, we made a similar announcement specifying 3 remaining abusers. The data at this time showed a downward trend in cancellation rates for all the abusers except one. In May, I contacted the one remaining abuser with a plot of his cancellation rate. Today, a past abuser is returning to old habits.</div><div class=""><br class=""></div><div class="">90% of our students have cancellation rates below 20%. We are addressing abusers individually to avoid any changes to our reservation policy. The google spreadsheet we made to automate the analysis makes identifying abusers effortless. Then checking their cancellation trends helps us decide what we want to do. This is a very slow experiment, but it feels promising. Perhaps by disciplining the few abusers, we can avoid the overhead/waste associated with charging for cancelled time or fines.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Long<br class=""><div><blockquote type="cite" class=""><div class="">On Jul 17, 2017, at 9:36 AM, Brent Gila <<a href="mailto:bgila@ufl.edu" class="">bgila@ufl.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
Hello Vito,<br class="">
<br class="">
Our tracking system was developed in-house and it stores the
reservations and actual use in a database. From this we run reports
and can compare all aspects of the tool reservation (even when it
was made or canceled) and the actual tool use. We then look for
large discrepancies between the two and address these as needed. I
am not familiar with other systems (either turn-key or home made)
but our has worked very well for us. <br class="">
<br class="">
We find that with some open discussion with the user groups we can
reel in the ones that make a 10hr reservation for 1hr of use. There
needs to be wiggle room for process issues and it is very hard to
predict exact times, we have a 15 minute window that is allowable on
both ends of the reservation to help out with this and take uncommon
circumstances into consideration when needed. The more open we are
on these kinds of issues and the more we communicate effectively
with the user groups, the less of an issue this has become.<br class="">
<br class="">
Best Regards,<br class="">
Brent<br class="">
<div class="moz-signature"><br class="">
-- <br class="">
Brent P. Gila, PhD.<br class="">
Director, Nanoscale Research Facility<br class="">
1041 Center Drive<br class="">
University of Florida<br class="">
Gainesville, Florida 32611<br class="">
<a class="moz-txt-link-freetext" href="tel:352-273-2245">Tel:352-273-2245</a><br class="">
Fax:352-846-2877<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:email:bgila@ufl.edu">email:bgila@ufl.edu</a><br class="">
</div>
<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">On 7/14/2017 4:23 PM, Vito Logiudice
wrote:<br class="">
</div>
<blockquote cite="mid:DA5E141F-7B21-42A2-A06C-A32053B6C7E8@connect.uwaterloo.ca" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
<div class="">
<div class="">
<div class="">Dear Colleagues,</div>
<div class=""><br class="">
</div>
<div class="">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 class=""><br class="">
</div>
<div class="">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 class=""><br class="">
</div>
<div class="">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 class=""><br class="">
</div>
<div class="">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 class=""><br class="">
</div>
<div class="">Thank you for any insights. All feedback is welcome.</div>
<div class=""><br class="">
</div>
<div class="">Best regards,</div>
<div class="">Vito</div>
<div class="">
<div id="MAC_OUTLOOK_SIGNATURE" class="">
<div class=""><font class="Apple-style-span"><font class="Apple-style-span" style="font-size: 14px; " face="Calibri"><font face="Calibri,sans-serif" class="">--</font></font></font></div>
<div class=""><font class="Apple-style-span"><font class="Apple-style-span" style="font-size: 14px; " face="Calibri"><font face="Calibri,sans-serif" class="">Vito
Logiudice MASc, </font>P.<font face="Calibri,sans-serif" class="">Eng.</font></font></font></div>
<div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri"><font style="font-size: 14px; " face="Calibri,sans-serif" class="">Director, Quantum
NanoFab</font></font></font></div>
<div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri"><font style="font-size: 14px; " face="Calibri,sans-serif" class="">University of Waterloo</font></font></font></div>
<div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri"><font style="font-size: 14px; " face="Calibri,sans-serif" class="">Lazaridis QNC 1207</font></font></font></div>
<div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri"><font style="font-size: 14px; " face="Calibri,sans-serif" class="">200 University Avenue
West</font></font></font></div>
<div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri"><font style="font-size: 14px; " face="Calibri,sans-serif" class="">Waterloo, ON
Canada N2L 3G1</font></font></font></div>
<div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri"><font style="font-size: 14px; " face="Calibri,sans-serif" class="">Tel.: (519) 888-4567
ext. 38703</font></font></font></div>
<div class=""><span style="font-size: 14px; " class="">Email: <a moz-do-not-send="true" href="mailto:vito.logiudice@uwaterloo.ca" class="">vito.logiudice@uwaterloo.ca</a></span></div>
<div class=""><span style="font-size: 14px; " class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri"><font face="Calibri,sans-serif" class="">Website: </font></font></font></span><a moz-do-not-send="true" href="https://fab.qnc.uwaterloo.ca/" class="">https://fab.qnc.uwaterloo.ca</a></div>
<div class=""><br class="">
</div>
</div>
</div>
</div>
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
labnetwork mailing list
<a class="moz-txt-link-abbreviated" href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a>
<a class="moz-txt-link-freetext" href="https://www-mtl.mit.edu/mailman/listinfo.cgi/labnetwork">https://www-mtl.mit.edu/mailman/listinfo.cgi/labnetwork</a>
</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">labnetwork mailing list<br class=""><a href="mailto:labnetwork@mtl.mit.edu" class="">labnetwork@mtl.mit.edu</a><br class="">https://www-mtl.mit.edu/mailman/listinfo.cgi/labnetwork<br class=""></div></blockquote></div><br class=""></div></body></html>