Management program

Abstract

To provide a novel program for project management, and the like, and applications thereof.SOLUTION: A program for an organization to manage work time assignment of human resources is configured to execute at least the steps of: receiving or storing staff basic information; receiving or storing data on basic workable time; calculating and storing assignment registrable time; providing an interface for displaying a result of aggregating the basic workable time, and the like; receiving or storing project information; receiving or storing assign request information and calculating and storing assign request time; and receiving or storing approval or denial information for an assign request.SELECTED DRAWING: None

Description

[Technical field]

[0001] The present disclosure relates to management programs, and more particularly, to programs for organizations to allocate and manage the working hours of human resources. [Background technology]

[0002] In many industrial fields, project management is one of the important management items. Examples of project management include assigning the right people to the right tasks and managing the progress.

[0003] Patent Document 1 discloses a device, program, etc. that can create a work schedule that does not concentrate the workload on a specific person. For example, Patent Document 1 discloses a work schedule creation unit 15, and discloses that the schedule creation unit 15 determines whether or not the difference in the number of work days between the personnel with the most and the least number of work days in the created work schedule is within a predetermined value (for example, within one day). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2014-052761 A Summary of the Invention [Problem to be solved by the invention]

[0005] Typically, multiple projects are carried out in parallel within a company. The leader of each project tries to recruit talented people from within the company to join the project. As a result, there is often a scramble for talented people, and the company's human resources are not used effectively. Therefore, the present disclosure aims to provide a new program for managing the allocation of human resources in project management, and its application. [Means for solving the problem]

[0006] In order to achieve the above object, in one aspect, the present disclosure includes the following invention. (Invention 1) A program for an organization to allocate and manage the working hours of human resources, comprising: The program is A step (10) of receiving or storing basic staff information (the basic staff information includes one or more of name, date of joining, date of leaving, working conditions, and basic attributes); A step (20) of receiving or storing data on basic available hours, the data on the basic available hours being data generated by calculating one or more of the basic available hours by day, week, month, period, and year that the target staff can work from one or more of the joining date, leaving date, and working conditions included in the received or stored staff basic information; A step (30) of subtracting the assignment schedule time from the calculated basic available operation time to calculate and store an assignment schedule registration available time; a step (40) of providing an interface (referred to as interface A) for aggregating one or more of the available basic time, scheduled assignment time, available time for scheduled assignment registration, and assignment request time in one or more formats of by project, by staff, by day, by week, by month, by period, and by year, and displaying the aggregation results together with the staff basic information and / or project information; a step (50) of receiving or storing the project information (wherein the project information includes one or more of project details, internal / external classification, order amount, project budget, project period, required personnel structure (including one or more of job rank and number of people), required personnel skills, and required personnel man-hours); A step (60) of receiving or storing assignment request information (wherein the assignment request information includes one or more of the project information, the job rank of the desired staff, the desired staff, the period, and the required man-hours, but the desired staff may not be specified) and calculating and storing an assignment request time; If the desired staff member is not specified in the assignment request information, or if the desired staff member is changed, information of a new designated staff member is received or stored, and the assignment request time is recalculated and stored (70); receiving or storing approval or denial information of the assignment request, and if approval, storing the assignment request information as scheduled assignment information for the target staff member, and recalculating the assignment request time as scheduled assignment time (80); The program is configured to execute at least the steps described above, although the steps may be performed in any order. (Invention 2) A program of Invention 1, wherein the program is configured to display, in the interface A, scheduled assignment information at the time of registering the scheduled assignment project and scheduled assignment information at the time the assignment request is approved and the scheduled assignment is finalized in a comparable form. (Invention 3) A program of Invention 1, wherein the program is configured, at the interface A, to display the labor force in a format different from the format of the labor force within a predetermined range when the labor force exceeds or falls below the predetermined range, and / or to display a warning to the effect that the labor force exceeds or falls below the predetermined range. (Invention 4) A program according to invention 1, comprising, in the recalculating step (80), setting a denial flag and / or a return flag in the assignment request information in the case of denial. (Invention 5) A program according to Invention 1, wherein the staff basic information further includes at least one of skills and experience. (Invention 6) The program of Invention 1, further configured to execute a step (90) of calculating project selection information (wherein the project selection information includes one or more of profitability and risk) from the received project information. (Invention 7) A program of Invention 1, comprising, in a step (50) of receiving or storing project information, when a target project is canceled, recalculating one or more of the scheduled assignment time, the scheduled assignment registration available time, and the assignment request time associated with the project information. (Invention 8) A system for an organization to allocate and manage work hours of human resources, the system comprising: a first server; and a second server; The first server includes the program according to claim 1 (hereinafter referred to as the first program), The second server includes the program according to claim 1 (hereinafter referred to as the second program), The first program is configured to generate external assignable staff list data in response to an operation from a first user; The second program is configured to receive the external assignable staff list data in response to an operation from a second user, and add at least one of the staff members included in the data to the assignment request information as a desired staff member; the second program is configured to send an outbound staff assignment request to the first program in response to an operation from a second user; The first program is configured to receive the outbound staff assignment request and send approval or denial information to the second program; system. (Invention 9) A system for an organization to allocate and manage work hours of human resources, the system comprising: a first server; and a second server; The first server includes the program according to claim 1 (hereinafter referred to as the first program), The second server includes the program according to claim 1 (hereinafter referred to as the second program), The second program is configured to generate external staff recruitment list data in response to an operation from a second user, The first program is configured to receive the external staff recruitment list data in response to an operation from a first user, and create external staff offer data including at least one of the staff members belonging to the first user as a desired staff member; The first program is configured to transmit the outbound staff offer data to the second program in response to an operation from a first user; The second program is configured to receive the outbound staff offer data and send approval or rejection information to the first program; system. (Invention 10) The system according to claim 8 or 9, further comprising a third server: the third server comprises a third program; the third program is used by a third user; The third program is configured to generate invoice data; the invoice data is invoice data which lists the third user as a creditor and at least one of the first user and the second user as a debtor, The invoice data is (a) Data concerning charges for the use of the system by the first user and / or the second user; (i) Data regarding charges for talent allocation agreements between the first user and / or the second user Includes one or more of the following: system. (Invention 11) A system according to invention 8, wherein the external assignable staff list data includes staff introduction video data. Effect of the Invention

