KR102629504B1 - System for vehicle maintenance service intermediation - Google Patents

Abstract

The present invention relates to a vehicle maintenance service brokerage system, which includes an information management unit that receives and stores user information, vehicle information including mileage and maintenance history, and company information including company name, company address, and company contact information, and vehicle information. Based on this, a timing management unit calculates the maintenance required period for the preset maintenance item and receives input of whether or not the maintenance item is requested from the user terminal; receives at least one maintenance request date for the maintenance item from the user terminal; and receives the maintenance request date for the maintenance item from the user terminal. A maintenance request section that receives input from the company terminal about whether to accept maintenance, possible dates and expected prices included in the maintenance request date, and a company that is selected from the user terminal among the company terminals that enter the corresponding input values regarding whether or not to accept maintenance. A service brokerage unit that transmits user information corresponding to the user terminal to the terminal; maintenance status, maintenance date, replacement status, replacement date, product name, product code, manufacturer name, for at least one maintenance item input from the company terminal; The maintenance history management department generates maintenance details based on maintenance details including parts prices and labor costs, and based on the maintenance details, determines the timeliness of whether the maintenance included in the maintenance details is appropriate and the price adequacy of whether the price is appropriate. It is characterized by including a maintenance history evaluation unit that evaluates.

Description

Vehicle maintenance service brokerage system {SYSTEM FOR VEHICLE MAINTENANCE SERVICE INTERMEDIATION}

The present invention relates to a vehicle maintenance service brokerage system.

It is very important to regularly inspect and maintain the vehicle in order to use it safely and for a long time.

However, people in modern society often postpone or forget to do this due to their busy schedules, and often do inspection and maintenance only when a problem occurs with the vehicle without inspecting and maintaining the vehicle.

In addition, even if they go for vehicle inspection and maintenance, people who are not interested in cars usually wonder whether the vehicle maintenance or replacement of consumables was done in a timely manner, whether unnecessary maintenance was done, and whether the maintenance was done at a reasonable price. Because it was difficult to understand, there was a problem with how to check the reliability of maintenance performed by a maintenance company.

Meanwhile, recently, as many people use smartphones, various applications have been developed, and among them, an application that brokers vehicle maintenance service providers to users has also been developed and is being used by many users.

However, the vehicle maintenance service brokerage application according to the prior art only performs the function of intermediating between the user and the maintenance company, and does not provide information on maintenance details, such as whether the maintenance company performed unnecessary maintenance on the vehicle and whether the maintenance was performed at a reasonable price. There was a problem that made it difficult to provide reliability to users.

Republic of Korea Patent Publication No. 10-1747367, registered on June 8, 2017

The purpose of the present invention is to solve the above-mentioned problems. When a user receives a vehicle maintenance service, the maintenance period for the vehicle's maintenance items can be calculated and the maintenance details are provided so that the user can determine whether the service was performed and the price is appropriate. The purpose is to provide a vehicle maintenance service brokerage system that provides users to users by calculating the timeliness and price adequacy of whether the timing and price are appropriate.

The object of the present invention is not limited to the object mentioned above, and other objects not mentioned can be clearly understood from the description below.

In order to achieve the above-mentioned purpose, the vehicle maintenance service brokerage system according to one aspect of the present invention receives user information, vehicle information including mileage and maintenance history, and company information including company name, company address, and company contact information. An information management unit that stores, calculates the maintenance need period for preset maintenance items based on vehicle information, and receives an input of maintenance request for the maintenance item from the user terminal, and at least one maintenance item for the maintenance item from the user terminal. A maintenance request department that receives the request date, whether or not maintenance is accepted for the maintenance item, and the possible date and estimated price included in the maintenance request date are entered from the company terminal. The company enters the corresponding input values regarding whether or not the maintenance is accepted. Among the terminals, a service brokerage unit that transmits user information corresponding to the user terminal to the company terminal selected from the user terminal; maintenance status, maintenance date, replacement status, replacement date, and product name for at least one maintenance item input from the company terminal. , a maintenance history management department that generates maintenance details based on maintenance details including product code, manufacturer name, parts price and labor cost, and timeliness of whether the maintenance included in the maintenance details was performed based on the maintenance details. It includes a maintenance history evaluation department that evaluates the price adequacy of whether the price is appropriate.

The vehicle maintenance service brokerage system according to the embodiment of the present invention with the above configuration can expect the following effects.

By calculating the time when maintenance is required for a given maintenance item of the vehicle and providing the calculated time when maintenance is required for the vehicle, it is possible to encourage the user to receive maintenance for the given maintenance item of the vehicle in a timely manner.

A maintenance report is created based on the maintenance details entered from the company, and based on the generated maintenance details, the timeliness and price adequacy of the maintenance period included in the maintenance details and whether the maintenance price is appropriate are calculated and provided to the user. This can help users determine whether the timing and price of maintenance included in the maintenance details are reasonable.

