| Recurring |
one_organization |
(a) The software failure incident at one_organization:
The article mentions that the James Webb Space Telescope, a joint project from NASA, the European Space Agency, and the Canadian Space Agency, experienced a software fault in its attitude control system, causing it to go into safe mode. This incident highlights a software failure within the same organization (NASA) that is responsible for the telescope's operations [136729].
(b) The software failure incident at multiple_organization:
The article does not provide information about similar incidents happening at other organizations or with their products and services. Therefore, it is unknown if this specific software failure incident has occurred at multiple organizations. |
| Phase (Design/Operation) |
design |
(a) The software failure incident with the James Webb Space Telescope was attributed to a software fault triggered in the attitude control system, which controls the pointing of the observatory. This fault occurred during the operation of the telescope, leading to the system going into safe mode for troubleshooting [136729].
(b) The article does not provide specific information indicating that the software failure incident was due to factors introduced by the operation or misuse of the system. Therefore, it is unknown if the failure was related to operation factors based on the provided article. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident with the James Webb Space Telescope was within the system. NASA mentioned that the issue was "due to a software fault triggered in the attitude control system" [136729]. The fault in the attitude control system, which is an integral part of the telescope's software, caused the telescope to go into safe mode and required adjustments by the telescope team to resolve the issue. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in the James Webb Space Telescope was due to a non-human action, specifically a software fault triggered in the attitude control system, which controls the pointing of the observatory. This fault caused the telescope to go into safe mode to protect itself while the team troubleshooted the issue [136729]. NASA mentioned that the observatory and instruments were in good health and not in any danger during the incident, indicating that the onboard fault management system worked as expected to keep the hardware safe.
(b) The articles do not mention any contributing factors introduced by human actions that led to the software failure incident. |
| Dimension (Hardware/Software) |
hardware |
(a) The software failure incident in the James Webb Space Telescope was due to a software fault triggered in the attitude control system, which controls the pointing of the observatory. This indicates that the failure originated in the hardware system of the telescope [136729].
(b) The software failure incident was specifically mentioned to be caused by a software fault triggered in the attitude control system, indicating that the contributing factor for the failure originated in the software of the telescope [136729]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident related to the James Webb Space Telescope was non-malicious. NASA stated that the issue was "due to a software fault triggered in the attitude control system" [136729]. The fault caused the telescope to go into safe mode to protect itself while the team troubleshooted the problem. NASA also mentioned that the observatory and instruments were in good health and not in any danger during the incident, indicating that the failure was not caused by malicious intent. |
| Intent (Poor/Accidental Decisions) |
unknown |
The software failure incident related to the James Webb Space Telescope experiencing technical hiccups was not due to poor decisions or accidental decisions. The incident was specifically attributed to a software fault triggered in the attitude control system, which controls the pointing of the observatory [136729]. NASA mentioned that the fault management system worked as expected to keep the hardware safe during the glitch, indicating that the incident was not caused by poor or accidental decisions. |
| Capability (Incompetence/Accidental) |
development_incompetence |
(a) The software failure incident with the James Webb Space Telescope was attributed to a "software fault triggered in the attitude control system" [136729]. This indicates a failure due to development incompetence, as the fault was likely introduced during the software development process.
(b) The article does not provide information indicating that the software failure incident was accidental. |
| Duration |
temporary |
(a) The software failure incident related to the James Webb Space Telescope was temporary. The incident lasted for nearly two weeks, starting on December 7 and being resolved by December 20. During this time, the telescope experienced pauses in science operations totaling a few days, indicating a temporary disruption caused by the software fault triggered in the attitude control system [136729]. |
| Behaviour |
omission, value |
(a) crash: The software fault triggered in the attitude control system of the James Webb Space Telescope caused the telescope to go into safe mode, shutting down nonessential systems while the team troubleshoots [136729].
(b) omission: The glitch in the software didn't completely stop JWST's work but resulted in several pauses to science operations totaling a few days [136729].
(c) timing: The software fault caused interruptions to the science operations of the telescope over a period of a few days [136729].
(d) value: The software fault triggered in the attitude control system caused the system to perform its functions incorrectly, leading to the need for adjustments in the commanding system [136729].
(e) byzantine: There is no indication in the article of the software failure incident exhibiting inconsistent responses or interactions.
(f) other: The software fault triggered in the attitude control system of the James Webb Space Telescope is not described as exhibiting any other specific behavior beyond causing interruptions and requiring adjustments in the commanding system. |