[0007] In one aspect, the invention has the functionality to receive or store approval or denial information for assignment requests, allowing the approver to act as a coordinator or monitor to prevent competition for talent. [Brief description of the drawings]

[0008] [Figure 1] 1 shows a system configuration according to an embodiment. [Diagram 2] 1 shows a configuration of an apparatus according to an embodiment. [Diagram 3] 13 shows the relationship between a basic available time, a scheduled assignment time, a scheduled assignment registration available time, and an assignment request time in one embodiment. [Figure 4] 1 illustrates an interface in one embodiment. [Diagram 5] 1 illustrates an interface in one embodiment. [Figure 6] 1 illustrates an interface in one embodiment. [Figure 7] 1 illustrates an interface in one embodiment. [Figure 8] 1 illustrates an interface in one embodiment. [Figure 9] 1 shows a system configuration according to an embodiment. [Figure 10] 1 shows a system configuration according to an embodiment. [Figure 11] 1 shows a system configuration according to an embodiment. [Figure 12] 1 illustrates an interface in one embodiment. [Figure 13] 1 illustrates an interface in one embodiment. [Figure 14] 1 illustrates an interface in one embodiment. [Figure 15] 1 illustrates an interface in one embodiment. [Figure 16]1 illustrates an interface in one embodiment. [Figure 17] 1 illustrates an interface in one embodiment. [Figure 18] 1 illustrates an interface in one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, specific embodiments for carrying out the present invention will be described. The following description is intended to facilitate understanding of the invention, and is not intended to limit the scope of the present invention.

[0010] 1. Operating environment, terminology, etc. In one embodiment, the presently disclosed invention relates to a method, a program, a storage medium (e.g., a computer-readable non-transitory storage medium) storing the program, an apparatus (e.g., an information processing device), and a system for an organization to allocate and manage the working hours of human resources.

[0011] The execution environment for implementing the above-mentioned invention is not particularly limited. FIG. 1 shows an execution environment for implementing the invention of the present disclosure in one embodiment. A server 1010 and multiple terminals are connected through a network. In FIG. 1, the server 1010 is represented as a single piece of hardware, but may be distributed across multiple pieces of physical hardware. The server 1010 may be a cloud server or an on-premise server. The edge terminal 1020 is represented as multiple terminals, but in theory it may be a single terminal. However, when using the server 1010, since it is often used jointly by multiple users, typically the system has multiple edge terminals 1020. The network may be wired, wireless, or a combination of both.

[0012] The above-mentioned server 1010 and edge terminal 1020 are typically information processing devices.

[0013] The information processing device may typically include a processor 1040, a memory 1050, a storage medium 1060, and a communication module 1070, as shown in FIG.

[0014] Examples of information processing devices include, but are not limited to, the following: servers, personal computers, single-board computers (e.g., Raspberry Pi, etc.), tablet terminals, smartphones, smart watches, smart glasses, etc.

[0015] The program is stored in a storage medium 1060 (e.g., HDD, SSD, etc.), loaded into a memory 1050 (e.g., RAM, etc.) as appropriate, and executed by a processor 1040 (e.g., an electronic processor such as a CPU, etc.). If necessary, the program can connect to a network through a communication module 1070 to transmit and receive information.

[0016] In one embodiment, the program may be installed as application software on one information processing device and executed by the information processing device.

[0017] In another embodiment, the number of information processing devices is not limited to one, and multiple information processing devices may be used as necessary. In this case, the functions of the program may be distributed among the multiple information processing devices. Therefore, the term "program" in this specification not only includes a single program installed in one information processing device, but also includes a combination of multiple programs distributed and installed among multiple information processing devices.

[0018] 2. Overview In one embodiment, the present disclosure relates to a program for an organization to allocate and manage work hours of human resources and a method of using the program, the program being configured to at least perform the following steps (10) to (90):

[0019] A step (10) of receiving or storing basic staff information (the basic staff information includes one or more of name, date of joining, date of leaving, working conditions, and basic attributes);

[0020] A step (20) of receiving or storing data on basic available hours, the data on the basic available hours being data generated by calculating one or more of the basic available hours by day, week, month, period, and year that the target staff can work from one or more of the joining date, leaving date, and working conditions included in the received or stored staff basic information, the step (20);

[0021] A step (30) of subtracting at least the scheduled assignment time from the calculated basic available time and calculating and storing the available time for scheduled assignment registration.

[0022] A step (40) of providing an interface (referred to as interface A) for aggregating one or more of the available basic time, scheduled assignment time, available time for scheduled assignment registration, and assignment request time in one or more formats of by project, by staff, by day, by week, by month, by period, and by year, and displaying the aggregation results together with the staff basic information and / or project information.

[0023] a step (50) of receiving or storing the project information (wherein the project information includes one or more of project details, internal / external classification, order amount, project budget, project period, required personnel structure (including one or more of job rank and number of people), required personnel skills, and required personnel man-hours);

[0024] A step (60) of receiving or storing assignment request information (wherein the assignment request information includes at least one of the project information, the job rank of the desired staff, the desired staff, the period, and the required man-hours, but the desired staff may not be specified) and calculating and storing an assignment request time.

[0025] If the desired staff member is not specified in the assignment request information, or if the desired staff member is changed, information on the new designated staff member is received or stored, and the assignment request time is recalculated and stored (70).

[0026] A step (80) of receiving or storing approval or denial information of the assignment request, and in the case of approval, storing the assignment request information as scheduled assignment information for the subject staff member, and recalculating the assignment request time as scheduled assignment time.

[0027] It should be noted that the above steps may be performed in any order. Each step will be described in detail below.

[0028] 3. Staff Basic Information, Steps (10) As described above, in one embodiment, the present disclosure is a program for an organization to allocate and manage the working hours of human resources. Therefore, it is necessary to manage basic information of the staff to be allocated in advance.

[0029] The specific content of the staff basic information is not particularly limited, but includes at least one of the staff member's name, joining date, leaving date, working conditions, and basic attributes. In addition, the basic attributes may include, but are not limited to, one or more of the following: position in the organization, department, etc. In addition to the above, the staff basic information may include one or more of the following: price (e.g., unit price), skills, experience, etc.