Figure 1 is a block diagram showing the overall configuration of a vehicle maintenance service brokerage system according to an embodiment of the present invention.
Figure 2 is a diagram for explaining the first interface created in the first interface management unit of the vehicle maintenance service brokerage system according to an embodiment of the present invention.
Figure 3 is a diagram for explaining a second interface created in the maintenance request unit of the vehicle maintenance service brokerage system according to an embodiment of the present invention.
Figure 4 is a diagram for explaining a third interface created in the service brokerage unit of the vehicle maintenance service brokerage system according to an embodiment of the present invention.
Figure 5 is a diagram for explaining a maintenance history input form stored in the maintenance history management unit of the vehicle maintenance service brokerage system according to an embodiment of the present invention.
Figure 6 is a diagram for explaining the adequacy range generated in the timeliness evaluation unit of the vehicle maintenance service brokerage system according to an embodiment of the present invention.
Figure 7 is a diagram for explaining the price range generated in the price adequacy determination unit of the vehicle maintenance service brokerage system according to an embodiment of the present invention.
Figure 8 is a diagram for explaining a conversion table generated in the second price adequacy evaluation unit of the vehicle maintenance service brokerage system according to an embodiment of the present invention.

The advantages and features of the present invention and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and will be implemented in various different forms, but the present embodiments only serve to ensure that the disclosure of the present invention is complete, and those skilled in the art It is provided to fully inform the user of the scope of the invention. Meanwhile, the terms used in this specification are for describing embodiments and are not intended to limit the present invention. As used herein, singular forms also include plural forms, unless specifically stated otherwise in the context.

Hereinafter, a vehicle maintenance service brokerage system according to an embodiment of the present invention will be described with reference to the drawings.

Throughout this specification, a user may refer to a person who wishes to receive vehicle maintenance services, and a company may refer to a maintenance company that seeks to provide vehicle maintenance services.

The vehicle maintenance service brokerage system according to an embodiment of the present invention includes a user terminal 11, a company terminal 12, an administrator terminal 13, and an integrated server 14.

The user terminal 11 may be a terminal used by a user, and may be at least one of a PC, a smartphone, and a tablet, but is not limited as long as it can be connected to the integrated server 14 through a communication network.

Here, the user may be a user who wishes to receive vehicle maintenance services.

The company terminal 12 may be a terminal used by a vehicle maintenance company and may be at least one of a PC, smartphone, and tablet, but is not limited as long as it can be connected to the integrated server 14 through a communication network.

The administrator terminal 13 may be a terminal used by the administrator who manages the integrated server 14, and may be at least one of a PC, smartphone, and tablet, but is not limited as long as it can be connected to the integrated server 14 through a communication network. No.

The integrated server 14 includes an information management department 100, a time management department 200, a maintenance request department 300, a service brokerage department 400, a maintenance history management department 500, and a maintenance history evaluation department 600. You can.

The information management unit 100 may receive and store at least one of user information, vehicle information, and company information from at least one of the user terminal 11, the company terminal 12, and the manager terminal 13.

Here, the user information may include a user name, user contact information, and user location, and the business information may include a business name, business address, and business contact information.

Additionally, vehicle information may include, but is not limited to, the vehicle's model name, year, vehicle location, mileage, and maintenance history.

The mileage included in the vehicle information stored in the information management unit 100 may be the cumulative mileage value of the vehicle at a certain point in time.

The information management unit 100 may receive and store the accumulated driving distance value corresponding to at least one point in time as the driving distance.

The maintenance history included in the vehicle information stored in the information management unit 100 may mean the past maintenance history of the vehicle, and if at least one of maintenance and replacement has been performed for the vehicle's preset maintenance items, at least one of maintenance and replacement has been performed. It may include the date on which it was made.

The maintenance history included in the vehicle information stored in the information management unit 100 may include at least one of a maintenance date on which maintenance was performed on the vehicle and a replacement date on which consumable parts of the vehicle were replaced.

The maintenance history included in the vehicle information stored in the information management unit 100 may include a maintenance history generated by the maintenance history management unit 500, which will be described later.

The timing management unit 200 calculates the maintenance required period for the preset maintenance items based on the vehicle information stored in the information management unit 100, and determines whether or not a maintenance request is made for the maintenance item corresponding to the calculated maintenance required period through the user terminal ( It may be receiving input from 11).

When the time difference between the current time and the calculated maintenance-need time becomes less than a preset time value, the time management unit 200 provides a space for receiving input values for maintenance request and maintenance request date, and includes maintenance-required items and maintenance-need period. The first interface (A) may be transmitted to the user terminal (11).

Here, the maintenance need period may mean the time when maintenance is required for preset maintenance items, or it may mean the time when replacement of certain vehicle consumable items is required, and the maintenance need item corresponds to the calculated maintenance need time. It may mean a maintenance item that is required.

The time management unit 200 may calculate the time when maintenance is required based on at least one of the mileage and maintenance history included in the vehicle information stored in the information management unit 100.

When transmitting the first interface (A) to the user terminal 11, the time management unit 200 may also transmit a notification requesting to enter input values for whether maintenance is requested and the maintenance request date.

The period management unit 200 may include a time period calculation unit 210, a distance period calculation unit 220, a maintenance need period determination unit 230, and a first interface management unit 240.

The time period calculation unit 210 may calculate the first maintenance period based on the maintenance history stored in the information management unit 100 and a preset time period.

The time period calculation unit 210 may calculate the first maintenance period based on at least one of the maintenance date and replacement date included in the maintenance history stored in the information management unit 100 and a preset time period.

Here, when the maintenance history stored in the information management unit 100 includes the maintenance history generated by the maintenance history management unit 500, the maintenance date and replacement date may correspond to those included in the maintenance history.

When there are a plurality of preset maintenance items, the time period calculation unit 210 may receive input from the manager terminal 14 and store the time period for each of the plurality of maintenance items, and may be used for each maintenance and replacement of the preset maintenance items. The time period may be input from the manager terminal 14 and stored.

