Information processing systems, information processing methods, and programs

Abstract

To provide an information processing system that can appropriately update documents. [Solution] According to one aspect of the present invention, an information processing system is provided, comprising at least one processor, the processor configured to perform the following steps by reading a program: in the acquisition step, acquires a resume document for a person under management working in the organization and registration information for that person registered in a database within the organization; in the extraction step, extracts from the acquired registration information any items not described in the resume document as undescribed items; and in the presentation step, presents to the person under management and / or the manager who manages the person under management that there are undescribed items in the resume document.

Description

Technical Field

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

Background Art

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

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] By the way, documents related to human resources may sometimes require appropriate updating of the content described in the documents.

[0005] In view of the above circumstances, the present invention aims to provide an information processing system or the like that can appropriately update a document.

Means for Solving the Problems

[0006] According to one aspect of the present invention, there is provided an information processing system including at least one processor configured to execute the following steps by reading a program. In an acquisition step, a resume document about a management target person engaged in an organization and registration information about the management target person registered in a database within the organization are acquired. In an extraction step, matters not described in the resume document are extracted as un-described matters from the acquired registration information. In a presentation step, an information processing system is provided that presents to the management target person and / or an administrator who manages the management target person that there are un-described matters in the resume document.

[0007] According to this configuration, an information processing system, etc., is provided that can properly manage information concerning the persons to be managed. [Brief explanation of the drawing]

[0008] [Figure 1] This is a diagram showing the configuration of Information Processing 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 is an example of a resume document RD created by the creation unit 112. [Figure 7] This is an activity diagram illustrating the information processing of this embodiment. [Figure 8] This is an example of a screen displayed on the managed user terminal 30. [Figure 9] This is an example of a screen displayed on the managed user terminal 30. [Figure 10] This is an example of a screen displayed on the managed user terminal 30. [Figure 11] This is an example of a screen displayed on the managed user terminal 30. [Figure 12] This is an example of a screen displayed on the managed user terminal 30. [Figure 13] This is an activity diagram illustrating the information processing of this embodiment. [Figure 14] This is an example of the management screen displayed on the administrator terminal 20. [Modes for carrying out the invention]

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

[0010] In other words, the information processing system of this embodiment is as follows. An information processing system, Equipped with at least one processor, The aforementioned processor is configured to perform the following steps by reading a program: In the acquisition step, the organization acquires resume documents for the managed persons working within the organization, and registration information for the said managed persons registered in the organization's database. In the extraction step, items not included in the resume document are extracted from the acquired registration information as unlisted items. An information processing system that, in the presentation step, presents to the person being managed and / or the manager managing the person being managed that there are missing items in the resume document.

[0011] Incidentally, the program for implementing the software appearing in one embodiment may be provided as a non-transitory computer-readable medium, or it may be provided as a downloadable medium 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).

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

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

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

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

[0016] <Information Processing System 1> Figure 1 is a configuration diagram representing information processing system 1. Information processing system 1 comprises a communication line 2, a server device 10, multiple administrator terminals 20, and multiple managed user terminals 30. The server device 10, the administrator terminals 20, and the managed user terminals 30 are configured to communicate with each other via the communication line 2. The connection between the server device 10, the administrator terminals 20, and the managed user terminals 30 and the communication line 2 may be wired or wireless.

[0017] Information Processing System 1 constitutes part of a human resources system used by personnel subject to human resource management within an organization (multiple managed persons) and multiple managers within the organization who have a relationship with the managed persons. "Managers" include individuals in the reporting line of the managed persons (e.g., supervisors, line managers, etc.), human resources managers, etc. In Information Processing System 1, "managed persons" can also be the "managers" of other managed persons. Conversely, "managers" can also be "managed persons." Persons managed by Information Processing System 1 may include both managers and managed persons, and typically may be employees belonging to the organization.

[0018] Information processing system 1 assists in creating resume documents and other related information about the managed individuals. In one embodiment, information processing system 1 consists of one or more devices or components. These components will be described below.

[0019] <Server device 10> Figure 2 is a block diagram showing the hardware configuration of the server device 10. The server device 10 comprises 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 within the server device 10 via the communication bus 14.

[0020] <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 predetermined programs stored in the memory unit 12. That is, information processing by software stored in the memory unit 12 is concretely 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 a single unit, and may be implemented with multiple control units 11 for each function, or a combination thereof.

[0021] <Storage section 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.

[0022] <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.

[0023] 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.

[0024] <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.

[0025] <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.

[0026] <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.

[0027] <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.

[0028] 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 (the processor provided by the information processing system 1).

[0029] 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).

[0030] As shown in Figure 4A, the server device 10 (control unit 11) includes a reception unit 111, a creation unit 112, a publication unit 113, a display control unit 114, an acquisition unit 115, an extraction unit 116, a presentation unit 117, an addition unit 118, a tag extraction unit 119, a tag assignment unit 120, a tag presentation unit 121, and an artificial intelligence unit 122. As shown in Figure 4B, the administrator terminal 20 (control unit 21) includes a display unit 211 and an operation reception unit 212. As shown in Figure 4C, the managed user terminal 30 (control unit 31) includes a display unit 311 and an operation reception unit 312.

[0031] <Reception Desk 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 and requests based on operations from the administrator terminal 20 and the managed person terminal 30. In this embodiment, the reception unit 111 also receives registration information about managed persons working for the organization, which is registered in the organization's database. This reception of registration information is triggered by terminal operations of inputters within the organization. Here, "inputters within the organization" includes administrators and managed persons.

[0032] Those managed are, for example, employees or staff of the organization. The database within the organization may be accessible only to those affiliated with the organization and may not be 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.), and public corporations (e.g., local governments, etc.).

[0033] 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.

[0034] 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).

[0035] 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.

[0036] Furthermore, 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 evaluation database D102).

[0037] <Creation Section 112> The creation unit 112 creates various types of information based on the information received by the server device 10. In this embodiment, the creation unit 112 creates a resume document (or a part of a resume document) that includes document components derived from the registered information. The document components here include text created based on the registered information. The resume document will be made public to a predetermined range within the organization through the "publication" process described later. That is, the resume document can exist in both a draft status and a published status (public status).

[0038] Furthermore, even if a resume document has already been published for a particular person under management, the creation unit 112 may create a draft of a new resume document for the same person under management so that it coexists with the published resume document.

[0039] In a typical embodiment, the creation unit 112 inputs the registration information received by the reception unit 111 into an artificial intelligence module and outputs document components to create a resume document. Hereinafter, the "artificial intelligence module" is described as the artificial intelligence unit 122 of the server device 10, but it is not limited to this; the resume document may also be created by inputting predetermined registration information into an artificial intelligence module located outside the server device 10. Furthermore, the resume document can be created by means other than inputting the received registration information into the artificial intelligence module. In an exemplary embodiment, the creation unit 112 may create the resume document from the received registration information based on a predetermined rule base. Further specific processing related to the creation of the resume document will be described later.