[0030] The basic staff information may be stored in the same device (e.g., a storage medium) as the information processing device in which the above-mentioned program is installed, or may be stored in a different information processing device. If stored in a different information processing device, the program may be configured to communicate with the different information processing device to receive the basic staff information. If stored in the same information processing device, the program may be configured to access a storage medium in the information processing device to receive the basic staff information.

[0031] The above-mentioned program may be incorporated as part of a program (for example, an ERP package) that includes a human resources and payroll function. In this case, when a staff member joins the company, the information is immediately reflected in the personnel database, so the above-mentioned program can access basic information on the staff member with little time lag.

[0032] In another example, the above-mentioned program may exist as an external program, without being incorporated into the program including the personnel and payroll functions, etc. In this case, basic information about the staff may be obtained by using an API provided by the program including the personnel and payroll functions, etc.

[0033] 4. Data on basic available time, step (20) Next, a step of receiving or storing data on the basic available hours of the staff is executed. The basic available hours data is data obtained by aggregating the hours that the target staff can work. The data may be aggregated by any one or more units of daily, weekly, monthly, quarterly (for example, by unit of first half / second half, or first quarter / second quarter / third quarter / fourth quarter), and annually.

[0034] The unit of calculation may be determined according to the nature of the project. For example, for an extremely short project that is completed in one or two weeks, calculations may be done by day. As another example, for a long-term project that lasts five years, calculations may be done by period or year.

[0035] The basic available hours may be tallied by the above-mentioned program based on the basic staff information. Alternatively, if data that has already been tallied by an external program is available, the data may be received.

[0036] When calculating basic available hours, basic staff information may be used. For example, basic available hours can be calculated by acquiring one or more of the following: date of joining, date of leaving, and working conditions. For example, if staff A has working conditions of 3 days a week (Monday, Wednesday, Friday, 9:00 to 15:00 (1 hour break)), the available hours per week will be 15 hours. And the daily working hours will be 5 hours, 0 hours, 5 hours, 0 hours, 5 hours.

[0037] 5. Assignment schedule registration time, step (30) After obtaining the data on the basic available hours, the available time for scheduled assignment registration is calculated. The available time for scheduled assignment registration indicates the remaining time for which a staff member can be assigned tasks. Therefore, when calculating the available time for scheduled assignment registration from the basic available hours, it is necessary to subtract the time corresponding to tasks that have already been assigned or are scheduled to be assigned (called scheduled assignment time). The aggregation of scheduled assignment times will be described later. Items to be subtracted from the basic available hours may include other items besides the scheduled assignment time. For example, time including the expected amount of paid leave may be further subtracted. Alternatively, spare time or buffer time may be further subtracted to allow some leeway in the project.

[0038] Like the data on basic available hours described above, the planned assigned time may be aggregated by one or more of the following units: daily, weekly, monthly, period (for example, first half / second half of the year, or first quarter / second quarter / third quarter / fourth quarter), and yearly.

[0039] In a preferred embodiment, it is preferable that the tabulation unit of the basal available time is the same as the tabulation unit of the scheduled assignment time. If the tabulation units are different, the tabulation may be performed according to the larger tabulation unit. For example, if the tabulation unit of the basal available time is daily and the tabulation unit of the scheduled assignment time is weekly, the basal available time may be re-tabulated weekly. After the re-tabulation, the scheduled assignment time may be subtracted.

[0040] 6. Providing an interface, step (40) In one embodiment, the program of the present disclosure is configured to execute a step of providing an interface for displaying the tabulated results. The interface also displays basic staff information and / or project information in addition to the tabulated results. The tabulated results include one or more of basic available hours, scheduled assignment hours, time available for scheduled assignment registration, and assignment request hours. The tabulated results can be tabulated in various units. Examples of the tabulated units include one or more of the following: by project, by staff, by day, by week, by month, by period, and by year.

[0041] 6-1. Statistical results The information to be aggregated is one or more of the following: available base time, scheduled assignment time, time available for scheduled assignment registration, and assignment request time. The meanings of available base time, scheduled assignment time, and time available for scheduled assignment registration have been explained above. Assignment request time refers to the time that is to be allocated to a specific person in relation to a specific project that is to be entered through the interface. The relationship between these four times can be summarized as shown in Figure 3.

[0042] When compiling, you can aggregate by project and then total man-hours. Or, you can aggregate by day, week, month, period, and year to see if there is a load on a specific period. Or, you can aggregate by project and staff to see if there is a load on a specific staff member in a specific project.

[0043] 6-2. Basic information about staff In addition, some additional information may be displayed together with the above tabulation results. For example, staff basic information can be cited as additional information to be displayed (the information contained in the staff basic information is as described above). For example, when referring to the above tabulation results, if a particular staff member has a heavy load and / or there are few allocations to a particular staff member, there may be times when it is desired to further refer to the information on these staff members and review the allocation. In such cases, the interface is configured so that the staff basic information can be further referred to.

[0044] 6-3.Project Information In another example, project information can be cited as further information to be displayed. For example, when the user refers to the above-mentioned aggregation result and finds that a particular staff member has a heavy load and / or that a particular staff member is not assigned much, the user may wish to refer to project information in which the particular staff member is involved. In addition, there may be times when the user wishes to review staff assignments depending on the content of the project. In such cases, the interface is configured so that the user can further refer to project information.

[0045] 6-4. Interface configuration The configuration of the interface for displaying the above-mentioned information is not particularly limited. For example, the interface provided may be one screen or a combination of multiple screens. For example, the above-mentioned tabulation results, basic staff information, and project information may be displayed on one screen. Alternatively, the above-mentioned tabulation results, basic staff information, and project information may be displayed on separate screens. When referring to separate screens, each screen may be provided with an item (button, link, pull-down, etc.) for switching to a screen displaying other information.

[0046] 7. Receiving or storing project information, step (50) As described above, in one embodiment, the program of the present disclosure may be configured to execute a step of providing an interface for displaying project information together with the aggregated results. In this regard, in one embodiment, the program of the present disclosure is configured to execute a step of receiving or storing project information. The project information includes any one or more of the following: project contents (e.g., client information, project purpose, etc.), internal / external classification (e.g., flags for distinguishing internal projects and external projects, etc.), order amount, project budget, project period, necessary personnel structure (e.g., including any one or more of job rank and number of people), necessary personnel skills, and necessary personnel man-hours.

