JP2015103187A - Vehicle evaluation system and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a qualification document which serves as a standard for correctly evaluating a second-hand vehicle, as one of purposes.SOLUTION: The vehicle evaluation system comprises: a chronological data recording part for each vehicle, which records vehicle servicing data; a servicing data input part to which vehicle servicing data is inputted; a link part which links the vehicle servicing data and a bill issued to the servicing, and records the servicing data to the chronological data recording part for each vehicle; and an approval part which compares the servicing data associated with the bill with predetermined standard servicing data predetermined for each vehicle, for evaluating the vehicle.

Description

  The present invention relates to a system or a method for certifying the quality of a vehicle from the maintenance status of the vehicle.

  There is a certified used car system as a way of raising the value of used cars. This system certifies that used cars that meet certain conditions are used cars of good quality that meet the standards of their manufacturers and distributors. These certifications have a certain level of validity because they are judged by specialists based on the conditions set by them, and are useful for purchasers. Generally, such authorization is judged based on the current appearance, the state of a machine such as an engine that can be confirmed from the outside, or a maintenance record attached to each vehicle.

  However, these judgments examine the current status of each vehicle, in other words, are only based on the current status, and there is no guarantee regarding the status of ongoing maintenance or replacement of consumables. Despite the fact that the history over time is important for maintaining the quality of each vehicle, it is difficult to examine. Even if the vehicle has a maintenance record, it is not complete.

  Various methods have been proposed for providing appraisal price information for used cars. For example, Patent Document 1 describes a used car appraisal price information supply system that connects a computer storing used car appraisal price information and a user's terminal device to an Internet line and supplies used car appraisal price information to the user. However, it only follows the traditional assessment method in examining the price of individual used cars.

  The inventions described in Patent Document 2 and Patent Document 3 propose a remote used car assessment system using the Internet. However, there is no difference from the conventional judgment method except that it is performed remotely using the Internet, and even if it is certified using this method, the used car assessment itself is not different from the conventional method.

  Patent Document 4 proposes an invention in which vehicle data obtained from a sensor attached to a vehicle is collected, analyzed to generate assessment data as one of assessment basic data, and an assessment report is presented. .

JP 2001-357256 A JP 2004-152212 A JP 2004-206610 A JP 2006-107409 A

  Appropriate maintenance, for example, regular oil exchange, regular parts replacement, appropriate adjustment of the body and engine parts, removal of dirt on the engine parts, and the like is necessary to maintain the condition of the vehicle. These maintenance and parts replacement have a time and mileage recommended for each vehicle type, and it is an important matter in the maintenance of the vehicle that it is performed appropriately at those occasions.

  However, it is difficult to know how such maintenance was done when selling the vehicle as a used car. Generally, each vehicle comes with a maintenance notebook, but it is not always described properly. Furthermore, if the same vehicle is serviced at different maintenance sites, It is assumed that it is very difficult to assess the vehicle based on the maintenance history due to differences in the way of doing so.

  However, the vehicle data in the invention described in Patent Document 4 is obtained by converting driving evaluation and maintenance records obtained from sensors into data, and trying to reflect the time-dependent factors of individual vehicles in the used car price. It can be determined more accurately than simply based on the current situation. In this respect, it can be said that it is epoch-making, but the maintenance record itself is not automatically accumulated, and it is guaranteed that the information is accurate, such as being input arbitrarily or incorrectly. There is a concern that sufficient objective evaluation is not possible. As a result, the description of the present invention alone cannot sufficiently evaluate used cars, and cannot take advantage of the time-dependent evaluation.

  In view of such circumstances, an embodiment of the present invention has an object to provide a certificate that can be used as a basis for accurately assessing a used vehicle.

  According to one embodiment of the present invention, a vehicle-by-vehicle chronological data recording unit for recording vehicle maintenance data, a maintenance data input unit for inputting vehicle maintenance data, vehicle maintenance data, and maintenance A link unit that links an invoice to be issued and records maintenance data in a vehicle-specific time-dependent data recording unit, and maintenance data associated with the invoice is compared with standard maintenance data predetermined for each vehicle. There is provided a vehicle evaluation system having an authorization unit for performing the evaluation.

  The vehicle-specific temporal data recording unit may record vehicle maintenance data in time series. The authorization unit may read the maintenance data from the vehicle-specific maintenance data recording unit, read the standard maintenance data from the maintenance evaluation data recording unit, and evaluate the vehicle by comparing the maintenance data and the standard maintenance data. .

