JP2011232788A - Workflow management system, workflow management method, and workflow management program - Google Patents

Workflow management system, workflow management method, and workflow management program Download PDF

Info

Publication number
JP2011232788A
JP2011232788A JP2010099588A JP2010099588A JP2011232788A JP 2011232788 A JP2011232788 A JP 2011232788A JP 2010099588 A JP2010099588 A JP 2010099588A JP 2010099588 A JP2010099588 A JP 2010099588A JP 2011232788 A JP2011232788 A JP 2011232788A
Authority
JP
Japan
Prior art keywords
user
task
execution
execution pattern
workflow management
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
JP2010099588A
Other languages
Japanese (ja)
Inventor
Takatoshi Kitamura
隆俊 北村
Original Assignee
Nec Corp
日本電気株式会社
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 Nec Corp, 日本電気株式会社 filed Critical Nec Corp
Priority to JP2010099588A priority Critical patent/JP2011232788A/en
Publication of JP2011232788A publication Critical patent/JP2011232788A/en
Pending legal-status Critical Current

Links

Images

Abstract

PROBLEM TO BE SOLVED: To dissolve deviation of the number of task allocation.SOLUTION: An execution pattern setting section 11 for setting execution patterns of each user to any one of a batch execution pattern or a sequential execution pattern for every task on the basis of execution history information in an execution history database 21, and an allocated user determination section 12 for determining a user to whom a predetermined unallocated task is allocated from users who are to be allocation objects by using an execution pattern that is set to a user who is to be an allocation object and the number of predetermined unexecuted tasks that is retained by the user who is to be an allocation object are included.

Description

  The present invention relates to a workflow management system, a workflow management method, and a workflow management program.

  The workflow management system is a system that manages a series of flow of business procedures. The workflow management system supports smooth execution of business procedures by sequentially assigning and executing operations included in business procedures (hereinafter referred to as “tasks”) to users. For example, the workflow management system of Patent Document 1 notifies all execution candidate users that a task can be processed, and allows only the user who first clicked the start button to execute the task. Exclusive control is possible. Further, the workflow management system of Patent Document 2 prevents tasks from being concentrated on a specific user by not assigning tasks to users who have refused assignment when assigning tasks.

JP 2001-319183 A JP 2009-205341 A

  In the workflow management systems of Patent Literature 1 and Patent Literature 2 described above, tasks are not assigned to users who do not click the start button or to users who have refused assignment, so the number of task assignments may be biased among users.

  SUMMARY An advantage of some aspects of the invention is that it provides a workflow management system, a workflow management method, and a workflow management program that can eliminate a bias in the number of task assignments.

  The workflow management system of the present invention includes, for each identification information of a user who executes a task included in the workflow, at least the identification information of the task, an allocation time when the task is allocated to the user, and the user executes the task A storage unit that stores execution history information including the execution time, and before assigning the unassigned task to any of the users, the user to be assigned when assigning the unassigned task, Based on the execution history information, an execution pattern setting unit that sets one of a plurality of predetermined execution patterns as an execution pattern for executing the task, and the execution set by the user to be assigned Pattern and the number of unexecuted tasks held by the user to be assigned There are, among the user to be the allocation target, and a assigner determination unit configured to determine the user to assign the task of the unassigned.

  According to the workflow management method of the present invention, for each identification information of a user who executes a task included in the workflow, at least the identification information of the task, an allocation time at which the task is allocated to the user, and the user executes the task A workflow management method executed in a workflow management system including a storage unit that stores execution history information including an execution time, and before assigning the unassigned task to any of the users, the unassigned An execution pattern setting step for setting the user to be assigned when assigning a task to one of a plurality of predetermined execution patterns as an execution pattern for executing the task, based on the execution history information; The execution pattern set for the user to be assigned And the number of unexecuted tasks held by the user to be allocated, and the allocated user who determines the user to which the unallocated task is allocated from among the users to be allocated And a determination step.

  The workflow management program of the present invention causes a computer to execute each step included in the workflow management method.

  According to the present invention, it is possible to eliminate a bias in the number of tasks allocated.