[0040] <Public Section 113> The Public Section 113 makes the resume document public to a specified scope based on the receipt of a disclosure request from a designated person within the organization (changing the status of the resume document from draft to public). Here, this "resume document" may also be called the work history of a managed person, such as an employee or staff member, and is a document that contains information about the managed person, and is sometimes referred to as a "human resources management document." Furthermore, the resume document here is an internal resume (for example, a document that aggregates the registration 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 specified scope. The scope to which this resume document is made public (the specified scope) can be arbitrarily set according to the purpose for which the resume document is used. For example, one example of a configuration in which the resume document is made public to a specified scope is to allow only the department to which the manager belongs (human resources department) and human resources decision-makers (for example, management) to view the resume document, and to prevent others (including the managed person themselves) from viewing it. Separately, another example of a method for making resume documents accessible to a predetermined range is one in which administrators and managed individuals can view the resume documents. This predetermined range can, for example, be set by the administrator. Alternatively, the predetermined range may be set automatically according to employee information access rights, etc. In a typical example, the disclosure unit 113 publishes the resume document so that only those with access rights to the employee information contained in the published resume document can view the predetermined information. The disclosure unit 113 may also set viewing conditions for each item of the resume document. For example, for a specific item of the resume document, publication may be performed so that only those with access rights to the employee information related to that specific item can view it. In this case, items other than the specific item may be published to a range unrelated to the above access rights. Furthermore, the disclosure unit 113 may also set viewing conditions for each document component of the resume document.

[0041] Furthermore, the specified scope here is typically an extended scope of the scope to which disclosure requests can be accepted. Disclosure requests can typically be accepted from the managed person and / or their manager, but the disclosure unit 113 can control the disclosure of the resume document so that it is accessible to others as well as the managed person and / or their manager. Also, in a typical embodiment, the resume document is made available for viewing within the organization. That is, the resume document may not be made public outside the organization. By creating a resume document for each managed person, managers and others can easily search for personnel within the organization using keywords, conditions (parameters), etc. The resume document is referenced, for example, in strategic personnel transfers, internal job postings, utilization of inactive personnel, and support for career inventory.

[0042] <Display Control Unit 114> The display control unit 114 is configured to generate various display information and control the display content that is visible to the user. The display information may be the information itself that is generated in a manner visible to the user, such as a screen, image, icon, or text, or it may be rendering information for displaying a screen, image, icon, text, etc. on various terminals. In this embodiment, the display control unit 114 displays the status of the creation status of personnel management documents for multiple managed persons to the administrator in an overview manner. The specific processing related to this display control will be described later.

[0043] <Acquisition part 115> The acquisition unit 115 is configured to acquire resume documents for managed persons working in the organization, and registration information about managed persons registered in the organization's database. That is, the acquisition unit 115 acquires resume documents for managed persons stored in a predetermined storage area (for example, the storage unit 12 of the server device 10), and at the same time acquires registration information registered in the organization's database. The registration information here may be information registered in the personnel database D10 shown in Figure 5, etc.

[0044] <Extraction part 116> The extraction unit 116 is configured to extract items not included in the resume document from the acquired registration information as unrecorded items. Details of this extraction process will be explained later.

[0045] <Presentation part 117> The presentation unit 117 is configured to display to the person being managed and / or the administrator managing the person being managed that there are missing entries in the resume document. Details of this display will be explained later.

[0046] <Additional part 118> The addition unit 118 is configured to add predetermined information to the resume document. In a typical example, the addition unit 118 is configured to add extracted unrecorded information to the resume document based on terminal operations by the managed person or administrator. Also in a typical example, the addition unit 118 adds the created summary text to the resume document. These specific processes will be explained later.

[0047] <Tag extraction unit 119> The tag extraction unit 119 is configured to extract tags from a predetermined master that indicate skills or experience related to at least the unrecorded items added by the addition unit 118. Details of the processing performed by the tag extraction unit 119 and its related assignment unit 120 and tag presentation unit 121 will be explained later.

[0048] <Granting section 120> The assignment unit 120 is configured to assign skills or experience corresponding to the tags extracted by the tag extraction unit 119 to the resume document. In an exemplary embodiment, the assignment unit 120 is configured to assign skills or experience corresponding to the tags selected by the person being managed to the resume document. Such selectable tags may be presented by the functions of the tag presentation unit 121 as described below.

[0049] <Tag display section 121> The tag presentation unit 121 is configured to present the tags extracted by the tag extraction unit 119 in a manner that can be selected by the person being managed.

[0050] <Artificial Intelligence Department 122> The artificial intelligence unit 122 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.

[0051] The artificial intelligence unit 122 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.

[0052] 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 122 can apply the above algorithms as appropriate.

[0053] The artificial intelligence unit 122 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.

[0054] The artificial intelligence unit 122 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.

[0055] The learning model included in the artificial intelligence unit 122 can undergo additional training. For example, the artificial intelligence unit 122 learns whether the created resume document has been modified by the person who instructed its creation, etc. In other words, the artificial intelligence unit 122 performs additional training and fine-tunes the resume document created by the learning model using a training dataset in which the actual modification results of the resume document are labeled, as feedback to the resume document created by the learning model. This optimizes the resume document output from the learning model.

[0056] <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.

[0057] <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.

[0058] 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. Although the information processing method in this embodiment involves unrecorded information in the resume document, this section will first describe the typical resume document creation process, and then explain the details of the information processing involving unrecorded information.

[0059] 3.1 Details of the resume document creation process First, we will describe the details of the resume document creation process in this embodiment. The resume document of this embodiment typically consists of multiple document components that show information such as the work history and attributes of the managed person belonging to the organization. These document components may include, for example, 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 creation unit 112 obtains the first registration information RI1 or the second registration information RI2 from multiple databases included in the personnel database D10.

[0060] The creation unit 112 extracts keywords included in the first registration information RI1 from the registered information as the first document component DC1, and creates a document as the second document component DC2 based on the second registration information RI2, which is different from the first registration information RI1. In this embodiment, registration information for two or more categories relating to managed persons working in the organization may be accepted, and a resume document may be created based on this. The creation unit 112 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 registration information from different categories into appropriate forms as elements of a resume document and integrate them into a single document.

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

[0062] 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 creation unit 112. 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.

[0063] As shown in Figure 5, the creation unit 112 may generate multiple second document component 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.

[0064] 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 creation unit 112 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.

[0065] Furthermore, as the first reference information, a keyword extraction model may be used, which is a learned model that has been trained (machine learning or fine-tuned) to take the first registration information RI1 as input and output the first document element DC1. For example, the keyword extraction model is a learned model that has been trained using the first registration information RI1 and its corresponding first document element DC1 as training data. The creation unit 112 inputs the first registration information RI1 to the keyword extraction model of the artificial intelligence unit 122 and causes the keyword extraction model to output the first document element DC1. Alternatively, the keyword extraction model may be a generative AI that includes a large-scale language model. In this case, the creation unit 112 inputs an instruction to extract keywords from the first registration information RI1 and a prompt with the first registration information RI1 inserted into it to the keyword extraction model and causes the keyword extraction model to output the first document element DC1. Furthermore, the creation unit 112 may input to the keyword extraction model a prompt that 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, in addition to the keyword extraction instruction and the first registration information RI1.

[0066] The second document component DC2 includes a newly created document using keywords included in the registration information. The second document component DC2 is a summary of a document included in the second registration information RI2, a document reconstructed using keywords included in the second registration information RI2, or a document newly constructed using keywords included in the first registration information RI1. The second document component DC2 may also be a document that summarizes a document (created document) such as a work history (internal work history) created by the creation unit 112. The second document component DC2 is, for example, a document about work history created using the registration information, or a summary document of work history and registration information. In this specification, a document that summarizes work history (internal work history) may also be called a "career summary" or "job summary."

[0067] 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 creation unit 112 inputs the second registration information RI2 to the summarization model of the artificial intelligence unit 122 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 creation unit 112 inputs an instruction to summarize the text contained in the second registration information RI2 and a prompt inserting the second registration information RI2 to the summarization model and causes the summarization model to output the second document component DC2. Furthermore, the creation unit 112 may input a prompt to the summary creation model that, in addition to the summary creation instruction and the second registration information RI2, includes, for example, one or more samples of the second registration information RI2 and one or more samples of the corresponding second document component DC2.

[0068] The creation unit 112 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 creation unit 112 inputs the first registration information RI1 or the second registration information RI2 to the document creation model of the artificial intelligence unit 122 and causes the document creation model to output the second document component DC2. The document creation model may also be a generative AI that includes a large-scale language model. In this case, the creation unit 112 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 creation unit 112 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.

[0069] The creation unit 112 determines whether the acquired registration information is the first registration information RI1 or the second registration information RI2, and generates either 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 also use a learning model (i.e., a model that integrates a keyword extraction model and a summary generation model) configured to take 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.

[0070] The creation of the second document component DC2, which is a summary of the text created by the creation unit 112, is performed by referring to fourth reference information, which includes the correlation between the created text and the second document component DC2. As the fourth reference information, for example, a summarization model is used, which is a learning model that has been trained to take created text such as work history (internal work history) as input and output the second document component DC2. For example, the summarization model is a learning model that has been trained using created text and its corresponding second document component DC2 as training data. The creation unit 112 inputs the created text into the summarization model of the artificial intelligence unit 122, causing 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 creation unit 112 inputs instructions to summarize the text contained in the created text and prompts with the creation information inserted into them into the summarization model, causing the summarization model to output the second document component DC2. Furthermore, the creation unit 112 may input prompts to the summary creation model that, in addition to summary creation instructions and creation text, include, for example, one or more sample creation texts and one or more corresponding sample second document component DC2.

[0071] The creation unit 112 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 creation unit 112 may generate multiple document components from the registered information of a single category. For example, Figure 5 shows an example where the first document component DC1 of "Possessed Skills / Job Title," the second document component DC2 of "Internal Work Experience," and the second document component DC2 of "Job Summary" are generated from the registered information of "Goals / Evaluation." Also, Figure 5 shows an example where 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." Note that the "Job Summary" shown in Figure 5 may be a re-summarization of a document (internal work experience, etc.) created based on the registered information of "Goals / Evaluation."

[0072] An example of a resume document created as described above is shown in Figure 6. Figure 6 is an example of a resume document RD created by the creation unit 112. The resume document RD shown in Figure 6 contains basic information about the managed person (ABC D) in the organization, such as their name and place of work. In addition, various information about the managed person in the organization, based on their work experience in the organization, is described in separate items. The example shown in Figure 6 shows the managed person terminal 30 displaying the mode in which the managed person can view their own resume document RD (viewing mode). By pressing the button BT1 shown in Figure 6, it is possible to exit the viewing mode and update the resume document RD.

[0073] In the resume document RD shown in Figure 6, column C1 contains a "Career Summary," which is a summary of the managed person's career. Column C2 shows the managed person's previous job titles, column C3 shows their previous industries, and column C4 shows their skills and experience, all in tag format. Column C5 shows the managed person's internal career history (workplace history) for predetermined periods (e.g., half-yearly). Within column C5, skills and experience corresponding to the career history for each predetermined period (e.g., half-yearly) are shown in tag format.

[0074] The information entered in each field of the resume document RD may be output based on the functions of the creation unit 112. Alternatively, the information entered in each field of the resume document RD may be manually modified by the administrator or managed person after being output based on the functions of the creation unit 112. Furthermore, the information entered in each field of the resume document RD may be manually entered by the administrator or managed person, regardless of the functions of the creation unit 112. Also, tags such as those shown in fields C2 to C5 may be displayed by selecting them from tags pre-prepared by the server device 10 (tags stored in the tag master). Of course, the items shown in Figure 6 are illustrative examples, and various items useful for managing personnel within an organization may be shown in the resume document RD.

[0075] Note that the resume document RD shown in Figure 6 is shown in draft status. By clicking button BT2 in Figure 6, you can change the status of the resume document RD to make it publicly available to a specified group.

[0076] 3.2 Processing via managed user terminal 30 Next, we will explain how to handle missing information in the resume document RD. Note that missing information may be presented to the person being managed and / or the administrator; however, we will first explain how it is presented to the person being managed.

[0077] Figure 7 is an activity diagram illustrating the information processing of this embodiment. As shown in this activity diagram, in the information processing method of this embodiment, first the acquisition unit 115 of the server device 10 acquires a resume document RD for a managed person working in the organization and registration information about the managed person registered in the organization's database (Activity A101). In a typical embodiment, the acquisition unit 115 acquires the resume document RD for the managed person stored in a predetermined storage area (for example, the storage unit 12 of the server device 10), and at the same time acquires the registration information registered in the organization's database. The registration information here may be information registered in the personnel database D10 shown in Figure 5, etc. The order in which the resume document RD and the registration information are acquired may be set as appropriate. That is, the acquisition unit 115 may acquire one of the resume document RD and the registration information first and the other later. Alternatively, the acquisition unit 115 may acquire both the resume document RD and the registration information simultaneously.

[0078] Next, the extraction unit 116 of the server device 10 extracts items not included in the resume document RD from the acquired registration information as unrecorded items (Activity A102). That is, after comparing the contents of the registration information and the resume document RD, it extracts information that is included in the registration information but not in the resume document RD as unrecorded items. If there are any extracted unrecorded items, the presentation unit 117 of the server device 10 presents to the person being managed that there are unrecorded items in the resume document RD (Activities A103-A104).

[0079] The processing performed by the extraction unit 116 when extracting unrecorded information may be arbitrary. For example, unrecorded information can be extracted by extracting the differences between the text information contained in the registration information and the text information contained in the resume document RD. On the other hand, the extraction unit 116 of this embodiment may perform the extraction process based on time data as shown below.

[0080] In other words, the acquisition unit 115 may acquire first time data linked to a predetermined item included in the resume document RD and second time data linked to a predetermined item included in the registration information. In such a case, the extraction unit 116 may extract matters related to the predetermined item included in the registration information as unrecorded items, based on the fact that the second time data is newer than the first time data. That is, unrecorded items can be extracted by matching the time data associated with the resume document RD with the time data associated with the registration information registered in the database for the items from which unrecorded items are extracted. Note that the items that can be extracted in this extraction process may be any items related to time data. For example, typical examples of items related to time data include information on "qualifications" related to the acquisition period, information on "salary" related to the payment period, information on "surveys" related to the implementation period, and "interview results" related to the interview implementation period.

[0081] In addition to the examples described above, the extraction unit 116 can also extract any missing information for the following items. Specifically, the registration information acquired by the acquisition unit 115 may include, as predetermined items, at least one of the business objectives entered by the managed person and the business evaluations entered by the manager. In this case, the extraction unit 116 can extract any information not included in the resume document RD for at least one of the business objectives and business evaluations.

[0082] A specific example will be explained with reference to Figure 8. Figure 8 is an example of a screen displayed on the managed person's terminal 30. That is, when the extraction unit 116 extracts unrecorded information about a managed person, the screen of the managed person's terminal 30 may display a message as shown in column C10 of Figure 8. In the example shown in Figure 8, column C10 indicates that there is a discrepancy between the resume document RD's career history (internal career) for a predetermined period and the registered information recorded in the database. That is, as shown in Figure 8, the predetermined items included in the resume document RD may relate to the managed person's career history. In this case, the presentation unit 117 of the server device 10 can present to the managed person that there is unrecorded information for a predetermined period (second-period data) linked to the internal career history. That is, in the example in Figure 8, the registered information (business objectives and business evaluations) registered in the database is linked to the second-period data "First half of FY2024", and the internal career history in the resume document RD is linked to the first-period data "Second half of FY2023". In the example shown in Figure 8, the managed individual is shown that there are missing entries for "First Half of Fiscal Year 2024," which is the difference between the first and second time data. To explain based on a typical example, if the managed individual's internal career history is only recorded up to "Second Half of Fiscal Year 2023," but registration information regarding work objectives and performance evaluations for "First Half of Fiscal Year 2024" is registered in the database (i.e., the database is updated to include work objectives and performance evaluations for "First Half of Fiscal Year 2024"), the extraction unit 116 can extract the missing entries for "First Half of Fiscal Year 2024," which corresponds to the difference between the first and second time data. The presentation unit 117 can then present the extracted missing entries in relation to the second time data, "First Half of Fiscal Year 2024."In the example in Figure 8, it is shown that there are unrecorded entries for one period, "First Half of Fiscal Year 2024." However, if there are unrecorded entries for multiple periods (for example, if there are unrecorded entries for "Second Half of Fiscal Year 2023" and "First Half of Fiscal Year 2024"), the presentation unit 117 can display on the screen of the managed user terminal 30 that there are unrecorded entries for these multiple periods (in this case, the extraction unit 116 extracts that there are unrecorded entries for multiple periods). The manner in which the presence of unrecorded entries is displayed is not limited to that shown in Figure 8. For example, it is also possible to display to the managed user or administrator how many periods have unrecorded entries without specifically identifying the periods with unrecorded entries.

[0083] In the example shown in Figure 8, the first time data acquired by the acquisition unit 115 corresponds to the most recent period in the employee's career history. In the example shown in Figure 8, the employee's internal career history is only recorded in the resume document RD up to the second half of fiscal year 2023. However, if the registered information contained in the database includes information for the first half of fiscal year 2024 (information linked to the second time data), the extraction unit 116 can determine that the second time data is newer than the first time data, and therefore can extract the information for the first half of fiscal year 2024 that is linked to the second time data.

[0084] Furthermore, the specific time periods that serve as the basis for the first and second time period data can be set arbitrarily. For the aforementioned items related to career history (internal career history), the first and second time period data can also be arbitrarily set within the period related to that career history (internal career history). For example, in the example shown in Figure 8, the most recent career history listed in the resume document RD is "October 2023 to March 2024." In one embodiment, the last day of this career (March 31, 2024) can be used as the first time period data. Conversely, if the database contains registered information such as work objectives and performance evaluations for "April 2024 to September 2024," the last day of these work objectives and performance evaluations (September 30, 2024) can be used as the second time period data. In this way, by comparing the first and second time period data corresponding to the last day of the period, it is possible to extract any unrecorded information. Of course, the criteria for the first and second time period data for items spanning a predetermined period may be set by methods other than those described above. For example, the start time of a predetermined period may be used as the basis for the first hourly data and the second hourly data, or the time corresponding to the middle of the period may be used as the basis for the first hourly data and the second hourly data.

[0085] Furthermore, in extracting the unrecorded information regarding the careers of the managed persons as described above, the acquisition unit 115 and the extraction unit 116 only need to extract information regarding at least one of the business objectives and business evaluations. However, the registered information referred to as "business objectives" here may include evaluations of those objectives (i.e., one data point referenced by the extraction unit 116 may include both business objectives and evaluations of those business objectives).

[0086] The resume document RD acquired by the acquisition unit 115 is typically a resume document RD in a public status, but it may also be a resume document RD in draft status. In addition, although the example in Figure 8 shows a semi-annual record of internal career history, the period managed as internal career history is not limited to this. That is, internal career history can also be recorded in any period, such as quarterly, annually, or biennially.

[0087] The first hourly data may also be as follows: the first hourly data may correspond to the latest update of a predetermined item included in the resume document RD. The resume document RD shown in Figure 8 of this embodiment is configured to accept edits from the managed person when buttons BT1 and BT3 labeled "Edit" are pressed. In other words, the acquisition unit 115 can acquire the editing history (update history) for a predetermined item, and thereby can acquire the first hourly data associated with that predetermined item. For example, if the "Internal Career History" item in the resume document RD is updated by the managed person in April 2024, and new information regarding "Internal Career History" (work objectives and work evaluations) is registered in the database in October 2024, the acquisition unit 115 can acquire the first hourly data of "April 2024" and the second hourly data of "October 2024". The extraction unit 116 can then extract information registered in "October 2024," which is later than "April 2024," the date of the last update of the "Internal Career History" section of the resume document RD, as unrecorded information in the resume document RD. However, since the first time data corresponds to the last update of the specified items, even if the organization's database retrospectively updates items related to work objectives and work evaluations, the extraction unit 116 can still extract this updated information. In other words, as mentioned above, even if the "Internal Career History" section of the resume document RD is updated by the person being managed in April 2024, and new information regarding "Past Internal Career History (e.g., first half of fiscal year 2020)" (such as work objectives and performance evaluations) is registered in the database in October 2024, the acquisition unit 115 can acquire the first time period data, "April 2024," and the second time period data, "October 2024," and the extraction unit 116 can extract any unrecorded information regarding "First half of fiscal year 2020." Note that information regarding the last update may be stored for each item included in the resume document RD.

[0088] The presentation of unfilled information by the presentation unit 117 may be performed by any method. That is, as shown in Figure 8, it may be performed by presenting a field C10 at the beginning of the resume document RD indicating that there is unfilled information, or a predetermined field indicating that there is unfilled information may be presented in conjunction with the item containing the unfilled information (for example, near the item in question). In the example shown in Figure 8, pressing the button BT3 located in field C10 transitions to the item containing the unfilled information and switches to an editable mode. That is, pressing button BT3 transitions to the screen shown in Figure 9, and the corresponding item (the "Internal Career History" item) becomes editable. Figure 9 is an example of a screen displayed on the managed user terminal 30. In the example shown in Figure 9, field C51 indicates that "Goals and Evaluation Data for the First Half of Fiscal Year 2024," related to internal career history, exists as unfilled information.

[0089] When a managed user's terminal 30 screen indicates that there are missing entries, the managed user can add the missing entries to the resume document RD by performing a predetermined operation, thereby updating the resume document RD (Activities A105-A106). The updated resume document RD is then presented to the managed user's terminal 30 again (Activities A107-A108). In other words, the addition unit 118 of the server device 10 in this embodiment can add extracted missing entries to the resume document RD based on the managed user's terminal operation.

[0090] In a specific example, pressing button BT4, shown in Figure 9, allows you to add missing information to the resume document RD. Specifically, when button BT4, shown in Figure 9, is pressed, the missing information, based on the goals and evaluation data for the first half of fiscal year 2024, can be added to the resume document RD.

[0091] Furthermore, in performing such additions, the creation unit 112 of the server device 10 may create a predetermined document and add the created document to the resume document RD. That is, based on the example shown in Figure 9, the creation unit 112 of the server device 10 may create a career document concerning the managed person's career over a predetermined period based on the extracted unrecorded information, and the addition unit 118 may add the career document for the predetermined period to the resume document RD.

[0092] In other words, when button BT4 shown in Figure 9 is pressed, field C52 shown in Figure 10 is created and presented. Figure 10 is an example of a screen displayed on the managed person's terminal 30. Field C52 shown in Figure 10 contains the managed person's career history for a predetermined period (first half of fiscal year 2024), and the career history document created by the creation unit 112 is displayed as "Achievements / Work Content". In addition, the tag TG51 corresponding to the managed person's career history for the "first half of fiscal year 2024" is displayed in field C52. Here, this tag TG51 is automatically presented by functions such as the tag extraction unit 119 described later, but the managed person can also manually input the corresponding career history tag by pressing button BT6. In the example shown in Figure 10, button BT7 is displayed to prompt the user to update the summary (item "Career Summary") and skills (item "Skills / Experience") in conjunction with updating the internal career history.

[0093] The career history document shown in column C52 of Figure 10 may be created by any method, but in a typical example, it is created by the creation unit 112 inputting the unrecorded information into the artificial intelligence module and having it output the career history document. As explained earlier, "Internal Career History," which is an example of the second document component DC2, may be created based on the content of "Goals / Evaluation," which is an example of the second registration information RI2. That is, the creation unit 112 can create a new document as a career history document by combining multiple keywords contained in the document relating to the unrecorded information about "Goals / Evaluation." This creation of the career history document is performed by referring to fifth reference information, which includes the correlation between the unrecorded information and the career history document. As fifth reference information, for example, a document creation model is used, which is a learning model that has been trained to take the aforementioned unrecorded information as input and output a career history document. For example, the document creation model is a learning model that has been trained using the aforementioned unrecorded information and the corresponding career history document as training data. The creation unit 112 inputs the aforementioned unrecorded information into the document creation model of the artificial intelligence unit 122 and has the document creation model output a career history document. Furthermore, the document creation model may be a generative AI that includes a large-scale language model. In this case, the creation unit 112 inputs an instruction to create a resume document based on the unspecified information, and a prompt inserting the unspecified information, causing the document creation model to output the resume document. Alternatively, the creation unit 112 may input a document creation instruction and a prompt inserting, in addition to the unspecified information, for example, one or more samples of unspecified information and corresponding sample resume documents. By inserting the resume document created in this manner into column C52, the resume document RD can be added.

[0094] Furthermore, the following processing may be performed with respect to tags such as TG51 shown in Figure 10. Specifically, the tag extraction unit 119 of the server device 10 may extract tags from a predetermined master that indicate skills or experience related to at least the unrecorded items added by the addition unit 118. In addition, the assignment unit 120 of the server device 10 may assign the skills or experience corresponding to the tags extracted by the tag extraction unit 119 to the resume document RD.

[0095] In other words, in this embodiment, the tag extraction unit 119 can extract a predetermined tag based on the unrecorded information to be added. The extraction process here may be achieved by any method, but typically, the tag extraction unit 119 extracts tags by inputting at least the unrecorded information added by the addition unit 118 and a predetermined master into the artificial intelligence module. That is, the server device 10 can prepare a plurality of keywords related to various skills or experiences in a predetermined memory area (typically the memory unit 12) and store these as a predetermined master. In this state, the tag extraction unit 119 inputs the unrecorded information added by the addition unit 118 (typically information related to business objectives and business evaluations) and the predetermined master into the artificial intelligence module (artificial intelligence unit 122), and instructs the artificial intelligence module (artificial intelligence unit 122) to extract keywords that are highly relevant to the skills and experiences expected from the unrecorded information added by the addition unit 118. Although not necessarily limited to this, such an extraction process may be carried out as follows. First, the tag extraction unit 119 instructs the artificial intelligence module (artificial intelligence unit 122) to convert the unrecorded text to be added into vector data. Meanwhile, the tag extraction unit 119 also instructs the artificial intelligence module (artificial intelligence unit 122) to similarly convert the keywords for job titles present in a predetermined master into vector data. Then, the tag extraction unit 119 instructs the artificial intelligence module (artificial intelligence unit 122) to extract keywords from the predetermined master that have a high correlation with the added unrecorded text, based on the proximity of the two sets of vector data. The proximity of the two sets of vector data can be evaluated using various methods, but typically it is evaluated by the angle between the two vectors (cosine similarity), etc. Furthermore, the correlation here may be scored, and the keywords may be displayed in column C52 in descending order of their scores.

[0096] The tags extracted by the tag extraction unit 119 are then assigned to the resume document RD, as shown by the tag TG51. In this way, the resume document RD of the managed person is assigned tags indicating skills and experience, such as "market share expansion" and "customer satisfaction improvement," linked to the corresponding internal company history.

[0097] Furthermore, the tags extracted by the tag extraction unit 119 may be presented in a manner that allows the managed user to select them, based on the function of the tag presentation unit 121 of the server device 10. That is, tags that can be assigned to the resume document RD by the managed user's selection, such as the tag TG52 shown in Figure 10, may be presented on the screen of the managed user's terminal 30. In other words, the tag TG52 shown in Figure 10 switches to the same display as tag TG51 when selected by the managed user, and even if the resume document RD is updated without any selection by the managed user, the items of tag TG52 will not be reflected in the content of the resume document RD. In addition, by pressing button BT6, it is also possible to present the tags present in a list format to the managed user in a predetermined master. The managed user who sees such a list of tags can arbitrarily set the tags to be assigned to the resume document RD by selecting the tags that they believe match their own career history.

[0098] While the above describes how to create a resume document from unfilled information, if the unfilled information does not require the creation of a separate document, the extracted unfilled information may be added to the resume document RD without going through the document creation process. Typical examples include information on qualifications and attendance, which may be managed only by keywords or numerical values ​​(scores). In such cases, unfilled information can be added to the resume document RD without any special document creation.

[0099] When button BT7, shown in the example in Figure 10, is pressed, the screen transitions to the one shown in Figure 11. Figure 11 is an example of a screen displayed on the managed user terminal 30. This Figure 11 shows the mode in which the managed user modifies their own resume document RD. On the screen shown in Figure 11, pressing button BT8 allows the user to regenerate (update) the "Career Summary" item of the resume document RD. Pressing button BT9 allows the user to automatically add (update) tags to the "Skills and Experience" item of the resume document RD. Pressing button BT10 allows the user to manually add tags to the "Skills and Experience" item of the resume document RD. When button BT11 in Figure 11 is pressed, the user exits the resume document RD editing mode and transitions to the mode for viewing their own resume document RD, as shown in Figure 6. After transitioning to the mode for viewing the resume document RD in this manner, pressing the button BT2, which is labeled "Publish," allows the managed user to request publication of the resume document RD, and the resume document RD will be made public to the specified scope (Activities A109~A111).

[0100] In relation to Figure 11, the process of regenerating (updating) the "Career Summary" item will be explained. In regenerating the "Career Summary" item, the creation unit 112 of the server device 10 creates a summary document that summarizes the managed person's career history based on at least the unrecorded information added by the addition unit 118. The addition unit 118 then adds the created summary document to the resume document RD. This summary document may be created by various methods, but in a typical embodiment, the creation unit 112 creates the summary document by inputting information based on at least the unrecorded information added by the addition unit 118 into the artificial intelligence module. To show a specific embodiment, the creation unit 112 can create a document (summary document) to be inserted into the "Career Summary" item based on information related to the managed person's career history. The "information related to past career history" here includes at least the information based on the unrecorded information added by the addition unit 118, and may optionally include information recorded in the resume document RD at the time the summary document is created, the first registration information RI1 or the second registration information RI2 registered in the database, etc. For example, a summary document may be created by inputting the entire career history document, including the career history document created based on unspecified items added to the second registration information RI2 such as goals or evaluations, into the artificial intelligence module as information based on unspecified items. From the viewpoint of creating a document that provides an overview of the managed person's career history, it is preferable that "information on past career history" includes, in addition to the information based on unspecified items added by the addition unit 118, information contained in the resume document RD at the time of creating the summary document, and one or more pieces of information selected from the first registration information RI1 and the second registration information RI2. Furthermore, from the viewpoint of efficiently creating the document, it is preferable that "information on past career history" includes both the information based on unspecified items added by the addition unit 118 and the information contained in the resume document RD at the time of creating the summary document. The information based on unspecified items included in "information on past career history" may be keywords or numerical values ​​(scores) added to the resume document RD as unspecified items, or it may be text added to the resume document RD that the creation unit 112 created based on the unspecified items (typically, the aforementioned "career history document," etc.).In other words, the creation unit 112 can create a summary document using keywords, numerical values ​​(scores), sentences, etc., added to the resume document RD as constituent elements. Furthermore, "information on past experience" may typically include information about the "experience" section described in the resume document RD. This allows the creation unit 112 to efficiently create a summary document. As a more specific example, "information on past experience" may include both the information (sentences) about the managed person's past experience described in the resume document RD and the information (experience sentences) about experience newly added based on undescribed information. Note that the information included in "information on past experience" is not necessarily limited to information about the "experience" section, but may also include information about various items (job title, position, skills, qualifications, etc.) that may be described in the resume document RD.

[0101] The creation of this summary text is typically performed by referring to sixth reference information, which includes the correlation between "information about past career history" and the summary text. As the sixth reference information, for example, a text generation model is used, which is a learning model that has been trained to take "information about past career history" as input and output a summary text. For example, the text generation model is a learning model that has been trained using "information about past career history" and its corresponding summary text as training data. The creation unit 112 inputs "information about past career history" into the text generation model of the artificial intelligence unit 122, causing the text generation model to output a summary text. Alternatively, the text generation model may be a generative AI that includes a large-scale language model. In this case, the creation unit 112 inputs an instruction to create a new text based on "information about past career history" and a prompt inserting "information about past career history" into the text generation model, causing the text generation model to output a summary text. Alternatively, the creation unit 112 may input a prompt to the text generation model that, in addition to the text creation instruction and "information about past career history," inserts, for example, one or more samples of "information about past career history" and one or more corresponding sample summary texts. This makes it possible to include information related to previously unrecorded details when documenting the career history of the person being managed.

[0102] Furthermore, the example shown in Figure 11 illustrates how the tag presentation unit 121 presents the tags extracted by the tag extraction unit 119 in a manner that can be selected by the person being managed.

[0103] In other words, the various tags shown in column C4 can be extracted based on the functions of the tag extraction unit 119. For example, the tag extraction unit 119 may extract tags from a predetermined master that indicate skills or experience related to at least the unrecorded information added by the addition unit 118. That is, in column C4 of the resume document RD, tags related to skills or experience (or candidate tags that the managed person can select) extracted based on the functions of the tag extraction unit 119 may be presented. In the screen showing the resume document RD in Figure 11, the tags extracted by the tag extraction unit 119 are presented in a manner that allows the managed person to select them, based on the functions of the tag presentation unit 121. In a typical embodiment, the tag extraction unit 119 extracts tags by inputting at least the unrecorded information added by the addition unit 118 and a predetermined master into the artificial intelligence module. To explain the process in more detail, the tag extraction unit 119 inputs the unrecorded information added by the addition unit 118 and the predetermined master data mentioned above into the artificial intelligence module (artificial intelligence unit 122), and instructs the artificial intelligence module (artificial intelligence unit 122) to extract keywords that are highly relevant to the expected skills and experience from the unrecorded information. The unrecorded information input into the artificial intelligence module here may include not only the information about the unrecorded information itself, but also the career history document created by the creation unit 112 (a career history document created based on the unrecorded information). Furthermore, although not necessarily limited to this, such extraction processing may be carried out as follows. First, the tag extraction unit 119 instructs the artificial intelligence module (artificial intelligence unit 122) to convert the added unrecorded information into vector data. At the same time, the tag extraction unit 119 instructs the artificial intelligence module (artificial intelligence unit 122) to similarly convert the keywords for job titles that exist in the predetermined master data into vector data. The tag extraction unit 119 then instructs the artificial intelligence module (artificial intelligence unit 122) to extract keywords from a predetermined master that have a high correlation with the added unrecorded information, based on the proximity of the two sets of vector data. The proximity of the two sets of vector data can be evaluated using various methods, but is typically evaluated by the angle between the two vectors (cosine similarity). The correlation here may also be scored.Furthermore, column C4 may display the keywords in descending order of their scores.

[0104] Furthermore, regarding the tags extracted by the tag extraction unit 119, they may be presented in a manner that allows the managed user to select them, based on the function of the tag presentation unit 121 of the server device 10, as explained in section C52. In other words, the various tags shown in Figure 11 can be assigned to the resume document RD by the managed user's selection. That is, the assignment unit 120 of the server device 10 will assign the skills or experience corresponding to the tags selected by the managed user to the resume document RD. To explain in more detail, the tags TG42 and TG43 shown in Figure 11 will switch to the same display as tag TG41 based on their selection by the managed user, and even if the resume document RD is updated without any selection by the managed user, the items of tags TG42 and TG43 will not be reflected in the content of the resume document RD. In the screen shown in Figure 11, the managed user can efficiently select tags by pressing button BT9. Specifically, when a user accessing the screen shown in Figure 11 presses button BT9, they can select all the tags TG51 added to field C52 (i.e., tags extracted by the tag extraction unit 119 and assigned by the assignment unit 120 based on unentered information) and reflect them as content to be registered in field C4. In addition, by pressing button BT10, the user can be presented with a list of tags existing in a predetermined master. When a user accesses such a list of tags, they can select the tags they believe match their own career history, thereby arbitrarily setting the tags to be assigned to field C4 of the resume document RD.

[0105] Figure 12 shows the resume document RD after the prescribed updates have been made. Figure 12 is an example of a screen displayed on the managed user's terminal 30. In column C1 of the screen shown in Figure 12, text related to "First half of fiscal year 2024" corresponding to the unfilled information has been inserted. Also, column C4 in Figure 12 shows how the prescribed tags have been reflected in the managed user's resume document RD. Note that Figure 12 shows an example where the managed user has entered the tag TG42 in C4, but has not entered the tag TG43 in column C4. By performing the above process, the managed user's resume document RD will be effectively updated.

[0106] 3.3 Processing via the administrator terminal Next, we will explain how unrecorded information is presented to the administrator. Figure 13 is an activity diagram illustrating the information processing in this embodiment. As shown in this activity diagram, in the information processing method of this embodiment, the administrator requests the display of the management screen from their terminal, and the display control unit 114 of the server device 10 displays the requested management screen on the administrator terminal 20 (activities A201 to A204). In other words, in this embodiment, the display control unit 114 displays the creation status of resume documents RD for multiple managed persons to the administrator via the screen.

[0107] Figure 14 shows an example of an administration screen displayed on the administrator terminal 20. Specifically, the administration screen shown in Figure 14 displays a list of managed persons who are the target of creating resume documents RD. In the administration screen in Figure 14, each managed person is associated with the name NM, the attribute AT, the status STT regarding the creation status of the resume document, the editing history EH of the resume document, the last update date UD of the resume document, the update difference UDF of the resume document, and the details DT of the resume document.

[0108] The attributes AT of the managed person may include attributes such as primary duties, concurrent duties, grade, job type, position, and work location for each managed person. Of course, the attributes of managed persons displayed on the administrator terminal are not limited to these and may include various items such as gender, age, and date of joining the company. Furthermore, in the management screen of Figure 14, managed persons can be sorted and displayed according to the above-mentioned status STT, attributes AT, resume document editing history EH, resume document last update date UD, and resume document update difference UDF. This allows administrators to efficiently narrow down the persons to be managed.

[0109] The status STT regarding the creation status of resume documents may include, for example, the status of each managed person not having created a resume document RD (not created), the status of each managed person having created a draft of a resume document RD but not having published it (draft), and the status of each managed person having already published a resume document RD (published). Of course, the types of these statuses and the way they are displayed on the management screen can be different from those shown in Figure 14.

[0110] Furthermore, the resume document editing history EH indicates whether the managed user has made edits to the resume document RD. Specifically, for resume document RDs that are in draft or published status, the editing history EH of this resume document shows whether the managed user has made modifications to the content created by the creation unit 112 of the server device 10. As will be described later, the administrator can perform update processing on the managed user's resume document RD, and when the administrator selects a managed user to perform the update, they can refer to the editing history of such resume document RDs.

[0111] In the example management screen in Figure 14, the last update date UD for the resume document shows when each managed person updated their resume document RD. Also, in the example management screen in Figure 14, the update difference UDF for the resume document shows items for each managed person that are not recorded in the database regarding business objectives and business evaluations. In other words, in this embodiment, the display unit 117 of the server device 10 displays on the screen (management screen) that there are unrecorded items for a given managed person, associating them with that managed person. Note that the example shown in Figure 14 shows how many periods (periods) are related to the unrecorded items. On the other hand, in the information processing method of this embodiment, information about which period (e.g., "first half of fiscal year 2024") has unrecorded items may also be displayed on the management screen.

[0112] The detailed DT for resume documents indicates whether the administrator can view the resume document RD. In the example of the management screen in Figure 14, documents with a status of "Draft" or "Published" are viewable, and the button labeled "Details" is displayed differently from other managed documents that are in the "Not Created" status. In this configuration, an administrator viewing the management screen in Figure 14 can view the corresponding resume document RD by clicking the "Details" button.

[0113] Furthermore, in the management screen shown in Figure 14, checkboxes CB associated with each managed user are displayed. When an administrator processes a resume document RD, they can select the managed users to be processed using these checkboxes CB. In this way, by selecting the managed users to be processed and pressing button BT12, batch processing of resume documents RD can be performed. Button BT12 is configured so that the content of the processing can be set as appropriate. Specifically, it is possible to publish the resume documents RD for each of the specified managed users in bulk, or to make the resume documents RD for each of the specified managed users private in bulk. In addition, based on the operation of button BT12, it is also possible to delete the resume documents RD for each of the specified managed users in bulk. Below, as shown in Figure 14, the method of updating the resume documents RD for each of the specified managed users in bulk will be described. Note that "batch processing" here refers to executing processing on multiple resume documents RD with a single instruction. In other words, "batch processing" is not limited to processing multiple resume documents RD simultaneously, but also includes a mode in which processing of the target multiple resume documents RD is performed sequentially.

[0114] In other words, in this embodiment, based on the administrator's terminal operation shown in Figure 14, a request can be made to add missing information for each managed person, and this request can update the resume document RD for each managed person (Activities A205~A206). That is, the addition unit 118 of the server device 10 can add the missing information extracted for each of the multiple managed people to the resume document RD all at once, based on the administrator's terminal operation. The addition process here may be performed by automatically executing the processes for Activities A105~A106 for each managed person. That is, for managed people who have missing information about their career history for a predetermined period, a process may be performed to automatically insert that career history into the resume document RD. After such an update process is performed, the display control unit 114 of the server device 10 displays the update status again on the administrator terminal 20 (Activities A207~A208).

[0115] Furthermore, in this embodiment, an organization may impose a limit on the number of times it can perform batch processing (such as batch updating of resume documents RD) within a predetermined period. This makes it easier to achieve information management while optimizing the cost of information processing. The number of times this limit is imposed can be set arbitrarily, but one example is to set it at predetermined intervals (for example, annually, quarterly, etc.) depending on the size of the organization.

[0116] Furthermore, when adding (updating) such unrecorded information, the addition unit 118 may set the resume document RD to draft status. That is, it may be desirable to request confirmation from the managed person regarding the automatically added information. From this perspective, the resume document RD to which the predetermined information has been added may not be immediately published, but may be set to draft status. Furthermore, with respect to a resume document RD in such draft status, the publication unit 113 may change the resume document RD from draft status to published status, which is made public to a predetermined range, based on a publication request from the managed person or administrator. That is, after the addition unit 118 adds the unrecorded information to the resume document RD, the administrator can change the managed person's resume document RD to published status by performing an operation on the administrator terminal 20 (Activity A209~A211). This operation is performed, for example, by pressing the button BT12 shown in Figure 14. In other words, by specifying the managed users to whom the resume document RD should be made public using the checkbox CB, and then pressing button BT12, the status of the resume document RD for the specified managed users can be changed to public. Note that when performing this publication process, button BT12 changes its mode to enable the bulk publication of resume documents. On the other hand, resume document RDs to which the administrator has added missing information may also be made public through the managed user's terminal operation. That is, each managed user can make their resume document RD public to a predetermined range by pressing button BT2 as shown in Figure 6. Through these processes, the resume document RD for each managed user will be effectively updated.

[0117] 4. Effect The operation of this embodiment can be summarized as follows: In this information processing method, the extraction unit 116 presents the extracted unrecorded information to the person being managed and / or the administrator, thereby appropriately prompting the updating of the resume document RD. Therefore, proper management of the resume document RD can be performed.

[0118] 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.

[0119] 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.

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

[0121] In the above embodiment, Figure 14 shows a management screen where the administrator is presented with the last updated date UD for the resume document and the update difference UDF for the resume document, and the administrator updates the resume document RD. Alternatively, a reminder (notification) may be sent to each managed person prompting them to update the resume document RD based on whether the last updated date UD for the resume document and the update difference UDF for the resume document meet predetermined requirements. This encourages managed people to voluntarily update the resume document RD, and allows the resume document RD to be updated without necessarily requiring administrator processing.

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

[0123] (1) An information processing system comprising at least one processor, wherein the processor is configured to perform the following steps by reading a program, the acquisition step of acquiring a resume document of a person under management working for the organization and registration information of the person under management registered in a database within the organization; the extraction step of extracting from the acquired registration information any items not described in the resume document as undescribed items; and the presentation step of presenting to the person under management and / or the manager who manages the person under management that there are undescribed items in the resume document.

[0124] (2) An information processing system as described in (1) above, wherein the acquisition step acquires first time data linked to a predetermined item included in the resume document and second time data linked to a predetermined item included in the registration information, and the extraction step extracts matters relating to the predetermined item included in the registration information as the unrecorded items, based on the fact that the second time data is newer than the first time data.

[0125] (3) An information processing system as described in (2) above, wherein the registered information includes, as predetermined items, at least one of the business objectives entered by the person being managed and the business evaluations entered by the manager, and in the extraction step, extracts items not described in the resume document for at least one of the business objectives and the business evaluations.

[0126] (4) An information processing system as described in (2) or (3) above, wherein in the presentation step, the information processing system presents to the person being managed and / or the administrator that there are unrecorded items regarding the second time data.

[0127] (5) An information processing system according to any one of (2) to (4) above, wherein the predetermined items included in the resume document relate to the career of the person being managed, and the first time data corresponds to the most recent period in the career.

[0128] (6) An information processing system according to any one of (2) to (4) above, wherein the first time data corresponds to the latest update of the predetermined item included in the resume document.

[0129] (7) An information processing system according to any one of (1) to (6) above, wherein in the first addition step, the extracted unrecorded items are added to the resume document based on the terminal operation of the person being managed or the administrator.

[0130] (8) An information processing system as described in (7) above, wherein in the first creation step, a career document relating to the career of the person to be managed over a predetermined period is created based on the extracted unrecorded information, and in the first addition step, the career document relating to the career over the predetermined period is added to the resume document.

[0131] (9) An information processing system as described in (8) above, wherein the first creation step is performed by inputting the missing information into an artificial intelligence module and outputting the career history document.

[0132] (10) An information processing system according to any one of (7) to (9) above, wherein in the tag extraction step, tags indicating skills or experience related to the undescribed items added in the first addition step are extracted from a predetermined master; in the tag presentation step, the tags extracted in the tag extraction step are presented in a manner that allows the managed person to select them; and in the assignment step, the skills or experience corresponding to the tags selected by the managed person are assigned to the resume document.

[0133] (11) An information processing system as described in (10) above, wherein in the tag extraction step, the tag is extracted by inputting at least the unrecorded information added in the first addition step and the predetermined master into an artificial intelligence module.

[0134] (12) An information processing system according to any one of (7) to (11) above, wherein in the second creation step, a summary document summarizing the career history of the person to be managed is created based on at least the unrecorded information added in the first addition step, and in the second addition step, the created summary document is added to the resume document.

[0135] (13) An information processing system as described in (12) above, wherein in the second creation step, information based on the undescribed items added in at least the first addition step is input to an artificial intelligence module to create the summary document.

[0136] (14) An information processing system according to any one of (1) to (13) above, wherein in the display control step, the status of resume document creation by multiple persons under management is displayed to the administrator via a screen, and in the presentation step, the screen is displayed that there are missing entries for a predetermined person under management, in association with that predetermined person under management.

[0137] (15) An information processing system as described in (14) above, wherein in the first addition step, the system adds the missing information extracted for each of the multiple persons under management to the resume document in a single step based on the terminal operation of the administrator.

[0138] (16) An information processing system as described in (15) above, wherein in the first addition step, the resume document to which the unrecorded information has been added is set to draft status, and in the publication step, based on a publication request from the person under management or the administrator, the resume document is changed from draft status to published status to be made public to a predetermined range.

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

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

[0141] 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]

