[labnetwork] Logging and Access Control of Legacy Equipment

[Ryan Taylor]

Hi John,

We are using OpenCoral to meet those requirements at our lab.  The 
enforcement mechanism is accomplished one of two ways.  We are using 
network-capable interlock boxes to that are physically wired into some 
tools.  For others, we are using a home-grown "software interlock" that 
runs on windows and locks the screen and keyboard until someone 
authenticates successfully.  We've been able to use that system to lock 
windows 98, XP and windows 7.  There's a bit more information about the 
hardware interlocks on our web page 
(http://coral.nanofab.utah.edu/lab/docs/get_doc/interlocks). Though, we 
built our own interlock box solution, I believe the latest version of 
OpenCoral has built-in support for a similar system.

I would be happy to share the software for the software interlocks too, 
if you are interested.  I could also share some of the techniques we've 
used for dealing with our logs for billing (we also charge for time in 
our lab, but we are moving toward a billing system based solely on tool 
usage).

Thanks,
Ryan Taylor



-- 
---------
Ryan Taylor
Software Systems Development Engineer
University of Utah Nanofab
www.nanofab.utah.edu
Phone: (801) 587-0671
Email: ryant at nanofab.utah.edu



On 2/25/13 12:41 PM, Hughes, John S wrote:
>
> Hi Everyone,
>
> We have a lot of process tools that are old enough not to have any 
> computer control, or the computer control available does not provide 
> login records and/or access control. We've been looking at what it 
> would take to provide this functionality in an all-inclusive way for 
> about twenty years, but for various reasons it has not yet been done.
>
> I'm aware of a number of ways to accomplish what we want, but with all 
> the new technology now available, I thought I'd first ask the 
> Labnetwork community for some recommendations. Needless to say, we 
> don't have unlimited funding or manpower to implement the project.
>
> Our minimum requirements are:
>
> . Each tool user would be required to provide a unique login and 
> password in order to operate the process tool. (The tool would be 
> inoperable unless an approved user logged in.)
>
> . Information about the user's identity, and the log-in and log-out 
> times would be permanently recorded, and the information would be 
> easily exported into a spreadsheet or database.
>
> . Additional entry fields (or perhaps check-box selections) providing 
> information pertinent to the process being performed on the tool could 
> also be required (and stored).
>
> We have long used a fairly elaborate door access control system 
> (Pro-Watch 3.80, w/ RFID card readers) that has been well integrated 
> into our in-house accounting program. We would eventually like to the 
> have the Pro-Watch and accounting programs make use of the tool usage 
> data, and perhaps vice-versa. (Pro-Watch has some hardware control 
> capabilities.)
>
> Any suggestions would be much appreciated.
>
> Thanks,
> John
>
> -------------------------------------------------------------
> John S. Hughes                         Office: (217) 333-4674
> Associate Director                        FAX: (217) 244-6375
> Laboratory Operations hughes at illinois.edu <mailto:hughes at illinois.edu>
> Micro and Nanotechnology Laboratory
> University of Illinois at Urbana-Champaign
> 2000E Micro and Nanotechnology Laboratory
> 208 North Wright Street
> Urbana, Illinois  61801 http://mntl.illinois.edu
> -------------------------------------------------------------
>
>
>
> _______________________________________________
> labnetwork mailing list
> labnetwork at mtl.mit.edu
> https://www-mtl.mit.edu/mailman/listinfo.cgi/labnetwork

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mtl.mit.edu/pipermail/labnetwork/attachments/20130225/9faa719f/attachment.html>