Information management system, information management method, and program

Abstract

Provided is an information management system or the like that can appropriately manage human resource management documents. 【Solution means】According to one aspect of the present invention, there is provided an information management system including at least one processor configured to execute the following steps by reading a program. In a reception step, registration information regarding a person to be managed who works for an organization, which is registered in a database within the organization, is received. In a creation step, a first document regarding a human resource management document including document components derived from the registration information is created. The document components include a sentence created based on the registration information. In a public reception step, a public request to publicly disclose the first document or an edited version of the first document within a predetermined range is received from the person to be managed and / or the administrator of the person to be managed. In a public disclosure step, based on the fact that the public request has been received, the first document or the edited version is publicly disclosed within a predetermined range as a human resource management document.

Description

Technical Field

[0001] The present invention relates to an information management system, an information management method, and a program.

Background Art

[0002] As disclosed in Patent Document 1, a technique for assisting in creating a sentence by automatically creating a template is known.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] By the way, in recent years, there has also been a movement to utilize a human resource management document for managing human resources within an organization. This human resource management document requires, for example, the description of various sentences regarding the person to be managed in addition to basic information such as the name of the person to be managed. On the other hand, when creating a sentence by applying the prior art as described above, there are cases where document management in accordance with the intention of the person to be managed, etc. cannot necessarily be achieved.

[0005] In view of the above circumstances, the present invention aims to provide an information management system or the like that can properly manage a human resource management document.

Means for Solving the Problems

[0006] According to one aspect of the present invention, there is provided an information management system comprising at least one processor configured to execute the following steps by reading a program. In a reception step, registration information regarding a person to be managed who is engaged in an organization and registered in a database within the organization is received. In a creation step, a first document regarding a human resource management document including document components derived from the registration information is created, and the document components include sentences created based on the registration information. In a public reception step, a public request to publicly release the first document or an edited version of the first document within a predetermined range is received from the person to be managed and / or the administrator of the person to be managed. In a public release step, based on the reception of the public request, the first document or the edited version is publicly released within a predetermined range as a human resource management document.

[0007] According to such an aspect, an information management system or the like that can appropriately manage human resource management documents is provided.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Embodiments for Carrying Out the Invention

[0009] Hereinafter, embodiments of the present invention will be described. Note that the various characteristic matters shown in the following embodiments can be combined with each other.

[0010] That is, the information management system of this embodiment is as follows. An information management system, comprising at least one processor, wherein the processor is configured to execute the following steps by reading a program, In the reception step, registration information regarding a management target person engaged in the organization, which is registered in a database within the organization, is received, In the creation step, a first document regarding a human resource management document including document components derived from the registration information is created. Here, the document components include a text created based on the registration information, In the public reception step, a public request to publicly disclose the first document or an edited version of the first document within a predetermined range is received from the management target person and / or an administrator of the management target person, In the public disclosure step, based on the fact that the public request has been received, the first document or the edited version is publicly disclosed within the predetermined range as a human resource management document. An information management system.

[0011] Incidentally, the program for realizing the software appearing in one embodiment may be provided as a non-transitory computer-readable medium that can be read by a computer, may be provided so as to be downloadable from an external server, or may be provided so that the program is started on an external computer to realize its function on a client terminal (so-called cloud computing).

[0012] Also, in various information processes according to one embodiment, an input and an output corresponding to the input can be realized. Here, if an output is obtained as a result of the input, the form of the information (hereinafter referred to as reference information) referred to in such information processing is not limited. The reference information may be, for example, rule-based information such as a database, a lookup table, a predetermined function (including a judgment formula such as a regression formula constructed by a statistical method), a learned model in which the correlation between the input and the output has been learned in advance, or a large language model capable of outputting a desired result by inputting a prompt.

[0013] Also, in one embodiment, the "unit" may include, for example, hardware resources implemented by a circuit in a broad sense and information processing of software that can be specifically realized by these hardware resources. Also, in one embodiment, various types of information are handled, and these information are represented, for example, by physical values of signal values representing voltage and current, the high and low of signal values as a set of binary bits composed of 0 or 1, or quantum superposition (so-called quantum bits), and communication and calculation can be executed on a circuit in a broad sense.

[0014] Furthermore, a circuit in a broad sense is a circuit realized by appropriately combining at least a circuit, circuitry, a processor, a memory, etc. The processor may be a general-purpose processor or a dedicated circuit. That is, it includes application specific integrated circuits (ASICs), programmable logic devices (e.g., simple programmable logic devices (SPLDs), complex programmable logic devices (CPLDs), and field programmable gate arrays (FPGAs)), etc.

[0015] 1. Hardware Configuration In this section, the hardware configuration will be described.

[0016] <Information Management System 1> Figure 1 is a configuration diagram showing Information Management System 1. Information Management System 1 includes a communication line 2, a server device 10, a plurality of administrator terminals 20, and a plurality of managed person terminals 30. The server device 10, the administrator terminals 20, and the managed person terminals 30 are configured to be communicable through the communication line 2. The connections of the server device 10, the administrator terminals 20, and the managed person terminals 30 to the communication line 2 may be wired or wireless.

[0017] Information Management System 1 constitutes a part of a personnel system used by the personnel to be managed (a plurality of managed persons) within an organization and a plurality of administrators having a relationship with the managed persons within the organization. "Administrators" include persons on the reporting line of the managed persons (e.g., supervisors, line managers, etc.), personnel administrators, etc. Note that the "managed persons" in Information Management System 1 can also be the "administrators" of other managed persons.

[0018] The information management system 1 supports the creation of human resource management documents for the persons to be managed. In one embodiment, the information management system 1 consists of one or more devices or components. Hereinafter, these components will be described.

[0019] <Server device 10> FIG. 2 is a block diagram showing the hardware configuration of the server device 10. The server device 10 includes a control unit 11, a storage unit 12, a communication unit 13, and a communication bus 14. The control unit 11, the storage unit 12, and the communication unit 13 are electrically connected inside the server device 10 via the communication bus 14.

[0020] <Control unit 11> The control unit 11 performs processing and control of the overall operations related to the server device 10. The control unit 11 is, for example, a Central Processing Unit (CPU). The control unit 11 realizes various functions related to the server device 10 by reading a predetermined program stored in the storage unit 12. That is, the information processing by the software stored in the storage unit 12 is specifically realized by the control unit 11, which is an example of hardware, and can be executed as each functional unit included in the control unit 11. These will be described in more detail in the next section. Note that the control unit 11 is not limited to being single, and may be implemented to have a plurality of control units 11 for each function, or a combination thereof.

[0021] <Storage unit 12> The storage unit 12 stores various information defined as described above. This can be implemented, for example, as a storage device such as a Solid State Drive (SSD) that stores various programs and the like related to the server device 10 executed by the control unit 11, or as a memory such as a Random Access Memory (RAM) that stores temporarily necessary information (arguments, arrays, etc.) related to the calculation of programs. The storage unit 12 stores various programs, variables, etc. related to the server device 10 executed by the control unit 11.

[0022] <Communication unit 13> The communication unit 13 preferably uses wired communication means such as USB, IEEE1394, Thunderbolt (registered trademark), and wired LAN network communication. However, wireless LAN network communication, mobile communication such as 3G / LTE / 5G, and BLUETOOTH (registered trademark) communication may be included as needed. That is, it is more preferably implemented as a set of these multiple communication means. That is, the server device 10 may communicate various information from the outside via the communication unit 13 and the network.

[0023] The server device 10 may be in an on-premises form or a cloud form. As the server device 10 in the cloud form, for example, it may provide the above-described functions and processes in the form of Software as a Service (SaaS) or cloud computing.

[0024] <Administrator terminal 20> FIG. 3 is a block diagram showing the hardware configurations of the administrator terminal 20 and the terminal 30 of the person to be managed. As shown in FIG. 3A, the administrator terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, an output unit 25, and a communication bus 26. The control unit 21, the storage unit 22, the communication unit 23, the input unit 24, and the output unit 25 are electrically connected inside the administrator terminal 20 via the communication bus 26. The descriptions of the control unit 21, the storage unit 22, and the communication unit 23 are omitted because they are the same as the descriptions of the respective units in the server device 10.

