Fleet management efficiency visualization

Through the combination of power transmission system controller and processor, the use of fuel in the vehicle is monitored and waste in the idle time period is identified, the impact of driving habits on fuel efficiency is solved, the identification and reduction of fuel waste is achieved, and the fuel use efficiency of the fleet is improved .

CN109712264BActive Publication Date: 2024-11-05FORD MOTOR CO
View PDF 12 Cites 0 Cited by

Patent Information

Application Number
CN201811217877.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2017-10-25
Filing Date
2018-10-18
Publication Date
2024-11-05
Estimated Expiration
2038-10-18

AI Technical Summary

Technical Problem

The impact of driving habits on vehicle fuel efficiency is difficult to effectively monitor and optimize, resulting in difficult identification and reduction of fleet fuel waste.

Method used

A system is designed to provide fuel pump actuator signals to the vehicle bus through a power transmission system controller, and accumulate fuel usage data by the processor. Combined with vehicle speed, engine speed and position, it is periodically sent to a remote server to identify Fuel waste during idle time period, and money waste is calculated, and a report is generated.

Benefits of technology

Accurate monitoring of vehicle fuel use and identification of waste behaviors, providing cost insights, helping fleet administrators improve driving habits, reduce fuel waste, and improve fuel efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN109712264B_ABST
    Figure CN109712264B_ABST
Patent Text Reader

Abstract

A powertrain controller of a vehicle provides a fuel pump actuator signal indicative of fuel flow to a vehicle bus. A processor is configured to receive data from the vehicle bus. The processor performs integration of the actuator signal to accumulate fuel usage of the vehicle, and periodically sends the accumulated fuel usage, vehicle speed, engine speed, engine status, and vehicle location to a remote server. A subset of accumulated fuel usage is retrieved for a group of the vehicles of a fleet traversing a route during a certain time range, the accumulated fuel usage compiled from the fuel pump actuator signal. Fuel waste is calculated for identified idling time periods within the accumulated fuel usage. Monetary waste is calculated based on the fuel waste. A report including the monetary waste is generated.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Aspects of the present disclosure generally relate to vehicle efficiency visualization for fleet management. Background Art

[0002] Hybrid electric powertrains, vehicle aerodynamics, weight budgets, and low rolling resistance tires contribute to overall vehicle fuel efficiency. Despite these technological advances, driving habits continue to influence the amount of fuel a vehicle consumes. For example, speeding, rapid acceleration, rapid braking, and excessive idling use more fuel than would otherwise be required. Because fuel efficiency is a priority in purchasing and managing vehicles, advances in technology and improvements in driver habits are factors to consider when improving fleet fuel efficiency. Summary of the invention

[0003] In one or more illustrative embodiments, a system includes: a powertrain controller of a vehicle, the powertrain controller configured to provide a fuel pump actuator signal indicating fuel flow to a vehicle bus; and a processor, the processor configured to receive data from the vehicle bus, programmed to perform integration of the actuator signal to accumulate fuel usage of the vehicle, and periodically send the accumulated fuel usage, vehicle speed, engine speed, engine status, and vehicle location to a remote server.

[0004] In one or more illustrative embodiments, a system includes: a memory storing cumulative fuel usage compiled from fuel pump actuator signals for vehicles of a fleet; and a processor of a server programmed to retrieve a subset of cumulative fuel usage for a group of vehicles traversing a route during a time range, calculate fuel waste within identified idling time periods within the cumulative fuel usage, calculate monetary waste based on the fuel waste, and generate a report including the monetary waste.

[0005] In one or more illustrative embodiments, a method includes: retrieving a subset of cumulative fuel usage of a group of vehicles of a fleet traversing a route during a time range, the cumulative fuel usage compiled from fuel pump actuator signals; calculating fuel waste during identified idling time periods within the cumulative fuel usage; calculating monetary waste based on the fuel waste; and generating a report including the monetary waste. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1A An exemplary system for monitoring vehicle fuel usage on a predefined route to identify wasted fuel costs is shown;

[0007] Figure 1BAn alternative exemplary system for monitoring vehicle fuel usage on a predefined route to identify wasted fuel costs is shown;

[0008] Figure 2 An example of a data report showing fuel waste by route is shown;

[0009] Figure 3 An example of a data report with expanded details for a vehicle showing fuel waste by route is shown;

[0010] Figure 4 An example of a data report for displaying details of a selected route traversal of a vehicle is shown;

[0011] Figure 5 illustrates an exemplary process for sending aggregated data from a vehicle to a remote server; and

[0012] Figure 6 An exemplary process for displaying a fuel waste data report by route based on aggregated data is shown. DETAILED DESCRIPTION

[0013] As required, detailed embodiments of the present invention are disclosed herein; however, it should be understood that the disclosed embodiments are merely examples of the present invention that may be embodied in various forms and alternative forms. The drawings are not necessarily drawn to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, the specific structural and functional details disclosed herein should not be interpreted as limiting, but merely as a representative basis for teaching those skilled in the art to employ the present invention in various ways.

