Program, method, and information processing apparatus

Abstract

To provide a technique for allowing a user to identify a person assigned to review, more easily.SOLUTION: A storage unit stores information on a subject of review of document data in association with the type of the document data to be reviewed, which is document data to be approved by a person concerned, or information on an organization that requires review of the document data. A program causes a computer processor to execute the steps of: acquiring information on the type of document data to be reviewed, or information on an organization that requires review of the document data to be reviewed; referring to the information stored in the storage unit in accordance with the acquired information, to specify a reviewer of the document data to be reviewed; and presenting the specified reviewer to a user.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present disclosure relates to a program, a method, and an information processing device. [Background technology]

[0002] In conducting business activities, various contracts are concluded and the concluded contracts are managed. Electronic contract services are also used to approve document data between the parties, and the approved document data is managed on the service. For example, there are witness and party-based electronic signature methods.

[0003] Prior to the conclusion of a contract, the terms of the contract are reviewed by the legal department, etc. Patent Document 1 describes a document creation system that aims to "support the creation of documents when risk is taken into consideration," and includes "a selection means for selecting the type of document to be created, a creation means for creating a document according to the selected document type, a risk diagnosis means for diagnosing the risk of the created document, and a display means for displaying the created document in association with the diagnosed risk."

[0004] According to the technology of Patent Document 1, this has the effect of "enabling document creators to easily create documents that take risk into consideration." [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-138746 Summary of the Invention [Problem to be solved by the invention]

[0006] If reviewing contracts is recognized as a primary function within an organization, such as the legal department, it is common practice to request a review.

[0007] On the other hand, there are limits to the scope of review that the legal department can perform. Because contracts are created in conjunction with business activities, reviews may also be required from departments other than the legal department, such as the accounting department, information systems department, and business department. However, if you are unsure of who to request to review what, you may miss out on requests for reviews.

[0008] Therefore, there is a need for a technique that allows users to more easily specify who to request reviews from. [Means for solving the problem]

[0009] According to one embodiment of the present disclosure, there is provided a program for operating a computer having a computer processor, the program storing in a memory unit information on a subject reviewing the document data in association with information on the type of document data to be reviewed and to be approved by the parties, or information on an organization requiring review of the document data, and the program causing the computer processor to execute the steps of acquiring information on the type of document data to be reviewed or information on the organization requiring review of the document data to be reviewed, referring to information stored in the memory unit in accordance with the acquired information, identifying reviewers for the document data to be reviewed, and presenting the identified reviewers to a user. [Effects of the Invention]

[0010] According to the present disclosure, a user can more easily specify who to request a review from. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing the configuration of the system 1. [Figure 2] FIG. 2 is a diagram showing the configuration of the server 20. As shown in FIG. [Figure 3]FIG. 3 is a diagram showing the configuration of the terminal 10. As shown in FIG. [Figure 4] FIG. 4 is a diagram showing the data structure of the user database 211. As shown in FIG. [Figure 5] FIG. 5 is a diagram showing the data structure of the fastening management database 212. As shown in FIG. [Figure 6] FIG. 6 is a diagram showing the data structure of the document management database 213. As shown in FIG. [Figure 7] FIG. 7 is a diagram showing the data structure of the reviewer setting database 214. As shown in FIG. [Figure 8] FIG. 8 is a diagram showing the data structure of the review history database 215. As shown in FIG. [Figure 9] FIG. 9 is a diagram showing the flow of processing for identifying a reviewer of document data depending on the type of document data. [Figure 10] FIG. 10 is a diagram showing the flow of processing for identifying a reviewer of document data in accordance with information about an organization that requires review of document data. [Figure 11] Figure 11 is an example of a screen that retrieves document data and recommends reviewers. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. The names and functions of the components are also the same. Therefore, detailed descriptions thereof will not be repeated.

[0013] <Outline of embodiment> <1.1 Overall system configuration> FIG. 1 is a diagram showing the configuration of the system 1.

[0014] 1 includes a contract conclusion and document management service server 20, a user terminal 10, a business support service server 92, a document review service server 93, a large-scale language model service server 95, a personnel management service server 96, a legal consultation task service server 98, and a user terminal 10A. These devices are connected to each other via a network 80.

[0015] In the illustrated example, terminals such as terminal 10 and terminal 10A are shown as terminals used by users of the contract conclusion and document management service provided by server 20, and each user operates their own terminal.

[0016] In this embodiment, each device (terminal device, server, etc.) can also be considered as an information processing device. That is, a collection of devices can be considered as one "information processing device," and system 1 can be formed as a collection of multiple devices. The way in which multiple functions required to realize system 1 according to this embodiment are allocated to one or multiple pieces of hardware can be determined appropriately in consideration of the processing capacity of each piece of hardware and / or the specifications required for system 1.

[0017] The terminal 10 is a device operated by a user. The terminal 10 is realized, for example, as follows. · Handheld devices such as smartphones and tablets Desktop PCs (Personal Computers), laptop PCs Wearable devices worn by users (wristwatches, glasses, etc.) The terminal 10 includes a communication IF (Interface) 12 , an input device 13 , an output device 14 , a memory 15 , a storage 16 , and a processor 19 .

[0018] The communication IF 12 is an interface for inputting and outputting signals so that the terminal 10 can communicate with an external device.

[0019] The input device 13 is a device for receiving input operations from a user (for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.).

[0020] The output device 14 is a device (such as a display or speaker) for presenting information to the user.

[0021] The memory 15 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0022] The storage 16 is for storing data, and is, for example, a flash memory or a hard disk drive (HDD).

