JP2009288962A - Information processing apparatus, program and, method of generating clause of insurance product - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an apparatus that generates clauses as contract clauses for implementing standard contract transaction which agree with the contents of a new insurance product. <P>SOLUTION: A product data editing part 102 reads out from a product data storage part 150 product data 120 constituted of coverage information corresponding to units of clauses generated by insurance products, such as main and special contracts, and product information defined for combining the coverage information according to an insurance product to be generated, and edits it in accordance with the statements and logical structure of clauses to be generated in consideration of structural differences and coverage references in the product data 120. A condition data generation part 104 converts the edited product data 124 into clause data 128 in a display format and outputs it to a display device 204. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an information processing apparatus, a program, and an insurance product policy generation method for generating a policy clause, which is a contract clause for executing a routine processing of a contract that matches the insurance content of the insurance product. The present invention relates to an information processing apparatus, a program, and an insurance product policy generation method for efficiently generating an insurance policy for an insurance product to be developed, designed and sold.

  Insurance products are stipulated by insurance policy that shows the contents of the insurance. Therefore, the structure related to the insurance content of the insurance product can be considered in the same way as the structure of the description content of the insurance policy. It is legally required to create insurance policies for each insurance product. The structure of a regular insurance policy is one ordinary insurance policy (hereinafter referred to as “main contract”) for each insurance product and a number of special insurance policies (hereinafter referred to as “special contracts” that are added to or modified from the coverage of the main policy. "). When a policyholder concludes an insurance contract for an insurance product, the contractor selects and applies a combination of the main contract and special provisions stipulated in the insurance policy for the insurance product.

  When developing and selling a new insurance product, it is necessary to create a new insurance policy as described above. In practice, however, a new special policy or a part of an existing insurance policy must be added. While reusing, change the contents as necessary to create. In this case, it is not allowed that the newly created insurance policy is inconsistent with the coverage of the new insurance product, so any method that supports the efficient creation of insurance policies that are consistent with the coverage. Is desired.

Conventionally, for example, as shown in Patent Document 1, only the special contract attached to the main contract of the insurance product applied by the contractor is selected, and an insurance policy is extracted by extracting only the part related to the contract of the contractor. This method has been proposed.
JP 2005-346305 A

  In order to make it easy to read, the insurance policy is usually created by applying processes such as “applied” and “reading” to the description. In terms of the special agreement, the same provisions as those in the main contract are used as they are, that is, they are applied mutatis mutandis to reduce the number of special provisions. In addition, when trying to use only a part of the provisions included in the insurance policy relating to the main contract, the part of the specially applied policy is further reduced by changing, ie, replacing, a part of the provisions applied mutatis mutandis.

  In this case, it would be redundant if the provisional provisions were included in the special agreements that are the quasi-applications, so it would be redundant. Must be specified correctly. Furthermore, it is necessary to simplify or supplement the wording by defining and replacing abbreviations for long words in the main contracts and special agreements. In addition, it is necessary to appropriately assign numbers such as chapters, articles, numbers, and sections of the articles that constitute the clauses to each article according to the type of insurance product.

  Furthermore, if the insurance policy for a new insurance product is created by changing or adding to the coverage of an existing insurance product, it is also necessary to clarify where it has been changed or added.

  In the method of Patent Document 1, it is assumed that insurance contracts for various special contracts already exist in a so-called ready-made manner, and the editing process required based on the relationship with the contents described in the main contract contract is taken into consideration. Absent. Therefore, when a new insurance product is developed, it cannot be applied to a case where a new insurance policy is prepared in accordance with the security content of the new product.

  SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and one object of the present invention is information that enables efficient generation of insurance contracts relating to newly developed, designed and sold insurance products. A processing device, a program, and an insurance policy generation method are provided.

  In order to achieve the above object, an aspect of the present invention is an information processing apparatus that generates an insurance policy for an insurance product, the product ID being identification information attached to identify the insurance product, the insurance A product information definition table including a security ID that is identification information for specifying a product name, insurance type, and a security contract, the security ID, a security name associated with the security ID, a security type, and the security A security information definition table including a security ID attached to the security of the reference to be referred to, and a security element component designation information ID which is information for identifying information designating an element component consisting of a clause text constituting the security; , The security element part designation information ID, the document item number indicating the item number attached to the words constituting the contract and the name associated with the guarantee element part designation information, and the name given to the guarantee element part designation information The part designation information name, the subordinate security element part designation information ID that is information for identifying the information that designates the subordinate security element parts that are further subordinate to the one guarantee element part designation information, and the clause text that constitutes each guarantee element part A security element part designation information definition table including a security element part ID assigned to identify a unit of the security element part ID, the security element part ID, a security element part type indicating the type of the security element part, and each security element A security element parts information definition table including a clause text for displaying the contents of the parts, a term data ID which is identification information for identifying terms used in the clause text included in the security element parts, and Term content that is the wording of the associated term, abbreviated term data that is an abbreviation of the term, and term content supplementary data that is a supplementary word for the term A product data storage unit storing a term data definition table storing contract terms data, including a product ID receiving unit that receives the product ID, and the received product ID as a key, and further associated therewith The product data storage unit is searched by the security ID, the security element component designation information ID, the dependent security component component designation information ID, and the security element component ID, and the name of the insurance product, the insurance type, An associated security name, a security type, a document item number indicating an item number attached to a word constituting the clause, a security element component designation information name which is a name given to the security element component designation information, A product data editing unit that extracts at least the security element component type, the terms of the contract, and the term content; and the extracted product data in advance It has a clause data generation section for generating clause data by converting the clause data into a prescribed display format.

  According to the present invention, it is possible to efficiently generate an insurance policy for an insurance product newly developed, designed and sold.

  An embodiment of the present invention will be described below with reference to the drawings. The same reference numerals indicate the same components.

  An information processing apparatus according to an embodiment of the present invention is a clause generation apparatus 100. FIG. 1 shows a functional block diagram thereof, and FIG. 2 shows a hardware configuration diagram thereof. As shown in FIG. 2, the contract generation apparatus 100 is a computer system having a CPU 201, a main storage device 202, an input device 203, a display device 204, an external storage device 205, and an I / O interface 206. is there.

  The external storage device 205 is composed of an appropriate storage medium such as a hard disk drive, and as shown in FIG. 2, a product ID receiving unit 101, a product data editing unit 102, a contract data generation unit 104, and a data output unit 105, which will be described later. A functioning computer software program, a product data storage unit 150, a template data storage unit 152, and a contract data storage unit 154 are stored in a database. The external storage device 205 may be provided separately from the clause generation device 100 as shown in FIG. 2 or may be provided integrally therewith.

  Each program constituting the product ID reception unit 101, the product data editing unit 102, the clause data generation unit 104, and the data output unit 105 is read from the external storage device 205 by the CPU 201 and is configured by a memory such as a RAM. Each function is realized by being expanded in the main storage device 202 and executed by the CPU 201.

  The input device 203 is an input device such as a keyboard and a mouse. The display device 204 is a display device such as various displays, and other output devices such as various printers can be connected thereto. The I / O interface 206 is mounted with an input interface circuit unit that receives an input signal from the input device 203 and delivers the input signal to the CPU 201, and an output interface circuit unit that delivers an output signal from the CPU 201 to the display device 204.

  First, the product data storage unit 150 will be described. As described above, the product data storage unit 150 is a database stored in the external storage device 205, and includes a table in which design data about a new insurance product to be newly planned and designed is recorded in element units. It is prepared for.

  An insurance product is a collection of contract items concluded between an insurance entity and an insured person, and has no physical substance. The collection of contract items constituting the insurance product is nothing but the content of the insurance product contract that expresses the contract items included in the insurance product as a document.

  Therefore, the design data for a new insurance product is the wording that constitutes the insurance product policy itself. If a new contract item is included, the design data is used as the design data. The data is input to the corresponding part of each table stored in the data storage unit 150. That is, at the stage of designing the insurance product, the terms of the clause that require additional changes are accumulated in the product data storage unit 150 as needed, so that the terms of the new insurance product can be automatically generated.

  Next, each table stored in the product data storage unit 150 will be described sequentially. The product data storage unit 150 stores a product information definition table 300, a security information definition table 400, a security element component designation information definition table 500, a security element component definition table 600, and a term data definition table 700. Yes. Hereinafter, the data stored in each table stored in the product data storage unit 150 will be collectively referred to as “product data 120”.

  FIG. 3 shows an example of data defined by the product information definition table 300. The product information definition table 300 has one or more records configured by including a product ID 302, a product name 304, a product type 306, and a guarantee ID list 308, and one record becomes one insurance product. Correspond.

The product ID 302 is an identification code having an arbitrary system assigned so as to uniquely correspond to each insurance product, and corresponds to each record recorded in the product information definition table 300.
The product name 304 is a name given to the insurance product represented by the record. For example, in the record of the insurance product recorded at the top of FIG. 3, the product name 304 is “ordinary accident insurance”.
The product type 306 represents the type of insurance provided by the insurance product of the record, and is recorded as “injury”, “fire”, etc., for example, as shown in FIG.

  The security ID list 308 records a security ID 402 that is an identification code assigned to each security recorded in the security information definition table 400 shown in FIG. 4 in order to further specify the security constituting each insurance product. . The security ID 402 recorded in the security ID list 308 associates each record of the product information definition table 300, that is, each insurance product, with the security content included therein.

  FIG. 4 shows an example of data defined in the security information definition table 400. The security information definition table 400 is a table for storing data representing “main contract” and “special contract”, which are basic units constituting one insurance product. Here, in general, a “main contract” is a part of the base of life insurance, such as “term insurance”, “life insurance”, “elderly insurance”, and so on. It is something that can be done. In addition, “special agreements” are optional additions to the main contract, such as “hospital special contract” and “cancer special contract”, and are generally contracts to further enhance the coverage of the main contract. It is something that cannot be contracted with.

  Each record relating to the security stored in the security information definition table 400 includes a security ID 402, a security name 404, a security type 406, a quasi-first security ID list 408, and a security element component designation information ID list 410.

The security ID 402 is an identification code given to each security that constitutes each insurance product, and an arbitrary system can be adopted.
The security name 404 is a name that is named to accurately represent the contents of each security. As shown in FIG. 4, for example, “Accident Insurance General Insurance Policy”, “Accident Insurance Liability Liability Security Special Provision” Etc. are recorded.
The security type 406 includes “main contract”, “additional special contract” that is contracted in addition to the main contract, and “modified special contract” that is contracted by changing a part of the main contract, depending on the type of security. Record the type.

  The quasi-destination guarantee ID list 408 includes other guarantee IDs 402 that are designated as quasi-destination, to which the guarantee of the record is applied mutatis mutandis. To be recorded. For example, in the security information definition table 400 illustrated in FIG. 4, the security “injury insurance liability liability special provision clause” specified by the security ID “HS0050” is the security “injury specified by the security ID“ HS0001 ”. It is shown that it is applied mutatis mutandis according to the “General Insurance Policy”.

  The security element component designation information ID list 410 records a security element component designation information ID 502 that is an identification code for identifying each clause as an element unit constituting the clause as the guarantee element component designation information. As a result, the record relating to each guarantee element component designation information defined in the guarantee element component designation information definition table 500 illustrated in FIG. 5 is associated with each guarantee that refers to it.

  Next, the security element part designation information definition table 500 will be described. FIG. 5 shows an example of the security element component designation information definition table 500.

The guarantee element component designation information definition table 500 includes a guarantee element component designation information ID 502, a document item number 504, a guarantee element component designation information name 506, a dependent guarantee element component designation information ID list 508, and a guarantee element component ID 510. Have.
As described above, the guarantee element parts designation information ID 502 is an identification code for identifying each clause as an element unit constituting the clause as guarantee element parts designation information, and can be given by an arbitrary system.
The document item number 504 represents the number of a chapter, article, or item that constitutes the agreement, and is recorded as, for example, “Chapter 1”, “Article 1”, “Item 1”, or the like. With respect to the security element component designation information without an item number, the value of the document item number 504 is blank (blank).
The security element part designation information name 506 records a name given to each security element part designation information, and is used as a title of a chapter, an article, or a section constituting a clause. For example, as shown in FIG. 5, words such as “responsibility of our company” and “responsibility of payment of our company” are recorded.

  In the subordinate security element component designation information ID list 508, a record specified by one security element component designation information ID 502 recorded in the security element component designation information definition table 500 of FIG. In order to be able to refer to the record specified by the subordinate, another guarantee element component designation information ID 502 that is the reference destination is recorded. For example, in FIG. 5, the record of the security element component designation information specified by the security element component designation information ID “YS0001” refers to other security element component designation information IDs “YS1001”, “YS1002”, etc. in a subordinate manner. It is shown that.

  The security element part ID 510 is used to specify a security element wording, which is a contract word that will be included in an element unit (guaranteed part parts) that constitutes a contract, from one record specified by the security element part designation information ID 502. In order to refer to the security element part ID 610 that is an assigned identification code, a security element part ID 602 that is a reference destination is recorded.

  Next, the security element part definition table 600 will be described. FIG. 6 shows an example of the security element part definition table 600. The security element part definition table 600 corresponds to a component unit such as a chapter, article, item, or issue included in the contract, and has a record for storing data representing the text of the contract to be included in the unit. It is a table to be recorded.

This security element part definition 600 has a security element part ID 602, a security element part type 604, and a security element wording 606 that is a clause text.
As described above, the security element part ID 602 is an identification code that is assigned to specify the wording that will be included in the element unit that constitutes the clause, and the security element wording, and is assigned based on an arbitrary system. can do.
The security element part type 604 indicates the type of one security element part specified by the security element part ID 602. For example, as shown in FIG. 6, “payment responsibility 001”, “responsibility period 001”, and the like are recorded.
The security element wording 606 records the wording of the contract to be included in the record specified by one security element component ID 602.

  Next, the term data definition table 700 will be described. FIG. 7 shows an example of the term data definition table 700. The term data definition table 700 is a table for storing records created for each term used in the guarantee element wording 606 described with reference to FIG.

  Each record stored in the term data definition table 700 has a term data ID 702, term content 704, abbreviated term data 706 corresponding to the term content 704, and term content supplement data 708 corresponding to the term content 704. .

The term data ID 702 is an identification code for specifying a record relating to each term, and can be defined and assigned based on an arbitrary system. In the example of FIG. 7, serial numbers from “YW0001” are assigned.
The term content 704 records terms corresponding to each record. For example, in the record designated by the term data ID “YW0001” in FIG. 7, the term “insured person described in the insurance policy” It is recorded.
In the abbreviation term data 706, when there is an abbreviation designated to make the clause text as easy to read and as simple as possible with respect to the term recorded in the record, the abbreviation term is recorded. In FIG. 7, “insured person” is recorded as an abbreviation for the term “insured person described in insurance policy” corresponding to the record specified by the term data ID “YW0001”.

  For a term for which the corresponding abbreviation term is not specified, the value is blank (blank), as for the term “insurance” of the term data ID “YW0003” in FIG. As will be described later, this abbreviated term is automatically inserted at a designated location in the guaranteed element wording 606 through control by an identifier embedded in the guaranteed term wording 606 in advance.

  The term contents supplementary data 708 records the word contents of the term contents 704 recorded in the record if a word for supplementary explanation is defined in the clause text. For example, in FIG. 7, the term “insurance claim” of the term data ID “YW0003” means “death insurance, after-effects insurance, hospitalization insurance, surgery insurance or hospital insurance as shown in the figure. "The same shall apply hereinafter" is recorded. As will be described later, the supplementary wording recorded in the term content supplementary data 708 is automatically inserted at a designated location in the guarantee element wording 606 through control by an identifier embedded in the guarantee terminology wording 606 in advance. .

  Next, the template data storage unit 152 will be described. As shown in FIG. 1, the template data storage unit 152 includes a product data editing template definition table 800 that is a table storing rules for editing the product data 120 extracted from the product data storage unit 150 as a contract, A contract data generation template definition table 900 that is referred to when generating a contract as a document as a target object using the edited product data 120;

  First, the product data editing template definition table 800 will be described. As shown in FIG. 1, the product data editing template definition table 800 is read into the product data editing unit 102 as a product data editing template 122 which is an individual record constituting the product data editing template definition table 800, and the product data 120 is edited here. Referenced when. As shown in FIG. 8, the product data editing template definition table 800 records a product type 802, a product data editing rule 804, and a product data numbering rule 806 as one record.

The merchandise type 802 corresponds to the merchandise type 302 recorded in the merchandise information definition table 300 of FIG. 3, and the type of insurance product such as “injury” and “fire” is recorded.
The product data edit rule 804 records an edit rule defined for editing the configuration of the security element defined for each product type 802. Details will be described later.
The merchandise data numbering rule 806 records a rule for numbering an item number such as a chapter, an article, an item, or a number according to the configuration of the security element. Details will be described in detail.

  Next, the clause data generation template definition table 900 will be described. FIG. 9 shows an example of the clause data generation template definition table 900. As shown in FIG. 1, the clause data generation template definition table 900 is read into the clause data generation unit 104 as a clause data generation template 125, which is an individual record constituting the clause data generation template, and is based on the edited product data 120 here. Applies to clause data generation processing.

  The clause data generation template definition table 900 includes a product type 902 and a clause data generation style sheet 904 as one record. Similar to the product type 802, the product type 902 corresponds to the product type 302 recorded in the product information definition table 300 of FIG. 3 and records the types of insurance products such as “injury” and “fire”.

  The contract data generation style sheet 904 records style sheets defined for each product type 902, in other words, format format data, in order to generate the contract data 128 from the product data 120 edited by the product data editing unit 102. Yes. The contract data 128 is a data file for conversion for converting the product data 120 into a format that can be displayed on a display or the like as the display device 204. This will be described in detail later.

  Next, the clause data storage unit 154 will be described. The clause data storage unit 154 is a database for storing the clause data definition table 1000, as illustrated in FIG. 10, and is stored in the external storage device 205 in FIG.

  The clause data definition table 1000 is a table for storing the clause data 128 generated by the clause data generation unit 104. As shown in FIG. 10, the generation date and time 1002, the product ID 1004, and the clause data content 1006 are stored. It is recorded.

  The generation date and time 1002 is time stamp data that is given to the contract data 128 generated by the contract data generation unit 104 at an appropriate timing to indicate the generation date and time. For example, for one insurance product, the date and time of the year when the clause data generation unit 104 has completed generation of the clause data 128 from the product data 120 (21:07 on March 28, 2008 in the example of FIG. 10). "2008-0328-2107") is acquired from the CPU 201 and the time stamp data is added to the clause data 128. This generation date and time 1002 can be used as, for example, one of the search keys when searching for the clause data 128 stored in the clause data storage unit 154 as will be described later.