Here, the time cycle may mean at least one of a maintenance cycle and a replacement cycle for one maintenance item, and the maintenance cycle and replacement cycle may correspond to the maintenance date and replacement date, respectively.

The time period calculation unit 210 may calculate the date calculated by adding the preset time period to at least one of the maintenance date and the replacement date stored in the information management unit 100 as the first maintenance period.

The time period calculation unit 210 may calculate the date calculated by adding the preset time period to one selected from the maintenance date and replacement date stored in the information management unit 100 as the first maintenance period.

At this time, when adding the time period to the maintenance date to calculate the first maintenance period, the time period may mean the maintenance cycle, and when adding the time period to the replacement date, the time period may mean the replacement cycle. there is.

When both the maintenance date and replacement date stored in the information management unit 100 are stored, the time period calculation unit 210 calculates the date by adding the preset time period to the relatively recent date of the maintenance date and replacement date. It may be calculated as the first maintenance period.

The distance cycle calculation unit 220 may calculate the second maintenance period based on at least one of the mileage and maintenance history stored in the information management unit 100 and a preset distance cycle.

The distance cycle calculation unit 220 may calculate the second maintenance period based on the mileage and maintenance history stored in the information management unit 100 and a preset distance cycle.

When the cumulative driving distance values for a plurality of points in time are stored as driving distances in the information management unit 100, the distance cycle calculation unit 220 generates a driving distance trend line based on the stored cumulative driving distance values, and the generated driving distance trend line Based on this, the expected driving distance for any point in time can be calculated.

The distance cycle calculation unit 220 may receive a preset distance cycle for calculating the second maintenance period from the manager terminal 13 and store it.

Here, the distance cycle may mean the unit driving distance when a preset maintenance item must be maintained or replaced at a predetermined unit driving distance. In this case, the unit driving distance may be a commonly known value, but is not limited thereto. no.

When there are a plurality of preset maintenance items, the distance cycle calculation unit 220 may receive input from the manager terminal 13 and store the distance cycle corresponding to each maintenance item.

For example, when the maintenance item is engine oil, it is known that the engine oil must be replaced every 10,000 km, and in this case, the distance cycle corresponding to the engine oil may be 10,000 km.

The distance cycle calculation unit 220 calculates a date corresponding to the distance value calculated when adding the preset distance cycle to the mileage stored in the information management unit 100 based on the generated mileage trend line, and the calculated date. It may be calculated as the second maintenance period.

At this time, when the preset distance cycle is added to the mileage stored in the information management unit 100, the mileage stored in the information management unit 100 corresponds to the most recent one among the mileage stored in the information management unit 100. It is desirable to add the driving distance to a preset distance period.

Meanwhile, generating a trend line based on data values for a plurality of time points and calculating a predicted value for a certain time point based on the generated trend line are technical matters widely known to those skilled in the art, so detailed description will be omitted.

The maintenance-need-time determination unit 230 selects the first maintenance period calculated by the time period calculation unit 210 and the second maintenance period calculated by the distance period calculation unit 220, which is relatively closer to the current time. It may be calculated based on judgment.

Accordingly, the vehicle maintenance service brokerage system according to an embodiment of the present invention can calculate the optimized maintenance period for each user by considering the replacement cycle according to the typical time and the replacement cycle according to the mileage that may be different for each driver. You can.

When the time difference between the current time and the maintenance-need time calculated by the maintenance-need time calculation unit 230 is less than a preset time value, the first interface management unit 240 selects the maintenance-need item and the maintenance-need-time calculation unit 230. A first interface (A) that includes the time when maintenance is required and can receive input values for maintenance request status and maintenance request date may be created and transmitted to the user terminal 11.

Here, the maintenance-required item may be at least one of maintenance and replacement for the maintenance item corresponding to the maintenance-need period calculated by the maintenance-need period calculation unit 230.

The first interface management unit 240 includes a calculation unit ( The first interface (A) may be created by arranging the maintenance need period calculated in 230).

Referring to Figure 2, the maintenance-required item is 'brake oil', and the maintenance-required period is '2021.' In the case of '11. 20.', the first interface management unit 240 places 'brake oil' in the space for placing maintenance-required items, and places '2021.11.20.' in the space for arranging maintenance-required times. The first interface (A) can be created.

The first interface management unit 240 transmits the generated first interface (A) to the user terminal 11 when the time difference between the current time and the maintenance need time calculated by the maintenance need time calculation unit is less than a preset time value. You can.

When transmitting the first interface (A) to the user terminal 11, the first interface management unit 240 may also transmit a notification requesting that input values for maintenance request and maintenance request date be entered.

When input values for the maintenance request and maintenance request date of the first interface (A) are input from the user terminal 11, the first interface management unit 240 provides input values for the maintenance request and maintenance request date. 1 It can be saved by including it in interface (A).

The maintenance request unit 300 receives at least one maintenance request date for the maintenance item from the user terminal 11, and reports whether or not the maintenance is accepted for the maintenance item, the possible date included in the maintenance request date, and the expected price to the company terminal ( It may be receiving input from 12).

When an input value corresponding to the maintenance request is entered from the user terminal 11, the maintenance request unit 300 includes the maintenance required items and the maintenance request date, and includes the maintenance acceptance status, estimated price, and maintenance request date. A second interface (B) may be created to receive input values for possible dates and transmitted to the business terminal.

