JP2000215244A - Work process management device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a work process management device applicable also to a wide network environment such as the Internet and strong against faults in a server and hardly generating losses of work process information. SOLUTION: In user side constitution 1 for requesting service, a work process specification part 11 generates working space information expressing virtual working space and stores the generated information in a working space storing part 12 correspondingly to work process information. A work process interpreting part 13 interprets the work process information and successively specifies service to be provided and a service request transmission part 14 transmits a service request as a token 3. In service providing side constitution 2, a service request receiving/storing part 16 receives and accumulates the token 3. Cooperative work is executed by a service requester interface part 15 and a service provider interface 17 through the working space in accordance with the stored service request to provide service.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a work process management device which supports performing a work in accordance with a series of work procedures expressed as a work process. The present invention relates to a work process management apparatus capable of controlling the execution of a work process without requiring a centralized management mechanism in a computer network communicating through a network.

[0002]

2. Description of the Related Art Many conventional workflow management systems and document circulation systems are intended to manage work processes assuming a relatively small work group such as a local area network (LAN) environment. For this reason, a centralized management system is adopted in which a work process execution mechanism and a document circulation control mechanism that are linked to a database or the like are arranged on one server, and workers access the server from a client and execute work. I was

On the other hand, in a wide area network environment typified by the Internet, when a plurality of organizations execute work processes or circulate documents, management is concentrated on a single server as described above. In the centralized management system, problems such as a reduction in efficiency due to the concentration of processing and a low reliability of the entire system are expected to occur.

[0004] The following techniques exist to address such a problem and support work process management in a wide area network environment. For example, in a system described in JP-A-8-320901, a server that stores a work process expressed as a document flow and a server that executes the work process are arranged for each department. When a work process executed in one department is executed in cooperation with the process of a work process managed in another department, the processed document is executed by the work process of the other department. The process is transferred to the server, and the process is performed while passing the process between the work process execution servers between departments.

In the system described in Japanese Patent Application Laid-Open No. 9-190399, a workflow management system of a different manufacturer is sent by sending an e-mail at the time of executing a work process to activate a workflow management system of a cooperation destination. Multiple different work process execution engines are dynamically linked. Information on the execution control of the work process is automatically exchanged between the workflow management systems by e-mail.

Further, L. Nastansky, W. Hilpert, “The
GroupFlow System: A Scalable Approach to Workflow M
anagement between Cooperation and Automation ”,
B. Wolfinger (Ed.), Proceedings of 24th Annual Confe
rence of the German Computer Society during 13th W
orld Computer Congress, IFIP '94, Springer Verlag,
In the system described in Berlin, Heidelberg etc., 1994, pp.473-479., Work processes are mutually started by exchanging messages by e-mail between multiple servers that manage workflows within an organization. And enable the execution of work processes that span organizations.

Further, WfMC (The Workflow Managem)
ent Coalition), “The Workflow Reference Mode
l ”, WFMC-TC00-1003, Issue 1.1), the system described in 1995 crosses a plurality of workflow engines by exchanging workflows expressed in a common format between different workflow engines. A standardization proposal for realizing the execution of the workflow is shown.

In the systems described in the above-mentioned documents, a method is proposed in which a work process managed by each work process management server is operated as a wide-area work process by cooperation between servers. However, this method has a problem that when a failure occurs in any of the work process management servers, all the work processes managed by that server are stopped.

As another work process management technique, for example, in a system described in Japanese Patent Application Laid-Open No. 6-290116, a work process execution interpreter is arranged in each computer (workstation) on a network, and a document is provided. The groups are exchanged between the computers as "objects" in units of work processes defined in association with the groups. The work process execution interpreter of each computer interprets and executes the work process included in the "object" and transmits the "object" to the next computer to advance the work process.

[0010] Japanese Patent Application Laid-Open No. 9-261267 describes a system for starting a system for performing a specific business process in association with a process type specified in an e-mail message. When the received e-mail includes a processing type related to another business process, the execution of the work is linked while transmitting a copy of the message to a partner capable of the business process.

In Japanese Patent Application Laid-Open No. H10-124596, an action relating to workflow control is attached to a document. A working process management method is described.

In the system described in US Pat. No. 5,754,857, a program corresponding to a work process execution engine called “workflow courier” is executed on a Java platform based on a work process. A work node is dynamically loaded on the client side which is a node in the process, and the work process is executed while dynamically loading the work process execution mechanism between clients having no work process execution mechanism.

In the system described in US Pat. No. 4,932,026, a document package with a circulation route is transmitted by an electronic mail system, and each client on the receiving side transmits the transmitted document. An operation environment for the package is provided, and the document package is exchanged between the clients via the electronic mail system according to the circulation route.

Further, A. Grasso, JL. Meunier, D. Pa
gani, and R. Pareschi, “Distributed Coordination a
nd Workflow on the World Wide Web ”, Computer Supp
orted Cooperative Work, The Journal of Collaborati
In the system described in ve Computing 6, 175-200, 1997, a work process cooperation server independent of these servers is specified in advance between servers that provide services to documents. Deriving a series of work processes according to the rules. In accordance with this work process, a series of processing is performed while a document moves between the servers. The execution of the work process is performed according to a work process coordinated by a server in charge of each document processing service.

[0015] In the technology described in these documents,
A method is adopted in which information obtained by attaching a work process to a document or an operation interface is transferred between a plurality of computers connected via a network based on the attached work process. However, such a method has a problem that if information including the work process is lost during the execution of the work process, it becomes difficult to continue the execution of the work process.

Further, since the conventional workflow management system is based on the premise that a routine work is performed according to a work process, a function for performing communication between a work process starter and a service provider when the work process is executed is provided. Nothing to do. However, when providing an atypical service, it is considered that means for performing highly interactive communication with the service requester is required.

In order to cope with such a problem, for example, H.
Lavana, A. Khetawat, and F. Brglez, “Internet-bas
ed Workflows: A Paradigm for Dynamically Reconfigu
In the system described in “rable Desktop Environment”, ACM Group '97, 1997, the work environment of the user corresponding to each node constituting the work process corresponds to the personal desktop, and the work process is performed by multiple workers. In this work process, at the point where a plurality of user flows intersect, the mutual desktop environment becomes accessible and the cooperative work can be performed. However, the communication here is performed by a shared text screen, but this method is intended for communication between work process performers, and supports communication between work process invokers and service providers. Not something.

[0018]

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned circumstances, and is a management system for performing a series of operations based on a work process through a cooperative operation between a service requester and a service provider. An object of the present invention is to provide a work process management apparatus which is applicable to a wide area network environment such as the Internet, is resistant to a server failure, and is unlikely to lose work process information.

[0019]

SUMMARY OF THE INVENTION According to the present invention, there is provided a work for performing a series of work for achieving a goal specified by a user while receiving various services provided through a virtual cooperative work space. A process management system, which is a work process management device applicable to a network to which a plurality of computers are connected. In particular, by disposing the work process control mechanism on the service requester side and making the service provider and service requester management mechanisms independent, it is possible to construct a distributed system, and also to prevent the server device from malfunctioning. It is resistant and avoids the loss of the work process itself.

In order to realize such a function, as a configuration of a user requesting a service, work process information indicating a virtual work space is generated according to a user's designation and work process information indicating a work procedure is provided. Means for associating the work space information with the work space information, a work space holding means for holding the work space information generated by the work process designating means together with the work process information, and interpreting and providing the work process information in the work space holding means. Work process interpreting means for sequentially specifying the service to be received, service request transmitting means for transmitting a service request to the next service to be provided specified by the work process interpreting means, and service request by the service request transmitting means Through the service space with the service provider on the service side that sent the And a service requestor interface means for providing a user interface for cooperative work. Further, as a configuration on the service side, a service request reception and accumulation unit that receives and accumulates a service request sent by a service request transmission unit on the user side, and a service request that is accumulated by the service request reception and accumulation unit, A service provider interface means for providing a user interface for performing cooperative work with a user through a work space corresponding to a service request source is provided.