It is a block diagram which illustrates typically the composition of the workflow management system in an embodiment. It is a figure which illustrates the data structure of an execution history database. It is a figure which illustrates the data structure of an execution pattern database. It is the figure which illustrated the information regarding the predetermined task of a predetermined user in tabular form in order to explain pattern setting processing. It is a flowchart for demonstrating the process sequence of a pattern setting process. It is a flowchart for demonstrating the process sequence of an allocation user determination process.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments of a workflow management system, a workflow management method, and a workflow management program according to the present invention will be described with reference to the accompanying drawings.

  First, the configuration of a workflow management system in the embodiment will be described with reference to FIG. FIG. 1 is a configuration diagram schematically showing a workflow management system in the embodiment.

  First, the configuration of a workflow management system in the embodiment will be described with reference to FIG. The workflow management system 1 includes a server device 10, a DB device 20, and a user terminal 30.

  The DB device 20 manages various databases referred to by the server device 10. Examples of the various databases include an execution history database 21 and an execution pattern database 22. The execution history database 21 and the execution pattern database 22 may be provided in the server device 10.

  The data structure of the execution history database 21 will be described with reference to FIG. The execution history database 21 manages execution history information related to tasks executed by the user. As data items constituting the execution history information, for example, there are a user ID item, a task ID item, an assigned time item, and an execution time item. The user ID item stores identification information that uniquely identifies the user. The task ID item stores identification information that uniquely identifies a task. The allocation time item stores the time when the task is allocated to the user. The execution time item stores the time when the user executed the task.

  The data configuration of the execution pattern database 22 will be described with reference to FIG. The execution pattern database 22 manages execution pattern information related to execution patterns when a user executes a task. Examples of data items constituting the execution pattern information include a user ID item, a task ID item, an execution pattern item, and a threshold item. The user ID item stores identification information that uniquely identifies the user. The task ID item stores identification information that uniquely identifies a task. The execution pattern item stores an execution pattern when the user executes a task. Examples of execution patterns include a batch execution pattern and a sequential execution pattern. The batch execution pattern is a pattern in which a task is executed after a plurality of tasks are assigned. The sequential execution pattern is a pattern in which a task is executed every time a task is assigned. The threshold item is a value that is referred to when a task is assigned to a user of a batch execution pattern, and is a value that can be determined to execute a task when the number of unexecuted tasks becomes larger than this value.

  The DB device 20 may further include a workflow database that manages various types of information used when executing business procedures. Examples of the various types of information include business procedure information regarding business procedures, task information regarding tasks, user information regarding users, user terminal information regarding user terminals, and the like.

  Functionally, the server device 10 illustrated in FIG. 1 includes, for example, an execution pattern setting unit 11, an assigned user determination unit 12, and a workflow control unit 13.

  Here, the server device 10 physically includes, for example, a CPU (Central Processing Unit), a memory, a storage device, and an input / output interface. The storage device includes, for example, a ROM (Read Only Memory) and HDD (Hard Disk Drive) that store programs and data processed by the CPU, and a RAM (Random Access Memory) mainly used as various work areas for control processing. ) Is included. These elements are connected to each other via a bus. The CPU executes a program stored in the ROM and processes messages received via the input / output interface and data expanded in the RAM, thereby realizing functions of each unit in the server device 10 to be described later. Can do.

  The execution pattern setting unit 11 uses the execution history information stored in the execution history database 21 to set the execution pattern of each user as either a batch execution pattern or a sequential execution pattern for each task. Execute the process. The execution pattern setting unit 11 registers execution pattern information generated by executing the pattern setting process in the execution pattern database 22. The execution pattern setting unit 11 sequentially executes pattern setting processing for all users.

  The execution pattern setting unit 11 starts the pattern setting process when receiving a request for starting the pattern setting process from the outside. An example of the pattern setting process executed by the execution pattern setting unit 11 will be described below with reference to FIG. FIG. 4 is a diagram showing information related to a predetermined task of a predetermined user in a tabular format for explaining the pattern setting process. The allocation time shown in FIG. 4 is a time corresponding to the allocation time shown in FIG. The allocation interval is an interval between allocation times. The average allocation interval is an average value of the allocation intervals. The execution time is a time corresponding to the execution time shown in FIG. The execution interval is an interval between execution times. The number of remaining tasks is the number of tasks remaining unexecuted when executing the tasks. The number of remaining tasks is counted when the task is first executed and when the task is executed at an execution interval longer than the average allocation interval. The average remaining task is an average value of the number of remaining tasks. The threshold value is a value corresponding to the threshold value shown in FIG. As this threshold value, for example, a value obtained by adding 1 to the value obtained by rounding up the number of remaining tasks after the decimal point can be used.

  First, the execution pattern setting unit 11 calculates an average allocation interval for each task based on the allocation time of the execution history information. This will be specifically described with reference to FIG. The execution pattern setting unit 11 sequentially calculates the allocation interval using each allocation time of the execution history information, and calculates the average allocation interval by calculating the average value of the calculated allocation intervals. In this embodiment, since no task occurs outside business hours from 18:00 to 8:00, this time slot is excluded from the allocation interval calculation target.

  Subsequently, the execution pattern setting unit 11 calculates the average number of remaining tasks using the number of tasks remaining unexecuted when the tasks are executed. This will be specifically described with reference to FIG. The execution pattern setting unit 11 sequentially calculates execution intervals using each execution time of the execution history information. In this embodiment, since no task occurs outside business hours from 18:00 to 8:00, this time period is excluded from the execution interval calculation target. The execution pattern setting unit 11 sets the time when the task is executed for the first time and the time when the task is executed at an execution interval longer than the average allocation interval as a target for counting the number of remaining tasks. On the other hand, when the task is executed at an execution interval shorter than the average allocation interval, the execution pattern setting unit 11 sets the remaining number of tasks out of the count target. The execution pattern setting unit 11 counts the number of remaining tasks that have not been executed as the number of remaining tasks when the task set as the count target is executed. The execution pattern setting unit 11 calculates the average number of remaining tasks by calculating the average value of the calculated number of remaining tasks.

  Subsequently, when the average number of remaining tasks is less than 1, the execution pattern setting unit 11 sets the execution pattern when the predetermined user executes the predetermined task as the sequential execution pattern, and the execution pattern item of the execution pattern information To store. On the other hand, when the average number of remaining tasks is 1 or more, the execution pattern setting unit 11 sets the execution pattern when the predetermined user executes the predetermined task as a batch execution pattern, and sets the execution pattern item in the execution pattern information. Store.

  This is because a user who executes a task every time a task is assigned does not have a predetermined unexecuted task remaining when executing a predetermined task. The user's execution pattern is set as a sequential execution pattern. On the other hand, when a user who executes a task after a plurality of tasks are assigned, when executing the predetermined task, it is considered that the predetermined task that has not yet been executed remains, and therefore when the average number of remaining tasks becomes 1 or more. The user's execution pattern is set as a batch execution pattern.

  Subsequently, when the user's execution pattern is set as a batch execution pattern, the execution pattern setting unit 11 sets a value obtained by adding 1 to the value obtained by rounding up the average remaining task number after the decimal point. To store.

  Subsequently, the execution pattern setting unit 11 registers the generated execution pattern information in the execution pattern database 22.

  The assigned user determination unit 12 shown in FIG. 1 determines the user to which the unassigned predetermined task is assigned using the execution pattern set for the user and the number of unexecuted predetermined tasks held by the user. Execute the process. The assigned user determining unit 12 starts an assigned user determining process when a task assigned to a user is generated by the workflow control unit 13. An example of the allocation user determination process executed by the allocation user determination unit 12 will be described below.

  First, the allocated user determination unit 12 selects a user who can execute a predetermined task that is not allocated from among all users. The selection of the user may be performed based on the execution history information in the execution history database 21 or may be performed based on various information in the workflow database. Subsequently, the assigned user determination unit 12 acquires execution pattern information of each user from the execution pattern database 22.

  Subsequently, when the execution pattern of the user is a batch execution pattern, the assigned user determination unit 12 acquires the number of unexecuted tasks and the threshold corresponding to the predetermined task of the user from the execution history database 21. When the number of unexecuted tasks is smaller than the threshold, the assigned user determining unit 12 makes this user a candidate for assigning a predetermined task. On the other hand, if the user execution pattern is a sequential execution pattern, the assigned user determination unit 12 acquires the number of unexecuted tasks corresponding to the predetermined task of the user from the execution history database 21. When the number of unexecuted tasks is 0, the allocation user determination unit 12 sets this user as a candidate to allocate a predetermined task.

  Subsequently, the assigned user determining unit 12 calculates the number of task executions per unit time of each user that is a candidate for assignment of the predetermined task. Subsequently, the allocated user determination unit 12 determines a user corresponding to the minimum task execution number among the calculated task execution numbers as a user to which a predetermined task is allocated.

  The workflow control unit 13 illustrated in FIG. 1 controls a workflow by executing a business procedure described in a language such as BPEL (Business Process Execution Language) or XPDL (XML Process Definition Language). The workflow control unit 13 performs, for example, status management of business procedures, management of data used in business procedures, assignment of tasks to users, notification of task information to the user terminal 30, task status management, and the like. The workflow control unit 13 executes a business procedure and assigns a task to the user determined by the allocation user determination unit 12 when a task to be allocated occurs.

  The user terminal 30 illustrated in FIG. 1 displays task information notified from the server device 10. When executing the task, the user terminal 30 transmits the task execution start / end, the task execution result, and the like to the server device 10.

  Next, the operation of the workflow management system in the embodiment will be described with reference to the drawings. With reference to FIG. 5, the process procedure of a pattern setting process is demonstrated.

  First, when a pattern setting process start request is received from the outside, the execution pattern setting unit 11 is a setting target for setting an execution pattern based on the execution history information stored in the execution history database 21. A user is selected (step S101).

  Subsequently, the execution pattern setting unit 11 selects a setting target task for which an execution pattern is to be set based on the execution history information of the setting target user selected in step S101 (step S102).

  Subsequently, the execution pattern setting unit 11 sets an execution pattern when the setting target user executes the setting target task based on the execution history information of the setting target task selected in step S102 (step S103). If the execution pattern is a batch execution pattern, a threshold value is calculated in addition to the execution pattern setting.

  Subsequently, the execution pattern setting unit 11 generates execution pattern information using the execution pattern set in step S103 and registers it in the execution pattern database 22 (step S104).

  Subsequently, the execution pattern setting unit 11 determines whether or not execution patterns have been set for all tasks of the setting target user (step S105). If this determination is NO (step S105; NO), the process proceeds to step S102.

  On the other hand, when it is determined in the determination in step S105 that execution patterns have been set for all tasks (step S105; YES), the execution pattern setting unit 11 determines whether execution patterns have been set for all users. (Step S106). If this determination is NO (step S106; NO), the process proceeds to step S101. On the other hand, if it is determined in step S106 that execution patterns have been set for all users (step S106; YES), the pattern setting process ends.

  With reference to FIG. 6, the processing procedure of the allocated user determination processing will be described.

  First, when the workflow control unit 13 generates a predetermined task to be assigned to a user, the assigned user determination unit 12 selects one candidate user from among users who can execute the predetermined task (step S201), and further compares One user is selected (step S202).

  Subsequently, the assigned user determining unit 12 determines whether or not the comparison target user has an unexecuted predetermined task based on the execution history information of the comparison target user selected in step S202 (step S203). If this determination is NO (step S203; NO), it can be determined that the predetermined task is not assigned to the comparison target user and the comparison target user is in a state where the predetermined task can be executed. Therefore, in this case, the process proceeds to step S206 described later.

  On the other hand, when it is determined in step S203 that the comparison target user has an unexecuted predetermined task (step S203; YES), the assigned user determination unit 12 is based on the execution pattern information of the comparison target user. Then, it is determined whether or not the execution pattern of the comparison target user is a batch execution pattern (step S204). If this determination is NO (step S204; NO), the execution pattern of the comparison target user is a sequential execution pattern, and a predetermined task that has not been executed remains, so that the task can be executed for some reason. It can be determined that it is not in a state. Therefore, in this case, the process proceeds to step S202 without setting the comparison target user as a candidate for assignment of the predetermined task.

  On the other hand, when it is determined in the determination in step S204 that the execution pattern of the comparison target user is a batch execution pattern (step S204; YES), the assigned user determination unit 12 It is determined whether the number of unexecuted predetermined tasks held by the comparison target user is greater than a threshold value (step S205). If this determination is YES (step S205; YES), the execution pattern of the comparison target user is a batch execution pattern, and there remains an unexecuted predetermined task that exceeds the threshold for executing the task in a batch. Therefore, it can be determined that the task cannot be executed for some reason. Therefore, in this case, the process proceeds to step S202 without setting the comparison target user as a candidate for assignment of the predetermined task.

  On the other hand, when it is determined in the determination in step S205 that the number of unexecuted predetermined tasks held by the comparison target user is equal to or less than the threshold (step S205; NO), the comparison target user has the number of predetermined tasks allocated as the threshold. Since it is considered that the predetermined task is not executed until the value exceeds, the comparison target user can determine that the predetermined task is ready to be executed.

  Subsequently, based on the execution pattern information of the comparison target user and the execution pattern information of the allocation candidate user, the allocation user determining unit 12 determines that the number of task executions within the unit time of the comparison target user is within the unit time of the allocation candidate user. It is determined whether the number is less than the task execution number (step S206). If this determination is NO (step S206; NO), it can be determined that the comparison target user cannot afford to perform the task more than the assignment candidate user, and therefore the comparison target user is set as a predetermined task assignment candidate. Then, the process proceeds to step S202.

  On the other hand, if it is determined in step S206 that the number of task executions in the unit time of the comparison target user is smaller than the number of task executions in the unit time of the allocation candidate user (step S206; YES), the allocation candidate user Since it can be determined that the comparison target user can afford to execute the task, the allocation user determining unit 12 changes the comparison target user to the allocation candidate user (step S207).

  Subsequently, the assigned user determination unit 12 determines whether or not the comparison between all users has been completed (step S208). If this determination is NO (step S208; NO), the process proceeds to step S202 in order to make the next user a comparison target user.

  On the other hand, if it is determined in step S208 that the comparison among all users has been completed (step S208; YES), the allocation user determination unit 12 determines the allocation candidate user at that time as a user to which a predetermined task is allocated. (Step S209).

  As described above, according to the workflow management system 1 in the embodiment, for each task executed by the user, an execution pattern for executing the task is set, and the execution set when an unassigned predetermined task occurs. Based on the pattern and the number of unexecuted predetermined tasks, a user to which an unallocated predetermined task is allocated can be determined. As a result, it is possible to eliminate the unevenness of the task allocation number.

  Specifically, for each task executed by the user, the average number of remaining tasks is calculated using the number of tasks remaining unexecuted when the task is executed, and based on the average number of remaining tasks, the user's The execution pattern for each task can be set to either a batch execution pattern or a sequential execution pattern.

  Further, when the user execution pattern is a batch execution pattern, the predetermined number of unexecuted tasks is greater than a threshold value that is determined according to the number of unexecuted remaining tasks when the predetermined task is executed in the past. When there are few users, this user can be a candidate for assignment of a predetermined task. On the other hand, when the execution pattern of the user is a sequential execution pattern, this user can be made a candidate for assignment of a predetermined task when the predetermined task that has not been executed is not held.

  Furthermore, a predetermined task can be allocated to a user who has the smallest number of tasks executed within a unit time among users selected as predetermined task allocation candidates.

