JP2006079640A - Insurance premium calculation system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To facilitate a system for providing an additional service for action such as purchase of a relevant apparatus of an automobile, in relation to a technique for calculating a fee of an insurance including an automobile insurance. <P>SOLUTION: A checking system 30 inputs apparatus information related to an apparatus (part) attached to an automobile from a dealer server 40, and calculates an insurance fee according to points related to each apparatus, and an insurance company server 20 creates an insurance contract plan according to the calculated insurance fee and annunciates it to a customer. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a technique for calculating a fee for insurance including automobile insurance using a computer system using a network.

  Conventionally, when calculating insurance premiums, the insurance premiums are calculated based on information related to the risk of insurance payment. Among them, there is a conventional technique used for the operation state of a car in order to calculate a premium for car insurance. Patent Document 1 discloses a technology that uses operation status data including the number of days of operation and the distance traveled as an insurance premium calculation standard. This prior art discloses an automobile management / insurance system that collects data related to actual vehicle information including the “mileage” of an automobile and calculates an insurance premium based on the collected data.

JP 2002-24553 A

However, in this prior art, it is necessary to always grasp the state of the automobile (every predetermined period) by the actual vehicle management means. In other words, this conventional technique can be applied as long as it can manage the running (operating) status like a rental car. Therefore, it is difficult to apply this conventional technique to an unmanaged automobile used by a general driver. In this case, it is difficult to grasp the driving situation of the car,
This makes it difficult to calculate insurance premiums.

