JPH10320456A - Method and device for work flow control and medium where work flow control program is recorded - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide the method and device for work flow control which can efficiently perform operation having a work flow and the medium where the program is recorded. SOLUTION: A work flow definition information storage device TM is stored with a status transition table wherein flows of fractionated operation units by operations and persons who should be in charge are defined, an operation state storage device FS is stored with the current states of the individual operation units, and a status transition determination device N checks the states of the individual operation units, determines whether or a next state can be entered and a person who should be in charge of it according to the end state of a finished operation unit and the status transition table, and updates the storage contents of the operation state storage device N.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a business having a feature that a subdivided business unit is sequentially executed by a plurality of executors, thereby completing an entire business having a single purpose (hereinafter, this business). Is referred to as a task having a workflow.) The present invention relates to a method and an apparatus for efficiently executing the task and a medium on which a program is recorded.

[0002]

2. Description of the Related Art Conventionally, the following method has been used as a method for executing a task having a workflow.

[0003] 1. A sequential processing order for each business unit and an executor for each business unit are designated each time the entire business is started, and the business is executed according to the order. 2. Alternatively, the processing order and executor information are defined and stored in advance for each type of business (hereinafter, this definition information is referred to as workflow definition information), and when the same business occurs, the definition information is re-created. By using it, you can save time when specifying.

[0004]

In such a conventional method, it is possible to handle a business in which each business unit has a sequential flow. However, the business unit is distributed to a plurality of executors at the same time. When all of these multiple executors complete a business unit, they cannot handle a business (distribution / collection-type business) in which the next business unit starts (or the entire business ends). was there.

Further, according to the conventional method, when the business flow partially differs depending on the business content (for example, whether the amount to be handled is 1,000,000 yen or more), the business flow is automatically changed according to the business content. Therefore, it is necessary to create workflow definition information as separate tasks, and it is necessary to create a large number of workflow definition information for similar tasks.

Further, in the conventional method, since the executor cannot be changed depending on the organization executing the business, it is necessary to create the workflow definition information for each organization executing the business. It was necessary to recreate the workflow definition information each time a member changed.

An object of the present invention is to provide a workflow control method and a workflow control method capable of allocating business units constituting a business having a workflow to respective executors without delay and without fail, thereby improving the efficiency of the entire business. Another object of the present invention is to provide a medium recording a workflow control program.

[0008]

According to the present invention, in order to solve the above-mentioned problems, in a workflow control method for controlling execution of a business having a workflow, a flow of a subdivided business unit and an executor to be in charge are defined. The defined definition information is stored, the current state of each business unit is checked, and for each completed business unit, whether the state can be changed to the next state based on the end state and the definition information and whether the state can be changed. And determining an executor to be in charge of the task.

According to the present invention, not only a simple workflow in which the subdivided business units have a sequential flow, but also a plurality of executors distribute the business units at the same time, When a unit is completed, a complicated workflow that automatically starts the next business unit can be defined and executed.

In addition, data to be handled in the business is stored, and at the end of each business unit, if the data is specified, the next executor of the business and the state to be transitioned are determined based on the data. By doing so, even if the business flow differs depending on the value of the data handled in the business, the executor and the business flow can be changed according to the data value.

[0011] Further, information on the structure of an organization that handles business is stored, and when a role to be in charge of the business unit transitions to the next state, the role is assigned based on the information. By changing to the executor, the executor can be changed depending on the organization that executes the business.

[0012]

FIG. 1 shows the structure of an apparatus according to the first, fourth and seventh aspects of the present invention, and FIG. 2 shows details thereof.