[0025] <Input unit 24> The input unit 24 receives operation inputs made by the user. The operation inputs are transferred as command signals to the control unit 21 via the communication bus 26. The control unit 21 can execute predetermined control and calculations based on the transferred command signals as necessary. The input unit 24 may be included in the housing of the administrator terminal 20 or may be externally attached. For example, the input unit 24 may be implemented as a touch panel integrated with the output unit 25. When the input unit 24 is implemented as a touch panel, the user can input tap operations, swipe operations, etc. to the input unit 24. As the input unit 24, instead of a touch panel, a switch button, a mouse, a track pad, a QWERTY keyboard, etc. can be adopted.

[0026] <Output unit 25> The output unit 25 displays a screen of a graphical user interface (GUI) operable by the user. The output unit 25 may be included in the housing of the administrator terminal 20 or may be externally attached. Specifically, the output unit 25 can be implemented as a display device such as a CRT display, a liquid crystal display, an organic EL display, or a plasma display. These display devices are preferably used separately according to the type of the administrator terminal 20.

[0027] <Terminal 30 of the person to be managed> As shown in FIG. 3B, the managed person terminal 30 includes a control unit 31, a storage unit 32, a communication unit 33, an input unit 34, an output unit 35, and a communication bus 36. The control unit 31, the storage unit 32, the communication unit 33, the input unit 34, and the output unit 35 are electrically connected via the communication bus 36 inside the managed person terminal 30. The descriptions of the control unit 31, the storage unit 32, the communication unit 33, the input unit 34, and the output unit 35 are omitted because they are the same as the descriptions of the respective units in the administrator terminal 20.

[0028] 2. Functional Configuration In this section, the functional configuration of this embodiment will be described. Information processing by software stored in the storage unit 12 is specifically realized by the control unit 11, which is an example of hardware, and thus can be executed as each functional unit included in the control unit 11 (the processor included in the information management system 1).

[0029] FIG. 4 is a block diagram showing the functions realized by the server device 10 (control unit 11), the administrator terminal 20 (control unit 21), and the managed person terminal 30 (control unit 31).

[0030] As shown in FIG. 4A, the server device 10 (control unit 11) includes a reception unit 111, a creation unit 112, a public reception unit 113, a publication unit 114, a display control unit 115, an editing unit 116, an artificial intelligence unit 117, a condition setting unit 118, and a notification unit 119. As shown in FIG. 4B, the administrator terminal 20 (control unit 21) includes a display unit 211 and an operation reception unit 212. As shown in FIG. 4C, the managed person terminal 30 (control unit 31) includes a display unit 311 and an operation reception unit 312.

[0031] <Reception Unit 111> The reception unit 111 is configured to receive various types of information. In a typical embodiment, the reception unit 111 of the server device 10 receives instructions, requests, etc. based on operations from the administrator terminal 20 and the managed person terminal 30. In this embodiment, the reception unit 111 receives registration information related to managed persons working in the organization, which is registered in a database within the organization. Note that the reception of this registration information is triggered by a terminal operation by a person inputting information within the organization. Here, the "person inputting information within the organization" includes the administrator and the managed person.

[0032] Those to be managed are, for example, employees of an organization (full-time employees, temporary employees, and fixed-term employees). An internal database is a database that can only be accessed by those involved with the organization, and data is not made public or provided to anyone outside the organization. Organizations include for-profit corporations (such as companies), non-profit corporations (such as cooperatives and foundations), and public corporations (such as local governments).

[0033] The databases within the organization include a personnel database. FIG. 5 is a block diagram showing an example of the configuration of the personnel database D10. The personnel database D10 includes, for example, a basic information database D101, a goal evaluation database D102, a position database D103, a skill database D104, a recruitment database D105, a condition survey database D106, an organization diagnosis survey database D107, an original survey database D108, an interview database D109, and an attendance database D110. Each of these databases stores and accumulates data (registration information) of individual persons to be managed. The recruitment database D105 stores recruitment data for new graduates and mid-career recruits. The position database D103 and the skill database D104 may be part of the basic information database D101 or the goal evaluation database D102.

[0034] The registration information regarding the persons to be managed stored in the personnel database D10 is personnel information and is classified into a plurality of categories. Examples of "categories" include, for example, the name, gender, age, employee code, contact information, department, employment form, workplace, job, goals within the organization set by the person to be managed, evaluations from the manager regarding the goals, information before the person to be managed belonged to the organization (information at the time of employment), the condition of the person to be managed, engagement (e.g., eNPS), the aptitude or personality of the person to be managed, the interview history of the person to be managed (interviewer, content of remarks, etc.), the attendance information of the person to be managed (overtime hours, number of annual leave taken, etc.), and the like. The information at the time of employment includes the offered position at the time of employment, annual income, interviewing officer in charge of employment, evaluation at the time of employment, aptitude test results, reference check information, and the like. Note that information other than the information at the time of employment is information after belonging to the organization (information after employment).

[0035] The categories of the registration information are distinguished by a plurality of attributes. Examples of the attributes for distinguishing categories include, for example, the registration time of the information reflected by the registration information, the description method of the information, and the like. In the example of the registration time, basic information such as name, gender, and age is information at the time of employment or transfer to the organization. Also, the goals and evaluations are information at the times when they are respectively implemented, and the registration times of the goals and evaluations are different from each other. Furthermore, the information at the time of employment is information before employment in the organization. Therefore, these pieces of information are classified into different categories. On the other hand, in the example of the description method of the information, information described by keywords or numerical values (e.g., name, department, job, etc.) and information described in sentences (e.g., work content, goals, evaluations, conditions, etc.) are distinguished. Therefore, the former information and the latter information are classified into different categories. Furthermore, as an attribute for distinguishing categories, whether the information is unique or not is also exemplified. Examples of unique information include the name and the like. Examples of non-unique information include gender, department, job, and the like. Also, the categories of the registration information may be arbitrarily set by the user without being limited to the distinction by the above-described attributes.

[0036] The personnel database D10 includes both a sub-database containing information of one category (for example, the basic information database D101) and a sub-database containing information of multiple categories (for example, the target evaluation database D102).

[0037] <Creation unit 112> Based on the information received as the server device 10, the creation unit 112 creates various types of information. In the present embodiment, the creation unit 112 creates a first document regarding a human resource management document including document components derived from the registration information. Here, the document components include sentences created based on the registration information. Here, this "first document" is positioned as a draft (manuscript) of the "human resource management document" described later. Further, through the process of "publication" described later, this "first document" will be publicly released within a predetermined range as the "human resource management document".

[0038] Note that even when there is an already publicly released human resource management document for a certain management target, the creation unit 112 may create a new first document for the same management target so as to coexist with the publicly released human resource management document.

[0039] Also, in a typical mode, the creation unit 112 creates the first document by inputting the registration information received by the reception unit 111 into the artificial intelligence module and outputting the document components. Regarding the "artificial intelligence module" here, it will be described below as the artificial intelligence unit 117 of the server device 10, but it is not limited to this. The first document may be created by inputting predetermined registration information into an artificial intelligence module existing outside the server device 10. Note that the first document can also be created by other modes than inputting the received registration information into the artificial intelligence module. In an exemplary mode, the creation unit 112 may create the first document from the received registration information based on a pre-defined rule base. Other specific processes regarding the creation of the first document will be described later.

[0040] <Publication reception unit 113> The public reception unit 113 receives a public disclosure request from the person to be managed and / or the administrator of the person to be managed to publicly disclose the first document or the edited version of the first document within a predetermined range. The specific process will be described later.

[0041] <Publication unit 114> Based on the receipt of the public disclosure request, the publication unit 114 publicly discloses the first document or the edited version within a predetermined range as a human resource management document. Here, the human resource management document is an in-organization resume (for example, a document that aggregates registration information) based on the registration information of the person to be managed registered in the personnel database, and is typically provided for viewing within a predetermined range. The range (predetermined range) for publicly disclosing this human resource management document can be arbitrarily set according to the purpose of utilizing the human resource management document. For example, a mode where only the department (personnel department) to which the administrator belongs and the decision-makers related to personnel (for example, the management level) can view the human resource management document, and others (including the person to be managed himself / herself) cannot view it, is also an example of the mode of publicly disclosing the human resource management document within a predetermined range. Separately from this, a mode where both the administrator and the person to be managed can view the human resource management document is also an example of the mode of publicly disclosing the human resource management document within a predetermined range. This setting of the predetermined range is, for example, set by the administrator. Also, the predetermined range may be automatically set according to the access rights of employee information, etc. In a typical example, the publication unit 114 executes the public disclosure of the human resource management document so that only those who have access rights to the employee information included in the publicly disclosed human resource management document can view the predetermined information. Further, the publication unit 114 may set viewable conditions for each item of the human resource management document. For example, for a specific item of the human resource management document, the public disclosure may be performed so that only those who have access rights to the employee information related to the specific item can view it. In this case, for items other than the specific item, the public disclosure may be performed within a range not related to the above access rights. Furthermore, the publication unit 114 may set viewable conditions for each document component of the human resource management document.

