Incident: Ford Focus Electric Power-Loss Software Recall Incident

Published Date: 2013-11-01

Postmortem Analysis
Timeline 1. The software failure incident involving the power-loss problem in Ford Focus Electric vehicles happened in 2012-2014 [22548]. 2. The article was published on 2013-11-01. 3. Therefore, the software failure incident with the power-loss problem in Ford Focus Electric vehicles likely occurred in 2013.
System 1. Powertrain control module software in 2012-14 Ford Focus Electric [22548]
Responsible Organization 1. Ford - Ford was responsible for causing the software failure incident in the 2012-14 Focus Electric due to a software issue in the powertrain control module [22548].
Impacted Organization 1. Ford - The software failure incident impacted Ford as they had to recall about 2,500 Focus Electric vehicles due to a power-loss problem caused by a software issue in the powertrain control module [22548].
Software Causes 1. Software issue in the powertrain control module causing power loss to the front wheels [22548]
Non-software Causes 1. Power-loss problem in the 2012-14 Ford Focus Electric due to a software issue in the powertrain control module [22548]. 2. Problem with an exhaust-gas temperature sensor in Ford Super Duty ambulances from the 2011-12 model years [22548].
Impacts 1. Loss of power to the front wheels in Ford Focus Electric vehicles due to a software issue in the powertrain control module, leading to potential safety hazards for drivers [22548]. 2. Potential shutdown of 6.7-liter turbocharged V8 diesel engines in Ford Super Duty ambulances due to a problem with an exhaust-gas temperature sensor, which could result in the engine not being restarted for at least one hour, posing risks for emergency response operations [22548].
Preventions 1. Implementing more rigorous software testing procedures during the development phase to catch the power-loss problem before the vehicles were released to the market [22548]. 2. Conducting thorough risk assessments and quality assurance checks on the powertrain control module software to identify and address potential issues related to power loss [22548]. 3. Enhancing the monitoring and reporting system for customer complaints and feedback to promptly identify patterns or trends indicating software-related problems, allowing for early intervention and prevention of widespread issues [22548].
Fixes 1. Updating the software in the powertrain control module of the affected Ford Focus Electric vehicles to address the power-loss problem [22548].
References 1. National Highway Traffic Safety Administration (N.H.T.S.A.) [22548] 2. Ford [22548]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization (a) In the provided article [22548], Ford experienced a software failure incident related to a power-loss problem in its 2012-14 Focus Electric vehicles due to a software issue in the powertrain control module. This incident led to a recall of about 2,500 vehicles. Additionally, Ford faced another software-related issue with its Super Duty ambulances from the 2011-12 model years, where a problem with an exhaust-gas temperature sensor could cause the engine to shut down. These incidents indicate that software failure incidents have occurred within the same organization (Ford) with different products.
Phase (Design/Operation) design, operation (a) The software failure incident related to the design phase is evident in the article as Ford identified a software issue in the powertrain control module of its 2012-14 Focus Electric vehicles. This software issue caused a loss of power to the front wheels, leading to a power-loss problem [22548]. (b) The software failure incident related to the operation phase is highlighted in the article when Ford received reports from Focus Electric owners who had experienced the power-loss problem while driving. One owner even got stranded on a highway due to the issue, indicating a failure during the operation or use of the vehicle [22548].
Boundary (Internal/External) within_system (a) The software failure incident related to the power-loss problem in Ford Focus Electric vehicles was within the system. Ford identified a software issue in the powertrain control module as the cause of the loss of power to the front wheels [22548]. The company's internal review group and customer satisfaction forum were involved in analyzing the problem and recommending further analysis based on reports from the field. Ford described the recall as voluntary but acknowledged the need to inform the National Highway Traffic Safety Administration (N.H.T.S.A.) once aware of the safety problem to avoid facing a civil fine. The incident was addressed through internal processes and evaluations before the N.H.T.S.A. opened its investigation.
Nature (Human/Non-human) non-human_actions (a) The software failure incident related to the Ford Focus Electric power-loss problem was due to non-human actions. The issue was attributed to a software problem in the powertrain control module, causing a loss of power to the front wheels. Ford mentioned that the steering and brakes would work normally despite the power loss, indicating that the failure was not directly caused by human actions [22548].
Dimension (Hardware/Software) hardware, software (a) The software failure incident related to hardware: - The article mentions a software issue in the powertrain control module causing a loss of power to the front wheels in Ford Focus Electric vehicles [22548]. (b) The software failure incident related to software: - The same article highlights that a software issue in the powertrain control module was the root cause of the power-loss problem in Ford Focus Electric vehicles, leading to the recall [22548].
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident related to the Ford Focus Electric recall was non-malicious. The power-loss problem in the 2012-14 Focus Electric was attributed to a software issue in the powertrain control module, which could cause a loss of power to the front wheels. Ford described the recall as voluntary and stated that they were following their process to address the issue. There was no indication in the article that the software issue was introduced with malicious intent by any individual or group [22548].
Intent (Poor/Accidental Decisions) unknown (a) The software failure incident related to the Ford Focus Electric power-loss problem was not due to poor decisions but rather due to a software issue in the powertrain control module that could cause a loss of power to the front wheels. Ford conducted an evaluation and analysis of the reports from the field, leading to the recall of the affected vehicles [22548]. (b) The incident was not caused by accidental decisions but rather by a specific software issue in the powertrain control module that resulted in power loss to the front wheels of the Ford Focus Electric vehicles [22548].
Capability (Incompetence/Accidental) accidental (a) The software failure incident related to the Ford Focus Electric recall was not due to development incompetence but rather due to a software issue in the powertrain control module that could cause a loss of power to the front wheels [22548]. (b) The software failure incident related to the Ford Focus Electric recall was accidental, as Ford described the recall as voluntary and stated that they were following their process, and the N.H.T.S.A. opened its investigation while Ford was conducting its evaluation [22548].
Duration temporary (a) The software failure incident related to the Ford Focus Electric's power-loss problem was temporary. Ford initially referred the issue to its customer satisfaction forum due to a "low occurrence rate" but later, after further analysis and reports of problems, decided to recall about 2,500 vehicles [22548].
Behaviour value, other (a) crash: The software failure incident related to the Ford Focus Electric involved a power-loss problem due to a software issue in the powertrain control module, causing a loss of power to the front wheels [22548]. (b) omission: There is no specific mention of the software failure incident omitting to perform its intended functions at an instance(s) in the provided article. (c) timing: There is no specific mention of the software failure incident performing its intended functions correctly, but too late or too early in the provided article. (d) value: The software failure incident in the Ford Focus Electric involved the system performing its intended functions incorrectly by causing a loss of power to the front wheels [22548]. (e) byzantine: There is no specific mention of the software failure incident behaving erroneously with inconsistent responses and interactions in the provided article. (f) other: The software failure incident in the Ford Focus Electric could be categorized as a "power-loss problem" that affected the functionality of the vehicle, leading to a recall due to safety concerns [22548].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence harm (b) harm: People were physically harmed due to the software failure. The software failure incident related to the Ford Focus Electric involved a power-loss problem due to a software issue in the powertrain control module. This issue could cause a loss of power to the front wheels while driving. One owner reported being stranded on a highway in what she thought was a hazardous location due to the power loss incident [22548].
Domain transportation, utilities (a) The failed system was intended to support the transportation industry. The software issue in the powertrain control module of Ford's 2012-14 Focus Electric caused a loss of power to the front wheels, impacting the vehicle's ability to move people and things [Article 22548]. (g) Additionally, the software failure incident also affected the utilities industry as Ford announced a recall of about 3,100 Super Duty ambulances due to a problem with an exhaust-gas temperature sensor that could shut down the 6.7-liter turbocharged V8 diesel engines, impacting power services [Article 22548].

Sources

Back to List