[Modification]
Note that the above-described embodiments are merely examples, and do not exclude various modifications and application of techniques that are not explicitly described in each embodiment. That is, the present invention can be implemented by being modified into various forms without departing from the spirit of the present invention.

  For example, although the execution pattern database 22 is provided in the above-described embodiment, the execution pattern database 22 is not necessarily provided. For example, when the allocation user determining unit 12 determines the execution pattern of the comparison target user, the execution pattern setting unit 11 executes the execution pattern of the comparison target user based on the execution history information stored in the execution history database 21. It is good also as setting. Thereby, when determining a user to which a task is assigned, an execution pattern can be set based on the latest execution history information. Therefore, tasks can be assigned based on the execution pattern reflecting the latest actual situation.

  In the above-described embodiment, the workflow management system is configured by the server device 10 and the DB device 20. However, in the present invention, the workflow management system may be configured by the server device 10 incorporating the database of the DB device 20. Alternatively, the workflow management system may be configured by a plurality of device groups including the components included in the server device 10 and the DB device 20 in a distributed manner. In short, it is only necessary to function similarly to the server device 10 and the DB device 20 of the workflow management system in the above-described embodiment.

  Finally, a part or all of the above embodiments can be described as the following supplementary notes, but the present invention is not limited to the following.

  (Supplementary Note 1) For each identification information of a user who executes a task included in a workflow, at least the identification information of the task, an allocation time when the task is allocated to the user, and an execution time when the user executes the task A storage unit that stores execution history information, and before assigning the unassigned task to any of the users, the user to be assigned when assigning the unassigned task is set as the execution history information. Based on an execution pattern setting unit that sets one of a plurality of predetermined execution patterns as an execution pattern for executing the task, the execution pattern set for the user to be assigned, and the execution pattern Using the number of unexecuted tasks held by the user to be allocated, the allocation target Wherein from the user, the workflow management system, characterized in that it comprises, an allocation user determination unit configured to determine the user to assign the task of the unallocated made.

  (Supplementary Note 2) The execution pattern includes a first execution pattern for executing the task after a plurality of the tasks are assigned, and a second execution pattern for executing the task every time the task is assigned. The workflow management system according to appendix 1, characterized by:

  (Additional remark 3) The said execution pattern setting part calculates the average remaining task number using the number of the said tasks that have not been executed when the task is executed, and based on the average remaining task number, The workflow management system according to appendix 2, wherein the user to be assigned is set to either the first execution pattern or the second execution pattern.

  (Additional remark 4) The said allocation user determination part remains unexecuted when the number of the said unexecuted tasks which the said user set to the said 1st execution pattern holds execute the said task in the past The workflow management system according to appendix 2 or 3, wherein when the number of tasks is less than a predetermined threshold determined according to the number of tasks, the user is made a candidate to be assigned the unallocated task.

  (Supplementary Note 5) When the user set in the second execution pattern does not have the unexecuted task, the allocation user determination unit allocates the unallocated task to the user. The workflow management system according to appendix 4, which is a candidate.

  (Additional remark 6) The said allocation user determination part makes the said unallocated task to the said user with the fewest number of the said tasks performed within the unit time among the said users who made the candidate to allocate the unallocated task. The workflow management system according to appendix 5, which is assigned.

  (Supplementary Note 7) For each identification information of a user who executes a task included in a workflow, at least the identification information of the task, an allocation time when the task is allocated to the user, and an execution time when the user executes the task A workflow management method that is executed in a workflow management system including a storage unit that stores execution history information including: when assigning the unassigned task before assigning the unassigned task to any of the users An execution pattern setting step for setting the user to be assigned to one of a plurality of execution patterns predetermined as an execution pattern for executing the task based on the execution history information; The execution pattern set for the user and the allocation Using the number of unexecuted tasks held by the user to be assigned, the assigned user determining step for determining the user to which the unassigned task is assigned from among the users to be assigned; A workflow management method comprising:

  (Additional remark 8) The workflow management program for making a computer perform each step of Additional remark 7.

  DESCRIPTION OF SYMBOLS 1 ... Workflow management system, 10 ... Server apparatus, 11 ... Execution pattern setting part, 12 ... Allocation user determination part, 13 ... Workflow control part, 20 ... DB apparatus, 21 ... Execution history database, 22 ... Execution pattern database, 30 ... User terminal.