The service provider interface means provides an interface for receiving an instruction necessary for providing a service to the user, in addition to the cooperative work through the work space, and provides an interface from the user at the interface. It can be configured to automatically execute a service based on the designation and provide an execution result to the user. Thus, the service provider can automatically provide a standard service by executing the program.

The service requester interface means and the service provider interface means detect an operation event of the user or the service provider on the work space, transmit the operation event to the other party, and reflect the operation event on the work space. Can be done. Thus, when providing a service, cooperative work can be performed while simultaneously sharing operations in the work space.

The service requests stored in the service request receiving and storing means are shared by a plurality of service providers, and a plurality of service provider interface means are arranged for the single service request receiving and storing means to provide each service. The user interface means retrieves the service requests stored in the service request receiving and storing means one by one and provides a service to the user through the service requester interface means corresponding to the work space from which the service request is transmitted. Can be. Thereby, a service can be provided by a plurality of service providers. Further, it is possible to dynamically increase or decrease the number of service providers according to the congestion state of the service without interrupting the provision of the service.

The service provider interface means includes a work space holding means, a work process designating means, and a service request transmission, when it is determined that a new work is necessary to derive from the service currently provided by the service provider. Means for starting execution of a new work, and further, the correspondence between the new work space generated by the work process designating means and the work space as a derivation source is held in each work space, Access to a new workspace derived from the current workspace or from the derived new workspace to the original workspace. This makes it possible to manage a series of tasks that the service provider does not directly involve and that are executed mainly by the service provider in association with the work space of the derivation source. In addition, the service provider retrieves a workspace derived from a certain workspace in which a service is being provided, or retrieves a workspace from which the source is derived upon completion of a work process in the derived workspace. , The service can be continued. The new work space may be generated separately from the user side by, for example, the work space holding unit, the work process designating unit, and the service request transmitting unit on the service providing side.

Further, the service provider has a subtask holding means for receiving designation of an execution procedure of a series of services required for providing the service, and holding the execution procedure as a work process. The interface means replaces the part of the work process held in the work space information for the work space providing the service, which specifies execution of the service, with the work process held in the subtask holding means and refines the work process. can do. As a result, it is possible to refine the work process step by step and dynamically in the process of receiving services according to the work process without having to specify a series of services constituting the work process in detail at the start of work. Therefore, the flexibility of the entire system can be increased.

The service provider interface means automatically generates a work space for the service provider when the service request is stored in the service request reception and storage means and the service is started, and the work space on the user side is provided. Can be stored in association with each other, and a shared workspace that enables data exchange between the workspace on the user side and the workspace on the service provider side can be generated. As a result, the data uniquely managed by the service requester can be managed by the service requester, and the data uniquely managed by the service provider can be managed by the service provider. Since the areas can be separated, security management can be easily realized.

At this time, the work process designating means provides a function for designating that a plurality of services receive cooperative work at the same time as a work process element, and the work process interpreting means is designated by the work process designating means. In the process of identifying the next service to be provided based on the work process, if an element that is specified to receive cooperative work among multiple services is detected, the specified The service request transmitting means controls the service request transmitting means so that the service request is transmitted at the same time, and the service requester interface means cooperates with all the service providers who transmitted the service request by the service request transmitting means through the work space, The service provider interface means includes a user's work space and other services. Scan may be configured to exchange data between the service provider side of the working space provided by. Thereby, the service requester can receive a plurality of services simultaneously and cooperatively in executing the work process, and can cope with a case where interactive coordination is required between the services.

The service requester interface means has a function of outputting a history of services received in the work space,
The work process designating means can take in the service history output by the service requester interface means as the work process information and associate it with the work space information. Thereby, the work process executed by the third party can be reused.

The service request reception / storage means notifies the work space corresponding to the service request of the service execution state in response to the reception of the service request and the retrieval of the service request from the service provider interface means. The user interface means can be configured to visualize the execution state of the service notified by the service request receiving and storing means. This allows
The entire execution state of the work process can be easily grasped.

The work space holding means can be configured to be able to hold a message in association with work space information.
Along with this, the service requester interface means and the service provider interface means enable input of a message and display the message held in the work space holding means, so that the user and the service requester are asynchronously connected. Communication can be configured. As a result, the user who is the service requester and the service provider can proceed with the work interactively without being mutually restricted by time.

The work space holding means stores a history of operation objects (documents, messages, application programs, and communication channels established with the service provider interface means of each service) used during execution of the work process. Can be held in association with the work space information with time, and the service requester interface means takes out the history of the operation target held in the work space holding means based on the time specified by the user, It can be configured so that the operation target used at the designated time can be accessed. Thus, the operation target can be managed in association with the work space, and when searching them, the work can be searched using the key as a key, so that the memory load of the user can be reduced.

Further, the work space holding means is capable of holding the state of each operation target used in conjunction with the execution of the work process at the time of execution of each service in association with each service, and a service corresponding to a certain service. The data is managed so that the provider interface means cannot access the operation target used when executing another service, and the service requester interface means:
The operation target held in the work space holding means can be extracted based on a service specified by the user, and the operation target used when executing the service can be configured to be accessible. This makes it possible to access the operation target in units of the services received in the past, and at the same time, it is possible to realize the confidentiality of the operation target between the services.

Further, a service providing environment preparation rule holding rule for automatically taking out an operation target (document, application program) used when the service provider provides a service based on a condition specified in advance. The service provider interface means retrieves the service request stored in the service request receiving and storing means, and provides the service. When providing the service, conditions necessary for providing the service and the service providing environment The rules held in the preparation rule holding means are collated, and when a corresponding rule is found, an operation target can be prepared based on the rule and used in the work space. As a result, it is possible to automatically prepare operation targets such as documents and application programs required for providing the service, and to efficiently provide the service.

At this time, a service providing environment condition designation form generation for generating a form for inputting a condition required for preparing a service providing environment based on the rules held in the service providing environment preparation rule holding means. Means for providing a service provider interface,
Upon detecting the reception of the service request, the form generated by the service providing environment condition specification form generating means is transmitted to the service request source, and the service requester interface means receives the form and sends the user condition information in accordance with the form. The condition information can be returned to the service provider interface means upon input. As a result, based on detailed information on service provision specified by the user, the operation targets such as documents and application programs required for providing the service are automatically prepared, and the service is efficiently provided. Can be.

[0035]

FIG. 1 is a basic configuration diagram showing an embodiment of a work process management apparatus according to the present invention. In the figure, 1 is a user side configuration, 2 is a service provider side configuration, 3
Is a token, 11 is a work process designating unit, 12 is a work space holding unit, 13 is a work process interpreting unit, 14 is a service request transmitting unit, 15 is a service requester interface unit, 16 is a service request receiving and storing unit, and 17 is a service. This is a provider interface unit.

The configuration shown in FIG. 1 comprises a user-side configuration 1 and a service-provider-side configuration 2, and the service-provider-side configuration 2 provides various services. When the user side configuration 1 intends to receive a service, the token 3 is transmitted from the user side configuration 1 to the service provider side configuration 2 as a service request. Service provider side configuration 2
Then, the token 3 is received and the service corresponding to the request is provided to the user.

The user-side configuration 1 includes a work process designating unit 11, a work space holding unit 12, a work process interpreting unit 13, a service request transmitting unit 14, and a service requester interface unit 15.

