AU2013101587A4 - System and Method for Management and Tracking of Vehicles - Google Patents

Abstract

Abstract A system for populating a driver profile in association with a driver's use of a vehicle from a vehicle dealer. The system includes a driver database for storing a plurality of driver profiles, and an access terminal having a keyless data input means for transferring portions of a driver's identification data into one of the driver profiles. Drive Agreement Flow Diagram o12 Driver lice r i rlinc Sales Replogsrrea'sdetail Mctr ontod~k enee MauacuenadM toh emnfctr touhasreefih aistancen of~~ driver feeba cacDrivenagreementt showroop erface co plte by Rep~~nrn &tor Tht vreuInhj ~~ean ate~reDriverh ande the by Driver &dt o eaep fodr

Description

1 SYSTEM AND METHOD FOR MANAGEMENT AND TRACKING OF VEHICLES Field of the Invention [0001] The present invention relates to improvements in systems for management reporting for motor dealers and motor vehicle manufactures. Background of the Invention [0002] It is often required that a driver desiring to borrow or test drive a vehicle provide contact information. The driver is usually handed a form to fill out. The processing of such forms leads to inefficiencies, particularly if the driver's handwriting is illegible. This impacts the ability to obtain relevant information from the driver, such as the driver's opinions on certain features of the vehicle being test-driven since the most optimal time in which to obtain driver survey information is during or shortly after the vehicle test drive. Accordingly, there exists a need to provide an improved system and method for obtaining driver identification and survey information which overcomes the inefficiencies of conventional systems. [0003] It will be clearly understood that, if a prior art publication is referred to herein, this reference does not constitute an admission that the publication forms part of the common general knowledge in the art in Australia or in any other country. Summary [0004] The present invention in one preferred aspect provides for a system for populating a user profile in association with a driver's use of a vehicle from a vehicle dealer. The system includes a driver database for storing a plurality of driver profiles, each driver profile including preconfigured fields for driver identification data and vehicle identification data of a vehicle which the driver intends to test-drive. The system further includes an access terminal having a 2 keyless data input means for transferring at least a portion of the driver's identification data into one of the driver profiles. [0005] In another preferred aspect, the present invention provides a method for electronically registering a driver for a test drive of a vehicle being offered for sale. The method includes: reading a portion of the driver's identity data with an electronic device; storing the identity data read from the electronic device in a driver profile; selecting a vehicle for the driver to test drive; and storing identity data associated with the selected vehicle with the driver profile. [0006] In a further preferred aspect, the present invention provides for a method for collecting driver preference data following a test drive of a vehicle being offered for sale. The method includes: electronically providing a driver experience survey to a driver of the vehicle being test driven, the survey being provided within 30 minutes of completion of the test drive; receiving the driver's response to the survey; and storing results of the survey in a database. [0007] In an additional preferred aspect, the invention provides for a system for populating a user profile in association with a driver's use of a vehicle from a vehicle fleet. The system includes a driver database for storing a plurality of driver profiles, each driver profile including preconfigured fields for driver identification data and vehicle identification data of a vehicle which the driver intends to borrow. The system further includes an access terminal having a keyless data input means for transferring at least a portion of the driver's identification data into one of the driver profiles. [0008] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed. In the present specification and claims, the word "comprising" and its derivatives including "comprises" and "comprise" include each of the stated integers, but does not exclude the inclusion of one or more further integers.

