<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi John,<br>
<br>
I've been using trac to document the projects that we've
undertaken for extending OpenCoral. Luckily, most of the hard
work has already been done in the Coral software and we've mostly
added adapters or small web service layers to extend the
functionality. You can check out the documentation that I've put
together at:<br>
<br>
<a class="moz-txt-link-freetext" href="http://nanoproject.eng.utah.edu/ClearLockInterlock/wiki">http://nanoproject.eng.utah.edu/ClearLockInterlock/wiki</a> for the
software interlocking<br>
<br>
and<br>
<br>
<a class="moz-txt-link-freetext" href="http://nanoproject.eng.utah.edu/HardwareServerProxy">http://nanoproject.eng.utah.edu/HardwareServerProxy</a> for the
hardware interlocking<br>
<br>
Being so close to the software, I'm not sure if the documentation
I've created always has enough detail to be clear to an outside
party so let me know if you find it lacking in any way and I will
fill it in. <br>
<br>
I think that coral wouldn't necessarily need to replace your
current system if you just wanted to use it for equipment
interlocking, but there would be some work involved in sync'ing
users, roles, equipment, etc.<br>
<br>
In my experience, the biggest pain point for using OpenCoral is
the initial installation and configuration. Once you get it
configured and running, it is relatively low maintenance. From
what I understand, the Badger project has put a lot of work into
making that part of the process as simple as possible. <br>
<br>
Please let me know if there's anything else I can help with.<br>
<br>
Thanks,<br>
Ryan<br>
<br>
On 2/26/13 9:11 AM, Hughes, John S wrote:<br>
</div>
<blockquote
cite="mid:BAEB67F7D00AEE4F8513105A149258C0381C797E@CITESMBX2.ad.uillinois.edu"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div><br>
</div>
Hi Ryan,
<div><br>
</div>
<div>Thanks for your input.</div>
<div><br>
</div>
<div>OpenCoral appears to accomplish for you the things we'd also
like to do. I've been aware of Coral as a possible solution for
a long time, but as I mentioned, we've developed over many years
a very elaborate (door) access/accounting/billing program using
ProWatch. We will look more closely at switching to OpenCoral or
Badger, but I'm hoping I can add the elements for tool access
and data logging to our existing system rather than starting
completely over. (Our business office might rebel.)</div>
<div><br>
</div>
<div>I really like the way your interlock boxes work (and look).
More details about how those were configured would be
appreciated, and the software interlocks as well. Unfortunately
for us, assistance from our (now college-wide) IT group to work
on a project like this may be difficult to come by, due to a
recent reorganization and staff/budget cuts. I expect we'll need
to set this up as a lab-funded project, contracting the
programming work, perhaps coordinating with the CS department to
find some student help. (Always a bit risky.) Any guesses on how
much time you've invested so far on the programming side of
things?</div>
<div><br>
</div>
<div>Like you, we are also wanting to move away from
time-in-the-cleanroom charges to tool-use charges, and the
success of this project is critical for that transition to take
place.</div>
<div><br>
</div>
<div>Thanks again,</div>
<div>John</div>
<div><br>
</div>
<div>
<div apple-content-edited="true">
<div><font class="Apple-style-span" style="font-family:
Courier; " size="3"><span class="Apple-style-span"
style="font-size: 12px; ">-------------------------------------------------------------<br>
John S. Hughes Office: (217)
333-4674<br>
Associate Director FAX: (217)
244-6375<br>
Laboratory Operations <a
moz-do-not-send="true"
href="mailto:hughes@illinois.edu">hughes@illinois.edu</a><br>
Micro and Nanotechnology Laboratory</span></font>
<div style="font-family: Courier; "><font
class="Apple-style-span" size="3"><span
class="Apple-style-span" style="font-size: 12px; ">University
of Illinois at Urbana-Champaign</span></font></div>
<div style="font-family: Courier; "><font
class="Apple-style-span" size="3"><span
class="Apple-style-span" style="font-size: 12px; ">2000E
Micro and Nanotechnology Laboratory<br>
208 North Wright Street<br>
Urbana, Illinois 61801 <a
moz-do-not-send="true"
href="http://mntl.illinois.edu">http://mntl.illinois.edu</a></span></font></div>
<div style="font-family: Courier; "><font
class="Apple-style-span" size="3"><span
class="Apple-style-span" style="font-size: 12px; ">-------------------------------------------------------------</span></font></div>
</div>
</div>
<br>
<div>
<div>On Feb 25, 2013, at 6:10 PM, Ryan Taylor <<a
moz-do-not-send="true"
href="mailto:ryant@nanofab.utah.edu">ryant@nanofab.utah.edu</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi John,<br>
<br>
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 (<a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://coral.nanofab.utah.edu/lab/docs/get_doc/interlocks">http://coral.nanofab.utah.edu/lab/docs/get_doc/interlocks</a>).
Though, we built our own interlock box solution, I
believe the latest version of OpenCoral has built-in
support for a similar system.<br>
<br>
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).<br>
<br>
Thanks,<br>
Ryan Taylor<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
---------
Ryan Taylor
Software Systems Development Engineer
University of Utah Nanofab
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.nanofab.utah.edu/">www.nanofab.utah.edu</a>
Phone: (801) 587-0671
Email: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:ryant@nanofab.utah.edu">ryant@nanofab.utah.edu</a>
</pre>
<br>
<br>
On 2/25/13 12:41 PM, Hughes, John S wrote:<br>
</div>
<blockquote
cite="mid:BAEB67F7D00AEE4F8513105A149258C0381C04A5@CITESMBX2.ad.uillinois.edu"
type="cite">
<div><br>
</div>
<div>Hi Everyone,</div>
<div><br>
</div>
<div>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.</div>
<div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Our minimum requirements are: </div>
<div><br>
</div>
<div>• 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.) </div>
<div><br>
</div>
<div>• 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. </div>
<div><br>
</div>
<div>• 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).</div>
<div><br>
</div>
<div>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.) </div>
<div><br>
</div>
<div>Any suggestions would be much appreciated. </div>
<div><br>
</div>
<div>Thanks,</div>
<div>John</div>
</div>
<div><br>
</div>
<!--EndFragment-->
<div apple-content-edited="true">
<div><font class="Apple-style-span"
style="font-family: Courier; " size="3"><span
class="Apple-style-span" style="font-size: 12px;
">-------------------------------------------------------------<br>
John S. Hughes Office:
(217) 333-4674<br>
Associate Director FAX:
(217) 244-6375<br>
Laboratory Operations <a
moz-do-not-send="true"
href="mailto:hughes@illinois.edu">hughes@illinois.edu</a><br>
Micro and Nanotechnology Laboratory</span></font>
<div style="font-family: Courier; "><font
class="Apple-style-span" size="3"><span
class="Apple-style-span" style="font-size:
12px; ">University of Illinois at
Urbana-Champaign</span></font></div>
<div style="font-family: Courier; "><font
class="Apple-style-span" size="3"><span
class="Apple-style-span" style="font-size:
12px; ">2000E Micro and
Nanotechnology Laboratory<br>
208 North Wright Street<br>
Urbana, Illinois 61801 <a
moz-do-not-send="true"
href="http://mntl.illinois.edu/">http://mntl.illinois.edu</a></span></font></div>
<div style="font-family: Courier; "><font
class="Apple-style-span" size="3"><span
class="Apple-style-span" style="font-size:
12px; ">-------------------------------------------------------------</span></font></div>
</div>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
labnetwork mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a>
<a moz-do-not-send="true" 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>
</div>
_______________________________________________<br>
labnetwork mailing list<br>
<a moz-do-not-send="true"
href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a><br>
<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><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
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>
<br>
<pre class="moz-signature" cols="72">--
---------
Ryan Taylor
Software Systems Development Engineer
University of Utah Nanofab
<a class="moz-txt-link-abbreviated" href="http://www.nanofab.utah.edu">www.nanofab.utah.edu</a>
Phone: (801) 587-0671
Email: <a class="moz-txt-link-abbreviated" href="mailto:ryant@nanofab.utah.edu">ryant@nanofab.utah.edu</a>
</pre>
</body>
</html>