All software updates dispatched to customers should be rigorously tested beforehand to ensure they are bug-free and the update process is seamless. A “failsafe strategy” should be established to maintain the vehicle’s operation, such as reverting to an earlier software version if any problems arise. Along with this, a warning system and information on how the user can address the issue should be provided. In the event of a major failure, the response might require preventing the user from using the vehicle. In all cases, the manufacturer must be aware of any issues impacting the entire fleet and act swiftly to resolve the issue and ensure the customer’s safety.
Main Question
Is a process for managing failed updates implemented?
Alternative Questions:
- As part of the update process is there a method for identifying the reason for a failed update?
- As part of the process is there a clearly defined method for encouraging updates to the customer’s vehicle?
- Does the update process include a method for reverting to the previous software version when an update fails or until a software patch has been developed?