Information management system, information management method, and program

Abstract

To provide an information management system or the like capable of properly managing a personnel management document.SOLUTION: According to an aspect of the present invention, there is provided an information management system, including at least one processor, the processor being configured to execute the following steps by reading a program: In the creation step, a first document related to a human resource management document including a document component derived from the registration information is created, the document component including a sentence created based on the registration information, and in the disclosure acceptance step, a disclosure request for disclosing the first document or a compilation of the first document in a predetermined range is accepted from the managed person and / or a manager of the managed person, in the disclosure step, the first document or the compilation is disclosed in a predetermined range as a human resource management document on the basis of reception of a disclosure request.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] As disclosed in Patent Document 1, a technique is known that supports the creation of text by automatically creating templates. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-230705 Summary of the Invention [Problem to be solved by the invention]

[0004] In recent years, there has been a trend to utilize human resource management documents to manage information on human resources within an organization. These human resource management documents are required to include not only basic information such as the names of the people to be managed, but also various statements about the people to be managed. However, when documents are created using the prior art described above, document management may not necessarily be in line with the intentions of the people to be managed.

[0005] In view of the above circumstances, the present invention provides an information management system and the like that can properly manage personnel management documents. [Means for solving the problem]

[0006] According to one aspect of the present invention, there is provided an information management system comprising at least one processor, the processor being configured to execute the following steps by reading a program: a reception step receiving registration information relating to managed persons working in an organization, which is registered in a database within the organization; a creation step creating a first document relating to a human resources management document including document components derived from the registration information, the document components including text created based on the registration information; a publication reception step receiving a publication request from the managed persons and / or an administrator of the managed persons to make the first document or a compilation of the first document public to a specified extent; and a publication step publishing the first document or compilation as a human resources management document to a specified extent based on the acceptance of the publication request.

[0007] According to this aspect, an information management system or the like that can properly manage personnel management documents is provided. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a configuration diagram illustrating an information management system 1. FIG. [Figure 2] 2 is a block diagram showing the hardware configuration of the server device 10. FIG. [Figure 3] 2 is a block diagram showing the hardware configuration of a manager terminal 20 and a managed person terminal 30. FIG. [Figure 4] 1 is a block diagram showing functions realized by a server device 10 (controller 11), an administrator terminal 20 (controller 21), and a managed person terminal 30 (controller 31). [Figure 5] FIG. 2 is a block diagram showing an example of the configuration of a personnel database D10. [Figure 6] FIG. 1 is an activity diagram illustrating an overview of an information management method according to an embodiment of the present invention. [Figure 7] 10 is an example of a management screen displayed on the manager terminal 20. [Figure 8] 10 is an example of a warning screen CS displayed on the administrator terminal 20. [Figure 9]FIG. 2 shows an example of a first document FD. [Figure 10] FIG. 10 is a diagram showing a part of the first document FD different from that shown in FIG. 9. [Figure 11] FIG. 11 shows a part of the first document FD different from that shown in FIGS. 9 and 10. [Figure 12] FIG. 12 shows a different part of the first document FD from that shown in FIGS. 9-11. [Figure 13] FIG. 10 is a diagram showing an example of an edit screen ED. DETAILED DESCRIPTION OF THE INVENTION

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

[0010] That is, the information management system of this embodiment is as follows. 1. An information management system, comprising: at least one processor; The processor is configured to execute the following steps by reading the program: In the receiving step, registration information regarding a person to be managed who works in the organization and is registered in a database within the organization is received; In the creation step, a first document related to a human resources management document is created, the first document including document components derived from the registration information, wherein the document components include sentences created based on the registration information; In the disclosure acceptance step, a disclosure request to disclose the first document or a compilation of the first document to a predetermined range is accepted from the managed person and / or an administrator of the managed person; In the disclosure step, the first document or the compilation is disclosed to the predetermined range as a human resources management document based on the acceptance of the disclosure request.

[0011] Incidentally, the program for realizing the software appearing in one embodiment may be provided as a non-transitory computer-readable medium, or may be provided so that it can be downloaded from an external server, or may be provided so that the program is started on an external computer and its functions are realized on a client terminal (so-called cloud computing).

[0012] Furthermore, various information processing according to an embodiment may realize input and output corresponding to the input. Here, the form of information referenced in such information processing (hereinafter referred to as reference information) is not limited as long as an output is obtained as a result of the input. The reference information may be, for example, rule-based information such as a database, a lookup table, or a predetermined function (including a decision formula such as a regression formula constructed using a statistical method), a trained model that has previously trained the correlation between input and output, or a large-scale language model that can output a desired result by inputting a prompt.

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

[0014] Furthermore, a circuit in the broad sense is a circuit realized by at least an appropriate combination of a circuit, circuitry, processor, memory, etc. The processor may be a general-purpose processor or a dedicated circuit. That is, it includes an application specific integrated circuit (ASIC), a programmable logic device (e.g., a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)), etc.

[0015] 1. Hardware Configuration This section explains the hardware configuration.

[0016] <Information Management System 1> 1 is a configuration diagram showing an information management system 1. The 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 terminal 20, and the managed person terminals 30 are configured to be able to communicate with each other via the communication line 2. The connection between the server device 10, the administrator terminal 20, and the managed person terminals 30 and the communication line 2 may be wired or wireless.

[0017] The information management system 1 constitutes part of a personnel system used by personnel (multiple managed persons) subject to personnel management within an organization and multiple managers within the organization who are related to the managed persons. "Managers" include people on the reporting line of the managed persons (e.g., superiors, line managers, etc.), personnel managers, etc. Note that a "managed person" in the information management system 1 can also be the "manager" of another managed person.

[0018] The information management system 1 supports the creation of human resource management documents for managed personnel. In one embodiment, the information management system 1 is comprised of one or more devices or components. These components will be described below.

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

[0020] <Control unit 11> The control unit 11 processes and controls 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 out predetermined programs stored in the storage unit 12. In other words, 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 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 multiple control units 11 may be provided for each function. A combination of these may also be used.

[0021] <Storage section 12> The memory unit 12 stores various pieces of information defined 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 required information (arguments, arrays, etc.) related to the program operations. The memory unit 12 stores various programs, variables, etc. related to the server device 10 executed by the control unit 11.

[0022] <Communications Department 13> The communication unit 13 is preferably a wired communication means such as USB, IEEE1394, Thunderbolt (registered trademark), or wired LAN network communication, but may also include wireless LAN network communication, mobile communication such as 3G / LTE / 5G, or BLUETOOTH (registered trademark) communication as needed. That is, it is more preferable to implement it as a collection of 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 an on-premise server or a cloud server. The cloud server device 10 may provide the above-described functions and processes in the form of, for example, SaaS (Software as a Service) or cloud computing.

[0024] <Administrator terminal 20> 3 is a block diagram showing the hardware configuration of the administrator terminal 20 and the managed user terminal 30. 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 via the communication bus 26 inside the administrator terminal 20. The description of the control unit 21, the storage unit 22, and the communication unit 23 is the same as the description of each unit in the server device 10, and therefore will be omitted.

