Information management system, information management method, and program

Abstract

We provide an information management system that enables the efficient creation of personnel management documents. [Solution] According to one aspect of the present invention, an information management system is provided. This information management system comprises a processor. The processor is configured to perform the following steps: In the reception step, it receives registration information of two or more categories relating to managed persons working for the organization, which is registered in a database within the organization. In the personnel management document creation step, it creates a personnel management document that includes document components derived from the registration information. The document components include text created based on the registration information.

Description

Technical Field

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

Background Art

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

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] For a human resource management document for managing human resources within an organization, in addition to basic information such as the name of the person to be managed, descriptions of sentences corresponding to each person to be managed are required for a plurality of categories such as goals, evaluations / achievements, and work histories within the organization. Therefore, even when a document template is automatically created by the above-described technique, it is not possible to create a sentence corresponding to each person to be managed, and a certain amount of labor for inputting items is required for the administrator or the person to be managed.

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

Means for Solving the Problems

[0006] According to one aspect of the present invention, an information management system is provided. This information management system comprises a processor. The processor is configured to perform the following steps: In the reception step, it receives registration information for two or more categories relating to managed persons working for the organization, which is registered in a database within the organization. In the personnel management document creation step, it creates a personnel management document that includes document components derived from the registration information. The document components include text created based on the registration information.

[0007] In this configuration, it is possible to automatically generate human resource management documents containing document components (items) of different categories based on the registration information in the organization's database. Therefore, human resource management documents can be created efficiently. [Brief explanation of the drawing]

[0008] [Figure 1] This is a diagram illustrating the configuration of Information Management System 1. [Figure 2] This is a block diagram showing the hardware configuration of server device 10. [Figure 3] This block diagram shows the hardware configuration of the administrator terminal 20 and the managed user terminal 30. [Figure 4] This block diagram shows the functions realized by the server device 10 (control unit 11), the administrator terminal 20 (control unit 21), and the managed user terminal 30 (control unit 31). [Figure 5] This is a block diagram showing an example of the configuration of the personnel database D10. [Figure 6] This figure shows an example of a personnel management document (PD). [Figure 7] This figure shows a different part of the Human Resources Management Document PD than Figure 6. [Figure 8] This diagram shows a different part of the Human Resources Management Document PD than Figures 6 and 7. [Figure 9] This diagram shows a different part of the Human Resources Management Document PD than Figures 6-8. [Figure 10] This figure shows an example of the generation accuracy display screen CS. [Figure 11] This figure shows an example of the editing screen ED. [Figure 12] This is an activity diagram showing the flow of information processing (creation of personnel management documents) performed by Information Management System 1. [Modes for carrying out the invention]

[0009] Embodiments of the present invention will be described below with reference to the drawings. The various features shown in the embodiments below can be combined with each other.

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

[0011] Furthermore, in this embodiment, "part" may include, for example, hardware resources implemented by circuits in a broad sense, and the information processing of software that can be specifically realized by these hardware resources. In addition, various types of information are handled in this embodiment, and these types of information can be represented, for example, by the physical values ​​of signal values ​​representing voltage and current, the high or low values ​​of signal values ​​as a set of binary bits composed of 0s or 1s, or by quantum superposition (so-called qubits), and communication and calculations can be performed on circuits in a broad sense.

[0012] In addition, a circuit in a broad sense is a circuit realized by appropriately combining at least a circuit (Circuit), circuitry (Circuitry), a processor (Processor), a memory (Memory), etc. That is, it includes an application specific integrated circuit (ASIC), programmable logic devices (for example, a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)), etc.

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

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

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

[0016] The information management system 1 mainly creates and displays human resource management documents about the management target. In one embodiment, the information management system 1 consists of one or more devices or components. Hereinafter, these components will be described.

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

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

[0019] <Storage unit 12> The storage unit 12 stores various types of information as defined above. This can be done, for example, as a storage device such as a solid-state drive (SSD) that stores various programs related to the server device 10 executed by the control unit 11, or as memory such as random access memory (RAM) that stores temporarily necessary information (arguments, arrays, etc.) related to program calculations. The storage unit 12 stores various programs, variables, etc. related to the server device 10 executed by the control unit 11.

[0020] <Communications Department 13> The communication unit 13 preferably uses wired communication methods such as USB, IEEE1394, Thunderbolt®, and wired LAN network communication, but may also include wireless LAN network communication, mobile communication such as 3G / LTE / 5G, and Bluetooth® communication as needed. In other words, it is more preferable to implement it as a collection of these multiple communication methods. That is, the server device 10 may communicate various information from the outside via the communication unit 13 and the network.

[0021] The server device 10 may be on-premises or in a cloud environment. In the case of a cloud-based server device 10, for example, it may provide the above-mentioned functions and processing in the form of SaaS (Software as a Service) or cloud computing.

[0022] <Administrator terminal 20> Figure 3 is a block diagram showing the hardware configuration of the administrator terminal 20 and the managed user terminal 30. As shown in Figure 3A, the administrator terminal 20 comprises 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, storage unit 22, communication unit 23, input unit 24, and output unit 25 are electrically connected within the administrator terminal 20 via the communication bus 26. The descriptions of the control unit 21, storage unit 22, and communication unit 23 are the same as the descriptions of each part in the server device 10 and are therefore omitted.

[0023] <Input section 24> The input unit 24 receives operation inputs made by the user. The operation inputs are transmitted as command signals to the control unit 21 via the communication bus 26. The control unit 21 can perform predetermined controls or calculations based on the transmitted command signals as needed. The input unit 24 may be included in the casing of the administrator terminal 20 or it may be an external component. 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, the input unit 24 can be a switch button, mouse, trackpad, QWERTY keyboard, etc.

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

