JP2002215859A - Managing method, managing system and managing server for workflow - Google Patents

Abstract

PROBLEM TO BE SOLVED: To set up a system whereby a higher department can grasp how a task which it has asked a lower department to execute is passed on, but the lower department can reject retrieval by the higher department for a task unrelated to the higher department. SOLUTION: Each of workflow managing servers 100, 200 and 300 comprises passing-on access control tables 120, 220 and 320, and workflow databases 110, 210 and 310 which retain a state of work passing-on of the department where a task occurs and a state of work passing-on of the other department obtained, and when there occurs a need to ask another cooperating department to execute a part of the work, registers a workflow control server of the requesting party to the passing-on access control table only when approving retrieval of a state of work passing-on from the workflow control server of the requesting party. Each workflow control server judges whether to approve or disapprove the request for submitting a state of passing-on from the workflow control server of the requesting party referring to the passing-on access control table of its own server.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a workflow management method, a workflow management system, and a workflow management server.

[0002]

2. Description of the Related Art A conventional workflow management system has a configuration shown in FIG.

[1.1] When a job is requested (S1),
Based on the contents of the request, the operator creates a file that specifies the route and to whom the application is routed, or the application automatically determines and creates a file that is specified in the same way. It is registered in the management server (WFSV) 100 (S3). In the following, a file designating the contents of the job and the routing route will be referred to as JOB 101.

[1.2] Then, the user A01 at the head of the job 101 is permitted to perform the task TASK-A01 (step S3).

[1.3] Workflow Management Server 10
0 receives this JOB 101 and notifies the first user A01 of the start of work by e-mail or message communication based on the JOB information (S10).
5).

[1.4] Upon receiving the event notification, the user A01 performs a process TASK-A01. And if the user TA01 completes the process TASK-A01,
The completion notification is written to the routing status file 103 of the workflow management server 100.

[1.5] Workflow management server 10
0 confirms the completion of writing and, based on the routing route defined as JOB, executes the next processing TASK-A02.
The user A02 who should perform the work,
The start of work is notified by e-mail or message communication (S7).

[1.6] Thereafter, the workflow management server 100 repeats the procedures of [1.4] and [1.5],
When the job is completed to the end of the routing route of JOB 101, it is determined that the requested job has been completed.

The workflow management server 100
Is the circulation status file 1 for users who can log in.
03 can be browsed.

A multi-layered workflow management system using such a conventional workflow management system is as shown in FIG. For example, suppose that the department A has decided to develop a product as a result of planning and studying a product, and has decided to proceed with the design. in this case,
The next hierarchical workflow.

[2.1] Department A carries out TASK-A01, which is a study of requirements for design. As a result, request TASK-A of design department B to meet the requirements.
02 is performed.

[2.2] In the section B, the requested design is implemented (TASK-B01).

[2.3] In the department B, as a result of the design, a part of the product is requested to the department C for the design TASK-B02.
I do.

[2.4] The department C implements the design received from the department B (TASK-C01).

[2.5] The department C verifies the design result, confirms that there is no problem, and returns the design result to the department B (TASK-C02).

[2.6] Since the department B has obtained the design of the parts, it verifies the entire design, confirms that there is no problem, and returns the result of the work to the department A (TASK-B0).
3).

[2.7] In the section A, since the product design has been obtained, it is verified whether or not the design satisfying the requirements has been made (TASK-A03).

When such hierarchical workflow management is performed by a distributed workflow management system in which a plurality of workflow management systems are linked, as shown in FIG. 12, a workflow management server (W) is provided for each department.
FSV-A, WFSV-B, WFSV-C) 100, 2
00 and 300 are set up, and work requests and results are exchanged as data between them. In FIG. 12, the workflow database (WF
DB-A, WFDB-B, WFDB-C) 110, 21
0,310 is each workflow management server 100,20
0,300 is a database for workflow management.