[0014] Figure 1AAn exemplary system 100A for monitoring fuel usage of a vehicle 102 on a predefined route to identify waste fuel costs is shown. As shown, the system includes one or more vehicles 102 of a fleet communicating with a remote server 128 via a communication network 122. The remote server 128 receives aggregated data 126 from each of the vehicles 102. The remote server 128 also performs analysis on the aggregated data 126 to generate a data report 140. The aggregated data 126 includes precise fuel usage information from the vehicle 102, which is compiled from fuel pump 118 data provided by a powertrain controller 116; and other information, such as vehicle speed, engine speed, engine on / off status, and / or vehicle location. The data report 140 includes data accumulation for various routes according to the stored route assignments 152 of the vehicle 102. The data report 140 also ranks the drivers of the vehicle 102 based on their performance against the waste average for the route. Using this data, the system 100 can identify wasteful driver behavior, such as excessive idling. Thus, the system 100 can provide information about how a driver performs when measured against other drivers with the same route pattern. The data report 140 can be accessed by a display device 144 to allow the operator of the device to understand behaviors that should be changed, as well as provide fleet managers with insights into the costs of identified wasteful behaviors. Additional aspects of the system 100 are discussed in detail below.

[0015] The vehicle 102 of the system 100 may include a fleet of trucks. In other examples, the vehicle 102 may include various other types of passenger vehicles, such as sedans, crossover utility vehicles (CUVs), sport utility vehicles (SUVs), trucks, recreational vehicles (RVs), or other mobile machinery for transporting people or goods. In many cases, the vehicle 102 may be powered by an internal combustion engine. In such cases, the fuel source may be gasoline or diesel fuel. As another possibility, the vehicle 102 may be a hybrid electric vehicle (HEV) powered by an internal combustion engine and one or more electric motors, such as a series hybrid electric vehicle (SHEV), a parallel hybrid electric vehicle (PHEV), or a parallel / series hybrid electric vehicle (PSHEV). Since the type and configuration of the vehicle 102 may vary, the capabilities of the vehicle 102 may vary accordingly. As some other possibilities, the vehicle 102 may have different capabilities regarding passenger capacity, traction capacity and capacity, and storage capacity. For title, inventory, and other purposes, the vehicle 102 may be associated with a unique identifier, such as a vehicle identification number (VIN).

[0016] The telematics controller 104 of the vehicle 102 may be configured to provide telematics services to the vehicle 102. As some non-limiting possibilities, these services may include navigation, turn-by-turn directions, vehicle health reports, local business searches, accident reports, and hands-free calling. The telematics controller 104 may include one or more processors 106 configured to execute instructions, commands, and other programs that support the processes described herein. Such instructions and other data may be maintained in a non-volatile manner using a variety of types of computer-readable storage media 108. Data may be loaded from the storage media 108 into the memory 110 for access by the processor 106. The computer-readable storage media 108 (also referred to as processor-readable media or storage media) includes any non-transitory media (e.g., tangible media) that participates in providing instructions or other data that can be read by the processor 106 of the telematics controller 104. Computer-executable instructions may be compiled or interpreted by a computer program created using a variety of programming languages ​​and / or techniques, including, but not limited to, Java, C, C++, C#, Objective C, Fortran, Pascal, JavaScript, Python, Perl, and PL / SQL, either alone or in combination.

[0017] The vehicle bus 112 may include various communication methods available between the telematics controller 104 and other components of the vehicle 102. For example, as some examples, the vehicle bus 112 may include one or more of a vehicle controller area network (CAN), an Ethernet network, or a media-oriented system transport (MOST) network. The vehicle 102 may include various vehicle controllers that communicate via the vehicle bus 112. As shown, these controllers may include a global positioning controller 114 and a powertrain controller 116. As some other examples, the controllers may include a body control module configured to manage various power control functions such as exterior lighting, interior lighting, keyless entry, remote start, and access point status verification (e.g., the closed state of the hood, doors, and / or trunk of the vehicle 102); a radio transceiver module configured to communicate with a key fob or other local vehicle 102 device; and a climate control management module configured to provide control and monitoring of heating and cooling system components (e.g., compressor clutch and blower control, temperature sensor information, etc.). The controllers shown are represented as discrete modules and systems. However, the controllers may share physical hardware, firmware, and / or software, such that functionality from multiple controllers may be integrated into a single controller, and functionality of various such controllers may be distributed across multiple controllers.

[0018] The global positioning controller 114 may be configured to provide current vehicle 102 location and heading information to the vehicle bus 112. This information may allow various vehicle 102 features to understand the vehicle's 102 current physical location and heading.

[0019] The powertrain controller 116 may be configured to provide control of components associated with the vehicle powertrain. As some examples, these engine operating components may include idle control components, fuel delivery components, and emission control components. The powertrain controller 116 may also provide monitoring of engine operating components, such as providing information about engine status, engine diagnostic codes, engine revolutions per minute (RPM), engine fuel usage, and engine torque, etc. The powertrain controller 116 may provide this information to the vehicle bus 112.

[0020] The fuel pump 118 may be configured to provide a fuel flow to the engine and may be one of the components controlled via the powertrain controller 116. The actuator of the fuel pump 118 may be driven by a pulse width modulated (PWM) signal generated by the powertrain controller 116. The powertrain controller 116 may adjust the PWM signal based on a number of factors, particularly through throttle control.

