JP5144340B2 - Contract content setting system and contract content setting method - Google Patents

Description

  The present invention relates to a contract content setting system and a contract content setting method.

  In companies, etc., the business control system executes the control of the setting of multiple business systems that perform various business operations and the transmission and reception of data between them according to a predetermined business process, so that the integrated operation as a whole can be achieved. Generally done. In such an integrated operation, an example in which the business control system also performs security management of each business system is known (for example, Patent Document 1).

In Patent Document 1, when a range of business systems to be secured is selected, and then a security policy to be observed by the selected business system is specified, the business control system sets / changes the security status of the business system in accordance with the security policy. Techniques to do this are disclosed.
Japanese Patent No. 3744361 (see paragraph 0011, FIG. 1)

In corporate activities, not only the intention of a single company but also the contents of contracts with other companies are reflected to define the contents of security policies and the like. Then, it is necessary to determine the contract contents in the contract negotiation process between the contracting parties and to set the determined contract contents in the business system quickly, accurately and consistently, rather than by manual work.
However, the technique of Patent Document 1 is based on the premise that the business system is set according to a given security policy, and the determination of contract contents in the contract negotiation process between contract parties is quick, accurate, and consistent. No technology is disclosed.

  Therefore, the present invention can determine the contract contents in the contract negotiation process between the contracting parties, and set the determined contract contents for the business system quickly, accurately and consistently, not manually. An object is to provide a contract content setting system and a contract content setting method.

The contract content setting system of the present invention includes a business device that is a target for setting information reflecting the content of an electronic contract document, and a contract support device that is a subject of the business device. The contract support device corresponds to a text template that is a template of an electronic contract, a setting template that indicates the correspondence between the contract contents to be set and the business device to be set, and information in which blank items in the text template are filled An electronic contract document describing a text template and contract status correspondence information for managing whether or not each contract party has agreed to the electronic contract document are stored.
The contract support apparatus refers to the contract status correspondence information, and if the agreement of all contract parties is confirmed, the contract support apparatus sets the contents of the electronic contract on the business apparatus based on the setting template.

  According to the present invention, the determination of the contract contents in the contract negotiation process between the contracting parties, and the setting of the determined contract contents for the business system can be performed quickly, accurately and consistently, not by manual work, A contract content setting system and a contract content setting method can be provided.

Hereinafter, the best mode for carrying out the present invention (hereinafter referred to as “the present embodiment”) will be described in detail with reference to the drawings.
An example will be described in which an organization A (consignment source) having a facility (library) to be maintained and consigned maintenance management of the facility after concluding a contract with an organization B (consignee).
The contract or electronic contract in this embodiment refers to a general document indicating that a matter between two or more parties has been agreed regardless of whether it is legally binding or not, and a memorandum, a memorandum, and service quality assurance. Including, but not limited to, contracts (SLA: Service Level Agreement), security level agreements, etc. In addition, it does not depend on a specific style or format, medium, applicable law, country, region, etc.

(overall structure)
FIG. 1 is an overall configuration diagram of the present embodiment.
The contract content setting system 100 includes a contract support apparatus 102 that supports a contract, a user management apparatus 103 that manages users who use the system, and various types of devices connected to each other via a network 101 under the management of an organization A. A DB (Database) device 104 that manages business data, a data transmission / reception device 105 that transmits / receives data to / from other organizations such as a consignee, a record management device 106 that manages various logs such as access records, The audit apparatus 107 that supervises whether or not the process is properly performed according to the contract, the progress management apparatus 108 that manages the progress of the business, and the business processing terminal apparatus 110 that performs the business processing in cooperation with these devices.
The “business device” corresponds to each device other than the contract support device 102. The “business processing device” corresponds to the business processing terminal devices 110 and 120. A “database device” corresponds to a DB device.

  Further, the data transmission / reception device 105 is further connected to the business processing terminal device 120 under the management of the organization B. The connection may be connected using a dedicated line, for example, or may be connected via the Internet. In the case of a dedicated line, there is a merit that risks such as eavesdropping can be reduced, and in the case of the Internet, there is an advantage that cost can be reduced. In addition, devices other than the data transmission / reception device 105 may be connected to an external network such as the Internet as necessary. For example, it is preferable that an information disclosure apparatus (not shown) is connected to the Internet because information can be widely disclosed outside the organization. When connected via the Internet, it is desirable to provide a mechanism for preventing unauthorized access via a network such as a firewall.

  In the present embodiment, the case where each of these devices is a physically different device is described as an example, but the functions of two or more of these devices are the same. May operate on the same device. When operating on the same device, there are advantages such as lower costs. In addition, when operating on different devices, there is an advantage that the range of damage can be limited even when a failure occurs. Further, in the present embodiment, the case where each device exists one by one has been described as an example. However, the present invention is not limited to this, and a plurality of devices may exist.

(Hardware configuration of the contract support apparatus 102)
FIG. 2 is a diagram illustrating an example of a hardware configuration and the like of the contract support apparatus 102 according to the present embodiment.
The contract support apparatus 102 includes a central control device (control unit) 201, a main storage device (storage unit) 202 that functions as a work area of the central control device 201, an external storage device (storage unit) 203 such as a hard disk device, A reader 204 that reads data from a portable storage medium 205 such as a CD-ROM or FD, an input device 206 such as a keyboard or a mouse, a display device 207 such as a display, and communicates with other devices via a network. It can be constructed by a general electronic computer provided with a communication device 208 for performing communication and an external interface 209 for managing data transmission / reception between the devices. When the operation of the contract support apparatus 102 is performed exclusively via the network, the display device 207 and the input device 206 may not be connected.

A contract template registration program 221, a contract content negotiation program 222, and a device setting program 223 are stored in the external storage device 203 of the contract support apparatus 102. These programs are loaded on the main storage device 202 and are realized by the central control device 201 as functions of a contract template registration processing unit 241, a contract content negotiation processing unit 242, and a device setting processing unit 243. A contract status management table 224 is also stored.
The “contract status correspondence information” corresponds to the contract status management table 224.

  Further, the external storage device 203 also stores a contract template 231 and an electronic contract document 234. The contract template 231 includes a text template 232 and a setting template 233. These will be described later.

  In the following description, each program is assumed to be stored in the external storage device 203 in advance. However, when necessary, other storage media such as an FD, a CD-ROM, a DVD-ROM, and a USB memory are used. Alternatively, it may be introduced into the external storage device 203 or the main storage device 202 via the external interface, such as via a network such as the Internet as a communication medium or a carrier wave propagating through the network.

  Further, in the description of the present embodiment, as shown in FIG. 2, an example is shown in which the functions of each device are realized as a software program on an electronic computer having a general configuration. The functions of one or more of the devices may be realized as a hardware device. In general, when implemented as a software program, there are merits such as low cost and easy modification, and when implemented as a hardware device, processing is fast and it is difficult to analyze fraud. There are benefits.

