Incident: F-35 Logistics Software System Failure Risks Fleet Grounding

Published Date: 2016-04-21

Postmortem Analysis
Timeline 1. The software failure incident related to the F-35 Joint Strike Fighter program happened in August 2016 as per [Article 47492]. 2. The incident occurred in August 2016 based on the information provided in the article.
System 1. Autonomic Logistics Information System (ALIS) [42632, 42642] 2. Joint Direct Attack Munition, laser-guided Paveway II bomb, Advanced Medium-Range Air-to-Air Missile, and infrared Sidewinder missile integration [38304]
Responsible Organization 1. The Department of Defense officials were responsible for causing the software failure incident related to the F-35 Joint Strike Fighter [42632]. 2. The F-35 Joint Program office was also involved in the software failure incident and was responsible for addressing the issues raised by the Pentagon's top weapons tester [47492].
Impacted Organization 1. The F-35 fleet across the Air Force, Navy, and Marines [42632, 42642] 2. The Department of Defense [42632, 47492] 3. The Pentagon [42632, 47492]
Software Causes 1. Lack of testing done to ensure the software will work properly by the time the Air Force plans to declare its version of the aircraft ready for deployment [42632] 2. Problems related to software, data fusion, electronic warfare, and weapons employment, as highlighted by the Pentagon's top weapons tester [47492]
Non-software Causes 1. Lack of a backup system for the F-35's Autonomic Logistics Information System (ALIS) that could take the entire fleet offline in case of failure [42632, 42642]. 2. Concerns related to the lack of testing done to ensure the software will work properly by the time the Air Force plans to declare its version of the aircraft ready for deployment [42632]. 3. Issues with the radar system crashing and the gun system not being ready until 2019 [38304]. 4. Problems with the F-35's data produced being routed to a single main operating unit without any backup system or redundancy [42632]. 5. Concerns about the F-35's limitations related to software, data fusion, electronic warfare, and weapons employment, as well as achieving full combat capability [47492].
Impacts 1. The software failure incident with the F-35 Joint Strike Fighter's complex logistics software system could potentially lead to grounding the entire fleet, future cost increases, and schedule delays [42632]. 2. The failure of the Autonomic Logistics Information System (ALIS) software could result in the F-35 not being operated as frequently as intended, leading to additional costs estimated between $20-100 billion [42632]. 3. The lack of testing done on the software could delay the readiness of the aircraft for deployment by the Air Force in August and the Navy in 2018, with no guarantee that the software will be fully functional by 2019 [42632]. 4. The software issues with the F-35 program have raised concerns about the aircraft's ability to achieve full combat capability, potentially jeopardizing the program's success and long-term sustainability [47492]. 5. The F-35 program is at risk of failing to deliver its full combat capability, as highlighted by the Pentagon's top weapons tester, Michael Gilmore, in an assessment that detailed limitations related to software, data fusion, electronic warfare, and weapons employment [47492].
Preventions 1. Adequate testing of the software system could have prevented the failure incident by ensuring its functionality and reliability before deployment [42632, 42642]. 2. Implementing a backup system for the logistics software could have mitigated the risk of grounding the entire fleet in case of a failure [42632]. 3. Addressing the software limitations related to data fusion, electronic warfare, and weapons employment could have improved the combat capability of the F-35 aircraft [47492]. 4. Allocating sufficient resources to correct the significant performance problems identified by the Director of Operational Test and Evaluation could have helped in achieving full combat capability [47492].
Fixes 1. Addressing limitations related to software, data fusion, electronic warfare, and weapons employment [47492] 2. Correcting significant performance problems to achieve full combat capability [47492] 3. Implementing the necessary fixes and modifications as recommended by the Director of Operational Test and Evaluation [47492]
References 1. Article 42632 gathers information from the Government Accountability Office report and statements from Department of Defense officials, including Lt. Gen. Chris Bogdon and a spokeswoman for Lockheed Martin. 2. Article 38304 gathers information from a memo from Michael Gilmore, the Defense Department’s director of operational testing, to defense officials. 3. Article 42642 gathers information from an Aug. 9th memo from Michael Gilmore, the Defense Department’s director of operational testing, to defense officials, and statements from Lt. Gen. Chris Bogdon and a Department of Defense spokesman.

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident having happened again at one_organization: - The F-35 Joint Strike Fighter program has faced criticism from the Pentagon's top weapons tester, Michael Gilmore, who warned that the aircraft is "on a path of failing to deliver" its full combat capability due to limitations related to software, data fusion, electronic warfare, and weapons employment [Article 47492]. - The F-35 program has experienced issues with its logistics software system, known as the Autonomic Logistics Information System (ALIS), which could potentially ground the entire fleet due to lack of a backup system and concerns about functionality problems [Article 42632]. - The F-35 program has been plagued with software glitches, hardware malfunctions, and delays, leading to a budget increase of $200 billion over initial estimates [Article 47492]. (b) The software failure incident having happened again at multiple_organization: - The F-35 program has faced criticism and concerns from federal watchdogs, including the Government Accountability Office, regarding problems with the complex logistics software system that could lead to grounding the entire fleet [Article 42632]. - The F-35 program has been under scrutiny for software issues, including radar stability problems and limitations related to software, data fusion, and weapons employment, as highlighted by the Pentagon's top weapons tester [Article 47492].
Phase (Design/Operation) design, operation (a) In the F-35 Joint Strike Fighter program, the software failure incident related to the development phase of design is highlighted in the articles. The Autonomic Logistics Information System (ALIS) is described as the "brains" of the F-35, designed to support operations, mission planning, maintenance, and sustainability. The failure of ALIS could potentially take the entire fleet offline due to the lack of a backup system, posing a significant risk to the program [42632, 42642]. (b) The software failure incident related to the development phase of operation is evident in the F-35 program as well. The Pentagon's top weapons tester raised concerns about limitations in software, data fusion, electronic warfare, and weapons employment, impacting the F-35's full combat capability. The aircraft continues to demonstrate issues related to software, data fusion, and weapons employment, indicating operational challenges [47492].
Boundary (Internal/External) within_system (a) within_system: The software failure incident related to the F-35 Joint Strike Fighter's logistics software system is primarily within the system. The failure is attributed to issues with the Autonomic Logistics Information System (ALIS), which is considered the "brains" of the aircraft and is responsible for supporting operations, mission planning, maintenance, and sustainability [42632]. The Government Accountability Office report highlighted concerns about the lack of testing done on the software, potential schedule slippage, and functionality problems with ALIS that could lead to significant additional costs [42632]. The F-35 program officials acknowledged that if ALIS is not fully functional, the aircraft could not be operated as frequently as intended, emphasizing the critical role of the software in the program's success and long-term sustainability [42632]. Lockheed Martin, the lead defense contractor, is working on the development of the logistics software system and remains confident in the program's progress despite the identified issues [42632]. (b) outside_system: There is no specific mention in the articles of the software failure incident being caused by contributing factors originating from outside the system. The focus is primarily on the challenges and issues related to the internal development and functionality of the F-35's logistics software system [42632, 47492].
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident occurring due to non-human actions: - The F-35 Joint Strike Fighter's complex logistics software system faced risks that could lead to grounding the entire fleet due to a failure in the Autonomic Logistics Information System (ALIS), which is considered the "brains" of the fifth-generation fighter. The lack of a backup system and concerns about testing the software's functionality were highlighted as non-human factors contributing to the potential failure of the system [42632]. - The software update needed to fire the 25mm cannons hidden inside the F-35's wings was not ready until 2019, indicating a delay in software development that could impact the aircraft's combat capabilities [38304]. - The F-35 program faced significant performance problems related to software, data fusion, electronic warfare, and weapons employment, as noted by the Pentagon's top weapons tester. The concerns raised in the memo indicated that the program might not achieve full combat capability due to software limitations and other technical challenges [47492]. (b) The software failure incident occurring due to human actions: - The Government Accountability Office report highlighted concerns about the lack of testing done to ensure the F-35's software would work properly by the time the Air Force and Navy planned to declare their versions of the aircraft ready for deployment. The report also mentioned the Pentagon's tendency to respond to software problems on a case-by-case basis, potentially leading to further delays and cost increases [42632]. - The F-35 program faced criticism from the Pentagon's top weapons tester, who warned that the aircraft was at risk of failing to deliver its full combat capability. The concerns raised in the memo pointed to software, data fusion, electronic warfare, and weapons employment as areas where human actions could impact the program's success [47492].
Dimension (Hardware/Software) hardware, software (a) The software failure incident occurring due to hardware: - The F-35 Joint Strike Fighter's complex logistics software system faced issues that could lead to grounding the entire fleet due to problems with the Autonomic Logistics Information System (ALIS), which is considered the "brains" of the aircraft [42632]. - The F-35 program experienced limitations related to software, data fusion, electronic warfare, and weapons employment, despite achieving major development milestones, raising concerns about achieving full combat capability [47492]. (b) The software failure incident occurring due to software: - The F-35 Joint Strike Fighter faced challenges with its logistics software system, particularly with the ALIS software component, which could lead to grounding the entire fleet if not fully functional [42632]. - The F-35 program was warned by the Pentagon's top weapons tester about failing to deliver its full combat capability due to limitations related to software, data fusion, electronic warfare, and weapons employment [47492].
Objective (Malicious/Non-malicious) non-malicious The software failure incident related to the F-35 Joint Strike Fighter program is categorized as non-malicious. The issues with the F-35's logistics software system were not due to any malicious intent but rather stemmed from technical challenges and limitations in the software's performance and capabilities. The concerns raised by the Pentagon's top weapons tester, Michael Gilmore, highlighted various limitations related to software, data fusion, electronic warfare, and weapons employment, indicating non-malicious software failures [47492]. The software issues with the F-35's Autonomic Logistics Information System (ALIS) were identified as significant performance problems that needed to be corrected for the aircraft to achieve full combat capability. The concerns raised by the Director of Operational Test and Evaluation pointed towards the software's limitations and the risk of the program failing to deliver its full combat capability as intended [47492]. Additionally, the software glitches that interfered with the F-35's radar system were also non-malicious in nature, causing problems with the radar's stability and functionality during flight. The issues with the radar system were technical in nature and impacted the aircraft's combat readiness and operational effectiveness [42642].
Intent (Poor/Accidental Decisions) poor_decisions (a) The software failure incident related to the F-35 Joint Strike Fighter program can be attributed to poor decisions. The incident was highlighted in an article where the Pentagon's top weapons tester criticized the program, warning that the aircraft is "on a path of failing to deliver" its full combat capability [Article 47492]. The concerns raised by the Defense Department's director of operational testing pointed out limitations related to software, data fusion, electronic warfare, and weapons employment, indicating that the program may not achieve full combat capability before realistic combat testing begins. The issues mentioned in the memo suggest that poor decisions or factors introduced by such decisions have contributed to the software failure incident. Additionally, the software failure incident was further emphasized in another article, where problems with the F-35's logistics software system were highlighted [Article 42642]. The Autonomic Logistics Information System (ALIS), described as the "brains" of the plane, faced significant issues, including a lack of testing, potential schedule slippage, functionality problems, and the risk of additional costs. The report mentioned that the F-35 could not be operated as frequently as intended if ALIS is not fully functional, indicating poor decisions or factors introduced by such decisions in the development and implementation of the software system. These instances point towards poor decisions or contributing factors introduced by such decisions that have led to the software failure incident in the F-35 program.
Capability (Incompetence/Accidental) development_incompetence, accidental (a) The software failure incident related to development incompetence is evident in the F-35 Joint Strike Fighter program. The program faced significant issues with its logistics software system, known as the Autonomic Logistics Information System (ALIS). The Government Accountability Office report highlighted concerns about the lack of testing done to ensure the software would work properly by the time the Air Force and Navy planned to declare their versions of the aircraft ready for deployment [42632]. The Director of Operational Testing at the Department of Defense also warned that the F-35 program was at risk of failing to deliver its full combat capability due to limitations related to software, data fusion, electronic warfare, and weapons employment [47492]. (b) The software failure incident related to accidental factors is seen in the F-35 program as well. The F-35A fighter jet faced issues with its software update needed to fire the 25mm cannons hidden inside its wings. The software update required to enable firing the cannons in the air was not ready until 2019, leading to delays in the full combat capability of the aircraft [38304]. Additionally, the F-35 program experienced a glitch in the radar system that interfered with the aircraft's radar working in flight, posing a threat to delaying the USAF's plans to declare the jets operationally deployable [47492].
Duration permanent, temporary From the articles provided, the software failure incident related to the F-35 Joint Strike Fighter's logistics software system can be considered both permanent and temporary. 1. **Permanent Failure**: The software failure incident related to the F-35's logistics software system can be seen as a permanent failure due to contributing factors introduced by all circumstances. The Government Accountability Office (GAO) report highlighted concerns about the lack of testing done to ensure the software will work properly, potential schedule delays, and functionality problems with the Autonomic Logistics Information System (ALIS) that could lead to significant additional costs ([42632], [42642]). 2. **Temporary Failure**: On the other hand, the software failure incident can also be viewed as a temporary failure due to contributing factors introduced by certain circumstances but not all. The F-35 program officials and Lockheed Martin expressed confidence in resolving the current issues and future discoveries related to the software. They are actively working on addressing the concerns raised by the GAO and are committed to developing a plan to improve the reliability of cost estimates and the overall functionality of the ALIS ([42632], [42642]). In summary, while the software failure incident has raised significant concerns and risks, efforts are being made to address the issues and ensure the F-35 program reaches its full combat capability.
Behaviour crash, omission, value, other (a) crash: The software failure incident related to the F-35 Joint Strike Fighter's complex logistics software system could lead to a grounding of the entire fleet, as a failure in the Autonomic Logistics Information System (ALIS) could potentially take the entire fleet offline due to the lack of a backup system [42632, 42642]. (b) omission: The software issues with the F-35's logistics software system have led to maintenance crews resorting to labor-intensive alternatives, such as manually burning data onto CDs and sending files across a civilian WiFi network [42642]. (c) timing: The software failure incident is related to timing issues as the lack of testing done on the software may result in it not being ready for deployment by the Air Force in August and the Navy in 2018, potentially causing delays in achieving full combat capability [42632, 47492]. (d) value: The software failure incident could lead to a failure in the system's value as it may not be fully functional, impacting the operational frequency of the F-35 as intended, potentially resulting in additional costs [42632]. (e) byzantine: The software failure incident does not exhibit characteristics of a byzantine failure as described in the articles. (f) other: The software failure incident also highlights concerns about the F-35's software glitches, limitations related to software, data fusion, electronic warfare, and weapons employment, as well as the program's potential lack of resources to correct these problems [47492].