According to one embodiment of the present invention, the maintenance data recording the maintenance content of the vehicle is input,
A vehicle that evaluates a vehicle by associating the maintenance data of the vehicle with a bill issued for maintenance, recording the maintenance data, and comparing the maintenance data associated with the invoice with the standard maintenance data of the vehicle An evaluation method is provided.

  The maintenance data may be recorded by issuing a bill, and the maintenance data may be recorded in time series.

  According to the present invention, it is possible to leave an accurate vehicle maintenance history by linking the maintenance data recording and the issuance of a bill for maintenance and recording the linked maintenance data as a maintenance record in the database. By linking the issuance of invoices when recording vehicle maintenance data, there is an indirect relationship between the conflict between the interests of those who provide vehicle maintenance and those who receive vehicle maintenance. Therefore, the maintenance data and the record of the maintenance data can be improved. Thereby, it is possible to accurately evaluate the vehicle, and it is possible to provide authentication with high objectivity and high utility value.

It is a figure which shows the structure of the quality certification | authentication system of the vehicle which concerns on one Embodiment of this invention. It is a figure which shows an example of the maintenance data recorded on the maintenance data recording part classified by vehicle which concerns on one Embodiment of this invention. It is a figure which shows an example of the standard maintenance data recorded on the maintenance evaluation data recording part which concerns on one Embodiment of this invention. It is a figure explaining the maintenance of the vehicle which concerns on one Embodiment of this invention, and the relationship of a 1st server, a 2nd server, and a terminal. It is a figure which shows an example of the screen display and operation of the terminal which concern on one Embodiment of this invention. It is a flowchart explaining the evaluation method of the vehicle which concerns on one Embodiment of this invention. It is a figure explaining an example of the certificate of vehicles concerning one embodiment of the present invention. It is a flowchart explaining the method of recording the maintenance data which linked the maintenance record and issuance of the bill which concern on one Embodiment of this invention on a recording medium. It is a flowchart explaining an example of operation | movement of the vehicle confirmation part which concerns on one Embodiment of this invention. It is a figure which shows the quality certification | authentication system of the vehicle which concerns on one Embodiment of this invention, and demonstrates the aspect which a server manages centrally the content of the maintenance performed in the some maintenance shop. It is a figure explaining an example of the maintenance details of the vehicle concerning one embodiment of the present invention.

[First embodiment]
FIG. 1 shows the configuration of a vehicle quality certification system according to an embodiment of the present invention. This vehicle quality certification system includes a first server 102 including a vehicle-specific maintenance data recording unit 106, a maintenance evaluation data recording unit 108, a registered vehicle data recording unit 110, a determination unit 112, and a certificate issuing unit 114, and price calculation. Unit 114, service menu recording unit 116, bill issuing unit 118, vehicle confirmation unit 120, and second server 104 including a link unit 122.

  As a preferred aspect of the present embodiment, the first server 102 is installed at an administrator site or a vehicle information provider site, and the second server 104 is installed at a site of a business operator that provides vehicle maintenance. . The first server 102 is connected to the user terminal 128 through an electric communication line, and vehicle quality information or vehicle assessment information is provided from the first server 102 to a site where the user terminal 130 is located.

  Note that FIG. 1 shows a configuration in which the first server 102 and the second server 104 are separated, but one embodiment of the present invention is not limited to this, and has functions associated with these servers. In the configuration, whether the servers are integrated or separated is not interpreted in a limited way.