At this time, the maintenance-required items and maintenance request dates included in the second interface (B) may correspond to those included in the first interface (A).

When the maintenance request unit 300 receives an input value corresponding to yes regarding whether to request maintenance through the first interface A from the user terminal 11 that has received the first interface A from the timing management unit 200, The second interface (B) may be created and transmitted to the company terminal (12).

The maintenance request unit 300 uses the first interface (A) on the second form, which includes a space for placing maintenance required items and maintenance request dates, and a space for receiving input values for available dates, expected prices, and whether or not to accept maintenance. The second interface (B) may be created by arranging the maintenance-required items and maintenance request date included in .

At this time, the maintenance request date may correspond to what is input through the first interface (A) from the user terminal 11, and the input value of the maintenance request date may have the form of a single date or a date range.

Referring to Figure 3, the maintenance-required item is 'brake oil', and the maintenance request date is '2021.' In the case of '11. 20. ~ 2021.11.24.', the maintenance request unit 300 places 'brake oil' in the space for placing maintenance required items, and places '2021.11.20 ~' in the space for placing maintenance request dates. The second interface (B) can be created by placing '2021.11.24.'.

The maintenance request unit 300 may transmit the generated second interface (B) to the company terminal 12.

At this time, the maintenance request unit 300 sends the second interface (B) to the business terminal 12 of the business corresponding to the business address located within a preset distance from at least one of the user location and the vehicle location stored in the information management unit 100. It may be transmitting.

When the maintenance request unit 300 transmits the second interface (B) to the company terminal 12, it may also transmit a notification requesting that an input value for maintenance acceptance be entered.

The maintenance request unit 300 instructs the company to enter input values for the possible date and expected price when the company terminal 12, which has received the second interface (B), inputs an input value corresponding to yes as to whether or not maintenance is accepted. A request can be made to the terminal 12.

When the expected price and possible date are input from the business terminal 12 through the second interface (B), the maintenance request unit 300 can include and store the input values in the second interface (B).

The service brokerage unit 400 connects the user corresponding to the user terminal 11 to the company terminal 12 selected from the user terminal 11 among the company terminals 12 that have entered an input value corresponding to whether or not to accept maintenance. It may be transmitting information.

The service brokerage unit 400 includes the company information, expected price, and possible date of the company terminal 12 that entered the input value corresponding to the acceptance of maintenance, and a third interface (C) for receiving the final acceptance. ) is provided to the user terminal 11, and when an input value corresponding to the final acceptance is input from the user terminal 11, the user information corresponding to the user terminal 11 is transmitted to the business terminal 12. It could be.

Here, the expected price and possible date may correspond to what is input into the second interface (B) from the company terminal 12, and final acceptance is determined by the company terminal entering the input value corresponding to whether or not maintenance is accepted. This may mean whether or not to receive maintenance from the company corresponding to (12).

The service brokerage unit 400 inputs the corresponding answer regarding whether or not maintenance is accepted in the third form, which includes a space for placing company information, expected price, and possible date, and a space for receiving input values for final acceptance. The third interface (C) may be created by arranging the company information, expected price, and available date of the company terminal 12 where the values have been entered.

Here, the company information placed in the third form may include the company name, company address, and company contact information.

Referring to Figure 4, the company name, company address, and company contact information are 'Best Engineering', '123-45, Maba-dong, Dara-gu, Kanashi', and '012-345-6789', respectively, and the available date and expected price are 'November 2021.' In the case of '23.' and '30000', the service brokerage department (400) places 'Best Engineering' and '123- Maba-dong, Dara-gu, Kanashi- The third interface (C) can be created by placing '45', '012-345-6789', '2021.11.23.', and '30000'.

If there are a plurality of company terminals 12 that have entered input values corresponding to whether or not to accept maintenance, the service brokerage unit 400 provides company information, expected price, and available date corresponding to each of the plurality of company terminals 12. The third interface (C) may be created by placing each in the third form.

When an input value corresponding to Yes is input as to whether or not to accept the final result from the user terminal 11, the service brokerage unit 400 sends the user information corresponding to the user terminal 11 that entered the input value to the final acceptance. The input value corresponding to whether or not to accept may be transmitted to the input company terminal 12.

The maintenance history management unit 500 receives maintenance details from the company terminal 12 and generates a maintenance detail based on the input maintenance details.

The maintenance history management unit 500 includes maintenance status, maintenance date, replacement status, replacement date, product name, product code, manufacturer name, parts price, and labor cost for at least one maintenance item input from the business terminal 12. A maintenance statement may be generated based on the maintenance history.

The maintenance history management unit 500 transmits a preset maintenance history input form (D) to the company terminal 12 to receive input values for the maintenance details, and inputs the maintenance details input values to the maintenance details input form (D). When this is entered, a maintenance statement may be created.

The maintenance details management unit 500 may receive input from the manager terminal 13 and store the maintenance details input form (D) for receiving input values for the maintenance details.

The maintenance history input form (D) stored in the maintenance history management unit 500 may be a table for entering maintenance details, and for at least one maintenance item, maintenance status, maintenance date, replacement status, replacement date, It may include a table for inputting part names, parts prices, and labor costs, and may be input and stored from an administrator terminal.

Here, maintenance items are not limited as long as they are items that are generally checked during vehicle inspection, for example, engine oil, transmission oil, power oil, brake oil, antifreeze, tires, wipers, brake pads, battery, air conditioner filter, timing belt, and May include a diagnostic device.

