JP4709612B2 - Method, program and computer for assigning personnel to tasks comprising a project - Google Patents

Description

  The present invention relates to a system and method for assigning personnel to projects such as research, development, and manufacturing, and more particularly, to a system and method that enables personnel assignment dynamically even if personnel data changes after assignment.

  In the field of project management, several techniques have been proposed as a method for assigning the optimal personnel to a project. Examples thereof include “human resource supply optimization method” described in Patent Document 1 and “resource management server, human resource management method, and human resource management system” described in Patent Document 2.

  Patent Document 1 discloses a system and a method that allow a person having a required skill to be selected not only from a specific business division but also from the entire company organization and assigned to a target project. In this system, data on personnel that can be assigned to a project (personnel data) is registered in advance as personnel files, skill files, and project management capability files. In the first embodiment, a method for searching and extracting necessary personnel in response to a personnel search request is disclosed. In the second embodiment, a method of searching for the presence or absence of a project that matches a specific person by collating the data of the registered person with the content of the search request is disclosed. In any case, on the premise that the personnel data is fixed and registered in advance, the matching operation between the project and the personnel is executed in response to the identification of the project requirements.

  Patent Document 2 discloses a resource management system that can effectively utilize the capabilities of individual personnel by linking information related to personnel (HR database) and information related to skills (knowledge database) with a project management tool. A method is disclosed. Also in this system, personnel data (including personnel information and skill information) that can be assigned to a project is stored in the database in advance, and when the requirements of the entered project are entered, appropriate personnel search is executed. Is done. Then, when the user who has requested the search selects a candidate listed in the search result, the assignment of personnel to the project is confirmed.

JP 2003-44642 A JP 2004-118648 A

  These conventional personnel assignment systems respond to the project requirements (eg, required task type, skills required for each task, duration, etc.) entered by the project manager (project manager). Then, the personnel data registered in advance is retrieved, and personnel having skills that satisfy the retrieval conditions are automatically assigned. Personnel data is stored locally in advance by a personnel assignment system or periodically replicated as a replica from another system. However, in such a system, once a person is assigned to a project, a mechanism for dynamically reviewing the assignment is not sufficiently considered. For example, when the personnel actually assigned to the project suddenly take a leave of absence, the conventional technology cannot flexibly cope with this.

  If the project requirements themselves are changed, the allocation personnel can be reconfigured by executing the allocation process again. However, if a change in personnel status occurs after the assignment process (eg, retirement of assigned personnel, leave of absence, skill change, etc.), the project manager usually cannot automatically recognize the fact. Even if the project manager notices a change in personnel data, he or she finds the project (or individual task) to which the personnel are assigned and assigns personnel to the project (or individual task) that needs to be changed. The allocation must be requested again. As a result, the burden on the project manager is increased and can affect the progress of the project.

  In order to avoid such problems, it is possible to make the personnel data static so that it cannot be changed. However, from the standpoint of the person who manages personnel data (resource manager), such a system is flexible. It is not realistic. From the standpoint of a project manager, it is extremely inconvenient because it cannot manage projects based on the latest personnel data.

  Therefore, while the personnel management system that manages personnel data and the project management system that manages project management data operate independently, the latest data of these systems is fully utilized, and from the project management side, the personnel management system From the management side, it is desirable to have a personnel assignment mechanism that can respond flexibly and dynamically.

An object of the present invention is to provide a mechanism capable of dynamically allocating personnel again in response to changes in personnel data even if the personnel situation changes after the personnel are allocated to the project. Is to provide.
Another object of the present invention is to reduce the processing load of project management and personnel management required by such change of personnel data.
Yet another object of the present invention is to allow a project manager or resource manager to quickly recognize even when personnel data changes occur, resulting in timely and efficient project management. is there.
Another object of the present invention is to provide a system capable of flexibly assigning personnel to a project while synchronizing with both the project management system and the personnel management system.

  According to the personnel assignment method of the present invention, a first system (project management system) for managing data (task data) relating to a plurality of tasks constituting a project, and data relating to personnel (personnel data) including identification data are managed. Implemented in a computer (personnel assignment system) connected to a second system (personnel management system).

  Information on tasks to which personnel have already been assigned is stored as task data in the first system (project management system), and at least identification data of the assigned personnel is associated with the task data. Since this identification data is also included in the personnel data held in the second system (personnel management system), it can be used as key information for record search.

  When a resource manager or other person in charge (HR person, person in charge, supervisor of the report, etc.) changes specific personnel data in the second system (HR management system), the personnel assignment system inputs the change. Accept. In response to accepting the change, the personnel assignment system determines whether there is a related task assigned to the person to be changed, using the identification data as a search key, and the task of the first system (project management system) Judgment is made by referring to the data. If there is at least one related task, the personnel assignment system acquires task data of the related task and stores it in an event database (personal event database).

  The event database data (event data) can be displayed on the display device of the resource manager or the project manager. In the embodiment, after the assignment operation by the resource manager, the project manager approves (or rejects) the assignment contents. Thus, it should be noted that event data is initially presented only to the resource manager user terminal, but such a configuration is optional.

  When the personnel assignment system receives a search request for substitute personnel for the displayed related task, the personnel assignment system searches the second system (HR management system) to search for alternative candidates that can be assigned to the related task, and substitute candidates. Get personnel data for. This list of alternative candidates that can be assigned is also displayed on the display device of the resource manager or the project manager. When the personnel assignment system accepts a selection of alternative personnel from this list, it assigns the selected alternative personnel to the related task described above and stores the personnel data in the event database. When the project manager approves the assignment of the substitute personnel, the personnel assignment system of the present invention stores the assigned substitute personnel identification data in association with the task data of the related task in the first system (project management system). To do. As a result, the reallocation data is automatically reflected in the project management system.

  When identifying an alternative candidate that can be reassigned, it is important to check whether there are tasks already assigned to that candidate. This is because it is not practical to assign such a candidate to a new task whose execution period overlaps with an already assigned task. In order to avoid such a situation, the personnel assignment system of the present invention finds not only personnel data of the second system (HR management system) but also the first system (project management system) when finding an alternative candidate. Also search for task data. The list of alternative candidates includes only alternative candidates in which the new task period data and the assigned task period data do not overlap.

  The present invention can be understood as a computer that executes the above-described personnel assignment, a method for such personnel assignment, and a program that causes a computer to execute such a method.

  The present invention provides a mechanism capable of dynamically allocating personnel again in response to changes in personnel data even if the personnel situation changes after the personnel are allocated to the project. The With this mechanism, it is possible to reduce the processing load of project management and personnel management required by such personnel data change. In addition, even when personnel data changes, the project manager or resource manager can quickly recognize the fact, and as a result, timely and efficient project management becomes possible.

  The present invention is constructed as an independent system separated from these systems while maintaining the functions of the existing project management system and personnel management system as they are, so that the latest data of each system can be synchronized in a timely manner. By doing so, flexible and dynamic personnel assignment can be performed.

  Hereinafter, the present invention will be described using specific embodiments and examples. However, such embodiments and examples are shown as examples only, and are intended to limit the invention according to the claims. is not.