FS: Business status storage device → Holds information on the current status of each business entity. This information consists of the following contents. □ business entity distinguished name: J □ current state of affairs: S □ performer _{list: {(P 1, R 1} , C 1), ......
(P _k , R _k , C _k )｝ P is the name of the executor R is the role of the executor C is the status of the business for each executor {unrequested; being submitted; executed} □ State transition table identifier: T □ Business data table identifier: FC (only when necessary; used in claim 2) □ Organization identifier: Oi (only when required; used in claim 3) TM: Workflow definition information storage device → subdivision Stores the state transition table that defines the state transition order of the specified business unit. There is one state transition table for each business,
It is distinguished by the state transition table identifier T. The state transition table holds the following information for each of the plurality of transition source states Sc. □ Transition source state: Sc □ Next state candidate list: {St ₁ ,..., St _m } When no data condition is specified, the next state is indicated. Transition to the next list of conditions of the candidate name □ synchronization condition :( only when _{necessary) {Ps 1, ...... Ps p} } or {Rs _1, ...... Rs _p} for the next state when the data condition is specified List of performers who should have completed the business unit before doing so. However, in the case of claim 3, a list of role names of the executor. □ Data condition: (only when necessary; used in case of claim 2) Business data table identifier: FC Data item name: D List of values for data item: {V ₁ ,..., V _q } Evaluation procedure identifier: CP □ role candidate _{list: {Pt 1, ...... Pt u} } or {R
List of t _1, ...... Rt _u} then run to execute the business's name. However, in the case of claim 3, a list of role names to be executed next. When data conditions are specified, a list of multiple execution candidate names or a list of role candidate names, respectively.

N: State transition determination device Input: State transition table, current state Output: next state, list of executors to be requested during execution FIG. 3 is an operation flowchart corresponding to the first, fourth and seventh aspects of the present invention. is there. Note that "VI" and "XI" in the flow indicate that the flowcharts corresponding to FIGS. 6 and 9 respectively exist.

The state transition determining device N has a business entity identifier J
The workflow control relating to the above operation is performed as follows.

(1) With respect to the job with the job entity identifier J, the current status S and the status transition table identifier T of the job corresponding to the job entity are extracted from the job status storage device FS.

(2) Search the workflow definition information storage device TM for a state in which the transition source state Sc of the state transition table T coincides with the above-mentioned current state S, and obtain information held about Sc.

(3) ΔPs ₁ ,... Specified by the synchronization condition
For Ps _p } or {Rs ₁ ,..., Rs _p }, the executor list of the business state storage device FS: {(P ₁ , R ₁ , C
₁ ),... (P _k , R _k , C _k )} corresponding {C
It s _1, to confirm whether ...... Cs _p} is in the pre-run. If this condition is not satisfied, no transition is made to the next state. Therefore, the state of the business is maintained in the current state.

(4) ΔPs ₁ ,... Specified by the synchronization condition
For Ps _p } or {Rs ₁ ,..., Rs _p }, the executor list of the business state storage device FS: (P ₁ , R ₁ ,
C ₁ ),... (P _k , R _k , C _k )} corresponding {Cs
₁ ,... Cs _p } has been executed, it is confirmed whether or not a data condition is designated.

(5) If no data condition is specified,
Role candidate list {Pt _1, ...... Pt _u} or {R
t _1, ...... Rt _u} as the next executor to execute the business name {Pd _1, ...... Pd _v} or role name {R
d ₁ ,..., Rd _v }. In this case, only _one St1 is designated in the next state candidate list, and this is set as the next business state Sn.

The data condition is specified in the case of claim 2, which will be described later.

(6) Update the status of the job to Sn for the job with the job entity identifier J in the job status storage device FS.

(7) It is confirmed whether or not an executor name is specified in the role candidate list.

(8) If an executor name is specified in the role candidate list, an executor name to be executed next {Pd ₁ ,
...... The Pd _v} in the execution list of the business state storage device FS {(Pd ₁ ,, in request), ...... (Pd _v ,, in request)}
Register as

The case where the role name of the executor is specified in the role candidate list is the case of claim 3, which will be described later.

FIG. 4 shows the structure of an apparatus according to the second, fifth and eighth aspects of the present invention. The following structure is newly added to FIG. FIG. 5 shows details of the added portion.