[0023] The processor 19 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like.

[0024] Server 20 is a device that provides a service for electronically concluding contracts and a service for managing document data concluded through electronic contracts. In system 1, the contract conclusion service provided by server 20 and the document data management service may be provided by different devices or different businesses. For example, server 20 may provide a document management service and, in addition to data on electronically signed contracts, optically read paper contracts with stamps to extract information such as the contract period and whether the contract is automatically renewed, and manage this information together with the scanned data of the contract as management information. This allows users to be notified when the contract period expires.

[0025] The server 20 includes a communication IF 22 , an input / output IF 23 , a memory 25 , a storage 26 , and a processor 29 .

[0026] The communication IF 22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

[0027] The input / output IF 23 functions as an interface with an input device for receiving input operations from the user and an output device for presenting information to the user.

[0028] The memory 25 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0029] The storage 26 is for storing data, and is, for example, a flash memory or a hard disk drive (HDD).

[0030] The processor 29 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

[0031] The business support service server 92 is a server that provides services to support business operations such as applications for approval in organizations (business companies, etc.) that carry out business activities. The business support (approval) service server 92 provides a service to users that enables them to design a workflow for obtaining budget approval among multiple users, for example.

[0032] The document review service server 93 is a service that supports document data reviews by accepting document data such as contracts and term sheets that specify contract terms and providing users with information such as whether each clause is favorable or unfavorable to the company, whether there are any missing clauses, and the importance of review items. The document review service server 93 provides a service that supports the above review using a rule base or a trained model. For example, a rule base may be used to review document data by previously associating specific wording or expressions with favorable or unfavorable conditions and explanations. Furthermore, the above review service can be provided by using data obtained by experts reviewing contracts, term sheets, etc. as training data to generate a trained model that responds with review results in response to input document data. The document review service server 93 can also summarize the contents of contracts and generate review comments using a large-scale language model and provide the results to users.

[0033] The large-scale language model service server 95 is a server that executes language processing tasks using a language model constructed by a learning process including artificial intelligence (AI). An LLM (Large Language Model) is a server that has previously learned a large amount of large-scale data (text data, etc.), for example, web content on the Internet, or a large amount of data stored in a specified database, and can execute various language processing tasks by giving the model a task.

[0034] The large-scale language model service server 95 accepts prompt inputs such as text, images, and voice, and generates and responds to the prompts. Examples of LLMs include GPT-3 and GPT-4 developed by OpenAI, and BERT developed by Google.

[0035] The personnel management service server 96 provides services to support recruitment, labor, and other operations for users such as the personnel department of an organization that conducts business activities. The personnel management service server 96, for example, manages a list of employees, and updates the employee list each time an employee joins or leaves the company. The personnel management service server 96 stores information for managing human resources, such as employee salaries and employee evaluations.

[0036] The legal consultation task service server 98 is a service for departments (such as legal departments) that handle the work of receiving and responding to legal consultations, and imports work requests (such as term sheets and contract reviews) via messaging tools, emails, etc., and enables management of the list as tasks. The legal consultation task service server 98 works in conjunction with the above-mentioned messaging tools, etc., and when a user responds on the legal consultation task service, it posts the response to an external messaging tool, etc.

[0037] <1.2 Functional configuration of server 20> 2 is a diagram showing the configuration of the server 20. As shown in FIG. 2, the server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0038] The communication unit 201 performs processing for the server 20 to communicate with external devices.

[0039] The storage unit 202 stores various databases such as a user database 211, a contract management database 212, a document management database 213, a reviewer setting database 214, and a review history database 215.

[0040] The user database 211 is a database for managing users.

[0041] The user database 211 contains information such as the user's name, employee number, etc., for using the services provided by the server 20. Details will be described later.

[0042] The contract conclusion management database 212 is a database that manages the contract conclusion process carried out by the electronic contract service provided by the server 20. Details will be described later.

[0043] The document management database 213 is a database for managing document data, and includes information for managing document data concluded through the electronic contract service provided by the server 20. Details will be described later.

[0044] The reviewer setting database 214 is a database that manages the entities that review document data by associating them with (i) information on the type of contract, (ii) information on the department that requires the contract to be reviewed, and (iii) information on the department that is responsible for reviewing the contract. (i) Information on the type of contract includes the type of contract, etc. (ii) Information on the department that requires the contract to be reviewed includes information on the business area that the contract covers and the department that requested the contract review, etc. (iii) Information on the department that is responsible for reviewing the contract includes information on the entities (reviewers) that are responsible for reviewing the contract. Details will be provided below.

[0045] The review history database 215 is a database that manages the history of reviews of document data such as contracts, etc. Details will be described later.

[0046] The control unit 203 is realized by the processor 29 reading a program stored in the storage unit 202 and executing instructions included in the program. By operating in accordance with the program, the control unit 203 exhibits functions shown as a reception control module 2041, a transmission control module 2042, a user management module 2043, a conclusion processing module 2044, a document management module 2045, a reviewer condition definition module 2046, and a reviewer extraction module 2047.