(1) Overall View of Integrated System FIG. 1 is a configuration diagram of an integrated system 1 for implementing the personnel assignment method of the present invention. As shown in FIG. 1, the integrated system 1 includes a personnel assignment system 10, a project management system (PM system) 20, and a personnel management system (RM system) 30. These systems are implemented using a computer such as a general server. In this specification, a user terminal 40 of a project manager (PM) and a user terminal 50 of a resource manager (RM) are connected to the integrated system 1 via a network 60. However, physically, the project manager may directly configure the PM system 20 and the resource manager may directly operate the RM system 30.

  The personnel assignment system 10 is a computer such as a server that realizes the main function of the present invention for assigning personnel to project tasks, and is connected to the PM system 20 and the RM system 30 via a network 60. The personnel assignment system 10 is accessible from both the project manager (PM) and the resource manager (RM), but the range of data that can be accessed is controlled. Specifically, the personnel assignment system 10 includes a task event database (task event DB) 12, an assignment processing module 14, a personnel event database (personnel event DB) 16, and a candidate table 18. These more detailed configurations and operations will be described later.

The PM system 20 is a computer such as a server that holds and manages information relating to a project, and is mainly used by a project manager. The PM system 20 can be implemented by introducing a commercially available project management tool into a computer. Functionally, the PM system 20 includes a project management database (PM-DB) 22, a project management module (PM module) 24, and an event. A table 26 is included.
The project manager accesses the PM system 20 via the user terminal 40. The PM module 24 generates a screen for inputting the requirements of a project that requires personnel assignment and displays the screen on the user terminal 40. One project is usually composed of a plurality of tasks. For example, in the case of a product development project, design, development, testing, etc. are examples of tasks. The project manager enters data on project requirements, such as the number of people, required skills and their level, and duration of implementation for each task. The input data is stored in the project management database 22 by the PM module 24. When the project manager enters data for all project requirements and requests personnel assignments, the request is written to the event table 26 as event data. An event that inputs a requirement for a task constituting such a project and requests assignment of personnel is referred to as a “task requirement event” or a “task event” in this specification. “Task requirement event” includes determination and change of task contents (including required skill and period), and addition and deletion of tasks.
In the present embodiment, the personnel assignment system 10 polls the event table 26 periodically. Thus, task requirement events are accepted by the personnel assignment system 10 by writing to the event table 26. Of course, the request may be transmitted to the personnel assignment system 10 each time a task requirement event occurs.

The RM system 30 is a computer such as a server that maintains and manages information about assigned personnel, and is mainly used by resource managers. The RM system 30 can be implemented by introducing a commercially available HR management tool into a computer. Functionally, the RM system 30 includes a HR management database (RM-DB) 32, a HR management module (RM module) 34, and an event. A table 36 is included.
The resource manager accesses the RM system 30 via the user terminal 50. The RM module 34 extracts necessary personnel data from the personnel management database 32 in response to a request from the resource manager, generates a screen, and transmits the screen to the user terminal 50. The resource manager can perform editing operations such as creation, change, and deletion of personnel data on the screen. Such personnel data can be referred to and edited by a person other than the resource manager (for example, a person in charge of the personnel department, each person himself / herself, a manager who reports the person, etc.). In response to editing personnel data, when the resource manager requests another personnel assignment, the request is written as event data to the event table 36. Events that require reassignment of personnel in response to such changes in personnel data are referred to herein as “personnel requirement events” or “personnel events”. “Personnel requirement events” include personnel decisions and changes, personnel deletions and additions, personnel skills and status updates.
In the present embodiment, the personnel assignment system 10 polls the event table 36 periodically. Accordingly, a personnel requirement event is accepted by the personnel assignment system 10 by writing to the event table 36. Of course, the request may be transmitted to the personnel assignment system 10 each time a personnel requirement event occurs.

  The user terminals 40 and 50 may be general information devices such as a personal computer, a PDA (personal digital assistant), and a mobile phone. Users (including project managers and resource managers) access the integrated system 1 from the user terminals 40 and 50 by using a general web browser or by installing a dedicated client program. can do. The network 60 may be a closed network such as an in-house LAN or an open network such as the Internet. However, for security reasons, it is desirable to have a mechanism that allows only authenticated users to access the system.

