Enterprise human resource management method and device, equipment and storage medium

Abstract

The invention discloses an enterprise human resource management method and device, equipment and a storage medium. The method comprises the following steps: determining an employee identifier, project task data corresponding to the employee identifier and daily task data from an employee weekly report file; the project task data comprises a project identifier and task data corresponding to the project identifier; based on the project identifier, summarizing the project task data corresponding to the project identifier, and determining an actual project progress corresponding to the project identifier; comparing the actual project progress corresponding to the project identifier with the planned project progress corresponding to the project identifier to generate a target Gantt chart; and performing human use calculation on the project task working hours determined from the project task data and the daily task working hours determined from the daily task data to determine the use condition of human resources, thereby realizing automatic processing of employee weekly reports. Management of the human resources is realized through the target Gantt chart and the use condition of the human resources, and the management efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of data management technology, and in particular to a method, apparatus, device and storage medium for managing enterprise human resources. Background Art

[0002] With the popularization of the digital economy, companies' human resource management is accelerating its transformation from "process-driven" to "data intelligence-driven".

[0003] In the existing technology, human resources management is usually achieved by having company managers summarize and analyze employee weekly reports. However, manual summary and analysis is time-consuming and labor-intensive, and may result in errors in the summary, resulting in reduced efficiency of human resources management. Summary of the Invention

[0004] Based on the above problems, the present application provides a method, apparatus, device and storage medium for managing enterprise human resources, with the aim of improving the efficiency of human resources management.

[0005] The embodiments of this application disclose the following technical solutions:

[0006] First, a method for managing enterprise human resources, comprising:

[0007] Determine an employee ID, project task data corresponding to the employee ID, and daily task data from the employee weekly report file; the project task data includes a project ID and task data corresponding to the project ID;

[0008] Based on the project identifier, the project task data corresponding to the project identifier is aggregated and processed to determine the actual project progress corresponding to the project identifier;

[0009] Comparing the actual project progress corresponding to the project identifier with the planned project progress corresponding to the project identifier to generate a target Gantt chart; the target Gantt chart is used to compare the actual project progress and the planned project progress of the target project corresponding to the project identifier, so that managers can perform human resource management;

[0010] A manpower usage calculation is performed on the project task working hours determined from the project task data and the daily task working hours determined from the daily task data to determine the usage of human resources.

[0011] Optionally, the method as described above further includes: storing the project task data in a relational database, and storing the daily task data in a time series database.

[0012] Optionally, in the above method, the step of aggregating the project task data corresponding to the project identifier based on the project identifier to determine the actual project progress corresponding to the project identifier includes:

[0013] Extracting a plurality of task data corresponding to the project identifier from the relational database; the task data including the completed project file identifier and the corresponding completion time;

[0014] Based on the preset file identifiers corresponding to each project stage and the completion time corresponding to each file identifier, the project file identifiers in the plurality of task data are compared to determine the actual project progress corresponding to the project identifiers.

[0015] Optionally, in the above method, comparing the actual project progress corresponding to the project identifier with the planned project progress corresponding to the project identifier to generate a target Gantt chart includes:

[0016] Obtaining a project baseline file corresponding to the project identifier, and determining the planned time corresponding to each project phase from the project baseline file to generate a baseline Gantt chart; the baseline Gantt chart uses each color in the first color group to represent the planned project progress corresponding to the project identifier at each project phase;

[0017] A second color group is used to represent the actual project progress corresponding to each project stage in the project identifier to generate a dynamic Gantt chart; the colors in the second color group correspond one-to-one to the actual project progress of the project stage;

[0018] The benchmark Gantt chart and the dynamic Gantt chart are merged to obtain a target Gantt chart.

[0019] Optionally, the method as described above further includes:

[0020] Calculate the progress deviation and performance index corresponding to the target project stage based on the actual project progress and the planned project progress corresponding to the target project stage in the target Gantt chart;

[0021] When it is determined that the progress deviation is greater than a first preset threshold or the performance index is lower than a second preset threshold, risk warning information is generated and sent to a manager.

[0022] Optionally, in the above method, the step of performing manpower usage calculation on the project task hours determined from the project task data and the daily task hours determined from the daily task data to determine the usage of human resources includes:

[0023] According to the employee ID, determining the project task working hours corresponding to the employee ID from the relational database, and determining the daily task working hours corresponding to the employee ID from the time series database;

[0024] Determining the actual manpower used corresponding to the employee ID based on the project task working hours and daily task working hours corresponding to the employee ID;

[0025] Determining the workload intensity corresponding to the employee identifier based on the actual manpower used and the preset planned task hours;

[0026] A human resource view is generated based on the actual manpower usage and workload intensity corresponding to the employee identification; the human resource view is used to represent the usage of human resources corresponding to each of the multiple employee identifications.

[0027] Optionally, in the above method, determining the employee ID, the project task data corresponding to the employee ID, and the daily task data from the employee weekly report file includes:

