<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Aptos;}
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Aptos;
color:windowtext;}
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 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'>Hi all, <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>To continue/piggyback on the discussion below, where do you draw the line between what the center covers and when you go after the PI for payment? Is this only by breaking policies or by a dollar amount as well? <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>We have had many instances of students breaking policies and they suffered access related consequences but since the dollar amount was reasonable, we never went after PIs for payment, with the understanding that it’s a university setting, learning environment, and students will make mistakes and break policies. Getting after PIs for payment could be tricky because many of them don’t have funds that are allocated for this type of expenses.<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><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Dr. Nava Ariel-Sternberg<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Senior Director of CNI Labs<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Columbia University<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>CEPSR/MC 8903 <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>530 west 120<sup>th</sup> st. NY<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>NY 10027<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Office: 212-8549927<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Cell: 201-5627600<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><img width=101 height=43 style='width:1.052in;height:.4479in' id="Picture_x0020_1" src="cid:image001.png@01DAAA8A.08CCCFE0" alt="https://sustainable.columbia.edu/sites/default/files/content/crown%20commuter%20badge_1.png"><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><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 #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> labnetwork <labnetwork-bounces@mtl.mit.edu> <b>On Behalf Of </b>Tobi Beetz<br><b>Sent:</b> Thursday, May 16, 2024 5:13 PM<br><b>To:</b> Sean M. Langelier <sean.langelier@nanomelbourne.com><br><b>Cc:</b> labnetwork@mtl.mit.edu<br><b>Subject:</b> Re: [labnetwork] damage by users<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Sean – Thanks for the info! This is very helpful!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I just browsed through your website and really like how you have organized the various policy sections. There is a lot of great information there. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cheers,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt'>Tobi<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'>Tobi Beetz, Ph.D.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'>Associate Director, Stanford Nano Shared Facilities, Stanford University, <a href="http://snsf.stanford.edu">http://snsf.stanford.edu</a><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Sean M. Langelier <<a href="mailto:sean.langelier@nanomelbourne.com">sean.langelier@nanomelbourne.com</a>> <br><b>Sent:</b> Wednesday, May 15, 2024 2:17 PM<br><b>To:</b> Tobi Beetz <<a href="mailto:tobi@stanford.edu">tobi@stanford.edu</a>><br><b>Cc:</b> <a href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a><br><b>Subject:</b> Re: [labnetwork] damage by users<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Hi Tobi-<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>We've certainly dealt with these issues in the past. One major instance was the crashing of a sample into the SEM pole piece by a user who wasn't following protocol. All of our SOPs and training assessments are clear in stating that damage as a result of not following proper procedure is the responsibility of the user/supervisor to rectify. Still though it's hard to get traction sometimes especially where the breach to procedure is not clear and easy to prove.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>In the SEM pole piece example though, we were able to recover the ~$50k AUD (can't remember the exact figure) form the University... didn't end up coming out of the PIs pocket. So it can be done. :-)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>That said, we've a number of other instances where we were unable to definitively prove misuse. In these cases, all you can do is try to refine procedures to better protect the instruments.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>My two cents...<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best,<o:p></o:p></p></div><div><p class=MsoNormal>Sean<br clear=all><o:p></o:p></p><div><div><div><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal><span style='font-family:"Times New Roman",serif'>---------------------------------------------------------</span><o:p></o:p></p></div><p class=MsoNormal>SEAN LANGELIER PhD / He, Him<br>General Manager<br>ANFF Victoria <i>&</i><o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Melbourne Centre for Nanofabrication<o:p></o:p></p></div><div><p class=MsoNormal>151 Wellington Road<o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.5pt'>Clayton, VIC 3168 Australia</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Ph: +61 (3) 9902 4100<br>W: <a href="http://nanomelbourne.com" target="_blank">http://nanomelbourne.com</a><br>W: <a href="http://www.anff.org.au" target="_blank">http://www.anff.org.au</a><br>E: <a href="mailto:sean.langelier@nanomelbourne.com" target="_blank">sean.langelier@nanomelbourne.com</a><o:p></o:p></p><div><p style='margin:0in;margin-bottom:.0001pt'>---------------------------------------------------------<o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p><p style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p><p style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:0in'><o:p> </o:p></p></div></div></div></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, 15 May 2024 at 21:50, Tobi Beetz <<a href="mailto:tobi@stanford.edu">tobi@stanford.edu</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi All – we’ve had some recent incidents that has led me to reflect on policies in regard to paying for costs associated with misuse of equipment/procedures. For example, a Stanford student mishandled a TEM holder, causing about $5k in damage. We had a difficult time getting the PI agree to pay for the repair. Another example is an external industry user who incorrectly disposed a chemical down the drain. We are still waiting to see if the city imposes an administrative fine of up to $25k per day of violation.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Getting access to our center includes that every user agrees to the <a href="https://snsf.stanford.edu/labmembers/policies" target="_blank">SNSF Code of Conduct</a> where list the following: <i>We reserve the right to charge repair costs, equipment and staff time resulting from damage caused by users to the PI.</i><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On the external user side our agreement has an indemnification section which includes: <i>… obligation to make Center whole for any and all damage to Center, its facilities, and equipment to the extent arising out of the negligent actions or use by User or User Personnel. </i><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>While this all seems reasonable, I am wondering if you have dealt with this type of issue in a better way. Our approach seems a bit of a patchwork. On the accountability side for local students/postdocs, I am also wondering if other labs have focused on contract language with PIs instead of just getting users to acknowledge policies and an administrator/PI provide the charge account. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt'>Tobi</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt'>Tobi Beetz, Ph.D.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt'>Associate Director, Stanford Nano Shared Facilities, Stanford University, </span><a href="http://snsf.stanford.edu" target="_blank"><span style='font-size:10.0pt'>http://snsf.stanford.edu</span></a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><p class=MsoNormal>_______________________________________________<br>labnetwork mailing list<br><a href="mailto:labnetwork@mtl.mit.edu" target="_blank">labnetwork@mtl.mit.edu</a><br><a href="https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork" target="_blank">https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork</a><o:p></o:p></p></div></blockquote></div></div></body></html>