(Contract Certificate 301)
FIG. 3 is a diagram showing an example of the contract certificate 301 according to the present embodiment.
The contract certificate 301 is data created in step S910 to be described later, and the items to be selected or entered (blank or optional) included in the text template 232 of the contract template 231 are agreed to the official form. This data is created by replacing the contents defined in the electronic contract 234. The contract certificate 301 indicates the same contract contents as the electronic contract document 234 shown in FIG. 6, but compared with the electronic contract document 234, the contract contents as one data without referring to the contract template 231. Since it is completed, there is a merit that it is easy to use, so it may be used as needed. Alternatively, the contract certificate 301 printed or further stamped by the contracting party may be used as a paper formal electronic contract document.

Incidentally, the underlined portion in FIG. 3 is a portion that can change for each contract, and corresponds to the contents of the electronic contract 234 (described later) (reference numeral 604 in FIG. 6).
In the text template 232, the underlined portion is blank or an option, and when the contract is concluded, the contract support apparatus 102 accepts the selection of the created text template 232, and only the underlined portion of the text template 232 is the user. Accepts input (selection) from (details below).

(Contract template 231)
The contract template 231 shown in FIG. 2 is a concept including a text template 232 (FIG. 4) and a setting template 233 (FIG. 5). The contract template 231 is created assuming typical contract contents before an actual contract is concluded (can be created when a contract is made). Of the contract templates 231, the text template 232 is a model of a contract. The setting template 233 determines, for each text template 232, which item information of the text template 232 should be set for which business device that constitutes the system.
On the other hand, the electronic contract 234 (FIG. 6) described later is created for each contract, and for each item of the information for identifying the electronic contract, the information for identifying the corresponding text template 232, and the text template 232 Information that should be selected or filled in. That is, the contract contents are not clarified only by the text template 232 or the electronic contract document 234, but the contract contents are clarified by combining the text template 232 and the electronic contract document 234.

(Text template 232)
FIG. 4 is a diagram illustrating an example of the text template 232 according to the present embodiment.
The text template 232 is information for uniquely identifying the text template 232 <agreement_template_ID> 401, <type> 402 indicating the type of the text template 232, <title> 403 indicating the title of the contract certificate 301, and indicating the foreword part < This is an XML (eXtensible Markup Language) file including elements such as heading> 404 and <clause> 405 and <subclause> 406 indicating the contents of the contract clause.
The text template 232 further includes <input> 407 that is information for identifying items to be entered in order to complete an electronic contract based on the text template 232, and <option> that is information for identifying items to be selected. 408 etc. are included.
Further, <input> 407 and <option> 408 indicate, for example, a trustee name as information 409 for identifying each piece of information to be entered or selected for the item in order to complete these electronic contracts. Attributes such as <consignee> and <facility> indicating the facility name are assigned.
Note that the present invention can be similarly applied even to element names different from those of the present embodiment. In addition, even a file having a format different from that of the XML file can be similarly applied. For example, it may be a CSV (Comma Separated Values) format file or an entry to an external database (the same applies to the electronic contract 234 and the setting template 233 described later).

  In the present embodiment, the case where the contract template 231 is created by the contract support apparatus 102 is described as an example. Instead of creating the contract template 231 by the contract support apparatus 102 in step S401 (FIG. 8) described later, For example, the contract template 231 created in another apparatus may be transmitted to the contract support apparatus 102. In this way, there is a merit that a template can be created even if the apparatus is not connected to the network 101. In this case, for example, the created contract template may be transmitted to the contract support apparatus 102 when the apparatus is connected directly or indirectly to the network 101.

(Setting template 233)
FIG. 5 is a diagram illustrating an example of the setting template 233 according to the present embodiment.
The setting template 233 in this embodiment includes elements such as <agreement_template_ID> 501 that uniquely identifies the text template 232 to which the setting template 233 corresponds, and <config> 502 in which setting information for each device is described. It is an XML file that is configured to include. The <config> 502 further includes elements <device> 503 for specifying a business device for which information is to be set, and <param> 504 for indicating a setting parameter to be transmitted to the business device. Has been. In addition, when describing <param> 504, information 505 described when the contract is completed may be designated using the attribute assigned in the sentence template 232, or other than that, It is also possible to specify setting information unique to the device.
For example, the example shown in FIG. 5 indicates that the information 505 of <report_period>, <consignee>, and <report_item> specified in the text template 232 is used as setting information for the progress management device 108. As setting information for the DB device 104, it is indicated that a character string 505 “read” meaning read authority and information 505 of <consignee> and <information> specified by the text template 232 are used. In this example, “read” corresponds to setting information unique to the DB device 104 that is independent of data to be entered in order to complete the contract specified by the text template 232.
The “information for identifying information including the contract partner selected or filled in for the item” corresponds to each information 505 such as <report_period>, <consignee>, <report_item>, and the like described here.

(Electronic contract 234)
FIG. 6 is a diagram illustrating an example of the electronic contract 234 in the present embodiment.
The electronic contract 234 is information <agreement_content_ID> 601 that uniquely identifies the electronic contract, information <agreement_template_ID> 602 that identifies the text template 232 on which the electronic contract 234 is based, The XML file is configured to include an element <filled> 603 that is information for identifying information entered or selected for an item to be filled or selected. There may be a plurality of <filled> 603 corresponding to the attribute of the item to be filled or selected. Then, as the value of <filled> 603, the information 604 itself including the contract partner entered or selected for the item to be entered or selected (“XX company” “library” “1” “2” “1, 2, 3 and 4 ”and“ number of unreturned books ”are set.

  Further, in this embodiment, the information shown in FIG. 6 is treated as an electronic contract draft in step S905 (FIG. 9), and when the consent of each organization is confirmed in step S908, the formal electronic contract is confirmed. The case where it is handled as a book is described as an example. However, unlike this, a draft electronic contract and a formal electronic contract may be used as different data. For example, in addition to the elements shown, there is an element called <conclusion> that identifies whether the data is an electronic contract draft or a formal electronic contract, and if the value is `` yes '' It is an official electronic contract, and if it is “no”, it may be treated as an electronic contract draft (not shown).

(Correspondence between text template 232, setting template 233, and electronic contract 234)
One text template 232 for creating the electronic contract 234 is determined for one electronic contract 234. For one sentence template 232, there are a plurality of electronic contracts 234 created using the sentence template 232.
The sentence template 232 and the setting template 233 have a one-to-one correspondence.
Therefore, one setting template 233 for setting the contents of the electronic contract 234 in each apparatus is determined for one electronic contract 234. For one setting template 233, there are a plurality of electronic contracts 234 whose contents are set in each device by the setting template 233. That is, the contract template 231 is repeatedly used for a plurality of electronic contract documents.

In the present embodiment, information for identifying the contract template 231 is used as information for identifying the text template 232 (<agreement in FIGS. 4, 5, and 6).
_template_ID> 401, 501, 602). This is because the contract template 231 and the text template 232 have a one-to-one relationship. However, unlike this, unique identification information may be assigned to each of the contract template 231 and the text template 232. In this case, the contract support apparatus 102 needs to store the correspondence between the information for identifying the contract template 231 and the information for identifying the text template 232.