[0021] To allow monitoring of fuel usage, the powertrain controller 116 may provide a PWM signal or information indicative of a PWM signal to the vehicle bus 112. Since the fuel information provided to the vehicle bus 112 is based on the actual signal controlling the fuel pump 118, the amount of fuel used can be measured with a low error margin (approximately 1% in some cases). This fuel consumption measurement is more accurate than the fuel consumption estimate estimated based on air flow, throttle position, and data set mapping.

[0022] The telematics controller 104 may communicate with the embedded modem 120 to facilitate communication of the vehicle 102 over the communication network 122. The communication network 122 may provide communication services, such as packet-switched network services (e.g., Internet access, Voice over Internet Protocol (VoIP) communication services) to devices connected to the communication network 122. An example of a communication network 122 is a cellular telephone network. For example, the embedded modem 120 may access a cellular network via connection to one or more cellular towers. To facilitate communication over the communication network 122, the embedded modem 120 may be associated with a unique device identifier (e.g., a mobile device number (MDN), an Internet Protocol (IP) address, etc.) to identify the communication of the embedded modem 120 over the communication network as being associated with the vehicle 102. To support telematics services, the telematics controller 104 may utilize the embedded modem 120 to facilitate networked communications between the vehicle 102 and devices external to the vehicle 102.

[0023] The data reporting application 124 may be an application installed to the storage medium 108 of the telematics controller 104. When executed by the telematics controller 104, the data reporting application 124 may include instructions that cause the telematics controller 104 to monitor the state of the vehicle 102 (e.g., whether the engine is on or off) and to monitor the fuel flow of the engine to determine how the fuel is flowing. The engine state may be determined based on state information provided by the powertrain controller 116 via the vehicle bus 112. The fuel flow may be determined based on a PWM signal issued by the powertrain controller 116 via the vehicle bus 112.

[0024] The data reporting application 124 may also include instructions for causing the telematics controller 104 to generate aggregate data 126 based on the received data. The aggregate data 126 may include the amount of fuel used (e.g., based on the integration of the received PWM data). The aggregate data 126 may also include other information captured from the vehicle bus 112, such as vehicle speed, engine speed, engine on / off status, vehicle identifier (e.g., VIN), and / or vehicle location (e.g., provided from the global positioning controller 114).

[0025] The data reporting application 124 may provide two transmission mechanisms for providing aggregate data 126: a periodic transmission of fuel used since the last reset of the telematics controller 104, and a transmission of a trip summary. The trip summary includes the fuel consumed for the current trip. Both of these transmissions may be provided as configurable parameters to reduce the likelihood of packet loss on the communication network 122. For example, the vehicle 102 may have cellular coverage throughout the route. However, in other cases, the route may traverse tunnels or other areas where connectivity is unavailable or unreliable. Therefore, by sending an aggregate accumulation of fuel used, the total fuel used may be reconstructed by the recipient regardless of whether one or more transmissions along the route are lost.

[0026] The remote server 128 may include computing hardware configured to provide data processing and reporting services to the vehicles 102 of the fleet. The remote server 128 may include various types of computing devices, such as a computer workstation, a server, a desktop computer, a virtual server instance executed by a mainframe server, or some other computing system and / or device. Similar to the telematics controller 104, the remote server 128 generally includes a storage device 132 on which computer executable instructions and data may be maintained, wherein the instructions may be executed by one or more processors 130, and the data and instructions may be loaded into a memory 134. The remote server 128 may be configured to store various data, such as the aggregated data 126 received from the vehicle 102.

[0027] The remote server 128 may also be configured to store route assignments 136 for the vehicles 102. For example, the vehicles 102 of the fleet may be driven to predefined routes, which may each be assigned a route identifier. When a vehicle 102 is assigned to travel on a particular route, an entry may be added to the route assignment 136 to specify which route. For example, the entry may include an identifier of the user (e.g., a unique identifier of the user), an identifier of the vehicle (e.g., a VIN or other identifier of the vehicle 102), an identifier of the route, and the time at which the vehicle 102 is expected to travel on the route.

[0028] The report generator application 138 may be an application included on the storage device 132 of the remote server 128. Generally, the report generator application 138 may include instructions that, when loaded into the memory and executed by the remote server 128, cause the remote server 128 to generate a data report 140 based on the aggregated data 126 received from the vehicle 102 and the route assignment 136 of the vehicle 102.

[0029] For example, the report generator application 138 may receive a request for a report including a route selection (e.g., one of the routes identified in the route assignment 136), and may retrieve aggregated data 126 corresponding to the vehicle 102 traversing the route over a period of time from the storage device 132. The time period may be specified in the request for the report, or may default to a predefined time period, such as the previous day, the previous week, the previous month, or all time. The vehicle 102 to be included in the route data set may be identified based on a query of the route assignment 136 for the vehicle 102 that traversed the selected route during the indicated time period. Thus, the report generator application 138 may query the stored data to retrieve aggregated data 126 for the vehicle 102 and the time range of the requested route report.

[0030] Using the selected data, the report generator application 138 can calculate the average fuel usage for the route traversed by the vehicles 102. In an example, this can be a simple average of the total fuel consumed by all vehicles 102 divided by the total number of vehicles 102. The report generator application 138 can also calculate an efficiency score (e.g., miles per gallon, gallons per liter, etc.) based on the fuel used and the total distance traveled by the corresponding vehicles 102.