[0047] In a preferred embodiment, the program may be configured to provide an interface for inputting project information, in alternative embodiments, the program may receive project information from another program, an external database, or the like.

[0048] In a preferred embodiment, the project information may further include project selection information. The project selection information includes at least one of profitability and risk. The project selection information is important information when allocating staff. For example, if a project has high profitability, it will be given a higher priority than other projects, and accordingly, a decision can be made to allocate more competent staff. Similarly, if a project has high risk, it can be decided to avoid allocating certain staff.

[0049] 8. Receiving or storing assignment request information, step (60) After the project information is registered, the program is further configured to receive or store assignment request information in relation to the project. The assignment request information includes one or more of the following: project information, desired staff rank, desired staff, period, and required man-hours. For example, after the project information is registered, the program can provide an interface for inputting the assignment request information. Then, through the interface, a user can input desired staff (e.g., information identifying staff, etc.) to specify which staff to assign to the project. Also, the rank when inputting the project information and the rank when inputting the assignment request information may not necessarily match. For example, when a project is accepted, a programmer may be input for a required position, but when it is time to actually assign personnel, the corresponding programmer cannot be secured, and a system engineer may be assigned to the position.

[0050] Also, at the stage of receiving or storing the assignment request information, the desired staff member may not be required, i.e. the post may be left vacant.

[0051] After receiving or storing the assignment request information, the required man-hours are tallied to calculate and store the assignment request time. For example, the assignment request time may be stored as being included in the assignment request information.

[0052] 9. Staff changes, etc., Step (70) The program can provide a user interface for approving the assignment request information. Approval of the assignment request information will be described later. The approver can designate or change staff when referring to the assignment request information. Therefore, the program may be configured to receive or store information on a new designated staff member designated by the approver. For example, if the desired staff member has not been specified when the assignment request information is circulated to the approver, the approver can specify a new staff member. Alternatively, if the assignor determines that a different staff member should be assigned when the assignment request information is circulated to the approver, the approver can specify a new staff member. Of course, there are also cases where the approver refers to the assignment request information and determines that there is no need to change the staff member. In that case, this step does not need to be performed.

[0053] 10. Approval and recalculation, step (80) The approver performs an operation such as approving or denying (e.g., rejecting or sending back) the assignment request information. In response to this, the program can receive or store the approval or denial information of the assignment request. For example, a flag corresponding to approval, denial, etc. can be set in the assignment request information. Furthermore, if approval is requested, the assignment request information is stored as scheduled assignment information for the target staff member. At this time, the program reflects the assignment request time as scheduled assignment time and performs recalculation. The subjects of the recalculation include scheduled assignment time, available time for scheduled assignment registration, etc. As described above, these times may be aggregated in one or more formats among project, staff, day, week, month, period, and year.

[0054] 11. Additional steps, features, etc. Further functions of the above-mentioned program and further steps executed will be described below.

[0055] 11-1. Comparison between registration and approval In one embodiment, the program can compare the scheduled assignment information for the same project at different times, which may include, for example, the scheduled assignment information at the time of registration of the scheduled assignment project and the scheduled assignment information at or after approval.

[0056] In one embodiment, the program is used at least by a user who gives approval and a user who registers project information. If the user who gives approval does not make any modifications to the assignment request information, there is a possibility that there will be a difference between the scheduled assignment information at the time of registering the scheduled assignment project and the scheduled assignment information at the time of approval or after. However, if the user who gives approval makes modifications (e.g., when changing staff), there is a possibility that there will be a difference between the two pieces of scheduled assignment information. Therefore, it is useful for both the user who gives approval and the user who registers project information to be able to confirm the differences.

[0057] 11-2. Expression of labor hours In one embodiment, the program is configured to present the effort above or below a predetermined range in a manner that is easy for the user to understand, for example, by displaying the effort in a format different from the format for the effort within the range, and / or by displaying a warning that the effort is above or below the predetermined range.

[0058] As an example of the former, if the man-hours are within a predetermined range, the man-hours figures may be displayed in black, and if they are outside the range, they may be displayed in a color other than black (e.g., red).Other methods include changing the background color, changing the font size, adding an icon indicating a warning, etc.

[0059] An example of the latter would be to display a text message such as "Staff member A's man-hours have exceeded the limit" on the margin of a table showing the man-hours.

[0060] 11-3. Handling project cancellations In addition, in the above process, the project itself may be canceled before or after the assignment request information is approved. In one embodiment, in the step (50) of receiving or storing project information, if the target project is canceled, the program can recalculate one or more of the scheduled assignment time, the scheduled assignment registration available time, and the assignment request time associated with the project information.

[0061] 12. Operation flow Above, the invention of this disclosure in one embodiment has been described in terms of program steps and functions. Below, we will explain how the program is used in terms of user screen operations.

[0062] 12-1.Project registration A user who registers assignment request information (or may be any other user) first registers project information before assigning staff. The contents of the project information are as described above. For example, the program can provide an interface shown in FIG. 4 for registering project information.

[0063] Figure 4 displays the received project code, project name, internal / external classification, order amount, project budget, project period, necessary personnel system, necessary personnel skills, necessary personnel man-hours, amount related to said man-hours (for example, calculated by multiplying unit price according to skill by man-hours), client information, project objective, profitability, and risk. Of these, the following items can be set by the user: internal / external classification, order amount, project budget, project period, necessary personnel system, necessary personnel skills, necessary personnel man-hours, client information, project objective, profitability, and risk.

[0064] In response to user input through the interface shown in FIG. 4, the program stores or receives project information (eg, as described above for step (50)).

[0065] 12-2. Registering assignment request information Next, the user who registered the assignment request information (or other users) assigns staff according to the project information. For example, the program can provide an interface shown in FIG. 5 for registering project information.

[0066] In FIG. 5, information related to the assignment request information can be displayed. For example, in FIG. 5, project information, desired staff position, desired staff, period, and required man-hours are displayed, and these items can be input. Note that the required man-hours may be assigned based on the man-hours in the project information as an initial setting. The man-hours assigned by the initial setting can be modified in the interface.

[0067] In addition, an "Approval Flow" button may be provided in the upper right corner of the screen for the purpose of making an assignment request and obtaining approval from an approver. By clicking the button, an approval request flag may be set for the assignment request information. The assignment request information for which the approval request flag has been set may be set so that it can be viewed by the approver.