(2) Data Structure Examples of various data used in the integrated system 1 will be described with reference to FIGS. It should be noted that these data structures are only examples of data items necessary for the present embodiment, and other data items may be included in an actual system.

  FIG. 2 is a diagram illustrating an example of task data stored in the project management database 22 of the PM system 20. The project management database 22 of this specification stores a project record 220, a task record 240, and a skill record 260. These task data are mainly entered by the project manager who specifies the project requirements.

  The project record 220 includes information necessary for specifying each project. Specifically, each project record 220 has the following fields. The “project ID” field includes a number for identifying a specific project, and one number is assigned to one project. The “project name” field contains the name of the project. The “Project Status” field has data indicating the current status of each project. For example, “CREATE (Creating Project Data)”, “ASSIGNED (Personnel Allocated)”, “ACTIVE (Start Project) And “under execution)”, “REVIEW (project verification in progress)”, “COMPLETE (project completion)”, “ARCHIVE (data storage)”, and the like. The “project start date” field is data of a date when the project is started. The “project end date” field is data on a date when all the tasks are completed and the project is ended.

  The task record 240 contains information necessary to identify each task. As already described, since one project is composed of a plurality of tasks, the project record 220 and the task record 240 have a “1: N” relationship. Specifically, each task record 240 has the following data fields. The “task ID” field includes a number for identifying a specific task, and one number is assigned to one task. The “task name” field includes the name of the task. The “task status” field has data indicating the current status of each task. For example, “CREATE (task data is being created)”, “ASSIGNED (assigned personnel)”, “ACTIVE (task start) And “Running”, “REVIEW (task verification)”, “COMPLETE (task completion)”, and the like. The “in charge” field contains data for identifying the personnel assigned to the task. The “task start date” field is data of a date when the task is started. The “task end date” field is data of a date when the task is ended. The “project ID” field has an identification number of the corresponding project. With this data as a foreign key, the task record 240 is associated with the corresponding project record 220.

  Skill record 260 includes information regarding skills required to perform a task. Since a plurality of skills may be required to execute one task, the task record 240 and the skill record 260 have a relationship of “1: N”. Specifically, the skill record 260 has the following data fields. The “skill ID” field is a number for identifying a specific skill. The “skill name” field represents the name of the skill and includes data such as project manager (role), designer (role), tester (role), English (language), JAVA (R) (programming language). In the “skill level” field, the relative evaluation of each skill is shown as a numerical value. In the embodiment of the present invention, a numerical value in the range of 0 to 9 can be input. The “task ID” field has an identification number of the corresponding task. With this data as a foreign key, the skill record 260 is associated with the corresponding task record 240.

  FIG. 3 is a diagram illustrating an example of personnel data stored in the personnel management database 32 of the RM system 30. The personnel management database 32 of this specification stores personnel records 320 and personnel skill records 340. These personnel data can be input by a resource manager or personnel manager who handles personnel information, the person himself / herself, a boss who reports the personnel, and the like.

  The personnel record 320 includes information necessary for identifying personnel managed by the RM system 30. The “personnel ID” field is a number for identifying an individual person. The “Name” field contains the name of the person. The “personnel status” field has data indicating the current situation of each person, and includes data such as “AVAILABLE (normal)”, “VACATION (vacation)”, “LEAVE (absence)”, and the like. In the present embodiment, the RM system 30 is not a system specialized for personnel assignment. Accordingly, a special status such as “ASIGEDED (assigned)” is not prepared, but status data unique to such personnel assignment may be provided. The “start date” field indicates the start date of the validity period (duration) of the data in the “personnel status” field, and the “end date” field indicates the end date of the validity period (duration) of the data in the “personnel status” field. Is shown.

  The personnel skill record 340 includes information on skills possessed by the personnel and has a data structure similar to that of the skill record 260 described above. Since one person may have a plurality of skills, the person record 320 and the person skill record 340 have a relationship of “1: N”. Specifically, the personnel skill record 340 has the following data fields. The “skill ID” field is a number for identifying a specific skill. The “skill name” field indicates the name of the skill, for example, data such as project manager (role), designer (role), tester (role), English (language), JAVA (R) (programming language), etc. Including. In the “skill level” field, the relative evaluation of each skill is shown as a numerical value. In the embodiment of the present invention, a numerical value in the range of 0 to 9 can be input. The “start date” field indicates when the skill has become effective, and the “end date” field indicates how long the skill has been effective. The “personnel ID” field is an identification number of a person having the skill. With this data as an external key, the personnel skill record 340 is associated with the corresponding personnel record 320.

  FIG. 4 is a diagram showing an example of event data stored in the task event database 12 of the personnel assignment system 10.

The task requirement event data can be represented as a collection of task requirement records 120. The task requirement record 120 is generated for each task in response to the personnel allocation system 10 receiving the task requirement event, and is deleted or stored as log data when processing is completed (inactive state and Become). The task requirement record 120 holds information as to which task is assigned to which task for how long. Specifically, the task requirement record 120 has the following data fields. The data in the “event ID” field is a number for identifying the task requirement event. The “project ID” field and the “task ID” field include numbers for identifying the related project and the related task, respectively. The data of this “project ID” serves as an external key and associates the task requirement record 120 with the project record 220 of the project management database 22. Since there are a plurality of tasks for one project, the task requirement record 120 and the project record 220 have a relationship of “N: 1”. Since the project record 220 has already been described, it will not be described in detail here.
The “personnel ID” field has a number for identifying the person assigned to the task. The “requirement status” field has data indicating the current status of each task. For example, “REQUESTED (request accepted)”, “ASSIGEDED (assigned personnel)”, “NOTASSIGED (unassigned personnel)”, “ It includes data such as “NOTAVAILABLE”, “APPROVED”, “REJECTED”. The “task start date” field has date data on which the task starts, and the “task end date” field has date data on which the task ends. The “owner” field indicates a user who can access the task requirement record 120. In this embodiment, since the project manager or resource manager is the main user, the type or person identification information is written (for example, switching between 0 and 1 of the corresponding data bit). That is, the user's access can be restricted by rewriting this “owner” field.

  FIG. 5 is a diagram illustrating an example of event data stored in the personnel event database 16 of the personnel assignment system 10.

  Personnel requirement event data can be represented as a collection of personnel requirement records 160. Each personnel requirement record 160 is generated when an event occurs, and when the processing is completed, it is deleted or stored as log data (becomes inactive). In response to a change in the data of the personnel already assigned to the project (specifically, tasks), the personnel requirement record 160 indicates each task to which the applicable personnel have been assigned (the corresponding personnel data). It is generated for each task that is affected by the change. Here, the change of personnel data includes deletion of personnel, status change, and skill change. Such a change in personnel data can be performed not only by the resource manager, but also by a personnel manager, each employee himself / herself, and a supervisor who reports the personnel. The personnel requirement record 160 holds information on the identification number, status, and period of the corresponding task, and specifically has the following data fields. The data in the “event ID” field is a number for identifying the personnel requirement event. The “task ID” field includes a number for identifying the related task to which the person has been assigned. The “personnel ID” field includes a number for identifying a person whose personnel data has been changed. This “personnel ID” data serves as an external key, and associates the personnel requirement record 160 with the personnel record 320 of the personnel management database 32. Since a plurality of tasks may be assigned to one person, the person requirement record 160 and the person record 320 have a relationship of “N: 1”. Since the personnel record 320 has already been described, it will not be described in detail here.

  The “requirement status” field has data indicating the current status of each person. For example, “REQUESTED (request accepted)”, “ASSIGNED (person assigned)”, “NOTASSIGNED (person unconfirmed)”, “NOTAVAILABLE” (Personnel assignment is not possible), “APPROVED (approval)”, “REJECTED (reassignment request)” and the like. The data in the “start date” and “end date” fields specify the start and end dates of the validity period of the personnel requirement. The “Owner” field indicates a user who can access the personnel requirement record 160. In this embodiment, since the project manager or resource manager is the main user, the type or person identification information is written (for example, switching between 0 and 1 of the corresponding data bit). That is, the user's access can be restricted by rewriting this “owner” field.