[0031] In addition, the report generator application 138 may determine the amount of waste for each vehicle 102. For example, the amount of waste may include the amount of fuel wasted during the idling time of the vehicle 102. To determine the amount of fuel wasted during idling, the report generator application 138 first identifies the time period during the route when the vehicle 102 is idling. Using this determination, the report generator application 138 assigns the fuel usage during these idling times to a fuel waste category. It should be noted that while many of the examples herein relate to fuel waste, the amount of waste is not limited to fuel and may be applied to other routine maintenance items, such as oil or powertrain wear.

[0032] For example, the report generator application 138 may identify the vehicle 102 as idling based on factors including geographic location, vehicle speed, and engine RPM. As a non-limiting example, if the vehicle speed is zero (or below a predefined speed) and the fuel consumption is greater than zero, then the vehicle 102 may be identified as idling. Using the aggregated data 126, the report generator application 138 accumulates the fuel usage during these idling times and determines a fuel waste measure based on the units of fuel used (e.g., gallons of fuel).

[0033] In order to provide the fleet operator with a measure of waste in terms of cost, the report generator application 138 may determine the dollar cost of waste for each vehicle 102. For example, the report generator application 138 may multiply the fuel used during the idling event by the dollar cost per unit of fuel (e.g., $4 per gallon of gasoline). In an example, the dollar costs for various geographic areas (such as metropolitan areas) may be predefined. In another example, the dollar cost may be entered by a user, or may be queried from the Internet using a service that provides local vehicle 102 fuel costs. The report generator application 138 may also rank the vehicles 102 in order from best to worst (or worst to best) fuel waste cost on the route.

[0034] The report server 142 may be another application included on the storage device 132 of the remote server 128. The report server 142 may include an interface to the report generator application 138 that may be accessed using a display device 144 that communicates with the remote server 128 via the communication network 122. When accessed, the report server 142 may be configured to allow a user of the display device 144 to access, view, and interact with various aspects of the information of the data report 140. In an example, the report server 142 may be a web server configured to support querying and displaying the data report 140 via a hypertext transfer protocol (HTTP). In another example, the report server 142 may be configured to support the data report 140 in a proprietary format via a thick client application (not shown) installed to the display device 144.

[0035] The display device 144 may include various devices that allow a user to access the report server 142 provided by the remote server 128 via the communication network 122. As some examples, the display device 144 may include a laptop computer, a tablet or other handheld computer, a mobile phone, a computer workstation, a server, a desktop computer, or some other computing system and / or device. Additional aspects of operating the display device 144 to view the data report 140 will be described with reference to FIG. Figures 2 to 4 As another possibility, the message delivery can be performed to the user himself via the HMI of the vehicle 102. In one example, when there is a message, a ringing effect can be provided in the cabin of the vehicle 102, or an indicator can be displayed in the instrument panel.

[0036] Figure 1B An alternative exemplary system 100B is shown for monitoring vehicle fuel usage on a predefined route to identify fuel waste costs. Compared to system 100A, system 100B includes a dongle 146 that communicates with vehicle bus 112 via a data port 148 (e.g., an OBD-II port). In system 100B, dongle 146 performs the data collection, aggregation, and transmission functions described as being performed by telematics controller 104 in system 100A.

[0037] Other variations of the system 100A and the system 100B are possible. For example, the operations described as being performed by the remote server 128 may be performed by multiple server devices. For example, a data storage server may receive and maintain aggregate data 126 and route assignments 136, while a data reporting server may execute a report generation application 138 and a reporting server 142. In such an example, the data reporting server may query the data storage server for relevant aggregate data 126 via a data interface or API exposed by the data storage server.

[0038] Figure 2 An example 200 of a data report 140 for displaying fuel waste by route is shown. In the example, the data report 140 may be displayed to a screen of a display device 144. The display device 144 may communicate with a remote server 128 via the communication network 122.

[0039] As shown, the data report 140 includes a title 202 indicating that the displayed data report 140 is related to fuel waste by route. The data report 140 also includes controls from which report criteria can be selected. For example, the data report 140 can include a route selection control 204 that includes a list of routes in which report data can be displayed; and a time range control 206 for selecting a time period for analyzing the vehicle 102 traversing the selected route. In one example, a route can be selected from the route selection control 204 according to a name assigned to the route, and a time period can be selected by week.

[0040] Based on the selected criteria, the data report 140 also includes a report details control 208. The report details control 208 may include a list of each of the vehicles 102 that have traversed the selected route within the selected time range, as well as details of the fuel efficiency of the vehicles 102. For example, for each vehicle 102, the report details control 208 may include the name or other identifier of the vehicle 102 (e.g., "Truck 123"), the distance traveled by the vehicle 102 (e.g., in miles), the amount of fuel used by the vehicle 102 in traversing the traveled distance (e.g., in gallons), and the efficiency of the vehicle 102 calculated using the traveled distance and the fuel used (e.g., in miles per gallon).