[0042] Furthermore, the predetermined range here is typically a range that extends the range within which public requests can be accepted. As described above, public requests can be received from the person to be managed and / or the administrator of the person to be managed. However, the public disclosure unit 114 discloses the human resource management document so that the human resource management document can be viewed not only by the person to be managed and / or the administrator but also by other persons. Also, in a typical aspect, the human resource management document is provided for viewing within the organization. That is, the human resource management document may not be disclosed outside the organization. By creating a human resource management document for each person to be managed, it becomes possible for administrators and the like to easily conduct a human resource search within the organization using keywords, conditions (parameters), and the like. The human resource management document is referred to, for example, in strategic personnel transfers, internal recruitment, utilization of inactive human resources, and support for career inventory. Specific processes regarding this disclosure and more specific aspects regarding the human resource management document will be described later.

[0043] <Display control unit 115> The display control unit 115 is configured to generate various display information and control the display content that can be visually recognized by the user. Note that the display information may be the information itself generated in a form that can be visually recognized by the user, such as a screen, an image, an icon, or text, or may be rendering information for displaying a screen, an image, an icon, text, etc. on various terminals. In the present embodiment, the display control unit 115 displays the status regarding the creation status of the human resource management document for a plurality of persons to be managed in a list form for the administrator. Specific processes regarding this display control will be described later.

[0044] <Editing unit 116> The editing unit 116 generates an edited product by receiving an edit to the first document created by the creation unit 112 from the person to be managed and / or the administrator. Specific processes regarding this edit will be described later.

[0045] <Artificial intelligence unit 117> The artificial intelligence unit 117 is configured to receive inputs from each functional unit and return the instructed outputs. Note that the artificial intelligence used by the server device 10 in each functional unit may be common or may be individually prepared for each functional unit.

[0046] The artificial intelligence unit 117 is an AI (Artificial Intelligence) equipped with language models such as transformers (including GPT (Generative Pretrained Transformer, including GPT-1, GPT-2, GPT-3), BERT (Bidirectional Encoder Representations from Transformers), BART (Bidirectional and Auto-regressive Transformer), etc.) and recurrent neural networks (Recurrent Neural Network (RNN)), including generative AI.

[0047] The language model is an example of a learning model by a machine learning algorithm. Specific algorithms for machine learning include the nearest neighbor method, the naive Bayes method, decision trees, support vector machines, and deep learning (deep neural networks) using neural networks. The artificial intelligence unit 117 can appropriately apply the above algorithms.

[0048] The artificial intelligence unit 117 has a trained model constructed by a learning method such as supervised learning, unsupervised learning, or self-supervised learning. In supervised learning, machine learning is performed using teacher data (learning data). The teacher data is composed of a pair of input data for learning and output data (correct data). Also, the language model may be a general-purpose model that can be used generally for a wide range of tasks, not just trained for a specific task.

[0049] The artificial intelligence unit 117 includes, as artificial intelligence, general-purpose natural language processing learning models such as large language models (LLMs) that have learned a vast amount of data. Such general-purpose learning models include language models that can handle various tasks without fine-tuning through One-shot Learning, Few-shot Learning, etc. Also, general-purpose learning models can handle various tasks through Zero-shot Learning. The artificial intelligence used in each functional unit of the control unit 11 may be separate learning models or a common general-purpose learning model.

[0050] The learning model included in the artificial intelligence unit 117 is capable of performing additional learning. For example, the artificial intelligence unit 117 learns whether the created human resource management document has been corrected by the creator or the like. That is, the artificial intelligence unit 117 performs additional learning and is fine-tuned using a teacher dataset in which the actual correction results are labeled on the human resource management document as feedback on the human resource management document created by the learning model. As a result, the human resource management document output from the learning model is optimized.

[0051] <Condition setting unit 118> The condition setting unit 118 is configured to set editable conditions for the publicly available human resource management document according to the terminal operation by the input person. Thereby, the management level of the human resource management document can be flexibly adjusted according to the input person.

[0052] The editable conditions can be set as appropriate according to the purpose of the human resource management document. For example, when the input person is an administrator (e.g., the personnel department), a condition that makes it impossible to edit for all people can be cited as an example of the editable conditions. Also, the editable conditions may be conditions that make it impossible to edit except for the person being managed himself / herself when the input person is the person being managed himself / herself or regardless of the input person, and only the person being managed himself / herself can edit.

[0053] Further, the condition setting unit 118 may set editable conditions for each item of the human resource management document. For example, when the inputter is an administrator, only specific items may be made editable, and the other items may be made non - editable for all. Furthermore, the condition setting unit 118 may set viewable conditions or editable conditions for each document component.

[0054] <Notification unit 119> The notification unit 119 is configured to notify various information to various terminals with which the server device 10 can communicate. In one aspect of the present embodiment, when there is an existing first document or an edited document for any of a plurality of management targets, the notification unit 119 notifies the administrator that a new first document is to be created in place of the existing first document or the edited document. Also, in another aspect of the present embodiment, the notification unit 119 notifies the administrator that the first document or the edited document that has received a publication request is to be published as a human resource management document in place of the published human resource management document. Specific processing regarding these notifications will be described later.

[0055] <Display unit> The display unit 211 of the administrator terminal 20 and the display unit 311 of the management target terminal 30 each display the screen indicated by the screen data transmitted from the server device 10.

[0056] <Operation reception unit> The operation reception unit 212 of the administrator terminal 20 receives operations by the user (administrator) using the administrator terminal 20. The operation reception unit 312 of the management target terminal 30 receives operations by the user (management target) using the management target terminal 30.

[0057] 3. Information processing method In this section, the information processing method of the server device 10 will be described. This information processing method is executed by a computer for each step by each part of the server device 10.

[0058] The information management method described below allows an administrator to create a first document for a plurality of management targets in a batch. Regarding this information management method, the outline of information processing, the details of the creation process of the first document, and the details and order of the first document will be described in sequence.

[0059] (Outline of Information Processing) First, the outline of information processing in the information management method of this embodiment will be described while showing an activity diagram. FIG. 6 is an activity diagram showing the outline of the information management method of this embodiment.

[0060] In the information management method of this embodiment, first, a predetermined management screen is displayed on the administrator terminal 20 (Activity A101). FIG. 7 is an example of the management screen displayed on the administrator terminal 20. As described above, the display control unit 115 of the server device 10 can display the status regarding the creation status of the human resource management documents for a plurality of management targets in a list for the administrator, and such information is displayed on the management screen shown in FIG. 7. Specifically, on the management screen shown in FIG. 7, a list of management targets who are the subjects of resume (in-house management document) creation is shown. On the management screen in FIG. 7, in addition to the name NM of each management target, the status STT regarding the creation status of the human resource management document, the attribute AT of the management target, and the details DT regarding the human resource management document are shown in association with each management target.

[0061] The status STT regarding the creation status of the human resource management document may include, for example, the status where each management target has not created the first document and the human resource management document (not created), the status where each management target has created up to the first document and has not published it as the first management document (draft), the status where each management target has already published the human resource management document (published), etc.

[0062] In addition, the attribute AT of the person to be managed may include attributes such as the main duties, concurrent duties, rank, job type, position, and workplace of each person to be managed. Of course, the attributes of the person to be managed displayed on the administrator terminal are not limited to this, and may include various items such as gender, age, and employment date. In the management screen of FIG. 7, for the person to be managed, sorting and display can be performed according to the above-mentioned status STT and attribute AT. As a result, the administrator can efficiently narrow down the persons to be managed.

[0063] The detailed DT regarding the human resource management document indicates whether the person to be managed can view the human resource management document or the draft of the human resource management document. In the example of the management screen in FIG. 7, the document with the status of "draft" or "published" can be viewed, and the button labeled "Details" is displayed in a different manner from other persons to be managed in the "not created" state. In such a manner, the administrator who accesses the management screen in FIG. 7 can view the corresponding document (the first document or the human resource management document) by pressing the "Details" button for the person to be managed in the "draft" or "published" state regarding the status STT of the creation status of the human resource management document.

