Post-Repair Data Comparison

• US 20170132578A1
• Filed: 11/05/2015
• Published: 05/11/2017
• Est. Priority Date: 11/05/2015
• Status: Active Grant

• Current Assignee: Snap-On Incorporated
• Original Assignee: Snap-On Incorporated
• Inventors: Merg, Patrick S., Foreman, Jacob G., Brozovich, Roy Steven
• Granted Patent: US 9,704,141 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/285 Clustering or classification
• CPC Class Codes: G06Q 10/20 Administration of product repair or maintenance
• CPC Class Codes: G07C 5/00 Registering or indicating the working of vehicles

Abstract

Methods and apparatus are provided for repairing vehicles. A computing device can receive post-repair data regarding a first vehicle. The computing device can compare the post-repair data to a post-repair dataset regarding at least one vehicle other than the first vehicle. The post-repair dataset can include at least one of an instance of successful post-repair data and an instance of unsuccessful post-repair data. The computing device can determine that a repair to the first vehicle is successful if the post-repair dataset matches an instance of successful post-repair data of the post-repair dataset. The computing device can determine that the repair to the first vehicle is unsuccessful if the post-repair dataset matches an instance of unsuccessful post-repair data within the post-repair dataset. The computing device can indicate whether the repair is successful or unsuccessful.

Claims

1. A method comprising:

receiving, by a computing device, first post-repair data regarding a first vehicle, wherein the first post-repair data is associated with a first repair order comprising first complaint data;

comparing, by the computing device, the first post-repair data to a first set of post-repair data regarding at least one vehicle other than the first vehicle, wherein the first set of post-repair data includes at least one of an instance of successful post-repair data and an instance of non-successful post-repair data, and wherein the first set of post-repair data includes at least one instance of post-repair data associated with a repair order including complaint data that matches the first complaint data;

determining, by the computing device, that a first repair to the first vehicle is successful if the first post-repair data matches a first instance of successful post-repair data within the first set of post-repair data or that the first repair to the first vehicle is non-successful if the first post-repair data matches a first instance of non-successful post-repair data within the first set of post-repair data; and

outputting, by the computing device, an indication that the first repair is successful or non-successful.

2. The method of claim 1, wherein outputting the indication that the first repair is successful or non-successful comprises outputting a likelihood that the first repair is successful.

3. The method of claim 1, wherein outputting the indication that the first repair is successful or non-successful comprises outputting a likelihood that the first repair is unsuccessful.

4. The method of claim 1, wherein the first post-repair data regarding the first vehicle is received after completion of the first repair to the first vehicle and prior to the first vehicle being returned to an owner of the first vehicle after completion of the first repair to the first vehicle.

5. The method of claim 1, wherein outputting the indication that the first repair is successful or non-successful comprises outputting one or more suggested repairs to avoid a comeback.

6. The method of claim 1, further comprising:

receiving, by the computing device, a second repair order including second complaint data and a comeback indicator; and

determining whether the first repair to the first vehicle is successful or non-successful based on the comeback indicator.

7. The method of claim 1, further comprising:

classifying, by the computing device, the first post-repair data as an instance of successful post-repair data in response to determining the first repair to the first vehicle is successful or as an instance of non-successful post-repair data in response to determining the first repair to the first vehicle is non-successful.

8. The method of claim 1, further comprising:

classifying, by the computing device, the first post-repair data as an instance of potentially-successful post-repair data in response to determining the first repair to the first vehicle is successful;

determining, by the computing device, that an indication that the first repair to the first vehicle is non-successful has not been received after a pre-determined amount of time; and

responsively reclassifying, by the computing device, the first post-repair data from an instance of potentially-successful post-repair data to an instance of successful post-repair data.

9. The method of claim 1, further comprising:

receiving, by the computing device, a first repair order associated with the first post-repair data, wherein the first repair order includes a first repair order entry including at least one of a complaint leading to the first repair, a cause leading to the first repair, and a correction indicating the first repair;

classifying, by the computing device, the first post-repair data as an instance of successful post-repair data; and

after classifying the first post-repair data as an instance of successful post-repair data, receiving, by the computing device, second post-repair data regarding the first vehicle and a second repair order associated with the second post-repair data.

10. The method of claim 9, further comprising:

reclassifying, by the computing device, the first post-repair data from an instance of successful post-repair data to an instance of non-successful post-repair data based on the second repair order.

11. The method of claim 10, wherein reclassifying the first post-repair data is conditioned on receiving the second repair order within a predetermined amount of time after receiving the first repair order.

12. The method of claim 10, wherein the second repair order includes a comeback indicator, and wherein reclassifying the first post-repair data from an instance of successful post-repair data to an instance of non-successful post-repair data based on the second repair order comprises:

determining whether the comeback indicator indicates the second repair order is a comeback repair; and