In the maintenance history input form (D), maintenance may mean whether maintenance has been performed on the maintenance item.

In the maintenance history input form (D), replacement may mean whether the maintenance item has been replaced.

In the maintenance history input form (D), the part name may be identification information to identify the product used to perform at least one of maintenance or replacement when at least one of maintenance or replacement has been performed for the maintenance item, for example, It may include the product name, product code, and manufacturer.

It may be the price of the product corresponding to the product identification information entered in the part name in the maintenance history input form (D).

In the maintenance history input form (D), the labor cost may be the labor cost for at least one of the maintenance and replacement of the maintenance item.

The maintenance history management unit 500 sends a notification requesting that the maintenance date be entered into the business terminal 12 when an input value corresponding to whether or not the maintenance history input form (D) is maintained is entered from the business terminal 12. can do.

When an input value corresponding to whether or not to replace the maintenance history input form (D) is entered from the company terminal 12, the maintenance history management unit 500 sends a notification requesting that the replacement date be entered in the company terminal 12. can do.

The maintenance history generated by the maintenance history management unit 500 may include maintenance status, maintenance date, replacement status, replacement date, part name, part price, and labor cost for at least one maintenance item.

When the maintenance history management unit 500 generates a maintenance history based on the input values entered into the maintenance history input form (D), the generated maintenance history is based on the maintenance history input form (D) and the maintenance history input form (D). May contain input values.

The maintenance history management unit 500 requests the service brokerage unit 400 to input whether maintenance has been completed in the company terminal 12 that provided the user information about the user terminal 11, and the company terminal 12 If the corresponding input value is entered, the maintenance details input form may be transmitted to the company terminal 12.

When the company terminal 12 inputs the maintenance history input form (D), the maintenance history management unit 500 can generate a maintenance history based on the input value.

The maintenance history management unit 500 may provide the generated maintenance history to at least one of the user terminal 11, the company terminal 12, and the manager terminal 13.

The maintenance details generated by the maintenance details management unit 500 may include a maintenance details input form (D) and input values entered into the maintenance details input form (D) from the company terminal 12.

Meanwhile, the information management unit 100 may store the maintenance details generated by the maintenance details management unit 500 as the vehicle's maintenance history.

That is, the maintenance history stored in the information management unit 100 may include the maintenance history generated in the maintenance history management unit 500.

The maintenance history evaluation unit 600 may evaluate the timeliness and price adequacy of the maintenance details based on the maintenance details generated by the maintenance details management unit 500.

The maintenance history evaluation unit 600 may calculate the timeliness of whether the maintenance included in the maintenance details was appropriate and the price adequacy of whether the price is appropriate based on the maintenance details generated by the maintenance history management unit 500. there is.

The maintenance history evaluation unit 600 may calculate the timeliness of the maintenance details based on the maintenance need period calculated by the timing management unit 200.

Here, timeliness may refer to whether the timing of maintenance is appropriate, for example, whether the timing of maintenance is early, appropriate, or slow.

More specifically, timeliness may refer to whether the timing of at least one of maintenance and replacement is appropriate when at least one of maintenance and replacement has been performed for at least one maintenance item included in the maintenance statement.

In addition, affordability may refer to whether the price of the maintenance performed is appropriate, for example, whether the price of the maintenance performed is cheap, appropriate, or expensive.

More specifically, price adequacy is determined when at least one of maintenance and replacement of at least one maintenance item included in the maintenance statement has been performed, and at least one of labor cost and parts price for at least one of the maintenance and replacement has been entered. It may be about whether labor costs and parts prices are appropriate.

The price adequacy calculated by the maintenance history evaluation unit 600 refers to the first price adequacy, which is for the parts price included in the maintenance details generated by the maintenance details management unit 500, and the maintenance details generated by the maintenance details management unit 500. It may include a second price adequacy regarding the included labor cost.

The maintenance history evaluation unit 600 may provide the calculated timeliness and price adequacy to at least one of the user terminal 11, the company terminal 12, and the manager terminal 13.

The maintenance history evaluation unit 600 may include a timeliness evaluation unit 610, a first price adequacy evaluation unit 620, and a second price adequacy evaluation unit 630.

The timeliness evaluation unit 610 may calculate the timeliness of the maintenance details of the maintenance details generated by the maintenance details generation unit 500 based on the maintenance need period calculated by the time management unit 200.

The timeliness evaluation unit 610 determines whether the input value for at least one of inspection and replacement included in the maintenance statement is multiple, and the time when at least one of inspection and replacement of the maintenance item for which the input value was entered is multiple. It may be to calculate the timeliness of whether it is appropriate or not.

When at least one of the inspection date and replacement date included in the maintenance statement is input, the timeliness evaluation unit 610 may calculate the timeliness of whether the timing of at least one of the input inspection date and replacement date is appropriate.

The timeliness evaluation unit 610 calculates at least one date threshold value based on the maintenance need period calculated by the time management unit 200, and determines an adequacy range including at least one section range based on the calculated date threshold value. , and at least one of the maintenance date and replacement date included in the maintenance history generated by the maintenance history management unit 500 may calculate the section name of the section range within the adequacy range with timeliness.

The timeliness evaluation unit 610 calculates at least one date threshold value by adding or subtracting a preset date value from the maintenance need period calculated by the timing management unit 200, and arranges the calculated date threshold values in date order. This may create an appropriateness range that includes at least one section.