(Contract status management table 224)
FIG. 7 is a diagram showing an example of the contract status management table 224 according to the present embodiment.
The contract status management table 224 is a data table that stores the agreement status of contract parties for each contract.
In association with the text template ID stored in the text template ID column 701, the electronic contract ID column 702 has an electronic contract ID, the consignee column 703 has a consignee, and the consignor agreement column 704 has a consignor agreement. Information is stored in the consignee agreement column 705, respectively.

The text template ID in the text template ID column 701 is information for identifying the text template 232 (values of elements <agreement_template_ID> 401, 501 and 602 in FIGS. 4, 5 and 6).
The electronic contract ID in the electronic contract ID column 702 is information for identifying the electronic contract 234 (value of element <agreement_content_ID> 601 in FIG. 5).
The consignee information in the consignee column 704 is information such as a character string indicating the consignee in FIG. 1, and is input as <input attribute = consignee> of the text template 232 (in the “information for identifying the contract partner”). Equivalent).
The consignment source agreement information in the consignment source agreement column 704 is information such as a character string indicating whether or not the consignment source in FIG. 1 has agreed to the contents of the electronic contract 234 identified by the electronic contract ID. Then, it is assumed that either the character string “Agreement” or “Unagreement” is stored.
The consignee agreement information in the consignee agreement column 705 is information such as a character string indicating whether or not the consignee in FIG. 1 has agreed to the contents of the electronic contract identified by the electronic contract ID. It is assumed that either the character string “Agreement” or “Unagreement” is stored.
The “agreement information” corresponds to consignment source agreement information and consignment destination agreement information.

  There are as many records (rows) in the contract status management table 224 as the number of electronic contracts 234 (that is, the number of electronic contract IDs). If the electronic contract ID is determined as one, the corresponding text template ID is determined as one, and the consignee information is also determined as one. If the contract ID is determined to be one, the combination of the trustee agreement information and the trustee agreement information at that time is determined to be one. “At that time” means that the contractor agreement information and the trustee agreement information change during the contract negotiation process between the trustee and the trustee, and the latest information is overwritten and stored (details) (Postscript).

(Overall procedure)
Hereinafter, a processing procedure according to the present embodiment will be described.
The processing procedure is roughly divided into (1) a contract template registration processing procedure realized by the template registration processing unit 241, (2) a contract content negotiation processing procedure realized by the contract content negotiation processing unit 242, and (3) an apparatus. There are three device setting processing procedures realized by each device that communicates with the setting processing unit 243 and the contract support device 102.
To execute (2), it is assumed that (1) has been completed. To execute (3), it is assumed that (2) has been completed. (1), (2), and (3) need not be executed sequentially in that order. (1) is executed for each contract template to be created. (2) and (3) are executed for each electronic contract 234.

(Contract template registration process)
FIG. 8 is a flowchart of a contract template registration process procedure according to this embodiment.
In step S401, the template registration processing unit 241 creates a contract template 231.
Specifically, the template registration processing unit 241 receives a contract template 231 created by the user via the input device 206 of the contract support apparatus 102. Alternatively, the already created contract template 231 is received from the storage medium 205 storing the contract template 231 via the reading device 204. Alternatively, the already created contract template 231 is received from the network via the communication device 208.
At this time, the text template 232 and the setting template 232 constituting the contract template 231 have the same contract template ID (<agreement in FIGS. 4 and 5).
_template_ID> 401, 501) is stored.

  In step S402, the template registration processing unit 241 registers the contract template 231. Specifically, the template registration processing unit 241 stores the contract template 231 received in step S401 in the external storage device 203 of the contract support apparatus 102. Thereafter, the processing procedure ends.

(Variation 1 of the contract template registration process procedure)
In the description of the present embodiment, the case where the contract support apparatus 102 of the organization A that is the contracting party creates the contract template 231 is described as an example, but for example, the contract template 231 that can be used by the organization A is different. You may make it create on behalf of the organization. In this way, for the organization A, there is an advantage that the trouble of creating the contract template 231 is reduced. In addition, it is expected that errors or the like that can be included in the contract template 231 can be reduced by the creation of another organization that specially creates the contract template 231.

(Modification 2 of the contract template registration process procedure)
A contract template 231 that can be commonly used for each type of industry may be created by an industry group in a lump and distributed to related companies for use. For example, a contract template 231 that can be commonly used by local governments may be used. It may be created by a wide-area federated organization and used by each local government. In this way, by using one contract template 231 in common for a plurality of organizations, organizations, etc., the labor involved in creating the contract template 231 is reduced as a whole, and the contract quality and security within the industry and between local governments are reduced. There are advantages such as being able to align the setting level.

(Modification 3 of the contract template registration processing procedure)
In addition, when a person or organization different from the organization A as a contracting party as exemplified above creates the contract template 231, it is desirable that the authenticity of the contract template 231 can be confirmed.
Specifically, for example, the creator may give a digital signature (digital signature) to the created contract template 231 and then provide it to the contract template user.
Alternatively, a contract template user can access a website that can be authenticated by SSL (Secure Socket Layer), TLS (Transport Layer Security), etc., and the contract template 231 can be downloaded from the website. Just keep it.

There may be a case where it is preferable to use the contract template 231 created by the creator after a third party different from the creator or the user has confirmed the validity. In such a case, in place of the digital signature of the creator, or in addition to the digital signature of the creator, a digital signature of a third party whose contents have been confirmed is also given to the contract template user. That's fine.
Alternatively, when using the above-described site authentication function, a third party who confirms the contents of the contract template 231 may be set up by the website. Before actually using the contract template user, for example, the digital signature attached to the contract template 231 is verified, or the Web site of the download source is confirmed with the site certificate (public key certificate of the Web site), After confirming the authenticity of the contract template 231, it may be registered in the contract support apparatus 102.