[0025] <Input section 24> The input unit 24 accepts 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 or 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. Instead of a touch panel, a switch button, a mouse, a trackpad, a QWERTY keyboard, etc. can be used as the input unit 24.

[0026] <Output section 25> The output unit 25 displays a screen of a graphical user interface (GUI) that can be operated by a user. The output unit 25 may be included in the housing of the administrator terminal 20 or may be attached externally. Specifically, the output unit 25 may be implemented as a display device such as a CRT display, a liquid crystal display, an organic EL display, or a plasma display. It is preferable that these display devices are used appropriately depending on the type of administrator terminal 20.

[0027] <Management target terminal 30> 3B, the managed user 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 user terminal 30. The description of the control unit 31, the storage unit 32, the communication unit 33, the input unit 34, and the output unit 35 is omitted because they are the same as the description of each unit in the administrator terminal 20.

[0028] 2. Functional configuration This section describes the functional configuration of this embodiment. 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 can be executed as each functional unit included in the control unit 11 (a processor provided in the information management system 1).

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

[0030] As shown in FIG. 4A, server device 10 (control unit 11) includes a reception unit 111, a creation unit 112, a publication 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, administrator terminal 20 (control unit 21) includes a display unit 211 and an operation reception unit 212. As shown in FIG. 4C, managed user terminal 30 (control unit 31) includes a display unit 311 and an operation reception unit 312.

[0031] <Reception Department 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 registered information about the managed persons stored in the personnel database D10 is personnel information and is classified into multiple categories. Examples of "categories" include the name, gender, age, employee code, contact information, affiliation, employment status, work location, job duties, organizational goals set by the managed persons, managerial evaluations of those goals, information about the managed persons before they joined the organization (information at the time of hiring), the managed persons' condition, engagement (e.g., eNPS), aptitude or personality, interview history (interviewees, comments, etc.), and attendance information (overtime hours, number of annual holidays taken, etc.) of the managed persons. The information at the time of hiring includes the position offered at the time of hiring, annual salary, hiring interviewer, hiring evaluation, aptitude test results, reference check information, etc. Information other than the information at the time of hiring is information about the managed persons after they join the organization (post-hiring information).

[0035] Categories of registered information are distinguished by multiple attributes. Examples of attributes that distinguish categories include the registration date of the information reflected in the registered information and the description format of the information. In the example of the registration date, basic information such as name, gender, and age is information at the time of employment or transfer to an organization. Furthermore, goals and evaluations are information about the time when each was implemented, and the registration dates of goals and evaluations differ. Furthermore, information at the time of employment is information before employment to an organization. Therefore, these pieces of information are classified into different categories. On the other hand, in the example of the description format of information, a distinction is made between information described using keywords or numbers (e.g., name, affiliation, job title, etc.) and information described in sentences (e.g., work content, goals, evaluation, condition, etc.). Therefore, the former information and the latter information are classified into different categories. Another example of an attribute that distinguishes categories is whether the information is unique. Examples of unique information include name. Examples of non-unique information include gender, affiliation, job title, etc. Furthermore, the categories of registered information are not limited to the above-mentioned attribute distinctions and may be arbitrarily set by the user.

[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 goal evaluation database D102).

[0037] <Creation Department 112> The creation unit 112 creates various pieces of information based on the information received as the server device 10. In this embodiment, the creation unit 112 creates a first document related to a human resources management document that includes document components derived from the registered information. The document components here include sentences created based on the registered information. Here, this "first document" is positioned as a draft (rough draft) of the "human resources management document" described below. Furthermore, by undergoing the "publication" process described below, this "first document" will be made public to a predetermined extent as a "human resources management document."

[0038] In addition, even if a publicly-available personnel management document already exists for a certain managed person, the creation unit 112 may create a new first document for the same managed person so that it coexists with the publicly-available personnel management document.

[0039] In a typical embodiment, 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 document components. Hereinafter, the "artificial intelligence module" will be described as the artificial intelligence unit 117 of the server device 10, but the present invention is not limited to this. The first document may be created by inputting predetermined registration information into an artificial intelligence module located outside the server device 10. The first document may also be created in a manner other than inputting the received registration information into the artificial intelligence module. In an exemplary embodiment, the creation unit 112 may create the first document from the received registration information based on a predefined rule base. Other specific processes related to the creation of the first document will be described later.

[0040] <Public Reception Section 113> The disclosure acceptance unit 113 accepts a disclosure request from a managed person and / or an administrator of the managed person to disclose the first document or a compilation of the first document to a predetermined range. The specific processing will be described later.

[0041] <Public Section 114> Upon receiving the disclosure request, the disclosure unit 114 discloses the first document or compilation to a predetermined range as a human resources management document. The human resources management document here is an internal resume (e.g., a document aggregating the registered information) based on the registration information of the managed person registered in the human resources database, and is typically made available for viewing within a predetermined range. The range (predetermined range) to which this human resources management document is disclosed can be arbitrarily set depending on the purpose of using the human resources management document. For example, one example of a human resources management document disclosed within a predetermined range is one in which only the department to which the manager belongs (the human resources department) and human resources-related decision makers (e.g., management) can view the human resources management document, and no one else (including the managed person) can view it. Another example of a human resources management document disclosed within a predetermined range is one in which both the manager and the managed person can view the human resources management document. The predetermined range is set, for example, by the manager. The predetermined range may also be set automatically depending on the access rights to employee information, etc. In a typical example, the disclosure unit 114 discloses the personnel management document so that only those who have access rights to the employee information included in the disclosed personnel management document can view the specified information. The disclosure unit 114 may also set viewing conditions for each item in the personnel management document. For example, a specific item in the personnel management document may be disclosed so that only those who have access rights can view the employee information related to the specific item. In this case, items other than the specific item may be disclosed to a range that is not related to the above-mentioned access rights. The disclosure unit 114 may also set viewing conditions for each document component of the personnel management document.

[0042] Furthermore, the predetermined range here typically refers to an expanded range within which a disclosure request can be accepted. As described above, a disclosure request can be accepted from the managed person and / or the administrator of the managed person. The disclosure unit 114 discloses the human resources management document so that the document can be viewed by those who are managed and / or the administrator, but not by others. In a typical embodiment, the human resources management document is provided for viewing within the organization. That is, the human resources management document may not be disclosed outside the organization. Creating a human resources management document for each managed person allows administrators and others to easily search for talent within the organization using keywords, conditions (parameters), and the like. Human resources management documents are referenced, for example, in strategic personnel transfers, internal recruitment, utilization of inactive human resources, career inventory support, and the like. Specific processes related to this disclosure and more specific aspects of the human resources 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 viewed by the user. The display information may be information itself generated in a form that can be viewed by the user, such as a screen, image, icon, text, etc., or may be rendering information for displaying a screen, image, icon, text, etc. on various terminals. In this embodiment, the display control unit 115 displays the status of the creation of human resource management documents for multiple managed persons in a visible manner to the manager. Specific processing related to this display control will be described later.

