Processing system, processing method, and program

The processing system addresses the challenge of accurately reflecting task requests by managing task lists with client-only requests, ensuring efficient task execution and reducing delays.

JP2025141468APending Publication Date: 2025-09-29NEC CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2024041413
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-03-15
Publication Date
2025-09-29

AI Technical Summary

Technical Problem

Existing systems fail to accurately reflect the contents of task requests in a shared task list, leading to potential work delays and inefficiencies.

Method used

A processing system with units that manage task lists by sharing them with clients while restricting agent requests, allowing only client requests to be accepted and executed, thereby ensuring accurate reflection of task content.

Benefits of technology

The system ensures that task list requests are accurately reflected, preventing work delays and enhancing operational efficiency by controlling access and updates based on predefined conditions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025141468000001_ABST
    Figure 2025141468000001_ABST
Patent Text Reader

Abstract

To provide a processing system which can precisely reflect a requested content on a task list.SOLUTION: A processing system according to the present invention has a first processing unit for carrying out processing for sharing a task list of an agent carrying out a work with a client asking the work, a second processing unit for receiving a request relating to information of the task list from the client and for not receiving any request from the agent, and a third processing unit for executing a request relating to the information of the task list from the client which the second processing unit received.SELECTED DRAWING: Figure 12
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present disclosure relates to a processing system, a processing method, and a program. [Background technology]

[0002] There are an increasing number of occasions where multiple users access the same information to perform tasks. Patent Document 1 discloses a related technology relating to a system for managing and sharing information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2000-181956 Summary of the Invention [Problem to be solved by the invention]

[0004] In the technology relating to the system related to Patent Document 1, there is a demand for a technology that can accurately reflect the contents of a request in a task list.

[0005] One of the objectives of each aspect of the present disclosure is to provide a processing system, a processing method, and a program that can solve the above-mentioned problems. [Means for solving the problem]

[0006] According to one aspect of the present disclosure, a processing system includes a first processing unit that performs processing to share a task list of an agent performing work with a client who requests the work, a second processing unit that accepts requests related to information in the task list from the client and does not accept requests from the agent, and a third processing unit that executes requests related to the information in the task list from the client accepted by the second processing unit.

[0007] According to another aspect of the present disclosure, a processing method includes performing a process of sharing a task list of an agent performing work with a client requesting the work, accepting a request from the client related to information in the task list, not accepting a request from the agent, and executing the accepted request from the client related to the information in the task list.

[0008] According to another aspect of the present disclosure, a program causes a computer to perform a process of sharing a task list of an agent performing work with a client who requests the work, accept a request from the client related to information in the task list, not accept a request from the agent, and execute the accepted request from the client related to the information in the task list. [Effects of the Invention]

[0009] According to each aspect of the present disclosure, the request content can be accurately reflected in the task list. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 illustrates an example of a task list according to some embodiments of the present disclosure. [Figure 2] FIG. 1 illustrates an example of a configuration of a processing system according to some embodiments of the present disclosure. [Figure 3] FIG. 2 is a diagram illustrating a first example of a processing flow of a processing system according to some embodiments of the present disclosure. [Figure 4] FIG. 10 is a diagram illustrating a second example of a processing flow of a processing system according to some embodiments of the present disclosure. [Figure 5] FIG. 10 is a diagram illustrating a third example of a processing flow of a processing system according to some embodiments of the present disclosure. [Figure 6] FIG. 10 is a diagram illustrating a fourth example of a processing flow of a processing system according to some embodiments of the present disclosure. [Figure 7] FIG. 10 is a diagram illustrating a fifth example of a processing flow of a processing system according to some embodiments of the present disclosure. [Figure 8] FIG. 10 is a diagram illustrating a sixth example of a processing flow of a processing system according to some embodiments of the present disclosure. [Figure 9] FIG. 10 is a diagram illustrating a seventh example of a processing flow of a processing system according to some embodiments of the present disclosure. [Figure 10] FIG. 1 is a first diagram illustrating processing performed by a processing system according to some embodiments of the present disclosure. [Figure 11] FIG. 2 is a second diagram illustrating the processing performed by the processing system according to some embodiments of the present disclosure. [Figure 12] FIG. 1 illustrates an example of a configuration of a processing system according to some embodiments of the present disclosure. [Figure 13] FIG. 1 is a diagram illustrating an example of a processing flow of a processing system according to some embodiments of the present disclosure. [Figure 14] FIG. 1 is a schematic block diagram illustrating the configuration of a computer according to at least one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, the embodiments will be described in detail with reference to the drawings. <Embodiment> A processing system 1 according to an embodiment of the present disclosure will be described with reference to the drawings. A processing device 10 of the processing system 1, which will be described later, is a device that executes processing on a task list LT, thereby suppressing work delays due to failure to add work to the task list LT. The task list LT shows a list of work to be performed by an agent. An agent is a person who performs work. A work is a job that is performed in a certain procedure.