(Modification 4 of the contract template registration process procedure)
In the description of the present embodiment, the case where each contract template 231 is created individually is described as an example. For example, based on one contract template 231, necessary information is added, Alternatively, unnecessary information may be deleted and another contract template 231 may be derived. In this case, since the derived contract template 231 can be configured as long as there is the original contract template 231 and information defining the difference from the original contract template 231, for example, from one contract template 231, a plurality of contract templates can be configured. When 231 is derived, there is an advantage that information to be managed as a whole can be reduced. The contract template 231 to be derived may be only the text contract template 231 among those constituting the contract template 231, only the set contract template 231, or both of them.

  Such a configuration method of the contract template 231 is particularly effective when one contract template 231 is shared by a plurality of companies, a plurality of local governments, and the like. For example, on the basis of a contract template 231 common to local governments created by a wide-area federation organization, each local government adds or deletes, for example, a provision for dealing with regulations specific to the local government, It is possible to add or delete configuration information to correspond to a device unique to the information system.

  Furthermore, the derivation of the contract template 231 may be performed hierarchically over a plurality of stages. For example, based on a contract template 231 common to all industries, a contract template 231 customized according to individual circumstances of each industry is derived, and further, a contract template 231 customized according to individual circumstances of each company is derived therefrom. You may use it.

(Variation 5 of the contract template registration processing procedure)
Even when the contract template 231 is derived in this way, it is desirable to be able to confirm the authenticity of the original contract template 231 and the difference information created when deriving. For that purpose, for example, the original contract template 231 or the difference information may be given a digital signature of each creator or a person or device responsible for the contents instead.
In this case, for example, Japanese Patent Application Laid-Open No. 2005-051734 (U.S. Patent Application No. 10 / 787,262) “Electronic Document Authenticity Guarantee Method and Electronic Document Publishing System” discloses an electronic document after a signature is added If the signature is given in accordance with the digital signature method that can be deleted, even if some information is deleted during the derivation of the contract template 231, the authenticity of the remaining portion can be confirmed. Therefore, it is more preferable. In addition, when a signature is given in accordance with a digital signature method different from this, even if the text is deleted when the contract template 231 is derived, the information of the original contract template 231 is not actually deleted. If the difference information indicates that the clause is regarded as deleted, the contract template user can confirm the authenticity of the contract template 231.

(Contract negotiation process)
FIG. 9 is a flowchart of the contract content negotiation processing procedure according to the present embodiment.
In the processing procedure, the contract support device 102 of the organization A, the business processing terminal device 110 of the organization A, and the business processing terminal device 120 of the organization B are based on an instruction from the contract content negotiation processing unit 242 of the contract support device 102. Information is transmitted and received between these devices. Further, the contract support apparatus 102 creates, updates, and stores a record of the contract status management table 224 as the processing procedure proceeds.

In step S <b> 901, the business processing terminal device 110 receives a list of sentence templates 232.
Specifically, the contract support apparatus 102 reads all the text templates 232 from the external storage device 203, transmits them to the business processing terminal apparatus 110 in the form of a list, and the business processing terminal apparatus 110 receives the list. To do. In this list, it is assumed that the contract template ID is described in association with the approximate contents (for example, <type>) of the contract template.

In step S <b> 902, the business processing terminal device 110 selects and notifies the text template 232.
Specifically, one of the text templates 232 described in the list received in step S901 is selected, and the selection result (contract template ID) is notified to the contract support apparatus 102.
Next, the contract support apparatus 102 creates a new record in the contract status management table 224 and stores the contract template ID for which the notification has been received in the text template ID column 701.

In step S <b> 903, the contract support apparatus 102 transmits the selected sentence template 232.
Specifically, the contract support apparatus 102 searches the external storage device 203 using the selection result (contract template ID) notified in step S902 as a search key, and searches the corresponding text template 232 for the business processing terminal apparatus 110. Send to.

In step S <b> 904, the business processing terminal device 110 fills the items and transmits them as an electronic contract draft.
Specifically, the business processing terminal device 110 displays the text template 232 transmitted in step S903 on the screen (browser), and the user can use the displayed text template 232 for the item of the element <input> 407. The electronic contract draft is accepted by accepting the user's selection from the choices (<item no = 1>, <item no = 1>, ...) for the item of the element <option> 408. And the electronic contract draft is transmitted to the contract support apparatus 102.
Next, the contract support apparatus 102 stores the contract template ID transmitted as the selection result in step S903 in the electronic contract draft.
Further, the contract support apparatus 102 transmits the element <filed_attribute of the electronic contract draft that has been transmitted.
The value of _consignee> is read and stored in the main storage device 202 as consignee information. Also, the electronic contract ID is numbered and temporarily held in the main storage device 202.
As described above, the electronic contract draft is the same as the electronic contract 234 in FIG. 6, but an electronic contract that has not been agreed upon by all the contracting parties is particularly distinguished as an “electronic contract draft” (reference number is The same 234).

In step S905, the contract support apparatus 102 transmits the electronic contract draft 234 to the contracting party.
Specifically, the electronic contract draft 234 and the text template 232 selected in step S902 are transmitted to the business processing terminal device 120 of the consignee (in this case, organization B) indicated by the consignee information held in step S904. Then, the electronic contract draft 234 is transmitted to the business processing terminal device 110.
Next, the contract support apparatus 102 stores the electronic contract ID and the entrustee temporarily held in step S904 in the electronic contract ID column 702 and the entrustee column 703 of the record of the contract status management table 224 created in step S902, respectively. The information is stored, “not agreed” is stored in the consignment source agreement column 704 and the consignee agreement column 705, and the record is updated.

In steps S <b> 906 a and S <b> 906 b, the business processing terminal device 110 and the business processing terminal device 120 separately notify whether or not they agree with the electronic contract draft 234.
Specifically, in the organization A, the business processing terminal device 110 transmits information indicating the user's judgment as to whether or not to agree on the contents of the electronic contract draft 234 transmitted in step S 905 to the contract support device 102. The information is, for example, “agreed” or “not agreed”. The same applies to the organization B.

In step S907, the contract support apparatus 102 determines whether both notification contents are “agreement”.
Specifically, first, the contract support apparatus 102 determines that the business processing terminal apparatus 110 of the organization A in step S906a has compared the consignment source agreement column 704 of the record in the contract status management table 224 updated in step S905. The transmitted information (“agreement” or “unagreement”) is overwritten as the outsourcer agreement information, and similarly, the information transmitted by the business processing terminal device 120 of the organization B in step S906b to the outsourcer agreement column 705. Overwrite as consignee agreement information and update the record.
Second, when the updated record is referred to and both the consignment source agreement information and the consignment destination agreement information are information indicating “agree” (step S907 “Yes”; corresponding to “first case”) Advances to step S909. In other cases (step S907 “No”; “corresponding to the second case”), the process proceeds to step S908.

  In step S908, the contract support apparatus 102 notifies the business processing terminal apparatus 110 that the contract cannot be made. Then, the process returns to step S902.

In step S909, the contract support apparatus 102 sets the electronic contract draft 234 as a formal electronic contract 234.
Specifically, the electronic contract ID 234 assigned in step S904 is attached to the created electronic contract 234, and the electronic contract 234 is stored in the external storage device 203.