[0047] The reception control module 2041 controls the process by which the server 20 receives signals from external devices in accordance with a communication protocol.

[0048] The transmission control module 2042 controls the process in which the server 20 transmits signals to external devices in accordance with a communication protocol.

[0049] The user management module 2043 is a module for managing information about each user who uses the system 1. Specifically, the user management module 2043 accepts registration of information about each user and updates the user database 211.

[0050] The conclusion processing module 2044 controls the process of the parties approving document data as a process for concluding a contract by electronic contract. Specifically, the conclusion processing module 2044 notifies each user who approves the document data, and updates the conclusion management database 212 in response to the operation of approving the document data.

[0051] The document management module 2045 controls the process of managing document data by referring to the document management database 213. Specifically, the document management module 2045 notifies the user whether to renew the contract when the contract period expires, based on the information about the contract period set in the document data, and updates the document management database 213 in response to the user's operation (such as renewal).

[0052] The reviewer condition definition module 2046 accepts the designation of the reviewer who will be responsible for reviewing the document data, by associating it with the type of document data that the parties are to approve and that will be reviewed, information about the organization that requires the document data to be reviewed, and information about the department responsible for reviewing the document data, and updates the reviewer setting database 214.

[0053] The reviewer extraction module 2047 refers to the reviewer setting database 214 and identifies reviewers according to the type of document data and information about the organization that requires review of the document data.

[0054] <1.3 Configuration of Terminal 10> FIG. 3 is a diagram showing the configuration of the terminal 10. As shown in FIG.

[0055] As shown in FIG. 3, the terminal 10 includes multiple antennas (antenna 111, antenna 112), communication units (first communication unit 120, second communication unit 121) corresponding to the respective antennas, an input device 130 (including a touch-sensitive device 131), a display 132, an audio processing unit 140, a microphone 141, a speaker 142, a position information sensor 150, a camera 160, a motion sensor 170, a memory unit 180, and a control unit 190. The terminal 10 also has functions and configurations (e.g., a battery for storing power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.) that are not specifically shown in FIG. 3. As shown in FIG. 3, the blocks included in the terminal 10 are electrically connected by a bus or the like.

[0056] The antenna 111 emits a signal emitted by the terminal 10 as a radio wave. The antenna 111 also receives a radio wave from space and provides the received signal to the first communication unit 120.

[0057] The antenna 112 emits a signal emitted by the terminal 10 as a radio wave. The antenna 112 also receives a radio wave from space and provides the received signal to the second communication unit 121.

[0058] The first communication unit 120 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 111 so that the terminal 10 can communicate with other wireless devices. The second communication unit 121 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 112 so that the terminal 10 can communicate with other wireless devices. The first communication unit 120 and the second communication unit 121 are communication modules including a tuner, a received signal strength indicator (RSSI) calculation circuit, a cyclic redundancy check (CRC) calculation circuit, a high-frequency circuit, and the like. The first communication unit 120 and the second communication unit 121 perform modulation / demodulation, frequency conversion, and the like for wireless signals transmitted and received by the terminal 10, and provide the received signals to the control unit 190.

[0059] Input device 130 has a mechanism for accepting input operations by a user. Specifically, input device 130 is configured as a touch screen and includes touch-sensitive device 131. Touch-sensitive device 131 accepts input operations by a user of terminal 10. Touch-sensitive device 131 detects the user's touch position on the touch panel, for example, by using a capacitive touch panel. Touch-sensitive device 131 outputs a signal indicating the user's touch position detected by the touch panel to control unit 190 as an input operation.

[0060] The display 132 displays data such as images, videos, and text under the control of the control unit 190. The display 132 is realized by, for example, an LCD, an organic EL display, or the like.

[0061] The audio processing unit 140 modulates and demodulates audio signals. The audio processing unit 140 modulates a signal provided from the microphone 141 and provides the modulated signal to the control unit 190. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is realized, for example, by a processor for audio processing. The microphone 141 accepts audio input and provides an audio signal corresponding to the audio input to the audio processing unit 140. The speaker 142 converts the audio signal provided from the audio processing unit 140 into audio and outputs the audio to the outside of the terminal 10.

[0062] The location information sensor 150 is a sensor that detects the location of the terminal 10, and is, for example, a GPS (Global Positioning System) module. The GPS module is a receiving device used in a satellite positioning system. The satellite positioning system receives signals from at least three or four satellites, and detects the current location of the terminal 10 equipped with the GPS module based on the received signals.

[0063] The camera 160 is a device that receives light with a light receiving element and outputs the received light as a captured image. The camera 160 is, for example, a depth camera that can detect the distance from the camera 160 to a subject being photographed.

[0064] The motion sensor 170 includes an acceleration sensor, an angular velocity sensor, etc., and detects the movement of the terminal 10 .

[0065] The storage unit 180 is configured with, for example, a flash memory, and stores data and programs used by the terminal 10. The various types of information stored in the storage unit 180 will be described later.

[0066] The control unit 190 controls the operation of the terminal 10 by reading a program stored in the storage unit 180 and executing instructions included in the program. The control unit 190 is, for example, an application processor. By operating in accordance with the program, the control unit 190 fulfills the functions of an operation reception unit 191, a transmission / reception unit 192, a data processing unit 193, a notification control unit 194, and a storage control unit 195.