In order to solve the above problems, the present invention has the following configuration.
In the present invention, device information relating to devices (parts) to be mounted on a car is input, and insurance premiums are calculated based on this information. Note that the present invention includes calculating the insurance premium based on other information such as information indicating the driving situation including the mileage of the automobile and the grade. Note that the devices to be mounted include devices to be mounted at the time of purchase including options in addition to devices to be mounted after purchasing the automobile. In the present invention,
Including notifying the customer of the next insurance plan based on the calculated premium.

  ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to provide easily the system for providing the additional service with respect to acts, such as the purchase of the related apparatus of a motor vehicle.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a system configuration diagram showing a system configuration of the present embodiment. In the present invention, computer devices are connected to each other via a network 60 including the Internet. This computer device includes an insurance policyholder terminal 10 used by an insurance policyholder, an insurance company server 20 managed by an insurance company, a collation system 30 for calculating insurance premiums, a dealer server 40 for managing equipment sales data, and equipment. A manufacturer server 50 managed by the production company is included. Here, there may be two or more of each computer device. Further, the dealer server 40 is installed for each of one or more dealers. Further, the present embodiment includes one or more dealer terminals 45 connected to the dealer server 40. The dealer terminal 45 is capable of inputting information related to sales including sales data, and includes a dealer terminal 45 such as a cash register or a POS terminal.

  The computer apparatus executes information processing according to a program. For this purpose, each computer device has a storage device for storing a program and data, a memory for expanding the program stored in the storage device, and a processing device (processor) for executing information processing according to the program. Note that the storage device may be a storage device connected to the computer device.

  Next, the flow of the first process in the present embodiment will be described using the flowchart shown in FIG. The flow of the first process shows the process of the preparation stage for realizing the point service.

  In step 101, the collation system 30 registers the contractor information 2 shown in FIG. 11 transmitted from each insurance company server 20 in step 100 in the contractor DB 21 shown in FIG. The verification system 30 is an insurance NO. The contractor information 2 indicating the contents of the insurance is registered. The contractor information 2 includes insurance NO. This includes the contractor for identifying the policyholder of the insurance including the name, the vehicle type for identifying the insured vehicle type, the license plate number of the insured vehicle, and the e-mail address of the contractor. The e-mail address may be a transmission destination in the case where PR data is transmitted to the contractor in step 114 described later.

  In step 103, the dealer server 40 registers the product data 3 shown in FIG. 4 including the product ID for identifying the product in the product DB shown in FIG. The product information 3 includes information presented / transmitted from the manufacturer server 50 in step 102. Further, the product information 3 includes information input to the store server 30 by a store related person or the like.

  Next, in step 104, the store server 40 executes additional service registration application processing for the insurance company server 20. In the present embodiment, the dealer server 40 transmits application information 5 including the product information 4 to the insurance company server 20. The product data 4 is based on the product DB 41.

  Here, the merchandise information 4 includes a merchandise ID, a merchandise name, a merchandise classification indicating the classification of the merchandise, a specification indicating the specifications of the merchandise such as a compatible vehicle type, a selling price, and points given by the merchandise. Here, the points are issued for sales of products. Further, the store server 40 may transmit individual application information 5 corresponding to each of the plurality of insurance company servers 20. That is, application information including product information 4 at different points may be transmitted even for the same product. Furthermore, the points include individual points according to the vehicle type or insurance contents (especially grades and premiums).

  Next, in step 106, the insurance company server 20 executes a process for determining whether or not registration is possible for the application information 5 received in step 105. The collation system 30 performs determination processing according to the relationship between the points and the predetermined information. Whether the collation system 30 has a predetermined relationship between the predetermined information shown in the correspondence table and the first correspondence between the permitted points and the second correspondence between the predetermined information and the points input in step 105. Depending on whether or not, the determination process is executed. The first correspondence relationship is not particularly illustrated.

  For example, when the second correspondence relationship satisfies the first correspondence relationship, a determination to permit registration is performed. In the correspondence table, product characteristic information including product price and identification information is stored as a predetermined relationship. In this case, allowable points are stored as an example of the first correspondence relationship according to the value indicated by the feature information. For example, the first correspondence relationship is such that the point value increases as the price of the product increases.

  The present embodiment also includes that the user of the insurance company server 20 executes the final determination in step 106. In this case, the insurance company server 20 may output the correspondence table and the application information 5. The user includes a person who uses the insurance company server 20 via a terminal device that can use the insurance company server 20.

  Next, when the determination in step 106 is negative, the insurance company server 20 presents the fact to the dealer server 40 in step 107. In step 111, the store server 40 receives this and outputs it or stores it in a predetermined storage area.

  If the determination at step 106 is affirmative, the routine proceeds to step 108. In step 108, the determination result including the application information 5 is transmitted to the verification system 30. The application information 5 includes information indicating the same content in addition to the information transmitted in step 104.

  Next, in step 109, the collation system 30 registers the application content indicated in the transmitted application information 5 in the additional service target master DB 33 shown in FIG. That is, the product information 4 including the product ID and the points to be given are stored in association with each other. In this case, in addition to these, information for specifying a store may be associated.

  Next, in step 110, the verification system 30 notifies the store server 30 of a registration notification. The registration notification includes information indicating registration, merchandise information 4 that is registered contents, and points. Information for specifying a store may be included in the registration notification. The notified registration notification is accepted by the store server 20 in step 112. The dealer server 40 outputs at least one of the contents of the received registration notification or registration.

  In addition, a store includes a plurality of stores such as a chain store in addition to a single store. When there are a plurality of dealers, information for identifying dealers may be included. In addition, the registration notification may be broadcast to a dealer server managed by each of a plurality of dealers.

  Next, the process after step 113 which is an additional process in this Embodiment is demonstrated. In step 113, the collation system 30 confirms the registered content. That is, it is determined whether an advertisement is necessary for the registered content. This is determined based on the advertisement information included in the registered content. The advertisement information is included in the application information 5 and indicates the necessity of advertisement. Further, when the advertisement information indicates that the advertisement is necessary, information on the advertisement destination (partner) is also included. That is, in step 104, the store server 40 transmits the application information 5 including the advertisement information. The dealer server 40 receives information indicating whether or not the advertisement is necessary (or at least one of necessity), and creates and transmits the application information 5 according to the received content.

  If an advertisement is required, an email address of the advertisement destination is added. This e-mail address may be extracted from customer information that the store server 40 has, or may be manually input. Furthermore, when extracting from customer information, the mail address of the customer corresponding to the information in which the product information 4 included in the application information 5 indicates a purchase tendency is extracted. Note that this embodiment includes using information for executing an electronic or non-electronic advertisement for a customer (advertisement destination) in addition to a mail address. The e-mail address indicates the address of the policyholder terminal 10 of the present embodiment, and the policyholder terminal 10 includes an information processing device including a personal computer and a mobile phone.

  If it is determined in step 113 that an advertisement is necessary, in step 114, the verification system 30 distributes the advertisement information to the e-mail address. The distributed advertisement information includes the product information 4 included in the application information 5.

  This is the end of the description of the first processing flow. Next, the flow of the second process in the present embodiment will be described with reference to FIG. The second processing shows processing of services such as point grant and insurance premium discount.

  First, in step 117, the collation system 30 presents the merchandise information 4 including points according to the contents registered in step 109 to the store server 40.

  In step 118, the merchandise information 40 presented by the store server 40 is output. Further, the product information 4 may be output to a store terminal 45 including a POS terminal connected to the store server 40, an advertising board, or the like. Note that steps 117 and 118 are optional in the present embodiment and need not be executed. Note that the insurance contractor terminal 10 may output the advertisement information as in step 118 '.

  The product information to be output may be as follows. You may output the merchandise information of the goods corresponding to the vehicle type shown by contractor DB21 or collation DB31. When transmitting to the policyholder terminal 10, the vehicle type is specified using the collation DB 31 with the mail address as the transmission destination as a key. In step 114 described above, advertisement information may be distributed in the same manner. Moreover, when transmitting to the store server 40, the information which specifies insurance, such as insurance NO, is received from a purchaser etc., and a vehicle type is specified using this and collation DB31.

  In step 119, the store server 40 accepts the purchase request of the point grant target product including the product information 4 and information for identifying the purchaser. Here, the store server 40 may determine whether or not the product of the input product information 4 is a point grant target. In step 112, it is determined whether or not the product of the received product information 4 is a target according to the registered content. The policyholder terminal 10 may accept a purchase request from the consumer (the policyholder) in step 119 '. In this case, in step 131, the policyholder terminal 10 notifies the store server 40 of information indicating the purchase request.

  Further, the purchase request input includes (1) input from the policyholder terminal 10, (2) input from the user to the store server 40, and (3) a POS terminal connected to the store server 40, a register The input from the store terminal 45 is included.

  Next, in step 120, the store server 40 transmits the purchase information 1 shown in FIG. The purchase information 1 includes product information 4, information for specifying a purchaser, and information for specifying a store (or store server 30). The information specifying the purchaser includes insurance No. specifying the purchaser's car insurance. Is used. The information specifying the purchaser may specify either the purchaser himself or the purchaser's car insurance.

  Next, in step 121, the collation system 30 registers the purchase information 1 in the collation DB 31 shown in FIG. In this case, registration is performed in association with the contractor information registered in step 101.

  Next, in step 122, the verification system 30 determines whether the insurance NO. Accumulated points are calculated every time. This is the verification DB 31 and insurance NO. A sort process is executed using the as a key to create the additional service target product DB 32 shown in FIG. In this calculation process, the insurance NO. Everything to do is included. For example, the calculation includes a certain time before the expiration date of the insurance. In this case, the accumulated points can be used for discounting the next insurance contract to be updated. Further, the calculation process includes calculating when there is a request from the insurance company server 20.

  In step 123, the collation system 30 calculates the calculated insurance NO. Each accumulated point is transmitted to the insurance company server 20. The insurance company server 20 as a transmission destination is an insurance company server corresponding to the insurance company included in the verification DB 31. That is, the insurance NO. The accumulated points are notified to the insurance company server of the insurance company that handles the insurance.

  Next, in step 124, the insurance company server 20 notified of the accumulated points calculates the next insurance premium including the next year. The insurance company server 20 calculates an insurance premium as a payment amount based on the point-billing amount correspondence table 34 shown in FIG. In the present embodiment, the point-billing amount correspondence table 34 is provided for each predetermined unit including a grade. Further, discounted premiums may be calculated using the point-insurance premium correspondence table 22 shown in FIG. 9, and the payment amount may be calculated from the calculated premiums. The point-insurance premium correspondence table 22 is also provided for each unit including a grade, similarly to the point-billed amount correspondence table 34.

  In this embodiment, step 124 is executed by the insurance company server 20, but may be executed by the verification system 30. In this case, the collation system 30 has a point-insurance premium correspondence table 22 and a point-invoice amount correspondence table 34. Then, using these tables, the process of step 122 is performed, and the process of step 124 is executed. Then, the calculated insurance premium is notified to the corresponding insurance company server 20. Furthermore, the discount premium may be calculated by the matching system 30, and the insurance premium may be calculated based on the discount premium by the corresponding insurance company.

  Next, the insurance company server 20 creates the next insurance plan based on the insurance premium calculated in step 124. Note that the present embodiment also includes calculating the grade in the same manner as the insurance premium in step 124.

  This is the end of the description of the second processing flow. Next, the flow of the third process in the present embodiment will be described with reference to FIG. The third process is a payment process in service grant.

  First, in step 126, the collation system 30 calculates an issue point for each predetermined unit including a store. The collation system 30 performs a sort process using the store as a key in the collation DB 31, and calculates the total number of issue points of each store.