[0025] <Managed user terminal 30> As shown in Figure 3B, the managed user terminal 30 comprises 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, storage unit 32, communication unit 33, input unit 34, and output unit 35 are electrically connected within the managed user terminal 30 via the communication bus 36. The descriptions of the control unit 31, storage unit 32, communication unit 33, input unit 34, and output unit 35 are the same as the descriptions of each part in the administrator terminal 20 and are therefore omitted.

[0026] 2. Functional Configuration This section describes the functional configuration of this embodiment. Information processing by software stored in the memory 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 (processor provided by the information management system 1).

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

[0028] As shown in Figure 4A, the server device 10 (control unit 11) comprises an information acquisition unit 111, a reception unit 112, a personnel management document creation unit 113, a condition setting unit 114, a display control unit 115, an editing unit 116, and an artificial intelligence unit 117. As shown in Figure 4B, the administrator terminal 20 (control unit 21) comprises a display unit 211 and an operation reception unit 212. As shown in Figure 4C, the managed user terminal 30 (control unit 31) comprises a display unit 311 and an operation reception unit 312.

[0029] <Information acquisition section 111> The information retrieval unit 111 is configured to retrieve registration information for each of several managed persons necessary for creating personnel management documents from the organization's database. Managed persons are, for example, the organization's employees (regular employees, temporary employees, and contract employees). The organization's database is accessible only to those affiliated with the organization, and the data is not made public or provided to those outside the organization. Organizations include for-profit corporations (e.g., companies), non-profit corporations (e.g., cooperatives, foundations, etc.), public corporations (e.g., local governments, etc.), etc.

[0030] The organization's databases include a human resources database. Figure 5 is a block diagram showing an example of the configuration of the human resources database D10. The human resources database D10 includes, for example, a basic information database D101, a goal evaluation database D102, a position database D103, a skills database D104, a recruitment database D105, a condition survey database D106, an organizational diagnostic 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) for each person being managed. The recruitment database D105 stores recruitment data for new graduates and recruitment data for mid-career hires. In addition, the position database D103 and the skills database D104 may be part of the basic information database D101 or the goal evaluation database D102.

[0031] The registered information about managed individuals stored in the HR database D10 is HR information and is classified into several categories. These categories include, for example, the managed individual's name, gender, age, employee code, contact information, department, employment type, work location, job duties, organizational goals set by the managed individual, manager's evaluation of those goals, information about the managed individual before joining the organization (recruitment information), the managed individual's condition, engagement (e.g., eNPS), suitability or personality, interview history (interviewer, content of statements, etc.), and attendance information (overtime hours, number of annual leave days taken, etc.). Recruitment information includes the offered position, annual salary, interviewer, evaluation, aptitude test results, and reference check information. Information other than recruitment information is information acquired after joining the organization (post-recruitment information).

[0032] The categories of registered information are distinguished by several attributes. Attributes that distinguish categories include, for example, the registration date of the information reflected in the registration information and the method of information description. Regarding registration date, basic information such as name, gender, and age is information from the time of hiring or transfer to the organization. Furthermore, goals and evaluations are information from the time they were implemented, and their registration dates differ. Additionally, hiring information is information from before hiring to the organization. Therefore, these types of information are classified into different categories. On the other hand, regarding the method of information description, information described using keywords or numbers (e.g., name, affiliation, job title) is distinguished from information described in sentences (e.g., job description, goals, evaluation, condition). Therefore, the former and the latter types of information are classified into different categories. Furthermore, whether or not the information is unique is also exemplified as an attribute that distinguishes categories. Unique information includes names, etc. Non-unique information includes gender, affiliation, job title, etc. Moreover, the categories of registered information are not limited to the distinctions made by the attributes described above and may be arbitrarily set by the user.

[0033] The personnel database D10 includes both sub-databases containing information for one category (e.g., basic information database D101) and sub-databases containing information for multiple categories (e.g., goal and performance evaluation database D102).

[0034] <Reception Desk 112> The reception unit 112 is configured to receive input instructions for creating personnel management documents from data entry personnel within the organization. "Data entry personnel within the organization" includes administrators and managed personnel. In other words, the reception unit 112 receives input instructions for creating personnel management documents from either an administrator's terminal or a managed personnel's terminal (administrator terminal 20 or managed personnel terminal 30).

[0035] If the inputter is an administrator, the reception unit 112 receives input from the administrator terminal 20 regarding the managed individuals for whom the personnel management document is to be created. The administrator can select multiple managed individuals for whom the personnel management document is to be created. In other words, the reception unit 112 receives input from the administrator for batch creation of multiple personnel management documents.

[0036] If the inputter is a managed person, the reception unit 112 accepts the creation of a personnel management document concerning the inputter themselves from the managed person's terminal 30. In other words, the reception unit 112 does not accept the selection of the target for personnel management document creation from managed people. Thus, the reception unit 112 allows the selection of the target for personnel management document creation depending on the inputter.

[0037] Talent management documents are internal resumes (e.g., documents aggregating registration information) based on the registration information of managed individuals registered in the HR database. Talent management documents are made available for viewing within the organization. In principle, talent management documents are not made public outside the organization. By creating a talent management document for each managed individual, managers and others can easily search for talent within the organization using keywords, conditions (parameters), etc. Talent management documents are referenced, for example, in strategic personnel transfers, internal job postings, utilization of inactive talent, and support for career inventory.

[0038] The reception unit 112 receives registration information for two or more categories relating to managed persons working for the organization, which is registered in the organization's database. For example, along with instructions to create a personnel management document, the reception unit 112 receives registration information (items) to be used to create the personnel management document, or the settings of the database containing the registration information, from the administrator terminal 20 or the managed person terminal 30, and retrieves the configured registration information or the registration information contained in the configured database. The reception unit 112 may also automatically retrieve registration information (mandatory registration information) that has been set in advance by a user (e.g., a system administrator). The settings of the automatically retrieved registration information are stored, for example, in the storage unit 22.