[0028] Determining the employee identifier corresponding to the employee weekly report file from the employee weekly report file;

[0029] Perform sentence segmentation processing on the employee weekly report file, dividing the employee weekly report file into multiple short sentences;

[0030] Performing entity extraction processing on the multiple short sentences using a pre-trained model to obtain entities;

[0031] By classifying the entities, the project task data and daily task data corresponding to the employee identification are determined.

[0032] In a second aspect, a management device for enterprise human resources includes:

[0033] A data acquisition module is used to determine an employee ID, project task data corresponding to the employee ID, and daily task data from the employee weekly report file; the project task data includes a project ID and task data corresponding to the project ID;

[0034] A project progress calculation module is used to aggregate and process the project task data corresponding to the project identifier based on the project identifier to determine the actual project progress corresponding to the project identifier;

[0035] A Gantt chart generation module is used to compare the actual project progress corresponding to the project identifier with the planned project progress corresponding to the project identifier to generate a target Gantt chart; the target Gantt chart is used to compare the actual project progress and the planned project progress of the target project corresponding to the project identifier, so that managers can perform human resource management;

[0036] The manpower utilization calculation module is used to perform manpower utilization calculation on the project task working hours determined from the project task data and the daily task working hours determined from the daily task data to determine the utilization of human resources.

[0037] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0038] Memory stores computer-executable instructions;

[0039] The processor executes the computer-executable instructions stored in the memory to implement the enterprise human resources management method described in any one of the above embodiments.

[0040] In a fourth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the enterprise human resources management method described in any of the above embodiments.

[0041] Compared with the existing technology, this application has the following beneficial effects:

[0042] The method of the present application determines the employee ID, the project task data corresponding to the employee ID, and the daily task data from the employee weekly report file, thereby realizing automatic parsing of the employee weekly report information, reducing manual summary time and avoiding data duplication errors; then, based on the project ID, the project task data corresponding to the project ID are summarized and processed to determine the actual project progress corresponding to the project ID; and the actual project progress corresponding to the project ID is compared with the planned project progress corresponding to the project ID to generate a target Gantt chart, so that managers can quickly discover progress anomalies based on the target Gantt chart; manpower usage is calculated for the project task working hours determined from the project task data and the daily task working hours determined from the daily task data to determine the utilization of human resources, so that managers can adaptively adjust the allocation of human resources based on the utilization of human resources, and deploy human resources in advance to avoid the risk of project delays and reduced efficiency of human resource management. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0044] Figure 1A flowchart of a method for managing enterprise human resources provided in an embodiment of the present application;

[0045] Figure 2 A Gantt chart for the project in 2024 provided in an embodiment of the present application;

[0046] Figure 3 The human resources view provided for the embodiment of this application;

[0047] Figure 4 A schematic diagram of the structure of a human resources management device for an enterprise provided in an embodiment of the present application;

[0048] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] To make the objectives, technical solutions, and advantages of this application more clearly understood, the application is further described in detail below in conjunction with specific embodiments and with reference to the accompanying drawings. It should be noted that the embodiments described in the embodiments of this application are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of this application.

[0050] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this application should have the ordinary meaning understood by people with ordinary skills in the field to which this application belongs. The words "first", "second" and similar terms used in the embodiments of this application do not indicate any order, quantity or importance, but are only used to distinguish different components. Words such as "include" or "comprise" mean that the elements or objects preceding the word include the elements or objects listed after the word and their equivalents, but do not exclude other elements or objects. Words such as "connect" or "connected" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0051] As described above, the traditional weekly reporting system in current banking business management relies on manual summarization, and key information in the weekly report is difficult to quickly extract. Managers need to manually integrate data and rely on experience to judge the current status of department projects and tasks. This leads to time-consuming and labor-intensive summarization problems and errors, resulting in reduced efficiency of human resource management.

[0052] After research, the inventors proposed a method, device, equipment and storage medium for enterprise human resources management to solve the problems of opaque business progress and irrational human resource allocation in banking project management. By automatically processing weekly data, visual analysis of project progress and manpower utilization can be achieved, thereby improving the efficiency of human resource management.

[0053] In order to help those skilled in the art better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0054] See also Figure 1 , which is a flow chart of a method for managing enterprise human resources provided by an embodiment of the present application. Figure 1 As shown, the method includes:

[0055] S101: Determine an employee ID, project task data corresponding to the employee ID, and daily task data from an employee weekly report file.

[0056] The project task data includes a project identifier and task data corresponding to the project identifier.

[0057] In this embodiment, the employee weekly report file is work content submitted through a preset weekly report template, and the preset weekly report template includes two modules: project progress and daily tasks.

[0058] It's understandable that in addition to filling out and submitting weekly employee reports directly online, employees can also upload Markdown documents and images. The report also undergoes file type detection and format verification to ensure its completeness. For example, if an employee doesn't fill in the "Project Name" or "Progress Percentage" field according to the pre-set weekly report template, they will be prompted to complete the information. The progress percentage is the employee's percentage of project progress based on the category of the project documents they completed. For example, if a project has 50 files and an employee has completed 30, the progress is 60%. The progress percentage is filled in accordingly.