[0067] Operation acceptance unit 191 performs processing to accept a user's input operation to an input device such as touch-sensitive device 131. Operation acceptance unit 191 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, or a drag (swipe) operation, based on information about the coordinates where the user has touched touch-sensitive device 131 with a finger or the like.

[0068] The transmitting / receiving unit 192 performs processing for the terminal 10 to transmit and receive data to and from an external device such as the server 20 in accordance with a communication protocol.

[0069] The data processing unit 193 performs calculations on data that the terminal 10 has received as input in accordance with a program, and outputs the calculation results to a memory or the like.

[0070] The notification control unit 194 performs processing for displaying a display image on the display 132, processing for outputting sound from the speaker 142, and processing for generating vibrations.

[0071] The storage control unit 195 controls the storage of data in the storage unit 180 .

[0072] A description will be given of various types of information stored in storage unit 180. In one aspect, storage unit 180 stores various types of information such as user information 181, attendance management information 182, and business task information 183.

[0073] The user information 181 is information about a user who uses the services of the server 20. The user information 181 includes, for example, information such as the employee number and name of the user.

[0074] The attendance management information 182 is information indicating the registration status of the user's attendance management (vacation, etc.) The terminal 10 and the server 20 can acquire attendance management information from the server 96 of the personnel management service.

[0075] The business task information 183 indicates the status of the task of a user requesting legal advice or a user providing a response. The terminal 10 and the server 20 can acquire the status of the legal advice task from the server 98 of the legal advice task service.

[0076] <2 Data Structure> 4 is a diagram showing the data structure of the user database 211. The user database 211 includes the following items: "User ID," "Business Operator ID," "Name," "Email Address," "Department," "Position," "Date of Employment," "Date of Resignation," and "Qualifications."

[0077] The item "user ID" is information that identifies each user.

[0078] The item "business operator ID" is information that identifies each business operator.

[0079] The item "Name" is information about the user's name.

[0080] The item "email address" is information that serves as the user's contact information.

[0081] The item "department" is information about the user's department.

[0082] Specifically, the item "department" may include the following as information about the department to which the user belongs: - Business departments, sales departments, etc. that do not primarily handle legal affairs Departments that primarily handle legal affairs, such as the legal department and intellectual property department The item "position" is information about the position of the user.

[0083] The item "Date of joining" is information about the date on which a user joined an organization.

[0084] The item "Retirement Date" is information about the date on which the user retired from the organization.

[0085] The item "Qualifications held" is information about qualifications held by the user.

[0086] Specifically, the item "Qualifications held" includes the following information as qualifications held by the user: Qualifications that are expected to give the knowledge to review contracts, such as a lawyer Qualifications that are expected to show knowledge of business activities, such as small and medium-sized enterprise management consultants Qualifications that are expected to have the necessary knowledge in accounting, tax, etc., such as certified public accountants and tax accountants 5 is a diagram showing the data structure of the agreement management database 212. The agreement management database 212 includes an item "agreement ID," an item "sender ID," an item "recipient ID," an item "data to be agreed upon," an item "first email address," an item "second email address," an item "sent date and time," an item "user signature date and time," an item "agreement completion date and time," and an item "status."

[0087] The item "contract ID" is information that identifies each contract conclusion procedure.

[0088] Specifically, the item "Conclusion ID" includes identification information issued by the server 20 when a new registration of a process for concluding an electronic contract by specifying an approver is accepted for document data to be approved by the parties.

[0089] The item "sender ID" is information for identifying the party who will be the sender when the party approves document data.

[0090] Specifically, the item "sender ID" may be associated with information about the business (business ID) or information about the user (user ID) managed in the user database 211.

[0091] The item "recipient ID" is information for identifying the party who will be the recipient when the party approves document data.

[0092] Specifically, the item "Receiver ID" is information that identifies the party designated by the sender's user as the receiver, and like the sender ID, may be associated with information about the business (business ID) or the user (user ID) managed in the user database 211.

[0093] The item "data to be concluded" is document data to be approved by the parties.

[0094] Specifically, the item "data to be concluded" indicates data (files such as PDF) of transaction documents such as contracts, applications, and estimates.

[0095] The item "primary email address" is an email address that serves as a contact point for the user who will be the sender in the process of concluding a contract by approving document data.

[0096] Specifically, the item "first email address" is the email address of the user who performs the operation to send document data as the sender.

[0097] The item "secondary email address" is an email address that serves as the contact address of the user who approves as a recipient in the process of concluding a contract by approving document data.

[0098] Specifically, the item "second email address" is the email address of the user who will approve the document data as the recipient. Note that there may be multiple users who approve the document data among the parties, and if the user who sends the document data specifies the email addresses of multiple users who will approve the document data, the specified email addresses are also managed in the agreement management database 212.

[0099] The item "transmission date and time" is information about the date and time when an operation to transmit document data was accepted from a user who will be the sender in order to request approval of the document data from each user.

[0100] The item "user signature date and time" is information on the date and time when the user performed an operation to approve the document data.

[0101] Specifically, the item "User Signature Date and Time" includes information on the timing when a user who has been requested to approve document data checks the document data, performs an operation to approve, and then digitally signs the document data by having the operation accepted by the server 20. The server 20 digitally signs the document data each time a user performs an operation to approve, and stores the timing information in the agreement management database 212.