The management of the hierarchical workflow by this distributed workflow management system is as shown in FIG. This will be described. A job occurs in department A (S
11) If it is necessary to assign this job to the user A01, the workflow management server 200 of the department B, and the user A02, such a job is created and circulated (S13).

When the work of the user A01 is completed in the created JOB (S15), the workflow management server 200 of the department B becomes ready for processing. Here, cooperation between the workflow management server 100 of the department A and the workflow management server 200 of the department B occurs (S1).
7). A job request is made to the workflow management server 200. This is a request to be created in the job, and is created by the user A01 in this example. The job request is sent to the workflow management server 10 of the department A.
0 is transmitted to the workflow management server 200 of the department B by e-mail or the like (S17-1).

In the workflow management server 200 of the department B which has received the job request, the JO is executed in the same manner as a normal job.
B is created and circulated (S17-2, S17-3). In the section B, a job is performed by the users B01 to B03 (S17-4 to S17-6).

When the job is completed in the department B, the result of the work created in the job is transmitted from the workflow management server 200 of the department B to the workflow management server 100 of the department A from which the job was requested by e-mail. Then, it is automatically transmitted (S17-7).

The department A workflow management server 100 receiving the result of the department B work receives the TASK-A0 assigned to the department B workflow management server 200.
2 is completed, and TASK-A03 is ready for processing (S19).

[0024]

However, such a conventional multi-layer workflow management system has the following problems. One of them is that only the information of the department A exists in the workflow database 110 of the workflow management server 100 of the department A where the work has occurred.
When the workflow A is searched for by the department A, the workflow database 110 of the workflow management server 100 can be searched, but the workflow databases 210 and 310 of the workflow management servers 200 and 300 of the other departments B and C are searched. It is not possible to search, and it is not possible to grasp the situation of the entire work. The other is a database 21 of the workflow management servers 200 and 300 of the departments A to B and C.
When the authority to enable the search of 0,310 is given, the department A can grasp the status of the work which does not involve the department A in the workflow management servers 200, 300 of the departments B, C. The point is that the security of the workflow management servers 200 and 300 of B and C cannot be maintained.

This problem occurs not only in a multi-layer workflow management system in a company but also in a workflow management system between companies. Although the relationship between buyers and suppliers at the time of procurement and the sub-department of the supplier (especially subcontractors) is multi-tiered, the supplier often does not want to disclose the workflow below the company to the buyer, so the conventional There is a problem that a distributed workflow management system cannot meet the demand.

The present invention has been made in view of such a conventional problem, and the status of a job requested from a higher department to a lower department can be grasped by the higher department, but is not related to the higher department. An object of the present invention is to provide a workflow management method, a workflow management system, and a workflow management server that can reject a search from a higher-level department for work.

[0027]

According to a first aspect of the present invention, there is provided a workflow management method, wherein each of a plurality of workflow management servers connected via a network obtains and obtains a routing access control table, a status of a job in its own department, and a status of the department. A workflow database that holds the obtained status of work from other departments is provided, and when a job that requires a part of the job to be linked to another department occurs, the If the request for the attachment status search is allowed, the requesting workflow management server is registered in the routing access control table, and if the search request is rejected, it is not registered. Refers to the access control table of the local server in response to the request for obtaining the status of the transfer from the workflow management server of the request source. Determining permission / non-permission of only if you allow the search, it is characterized in transmitting the job-specific circulation conditions applicable to the requester of the workflow management server.

In the workflow management method according to the first aspect of the present invention, when a job that requires a part of the job to be performed to another department to cooperate occurs, a search of a circulation status from the requesting workflow management server is performed. If the request is permitted, the requesting workflow management server is registered in the routing access control table. If the search request is rejected, it is not registered. On the other hand, the workflow management server of each section refers to the circulating access control table of the own server and permits / disallows the search. As a result, it is possible for the upper department to grasp the status of the work requested by the higher department to the lower department (or subcontractor), but the lower department can reject search from the higher department for work that is not related to the higher department. To ensure uniqueness and security between them.