[0064] In addition, in the management screen of FIG. 7, a check box CB associated with each person to be managed is shown. When performing processing related to the human resource management document, the administrator can select the person to be managed as the processing target using this check box CB. In this way, by selecting the person to be managed as the processing target and pressing the button BT1, batch processing related to the human resource management document can be executed.

[0065] In the management screen of FIG. 7, a mode of collectively creating drafts (first documents) of human resource management documents for the selected management target is shown. That is, after the management target is selected and the button BT1 labeled "Collective Creation" is pressed, the server device 10 will receive an instruction to create the first document (see Activity A102-103). Here, "Collective Creation" refers to creating a plurality of first documents with a single instruction. That is, "Collective Creation" is not limited to the simultaneous creation of a plurality of first documents, but also includes a mode in which a plurality of first documents to be created are sequentially created.

[0066] Note that the content of the processing of button BT1 can be set as appropriate. Specifically, for the specified management target, a plurality of human resource management documents can be publicly released collectively, or for the specified management target, a plurality of human resource management documents can be made non-public collectively. In addition, based on the operation of button BT1, a plurality of first documents and / or human resource management documents can be deleted collectively for the specified management target.

[0067] In this way, when a creation instruction for the first document is issued from the administrator terminal 20, the server device 10 will receive the instruction (Activity A104). Then, based on this creation instruction, the server device 10 acquires predetermined registration information and executes a process of creating the first document (Activities A105-107). That is, the reception unit 111 of the server device 10 receives from the administrator terminal 20 an input of a collective creation instruction for the first document for a plurality of management targets, and the creation unit 112 will create the first document for each of the plurality of management targets.

[0068] Note that prior to the execution of such a first document creation process, a caution screen CS as shown in FIG. 8 may be displayed on the administrator terminal 20. FIG. 8 is an example of the caution screen CS displayed on the administrator terminal 20.

[0069] As described above, when there is an existing first document or edited document for any of a plurality of management targets, the notification unit 119 can notify the administrator that a new first document is to be created in place of the existing first document or edited document. The caution screen CS in FIG. 8 notifies the administrator that a new first document is created (overwritten) in such a manner. Further, in the information management system 1 of the present embodiment, a limit on the number of times of input of a batch creation instruction in a predetermined period may be provided in the organization. Thereby, it becomes easier to realize information management while optimizing the cost of information processing. Such a limit on the number of times may also be shown on the caution screen CS. Note that the number of times of the limit on the number of times here can be arbitrarily set. As an example, it is set for each predetermined period (for example, annually, quarterly, etc.) according to the scale of the organization and the like. Although three items related to the above are shown as the caution screen CS in FIG. 8, the number of items shown on the caution screen CS may be less than or more than this number of items. That is, the caution screen CS may show only one of the above-described processing when there is an existing first document or edited document and the limit on the number of times of batch creation instructions in the organization. Of course, although not explicitly stated in this specification, when there are useful matters in operating the system within the organization, the relevant useful matters may be separately shown on the caution screen CS.

[0070] In addition, the administrator who has accessed such a caution screen CS can, after confirming the notified matters, press the button BT2 to proceed with the batch creation process of the first document. In other words, by causing the administrator to press the button BT2, it is possible to prompt the administrator to confirm and approve the creation of the first document and the creation of a new first document in place of the existing first document or the like. Note that in the caution screen CS, it may be configured to return to the previous screen (management screen) when the button BT3 is pressed.

[0071] On the one hand, such a notice may be given only to the administrator, or may be given to the persons to be managed in addition to the administrator. In the above, regarding creating the first document and creating a new first document in place of an existing first document or the like, the mode of execution with the administrator's approval was shown. However, in one aspect, the system may be constructed to obtain confirmation or approval from the persons to be managed regarding creating such a first document and creating a new first document in place of an existing first document or the like. Note that such a notice may also be given when batch deleting the first document and / or the human resource management document described above. That is, when the administrator attempts to batch delete the first document and / or the human resource management document, a predetermined caution screen may be shown to the administrator, and the system may be configured to obtain approval or confirmation regarding batch deleting the first document and / or the human resource management document. Also, regarding such batch deletion, the system may be constructed to obtain confirmation or approval from the persons to be managed regarding the first document and / or the human resource management document being deleted.

[0072] Although the details of the process regarding creating the first document will be described later, by executing this creation process for each person to be managed, a plurality of first documents can be created in a batch. Also, each of the first documents created by the creation unit 112 is displayed on the administrator terminal 20 and / or the person-to-be-managed terminal 30 (see activity A108-109).

[0073] FIG. 9 is a diagram showing an example of the first document FD. FIG. 10 is a diagram showing a part of the first document FD different from that in FIG. 9. FIG. 11 is a diagram showing a part of the first document FD different from those in FIGS. 9 and 10. FIG. 12 is a diagram showing a part of the first document FD different from those in FIGS. 9 to 11. As shown in FIGS. 9 to 12, the first document FD includes a header HD and a plurality of document components (first document component DC1 and second document component DC2). The header HD describes the name, thumbnail (e.g., face photo), affiliation, etc. of the administrator target person. Note that the first document FD shown in FIGS. 9 to 12 is the document seen from the person-to-be-managed terminal 30, and when the first document FD is seen from the administrator terminal 20, some information may be increased or deleted.

[0074] In the first document FD of FIG. 9, a button BT4 is shown, which is a button used for editing the first document. As described above, the editing unit 116 of the server device 10 is configured to generate an edited document by receiving an edit for the first document FD created by the creation unit 112 from the person to be managed and / or the administrator. However, when a user (typically an administrator or a person to be managed, also referred to as an "editor") who touches FIG. 9 presses this button BT4, it is configured to transition to a predetermined edit screen. In this specification, a document obtained by artificially editing the first document FD created by the creation unit 112 may also be referred to as an "edited document". Further, hereinafter, the first document FD and the edited document may be collectively referred to as "the first document FD and the like".

[0075] Specific processing related to editing will be described. After the creation unit 112 creates the first document FD, the editing unit 116 displays a screen for receiving an edit for this first document FD. Further, the editing unit 116 may receive edits (inputs) step by step for each item of the first document FD. FIG. 13 is a diagram showing an example of the edit screen ED. At the upper part of the edit screen ED, a step ST indicating the progress of the edit is displayed. In the example of FIG. 13, in step ST, it is shown that the edits for two items, "basic information" and "external work history", are completed, that the third item, "internal work history", is currently being edited, and that there are two remaining items ("career summary" and "others") after "internal work history". Also, on the edit screen ED, an edit button EB is arranged for each item generated by the creation unit 112 or for each more subdivided edit unit of the item. By inputting an operation to the edit button EB, the corresponding description item can be edited. The editing of the description item is executed, for example, by inputting a sentence or a word from the administrator terminal 20 or the person-to-be-managed terminal 30, selecting a tag from tag candidates, or the like. For example, the editing unit 116 may display a list of tags extracted from the registered information as tag candidates. Thereby, the user can edit the tag to be arranged in the first document FD by selecting an arbitrary tag from the list of displayed tag candidates.

[0076] When the editing of one item is completed, for example, by clicking the completion button, the editing unit 116 causes the editing screen ED of the next item to be displayed in the order shown in step ST. The editing unit 116 switches the editing screen ED to be displayed on the administrator terminal 20 or the managed person terminal 30 for each item of the human resource management document in this way, and accepts editing for each item. Thereby, for example, it is possible to accept editing while conforming to the mental model (what one wants to do or what one can understand) of the person to be managed.

[0077] Further, the editing unit 116 may accept the editing of each item on the screen where the entire first document FD is displayed without switching the editing screen ED for each item.

[0078] Regarding the editing of the first document FD as described above, restrictions may be provided on the editing authority. In a typical aspect, the range in which the first document FD can be edited is narrower than the range in which the disclosure unit 114 discloses the human resource management document. Also, in one aspect, the first document FD may be configured to be editable only by the person to be managed and / or the administrator of the person to be managed, or may be configured to be editable only by the person to be managed. That is, in one aspect, it is assumed that the range in which the first document FD can be edited is narrower than the range in which a public request for the first document FD or the like can be made. As a typical example, it is assumed that the range in which the first document FD can be edited is only the person to be managed and some limited administrators, and the range in which a public request for the first document FD or the like can be made is the range including the person to be managed and the administrator. Also, the editing authority and the disclosure range may be arbitrarily set by the user.