In step S <b> 910, the contract support apparatus 102 creates a contract certificate 301.
Specifically, the contract certificate 301 is created based on the electronic contract draft 234 transmitted in step S905. This step can be omitted. Thereafter, the processing procedure ends.
The “contract negotiation process procedure” corresponds to steps S901 to S907 (up to “first”) of the contract content negotiation process.
Steps S901 to S910 of the processing procedure are not always continuous in time. In particular, there is a possibility that a reception waiting interval (user examination time) may be left immediately after S901, immediately after S903, and immediately after S905. In this case, the contract support apparatus 102 memorizes how far the processing procedure has progressed, and then temporarily puts the processing procedure into a waiting state. When the next information is received, the subsequent steps are resumed. Further, the contract support apparatus 102 stores the electronic contract draft 234 and the contract state management table 224 that are being created in the external storage device 203 in the waiting state.

(Modification 1 of contract content negotiation process)
In this embodiment, in step S905, the contract support apparatus 102 transmits the electronic contract draft 234 to the business processing terminal apparatus 110 of the organization A. However, unlike this, the business processing terminal in step S904. The electronic contract draft 234 created by the apparatus 110 may be stored in the business processing terminal apparatus 110 and used in the subsequent steps.

(Modification 2 of the contract content negotiation process)
In the present embodiment, in step S906a, the business processing terminal device 110 of the organization A also transmits information indicating whether or not the contents indicated in the electronic contract draft 234 are agreed to the contract support device 102. However, it is also possible that the contract support apparatus 102 agrees to the contents when the contract support apparatus 102 sends the electronic contract draft to the business processing terminal apparatus 110 in step S905.

(Variation 3 of the contract content negotiation process)
In the present embodiment, in the case where the electronic contract draft 234 has not reached an agreement in step S907, an example has been described in which the process returns to step S902 and starts again from the selection of the contract template 231. Differently, the process may return to step S904 and start again from the entry of items to be entered or selected.

(Modification 4 of contract content negotiation process)
In the present embodiment, there is no particular limitation on the number of redoes (the number of times to return to step S902 or S904 via “No” in step S907), but the number of redoes (“the number of times the contract negotiation processing procedure is repeated”). May be limited. In this case, for example, in the contract status management table 224 shown in FIG. 7, a column for holding the number of redoes is provided, and the count is incremented each time redoing, and when it exceeds a certain number, The contract content negotiation process procedure may be terminated.
Similarly, there is a limitation on the date and time, not the number of times, and if the agreement by all contracting parties has not been reached by the specified time, the contract content negotiation process procedure may be terminated. .

(Variation 5 of the contract content negotiation process)
In the present embodiment, the business processing terminal devices 110 and 120 of the organization A and the organization B have shown an example of selecting only whether or not to agree with the electronic contract draft 234. In some cases, conditions for agreement may be further indicated.
For example, if the electronic contract draft 234 whose business report is submitted every month cannot be agreed, but can be agreed if it is submitted every period, the information transmitted in steps S906a and S906b is simply “not agreed”. Instead of “not agreed” (can be agreed if the frequency of submission of business reports is submitted every period). The contract support apparatus 102 that has received the request transmits the conditions for the agreement to the business processing terminal device 110 (120) of the other contract party, and may inquire whether or not to agree again.

(Modification 6 of the contract content negotiation process)
Further, in the present embodiment, the case where the business processing terminal device 110 of the organization A that is the consignment source creates the electronic contract draft 234 is described as an example, but the business processing terminal of the organization B that is the consignment destination The device 120 may create the electronic contract draft 234, or both the business processing terminal devices 110 and 120 may create the electronic contract draft 234, respectively.
In this case, for example, after selecting the contract template 231 to be used by the business processing terminal device 110 of the organization A in step S902, in step S903, the contract support device 102 not only includes the business processing terminal device 110 of the organization A but also the organization The contract template may be sent to the business processing terminal device 120 of B, and the process of step S904 may be performed by both the organizations A and B. It is assumed that the electronic contract draft 234 of the own organization has been agreed upon when the electronic contract draft 234 is transmitted. In steps S906a and S906b, the business processing terminal device 110 of the organization A uses the electronic contract draft of the organization B. The business processing terminal device 120 of the organization B sends information indicating whether or not to agree to the document draft 234 to the contract support device 102. Send it.

Here, the agreement information of each organization is stored in the contract status management table 224 shown in FIG. 7 in the agreement column of the other organization for the electronic contract draft 234 of the own organization and the agreement column of the own organization for the electronic contract draft 234 of the other organization. And record it there. If both parties agree on the electronic contract draft 234 of only one of the organization A and the organization B, the electronic contract draft 234 may be used as the formal electronic contract draft 234. In contrast, if both parties agree, one of the electronic contract drafts 234 may be a formal electronic contract 234.
Here, which one is the formal electronic contract 234 may be defined in the text template 232 by setting priorities for each item in advance. For example, the priority may be determined such that priority is given to a report item (report_item) having a higher priority, priority is given to a report frequency (report_period), or the like. If neither agreement is obtained for either electronic contract draft 234, for example, the process may return to step S902 or may return to step S904.

(Variation 7 of the contract content negotiation process)
Further, in the present embodiment, an example is shown in which the electronic contract draft 234 is transmitted to the entrustee indicated in the electronic contract draft 234 in step S905, but unlike this, the entrustee in the contract support apparatus 102 in advance. The candidate list may be managed, and the electronic contract draft 234 may be transmitted to one or a plurality of consignee candidates selected from the list (corresponding to “contract partner candidates”). In this case, when the sentence template 232 is filled in step S904, the consignee name need not be described. By sending it to a plurality of consignee candidates, there is a merit that the possibility of the contract content negotiation processing procedure being terminated halfway can be reduced.

(Modification 8 of contract content negotiation process)
In the present embodiment, the case of a contract between two organizations has been described as an example, but more generally, the case of a contract between three or more organizations can be similarly applied.

(Modification 9 of the contract content negotiation process)
As the information transmitted in steps S906a and S906b of the present embodiment and indicating whether or not to agree, a digital signature of the agreed entity may be added. This is preferable from the viewpoint of security, because it becomes possible to confirm later whether or not the information indicating whether or not the agreement has been made.
Furthermore, when it is considered that the creator (in this case, organization A) of the electronic contract draft 234 agrees when the electronic contract draft 234 is transmitted in step S904 as described above, The electronic contract draft 234 may be given the signature of the organization A, and if the organization B as the other contracting party agrees with the electronic contract draft 234 in step S906b, information indicating the agreement As an alternative, the electronic contract draft 234 or the electronic contract draft 234 signed by the organization A may be given the signature of the organization B.
This is not only preferable from the viewpoint of security because tampering detection is possible, and furthermore, both parties as contracting parties give digital signatures to the electronic contract draft 234 agreed upon by both parties. Therefore, there is an advantage that this can be used as a formal electronic contract 234.