[0012] (Task List) First, a task list LT to be processed by the processing device 10 according to an embodiment of the present disclosure will be described. FIG. 1 is a diagram illustrating an example of a task list LT according to some embodiments of the present disclosure. Each agent has a task list LT such as that shown in FIG. 1. A client is a person who requests work. The task list LT is shared between the client and the agent. The task list LT displays, for example, one week's worth of working hours. Here, working hours refer to the amount of time available for work within a certain period of time. Specifically, for example, if a client works eight hours a day and works five days a week, 40 hours of working hours are displayed in the task list LT. The agent can also reserve time in advance for other tasks that the agent wishes to use for their primary work. For example, if the client works 40 hours a week and the agent wishes to use 25 hours for their primary work, the task list LT displays 15 hours as the working time. Note that tasks can be added to the task list LT beyond the working hours. The agent cannot delete tasks requested by the client. Only the requester can delete a task (this process will be described in detail later).

[0013] (Configuration of processing device) 2 is a diagram illustrating an example of a configuration of a processing system 1 according to some embodiments of the present disclosure. As shown in FIG. 2, the processing system 1 includes a processing device 10 and a storage device 20.

[0014] The processing device 10 accesses a task list database 2011 provided in database software 201 (described later) stored in the storage device 20. The processing device 10 then performs processing such as addition, update, deletion, and reference to the task list of the corresponding agent (for example, the task list 2011a of agent 1).

[0015] 2, the processing device 10 includes a task time addition unit 101, a task time update unit 102, a task time deletion unit 103, a proxy task list reference unit 104, a working time addition unit 105, a working time update unit 106, and a working time deletion unit 107. The task time addition unit 101, the task time update unit 102, the task time deletion unit 103, the proxy task list reference unit 104, the working time addition unit 105, the working time update unit 106, and the working time deletion unit 107 are each realized by the processing device 10 executing software. Details of the processing performed by the task time addition unit 101, the task time update unit 102, the task time deletion unit 103, the proxy task list reference unit 104, the working time addition unit 105, the working time update unit 106, and the working time deletion unit 107 will be described later.

[0016] The storage device 20 stores database software 201, as shown in Fig. 2. The database software 201 includes a task list database 2011, an agent database 2012, and a client database 2013, as shown in Fig. 2.

[0017] The task list database 2011 includes a task list for each proxy. For example, the task list database 2011 shown in FIG. 2 includes a task list 2011a for proxy 1, a task list 2011b for proxy 2, and a task list 2011c for proxy 3.

[0018] The agent database 2012 contains information including at least the name and identifier (ID) of each agent. The agent database 2012 shown in Figure 2 indicates that the identifier of the agent with the name 1a is ID1a, and the identifier of the agent with the name 2a is ID2a. For example, the identifiers are email addresses.

[0019] The client database 2013 includes information including at least the name and identifier of each client. For example, the identifier is an ID. The client database 2013 shown in FIG. 2 indicates that the identifier of the client with the name 1b is ID1b, and the identifier of the client with the name 2b is ID2b.

[0020] Here, we will explain how the task list LT is shared between the client and the agent. For example, in order to realize access control to the task list LT, access to the task list LT by anyone other than the agent (the owner of the task list) is made via the agent task list reference unit 104. The agent himself / herself accesses the task list LT directly.