[0142] 1: Information Processing 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 terminals 31: Control Unit 32: Storage section 33: Communications Department 34: Input section 35: Output section 36: Communications bus 111: Reception Department 112: Creation Department 113: Public Section 114: Display Control Unit 115: Acquisition Department 116:Extraction part 117:Presentation part 118: Addition part 119: Tag extraction unit 120: Assignment section 121: Tag display section 122: Artificial Intelligence Department 211:Display section 212: Operation Reception Section 311: Display section 312: Operation Reception Section AT: Attribute BT1~BT12: Buttons C1~C5, C10, C51, C52: Column CB: Checkbox D10: Human Resources Database D101: Basic Information Database D102: Target Evaluation Database D103: Position Database D104: Skill Database D105: Recruitment Database D106: Condition Survey Database D107: Tissue Diagnostic Survey Database D108: Original Survey Database D109: Interview Database D110: Attendance Database DC1: First Document Component DC2: Second Document Component DT:Details EH: Edit history of resume document NM: Name RD: Resume document RI1: First Registration Information RI2: Second Registration Information STT: Status TG41~TG43, TG51, TG52: Tags UD: Last updated date of the resume document UDF: Resume document update differences

Claims

1. An information processing system, Equipped with at least one processor, The aforementioned processor is configured to perform the following steps by reading a program: In the acquisition step, the organization acquires resume documents for the managed persons working within the organization, and registration information for the managed persons registered in the organization's database. In the extraction step, items not included in the resume document are extracted from the acquired registration information as unlisted items. An information processing system that, in the presentation step, presents to the person being managed and / or the manager managing the person being managed that there are missing items in the resume document.

