| Recurring |
multiple_organization |
(a) The software failure incident related to the glitch in the Ninebot KickScooter model has not been reported to have happened again within the same organization (Segway) or with its products and services. The article mentions that the glitch did not occur on Ninebot KickScooters from Spin (owned by Ford) and Jump (owned by Uber) [86186].
(b) The software failure incident related to the glitch in the Ninebot KickScooter model has been reported to have happened with products from multiple organizations. The article mentions that several scooters from Bird, Lyft, and Skip in Washington, DC, achieved speeds exceeding the local limits due to the glitch. Skip and Lyft are actively investigating the issue, indicating that it is not limited to just one organization [86186]. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident in this case seems to be related to the design phase. The glitch causing the e-scooters to exceed local speed limits was reportedly due to a design flaw in the Ninebot KickScooter model manufactured by Segway. This glitch could be activated by specific steps involving the rear brake and the throttle, indicating a design issue in the system development of the scooter model [86186].
(b) Additionally, there are mentions of operation-related factors contributing to the failure incident. The article highlights that riders have faced accidents and injuries due to issues such as brakes not working or speeding into oncoming traffic, which could be attributed to the operation or misuse of the e-scooters by users [86186]. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident related to the glitch in the e-scooter model exceeding local speed limits can be categorized as within_system. The glitch was specifically related to the Ninebot KickScooter model manufactured by Segway, affecting scooters rented by companies like Lyft, Bird, and Skip [86186]. The issue was not observed in Ninebot KickScooters from Spin and Jump, indicating that the problem was internal to the specific model rather than a widespread external factor. The glitch could be activated by specific actions involving the rear brake and throttle, indicating an internal software issue within the scooter's system. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in this case appears to be related to non-human actions, specifically a glitch in the e-scooter model manufactured by Segway. The glitch caused the scooters to exceed local speed limits, reaching up to 21 miles per hour instead of the allowed 15 miles per hour. This glitch was activated by a specific sequence involving the rear brake and throttle, indicating a technical issue rather than a human error [86186]. |
| Dimension (Hardware/Software) |
hardware |
(a) The software failure incident in this case is related to hardware. The glitch causing the e-scooters to exceed local speed limits is reportedly due to a hardware issue in the Ninebot KickScooter model used by companies like Lyft and Bird [86186]. The glitch involves manipulating the rear brake and throttle, indicating a hardware-related problem within the scooter model itself. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident in this case appears to be non-malicious. The glitch in the e-scooter model, specifically the Ninebot KickScooter, causing it to exceed local speed limits was not intentional but rather a technical issue. The glitch was reportedly activated by a specific sequence involving the rear brake and throttle, leading to the scooters going faster than the allowed speed limits. Companies like Lyft and Bird are investigating the issue to ensure the safety of their customers [86186]. |
| Intent (Poor/Accidental Decisions) |
poor_decisions |
(a) The software failure incident related to the e-scooter glitch causing it to exceed local speed limits can be attributed to poor decisions made during the design or implementation of the software. This glitch was reportedly activated by taking specific steps with the rear brake and throttle, indicating a design flaw that allowed users to bypass the speed restrictions [86186]. Additionally, the fact that the glitch did not occur on Ninebot KickScooters from other companies like Spin and Jump suggests that there were specific design choices or implementations in the affected scooters that led to this issue. |
| Capability (Incompetence/Accidental) |
development_incompetence |
(a) The software failure incident in the article seems to be more related to development incompetence rather than accidental factors. The glitch in the e-scooter model, causing it to exceed local speed limits, was reportedly due to a specific sequence of steps involving the rear brake and throttle. This indicates a specific flaw or oversight in the software development of the scooter model by the manufacturer, Segway. Additionally, the fact that the glitch did not occur in Ninebot KickScooters from other companies like Spin and Jump suggests a specific issue with the software implementation by Segway [86186]. |
| Duration |
temporary |
(a) The software failure incident in this case seems to be temporary. The glitch in the e-scooter model manufactured by Segway was causing it to exceed local speed limits, but it was not a permanent issue affecting all scooters. The glitch reportedly didn't happen on Ninebot KickScooters from Spin and Jump, indicating that it was not a fleet-wide problem [86186]. |
| Behaviour |
value, other |
(a) crash: The software failure incident in the article does not involve a crash where the system loses state and does not perform any of its intended functions [86186].
(b) omission: The software failure incident does not involve omission where the system omits to perform its intended functions at an instance(s) [86186].
(c) timing: The software failure incident does not involve timing issues where the system performs its intended functions correctly, but too late or too early [86186].
(d) value: The software failure incident involves a value issue where the system performs its intended functions incorrectly. In this case, the glitch in the e-scooter model causes it to exceed local speed limits, going up to 21 miles per hour instead of the allowed 15 miles per hour [86186].
(e) byzantine: The software failure incident does not involve a byzantine behavior where the system behaves erroneously with inconsistent responses and interactions [86186].
(f) other: The other behavior observed in this software failure incident is related to a glitch in the e-scooter model that allows users to activate the speed exceeding feature by manipulating the rear brake and throttle, which is not the intended behavior of the scooter [86186]. |