JP4637208B2 - Vehicle inspection and maintenance information management system for service stations - Google Patents

Description

  The present invention relates to a system for managing information relating to vehicle inspection and maintenance carried out at a service station, which is connected to a network (data communication network).

  In recent years, due to the deregulation measures related to the vehicle inspection and maintenance system, the 6-month legal inspection of vehicles that had been obligated in the past has been abolished, and the 12-month legal inspection has been greatly simplified. At the same time, it was clarified that the responsibility for vehicle maintenance management lies with the user himself, and the importance of carrying out vehicle inspection and maintenance at the discretion of the user has increased.

  Vehicle inspection and maintenance is not limited to card dealers and vehicle maintenance factories, but is also performed at service stations (hereinafter referred to as SS), car goods shops, and the like. Among these, SS is a place where there are about 47,000 stores nationwide, and users use it at a relatively high frequency (for example, about once or twice a month) for refueling. Therefore, the vehicle inspection and maintenance service at the SS is easy for the user to use.

  Conventionally, a vehicle inspection / maintenance information management system has been proposed in which the results of inspection / maintenance performed in the SS can be viewed from a terminal such as a personal computer or a mobile phone using a network such as the Internet (Patent Document 1). reference). By this system, the user himself / herself can easily confirm the results and history of vehicle inspection and maintenance performed at the SS, and the user's awareness of vehicle inspection and maintenance is improved.

  The service of vehicle inspection and maintenance at the SS has the advantage that the SS can lead to sales of products other than fuel oil (for example, tires and engine oil) and orders for paid maintenance services.

JP 2002-92213 A

  In the vehicle inspection and maintenance information management system, a user of a vehicle that has been inspected and maintained is determined using a fueling card in which personal information such as the user's name is recorded. Therefore, in order to use the above system, the user performs a refueling card issuance procedure at the SS. However, the procedure is cumbersome and personal information must be provided, so some users hesitate to do so.

  It is also conceivable that the user inputs information necessary for using the system from a user terminal connected to the network and performs the registration procedure in the system instead of performing the refueling card issuing procedure at the SS. At this time, at least information for specifying the vehicle of the user is necessary. As such information, it is common to use numbers and letters written on a license plate. However, since the information on the license plate can be easily obtained by a third party by looking at the vehicle, the third party can register the license plate information of others from a terminal connected to the network, There is a risk of illegally browsing the inspection and maintenance results of other people's vehicles.

  The present invention has been made to solve the above-described problems. The purpose of the present invention is not to perform registration procedures necessary for the use of the system in the SS, and consideration is given to the handling of personal information. Another object of the present invention is to provide a vehicle inspection and maintenance information management system capable of preventing a third party from illegally registering or browsing information on another person's vehicle.