IoT System Layer

Layer Option Rationale
Perception sensor, embedded_software (a) The failure was related to the perception layer of the cyber physical system that failed due to contributing factors introduced by sensor error. The Autonomic Logistics Information System (ALIS) of the F-35 Joint Strike Fighter, described as the "brains" of the aircraft, faced issues with its software system. The lack of testing done to ensure the software will work properly was a concern, and the failure of the ALIS could potentially take the entire fleet offline due to the lack of a backup system [42632]. (b) No information was provided in the articles about the failure being related to the actuator layer of the cyber physical system. (c) No information was provided in the articles about the failure being related to the processing unit layer of the cyber physical system. (d) No information was provided in the articles about the failure being related to the network communication layer of the cyber physical system. (e) The failure was related to the perception layer of the cyber physical system that failed due to contributing factors introduced by embedded software error. The F-35 Joint Strike Fighter program faced issues with its software system, particularly the Autonomic Logistics Information System (ALIS), which is considered one of the three major components of the aircraft. The software runs on ground computers to support operations, mission planning, maintenance, and sustainability. Concerns were raised about the lack of testing done to ensure the software will work properly, and the failure of the ALIS could potentially ground the entire fleet [42632].
Communication unknown The software failure incident related to the F-35 Joint Strike Fighter program was not specifically mentioned to be related to the communication layer of the cyber physical system that failed at the link_level or connectivity_level in the provided articles [42632, 38304, 42642, 47492]. The focus of the articles was on concerns regarding the F-35's complex logistics software system, Autonomic Logistics Information System (ALIS), which is considered the "brains" of the aircraft. The issues highlighted included problems with software, data fusion, electronic warfare, and weapons employment, as well as limitations related to software, data fusion, electronic warfare, and weapons employment. The failure analysis did not delve into specific technical layers of the cyber physical system related to communication failures.
Application FALSE The software failure incidents related to the F-35 Joint Strike Fighter program were not explicitly mentioned as being related to the application layer of the cyber physical system. The articles primarily focused on issues with the logistics software system, data fusion, electronic warfare, and weapons employment capabilities of the F-35 aircraft. Therefore, it is unknown whether the failure was specifically related to the application layer as defined. [42632, 38304, 47492]