The product ID 1004 corresponds to the product ID 302 in the product information definition table 300 and is an identification code for specifying the insurance product for which the clause data 128 is generated.
The clause data content 1006 records the contents of the generated clause data 128. The clause data 128 once stored in the clause data storage unit 154 is hereinafter referred to as “past clause data 126”.

  Next, with reference to FIG. 1, the processing flow until the contract data 128 is generated for a certain insurance product will be described with reference to the related drawings.

  As shown in FIG. 1, a product ID 118 of an insurance product for which a policy is to be generated is input from the input device 203. At this time, it is assumed that the product data 120 necessary for generating the contract data 128 is already stored in the product data storage unit 150. As described above, the product data 120 is input from the input device 203 at any time during the development and design stage of the insurance product and stored in the product data storage unit 150. When the development design of the insurance product is completed, The contract for the product can be automatically generated.

  In addition, although not shown in particular, an interface in which a security element part or the like that has been completed as the development design progresses is automatically taken from the design process to a newly developed and designed insurance product. It is good also as providing.

The product ID 118 input from the input device 203 is received by the product ID receiving unit 101 and delivered to the product data editing unit 102.
The product data editing process in the product data editing unit 102 will be described according to the processing flow of FIG.
When the product data editing unit 102 starts processing in step 1101, the product data reading unit 102 performs the following processing in product data reading processing step 1102. That is, first, the product information definition table 300 is searched using the product ID 118 received from the product ID receiving unit 101 as a key, and records having the same product ID are read.

  Next, the security information definition table 400 is searched by the security ID 402 recorded in the security ID list 308 included in the corresponding record of the read product information definition table 300, and a record having the corresponding security ID 402 is read.

  Further, the security element part designation information definition table 500 is searched by using the security element part designation information ID 502 recorded in the security element part designation information ID list 410 included in the read security information definition table 400 record, and the corresponding security element designation information definition table 500 is searched. A record having element component designation information ID 502 is read.

  Further, the guarantee element component designation information definition table 500 is searched by the guarantee element component designation information ID 502 recorded in the dependent guarantee element component designation information ID list 508 included in the read guarantee element component designation information definition table 500 record. Then, the record having the corresponding security element component designation information ID 502 is read as subordinate security element component designation information.

  Further, the security element component definition table 600 is searched by the security element component ID recorded in the security element component ID list 510 included in the read security element component designation information definition table 500, and the corresponding security element component definition table is searched. 600 records are read.

  In this way, with the data of the product information definition 300 as the head, the product data 120 necessary for generating a policy for a certain insurance product is read. In this way, a record including necessary product data 120 is read out from each table stored in the product data storage unit 150 in a so-called formula using the designated product ID 118 as an initial search key.

  Next, the product data editing unit 102 performs a replacement process on the product data 120 read from the product data storage unit 150 in Step 1102 in Step 1104 of FIG.

  In step 1104, first, a record in the security information definition table 400 referred to by the security ID 402 recorded in the security ID list 308 (hereinafter referred to as “applied source security information”) from the record in the product information definition table 300 read in step 1102. Get one definition record). In the same manner as in step 1102, the records of the security element component designation information definition table 500 and the security element component definition table 600 that are referenced by the acquired records of the security information definition table 400 are acquired.

  Further, the security information definition table 400 is further searched for a record including the security ID 402 corresponding to the record of the acquired security information definition table 400 in the quasi-destination security ID list 408. Records included in the element component designation information definition table 500 and the guarantee element definition component definition table 600 are acquired. That is, when a record having “HS0001” as the guarantee ID 402 is acquired, another record included in the guarantee information definition table 400 is searched with the guarantee ID 402. In this case, the guarantee ID 402 is “HS0050”, “HS0100”. And the records included in the guarantee element component designation information definition table 500 and the guarantee element definition component definition table 600 associated therewith are also acquired.

  Guarantee as a quasi-use destination acquired in the latter having the same value of the guarantor element part type 604 as the record of the guarantor element part definition table 600 as the quasi-use source acquired in the former (hereinafter referred to as “semi-source element guarantee element part definition record”) If there is a record in the element definition component definition table 600 (hereinafter referred to as “secondary pre-guaranteed element component definition record”), the following processing is performed.

  That is, the text of the security element wording 606 of the quasi-used source security element part definition record is compared with the text of the security element text 606 of the quasi-source security element part definition record, and a portion having a different wording is detected. Using the detected different wording, a new security element component definition table 600 record expressing replacement and a new security element component designation information definition table 500 record referring to this are generated.

  The security element wording 606 of the newly generated guarantee element part definition table 600 record is the value of the security element part designation information ID 602 of the quasi-destination guarantee element part definition record in order to record where the quasi-use source has been read. Based on the above, a word including “$ r {value of security element component designation information ID 602}” is also generated.

  Further, in order to make it possible to refer to the data of the generated guarantee element component designation information definition table 500 from the quasi-source security information definition record, the guarantee element component designation information ID 502 of the record of the generated guarantee element component designation information definition table 500 is used. Is added to the security element component designation information ID list 410 of the quasi-source security information definition record. In addition, since the quasi-original security element part definition record is unnecessary when the replacement is performed, the data of the security part designation information definition table 500 that refers to this is deleted.

  An example of the processing from step 1102 to step 1104 described above will be specifically described. First, in step 1102, “SH0001” is received as the product ID 118, a record 350 including the product ID 118 is acquired from the product information definition table 300, and product data 120 associated with this as an initial search key is acquired.

  Next, in step 1104, a record 652 is acquired from the security element part definition table 600 of FIG. 6 as a quasi-source security element part definition record, and a record 654 is acquired as a quasi-destination security element part definition record. The merchandise data editing unit 102 compares the record 652 and the record 654 with respect to the text of the security element wording 606, and the portion described as “injury” in the security element wording 606 of the record 652 is the security element wording 606 of the record 654. Detects that it is listed as "damage".

  Therefore, as data of the security element part definition table 600 indicating replacement, “injury” where the security element part ID 602 is “YY20001”, the security element part type 604 is “replacement 002”, and the security element wording 606 is “$ r {YS10023}”. Is replaced with “damage”. Is generated.

  Further, in order to be able to refer to the replacement record of the security element component definition table 600 generated in this way, the security element component designation information ID 502 is “YS30001” as a record of the security element component designation information definition table 500. A new record in which the document item number 504, the security element component designation information name 506, and the dependent security component component designation information list 508 are “(blank)” and the security element component ID 510 is “YY20001” is generated and added.

  Furthermore, in order to match the structure of the contract to be generated, the guarantee element parts designation information ID 502 is “YS3000”, the document item number 504 is “(blank)”, the guarantee element parts designation information name 506 is “replacement of the normal agreement”, the subordinate guarantee “YS30001” is added to the element component designation information list 508, and a record in which the guaranteed element component ID 510 is “YY0005” is generated.

  Further, in order to make it possible to refer to them, “YS3000” is added to the security element component designation information ID list 410 in the quasi-source security information definition record 452. Further, the data of the security part designation information definition 500 shown in the record 584 referring to the quasi-source security element part is deleted.

  Returning to the processing flow in the product data editing unit 102 in FIG. 11, in step 1106, a security element configuration editing process is performed to match the product data 120 processed in step 1104 with the configuration content of the generated clause. The product data editing template 122 which is a record of the product data editing template definition table 800 having the same value as the product type 306 of the record of the product information definition table 300 read in step 1102 as the product type 802 is read.

  In accordance with the product data editing rules 804 recorded in the read product data editing template 122, the security element configuration editing process is performed. Here, it is assumed that a processing example described below is recorded in the product data editing rule 804 in accordance with an appropriate format. The contents of this processing differ depending on the rules recorded in the product data editing template 122.

  First, the product data editing unit 102 compares the quasi-source record and the quasi-destination record included in the guaranty element component designation information definition table 500 and refers to the guarantor element component designation information referring to the record in the same guarantee element component definition table 600. The record in the definition table 500 is deleted. For example, the records 560 and 562 of the quasi-destination guarantee element part designation information definition table 500 and the records 580 and 582 of the quasi-destination guarantee element part designation information definition table 500 are compared, and the results are “YY00021” and “YY00022”, respectively. ”, The records 580 and 582 which are quasi-application sources are deleted.

  Next, in the record of the security element component designation information definition table 500, when both values of the dependent security component component designation information ID list 508 and the security element component ID 510 are blank (blank), the product data editing unit 102 selects the record. Judge as unnecessary and delete it. For example, as described above, the records 580 and 582 are deleted, and the record 584 is deleted by the replacement process in step 1104. Therefore, the dependent security element component designation information ID of the record 578 of the security element component designation information definition table 500 that refers to them. Since the list 508 is determined to be blank (blank) and the guarantee element part ID 510 is also blank (blank), the record 578 is deleted.

  Next, in step 1108, term processing is performed. The term processing is to replace the designated part with the term recorded in the term data definition table 700 to which the designated part is referred with respect to the guarantee element wording 606 included in each record of the guarantee element component definition table 600. . In the present embodiment, the term reference location in the security element wording 606 is defined in the format of “$ w {term data ID 702}”. The merchandise data editing unit 102 searches for the code “$ w” in the security element wording 606 in each record of the security element component definition table 600 and performs the following processing.

  First, the record of the term data definition table 700 referred to by the code “$ w” is searched. When the omitted term data 706 and the term content supplement data 708 are not recorded, the part of “$ w {}” is replaced with the term content 704. If the omitted term data 706 is recorded and it is not the first time to refer to the record of the term data definition table 700 to be referred to in the record of the security information definition table 400 acquired in step 1104, “$ w {} "Is replaced with abbreviation term data 706 which is an abbreviation corresponding to the term contents 704.

  At this time, when it is the first time to refer to the record of the term data definition table 700 to be referred to among the records of the security information definition table 400 acquired in step 1104, the part of “$ w {}” is used as the term contents 704. And abbreviated term data 706. If there is term content supplement data 708, term content supplement data 708 is inserted in addition to term content 704.

  A specific processing example of step 1108 will be described. In step 1104, it is assumed that records 650, 652, and 656 are acquired as the quasi-source former security element part definition data. Since it is detected that “$ w {YW0002}” is included in the security element wording 606 recorded in the records 650, 652, and 656, “$ w { “YW0002}” is abbreviated and accidental outpatient accident (hereinafter referred to as “accident”), and “$ w {YW0002}” in the security element wording 606 of records 652 and 656 is an abbreviation “accident”. Replace with

  Further, since it is detected that “$ w {YW0001}” is included in the security element wording 606 of the records 650 and 656, “$ w {YW0001}” of the security element wording 606 of the record 650 is “insurance”. In the insured person of the security (hereinafter referred to as “insured person”), “$ w {YW0002}” in the security element wording 606 of the record 656 is replaced with the abbreviation “insured person”.

  Furthermore, since “$ w {YW0003}” is detected in the security element wording 606 of the records 650 and 652, “$ w {YW0003}” of the security element wording 606 of the record 650 is changed to “insurance (death insurance, Refers to post-mortem disability insurance, hospitalization insurance, surgery insurance, or outpatient insurance. The same shall apply hereinafter.) ”And“ $ w {YW0003} ”in the security element wording 606 of record 652 is changed to“ insurance ”. replace.

  In step 1110, it is determined whether or not the processing in steps 1104 to 1108 is continued. This process continuation determination means that the record in the security information definition table 400 referred to by the security ID list 308 from the record in the product information definition table 300 read in step 1102 has not yet been acquired in step 1104 and has not been acquired in step 1104. If there is something that has not been processed in 1108, the process proceeds to step 1104; otherwise, the process proceeds to step 1112.

  In step 1112, item numbering processing is performed. The item numbering process is to assign a number such as a chapter, article, item, or number to the product data 120 processed in steps 1104 to 1110 according to the structure of the contract. The numbering rules differ depending on the product type 306.

  The product data editing template 122 having the same value as the product type 306 of the record of the product information definition table 300 read in step 1102 as the product type 802 is read, and the product type 306 is based on the product data numbering rule 806 recorded on the template. The document number 504 representing the number such as a chapter, article, item, or issue in the security element component designation information definition table 500 is generated.

  In step 1114, an item number complementing process is performed. In a clause, other parts of the clause may be referred to by the number of the chapter, article, section, or issue and the name given to that part. Therefore, in the security element wording 606 recorded in the record of the security element component definition table 600, a part that refers to another part is defined with an identifier of “$ r {guarantee element component designation information ID 502}”. At this point, at step 1112, the composition of the entire contract based on the product data 120 and the number of the chapter, article, item, or number attached to it are determined. Replace with the number and name of the article, paragraph, or issue.