[0079] Note that this editing authority may be configured to vary according to the processing executed by the information management system 1. As an example, the editing unit 116 may be configured to limit the editing authority for the edited material to only the person to be managed, triggered by accepting the editing of the first document FD by the person to be managed. By adopting such an aspect, it becomes easier to reflect the intention of the person to be managed in the first document FD or the like.

[0080] Also, as shown in FIG. 9, various tags TG1 may be attached to the header HD of the first document FD. This tag TG1 may be related to at least one of the number of times the first document FD has been edited, the creator of the first document FD, the editor of the first document FD, the status regarding the creation status of the human resource management document, and the status regarding the public information of the human resource management document. In the example shown in FIG. 9, the status regarding the public status of the human resource management document is indicated by a tag of "non-public". Also, the status regarding the creation status of the human resource management document is indicated by a tag of "draft". Furthermore, the creator of the first document FD is indicated by a tag of "generated by AI". Note that when the above-described editing is performed by the person to be managed and / or the administrator of the person to be managed, the tag of "generated by AI" may be configured to disappear. That is, when the first document FD shown in FIG. 9 is the document itself created by the functions of the creation unit 112 and the artificial intelligence unit 117, it may be configured such that a tag of "generated by AI" is attached. In that case, the tag of "generated by AI" can indicate the number of times the first document FD has been edited (the number of times of editing is zero) and the editor of the first document FD (substantially no editing (update) of the first document FD has been performed). Note that instead of the tag TG1 with the notation of "generated by AI" in FIG. 9, a tag with the notation of "automatically generated" may be attached. This tag with the notation of "automatically generated" can indicate a tag indicating the first document FD generated by the functions of the creation unit 112 and the artificial intelligence unit 117, while it can also be attached when the first document FD is mechanically created based on a pre-defined rule base without the creation unit 112 using the artificial intelligence unit 117 (AI). Also, when the first document FD is edited by a predetermined person (for example, the person to be managed), the fact that this editing has been performed can also be indicated in the header HD as the tag TG1. Tags TG1 shown in such a case include, for example, a tag indicating the person who performed the latest editing (update), a tag indicating the date and time of the editing history up to the present, a tag indicating version information, and the like. By displaying the tags TG1 as described above, it becomes easier to manage various documents.

[0081] Note that this tag TG1 may also be displayed even when the first document FD or the like is published. That is, in the human resource management document which is a publication of the first document FD or the like, tags related to at least one of the number of edits of the first document FD, the creator of the first document FD, the editor of the first document FD, the status regarding the creation status of the human resource management document, and the status regarding the publication status of the human resource management document may be displayed.

[0082] Returning to the flow of information processing. After the first document FD or the like is displayed as described above, the server device 10 receives a publication request from the user who has accessed the first document FD or the like, and publishes the first document FD or its edited version as a human resource management document within a predetermined range (Activity A110-112).

[0083] This publication request may be made by the person to be managed or by the administrator. That is, when receiving a publication request from the person to be managed, based on this publication request, the first document FD or the edited version of the person to be managed is published within a predetermined range. This publication request by the person to be managed may be achieved, for example, by pressing a button BT5 indicating "publication" in the first document FD shown in FIG. 9.

[0084] Also, when a publication request is made by the administrator, after the administrator designates the first document FD or the like to be published, by making the publication request, the designated first document FD or the like is published within a predetermined range.

[0085] On the other hand, the server device 10 may be configured to publish the first document FDs of a plurality of persons to be managed all at once. Specifically, the publication reception unit 113 of the server device 10 can also receive a publication request from the administrator regarding a plurality of first document FDs or edited versions. Correspondingly, the publication unit 114 can also publish a plurality of first document FDs and / or edited versions within the predetermined ranges corresponding to each of them.

[0086] Such batch document disclosure may be performed via operations on a management screen shown in FIG. 7, for example. Although the button BT1 in FIG. 7 is shown as a mode for performing "batch creation", by switching this mode to the content of "batch disclosure" and the administrator pressing the button BT1, human resource management documents for a plurality of management targets can be disclosed.

[0087] In addition, when a human resource management document that has already been disclosed within a predetermined range coexists with the first document FD or the edited material for a management target, the disclosure unit 114 may be configured to disclose the first document FD or the edited material that has received a disclosure request as a human resource management document instead of the disclosed human resource management document. That is, when the human resource management document and the first document FD coexist as described above, usually, the first document FD or the edited material often contains new information about the management target. From this perspective, the first document FD or the edited material that has received disclosure can be disclosed as a new human resource management document.

[0088] Further, the notification unit 119 may notify the administrator that the first document FD or the edited material that has received a disclosure request is disclosed as a human resource management document instead of the disclosed human resource management document. This makes it less likely for the administrator to cause an error when performing batch disclosure. Such a notification may be performed via a caution screen CS as shown in FIG. 8, for example.

[0089] On the other hand, such a notification may be made only to the administrator, or may be made to the management targets in addition to the management targets. Also, in one aspect, a system may be constructed to obtain confirmation and consent from the management targets regarding the disclosure of such a first document FD or edited material as a human resource management document.

[0090] Also, in the information management system 1 of this embodiment, the disclosed human resource management documents may be configured to be made non-public in a batch by an administrator's operation. For this operation, for the button BT1 in FIG. 7, the content is switched to "Batch Non-Public", and when the administrator presses the button BT1, the human resource management documents for a plurality of management targets can be made non-public. Here, the non-public state is exemplified when the public range corresponds to the range corresponding to the first document FD and the like.

[0091] (Details of the creation process of the first document FD) Subsequently, the details of the creation process of the first document FD will be described. The first document FD, which is positioned as a draft (in progress) of the human resource management document, is composed of a plurality of document components. In a typical aspect, the document components include a first document component that is a keyword included in the registration information, and a second document component that includes a sentence created based on the registration information. As shown in FIG. 5, the creation unit 112 acquires the first registration information RI1 or the second registration information RI2 from a plurality of databases included in the personnel database D10.

[0092] The creation unit 112 extracts the keyword included in the first registration information RI1 among the registration information as the first document component DC1, and creates a sentence created based on the second registration information RI2 different from the first registration information RI1 among the registration information as the second document component DC2. That is, in this embodiment, it is desirable to receive registration information of two or more categories regarding the management targets engaged in the organization, and thereby create the first document FD. The creation unit 112 selects a conversion procedure of the registration information into the document components according to the form or category of the registration information. Thereby, while appropriately converting a plurality of registration information with different categories into the elements of the human resource management document, they can be integrated into one document.

[0093] The first registration information RI1 is the registration information among the registration information registered in the database that is converted into the first document component DC1 or the second document component DC2 by the creation unit 112. The first registration information RI1 is information described by keywords or numerical values. Examples of the first registration information RI1 include basic information obtained from the basic information database D101, position information obtained from the position database D103, skill information obtained from the skill database D104, conditions obtained from the condition survey database D106, eNPS obtained from the organizational diagnosis survey database D107, propriety or personality obtained from the original survey database D108, and the like. The creation unit 112 may generate a plurality of first document components DC1 from the first registration information RI1 of one category, or may generate one first document component DC1 from the first registration information RI1 of a plurality of categories.

[0094] The second registration information RI2 is the registration information among the registration information registered in the database that is converted into the first document component DC1 or the second document component DC2 by the creation unit 112. The second registration information RI2 is information described in text. Examples of the second registration information RI2 include goals or evaluations obtained from the target evaluation database D102, recruitment information obtained from the recruitment database D105, 1on1 history obtained from the interview database D109, attendance information obtained from the attendance database D110, and the like.

[0095] As shown in FIG. 5, the creation unit 112 may generate a plurality of second document components DC2 from the second registration information RI2 of one category, or may generate the first document component DC1 and the second document component DC2 from the second registration information RI2 of one category.