A workflow management system according to a second aspect of the present invention comprises a plurality of workflow management servers for transmitting data via a network, wherein each workflow management server includes a workflow database for registering a work circulation status, and a workflow database for registering a work circulation status. A workflow access control table for registering an index of permission / non-permission for each job in response to an access request to the workflow database of the server; The requesting workflow management server refers to the routing access control table of its own server, permits the access based on the permission / non-permission index for each job, and transmits the corresponding routing status for each job. Or denies the access That.

In the workflow management system according to the second aspect of the present invention, if a certain workflow management server sends an access request for the status of the job to another server to another server, the requested workflow management server sends the access request of the own server. Referring to the control table, it is determined whether the access is permitted or not based on the permission / non-permission index for each job. If the access is permitted, the access status is obtained from the own department registered in the workflow database. The obtained circulation status of the other department is transmitted, but if it is not permitted, the access is rejected.
In this way, the status of the work that has been requested from the upper department to the lower department (or subcontractor) can be grasped by the upper department, but for jobs that are not related to the upper department, search from the higher department can be refused by the lower department, and To ensure the uniqueness and security of

A workflow management server according to a third aspect of the present invention registers a workflow database for registering work circulation status and an index of permission / non-permission for each job in response to an access request to the workflow database from another server. And a circulation access control table.
Receives an access request for the job-specific routing status from another server via the network, refers to the routing access control table, and permits the access based on the job-based permission / non-permission index to permit the relevant job. It is characterized in that another circulation status is transmitted through a network or access to the workflow database is denied.

In the workflow management server according to the third aspect of the present invention, upon receiving an access request for a work-specific routing status from another server via a network, the workflow management server refers to the routing access control table and permits / disallows the job. Based on the permission index, the access is permitted and the corresponding job-specific routing status is transmitted through the network, or the access to the workflow database is denied. Therefore, the workflow management server according to the second aspect of the present invention can be constructed by installing the workflow management server in each department and connecting them via a network.

[0033]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 shows a configuration of a workflow management system according to one embodiment of the present invention. This system is a distributed workflow management server (WFS)
VA) 100, (WFSV-B) 200, (WFSV
-C) A configuration in which 300 is connected by an information network such as a LAN, the Internet, or a dedicated communication line.

The department A has a workflow management server (W
An FSV-A) 100 is installed, a workflow management server (WFSV-B) 200 is installed in department B, and a workflow management server (WFSV-C) 3 is installed in department C.
00 is installed. Workflow management server 10
Reference numerals 0, 200, and 300 denote workflow databases (W) for storing work circulation status and other necessary information.
FDB-A) 110, (WFDB-B) 210, (WF
DB-C) 310.

The workflow management server 100,
Each of the computers 200 and 300 is a computer in which a program for executing each process described later is incorporated. As a characteristic function of the present embodiment, the computer 200 includes circulation access control tables 120, 220, and 320. A circulation status acquisition control function is provided. Each server 100, 200,
Cooperation of workflow between 300 is e-mail or ftp
This is performed by message communication means such as

Next, the operation of the workflow management system having the above configuration will be described.

<Business Flow> Each function in the business flow will be described with reference to the functional block diagram of FIG. 1, the data map of the circulation access control table 120 of FIG. 2, and the flowcharts of FIGS. A job is generated in the department A, and a job is created in the workflow database 110 in the workflow management server 100 by an operator or an application (S111). Job name (JOBID)
Must be unique among all the related workflow management servers, so it is created with the server name + time. Here, the JOBID of the first job is JOB-001.

In the job management server 100, TASK-A01 to TASK-A
03 are created so that each user A0
1. Department B workflow management server (WFSV-
B) 200, assign user A02. Also, JOB-
001, it is known that the work is to be routed to the department A and the department B at the time of creating the work, so the workflow management server 100 of the department A and the workflow management server 2 of the department B
FIG. 2 is displayed by the operator or the application so that 00 is permitted to inquire about JOB-001.
The data JOB-001: WFSV-A, JOB-001: WF are stored in the circulation access control table 120 as shown in FIG.
The SV-B is created and stored (S112).