3 [0009] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several embodiments of the invention and together with the description, serve to explain the principles of the invention. Brief Description of the Figures [0010] Fig. 1 is a diagrammatic representation of a system and method for obtaining and utilising driver data in accordance with a preferred embodiment of the present invention. [0011] Fig. 2 is a screen shot of a graphic user interface with predefined fields for driver name and license data for the system of Fig. 1. [0012] Fig. 3 is a screen shot of a graphic user interface with predefined fields for driver address, e-mail and phone number data for the system of Fig. 1. [0013] Fig. 4 is a screen shot of a graphic user interface with pull-down menus and predefined fields for entry of vehicle information for the system of Fig. 1. [0014] Fig. 5 is a test drive agreement generated by the system of Fig. 1 using data entered in the graphic user interfaces of Figs. 2, 3 and 4. [0015] Fig. 6 is a graphical representation of the number of test drives over a given period of time as part of a report generated in accordance with another preferred embodiment of the present invention. [0016] Fig. 7 is a graphical representation of the number of test drives by vehicle model as part of the report generated in the embodiment of Fig. 6. [0017] Fig. 8 is a graphical representation of the number of test drives associated with a particular sales person as part of the report generated in the embodiment of Fig. 6.

4 Detailed Description of the Drawings [0018] Reference will now be made in detail to the present preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings. [0019] Fig. 1 shows a preferred embodiment of a system 100 for obtaining and utilising driver data. System 100 preferably includes an access terminal 102 operationally connected to a driver database 104. In use, a driver visits a showroom of a vehicle dealer, selects a vehicle they wish to test drive, presents an ID that is read by access terminal 102 to populate a driver agreement form, and signs the driver agreement form, which is preferably stored and maintained in a driver profile associated with the driver. The system described below is generally described using an example of a vehicle test-drive from a vehicle dealer. It will be appreciated that the system is applicable to other environments, such as, for example only, fleet vehicle management. The preferred elements of system 100 and their interrelationship are described in further detail below. [0020] Referring to Fig. 1, access terminal 102 is preferably in the form of a kiosk 106 having a keyless data input means 108. In a preferred form, keyless data input means 108 includes any one or more of a card reader, a chip reader, a scanner, and/or a barcode reader. More preferably, data input means 108 is configured to read a chip 110 contained on an identification card such as driver's licence 112. A keyless data input means has many advantages over data input means requiring manual sequential input of letters and numbers. For example, reading personal identification data from a chip minimises the risk of typographical errors, and speeds the creation of a driver profile (described in more detail below) and generation of forms. [0021] If desired, the access terminal may be formed as part of a mobile communications device such as a smartphone, tablet computer and/or laptop computer. The access terminal may further include a keyboard (push-key or digital) for manual key entry of data if desired.

5 [0022] With continued reference to Fig. 1, kiosk 106 is preferably operationally connected to a network printer 114 for printing out hard copies of any details entered in by a user (sales representative and/or driver). Kiosk 106 is also preferably connected to a driver database 104 for storing a plurality of driver profiles. Each driver profile preferably includes fields for driver identification and/or contact information, vehicle identification data of a vehicle which the driver intends to test drive, and driver preferences from survey information (described in further detail below). For example only, the driver preference data may include any one or more of the driver's assessment of a particular sales associate, driver preferences regarding the vehicle they test-drove, and preference information regarding the dealership where the test drive originated. Driver database 104 may be formed as a physical on-site or off-site server, or formed as an electronic database in the Cloud (or a combination of any of the foregoing). [0023] System 100 preferably includes an analytics database (not illustrated). The analytics database preferably includes data from a plurality of driver profiles. Such data may include driver preference data regarding the test drive experience. For example, the driver may be surveyed regarding their opinion about the dealership from where the test drive took place, the sales associate they used, their opinion of the vehicle test-driven, and a variety of other items. Survey information may be collected regarding the driver's opinion on an array of items such as, but not limited to, vehicle size, type (sport utility, sedan, etc.), noise, colour, convenience of features, road performance, and many other items. This data is preferably organised and available for the generation of different reports, as will be described in further detail below. [0024] System 100 further preferably includes a processor for generating reports utilising information stored in any of the databases. Example reports include a report regarding sales associate performance using at least a portion of the driver's assessment data stored in the driver profiles, and driver preferences for different features of the vehicle test-driven. The details of the reports may be shared amongst car dealerships and/or car manufactures.