[0068] The main function of the interface for registering assignment request information is to assign staff. Therefore, the interface may be equipped with a function for specifically assigning staff to the personnel slots set when registering project information. For example, on the screen in FIG. 5, to the right of the staff member's name, there is a section for selecting staff (the section marked with a ▼), and clicking on this section displays a screen corresponding to the above-mentioned interface A. Then, when a specific staff member is designated in the above-mentioned interface A, it may be reflected in the interface in FIG. 5.

[0069] An example of interface A is shown in Figure 6. At the top of the screen, there are items for entering search criteria so that searches can be performed based on staff name or job rank. There is also an item for selecting between yearly and weekly display so that the aggregation unit can be switched. Furthermore, there is an item for selecting one of available basic hours, scheduled assignment hours, time available for scheduled assignment registration, and assignment request hours so that the type of time to be displayed can be switched.

[0070] At the bottom of the screen of the interface in FIG. 6, a list of staff members is displayed in list form. Information such as the job rank, staff name, and man-hours for each staff member is displayed. In addition, for example, when the scheduled assignment time is displayed, if there is a month with extremely high man-hours or a month with extremely low man-hours, the display method can be changed so that the user can understand. In the example of FIG. 6, the man-hours for the month of staff members with extremely high man-hours are displayed with a gray background. On the other hand, the man-hours for staff members with extremely low man-hours are displayed in bold or italic. The reference value for determining whether the man-hours are high or low is not particularly limited, but in FIG. 6, the specified range is 120 to 180, and if the man-hours are outside the range, they are displayed in a different form.

[0071] A user who registers assignment request information can select staff to be assigned to a project while referring to the screen in Fig. 6. The method of selecting staff is not particularly limited, and for example, by performing an operation of selecting the staff name or the corresponding line, the staff can be reflected in the staff list on the screen shown in Fig. 5.

[0072] In addition, the user can refer to the screen in Figure 6 to determine which staff are busy, which staff have spare time, etc., and can use this information to allocate personnel. This can reduce the negative effects of personnel competition.

[0073] When outputting the contents shown in FIG. 6, the program can perform processing to acquire various information. For example, the program can acquire basic information about staff members (for example, as described above for step (10)). In particular, if the program is incorporated in an ERP package or the like and configured to be able to quickly acquire personnel information, information about new employees and the like can be displayed on the screen shown in FIG. 6. Therefore, a user who registers assignment request information can make assignments to new employees and the like who have plenty of time, without being significantly affected by the time lag between the personnel information system and the project management system.

[0074] In addition to the basic staff information, the program can also obtain and tally up basic available hours data. For example, in Figure 6, if "Monthly" and "Basic available hours" are selected (and the employee works 8 hours a day and 20 days a month), the screen will display 160 hours for each month (for example, as described above for step (20)).

[0075] The program can also obtain a scheduled assignment time, which corresponds to the time that the assigned effort was recorded, such as in the interface of FIG. 5. The program can then subtract the scheduled assignment time from the base available time to calculate the scheduled assignment time (e.g., as described above for step (30)).

[0076] Once the above information has been obtained and calculated, an interface of the form shown in FIG. 6 may be displayed (eg, as described above for step (40)).

[0077] After completing the input in Figure 5, the user may click an approval flow button or, although not shown in Figure 5, a save button (a function for saving the contents that have been partially input) may be clicked. In response, the program receives or stores the assignment request information. The program also calculates and stores the assignment request time (e.g., as described above for step (60)).

[0078] 12-3.Approval procedure The program is configured to provide an interface as shown in Fig. 7. Specifically, the program is configured to provide an interface that displays a list of multiple pieces of assignment request information. The interface may display code information (e.g., order code, project code, etc.) that identifies the assignment request information, a project name, a status, etc. The status may be expressed in multiple state categories, such as unapproved, approved, rejected, and returned.

[0079] The user who is to approve the project can open an interface like that shown in Figure 7. Then, from the list, the user can select the relevant project.

[0080] In response to an operation by the approving user (i.e., an operation to select a project), the program is further configured to provide an interface as shown in Fig. 8. This interface is similar to the interface shown in Fig. 5. The difference is that an item for approval is provided. For example, in the upper right corner of the interface shown in Fig. 8, approval, rejection, and return can be selected as options for approval, and the approving user can make the decision by selecting one of these and clicking the Confirm button.

[0081] By manipulating the personnel list area, like the interface shown in Figure 5, the program can provide the interface shown in Figure 6. Therefore, the user who is approving the project can determine whether or not to approve the project while checking whether a particular staff member is overworked or not.

[0082] In addition, in the interface shown in Figure 5, if a specific assignment slot remains vacant and the matter comes up for approval (for example, in the example shown in Figure 5, the slot for the sixth associate remains blank), the approving user can assign a specific staff member to the vacant slot through the interface of Figure 6.

[0083] Alternatively, for staff who have already been assigned, if the approving user determines that the staff member in question is overworked and overburdened, or is unsuitable in terms of skills, or in other cases, the staff member can be changed to another staff member.

[0084] In response to such an action, the program may receive or store new designated staff information and recalculate and store the assignment request time (eg, as described above for step (70)).

[0085] After checking the contents of the assignment request, the approving user can set the above-mentioned options for approval and then perform the finalization process. In response to this, the program receives or stores the approval or denial information of the assignment request, and in the case of approval, stores the assignment request information as the scheduled assignment information of the target staff member, and recalculates the assignment request time as the scheduled assignment time (e.g., as described above for step (80)).

[0086] Through the above procedures, assignments can be made in the project. The above program system allows the approver to perform the approval operation, so that even if each project leader competes for personnel independently, adjustments can be made at the approval stage. Furthermore, the user who gives the approval can refer to the man-hours of the staff, and this reference helps to make appropriate decisions. Also, by linking order management with staff assignment, the operational burden on the project leader is reduced.

[0087] 13. Mutual provision of human resources system (part 1) While the above embodiments have described project allocation within a particular organization, in another embodiment, the present disclosure relates to a system for cross-sharing of human resources, and more particularly, to a system for enabling cross-sharing of staff between different organizations.

