JPH1097569A - Operation request support device and computer-readable recording medium storing operation request support program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To speedily determine a proper request destination for an operation requester without any restrictions of system environment. SOLUTION: Individual agents are generated previously by persons in charge as operation request destinations and manage the acceptance to the operation end of an operation request specifying a person in charge. Organization agents 18 are generated previously by previously defined enterprises and organizations and a person in charge is determined at an operation request specifying an organization. When the operation request is received from an interface agent 12, operation agents 14 are generated by request operations and request an individual agent 16 or organization agent 18 specified at the operation request to determine a destination in charge of the request operation, thereby managing the operation contents to the end of the request operation after being informed of the decision on the destination in charge.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a work request support apparatus for automatically determining a person in charge of a work request to a company or an organization and processing the work, and a computer readable recording of a work request support program. Regarding the medium.

[0002]

2. Description of the Related Art In recent years, a process management system and an approval system using a workflow for managing the progress of work have been expanding. However, with the expansion of a corporate organization, it is necessary to support the determination of a work request destination. is there. In a conventional work request support device, a client server system is used as a system environment, work requests are collectively received by a server, and a ToDo list is provided as a work undertaking list provided for each person in charge on the client side. The work of the new request is displayed, and the person in charge decides whether to accept the new work.

[0003]

However, in a system for displaying and accepting the work of a new request on the ToDo list of the person in charge, the acceptance and rejection of the work depends on the judgment of the person in charge. Depending on the work, it may take time to determine the person in charge, or the person in charge may be rejected, and there is a risk that the person in charge of the work request may not be properly determined.

[0004] Further, since the conventional system is a client-server system, the area under the jurisdiction of the server becomes a range in which work can be requested, and a large number of client-server systems are constructed in a company or organization to form a distributed system. There was a problem that could not be addressed. The present invention provides a work request support device and a computer that records a work request support program that enable an appropriate request destination to be quickly determined for a work request without being restricted by a system environment such as a client server system. It is an object to provide a possible recording medium.

[0005]

FIG. 1 is a diagram illustrating the principle of the present invention. The work request support device of the present invention includes a personal agent 16, an interface agent 12, an organization agent 18, and a work agent 14 having independent processing functions. The individual agent 16
It is generated in advance for each person in charge as a work request destination, and manages a work request in which a person in charge is designated from reception to completion of the work. The interface agent 12 functions as a user interface of the personal agent, displays its management information, and notifies the requester of acceptance, rejection, and completion of the requested work.

The organization agent 18 is generated for each company or organization defined in advance, and determines a person in charge of a work request specifying an organization. Further, the work agent 14
It is generated for each requested work, and requests the individual agent 16 or the organization agent 18 designated by the work request to determine the person in charge of the requested work. Manage work content.

More specifically, the individual agent 16 has a management function of a new request work, an underwriting work (ToDo list), and a work priority, and the interface agent 12 has a function of displaying the underwriting work list of the personal agent 16. It has a notification function for accepting, rejecting, and ending work requested. The organization agent 18 has a function of managing organization information and work charge information that define a company or organization, and a function of registering an organization and charge.
It has route information indicating that the requested work has reached the requested destination from the request source, related work information such as whether the request is a new request or a request again, and a work deadline management function.

[0010] According to the work request support apparatus of the present invention, the work charge information including the charge information managed by the individual agent 16 and the charge organization information managed by the organization agent 18 is provided in the organization. In addition, the person in charge of the work in the organization can quickly determine the work request. In addition, even if an appropriate person in charge is not found, the request is not rejected, but is designated within the organization and assumed.

Further, in the client server system, the scope of the server is in the range in which the requested work can be managed. However, the present invention does not use the server, but allows individuals or organizations to operate as agents operating on any terminal on the system. In order to realize this, work requests can be made between companies even on a large company scale. When the individual agent 16 receives the work request,
The request is compared with the schedule information of the individual registered in advance, and if there is a vacancy from the schedule information, the request is accepted, and if there is no vacancy in the schedule, the work request is rejected. This solves the problem that work is performed even when work cannot be performed according to a personal schedule such as a day with many schedules or a holiday.

