<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="">Tom, <div class=""><br class=""></div><div class="">We are using a highly customized version of Web-CORAL. RFID is a challenge because of numerous accounts and simultaneous tool enable scenarios. We use CORAL screen locks whenever feasible and for non-PC controlled systems, the high voltage/pneumatic interlocks. It works quite well for us. </div><div class=""><br class=""></div><div class="">Mike,</div><div class=""><br class=""></div><div class="">Our biggest deterrent to the forgot to disable problem - fees for forgetting. We will make non-fee adjustments for things like equipment failure and planned overnight runs where we only charge valid use of course. However, we have an annual progressive fee schedule for adjusting “forgot to disable" times where (N-1)*$25 for each reoccurring incident, where N is the count of change requests. So the first offense is free and then the charges grow quickly. As you can imagine, this is a strong deterrent and we have had very few “forgetfulness” adjustment requests since implementing this policy. Of course we hate charging erroneous fees, but I hated wasting significant staff time each week fixing the billing issues.</div><div class=""><br class=""></div><div class="">Maybe a little draconian and simple, but effective. </div><div class=""><br class=""></div><div class="">Best, </div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Dr. Michael Khbeis<br class="">Director, Washington Nanofabrication Facility (WNF) <br class="">National Nanotechnology Coordinated Infrastructure (NNCI)<br class="">University of Washington<br class="">Fluke Hall, Box 352143<br class="">(O) 206.543.5101<br class="">(F) 206.221.1681<br class="">(C) 443.254.5192<br class=""><a href="mailto:khbeis@uw.edu" class="">khbeis@uw.edu</a><br class="">www.wnf.washington.edu/</div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Mar 7, 2018, at 9:51 AM, Michael Young <<a href="mailto:myoung6@nd.edu" class="">myoung6@nd.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class="">Hi Tom. At NDNF, we are approaching this model, slowly. Our campus recently switched to RFID+magstripe smart cards to replace magstripe-only student/staff/faculty ID cards. I was able to locate a generic (Pacific Rim origin) RFID reader for about $10; it's USB and it reliably reads the card ID from these new smart cards. My goal is to add these readers to key equipment, as well as to our Coral computers, in the cleanroom. For equipment, the reader can be connected to, say, a networked Raspberry Pi, one per tool, which can inform the Coral server that someone needs that tool to be enabled. The coral server can then take care of the bookkeeping, and also tell the hardware interlock to enable.</p><p style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class="">The good thing: this approach builds on our current infrastructure, at a manageable one-time cost. The bad thing: it's not quite what you are looking for, as it's not a comprehensive 3rd-party turnkey solution.<br class=""></p><p style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class="">The other big drawback: I expect to see the same sort of behavior that we get now with Coral + hardware interlocks: folks<span class="Apple-converted-space"> </span><b class="">enable</b><span class="Apple-converted-space"> </span>and then<span class="Apple-converted-space"> </span><b class="">forget to disable</b>. (I'm not even sure a big bright flashing "ENABLED!!!" display on the tool would help.) This of course messes up the monthly cost recovery ("I used it for HOW MANY HOURS?????"), and also allows (or "fails to prevent") other users sneaking in and using the tool while it's enabled. I've thought about implementing auto-timeouts (disable on timeout), but this quickly becomes very tool-specific and can potentially cause process disruption ("Hey, how come the spinner just stopped?!?").<span class="Apple-converted-space"> </span><br class=""></p><p style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class="">Anyone have any good ideas regarding this issue?</p><p style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class="">--Mike (who really didn't intend to hijack Tom's thread...)<br class=""></p><p style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class=""><br class=""></p><div class="moz-cite-prefix" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);">On 3/7/18 8:29 AM, Ferraguto, Thomas S wrote:<br class=""></div><blockquote type="cite" cite="mid:a2f7a4cadb2f44f18d321ba3deac34e5@uml.edu" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class=""><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Colleagues,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">To resolve the issue of untracked use of equipment at our Nanofab, I’ve been working with a Easyclocking in Florida with mixed results.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">The goal was to have RFID badges to open and close interlocks on our equipment and provide a data table with which we could reconcile accounts.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Is anyone else using an RFID system to track equipment usage?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I am trying to use existing services and hardware to get to a better tracking system (I don’t have the resources to develop a system internally).<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Please let me know?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Best Regards<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Thomas S. Ferraguto<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Saab ETIC Nanofabrication Laboratory Director<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Saab ETIC Building Director<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">1 University Avenue<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Lowell MA 01854<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Mobile 617-755-0910<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Land 978-934-1809<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Fax 978-934-1014<span class="Apple-converted-space"> </span><o:p class=""></o:p></div><br class=""></div></blockquote><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class=""><pre class="moz-signature" cols="72" style="font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);">--
Michael P. Young (574) 631-3268 (office)
Nanofabrication Specialist (574) 631-4393 (fax)
Department of Electrical Engineering (765) 637-3784 (cell)
University of Notre Dame <a class="moz-txt-link-abbreviated" href="mailto:mike.young@nd.edu" style="color: rgb(149, 79, 114); text-decoration: underline;">mike.young@nd.edu</a>
B-38 Stinson-Remick Hall
Notre Dame, IN 46556-5637</pre><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); float: none; display: inline !important;" class="">_______________________________________________</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); float: none; display: inline !important;" class="">labnetwork mailing list</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class=""><a href="mailto:labnetwork@mtl.mit.edu" style="color: rgb(149, 79, 114); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class="">labnetwork@mtl.mit.edu</a><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class=""><a href="https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork" style="color: rgb(149, 79, 114); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class="">https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork</a><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class=""></div></blockquote></div><br class=""></div></body></html>