JP2002197244A - Work management system, job management system, and work and job management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a work management system enabling to easily manage a work progress status by the action set in a job. SOLUTION: When a front-end application 11 receives the information specifying an action set in a job as an object of work, and details of operation for the action, the work management system is characterized to enable to make a client user manage the work condition for the action by changing the connection condition between a work directory 30a and a job directory 21a that stores a file for the job where the action, an object of work of the above work entity is set and is recorded in a storage medium or a file server 20 and also making the database server 40 record the information for the work condition of the work entity to the action set in the job.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

TECHNICAL FIELD The present invention relates to a work management system,
More specifically, the present invention relates to a work management system, a job management system, and a work / job management system capable of managing work and jobs in units of actions set for the job.

[0002]

2. Description of the Related Art Conventionally, when requesting work from another person at a company or the like, the amount of work time spent by the person who received the work is determined by the time taken by the person who received the work. Was recorded, and it was very vague.

In recent years, networking such as an in-house LAN has been rapidly progressing.
It is being performed through a network such as an in-house LAN.

FIG. 20 shows a data access method in a conventional in-house LAN or the like. In FIG. 20, 100
Indicates a shared hard disk area, which is set in advance so that it can be shared by a plurality of clients 200a, 200b, and 200c. Such sharing settings
Normally, this is performed when setting up an in-house LAN or the like. After setting, any client 200a, 200b, 200c
You can also access from. Therefore, one client 2
When requesting a job from another client 200b from 00a, the client 200a stores a file related to the job in the shared hard disk area, and then the other client 200b who has received the job accesses the shared hard disk area 100. He had access to work-related files and was working.

According to such a method, work can be requested through a network, which is excellent for speeding up work and increasing efficiency.

However, in a network using such an in-house LAN or the like, the shared hard disk area 100 is set in advance when setting the network, and the clients 200a, 200b, and 200c access files related to work only in the shared hard disk area. Since the user was accessing 100, it was not known at all which client was accessing which file.

That is, a plurality of clients 200a, 20
0b and 200c are always accessible, so even if the client who has received the work accesses the hard disk, it does not necessarily mean that the client is working on the work, and even if the client has accessed the hard disk. However, it was not possible to ascertain which job in the hard disk was being accessed, and the progress of the work on the side receiving the work had to be ascertained by recording the work on the side receiving the work as usual.

In addition, the person who requested the job could not grasp the progress of the requested job in the middle, and the person who requested the job could not manage the requested job.

[0009]

SUMMARY OF THE INVENTION Accordingly, the present invention has been made in view of such a conventional problem, and an object of the present invention is to easily manage the progress of work in units of actions set in a job. The purpose of the present invention is to provide a work management system.

Another object of the present invention is to provide a job management system capable of easily managing the progress of a job in units of actions set for the job.

Another object of the present invention is to provide a work / job management system capable of easily managing the work progress status and the job progress status for each action set for the job.

Other objects of the present invention will become apparent from the following description.

[0013]

[Means for Solving the Problems]

According to a first aspect of the present invention, there is provided a recording medium or a file server storing one or more job directories storing files relating to jobs, a database server, a client terminal,
A front-end application used by the client user at each client terminal, and a work directory on the client terminal provided in correspondence with the client user and the job directory, which are the work subjects, wherein the front-end application When receiving the action set for the target job and information for specifying the operation content for the action, the action recorded in the work directory and the recording medium or the file server and the action to be performed by the work subject are executed. Changing a connection state between the set job directory and a job directory storing files related to the set job, and causing the database server to record information on a work state of the work subject for an action set for the job. Therefore, a work management system which is characterized in that a manageable work state with respect to the actions of the client user.

In the present invention, a job is a unit of work defined by a series of work, and is a collection of work and also a management unit of data required in the series of work. For example, consider a case where 100 photos are input by a scanner, color correction of the input photo data is performed, and the data is output to a printer. If two workers share this process and perform 50 jobs each, they can be regarded as separate jobs. In this case, from the viewpoint of work, a job is a collection of a series of work of input, color correction, and output, and can be considered as a management unit of 50 pieces of photograph data from the viewpoint of data.

In the present invention, an action is a management entity on a system that is registered in a database table in association with a series of operations constituting the job.
A plurality of different actions can be assigned to one job. For example, job a is input, color correction,
In the case of three operations called output, three actions associated with the respective operations of input, color correction, and output are set for job a.

In the present invention, examples of the work subject include a client user, a front-end application, a client external application, a client terminal, and the like. The work subject is not a person who actually performs work on a job, but should manage work. Refers to the object. For example, even if a person who actually performs a work on a job is a client user, if the work management is to be performed for each front-end application, the work subject is the front-end application.

In the present invention, a client user is a user who uses a front-end application.

In the present invention, a directory is a memory, an HD (hard disk), an FD (floppy (registered trademark) disk), an MO
(Magneto-optical disk), a recording medium of a portion where data is recorded among recording media such as a CD-ROM. For example, when a job directory storing a certain job is recorded on the HD, if the job directory is expressed in hardware, it can be expressed as the HD of the portion where the data of the job is recorded.

According to a second aspect of the present invention, there is provided a recording medium or a file server recording one or more job directories storing files relating to jobs, a database server, a client terminal,
A front-end application used by the client user at the client terminal; and a work directory on the client terminal provided in correspondence with the front-end application and the job directory that are the main subjects of the work. In accordance with the action set for the target job and the information specifying the operation content for the action, a work directory, and a job recorded on the recording medium or file server and set with the target action of the work by the work subject In addition to changing the connection status with the job directory that stores the file related to the job, the information on the work status of the work subject for the action set for the job is recorded in the database server. By a work management system which is characterized in that a manageable work state with respect to the action of the front-end application.

In the present invention, a front-end application is application software that operates according to an instruction from a client user or a client external application, and realizes the system described in this specification.

According to a third aspect of the present invention, there is provided a recording medium or a file server recording one or more job directories storing files relating to jobs, a database server, a client terminal,
A front-end application used by the client external application on the client terminal; and a work directory on the client terminal provided corresponding to the client external application and the job directory that are the work subject. Receiving information specifying the action set for the target job and the operation content for the action, the action is recorded in the work directory and the recording medium or the file server, and the action to be performed by the work subject is performed. Changes the connection status with the job directory that stores the file related to the job for which the job has been set, and stores information on the work status of the work subject for the action set for the job in the database. By recording the Susaba a work management system according to claim capital which enables managing work state with respect to the actions of the client external application.

In the present invention, the client external application is application software other than the front-end application that operates using the front-end application or operates in conjunction therewith.

According to a fourth aspect of the present invention, there is provided a recording medium or a file server recording one or more job directories storing files relating to jobs, a database server, a client terminal,
A front-end application to be used on the client terminal, and a work directory on the client terminal provided corresponding to the client terminal and the job directory that are the work subject, wherein the front-end application is a job to be worked on , And the job in which the action recorded in the recording medium or the file server and in which the action to be performed by the work subject is set is received. By changing the connection state between the client directory and the job directory that stores the file related to the job, and recording information on the work state of the work subject for the action set for the job in the database server, A work management system which is characterized in that a manageable work state with respect to the action of the terminal.

The invention according to claim 5, which solves the above problem, is characterized in that the work directory is set so that a work subject other than the corresponding work subject cannot access the work directory. A work management system described in Crab.

According to a sixth aspect of the present invention to solve the above-mentioned problem, the work subject is in the connected state only during work, and is not in the connected state during non-work. 5. The work management system according to any one of 5.

According to a seventh aspect of the present invention, the front end application includes at least a first work state to a third work state as information on a work state of the work subject for an action set for the job. 7. The work management system according to claim 1, wherein any one of the states is recorded in a database server.

According to an eighth aspect of the present invention, the front end application includes at least a first work state to a third work state as information on a work state of the work subject for an action set in the job. 7. The work management system according to claim 1, wherein one of the states and a time at which the work state is changed are recorded in a database server.

According to a ninth aspect of the present invention, the front end application includes at least a first work state to a third work state as information on a work state of the work subject for an action set in the job. A database server records one of the states and the time at which the work state was changed, and the database server calculates and records a work time for the action for the work subject using the time. The work management system according to any one of claims 1 to 6.

According to a tenth aspect of the present invention, the front end application includes at least a first work state to a third work state as information on a work state of the work subject for an action set in the job. 7. The method according to claim 1, wherein one of the states and a time at which the work state is changed are recorded in a database server, and the work time for the action with respect to the work subject is calculated using the time. The work management system according to any one of the above.

According to an eleventh aspect of the present invention for solving the above-mentioned problems, the first work state acquires information on a storage destination of a job in which an action to be worked is set from a database server by a front-end application. 11. The work management system according to claim 7, wherein the work directory is recorded after directly connecting the job directory storing the job and the work directory according to the acquired information on the storage destination.

According to a twelfth aspect of the present invention, the second work state is recorded after the direct connection is once disconnected by a front-end application. An operation management system according to any one of the above.

According to a thirteenth aspect of the present invention, the third work state is recorded after the direct connection is disconnected by a front-end application and the work of the work subject is determined. The work management system according to any one of claims 7 to 10, wherein

According to a fourteenth aspect of the present invention, the first work status is obtained from the database server by the front-end application, the information relating to the storage destination of the job in which the action to be performed is set. A job directory storing the job in accordance with the obtained information about the storage location and the work directory are recorded after directly connecting, the second work state is recorded after the direct connection is temporarily disconnected by a front-end application, The third working state is:
The work management system according to any one of claims 7 to 10, wherein the work management system is recorded after the direct connection is disconnected by a front-end application and the work of the work subject is determined.

According to a fifteenth aspect of the present invention for solving the above-mentioned problems, when an instruction relating to any one of the first to third work states is received, the connection or connection is performed by the front-end application. Prior to the disconnection process, as authentication processing, a process of inquiring the work status of the work subject to the database server and a process of determining whether or not the instruction can be accepted based on the query result are performed. If the connection is determined to be acceptable, the connection or disconnection processing is performed, and if it is determined that the reception is not acceptable in the determination processing, processing for notifying that the instruction is not accepted is performed. Item 7-
14. The work management system according to any one of 14.