(First server)
In FIG. 1, the first server 102 has a vehicle-specific maintenance data recording unit 106 in which maintenance data for each vehicle is recorded. Maintenance data may include maintenance such as replacement of consumables such as engine oil and tires, and coating of coated surfaces that do not directly affect the running performance of the vehicle, in addition to legally performed maintenance. . The vehicle-specific maintenance data recording unit 106 links maintenance record data indicating the contents of maintenance and issuance of a bill for the maintenance, and records maintenance data that matches the link. The first server 102 is provided with maintenance data matching the link from the second server 104, and records the maintenance data in the vehicle-specific maintenance data recording unit 106 in time series for each vehicle.

  The first server 102 has a registered vehicle data recording unit 110. In the registered vehicle data recording unit 110, identification information of a vehicle that is a target of quality certification is registered. When there is an inquiry about a registered vehicle from the second server 104, the first server 102 provides the second server 104 with information on the registered vehicle recorded in the registered vehicle data recording unit 110. The vehicle data recorded in the registered vehicle data recording unit 110 is updated as needed.

  The first server 102 has a maintenance evaluation data recording unit 108. The maintenance evaluation data recording unit 108 records standard maintenance data in which recommended maintenance contents are described for the maintenance target items of the vehicle. The standard maintenance data records the recommended maintenance content for each vehicle type. The contents of maintenance include items related to maintaining the running performance of the vehicle such as the engine, suspension, steering, brake, and electric system. For example, data on consumables to be exchanged according to the travel distance, such as oil, filter elements, and belts, is included. The standard maintenance data is not permanent and may be updated as appropriate by the administrator. For example, when there is a recall, the standard maintenance data may be updated according to the content.

  The determination unit 112 compares the data recorded in the vehicle-specific maintenance data recording unit 106 with the data recorded in the maintenance evaluation data 108 to evaluate and determine the vehicle maintenance status. In the evaluation, each maintenance item recorded in the maintenance data is compared with the standard maintenance data for the maintenance item to check whether the maintenance is properly performed. Furthermore, comprehensive determination is performed from the result of the comparative evaluation of each item.

  The certificate issuing unit 114 issues a certificate for certifying the quality of the vehicle that is the object of evaluation based on the determination result of the determination unit 112. The certificate issued by the certificate issuing unit 114 is provided to the user terminal 130, for example.

(Second server)
The second server 104 shown in FIG. 1 includes a service menu recording unit 124 in which vehicle maintenance content and a price list corresponding thereto are recorded, and the service menu recording unit 124 based on the input maintenance content. Vehicle identification information acquired by the vehicle price acquisition unit 122, the vehicle information acquisition unit 126, and the vehicle confirmation unit 122 for identifying the maintenance vehicle, the vehicle identification information confirmed by the vehicle confirmation unit 122, and the vehicle identification information. A link unit 118 for associating maintenance contents, and a bill issuing unit 120 for issuing a bill based on the associated maintenance information.

  The second server 104 may be installed in a service station (including a gas station, a gas station, etc.) that can perform vehicle maintenance, or is constructed as a virtual server in the first server 102. May be. Further, when there are a plurality of service stations, the contents of the vehicle maintenance recorded in the service menu recording unit 124 and the price list corresponding thereto may be different for each service station.

  The contents of the service menu vary, and there are services that do not charge for costs such as tire pressure adjustment for vehicle maintenance. Even in such a case, it can be added to the present system by issuing a bill as billing 0 yen.

  The maintenance content input unit 128 receives the maintenance content of the vehicle. The maintenance content may be input from the terminal. The maintenance content may be input to the terminal by an operator or an assistant or administrator thereof. When a plurality of maintenances are performed on one vehicle, the maintenance details may be input at the same time.

  The price calculation unit 116 searches the service menu recording unit 124 for the price of the maintenance corresponding to the maintenance item input from the maintenance content input unit 128, and reads the corresponding price data. Then, the maintenance item and the maintenance price are associated with each other to generate data as an invoice or invoice.

  The vehicle confirmation unit 122 acquires vehicle identification information from the vehicle information acquisition unit 126 and confirms whether or not the vehicle is a vehicle registered in the database of the first server 102. The vehicle confirmation unit 122 sends a request for the vehicle identification information to the first server 102 and collates with the vehicle identification information registered in the registered vehicle data recording unit 110. Alternatively, the verification request is sent to the first server 102 and the verification result is received.

  The link unit 124 associates the maintenance data generated by the price calculation unit 116 with the vehicle identification information input from the vehicle confirmation unit 122. When the maintenance content (maintenance item), price, and vehicle identification information are confirmed, a bill is issued by the bill issuing unit 120. As a result, the maintenance data and the invoice are associated with each other. In this process, identification may be added by a credit card or a driver's license.

  When the invoice is issued, the maintenance data describing the contents of the maintenance is recorded in the time data recording unit 106 for each vehicle of the first server 102 together with the date and time when the maintenance was performed. In the vehicle time-dependent data recording unit 106, a record is created for each vehicle based on the vehicle identification information, and the maintenance content is recorded in the corresponding record. Thus, the maintenance data associated with the created invoice is communicated to the first server 102 and recorded in the vehicle-specific time data recording unit 106 when payment or a payment method is determined.