[0039] <Human Resources Management Document Creation Department 113> The personnel management document creation unit 113 is configured to create a personnel management document that includes document components derived from the registration information received by the reception unit 112. The personnel management document creation unit 113 creates a personnel management document for a single managed person based on the registration information of that managed person.

[0040] When the reception unit 112 receives an input from the administrator terminal 20 for batch creation of multiple personnel management documents, the personnel management document creation unit 113 creates personnel management documents for each of the multiple managed persons. This allows the administrator to easily create personnel management documents for multiple managed persons in the information management system 1.

[0041] A human resources management document consists of multiple document components. These components include a first document component, which is a keyword included in the registration information, and a second document component, which contains text created based on the registration information. As shown in Figure 5, the human resources management document creation unit 113 obtains the first registration information RI1 or the second registration information RI2 received by the reception unit 112 from multiple databases included in the personnel database D10.

[0042] The Human Resources Management Document Creation Unit 113 extracts keywords included in the first registration information RI1 from the registered information as the first document component DC1, and creates a document based on the second registration information RI2, which is different from the first registration information RI1, as the second document component DC2. In other words, the Human Resources Management Document Creation Unit 113 selects a procedure for converting the registered information into document components according to 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 human resources management document.

[0043] The first registration information RI1 is registration information from the database that is converted into a first document component DC1 or a second document component DC2 by the personnel management document creation unit 113. The first registration information RI1 is information described by keywords or numerical values. Examples of the first registration information RI1 include basic information obtained from the basic information database D101, position information obtained from the position database D103, skill information obtained from the skill database D104, condition obtained from the condition survey database D106, eNPS obtained from the organizational diagnostic survey database D107, and suitability or personality obtained from the original survey database D108. The personnel management document creation unit 113 may generate multiple first document component DC1 from the first registration information RI1 of one category, or it may generate one first document component DC1 from the first registration information RI1 of multiple categories.

[0044] Second registration information RI2 is registration information from the database that is converted into first document component DC1 or second document component DC2 by the personnel management document creation unit 113. Second registration information RI2 is information described in text. Examples of second registration information RI2 include goals or evaluations obtained from the goal evaluation database D102, recruitment information obtained from the recruitment database D105, 1on1 history obtained from the interview database D109, and attendance information obtained from the attendance database D110.

[0045] As shown in Figure 5, the personnel management document creation unit 113 may generate multiple second document components DC2 from the second registration information RI2 of one category, or it may generate a first document component DC1 and a second document component DC2 from the second registration information RI2 of one category.

[0046] The extraction of the first document component DC1 from the first registration information RI1 is performed by referring to first reference information that includes the correlation between the first registration information RI1 and the first document component DC1. For example, an extraction item list is used as the first reference information. The extraction item list contains candidates (samples) for each item, such as department, job, etc., and the personnel management document creation unit 113 extracts keywords corresponding to each item from the registration information to form the first document component DC1. Therefore, the first document component DC1 may contain multiple keywords.

[0047] Furthermore, as the first reference information, a keyword extraction model may be used, which is a learning model that has been trained (machine learning or fine-tuned) to take the first registration information RI1 as input and output the first document component DC1. For example, the keyword extraction model is a learning model that has been trained using the first registration information RI1 and its corresponding first document component DC1 as training data. The personnel management document creation unit 113 inputs the first registration information RI1 into the keyword extraction model of the artificial intelligence unit 117 and causes the keyword extraction model to output the first document component DC1. Alternatively, the keyword extraction model may be a generative AI that includes a large-scale language model. In this case, the personnel management document creation unit 113 inputs an instruction to extract keywords from the first registration information RI1 and a prompt with the first registration information RI1 inserted into it into the keyword extraction model and causes the keyword extraction model to output the first document component DC1. Furthermore, the personnel management document creation unit 113 may input a prompt to the keyword extraction model that, in addition to the keyword extraction instruction and the first registration information RI1, includes, for example, one or more samples of the first registration information RI1 and one or more samples of the corresponding first document component DC1.

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

[0049] The creation of the second document component DC2, which is a summary of the text contained in the second registration information RI2, is performed by referring to second reference information that includes the correlation between the second registration information RI2 and the second document component DC2. As the second reference information, for example, a summarization model is used, which is a learning model that takes the second registration information RI2 as input and outputs the second document component DC2. For example, the summarization model is a learning model that has been trained using the second registration information RI2 and its corresponding second document component DC2 as training data. The personnel management document creation unit 113 inputs the second registration information RI2 into the summarization model of the artificial intelligence unit 117 and causes the summarization model to output the second document component DC2. Alternatively, the summarization model may be a generative AI that includes a large-scale language model. In this case, the personnel management document creation unit 113 inputs an instruction to summarize the text contained in the second registration information RI2 and a prompt inserting the second registration information RI2 into the summarization model and causes the summarization model to output the second document component DC2. Furthermore, the personnel management document creation unit 113 may input prompts to the summary creation model that, in addition to the summary creation instructions and the second registration information RI2, include, for example, one or more samples of the second registration information RI2 and one or more samples of the corresponding second document component DC2.

[0050] Furthermore, as described above, the personnel management document creation unit 113 may create a new document as a second document component DC2 by combining multiple keywords contained in the first registration information RI1 or multiple keywords contained in the text of the second registration information RI2. The creation of a new document based on the first registration information RI1 or the second registration information RI2 is performed by referring to third reference information that includes the correlation between the first registration information RI1 or the second registration information RI2 and the new document. As the third reference information, for example, a document creation model is used, which is a learning model that takes the first registration information RI1 or the second registration information RI2 as input and outputs the second document component DC2. For example, the document creation model is a learning model that has learned using the first registration information RI1 or the second registration information RI2 and the corresponding second document component DC2 as training data. The personnel management document creation unit 113 inputs the first registration information RI1 or the second registration information RI2 into the document creation model of the artificial intelligence unit 117 and causes the document creation model to output the second document component DC2. Furthermore, the document creation model may be a generative AI that includes a large-scale language model. In this case, the personnel management document creation unit 113 inputs an instruction to create a new document based on the first registration information RI1 or the second registration information RI2, and a prompt inserting the first registration information RI1 or the second registration information RI2 into the document creation model, causing the document creation model to output the second document component DC2. Alternatively, the personnel management document creation unit 113 may input a prompt to the document creation model that, in addition to the document creation instruction and the first registration information RI1 or the second registration information RI2, inserts, for example, one or more samples of the first registration information RI1 or the second registration information RI2 and one or more corresponding samples of the second document component DC2.

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