6 [0025] It will be appreciated that any of the components of system 100 may be wired or wirelessly connected to each other. [0026] Figs. 2 to 4 show a series of preferred graphic user interfaces (GUls) for use in generating a test drive agreement. The graphic user interfaces illustrated in Figs. 2 to 4 preferably include a plurality of predefined fields for entry of driver details and the details of a vehicle which the driver intends to test drive. The particular details of the graphic user interfaces illustrated in Figs. 2 to 4 will be described in further detail in relation to a preferred method for registering driver details. [0027] Referring to Fig. 2, graphic user interface 120 preferably includes a plurality of predefined fields for entry of the driver's personal and identity information. For example only, field 122 is preferably configured for entry of the driver's name details. Field 124 is preferably configured for entry of the licence number of the driver. Field 126 is preferably configured for entry of the driver's birth date. The driver details may be entered manually, or may be read and/or scanned into database 104 as mentioned above using NFC technology alone, or in conjunction with a card reader. [0028] Fig. 3 shows an exemplary graphic user interface 128 for entry of driver contact details. Graphic user interface 128 preferably includes a field 130 for entry of the driver's residence information; a field 132 for entry of the driver's electronic contact details, for example, e-mail address; and a field 134 for entry of the driver's phone number. It will be appreciated that the fields for the contact information may be varied as desired. For example only, additional fields may be included, or fields omitted depending upon the desired application. If desired, the driver details shown in graphical user interfaces 120 and 128 may be manually entered into the interface by the driver with or without the assistance of a representative, or the driver contact details may be electronically entered into driver database 104 using any of the input means referred to above. [0029] Fig. 4 shows an exemplary graphic user interface 136 for entry of vehicle details. In particular, graphic user interface 136 preferably contains a 7 plurality of pull down menus and data entry fields for entry of the vehicle data. Referring to Fig. 4, graphic user interface 136 preferably includes a pull-down menu 138 containing a list of dealership branches. Pull-down menu 140 preferably includes a list of vehicle makes. A further pull-down menu may be included with a listing of vehicle models. Graphic user interface 136 preferably includes a pre-configured field 142 for entry of the registration data of the vehicle which the driver intends to test drive. Additional fields and/or pull-down menus may be included as desired. It will be appreciated that the form of data entry may be varied and not restricted to pull-down menus or entry fields. [0030] Fig. 5 shows an exemplary driver agreement 146 generated using the data inputted into graphic user interfaces 120, 128 and 136. [0031] Having described the preferred components of system 100, a preferred method of use 200 will now be described with reference to Figs. 1-5. Referring to Fig. 1, a driver preferably approaches kiosk 106, positions their driver's licence 112 in close proximity to keyless data input means 108 so that input means 108 will read chip 110 preferably using Near Field Communications (NFC) technology. Chip 110 preferably includes the driver's details such as, for example, the driver's first name, last name, address details, electronic contact details (e.g., e-mail) and driver's licence number. In step 202, a sales representative logs onto the showroom touch screen interface on kiosk 106. Next, in step 204, the driver enters their details into driver input means 108 preferably using a chip reader and their driver's licence 112 with chip 110. The driver details are preferably such as illustrated in Figs. 2 and 3 and preferably include the name details, the driver's licence details, the date of birth of the driver, and the driver contact details such as, for example only, residential address, electronic contact details, and a contact telephone number. [0032] Referring to Figs. 1, 4 and 5, once all the driver and vehicle details have been entered into driver database 104, in step 206, the representative and/or the driver may access link 144 to generate drive agreement 146. Test drive agreement 146 preferably is generated via network printer 114 and includes 8 all the details entered into graphic user interfaces 120, 128, and 136. Once test drive agreement 146 has been printed out, the driver signs the document in step 208, which is returned to the representative for storage either in paper form and/or electronic form. Agreement 146 may be electronically signed without printing out the document if desired. The driver agreement is preferably loaded to driver database 104 in step 210. Thereafter, in step 212, the driver proceeds to test drive the chosen vehicle. Upon completion of the test drive, in step 214 the driver is preferably solicited for their opinion of the vehicle and their experience in the dealership. The driver feedback is preferably entered into one or more data screens at kiosk 106. After a predetermined period of time, in step 216, the driver is sent an online satisfaction survey using the electronic contact details that were collected during step 204. If desired, in step 218, the driver may have a brochure e-mailed to them using the electronic details collected in step 204. In step 220, details of the driver's experience may be accessed from driver database 204. System 100 may form part of a web platform that includes access means permitting motor vehicle dealer 116 and/or motor vehicle manufacturer 118 to access details of the driver, including the driver contact details and/or survey details. [0033] It will be appreciated that the steps described above may be performed in a different order, varied, or certain steps added or omitted entirely without departing from the scope of the present invention. For example only, instead of using kiosk 106 to enter survey information, survey questions may be presented to the driver using a mobile communications device present in the vehicle, or the driver's own mobile communications device. This advantageously permits the survey to be conducted in real-time, during the test drive, or shortly after the test drive. [0034] As described above, system 100 preferably includes a means to collect survey information from the driver regarding the driver's experience with the vehicle and/or the dealership. Preferably, the driver preference data is collected following the test drive of the vehicle being offered for sale. A method for collecting driver preference data preferably includes electronically providing a 9 driver experience survey to the driver of the vehicle being test driven. Preferably, the survey is provided within 30 minutes of completion of the test drive. The details of the driver's response to the survey are preferably electronically received, collected and stored in driver database 104. Once stored, the survey results may be shared with another dealership and/or with a vehicle manufacturer of the vehicle that was test driven by the driver. If desired, the survey may be provided to the driver within 5 minutes of completion of the test drive, more preferably provided at completion of the test drive. If desired, the completion of the test drive may be determined upon electronic detection of the vehicle within the dealership. If desired, the survey may be provided during the test drive. [0035] It will be appreciated that the steps described above may be performed in a different order, varied, or certain steps added or omitted entirely without departing from the scope of the present invention. [0036] Figs. 6 to 8 show example reports that may be generated using the survey results obtained during the above-described method for collecting driver preference information. In particular, referring to Fig. 6, a report 300 may be generated which shows the frequency of test drives during a predetermined period of time. Fig. 7 shows a report 302 of the number of test drives per a make and/or model of vehicle. Fig. 8 shows a report 304 detailing the number of test drives per salesperson. It will be appreciated that the above-described reports are examples only, and any number of different types of reports may be generated. [0037] The foregoing description is by way of example only, and may be varied considerably without departing from the scope of the present invention. For example only, the data input means on the kiosk may include a card reader, a chip reader, a barcode reader, or any combination of the foregoing. If desired, the access terminal may be in a form other than a kiosk. For example only, the access terminal may be formed as part of a mobile communications device such as, but not limited to, a smart phone, a tablet computer, and/or a laptop computer.