When receiving a work request, the personal agent 16 refers to a request source list that does not reject a predetermined work request, and always accepts a work request from a request source registered on this request source list. You may make it. This specifies that the work cannot be refused by the organization information or the requester because there is a problem in rejecting requests from all persons due to the schedule of the individual. For example, by designating the affiliation manager as a request source that cannot be rejected, the work request from the affiliation manager can be presented to the person regardless of the schedule.

The present invention may further include a product agent. The product agent manages, for individuals and organizations managed by the individual agent 16 and the organization agent 18, route information of a request destination for creating a product such as a monthly report and a deadline for creating the product, and satisfies the deadline for the creation. Request product creation work.

The route information and the time limit for creating a product such as a monthly report usually exist independently of the work request processing and are managed separately.
When the expiration date of the product agent is approaching, a product work request is made according to the route information. In this case, when requesting a product creation operation, the product agent determines a request date with reference to a predetermined schedule of the request destination. In other words, immediately before the deadline and when the personal schedule is tight, even if a new work is added by the product agent, it is not possible to cope with the new work. Therefore, the work request date is determined with reference to the schedule.

The organization agent 18 can select a plurality of work candidates in response to a work request and present the work candidate to the request source for selection. That is, when it is not possible to narrow down the candidates for work, or when another person, such as the client or the affiliation manager of the organization, wants to select the request destination, it is possible to present a plurality of candidates to the request source and select it. I do. As a result, it is possible to present only those having a work ability, and it becomes possible for the person in charge to select candidates.

Further, a function for defining a role in an external company or organization is provided, and the work agent 14 notifies the external company or organization of the work request in response to the work request, and, based on the response information to the notification, the organization of the request destination. Alternatively, a company can be selected. That is, if the name of the organization and the company that can request the work is not known, there is a problem that the work cannot be requested. However, the role information is assigned to an external company or organization, and the role information is By referring to the information, it is possible to search for a request destination by generating the work agent 14 without knowing an external company name or organization name.

The present invention also provides a computer-readable recording medium on which a work request support program is recorded, wherein the recording medium is generated for each requested work and ends after the requested work is accepted. A work agent that manages the work request, a personal agent that is generated for each person in charge of the work request, manages the work request from the reception to the end of the work request that specifies the person in charge, and displays the management information of the individual agent. , An interface agent that notifies the requester of the acceptance, rejection, and completion of the requested work, and an organization agent that is generated for each predefined company or organization and determines the person in charge of the work request specifying the organization Is generated for each requested work and is requested to the individual agent or organization agent specified by the work request Ask the responsible destination of the determination of the work, work the agent and, work request support program with which to manage your work until the end of the work request after receiving the charge destination of the decision notice has been recorded. The details of a computer-readable recording medium that records the work request support program are basically the same as the device configuration.

[0016]

FIG. 2 is a block diagram of a system environment to which a work request support device of the present invention is applied, and exemplifies a system environment in which a plurality of client server systems are distributed. 2, in this embodiment, two client server systems 1A, 1B
Is provided. Client server system 1A,
1B each have a local area network (LA).
N) The server 2 and a plurality of clients 3 are connected via a connection 4, and each LAN is connected via a network server 5.

The server 2 provided in each of the client-server systems 1A and 1B has an LA in its own system.
An appropriate server function is provided for each client's request under the jurisdiction of the client connected to N4. Furthermore, LAN4 of the client server system 1B
Is connected to an external network 6 outside the system via a network server 5, and a user terminal 7 for requesting work is connected to the external network 6.

In the work request support apparatus of the present invention, a program application as a work request support module is installed in each of the clients 3 provided in the client server systems 1A and 1B.
Execute the underwriting process for the work request. The program module that implements this work request support processing is composed of an organization work request support module 8 and an individual work request support module 9.

For example, taking the client server system 1A as an example, the client server system 1A is assigned to one organization, for example, and the organization work request support module 8 is installed in one of the six clients. The personal work request support module 9 is installed in another client 3. Client 3 that has installed work request support module 8 for organization
Is a terminal used by the person in charge of the organization to which the client-server system 1A is applied, and the other clients 3 equipped with the personal work support module 9 are each person in charge of the organization to which the client-server system 1A is assigned. Is a terminal used personally.