First, the data of the security element component designation information definition 500 referenced by $ r is searched. If the document item number 504 of the data of the guaranteed element component designation information definition table 500 and the guaranteed element component designation information name 506 are not blank, the “$ r {}” portion is used as a chapter or an article. Replace with the number and name of the item or item.
However, when referring to “Section”, it is not possible to specify which “Section” belongs to which “Section” refers to by “Section” number. The number and its name are also replaced.

  Whether the reference destination is an article or a term can be determined by the product data editing unit 102 based on the number of characters of the insurance element component designation information ID 502, for example. If it is determined that the reference destination is “item”, the “item” number is set using the document item number 504 of the record in the security element component designation information definition table 500 corresponding to the “article” referring to the item. In addition, replace with the “Article” number. If the security element component designation information name 506 is not blank, the name is also replaced.

  A specific processing example of step 1114 will be described. In this processing example, it is defined that the “article” number is indicated when the number of digits of the security element component designation information ID 502 is 6 digits, and the “item” number is indicated when it is 7 digits. To do.

  When there is a record 656 as a record of the security element part definition table 600, the product data editing unit 102 detects the code “$ r {YS1001}” indicating the item number complementing process location in the security element wording 606. . Then, a record 552 is detected as a record of the security element component designation information definition table 500 from the security element component designation information ID “YS1001”.

  Here, in the preceding step 1112, it is assumed that “Article 1” is set in the document item number 504 of the record 552 and “payment responsibility of this company” is set as the security element component designation information name 506. At this time, “$ r {YS1001}” in the security element wording 606 of the record 656 is replaced with “Article 1 (Responsibility for payment of the Company)”. Further, in the record of the security element part definition table 600 indicating the replacement of the security element part ID 602 of “YY20001” shown in the processing examples from the step 1102 to the step 1104, the security element wording 606 is “$ r {YS10023}”. "Injury" is replaced with "Damage".

  At this time, the record 564 is detected as a record of the guarantee element part designation information definition table 500 from the guarantee element part designation information ID “YS10023”, and since the guarantee element part designation information ID “YS10023” has seven digits, this is And the record 558 is also detected as a record of the guarantee element component designation information definition table 500 that includes this in the dependent guarantee element component designation information ID list 508.

  Here, in the preceding step 1112, “Article 2” is set as the document item number 504 of the record 558, “Start and end of responsibility” are set as the security element component designation information name 506, and the document item number 504 of the record 564 is set. It is assumed that “3rd term” is set in. At this time, the item number supplement processing designation location “$ r {YS10023” included in the security element wording 606 of the record of the security element part definition table 600 indicating the replacement of the security element wording 606 whose security element part ID 602 is “YY20001”. } "Is replaced with the phrase“ Article 2 (Start and End of Liability) Section 3 ”.

  When the above processing is executed, the processing flow ends at step 1115.

  Next, the clause data generation process in the clause data generation unit 104 will be described according to the processing flow shown in FIG.

  When processing is started in step 1201, in step 1202, first, product data 120 processed by the product data editing unit 102 (hereinafter referred to as “edited product data 124”) is received from the product data editing unit 102, The contract data generation template 125 having the same value as the product type 306 of the record of the product information definition table 300 that is one of the edited product data 124 as the product type 902 is read from the template data storage unit 152. Based on the clause data generation style sheet 904 recorded in the read clause data generation template 125, for example, the edited product data 124 is converted into an XML format (hereinafter, the converted edited product data 124 is referred to as “term data 128”. ").

  An example of the contract data 128 is shown in FIG. Since the edited product data 124 is defined according to the structure of the contract and edited by the product data editing unit 102, for example, conversion to the XML format is performed in the same manner as the data structure in the contract data storage unit 154. By defining an XML tag for the structure, conversion from the clause data 128 to the XML format can be realized.

  In step 1204, first, data in the contract data definition table 1000 having the same value as the product ID 302 included in the record of the product information definition table 300, which is one of the edited product data 124, as the product ID 1004 (hereinafter referred to as “past clause data”). 126 ”).

  Of the past agreement data 126, the one with the latest generation date 1002 is selected, and text matching with the agreement data 128 generated in step 1202 is performed to generate the difference data 130 of the agreement. It is assumed that the product ID 302 of the record of the product information definition table 300 which is one of the edited product data 124 is “SH0001”, and the record 1050 of the clause data definition table 1000 is read as the past clause data 126. The clause data content 1006 is clause data 1300 shown in FIG.

  Compared to the past clause data 126, the clause data 128 generated in step 1202 is that the portion indicated by reference numeral 1302 in the clause data 1300 has changed from “180” to “300” as illustrated in FIG. To do. An example of the difference data 1500 at this time is shown in FIG.

  As described above, the clause data generation unit 104 can also compare the changed portion of the newly generated clause data 128 with respect to the past clause data 126 with the contents of the change, and also generate the clause difference data 130 that can be specified.

  Next, in step 1206, first, a record of the contract data definition table 1000 is generated based on the generated contract data 128 and written to the contract data storage unit 154. As described above, the record of the contract data definition table 1000 to be generated is recorded in the record of the product information definition table 300, which is one of the edited product data 124, with the date and time when the contract data 128 is generated as the generation date and time 1002. The product ID 302 is recorded in the product ID 1004, and the clause data 128 is recorded in the clause data content 1006.