[0096] The extraction of the first document component DC1 from the first registration information RI1 is performed by referring to first reference information including the correlation between the first registration information RI1 and the first document component DC1. As the first reference information, for example, an extraction item list is used. In the extraction item list, for example, candidates (samples) for each item such as department and job are described, and the creation unit 112 extracts keywords corresponding to each item from the registration information and uses them as the first document component DC1. Therefore, the first document component DC1 may include a plurality of keywords.

[0097] Also, as the first reference information, a keyword extraction model, which is a learning model (machine learning or fine-tuning) trained to take the first registration information RI1 as input and output the first document component DC1, may be used. For example, the keyword extraction model is a learning model trained using the first registration information RI1 and the corresponding first document component DC1 as teacher data. The creation unit 112 inputs the first registration information RI1 into the keyword extraction model of the artificial intelligence unit 117 and causes the keyword extraction model to output the first document component DC1. Also, the keyword extraction model may be a generative AI including a large language model. In this case, the creation unit 112 inputs an instruction to extract keywords from the first registration information RI1 and a prompt inserted with the first registration information RI1 into the keyword extraction model and causes the keyword extraction model to output the first document component DC1. Also, in addition to the keyword extraction instruction and the first registration information RI1, the creation unit 112 may input a prompt inserted with, for example, one or more samples of the first registration information RI1 and one or more samples of the corresponding first document component DC1 into the keyword extraction model.

[0098] The second document component DC2 includes a newly created sentence using the keywords included in the registration information. The second document component DC2 is a summary of the sentence included in the second registration information RI2, a sentence reconstructed using the keywords included in the second registration information RI2, or a sentence newly constructed using the keywords included in the first registration information RI1.

[0099] Creation of the second document component DC2, which is a summary of the text included in the second registration information RI2, is performed by referring to second reference information including the correlation between the second registration information RI2 and the second document component DC2. As the second reference information, for example, a summary creation model, which is a learning model trained to take the second registration information RI2 as input and output the second document component DC2, is used. For example, the summary creation model is a learning model trained using the second registration information RI2 and the corresponding second document component DC2 as teacher data. The creation unit 112 inputs the second registration information RI2 into the summary creation model of the artificial intelligence unit 117 to cause the summary creation model to output the second document component DC2. Also, the summary creation model may be a generative AI including a large language model. In this case, the creation unit 112 inputs a prompt inserted with an instruction to summarize the text included in the second registration information RI2 and the second registration information RI2 into the summary creation model to cause the summary creation model to output the second document component DC2. Further, in addition to the summary creation instruction and the second registration information RI2, the creation unit 112 may input into the summary creation model a prompt inserted with, for example, one or more samples of the second registration information RI2 and one or more samples of the corresponding second document component DC2.

[0100] Also, as described above, the creation unit 112 may create a new sentence by combining a plurality of keywords included in the first registration information RI1 or a plurality of keywords included in the sentence of the second registration information RI2 as the second document component DC2. The creation of the new sentence based on the first registration information RI1 or the second registration information RI2 is performed by referring to third reference information including the correlation between the first registration information RI1 or the second registration information RI2 and the new sentence. As the third reference information, for example, a sentence creation model which is a learning model learned to take the first registration information RI1 or the second registration information RI2 as an input and output the second document component DC2 is used. For example, the sentence creation model is a learning model learned with the first registration information RI1 or the second registration information RI2 and the corresponding second document component DC2 as teacher data. The creation unit 112 inputs the first registration information RI1 or the second registration information RI2 into the sentence creation model of the artificial intelligence unit 117 and causes the sentence creation model to output the second document component DC2. Also, the sentence creation model may be a generative AI including a large language model. In this case, the creation unit 112 inputs a prompt in which an instruction to create a new sentence based on the first registration information RI1 or the second registration information RI2 and the first registration information RI1 or the second registration information RI2 are inserted into the sentence creation model, and causes the sentence creation model to output the second document component DC2. Also, in addition to the sentence creation instruction and the first registration information RI1 or the second registration information RI2, the creation unit 112 may input, for example, a prompt in which one or more samples of the first registration information RI1 or the second registration information RI2 and one or more samples of the corresponding second document component DC2 are inserted into the sentence creation model.

[0101] The creation unit 112 determines whether the acquired registration information is either the first registration information RI1 or the second registration information RI2, and generates the first document component DC1 or the second document component DC2 using the first reference information, the second reference information, or the third reference information. The creation unit 112 may use a learning model (i.e., a model that integrates a keyword extraction model and a summary creation model) configured to take the registration information as input, determine whether the input registration information is either the first registration information RI1 or the second registration information RI2, and then output either the first document component DC1 or the second document component DC2.

[0102] The creation unit 112 may generate document components for each category from the registration information of multiple categories, or may generate one document component from the registration information of multiple categories. Also, the creation unit 112 may generate multiple document components from the registration information of one category. For example, in FIG. 5, from the registration information of "Goal / Evaluation", the first document component DC1 of "Owned Skills / Occupation" and the second document component DC2 of "Internal Work History" are generated. Also, from the registration information of "Hiring Information", the first document component DC1 of "Education / Occupation / Qualification at the Time of Hiring" and the second document component DC2 of "Offer Content / Evaluation" are generated.

[0103] (Details of the First Document FD) Regarding the details of the first document FD, they will also be described in relation to the processing of the creation unit 112 described above. As can be recognized from FIGS. 9-12, the creation unit 112 may group, for example, document components based on registration information recorded in the same database in the first document FD. In the example of FIGS. 9-12, a plurality of document components are grouped by items of "basic information" (components based on the basic information database D101), "employment history" (components based on the employment database D105), "evaluation at the time of employment" (components also based on the employment database D105), "experience / skills" (components based on the target evaluation database D102, the position database D103, and the skill database D104), "evaluation history within the company" (components also based on the target evaluation database D102), and "company history" (components based on a plurality of databases). Note that the second document component DC2 included in the "evaluation history within the company" in FIG. 10 includes the name and face photo of the evaluator and the evaluation content (comments, etc.). Also, the "evaluation history within the company" includes the first document component DC1 including the evaluation value (such as "S") and the evaluator.

[0104] The document component may include a job summary in the organization of the person to be managed. The "job summary" describes the job history within the organization of the person to be managed and corresponds to the item of "company history" in the example of FIG. 12. In the job summary, for example, for each predetermined period (annual in the example of FIG. 12), the department, role or job type, work content, results or achievements, etc. are described. Thereby, based on the job summary of the person to be managed, the administrator can easily consider the suitability of the person to be managed for a new position. Also, the job summary ("company history") may include time-series data indicating the temporal changes of attributes such as the personality, characteristics, and condition of the person to be managed.

[0105] The registration information converted by the creation unit 112 into document components may include the goals in the organization of the person to be managed. Goals within the organization are likely to be created by the person to be managed in the organization's operations and are likely to include information related to the job content within the organization. Therefore, by including the organization's goals in the registration information, it is possible to create the work history of the person to be managed within the organization more reliably and accurately. In addition, it becomes possible to search for human resources based on the goals, and other information related to the person to be managed can be confirmed in the human resource management document in conjunction with the goals. The creation unit 112 generates a second document component DC2 that summarizes the goals from the goals included in the registration information and arranges it in the first document FD.

[0106] In addition, the registration information converted by the creation unit 112 into document components may further include an evaluation in the organization of the person to be managed in addition to the goals. The creation unit 112 creates a job summary based on the registration information that includes the goals and the evaluation. Evaluations within the organization are likely to exist in the organization's operations as objective information about the person to be managed and are likely to include information related to the job content (especially achievements, results, etc.) within the organization. Therefore, it is possible to create the work history of the person to be managed within the organization more reliably and accurately. In addition, managers can confirm the goals, the evaluations thereof, the degree of goal achievement, etc. The creation unit 112 generates a second document component DC2 that integrates and summarizes these from the goals and evaluations included in the registration information and arranges it in the first document FD. For example, the second document component DC2 included in the "Summary" in the "Internal History" of FIG. 11 is generated based on the goals and results stored in the goal evaluation database D102. In particular, in the "Summary", a second document component DC2 including the degree of goal achievement calculated based on the text regarding the evaluation is arranged. The degree of achievement may include the main achievement (achievement rate for the major goal) and the sub-achievement (achievement rate for the minor goals obtained by subdividing the major goal). In addition, the "Summary" may be information that combines both the internal history and the external history. Furthermore, the "Summary" may be generated based on a wide range of internal company information such as position information and project information, not limited to goals or evaluations.