The personal work request support module 9 mounted on the client 3 is provided for each person in charge of the organization. The person in charge of the organization can use any client, and the corresponding personal work request support module 9 moves according to the client use address of the person in charge. Similarly, the client server system 1B is also assigned to another organization, and has one client 3 equipped with an organization work request support module 8 used by an administrator and a personal client corresponding to each person in charge. There are four clients equipped with the work request support module 9.

FIG. 3 is a functional block diagram of a work request support module for realizing the processing function of the work request support device of the present invention. In FIG. 3, the processing function of the work request support apparatus of the present invention is composed of an interface agent 12, a work agent 14, a personal agent 16 and an organization agent 18, and a product agent 20 is provided as needed.

Each of the interface agent 12, the work agent 14, the individual agent 16 and the organization agent 18 is realized as a program module having an independent processing function, activated upon receiving a work request from the outside, and cooperating with each other. The assignment of the person in charge of the requested work is performed while taking the steps, and a series of management from the assignment to the end of the work is executed.

Here, the interface agent 12,
As shown in FIG. 2, the individual agent 16, the organization agent 18, and the product agent 20 are prepared in advance by a program module when a system to which the present invention is applied is constructed. Is generated in the system each time.

The work agent 14 includes information such as the contents of the work based on the work request, the requester, the request destination, the person in charge of the work, the acceptance status of the work, and the like. Work management unit 28
Is provided with a path information management unit 30, a related information management unit 32, and a time limit management unit 34. The route information management unit 30 manages route information indicating that the work request created by the requester has reached the request destination.

The related information management unit 32 manages information indicating whether the requested work is a new work or a re-requested work, or whether it is the parent work agent in the related work that has caused the work to occur. The deadline management unit 34 manages the deadline of the requested work, and has a function of notifying the work request destination (underwriter) or the work request source of the work deadline and displaying the work deadline. The personal agent 16 is individually generated for every person in charge of a work request included in the organization when the system to which the present invention is applied as shown in FIG. 2 is constructed. The individual agent 16 has a function of managing individual work. The work management unit 36 includes a ToDo list management unit 38, a priority order management unit 40, and a new request management unit 42.

The ToDo list management unit 38 is, for example, as shown in FIG.
Manages the ToDo list 60 indicating the contents of the undertaking work as described above. The ToDo list 60 includes, for example, a requester of underwriting work, a deadline, a work name, and the like. The priority management unit 40 performs setting management of the priority of the work in the waiting state written in the ToDo list managed by the ToDo list management unit 38.

The new request management unit 42 writes a new request received by specifying the address of the personal agent 16 via the interface agent 12 into a new request list, refers to the ToDo list by the ToDo list management unit 38, and vacates the list. It manages the rejection of new requests that are accepted if there is any, and rejected if there is no room. Also To
It also manages the end of the work on the Do list. The personal agent accepts the newly requested work request by referring to the schedule information of the person in charge corresponding to the personal agent 16 other than the vacant state of the ToDo list, or by referring to the exception information defining the exception of the work request acceptance. May be decided.

The personal agent 16 is provided with an interface agent 12 functioning as a user interface with a person in charge. The interface agent 12 has the functions of a new request unit 22, a ToDo list display unit 24, and a work notification unit 26. The new request unit 22 receives a new work request from the outside and triggers generation of the work agent 14 by the system.

The ToDo list display unit 24 outputs and displays a ToDo list 60 as shown in FIG. 4 managed by the ToDo list management unit 38 of the personal agent 16 in response to a display request of the person in charge. When the work notification unit 26 receives a notification of acceptance, rejection, and further completion of the underwriting work from the new request management unit 42 of the personal agent 16, the work notification unit 26 notifies the request source of the corresponding acceptance, rejection, and end work. .

The organization agent 18 is generated in advance corresponding to a company or an organization within the company, and its work management unit 44
Are provided with the functions of an organization information management unit 46, a work information management unit 48, and a request destination determination unit 50, and are further configured to register the organization information and work information of the work management unit 44.
A charge registration unit 52 is provided. The organization information management unit 46 manages organization information defining the organization form of the company applied by the work request support device of the present invention. The organization information basically has a hierarchical structure, and includes information on individuals belonging to the organization and information on an upper or lower organization belonging to the organization. The work-in-charge information management unit 48 stores information on the names (person-in-charge addresses) and roles of the persons in charge included in the organization. For example, the work charge information management unit 48
Manages a work list 62 as shown in FIG.
The name of the person in charge or the organization, the history information of the requester, and keywords indicating the details of the work are registered in the work list 60.

