JPH08329142A - Insurance commodity management system - Google Patents

Abstract

PURPOSE: To allow an insurance commodity management system to simply correspond to the new development/correction of an insurance commodity by adding/correcting only data in a commodity information table in accordance with the new development/ correction by preparing a transaction procedure in each reference information related to each insurance commodity and evaluating the commodity based upon data in the commodity information table. CONSTITUTION: Transaction check peculiar to a new contact or maintenance is executed based upon customer's information given from a terminal 1, reference keys 5 and sub-keys 6 in corresponding commodity information tables 4 are retrieved by successively starting all transaction procedures 3 (contact age transaction, maximum insurance transaction, etc.) to be reference information to generate an evaluation result indicating whether the transaction procedures can be transacted or not, and when all the procedures can be transacted, a message indicating the success of the contract is transmitted to the terminal 1. Since a transaction procedure and a commodity information table 4 are combined like a capsule in each reference information of an insurance commodity, corresponding tables 4 are retrieved by successively starting the procedures 3 to generate respective evaluated results, the new development or correction of an insurance can simply be dealed only by adding or correcting data to/in the table 4.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an insurance product management system for managing insurance products.

[0002]

2. Description of the Related Art Conventionally, an insurance product management system for managing various insurance products such as life insurance, as shown in FIG. 6, for example, does the information received from a terminal via a line relate to a new contract? After classifying whether it is related to maintenance or fee, the information is passed to each applicable new contract subsystem, maintenance subsystem, or fee subsystem, and the subsystem to which the information is passed According to the handling procedure (for each type), the result was obtained and returned to the terminal.

[0003]

Conventionally, as shown in FIG.
For information about insurance from the terminal,
After determining whether it is a new contract, maintenance, fee, etc. as pre-processing, further pass the information to the relevant subsystem, request the result according to the handling procedure for each kind of maintenance within the subsystem, and send it back to the terminal Therefore, when a new product is developed, it is necessary to add a mortar in each subsystem and to describe a handling procedure (program) for the mortar, which is extremely troublesome. However, even if a change occurs, there is a problem that it is necessary to change the handling procedure (program) of the corresponding breeding species, which is troublesome.

The present invention solves these problems.
Encapsulates the handling procedure of each basic information related to insurance products and the table for registering basic keys and subsidiary keys, and easily responds by adding / correcting only the table data according to new development / correction of insurance products. It is intended to be possible.

[0005]

[Means for Solving the Problems] Means for solving the problems will be described with reference to FIG. In FIG. 1, the handling procedure 3 is a procedure provided for each basic information regarding insurance products, and is a procedure (program) for evaluation based on the data in the product information table 4.

[0006] The product information table 4 is a table for setting data for evaluating basic information on insurance products in cooperation with the handling procedure 3, and sets common items 5 and individual items 6. .

[0007]

As shown in FIG. 1, the present invention refers to the product information table 4 associated with the handling procedure 3 for each basic information in response to the input of information regarding the customer's insurance product from the terminal 1 or the like. Evaluation is performed using the data of common item 5 of the applicable insurance type, or if there is data of individual item 6, evaluation is performed using the data of common item 5 and the data of individual item 6 and the evaluation results are output. I am trying to do it.

At this time, the presence / absence of the common item 5 data and individual individual item 6 common to the insurance type of the product information table 4 is set, and the individual item 6 is used as the individual item 6 data.
When "Yes" is set, an individual item name and its data are set.

Therefore, by encapsulating the handling procedure 3 of each basic information regarding insurance products and the product information table 4 for registering common items (basic keys) and individual items (secondary keys), new development of insurance products・ It became possible to easily respond by adding / correcting only data to the product information table 4 according to corrections.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the construction and operation of an embodiment of the present invention will be described in detail with reference to FIGS.

FIG. 1 shows a block diagram of an embodiment of the present invention.
FIG. 1A shows a configuration diagram. In FIG. 1 (a), the terminal 1 inputs information about a customer's insurance product,
For example, the host life insurance contract management system is inquired about the evaluation via a line, and the evaluation result is returned to notify the customer.