[0021] The proxy task list reference unit 104 determines whether the request was made by a proxy. If the proxy task list reference unit 104 determines that the request was made by a proxy, it terminates the processing. If the proxy task list reference unit 104 determines that the request was not made by a proxy, it determines whether the request content is to acquire a task list LT. If the proxy task list reference unit 104 determines that the request content is to acquire a task list LT, it presents the task list LT to the requester and terminates the processing. If the proxy task list reference unit 104 determines that the request content is not to acquire a task list LT, it determines whether the request content is to update a "task" in the task list LT. If the proxy task list reference unit 104 determines that the request content is to update a "task" in the task list LT, it terminates the processing. If the proxy task list reference unit 104 determines that the request content is not to update a "task" in the task list LT, it terminates the processing. If the proxy task list reference unit 104 determines that the request content is to update a "task" in the task list LT, it performs the necessary update to the "task" in the task list LT. Then, the agent task list reference unit 104 returns the task list LT to the client and ends the process.

[0022] The above-described processing performed by the processing system 1 according to the embodiment of the present disclosure is merely an example, and the processing system 1 is not limited to the above-described processing. For example, the processing system 1 may perform the processing described below.

[0023] (Processing performed by the processing system of the present disclosure) FIG. 3 is a diagram illustrating a first example of a processing flow of the processing system 1 according to some embodiments of the present disclosure. FIG. 4 is a diagram illustrating a second example of a processing flow of the processing system 1 according to some embodiments of the present disclosure. FIG. 5 is a diagram illustrating a third example of a processing flow of the processing system 1 according to some embodiments of the present disclosure. FIG. 6 is a diagram illustrating a fourth example of a processing flow of the processing system 1 according to some embodiments of the present disclosure. FIG. 7 is a diagram illustrating a fifth example of a processing flow of the processing system 1 according to some embodiments of the present disclosure. FIG. 8 is a diagram illustrating a sixth example of a processing flow of the processing system 1 according to some embodiments of the present disclosure. FIG. 9 is a diagram illustrating a seventh example of a processing flow of the processing system 1 according to some embodiments of the present disclosure. Note that FIG. 3 illustrates processing performed by the business time adding unit 101. FIG. 4 illustrates processing performed by the business time updating unit 102. FIG. 5 illustrates processing performed by the business time deleting unit 103. FIG. 6 illustrates processing performed by the proxy task list referring unit 104. FIG. 7 illustrates processing performed by the working time adding unit 105. FIG. 8 illustrates processing performed by the working time updating unit 106. Fig. 9 shows the processing performed by the operation time deletion unit 107. Here, the processing performed by the processing system 1 shown in Figs. 3 to 9 will be described.

[0024] The authority to view and update the task list is controlled under certain conditions. For example, the agent can view the task list and can also update the "tasks." However, the agent cannot update the "tasks." The requester can view the task list and can also update the "tasks" that the requester added. The processing system 1 is a system that realizes this state.

[0025] (Processing performed by the business hours addition unit) First, the processing performed by the task time adding unit 101 shown in Fig. 3 will be described. The agent performs an operation on the processing device 10 to add one week's worth of task content and task hours for a certain task (for example, task 11 shown in Fig. 1). In response to this operation, the task time adding unit 101 performs a process to add one week's worth of task content and task hours (step S1). Then, the task time adding unit 101 determines whether the task hours are within one week's working hours (step S2).

[0026] If the task time adding unit 101 determines that the task hours exceed one week's worth of working hours (NO in step S2), it notifies the user (for example, by displaying this on an external display device) that the task hours exceed one week's worth of working hours (step S3). Then, the task time adding unit 101 returns to the processing of step S1. If the agent performs an operation to correct one week's worth of task content and task hours in response to the notification, the task time adding unit 101 executes the processing of step S1 in response to the operation by the agent.

[0027] Furthermore, if the task time adding unit 101 determines that the task time is within one week's working hours (YES in step S2), it determines whether the sum of the task time and working time is within one week's working hours (step S4). If the task time adding unit 101 determines that the sum of the task time and working time exceeds one week's working hours (NO in step S4), it notifies (for example, displays on an external display device) that the sum of the task time and working time exceeds one week's working hours (step S5). Then, the task time adding unit 101 ends the processing. If the task time adding unit 101 determines that the sum of the task time and working time is within one week's working hours (YES in step S4), it ends the processing.

[0028] (Processing performed by the business hours update unit) Next, the processing performed by the task time update unit 102 shown in Fig. 4 will be described. The agent selects a task to be updated and performs an operation on the processing device 10 to update the task time of the selected task. The task time update unit 102 performs a process to update the task time in response to the operation (step S11). The task time update unit 102 then determines whether the task time for one week is within the working hours for one week (step S12).