Referring again to FIG. 3, the request destination determining unit 50 of the organization agent 18 refers to the work list 62 managed by the work information management unit 48 as shown in FIG. Determine the person in charge. The determination of the person in charge as the request destination by the request destination determination unit 50 is specifically performed by the individual agents 16 of a plurality of persons in charge included in the organization.
Is designated, and the corresponding individual agent 16 is activated according to the result of the determination of the person in charge by the organization agent 18.

When the function of each agent for realizing the work request support apparatus of the present invention shown in FIG. 3 is applied to the system environment shown in FIG. 2, the organization work request support module 8 of the client 3 used by the manager is It has a processing function for each of the interface agent 12, the work agent 14, the individual agent 16 and the organization agent 18 in FIG.

On the other hand, regarding the personal work request support module 9 of the client 3 used by the person in charge,
The organization agent 18 does not exist, and has a module configuration for executing three processes of the interface agent 12, the individual agent 16, and the work agent 14. The organization work request support module 8 including the organization agent 18 is fixedly installed on a specific client 3 used by the administrator of the organization.

However, the interface agent 12 and the work agent 14 provided for each person in charge of the organization
And the personal work request support module 9 composed of the personal agent 16 is not fixed at the physical client position, and when the person in charge changes the client 3 used on the system, the changed client becomes In response to the request for the ID code of the person in charge, the person moves to a client supported by the person in charge and executes the work request support process.

The product agent 20 provided as needed in FIG.
As in the case of No. 8, for example, it is fixedly installed on the client of the manager in the organization, and a work request for generating a product such as a monthly report is made. Here Product Agent 2
Reference numeral 0 denotes a work request management unit 54, a route management unit 56, and a time management unit 58, which are individual agents 1 existing in a system environment to which the work request support device of the present invention is applied.
6 and the organization agent 18, the generation of a product such as the creation of a monthly report is performed as one work request.

When a product work request such as a monthly report is received from the product agent 20, the interface agent 12 operates the work agent 1 corresponding to the product.
4 and requests the work agent 14 of the product to generate the product from the personal agent 16 of the designated person in charge or the designated organization agent 18, and manages the route information, related information and time limit on the work agent 14. Will do.

FIG. 6 is a schematic diagram of the work request support processing of the present invention in the system environment 11 for the client server systems 1A and 1B of FIG. First, when a work request 8 is made from the outside to the system environment 11, the work request is accepted by the interface agent 12, and
A work agent 14 is generated in the system environment 11 in response to the work request.

Since the work request 8 includes the address designation of the person in charge or the organization as the request destination, if the work request that generated the work agent 14 is a personal address, for example, the persons A and B ,..., Z, personal agent addresses designated by the work request 8 from the individual agents 16A, 16B,. Of the work request to the personal agent, for example, the personal agent 16A, and determines the acceptance or rejection of the new acceptance by To.
The Do list is referred to, and when a new request is received, the Do list is written to the To Do list, and the person in charge A performs the work.

On the other hand, when the request destination of the work request 8 specifies, for example, the organization A, the work request is notified to the organization agent 18 provided corresponding to the organization A, and the organization agent 18A Then, the person in charge of the request is determined by referring to the work charge information. When the person in charge of the request is determined by the organization agent 18A, a work request is notified to the personal agent 16B of the determined person B belonging to the organization A by designating the person in charge address.

After that, the same work as when the requested work is directly notified to the individual agent is accepted, rejected, and when it is accepted, writing to the ToDo list and management until the end of the work are performed. Although the interface agent 12 exists corresponding to each of the individual agents 16A to 16Z, FIG. 6 shows one interface agent 12 which has received a work request as a representative.

Next, with reference to the flowcharts of FIGS. 7 and 8, the processing operation by the functional blocks of the work request support apparatus of the present invention of FIG. 3 will be described. In FIG. 7, first, a user who makes a work request using the user terminal 7 connected to the external network 6 outside the system in FIG. 2 makes a new work request in step S1. When a new request for this operation is made,
The deadline, the designation of the related work that has caused the requested work, the contents of the work, and the organization address or the individual address of the request destination are specified.

