<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:#000066;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:#000066;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:#000066;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If there is an interest, I have a great forum for us to use as an every-year meeting on facility operations. I have just gone onto the Executive Board of IEST, and we have been having some really good discussions about where we want to go with fabrication facilities. Right now we have been concentrating on design issues, but we could very easily add operational issues to the agenda. The IEST meets every year in May, generally the first week. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If it looks like this is something that has significant interest, we can look at ESTECH 2013 to kick off an operations symposium. Long term, we may want to consider combining UGIM with ESTECH in years when UGIM would normally meet, and use ESTECH as a free-standing conference in alternate years.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>For those who are not familiar with IEST, that is the organization that has been the technical arm of cleanroom design and operation since the 1960s. It is the secretariat for many of the ISO standards in both cleanrooms and now nanotechnology. The standard for cleanroom classification – now ISO, formerly Federal Standard 209 – was written by the IEST. It would be a great forum for our group, now that we have moved away from devices and toward facilities, especially facility operation.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>What are the thoughts of the group?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>John<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><b><i><span style='font-size:10.0pt;color:#1F497D'>John R. Weaver<o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:10.0pt;color:#1F497D'>Facility Manager<o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:10.0pt;color:#1F497D'>Birck Nanotechnology Center<o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:10.0pt;color:#1F497D'>Purdue University<o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:10.0pt;color:#1F497D'>(765) 494-5494<o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:10.0pt;color:#1F497D'>jrweaver@purdue.edu<o:p></o:p></span></i></b></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> labnetwork-bounces@mtl.mit.edu [mailto:labnetwork-bounces@mtl.mit.edu] <b>On Behalf Of </b>Abbie Gregg<br><b>Sent:</b> Tuesday, June 07, 2011 1:48 AM<br><b>To:</b> David A. Bunzow; labnetwork@mtl.mit.edu<br><b>Subject:</b> Re: [labnetwork] More on buddy system and a labnetwork suggestion / Fwd: 24/7 operations<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Arial","sans-serif";color:#1F497D'>Agreed, maybe we can develop a way to get it funded by another entity in the alternate years….<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Abbie Gregg</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>President</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Abbie Gregg, Inc.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>1130 East University Drive, Suite 105</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Tempe, Arizona 85281</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Phone 480 446-8000 x 107</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Cell 480-577-5083</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>FAX 480-446-8001</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>email <a href="mailto:agregg@abbiegregg.com" title="mailto:agregg@abbiegregg.com">agregg@abbiegregg.com</a></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>website <a href="http://www.abbiegregg.com" title="http://www.abbiegregg.com/">www.abbiegregg.com</a></span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:red'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><i><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:navy'>CONFIDENTIALITY NOTICE: All information contained in or attached to this email constitutes confidential information belonging to Abbie Gregg, Inc., its affiliates and subsidiaries and/or its clients. This email and any attachments are proprietary and/or confidential and are intended for business use of the addressee(s) only. All other uses or disclosures are strictly prohibited. If the reader is not the intended recipient you are hereby notified that the perusal, copying or dissemination of this email is strictly prohibited. If you have received this communication in error, please notify the sender, and delete all copies of this message and its attachments immediately</span></i><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:navy'>. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Arial","sans-serif";color:blue'><o:p> </o:p></span></p></div><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> labnetwork-bounces@mtl.mit.edu [mailto:labnetwork-bounces@mtl.mit.edu] <b>On Behalf Of </b>David A. Bunzow<br><b>Sent:</b> Monday, June 06, 2011 1:08 PM<br><b>To:</b> labnetwork@mtl.mit.edu<br><b>Subject:</b> Re: [labnetwork] More on buddy system and a labnetwork suggestion / Fwd: 24/7 operations<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'>Dear Abbie and Ian,<br>I myself have wondered myself why UGIM is only held every two years. Seems to me that a whole lot more goes on that we could cover better annually rather then bi-annually...<br>Just my $0.05 worth....<o:p></o:p></p><pre style='margin-left:.5in'>David A. Bunzow<o:p></o:p></pre><pre style='margin-left:.5in'>User Facilities Program Manager<o:p></o:p></pre><pre style='margin-left:.5in'>The Molecular Foundry<o:p></o:p></pre><pre style='margin-left:.5in'>Materials Science Division<o:p></o:p></pre><pre style='margin-left:.5in'>Lawrence Berkeley National Laboratory<o:p></o:p></pre><pre style='margin-left:.5in'>1 Cyclotron Road MS 67-3207<o:p></o:p></pre><pre style='margin-left:.5in'>Berkeley, CA 94720<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Office: 510-486-4574<o:p></o:p></pre><pre style='margin-left:.5in'>FAX: 510-486-7424<o:p></o:p></pre><pre style='margin-left:.5in'>Cell: 701-541-2354<o:p></o:p></pre><p class=MsoNormal style='margin-left:.5in'><br>On 6/1/2011 12:20 AM, Abbie Gregg wrote: <o:p></o:p></p><pre style='margin-left:.5in'>Dear Ian,<o:p></o:p></pre><pre style='margin-left:.5in'>Great answers here about good ideas for safe 24 x 7 operations, and I am very interested in the Coral system interlock boxes and also to have more interactions in the "off years" between UGIM conferences.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Abbie Gregg<o:p></o:p></pre><pre style='margin-left:.5in'>President<o:p></o:p></pre><pre style='margin-left:.5in'>Abbie Gregg, Inc.<o:p></o:p></pre><pre style='margin-left:.5in'>1130 East University Drive, Suite 105<o:p></o:p></pre><pre style='margin-left:.5in'>Tempe, Arizona 85281<o:p></o:p></pre><pre style='margin-left:.5in'>Phone 480 446-8000 x 107<o:p></o:p></pre><pre style='margin-left:.5in'>Cell 480-577-5083<o:p></o:p></pre><pre style='margin-left:.5in'>FAX 480-446-8001<o:p></o:p></pre><pre style='margin-left:.5in'>email <a href="mailto:agregg@abbiegregg.com">agregg@abbiegregg.com</a><o:p></o:p></pre><pre style='margin-left:.5in'>website <a href="http://www.abbiegregg.com">www.abbiegregg.com</a><o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>CONFIDENTIALITY NOTICE: All information contained in or attached to this email constitutes confidential information belonging to Abbie Gregg, Inc., its affiliates and subsidiaries and/or its clients. This email and any attachments are proprietary and/or confidential and are intended for business use of the addressee(s) only. All other uses or disclosures are strictly prohibited. If the reader is not the intended recipient you are hereby notified that the perusal, copying or dissemination of this email is strictly prohibited. If you have received this communication in error, please notify the sender, and delete all copies of this message and its attachments immediately. <o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>-----Original Message-----<o:p></o:p></pre><pre style='margin-left:.5in'>From: <a href="mailto:labnetwork-bounces@mtl.mit.edu">labnetwork-bounces@mtl.mit.edu</a> [<a href="mailto:labnetwork-bounces@mtl.mit.edu">mailto:labnetwork-bounces@mtl.mit.edu</a>] On Behalf Of Ian Harvey<o:p></o:p></pre><pre style='margin-left:.5in'>Sent: Tuesday, May 31, 2011 10:38 AM<o:p></o:p></pre><pre style='margin-left:.5in'>To: <a href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a><o:p></o:p></pre><pre style='margin-left:.5in'>Subject: [labnetwork] More on buddy system and a labnetwork suggestion / Fwd: 24/7 operations<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Dear lab network,<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Great forum. Thanks to all for important feedback which I have compiled in the thread below.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Here at the Utah nanofab, we run 24/7 with training aimed at proper off-shift use of tools, and we work to create an enforceable buddy system, and build systems that make it easier for labmembers to adhere to the off-shift buddy system. Our intent is: not having a safety buddy is not an option.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Among the tools we use to make it easier to adhere to the buddy system (and to silence complaints from faculty that the buddy system requirement is too onerous!) include:<o:p></o:p></pre><pre style='margin-left:.5in'>a buddy system online calendar, buddy system mailing list, and even buddies for hire (trained undergrads willing to sit in the lab (doing homework) and be a buddy, for pay. No one has used this last tool since it was implemented a year ago, but it has helped silence the faculty critics) <a href="http://fab.eng.utah.edu/buddy-tools">http://fab.eng.utah.edu/buddy-tools</a><o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Outside the fab we have a monitor indicating who is inside (buddies are not required in the adjacent SEM/XPS lab or in the packaging lab).<o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://fab.eng.utah.edu/index/about-us/Home/lab-members/userinlab">http://fab.eng.utah.edu/index/about-us/Home/lab-members/userinlab</a><o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>And we use the combination of card-key records (we have our own system, and so have real-time access) and video monitoring (including at wetbenches) to enforce the rule as others have indicated. <o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Recently we began generating a monthly report of buddy system violations, sorted by research group, and send the relevant violations to the faculty PI along with their user fee invoice, so that he or she is aware of what is going on with their own group. We do not necessarily associate (yet) disciplinary measures with this report, as we wish to initially just raise the visibility of the need for adherence (and the fact that we are paying attention) first.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>We do not yet have a culture wherein the labmembers themselves feel a sufficient sense of ownership that they are generally willing to either confront a safety violator in the lab, or else report violations. But it is part of our formal training, that "someone else's safety violation certainly affects you in a number of ways, including..." Such a culture is an ideal that we are striving for: self-monitoring & self-correction among the labmember community. In order to achieve this sense of ownership, belonging, responsibility & accountability, we have had our student representatives assist us by actually writing the policies and being involved in scheduled and weekly lab cleans.<o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://fab.eng.utah.edu/uploads/pdfs/Nanofab_User_Policy%20Aug_2010.pdf">http://fab.eng.utah.edu/uploads/pdfs/Nanofab_User_Policy%20Aug_2010.pdf</a><o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>As we prepare to move into our new facility, we will be making additional improvements to the buddy system:<o:p></o:p></pre><pre style='margin-left:.5in'>(1) by implementation of CORAL and interlock boxes on each of the tools (now in progress), we will be able to begin billing based on time spent on a tool, rather than time spent in the lab. Our interest in the buddy system is a key driver for this administrative change. We hope that by so doing, a researcher will be able to more easily find a colleague to be a buddy (or associate in the same research group, perhaps), since that buddy will not have to pay to be in the lab.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>(2) our new facility includes a clean conference room attached to the fab and accessible in the bunny suit as well as from a pedestrian entrance (think of the negotiation table between N & S Korea, entered on either side with a symbolic barrier to crossing between. Since ours is not complete yet, here is a link to the Korean table!). <o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://www.traveladventures.org/continents/asia/panmunjom2.shtml">http://www.traveladventures.org/continents/asia/panmunjom2.shtml</a><o:p></o:p></pre><pre style='margin-left:.5in'>One of the functions of our clean conference room at night will be for buddies not working on the fab tools to have a place to sit in a bunny suit and work on reports or mask designs or device simulations.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>(3) Carding out of the lab, we will be implementing an annunciator to indicate if someone is about to exit, and leave someone else stranded without a buddy. Clearly, the policies and software methods for allowing someone to enter alone (needs a buddy to also enter within a prescribed period) or exiting (and potentially stranding someone) requires special attention, and we are working on how to implement this presently.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>ASIDE: As a result of the recent informative LABNETWORK thread on TMAH, we are implementing changes in our lab. My recent question posed to the LABNETWORK on alarm response protocols was also very helpful in providing us much useful information. <o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>I suggest that in addition to the UGIM meetings held once per year and which describe these types of management topics, Perhaps we should also have some forum in the "off-years" to get into detail regarding the soft administrative systems, and provide a means of sharing not only best practices, but also code for the soft systems themselves. For example we are implementing CORAL with home-designed interlock boxes with off-the-shelf components, and are quite willing to share our design and the associated CORAL software modules. We are currently in the planning/design stage of our new prox-card entry and tool enable system with associated buddy system features. Others have implemented add-ons to CORAL, or perhaps generated their own soft admin systems with modules that can be ported to others. Is it worthwhile attempting something such as this? We at Utah would be happy to host the first, unless someone else would like to do it.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Thank you all,<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>--Ian<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>********************************************<o:p></o:p></pre><pre style='margin-left:.5in'>Ian R. Harvey, Ph.D.<o:p></o:p></pre><pre style='margin-left:.5in'>Research Associate Professor<o:p></o:p></pre><pre style='margin-left:.5in'>Department of Mechanical Engineering<o:p></o:p></pre><pre style='margin-left:.5in'>Adjunct Associate Professor<o:p></o:p></pre><pre style='margin-left:.5in'>Department of Electrical & Computer Engineering<o:p></o:p></pre><pre style='margin-left:.5in'>2232 MEB<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Associate Director, Utah nanofab<o:p></o:p></pre><pre style='margin-left:.5in'>College of Engineering / University of Utah<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>mail to suite 2110 MEB, 50 S. Central Campus Drive<o:p></o:p></pre><pre style='margin-left:.5in'>Salt Lake City, Utah 84112-9011<o:p></o:p></pre><pre style='margin-left:.5in'>801/585-6162 (voicemail)<o:p></o:p></pre><pre style='margin-left:.5in'>801/581-5676 (lab main number)<o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://www.nanofab.utah.edu">www.nanofab.utah.edu</a><o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Begin forwarded message:<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>From: "Hathaway, Malcolm" <a href="mailto:hathaway@cns.fas.harvard.edu"><hathaway@cns.fas.harvard.edu></a><o:p></o:p></pre><pre style='margin-left:.5in'>Date: May 31, 2011 7:07:41 AM MDT<o:p></o:p></pre><pre style='margin-left:.5in'>To: <a href="mailto:labnetwork@mtl.mit.edu">"labnetwork@mtl.mit.edu"</a> <a href="mailto:labnetwork@mtl.mit.edu"><labnetwork@mtl.mit.edu></a><o:p></o:p></pre><pre style='margin-left:.5in'>Subject: Re: [labnetwork] 24/7 operations<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Hi all,<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>This is Mac Hathaway, at Harvard CNS. We have protocols in place similar to those described by John, with the exception that our "toxic" gases (flammables and anything monitored with sensors, Cl2, SiH4, BCl3, etc) are only enabled from 6 AM to 8 PM. We have had discussions about whether this restriction is still needed, given the maturity of our toxic gas monitoring, but 6 AM-8 PM is the current scheme. Everything else in the cleanroom is physically accessible 24/7 (most notably, from a safety standpoint, wetbenches).<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>One thing that is a little different here is that we have an ERT (Emergency Response Team), similar to what exists in many commercial fabs, (not typical for academic sites, as I understand it). The ERT consists of most of our cleanroom staff. We meet monthly for training (and pizza), and we are all on call in the event of an emergency in the cleanroom.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>We have the buddy rule for working with hazardous materials, with a strong emphasis on the need for a buddy for any work during "off-hours", but as John pointed out, it's not something that lends itself to absolute compliance. With regard to "encouraging compliance", how do people feel about the use of video cameras on the wetbenches? I understand that some locations are using them; has wetbench user "behavior" improved when cameras are in use? Obviously, 24-hour monitoring is not practical, but does the "someone is watching" effect yield positive results?<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Mac Hathaway<o:p></o:p></pre><pre style='margin-left:.5in'>Senior Process Engineer<o:p></o:p></pre><pre style='margin-left:.5in'>Harvard CNS<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Begin forwarded message:<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>From: "Luciani, Vincent" <a href="mailto:vincent.luciani@nist.gov"><vincent.luciani@nist.gov></a><o:p></o:p></pre><pre style='margin-left:.5in'>Date: May 31, 2011 7:29:28 AM MDT<o:p></o:p></pre><pre style='margin-left:.5in'>To: "'Matthieu Nannini, Dr.'" <a href="mailto:matthieu.nannini@mcgill.ca"><matthieu.nannini@mcgill.ca></a>, <a href="mailto:labnetwork@mtl.mit.edu">"labnetwork@mtl.mit.edu"</a> <a href="mailto:labnetwork@mtl.mit.edu"><labnetwork@mtl.mit.edu></a><o:p></o:p></pre><pre style='margin-left:.5in'>Subject: Re: [labnetwork] 24/7 operations<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Hello Matt,<o:p></o:p></pre><pre style='margin-left:.5in'> <o:p></o:p></pre><pre style='margin-left:.5in'>Here at the CNST NanoFab (<a href="http://www.nist.gov/cnst/index.cfm">http://www.nist.gov/cnst/index.cfm</a>), we are staffed from 7 AM to midnight, M-F. We use card key access control system and Coral. All users are locked out after hours and we program their afterhours access into the system after their request for after hours access is approved.<o:p></o:p></pre><pre style='margin-left:.5in'> <o:p></o:p></pre><pre style='margin-left:.5in'>· Advance notification, the day before is fine. That way we can avoid any tool repair or facilities conflicts. The advance notification also helps me help others to find a buddy if needed.<o:p></o:p></pre><pre style='margin-left:.5in'>o A loose, casual buddy agreement between users, leading to one user leaving before another or one working in their office while the other was in the lab was a common failure mode at first. So, we require verbal or email confirmation from both people that they are committed to being each other's buddy at all times.<o:p></o:p></pre><pre style='margin-left:.5in'>· Once approved, they can use all tools/processes.<o:p></o:p></pre><pre style='margin-left:.5in'>· We use deterrence to discourage cheating, because it will happen. I randomly check Coral records and our CCTV video tapes and suspend/revoke cleanroom privileges for violators (from a 2 week suspension to full revocation depending on the degree of fraud/abuse). Word travels fast when this happens and is a strong deterrent.<o:p></o:p></pre><pre style='margin-left:.5in'>· Some tools outside the cleanroom, like the FIB or AFM, can be used without a buddy after I confirm with whoever trained them that they have the required proficiency.<o:p></o:p></pre><pre style='margin-left:.5in'>· The NanoFab staff is notified automatically via Blackberry about any gas or fire alarm 24/7.<o:p></o:p></pre><pre style='margin-left:.5in'> <o:p></o:p></pre><pre style='margin-left:.5in'>Let me know how it goes for you.<o:p></o:p></pre><pre style='margin-left:.5in'> <o:p></o:p></pre><pre style='margin-left:.5in'>Vince<o:p></o:p></pre><pre style='margin-left:.5in'> <o:p></o:p></pre><pre style='margin-left:.5in'> <o:p></o:p></pre><pre style='margin-left:.5in'>Vincent K. Luciani<o:p></o:p></pre><pre style='margin-left:.5in'>NanoFab Manager<o:p></o:p></pre><pre style='margin-left:.5in'>Center for Nanoscale Science and Technology National Institute of Standards and Technology 100 Bureau Drive, MS 6201 Gaithersburg, MD 20899-6200 USA<o:p></o:p></pre><pre style='margin-left:.5in'>+1-301-975-2886<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>_______________________________________________<o:p></o:p></pre><pre style='margin-left:.5in'>labnetwork mailing list<o:p></o:p></pre><pre style='margin-left:.5in'><a href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a><o:p></o:p></pre><pre style='margin-left:.5in'><a href="https://www-mtl.mit.edu/mailman/listinfo.cgi/labnetwork">https://www-mtl.mit.edu/mailman/listinfo.cgi/labnetwork</a><o:p></o:p></pre></div></body></html>