| Recurring |
unknown |
(a) The software failure incident at Ocado involving a robot malfunction causing a fire in a warehouse is specific to that organization. There is no mention in the article of a similar incident happening before at Ocado or with its products and services [116727].
(b) There is no information in the article suggesting that a similar incident has happened before at other organizations or with their products and services. The focus of the article is on the specific incident at Ocado's warehouse caused by a robot malfunction [116727]. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident at Ocado's warehouse was caused by a robot malfunction resulting in a fire. The company mentioned that the fire was caused by the collision of three robots on the grid, indicating a failure related to the design or development of the robotic system [116727].
(b) The operation of the system was also a contributing factor to the incident. The article mentioned that the fire was caused by a robot malfunction during operations in the warehouse. This indicates that the operation or use of the robotic system played a role in the failure [116727]. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident at Ocado's warehouse was within the system. The fire was caused by a robot malfunction, specifically the collision of three robots on the grid within the warehouse [116727]. The damage was limited to a small section of less than 1% of the grid, indicating that the failure was contained within the system itself. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident at Ocado's warehouse was caused by a robot malfunction, specifically the collision of three robots on the grid, leading to a fire [116727].
(b) Human actions were not mentioned as contributing factors to the software failure incident at Ocado's warehouse. |
| Dimension (Hardware/Software) |
hardware |
(a) The software failure incident at Ocado's warehouse was caused by a robot malfunction, specifically the collision of three robots on the grid. This indicates a hardware-related failure as the contributing factors originated in the hardware components (robots) [116727].
(b) The software failure incident did not specifically mention any contributing factors originating in the software itself. The focus was on a robot malfunction leading to a fire in the warehouse, indicating a hardware-related issue rather than a software-related one [116727]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident at Ocado's warehouse, which resulted in a fire, was non-malicious. The incident was caused by a robot malfunction where three robots collided on the grid, leading to the fire. There is no indication in the article that the malfunction was intentional or caused by malicious actors. The company mentioned that the damage was limited to a small section of the grid, and all workers were safe [116727]. |
| Intent (Poor/Accidental Decisions) |
unknown |
The software failure incident at Ocado's warehouse, where a fire was caused by a robot malfunction, does not directly point to poor_decisions or accidental_decisions as the intent behind the failure. The incident seems to be more related to a technical malfunction in the robots rather than being a result of specific poor or accidental decisions. Therefore, the articles do not provide clear evidence to support either of the options. |
| Capability (Incompetence/Accidental) |
development_incompetence, accidental |
(a) The software failure incident at Ocado's warehouse was caused by a robot malfunction, specifically the collision of three robots on the grid. This indicates a failure due to contributing factors introduced by the development organization, possibly related to the programming or control systems of the robots [116727].
(b) The incident was described as a fire caused by a robot malfunction, suggesting an accidental failure rather than a deliberate act. The collision of the robots was likely an unintended event that led to the fire and subsequent disruption in operations [116727]. |
| Duration |
temporary |
The software failure incident at Ocado's warehouse, caused by a robot malfunction leading to a fire, resulted in temporary disruption to operations. The company stated that they expected "some disruption to operations" but were working to restore normal service as soon as possible [116727]. Additionally, the company mentioned that the damage was limited to a small section of less than 1% of the grid, indicating that the impact was contained and not permanent. |
| Behaviour |
crash, other |
(a) crash: The software failure incident in the Ocado warehouse was caused by a fire resulting from a robot malfunction, specifically the collision of three robots on the grid. This led to a disruption in operations, with the facility expected to begin operating within the coming week [116727].
(b) omission: There is no specific mention of the software failure incident being related to the system omitting to perform its intended functions at an instance(s) in the provided article.
(c) timing: The software failure incident did not involve the system performing its intended functions too late or too early; rather, it led to a disruption in operations due to the fire caused by the robot malfunction [116727].
(d) value: The software failure incident did not involve the system performing its intended functions incorrectly; instead, it resulted in a disruption in operations at the warehouse [116727].
(e) byzantine: The software failure incident did not exhibit the system behaving erroneously with inconsistent responses and interactions; it was primarily related to a fire caused by a robot malfunction in the warehouse [116727].
(f) other: The other behavior exhibited by the software failure incident was the limited damage caused by the fire, which was contained to a small section of less than 1% of the grid due to planned fire attenuation measures [116727]. |