Next, the display data conversion program prepared in step 1202 is converted by a display data conversion program or the like prepared in advance, for example, the clause data 128 generated in XML format, and the difference data 130 generated in step 1204 is prepared in advance. Etc., and the data is transferred to the data output unit 105. Thereafter, in step 1207, the processing flow ends. A display example of an example 1300 of the contract data shown in FIG. 13 is shown in 1500 of FIG.
The data output unit 105 converts display data such as the clause data 128 into an appropriate output interface signal and outputs it to the display device 204.

  As described above, according to an embodiment of the present invention, it is possible to efficiently generate an insurance policy for an insurance product newly developed, designed and sold.

  Product data editing rules defining rules for arranging insurance product types and product data extracted by the product data editing section associated with the insurance product as a contract, and the guarantee included in the product data Product data editing template definition table that stores product data numbering rules that define the rules for assigning item numbers to element parts, and format data that converts the extracted product data into a format for display as a contract And a product data editing unit for extracting the insurance product type associated with the product ID from the product information definition table, and the insurance product type. The corresponding product data editing template is read from the template data storage unit according to If the policy data generation template for the insurance product is generated by applying the policy data generation template to the read product data based on the data, the policy for displaying the consistency of the description content can be displayed as a document. Data can be created efficiently.

  The Product Data Editor compares the clause text contained in the referenced security element part with the clause text contained in the reference source security element part, and if it finds a different word, it uses the found word. Thus, if a new security element part and new security element part designation information that refers to the new security element part are generated, the mutatis mutandis relationship between clauses in the clauses can be accurately defined.

  If the product data editing section deletes the security element wording contained in the security element component that is the reference source, the product data editing section can omit the duplicate description in the contract and simplify the description of the contract.

  The clause text recorded in the guarantee element part definition table of the product data includes an identifier indicating a term that can be replaced with the abbreviation term data recorded in the term data definition table, and the product data editing unit If the corresponding term in the security element statement is replaced with an abbreviation according to the identifier, the redundant term included in the agreement can be accurately replaced with an abbreviation to make the description of the agreement more concise.

  The clause text recorded in the guarantee element part definition table of the product data includes an identifier indicating the insertion location of the term content supplementary data recorded in the term data definition table, and the product data editing unit is in accordance with the identifier. If the term content supplementary data is inserted into the relevant part of the agreement text, the supplementary description of the term can be accurately inserted into the relevant part of the agreement to make it easier to understand the provision. .

  The product data editing unit reads the product data editing template corresponding to the insurance type of the target insurance product from the template data storage unit, and assigns a number to the clause included in the product data according to the product data numbering rule recorded in the product data editing rule. If it is granted, a consistent number in accordance with the system of regulations can be assigned to each clause of the agreement.

  The clause text recorded in the security data component definition table of the product data includes an identifier indicating the insertion position of the item number attached to the reference clause in the clause, and the product data editing unit, according to the identifier, If the item number of the reference clause is inserted at the relevant place in the wording, the item number of the reference clause can be accurately given to the description of the clause.

  The policy data generation unit reads the policy data generation template corresponding to the insurance type of the target insurance product from the template data storage unit, and is generated by the product data editing unit according to the display format recorded in the policy data generation template. If the product data is converted into terms and conditions data, the contents of the terms and conditions can be output in the prescribed terms and conditions format.

  A provision data storage unit for storing the general data is further provided. If the general data generation unit writes the generated general data to the general data storage unit, the generated general data is read out later and changed or modified. It can be reused by doing so.

  The clause data generation unit generates the difference data by comparing the generated clause data with other clause data generated in the past stored in the clause data storage unit. It is possible to clarify the difference between the contents of the contract and the contents of other contracts generated in the past.

  In the above-described embodiment, the insurance policy has been described as an example. However, the present invention can also be applied to generation of a policy for various financial products other than insurance.