[0036] The invention according to claim 16 which solves the above-mentioned problem is that, when an instruction relating to any one of the first to third working states is received, the file server connects or disconnects. Prior to the process, as an authentication process, a process of inquiring the work state of the work subject to the database server and a process of determining whether or not the instruction can be received based on the result of the query are performed. If it is determined that the connection or disconnection is possible, the connection or disconnection process is performed, and if it is determined that the instruction is not acceptable in the determination process, a process of notifying that the instruction is not received is performed. An operation management system according to any one of 7-14.

[0037] In the invention according to claim 17 which solves the above-mentioned problem, in the authentication processing, the instruction of the first work state is accepted depending on whether there is an action to be worked or whether it is in the second work state. It is determined whether or not the instruction is possible. The instruction for the second operation state is determined based on whether or not the operation state is the first operation state. Whether the instruction for the third operation state is the first operation state or the second operation state. 17. The work management system according to claim 15, wherein it is determined whether or not the work can be accepted based on whether or not the work management system is in operation. 18.

According to an embodiment of the present invention, there is provided a recording medium or a file server which records one or more job directories storing files relating to jobs, a database server, a client terminal, and each client. A front-end application used by the work subject at the terminal, and a work directory on the client terminal provided corresponding to the work subject and the job directory, wherein the front-end application sets a job to be worked; The work directory, and a job directory that stores job data recorded on the recording medium or the file server and to be processed by the work subject when receiving the specified action and information for specifying the operation content for the action. Connection between With changing the state, by recording information about the configured action state to the job in the database server, a job management system characterized in that a manageable work status of the job.

The invention according to claim 19, wherein the job directory is set so that a work subject other than a corresponding work subject cannot access the work directory. It is a management system.

According to a twentieth aspect of the present invention for solving the above-mentioned problems, the working subject is in the connected state only when working, and is not in the connected state when not working. 20. A job management system according to any one of claims 19 to 19.

According to a twenty-first aspect of the present invention, the front-end application stores at least one of a first action state to a fourth action state as information on an action state set for the job. The job management system according to any one of claims 18 to 20, wherein the job management system is configured to cause the database server to record the following.

According to a twenty-second aspect of the present invention, the front-end application stores at least one of a first action state to a fourth action state as information on an action state set for the job. 21. The job management system according to claim 18, wherein a change time at which the action state is changed is recorded in a database server.

According to a twenty-third aspect of the present invention for solving the above-mentioned problem, the front-end application stores at least one of a first action state to a fourth action state as information relating to an action state set for the job. 21. The job management system according to claim 18, wherein a change time at which the action state is changed is recorded in a database server, and a work time for the action is calculated using the time. It is.

According to a twenty-fourth aspect of the present invention, the front-end application stores at least one of a first action state to a fourth action state as information on an action state set for the job. 21. A database server which records a change time at which the action state is changed, and the database server calculates and records a work time for the action using the time. A job management system according to the first aspect.

According to a twenty-fifth aspect of the present invention, the first action state is recorded after the front-end application sets an action for a job. 24. The job management system according to claim 24.

In the invention according to claim 26, which solves the above-mentioned problem, in the second action state, information on a storage destination of a job in which an action to be worked is set is acquired from a database server by a front-end application. 25. The job management system according to claim 21, wherein the job directory is recorded after directly connecting the job directory storing the job and the work directory in accordance with the acquired information on the storage destination.

The invention according to claim 27, which solves the above problem, is characterized in that the third action state is recorded after the direct connection is once disconnected by a front-end application. A job management system according to any one of the above.

According to a twenty-eighth aspect of the present invention, the fourth action state is recorded after the front-end application disconnects the direct connection and determines the action in the database server. The job management system according to any one of claims 21 to 24, wherein:

According to an embodiment of the present invention, the first action state is recorded after the front-end application has set an action for the job, and the second action state is recorded in the front-end application. The application obtains information on the storage location of the job for which the action to be performed is set from the database server, and records after directly connecting the job directory storing the job and the work directory according to the obtained storage location information. The third action state is recorded after the direct connection is temporarily disconnected by the front-end application, and the fourth action state is disconnected by the front-end application and the database server is notified of the action. Job management system according to any one of claims 21 to 24, characterized in that it is recorded after the constant.

According to a thirty-fifth aspect of the present invention for solving the above-mentioned problems, when an instruction regarding any one of the first action state to the fourth action state is received, the setting of the action is performed by the front-end application. Prior to the connection or disconnection process, as an authentication process, a process of querying the database server for the action state of the action, and a process of determining whether or not the instruction can be accepted based on the query result, If it is determined in the determining process that the instruction is acceptable, the action setting, the connection or disconnection process is performed, and if it is determined that the instruction is not acceptable in the determining process, a process of notifying that the instruction is not accepted is performed. The work management system according to any one of claims 21 to 29, wherein the work management system is performed.

According to a thirty-first aspect of the present invention for solving the above-mentioned problems, when an instruction concerning any one of the first action state to the fourth action state is received, the file server sets the action, Prior to the connection or disconnection process, as an authentication process, a process of inquiring the action state of the action to a database server and a process of determining whether or not the instruction can be accepted based on the query result are performed. If it is determined in the processing to be acceptable, the action setting, the connection or disconnection processing is performed, and if it is determined that the instruction is not acceptable in the determining processing, a processing to notify that the instruction is not accepted is performed. 22. The method according to claim 21, wherein
30. The work management system according to any one of claims to 29.

According to a thirty-second aspect of the present invention, in the authentication processing, it is determined whether or not an instruction of the first action state can be accepted based on whether or not a job to be set exists. It is determined whether the instruction in the two-action state is acceptable based on whether the state is the first action state, and whether the instruction in the third action state is acceptable based on whether the state is the second action state. 32. The work management system according to claim 30, wherein whether the instruction of the fourth action state is acceptable is determined based on whether the instruction is the second action state or the fourth action state. It is.

According to a thirty-third aspect of the present invention, there is provided a recording medium or file server recording one or more job directories storing files relating to jobs, a database server, a client terminal, and a client terminal. A front-end application used by the work subject at the terminal, and a plurality of work directories on the client terminal provided corresponding to each work subject and a job directory of a group of client users who are the work subjects, When the front-end application receives an action set for a job to be worked and information for specifying the operation content for the action, the work directory;
Changing the connection state between the storage medium and a job directory that stores job data recorded on the file server and targeted for the work of the work subject, and the work of the work subject for an action set in the job Work / job management wherein the work state of the work subject and the work state of the job can be managed by recording information on a state and information on an action state set for the job in the database server. System.

According to a thirty-fourth aspect of the present invention, there is provided a recording medium or file server recording one or more job directories storing files relating to jobs, a database server, a client terminal, and a client terminal. A front-end application used by the work subject at the terminal, and a plurality of work directories on the client terminal provided corresponding to each work subject and a job directory of the group consisting of the front-end application being the work subject; When the front-end application receives an action set for a job to be worked on and information for specifying an operation content for the action, the work directory is recorded on the recording medium or the file server and the work is performed. Subject Changes the connection status with the job directory that stores the job data to be worked, and also information on the work status of the work subject for the action set in the job and information on the action status set in the job Is recorded in the database server, so that the work state of the work subject and the work state of the job can be managed.

According to another aspect of the present invention, there is provided a recording medium or a file server which records one or more job directories storing files relating to jobs, a database server, a client terminal, and each client. A plurality of work directories on the client terminal provided corresponding to each work subject and a job directory of a group including a client external application which is the work subject, and a front end application used by the work subject at the terminal; When the front-end application receives an action set for a job to be worked on and information for specifying an operation content for the action, the work directory is recorded on the recording medium or the file server and the work is performed. main Changes the connection state with the job directory that stores the job data to be processed, and information on the work state of the work subject for the action set in the job and the action state set in the job. A work / job management system characterized in that the work state of the work subject and the work state of the job can be managed by recording information in the database server.

According to a thirty-sixth aspect of the present invention, there is provided a recording medium or a file server for recording one or more job directories storing files relating to a job, a database server, a client terminal, and a client terminal. A front-end application used by the work subject at the terminal, a plurality of work directories on the client terminal provided corresponding to each work subject and a job directory of a group consisting of the client terminal being the work subject, When the front-end application receives information specifying an action set for a job to be worked on and an operation content for the action, the work directory and the work medium recorded in the recording medium or the file server and The subject of work The connection state between the job directory and the job directory storing the job data to be stored is changed, and information on the work state of the work subject for the action set in the job and information on the action state set in the job are stored in the database server. , The work state of the work subject and the work state of the job can be managed.

According to a thirty-seventh aspect of the present invention, there is provided a recording medium or a file server which records one or more job directories storing files relating to jobs, a database server, a client terminal, and each client. A plurality of work directories on the client terminal provided in correspondence with the front-end application used by the work subject at the terminal, and the work subject and the job directory comprising a group of a client user, a front-end application, a client external application, and a client terminal. When the front-end application receives information specifying an action set for a job to be worked on and an operation content for the action, the work directory Change the connection state between the storage medium and a job directory that stores job data to be processed by the work subject, which is recorded on the file server, and the work state of the work subject with respect to the action set for the job A job status of the work subject and a job status of the job by recording the information on the job status and the action status set for the job in the database server. It is.

The invention according to claim 38, which solves the above-mentioned problem, is characterized in that the work directory is set so that a work subject other than the corresponding work subject cannot access the work directory. Work described in crab
It is a job management system.

According to a thirty-ninth aspect of the present invention for solving the above-mentioned problems, the working subject is in the connected state only during work, and is not in the connected state when not working. 38. The work / job management system according to any one of 38.

The invention according to claim 40, which solves the above-mentioned problem, is characterized in that the front-end application has at least a first work state to a third work state as information on a work state of the work subject for an action set in the job. 40. The database server records at least one of a first action state to a fourth action state as information relating to any one of the above-mentioned and the action state set for the job. The work / job management system according to any one of the above.

The invention according to claim 41, which solves the above-mentioned problem, is characterized in that the front-end application has at least a first work state to a third work state as information relating to the work state of the work subject for the action set in the job. At least one of the first to fourth action states and the time at which the action state was changed as information on the action state set for the job. The work / job management system according to any one of claims 33 to 39, wherein the work / job management system is recorded in a database server.