2. In the information processing system described in claim 1, The acquisition step acquires first time data linked to a predetermined item included in the resume document and second time data linked to a predetermined item included in the registration information. An information processing system that, in the extraction step, extracts matters relating to the predetermined items included in the registration information as the unrecorded items, based on the fact that the second time data is newer than the first time data.

3. In the information processing system described in claim 2, The registration information includes, as a predetermined item, at least one of the business objectives entered by the person being managed and the business evaluation entered by the manager. An information processing system that, in the extraction step, extracts items not described in the resume document for at least one of the business objectives and the business evaluation.

4. In the information processing system described in claim 2, An information processing system that, in the presentation step, presents to the person being managed and / or the administrator that there are missing entries regarding the second time data.

5. In the information processing system described in claim 2, The predetermined items included in the resume document relate to the career of the person being managed, The first time data corresponds to the most recent period in the career history, and is an information processing system.

6. In the information processing system described in claim 2, The first time data corresponds to the latest update of the predetermined items included in the resume document in the information processing system.

7. In the information processing system described in claim 1, An information processing system that, in the first addition step, adds the extracted missing information to the resume document based on the terminal operation of the person being managed or the administrator.

8. In the information processing system described in claim 7, In the first creation step, a career history document concerning the career of the person being managed over a specified period is created based on the extracted missing information. An information processing system that, in the first addition step, adds the career history document for the predetermined period to the resume document.