[0041] In addition, the report details control 208 may also include details related to the fuel waste of the vehicles 102. For example, for each vehicle 102, the report details control 208 may display a waste calculation in monetary units (e.g., dollars) and a graphical representation of the amount of waste for the vehicle 102 in the data report 140 compared to the average amount of waste. In one example, the graphical representation may include a bar shown with a size proportional to the amount of waste identified for the corresponding vehicle 102, and an average waste indication placed along the position of the bar for average vehicle 102 waste. In addition, bars that exceed the average waste indication may be displayed with a first appearance (e.g., a color such as red, a first pattern, etc.), while bars that do not exceed the average waste indication may be displayed with a second appearance (e.g., a color such as yellow, a second pattern, etc.). The report details control 208 may also provide an indication of the currency of the average waste amount, which is shown in the label of the waste column in the example shown.

[0042] Since the time period of the data report 140 may include multiple traversals of a route by a single vehicle 102, the data shown for each vehicle 102 may be an aggregation of data from multiple traversals of the selected route. The report details control 208 may also allow a user to expand the information shown for the selected vehicle 102 to allow the data report 140 to display data about various routes. For example, each vehicle 102 record may include an expansion control 210 that, when selected, causes the corresponding vehicle 102 record to be expanded.

[0043] As another example, the data report may include providing a fleet manager or driver with tips on what actions may be performed to improve fuel efficiency. In an example, poor fuel economy may be due to excessive idling or may be due to poor powertrain operation that negatively affects fuel. As yet another example, tips may be provided on how to avoid idling events, such as by introducing ideas for improving operating procedures or by providing suggested changes to routes.

[0044] Figure 3 An example 300 of a data report 140 showing fuel waste by route with expanded details for a vehicle 102 is shown. In response to a user selecting the expanded control 210 for the "Truck 263" vehicle 102 in example 200, the data report 140 in example 300 may be presented.

[0045] As shown, extended data 302 about the multiple traversals of the selected route by the extended vehicle 102 is provided in the report details control 208. These additional details include, for example, data for each traversal of the route that is incorporated into the overall vehicle 102 information. For each traversal, the extended data 302 may include a time range for the traversal (e.g., date and / or time), a distance traveled by the vehicle 102 (e.g., in miles), an amount of fuel used by the vehicle 102 when traversing the traveled distance (e.g., in gallons), an efficiency of the vehicle 102 calculated using the traveled distance and the used fuel (e.g., in miles per gallon), and a waste calculation in monetary units (e.g., dollars). It can be seen that, although the efficiency of each traversal may be different, the sum of the traveled distance, used fuel, and waste for each route adds up to a total for each vehicle 102 overall.

[0046] The extended data 302 may also allow a user to view details of each vehicle 102 route traversal in the displayed extended information for the selected vehicle 102. For example, each route in the extended data 302 may include a details control 304 that, when selected, causes a details view of the selected route traversal to be displayed.

[0047] Figure 4An example 400 of a data report 140 is shown for displaying details of a selected route traversal of the vehicle 102. In response to a user selecting the details control 304 of the "Monday, June 5" route traversal in the example 300, the data report 140 in the example 400 may be presented.

[0048] As shown, details pane 402 includes additional information about the selected route traversal. Details pane 402 may include a title 404 indicating vehicle 102 and the route time being displayed. In addition, details pane 402 may include a map view 406, which shows the path 408 of vehicle 102 along the selected route. Details pane 402 may also include a waste event list 410, which shows an event list that contributes to the waste calculation of the selected route. As shown, each waste event is specified according to the type of event (e.g., idling, speeding, etc.), time (e.g., the time when the event starts), the duration of the event (e.g., in minutes) and the waste value of the event (e.g., in dollars). As shown, four idling events have an impact on the total waste value of the selected route traversed by vehicle 102.

[0049] Figure 5 An exemplary process 500 is shown for sending aggregated data 126 from a vehicle 102 to a remote server 128. In an example, the process 500 may be performed by a processor 106 and / or a dongle 146 of a telematics controller 104 of a fleet of vehicles 102. For example, the process 500 may begin in response to a vehicle 102 beginning to traverse a route.

[0050] Route traversal may begin due to user interaction, such as a user beginning to select a route from a user interface of the vehicle 102. In another example, the process 500 begins in response to another action, such as the vehicle 102 leaving a predefined location marked as the start of the route, or the vehicle 102 starting at a predefined time corresponding to the route. In some examples, the initiation of the route may be identified based on a shift, such that the route is considered to be initiated at a predefined time when the shift is expected to start. Similarly, the route may be considered to be completed at an estimated time when the route is expected to be completed. In other examples, a trip state parameter may be provided by the processor 106, which records when the vehicle 102 is turned on and off in the context of the trip. In yet another example, geo-fences may be used to infer the start and end of the route. In an example, a geo-fence may be defined for the start location of the route, and a second geo-fence may be defined for the end location of the route. When the vehicle 102 leaves the start location geo-fence, the route may be considered to have started, and when the vehicle 102 reaches the end location geo-fence, the route may be considered to have ended.

[0051] At operation 502 , the processor 106 receives a fuel pump actuator signal. In an example, the powertrain controller 116 provides a PWM signal used to drive an actuator of the fuel pump 118 or information indicative of the PWM signal to the vehicle bus 112 . The processor 106 may receive this data via the vehicle bus 112 .