The work process designation section 11 responds to a goal designated by the user, for example, a goal for accomplishing the work.
Generate work space information representing a virtual work space.
In addition, a work procedure for accomplishing a goal for accomplishing a work specified by a user is input as work process information indicating a work procedure expressed as a movement route between services provided by the service providing side configuration 2. Then, the work process information is associated with the work space information. Then, the work space information and the work process information are stored in the work space holding unit 12.
To be stored.

The work space holding unit 12 stores work space information generated by the work process designating unit 11 and information necessary for performing various work processes such as work process information associated with the work space. Hold in.

The work process interpreting section 13 interprets the work process specified by the work process specifying section 11 and sequentially synchronizes the services provided by the service providing side configuration 2 with the completion of the service provision. Next, identify the services to be provided.

The service request transmitting unit 14 transmits a service request as a token 3 to the service providing side configuration 2 for the service to be provided next specified by the work process interpreting unit 13.

The service requester interface unit 15
It provides a user interface for performing cooperative work through the work space generated by the work process designating unit 11 with the service provider of the service providing side configuration 2 that has transmitted the service request by the service request transmitting unit 14.

The service provider side configuration 2 includes a service request reception / storage section 16, a service provider interface section 17
have. The service request receiving and storing unit 16 receives the token 3 transmitted from the service request transmitting unit 14 of the user side configuration 1, and stores the service request from the user. The service provider interface unit 17 provides a user interface for performing collaborative work with the user through the work space that is the source of the service request in response to the service request received and stored by the service request reception / storage unit 16. To provide.

The user-side configuration 1 and the service-provider-side configuration 2 may be realized in the same computer so that one or many terminal devices are operated by the user or the service provider, but a plurality of computers are connected. It can be realized in a network. The network is not limited to the local area network (LAN),
A wide area network or the Internet may be used. The user can perform a series of work (work process) for achieving the goal specified by the user while receiving various services provided on the network through the virtual work space.

Also, in such a distributed configuration, work space information and work process information for advancing a work process to the user side configuration 1 are held.
As in the related art, when an error occurs in a server device, all work processes do not stop. Further, the work process is not lost due to the loss of the mail or the document during the execution of the work process.

FIG. 2 is a block diagram showing a first configuration example of an embodiment of the work process management device of the present invention. In the figure, 21 is a service requesting client, 2
2 is a service requesting server, 23 is a service providing server, 24 and 25 are service providing clients, 26 is a network, 31 is a Web browser, 32 is a work process execution engine, 33 is a service providing manager,
34 is an HTTP server, 41 is a work process generation designating unit, 42 is a work space holding area, 43 is a work process interpreter, 44 is a token transmission mechanism, 45 is an applet storage area, 46 is a work process execution interface, and 51 is a token receiving mechanism. , 52 are token storage queues, 53 is a service provider work space holding area, 54 is an applet saving area, 55 is a subtask saving area, and 56 is a service providing interface.

This configuration example shows an example in which a work process management apparatus of the present invention is realized on a system in which a plurality of servers and a plurality of clients are connected to a network 26. Each server has a World Wide Web (Worl
An HTTP server 34 for managing d-Wide Web) is provided. In addition, each client is provided with a Web browser 31 capable of executing a program in response to a remote procedure invocation (RMI). For example, it is possible to use a Web browser or the like capable of executing a Java program by incorporating a Java virtual machine.

The Web browser 31 is, for example, the service requesting server 21 in the service requesting client 21.
2 to receive and execute the applet of the work process execution interface 46 sent from the server 2. by this,
The service requester interface unit 15 of FIG. 1 is realized. Further, for example, the service providing client 24,
25, the service providing interface 56 sent from the service providing server 23.
To receive and execute the applet. As a result, FIG.
Of the service provider interface unit 17 of FIG.

In the server connected to the network 26, one or both of the work process execution engine 32 and the service providing manager 33 can be arranged. In this example, the service requesting server 22 in which only the work process execution engine 32 is arranged
And a service providing server 23 in which a service providing manager 33 is arranged. Here, it is assumed that the work process execution engine 32 and the service providing manager 33 are given unique addresses on a network expressed in the form of a URL (Universal Resource Locator). With this URL, even if there are many work process execution engines 32 and service provision managers 33 on the network 26, each of them can be specified.

The work process execution engine 32 has a work process generation / designation unit 41, a work process interpreter 43, a token transmission mechanism 44, and the like. 14, a work space holding area 42 that forms the work space holding unit 12 therein, and an applet storage area 45.

The work process generation designating section 41 has an HTT
A work space is generated based on a user's instruction given via the P server 34, and the work space data is held in the work space holding area 42. For each workspace, a unique address on the network 26 expressed in the form of a URL is given as a workspace address, and an interface for accessing each data constituting the workspace data is provided. .

The work space holding area 42 holds work space data for each work space. FIG. 3 is an explanatory diagram of an example of the data structure of the work space data. As shown in FIG. 3, for example, each workspace data is composed of information such as a workspace ID, a workspace name, an object group, a work process, a current activity, a derivation workspace, a derivation workspace, a message storage area, and the like. be able to. The objects that make up the object group include, for example, information such as an object ID, object data, an object type (a distinction between “document file” and “URL”), a position, and the like. In addition, the position information expresses the coordinates in the shared work space and the individual work space in each service unit, and may be constituted by information such as an activity ID, a shared / individual tag, an X coordinate, and a Y coordinate. it can. Also,
The derivation source workspace and the derivation destination workspace store the addresses of the workspaces given in the form of URL. Each message stored in the message storage area includes, for example, a message body, a transmission date and time, a sender, and the like.

The work process information in the work space data is stored as data having a structure in units of activities. FIG. 4 is an explanatory diagram of an example of the data structure of the work process. As shown in FIG. 4, the activities constituting each work process include an activity ID, a service provider URL, a service provider address, an execution state, a next process tag, and a next process list. here,
The activity ID is a unique identifier within the work space data. The service provider URL is the address of the token storage area, and the service provider address is the address of the client actually operated by the service provider.
The execution state is set to one of the states “unexecuted”, “waiting for execution”, “under execution”, “completed”, and “aborted”. The type of “parallel” or “synthesis” is set in the next process tag. When this next process tag is “synthesis”, that is, in the case of a “synthesis” service in which a plurality of services cooperate and operate as one service, those service groups have the same activity ID. In the next process list, a list of activities of the next process is set. Of course, various other information may be included as the work process information. The same applies to the activity information.

Such a work process can be created, for example, as a file described in a predetermined format. FIG. 5 is an explanatory diagram of an example of a description format of a file describing a work process. In FIG.
“[A]” indicates a sequence of zero or more a, and “a | b |
c "represents one of a, b, and c. The description format is not limited to the format shown in FIG. Any description format may be used.
The activity only needs to include at least the service providing URL of the activity data shown in FIG. Of course, it may have other information.

For example, the file storing the data of the work process described in the description format as shown in FIG.
Can be held as a work process of the type shown in FIG. The file storing the work process data described in the description format as shown in FIG.
For example, they can be exchanged between users by e-mail, or stored in an external database and shared between users.

Returning to FIG. 2, the work process interpreter 43 of the work process execution engine 32 interprets the work process of each work space data held in the work space holding area 42, and addresses the next service to be enjoyed. Is calculated.

The token transmitting mechanism 44 transmits a token 3 (see FIG. 1) as a service request to each service address calculated by the work process interpreter 43. FIG. 6 is an explanatory diagram of an example of the data structure of the token. The token 3 includes a token ID, a request source address, a request destination address, an activity ID, a tag combination service tag, and the like. The token ID is uniquely determined in the network 26. The request source address is given as an address corresponding to the work space of the request source. The request destination address is given as the address of the service providing manager. Activity ID is
The activity ID of the activity corresponding to the service. The composite service tag indicates whether or not the composite service is provided by a plurality of services. Token 3
Is converted into a data format that can be transferred on the network 26 by an object serialization mechanism provided by the Java platform, and converted to an address specified by a request destination address between servers using an RMI mechanism. Can be sent. Of course, the token 3 may be transferred by another mechanism.