The vehicle inspection and maintenance information management system according to the present invention, which has been made to solve the above problems,
An SS terminal that is installed at a service station and into which a vehicle identification number and inspection data of a vehicle inspected and maintained by the service station are input;
Together are connected via the SS terminal and a network, which can log in with a unique account from a user terminal connected to said network, said vehicle identification number, the servicing data and said account associated with each other A server having a database to be stored
A vehicle inspection and maintenance information management system comprising:
The SS terminal is
An access key issuing means for issuing an access key corresponding to the vehicle identification number when the vehicle identification number is input to the SS terminal;
The server is
When a vehicle identification number is received from a user terminal logged in using the account, the account is associated with the vehicle identification number, stored in the database, and temporarily registered with the vehicle identification number corresponding to the account When,
Storage means for receiving the access key created at the SS terminal from the SS terminal, and storing the access key and the maintenance data in the database in association with the vehicle identification number;
The temporary registration receives the access key corresponding to said vehicle identification number from the user terminal to log in using the account corresponding to the vehicle identification number has been performed, the relative said servicing data associated with the vehicle identification number A registration means that allows access from the account;
Inspection and maintenance data transmitting means for transmitting the inspection and maintenance data associated with the account to the user terminal in response to an instruction from the user terminal logged in using the account corresponding to the vehicle identification number for which the main registration has been performed. When,
It is characterized by providing.

  The “vehicle identification number” means information of numbers and characters used for vehicle identification such as a license plate and a vehicle body number. Further, the “inspection / maintenance data” means data relating to inspection results and maintenance contents of inspection / maintenance items of vehicles, work dates / places of inspection / maintenance, and the like.

  According to the vehicle inspection and maintenance information management system according to the present invention, the user simply enters the access key issued by the SS into the user terminal connected to the network, and browses the inspection and maintenance data regarding the user's vehicle from the terminal. Therefore, it is not necessary to perform complicated registration procedures at the SS. Moreover, since this system does not use personal information to specify the user's vehicle, the user does not need to provide personal information to the SS side. In addition, a vehicle identification number such as a license plate is input from a terminal installed at the SS, and inspection and maintenance data cannot be viewed without an access key issued by the input. It is possible to prevent the number from being registered without permission and unauthorized viewing of information related to the vehicle.

  FIG. 1 shows a schematic diagram of a network including a vehicle inspection and maintenance information management system according to an embodiment of the present invention. The network 10 is an existing network such as the Internet. The network 10 includes a server 20 in which a database server program and a Web server program are installed, an SS terminal 30 installed in each service station (SS) in which a vehicle inspection and maintenance service is performed, and in which a database client program is installed. A user terminal 40 such as a personal computer or a mobile phone provided with a Web browser is connected. Each SS terminal 30 is connected to an input device 31 for inputting a vehicle identification number, inspection and maintenance data, and a printer 32 for printing inspection and maintenance results.

  FIG. 2 shows a configuration diagram of the database 21 managed by the database server program of the server 20. The database 21 is provided with a vehicle master 22 and a member master 23 in association with each other. An inspection history table 24, a maintenance history table 25, and a sales history table 26 are associated with the vehicle master 22, an inspection result master 27 is associated with the inspection history table 24, and a product master 28 is associated with the sales history table 26. It has been.

  In the vehicle master 22, a vehicle identification number, an access key and access permission data described later are registered. Here, as the vehicle identification number, a vehicle number that is a number or a letter written on the license plate of the vehicle is used, but a vehicle body number or the like may be used. In the vehicle master 22, various information related to the vehicle such as a manufacturer name, a vehicle type name, a form, and vehicle inspection information of each vehicle is also registered. In order to prevent duplicate registration of the same vehicle, it is preferable to set the main key in the vehicle master 22 to the vehicle identification number.

  In the inspection history table 24, the work date of the vehicle inspection, the place of execution, and the results of the inspection items performed are registered. The inspection items are, for example, tires, washer fluid, wiper blades, batteries, brake lamps, engine oil, radiator fluid, automatic oil, brake fluid, and the like. In the inspection result master 27, as shown in FIG. 3, the inspection item 272 and the inspection result 273 are registered corresponding to the main key 271 of the inspection result master 27, and the fixed sentence is corresponding to them. The comment 274 and the importance 275 which is an index indicating whether or not the comment 274 should be transmitted to the user are registered. The result 273 and the importance 275 are preferably expressed in stages such as numerical values, ◯, Δ, and x.

  In the maintenance history table 25, the vehicle maintenance work date, the place of implementation, and the contents of the implementation are registered. The implementation content may be registered separately for the headline and the detailed content.

  In the sales history table 26, a product identification code (for example, JAN code) of a product sold for each vehicle, a sales date thereof, and the like are registered. In the product master 28, a product name, a manufacturer name, a price, etc. corresponding to the product identification code are registered.

  In the member master 23, a user-specific account and password are registered. Also, the user's e-mail address, name, address, telephone number, etc. may be registered. Each account is associated with one or more vehicle identification numbers of the vehicle master 22.

  The server 20 implements a function of receiving a vehicle identification number and inspection maintenance data input to each SS terminal 30 and registering them in the database 21 by executing a database server program. In addition, a function of transmitting data stored in the database 21 to each SS terminal 30 and a function of extracting data in response to a data browsing request instructed by the Web server program are realized.

  The server 20 executes a Web server program to realize a function of transmitting HTML data such as an HTML (HyperText Markup Language) document or an image representing a website to the user terminal 40 in accordance with an instruction from the user terminal 40. . In addition, a function of creating a command statement for the database server program in response to an instruction from the user terminal 40, a function of converting data extracted from the database 21 into a form that can be viewed with a Web browser, and the like, are also provided. Realize.

  The input device 31 connected to the SS terminal 30 may be a general keyboard, mouse, or the like. However, in order to input inspection and maintenance data at the inspection and maintenance work place, wireless communication with the SS terminal 30 is possible. A portable information terminal such as a PDA (Personal Digital Assistant) is preferable.

  The SS terminal 30 is provided with an SS database managed by a database client program. The SS database includes the same vehicle master 22, inspection history table 24, maintenance history table 25, sales history table 26, inspection result master 27, and product master 28 provided in the database 21 of the server 20. Since the member master 23 may include personal information, it is preferably not included in the SS database in order to reduce the possibility of leakage of personal information.

  The SS terminal 30 executes a database client program to perform data communication with the server 20 and a function for registering data input by the input device 31 in the SS database, and synchronizes a master and a table common to each database. Realize functions.

  In order to use the vehicle inspection and maintenance information management system of this embodiment, the user registers an account in this system. The procedure may be any known method. Thereafter, provisional registration of the vehicle number is performed as follows.

  FIG. 4 is a flowchart showing a procedure for temporarily registering the vehicle number. The user logs in to the system from the user terminal 40 using the registered account, and causes the user terminal 40 to display a member-only screen (step S11). When the user clicks a new vehicle information registration button in the screen, the user terminal 40 transmits a URL (Uniform Resource Locator) corresponding to the button to the server 20 (step S12). When the server 20 receives the URL, the server 20 transmits HTML data representing the vehicle number temporary registration screen shown in FIG. 5 to the user terminal 40 (step S31). When the user number is displayed in the vehicle number input box 50 and the temporary registration button 51 is clicked, the user terminal 40 transmits the input vehicle number to the server 20 (step S13). The server 20 registers the received vehicle number in the database 21 (step S32), and transmits HTML data representing a member-only screen on which the temporarily registered vehicle number 52 is described as shown in FIG. 6 to the user terminal 40. (Step S33). The user terminal 40 displays the screen (step S14) and informs the user that the vehicle number has been provisionally registered in the present system. The server 20 transmits the registered vehicle number to each SS terminal 30 (step S34). The SS terminal 30 registers the received vehicle number in the SS database (step S51).

  Next, the system issues an access key corresponding to the temporarily registered vehicle number, and performs the main registration of the vehicle number using the access key. FIG. 7 is a flowchart showing a procedure for issuing an access key and registering the vehicle number. After the vehicle number of the user's vehicle is provisionally registered as described above, when the vehicle is inspected and maintained at the SS, the vehicle number of the vehicle and the inspection and maintenance result (inspection and maintenance data) are input to the SS terminal 30. (Step S52). The SS terminal 30 registers the input inspection and maintenance data in the SS database in association with the vehicle number (step S53). The SS terminal 30 creates an access key corresponding to the vehicle number (step S54), creates print data including the access key and check maintenance data, and uses the print data to check the maintenance result sheet from the printer 32. Is printed (step S55). At this time, the comment 274 registered in the inspection result master 27 of the SS database may be printed together with or instead of the inspection maintenance data. Furthermore, only the comment 274 having a high importance may be selectively printed based on the importance 275 registered in the inspection result master 27. On the inspection and maintenance result sheet, the URL or the like of the website of the system may be described with a two-dimensional code such as a QR code.

  The SS terminal 30 transmits the vehicle number, inspection maintenance data, and access key to the server 20 (step S56). The server 20 registers the received maintenance data and access key in the database 21 in association with the vehicle number (step S35). At this time, of the inspection and maintenance data, data relating to inspection is registered in the inspection history table 24, and data relating to maintenance is registered in the maintenance history table 25. The access key is registered in the vehicle master 22.

  The user displays the member-only screen (FIG. 6) displayed in step S14 on the user terminal 40 (step S15). When the access key is entered in the access key input text box 53 and the main registration button 54 is clicked, the user terminal 40 transmits the entered access key to the server 20 (step S16). The server 20 collates the received access key with the access key registered in step S35 (step S36), and if they match, the access permission data corresponding to the vehicle number is registered in the vehicle master 22 (step S37). ). This access permission data is a flag for permitting browsing of inspection and maintenance data associated with the vehicle number. The server 20 transmits the HTML data of the member-only screen (FIG. 8) on which the registered vehicle number is described to the user terminal 40 (step S38). The user terminal 40 displays the member-only screen (step S17) and informs the user that the vehicle number 52 has been fully registered in the system. The server 20 transmits access permission data to the SS terminal 30 (step S39). The SS terminal 30 registers the received access permission data in the SS database (step S57).