The invention according to claim 42, which solves the above-mentioned problem, is characterized in that the front-end application has at least a first work state to a third work state as information on the work state of the work subject for the action set in the job. At least one of the first to fourth action states and the time at which the action state was changed as information on the action state set for the job. 4. The method according to claim 3, wherein the time is recorded in a database server, and using the time, a work time for the action with respect to the work subject is calculated.
The work / job management system according to any one of Items 3 to 39.

The invention according to claim 43, which solves the above-mentioned problem, is characterized in that the front-end application has at least a first work state to a third work state as information relating to the work state of the work subject for the action set in the job. At least one of the first to fourth action states and the time at which the action state was changed as information on the action state set for the job. The database server records, using the time, the database server calculates a work time for the action for the work subject,
The work / job management system according to any one of claims 33 to 39, which records the information.

The invention according to claim 44, which solves the above-mentioned problem, is characterized in that the front-end application has at least a first work state to a third work state as information relating to the work state of the work subject for the action set in the job. At least one of the first to fourth action states and the time at which the action state was changed as information on the action state set for the job. The work / job management system according to any one of claims 33 to 39, wherein a work time for the action is calculated by using a time recorded on a database server.

The invention according to claim 45, which solves the above-mentioned problem, is characterized in that the front-end application has at least a first work state to a third work state as information relating to the work state of the work subject for the action set in the job. At least one of the first to fourth action states and the time at which the action state was changed as information on the action state set for the job. The work / job management system according to any one of claims 33 to 39, wherein the work / job management system according to any one of claims 33 to 39, wherein the work time is calculated by the database server using the time and the work time for the action is recorded. is there.

The invention according to claim 46, which solves the above problem, is characterized in that the first action state is recorded after setting an action for a job by a front-end application. A work / job management system according to the present invention.

The invention according to claim 47, which solves the above-mentioned problem, is characterized in that the first work state is obtained from a database server by a front-end application, which acquires information on a storage location of a job in which an action to be worked is set. 46. The work / job management system according to claim 40, wherein the information is recorded after the job directory storing the job and the work directory are directly connected in accordance with the acquired information on the storage destination.

The invention according to claim 48, which solves the above problem, is characterized in that the second work state is recorded after the direct connection is once disconnected by a front-end application. An operation / job management system according to any one of the above.

The invention according to claim 49, which solves the above problem, is characterized in that the third work state is recorded after the front-end application disconnects the direct connection and determines an action in the database server. The work / job management system according to any one of claims 40 to 45, wherein:

The invention according to claim 50, which solves the above-mentioned problem, is characterized in that the first work state obtains information on a storage destination of a job in which an action to be worked is set from a database server by a front-end application. A job directory storing the job in accordance with the obtained information about the storage location and the work directory are recorded after directly connecting, the second work state is recorded after the direct connection is temporarily disconnected by a front-end application, The third working state is:
The job / job management system according to any one of claims 40 to 45, wherein the job / job management system is recorded after the front-end application disconnects the direct connection and determines an action in the database server.

The invention according to claim 51, which solves the above-mentioned problem, is characterized in that the second to fourth action steps are determined according to the work states of the plurality of work subjects. 45. The work / job management system according to any one of 45.

The invention according to claim 52, which solves the above-mentioned problem, is characterized in that, when a work state of at least one work subject is a first work state in a group that performs a work on the action, the action state of the action is a second work state. 52. The work / job management system according to claim 51, wherein the work / job management system is described in a two-action state and a database.

The invention according to claim 53, which solves the above-mentioned problem, is characterized in that, when the work state of all the working subjects is the third work state, the action state of the action is the fourth work state among the groups performing the work on the action. 6. An action state and a description in a database.
53. The work / job management system according to any one of 1 to 52.

According to a fifty-fourth aspect of the present invention for solving the above-mentioned problem, at least one of the working groups of the group performing the work for the action is the second working state.
The work according to any one of claims 51 to 53, wherein when there is no work subject whose work state is the first work state, the action state of the action is described in the database as the third action state. -It is a job management system.

The invention according to claim 55, which solves the above-mentioned problem, is characterized in that, when an instruction regarding any one of the first to third working states is received, the connection or disconnection processing is performed by the front-end application. Prior to the authentication process, a process of inquiring the database server of the work state of the work subject and a process of determining whether or not the instruction can be received based on the result of the query are performed as authentication processes. 41. The method according to claim 40, wherein the connection or disconnection processing is performed if it is determined that the instruction is not acceptable in the determination processing. ~ 5
0.

The invention according to claim 56, which solves the above-mentioned problem, is characterized in that, when receiving an instruction regarding any one of the first to third working states, the file server:
Prior to the connection or disconnection process, as an authentication process, a process of inquiring the work status of the work subject to the database server and a process of determining whether or not the instruction can be accepted based on the query result are performed. The connection or disconnection processing is performed if it is determined that the instruction is acceptable in the processing to be performed, and the notification that the instruction is not accepted is performed if it is determined that the instruction is not acceptable in the determination processing. The work / job management system according to any one of claims 40 to 50.

According to a fifty-seventh aspect of the present invention, in the authentication processing, the instruction of the first work state is accepted depending on whether an action to be worked exists or whether the action is in the second work state. It is determined whether or not the instruction is possible. The instruction for the second operation state is determined based on whether or not the operation state is the first operation state. Whether the instruction for the third operation state is the first operation state or the second operation state. 57. The work / job management system according to claim 55, wherein whether or not the job can be accepted is determined based on whether or not the job is accepted.

In the present invention, a logical connection means that an arbitrary directory (connection point) existing on the client terminal is related to another directory (connection destination directory) to which the connection is made by software. In addition, by accessing the connection point, software access to data under the corresponding connection destination directory is enabled at the user level or the application level, or the state thereof.

In the present invention, the direct connection means that a logical connection is made with the job directory of the work target as a connection destination, or the state of the logical connection, and the directory of the upper hierarchy including the target job directory is logically connected with the connection destination. This is different from a state in which a temporary connection is made and the job directory can be accessed via the upper-level directory.

[0080]

Embodiments of the present invention will be described below in detail.

The job management system and the job management system of the present invention can be preferably applied to a case where work is performed while accessing data in a computer environment connected via a network. For example, the printing industry such as DTP and prepress, the medical industry that manages and operates X-ray images,
It is applicable in the photo and image processing industries such as online publishing, electronic publishing, and postcard creation. (Inventions as set forth in claims 1 to 17)
The work management system according to the present invention (hereinafter abbreviated as the work management system of the present invention as necessary) will be described in detail.

FIGS. 1 and 2 are explanatory diagrams for explaining a first embodiment of the work management system of the present invention.

In this embodiment, work management is performed for each client user, and work directories are provided corresponding to the client user who is the work subject and the job directory to be worked.

1 and 2, reference numeral 10 denotes a client terminal, 11 denotes a front-end application installed on the client terminal 10, and 1
2a and 12b are client users who operate the client terminal 10. Reference numeral 20 denotes a recording medium or a file server, which logically stores job directories 21a, 21b, and 21c storing job data.
Reference numerals a and 30b denote work directories corresponding to the client user 12a and the job directory 21a, which are the work subjects, and the client user 12b and the job directory 21b, respectively. Reference numeral 40 denotes a database server in which information about the work subject is recorded.

As the client terminal 10, an ordinary personal computer (hardware resource) or the like can be used.

The front-end application 11
A work directory 30a corresponding to the work subject when the program installed in the client terminal 10 receives information from the work subject that specifies an action set for the job to be worked on and the content of the operation for the action. , 30b and the job directory 21
a, 21b, and 21c are logically directly connected. After making this direct connection, any external application can access the job directory regardless of the type of external application. As described above, since the front-end application is independent of the external application, work management independent of the external application can be realized.

Further, the front-end application 1
1 receives, from the work subject, information specifying the action set for the job to be worked on and the content of the operation for the action, the database server 40 transmits the action of the work subject to the action set for the job. Record information about working conditions.

As the recording medium or the file server 20, a readable / writable recording medium or a file server having such a recording medium can be used. At this time, the recording medium may be HD (hard disk), FD (floppy disk), MO (magneto-optical disk), CD-RO
M or the like can be used.

The job directories 21a, 21b, 21
“c” stores a file related to a series of related jobs, and is logically stored in the recording medium or the file server 20. Each job directory 21a, 21b, or 21c may be logically stored in one recording medium, or may be distributed or redundantly stored in a plurality of recording media.

The work directories 30a and 30b are directories stored in a recording medium such as a hard disk in the client terminal 10, and are connection points provided corresponding to a client user who is a work subject. Such connection points are unique to the work subject, and are set so that work subjects other than the corresponding work subject cannot access.

In order to prevent the work directories 30a and 30b from being accessed by anyone other than the corresponding work subject, a method of performing authentication for access to the work directory, for example, a password is issued for each work subject and the work is performed using the password An OS (operating system) in which access to the directory is permitted, and directory write / read permissions can be separately set for the owner of the directory, the group to which the owner belongs, and other users ) Can be used.

By setting such a work directory so that only the corresponding work subject can access the work directory, the connection status of the work directory matches the connection status of the corresponding work subject. The connection state can be managed.

The front end application 11
Recording medium or file server 20 (each job directory 21a, 21b, 21c) and client terminal 10
(Work directories 30a, 30b) are LAN, WA
N or a direct logical connection using a network such as the Internet, or the CP of the client terminal 10.
In an environment where the control unit such as U controls the recording medium or the file server 20 (each job directory 21a, 21b, 21c), the two may be logically directly connected.

The database server 40 is at least constituted by a database capable of recording data such as information on the work subject at any time. Examples of such a database include an HD (hard disk), an FD (floppy disk), A recording medium such as an MO (magneto-optical disk) or a CD-ROM can be used, but is not particularly limited.

In the present invention, the database server 4
Since the table structure of the 0 database is important, the structure will be described here.

FIG. 3 is a diagram showing a preferred example of the table structure of the database server 40. As shown in FIG.

The table of the database server 40 is a job table in which a job ID, a job name, and a storage location ID are associated. An action table in which an action ID, a job ID, and an action name are associated. A storage location table in which storage location IDs and storage location data are associated. Work subject I
It is constituted at least by a work state table in which D, an action ID, a work state for the action, and a change time of the work state are associated with each other.