The applet of the work process execution interface 46 is stored in the applet storage area 45. The work process execution interface 46 is provided to the user by loading the applet of the work process execution interface 46 on the Web browser 31 of each service requesting client 21 on the network 26 via the network 26 and then executing the applet. .

The service providing manager 33 includes a token receiving mechanism 51 and a token storing queue 52 constituting the service request receiving and storing unit 16 of FIG. 1, a service provider working space holding area 53, an applet saving area 54, and a subtask saving area 55. have. Token receiving mechanism 5
1 receives the token 3 transmitted by the work process execution engine 32.

The token storage queue 52 holds the token 3 received by the token receiving mechanism 51. FIG. 7 is an explanatory diagram of an example of the data structure of the token storage queue area and the received token in the first configuration example. The token storage queue 52 accumulates tokens 3 in the order of arrival in a token storage queue area having a queue structure as shown in FIG. The received token 3 is stored in the token storage queue area as a received token.
As shown in FIG. 7, the received token includes a token, a reception time, a service person, and a service providing state. The received token stored in the token storage queue 52 provides a token access mechanism for accessing from a plurality of clients through the service providing interface 56. This token access mechanism
The URL provided to the service providing manager 33 allows access from a client on the service providing side.

The service provider work space holding area 53 is
It holds the data of the work space for the service provider generated by the service providing manager. FIG. 8 is an explanatory diagram of an example of a data structure of service provider work space data. The service provider work space data includes, for example, a work space ID, an object group, a service provision destination address, a service start date and time, a service end date and time, as shown in FIG.
It can be composed of fields such as service providers.

The applet of the service providing interface 56 is stored in the applet storage area 54.
The applet of this service providing interface 56 is
Each service providing client 2 on the network 26
4 and 25, after loading via the network 26 on the web browser 31, executing the service providing interface 56 to the service provider.
Can be provided.

The subtask storage area 55 receives a specification of a series of service execution procedures required for providing a service from the service providing interface 56,
The execution procedure is saved as a work process (subtask).

Next, an example of the operation of the first configuration example in the embodiment of the work process management device of the present invention will be described. First, the operation on the service request side will be described. First, the user creates a work space and specifies a corresponding work process. When the URL corresponding to the respective work process execution engine 32 is designated from the Web browser 31 running on the service requesting client 21, the applet of the work process execution interface is loaded from the applet holding area 45, and
It is executed on the b browser 31. Thereby, the work process execution interface 46 is provided.

FIG. 9 is an explanatory diagram of an example of a display screen provided to the user by the work process execution interface.
In the figure, 61 is a work space list area, 62 is an activity list area, 63 is a work process control panel, 64
Is a message exchange area, 65 is a message display area, 6
6 is a message input area, 67 is a shared work area, and 68 is a personal work area. The work process execution interface 46 presents a display screen, for example, as shown in FIG.

The Web browser 31 has a message exchange area 6 including a work space list area 61, an activity list area 62, a work process control panel 63, a message display area 65, and a message input area 66.
4, respective areas such as a shared work area 67 and a personal work area 68 are displayed.

The work space list area 61 displays a list of generated virtual work spaces. The activity list area 62 displays an order relationship of a series of services enjoyed by the work space selected in the work space list area 61 and an execution state thereof. Work process control panel 63
Arranges various virtual buttons for controlling the execution of a work process. In this example, an “execute” button, a “stop” button, and a “history output” button are arranged. The message exchange area 64 is an area for exchanging text messages with the service provider, and includes a message display area 65 for displaying a message from the service provider, and a message input area for inputting a message to the service provider. 66.
The shared work area 67 is a work area for performing cooperative work with the service provider. The personal work area 68 is an area used by the user as a personal work area corresponding to the work process.

When a new work space is created and a work process is designated, the user operates the display screen of the work process execution interface 46 as described above.
In the work space list area 61, for example, a menu “work space generation” is selected from a pop-up menu or the like. Further, a name of a newly created work space and a file describing a work process in the format shown in FIG. 5 are specified. FIG.
0 is an overview diagram of an example of a window for specifying a file describing a work process. When a file in which a work process is described is specified, for example, a window as shown in FIG. 10 is displayed, so it is sufficient to specify the file name and indicate “complete”.

When these designations are completed, the work process creation designation unit 41 creates new work space data having a structure as shown in FIG. New workspace data includes:
In the work process execution engine 32, a unique identifier is stored in a field of a workspace ID, and a designated workspace name is stored in a field of a workspace name. Further, the work process described in the designated file is converted into, for example, data in the format shown in FIG. Are stored in the fields of the current activity, respectively. When the data format of the file as shown in FIG. 5 is converted into the data of the internal structure as shown in FIG. The value of "parallel" or "synthesis" is set. Also, the same “Activity I” is included in the activities forming the “composite” service.
D ”is set. These work space data and work process data are held in the work space holding area 42.

In the activity list area 62 being displayed on the work process execution interface 46, the execution status of each service constituting the work process of the work space specified in the work space list area 61 is displayed. Extract from the data of the work process inside and display it as a tree-like list.

An event listener is associated with the execution state field of each activity constituting the work process of the work space data. The execution state of the activity is changed on the service providing side by the provision of the service. It is also changed when the user instructs to stop providing the service. When the value of a field in the execution state changes, an event related to the data change occurs and is detected by the corresponding event listener,
The display of the activity list area 62 is updated. The event processing here can be realized by, for example, an event processing mechanism provided by Java. By displaying such an execution state, the user can easily grasp the overall progress of the work process and the like.

FIG. 11 is a flowchart showing an example of processing for executing a work process and transmitting a token to the service providing manager 33. A work space is selected in the work space list area 61 on the display screen of the work process execution interface 46, and an “execute” button on the work process execution control panel 63 is operated. Then, after confirming the operation of the “execute” button in S101, the work process interpreter 43 obtains the next service to be executed from the execution state of the work process held in the selected work space, and obtains the token related to the address of the service. Generate

Here, first, in S102, it is confirmed that the execution state field of the activity in the work process indicated by the current activity of the work space selected in the work space list area 61 is "completed" or "canceled". I do. Thereafter, in S103, the activity of the next process is extracted by referring to the field of the next process list.

Next, in S104, the processes in S111 to S113 are performed in accordance with the individual activities extracted in S103. In S111, for example, new token data as shown in FIG. 6 is generated. At this time, a unique identifier on the network is set in the token ID field. In the workspace name field, the workspace name of the selected workspace is set. Further, the URL corresponding to the work space selected in the work space list area 61 is set in the field of the service request source. In the field of the service request destination, the service provider UR in the activity is displayed.
Set the contents of the L field. Here, the service providing URL held by one or more activities set in the next process activity list is set in the field of the service request destination. Further, an activity ID in the activity is set in the activity ID field. In the field of the composite service tag, values of “parallel” and “composite” indicated by the next process tag are set.

The token generated in this way is referred to as S1
In step 12, the data is converted into data that can be transferred on the network 26. For example, object serialization (Object Seria
lization) mechanism. Then, in S113, the token transmitting mechanism 44 transmits the token to the service providing manager indicated by the service request destination of the token, for example, by using an RMI mechanism. As a result, the service is provided by the service providing manager that has received the token.

