[labnetwork] 24/7 operations
John Shott
shott at stanford.edu
Sun May 29 12:10:27 EDT 2011
Matt:
I'm sure that there will be a lively and interesting discussion of this
topic. My guess is that we all probably have some form of "buddy rule"
will differing approaches and degrees of success in enforcing it.
Let me get the ball rolling by telling your what we do in the Stanford
Nanofabrication Facility.
Yes, we are open 24/7 but are only staffed 1+ shifts .... approximately
6 a.m. to 6 p.m. M-F. We don't limit tools or processes.
Because of our physical configuration, the sub-fab where pumps,
chillers, scrubbers, etc live are off limits and not accessible to lab
members. Same for the gas bunkers and main chemical storage areas so we
at least don't have to worry about folks in those areas trying to
"adjust" things themselves.
Our card key system is managed as a part of the university-wide system
so we don't have real-time access to who enters the lab. Folks that
tailgate when entering the lab or fail to swipe the card reader when
they leave would make that information virtually useless in terms of
actually knowing who is in the lab at any point in time.
We have a rotating cell phone carried by several members of the senior
staff that is for emergency calls for anyone in the lab and is also the
first number that the central-campus facility monitoring system calls if
sensors relevant to our operation go into alarm. Things like toxic gas
sensors automatically sound the evacuation alarms in the lab and, if gas
sensors in breathing air go into alarm, call the Fire Department as
well. Being in earthquake country, we also have a seismic sensor that
shuts off all gases and sound the alarm in the event of an earthquake.
Although we don't use this particular feature, since I know that you are
running Coral, that gives you the ability to create and use either a
lab-wide role or an equipment-specific role of "restricted" that would
allow you to define policies that would prevent people from reserving or
enabling equipment outside the period when staff was available. That
allows you to let someone get more experience with staff resources
available before you "turn them loose" with unrestricted access. Of
course, the downside is that you and your staff have to manage who is
"restricted" and then determine based on time or more rigorous means
when someone is allowed to work at any time. Also, while you can limit
when people enable a tool to a certain time window, it's very hard to
control when they quit using it.
Are there times in our facility when people violate the buddy rule?
Probably ... Of course, depending where people are in the lab, just
having a second person in the lab isn't a guarantee that they'd be in a
position to help in the event of a problem.
I'll be interested to read other offerings on this topic.
Thanks,
John
More information about the labnetwork
mailing list