[0044] <Editorial Department 116> The editing unit 116 generates an edited product by accepting edits from the managed person and / or the administrator to the first document created by the creation unit 112. Specific processing related to this editing will be described later.

[0045] <Artificial Intelligence Department 117> The artificial intelligence unit 117 is configured to receive input from each functional unit and return the instructed output. The artificial intelligence used by the server device 10 in each functional unit may be a common one, or may be prepared individually for each functional unit.

[0046] The artificial intelligence unit 117 is an AI (Artificial Intelligence) that includes language models such as Transformers including GPT (Generative Pretrained Transformer, including GPT-1, GPT-2, and GPT-3), BERT (Bidirectional Encoder Representations from Transformers), and BART (Bidirectional and Auto-regressive Transformer), and Recurrent Neural Networks (RNNs), and includes generative AI.

[0047] The language model is an example of a learning model based on a machine learning algorithm. Specific examples of machine learning algorithms include nearest neighbor methods, naive Bayes methods, decision trees, support vector machines, and deep learning using neural networks. The artificial intelligence unit 117 can apply the above algorithms as appropriate.

[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 training data (training data). The training data is composed of pairs of input data for learning and output data (correct answer data). Furthermore, the language model may not only be one trained for a specific task, but also a general-purpose model that can be used for a wide range of tasks.

[0049] The artificial intelligence unit 117 includes, as its artificial intelligence, a general-purpose natural language processing learning model such as a large language model (LLM) that has learned a huge amount of data. Such a general-purpose learning model includes a language model that can handle various tasks without fine tuning using one-shot learning, few-shot learning, etc. Furthermore, the general-purpose learning model can also handle various tasks using zero-shot learning. The artificial intelligence used in each functional unit of the control unit 11 may be a separate learning model, or may be a common general-purpose learning model.

[0050] The learning model included in the artificial intelligence unit 117 is capable of additional learning. For example, the artificial intelligence unit 117 learns whether the created human resource management document has been modified by the person instructing the creation, etc. In other words, the artificial intelligence unit 117 performs additional learning and fine-tuning using a training data set in which the human resource management document is labeled with actual modification results as feedback for the human resource management document created by the learning model. This optimizes the human resource management document output from the learning model.

[0051] <Condition setting section 118> The condition setting unit 118 is configured to set editable conditions for the published personnel management document in accordance with the terminal operation of the person entering the information, thereby enabling the management level of the personnel management document to be flexibly adjusted in accordance with the person entering the information.

[0052] The editability conditions can be set appropriately depending on the purpose of the human resources management document. For example, one example of an editability condition is that if the person who inputs the document is a manager (e.g., a person in the human resources department), editing is prohibited for everyone. The editability condition may also be that if the person who inputs the document is the person to be managed, editing is permitted only for the person to be managed, or regardless of the person who inputs the document, editing is prohibited for everyone else.

[0053] The condition setting unit 118 may also set editable conditions for each item in the human resources management document. For example, if the inputter is a manager, only specific items may be editable, and all other items may be uneditable. Furthermore, the condition setting unit 118 may also set viewable conditions or editable conditions for each document component.

[0054] <Notification section 119> The notification unit 119 is configured to notify various types of information to various terminals with which the server device 10 can communicate. In one aspect of this embodiment, if there is an existing first document or compilation for any of multiple managed persons, the notification unit 119 notifies the administrator that a new first document will be created in place of the existing first document or compilation. In another aspect of this embodiment, the notification unit 119 notifies the administrator that the first document or compilation, for which a disclosure request has been accepted, will be made public as a human resources management document in place of the publicly available human resources management document. Specific processing related to these notifications will be described later.

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

[0056] <Operation reception section> The operation acceptance unit 212 of the administrator terminal 20 accepts operations by a user (administrator) who uses the administrator terminal 20. The operation acceptance unit 312 of the managed person terminal 30 accepts operations by a user (managed person) who uses the managed person terminal 30.

[0057] 3. Information Processing Method This section describes an information processing method of the server device 10. This information processing method is executed by a computer, with each unit of the server device 10 acting as each step.

[0058] The information management method described below allows an administrator to create first documents for multiple managed users at once. This information management method will be explained in order, including an overview of information processing, details of the first document creation process, and details of the first document.

[0059] (Outline of Information Processing) First, an overview of information processing in the information management method of this embodiment will be described with reference to an activity diagram. Fig. 6 is an activity diagram showing an overview 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 manager terminal 20 (activity A101). FIG. 7 is an example of the management screen displayed on the manager terminal 20. As described above, the display control unit 115 of the server device 10 can display, to the manager, the status of the creation status of human resource management documents for multiple managed persons in a listable manner, and displays such information on the management screen shown in FIG. 7. Specifically, the management screen shown in FIG. 7 displays a list of managed persons who are targets for creating resumes (internal management documents). The management screen in FIG. 7 displays, in association with each managed person, the name NM of each managed person, as well as a status STT of the creation status of the human resource management document, attributes AT of the managed person, and details DT of the human resource management document.

[0061] The status STT regarding the creation status of the human resources management document may include, for example, a status in which each managed person has not created the first document or the human resources management document (not created), a status in which each managed person has created up to the first document but has not yet published it as the first managed document (draft), and a status in which each managed person has already published the human resources management document (published).

[0062] Furthermore, the attributes AT of the managed persons may include attributes such as each managed person's primary job, concurrent jobs, grade, job type, position, and work location. Of course, the attributes of the managed persons displayed on the administrator terminal are not limited to these, and may include various items such as gender, age, and time of joining the company. In addition, on the management screen of FIG. 7, the managed persons can be sorted and displayed according to the above-mentioned status STT and attribute AT. This allows the administrator to efficiently narrow down the persons to be managed.

[0063] The details DT for a human resources management document indicates whether the managed person can view the human resources management document or a draft of the human resources management document. In the example of the management screen in Figure 7, documents with a status of "draft" or "public" are available for viewing, and the button labeled "details" is displayed in a different manner from other managed people who are in the "not created" state. In this manner, an administrator viewing the management screen in Figure 7 can view the corresponding document (first document or human resources management document) by pressing the "details" button for a managed person whose status STT regarding the creation status of the human resources management document is "draft" or "public."

[0064] 7 also shows check boxes CB associated with each person to be managed. When processing personnel management documents, the administrator can use these check boxes CB to select the persons to be managed who will be the targets of the processing. In this way, by selecting the persons to be managed who will be the targets of the processing and pressing button BT1, it is possible to perform batch processing of personnel management documents.

[0065] The management screen in Fig. 7 shows a mode in which drafts of personnel management documents (first documents) are created in a batch for selected managed persons. That is, after the managed persons are selected, the server device 10 receives an instruction to create the first documents by pressing the button BT1 labeled "Batch Creation" (see activities A102-103). Note that "batch creation" here refers to creating multiple first documents with a single instruction. That is, "batch creation" is not limited to the simultaneous creation of multiple first documents, but also includes a mode in which multiple first documents that are the creation targets are created sequentially.

[0066] The content of the process can be set as appropriate using button BT1. Specifically, it is possible to make multiple personnel management documents public at once for a specified managed person, or to make multiple personnel management documents private at once for a specified managed person. In addition, it is also possible to delete multiple first documents and / or personnel management documents at once for a specified managed person based on the operation of button BT1.

[0067] In this way, when an instruction to create a first document is given from the administrator terminal 20, the server device 10 accepts the instruction (activity A104). Then, based on the creation instruction, the server device 10 acquires predetermined registration information and executes processing to create the first document (activities A105-107). That is, the reception unit 111 of the server device 10 accepts, from the administrator terminal 20, an input of an instruction to collectively create first documents for multiple managed users, and the creation unit 112 creates a first document for each of the multiple managed users.

[0068] Before the creation process of the first document is executed, a warning screen CS as shown in Fig. 8 may be displayed on the administrator terminal 20. Fig. 8 is an example of the warning screen CS displayed on the administrator terminal 20.

[0069] As described above, if there is an existing first document or compilation for any of the multiple managed users, the notification unit 119 can notify the administrator that a new first document will be created in place of the existing first document or compilation. The warning screen CS in FIG. 8 notifies the administrator that a new first document will be created (overwritten) in this manner. Furthermore, in the information management system 1 of this embodiment, an organization may impose a limit on the number of times a batch creation instruction can be input within a predetermined period. This facilitates information management while optimizing information processing costs. Such a limit on the number of times may also be displayed on the warning screen CS. Note that the number of times the limit on the number of times can be set arbitrarily, but as an example, it may be set for a predetermined period (e.g., annually, quarterly, etc.) depending on the size of the organization. Note that while FIG. 8 shows three related items as the warning screen CS, the number of items displayed on the warning screen CS may be less than or greater than this number. In other words, the warning screen CS may only indicate either the process when there is an existing first document or compilation and the limit on the number of times a batch creation instruction can be input within the organization. Of course, although not explicitly stated in this specification, if there are any matters that are useful for operating the system within an organization, the matters may be separately displayed on the caution screen CS.

[0070] Furthermore, upon encountering such a warning screen CS, the administrator can confirm the notification items and then press button BT2 to proceed with the batch creation process of the first documents. In other words, by having the administrator press button BT2, the administrator can be prompted to confirm and agree to creating the first document, or to creating a new first document in place of an existing first document, etc. Note that the warning screen CS may be configured so that pressing button BT3 returns to the previous screen (management screen).

[0071] On the other hand, such notification may be given only to the administrator, or may be given to the managed person and the managed person. In the above, an embodiment has been described in which the creation of a first document or the creation of a new first document in place of an existing first document, etc., is performed with the administrator's consent. However, in one embodiment, a system may be configured to obtain the confirmation or consent of the managed person regarding the creation of such a first document or the creation of a new first document in place of an existing first document, etc. Such notification may also be given when the aforementioned first documents and / or human resources management documents are deleted in bulk. That is, when the administrator attempts to delete the first documents and / or human resources management documents in bulk, a predetermined warning screen may be displayed to the administrator to obtain consent or confirmation regarding the deletion of the first documents and / or human resources management documents in bulk. Furthermore, a system may be configured to obtain the confirmation or consent of the managed person regarding the deletion of the first documents and / or human resources management documents in connection with such bulk deletion.

[0072] Although the process for creating the first document will be described in detail later, by executing this creation process for each managed user, multiple first documents can be created at once. Furthermore, each of the first documents created by the creation unit 112 is displayed on the administrator terminal 20 and / or the managed user terminal 30 (see activities A108-109).

[0073] FIG. 9 is a diagram showing an example of a first document FD. FIG. 10 is a diagram showing a different portion of the first document FD from FIG. 9. FIG. 11 is a diagram showing a different portion of the first document FD from FIGS. 9 and 10. FIG. 12 is a diagram showing a different portion of the first document FD from FIGS. 9-11. As shown in FIGS. 9-12, the first document FD includes a header HD and multiple document components (first document component DC1 and second document component DC2). The header HD contains the name, thumbnail (e.g., a photo of the person being managed), affiliation, etc. of the person being managed. Note that the first document FD shown in FIGS. 9-12 is a document viewed from the managed user terminal 30; when the first document FD is viewed from the administrator terminal 20, some information may have been added or deleted.

[0074] In the first document FD of FIG. 9, button BT4 is shown as a button used to edit the first document. As described above, the editing unit 116 of the server device 10 is configured to generate an edited product by accepting edits to the first document FD created by the creation unit 112 from the managed person and / or administrator. A user (typically an administrator or managed person, but also referred to as an "editor") accessing FIG. 9 is configured to transition to a predetermined editing screen by pressing this button BT4. Note that, in this specification, a first document FD created by the creation unit 112 that has been manually edited may also be referred to as an "edited product." Hereinafter, the first document FD and the edited product may also be collectively referred to as the "first document FD, etc."

[0075] Specific editing processing will now be described. After the creation unit 112 creates the primary document FD, the editing unit 116 displays a screen that accepts edits to the primary document FD. Alternatively, the editing unit 116 may accept edits (inputs) step by step for each item on the primary document FD. FIG. 13 illustrates an example of an editing screen ED. A step ST indicating the progress of editing is displayed at the top of the editing screen ED. In the example of FIG. 13, step ST indicates that editing of two items, "Basic Information" and "External Experience," has been completed, that a third item, "Internal Experience," is currently being edited, and that two items ("Career Summary" and "Other") remain after "Internal Experience." Furthermore, an edit button EB is provided on the editing screen ED for each item created by the creation unit 112 or for each editing unit that further subdivides an item. By operating the edit button EB, the corresponding entry can be edited. Editing of the entries is performed, for example, by inputting sentences or words from the administrator terminal 20 or the managed person terminal 30, or by selecting a tag from tag candidates. For example, the editing unit 116 may display a list of tags extracted from the registered information as tag candidates. This allows the user to edit the tag to be placed on the primary document FD by selecting any tag from the displayed list of tag candidates.

[0076] When editing of one item is completed by, for example, clicking a done button, the editing unit 116 displays the editing screen ED for the next item in the order displayed in step ST. In this way, the editing unit 116 switches the editing screen ED displayed on the manager terminal 20 or the managed person terminal 30 for each item of the human resources management document, and accepts editing for each item. This makes it possible to accept editing while staying close to the mental model (what the managed person wants to do or what they can understand), for example.

[0077] Furthermore, the editing unit 116 may accept edits for each item on a screen displaying the entire primary document FD, without switching the edit screen ED for each item.

[0078] Note that restrictions may be placed on the editing authority for the primary document FD described above. In a typical embodiment, the scope of editing of the primary document FD is narrower than the scope of disclosure of the human resources management document by the disclosure unit 114. In one embodiment, the primary document FD may be configured to be editable only by the managed person and / or the administrator of the managed person, or may be configured to be editable only by the managed person. That is, in one embodiment, the scope of editing of the primary document FD may be narrower than the scope of disclosure requests for the primary document FD, etc. In a typical example, the scope of editing of the primary document FD may be limited to the managed person and a limited number of administrators, and the scope of disclosure requests for the primary document FD, etc. may be limited to the managed person and a limited number of administrators. In addition, the editing authority and disclosure scope may be arbitrarily set by the user.

[0079] The editing authority may be configured to change depending on the process executed by the information management system 1. As an example, the editing unit 116 may be configured to restrict the editing authority for the edited product to only the managed person upon receiving edits to the primary document FD by the managed person. By adopting such an embodiment, it becomes easier to reflect the intentions of the managed person in the primary document FD, etc.

[0080] Furthermore, as shown in FIG. 9, various tags TG1 may be attached to the header HD of the first document FD. This tag TG1 may relate 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 of the creation status of the human resources management document, and the status of the disclosure information of the human resources management document. In the example shown in FIG. 9, the status of the disclosure status of the human resources management document is indicated by the tag "private." Furthermore, the status of the creation status of the human resources management document is indicated by the tag "draft." Furthermore, the creator of the first document FD is indicated by the tag "generated by AI." Note that the tag "generated by AI" may be configured to disappear when the above-mentioned editing is performed by the managed person and / or the administrator of the managed person. That is, if the first document FD shown in FIG. 9 is a document created by the functions of the creation unit 112 and the artificial intelligence unit 117, it may be configured to be tagged with "AI-generated." In this case, the "AI-generated" tag may indicate the number of edits of the first document FD (i.e., zero edits) or the editor of the first document FD (i.e., no edits (updates) have been made to the first document FD). Note that instead of the tag TG1 labeled "AI-generated" in FIG. 9, a tag labeled "automatically generated" may be used. While this tag labeled "automatically generated" may indicate a first document FD created by the functions of the creation unit 112 and the artificial intelligence unit 117, it may also be used when the creation unit 112 mechanically creates the first document FD based on a predefined rule base without using the artificial intelligence unit 117 (AI). Furthermore, if the first document FD is edited by a specific person (e.g., a person under management), the fact that the first document FD has been edited may be indicated in the header HD by the tag TG1. The tag TG1 displayed in such a case may be, for example, a tag indicating the person who performed the most recent edit (update), a tag indicating the date and time showing the editing history up to the present, a tag indicating version information, etc. By displaying such tags TG1, it becomes easier to manage various documents.

[0081] Note that this tag TG1 may also be displayed when the first document FD, etc. is made public. That is, even in a human resources management document that is a publicly-available object such as the first document FD, tags 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 related to the creation status of the human resources management document, and the status related to the publication status of the human resources management document may be displayed.

[0082] Returning to the flow of information processing, after the primary document FD etc. is displayed as described above, the server device 10 accepts a disclosure request from a user who has accessed the primary document FD etc., and discloses the primary document FD or its edited version to a predetermined range as a human resources management document (activity A110-112).

[0083] This disclosure request may be made by the managed person or by the administrator. In other words, when a disclosure request is received from the managed person, the managed person's primary document FD or edited material is made public to a predetermined range based on this disclosure request. This disclosure request by the managed person may be fulfilled, for example, by pressing the "Release" button BT5 on the primary document FD shown in FIG. 9.

[0084] In addition, when a disclosure request is made by an administrator, the administrator designates the primary document FD, etc. to be disclosed and then makes the disclosure request, whereby the designated primary document FD, etc. is made public within a specified range.

[0085] On the other hand, the server device 10 may be configured to collectively publish the primary document FDs and the like of multiple managed users. Specifically, the publication accepting unit 113 of the server device 10 can also accept publication requests for multiple primary document FDs or compilations from the administrator. In response to this, the publication unit 114 can also publish the multiple primary document FDs and / or compilations to a predetermined range corresponding to each of them.

[0086] Such batch document publication may be performed, for example, through operations on the management screen shown in Fig. 7. Button BT1 in Fig. 7 is shown as the mode for "batch creation," but by switching this mode to "batch publication" and having the administrator press button BT1, human resource management documents for multiple managed persons can be published.

[0087] In addition, when a personnel management document and a first document FD or compilation that have already been made public within a predetermined range coexist for a managed person, the disclosure unit 114 may be configured to disclose the first document FD or compilation that has been requested for disclosure as the personnel management document instead of the publicly disclosed personnel management document. In other words, when a personnel management document and a first document FD coexist as described above, the first document FD or compilation usually contains more recent information about the managed person. From this perspective, the first document FD or compilation that has been requested for disclosure can be disclosed as a new personnel management document.

[0088] The notification unit 119 may also notify the administrator that the first document FD or compilation for which a disclosure request has been accepted will be disclosed as a personnel management document instead of the disclosed personnel management document. This makes it less likely that errors will occur when the administrator performs bulk disclosure. Note that such a notification may be made, for example, via a warning screen CS as shown in FIG. 8.

[0089] On the other hand, such notification may be given only to the administrator, or may be given to the managed person in addition to the managed person. Also, in one aspect, a system may be constructed so that the managed person's confirmation and consent are obtained before such a first document FD or compilation is made public as a personnel management document.

[0090] Furthermore, the information management system 1 of this embodiment may be configured so that the administrator can collectively make public the personnel management documents. This operation is performed by switching the button BT1 in Fig. 7 to "all private" and having the administrator press the button BT1, thereby making the personnel management documents for multiple managed persons private. Note that the private state here is exemplified by the case where the disclosure range is the range corresponding to the first document FD, etc.

[0091] (Details of the process for creating the first document FD) Next, the process of creating the first document FD will be described in detail. The first document FD, which is positioned as a draft (rough draft) of the human resources management document, is composed of multiple document components. In a typical embodiment, the document components include a first document component, which is a keyword included in the registration information, and a second document component, which 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 multiple databases included in the personnel database D10.

[0092] The creation unit 112 extracts keywords included in the first registered information RI1 from the registered information as the first document component DC1, and creates a sentence created based on the second registered information RI2, which is different from the first registered information RI1, as the second document component DC2. That is, in this embodiment, it is desirable to accept two or more categories of registered information related to the people to be managed who work in the organization, and create the first document FD using this information. The creation unit 112 selects a procedure for converting the registered information into document components depending on the form or category of the registered information. This makes it possible to convert multiple pieces of registered information from different categories into appropriate forms as elements of a human resources management document and integrate them into a single document.

[0093] The first registration information RI1 is registration information that is converted into a first document component DC1 or a second document component DC2 by the creation unit 112 from among the registration information registered in the database. The first registration information RI1 is information described using keywords or numerical values. Examples of the first registration information RI1 include basic information acquired from the basic information database D101, position information acquired from the position database D103, skill information acquired from the skill database D104, condition acquired from the condition survey database D106, eNPS acquired from the organization diagnosis survey database D107, and aptitude or personality acquired from the original survey database D108. The creation unit 112 may generate multiple 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 multiple categories.

[0094] The second registered information RI2 is registered information that is registered in the database and converted into the first document component DC1 or the second document component DC2 by the creation unit 112. The second registered information RI2 is information described in sentences. Examples of the second registered information RI2 include goals or evaluations obtained from the goal evaluation database D102, hiring information obtained from the hiring database D105, 1-on-1 history obtained from the interview database D109, and attendance information obtained from the attendance database D110.

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

[0096] Extraction of the first document constituent DC1 from the first registered information RI1 is performed by referring to first reference information including the correlation between the first registered information RI1 and the first document constituent DC1. As the first reference information, for example, an extraction item list is used. The extraction item list lists candidates (samples) for each item, such as department, job, etc., and the creation unit 112 extracts keywords corresponding to each item from the registered information and sets them as the first document constituent DC1. Therefore, the first document constituent DC1 may include multiple keywords.

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

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

[0099] The second document component DC2, which is a summary of the sentence included in the second registered information RI2, is created by referencing second reference information including the correlation between the second registered information RI2 and the second document component DC2. For example, the second reference information may be a summarization model, which is a learning model trained to use the second registered information RI2 as input and output the second document component DC2. For example, the summarization model is a learning model trained using the second registered information RI2 and the corresponding second document component DC2 as training data. The creation unit 112 inputs the second registered information RI2 into the summarization model of the artificial intelligence unit 117 and causes the summarization model to output the second document component DC2. The summarization model may also be a generative AI including a large-scale language model. In this case, the creation unit 112 inputs a prompt containing an instruction to summarize the sentence included in the second registered information RI2 and the second registered information RI2 to the summarization model, and causes the summarization model to output the second document component DC2. In addition, the creation unit 112 may input a prompt into the summary creation model that, in addition to the summary creation instruction and the second registered information RI2, includes, for example, one or more samples of the second registered information RI2 and one or more corresponding samples of the second document components DC2.

[0100] As described above, the creation unit 112 may create a new sentence as the second document component DC2 by combining multiple keywords included in the first registered information RI1 or multiple keywords included in the sentence of the second registered information RI2. The creation of a new sentence based on the first registered information RI1 or the second registered information RI2 is performed by referring to third reference information including a correlation between the new sentence and the first registered information RI1 or the second registered information RI2. As the third reference information, for example, a sentence creation model is used, which is a learning model trained to input the first registered information RI1 or the second registered information RI2 and output the second document component DC2. For example, the sentence creation model is a learning model trained using the first registered information RI1 or the second registered information RI2 and the corresponding second document component DC2 as training data. The creation unit 112 inputs the first registered information RI1 or the second registered 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. The sentence creation model may also be a generative AI including a large-scale language model. In this case, the creation unit 112 inputs an instruction to create a new sentence based on the first registered information RI1 or the second registered information RI2 and a prompt into which the first registered information RI1 or the second registered information RI2 is inserted, to the writing creation model, and causes the writing creation model to output the second document constituent DC2. Furthermore, the creation unit 112 may input, to the writing creation model, a prompt into which, in addition to the sentence creation instruction and the first registered information RI1 or the second registered information RI2, for example, one or more samples of the first registered information RI1 or the second registered information RI2 and one or more corresponding samples of the second document constituent DC2 are inserted.

[0101] The creation unit 112 determines whether the acquired registered information is the first registered information RI1 or the second registered 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) that receives the registered information as input, determines whether the input registered information is the first registered information RI1 or the second registered information RI2, and then outputs 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 registered information of multiple categories, or may generate one document component from the registered information of multiple categories. Furthermore, the creation unit 112 may generate multiple document components from the registered information of one category. For example, in FIG. 5, a first document component DC1 of "possessed skills / job type" and a second document component DC2 of "internal career" are generated from the registered information of "goals / evaluation." Furthermore, a first document component DC1 of "educational background / job type / qualifications at time of employment" and a second document component DC2 of "offer content / evaluation" are generated from the registered information of "information at time of employment."

