| Recurring |
unknown |
The article does not provide information about the software failure incident happening again at either the same organization (NASA) or at other organizations. Therefore, the information about the recurrence of the software failure incident is unknown. |
| Phase (Design/Operation) |
design |
(a) The software failure incident in Article 135500 was related to the design phase. The incident was described as a communications glitch between the Orion spacecraft and the Deep Space Network during the Artemis I mission. NASA mentioned that the loss of data communication occurred while reconfiguring the communication link between Orion and the Deep Space Network, indicating a potential issue introduced during the system development or update process.
Additionally, NASA stated that the team was investigating the cause of the loss of signal, suggesting that the incident was likely due to contributing factors introduced during the design or development phases of the system [135500]. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident described in the article is within_system. The incident was a communications glitch between the Orion spacecraft and the Deep Space Network, which are both components of the system designed and operated by NASA [135500]. The glitch occurred during the reconfiguration of the communication link between Orion and the Deep Space Network, indicating an internal system issue that led to the loss of data transmission for 47 minutes. NASA was able to regain communication with Orion after making adjustments on Earth, highlighting that the failure was within the system and could be addressed internally. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in this case was due to non-human actions. The incident was specifically described as a communications glitch between the Orion spacecraft and the Deep Space Network, which resulted in a loss of data transmission for 47 minutes. This glitch occurred while reconfiguring the communication link between Orion and the network overnight, indicating a technical issue rather than a human error [135500]. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident in Article 135500 was not directly attributed to hardware issues. The incident was described as a communications glitch between the Orion spacecraft and the Deep Space Network, which is a network of antennas used for data transmission between space missions and Earth. The glitch occurred while reconfiguring the communication link between Orion and the network, leading to a loss of data transmission for 47 minutes [135500].
(b) The software failure incident in Article 135500 was related to a communications glitch between the Orion spacecraft and the Deep Space Network. The glitch was described as a loss of data to and from the spacecraft while reconfiguring the communication link between Orion and the network. NASA mentioned that the team was investigating the cause of the loss of signal, indicating that the software aspect of the communication link was being examined for potential issues [135500]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident described in Article 135500 was non-malicious. The incident was specifically referred to as a "communications glitch" that occurred during the Artemis I mission involving NASA's Orion capsule. The glitch led to a loss of data communication between the spacecraft and Earth for 47 minutes while reconfiguring the communication link between Orion and the Deep Space Network. NASA mentioned that the team was investigating the cause of the loss of signal, indicating that the failure was not intentional but rather a technical issue that needed to be addressed [135500]. |
| Intent (Poor/Accidental Decisions) |
unknown |
The intent of the software failure incident in Article 135500 was not related to poor decisions or accidental decisions. The incident was described as a communications glitch encountered by NASA's Orion spacecraft during its Artemis I mission test flight. NASA attributed the glitch to a loss of data to and from the spacecraft while reconfiguring the communication link between Orion and the Deep Space Network. The agency mentioned that the spacecraft is healthy, and the team is investigating the cause of the signal loss. The incident was framed as a part of the testing process to work out kinks before crewed missions, emphasizing the importance of testing in space exploration [135500]. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident in Article 135500 was not explicitly attributed to development incompetence. The incident was described as a communications glitch between the Orion spacecraft and the Deep Space Network during a test flight by NASA. The focus was on the technical aspect of the glitch and the need for testing to uncover and address such issues.
(b) The software failure incident in Article 135500 was categorized more as an accidental failure. The glitch in communication between the Orion spacecraft and the Deep Space Network was not portrayed as a result of development incompetence but rather as an unexpected issue that occurred during the test flight. NASA mentioned that the team was investigating the cause of the loss of signal, indicating that it was an accidental occurrence that needed further examination. |
| Duration |
temporary |
The software failure incident described in Article 135500 was temporary. The incident involved a communications glitch between the Orion spacecraft and the Deep Space Network, resulting in a loss of data transmission for 47 minutes. NASA was able to regain communications with Orion after making adjustments back on Earth, indicating that the failure was not permanent but rather a temporary glitch that was resolved [135500]. |
| Behaviour |
crash, other |
(a) crash: The software failure incident in the article can be categorized as a crash. The Orion spacecraft encountered a communications glitch, leading to a loss of data to and from the spacecraft for 47 minutes while reconfiguring the communication link between Orion and the Deep Space Network [135500].
(b) omission: There is no indication in the article that the software failure incident was due to the system omitting to perform its intended functions at an instance(s).
(c) timing: The software failure incident was not related to the system performing its intended functions correctly but too late or too early.
(d) value: The software failure incident was not due to the system performing its intended functions incorrectly.
(e) byzantine: The software failure incident was not characterized by the system behaving erroneously with inconsistent responses and interactions.
(f) other: The behavior of the software failure incident can be described as a glitch in communication that led to a temporary loss of data exchange between the Orion spacecraft and the Deep Space Network during a critical phase of the mission [135500]. |