When a new work request from the user in step S1 is received by the system, a work agent 14 is generated in step S2 corresponding to the requested work. The processing after the generation of the work agent 14 in step S2 is divided depending on whether the request destination is an individual or an organization. If the request destination is the personal address, the process proceeds to step S4, and the new request newly received is written in the new request management list managed by the new request management unit 42 of the personal agent 16.

Subsequently, in step S5, the contents of the current ToDo list managed by the ToDo list management unit 38 are referred to, and if there is a vacancy in the ToDo list, it is determined that a new request has been received. For example, in the ToDo list 60 of FIG. 4 managed by the ToDo list management unit 38 of the agent 16, a requester based on a new request, a deadline,
Write additional work name.

Subsequently, in step S7, the route information management unit 30 of the work agent 14 additionally writes the route management information to the ToDo list of the personal agent 16 in the route management information, and determines the request source and the request destination of the new request. Write the person in charge of the request and the method of requesting the work until the person in charge is determined. On the other hand, if the destination of the work request is the organization address in step S3, the process proceeds to step S20, and the work charge information such as the work charge list 62 in FIG. 5 is extracted. Subsequently, step S21
Then, the request source on the work list 62 is compared with the request source of the currently received work request. Further, step S22
Then, the keywords on the work charge list are compared with the keywords of the currently received work request, and the keywords are extracted from the request source and the request contents. In step S23, a keyword indicating the work contents is registered as a database. The information is compared with the work agent information of the individual agent of the person in charge in the functioning organization, and the person or department to which the work request currently received can be assigned is assigned.

When the department or person in charge with the organization as the request destination is determined in step S23, the process returns to step S23.
Returning to 3, it is checked whether or not the request destination is an individual with respect to the department or person in charge determined for the processing for the organization in steps S20 to S23. Step S23
For example, when the department in charge is determined, the department in charge is also one subordinate organization, so that the process proceeds to step S20, and the person in charge in the department in charge is finally determined by the same processing.

If the person in charge has been finally determined in step S23, it is determined in step S3 that the request destination is an individual, and in the same manner as in the case of a work request using a personal address, steps S4 to S4 are performed. The process of S7 will be performed. On the other hand, when a new request is made to the personal agent by designating a personal address or an organization address, and the work request is rejected in step S5, the processing from step S8 in FIG. 8 is performed. First, in step S8, it is checked whether or not there is another candidate. If there is another candidate, in step S10, as a new request to another candidate,
The new request is passed to the individual agent, and the process returns to step S3 in FIG. 7 and repeats the same process.

If there is no other candidate in step S3, the process proceeds to step S9, where a new request is assigned to the individual agent 16 of the person in charge who becomes the supervisor of the person in charge who rejected the work request. If the responsible person accepts the new request for the personal agent 16 in step S11, the new request is added to the ToDo list in the responsible personal agent 16 in step S12, and the work agent is designated in step S13. Then, additional writing of the path information is performed in step S14, and the series of processing ends.

If the responsible person rejects the new request in step S11, the process proceeds to step S14, where it is checked whether the work request is a request from the company or a request from outside the company. If the work request is an in-house work request, there is not much problem even if the work request is rejected, so the work request is returned to the request source in step S19. On the other hand, if it is not a request from inside the company in step S14, since it is a request from outside the company,
In step S15, it is checked whether the request is from a company or an upper organization of the company or organization. If it is a request from an upper organization or a company, it is handed over to a person in charge of the upper organization as a new request in step S16 because the request cannot be accepted by the own organization, and the responsibility for the request is left.

If the request is not from the upper organization or the company in step S15, the request is an external work request. In this case, the request is not rejected even if a person in charge is not found. Additional writing is performed on the ToDo list of the person in charge, and in step S18, additional writing is performed on the route information of the work agent 14 to accept the work request.

In step S17, even if there is no appropriate person in charge in the organization, the new request is written on the ToDo list of the person in charge, and the work request is directly sent to the person who is deemed necessary by the person in charge. And appropriately respond to external requests. FIG. 9, FIG.
9 is a flowchart of work end processing after assignment of a person in charge to the work request has been completed by the processing of FIG. 8. When the person in charge performs the requested work in accordance with the ToDo list provided by the personal agent 16 and gives a work end instruction in step S1, the work notification is sent from the work notification unit 26 of the interface agent 12 via the work agent 14 in step S2. The end of the requested work is notified to the source.