[0052] The Human Resources Management Document Creation Unit 113 may generate document components for each category from the registered information of multiple categories, or it may generate one document component from the registered information of multiple categories. Furthermore, the Human Resources Management Document Creation Unit 113 may generate multiple document components from the registered information of one category. For example, in Figure 5, the first document component DC1 of "Possessed Skills / Job Title" and the second document component DC2 of "Internal Career History" are generated from the registered information of "Goals / Evaluation". Also, the first document component DC1 of "Educational Background / Job Title / Qualifications at Time of Recruitment" and the second document component DC2 of "Offer Details / Evaluation" are generated from the registered information of "Recruitment Information".

[0053] Figure 6 shows an example of a personnel management document (PD). Figure 7 shows a different part of the personnel management document (PD) from Figure 6. Figure 8 shows a different part of the personnel management document (PD) from Figures 6 and 7. Figure 9 shows a different part of the personnel management document (PD) from Figures 6-8. As shown in Figure 6-9, the personnel management document (PD) includes a header (HD) and multiple document components (first document component DC1 and second document component DC2). The header (HD) contains the name, photograph, and affiliation of the person to be managed.

[0054] The Human Resources Management Document Creation Unit 113 may, for example, group document components based on registered information recorded in the same database within the Human Resources Management Document PD. In the example in Figure 6-9, multiple document components are grouped under the following items: "Basic Information" (elements based on the basic information database D101), "Hiring History" (elements based on the hiring database D105), "Hiring Evaluation" (elements also based on the hiring database D105), "Experience / Skills" (elements based on the target evaluation database D102, position database D103, and skills database D104), "Internal Evaluation History" (elements also based on the target evaluation database D102), and "Internal History" (elements based on multiple databases). Note that the second document component DC2 included in "Internal Evaluation History" in Figure 8 contains the evaluator's name and photograph, as well as the evaluation content (comments, etc.). In addition, "Internal Evaluation History" includes the first document component DC1, which includes the evaluation value ("S," etc.) and the evaluator.

[0055] The document components should ideally include a job summary of the person being managed within the organization. The "job summary" describes the person's work history within the organization and corresponds to the "internal career" section in the example in Figure 9. The job summary should include, for example, information for each specified period (yearly in the example in Figure 9), such as department, role or job type, work content, results or achievements. This allows managers to easily consider the suitability of the person being managed for a new position based on the job summary. The job summary ("internal career") may also include time-series data showing the changes in the person's attributes, such as personality, characteristics, and condition over time.

[0056] The registration information that the Human Resources Management Document Creation Unit 113 converts into document components should preferably include the organizational goals of the person being managed. Organizational goals are likely to be created by the person being managed in the course of organizational operations and are likely to contain information about their job duties within the organization. Therefore, including organizational goals in the registration information allows for a more reliable and accurate creation of the person's job history within the organization. Furthermore, it enables personnel searches based on goals, and other information about the person being managed can be confirmed in the human resources management document along with their goals. The Human Resources Management Document Creation Unit 113 generates a second document component DC2, which summarizes the goals, from the goals included in the registration information and places it in the human resources management document.

[0057] The registration information that the Human Resources Management Document Creation Unit 113 converts into document components should ideally include, in addition to goals, the evaluation of the managed person within the organization. The Human Resources Management Document Creation Unit 113 creates a job summary based on the registration information that includes goals and evaluations. Evaluations within the organization are likely to exist in organizational operations as objective information about the managed person, and are likely to include information about the job content within the organization (especially results, achievements, etc.). Therefore, the job history of the managed person within the organization can be created more reliably and accurately. In addition, managers can confirm goals, evaluations against them, and the degree of goal achievement. The Human Resources Management Document Creation Unit 113 generates a second document component DC2 that integrates and summarizes the goals and evaluations included in the registration information, and places it in the human resources management document. For example, the second document component DC2 included in the "Summary" in "Internal Career History" in Figure 9 is generated based on goals and results stored in the goal evaluation database D102. In particular, the "Summary" contains a second document component DC2 that includes the degree of goal achievement calculated based on the evaluation text. The achievement level may include both main achievements (the achievement rate against the major goal) and sub-achievements (the achievement rate against smaller goals that are subdivisions of the major goal). Furthermore, the "summary" may be information that combines both internal and external experience. In addition, the "summary" may be generated based on a wide range of internal information, such as position information and project information, not just goals or evaluations.

[0058] The personnel management document creation unit 113 creates job summaries so that the job summaries for a specified period fit within a designated display area. This reduces the need for administrators to move (scroll) the screen displayed on the administrator terminal 20, while making it easier for administrators to grasp the work history. The "specified period" can be set by the creator (editor) of the personnel management document, and in the example in Figure 9, it is three years ago from the present. By setting the specified period to a period from the present to the relatively recent past, the inclusion of older, low-priority information in the personnel management document is suppressed. The personnel management document creation unit 113 may also change the size of the display area (the number of characters displayed), the font or size of the text, etc., for each year. For example, the personnel management document creation unit 113 may increase the display area and display more information, or use more prominent fonts, for newer information within the job summary.