By registering the job or the work subject to be managed, the job I corresponding to the job 1: 1
D, a work subject ID corresponding to 1: 1 is issued to each work subject.

In the job table, a job ID and a storage destination ID are recorded in association with each job.

An action can be set for each job. When an action is set, an ID corresponding to 1: 1 is issued and recorded in the action table in association with the action name and the ID of the job to be set. Is done.

In the storage location table, the storage location of the job to be managed is recorded together with the storage location ID.
When starting the connection, the front-end application 11 can acquire the storage location of the job from the job table and the storage location table.

In the work status table, a work status associated with a work subject ID and an action ID for managing a work status in accordance with an instruction from the front end application 11 is appropriately recorded. As such a work state, at least one of the first to third work states is recorded.

In the present invention, the first work state indicates that the work subject is performing work, and the second work state indicates that the work subject is interrupting work. The third work state indicates that the work subject has completed the work. In FIG. 3, the first work state is “work start”, the second work state is “interrupted”, and the third work state is “interrupted”.
The work state is expressed as “end”, and in this specification, the first work state is described as “work start”, the second work state is “interrupted”, and the third work state is “finished” as necessary. I do.

With such a table structure, the work subject can perform the work by instructing the front-end application 11 only the information of the action to be worked on and the operation content for the action, and the operation content for the action is also stored in the database. It can be managed simply by accessing the server 40.

Further, as tables of the database server 40, a work subject ID, an action ID, a work state,
A work state history table is provided that associates the time at which the work state was changed, the work time of the work subject for the action is calculated using the change time, and the calculation result is stored in the work state table as the work subject ID and the action ID. It is preferable to record the information in association with the operation time because the operation time of each action of the operation subject can be managed.

Next, the processing flow in the first embodiment of the work management system of the present invention will be described with reference to FIGS.

First, the client user 12a, who is the work subject, performs the work for the action "input image of project A". As the information for specifying the operation content for the action, "input of image of project A" is input as "work start of work subject".

The front-end application 11, which has received the information “input of project A” and “start of work” as information for specifying the action set for the job to be processed and the operation content for the action, In accordance with the processing flow shown in FIG. 4, a process for acquiring information about the storage location of the job “Project A” in which “image input of project A”, which is the action to be performed, is set from the database shown in FIG. Then, the job directory 21a storing the job and the work directory 30a are logically directly connected as shown in FIG. 1 according to the obtained information on the storage destination (S2).

In this manner, the client user 12
After the environment in which the work can be performed by logically establishing a direct connection between the work directory 30a and the job directory 21a that can be used only by the a, the front-end application 11 executes the action set for the job. To cause the database server 40 to record “work start” indicating the first work state as information on the work state of the work subject in question (S)
3).

As described above, when the work directory 30a and the job directory 21a which can be used only by the client user 12a are logically directly connected to each other, the first work state is recorded in the database server 40. When one work state is recorded, the environment is such that the work can be performed reliably, and the reliability of the system that the “first work state” means that the work is being performed is increased.

After the connection state as shown in FIG. 1 is established, if the client user 12a temporarily suspends the work of “inputting the image of the project A”, the client user 12a performs the action of “inputting the image of the project A”. In order to suspend the work, the “input image of project A” is sent to the front-end application 11 as information specifying the action set for the job to be worked and the operation content for the action. Interrupted ".

The front-end application 11 that has received the information that “project A image input” is “interrupted” as information for specifying the action set for the job to be worked on and the operation content for the action
Disconnects the logically direct connection between the work directory 30a and the job directory 21a that can be used only by the client user 12a according to the processing flow shown in FIG. 5 (S4).

Thus, the client user 12
a, the work directory 30a and the job directory 21a, which can be used only by a, are not logically and directly connected to each other, so that the work cannot be performed. The database server 40 sets “interruption” indicating the second work state as information on the work state of the work subject for the action set in the job.
(S5).

As described above, if the logical connection between the work directory 30a and the job directory 21a which can be used only by the client user 12a is temporarily disconnected, the second work state is recorded in the database server 40. When the second work state is recorded, the work is not confirmed even though there is an environment where the work cannot be performed reliably. Therefore, the reliability of the system that the “second work state” means interruption is required. Get higher.

After the connection state as shown in FIG. 1 is established, when the client user 12a completes the above-mentioned operation of “input of image of project A”, the client user 12a calls “input of image of project A”. In order to end the work for the action, the front-end application 11 sets “Project A image input” to “Work” as information for specifying the action set for the job to be worked on and the operation content for the action. End of subject ".

The front-end application 11 that has received the information that “input image of project A” is “finished” as information for specifying the action set for the job to be processed and the operation content for the action
Performs a process of disconnecting the logically direct connection between the work directory 30a and the job directory 21a that can be used only by the client user 12a as shown in FIG. 2 in accordance with the process flow shown in FIG. 6 (S6). A process for determining the main task is performed (S7).

The processing for determining the work of the work subject is
Finish working to handle the corresponding action,
This is a process that makes it impossible to restart such work.

Thus, the client user 12
After disconnecting the logical direct connection between the work directory 30a and the job directory 21a that can be used only by a and confirming the work, the front-end application 11 sends the work subject to the action set for the job. The database server 40 records "end" indicating the third work state as information on the work state (S5).

In this way, the logical connection between the work directory 30a and the job directory 21a that can be used only by the client user 12a is logically directly disconnected, and after the work is determined, the third work state is changed to the database server 40. When the third work state is recorded, the work is determined even in an environment where the work cannot be performed reliably, so the “third work state” is recorded.
Means the end of the system.

Similarly, the work state of the client user 12b is "interrupted" or "finished" in the state of FIG. 1, and is "work started" in the state of FIG.

As described above, the front-end application 11 is executed by the client user who is the main work (FIG. 1).
2a and 12b in FIG. 2) If it is possible to make a logical direct connection of the corresponding work directory only when the work is in progress, the connection state of the work main body is substantially managed, whereby the work main body is managed. Work status can be managed.

The front-end application causes the database server to record at least one of the first to third work states as information on the work state of the work subject for the action set for the job. Therefore, the work state can be grasped in three states.

Also, the front end application 1
1 records the time when the work state is changed in the database simultaneously or sequentially with the recording of each work state (S3, S5, S8), so that the time when the work state is changed can be managed. Becomes

If the database server calculates and records the work time for the action with respect to the work subject using the time at which the work state was changed, the work subject required work for each action. Time can be easily managed.

In the above aspect, when an instruction regarding the first to third work states is received, the database server performs an authentication process by the front end application 11 prior to the connection or disconnection process (S1, S4, S6). At step 40, a process is performed to inquire about the current work state of the work subject, and a process is performed to determine whether such an instruction can be accepted. If the instruction can be accepted, the next process (S1, S
4, S6), and if a process for notifying that such an instruction is not accepted is performed if it cannot be accepted, an instruction relating to the second work state or the third work state can be issued only from the work entity involved in the work. It can be accepted and work management can be performed reliably.

In the authentication processing as described above, the instruction of the first work state is that the action to be worked exists or the second work state
Determine whether or not it can be accepted depending on whether or not it is in the work state,
It is determined whether or not the instruction for the second work state is acceptable based on whether the state is the first work state, and the instruction for the third work state is acceptable depending on whether the state is the first work state or the second work state. It is determined whether or not.

Further, the front end application 1
The first authentication process may be performed by a file server.

Also, in the above-mentioned embodiment, if the work subject ID issued to correspond to the work subject in a one-to-one correspondence is issued to the combination of the work subject and the client terminal in a one-to-one correspondence. In addition, the same work subject can be managed separately for each client terminal.

FIG. 7 and FIG. 8 are explanatory diagrams for explaining a second embodiment of the work management system of the present invention. 7 and 8, the same reference numerals as in FIG. 1 denote the same components, and a detailed description thereof will be omitted.

In the present embodiment, since the work subject is the front-end application, the work directory provided for each client user in the above embodiment corresponds to the front-end application (the work directory for the front-end application 11a). Directory 30a, front end application 11
b is different from the above embodiment in that a work directory 30b) is provided for b.

In the present embodiment, the work subject is the front-end application. However, information about the work status of the work subject for the action set for the job is actually input to each of the front-end applications 11a and 11b. What performs the action for the action may be a client user or a client external application.

For example, as shown in FIGS. 7 and 8, the action set for the job stored in the job directories 21a and 21b to which the work directories 30a and 30b corresponding to the front-end applications 11a and 11b are actually connected. Even if the client user performs the operation, the work state recorded in the database server 40 is “start work” in the state of FIG. 7 and the front end application 11a which is the work subject in the state of FIG. 11b is "work start".

As described above, when a work directory corresponding to the front-end application is provided as a work subject and managed, the work state of each front-end application can be managed irrespective of the actual work.

FIGS. 9 and 10 are explanatory views for explaining a third embodiment of the work management system according to the present invention. FIG.
In FIG. 10 and FIG. 10, the portions denoted by the same reference numerals as those in FIG. 1 indicate the same configuration, and detailed description thereof will be omitted.

In the present embodiment, since the work subject is a client external application, the work directory provided for each client user in the first mode corresponds to each client external application (the client external application 13a On the other hand, this embodiment is different from the above embodiment in that a work directory 30a and a work directory 30b) are provided for the client external application 13b.

In the present embodiment, the work subject is a client external application. However, work for a reaction in which information on the work status of the work subject for the action set for the job is actually input to each front-end application 11. May be performed by the client external application itself, which is the work subject, or by the client user.

For example, as shown in FIG. 9 and FIG. 10, the actions actually set for the jobs stored in the job directories 21a and 21b to which the work directories 30a and 30b corresponding to the client external applications 13a and 13b are connected. Is performed by the client user, the work state recorded in the database server 40 is “start work” in the state of FIG.
In the state of FIG. 10, the client external application 1
3b is "work start".

As described above, when a work directory corresponding to a client external application is set as a work entity and managed, a work state of each client external application can be managed irrespective of the actual work performed.

FIG. 11 and FIG. 12 are explanatory diagrams for explaining a fourth embodiment of the work management system of the present invention. 11 and 12, the same reference numerals as those in FIG. 1 denote the same components, and a detailed description thereof will be omitted.