FIG. 10 shows another embodiment of the personal agent 16 used in the present invention. In this embodiment, the work management unit 36 further manages the schedule of the person in charge. 64 is provided, and whether to accept or reject a newly requested work is determined based on the contents of the schedule management file 66 managed by the schedule management unit 64.

The schedule management file 66 managed by the schedule management unit 64 includes the individual agent 16
It checks whether there is a vacancy of a predetermined time, for example, several hours or more, by the deadline of the requested new work request from the ToDo list of the person in charge who assigns the information, and whether there is a vacancy of several hours or more before this work deadline. Is selected as a candidate for a new request.

FIG. 11 is a flowchart of the processing operation in the personal agent 16 of FIG.
When it is determined that the request destination is a personal address in step S24, the process proceeds to step S24, where the schedule management unit 64 refers to the contents of the schedule management file 66 of the person to whom the personal agent 16 has been assigned, and sets the time limit for the new request. Get a schedule.

Subsequently, in step S25, it is checked whether or not the acquired schedule has a free time of several hours or more before the deadline. If the free time is several hours or more, in step S6 the work schedule is determined as a candidate for a work request destination. Add the requested work to the ToDo list of the individual agent,
In step S7, the request source and the request destination are additionally written in the route management information of the work agent 14.

By checking whether or not the necessary work time is available by referring to the schedule up to the request deadline in such an individual agent, it is possible to find an appropriate person in charge who can reliably process the requested work and accept the request. FIG. 12 shows another embodiment of the personal agent 16 according to the present invention.
In addition to the above, an exception acquisition unit 68 is further provided. An exception database 70 storing predetermined exception information is connected to the exception acquisition unit 68.

As the exception information of the exception database 70, the information of the requester who accepts the request without checking by the schedule management unit 64 is described in advance. Thus, a request from a specific person described in the exception database 70 is written in the ToDo list of the personal agent regardless of the schedule of the person in charge, and the request is preferentially accepted.

FIG. 13 shows a process of accepting a request by the individual agent 16 shown in FIG. 12. If the request destination is a personal address in step S3, first, in step S26, the exception database 70 which is a list of persons not to reject is obtained. Get exception information. If there is a requester on the list acquired in step S27, the process immediately proceeds to step S6 without making an underwriting judgment based on the schedule management in steps S24 and S25, and additionally writes the work request to the ToDo list of the individual agent. Then, the path information of the work agent 14 is written in step S7.

FIG. 14 is a functional block diagram of the product agent 20 additionally provided in FIG. In a company or organization that constructs a system to which the work request support device of the present invention is applied, it is usually necessary to create a report document showing the progress of work and the result every certain number of work days. Therefore, in the present invention, a product agent 20 for creating, for example, a monthly report document which is not directly related to the original work request support work as shown in FIG. 14 but is important for its management is additionally provided.

The product agent 20 comprises a work request unit 54, a route management unit 56, and a time management unit 58. In this embodiment, the product agent 20 stores the monthly report document 1 stored in the document file 100.
2 is created for the target individual agent 16 and organization agent 18 by generating the work agent 14 in FIG. For example, the time management unit 58 manages the 20th of each month as a time limit for creating the monthly report document 102.
Through the step 4, a request to create a monthly report is made to the individual agent of the person in charge of the request destination and the organization agent of the request destination organization specified by the route management unit 56. Normally, a request is made to a section manager-level individual agent, who is responsible for the organization, two business days before the 20th day of the monthly report creation deadline.

FIG. 15 shows another embodiment of the product agent 20 according to the present invention, in which a personal schedule management unit 104 is further provided, and the monthly report document 10 of the time management unit 58 is provided.
For example, the request date two business days before, based on the work deadline 2, is changed as necessary by referring to the personal schedule. That is, the person in charge of the monthly report document creation request managed by the route management unit 56 issues a work request 20.
If another work is entered or a vacation is taken two business days before the day, the contents of the personal schedule are known by referring to the personal schedule management unit 104, and it is not possible to meet the schedule two business days before the closing date of the monthly report document 102. Therefore, a work request for a monthly report is issued as soon as possible.