[0029] If the task time update unit 102 determines that the task hours for one week exceed the working hours for one week (NO in step S12), it notifies (for example, displays on an external display device) that the task hours for one week exceed the working hours for one week (step S13). Then, the task time update unit 102 returns to the processing of step S11. If the agent performs an operation to correct and update the task hours in response to the notification, the task time update unit 102 executes the processing of step S11 in response to the operation by the agent.

[0030] Furthermore, if the task time updating unit 102 determines that the task times for one week are within the working hours for one week (YES in step S12), it determines whether the sum of the task times and working times for one week is within the working hours for one week (step S14). If the task time updating unit 102 determines that the sum of the task times and working times for one week exceeds the working hours for one week (NO in step S14), it notifies (for example, displays on an external display device) that the sum of the task times and working times for one week exceeds the working hours for one week (step S15). Then, the task time updating unit 102 ends the processing. If the task time updating unit 102 determines that the sum of the task times and working times for one week is within the working hours for one week (YES in step S14), it ends the processing.

[0031] (Processing performed by the business hours deletion unit) Next, the processing performed by the task time deletion unit 103 shown in FIG. 5 will be described. The agent selects a task to be deleted and performs an operation on the processing device 10 to delete the task time of the selected task. The task time deletion unit 103 performs processing to delete the task time in response to the operation (step S21). The task time deletion unit 103 then determines whether the sum of the task time and working time for one week is within the working hours for one week (step S22). If the task time deletion unit 103 determines that the sum of the task time and working time for one week exceeds the working hours for one week (NO in step S22), it notifies (for example, displays on an external display device) that the sum of the task time and working time for one week exceeds the working hours for one week (step S23). Then, the task time deletion unit 103 ends the processing. If the task time deletion unit 103 determines that the sum of the task time and working time for one week is within the working hours for one week (YES in step S22), it ends the processing.

[0032] (Processing performed by the agent task list reference unit) Next, the processing performed by the agent task list reference unit 104 shown in FIG. 6 will be described. The agent or client operates the processing device 10 to select the agent's task list LT and acquire the task hours and work hours from the task list LT of the selected agent. The agent task list reference unit 104 performs processing to acquire the task hours and work hours from the agent's task list LT in response to the operation (step S31). The agent task list reference unit 104 then determines whether the total of the task hours and work hours for one week is within the working hours for one week (step S32). If the agent task list reference unit 104 determines that the total of the task hours and work hours for one week exceeds the working hours for one week (NO in step S32), it notifies (for example, by displaying on an external display device) that the total of the task hours and work hours for one week exceeds the working hours for one week (step S33). The agent task list reference unit 104 then terminates the processing. Furthermore, if the proxy task list reference unit 104 determines that the total of the business hours and the working hours for one week is within the working hours for one week (YES in step S32), the process ends.

[0033] (Processing performed by the work time addition unit) Next, the processing performed by the task time adding unit 105 shown in FIG. 7 will be described. The client performs an operation on the processing device 10 to add one week's worth of task content and task time for a certain task (for example, task 11 shown in FIG. 1). The task time adding unit 105 performs processing to add one week's worth of task content and task time in response to the operation (step S41). The task time adding unit 105 then determines whether the total of the task time and task time is within one week's work hours (step S42). If the task time adding unit 105 determines that the total of the task time and task time exceeds one week's work hours (NO in step S42), it notifies (for example, displays on an external display device) that the total of the task time and task time exceeds one week's work hours (step S43). The task time adding unit 105 then terminates the processing. If the task time adding unit 105 determines that the total of the task time and task time is within one week's work hours (YES in step S42), it terminates the processing.

[0034] (Processing performed by the work time update unit) Next, the processing performed by the task time update unit 106 shown in FIG. 8 will be described. The client selects a task to be updated and performs an operation on the processing device 10 to update the task time of the selected task. The task time update unit 106 performs processing to update the task time in response to the operation (step S51). The task time update unit 106 then determines whether the sum of the task time and task time for one week is within the working hours for one week (step S52). If the task time update unit 106 determines that the sum of the task time and task time for one week exceeds the working hours for one week (NO in step S52), it notifies (for example, displays on an external display device) that the sum of the task time and task time for one week exceeds the working hours for one week (step S53). The task time update unit 106 then terminates the processing. If the task time update unit 106 determines that the sum of the task time and task time for one week is within the working hours for one week (YES in step S52), it terminates the processing.

