US20130164715A1 - Using social networking to improve driver performance based on industry sharing of driver performance data - Google Patents
Using social networking to improve driver performance based on industry sharing of driver performance data Download PDFInfo
- Publication number
- US20130164715A1 US20130164715A1 US13/725,886 US201213725886A US2013164715A1 US 20130164715 A1 US20130164715 A1 US 20130164715A1 US 201213725886 A US201213725886 A US 201213725886A US 2013164715 A1 US2013164715 A1 US 2013164715A1
- Authority
- US
- United States
- Prior art keywords
- vehicle
- data
- driver
- performance
- time
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0639—Performance analysis of employees; Performance analysis of enterprise or organisation operations
- G06Q10/06398—Performance of employee with respect to a job function
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
- G01S19/00—Satellite radio beacon positioning systems; Determining position, velocity or attitude using signals transmitted by such systems
- G01S19/01—Satellite radio beacon positioning systems transmitting time-stamped messages, e.g. GPS [Global Positioning System], GLONASS [Global Orbiting Navigation Satellite System] or GALILEO
- G01S19/13—Receivers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
- G06F16/24578—Query processing with adaptation to user needs using ranking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/02—Registering or indicating driving, working, idle, or waiting time only
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0816—Indicating performance data, e.g. occurrence of a malfunction
- G07C5/0825—Indicating performance data, e.g. occurrence of a malfunction using optical means
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09B—EDUCATIONAL OR DEMONSTRATION APPLIANCES; APPLIANCES FOR TEACHING, OR COMMUNICATING WITH, THE BLIND, DEAF OR MUTE; MODELS; PLANETARIA; GLOBES; MAPS; DIAGRAMS
- G09B19/00—Teaching not covered by other main groups of this subclass
- G09B19/14—Traffic procedures, e.g. traffic regulations
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09B—EDUCATIONAL OR DEMONSTRATION APPLIANCES; APPLIANCES FOR TEACHING, OR COMMUNICATING WITH, THE BLIND, DEAF OR MUTE; MODELS; PLANETARIA; GLOBES; MAPS; DIAGRAMS
- G09B19/00—Teaching not covered by other main groups of this subclass
- G09B19/16—Control of vehicles or other craft
- G09B19/167—Control of land vehicles
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09B—EDUCATIONAL OR DEMONSTRATION APPLIANCES; APPLIANCES FOR TEACHING, OR COMMUNICATING WITH, THE BLIND, DEAF OR MUTE; MODELS; PLANETARIA; GLOBES; MAPS; DIAGRAMS
- G09B9/00—Simulators for teaching or training purposes
- G09B9/02—Simulators for teaching or training purposes for teaching control of vehicles or other craft
- G09B9/04—Simulators for teaching or training purposes for teaching control of vehicles or other craft for teaching control of land vehicles
- G09B9/052—Simulators for teaching or training purposes for teaching control of vehicles or other craft for teaching control of land vehicles characterised by provision for recording or measuring trainee's performance
Definitions
- such tools can be used to provide feedback to drivers to enable the fleet operator to encourage driving habits leading to cost savings.
- Such a tool might thus be used to develop objective criteria that could be used encourage and provide incentives to drivers to improve their performance in operating the vehicles in a fleet.
- One aspect of the novel concepts presented herein is a method of producing a numerical ranking of a driver's performance based on a plurality of metrics (recognizing that the concepts disclosed herein also encompass the use of only a single metric), and then sharing those metrics on a hosted website, such that the drivers can compare their performance metrics to those of their peers. Fleet operators can use these performance metrics as incentives, by linking driver pay with performance.
- Such a method comprises the steps of automatically collecting a plurality of metrics while a driver is operating a vehicle, automatically determining a numerical value for each metric, automatically combining the numerical values for the plurality of metrics to achieve a numerical performance value, and normalizing the numerical performance value to achieve a numerical ranking of the driver's performance while operating a vehicle, and then posting the driver performance data to the hosted website.
- fleet operators will pay drivers using a mileage component (i.e., paying drivers a fixed rate per loaded mile), while also making additional payments to drivers meeting predefined performance characteristics.
- a mileage component i.e., paying drivers a fixed rate per loaded mile
- only drivers having top ranking performance metrics (such as drivers having performance scores in the top 10% of the fleet, or the 25 drivers having the best performance scores in the fleet, recognizing that such specific examples are not intended to be limiting) will be eligible for the performance pay.
- any driver in the fleet will be eligible for performance bonus pay once they have met a predefined performance metric.
- performance pay can be linked to specific performance metrics. For example, consider a fleet operator who has many routes involving mountainous terrain, and that fleet is experiencing excessing brake wear/failure over those routes. That operator may want to link performance pay to brake operating temperature for a period of time to induce drivers operating over those routes to pay more attention to brake temperature. Such a focused review of driver performance data for a defined period of time will be referred to herein and in the claims that follow as a campaign.
- the campaign can be designed to score drivers' performance in that campaign based only on the target metric (or metrics), such as brake temperature, or an existing normalized performance score can be modified so that the target metric (in this case, brake temperature) is more heavily weighted than normal.
- target metric or metrics
- brake temperature or an existing normalized performance score
- campaigns can be metric specific, or can be based on a single normalized score, but will generally share in common the characteristic of being implemented for a defined period of time.
- Drivers will learn to associate such campaigns with opportunities to increase their pay by meeting the performance goals of individual campaigns.
- campaign participants are limited to drivers in a specific fleet (i.e., an intra-company or intra-fleet campaign). In such embodiments, that fleet generally will be paying the performance bonuses for the campaign.
- campaign participants are not limited to drivers in only one specific fleet (i.e., an inter-company or inter-fleet campaign).
- a third party may be paying the performance bonuses for the campaign. For example, companies providing goods and services to the trucking or vehicle transportation industry may sponsor such a campaign for advertising purposes. A particular fleet operator seeking to attract the attention of drivers in other fleets might also be a sponsor of an inter-company campaign.
- the performance metric is designed to facilitate comparison of driver performance data across different fleets, and different vehicles. This will enable individual campaigns to include more participating drivers, which in turn will bring in more advertising revenue to fund bigger performance bonuses.
- a metric is mutually agreed upon by a plurality of different fleet operators. Adoption of a common performance metric across multiple fleets will enable top performing drivers to be able to show their cumulative performance scores to other participating fleet operators, providing an additional tool for fleets to use when evaluating potential new hires.
- Such a common performance metric will also enable participating fleet operators to appear more attractive as potential employers than non-participating fleet operators, who will not be offering the drivers the potential of earning the additional performance based income (i.e., income in addition to the industry standard pay by the mile driver compensation).
- the concepts disclosed herein encompass embodiments in which individual fleet operators host their own website, where driver rankings in that fleet can be compared.
- the website is hosted by a third party, and multiple fleet operators participate.
- the third party can offset their costs for operating the website by charging participating fleet operators a fee, and/or by advertising revenue.
- all driver performance data is displayed in an anonymous format, so that individual drivers cannot be identified unless the driver shares their user ID.
- drivers can only compare their score with drivers in their own fleet, while in other embodiments drivers can see the performance data of drivers in other fleets.
- the social networking/performance pay concepts disclosed herein can be implemented using driver performance metrics generated using different techniques, including techniques that do and do not rely on real-time transmission of performance data from participating vehicles to a remote data center. At least some of the concepts disclosed herein can be implanted using data recorders that store data for a period of time before conveying that data to a data center for generating the driver performance data.
- the performance metric is based at least in part from data collected from one or more engine control units (or vehicle computer(s)) in a vehicle operated by the driver whose performance is being measured.
- the performance metric is based at least in part on fuel economy.
- the performance metric is based at least in part on carbon footprint reduction.
- the performance metric is based at least in part on minimizing fuel efficiency robbing behavior, including sudden braking, rapid acceleration and downshifting too early.
- the performance metric is based at least in part on maximizing fuel efficiency enhancing behavior, including coasting to a stop (instead of staying on the accelerator until the last minute and then braking hard), driving at high average vehicle speeds with minimum time spent at maximum vehicle speed, driving in such a manner so as to achieve a high percent trip distance in top gear (90+% recommended), driving in such a manner so as to achieve a high percent distance in cruise control, driving in such a manner so as to achieve a minimum percent idle/PTO operation, driving in such a manner so as to achieve a minimum service brake activity, driving in such a manner so as to achieve a relatively low number of sudden decelerations, and driving in such a manner so as to achieve a relatively low number of service brake actuations/1000 miles.
- the commonly adopted performance metric is based on the amount of vehicle work performed.
- such a metric includes using vehicle position derived slope data to determine a vehicle's mass at a plurality of different times during the operation of a vehicle, and then using the mass to calculate work.
- the vehicle position data is generated by a position sensing system including a component (such as a receiver) disposed in the vehicle.
- An exemplary position sensing system is the Global Positioning System (GPS).
- GPS Global Positioning System
- the GPS system is a space-based satellite navigation system that provides location and time information in all weather, anywhere on or near the Earth, where there is an unobstructed line of sight to four or more GPS satellites. It is maintained by the United States government and is freely accessible to anyone with a GPS receiver.
- GPS Global Navigation Satellite System
- GLONASS Russian Global Navigation Satellite System
- Galileo positioning system the Chinese Compass navigation system
- Indian Regional Navigational Satellite System the concepts disclosed herein can be implemented using different types of vehicle position sensing systems, such as the Russian Global Navigation Satellite System (GLONASS), the planned European Union Galileo positioning system, the Chinese Compass navigation system, and the Indian Regional Navigational Satellite System, and similar such systems as they are developed.
- the concepts disclosed herein can also be implemented by relying on basic triangulation of signals received from terrestrial based transmitters (such as cell towers), should sufficient transmitters be available (and should the vehicle position resolution obtainable using such technology be generally comparable with that available from satellite based systems).
- GPS systems calculate velocity in three components (X, Y, Z or N/S, E/W, and Up/Down) based on a Doppler shift of the GPS satellite signals.
- Scalar speeds can then be calculated from those three components. For example, absolute speed or actual vehicle speed can be determined, as well as ground speed based on the shortest distance between two points (i.e., based on distance as the crow flies).
- Horizontal ground speed (V HGS ) can be calculated using the Pythagorean Theorem. To calculate a grade (G) the vehicle is traveling over (as a percentage), one can take the Z/Up magnitude and divide it by the horizontal ground speed.
- each one of the plurality of metrics will correspond to a different aspect of the driver's performance while operating a vehicle.
- a number of different types of sensors are commonly integrated into commercial, passenger, and fleet vehicles. Such sensors can readily collect a wide variety of operational data that are related to driver performance. For example, one such metric is idle time of a vehicle. Excessive idling time generates increased emissions, increased fuel consumption, and increased engine wear. From the point of view of the fleet operator, drivers who operate vehicles so as to incur relatively greater idle times exhibit a lower performance compared to drivers who do so while incurring relatively less idle time.
- Additional performance metrics related to both vehicle and driver performance include the amount of time the vehicle is accelerating during the operation of the vehicle by the driver, the extent of such acceleration, the amount of time the vehicle is decelerating during the operation of the vehicle by the driver, the extent of deceleration, whether (or how often) a driver deviates from a predefined route, and whether (or how often and to what extent) a driver exceeds a speed limit.
- Drivers who accelerate and decelerate often and accelerate or brake excessively are likely to increase fuel consumption, emissions, engine and/or brake wear, as compared to drivers who are more able to accelerate and decelerate modestly, and who are more able to maintain a constant speed.
- a single numerical score or numerical ranking can be used to provide feedback to individual drivers.
- Such a numerical ranking can be used as a management tool to improve driver performance.
- drivers with relatively poor numerical ranking scores can receive counseling or warnings, which should lead to an improvement in their performance, while drivers receiving relatively better scores receive praise or bonuses that encourage them and others to maintain or improve good performance in operating a vehicle. Comparing such scores across companies or between individual branches of a company can be used as a contest or as a motivational tool, where drivers with relatively better scores earn prizes or public praise.
- a fleet operator could regularly post a list of driver performance rankings in company break rooms, so that drivers can compare their individual performance rankings with one another (note the concepts disclosed herein also encompass posting such scores on a website).
- a numerical value will be determined for that metric.
- Different metrics can be weighted differently, according to the preference of the fleet operator. For example, if a fleet operator is particularly concerned about reducing excessive idle time, but is less concerned about drivers' acceleration and deceleration habits, idle time can weighted more significantly, to have a greater effect on the numerical ranking determined for the drivers than acceleration and deceleration metrics. Thus, in that case, increased idle time will have a greater proportional negative effect on a driver's overall score, than will excessive acceleration and deceleration of a vehicle.
- Normalizing the combined numerical scores for each metric is important; as such normalization enables the numerical rankings for different drivers to be compared.
- the normalization is based on dividing the combined rankings by the distance over which the driver has operated the vehicle. For example, the drivers' combined numerical values for each metric can be divided by the number of miles over which the driver has operated vehicle.
- the normalization is based on dividing the combined rankings by the length of time the driver has operated a vehicle. For example, a driver's combined numerical values for each metric can be divided by the number of hours the driver has operated a vehicle.
- valuation paradigms can be implemented for determining a numerical value for each metric. Under some paradigms, a relatively higher normalized combined total will represent relatively better driver performance, while under other paradigms a relatively lower normalized combined total will represent relatively better driver performance.
- the specific valuation paradigm employed is less important than the aspect of the present invention directed to providing a numerical value that can be used to evaluate driver performance, where the numerical value is based on measurable metrics corresponding to a driver's performance while operating a vehicle.
- the concepts presented herein can be applied to other types of equipment, such as heavy machinery and heavy construction equipment (backhoes, excavators, bulldozers, etc.), as well as to other types of equipment or machinery that an operator controls, so long as the various aspects of the operator's performance can be sensed and the results used to determine a numerical value representative of the overall quality with which the operator controls the equipment or machinery. It should also be recognized that the concepts provided herein can also be beneficially implemented in other types of vehicles, including automobiles (such as rental car fleets, government vehicles, and fleet vehicles assigned to sales representatives or other employees of a business).
- one of the metrics that can be beneficially employed relates to determining if a driver has deviated from a predefined route.
- This metric can be automatically determined by providing predefined route data comprising geographical coordinates, automatically collecting geographical coordinate data while the driver is operating the vehicle (for example using a global positioning satellite (GPS) receiver), and determining if the driver has deviated from the predefined route by comparing the collected geographical coordinate data with the predefined route data.
- GPS global positioning satellite
- Yet another metric that can be beneficially employed relates to determining whether a driver has exceeded a speed limit, which can be automatically determined in several different fashions.
- it can be determined if a driver has violated the speed limit by providing a baseline speed limit value (such as 60 miles an hour, for vehicles primarily operated on freeways), automatically collecting vehicle speed data while the driver is operating the vehicle on freeways, and determining if the driver has deviated from the baseline speed limit value by comparing the collected vehicle speed data with the baseline speed limit value (or distance traveled per unit time).
- a baseline speed limit value such as 60 miles an hour, for vehicles primarily operated on freeways
- the step of determining if the driver has violated the speed limit comprises the steps of providing predefined route data comprising geographical coordinates and speed limits associated with each geographical coordinate, automatically collecting geographical coordinate data and vehicle speed data while the driver is operating the vehicle, and determining if the driver has violated the speed limit by comparing the collected geographical coordinate data and vehicle speed data with the predefined route data for which the speed limit is specified at different portions of the route.
- the steps of collecting the plurality of metrics and processing the plurality of metrics to determine the numerical ranking of the driver's performance can be implemented in physically different locations.
- the plurality of metrics are automatically collected by the vehicle, and then transmitted to a remote computing device for processing.
- the metrics can be transmitted to the remote computing device in real-time, or can be saved in a memory in the vehicle and later transmitted to the remote computing device for processing, for example, when the vehicle is returned to a central garaging facility.
- processing of the plurality of the metrics occurs within the vehicle. Where the processing of the plurality of metrics occurs within the vehicle, the driver's current performance ranking can be displayed in real-time to the driver to provide immediate feedback to help the driver improve performance while operating a vehicle.
- This approach would be analogous to providing real-time fuel mileage estimates to a driver based on current vehicle operating conditions. Providing drivers with feedback in real-time will enable drivers to correct driving habits while operating the vehicle, leading to an improved performance ranking In such an embodiment, it would be desirable to enable the driver to review the metrics responsible for decreasing a driver's performance ranking. For example, if the driver's current performance ranking is relatively low because the driver is frequently accelerating and decelerating, rather than maintaining a constant speed, the display provided to the driver can be customized to indicate the specific metrics responsible for the lower than desired performance ranking.
- FIG. 1 is a high level flow chart showing the overall method steps implemented in accord with one exemplary embodiment for achieving the concepts disclosed herein;
- FIG. 2 is a more detailed flow chart showing method steps implemented in an exemplary preferred embodiment
- FIG. 3 schematically illustrates a vehicle that includes a plurality of sensors configured to collect the required metrics
- FIG. 4A is a functional block diagram illustrating the functional elements of an embodiment in which the metrics are processed within the vehicle to obtain the driver's performance ranking, for example, in real-time;
- FIG. 4B is a functional block diagram illustrating the functional elements of an embodiment in which the metrics are processed by a computing device remote from the vehicle to obtain the driver's performance ranking;
- FIG. 5 schematically illustrates the interior of a vehicle configured with a display to provide the driver with the performance ranking in real-time;
- FIG. 6 schematically illustrates a vehicle that includes a GPS unit configured to collect GPS data that can be used to provide a plurality of metrics for use in determining a driver performance ranking in accord with one aspect of the concepts disclosed herein;
- FIG. 7 is a flow chart showing method steps implemented in an exemplary preferred embodiment, where GPS data are used to provide a plurality of metrics used to determine the driver's performance ranking;
- FIG. 8 is a flow chart showing method steps implemented in accord with one aspect of the concepts disclosed herein, the method steps representing an exemplary technique used to implement that aspect, the aspect comprising using GPS or position data are used to determine a slope the vehicle is traveling over (in at least one embodiment, the slope data will in turn be used to calculate an accurate vehicle mass metric);
- FIG. 9 is a functional block diagram graphically illustrating force vectors acting on a vehicle, and how those vector can be used to solve for vehicle mass, where the GPS derived slope represents a unique metric;
- FIG. 10 is a flow chart showing exemplary method steps implemented according to one aspect of the concepts disclosed herein, where GPS or position derived slope data is used to calculate a vehicle's mass at a plurality of intervals during the operation of a vehicle, and then using the vehicle mass to determine a cost per loaded mile;
- FIGS. 11A-11C graphically illustrate vehicle performance histograms generated derived in part using the GPS derived slope data of FIG. 8 ;
- FIGS. 12A-12B graphically illustrate vehicle performance histograms generated derived in part using the GPS derived slope data
- FIG. 13 is a flow chart showing exemplary method steps implemented according to one aspect of the concepts disclosed herein, in which a promotional driver performance campaign is implemented at a hosted website;
- FIGS. 14 and 15 are functional blocks diagram illustrating that the promotional driver performance campaigns and bonuses of the method of FIG. 13 can include drivers from a single fleet (intra-company) or drivers from multiple fleets (inter-company);
- FIG. 16 is a functional block diagram illustrating exemplary elements in a vehicle/driver performance monitoring system in accord with one aspect of the concepts disclosed herein;
- FIG. 17 is an exemplary screen shot of a website hosting a promotional driver performance campaign
- FIG. 18 is a another functional block diagram illustrating exemplary elements in a vehicle/driver performance monitoring system in accord with one aspect of the concepts disclosed herein;
- FIG. 19 is an exemplary computing environment for implementing some of the concepts disclosed herein.
- FIG. 20 is a functional block diagram of an exemplary telematics device added to an enrolled vehicle to implement one or more of the methods of FIGS. 1 , 2 , 7 , 8 and 10 .
- FIG. 1 is a high level flow chart showing the overall method steps implemented in accord with one aspect of the concepts disclosed herein.
- a plurality of metrics related to driver performance are automatically collected by a plurality of sensors incorporated into a vehicle.
- Such metrics generally relate to driver operation of the vehicle, but may also simply include data related to the vehicle.
- Such metrics can include, but are not limited to, vehicle speed, vehicle acceleration, vehicle deceleration, engine RPMs, idle time, engine temperature, coolant temperature, oil temperature, fuel consumption, and vehicle positional data.
- Those of ordinary skill in the art will readily recognize that many different metrics related to vehicle performance and driver performance can be collected. Thus, it should be recognized that the specifically identified metrics are intended to be exemplary, rather than limiting.
- a numerical ranking of the driver's performance is determined based on at least some of the metrics collected.
- FIG. 2 is a more detailed flow chart showing method steps implemented in a preferred embodiment, providing additional details as to how the numerical ranking of the driver's performance can be determined.
- a numerical value is assigned to each metric collected. It should be recognized that plurality of valuation schemes can be implemented, and the specific scheme implemented is not critical. It should also be recognized that a fleet operator can perceive some metrics to be more or less important to overall driver performance. Thus, individual metrics can be weighted differently. For example, one fleet operator may have little tolerance for drivers who exceed posted speed limits and want to place great emphasis on this metric when determining the numerical ranking. Such a fleet operator can assign significantly more weight to the detection of a driver exceeding a speed limit than to the detection of a driver incurring excessive idle time.
- a numerical ranking will be determined for each metric collected.
- the numerical rankings for each metric are combined.
- the combined numerical values for each metric are normalized, to enable performance rankings for different drivers to be more equitably compared.
- the normalization is based on a distance over which a driver has operated a vehicle.
- the normalization is based on an amount of time the driver has operated a vehicle. This normalization enables the output of the normalized combined total to be provided as a numerical ranking in a block 20 indicating a driver's performance.
- the valuation scheme implemented will determine whether a specific numerical value is indicative of a relatively good performance or a relatively poor performance. Under some valuation schemes, relatively higher combined and normalized numerical rankings are generally indicative of relatively better driver performance. In other valuation schemes, relatively lower combined and normalized numerical rankings are generally indicative of relatively better driver performance.
- FIG. 3 schematically illustrates a vehicle including a plurality of sensors configured to collect the required metrics.
- a vehicle 22 such as a bus or a truck, includes a plurality of sensors 24 a - 24 h .
- the specific number of sensors, and the specific types of sensors and types of data collected by the sensors are not critical, so long as the sensors collect data for the desired metrics.
- a plurality of different metrics have been specifically identified, however it should be recognized that such metrics are intended to be exemplary, and not limiting on the concepts disclosed herein.
- each sensor is coupled to a CPU 26 (which, as described in greater detail below, may in some of embodiments be replaced with (or provided in addition to) a transmitter).
- FIG. 4A is a functional block diagram 28 a illustrating the functional elements of an exemplary embodiment in which the metrics are processed within the vehicle to obtain the driver's performance ranking.
- the vehicle is equipped with sensors 30 configured to collect the required metrics.
- the sensors are logically coupled with an onboard vehicle CPU 34 , which is configured to implement the method steps generally described above.
- CPU 34 is logically coupled to a memory 32 in which are stored the machine instructions that are executed by the CPU to carry out these logical steps.
- the plurality of metrics collected by sensors 30 can also be stored in memory 32 .
- a (preferably optical or wireless) transmitter 36 (or other data link) can be included to enable either the plurality of metrics or the driver's performance ranking to be communicated to a remote computing device.
- An optional display 38 can be included in the vehicle to provide real-time feedback to the driver (by displaying the driver's performance ranking in real-time). As discussed above, if display 38 is implemented, it is desirable to provide the ability for the driver to determine which metrics are having the most impact on the driver's performance ranking.
- FIG. 4B is a functional block diagram 28 b illustrating the functional elements of an exemplary embodiment in which the metrics are processed by a computing device to obtain the driver's performance ranking, where the computing device is remote from the vehicle.
- the vehicle is equipped with sensors 30 configured to collect the required metrics.
- the sensors are logically coupled with an onboard vehicle CPU 34 , which is configured to transmit the collected metrics to remote computing device 39 through transmitter 36 (or other data link)
- transmitter 36 is a wireless transmitter.
- the method steps generally described above for processing the collected metrics can be executed by the remote computing device.
- CPU 34 is logically coupled to memory 32 in which the collected metrics can be stored, if the metrics are not to be transmitted to the remote computing device in real-time.
- the metrics are transmitted to the remote computing device in real-time, such metrics can be stored in memory 32 as a backup in case the transmission is not successful.
- a display is not likely to be beneficial, unless the remote computing device is configured to transmit the calculated performance ranking back to the vehicle for display to the driver.
- FIG. 5 schematically illustrates the interior of a vehicle configured with a display 40 to provide the driver with a performance ranking in real-time.
- a display can be implemented by the embodiment schematically illustrated in FIG. 4A .
- FIG. 5 shows a single numerical performance ranking being dis-played, it should be understood that the concepts disclosed herein encompass displaying a plurality of different metrics (at one or in rotation), as well as displaying a cost per loaded mile metric, which is discussed in detail below in connection with FIG. 10 .
- the cost per loaded mile metric can be calculated using the concepts disclosed herein at a remote computing device and conveyed back to the vehicle for display, or can be calculated using a processor in the vehicle.
- FIG. 6 schematically illustrates a vehicle 22 a that includes a GPS unit 44 configured to collect GPS data that can be used to determine a plurality of metrics for use in determining a driver performance ranking.
- a GPS unit 44 configured to collect GPS data that can be used to determine a plurality of metrics for use in determining a driver performance ranking.
- Vehicle 22 a such as a bus or a truck (or automobile, or construction equipment, generally as described above) includes GPS unit 44 coupled with an ignition system 42 of the vehicle.
- the GPS unit will be coupled with the ignition switch, such that it is assumed that when the ignition switch is on, the engine of the vehicle is actually running, and the GPS unit will be activated.
- GPS data can be used for a plurality of metrics, including idle time, deceleration time and magnitude, acceleration time and magnitude, and to determine if a driver has violated a speed limit.
- the most basic GPS unit is able to determine a position of the vehicle at a specific time. That positional information can be used to calculate the speed of a vehicle by determining the change in position of the vehicle between two successive points in time, and to calculate the acceleration or deceleration of the vehicle by determining the change in speed of the vehicle over a time increment. More typically, GPS units automatically determine position, speed, and acceleration/deceleration internally, and these metrics would then not need to be determined by an external computing device (remote or local).
- GPS unit 44 preferably includes or is connected to a wireless transmitter (not separately shown), such that the GPS data can be wirelessly transmitted to a remote computing device, preferably in real-time.
- the remote computing device can be programmed to manipulate the GPS data to determine a plurality of metrics, which can then be used to calculate a driver's performance ranking, generally as described above.
- GPS unit 44 can include an onboard memory, such that the GPS data are stored in the GPS unit, to be uploaded to a remote computing device at a later time (for example, using a wireless or hardwired data link)
- GPS unit 44 enables driver performance rankings to be determined, even if the vehicle is not equipped with separate other sensors of the metric data or an onboard computer (as are required in the embodiments of FIGS. 3 , 4 A, and 4 B).
- the concepts disclosed herein encompasses coupling such a GPS unit to vehicle sensors and/or a vehicle data bus, such that driver/vehicle performance data collected by other vehicle sensors can be combined with GPS data and conveyed to a remote computing site. While not specifically shown in FIG.
- GPS unit 44 can include a processor that uses GPS data and sensor data collected from the vehicle to calculate performance metrics, which are then combined with GPS data and conveyed to the remote computing site.
- One such metric is GPS derived slope data, discussed in detail in below in connection with FIG. 8 .
- Such performance metrics calculated by a processor in the vehicle can be displayed in the vehicle, as well as (or in lieu of) being conveyed to a remote computing device.
- FIG. 7 is a flow chart showing method steps implemented in one exemplary embodiment when GPS data are used to calculate a plurality of metrics used to determine the driver's performance ranking.
- the vehicle ignition is switched on (and it is assumed that the engine is running), thereby powering on the GPS unit.
- the GPS unit collects GPS data (information corresponding both to a particular point in time and a specific geographical position that the vehicle occupies at that specific point in time).
- the GPS data are transmitted to a remote computing device. As noted above, the GPS data are preferably transmitted to the remote computing device in real-time.
- the GPS data can be temporarily stored within the GPS unit (or in a memory electronically coupled to the GPS unit), and transferred to the remote computing device at a later time.
- the remote computing device uses the GPS data to calculate an idle time metric. Because the GPS unit is only on when the ignition switch is on and the engine of the vehicle is assumed to be running, an assumption can be made that the idle time equals the accumulated time that the GPS unit is on, but the vehicle is not changing position.
- the remote computing device uses the GPS data to determine metrics corresponding to acceleration time and acceleration magnitude.
- the remote computing device uses the GPS data to determine metrics corresponding to deceleration time and deceleration magnitude.
- the remote computing device uses the GPS data to determine whether a driver has exceeded a speed limit.
- mapping databases include a database of speed limits and which enable a speed limit for a specific portion of a route being driven by a vehicle to be determined based on a particular geographical coordinate of the vehicle following that route.
- GPS data includes an indication of the speed of the vehicle at a particular time while the vehicle is at a particular geographical location.
- a database can be consulted to determine the speed limit associated with that position along the route, thereby enabling a determination to be made as to whether the driver has exceeded the speed limit.
- the plurality of metrics calculated from the GPS data are used to determine the driver's performance ranking, generally as described above in connection with FIGS. 1 and 2 .
- the GPS data can be used to calculate fewer metrics than those described above in connection with FIG. 7 , and that the metrics specifically identified in FIG. 7 are intended to be exemplary, rather than limiting.
- the sensor data can also be forwarded to the remote computing device to be used in calculating the driver's performance ranking, also generally as described above.
- the GPS data can be conveyed to a computing device on the vehicle, for determining the driver's performance ranking.
- performance rankings are determined for each driver in a company (or each driver of a vehicle for which driver performance is of interest), and posted publicly so that drivers can compare each other's individual performance rankings.
- the public display of driver performance is expected to provide an incentive for drivers to improve their driving performance rankings.
- the concepts disclosed herein encompass many differ types of performance metrics, and different techniques for collecting them.
- the performance metrics are transmitted from the vehicle to a remote computing device by a wireless data link enabled GPS unit (such as a GSM/GPS), that also collects location data during the vehicle's operation.
- a wireless data link enabled GPS unit such as a GSM/GPS
- performance metrics can also be collected using a data recorder that does not have wireless data transmission capability, such that data will need to be exported from the data recorder to a remote computing device periodically, or the data recorder will need to be removed from the vehicle and coupled to a computing device periodically to export the data used to calculate the driver performance metric(s).
- the performance metric is based at least in part from data collected from one or more engine control units (or vehicle computer) in a vehicle operated by the driver whose performance is being measured.
- the performance metric is based at least in part on fuel economy.
- the performance metric is based at least in part on carbon footprint reduction.
- the performance metric is based at least in part on minimizing fuel efficiency robbing behavior, including sudden braking, rapid acceleration and downshifting too early.
- the performance metric is based at least in part on maximizing fuel efficiency enhancing behavior, including coasting to a stop (instead of staying on the accelerator until the last minute and then braking hard), high average vehicle speeds with minimum time spent at maximum vehicle speed, high percent trip distance in top gear (90+% recommended), high percent distance in cruise control, minimum percent idle/PTO operation, minimum service brake activity, low number of sudden decelerations, and low service brake actuation's/1000 miles.
- Another aspect of the concepts disclosed herein is a technique to monitor vehicle location data (i.e. GPS data) over time to determine the actual operating speed of a fleet vehicle.
- vehicle location data i.e. GPS data
- Many fleet operators have the ability to define maximum speed parameters on their vehicles.
- Maximum speed parameters are defined to enhance safety and to reduce fuel costs (statistics indicated that for heavy trucks every MPH over 62 MPH reduces fuel economy by 0.1 MPG).
- these speed settings can fail due to maintenance issues, or driver manipulations.
- the maximum speed setting is based on understanding the size of the vehicle's tires. If during maintenance a different size tire is used as a replacement, the predefined speed settings will be inaccurate.
- the concepts disclosed herein encompass collecting GPS data during the operation of a fleet vehicle, and analyzing the location and time parameters of that data to identify when a fleet vehicle exceeds a predefined maximum speed.
- the GPS verified speed metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- Another aspect of the concepts disclosed herein is to monitor manual overrides for cooling fans in fleet vehicles.
- Such cooling fans generally controlled by a vehicle engine control unit (ECU) or vehicle computer, consume up to 50-70HP, and measurably reduce fuel economy.
- Drivers who habitually override the automatic fan settings can consume unnecessary amounts of fuel.
- the cooling fan manual override metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- Another aspect of the concepts disclosed herein is to monitor engine RPMs during a driver's operation of a vehicle. Over revving an engine can lead to increased fuel use and engine wear. Drivers who habitually over rev their vehicles engines can consume unnecessary amounts of fuel. Thus the concepts disclosed herein encompass monitoring the RPM parameters while a driver operates a vehicle, to facilitate an evaluation of a driver's performance, and to enable drivers who consistently over rev their vehicle's engines to be identified and trained to reduce their over revving behavior.
- the over revving metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- Another aspect of the concepts disclosed herein is to monitor the shifting behavior during a driver's operation of a vehicle. Not running a heavy truck in the highest possible gear when possible can lead to increased fuel use and engine wear. Statistics indicate that every 10% drop of time in top gear results in a 0.5% MPG loss.
- the shifting pattern metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- Another aspect of the concepts disclosed herein is to monitor the amount if idle time during a driver's operation of a vehicle. Increased idle time leads to increased fuel use and engine wear.
- the concepts disclosed herein encompass monitoring idle time behavior while a driver operates a vehicle, to facilitate an evaluation of a driver's performance, and to enable drivers who excessively allow their vehicle to idle to be identified and trained to reduce their excess idle behavior.
- the excessive idle metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- Another aspect of the concepts disclosed herein is to monitor a load placed upon a vehicle's engine during a driver's operation of a vehicle. While related to RPM, load is not equivalent.
- An estimation of engine load is sometimes calculated by a vehicle ECU, and different manufacturers use different combinations of parameters to calculate engine load, including but not limited to throttle position, RPM, manifold pressure, air flow, temperature, air conditioning clutch status, power steering pressure, and transmission gear status.
- engine load is increased without performing more useful work (i.e., carrying more cargo), increased fuel use and engine wear result without a net benefit.
- Drivers who habitually operate their vehicles under higher engine loads than required consume unnecessary amounts of fuel.
- the concepts disclosed herein encompass monitoring engine load while a driver operates a vehicle, to facilitate an evaluation of a driver's performance, and to enable drivers who consistently over load their vehicle's engines to be identified and trained to reduce their over loading behavior.
- the engine load metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- a relatively higher numerical ranking value is generally indicative of relatively poorer driver performance.
- the lower the numerical performance ranking the better the driver's performance.
- the sensor data are collected for various metrics corresponding to vehicle acceleration, vehicle deceleration, vehicle idle time, and vehicle speed.
- Each minute of acceleration time will be assigned one point.
- Each minute of deceleration time will be assigned one point.
- Each minute of idle time will be assigned one point.
- the fleet operator is also particularly concerned with drivers who violate speed limits on the freeway. Thus, each minute where the vehicle speed exceeds 60 miles an hour while the driver is driving the vehicle on the freeway will result in five points (the fleet operator weighting excessive vehicle speed five times greater than the other metrics).
- the points are added together to achieve a combined total.
- the total is then normalized to derive a numerical ranking value for the driver.
- the normalization can be based on either distance driven or time of operation, or a combination thereof.
- the concepts disclosed herein encompass using data collected during the operation of a vehicle to calculate a weight of the vehicle, and then using the calculated weight in a performance analysis of the vehicle.
- the novel vehicle weight calculation disclosed herein employs in part vehicle position data collected while a vehicle is moving.
- the position metric can be automatically determined using a global positioning satellite (GPS) receiver installed in the vehicle, to track the vehicle's change in position over time.
- GPS global positioning satellite
- GPS systems calculate velocity in three components (X, Y, Z or N/S, E/W, and Up/Down) based on a Doppler shift of the GPS satellite signals.
- Scalar speeds can then be calculated from those three components. For example, absolute speed or actual vehicle speed can be determined, as well as ground speed based on the shortest distance between two points (i.e., based on distance as the crow flies).
- V HGS Horizontal ground speed
- V HGS ⁇ square root over ( x 2 +y 2 ) ⁇ (1)
- Mass is a useful metric that can be used as a feedback metric for controlling certain vehicle systems.
- Some vehicle engine control units ECUs
- ECUs use torque output, engine RPMs, and vehicle velocity (noting that scalar vehicle speed can be used for velocity) to calculate a vehicle's mass or weight (as used herein and in the claims that follow, the terms mass and weight are used synonymously, because on the surface of the Earth, the acceleration due to gravity (the “strength of gravity”) is approximately constant; thus the ratio of the weight force of a motionless object on the surface of the Earth to its mass is almost independent of its location, so that an object's weight force can stand as a proxy for its mass, and vice versa).
- That ECU weight/mass determination technique is error prone, because it does not take into account any slope conditions. Even though the ECU weight/mass determination technique is error prone, the ECU weight/mass determination technique mass estimation provides a metric that can be used to as a feedback metric for various vehicle systems, including transmission shift points, engine RPM control, and emission controls. Having more accurate mass metrics (by including the GPS derived slope data in a mass calculation) will provide an improved mass metric.
- the concepts disclosed herein specifically encompass a GPS unit configured to use GPS data to calculate slope, to use the slope data and other vehicle parameters to determine vehicle mass (generally as discussed below), and then to provide a GPS slope based vehicle mass metric to a vehicle ECU to be used as a metric to control vehicle operation.
- Vehicle mass can also be used as an analytical metric to determine how much work a vehicle has performed. Being able to accurately determine the amount of work a vehicle performs will help vehicle operators analyze their use patterns to seek out efficiency improvements.
- the GPS derived slope data enables more accurate vehicle mass calculations to be determined, which in turn will provide an improved vehicle performance data set that can be mined to identify areas in which efficiency improvements could be made.
- Vehicle speed is a scalar quantity; whereas velocity is a vector (velocity is the rate of change of the position of an object, equivalent to a specification of its speed and direction of motion). In other words, speed describes only how fast an object is moving; whereas velocity gives both how fast and in what direction the object is moving.
- position data such as GPS data
- position data changing over time provides three-dimensional vectors (speed and direction) that can be used to derive slope, generally as discussed above.
- Vehicle speed (which in the terms of vehicle arts is often inaccurately referred to as velocity) is generally available in the vehicle from a vehicle ECU or speed sensor (most over the road vehicles, such as trucks and buses, are equipped with relatively accurate speed sensors). While the GPS unit can be used to determine vehicle speed by tracking changes in position over time, in general the resolution of vehicle speed measurements taken from vehicle speed sensors is greater than a resolution of vehicle speed derived from changes in GPS data over time (or other position data), and thus the use of vehicle speed data from vehicle speed sensors is quite useful for the following mass determination techniques.
- a first force opposing a motion of the vehicle relates to a grade or slope the vehicle is traveling over, which can be defined using the relationship of Equation (4).
- m vehicle mass and g is the local gravitational field (i.e., Earth's gravity).
- a second force opposing a motion of the vehicle relates to aerodynamic forces acting on the vehicle, which can be defined using the relationship of Equation (5).
- ⁇ air density
- C d the coefficient of drag of the vehicle
- A the frontal area of the vehicle
- ⁇ the vehicle velocity (which can be obtained from the vehicle data bus as speed or from GPS data).
- a third force opposing a motion of the vehicle relates to frictional forces acting on the vehicle, which can be defined using the relationship of Equation (6).
- C rr is the coefficient of rolling resistance of the vehicle (which is assumed to be constant)
- m is vehicle mass
- g is the local gravitational field (i.e., Earth's gravity)
- G is the slope, which is calculated using the GPS data as discussed above.
- the force generated by the vehicle to overcome these opposing forces can be defined using the relationship of Equation (7).
- ⁇ is engine output torque (as measured at the vehicle by vehicle sensors/reported by the vehicle data bus)
- N is engine RIVIPs (as measured at the vehicle by vehicle sensors/reported by the vehicle data bus)
- ⁇ is the vehicle velocity (which can be obtained from the vehicle data bus or from GPS data)
- ⁇ is the mathematical constant defined as the ratio of any circle's circumference to its diameter
- r is the radius of the vehicles tires.
- Vehicle mass is a parameter in the grade and frictional force relationships, of Equations (4) and (6), respectively.
- the mass parameter itself can be defined using the relationship of Equation (8).
- ⁇ is acceleration (which can be obtained from the vehicle data bus or from GPS data). In an exemplary embodiment, acceleration is obtained from the vehicle sensors.
- Equations (4)-(8) can be solved to obtain mass, as defined using the relationship of Equation (9).
- velocity or speed
- torque or speed
- RPM speed
- Velocity (or speed), torque, and RPM represent metrics that many vehicles already measure during vehicle operation, and thus can be accessed by tapping into a vehicle ECU or data bus.
- the concepts disclosed herein specifically encompass a GPS unit (or other position sensing unit) including a data port coupled to a vehicle ECU/data bus and a processor configured to calculate a GPS derived slope metric (generally as discussed herein) and a vehicle mass metric (generally as discussed herein, using in part the GPS derived slope data).
- a GPS unit or other position sensing unit
- a processor configured to calculate a GPS derived slope metric (generally as discussed herein) and a vehicle mass metric (generally as discussed herein, using in part the GPS derived slope data).
- the work metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- FIG. 8 is a flow chart showing method steps implemented in an exemplary embodiment, where position data (such as GPS data) collected during the operation of a vehicle is used to determine a slope or grade over which the vehicle is being operated. That grade then can be used to calculate other data, such as a weight or mass of the vehicle.
- position data such as GPS data
- That grade then can be used to calculate other data, such as a weight or mass of the vehicle.
- three dimensional position data (longitude, latitude and elevation) is collected during vehicle operation.
- that data is conveyed from the vehicle to a remote computing site (i.e., a monitoring/data storage location) in real-time.
- the position data is stored in a memory in the vehicle, to be conveyed to a remote computing site at a later time.
- the position data is used to determine horizontal ground speed, using the relationship of Equation (1).
- the horizontal ground speed (from the GPS data) and the Z-axis position data is used to determine the slope or grade, using the relationships of Equations (2) and (3).
- the slope data is used to calculate a mass of the vehicle, using the relationship of Equation (9).
- the data processing of blocks 122 , 124 , and 126 are performed by a remote computing device.
- the concepts disclosed herein encompass embodiments where some or all of the data processing of blocks 122 , 124 , and 126 are performed by a processor or logic circuit in the vehicle.
- the mass parameter is used by an ECU in the vehicle to control operating parameters of the vehicle.
- vehicle mass can be used as a feedback parameter for controlling vehicle operations, including engine speed (RPM), transmission gear selection, and fuel flow/mixture (to control vehicle emissions). While using vehicle mass data used as a feedback parameter for controlling vehicle operations has been implemented before, those implementations have not used GPS derived slope data as a parameter to determine vehicle mass.
- FIG. 9 graphically illustrates force vectors acting on a vehicle, including a frictional force, an aerodynamic force, a grade/slope related force, and a vehicle applied force used to overcome the opposing forces.
- the forces are discussed above in connection with Equations (4)-(7), and those relationships can be used to use GPS derived slope data to calculate vehicle mass, as shown in Equation (9).
- FIG. 10 is a flow chart showing method steps implemented in an exemplary embodiment, where GPS derived slope data and vehicle mass data calculated using GPS derived slope data position data are used to analyze vehicle performance, to determine a cost per loaded mile. Because the concepts disclosed herein provide an improved vehicle mass parameter that is determined while a vehicle is operating, the analysis of the work performed by the vehicle, and the cost per loaded mile calculation, are more accurate than have been heretofore obtainable using data derived by existing techniques. In a block 120 , three dimensional position data (longitude, latitude and elevation) is collected during operation of the vehicle.
- that data is conveyed from the vehicle to a remote computing site (i.e., a monitoring/data storage location) in real-time, while in other embodiments, the position data is stored in a memory in the vehicle, to be conveyed to a remote computing site at a later time.
- fuel use and mileage data is collected during the operation of the vehicle.
- GPS derived slope data is used to calculate vehicle mass, generally as discussed above.
- the mileage data, fuel use data, and vehicle mass data are used to slope data is used to calculate a cost per loaded mile metric.
- An exemplary data set collected from a vehicle will include time indexed position data, engine RPM data, vehicle torque data, and vehicle speed. This data will be collected frequently (multiple times per minute, or a plurality of times over a ten minute period) while the vehicle is operational. Note that vehicle speed can be determined by analyzing position data over time, or can be measured using a vehicle sensor (note that comparing vehicle speed obtained from vehicle sensors with vehicle speed calculated based on GPS data can identify errors in the vehicle speed sensor, which can be caused by incorrect tire sizes, or driver added speed cheating devices designed to override vehicle speed governors).
- Such a data set can also include other types of vehicle data, including, but not limited to, data relating to the vehicle transmission (so drivers can be evaluated based on percentage of time spent in the most efficient gear), data relating to the vehicle braking system (so drivers can be evaluated based on their braking behavior), data relating to the use of cooling fan overrides (so drivers can be evaluated based on how often they such an override that reduces fuel efficiency), data relating to idle time (so drivers can be evaluated based on percentage of time spent in wasting fuel by idling, noting that idle time can be evaluated in light of position data, so that drivers are not penalized for idling at traffic lights), data relating to the use of a vehicle's cruise control system (so drivers can be evaluated based on percentage of time spent driving at fuel efficient speeds).
- this exemplary data set includes the data required to calculate vehicle mass using GPS derived slope data, generally as discussed above.
- FIGS. 11A-11C graphically illustrate histograms that can be derived using the exemplary data set discussed above. These histograms can be used by fleet operators to evaluate the efficiency performance of individual drivers and/or individual vehicles, being operated over specific routes (the routes being defined by the position data). Each Figure has a histogram based on a vehicle being operated with a heavy load, and a histogram based on a vehicle being operated with a light load.
- speed histograms show a percentage of time a vehicle is operated at specific speeds, enabling fleet operators to determine how often the driver/vehicle is using the most efficient vehicle speeds.
- the histograms include bars that show load vs. speed, and time vs. speed.
- FIG. 11A graphically illustrate histograms that can be derived using the exemplary data set discussed above. These histograms can be used by fleet operators to evaluate the efficiency performance of individual drivers and/or individual vehicles, being operated over specific routes (the routes being defined by the position data).
- Each Figure has
- RPM histograms show a percentage of time a vehicle is operated at specific RMP settings, enabling fleet operators to determine how often the driver/vehicle is using the most efficient engine speeds.
- the histograms include bars that show load vs. RPM, and time vs. RPM.
- load histograms show a percentage of time a vehicle is operated at specific load settings, enabling fleet operators to determine how often the driver/vehicle is placed under the most demanding loads.
- the histograms of FIGS. 11A-11C can be generated using the vehicle mass calculated using GPS derived slope data, generally as discussed above.
- FIGS. 12A and 12B graphically illustrate histograms that can be derived using the exemplary data set discussed above. These histograms can be used by fleet operators to evaluate the efficiency performance of individual drivers and/or individual vehicles, being operated over specific routes (the routes being defined by the position data).
- the histogram of FIG. 12A includes bars that show the cost per loaded mile and MPG for 14 different trips (each trip being defined by a different set of position data from the exemplary data set.).
- the histogram of FIG. 12B includes bars that show the cost per loaded mile and MPG for 14 different trips, with the data being normalized to a 30 ton load.
- the histograms of FIGS. 12 and 12B are generated using the vehicle mass calculated using GPS derived slope data, generally as discussed above.
- One aspect of the concepts disclosed herein is a hosted website, enabling drivers and fleet operators to monitor the performance of drivers, based on data collected during the drivers operation of a vehicle.
- drivers can compare their performance metrics to those of their peers, although the concepts disclosed herein also encompass embodiments where individual drivers can only see their own performance scores.
- Fleet operators can use these performance metrics as incentives, by linking driver pay with performance.
- one or more performance metrics are automatically collected while a driver is operating a vehicle, and that data is used to generate a score or rating of the driver's performance.
- the score is normalized to enable driver scores from other types of vehicles to be compared. Then, the driver performance data is posted to the hosted website.
- fleet operators will pay drivers using a mileage component (i.e., paying drivers a fixed rate per loaded mile), while also making additional payments to drivers meeting predefined performance characteristics.
- the hosted website can be used as a forum to enable drivers to track their progress in achieving their pay for performance goals.
- Fleet operators will have a wide degree of freedom in designing pay for performance goals or campaigns. For example, Fleet A can design a campaign in which only drivers having performance scores in the top 10% of the fleet will earn performance pay.
- Fleet B can design a campaign in which only the top 25 scoring will earn performance pay during a particular campaign.
- Fleets can predefine the amount of performance pay each driver can earn.
- Fleets can also predefine a performance pay pool, such that the share of the pool earned by each driver is a function of the number of drivers meeting predefined performance goals for the campaign.
- the performance metric will be a work based performance metric whose calculation involves using vehicle mass determined using GPS derived slope data, generally as discussed above.
- performance campaigns can be metric specific (hard braking performance, idle time performance, such metrics being exemplary and not limiting), or can be based on a single normalized score (cost per loaded mile), but will share in common the characteristic of being implemented for a defined period of time. Drivers will learn to associate such campaigns with opportunities to increase their pay by meeting the performance goals of individual campaigns.
- FIG. 13 is a flow chart showing method steps implemented in an exemplary embodiment.
- the hosted website defines a campaign (noting that the website host may be a fleet operator providing the website for only their drivers, or the hosting website host may be offering the driver performance campaign to drivers from multiple fleets).
- Parameters of the campaign being defined will likely include a duration of the campaign, the prize or performance pay being offered, the eligible pool drivers, and any rules governing disqualification (such as any safety violation or speeding ticket automatically disqualifying a driver), noting that such parameters are exemplary, and not limiting.
- the concepts disclosed herein encompass embodiments in which campaigns are fleet specific, such that only drivers from a specific fleet can participate in that campaign (in such an embodiment, the specific fleet is likely funding the prize, although some third party, such as a favored vendor, customer, or advertiser might offer to fund the prize).
- campaigns are not fleet specific, such that drivers from multiple fleets can participate in that campaign (in such an embodiment, an advertiser or transportation industry vendor might offer to fund the prize).
- the campaign duration is open ended, in that the hosted website will track a drivers' performance data over time, so the driver can use that data to look for other employment opportunities. For example, fleets would likely compete among themselves for drivers having a combination of experience and high performance rankings.
- driver performance data is posted to the hosted website.
- the concepts disclosed herein encompass permutations and combinations of the following: embodiments in which fleet operators can view performance rankings for all of their drivers, but not drivers of other fleets, embodiments in which drivers can only view their own personal performance ranking, embodiments in which drivers can view performance ranking for all of the drivers in their fleet, but not drivers of other fleets, and very transparent embodiments, in which interested parties can visit the website and peruse driver performance rankings with little restrictions.
- a block 66 at the end of the defined campaign, the winning driver (or drivers) are announced and paid a performance pay bonus.
- the concepts disclosed herein can be extended to other types of incentives, such as vacation time, paid travel, tickets to sporting events, and/or goods and services.
- campaign participants are limited to drivers in a specific fleet (i.e., an intra-company or intra-fleet campaign). In such embodiments, that fleet generally will be paying the performance bonuses for the campaign. In other embodiments, campaign participants are not limited to drivers in only one specific fleet (i.e., an inter-company or inter-fleet campaign). In such an embodiment, a third party may be paying the performance bonuses for the campaign. For example, companies providing goods and services to the trucking or vehicle transportation industry may sponsor such a campaign for advertising purposes. A particular fleet operator seeking to attract the attention of drivers in other fleets might also be a sponsor of an inter-company campaign.
- FIG. 14 is a block diagram indicating that block 62 of FIG.
- FIG. 15 is a block diagram indicating that the performance bonus can encompass both intra-company payouts, as indicated in a block 74 (where those bonus funds are used only to pay drivers of a specific fleet), as well as inter-company payouts (where those bonus funds are usedy to pay any winning driver, regardless of fleet), as indicated in a block 76 .
- the performance metric is designed to facilitate comparison of driver performance data across different fleets, and different vehicles. This will enable individual campaigns to include more participating drivers, which in turn will bring in more advertising revenue to fund bigger performance bonuses.
- a metric is mutually agreed upon by a plurality of different fleet operators. Adoption of a common performance metric across multiple fleets will enable top performing drivers to be able to show their cumulative performance scores to other participating fleet operators, providing an additional tool for fleets to use when evaluating potential new hires.
- Such a common performance metric will also enable participating fleet operators to appear more attractive as potential employers than non-participating fleet operators, who will not be offering the drivers the potential of earning the additional performance based income (i.e., income in addition to the industry standard pay by the mile driver compensation).
- the concepts disclosed herein encompass embodiments in which individual fleet operators host their own website, where driver rankings in that fleet can be compared.
- the website is hosted by a third party, and multiple fleet operators participate.
- the third party can offset their costs for operating the website by charging participating fleet operators a fee, and/or by advertising revenue.
- all driver performance data is displayed in an anonymous format, so that individual drivers cannot be identified unless the driver shares their user ID.
- drivers can only compare their score with drivers in their own fleet, while in other embodiments drivers can see the performance data of drivers in other fleets.
- FIG. 16 is a functional block diagram of various elements that can be employed to implement the hosted driver performance website concept, in one exemplary embodiment.
- the elements includes a plurality of enrolled vehicles 148 a - 148 c (noting that the concepts disclosed herein can be applied to a different number of vehicles), a plurality of drivers 152 a - 152 c (noting that the concepts disclosed herein can be applied to a different number of drivers), a plurality of vehicle operators 156 a - 156 c (noting that the concepts disclosed herein can be applied to a different number of vehicle operators), and a remote monitoring service 150 .
- Each vehicle includes the components discussed above in connection with FIG. 3 (noting the number and types of sensors disclosed in FIG.
- monitoring service 150 generates a webpage (as indicated by webpages 154 a - 154 c ) for each vehicle operator, so the vehicle operator can review the performance rankings of each of their drivers. It should be understand that the concepts disclosed herein also encompass other website designs, and the webpage per fleet is not the only possible model. In one embodiment, drivers will have their own webpage 154 d (alternatively, drivers can access the webpage for their specific fleet).
- monitoring service 150 is implemented using a remote computing device, and that the term remote computing device is intended to encompass networked computers, including servers and clients, in private networks or as part of the Internet.
- the monitoring of the vehicle/driver performance data and driver performance ranking by monitoring service 150 can be performed by multiple different computing devices, such that performance data is stored by one element in such a network, retrieved for review by another element in the network, and analyzed by yet another element in the network.
- FIG. 17 is an exemplary screen shot of a webpage accessed by a driver to review his (or her) performance ranking. It should be understood that the exemplary webpage of FIG. 17 is based on having a webpage upon which drivers for a specific fleet can view their individual scores, as well as the scores of other drivers in their fleet. The concepts disclosed herein specifically encompass embodiments where drivers can view only their own performance rankings, in which case a different webpage design would be employed.
- a webpage 100 includes a first portion 102 that enables a driver to select a specific driver from among a plurality of drivers.
- the driver identities can be made anonymous, as shown in FIG. 17 (numbers, not names), or some fleets may wish to list drivers by name (noting that privacy and consent issues for such a scheme are not discussed herein).
- webpage 100 can be unique to only one driver, such that portion 102 is not required. Using numbers to identify drivers enables individual drivers to look at the scores of their peers, without being able to individually identify which driver obtained what score. The driver will likely only know his or her own unique number, and thus will only be able to personally identify his or her own score.
- Webpage 100 also includes a results section 104 , where details of the selected driver's performance ranking are disclosed. It should be understood that the elements shown on webpage 100 can be displayed on different portions of the webpage, or on different webpages and/or different websites, instead of together. Webpage 100 also includes an ad section 112 , where the website host can earn revenue by displaying advertising, and a performance tip section 106 , where the website host provides tips to the driver for improving their performance ranking.
- results section 104 includes results from three different campaigns, recognizing that in some embodiments drivers will be participating in multiple campaigns (although it should be recognized that the concepts disclosed herein encompass embodiments where drivers participate a greater number of campaigns, or fewer campaigns, including only a single campaign (noting the duration of the single campaign could span the driver's career).
- exemplary (but not limiting) information displayed herein includes details on the campaign, whether the campaign is inter-company or intra-company, and the driver's performance ranking for that campaign.
- a visual guide to the driver's relative performance is displayed using a plurality of fuel pump icons (where a greater number of fuel pump icons, or other graphical icons, indicates a better performance rating).
- webpage 100 is based on displaying 10 fuel pump icons for each campaign (icons 108 a - 108 c ), enabling the driver's performance to be graphically displayed on a scale of 1 to 10.
- a driver whose performance ranking is in the top 80 th percentile would have 8 solid or un-shadowed fuel pumps.
- buttons 110 a - c can be used by the driver to select performance tips for the particular campaign to be displayed in section 106 .
- webpage 100 it should be understood that the design of webpage 100 is intended to be exemplary, and different webpage designs can be employed; and further, that the data on webpage 100 can be provided to the vehicle operator on more than one webpage. If desired, access to webpage 100 can be restricted only to the fleet operator employer the driver and the driver themself. However, providing other drivers access to webpage 100 will enable drivers to see how they rank compared to their peers, encouraging drivers to compete amongst themselves to collect the performance bonus available in campaigns.
- a first campaign (associated with radio button 110 a ) is identified as INTRA-COMPANY RANKING.
- This campaign is a fleet sponsored campaign for all of the fleet drivers to compete with each other for a performance bonus.
- Driver ZONA0047 ranks as 83 rd out of 225 drivers, with lower numbers indicating better performance (i.e., the top ranking driver would be ranked as 1, noting that the fleet operator could have reversed the logic, such that 225 was the top ranking driver).
- Six fuel pump icons 108 a are filled in.
- the campaign parameters are summarized, indicating that drivers having rankings from 1-25 (i.e., the top 88.89%) across the entire fleet share in the bonus pool assigned to this campaign.
- Driver ZONA0047 needs to increase his ranking from 83 rd to 25 th in order to be eligible for a share in the bonus pool.
- campaigns can be configured such that the top 25 drivers earn equal shares of the bonus pool, and campaigns can also be configured such that higher ranking drivers (i.e., closer to #1) earn a proportionally larger share of the bonus pool.
- a second campaign (associated with radio button 110 b ) is identified as INTRA-COMPANY CAMPAIGN XYZ.
- This campaign is a fleet sponsored campaign for all of the fleet drivers to compete with each other for a performance bonus.
- Driver ZONA0047 has no ranking indicated in the campaign, thus all ten fuel pump icons 108 b are shadowed or empty.
- the campaign parameters are summarized, indicating that Campaign XYZ includes a bonus pool to be shared by the 10 fleet drivers having the most improved performance scores for December 2011.
- Driver ZONA0047 has selected radio button 110 b so that performance tips and additional information related to Campaign XYZ are displayed in section 106 .
- Those performance tips include a first tip indicating that late shifting reduced Driver ZONA0047's performance ranking by 9.2% over the last 14 days. A second performance tip indicates that hard breaking events reduced Driver ZONA0047's performance ranking by 5.3% over the last 19 days. Finally, the last performance tip indicates that excessive idling on Dec. 11, 2011 disqualified Driver ZONA0047 from Campaign XYZ. It should be recognized that the specific performance tips shown in section 106 are intended to be exemplary, and not limiting. The actual performance tips displayed will be related to the specific campaign, and designed to provide feedback to individual driver's to enable them to identify behaviors that have reduced their performance ranking.
- section 112 includes banner ads targeted to drivers.
- section 112 includes advertising from vendors who are sponsoring specific campaigns, or who are sponsoring hosting of the driver performance ranking website.
- the advertising can be a mixture of those different types, and other types of advertising.
- FIG. 18 is a functional block diagram of an exemplary system employed to implement some of the concepts disclosed herein.
- the functional block diagram illustrates exemplary components used in each vehicle 128 that is enrolled in a vehicle/driver performance monitoring service, to implement some of the method steps discussed above.
- An exemplary vehicle/driver performance monitoring service is based on adding an optional data buffer 136 (or other short-term memory storage) and a bi-directional data link 134 to each enrolled vehicle (in an exemplary, but not limiting embodiment, the data buffer and data link are combined into a single component).
- the short term memory storage is not required for embodiments where the performance data transmitted from the enrolled vehicle does not include operational, vehicle, or driver related data that must be briefly stored.
- the data link is a combination radio frequency (RF) transmitter and receiver, although separate transmitters and receivers could be used (note the term RF specifically encompasses cellular telephone based data links).
- RF radio frequency
- a data terminal can optionally be included in the vehicle to facilitate operator entry of information and operator transmission of information that is presented to the operator on a display within the vehicle. Data collected on a portable data collection device during an inspection can also be uploaded through such a data terminal, or independently by direct transmission to the remote monitoring service. While RF data transmission represents an exemplary embodiment, other types of data transmission could be employed. If the vehicle does not already include performance data/operational data collecting components 130 , such components are added.
- the vehicle includes at least one processor 132 that performs the function of managing the transmission of performance data from the vehicle to the remote monitoring service, according to one or more of the transmission paradigms discussed herein.
- the processor also implements the function of temporarily storing operational data from components 130 in data buffer 136 or other temporary storage, and using bi-directional data link 134 to convey real-time performance data and/or the buffered operational/performance data from the enrolled vehicle to a remote computing device 140 (which is used to analyze the performance of the vehicle and/or driver). It should be understood that those processor functions can be implemented by a single processor, or distributed across multiple processors.
- an output 138 is also included, to provide information to the driver in a form that can be easily understood by the driver.
- Output 138 can be implemented using a speaker providing an audible output, and using a display providing a visual output. Note that output 138 can be combined into a single component with the data buffer and the data link, so only a single additional component is added to the vehicle (recognizing that most vehicles already include the additional required components, such as the operational data collecting components and the processor).
- the vehicle is equipped with a GPS unit (exemplary GPS units are illustrated in FIGS. 6 and 20 ).
- the processor, the GPS component, any buffer, and data link are combined into a single telematics device.
- a telematics device will send GPS and vehicle/driver performance data to the remote computing device discussed below at a plurality of different times during the course of the operation of the vehicle.
- the telematics device will transmit data at intervals ranging from as frequently as every 5 to 15 seconds, or as rarely as every 5 minutes, recognizing that such intervals can vary, and are intended to be exemplary, and not limiting.
- remote computing device 140 (operated by the monitoring service) is logically coupled via a network 142 (such as the Internet) to a computing device 144 (such as a personal computer, a tablet, or a smart phone) accessible to a driver (in embodiments where driver performance rankings are shared with drivers, noting only one such driver device is shown in the Figure; however, the monitoring service will likely be monitoring the performance of a plurality of drivers, each likely having access to a different computing device 144 ), and a computing device 146 accessible to a vehicle operator (noting that in at least some embodiments, the monitoring service performs the monitoring function for a plurality of different vehicle operators/fleets).
- Network 142 facilitates communication between computing devices 140 , 144 , and 146 , enabling the monitoring service to efficiently communicate with drivers and vehicle operators. It should be noted that the concepts disclosed herein encompass embodiments where the monitoring service and vehicle operator are the same entity.
- the concepts disclosed herein are in at least some embodiments intended to be used by fleet owners operating multiple vehicles, and the performance data conveyed to the remote location for diagnosis will include an ID component that enables each enrolled vehicle to be uniquely identified.
- FIG. 19 is a functional block diagram of an exemplary computing device that can be employed to implement some of the method steps disclosed herein. It should be understood that the concepts disclosed herein encompass processing of data collected at a vehicle both in the vehicle and at a remote computing device.
- FIG. 19 schematically illustrates an exemplary computing system 250 suitable for use in implementing the processing functions disclosed herein.
- Exemplary computing system 250 includes a processing unit 254 that is functionally coupled to an input device 252 and to an output device 262 , e.g., a display (which can be used to output a result to a user, although such a result can also be stored).
- Processing unit 254 comprises, for example, a central processing unit (CPU) 258 that executes machine instructions for carrying out an analysis of performance data (and in some embodiments, of position data) collected from enrolled vehicles, to identify mechanical faults in the enrolled vehicles.
- the machine instructions implement functions generally consistent with those described above.
- CPUs suitable for this purpose are available, for example, from Intel Corporation, AMD Corporation, Motorola Corporation, and other sources, as will be well known to those of ordinary skill in this art.
- RAM random access memory
- non-volatile memory 260 which can include read only memory (ROM) and may include some form of memory storage, such as a hard drive, optical disk (and drive), etc. These memory devices are bi-directionally coupled to CPU 258 . Such storage devices are well known in the art. Machine instructions and data are temporarily loaded into RAM 256 from non-volatile memory 260 . Also stored in the non-volatile memory are operating system software and ancillary software. While not separately shown, it will be understood that a generally conventional power supply will be included to provide electrical power at voltage and current levels appropriate to energize computing system 250 .
- Input device 252 can be any device or mechanism that facilitates user input into the operating environment, including, but not limited to, one or more of a mouse or other pointing device, a keyboard, a microphone, a modem, or other input device.
- the input device will be used to initially configure computing system 250 , to achieve the desired processing (i.e., to monitor vehicle performance data over time to detect a mechanical fault).
- Configuration of computing system 250 to achieve the desired processing includes the steps of loading appropriate processing software into non-volatile memory 260 , and launching the processing application (e.g., loading the processing software into RAM 256 for execution by the CPU) so that the processing application is ready for use.
- the computing system 250 can be configured to run autonomously, such that a user input device not regularly employed.
- Output device 262 generally includes any device that produces output information, but will most typically comprise a monitor or computer display designed for human visual perception of output. Use of a conventional computer keyboard for input device 252 and a computer display for output device 262 should be considered as exemplary, rather than as limiting on the scope of this system.
- the computing system 250 can be vehicle performance data (and position data when desired) collected in connection with operation of enrolled vehicles to configured to run autonomously, such that a user output device not regularly employed.
- Data link 264 is configured to enable data to be input into computing system 250 for processing.
- Those of ordinary skill in the art will readily recognize that many types of data links can be implemented, including, but not limited to, universal serial bus (USB) ports, parallel ports, serial ports, inputs configured to couple with portable memory storage devices, FireWire ports, infrared data ports, wireless data communication such as Wi-Fi and BluetoothTM, network connections via Ethernet ports, and other connections that employ the Internet.
- USB universal serial bus
- vehicle/driver performance data from the enrolled vehicles will be communicated wirelessly in at least some embodiments, either directly to the remote computing system that analyzes the data to evaluate the driver's performance, or to some storage location or other computing system that is linked to computing system 250 .
- remote computer “computing device”, and “remote computing device” are intended to encompass a single computer as well as networked computers, including servers and clients, in private networks or as part of the Internet.
- the vehicle/driver performance data received by the monitoring service from the vehicle can be stored by one element in such a network, retrieved for review by another element in the network, and analyzed by yet another element in the network. While implementation of the methods noted above have been discussed in terms of execution of machine instructions by a processor (i.e., the computing device implementing machine instructions to implement the specific functions noted above), the methods could also be implemented using a custom circuit (such as an application specific integrated circuit or ASIC).
- ASIC application specific integrated circuit
- the concepts disclosed herein encompass collecting data from a vehicle during operation of the vehicle.
- the data collected is used to analyze the performance of at least one of the driver and the vehicle.
- the data is collected during operation of the vehicle and wirelessly transmitted from the vehicle during its operation to a remote computing device using a cellular phone network based data link.
- the frequency of such data transmissions can be varied significantly. In general, more data is better, but data transmission is not free, so there is a tension between cost and performance that is subject to variation based on an end user's needs and desires (some users will be willing to pay for more data, while other users will want to minimize data costs by limiting the quantity of data being transferred, even if that results in a somewhat lower quality data set).
- the artisan of skill will be able to readily determine a degree to which data quality can be reduced while still provide useful data set.
- FIG. 20 is a functional block diagram of an exemplary telematics device added to an enrolled vehicle to implement one or more of the methods of FIGS. 1 , 2 , 7 , 8 and 10 .
- An exemplary telematics unit 160 includes a controller 162 , a wireless data link component 164 , a memory 166 in which data and machine instructions used by controller 162 are stored (again, it will be understood that a hardware rather than software-based controller can be implemented, if desired), a position sensing component 170 (such as a GPS receiver), and a data input component 168 configured to extract vehicle data from the vehicle's data bus and/or the vehicle's onboard controller (noting that the single input is exemplary, and not limiting, as additional inputs can be added, and such inputs can be bi-directional to support data output as well).
- Telematics unit 160 is configured to collect position data from the vehicle (to enable vehicle owners to track the current location of their vehicles, and where they have been) and to collect vehicle operational data (including but not limited to engine temperature, coolant temperature, engine speed, vehicle speed, brake use, idle time, and fault codes), and to use the RF component to wirelessly convey such data to vehicle owners.
- vehicle operational data including but not limited to engine temperature, coolant temperature, engine speed, vehicle speed, brake use, idle time, and fault codes
- the exemplary data set discussed above in connection with calculated loaded cost per mile can also be employed. These data transmission can occur at regular intervals, in response to a request for data, or in real-time, or be initiated based on parameters related to the vehicle's speed and/or change in location.
- the term “real-time” as used herein is not intended to imply the data are transmitted instantaneously, since the data may instead be collected over a relatively short period of time (e.g., over a period of seconds or minutes), and transmitted to the remote computing device on an ongoing or intermittent basis, as opposed to storing the data at the vehicle for an extended period of time (hour or days), and transmitting an extended data set to the remote computing device after the data set has been collected.
- Data collected by telematics unit 160 can be conveyed to the vehicle owner using RF component 164 . If desired, additional memory can be included to temporarily store data id the RF component cannot transfer data.
- the RF components is GSM or cellular technology based.
- the controller is configured to implement the method of FIG. 1 by using one or more of data collected from GPS 170 and data from input 168 .
- the controller is configured to implement the method of FIG. 2 by using one or more of data collected from GPS 170 and data from input 168 .
- the controller is configured to implement steps of the method of FIG. 7 .
- the controller is configured to implement steps of the method of FIG. 8 .
- that data can be added to GPS data that is transmitted to a remote computing device.
- input 168 is bi-directional, and the vehicle mass is output from the telematics device onto a vehicle data bus, and can be used by an ECU to control vehicle operations.
- ECUs have been developed to use estimates of vehicle mass to control engine speed and transmission shifting, however, those estimates of vehicle mass have not been based on GPS derived slope data, and as such those prior art vehicle mass estimations have been less accurate than the vehicle mass calculations based on GPS derived slope data as disclosed herein.
- the vehicle is equipped with a multi-axis accelerometer (such as a 3-D accelerometer), that the data from the accelerometer can be used in place of the position data to calculate slope.
- the position data over time provides vectors, and the accelerometer data provides similar vectors.
- the vectors from the 3-D accelerometer can be used in place of the GPS derived vectors in Equations 1-3 discussed above.
- a GPS receiver at the vehicle incorporates a 3-D accelerometer, so both inputs (GPS and 3-D accelerometer) are available to a processor for the calculation of the slope.
Abstract
Description
- This application is based on a prior copending provisional application Ser. No. 61/580,197, filed on Dec. 23, 2011, the benefit of the filing date of which is hereby claimed under 35 U.S.C. §119(e).
- As the cost of sensors, communications systems and navigational systems has dropped, operators of commercial and fleet vehicles now have the ability to collect a tremendous amount of data about the vehicles that they operate, including how the vehicles are being driven by the drivers operating such vehicles.
- Unfortunately, simply collecting such data does not automatically translate into cost savings. It would be desirable to provide such fleet operators with additional tools in order to derive a benefit from the wealth of data that can be collected. Preferably, such tools can be used to provide feedback to drivers to enable the fleet operator to encourage driving habits leading to cost savings. Such a tool might thus be used to develop objective criteria that could be used encourage and provide incentives to drivers to improve their performance in operating the vehicles in a fleet.
- One aspect of the novel concepts presented herein is a method of producing a numerical ranking of a driver's performance based on a plurality of metrics (recognizing that the concepts disclosed herein also encompass the use of only a single metric), and then sharing those metrics on a hosted website, such that the drivers can compare their performance metrics to those of their peers. Fleet operators can use these performance metrics as incentives, by linking driver pay with performance. Such a method comprises the steps of automatically collecting a plurality of metrics while a driver is operating a vehicle, automatically determining a numerical value for each metric, automatically combining the numerical values for the plurality of metrics to achieve a numerical performance value, and normalizing the numerical performance value to achieve a numerical ranking of the driver's performance while operating a vehicle, and then posting the driver performance data to the hosted website.
- In at least one related embodiment, fleet operators will pay drivers using a mileage component (i.e., paying drivers a fixed rate per loaded mile), while also making additional payments to drivers meeting predefined performance characteristics. In at least one related embodiment, only drivers having top ranking performance metrics (such as drivers having performance scores in the top 10% of the fleet, or the 25 drivers having the best performance scores in the fleet, recognizing that such specific examples are not intended to be limiting) will be eligible for the performance pay. In at least one other related embodiment, any driver in the fleet will be eligible for performance bonus pay once they have met a predefined performance metric.
- While many embodiments will employ a single normalized numerical performance score (i.e., a numerical score that combines several different metrics together), it should be recognized that in some embodiments performance pay can be linked to specific performance metrics. For example, consider a fleet operator who has many routes involving mountainous terrain, and that fleet is experiencing excessing brake wear/failure over those routes. That operator may want to link performance pay to brake operating temperature for a period of time to induce drivers operating over those routes to pay more attention to brake temperature. Such a focused review of driver performance data for a defined period of time will be referred to herein and in the claims that follow as a campaign. Where a campaign emphasizes a performance metric such as brake temperature, the campaign can be designed to score drivers' performance in that campaign based only on the target metric (or metrics), such as brake temperature, or an existing normalized performance score can be modified so that the target metric (in this case, brake temperature) is more heavily weighted than normal.
- It should be recognized that campaigns can be metric specific, or can be based on a single normalized score, but will generally share in common the characteristic of being implemented for a defined period of time. Drivers will learn to associate such campaigns with opportunities to increase their pay by meeting the performance goals of individual campaigns. In some embodiments, campaign participants are limited to drivers in a specific fleet (i.e., an intra-company or intra-fleet campaign). In such embodiments, that fleet generally will be paying the performance bonuses for the campaign. In other embodiments, campaign participants are not limited to drivers in only one specific fleet (i.e., an inter-company or inter-fleet campaign). In such an embodiment, a third party may be paying the performance bonuses for the campaign. For example, companies providing goods and services to the trucking or vehicle transportation industry may sponsor such a campaign for advertising purposes. A particular fleet operator seeking to attract the attention of drivers in other fleets might also be a sponsor of an inter-company campaign.
- In at least one aspect of the concepts disclosed herein, the performance metric is designed to facilitate comparison of driver performance data across different fleets, and different vehicles. This will enable individual campaigns to include more participating drivers, which in turn will bring in more advertising revenue to fund bigger performance bonuses. In at least one embodiment, such a metric is mutually agreed upon by a plurality of different fleet operators. Adoption of a common performance metric across multiple fleets will enable top performing drivers to be able to show their cumulative performance scores to other participating fleet operators, providing an additional tool for fleets to use when evaluating potential new hires. Such a common performance metric will also enable participating fleet operators to appear more attractive as potential employers than non-participating fleet operators, who will not be offering the drivers the potential of earning the additional performance based income (i.e., income in addition to the industry standard pay by the mile driver compensation).
- The concepts disclosed herein encompass embodiments in which individual fleet operators host their own website, where driver rankings in that fleet can be compared. In other embodiments, the website is hosted by a third party, and multiple fleet operators participate. The third party can offset their costs for operating the website by charging participating fleet operators a fee, and/or by advertising revenue. In some embodiments, all driver performance data is displayed in an anonymous format, so that individual drivers cannot be identified unless the driver shares their user ID. In some embodiments, drivers can only compare their score with drivers in their own fleet, while in other embodiments drivers can see the performance data of drivers in other fleets.
- Having described the social networking/performance pay aspect of the concepts disclosed herein, the following is directed to discussing exemplary techniques that can be used to acquire the performance data. However, it should be recognized that the social networking/performance pay concepts disclosed herein can be implemented using driver performance metrics generated using different techniques, including techniques that do and do not rely on real-time transmission of performance data from participating vehicles to a remote data center. At least some of the concepts disclosed herein can be implanted using data recorders that store data for a period of time before conveying that data to a data center for generating the driver performance data.
- In at least one embodiment, the performance metric is based at least in part from data collected from one or more engine control units (or vehicle computer(s)) in a vehicle operated by the driver whose performance is being measured.
- In at least one embodiment, the performance metric is based at least in part on fuel economy.
- In at least one embodiment, the performance metric is based at least in part on carbon footprint reduction.
- In at least one embodiment, the performance metric is based at least in part on minimizing fuel efficiency robbing behavior, including sudden braking, rapid acceleration and downshifting too early.
- In at least one embodiment, the performance metric is based at least in part on maximizing fuel efficiency enhancing behavior, including coasting to a stop (instead of staying on the accelerator until the last minute and then braking hard), driving at high average vehicle speeds with minimum time spent at maximum vehicle speed, driving in such a manner so as to achieve a high percent trip distance in top gear (90+% recommended), driving in such a manner so as to achieve a high percent distance in cruise control, driving in such a manner so as to achieve a minimum percent idle/PTO operation, driving in such a manner so as to achieve a minimum service brake activity, driving in such a manner so as to achieve a relatively low number of sudden decelerations, and driving in such a manner so as to achieve a relatively low number of service brake actuations/1000 miles.
- In at least one embodiment, the commonly adopted performance metric is based on the amount of vehicle work performed. In at least one embodiment, such a metric includes using vehicle position derived slope data to determine a vehicle's mass at a plurality of different times during the operation of a vehicle, and then using the mass to calculate work. The vehicle position data is generated by a position sensing system including a component (such as a receiver) disposed in the vehicle. An exemplary position sensing system is the Global Positioning System (GPS). The GPS system is a space-based satellite navigation system that provides location and time information in all weather, anywhere on or near the Earth, where there is an unobstructed line of sight to four or more GPS satellites. It is maintained by the United States government and is freely accessible to anyone with a GPS receiver. It should be understood that when the term GPS is used herein and the claims that follow to refer to a component located at a vehicle, that such a component is a receiver for receiving satellite signals from the GPS system. Further, it should be understood that the concepts disclosed herein can be implemented using different types of vehicle position sensing systems, such as the Russian Global Navigation Satellite System (GLONASS), the planned European Union Galileo positioning system, the Chinese Compass navigation system, and the Indian Regional Navigational Satellite System, and similar such systems as they are developed. The concepts disclosed herein can also be implemented by relying on basic triangulation of signals received from terrestrial based transmitters (such as cell towers), should sufficient transmitters be available (and should the vehicle position resolution obtainable using such technology be generally comparable with that available from satellite based systems).
- Fundamentally, GPS systems calculate velocity in three components (X, Y, Z or N/S, E/W, and Up/Down) based on a Doppler shift of the GPS satellite signals. Scalar speeds can then be calculated from those three components. For example, absolute speed or actual vehicle speed can be determined, as well as ground speed based on the shortest distance between two points (i.e., based on distance as the crow flies). Horizontal ground speed (VHGS) can be calculated using the Pythagorean Theorem. To calculate a grade (G) the vehicle is traveling over (as a percentage), one can take the Z/Up magnitude and divide it by the horizontal ground speed. Replacing Z, x and y with directional vectors (such as Up for Z, West for x and North for y, recognizing that such directional vectors are exemplary, and may change based on the actual GPS data collected from the vehicle) enables one to calculate slope. The slope data is then used to determine the mass of the vehicle at that time. Pervious techniques to calculate mass use torque output, engine RPMs, and vehicle velocity (scalar vehicle speed values can be used in place of velocity) to calculate a vehicle's mass or weight, but did not factor in slope, and thus are not accurate over routes including variable slopes (which most routes include). An improved mass metrics (by including the GPS derived slope data in a mass calculation) enables a more accurate weight based or work based performance metric to be provided.
- In at least one exemplary embodiment, where the driver performance metric is based on a plurality of different parameters or metrics, each one of the plurality of metrics will correspond to a different aspect of the driver's performance while operating a vehicle. Those of ordinary skill in the art will readily recognize that a number of different types of sensors are commonly integrated into commercial, passenger, and fleet vehicles. Such sensors can readily collect a wide variety of operational data that are related to driver performance. For example, one such metric is idle time of a vehicle. Excessive idling time generates increased emissions, increased fuel consumption, and increased engine wear. From the point of view of the fleet operator, drivers who operate vehicles so as to incur relatively greater idle times exhibit a lower performance compared to drivers who do so while incurring relatively less idle time. Additional performance metrics related to both vehicle and driver performance include the amount of time the vehicle is accelerating during the operation of the vehicle by the driver, the extent of such acceleration, the amount of time the vehicle is decelerating during the operation of the vehicle by the driver, the extent of deceleration, whether (or how often) a driver deviates from a predefined route, and whether (or how often and to what extent) a driver exceeds a speed limit. Drivers who accelerate and decelerate often and accelerate or brake excessively are likely to increase fuel consumption, emissions, engine and/or brake wear, as compared to drivers who are more able to accelerate and decelerate modestly, and who are more able to maintain a constant speed.
- By combining a plurality of vehicle metrics related to driver performance, a single numerical score or numerical ranking can be used to provide feedback to individual drivers. Such a numerical ranking can be used as a management tool to improve driver performance. For example, drivers with relatively poor numerical ranking scores can receive counseling or warnings, which should lead to an improvement in their performance, while drivers receiving relatively better scores receive praise or bonuses that encourage them and others to maintain or improve good performance in operating a vehicle. Comparing such scores across companies or between individual branches of a company can be used as a contest or as a motivational tool, where drivers with relatively better scores earn prizes or public praise. For example, a fleet operator could regularly post a list of driver performance rankings in company break rooms, so that drivers can compare their individual performance rankings with one another (note the concepts disclosed herein also encompass posting such scores on a website).
- Essentially, for each metric collected, a numerical value will be determined for that metric. Different metrics can be weighted differently, according to the preference of the fleet operator. For example, if a fleet operator is particularly concerned about reducing excessive idle time, but is less concerned about drivers' acceleration and deceleration habits, idle time can weighted more significantly, to have a greater effect on the numerical ranking determined for the drivers than acceleration and deceleration metrics. Thus, in that case, increased idle time will have a greater proportional negative effect on a driver's overall score, than will excessive acceleration and deceleration of a vehicle.
- Normalizing the combined numerical scores for each metric is important; as such normalization enables the numerical rankings for different drivers to be compared. In one embodiment, the normalization is based on dividing the combined rankings by the distance over which the driver has operated the vehicle. For example, the drivers' combined numerical values for each metric can be divided by the number of miles over which the driver has operated vehicle. In another embodiment, the normalization is based on dividing the combined rankings by the length of time the driver has operated a vehicle. For example, a driver's combined numerical values for each metric can be divided by the number of hours the driver has operated a vehicle.
- Those of ordinary skill in the art will readily recognize that a variety of different valuation paradigms can be implemented for determining a numerical value for each metric. Under some paradigms, a relatively higher normalized combined total will represent relatively better driver performance, while under other paradigms a relatively lower normalized combined total will represent relatively better driver performance. The specific valuation paradigm employed is less important than the aspect of the present invention directed to providing a numerical value that can be used to evaluate driver performance, where the numerical value is based on measurable metrics corresponding to a driver's performance while operating a vehicle. It should also be recognized that the concepts presented herein can be applied to other types of equipment, such as heavy machinery and heavy construction equipment (backhoes, excavators, bulldozers, etc.), as well as to other types of equipment or machinery that an operator controls, so long as the various aspects of the operator's performance can be sensed and the results used to determine a numerical value representative of the overall quality with which the operator controls the equipment or machinery. It should also be recognized that the concepts provided herein can also be beneficially implemented in other types of vehicles, including automobiles (such as rental car fleets, government vehicles, and fleet vehicles assigned to sales representatives or other employees of a business).
- As noted above, one of the metrics that can be beneficially employed relates to determining if a driver has deviated from a predefined route. This metric can be automatically determined by providing predefined route data comprising geographical coordinates, automatically collecting geographical coordinate data while the driver is operating the vehicle (for example using a global positioning satellite (GPS) receiver), and determining if the driver has deviated from the predefined route by comparing the collected geographical coordinate data with the predefined route data.
- Yet another metric that can be beneficially employed relates to determining whether a driver has exceeded a speed limit, which can be automatically determined in several different fashions. In one embodiment, it can be determined if a driver has violated the speed limit by providing a baseline speed limit value (such as 60 miles an hour, for vehicles primarily operated on freeways), automatically collecting vehicle speed data while the driver is operating the vehicle on freeways, and determining if the driver has deviated from the baseline speed limit value by comparing the collected vehicle speed data with the baseline speed limit value (or distance traveled per unit time). In a different embodiment, the step of determining if the driver has violated the speed limit comprises the steps of providing predefined route data comprising geographical coordinates and speed limits associated with each geographical coordinate, automatically collecting geographical coordinate data and vehicle speed data while the driver is operating the vehicle, and determining if the driver has violated the speed limit by comparing the collected geographical coordinate data and vehicle speed data with the predefined route data for which the speed limit is specified at different portions of the route.
- It should be recognized that the steps of collecting the plurality of metrics and processing the plurality of metrics to determine the numerical ranking of the driver's performance can be implemented in physically different locations. In one embodiment, the plurality of metrics are automatically collected by the vehicle, and then transmitted to a remote computing device for processing. The metrics can be transmitted to the remote computing device in real-time, or can be saved in a memory in the vehicle and later transmitted to the remote computing device for processing, for example, when the vehicle is returned to a central garaging facility. In other embodiments, processing of the plurality of the metrics occurs within the vehicle. Where the processing of the plurality of metrics occurs within the vehicle, the driver's current performance ranking can be displayed in real-time to the driver to provide immediate feedback to help the driver improve performance while operating a vehicle. This approach would be analogous to providing real-time fuel mileage estimates to a driver based on current vehicle operating conditions. Providing drivers with feedback in real-time will enable drivers to correct driving habits while operating the vehicle, leading to an improved performance ranking In such an embodiment, it would be desirable to enable the driver to review the metrics responsible for decreasing a driver's performance ranking. For example, if the driver's current performance ranking is relatively low because the driver is frequently accelerating and decelerating, rather than maintaining a constant speed, the display provided to the driver can be customized to indicate the specific metrics responsible for the lower than desired performance ranking.
- This Summary has been provided to introduce a few concepts in a simplified form that are further described in detail below in the Description. However, this Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
- Various aspects and attendant advantages of one or more exemplary embodiments and modifications thereto will become more readily appreciated as the same becomes better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
-
FIG. 1 is a high level flow chart showing the overall method steps implemented in accord with one exemplary embodiment for achieving the concepts disclosed herein; -
FIG. 2 is a more detailed flow chart showing method steps implemented in an exemplary preferred embodiment; -
FIG. 3 schematically illustrates a vehicle that includes a plurality of sensors configured to collect the required metrics; -
FIG. 4A is a functional block diagram illustrating the functional elements of an embodiment in which the metrics are processed within the vehicle to obtain the driver's performance ranking, for example, in real-time; -
FIG. 4B is a functional block diagram illustrating the functional elements of an embodiment in which the metrics are processed by a computing device remote from the vehicle to obtain the driver's performance ranking; -
FIG. 5 schematically illustrates the interior of a vehicle configured with a display to provide the driver with the performance ranking in real-time; -
FIG. 6 schematically illustrates a vehicle that includes a GPS unit configured to collect GPS data that can be used to provide a plurality of metrics for use in determining a driver performance ranking in accord with one aspect of the concepts disclosed herein; -
FIG. 7 is a flow chart showing method steps implemented in an exemplary preferred embodiment, where GPS data are used to provide a plurality of metrics used to determine the driver's performance ranking; -
FIG. 8 is a flow chart showing method steps implemented in accord with one aspect of the concepts disclosed herein, the method steps representing an exemplary technique used to implement that aspect, the aspect comprising using GPS or position data are used to determine a slope the vehicle is traveling over (in at least one embodiment, the slope data will in turn be used to calculate an accurate vehicle mass metric); -
FIG. 9 is a functional block diagram graphically illustrating force vectors acting on a vehicle, and how those vector can be used to solve for vehicle mass, where the GPS derived slope represents a unique metric; -
FIG. 10 is a flow chart showing exemplary method steps implemented according to one aspect of the concepts disclosed herein, where GPS or position derived slope data is used to calculate a vehicle's mass at a plurality of intervals during the operation of a vehicle, and then using the vehicle mass to determine a cost per loaded mile; -
FIGS. 11A-11C graphically illustrate vehicle performance histograms generated derived in part using the GPS derived slope data ofFIG. 8 ; -
FIGS. 12A-12B graphically illustrate vehicle performance histograms generated derived in part using the GPS derived slope data; -
FIG. 13 is a flow chart showing exemplary method steps implemented according to one aspect of the concepts disclosed herein, in which a promotional driver performance campaign is implemented at a hosted website; -
FIGS. 14 and 15 are functional blocks diagram illustrating that the promotional driver performance campaigns and bonuses of the method ofFIG. 13 can include drivers from a single fleet (intra-company) or drivers from multiple fleets (inter-company); -
FIG. 16 is a functional block diagram illustrating exemplary elements in a vehicle/driver performance monitoring system in accord with one aspect of the concepts disclosed herein; -
FIG. 17 is an exemplary screen shot of a website hosting a promotional driver performance campaign; -
FIG. 18 is a another functional block diagram illustrating exemplary elements in a vehicle/driver performance monitoring system in accord with one aspect of the concepts disclosed herein; -
FIG. 19 is an exemplary computing environment for implementing some of the concepts disclosed herein; and -
FIG. 20 is a functional block diagram of an exemplary telematics device added to an enrolled vehicle to implement one or more of the methods ofFIGS. 1 , 2, 7, 8 and 10. - Exemplary embodiments are illustrated in referenced Figures of the drawings. It is intended that the embodiments and Figures disclosed herein are to be considered illustrative rather than restrictive. No limitation on the scope of the technology and of the claims that follow is to be imputed to the examples shown in the drawings and discussed herein. Further, it should be understood that any feature of one embodiment disclosed herein can be combined with one or more features of any other embodiment that is disclosed, unless otherwise indicated.
- Many of the concepts disclosed herein are implemented using a processor that executes a sequence of logical steps using machine instructions stored on a physical or non-transitory memory medium. It should be understood that where the specification and claims of this document refer to a memory medium, that reference is intended to be directed to a non-transitory memory medium. Such sequences can also be implemented by physical logical electrical circuits specifically configured to implement those logical steps (such circuits encompass application specific integrated circuits).
-
FIG. 1 is a high level flow chart showing the overall method steps implemented in accord with one aspect of the concepts disclosed herein. In a block 10 a plurality of metrics related to driver performance are automatically collected by a plurality of sensors incorporated into a vehicle. Such metrics generally relate to driver operation of the vehicle, but may also simply include data related to the vehicle. Such metrics can include, but are not limited to, vehicle speed, vehicle acceleration, vehicle deceleration, engine RPMs, idle time, engine temperature, coolant temperature, oil temperature, fuel consumption, and vehicle positional data. Those of ordinary skill in the art will readily recognize that many different metrics related to vehicle performance and driver performance can be collected. Thus, it should be recognized that the specifically identified metrics are intended to be exemplary, rather than limiting. In ablock 12, a numerical ranking of the driver's performance is determined based on at least some of the metrics collected. -
FIG. 2 is a more detailed flow chart showing method steps implemented in a preferred embodiment, providing additional details as to how the numerical ranking of the driver's performance can be determined. In ablock 14, a numerical value is assigned to each metric collected. It should be recognized that plurality of valuation schemes can be implemented, and the specific scheme implemented is not critical. It should also be recognized that a fleet operator can perceive some metrics to be more or less important to overall driver performance. Thus, individual metrics can be weighted differently. For example, one fleet operator may have little tolerance for drivers who exceed posted speed limits and want to place great emphasis on this metric when determining the numerical ranking. Such a fleet operator can assign significantly more weight to the detection of a driver exceeding a speed limit than to the detection of a driver incurring excessive idle time. Regardless of the specific valuation scheme implemented, a numerical ranking will be determined for each metric collected. In ablock 16, the numerical rankings for each metric are combined. In ablock 18, the combined numerical values for each metric are normalized, to enable performance rankings for different drivers to be more equitably compared. In one embodiment, the normalization is based on a distance over which a driver has operated a vehicle. In another embodiment, the normalization is based on an amount of time the driver has operated a vehicle. This normalization enables the output of the normalized combined total to be provided as a numerical ranking in ablock 20 indicating a driver's performance. Note that the valuation scheme implemented will determine whether a specific numerical value is indicative of a relatively good performance or a relatively poor performance. Under some valuation schemes, relatively higher combined and normalized numerical rankings are generally indicative of relatively better driver performance. In other valuation schemes, relatively lower combined and normalized numerical rankings are generally indicative of relatively better driver performance. -
FIG. 3 schematically illustrates a vehicle including a plurality of sensors configured to collect the required metrics. Avehicle 22, such as a bus or a truck, includes a plurality of sensors 24 a-24 h. It should be recognized that the specific number of sensors, and the specific types of sensors and types of data collected by the sensors, are not critical, so long as the sensors collect data for the desired metrics. As noted above, a plurality of different metrics have been specifically identified, however it should be recognized that such metrics are intended to be exemplary, and not limiting on the concepts disclosed herein. In the disclosed exemplary embodiment, each sensor is coupled to a CPU 26 (which, as described in greater detail below, may in some of embodiments be replaced with (or provided in addition to) a transmitter). -
FIG. 4A is a functional block diagram 28 a illustrating the functional elements of an exemplary embodiment in which the metrics are processed within the vehicle to obtain the driver's performance ranking. The vehicle is equipped withsensors 30 configured to collect the required metrics. The sensors are logically coupled with anonboard vehicle CPU 34, which is configured to implement the method steps generally described above.CPU 34 is logically coupled to amemory 32 in which are stored the machine instructions that are executed by the CPU to carry out these logical steps. The plurality of metrics collected bysensors 30 can also be stored inmemory 32. A (preferably optical or wireless) transmitter 36 (or other data link) can be included to enable either the plurality of metrics or the driver's performance ranking to be communicated to a remote computing device. Anoptional display 38 can be included in the vehicle to provide real-time feedback to the driver (by displaying the driver's performance ranking in real-time). As discussed above, ifdisplay 38 is implemented, it is desirable to provide the ability for the driver to determine which metrics are having the most impact on the driver's performance ranking. -
FIG. 4B is a functional block diagram 28 b illustrating the functional elements of an exemplary embodiment in which the metrics are processed by a computing device to obtain the driver's performance ranking, where the computing device is remote from the vehicle. Once again, the vehicle is equipped withsensors 30 configured to collect the required metrics. The sensors are logically coupled with anonboard vehicle CPU 34, which is configured to transmit the collected metrics toremote computing device 39 through transmitter 36 (or other data link) In a particularly preferred embodiment,transmitter 36 is a wireless transmitter. In such an embodiment, the method steps generally described above for processing the collected metrics can be executed by the remote computing device.CPU 34 is logically coupled tomemory 32 in which the collected metrics can be stored, if the metrics are not to be transmitted to the remote computing device in real-time. Even if the metrics are transmitted to the remote computing device in real-time, such metrics can be stored inmemory 32 as a backup in case the transmission is not successful. In such an embodiment, a display is not likely to be beneficial, unless the remote computing device is configured to transmit the calculated performance ranking back to the vehicle for display to the driver. -
FIG. 5 schematically illustrates the interior of a vehicle configured with adisplay 40 to provide the driver with a performance ranking in real-time. As discussed above, such a display can be implemented by the embodiment schematically illustrated inFIG. 4A . WhileFIG. 5 shows a single numerical performance ranking being dis-played, it should be understood that the concepts disclosed herein encompass displaying a plurality of different metrics (at one or in rotation), as well as displaying a cost per loaded mile metric, which is discussed in detail below in connection withFIG. 10 . The cost per loaded mile metric can be calculated using the concepts disclosed herein at a remote computing device and conveyed back to the vehicle for display, or can be calculated using a processor in the vehicle. -
FIG. 6 schematically illustrates avehicle 22 a that includes aGPS unit 44 configured to collect GPS data that can be used to determine a plurality of metrics for use in determining a driver performance ranking. Such an embodiment enables the driver performance ranking discussed above to be generated without requiring individual or additional sensors to be integrated into the vehicle (although it should be recognized that such individual sensors could be used in addition to (or as an alternative source of) the data provided by the GPS unit, to provide additional metrics used in determining a driver's performance ranking, generally consistent with the method steps described above with respect toFIGS. 1 and 2 ).Vehicle 22 a, such as a bus or a truck (or automobile, or construction equipment, generally as described above) includesGPS unit 44 coupled with anignition system 42 of the vehicle. In an exemplary embodiment, the GPS unit will be coupled with the ignition switch, such that it is assumed that when the ignition switch is on, the engine of the vehicle is actually running, and the GPS unit will be activated. As described in greater detail below, GPS data can be used for a plurality of metrics, including idle time, deceleration time and magnitude, acceleration time and magnitude, and to determine if a driver has violated a speed limit. The most basic GPS unit is able to determine a position of the vehicle at a specific time. That positional information can be used to calculate the speed of a vehicle by determining the change in position of the vehicle between two successive points in time, and to calculate the acceleration or deceleration of the vehicle by determining the change in speed of the vehicle over a time increment. More typically, GPS units automatically determine position, speed, and acceleration/deceleration internally, and these metrics would then not need to be determined by an external computing device (remote or local). -
GPS unit 44 preferably includes or is connected to a wireless transmitter (not separately shown), such that the GPS data can be wirelessly transmitted to a remote computing device, preferably in real-time. The remote computing device can be programmed to manipulate the GPS data to determine a plurality of metrics, which can then be used to calculate a driver's performance ranking, generally as described above. It should be recognized that as an alternative,GPS unit 44 can include an onboard memory, such that the GPS data are stored in the GPS unit, to be uploaded to a remote computing device at a later time (for example, using a wireless or hardwired data link) Significantly,GPS unit 44 enables driver performance rankings to be determined, even if the vehicle is not equipped with separate other sensors of the metric data or an onboard computer (as are required in the embodiments ofFIGS. 3 , 4A, and 4B). It should be understood that the concepts disclosed herein encompasses coupling such a GPS unit to vehicle sensors and/or a vehicle data bus, such that driver/vehicle performance data collected by other vehicle sensors can be combined with GPS data and conveyed to a remote computing site. While not specifically shown inFIG. 6 , it should be understood thatGPS unit 44 can include a processor that uses GPS data and sensor data collected from the vehicle to calculate performance metrics, which are then combined with GPS data and conveyed to the remote computing site. One such metric is GPS derived slope data, discussed in detail in below in connection withFIG. 8 . Such performance metrics calculated by a processor in the vehicle (whether or not that processor is associated with a GPS unit, or is a separate processor in the vehicle) can be displayed in the vehicle, as well as (or in lieu of) being conveyed to a remote computing device. -
FIG. 7 is a flow chart showing method steps implemented in one exemplary embodiment when GPS data are used to calculate a plurality of metrics used to determine the driver's performance ranking. In ablock 46, the vehicle ignition is switched on (and it is assumed that the engine is running), thereby powering on the GPS unit. In ablock 48, the GPS unit collects GPS data (information corresponding both to a particular point in time and a specific geographical position that the vehicle occupies at that specific point in time). In ablock 50, the GPS data are transmitted to a remote computing device. As noted above, the GPS data are preferably transmitted to the remote computing device in real-time. However, it should be recognized that the GPS data can be temporarily stored within the GPS unit (or in a memory electronically coupled to the GPS unit), and transferred to the remote computing device at a later time. In ablock 52, the remote computing device uses the GPS data to calculate an idle time metric. Because the GPS unit is only on when the ignition switch is on and the engine of the vehicle is assumed to be running, an assumption can be made that the idle time equals the accumulated time that the GPS unit is on, but the vehicle is not changing position. - In a
block 54, the remote computing device uses the GPS data to determine metrics corresponding to acceleration time and acceleration magnitude. In ablock 56, the remote computing device uses the GPS data to determine metrics corresponding to deceleration time and deceleration magnitude. In ablock 58, the remote computing device uses the GPS data to determine whether a driver has exceeded a speed limit. Those of ordinary skill in the art will readily recognize that several mapping databases exist that include a database of speed limits and which enable a speed limit for a specific portion of a route being driven by a vehicle to be determined based on a particular geographical coordinate of the vehicle following that route. GPS data includes an indication of the speed of the vehicle at a particular time while the vehicle is at a particular geographical location. Once the vehicle speed has been determined for a particular geographical position, a database can be consulted to determine the speed limit associated with that position along the route, thereby enabling a determination to be made as to whether the driver has exceeded the speed limit. In ablock 60, the plurality of metrics calculated from the GPS data are used to determine the driver's performance ranking, generally as described above in connection withFIGS. 1 and 2 . - It should be recognized that the GPS data can be used to calculate fewer metrics than those described above in connection with
FIG. 7 , and that the metrics specifically identified inFIG. 7 are intended to be exemplary, rather than limiting. Furthermore, if the vehicle includes other sensors for determining metrics, the sensor data can also be forwarded to the remote computing device to be used in calculating the driver's performance ranking, also generally as described above. Furthermore, it should be recognized that rather than (or in addition to) transmitting the GPS data to a remote computing device, the GPS data can be conveyed to a computing device on the vehicle, for determining the driver's performance ranking. - Preferably, performance rankings are determined for each driver in a company (or each driver of a vehicle for which driver performance is of interest), and posted publicly so that drivers can compare each other's individual performance rankings. The public display of driver performance is expected to provide an incentive for drivers to improve their driving performance rankings.
- It should be understood that the concepts disclosed herein encompass many differ types of performance metrics, and different techniques for collecting them. In at least some embodiments, as exemplified by
FIG. 6 , the performance metrics are transmitted from the vehicle to a remote computing device by a wireless data link enabled GPS unit (such as a GSM/GPS), that also collects location data during the vehicle's operation. It should be understood that such performance metrics can also be collected using a data recorder that does not have wireless data transmission capability, such that data will need to be exported from the data recorder to a remote computing device periodically, or the data recorder will need to be removed from the vehicle and coupled to a computing device periodically to export the data used to calculate the driver performance metric(s). - While specific parameters or metrics used to derive a driver performance metric have been discussed above, it should be recognized that the following different parameters/metrics are specifically encompassed herein. One or more embodiments in which the performance metric is based at least in part from data collected from one or more engine control units (or vehicle computer) in a vehicle operated by the driver whose performance is being measured. One or more embodiments in which the performance metric is based at least in part on fuel economy. One or more embodiments in which the performance metric is based at least in part on carbon footprint reduction. One or more embodiments in which the performance metric is based at least in part on minimizing fuel efficiency robbing behavior, including sudden braking, rapid acceleration and downshifting too early. One or more embodiments in which the performance metric is based at least in part on maximizing fuel efficiency enhancing behavior, including coasting to a stop (instead of staying on the accelerator until the last minute and then braking hard), high average vehicle speeds with minimum time spent at maximum vehicle speed, high percent trip distance in top gear (90+% recommended), high percent distance in cruise control, minimum percent idle/PTO operation, minimum service brake activity, low number of sudden decelerations, and low service brake actuation's/1000 miles.
- Another aspect of the concepts disclosed herein is a technique to monitor vehicle location data (i.e. GPS data) over time to determine the actual operating speed of a fleet vehicle. Many fleet operators have the ability to define maximum speed parameters on their vehicles. Maximum speed parameters are defined to enhance safety and to reduce fuel costs (statistics indicated that for heavy trucks every MPH over 62 MPH reduces fuel economy by 0.1 MPG). However, these speed settings can fail due to maintenance issues, or driver manipulations. The maximum speed setting is based on understanding the size of the vehicle's tires. If during maintenance a different size tire is used as a replacement, the predefined speed settings will be inaccurate. Because drivers are often paid by the mile, drivers have an incentive to defeat the maximum speed settings, and drivers may encourage the use of different tire sizes, so they can go faster than the maximum speed setting, to increase their earnings. Drivers can also purchase and install aftermarket kits designed to bypass speed governors, again so they can go faster than the maximum speed setting, to increase their earnings. The concepts disclosed herein encompass collecting GPS data during the operation of a fleet vehicle, and analyzing the location and time parameters of that data to identify when a fleet vehicle exceeds a predefined maximum speed. The GPS verified speed metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- Another aspect of the concepts disclosed herein is to monitor manual overrides for cooling fans in fleet vehicles. Such cooling fans, generally controlled by a vehicle engine control unit (ECU) or vehicle computer, consume up to 50-70HP, and measurably reduce fuel economy. Drivers who habitually override the automatic fan settings can consume unnecessary amounts of fuel. Thus the concepts disclosed herein encompass monitoring a driver's use of cooling fan manual override, to facilitate an evaluation of a driver's performance, and to enable drivers who use such overrides excessively to be identified and trained to reduce their use of manual cooling fan overrides. The cooling fan manual override metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- Another aspect of the concepts disclosed herein is to monitor engine RPMs during a driver's operation of a vehicle. Over revving an engine can lead to increased fuel use and engine wear. Drivers who habitually over rev their vehicles engines can consume unnecessary amounts of fuel. Thus the concepts disclosed herein encompass monitoring the RPM parameters while a driver operates a vehicle, to facilitate an evaluation of a driver's performance, and to enable drivers who consistently over rev their vehicle's engines to be identified and trained to reduce their over revving behavior. The over revving metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- Another aspect of the concepts disclosed herein is to monitor the shifting behavior during a driver's operation of a vehicle. Not running a heavy truck in the highest possible gear when possible can lead to increased fuel use and engine wear. Statistics indicate that every 10% drop of time in top gear results in a 0.5% MPG loss. Thus the concepts disclosed herein encompass monitoring shifting behavior while a driver operates a vehicle, to facilitate an evaluation of a driver's performance, and to enable drivers who consistently under shift to be identified and trained to reduce their over revving behavior. The shifting pattern metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- Another aspect of the concepts disclosed herein is to monitor the amount if idle time during a driver's operation of a vehicle. Increased idle time leads to increased fuel use and engine wear. Thus the concepts disclosed herein encompass monitoring idle time behavior while a driver operates a vehicle, to facilitate an evaluation of a driver's performance, and to enable drivers who excessively allow their vehicle to idle to be identified and trained to reduce their excess idle behavior. The excessive idle metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- Another aspect of the concepts disclosed herein is to monitor a load placed upon a vehicle's engine during a driver's operation of a vehicle. While related to RPM, load is not equivalent. An estimation of engine load is sometimes calculated by a vehicle ECU, and different manufacturers use different combinations of parameters to calculate engine load, including but not limited to throttle position, RPM, manifold pressure, air flow, temperature, air conditioning clutch status, power steering pressure, and transmission gear status. Where engine load is increased without performing more useful work (i.e., carrying more cargo), increased fuel use and engine wear result without a net benefit. Drivers who habitually operate their vehicles under higher engine loads than required consume unnecessary amounts of fuel. Thus the concepts disclosed herein encompass monitoring engine load while a driver operates a vehicle, to facilitate an evaluation of a driver's performance, and to enable drivers who consistently over load their vehicle's engines to be identified and trained to reduce their over loading behavior. The engine load metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
- The calculation of an exemplary performance ranking is described below in regard to one exemplary embodiment. It should be recognized that this approach for determining the performance ranking is not intended to be limiting, but rather to be illustrative of one contemplated valuation scheme and performance ranking implementation. In the exemplary performance ranking, a relatively higher numerical ranking value is generally indicative of relatively poorer driver performance. Thus, in this example, the lower the numerical performance ranking, the better the driver's performance.
- In this example, the sensor data are collected for various metrics corresponding to vehicle acceleration, vehicle deceleration, vehicle idle time, and vehicle speed. Each minute of acceleration time will be assigned one point. Each minute of deceleration time will be assigned one point. Each minute of idle time will be assigned one point. In this example, the fleet operator is also particularly concerned with drivers who violate speed limits on the freeway. Thus, each minute where the vehicle speed exceeds 60 miles an hour while the driver is driving the vehicle on the freeway will result in five points (the fleet operator weighting excessive vehicle speed five times greater than the other metrics). The points are added together to achieve a combined total. The total is then normalized to derive a numerical ranking value for the driver. As noted above, the normalization can be based on either distance driven or time of operation, or a combination thereof.
- The concepts disclosed herein encompass using data collected during the operation of a vehicle to calculate a weight of the vehicle, and then using the calculated weight in a performance analysis of the vehicle. The novel vehicle weight calculation disclosed herein employs in part vehicle position data collected while a vehicle is moving. The position metric can be automatically determined using a global positioning satellite (GPS) receiver installed in the vehicle, to track the vehicle's change in position over time. It should be recognized that the GPS system is but one of a plurality of different vehicle position sensing technologies that can be employed.
- Fundamentally, GPS systems calculate velocity in three components (X, Y, Z or N/S, E/W, and Up/Down) based on a Doppler shift of the GPS satellite signals. Scalar speeds can then be calculated from those three components. For example, absolute speed or actual vehicle speed can be determined, as well as ground speed based on the shortest distance between two points (i.e., based on distance as the crow flies).
- Horizontal ground speed (VHGS) can be calculated using the following relationship based on the Pythagorean theorem:
-
V HGS=√{square root over (x 2 +y 2)} (1) - To calculate a grade (G) the vehicle is traveling over (as a percentage), one can take the Z/Up magnitude and divide it by the horizontal ground speed, VHGS, which results in the following relationship:
-
- Replacing Z, x and y with directional vectors (such as Up for Z, West for x and North for y, recognizing that such directional vectors are exemplary, and may change based on the actual GPS data collected from the vehicle) results in the following relationship:
-
- Once one has derived G as discussed above, very useful vehicle performance metrics can be determined.
- One exemplary use of the slope data is to determine the mass of the vehicle at that time. Mass is a useful metric that can be used as a feedback metric for controlling certain vehicle systems. Some vehicle engine control units (ECUs) use torque output, engine RPMs, and vehicle velocity (noting that scalar vehicle speed can be used for velocity) to calculate a vehicle's mass or weight (as used herein and in the claims that follow, the terms mass and weight are used synonymously, because on the surface of the Earth, the acceleration due to gravity (the “strength of gravity”) is approximately constant; thus the ratio of the weight force of a motionless object on the surface of the Earth to its mass is almost independent of its location, so that an object's weight force can stand as a proxy for its mass, and vice versa). That ECU weight/mass determination technique is error prone, because it does not take into account any slope conditions. Even though the ECU weight/mass determination technique is error prone, the ECU weight/mass determination technique mass estimation provides a metric that can be used to as a feedback metric for various vehicle systems, including transmission shift points, engine RPM control, and emission controls. Having more accurate mass metrics (by including the GPS derived slope data in a mass calculation) will provide an improved mass metric. The concepts disclosed herein specifically encompass a GPS unit configured to use GPS data to calculate slope, to use the slope data and other vehicle parameters to determine vehicle mass (generally as discussed below), and then to provide a GPS slope based vehicle mass metric to a vehicle ECU to be used as a metric to control vehicle operation.
- Vehicle mass can also be used as an analytical metric to determine how much work a vehicle has performed. Being able to accurately determine the amount of work a vehicle performs will help vehicle operators analyze their use patterns to seek out efficiency improvements. The GPS derived slope data enables more accurate vehicle mass calculations to be determined, which in turn will provide an improved vehicle performance data set that can be mined to identify areas in which efficiency improvements could be made.
- Having described the GPS based slope determination technique; the following relationships will be used to obtain vehicle mass from the GPS determined slope (G). These relationships define the forces acting on the vehicle, and include a force related to a grade the vehicle is traveling over, an aerodynamic force, a frictional force, and a force applied by the vehicle to overcome the forces acting on the vehicle. The understanding of these forces is not new, but what is novel are techniques disclosed herein to measure certain parameters that are used to calculate such forces. Being able to measure those parameters, such as a grade the vehicle is traveling over, enables more accurate force calculations to be performed, which in turn enables a better understanding of vehicle operational efficiency.
- It should be understood that with respect to calculating mass, the equations discussed below refer to the velocity of the vehicle as a parameter. Vehicle speed is a scalar quantity; whereas velocity is a vector (velocity is the rate of change of the position of an object, equivalent to a specification of its speed and direction of motion). In other words, speed describes only how fast an object is moving; whereas velocity gives both how fast and in what direction the object is moving. In terms of using position data, such as GPS data, to determine slope, position data changing over time provides three-dimensional vectors (speed and direction) that can be used to derive slope, generally as discussed above. With respect to calculating mass, it is important to recognize that scalar values can be used in place of vectors, while still providing useful results. Thus, it should be understood that the scalar parameter of vehicle speed can be used in place of the velocity parameter discussed below when using the following relationships to determine vehicle mass. Vehicle speed (which in the terms of vehicle arts is often inaccurately referred to as velocity) is generally available in the vehicle from a vehicle ECU or speed sensor (most over the road vehicles, such as trucks and buses, are equipped with relatively accurate speed sensors). While the GPS unit can be used to determine vehicle speed by tracking changes in position over time, in general the resolution of vehicle speed measurements taken from vehicle speed sensors is greater than a resolution of vehicle speed derived from changes in GPS data over time (or other position data), and thus the use of vehicle speed data from vehicle speed sensors is quite useful for the following mass determination techniques.
- A first force opposing a motion of the vehicle relates to a grade or slope the vehicle is traveling over, which can be defined using the relationship of Equation (4).
-
f grade =m*g*G (4) - where m is vehicle mass and g is the local gravitational field (i.e., Earth's gravity).
- A second force opposing a motion of the vehicle relates to aerodynamic forces acting on the vehicle, which can be defined using the relationship of Equation (5).
-
f areo=½*p*Cd*A*v 2 (5) - where ρ is air density, Cd is the coefficient of drag of the vehicle, A is the frontal area of the vehicle, and ν is the vehicle velocity (which can be obtained from the vehicle data bus as speed or from GPS data).
- A third force opposing a motion of the vehicle relates to frictional forces acting on the vehicle, which can be defined using the relationship of Equation (6).
-
f Friction =C rr *m*g*(1−G) (6) - where Crr is the coefficient of rolling resistance of the vehicle (which is assumed to be constant), m is vehicle mass, g is the local gravitational field (i.e., Earth's gravity), and G is the slope, which is calculated using the GPS data as discussed above.
- The force generated by the vehicle to overcome these opposing forces can be defined using the relationship of Equation (7).
-
- where τ is engine output torque (as measured at the vehicle by vehicle sensors/reported by the vehicle data bus), N is engine RIVIPs (as measured at the vehicle by vehicle sensors/reported by the vehicle data bus), ν is the vehicle velocity (which can be obtained from the vehicle data bus or from GPS data), π is the mathematical constant defined as the ratio of any circle's circumference to its diameter, and r is the radius of the vehicles tires.
- Vehicle mass is a parameter in the grade and frictional force relationships, of Equations (4) and (6), respectively. The mass parameter itself can be defined using the relationship of Equation (8).
-
- where m is vehicle mass and α is acceleration (which can be obtained from the vehicle data bus or from GPS data). In an exemplary embodiment, acceleration is obtained from the vehicle sensors.
- Equations (4)-(8) can be solved to obtain mass, as defined using the relationship of Equation (9).
-
- Note that the following parameters will be measured during vehicle operation in order for mass to be calculated: velocity (or speed), torque, RPM. Those parameters, combined with the GPS derived slope data, and known parameters (gravity, air density, rolling resistance, frontal area, drag, π(pi), and tire radius, such parameters can be programmed into the a telematics device or processor at the vehicle) can be used by a processor in the vehicle to calculate mass. Velocity (or speed), torque, and RPM represent metrics that many vehicles already measure during vehicle operation, and thus can be accessed by tapping into a vehicle ECU or data bus. The concepts disclosed herein specifically encompass a GPS unit (or other position sensing unit) including a data port coupled to a vehicle ECU/data bus and a processor configured to calculate a GPS derived slope metric (generally as discussed herein) and a vehicle mass metric (generally as discussed herein, using in part the GPS derived slope data).
- Having an accurate mass parameter, determined in real-time during the operation of the vehicle, will enable a more accurate measurement of the work being performed by the vehicle to be measured. The work metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
-
FIG. 8 is a flow chart showing method steps implemented in an exemplary embodiment, where position data (such as GPS data) collected during the operation of a vehicle is used to determine a slope or grade over which the vehicle is being operated. That grade then can be used to calculate other data, such as a weight or mass of the vehicle. In ablock 120, three dimensional position data (longitude, latitude and elevation) is collected during vehicle operation. In at least some embodiments, that data is conveyed from the vehicle to a remote computing site (i.e., a monitoring/data storage location) in real-time. In other embodiments, the position data is stored in a memory in the vehicle, to be conveyed to a remote computing site at a later time. In ablock 122, the position data is used to determine horizontal ground speed, using the relationship of Equation (1). In ablock 124, the horizontal ground speed (from the GPS data) and the Z-axis position data is used to determine the slope or grade, using the relationships of Equations (2) and (3). - In an
optional block 126, the slope data is used to calculate a mass of the vehicle, using the relationship of Equation (9). In at least some embodiments, the data processing ofblocks blocks -
FIG. 9 graphically illustrates force vectors acting on a vehicle, including a frictional force, an aerodynamic force, a grade/slope related force, and a vehicle applied force used to overcome the opposing forces. The forces are discussed above in connection with Equations (4)-(7), and those relationships can be used to use GPS derived slope data to calculate vehicle mass, as shown in Equation (9). -
FIG. 10 is a flow chart showing method steps implemented in an exemplary embodiment, where GPS derived slope data and vehicle mass data calculated using GPS derived slope data position data are used to analyze vehicle performance, to determine a cost per loaded mile. Because the concepts disclosed herein provide an improved vehicle mass parameter that is determined while a vehicle is operating, the analysis of the work performed by the vehicle, and the cost per loaded mile calculation, are more accurate than have been heretofore obtainable using data derived by existing techniques. In ablock 120, three dimensional position data (longitude, latitude and elevation) is collected during operation of the vehicle. As noted above, in at least some embodiments, that data is conveyed from the vehicle to a remote computing site (i.e., a monitoring/data storage location) in real-time, while in other embodiments, the position data is stored in a memory in the vehicle, to be conveyed to a remote computing site at a later time. In ablock 123, fuel use and mileage data is collected during the operation of the vehicle. In ablock 126, GPS derived slope data is used to calculate vehicle mass, generally as discussed above. Then, in ablock 127, the mileage data, fuel use data, and vehicle mass data are used to slope data is used to calculate a cost per loaded mile metric. - Fleet operators recognize that cost per loaded is a metric that can be analyzed to improve the efficiency of their fleets, by allowing driver performance to be evaluated, and by allowing different routes to be analyzed, to determine the actual cost of servicing a particular route. While these concepts are not new, what is new is the improved vehicle mass metric that can be calculate in real-time while the vehicle is operated, or at a later time, where the mass metric is available for the duration of the vehicle operating segment (or trip). Note that in the prior art, unless the vehicle was weighed during the trip (i.e., before the trip, after the trip, or during the trip at a scale stop) such accurate vehicle mass data was not available, so the cost per loaded metric was error prone, or accurate based on data collected at only a few selected segments of the trip. The concepts disclosed herein are based on collecting vehicle operational data (fuel use, mileage, position data, etc.) frequently (i.e., multiple times a minute, or at least once every few minutes, such intervals being exemplary) so that vehicle mass can be accurately calculated at almost any time during the operation of a vehicle.
- An exemplary data set collected from a vehicle will include time indexed position data, engine RPM data, vehicle torque data, and vehicle speed. This data will be collected frequently (multiple times per minute, or a plurality of times over a ten minute period) while the vehicle is operational. Note that vehicle speed can be determined by analyzing position data over time, or can be measured using a vehicle sensor (note that comparing vehicle speed obtained from vehicle sensors with vehicle speed calculated based on GPS data can identify errors in the vehicle speed sensor, which can be caused by incorrect tire sizes, or driver added speed cheating devices designed to override vehicle speed governors). Such a data set can also include other types of vehicle data, including, but not limited to, data relating to the vehicle transmission (so drivers can be evaluated based on percentage of time spent in the most efficient gear), data relating to the vehicle braking system (so drivers can be evaluated based on their braking behavior), data relating to the use of cooling fan overrides (so drivers can be evaluated based on how often they such an override that reduces fuel efficiency), data relating to idle time (so drivers can be evaluated based on percentage of time spent in wasting fuel by idling, noting that idle time can be evaluated in light of position data, so that drivers are not penalized for idling at traffic lights), data relating to the use of a vehicle's cruise control system (so drivers can be evaluated based on percentage of time spent driving at fuel efficient speeds). Note this exemplary data set includes the data required to calculate vehicle mass using GPS derived slope data, generally as discussed above.
-
FIGS. 11A-11C graphically illustrate histograms that can be derived using the exemplary data set discussed above. These histograms can be used by fleet operators to evaluate the efficiency performance of individual drivers and/or individual vehicles, being operated over specific routes (the routes being defined by the position data). Each Figure has a histogram based on a vehicle being operated with a heavy load, and a histogram based on a vehicle being operated with a light load. InFIG. 11A , speed histograms show a percentage of time a vehicle is operated at specific speeds, enabling fleet operators to determine how often the driver/vehicle is using the most efficient vehicle speeds. The histograms include bars that show load vs. speed, and time vs. speed. InFIG. 11B , RPM histograms show a percentage of time a vehicle is operated at specific RMP settings, enabling fleet operators to determine how often the driver/vehicle is using the most efficient engine speeds. The histograms include bars that show load vs. RPM, and time vs. RPM. InFIG. 11C , load histograms show a percentage of time a vehicle is operated at specific load settings, enabling fleet operators to determine how often the driver/vehicle is placed under the most demanding loads. In exemplary embodiments, when appropriate, the histograms ofFIGS. 11A-11C can be generated using the vehicle mass calculated using GPS derived slope data, generally as discussed above. -
FIGS. 12A and 12B graphically illustrate histograms that can be derived using the exemplary data set discussed above. These histograms can be used by fleet operators to evaluate the efficiency performance of individual drivers and/or individual vehicles, being operated over specific routes (the routes being defined by the position data). The histogram ofFIG. 12A includes bars that show the cost per loaded mile and MPG for 14 different trips (each trip being defined by a different set of position data from the exemplary data set.). The histogram ofFIG. 12B includes bars that show the cost per loaded mile and MPG for 14 different trips, with the data being normalized to a 30 ton load. In exemplary embodiments, the histograms ofFIGS. 12 and 12B are generated using the vehicle mass calculated using GPS derived slope data, generally as discussed above. - One aspect of the concepts disclosed herein is a hosted website, enabling drivers and fleet operators to monitor the performance of drivers, based on data collected during the drivers operation of a vehicle. In at least one embodiment, drivers can compare their performance metrics to those of their peers, although the concepts disclosed herein also encompass embodiments where individual drivers can only see their own performance scores. Fleet operators can use these performance metrics as incentives, by linking driver pay with performance.
- In general, one or more performance metrics are automatically collected while a driver is operating a vehicle, and that data is used to generate a score or rating of the driver's performance. In at least one embodiment, the score is normalized to enable driver scores from other types of vehicles to be compared. Then, the driver performance data is posted to the hosted website.
- In at least one related embodiment, fleet operators will pay drivers using a mileage component (i.e., paying drivers a fixed rate per loaded mile), while also making additional payments to drivers meeting predefined performance characteristics. The hosted website can be used as a forum to enable drivers to track their progress in achieving their pay for performance goals. Fleet operators will have a wide degree of freedom in designing pay for performance goals or campaigns. For example, Fleet A can design a campaign in which only drivers having performance scores in the top 10% of the fleet will earn performance pay. Fleet B can design a campaign in which only the top 25 scoring will earn performance pay during a particular campaign. Fleets can predefine the amount of performance pay each driver can earn. Fleets can also predefine a performance pay pool, such that the share of the pool earned by each driver is a function of the number of drivers meeting predefined performance goals for the campaign.
- In at least one embodiment, the performance metric will be a work based performance metric whose calculation involves using vehicle mass determined using GPS derived slope data, generally as discussed above.
- It should be recognized that performance campaigns can be metric specific (hard braking performance, idle time performance, such metrics being exemplary and not limiting), or can be based on a single normalized score (cost per loaded mile), but will share in common the characteristic of being implemented for a defined period of time. Drivers will learn to associate such campaigns with opportunities to increase their pay by meeting the performance goals of individual campaigns.
-
FIG. 13 is a flow chart showing method steps implemented in an exemplary embodiment. In ablock 62, the hosted website defines a campaign (noting that the website host may be a fleet operator providing the website for only their drivers, or the hosting website host may be offering the driver performance campaign to drivers from multiple fleets). Parameters of the campaign being defined will likely include a duration of the campaign, the prize or performance pay being offered, the eligible pool drivers, and any rules governing disqualification (such as any safety violation or speeding ticket automatically disqualifying a driver), noting that such parameters are exemplary, and not limiting. The concepts disclosed herein encompass embodiments in which campaigns are fleet specific, such that only drivers from a specific fleet can participate in that campaign (in such an embodiment, the specific fleet is likely funding the prize, although some third party, such as a favored vendor, customer, or advertiser might offer to fund the prize). The concepts disclosed herein encompass embodiments in which campaigns are not fleet specific, such that drivers from multiple fleets can participate in that campaign (in such an embodiment, an advertiser or transportation industry vendor might offer to fund the prize). - In at least one embodiment, the campaign duration is open ended, in that the hosted website will track a drivers' performance data over time, so the driver can use that data to look for other employment opportunities. For example, fleets would likely compete among themselves for drivers having a combination of experience and high performance rankings.
- In a
block 64, driver performance data is posted to the hosted website. The concepts disclosed herein encompass permutations and combinations of the following: embodiments in which fleet operators can view performance rankings for all of their drivers, but not drivers of other fleets, embodiments in which drivers can only view their own personal performance ranking, embodiments in which drivers can view performance ranking for all of the drivers in their fleet, but not drivers of other fleets, and very transparent embodiments, in which interested parties can visit the website and peruse driver performance rankings with little restrictions. - In a
block 66, at the end of the defined campaign, the winning driver (or drivers) are announced and paid a performance pay bonus. Note that the concepts disclosed herein can be extended to other types of incentives, such as vacation time, paid travel, tickets to sporting events, and/or goods and services. - As noted above, in some embodiments, campaign participants are limited to drivers in a specific fleet (i.e., an intra-company or intra-fleet campaign). In such embodiments, that fleet generally will be paying the performance bonuses for the campaign. In other embodiments, campaign participants are not limited to drivers in only one specific fleet (i.e., an inter-company or inter-fleet campaign). In such an embodiment, a third party may be paying the performance bonuses for the campaign. For example, companies providing goods and services to the trucking or vehicle transportation industry may sponsor such a campaign for advertising purposes. A particular fleet operator seeking to attract the attention of drivers in other fleets might also be a sponsor of an inter-company campaign.
FIG. 14 is a block diagram indicating thatblock 62 ofFIG. 13 can encompass both intra-company campaigns, as indicated in ablock 68, as well as inter-company campaigns, as indicated in ablock 70.FIG. 15 is a block diagram indicating that the performance bonus can encompass both intra-company payouts, as indicated in a block 74 (where those bonus funds are used only to pay drivers of a specific fleet), as well as inter-company payouts (where those bonus funds are usedy to pay any winning driver, regardless of fleet), as indicated in ablock 76. - In at least one aspect of the concepts disclosed herein, the performance metric is designed to facilitate comparison of driver performance data across different fleets, and different vehicles. This will enable individual campaigns to include more participating drivers, which in turn will bring in more advertising revenue to fund bigger performance bonuses. In at least one embodiment, such a metric is mutually agreed upon by a plurality of different fleet operators. Adoption of a common performance metric across multiple fleets will enable top performing drivers to be able to show their cumulative performance scores to other participating fleet operators, providing an additional tool for fleets to use when evaluating potential new hires. Such a common performance metric will also enable participating fleet operators to appear more attractive as potential employers than non-participating fleet operators, who will not be offering the drivers the potential of earning the additional performance based income (i.e., income in addition to the industry standard pay by the mile driver compensation).
- The concepts disclosed herein encompass embodiments in which individual fleet operators host their own website, where driver rankings in that fleet can be compared. In other embodiments, the website is hosted by a third party, and multiple fleet operators participate. The third party can offset their costs for operating the website by charging participating fleet operators a fee, and/or by advertising revenue. In some embodiments, all driver performance data is displayed in an anonymous format, so that individual drivers cannot be identified unless the driver shares their user ID. In some embodiments, drivers can only compare their score with drivers in their own fleet, while in other embodiments drivers can see the performance data of drivers in other fleets.
-
FIG. 16 is a functional block diagram of various elements that can be employed to implement the hosted driver performance website concept, in one exemplary embodiment. The elements includes a plurality of enrolled vehicles 148 a-148 c (noting that the concepts disclosed herein can be applied to a different number of vehicles), a plurality of drivers 152 a-152 c (noting that the concepts disclosed herein can be applied to a different number of drivers), a plurality of vehicle operators 156 a-156 c (noting that the concepts disclosed herein can be applied to a different number of vehicle operators), and aremote monitoring service 150. Each vehicle includes the components discussed above in connection withFIG. 3 (noting the number and types of sensors disclosed inFIG. 3 are exemplary, and not limiting), enabling the vehicle to convey performance data from the vehicle toremote monitoring service 50, which monitors the performance data from each vehicle 148 a-148 c over time to enable the driver's performance while operating that vehicle to be evaluated. In an exemplaryembodiment monitoring service 150 generates a webpage (as indicated by webpages 154 a-154 c) for each vehicle operator, so the vehicle operator can review the performance rankings of each of their drivers. It should be understand that the concepts disclosed herein also encompass other website designs, and the webpage per fleet is not the only possible model. In one embodiment, drivers will have theirown webpage 154 d (alternatively, drivers can access the webpage for their specific fleet). - It should be understood that
monitoring service 150 is implemented using a remote computing device, and that the term remote computing device is intended to encompass networked computers, including servers and clients, in private networks or as part of the Internet. The monitoring of the vehicle/driver performance data and driver performance ranking by monitoringservice 150 can be performed by multiple different computing devices, such that performance data is stored by one element in such a network, retrieved for review by another element in the network, and analyzed by yet another element in the network. -
FIG. 17 is an exemplary screen shot of a webpage accessed by a driver to review his (or her) performance ranking. It should be understood that the exemplary webpage ofFIG. 17 is based on having a webpage upon which drivers for a specific fleet can view their individual scores, as well as the scores of other drivers in their fleet. The concepts disclosed herein specifically encompass embodiments where drivers can view only their own performance rankings, in which case a different webpage design would be employed. - Referring to
FIG. 17 , awebpage 100 includes afirst portion 102 that enables a driver to select a specific driver from among a plurality of drivers. The driver identities can be made anonymous, as shown inFIG. 17 (numbers, not names), or some fleets may wish to list drivers by name (noting that privacy and consent issues for such a scheme are not discussed herein). It should be understood thatwebpage 100 can be unique to only one driver, such thatportion 102 is not required. Using numbers to identify drivers enables individual drivers to look at the scores of their peers, without being able to individually identify which driver obtained what score. The driver will likely only know his or her own unique number, and thus will only be able to personally identify his or her own score.Webpage 100 also includes aresults section 104, where details of the selected driver's performance ranking are disclosed. It should be understood that the elements shown onwebpage 100 can be displayed on different portions of the webpage, or on different webpages and/or different websites, instead of together.Webpage 100 also includes anad section 112, where the website host can earn revenue by displaying advertising, and aperformance tip section 106, where the website host provides tips to the driver for improving their performance ranking. - Referring to
first portion 102, a driver has selected driver number ZONA0047 (noting that any type of driver identification can be employed), such that the data displayed inresults section 104 andperformance tip section 106 relate to driver ZONA0047. As shown inFIG. 17 ,results section 104 includes results from three different campaigns, recognizing that in some embodiments drivers will be participating in multiple campaigns (although it should be recognized that the concepts disclosed herein encompass embodiments where drivers participate a greater number of campaigns, or fewer campaigns, including only a single campaign (noting the duration of the single campaign could span the driver's career). - Referring to
results section 104, exemplary (but not limiting) information displayed herein includes details on the campaign, whether the campaign is inter-company or intra-company, and the driver's performance ranking for that campaign. A visual guide to the driver's relative performance is displayed using a plurality of fuel pump icons (where a greater number of fuel pump icons, or other graphical icons, indicates a better performance rating). As shown,webpage 100 is based on displaying 10 fuel pump icons for each campaign (icons 108 a-108 c), enabling the driver's performance to be graphically displayed on a scale of 1 to 10. Thus, a driver whose performance ranking is in the top 80th percentile would have 8 solid or un-shadowed fuel pumps. Recognizing that while only full icons are displayed in this example, partial fuel pump icons can be used as well, to provide fractional ratings, or numbers between 0 and 10 can be rounded up to the next whole number. Radio buttons 110 a-c can be used by the driver to select performance tips for the particular campaign to be displayed insection 106. - With respect to
webpage 100, it should be understood that the design ofwebpage 100 is intended to be exemplary, and different webpage designs can be employed; and further, that the data onwebpage 100 can be provided to the vehicle operator on more than one webpage. If desired, access towebpage 100 can be restricted only to the fleet operator employer the driver and the driver themself. However, providing other drivers access towebpage 100 will enable drivers to see how they rank compared to their peers, encouraging drivers to compete amongst themselves to collect the performance bonus available in campaigns. - Referring once again to
section 104 ofwebpage 100, note that a first campaign (associated withradio button 110 a) is identified as INTRA-COMPANY RANKING. This campaign is a fleet sponsored campaign for all of the fleet drivers to compete with each other for a performance bonus. Driver ZONA0047 ranks as 83rd out of 225 drivers, with lower numbers indicating better performance (i.e., the top ranking driver would be ranked as 1, noting that the fleet operator could have reversed the logic, such that 225 was the top ranking driver). Being the 83rd lowest ranking driver out of a fleet of 225 drivers places driver ZONA0047 in the top 63% ((225-83)/(225*100)=63.11%). Sixfuel pump icons 108 a are filled in. The campaign parameters are summarized, indicating that drivers having rankings from 1-25 (i.e., the top 88.89%) across the entire fleet share in the bonus pool assigned to this campaign. Driver ZONA0047 needs to increase his ranking from 83rd to 25th in order to be eligible for a share in the bonus pool. Note that campaigns can be configured such that the top 25 drivers earn equal shares of the bonus pool, and campaigns can also be configured such that higher ranking drivers (i.e., closer to #1) earn a proportionally larger share of the bonus pool. - Referring once again to
section 104 ofwebpage 100, note that a second campaign (associated withradio button 110 b) is identified as INTRA-COMPANY CAMPAIGN XYZ. This campaign is a fleet sponsored campaign for all of the fleet drivers to compete with each other for a performance bonus. Driver ZONA0047 has no ranking indicated in the campaign, thus all ten fuel pump icons 108 b are shadowed or empty. The campaign parameters are summarized, indicating that Campaign XYZ includes a bonus pool to be shared by the 10 fleet drivers having the most improved performance scores for December 2011. Driver ZONA0047 has selectedradio button 110 b so that performance tips and additional information related to Campaign XYZ are displayed insection 106. Those performance tips include a first tip indicating that late shifting reduced Driver ZONA0047's performance ranking by 9.2% over the last 14 days. A second performance tip indicates that hard breaking events reduced Driver ZONA0047's performance ranking by 5.3% over the last 19 days. Finally, the last performance tip indicates that excessive idling on Dec. 11, 2011 disqualified Driver ZONA0047 from Campaign XYZ. It should be recognized that the specific performance tips shown insection 106 are intended to be exemplary, and not limiting. The actual performance tips displayed will be related to the specific campaign, and designed to provide feedback to individual driver's to enable them to identify behaviors that have reduced their performance ranking. - In some
embodiments section 112 includes banner ads targeted to drivers. Inother embodiments section 112 includes advertising from vendors who are sponsoring specific campaigns, or who are sponsoring hosting of the driver performance ranking website. The advertising can be a mixture of those different types, and other types of advertising. -
FIG. 18 is a functional block diagram of an exemplary system employed to implement some of the concepts disclosed herein. The functional block diagram illustrates exemplary components used in eachvehicle 128 that is enrolled in a vehicle/driver performance monitoring service, to implement some of the method steps discussed above. An exemplary vehicle/driver performance monitoring service is based on adding an optional data buffer 136 (or other short-term memory storage) and abi-directional data link 134 to each enrolled vehicle (in an exemplary, but not limiting embodiment, the data buffer and data link are combined into a single component). It should be understood that the short term memory storage is not required for embodiments where the performance data transmitted from the enrolled vehicle does not include operational, vehicle, or driver related data that must be briefly stored. In an exemplary embodiment, the data link is a combination radio frequency (RF) transmitter and receiver, although separate transmitters and receivers could be used (note the term RF specifically encompasses cellular telephone based data links). A data terminal can optionally be included in the vehicle to facilitate operator entry of information and operator transmission of information that is presented to the operator on a display within the vehicle. Data collected on a portable data collection device during an inspection can also be uploaded through such a data terminal, or independently by direct transmission to the remote monitoring service. While RF data transmission represents an exemplary embodiment, other types of data transmission could be employed. If the vehicle does not already include performance data/operationaldata collecting components 130, such components are added. Most vehicles manufactured today include operational data collecting components already, as many of today's vehicles are designed to use such continuously generated operational data to control operation of the vehicle in real-time, and such vehicles generally include data collecting components, data buses, and controllers that use the operational data to control the operation of the vehicle. The vehicle includes at least oneprocessor 132 that performs the function of managing the transmission of performance data from the vehicle to the remote monitoring service, according to one or more of the transmission paradigms discussed herein. In embodiments where the performance data includes temporary storage of operational data, the processor also implements the function of temporarily storing operational data fromcomponents 130 indata buffer 136 or other temporary storage, and using bi-directional data link 134 to convey real-time performance data and/or the buffered operational/performance data from the enrolled vehicle to a remote computing device 140 (which is used to analyze the performance of the vehicle and/or driver). It should be understood that those processor functions can be implemented by a single processor, or distributed across multiple processors. - In some embodiments, an
output 138 is also included, to provide information to the driver in a form that can be easily understood by the driver.Output 138 can be implemented using a speaker providing an audible output, and using a display providing a visual output. Note thatoutput 138 can be combined into a single component with the data buffer and the data link, so only a single additional component is added to the vehicle (recognizing that most vehicles already include the additional required components, such as the operational data collecting components and the processor). - While not specifically shown in
FIG. 18 , in particularly preferred embodiments the vehicle is equipped with a GPS unit (exemplary GPS units are illustrated inFIGS. 6 and 20 ). In a related preferred embodiment the processor, the GPS component, any buffer, and data link are combined into a single telematics device. Such a device will send GPS and vehicle/driver performance data to the remote computing device discussed below at a plurality of different times during the course of the operation of the vehicle. In general, the telematics device will transmit data at intervals ranging from as frequently as every 5 to 15 seconds, or as rarely as every 5 minutes, recognizing that such intervals can vary, and are intended to be exemplary, and not limiting. - As indicated in
FIG. 18 , remote computing device 140 (operated by the monitoring service) is logically coupled via a network 142 (such as the Internet) to a computing device 144 (such as a personal computer, a tablet, or a smart phone) accessible to a driver (in embodiments where driver performance rankings are shared with drivers, noting only one such driver device is shown in the Figure; however, the monitoring service will likely be monitoring the performance of a plurality of drivers, each likely having access to a different computing device 144), and acomputing device 146 accessible to a vehicle operator (noting that in at least some embodiments, the monitoring service performs the monitoring function for a plurality of different vehicle operators/fleets).Network 142 facilitates communication betweencomputing devices - The concepts disclosed herein are in at least some embodiments intended to be used by fleet owners operating multiple vehicles, and the performance data conveyed to the remote location for diagnosis will include an ID component that enables each enrolled vehicle to be uniquely identified.
-
FIG. 19 is a functional block diagram of an exemplary computing device that can be employed to implement some of the method steps disclosed herein. It should be understood that the concepts disclosed herein encompass processing of data collected at a vehicle both in the vehicle and at a remote computing device. -
FIG. 19 schematically illustrates anexemplary computing system 250 suitable for use in implementing the processing functions disclosed herein.Exemplary computing system 250 includes aprocessing unit 254 that is functionally coupled to aninput device 252 and to anoutput device 262, e.g., a display (which can be used to output a result to a user, although such a result can also be stored).Processing unit 254 comprises, for example, a central processing unit (CPU) 258 that executes machine instructions for carrying out an analysis of performance data (and in some embodiments, of position data) collected from enrolled vehicles, to identify mechanical faults in the enrolled vehicles. The machine instructions implement functions generally consistent with those described above. CPUs suitable for this purpose are available, for example, from Intel Corporation, AMD Corporation, Motorola Corporation, and other sources, as will be well known to those of ordinary skill in this art. - Also included in
processing unit 254 are a random access memory (RAM) 256 andnon-volatile memory 260, which can include read only memory (ROM) and may include some form of memory storage, such as a hard drive, optical disk (and drive), etc. These memory devices are bi-directionally coupled toCPU 258. Such storage devices are well known in the art. Machine instructions and data are temporarily loaded intoRAM 256 fromnon-volatile memory 260. Also stored in the non-volatile memory are operating system software and ancillary software. While not separately shown, it will be understood that a generally conventional power supply will be included to provide electrical power at voltage and current levels appropriate to energizecomputing system 250. -
Input device 252 can be any device or mechanism that facilitates user input into the operating environment, including, but not limited to, one or more of a mouse or other pointing device, a keyboard, a microphone, a modem, or other input device. In general, the input device will be used to initially configurecomputing system 250, to achieve the desired processing (i.e., to monitor vehicle performance data over time to detect a mechanical fault). Configuration ofcomputing system 250 to achieve the desired processing includes the steps of loading appropriate processing software intonon-volatile memory 260, and launching the processing application (e.g., loading the processing software intoRAM 256 for execution by the CPU) so that the processing application is ready for use. In embodiments wherecomputing system 250 is implemented in a vehicle, thecomputing system 250 can be configured to run autonomously, such that a user input device not regularly employed. -
Output device 262 generally includes any device that produces output information, but will most typically comprise a monitor or computer display designed for human visual perception of output. Use of a conventional computer keyboard forinput device 252 and a computer display foroutput device 262 should be considered as exemplary, rather than as limiting on the scope of this system. In embodiments wherecomputing system 250 is implemented in a vehicle, thecomputing system 250 can be vehicle performance data (and position data when desired) collected in connection with operation of enrolled vehicles to configured to run autonomously, such that a user output device not regularly employed. -
Data link 264 is configured to enable data to be input intocomputing system 250 for processing. Those of ordinary skill in the art will readily recognize that many types of data links can be implemented, including, but not limited to, universal serial bus (USB) ports, parallel ports, serial ports, inputs configured to couple with portable memory storage devices, FireWire ports, infrared data ports, wireless data communication such as Wi-Fi and Bluetooth™, network connections via Ethernet ports, and other connections that employ the Internet. - Note that vehicle/driver performance data from the enrolled vehicles will be communicated wirelessly in at least some embodiments, either directly to the remote computing system that analyzes the data to evaluate the driver's performance, or to some storage location or other computing system that is linked to
computing system 250. - It should be understood that the terms “remote computer”, “computing device”, and “remote computing device” are intended to encompass a single computer as well as networked computers, including servers and clients, in private networks or as part of the Internet. The vehicle/driver performance data received by the monitoring service from the vehicle can be stored by one element in such a network, retrieved for review by another element in the network, and analyzed by yet another element in the network. While implementation of the methods noted above have been discussed in terms of execution of machine instructions by a processor (i.e., the computing device implementing machine instructions to implement the specific functions noted above), the methods could also be implemented using a custom circuit (such as an application specific integrated circuit or ASIC).
- The concepts disclosed herein encompass collecting data from a vehicle during operation of the vehicle. The data collected is used to analyze the performance of at least one of the driver and the vehicle. In preferred embodiments, the data is collected during operation of the vehicle and wirelessly transmitted from the vehicle during its operation to a remote computing device using a cellular phone network based data link. The frequency of such data transmissions can be varied significantly. In general, more data is better, but data transmission is not free, so there is a tension between cost and performance that is subject to variation based on an end user's needs and desires (some users will be willing to pay for more data, while other users will want to minimize data costs by limiting the quantity of data being transferred, even if that results in a somewhat lower quality data set). The artisan of skill will be able to readily determine a degree to which data quality can be reduced while still provide useful data set.
- Exemplary GPS Device with Onboard Computing Environment
-
FIG. 20 is a functional block diagram of an exemplary telematics device added to an enrolled vehicle to implement one or more of the methods ofFIGS. 1 , 2, 7, 8 and 10. - An
exemplary telematics unit 160 includes acontroller 162, a wirelessdata link component 164, amemory 166 in which data and machine instructions used bycontroller 162 are stored (again, it will be understood that a hardware rather than software-based controller can be implemented, if desired), a position sensing component 170 (such as a GPS receiver), and adata input component 168 configured to extract vehicle data from the vehicle's data bus and/or the vehicle's onboard controller (noting that the single input is exemplary, and not limiting, as additional inputs can be added, and such inputs can be bi-directional to support data output as well). - The capabilities of
telematics unit 160 are particularly useful to fleet operators.Telematics unit 160 is configured to collect position data from the vehicle (to enable vehicle owners to track the current location of their vehicles, and where they have been) and to collect vehicle operational data (including but not limited to engine temperature, coolant temperature, engine speed, vehicle speed, brake use, idle time, and fault codes), and to use the RF component to wirelessly convey such data to vehicle owners. The exemplary data set discussed above in connection with calculated loaded cost per mile can also be employed. These data transmission can occur at regular intervals, in response to a request for data, or in real-time, or be initiated based on parameters related to the vehicle's speed and/or change in location. The term “real-time” as used herein is not intended to imply the data are transmitted instantaneously, since the data may instead be collected over a relatively short period of time (e.g., over a period of seconds or minutes), and transmitted to the remote computing device on an ongoing or intermittent basis, as opposed to storing the data at the vehicle for an extended period of time (hour or days), and transmitting an extended data set to the remote computing device after the data set has been collected. Data collected bytelematics unit 160 can be conveyed to the vehicle owner usingRF component 164. If desired, additional memory can be included to temporarily store data id the RF component cannot transfer data. In particularly preferred embodiments the RF components is GSM or cellular technology based. - In at least one embodiment, the controller is configured to implement the method of
FIG. 1 by using one or more of data collected fromGPS 170 and data frominput 168. In a related embodiment, the controller is configured to implement the method ofFIG. 2 by using one or more of data collected fromGPS 170 and data frominput 168. In yet another related embodiment, the controller is configured to implement steps of the method ofFIG. 7 . - In another embodiment, the controller is configured to implement steps of the method of
FIG. 8 . Once the vehicle mass has been determined, that data can be added to GPS data that is transmitted to a remote computing device. In a related embodiment,input 168 is bi-directional, and the vehicle mass is output from the telematics device onto a vehicle data bus, and can be used by an ECU to control vehicle operations. ECUs have been developed to use estimates of vehicle mass to control engine speed and transmission shifting, however, those estimates of vehicle mass have not been based on GPS derived slope data, and as such those prior art vehicle mass estimations have been less accurate than the vehicle mass calculations based on GPS derived slope data as disclosed herein. - In addition to using GPS or position data to derive slope, it should be noted that if the vehicle is equipped with a multi-axis accelerometer (such as a 3-D accelerometer), that the data from the accelerometer can be used in place of the position data to calculate slope. Essentially, the position data over time provides vectors, and the accelerometer data provides similar vectors. The vectors from the 3-D accelerometer can be used in place of the GPS derived vectors in Equations 1-3 discussed above. Once slope has been determined using the 3-D accelerometer data, mass can be derived using the relationships discussed above. Performance metrics can be similarly determined, generally as described above, using slope derived from 3-D accelerometer data.
- Where a vehicle is equipped both with a 3-D accelerometer and a position tracking component (such as a GPS receiver), input from both sources can be used to calculate velocity in three components (X, Y, Z or N/S, E/W, and Up/Down). Using data from two input sources may increase the accuracy of the slope thus derived using Equations 1-3. If it is determined that data from the 3-D accelerometer is generally more accurate than data from the GPS component (or other position tracking component), or vice versa, then the input data from the relatively more accurate source can be afforded more weight when being used to calculate the three required velocity components (X, Y, Z or N/S, E/W, and Up/Down). In at least one embodiment encompassed by the concepts disclosed herein, a GPS receiver at the vehicle incorporates a 3-D accelerometer, so both inputs (GPS and 3-D accelerometer) are available to a processor for the calculation of the slope.
- Although the concepts disclosed herein have been described in connection with the preferred form of practicing them and modifications thereto, those of ordinary skill in the art will understand that many other modifications can be made thereto within the scope of the claims that follow. Accordingly, it is not intended that the scope of these concepts in any way be limited by the above description, but instead be determined entirely by reference to the claims that follow.
Claims (20)
Priority Applications (10)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/725,886 US20130164715A1 (en) | 2011-12-24 | 2012-12-21 | Using social networking to improve driver performance based on industry sharing of driver performance data |
US14/214,008 US10056008B1 (en) | 2006-06-20 | 2014-03-14 | Using telematics data including position data and vehicle analytics to train drivers to improve efficiency of vehicle use |
US15/005,746 US9527515B2 (en) | 2011-12-23 | 2016-01-25 | Vehicle performance based on analysis of drive data |
US15/355,452 US10099706B2 (en) | 2011-12-23 | 2016-11-18 | Method and apparatus for changing vehicle behavior based on current vehicle location and zone definitions created by a remote user |
US15/355,423 US10507845B2 (en) | 2011-12-23 | 2016-11-18 | Method and apparatus for changing vehicle behavior based on current vehicle location and zone definitions created by a remote user |
US15/369,090 US10431020B2 (en) | 2010-12-02 | 2016-12-05 | Method and apparatus for implementing a vehicle inspection waiver program |
US16/044,475 US10223935B2 (en) | 2006-06-20 | 2018-07-24 | Using telematics data including position data and vehicle analytics to train drivers to improve efficiency of vehicle use |
US16/267,244 US20190180645A1 (en) | 2006-06-20 | 2019-02-04 | Using telematics data including position data and vehicle analytics to train drivers to improve efficiency of vehicle use |
US16/589,382 US10685509B2 (en) | 2010-12-02 | 2019-10-01 | Method and apparatus for implementing a vehicle inspection waiver program |
US16/704,277 US10668932B2 (en) | 2011-12-23 | 2019-12-05 | Method and apparatus for changing vehicle behavior based on current vehicle location and zone definitions mandated by a remote user |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161580197P | 2011-12-24 | 2011-12-24 | |
US13/725,886 US20130164715A1 (en) | 2011-12-24 | 2012-12-21 | Using social networking to improve driver performance based on industry sharing of driver performance data |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/725,183 Continuation-In-Part US9170913B2 (en) | 2006-06-20 | 2012-12-21 | Method and apparatus for 3-D acceleromter based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US13/725,128 Continuation-In-Part US9412282B2 (en) | 2006-06-20 | 2012-12-21 | Using social networking to improve driver performance based on industry sharing of driver performance data |
Related Child Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/725,266 Continuation-In-Part US9489280B2 (en) | 2006-06-20 | 2012-12-21 | Method and apparatus for 3-D accelerometer based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US13/725,128 Continuation-In-Part US9412282B2 (en) | 2006-06-20 | 2012-12-21 | Using social networking to improve driver performance based on industry sharing of driver performance data |
US14/214,008 Continuation-In-Part US10056008B1 (en) | 2006-06-20 | 2014-03-14 | Using telematics data including position data and vehicle analytics to train drivers to improve efficiency of vehicle use |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130164715A1 true US20130164715A1 (en) | 2013-06-27 |
Family
ID=48654903
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/725,886 Abandoned US20130164715A1 (en) | 2006-06-20 | 2012-12-21 | Using social networking to improve driver performance based on industry sharing of driver performance data |
US13/725,128 Active 2033-07-14 US9412282B2 (en) | 2006-06-20 | 2012-12-21 | Using social networking to improve driver performance based on industry sharing of driver performance data |
US15/227,684 Abandoned US20160342924A1 (en) | 2011-12-24 | 2016-08-03 | Method and system for producing a performance metric based on vehicle at a plurality of different locations |
US15/228,676 Abandoned US20160342925A1 (en) | 2011-12-24 | 2016-08-04 | Method and system for producing and displaying a vehicle operating tip to help a driver improve performance |
US15/230,707 Abandoned US20160342926A1 (en) | 2011-12-24 | 2016-08-08 | Method and system for displaying information regarding a bonus program to a driver |
US15/234,461 Abandoned US20160350693A1 (en) | 2011-12-24 | 2016-08-11 | Computer program for generating driver ranking based in part on vehicle weight determined while on road |
Family Applications After (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/725,128 Active 2033-07-14 US9412282B2 (en) | 2006-06-20 | 2012-12-21 | Using social networking to improve driver performance based on industry sharing of driver performance data |
US15/227,684 Abandoned US20160342924A1 (en) | 2011-12-24 | 2016-08-03 | Method and system for producing a performance metric based on vehicle at a plurality of different locations |
US15/228,676 Abandoned US20160342925A1 (en) | 2011-12-24 | 2016-08-04 | Method and system for producing and displaying a vehicle operating tip to help a driver improve performance |
US15/230,707 Abandoned US20160342926A1 (en) | 2011-12-24 | 2016-08-08 | Method and system for displaying information regarding a bonus program to a driver |
US15/234,461 Abandoned US20160350693A1 (en) | 2011-12-24 | 2016-08-11 | Computer program for generating driver ranking based in part on vehicle weight determined while on road |
Country Status (1)
Country | Link |
---|---|
US (6) | US20130164715A1 (en) |
Cited By (69)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130166170A1 (en) * | 2011-12-23 | 2013-06-27 | Zonar Systems, Inc. | Method and apparatus for gps based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US20130289873A1 (en) * | 2012-04-27 | 2013-10-31 | Fleetmatics Irl Limited | System and method for tracking driver hours and timekeeping |
US8876535B2 (en) * | 2013-03-15 | 2014-11-04 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and scoring for driver's education |
US8918229B2 (en) | 2011-12-23 | 2014-12-23 | Zonar Systems, Inc. | Method and apparatus for 3-D accelerometer based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US20150032490A1 (en) * | 2013-07-26 | 2015-01-29 | Xerox Corporation | Identifying driver report data based upon transportation system schedule information |
US9056616B1 (en) * | 2014-09-23 | 2015-06-16 | State Farm Mutual Automobile Insurance | Student driver feedback system allowing entry of tagged events by instructors during driving tests |
US20150199636A1 (en) * | 2014-01-13 | 2015-07-16 | Xerox Corporation | Method and system for performance metric anomaly detection in transportation systems |
US9159032B1 (en) | 2014-03-19 | 2015-10-13 | Xerox Corporation | Predicting arrival times of vehicles based upon observed schedule adherence |
US20160019651A1 (en) * | 2014-07-18 | 2016-01-21 | GM Global Technology Operations LLC | Method and apparatus of determining relative driving characteristics using vehicular participative sensing systems |
US20160135110A1 (en) * | 2014-11-06 | 2016-05-12 | Facebook, Inc. | Association in line-of-sight communication networks |
US9373203B1 (en) | 2014-09-23 | 2016-06-21 | State Farm Mutual Automobile Insurance Company | Real-time driver monitoring and feedback reporting system |
US9412282B2 (en) | 2011-12-24 | 2016-08-09 | Zonar Systems, Inc. | Using social networking to improve driver performance based on industry sharing of driver performance data |
US9440657B1 (en) | 2014-04-17 | 2016-09-13 | State Farm Mutual Automobile Insurance Company | Advanced vehicle operator intelligence system |
US9510191B2 (en) | 2014-06-20 | 2016-11-29 | Facebook, Inc. | Authorization of network address tracking |
US9527515B2 (en) | 2011-12-23 | 2016-12-27 | Zonar Systems, Inc. | Vehicle performance based on analysis of drive data |
US9563869B2 (en) | 2010-09-14 | 2017-02-07 | Zonar Systems, Inc. | Automatic incorporation of vehicle data into documents captured at a vehicle using a mobile computing device |
US20170061825A1 (en) * | 2015-08-25 | 2017-03-02 | Toyota Motor Engineering & Manufacturing North America, Inc. | Systems and methods for driver coaching |
US9586591B1 (en) | 2015-05-04 | 2017-03-07 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and progress monitoring |
US20170088142A1 (en) * | 2015-09-25 | 2017-03-30 | Mcafee, Inc. | Contextual scoring of automobile drivers |
US9646428B1 (en) | 2014-05-20 | 2017-05-09 | State Farm Mutual Automobile Insurance Company | Accident response using autonomous vehicle monitoring |
US9734685B2 (en) | 2014-03-07 | 2017-08-15 | State Farm Mutual Automobile Insurance Company | Vehicle operator emotion management system and method |
US9754425B1 (en) | 2014-02-21 | 2017-09-05 | Allstate Insurance Company | Vehicle telematics and account management |
US9783159B1 (en) | 2014-07-21 | 2017-10-10 | State Farm Mutual Automobile Insurance Company | Methods of theft prevention or mitigation |
US9793988B2 (en) | 2014-11-06 | 2017-10-17 | Facebook, Inc. | Alignment in line-of-sight communication networks |
US9805601B1 (en) | 2015-08-28 | 2017-10-31 | State Farm Mutual Automobile Insurance Company | Vehicular traffic alerts for avoidance of abnormal traffic conditions |
US9806809B2 (en) | 2014-11-06 | 2017-10-31 | Facebook, Inc. | Deploying line-of-sight communication networks |
US9836979B2 (en) | 2014-01-13 | 2017-12-05 | Conduent Business Services, Llc | Method and system for latent demand modeling for a transportation system |
US9892573B1 (en) | 2015-10-14 | 2018-02-13 | Allstate Insurance Company | Driver performance ratings |
US9940834B1 (en) | 2016-01-22 | 2018-04-10 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
US9944282B1 (en) | 2014-11-13 | 2018-04-17 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle automatic parking |
US9972054B1 (en) | 2014-05-20 | 2018-05-15 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US10042359B1 (en) | 2016-01-22 | 2018-08-07 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle refueling |
US10056008B1 (en) | 2006-06-20 | 2018-08-21 | Zonar Systems, Inc. | Using telematics data including position data and vehicle analytics to train drivers to improve efficiency of vehicle use |
US10134278B1 (en) | 2016-01-22 | 2018-11-20 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
US10157509B2 (en) | 2016-12-28 | 2018-12-18 | Conduent Business Services, Llc | System for public transit incident rate analysis and display |
US10185455B2 (en) | 2012-10-04 | 2019-01-22 | Zonar Systems, Inc. | Mobile computing device for fleet telematics |
US10185999B1 (en) | 2014-05-20 | 2019-01-22 | State Farm Mutual Automobile Insurance Company | Autonomous feature use monitoring and telematics |
US10289651B2 (en) | 2012-04-01 | 2019-05-14 | Zonar Systems, Inc. | Method and apparatus for matching vehicle ECU programming to current vehicle operating conditions |
US10319039B1 (en) | 2014-05-20 | 2019-06-11 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US10324463B1 (en) | 2016-01-22 | 2019-06-18 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation adjustment based upon route |
US10373259B1 (en) | 2014-05-20 | 2019-08-06 | State Farm Mutual Automobile Insurance Company | Fully autonomous vehicle insurance pricing |
US10373257B1 (en) | 2014-02-21 | 2019-08-06 | Arity International Limited | Vehicle telematics and account management |
US10373523B1 (en) | 2015-04-29 | 2019-08-06 | State Farm Mutual Automobile Insurance Company | Driver organization and management for driver's education |
US10395332B1 (en) | 2016-01-22 | 2019-08-27 | State Farm Mutual Automobile Insurance Company | Coordinated autonomous vehicle automatic area scanning |
US10417929B2 (en) | 2012-10-04 | 2019-09-17 | Zonar Systems, Inc. | Virtual trainer for in vehicle driver coaching and to collect metrics to improve driver performance |
US10431020B2 (en) | 2010-12-02 | 2019-10-01 | Zonar Systems, Inc. | Method and apparatus for implementing a vehicle inspection waiver program |
US10599155B1 (en) | 2014-05-20 | 2020-03-24 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
US10650621B1 (en) | 2016-09-13 | 2020-05-12 | Iocurrents, Inc. | Interfacing with a vehicular controller area network |
US20200152067A1 (en) * | 2018-11-13 | 2020-05-14 | Toyota Motor North America, Inc. | Systems and methods for determining actual operating conditions of fleet cars |
US10720080B1 (en) * | 2015-11-18 | 2020-07-21 | State Farm Mutual Automobile Insurance Company | System and method for determining a quality of driving of a vehicle |
US11000953B2 (en) * | 2016-08-17 | 2021-05-11 | Locus Robotics Corp. | Robot gamification for improvement of operator performance |
US20210241506A1 (en) * | 2018-12-19 | 2021-08-05 | EffectiveTalent Office LLC | Matched array general talent architecture system and method |
US11107305B2 (en) | 2019-03-14 | 2021-08-31 | Honda Motor Co., Ltd. | Ride-hailing vehicle identification |
US11138524B2 (en) * | 2016-03-11 | 2021-10-05 | Uber Technologies, Inc. | Cascaded boosted predictive models |
US20210334727A1 (en) * | 2020-04-26 | 2021-10-28 | Paccar Inc | Fleet-specific performance impact of vehicle configuration |
US20210387629A1 (en) * | 2020-06-11 | 2021-12-16 | 7980302 Canada Inc. | Using isa system to implement a speed policy identified based on profile of a driving instance |
US11242051B1 (en) | 2016-01-22 | 2022-02-08 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle action communications |
US11250650B2 (en) * | 2019-03-14 | 2022-02-15 | Honda Motor Co., Ltd. | Ride-hailing vehicle identification |
US11441916B1 (en) | 2016-01-22 | 2022-09-13 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle trip routing |
US11504622B1 (en) * | 2021-08-17 | 2022-11-22 | BlueOwl, LLC | Systems and methods for generating virtual encounters in virtual games |
US11572067B2 (en) | 2019-08-30 | 2023-02-07 | 7980302 Canada Inc. | Using ISA system to decelerate truck upon entering geofenced area |
US11590427B1 (en) * | 2020-03-19 | 2023-02-28 | BlueOwl, LLC | Systems and methods for tournament-based telematics insurance pricing |
US11593539B2 (en) | 2018-11-30 | 2023-02-28 | BlueOwl, LLC | Systems and methods for facilitating virtual vehicle operation based on real-world vehicle operation data |
US11597276B2 (en) * | 2021-02-19 | 2023-03-07 | Taipale Telematics Oy | Device, a method, and a computer program for determining the driving behavior of a driver |
US11669090B2 (en) | 2014-05-20 | 2023-06-06 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
US11691084B2 (en) | 2020-01-20 | 2023-07-04 | BlueOwl, LLC | Systems and methods for training and applying virtual occurrences to a virtual character using telematics data of one or more real trips |
US11697069B1 (en) | 2021-08-17 | 2023-07-11 | BlueOwl, LLC | Systems and methods for presenting shared in-game objectives in virtual games |
US11719545B2 (en) | 2016-01-22 | 2023-08-08 | Hyundai Motor Company | Autonomous vehicle component damage and salvage assessment |
US11896903B2 (en) | 2021-08-17 | 2024-02-13 | BlueOwl, LLC | Systems and methods for generating virtual experiences for a virtual game |
Families Citing this family (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101605453B1 (en) * | 2010-08-25 | 2016-04-01 | 네이버 주식회사 | Internet telematics service providing system and internet telematics service providing method for providing mileage-related driving information |
US20160086391A1 (en) * | 2012-03-14 | 2016-03-24 | Autoconnect Holdings Llc | Fleetwide vehicle telematics systems and methods |
JP6424229B2 (en) * | 2014-01-28 | 2018-11-14 | ボルボトラックコーポレーション | Vehicle driver feedback system, vehicle equipped with the system, method for providing vehicle driver feedback, computer program, computer readable medium and control device |
US9679422B2 (en) * | 2014-07-23 | 2017-06-13 | William D. Nicholson | Method for increasing accuracy of vehicle data |
US10402465B1 (en) * | 2014-09-26 | 2019-09-03 | Amazon Technologies, Inc. | Content authority ranking using browsing behavior |
US11318951B2 (en) * | 2014-10-22 | 2022-05-03 | Transportation Ip Holdings Llc | Vehicle consumption monitoring system and method |
US20220244061A1 (en) * | 2014-10-22 | 2022-08-04 | Transportation Ip Holdings, Llc | Vehicle consumption monitoring system and method |
US20160196762A1 (en) * | 2015-01-07 | 2016-07-07 | Caterpillar Inc. | Systems and methods for machine-to-machine coaching |
US10040459B1 (en) * | 2015-09-11 | 2018-08-07 | Lytx, Inc. | Driver fuel score |
US10491590B2 (en) * | 2015-10-12 | 2019-11-26 | AssetWorks LLC | System and method for verifying and redirecting mobile applications |
US10810533B2 (en) * | 2015-12-30 | 2020-10-20 | Lyft, Inc. | System for navigating drivers to passengers and dynamically updating driver performance scores |
US11055785B1 (en) | 2016-05-03 | 2021-07-06 | Allstate Insurance Company | System for monitoring and using data indicative of driver characteristics based on sensors |
WO2018049171A1 (en) | 2016-09-09 | 2018-03-15 | Apex Pro, LLC | Performance coaching method and apparatus |
US20180240164A1 (en) * | 2017-02-17 | 2018-08-23 | Omnitracs, Llc | Cost per mile calculation system |
US10916075B1 (en) * | 2017-06-02 | 2021-02-09 | State Farm Mutual Automobile Insurance Company | Dynamic driving comparison groups for assessing driving safety |
US10832593B1 (en) | 2018-01-25 | 2020-11-10 | BlueOwl, LLC | System and method of facilitating driving behavior modification through driving challenges |
CN112445969A (en) * | 2019-09-05 | 2021-03-05 | 中车时代电动汽车股份有限公司 | Man-machine interaction method and device based on Internet of vehicles |
US11919423B2 (en) | 2020-06-19 | 2024-03-05 | Toyota Motor North America, Inc. | Weight and pressure related validation |
US11613271B2 (en) | 2020-08-18 | 2023-03-28 | Allstate Insurance Company | Driver behavior tracking and prediction |
US20230394964A1 (en) * | 2020-10-16 | 2023-12-07 | Grabtaxi Holdings Pte. Ltd. | Method, electronic device, and system for detecting overspeeding |
BE1028878A9 (en) * | 2020-12-11 | 2022-07-25 | Xwift Bvba | COMPUTER-IMPLEMENTED METHOD, COMPUTER SYSTEM AND COMPUTER PROGRAM TO IMPROVE TRANSPORT EFFICIENCY |
US11132853B1 (en) | 2021-01-28 | 2021-09-28 | Samsara Inc. | Vehicle gateway device and interactive cohort graphical user interfaces associated therewith |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5768382A (en) * | 1995-11-22 | 1998-06-16 | Walker Asset Management Limited Partnership | Remote-auditing of computer generated outcomes and authenticated biling and access control system using cryptographic and other protocols |
US6049755A (en) * | 1998-05-05 | 2000-04-11 | Magellan Dis, Inc. | Navigation system vehicle location display |
US6801901B1 (en) * | 2000-06-09 | 2004-10-05 | Penske Truck Leasing Co. | Systems and methods for building and improving the quality of inventory load configurations |
US20070156337A1 (en) * | 2005-12-30 | 2007-07-05 | Mamdouh Yanni | Systems, methods and apparatuses for continuous in-vehicle and pedestrian navigation |
US7424414B2 (en) * | 2003-09-05 | 2008-09-09 | Road Safety International, Inc. | System for combining driving simulators and data acquisition systems and methods of use thereof |
US20090156310A1 (en) * | 2007-12-18 | 2009-06-18 | Inxile Entertainment | Online gaming and rewards system |
US20090186325A1 (en) * | 2006-03-20 | 2009-07-23 | Ajith Kuttannair Kumar | System, Method, and Computer Software Code for Instructing an Operator to Control a Powered System Having an Autonomous Controller |
US20100160013A1 (en) * | 2007-09-04 | 2010-06-24 | Inertia Wrx | Vehicle tracking system, method and game |
US20120256770A1 (en) * | 2011-04-08 | 2012-10-11 | Peter Mitchell | System and method for providing vehicle and fleet profiles and presentations of trends |
Family Cites Families (163)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3990067A (en) | 1974-09-30 | 1976-11-02 | Sentry Technology Incorporated | Electronic security tour system |
US4025791A (en) | 1975-08-12 | 1977-05-24 | Kilo Corporation | Object identification system |
US4258421A (en) | 1978-02-27 | 1981-03-24 | Rockwell International Corporation | Vehicle monitoring and recording system |
US4325057A (en) | 1980-06-30 | 1982-04-13 | Bishop-Hall, Inc. | School bus approach notification method and apparatus |
US4602127A (en) | 1984-03-09 | 1986-07-22 | Micro Processor Systems, Inc. | Diagnostic data recorder |
EP0219859B1 (en) | 1985-10-25 | 1993-10-06 | Mitsubishi Denki Kabushiki Kaisha | Route bus service controlling system |
US4750197A (en) | 1986-11-10 | 1988-06-07 | Denekamp Mark L | Integrated cargo security system |
US4688244A (en) | 1986-11-10 | 1987-08-18 | Marwan Hannon | Integrated cargo security system |
US4763356A (en) | 1986-12-11 | 1988-08-09 | AT&T Information Systems, Inc. American Telephone and Telegraph Company | Touch screen form entry system |
US4804937A (en) | 1987-05-26 | 1989-02-14 | Motorola, Inc. | Vehicle monitoring arrangement and system |
DE3828725A1 (en) | 1987-09-29 | 1989-04-13 | Pioneer Electronic Corp | METHOD FOR RECORDING THE DRIVING ROUTE DATA FOR A NAVIGATION DEVICE OF A MOTOR VEHICLE |
US5058044A (en) | 1989-03-30 | 1991-10-15 | Auto I.D. Inc. | Automated maintenance checking system |
DE3942070A1 (en) | 1989-12-20 | 1991-06-27 | Deutsche Lufthansa | DEVICE FOR MANAGING A VARIETY OF MOTOR VEHICLES |
WO1991010881A1 (en) | 1990-01-11 | 1991-07-25 | Kabushiki Kaisha Toshiba | Apparatus for supporting inspection of plant |
US5068656A (en) | 1990-12-21 | 1991-11-26 | Rockwell International Corporation | System and method for monitoring and reporting out-of-route mileage for long haul trucks |
US5128651A (en) | 1991-01-02 | 1992-07-07 | Heckart Daniel | School bus alarm system |
JP3273800B2 (en) | 1991-11-11 | 2002-04-15 | 茂 近藤 | Car driving analysis diagnosis method and device |
US5243323A (en) | 1991-12-20 | 1993-09-07 | Rogers Telecom Products, Inc. | School bus alarm system |
US5223844B1 (en) | 1992-04-17 | 2000-01-25 | Auto Trac Inc | Vehicle tracking and security system |
US5585552A (en) | 1992-11-09 | 1996-12-17 | The Technician's Company | Method and apparatus for diagnosing automotive engine problems using oxygen |
CA2110025A1 (en) | 1992-12-16 | 1994-06-17 | Gerard Joseph Hughes | Automatic vehicle recognition and customer automobile diagnostic system |
US5399844A (en) | 1993-01-12 | 1995-03-21 | Facility Management Systems, Inc. | Inspection prompting and reading recording system |
US5719771A (en) | 1993-02-24 | 1998-02-17 | Amsc Subsidiary Corporation | System for mapping occurrences of conditions in a transport route |
GB9308426D0 (en) | 1993-04-23 | 1993-06-09 | Roster Control Syst Ltd | Watchmans clock system |
FR2706934B1 (en) | 1993-06-21 | 1995-10-13 | Valeo Electronique | |
US5394136A (en) | 1993-08-30 | 1995-02-28 | Rockwell International Corporation | Satellite communication and truck driver bonus notification and awards system |
FR2711821B1 (en) | 1993-10-22 | 1995-12-29 | Cogema | Industrial installation monitoring system. |
US5557254A (en) | 1993-11-16 | 1996-09-17 | Mobile Security Communications, Inc. | Programmable vehicle monitoring and security system having multiple access verification devices |
US5459660A (en) | 1993-12-22 | 1995-10-17 | Chrysler Corporation | Circuit and method for interfacing with vehicle computer |
US6546363B1 (en) | 1994-02-15 | 2003-04-08 | Leroy G. Hagenbuch | Apparatus for tracking and recording vital signs and task-related information of a vehicle to identify operating patterns |
US5572192A (en) | 1994-03-17 | 1996-11-05 | Detection Systems, Inc. | Personal security system with guard tour features |
US7103460B1 (en) | 1994-05-09 | 2006-09-05 | Automotive Technologies International, Inc. | System and method for vehicle diagnostics |
US5541845A (en) | 1994-08-02 | 1996-07-30 | Trimble Navigation Limited | Monitoring of route and schedule adherence |
US5459304A (en) | 1994-09-13 | 1995-10-17 | At&T Ipm Corp. | Smart card techniques for motor vehicle record administration |
US6128959A (en) | 1994-11-07 | 2000-10-10 | Eaton Corporation | Driveline vibration analyzer |
US8280682B2 (en) | 2000-12-15 | 2012-10-02 | Tvipr, Llc | Device for monitoring movement of shipped goods |
US5499182A (en) | 1994-12-07 | 1996-03-12 | Ousborne; Jeffrey | Vehicle driver performance monitoring system |
US5839112A (en) | 1994-12-28 | 1998-11-17 | Automatic Data Processing | Method and apparatus for displaying and selecting vehicle parts |
US5629678A (en) | 1995-01-10 | 1997-05-13 | Paul A. Gargano | Personal tracking and recovery system |
US5680328A (en) | 1995-05-22 | 1997-10-21 | Eaton Corporation | Computer assisted driver vehicle inspection reporting system |
US6043661A (en) | 1995-09-07 | 2000-03-28 | Gutierrez; Alejandro | School bus and trailer systems tester |
US5671158A (en) | 1995-09-18 | 1997-09-23 | Envirotest Systems Corp. | Apparatus and method for effecting wireless discourse between computer and technician in testing motor vehicle emission control systems |
US5758299A (en) | 1995-11-03 | 1998-05-26 | Caterpillar Inc. | Method for generating performance ratings for a vehicle operator |
US5808565A (en) | 1996-02-20 | 1998-09-15 | E-Systems, Inc. | GPS triggered automatic annunciator for vehicles |
US5731893A (en) | 1996-02-21 | 1998-03-24 | Dominique; Jeffrey M. | Portable microscope for inspecting fiber optic cable |
WO1997039260A1 (en) | 1996-04-12 | 1997-10-23 | Equos Research Co., Ltd. | Vehicle controller |
AU735935B2 (en) | 1996-08-13 | 2001-07-19 | Paul Freda | Public transit vehicle arrival information system |
US5995898A (en) | 1996-12-06 | 1999-11-30 | Micron Communication, Inc. | RFID system in communication with vehicle on-board computer |
WO1998040837A1 (en) | 1997-03-10 | 1998-09-17 | Global Research Systems, Inc. | Advanced notification systems and methods utilizing a computer network |
US5942753A (en) | 1997-03-12 | 1999-08-24 | Remote Sensing Technologies | Infrared remote sensing device and system for checking vehicle brake condition |
US6253129B1 (en) | 1997-03-27 | 2001-06-26 | Tripmaster Corporation | System for monitoring vehicle efficiency and vehicle and driver performance |
US5874891A (en) | 1997-05-22 | 1999-02-23 | Child Check-Mate Systems, Inc. | Alarm system for use on a bus |
US20020150050A1 (en) | 1999-06-17 | 2002-10-17 | Nathanson Martin D. | Automotive telemetry protocol |
US6092021A (en) | 1997-12-01 | 2000-07-18 | Freightliner Corporation | Fuel use efficiency system for a vehicle for assisting the driver to improve fuel economy |
US6054950A (en) | 1998-01-26 | 2000-04-25 | Multispectral Solutions, Inc. | Ultra wideband precision geolocation system |
US6664897B2 (en) | 1998-03-09 | 2003-12-16 | William R. Pape | Method and system for livestock data collection and management |
US6202024B1 (en) | 1998-03-23 | 2001-03-13 | Kabushikikaisha Equos Research | Communicatory navigation system |
IL123949A (en) | 1998-04-03 | 2001-07-24 | On Track Innovations Ltd | Data transaction card having extended range |
CA2237415C (en) | 1998-05-13 | 2007-08-14 | B.M.R. Mfg. Inc. | System and method for prompting inspection of a multi-passenger vehicle |
DE19826059B4 (en) | 1998-06-12 | 2006-04-06 | Zf Friedrichshafen Ag | Method for controlling an automatic transmission |
US6078255A (en) | 1998-06-23 | 2000-06-20 | The Gleason Agency, Inc. | System for logging premises hazard inspections |
US6311162B1 (en) | 1998-07-25 | 2001-10-30 | Ernst F. Reichwein | Interactive symptomatic recording system and methods |
JP3044025B1 (en) | 1998-12-09 | 2000-05-22 | 株式会社データ・テック | Operation management system capable of analyzing driving tendency and its constituent devices |
US6107917A (en) | 1998-10-16 | 2000-08-22 | Carrender; Curtis L. | Electronic tag including RF modem for monitoring motor vehicle performance with filtering |
EP1127257A4 (en) | 1998-11-05 | 2008-05-28 | Int Truck & Engine Corp | Land vehicle communications system and process for providing information and coordinating vehicle activities |
US6396413B2 (en) | 1999-03-11 | 2002-05-28 | Telephonics Corporation | Personal alarm monitor system |
US6236911B1 (en) | 1999-04-20 | 2001-05-22 | Supersensor (Proprietary) Limited | Load monitoring system and method utilizing transponder tags |
US6505106B1 (en) | 1999-05-06 | 2003-01-07 | International Business Machines Corporation | Analysis and profiling of vehicle fleet data |
US6317668B1 (en) | 1999-06-10 | 2001-11-13 | Qualcomm Incorporated | Paperless log system and method |
WO2000079771A1 (en) | 1999-06-18 | 2000-12-28 | Swisscom Mobile Ag | Interchangeable battery pack for a mobile telephone |
US6256579B1 (en) | 1999-07-13 | 2001-07-03 | Alpine Electronics, Inc. | Vehicle navigation system with road link re-costing |
US6169943B1 (en) | 1999-07-14 | 2001-01-02 | Eaton Corporation | Motor vehicle diagnostic system using hand-held remote control |
DE19933638A1 (en) | 1999-07-17 | 2001-01-18 | Bosch Gmbh Robert | Navigational method for a means of transportation |
US7184866B2 (en) | 1999-07-30 | 2007-02-27 | Oshkosh Truck Corporation | Equipment service vehicle with remote monitoring |
US7783507B2 (en) | 1999-08-23 | 2010-08-24 | General Electric Company | System and method for managing a fleet of remote assets |
US6597973B1 (en) | 1999-10-01 | 2003-07-22 | Daniel M. Barich | Method and arrangement for inspection and requalification of lined vehicles used for transporting commodities and/or hazardous materials |
US6834259B1 (en) | 1999-10-15 | 2004-12-21 | Timekeeping Systems, Inc. | Guard tour system |
US7027955B2 (en) | 1999-10-15 | 2006-04-11 | Timekeeping Systems, Inc. | Guard tour system incorporating a positioning system |
CA2388572A1 (en) | 1999-10-28 | 2001-05-03 | General Electric Company | Diagnosis and repair system and method |
AU2619801A (en) | 1999-10-29 | 2001-06-06 | Gelco Corporation | Method and system for tracking equipment usage information |
US20010047283A1 (en) | 2000-02-01 | 2001-11-29 | Melick Bruce D. | Electronic system for identification, recording, storing, and retrieving material handling equipment records and certifications |
US6370454B1 (en) | 2000-02-25 | 2002-04-09 | Edwin S. Moore Iii | Apparatus and method for monitoring and maintaining mechanized equipment |
US6594621B1 (en) | 2000-03-06 | 2003-07-15 | James H. Meeker | System and method for determining condition of plant |
EP1136788A1 (en) | 2000-03-22 | 2001-09-26 | Asulab S.A. | Portable GPS receiver using a barometric altimeter |
JP2001280985A (en) | 2000-03-29 | 2001-10-10 | Clarion Co Ltd | Automobile navigation system |
US6924750B2 (en) | 2000-05-17 | 2005-08-02 | Omega Patents, L.L.C. | Vehicle tracking unit for controlling operable vehicle devices using a vehicle data bus and related methods |
AU2001270015A1 (en) | 2000-06-23 | 2002-01-08 | Automated Car Rental, L.L.C. | System and method for the automated release of vehicles from a moter pool |
US20020111725A1 (en) | 2000-07-17 | 2002-08-15 | Burge John R. | Method and apparatus for risk-related use of vehicle communication system data |
US20020016655A1 (en) | 2000-08-01 | 2002-02-07 | Joao Raymond Anthony | Apparatus and method for processing and/or for providing vehicle information and/or vehicle maintenance information |
MXPA02003523A (en) | 2000-08-07 | 2002-08-20 | Gen Electric | Computerized method and system for guiding service personnel to select a preferred work site for servicing transportation equipment. |
US20090143923A1 (en) | 2000-09-08 | 2009-06-04 | Breed David S | Arrangement and Method for Monitoring Shipping Containers |
WO2002023403A2 (en) | 2000-09-11 | 2002-03-21 | Pinotage, Llc. | System and method for obtaining and utilizing maintenance information |
US6909947B2 (en) | 2000-10-14 | 2005-06-21 | Motorola, Inc. | System and method for driver performance improvement |
US6450411B1 (en) | 2001-02-02 | 2002-09-17 | Logis-Tech Corporation | Environmental stabilization system and method for maintenance and inventory |
US20020107873A1 (en) | 2001-02-07 | 2002-08-08 | Bandag Licensing Corporation | System and method for data collection, reporting, and analysis of fleet vehicle information |
CA2335692A1 (en) | 2001-02-13 | 2002-08-13 | Kabushiki Kaisha Piste Snow Industries | System and method for maintaining a ski slope using snowmaking apparatuses |
US7627546B2 (en) | 2001-02-14 | 2009-12-01 | General Electric Railcar Services Corporation | Railcar condition inspection database |
US6801841B2 (en) | 2001-02-15 | 2004-10-05 | Joseph A. Tabe | Standard transportation excellent maintenance solutions |
US6754584B2 (en) | 2001-02-28 | 2004-06-22 | Enpoint, Llc | Attitude measurement using a single GPS receiver with two closely-spaced antennas |
US6611740B2 (en) | 2001-03-14 | 2003-08-26 | Networkcar | Internet-based vehicle-diagnostic system |
US6954689B2 (en) | 2001-03-16 | 2005-10-11 | Cnh America Llc | Method and apparatus for monitoring work vehicles |
US6735542B1 (en) | 2001-05-09 | 2004-05-11 | Garmin Ltd. | Method and apparatus for calculating altitude based on barometric and GPS measurements |
WO2002093438A1 (en) | 2001-05-15 | 2002-11-21 | Akzo Nobel N.V. | Fleet servicing method |
US20030030550A1 (en) | 2001-06-08 | 2003-02-13 | Talbot Douglas C. | Child safety device for buses |
JP4076740B2 (en) | 2001-06-22 | 2008-04-16 | 住友ゴム工業株式会社 | Road surface gradient determination apparatus and method, and gradient determination program |
IES20010666A2 (en) | 2001-07-17 | 2002-11-13 | Aircraft Man Technologies Ltd | An electronic operations and maintenance log and system for an aircraft |
US6587768B2 (en) | 2001-08-08 | 2003-07-01 | Meritor Heavy Vehicle Technology, Llc | Vehicle inspection and maintenance system |
US6671646B2 (en) | 2001-09-11 | 2003-12-30 | Zonar Compliance Systems, Llc | System and process to ensure performance of mandated safety and maintenance inspections |
US7174243B1 (en) | 2001-12-06 | 2007-02-06 | Hti Ip, Llc | Wireless, internet-based system for transmitting and analyzing GPS data |
US6614392B2 (en) | 2001-12-07 | 2003-09-02 | Delaware Capital Formation, Inc. | Combination RFID and GPS functionality on intelligent label |
JP3719659B2 (en) | 2001-12-26 | 2005-11-24 | 株式会社日立製作所 | Information receiving system and information receiving terminal |
US7048185B2 (en) | 2002-03-08 | 2006-05-23 | Fleettrakker, L.L.C. | Equipment tracking system and method |
US20030182033A1 (en) | 2002-03-25 | 2003-09-25 | Underdahl Craig T | Vehicle usage data tracking system |
US6529808B1 (en) | 2002-04-22 | 2003-03-04 | Delphi Technologies, Inc. | Method and system for analyzing an on-board vehicle computer system |
US6894617B2 (en) | 2002-05-04 | 2005-05-17 | Richman Technology Corporation | Human guard enhancing multiple site integrated security system |
JP2004044779A (en) | 2002-05-21 | 2004-02-12 | Aisin Seiki Co Ltd | Drive device |
US8047432B2 (en) | 2002-06-11 | 2011-11-01 | Intelligent Technologies International, Inc. | Package tracking techniques |
US20040236596A1 (en) | 2003-02-27 | 2004-11-25 | Mahesh Chowdhary | Business method for a vehicle safety management system |
US6847887B1 (en) | 2003-03-04 | 2005-01-25 | Navteq North America, Llc | Method and system for obtaining road grade data |
JP3763476B2 (en) | 2003-05-29 | 2006-04-05 | 三菱電機株式会社 | Vehicle and driver behavior analysis system |
US7627422B2 (en) * | 2003-06-24 | 2009-12-01 | At&T Intellectual Property I, Lp | Methods, systems and computer program products for ride matching based on selection criteria and drive characteristic information |
US6856897B1 (en) | 2003-09-22 | 2005-02-15 | Navteq North America, Llc | Method and system for computing road grade data |
US7035733B1 (en) | 2003-09-22 | 2006-04-25 | Navteq North America, Llc | Method and system for obtaining road grade data |
US20050107946A1 (en) | 2003-11-13 | 2005-05-19 | Takanori Shimizu | Vehicle navigation apparatus |
DE102004026639B4 (en) | 2004-03-22 | 2006-03-02 | Daimlerchrysler Ag | Method for determining height information in a motor vehicle |
US20050273250A1 (en) | 2004-05-18 | 2005-12-08 | Bruce Hamilton | System and method for dynamic navigational route selection |
US7254516B2 (en) | 2004-12-17 | 2007-08-07 | Nike, Inc. | Multi-sensor monitoring of athletic performance |
US8670922B2 (en) | 2005-01-19 | 2014-03-11 | Kabushiki Kaisha Kenwood | Guiding route generation device and guiding route generation method |
EP1894180A4 (en) | 2005-06-09 | 2011-11-02 | Greenroad Driving Technologies Ltd | System and method for displaying a driving profile |
DE602005008601D1 (en) | 2005-09-14 | 2008-09-11 | Fiat Ricerche | Method and system for detecting the speed direction of a vehicle and the road inclination |
US8024114B2 (en) | 2006-02-01 | 2011-09-20 | Qualcomm Incorporated | Navigation data quality feedback |
GB0605069D0 (en) * | 2006-03-14 | 2006-04-26 | Airmax Group Plc | Method and system for driver style monitoring and analysing |
US8508353B2 (en) | 2009-01-26 | 2013-08-13 | Drivecam, Inc. | Driver risk assessment system and method having calibrating automatic event scoring |
US8849501B2 (en) | 2009-01-26 | 2014-09-30 | Lytx, Inc. | Driver risk assessment system and method employing selectively automatic event scoring |
US20130164713A1 (en) | 2011-12-23 | 2013-06-27 | Zonar Systems, Inc. | Method and apparatus for gps based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US20130164715A1 (en) | 2011-12-24 | 2013-06-27 | Zonar Systems, Inc. | Using social networking to improve driver performance based on industry sharing of driver performance data |
US7659808B1 (en) * | 2006-08-21 | 2010-02-09 | Richard P Cooper | Automotive messaging display unit |
KR20200051054A (en) | 2006-12-13 | 2020-05-12 | 크라운 이큅먼트 코포레이션 | Fleet management system |
US7692552B2 (en) | 2007-01-23 | 2010-04-06 | International Business Machines Corporation | Method and system for improving driver safety and situational awareness |
JP2008242544A (en) | 2007-03-26 | 2008-10-09 | Hitachi Ltd | Collision avoidance device and method |
US9129460B2 (en) | 2007-06-25 | 2015-09-08 | Inthinc Technology Solutions, Inc. | System and method for monitoring and improving driver behavior |
US8577703B2 (en) | 2007-07-17 | 2013-11-05 | Inthinc Technology Solutions, Inc. | System and method for categorizing driving behavior using driver mentoring and/or monitoring equipment to determine an underwriting risk |
EP2116968A1 (en) | 2008-05-06 | 2009-11-11 | Airmax Remote Limited | Method and apparatus for rating how a vehicle is driven |
JP4906808B2 (en) | 2008-07-31 | 2012-03-28 | トヨタ自動車株式会社 | Fuel saving driving diagnosis device, fuel saving driving diagnosis system, vehicle travel control device, and fuel saving driving diagnosis method |
US8229639B2 (en) | 2009-02-17 | 2012-07-24 | Lockheed Martin Corporation | System and method for stability control |
US20100209890A1 (en) | 2009-02-18 | 2010-08-19 | Gm Global Technology Operations, Inc. | Vehicle stability enhancement control adaptation to driving skill with integrated driving skill recognition |
US20100209884A1 (en) | 2009-02-18 | 2010-08-19 | Gm Global Technology Operations, Inc. | Driving skill recognition based on vehicle left and right turns |
US20100209891A1 (en) | 2009-02-18 | 2010-08-19 | Gm Global Technology Operations, Inc. | Driving skill recognition based on stop-and-go driving behavior |
US8604920B2 (en) | 2009-10-20 | 2013-12-10 | Cartasite, Inc. | Systems and methods for vehicle performance analysis and presentation |
US9285485B2 (en) | 2009-11-12 | 2016-03-15 | GM Global Technology Operations LLC | GPS-enhanced vehicle velocity estimation |
US9558520B2 (en) | 2009-12-31 | 2017-01-31 | Hartford Fire Insurance Company | System and method for geocoded insurance processing using mobile devices |
GB2483251A (en) | 2010-09-01 | 2012-03-07 | Ricardo Uk Ltd | Driver feedback system and method |
US8996287B2 (en) | 2011-03-31 | 2015-03-31 | United Parcel Service Of America, Inc. | Calculating speed and travel times with travel delays |
US8538785B2 (en) | 2011-08-19 | 2013-09-17 | Hartford Fire Insurance Company | System and method for computing and scoring the complexity of a vehicle trip using geo-spatial information |
US20130052614A1 (en) * | 2011-08-31 | 2013-02-28 | Pulsar Informatics, Inc. | Driver Performance Metric |
US8918229B2 (en) | 2011-12-23 | 2014-12-23 | Zonar Systems, Inc. | Method and apparatus for 3-D accelerometer based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US20130274955A1 (en) | 2012-04-13 | 2013-10-17 | Walter Steven Rosenbaum | Method for analyzing operation characteristics of a vehicle driver |
WO2013184832A2 (en) | 2012-06-07 | 2013-12-12 | Zoll Medical Corporation | Systems and methods for video capture, user feedback, reporting, adaptive parameters, and remote data access in vehicle safety monitoring |
US9171382B2 (en) | 2012-08-06 | 2015-10-27 | Cloudparc, Inc. | Tracking speeding violations and controlling use of parking spaces using cameras |
WO2014172323A1 (en) | 2013-04-15 | 2014-10-23 | Flextronics Ap, Llc | Driver facts behavior information storage system |
JP6179191B2 (en) | 2013-05-27 | 2017-08-16 | 富士通株式会社 | Driving diagnosis device, driving diagnosis method and program |
JP6221364B2 (en) | 2013-06-06 | 2017-11-01 | 富士通株式会社 | Driving diagnosis device, driving diagnosis system, and driving diagnosis method |
KR101558388B1 (en) | 2014-04-14 | 2015-10-07 | 현대자동차 주식회사 | Apparatus and method of road slope estimating by using gravitational acceleration sensor |
-
2012
- 2012-12-21 US US13/725,886 patent/US20130164715A1/en not_active Abandoned
- 2012-12-21 US US13/725,128 patent/US9412282B2/en active Active
-
2016
- 2016-08-03 US US15/227,684 patent/US20160342924A1/en not_active Abandoned
- 2016-08-04 US US15/228,676 patent/US20160342925A1/en not_active Abandoned
- 2016-08-08 US US15/230,707 patent/US20160342926A1/en not_active Abandoned
- 2016-08-11 US US15/234,461 patent/US20160350693A1/en not_active Abandoned
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5768382A (en) * | 1995-11-22 | 1998-06-16 | Walker Asset Management Limited Partnership | Remote-auditing of computer generated outcomes and authenticated biling and access control system using cryptographic and other protocols |
US6049755A (en) * | 1998-05-05 | 2000-04-11 | Magellan Dis, Inc. | Navigation system vehicle location display |
US6801901B1 (en) * | 2000-06-09 | 2004-10-05 | Penske Truck Leasing Co. | Systems and methods for building and improving the quality of inventory load configurations |
US7424414B2 (en) * | 2003-09-05 | 2008-09-09 | Road Safety International, Inc. | System for combining driving simulators and data acquisition systems and methods of use thereof |
US20070156337A1 (en) * | 2005-12-30 | 2007-07-05 | Mamdouh Yanni | Systems, methods and apparatuses for continuous in-vehicle and pedestrian navigation |
US20090186325A1 (en) * | 2006-03-20 | 2009-07-23 | Ajith Kuttannair Kumar | System, Method, and Computer Software Code for Instructing an Operator to Control a Powered System Having an Autonomous Controller |
US20100160013A1 (en) * | 2007-09-04 | 2010-06-24 | Inertia Wrx | Vehicle tracking system, method and game |
US20090156310A1 (en) * | 2007-12-18 | 2009-06-18 | Inxile Entertainment | Online gaming and rewards system |
US20120256770A1 (en) * | 2011-04-08 | 2012-10-11 | Peter Mitchell | System and method for providing vehicle and fleet profiles and presentations of trends |
Cited By (262)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10223935B2 (en) | 2006-06-20 | 2019-03-05 | Zonar Systems, Inc. | Using telematics data including position data and vehicle analytics to train drivers to improve efficiency of vehicle use |
US10056008B1 (en) | 2006-06-20 | 2018-08-21 | Zonar Systems, Inc. | Using telematics data including position data and vehicle analytics to train drivers to improve efficiency of vehicle use |
US9563869B2 (en) | 2010-09-14 | 2017-02-07 | Zonar Systems, Inc. | Automatic incorporation of vehicle data into documents captured at a vehicle using a mobile computing device |
US10431020B2 (en) | 2010-12-02 | 2019-10-01 | Zonar Systems, Inc. | Method and apparatus for implementing a vehicle inspection waiver program |
US20130184964A1 (en) * | 2011-12-23 | 2013-07-18 | Zonar Systems, Inc. | Method and apparatus for 3-d acceleromter based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US8918229B2 (en) | 2011-12-23 | 2014-12-23 | Zonar Systems, Inc. | Method and apparatus for 3-D accelerometer based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US9280435B2 (en) * | 2011-12-23 | 2016-03-08 | Zonar Systems, Inc. | Method and apparatus for GPS based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US20130166170A1 (en) * | 2011-12-23 | 2013-06-27 | Zonar Systems, Inc. | Method and apparatus for gps based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US10507845B2 (en) | 2011-12-23 | 2019-12-17 | Zonar Systems, Inc. | Method and apparatus for changing vehicle behavior based on current vehicle location and zone definitions created by a remote user |
US9170913B2 (en) * | 2011-12-23 | 2015-10-27 | Zonar Systems, Inc. | Method and apparatus for 3-D acceleromter based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US10099706B2 (en) | 2011-12-23 | 2018-10-16 | Zonar Systems, Inc. | Method and apparatus for changing vehicle behavior based on current vehicle location and zone definitions created by a remote user |
US9527515B2 (en) | 2011-12-23 | 2016-12-27 | Zonar Systems, Inc. | Vehicle performance based on analysis of drive data |
US9489280B2 (en) | 2011-12-23 | 2016-11-08 | Zonar Systems, Inc. | Method and apparatus for 3-D accelerometer based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US10102096B2 (en) | 2011-12-23 | 2018-10-16 | Zonar Systems, Inc. | Method and apparatus for GPS based Z-axis difference parameter computation |
US9384111B2 (en) | 2011-12-23 | 2016-07-05 | Zonar Systems, Inc. | Method and apparatus for GPS based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis |
US9412282B2 (en) | 2011-12-24 | 2016-08-09 | Zonar Systems, Inc. | Using social networking to improve driver performance based on industry sharing of driver performance data |
US10289651B2 (en) | 2012-04-01 | 2019-05-14 | Zonar Systems, Inc. | Method and apparatus for matching vehicle ECU programming to current vehicle operating conditions |
US10679157B2 (en) * | 2012-04-27 | 2020-06-09 | Verizon Connect Ireland Limited | System and method for tracking driver hours and timekeeping |
US20130289873A1 (en) * | 2012-04-27 | 2013-10-31 | Fleetmatics Irl Limited | System and method for tracking driver hours and timekeeping |
US10185455B2 (en) | 2012-10-04 | 2019-01-22 | Zonar Systems, Inc. | Mobile computing device for fleet telematics |
US10565893B2 (en) | 2012-10-04 | 2020-02-18 | Zonar Systems, Inc. | Virtual trainer for in vehicle driver coaching and to collect metrics to improve driver performance |
US10417929B2 (en) | 2012-10-04 | 2019-09-17 | Zonar Systems, Inc. | Virtual trainer for in vehicle driver coaching and to collect metrics to improve driver performance |
US9530333B1 (en) * | 2013-03-15 | 2016-12-27 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and scoring for driver's education |
US9478150B1 (en) * | 2013-03-15 | 2016-10-25 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and scoring for driver's education |
US9342993B1 (en) | 2013-03-15 | 2016-05-17 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and scoring for driver's education |
US9275552B1 (en) * | 2013-03-15 | 2016-03-01 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and scoring for driver'S education |
US10446047B1 (en) * | 2013-03-15 | 2019-10-15 | State Farm Mutual Automotive Insurance Company | Real-time driver observation and scoring for driver'S education |
US10311750B1 (en) * | 2013-03-15 | 2019-06-04 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and scoring for driver's education |
US8876535B2 (en) * | 2013-03-15 | 2014-11-04 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and scoring for driver's education |
US20150032490A1 (en) * | 2013-07-26 | 2015-01-29 | Xerox Corporation | Identifying driver report data based upon transportation system schedule information |
US20150199636A1 (en) * | 2014-01-13 | 2015-07-16 | Xerox Corporation | Method and system for performance metric anomaly detection in transportation systems |
US9836979B2 (en) | 2014-01-13 | 2017-12-05 | Conduent Business Services, Llc | Method and system for latent demand modeling for a transportation system |
US11132849B1 (en) | 2014-02-21 | 2021-09-28 | Arity International Limited | Vehicle telematics and account management |
US11798089B1 (en) | 2014-02-21 | 2023-10-24 | Arity International Limited | Vehicle telematics and account management |
US9754425B1 (en) | 2014-02-21 | 2017-09-05 | Allstate Insurance Company | Vehicle telematics and account management |
US10373257B1 (en) | 2014-02-21 | 2019-08-06 | Arity International Limited | Vehicle telematics and account management |
US10482685B1 (en) | 2014-02-21 | 2019-11-19 | Arity International Limited | Vehicle telematics and account management |
US9734685B2 (en) | 2014-03-07 | 2017-08-15 | State Farm Mutual Automobile Insurance Company | Vehicle operator emotion management system and method |
US10121345B1 (en) | 2014-03-07 | 2018-11-06 | State Farm Mutual Automobile Insurance Company | Vehicle operator emotion management system and method |
US10593182B1 (en) | 2014-03-07 | 2020-03-17 | State Farm Mutual Automobile Insurance Company | Vehicle operator emotion management system and method |
US9934667B1 (en) | 2014-03-07 | 2018-04-03 | State Farm Mutual Automobile Insurance Company | Vehicle operator emotion management system and method |
US9159032B1 (en) | 2014-03-19 | 2015-10-13 | Xerox Corporation | Predicting arrival times of vehicles based upon observed schedule adherence |
US9440657B1 (en) | 2014-04-17 | 2016-09-13 | State Farm Mutual Automobile Insurance Company | Advanced vehicle operator intelligence system |
US9908530B1 (en) | 2014-04-17 | 2018-03-06 | State Farm Mutual Automobile Insurance Company | Advanced vehicle operator intelligence system |
US11127086B2 (en) | 2014-05-20 | 2021-09-21 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US10055794B1 (en) | 2014-05-20 | 2018-08-21 | State Farm Mutual Automobile Insurance Company | Determining autonomous vehicle technology performance for insurance pricing and offering |
US10599155B1 (en) | 2014-05-20 | 2020-03-24 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
US10510123B1 (en) | 2014-05-20 | 2019-12-17 | State Farm Mutual Automobile Insurance Company | Accident risk model determination using autonomous vehicle operating data |
US9852475B1 (en) | 2014-05-20 | 2017-12-26 | State Farm Mutual Automobile Insurance Company | Accident risk model determination using autonomous vehicle operating data |
US9858621B1 (en) | 2014-05-20 | 2018-01-02 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle technology effectiveness determination for insurance pricing |
US9805423B1 (en) | 2014-05-20 | 2017-10-31 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US10504306B1 (en) | 2014-05-20 | 2019-12-10 | State Farm Mutual Automobile Insurance Company | Accident response using autonomous vehicle monitoring |
US11062396B1 (en) | 2014-05-20 | 2021-07-13 | State Farm Mutual Automobile Insurance Company | Determining autonomous vehicle technology performance for insurance pricing and offering |
US11869092B2 (en) | 2014-05-20 | 2024-01-09 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
US9792656B1 (en) | 2014-05-20 | 2017-10-17 | State Farm Mutual Automobile Insurance Company | Fault determination with autonomous feature use monitoring |
US11023629B1 (en) | 2014-05-20 | 2021-06-01 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature evaluation |
US10963969B1 (en) | 2014-05-20 | 2021-03-30 | State Farm Mutual Automobile Insurance Company | Autonomous communication feature use and insurance pricing |
US10185999B1 (en) | 2014-05-20 | 2019-01-22 | State Farm Mutual Automobile Insurance Company | Autonomous feature use monitoring and telematics |
US10748218B2 (en) | 2014-05-20 | 2020-08-18 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle technology effectiveness determination for insurance pricing |
US11080794B2 (en) | 2014-05-20 | 2021-08-03 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle technology effectiveness determination for insurance pricing |
US9972054B1 (en) | 2014-05-20 | 2018-05-15 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US9715711B1 (en) | 2014-05-20 | 2017-07-25 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle insurance pricing and offering based upon accident risk |
US11710188B2 (en) | 2014-05-20 | 2023-07-25 | State Farm Mutual Automobile Insurance Company | Autonomous communication feature use and insurance pricing |
US11669090B2 (en) | 2014-05-20 | 2023-06-06 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
US10026130B1 (en) | 2014-05-20 | 2018-07-17 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle collision risk assessment |
US10529027B1 (en) | 2014-05-20 | 2020-01-07 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
US10185998B1 (en) | 2014-05-20 | 2019-01-22 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US9646428B1 (en) | 2014-05-20 | 2017-05-09 | State Farm Mutual Automobile Insurance Company | Accident response using autonomous vehicle monitoring |
US10719886B1 (en) | 2014-05-20 | 2020-07-21 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US9767516B1 (en) | 2014-05-20 | 2017-09-19 | State Farm Mutual Automobile Insurance Company | Driver feedback alerts based upon monitoring use of autonomous vehicle |
US10373259B1 (en) | 2014-05-20 | 2019-08-06 | State Farm Mutual Automobile Insurance Company | Fully autonomous vehicle insurance pricing |
US10354330B1 (en) | 2014-05-20 | 2019-07-16 | State Farm Mutual Automobile Insurance Company | Autonomous feature use monitoring and insurance pricing |
US10089693B1 (en) | 2014-05-20 | 2018-10-02 | State Farm Mutual Automobile Insurance Company | Fully autonomous vehicle insurance pricing |
US10719885B1 (en) | 2014-05-20 | 2020-07-21 | State Farm Mutual Automobile Insurance Company | Autonomous feature use monitoring and insurance pricing |
US10319039B1 (en) | 2014-05-20 | 2019-06-11 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US10726499B1 (en) | 2014-05-20 | 2020-07-28 | State Farm Mutual Automoible Insurance Company | Accident fault determination for autonomous vehicles |
US11436685B1 (en) | 2014-05-20 | 2022-09-06 | State Farm Mutual Automobile Insurance Company | Fault determination with autonomous feature use monitoring |
US11282143B1 (en) | 2014-05-20 | 2022-03-22 | State Farm Mutual Automobile Insurance Company | Fully autonomous vehicle insurance pricing |
US11010840B1 (en) | 2014-05-20 | 2021-05-18 | State Farm Mutual Automobile Insurance Company | Fault determination with autonomous feature use monitoring |
US11580604B1 (en) | 2014-05-20 | 2023-02-14 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
US11288751B1 (en) | 2014-05-20 | 2022-03-29 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
US10726498B1 (en) | 2014-05-20 | 2020-07-28 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US11386501B1 (en) | 2014-05-20 | 2022-07-12 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US9754325B1 (en) | 2014-05-20 | 2017-09-05 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
US10223479B1 (en) | 2014-05-20 | 2019-03-05 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature evaluation |
US10185997B1 (en) | 2014-05-20 | 2019-01-22 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US10181161B1 (en) | 2014-05-20 | 2019-01-15 | State Farm Mutual Automobile Insurance Company | Autonomous communication feature use |
US9510191B2 (en) | 2014-06-20 | 2016-11-29 | Facebook, Inc. | Authorization of network address tracking |
US20160019651A1 (en) * | 2014-07-18 | 2016-01-21 | GM Global Technology Operations LLC | Method and apparatus of determining relative driving characteristics using vehicular participative sensing systems |
US9477989B2 (en) * | 2014-07-18 | 2016-10-25 | GM Global Technology Operations LLC | Method and apparatus of determining relative driving characteristics using vehicular participative sensing systems |
US9786154B1 (en) | 2014-07-21 | 2017-10-10 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
US9783159B1 (en) | 2014-07-21 | 2017-10-10 | State Farm Mutual Automobile Insurance Company | Methods of theft prevention or mitigation |
US10825326B1 (en) | 2014-07-21 | 2020-11-03 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
US10832327B1 (en) | 2014-07-21 | 2020-11-10 | State Farm Mutual Automobile Insurance Company | Methods of providing insurance savings based upon telematics and driving behavior identification |
US11030696B1 (en) | 2014-07-21 | 2021-06-08 | State Farm Mutual Automobile Insurance Company | Methods of providing insurance savings based upon telematics and anonymous driver data |
US11069221B1 (en) | 2014-07-21 | 2021-07-20 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
US10723312B1 (en) | 2014-07-21 | 2020-07-28 | State Farm Mutual Automobile Insurance Company | Methods of theft prevention or mitigation |
US10540723B1 (en) | 2014-07-21 | 2020-01-21 | State Farm Mutual Automobile Insurance Company | Methods of providing insurance savings based upon telematics and usage-based insurance |
US11634102B2 (en) | 2014-07-21 | 2023-04-25 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
US11565654B2 (en) | 2014-07-21 | 2023-01-31 | State Farm Mutual Automobile Insurance Company | Methods of providing insurance savings based upon telematics and driving behavior identification |
US10475127B1 (en) | 2014-07-21 | 2019-11-12 | State Farm Mutual Automobile Insurance Company | Methods of providing insurance savings based upon telematics and insurance incentives |
US10387962B1 (en) | 2014-07-21 | 2019-08-20 | State Farm Mutual Automobile Insurance Company | Methods of reconstructing an accident scene using telematics data |
US11634103B2 (en) | 2014-07-21 | 2023-04-25 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
US11257163B1 (en) | 2014-07-21 | 2022-02-22 | State Farm Mutual Automobile Insurance Company | Methods of pre-generating insurance claims |
US10102587B1 (en) | 2014-07-21 | 2018-10-16 | State Farm Mutual Automobile Insurance Company | Methods of pre-generating insurance claims |
US10974693B1 (en) | 2014-07-21 | 2021-04-13 | State Farm Mutual Automobile Insurance Company | Methods of theft prevention or mitigation |
US10997849B1 (en) | 2014-07-21 | 2021-05-04 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
US11068995B1 (en) | 2014-07-21 | 2021-07-20 | State Farm Mutual Automobile Insurance Company | Methods of reconstructing an accident scene using telematics data |
US9751535B1 (en) | 2014-09-23 | 2017-09-05 | State Farm Mutual Automobile Insurance Company | Real-time driver monitoring and feedback reporting system |
US9373203B1 (en) | 2014-09-23 | 2016-06-21 | State Farm Mutual Automobile Insurance Company | Real-time driver monitoring and feedback reporting system |
US9279697B1 (en) * | 2014-09-23 | 2016-03-08 | State Farm Mutual Automobile Insurance Company | Student driver feedback system allowing entry of tagged events by instructors during driving tests |
US10083626B1 (en) * | 2014-09-23 | 2018-09-25 | State Farm Mutual Automobile Insurance Company | Student driver feedback system allowing entry of tagged events by instructors during driving tests |
US9180888B1 (en) * | 2014-09-23 | 2015-11-10 | State Farm Mutual Automobile Insurance Company | Student driver feedback system allowing entry of tagged events by instructors during driving tests |
US10414408B1 (en) | 2014-09-23 | 2019-09-17 | State Farm Mutual Automobile Insurance Company | Real-time driver monitoring and feedback reporting system |
US9056616B1 (en) * | 2014-09-23 | 2015-06-16 | State Farm Mutual Automobile Insurance | Student driver feedback system allowing entry of tagged events by instructors during driving tests |
US9847043B1 (en) * | 2014-09-23 | 2017-12-19 | State Farm Mutual Automobile Insurance Company | Student driver feedback system allowing entry of tagged events by instructors during driving tests |
US9661552B2 (en) * | 2014-11-06 | 2017-05-23 | Facebook, Inc. | Association in line-of-sight communication networks |
US9806809B2 (en) | 2014-11-06 | 2017-10-31 | Facebook, Inc. | Deploying line-of-sight communication networks |
US11652550B2 (en) | 2014-11-06 | 2023-05-16 | Meta Platforms, Inc. | Deploying line-of-sight communication networks |
US10382127B2 (en) | 2014-11-06 | 2019-08-13 | Facebook, Inc. | Alignment in line-of-sight communication networks |
US9793988B2 (en) | 2014-11-06 | 2017-10-17 | Facebook, Inc. | Alignment in line-of-sight communication networks |
US20160135110A1 (en) * | 2014-11-06 | 2016-05-12 | Facebook, Inc. | Association in line-of-sight communication networks |
US11398863B2 (en) | 2014-11-06 | 2022-07-26 | Meta Platforms, Inc. | Alignment in line-of-sight communication networks |
US11173918B1 (en) | 2014-11-13 | 2021-11-16 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
US11954482B2 (en) | 2014-11-13 | 2024-04-09 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
US11720968B1 (en) | 2014-11-13 | 2023-08-08 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle insurance based upon usage |
US10431018B1 (en) | 2014-11-13 | 2019-10-01 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operating status assessment |
US9946531B1 (en) | 2014-11-13 | 2018-04-17 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle software version assessment |
US10416670B1 (en) | 2014-11-13 | 2019-09-17 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
US11726763B2 (en) | 2014-11-13 | 2023-08-15 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle automatic parking |
US11740885B1 (en) | 2014-11-13 | 2023-08-29 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle software version assessment |
US11748085B2 (en) | 2014-11-13 | 2023-09-05 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operator identification |
US10166994B1 (en) | 2014-11-13 | 2019-01-01 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operating status assessment |
US11127290B1 (en) | 2014-11-13 | 2021-09-21 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle infrastructure communication device |
US10007263B1 (en) | 2014-11-13 | 2018-06-26 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle accident and emergency response |
US10824144B1 (en) | 2014-11-13 | 2020-11-03 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
US10824415B1 (en) | 2014-11-13 | 2020-11-03 | State Farm Automobile Insurance Company | Autonomous vehicle software version assessment |
US11645064B2 (en) | 2014-11-13 | 2023-05-09 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle accident and emergency response |
US11014567B1 (en) | 2014-11-13 | 2021-05-25 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operator identification |
US10353694B1 (en) | 2014-11-13 | 2019-07-16 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle software version assessment |
US11494175B2 (en) | 2014-11-13 | 2022-11-08 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operating status assessment |
US10336321B1 (en) | 2014-11-13 | 2019-07-02 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
US9944282B1 (en) | 2014-11-13 | 2018-04-17 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle automatic parking |
US11175660B1 (en) | 2014-11-13 | 2021-11-16 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
US11247670B1 (en) | 2014-11-13 | 2022-02-15 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
US10821971B1 (en) | 2014-11-13 | 2020-11-03 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle automatic parking |
US11500377B1 (en) | 2014-11-13 | 2022-11-15 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
US10940866B1 (en) | 2014-11-13 | 2021-03-09 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operating status assessment |
US10831204B1 (en) | 2014-11-13 | 2020-11-10 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle automatic parking |
US10943303B1 (en) | 2014-11-13 | 2021-03-09 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operating style and mode monitoring |
US10157423B1 (en) | 2014-11-13 | 2018-12-18 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operating style and mode monitoring |
US10266180B1 (en) | 2014-11-13 | 2019-04-23 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
US10246097B1 (en) | 2014-11-13 | 2019-04-02 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operator identification |
US11532187B1 (en) | 2014-11-13 | 2022-12-20 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operating status assessment |
US10241509B1 (en) | 2014-11-13 | 2019-03-26 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
US10915965B1 (en) | 2014-11-13 | 2021-02-09 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle insurance based upon usage |
US10373523B1 (en) | 2015-04-29 | 2019-08-06 | State Farm Mutual Automobile Insurance Company | Driver organization and management for driver's education |
US10748446B1 (en) | 2015-05-04 | 2020-08-18 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and progress monitoring |
US9586591B1 (en) | 2015-05-04 | 2017-03-07 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and progress monitoring |
US9959780B2 (en) | 2015-05-04 | 2018-05-01 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and progress monitoring |
US10109218B2 (en) * | 2015-08-25 | 2018-10-23 | Toyota Motor Engineering & Manufacturing North America, Inc. | Systems and methods for driver coaching |
US20170061825A1 (en) * | 2015-08-25 | 2017-03-02 | Toyota Motor Engineering & Manufacturing North America, Inc. | Systems and methods for driver coaching |
US10026237B1 (en) | 2015-08-28 | 2018-07-17 | State Farm Mutual Automobile Insurance Company | Shared vehicle usage, monitoring and feedback |
US10950065B1 (en) | 2015-08-28 | 2021-03-16 | State Farm Mutual Automobile Insurance Company | Shared vehicle usage, monitoring and feedback |
US10343605B1 (en) | 2015-08-28 | 2019-07-09 | State Farm Mutual Automotive Insurance Company | Vehicular warning based upon pedestrian or cyclist presence |
US9805601B1 (en) | 2015-08-28 | 2017-10-31 | State Farm Mutual Automobile Insurance Company | Vehicular traffic alerts for avoidance of abnormal traffic conditions |
US9868394B1 (en) | 2015-08-28 | 2018-01-16 | State Farm Mutual Automobile Insurance Company | Vehicular warnings based upon pedestrian or cyclist presence |
US9870649B1 (en) | 2015-08-28 | 2018-01-16 | State Farm Mutual Automobile Insurance Company | Shared vehicle usage, monitoring and feedback |
US10769954B1 (en) | 2015-08-28 | 2020-09-08 | State Farm Mutual Automobile Insurance Company | Vehicular driver warnings |
US10325491B1 (en) | 2015-08-28 | 2019-06-18 | State Farm Mutual Automobile Insurance Company | Vehicular traffic alerts for avoidance of abnormal traffic conditions |
US10748419B1 (en) | 2015-08-28 | 2020-08-18 | State Farm Mutual Automobile Insurance Company | Vehicular traffic alerts for avoidance of abnormal traffic conditions |
US10242513B1 (en) | 2015-08-28 | 2019-03-26 | State Farm Mutual Automobile Insurance Company | Shared vehicle usage, monitoring and feedback |
US11450206B1 (en) | 2015-08-28 | 2022-09-20 | State Farm Mutual Automobile Insurance Company | Vehicular traffic alerts for avoidance of abnormal traffic conditions |
US11107365B1 (en) | 2015-08-28 | 2021-08-31 | State Farm Mutual Automobile Insurance Company | Vehicular driver evaluation |
US10163350B1 (en) | 2015-08-28 | 2018-12-25 | State Farm Mutual Automobile Insurance Company | Vehicular driver warnings |
US10977945B1 (en) | 2015-08-28 | 2021-04-13 | State Farm Mutual Automobile Insurance Company | Vehicular driver warnings |
US10019901B1 (en) | 2015-08-28 | 2018-07-10 | State Farm Mutual Automobile Insurance Company | Vehicular traffic alerts for avoidance of abnormal traffic conditions |
US10106083B1 (en) | 2015-08-28 | 2018-10-23 | State Farm Mutual Automobile Insurance Company | Vehicular warnings based upon pedestrian or cyclist presence |
US9914460B2 (en) * | 2015-09-25 | 2018-03-13 | Mcafee, Llc | Contextual scoring of automobile drivers |
US20170088142A1 (en) * | 2015-09-25 | 2017-03-30 | Mcafee, Inc. | Contextual scoring of automobile drivers |
US10026243B1 (en) | 2015-10-14 | 2018-07-17 | Allstate Insurance Company | Driver performance ratings |
US10304265B1 (en) | 2015-10-14 | 2019-05-28 | Arity International Limited | Driver performance ratings |
US9892573B1 (en) | 2015-10-14 | 2018-02-13 | Allstate Insurance Company | Driver performance ratings |
US10521983B1 (en) | 2015-10-14 | 2019-12-31 | Arity International Limited | Driver performance ratings |
US11721238B1 (en) | 2015-11-18 | 2023-08-08 | State Farm Mutual Automobile Insurance Company | System and method for determining a quality of driving of a vehicle |
US10720080B1 (en) * | 2015-11-18 | 2020-07-21 | State Farm Mutual Automobile Insurance Company | System and method for determining a quality of driving of a vehicle |
US11062414B1 (en) | 2016-01-22 | 2021-07-13 | State Farm Mutual Automobile Insurance Company | System and method for autonomous vehicle ride sharing using facial recognition |
US11682244B1 (en) | 2016-01-22 | 2023-06-20 | State Farm Mutual Automobile Insurance Company | Smart home sensor malfunction detection |
US10482226B1 (en) | 2016-01-22 | 2019-11-19 | State Farm Mutual Automobile Insurance Company | System and method for autonomous vehicle sharing using facial recognition |
US10469282B1 (en) | 2016-01-22 | 2019-11-05 | State Farm Mutual Automobile Insurance Company | Detecting and responding to autonomous environment incidents |
US10395332B1 (en) | 2016-01-22 | 2019-08-27 | State Farm Mutual Automobile Insurance Company | Coordinated autonomous vehicle automatic area scanning |
US10802477B1 (en) | 2016-01-22 | 2020-10-13 | State Farm Mutual Automobile Insurance Company | Virtual testing of autonomous environment control system |
US10493936B1 (en) | 2016-01-22 | 2019-12-03 | State Farm Mutual Automobile Insurance Company | Detecting and responding to autonomous vehicle collisions |
US11920938B2 (en) | 2016-01-22 | 2024-03-05 | Hyundai Motor Company | Autonomous electric vehicle charging |
US11119477B1 (en) | 2016-01-22 | 2021-09-14 | State Farm Mutual Automobile Insurance Company | Anomalous condition detection and response for autonomous vehicles |
US11126184B1 (en) | 2016-01-22 | 2021-09-21 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle parking |
US11124186B1 (en) | 2016-01-22 | 2021-09-21 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control signal |
US10384678B1 (en) | 2016-01-22 | 2019-08-20 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle action communications |
US10386845B1 (en) | 2016-01-22 | 2019-08-20 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle parking |
US10386192B1 (en) | 2016-01-22 | 2019-08-20 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle routing |
US11879742B2 (en) | 2016-01-22 | 2024-01-23 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
US10824145B1 (en) | 2016-01-22 | 2020-11-03 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle component maintenance and repair |
US10503168B1 (en) | 2016-01-22 | 2019-12-10 | State Farm Mutual Automotive Insurance Company | Autonomous vehicle retrieval |
US10324463B1 (en) | 2016-01-22 | 2019-06-18 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation adjustment based upon route |
US11181930B1 (en) | 2016-01-22 | 2021-11-23 | State Farm Mutual Automobile Insurance Company | Method and system for enhancing the functionality of a vehicle |
US11189112B1 (en) | 2016-01-22 | 2021-11-30 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle sensor malfunction detection |
US10829063B1 (en) | 2016-01-22 | 2020-11-10 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle damage and salvage assessment |
US10828999B1 (en) | 2016-01-22 | 2020-11-10 | State Farm Mutual Automobile Insurance Company | Autonomous electric vehicle charging |
US11242051B1 (en) | 2016-01-22 | 2022-02-08 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle action communications |
US10747234B1 (en) | 2016-01-22 | 2020-08-18 | State Farm Mutual Automobile Insurance Company | Method and system for enhancing the functionality of a vehicle |
US11022978B1 (en) | 2016-01-22 | 2021-06-01 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle routing during emergencies |
US10308246B1 (en) | 2016-01-22 | 2019-06-04 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle signal control |
US11015942B1 (en) | 2016-01-22 | 2021-05-25 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle routing |
US10295363B1 (en) | 2016-01-22 | 2019-05-21 | State Farm Mutual Automobile Insurance Company | Autonomous operation suitability assessment and mapping |
US11348193B1 (en) | 2016-01-22 | 2022-05-31 | State Farm Mutual Automobile Insurance Company | Component damage and salvage assessment |
US10249109B1 (en) | 2016-01-22 | 2019-04-02 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle sensor malfunction detection |
US11016504B1 (en) | 2016-01-22 | 2021-05-25 | State Farm Mutual Automobile Insurance Company | Method and system for repairing a malfunctioning autonomous vehicle |
US10185327B1 (en) | 2016-01-22 | 2019-01-22 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle path coordination |
US11441916B1 (en) | 2016-01-22 | 2022-09-13 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle trip routing |
US10545024B1 (en) | 2016-01-22 | 2020-01-28 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle trip routing |
US10691126B1 (en) | 2016-01-22 | 2020-06-23 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle refueling |
US10168703B1 (en) | 2016-01-22 | 2019-01-01 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle component malfunction impact assessment |
US10579070B1 (en) | 2016-01-22 | 2020-03-03 | State Farm Mutual Automobile Insurance Company | Method and system for repairing a malfunctioning autonomous vehicle |
US9940834B1 (en) | 2016-01-22 | 2018-04-10 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
US11719545B2 (en) | 2016-01-22 | 2023-08-08 | Hyundai Motor Company | Autonomous vehicle component damage and salvage assessment |
US11513521B1 (en) | 2016-01-22 | 2022-11-29 | State Farm Mutual Automobile Insurance Copmany | Autonomous vehicle refueling |
US11526167B1 (en) | 2016-01-22 | 2022-12-13 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle component maintenance and repair |
US10679497B1 (en) | 2016-01-22 | 2020-06-09 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
US10156848B1 (en) | 2016-01-22 | 2018-12-18 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle routing during emergencies |
US10818105B1 (en) | 2016-01-22 | 2020-10-27 | State Farm Mutual Automobile Insurance Company | Sensor malfunction detection |
US10134278B1 (en) | 2016-01-22 | 2018-11-20 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
US11656978B1 (en) | 2016-01-22 | 2023-05-23 | State Farm Mutual Automobile Insurance Company | Virtual testing of autonomous environment control system |
US10042359B1 (en) | 2016-01-22 | 2018-08-07 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle refueling |
US11600177B1 (en) | 2016-01-22 | 2023-03-07 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
US10065517B1 (en) | 2016-01-22 | 2018-09-04 | State Farm Mutual Automobile Insurance Company | Autonomous electric vehicle charging |
US11625802B1 (en) | 2016-01-22 | 2023-04-11 | State Farm Mutual Automobile Insurance Company | Coordinated autonomous vehicle automatic area scanning |
US10086782B1 (en) | 2016-01-22 | 2018-10-02 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle damage and salvage assessment |
US11138524B2 (en) * | 2016-03-11 | 2021-10-05 | Uber Technologies, Inc. | Cascaded boosted predictive models |
US11000953B2 (en) * | 2016-08-17 | 2021-05-11 | Locus Robotics Corp. | Robot gamification for improvement of operator performance |
US11232655B2 (en) | 2016-09-13 | 2022-01-25 | Iocurrents, Inc. | System and method for interfacing with a vehicular controller area network |
US10650621B1 (en) | 2016-09-13 | 2020-05-12 | Iocurrents, Inc. | Interfacing with a vehicular controller area network |
US10157509B2 (en) | 2016-12-28 | 2018-12-18 | Conduent Business Services, Llc | System for public transit incident rate analysis and display |
US20200152067A1 (en) * | 2018-11-13 | 2020-05-14 | Toyota Motor North America, Inc. | Systems and methods for determining actual operating conditions of fleet cars |
US11482110B2 (en) * | 2018-11-13 | 2022-10-25 | Toyota Motor North America, Inc. | Systems and methods for determining actual operating conditions of fleet cars |
US11593539B2 (en) | 2018-11-30 | 2023-02-28 | BlueOwl, LLC | Systems and methods for facilitating virtual vehicle operation based on real-world vehicle operation data |
US20210241506A1 (en) * | 2018-12-19 | 2021-08-05 | EffectiveTalent Office LLC | Matched array general talent architecture system and method |
US11508103B2 (en) * | 2018-12-19 | 2022-11-22 | EffectiveTalent Office LLC | Matched array general talent architecture system and method |
US11107305B2 (en) | 2019-03-14 | 2021-08-31 | Honda Motor Co., Ltd. | Ride-hailing vehicle identification |
US11250650B2 (en) * | 2019-03-14 | 2022-02-15 | Honda Motor Co., Ltd. | Ride-hailing vehicle identification |
US11572067B2 (en) | 2019-08-30 | 2023-02-07 | 7980302 Canada Inc. | Using ISA system to decelerate truck upon entering geofenced area |
US11691084B2 (en) | 2020-01-20 | 2023-07-04 | BlueOwl, LLC | Systems and methods for training and applying virtual occurrences to a virtual character using telematics data of one or more real trips |
US11707683B2 (en) | 2020-01-20 | 2023-07-25 | BlueOwl, LLC | Systems and methods for training and applying virtual occurrences and granting in-game resources to a virtual character using telematics data of one or more real trips |
US11857866B2 (en) | 2020-01-20 | 2024-01-02 | BlueOwl, LLC | Systems and methods for training and applying virtual occurrences with modifiable outcomes to a virtual character using telematics data of one or more real trips |
US11590427B1 (en) * | 2020-03-19 | 2023-02-28 | BlueOwl, LLC | Systems and methods for tournament-based telematics insurance pricing |
US20210334727A1 (en) * | 2020-04-26 | 2021-10-28 | Paccar Inc | Fleet-specific performance impact of vehicle configuration |
US11702083B2 (en) * | 2020-06-11 | 2023-07-18 | 7980302 Canada Inc. | Using ISA system to implement a speed policy identified based on profile of a driving instance |
US20210387629A1 (en) * | 2020-06-11 | 2021-12-16 | 7980302 Canada Inc. | Using isa system to implement a speed policy identified based on profile of a driving instance |
US11597276B2 (en) * | 2021-02-19 | 2023-03-07 | Taipale Telematics Oy | Device, a method, and a computer program for determining the driving behavior of a driver |
US11504622B1 (en) * | 2021-08-17 | 2022-11-22 | BlueOwl, LLC | Systems and methods for generating virtual encounters in virtual games |
US11697069B1 (en) | 2021-08-17 | 2023-07-11 | BlueOwl, LLC | Systems and methods for presenting shared in-game objectives in virtual games |
US11896903B2 (en) | 2021-08-17 | 2024-02-13 | BlueOwl, LLC | Systems and methods for generating virtual experiences for a virtual game |
US11918913B2 (en) | 2021-08-17 | 2024-03-05 | BlueOwl, LLC | Systems and methods for generating virtual encounters in virtual games |
Also Published As
Publication number | Publication date |
---|---|
US9412282B2 (en) | 2016-08-09 |
US20160342924A1 (en) | 2016-11-24 |
US20130164714A1 (en) | 2013-06-27 |
US20160342926A1 (en) | 2016-11-24 |
US20160342925A1 (en) | 2016-11-24 |
US20160350693A1 (en) | 2016-12-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10102096B2 (en) | Method and apparatus for GPS based Z-axis difference parameter computation | |
US9527515B2 (en) | Vehicle performance based on analysis of drive data | |
US9412282B2 (en) | Using social networking to improve driver performance based on industry sharing of driver performance data | |
US8918229B2 (en) | Method and apparatus for 3-D accelerometer based slope determination, real-time vehicle mass determination, and vehicle efficiency analysis | |
US10289651B2 (en) | Method and apparatus for matching vehicle ECU programming to current vehicle operating conditions | |
US9747254B2 (en) | Method and apparatus for matching vehicle ECU programming to current vehicle operating conditions | |
US9229906B2 (en) | Method and apparatus for matching vehicle ECU programming to current vehicle operating conditions | |
US10223935B2 (en) | Using telematics data including position data and vehicle analytics to train drivers to improve efficiency of vehicle use | |
US7769499B2 (en) | Generating a numerical ranking of driver performance based on a plurality of metrics | |
US8862346B2 (en) | System and method for simulating the performance of a virtual vehicle | |
US8682572B2 (en) | Method and device for evaluating vehicle's fuel consumption efficiency | |
US6931309B2 (en) | Motor vehicle operating data collection and analysis | |
CN103717470B (en) | Fuel saving-aimed motor vehicle driving style evaluation | |
EP2036777B1 (en) | Method and system of providing driving data to a driver of a vehicle | |
US9513151B2 (en) | Fuel waste variable identification and analysis system | |
US20210302183A1 (en) | Vehicle efficiency prediction and control |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., CALIFORNIA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:ZONAR SYSTEMS, INC.;REEL/FRAME:034274/0129 Effective date: 20141023 |
|
AS | Assignment |
Owner name: ZONAR SYSTEMS, INC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HUNT, BRYAN;MCQUADE, CHARLES MICHAEL;REEL/FRAME:037253/0038 Effective date: 20150511 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: ZONAR SYSTEMS, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A.;REEL/FRAME:040512/0099 Effective date: 20161028 |