10 Driver database 104 may be formed as a remote server and/or may store data in the Cloud. [0038] The present invention in a preferred form provides the advantages of providing accurate driver feedback regarding the vehicle that was test driven and the experience of the driver with the dealership including any salespersons. The survey information may also include demographic information which can be quite useful to car manufacturers. The survey information may preferably be used to evaluate sales associate performance, which may be used by a car dealer to evaluate the effectiveness of a particular sales associate. The data collected may be further analysed and used to suggest or recommend other makes or models to the test driver in the event that the test driver does not follow through with a purchase of the test vehicle. [0039] The features described with respect to one embodiment may be applied to other embodiments, or combined with or interchanged with the features of other embodiments, as appropriate, without departing from the scope of the present invention. [0040] Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

Claims (35)

1. A system for populating a user profile in association with a driver's use of a vehicle from a vehicle dealer, said system including: a driver database for storing a plurality of driver profiles, each driver profile including preconfigured fields for driver identification data and vehicle identification data of a vehicle which the driver intends to test-drive; and an access terminal having a keyless data input means for transferring at least a portion of the driver's identification data into one of the driver profiles.

2. The system of claim 1, wherein said keyless data input means includes a card reader.

3. The system of claim 1, wherein said keyless data input means includes a chip reader.

4. The system of claim 1, wherein said keyless data input means includes a scanner for scanning information from a card.