[0088] For example, there may be cases where Company A needs personnel for a specific project, but cannot meet the demand with its own staff. In such a case, if Company B, which has temporary surplus staff, can provide Company A with suitable staff, it will be an effective use of human resources. In addition, it will be possible to avoid the drawbacks of a pyramidal structure (first-tier, second-tier, third-tier subcontracting) and flatten the chain, thereby reducing the middleman's margin.

[0089] In another embodiment, the system of the present disclosure may include a first server and a second server. Both servers may include the above-mentioned programs (first program, second program, respectively). An example is shown in FIG. 9. Each server is connected to a terminal corresponding to each organization. The above-mentioned programs can be utilized within each organization, thereby making it possible to allocate staff for each project. Here, the first server and the second server may be connected to each other through a network (typically the Internet). Also, the first server and the user of the first program may correspond to the organization that supplies staff. The second server and the user of the second program may correspond to the organization that supplies staff.

[0090] Each program may be configured to perform at least the following steps: The first program creates an external assignable staff list data in response to an operation from the first user; The second program receives externally assignable staff list data in response to an operation from the second user, and adds at least one of the staff members included in the data to the assignment request information as a desired staff member; the second program is configured to send an outbound staff assignment request to the first program in response to an operation from the second user; The first program receives outgoing staff assignment requests and sends approval or denial information to the second program.

[0091] The following provides specific examples of processing and screen operations.

[0092] 13-1. Creating external assignable staff list data The first program can register users who can be assigned within the organization in response to an operation from the first user. FIG. 12 shows an example of an interface provided by the first program. The first program can create external assignable staff list data through the interface, for example. The external assignable staff list data can include any one or more of the above-mentioned staff basic information, available basic hours, scheduled assignment hours, scheduled assignment registration available hours, and assignment request hours. Furthermore, the external assignable staff list data can include CV (curriculum vitae) information. The CV information can include, for example, any one or more of the following: work experience, achievements, awards, scholarships and grants obtained, curriculum acquired, research projects, publications, introduction videos (including PR videos), etc.

[0093] Furthermore, the external assignable staff list data may include an external assignment permission flag. The external assignment permission flag may be expressed as an item "external assignment" in the system interface, as shown in FIG. 12, for example, and the setting method is not particularly limited, but may be set by items such as a pull-down, a radio button, or a check box. In the interface shown in FIG. 12, the operation and expression method of the parts other than the external assignment may be the same as the interface shown in FIG. 6. Staff that have become externally assignable through the above interface may be displayed when other companies refer to the external talent assignable list. After setting the external assignment permission flag in the above interface, the data can be updated by clicking the "confirm" button, and the external assignable staff list data is created.

[0094] Furthermore, although not shown in the interface shown in Fig. 12, the first program may be configured to set a public / private flag. For example, a public / private flag may be set for personal information such as names included in the staff basic information to prevent them from being made public when reference is made from outside the company. When a public / private flag is set, the first program may be configured to change the expression to anonymous, initials, or the like. Furthermore, the first program may be configured to set whether any item other than the name should be made private.

[0095] Furthermore, the first program may be configured to set a target to be made public. In this case, the first program may be configured to refer to the list data of the disclosure target. For example, the system may be configured so that an intermediary server is provided in the system as shown in Fig. 11, and the list of the disclosure target is stored in the intermediary server. The first server (and the first program) may access the list data of the disclosure target and set, for each staff member in the company, to which company the information may be disclosed.

[0096] 13-2. Assignment of externally assignable staff The second server and the second program are configured to receive the above-mentioned external assignable staff list data. The assignable staff list data may be received, for example, by the second program accessing the first server through a network. Alternatively, the assignable staff list data may be received, for example, by the second program accessing the intermediary server through a network. In this case, the assignable staff list data is provided in advance from the first server to the intermediary server.

[0097] FIG. 13 shows an example of an interface provided by the second program. In this interface, data of the assignable staff list is displayed. The interface shown in FIG. 13 has the same functions as the interface shown in FIG. 6. However, in addition to the functions of the interface shown in FIG. 6, it has a function of switching between displaying a list of staff within the organization and a list of staff outside the organization (the "internal / external classification" shown in FIG. 13). In FIG. 13, "external" is selected, and in response to this, the list of staff that can be made public, which was set in the interface shown in FIG. 12, is displayed.

[0098] Also, since the staff outside the organization are displayed, the interface shown in FIG. 13 may be configured to display information of the affiliated company, unlike the interface shown in FIG. 6. Also, the interface shown in FIG. 13 can display basic information of each staff member. For example, a link is embedded in the staff member's name or initials field, and the link can be displayed on another screen by clicking on the link. Therefore, when selecting an outside staff member, the project leader can save the trouble of interviewing and the like, and can determine which staff member to assign by referring to the staff member basic information, CV information, etc. (for example, an introduction video, etc.). Then, the staff outside the organization can be set through the assignment request interface shown in FIG. 13 and FIG. 5. In response to this, the second program can add the set outside-organization staff member to the assignment request information as a desired staff member. Also, the second program can create an external staff assignment request including the set outside-organization staff member as a desired staff member.

[0099] 13-3. External staff assignment requests As described above, after creating the external staff assignment request, the second program can send the external staff assignment request to the first program. The first program can notify the first user, for example, through an arbitrary interface, that a request has come for a staff member in the organization to be assigned to an external project. The notification method is not particularly limited, and for example, a message that an assignment request has come from outside the organization for a specific staff member may be displayed on the interface shown in FIG. 12. In this case, the first program may be configured to be able to refer to information on the project to be assigned. For example, when the second program sends the external staff assignment request to the first program, it may also send at least a part of the above-mentioned assignment request information. Since the assignment request information includes the contents of the project, the first program can display the contents of the project for the first user. This allows the first user to determine whether or not it is acceptable to allow a staff member in the organization to be assigned to a project outside the organization.

[0100] In a preferred embodiment, the second program may be configured to set restrictions on items to be made public when sending assignment request information to the first program. For example, among project information, information on the order amount, project budget, etc. may be set not to be made public when sending to the first program.

[0101] 13-4. Assignment approval process After recognizing the notification of the external staff assignment request, the first user may operate an approval button in any interface if he / she wishes to allow the staff in his / her own organization to be assigned to a project outside his / her own organization. Conversely, if he / she wishes to refuse the assignment to a project outside his / her own organization, he / she may operate a denial button in any interface. In response to these operations, the first program is configured to send approval or denial information to the second program.