[0103] (Details of Document 1 FD) In connection with the processing of the creation unit 112 described above, the first document FD will also be described in detail. As can be seen 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 FIG. 9-12, multiple document components are grouped by the following categories: "basic information" (elements based on the basic information database D101), "hiring history" (elements based on the recruitment database D105), "hiring evaluation" (elements also based on the recruitment database D105), "experience / skills" (elements based on the goal evaluation database D102, the position database D103, and the skill database D104), "internal evaluation history" (elements also based on the goal evaluation database D102), and "internal history" (elements based on multiple databases). The second document component DC2 included in the "internal evaluation history" in FIG. 10 includes the name and photograph of the evaluator, as well as the evaluation content (e.g., comments). The "internal evaluation history" also includes the first document component DC1, which includes the evaluation value (e.g., "S") and the evaluator.

[0104] The document components may include a job summary of the person to be managed within the organization. The "job summary" describes the person's work history within the organization, and corresponds to the "internal experience" item in the example of Figure 12. The job summary describes, for example, the department, role or job type, job content, results or achievements, etc. for a predetermined period (yearly in the example of Figure 12). This allows the manager to easily consider the suitability of the person to be managed for a new position based on the job summary. The job summary ("internal experience") may also include time-series data showing changes over time in the person's attributes, such as their personality, characteristics, and condition.

