Not Applicable
The present invention relates to automotive diagnostics, and more specifically, to a system and method of predicting automotive problems or failure based on a collection of historical information.
Automotive repair is, for the most part, inevitable. If driven long enough, most automobiles will require at least some form of routine maintenance and repair. Although repairs are almost certain, it is unknown as to when the vehicle will fail, and therefore, automotive failure usually comes as a surprise. Furthermore, the average vehicle owner does not know what those failures are likely to be or what the related cost of repair would entail.
The difficulty in predicting diagnostic events for a vehicle stem from the fact that different vehicles exhibit different vulnerabilities. Therefore, a particular component may be susceptible to failure in a particular vehicle, and not as susceptible to failure in another model of vehicle. Furthermore, that same component may have a different susceptibility of failure from one model year to the next in the same model of vehicle. Thus, there is not a universal template or formula that can be applied to all vehicles for predicting when failure is likely to occur.
To the average automobile owner, there is a considerable amount of uncertainty associated with automotive diagnostics and repair. Automobiles are complex electro-mechanical devices, and as such, when a problem associated with the operation of the automobile arises, it may be well beyond the skill of the ordinary automobile owner to identify the problem and know how to perform the related fix. Thus, automobile owners have been relying on automotive professionals, such as a repair shop or dealership, to assist in the diagnosis and repair of their automobiles.
Although automotive professionals may be helpful in diagnosing and repairing an automotive problem, there is a certain level of distrust consumers have associated with automotive professionals. In some instances, the automotive professionals may leverage their experience and knowledge when dealing with the consumer to drive up the cost or to encourage the consumer to make repairs which may not be absolutely necessary. Therefore, consumers tend to feel as if they have been taken advantage of when they visit automotive professionals. That feeling is compounded by the fact that costs associated with having an automotive professional service your vehicle tends to be very high.
Aside from automotive professionals, oftentimes the best available information is from someone who currently owns or previously owned the same year, make, and model of the vehicle under consideration. That person can describe their experience with the vehicle, including the maintenance history or any repairs that performed on the vehicle, and when those repairs took place (i.e., at 50,000 miles, etc.).
Although the information received from the experienced individual may provide some measure of assistance in gauging the diagnostic future of a particular vehicle, the information provided by the experienced individual may not be representative of a pattern of failure. In this regard, there is a likelihood that the failures, or lack thereof, identified by the experienced individual may not be attributable to a reliable pattern, but instead are simply anecdotal events which may provide very little basis for reliability.
As such, there is a need in the art for a reliable and comprehensive predictive diagnostic system and method which provides a predictive diagnostic summary for a vehicle under consideration, wherein the predictive diagnostic summary is compiled from a historical database of similar vehicles.
According to one embodiment of the present invention, there is provided a method of predicting defects likely to occur in a vehicle over a predetermined period. The method includes receiving vehicle characteristic data regarding a vehicle under consideration, and establishing a defect database including information related to defects that have occurred in different vehicles and the mileage at which such defects occurred. The method additionally includes identifying defects that occurred in vehicles corresponding to the vehicle under consideration, and the mileage at which such defects occurred. Defects which fail to satisfy minimum count requirements are then filtered out, and the defects are then sorted in order of the highest defect count.
The received vehicle characteristic data may include vehicle identification information including the year, make, model, engine, and current mileage of the vehicle under consideration. The defect database information may include the year, make, model, engine, defect(s), and mileage of the referenced vehicle as of the time of each associated defect.
The method may additionally include the step of comparing vehicle characteristic data associated with the vehicle under test with vehicle characteristic data associated with the identified defects stored in the defect database to identify defects that have occurred in vehicles that substantially correspond to the vehicle under consideration.
The method may also include the step of restricting the identified defects to defects that have occurred in substantially corresponding vehicles that are associated with a reference mileage that is within a mileage bracket that substantially corresponds to the current mileage of the vehicle under test. The mileage bracket may extend from a mileage less than the current mileage to a mileage greater than the current mileage. The mileage bracket may extend from a mileage approximately 15,000 less than the current mileage to a mileage approximately 30,000 miles greater than the current mileage.
The method may additionally include the step of adjusting the current mileage to the nearest 5,000 mile gradient. The mileage bracket may extend from 15,000 miles less than the adjusted mileage to 30,000 miles greater than adjusted mileage.
The method may further include the step of receiving live data from the vehicle under consideration. The live data may include diagnostic information regarding operating characteristics of an automotive device associated with at least one defect within the mileage bracket. The method may additionally include the step of adjusting the current mileage based on diagnostic information indicating the operating condition of the automotive device associated with the defect. The step of adjusting the current mileage may include the step of increasing the current mileage where the diagnostic information associated with the automotive device associated with the defect indicates that the associated device is not in optimum operating condition. The step of adjusting the current mileage may also include the step of increasing the current mileage where the diagnostic information indicates that the device associated with the defect is in optimum operating condition.
The method may also include the steps of receiving information regarding the climatic region in which the vehicle under consideration has been used, and adjusting the current mileage based on the information regarding the climate region. The step of adjusting the current mileage based on the information regarding the climatic region may comprise the step of increasing the current mileage where the information regarding the climate region indicates that the vehicle has operated in a region characterized by harsh climate conditions. At least one defect may be associated with a climatically sensitive vehicle device, which may include a muffler, a body panel, a radiator, a battery, a door lock, and a starter.
The method may include the step of limiting the identified defects to those defects which occurred in a mileage bracket that includes the mileage of the vehicle under consideration.
The defects in the defect database may be derived from actual repair records, or from a probabilistic determination of a most likely defect based on vehicle diagnostic data.
The received vehicle characteristic data may include geographic information associated with the vehicle under consideration.
The method may include the step of adjusting the mileage associated with the identified defects based on vehicle characteristic data. The mileage associated with the identified defects may be lowered based on the vehicle characteristic data. The mileage associated with the identified defects may be raised based on the vehicle characteristic data.
According to another embodiment, there is provided a predictive diagnostic system for generating a predictive diagnostic report for a vehicle under consideration. The predictive diagnostic system includes a defect database having information related to defects that have occurred in different reference vehicles and the reference mileage at which such defects occurred, wherein each reference vehicle is associated with classification data. A comparison module is in operative communication with the defect database and is configured to compare vehicle characteristic data associated with the vehicle under consideration and to identify defects that have occurred in certain ones of the different reference vehicles having associated vehicle characteristic data that is substantially similar to the vehicle characteristic data associated with the vehicle under consideration and a reference mileage that is substantially similar to the current mileage of the vehicle under consideration.
The predictive diagnostic system may also include a report generating module in operative communication with the comparison module and configured to generate a predictive diagnostic report including the identified defects and the reference mileage at which such defects occurred.
These and other features and advantages of the various embodiments disclosed herein will be better understood with respect to the following description and drawings, in which like numbers refer to like parts throughout, and in which:
The present invention is best understood by reference to the following detailed description when read in conjunction with the accompanying drawings.
Referring now to the drawings, wherein the showings are for purposes of illustrating a preferred embodiment of the present invention only, and not for purposes of limiting the same, there is shown a predictive diagnostic system 10 capable of determining a likelihood of failure for a particular vehicle system or component. The predictive diagnostic system 10 compares vehicle characteristic data associated with a vehicle under consideration with stored information in a historical defect database to identify defects that have occurred in the same or substantially similar vehicles, and the mileage at which those defects occurred. In this regard, the predictive diagnostic system 10 may predict a low, medium or high probability of failure for a component(s) within a certain mileage range, and thus, provides the owner of the vehicle with a probable likelihood of which components are likely to fail over certain mileage ranges. The predictive diagnosis may allow the owner to preempt the failure by replacing the component beforehand, or if the vehicle begins to operate at a sub-optimal level, the owner will have a good idea of what component may need replacing. Therefore, the owner may be able to resolve the problem on his own, or if the owner takes the vehicle to an automotive professional, the owner will have a good idea of what is needed to fix the problem, rather than relying solely on the recommendation of the automotive professional.
Referring now specifically to
The historical database 14 is a comprehensive compilation of historical vehicle data. As used herein, the stored information in the defect database includes, but is not limited to, information associated with defects which are not commonly known to occur in certain vehicles. Each entry into the database 14 relates to a system or component failure for a specific vehicle associated with characteristic data representative of the vehicle. For instance, the characteristic data may include vehicle identification information, such as the year, make, model, engine of the vehicle and current mileage. Therefore, to determine the predictive diagnosis for the vehicle under consideration, the characteristic data associated the vehicle under consideration is entered into the defect database 14 and the characteristic data is matched with vehicle data in the database associated with similar characteristic data, e.g., stored vehicle identification data, to determine the likelihood of failure within a certain mileage range.
The failures/defects listed in the historical defect database 14 may be identified according to several different strategies. In one embodiment, the defects are associated with actual repairs performed at a repair shop. In another embodiment, the defects are determined by insurance claims submitted to an insurance company. In yet another embodiment, the defects are determined based on a probabilistic determination of a likely defect based on an analysis of vehicle data. For more information related to the probabilistic determination, please see U.S. patent application Ser. No. 13/567,745 for Handheld Scan Tool with Fixed Solution Capability, now U.S. Pat. No. 8,909,416 issued Dec. 9, 2014, the contents of which are incorporated herein by reference. The failures/defects listed in the database 14 may also be determined according to a combination of any of the strategies listed above, or according to other means known by those skilled in the art.
The system 10 further includes a comparison module 20 and a report generating module 22 in operative communication with each other and the defect database/server 14. The comparison module 20 is operative to match the vehicle characteristic data associated with the vehicle under consideration with similar data found in the database 14 to identify defects which have occurred in those matching vehicles. The report generating module 22 is operative to compile the results and generate the predictive diagnostic report, which is presented to the user on a display, such a display associated with computing device 12.
The following example illustrates benefits which the predictive diagnostic system 10 provides. In this example, the vehicle under consideration is a 2005 HONDA™ ACCORD™, although it is understood that the predictive diagnostic system 10 may be used with any vehicle. The defect database 14 includes several entries related to a 2005 HONDA™ ACCORD™. Based on those entries, an owner of a 2005 HONDA ACCORD can determine the likelihood that his vehicle will experiences problems at certain mileage ranges. For example, between 75,000 and 100,000 miles, there may be a high likelihood that the owner may need to replace the ignition coil, a median probability or likelihood that the user will need to replace the camshaft position sensors, and a low probability that the owner will need to replace the engine coil module.
According to one embodiment, the input into the defect database 14 is vehicle characteristic data representative of the vehicle under consideration. Thus, the more vehicle characteristic data entered by the user, the more accurate and precise the resultant predictive diagnosis will be. Along these lines, the vehicle characteristic data may not only include vehicle identification information, such as the year, make, model, and engine, as mentioned above, but may also include other information that is specific to the vehicle under consideration. For instance, the vehicle characteristic data may include the geographic area (state, city, zip code, etc.) or climatic conditions in which the vehicle is primarily driven. Vehicles in different geographic areas may encounter symptoms related to the geographic area in which the vehicle is driven. For instance, vehicles driven in the northern part of the United States regularly encounter snow in the winter months. Road maintenance crews in those areas of the country regularly spread salt on the roads to mitigate slippery road conditions. Thus, as the vehicle drives over the salted roads, the undercarriage of the vehicle may be exposed to the salt, which may cause rust/corrosion or may lead to other problematic conditions.
However, vehicles driven in southern states may not be susceptible to the same problems since those vehicles are generally not driven over salted roads. However, other geographic locations offer different environmental conditions which may be problematic for the vehicle, i.e., desert areas may lead to engine overheating. Therefore, the geographic location in which the vehicle under consideration is driven may lead to a more accurate and precise predictive diagnosis. Exemplary components/devices which may be climatically or geographically sensitive include may include the vehicle's muffler, body panel (susceptible to rust), radiator, battery, door lock, and starter.
Other vehicle characteristic data which may be entered into the historical database is recall information, usage information (i.e., how many miles the vehicle is driven per year), warranty information, replacement parts on the vehicle, original parts on the vehicle, gas octane used, maintenance records. Thus, the vehicle characteristic data entered into the defect database 14 allows the user to obtain matches with vehicle records associated with vehicles that not only are the same or similar to the vehicle under consideration, but were also operated and maintained in a similar fashion.
According to one embodiment, and referring now specifically to
The number of failures may then be totaled for each component within each mileage bracket to determine a percentage of failure (see bottom row of matrix 30). For instance, as shown in the example depicted in
In one implementation, the predictive diagnostic system 10 may filter out results which do not meet or exceed a defined threshold. In this regard, it is desirable to only report failures which are believed to be representative of a pattern and thus indicative of a probable outcome in the future. If there are only a minimum number of failures, i.e., failures below the set threshold, such a minimum number of failures may not be a reliable data-set for representing a potential failure in the future. The threshold may be selectively adjusted by the system operator, or by the user. The threshold may be low for newer vehicles, since there is generally less data associated with the new vehicles, and high for older vehicles, since there is generally more data associated with the older vehicles.
Referring again to
The matrix 30 may further be beneficial to identify clusters of failures at certain mileage points. For instance, with regard to Component 1 listed in the example matrix, there are three failures between 10,000-15,000 miles and five failures between 20,000-25,000 miles, although there are zero failures in the intermediate mileage bracket (i.e., 15,000-20,000 miles).
After the thresholds have been applied, the overall percentages may be recalculated to determine the percentage of failures within each mileage bracket that meet the threshold.
The results may be presented to the user in a user friendly summary 40.
In one embodiment, the predictive diagnostic system 10 may also be capable of, identifying at the server, parts and/or tools useful to repair the defects identified in the diagnostic summary 40. This may also include identifying the likely cost of the parts, tools and services for fixing/replacing the defects/components listed in the predictive diagnostic summary 40. The predictive diagnostic system 16 may also identify at the server, a listing of procedures useful to repair/replace defective components.
In one embodiment the necessary repair parts and/or tools associated with existing and/or predicted defect are identified by the corresponding universal part numbers, or Aftermarket Catalog Enhanced Standard (ACES) part number. This permits parts/service providers and “do it yourself” DIY customers to readily price and order the exact parts/tools necessary to make repairs. Parts/service providers may electronically cross reference ACES numbers to their own parts numbering system to identify the availability/costs of parts and tools without the need for manually identifying any necessary parts, tools or services. DIY customers can locate competitive prices for parts and tools by searching the ACES numbers on the World Wide Web. The results of such a search can also be provided with predictive diagnostic summary 40.
According to other implementation of the present invention, the predictive failure analysis may also be refined based on specific diagnostic history of the vehicle under consideration. In other words, the predictive failure analysis may be able to correlate one part failing in response to another part failing in the past. More specifically, one part or component which wears out may have a cascading effect on wearing out other parts or components, particularly other parts or components within the same vehicle system. Thus, there may be a system level correlation when one part has failed in the past.
The system 10 may also be capable of adjusting the predictive diagnosis for the vehicle under consideration based on operating condition information received from the vehicle, such as live data. The predictive diagnostic system 10 may generate a baseline predictive diagnostic summary when characteristic data is uploaded to the historical database, as described above. From the baseline predictive diagnostic summary, the system 10 may be able to make a prediction as to the general health or remaining effectiveness/lifespan of one or more vehicle components. For instance, the baseline predictive diagnostic summary may be used to predict that a particular component may be useful for another 5,000 miles before the likelihood of failure increases to the point where a failure is likely.
The information extrapolated from the baseline predictive diagnostic summary may be cross-referenced with live data to provide a more accurate prediction as to the remaining lifespan of that component. For instance, if the live data shows a relatively healthy component, the prediction of 5,000 miles before a likely failure may be increased. Conversely, if the live data shows a relatively worn or ineffective component, the prediction of 5,000 miles before a likely failure may be decreased.
Thus, the system 10 may conduct an iterative analysis based on the live data to more accurately predict the likelihood of failure. The iterations include initially generating the baseline diagnostic report from basic characteristic data, i.e., year, make, model, and current mileage. Then the prediction may be refined based on the live data supplied to the system 10. In this regard, the likelihood of failure may be increased, decreased, or remain unchanged based on the live data.
Referring now specifically to
After vehicle information is analyzed, the current mileage “CM” may be adjusted to define an adjusted current mileage “ACM.” For instance, if the vehicle was driven off-road, in harsh conditions, etc., the vehicle may have endured “hard miles.” Thus, the current mileage CM for the vehicle may be increased to account for the hard miles. Conversely, if the vehicle was almost exclusively driven in ideal driving conditions, and has been routinely maintained, the current mileage CM of the vehicle may be decreased to account for the optimal conditions. In the example listed in
Once the adjusted current mileage ACM has been determined, an adjusted mileage bracket “AMB” is defined based on the adjusted current mileage ACM. The defects which fall within the adjusted mileage bracket AMB are then identified. In
In the example described above in relation to
After a preliminary assessment, the current mileage CM and defects D1, D2, D3 may be plotted on the mileage axis. A more detailed analysis may reveal that the effective life of the vehicle is less than the standard or more than the standard. Therefore, the mileage associated with the defects may be adjusted along the mileage axis, accordingly. When the effective life of the vehicle is more than the standard, the mileage associated with the defects may be increased, and conversely, if the effective life of the vehicle is less than the standard, the mileage associated with the defects may be decreased.
After this analysis, an adjusted mileage bracket AMB may be created to include the current mileage CM of the vehicle. The adjusted defects AD1, AD2, and AD3 which fall within the adjusted mileage bracket AMB may then be identified.
The above description is given by way of example, and not limitation. Given the above disclosure, one skilled in the art could devise variations that are within the scope and spirit of the invention disclosed herein. Further, the various features of the embodiments disclosed herein can be used alone, or in varying combinations with each other and are not intended to be limited to the specific combination described herein. Thus, the scope of the claims is not to be limited by the illustrated embodiments.
This present application is a continuation-in-part application of U.S. patent application Ser. No. 13/589,532, filed Aug. 20, 2012, the contents of which are incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
D334560 | Wilson | Apr 1993 | S |
5347211 | Jakubowski | Sep 1994 | A |
D377622 | Chen | Jan 1997 | S |
5635841 | Taylor | Jun 1997 | A |
5758300 | Abe | May 1998 | A |
5767681 | Huang | Jun 1998 | A |
5809437 | Breed | Sep 1998 | A |
5859628 | Ross et al. | Jan 1999 | A |
5884202 | Arjomand | Mar 1999 | A |
6000413 | Chen | Dec 1999 | A |
6055468 | Kaman et al. | Apr 2000 | A |
6094609 | Arjomand | Jul 2000 | A |
6169943 | Simon et al. | Jan 2001 | B1 |
6225898 | Kamiya et al. | May 2001 | B1 |
6263268 | Nathanson | Jul 2001 | B1 |
6389337 | Kolls | May 2002 | B1 |
6438471 | Katagishi et al. | Aug 2002 | B1 |
6499385 | Protti | Dec 2002 | B2 |
6535112 | Rothshink | Mar 2003 | B1 |
6587768 | Chene et al. | Jul 2003 | B2 |
6611740 | Lowrey et al. | Aug 2003 | B2 |
6650318 | Arnon | Nov 2003 | B1 |
6718425 | Pajakowski et al. | Apr 2004 | B1 |
6732031 | Lightner et al. | May 2004 | B1 |
6807469 | Funkhouser et al. | Oct 2004 | B2 |
6836708 | Tripathi | Dec 2004 | B2 |
6847916 | Ying | Jan 2005 | B1 |
6868369 | Huang | Mar 2005 | B2 |
6925368 | Funkhouser et al. | Aug 2005 | B2 |
6940270 | Chen | Sep 2005 | B2 |
D510287 | Chen | Oct 2005 | S |
6957133 | Hunt et al. | Oct 2005 | B1 |
6968733 | Andreasen | Nov 2005 | B2 |
7030742 | Treadway | Apr 2006 | B2 |
7085680 | Huang | Aug 2006 | B2 |
7116216 | Andreasen | Oct 2006 | B2 |
7209813 | Namaky | Apr 2007 | B2 |
RE39619 | Andreasen | May 2007 | E |
D545223 | Chen | Jun 2007 | S |
D559137 | Protti | Jan 2008 | S |
D560129 | Rich | Jan 2008 | S |
D560527 | Rich | Jan 2008 | S |
7321774 | Lau | Jan 2008 | B1 |
7325775 | Chen | Feb 2008 | B2 |
D563249 | Chen | Mar 2008 | S |
7363149 | Klausner et al. | Apr 2008 | B2 |
D569280 | Chen | May 2008 | S |
7376497 | Chen | May 2008 | B2 |
D571241 | Andreasen | Jun 2008 | S |
7437227 | Andreasen | Oct 2008 | B2 |
D581822 | Madison | Dec 2008 | S |
7464000 | Huang | Dec 2008 | B2 |
D588621 | Baty | Mar 2009 | S |
D590387 | Chen | Apr 2009 | S |
7520668 | Chen | Apr 2009 | B2 |
RE40798 | Chen | Jun 2009 | E |
RE40799 | Chen | Jun 2009 | E |
7603293 | Chen | Oct 2009 | B2 |
7620484 | Chen | Nov 2009 | B1 |
D610586 | Chen | Feb 2010 | S |
7734390 | Chen | Jun 2010 | B2 |
7778750 | Knight et al. | Aug 2010 | B2 |
D624446 | Chen | Sep 2010 | S |
D624838 | Chen | Oct 2010 | S |
D625209 | Chen | Oct 2010 | S |
D625210 | Chen | Oct 2010 | S |
D625634 | Chen | Oct 2010 | S |
7904219 | Lowrey et al. | Mar 2011 | B1 |
7974750 | Namaky | Jul 2011 | B2 |
8019503 | Andreasen | Sep 2011 | B2 |
8024083 | Chen | Sep 2011 | B2 |
D646188 | Chen | Oct 2011 | S |
D646599 | Chen | Oct 2011 | S |
8032419 | Chen | Oct 2011 | B2 |
8068951 | Chen et al. | Nov 2011 | B2 |
8301329 | Andreasen | Oct 2012 | B2 |
8306687 | Chen | Nov 2012 | B2 |
8370018 | Andreasen et al. | Feb 2013 | B2 |
8509986 | Chen | Aug 2013 | B1 |
8600610 | Bertosa et al. | Dec 2013 | B2 |
8630765 | Chen | Jan 2014 | B2 |
8811008 | Selkirk et al. | Aug 2014 | B2 |
8825270 | Chen | Sep 2014 | B2 |
8825271 | Chen | Sep 2014 | B2 |
8831814 | Chen | Sep 2014 | B2 |
8855621 | Chen | Oct 2014 | B2 |
8862117 | Chen | Oct 2014 | B2 |
8880274 | Chen | Nov 2014 | B2 |
8909416 | Chen et al. | Dec 2014 | B2 |
9002554 | Chen | Apr 2015 | B2 |
9014908 | Chen | Apr 2015 | B2 |
9026400 | Chen et al. | May 2015 | B2 |
9117319 | Chen et al. | Aug 2015 | B2 |
9123051 | Chen | Sep 2015 | B2 |
9177428 | Nguyen et al. | Nov 2015 | B2 |
9183681 | Fish | Nov 2015 | B2 |
D745029 | Gray et al. | Dec 2015 | S |
D746316 | Gray et al. | Dec 2015 | S |
D746323 | Gray et al. | Dec 2015 | S |
9213332 | Fish et al. | Dec 2015 | B2 |
D747734 | Gray et al. | Jan 2016 | S |
D749623 | Gray et al. | Feb 2016 | S |
9262254 | Bertosa et al. | Feb 2016 | B2 |
9292977 | Bertosa et al. | Mar 2016 | B2 |
D757059 | Gray et al. | May 2016 | S |
9329633 | Selkirk et al. | May 2016 | B2 |
D770462 | Gray et al. | Nov 2016 | S |
9858731 | Fish et al. | Jan 2018 | B2 |
9904634 | Case, Jr. et al. | Feb 2018 | B2 |
10295333 | Fish et al. | May 2019 | B2 |
10467906 | Fish et al. | Nov 2019 | B2 |
20030171111 | Clark | Sep 2003 | A1 |
20040110472 | Witkowski | Jun 2004 | A1 |
20080004764 | Chinnadurai | Jan 2008 | A1 |
20080154755 | Lamb | Jun 2008 | A1 |
20090062978 | Picard | Mar 2009 | A1 |
20140046800 | Chen | Feb 2014 | A1 |
20170186054 | Fish et al. | Jun 2017 | A1 |
20180101775 | Fish | Apr 2018 | A1 |
Number | Date | Country |
---|---|---|
WO 0186576 | Nov 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20160027223 A1 | Jan 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13589532 | Aug 2012 | US |
Child | 14871594 | US |