(Other configurations)
Maintenance vehicle identification information is input to the vehicle information acquisition unit 126. The vehicle identification information may be a unique number assigned to the vehicle such as a vehicle registration number or a chassis number, or may be a user number assigned to the user of the vehicle. The function of the vehicle acquisition unit 126 is realized by a terminal operated by an operator or an assistant or manager thereof.

  As another form, the vehicle information acquisition unit 126 may be provided with an imaging function, and a vehicle registration number (number plate) may be photographed to automatically acquire vehicle information by image recognition. Alternatively, an in-vehicle device may be installed in the vehicle, and the vehicle information acquisition unit 126 may perform wireless communication with the in-vehicle device using a communication function to acquire the vehicle identification information. In this case, the vehicle information acquisition unit 126 communicates with the vehicle-mounted device 132 mounted on the vehicle 132 when the vehicle 130 is parked in a predetermined area. For example, when the vehicle 132 is parked in the vehicle parking area of the maintenance shop, communication with the in-vehicle device 132 may be started in conjunction with turning off the ignition key.

(Maintenance data)
An example of the maintenance data recorded in the vehicle-specific maintenance data recording unit 106 is shown in FIG. The maintenance data includes information for identifying the vehicle type such as the vehicle name and model number, information for identifying the vehicle such as an identification code, and information indicating the content of the maintenance. The information indicating the maintenance content includes the date of maintenance, the distance traveled at that time, maintenance items, and maintenance details. Since maintenance on a vehicle is usually performed a plurality of times while the vehicle is in operation, these maintenance records are recorded in time series.

(Standard maintenance data)
An example of standard maintenance data recorded in the maintenance evaluation data recording unit 108 is shown in FIG. The standard maintenance data includes information for identifying the vehicle type such as the vehicle name and model number, and information related to the maintenance content. The maintenance contents include periodic inspection items for each part of the vehicle and periodic replacement items for replacement of consumables and the like.

  The periodic inspection items include a steering device, a braking device, a traveling device, a shock absorber, a power transmission device, an electric device, a prime mover, an exhaust gas device, and the like, and the content of these items may be further subdivided. . Periodic replacement items include items such as engine oil replacement, oil element replacement, brake oil replacement, battery check, tire replacement, and the like. For example, engine oil is changed at least once every six months, but no change has been made for more than 12 months. These maintenance items may be set as items common to all vehicles, or may be set for each vehicle type. The maintenance conditions allowed for each maintenance item and the limit maintenance conditions exceeding the allowable range are included.