The life insurance contract management system 2 receives information about a customer's insurance product from a large number of terminals 1, evaluates it, returns the evaluation result, and manages the insurance contract.

The handling procedure 3 is a procedure (program) provided for each basic information regarding insurance products, and is encapsulated with the corresponding product information table 4, and the applicable insurance type in the product information table 4 concerned. It is evaluated based on each data.

The product information table 4 is a table for setting data for each insurance type for evaluating basic information on insurance products in cooperation with the handling procedure 3, and is as shown in FIG. 1 (b). In addition, the basic key which is the common item 5 and the subsidiary key which is the individual item 6 are set.

FIG. 1B shows an example of a product information table (basic information = contract age range). In FIG. 1B, the common item 5 is called a basic key in this embodiment, and whether or not data is set in the item common to all insurance types and the individual item 6 for each basic information of the insurance product. The information (relevant item type) indicating the is set. Here, the following keys are set as the basic keys.

・ Type of insurance (insured CN): 001 (whole life insurance), 002 (endowment insurance), etc. ・ Operation start date: 19950401 (April 1, 1995), etc. ・ Operation end date: 99999999 (undecided) ・ Related Item type: A (insurance period as a secondary key), Z (ANYTYING as a secondary key) Individual item (secondary key) 6 is unique to each insurance type set in the related item type of common item 5. The data (for example, insurance period) is set, and the following items shown in the figure are set.

When "A" (insurance period) is set in the related item type of the basic key: As the insurance period: Less than 20 years As the contract age range is 30 to 60 years old, the product information table 4 By setting a basic key and subsidiary key for each insurance type and setting as shown in the figure, data common to all insurance types can be set to the basic key and individual data can be set to the subsidiary key. It will be possible. When a new life insurance product is developed, it can be added simply by setting data in the basic key and subsidiary key for each insurance type, and even when modifying the product, the basic key and subsidiary key of the applicable insurance type Can be dealt with only by modifying
In either case, it is possible to deal with it by adding / correcting only the data.

FIG. 1C shows a search example. In case of endowment insurance with CN = 002, the applicable date is 19
When the basic key is searched with 950601, two entries of: operation start date: 19950401, operation end date: 99999999, related item type: A (representing the insurance period) are obtained, and both are related item type A.
It is found that (representing the insurance period) is necessary as a secondary key, and it is necessary to make a determination in consideration of the data of this secondary key. Here, as a subsidiary key, ・ In the third entry, ・ Subordinate key: less than 10 years ・ Contract age range: 10 to 60 years old ・ In the fourth entry, ・ Subordinate key: 10 years or more ・Contract age range: data of 05-55 years old is obtained, and as a result, the data of the basic key and the data of any of the secondary keys are satisfied in the third entry or the fourth entry. The result is the desired evaluation result.

[0019] In case of endowment insurance of CN = 002
When the basic key is searched with the application date = 199950601 and the insurance period = 30 years, two entries are obtained: -operation start date: 19950401-operation end date: 99999999-related item type: A (representing the insurance period), All are related item type A
It is found that (representing the insurance period) is necessary as a subsidiary key, and it is necessary to make a determination in consideration of the data of this subsidiary key. Here, as a subsidiary key, ・ In the third entry, ・ Subordinate key: less than 10 years ・ Contract age range: 10 to 60 years old ・ In the fourth entry, ・ Subordinate key: 10 years or more ・Contract age range: 05-55 years old data is obtained, but since the insurance period = 30 years, ・ 4th entry ・ Secondary key: 10 years or more ・ Contract age range: 05-55 years old, An evaluation result obtained by a result that satisfies all the data of the basic key and the data of the subsidiary key of the fourth entry. Here, the evaluation result that the contract age range of the customer needs to be 05 to 55 years old. Becomes

A detailed description will be given below. FIG. 2 shows a flowchart for explaining the operation of the present invention. In FIG. 2, S1
Sells new insurance.