Next, in step 127, a burden amount corresponding to the issue point is calculated.
First, similarly to the point-insurance premium correspondence table 22 and the point-billing amount correspondence table 34, a billing amount for each store is determined using a table showing the correspondence between points and amounts.

  Next, in step 127, the collation system 30 notifies the calculated billing amount to each store server 40. Then, the dealer server 40 that has received the notification of the charged amount in step 129 executes a process for settlement of the charged amount in step 130. Here, processing for paying the billing amount to the organization that manages the verification system 30 is executed. This process includes bank account transfers and transfers.

  In the present embodiment, the verification system 30 includes processing for payment to each insurance company. In this case, the collation system 30 executes a sort process using the insurance company as a key in the collation DB 31 and calculates the accumulated points of each insurance company. Then, a process for executing payment of the amount corresponding to the calculated cumulative points is performed for each insurance company.

  In addition, as for the processing after step 126, the following processing is also included in the present embodiment. First, in step 126, issue points calculated for each store are subdivided and calculated for each insurance company. For this purpose, the collation DB 31 first sorts at the store and calculates points for each store. Next, the sorted data is sorted using the insurance company as a key, and the points of each dealer are sorted by the insurance company. As a result, the points subdivided for each insurance company can be calculated.

  Next, in step 127, the calculated points are converted into billing amounts. In step 128, the billing amount for each insurance company is notified to the store server 40 of the store that issued the points.

  Next, in step 130, each dealer server 40 that has received the notification executes a process for payment (settlement) to each insurance company. This process includes course transfer and transfer processes as in the previous case.

  This is the end of the description of the present embodiment. In this embodiment, the points are used for reducing or excluding insurance premiums in automobile insurance, but may be used for other value-added services.

  The present invention makes it possible to implement advertisement distribution of equipment related to car insurance using a computer.