(3) Personnel Assignment System FIG. 6 is a functional block diagram of the personnel assignment system 10. In the following, the personnel assignment system 10 forming the core of the present invention will be described in more detail. The personnel assignment system 10 includes an input / output control means 11, a task event database (task event DB) 12, a communication control means 13, an assignment processing module 14, a personnel event database (personnel event DB) 16, and a candidate table 18. Has been. Since the task event DB 12 and the personnel event DB 16 have already been described with reference to FIGS. 5 and 6, detailed description thereof will be omitted.

  The input / output control means 11 is an interface between the assignment processing module 14 and an input device such as a keyboard and a mouse, an output device such as a display and a printer, an external storage device such as a CD-ROM and a hard disk device, and other input / output devices. For example, when the project manager or the resource manager directly operates the personnel assignment system 10, the input / output control means 11 processes the input / output.

  The communication control means 13 is an interface between the external network and the assignment processing module 14. In the present embodiment, the communication control means 13 controls the exchange of data with the user terminal 40 of the project manager or the user terminal 50 of the resource manager via the network 60.

  The assignment processing module 14 is a program that executes a series of processes for assigning appropriate personnel when a task requirement event and a personnel requirement event occur. Physically, various functions are realized by reading a program stored in a storage device such as a hard disk device of the personnel assignment system 10 into a main storage device and executing it by a processor (CPU). Specifically, the allocation processing module 14 includes a receiving unit 110, a task determining unit 120, a notification unit 130, a search unit 140, a display control unit 150, and an allocation control unit 160.

  The accepting unit 110 accepts a request, selection or other input from the project manager or resource manager. Specifically, the reception unit 110 displays a personnel assignment request (task requirement event) in response to an input of task requirements, a change in personnel data in response to an input of personnel requirements (personal requirement event), a search request for personnel, and the like. Accept, edit, select, confirm or reject records, approve assignments, etc.

  The task determination unit 120 identifies a person whose data has been changed when a staff requirement event occurs, and determines whether there is a task assigned to the person. Specifically, the task determination unit 120 makes an inquiry to the PM system 20 using the personnel ID as a search key, and determines whether the project management database 22 has an associated task record 240.

  The notification means 130 notifies the project manager or resource manager that there is some event that requires action. Specifically, when the project manager or resource manager accesses the personnel assignment system 10, the notification unit 130 can access the task requirement record 120 and the personnel requirement record 160 by referring to the data in the “owner” field. If there is event data, the data is presented to the project manager or resource manager.

  In response to the search request, the search unit 140 accesses the PM system 20 or the RM system 30 and acquires information on necessary personnel or tasks. For example, in response to a personnel search request from the resource manager, the personnel management database 32 of the RM system 30 is searched to retrieve candidate personnel data that matches the task requirements. In addition, when a personnel requirement event occurs, the search unit 140 searches the project management database 22 of the PM system 20 in response to a search request for an alternative candidate, and acquires necessary task data. This is because if a person listed as an alternative candidate already has a task assigned, a new task cannot be assigned during the execution of that task, so information about such assigned tasks is obtained. It is necessary. Specifically, the search means 140 described above examines the period data included in the related task data of the alternative candidate acquired as the search result, and the period of the related task already allocated and the period of the task to be reassigned Are not stored in the candidate table 18 described later. In this way, a list of only personnel that can be assigned is created, and the data is displayed by the display control means 150.

  In the present embodiment, the PM system 20 and the RM system 30 are connected as independent systems, and the personnel assignment system 10 operates in such a manner that these are integrated in the situation of personnel assignment. Therefore, the PM system 20 and the RM system 30 can hold the latest data without being aware of the personnel assignment system 10. On the other hand, the personnel assignment system 10 acquires necessary data from the PM system 20 or the RM system 30 only when necessary. As described above, the period data of tasks already assigned to the listed candidates is also acquired from the project management database 22 as necessary after the search for candidates is completed.

  The candidate table 18 stores a list of assignable personnel (candidates) acquired as a result of the search by the search means 140. This data is presented to the project manager or resource manager and held until the assignment (or reassignment) of personnel to the task is finally approved through candidate selection, confirmation or rejection.

  The display control means 150 displays the contents of the event that has occurred, the result of the search (list of candidates that can be assigned), the result of the assignment execution, etc. on the user terminal 40 of the project manager or the user terminal 50 of the resource manager. . In order to create this display content, data from the task event database 12, the personnel event database 16, the candidate table 18, the PM database 22, and the RM database 32 are referred to as necessary.

  In response to accepting the task requirement event or the personnel requirement event, the assignment control means 160 creates an event record (120, 160) and manages it in the event database (12, 16). In addition, the assignment control unit 160 performs assignment of personnel appropriate to the task in response to user operations such as input by the resource manager, selection, confirmation, input by the project manager, selection, confirmation, and approval. The content of the personnel assignment approved by the project manager is finally written into the project management database 22 of the PM system 20 by the assignment control means 160.

  In the following embodiment, a processing flow of the personnel assignment system 10 will be described using a specific example. More specifically, a processing flow when a task requirement event occurs will be described with reference to FIG. 7, and a processing flow when a personnel requirement event occurs will be described with reference to FIG. It should be noted that the process shown in FIG. 8 is executed after the personnel assignment process as shown in FIG. 7 is performed.