[0107] Further, the creation unit 112 may be configured to create a job summary so as to fit within a display area in which a job summary for a predetermined period is specified. Thereby, it is possible to more easily grasp the work history while reducing the operation of moving (scrolling) the screen displayed on the administrator terminal 20 or the like. The "predetermined period" can be set by the creator (editor) of the first document FD. In the example of FIG. 12, it is three years ago from the present. By setting the predetermined period to a period from the present to a relatively recent past, the reflection of old information with low priority on the human resource management document is suppressed. Further, the creation unit 112 may change the size of the display area (the number of characters of the displayed text), the font or size of the characters, etc. for each number of years. For example, the creation unit 112 may increase the display area and increase the amount of information, or display it with prominent characters, for newer information within the job summary.

[0108] The "designated display area" is, for example, an area that can be displayed on one page of the screen of the administrator terminal 20 or the managed person terminal 30. The creation unit 112 adjusts the number of items, the size of the characters, the amount of information, etc. so as to fit within the designated display area. Further, the reception unit 111 may receive the size (number of pages) of the display area of the job summary from the administrator terminal 20 or the managed person terminal 30, and the creation unit 112 may create the job summary so as to fit within the received display area.

[0109] In the example of FIG. 12, the job summary ("company internal history") includes "summary", "extracted skills", and the work history JH, but the job summary may be composed of only the work history JH. Note that "summary" is an item in which current achievements and the like are described, and "extracted skills" is an item in which skills extracted from the work history are displayed as the tag TG2. Also, in the work history JH, for example, the department, position (role, position), job type, etc. for each year are displayed as the tag TG2.

[0110] The registration information converted by the creation unit 112 into document components includes information before the management target person belonged to the organization and information after the management target person belonged to the organization. The document components may include information before the management target person belonged to the organization. Thereby, in addition to the history of the management target person within the organization, information before being employed by the organization can be referenced in one human resource management document. The creation unit 112 generates a second document component DC2 that summarizes the information of the management target person before belonging to the organization included in the registration information, and arranges it in the first document FD.

[0111] For example, the second document component DC2 included in the "work history" in the "history at the time of employment" in FIG. 10 is generated based on the information before the management target person belonged to the organization (employment information stored in the employment database D105). Note that the second document component DC2 included in the "work history" may be generated based on the information at the time of employment of the management target person (such as a resume). Also, the first document component DC1 (evaluation value, evaluator, etc.) and the second document component DC2 (comments, etc.) included in the "evaluation at the time of employment" in the "evaluation at the time of employment" in FIG. 9 are also generated based on the information before the management target person belonged to the organization. In addition, both the "history at the time of employment" and the "evaluation at the time of employment" include the first document component DC1, which is a keyword extracted from the information before the management target person belonged to the organization. Note that the second document component DC2 included in the "evaluation at the time of employment" includes the evaluation at the time of interview ("S"), the name and face photo of the interviewer, and the evaluation content.

[0112] In the example of FIG. 10, the creation unit 112 generates the first document component DC1 and the second document component DC2 from the "employment information". Specifically, the creation unit 112 extracts keywords from the registration information such as educational background included in the "employment information" to generate the first document component DC1, and summarizes the text of the registration information such as the interview evaluation included in the "employment information" to generate the second document component DC2.

[0113] The registration information converted by the creation unit 112 into document components may include the attribute information of the person to be managed. Typically, the creation unit 112 may create a first document FD including tags related to the attribute information as document components. Thereby, the attributes of the person to be managed become easier to visually grasp. The "attribute information of the person to be managed" is, for example, information indicating the position, history, experience, skills, qualifications, etc. of the person to be managed. A tag is an objectification of a keyword representing the attribute information of the person to be managed. Also, the tag may be a tag combining a plurality of categories or a tag having a hierarchical structure. An example of a tag combining a plurality of categories is "Sales: 10 years". An example of a tag having a hierarchical structure is "Management: Organizational Design".

[0114] The creation unit 112 tags, for example, those representing the specified attribute information among the keywords included in the registration information or the first document components DC1. Specifically, the creation unit 112 prepares a tag list in which a plurality of tags are described in advance, extracts the tag words corresponding to the registration information or the document components from the tag list, and tags the registration information or the document components. Here, the tag list is a list in which one or more tag words are described.

[0115] In the example of FIG. 11, the tag TG2 is included in the "Job Type of Experience" and "Possessed Skills" in the item of "Experience / Skills". The tag TG2 is arranged in the first document FD for each type such as position, job type, skills / qualifications, etc. Also, as shown in FIG. 12, the tag TG2 may be included regarding the job summary.

[0116] The tag TG2 may be the same as the tag attached to the job seeker information registered in the job seeker database. The "job seeker database" is a database that stores the registration information of job seekers, and the registration information of job seekers includes resumes, work histories, and other profile information. As a result, administrators can search for internal human resources based on tags in a similar way to searching for job seekers using tags. Note that a "resume" is mainly a document that describes the profile, current situation, education background, work history, and desired working conditions of a job seeker, and a "work history" is also called a resume and is a document in which a job seeker conveys their past work history, experience, skills, qualifications, etc. to the employer.

[0117] The job seeker database is a database publicly available to users of the job search service, which is different from the employee database within the organization and is typically set up outside the organization. When the tag TG2 included in the first document FD is made common with the tag attached to the job seeker information, the creation unit 112 refers to the tag list used in the job seeker database and tags the registration information or document components. Additionally, the creation unit 112 may generate the tag TG2 by referring to an occupation dictionary, a skill dictionary, an in-house terminology dictionary, etc. used in the job seeker database.

[0118] Also, the job seeker database may be a recruitment candidate database (such as a talent pool, etc.) registered in the organization's database.

[0119] Also, although not shown in the figure, the creation unit 112 may calculate the generation accuracy of the first document FD based on the amount of information in the registration information. The generation accuracy is presented before the creation of the first document FD or is displayed on the browsing terminal (the administrator terminal 20 or the management target terminal 30) together with the created first document FD. As a result, information management of internal human resources can be carried out while confirming the reliability of the human resource management document.

[0120] The creation unit 112 evaluates the generation accuracy higher as the number of items of the registration information acquired by the creation unit 112 is larger. For example, for the set (designated by the input person) items of the registration information, when the registration information of all items can be obtained from the database, the generation accuracy is 100%. On the other hand, for the set items of the registration information, when the registration information of some items cannot be obtained due to reasons such as there being unregistered information, the generation accuracy is less than 100%. The more the number of items that cannot be obtained increases, the smaller the generation accuracy becomes. Note that the creation unit 112 can also make the items based on the registration information that could not be obtained in the first document FD blank. Also, the creation unit 112 may evaluate the generation accuracy higher as the amount of information (amount of text) in the acquired registration information is larger.

[0121] Such generation accuracy may be displayed in the header HD of the first document FD. Also, the generation accuracy may be stored in the storage unit 12 of the server device 10 as internal data regarding the human resource management document. Further, the creation unit 112 may calculate the generation accuracy for each item or each document component of the first document FD and present or display it.

[0122] Note that the configuration, items, layout, etc. of the first document FD illustrated in FIGS. 9 - 12 are examples, and the structural design such as the information, order, etc. described in the first document FD can be arbitrarily set.

[0123] 4. Operations Summarizing the operations of the present embodiment, it is as follows. That is, in the information management method of the present embodiment, when the public reception unit 113 receives a public request from a predetermined person, the first document FD or its edited version is publicly disclosed as a human resource management document within a predetermined range. Therefore, proper management of the human resource management document can be performed.

[0124] As described above, the embodiments of the present invention have been described, but the present invention is not limited thereto and can be appropriately changed without departing from the technical idea of the invention.

[0125] 5. Others In the above embodiment, the server device 10 performs various storage and controls. However, instead of the server device 10, a plurality of external devices may be used. That is, various information and programs may be distributed and stored in a plurality of external devices using blockchain technology or the like.

[0126] In the above embodiment, an aspect in which an administrator creates the first document and publishes the first document or the like in a batch is shown. However, the creation of the first document and the publication of the first document or the like may be performed by the management target person. Usually, the first document or the like created and published by the management target person is related to the management target person himself / herself. Regarding the creation and publication of such a first document or the like, the management target person may perform it by operating the management target terminal 30 which is his / her own terminal.

