System and method for identifying undesired vehicle events

• US 20070173991A1
• Filed: 01/23/2006
• Published: 07/26/2007
• Est. Priority Date: 01/23/2006
• Status: Abandoned Application

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Passman, Jon, Tenzer, Stephen, Nielsen, Benjamin
• Application Number:
  US11/337,888
• Publication Number:
  US 20070173991A1
• Time in Patent Office: Days
• US Class Current: 701/29
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C

Abstract

A method for assessing the undesired use of vehicles within a fleet is described. At least one exception is defined relating to the use of vehicles within the fleet, wherein the exception is selected from the group of safety exceptions, maintenance exceptions, legal compliance exceptions, and unauthorized use exceptions. Data is received relating to the use of each vehicle within the fleet. The at least one exception is then applied to the data for each vehicle and it is determined whether any defined exceptions have occurred. A statistical metric is determined representative of the undesired use of the vehicles within the fleet based upon the defined exceptions.

Claims

1. A method for assessing the undesired use of vehicles within a fleet, comprising:

defining at least one exception relating to the use of vehicles within the fleet, wherein the exception is selected from the group of safety exceptions, maintenance exceptions, legal compliance exceptions, and unauthorized use exceptions;

receiving data relating to the use of each vehicle within the fleet;

applying the at least one exception to the data for each vehicle and determining whether any defined exceptions have occurred;

determining a statistical metric representative of the undesired use of the vehicles within the fleet based upon the defined exceptions.

2. The method of claim 1, wherein the statistical metric comprises the percentage of vehicles within the fleet having either safety or maintenance exceptions over a predetermined period of time.

3. The method of claim 1, wherein the statistical metric comprises the percentage of safety, maintenance, legal compliance, and unauthorized use exceptions generated by all of the vehicles in the fleet out of the total number of safety, maintenance, legal compliance, and unauthorized use exceptions that could have been generated by all of the vehicles in the fleet.

4. The method of claim 1, wherein the statistical metric comprises the total number of safety, maintenance, legal compliance, and unauthorized use exceptions generated by each vehicle.

5. The method of claim 1, wherein if at least one exception is a safety exception, defining a safety exception comprises selecting a use condition relating to safety and defining a threshold value or a range of threshold values representing desired use.

6. The method of claim 5, wherein the use condition relating to safety is selected from the group of speed, acceleration, braking, seat belt usage, frequent lane changes, tailgating, speed relative to turns, and the occurrence of an accident.

7. The method of claim 6, wherein, if the use condition relating to safety is the occurrence of an accident, defining a threshold value or range of threshold values representing desired use comprises importing from a fleet management module information relating to the occurrence of an accident.

8. The method of claim 5, wherein determining whether safety exceptions have occurred comprises comparing the data relating to a use condition to the threshold value or range of threshold values representing a desired use condition, and generating an exception if the data does not match the threshold value or is not within the range of threshold values representing a desired use condition.

9. The method of claim 1, wherein if at least one exception is a maintenance exception, defining a maintenance exception comprises selecting a use condition relating to maintenance and defining a threshold value or a range of threshold values representing desired use.

10. The method of claim 9, wherein the use condition relating to maintenance is selected from the group of operating the vehicle while a warning indicator is on in the vehicle, operating the vehicle while a check engine light is on in the vehicle, and operating a vehicle for which scheduled maintenance is overdue.

11. The method of claim 10, wherein, if the use condition relating to maintenance is operating a vehicle for which a scheduled maintenance is overdue, defining a threshold value or a range of threshold values representing desired use comprises receiving data relating to the maintenance schedule for each vehicle within the fleet that indicates the time at which scheduled maintenance is due for each vehicle and whether that maintenance has been performed.

12. The method of claim 11, wherein receiving data relating to the maintenance schedule for each vehicle within the fleet comprises receiving maintenance schedule data generated by a scheduling module.

13. The method of claim 9, wherein determining whether maintenance exceptions have occurred comprises comparing the data relating to a use condition to the threshold value or range of threshold values representing a desired use condition, and generating an exception if the data does not match the threshold value or is not within the range of threshold values representing a desired use condition.

14. The method of claim 1, wherein if at least one exception is a legal compliance exception, defining a legal compliance exception comprises selecting a use condition relating to legal compliance and defining a threshold value or range of threshold values representing desired use.