In the present embodiment, since the work subject is the client terminal, the work directory provided for each client user in the first mode corresponds to each client terminal (the work directory for the client terminal 10a). Directory 30a, client terminal 10b
Is different from the above embodiment in that a work directory 30b) is provided.

[0141] In this embodiment, although the working entity is a client terminal, used to input actual information about the working status of the working entity for action set to those the job to the front-end application 11, It can be a client external application or a client user.

For example, as shown in FIGS. 11 and 12, the actions set in the jobs stored in the job directories 21a and 21b to which the work directories 30a and 30b corresponding to the client terminals 10a and 10b are actually connected are described. Even if what is performed is a client user, the work state recorded in the database server 40 is the client terminal 10a which is the work subject in the state of FIG.
Is "work started", and in the state of FIG. 12, the client terminal 10b is "work started".

As described above, when a corresponding work directory is provided and managed with the client terminal as the work subject,
It is possible to manage the work state of each client terminal regardless of what performs the actual work.

Next, the job management system of the present invention will be described in detail. (The invention according to claims 18 to 32) The job management system of the present invention will be described. This embodiment can be explained based on FIGS. 1, 2, 4 to 6, 13 and 14 which describe the first embodiment of the work management system of the present invention.

The job management system of the present invention embodies the technical idea of focusing on the work state of the action set for the job, unlike the technical idea of the work management system of the present invention which focuses on the work state of the worker. It does not matter who works. In the present embodiment, a case where the work subject is a client user will be described as an example, but the work subject is not limited to this, and may be a front-end application or a client external application. Or a client terminal.

Since the configuration shown in FIGS. 1 and 2 has already been described in the first embodiment of the work management system of the present invention, the description of the hardware other than the database server 40 will be omitted.

In the job management system of the present invention, a database server 40 having a table structure as shown in FIG. 13 is used instead of the table structure of the database server 40 used in the work management system.

In FIG. 13, the description of the same parts as in FIG. 3 is omitted.

The action status table shown in FIG. 13 has an action ID and a job I of the job in which the action is set.
D, the action state, and the change time of the action state are recorded in association with each other.

In the action status table, when an action is set, an action ID is issued and recorded in association with the job ID to be set and the action status.

In the action state table, an action ID for managing a job in an action state in accordance with an instruction from the front end application 11 and an action state associated with the job ID of the job in which the action is set are displayed together with the change of the action state. Recorded as appropriate. As such an action state, at least one of the first to fourth action states is recorded.

In the present invention, the first action state indicates that an action has been set for a job, and the second action state indicates that an action is being performed. The third action state indicates that the action has been suspended, and the fourth action state indicates that the action has been completed. In FIG. 13, the first action state is expressed as "entry", the second action state is expressed as "work start", the third action state is expressed as "interrupted", and the fourth action state is expressed as "end". In the specification, the first action state is “entry”, the second action state is “work start”,
The third action state is described as “interrupted”, and the fourth action state is described as “finished”.

Next, an example of the processing flow in the job management system of the present invention will be described below.

First, a job manager who sets an action for a job inputs “image input” (action) to “project A” (job) as an “entry” (step) to the database server 40.

The database server 40, which has received the information “input image” and “entry” of “project A” as information for specifying the action set for the job to be operated and the operation content for the action, Then, a process for setting an action for is performed (S9).

Thus, after the action is set,
The front-end application 11 causes the database server 40 to record “entry” as the first action state as information on the action state set for the job (S10).

As described above, if the first action state is recorded in the database server 40 after the action is definitely set for the job, the job is surely recorded when the first action state is recorded. Since the action has been set for
Consistency that "action state" means that an action has been set can be improved.

Next, the client user 12a operates the front-end application 11
Then, "input of image of project A" is input as "start of work of action" as information for specifying the action set for the job to be worked and the operation content for the action.

The front-end application 11, which has received the information "input of project A" and "start work" as information for specifying the action set for the job to be worked and the operation content for the action, According to the processing flow shown in FIG. 4, a process for acquiring information on the storage location of the job "Project A" in which the action "input image of project A" is set from the database shown in FIG. Then, the job directory 21a storing the job and the work directory 30a are logically directly connected as shown in FIG. 1 according to the obtained information on the storage destination (S2).

In this way, the client user 12
After establishing a logical direct connection between the work directory 30a and the job directory 21a that can be used only by the a, the front-end application 11 indicates the second action status as information on the action status set for the job. “Start work” is recorded in the database server 40 (S3).

As described above, if the work directory 30a and the job directory 21a that can be used only by the client user 12a are logically directly connected to each other, and then the second action state is recorded in the database server 40, When the two-action state is recorded, the environment in which the work can be reliably performed is provided, and the reliability of the system that the “second action state” means that the work is being performed is increased.

After the connection state as shown in FIG. 1 has been established, if the client user 12a temporarily suspends the work of “inputting the image of project A”, the client user 12a performs the action of “inputting the image of project A”. In order to interrupt the operation, “input image of project A” is input to the front-end application 11 as “interruption of action” as information on the action status set for the job.

The front-end application 11 that has received the information that "the image input of the project A" is "interrupted" as information for specifying the action set for the job to be operated and the operation content for the action
Performs a process of temporarily disconnecting the logical direct connection between the work directory 30a and the job directory 21a that can be used only by the client user 12a as shown in FIG. 2 according to the process flow shown in FIG. 5 (S4).

Thus, the client user 12
After the logical direct connection between the work directory 30a and the job directory 21a that can be used only by a is temporarily disconnected, the front-end application 11 indicates the third action status as information on the action status set for the job. “Interruption” is recorded in the database server 40 (S5).

As described above, after the logical direct connection between the work directory 30a and the job directory 21a that can be used only by the client user 12a is temporarily disconnected, the second work state is recorded in the database server 40. When the third action state is recorded, the action is not confirmed even though the environment cannot perform the work reliably, so the reliability of the system that the “third action state” means interruption is Get higher.

After the connection state as shown in FIG. 1 is established, when the client user 12a completes the above-mentioned “input of image of project A”, the client user 12a calls “input of image of project A”. In order to end the work for the action, “input an image of project A” is input to the front end application 11 as “end of action” as information on the action state set for the job.

The front-end application 11 that has received the information that “input image of project A” is “finished” as information for specifying the action set for the job to be processed and the operation content for the action
Performs a process of disconnecting the logically direct connection between the work directory 30a and the job directory 21a, which can be used only by the client user 12a, as shown in FIG. 2 according to the process flow shown in FIG. 6 (S6). A process for determining is performed (S7).

The process of deciding an action is a process of ending the work for the purpose of processing the action and making it impossible to resume the work for the action.

Thus, the client user 12
After logically disconnecting the direct connection between the work directory 30a and the job directory 21a that can be used only by a, and determining the action, the front-end application 11 sends information on the action status set for the job. “End” indicating the fourth action state is recorded in the database server 40 (S5).

As described above, the direct connection between the work directory 30a and the job directory 21a that can be used only by the client user 12a is logically disconnected, and after the action is determined, the fourth action state is changed to the database server 40. When the fourth action state is recorded, the work is determined even in an environment where the work cannot be performed reliably, so the “fourth action state” means the end. The system is more reliable.

As described above, the front-end application 11 transmits the corresponding job directory (21 in FIG. 1) only when the work state of the action is “work start”.
a, if the logical direct connection 21b) in FIG. 2 can be performed, the work state of the work subject can be managed by substantially managing the connection state of the work subject.

Further, since the front end application 11 records at least one of the first action state to the fourth action state in the database server 40 as information on the action state set for the job, the four state The work state can be grasped by using.

Also, the front end application 1
1 records each work state (S3, S5, S8) and, at the same time, records the time at which the work state was changed in the database, so that the time at which the work state was changed can be managed.

If the database server calculates and records the work time for the action with respect to the work subject using the time when the work state is changed, the time required for the work for each action can be easily managed. can do.

In the above manner, the file server that controls the recording medium that logically stores the job directory 21
It is preferable that authentication is performed when a logical direct connection is made by the front-end application 11, and thus such authentication processing will be described below.

The file server that has received the connection permission request from the front-end application 11 accesses the database according to the processing flow shown in FIG. 15 and registers the action and the job to be requested. A confirmation is made (S11), and it is determined whether or not the requested action can be entered (S12).
If it is determined in step 13 that entry is possible, it is determined whether or not a job corresponding to the action exists (S13). If it is determined in S14 that a job corresponding to the action exists, the job directory is checked out (accessible setting) (S14). On the other hand, entry is not possible in S13,
If it is determined in step 14 that a job corresponding to the action exists, information indicating that the connection request is not permitted is sent to the front-end application 11.

When the job is checked out by the file server as described above, for the job in which the fourth action status is recorded, the file server checks in the job directory (inaccessible setting). I do.

In this way, the front-end application 11 obtains information on the storage location of the job in which the action to be performed is set from the database, and then requests the file server to permit connection, and If the direct connection is performed only when permission is given by the file server, a highly reliable action management system can be obtained.

In the above aspect, when an instruction regarding the first to fourth action states is received,
Setting of the action, the connection or disconnection process (S1,
Prior to S4, S6, and S9), as the authentication processing by the front-end application 11, the database server 40 performs processing for inquiring the current work state of the work subject, and determines whether or not such an instruction can be accepted. Perform the next process (S1, S4, S6,
If S9) is performed and a process of notifying that the instruction is not accepted if the instruction cannot be accepted is performed, an instruction that causes the second action state, the third action state, or the fourth action state is processed by the action of the action. The job can be received only from the work subject involved in the job, and job management in which an action is set can be reliably performed.

In the authentication processing as described above, it is determined whether or not the instruction in the first action state is acceptable based on whether or not the job to be set exists, and the instruction in the second action state is in the first action state. It is determined whether or not it can be accepted based on whether or not there is, and the instruction of the third action state is determined whether or not it can be accepted depending on whether or not it is the second action state.
It is determined whether the instruction of the action state can be accepted based on whether the instruction is the second action state or the third action state.

In addition, the front end application 1
The first authentication process may be performed by a file server.

(Invention of Claims 33 to 57) Next, the work / job management system of the present invention will be described.