[0035] (Processing performed by the work time deletion unit) Next, the processing performed by the task time deletion unit 107 shown in FIG. 9 will be described. The client selects a task to be deleted and performs an operation on the processing device 10 to delete the task time of the selected task. The task time deletion unit 107 performs processing to delete the task time in response to the operation (step S61). The task time deletion unit 107 then determines whether the sum of the task time and task time for one week is within the working hours for one week (step S62). If the task time deletion unit 107 determines that the sum of the task time and task time for one week exceeds the working hours for one week (NO in step S62), it notifies (for example, displays on an external display device) that the sum of the task time and task time for one week exceeds the working hours for one week (step S63). The task time deletion unit 107 then terminates the processing. If the task time deletion unit 107 determines that the sum of the task time and task time for one week is within the working hours for one week (YES in step S62), it terminates the processing.

[0036] (advantage) The processing system 1 according to an embodiment of the present disclosure has been described above. In the processing system 1, the proxy task list reference unit 104 (an example of a first processing unit) performs processing to share the task list of the proxy who will perform the work with the client who requests the work. The proxy task list reference unit 104 (an example of a second processing unit) accepts requests related to the task list information from the client, but does not accept requests from the proxy. The proxy task list reference unit 104 (an example of a third processing unit) executes the accepted request related to the task list information from the client. This processing system 1 allows the request content to be accurately reflected in the task list.

[0037] As mentioned above, the authority to view and update the task list is controlled under certain conditions. For example, the agent can view the task list and can also update the "tasks." However, the agent cannot update the "tasks." The requester can view the task list and can also update the "tasks" that the requester added. The processing system 1 is a system that realizes this state.

[0038] However, if there are multiple requesters, tasks by other requesters on the task list cannot be updated, and may not necessarily be viewable. The processing system 1 according to another embodiment of the present disclosure may perform different processing depending on whether the agent and requester belong to the same organization. For example, if the identifier is an email address and the domain name of the identifier in the agent database 2012 is the same as the domain name of the identifier in the requester database 2013, the processing device 10 determines that the agent and requester belong to the same organization. If the domain name of the identifier in the agent database 2012 is different from the domain name of the identifier in the requester database 2013, the processing device 10 determines that the agent and requester belong to different organizations. If the processing device 10 determines that the agent and requester belong to the same organization, the processing device 10 may perform the processing of steps S1 to S63 shown in FIGS. 3 to 9. Furthermore, if the processing device 10 determines that the agent and requester belong to different organizations, the processing device 10 may perform the processing described below.

[0039] Fig. 10 is a first diagram for explaining processing performed by the processing system 1 according to some embodiments of the present disclosure. Fig. 11 is a second diagram for explaining processing performed by the processing system 1 according to some embodiments of the present disclosure. Fig. 10 is a diagram showing an example of a task list LT when the agent and the client belong to different organizations. Fig. 11 is a diagram showing an example of a processing flow of the processing system 1 when the agent and the client belong to different organizations.

[0040] The task list LT shown in FIG. 10 is a task list in which there is one agent, Agent 1, and three requesters, Requester 1, Requester 2, and Requester 3, and the domain names in the identifiers of Agent 1, Requester 1, and Requester 2 are the same, while the domain name of Requester 3 is different. For example, Requester 1 can perform processes on the processing device 10, such as updating or referencing task 11 added by Requester 1, referencing task 21 added by Requester 2 who belongs to the same organization, or referencing task 31 added by Requester 3 who belongs to a different organization. When Requester 1 performs any of these processes, the processing device 10 executes a process corresponding to the process performed by Requester 1, among processes such as updating or referencing task 11 added by Requester 1, referencing task 21 added by Requester 2 who belongs to the same organization, or referencing task 31 added by Requester 3 who belongs to a different organization. In addition, Requester 3 can perform processes on the processing device 10, such as updating or referencing task 31 added by Requester 3. When the requester 3 performs any of these processes, the processing device 10 executes a process corresponding to the process performed by the requester 3, among processes for updating or referencing the task 31 added by the requester 3.

[0041] For example, the client selects the agent's task list LT and performs an operation to acquire the task hours and working hours from the selected task list LT on the processing device 10. The agent task list reference unit 104 acquires the task hours and working hours from the task list LT in accordance with the operation performed by the client (step S71). The agent task list reference unit 104 determines whether the task list LT includes work by a client in a different organization from the client (step S72).