15. The method of claim 14, wherein defining a threshold value or range of threshold values representing desired use comprises receiving data relating to the legal compliance of each vehicle within the fleet.

16. The method of claim 15, wherein receiving data relating to the legal compliance status of each vehicle within the fleet comprises receiving legal compliance data generated by a fleet management module.

17. The method of claim 14, wherein the use condition relating to legal compliance is selected from the group of operating a vehicle on which inspection is overdue, operating an ineligible vehicle, operating a vehicle having an unpaid violation, operating a vehicle on which the driver information is not updated, operating a vehicle with an expired registration that was not renewed, and operating a vehicle housed in a state in which it is no longer registered.

18. The method of claim 14, wherein determining whether legal compliance exceptions have occurred comprises comparing the data relating to a use condition to the threshold value or range of threshold values representing a desired use condition, and generating an exception if the data does not match the threshold value or is not within the range of threshold values representing a desired use condition.

19. The method of claim 1, wherein if at least one exception is an unauthorized use exception, defining an unauthorized use exception comprises selecting a use condition relating to unauthorized use and defining a threshold value or a range of threshold values representing desired use.

20. The method of claim 19, wherein the use condition relating to unauthorized use is selected from the group of operating a vehicle outside of an authorized time frame, and operating a vehicle outside of an authorized area.

21. The method of claim 20, wherein, if the use condition is operating a vehicle outside of an authorized time frame, defining a threshold value or a range of threshold values representing desired use comprises receiving data relating to the schedule for each vehicle within the fleet that indicates the times of authorized use.

22. The method of claim 21, wherein receiving data relating to the schedule for each vehicle within the fleet comprises receiving schedule data generated by a scheduling module.

23. The method of claim 20, wherein, if the use condition is operating a vehicle outside of an authorized area, defining a threshold value or a range of threshold values representing desired use comprises receiving location data for each vehicle and receiving data relating to the planned routes for each vehicle within the fleet that indicates the authorized routes for each vehicle.

24. The method of claim 23, wherein receiving data relating to the planned routes for each vehicle within the fleet comprises receiving planned route data generated by a routing module.

25. The method of claim 19, wherein determining whether unauthorized use exceptions have occurred comprises comparing the data relating to a use condition to the threshold range of values representing a desired use condition, and generating an exception if the data does not match the threshold value or is not within the range of threshold values representing a desired use condition.

26. The method of claim 1, wherein the data received relating to the use of each vehicle is processed data.

27. A method for assessing the undesired use of vehicles within a fleet, comprising:

defining at least one safety exception, one maintenance exception, and one unauthorized use exception relating to the use of vehicles within the fleet;

receiving data relating to the use of each vehicle within the fleet;

applying the at least one safety exception, one maintenance exception, and one unauthorized use exception to the data for each vehicle and determining whether any defined exceptions have occurred;

determining a statistical metric representative of the undesired use of the vehicles within the fleet based upon the defined exceptions.

28. The method of claim 27, wherein the statistical metric comprises the percentage of vehicles within the fleet having a safety, maintenance, or unauthorized use exception over a predetermined period of time.

29. The method of claim 27, wherein the statistical metric comprises the percentage of safety, maintenance, and unauthorized use exceptions generated by all of the vehicles in the fleet out of the total number of safety or maintenance exceptions that could have been generated by all of the vehicles in the fleet.

30. The method of claim 27, wherein the statistical metric comprises the total number of safety, maintenance, and unauthorized use exceptions generated by each vehicle.

31. The method of claim 27,

wherein the safety exception relating to the use of vehicles within the fleet is a speed safety exception relating to operation of a vehicle at an undesired speed;

wherein defining a speed safety exception comprises defining a threshold value or a range of threshold values representing desired use; and

wherein the data received relating to the use of each vehicle includes data relating to speed;

wherein determining whether the speed safety exception has occurred comprises comparing the data relating to the speed of each vehicle to the threshold value or range of threshold values representing a desired use condition, and generating an exception if the data does not match the threshold value or is not within the range of threshold values representing a desired use.

32. The method of claim 27,

wherein the maintenance exception relating to the use of vehicles within the fleet is a check engine light exception related to operation of the vehicle while a check engine light is on in the vehicle;

wherein defining the check engine light maintenance exception comprises defining a threshold value or a range of threshold values representing desired use;

wherein the data received relating to the use of a vehicle includes data relating to the status of the check engine light in each vehicle and data relating to when each vehicle was used; and