(4) Task Requirement Event FIG. 7 is a diagram showing a processing flow of the personnel assignment system 10 when a task requirement event occurs. This processing flow will be described with reference to FIGS. 9 to 12 together with FIG.

  In the personnel assignment system 10, first, the accepting unit 110 accepts a request for assigning personnel to one or more tasks constituting the project from the PM system 20 (step 710). This assignment request is generated by the project manager accessing the PM system 20 and entering task requirements.

  FIG. 9 is a diagram showing an example of a screen image of the PM system 20 for inputting such task requirements. Here, it is assumed that personnel are allocated to the development project of the product AAA. This project is composed of four tasks, “Design”, “Develop”, “Develop 2”, and “Test”, and it is possible to input data on the content of skill required, its level, and the duration of the task. Needed. After inputting these data, for example, by clicking the “ASSIGN” button, an allocation request is generated and written into the event table 26. The personnel assignment system 10 (accepting means 110) periodically polls the event table 26, and as a result, the assignment request is accepted by the personnel assignment system 10. The assignment control means 160 creates a task requirement event record 120 for each task in response to accepting the assignment request. Necessary data is acquired from the project management database 22. At this time, data is written in the “owner” field so as to permit access to the resource manager. When the resource manager accesses the personnel assignment system 10, the presence of this event is notified by the notification means 130 (step 715).

  FIG. 10 is a diagram illustrating an example of a screen image when the resource manager accesses the personnel assignment system 10. This screen shows that there are two task requirement events (EVT0001 and EVT0002). When the resource manager clicks the “select” button of “EVT0001”, a table regarding the details of the corresponding task requirement is displayed. Here, it is shown that there are four task requirements. When the resource manager clicks a “search” button for a specific task (developer skill: 7), the accepting means 110 accepts a search request for assignable personnel (step 720).

  The search unit 140 searches the RM system 30 in response to the search request, and acquires personnel data that meets the search conditions from the personnel management database 32 (step 725). Specifically, the search means 140 compares the skill content, skill level and task period data included in the search condition with the personnel skill record 340, and the personnel who meet or close to the condition Is identified. If the conditions do not completely match, how much is specified as “assignable” personnel is arbitrary. Further, after confirming the “status” data of the personnel record 320, personnel data such as assignable personnel ID, name, and skill are acquired. When there are a plurality of assignable personnel, a plurality of personnel data is acquired as a list.

  The display control means 150 displays the acquired assignable personnel data on the screen as a table (step 730). Referring to FIG. 10, an example of a search result is shown. Here, three people are shown as candidates. The resource manager can select a person to be assigned from the list by putting a check mark in the “selection” column. In this case, it is possible to select a plurality of personnel as allocation candidates. Here, since the level of the required skill is “7”, it is most appropriate to select “Kato” having a skill higher than that. When the resource manager clicks the “confirm” button after selecting a specific person (for example, “Kato”), the accepting unit 110 of the staff assignment system 10 accepts the selection of the assignment candidate (step 735). In response to the confirmation of the personnel selection, the “Status” data in the detailed task requirement table of FIG. 10 is changed from “NotAssigned” to “Assigned”. Refer to the task record of “Designer” to which “Yamazaki” is assigned.

  If there are other tasks to assign personnel (No in step 740), the assignment control means 160 waits for further search requests from the resource manager (the personnel assignment system 10 waits). If the resource manager assigns personnel to all tasks and clicks the “Finish” button at the bottom of the screen (Yes in step 740), the notification means 110 indicates that the assignment of personnel to the project or task is complete. Notify the manager (step 745).

FIG. 11 is a diagram illustrating an example of a screen image when the project manager accesses the personnel assignment system 10. As can be seen from the figure, the configuration of the screen is similar to FIG. For example, the task requirement detail table is displayed by selecting a specific task. The main difference is that the search for allocation candidates (and provisional allocation) has already been completed on this screen. As a result, the project manager is not required to perform a search request. For example, in the leftmost column of the detailed table, a “confirm” button is prepared instead of “search”. When the project manager clicks this “confirm” button, a list of personnel assigned to the corresponding task is displayed. If multiple tasks are present in the list (Yes in step 750), the project manager needs to confirm and confirm the personnel assignment of all tasks (No in step 760).
If there are multiple assignment candidates, the project manager can change or add the assigned personnel selection. To do this, add or delete a check mark in the “Select” column of the search result, and then click the “Confirm” button. If there is only one candidate, the project manager simply clicks the “OK” button. Thereby, the reception means 110 of the personnel assignment system 10 receives the selection of personnel (step 755). In response to the confirmation of the personnel selection, the “Status” data in the detailed table of FIG. 11 is changed from “Assigned” to “Approved”. Refer to the task record of “Designer” to which “Yamazaki” is assigned.
If the project manager rejects the assigned personnel, click the "Reject" button in the search results table. In this case, “Status” in the detailed table is not changed, and the “Approve” button at the bottom of the screen cannot be clicked.

  If assignments for all tasks are confirmed (Yes in step 760), or if there is only one task in the first place (No in step 750), the project manager asks whether or not to approve the assigned personnel (Step 765). When approving, the project manager clicks an “approve” button at the bottom of the screen of FIG. 11 (Yes in step 765). In the personnel assignment system 10, the assignment control means 160 automatically reflects the approved personnel data in the project management database 22 of the PM system 20 (step 770), and the process ends. If not approved, the project manager clicks the “re-notify” button at the bottom of the screen of FIG. 11 (No in step 765). As a result, the notification unit 110 notifies the resource manager again of the event. The personnel assignment system 10 resumes the process from step 715. As described above, when the project manager rejects even one task, the “approval” button cannot be clicked. Therefore, in this case as well, the “re-notify” button is pressed and the same processing is executed.

  FIG. 12 is a diagram illustrating an example of a screen image of the PM system 20 after approval of personnel assignment. As understood from comparison with FIG. 9, the “Status” data is updated from “Not Assigned” to “Assigned”, and the names of the personnel assigned to the “Assign” column are displayed.