Other Details

Category Option Rationale
Consequence property, delay, non-human, theoretical_consequence, other (a) death: People lost their lives due to the software failure - There is no mention of any deaths resulting from the software failure incident in the provided articles. (b) harm: People were physically harmed due to the software failure - There is no mention of people being physically harmed due to the software failure incident in the provided articles. (c) basic: People's access to food or shelter was impacted because of the software failure - There is no mention of people's access to food or shelter being impacted due to the software failure incident in the provided articles. (d) property: People's material goods, money, or data was impacted due to the software failure - The software failure incident related to the F-35 Joint Strike Fighter program could lead to significant issues with the warplane and risks of not reaching full combat capability, potentially affecting the investment in the program [47492]. (e) delay: People had to postpone an activity due to the software failure - The software failure incident with the F-35 program has caused delays in achieving full combat capability and meeting operational testing timelines [47492]. (f) non-human: Non-human entities were impacted due to the software failure - The software failure incident primarily impacted the F-35 Joint Strike Fighter program, which is a military aircraft system [47492]. (g) no_consequence: There were no real observed consequences of the software failure - The software failure incident with the F-35 program has led to concerns about the aircraft's combat capability and potential delays in achieving full functionality [47492]. (h) theoretical_consequence: There were potential consequences discussed of the software failure that did not occur - The articles discuss potential consequences of the software failure incident, such as the risk of the F-35 not achieving full combat capability and facing delays in operational testing [47492]. (i) other: Was there consequence(s) of the software failure not described in the (a to h) options? What is the other consequence(s)? - The software failure incident with the F-35 program raised concerns about the aircraft's performance limitations related to software, data fusion, electronic warfare, and weapons employment, potentially impacting its combat effectiveness [47492].
Domain information, government (a) The failed system was intended to support the production and distribution of information. The software system in question is the Autonomic Logistics Information System (ALIS) for the F-35 Joint Strike Fighter, described as the "brains" of the fifth-generation fighter. The ALIS is designed to support operations, mission planning, maintenance, and sustainability of the aircraft [42632, 42642]. (b) The failed system was not related to the transportation industry. (c) The failed system was not related to the extraction of natural resources. (d) The failed system was not related to the sales industry. (e) The failed system was not related to the construction industry. (f) The failed system was not related to the manufacturing industry. (g) The failed system was not related to the utilities industry. (h) The failed system was not related to the finance industry. (i) The failed system was not related to the knowledge industry. (j) The failed system was not related to the health industry. (k) The failed system was not related to the entertainment industry. (l) The failed system was not related to the government industry. (m) The failed system was specifically related to the defense industry, as it was crucial for the operations, maintenance, and sustainability of the F-35 Joint Strike Fighter, a military aircraft program [42632, 47492].

Sources

Back to List