| Recurring |
one_organization |
(a) The software failure incident related to Jawbone's UP activity-monitoring wristbands has happened again within the same organization. The article mentions that numerous complaints of "bricked" units riddle Jawbone's user forums, with 41 different user reviews complaining of 23 bricked devices. Jawbone CEO Hosain Rahman issued a statement explaining that problems with circuit board capacitors are to blame for the failures, affecting the ability to hold a charge, exhibit erratic data-recording behavior, or stop working. Rahman also mentioned that Jawbone has temporarily paused production of the bands to resolve the technical issues before resuming orders [54439]. |
| Phase (Design/Operation) |
design |
(a) The software failure incident with Jawbone's UP activity-monitoring wristbands was attributed to problems with circuit board capacitors affecting the ability to hold a charge, exhibit erratic data-recording behavior, or stop working. Jawbone CEO Hosain Rahman mentioned, "We’ve found an issue with two specific capacitors in the power system that affects the ability to hold a charge in some of our bands" [54439].
(b) The article did not provide specific information about the software failure incident related to operation or misuse of the system. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident with Jawbone's UP activity-monitoring wristbands was primarily within the system. The CEO of Jawbone, Hosain Rahman, explained that the failures were caused by issues with circuit board capacitors affecting the ability to hold a charge, erratic data-recording behavior, and syncing problems [54439]. Additionally, the VP of Product Management and Strategy at Jawbone mentioned that they had temporarily paused production to resolve the hardware's technical issues before resuming orders [54439]. |
| Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident in the article was primarily due to non-human actions, specifically problems with circuit board capacitors affecting the ability to hold a charge, erratic data-recording behavior, and syncing issues. Jawbone CEO Hosain Rahman mentioned that the glitches were purely performance-related and did not pose any safety risk [54439].
(b) Human actions were also involved in addressing the software failure incident. Jawbone CEO Hosain Rahman issued a statement explaining the cause of the failures and offered a comprehensive refund program for unhappy customers. Additionally, Jawbone VP Travis Bogard mentioned that they had temporarily paused production of the bands to resolve the technical issues before resuming orders [54439]. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident with Jawbone's UP activity-monitoring wristbands was primarily attributed to hardware issues. Jawbone CEO Hosain Rahman mentioned that the failures were caused by problems with circuit board capacitors affecting the ability to hold a charge, exhibit erratic data-recording behavior, or stop working. Rahman specifically stated, "We’ve found an issue with two specific capacitors in the power system that affects the ability to hold a charge in some of our bands" [54439].
(b) The software failure incident also had software-related issues, as mentioned by Rahman. He stated that they were fixing an issue with syncing related to the band hardware. Additionally, the article highlighted problems such as bands exhibiting syncing failures before bricking for good, indicating software-related issues alongside the hardware problems [54439]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident related to the Jawbone UP activity-monitoring wristbands was non-malicious. The failure was attributed to problems with circuit board capacitors affecting the ability to hold a charge, erratic data-recording behavior, and syncing issues. Jawbone CEO Hosain Rahman explained that the glitches were purely performance-related and did not pose any safety risk [54439]. |
| Intent (Poor/Accidental Decisions) |
unknown |
The software failure incident related to the Jawbone UP activity-monitoring wristbands was not primarily caused by poor decisions or accidental decisions. Instead, the failure was attributed to technical issues with specific capacitors in the power system affecting the ability to hold a charge, as well as problems with syncing related to the band hardware [54439]. The CEO of Jawbone, Hosain Rahman, acknowledged these issues and offered a comprehensive refund program for affected customers. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident related to development incompetence is not explicitly mentioned in the provided article. Therefore, it is unknown whether the failure was due to contributing factors introduced due to lack of professional competence by humans or the development organization.
(b) The software failure incident related to accidental factors is evident in the article. The failure of Jawbone's UP activity-monitoring wristbands was attributed to problems with circuit board capacitors, which affected the ability to hold a charge, exhibit erratic data-recording behavior, or stop working. Jawbone CEO Hosain Rahman mentioned that the glitches were purely performance-related and did not pose any safety risk, indicating that the failure was accidental rather than intentional [54439]. |
| Duration |
permanent |
(a) The software failure incident related to Jawbone's UP activity-monitoring wristbands was more of a permanent nature. The failure was attributed to problems with circuit board capacitors affecting the ability to hold a charge, exhibit erratic data-recording behavior, or stop working. Jawbone CEO Hosain Rahman mentioned that these issues typically surface within the first seven to ten days of use and are purely performance-related, not posing any safety risk. As a result of these hardware technical issues, Jawbone temporarily paused production of the bands and offered a comprehensive refund program for unsatisfied customers [54439]. |
| Behaviour |
value, other |
(a) crash: The software failure incident in the article is not described as a crash where the system loses state and does not perform any of its intended functions [54439].
(b) omission: The software failure incident does not involve the system omitting to perform its intended functions at an instance(s) [54439].
(c) timing: The software failure incident is not related to the system performing its intended functions correctly but too late or too early [54439].
(d) value: The software failure incident is related to the system performing its intended functions incorrectly. Specifically, the Jawbone UP activity-monitoring wristbands were failing due to problems with circuit board capacitors affecting the ability to hold a charge, exhibit erratic data-recording behavior, or stop working [54439].
(e) byzantine: The software failure incident is not described as the system behaving erroneously with inconsistent responses and interactions [54439].
(f) other: The behavior of the software failure incident in the article is related to performance issues such as syncing failures, random vibrations, dropping data, and bands bricking for good due to hardware issues with capacitors in the power system [54439]. |