At this time, each section may be matched with a corresponding section name, and the timeliness evaluation unit 610 may receive the section name from the manager terminal 13 and match it to each section.

The timeliness evaluation unit 610 may calculate the timeliness of a section in the created adequacy range in which at least one of inspection and replacement is performed.

The timeliness evaluation unit 610 may calculate the section name of the section in which at least one of inspection and replacement was performed in the created adequacy range as timeliness.

The timeliness evaluation unit 610 may calculate the timeliness of a section in which at least one of the maintenance date and replacement date of the maintenance details generated by the maintenance details management unit 500 falls within the appropriateness range.

The timeliness evaluation unit 610 may calculate the section name of the section in which at least one of the maintenance date and replacement date of the maintenance details generated by the maintenance details management unit 500 falls within the appropriateness range as timeliness.

For example, if the maintenance required period calculated by the time management unit 200 is 2021. 11. 20, and the preset date value is 5 days, the timeliness evaluation unit 610 calculates the maintenance required period 2021. 11. 20. 2021. 11. 25., which is calculated by adding 5 days, which is the preset date value, to 2021. 11. 25., and 2021. 11., which is calculated by subtracting 5 days, which is the preset date value, from 2021. 11. 20., which is the time when maintenance is required. 15. can be calculated as a date threshold and arranged in date order to create an adequacy range that includes at least one section.

At this time, the section name for the section corresponding to before November 15, 2021 is entered as 'fast', and the section name for the section corresponding to between November 15, 2021 and November 25, 2021 is entered as 'adequate'. If the section name for the corresponding section is entered as 'slow' after November 25, 2021, an appropriateness range as shown in Figure 6 can be created, and the replacement date included in the maintenance statement is November 23, 2021. In this case, the timeliness evaluation unit 610 can calculate 'appropriate' as timeliness.

The first price adequacy evaluation unit 620 may calculate the first price adequacy, which is the price adequacy for the parts prices included in the maintenance statement generated by the maintenance statement generation unit 500.

The first price adequacy evaluation unit 620 may calculate an appropriate price based on the maintenance details, and calculate the first price adequacy for the parts prices included in the maintenance details based on the calculated appropriate prices.

The first price adequacy evaluation unit 620 may generate a search keyword based on the maintenance details to calculate the appropriate price, and calculate the first price adequacy based on the generated search keyword.

The first price adequacy evaluation unit 620 searches for products in the external DB 20 using search keywords generated based on the product name, product code, and manufacturer name, and calculates the appropriate price based on the price of the searched product. Price adequacy may be calculated by comparing the price with the parts price included in the maintenance history generated by the maintenance history management unit 500.

The first price adequacy evaluation unit 620 may include a keyword generation unit 621, an appropriate price calculation unit 622, and a first price adequacy determination unit 623.

The keyword generator 621 may create a search keyword based on at least one of the product name, product code, and manufacturer included in the maintenance statement to calculate an appropriate price.

The keyword generator 621 may generate search keywords by extracting fragment strings from strings constituting the product name, product code, and manufacturer included in the maintenance statement, and arranging the extracted fragment strings.

At this time, the fragment string may be composed of at least two consecutive characters.

The fragment string extracted from the keyword generator 621 may be created as a group consisting of at least two consecutive characters.

For example, if the product name included in the maintenance statement is 'Brake Oil DOT4+', the product code is 'P93725', and the manufacturer is 'Sabori', the keyword generator 621 extracts search keywords from the product name. In this case, the search keywords extracted are 'Bre', 'Ray', 'Ike', 'Koh', 'Oil', 'IlD', 'DO', 'OT', 'T4', '4+', 'Bray' ', 'Lake', 'Ike O', 'K Oil', 'Oil D', 'Il DO', 'DOT', 'OT4', 'T4+', 'Break', 'Lake O', 'Ike Oil ', 'K Oil D', 'Oil DO', 'IlDOT', 'DOT4', 'OT4+', 'Break O', 'Lake Oil', 'Ike Oil D', 'K Oil DO', 'Oil DOT', 'IL DOT4', 'DOT4+', 'Brake Oil', 'Lake Oil D', 'Ike Oil DO', 'KR Oil DOT', 'Oil DOT4', 'IL DOT4+', 'Brake Oil D' , 'Lake Oil DO', 'Ike Oil DOT', 'K Oil DOT4', 'Oil DOT4+', 'Brake Oil DO', 'Lake Oil DOT', 'Ike Oil DOT4', 'K Oil DOT4+', 'Brake It can be created as a group consisting of 'Oil DOT', 'Lake Oil DOT4', 'Ike Oil DOT4+', 'Brake Oil DOT4', 'Lake Oil DOT4+', and 'Brake Oil DOT4+'.

In addition, when the keyword generator 621 extracts search keywords from the product code, the extracted search keywords are 'P9', '93', '37', '72', '25', 'P93', '937, It can be created as a group consisting of '372', '725', 'P937', '9372,' 3725', 'P9372', '93725, and 'P93725', and can be extracted when searching keywords from the manufacturer. Search keywords can be created as a group consisting of 'Sebo', 'Bore', and 'Sebore'.

When the keyword generator 621 arranges the fragment strings extracted from each of the product name, product code, and manufacturer to generate a search keyword, the order in which they are arranged is not limited, but the fragment strings are arranged in the order of manufacturer, product name, and product code. You can create search keywords by arranging them.