(5) Personnel requirement event FIG. 8 is a diagram showing a processing flow of the personnel assignment system 10 when a personnel requirement event occurs. This processing flow will be described with reference to FIGS. 13 to 16 together with FIG. 13 to 16 are shown as examples of screens that are transitioned after the approval of the personnel assignment shown in FIG. 12 for easy understanding.

  In the personnel assignment system 10, the accepting unit 110 first accepts a personnel data change request from the RM system 30 (step 810). This change request is typically generated by the resource manager accessing the RM system 30 and inputting the contents of the personnel requirements (update contents). Here, the change of personnel data includes addition and deletion of personnel, addition, modification and deletion of data relating to skills and status. Such change of personnel data can be performed not only by the resource manager but also by other personnel (for example, personnel personnel, individual personnel, and managers reported by the personnel).

  FIG. 13 is a diagram illustrating an example of a screen image of the RM system 30 for inputting such personnel requirements. In this example, data for six personnel is shown. In this embodiment, as highlighted in FIG. 13, (1) “Developer” (level 4) is added as the skill of “Yamazaki”, and (2) the status of “Yamada” is changed from “normal” to “normal”. The processing flow of the present invention will be described using a scenario for changing to “time off” for a period. The resource manager and other data editors enter the personnel requirements (1) and (2) in the screen edit mode. After that, by clicking the “Update” button at the bottom of the screen, the personnel data change request is written to the event table 36 as event data. The personnel assignment system 10 (accepting means 110) periodically polls the event table 36, and as a result, a change request is accepted by the personnel assignment system 10.

  Returning to the processing flow of the personnel assignment system 10. In response to the reception of the personnel data change request, the task determination unit 120 determines whether there is a task that has already been assigned to the personnel to be changed and is affected by the data change. It is determined whether or not (step 812). The task determination unit 120 checks whether there is task data related to the project management database 22 of the PM system 20 using the personnel ID data as a key. As a result, when the assigned task does not exist and when only the task that is assigned but not affected by the personnel data change exists, the personnel assignment system 10 ends the process (N0 in step 812). . If there are only tasks that are not subject to the latter change, if there is a skill addition or change or skill level change but the requirements of the assigned task are met (for example, a new skill has been added) Only if the necessary skills are still retained in the assigned task), if the status has changed but does not overlap with the execution period of the assigned task (for example, August 10-14, 2004) The status is changed to “vacation” until the task start date is September 1, 2004). Therefore, in the case of (1), there is no related task (No in Step 812), but in the case of (2), there is a related task (Yes in Step 812). .

  If there are related tasks, the assignment control means 160 creates a personnel requirement event record 160 for each task. Necessary data is acquired from the project management database 22 and the personnel management database 32. At this time, data is written in the “owner” field so as to permit access to the resource manager. When the resource manager accesses the personnel assignment system 10, the presence of this event is notified by the notification means 130 (step 815). The display control means 150 displays information on tasks assigned to the corresponding personnel. It is displayed on the user terminal 50 of the resource manager.

  FIG. 14 is a diagram illustrating an example of a screen image when the resource manager accesses the personnel assignment system 10. This screen indicates that there is one event (EVT9001). When the resource manager clicks the “select” button of “EVT 9001”, a table regarding the details of the corresponding personnel requirement is displayed. Here it is shown that one personnel requirement exists. When the resource manager clicks a “search” button for a specific task (developer skill: 3), the accepting means 110 accepts a search request for an assignable substitute person (step 820).

  The search unit 140 searches the RM system 30 in response to the search request, and acquires data of alternative personnel (candidates) that meet the search conditions from the personnel management database 32 (step 825). Specifically, the search means 140 compares the skill content, skill level, and task period data included in the search condition with the personnel skill record 340, and replaces it with an alternative candidate that meets the condition or with this. Identify nearby alternative candidates. If the conditions do not completely match, the extent to which the candidate is specified as an “assignable” alternative candidate is arbitrary. Further, after confirming the “status” data of the personnel record 320, personnel data such as the ID, name, and skill of the alternative candidate that can be assigned is acquired. When there are a plurality of alternative candidates that can be assigned, a plurality of personnel data is acquired as a list.

  The search unit 140 also searches the PM system 20 using the alternative candidate ID as a key, and acquires data (particularly, period data) related to the task assigned to the alternative candidate from the project management database 22 (step 828). ). Such data is necessary because it is not practical to assign a task to such an alternative candidate if the execution period of the task already assigned to the alternative candidate overlaps with the execution period of the task to be newly assigned. is there. For this determination, the search unit 140 searches not only the RM system 30 but also the PM system 20.

  The display control means 150 displays assignable alternative candidate data as a table on the screen (step 830). Referring to FIG. 14, an example of a search result is shown. Here, two personnel are shown as candidates. Among them, “Yamazaki” is a person who has added skills in (1) above, and has already been assigned to a task as a “designer” in a task requirement event (see, for example, FIG. 12), but the periods do not overlap. Therefore, it is listed as an assignable candidate. The resource manager can select a person to be assigned from the list by putting a check mark in the “selection” column. In this case, it is possible to select a plurality of personnel as allocation candidates. Here, since the level of the required skill is “3”, it is most appropriate to select “Yamazaki” having a skill higher than that. When the resource manager clicks the “confirm” button after selecting a specific person (for example, “Yamazaki”), the accepting means 110 of the staff assignment system 10 accepts the selection of the assignment candidate (step 835). In response to the confirmation of the personnel selection, the “Status” data in the detailed table of personnel requirements in FIG. 14 is changed from “NotAssigned” to “Assigned”.

  If there are other tasks to assign personnel (No in step 840), the assignment control means 160 waits for further search requests from the resource manager (the personnel assignment system 10 waits). If the resource manager assigns personnel to all tasks and clicks the “Finish” button at the bottom of the screen (Yes in step 840), the notification means 110 indicates that the assignment of personnel to the project or task is complete. Notify the manager (step 845).