[0105] The registration information that the creation unit 112 converts into document components preferably includes organizational goals of the managed person. Goals within an organization are likely to be created by the managed person in the operation of the organization, and are likely to include information about the job content within the organization. Therefore, including organizational goals in the registration information makes it possible to create a more reliable and accurate record of the managed person's work history within the organization. This also enables personnel searches based on goals, and allows other information about the managed person to be confirmed in the personnel management document along 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 places the second document component DC2 in the first document FD.

[0106] Furthermore, the registration information that the creation unit 112 converts into document components may preferably further include, in addition to goals, the organizational evaluation of the managed person. The creation unit 112 creates a job summary based on the registration information including goals and evaluations. The organizational evaluation is likely to exist as objective information about the managed person in the organization's management, and is likely to include information about the job content (especially achievements, track record, etc.) within the organization. This allows the managed person's work history within the organization to be created more reliably and accurately. Furthermore, the manager can confirm the goals, their evaluations, and the degree of goal achievement. The creation unit 112 generates a second document component DC2 by integrating and summarizing the goals and evaluations included in the registration information, and places the second document component DC2 in the first document FD. For example, the second document component DC2 included in the "Summary" in the "Internal Career" section of FIG. 11 is generated based on the goals and achievements stored in the goal evaluation database D102. In particular, the "Summary" section includes a second document component DC2 including the degree of goal achievement calculated based on the evaluation-related text. The achievement level may include the main achievement (achievement rate of the major goal) and sub-achievements (achievement rate of the sub-goals into which the major goal is subdivided). The "summary" may also be information that combines both internal and external experience. Furthermore, the "summary" may be generated based on a variety of internal information, such as position information, project information, etc., in addition to goals or evaluations.

