LANL: The Corporate Story

Isn't it about time for another security flap?
 

I guess its just a curious coincidence that LANS/LANL put out a press release after these incidents started being discussed on this blog.
 

If you weren't informed about it, you probably didn't need to know. I received a forwarded email from my group leader on Jan 22 about this. The email he forwarded was dated Jan 19.

If you don't work at TA-55 why would you need to be informed?
 

Anonymous @ 2/20/2007 12:51 PM.

OK, but why would we not need to be informed? As a LANL employee who might be seeking to transfer to another LANL organization, I would like to know as much about other LANL groups and divisions as possible so that I might make an informed choice. The safety and security records of these organizations is part of the equation.
 

Just another incident(s) that DOE is responsible for and aragont LANL workers will be disiplined for. DOE should be fined an amount equal to the LANL shortfall. Nanos also is responsible for this incident(s) and should forfeit his severence package LANL so graciously awarded him for helping sink LANL even deeper. The LANS/LANL director should personally address congress and inform them DOE is responsible for this incident as well as previous security incidents.
 

Mr.Pdog
Your blog made the managers standup meeting at TA-55 this morning. It was the safety topic(no they didn't say if you read it you will be drawn a quartered). One of the five new Div leaders used it as a segue to talk about the lack of communication at LANL. The sad part is that all the GL's at the meeting didn't seem to understand that when they learn something that may be of value to the workers maybe they should pass it along - to the workers that is. Imagine that.
 

12:51 pm:

You are correct, all these incident reports are forwarded to a long list of people on the day, or day after, they occur. There is no attempt to hide them. I get them routinely over email, and frankly, delete them because there are too many. If the local rag doesn't care, why should anyone else? Why not complain to them?

This is just more "bash management, the truth be damned" that is all too prevalent here.
 

"You are correct, all these incident reports are forwarded to a long list of people on the day, or day after, they occur. There is no attempt to hide them. I get them routinely over email, and frankly, delete them because there are too many."

I'll bite. How do I get on that email distribution list?
 

These incidents were known to the employees who needed to know about them, especially those who routinely work in gloveboxes with plutonium. Work was suspended, safety protocol's reviewed, and glovebox procedures improved by the lessons learned process. The matters were reported up the appropriate chain of command, and the director even mentioned it at his "all-hands" meeting.

We should have a mindset to learn from accidents and mistakes, not fear appraisals from management, or even try to blame somebody. There is risk in everything we do, and we should do our best to reduce that risk wherever we can. Perhaps if everyone would put their minds to work (which I believe is what the DOE is paying us to do) instead of whining and coplaining, and follow procedures and policy, that LANL will be better off.
 

Bullshit, 1:19pm. LANL staff deserve to be told when an on-site accident has occurred, especially serious ones involving plutonium uptake.

Your "the people who needed to know were told" crap is managerspeak for "we wanted to cover our asses by making sure as few people as possible learned that there had been two more fuck-ups at LANL".
 

mgr@plutoniumpalace forgot to say...

besides, small doses of Pu can be good for you. It has the same effect at Viagra, plus your Pp will glow in the dark like Luke Skywalker's sword!
 

"LANL staff deserve to be told when an on-site accident has occurred, especially serious ones involving plutonium uptake."

Consider yourself told. There are still more that have not made the news.