Claims (8)

  1. For each piece of identification information of a user who executes a task included in a workflow, execution history information including at least the identification information of the task, an allocation time at which the task is allocated to the user, and an execution time at which the user executes the task A storage unit for storing
    Before assigning the unassigned task to any one of the users, the user who is the assignment target when assigning the unassigned task is executed when the task is executed based on the execution history information. An execution pattern setting unit that sets one of a plurality of predetermined execution patterns as a pattern;
    Using the execution pattern set for the user to be assigned and the number of unexecuted tasks held by the user to be assigned, the unassigned user is selected from among the users to be assigned. An allocation user determination unit that determines the user to which the task of allocation is allocated;
    A workflow management system comprising:
  2.   The execution pattern includes a first execution pattern for executing the task after a plurality of the tasks are assigned, and a second execution pattern for executing the task every time the task is assigned. The workflow management system according to claim 1.
  3.   The execution pattern setting unit calculates the average number of remaining tasks using the number of tasks remaining unexecuted when the task is executed, and becomes the allocation target based on the average number of remaining tasks. The workflow management system according to claim 2, wherein the user is set to either the first execution pattern or the second execution pattern.
  4.   The assigned user determination unit is configured to determine whether the number of unexecuted tasks held by the user set in the first execution pattern is unexecuted and remaining when the task is executed in the past. 4. The workflow management system according to claim 2, wherein when the number is less than a predetermined threshold determined according to the number, the user is set as a candidate to which the unassigned task is assigned.
  5.   When the user set in the second execution pattern does not have the unexecuted task, the allocation user determination unit sets the user as a candidate to allocate the unallocated task. The workflow management system according to claim 4.
  6.   The assigned user determining unit assigns the unassigned task to the user having the smallest number of tasks executed within a unit time among the users who are candidates for assigning the unassigned task. The workflow management system according to claim 5.
  7. For each piece of identification information of a user who executes a task included in a workflow, execution history information including at least the identification information of the task, an allocation time at which the task is allocated to the user, and an execution time at which the user executes the task A workflow management method executed in a workflow management system including a storage unit for storing
    Before assigning the unassigned task to any one of the users, the user who is the assignment target when assigning the unassigned task is executed when the task is executed based on the execution history information. An execution pattern setting step for setting any one of a plurality of predetermined execution patterns as a pattern;
    Using the execution pattern set for the user to be assigned and the number of unexecuted tasks held by the user to be assigned, the unassigned user is selected from among the users to be assigned. An allocation user determining step for determining the user to which the task of allocation is allocated;
    A workflow management method comprising:
  8.   A workflow management program for causing a computer to execute each step according to claim 7.