When the user clicks the inspection history inquiry button 55 at the top of each member-dedicated screen, the inspection history inquiry screen shown in FIG. In this example, vehicle numbers 52a, 52b, and 52c of three vehicles registered in the user account are displayed.
When a detailed button 56 provided for each vehicle number is clicked on this screen, an inspection history list screen (FIG. 10) relating to that vehicle is displayed. On this screen, a list of work days 57 on which inspections have been performed, implementation stores 58, and results 59 of each inspection item are displayed. These are extracted from the inspection history table 24 of the database 21 of the server 20. The result 59 is preferably displayed as ◯, Δ, x for each inspection item. Thereby, a user can confirm the inspection result visually easily.
Further, when a detail display button 60 provided for each work day is clicked, an inspection detail screen shown in FIG. 11 is displayed. In this example, a detailed result 61 indicating the detailed contents is displayed together with the result 59 displayed also in FIG. Specifically, the state of tire grooves, cracks and pressure, the amount of battery fluid, the replacement time, the load voltage, the amount of engine oil fluid, the replacement time, and the like are displayed. These are extracted from the inspection history table 24 of the database 21 of the server 20. A comment 62 corresponding to the result 59 is also displayed. The comment 62 is extracted from the inspection result master 27.

  When the user clicks the maintenance history inquiry 63 button at the top of each member-dedicated screen, the maintenance history inquiry screen shown in FIG. Here, when the vehicle number to be browsed is selected from the pull-down list 64, the maintenance history (work date, execution location, implementation content, etc.) of the vehicle is displayed. In this example, a detail display button 65 is provided for the maintenance performed in the SS, and when the detail display button 65 is clicked, a maintenance result detail screen shown in FIG. 13 is displayed. Here, the detailed content 66 of the maintenance performed in SS is displayed.