S2 is an online transmission. S3 is
Check the handling. As will be described in detail later with reference to FIG. 3, when operating the terminal 1 of FIG. 1 to sell a new insurance to a customer, the insurance content to be sold is specified through the line to the life insurance of the host. When it is transmitted online to the contract management system 2, the host receives it and sequentially starts all the handling procedures to evaluate whether it can be handled. Here, the evaluation target is the following basic information shown in the figure according to the insurance type.

-Contract age-Maximum insurance premium-Minimum insurance premium-Insurance period-Payment period-etc S4 establishes a contract / issues an insurance policy.

As described above, when the salesperson inputs and sends the customer information about the insurance product to be newly sold to the customer from the terminal 1 of FIG. 1, the life insurance contract management system 2 of the host receives the information and the present invention is applied to the present invention. The handling procedure is sequentially activated, basic information corresponding to the handling procedure is checked, a result (evaluation result) is generated, and the result is returned to the terminal to notify the sales staff. When the evaluation result is OK, the insurance product is sold and contracted, and the insurance policy is issued.

Next, referring to the flow chart of FIG.
The handling check in S3 will be described in detail. Figure 3
Shows a handling check flowchart of the present invention.

In FIG. 3, S11 is input. For this, the salesperson operates the terminal 1 to input the customer information regarding the insurance product to be sold to the customer, and sends it to the system (host) via the line.

The system receives S12. S13
Determines whether it is a new contract or maintenance. This determines whether the information received in S12 is related to a new insurance contract or is related to maintenance. If it turns out to be a new contract,
In S14, a handling check peculiar to the new contract is checked (for example, check contents are checked), and the process proceeds to S16. On the other hand, if it is determined to be maintenance, the handling check peculiar to the maintenance (for example, the elapsed year and month is checked) is performed in S15, and the process proceeds to S16.

In step S16, it is determined whether the contract age can be handled.
For example, as shown in FIG. 4 described later, the contract age handling procedure, which is one of the basic information, is activated and associated with FIG.
The basic key and the subsidiary key of the product information table (contract age range) 4 in (b) are searched, and the evaluation result is obtained to determine whether the product can be handled. If YES, the process proceeds to the next S17.
On the other hand, in the case of NO, in S19, a reply that the handling is impossible is returned.

In step S17, it is determined whether the maximum insurance money can be handled. Similarly, as shown in FIG.
The maximum insurance money handling procedure, which is one of the above, is started, the basic key and the subsidiary key of the associated product information table (maximum insurance money) 4 are searched, and the evaluation result is obtained to determine whether or not it can be handled. If YES, the process proceeds to the next S18. On the other hand, N
In the case of O, a reply that the handling is impossible is returned in S20.

In S18, all basic information such as contract age handling, maximum insurance money handling ...
Since the evaluation result of S is obtained (because everything is OK), the contract is concluded.

In S21, since the contract has been established in S18, the fact that the contract has been established is notified to the terminal 1 via the line. Based on the above, based on the customer information notified from the terminal 1, a handling check peculiar to a new contract or maintenance is performed, and all handling procedures (contract age handling, maximum insurance claim handling, etc.) that are basic information are performed. It sequentially activates and searches the corresponding basic key and subsidiary key of the product information table 4 to generate an evaluation result of whether or not it can be handled, and when all are available, the fact that the contract is concluded is transmitted to the terminal. In this way, the handling procedure 3 and the product information table 4 are encapsulated for each basic information of the insurance product, the handling procedure 3 is sequentially activated, the corresponding product information table 4 is searched, and the evaluation result is generated. Even if there is development or modification of new insurance, it is only necessary to add or modify the data of the product information table 4, and it is possible to deal with it very easily.

Next, the procedure for obtaining the evaluation result as to whether or not it can be handled in FIG. 3 will be described in detail in the order shown in the flowchart in FIG. FIG. 4 shows a table search flowchart of the present invention.