[0052] At 504, processor 106 aggregates the fuel pump signals. In an example, processor 106 determines the amount of fuel used based on the fuel pump actuator signals. The calculation of the amount of fuel used may be determined based on an integration of the received PWM data.

[0053] At 506, the processor 106 receives additional signal data. In an example, the processor 106 receives vehicle location data provided from the global positioning controller 114 via the vehicle bus 112. In another example, the processor 106 receives other information captured from the vehicle bus 112, such as vehicle speed, engine speed, engine on / off status, and a vehicle identifier (e.g., VIN).

[0054] At operation 508, the processor 106 determines whether a periodic timeout has expired. In an example, the processor 106 may maintain a counter that causes the vehicle 102 to periodically send the aggregated data 126 to the remote server 128. The periodic timeout may be every minute, every five minutes, or every hour, as some possibilities. If the timer has expired, then the timer is reset and control passes to operation 510. Otherwise, control passes to operation 512.

[0055] At 510, the processor 106 sends a data update for the aggregated data 126. The data update may include the amount of fuel used determined at operation 504, and the additional signal data captured at operation 506. The amount of fuel may be an accumulation of the fuel used over the duration of the route to allow the remote server 128 to identify the total fuel used by the vehicle 102 regardless of whether one or more transmissions are lost.

[0056] At 512, the processor 106 determines whether the route is complete. One or more of the above methods may be used to identify that the route is complete. In an example, the processor 106 may determine that the route is complete due to user interaction, such as a user selecting route complete from a user interface of the vehicle 102. In another example, the processor 106 may determine that the route is complete due to another action, such as the vehicle 102 arriving at a predefined location marked as the end of the route, or the vehicle 102 arriving at the location of the end of the route. If the route is complete, then control passes to operation 514. Otherwise, control returns to operation 502.

[0057] At operation 514, the processor 106 sends a route summary. The route summary may include complete information for the route, such as the start time, end time, and total fuel consumption. After operation 514, the process 500 ends.

[0058] Figure 6 An exemplary process 600 is shown for displaying the fuel waste data report 140 by route based on the aggregated data 126. In an example, the process 600 may be performed by the remote server 128 in response to a communication from the display device 144.

[0059] At operation 602, the remote server 128 receives aggregated data 126 from the vehicles 102 of the fleet. Further details of receiving the aggregated data 126 are discussed above with respect to the process 500.

[0060] At 604, the remote server 128 identifies a route and a time range. In the example, the remote server 128 receives a selection of the route and the time range from the display device 144. For example, the selection may be performed at the display device 144 via the route selection control 204 and the time range control 206, where in response to the selection, the display device 144 may send a message indicating the selection to the remote server 128 via the communication network.

[0061] At 606 , the remote server 128 retrieves aggregate data 126 corresponding to the identified route and time range. In an example, the aggregate data 126 may be indexed by the remote server 128 according to the route assignment 136 and the time range, and the remote server 128 may query the requested data based on the selection received at operation 602 .

[0062] At operation 608, the remote server 128 identifies the idle time period. In an example, the remote server 128 may analyze the aggregated data 126 received at operation 604 to identify the idle time period. In an example, the remote server 128 may identify the vehicle 102 as idling based on factors including geographic location, vehicle speed, and engine RPM. As a non-limiting example, if the vehicle speed is zero (or below a predefined speed) and the engine RPM is not zero, then the vehicle 102 may be identified as idling.

[0063] At 610, the remote server 128 calculates fuel waste during the idle time period. In an example, using the fuel usage information in the aggregated data 126, the remote server 128 accumulates fuel usage during these idle times and determines a fuel waste measure based on the units of fuel used (e.g., gallons of fuel).

[0064] At 612, the remote server 128 calculates the monetary waste based on the fuel waste. In an example, the remote server 128 may multiply the fuel used during the idling event by the dollar cost per unit of fuel (e.g., $4 per gallon of gasoline). In an example, the dollar cost may be predefined for various geographic areas (such as metropolitan areas). In another example, the remote server 128 may receive the dollar cost from the user (e.g., via the display device 144), or may query the information from the Internet using a service that provides the fuel cost of the local vehicle 102 based on the location information of the route.

[0065] At operation 614, the remote server 128 calculates the average waste. In an example, the remote server 128 may identify, for the route being displayed, the average of the waste calculated at operation 610. This metric may be used to provide a measure of how a single vehicle 102 performs compared to other vehicles 102 traversing the same route.

[0066] At 616, the remote server 128 presents the results. Exemplary presentations of results are discussed in detail above with respect to examples 200, 300, and 400. After operation 616, process 600 ends.

[0067] The computing devices described herein, such as telematics controller 104, global positioning controller 114, powertrain controller 116, remote server 128, display device 144, and dongle 146, generally include computer executable instructions, wherein the instructions can be executed by one or more computing devices (such as those listed above). Computer executable instructions (such as those of data reporting application 124, report generator application 138, and report server 142) can be compiled or interpreted by a computer program created using various programming languages ​​and / or technologies, including, alone or in combination, but not limited to Java. TM , C, C++, C#, Visual Basic, Java Script, Python, JavaScript, Perl, PL / SQL, etc. In general, a processor (e.g., a microprocessor) receives instructions, such as from a memory, a computer-readable medium, etc., and executes these instructions to perform one or more processes, including one or more of the processes described herein. A variety of computer-readable media can be used to store and transmit such instructions and other data.