It is a figure which shows an example of the functional block of the clause production | generation apparatus which concerns on one Embodiment of this invention. It is a figure which shows an example of the hardware constitutions of the agreement production | generation apparatus which concerns on one Embodiment of this invention. It is a figure which shows an example of a structure of the merchandise information definition table with which the clause production | generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example of a structure of the security information definition table with which the clause production | generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example of a structure of the security element components designation | designated information definition table with which the clause production | generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example of a structure of the security element components definition table with which the clause production | generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example of a structure of the term data definition table with which the clause production | generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example of a structure of the goods data edit template definition table with which the clause production | generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example of a structure of the clause data generation template definition table with which the clause generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example of a structure of the clause data definition table with which the clause production | generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example of the processing flow in the goods data edit part with which the clause production | generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example of the processing flow in the clause data generation part with which the clause generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example of the clause data produced | generated in the clause data generation part with which the clause production | generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example of the clause difference data produced | generated in the clause data generation part with which the clause production | generation apparatus which concerns on one Embodiment of this invention is provided. It is a figure which shows an example which output the contract data produced | generated in the clause data generation part with which the clause production | generation apparatus which concerns on one Embodiment of this invention is provided to the display apparatus.

Explanation of symbols

100 Covenant Generation Device 101 Product ID Accepting Unit 102 Product Data Editing Unit 104 Contract Data Generating Unit 105 Data Output Unit 118 Product ID
120 Commodity data 122 Commodity data editing template 125 Contract data generation template 128 Contract data 130 Contract difference data 150 Commodity data storage unit 152 Template data storage unit 154 Contract data storage unit 203 Input device 204 Display device 300 Product information definition table 400 Security information definition Table 500 Security element part designation information definition table 600 Security element part definition table 700 Term data definition table