[0059] The "specified display area" is, for example, the area that can be displayed on one page on the screen of the administrator terminal 20 or the managed employee terminal 30. The personnel management document creation unit 113 adjusts the number of items, font size, amount of information, etc., so that it fits within the specified display area. Alternatively, the reception unit 112 may receive the size (number of pages) of the display area for the job summary from the administrator terminal 20 or the managed employee terminal 30, and the personnel management document creation unit 113 may create the job summary so that it fits within the received display area.

[0060] In the example in Figure 9, the job summary ("Internal Career") includes "Summary," "Extracted Skills," and Job History JH, but the job summary may consist only of Job History JH. "Summary" is an item that describes current achievements, etc., and "Extracted Skills" is an item where skills extracted from the career history are displayed as tags TG. Similarly, in Job History JH, for example, department, position (role, title), job type, etc., for each year are displayed as tags TG.

[0061] The registration information that the personnel management document creation unit 113 converts into document components includes information about the managed person before they joined the organization and information about the managed person after they joined the organization, and the document components should include information about the managed person before they joined the organization. This allows information about the managed person before they were hired by the organization, in addition to their career history within the organization, to be referenced in a single personnel management document. The personnel management document creation unit 113 generates a second document component DC2 that summarizes the information about the managed person before they joined the organization included in the registration information, and places it in the personnel management document.

[0062] For example, in Figure 7, the second document component DC2 included in "Work History" under "Hiring History" is generated based on information about the managed person before they joined the organization (hiring information stored in the hiring database D105). The second document component DC2 included in "Work History" may also be generated based on the managed person's hiring information (resume, etc.). Similarly, the first document component DC1 (evaluation value, evaluator, etc.) and the second document component DC2 (comments, etc.) included in "Hiring Evaluation" under "Hiring Evaluation" in Figure 7 are also generated based on information about the managed person before they joined the organization. Furthermore, both "Hiring History" and "Hiring Evaluation" include the first document component DC1, which is a keyword extracted from information about the managed person before they joined the organization. The second document component DC2 included in "Hiring Evaluation" includes the interview evaluation ("S"), the interviewer's name and photograph, and the evaluation content.

[0063] In the example shown in Figure 7, the Human Resources Management Document Creation Unit 113 generates the first document component DC1 and the second document component DC2 from the "Recruitment Information". Specifically, the Human Resources Management Document Creation Unit 113 extracts keywords from the registered information such as educational background included in the "Recruitment Information" to generate the first document component DC1, and summarizes the text of the registered information such as interview evaluations included in the "Recruitment Information" to generate the second document component DC2.

[0064] The registration information that the Human Resources Management Document Creation Unit 113 converts into document components includes attribute information of the person being managed, and the Human Resources Management Document Creation Unit 113 should create a human resources management document that includes tags related to attribute information as document components. This makes it easier to visually grasp the attributes of the person being managed. "Attribute information of the person being managed" refers to information such as the person being managed's position, career, experience, skills, qualifications, etc. Tags are objects that represent keywords that express the attribute information of the person being managed. 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 with a hierarchical structure is "Management: Organizational Design".

[0065] The personnel management document creation unit 113 tags, for example, keywords included in the registration information or the first document component DC1 that represent pre-specified attribute information. Specifically, the personnel management document creation unit 113 prepares a tag list in which multiple tags are written in advance, extracts tag words corresponding to the registration information or document component from the tag list, and tags the registration information or document component. Here, the tag list is a list in which one or more tag words are written.

[0066] In the example in Figure 8, the "Experienced Job Titles" and "Possessed Skills" sections of the "Experience / Skills" category include the tag TG. Tag TGs are placed in the talent management document PD for each type, such as position, job title, and skills / qualifications. Additionally, as shown in Figure 9, the job summary may also include the tag TG.

[0067] The tag TG should be the same as the tags assigned to job seeker information registered in the job seeker database. The "job seeker database" is a database that stores the registration information of job seekers, and this registration information includes the job seeker's resume, work history, and other profile information. This allows administrators to search for personnel within the company based on tags, in a similar way to searching for job seekers using tags. A "resume" is a document that mainly contains the job seeker's profile, current situation, educational background, work history, desired working conditions, etc. A "work history," also called a resume, is a document in which the job seeker conveys their past work history, experience, skills, qualifications, etc. to the employer.

[0068] The job seeker database is a database accessible to users of the recruitment service, distinct from the organization's internal employee database, and is typically located outside the organization. When tags TG included in the human resources management document are to be shared with tags assigned to job seeker information, the human resources management document creation unit 113 refers to the tag list used in the job seeker database and tags the registration information or document components. The human resources management document creation unit 113 may also generate tags TG by referring to the job dictionary, skills dictionary, company terminology dictionary, etc., used in the job seeker database.

[0069] Furthermore, the job seeker database may be a database of potential candidates registered within the organization's internal database (e.g., a talent pool).

[0070] The personnel management document creation unit 113 may calculate the accuracy of generating personnel management documents based on the amount of information in the registered information. The generation accuracy is presented before the creation of the personnel management document, or displayed on the viewing terminal (administrator terminal 20 or managed person terminal 30) along with the created personnel management document. This allows for the management of personnel information within the organization while confirming the reliability of the personnel management document.

[0071] The Human Resources Management Document Creation Unit 113 increases its generation accuracy as the number of registered information items it acquires increases. For example, if all registered information items for the set (specified by the inputter) registered information items can be acquired from the database, the generation accuracy will be 100%. On the other hand, if some registered information items cannot be acquired for reasons such as some information not being registered, the generation accuracy will be less than 100%. The more items that cannot be acquired, the lower the generation accuracy will be. The Human Resources Management Document Creation Unit 113 will leave blank any items in the human resources management document that are based on registered information that could not be acquired. The Human Resources Management Document Creation Unit 113 may also increase its generation accuracy as the amount of information (amount of text) in the registered information it acquires increases.