According to the work / job management system of the present invention, in the above-described work management system and job management system of the present invention, the front-end application sets information on the work state of the work subject for the action set in the job and the setting in the job. Since the information on the performed action status is recorded in the database server, the description of the same hardware components as those of the work management system and the job management system will be omitted.

As the table structure of the database server 40 in the work / job management system of the present invention, the structure shown in FIG. 16 can be used. Such a table structure is basically the same as the table structure of FIG.
Since the table structure described above is combined, the description thereof is omitted.

Next, an example of the processing flow of the work / job management system of the present invention will be described below.

First, a job manager who sets an action for a job inputs “image input” (action) to “project A” (job) as an “entry” (operation content) to the database server 40.

The database server 40, which has received the information that “image input” of “project A” is “entry” as information for specifying the action set for the job to be operated and the operation content for the action, Then, a process for setting an action for is performed (S9).

As described above, after the action is set,
The front end application 11 causes the database server 40 to record an “entry” indicating the first action state as information on the action state set for the job (S10).

As described above, if the first action state is recorded in the database server 40 after the action is definitely set for the job, when the first action state is recorded, the job is surely recorded. Since the action has been set for
Consistency that "action state" means that an action has been set can be improved.

Next, the client user 12a operates the front-end application 11 in order to work on the action "input image of project A".
Then, "input of image of project A" is input as "work and action work start" as information for specifying the action set for the job to be worked and the operation content for the action.

The front-end application 11, which has received the information of “input of image of project A” as “start of work”, as information for specifying the action set for the job to be worked and the operation content for the action, According to the processing flow shown in FIG. 4, a process for acquiring information on the storage location of the job "Project A" in which the action "input image of project A" is set from the database shown in FIG. Then, the job directory 21a storing the job and the work directory 30a are logically directly connected as shown in FIG. 1 according to the obtained information on the storage destination (S2).

In this manner, the client user 12
After a logical direct connection is established between the work directory 30a and the job directory 21a that can be used only by the a, the front-end application 11 obtains information on the work state of the work subject for the action set for the job and the As the information on the action status set for the job, “work start” indicating the first work status and “work start” indicating the second action status are recorded in the database server 40 (S3).

As described above, if the work directory 30a and the job directory 21a which can be used only by the client user 12a are logically directly connected to each other and then the second action state is recorded in the database server 40, When the two-action state is recorded, the environment is such that the work can be performed reliably, so that the “first work state” is the work subject is working and the “second action state” is the work on the action. This means that the reliability of the system is increased.

After the connection state as shown in FIG. 1 has been established, if the client user 12a temporarily suspends the work of “inputting the image of project A”, the client user 12a performs the action of “inputting the image of project A”. In order to interrupt the operation, “input of image of project A” is input to the front end application 11 as “information of the action state set for the job” as “interruption of operation and action”.

The front-end application 11 that has received the information that “project A image input” is “interrupted” as information for specifying the action set for the job to be worked on and the operation content for the action
Performs a process of temporarily disconnecting the logical direct connection between the work directory 30a and the job directory 21a that can be used only by the client user 12a as shown in FIG. 2 according to the process flow shown in FIG. 5 (S4).

In this way, the client user 12
After the logical direct connection between the work directory 30a and the job directory 21a, which can be used only by a, is temporarily disconnected, the front-end application 11 returns information on the work state of the work subject to the action set for the job and As the information on the action status set for the job, “interruption” indicating the second work status and “interruption” indicating the third action status are recorded in the database server 40 (S5).

As described above, if the direct connection between the work directory 30a and the job directory 21a that can be used only by the client user 12a is temporarily disconnected, the second work state is recorded in the database server 40. When the third action state is recorded, the action is not determined even though the environment is such that the work cannot be performed reliably, so the “second work state”
Increases the reliability of the system that the interruption of the work by the operator and the “third action state” mean the interruption of the operation for the action.

After the connection state as shown in FIG. 1 is established, when the client user 12a completes the above-mentioned “input of image of project A”, the client user 12a calls “input of image of project A”. In order to end the work for the action, the user inputs “image input of project A” as “end of work and action” to the front-end application 11 as information on the action state set for the job.

The front-end application 11 that has received the information that “image input of project A” is “finished” as information for specifying the action set for the job to be worked on and the content of the operation for the action
Performs a process of disconnecting the logically direct connection between the work directory 30a and the job directory 21a that can be used only by the client user 12a as shown in FIG. 2 according to the process flow shown in FIG. 6 (S6). A process for determining the action is performed (S7).

Thus, the client user 12
a, the direct connection between the work directory 30a and the job directory 21a that can be used only by the user is cut off, and after the work and the action are determined, the front-end application 11 As the information on the work state of the work subject and the information on the action state set for the job, “end” indicating the third work state and “end” indicating the fourth action state are recorded in the database server 40 (S5).

As described above, the logical connection between the work directory 30a and the job directory 21a that can be used only by the client user 12a is logically disconnected, and after the work and action are determined, the fourth action state is stored in the database. If you make the server 40 record,
When the fourth action state is recorded, the work is determined even in an environment in which the work cannot be performed reliably, so that the “third work state” indicates that the work subject has completed the work,
The reliability of the system that the “fourth action state” means the end of the work for the action is increased.

As described above, the front-end application 11 transmits the corresponding job directory (21 in FIG. 1) only when the work state of the action is “work start”.
a, if the logical direct connection 21b) in FIG. 2 can be performed, the work state of the work subject can be managed by substantially managing the connection state of the work subject.

The front-end application 11 records at least one of the first action state to the fourth action state in the database server 40 as information relating to the action state set for the job. The work state can be grasped by using.

Also, the front end application 1
1 records each work state (S3, S5, S8) and, at the same time, records the time at which the work state was changed in the database, so that the time at which the work state was changed can be managed.

If the database server calculates and records the work time for the action for the work subject using the time at which the work state was changed, the time required for the work for each action can be easily managed. can do.

In the above manner, the file server that controls the recording medium that logically stores the job directory 21
It is preferable that authentication is performed when a logical direct connection is made by the front-end application 11, and thus such authentication processing will be described below.

The file server that has received the connection permission request by the front-end application 11 accesses the database according to the processing flow shown in FIG. 15 and registers the target action and job. A confirmation is made (S11), and it is determined whether or not the requested action can be entered (S12).
If it is determined in step 13 that entry is possible, it is determined whether or not a job corresponding to the action exists (S13). If it is determined in S14 that a job corresponding to the action exists, the job directory is checked out (accessible setting) (S14). On the other hand, entry is not possible in S13, S
If it is determined in step 14 that a job corresponding to the action exists, information indicating that the connection request is not permitted is sent to the front-end application 11.

When the job is checked out by the file server as described above, for the job in which the fourth action status is recorded, the file server checks in the job directory (inaccessible setting). I do.

[0209] In this way, the front-end application 11 obtains information about the storage location of the job in which the action to be performed is set from the database, and then requests the file server for connection permission. If the direct connection is performed only when permission is given by the file server, a highly reliable action management system can be obtained.

The above-described work management system and job management system of the present invention are preferably used when a single work subject performs work on an action set for a job, but the work / job management system of the present invention is preferably used. Is
As described in the above-described embodiment, the case where one action is performed by one work subject has been described. However, the work subject may be a plurality of client users, a plurality of front-end applications, a plurality of client external applications, and a plurality of client terminals. Alternatively, the present invention can also be used when a group is formed from two or more work subjects selected from a client user, a front-end application, a client external application, and a client terminal, and work is performed on an action set for a job in the group. .

In the present invention, when a group is composed of a plurality of work subjects and work is performed for one action by the group, the work subject is any one of a client user, a front-end application, a client external application, and a client terminal. However, since the operation of the system is basically the same, the work / job management system of the present invention will be described below by taking as an example a case where a plurality of work subjects constituting a group are a plurality of client users. However, the work is performed by client users, front-end applications,
Any of a client external application and a client terminal may be used.

FIG. 17 is a diagram showing a connection state in a case where there is one client user who is a work subject for an action. FIG. 18 is a diagram showing a connection state in the case where one client user is a work subject for an action. FIG. 19 is a state transition diagram showing the correspondence between the work state of the work subject and the action state of the job in the work / job management system of the present invention.

In FIGS. 17 and 18, it is assumed that the job 21a has only one action (hereinafter, also referred to as action A).

In the state shown in FIG. 17, since only the client user 12a works on the action A, the action state of the action A is changed together with the change of the work state of the client user 12a who is the work subject.

However, when the client user 12b also starts work as shown in FIG. 18 in a state where the action state of the action A has not been determined, the client users 12a and 12b, who are the work subjects, perform the action A Is working in a group. In this case, the action state of action A is determined according to a combination of the work states of the client users 12a and 12b.

For example, in FIG. 18, since the job directory 21a is connected to the client users 12a and 12b,
Since d is determined as “work start” for the action A set for the job stored in the job directory 21a, the action state of the action A is recorded in the database as “work start”.

As described above, according to the job management system of the present invention, the group corresponding to the action set for the job to be managed (the client user 12a in FIG. 18)
And 12b), when the work state of at least one client user who is the work subject is “work start”, the action state of the action set for the job is determined to be “work start”.

