| Recurring |
one_organization |
(a) The software failure incident having happened again at one_organization:
The article mentions that this is not the first time a glitch has affected operations at the Indira Gandhi International Airport's Terminal 3. In the past, there have been incidents such as ATC operations being hit by radar failure and issues with the terminal's infrastructure like leaking roofs and water-logging in the basement and arrival terminal [17910]. These incidents indicate a history of technical problems at the airport, suggesting a recurring issue within the same organization.
(b) The software failure incident having happened again at multiple_organization:
There is no specific mention in the article about similar software failure incidents occurring at other organizations or airports. Therefore, it is unknown if this particular type of glitch has affected multiple organizations. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident at Indira Gandhi International Airport's Terminal 3 was related to the design phase. The article mentions that the computerized check-in and baggage handling system developed a snag due to a glitch in the Common User Terminal Equipment (CUTE) software, which is maintained by the airport operator - Delhi International Airport Limited (DIAL) [17910].
(b) The software failure incident at the airport was also related to the operation phase. The article describes how the employees of various airlines had to switch to manual mode for check-in when the boarding gates and baggage belts were not functioning properly, causing delays and long queues. This indicates that the failure was exacerbated by the operation or misuse of the system [17910]. |
| Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident at Indira Gandhi International Airport's Terminal 3 was primarily within the system. The article mentions that the Common User Terminal Equipment (CUTE) software, which is maintained by the airport operator, developed a snag, leading to the disruption in operations. The article specifically states, "The problem started at around 8.20 am when the CUTE software...developed a snag" [17910]. Additionally, the article highlights that the visual ground display system, another component of the airport's software infrastructure, was also not operational during the incident, further indicating internal system issues. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident at Indira Gandhi International Airport's Terminal 3 was primarily due to non-human actions. The article mentions that a technical glitch occurred in the Common User Terminal Equipment (CUTE) software, which is maintained by the airport operator, Delhi International Airport Limited (DIAL) [17910]. This glitch led to the disruption of operations, causing delays in check-in processes and baggage handling. The malfunction in the CUTE system resulted in the need for manual intervention by airline employees, leading to long queues and inconvenience for passengers. The restoration of the system was eventually achieved after the technical issue was addressed.
(b) While the software failure incident was primarily attributed to non-human actions, there is no specific mention in the article of any contributing factors introduced by human actions that may have exacerbated the situation or directly caused the glitch. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident at Indira Gandhi International Airport's Terminal 3 was primarily due to a hardware-related issue. The article mentions that the Common User Terminal Equipment (CUTE) software, which is maintained by the airport operator, developed a snag, leading to the disruption in operations [17910].
(b) The software failure incident was also related to software issues as the CUTE software, which is a critical component for reservation and passenger check-in, malfunctioned, causing delays and inconvenience to passengers. The software glitch affected the computerized check-in and baggage handling system, leading to manual operations and long queues [17910]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident at Indira Gandhi International Airport's Terminal 3 was non-malicious. The incident was attributed to a technical glitch in the Common User Terminal Equipment (CUTE) software, which is maintained by the airport operator. The glitch affected the computerized check-in and baggage handling system, leading to operational disruptions for more than an hour. The article does not suggest any malicious intent behind the failure, indicating that it was a technical issue rather than a deliberate act to harm the system [17910]. |
| Intent (Poor/Accidental Decisions) |
accidental_decisions |
(a) The software failure incident at Indira Gandhi International Airport's Terminal 3 was not explicitly attributed to poor decisions. The incident was primarily described as a technical glitch in the Common User Terminal Equipment (CUTE) software, which led to disruptions in the check-in and baggage handling systems, causing delays for multiple flights and inconveniencing passengers [17910].
(b) The software failure incident at the airport was characterized by an accidental technical glitch rather than intentional poor decisions. The malfunction in the CUTE software was described as unexpected and resulted in the need for manual check-in processes and delays in operations, indicating that the failure was accidental rather than a result of deliberate decisions [17910]. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident at Indira Gandhi International Airport's Terminal 3 was not explicitly attributed to development incompetence. The article primarily highlights a technical glitch in the Common User Terminal Equipment (CUTE) software, which is maintained by the airport operator, Delhi International Airport Limited (DIAL) [17910].
(b) The software failure incident at Terminal 3 of the airport was described as a computer glitch that affected the check-in and baggage handling system, leading to operational disruptions for over an hour. The glitch was reported to have caused delays for more than 20 domestic and international flights, inconveniencing hundreds of passengers. The incident was characterized by the system not functioning properly, resulting in manual operations and long queues, indicating an accidental failure rather than intentional [17910]. |
| Duration |
temporary |
The software failure incident at Indira Gandhi International Airport's Terminal 3 was temporary. The glitch in the Common User Terminal Equipment (CUTE) software caused operations to be crippled for more than an hour, delaying the departure of more than 20 flights and inconveniencing hundreds of passengers. The system was finally restored at around 9.40 am, indicating that the failure was temporary [17910]. |
| Behaviour |
crash, omission, other |
(a) crash: The software failure incident at Indira Gandhi International Airport's Terminal 3 was characterized by a crash as the computerized check-in and baggage handling system developed a snag, leading to operations being crippled for more than an hour and causing delays for more than 20 flights [17910].
(b) omission: The software failure incident also involved omission as the Common User Terminal Equipment (CUTE) software, which helps streamline the reservation system and facilitates passenger check-in, developed a snag, leading to boarding gates and baggage belts not functioning properly and employees having to switch to manual mode for check-in, causing delays and long queues [17910].
(c) timing: The timing of the software failure incident was crucial as it occurred at around 8.20 am, disrupting operations and causing inconvenience to passengers for more than an hour before being fully restored at 9.40 am [17910].
(d) value: The software failure incident did not specifically involve a failure due to the system performing its intended functions incorrectly (value).
(e) byzantine: The software failure incident did not exhibit behavior indicative of a byzantine failure where the system behaves erroneously with inconsistent responses and interactions.
(f) other: The software failure incident at the airport exhibited behavior that could be categorized as a system failure due to external factors such as technical glitches impacting the smooth functioning of critical systems like check-in and baggage handling, leading to manual operations and delays [17910]. |