(How to record maintenance details)
A method for linking maintenance data and issuance of a bill, recording the maintenance data on a recording medium and issuing a bill using the vehicle quality certification system shown in FIG. 1 will be described. FIG. 8 is a flowchart for explaining a method of linking maintenance data and issuance of a bill and recording the maintenance data in the vehicle-specific maintenance data recording unit.

  First, identification information of a vehicle to be maintained is acquired (S201). In obtaining the vehicle identification information, the operator or an assistant or manager of the vehicle inputs the vehicle registration number or the chassis number as the vehicle information acquisition unit 126 at the terminal and inputs the vehicle identification information to the vehicle confirmation unit 122. As another form, it carries out by reading vehicle identification information from the vehicle equipment installed in the vehicle.

  FIG. 9 is a flowchart for explaining an example of the operation of the vehicle confirmation unit 122. In FIG. 9, it is assumed that vehicle identification information is input from a terminal. First, vehicle identification information is input to the vehicle confirmation unit 122 (S201-1). When the vehicle identification information is input, the vehicle confirmation unit 122 requests the first server 102 to confirm whether the vehicle identification information is registered in the database (S201-2). When it is confirmed that the vehicle is registered in the database (S201-3), it is determined that the vehicle is registered and the process proceeds to the next process (S201-4). On the other hand, when the registration information of the vehicle is not recorded in the registered vehicle data recording unit 110 (S201-3), a message indicating no registration is transmitted to the terminal (S201-5). Then, whether or not re-input is necessary is displayed on the terminal (S201-5), and if re-input is selected, the process returns to the vehicle identification information input (S201-1). On the other hand, if re-input is not selected (S201-5), it is confirmed whether or not new registration is necessary (S201-7). And when new registration is selected, a new vehicle registration process is performed (S201-8), and it returns to vehicle identification information input (S201-1). If new registration is not selected, the process ends (S201-7).

  In FIG. 8, the acquired vehicle identification information is displayed on the terminal of the worker or its assistant or manager (S202). If it is confirmed that the vehicle identification information is correct, vehicle maintenance content is input (S203). The maintenance content may be input from the terminal of the operator or its assistant or administrator.

  Next, when the maintenance content is input, it is confirmed whether or not the input maintenance content is accurate (S204). This can be done by displaying the input contents on the display screen of the terminal of the worker or his / her assistant or manager.

  When the vehicle maintenance content is confirmed, the second server 104 reads price data for the corresponding maintenance from the service menu recording unit 118 (S205). The service menu recording unit 118 records a maintenance price table, and the maintenance item and the maintenance price are associated with each other by referring to this table.

  The billing data is created from the data in which the maintenance content and the maintenance price are associated with each other, and this is displayed on the display screen of the terminal of the operator or its assistant or manager (S206). This displays the maintenance content and the price of the maintenance together with the vehicle identification information, and designates the payment method (S207). The payment method may be selected, for example, by displaying a selection button on the screen display of the terminal and inputting from the terminal.

  When the payment method is designated, an invoice is issued (S208). At this time, the link unit 124 in the second server 104 associates the maintenance data with the vehicle identification information, and gives a command to issue a bill to the bill issuing unit 120. Thereby, the bill is issued on the display screen of the terminal or the like as printed on a paper medium or as electronic data.

  The maintenance data for which the invoice has been issued is transmitted to the first server 102 and recorded in the vehicle-specific time data recording unit 106 (S209). As shown in FIG. 8, the vehicle-specific temporal data recording unit 106 creates a record for each vehicle identification information, and records maintenance contents in the corresponding record.

  Thereby, maintenance data distinguished for each vehicle is recorded in the database. In this case, since the bill is required to be very accurate, it can be said that the maintenance data in which the bill is linked to the bill guarantees a certain level of accuracy.