[0218] In the group that performs the work for the action, the work state of at least one work subject is the first.
At the time of the work state (work start), the action state of the action is described in the database as the second action state (work start), and among the groups that perform work on the action, the work states of all work subjects are the third work state When the state is (end), the action state of the action is described as a fourth action state (end) in the database, and the work state of at least one work subject in the group that performs work on the action is the second work state ( When there is no work subject whose work state is the first work state (work start) and the work state is the first work state (work start), the action state of the action is described in the database as the third action state (pause).

As shown in FIG. 19, the correspondence between the work state and the action state of each work subject in consideration of the group work is established. When the action status of the job is “interrupted”, it indicates that the work status of the work subject can be either “interrupted” or “finished”, and the action status of the job is “work started”. Occasionally, the work status of the worker is "interrupted",
It indicates that the status of the job can be either "start" or "end". When the action status of the job is "end", it indicates that the work status of the work subject can take the "end" status. ing.

In FIG. 19, in the work state or the action state in the top row, the operation contents described in the leftmost column can be accepted. Alternatively, "●" is provided in the field indicating the action status. For example, when "work start" is input as information for specifying the operation content, the action state when such input is accepted is "entry" or "interrupt", and the work state is "interrupt" or "end" or This indicates that the work state has not yet been determined.

As described above, if the system controls the work state of the work subject in association with the action state of the job, even when a plurality of work subjects work on one action, both the work subject and the action can be used. Can be managed mainly by

[Brief description of the drawings]

FIG. 1 is an explanatory diagram illustrating a first embodiment of a work management system according to the present invention;

FIG. 2 is an explanatory diagram illustrating a first embodiment of the work management system of the present invention.

FIG. 3 is a diagram showing an example of a table structure of a database server according to the present invention.

FIG. 4 is a diagram showing an example of a processing flow of a front-end application of the present invention.

FIG. 5 is a diagram showing another example of the processing flow of the front-end application of the present invention.

FIG. 6 is a diagram showing another example of the processing flow of the front-end application of the present invention.

FIG. 7 is an explanatory diagram for explaining a second embodiment of the work management system of the present invention.

FIG. 8 is an explanatory diagram illustrating a second embodiment of the work management system of the present invention.

FIG. 9 is an explanatory diagram for explaining a third embodiment of the work management system of the present invention.

FIG. 10 is an explanatory diagram for explaining a third embodiment of the work management system of the present invention.

FIG. 11 is an explanatory diagram for explaining a fourth embodiment of the work management system of the present invention.

FIG. 12 is an explanatory diagram illustrating a fourth embodiment of the work management system of the present invention.

FIG. 13 is a diagram showing another example of the table structure of the database server of the present invention.

FIG. 14 is a diagram showing another example of the processing flow of the front-end application of the present invention.

FIG. 15 is a diagram showing another example of the processing flow by the file server of the present invention.

FIG. 16 is a diagram showing another example of the table structure of the database server of the present invention.

FIG. 17 is a diagram illustrating a connection state in a case where there is one client user who is a work subject for an action

FIG. 18 is a diagram showing a connection state in the case where there is one client user who is a work subject for an action.

FIG. 19 is a state transition diagram showing a correspondence relationship between a work state of a work subject and an action state of a job in the work / job management system of the present invention.

FIG. 20 is a diagram for explaining a conventional data access method in an in-house LAN or the like.

Claims (57)

[Claims] 1. A recording medium or a file server storing one or more job directories storing files related to jobs, a database server, a client terminal, a front-end application used by a client user at each client terminal, A work directory on a client terminal provided in correspondence with the client user who is a work subject and a job directory, wherein the front-end application performs an action set for a job to be worked and an operation for the action When the information for specifying the content is received, the work directory and a job data for storing a file related to a job recorded in the recording medium or a file server and set with an action to be performed by the work subject are set. By changing the connection status with the directory and recording information on the work status of the work subject for the action set for the job in the database server, the work status of the client user for the action can be managed. A work management system characterized in that: 2. A recording medium or a file server storing one or more job directories storing files related to jobs, a database server, a client terminal, a front-end application used by a client user at the client terminal, A work directory on a client terminal provided in correspondence with the front-end application and a job directory as a subject, wherein the front-end application performs an action set for a job to be worked and an operation for the action A job for storing a file related to a job recorded on the recording medium or the file server and set with an action to be performed by the work subject according to the information specifying the content. Managing the work state of the front-end application for the action by changing the connection state with the directory and recording information on the work state of the work subject for the action set for the job in the database server A work management system characterized by being made possible. 3. A recording medium or file server storing one or more job directories storing files related to jobs, a database server, a client terminal, a front-end application used by a client external application on the client terminal, A work directory on a client terminal provided in correspondence with the client external application and a job directory, which are work subjects, and wherein the front-end application performs an action set for a job to be worked on and an action corresponding to the action. When the information specifying the operation content is received, the operation directory and the job recorded in the recording medium or the file server and set with the action to be performed by the work subject are set. By changing the connection state between the client directory and the job directory storing the file, and by recording information on the work state of the work subject to the action set for the job in the database server, the action of the client external application A work management system characterized in that the work state of the work can be managed. 4. A recording medium or a file server storing one or more job directories storing files related to jobs, a database server, a client terminal, a front-end application used by the client terminal, and a work subject. A work directory on the client terminal provided in correspondence with the client terminal and a job directory, wherein the front-end application specifies an action set for the job to be worked and an operation content for the action When information is received, a connection state between the work directory and a job directory that stores a file related to a job recorded on the recording medium or a file server and set with an action to be performed by the work subject is set. Changing the state of the client terminal and recording the information on the work state of the work subject for the action set in the job in the database server, whereby the work state of the client terminal for the action can be managed. Work management system. 5. The work management system according to claim 1, wherein the work directory is set so that a work subject other than a corresponding work subject cannot access the work directory. 6. The work management system according to claim 1, wherein the work subject is in the connected state only during work, and is not in the connected state when not working. 7. The database server according to claim 1, wherein the front-end application records at least one of a first work state to a third work state as information on a work state of the work subject for an action set in the job. The work management system according to claim 1, wherein: 8. The front-end application changes at least one of the first to third work states and the work state as information on the work state of the work subject for the action set in the job. The work management system according to any one of claims 1 to 6, wherein the performed time is recorded in a database server. 9. The front end application changes at least one of the first to third work states and the work state as information on the work state of the work subject for the action set in the job. The recorded time is recorded in a database server, the database server uses the time, calculates the work time for the action for the work subject,
The work management system according to claim 1, wherein the work management system records the information. 10. The information processing apparatus according to claim 1, wherein the front-end application includes at least a first state as information on a work state of the work subject with respect to an action set in the job.
Any one of the work state to the third work state and the time at which the work state was changed are recorded in the database server, and the work time for the action with respect to the work subject is calculated using the time. The work management system according to claim 1. 11. The method according to claim 1, wherein the first work status is obtained from the database server by the front-end application, the information relating to the storage location of the job to which the action to be performed is set, The work management system according to any one of claims 7 to 10, wherein the information is recorded after directly connecting the stored job directory and the work directory. 12. The work management system according to claim 7, wherein said second work state is recorded after said direct connection has been once disconnected by a front-end application. 13. The method according to claim 7, wherein the third work state is recorded after the direct connection is disconnected by a front-end application and the work of the work subject is determined. Work management system described in Crab. 14. The first work state is obtained by acquiring information on a storage location of a job in which an action to be worked on is set from a database server by a front-end application, and executing the job in accordance with the acquired information on the storage location. The job state is recorded after directly connecting the stored job directory and the work directory, the second work state is recorded after the direct connection is temporarily disconnected by a front-end application, and the third work state is recorded by the front-end application. The work management system according to any one of claims 7 to 10, wherein the work management system is recorded after disconnecting the direct connection and determining the work of the work subject. 15. When receiving an instruction relating to any one of the first to third working states, the front-end application performs an authentication process on the database server as an authentication process prior to the connection or disconnection process. A process of inquiring the work state of the work subject and a process of determining whether or not the instruction can be accepted based on the inquiry result, and if it is determined that the instruction can be accepted, the connection or disconnection process The work management according to any one of claims 7 to 14, wherein, if it is determined that the instruction cannot be received in the determining process, a process of notifying that the instruction is not received is performed. system. 16. When receiving an instruction related to any one of the first to third working states, the file server performs an authentication process on the database server as an authentication process prior to the connection or disconnection process. A process of inquiring the work state of the work subject and a process of determining whether or not the instruction can be received based on the result of the inquiry are performed. If it is determined that the instruction can be received, the connection or disconnection process is performed. The work management system according to any one of claims 7 to 14, wherein, if it is determined that the instruction cannot be received in the determining process, a process of notifying that the instruction is not received is performed. . 17. In the authentication processing, the instruction of the first work state is determined whether an action to be worked exists or not.
Determine whether or not it can be accepted depending on whether or not it is in the work state,
It is determined whether or not the instruction of the second work state can be received based on whether or not the first work state, and the instruction of the third work state can be received depending on whether or not the first work state or the second work state. 17. The work management system according to claim 15, wherein it is determined whether or not the operation is performed. 18. A storage medium or a file server storing one or more job directories storing files related to jobs, a database server, a client terminal, a front-end application used by a work subject at each client terminal, A work directory on the client terminal provided in correspondence with the work subject and the job directory, wherein the front-end application specifies an action set for the job to be worked and an operation content for the action. When receiving the information, the connection state between the work directory and a job directory stored in the recording medium or the file server and storing job data to be processed by the work subject is changed. Set in the job The information about the action status be recorded in the database server, the job management system is characterized in that a manageable work status of the job. 19. The job management system according to claim 18, wherein the work directory is set so that a work subject other than the corresponding work subject cannot access the work directory. 20. The job management system according to claim 18, wherein the work subject is in the connected state only during work, and is not in the connected state when not working. 21. The front-end application records at least one of a first action state to a fourth action state in a database server as information on an action state set for the job. 21. The job management system according to any one of Items 18 to 20. 22. The database server according to claim 21, wherein the front-end application stores at least one of a first action state to a fourth action state and a change time at which the action state was changed as information on the action state set in the job. The job management system according to any one of claims 18 to 20, wherein the job management system records the job. 23. The front-end application stores at least one of a first action state to a fourth action state and a change time at which the action state is changed as a database server as information on an action state set for the job. 21. The job management system according to claim 18, wherein the job management system calculates a work time for the action using the time. 24. The database server according to claim 24, wherein the front-end application stores at least one of a first action state to a fourth action state and a change time at which the action state was changed as information on the action state set for the job. 21. The job management system according to claim 18, wherein the database server calculates and records a work time for the action using the time. 25. The method according to claim 21, wherein the first action state is recorded after the front-end application sets an action for the job.
24. The job management system according to any one of 24. 26. The second action state is a step in which information on a storage location of a job in which an action to be performed is set is acquired from a database server by a front-end application, and the job is stored in accordance with the acquired information on the storage location. 25. The job management system according to claim 21, wherein the information is recorded after directly connecting the stored job directory and the work directory. 27. The job management system according to claim 21, wherein said third action state is recorded after said direct connection is once disconnected by a front-end application. 28. The fourth action state includes disconnecting the direct connection by a front end application,
The job management system according to any one of claims 21 to 24, wherein the job management system records the action after confirming the action in the database server. 29. The first action state is recorded after the front-end application sets an action for a job, and the second action state is an action to be performed by the front-end application from the database server. The information about the storage location of the set job is obtained, and the job directory is stored after directly connecting the job directory storing the job and the work directory according to the information about the obtained storage location, and the third action state is stored in the front-end application. The first action state is recorded after the direct connection is once disconnected, and the fourth action state is recorded after the direct connection is disconnected by the front-end application and the action is determined in the database server. Job management system according to any one of the Motomeko 21 to 24. 30. When receiving an instruction relating to any one of the first action state to the fourth action state, the front-end application performs an authentication process prior to the setting of the action, the connection or the disconnection process. Performing a process of querying the database server for the action state of the action, and a process of determining whether the instruction can be received based on the query result,
The process of setting the action, connecting or disconnecting if it is determined that the instruction is acceptable in the determining process, and notifying that the instruction is not accepted if the process is not acceptable in the determining process. The work management system according to any one of claims 21 to 29, wherein: 31. When receiving an instruction relating to any one of the first action state to the fourth action state, the file server performs an authentication process prior to the action setting, the connection or the disconnection process. ,
A process of querying the database server for the action status of the action, and a process of determining whether or not the instruction can be received based on the result of the query. 30. The method according to claim 21, wherein the setting, the connection, or the disconnection processing is performed, and if it is determined that the instruction cannot be received in the determination processing, a processing of notifying that the instruction is not received is performed. The work management system according to any one of the above. 32. In the authentication processing, it is determined whether or not an instruction for a first action state is acceptable based on whether or not a job to be set exists, and an instruction for a second action state is a first action state. It is determined whether or not reception is possible based on whether or not the instruction in the third action state is in the second action state.
32. The work management system according to claim 30, wherein it is determined whether the instruction of the action state is acceptable based on whether the instruction is the second action state or the fourth action state. 33. A recording medium or file server storing one or more job directories storing files relating to a job, a database server, a client terminal, a front-end application used by a work subject at each client terminal, A plurality of work directories on a client terminal provided in correspondence with each work subject and a job directory of a group of client users who are the work subjects, wherein the front-end application stores A job for storing the work directory and job data recorded on the recording medium or the file server and to be processed by the work subject when the set action and information for specifying the operation content for the action are received; Directory By changing the connection state between the server and the information on the work state of the work subject for the action set in the job and the information on the action state set in the job in the database server, A work / job management system, wherein a work state of a work subject and a work state of the job can be managed. 34. A recording medium or a file server storing one or more job directories storing files relating to jobs, a database server, a client terminal, a front-end application used by a work subject at each client terminal, A plurality of work directories on a client terminal provided corresponding to each work subject and a job directory of a group consisting of front-end applications as the work subjects,
When the front-end application receives an action set for a job to be worked on and information for specifying an operation content for the action, the work directory is recorded on the recording medium or the file server and the work is performed. Changes the connection status with the job directory that stores the job data to be processed by the subject, information on the work status of the work subject with respect to the action set in the job, and the action status set in the job A work / job management system characterized in that the work state of the work subject and the work state of the job can be managed by recording information about the work in the database server. 35. A recording medium or a file server storing one or more job directories storing files related to jobs, a database server, a client terminal, a front-end application used by a work subject at each client terminal, A plurality of work directories on a client terminal provided in correspondence with each work subject and a job directory of a group consisting of client external applications as the work subjects, wherein the front-end application has When receiving the action specified in step (a) and information for specifying the operation content for the action, the job directory and job data recorded on the recording medium or the file server and targeted for the work of the work subject are stored. By changing the connection status with the job directory and recording the information on the work status of the work subject for the action set in the job and the information on the action status set in the job in the database server. And a work state of the work subject and a work state of the job. 36. A recording medium or a file server storing one or more job directories storing files relating to jobs, a database server, a client terminal, a front-end application used by a work subject at each client terminal, A plurality of work directories on the client terminal provided corresponding to each work subject and a job directory of the group consisting of the client terminals which are the work subjects, wherein the front-end application provides A job for storing the work directory and job data recorded on the recording medium or the file server and to be processed by the work subject when the set action and information for specifying the operation content for the action are received; Direct By changing the connection state between the database server and the information on the work state of the work subject for the action set in the job and the information on the action state set in the job in the database server. A work / job management system, wherein a work state of a subject and a work state of the job can be managed. 37. A recording medium or a file server storing one or more job directories storing files related to jobs, a database server, a client terminal, a front-end application used by a work subject at each client terminal, A client user, a front-end application, a client external application, a plurality of work directories on the client terminal provided corresponding to the work subject and a job directory comprising a group of client terminals, wherein the front-end application When receiving information specifying the action set for the target job and the operation content for the action,
A connection state between the work directory and a job directory that is stored in the recording medium or the file server and stores job data to be processed by the work subject is changed, and a response to an action set for the job is changed. The information on the work state of the work subject and the information on the action state set for the job are recorded in the database server, whereby the work state of the work subject and the work state of the job can be managed. Work and job management system. 38. The work / job management system according to claim 33, wherein the work directory is set so that a work subject other than the corresponding work subject cannot access the work directory. 39. The work / job management system according to claim 33, wherein the work subject is in the connected state only during work, and is not in the connected state when not working. . 40. The front-end application sets at least one of a first work state to a third work state as information on a work state of the work subject for an action set in the job, and sets the information in the job. 40. The work / job management system according to claim 33, wherein at least one of the first action state to the fourth action state is recorded in the database server as the information on the performed action state. 41. The front end application changes at least one of the first to third work states and the work state as information on the work state of the work subject for the action set in the job. The database server is configured to record at least one of a first action state to a fourth action state and a time at which the action state was changed as information on an action state set for the job. The work / job management system according to any one of 33 to 39. 42. The front-end application changes at least one of the first to third work states and the work state as information on the work state of the work subject for the action set in the job. The time, at least one of the first to fourth action states and the time at which the action state was changed are recorded in the database server as information on the action state set for the job, and 40. The work / job management system according to claim 33, wherein a work time for the action with respect to the work subject is calculated. 43. The front-end application changes at least one of the first to third work states and the work state as information on the work state of the work subject for the action set in the job. A time, at least one of a first action state to a fourth action state and a time at which the action state was changed are recorded in a database server as information relating to the action state set in the job; The work / job management system according to any one of claims 33 to 39, wherein a work time for the action with respect to the work subject is calculated and recorded using the data. 44. The front-end application changes at least one of the first to third work states and the work state as information on the work state of the work subject for the action set in the job. The time, at least one of the first to fourth action states and the time at which the action state was changed are recorded in the database server as information on the action state set for the job, and The work / job management system according to any one of claims 33 to 39, wherein a work time for the action is calculated. 45. The front-end application changes at least one of the first to third work states and the work state as information on the work state of the work subject for the action set in the job. A time, at least one of a first action state to a fourth action state and a time at which the action state was changed are recorded in a database server as information relating to the action state set in the job; The work / job management system according to any one of claims 33 to 39, wherein a work time for the action is calculated and recorded by using (1). 46. The method according to claim 40, wherein the first action state is recorded after setting an action for a job by a front-end application.
45. The work / job management system according to any one of -45. 47. A method according to claim 1, wherein the first work state is obtained from the database server by the front-end application, the information relating to the storage location of the job to which the action to be performed is set, and the job being executed in accordance with the acquired storage location information. 46. The work / job management system according to claim 40, wherein the information is recorded after directly connecting the stored job directory and the work directory. 48. The work / job management system according to claim 40, wherein said second work state is recorded after said direct connection is once disconnected by a front-end application. 49. The method according to claim 40, wherein the third work state is recorded after the front-end application disconnects the direct connection and makes an action decision to the database server. Work / job management system described in 1. 50. A method according to claim 1, wherein the first work state acquires information on a storage location of a job in which an action to be worked is set from a database server by a front-end application, and executes the job in accordance with the acquired information on the storage location. The job state is recorded after directly connecting the stored job directory and the work directory, the second work state is recorded after the direct connection is once disconnected by a front-end application, and the third work state is recorded by the front-end application. 41. The information is recorded after the direct connection is disconnected and the action is determined in the database server.
45. The work / job management system according to any one of 45. 51. The work / job management system according to claim 40, wherein said second to fourth action stages are determined according to work states of said plurality of work subjects. . 52. When at least one of the working groups of the group performing the work for the action is in the first working state, the action state of the action is described in the database as the second action state. The work / job management system according to claim 51, wherein 53. A method according to claim 53, wherein, among the group that performs the work for the action, when the work state of all the work subjects is the third work state, the action state of the action is described in the database as the fourth action state. The work / job management system according to any one of claims 51 and 52. 54. When at least one of the groups performing the work for the action is in the second work state and there is no work body in which the work state is the first work state, the action of the action is The work / job management system according to any one of claims 51 to 53, wherein the action state is described in the database as the third action state. 55. When an instruction relating to any one of the first to third work states is received, the front end application sends the work to the database server as authentication processing prior to the connection or disconnection processing. A process of inquiring about the work state of the subject and a process of determining whether or not the instruction can be received based on the result of the inquiry are performed. If the determination process determines that the instruction can be received, the connection or disconnection process is performed. 5. The method according to claim 4, wherein if it is determined that the instruction cannot be received in the determining process, a process of notifying that the instruction is not received is performed.
The work / job management system according to any one of 0 to 50. 56. When receiving an instruction relating to any one of the first working state to the third working state, the file server performs an authentication process on the database server as an authentication process prior to the connection or disconnection process. The process of inquiring the work state of, and performing a process of determining whether or not the instruction can be received based on the result of the inquiry, the connection or disconnection process if determined to be acceptable in the determining process,
The work / job management system according to any one of claims 40 to 50, wherein if it is determined that the instruction cannot be received in the determination process, a process of notifying that the instruction is not received is performed. . 57. In the authentication processing, the instruction of the first work state is determined whether an action to be worked exists or not.
Determine whether or not it can be accepted depending on whether or not it is in the work state,
It is determined whether or not the instruction of the second work state can be received based on whether or not the first work state, and the instruction of the third work state can be received depending on whether or not the first work state or the second work state. 57. The work / job management system according to claim 55, wherein it is determined whether or not the operation is performed.