(Device setting processing procedure)
FIG. 10 is a flowchart of a device setting process procedure according to the present embodiment.
In step S <b> 1001, the device setting processing unit 243 acquires the setting template 233.
Specifically, in the apparatus setting processing unit 243, first, both the consignment source agreement column 704 and the consignee agreement column 705 are “agreement” in the records of the contract status management table 224 from the external storage device 203. The contract template ID stored in the text template ID column 701 of the record (agreement record) and the electronic contract ID stored in the electronic contract ID column 702 are acquired (there may be a plurality of target records). .
Next, using the acquired contract template ID as a search key, the external storage device 203 is searched to acquire the corresponding setting template 233.

In step S1002, the device setting processing unit 243 acquires information to be set for each device.
Specifically, the device setting processing unit 243 acquires the value of the element <device> 503 and the value of the element <param> 504 described in the element <config> 502 of the setting template 233 acquired in step S1001. To do.
Next, the external storage device 203 is searched using the electronic contract ID acquired in step S1001 as a search key, and the corresponding electronic contract 234 is acquired.
Furthermore, information 604 including the contract partner entered or selected for the item corresponding to the value 505 of element <param> 504 (<report_period>, <consignee>, <report_item>, etc. in FIG. 5) is electronically contracted. Obtained from the element <filed> 603 of the document 234.

In step S1003, the device setting processing unit 243 transmits information to be set to each device.
Specifically, the device setting processing unit 243 transmits the information 604 of the electronic contract document 234 acquired in step S1002 to the business device identified by the value of the element <device> 503 acquired in step S1002. .
Thereafter, the processing procedure ends.

  The processing procedure of step S1002 is repeated for all devices (business devices identified by the value of element <device> 503) for which information is to be set. Furthermore, the processing procedure of steps S1001 to S1003 is repeated for all the agreement records.

(Specific setting example 1)
As specific setting contents, for example, the device setting processing unit 243 should report to the progress management device 108 <report_period> indicating the report frequency defined in the contract, <consignee> indicating the consignee, and so on. Send <report_item> etc. indicating the item and set that a certain consignee specified by <consignee> needs to report the item specified by <report_item> at the frequency specified by <report_period> What should I do? The set progress management device 108 transmits, to the business processing terminal devices 110 and 120, for example, a report that prompts the user to report what items should be reported by when the reporting deadline is approaching or the deadline has passed. May be.

(Specific setting example 2)
The device setting processing unit 243 transmits, to the DB device 104, “read” indicating that read authority is given, <consignee> indicating a consignee, <information> indicating the type of information provided by the contractor, and the like. , For the DB device 104, the contract partner specified by <consignee> is set so that reading authority is given to the item specified by <information> in the data held by the DB device 104 do it.

(Specific setting example 3)
The device setting processing unit 243 transmits <consignee> indicating a contract destination to the user management device 103, and additionally registers the contract destination specified by <consignee> as one user of the system of the organization A. It may be set.

(Specific setting example 4)
The device setting processing unit 243 transmits <consignee> indicating the contract destination to the recording management device 106 and the data transmitting / receiving device 105, and determines all or all of the information exchanged between the organization A and the organization B. It may be set to record those satisfying the specified conditions. Similarly, the recording management device 106 and the DB device 104 may be set so as to record all access records from the consignees to the DB device 104 or those satisfying a predetermined condition.

Specific data to be recorded includes, for example, one or more of time, sender, receiver, access source, access destination, transmission or reception type, exchanged information itself, or its hash value. Combinations may be included. In addition, in order to be able to confirm later that various records have not been changed or altered while being stored in the record management device 106, the record management device 106 can digitally record the various records. You may make it store after giving a signature.
Furthermore, when the digital signature disclosed in Japanese Patent No. 3899808 “Digital Signature Generation Method and Digital Signature Verification Method” is added, the signature private key is compromised during the storage period. Can show the authenticity and non-tampering of the record with high reliability, and shows the temporal order relationship between each record and various reports related to the record. It is preferable because it has advantages such as

(Specific setting example 5)
Information regarding the access authority transmitted to the DB device 104 may be transmitted to the audit device 107 so as to confirm whether or not the access to the DB device 104 from the entrustee is appropriate. In this case, the set auditing device 107 compares, for example, the access record for the DB device 104 from the consignee recorded in the record management device 106 with the information regarding the access authority for the DB device 104 transmitted from the contract support device 102. Then, it is only necessary to confirm whether or not there is an access that deviates from the conditions (for example, the user has only been given the read right but has written or attempted to do so).
When a digital signature is given to a record stored in the record management apparatus 106, the audit apparatus 107 may use the digital signature after confirming the authenticity of the digital signature.

  Generally, in business consignment, a consignor has the right to audit and supervise and is often obligated to a consignee. In such a case, if the electronic contract 234 that has been concluded or other explicit or implicit conditions are stipulated, the scope to be checked by the auditing apparatus 107 of the organization A is the organization A that is the consignment source. In addition to the processing in each device, the status of processing in each device of the organization B, which is the outsourcer, may be confirmed.

Specifically, for example, a contract that “When organization B accesses personal information in a commissioned business, keep a record of the access for one year and promptly provide it when requested by organization A”. When the electronic contract 234 including the clause is concluded, the auditing apparatus 107 accesses the organization B periodically or irregularly (this frequency may be determined by the setting template 233, for example). Whether the submission of records is requested and the contents do not deviate from the conditions stipulated in the electronic contract 234 (personal information may be accessed only if it has been notified to Organization A in advance) Check it.
Or, an electronic document that includes a contractual clause that says “Organization B shall send and receive information to and from Organization A for one year and provide it promptly upon request from Organization A”. When the contract 234 is concluded, the auditing device 107 requests the organization B to submit a transmission / reception record periodically or irregularly, and is consistent with the data recorded in the record management device 106 of the organization A. What is necessary is just to confirm whether it is.

  FIG. 11 shows a processing procedure for confirming whether or not the transmission / reception record recorded by the organization A and the transmission / reception record recorded by the organization B match in the auditing apparatus 107 according to the present embodiment. It is a flowchart.

In step S1101, the auditing apparatus 107 receives the transmission / reception record of the organization A.
Specifically, the auditing device 107 first requests the recording management device 106 to record data transmitted to and received from the organization B.
Second, the transmission / reception record of the organization A is received from the record management device 106.

In step S1102, the auditing apparatus 107 receives the transmission / reception record of the organization B.
Specifically, first, the auditing device 107 requests the business processing terminal device 120 of the organization B to record data transmitted to and received from the organization A.
Second, the transmission / reception record of the organization B is received from the business processing terminal device 120.

