[labnetwork] RFID interlocks

[Michael Khbeis]

Tom, 

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. 

Mike,

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.

Maybe a little draconian and simple, but effective. 

Best,  

Dr. Michael Khbeis
Director, Washington Nanofabrication Facility (WNF) 
National Nanotechnology Coordinated Infrastructure (NNCI)
University of Washington
Fluke Hall, Box 352143
(O) 206.543.5101
(F) 206.221.1681
(C) 443.254.5192
khbeis at uw.edu
www.wnf.washington.edu/

> On Mar 7, 2018, at 9:51 AM, Michael Young <myoung6 at nd.edu> wrote:
> 
> 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.
> 
> 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.
> 
> The other big drawback: I expect to see the same sort of behavior that we get now with Coral + hardware interlocks: folks enable and then forget to disable. (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?!?"). 
> 
> Anyone have any good ideas regarding this issue?
> 
> --Mike (who really didn't intend to hijack Tom's thread...)
> 
> 
> 
> On 3/7/18 8:29 AM, Ferraguto, Thomas S wrote:
>> Colleagues,
>>  
>> To resolve the issue of untracked use of equipment at our Nanofab, I’ve been working with a Easyclocking in Florida with mixed results.
>>  
>> 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.
>>  
>> Is anyone else using an RFID system to track equipment usage?
>>  
>> 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).
>>  
>> Please let me know?
>>  
>> Best Regards
>>  
>>  
>> Thomas S. Ferraguto
>> Saab ETIC Nanofabrication Laboratory Director
>> Saab ETIC Building Director
>> 1 University Avenue
>> Lowell MA 01854
>> Mobile 617-755-0910
>> Land 978-934-1809
>> Fax 978-934-1014 
>> 
> 
> -- 
> 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                         mike.young at nd.edu <mailto:mike.young at nd.edu>
> B-38 Stinson-Remick Hall
> Notre Dame, IN 46556-5637
> _______________________________________________
> labnetwork mailing list
> labnetwork at mtl.mit.edu <mailto:labnetwork at mtl.mit.edu>
> https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork <https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mtl.mit.edu/pipermail/labnetwork/attachments/20180307/6c7c3003/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1350 bytes
Desc: not available
URL: <https://mtl.mit.edu/pipermail/labnetwork/attachments/20180307/6c7c3003/attachment.bin>