FCM: business data storage device → holds data handled in each business. There is another table for each task, and each table is distinguished by a task data table identifier FC. Each table holds the following information. □ Data item name: ｛D ₁ ,..., _Dr ｝ □ Business entity identifier: J □ Data value of each business entity for each data item: ｛Vj
₁ ,... Vj _r Ｂ B: branch destination determination device → determines the next executor (or the role of the executor) and the next state of the business. A plurality of evaluation procedures distinguished by the evaluation procedure identifier are stored. Input: evaluation procedure identifier, data value, value list, role candidate list (or candidate list of performers), next state candidate list Output: list of determined roles (or performers), determined next state Is an operation flowchart corresponding to the second, fifth and eighth aspects of the present invention.

The state transition determining device N uses the business entity identifier J
Is performed in the same manner as in the case of FIG. However, only the operation of (5) is different, and the operation is performed as follows. In this case, a data condition is specified for the transition source state Sc of the state transition table T of the workflow definition information storage device TM.

[0029] (11) a state transition determination unit N, to the branch destination determining unit B, operational data table DN FC, data item name D, the value for the data item list _{{V 1, ...... V q}} ,
Evaluation procedure distinguished name CP, the role candidate list {Pt _1, ...... P
t _u} or _{{Rt 1, ...... Rt u}} , the next state candidate list {St _1, pass ...... St _m}.

(12) The branch destination determining apparatus B finds a business data table having the business data table identifier FC from the business data storage FCM, and reads the value Vj corresponding to the data item name D.

(13) The branch destination determining apparatus B reads out the evaluation procedure of the evaluation procedure identifier CP, and according to the evaluation procedure, V
j and {V ₁ ,..., V _q } are evaluated, and based on the result, some elements are selected from the elements of the role candidate list, and this is executed by the next executor. Name @ P
d ₁ ,..., Pd _v } or role name {Rd ₁ ,.
d _v }.

(14) Next state candidate list {St ₁ ,... St
_m }, one element is selected from the elements, and this is set as the next business state Sn.

FIG. 7 shows the structure of an apparatus according to the third, sixth and ninth aspects of the present invention. The following structure is newly added to FIG. FIG. 8 shows details of the added portion.

A: Role embodying device → Returns the executor having the designated role in the organization handling the business. Input: Executor role name, organization identification name Output: Executor name The following information is held in the role embodying device A. Organizational structure table: OC Holds information on the hierarchical relationship from the lower-level organization to the highest-level organization. □ Organization identifier: Oi. □ Organization identifier of the upper organization: Oh. Holds information for mapping. □ Organization identification name: O □ Role name: R □ Executor name: P FIG. 9 is an operation flowchart corresponding to the third, sixth and ninth aspects of the present invention.

The state transition determining device N uses the business entity identifier J
Is performed in the same manner as in the case of FIG. However, only the operation of (8) is different, and it is performed as follows. In this case, for the transition source state Sc of the state transition table T of the workflow definition information storage device TM, the synchronization condition and the role candidate list are specified not by the executor name but by the role name. role name {Rd _1, ...
.. Rd _v } are determined by the operations (1) to (7) in FIG.

(21) The state transition determining device N determines the role name $ Rd
₁ , …… Rd _v } to convert each element to
From application status storage device FS, removed tissue DN Oi concerning the business of the business entity DN J, pass each element Rd _j of Oi and role name role embodied apparatus A.

(22) The role embodying device A is a role assignment table RP
Searching, obtaining a performer name Pd _j whose role Rd _j to tissue Oi.

[0038] (23) execution name Pd _j with the role Rd _j to confirm whether or not obtained.

[0039] (24) If the invoker name Pd _j whose role Rd _j to tissue DN Oi can not be obtained, the tissue composition table O
The organization identifier Oh of the superior organization of Oi is obtained from C. Find the role the person in charge Table RP, locate the executable name Pd _j with the role Rd _j relative to the tissue Oh. Repeat until a role name is found.