[0127] The aspect of this embodiment is not limited to the information management system 1, and may be an information management method or a program. The information management method includes each step executed by the information management system 1. The program causes a computer to execute each step of the information management system 1.

[0128] It may also be provided in each of the aspects described below.

[0129] (1) An information management system, comprising at least one processor, wherein the processor is configured to execute the following steps by reading a program. In the reception step, registration information regarding a management target person who works for the organization and is registered in a database within the organization is received. In the creation step, a first document regarding a human resource management document including document components derived from the registration information is created. Here, the document components include a text created based on the registration information. In the public reception step, a public request to publicly release the first document or an edited version of the first document within a predetermined range is received from the management target person and / or the administrator of the management target person. In the public release step, based on the fact that the public request has been received, the first document or the edited version is publicly released within the predetermined range as a human resource management document.

[0130] (2) In the information management system according to (1) above, in the creation step, the first document is created by inputting the received registration information into an artificial intelligence module and outputting the document components.

[0131] (3) In the information management system according to (1) or (2) above, in the editing step, an edit of the first document created in the creation step is received from the person to be managed and / or the administrator, thereby generating the edited matter.

[0132] (4) In the information management system according to (3) above, in the editing step, upon receiving an edit of the first document by the person to be managed, the editing authority for the edited matter is restricted to only the person to be managed.

[0133] (5) In the information management system according to any one of (1) to (4) above, in the first document and / or the human resource management document, tags related to at least one of the number of edits of the first document, the creator of the first document, the editor of the first document, the status regarding the creation status of the human resource management document, and the status regarding the publication status of the human resource management document are displayed.

[0134] (6) In the information management system according to any one of (1) to (5) above, in the reception step, an input of a batch creation instruction for the first document regarding a plurality of the persons to be managed is received from the administrator, and in the creation step, the first document regarding each of the plurality of the persons to be managed is created.

[0135] (7) In the information management system according to (6) above, in the organization, a limit on the number of times of input of the batch creation instruction in a predetermined period is provided.

[0136] (8) In the information management system according to the above (6) or (7), in the notification step, when there is an existing first document or the edited material for any of the plurality of management targets, the administrator is notified that a new first document is created in place of the existing first document or the edited material. Information management system.

[0137] (9) In the information management system according to any one of the above (1) to (8), in the public acceptance step, a public request for a plurality of the first documents or the edited materials is received from the administrator, and in the public step, the plurality of the first documents and / or the edited materials are publicly disclosed in a corresponding predetermined range. Information management system.

[0138] (10) In the information management system according to the above (9), in the public step, when the personnel management document already publicly disclosed in the predetermined range coexists with the first document or the edited material, the first document or the edited material for which the public request has been received is publicly disclosed as the personnel management document in place of the publicly disclosed personnel management document. Information management system.

[0139] (11) In the information management system according to the above (10), in the notification step, the administrator is notified that the first document or the edited material for which the public request has been received is publicly disclosed as the personnel management document in place of the publicly disclosed personnel management document. Information management system.

[0140] (12) In the information management system according to any one of the above (1) to (11), in the display control step, the status regarding the creation status of the personnel management documents among the plurality of management targets is displayed to the administrator in a list form. Information management system.

[0141] (13) An information management method comprising each step executed by the information management system according to any one of the above (1) to (12). Information management method.

[0142] (14) A program for causing a computer to execute each step of the information management system according to any one of (1) to (12) above. Of course, this is not the limit.

[0143] Finally, although various embodiments according to the present disclosure have been described, these are presented as examples and are not intended to limit the scope of the invention. The novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. The embodiments and their modifications are included in the scope and gist of the invention, and are included in the invention described in the claims and its equivalent scope.

Explanation of Reference Numerals

[0144] 1: Information management system 2: Communication line 10: Server device 11: Control unit 12: Storage unit 13: Communication unit 14: Communication bus 20: Administrator terminal 21: Control unit 22: Storage unit 23: Communication unit 24: Input unit 25: Output unit 26: Communication bus 30: Managed person terminal 31: Control unit 32: Storage unit 33: Communication unit 34: Input unit 35: Output unit 36: Communication bus 111: Reception unit 112: Creation unit 113: Publication reception unit 114: Publication unit 115: Display control unit 116: Editing unit 117: Artificial intelligence unit 118: Condition Setting Section 119: Notification Section 211: Display Section 212: Operation Reception Section 311: Display Section 312: Operation Reception Section AT: Attribute BT1~BT5: Buttons CB: Check Box CS: Caution Screen D10: Personnel Database D101: Basic Information Database D102: Target Evaluation Database D103: Position Database D104: Skill Database D105: Recruitment Database D106: Condition Survey Database D107: Organizational Diagnosis Survey Database D108: Original Survey Database D109: Interview Database D110: Attendance Database DC1: First Document Component DC2: Second Document Component DT: Details EB: Edit Button ED: Edit Screen FD: First Document HD: Header JH: Work History NM: Name RI1: First Registration Information RI2: Second Registration Information ST: Step STT: Status TG1, TG2: Tags

Claims

1. An information management system, comprising at least one processor, wherein the processor is configured to execute the following steps by reading a program: In a reception step, registration information regarding a plurality of persons to be managed who are engaged in the organization and registered in a database within the organization, and a batch creation instruction of a first document regarding the plurality of persons to be managed from an administrator of the plurality of persons to be managed are received. Here, the first document is a draft of a human resource management document including document components derived from the registration information, and the document components include sentences created based on the registration information. In a creation step, based on the batch creation instruction, the first document regarding each of the plurality of persons to be managed is created in a manner that it can be edited by a person belonging to an editable range composed only of the persons to be managed and the administrator. In a public reception step, after the creation step, a public request to publicly release the first document regarding the plurality of persons to be managed or an edited version of the first document in a batch to a predetermined range is received from the administrator. Here, the predetermined range is wider than the editable range. In a public release step, based on the fact that the public request has been received, the first document regarding the plurality of persons to be managed or the edited version is publicly released in a batch to the corresponding predetermined range as a human resource management document. Here, when the human resource management document already publicly released to the predetermined range and the first document or the edited version coexist for the person to be managed, instead of the publicly released human resource management document, the first document or the edited version for which the public request has been received is publicly released as the human resource management document. An information management system.

2. The information management system according to claim 1, wherein in the creation step, the received registration information is input into an artificial intelligence module, and the first document is created by outputting the document components. An information management system.

3. The information management system according to claim 1, In an editing step, an edited version is generated by receiving an edit to the first document created in the creation step from the person to be managed and / or the administrator. An information management system.

4. The information management system according to claim 3, An information management system that, upon receiving an edit to the first document by the person to be managed in the editing step, restricts the editing authority for the edited material to only the person to be managed.

5. In the information management system according to claim 1, At least one tag related to the number of edits to the first document, the creator of the first document, the editor of the first document, the status regarding the creation status of the human resource management document, and the status regarding the publication status of the human resource management document is displayed in the first document and / or the human resource management document. Information management system.

6. In the information management system according to claim 5, The creation step creates the first document by inputting the received registration information into an artificial intelligence module and outputting the document components, and When no edit has been made to the first document, A tag indicating that the human resource management document is the document itself created by the function of the artificial intelligence module is displayed in the human resource management document. Information management system.

7. In the information management system according to claim 1, In the organization, a limit is set on the number of times of input of the batch creation instruction within a predetermined period. Information management system.

8. In the information management system according to claim 1, In the notification step, when there is an existing first document or the edited material for any of the plurality of persons to be managed, the administrator is notified to create a new first document in place of the existing first document or the edited material. Information management system.

9. In the information management system according to claim 1, In the notification step, the administrator is notified to publicly disclose the first document or the edited material that has received the public disclosure request as the human resource management document in place of the publicly disclosed human resource management document. Information management system.

10. In the information management system according to claim 1, In the display control step, the status regarding the creation status of the human resource management document among the plurality of persons to be managed is displayed to the administrator in a listable manner. Information management system.

11. In the information management system according to claim 10, In the display control step, when the status is a situation where the first document has been created or a situation where the human resource management document is published, a button that enables the administrator to view the first document or the human resource management document is displayed in association with the management target person. An information management system.

12. An information management method, comprising: An information management method including each step executed by the information management system according to any one of Claims 1 to 11.

13. A program, comprising: A program for causing a computer to execute each step of the information management system according to any one of Claims 1 to 11.

Images