Patent Application
20230360450
Vehicles including refuse vehicles may track and record data related to actions performed by the vehicle. Further, this data may be wirelessly transmitted (e.g., to a server, other vehicle, etc.) such that the vehicles actions may be shared with other computing devices.
At least one embodiment relates to a system for monitoring operation of a vehicle. The system includes a device configured to collect data pertaining to operations of the vehicle and one or more processing circuits in communication with the device. The one or more processing circuits configured to receive, from the device responsive to a first operation of the vehicle, data pertaining to the first operation of the vehicle, determine, using the data pertaining to the first operation of the vehicle, that the first operation of the vehicle includes a vehicle backup, and provide, to a user device, a user interface that displays an indication of the vehicle backup.
At least one embodiment relates to a system for monitoring operation of a vehicle. The system includes a device configured to collect data pertaining to operations of the vehicle and one or more processing circuits in communication with the device. The one or more processing circuits configured to receive data pertaining to a plurality of operations of the vehicle, determine, using the data pertaining to the plurality of operations of the vehicle, a number of vehicle backups performed by the vehicle, associate, using location information included in the data pertaining to the plurality of operations of the vehicle, the number of vehicle backups performed by the vehicle with a route taken by the vehicle, and provide, to a user device, a user interface that displays an indication of the number of vehicle backups and the route taken by the vehicle.
At least one embodiment relates to a system for monitoring operation of a vehicle. The system includes a device configured to collect data pertaining to operations of the vehicle and one or more processing circuits in communication with the device. The one or more processing circuits configured to receive data pertaining to a plurality of operations of the vehicle, determine, using the data pertaining to the plurality of operations of the vehicle, a number of vehicle backups performed by the vehicle, associate, using location information included in the data pertaining to the plurality of operations of the vehicle, the number of vehicle backups performed by the vehicle with a route taken by the vehicle, identify, using the data pertaining to the plurality of operations of the vehicle, a plurality of tasks included along the route taken by the vehicle, and provide, to a user device, a user interface that displays an indication of the route taken by the vehicle, an indication of number of vehicle backups performed by the vehicle, and an indication of the plurality of tasks included along the route taken by the vehicle.
This summary is illustrative only and is not intended to be in any way limiting. Other aspects, inventive features, and advantages of the devices or processes described herein will become apparent in the detailed description set forth herein, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements.
Before turning to the figures, which illustrate certain exemplary embodiments in detail, it should be understood that the present disclosure is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology used herein is for the purpose of description only and should not be regarded as limiting.
Referring generally to the figures, systems and methods for supplying and/or monitoring a service to a customer are shown below. In a typical application, a refuse vehicle travels along a route. While the refuse vehicle is traveling along the route the refuse vehicle may perform a backup maneuver (e.g., the vehicle travels in reverse) and/or other vehicle maneuvers and operations. In one embodiment, the system determines a number of backups (e.g., how many times the vehicle travels backwards) performed by a refuse vehicle during daily operations. The system may utilize data associated with the refuse vehicle to generate one or more reports. The system can provide the reports to a user that is associated with the refuse vehicle and/or be transmitted (e.g., via telematics) to a vehicle monitoring and/or control center. The reports can include information pertaining to the number of backups performed, the route associated with the number of vehicle backups and the vehicle tasks associated with the route (e.g., waste collection stops). The system may be configured to present the data via an interactive graphical user interface that allows a user to visualize the number of backups graphically for individual vehicles and locations at which the backups were performed. It should be appreciated that although the methods herein are described with reference to vehicle backup monitoring and detection, similar methods can be used to monitor other vehicle operations (e.g., body operations such as vehicle unloading, and/or refuse vehicle specific operations such as ejector operation, vehicle capacity monitoring, etc.).
Referring now to
Referring now to
In some embodiments, the data collection system 205 can receive vehicle data from the vehicle detection system 210, the user device 220 and/or the service manager 215. In some embodiments, the data received can include telematics data. In some embodiments, the data collection system 205, the service manager 215 and the user device 220 can interface using a controller area network (CAN). The data collection system 205 can use the vehicle data to determine if a vehicle backup has occurred. For example, the data collection system 205 can receive a GPS coordinate of the vehicle as well as the drive mode of the vehicle (e.g., forward or reverse). The data collection system 205 can detect that the GPS coordinate of the vehicle has changed (e.g., the vehicle is moving) and that the vehicle is in reverse. The data collection system 205 can then determine that a vehicle backup has occurred. In some embodiments, the data collection system 205 can assign a location associated with the vehicle backup.
In some embodiments, the data collection system 205 can provide the information including the determined vehicle backup to the service manager 215 and/or the user device 220. A route traveled by the vehicle can also be included. In some embodiments, the service manager 215 and/or the data collection system 205 can analyze the route taken which included a vehicle backup. In some embodiments, the data collection system 205 and/or the service manager 215 can identify a route that can be taken to avoid repeating the vehicle backup.
In some embodiments, the information including the determined vehicle backup can be used for training drivers of a vehicle. For example, a driver can be trained to avoid situations that can result in the vehicle backup.
Referring now to
The processor 315 may be a general purpose or specific purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable processing components. The processor 315 may be configured to execute computer code or instructions stored in memory 206 or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc.) to perform one or more of the processes described herein. Memory 320 may include one or more data storage devices (e.g., memory units, memory devices, computer-readable storage media, etc.) configured to store data, computer code, executable instructions, or other forms of computer-readable information. Memory 320 may include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. Memory 320 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. Memory 320 may be communicably connected to processor 315 via processing circuit 310 and may include computer code for executing (e.g., by processor 315, etc.) one or more of the processes described herein.
The memory 320 is described below as including various modules. While the exemplary embodiment shown in the figures shows each of the modules 325, 330, 335 and 340 as being separate from one another, it should be understood that, in various other embodiments, the memory may include more, less, or altogether different modules. For example, the structures and functions of one module may be performed by another module, or the activities of two modules may be combined such that they are performed by only a signal module.
The communications module 325 is configured to facilitate wireless communications with external computing systems and with other vehicles via communications interface 345 (e.g., a transceiver, etc.). Communications interface 345 may support any kind of wireless standard (e.g., 802.11 b/g/n, 802.11a, etc.) and may interface with any type of external computing system including wireless communication capability (e.g., cellular, Wi-Fi, etc.). Communications interface 345 may further facilitate wireless communications with an external global positioning system (GPS). Communications module 325 may be any type of capable module (e.g., a CL-T04 CANect® Wi-Fi Module manufactured by HED Inc., etc.) configured to support wireless communications with the external computing systems and other response vehicles. In one embodiment, the external computing systems communicate with the response vehicles via Wi-Fi. In other embodiments, the communications between the external computing systems and/or response vehicles may be supported via CDMA, GSM, or another cellular connection. In still other embodiments, another wireless protocol is utilized (e.g., Bluetooth, Zigbee, radio, etc.).
The system module 330 is structured to enable the processor 315 of the data collection system 205 to interface with vehicle detection system 210 of the vehicle 20. In the exemplary embodiment shown, the data collection system 205, via the system module 330, may generate a vehicle system report based on various sensor data points received from the vehicle detection system 210. The report may be generated by comparing the sensor data points received from the vehicle detection system 210. For example, a baseline sensor value for the vehicle detection system 210 may include an initial location of the vehicle 20. Thus, upon receipt of a sensor data point indicative of the location of the vehicle 20, the processor 315 may compare the received data point to the baseline value to determine if a vehicle backup has occurred. The generated report may indicate a total number of vehicle backups. As will be understood, there may be multiple baseline values with respect to each sensor of the vehicle detection system 210.
According to various embodiments, the system module 330 is structured to enable the processor 315 to modify the sample rate of the various sensors included in vehicle detection system 210. For example, the processor 315 may modify the sample rate of a particular sensor in response to detecting a particular operating state. In this sense, the processor 315 may cause each sensor to selectively record data points at predetermined intervals. For example, the processor 315 may determine an operating state of the vehicle (e.g., emergency response, pumping event, etc.) and adjust the predetermined intervals accordingly. For example, the processor 315 may cause the sample rate of the sensors to change depending on the operating state of the vehicle. According to various embodiments, the first rate corresponds with the sensors taking measurements at a more frequent rate (e.g., once every two minutes) than the second rate (e.g., once every thirty minutes).
The system module 330 may be structured to interface with various other modules to present the vehicle system report to an operator and/or other user. For example, the system module 330 may interface with the display module 340 to present the operator with the vehicle system report via the display device 225. The display module 340 may be configured to present the generated vehicle systems report on the display device 225 (e.g., via an interactive graphical user interface). Alternatively or additionally, the system module 330 may interface with the communications module 325 so as to format the generated vehicle system report into a webpage or the like that is viewable on a display device (e.g., user device 220) included in an external computing system and transmit the report data to the external computing system via the secure connection discussed above.
The vehicle database 335 may include, for example, telemetric data captured by the vehicle detection system 210. For example, the system module 330 may include a data logger or the like that stores any sensor data points received from the vehicle detection system 210. The vehicle database 335 may include a plurality of telemetry datasets, with each dataset corresponding to a different sensor device of the vehicle detection system 210. Each dataset may include a plurality of entries, with each entry including a sensor data point value and a time stamp. Alternatively or additionally, the vehicle database 335 may store the vehicle system reports generated via the system module 330.
The stored data may be removed from the vehicle database 335 once the data is uploaded to a remote cloud storage. For example, long-term storage of the telemetry data and other data may be done on a centralized server, and communications interface 345 may wirelessly connect with a remote server to transmit and store the data. The data includes a timestamp and vehicle identifier information to identify the data in remote server. In some embodiments, the service manager 215 can perform similarly functionality to a remote server.
In one embodiment, the data is automatically updated periodically. The data may also be updated upon user request. A controller area network (CAN) controller, such as system module 330 or another module may be configured to monitor the data and to determine when a potential status of the vehicle 20 has changed based on the telemetry data changes (e.g., determine that a vehicle backup has occurred).
According to various embodiments, the processor may selectively transmit a subset of the data (e.g., data points from a specific subset of sensors) in response to an operating state of the vehicle being determined. For example, the data collection system may transmit data points from certain sensors (e.g., a water level sensor in the pump system) at a higher rate during a pumping event than other sensors (e.g., an engine output sensor). By reducing the total number of data points being transmitted, the strain on the communications interface 345 may be reduced.
Vehicle database 335 may be any type of database (e.g., a SQLite database, etc.), and modules 325, 330, 340 may query the database using any type of language or method via backend framework. The backend framework of data collection system 205 may support the activities of periodically updating and querying vehicle database 335, as well as providing web layer authentication (e.g., to authenticate devices that attempt to access data from vehicle database 335, etc.). The backend framework may further support the various security-related functionality of communications module 325.
Data collection system 205 may include, for example, a data transport protocol layer configured to facilitate the query of data from vehicle database 335 for use by the various modules of memory 320. In one embodiment, at least one of web sockets and AJAX polling is used to invoke queries via backend framework and provide the data to the frontend applications (e.g., the application layer, the modules, etc.), as they allow changes to the vehicle database 335 to be detected and pushed to the application layer. The use of web sockets and/or AJAX may be based on compatibility constraints and performance constraints with the external computing system accessing the data collection system 205. The application layer, or the frontend application, of data collection system 205 may be built using, for example, HTML5, CSS, and various Javascript libraries.
The sensor array 350 can include one or more sensors. The sensors can be at least one of a location sensor, a fuel sensor, an engine sensor, a drive mode sensor, a pump sensor, a collector sensor or a temperature sensor. The location sensors can detect location data. The sensor array 350 can provide the location data to the communications interface 345. The system module 330 can use the location data to determine whether a vehicle backup has occurred. In some embodiments, the system module 330 can use the location data to associate the vehicle with a position on a map. In some embodiments, the system module 330 may utilize the location data to generate a route traveled by the vehicle 20. The system module 330 can associate a route with a total number of vehicle backups. In some embodiments, the system module 330 can compare the routes and the vehicle backups associated with the route to a vehicle backup metric. In some embodiments, the vehicle backup metric can be a predetermined number of vehicle backups. The system module 330 can use the vehicle backup metric to identify routes that have a total number of vehicle backups above, below and/or within the vehicle backup metric.
The fuel sensors can detect data that can be used by the system module 330 to determine fuel usage. The engine sensor can detect data can be used by the system module 330 to determine an engine runtime metric. The drive mode sensor can detect data that can be used by the system module 330 to determine a drive mode of the vehicle. The pump sensor can detect data that can be used by the system module 330 to determine a pump metric. The pump metric can include a number of pump hours. The collector sensor can detect data that can be used by the system module 330 to determine a collector metric. The collector metric can include a number of waste collection stops, a number of arm dumps, a number of eject cycles and/or a number of arm dumps. The temperature sensor can detect data that can be used by the system module 330 to determine temperature throughout various components of the vehicle.
In some embodiments, the service manager 215 can perform similar functionality to the data collection system 205 and/or the vehicle detection system 210. For example, the data collected by the vehicle detection system 210 can be provided to the service manager 215. The service manager 215 can use the data to determine whether a vehicle backup has occurred. The service manager 215 can associate the vehicle backup with a route traveled by the vehicle.
In some embodiments, the data collection system 205 and/or the vehicle detection system 210 can perform similar functionality to a telematics control unit (TCU) connected to a Controller Area Network bus which can interface with a remote data center. In some embodiments, the data collected by the data collection system 205 and/or the vehicle detection system 210 can be provided to the service manager 215. (e.g., remote data center) The service manager 215 can analyze the data provided by the data collection system 205 and/or the vehicle detection system. For example, the data provided to the service manager 215 can include location data and drive mode data. The service manager 215 can determine, using the location data and the drive mode data, that a vehicle backup occurred. In some embodiments, the service manager 215 can associated the vehicle backup with one or more routes. In some embodiments, the service manager 215 can analyze one or more vehicle backups and determine a backup factor associated with a vehicle backup. For example, a backup factor can be at least one of a road closure, a driver action, a weather occurrence or a vehicle failure. In some embodiments, the service manager 215 can analysis the backup factors associated with the vehicle backups to determine if a coaching opportunity exists. For example, driver 1 and driver 2 travel on the same route and perform the same vehicle tasks. However, driver 1 performed more vehicle backups compared to the vehicle backups performed by driver 2. In some embodiments, the service manager 215 can recommend that driver 1 receive additional coaching.
In some embodiments, the service manager 215 can compare vehicle backups associated with a certain route to determine if the vehicle backups change amongst days of the week. For example, on a Tuesday and/or a Thursday a driver travels on the same route and performs the same vehicle tasks. However, the vehicle backups performed on one of the days was higher than the other day. In some embodiments, the service manager 215 can determine that on certain days the vehicle backups can be higher.
In some embodiments, the service manager 215 can provide the information associated with a vehicle backup to a display device. The display device can provide a user interface to a user. The user can view the information associated with the vehicle backups. For example, the location of the vehicle backups can be placed on a map. The map can include an interactive satellite view. The user can view roads, objects (e.g., trees, buildings, etc.) and/or the locations of the vehicle backups. In some embodiments, the user interface can provide a graphical representation of the information associated with the vehicle backups. For example, a graph that includes one or more days and the number of vehicle backups associated with a certain day. In some embodiments, the user can select a date range of vehicle information. The user interface can display the information associated with the vehicle backups included within the selected date range. In some embodiments, the service manager 215 can determine that the number of vehicle backups associated with a certain route is not within the vehicle backup metric. In some embodiments, the service manager 215 can display an alert on the user interface. In some embodiments, the user can select a prompt associated with the alert to view the information associated with the alert. In some embodiments, the user can provide an indication to the service manager 215. The indication can be an indication that a driver associated with certain vehicle backups has been selected to undergo vehicle backup coaching. The service manager 215 can provide the indication to the driver associated with the certain vehicle backups. In some embodiments, the service manager 215 can schedule and track the vehicle backup coaching associated with the driver.
Referring now to
At step 415, the location data can be used to determine that a vehicle backup has occurred. The system module 330 can use the location data to identify the location of the vehicle. For example, the system module 330 can determine that the vehicle is at a dead end (e.g., an alley that connects directly to a building). The system module 330 can use the location data and the drive mode data to determine whether a vehicle backup has occurred. For example, the system module 330 can use the location data to determine that the vehicle is moving and can use the drive mode data to determine the vehicle is in reverse.
At step 420, the vehicle backup can be associated with a route. The system module 330 can use the location data to determine a route traveled by the vehicle. The system module 330 can associate a vehicle backup with the route. For example, as the system module 330 determines that a vehicle backup has occurred the system module 330 can assign a location to the vehicle backup. The system module 330 can use the location assigned to the vehicle backup to associate the vehicle backup with the route (e.g., the location is included in the route).
At step 425, a report is generated. The report can include a vehicle travel route, a number of vehicle backups performed during the vehicle travel route, a location associated with a vehicle backup, a number of vehicle tasks, the location associated with a vehicle task and a comparison of the number of vehicle backups to the vehicle backup metric.
In some embodiments, the report can be provided to a user. The report can be displayed using a user interface. For example, the communications module 325 can interface with the user device 220. The communications module 325 can provide the report to the user device 220 and the user device 220 can display the report using a user interface associated with the user device 220. A user associated with the user device 220 can view the information associated with the report. For example, the user can view the total number of vehicle backups associated with a route. In some embodiments, the user can provide an indication to the data collection system 205. The indication can be an indication to recommend a route that can be traveled with fewer vehicle backups. For example, the system module 330 can identify the report associated with the indication. The system module 330 can determine the number of vehicle backups associated with the report, the locations of the vehicle backups, the number of vehicle tasks and the location of the vehicle tasks. The system module 330 can recommend a route that can be traveled which includes the vehicle tasks and a number of vehicle backups that is less than the previous route.
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
The user can be presented with the information associated with the status dashboard 2110 by selecting the status tab. The user can be presented with the information associated with the totals dashboard 2115 by selecting the totals tab. The user can be presented with the information associated with the analytics dashboard 2120 by selecting the analytics tab. In some embodiments, the data collection system 205 can generate the information displayed in
Referring now to
Referring now to
Referring now to
Referring now to
Referring now to
In some embodiments, the data collection system 205 can generate the information displayed in
As utilized herein, the terms “approximately,” “about,” “substantially,” and similar terms are intended to have a broad meaning in harmony with the common and accepted usage by those of ordinary skill in the art to which the subject matter of this disclosure pertains. It should be understood by those of skill in the art who review this disclosure that these terms are intended to allow a description of certain features described and claimed without restricting the scope of these features to the precise numerical ranges provided. Accordingly, these terms should be interpreted as indicating that insubstantial or inconsequential modifications or alterations of the subject matter described and claimed are considered to be within the scope of the disclosure as recited in the appended claims.
It should be noted that the term “exemplary” and variations thereof, as used herein to describe various embodiments, are intended to indicate that such embodiments are possible examples, representations, or illustrations of possible embodiments (and such terms are not intended to connote that such embodiments are necessarily extraordinary or superlative examples).
The term “coupled” and variations thereof, as used herein, means the joining of two members directly or indirectly to one another. Such joining may be stationary (e.g., permanent or fixed) or moveable (e.g., removable or releasable). Such joining may be achieved with the two members coupled directly to each other, with the two members coupled to each other using a separate intervening member and any additional intermediate members coupled with one another, or with the two members coupled to each other using an intervening member that is integrally formed as a single unitary body with one of the two members. If “coupled” or variations thereof are modified by an additional term (e.g., directly coupled), the generic definition of “coupled” provided above is modified by the plain language meaning of the additional term (e.g., “directly coupled” means the joining of two members without any separate intervening member), resulting in a narrower definition than the generic definition of “coupled” provided above. Such coupling may be mechanical, electrical, or fluidic.
References herein to the positions of elements (e.g., “top,” “bottom,” “above,” “below”) are merely used to describe the orientation of various elements in the FIGURES. It should be noted that the orientation of various elements may differ according to other exemplary embodiments, and that such variations are intended to be encompassed by the present disclosure.
The hardware and data processing components used to implement the various processes, operations, illustrative logics, logical blocks, modules and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some embodiments, particular processes and methods may be performed by circuitry that is specific to a given function. The memory (e.g., memory, memory unit, storage device) may include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present disclosure. The memory may be or include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory is communicably connected to the processor via a processing circuit and includes computer code for executing (e.g., by the processing circuit or the processor) the one or more processes described herein.
The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
Although the figures and description may illustrate a specific order of method steps, the order of such steps may differ from what is depicted and described, unless specified differently above. Also, two or more steps may be performed concurrently or with partial concurrence, unless specified differently above. Such variation may depend, for example, on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations of the described methods could be accomplished with standard programming techniques with rule-based logic and other logic to accomplish the various connection steps, processing steps, comparison steps, and decision steps.
It is important to note that the construction and arrangement of the system 200 as shown in the various exemplary embodiments is illustrative only. Additionally, any element disclosed in one embodiment may be incorporated or utilized with any other embodiment disclosed herein. For example, the refuse vehicle 20 of the exemplary embodiment shown in at least
This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63/338,600, filed on May 5, 2022, the entirety of which is incorporated by reference herein.
| Number | Date | Country | |
|---|---|---|---|
| 63338600 | May 2022 | US |