[0102] After obtaining the consent of the first user, the second user can carry out the above-mentioned approval procedure (eg, via the interface shown in FIG. 7).

[0103] 13-5.Other In the above-mentioned embodiment, the first server, the first program, and the first user are the staff providing side, and the second server, the second program, and the second user are the staff receiving side. However, the direction of providing and receiving staff may not be one-way, but may be two-way. Therefore, the above-mentioned program may have both the function of the staff providing side and the function of the staff receiving side.

[0104] In addition, the first server and the second server are not limited to physical servers, and may be virtual servers. For example, in Fig. 11 and Fig. 9, two servers are shown and are shown to exist as physically separate devices. However, in another embodiment, for example, as shown in Fig. 10, within one cloud server, a server corresponding to resources used by organization A and a server corresponding to resources used by organization B may be virtually separated. Therefore, it should be noted that the expression "first server" and "second server" includes not only physically separate servers, but also virtually separate servers.

[0105] Also, please note that the above method is not limited to one-to-one personnel exchanges, but includes 1-to-N (one first user and multiple second users), N-to-1 (multiple first users and one second user), and N-to-N (multiple first users and multiple second users) patterns.

[0106] Similarly, the above-mentioned first program and second program are not limited to being programs installed on physically separate devices, and may be installed within the same hardware.

[0107] 14. Human Resource Mutual Provision System (Part 2) In the above system ("Human Resources Mutual Provision System (Part 1)"), the second user (the staff accepting party) obtains approval from the first user (the staff providing party).

[0108] In other embodiments, the authorization may be performed in other ways. In such embodiments, the program may be configured to perform at least the following steps: The second program creates external staff recruitment list data in response to an operation from the second user; A first program receives external staff recruitment list data in response to an operation from a first user, and creates external staff offer data including at least one of the staff members belonging to the first user as a desired staff member; The first program transmits outward staff offer data to the second program in response to an operation from the first user; The second program receives the outgoing staff offer data and sends approval or rejection information to the first program.

[0109] 14-1. Creating external assignable staff list data Although not required, the externally-facing assignable staff list data may be created using a method and mechanism similar to that described above in "13-1. Creating externally-facing assignable staff list data."

[0110] 14-2. Creating external staff recruitment list data A difference from the above "13. Human Resource Mutual Provision System (Part 1)" is that external staff recruitment list data can be created in response to an operation from the second user. This allows an external organization that can provide staff to select a provision destination. The specific procedure is not particularly limited, but for example, the second program may be configured to provide an interface shown in FIG. 14. The interface shown in FIG. 14 is similar to the interface shown in FIG. 4, but the two differ in the following points: (1) it has an item for setting whether or not to allow external personnel recruitment, and (2) it has an item for setting whether or not to allow the allocation of personnel from external organizations for each personnel.

[0111] For example, in the example shown in Figure 14, the project is set to allow the recruitment of external personnel. In addition, the two associates are set to allow the assignment of personnel from outside.

[0112] In response to the second user operating the interface of Fig. 14, the second program can create external staff recruitment list data. The external staff recruitment list data can include, for example, any one or more of the following: a code of an order project, a project name, an internal / external classification, an order amount, a project budget, a project period, a necessary personnel system, a necessary personnel skill, a necessary personnel man-hour, an amount related to the man-hour (for example, calculated by multiplying a unit price according to a skill by a man-hour), an order source information, a project objective, profitability, and a risk. Furthermore, the external staff recruitment list data can include flag information on whether or not to permit external personnel recruitment in the project, and flag information on whether or not to permit allocation as external personnel among the necessary personnel skills.

[0113] In a preferred embodiment, by setting flag information regarding which items in the above-mentioned external staff recruitment list data are to be made public and which items are to be kept private, some items may not be included in the external staff recruitment list data, or may be included but may be restricted from being viewed. The second program can transmit the created external staff recruitment list data to the first program via a network. Alternatively, an intermediary server or the like may be provided, and the second program may upload the data to the server.

[0114] 14-3. Creation of external staff offer data Thereafter, the first program can receive the external staff recruitment list data in response to an operation from the first user. For example, the first program can provide an interface shown in Fig. 15. The first program can obtain the external staff recruitment list data by, for example, accessing an intermediary server, and can display the contents of the external staff recruitment list data in the interface shown in Fig. 15.

[0115] In the interface shown in FIG. 15, a list of projects selectable by the first user is displayed, and the interface is configured so that the list can be narrowed down appropriately by search or the like.

[0116] The first program may be configured to display detailed information when the recruitment requirements (or each project) are selected in the interface shown in FIG. 15. The configuration of the detailed information is not particularly limited, but the first program may be configured to provide an interface shown in FIG. 16, for example. The interface shown in FIG. 16 has a function for assigning at least one of the staff members belonging to the first user (or included in the externally assignable staff list data) as a desired staff member. In the example shown in FIG. 16, the number of personnel to be recruited is two, and the personnel designated as externally assignable staff members in the organization to which the first user belongs (see FIG. 13) can be assigned. After the assignment is completed, the first program creates externally-oriented staff offer data by the first user performing an operation such as clicking an "execute offer" button.

[0117] The external staff offer data may include at least a part of the external staff recruitment list data described above. In addition, the external staff offer data may include basic staff information, CV information, etc. (e.g., introduction video, etc.) of the staff specified in the interface shown in FIG.

[0118] 14-4. Sending staff offer data to the outside The first program can transmit outgoing staff offer data to the second program. In this specification, unless otherwise specified, transmission includes not only direct transmission but also indirect transmission. As an example of indirect transmission, for example, the first program may once upload outgoing staff offer data to the intermediary server, and the second program may access the intermediary server and download the outgoing staff offer data.

[0119] 14-5. Offer Approval Process The second program can receive outgoing staff offer data. For example, the second program can provide an interface shown in FIG. 17. The interface shown in FIG. 17 is similar to the interface shown in FIG. 14. For example, when project information created in the interface shown in FIG. 14 is called up again, the interface shown in FIG. 17 can be provided. The interface shown in FIG. 17 may be configured to display the latest version of the project information.

[0120] Then, a notification may be displayed to inform the user that the staff offer data for the outside of the organization has been received. Then, the interface shown in FIG. 18 may be further displayed by any means.