Claims (15)

An information processing device for generating insurance policies for insurance products,
A product information definition table including a product ID that is identification information assigned to specify an insurance product, a name of the insurance product, an insurance type, and a security ID that is identification information for specifying a security contract;
Information specifying the security ID, a security name associated with the security ID, a security type, a security ID attached to the security of a reference destination referred to by the security, and information specifying an element part of a contract word constituting the security A security information definition table including a security element component designation information ID which is information for identification;
The guarantee element component designation information ID, the document item number indicating the item number attached to the words constituting the contract, and the name assigned to the guarantee element component designation information are associated with the guarantee element component designation information ID. Information name, subordinate security element part designation information ID that is information for identifying information that designates a subordinate security element part that is further subordinate to one security element part designation information, and a unit of a contract word constituting each security element part A security element part designation information definition table including a security element part ID attached to identify
A security element part information definition table that includes the security element part ID, a security element part type that indicates the type of the security element part, and a clause statement that displays the contents of each security element part;
It is a term data ID that is identification information for identifying a term used in the clause text included in the guarantee element component, a term content that is a term of a term associated with the term data ID, and an abbreviation of the term A product data storage unit storing a term data definition table that stores contract term data including abbreviation term data and term content supplement data that is a supplementary word for the term;
A product ID receiving unit for receiving the product ID;
Using the received product ID as a key, the product data storage unit is further configured by the security ID, the security element component designation information ID, the dependent security component component designation information ID, and the security element component ID associated with the guarantee ID. The name of the insurance product, the insurance type, the security name associated therewith, the security type, the document item number indicating the item number attached to the words constituting the clause, and the security element component designation information A product data editing unit for extracting at least the security element part designation information name, the security element part type, the terms of agreement, and the term contents,
An information processing apparatus comprising: a contract data generation unit that converts the extracted product data into contract data in a display format defined in advance to generate contract data.   The product data editing rule that defines the insurance type of the insurance product and the rules for arranging the product data extracted by the product data editing unit associated with the insurance product as a contract, and included in the product data The product data editing template definition table that stores the product data numbering rules that define the rules for assigning item numbers to the guaranteed element parts, and the extracted product data is converted into a format for display as a contract A template data storage unit that stores a clause data generation definition table that is format data to be generated, and the product data editing unit extracts an insurance product type associated with the product ID from the product information definition table, and According to the insurance product type, the corresponding product data editing template is stored from the template data storage unit. Look out, the information processing apparatus according to claim 1, characterized in that to generate the clause data of the insurance products by applying the clause data generation templates to the read commodity data based on this.   The product data editing unit compares the terms of the clause included in the referenced security element part with the terms of the clause included in the reference source security element part, and if they find different words, 3. The information processing apparatus according to claim 2, wherein a new security element part and new security element part designation information that refers to the new security element part are generated.   The information processing apparatus according to claim 3, wherein the product data editing unit deletes the clause text included in the security element part that is a reference source.   The clause text recorded in the guarantee element part definition table of the product data includes an identifier indicating a term that can be replaced with the abbreviation data recorded in the term data definition table, and the product data editing unit includes: The information processing apparatus according to claim 2, wherein a corresponding term in the clause text is replaced with an abbreviation according to the identifier.   The clause text recorded in the security element component definition table of the product data includes an identifier indicating an insertion position of the term content supplementary data recorded in the term data definition table, and the product data editing unit includes the identifier 3. The information processing apparatus according to claim 2, wherein the term content supplementary data is inserted at a corresponding location in the clause text according to the above.   The product data editing unit reads the product data editing template corresponding to the insurance type of the target insurance product from the template data storage unit, and numbers the clauses included in the product data according to the product data numbering rule recorded in the product data editing rule. The information processing apparatus according to claim 2, wherein:   The clause text recorded in the security data component definition table of the product data includes an identifier indicating the insertion position of the item number attached to the reference clause in the clause, and the product data editing unit is configured to 3. The information processing apparatus according to claim 2, wherein an item number of the reference clause is inserted at a corresponding portion in the clause text.   The policy data generation unit reads the policy data generation template corresponding to the insurance type of the target insurance product from the template data storage unit, and generates the policy data editing unit according to the display format recorded in the policy data generation template. The information processing apparatus according to claim 2, wherein the processed product data is converted into contract data.   The information processing apparatus according to claim 1, further comprising a clause data storage unit that stores clause data, wherein the clause data generation unit writes the generated clause data into the clause data storage unit.   The clause data generation unit compares the generated clause data with other clause data generated in the past stored in the clause data storage unit, and generates difference data thereof. The information processing apparatus according to 1. A program for generating insurance policies for insurance products,
A product information definition table including a product ID that is identification information assigned to specify an insurance product, a name of the insurance product, an insurance type, and a security ID that is identification information for specifying a security contract;
Information specifying the security ID, a security name associated with the security ID, a security type, a security ID attached to the security of a reference destination referred to by the security, and information specifying an element part of a contract word constituting the security A security information definition table including a security element component designation information ID which is information for identification;
The guarantee element component designation information ID, the document item number indicating the item number attached to the words constituting the contract, and the name assigned to the guarantee element component designation information are associated with the guarantee element component designation information ID. Information name, subordinate security element part designation information ID that is information for identifying information that designates a subordinate security element part that is further subordinate to one security element part designation information, and a unit of a contract word constituting each security element part A security element part designation information definition table including a security element part ID attached to identify
A security element part information definition table that includes the security element part ID, a security element part type that indicates the type of the security element part, and a clause statement that displays the contents of each security element part;
It is a term data ID that is identification information for identifying a term used in the clause text included in the guarantee element component, a term content that is a term of a term associated with the term data ID, and an abbreviation of the term In an information processing apparatus including a product data storage unit storing a term data definition table storing contract term data including abbreviation term data and term content supplement data that is a supplementary word for the term,
Using the received product ID as a key, the product data storage unit is further configured by the security ID, the security element component designation information ID, the dependent security component component designation information ID, and the security element component ID associated with the guarantee ID. The name of the insurance product, the insurance type, the security name associated therewith, the security type, the document item number indicating the item number attached to the words constituting the clause, and the security element component designation information A security element parts designation information name that is affixed, the security element part type, the terms of the agreement, and the term contents are extracted as at least product data;
A program for executing the step of converting the extracted product data into contract data in a display format defined in advance to generate contract data. The product data editing rule that defines the insurance type of the insurance product and the rules for arranging the product data extracted by the product data editing unit associated with the insurance product as a contract, and included in the product data The product data editing template definition table that stores the product data numbering rules that define the rules for assigning item numbers to the guaranteed element parts, and the extracted product data is converted into a format for display as a contract A template data storage unit for storing a clause data generation definition table that is format data to be
The insurance product type associated with the product ID is extracted from the product information definition table, the corresponding product data editing template is read from the template storage unit according to the insurance product type, and the read product data is The program according to claim 12, wherein a step of generating policy data for insurance products is executed.   If the terms of the agreement included in the referenced security element component are compared with the terms of the agreement included in the reference security element component, and if a different language is found between the two, a new security 14. The program according to claim 13, further comprising the step of generating an element part and new guarantee element part designation information referring to the element part. A method for generating an insurance policy for an insurance product, comprising:
A product information definition table including a product ID that is identification information assigned to specify an insurance product, a name of the insurance product, an insurance type, and a security ID that is identification information for specifying a security contract;
Information specifying the security ID, a security name associated with the security ID, a security type, a security ID attached to the security of a reference destination referred to by the security, and information specifying an element part of a contract word constituting the security A security information definition table including a security element component designation information ID which is information for identification;
The guarantee element component designation information ID, the document item number indicating the item number attached to the words constituting the contract, and the name assigned to the guarantee element component designation information are associated with the guarantee element component designation information ID. Information name, subordinate security element part designation information ID that is information for identifying information that designates a subordinate security element part that is further subordinate to one security element part designation information, and a unit of a contract word constituting each security element part A security element part designation information definition table including a security element part ID attached to identify
A security element part information definition table that includes the security element part ID, a security element part type that indicates the type of the security element part, and a clause statement that displays the contents of each security element part;
It is a term data ID that is identification information for identifying a term used in the clause text included in the guarantee element component, a term content that is a term of a term associated with the term data ID, and an abbreviation of the term Prepare a term data definition table that stores contract term data including abbreviated term data and term content supplement data that is a supplementary word for the term,
Using as a key a product ID that identifies an insurance product for which an insurance policy is to be generated, the security ID, the security element component designation information ID, the subordinate security element component designation information ID, and the security element that are associated therewith The product data storage unit is searched by part ID, and the document item number indicating the name of the insurance product, the insurance type, the security name associated therewith, the security type, and the item number attached to the words constituting the clause And at least extracting a security element part designation information name, which is a name given to the guarantee element part designation information, the security element part type, the terms of agreement, and the term contents,
A contract generation method, wherein the extracted product data is converted into contract data in a display format defined in advance to generate contract data.