after determining that the comeback indicator indicates that the second repair order is a comeback repair, reclassifying the first post-repair data from an instance of successful post-repair data to an instance of non-successful post-repair data based on the second repair order.

13. The method of claim 10, further comprising:

determining that the second post-repair data is successful post-repair data; and

reclassifying at least the first repair order based on the second post-repair data.

14. The method of claim 9, further comprising:

comparing, by the computing device, the second post-repair data to a second set of post-repair data regarding at least one vehicle other than the first vehicle, wherein the second set of post-repair data includes at least one of an instance of successful post-repair data and an instance of non-successful post-repair data;

determining, by the computing device, that a second repair to the first vehicle is successful if the second post-repair data matches an instance of the successful post-repair data within the second set of post-repair data or that the second repair to the first vehicle is non-successful if the second post-repair data matches an instance of the non-successful post-repair data within the second set of post-repair data; and

outputting, by the computing device, an indication that the second repair is successful or non-successful.

15. The method of claim 1, wherein the first post-repair data includes data selected from the group consisting of:

(i) serial data from an electronic control unit within the first vehicle, (ii) electrical measurement data from an electrical meter connected to the first vehicle, (iii) a graphical waveform from an oscilloscope connected to the first vehicle, and (iv) an On-Board Diagnostics II (OBD II) Parameter ID (PID).

16. The method of claim 1, wherein the computing device determines the first repair to the first vehicle is non-successful and outputs an indication the first repair is non-successful, and the method further comprises:

determining, by the computing device, a second instance of successful post-repair data that is associated with the first instance of non-successful post-repair data, wherein the first instance of the non-successful post-repair data is associated with a first repair order and the second instance of successful post-repair data is associated with a second repair order, and wherein each of the first repair order and the second repair order recite a common complaint; and

outputting, by the computing device, a repair listed on the second repair order.

17. The method of claim 16, further comprising:

receiving, by the computing device, second post-repair data regarding the first vehicle;

comparing, by the computing device, the second post-repair data to post-repair data associated with the second repair order;

determining, by the computing device, the second post-repair data matches the post-repair data associated with the second repair order; and

outputting, by the computing device, an indication that performing the repair listed on the second repair order to the first vehicle is successful.

18. The method of claim 1, wherein outputting the indication includes outputting an indication that the repair is non-successful, and the method further comprising:

determining, by the computing device, a possible repair to the first vehicle;

outputting, by the computing device, the possible repair to the first vehicle;

receiving, by the computing device, second post-repair data regarding the vehicle after performance of the possible repair to the first vehicle and an indication that performance of the possible repair was successful; and

classifying, by the computing device, the second post-repair data as an instance of successful post-repair data.

19. A computing device, comprising:

a processor; and

a computer readable medium configured to store at least executable instructions, wherein the executable instructions, when executed by the processor, cause the computing device to perform functions comprising;

receiving first post-repair data regarding a first vehicle, wherein the first post-repair data is associated with a first repair order comprising first complaint data,

comparing the first post-repair data to a first set of post-repair data regarding at least one vehicle other than the first vehicle, wherein the first set of post-repair data includes at least one of an instance of successful post-repair data and an instance of non-successful post-repair data, and wherein the first set of post-repair data includes at least one instance of post-repair data associated with a repair order including complaint data that matches the first complaint data,

determining that a first repair to the first vehicle is successful if the first post-repair data matches a first instance of successful post-repair data within the first set of post-repair data or that the first repair to the first vehicle is non-successful if the first post-repair data matches a first instance of non-successful post-repair data within the first set of post-repair data, and

outputting an indication that the first repair is successful or non-successful.

20. The computing device of claim 19, wherein outputting the indication that the first repair is successful or non-successful comprises outputting one or more suggested repairs to avoid a comeback.

21. A non-transitory computer readable medium configured to store at least executable instructions, wherein the executable instructions, when executed by a processor of a computing device, cause the computing device to perform functions comprising:

receiving first post-repair data regarding a first vehicle, wherein the first post-repair data is associated with a first repair order comprising first complaint data;

comparing the first post-repair data to a first set of post-repair data regarding at least one vehicle other than the first vehicle, wherein the first set of post-repair data includes at least one of an instance of successful post-repair data and an instance of non-successful post-repair data, and wherein the first set of post-repair data includes at least one instance of post-repair data associated with a repair order including complaint data that matches the first complaint data;

determining that a first repair to the first vehicle is successful if the first post-repair data matches a first instance of successful post-repair data within the first set of post-repair data or that the first repair to the first vehicle is non-successful if the first post-repair data matches a first instance of non-successful post-repair data within the first set of post-repair data; and

outputting an indication that the first repair is successful or non-successful.

22. The non-transitory computer readable medium of claim 21, wherein outputting the indication that the first repair is successful or non-successful comprises outputting one or more suggested repairs to avoid a comeback.