[0068] With respect to the processes (such as processes 500 and 600), systems, methods, heuristics, etc. described herein, it should be understood that although the steps of such processes, etc. have been described as occurring in a sequence in a particular order, such processes may be practiced by performing the described steps in an order different from that described herein. It should also be understood that certain steps may be performed simultaneously, other steps may be added, or certain steps described herein may be omitted. In other words, the descriptions of processes herein are provided for the purpose of illustrating certain embodiments and should in no way be construed as limiting the claims.

[0069] Therefore, it should be understood that the above description is intended to be illustrative and not restrictive. After reading the above description, many embodiments and applications other than the examples provided will become readily apparent. The scope should not be determined with reference to the above description, but with reference to the full scope of equivalents to which such claims are assigned. It is expected and hoped that the technology discussed herein will develop in the future, and the disclosed system and method will be incorporated into such future embodiments. In short, it should be understood that the present application is capable of modification and variation.

[0070] Unless expressly indicated to the contrary herein, all terms used in the claims are intended to be given their broadest reasonable interpretations and ordinary meanings as understood by those skilled in the art. In particular, use of singular articles such as "a," "an," "the," and the like should be understood to recite one or more of the indicated elements unless a claim recites an explicit limitation to the contrary.

[0071] An abstract of the present disclosure is provided to allow the reader to quickly ascertain the essence of the technical disclosure. It should be understood that the submitted abstract is not intended to interpret or limit the scope or meaning of the claims. In addition, in the foregoing detailed description, it can be seen that various features are combined together in various embodiments for the purpose of streamlining the present disclosure. This method of disclosure should not be interpreted as reflecting the following intention: the claimed embodiments require more features than the features explicitly recited in each claim. Rather, as reflected in the following claims, the subject matter of the present invention lies in fewer features than all the features of a single disclosed embodiment. Therefore, the following claims are hereby incorporated into the detailed description, wherein each claim itself may serve as a separately claimed subject matter.

[0072] Although exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the present invention. On the contrary, the words used in this specification are descriptive rather than limiting words, and it should be understood that various changes can be made without departing from the spirit and scope of the present invention. In addition, the features of the various embodiments of implementation can be combined to form other embodiments of the present invention.

[0073] According to the present invention, a system is provided, which has: a vehicle's powertrain controller, the powertrain controller being configured to provide a fuel pump actuator signal indicating fuel flow to a vehicle bus; and a processor, the processor being configured to receive data from the vehicle bus, being programmed to perform integration of the actuator signal to accumulate fuel usage of the vehicle, and periodically sending the accumulated fuel usage, vehicle speed, engine speed, engine status, and vehicle position to a remote server.

[0074] According to one embodiment, the fuel pump actuator signal is a pulse width modulated (PWM) signal generated by the powertrain controller to drive a fuel pump.

[0075] According to one embodiment, the above invention is further characterized by having a global positioning controller configured to provide information indicative of the vehicle's location to the vehicle bus, wherein the processor is programmed to retrieve the vehicle's location from the vehicle bus.

[0076] According to one embodiment, the above invention is further characterized by having a data port configured to provide access to the vehicle bus, wherein the processor is included in a dongle connected to the data port.

[0077] According to one embodiment, the above invention is further characterized by having a telematics controller in communication with the vehicle bus, wherein the processor is included in the telematics controller.

[0078] According to one embodiment, the engine status indicates whether the engine is on or off.

[0079] According to the present invention, a system is provided having: a memory storing cumulative fuel usage compiled from fuel pump actuator signals for vehicles of a fleet; and a processor of a server programmed to retrieve a subset of the cumulative fuel usage of a group of vehicles traversing a route during a certain time range, calculate fuel waste during identified idling time periods within the cumulative fuel usage, calculate monetary waste based on the fuel waste, and generate a report including the monetary waste.

[0080] According to one embodiment, the processor is further programmed to calculate an average monetary waste for the vehicle traversing the route during the time frame and include the average monetary waste in the report.

[0081] According to one embodiment, the processor is also programmed to include in the report for each vehicle in the group of vehicles a graphical representation having a size proportional to the amount of monetary waste identified for the corresponding vehicle, wherein an indication of the average monetary waste is placed at a position along the graphical representation to indicate average vehicle waste.

[0082] According to one embodiment, the processor is further programmed to periodically receive the cumulative fuel usage data from the vehicle in the group of vehicles.

[0083] According to one embodiment, the monetary waste is calculated based on local fuel costs in the region of operation of the fleet.

[0084] According to one embodiment, the processor is further programmed to, in response to receiving a selection of expanded data for one of the vehicles in the group of vehicles, expand the data for the vehicle to display details of each traversal of the route performed by the vehicle within the time range.

[0085] According to the present invention, a method is provided, which includes: retrieving a subset of cumulative fuel usage of a group of vehicles of a fleet traversing a route during a certain time range, the cumulative fuel usage compiled from fuel pump actuator signals; calculating fuel waste during identified idling time periods within the cumulative fuel usage; calculating monetary waste based on the fuel waste; and generating a report including the monetary waste.

