AUTOMATED AUTOMOBILE MANAGEMENT SYSTEM
CROSS-REFERENCE TO OTHER APPLICATION
[0001] This application claims the benefit of the filing date of U.S. Provisional Patent Application 61/422,729, filed December 14, 2010, which is hereby incorporated by reference.
TECHNICAL FIELD
[0002] The present disclosure is directed, in general, to systems and methods for managing data related to automobiles, including systems for automatic processing of rental automobile returns.
BACKGROUND OF THE DISCLOSURE
[0003] Many companies, including automobile rental agencies, must manage data for multiple vehicles. Improved systems are desirable.
SUMMARY OF THE DISCLOSURE
[0004] Various disclosed embodiments include methods for vehicle management and corresponding systems and computer-readable mediums. A method includes detecting and wirelessly communicating with a vehicle data collection unit installed in a vehicle. The method includes wirelessly receiving vehicle data from the vehicle data collection unit, including a vehicle identifier. The method includes loading stored vehicle data corresponding to the vehicle identifier. The method includes updating a vehicle inventory corresponding to the vehicle identifier. The method includes generating a report according to the received vehicle data and the stored vehicle data.
[0005] The foregoing has outlined rather broadly the features and technical advantages of the present disclosure so that those skilled in the art may better understand the detailed description that follows. Additional features and advantages of the disclosure will be described hereinafter that form the subject of the claims. Those skilled in the art will appreciate that they may readily use the conception and the specific embodiment disclosed as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Those skilled in the art will also realize that such equivalent constructions do not depart from the spirit and scope of the disclosure in its broadest form.
[0006] Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words or phrases used throughout this patent document: the terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation; the term "or" is inclusive, meaning and/or; the phrases "associated with" and "associated therewith," as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like; and the term "controller" means any device, system or part thereof that controls at least one operation, whether such a device is implemented in hardware, firmware, software or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. Definitions for certain words and phrases are provided throughout this patent document, and those of ordinary skill in the art will understand that such definitions apply in many, if not most, instances to prior as well as future uses of such defined words and phrases. While some terms may include a wide variety of embodiments, the appended claims may expressly limit these terms to specific embodiments.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007] For a more complete understanding of the present disclosure, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, wherein like numbers designate like objects, and in which:
[0008] Figure 1 depicts a block diagram of a data processing system in which an embodiment can be implemented;
[0009] Figure 2 depicts a simplified block diagram of a vehicle management system 200 in accordance with disclosed embodiments; and
[0010] Figure 3 depicts a flowchart of a process in accordance with disclosed embodiments. DETAILED DESCRIPTION
[0011] FIGURES 1 through 3, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged device. The numerous innovative teachings of the present application will be described with reference to exemplary non-limiting embodiments.
[0012] Many companies must manage data for multiple vehicles or even fleets of vehicles. In the rental or car-sharing business, efficiency is important and can be obtained by optimizing processes in the process chain from returned-vehicle processing to preparing and presenting the vehicle to the next customer.
[0013] As used herein, terms such as vehicle, automobile, car, and similar terms are all intended to refer to any roadway vehicle including cars, trucks, other passenger and commercial vehicles, and otherwise.
[0014] Various embodiments described herein are particularly advantageous in the car-rental industry, and the exemplary systems and methods below are described in that context. However, those of skill in the art will recognize that the principles disclosed herein can be applied to any system that manages data for multiple vehicles, and such other implementations are intended to be within the scope of this disclosure.
[0015] Currently, vehicle return handling is mostly a manual or partially automated process. At big rental car facilities, operators perform the return handling using hand-held computers. The operator identifies the returned vehicle by scanning a barcode with the hand-held computer. The barcode is applied on the vehicle or on the customer contract. If there is no barcode in use, the operator identifies the vehicle via the license plate, the contract number, or other identification means and types it into the hand-held computer. Then the operator reads the mileage and fuel level of the vehicle, and enters these into the hand-held computer. For that processing step, the vehicle must be started again because the vehicle's odometer and fuel level gauge indicator functions are typically available only when the vehicle's engine is running or the ignition is on. This additional engine start consumes unnecessary energy and consequently increases pollution. Thus, because of the number of cars handled by each rental car and car sharing agency, the techniques described herein also provide environmental or "green" advantages.
[0016] After or before collecting and entering the vehicle data, the operator performs a manual vehicle inspection by walking around the car, looking for visible damage. If the operator recognizes damage, a look-up of the vehicle condition record in the contract is necessary to determine if the damage is new or was existing at the time the vehicle was issued to the customer.
[0017] After all of these manual procedural steps, the conventional vehicle return-handling operation is finished. If the customer would like to get a printed confirmation, a customer receipt can be printed.
[0018] All current variations in processes for rental-vehicle return require remarkable labor effort, and provide imprecise data to determine the vehicle usage.
[0019] The techniques described herein can reduce operating costs and improve the satisfaction of the customers and users, and can reduce the elapsed time of the vehicle processing chain. Further, disclosed embodiments provide more precise data on vehicle usage, condition, and location.
[0020] Various embodiments can be implemented using one or more data processing systems to perform functions described herein, in conjunction with the other system elements described herein. Figure 1 depicts a block diagram of a data processing system in which an embodiment can be implemented, for example, as a vehicle management system particularly configured by software or otherwise to perform the processes as described herein, and in particular, as each one of a plurality of interconnected and communicating systems as described herein. The data processing system depicted includes a processor 102 connected to a level two cache/bridge 104, which is connected in turn to a local system bus 106. Local system bus 106 may be, for example, a peripheral component interconnect (PCI) architecture bus. Also connected to local system bus 106 in the depicted example are a main memory 108 and a graphics adapter 1 10. The graphics adapter 1 10 may be connected to display 1 1 1.
[0021] Other peripherals, such as local area network (LAN) / Wide Area Network / Wireless (e.g. WiFi) adapter 1 12, may also be connected to local system bus 106. Expansion bus interface 1 14 connects local system bus 106 to input/output (I/O) bus 1 16. I/O bus 1 16 is connected to keyboard/mouse adapter 118, disk controller 120, and I/O adapter 122. Disk controller 120 can be connected to a storage 126, which can be any suitable machine usable or machine readable storage medium, including but not limited to nonvolatile, hard-coded type mediums such as read only memories (ROMs) or erasable, electrically programmable read only memories (EEPROMs), magnetic tape storage, and user-recordable type mediums such as floppy disks, hard disk drives and compact disk read only memories (CD-ROMs) or digital versatile disks (DVDs), and other known optical, electrical, or magnetic storage devices.
[0022] Also connected to I/O bus 116 in the example shown is audio adapter 124, to which speakers (not shown) may be connected for playing sounds. Keyboard/mouse adapter 118 provides a connection for a pointing device (not shown), such as a mouse, trackball, trackpointer, etc.
[0023] Those of ordinary skill in the art will appreciate that the hardware depicted in Figure 1 may vary for particular implementations. For example, other peripheral devices, such as an optical disk drive and the like, also may be used in addition or in place of the hardware depicted. The depicted example is provided for the purpose of explanation only and is not meant to imply architectural limitations with respect to the present disclosure.
[0024] A data processing system in accordance with an embodiment of the present disclosure includes an operating system employing a graphical user interface. The operating system permits multiple display windows to be presented in the graphical user interface simultaneously, with each display window providing an interface to a different application or to a different instance of the same application. A cursor in the graphical user interface may be manipulated by a user through the pointing device. The position of the cursor may be changed and/or an event, such as clicking a mouse button, generated to actuate a desired response.
[0025] One of various commercial operating systems, such as a version of Microsoft Windows™, a product of Microsoft Corporation located in Redmond, Wash, may be employed if suitably modified. The operating system is modified or created in accordance with the present disclosure as described.
[0026] LAN/ WAN/Wireless adapter 112 can be connected to a network 130 (not a part of data processing system 100), which can be any public or private data processing system network or combination of networks, as known to those of skill in the art, including the Internet. Data processing system 100 can communicate over network 130 with server system 140, which is also not part of data processing system 100, but can be implemented, for example, as a separate data processing system 100.
[0027] As noted above, the various processes described herein are particularly useful for vehicle inventory functions and for rental- vehicle return processes. In the rental-return context, the operations from the step of returning the vehicle by the customer to the operating organization, to the step of providing the vehicle again for new customers or users is known as the turnaround process chain. In addition to return handling, this process chain includes all necessary maintenance processes such as cleaning, fuel provision, vehicle inspection, etc., to achieve vehicle readiness. Various embodiment described herein improve the process chain by automating the vehicle turn-around task and providing more precise and actionable data for the follow-up processes.
[0028] Disclosed embodiments include methods, systems, and processes that improve the vehicle return process. These embodiments include an automated system that reduces the manual activities and interaction of the organization's operations personnel to a minimum. In many cases, manual interventions can be reduced to exception handling, and labor efforts can be reduced significantly.
[0029] Various embodiments perform automatic collection of vehicle-related data, providing the additional advantage of collecting precise data to track vehicle usage. The data collected can include mileage data, fuel level data, and time that the vehicle was returned, and other data as described herein. The fuel level and mileage data can be determined, in some embodiment, from the vehicle's on-board self-diagnostic system. The data can be collected from a vehicle unit installed inside the vehicle and transmitted wirelessly to the vehicle management system described herein. This approach can reduce human error in manually reading this information from a vehicle odometer and fuel gauge. This also reduces error caused by deviation in the tolerance of vehicle gauges and indicators.
[0030] Various embodiments can also include an automated, real-time video vision and image processing system. This 3D video inspection system can perform the visual vehicle inspection task automatically. The video inspection system can check the vehicle for visible damage and major color deviations. If the video inspection system identifies such damage, the automation system can issue a notification to alert operations personnel. The video inspection system provides more reliability and consistency compared to human inspectors, and save labor effort and costs regarding vehicle return handling.
[0031] These automated processes improve efficiency and minimize the waiting time of the rental car customer. Using techniques described herein, the customer can drive into the rental car return area, pass through the video inspection system, park and empty the car, and optionally pick up his receipt, all without operations personnel effort. These processes can also be used to receive vehicle returns after business hours.
[0032] The vehicle management system can also automatically update a vehicle inventory database by recognizing the vehicle and gathering any necessary or useful data. The inventory management can include the inventory at many locations, such as the return facility, remote parking, overflow lots, and otherwise, and the specific location of the vehicles can be tracked by direct input, direction to drivers or operators, wireless beacons, global positioning satellite (GPS) data, video tracking, and otherwise.
[0033] Figure 2 depicts a simplified block diagram of a vehicle management system 200 in accordance with disclosed embodiments. Various components are described briefly in the following paragraphs, and other details, features, and alternatives are then described in more detail.
[0034] The system includes a vehicle data collection unit 202 that is connected to and mounted on or inside a vehicle 204. Preferably, vehicle data collection unit 202 is hidden so that renters or other drivers do not have access to it. It can communicate with or be integrated with a GPS receiver also located in the car.
[0035] The system includes a wireless network 206, connected to communicate wirelessly with the vehicle data collection unit 202, and connected to also communicate with the other system components described herein. Wireless network 206 can be implemented, in some cases, as a mesh network with a plurality of nodes connected to intercommunicate data, and can include wired portions. Wireless network 206 can also be connected to network 208, which can be any public or private network, including the Internet, so that any of the functions described herein with regard to the operations of wireless network 206 can also be accomplished using network 208. In other embodiments, wireless network 206 could be implemented using cellular or telephone network systems, with the vehicle data collection unit suitably configured for such communications.
[0036] The system includes a video inspection system 210. Video inspection system 210 includes one or more cameras configured to examine the physical condition of the vehicle, for example, by taking images of the front, back, sides, top, or windows of the vehicle, and can include a video data processing system configured to perform the inspection processes described herein.
[0037] The system includes a server system 212, which can be implemented as one or more data processing systems 100. Server system 212 is configured to perform processes as described herein. In particular, server system 212 can identify the location of each of the vehicles, for example, by receiving GPS location data from each of the vehicle data collection units 202, or by deriving the data from the data received from mesh nodes of wireless network 206, or otherwise. Server system 212 can process vehicle data as described herein. Server system 212 can perform video data processing as described herein, in particular in embodiments where this function is not performed by the video inspection subsystem 210. Server system 212 can maintain, update, and report on a vehicle inventory based on vehicle data. Server system 212 can monitor the turn-around processes and other processes performed as described herein. Server system 212 can process and analyze the collected vehicle data for statistics, reporting, and other functions. Server system 212 can communicate with the other components described herein over wireless network 206 or network 208.
[0038] The system can also include one or more client data processing systems 214, each of which can be implemented as a data processing system 100. The client data processing systems 214 can act, for example, as web-based workstations that can monitor and control various processes described herein, can initiate and produce reports based on the vehicle data, can display alerts and notifications generated by the system, and can otherwise interact with and be controlled by users.
[0039] Vehicle data collection unit 202 can be implemented using an active "tag" connected to the vehicle's controller area network (CAN) bus. The active tag sends and receives data via radio communication with wireless network 206. Based on the on-board diagnostic (OBD) standard mechanism, known to those of skill in the art, the vehicle data collection unit collects various vehicle data identified by parameter identification numbers (PIDs). ODB standards are the basis of the vehicle self-diagnostic standard.
[0040] The vehicle data collection unit 202, in some embodiments, is compliant with the OBD-II 1979 standard, though those of skill in the art will recognize that as vehicle diagnostic and communication standards evolve, the principles disclosed herein will apply to any newer standards as well, and will also apply to any corresponding foreign standards. The SAE J 1979 standard defines a method for requesting various diagnostic data and a list of standard parameters that may be available from the vehicle engine unit. SAE J 1979 currently is a required standard in the United States for all passenger vehicles since 2007. Data is collected at all times as they become available on the vehicles' CAN bus system and stored in the internal storage of the vehicle data collection unit. The stored data can be transferred to the host system when the active tag reaches the radio coverage range of wireless network 206, such as when the network is installed in a rental car company or car- sharing operator premises. To initiate this data transfer, the vehicle data collection unit 202 sent message to connect to the server system 212 over wireless network 206 or network 208.
[0041] Position determination of the vehicle within the operation premises can be implemented by the vehicle data collection unit 202 sending frequent data messages. The position of the vehicle itself can then be determined by the system based on the information detected by wireless network 206, for example by determining that the node of wireless network 206 receiving the highest signal strength from the vehicle data collection unit 202 indicates the approximate location of the corresponding vehicle, for example in a return operation area, cleaning area, parking/storage area, fuel station, etc. If a more precise determination is needed, the position can be calculated using triangulation techniques between several nodes, or using GPS data. Note that GPS implementations are not needed to monitor operations on the premises where the wireless network 206 is located, but can be used where vehicle tracking and vehicle usage analysis extends beyond the premises.
[0042] Vehicle data collection unit 202 can collect, store, and transfer vehicle parameters to the system to enable tracking of the vehicle status and analysis of vehicle usage. These parameters can include the vehicle identification number (VID) or other unique identifier, odometer/mileage data, fuel level data, battery voltage, tire pressure, engine running time, key-on without running engine, vehicle in-use time at configurable speed thresholds, vehicle speed records, engine diagnostic codes (DTCs), and others. With additional appropriate sensors, the vehicle data collection unit 202 can also collect data related to oil level, water level, tampering, etc.
[0043] Wireless network 206 is used because the vehicles to be tracked are mobile assets. The network range should preferably cover at least all process areas to be monitored by the system, should work outdoors and indoors in appropriate implementations, and can be customized to particular implementations. Placement of the nodes (or antennas) of the network can be important for location and triangulation purposes, as will be understood by those of skill in the art. Mesh network implementations can be particularly advantageous for expansion and reconfiguration.
[0044] Video inspection system 210 can perform processes for object identification and 2D and 3D visual inspections. Video inspection system 210 can identify damage and major paint deviations from stored model and color patterns. A shared 3D model structure for the appropriate vehicle can be used and stored in a video template database for retrieval when the vehicle is identified. In particular embodiments, video inspection system 210 can capture and process vehicle images as the vehicle is both leaving and entering the premises, which provides data for use in legal processes and evidence in case of customer disputes or conflicts. Video inspection system 210 can also identify and record the license plate of the vehicle.
[0045] Upon vehicle return or other situations, if the video inspection system 210 identifies damage that is not recorded and archived in a corresponding vehicle condition data set, and operator notification can be issued by the system, for example, at a client data processing system 214. This notification can alert a user, such as operation office or management staff, of such an exception case.
[0046] In some cases, the video inspection system 210 can include such elements as three cameras for right, top, and left of the vehicle, trigger equipment for image acquisition, such as a motion sensor, photosensor, by notification by the system, or otherwise, and appropriate processors, software, storage, and other elements. The vehicle model data and color pattern can be populated into a video database by auxiliary function of a vehicle configuration setup and vehicle registration process.
[0047] The system can maintain databases and appropriate executable software for the processes described herein. In some embodiments, functions described herein are implemented using MICROSOFT WINDOWS® and JAVA® software technology. Various processes can be hosted and run one or more server systems 212, which can perform the various processes described herein. Various processes can be performed either by the server system 212 or by the client data processing system 214. Various such processes include automatic vehicle identification, real-time position detection for each vehicle, transfer of the vehicle data between the various systems described herein, and consolidation, processing, and storage of the vehicle data. Other processes can include analyzing the vehicle data to determine vehicle usage data, determining corresponding billing and usage payment data, and, in some cases, exporting such information to external billing systems.
[0048] Other processes performed by the system can include checking for contract/agreement compliance based on the vehicle data, notification to users if the vehicle usage is not compliant, and correlating data from the vehicle inspection system 210, including images and the inspection result, with the corresponding vehicle data and any contract/agreement information.
[0049] Other processes performed by the system can include updating vehicle inventory data by capturing departure and arrival events of vehicles, process monitoring and comparison with process and performance standards, and calculation of key performance indicators. Other processes performed by the system can include issuing vehicle-specific work orders at the end of the return-handling operations, supporting vehicle maintenance for all registered vehicles, statistics, reporting, and system administration including user management, base data editing, system configuration setup, and vehicle registration.
[0050] Client data processing systems 214 can include a graphical user interface for interacting with users to perform functions as described herein. Client data processing systems 214 can display alerts, notifications, dialog screens, and otherwise interact with users to perform various processes. Such processes can include vehicle usage analysis and management, customer billing, fuel management, vehicle maintenance management, inventory updates, alert and notification services, query functionality for specific vehicles and vehicle groups, display of key process indicators, such as in table or graphical format, and statistics and reposting, including selecting and initiating report presentations. The system can provide alert and notification services, as well as performance monitoring, for all measurable processes described herein. [0051] In multi-location implementations, each location may have one or more of the components indicated above, and the systems at each location can communicate with each other, for example, over network 208.
[0052] Figure 3 depicts a flowchart of a process in accordance with disclosed embodiments that may be performed, for example, by a vehicle management system.
[0053] The system detects an approaching vehicle (step 305). This can be performed, for example, by the system detecting and communicating with the vehicle data collection unit in the vehicle.
[0054] The system receives vehicle data from the vehicle data collection unit (step 310). This can include, for example, a vehicle identifier such as a VIN or other unique identifier, other parameters and data as described above, and any other data contained in the internal storage of the vehicle data collection unit. As part of this step, the system can determine the day and time (arrival timestamp) of the return.
[0055] The system can load stored vehicle data corresponding to the vehicle identifier (step 315). This can include the vehicle configuration, the vehicle base location, the previous vehicle condition, any current contract on the vehicle, and other data.
[0056] The system performs a video inspection of the vehicle (step 320). This can include taking images of the vehicle, deriving a data model and color pattern from the images and comparing them to a stored data model and color pattern corresponding to the vehicle, and determining, based on the comparison, whether there is any potential new damage. If there is potential new damage, this step can include making an alert or notification to a user as described herein.
[0057] The system can update the vehicle inventory to reflect that the vehicle has been returned (step 325).
[0058] The system can generate one or more reports according to one or more of the video inspection, the received vehicle data, and the stored vehicle data (step 330). The report can include a receipt for delivery to the customer, a report of damage to the vehicle, a usage summary for the contract period, and otherwise. If damage was detected during the video inspection, the receipt can indicate the damage, and the system can alert an operator or employee to deal with the customer. The report can be displayed, printed, stored, or any combination of these.
[0059] The system can generate a work order corresponding to one or more of the video inspection, the received vehicle data, and the stored vehicle data (step 335). As part of this step, the system determines what actions need to be taken to prepare the vehicle for its next rental or other use. In addition to other information, the work order can be based on a historical maintenance record and vehicle health data included in the stored vehicle data, such as fuel level, mileage, battery voltage, tire pressure, any DTC information, etc.
[0060] The system can store any reports, received vehicle data, and any other generated data in the vehicle database as updated stored vehicle data (step 340).
[0061] Additionally, during each of the steps above, the system can detect and record the current location and status of each vehicle, such as returned, in queue, being inspected, being cleaned, maintained, repaired, or otherwise processed, or otherwise. Note that the processes described above, unless specifically noted, can be performed automatically without operator intervention on the part of the business, though of course the driver/renter is still operating the vehicle at some points. That is, from the moment that the approaching vehicle is noted, the system can perform the processes as described above, including performing a vehicle inspection as the driver drives the vehicle past or through the video inspection system, without intervention of the system operators or other employees in most cases. By automatically detecting, receiving data from, and inspecting the vehicle, the system provides a much more accurate and efficient process of vehicle management.
[0062] The system can also provide inventory functions for work areas, and update the work area inventories as vehicles are moved between work areas. The system can also respond to queries for inventor management or other functions. Queries can be directed to specific vehicles or vehicle groups, and can include various selectable search filters, such as VIN, license plate number, state of registration, mileage, manufacturer, model, make, year, etc.
[0063] Of course, those of skill in the art will recognize that, unless specifically indicated or required by the sequence of operations, certain steps in the processes described above may be omitted, performed concurrently or sequentially, or performed in a different order. Further, no component, element, or process should be considered essential to any specific claimed embodiment. [0064] Those skilled in the art will recognize that, for simplicity and clarity, the full structure and operation of all data processing systems suitable for use with the present disclosure is not being depicted or described herein. Instead, only so much of a data processing system as is unique to the present disclosure or necessary for an understanding of the present disclosure is depicted and described. The remainder of the construction and operation of data processing system 100 may conform to any of the various current implementations and practices known in the art.
[0065] It is important to note that while the disclosure includes a description in the context of a fully functional system, those skilled in the art will appreciate that at least portions of the mechanism of the present disclosure are capable of being distributed in the form of instructions contained within a machine-usable, computer-usable, or computer-readable medium in any of a variety of forms, and that the present disclosure applies equally regardless of the particular type of instruction or signal bearing medium or storage medium utilized to actually carry out the distribution. Examples of machine usable/readable or computer usable/readable mediums include: nonvolatile, hard-coded type mediums such as read only memories (ROMs) or erasable, electrically programmable read only memories (EEPROMs), and user-recordable type mediums such as floppy disks, hard disk drives and compact disk read only memories (CD-ROMs) or digital versatile disks (DVDs).
[0066] Although an exemplary embodiment of the present disclosure has been described in detail, those skilled in the art will understand that various changes, substitutions, variations, and improvements disclosed herein may be made without departing from the spirit and scope of the disclosure in its broadest form.
[0067] None of the description in the present application should be read as implying that any particular element, step, or function is an essential element which must be included in the claim scope: the scope of patented subject matter is defined only by the allowed claims. Moreover, none of these claims are intended to invoke paragraph six of 35 USC § 112 unless the exact words "means for" are followed by a participle.