F-35 Software: DoD's Chief Tester Remains Unimpressed
By Robert N. Charette
Posted 3 Feb 2014 | 18:49 GMT
U.S. Air Force
Last week was a very quiet week in regard to reported IT-related system snarls, snags and snafus. With yesterday being
ground-hog day here in the U.S., and in keeping with the spirit of the
movie of the same name, I have decided to
return once more to F-35 Joint Strike Fighter and its continuing software “challenges.”
Last week, the
Department of Defense's Director of Operational Test and Evaluation (DOT&E), J. Michael Gilmore, publicly released his
annual report on major U.S. defense acquisitions. Gilmore reiterated his frustration with the lack of reliability and supportability of software in major defense support and weapon system programs. While Gilmore’s report highlighted many defense programs' software problems, those related to the F-35 continue to hold center stage.
For instance, in October 2013, a new increment of Block 2B software—the
block that provides initial combat capability—that was supposed to include many fixes to previously identified deficiencies, began flight testing, the report says. However, the DOT&E report goes on to say:
“Initial results with the new increment of Block 2B software indicate deficiencies still exist in fusion, radar, electronic warfare, navigation, EOTS, Distributed Aperture System (DAS), Helmet‑Mounted Display System (HMDS), and datalink. These deficiencies block the ability of the test team to complete baseline Block 2B test points, including weapons integration.”
Although plans call for the military to “complete Block 2B fight testing in October 2014...there is no margin for additional growth to meet that date,” the DOT&E report found. “Projections for completing Block 2B fight testing using the historical rate of continued growth ... show that Block 2B developmental testing will complete about 13 months later, in November 2015, and delay the associated fleet release to July of 2016.”
In addition, the DOT&E report notes that there are still problems with the F-35's Block 2A software, i.e., the block that is “designed to provide enhanced training capabilities to the Integrated Training Center at Eglin AFB, Florida, and to the first operational units.”
The F-35 test teams found:
“deficiencies in the aircraft sensor operations, particularly the Electro-Optical Targeting System (EOTS), aircraft communications capabilities, pilot electronic interfaces, and the aircraft Caution, Advisory, and Warning System. Although the software was intended to provide more mission systems capability, poor sensor performance and stability, excessive nuisance warnings, and disproportionate pilot workload required for workarounds and system resets made the software of limited utility for training. In any type of operational mission scenario, the performance of the software would be unacceptable.”
These and other software issues, e.g., related to the F-35's Autonomic Logistics Information System (
ALIS)—as well as
non-software related problems—notwithstanding, neither the U.S. military's nor its international partners’ enthusiasm for the F-35 has diminished. The Marine Corps, for instance, insists it's still
planning for a 2015 IOC (initial operating capability) for its F35B version, while the
U.K. says it is close to placing its first order and
South Korea is expected to do so later this year.
The F-35 Program Office complained that while Gilmore’s report “was factually accurate” it “did not reflect concerted efforts under way by this office and industry to address software, reliability and maintenance issues,”
Reutersreported. “Of course, we recognize risks still exist in the program, but they are understood and manageable,” the Program Office insisted.
Gilmore may need to remind the F-35 Program Office (again) that the DOT&E office deals with facts, not promises.
F-35 Software: DoD's Chief Tester Remains Unimpressed - IEEE Spectrum