[0086] According to one embodiment, the above invention is further characterized by calculating an average monetary waste for said vehicle traversing said route during said time range and including said average monetary waste in said report.

[0087] According to one embodiment, the above invention is also characterized in that a graphical representation whose size is proportional to the amount of monetary waste identified for the corresponding vehicle is included in the report for each vehicle in the group of vehicles, wherein an indication of the average monetary waste is placed at a position along the graphical representation to indicate the average vehicle waste.

[0088] According to one embodiment, the above invention is further characterized by periodically receiving said accumulated fuel usage data from said vehicle in said group of vehicles.

[0089] According to one embodiment, the above invention is further characterized in that the monetary waste is calculated based on the local fuel cost of the operating area of ​​the fleet.

[0090] According to one embodiment, the above invention is further characterized in that, in response to receiving a selection of expanded data for one of the vehicles in the group of vehicles, the data for the vehicle is expanded to display details of each traversal of the route performed by the vehicle within the time range.

[0091] According to one embodiment, the above invention is further characterized in that the report is sent to a display device via a communication network for viewing.

Claims

1. A system for fleet management, include: A remote server, including storage and a server processor, wherein the memory stores cumulative fuel usage of vehicles of the fleet compiled from fuel pump actuator signals, and The server processor is configured to: periodically obtaining from each vehicle of the fleet fuel usage, vehicle speed, engine speed, engine status, and vehicle location of the vehicle, the fuel usage of the vehicle being obtained by: performing integration of a fuel pump actuator signal indicative of fuel flow received from a powertrain controller included in each of the vehicles to accumulate fuel usage of the vehicle; retrieving a subset of cumulative fuel usage of a set of vehicles of a fleet traversing a route during a certain time range; calculating fuel waste during identified idling time periods within the cumulative fuel usage; calculating monetary waste based on the fuel waste; and A report is generated including said monetary waste.

2. The system according to claim 1, in, The fuel pump actuator signal is a pulse width modulated (PWM) signal generated by the powertrain controller to drive a fuel pump.

3. The system of claim 1, wherein each vehicle in the fleet further include: A vehicle processor and a global positioning controller configured to provide information indicative of the vehicle's location to a vehicle bus, wherein the vehicle processor is configured to retrieve the vehicle's location from the vehicle bus.

4. The system of claim 3, wherein each vehicle in the fleet further include: A data port is configured to provide access to the vehicle bus, wherein the vehicle processor is included in a dongle connected to the data port.

5. The system of claim 3, wherein each vehicle in the fleet further include: A telematics controller is in communication with the vehicle bus, wherein the vehicle processor is included in the telematics controller.

6. The system of claim 1, in, The engine status indicates whether the engine is on or off.

7. The system of claim 1, in, The server processor is further configured to: calculating an average monetary waste for the vehicle traversing the route during the time range, and The average monetary waste is included in the report.

8. The system of claim 7, in, The server processor is also configured to include in the report for each vehicle in the group of vehicles a graphical representation having a size proportional to the amount of monetary waste identified for the corresponding vehicle, wherein an indication of the average monetary waste is placed at a position along the graphical representation to indicate average vehicle waste.

9. A method for fleet management, include: periodically obtaining a fuel usage, a vehicle speed, an engine speed, an engine status, and a vehicle location of the vehicle from each vehicle in the fleet, the fuel usage of the vehicle being obtained by: performing an integration of a fuel pump actuator signal indicative of fuel flow received from each vehicle in the fleet to accumulate the fuel usage of the vehicle; retrieving a subset of cumulative fuel usage of a set of vehicles of a fleet traversing a route during a time range, the cumulative fuel usage compiled from the fuel pump actuator signal; calculating fuel waste during identified idling time periods within the cumulative fuel usage; calculating monetary waste based on said fuel waste; as well as A report is generated including said monetary waste.

10. The method of claim 9, further comprising: include: calculating an average monetary waste for the vehicle traversing the route during the time range, and The average monetary waste is included in the report.

11. The method according to claim 10, further comprising: include: A graphical representation having a size proportional to the amount of monetary waste identified for the respective vehicle is included in the report for each vehicle in the group of vehicles, wherein an indication of the average monetary waste is placed at a location along the graphical representation to indicate average vehicle waste.

12. The method of claim 9, further comprising: include: The accumulated fuel usage data is periodically received from the vehicles in the group of vehicles.

13. The method of claim 9, further comprising: include: The monetary waste is calculated based on local fuel costs in the area of ​​operation of the fleet.

14. The method of claim 9, further comprising: include: In response to receiving a selection of expanded data for one of the vehicles in the group of vehicles, the data for the vehicle is expanded to display details of each traversal of the route performed by the vehicle within the time range.

15. The method of claim 9, further comprising: include: The report is sent via a communication network to a display device for viewing.

Citation Information

Patent Citations

  • Fuel usage meter

    CA2832454A1

  • Fuel consumption evaluation system

    CN101002012A

  • A clear pulp production process for realizing complete comprehensive utilization and removing three wastes

    CN101775750A

  • An energy efficient data acquisition system and computer controlled energy monitoring system incorporating the same

    CN1751535A

  • Self-propelled vehicle

    JP1997329051A