[0059] In this embodiment, as an implementable method, specific implementation steps for determining the employee ID, the project task data corresponding to the employee ID, and the daily task data from the employee weekly report file include:

[0060] S1011: Determine the employee ID corresponding to the employee weekly report file from the employee weekly report file.

[0061] In this embodiment, for the obtained employee weekly report files, the name or employee number corresponding to each employee weekly report file is obtained as the employee identification.

[0062] S1012: Sentence processing is performed on the employee weekly report file, and the employee weekly report file is split into multiple short sentences.

[0063] In this embodiment, the employee weekly report file corresponding to each employee identifier is sequentially sentence-processed. First, the employee weekly report file is cleaned and preprocessed to convert full-width characters (such as "." "()") to half-width to eliminate the interference of symbol format differences on sentence separation; irrelevant noise such as Markdown format symbols and flowchart symbols is filtered, and key punctuation marks (periods, question marks, semicolons, etc.) are retained as potential sentence identifiers. Unclosed quotation marks (such as """''") or bracketed areas in the text are marked to avoid splitting complete sentences within the quotation marks; then, the work content in the preprocessed employee weekly report file is split using the preset sentence separation logic to obtain multiple short sentences.

[0064] S1013: Perform entity extraction processing on multiple short sentences using a pre-trained model to obtain entities.

[0065] In this embodiment, the data source is the desensitized historical weekly report data within the department, the industry public domain data, and the simulated weekly report in a standard format generated based on the template. The data after the entity boundary is marked using the BIOES annotation method is used to obtain the training data set. The model is trained using the obtained training data set to obtain a pre-trained model. Multiple short sentences are sequentially input into the pre-trained model, and the entities identified from each short sentence are output. Among them, the entities may include but are not limited to progress percentage, manpower input, and task name.

[0066] S1014: Determine the project task data and daily task data corresponding to the employee ID by classifying the entity.

[0067] In this embodiment, the identified entities are classified by a pre-trained model to determine which entities belong to project tasks and which entities belong to daily tasks, and the entities corresponding to project tasks are used as project task data, and the entities corresponding to daily tasks are used as daily task data. For example, tasks containing words such as "project development", "test case", and "review" are classified as project tasks, while words such as "customer consultation", "report submission", and "system upgrade" are classified as daily tasks. If the employee weekly report fails to be parsed (such as the content is vague), the system will put it into the manual review queue for the administrator to assist in processing.

[0068] It is understood that different tasks can be assigned corresponding priorities. For example, priorities include, but are not limited to, "L1, urgent and important," "L2, urgent," "L3, urgent but not important," "L4, not urgent but important," and "L5, not urgent but not important," with L1 being the highest priority. For example, if the "review" task in a project is assigned by a first-level leader and has a short deadline, the task would be marked as L1, indicating an urgent and important task.

[0069] In this embodiment, the employee identification corresponding to the employee weekly report file is determined from the employee weekly report file; the employee weekly report file is sentence-processed to split the employee weekly report file into multiple short sentences; the pre-trained model is used to perform entity extraction processing on the multiple short sentences to obtain entities; by classifying the entities, the project task data and daily task data corresponding to the employee identification are determined, and the key information in the employee weekly report file is automatically extracted and classified, thereby improving the data processing efficiency of the employee weekly report.

[0070] Furthermore, after obtaining the employee ID, the project task data corresponding to the employee ID, and the daily task data, the method may further include:

[0071] Store project task data in a relational database and daily task data in a time series database.

[0072] In this embodiment, the project task data obtained after parsing is stored in a relational database, such as a PostgreSQL database, and records are made of information such as the project ID corresponding to each employee ID, the project file name, the planned completion time corresponding to each project file, and the actual completion time. Specifically, the planned time is the planned completion time of the project file in each project stage according to the pre-set settings of the project establishment; the actual completion time is the completion time of the project file actually completed by the employee corresponding to each employee ID determined by the file judgment entered in the weekly report. The time consumption of the daily task data obtained after parsing is stored in a time series database, such as an InfluxDB database, and the time consumed by employees in handling each daily task is stored according to the timestamp. For example, according to the employee's entry of the company's XX lecture, it is planned to take two weeks, with a start time of June 1 and an end time of June 7. It can be determined that it takes 7 days and the current task progress is 50%.

[0073] S102: Based on the project identifier, the project task data corresponding to the project identifier is aggregated and processed to determine the actual project progress corresponding to the project identifier.

[0074] In this embodiment, taking the project corresponding to project ID 01 as an example, the project file name, the start time and the completion time of the project file are extracted from the project task data, and the actual project progress of the project is obtained after summarizing, including the completion status of each project file in each project stage.

[0075] As a feasible approach, based on the project identifier, the project task data corresponding to the project identifier is aggregated and processed, and the specific implementation steps for determining the actual project progress corresponding to the project identifier include:

[0076] S1021: Extracting multiple task data corresponding to the project identifier from the relational database.

[0077] The task data includes the completed project file identifier and the corresponding completion time.

[0078] In this embodiment, the project file identifier corresponding to the project identifier and the actual completion time of the project file corresponding to the project file identifier are extracted from the relational database; the actual completion time of the project file includes the actual start time and the actual end time.

[0079] S1022: Based on the preset file identifiers corresponding to each project phase and the completion time corresponding to each file identifier, the project file identifiers in the plurality of task data are compared to determine the actual project progress corresponding to the project phase identifier.

[0080] In this embodiment, the preset file identifiers corresponding to each project phase and the completion time corresponding to each file identifier are compared with the project file identifiers in the acquired task data to determine the current project phase, the completed project files, and the actual completion time of each project file. For example, there are 5 project files corresponding to the project establishment phase, 10 project files corresponding to the requirements phase, 20 project files corresponding to the project implementation phase, and 5 project files corresponding to the production phase. If the fifth of the 10 project files with the project file identifier of the requirements phase is obtained, then it is determined that there are 10 completed project files currently in the requirements phase, and the actual completion time of each project file can be extracted from the relational database.

[0081] In this embodiment, multiple task data corresponding to the project identifier are extracted from the relational database; based on the preset file identifier corresponding to each project stage and the completion time corresponding to each file identifier, they are compared with the project file identifiers in the multiple task data to determine the actual project progress corresponding to the completion time project identifier corresponding to each file identifier, which can accurately determine the actual project progress and improve the efficiency and accuracy of project task management.

[0082] S103: Compare the actual project progress corresponding to the project identifier with the planned project progress corresponding to the project identifier to generate a target Gantt chart.

[0083] The target Gantt chart is used to compare the actual project progress and the planned project progress of the target project corresponding to the project identifier, so that managers can perform human resource management.

[0084] As a feasible approach, the actual project progress corresponding to the project ID is compared with the planned project progress corresponding to the project ID. The specific implementation steps for generating a target Gantt chart include:

[0085] S1031: Obtain a project baseline file corresponding to the project identifier, determine the planned time corresponding to each project phase from the project baseline file, and generate a baseline Gantt chart.

[0086] The baseline Gantt chart uses each color in the first color group to represent the planned project progress corresponding to the project identifier at each project stage.

[0087] In this embodiment, in a project baseline file, such as an MS Project plan, different project phases correspond to different project files, and the project files are in order. For example, the project files corresponding to the project establishment phase may include, but are not limited to, project establishment documents and feasibility analysis reports; the project files corresponding to the requirements phase may include, but are not limited to, user requirements documents, functional requirements specifications, and requirements review documents; the project files corresponding to the project implementation phase may include, but are not limited to, overall solution documents, interface documents, and test cases; and the project files corresponding to the production phase may include, but are not limited to, deployment documents and acceptance reports. Based on the file names corresponding to different project phases in the project baseline file and the pre-set planned time, a baseline Gantt chart is generated. In the baseline Gantt chart, the colors in the first color group are used to represent the planned start / end time of each project phase in turn. For example, in the baseline Gantt chart, the project establishment phase is represented by light yellow, the requirements phase is represented by light blue, the project implementation phase is represented by light green, and the production phase is represented by light purple.

[0088] S1032: Using the second color group to represent the actual project progress corresponding to each project stage in the project identifier, and generating a dynamic Gantt chart.

[0089] The colors in the second color group correspond one-to-one to the actual project progress of the project phase.

[0090] In this embodiment, for example, if the completed project file in the actual project progress is a deployment file and is in the production stage, yellow is used to represent it in the project establishment stage, and the actual completion time of the project establishment stage is determined based on the project file corresponding to the project establishment stage; blue is used to represent it in the demand stage, and the actual completion time of the demand stage is determined based on the project file corresponding to the demand stage; green is used to represent it in the project implementation stage, and the actual completion time of the project implementation stage is determined based on the project file corresponding to the project implementation stage; purple is used to represent it in the production stage, and the current project progress is determined based on the actual completion time corresponding to the deployment file in the production stage and other completed project files in the production stage, thereby generating a dynamic Gantt chart to represent the actual project progress.

[0091] S1033: Merge the baseline Gantt chart and the dynamic Gantt chart to obtain a target Gantt chart.

[0092] In this embodiment, the obtained baseline Gantt chart and the dynamic Gantt chart are merged and represented on the same Gantt chart whose abscissa is time, thereby obtaining a target Gantt chart.

[0093] As a practical approach, a target Gantt chart can also display the timeline work allocation and future planned work status of each department employee, allowing managers to adjust work content based on employee status. For example, if a project has completed the first 50% of the project documents, and there are still 50% of the remaining project documents, the unfinished project documents can be listed in order on the target Gantt chart according to the time plan.

[0094] See also Figure 2 , which is a Gantt chart of the project for 2024 provided in the embodiment of this application. Figure 2As shown, the horizontal axis extends from week 1 to week N (shown as week 37 in the figure), with "now" marked as week 28 (red vertical line), representing the current time point. The weekly scale indicates the time span between planned and actual progress. The vertical axis lists multiple project identifiers, each corresponding to a project with two horizontal Gantt charts, showing the progress of each project phase. The top Gantt chart in each horizontal Gantt chart is the baseline Gantt chart for that project, while the bottom Gantt chart is the dynamic Gantt chart for that project. This chart dynamically updates the actual time taken for tasks based on the actual progress synchronized with employee weekly reports. Taking the first set of Gantt charts as an example, the light yellow phase in the baseline Gantt chart represents the project initiation phase, scheduled to run from week 7 to week 10; the light blue phase represents the requirements phase, scheduled to run from week 10 to week 14; the light green phase represents the project implementation phase, scheduled to run from week 14 to week 28; and the light purple phase represents the production phase, scheduled to run from week 26 to week 30. The yellow stage in the dynamic Gantt chart represents the actual project establishment stage, which starts from the 7th week and lasts to about the 11th week; the blue stage represents the actual demand stage, which starts from the 11th week and lasts to the 16th week; the green stage represents the actual project implementation stage, which starts from the 16th week and lasts to the current time point.

[0095] In this embodiment, a project baseline file corresponding to the project identifier is obtained, and the planned time corresponding to each project phase is determined from the project baseline file to generate a baseline Gantt chart; the actual project progress corresponding to each project phase in the project identifier is represented by a second color group to generate a dynamic Gantt chart; the baseline Gantt chart and the dynamic Gantt chart are merged to obtain a target Gantt chart, which can intuitively show the actual progress of the project and the gap between it and the planned progress, so that managers can quickly discover the progress, make timely project schedule arrangements and work allocation adjustments, and improve the efficiency of personnel resource management.

[0096] Furthermore, based on the above embodiment, after obtaining the target Gantt chart, the method may further include:

[0097] Based on the actual project progress and planned project progress corresponding to the target project stage in the target Gantt chart, the progress deviation and performance index corresponding to the target project stage are calculated.

[0098] In this embodiment, the progress deviation and performance index are calculated by comparing the actual project progress corresponding to the current target project stage with the planned project progress preset by the administrator. For example, if the actual project progress corresponding to the current target project stage is 50%, while the planned project progress preset by the administrator is 75%, the progress deviation is 25%; the performance index is then the ratio of the actual project progress to the planned project progress, which is 0.67.

[0099] When it is determined that the progress deviation is greater than the first preset threshold or the performance index is lower than the second preset threshold, risk warning information is generated and sent to the manager.

[0100] In this embodiment, for example, if the progress deviation exceeds the first preset threshold of 20% or the performance index is lower than the second preset threshold of 0.9, a risk warning message is generated and the risk warning message is notified to the administrator via email or in-site message.

[0101] In this embodiment, based on the actual project progress and the planned project progress corresponding to the target project stage in the target Gantt chart, the progress deviation and the performance index corresponding to the target project stage are calculated; when it is determined that the progress deviation is greater than the first preset threshold or the performance index is lower than the second preset threshold, risk warning information is generated and sent to the manager, which can quickly discover abnormal project progress so that the manager can adjust the work arrangements of department employees in a timely manner and improve the management efficiency of human resources.

[0102] S104: Calculate the manpower usage of the project task working hours determined from the project task data and the daily task working hours determined from the daily task data to determine the usage of human resources.

[0103] In this embodiment, for any employee, the employee ID corresponding to the employee is used to extract the actual working hours used in the project tasks corresponding to each project ID from the project task data, and the actual working hours used in daily tasks are extracted from the daily task data to perform manpower utilization statistics, and the manpower utilization statistics results of all employees are summarized to obtain the utilization of human resources.

[0104] As an achievable approach, human resource utilization is calculated based on the project task hours determined from the project task data and the daily task hours determined from the daily task data. Specific implementation steps for determining human resource utilization include:

[0105] S1041: According to the employee ID, determine the project task working hours corresponding to the employee ID from the relational database, and determine the daily task working hours corresponding to the employee ID from the time series database.

[0106] In this embodiment, the corresponding task working hours are extracted from the relational database and the time series database respectively according to the employee ID. For example, it is found from the relational database that employee ID A has invested 5 hours in project ID 01 and 15 hours in project ID 02; it is found from the time series database that employee ID A has invested 10 hours in daily tasks.

[0107] S1042: Determine the actual manpower used corresponding to the employee ID based on the project task working hours and daily task working hours corresponding to the employee ID.

[0108] In this embodiment, the project task hours and daily task hours corresponding to the determined employee ID are added together to obtain the actual manpower usage of the employee corresponding to the employee ID. For example, if the employee invested 5 hours in project ID 01, 15 hours in project ID 02, and 10 hours in daily tasks, the employee's actual manpower usage is 30 hours.

[0109] S1043: Based on the actual manpower used and the preset planned task working hours, determine the workload intensity corresponding to the employee ID.

[0110] In this embodiment, for example, based on the actual manpower usage of 30 hours and the planned task hours of 40 hours preset by the manager, a ratio of 75% of the actual manpower usage to the planned task hours is used as the workload intensity of the employee.

[0111] It should be noted that the preset planned task working hours are set by the manager of the employee's department. For example, if the planned working hours for project ID 01 are set to 10 hours, the planned working hours for project ID 01 are set to 20 hours, and the planned working hours for daily tasks are set to 10 hours, then the employee's planned task working hours will be 40 hours.

[0112] S1044: Generate a human resource view based on the actual manpower usage and workload intensity corresponding to the employee ID; the human resource view is used to represent the usage of human resources corresponding to multiple employee IDs.

[0113] In this embodiment, a human resources view can be generated based on the actual manpower used, planned task hours, and workload intensity corresponding to the employee ID. For example, two thresholds for workload intensity are preset at 80% and 120%. If an employee's workload intensity exceeds 120%, the employee is in an overloaded state; if the employee's workload intensity is between 80% and 120%, the employee is in a normal load state; and if the employee's workload intensity is less than 80%, the employee is in an underloaded state. Different colors are used in the human resources view to represent different load intensities, for example, red represents an overloaded state, green represents an underloaded state, and yellow represents a normal load state.

[0114] As an achievable method, you can click any employee in the human resources view to view the specific work details of the employee.

[0115] See also Figure 3 , which is a human resources view provided by the embodiment of this application. Figure 3As shown in the table, the first column is the employee ID, the second column is the planned manpower utilization, the third column is the actual manpower utilization, the fourth column is the employee workload intensity, the fifth column is the employee status, and the sixth column is the notes. Each row of data in the table represents the employee's manpower utilization. Taking the fifth column as an example, the color of the data intuitively displays the current employee's workload level. Specifically, yellow indicates that the employee is in a normal state of compliance; red indicates that the employee is overloaded; and green indicates that the employee is under a low workload. The donut chart in the upper right corner shows the total manpower distribution. Of the total manpower hours, 210 hours are used for project tasks, 355 hours are used for daily tasks, and 35 hours are idle. The donut chart in the lower right corner shows the employee stress distribution, showing that 5% of employees are overloaded, 20% are in a normal state, and 75% are under a low workload.

[0116] In this embodiment, according to the employee ID, the project task hours corresponding to the employee ID are determined from the relational database, and the daily task hours corresponding to the employee ID are determined from the time series database; based on the project task hours and daily task hours corresponding to the employee ID, the actual manpower used corresponding to the employee ID is determined; based on the actual manpower used and the preset planned task hours, the workload intensity corresponding to the employee ID is determined; based on the actual manpower used and the workload intensity corresponding to the employee ID, a human resources view is generated, which realizes the visualization of human resource usage and improves the efficiency of human resource management.

[0117] In this embodiment, by determining the employee ID, the project task data corresponding to the employee ID, and the daily task data from the employee weekly report file, automatic parsing of the employee weekly report information is achieved, thereby reducing manual summary time and avoiding data duplication errors; then, based on the project ID, the project task data corresponding to the project ID is summarized and processed to determine the actual project progress corresponding to the project ID; and the actual project progress corresponding to the project ID is compared with the planned project progress corresponding to the project ID to generate a target Gantt chart, so that managers can quickly discover progress anomalies based on the target Gantt chart; manpower usage calculation is performed on the project task working hours determined from the project task data and the daily task working hours determined from the daily task data to determine the utilization of human resources, so that managers can adaptively adjust human resource allocation based on the utilization of human resources and deploy human resources in advance to avoid the risk of project delays and reduced efficiency of human resource management.

[0118] See also Figure 4 , which is a schematic diagram of the structure of an enterprise human resources management device provided by an embodiment of the present application. The device 20 includes a data acquisition module 21, a project schedule calculation module 22, a Gantt chart generation module 23, and a human resource utilization calculation module 24.

[0119] Among them, the data acquisition module 21 is used to determine the employee ID, the project task data corresponding to the employee ID, and the daily task data from the employee weekly report file; the project task data includes the project ID and the task data corresponding to the project ID. The project progress calculation module 22 is used to summarize and process the project task data corresponding to the project ID based on the project ID, and determine the actual project progress corresponding to the project ID. The Gantt chart generation module 23 is used to compare the actual project progress corresponding to the project ID with the planned project progress corresponding to the project ID to generate a target Gantt chart; the target Gantt chart is used to compare the actual project progress of the target project corresponding to the project ID with the planned project progress, so that managers can perform human resource management. The human resource utilization calculation module 24 is used to calculate the human resource utilization of the project task working hours determined from the project task data and the daily task working hours determined from the daily task data, and determine the utilization of human resources.

[0120] An enterprise human resources management device provided in an embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0121] Furthermore, based on the above embodiment, the data acquisition module 21 can also be used to store project task data in a relational database and store daily task data in a time series database.

[0122] An enterprise human resources management device provided in an embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0123] Furthermore, based on the above embodiment, the project progress calculation module 22 is specifically used to extract multiple task data corresponding to the project identifier from the relational database; the task data includes the completed project file identifier and the corresponding completion time; based on the preset file identifier corresponding to each project stage and the completion time corresponding to each file identifier, the project file identifier in the multiple task data is compared to determine the actual project progress corresponding to the project identifier.

[0124] An enterprise human resources management device provided in an embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0125] Further, based on the above embodiment, the Gantt chart generation module 23 is specifically used to obtain a project baseline file corresponding to the project identifier, and determine the planned time corresponding to each project stage from the project baseline file to generate a baseline Gantt chart; the baseline Gantt chart uses each color in the first color group to represent the planned project progress corresponding to the project identifier in each project stage; uses the second color group to represent the actual project progress corresponding to each project stage in the project identifier to generate a dynamic Gantt chart; the colors in the second color group have a one-to-one correspondence with the actual project progress of the project stage; and the baseline Gantt chart and the dynamic Gantt chart are merged to obtain a target Gantt chart.

[0126] An enterprise human resources management device provided in an embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0127] Furthermore, based on the above embodiment, the Gantt chart generation module 23 can also be used to calculate the progress deviation and performance index corresponding to the target project stage based on the actual project progress and planned project progress corresponding to the target project stage in the target Gantt chart; when it is determined that the progress deviation is greater than the first preset threshold or the performance index is lower than the second preset threshold, risk warning information is generated and sent to the manager.

[0128] An enterprise human resources management device provided in an embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0129] Furthermore, based on the above embodiment, the manpower utilization calculation module 24 is specifically used to determine the project task hours corresponding to the employee ID from the relational database, and to determine the daily task hours corresponding to the employee ID from the time series database according to the employee ID; based on the project task hours and daily task hours corresponding to the employee ID, determine the actual manpower used corresponding to the employee ID; based on the actual manpower used and the preset planned task hours, determine the workload intensity corresponding to the employee ID; based on the actual manpower used and the preset planned task hours, generate a human resource view based on the actual manpower used and the workload intensity corresponding to the employee ID; the human resource view is used to characterize the usage of human resources corresponding to multiple employee IDs.

[0130] An enterprise human resources management device provided in an embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0131] Furthermore, based on the above embodiment, the data acquisition module 21 is specifically used to determine the employee identification corresponding to the employee weekly report file from the employee weekly report file; perform sentence segmentation processing on the employee weekly report file to split the employee weekly report file into multiple short sentences; use the pre-trained model to perform entity extraction processing on the multiple short sentences to obtain entities; and determine the project task data and daily task data corresponding to the employee identification by classifying the entities.

[0132] An enterprise human resources management device provided in an embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0133] See also Figure 5 , which is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application, including:

[0134] Memory 11, for storing computer programs;

[0135] The processor 12 is configured to implement the steps of a method for managing enterprise human resources as described in any of the above method embodiments when executing the computer program.

[0136] In this embodiment, the device may be a vehicle-mounted computer, a PC (Personal Computer), or a terminal device such as a smart phone, a tablet computer, a PDA, or a portable computer.

[0137] The device may include a memory 11 , a processor 12 , and a bus 13 .

[0138] The memory 11 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 11 can be an internal storage unit of the device, such as the hard disk of the device. In other embodiments, the memory 11 can also be an external storage device of the device, such as a plug-in hard disk equipped on the device, a smart memory card (SmartMedia Card, SMC), a secure digital (Secure Digital, SD) card, a flash card, etc. Furthermore, the memory 11 can also include both an internal storage unit of the device and an external storage device. The memory 11 can not only be used to store application software installed on the device and various types of data, such as program code for executing a method for managing enterprise human resources, but can also be used to temporarily store data that has been output or is about to be output. In some embodiments, the processor 12 can be a central processing unit (CPU).

[0139] In some embodiments, the processor 12 can be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip, used to run the program code stored in the memory 11 or process data, such as the program code for executing the enterprise human resources management method.

[0140] The bus 13 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0141] Furthermore, the device may also include a network interface 14, which may optionally include a wired interface and / or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is generally used to establish a communication connection between the device and other electronic devices.

[0142] Optionally, the device may further include a user interface 15, which may include a display and an input unit such as a keyboard. The optional user interface 15 may also include a standard wired interface or a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen. The display may also be appropriately referred to as a display screen or display unit, and is used to display information processed in the device and to display a visual user interface.

[0143] Figure 5 Only the device with components 11-15 is shown, and it will be understood by those skilled in the art that Figure 5 The structure shown does not constitute a limitation of the device, and may include fewer or more components than shown, or combine certain components, or arrange the components differently.

[0144] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, an embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the enterprise human resources management method as described in any of the above embodiments.

[0145] The computer-readable media of the embodiments of the present application include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0146] The computer instructions stored in the storage medium of the above embodiment are used to enable the computer to execute the enterprise human resources management method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0147] It should be noted that the various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for methods, devices, electronic devices and media, since they are basically similar to the method embodiments, the description is relatively simple. For relevant parts, refer to the partial description of the method embodiments. The methods, devices, electronic devices and media described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components indicated as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement them without expending any creative effort.

[0148] The above is merely one specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for managing enterprise human resources, characterized in that: include: Determine the employee ID, the project task data corresponding to the employee ID, and the daily task data from the employee weekly report file; The project task data includes a project identifier and task data corresponding to the project identifier; Based on the project identifier, the project task data corresponding to the project identifier is aggregated and processed to determine the actual project progress corresponding to the project identifier; Comparing the actual project progress corresponding to the project identifier with the planned project progress corresponding to the project identifier to generate a target Gantt chart; the target Gantt chart is used to compare the actual project progress and the planned project progress of the target project corresponding to the project identifier, so that managers can perform human resource management; A manpower usage calculation is performed on the project task working hours determined from the project task data and the daily task working hours determined from the daily task data to determine the usage of human resources.

2. The method according to claim 1, characterized in that The method further includes: storing the project task data in a relational database, and storing the daily task data in a time series database.

3. The method according to claim 2, characterized in that The step of aggregating and processing the project task data corresponding to the project identifier based on the project identifier to determine the actual project progress corresponding to the project identifier includes: Extracting a plurality of task data corresponding to the project identifier from the relational database; the task data including the completed project file identifier and the corresponding completion time; Based on the preset file identifiers corresponding to each project stage and the completion time corresponding to each file identifier, the project file identifiers in the plurality of task data are compared to determine the actual project progress corresponding to the project identifier.

4. The method according to claim 3, characterized in that The comparing the actual project progress corresponding to the project identifier with the planned project progress corresponding to the project identifier to generate a target Gantt chart includes: Obtaining a project baseline file corresponding to the project identifier, and determining the planned time corresponding to each project phase from the project baseline file to generate a baseline Gantt chart; the baseline Gantt chart uses each color in the first color group to represent the planned project progress corresponding to the project identifier at each project phase; A second color group is used to represent the actual project progress corresponding to each project stage in the project identifier to generate a dynamic Gantt chart; the colors in the second color group correspond one-to-one to the actual project progress of the project stage; The benchmark Gantt chart and the dynamic Gantt chart are merged to obtain a target Gantt chart.

5. The method according to claim 4, characterized in that The method further comprises: Calculate the progress deviation and performance index corresponding to the target project stage based on the actual project progress and the planned project progress corresponding to the target project stage in the target Gantt chart; When it is determined that the progress deviation is greater than a first preset threshold or the performance index is lower than a second preset threshold, risk warning information is generated and sent to a manager.

6. The method according to claim 2, characterized in that The performing of manpower usage calculation on the project task working hours determined from the project task data and the daily task working hours determined from the daily task data to determine the usage of human resources includes: According to the employee ID, determining the project task working hours corresponding to the employee ID from the relational database, and determining the daily task working hours corresponding to the employee ID from the time series database; Determining the actual manpower used corresponding to the employee ID based on the project task working hours and daily task working hours corresponding to the employee ID; Determining the workload intensity corresponding to the employee identifier based on the actual manpower used and the preset planned task hours; A human resource view is generated based on the actual manpower usage and workload intensity corresponding to the employee identification; the human resource view is used to represent the usage of human resources corresponding to each of the multiple employee identifications.

7. The method according to claim 1, characterized in that Determining the employee ID, the project task data corresponding to the employee ID, and the daily task data from the employee weekly report file includes: Determining the employee identifier corresponding to the employee weekly report file from the employee weekly report file; Perform sentence segmentation processing on the employee weekly report file, dividing the employee weekly report file into multiple short sentences; Performing entity extraction processing on the multiple short sentences using a pre-trained model to obtain entities; By classifying the entities, the project task data and daily task data corresponding to the employee identification are determined.

8. A management device for enterprise human resources, characterized in that: include: A data acquisition module is used to determine the employee ID, the project task data corresponding to the employee ID, and the daily task data from the employee weekly report file; The project task data includes a project identifier and task data corresponding to the project identifier; A project progress calculation module is used to aggregate and process the project task data corresponding to the project identifier based on the project identifier to determine the actual project progress corresponding to the project identifier; A Gantt chart generation module is used to compare the actual project progress corresponding to the project identifier with the planned project progress corresponding to the project identifier to generate a target Gantt chart; the target Gantt chart is used to compare the actual project progress and the planned project progress of the target project corresponding to the project identifier, so that managers can perform human resource management; The manpower utilization calculation module is used to perform manpower utilization calculation on the project task working hours determined from the project task data and the daily task working hours determined from the daily task data to determine the utilization of human resources.

9. An electronic device, characterized in that: The device includes: a processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

Images