WO2019223152A1 - 任务派工方法、服务器及计算机可读存储介质 - Google Patents
任务派工方法、服务器及计算机可读存储介质 Download PDFInfo
- Publication number
- WO2019223152A1 WO2019223152A1 PCT/CN2018/102404 CN2018102404W WO2019223152A1 WO 2019223152 A1 WO2019223152 A1 WO 2019223152A1 CN 2018102404 W CN2018102404 W CN 2018102404W WO 2019223152 A1 WO2019223152 A1 WO 2019223152A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- monthly
- team
- working
- day
- workload
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
Definitions
- the present application relates to the field of data processing technology, and in particular, to a task dispatch method, a server, and a computer-readable storage medium.
- the working day setting of each department of the existing company is basically a unified holiday arrangement, which lacks a humanized arrangement and cannot meet the work arrangements of different teams.
- Property insurance customer resources are assigned on a monthly basis to make phone sales calls.
- Organizations need to customize the first dial time, workday time, and workday's workload ratio in the cycle. Dialing cadences in different regions and months need to be differentiated, and you need to customize the dialing cycle.
- this application proposes a task dispatching method, a server, and a computer-readable storage medium, which can enable each team to flexibly adjust the work arrangement according to its own workload, and the workload distribution is more flexible and intelligent.
- the server includes a memory and a processor.
- the memory stores a task dispatch system that can run on the processor.
- the task dispatch system is When the processor executes, the following steps are implemented:
- the present application further provides a task dispatch method, which is applied to a server, and the method includes:
- the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores a task dispatch system, and the task dispatch system can be executed by at least one processor so that The at least one processor executes the steps of the task dispatch method as described above.
- FIG. 1 is a schematic diagram of an optional hardware architecture of a server of the present application
- FIG. 2 is a schematic diagram of a program module of the first embodiment of the task dispatch system of the present application
- FIG. 3 is a schematic diagram of a program module of a second embodiment of the task dispatch system of the present application.
- FIG. 5 is a schematic flowchart of implementation of a second embodiment of a task dispatch method of the present application.
- FIG. 1 is a schematic diagram of an optional hardware architecture of the server 2 of the present application.
- the server 2 may include, but is not limited to, a memory 11, a processor 12, and a network interface 13 which may communicate with each other through a system bus. It should be noted that FIG. 2 only shows the server 2 with components 11-13, but it should be understood that it is not required to implement all the illustrated components, and more or fewer components may be implemented instead.
- the server 2 may be a computing device such as a rack server, a blade server, a tower server, or a rack server.
- the server 2 may be an independent server or a server cluster composed of multiple servers.
- the memory 11 includes at least one type of readable storage medium.
- the readable storage medium includes a flash memory, a hard disk, a multimedia card, a card-type memory (for example, SD or DX memory, etc.), a random access memory (RAM), and a static memory.
- the memory 11 may be an internal storage unit of the server 2, such as a hard disk or a memory of the server 2.
- the memory 11 may also be an external storage device of the server 2, such as a plug-in hard disk, a smart memory card (SMC), and a secure digital (Secure) Digital, SD) card, Flash card, etc.
- the memory 11 may also include both an internal storage unit of the server 2 and an external storage device thereof.
- the memory 11 is generally used to store an operating system and various application software installed on the server 2, such as program codes of the task dispatch system 100.
- the memory 11 may also be used to temporarily store various types of data that have been output or will be output.
- the processor 12 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or another data processing chip.
- the processor 12 is generally used to control the overall operation of the server 2.
- the processor 12 is configured to run program code or process data stored in the memory 11, for example, to run the task dispatch system 100 and the like.
- the network interface 13 may include a wireless network interface or a wired network interface.
- the network interface 13 is generally used to establish a communication connection between the server 2 and other electronic devices.
- the present application proposes a task dispatch system 100.
- FIG. 2 it is a program module diagram of the first embodiment of the task dispatch system 100 of the present application.
- the task dispatching system 100 includes a series of computer program instructions stored in the memory 11. When the computer program instructions are executed by the processor 12, the task dispatching operations of the embodiments of the present application can be implemented. . In some embodiments, the task dispatching system 100 may be divided into one or more modules based on specific operations implemented by various portions of the computer program instructions. For example, in FIG. 2, the task dispatching system 100 may be divided into a setting module 101, a first calculation module 102, a second calculation module 103, and a dispatch module 104. among them:
- the setting module 101 is configured to set a monthly workday and a daily workload ratio of a team according to a preset date strategy and a monthly workload of the team.
- the initial monthly working day can be set according to the national annual holiday arrangement.
- statutory holidays and weekends can be set to rest days by default, and the base number of working days per month can be set to 20 days.
- Different regions and different teams may have different said preset date policies, and workdays and rest days may be freely set and adjusted according to the actual needs of the team.
- a team's rest day can be the default legal rest day and a selected rest day.
- the selected rest day may be any selected date, and may be selected by the team according to their own needs when formulating the preset date strategy. Intermediation within each team can be set to a selected day off. Days that are not set as rest days are treated as team workdays.
- the team month working days and month rest days set by the setting module 101 need to be greater than the base rest days and the base month working days, so as to avoid setting too many or too few days for the month working days. For example, if the baseline number of working days per month is 20 days, the monthly workload of the team corresponding to the 20 days is quantity A. The number of working days set by the setting module 101 should be greater than 20 days. If the monthly workload of the team in January is less than A, the monthly workday of the month is 20 days.
- the monthly workday of the team calculated by the formula is preferably a positive integer. If the calculated data is a decimal number, the calculation result is automatically incremented by one.
- the first preset number of working days is added to the base month's working day. If the monthly workload of the team is less than the annual average monthly workload, The second preset number of working days is added to the base month working day. The first preset number of days is greater than the second preset number of days. You can set the daily workload ratio for each working day. The default daily workload ratio is 100%. Due to the upper limit of the number of days in a monthly working day, when the monthly workload is large, the daily workload ratio can be adjusted according to the actual monthly workload to be completed. If the monthly workload of the team is heavy, the proportion of the daily workload can be appropriately increased (for example, adjusted to 110%).
- the proportion of the daily workload can be appropriately reduced to (For example, adjusted to 95%).
- the base number of monthly workdays is 20 days
- the corresponding monthly workload of the team for the 20 days is quantity A
- the corresponding daily workload is 100%.
- the team's monthly workday limit in March is 25 Days
- the workload in March is quantity C
- quantity C is calculated by the above-mentioned monthly workday formula.
- the calculation result is greater than 25 days.
- the first calculation module 102 is configured to calculate a monthly planned amount of each of the employees according to the monthly workload of the team and the number of employees of the team.
- the first calculation module 102 is further configured to calculate an expected manpower of the team according to the number of employees of the team, the monthly work day of the team, and the daily workload ratio.
- the first calculation module 102 is further configured to determine whether the calculated ratio of the expected manpower of the team to the current number of employees of the team is greater than a preset ratio; if the expected manpower of the team is With the current number of employees of the team being greater than the preset ratio, the first calculation module 102 controls a display unit (not shown) to output warning information that the task is overloaded with a dispatch task.
- the second calculation module 103 is configured to calculate a daily planned amount of each of the employees according to a remaining monthly planned amount, a monthly remaining working day, and a proportion of the daily working amount of each of the employees.
- the dispatching module 104 is configured to assign a corresponding number of work tasks to each of the employees according to the calculated daily planning amount of each of the employees.
- the assignment module 104 assigns 13 work tasks to the employee.
- the task dispatching system 100 includes a series of computer program instructions stored in the memory 11.
- the task dispatching operations of the embodiments of the present application can be implemented.
- the task dispatching system 100 may be divided into one or more modules based on specific operations implemented by various portions of the computer program instructions.
- the task dispatching system 100 may be divided into a setting module 101, a first calculation module 102, a second calculation module 103, a dispatch module 104, and an association module 105.
- Each of the program modules 101-104 is the same as the first embodiment of the task dispatch system 100 of the present application, and an association module 105 is added on this basis. among them:
- the setting module 101 is configured to set a monthly workday and a daily workload ratio of a team according to a preset date strategy and a monthly workload of the team.
- the initial monthly working day can be set according to the national annual holiday arrangement.
- statutory holidays and weekends can be set to rest days by default, and the base number of working days per month can be set to 20 days.
- Different regions and different teams may have different said preset date policies, and workdays and rest days may be freely set and adjusted according to the actual needs of the team.
- a team's rest day can be the default legal rest day and a selected rest day.
- the selected rest day may be any selected date, and may be selected by the team according to their own needs when formulating the preset date strategy. Intermediation within each team can be set to a selected day off. Days that are not set as rest days are treated as team workdays.
- the team month working days and month rest days set by the setting module 101 need to be greater than the base rest days and the base month working days, so as to avoid setting too many or too few days for the month working days. For example, if the baseline number of working days per month is 20 days, the monthly workload of the team corresponding to the 20 days is quantity A. The number of working days set by the setting module 101 should be greater than 20 days. If the monthly workload of the team in January is less than A, the monthly workday of the month is 20 days.
- the monthly workday of the team calculated by the formula is preferably a positive integer. If the calculated data is a decimal number, the calculation result is automatically incremented by one.
- the first preset number of working days is added to the base month's working day. If the monthly workload of the team is less than the annual average monthly workload, The second preset number of working days is added to the base month working day. The first preset number of days is greater than the second preset number of days. You can set the daily workload ratio for each working day. The default daily workload ratio is 100%. Due to the upper limit of the number of days on a monthly working day, when the monthly workload is large, the daily workload ratio can be adjusted according to the actual monthly workload to be completed. If the monthly workload of the team is heavy, the proportion of the daily workload can be appropriately increased (for example, adjusted to 110%).
- the proportion of the daily workload can be appropriately reduced to (For example, adjusted to 95%).
- the base number of working days for a month is 20 days
- the corresponding monthly workload of the team for the 20 days is quantity A
- the corresponding daily workload is 100%.
- the team's monthly working day limit in March is 25 Days
- the workload in March is quantity C
- quantity C is calculated by the above-mentioned monthly workday formula. The calculation result is greater than 25 days.
- the first calculation module 102 is configured to calculate a monthly planned amount of each of the employees according to the monthly workload of the team and the number of employees of the team.
- the first calculation module 102 is further configured to calculate an expected manpower of the team according to the number of employees of the team, the monthly work day of the team, and the daily workload ratio.
- the first calculation module 102 is further configured to determine whether the calculated ratio of the expected manpower of the team to the current number of employees of the team is greater than a preset ratio; if the expected manpower of the team is With the current number of employees of the team being greater than the preset ratio, the first calculation module 102 controls a display unit (not shown) to output warning information that the task is overloaded with a dispatch task.
- the second calculation module 103 is configured to obtain a remaining monthly planned amount and a monthly remaining working day of each of the employees, and calculate the remaining monthly planned amount, the monthly remaining working day, and the daily working amount of each of the employees. The ratio is calculated for each employee of the day.
- the dispatching module 104 is configured to assign a corresponding number of work tasks to each of the employees according to the calculated daily planning amount of each of the employees.
- the assignment module 104 assigns 13 work tasks to the employee.
- the association module 105 is configured to determine whether a date is a work day according to the monthly work day of the team, and to associate a work log for the work day when the date is determined to be a work day, and generate the work log according to the status of the work log. Weekday mark.
- the work log includes progress information of a currently assigned work task.
- a certain date is a working day
- employees are likely to need to record schedules, set event reminders, and so on.
- the work log can be edited and recorded by employees.
- two working logs can be associated with one working day, and the two working logs record the morning schedule and the afternoon schedule, respectively.
- a first working day mark may be generated; when the status of the work log is filled, a second work day mark may be generated.
- a first working day mark and a second working day mark are marked on that date. If the work log user who records the afternoon schedule is filled, it means that the status of the work log is updated, and the work day mark also needs to be updated, that is, the work day mark needs to be regenerated and added according to the updated status of the work log.
- the task dispatch system 100 proposed in the present application firstly sets the monthly workday and daily workload ratio of the team according to the preset date strategy and the monthly workload of the team; secondly, according to the description
- the monthly workload of the team and the number of employees of the team are used to calculate the monthly planned amount of each of the employees; further, the remaining monthly planned amount of each of the employees and the remaining working days of the month are obtained, and according to each of the employees
- the working day of each month determines whether a date is a working day, and when the
- the job log includes information about the current progress of the work assigned to the task. In this way, you can set personalized working days according to the needs of different regions and different teams, calculate the human input and schedule the employees' work according to the task amount of the team in advance, and automatically calculate the task plan amount of the month according to the setting of the working day. And the amount of work tasks that should be dispatched on the day, it can also automatically associate the work log of each employee according to the work day.
- this application also proposes a method of task dispatch.
- FIG. 4 is a schematic diagram of an implementation process of a first embodiment of a task dispatch method of the present application.
- the execution order of the steps in the flowchart shown in FIG. 4 may be changed, and some steps may be omitted.
- step S400 the monthly workday and the daily workload of the team are set according to the preset date strategy and the monthly workload of the team.
- the initial monthly working day can be set according to the national annual holiday arrangement.
- statutory holidays and weekends can be set to rest days by default, and the base number of working days per month can be set to 20 days.
- Different regions and different teams may have different said preset date policies, and workdays and rest days may be freely set and adjusted according to the actual needs of the team.
- a team's rest day can be the default legal rest day and a selected rest day.
- the selected rest day may be any selected date, and may be selected by the team according to their own needs when formulating the preset date strategy. Intermediation within each team can be set to a selected day off. Days that are not set as rest days are treated as team workdays.
- the set team month working days and month rest days must be greater than the benchmark rest day.
- the number of days and the number of working days in the base month so as to avoid setting too many or too few days for the monthly working days. For example, if the baseline number of working days per month is 20 days, the monthly workload of the team corresponding to the 20 days is quantity A. The number of working days in the month should be greater than 20 days. If the monthly workload of the team in January is less than A, the monthly workday of the month is 20 days.
- the monthly workday of the team calculated by the formula is preferably a positive integer. If the calculated data is a decimal number, the calculation result is automatically incremented by one.
- the first preset number of working days is added to the base month's working day. If the monthly workload of the team is less than the annual average monthly workload, The second preset number of working days is added to the base month working day. The first preset number of days is greater than the second preset number of days. You can set the daily workload ratio for each working day. The default daily workload ratio is 100%. Due to the upper limit of the number of days in a monthly working day, when the monthly workload is large, the daily workload ratio can be adjusted according to the actual monthly workload to be completed. If the monthly workload of the team is heavy, the proportion of the daily workload can be appropriately increased (for example, adjusted to 110%).
- the proportion of the daily workload can be appropriately reduced to (For example, adjusted to 95%).
- the base number of monthly workdays is 20 days
- the corresponding monthly workload of the team for the 20 days is quantity A
- the corresponding daily workload is 100%.
- the team's monthly workday limit in March is 25 Days
- the workload in March is quantity C
- quantity C is calculated by the above-mentioned monthly workday formula.
- the calculation result is greater than 25 days.
- step S402 a monthly planned amount of each of the employees is calculated according to the monthly workload of the team and the number of employees of the team.
- the expected manpower of the team may also be calculated according to the number of employees of the team, the monthly work day of the team, and the proportion of the daily work.
- a warning message that the work dispatch task is overloaded will be generated and output.
- Step S404 Calculate the daily planned amount of each employee according to the remaining monthly planned amount of each employee, the monthly remaining working days, and the proportion of the daily working amount.
- Step S406 Assign a corresponding number of work tasks to each of the employees according to the calculated daily planning amount of each of the employees.
- the task dispatch method proposed in the present application firstly sets the monthly workday and daily workload ratio of the team according to the preset date strategy and the monthly workload of the team; secondly, according to the team month
- the workload and the number of employees of the team calculate the monthly planned amount of each of the employees; further, the remaining monthly planned amount of each of the employees and the remaining working days of the month are obtained, and according to the remaining months of each of the employees
- FIG. 5 is a schematic diagram of an implementation process of a second embodiment of a task dispatch method of the present application.
- the execution order of the steps in the flowchart shown in FIG. 5 may be changed, and some steps may be omitted.
- step S400 the monthly workday and the daily workload of the team are set according to the preset date strategy and the monthly workload of the team.
- the initial monthly working day can be set according to the national annual holiday arrangement.
- statutory holidays and weekends can be set to rest days by default, and the base number of working days per month can be set to 20 days.
- Different regions and different teams may have different said preset date strategies, and workdays and rest days may be freely set and adjusted according to the actual needs of the team.
- a team's rest day can be the default legal rest day and a selected rest day.
- the selected rest day may be any selected date, and may be selected by the team according to their own needs when formulating the preset date strategy. Intermediation within each team can be set to a selected day off. Days that are not set as rest days are treated as team workdays.
- the set team month working days and month rest days must be greater than the benchmark rest day.
- the number of days and the number of working days in the base month so as to avoid setting too many or too few days for the monthly working days. For example, if the baseline number of working days per month is 20 days, the monthly workload of the team corresponding to the 20 days is quantity A. The number of working days in the month should be greater than 20 days. If the monthly workload of the team in January is less than A, the monthly workday of the month is 20 days.
- the monthly workday of the team calculated by the formula is preferably a positive integer. If the calculated data is a decimal number, the calculation result is automatically incremented by one.
- the first preset number of working days is added to the base month's working day. If the monthly workload of the team is less than the annual average monthly workload, The second preset number of working days is added to the base month working day. The first preset number of days is greater than the second preset number of days. You can set the daily workload ratio for each working day. The default daily workload ratio is 100%. Because the number of days of a monthly working day has an upper limit, when the monthly workload is large, the daily workload ratio can be adjusted according to the actual monthly workload to be completed. If the monthly workload of the team is heavy, the proportion of the daily workload can be appropriately increased (for example, adjusted to 110%).
- the proportion of the daily workload can be appropriately reduced to (For example, adjusted to 95%).
- the base number of monthly workdays is 20 days
- the corresponding monthly workload of the team for the 20 days is quantity A
- the corresponding daily workload is 100%.
- the team's monthly workday limit in March is 25 Days
- the workload in March is quantity C
- quantity C is calculated by the above-mentioned monthly workday formula.
- the calculation result is greater than 25 days.
- step S402 a monthly planned amount of each of the employees is calculated according to the monthly workload of the team and the number of employees of the team.
- the expected manpower of the team may also be calculated according to the number of employees of the team, the monthly work day of the team, and the proportion of the daily work.
- a warning message that the work dispatch task is overloaded will be generated and output.
- Step S404 Obtain the remaining monthly planned amount and monthly remaining working days of each of the employees, and calculate each described according to the remaining monthly planned amount, monthly remaining working days, and the proportion of the daily working amount of each of the employees. Employee's plan for the day.
- Step S406 Assign a corresponding number of work tasks to each of the employees according to the calculated daily planning amount of each of the employees.
- Step S408 Determine whether a date is a working day according to the monthly working day of the team, and associate a working log for the working day when the date is determined to be a working day, and generate a working day mark according to the status of the working log.
- the work log includes progress information of a currently assigned work task.
- a certain date is a working day
- employees are likely to need to record schedules, set event reminders, and so on.
- the work log can be edited and recorded by employees.
- two working logs can be associated with one working day, and the two working logs record the morning schedule and the afternoon schedule, respectively.
- a first working day mark may be generated; when the status of the work log is filled, a second work day mark may be generated.
- a first working day mark and a second working day mark are marked on that date. If the work log user who records the afternoon schedule is filled, it means that the status of the work log is updated, and the work day mark also needs to be updated, that is, the work day mark needs to be regenerated and added according to the updated status of the work log.
- the task dispatching method proposed in this application firstly sets the monthly workday and daily workload ratio of the team according to the preset date strategy and the monthly workload of the team; secondly, according to the team month
- the workload and the number of employees of the team calculate the monthly planned amount of each of the employees; further, the remaining monthly planned amount of each of the employees and the remaining working days of the month are obtained, and according to the remaining months of each of the employees
- a corresponding number of work tasks are assigned to each of the employees according to the calculated daily planning amount of each said employee; finally, according to the monthly work of the team Day to determine whether a date is a working day, and when the date is determined to be a
- the methods in the above embodiments can be implemented by means of software plus a necessary universal hardware platform, and of course, also by hardware, but in many cases the former is better.
- Implementation Based on such an understanding, the technical solution of this application that is essentially or contributes to the existing technology can be embodied in the form of a software product that is stored in a storage medium (such as ROM / RAM, magnetic disk, The optical disc) includes several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the embodiments of the present application.
- a terminal device which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Operations Research (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Educational Administration (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
本申请公开了一种任务派工方法,包括:根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比;根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量;获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量;及根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。本申请还提供一种服务器及计算机可读存储介质。本申请提供的任务派工方法、服务器及计算机可读存储介质可根据工作日的设置自动计算当月任务计划量及当日应派发的工作任务量。
Description
本申请要求于2018年5月23日提交中国专利局,申请号为201810501878.1、发明名称为“任务派工方法、服务器及计算机可读存储介质”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及数据处理技术领域,尤其涉及任务派工方法、服务器及计算机可读存储介质。
现有公司的各部门的工作日设定基本是统一的节假日安排,缺乏人性化安排,无法满足不同团队的工作安排。产险客户资源的派工数量按月为周期进行分派,以进行电话销售拨打,各机构需要自定义周期内的首拨时间、工作日时间、工作日的工作量占比。不同区域、不同月份的拨打节奏需有所区分,需要自定义拨打周期。
发明内容
有鉴于此,本申请提出一种任务派工方法、服务器及计算机可读存储介质,可以实现各团队根据自身工作量灵活调整工作安排,工作量分配更灵活、智能化。
首先,为实现上述目的,本申请提出一种服务器,所述服务器包括存储器、处理器,所述存储器上存储有可在所述处理器上运行的任务派工***,所述任务派工***被所述处理器执行时实现如下步骤:
根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比;
根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量;
获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量,其中,所述当日计划量通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比);及
根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。
此外,为实现上述目的,本申请还提供一种任务派工方法,应用于服务器,所述方法包括:
根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比;
根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计 划量;
获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量,其中,所述当日计划量通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比);及
根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。
进一步地,为实现上述目的,本申请还提供一种计算机可读存储介质,所述计算机可读存储介质存储有任务派工***,所述任务派工***可被至少一个处理器执行,以使所述至少一个处理器执行如上述任务派工方法的步骤。
图1是本申请服务器一可选的硬件架构的示意图;
图2是本申请任务派工***第一实施例的程序模块示意图;
图3是本申请任务派工***第二实施例的程序模块示意图;
图4为本申请任务派工方法第一实施例的实施流程示意图;
图5为本申请任务派工方法第二实施例的实施流程示意图。
附图标记:
服务器 | 2 |
存储器 | 11 |
处理器 | 12 |
网络接口 | 13 |
任务派工*** | 100 |
设定模块 | 101 |
第一计算模块 | 102 |
第二计算模块 | 103 |
分派模块 | 104 |
关联模块 | 105 |
本申请目的的实现、功能特点及优点将结合实施例,参照附图做进一步说明。
为了使本申请的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本申请进行进一步详细说明。应当理解,此处所描述的具体实施例仅用以解释本申请,并不用于限定本申请。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
需要说明的是,在本申请中涉及“第一”、“第二”等的描述仅用于描述目的,而不能理解为指示或暗示其相对重要性或者隐含指明所指示的技术特征的数量。由此,限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。另外,各个实施例之间的技术方案可以相互结合,但是必须是以本领域普通技术人员能够实现为基础,当技术方案的结合出现相互矛盾或无法实现时应当认为这种技术方案的结合不存在,也不在本申请要求的保护范围之内。
参阅图1所示,是本申请服务器2一可选的硬件架构的示意图。
本实施例中,所述服务器2可包括,但不仅限于,可通过***总线相互通信连接存储器11、处理器12、网络接口13。需要指出的是,图2仅示出了具有组件11-13的服务器2,但是应理解的是,并不要求实施所有示出的组件,可以替代的实施更多或者更少的组件。
其中,所述服务器2可以是机架式服务器、刀片式服务器、塔式服务器或机柜式服务器等计算设备,该服务器2可以是独立的服务器,也可以是多个服务器所组成的服务器集群。
所述存储器11至少包括一种类型的可读存储介质,所述可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如,SD或DX存储器等)、随机访问存储器(RAM)、静态随机访问存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁性存储器、磁盘、光盘等。在一些实施例中,所述存储器11可以是所述服务器2的内部存储单元,例如该服务器2的硬盘或内存。在另一些实施例中,所述存储器11也可以是所述服务器2的外部存储设备,例如该服务器2上配备的插接式硬盘,智能存储卡(Smart Media Card,SMC),安全数字(Secure Digital,SD)卡,闪存卡(Flash Card)等。当然,所述存储器11还可以既包括所述服务器2的内部存储单元也包括其外部存储设备。本实施例中,所述存储器11通常用于存储安装于所述服务器2的操作***和各类应用软件,例如任务派工***100的程序代码等。此外,所述存储器11还可以用于暂时地存储已经输出或者将要输出的各类数据。
所述处理器12在一些实施例中可以是中央处理器(Central Processing Unit,CPU)、控制器、微控制器、微处理器、或其他数据处理芯片。该处理器12通常用于控制所述服务器2的总体操作。本实施例中,所述处理器12用于运行所述存储器11中存储的程序代码或者处理数据,例如运行所述的任务派工***100等。
所述网络接口13可包括无线网络接口或有线网络接口,该网络接口13通常用于在所述服务器2与其他电子设备之间建立通信连接。
至此,己经详细介绍了本申请相关设备的硬件结构和功能。下面,将基于上述介绍提出本申请的各个实施例。
首先,本申请提出一种任务派工***100。
参阅图2所示,是本申请任务派工***100第一实施例的程序模块图。
本实施例中,所述任务派工***100包括一系列的存储于存储器11上的计算机程序指令,当该计算机程序指令被处理器12执行时,可以实现本申请各实施例的任务派工操作。在一些实施例中,基于该计算机程序指令各部分所实现的特定的操作,任务派工***100可以被划分为一个或多个模块。例如,在图2中,任务派工***100可以被分割成设定模块101、第一计算模块102、第二计算模块103及分派模块104。其中:
所述设定模块101用于根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比。
在一实施例中,初始的月工作日可以根据国家年度放假安排进行设置。例如法定节假日、周末可以被默认设置为休息日,每月工作日的基准天数可以设置为20天。不同区域、不同团队可制定有不同的所述预设日期策略,可以根据团队的实际需求通过所述预设日期策略对工作日和休息日进行自由的设定和调整。团队的休息日可以是默认的法定休息日和选定休息日。所述选定休息日可以是任意被选定的日期,可由团队在制定所述预设日期策略的时候,根据自身需求自行选定。各团队内部的调休可以被设定成选定休息日。未被设定为休息日的日期,即被作为团队的工作日。通过所述预设日期策略可以明确了解哪些日期为所述工作日,哪些日期为所述休息日,并可进行实时调整。所述设定模块101设定的团队月工作日及月休息日均需大于基准休息日天数和基准月工作日天数,从而避免月工作日的天数设定太多或者太少。举例而言,若每月工作日的基准天数为20天,该20天对应的团队月工作量为数量A。所述设定模块101设定的月工作日天数应大于20天。若团队一月份的月工作量小于A,则该月的月工作日为20天。若团队三月份的工作量为B且B>A,所述设定模块101设定的团队的月工作日可以通过以下公式计算得到:团队的月工作日=B*A/20;其中,该公式计算得到的团队的月工作日优选为正整数,若计算得到数据是小数,则计算结果自动加1。
在一实施方式中,若团队的月工作量大于年度月平均工作量,则在基准月工作日基础上增加第一预设天数的工作日,若团队的月工作量小于年度月平均工作量,则在基准月工作日基础上增加第二预设天数的工作日。所述第一预设天数大于所述第二预设天数。每个工作日都可以设置日工作量占比,默认的日工作量占比为100%。由于月工作日的天数具有上限,当月工作量较大时,可以根据实际需要完成的月工作量进行日工作量占比调整。若团队月工作量较重时,可以适当调高所述日工作量占比为(例如调整为110%),若团队月工作量较轻时,可以适当调低所述日工作量占比为(例如调整为95%)。 举例而言,月工作日的基准天数为20天,该20天对应的团队月工作量为数量A,对应的日工作量占比为100%,若该团队三月份的月工作日上限为25天,三月份的的工作量为数量C,且数量C通过上述的月工作日公式计算得到的计算结果大于25天,需要调整日工作量占比大于100%才可能在25天完成任务,此时日工作量占比可以通过以下公式计算得到:日工作量占比=20*C/A*25。
所述第一计算模块102用于根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量。
在一实施方式中,所述第一计算模块102还用于根据所述团队的员工数量、所述团队的月工作日及所述日工作量占比计算所述团队的预期人力。
在一实施方式中,所述团队月工作量可以通过以下公式计算得到:团队月工作量=***月总工作量*(团队当前人力/***总人力)。每一所述员工的月计划量可以通过以下公式计算得到:员工的月计划量=团队月工作量/团队当前人力。所述团队的预期人力可以通过以下公式计算得到:团队预期人力=团队当前人力*SUM(工作日*日工作量占比)/工作日天数。举例而言,***上传月总任务量为1万份,团队人力为10人,部门总人力为40人,月工作日为20天,20天中每天对应的工作量占比为110%、110%、120%、100%、110%、120%、110%、110%、120%、100%,110%、110%、120%、100%、110%、120%、110%、110%、120%、100%,则团队月工作量=[10000*(10/40)]=2500份,员工月计划量=2500/10=250份,团队预期人力
=10*[(110%+110%+120%+100%+110%+120%+110%+110%+120%+100%+110%+110%+120%+100%+110%+120%+110%+110%+120%+100%)/20]。
在一实施方式中,所述第一计算模块102还用于判断计算得到的所述团队的预期人力与所述团队的当前员工数量的比值是否大于一预设比值;若所述团队的预期人力与所述团队的当前员工数量大于所述预设比值,所述第一计算模块102控制一显示单元(图未示)输出以一派工任务超负荷的警示信息。
所述第二计算模块103用于根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量。
在一实施方式中,所述员工的当日计划量可以通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比)。
所述分派模块104用于根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。
举例而言,若所述第二计算模块103计算一员工的当日计划量为13份,则所述分派模块104分派13份的工作任务至该员工。
通过上述程序模块101-104,本申请所提出的任务派工***100,首先,根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比;其次,根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量;再者,获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所 述员工的当日计划量,其中,所述当日计划量通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比);最后,根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。这样,可以实现根据不同区域、不同团队的需求设定个性化的工作日,提前根据团队的任务量计算人力的投入并进行员工的工作安排,且可根据工作日的设置自动计算当月任务计划量及当日应派发的工作任务量,还可根据工作日自动关联每一员工的工作日志。
参阅图3所示,是本申请任务派工***100第二实施例的程序模块图。本实施例中,所述任务派工***100包括一系列的存储于存储器11上的计算机程序指令,当该计算机程序指令被处理器12执行时,可以实现本申请各实施例的任务派工操作。在一些实施例中,基于该计算机程序指令各部分所实现的特定的操作,任务派工***100可以被划分为一个或多个模块。例如,在图3中,任务派工***100可以被分割成设定模块101、第一计算模块102、第二计算模块103、分派模块104及关联模块105。所述各程序模块101-104与本申请任务派工***100第一实施例相同,并在此基础上增加关联模块105。其中:
所述设定模块101用于根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比。
在一实施例中,初始的月工作日可以根据国家年度放假安排进行设置。例如法定节假日、周末可以被默认设置为休息日,每月工作日的基准天数可以设置为20天。不同区域、不同团队可制定有不同的所述预设日期策略,可以根据团队的实际需求通过所述预设日期策略对工作日和休息日进行自由的设定和调整。团队的休息日可以是默认的法定休息日和选定休息日。所述选定休息日可以是任意被选定的日期,可由团队在制定所述预设日期策略的时候,根据自身需求自行选定。各团队内部的调休可以被设定成选定休息日。未被设定为休息日的日期,即被作为团队的工作日。通过所述预设日期策略可以明确了解哪些日期为所述工作日,哪些日期为所述休息日,并可进行实时调整。所述设定模块101设定的团队月工作日及月休息日均需大于基准休息日天数和基准月工作日天数,从而避免月工作日的天数设定太多或者太少。举例而言,若每月工作日的基准天数为20天,该20天对应的团队月工作量为数量A。所述设定模块101设定的月工作日天数应大于20天。若团队一月份的月工作量小于A,则该月的月工作日为20天。若团队三月份的工作量为B且B>A,所述设定模块101设定的团队的月工作日可以通过以下公式计算得到:团队的月工作日=B*A/20;其中,该公式计算得到的团队的月工作日优选为正整数,若计算得到数据是小数,则计算结果自动加1。
在一实施方式中,若团队的月工作量大于年度月平均工作量,则在基准月工作日基础上增加第一预设天数的工作日,若团队的月工作量小于年度月平均工作量,则在基准月工作日基础上增加第二预设天数的工作日。所述第一预设天数大于所述第二预设天数。每个工作日都可以设置日工作量占比,默认的日工作量占比为100%。由于月工作日的天数具有一上限值,当月工作 量较大时,可以根据实际需要完成的月工作量进行日工作量占比调整。若团队月工作量较重时,可以适当调高所述日工作量占比为(例如调整为110%),若团队月工作量较轻时,可以适当调低所述日工作量占比为(例如调整为95%)。例而言,月工作日的基准天数为20天,该20天对应的团队月工作量为数量A,对应的日工作量占比为100%,若该团队三月份的月工作日上限为25天,三月份的的工作量为数量C,且数量C通过上述的月工作日公式计算得到的计算结果大于25天,需要调整日工作量占比大于100%才可能在25天完成任务,此时日工作量占比可以通过以下公式计算得到:日工作量占比=20*C/A*25。
所述第一计算模块102用于根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量。
在一实施方式中,所述第一计算模块102还用于根据所述团队的员工数量、所述团队的月工作日及所述日工作量占比计算所述团队的预期人力。
在一实施方式中,所述团队月工作量可以通过以下公式计算得到:团队月工作量=***月总工作量*(团队当前人力/***总人力)。每一所述员工的月计划量可以通过以下公式计算得到:员工的月计划量=团队月工作量/团队当前人力。所述团队的预期人力可以通过以下公式计算得到:团队预期人力=团队当前人力*SUM(工作日*日工作量占比)/工作日天数。举例而言,***上传月总任务量为1万份,团队人力为10人,部门总人力为40人,月工作日为20天,20天中每天对应的工作量占比为110%、110%、120%、100%、110%、120%、110%、110%、120%、100%,110%、110%、120%、100%、110%、120%、110%、110%、120%、100%,则团队月工作量=[10000*(10/40)]=2500份,员工月计划量=2500/10=250份,团队预期人力
=10*[(110%+110%+120%+100%+110%+120%+110%+110%+120%+100%+110%+110%+120%+100%+110%+120%+110%+110%+120%+100%)/20]。
在一实施方式中,所述第一计算模块102还用于判断计算得到的所述团队的预期人力与所述团队的当前员工数量的比值是否大于一预设比值;若所述团队的预期人力与所述团队的当前员工数量大于所述预设比值,所述第一计算模块102控制一显示单元(图未示)输出以一派工任务超负荷的警示信息。
所述第二计算模块103用于获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量。
在一实施方式中,所述员工的当日计划量可以通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比)。
所述分派模块104用于根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。
举例而言,若所述第二计算模块103计算一员工的当日计划量为13份,则所述分派模块104分派13份的工作任务至该员工。
所述关联模块105用于根据所述团队的月工作日判断一日期是否为工作日,及在判断该日期是工作日时为所述工作日关联工作日志,并根据所述工作日志的状态生成工作日标记。其中,所述工作日志包括有当前分派到的工作任务的进度信息。
在一实施方式中,若某一日期为工作日,员工很可能需要记录日程安排、设置事件提醒等。所述工作日志可以供员工进行编辑和记录。一个工作日关联的工作日志可以是一个,也可以是多个。若所述工作日志的状态是未填写时,则所述关联模块105生成第一工作日标记;若所述工作日志的状态是已填写时,则所述关联模块105生成第二工作日标记;若所述工作日志的状态被更新时,则所述关联模块105重新根据所述工作日志的状态生成工作日标记。
举例而言,可设定一个工作日关联两个工作日志,两个工作日志分别记录上午日程和下午日程。当所述工作日志的状态是未填写,可以生成第一工作日标记;当所述工作日志的状态是已填写,可以生成第二工作日标记。例如,一工作日记录上午日程的工作日志已填写,记录下午日程的工作日志未填写,则在该日期上标记一个第一工作日标记及一个第二工作日标记。若记录下午日程的工作日志用户被填写,则意味着工作日志的状态更新,则工作日标记同样需要更新,即需要根据工作日志更新后的状态,重新生成工作日标记并添加。
通过上述程序模块101-105,本申请所提出的任务派工***100,首先,根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比;其次,根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量;再者,获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量,其中,所述当日计划量通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比);再者,根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工;最后,根据所述团队的月工作日判断一日期是否为工作日,及在判断该日期是工作日时为所述工作日关联工作日志,并根据所述工作日志的状态生成工作日标记,其中,所述工作日志包括有当前分派到的工作任务的进度信息。这样,可以实现根据不同区域、不同团队的需求设定个性化的工作日,提前根据团队的任务量计算人力的投入并进行员工的工作安排,且可根据工作日的设置自动计算当月任务计划量及当日应派发的工作任务量,还可根据工作日自动关联每一员工的工作日志。
此外,本申请还提出一种任务派工方法。
参阅图4所示,是本申请任务派工方法第一实施例的实施流程示意图。在本实施例中,根据不同的需求,图4所示的流程图中的步骤的执行顺序可以改变,某些步骤可以省略。
步骤S400,根据预设日期策略及团队月工作量设定团队的月工作日及日 工作量占比。
在一实施例中,初始的月工作日可以根据国家年度放假安排进行设置。例如法定节假日、周末可以被默认设置为休息日,每月工作日的基准天数可以设置为20天。不同区域、不同团队可制定有不同的所述预设日期策略,可以根据团队的实际需求通过所述预设日期策略对工作日和休息日进行自由的设定和调整。团队的休息日可以是默认的法定休息日和选定休息日。所述选定休息日可以是任意被选定的日期,可由团队在制定所述预设日期策略的时候,根据自身需求自行选定。各团队内部的调休可以被设定成选定休息日。未被设定为休息日的日期,即被作为团队的工作日。通过所述预设日期策略可以明确了解哪些日期为所述工作日,哪些日期为所述休息日,并可进行实时调整,被设定的团队月工作日及月休息日均需大于基准休息日天数和基准月工作日天数,从而避免月工作日的天数设定太多或者太少。举例而言,若每月工作日的基准天数为20天,该20天对应的团队月工作量为数量A。则设定的月工作日天数应大于20天。若团队一月份的月工作量小于A,则该月的月工作日为20天。若团队三月份的工作量为B且B>A,所述设定模块101设定的团队的月工作日可以通过以下公式计算得到:团队的月工作日=B*A/20;其中,该公式计算得到的团队的月工作日优选为正整数,若计算得到数据是小数,则计算结果自动加1。
在一实施方式中,若团队的月工作量大于年度月平均工作量,则在基准月工作日基础上增加第一预设天数的工作日,若团队的月工作量小于年度月平均工作量,则在基准月工作日基础上增加第二预设天数的工作日。所述第一预设天数大于所述第二预设天数。每个工作日都可以设置日工作量占比,默认的日工作量占比为100%。由于月工作日的天数具有上限,当月工作量较大时,可以根据实际需要完成的月工作量进行日工作量占比调整。若团队月工作量较重时,可以适当调高所述日工作量占比为(例如调整为110%),若团队月工作量较轻时,可以适当调低所述日工作量占比为(例如调整为95%)。举例而言,月工作日的基准天数为20天,该20天对应的团队月工作量为数量A,对应的日工作量占比为100%,若该团队三月份的月工作日上限为25天,三月份的的工作量为数量C,且数量C通过上述的月工作日公式计算得到的计算结果大于25天,需要调整日工作量占比大于100%才可能在25天完成任务,此时日工作量占比可以通过以下公式计算得到:日工作量占比=20*C/A*25。
步骤S402,根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量。
在一实施方式中,还可以根据所述团队的员工数量、所述团队的月工作日及所述日工作量占比计算所述团队的预期人力。
在一实施方式中,所述团队月工作量可以通过以下公式计算得到:团队月工作量=***月总工作量*(团队当前人力/***总人力)。每一所述员工的月计划量可以通过以下公式计算得到:员工的月计划量=团队月工作量/团队当前人力。所述团队的预期人力可以通过以下公式计算得到:团队预期人力=团队 当前人力*SUM(工作日*日工作量占比)/工作日天数。举例而言,***上传月总任务量为1万份,团队人力为10人,部门总人力为40人,月工作日为20天,20天中每天对应的工作量占比为110%、110%、120%、100%、110%、120%、110%、110%、120%、100%,110%、110%、120%、100%、110%、120%、110%、110%、120%、100%,则团队月工作量=[10000*(10/40)]=2500份,员工月计划量=2500/10=250份,团队预期人力
=10*[(110%+110%+120%+100%+110%+120%+110%+110%+120%+100%+110%+110%+120%+100%+110%+120%+110%+110%+120%+100%)/20]。
在一实施方式中,当所述计算得到的团队的预期人力与所述团队的当前员工数量大于一预设比值,将会产生并输出一派工任务超负荷的警示信息。
步骤S404,根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量。
在一实施方式中,所述员工的当日计划量可以通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比)。
步骤S406,根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。
举例而言,若计算一员工的当日计划量为13份,则分派13份的工作任务至该员工。
通过上述步骤S400-S406,本申请所提出的任务派工方法,首先,根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比;其次,根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量;再者,获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量,其中,所述当日计划量通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比);最后,根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。这样,可以实现根据不同区域、不同团队的需求设定个性化的工作日,提前根据团队的任务量计算人力的投入并进行员工的工作安排,且可根据工作日的设置自动计算当月任务计划量及当日应派发的工作任务量,还可根据工作日自动关联每一员工的工作日志。
参阅图5所示,是本申请任务派工方法第二实施例的实施流程示意图。在本实施例中,根据不同的需求,图5所示的流程图中的步骤的执行顺序可以改变,某些步骤可以省略。
步骤S400,根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比。
在一实施例中,初始的月工作日可以根据国家年度放假安排进行设置。例如法定节假日、周末可以被默认设置为休息日,每月工作日的基准天数可以设置为20天。不同区域、不同团队可制定有不同的所述预设日期策略,可以根据团队的实际需求通过所述预设日期策略对工作日和休息日进行自由的 设定和调整。团队的休息日可以是默认的法定休息日和选定休息日。所述选定休息日可以是任意被选定的日期,可由团队在制定所述预设日期策略的时候,根据自身需求自行选定。各团队内部的调休可以被设定成选定休息日。未被设定为休息日的日期,即被作为团队的工作日。通过所述预设日期策略可以明确了解哪些日期为所述工作日,哪些日期为所述休息日,并可进行实时调整,被设定的团队月工作日及月休息日均需大于基准休息日天数和基准月工作日天数,从而避免月工作日的天数设定太多或者太少。举例而言,若每月工作日的基准天数为20天,该20天对应的团队月工作量为数量A。则设定的月工作日天数应大于20天。若团队一月份的月工作量小于A,则该月的月工作日为20天。若团队三月份的工作量为B且B>A,所述设定模块101设定的团队的月工作日可以通过以下公式计算得到:团队的月工作日=B*A/20;其中,该公式计算得到的团队的月工作日优选为正整数,若计算得到数据是小数,则计算结果自动加1。
在一实施方式中,若团队的月工作量大于年度月平均工作量,则在基准月工作日基础上增加第一预设天数的工作日,若团队的月工作量小于年度月平均工作量,则在基准月工作日基础上增加第二预设天数的工作日。所述第一预设天数大于所述第二预设天数。每个工作日都可以设置日工作量占比,默认的日工作量占比为100%。由于月工作日的天数具有一上限值,当月工作量较大时,可以根据实际需要完成的月工作量进行日工作量占比调整。若团队月工作量较重时,可以适当调高所述日工作量占比为(例如调整为110%),若团队月工作量较轻时,可以适当调低所述日工作量占比为(例如调整为95%)。举例而言,月工作日的基准天数为20天,该20天对应的团队月工作量为数量A,对应的日工作量占比为100%,若该团队三月份的月工作日上限为25天,三月份的的工作量为数量C,且数量C通过上述的月工作日公式计算得到的计算结果大于25天,需要调整日工作量占比大于100%才可能在25天完成任务,此时日工作量占比可以通过以下公式计算得到:日工作量占比=20*C/A*25。
步骤S402,根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量。
在一实施方式中,还可以根据所述团队的员工数量、所述团队的月工作日及所述日工作量占比计算所述团队的预期人力。
在一实施方式中,所述团队月工作量可以通过以下公式计算得到:团队月工作量=***月总工作量*(团队当前人力/***总人力)。每一所述员工的月计划量可以通过以下公式计算得到:员工的月计划量=团队月工作量/团队当前人力。所述团队的预期人力可以通过以下公式计算得到:团队预期人力=团队当前人力*SUM(工作日*日工作量占比)/工作日天数。举例而言,***上传月总任务量为1万份,团队人力为10人,部门总人力为40人,月工作日为20天,20天中每天对应的工作量占比为110%、110%、120%、100%、110%、120%、110%、110%、120%、100%,110%、110%、120%、100%、110%、120%、 110%、110%、120%、100%,则团队月工作量=[10000*(10/40)]=2500份,员工月计划量=2500/10=250份,团队预期人力
=10*[(110%+110%+120%+100%+110%+120%+110%+110%+120%+100%+110%+110%+120%+100%+110%+120%+110%+110%+120%+100%)/20]。
在一实施方式中,当所述计算得到的团队的预期人力与所述团队的当前员工数量大于一预设比值,将会产生并输出一派工任务超负荷的警示信息。
步骤S404,获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量。
在一实施方式中,所述员工的当日计划量可以通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比)。
步骤S406,根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。
举例而言,若计算一员工的当日计划量为13份,则分派13份的工作任务至该员工。
步骤S408,根据所述团队的月工作日判断一日期是否为工作日,及在判断该日期是工作日时为所述工作日关联工作日志,并根据所述工作日志的状态生成工作日标记。其中,所述工作日志包括有当前分派到的工作任务的进度信息。
在一实施方式中,若某一日期为工作日,员工很可能需要记录日程安排、设置事件提醒等。所述工作日志可以供员工进行编辑和记录。一个工作日关联的工作日志可以是一个,也可以是多个。若所述工作日志的状态是未填写时,则生成第一工作日标记;若所述工作日志的状态是已填写时,则生成第二工作日标记;若所述工作日志的状态被更新时,则重新根据所述工作日志的状态生成工作日标记。
举例而言,可设定一个工作日关联两个工作日志,两个工作日志分别记录上午日程和下午日程。当所述工作日志的状态是未填写,可以生成第一工作日标记;当所述工作日志的状态是已填写,可以生成第二工作日标记。例如,一工作日记录上午日程的工作日志已填写,记录下午日程的工作日志未填写,则在该日期上标记一个第一工作日标记及一个第二工作日标记。若记录下午日程的工作日志用户被填写,则意味着工作日志的状态更新,则工作日标记同样需要更新,即需要根据工作日志更新后的状态,重新生成工作日标记并添加。
通过上述步骤S400-S408,本申请所提出的任务派工方法,首先,根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比;其次,根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量;再者,获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量,其中,所述当日计划量通过以下公式计算得到:当日计划量= 剩余月计划量/SUM(月剩余工作日*日工作量占比);再者,根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工;最后,根据所述团队的月工作日判断一日期是否为工作日,及在判断该日期是工作日时为所述工作日关联工作日志,并根据所述工作日志的状态生成工作日标记,其中,所述工作日志包括有当前分派到的工作任务的进度信息。这样,可以实现根据不同区域、不同团队的需求设定个性化的工作日,提前根据团队的任务量计算人力的投入并进行员工的工作安排,且可根据工作日的设置自动计算当月任务计划量及当日应派发的工作任务量,还可根据工作日自动关联每一员工的工作日志。
上述本申请实施例序号仅仅为了描述,不代表实施例的优劣。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例,并非因此限制本申请的专利范围,凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换,或直接或间接运用在其他相关的技术领域,均同理包括在本申请的专利保护范围内。
Claims (20)
- 一种任务派工方法,应用于服务器,其特征在于,所述方法包括:根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比;根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量;获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量,其中,所述当日计划量通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比);及根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。
- 如权利要求1所述的任务派工方法,其特征在于,所述根据预设日期策略及团队月工作量设定团队的月工作日的步骤包括:根据团队月工作量对法定月工作日和月休息日进行调整,以得到团队的月工作日及月休息日;其中,所述团队的月工作日天数大于预设月基准工作天数。
- 如权利要求1所述的任务派工方法,其特征在于,所述方法还包括:根据所述团队的员工数量、所述团队的月工作日及所述日工作量占比计算所述团队的预期人力;判断所述团队的预期人力与所述团队的员工数量的比值是否大于一预设比值;及若大于所述预设比值,输出以一派工任务超负荷的警示信息。
- 如权利要求2所述的任务派工方法,其特征在于,所述方法还包括:根据所述团队的员工数量、所述团队的月工作日及所述日工作量占比计算所述团队的预期人力;判断所述团队的预期人力与所述团队的员工数量的比值是否大于一预设比值;及若大于所述预设比值,输出以一派工任务超负荷的警示信息。
- 根据权利要求1所述的任务派工方法,其特征在于,所述方法还包括:根据所述团队的月工作日判断一日期是否为工作日;及若判断该日期是工作日,则为所述工作日关联工作日志,并根据所述工作日志的状态生成工作日标记;其中,所述工作日志包括有当前分派到的工作任务的进度信息。
- 根据权利要求2或3或4所述的任务派工方法,其特征在于,所述方法还包括:根据所述团队的月工作日判断一日期是否为工作日;及若判断该日期是工作日,则为所述工作日关联工作日志,并根据所述工 作日志的状态生成工作日标记;其中,所述工作日志包括有当前分派到的工作任务的进度信息。
- 根据权利要求6所述的任务派工方法,其特征在于,所述根据所述工作日志的状态生成工作日标记的步骤包括:若所述工作日志的状态是未填写时,生成第一工作日标记;若所述工作日志的状态是已填写时,生成第二工作日标记;或若所述工作日志的状态被更新时,重新根据所述工作日志的状态生成工作日标记。
- 一种服务器,其特征在于,所述服务器包括存储器、处理器,所述存储器上存储有可在所述处理器上运行的任务派工***,所述任务派工***被所述处理器执行时实现如下步骤:根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比;根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量;获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量,其中,所述当日计划量通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比);及根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。
- 如权利要求8所述的服务器,其特征在于,所述根据预设日期策略及团队月工作量设定团队的月工作日的步骤包括:根据团队月工作量对法定月工作日和月休息日进行调整,以得到团队的月工作日及月休息日;其中,所述团队的月工作日天数大于预设月基准工作天数。
- 如权利要求8所述的服务器,其特征在于,所述任务派工***被所述处理器执行时还实现如下步骤:根据所述团队的员工数量、所述团队的月工作日及所述日工作量占比计算所述团队的预期人力;判断所述团队的预期人力与所述团队的员工数量的比值是否大于一预设比值;及若大于所述预设比值,输出以一派工任务超负荷的警示信息。
- 如权利要求9所述的服务器,其特征在于,所述任务派工***被所述处理器执行时还实现如下步骤:根据所述团队的员工数量、所述团队的月工作日及所述日工作量占比计算所述团队的预期人力;判断所述团队的预期人力与所述团队的员工数量的比值是否大于一预设比值;及若大于所述预设比值,输出以一派工任务超负荷的警示信息。
- 如权利要求8所述的服务器,其特征在于,所述任务派工***被所述处理器执行时还实现如下步骤:根据所述团队的月工作日判断一日期是否为工作日;及若判断该日期是工作日,则为所述工作日关联工作日志,并根据所述工作日志的状态生成工作日标记;其中,所述工作日志包括有当前分派到的工作任务的进度信息。
- 如权利要求9或10或11所述的服务器,其特征在于,所述任务派工***被所述处理器执行时还实现如下步骤:根据所述团队的月工作日判断一日期是否为工作日;及若判断该日期是工作日,则为所述工作日关联工作日志,并根据所述工作日志的状态生成工作日标记;其中,所述工作日志包括有当前分派到的工作任务的进度信息。
- 如权利要求13所述的服务器,其特征在于,所述根据所述工作日志的状态生成工作日标记的步骤包括:若所述工作日志的状态是未填写时,生成第一工作日标记;若所述工作日志的状态是已填写时,生成第二工作日标记;或若所述工作日志的状态被更新时,重新根据所述工作日志的状态生成工作日标记。
- 一种计算机可读存储介质,所述计算机可读存储介质存储有任务派工***,所述任务派工***可被至少一个处理器执行,以使所述至少一个处理器执行如下步骤:根据预设日期策略及团队月工作量设定团队的月工作日及日工作量占比;根据所述团队月工作量、所述团队的员工数量计算每一所述员工的月计划量;获取每一所述员工的剩余月计划量、月剩余工作日,并根据每一所述员工的剩余月计划量、月剩余工作日及所述日工作量占比计算每一所述员工的当日计划量,其中,所述当日计划量通过以下公式计算得到:当日计划量=剩余月计划量/SUM(月剩余工作日*日工作量占比);及根据计算得到的每一所述员工的当日计划量分派相应数量的工作任务至每一所述员工。
- 如权利要求15所述的计算机可读存储介质,其特征在于,所述根据预设日期策略及团队月工作量设定团队的月工作日的步骤包括:根据团队月工作量对法定月工作日和月休息日进行调整,以得到团队的月工作日及月休息日;其中,所述团队的月工作日天数大于预设月基准工作天数。
- 如权利要求15所述的计算机可读存储介质,其特征在于,所述任务派工***被所述处理器执行时还实现如下步骤:根据所述团队的员工数量、所述团队的月工作日及所述日工作量占比计算所述团队的预期人力;判断所述团队的预期人力与所述团队的员工数量的比值是否大于一预设比值;及若大于所述预设比值,输出以一派工任务超负荷的警示信息。
- 如权利要求16所述的计算机可读存储介质,其特征在于,所述任务派工***被所述处理器执行时还实现如下步骤:根据所述团队的员工数量、所述团队的月工作日及所述日工作量占比计算所述团队的预期人力;判断所述团队的预期人力与所述团队的员工数量的比值是否大于一预设比值;及若大于所述预设比值,输出以一派工任务超负荷的警示信息。
- 如权利要求15-18任一项所述的计算机可读存储介质,其特征在于,所述任务派工***被所述处理器执行时还实现如下步骤:根据所述团队的月工作日判断一日期是否为工作日;及若判断该日期是工作日,则为所述工作日关联工作日志,并根据所述工作日志的状态生成工作日标记;其中,所述工作日志包括有当前分派到的工作任务的进度信息。
- 如权利要求19所述的计算机可读存储介质,其特征在于,所述根据所述工作日志的状态生成工作日标记的步骤包括:若所述工作日志的状态是未填写时,生成第一工作日标记;若所述工作日志的状态是已填写时,生成第二工作日标记;或若所述工作日志的状态被更新时,重新根据所述工作日志的状态生成工作日标记。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810501878.1 | 2018-05-23 | ||
CN201810501878.1A CN108764697A (zh) | 2018-05-23 | 2018-05-23 | 任务派工方法、服务器及计算机可读存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019223152A1 true WO2019223152A1 (zh) | 2019-11-28 |
Family
ID=64004976
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/102404 WO2019223152A1 (zh) | 2018-05-23 | 2018-08-27 | 任务派工方法、服务器及计算机可读存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN108764697A (zh) |
WO (1) | WO2019223152A1 (zh) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109726996A (zh) * | 2019-01-03 | 2019-05-07 | 深圳壹账通智能科技有限公司 | 人力投入管理方法、装置、计算机设备和存储介质 |
CN110264060B (zh) * | 2019-06-13 | 2023-06-20 | 智慧中医科技(广东)有限公司 | 一种基于药师审方状态的处方分发方法及*** |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105741003A (zh) * | 2014-12-11 | 2016-07-06 | 金蝶软件(中国)有限公司 | 一种计划书生成方法及计划书生成设备 |
CN107844907A (zh) * | 2017-11-08 | 2018-03-27 | 厦门市再丰运动器材有限公司 | 一种生产计划和派工验收进度的生产管理方法 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014174610A1 (ja) * | 2013-04-24 | 2014-10-30 | Suguro Takao | 勤務計画作成システム |
CN104036369A (zh) * | 2014-06-29 | 2014-09-10 | 谭希妤 | 一种自动生成银行团队电子工作日志的方法和*** |
CN105094820A (zh) * | 2015-07-17 | 2015-11-25 | 北京乐动卓越科技有限公司 | 一种日期信息的显示方法及*** |
-
2018
- 2018-05-23 CN CN201810501878.1A patent/CN108764697A/zh active Pending
- 2018-08-27 WO PCT/CN2018/102404 patent/WO2019223152A1/zh active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105741003A (zh) * | 2014-12-11 | 2016-07-06 | 金蝶软件(中国)有限公司 | 一种计划书生成方法及计划书生成设备 |
CN107844907A (zh) * | 2017-11-08 | 2018-03-27 | 厦门市再丰运动器材有限公司 | 一种生产计划和派工验收进度的生产管理方法 |
Also Published As
Publication number | Publication date |
---|---|
CN108764697A (zh) | 2018-11-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7660406B2 (en) | Systems and methods for integrating outsourcers | |
US20060059059A1 (en) | Systems and methods for managing the execution of services | |
US8255260B2 (en) | System and method for filtering exceptions generated by forecasting and replenishment engine | |
US7539627B2 (en) | System and method for forecasting workload and resource requirements in a call center/help desk | |
US8705723B2 (en) | Systems and methods for scheduling contact center agents | |
US20210337069A1 (en) | Exclusive Agent Pool Allocation Method, Electronic Device, And Computer Readable Storage Medium | |
US8458002B2 (en) | Service scheduling | |
US20070038498A1 (en) | Method and system for allocating specific appointment time windows in a service industry | |
WO2019223150A1 (zh) | 排班方法、服务器及计算机可读存储介质 | |
EP3074932A1 (en) | Communicating task instructions to a plurality of distributed computer devices to provide a healthcare task management system | |
US20110010343A1 (en) | Optimization and staging method and system | |
CN108183933A (zh) | 消息推送方法、装置及***、电子设备和计算机存储介质 | |
US20150286982A1 (en) | Dynamically modeling workloads, staffing requirements, and resource requirements of a security operations center | |
KR20220004549A (ko) | 배달원의 배정을 위한 전자 장치 및 그 동작 방법 | |
WO2019223152A1 (zh) | 任务派工方法、服务器及计算机可读存储介质 | |
US20220383236A1 (en) | Enterprise Workload Sharing System | |
EP2182675A1 (en) | Message sequence management of enterprise based correlated events | |
US20180144407A1 (en) | Supplemental electronic note data message distribution in near real-time | |
CN108521524B (zh) | 坐席协办任务管理方法、装置、计算机设备及存储介质 | |
CN114358508A (zh) | 一种工单分配方法、装置、设备和介质 | |
JP2004118832A (ja) | 保険の挙績又は販売手数料配分のための情報処理方法及び装置 | |
US20140310029A1 (en) | System and method for intelligent management of appointment waiting list | |
US20240161033A1 (en) | System and method for updating resource assignments | |
CN115088240B (zh) | 用于对与电子交易订购平台相关联的入站电信进行预测的***和方法 | |
JP6016657B2 (ja) | データ処理装置及びプログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18919630 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18919630 Country of ref document: EP Kind code of ref document: A1 |