| Recurring |
one_organization, multiple_organization |
(a) The software failure incident related to the What3Words (W3W) addressing system has happened again within the same organization. The incident involved errors in pinpointing locations due to similar-sounding words and plurals being close to each other, potentially leading emergency services to the wrong location. An example cited in the article is how a couple waiting with an injured walker provided a W3W grid reference to emergency services, but the rescue team was initially sent "many miles" away from their actual location [113504].
(b) The software failure incident related to the What3Words (W3W) addressing system has also happened at multiple organizations or with their products and services. The article mentions that a security consultant found thousands of locations with similar words less than 1km apart, raising concerns about the accuracy of the system used by 100 UK emergency services. Additionally, a recent report from UK-based Keswick Mountain Rescue highlighted errors that occurred when using W3W grid references, leading to confusion in locating individuals in need of assistance [113504]. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident related to the design phase is evident in the What3Words (W3W) addressing system. The system's algorithm for assigning three-word addresses to locations led to the presence of numerous similar-sounding words, homophones, and plurals in close proximity to each other. This design flaw raised concerns about the potential for emergency services personnel to be directed to incorrect locations, which could have life-threatening consequences [113504].
(b) The software failure incident related to the operation phase is highlighted in a report from Keswick Mountain Rescue, where errors occurred when a couple provided a W3W grid reference to emergency services. The rescue team was initially sent many miles away from the actual location of the injured walker due to an incorrect W3W reference. This operational error resulted in a delay in reaching the correct location, emphasizing the importance of accurate operation and communication when using location-based systems like W3W [113504]. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident related to the What3Words (W3W) addressing system can be categorized as within_system. The issue with the system's algorithm sorting similar words, homophones, and plurals in close proximity led to potential errors in pinpointing locations accurately. The design feature of shuffling word combinations within the system contributed to the occurrence of similar sounding three-word combinations being nearby, increasing the risk of mistakes in critical situations [113504]. The system's design choices and intentional features played a role in the failure incident. |
| Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident occurring due to non-human actions:
The software failure incident related to the What3Words (W3W) addressing system was primarily due to the system's algorithm sorting words in a way that led to similar-sounding words, homophones, and plurals being placed in close proximity to each other. This issue was identified by a security consultant who found thousands of locations with similar words less than 1km apart [113504].
(b) The software failure incident occurring due to human actions:
In the case of the Keswick Mountain Rescue report, an error occurred when a couple provided a W3W grid reference to emergency services, leading the rescue team to be sent many miles away from the actual location of the injured walker. The error in this incident was attributed to factors such as mistakes in reading out the words, typing them in, or in onward communication, which are human actions that could have contributed to the failure [113504]. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident occurring due to hardware:
- The article does not mention any software failure incident occurring due to contributing factors originating in hardware [113504].
(b) The software failure incident occurring due to software:
- The software failure incident discussed in the article is related to the What3Words (W3W) digital addressing system. The issue highlighted is with the system's algorithm that sorts where to put which three words, particularly in cases of similar sounding words, homophones, and plurals. This software failure could lead to emergency services personnel being directed to the wrong location, potentially causing life-threatening delays [113504]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident related to the What3Words (W3W) addressing system does not appear to be malicious. The failure was non-malicious and stemmed from the system's algorithm sorting similar words in close proximity, leading to potential errors in pinpointing locations for emergency services. The issue was highlighted by a security consultant, Andrew Tierney, who found numerous examples of similar-sounding words and plurals in close proximity, which could result in emergency services personnel being directed to the wrong location, potentially impacting response times and outcomes [113504]. The incident was attributed to design features of the system, such as shuffling word combinations intentionally, rather than any malicious intent to harm the system. |
| Intent (Poor/Accidental Decisions) |
poor_decisions |
(a) The intent of the software failure incident:
- The software failure incident related to the What3Words (W3W) addressing system appears to involve poor_decisions. The system's algorithm sorting the three-word addresses seems to have introduced a significant number of words that can be easily confused, such as plurals and homophones, in close proximity to each other. This issue could lead to emergency services personnel being directed to the wrong location, potentially causing life-threatening delays [113504]. |
| Capability (Incompetence/Accidental) |
development_incompetence, accidental |
(a) The software failure incident related to development incompetence is evident in the case of the What3Words (W3W) addressing system. A security consultant discovered that the system had thousands of locations with similar words less than 1km apart, including plurals and homophones that could easily be confused. This issue was attributed to how the system's algorithm sorted where to place which three words, particularly in terms of similar sounding words and plurals. The researcher Andrew Tierney highlighted that in time-critical situations, such as emergencies, confusion caused by the system's design could lead emergency services personnel to the wrong location, potentially resulting in life-threatening consequences [113504].
(b) The software failure incident related to accidental factors is seen in the report from Keswick Mountain Rescue, where errors occurred when a couple provided a W3W grid reference to emergency services for an injured walker. The rescue team was initially sent "many miles" away from the actual location due to an unknown reason in the W3W reference. This incident highlights how accidental factors, such as miscommunication or misinterpretation of the three-word addresses, could lead to errors in locating individuals in need of assistance [113504]. |
| Duration |
temporary |
The software failure incident related to the What3Words (W3W) addressing system can be categorized as a temporary failure. This is because the incident was caused by contributing factors introduced by certain circumstances, specifically the algorithm sorting issues related to similar sounding words, homophones, and plurals [113504]. The system's design intentionally shuffles word combinations around the world, which can lead to close repetitions and the use of plurals in physically close locations. While the overwhelming proportion of similar sounding three-word combinations are far apart, there are still cases where similar sounding word combinations are nearby, leading to potential errors in location pinpointing [113504]. The company acknowledged the issue and mentioned that their Autosuggest feature actively intercepts possible errors or confusions to help users identify potential mistakes, indicating that the failure was not permanent but rather a result of specific design choices and circumstances [113504]. |
| Behaviour |
other |
(a) crash: The software failure incident related to the What3Words (W3W) addressing system does not involve a crash where the system loses state and does not perform any of its intended functions. Instead, the issue highlighted by a security consultant is related to the proximity of similar three-word addresses in the system, potentially leading to emergency services personnel being directed to the wrong location [113504].
(b) omission: The incident does not involve a failure due to the system omitting to perform its intended functions at an instance(s). The concern raised is about the potential for confusion and errors in location pinpointing due to the close proximity of similar-sounding or spelled three-word addresses in the W3W system [113504].
(c) timing: The failure is not related to the system performing its intended functions correctly but too late or too early. The issue highlighted in the article is more about the accuracy of location pinpointing and the potential for errors due to similar three-word addresses being in close proximity [113504].
(d) value: The software failure incident is not due to the system performing its intended functions incorrectly. Instead, the concern raised is about the potential for mistakes in location identification and the implications this could have in time-critical situations, such as emergency services responding to the wrong location [113504].
(e) byzantine: The failure is not related to the system behaving erroneously with inconsistent responses and interactions. The issue highlighted in the article is more about the design and implementation of the W3W system, specifically regarding the proximity of similar three-word addresses and the potential for confusion in location identification [113504].
(f) other: The behavior of the software failure incident can be categorized as a design flaw in the system's algorithm for sorting and placing three-word addresses, particularly in terms of handling homophones, similar-sounding words, and plurals. This flaw could lead to confusion and potential errors in location pinpointing, impacting the effectiveness of emergency services and potentially risking lives in critical situations [113504]. |