When the service in the “waiting for execution” or “in execution” state is canceled, the “cancel” button on the work process control panel 63 in the display screen of the work process execution interface 46 is operated. Good. Then, in the work process held by the work space data, the “execution state” corresponding to the currently received service
Is set to "stop" and the service is stopped.

In the state where a work space is selected in the work space list area 61 on the display screen of the work process execution interface 46 and a work process related to the work space is displayed in the activity list area 62,
Select a service (activity) that is currently in "running" state. Then, a shared work area 67 and a personal work area 68 for performing cooperative work with a service provider in the selected service are displayed on the display screen of the work process execution interface 46. In the personal work area 68 and the shared work area 67, an icon corresponding to the object type field of the object data indicated by the object group field held in the work space data is displayed. At this time, an activity ID also included in the information on the position of the object data, an individual / shared tag for distinguishing the individual work area 68 from the shared work area 67,
And an icon is displayed based on the X coordinate and the Y coordinate which are the position information in the area. When a new service is started, the information of the position of each object is reset to the value of the position where the icon was placed in the previous service, and then the icon of each object is displayed. Here, the activity ID in the location information includes the activity ID corresponding to the selected activity.
Is set. When a plurality of activities have the same activity ID (that is, in the case of a composite activity), the shared work area 67 is shared among the plurality of activity IDs. When a certain service is executed as a post-process of a plurality of services executed in parallel, the position used by the plurality of services is used as it is in the post-process service.

FIG. 12 is a flowchart showing an example of an event propagation process in the shared work area. When the user operating the work process execution interface 46 in the shared work area 67 operates an icon corresponding to an object with a mouse or the like, the operation event is detected in step S121 by, for example, an event handler. In step S122, an activity corresponding to the service currently selected in the activity list in the work process of the work space data is extracted. In S123, the operation event is transmitted to all the addresses stored in the service provider address of the activity extracted in S122. To transmit the event, the event is converted into data that can be exchanged on the network 26 by, for example, Java object serialization technology, and a remote method call (RMI) provided by the Java platform is provided.
It is possible to propagate by the mechanism of.

The position of the icon corresponding to the object on the personal work area 68 or the shared work area 67 is sequentially stored as information on the position of the work space data in the object data with the change. The activity ID in the position information includes the activity ID of the activity in the work process corresponding to the currently selected service, and the personal / shared tag includes the identifier corresponding to the personal work area 68 or the shared work area 67. , X coordinate, and Y coordinate store the position in each area.

If an event is notified from another device such as the service providing clients 24 and 25, the event is detected in S124, and the operation of the detected event is reflected in the supply work area 67 in S125. I do.

The shared work area 67 or the personal work area 68
By selecting an icon corresponding to the object with the mouse above and performing a predetermined operation such as operating the right button, for example, a pop-up menu relating to the operation of the object can be displayed. Pop-up menus include "cut", "copy",
"Generate", "Paste", "Edit", "Delete", etc. are displayed. In the example shown in FIG.
Only "Copy", "Generate", "Edit", and "Delete" are displayed.

When "generate" is selected, a new object corresponding to the specified object type is generated,
Stored in workspace data. At the same time, information on the position in the object data is also set. When "edit" is selected, the object data corresponding to the icon is taken out of the work space data, the applet for editing the document is loaded on the web browser 31, and the editing can be performed in another window. When "delete" is selected, the object corresponding to the icon is deleted from the work space data. When "Cut" or "Copy" is selected, the object corresponding to the icon is copied into the paste area secured in the memory, and when "Paste" is instructed, the mouse is A new object having the location designated by the position information is generated. When “cut” is specified, the object specified at that time is deleted from the work space data.

The message exchange area 64 in the display screen of the work process execution interface has a message display area 65 and a message input area 66 as shown in FIG.
Composed of Here, the message input area 66
Is input to the message storage area in the work space data.
As shown in FIG. 3, the message includes a message body,
The date and time of the call and the caller. The input message is stored in the message body, the time acquired from the clock built in the computer is the transmission date and time, and the machine address of the client is stored in the sender. At the same time, the message stored in the message body together with the sender's address is sequentially displayed in the message display area 65 in the order of the sending time.

On the display screen of the work process execution interface 46, a work space is selected in the work space list area 61, and a work process related to the work space is displayed in the activity list area 62.
Select a service (activity) that has already been executed. Then, the shared work area 6 as a result of performing the cooperative work with the person in charge of providing the service in the selected service
7 and a personal work area 68 are displayed. Note that the position of the object cannot be changed here, but, for example, by operating the right mouse button, a pop-up menu is displayed, and the object data of the selected object is extracted by the “cut”, and the object data is stored in the memory. Can be accumulated in the paste buffer. Then, the data accumulated in this paste buffer is
In the personal work area 68 or the shared work area 67 that is currently being operated, a pop-up menu is displayed by operating the right mouse button, for example, and restored to an editable form by “pasting”. it can.

On the display screen of the work process execution interface 46, when the "history output" button on the work process execution control panel 63 is operated in a state where the work space is selected in the work space list area 61, the work space is selected up to that point. A series of services received can be output as a work process file. FIG. 13 is an explanatory diagram of an example of the work process output designation screen. By operating the "history output" button, a window for specifying an output destination, for example, as shown in FIG. 13, is opened. Here, an output destination file name or the like for outputting the work process is input, and, for example, a “Done” button is operated.

When the designation of the output destination file is completed, the activities whose execution status is “completed” among the activities stored in the work process in the work space data corresponding to the work space are traced and extracted. Then, the work process described in the syntax in the format shown in FIG. 5 is output to the output destination file specified in the window shown in FIG. The file output in this way can be read as a work process if it is designated when the work space is generated, for example, so that the work process can be reused. Further, if this file is held in, for example, a shared database, a plurality of users can share the same work process.

Here, an activity in a work process in which the execution state is “completed” is treated as “history”. The present invention is not limited to this. For example, the work space data may further hold a history field. In the history field, the history of services received up to any point in time,
For example, it can be stored together with time information. The user retrieves the history based on time and accesses the operation target (document, message, application program, and communication channel established between the service providing interface 56 of each service) used at that time. Is possible. As a result, there is no need to store the services that have been enjoyed so far, and it is possible to search using work or time as a key if desired. Also, as described above,
The user can retrieve the history data through the work process execution interface 46 and output it as a re-executable work process data file. The output file holds history data, for example, as data in the format shown in FIG. 5 and is read in via the work process execution interface 46, thereby holding it in the work space holding area 42 as a work process as described above. Can be done.

Next, the operation accompanying the service provision on the service providing side will be described. The token receiving mechanism 51 of the service providing manager 33 receives the token sent via the network 46, and sequentially stores it as a new received token in a token storage queue 52 having a data structure as shown in FIG. go. At this time, for the newly added received token, the received token data is set as the token, and the current time obtained by the clock held by the computer in which the service providing manager 33 is operating is set as the received time.

Each received token stored in the token storage queue 52 can be configured to be shared by, for example, a plurality of service providers. Thereby, a service can be provided by a plurality of service providers. In addition, it is possible to dynamically increase or decrease the number of service providers according to the congestion state of the service without interrupting the provision of the service.

When the URL corresponding to the service providing manager 33 is designated by the Web browser 31 running on the service providing clients 24 and 25, the applet of the service providing interface 56 stored in the applet storage area 54 is opened. It is loaded into the Web browser 31 via the network 26 and executed. As a result, the service providers of the service providing clients 24 and 25 can provide the service via the service providing interface 56.