[0107] The creation unit 112 may also be configured to create a job summary so that the job summary for a predetermined period fits within a specified display area. This reduces the need to scroll the screen displayed on the administrator terminal 20, etc., and makes it easier to understand the employee's work history. The "predetermined period" can be set by the creator (editor) of the first document FD, and in the example of FIG. 12, it is three years ago. By setting the predetermined period to a relatively recent period from the present, the reflection of low-priority old information in the personnel management document is suppressed. The creation unit 112 may also change the size of the display area (number of characters displayed), the font or size of the characters, etc., for each year. For example, the creation unit 112 may increase the display area to display more information or display the information in more prominent characters for newer information in the job summary.

[0108] The "designated display area" is, for example, an area that can be displayed in one page on the screen of the administrator terminal 20 or the managed person terminal 30. The creation unit 112 adjusts the number of items, font size, amount of information, etc. so that the job summary fits within the designated display area. The reception unit 111 may also receive the size (number of pages) of the display area for 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 that it fits within the received display area.

[0109] In the example of FIG. 12, the job summary ("Internal Experience") includes "Summary," "Extracted Skills," and Work Experience JH, but the job summary may also consist of only Work Experience 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 experience are displayed as tags TG2. Also, in Work Experience JH, for example, department by year, position (role, title), job type, etc. are displayed as tags TG2.