In step S1103, the auditing apparatus 107 confirms the consistency of transmission / reception records.
Specifically, the auditing apparatus 107 has a record of “reception” or “transmission” regarding the data corresponding to a record of “transmission” or “reception” regarding certain data present in the transmission / reception record of the organization A. It is confirmed whether or not it exists in the transmission / reception record of the organization B.

In step S1104, the auditing apparatus 107 notifies the audit result.
Specifically, the auditing apparatus 107 notifies the confirmation result of step S1103 to the business processing terminal apparatus 110 as an audit result. When there is a discrepancy between the transmission / reception record of organization A and the transmission / reception record of organization B, the transmission / reception record is also notified as a concern. If there are no inconsistencies, this is also notified. The processing procedure is thus completed.
Note that the processing procedure of steps S1101 to S1104 is such that a central control device (not shown) of the audit device 107 audits a program (not shown) stored in an auxiliary storage device (not shown) of the audit device 107. It is assumed that the program is loaded into a main storage device (not shown) of the device 107 and executed.

  In the above-described processing procedure, an example in which the transmission / reception record of the organization B is received from the business processing terminal device 120 of the organization B in step S1102 is shown. In the case where it is provided, the record management apparatus may transmit it to the audit apparatus 107 of the organization A.

  Alternatively, the auditing device 107 may refer to the access record recorded in the record management device 106 and confirm whether there is a record different from the normal access. Specifically, for example, access to certain data usually occurs only between 9:00 am and 5:00 pm on weekdays, but if there is a record accessed at midnight on a holiday, the record is different from normal There will be. In order to discriminate access different from normal, for example, conditions that are permitted as normal access (for example, access from 9 am to 5 pm on weekdays is permitted as normal access) are set in advance. 107 may be set, or a statistical amount such as an average value or a variance value is calculated from a feature amount (eg, access time) of an access record recorded in the record management device 106, and is equal to or greater than an allowable error (threshold value). Data having a deviation (difference) may be extracted as an abnormal value. These discriminating conditions and discriminating logic may be determined by, for example, a setting template, or may be explicitly shown as contract conditions in the text template. If it is shown in the text template, the validity of the discriminating conditions and discriminating logic is preferable because it is agreed between the contracting parties, and it is determined independently from the text template, for example, only by the setting template. In such a case, the determination conditions and the like can be changed without changing the contract itself, which is excellent in that the accuracy of detecting an abnormal value can be improved by appropriate optimization.

  In addition, if any questionable points are found as a result of these confirmations, for example, the manager in charge of organization A may be notified, and further consistency with other records etc. may be confirmed. You may make it do. For example, when an access record at midnight on a holiday is detected as an abnormal value as in the above example, the cause is (1) unauthorized access by an internal unauthorized person (an unauthorized person who is a legitimate user). (2) Unauthorized access by external (or other internal) unauthorized persons pretending to be regular users, (3) Regular work (overtime) by regular users, etc. In this case, it is preferable that the auditing device 107 further confirms the possibility of (3) by referring to the record of the attendance / leaving / recording device (not shown). In addition, it is preferable to record the series of auditing actions as described above in the record management device 106 in order to show the validity and validity of the audit.

  In the description of the present embodiment, only the business processing terminal device 120 is shown as a device managed by the organization B that is a consignee. Other devices may be provided. When such a configuration is provided, when the contract is concluded, the setting of the device group of the organization B is also in an appropriate state consistent with the contract content, which is preferable. In this case, the same contract template 231 may be shared between the organization A and the organization B, and when the system configurations of the organization A and the organization B are different, the sentence template 232 portion is shared and associated therewith. The setting template 233 may be created for each organization.

In the description of the present embodiment, the case where each device such as the contract support device 102 is a device of the organization A that is a consignment source has been described as an example. It may be a device managed by an organization C (IT outsourcing company, etc.) different from the organization A or organization B, and the organization C manages devices (groups) of a plurality of organizations including those other than the organization A. It may be.
For example, among the devices in the organization A shown in FIG. 1, the business processing terminal device 110 may be directly managed by the organization A itself, and the other devices may be managed by the organization C. Even in such a case, the intention display for the electronic contract draft 234 may be performed by the organization A itself using, for example, the business processing terminal device 110. With such a configuration, the organization A can obtain merits such as reducing the effort for managing the apparatus while appropriately fulfilling the intention expression and management obligations necessary as a contracting party.

  In the description of the present embodiment, the case where the texts of the text template 232, the setting template 233, and the electronic contract 233 are text data described in a natural language has been described as an example. For example, text, numerical value, figure, sound, video (still image, moving picture, etc.), design drawing, map, form, statistical data, biological information, chemical formula (composition formula, structural formula, etc.), table, calculation formula It may be a sentence composed of computer program code or the like.

It is a whole block diagram of this embodiment. It is a figure which shows an example of the hardware constitutions etc. of the contract assistance apparatus which concerns on this embodiment. It is a figure which shows an example of the contract certificate which concerns on this embodiment. It is a figure which shows an example of the text template which concerns on this embodiment. It is a figure which shows an example of the setting template which concerns on this embodiment. It is a figure which shows an example of the electronic contract based on this embodiment. It is a figure which shows an example of the contract status management table which concerns on this embodiment. It is a flowchart of the contract template registration processing procedure which concerns on this embodiment. It is a flowchart of the contract content negotiation processing procedure which concerns on this embodiment. It is a flowchart of the apparatus setting process sequence which concerns on this embodiment. 5 is a flowchart of a processing procedure for confirming whether or not the transmission / reception record recorded by the organization A and the transmission / reception record recorded by the organization B are consistent in the auditing apparatus according to the present embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Contract content setting system 101 Network 102 Contract support apparatus 103 User management apparatus 104 DB apparatus 105 Data transmission / reception apparatus 106 Recording management apparatus 107 Auditing apparatus 108 Progress management apparatus 110,120 Business processing terminal apparatus (business processing apparatus)
201 Central control unit (control unit)
202 Main storage device (storage unit)
203 External storage device (storage unit)
224 Contract status management table 231 Contract template 232 Text template 233 Setting template 234 Electronic contract, electronic contract draft 301 Contract certificate 401, 501, 602 Contract template ID
601 Electronic contract ID

Claims (15)