[0072] Figure 10 shows an example of a generation accuracy display screen CS. When the personnel management document creation unit 113 presents the generation accuracy before creating a personnel management document, the personnel management document creation unit 113 displays the generation accuracy display screen CS, including the generation accuracy, on the administrator terminal 20 or the managed person terminal 30. The administrator or managed person selects whether or not to create the personnel management document with the presented generation accuracy.

[0073] When the display control unit 115 displays the generation accuracy together with the personnel management document, for example, as shown in Figure 6, the generation accuracy GA is displayed at the top of the header HD of the personnel management document PD. Alternatively, the generation accuracy may be stored as internal data of the personnel management document, together with the document components included in the personnel management document.

[0074] The personnel management document creation unit 113 may calculate and display the generation accuracy for each item or document component of the personnel management document.

[0075] The personnel management document creation unit 113 may store in the storage unit 12, alongside personnel management documents created at the instruction of the person being managed and personnel management documents created at the instruction of the manager for the same person being managed. Furthermore, the personnel management document creation unit 113 may overwrite an earlier document with a later-created document, either one created at the instruction of the person being managed or one created at the instruction of the manager.

[0076] Note that the structure, items, and layout of the personnel management document PD shown in Figure 6-9 are just an example, and the structure design of the information, order, etc., included in the personnel management document PD can be arbitrarily set.

[0077] <Condition setting section 114> The condition setting unit 114 is configured to set viewing or editing conditions for the personnel management document according to the person who inputs the creation instruction. This allows for flexible adjustment of the management level of the personnel management document according to the inputter. For example, if the inputter is an administrator (e.g., the personnel department) (i.e., input from the administrator terminal 20), the viewing condition is set so that only the department to which the administrator belongs (the personnel department) and personnel-related decision-makers (e.g., management) can view the document, and no one else (including the person being managed who is the subject of the personnel management document) can view it. In this case, if the inputter is the person being managed (i.e., input from the person being managed terminal 30), the viewing condition is set so that only the person being managed, the administrator, and decision-makers can view the document, and no one else can view it.

[0078] The editing permission condition is, for example, if the inputter is an administrator (e.g., the human resources department), then editing is disabled for everyone. In this case, if the inputter is the person being managed, then only the person being managed can edit the data, and editing is disabled for everyone else.

[0079] Furthermore, the condition setting unit 114 may set viewing or editing conditions for each item in the personnel management document. For example, if the inputter is an administrator, only specific items such as "basic information" and "experience / skills" may be made editable, while all other items may be made uneditable for everyone. In addition, the condition setting unit 114 may set viewing or editing conditions for each document component.

[0080] <Display Control Unit 115> The display control unit 115 is configured to display the personnel management documents created by the personnel management document creation unit 113 on the administrator terminal 20 or the managed person terminal 30. Furthermore, the display control unit 115 displays the personnel management documents on the viewing terminals according to whether the viewer meets the viewing conditions for the personnel management documents. In other words, the display control unit 115 displays the personnel management documents only on viewing terminals that meet the viewing conditions set by the condition setting unit 114. This ensures the confidentiality of the personnel management documents.

[0081] <Editorial Department 116> The editorial department 116 is configured to accept edits to the personnel management documents created by the personnel management document creation department 113. Editing of the personnel management documents may involve directly accepting input to the items to be edited, or it may involve specifying items and then regenerating the document components for the specified items (i.e., re-acquiring the registration information).

[0082] The editorial department 116 accepts edits to personnel management documents depending on whether the editors meet the editing requirements for those documents. In other words, the editorial department 116 accepts edits to personnel management documents only from viewing terminals that meet the editing requirements set by the condition setting unit 114. This ensures the reliability of the personnel management documents.

[0083] The editing department 116 displays a screen that accepts edits to the personnel management document after the personnel management document creation department 113 has created the document. The editing department 116 may also accept edits (inputs) in stages for each item of the personnel management document. Figure 11 is a diagram showing an example of the editing screen ED. At the top of the editing screen ED, the step ST indicating the progress of editing is displayed. In the example in Figure 11, step ST shows that editing of the two items "Basic Information" and "External Career" has been completed, the third item, "Internal Career," is currently being edited, and there are two remaining items after "Internal Career" ("Career Summary" and "Other"). In addition, on the editing screen ED, an edit button EB is placed for each item generated by the personnel management document creation department 113, or for each editing unit that is a more detailed subdivision of an item. When the edit button EB is pressed, the corresponding entry can be edited. Editing of the entry can be performed, for example, by inputting text or words from the administrator terminal 20 or the managed person terminal 30, or by selecting a tag from tag candidates. For example, editorial staff 116 may display a list of tags extracted from the registration information as tag candidates. This allows users to edit the tags to be placed in the personnel management document by selecting any tag from the displayed list of tag candidates.

[0084] When editing of one item is completed, for example by clicking the "Complete" button, the editorial department 116 displays the editing screen ED for the next item in the order shown in step ST. In this way, the editorial department 116 switches the editing screen ED displayed on the administrator terminal 20 or the managed person terminal 30 for each item of the personnel management document, and accepts edits for each item. This makes it possible to accept edits while taking into account the mental model of the managed person (what they want to do or what they can understand).

[0085] Furthermore, the editorial department 116 may accept edits for each item on a screen that displays the entire personnel management document, without having to switch editing screens ED for each item.

[0086] Furthermore, the editorial department 116 may modify the editing steps depending on the editor. For example, if the editor is an administrator, they may complete the editing with a single click, for instance, without going through item-by-item editing (multiple steps). Moreover, if the person instructing the creation of the personnel management document is an administrator, the editing step itself may be skipped. When an administrator (e.g., HR) creates a personnel management document, they do not need to consider the mental model of the person being managed. Therefore, simplifying the editing steps allows administrators to create personnel management documents more easily without going through multiple steps.