When the user performs vehicle inspection and maintenance at a place other than the SS, the system can also register the inspection and maintenance data. FIG. 14 is a flowchart showing a procedure for inputting vehicle maintenance data by the user. When the user clicks the maintenance history inquiry button 63 at the top of each member-dedicated screen, the user terminal 40 displays the maintenance history inquiry screen shown in FIG. 12 (step S18). When the user maintenance input button 67 is clicked here, the user terminal 40 transmits a URL corresponding to the button to the server 20 (step S19). The server 20 transmits HTML data representing the user maintenance registration screen shown in FIG. 15 to the user terminal 40 (step S40). The user terminal 40 displays the screen, the vehicle number is selected from the pull-down list 64 by the user, data is input into the text box 68 regarding the total number of meters, the date of maintenance, the location of maintenance, and the content of maintenance, and the registration button If 69 is clicked, those data (maintenance data) are transmitted to the server 20 (step S20). The server 20 registers the received maintenance data in the maintenance history table 25 (step S41). The server 20 transmits the maintenance data to the SS terminal 30 (step S42). The SS terminal 30 registers the received maintenance data in the SS database (step S58).
Although the maintenance data registration procedure by the user has been described here, the inspection data registration procedure by the user can be performed in the same manner.

  When the user of this system purchases various products such as tires at the SS, the contents are input to the SS terminal 30 and registered in the sales history table of the SS database. Thereafter, the data is transmitted to the server 20 and registered in the sales history table 26 provided in the database 21 of the server 20. For registration in the SS terminal 30, it is preferable to read the product identification code of each product with a barcode reader or the like.

  This system can be used even if the user does not input personal information such as name and address. However, if the user agrees to provide personal information, the personal information can be registered in the member master 23 of the database 21. Good. At that time, the user clicks the customer information button 70 at the top of each member-dedicated screen displayed on the user terminal 40, displays an input screen, and inputs personal information. The user terminal 40 transmits the input personal information data to the server 20. The server 20 registers the data in the member master 23. If the personal information is registered in this way, the personal information is not exposed to the clerk of the SS, so that the user can register the personal information with peace of mind. If personal information is registered in this system so that the contact information of the user can be known, for example, the user is notified based on data stored in the inspection history table 24, the maintenance history table 25, the sales history table 26, and the like. It is possible to send by e-mail, mail or the like to urge the implementation of inspection and maintenance or to notify the product that is about to be replaced.

  When a user requests vehicle inspection and maintenance, or when a product is purchased, a point at which a predetermined service (for example, purchase or discount of a product, use of a paid service, etc.) can be received at the SS is determined for each vehicle number of the user or You may provide for every user account. The point is registered in the vehicle master 22, the sales history table 26, the member master 23, or the like. It is preferable that the balance of points can be viewed from the user terminal 40. If such a point system is introduced into this system, the user can expect to repeatedly visit the SS where the SS terminal 30 is installed, leading to the sale of fuel oil and other products.

  In the member master 23, if a plurality of vehicle numbers are associated with one account, for example, inspection and maintenance data relating to a plurality of vehicles owned by the user's family and a plurality of vehicles owned by the office are collectively managed with one account. This can improve user convenience.

  The above embodiment is an example of the present invention, and appropriate modifications are allowed within the scope of the present invention. For example, data transmitted from the server 20 to the user terminal 40 may be displayed by dedicated software instead of a Web browser. In the embodiment described above, the vehicle inspection / maintenance is performed after the user's vehicle number is provisionally registered, and then the vehicle number is permanently registered. However, the vehicle number may be registered after the vehicle inspection / maintenance. The database client program is installed on the server 20, the database server program is installed on a second server different from the server 20, and data stored in the second server is stored in the server 20 and the SS terminal 30. It may be synchronized with existing data. Data synchronization may be performed by periodically exchanging update data (difference data) between each server and the SS terminal.