In FIG. 4, in S31, the value of the related item type is evaluated by using the seed keeping CN and the application date as keys. This is the type CN (insurance type code) and the date of application (for example, the date of new participation in insurance) in the customer information regarding the insurance product notified from the terminal 1 of FIG. 1 via the line. Using the key as a key, a basic key (common item) in the product information table 4 of the basic information “contract age range” of FIG. 1B is searched, and the applicable date is satisfied among the entries of the corresponding species CN. The entry having the application start date and the application end date is found, and the value of the related item type of the found entry (for example, A: the value having the insurance period and the contract age range as a secondary key) is extracted.

S32 is a case where the value of the related item type is "insurance period", and in this case, the information of "insurance period" is fetched from the secondary key (for example, in (b) of FIG. 1). Re-edit the key (after importing the "insurance period" from the subsidiary key), for example: -Keep the CN, date of application, insurance period as the key.

In step S33, the applicable contract age range is evaluated by using the maintenance CN, application date, and insurance period as keys. S34 is
According to the evaluation result evaluated in S33, the result of acceptability is returned.

By the above S31, S32 to S34, the handling procedure 3 for each activated basic information is associated with the maintenance CN notified from the terminal 1 and the application date as keys (b) in FIG. When the basic key of the product information table 4 is searched to retrieve the value of the related item type of the corresponding entry, and it is found that the retrieved value is set as a secondary key such as "insurance period". , In addition to the “insurance period” extracted from the sub-key, the contract age range is evaluated using the breeding CN, application date, and insurance period as keys, and the evaluation results are obtained. It is possible to collect and reply the result of insurance coverage when everything is OK.

On the other hand, in S35, since the value of the related item type in S31 is found to be “no related item type”, the contract age range is evaluated as it is (reservation CN, the contract age range is evaluated as it is on the application date). . Then, in S34, the result of acceptability is returned according to the evaluation result.

By the above S31, S35 and S34,
FIG. 1 in which the handling procedure 3 for each activated basic information is associated with the maintenance CN notified from the terminal 1 and the application date as keys.
If the value of the related item type of the relevant entry is found to be none by searching the basic key of the product information table 4 in (b) of (3), the contract age range is evaluated using the relevant maintenance CN and the application date as keys. And returns the result of acceptability according to the evaluation result.

FIG. 5 shows a concrete example of the table of the present invention. This is a schematic representation of how the product information table (basic information = contract age range) of FIG. 1B is actually created.

The "merchandise information table 1" in the upper part is a table for setting the following items shown as the basic key and the subsidiary key, respectively.・ Basic key ・ Reservation CN ・ Application start date ・ Application end date ・ Related item type ・ Secondary key ・ Insurance period ・ Contract age range ・ Related item type The lower part defines the items of product information table 1 It was done. For example, the species CN is defined as PIC X (3), that is, three alphanumeric characters. Others are similarly defined as shown.

[0040]

As described above, according to the present invention,
New development of insurance products because it adopts a structure that encapsulates the handling procedure 3 of each basic information related to insurance products and the product information table 4 for registering common items (basic key) and individual items (secondary key).・ It is now possible to add or modify only the data in the product information table 4 in response to corrections, etc., and easily respond.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

FIG. 2 is a flowchart explaining the operation of the present invention.

FIG. 3 is a handling check flowchart of the present invention.

FIG. 4 is a table search flowchart of the present invention.

FIG. 5 is a specific example of a table of the present invention.

FIG. 6 is an explanatory diagram of a conventional technique.

[Explanation of symbols]

 1: Terminal 2: Life insurance contract management system 3: Handling procedure 4: Product information table 5: Common items (basic key) 6: Individual items (secondary key)

Claims (2)

[Claims] 1. A table for correlating and setting the handling procedure of the basic information for each insurance product, the common item data common to the insurance type and the individual individual item data, and the insurance product of the customer. Corresponding to information input, refer to the above table associated with the handling procedures of the above basic information, evaluate using common item data of the applicable insurance type, or if there is individual item data, common item An insurance product management system comprising means for performing an evaluation using the data of and the data of individual items and outputting the evaluation results. 2. The data of common items common to the insurance types in the above table and the presence / absence of individual items are set, and when the presence of the individual items is set as the data of the individual items, the individual item name is set. The insurance product management system according to claim 1, wherein the data is set.