When the work of the user A01 is completed in the department A, the work is transferred to the department B. For the job request to the department B, data is created as a design request, and the design request is transmitted to the workflow management server 200 of the department B by e-mail or ftp.

The workflow management server 200 of the department B that has received the design request creates JOB-001. This JOB-001 is created by an operator or an application so that TASK-B01 to TASK-B03 exist in the workflow management server 200, and the workflow management server (WFSV-C) 300 of the user B01 and the department C respectively User B02
Is assigned (S211).

Also, in JOB-001, it is known that when a job is created, the department A, the department B, and the department C circulate the job, so the workflow management servers 100, 200,
Data JOB-001: WF is stored in the circulated access control table 220 by the operator or the application so that 300 can permit an inquiry to JOB-001
An SV-C is created (S212). At the same time, JO
Regarding B-001, the information that the department C is related is notified to the workflow management server 100 of the department A and registered in the circulation access control table 120 (S21).
3). In the department A, when responding to the routing status acquisition request from the department C, the operator or the application additionally registers the workflow management server (WFSV-C) of the department C in the routing access control table 120.

When the work of the user B01 is completed, the work is transferred to the department C. For the job request to the department C, data is created as a part design request, and the design request is transmitted to the workflow management server 300 of the department C by e-mail or ftp (S214).

The workflow management server 300 of the department C receiving the design request creates JOB-001. This JOB-001 is created by an operator or an application so that TASK-C01 to TASK-C02 exist in the workflow management server 300, and a user C01 and a user C02 are assigned to each of them (S311).

Also, in JOB-001, since it is known that the work is to be routed to the department A, the department B, and the department C when the job is created, the workflow management servers 100, 200, and 300 of the departments A to C are respectively assigned to the JOB-001. Data is created in the circulation access control table 320 by an operator or an application so that an inquiry to 001 is permitted (S312). At this time, if the department C wants to refuse the search from the department A, it is possible not to create the data of JOB-001: WFSV-A in the table 320.

When the work of the user C01 is completed, the user C0
When the work of the second job is also completed, the work of the department C is completed, and the result of the work is passed to the department B (S31)
3). The delivery of the work result from the department C to the department B is performed by e-mail or ftp as the part design result.
To the workflow management server 200.

In the workflow management server 200 of the department B that has received the part design result, TASK-B02 is completed, and the user B02 performs a job with TASK-B03 (S21a).

When the user B02 completes the work with TASK-B03, the work of the department B is completed, and the result of the work of the department B is passed to the department A. The delivery of the result to the department A is transmitted to the workflow management server 100 of the department A by e-mail or ftp as a design result (S21b).

In the workflow management server 100 of the department A that has received the design result from the department B, the TASK-A0
2 is completed, and the user A02 performs work in TASK-A03. When the user A02 completes the work, the work of the department A is completed, and JOB-001 is completed (S11a, S11b).

<Flow of Request for Acquisition of Circulation Status> For example, when a request for acquisition of a circulation status is issued from the department A to the department B and the department C, in response to the request for the acquisition of the circulation status, the circulation of the own department is performed. The operation for determining whether or not to search the attachment status is described in the functional configuration diagram of FIG. 5, the XML files of FIGS. 6 and 7, and FIGS.
This will be described with reference to the flowchart of FIG. The user A01 of the department A requests the acquisition of the circulation status of JOB-001. At this time, as the request range, the workflows of the departments A to C are managed by the management servers (WFSV-A) 100 and (WFSV-A).
-B) 200 and (WFSV-C) 300 are specified (S121).

In this case, the request command is XML in FIG.
-001. "Requesting user: A0
1, "request source server: WFSV-A", "request range: (1) WFSV-A, (2) WFSV-B, (3)
WFSV-C "and" JOBID: JOB-00 "
Specify "1".