[0087] <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 each functional unit of the server device 10 may be common to all units, or it may be prepared individually for each functional unit.

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

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

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

[0091] The artificial intelligence unit 117 includes a general-purpose natural language processing learning model, such as a Large Language Model (LLM), which has learned from a vast amount of data. Such a general-purpose learning model includes language models that can handle various tasks without fine-tuning using methods such as One-shot Learning and Few-shot Learning. 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 it may be a common general-purpose learning model.

[0092] The learning model included in the artificial intelligence unit 117 can undergo additional training. For example, the artificial intelligence unit 117 learns whether the created personnel management documents have been modified by the person who instructed them to create them. In other words, the artificial intelligence unit 117 performs additional training and fine-tunes the personnel management documents created by the learning model using a training dataset in which the actual modification results of the personnel management documents are labeled, as feedback to the personnel management documents created by the learning model. This optimizes the personnel management documents output from the learning model.

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

[0094] <Operation Reception Section> The operation reception unit 212 of the administrator terminal 20 accepts operations from the user (administrator) using the administrator terminal 20. The operation reception unit 312 of the managed user terminal 30 accepts operations from the user (managed user) using the managed user terminal 30.

[0095] 3. Information Processing Methods This section describes the information processing method of the server device 10. In this information processing method, each part of the server device 10 is executed by a computer as a step.

[0096] Specifically, this information processing method comprises a reception step and a personnel management document creation step. In the reception step, registration information for two or more categories concerning managed personnel working for the organization, registered in the organization's database, is received. In the personnel management document creation step, a personnel management document is created that includes document components derived from the registration information.

[0097] Figure 12 is an activity diagram showing the flow of information processing (creation of personnel management documents) performed by the information management system 1. The following sections will explain the information processing in accordance with each activity in this activity diagram.

[0098] The process of creating a personnel management document begins with the administrator selecting the person to whom the personnel management document will be created from the administrator terminal 20, or the person being managed selecting the person to whom the personnel management document will be created from the person being managed terminal 30 (Activity A101). Note that if the person being managed is creating the personnel management document, the selection of the person being managed (Activity A101) may be omitted, or only the person being managed may be selected as the target of the personnel management document creation. Furthermore, if the person being managed is creating the personnel management document, multiple people being managed can be selected. The administrator or person being managed then selects the items to be included in the personnel management document from the administrator terminal 20 or the person being managed terminal 30 (Activity A102).

[0099] The server device 10 obtains the registration information necessary to configure the items sent from the administrator terminal 20 or the managed user terminal 30 (reception step, activity A103). Subsequently, the server device 10 generates document components from the registration information (activity A104). Furthermore, the server device 10 creates a personnel management document using the document components (personnel management document creation step, activity A105).

[0100] After the personnel management document is created, the server device 10 controls the display of the personnel management document on the administrator terminal 20 or the managed person terminal 30 (Activity A106). As a result, the personnel management document is displayed on the administrator terminal 20 or the managed person terminal 30 (Activity A107). The administrator or managed person edits the displayed personnel management document on the administrator terminal 20 or the managed person terminal 30 as needed (Activity A108). The server device 10 accepts the editing of the personnel management document from the administrator terminal 20 or the managed person terminal 30 (Activity A109).

[0101] 4. Effect The operation of this embodiment can be summarized as follows: Based on the registration information in the organization's database, it is possible to automatically generate personnel management documents containing document components (items) of different categories. Therefore, personnel management documents can be created efficiently.

[0102] Although embodiments of the present invention have been described above, the present invention is not limited thereto and can be modified as appropriate without departing from the technical spirit of the invention.

[0103] 5. Others In the above embodiment, the server device 10 performed various storage and control functions, but instead of the server device 10, multiple external devices may be used. That is, various information and programs may be distributed and stored across multiple external devices using blockchain technology or the like.

[0104] The embodiments of this model are not limited to the information management system 1, but may also be an information processing method or a program. The information management method comprises each step executed by the information management system 1. The program causes a computer to execute each step of the information management system 1.

[0105] The product may be provided in any of the following embodiments.

[0106] (1) Information management system comprising a processor, the processor configured to perform the following steps: in the reception step, it receives registration information of two or more categories relating to managed persons working for the organization, which is registered in a database within the organization; and in the personnel management document creation step, it creates a personnel management document which includes document components derived from the registration information, wherein the document components include text created based on the registration information.

[0107] (2) An information management system described in (1) above, wherein the document component includes a newly created document using the keywords included in the registered information.

[0108] (3) An information management system described in (1) or (2) above, wherein the reception step receives input of instructions for creating the personnel management document from an inputter within the organization, and the personnel management document is made available for viewing within the organization.

[0109] (4) An information management system described in any one of (1) to (3) above, wherein the reception step receives input from an administrator for batch creation of multiple personnel management documents, and the personnel management document creation step creates the personnel management document for each of the multiple persons under management.

[0110] (5) An information management system according to any one of (1) to (4) above, wherein the document component includes a summary of the job duties of the person to be managed within the organization.

[0111] (6) An information management system as described in (5) above, wherein the registration information includes the goals of the person to be managed within the organization.

[0112] (7) An information management system as described in (6) above, wherein the registration information further includes the evaluation of the person to be managed within the organization, and in the personnel management document creation step, the information management system creates the job summary based on the registration information which includes the goals and the evaluation.

[0113] (8) An information management system described in any one of (5) to (7) above, wherein in the personnel management document creation step, the information management system creates the job summary such that the job summary for a predetermined period fits within a designated display area.

[0114] (9) An information management system described in any one of (1) to (8) above, wherein in the personnel management document creation step, keywords included in the first registration information from the registered information are extracted as document components, and a document created based on a second registration information different from the first registration information is created as a document component.