[0042] If the proxy task list reference unit 104 determines that the task list LT includes work by a client in a different organization from the client (YES in step S72), it hides the work content added by the client in a different organization from the client (step S73).Then, the proxy task list reference unit 104 determines whether the total of the business hours and working hours for one week is within the working hours for one week (step S74).

[0043] If the proxy task list reference unit 104 determines that the total of the task hours and work hours for one week exceeds the working hours for one week (NO in step S74), it notifies (for example, displays on an external display device) that the total of the task hours and work hours for one week exceeds the working hours for one week (step S75). Then, the proxy task list reference unit 104 ends the processing. On the other hand, if the proxy task list reference unit 104 determines that the total of the task hours and work hours for one week is within the working hours for one week (YES in step S74), it ends the processing.

[0044] Furthermore, if the proxy task list reference unit 104 determines that the task list LT does not include work of a client in a different organization from this client (NO in step S72), the process proceeds to step S74.

[0045] The processing system 1 according to another embodiment of the present disclosure can limit the information that can be referenced by an agent or a client.

[0046] 12 is a diagram illustrating an example of the configuration of a processing system 1 according to some embodiments of the present disclosure. As illustrated in FIG. 12, the processing system 1 includes a first processing unit 301, a second processing unit 302, and a third processing unit 303.

[0047] The first processing unit 301 performs a process of sharing a task list of an agent who will perform work with a client who requests the work. The second processing unit 302 accepts a request related to the task list information from the client, but does not accept a request from the agent. The third processing unit 303 executes the request related to the task list information from the client that the second processing unit has accepted.

[0048] The first processing unit 301, the second processing unit 302, and the third processing unit 303 can be realized by using the functions of the proxy task list reference unit 104 shown in FIG. 2, for example.

[0049] 13 is a diagram showing an example of a processing flow of the processing system 1 according to some embodiments of the present disclosure. Next, the processing of the processing system 1 will be described with reference to FIG.

[0050] The first processing unit 301 performs a process of sharing a task list of an agent who will perform work with a client who requests the work (step S101). The second processing unit 302 accepts a request related to the task list information from the client, but does not accept a request from the agent (step S102). The third processing unit 303 executes the request related to the task list information from the client accepted by the second processing unit (step S103).

[0051] The processing device 10 according to another embodiment of the present disclosure has been described above. The processing device 10 can accurately reflect the request content in the task list.

[0052] The order of the processes in the embodiments of the present disclosure may be changed as long as the processes are performed appropriately.

[0053] Although the embodiments of the present disclosure have been described, the above-mentioned processing system 1 and other control devices may have a computer system built therein. The above-mentioned processing steps are stored in the form of a program on a computer-readable recording medium, and the above processing is performed by reading and executing this program by a computer. Specific examples of computers are shown below.

[0054] 14 is a schematic block diagram showing the configuration of a computer according to at least one embodiment. As shown in FIG. 14, the computer 5 includes a CPU (Central Processing Unit) 6, a main memory 7, a storage 8, and an interface 9.

[0055] For example, the above-described processing system 1 and each of the other control devices are implemented in a computer 5. The operation of each of the above-described processing units is stored in the form of a program in a storage 8. The CPU 6 reads the program from the storage 8, loads it into the main memory 7, and executes the above-described processing in accordance with the program. The CPU 6 also allocates storage areas in the main memory 7 corresponding to each of the above-described storage units in accordance with the program. Note that the CPU 6 of the present disclosure may be a controller.

[0056] Examples of storage 8 include a hard disk drive (HDD), a solid state drive (SSD), a magnetic disk, a magneto-optical disk, a compact disc read-only memory (CD-ROM), a digital versatile disc read-only memory (DVD-ROM), and a semiconductor memory. Storage 8 may be an internal medium directly connected to the bus of computer 5, or an external medium connected to computer 5 via interface 9 or a communication line. In addition, when this program is distributed to computer 5 via a communication line, computer 5 that receives the program may load the program into main memory 7 and execute the above-mentioned processing. In at least one embodiment, storage 8 is a non-transitory tangible storage medium.

[0057] The program may also implement some of the functions described above. Furthermore, the program may be a file that can implement the functions described above in combination with a program already recorded in the computer system, a so-called differential file (differential program).