[0102] The item "conclusion completion date and time" is information about the date and time when the conclusion of the contract was completed.

[0103] Specifically, when a contract is concluded using the electronic contract service provided by server 20, the item "Date and time of conclusion completion" stores the date and time information in the conclusion management database 212, assuming that the conclusion of the contract is completed when all users designated to approve the document data perform the approval operation.

[0104] The item "status" is information indicating the stage at which the contract conclusion work is currently underway.

[0105] Specifically, the item "status" may include the following as the stage of the contract conclusion process: Before sending: Indicates that the document data has been registered on the server 20 by the sender, but has not yet been sent to the recipient. - In Progress: Indicates that the document data has been sent and approval by each user has not yet been completed. Completed: Indicates that the contract has been concluded Rejected, returned: Indicates that the contract was not completed due to reasons such as the user not approving the document data, or a timeout occurring after a certain period of time had passed without approval being completed. 6 is a diagram showing the data structure of the document management database 213. The document management database 213 includes an item "document management ID," an item "contract ID," an item "document title," an item "contract start date," an item "contract expiration date," and an item "automatic renewal status."

[0106] The item "document management ID" is information for identifying each document data being managed.

[0107] The item "contract ID" is information that identifies each contract conclusion procedure that the parties have performed to approve the document data.

[0108] Specifically, the item "contract ID" may be associated with information (contract ID) that identifies each contract conclusion, which is managed in the contract management database 212.

[0109] The item "document title" is information about the title of the document data being managed.

[0110] Specifically, the item "document title" may be a word used as a type or name of a contract, such as a confidentiality agreement, a sales contract, or a license agreement.

[0111] The item "contract start date" is information indicated as the start date of the contract in the document data.

[0112] Specifically, the value of the item "contract start date" may be set as follows. When the contract is concluded, the server 20 reads the start date of the contract from the contract data. - Information entered by the user as the contract start date The same applies to the following items "Contract Expiration Date" and "Automatic Renewal Enabled."

[0113] The item "contract expiration date" is information indicated as the contract expiration date in the document data.

[0114] The item "automatic renewal" is information indicating whether the contract period is automatically extended (automatic renewal) when the contract period expires in the document data without the parties having to re-enter the contract.

[0115] 7 is a diagram showing the data structure of the reviewer setting database 214. The reviewer setting database 214 includes an item "business operator ID," an item "contract type," an item "business," an item "review request department," an item "reviewer department," an item "reviewer user," an item "review ID," an item "contract ID," and an item "document management ID."

[0116] The item "business operator ID" is information that identifies each business operator.

[0117] Specifically, the item "business ID" may be associated with information about the business (business ID) managed in the user database 211.

[0118] The item "contract type" is information indicating the type of contract.

[0119] Specifically, the item "contract type" includes the following information as the type of contract: Typical contracts (sales contracts, etc.), non-typical contracts The item "business" is information about the business area covered by the contract.

[0120] Specifically, the item "business" may include information on the business domain that the business operator defines in the course of conducting business activities.

[0121] The item "review requesting department" is information that identifies the organization (department, etc.) that requests a review of the contract conditions.

[0122] Specifically, the item "review request department" may include information on each department shown in an organizational chart defined by the business operator, and information on the departments included in these departments.

[0123] The item "reviewer department" is information about the department in charge of the review.

[0124] Specifically, the item "Reviewer department" includes information about the organization that will perform the review, depending on the items "Contract type," "Business," and "Department requesting review." For example, in addition to departments that are typically recognized as reviewing contracts, such as the legal department, there may also be the accounting department (checking payment methods, etc.), the information systems department (checking security-related matters), the business department (checking terms such as amounts), etc.

[0125] The item "reviewer user" is information about the user in charge of review.

[0126] Specifically, the item "reviewer user" includes information about the user who will perform the review according to the items "contract type," "business," and "review requesting department."

[0127] The item "review ID" is information that identifies each review performed on document data.

[0128] Specifically, the item "review ID" may be associated with information (review ID) that identifies each review, which is managed in the review history database 215.

[0129] The item "contract ID" is information that identifies each contract conclusion procedure.

[0130] Specifically, the item "contract ID" may be associated with information (contract ID) that identifies each contract conclusion procedure, which is managed in the contract conclusion management database 212.

[0131] The item "document management ID" is information for identifying each document data being managed.

[0132] Specifically, the item "document management ID" may be associated with information (document management ID) that is managed in the document management database 213 and identifies each document data being managed.

[0133] 8 is a diagram showing the data structure of the review history database 215. The review history database 215 includes an item "review ID," an item "document data," an item "document management ID," an item "review date and time," an item "review user," an item "review content," and an item "review requester's evaluation."

[0134] The item "review ID" is information that identifies each review performed on document data.

[0135] The item "Document Data" is information about the document data to be reviewed.

[0136] The item "document management ID" is information for identifying each document data being managed.

[0137] Specifically, the item "document management ID" may be associated with information (document management ID) that identifies each piece of document data, which is managed in the document management database 213.

[0138] The item "review date and time" is information about the date and time when the review was performed.

[0139] The item "reviewer user" is information about the user who reviewed the item.

[0140] The item "review content" is information indicating the results of the review.