In the embodiments shown in FIGS. 14 and 15, the creation of a monthly report document as a product is taken as an example. The product agent 20 can be constructed in exactly the same way. FIG. 16 shows another embodiment of the work agent used in the work request support device of the present invention. The work agent 14 generated in response to the work request notifies the contents of the work to an external company or organization. It is characterized in that the work accepting destination is determined from the response.

In FIG. 16, in the work request support system 72 according to the present invention, a work agent 14 is generated according to a requested work. On the other hand, a company order receiving system 76, 78 and an organization order receiving system 80 by an external company or organization are pre-established for the work request support system 72 through the network 74, and the role information sections 88, 90, 92 are defined.

When the work agent 14 of the work request support system 72 receives a work request, the work request unit 82 sends the company order receiving system 76, 78 through the network 74.
And role information section 8 provided in organization order receiving system 80
An inquiry is made to 8, 90, 92 as to whether or not to accept the requested operation by the broadcast command 94.
When a response notification 96, 97.98 is made from the role information units 88, 90, 92 in response to the work request inquiry by the broadcast command 94, these are received by the reply receiving unit 84 of the work agent 14, and the work request unit 86
, And selects an appropriate request destination from the companies or organizations that have responded to the acceptance of the requested operation, and performs the operation request. Even if the name or person in charge of an external company or organization is unknown, the role information for work requests in the company or organization is defined in advance, and the company name, organization name, etc. are required. It is possible to appropriately select a required request destination from the contents of the response simply by inquiring of the accepting destination of the work request by the broadcast command without having to perform the above.

[0064]

As described above, according to the present invention, information on a work request in an organization such as a company is provided as an independent processing function unit such as an individual agent corresponding to the person in charge or an organization agent corresponding to the organization. By doing so, the work requested by designating an individual or an organization can be requested to an appropriate person in charge.

In the case where a request from a person in charge within the organization is rejected, a specific person or a specific requestee can accept the request as it is, without rejecting the request to the requester. Work requests can be accepted and processed as much as possible. Furthermore, since the function of assigning the responsible information to the work request is realized as a function that can be independently processed as a personal agent corresponding to the person in charge or an organization agent corresponding to each organization, the scope of server control such as a server client system Even if it is a large-scale distributed system, it is possible to accept work requests with each individual or organization as a processing unit, a flexible system form can be adopted, Assignment of an appropriate person in charge to the work request at the time can be realized efficiently.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating the principle of the present invention.

FIG. 2 is a block diagram of a system environment to which the present invention is applied;

FIG. 3 is a functional block diagram of a work request support device according to the present invention.

FIG. 4 is an explanatory diagram of a ToDo list of the personal agent of FIG. 3;

FIG. 5 is an explanatory diagram of a work list used by the organization agent of FIG. 3;

FIG. 6 is a block diagram of functions of the present invention corresponding to a system environment.

FIG. 7 is a flowchart of a work request support process according to the present invention.

FIG. 8 is a flowchart of a work request support process according to the present invention (continued).

FIG. 9 is a flowchart of a work end process according to the present invention.

FIG. 10 is an explanatory diagram of a personal agent of the present invention provided with a schedule management function.

FIG. 11 is a flowchart of an underwriting process with reference to the schedule in FIG. 10;

FIG. 12 is an explanatory diagram of a personal agent of the present invention provided with a schedule management function and an exception acquisition function.

FIG. 13 is a flowchart of an underwriting process with reference to an exception in FIG. 12;

FIG. 14 is a functional block diagram of the contact agent of FIG. 3;

FIG. 15 is a functional block diagram of a contact agent having a personal schedule management function.

FIG. 16 is a block diagram showing determination of a request destination by referring to role information of external companies and organizations.