[0058] Although several embodiments of the present disclosure have been described, these embodiments are merely examples and do not limit the scope of the disclosure. Various additions, omissions, substitutions, and modifications may be made to these embodiments without departing from the spirit of the disclosure.

[0059] Note that part or all of the above-described embodiments can be described as, but are not limited to, the following supplementary notes.

[0060] (Appendix 1) a first processing unit that performs processing to share a task list of an agent who performs work with a client who requests the work; a second processing unit that accepts a request related to the information in the task list from the client and does not accept a request from the agent; a third processing unit that executes a request related to the information in the task list from the requester that is accepted by the second processing unit; A processing system comprising:

[0061] (Appendix 2) The request from the client relating to the information on the task list is including at least one of adding, updating, and deleting information from the task list; 10. The processing system of claim 1.

[0062] (Appendix 3) The task list information includes: including the work content and working hours for a given period; 10. The processing system of claim 1 or 2.

[0063] (Appendix 4) a fourth processing unit that issues a notification when a working time for a predetermined period included in the information of the task list exceeds an upper limit of working time set for the predetermined period; 4. The processing system of any one of claims 1 to 3, comprising:

[0064] (Appendix 5) A process of sharing a task list of the agent who will perform the work with a requester who will request the work; Accepting a request related to the information on the task list from the client, and not accepting a request from the agent; Executing the received request from the requester relating to the information in the task list; A processing method comprising:

[0065] (Appendix 6) The request from the client relating to the information on the task list is including at least one of adding, updating, and deleting information from the task list; The processing method described in Appendix 5.

[0066] (Appendix 7) The task list information includes: including the work content and working hours for a given period; A processing method as described in Appendix 5 or Appendix 6.

[0067] (Appendix 8) notifying the user when the working hours for a predetermined period included in the information on the task list exceed an upper limit of working hours set for the predetermined period; 8. The processing method according to any one of appendices 5 to 7,

[0068] (Appendix 9) On the computer, A process of sharing a task list of the agent who will perform the work with a requester who will request the work; Accepting a request related to the information on the task list from the client, and not accepting a request from the agent; Executing the received request from the requester relating to the information in the task list; A program that executes the following.

[0069] (Appendix 10) The request from the client relating to the information on the task list is including at least one of adding, updating, and deleting information from the task list; 10. The program described in Appendix 9.

[0070] (Appendix 11) The task list information includes: including the work content and working hours for a given period; 10. A program according to claim 9 or 10.

[0071] (Appendix 12) notifying the user when the working hours for a predetermined period included in the information on the task list exceed an upper limit of working hours set for the predetermined period; 12. The program according to any one of claims 9 to 11, which causes the computer to execute the above. [Explanation of symbols]

[0072] 1. Processing System 5. Computer 6 CPU 7. Main memory 8. Storage 9. Interface 10 Processing equipment 20...Storage device 101···Additional Business Hours 102...Business hours update department 103 Business hours deletion section 104. Agent Task List Reference 105...Work time addition unit 106...Working time update section 107 Work time deletion section 201···Database Software 2011 Task List Database 2012 Agent Database 2013···Client Database

Claims

1. a first processing unit that performs processing to share a task list of an agent who performs a task with a client who requests the task; a second processing unit that accepts a request related to the information in the task list from the client and does not accept a request from the agent; a third processing unit that executes a request related to the information in the task list from the requester that is accepted by the second processing unit; A processing system comprising:

2. The request from the client relating to the information on the task list is at least one of adding, updating, and deleting information from the task list; The processing system of claim 1 .

3. The task list information includes: including the work content and working hours for a given period; The processing system of claim 1 .

4. a fourth processing unit that issues a notification when a working time for a predetermined period included in the information of the task list exceeds an upper limit of working time set for the predetermined period; The processing system according to claim 1 , comprising:

5. A process of sharing a task list of the agent who will perform the work with a requester who will request the work; Accepting a request related to the information on the task list from the client, and not accepting a request from the agent; Executing the received request from the requester relating to the information in the task list; A processing method comprising:

6. On the computer, A process of sharing a task list of the agent who will perform the work with a requester who will request the work; Accepting a request related to the information on the task list from the client, and not accepting a request from the agent; Executing the received request from the requester relating to the information in the task list; A program that executes the following.

Citation Information

Patent Citations

  • Information managing and sharing system

    JP2000181956A