[0110] The registration information that the creation unit 112 converts into document components includes information about the managed person before he joined the organization and information about the managed person after he joined the organization, and the document components preferably include information about the managed person before he joined the organization. This makes it possible to refer to information about the managed person before he was hired by the organization in a single human resources management document. The creation unit 112 generates a second document component DC2 that summarizes the information about the managed person before he joined the organization, which is included in the registration information, and places it in the first document FD.

[0111] For example, the second document component DC2 included in "Work History" in "Hiring History" in FIG. 10 is generated based on information before the managed person joined the organization (information at the time of hiring stored in the hiring database D105). The second document component DC2 included in "Work History" may be generated based on information at the time of hiring (such as a resume) of the managed person. The first document component DC1 (evaluation value, evaluator, etc.) and the second document component DC2 (comments, etc.) included in "Hiring Evaluation" in "Hiring Evaluation" in FIG. 9 are also generated based on information before the managed person joined the organization. Both the "Hiring History" and the "Hiring Evaluation" include the first document component DC1, which is a keyword extracted from information before the managed person joined the organization. The second document component DC2 included in "Hiring Evaluation" includes an evaluation at the time of the interview ("S"), the name and face photo of the interviewer, and the evaluation content.

[0112] 10, the creation unit 112 generates a first document component DC1 and a second document component DC2 from the “recruitment information.” Specifically, the creation unit 112 generates the first document component DC1 by extracting keywords from registered information such as educational background included in the “recruitment information,” and generates the second document component DC2 by summarizing the text of registered information such as interview evaluation included in the “recruitment information.”

[0113] The registration information that the creation unit 112 converts into document components may include attribute information of the managed person. Typically, the creation unit 112 may create a first document FD that includes tags related to the attribute information as document components. This makes it easier to visually grasp the attributes of the managed person. "Attribute information of the managed person" is, for example, information indicating the position, career, experience, skills, qualifications, etc. of the managed person. Tags are objects made from keywords that represent the attribute information of the managed person. Tags may also be tags that combine multiple categories or tags that have a hierarchical structure. An example of a tag that combines multiple categories is "Sales: 10 years." An example of a tag that has a hierarchical structure is "Management: Organizational design."

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

[0115] In the example of Figure 11, the tag TG2 is included in the "Experienced Job Type" and "Possessed Skills" items in the "Experience / Skills" section. The tag TG2 is placed in the first document FD for each type of position, job type, skill / qualification, etc. Also, as shown in Figure 12, the tag TG2 may be included in the job summary.

[0116] The tag TG2 should be the same as the tag assigned to job seeker information registered in the job seeker database. The "job seeker database" is a database that stores registered information about job seekers, including their resumes, curriculum vitae, and other profile information. This allows administrators to search for internal talent based on tags in a similar way to searching for job seekers using tags. Note that a "resume" is a document that primarily contains a job seeker's profile, current situation, educational background, work history, desired working conditions, etc., while a "curriculum vitae," also known as a resume, is a document in which a job seeker conveys to an employer their work history, experience, skills, qualifications, etc.

[0117] The job seeker database is a database that is open to users of the recruitment service, distinct from the organization's internal employee database, and is typically located outside the organization. If the tag TG2 included in the first document FD is shared with the tag assigned to the job seeker information, the creation unit 112 references a tag list used in the job seeker database to tag the registered information or document components. The creation unit 112 may also generate the tag TG2 by reference to a job type dictionary, skill dictionary, in-house terminology dictionary, etc. used in the job seeker database.

[0118] The job seeker database may also be a database of job candidates registered in an organization's internal database (for example, a talent pool).

[0119] Furthermore, although not shown, the creation unit 112 may calculate the generation accuracy of the first document FD based on the amount of information in the registered information. The generation accuracy is presented before the first document FD is created, or is displayed on the viewing terminal (the administrator terminal 20 or the managed person terminal 30) together with the created first document FD. This allows information management of personnel within an organization to be performed while checking the reliability of the personnel management document.

[0120] For example, the creation unit 112 evaluates the generation accuracy higher the more the number of registered information items acquired by the creation unit 112. For example, if registration information for all items of the set (specified by the inputter) registered information items can be acquired from the database, the generation accuracy is 100%. On the other hand, if registration information for some items cannot be acquired because there is information that is not registered for the set registered information items, the generation accuracy is less than 100%. The more items that cannot be acquired, the lower the generation accuracy. Note that the creation unit 112 can also leave blank any items based on registration information that could not be acquired in the first document FD. Furthermore, the creation unit 112 may evaluate the generation accuracy higher the greater the amount of information (amount of text) in the acquired registered information.

[0121] Such generation accuracy may be displayed in the header HD of the primary document FD. The generation accuracy may also be stored in the storage unit 12 of the server device 10 as internal data related to the human resources management document. The creation unit 112 may also calculate the generation accuracy for each item or each document component of the primary document FD and present or display it.

[0122] The configuration, items, layout, etc. of the primary document FD shown in Figures 9-12 are merely examples, and the structural design of the information, order, etc. written on the primary document FD can be set arbitrarily.

[0123] 4. Effect The operation of this embodiment can be summarized as follows: In other words, in the information management method of this embodiment, when the disclosure receiving unit 113 receives a disclosure request from a predetermined person, the first document FD or an edited version thereof is made public to a predetermined range as a personnel management document. This allows for proper management of personnel management documents.

[0124] Although the embodiment of the present invention has been described above, the present invention is not limited to this and can be modified as appropriate within the scope of the technical idea of ​​the invention.

[0125] 5.Other In the above embodiment, the server device 10 performs various storage and control operations, but multiple external devices may be used instead of the server device 10. That is, various information and programs may be distributed and stored in multiple external devices using block chain technology or the like.

[0126] In the above embodiment, the administrator collectively creates the first documents and publishes the first documents, etc. However, the creation and publication of the first documents, etc. may be performed by the managed person. Typically, the first documents, etc. created and published by the managed person are related to the managed person himself / herself. The creation and publication of such first documents, etc. may be performed by the managed person operating his / her own terminal, the managed person terminal 30.