[0141] Specifically, the item "review content" may include the following as review results: - Review results by the document review service server 93 (advantages and disadvantages of the conditions, importance, proposed revisions, etc.) Comments and suggested corrections entered by users (including information about users who enter review comments) The item "rating of review requester" is information indicating the rating of the user who requested the review on the review content of the reviewer.

[0142] Specifically, the item "review requester's evaluation" includes the result of the user who requested the review evaluating the reviewer based on the operation performed on the review result, and the following are possible. The user who requested the review can set a score for the review result. The number of reactions, such as "likes," added to posts sent via messaging tools to contact users for reviews <3 operations> FIG. 9 is a diagram showing the flow of processing for identifying a reviewer of document data depending on the type of document data.

[0143] In step S921, the server 20 presents the user with a screen that supports reviewer assignment.

[0144] In step S911, the terminal 10 receives from the user the specification of the document data to be reviewed or the type of document data (information specifying the contract type or business).

[0145] In step S923, the server 20 extracts reviewers corresponding to the type of document data, based on the information specified by the user in step S911, by referring to the reviewer setting database 214. The server 20 identifies the extracted reviewers as reviewers for the document data to be reviewed.

[0146] Specifically, the reviewer setting database 214 stores information about the review subject in association with the contract type as the type of document data. The server 20 acquires information about the contract type of the document data as the information about the type of document data. The server 20 identifies a reviewer according to the type.

[0147] Specifically, the reviewer setting database 214 stores information about the review subject in association with information identifying the business related to the document data as the type of document data. The server 20 acquires information identifying the business related to the document data as information about the type of document data. For example, the server 20 can refer to information about the parties in the document data and identify the business area in which transactions with the parties take place from transaction histories indicated in estimates, purchase orders, invoices, etc., or from a database of business partners. In addition, the business area related to the document data may be identified based on the contract terms indicated in the document data (e.g., the type of goods or services that are the subject of a transaction such as buying and selling) (the objects of transactions such as purchasing may differ for each business). The server 20 identifies the reviewer based on the information identifying the business.

[0148] The server 20 may identify reviewers to be presented to a user depending on the status of the tasks that the reviewers are responsible for. Specifically, the server 20 may identify reviewers to be presented to a user depending on the status of the tasks that the reviewers are responsible for, such as the registration status of the reviewer's attendance management data, the registration status of the reviewer's calendar schedule (whether the schedule is filled), and the amount of tasks assigned to the reviewer user as the person in charge (legal consultation tasks, or task information that can be obtained by linking with a general-purpose task management tool). For example, if there are circumstances such as the number of cases that the reviewer is handling as tasks, being on vacation, or having a certain number of schedules registered in the calendar, it may be assumed that it will take time to respond to a review request, and the priority of extracting the reviewer may be lowered.

[0149] In step S925, the server 20 presents the identified reviewers to the user.

[0150] In step S913, the terminal 10 displays the recommended reviewers. The terminal 10 accepts an operation to set other systems (such as an approval application service, a contract conclusion service, and a document management service) as persons in charge of the workflow.

[0151] In step S927, the server 20 sets the identified reviewer as a person in charge of processing related to the contract in response to a user operation. For example, the server 20 sets the identified reviewer as the person in charge of the following: - Ability to register as a person in charge of legal consultation tasks Review contracts and set users as those who can edit the review Set as a user in the process of concluding a contract between parties, or as a user who manages a concluded contract. For example, set as a user who approves a contract in the process of concluding a contract between parties, or set as a user who can view a contract in the process of managing a contract. FIG. 10 is a diagram showing the flow of processing for identifying a reviewer of document data in accordance with information about an organization that requires review of document data.

[0152] In step S1011, the terminal 10 receives, from the user, information about the organization that requires the review of the document data to be reviewed (the department requesting the review, the user requesting the review).

[0153] In step S1023, the server 20 refers to the reviewer setting database 214 based on the information of the department or user requesting the review, extracts reviewers corresponding to the type of document data, and identifies them as reviewers for the document data to be reviewed.

[0154] Also, similarly to step S923, the server 20 may identify reviewers to be presented to the user depending on the status of the tasks that the reviewers are in charge of.

[0155] <4 Screen example> Figure 11 is an example of a screen that retrieves document data and recommends reviewers.

[0156] A screen 1200 is an operation screen for setting reviewers for document data.

[0157] The account display area 1210 is an area for displaying information about the account of a user who has logged in to a service provided by the server 20.

[0158] The review target receiving unit 1220 is an operation member that receives an operation for acquiring document data to be reviewed by uploading it by the user or the like.

[0159] The review target receiving unit 1220 corresponds to the processing of step S911 and the like.

[0160] The reviewer setting reception area 1230 is an area that displays information about the document data to be reviewed and reviewers extracted as recommendations, and receives an operation to set the reviewer as a reviewer.

[0161] The review target viewing reception section 1231 is information on document data to be reviewed that has been uploaded by the user.

[0162] In the illustrated example, the review target browsing acceptance section 1231 displays a file name. The server 20 may preview details of the document data in response to a user's operation on the review target browsing acceptance section 1231.

[0163] The details display area 1232 is an area for displaying the conditions for setting reviewers for the uploaded document data.

