WO2019015656A1 - 一种系统派工方法 - Google Patents

一种系统派工方法 Download PDF

Info

Publication number
WO2019015656A1
WO2019015656A1 PCT/CN2018/096345 CN2018096345W WO2019015656A1 WO 2019015656 A1 WO2019015656 A1 WO 2019015656A1 CN 2018096345 W CN2018096345 W CN 2018096345W WO 2019015656 A1 WO2019015656 A1 WO 2019015656A1
Authority
WO
WIPO (PCT)
Prior art keywords
role
task
dispatched
user
employee
Prior art date
Application number
PCT/CN2018/096345
Other languages
English (en)
French (fr)
Inventor
陈达志
Original Assignee
成都牵牛草信息技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 成都牵牛草信息技术有限公司 filed Critical 成都牵牛草信息技术有限公司
Publication of WO2019015656A1 publication Critical patent/WO2019015656A1/zh

Links

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/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • 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
    • 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
    • G06Q10/063112—Skill-based matching of a person or a group to a task
    • 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/10—Office automation; Time management
    • 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/10—Office automation; Time management
    • G06Q10/105—Human resources

Definitions

  • the invention relates to a dispatching method of a management software system such as ERP.
  • Role-based access control is one of the most researched and matured database rights management mechanisms in recent years. It is considered to be an ideal candidate to replace traditional mandatory access control (MAC) and autonomous access control (DAC). Traditional autonomous access control has high flexibility but low security. Forced access control is highly secure but too restrictive. Role-based access control combines both ease of management and reduces the complexity, cost, and probability of errors. Therefore, it has been greatly developed in recent years.
  • the basic idea of role-based access control (RBAC) is to divide different roles according to different functional positions in the enterprise organization view, encapsulate the access rights of database resources in roles, and indirectly access database resources by being assigned different roles.
  • the role-based permission control mechanism can manage the access rights of the system simply and efficiently, which greatly reduces the burden and cost of the system rights management, and makes the system rights management more in line with the business management specifications of the application system.
  • the traditional role-based user rights management adopts the "role-to-user one-to-many" association mechanism, and the "role” is group/class nature, that is, one role can simultaneously correspond to/associate multiple users, and the role is similar to the post/
  • the concept of position/work type the authorization of user rights under this association mechanism is basically divided into the following three forms: 1. As shown in Figure 1, the user is authorized directly, the disadvantage is that the workload is large, the operation is frequent and troublesome; Employee changes (such as transfer, resignation, etc.), all the form operation rights involved in the employee must be adjusted accordingly, especially for company management personnel, the form permissions involved, the task of authority adjustment is large and complicated. It is easy to make mistakes or omissions, affecting the normal operation of the company and even causing unpredictable losses.
  • the role (class/group/post/work type) is authorized (a role can be associated with multiple users), the user obtains the permission through the role, and the approval operation subject is the group/class nature role; As shown in Figure 3, the above two methods are combined.
  • both 2 and 3 need to authorize the role of the class/group nature, and the way of authorization and workflow control through the role of class/group/post/work type has the following disadvantages: 1.
  • Difficulties in operation In the actual system use process, it is often necessary to adjust the user's authority during the operation process. For example, when dealing with employee permission changes, the employee rights associated with the role change, we cannot because of this Changes in employee permissions change the permissions of the entire role, because the role is also associated with other employees whose permissions have not changed. So in response to this situation, either create a new role to satisfy the employee whose permissions have changed, or directly authorize (disengage the role) from the employee based on the permission requirements.
  • the above two processing methods not only require a long time for the role authorization in the case of a large number of role permissions, but also are easy to make mistakes, the user is cumbersome and troublesome to operate, and is also prone to errors resulting in loss to the system user.
  • the employee/user's form operation permissions change either the employee/user is removed from the role or the role is added to meet the job requirements.
  • the defect of the first method is the same as the above-mentioned "direct authorization to the user" method.
  • the new role involves the creation, association, and authorization of the role. Especially in the case of a large number of roles and a large number of users associated with the role, it is difficult to remember which users are associated with the role.
  • the traditional system usually distributes the work task directly to the person. Once the person leaves the post or adjusts the post, he must return all the tasks in his hand. There are several defects in the following aspects: A: For this person All tasks must be returned one by one, and the operation is troublesome. Especially for the employees who are leaving, they are not necessarily willing to cooperate with the operation of returning the task. B: For the dispatcher, these tasks need to be re-distributed to other employees.
  • C the process of returning to the task usually needs to be approved, prolonging the cycle of task execution, increasing the internal friction of the system; Approval is required. If the task is not returned in time, it will seriously affect the execution of the task. In particular, some tasks require urgent time. If not returned in time and handed over to new people, it may cause serious consequences and unpredictable losses; D: When the user adjusts the post, it is also necessary to return all the previous tasks by the user, and then assign the new post to the dispatcher. There are also problems such as troublesome operations and delays in task execution cycles.
  • the object of the present invention is to overcome the deficiencies of the prior art, and to provide a system dispatching method, which distributes tasks to a role, and an employee obtains a task assigned by a corresponding user-associated role.
  • the system administrator directly (or the corresponding administrator) cancel the association between the user and the role of the employee.
  • the new employee replaces the task of the employee, directly associate the new employee with the role, without relying on the employee to return to the task, or to enter the new job.
  • the employee re-delivers the work to achieve seamless docking, which is convenient and quick to operate.
  • the system administrator (or the corresponding administrator) directly cancels the association between the employee and the original role, and then associates the new role to automatically obtain the
  • the task of the new role dispatching can guarantee the execution cycle of the task without approval.
  • the dispatcher it is only necessary to do the dispatch of the role in the early stage, and no longer need to send it when the employee leaves or adjusts the post. The operator does any work, greatly reducing the workload of the dispatcher.
  • a system dispatching method comprising a step of determining a dispatched task, a step of determining a dispatched object, and a dispatching step of determining a dispatched task.
  • the steps and the steps of determining the dispatched object are in no particular order; the step of determining the dispatched task: determining the task to be dispatched; and the step of determining the dispatched object: determining the assigned object, the object being the role
  • the role is an independent individual, not a group/class. A role can only be associated with a unique user at the same time, and a user is associated with one or more roles.
  • a dispatch step dispatching a task that needs to be dispatched to the The role of the dispatched worker, the employee corresponding to the user associated with the assigned role obtains the assigned task.
  • a system dispatch method further includes a step of returning a task, and the dispatched worker returns the assigned task through the step.
  • a system dispatch method also includes the steps of the assigned role to choose whether to accept the dispatch.
  • the role must select a department. Once the role is selected, the role belongs to the department. The name of the role is unique under the department. The role number is unique in the system, and the role is authorized according to the work content of the role.
  • a system dispatching method further includes a step of managing an inter-departmental management of a user, which includes: (1) canceling the association between the user and the role in the original department; (2) associating the user with the role in the new department, the user The task of dispatching the new character is automatically obtained.
  • One user corresponds to one employee, one employee corresponds to one user, and the user determines (acquires) permissions through its association with the role.
  • a system dispatch method that also includes the steps of setting up a task or role that an employee needs to be assigned to handle.
  • a method of system dispatching also includes the step of setting a level of capability level of a role or employee that needs to be dispatched to handle the task.
  • the assigned role is one or more. When there are multiple roles assigned, you need to assign a responsible role.
  • a system dispatch method further includes a step of setting a task urgency, and the dispatcher selects a task urgency when performing the dispatch, and the dispatched character displays the urgency of the task when the task is received.
  • the beneficial effects of the present invention are as follows: (1) The present application distributes the task to the role, and the employee obtains the assigned task through the corresponding user-associated role.
  • the system administrator or the corresponding administrator directly cancels the task.
  • the relationship between the user and the role of the employee When the new employee replaces the task of the employee, the new employee is directly associated with the role. There is no need to rely on the employee to return to the task, and there is no need to re-deliver the new employee.
  • the seamless seamless connection makes the operation convenient and quick; when the employee is transferred, the system administrator (or the corresponding administrator) directly cancels the association between the user corresponding to the original role and the original role, and then associates the new role to automatically obtain the new one.
  • the task of dispatching a character can guarantee the execution cycle of the task without approval.
  • it is only necessary to do the dispatch of the role in the early stage, and no need to send the worker when the employee leaves or adjusts the post. Any operation is carried out, which greatly reduces the workload of the dispatcher.
  • Example of resignation The dispatcher dispatched tasks A, B, and C for the role of “production worker 1”.
  • Zhang San obtained tasks A, B, and C.
  • the system administrator or the corresponding administrator directly cancels the association between Zhang San and the role of “production worker 1”, and does not need to return the assigned task by Zhang San operation; the newly recruited employee Li Si takes over the work content and tasks of Zhang San.
  • Li Si was directly associated with “production worker 1”
  • Li Si automatically obtained the tasks A, B, and C assigned to the role of “production worker 1”, and no need to re-deliver the work for Li Si. , greatly reducing the workload of the dispatcher.
  • Example of transfer employee Zhang San should be transferred from the production department to the after-sales department.
  • the system administrator (or the corresponding administrator) cancels the association between Zhang San and the original role “production worker 1”, and then links to the new role of the after-sales department.
  • Service staff 3 Zhang San automatically obtained the tasks E, F assigned to the role of "after-sales service personnel 3".
  • This application provides the function of returning a task.
  • special cases such as time conflicts or inability to complete tasks, etc.
  • the assigned role is allowed to return the assigned task.
  • the return of the task requires filling in the reason, and the design is reasonable and used. Convenience.
  • Zhang San can return to the task G, when returning Fill in or choose the reason for the return.
  • the system can set which tasks or employees that need to be dispatched can handle tasks, and the level of ability of the roles or employees who need to be assigned to handle the corresponding tasks, which is convenient for the dispatcher to select and refer to when dispatching workers. Improve the efficiency of dispatched workers and improve the accuracy and rationality of dispatch.
  • an existing ULP5 model air conditioning maintenance task with difficulty in maintenance the dispatcher is ready to distribute the task to the after-sales service personnel of the after-sales department. Since the system sets up what tasks each employee can handle, the dispatcher will soon be able to Among the after-sales service personnel, find out which employees can repair the ULP5 model air conditioner, and then consider that the maintenance of the task is difficult.
  • the level of ability to repair the air conditioner is five. The level of ability to repair air conditioners is divided into first-level, second-level, ..., five-level, five-level representative level of the highest level of employees; and if not, the dispatcher shows that it can repair ULP5 air conditioners.
  • the role of the application is a one-to-one relationship to the user.
  • One role can only be associated with a unique user at the same time, and one user is associated with one or more roles.
  • Permissions that is, users gain access to their associated roles
  • the role's permission changes are much less than the user permissions in the traditional mechanism.
  • the number of roles of the nature of the independent body is small. Although the employee turnover is large, the change of the post number/station number is small (even if there is no change in a certain period of time, that is, the role does not change), This will greatly simplify the user's rights management and reduce the overhead of the system.
  • the operation of dynamic management, on-the-job adjustment, etc. is simple and convenient, high efficiency, high reliability: the application of the entry/departure/adjustment in the authority management is simple, and the user/user does not need to reset the permission when the user/user changes, the user only You need to cancel or associate the role: the user who is no longer in the role cancels the role association, and the user who takes the role is associated with the role of the post number. The user associated with the role automatically obtains the related tasks and operations of the role. Permissions, without the need to re-authorize and dispatch roles, greatly improve the efficiency, security, and reliability of system setup.
  • Zhang San due to Zhang San’s resignation or transfer, Zhang San will no longer work as a “buyer 3”, and Zhang will cancel the association with “Purchaser 3”; Li Si will take over as “Purchaser”. 3"
  • the role of this role only need to associate Li Si with the role, then Li Si automatically obtained the authority and task of the "Purchaser 3" role.
  • the traditional authority management mechanism defines roles as groups, types of work, classes, etc.
  • the role is a one-to-many relationship with the user. In the actual system use process, the user's authority is often required in the operation process. Adjustments, for example, when the employee permissions are changed, the permissions of an employee associated with the role change. We cannot change the permissions of the entire role because of the change of the individual employee permissions, because the role is also associated with other permissions. Staff. So in response to this situation, either create a new role to satisfy the employee whose permissions have changed, or directly authorize (disengage the role) from the employee based on the permission requirements.
  • the above two processing methods not only require a long time for the role authorization in the case of a large number of role permissions, but also are easy to make mistakes, the user is cumbersome and troublesome to operate, and is also prone to errors resulting in loss to the system user.
  • the role since the role is an independent individual, the role permission can be changed to achieve the goal.
  • the method of the present application seems to increase the workload when the system is initialized, it can be made by copying or the like to make the role or authorization more efficient than the traditional group/class nature, because the group/class role is not considered.
  • the application scheme will make the permission setting clear and clear; especially after the system is used for a period of time (the user/role authority changes dynamically), the application scheme can greatly improve the system usage for the system user.
  • the efficiency of the rights management makes the dynamic authorization simpler, more convenient, clearer and clearer, and improves the efficiency and reliability of the permission setting.
  • the traditional group/class role authorization method is error-prone, and the method of the present application greatly reduces the probability of authorization error, because the method of the present application only needs to consider the role as an independent individual, without considering the traditional method to associate the role of the group. What are the commonalities of multiple users? Even if the authorization error occurs, it only affects the user associated with the role, while the traditional group-based role affects all users associated with the role. Even if a permission authorization error occurs, the correction method of the present application is simple and short, and the traditional group-type role needs to consider the commonality of all users associated with the role when correcting the error, and not only the modification when there are many function points. Troublesome, complicated, very error-prone, and in many cases only new roles can be created.
  • the method of the present application is as follows: the transferred user associates several roles.
  • the user When adjusting the post, the user is first unlinked from the role in the original department (the canceled roles can be re-associated to other users), and then Associate users with roles in the new department. The operation is simple and will not go wrong.
  • FIG. 1 is a schematic diagram of a manner in which a system directly authorizes a user in the background art
  • FIG. 2 is a schematic diagram of a manner in which a system authorizes a group/class role in the background art
  • FIG. 3 is a schematic diagram of a manner in which a system directly authorizes a user and authorizes a group/class role role in the background art
  • FIG. 4 is a schematic diagram of a manner in which a system authorizes a user through an independent individual role
  • Figure 5 is a flow chart of the dispatch of the present invention.
  • a system dispatching method includes a step of determining a dispatched task, a step of determining a dispatched object, and a dispatching step; S1: determining a dispatched task Step: Determine the task that needs to be dispatched.
  • the task can be manually filled in content, or it can be the content of the specified form data or the specified form data (such as dispatching a worker to process a document, dispatching a worker to process a complaint) , designated to handle an installation request, etc., or a combination of the three; tasks include: production nature tasks, sales nature tasks, logistics nature tasks, after-sales nature tasks and other tasks that need to be dispatched.
  • Step of determining the dispatched object determining the object to be dispatched, the object is a role, as shown in FIG. 4, the character is an independent individual, not a group/class, and one role can only be associated in the same time period.
  • a unique user, and a user is associated with one or more roles, one user corresponds to one employee, one employee corresponds to one user, and the user determines (acquires) authority through its association with the role; the user is A frozen, frozen user cannot be associated/associated with another employee. If the employee leaves the company for a certain period of time and returns to the company (job entry), the user whose original employee was frozen is thawed and continues to respond to the employee (ie, the employee continues to use the user) ).
  • the role must select a department. Once the role is selected, the role belongs to the department. The name of the role is unique under the department. The role number is unique in the system, and the role is authorized according to the work content of the role.
  • S3 dispatching step: dispatching the task that needs to be dispatched to the assigned worker, sending a dispatched work order after dispatching the worker, and obtaining the assigned task by the employee corresponding to the user associated with the dispatched role.
  • a dispatch order can be associated with relevant form data, such as an after-sales work order associated with an after-sales request.
  • the role of the dispatched worker can choose whether or not to accept the dispatch.
  • the assigned role is one or more. When there are multiple roles assigned, you need to assign a responsible role. For example, a maintenance task for a large-scale equipment may require multiple after-sales service personnel to complete the repair work. In this case, the maintenance task can be assigned to multiple after-sales service personnel, and one of them is designated as the responsible role.
  • a system dispatching method includes a step of determining a dispatched task, a step of determining a dispatched object, and a dispatching step;
  • SS1 determining a dispatched object Step: determining an object to be dispatched, the object is a role, the role is an independent individual, not a group/class, and a role can only associate with a unique user in the same period, and one user associates one or more roles;
  • SS2 Steps to determine the assigned task: determine the task that needs to be dispatched;
  • SS3 dispatch step: the dispatcher will assign the task to be dispatched to the assigned role, the user associated with the assigned role The corresponding employee gets the assigned task.
  • a dispatcher can be a character, a user, or a person.
  • the user needs to adjust the posts across departments, it also includes a user cross-department management process, which includes: (1) canceling the association between the user and the role in the original department; and (2) associating the user with the role in the new department. The user automatically gets the task of dispatching the new character.
  • the task is assigned to the role, and the employee obtains the assigned task through the corresponding user-associated role.
  • the system administrator or the corresponding administrator directly cancels the association between the user and the role corresponding to the employee.
  • the on-duty employee takes over the task of the retired employee, the new employee can be directly associated with the role.
  • Example of resignation The dispatcher dispatched tasks A, B, and C for the role of “production worker 1”.
  • Zhang San obtained tasks A, B, and C.
  • the system administrator or the corresponding administrator directly cancels the association between Zhang San and the role of “production worker 1”, and does not need to return the assigned task by Zhang San operation; the newly recruited employee Li Si takes over the work content and tasks of Zhang San.
  • Li Si was directly associated with “production worker 1”
  • Li Si automatically obtained the tasks A, B, and C assigned to the role of “production worker 1”, and no need to re-deliver the work for Li Si. , greatly reducing the workload of the dispatcher.
  • Example of transfer employee Zhang San should be transferred from the production department to the after-sales department.
  • the system administrator (or the corresponding administrator) cancels the association between Zhang San and the original role “production worker 1”, and then links to the new role of the after-sales department.
  • Service staff 3 Zhang San automatically obtained the tasks E, F assigned to the role of "after-sales service personnel 3".
  • a system dispatching method includes a step of determining a dispatched task, a step of determining a dispatched object, and a dispatching step; S1: determining a dispatched task Step: determining the task that needs to be dispatched; S2: the step of determining the dispatched object: determining the object to be dispatched, the object is a role, the role is an independent individual, not a group/class, one at the same time A role can only be associated with a unique user, and a user is associated with one or more roles; S3: A dispatch step: a task that needs to be dispatched to a assigned role, and a corresponding employee of the assigned role Get the assigned task.
  • the time for dispatching a job is a time period, not an exact time point, as long as it is completed within this time period.
  • Zhang San can return to the task G, when returning Fill in or choose the reason for the return.
  • the role of the dispatched worker is an independent individual of the station number and the post number nature, the task can be set to handle which tasks and corresponding skill level levels, then the employee corresponding to the post number should have the job number requirement. The ability to work, the corresponding employee of the user associated with the role should be able to complete the task assigned to the post number.
  • Set the dispatching authority of the dispatcher that is, which roles the dispatcher can dispatch, including: (1) setting the department that can be dispatched by the dispatcher (including all the roles added in the follow-up department); For example, the workshop director who produces one can only send workers to the production workers.
  • the traditional method can be assigned to people/employees. For example, there are 100 people who can send workers to K. These include an employee A. After A leaves, the new employee B replaces the work of A, but it is not set. Previously, the dispatcher K was unable to dispatch directly to B because B was not within the scope of his work.
  • the role that can be assigned to the application is the role.
  • the role M associated with A is the role of the dispatcher K. When B enters the post, the association between A and role M is cancelled, and then B is associated with role M. Worker K can automatically dispatch B without any setup.
  • the traditional method requires constant setting of people/employees who can be dispatched when the personnel change frequently. The operation is troublesome and will affect the normal work. .
  • a system dispatching method includes a step of determining a dispatched task, a step of determining a dispatched object, and a dispatching step; S1: determining a dispatched task Step: determining the task that needs to be dispatched; S2: the step of determining the dispatched object: determining the object to be dispatched, the object is a role, the role is an independent individual, not a group/class, one at the same time A role can only be associated with a unique user, and a user is associated with one or more roles; S3: A dispatch step: a task that needs to be dispatched to a assigned role, and a corresponding employee of the assigned role Get the assigned task.
  • it also includes a step of setting a task that the role or employee that needs to be dispatched can handle. Further, it also includes a step of setting a level of capability level for the role or employee to be dispatched to handle the corresponding task.
  • the system can set the tasks or employees that need to be dispatched to be able to handle which tasks, as well as the level of ability of the roles or employees who need to be assigned to handle the corresponding tasks, which is convenient for the dispatcher to select and refer to the work, which helps to improve the dispatch.
  • an existing ULP5 model air conditioning maintenance task with difficulty in maintenance the dispatcher is ready to distribute the task to the after-sales service personnel of the after-sales department. Since the system sets up what tasks each employee can handle, the dispatcher will soon be able to Among the after-sales service personnel, find out which employees can repair the ULP5 model air conditioner, and then consider that the maintenance of the task is difficult.
  • the level of ability to repair the air conditioner is five. The level of ability to repair air conditioners can be divided into first-level, second-level, ..., five-level, and five-level employees with the highest level of competence.
  • a system dispatching method includes a step of determining a dispatched task, a step of determining a dispatched object, and a dispatching step; S1: determining a dispatched task Step: determining the task that needs to be dispatched; S2: the step of determining the dispatched object: determining the object to be dispatched, the object is a role, the role is an independent individual, not a group/class, one at the same time A role can only be associated with a unique user, and a user is associated with one or more roles; S3: A dispatch step: a task that needs to be dispatched to a assigned role, and a corresponding employee of the assigned role Get the assigned task.
  • the dispatcher selects a task urgency when performing the dispatch.
  • the urgency of the task is displayed. For example: divided into 5 levels (immediate / priority / normal / set / last), the dispatch time is normal by default, the dispatcher can modify when sending workers.
  • the object of the present application is an independent individual role.
  • the following is an analysis of the advantages of authorizing the user through the independent individual role: the user determines by its association with the role. (Acquire) permission, if you want to modify the user's permissions, by adjusting the permissions owned by the role to achieve the purpose of changing the permissions of the user associated with the role. Once a user associates a role, that user has all the operational privileges for that role.
  • the role of the role to the user is one-to-one (when the role is associated with a user, other users can no longer associate the role; if the role is not associated with the user, it can be selected by other users; that is, a role can be And can only be associated by one user).
  • a user's relationship to a role is one-to-many (one user can associate multiple roles at the same time).
  • Role definition The role does not have the nature of group/class/category/post/job/work, but a non-collection nature, the role is unique, the role is an independent independent entity; in the enterprise application is equivalent Job number (The job number here is not a post, one post may have multiple employees at the same time, and one job number can only correspond to one employee at the same time).
  • a company system can create the following roles: general manager, deputy general manager 1, deputy general manager 2, Beijing sales manager, Beijing sales manager, Beijing sales manager, Shanghai sales engineer 1, Shanghai sales Engineer 2, Shanghai Sales Engineer 3, Shanghai Sales Engineer 4, Shanghai Sales Engineer 5...
  • general manager deputy general manager 1, deputy general manager 2, Beijing sales manager, Beijing sales manager, Shanghai sales engineer 1, Shanghai sales Engineer 2, Shanghai Sales Engineer 3, Shanghai Sales Engineer 4, Shanghai Sales Engineer 5...
  • Zhang San serves as the company's deputy general manager 2, and also serves as a sales manager in Beijing, then Zhang The three roles to be associated are Deputy General Manager 2 and Beijing Sales Manager. Zhang San has the rights to these two roles.
  • roles are group/class/post/position/work type, and one role can correspond to multiple users.
  • the concept of "role" in this application is equivalent to the post number/station number, and is similar to the role in the film and television drama: a character can only be played by one actor at the same time (childhood, juvenile, middle-aged). And an actor may be decorated with multiple angles.
  • Roles can be associated in the process of creating a user, or they can be associated at any time after the user has been created. After the user associates the role, the relationship with the role can be released at any time, and the relationship with other roles can be established at any time.
  • the composition of the character is: post name + post number.
  • workshop production workers 1, workshop production workers 2, workshop production workers 3... roles are independent individuals, equivalent to the concept of job number and station number, different from the role in the traditional authority management system, the concept of role in the traditional system It is the group/class nature of the position/position/work type.
  • the following example shows the relationship between employees, users and roles after the employee Zhang San enters a company: 1. New entry: The employee is newly hired, and directly associates the role of the corresponding job number/station number for the user (employee). Yes, for example: Zhang San joined the company (the company assigned a three-user for Zhang San), the job content is in the sales department, responsible for the sales of refrigerator products in Beijing area (the corresponding role is to sell the sales engineer under the 5 "This role", Zhang San users directly select the "sales engineer 5" role association.
  • Zhang also arranged for Zhang San to be responsible for the sales of regional TV products in Beijing (the corresponding role is to sell the role of “Sales Engineer 8” under the Ministry of Sales) and concurrently as the head of the after-sales department (corresponding to the after-sales department)
  • the three users added the roles of “sales engineer 8” under the sales department and “sales department supervisor 1” under the after-sales department.
  • Zhang San employees associated three roles, respectively.
  • Zhang San users have the authority of these three roles.
  • Zhang San serves as the post-sales manager (corresponding to the role of “after-sales manager” in the after-sales department) and no longer take up other jobs. Then Zhang San user is associated with the role of “after-sales manager” in the after-sales department, and cancels the three roles previously associated (Sales Engineer 5 under Sales, Sales Engineer 8 and “After Sales Manager 1” under the after-sales department) At this time, Zhang San users only have the authority of the role of “after-sales manager” under the after-sales department.
  • This application authorizes the role of the nature of the post number/station number, and the user determines the (acquired) authority by associating the role, and the control of the user authority is realized by a simple user-role relationship. It makes the permission control simple, easy to operate, clear and clear, and greatly improves the authorization efficiency and authorization reliability.

Abstract

一种系统派工方法，包括：确定被派工任务：确定需要进行派工的任务；确定被派工对象：确定被派工的对象，所述对象为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；派工：将需要进行派工的任务派发给被派工的角色。该方法将任务派发给角色，用户通过与角色的关联获得任务，员工离职时，取消该员工与角色的关联，直接让新入职员工关联该角色即可，无需为新入职员工重新派工，操作方便快捷；员工调岗时，取消与原角色的关联，关联新的角色即可自动获得对该新角色派工的任务；对于派工者而言，在发生离职或调岗时都不需要进行任何操作。

Description

一种系统派工方法 技术领域
本发明涉及一种ERP等管理软件系统派工方法。
 背景技术
基于角色的访问控制（RBAC）是近年来研究最多、思想最成熟的一种数据库权限管理机制，它被认为是替代传统的强制访问控制（MAC）和自主访问控制（DAC）的理想候选。传统的自主访问控制的灵活性高但是安全性低，强制访问控制安全性高但是限制太强；基于角色的访问控制两者兼具，不仅易于管理而且降低了复杂性、成本和发生错误的概率，因而近年来得到了极大的发展。基于角色的访问控制（RBAC）的基本思想是根据企业组织视图中不同的职能岗位划分不同的角色，将数据库资源的访问权限封装在角色中，用户通过被赋予不同的角色来间接访问数据库资源。
在大型应用系统中往往都建有大量的表和视图，这使得对数据库资源的管理和授权变得十分复杂。由用户直接管理数据库资源的存取和权限的收授是十分困难的，它需要用户对数据库结构的了解非常透彻，并且熟悉SQL语言的使用，而且一旦应用系统结构或安全需求有所变动，都要进行大量复杂而繁琐的授权变动，非常容易出现一些意想不到的授权失误而引起的安全漏洞。因此，为大型应用系统设计一种简单、高效的权限管理方法已成为系统和系统用户的普遍需求。
基于角色的权限控制机制能够对系统的访问权限进行简单、高效的管理，极大地降低了系统权限管理的负担和代价，而且使得系统权限管理更加符合应用系统的业务管理规范。
然而，传统基于角色的用户权限管理均采用“角色对用户一对多”的关联机制，其“角色”为组/类性质，即一个角色可以同时对应/关联多个用户，角色类似于岗位/职位/工种等概念，这种关联机制下对用户权限的授权基本分为以下三种形式：1、如图1所示，直接对用户授权，缺点是工作量大、操作频繁且麻烦；当发生员工变动（如调岗、离职等），该员工涉及到的所有表单操作权限必须要作相应调整，特别是对于公司管理人员，其涉及到的表单权限多，权限调整的工作量大、繁杂，容易出错或遗漏，影响企业的正常运营，甚至造成不可预估的损失。
2、如图2所示，对角色（类/组/岗位/工种性质）进行授权（一个角色可以关联多个用户），用户通过角色获得权限，审批操作主体是组/类性质角色；3、如图3所示，以上两种方式结合。
以上的表述中，2、3均需要对类/组性质的角色进行授权，而通过类/组/岗位/工种性质的角色进行授权和工作流控制的方式有以下缺点：1、用户权限变化时的操作难：在实际的系统使用过程中，经常因为在运营过程中需要对用户的权限进行调整，比如：在处理员工权限变化时，角色关联的某个员工权限发生变化，我们不能因该个别员工权限的变化而改变整个角色的权限，因为该角色还关联了其他权限未变的员工。因此为了应对该种情况，要么创建新角色来满足该权限发生变化的员工，要么对该员工根据权限需求直接授权（脱离角色）。以上两种处理方式，在角色权限较多的情况下对角色授权不仅所需时间长，而且容易犯错，使用方操作起来繁琐又麻烦，也容易出错导致对系统使用方的损失。
员工/用户的表单操作权限发生变化时，要么员工/用户脱离角色，要么新增角色来满足工作要求。第一种方式的缺陷同上述“直接对用户授权”方式的缺陷。第二种方式，新增角色便涉及到角色的新建、关联、授权工作，特别在角色多、角色关联的用户也多的情况下，角色具体关联了哪些用户是很难记住的。
2、要长期记住角色包含的具体权限难：若角色的权限功能点比较多，时间一长，很难记住角色的具体权限，更难记住权限相近的角色之间的权限差别，相近角色的权限也很容易混淆；若要关联新的用户，无法准确判断应当如何选择关联。
3、因为用户权限变化，则会造成角色创建越来越多（若不创建新角色，则会大幅增加直接对用户的授权），更难分清各角色权限的具体差别。
4、调岗时，若要将被调岗用户的很多个权限分配给另外几个用户承担，则处理时必须将被调岗用户的这些权限区分开来，分别再创建角色来关联另外几个用户，这样的操作不仅复杂耗时，而且还很容易发生错误。
针对派工方式而言，传统系统通常是将工作任务直接派发给人，这个人一旦离职或调岗，必须全部退回其手上的任务，存在以下几方面的缺陷：A：对于这个人而言，必须逐个、全部退回所有任务，操作比较麻烦，特别是对于即将离职的员工而言，不一定愿意配合完成退回任务的操作；B：对于派工者而言，需要将这些任务重新派发给其他人，等于需要做重复的工作，增加了内耗，派工者工作量大，且容易出错；C：退回任务的过程通常需要经过审批，拖长了任务执行的周期，增加了系统内耗；即使不需要审批，若未及时退回任务，也会严重影响任务的执行，特别是有些任务时间要求紧迫，如果不及时退回并交由新的人处理，可能造成严重后果和不可预估的损失；D：用户调岗时，也需要先由用户退回其之前的所有任务，再由派工者派发新岗位的任务，同样存在操作麻烦、耽误任务执行周期等问题。
 技术问题
本发明的目的在于克服现有技术的不足，提供一种系统派工方法，将任务派发给角色，员工通过对应的用户关联的角色获得被派工的任务，员工离职时，直接由系统管理员（或相应管理员）取消该员工对应的用户与角色的关联，新入职员工接替离职员工的任务时，直接让新入职员工关联该角色即可，无需依赖离职员工退回任务，也无需为新入职员工重新派工，实现无缝对接，操作方便快捷；员工调岗时，直接由系统管理员（或相应管理员）取消该员工与原角色的关联，再关联新的角色即可自动获得对该新角色派工的任务，无需经过审批，能够保障任务的执行周期；对于派工者而言，只需在前期做好对角色的派工，在发生员工离职或调岗时都不再需要派工者进行任何操作，大大减少了派工者的工作量。
 技术解决方案
本发明的目的是通过以下技术方案来实现的：一种系统派工方法，包括一个确定被派工任务的步骤、一个确定被派工对象的步骤和一个派工步骤，确定被派工任务的步骤和确定被派工对象的步骤顺序不分先后；确定被派工任务的步骤：确定需要进行派工的任务；确定被派工对象的步骤：确定被派工的对象，所述对象为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；派工步骤：将需要进行派工的任务派发给被派工的角色，被派工的角色关联的用户对应的员工获得所派任务。
一种系统派工方法，还包括一个退回任务的步骤，被派工的角色通过该步骤退回被派工的任务。
一种系统派工方法，还包括被派工的角色选择是否接受派工的步骤。
所述的角色必须选择一个部门，角色一旦选择部门后则该角色归属于该部门，该角色的名称在该部门下唯一，角色的编号在系统中唯一，根据角色的工作内容对角色进行授权。
一种系统派工方法，还包括一个用户跨部门调岗管理步骤，具体包括：（1）取消用户与原部门内的角色的关联；（2）将用户与新部门内的角色进行关联，用户自动获得对该新角色派工的任务。
一个用户对应一个员工，一个员工对应一个用户，用户通过其与角色的关联确定（获得）权限。
一种系统派工方法，还包括一个设置需要被派工的角色或员工能够处理的任务的步骤。
进一步的，一种系统派工方法，还包括一个设置需要被派工的角色或员工处理相应任务的能力水平等级的步骤。
设置派工者的派工权限，即派工者能对哪些角色进行派工，具体方式包括以下一种或两种的组合：
（1）设置可被该派工者派工的部门；
（2）设置可被该派工者派工的角色。
被派工的角色为一个或多个，当被派工的角色为多个时，需要指定一个负责角色。
一种系统派工方法，还包括一个设置任务紧急度的步骤，派工者在进行派工时选择一个任务紧急度，被派工角色收到任务时将显示该任务的紧急度。
 有益效果
本发明的有益效果是：（1）本申请将任务派发给角色，员工通过对应的用户关联的角色获得被派工的任务，员工离职时，直接由系统管理员（或相应管理员）取消该员工对应的用户与角色的关联，新入职员工接替离职员工的任务时，直接让新入职员工关联该角色即可，无需依赖离职员工退回任务，也无需为新入职员工重新派工，实现了人员变动的无缝对接，操作方便快捷；员工调岗时，直接由系统管理员（或相应管理员）取消该员工对应的用户与原角色的关联，再关联新的角色即可自动获得对该新角色派工的任务，无需经过审批，能够保障任务的执行周期；对于派工者而言，只需在前期做好对角色的派工，在发生员工离职或调岗时都不再需要派工者进行任何操作，大大减少了派工者的工作量。
离职举例：派工者为“生产工人1”这一角色派发了任务A、B、C，员工张三关联“生产工人1”时，张三则获得了任务A、B、C，张三离职时，系统管理员（或相应管理员）直接取消张三与“生产工人1”这一角色的关联，无需由张三操作退回所派任务；新入职员工李四接替张三的工作内容和任务时，直接让李四关联“生产工人1”，则李四自动获得了对“生产工人1”这一角色所派的任务A、B、C，无需再为李四重新派工，操作简单快捷，大大减少了派工者的工作量。
调岗举例：员工张三要从生产部调岗到售后部，系统管理员（或相应管理员）取消张三与原角色“生产工人1”的关联，再关联到售后部的新角色“售后服务人员3”，张三则自动获得了对“售后服务人员3”这一角色所派的任务E、F。
（2）本申请提供了退回任务的功能，在特殊情况下（如时间冲突或没能力完成任务等）允许被派工的角色退回被派工的任务，退回任务需要填写原因，设计合理，使用方便。
举例：派工者分配了任务G给张三，且该任务时间紧迫必须在一周内完成，但张三最近一周恰好要出差，明显无法完成任务G，则张三可退回任务G，退回时可填写或选择退回原因。
（3）系统可设置需要被派工的角色或员工能够处理哪些任务，以及需要被派工的角色或员工处理相应任务的能力水平等级，便于派工者派工时进行选择和参考，有助于提高派工者派工的效率并提高派工的准确性和合理性。
举例：现有一维修难度较大的ULP5型号空调维修任务，派工者准备将该任务派发给售后部的售后服务人员，由于系统设置了每个员工能够处理哪些任务，派工者很快就能在售后服务人员当中找出能够维修ULP5型号空调的员工有哪些，随后考虑到该任务的维修难度较大，在能够维修ULP5型号空调的售后服务人员中选择维修空调的能力水平等级为五级（维修空调的能力水平等级分为一级、二级、……、五级，五级代表能力水平最高）的员工即可；又如也可：派工者派工时显示出能够维修ULP5型号空调的所有售后服务人员对应的用户关联的所有角色，并选择维修空调能力水平等级为五级的所有售后服务人员对应的用户关联的所有角色中的一个或多个角色（若一个用户关联了多个角色，则只能选择该用户关联的其中一个角色，因为用户与员工是1对1的关系），此时是对角色进行派工，在派工者派工时显示可派工的角色、角色关联的用户当前对应的员工、当前对应的员工能够处理的任务及相应任务的能力水平等级，这些信息的显示有利于对角色的派工；又如还可：对需要被派工的角色设置能够处理的任务及相应任务的能力水平等级，将符合该角色（岗位号/工位号）任务及能力水平要求的用户与该角色关联（即该用户对应员工符合该角色的任务及能力水平要求），则在派工时，直接选择能够满足被派工任务及要求的角色即可。
（4）本申请角色对用户是一对一的关系，同一时段一个角色只能关联唯一的用户，一个用户关联一个或多个角色，这样做的好处是，只要将用户关联到角色即可获得权限（即用户获得其关联的角色的权限），而且角色的权限变更比传统机制中的用户权限变更要少得多。独立体性质（岗位号/工位号性质）的角色数量变化小，虽然员工流动大，但岗位号/工位号的变化小（甚至在一定时段内是没有变化的，即角色没有变化），这样将极大简化用户的权限管理，减少系统的开销。
（5）动态管理、入职调岗等的操作简单方便，效率高，可靠性高：入职/离职/调岗在权限管理中的应用简单，当员工/用户发生变化时不用重新设置权限，用户只需取消或关联角色即可：不再任职该角色的用户就取消该角色关联，接手任职该角色的用户关联该岗位号的角色，关联该角色的用户自动就获得了该角色的相关任务和操作权限，无需对角色进行重新授权和派工，极大地提高了系统设置的效率、安全性和可靠性。
举例：因张三用户离职或调岗等原因，张三不再做“采购员3”这个角色的工作，则将张三取消与“采购员3”的关联；另外李四接手做“采购员3”这个角色的工作，只需将李四关联该角色，则李四自动获得了“采购员3”这个角色的权限和任务。
（6）传统的权限管理机制将角色定义为组、工种、类等性质，角色对用户是一对多的关系，在实际的系统使用过程中，因为在运营过程中经常需要对用户的权限进行调整，比如：在处理员工权限变化的时候，角色关联的某个员工的权限发生变化，我们不能因该个别员工权限的变化而改变整个角色的权限，因为该角色还关联了其他权限未变的员工。因此为了应对该种情况，要么创建新角色来满足该权限发生变化的员工，要么对该员工根据权限需求直接授权（脱离角色）。以上两种处理方式，在角色权限较多的情况下对角色授权不仅所需时间长，而且容易犯错，使用方操作起来繁琐又麻烦，也容易出错导致对系统使用方的损失。
但在本申请的方法下，因为角色是一个独立的个体，则可以选择改变角色权限即可达到目的。本申请的方法，虽然看起来在系统初始化时会增加工作量，但可以通过复制等方法，使其创建角色或授权的效率高于传统组/类性质的角色，因为不用考虑组/类性质角色在满足关联用户时的共通性，本申请方案会让权限设置清晰，明了；尤其是在系统使用一段时间后（用户/角色权限动态变化），该申请方案能为系统使用方大幅度提高系统使用中的权限管理效率，使动态授权更简单，更方便，更清晰、明了，提高权限设置的效率和可靠性。
（7）传统组/类性质的角色授权方法容易出错，本申请方法大幅降低了授权出错的几率，因为本申请方法只需考虑作为独立个体的角色，而不用考虑传统方法下关联该组性质角色的多个用户有哪些共通性。即使授权出错也只影响关联到该角色的那一个用户，而传统以组性质的角色则会影响关联到该角色的所有用户。即使出现权限授权错误，本申请的修正方法简单、时间短，而传统以组性质的角色在修正错误时需要考虑关联到该角色的所有用户的权限共通性，在功能点多的情况下不仅修改麻烦、复杂，非常容易出错，且很多情况下只能新创建角色才能解决。
（8）在传统以组为性质的角色授权方法下，若角色的权限功能点比较多，时间一长，很难记住角色的具体权限，更难记住权限相近的角色之间的权限差别，若要关联新的用户，无法准确判断应当如何选择关联。本申请方法的角色本身就具有岗位号/工位号的性质，选择一目了然。
（9）调岗时，若要将被调岗用户的很多个权限分配给另外几个用户承担，则处理时必须将被调岗用户的这些权限区分开来，分别再创建角色来关联另外几个用户，这样的操作不仅复杂耗时，而且还很容易发生错误。
本申请方法则为：被调岗用户关联了几个角色，在调岗时，首先取消用户与原部门内的角色的关联（被取消的这几个角色可以被重新关联给其他用户），然后将用户与新部门内的角色进行关联即可。操作简单，不会出错。
 附图说明
图1为背景技术中系统直接对用户进行授权的方式示意图；
图2为背景技术中系统对组/类性质角色进行授权的方式示意图；
图3为背景技术中系统对用户直接授权和对组/类性质角色授权相结合的方式示意图；
图4为本发明系统通过独立个体性质角色对用户进行授权的方式示意图；
图5为本发明派工流程图。
 本发明的实施方式
下面结合附图进一步详细描述本发明的技术方案，但本发明的保护范围不局限于以下所述。
【实施例1】如图5所示，一种系统派工方法，包括一个确定被派工任务的步骤、一个确定被派工对象的步骤和一个派工步骤；S1：确定被派工任务的步骤：确定需要进行派工的任务，任务可以是人工填写的内容，也可以是指定表单数据或指定的表单数据带出的内容（如派工去处理一个跟单，派工去处理一个投诉单、指定去处理一个安装请求单等），或者三者的组合；任务包括：生产性质任务、销售性质任务、物流性质任务、售后性质任务等需要派工处理的任务。
S2：确定被派工对象的步骤：确定被派工的对象，所述对象为角色，如图4所示，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色，一个用户对应一个员工，一个员工对应一个用户，用户通过其与角色的关联确定（获得）权限；所述用户在其对应的员工离职后被冻结，冻结的用户不能被其他员工对应/关联，若该员工离职一段时间又回到公司（入职），则原来该员工被冻结的用户被解冻并继续对应该员工（即该员工继续使用该用户）。
所述的角色必须选择一个部门，角色一旦选择部门后则该角色归属于该部门，该角色的名称在该部门下唯一，角色的编号在系统中唯一，根据角色的工作内容对角色进行授权。
S3：派工步骤：将需要进行派工的任务派发给被派工的角色，派工后生成派工单，由被派工的角色关联的用户对应的员工获得所派任务。派工单可以关联相关表单数据，比如售后派工单关联售后请求单。
被派工的角色可以选择是否接受派工。
被派工的角色为一个或多个，当被派工的角色为多个时，需要指定一个负责角色。例如，一个大型设备的维修任务，可能需要多个售后服务人员配合完成维修工作，这种情况下可将该维修任务派工给多个售后服务人员，指定其中一个作为负责角色。
【实施例2】如图5所示，一种系统派工方法，包括一个确定被派工任务的步骤、一个确定被派工对象的步骤和一个派工步骤；SS1：确定被派工对象的步骤：确定被派工的对象，所述对象为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；SS2：确定被派工任务的步骤：确定需要进行派工的任务；SS3：派工步骤：派工者将需要进行派工的任务派发给被派工的角色，被派工的角色关联的用户对应的员工获得所派任务。派工者可以是角色、用户或者人等。
如果用户需要跨部门调岗，还包括一个用户跨部门调岗管理步骤，具体包括：（1）取消用户与原部门内的角色的关联；（2）将用户与新部门内的角色进行关联，用户自动获得对该新角色派工的任务。
本申请将任务派发给角色，员工通过对应的用户关联的角色获得被派工的任务，员工离职时，直接由系统管理员（或相应管理员）取消该员工对应的用户与角色的关联，新入职员工接替离职员工的任务时，直接让新入职员工关联该角色即可，无需依赖离职员工退回任务，也无需为新入职员工重新派工，实现了人员变动的无缝对接，操作方便快捷；员工调岗时，直接由系统管理员（或相应管理员）取消该员工与原角色的关联，再关联新的角色即可自动获得对该新角色派工的任务，无需经过审批，能够保障任务的执行周期；对于派工者而言，只需在前期做好对角色的派工，在发生员工离职或调岗时都不再需要派工者进行任何操作，大大减少了派工者的工作量。
离职举例：派工者为“生产工人1”这一角色派发了任务A、B、C，员工张三关联“生产工人1”时，张三则获得了任务A、B、C，张三离职时，系统管理员（或相应管理员）直接取消张三与“生产工人1”这一角色的关联，无需由张三操作退回所派任务；新入职员工李四接替张三的工作内容和任务时，直接让李四关联“生产工人1”，则李四自动获得了对“生产工人1”这一角色所派的任务A、B、C，无需再为李四重新派工，操作简单快捷，大大减少了派工者的工作量。
调岗举例：员工张三要从生产部调岗到售后部，系统管理员（或相应管理员）取消张三与原角色“生产工人1”的关联，再关联到售后部的新角色“售后服务人员3”，张三则自动获得了对“售后服务人员3”这一角色所派的任务E、F。
【实施例3】如图5所示，一种系统派工方法，包括一个确定被派工任务的步骤、一个确定被派工对象的步骤和一个派工步骤；S1：确定被派工任务的步骤：确定需要进行派工的任务；S2：确定被派工对象的步骤：确定被派工的对象，所述对象为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；S3：派工步骤：将需要进行派工的任务派发给被派工的角色，被派工的角色关联的用户对应的员工获得所派任务。派工安排的时间是一个时间段，而不是确切时间点，只要在这个时间段内完成都算正常完成。
还包括一个退回任务的步骤，被派工的角色通过该步骤退回被派工的任务。在特殊情况下允许被派工的角色退回被派工的任务，设计合理，使用方便。
举例：派工者分配了任务G给张三，且该任务时间紧迫必须在一周内完成，但张三最近一周恰好要出差，明显无法完成任务G，则张三可退回任务G，退回时可填写或选择退回原因。
因为被派工的角色是工位号、岗位号性质的独立个体，可对角色设置能够处理哪些任务及对应的能力水平级别，那么关联该岗位号的用户对应的员工都应该具备该岗位号要求的工作能力，则该角色关联的用户对应的员工应该都能完成派给该岗位号的任务。
设置派工者的派工权限，即派工者能对哪些角色进行派工，具体方式包括：（1）设置可被该派工者派工的部门（包括后续部门下增加的所有角色）；例如：生产一部的车间主任只能派工给生产一部的生产工人。
（2）设置可被该派工者派工的角色。传统方法可被派工的是人/员工，比如派工者K可派工的人有100个，其中包括某员工A，A离职后由新入职员工B来替代A的工作，则在未设置之前，派工者K无法对B进行直接派工，因为B不在可被其派工的范围内。而本申请可被派工的是角色，A之前所关联的角色M是派工者K可派工的角色，B入职后，取消A与角色M的关联，再将B与角色M关联，则派工者K自动的就能对B进行派工，无需进行任何设置，而传统方法在人员频繁变动时需要不断地设置可被派工的人/员工，操作麻烦，而且会影响正常的工作开展。
【实施例4】如图5所示，一种系统派工方法，包括一个确定被派工任务的步骤、一个确定被派工对象的步骤和一个派工步骤；S1：确定被派工任务的步骤：确定需要进行派工的任务；S2：确定被派工对象的步骤：确定被派工的对象，所述对象为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；S3：派工步骤：将需要进行派工的任务派发给被派工的角色，被派工的角色关联的用户对应的员工获得所派任务。
本实施例中，还包括一个设置需要被派工的角色或员工能够处理的任务的步骤。进一步的，还包括一个设置需要被派工的角色或员工处理相应任务的能力水平等级的步骤。
确定被派工任务后，选择被派工者时，弹出所有能够处理该任务的人，再选择其中符合该任务要求的能力水平等级的人（高能力水平等级的员工能够处理低能力水平等级要求的任务）。
系统可设置需要被派工的角色或员工能够处理哪些任务，以及需要被派工的角色或员工处理相应任务的能力水平等级，便于派工者派工时进行选择和参考，有助于提高派工者派工的效率并提高派工的准确性和合理性。
举例：现有一维修难度较大的ULP5型号空调维修任务，派工者准备将该任务派发给售后部的售后服务人员，由于系统设置了每个员工能够处理哪些任务，派工者很快就能在售后服务人员当中找出能够维修ULP5型号空调的员工有哪些，随后考虑到该任务的维修难度较大，在能够维修ULP5型号空调的售后服务人员中选择维修空调的能力水平等级为五级（维修空调的能力水平等级分为一级、二级、……、五级，五级代表能力水平最高）的员工即可。
【实施例5】如图5所示，一种系统派工方法，包括一个确定被派工任务的步骤、一个确定被派工对象的步骤和一个派工步骤；S1：确定被派工任务的步骤：确定需要进行派工的任务；S2：确定被派工对象的步骤：确定被派工的对象，所述对象为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；S3：派工步骤：将需要进行派工的任务派发给被派工的角色，被派工的角色关联的用户对应的员工获得所派任务。
还包括一个设置任务紧急度的步骤，派工者在进行派工时选择一个任务紧急度，被派工角色收到任务时将显示该任务的紧急度。比如：分为5级(立即/优先/正常/置后/最后)，派工时默认为正常，派工者在派工的时候可以修改。
上述实施例中，如图4所示，本申请被派工的对象为独立个体性质角色，以下对通过独立个体性质角色对用户进行授权所具备的优势进行分析：用户通过其与角色的关联确定（获得）权限，如果要修改用户的权限，通过调整角色所拥有的权限以达到改变关联了该角色的用户的权限的目的。一旦用户关联角色后，该用户就拥有了该角色的所有操作权限。
角色对用户的关系为一对一（该角色与一个用户关联时，其他用户则不能再关联该角色；若该角色未被用户关联，则可以被其他用户选择关联；即同一时段，一个角色能且只能被一个用户关联）。用户对角色的关系为一对多（一个用户可以同时关联多个角色）。
角色的定义：角色不具有组/类/类别/岗位/职位/工种等性质，而是一个非集合的性质，角色具有唯一性，角色是独立存在的独立个体；在企事业单位应用中相当于岗位号（此处的岗位号非岗位，一个岗位同时可能有多个员工，而同一时段一个岗位号只能对应一个员工）。
举例：某个公司系统中可创建如下角色：总经理、副总经理1、副总经理2、北京销售一部经理、北京销售二部经理、北京销售三部经理、上海销售工程师1、上海销售工程师2、上海销售工程师3、上海销售工程师4、上海销售工程师5……用户与角色的关联关系：若该公司员工张三任职该公司副总经理2，同时任职北京销售一部经理，则张三需要关联的角色为副总经理2和北京销售一部经理，张三拥有了这两个角色的权限。
传统角色的概念是组/类/岗位/职位/工种性质，一个角色能够对应多个用户。而本申请“角色”的概念相当于岗位号/工位号，也类同于影视剧中的角色：一个角色在同一时段（童年、少年、中年……）只能由一个演员来饰演，而一个演员可能会分饰多角。
可以在创建用户的过程中关联角色，也可以在用户创建完成后随时关联角色。用户关联角色后可以随时解除与角色的关联关系，也可以随时建立与其他角色的关联关系。
所述角色的构成为：岗位名+岗内编号。例如：车间生产工人1、车间生产工人2、车间生产工人3……角色是独立个体，相当于岗位号、工位号的概念，不同于传统权限管理体系中的角色，传统体系中角色的概念是岗位/职位/工种等的组/类性质。
以下举例员工张三进入某公司后，员工、用户与角色之间的关系为：1、新入职：员工新入职，直接为该用户（员工）选择相应的岗位号/工位号的角色进行关联即可，例：张三入职公司（公司为张三分配了一个张三用户），工作内容是在销售一部，负责北京区域冰箱产品的销售（对应的角色是销售一部下的“销售工程师5”这个角色），则张三用户直接选择“销售工程师5”这个角色关联即可。
2、增加职位：张三工作一段时间后，公司还安排张三负责北京区域电视产品的销售（对应的角色是销售一部下的“销售工程师8”这个角色）并兼任售后部主管（对应售后部主管1这个角色），则张三用户再增加关联销售一部下的“销售工程师8”和售后部下的“售后部主管1”这两个角色，此时，张三员工关联了三个角色，分别为销售一部下的“销售工程师5”、“销售工程师8”和售后部下的“售后部主管1”，张三用户则拥有了这三个角色的权限。
3、减少职位：又过了一段时间，公司决定让张三任职售后部经理（对应售后部下“售后部经理”这个角色），且不再兼任其他工作。则张三用户关联售后部下“售后部经理”这个角色，同时取消此前关联的三个角色（销售一部下的“销售工程师5”、“销售工程师8”和售后部下的“售后部主管1”），此时，张三用户只拥有售后部下“售后部经理”这个角色的权限。
4、角色权限的调整（针对角色本身所拥有的权限的调整）：如公司决定增加售后部经理的权限，则只需增加对售后部经理这个角色的授权即可，则张三用户因为售后部经理这个角色的权限增加了，张三用户的权限也增加了。
5、离职：一年后，张三离职了，则取消张三用户与售后部下“售后部经理”这个角色的关联即可。
举例：公司在动态的经营中，职员的入职、离职是经常持续发生的，但岗位号/工位号的变化非常少(甚至在一定时期内是没有变化的)。
传统授权方法：在系统功能点多的情况下，以传统的组/类性质的角色进行授权，不仅授权工作量大，繁杂，而且很容易出错，甚至出错了在短时间内都不容易发现，容易对系统使用方造成损失。
本申请授权方法：本申请是对岗位号/工位号性质的角色进行授权，用户关联角色而确定（获得）权限，则对用户权限的控制，通过简单的用户-角色的关联关系来实现，让权限控制变得简单、易操作，清晰明了，大幅度提高了授权效率和授权可靠性。
以上所述仅是本发明的优选实施方式，应当理解本发明并非局限于本文所披露的形式，不应看作是对其他实施例的排除，而可用于各种其他组合、修改和环境，并能够在本文所述构想范围内，通过上述教导或相关领域的技术或知识进行改动。而本领域人员所进行的改动和变化不脱离本发明的精神和范围，则都应在本发明所附权利要求的保护范围内。

Claims (10)

  1. 一种系统派工方法，其特征在于，包括一个确定被派工任务的步骤、一个确定被派工对象的步骤和一个派工步骤，确定被派工任务的步骤和确定被派工对象的步骤顺序不分先后；
    确定被派工任务的步骤：确定需要进行派工的任务；
    确定被派工对象的步骤：确定被派工的对象，所述对象为角色，所述角色是独立的个体，而非组/类，同一时段一个角色只能关联唯一的用户，而一个用户关联一个或多个角色；
    派工步骤：将需要进行派工的任务派发给被派工的角色，被派工的角色关联的用户对应的员工获得所派任务。
  2. 根据权利要求1所述的一种系统派工方法，其特征在于：还包括一个退回任务的步骤，被派工的角色通过该步骤退回被派工的任务。
  3. 根据权利要求1所述的一种系统派工方法，其特征在于：还包括被派工的角色选择是否接受派工的步骤。
  4. 根据权利要求1所述的一种系统派工方法，其特征在于：所述的角色必须选择一个部门，角色一旦选择部门后则该角色归属于该部门，该角色的名称在该部门下唯一，角色的编号在系统中唯一，根据角色的工作内容对角色进行授权。
  5. 根据权利要求3所述的一种系统派工方法，其特征在于：还包括一个用户跨部门调岗管理步骤，具体包括：
    （1）取消用户与原部门内的角色的关联；
    （2）将用户与新部门内的角色进行关联，用户自动获得对该新角色派工的任务。
  6. 根据权利要求1所述的一种系统派工方法，其特征在于：一个用户对应一个员工，一个员工对应一个用户，用户通过其与角色的关联确定权限。
  7. 根据权利要求1所述的一种系统派工方法，其特征在于：还包括一个设置需要被派工的角色或员工能够处理的任务的步骤；和/或还包括一个设置需要被派工的角色或员工处理相应任务的能力水平等级的步骤。
  8. 根据权利要求1所述的一种系统派工方法，其特征在于：设置派工者的派工权限，即派工者能对哪些角色进行派工，具体方式包括以下一种或两种的组合：
    （1）设置可被该派工者派工的部门；
    （2）设置可被该派工者派工的角色。
  9. 根据权利要求1所述的一种系统派工方法，其特征在于：被派工的角色为一个或多个，当被派工的角色为多个时，需要指定一个负责角色。
  10. 根据权利要求1所述的一种系统派工方法，其特征在于：还包括一个设置任务紧急度的步骤，派工者在进行派工时选择一个任务紧急度，被派工角色收到任务时将显示该任务的紧急度。
PCT/CN2018/096345 2017-07-20 2018-07-19 一种系统派工方法 WO2019015656A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710596958.5 2017-07-20
CN201710596958.5A CN107368968A (zh) 2017-07-20 2017-07-20 一种系统派工方法

Publications (1)

Publication Number Publication Date
WO2019015656A1 true WO2019015656A1 (zh) 2019-01-24

Family

ID=60306928

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/096345 WO2019015656A1 (zh) 2017-07-20 2018-07-19 一种系统派工方法

Country Status (2)

Country Link
CN (2) CN107368968A (zh)
WO (1) WO2019015656A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107368968A (zh) * 2017-07-20 2017-11-21 成都牵牛草信息技术有限公司 一种系统派工方法
CN107360083A (zh) * 2017-07-29 2017-11-17 成都牵牛草信息技术有限公司 根据角色间的通讯关系预设即时通讯账号联系人及预设通讯录的方法
CN108197838A (zh) * 2018-02-08 2018-06-22 广东电网有限责任公司江门供电局 一种电力施工作业风险管控方法
CN108665154A (zh) * 2018-04-26 2018-10-16 上海韦地计算机科技有限公司 一种航空产品生产过程执行管理系统
CN108965109B (zh) * 2018-06-27 2021-08-31 腾讯科技（深圳）有限公司 一种即时通讯控制方法、装置及存储介质
CN111695747A (zh) * 2019-03-13 2020-09-22 鸿富锦精密电子（成都）有限公司 智能派工方法、装置及计算机可读储存介质
CN110020813A (zh) * 2019-04-18 2019-07-16 厦门烟草工业有限责任公司 工单管理方法、装置和计算机可读存储介质
CN112884335A (zh) * 2021-03-03 2021-06-01 银清科技有限公司 一种多角色人员安排与任务分派方法、装置及系统
CN113592106B (zh) * 2021-07-07 2023-12-19 杭州智果科技有限公司 一种工单服务系统
CN117132171B (zh) * 2023-10-26 2024-01-02 江苏工小兔信息科技有限公司 一种自动化的办公信息管理系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102468971A (zh) * 2010-11-04 2012-05-23 北京北方微电子基地设备工艺研究中心有限责任公司 权限管理方法和装置、权限控制方法和装置
US20140228976A1 (en) * 2013-02-12 2014-08-14 Nagaraja K. S. Method for user management and a power plant control system thereof for a power plant system
CN105809329A (zh) * 2016-02-29 2016-07-27 江苏省电力公司张家港市供电公司 一种电力呼叫抢修系统及工单接收装置
CN106485417A (zh) * 2016-10-17 2017-03-08 南京国电南自电网自动化有限公司 基于动态自适应任务调度策略的光伏电站移动运维方法
CN106845809A (zh) * 2017-01-11 2017-06-13 东方航空技术有限公司 一种机务航线派工方法、系统及装置、派工系统
CN107368968A (zh) * 2017-07-20 2017-11-21 成都牵牛草信息技术有限公司 一种系统派工方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101159053A (zh) * 2007-11-23 2008-04-09 金蝶软件（中国）有限公司 一种资源分配方法及系统
CN104715313A (zh) * 2013-12-12 2015-06-17 笛飞儿顾问有限公司 派工管理系统及其方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102468971A (zh) * 2010-11-04 2012-05-23 北京北方微电子基地设备工艺研究中心有限责任公司 权限管理方法和装置、权限控制方法和装置
US20140228976A1 (en) * 2013-02-12 2014-08-14 Nagaraja K. S. Method for user management and a power plant control system thereof for a power plant system
CN105809329A (zh) * 2016-02-29 2016-07-27 江苏省电力公司张家港市供电公司 一种电力呼叫抢修系统及工单接收装置
CN106485417A (zh) * 2016-10-17 2017-03-08 南京国电南自电网自动化有限公司 基于动态自适应任务调度策略的光伏电站移动运维方法
CN106845809A (zh) * 2017-01-11 2017-06-13 东方航空技术有限公司 一种机务航线派工方法、系统及装置、派工系统
CN107368968A (zh) * 2017-07-20 2017-11-21 成都牵牛草信息技术有限公司 一种系统派工方法

Also Published As

Publication number Publication date
CN108932610B (zh) 2021-04-06
CN107368968A (zh) 2017-11-21
CN108932610A (zh) 2018-12-04

Similar Documents

Publication Publication Date Title
WO2019015656A1 (zh) 一种系统派工方法
CN108764833B (zh) 工作流审批节点按部门设置审批角色的方法
WO2018196876A1 (zh) 基于角色对用户一对一的工作流控制方法和系统
WO2019007260A1 (zh) 表单字段值操作权限授权方法
WO2019011220A1 (zh) 基于依据字段设置审批流程的方法
WO2018210248A1 (zh) 基于表单字段的工作流审批节点设置审批角色的方法
WO2019029650A1 (zh) 表单数据操作的审核方法
WO2018224024A1 (zh) 工作流审批节点高效审批方法
EP3661119A1 (en) Method for managing instant messaging account in management system
WO2019007292A1 (zh) 基于角色的表单操作权限授权方法
WO2019029501A1 (zh) 统计列表操作权限授权方法
CN107045675A (zh) 工作流审批节点按角色设置审批角色的方法
JP7231910B2 (ja) フォームデータの操作権限を承認する方法
WO2018205942A1 (zh) 工作流审批节点按部门级别设置审批角色的方法
WO2018192557A1 (zh) 基于角色对用户的一对一的权限授权方法和系统
WO2019007210A1 (zh) 一种表单的关联信息授权方法
WO2019007291A1 (zh) 根据表单字段值对表单操作权限进行分别授权的方法
WO2019011162A1 (zh) 快捷功能设置方法
WO2019029648A1 (zh) 基于改进型rbac权限控制机制的审批任务转交方法
CN109102253A (zh) 审批者针对审批任务征询参考意见的方法
CN107292580A (zh) 审批工作流的委托及其再委托方法
CN108985648B (zh) 管理系统中事务处理的管理方法
WO2018205940A1 (zh) 基于角色对用户的一对一的组织结构图生成及应用方法
US11632348B2 (en) Method for acquiring mail box account in system
WO2019029500A1 (zh) 基于列值对统计列表操作权限进行分别授权的方法

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: 18835099

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: 18835099

Country of ref document: EP

Kind code of ref document: A1