wherein determining whether the check engine light maintenance exception has occurred comprises comparing the data relating to use of each vehicle with the check engine light on to the threshold value or range of threshold values representing a desired use condition, and generating an exception if the data does not match the threshold value or is not within the range of threshold values representing a desired use.

33. The method of claim 27,

wherein the unauthorized use exception relating to the use of vehicles within the fleet is an unauthorized time use exception related to operation of the vehicle outside of an authorized time;

wherein defining the unauthorized time use exception comprises defining a threshold value or a range of threshold values representing desired use;

wherein the data received relating to the use of a vehicle includes data relating to the time when each vehicle was used; and

wherein determining whether the unauthorized time use exception has occurred comprises comparing the data relating to the time of use of the vehicle to the threshold value or range of threshold values representing a desired use, and generating an exception if the data does not match the threshold value or is not within the range of threshold values representing a desired use.

34. The method of claim 33, defining a threshold value or a range of threshold values representing desired use comprises receiving data relating to the schedule for each vehicle within the fleet that indicates the times of authorized use.

35. The method of claim 34, wherein receiving data relating to the schedule for each vehicle within the fleet comprises receiving schedule data generated by a scheduling module.

36. A system comprising:

a mobile device on a vehicle configured to obtain raw data relating to use conditions on a vehicle and wirelessly transmit that raw data to a diagnostics server, wherein the diagnostics server processes the raw data and creates processed data relating to use conditions;

a data warehouse server configured to receive the processed data from the first server;

a processor configured to apply at least one exception selected from the group of safety exceptions, maintenance exceptions, unauthorized use exceptions, and legal compliance exceptions to the processed data, and further configured to determine a statistical metric representative of the undesired use of the vehicles within the fleet based upon the application of the exceptions.

37. The system of claim 36, further comprising, if the processor is configured to apply a safety exception to the processed data relating to the occurrence of accidents,

a fleet management module having accident information for each vehicle in a fleet, wherein the fleet management module is configured to provide the data warehouse server with data relating to accidents for each vehicle in the fleet for use by the processor in defining the safety exception.

38. The system of claim 36, further comprising, if the processor is configured to apply a maintenance exception to the processed data relating to operation of a vehicle for which scheduled maintenance is overdue,

a scheduling module having maintenance schedule information for each vehicle in a fleet, wherein the scheduling module is configured to provide the data warehouse with data relating to the maintenance schedule information for each vehicle in the fleet for use by the processor in defining the maintenance exception.

39. The system of claim 36, further comprising, if the processor is configured to apply a legal compliance exception to the processed data relating to the legal status of each vehicle,

a fleet management module having legal status information for each vehicle in a fleet, wherein the fleet management module is configured to provide the data warehouse with data relating to the legal status information for each vehicle in the fleet for use by the processor in defining the legal compliance exception.

40. The system of claim 36, further comprising, if the processor is configured to apply an unauthorized use exception to the processed data relating to operation of a vehicle outside of an authorized time frame,

a scheduling module having schedule information indicating the authorized time or times of use for each vehicle in the fleet, wherein the scheduling module is configured to provide the data warehouse with data relating to the schedule information for each vehicle in the fleet for use by the processor in defining the unauthorized use exception.

41. The system of claim 36, further comprising, if the processor is configured to apply an unauthorized use exception to the processed data relating to operation of a vehicle outside of an authorized route,

a routing module having route information indicating the authorized route for each vehicle in the fleet, wherein the routing module is configured to provide the data warehouse with data relating to the authorized route for each vehicle in the fleet for use by the processor in defining the unauthorized use exception.

42. A system comprising:

a mobile device on a vehicle configured to obtain raw data relating to use conditions on a vehicle and wirelessly transmit that raw data to a diagnostics server, wherein the diagnostics server processes the raw data and creates processed data relating to use conditions;

a data warehouse configured to receive the processed data from the diagnostics server;

a processor configured to apply at least one safety exception, one maintenance exception, and one unauthorized use exception to the processed data, and further configured to determine a statistical metric representative of the undesired use of the vehicles within the fleet based upon the application of the exceptions; and

a scheduling module having schedule information indicating the authorized time or times of use for each vehicle in the fleet, wherein the scheduling module is configured to provide the data warehouse with data relating to the schedule information for each vehicle in the fleet for use by the processor in defining the unauthorized use exception.