[0164] The detail display area 1232 displays the results of determining, from the uploaded document data, information on each item of the reviewer setting database 214, which is used by the server 20 as a condition for extracting reviewers in the process of step S923 and the like.

[0165] For example, the server 20 extracts the type of contract from the title of the uploaded contract.

[0166] For example, the server 20 extracts the business area of ​​the contract from the department to which the user who uploaded the contract belongs or from the contract terms and conditions set forth in the contents of the contract (such as extracting the business area as the business conducted by the department to which the uploading user belongs, or extracting the business area from the purchase target set forth in the contract).

[0167] Reviewed document data information 1233 is an area that displays details of the conditions for setting a reviewer.

[0168] The reviewer setting area 1234 is an area that displays reviewers extracted as recommendations according to the uploaded document data and accepts operations to set them as reviewers or other people in charge of the document data.

[0169] The reviewer setting area 1234 corresponds to the processing of step S923 and the like.

[0170] The request operation receiving section 1235 is an area for displaying a list of extracted reviewers and receiving an operation to request a review of uploaded document data and an operation to set a reviewer as a person in charge of another system.

[0171] The requested operation receiving unit 1235 corresponds to the processing of steps S925, S927, etc. As shown in the example, the following is displayed. Reviewer's name and department Reason for recommending a reviewer (Which of the conditions shown in the reviewer setting database 214 did the reviewer meet and be extracted? The review history database 215 may be referenced and the reviewer may be extracted based on the number of reviews or other track records, in which case the reviewer must have a certain number of review records or more) An operation member for accepting an operation to set as a reviewer (set as a reviewer in the review history database 215) - Operational components that accept operations to be set as the person in charge of other systems (settings for approval applications, contract signing, document management service viewers, etc.) The person in charge status display area 1236 is an area that displays the status of the tasks of the person in charge of review and notifies the estimated time for review.

[0172] The person in charge status display unit 1236 corresponds to the processing of step S923 etc. For example, the server 20 may specify the time when the reviewer can start work based on the reviewer's attendance, schedule, and the amount of tasks for which the reviewer is responsible for the case, and display this as a guide for the review time.

[0173] <Modification> In addition to the aspects described in the above embodiment, the following may be adopted.

[0174] In the above embodiment, it has been described that each business provides a service using each device, such as the business support system service server 92, the document review service server 93, the large-scale language model service server 95, and the human resources management service server 96. However, it is also possible for a single business to provide multiple services. For example, it is possible for a single business to provide a contract conclusion service, a document management service, and a business support (approval application) service.

[0175] In the above embodiment, an example has been described in which a reviewer for a contract is identified based on the conditions for setting a reviewer. In addition to the contract, a reviewer may be set for a term sheet or the like that defines the terms of the contract.

[0176] Although several embodiments of the present disclosure have been described above, these embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are intended to be included in the scope of the inventions and their equivalents as defined in the claims, as well as in the scope and spirit of the inventions.