For example, the keyword generator 621 arranges 'Savore' extracted from the manufacturer, 'Brake oil' extracted from the product name, and 'P93725' extracted from the product code, and searches for 'Savoir brake oil P93725' as a search keyword. It may be created with .

When extracting a search keyword, the keyword generator 621 may extract a search keyword from the string with the space removed if a space exists in the string constituting the product name, product code, and manufacturer included in the maintenance statement.

The appropriate price calculation unit 622 may perform a search in an external DB using the search keyword generated in the keyword generation unit 621, and calculate an appropriate price for the parts price included in the maintenance statement based on the search results. there is.

Here, the external DB 20 may be a database in which the product name and product price of the product are searched as search results when a predetermined keyword is searched.

When a search is performed on an external DB using the search keyword generated by the keyword generation unit 621, the appropriate price calculation unit 622 calculates the product price of the product as an appropriate price when there is only one product included in the search results. It could be.

When a search is performed on an external DB using the search keyword generated by the keyword generation unit 621, the appropriate price calculation unit 622 calculates the similarity between the product name of the product and the search keyword when there are multiple products included in the search results. It may be calculated and the product price of the product corresponding to the product name with the highest degree of similarity is calculated as an appropriate price.

At this time, the similarity between the product name and the search keyword can usually be calculated by calculating the similarity between two different words, but preferably, the string forming the search keyword and the string forming the product name are compared and the degree of similarity is calculated. The similarity may be calculated based on

More preferably, when the string forming the product name is matched to the string forming the search keyword, the similarity of the product corresponding to the product name is determined to be at least one of 'mismatch', 'partial match', 'included', and 'complete match' depending on the degree of correspondence. It may be calculated as a setting value corresponding to one.

The appropriate price calculation unit 622 may calculate the similarity as 'mismatch' when the string forming the product name does not match the string forming the search keyword.

The appropriate price calculation unit 622 may calculate the similarity as 'partial match' when a part of the string forming the product name matches a part of the string forming the search keyword.

The appropriate price calculation unit 622 may calculate the similarity as 'included' when the entire string forming the product name matches part of the search keyword.

The appropriate price calculation unit 622 may calculate the similarity as 'exact match' when the entire string forming the product name and the entire string forming the search keyword completely match.

The appropriate price calculation unit 622 may calculate the similarity as 'exact match' when the entire string forming the search keyword matches a part of the string forming the product name.

The appropriate price calculation unit 622 can determine that the similarity is relatively high in the order of 'complete match', 'included', 'partial match', and 'mismatch'.

When the similarity of products corresponding to different product names is the same, the appropriate price calculation unit 622 calculates the similarity of products with a relatively large number of characters included in the search keyword used during the search at a relatively high similarity. You can.

For example, if the search keyword is 'Sabory Brake Oil P937543' and the product name of the product being searched is 'Sabory Brake Oil P93754', the string that makes up the product name is included in the search keyword, so the similarity of the product can be calculated as 'included'. And, if the search keyword is 'Sabory Brake Oil P9375431B' and the product name of the product being searched is 'Sabory Brake Oil P9375431', the similarity of the product can be calculated as 'Included'.

At this time, when the search keyword is 'Sabory Brake Oil P9375431B', the number of characters included in the search keyword is relatively greater than when the search keyword is 'Sabory Brake Oil P937543', so the product name is 'Sabory Brake Oil P937543'. The similarity in the case of 'P9375431' can be calculated to be relatively higher than the similarity in the case where the product name is 'Sabory Brake Oil P93754'.

When there are a plurality of different products with the same degree of similarity, the appropriate price calculation unit 622 calculates the price range by multiplying the median of the prices corresponding to the products by a preset ratio, and calculates the price of the product included in the calculated price range. The price value calculated by averaging may be calculated as an appropriate price.

The price adequacy determination unit 623 may calculate the first price adequacy for the parts price included in the maintenance statement based on the appropriate price calculated by the appropriate price calculation unit 622.

The price adequacy determination unit 623 calculates a threshold value by multiplying the appropriate price calculated by the appropriate price calculation unit 622 by at least one preset ratio, and arranges the calculated threshold values in order of relative decreasing order to determine at least one This may be to create a price range that includes the range.

At this time, each section included when creating the price section range can be matched with a preset section name, and the price adequacy determination unit 623 determines the section for each section included in the price section range from the manager terminal 13. You can input a name and match it to each section.

The price adequacy determination unit 623 may calculate the section name of the price range range to which the parts price included in the maintenance statement belongs as the first price adequacy.

For example, if the appropriate price calculated by the appropriate price calculation unit 622 is 30000 and the preset ratios are 0.8, 0.9, 1.1, and 1.2, the price adequacy determination unit 623 determines the appropriate price of 30000 and a plurality of preset ratios. 24000, 27000, 33000, and 36000, which are calculated by multiplying each, are calculated as threshold values, and the calculated threshold values are listed in relatively small order of 24000, 27000, 33000, 36000 to create a price range that includes at least one section. can be created.

At this time, the section corresponding to less than 24000 is called 'very cheap', the section name of the section corresponding to 24000 to less than 27000 is 'ssam', the section name corresponding to 27000 to less than 33000 is 'adequate', and the section name of the section corresponding to 27000 to less than 33000 is 'adequate', and the section name of the section corresponding to 24000 to less than 33000 is 'reasonable'. When the section name of the section corresponding to less than 36000 is input as 'expensive' and the section name of the section corresponding to 36000 or more is input as 'very expensive', a price range range can be created as shown in FIG. 7.