FIG. 14 is an explanatory diagram of an example of a display screen provided by the service providing interface to the service provider. In the figure, reference numeral 71 denotes a service waiting work space list area;
2 is an activity list area, 73 is a work process control panel, 74 is a message exchange area, 75 is a message display area, 76 is a message input area, 77 is a shared work area, and 78 is a service provider work area. The service providing interface 56 can present, for example, a display screen as shown in FIG. 14 to the service provider by the Web browser 31, for example.

In the service waiting work space list area 71, a list of work space names indicated by the request source addresses of the received tokens in the service waiting state stored in the token storage queue 52 is displayed. The activity list area 72 displays the activity of a subtask or a work process when a subtask or a new work process is derived. The work process control panel 73 has various virtual buttons for controlling the execution of the work process. In this example, "end service" button, "subtask registration" button, "subtask detail"
Button and "Derived" button. The message exchange area 74 is composed of a message display area 75 and a message input area 76, and is an area for performing synchronous and asynchronous message exchange between the service requester and the service provider. The shared work area 77 is an area shared by a service requester accessing the shared work space and the service provider. The service provider work area 78 is an area used by the service provider.

Select one of the work space names displayed in the service waiting work space list area 71, and select, for example, "provide service" from a pop-up menu. Then, the token corresponding to the selected workspace name is extracted from the token storage queue 52. Then, the activity in the work process held by the work space data indicated by the request source address included in the token is extracted based on the activity ID included in the token, and the execution state stored in the activity is extracted. When the value of the execution state is “abort”, the execution ends. The execution status is "Waiting"
In the case of (1), the execution state is set to “executing”, service provider workspace data is generated as a service provider workspace corresponding to the token, and is stored in the service provider workspace storage area 53. At this time, a unique identifier within the service providing manager 33 is set as the work space ID of the service provider work space data. In the service start date and time, the date and time when the token is extracted, which is detected from the clock built in the client, is set. Further, the user name of the service provider is set as the service provider, and the address specified as the service requester of the token is set as the service destination address. Further, based on the activity ID included in the token, the service provider address of the activity stored in the service requester's workspace data extracted based on the requester address in the token. Of the service provider.

Thus, the data uniquely managed by the service provider can be managed by the service provider work area 78, and security management becomes easy, for example.

Further, the service provider sets the shared work area 77
The key input and mouse operation performed in the above are transmitted to the service requester as an event, and it is possible to provide services to the service requester by performing cooperative work while simultaneously sharing operations in the virtual workspace. it can.

[0096] The shared work space 77 on the display screen of the service providing interface 56 is shared between a plurality of services when the composite service tag of the token is "composite". As a result, the service requester can simultaneously and cooperatively receive a plurality of services in executing the work process, and can cope with a case where interactive adjustment is required between the services. Conversely, the service cannot be shared between the services unless it is “synthesis”. Therefore, confidentiality of the operation target between the services can be realized.

The message exchange area in the display screen of the service providing interface 56 includes a message display area 75 and a message input area 76 as in the work process execution interface 46. Here, when a message is input to the message input area 76, the message is stored in the message storage area in the work space data specified by the request source address in the token. That is, the input message is stored in the message body, the time obtained from the clock built in the computer is the transmission date and time, and the machine address of the client is stored in the sender. At the same time, the messages stored in the message body are sequentially displayed in the message display area 75 together with the sender's address in the order of the sending time. As a result, asynchronous communication can be achieved with the service requester, and the work can proceed interactively without any mutual time constraints.

When the “end service” button is operated on the work process control panel 73, the work space data indicated by the service providing address is referred to, and based on the activity ID included in the token, The activity in the work space data is specified, and the execution state is set to “completed”.

When a “subtask registration” button is operated on the work process control panel 73, the subtask is saved. FIG. 15 is an explanatory diagram of an example of a window for inputting a subtask. By operating the “register subtask” button, for example, a window for inputting a subtask as shown in FIG. 15 is opened. Here, when the URL of the service providing manager 33 to be a subtask is specified, the result is stored in the subtask storage area 55.

When the “detail task” button is operated on the work process control panel 73, the subtask stored in the subtask storage area 55 is retrieved. Then, for the work process stored in the work space data of the service providing address which currently provides the service, the activity I included in the token is performed.
The extracted subtask is set as the subtask of the activity specified by D.

By utilizing such a subtask setting mechanism, a series of services constituting a work process can be specified in the process of receiving a service according to the work process without having to specify them in detail at the start of the work. Work processes can be refined step by step and dynamically. Thereby, the flexibility of the system can be increased.

"Derived" on work process control panel 73
When the button is operated, new work space data is generated. Then, a service providing destination address corresponding to the workspace currently handled by the service provider is set in a workspace from which the generated workspace data is derived, and a work process execution interface corresponding to the newly generated workspace is set. A window 46 opens. At the same time, the newly created workspace includes the work space data derived from the work space data indicated by the service provision address corresponding to the work space being processed by the service provider from which the derivation was performed. The URL of the data is set.

By this derivation process, a series of operations executed mainly by the service provider without directly involving the service requester can be managed in association with the derivation source workspace. . The service provider retrieves a derived workspace for a certain workspace in which the service is being provided, or retrieves a derived workspace when a work process is completed on the derived workspace.
Provision of services can be continued.

FIG. 16 is a block diagram showing a second configuration example of the embodiment of the work process management apparatus of the present invention. In the figure, the same parts as those in FIG. 81 is an application start condition designation form generation mechanism, 82 is an application start rule storage area, and 83 is an application start rule input interface mechanism. This second configuration example shows an example in which a service providing environment is set according to conditions.

The service providing manager 33 further includes:
Application start condition specification form generation mechanism 81,
An application start rule storage area 82 is provided. Application start condition specification form generation mechanism 8
Reference numeral 1 denotes a service providing environment condition specification form generation unit which generates an inquiry form based on attributes. The inquiry form can be generated in a format such as an HTML format. The application startup rule storage area 82 constitutes a service provision environment preparation rule holding unit, and stores rules relating to the startup of various applications that are automatically prepared with the provision of a service when a token is received. .

Further, the applet storage area 54 of the service providing manager 33 holds an applet of the application start rule input interface mechanism 83 for designating a rule regarding the start of the application.

The rules relating to the activation of the application may be in any data format. Here, as a specific example, “I
F attribute comparison operator value THEN application (argument 1, argument 2, ...) ". Here, the comparison operator is “=”
(Equal to the value), “>” (greater than the value), “<” (smaller than the value), “<=” (less than the value), “> =” (more than the value), “! =” (Equal to the value) Not).
The application to be activated may be a program such as a document editor, a spreadsheet, or a Web browser.

FIG. 17 is an explanatory diagram of an example of the data structure of the token storage queue and the received token in the second configuration example. The received token stored in the token storage queue 52 includes, in addition to the information shown in FIG. A pair has been added.

Next, an example of an operation in the second configuration example in the embodiment of the work process management apparatus according to the present invention will be described mainly with respect to a portion for providing a service according to a condition. Service providing client 24, 2
5, the applet storage area 54
The application start rule input interface 83 is provided by loading and starting the applet of the application start rule input interface 83 stored in the application start rule.

FIG. 18 is an explanatory diagram of an example of a display screen of the application start rule input interface 83. Application start rule input interface 8
As a result, the web browser 31 displays a display screen for inputting rules as shown in FIG. Here, a rule for starting the application is input. In the example shown in FIG. 18, the rule is input in the format of “IF attribute comparison operator value THEN application (argument 1, argument 2,...)”. For example, the first rule indicates that if the estimated amount exceeds 100,000 yen, the high-end estimate ledger file is opened by a "word processor". The following rule indicates that if the estimate destination is “A Shoji”, a predetermined HTML document is displayed by a “browser”. The rules input in this manner are stored in the application activation rule storage area 82.

