UC Wins Contract to Run Los Alamos
crlove writes "LA Times reports, 'The University of California today won its hard-fought bid to continue operating the Los Alamos National Laboratory in New Mexico, beating back a challenge from a Lockheed Corp.-University of Texas team to run the nuclear weapons research facility...
For months, the New Mexico laboratory had been shaken by allegations and revelations of theft, fraud, security lapses and lax oversight.'"
Part of the deal that had my parents paying for my education was an undergraduate, course load heavy in Economics, Commmerce and Business Law. Having the tools to gain some perspective in how large organizations run, it's instructive to look into the internals of a giant, once prestigious organization like Los Alamos and try to trace the systemic flaws that led to it's current plight.
"Academicians are more likely to share each other's toothbrush than each other's nomenclature."
Cohen
While the University of California will be deeply involved in the new management of the Los Alamos National Laboratory, it is not strictly correct to call this a win for UC. As the DOE press release makes clear, the winner of the competition was a limited liability corporation comprised of UC, Bechtel, BWX Technologies and others. The difference is very significant in some areas. For example, LANL personnel will no longer be members of the UC staff and participants in their retirement system, but employees of the LLC. The DOE did not release details of the winning proposal yet. As they do, I believe it will become increasingly clear that there is much more to this change than just UC continuing to play the same role.
There's been a lot of ambivalence at Berkeley in the past about it running labs like this. One line (not that I believe it) goes that it is better for the Univeristy involved than leave it strictly to the defense contractors.
I think it provides UC with some serious money and opportunity to do major research, so the geeks get attracted to it and tend to brush over any ethical concerns.
E.g. who else has the budget and inclination for some serious computin'?
Similar stuff happened at MIT in the beginning of computing. It was somehow harmless when it was just Ma Bell wanting telephone switching technology -- but the defense contractors have budgets and interesting requirements, so it is easy to look the other way.
http://www.thebricktestament.com/the_law/when_to_
The postings are interesting. It appears that other labs are being grabbed by the original university that managed it AND a large company. For example, BWXT teams with University of Chicago for Argonne Lab. This makes me wonder if this is the wholesale sell-off of our R&D labs to private enterprise. IOW, will these companies now have unfettered access to all the ideas that comes from these labs and will declare them their own? I only mention this because of the large system support contract that GWB awarded Accenture (a company of crooks and inepts) a HUGE contract that takes place overseas. They not only pull the jobs away but much of the code is now being done elsewhere. IIRC, Accenture will have partial ownership as well as will be in control of a large number of federal systems.
I prefer the "u" in honour as it seems to be missing these days.
But seriously, my opinion is this: Your first point (about not knowing the next year's budget numbers) is true, but the management minimises that problem by saving some funds into any number of accounts, so they can shift them as they need to. I also have to disagree with your second paragraph somewhat:
No, the biggest management problem is balancing "Security" and "Efficiency". If it's easy to do, it's probably not secure, and vice versa. And the security side wins most decisions (which is usually a GoodThing(tm), given the stuff people play with at the Labs.) Nobody MEANS to cause a problem, but they break one little rule ... and it gets easier to do it that way, or it encourages somebody else to break one little rule too ... and as you say, "things can get kind of out of hand."
(*And nobody seems to want to write such software for OSX/Linux/etc ... why is that?)
Hmmm. Your ideas are intriguing to me and I wish to subscribe to your newsletter.