FIG. 15 is a diagram illustrating an example of a screen image when the project manager accesses the personnel assignment system 10. As can be seen from the figure, the configuration of the screen is similar to that of FIG. For example, the details table is displayed by selecting a specific personnel requirement. The difference is that the search for assignment candidates (and provisional assignment) has already been completed on this screen. As a result, the project manager is not required to perform a search request. For example, in the leftmost column of the detailed table, a “confirm” button is prepared instead of “search”. When the project manager clicks this “confirm” button, a list of corresponding assignment candidates is displayed. If multiple tasks (personnel requirements) are present in the list (Yes in step 850), the project manager needs to confirm and confirm the personnel assignment of all tasks (personnel requirements) (No in step 860).
If there are multiple assignment candidates, the project manager can change or add the assigned personnel selection. To do this, add or delete a check mark in the “Select” column of the search result, and then click the “Confirm” button. If there is only one candidate, the project manager simply clicks the “OK” button. Thereby, the reception means 110 of the personnel assignment system 10 receives the selection of personnel (step 855). In response to the confirmation of the personnel selection, the “Status” data in the detailed table of FIG. 15 is changed from “Assigned” to “Approved”.
If the project manager rejects the assigned personnel, click the "Reject" button in the search results table. In this case, the “Approve” button at the bottom of the screen cannot be clicked.

  If the assignment for all tasks (personnel requirements) is confirmed (Yes in step 860), or if only one task (personnel requirement) exists (No in step 850), the project manager approves the assigned personnel A determination is made as to whether or not to perform (step 865). When approving, the project manager clicks an “approve” button at the bottom of the screen of FIG. 15 (Yes in step 865). In the personnel assignment system 10, the assignment control means 160 automatically reflects the approved personnel data in the project management database 22 of the PM system 20 (step 870). If not approved, the project manager clicks the “re-notify” button at the bottom of the screen of FIG. 15 (No in step 865). As a result, the notification unit 110 notifies the resource manager again of the event. The personnel assignment system 10 resumes the process from step 815. As described above, if the project manager rejects even one task (personnel requirement), the “approval” button cannot be clicked. Therefore, in this case as well, the “re-notify” button is pressed and the same processing is executed.

  FIG. 16 is a diagram illustrating an example of a screen image of the PM system 20 after approval of personnel assignment. As is highlighted, it can be seen that the person in charge of the task “Develop2” is updated from “Yamada” to “Yamazaki” and displayed in the “Assign” column, as compared with FIG.

  In summary, the present invention is implemented as a project management system that manages data (task data) related to a plurality of tasks constituting a project and a personnel assignment system that is connected to a personnel management system that manages data related to personnel (personnel data). Is done. Information on tasks to which personnel have already been assigned is held as task data in the project management system, and at least identification data of the assigned personnel is associated with the task data. Since this identification data is also included in personnel data held in the personnel management system, it can be used as key information for record search. Therefore, even if a change occurs in the personnel data, the personnel allocation system of the present invention can automatically extract a related assigned task from the identification data, and automatically reassign the replacement personnel from there again. It can be performed.

(6) Other Embodiments In the above embodiment, when assigning personnel to a task, the resource manager first searches for and selects a preliminary personnel (provisional assignment), and then the project manager performs this content. The assignment contents are confirmed for the first time by approving. However, it may be configured to cause the project manager to directly perform personnel search and selection. In this case, in step 715 of FIG. 7 and step 815 of FIG. 8, the event is notified to the project manager, and the project manager executes the subsequent operations. Then, the processing flow after the connection points A (FIG. 7) and B (FIG. 8) is connected to the block 765 in FIG. 7 and the block 865 in FIG. 8, respectively.

  Further, in the above embodiment, when there are a plurality of allocation candidates, it is possible to change the personnel by presenting all candidates to the project manager. However, the selection by the resource manager may be fixed, and the project manager may be configured not to select other candidates.

 In the embodiment, the user terminal 40 of the project manager and the user terminal 50 of the resource manager are connected to the personnel assignment system 10 via the network 60. However, the project manager or the resource manager may directly operate the personnel assignment system 10.

It is a block diagram of the integrated system 1 suitable for the personnel allocation method of this invention. It is a figure which shows an example of the task data memorize | stored in the project management database. It is a figure which shows an example of the personnel data memorize | stored in the personnel management database. It is a figure which shows an example of the event data memorize | stored in the task event database. It is a figure which shows an example of the event data memorize | stored in personnel event database. 1 is a functional block diagram of a personnel assignment system 10. FIG. It is a figure which shows the processing flow of the personnel assignment system 10 when a task requirement event generate | occur | produces. It is a figure which shows the processing flow of the personnel allocation system 10 when a personnel requirement event generate | occur | produces. It is a figure which shows the example of the screen image of the project management system 20 for inputting task requirements. It is a figure which shows the example of a screen image when a resource manager accesses the personnel allocation system. It is a figure which shows the example of a screen image when a project manager accesses the personnel allocation system. It is a figure which shows the example of the screen image of the project management system 20 after personnel allocation approval. It is a figure which shows the example of the screen image of the personnel management system 30 for inputting personnel requirements. It is a figure which shows the example of a screen image when a resource manager accesses the personnel allocation system. It is a figure which shows the example of a screen image when a project manager accesses the personnel allocation system. It is a figure which shows the example of the screen image of the project management system 20 after personnel allocation approval.

Explanation of symbols

1. . . Integrated system, 10. . . Personnel assignment system, 20. . . Project management system, 30. . . Human resource management system, 40. . . User terminal (project manager), 50. . . User terminal (resource manager)

Claims (20)

