Fear of Lost Jobs Is Hurdle to Reining In Defense Contracts -...
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
URL Tag Cloud
Bookmark History
Saved by 1 people (0 private), first by anonymouse user on 2009-03-09
- Transtracker on 2009-03-09 - Tags F-22 , fcs , procurement
Public Sticky notes
Highlighted by TransTracker
Highlighted by TransTracker
on 2009-03-09 by TransTracker
Missile defense is so obviously irrelevant. With Iran test firing long range missiles, and North Korea preparing to do the same, and even threatening war if we attempt to shoot it down, anyone can see that there's no reason why we would want to develop missile defense systems. And beyond that, since when does the Air Force need airplanes, the Navy ships, or the Army new tanks, artillery, armored transports, etc.? [sarcasm]
Many studies, including those by the Government Accountability Office and Pentagon boards, have shown that many weapons projects start out with unrealistically low cost estimates, depend on technologies that are not ready and face constant changes in design requirements.
“The root cause is that you’ve got an ever-changing kaleidoscope of entities involved in the decisions, and nobody has the authority to just say no and be held accountable for it,” said John F. Lehman, the first secretary of the navy in the Reagan administration. “That’s what has to change.”
Highlighted by TransTracker
on 2009-03-09 by TransTracker
While I don't want to defense massive cost overruns (because I agree it's a problem), this argument makes a number of unrealistic assumptions about teh way technological change works. First, of course the technologies are "not ready." That's why it's called "research and development." It will not be perfect on day one. And the fact that it is not perfect on day one is not evidence that it will never work. This is an argument that gets leveled constantly against new weapon systems. Second, design requirements will change, and indeed should change. As the R&D process moves forward, as new lessons are learned, and as mission requirements, the likely environment of conflict, etc., all change, so will dessign requirements. Third, multiple entities will and should have input. Taken altogether, it is unrealistic and indesirable to have one authority that works to create a new system only from existing technologies where the design is fixed from the beginning and unresponsive both to lessons learned during development and from input from other entities.


Public Comment