Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

unhappycamper

(60,364 posts)
Thu Sep 18, 2014, 09:42 AM Sep 2014

JSF & The Path of DOOM

http://breakingdefense.com/2014/09/the-path-of-doom-jsf-et-al/



JSF & The Path of DOOM
By Lt. Col. Dan Ward on September 16, 2014 at 10:17 AM

In February of 2014, Lt. Gen. Charles Davis, the Air Force’s top uniformed acquisition official, said big, audacious programs like the Joint Strike Fighter were “doomed the day the contract was signed.” As the former Program Executive Officer for the JSF, he brings a pretty credible perspective to the situation. Given his first-hand experience and the F-35’s track record of delays, cost overruns, technical problems, operational limitations, and the recent grounding of the entire fleet due to an engine fire, I am very much inclined to agree with him.

The phrasing of Lt. Gen. Davis’ assessment is important: He is not saying the F-35 was recently doomed, or is troubled because of late-breaking developments like sequestration, the Afghan drawdown, recent technical challenges, or the latest Chinese stealth fighter. Not at all. He is saying that America’s most expensive weapon system began its very existence behind the eight ball. It was doomed from the start.

The seeds of JSF’s troubles were firmly rooted in 2001, when the system development contract was signed. For that matter, the situation was already pretty clear in 1996, when the Air Force awarded contracts to develop a pair of competing prototypes. The proposed aircrafts’ complexity, cost, and development timeline all pointed to an ill-advisedly large, pricey, and slow effort that was immediately on track to cost more, take longer, and deliver less than promised. The problems that followed (and the accompanying charges of acquisition malpractice) were therefore entirely predictable and, more importantly, avoidable.

~snip~

The JSF malpractitioners chose to follow what we might call “the path of D.O.O.M.” – Delayed, Over-budget, Over-engineered, Marginally-effective — by establishing a massive bureaucracy, a distant delivery date, an enormous budget, and a highly complex technical architecture. This fostered an expansive culture where rising price tags and receding milestones were seen as inevitable and where the primary problem-solving strategy was to add time, money, and complexity to the project. Data from the GAO and other reliable analysts agree this is a demonstrably ineffective approach. Because it was on the Path of D.O.O.M., the JSF’s Nunn-McCurdy breaches in 2004 and 2010 were simply a matter of time.
1 replies = new reply since forum marked as read
Highlight: NoneDon't highlight anything 5 newestHighlight 5 most recent replies
JSF & The Path of DOOM (Original Post) unhappycamper Sep 2014 OP
broken by design jollyreaper2112 Sep 2014 #1

jollyreaper2112

(1,941 posts)
1. broken by design
Thu Sep 18, 2014, 10:30 AM
Sep 2014

The goal was not to deliver an operational fighter to the military, it was to deliver trillions to the defense contractors. Mission accomplished.

Latest Discussions»Issue Forums»National Security & Defense»JSF & The Path of DOO...