In a computer connected to a project management system for managing data (task data) related to a plurality of tasks constituting a project and a personnel management system for managing data (personnel data) including personnel data including identification data. A method for assigning personnel to tasks,
In response to a request from the project management system to assign personnel to at least one task, the computer retrieves the personnel management system and retrieves at least one personnel that meets the requirements of the at least one task. Storing the identification data of the assigned at least one person in association with the task data in the project management system;
The computer accepting a change in personnel data for a particular personnel from a personnel management system;
In response to acceptance of the change, the computer determines whether there is at least one related task assigned to the specific person, using the identification data of the specific person as a key, and task data of the project management system Determining by referring to:
If there is the at least one related task, the computer obtains task data of the related task, stores it in an event database, and displays it on a display device;
The computer accepting a search request for substitute personnel for the related task;
The computer in response to the substitute personnel search request, searching a human resources management system to search for alternative candidates that can be assigned to the related task, and obtaining personnel data of the alternative candidates;
The computer displaying on the display device a list of alternative candidates that can be assigned;
The computer accepting a selection of alternative personnel from the list;
The computer responsive to selection of the substitute personnel assigning the selected substitute personnel to the associated task and storing personnel data of the substitute personnel in the event database;
Equipped with a,
If there is no related task, the process is terminated in the determining step.
A method for personnel assignment.   The method according to claim 1, wherein the task data includes data related to a task execution period (period data). After the step of acquiring the replacement candidate personnel data, the computer determines whether there is at least one assigned task assigned to the replacement candidate, using the identification data of the replacement candidate as a key. Determining by referring to the task data of the project management system, and when there is the assigned task, further including the step of acquiring the task data of the assigned task;
The list of assignable alternative candidates includes only alternative candidates in which the period data of the related task and the period data of the assigned task do not overlap.
The method of claim 2.   The computer further comprising storing, in the project management system, identification data of the substitute personnel in association with the task data of the related task in response to the project manager approving the assignment of the substitute personnel; The method of claim 1.   The method of claim 1, wherein the display device is a display of a first user terminal used by a resource manager.   The computer notifying the project manager that the substitute person has been assigned to the related task and displaying the data contained in the event database on a second user terminal used by the project manager; The method of claim 5, further comprising:   The computer further includes the step of storing the substitute personnel identification data in the project management system in association with the task data of the related task in response to the project manager approving the assignment of the substitute personnel. The method according to claim 6.   The method of claim 1, wherein the display device is a display of a project manager user terminal. To a computer connected to a project management system for managing data (task data) related to a plurality of tasks constituting a project and a personnel management system for managing data (personnel data) including personnel identification data. A program for executing a procedure for assigning personnel to a task, the procedure being
In response to a request for assignment of personnel to at least one task from the project management system, the personnel management system is searched and at least one person meeting the requirements of the at least one task is assigned by searching the personnel management system. Storing at least one assigned personnel identification data in the project management system in association with the task data;
Accepting changes to personnel data for a specific person from the HR management system;
In response to accepting the change, whether or not there is at least one related task assigned to the specific person is referred to the task management system task data using the identification data of the specific person as a key. Determining by
If there is at least one related task, obtaining task data of the related task, storing it in an event database, and displaying it on a display device;
Accepting a substitute search request for the related task;
In response to the search request for substitute personnel, searching a personnel management system to search for substitute candidates that can be assigned to the related task, and obtaining personnel data of the substitute candidates;
Displaying a list of possible alternative candidates on the display device;
Receiving a selection of alternative personnel from the list;
In response to selecting the substitute personnel, assigning the selected substitute personnel to the related task and storing personnel data of the substitute personnel in the event database;
Only including,
If there is no related task, the process ends in the determining step.
A program for personnel assignment.   The program according to claim 9, wherein the task data includes data (period data) related to a task execution period. After the step of acquiring personnel data of the alternative candidate, the procedure determines whether there is at least one assigned task assigned to the alternative candidate using the identification data of the alternative candidate as a key. Determining by referring to the task data of the project management system, and when there is the assigned task, further including the step of acquiring the task data of the assigned task;
The list of assignable alternative candidates includes only alternative candidates in which the period data of the related task and the period data of the assigned task do not overlap.
The program according to claim 10.   The procedure further includes storing the substitute personnel identification data in the project management system in association with the task data of the related task in response to the project manager approving the substitute personnel assignment. The program according to claim 9.   The program according to claim 9, wherein the display device is a display of a first user terminal used by a resource manager.   The step of notifying a project manager that the substitute person has been assigned to the related task and displaying the data contained in the event database on a second user terminal used by the project manager; The program according to claim 13, further comprising:   The computer further includes the step of storing the substitute personnel identification data in the project management system in association with the task data of the related task in response to the project manager approving the assignment of the substitute personnel. The program according to claim 14.   The program according to claim 9, wherein the display device is a display of a user terminal of a project manager. It is connected via a network to a project management system for managing data related to multiple tasks (task data) constituting a project and a personnel management system for managing data related to personnel (personnel data) including identification data. , A computer for assigning personnel to the task, wherein the task data includes identification data of the personnel if personnel have already been assigned to the corresponding task,
Receiving means for receiving events, requests or inputs from a project management system, personnel management system or other user terminal;
In response to receiving an input to change personnel data of a specific person from the personnel management system, the receiving means determines whether there is at least one related task assigned to the specific person. Judgment means for judging by referring to task data of the project management system using personnel identification data as a key,
If there is at least one related task, assignment control means for acquiring task data of the related task and storing it in the event database;
Display control means for displaying data contained in the event database on a display device;
In response to the reception means accepting a search request for substitute personnel for the related task, the personnel management system is searched for a substitute candidate that can be assigned to the related task, and personnel data of the substitute candidate is retrieved. And a search means for acquiring
The display control means displays the list of alternative candidates on the display device, and the assignment control means is selected in response to the reception means accepting selection of alternative personnel from the list. Assigning the substitute personnel to the related task, storing personnel data of the substitute personnel in the event database ;
When there is no related task, the process is terminated by the determination by the determination unit.
Computer for personnel assignment. The task data includes data (period data) related to the task execution period,
After the retrieval means obtains personnel data of the alternative candidate, whether or not there is at least one assigned task further assigned to the alternative candidate is determined by using the identification data of the alternative candidate as a key and the project. Judgment is made by referring to the task data of the management system, and when there is the assigned task, the task data of the assigned task is obtained
The list of assignable alternative candidates includes only alternative candidates in which the period data of the related task and the period data of the assigned task do not overlap.
The computer according to claim 17.   The assignment control means is further responsive to the approval of the assignment of the substitute personnel by the project manager, and stores the identification data of the substitute personnel in the project management system in association with the task data of the related task. Item 18. The computer according to Item 17. The display device is a display of a first user terminal used by a resource manager;
The display control means displays data included in the event database on a second user terminal used by the project manager.
The computer according to claim 17.

Images