5. The system of claim 1, wherein said keyless data input means includes a magnetic strip reader.

6. The system of claim 1, wherein said keyless data input means includes a barcode reader.

7. The system of claim 1, wherein said keyless data input means includes a chip reader and a magnetic strip reader.

8. The system of any one of the above claims, wherein said access terminal is a kiosk.

9. The system of any one of claims 1-7, wherein said access terminal is incorporated as part of a mobile communications device. 12

10. The system of claim 9, wherein said mobile communications device includes a tablet computer.

11. The system of claim 9, wherein said mobile communications device includes a smartphone.

12. The system of any one of the above claims, wherein said database is incorporated into the Cloud.

13. The system of any one of claims 1-11, wherein said database is physically stored on a database server.

14. The system of any one of the above claims, further including an analytics database for storing driver preference data associated with a vehicle category.

15. The system of claim 14, wherein the driver preference data includes a vehicle model.

16. The system of claim 14, wherein the driver preference data includes data collected from a plurality of driver profiles.

17. The system of any one of the above claims, further including a processor for generating a driver agreement using at least a portion of the data stored in one of the driver profiles.

18. The system of any one of claims 1-16, wherein the driver profile includes a preconfigured field for the driver's assessment of a sales associate.

19. The system of claim 18, further comprising a processor for generating a report regarding sales associate performance using at least a portion of the driver's assessment data stored in the driver profiles.

20. The system of any one of the above claims, wherein the driver identification data includes the driver's name and contact address.

21. A method for electronically registering a driver for a test drive of a vehicle being offered for sale, the method including: 13 reading a portion of the driver's identity data with an electronic device; storing the identity data read from the electronic device in a driver profile; selecting a vehicle for the driver to test drive; and storing identity data associated with the selected vehicle with the driver profile.

22. The method of claim 21, further including receiving data regarding the driver's experience with the vehicle test-driven by the driver.

23. The method of claim 21, further including receiving data from the driver that includes the driver's intent to purchase the vehicle test driven by the driver.

24. The method of claim 23, further including sharing the driver experience data with the manufacturer of the vehicle.

25. The method of any one of claims 22-24, wherein the driver experience data includes survey information regarding the driver's preferences for particular features and/or functions of the vehicle that was test driven by the driver.

26. The method of any one of claims 21-25, further including receiving data regarding the driver's experience with a sales associate.

27. The method of claim 26, further including generating a sales associate performance report using at least a portion of the data received regarding the driver's experience with the sales associate.

28. A method for collecting driver preference data following a test drive of a vehicle being offered for sale, the method including: electronically providing a driver experience survey to a driver of the vehicle being test driven, the survey being provided within 30 minutes of completion of the test drive; receiving the driver's response to the survey; and 14 storing results of the survey in a database.

29. The method of claim 28, further including sharing the survey results with another dealership.

30. The method of claim 28, further including sharing the survey results with a vehicle manufacturer.

31. The method of any one of claims 28-30, wherein the survey is provided to the driver within 5 minutes of completion of the test drive.

32. The method of any one of claims 28-31, wherein the survey is provided at the completion of the test drive.

33. The method of claim 32, wherein the completion of the test drive is determined upon electronic detection of the vehicle within the dealership.

34. The method of any one of claims 28-32, wherein the survey is provided during the test drive.

35. A system for populating a user profile in association with a driver's use of a vehicle from a vehicle fleet, said system including: a driver database for storing a plurality of driver profiles, each driver profile including preconfigured fields for driver identification data and vehicle identification data of a vehicle which the driver intends to borrow; and an access terminal having a keyless data input means for transferring at least a portion of the driver's identification data into one of the driver profiles.