[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 steps executed by the information management system 1. The program causes a computer to execute the steps of the information management system 1.

[0128] It may be provided in the following manner.

[0129] (1) An information management system comprising at least one processor, the processor being configured to execute each of the following steps by reading a program: a receiving step receiving registration information about managed persons working in an organization, which is registered in a database within the organization; a creation step creating a first document related to a human resources management document including document components derived from the registration information, wherein the document components include text created based on the registration information; a publication receiving step receiving a publication request from the managed persons and / or an administrator of the managed persons to make the first document or a compilation of the first document public to a specified range; and a publication step publishing the first document or the compilation as a human resources management document to the specified range based on the acceptance of the publication request.

[0130] (2) In the information management system described in (1) above, 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.

[0131] (3) In the information management system described in (1) or (2) above, in the editing step, the edited product is generated by accepting edits to the first document created in the creation step from the managed person and / or the administrator.

[0132] (4) In the information management system described in (3) above, in the editing step, upon accepting edits to the first document by the managed person, editing authority for the edited work is restricted to only the managed person.

[0133] (5) In the information management system described in any one of (1) to (4) above, the first document and / or the human resources management document displays tags related to at least one of the number of times the first document has been edited, the creator of the first document, the editor of the first document, the status regarding the creation status of the human resources management document, and the status regarding the publication status of the human resources management document.

[0134] (6) In the information management system described in any one of (1) to (5) above, in the reception step, an input of an instruction to collectively create the first documents for multiple managed persons is received from the administrator, and in the creation step, the first documents for each of the multiple managed persons are created.

[0135] (7) In the information management system described in (6) above, a limit is set on the number of times the batch creation instruction can be input within a predetermined period in the organization.

[0136] (8) In the information management system described in (6) or (7) above, in the notification step, if there is an existing first document or edited work for any of the multiple managed persons, the information management system notifies the administrator that a new first document will be created in place of the existing first document or edited work.

[0137] (9) In the information management system described in any one of (1) to (8) above, in the disclosure acceptance step, a disclosure request for multiple first documents or edited works is accepted from the administrator, and in the disclosure step, the multiple first documents and / or edited works are disclosed to a specified range corresponding to each of them.

[0138] (10) In the information management system described in (9) above, in the disclosure step, when the human resources management document that has already been made public within the specified range coexists with the first document or the edited work for the managed person, the first document or the edited work for which the disclosure request was accepted is made public as the human resources management document instead of the publicly-available human resources management document.

[0139] (11) In the information management system described in (10) above, in the notification step, the administrator is notified that the first document or the edited material for which the disclosure request was accepted will be made public as the human resources management document instead of the publicly disclosed human resources management document.

[0140] (12) In the information management system described in any one of (1) to (11) above, in the display control step, the status regarding the creation status of the human resources management documents for the multiple managed persons is displayed to the manager in a listable manner.

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

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

[0143] Finally, while various embodiments of the present disclosure have been described, they are presented as examples and are not intended to limit the scope of the invention. The novel embodiments may be embodied in various other forms, and various omissions, substitutions, and modifications may be made without departing from the spirit of the invention. Such embodiments and modifications are intended to be included within the scope and spirit of the invention, as well as within the scope of the inventions and their equivalents as defined in the claims. [Explanation of symbols]

[0144] 1: Information Management System 2: Communication line 10: Server device 11: Control section 12: Storage section 13: Communications Department 14: Communication bus 20: Administrator terminal 21: Control unit 22: Storage section 23: Communications Department 24: Input section 25: Output section 26: Communication bus 30: Managed device 31: Control unit 32: Storage section 33: Communications Department 34: Input section 35: Output section 36: Communication bus 111: Reception 112: Creation Department 113: Public Reception Department 114: Public Section 115: Display control unit 116: Editorial Department 117: Artificial Intelligence Department 118: Condition setting section 119: Notification Department 211:Display section 212: Operation reception unit 311: Display section 312: Operation reception section AT: Attribute BT1~BT5: Buttons CB: Checkbox 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: Tissue 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: Editing screen FD: Document 1 HD: Header JH: Work history NM : Name RI1: First registration information RI2: Second registration information ST: Step STT: Status TG1, TG2: Tags

Claims

1. 1. An information management system, comprising: at least one processor; The processor is configured to execute the following steps by reading the program: In the receiving step, registration information regarding a person to be managed who works in the organization and is registered in a database within the organization is received; In the creation step, a first document related to a human resources management document is created, the first document including document components derived from the registration information, wherein the document components include sentences created based on the registration information; In the disclosure acceptance step, a disclosure request for disclosing the first document or the compilation of the first document to a predetermined range is accepted from the managed person and / or an administrator of the managed person; In the disclosure step, the first document or the compilation is disclosed to the predetermined range as a human resources management document based on the acceptance of the disclosure request.

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

3. 2. The information management system according to claim 1, In the editing step, the edited product is generated by accepting edits to the first document created in the creating step from the person to be managed and / or the administrator.

4. 4. The information management system according to claim 3, In the editing step, when edits to the first document by the managed person are accepted, editing authority for the edited product is restricted to only the managed person.

5. 2. The information management system according to claim 1, An information management system in which the first document and / or the human resources management document displays 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 resources management document, and the status regarding the publication status of the human resources management document.

6. 2. The information management system according to claim 1, In the receiving step, an input of a batch creation instruction for the first documents for the plurality of managed users is received from the administrator, In the creating step, the first document is created for each of the plurality of managed persons.

7. 7. The information management system according to claim 6, An information management system in which a limit is set on the number of times the batch creation instruction can be input within a predetermined period in the organization.

8. 7. The information management system according to claim 6, In the notification step, if there is an existing first document or edited work for any of the multiple managed persons, the information management system notifies the administrator that a new first document will be created in place of the existing first document or edited work.

9. 2. The information management system according to claim 1, In the disclosure acceptance step, a disclosure request for a plurality of the first documents or the compilations is accepted from the administrator; In the publishing step, the plurality of first documents and / or the compilations are published to respective corresponding predetermined ranges.

10. 10. The information management system according to claim 9, In the disclosure step, when the human resources management document that has already been made public within the specified range coexists with the first document or the edited work for the managed person, the information management system discloses the first document or the edited work for which the disclosure request was accepted as the human resources management document instead of the publicly disclosed human resources management document.

11. 11. The information management system according to claim 10, In the notification step, the information management system notifies the administrator that the first document or the edited material for which the disclosure request was accepted will be made public as the human resources management document instead of the publicly disclosed human resources management document.

12. 2. The information management system according to claim 1, In the display control step, the information management system displays, to the manager, a status relating to the creation status of the human resource management document for the plurality of managed persons in a browsable manner.

13. 1. An information management method, comprising: An information management method comprising the steps executed by the information management system according to any one of claims 1 to 12.

14. A program, A program for causing a computer to execute each step of the information management system according to any one of claims 1 to 12.

Images