1 is a schematic diagram of a network including a vehicle inspection and maintenance information management system that is an embodiment of the present invention. The block diagram of the database managed by the database server program of a server. The figure which shows an example of an inspection result master. The flowchart which shows the temporary registration procedure of a vehicle number. The figure which shows the vehicle number temporary registration screen. The figure which shows the member exclusive screen on which the vehicle number temporarily registered was described. The flowchart which shows the procedure of issuing of an access key and the main registration of a vehicle number. The figure which shows the member exclusive screen on which the vehicle number temporarily registered was described. The figure which shows an inspection log inquiry screen. The figure which shows an inspection log list screen. The figure which shows an inspection details screen. The figure which shows a maintenance log inquiry screen. The figure which shows a maintenance result detailed screen. The flowchart which shows the input procedure of the maintenance data of the vehicle by a user. The figure which shows a user maintenance registration screen.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Network 20 ... Server 21 ... Database 22 ... Vehicle master 23 ... Member master 24 ... Inspection history table 25 ... Maintenance history table 26 ... Sales history table 27 ... Inspection result master 28 ... Product master 30 ... SS terminal 30 ... User terminal 31 ... Input device 32 ... Printer 40 ... User terminal

Claims (6)

An SS terminal that is installed at a service station and into which a vehicle identification number and inspection data of a vehicle inspected and maintained by the service station are input;
Together are connected via the SS terminal and a network, which can log in with a unique account from a user terminal connected to said network, said vehicle identification number, the servicing data and said account associated with each other A server having a database to be stored
A vehicle inspection and maintenance information management system comprising:
The SS terminal is
An access key issuing means for issuing an access key corresponding to the vehicle identification number when the vehicle identification number is input to the SS terminal;
The server is
When a vehicle identification number is received from a user terminal logged in using the account, the account is associated with the vehicle identification number, stored in the database, and temporarily registered with the vehicle identification number corresponding to the account When,
Storage means for receiving the access key created at the SS terminal from the SS terminal, and storing the access key and the maintenance data in the database in association with the vehicle identification number;
The temporary registration receives the access key corresponding to said vehicle identification number from the user terminal to log in using the account corresponding to the vehicle identification number has been performed, the relative said servicing data associated with the vehicle identification number A registration means that allows access from the account;
Inspection and maintenance data transmitting means for transmitting the inspection and maintenance data associated with the account to the user terminal in response to an instruction from the user terminal logged in using the account corresponding to the vehicle identification number for which the main registration has been performed. When,
A vehicle inspection and maintenance information management system characterized by comprising:   The vehicle inspection and maintenance information management system according to claim 1, wherein the vehicle identification number is set as a main key in the database.   The vehicle inspection and maintenance information management system according to claim 1, wherein the vehicle identification numbers of a plurality of vehicles are associated with one account in the database. In the database, a fixed phrase corresponding to the result of at least one inspection item in the inspection and maintenance data is registered,
The server includes a fixed sentence transmission unit that transmits the fixed sentence together with the inspection maintenance data or instead of the inspection maintenance data to the user terminal in response to an instruction from the user terminal to which the account is input. The vehicle inspection and maintenance information management system according to any one of claims 1 to 3.   When the server receives inspection and maintenance data of a vehicle that has been inspected and maintained at a place other than the service station from the user terminal to which the account is input, the server includes inspection and maintenance data registration means for registering the inspection and maintenance data in the database. The vehicle inspection and maintenance information management system according to any one of claims 1 to 4.   2. The server according to claim 1, further comprising personal information registration means for registering in the database in association with the account when the server receives personal information of the user of the vehicle from the user terminal to which the account is input. The vehicle inspection and maintenance information management system according to any one of?

Images