[0177] The functions performed by the components described herein may be implemented in circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), a CPU (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to perform the described functions. A processor includes transistors and other circuits and is considered to be circuitry or processing circuitry. A processor may also be a programmed processor that executes programs stored in memory.

[0178] In this specification, a circuitry, unit, or means is hardware that is programmed to realize or performs the described functions, which may be any hardware disclosed herein or any hardware known to be programmed to realize or perform the described functions.

[0179] If the hardware is a processor considered to be a type of circuitry, the circuitry, means, or unit is a combination of the hardware and software used to configure the hardware and / or processor.

[0180] <Additional Notes> The matters explained in the above embodiment will be supplemented below.

[0181] (Appendix 1) A program for operating a computer having a computer processor, the program storing in a memory unit information about the subject of review of the document data in association with information about the type of document data to be reviewed and to be approved by the parties, or information about the organization that requires the review of the document data, the program causing the computer processor to execute the steps of acquiring information about the type of document data to be reviewed or the information about the organization that requires the review of the document data to be reviewed, referring to the information stored in the memory unit in accordance with the acquired information, identifying reviewers for the document data to be reviewed, and presenting the identified reviewers to a user.

[0182] (Appendix 2) A program as described in Appendix 1, in which a memory unit stores information on the review subject in association with the contract type as the type of document data, and in the acquisition step, information on the contract type of the document data is acquired as information on the type of document data, and in the identification step, a reviewer is identified according to the type.

[0183] (Appendix 3) A program described in any of Appendices 1 to 2, wherein a memory unit stores information about the review subject in association with information identifying the business related to the document data as the type of document data, and in the acquisition step, acquires information identifying the business related to the document data as information about the type of document data, and in the identification step, identifies a reviewer according to the information identifying the business.

[0184] (Appendix 4) A program according to any one of appendices 1 to 3, wherein in the obtaining step, information about the department requesting the review or the user requesting the review is obtained as information about the organization that requires the document data to be reviewed, and in the identifying step, a reviewer is identified based on the information about the department requesting the review or the user requesting the review.

[0185] (Appendix 5) A program described in any of Appendices 1 to 4, further causing the processor to execute a step of setting the identified reviewer as the person in charge of processing the contract.

[0186] (Appendix 6) 6. The program according to claim 5, wherein the step of setting enables the identified reviewer to be registered as a person in charge of a task related to legal consultation.

[0187] (Appendix 7) 7. The program according to any one of appendices 5 to 6, wherein in the setting step, the identified reviewer is set as a user who can review the contract and edit the review content.

[0188] (Appendix 8) A program described in any of Appendices 5 to 7, in which, in the setting step, the identified reviewer is set as a user in the process of concluding a contract between the parties, or as a user who manages the concluded contract.

[0189] (Appendix 9) A program as described in Appendix 8, in which, in the setting step, the identified reviewer is set as a user who approves a contract in a process of concluding a contract between parties, or as a user who can view a contract in a process of managing a contract.

[0190] (Appendix 10) In the identifying step, 10. The program according to any one of appendices 1 to 9, which identifies reviewers to be presented to a user depending on the reviewer's task status.

[0191] (Appendix 11) In the identifying step, A program as described in Appendix 10, which identifies the reviewer to be presented to the user based on the reviewer's attendance management data registration status or the amount of tasks assigned to the reviewer's user as the person in charge of the tasks for which the reviewer is responsible.

[0192] (Appendix 12) A method for operating a computer having a computer processor, wherein a memory unit stores information about the subject of review of document data in association with information about the type of document data to be reviewed and to be approved by the parties, or information about the organization requiring the review of the document data, and the method includes the steps of the computer processor acquiring information about the type of document data to be reviewed or the organization requiring the review of the document data, referring to the information stored in the memory unit in accordance with the acquired information to identify reviewers of the document data to be reviewed, and presenting the identified reviewers to a user.

[0193] (Appendix 13) An information processing device having a control unit, wherein a memory unit stores information about the subject of review of the document data in association with information about the type of document data to be reviewed and to be approved by the parties, or information about the organization that requires the review of the document data, and the control unit executes the steps of acquiring information about the type of document data to be reviewed or the information about the organization that requires the review of the document data to be reviewed, referring to the information stored in the memory unit in accordance with the acquired information, identifying reviewers for the document data to be reviewed, and presenting the identified reviewers to a user.

Claims

1. A program for operating a computer having a computer processor, a storage unit stores information about a subject of review of the document data in association with information about the type of the document data that is the subject of approval by the parties and is the subject of review, or information about an organization that requires the review of the document data; The program causes the computer processor to: acquiring information on the type of document data to be reviewed or information on an organization that requires review of the document data to be reviewed; a step of identifying a reviewer of the document data to be reviewed by referring to information stored in the storage unit according to the acquired information; and presenting the identified reviewers to a user.

2. the storage unit stores information about the review subject in association with a contract type as the type of the document data; In the obtaining step, information on the type of contract of the document data is obtained as information on the type of the document data; The program according to claim 1 , wherein the step of identifying the reviewer identifies the reviewer according to the type.

3. the storage unit stores information about the review subject in association with information identifying a business related to the document data as the type of the document data; In the obtaining step, information specifying a business related to the document data is obtained as information on the type of the document data; The program according to claim 1 , wherein in the step of identifying, the reviewer is identified according to information identifying the business.

4. In the obtaining step, information on the department requesting the review or the user requesting the review is obtained as information on the organization that requires the review of the document data; 2. The program according to claim 1, wherein the step of specifying the reviewer includes specifying the reviewer according to information about a department or a user requesting the review.

5. The program further causes the processor to The program according to claim 1 , further comprising a step of setting the identified reviewer as a person in charge of processing the contract.

6. 6. The program according to claim 5, wherein in the setting step, the identified reviewer can be registered as a person in charge of a task related to legal consultation.

7. 6. The program according to claim 5, wherein the step of setting includes setting the identified reviewer as a user who can review the contract and edit review content.

8. 6. The program according to claim 5, wherein in the setting step, the identified reviewer is set as a user in a process of concluding a contract between the parties, or as a user who manages the concluded contract.

9. 9. The program of claim 8, wherein in the setting step, the identified reviewer is set as a user who approves the contract in a process of concluding the contract between the parties, or as a user who can view the contract in a process of managing the contract.

10. In the step of specifying, The program according to claim 1 , further comprising: identifying the reviewers to be presented to the user according to the status of tasks that the reviewers are in charge of.

11. In the step of specifying, The program of claim 10, wherein the reviewer to be presented to the user is identified based on the reviewer's attendance management data registration status or the amount of tasks assigned to the reviewer's user as the person in charge of the tasks for which the reviewer is responsible.

12. 1. A method of operating a computer having a computer processor, comprising: a storage unit stores information about a subject of review of the document data in association with information about the type of the document data that is the subject of approval by the parties and is the subject of review, or information about an organization that requires the review of the document data; The method further comprises the steps of: acquiring information on the type of document data to be reviewed or information on an organization that requires review of the document data to be reviewed; a step of identifying a reviewer of the document data to be reviewed by referring to information stored in the storage unit according to the acquired information; presenting the identified reviewers to a user.

13. An information processing device including a control unit, a storage unit stores information about a subject of review of the document data in association with information about the type of the document data that is the subject of approval by the parties and is the subject of review, or information about an organization that requires the review of the document data; The control unit acquiring information on the type of document data to be reviewed or information on an organization that requires review of the document data to be reviewed; a step of identifying a reviewer of the document data to be reviewed by referring to information stored in the storage unit according to the acquired information; and presenting the identified reviewer to a user.

Images