JP2010099588A 2010-04-23 2010-04-23 Workflow management system, workflow management method, and workflow management program Pending JP2011232788A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2010099588A JP2011232788A (en) 2010-04-23 2010-04-23 Workflow management system, workflow management method, and workflow management program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2010099588A JP2011232788A (en) 2010-04-23 2010-04-23 Workflow management system, workflow management method, and workflow management program

Publications (1)

Publication Number Publication Date
JP2011232788A true JP2011232788A (en) 2011-11-17

Family

ID=45322068

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2010099588A Pending JP2011232788A (en) 2010-04-23 2010-04-23 Workflow management system, workflow management method, and workflow management program

Country Status (1)

Country Link
JP (1) JP2011232788A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014120031A (en) * 2012-12-18 2014-06-30 International Business Maschines Corporation Task allocation server, task allocation method and task allocation program
CN107832901A (en) * 2017-07-28 2018-03-23 平安科技(深圳)有限公司 Method for allocating tasks, device, terminal device and storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014120031A (en) * 2012-12-18 2014-06-30 International Business Maschines Corporation Task allocation server, task allocation method and task allocation program
CN107832901A (en) * 2017-07-28 2018-03-23 平安科技(深圳)有限公司 Method for allocating tasks, device, terminal device and storage medium