[0115] (10) An information management system according to any one of (1) to (9) above, wherein the registration information includes information of the managed person before he / she belonged to the organization and information of the managed person after he / she belonged to the organization, and the document components include information of the managed person before he / she belonged to the organization.

[0116] (11) An information management system according to any one of (1) to (10) above, wherein the processor is configured to perform the following steps: in the display control step, the system displays the personnel management document on a viewing terminal according to the viewer's satisfaction of the conditions for viewing the personnel management document; and in the editing step, the system accepts editing of the personnel management document from an editor according to the editor's satisfaction of the conditions for editing the personnel management document.

[0117] (12) An information management system as described in (11) above, wherein in the reception step, the system receives input of instructions to create the personnel management document from either the administrator's or the managed person's terminal, and in the condition setting step, the system sets the viewing conditions or editing conditions for the personnel management document according to the person who input the creation instructions.

[0118] (13) An information management system described in any one of (1) to (12) above, wherein in the personnel management document creation step, the accuracy of generating the personnel management document is calculated based on the amount of information in the registered information, and the accuracy of generation is presented before the creation of the personnel management document or displayed on the viewing terminal together with the created personnel management document.

[0119] (14) An information management system according to any one of (1) to (13) above, wherein the registration information includes attribute information of the person to be managed, and in the personnel management document creation step, a personnel management document is created that includes tags relating to the attribute information as document components.

[0120] (15) An information management system described in (14) above, wherein the tags are the same as the tags assigned to job seeker information registered in the job seeker database.

[0121] (16) An information management method comprising each step performed by the information management system described in any one of (1) to (15) above.

[0122] (17) A program that causes a computer to perform each step of the information management system described in any one of (1) to (15) above. Of course, this is not always the case.

[0123] Finally, while various embodiments relating to this disclosure have been described, these are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents. [Explanation of symbols]

[0124] 1: Information Management System 2: Communication lines 10: Server device 11: Control Unit 12: Storage section 13: Communications Department 14: Communications bus 20: Administrator terminal 21: Control Unit 22: Storage section 23: Communications Department 24: Input section 25: Output section 26: Communications bus 30: Managed device 31: Control Unit 32: Storage section 33: Communications Department 34: Input section 35: Output section 36: Communications bus 111: Information acquisition department 112: Reception Department 113: Human Resources Management Document Creation Department 114: Condition Setting Section 115: Display Control Unit 116: Editorial Department 117: Artificial Intelligence Department 211: Display section 212: Operation Reception Section 311: Display section 312: Operation Reception Section

Claims

1. It is an information management system, Equipped with a processor, The aforementioned processor is configured to perform the following steps: In the reception step, registration information for two or more categories relating to managed persons working for the organization, which is registered in the organization's database, is accepted. In the personnel management document creation step, a personnel management document is created that includes document components derived from the registration information, where the document components include text created based on the registration information, and is an information management system.

2. In the information management system described in claim 1, The document components include an information management system that contains newly created text using keywords included in the registered information.

3. In the information management system described in claim 1, In the aforementioned reception step, the input of instructions for creating the personnel management document is received from an inputter within the organization. The aforementioned personnel management documents are made available for viewing within the organization through an information management system.

4. In the information management system described in claim 1, In the aforementioned reception step, the administrator inputs instructions for the batch creation of multiple personnel management documents. The information management system, in the aforementioned personnel management document creation step, creates the aforementioned personnel management document for each of the multiple persons to be managed.

5. In the information management system described in claim 1, An information management system in which the document components include a summary of the job duties of the person being managed within the organization.

6. In the information management system described in claim 5, An information management system in which the registration information includes the goals of the managed person within the organization.

7. In the information management system described in claim 6, The registration information further includes the evaluation of the managed person within the organization, An information management system that, in the aforementioned personnel management document creation step, creates the job summary based on the registration information which includes the objectives and the evaluation.

8. In the information management system described in claim 5, An information management system that, in the aforementioned personnel management document creation step, creates the job summary such that the job summary for a predetermined period fits within a designated display area.

9. In the information management system described in claim 1, An information management system that, in the personnel management document creation step, extracts keywords included in the first registration information from the registered information as document components, and creates a document component using text created based on a second registration information different from the first registration information.

10. In the information management system described in claim 1, The registration information includes information about the managed person before he / she joined the organization and information about the managed person after he / she joined the organization. An information management system in which the document components include information about the person being managed before he / she belonged to the organization.

11. In the information management system described in claim 1, The aforementioned processor is configured to perform the following steps: In the display control step, the personnel management document is displayed on the viewing terminal according to the viewer's status of fulfilling the conditions for viewing the personnel management document. The editing step involves an information management system that accepts editing requests for the aforementioned personnel management document, depending on whether the editor has met the conditions for editing the document.

12. In the information management system according to claim 11, In the aforementioned reception step, the input of the instruction to create the personnel management document is received from either the administrator's or the managed person's terminal. An information management system that, in the condition setting step, sets the viewing conditions or editing conditions for the personnel management document according to the person who inputs the creation instructions.

13. In the information management system described in claim 1, In the aforementioned personnel management document creation step, the accuracy of generating the personnel management document is calculated based on the amount of information in the registered information. The aforementioned generation accuracy is presented before the creation of the personnel management document, or is displayed on the viewing terminal together with the created personnel management document, in an information management system.

14. In the information management system described in claim 1, The registration information includes attribute information of the person being managed, An information management system that, in the step of creating a human resources management document, creates a human resources management document that includes tags relating to attribute information as document components.

15. In the information management system according to claim 14, The aforementioned tags are the same as the tags assigned to job seeker information registered in the job seeker database, in this information management system.

16. Information management method, An information management method comprising each step performed by the information management system described in any one of claims 1 to 15.

17. It is a program, A program that causes a computer to perform each step of the information management system described in any one of claims 1 to 15.

Images