When the token is received by the token receiving mechanism 51, the service providing manager 33 starts the application starting condition designating form generating mechanism 81, and sets the "attribute" of all the rules stored in the application starting rule storing area 82. Is extracted, and an HTML form for inputting a condition composed of the "attributes" is generated.

The HTML form generated by the application start condition specification form generation mechanism 81 is opened in the service requesting client 21 using, for example, the RMI mechanism based on the address specified by the request source address in the token. Is done. This process can be performed by, for example, a process of deriving a new work process on the service provider side.

FIG. 19 is an explanatory diagram of an example of the window of the application start condition designation form. The service requesting client 21 receives the HTML form generated by the application start condition specification form generation mechanism 81, and thereby opens a window of the application start condition specification form as shown in FIG. 19, for example. Then, the user can input a condition for each “attribute” in this window.

Upon completion of the input of the condition for the attribute from the user, each input attribute value is sent to the service providing manager 33 and stored as a service activation condition of the received token stored in the token storage queue 52. .

When the service provider takes out the received token from the token storage queue 52 through the service providing interface 56 and starts the service, the application is automatically started based on the service starting conditions contained in the received token. Then, the application is activated on the service provider workspace.

In this way, according to the conditions specified by the user who requests the service, the documents and application programs required for providing the service can be automatically started and the service can be prepared. Service can be provided. In the above example, the user is required to input the conditions. For example, when the content can be determined based on the content of the received token and the information of the service provider, a document or an application program necessary for providing the service is automatically generated. May be configured to be started.

FIG. 20 is a block diagram showing a third configuration example of the embodiment of the work process management apparatus of the present invention. In the figure, the same parts as those in FIG. 91 is a search result output mechanism, 92 is a search condition input form display mechanism, 93 is an automatic database search mechanism, and 94 is a database. This configuration example shows an example in which a service is automatically provided.

The service providing server 23 has a database 94 together with the service providing manager 33. The database 94 stores services provided by the service providing side to the service requesting side.

The service providing manager 33 has a search result output mechanism 91, a search condition input form display mechanism 92, and an automatic database search mechanism 93. The search condition input form display mechanism 92 displays a form for inputting execution conditions for instructing the automatic provision of a database search service in the shared work area 67 (FIG. 9) of the work process execution interface 46. The automatic database search mechanism 93 searches the database 94 based on the form input using the search condition input form display mechanism 92. The search result output mechanism 91 outputs the search result of the database 94 by the automatic database search mechanism 93 to the shared work area 67 of the work process execution interface 46.
Output to the top.

Next, an example of the operation relating to the automatic service provision of the third configuration example in the embodiment of the work process management apparatus of the present invention will be described. In the search condition input form display mechanism 92, when the token is received, based on the address specified by the request source address in the token, a database search condition formula prepared in advance is used, for example, using an RMI mechanism or the like. A search condition input form for designating is sent to the service requesting client 21. This process can be performed by, for example, a process of deriving a new work process on the service provider side.

FIG. 21 is an explanatory diagram of an example of the window of the search condition input form. In the service requesting client 21, for example, a window as shown in FIG. 21 is displayed by the search condition input form received from the search condition input form display mechanism 92. The user inputs search conditions using this form. The search condition expression can be expressed, for example, by combining a keyword with Boolean operators such as AND and OR. In the example shown in FIG. 21, the AND condition is indicated by “*”, the OR condition is indicated by “+”, and the priority of the operation is indicated by parentheses.

When the input of the search condition in the window of the search condition input form displayed by the search condition input form display mechanism 92 is completed, the input result of the search condition is sent to the automatic database search mechanism 93. The automatic database search mechanism 93 searches the database 94 based on the input search conditions.

The search result of the database 94 is converted into a fixed form document by the search result output mechanism 91, and is output as a document on the shared work area 67 on the display screen of the work process execution interface 46. Here,
The output of the search result document to the shared work area 67 on the display screen of the work process execution interface 46 can be realized by, for example, data transfer by the RMI mechanism with respect to the work space data indicated by the request source address in the token. .

Here, a case where a document is obtained as a search result has been described. However, the present invention is not limited to this.
4 may be configured to store an application that provides a service, execute an application obtained as a search result, and provide the execution result to the user.

In this way, for example, a fixed service can be automatically executed and a service can be provided to the user.

[0126]

As is apparent from the above description, according to the present invention, a mechanism for centrally managing work processes is not required, and a specific management mechanism or management for managing the entire network, such as the Internet, is not required. It is possible to execute a work process on a worldwide scale in a wide-area network environment where it is difficult to place workers.

Further, since the work process execution mechanism is distributed and arranged on the service requester side and operates independently of the service providing mechanism, the failure in the specific work process execution mechanism and the specific service A failure in the provider does not affect the execution of the entire work process. For this reason, the reliability of the whole system can be improved as compared with the conventional system, and at the same time, semi-permanent continuous operation of the whole system is enabled.

Further, since the service providing mechanism is separated from the work process execution management, a new service providing mechanism can be added / changed / deleted step by step independently of the work process execution. Become.

Further, since related information such as a document and a communication channel is associated with a virtual work space generated corresponding to each work process, a document, a conversation destination, and the like are set in units of a work process. Can be managed. As a result, the user's cognitive load in operation can be reduced.

Further, services requiring high interactivity are provided by using synchronous communication means, and asynchronous services are provided when providing services free from time constraints. For example, a communication means according to the nature of the service can be selected according to the situation.

Further, since the service providing interface on the service providing side can be dynamically added / deleted independently of the shared service request management mechanism, the service provider is arranged according to the degree of congestion to the service. can do. At the same time, the service can be provided by accessing the service request management mechanism from the service providing interface through the network, even if the services are remotely located on the network.

Further, since the work process execution mechanism on the service requesting side and the interface on the service requesting side are independent, the service requester can access the service requesting network through the network.
The service can be enjoyed by accessing the work process execution mechanism from the service request interface at various places. According to the present invention, there are various effects as described above.

[Brief description of the drawings]

FIG. 1 is a basic configuration diagram showing an embodiment of a work process management device of the present invention.

FIG. 2 is a block diagram showing a first configuration example according to an embodiment of the work process management device of the present invention.

FIG. 3 is an explanatory diagram of an example of a data structure of work space data.

FIG. 4 is an explanatory diagram of an example of a data structure of a work process.

FIG. 5 is an explanatory diagram of an example of a description format of a file describing a work process.

FIG. 6 is an explanatory diagram of an example of a data structure of a token.

FIG. 7 is an explanatory diagram of an example of a data structure of a token storage queue area and a received token in the first configuration example.

FIG. 8 is an explanatory diagram of an example of a data structure of service provider work space data.

FIG. 9 is an explanatory diagram of an example of a display screen provided to a user by a work process execution interface.

FIG. 10 is an outline view of an example of a window for designating a file describing a work process.

FIG. 11 is a flowchart illustrating an example of processing for executing a work process and transmitting a token to the service providing manager 33.

FIG. 12 is a flowchart illustrating an example of an event propagation process in a shared work area.

FIG. 13 is an explanatory diagram of an example of a work process output designation screen.

FIG. 14 is an explanatory diagram of an example of a display screen provided by a service providing interface to a service provider.

FIG. 15 is an explanatory diagram of an example of a subtask input window.

FIG. 16 is a block diagram showing a second configuration example according to an embodiment of the work process management device of the present invention.

FIG. 17 is an explanatory diagram of an example of a data structure of a token storage queue and a received token in the second configuration example.

FIG. 18 is an explanatory diagram of an example of a display screen of an application activation rule input interface.

FIG. 19 is an explanatory diagram of an example of a window of an application activation condition specification form.

FIG. 20 is a block diagram showing a third configuration example according to an embodiment of the work process management device of the present invention.