(25) The role embodying apparatus A executes the list {Pd ₁ ,... P of the names of the executors obtained as a result of (23) and (24).
d _v } is returned to the state transition determining device N.

(26) The state transition determining device N calculates the ｛Pd ₁ ,.
.. Pd _v } and {Rd ₁ ,... Rd _v } are stored in the executor list of the business state storage device FS as {(Pd ₁ , Rd ₁ , requesting),... (Pd _v , Rd _v , requesting). Register as｝.

[0042]

FIG. 10 shows an embodiment of the present invention. In this embodiment, an apparatus corresponding to the third, sixth and ninth aspects of the present invention, for example, a business entity execution apparatus 20 for registering, retrieving and executing business entities is provided.
1 shows an example of a system that realizes automatic delivery of a slip between organizations within an organization by combining.

When a slip is issued, the business entity execution device 20 stores information on a new business entity in the business status storage device FS as a business entity identification name: a slip number, a current status of the business: an initial status, and a status transition table identification. Name: Identifier of the state transition table that defines the workflow for this slip (“Travel Expense Application” in the figure) Organization Identifier: Organization name of the issuer of this slip (Section III, Section 1) Executor list: Issuer name (A in the figure),
"Issuer", processed) is registered.

Next, a request is made to the state transition determining device N for processing, and the state is shifted to the state of the next slip according to the state transition table.
In the figure, from the state transition table, “section manager” is obtained as the role of the executor who should execute the task next, and “application” is obtained as the next task state. Further, the role embodying device A obtains “Mr. B” as the name of the executor for “section manager” in the organization of the slip issuer. Then, based on these contents, the status of the relevant business entity in the business status storage device FS is changed in such a way that the current status of the business: application executor list: (Mr. B, section manager, requesting) is added.

The business entity execution device 20 stores a list of the slips “requesting” to itself in the business status storage device FS.
, And refer to the contents of the slip based on the slip number. If the contents of the slip are valid, the business entity executing device 20 can be instructed to approve the slip. At this time, the business entity execution device 20 requests the state transition determination device N to perform a process after setting the status for the approver of the performer list regarding the slip in the business status storage device FS to “executed”.

In the example shown in the figure, "manager" is obtained from the state transition table as the role of the executor who should execute the next task, and "section approved" is obtained as the next task state. Furthermore, the role embodying apparatus A obtains “Ms. M” as the executor name for the “manager” in the organization of the slip issuer. Based on these contents, the status of the relevant business entity in the business status storage device FS is changed as follows: Current status of business: Section approved Executor list: (Mr., manager, requesting).

In this embodiment, the slip is automatically delivered to the person in charge of the role by the organization of the slip issuer, so that the state transition of the slip is the same for all organizations. You only need to prepare one. Further, when there is a personnel change, it is only necessary to correct the role staff table PR, and when there is an organization change, the organization structure table OD
It is only necessary to correct the role assignment table PR, and it is not necessary to correct other information.

[0048]

As described above, according to the first, fourth and seventh aspects of the present invention, not only a simple workflow in which the subdivided business units have a sequential flow, but also a plurality of executors A business unit can be distributed or a complicated workflow can be defined and executed such that when a plurality of executors complete each business unit, the next business unit is automatically started. This makes it possible to easily control, as a workflow, a broadcast-type processing request for requesting the same unit of work to each of a plurality of persons, a collection-type task for compiling results of tasks requested by the broadcast-type, and the like.

According to the second, fifth and eighth aspects of the present invention, even when the business flow partially differs depending on the value of the data handled in the business, the executor and the business flow are changed in accordance with the data value. can do. For example, a task in which a settler differs depending on whether the amount to be handled is equal to or more than 1,000,000 yen or a task in which charge is different depending on the classification of a customer or the like can be described as one workflow.