According to this request, the routing status acquisition control of the WFSV-A functions. First, the routing access control table 120 is searched to determine whether the routing status of JOB-001 may be answered in response to an inquiry from WFSV-A. In the case of this example, department A for JOB-001
Workflow management server WFSV-A is permitted. WFSV-A is specified in the request range.
As a result, it can be determined that the creation of the circulation status answer is permitted, so that the circulation status of JOB-001 registered in the workflow database (WFDB-A) 110 in the WFSV-A 100 of the department A is created. (S12
2).

Here, in JOB-001, since it is possible to determine from the data of the WFDB-A110 that a subordinate department exists, a circulation status acquisition request XML-001 is created (S123), and the subordinate department B is created. e-mail or f
tp is transmitted (S124).

Department B workflow management server (FW
SV-B) 200, the circulation status acquisition request XML-A1
Is received, the circulation status acquisition control is executed. In this routing status acquisition control, first, the routing access control table 2 of the workflow database (WFDB-B) 210
20 in response to the inquiry from the WFSV-A 100, it is determined whether or not the routing status of JOB-001 may be answered. WFSV-A permission has been granted to JOB-001. Also, WFSV-B is specified in the request range. Therefore, since it can be determined that the creation is permitted, here, the JOB-
001 is created (S221).

In this case as well, it is possible to judge from the data of the WFDB-B210 that there is a further subordinate department in JOB-001, so the transfer status acquisition control is transferred to the subordinate department C by e-mail or ftp. Yes (S22
2).

Department C workflow management server (WF
In the SV-C) 300, upon receiving the circulation status acquisition request, the circulation status acquisition control functions. First, the routing access control table 320 is searched, and it is determined whether the routing status of JOB-001 may be answered in response to an inquiry from the WFSV-A100. W for JOB-001
FSV-A permission has been granted. In addition, WF
SV-C is specified. As a result, it can be determined that the creation of the circulation status is permitted, so that the circulation status of JOB-001 in the workflow database (WFDB-C) 310 of the workflow management server (WFSV-C) 300 is created (S321). ).

Department C workflow management server (WF
SV-C) Routing status XML-C1 created in 300
Is sent by e-mail or ftp to department B of the inquiry source
Is transmitted to the workflow management server (WFSV-B) 200 (S322). The circulation access control table 3 in the workflow management server 300 of the department C
If WFSV-A is not permitted in 20, a blank file is created as the circulation status and transmitted to WFSV-B.

Department B workflow management server (WF
In the SV-B) 200, if the distribution status XML-C1 of the workflow database (WFDB-C) 310 of the department C is received, the distribution status in the workflow database (WFDB-B) 210 of the server 200 is received. The circulating status XML-C1 of the WFDB-C 310 is embedded and created as the circulating status XML-B1 of the own database (WFDB-B) 210. And the created W
The distribution status XML-B1 of the FDB-B210 is transmitted to the workflow management server (WFSV-A) 100 of the department A of the inquiry source by e-mail or ftp (S2).
2a).

In the WFSV-A 100, the WFDB-B received from the workflow management server 200 of the department B
The routing status XML-B1 of 210 is embedded in the routing status in the workflow database (WFDB-A) 110 of the own server 100, and the routing status XML of the own database 100 is embedded.
-A1 (S12a).

The WFDB-A1 thus created
The routing status XML-A1 of 10 is the routing status of JOB-001, and the file expressed in XML has the contents as shown in FIG. The user A01 displays this on a display by a browser and refers to it.

As described above, in the workflow management system according to the present embodiment, the workflow management servers 100, 200, and 300 of each department are provided with the circulation access control tables 120, 220, and 320, and work is performed by other departments that cooperate. When you have a job that needs to be partially commissioned,
If the request of the circulation status search from the requesting workflow management server is allowed, register the requesting workflow management server in this routing access control table, and if the search request is rejected, do not enter it. It is registered, and the workflow management server in each department refers to the routing access control table of its own server and permits / disallows the search in response to the circulation status acquisition request from the request source. Or a subcontractor), the status of the rescheduling of the job requested by the upper department can be grasped by the upper department. Can be secured.