The price adequacy determination unit 623 may provide the calculated first price adequacy to the user terminal 11 along with the maintenance details.

The second price adequacy evaluation unit 630 may calculate a second price adequacy, which is the price adequacy for the input labor cost, when at least one labor cost is entered in the maintenance statement generated by the maintenance statement generation unit 500.

The second price adequacy evaluation unit 630 may store the appropriate labor cost for each preset maintenance item included in the maintenance details input form (D) transmitted by the maintenance detail generation unit 500 to the company terminal 12. , the second price adequacy may be calculated based on the appropriate cost, which is the ratio of the labor cost to the stored appropriate labor cost.

The second price adequacy evaluation unit 630 may store an appropriate labor cost for each maintenance item in the maintenance statement generated by the maintenance statement generation unit 500, and may store the appropriate labor cost based on the appropriate cost, which is the ratio of the labor cost to the stored appropriate labor cost. It may be calculating the second price adequacy.

The second price adequacy evaluation unit 630 may store a conversion table in which the section range for at least one appropriate cost matches the second price adequacy, and the section in which the appropriate cost, which is the ratio of the labor cost to the appropriate labor cost, belongs in the conversion table. may be calculated as the second price adequacy.

For example, as shown in FIG. 8, if the conversion table is stored in the second price adequacy evaluation unit 630, the labor cost for the preset maintenance item is 12,500 won, and the appropriate labor cost is 10,000 won, the second price adequacy evaluation unit (630) may calculate 'expensiveness' corresponding to 1.1 or more and less than 1.3, where the appropriate cost of 1.25 falls, as the second price adequacy.

Those skilled in the art to which the present invention pertains will understand that the present invention can be implemented in other specific forms without changing its technical idea or essential features. Therefore, the embodiments described above should be understood in all respects as illustrative and not restrictive. The scope of the present invention is indicated by the scope of the claims described below rather than the detailed description above, and all changes or modified forms derived from the scope of the claims and their equivalent concepts should be construed as being included in the scope of the present invention.

20: External DB,
11: User terminal, 12: Company terminal, 13: Administrator terminal, 14: Integrated server,
100: Information Management Department,
200: Timing Management Department,
210: time period calculation unit, 220: distance period calculation unit,
230: Maintenance need period judgment unit, 240: First interface management unit,
300: Maintenance request department,
400: Service Brokerage Department,
500: Maintenance history management department,
600: Maintenance history evaluation department,
610: Timeliness judgment unit,
620: First Price Adequacy Evaluation Department,
621: Keyword generation unit, 622: Appropriate price calculation unit, 623: First price adequacy judgment unit,
630: Second price adequacy evaluation department.

Claims (5)

An information management unit that receives and stores user information, vehicle information including mileage and maintenance history, and company information including company name, company address, and company contact information;
A timing management unit that calculates a maintenance need period for preset maintenance items based on the vehicle information and receives an input of whether or not a maintenance request is required for the maintenance items from the user terminal;
A maintenance request unit that receives at least one maintenance request date for the maintenance item from the user terminal, and receives input from the company terminal whether maintenance is accepted for the maintenance item, a possible date included in the maintenance request date, and an expected price;
A service intermediary unit that transmits the user information corresponding to the user terminal to the company terminal selected from the user terminal among the company terminals that have entered an input value corresponding to whether or not to accept the maintenance;
A maintenance statement is created based on the maintenance details including maintenance status, maintenance date, replacement status, replacement date, product name, product code, manufacturer name, parts price, and labor cost for at least one maintenance item input from the business terminal. Maintenance history management department that generates; and
It includes a maintenance history evaluation unit that evaluates the timeliness of whether the maintenance included in the maintenance details was appropriate based on the maintenance details and the price adequacy of whether the price is appropriate,
The maintenance history evaluation department
Extracting fragment strings consisting of at least two consecutive characters from the strings constituting the product name, product code, and manufacturer name, and sequentially arranging the fragment strings extracted from each of the manufacturer, product name, and product code. A keyword generator that generates search keywords;
A product search is performed in an external DB using the search keyword, and the appropriate price for the part price is calculated based on the price of the searched product. However, if there are multiple searched products, the string forming the product name of the product is the search keyword. The similarity of each of the plurality of products is calculated based on the degree of matching with the string forming the product, the price of the product with the highest similarity is calculated as the appropriate price, and a plurality of different products with the same degree of similarity are calculated. If it exists, the price range is calculated by multiplying the median price corresponding to the product by a preset ratio, and the price value calculated by averaging the prices of the products included in the calculated price range is calculated as the appropriate price. wealth; and
Calculating a threshold value by multiplying the appropriate price by at least one preset ratio, arranging the calculated threshold values in relatively decreasing order to generate a price range range including at least one range, and the generated price range Containing a price adequacy determination unit that determines the price adequacy of the part price based on the range
In-vehicle maintenance service brokerage system. According to clause 1,
The maintenance history evaluation department
Calculating at least one date threshold based on the maintenance need period, generating an adequacy range including at least one section range based on the date threshold, and at least one of the maintenance date and the replacement date is the adequacy value. A timeliness evaluation unit that determines the timeliness of the section name of the section range belonging to the range; comprising a.
In-vehicle maintenance service brokerage system. delete delete delete

Images