According to the third, sixth and ninth aspects of the present invention, the executor can be changed depending on the organization that executes the business, and it is necessary to create the workflow definition information for each organization that executes the business. Instead, it is only necessary to define one common workflow for the organization. For this reason, when the workflow of the business is changed, the change target is limited, the maintenance and management of information is facilitated, and the workflow definition information is re-created even when the members or organizational structure of the organization are changed. There is an advantage that there is no need to change the definition information of the organization.

[Brief description of the drawings]

FIG. 1 is a block diagram of a device according to the inventions of claims 1, 4 and 7;

FIG. 2 is a detailed configuration diagram of FIG. 1;

FIG. 3 is an operation flowchart according to the first, fourth and seventh aspects of the present invention;

FIG. 4 is a block diagram of an apparatus according to the second, fifth and eighth aspects of the present invention.

FIG. 5 is a detailed configuration diagram of FIG. 4;

FIG. 6 is an operation flowchart according to the second, fifth and eighth aspects of the present invention;

FIG. 7 is a block diagram of an apparatus according to the third, sixth and ninth aspects of the present invention.

FIG. 8 is a detailed configuration diagram of FIG. 7;

FIG. 9 is an operation flowchart according to the third, sixth and ninth aspects of the present invention;

FIG. 10 is a configuration diagram showing one embodiment of the present invention.

[Explanation of symbols]

TM: Workflow definition information storage device, FS: Business status storage device, N: State transition determination device, FCM: Business data storage device, B: Branch destination determination device, A: Role embodying device.

Claims (9)

[Claims] 1. A workflow control method for controlling the execution of a task in which a subdivided business unit is executed by a plurality of executors and which is completed as a whole, comprising: a flow of the subdivided business unit; Is stored, the current state of each business unit is checked, and for each completed business unit, whether or not it is possible to transit to the next state based on the end state and the definition information and A workflow control method characterized by determining an executor to be in charge of this. 2. Data to be handled in a business is stored, and at the end of each business unit, if the data is specified, a next executor of the business and a state to be transitioned are determined based on the data. 2. The workflow control method according to claim 1, further comprising: 3. The information relating to the structure of an organization that handles business is stored, and when a business unit transitions to the next state, if a role to be in charge of the business unit is specified, the role is assigned based on the information. 2. The workflow control method according to claim 1, wherein the method is changed to an executor. 4. A workflow control apparatus for controlling execution of a task in which a subdivided task unit is executed by a plurality of executors to complete the entire task. A workflow definition information storage device that stores definition information defining the status of each business unit, a business status storage device that stores the current status of each business unit, and checks the status of each business unit and terminates any completed business units. A state transition determining device that determines whether the state can be transited to the next state based on the state and the definition information, determines an executor to be in charge of the state, and updates the storage content of the business state storage device. And a workflow control device. 5. A business data storage device for storing data handled in a business, and a branch destination determining device for determining a next executor of the business and a state to be transitioned based on the value of the data, 5. The workflow control device according to claim 4, wherein at the end of the unit, the branch destination determination device is operated if the data is specified. 6. A role embodying device that has information on the structure of an organization that handles business, and converts information on a role to be in charge of a business unit into information on an executor to be in charge of a business unit. 5. The workflow control device according to claim 4, wherein when transitioning to the next state, if information of a role to be in charge of the status is specified, the role realization device is operated. 7. A medium in which a work flow control program for controlling execution of a job in which a subdivided business unit is executed by a plurality of executors to complete the entire business unit is recorded. It stores the definition information that defines the executor and the current state of each business unit, and for each completed business unit, is it possible to transit to the next state based on the end state and the definition information? A medium recording a workflow control program characterized by determining whether or not an executor to be in charge of the workflow control program. 8. A method for storing data handled in a business, and determining the next executor of the business and the state to be transitioned based on the value of the data if the data is designated at the end of each business unit. A medium on which the workflow control program according to claim 7 is recorded. 9. The system stores information on the structure of an organization that handles business, and when a business unit transitions to the next state, if a role to be in charge of the business unit is specified, the role is executed based on the information. A medium recording the workflow control program according to claim 7, wherein the medium is changed to: