Experts to Study F-35 Software Delays

F-35_training

The U.S. Defense Department’s top weapons buyer is assembling a team of independent experts to study the F-35 fighter jet’s software development delays.

Frank Kendall, the Pentagon’s undersecretary of defense for acquisition, technology and logistics, was ordered to put together a group to study the issue and submit a report to Congress by March 3 as part of 2014 National Defense Authorization Act, which sets policy goals and spending targets for the fiscal year that began Oct. 1.

President Barack Obama signed the legislation into law today while vacationing with his family in Hawaii.

Air Force Lt. Gen. Christopher Bogdan, who oversees the F-35 Joint Strike Fighter, the Pentagon’s most expensive weapons acquisition program, and auditors from the Government Accountability Office, the investigative arm of Congress, have identified the aircraft’s software development “as an area of risk because of its complexity,” according to an earlier version of a report accompanying the legislation.

The F-35, which is made by Lockheed Martin Corp., requires more than 8 million lines of code, compared with about 2 million for the F-16 and less than 1 million for other fourth-generation fighter aircraft, according to Steve O’Bryan, vice president of F-35 program integration and business development at the Bethesda, Md.-based defense contractor.

O’Bryan in June said Lockheed reassigned some 200 engineers to work on the F-35’s software, many from outside the aeronautics division, with specialties in space, ship-board and sensor technology, O’Bryan said. The company also invested about $100 million to build a second laboratory where the employees work in shifts around the clock to write, test, and verify the code, he said.

By using a more limited version of the software, the Marine Corps plans to begin operational flights of the fighter jet in 2015, followed by the Air Force in 2016 and the Navy in 2019.

The full software package, known as 3F, is designed to support a suite of internal and external weapons, including the GPS-guided Joint Direct Attack Munition, laser-guided Paveway II bomb, Advanced Medium-Range Air-to-Air Missile, and infrared Sidewinder missile.

It wasn’t immediately clear how many or which experts would conduct the software study.

The Pentagon plans to spend $391 billion to develop and build 2,457 Lightning II aircraft, according to budget documents. That’s $4.5 billion, or 1.1 percent, less than a projection from last year due in part to revised labor rates. The stealthy, single-engine jet designed to replace such aircraft as the F-16, A-10, F/A-18, and AV-8B.

The legislation authorizes the department to spend $5.5 billion to buy 29 of the aircraft, including 19 for the Air Force, six for the Marine Corps and four for the Navy, according to the legislative report. The figure doesn’t include funding for research and development or spare parts.

About the Author

Brendan McGarry
Brendan McGarry is the managing editor of Military.com. He can be reached at brendan.mcgarry@military.com. Follow him on Twitter at @Brendan_McGarry.

30 Comments on "Experts to Study F-35 Software Delays"

  1. 8 million lines from various vendors and teams.
    A few things come to mind:
    Windows
    China
    Stuxnet

    I have sympathy for the developers tasked with writing software to handle life critical functions on cutting edge hardware that has to seamlessly and reliably perform a multitude of tasks while being secure from outside mischief.
    And all this for a program that comprises thousands of planes, in three main variants, to be used by multiple operators (including other nations).
    My advice: Test, test, test again. And create a "red Team" to find vulnerabilities before the stuff is fielded.

  2. If you think the Obamacare website was bad, just wait till they try to make the "3F" Software work in the " Junk Strike Fighter". And from what I've read on Aviation Week it is more like 20 million lines of code not 8 million. 8 million is just the block 2 software. To put it in Perspective think Microsoft Vista and how well it worked with older hardware ( NOT Very WELL). Remember a lot of the current weapons we are using were built on 8/16-32/64 bit hardware (3rd & 4th Gen Fighters ) and the F-35 use new more powerful data buses etc. etc. Thats just the connectors, with well over 20+ years of coding experience, and making new software work with old hardware, the FUN & DELAYS have just begun!!!

  3. What precisely is an investigation of the blatantly obvious going to cost us I wonder? I bet we spend $100 million to be told LM promised too much, assigned too little resources, and the DoD made too many changes in the middle. Which is what we pretty much know now I think.

  4. I will display my complete ignorance of programing here and ask a question.

    Why do they have to reinvent the wheel each time a new aircraft is fielded and write entirely new code for everything, including weapons that are already fielded on current aircraft? Is there really no way to create an "industry standard," so to speak, for the various sub systems that the manufacturer can build and spec to without having to reinvent the system each time?

  5. Yeah, this is what we need is a huge, taxpayer funded study to figure out why a company that makes more profit by dragging out development can't get their software done any faster. That's not incredibly stupid at all.

  6. The complexity of the F-35 software is driven by the integrated sensor suite. The old way of doing business was each subsystem had it's own software with a central computer to direct the activity. Then there was a need to have dedicated signal processors for each sensor and they didn't really interact. Now the idea is that the sensors will be able to interact in real time and the processors will have access to each other's data. It's not easy to meld the sensor and flight control data while tracking a target in real time.

  7. Part of the problem is government quotas. When I was in the business we always had a certain number of people who were the “correct color” for the job at hand. I’ll never forget when a black female software engineer asked me what a stack was. I’m a hardware guy and I still knew what a stack was.

  8. Our government needs to go back to the good old competitive bidding process. Prices should be fixed, and any overruns not caused by gov't scope creep are absorbed by the contractor.

  9. It would be so much easier if everyone just used flight simulator software in an MMO environment to fight wars. The software just works.

  10. Shows real stupidity here. We at one time did have a 5th gen fighter on in production no software problems. called the F-22. Yet the idiots in DC killed production and go with this Junk Strike fighter instead and it all inferior in performance too.

  11. Every time I point out the truth about this failing program my comments get deleted :-[

  12. It's Obamacare.

  13. I suspect censoring. NSA is empowered to black line kernels of truth from comments here. When in doubt, eliminate the entire comment. It has happened to me, more than once.

  14. Considering that the F32/35 series of aircraft were the first operational types designed and built to fly relying on computer moderation, one would think that A) the requisite software would have been as important as cutting metal and B) keeping that aspect as simple and tamper resistant (free of tangential sub routines) as possible, would have been a perquisite in the design brief.

    Like the proverbial battle plan, that too went out the window on first contact long, long ago.

  15. Lonnie Williams | December 28, 2013 at 8:32 am | Reply

    The software delays are the critical keystone to this jet, but not the full story. I spent 10 years on the program developing the training for all versions of this jet so when the software lags so does just about everything else – training for sure! Now we have a number of different syllabi because of the software versions on the jets at the training facility. Then maintenance is casing their butt because the 'black boxes' are coded to work with certain versions of software…so round and round it goes where it stops…who knows?

  16. The basic underlying problem is the vendor (Lockhead) views this as a make work project and will do anything to make it last as long as possible therefore making the most dollars possible. They truly don't care about the outcome-only the dollars. The way this program is heading, it will eat up the entire DOD budget in a few years.

    But on top of this is the shear incompetence of the project manager (the air force). They have repeated show their inability to mange the project and the vendor and one wonders if the air force will be giving the vendor 20+ years and 6 Trillion dollars to complete this project

  17. You are all right!!!!

  18. Most likely, the team of independent experts will marvel at the immaculate political engineering of the Lockheed Martin F-35 Lightning II.

  19. PLEASE make this program go away!

  20. There is an old saying at Lockheed… "money in garbage out"

    The F-35 isnt a project management issue it's a fraud issue. They don't need to call some software experts they need to call the FBI.

  21. Has anyone here actually SEEN CODE for the F-35? ..What development methodology/approach are the developers using? What version control? Are they using Test/Behavior Driven Development? (etc, etc)..

  22. The solution to the F35 was the already operational F22 (a better plane than the F35 will ever be … and cheaper than the F35 when the final accounting is done on the F35). Oh .., but the dickhead in chief got rid of the F22 production line …

  23. I'm guessing the F-35 will have to re-architect its avionics and software before they will ever reach full capability. Perhaps they can use the FACE technical standard from The Open Group to ease the complexity problem, but they will need to add processing power to do so. That's not such a big deal because obsolescence is already affecting the original computer hardware. If we don't start developing modular, segmented, open, hardware-abstracted software capabilities, we'll never reach our goals.

  24. By the time the F35 is declared operational and all the bugs are worked out the Chinese and Russians will have already stolen all our secrets and will be building the same airplane using our technology. Then we get to start all over again with a F36

  25. Hope the same company that did Obamacare is not working on this stuff.

  26. The biggest joke of all will be when "they" figure out how to detect "stealthy" aircraft consistently and reliably ….. then it's back to ACM (dogfighting) with SRAAM's and guns. The F-35 appears to be deficient in the Air Combat area.
    I hope I'm wrong. I think the "JOINT" part of this programme is where the real problems arise.

  27. Forget the "software", the main problem lay in the meeting rooms in DC where decisions are made by those that do NOT have the knowledge or background listen to those with vested interest. If you stand back and look you'll see that the issue starts with Green Hills then cascades into an uncontrollable runaway bolstered by rent seeking crony capitalism.
    Start with the FCC and end with the DOD, look at what is being done and why then start over with a clean slate. In writing software for over 30 years the one thing that has enable success has been to look at the problem from a new prospective then rewrite everything from scratch to deal with past tunnel issues.

  28. Thanks for sharing your thoughts about joint strike fighter.
    Regards

  29. http://www.ihatewritingessays.net/ Wonderful site. Lots of useful info the following. I’m transmitting this to many pals ans furthermore discussing throughout yummy. As well as, great attempt!

Leave a comment

Your email address will not be published.


*