It is a system configuration figure of an embodiment of the invention. It is a figure which shows contractor DB21. It is a figure which shows the purchase information. It is a figure which shows the product data 3 and the product data 4. FIG. It is a figure which shows collation DB31. It is a figure which shows additional service object goods DB32. It is a figure which shows additional service object master DB33. It is a figure which shows goods DB41. It is a figure which shows a point-insurance premium correspondence table. It is a figure which shows the point-billing amount correspondence table. It is a figure which shows the contractor information. It is a flowchart which shows the 1st process in embodiment of this invention. It is a flowchart which shows the 2nd process in embodiment of this invention. It is a flowchart which shows the 3rd process in embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Insurance policyholder terminal, 20 ... Insurance company server, 30 ... Verification system, 40 ... Dealer server, 45 ... Dealer terminal, 50 ... Manufacturer server, 60 ... Network

Claims (1)

In an insurance premium calculation system that is connected via a network to an insurance company server managed by an insurance company that provides automobile insurance and a dealer server that is managed by a dealer that sells equipment related to automobiles,
A storage device for storing points predetermined for each device and contractor information and a program related to the contractor of the car insurance;
Device purchase information including device identification information for identifying a purchased device and insurance identification information for identifying a vehicle insurance of a purchaser of the device from the store server, and an application for additional service related to the device from the store server A receiving device for receiving;
Connected to the storage device and the receiving device, according to the program,
Control is performed so as to calculate a point corresponding to the device identification information based on the received device identification information and the storage unit, and store the insurance identification information and the calculated point in the storage unit in association with each other. And calculating the cumulative value of the corresponding points for the insurance identification information for each fixed period specified by the automobile insurance specified by the insurance identification information, and after updating the automobile insurance based on the cumulative value Calculate information on insurance premiums for
An insurance premium calculation system comprising: a control device that determines whether or not advertisement distribution for the additional service application is necessary and controls distribution of the advertisement to an insurance policyholder terminal when distribution is necessary.

Images