[0121] The interface shown in Fig. 18 is configured to display outgoing staff offer data from the first user. In addition to the information of the applicant corresponding to the first user, an item for approving or rejecting the application (offer) may be provided. The second user can select either approval or rejection of the application from the first user and perform an operation to confirm it. In response to the operation, the second program can reflect the above-mentioned assignment request information, etc.

[0122] Furthermore, the second program can transmit information on either approval or denial of the application from the first user to the first program.

[0123] 14-6.Other The subsequent flow may be as shown in "12. Operation Flow" above.

[0124] 15. Human Resource Mutual Provision System (Part 3)

[0125] Furthermore, the comprehensive server including the two cloud servers shown in FIG. 10 may also function as an intermediary server.

[0126] The intermediary server may be incorporated into the system as a third server, and the third server may include a third program. The third program may generate invoice data in response to a staff assignment contract being concluded between the first user and the second user.

[0127] The invoice data is data for an intermediary fee due to the establishment of a contract for staff assignment. Therefore, the third user corresponding to the intermediary may be the creditor. The third user may be a user corresponding to the third server described above. The debt for the intermediary fee may be incurred by the first user described above, the second user described above, or both.

[0128] The third program may also generate bill data corresponding to system usage fees between the first user and the second user.

[0129] The above-mentioned system enables each organization to exchange staff in both directions, and can provide a different business model from the conventional system of human resources provision through hierarchical outsourcing run by system companies.

[0130] Above, specific embodiments of the invention have been described. The above embodiments are merely examples, and the present invention is not limited to the above embodiments. For example, a technical feature disclosed in one of the above embodiments can be applied to other embodiments. In addition, unless otherwise specified, for a particular method, some steps can be replaced with other steps, and additional steps can be added between two specific steps. The scope of the present invention is defined by the claims.

Claims

1. A program for an organization to allocate and manage the working hours of human resources, comprising: The program is A step (10) of receiving or storing basic staff information (the basic staff information includes one or more of name, date of joining, date of leaving, working conditions, and basic attributes); A step (20) of receiving or storing data on available basic hours, the available basic hours being data generated by calculating one or more available basic hours of the day, week, month, period, and year that the target staff can work from one or more of the joining date, leaving date, and working conditions included in the received or stored staff basic information; A step (30) of subtracting the assignment schedule time from the calculated basic available time to calculate and store an assignment schedule registration available time; A step (40) of providing an interface (referred to as interface A) for aggregating one or more of the available basic time, scheduled assignment time, scheduled assignment registration available time, and assignment request time in one or more formats of by project, by staff, by day, by week, by month, by period, and by year, and displaying the aggregation results together with the staff basic information and / or project information; a step (50) of receiving or storing the project information (wherein the project information includes one or more of project details, internal / external classification, order amount, project budget, project period, required personnel structure (including one or more of job rank and number of people), required personnel skills, and required personnel man-hours); A step (60) of receiving or storing assignment request information (wherein the assignment request information includes one or more of the project information, the job rank of the desired staff, the desired staff, the period, and the required man-hours, but the desired staff may not be specified) and calculating and storing an assignment request time; If the desired staff member is not specified in the assignment request information, or if the desired staff member is changed, information of a new designated staff member is received or stored, and the assignment request time is recalculated and stored (70); receiving or storing approval or denial information of the assignment request, and if approval, storing the assignment request information as scheduled assignment information for the target staff member, and recalculating the assignment request time as scheduled assignment time (80); The program is configured to execute at least the steps described above, although the steps may be performed in any order.

2. 2. The program of claim 1, wherein the program is configured to display, in the interface A, scheduled assignment information at the time of registering the scheduled assignment project and scheduled assignment information at the time the assignment request is approved and the scheduled assignment is finalized in a comparable form.

3. 2. The program of claim 1, wherein the program is configured, at the interface A, to display the labor hours in a format different from the format of the labor hours within a predetermined range when the labor hours exceed or fall below the predetermined range, and / or to display a warning to the effect that the labor hours exceed or fall below the predetermined range.

4. 2. The program of claim 1, wherein the recalculating step (80) includes setting a denial flag and / or a return flag in the assignment request information in the case of denial.

5. 2. The program according to claim 1, wherein the staff basic information further includes at least one of skills and experience.

6. 2. The program of claim 1, further configured to perform the step of: calculating (90) project selection information from the received project information, where the project selection information includes one or more of profitability and risk.

7. 2. The program of claim 1, comprising, in the step (50) of receiving or storing project information, when a target project is canceled, recalculating one or more of the scheduled assignment time, the scheduled assignment registration available time, and the assignment request time associated with the project information.

8. A system for an organization to allocate and manage work hours of human resources, the system comprising: a first server; and a second server; The first server includes a program according to claim 1 (hereinafter referred to as a first program), The second server includes the program according to claim 1 (hereinafter, the second program), The first program is configured to generate external assignable staff list data in response to an operation from a first user, The second program is configured to receive the external assignable staff list data in response to an operation from the second user, and add at least one of the staff members included in the data to the assignment request information as a desired staff member; The second program is configured to send an outbound staff assignment request to the first program in response to an operation from a second user; The first program is configured to receive the outbound staff assignment request and send approval or denial information to the second program. system.

9. A system for an organization to allocate and manage work hours of human resources, the system comprising: a first server; and a second server; The first server includes a program according to claim 1 (hereinafter referred to as a first program), The second server includes the program according to claim 1 (hereinafter, the second program), The second program is configured to create external staff recruitment list data in response to an operation from a second user, The first program is configured to receive the external staff recruitment list data in response to an operation from the first user, and to create external staff offer data including at least one of the staff members belonging to the first user as a desired staff member; The first program is configured to transmit the outbound staff offer data to the second program in response to an operation from a first user, The second program is configured to receive the outbound staff offer data and send approval or denial information to the first program; system.

10. 10. The system of claim 8 or 9, further comprising a third server, the third server comprises a third program; the third program is used by a third user; the third program is configured to generate invoice data; the invoice data is invoice data which lists the third user as a creditor and at least one of the first user and the second user as a debtor, The invoice data is (a) data relating to charges for the first user and / or the second user's use of the system; (i) data regarding charges for talent allocation agreements between the first user and / or the second user; Including one or more of the following: system.

11. 9. The system according to claim 8, wherein the externally-available staff list data includes introductory video data of staff members.

Images