(Example of processing)
The procedure of the process shown in FIG. 8 will be described by taking as an example maintenance work for exchanging engine oil of a vehicle at a certain car maintenance shop. In this example, as shown in FIG. 4, a plurality of maintenance target vehicles are registered in a computer 105 in an automobile maintenance shop, and the computer 105 communicates with a maintenance worker or its assistant or manager's terminal 127. It shall be established. The computer 105 is assumed to be connected to the second server 104. The first server 102 and the second server 104 are the same as those shown in FIG.

  The identification information of the plurality of vehicles in the car maintenance shop is input to the computer 105 in the maintenance shop. The computer 105 transmits the identification information of the vehicle that is the maintenance target to the second server 102. The second server 104 checks the first server 102 as to whether or not the input vehicle identification information has been registered (S201). Then, the second server 104 returns information about the registered vehicle to the computer 105, and the computer 105 shows the screen of the operator or its assistant or manager's terminal 127 as shown in FIG. Thus, the vehicle identification information is displayed on the maintenance worker's terminal (S202). The maintenance worker can select a vehicle to be maintained from the display screen.

  After the work on the vehicle is completed, the maintenance details of the engine oil change are input from the terminal 127 at the maintenance shop. In this process, in the screen display as shown in FIG. 5B, “engine oil change” is selected as the maintenance target item from the screen and the maintenance content is input (S203). After this input, a screen display for confirming the input content may be displayed on the screen of the terminal 127 (S204). When multiple items are maintained, a plurality of items can be selected.

  Even if maintenance is performed for a plurality of vehicles, as shown in FIG. 5A, the corresponding vehicle may be selected from the selection screen of the terminal, and maintenance content may be input. FIG. 5A shows a screen display of the terminal device, and a plurality of vehicles currently being maintained are displayed together with vehicle identification information. The vehicle identification information may be only the identification number assigned to each vehicle, or may be used in combination with the identification number and the vehicle registration number (description of the number plate). In addition, since the customer's name and the like are confirmed when maintaining the vehicle, the customer name may be displayed at the same time. By displaying the vehicle identification information and the customer name at the same time, vehicle selection mistakes can be further reduced.

  The vehicle identification information and the maintenance content input from the terminal 127 are transmitted to the second server 104 via the computer 105. The second server 104 reads the input engine oil replacement price from the service menu recording unit 124 (S206), and transmits the data to the computer 105. As shown in FIG. 5C, the billing amount is displayed on the screen of the terminal 127 together with the maintenance details. Then, when a payment method is designated from the screen of the terminal 127 (S207), the second server 104 links the maintenance data (engine oil replacement) with the bill, and a bill for the maintenance is issued. (S208). Thereafter, the second server 104 transmits the maintenance content to the vehicle-specific time-lapse data recording unit 106 in the first server 102 (S209).

  Although technically, it can be said that the link between the maintenance contents and the invoice has been completed, it is possible to add identity verification such as a credit card to this process. Alternatively, the vehicle identification information may be obtained from the first server after verifying the identity with a credit card or the like. Thereby, maintenance data for each vehicle is recorded in the database. In this case, the bill is confirmed by the maintenance requester, so the accuracy is improved.

  5A to 5C exemplify a case where an operator or its assistant or administrator performs an operation from a tablet terminal, but the same operation is performed on a POS (Point Of Sales system) screen. Alternatively, it may be performed by a computer that has downloaded a specific application program.