9. In the information processing system described in claim 8, The first creation step is performed by inputting the missing information into an artificial intelligence module and outputting the career history document, and is an information processing system.

10. In the information processing system described in claim 7, In the tag extraction step, tags indicating skills or experience related to the undescribed items added in at least the first addition step are extracted from a predetermined master. In the tag presentation step, the tags extracted in the tag extraction step are presented in a manner that allows the managed person to select them. An information processing system that, in the assignment step, assigns the skills or experience corresponding to the tags selected by the person being managed to the resume document.

11. In the information processing system according to claim 10, An information processing system that extracts tags in the tag extraction step by inputting the unrecorded information added in at least the first addition step and the predetermined master into an artificial intelligence module.

12. In the information processing system described in claim 7, In the second creation step, a summary document summarizing the past career of the person being managed is created based on at least the previously unrecorded information added in the first addition step. The second addition step involves an information processing system that adds the created summary text to the resume document.

13. In the information processing system according to claim 12, An information processing system that, in the second creation step, creates the summary text by inputting information based on the unrecorded items added in at least the first addition step into an artificial intelligence module.

14. In the information processing system described in claim 1, In the display control step, the status of resume document creation by multiple managed persons is displayed to the administrator via the screen. An information processing system that, in the presentation step, presents on the screen that there are missing entries regarding a predetermined person to be managed, in association with that predetermined person to be managed.

15. In the information processing system described in claim 14, In the first addition step, an information processing system adds the previously unrecorded information extracted for each of the multiple managed persons to the resume document in a single step, based on the administrator's terminal operation.

16. In the information processing system described in claim 15, In the first addition step, the resume document to which the missing information has been added is set to draft status, In the publishing step, an information processing system changes the status of the resume document from draft to published, based on a publishing request from the person under management or the administrator.

17. Information processing method, An information processing method comprising each step performed by the information processing system according to any one of claims 1 to 16.

18. It is a program, A program for causing a computer to perform each step of the information processing system described in any one of claims 1 to 16.

Images