In the above-described embodiment, the XML format is used for the request for obtaining the circulating status between the servers and the circulating status. However, the present invention is not limited to this.
A format can be used, and if a definition of data is determined in advance, another format such as a CSV format can be used. Further, the message communication means between the servers is not limited to the illustrated one, but may be another communication method.

[0062]

As described above, according to the workflow management method of the first aspect of the invention and the workflow management system of the second aspect of the present invention, the distribution status of a job requested from a higher department to a lower department (or a subcontractor). Can be grasped by the upper section, but for jobs not related to the upper section, the search from the upper section can be rejected by the lower section, and the uniqueness and security between the sections can be secured.

According to the workflow management server according to the third aspect of the present invention, the workflow management server according to the second aspect of the present invention can be constructed by installing the workflow management server in each department and connecting them via a network.

[Brief description of the drawings]

FIG. 1 is a functional block diagram of a workflow management system according to an embodiment of the present invention.

FIG. 2 is a data map of a routing access control table employed in the embodiment.

FIG. 3 is a flowchart (part 1) of workflow management for a job of JOB001 according to the embodiment.

FIG. 4 is a flowchart (part 2) of the workflow management for the job of JOB001 according to the embodiment.

FIG. 5 is a functional block diagram showing a flow of a circulation status acquisition operation in the embodiment.

FIG. 6 is an XML of a circulation status acquisition request used in the above embodiment.

FIG. 7 is an XM showing a turning situation used in the above embodiment.
L.

FIG. 8 is a flowchart (part 1) of a circulation status acquisition operation in the embodiment.

FIG. 9 is a flowchart (part 2) of a circulation status acquisition operation in the embodiment.

FIG. 10 is a functional block diagram of a conventional independent workflow management server.

FIG. 11 is a workflow diagram showing a flow of a design work of the hierarchical job JOB001.

FIG. 12 is a functional block diagram of a conventional hierarchical workflow management system.

FIG. 13 is a detailed functional block diagram of a conventional hierarchical workflow management system.

[Explanation of symbols]

 Reference Signs List 100 Workflow management server (WFSV-A) 110 Workflow database (WFDB-A) 120 Access control table A 200 Workflow management server (WFSV-B) 210 Workflow database (WFDB-B) 220 Access control table B 300 Workflow Management server (WFSV-C) 310 Workflow database (WFDB-C) 320 Access control table C

Claims (3)

[Claims] 1. A plurality of workflow management servers connected by a network, a workflow database holding a circulation access control table, a circulation status of a job in the own department, and a circulation status of an acquired job in another department. If there is a task that requires a part of the job to be linked to another department to cooperate with, the request for workflow status search from the requesting workflow management server can be requested. The requesting workflow management server is registered in the control table, and if the search request is rejected, it is not registered. Each workflow management server responds to the request for obtaining the circulation status from the requesting workflow management server. Search permission by referring to the circulation access control table of the local server.
A workflow management method characterized by determining refusal and transmitting the relevant job-specific circulation status to the requesting workflow management server only when the search is permitted. 2. A workflow management server comprising: a plurality of workflow management servers for transmitting data via a network; each workflow management server receives a workflow database for registering a work circulation status and a request for access from another server to a workflow database of its own server; A workflow access server for registering an index of permission / non-permission for each job, wherein each workflow management server transmits an access request for the status of the routing for each job to another server, and a workflow management server of the request destination. Refers to the routing access control table of its own server, permits the access based on the permission / non-permission index for each job, transmits the corresponding routing status for each job, or denies the access A workflow management system characterized by the following. 3. A workflow database for registering a work circulation status, and a circulation access control table for registering an index of permission / non-permission for each work in response to an access request to the workflow database from another server, Receives an access request for the job-specific routing status from another server via the network, refers to the routing access control table, and permits the access based on the job-based permission / non-permission index to permit the relevant job. A workflow management server for transmitting another circulation status via a network or denying access to the workflow database.