FIG. 21 is an explanatory diagram of an example of a window of a search condition input form.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... User side composition, 2 ... Service provider side composition, 3 ... Token, 11 ... Work process designation part, 12 ... Work space holding part, 13 ... Work process interpretation part, 14 ... Service request transmission part, 15 ... Service request User interface section,
16: Service request reception / storage unit, 17: Service provider interface unit, 21: Service requesting client, 22: Service requesting server, 23: Service providing server, 24, 25: Service providing client,
26 Network, 31 Web browser, 32 Work process execution engine, 33 Service provider manager, 34 HTTP server, 41 Work process generation designating unit, 42 Work space holding area, 43 Work process interpreter, 44 Token transmission mechanism, 45: applet storage area, 46: work process execution interface, 51: token reception mechanism, 52: token storage queue, 53: service provider work space holding area, 54
... applet storage area, 55 ... subtask storage area, 5
6 service providing interface, 61 work space list area, 62 activity list area, 63 work process control panel, 64 message exchange area, 6
5 Message display area 66 Message input area
67: shared work area, 68: personal work area, 71: service waiting work space list area, 72: activity list area, 73: work process control panel, 74: message exchange area, 75: message display area, 76 ...
Message input area, 77: shared work area, 78: service provider work area, 81: application start condition designation form generation mechanism, 82: application start rule storage area, 83: application start rule input interface mechanism, 91: search result output Mechanism, 92 ...
Search condition input form display mechanism, 93: Automatic database search mechanism, 94: Database.

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5B049 AA06 CC02 CC21 EE04 EE05 EE51 EE59 FF03 FF04 GG03 GG04 GG07 5B089 GA11 GB04 GB10 HA10 HB05 JA16 JA22 KA12 KB14

Claims (15)

[Claims] 1. A work process management system for performing a series of operations by receiving a provided service,
Work process designating means for generating work space information representing a virtual work space in accordance with a user's designation and associating work process information indicating work procedures with the work space information, and the work process designating means generated by the work process designating means. A work space holding means for holding work space information together with the work process information; a work process interpreting means for interpreting the work process information in the work space holding means and sequentially specifying a service to be provided; Service request transmitting means for transmitting a service request for the next service to be provided specified by the interpreting means; and a service provider on the service side transmitting the service request by the service request transmitting means, cooperative work through the work space Service that provides a user interface for performing Requester interface means, service request receiving and storing means for receiving and storing the service request sent by the service request transmitting means, and providing the service request to the service request stored by the service request receiving and storing means. A work process management device, comprising: service provider interface means for providing a user interface for performing cooperative work with the user through the work space corresponding to a transmission source. 2. The service provider interface means provides an interface for receiving an input of an instruction necessary for providing a service to the user, in addition to the cooperative work through the work space, 2. The work process management apparatus according to claim 1, wherein a service is automatically executed based on a designation from the user, and an execution result is provided to the user. 3. The service requester interface means and the service provider interface means detect an operation event on the work space by the user or the service provider and transmit the operation event to a partner. The work process management device according to claim 1, wherein the work process management device reflects the work process. 4. The service request stored in the service request receiving and storing means is shared by a plurality of service providers, and the service provider interface means is provided for a single service request receiving and storing means. A plurality of service provider interface means, each of which retrieves the service requests stored in the service request reception and storage means one by one and corresponds to the work space from which the service request is transmitted; The workflow management apparatus according to any one of claims 1 to 3, wherein a service is provided to the user through a web browser. 5. The service provider interface means, when it is determined that a new work is necessary to derive from a service currently provided by the service provider, the work space holding means, the work process designation. Means for starting execution of the new work by the service request transmitting means, and further, for each work, the correspondence between the new workspace generated by the work process designating means and the work space from which the work is derived. 5. The storage device according to claim 1, further comprising: a storage unit configured to store in the storage space, and enable access to a new work space derived from the work space of the derivation source or to the work space of the derivation source from the new work space derived. The work process management device according to any one of the above. 6. A service providing side further comprising: a subtask holding unit that receives a specification of an execution procedure of a series of services required for providing the service and holds the execution procedure as a work process. The provider interface means replaces a part of the work process held in the work space information for the work space providing the service, which specifies execution of the service, with a work process held in the subtask holding means. The work process management device according to claim 1, wherein the work process management device performs the detailed processing. 7. The service provider interface means automatically generates a work space for the service provider when the service request stored in the service request receiving and storing means is taken out and a service is started. Storing the workspace on the user side in association with the workspace on the user side and generating a shared workspace enabling data exchange between the workspace on the user side and the workspace on the service provider side. Claims 1 to 6 characterized by the above-mentioned.
The work process management device according to any one of the above. 8. The work process designating means provides a function for designating that a plurality of services receive cooperative work at the same time as an element of the work process. In the process of specifying the next service to be provided based on the work process specified in, when an element specified to receive cooperative work among multiple services is detected, the specified The service request transmitting means controls the service request transmitting means so that the service request is transmitted at the same time for the service, and the service requester interface means communicates with all the service providers who transmitted the service request by the service request transmitting means. The service provider interface means performs cooperative work through a space, and The work process management device according to claim 7, wherein data is exchanged between the work space on the user side and the work space on the service provider side provided by another service. 9. The service requester interface means has a function of outputting a history of services received in the work space, and the work process designating means outputs the work process information by the service requester interface means. 9. The work process management device according to claim 1, wherein a history of the service performed is taken in and associated with the work space information. 10. The service request receiving and storing means, in response to receiving a service request and fetching a service request from the service provider interface means, changes a service execution state to the work space corresponding to the service request. The work process according to any one of claims 1 to 9, wherein the notification is performed, and the service requester interface unit visualizes an execution state of the service notified by the service request reception / storage unit. Management device. 11. The work space holding means can hold a message in association with the work space information, and the service requester interface means and the service provider interface means can input a message. The message held in the work space holding means is displayed, and asynchronous communication is performed between the user and the service requester. The method according to any one of claims 1 to 10, wherein: A work process management device as described. 12. The work space holding means is capable of holding a history of operation targets used during execution of a work process in association with time with the work space information, and the service requester interface means is provided with: 4. The method according to claim 1, wherein the history of the operation target stored in the work space holding unit is retrieved based on the time specified by the user, and the operation target used at the specified time is accessed. Item 12. The work process management device according to any one of items 11. 13. The work space holding means can hold a state of an operation target used in conjunction with execution of a work process at the time of execution of each service in association with each service, and also corresponds to a certain service. Data is managed so that the service provider interface means cannot access the operation target used at the time of executing another service, and the service requester interface means operates the operation held in the work space holding means. 13. The work process management device according to claim 12, wherein an object is taken out based on a service designated by a user and an operation object used at the time of executing the service is accessed. 14. A service providing environment preparation rule holding means for holding a rule for automatically extracting an operation target used when the service provider provides a service based on a condition specified in advance. The service provider interface means retrieves the service request stored in the service request receiving and storing means and provides the service when providing the service, and the service provision environment preparation rule holding means. 2. The method according to claim 1, further comprising: comparing the rules stored in the workspace and, when a corresponding rule is found, preparing an operation target based on the rule so that the operation target can be used in the work space. Item 14. The work process management device according to any one of items 13. 15. A service providing environment condition designation form generation for generating a form for inputting a condition required for preparing a service providing environment based on a rule held in the service providing environment preparation rule holding means. Means for transmitting the form generated by the service providing environment condition designation form generating means to the service request source upon detecting reception of the service request, the service requester interface means comprising: 15. The work process management device according to claim 14, wherein the interface unit receives the form, causes the user to input condition information according to the form, and returns the condition information to the service provider interface unit.