[Explanation of symbols]

 1A, 1B: Client server system 2: Server 3: Client 4: LAN 5: Network server 6: External network 7: User terminal 12: Interface agent 14: Work agent 16: Individual agent 18: Organization agent 20: Product agent 22: New request 24: ToDo list display 26: Work notification unit 28, 36, 44: Work management unit 30: Route information management unit 32: Related information management unit 34: Deadline management unit 38: ToDo list management unit 40: Priority order management unit 42: New request management unit 46: Organization information management unit 48: Work information management unit 50: Request destination determination unit 52: Organization / charge registration unit 54: Work request unit 56: Route management unit 58: Time management unit

 ────────────────────────────────────────────────── ─── Continuing on the front page (72) Inventor Hiroki Ichiki 4-1-1, Kamidadanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Prefecture Inside Fujitsu Limited (72) Inventor Satoru Ushijima 4-chome, Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa No. 1 in Fujitsu Limited

Claims (10)

[Claims] 1. A work agent that is generated for each requested work and manages from acceptance to completion of a requested work, and is generated for each person who is a work request destination and receives a work request specifying a person in charge. A personal agent that manages from the end of the work to the end of the work; an interface agent that displays the management information of the individual agent and notifies the requester of acceptance, rejection, and completion of the requested work to the requestor; An organization agent that is generated for each organization and determines the person in charge of the work request that specifies the organization, and the person in charge of the work requested for the individual agent or organization agent that is generated for each requested work and specified by the work request And a work agent that manages the contents of work up to the end of the requested work after receiving the decision of the person in charge and An operation request support device characterized by being provided. 2. The work request support device according to claim 1, wherein the individual agent includes a new request operation, an underwriting operation,
The interface agent has a function of managing work priorities, and the interface agent has a function of displaying an underwriting work list of the personal agent and accepting a requested work,
The organization agent has a function of notifying rejection and work completion, the organization agent has a function of managing organization information and work person information defining a company or an organization, and a function of registering an organization and a person in charge. A work request support device comprising a route information indicating that the request has been reached from the source, related work information such as a new request or a request again, and a work deadline management function. 3. The work request support device according to claim 1, wherein the individual agent receives a work request when receiving the work request.
A work request support apparatus, which compares the schedule information with pre-registered individual schedule information, accepts the request if there is a vacancy from the schedule information, and rejects the work request if there is no vacancy in the schedule. 4. The work request support device according to claim 3, wherein the individual agent receives a work request when receiving the work request.
A work request support apparatus characterized in that a work request from a request source registered on the request source list is always accepted by referring to a request source list that does not reject a predetermined work request. 5. The work request support apparatus according to claim 1, further comprising: a path information of a request destination for creating a product such as a monthly report for an individual and an organization managed by the individual agent and the organization agent; A work request support device, comprising: a product agent for managing a creation time limit and requesting a product creation operation to satisfy the creation time limit. 6. The work request support device according to claim 5, wherein the product agent determines a request date by referring to a predetermined request destination schedule when requesting a product creation operation. A work request support device characterized by the following. 7. The work request supporting device according to claim 1, wherein the organization agent selects a plurality of work candidates for the work request, presents the candidate to the requester, and causes the requester to select the work candidate. Support equipment. 8. The work request supporting apparatus according to claim 1, wherein a function for defining role information for the work request is provided to an external company or organization, and said work agent is provided to said external company or organization for said work request. And a request destination organization or company is selected from response information to the notification. 9. A work agent that is generated for each requested work and manages from acceptance to completion of a requested work, and is generated for each person who is a work request destination and receives a work request specifying a person in charge. A personal agent that manages from the end of the work to the end of the work; an interface agent that displays the management information of the individual agent and notifies the requester of acceptance, rejection, and completion of the requested work to the requestor; An organization agent that is generated for each organization and determines the person in charge of the work request that specifies the organization, and the person in charge of the work requested for the individual agent or organization agent that is generated for each requested work and specified by the work request And a work agent that manages the contents of work up to the end of the requested work after receiving the decision of the person in charge and A computer-readable recording medium having recorded thereon a work request support program. 10. A computer-readable recording medium having recorded thereon the work request support program according to claim 9, wherein the individual agent performs a new request operation, an underwriting operation,
The interface agent has a function of managing work priorities, and the interface agent has a function of displaying an underwriting work list of the personal agent and accepting a requested work,
The organization agent has a function of notifying rejection and work completion, the organization agent has a function of managing organization information and work person information defining a company or an organization, and a function of registering an organization and a person in charge. It can be read by a computer that records a work request support program characterized by having a route information indicating that the request has been reached from the original, a related work information such as a new request or a request again, and a work deadline management function. recoding media.