A contract content setting system configured to reflect the content of a contract for devices in multiple organizations that are contract parties,
The contract content setting system includes:
One or a plurality of business devices to be set in the plurality of organizations and a contract support device that confirms that all the contracting parties have agreed to the contract and instructs the setting,
The contract support apparatus includes:
Information for identifying a text template that is a model of an electronic contract in association with information for identifying an electronic contract, information for identifying a contract partner other than the contract creator of the contract, and each contract party Contract status correspondence information storing agreement information indicating whether or not has agreed to an electronic contract,
Information identifying the text template, information indicating the contents of the contract terms, information identifying items to be selected or filled in on the text template to complete the electronic contract, and contracts selected or filled in for the items A text template with information identifying the information including the other party,
A setting template in which information for identifying the text template, information for identifying a business device to be set, and information for identifying information including a contract partner selected or filled in for the item,
Including information identifying the electronic contract, information identifying the text template, information identifying information including a contract partner selected or filled in for the item, and a contract partner selected or filled in for the item A storage unit for storing an electronic contract in which information is written;
Selecting a text template for a business processing device of an electronic contract creator in a business processing device that is a business device indicating whether the contracting party agrees with the electronic contract;
When the contract partner is blank, the contract partner is selected from the preset contract partner candidates,
Information including a contract partner selected or filled in for the item of the text template by the business processing device is accepted as the electronic contract,
The electronic contract and the text template are transmitted to the business processing device of the contract partner described in the electronic contract,
When the agreement information is received as a reply, the agreement negotiation processing procedure including storing the agreement information in the storage unit as the contract status correspondence information is performed,
When the agreement information stored in the contract status correspondence information is referred to and the agreement information indicates the agreement of all the contract parties, the business device that is the target of the setting described in the setting template is identified. Refer to the information to identify the business device that is the target of the setting,
The setting information including counterparties selected or entered with respect to the items described in the electronic contract, have a, and a control unit that performs relative subject to business device of said set,
The agreement information is stored for a plurality of electronic contracts,
There are a plurality of electronic contract creators, and each business processing device creates each of the plurality of electronic contracts,
When the agreement information indicates agreements of all contract parties, the agreement information is a case of agreements of all contract parties with respect to any one electronic contract among the plurality of electronic contracts. Contract content setting system. The controller is
2. The contract content setting system according to claim 1, wherein all or part of the contract negotiation processing procedure is repeated unless the agreement information indicates an agreement of all contract parties. The contract status correspondence information is:
Storing the number of times the contract negotiation process is repeated in association with information identifying the electronic contract;
2. The contract content setting system according to claim 1, wherein the control unit ends the contract negotiation processing procedure when the number of times reaches a predetermined number at the time of the reference. In the case where the agreement information indicates an intention of not agreeing, the agreement information is provided with a condition for agreement.
The controller is
In the repeated contract negotiation processing procedure, when the electronic contract is transmitted to the business processing device of the contract partner, the agreement is given to the business processing device other than the contract partner with the conditions for the agreement. The contract content setting system according to claim 1, further comprising: The contract content setting system according to claim 1, wherein a digital signature of the creator is attached to all or part of the text template, the setting template, and the agreement information. The business device subject to the setting is
A record management device for managing records relating to the business related to the contract;
An auditing device for auditing whether or not the work is properly performed;
The contract content setting system according to claim 1, comprising: The record management device comprises:
Record data sent to and received from other organizations,
The auditing device
Comparing the past data transmission / reception record received from the other organization with the transmission / reception record recorded in the record management device, and confirming whether or not a predetermined condition is satisfied,
The contract content setting system according to claim 6 . The business device subject to the setting is
Including a database device for managing data used in the business,
The record management device comprises:
Holding a record of access to the database device;
The auditing device
Confirming whether the access record recorded in the record management device satisfies a predetermined condition;
The contract content setting system according to claim 6 . The predetermined condition is
The access authority set for the database apparatus is compared with the access record recorded in the record management apparatus, and a record relating to access that is not permitted as the set access authority is stored in the record management apparatus. Is not included in the recorded access record,
The contract content setting system according to claim 8 , wherein: The predetermined condition is
Of the access records stored in the record management device, the difference between the feature quantity of the access record to be audited and the statistic calculated from the feature quantity of one or more other access records is: Being within a predetermined threshold,
The contract content setting system according to claim 8 , wherein: A contract content setting method using a contract content setting system that performs settings reflecting the content of a contract for devices in multiple organizations that are contract parties,
The contract content setting system includes:
One or a plurality of business devices to be set in the plurality of organizations and a contract support device that confirms that all the contracting parties have agreed to the contract and instructs the setting,
The storage unit of the contract support apparatus
Information for identifying a text template that is a model of an electronic contract in association with information for identifying an electronic contract, information for identifying a contract partner other than the contract creator of the contract, and each contract party Contract status correspondence information storing agreement information indicating whether or not has agreed to an electronic contract,
Information identifying the text template, information indicating the contents of the contract terms, information identifying items to be selected or filled in on the text template to complete the electronic contract, and contracts selected or filled in for the items A text template with information identifying the information including the other party,
A setting template in which information for identifying the text template, information for identifying a business device to be set, and information for identifying information including a contract partner selected or filled in for the item,
Including information identifying the electronic contract, information identifying the text template, information identifying information including a contract partner selected or filled in for the item, and a contract partner selected or filled in for the item Have an electronic contract with information,
The control unit of the contract support apparatus
Selecting a text template for a business processing device of an electronic contract creator in a business processing device that is a business device indicating whether the contracting party agrees with the electronic contract;
When the contract partner is blank, the contract partner is selected from the preset contract partner candidates,
Information including a contract partner selected or filled in for the item of the text template by the business processing device is accepted as the electronic contract,
The electronic contract and the text template are transmitted to the business processing device of the contract partner described in the electronic contract,
When the agreement information is received as a reply, the agreement negotiation processing procedure including storing the agreement information in the storage unit as the contract status correspondence information is performed,
When the agreement information stored in the contract status correspondence information is referred to and the agreement information indicates the agreement of all the contract parties, the business device that is the target of the setting described in the setting template is identified. Refer to the information to identify the business device that is the target of the setting,
The setting information including counterparties selected or entered with respect to the items described in the electronic contract, have row to the business system to be the setting,
The agreement information is stored for a plurality of electronic contracts,
There are a plurality of electronic contract creators, and each business processing device creates each of the plurality of electronic contracts,
If the agreement information indicates agreements of all contract parties, the agreement information indicates agreements of all contract parties for any one of the plurality of electronic contracts;
A contract content setting method characterized by The controller is
12. The contract content setting method according to claim 11 , wherein all or part of the contract negotiation processing procedure is repeated when the agreement information does not indicate agreements of all contract parties. The contract status correspondence information is:
Storing the number of times the contract negotiation process is repeated in association with information identifying the electronic contract;
The contract content setting method according to claim 11 , wherein, when the reference is made, the control unit ends the contract negotiation processing procedure when the number of times reaches a predetermined number. In the case where the agreement information indicates an intention of not agreeing, the agreement information is provided with a condition for agreement.
The controller is
In the repeated contract negotiation processing procedure, when the electronic contract is transmitted to the business processing device of the contract partner, the agreement is given to the business processing device other than the contract partner with the conditions for the agreement. The contract content setting method according to claim 11 , further comprising: The contract content setting method according to claim 11 , wherein a digital signature of the creator is attached to all or a part of the text template, the setting template, and the agreement information.

Images