(Method of vehicle evaluation)
In order to be a good used car, (1) there is no problem in the current situation, and (2) it has not been handled by having been properly maintained. The above (1) can be determined by confirming the current vehicle, and (2) can be determined by referring to the data recorded in the first server 102 to meet a predetermined standard. it can.

  In this embodiment, vehicle quality is evaluated using vehicle maintenance data collected over time. With respect to this evaluation method, the vehicle evaluation method in this embodiment will be described with reference to the flowchart shown in FIG.

  First, the maintenance data of the vehicle to be evaluated is read out from the time data recording unit by vehicle 106 of the first server 102 (S301). Further, standard maintenance data of the vehicle to be evaluated is read from the maintenance evaluation data recording unit 108 (S302). Then, the maintenance data is evaluated based on the standard maintenance data (S303). The contents of the operation data and the standard operation data are as described with reference to FIGS. 4 and 5, and the maintenance data and the standard maintenance data are collated to determine whether the maintenance is properly performed.

  For example, if the standard maintenance data is defined as “changing engine oil more than once every six months on average, but not changing more than 12 months”, the actual oil change The evaluation is made based on the maintenance data. If the oil change is done once every six months, a pass is determined. Conversely, if the oil change has not been done for more than one year, a failure is determined.

  An authorization judgment is made from the result of the vehicle maintenance evaluation (S304). In the certification judgment, each evaluation item can be scored and the total score can be used for evaluation. In this case, all the evaluation items are not judged equally, and weighting may be applied to those that are likely to affect the deterioration of the vehicle. In addition, the certification judgment does not have to be evaluated for the entire period during which the vehicle is operating, but may be displayed as a percentage of the total period based on the travel distance. .

  After the certification judgment is made, a certification is issued (S305). An example of the certificate is shown in FIG. The format of the certificate is arbitrary, but overall evaluation and evaluation may be described for individual items.

  By recording and accumulating vehicle maintenance data over time in this way, based on preset evaluation criteria, vehicle evaluation at that point can be performed based on objective criteria and can be known.

  According to an embodiment of the present invention, the maintenance data record and the issuance of a bill for maintenance are linked, and the linked maintenance data is recorded in the database as a maintenance record, thereby leaving an accurate vehicle maintenance history. Can do. In this case, the reliability of the maintenance data is effectively determined because both the person who provides the vehicle maintenance and the person who receives the vehicle maintenance conflict conflict with each other. Will further increase. As a result, the vehicle can be evaluated accurately, and authentication with high objectivity and high utility value can be obtained.

[Second Embodiment]
In addition to legal inspection and maintenance, vehicle users may voluntarily perform vehicle maintenance. There are multiple locations for vehicle maintenance, including car dealerships, service stations with a maintenance station at a gas station (gas station), auto repair and maintenance factories that specialize in car maintenance and inspection, and stores that sell car supplies. There are various business formats such as a car supply store that provides a comprehensive service with a maintenance facility. The user of the vehicle usually performs maintenance of the vehicle by freely selecting from these.

  When vehicle maintenance is performed at a plurality of locations, conventionally, maintenance records are dispersed, and it is extremely difficult to grasp the maintenance history. However, according to the present invention, maintenance data is linked to the issuance of an invoice and can be managed centrally by the server, so that an accurate maintenance history can be grasped.

  FIG. 10 illustrates a configuration in which maintenance data is managed by the first server 102 when there are a plurality of maintenance shops. In FIG. 10, a mode in which the second servers 104a, 104b, and 104c in the first maintenance site 134a, the second maintenance site 134b, and the third maintenance site 134c are installed with respect to the first server 102, respectively. Show. Second servers 104a, 104b, and 104c are connected to the first server 102 by electric communication lines such as the Internet.

  The first server 102 and the second servers 104a, 104b, and 104c have functions similar to those described in FIG.

  The first maintenance place 134a, the second maintenance place 134b, and the third maintenance place 134c indicate different maintenance places, and car dealerships, service stations, automobile repair and maintenance shops, automobile supply shops, and the like correspond to these. .

  The user of the vehicle will receive the maintenance of the vehicle by arbitrarily selecting from these maintenance places. In this case, as described with reference to FIG. 8, at each maintenance site, the maintenance record is transmitted to the first server 102 via the second server 104 and the maintenance content is recorded in the vehicle-specific maintenance data recording unit 106. . At this time, the maintenance data created at each maintenance site is linked to the issuance of the invoice and recorded in the first server 102, so that a record omission can be prevented. In other words, according to the present invention, even if one vehicle is maintained at a different maintenance site, the maintenance record can be recorded and managed without leaking. Then, a certification for vehicle maintenance that can be referred to as a basis for vehicle assessment using the maintenance data can be issued.

  Although FIG. 10 shows a mode in which maintenance data is centrally managed by the first server 102, the present invention is not limited to this, and the second servers 104a, 104b, 104c, the vehicle-specific maintenance data recording unit 106, and the like. The first server 102 may read out the maintenance data of the vehicle to be evaluated with the corresponding function from the second servers 104a, 104b, and 104c and perform the accreditation evaluation. According to such a configuration, the load on the first server 102 can be reduced.