Similar Documents

Publication Publication Date Title
US9430288B2 (en) Job scheduling based on historical job data
JP6254949B2 (en) Pricing resources in virtual machine pools
US9003037B2 (en) Dynamic allocation of physical computing resources amongst virtual machines
EP2921975B1 (en) Determining and extracting changed data from a data source
Baruah et al. The preemptive uniprocessor scheduling of mixed-criticality implicit-deadline sporadic task systems
US10678602B2 (en) Apparatus, systems and methods for dynamic adaptive metrics based application deployment on distributed infrastructures
US8332863B2 (en) Fair share scheduling based on an individual user's resource usage and the tracking of that usage
US8762997B2 (en) Constraint-conscious optimal scheduling for cloud infrastructures
Tan et al. Coupling task progress for mapreduce resource-aware scheduling
JP4308241B2 (en) Job execution method, job execution system, and job execution program
Batur et al. Finding feasible systems in the presence of constraints on multiple performance measures
US8434088B2 (en) Optimized capacity planning
JP4629587B2 (en) Reservation management program
US8276143B2 (en) Dynamic scheduling of application tasks in a distributed task based system
US8793693B2 (en) Apparatus and method for predicting a processing time of a computer
JP3892002B2 (en) Resource allocation method and program
US8635624B2 (en) Resource management using environments
JP5334226B2 (en) Schedule management method and schedule management server
US7779413B2 (en) Method of assigning available resources for internal and external users at start time of scheduled time period based on program reservations information
Davis et al. Optimal fixed priority scheduling with deferred pre-emption
JP4935595B2 (en) Job management method, job management apparatus, and job management program
US10083424B2 (en) Scheduling events for multiple invitees
US8918792B2 (en) Workflow monitoring and control system, monitoring and control method, and monitoring and control program
JP2005044326A (en) Improved edf scheduling method
TWI533211B (en) Computer system, method and computer-readable storage medium for tasks scheduling