[Third embodiment]
According to the present invention, a maintenance record with high reliability can be proved by linking the maintenance of the vehicle and the charge for the cost. At this time, not only the maintenance items of the vehicle are recorded as maintenance data on the server but also the maintenance details are recorded, so that higher reliability can be ensured.

  FIG. 11 shows an example of the maintenance details. There are no limitations on the form of maintenance details, but in addition to the data related to maintenance details such as work contents and unit price, quantity and labor, such as the invoice number and issue date, information specifying the details, customer number and Information that identifies users such as customer names, information that identifies vehicles such as vehicle names and model numbers, maintenance classifications, information that identifies maintenance personnel such as maintenance personnel, and information that identifies issuers of details Good.

  Information regarding these maintenance details is recorded in the vehicle-specific maintenance data recording unit 106 of the first server 102 together with the maintenance data. Alternatively, the second server 104 may store the data by linking with the maintenance data recorded in the vehicle-specific maintenance data recording unit 106.

  In this way, the maintenance details of the vehicle can be evaluated more precisely by associating the maintenance data with the maintenance data.

[Other embodiments]
Although one embodiment of the present invention has been described above by the embodiments, the present invention is not limited to the illustrated example, and may be applied to a system including a plurality of devices or may be realized by a single device. Also good. Furthermore, the present invention may be provided by a program recorded on a computer-readable recording medium that implements the functions described in the embodiments or a program provided through an electric communication line.

102 1st server, 104 2nd server, 106 maintenance data recording unit for each vehicle, 108 maintenance evaluation data recording unit, 110 registered vehicle data recording unit, 112 certification unit, 114 certificate issuing unit, 116 price calculation unit, 118 Service menu recording unit, 120 bill issuing unit, 122 vehicle confirmation unit, 124 link unit

Claims (6)

A vehicle-specific time-dependent data recording unit for recording vehicle maintenance data;
A maintenance data input unit for inputting maintenance data of the vehicle;
A link unit that links the maintenance data of the vehicle and a bill issued for the maintenance, and records the maintenance data in the vehicle-specific time data recording unit;
A vehicle evaluation system comprising: a certification unit that evaluates the vehicle by comparing maintenance data associated with the bill with standard maintenance data predetermined for each vehicle.   The vehicle evaluation system according to claim 1, wherein the vehicle-specific temporal data recording unit records the maintenance data of the vehicle in time series.   The authorization unit reads the maintenance data from the vehicle-specific maintenance data recording unit, reads the standard maintenance data from the maintenance evaluation data recording unit, and compares the maintenance data with the standard maintenance data to evaluate the vehicle. The vehicle evaluation system according to claim 1, wherein the vehicle evaluation system is performed. Enter maintenance data that records the maintenance details of the vehicle,
Associating the maintenance data of the vehicle with a bill issued for the maintenance, recording the maintenance data;
A vehicle evaluation method, wherein the vehicle is evaluated by comparing the maintenance data associated with the bill with standard maintenance data of the vehicle.   5. The vehicle evaluation method according to claim 4, wherein the maintenance data is recorded when the bill is issued.   5. The vehicle evaluation method according to claim 4, wherein the maintenance data is recorded in time series.

Images