Work management device, work management method and program

Abstract

To support improvement of work efficiency.SOLUTION: A server 101 comprises: a reference acquisition unit 119 that acquires reference data obtained by performing statistical processing on a log for statistical processing, which is a log related to a first work; an evaluation target log acquisition unit 120 that acquires an evaluation target log, which is a log related to the first work performed by a first organization; an evaluation data generation unit 121 that generates evaluation data for evaluating an evaluation target set in relation to the first organization based on the evaluation target log; and evaluation means that generates evaluation data including an evaluation result for the evaluation target using the reference data and the evaluation data.SELECTED DRAWING: Figure 9

Description

[Technical field]

[0001] The present invention relates to a work management device, a work management apparatus, and a program. [Background technology]

[0002] For example, Patent Document 1 describes a counter support system for supporting procedures at counters of administrative agencies such as government offices.

[0003] The counter support system described in Patent Document 1 includes counter terminals for staff provided at a plurality of billing counters, a reception terminal, and a server connected to the counter terminals.

[0004] In the counter support system described in Patent Document 1, the reception terminal transmits identification card data, including selected data on the application form, selected data on the identification card, and an image of the identification card of the claimant captured using the camera function, as visit information to the server based on the claimant's operation on the screen. The server transmits information necessary for the staff at the claim counter, including the identification card data, to the counter terminal as visit information based on the visit information received from the reception terminal. The counter terminal displays information including the identification card data based on the visit information received from the server.

[0005] Patent Document 1 describes that the server performs statistical processing and predetermined analysis processing on history information related to visit status information, and creates graphs or the like of the resulting statistical information. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2018-139027 A Summary of the Invention [Problem to be solved by the invention]

[0007] However, the graphs created by the service support system described in Patent Document 1 show the number of residents who have completed procedures and waiting times for each department counter and each case in a given period of time. Therefore, even if it is possible to grasp the work status for each department counter and each case, it is difficult to get a clue as to how to improve work efficiency.

[0008] The present invention has been made in view of the above circumstances, and one of its objects is to provide a work management device and the like that can assist in improving work efficiency. [Means for solving the problem]

[0009] In order to achieve the above object, a work management device according to a first aspect of the present invention comprises: A reference acquisition means for acquiring reference data obtained by performing statistical processing on a statistical processing log, which is a log related to a first task; an evaluation target log acquisition means for acquiring an evaluation target log which is a log related to the first work performed by a first organization; an evaluation data generating means for generating evaluation data for evaluating an evaluation target set in relation to the first organization based on the evaluation target log; The system further comprises an evaluation means for generating evaluation data including an evaluation result for the evaluation object using the reference data and the evaluation data.

[0010] A work management method according to a second aspect of the present invention includes: Obtaining reference data obtained by performing statistical processing on a statistical processing log, which is a log related to a first task; Acquiring an evaluation target log, which is a log related to the first work performed by a first organization; generating evaluation data for evaluating an evaluation target set in relation to the first organization based on the evaluation target log; The method includes generating evaluation data including an evaluation result for the evaluation target using the reference data and the evaluation data.

[0011] The program according to the second aspect of the present invention comprises: On the computer, A program for executing the work management method. Effect of the Invention

[0012] According to the present invention, it is possible to assist in improving work efficiency. [Brief description of the drawings]

[0013] [Figure 1] 1 is a diagram showing a configuration of a work management system according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a diagram illustrating a functional configuration of a terminal according to an embodiment. [Diagram 3] FIG. 2 is a diagram illustrating a functional configuration of a server according to an embodiment. [Figure 4] FIG. 2 is a diagram illustrating a functional configuration of a terminal management unit according to an embodiment. [Diagram 5] FIG. 4 is a diagram illustrating an example of worker data according to an embodiment. [Figure 6] FIG. 4 is a diagram illustrating an example of workflow data according to an embodiment. [Figure 7] FIG. 2 is a diagram illustrating a functional configuration of a log recorder according to an embodiment. [Figure 8] FIG. 13 is a diagram illustrating an example of combination definition data according to an embodiment. [Figure 9] FIG. 2 is a diagram illustrating a functional configuration of an activity evaluation unit according to an embodiment. [Figure 10] FIG. 2 is a diagram showing the physical configuration of each of a terminal and a server according to an embodiment of the present invention. [Figure 11] 10 is a flowchart illustrating an example of a terminal process according to an embodiment of the present invention. [Figure 12] FIG. 11 is a diagram illustrating a first example of a screen transition in a terminal process according to an embodiment. [Figure 13] 13 illustrates a first example of a terminal log according to an embodiment. [Figure 14]FIG. 11 is a diagram illustrating a second example of a screen transition in the terminal processing according to an embodiment. [Figure 15] 13 illustrates a second example of a terminal log according to an embodiment. [Figure 16] 11 is a flowchart illustrating an example of a log collection process according to an embodiment of the present invention. [Figure 17A] FIG. 13 is a diagram illustrating an example of a work log according to an embodiment. [Figure 17B] FIG. 13 is a diagram illustrating an example of a work log according to an embodiment. [Figure 18] 1 is a flowchart illustrating an example of a work management process according to an embodiment of the present invention. [Figure 19A] FIG. 11 is a diagram showing an example of evaluation data (summary) according to an embodiment. [Figure 19B] FIG. 11 is a diagram showing an example of evaluation data (details) according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The same elements are designated by the same reference numerals throughout the drawings, and the description will be omitted where appropriate.

[0015] 1, a work management system according to an embodiment of the present invention includes terminals 100_a1-a3, 100_b, 100_c1-c2, and a server 101. The server 101 and each of the terminals 100_a1-a3, 100_b, 100_c1-c2 are communicatively connected via a network N constructed by wired or wireless means or a combination of these. Thus, the server 101, as a work management device, manages work performed using the terminals 100_a1-a3, 100_b, 100_c1-c2.

[0016] The terminals 100_a1 to a3 are terminals managed by organization A and used by workers performing work at organization A. The terminal 100_b is a terminal managed by organization B and used by workers performing work at organization B. The terminals 100_c1 to c2 are terminals managed by organization C and used by workers performing work at organization C.

[0017] In the following description, when there is no particular need to distinguish between the terminals 100_a1 to a3, 100_b, and 100_c1 to c2, they will be simply referred to as "terminals 100."

[0018] The organizations A to C according to the present embodiment are government offices of different cities, wards, towns, and villages. Each of the organizations A to C performs a common type of work, such as work associated with the movement out of a resident in the area under its jurisdiction (moving out work) and work associated with the movement in of a resident (moving in work), using a terminal 100 managed by each organization. Each work includes multiple steps common to each of the organizations A to C.

[0019] Each of the organizations A to C is not limited to a government office, and may be, for example, an administrative agency, a company, an organization, or an association, and the number of organizations managed by the server 101 may be one or more. Also, the number of terminals managed by each organization may be one or more. Furthermore, the tasks performed by each of the organizations A to C are not limited to moving-out and moving-in tasks, and may be various types of tasks.

[0020] (Functional configuration of terminal 100) The terminal 100 is a device operated by a worker to process work, and functionally includes an input receiving unit 102, a terminal communication unit 103, a display unit 104, and a terminal log creation unit 105, as shown in FIG. 2.

[0021] The input receiving unit 102 receives input from a worker.

[0022] The terminal communication unit 103 communicates with the server 101 via the network N to transmit and receive data to and from the server 101 .

[0023] The display unit 104 displays various types of information, such as information accepted by the input accepting unit 102 and information received by the terminal communication unit 103.

[0024] The terminal log creating unit 105 creates a terminal log.

[0025] The terminal log is data showing the history of the processes and operations performed at the terminal 100 to process a task.

[0026] (Functional configuration of server 101) The server 101 supports the processing of work using the terminal 100 by communicating with the terminal 100 via the network N. The server 101 also generates evaluation data including evaluation results for the evaluation target based on the terminal log.

[0027] Here, the evaluation target may be set by the user, and is specified by, for example, a target task and a target subject.

[0028] The target work is a type of work to be evaluated, and is set by the user from among the works performed by each of the groups A to C. The target work corresponds to the first work.

[0029] The target entity is an entity that is the subject of evaluation and is associated with an organization (first organization). For example, the target entity may be the organization itself, a terminal managed by the organization, or a worker belonging to the organization.

[0030] As shown in FIG. 3, the server 101 functionally includes a terminal management unit 106, a log collection unit 107, and an activity evaluation unit 108.

[0031] The terminal management unit 106 performs a login process to the terminal 100. The terminal management unit 106 also supports the processing of tasks using the terminal 100.

[0032] In detail, as shown in FIG. 4, the terminal management unit 106 functionally includes a worker storage unit 109, a login processing unit 110, a work flow storage unit 111, and a screen transmission unit 112.

[0033] The worker storage unit 109 is a storage unit in which worker data 109a is stored.

[0034] The worker data 109a is data related to a worker. The workers related to the worker data 109a are people who belong to the organizations A to C managed by the server 101.

[0035] For example, as shown in FIG. 5, in worker data 109a, a worker ID (identifier), a group ID, a password, and authority are associated with each other.

[0036] The worker ID is information for identifying a worker, and in the worker data 109a shown in FIG. 5, "A001", "A005", and the like are given to the workers.

[0037] The organization ID is information for identifying organizations A to C. In the worker data 109a shown in FIG.

[0038] The password is a password for the worker to log in to the terminal 100. It is preferable that the password is appropriately set in advance.

[0039] The authority is information indicating the authority regarding the work.

[0040] In the worker data 109a shown in Fig. 5, either "report acceptance" or "approval" is set as the authority. "Report acceptance" indicates the authority to accept reports, which is the authority to accept reports from residents at a counter or the like. "Approval" indicates the authority to make decisions by checking whether or not there are any defects in the received report and judging it.

[0041] In the worker data 109a, a worker ID, the organization ID of one of organizations A to C to which the worker identified thereby belongs, a password for the worker to log in to the terminal 100, and the authority of the worker are associated with each other.

[0042] In the worker data 109a shown in FIG. 5, for example, a worker ID "A005", a group ID "A" corresponding to group A, a password "123456", and an authority "Approval" corresponding to the decision-making authority are associated with each other.

[0043] This indicates that the worker corresponding to the worker ID "A005" belongs to organization A, can log in to the terminals 100_a1 to 100_a3 using the password "123456," and has the authority to make decisions.

[0044] In addition, approval is usually performed by a superior of the worker who handles the process at the counter in the back yard, etc., and a person who has approval authority may also have notification acceptance authority. In such a case, in the worker data 109a, information indicating the multiple authorities of "approval" and "notification acceptance" may be set as "authority."

[0045] Referring again to FIG. The login processing unit 110 communicates with the terminal 100 via the network N to perform a login process to the terminal 100 .

[0046] In detail, when the login processing unit 110 acquires from the terminal 100 the worker ID and password input from the input receiving unit 102, the login processing unit 110 refers to the worker data 109a and determines whether or not to permit the login. For example, if the worker ID and password acquired from the terminal 100 match those associated in the worker data 109a, the login processing unit 110 permits the login, and does not permit the login in other cases.

[0047] If the login processing unit 110 determines that the login is permitted, it instructs the screen transmission unit 112 to transmit predetermined screen information to the terminal 100. If the login processing unit 110 determines that the login is not permitted, it notifies the terminal 100 from which the login was attempted of the determination result. Upon receiving this notification, the terminal 100 prompts the worker to, for example, re-enter the worker ID and password.

[0048] The workflow storage unit 111 is a storage unit in which workflow data 111a is stored.

[0049] The workflow data 111a is data showing the workflow for each type of work. In the workflow data 111a, a work ID, a process ID, a person in charge's authority, work content, and a screen ID are associated with each other, as shown in an example in FIG.

[0050] The task ID is information for identifying the type of task. In the workflow data 111a shown in Fig. 6, the task ID includes "transfer-out" indicating a transfer-out task and "transfer-in" indicating a transfer-in task.

[0051] A process ID is information for identifying each process that constitutes a task of a type corresponding to the associated task ID. In the workflow data 111a shown in FIG. 6, "Process 1" to "Process 7" are set for each of the task ID "Transfer-out" and task ID "Transfer-in." The processes "Process 1" to "Process 7" correspond to each of Process 1 to Process 7 that are performed in order to process each task.

[0052] The process ID associated with the work ID may correspond to the number of processes constituting the type of work corresponding to the work ID, and may be one or more.

[0053] The authority to take charge is information indicating the authority required to take charge of the process corresponding to the task ID and process ID associated therewith.

[0054] Here, "a process corresponding to a work ID and a process ID" refers to a process that corresponds to a process ID associated with the work ID, among the processes that make up the type of work that corresponds to the work ID.

[0055] In the workflow data 111a shown in FIG. 6, for example, the task ID "transfer" and task IDs "step 1" to "step 5" are associated with the authority of responsibility "notification acceptance." This means that workers in charge of steps 1 to 5 included in the transfer-out task need the authority to accept notifications. Also, for example, the task ID "transfer" and task IDs "step 6" to "step 7" are associated with the authority of responsibility "approval." This means that workers in charge of steps 6 to 7 included in the transfer-out task need the authority to approve.

[0056] The work content is information that indicates the work content of the process corresponding to the work ID and process ID associated therewith.

[0057] In the workflow data 111a shown in FIG. 6, for example, the work ID “Transfer” and the work IDs “Step 1” to “Step 7” are each associated with the following work contents: “Designation of type of work with authority,” “Search for target person,” “Verification of required documents,” “Identity verification,” “Acceptance,” “Designation of type of work,” and “Approval.”

[0058] The screen ID is information for identifying a screen displayed on the terminal 100 for processing a process corresponding to the task ID and process ID associated with the screen ID. In this embodiment, the screen ID can be used to identify a screen (operation screen) for processing each process constituting each job.

[0059] Referring again to FIG. The screen transmission unit 112 transmits screen information including an operation screen to the terminal 100 .

[0060] In detail, for example, the screen transmission unit 112 holds in advance screen information associated with a screen ID, and transmits to the terminal 100 screen information according to the type and step of the work to be processed in the terminal 100.

[0061] Referring again to FIG. The log collection unit 107 creates and stores a work log for each task based on the terminal log created by the terminal log creation unit 105. The work log is a log related to a task, and is data including, for example, a history of processes and operations performed by the terminal 100 to process a step included in the task.

[0062] The work log includes a log for each process. The work log also includes the work time required to complete the entire work or time information at which the work time is obtained (in this embodiment, the start time and end time of the entire work), and the work time required to complete each step or time information at which the work time is obtained (in this embodiment, the start time and end time of each step).

[0063] In detail, as shown in FIG. 7, log recorder 107 functionally includes terminal log acquisition unit 113, work log storage unit 114, merger rule storage unit 115, merger determination unit 116, and log generation unit 117.

[0064] The terminal log acquisition unit 113 acquires the terminal log created in the terminal 100 from the terminal 100 via the network N.

[0065] The work log storage unit 114 is a storage unit in which the work logs of a plurality of organizations A to C are stored.

[0066] The combination rule storage unit 115 is a storage unit in which combination rule data 115a is stored.

[0067] The merge specification data 115a is data that defines rules for merging a plurality of terminal logs.

[0068] In the merge specification data 115a, the acquired log and the log to be merged are associated with each other, as shown in an example in Fig. 8. Each of the acquired log and the log to be merged is data for specifying the type and process of the work.

[0069] The associated acquired log and the log to be combined indicate that the terminal log of the work type and process identified by the acquired log is combined with the work log of the work type and process identified by the log to be combined.

[0070] For example, the processes identified by the associated acquisition log and the linked target are processes included in the same type of work, and the process identified by the acquisition log is a downstream process in that work than the process identified by the linked target.

[0071] By referring to such merge specification data 115a, even if the steps included in a job are processed by different workers or terminals 100, a unified work log can be created for the entire job.

[0072] Referring again to FIG. When the terminal log acquisition unit 113 acquires the terminal log, the merge determination unit 116 refers to the merge specification data 115a and determines whether or not there is a merge target.

[0073] In detail, the merge determination unit 116 determines whether there is a merge target based on the type and step of the work in the acquired terminal log and the type and step of the work specified by the acquired log in the merge specification data 115a.

[0074] For example, if the type and process of the work in the acquired terminal log are included in the type and process of the work specified by the acquired log in the merge specification data 115a, it is determined that there is a merge target. Also, if the type and process of the work in the acquired terminal log are not included in the type and process of the work specified by the acquired log in the merge specification data 115a, it is determined that there is no merge target.

[0075] The log generating unit 117 generates a work log based on the terminal log acquired by the terminal log acquiring unit 113 and the determination result by the combination determining unit 116. Then, the log generating unit 117 stores the generated work log in the work log storage unit 114.

[0076] Referring again to FIG. The task evaluation unit 108 generates evaluation data including an evaluation result for the evaluation target based on the task log. The evaluation data according to this embodiment includes an evaluation result regarding the task efficiency of the evaluation target.

[0077] In detail, as shown in FIG. 9, the activity evaluation unit 108 includes an evaluation target receiving unit 118 , a criteria acquiring unit 119 , an evaluation target log acquiring unit 120 , an evaluation data generating unit 121 , and an evaluation unit 122 .

[0078] The evaluation target receiving unit 118 receives the designation of the evaluation target input by the user. In particular, the evaluation target receiving unit 118 receives the designation of the target work and the target subject input by the user.

[0079] The reference acquisition unit 119 acquires reference data obtained by performing statistical processing on the statistical processing log. The statistical processing log is a work log related to the target work, and includes, for example, work logs related to the target work performed by each of the terminals 100 of the multiple organizations A to C.

[0080] In detail, the reference acquisition unit 119 acquires a work log related to the target work as a statistical processing log from the work log storage unit 114, and acquires reference data by performing statistical processing on the statistical processing log. Note that reference data obtained by performing statistical processing on the statistical processing log may be prepared in advance and stored in the storage unit, and the reference acquisition unit 119 may acquire the prepared reference data from the storage unit.

[0081] The statistical processing of the statistical processing log is, for example, a process of calculating the number of statistical processing logs. Also, the statistical processing of the statistical processing log is, for example, a process of calculating an average time of the required time, a process of calculating the shortest time of the required time, a process of calculating a distribution of the required time, and a process of calculating a required time within a predetermined range of deviation values ​​in the distribution, based on the statistical processing log.

[0082] The required time is, for example, at least one of the task time required to process the target task and the task time required to process each step that constitutes the target task. That is, the reference acquisition unit 119 acquires reference data obtained by performing statistical processing on the task time included in the statistical processing log.

[0083] The evaluation target log acquisition unit 120 acquires an evaluation target log. The evaluation target log is a work log related to a target work in an organization (first organization) related to the target subject. In this embodiment, the evaluation target log is acquired by the evaluation target log acquisition unit 120 from the work log storage unit 114. Note that the evaluation target log may be included in the statistical processing log or may be excluded from the statistical processing log.

[0084] The evaluation data generating unit 121 generates evaluation data for evaluating the evaluation target based on the evaluation target log acquired by the evaluation target log acquiring unit 120.

[0085] In detail, for example, the evaluation data generating unit 121 obtains the work time required to process the target work in the work log related to the target subject based on the evaluation target log, and the time required to process each step constituting the target work. That is, the evaluation data generating unit 121 generates evaluation data based on the work time included in the evaluation target log.

[0086] When a plurality of work logs related to the target subject are included in the evaluation target log, the evaluation data generating unit 121 may perform statistical processing on the plurality of evaluation target logs.

[0087] In this case, the statistical processing of the evaluation target log is, for example, a process of calculating the number of logs for statistical processing. The statistical processing of the evaluation target log is, for example, a process of calculating the average time required based on the evaluation target log, a process of calculating the shortest time required, a process of calculating the distribution of the required times, and a process of calculating the required times within a predetermined range of deviation values ​​in the distribution. The statistical processing of the evaluation target log may include a process of calculating the longest time required.

[0088] The evaluation unit 122 generates evaluation data including an evaluation result for the evaluation target, using the reference data acquired by the reference acquisition unit 119 and the evaluation data generated by the evaluation data generation unit 121. That is, the evaluation data includes a result of evaluation of the entire target work performed by the target subject.

[0089] In detail, for example, the evaluation unit 122 generates the evaluation data by using the operation times included in the reference data and the evaluation data. The evaluation data also includes the results of evaluation associated with the workflow by including the results of evaluation of each process performed by the subject.

[0090] (Physical configuration of terminal 100 and server 101) From here, the physical configuration of the terminal 100 and the server 101 will be explained. Each of the terminal 100 and the server 101 physically comprises a bus 1010, a processor 1020, a memory 1030, a storage device 1040, a network interface 1050, and a user interface 1060, as shown in FIG.

[0091] The bus 1010 is a data transmission path for transmitting and receiving data among the processor 1020, the memory 1030, the storage device 1040, the network interface 1050, and the user interface 1060. However, the method of connecting the processor 1020 and the like to each other is not limited to a bus connection.

[0092] The processor 1020 is implemented by a central processing unit (CPU) or a graphics processing unit (GPU).

[0093] The memory 1030 is a main storage device realized by a RAM (Random Access Memory) or the like.

[0094] The storage device 1040 is an auxiliary storage device realized by a hard disk drive (HDD), a solid state drive (SSD), a memory card, a read only memory (ROM), or the like.

[0095] The storage devices 1040 of the terminal 100 and the server 101 respectively realize the memory units of the terminal 100 and the server 101 .

[0096] Furthermore, the storage device 1040 of the terminal 100 and the server 101 stores program modules for implementing each of the respective functional units. The processor 1020 loads each of these program modules onto the memory 1030 and executes them, thereby implementing each of the functional units corresponding to the program modules.

[0097] The network interface 1050 of the terminal 100 and the server 101 is an interface for connecting the terminal 100 and the server 101, respectively, to a network N that is configured using a wired or wireless network or a combination of these.

[0098] The user interface 1070 of the terminal 100 and the server 101 is an interface through which information is input by the user and an interface that presents information to the user, and includes, for example, a mouse, keyboard, touch sensor, camera, scanner, etc. for user input, and an LCD display for displaying information.

[0099] In this way, the functions of the terminal 100 and the server 101 can be realized by the physical components working together to execute a software program. Therefore, the present invention may be realized as a software program (also called a "software program program") or as a non-transitory storage medium on which the program is recorded.

[0100] From here, the operation of the work management system according to the present embodiment will be described with reference to the drawings.

[0101] (Terminal Processing) 11 is a flowchart showing an example of terminal processing according to the present embodiment. The terminal processing is processing for the terminal 100 to create a terminal log and transmit the created terminal log to the server 101. The terminal processing is performed after a worker logs in to the terminal 100. For example, the login processing unit 110 performs login processing based on a worker ID and password inputted into the terminal 100 by the worker, thereby enabling the worker to log in to the terminal 100.

[0102] The input reception unit 102 receives the type of work input by the user to the work selection screen SC11 (see Figs. 12 and 14 showing a first example of screen transitions) (step S101). The work selection screen SC11 is an operation screen for the user to select the type of work. By performing step S101, the target work is set.

[0103] Here, Fig. 12 shows an example of screen transitions on the terminal 100 when a worker with notification acceptance authority logs in to the terminal 100 and processes a transfer-out operation. Fig. 14 shows an example of screen transitions on the terminal 100 when a worker with decision-making authority logs in to the terminal 100 and processes a transfer-out operation.

[0104] In detail, when the login is successful, the screen transmission unit 112 of the server 101 transmits screen information showing a work selection screen SC11 to the terminal 100. Here, the work selection screen SC11 is an operation screen for processing the first step performed after login, regardless of the type of work or the authority of the worker who has logged in, as shown in the flow data 111a in Fig. 6.

[0105] When the display unit 104 acquires the screen information via the device communication unit 103, it displays the work selection screen SC11 indicated by the screen information. The user inputs the type of work to be processed by selecting one of the buttons included in the work selection screen SC11.

[0106] At this time, the input receiving unit 102 holds a terminal log including a history of processes and operations at the logged-in terminal 100 .

[0107] Here, a terminal log is stored for the processing of step 1 or step 6 included in the input type of work. Whether it is step 1 or step 6 is determined according to the authority associated with the worker ID of the worker who logged in in worker data 109a. If the logged in worker has the authority to accept notifications, a terminal log for step 1 is stored, and if the logged in worker has the authority to make decisions, a terminal log for step 6 is stored.

[0108] This terminal log includes the time (date and time) when the work selection screen SC11 was displayed as the start time of process 1 or process 6, and the time (date and time) when the work type was accepted in step S101 as the end time of process 1 or process 6.

[0109] Furthermore, the terminal log includes the type of work that was input, the worker ID of the worker, the organization ID of the organization to which the worker belongs, and a terminal ID for identifying the terminal 100 used by the worker.

[0110] Referring again to FIG. When a type of work is specified in step S101, terminal 100 repeats steps S103 to S105 for all steps corresponding to the specified type of work and the authority of the logged-in worker (loop A; step S102).

[0111] In loop A, when the display unit 104 acquires screen information from the screen transmission unit 112 via the terminal communication unit 103, the display unit 104 displays an operation screen indicated by the acquired screen information (step S103).

[0112] In detail, for example, the screen transmission unit 112 refers to the workflow data 111a and transmits screen information indicating an operation screen for processing the next step in the type of work specified in step S101 to the terminal 100. When the display unit 104 acquires this screen information via the terminal communication unit 103, it displays the operation screen indicated by the screen information.

[0113] 12, for example, when a "Transfer" button corresponding to the transfer-out operation is selected in step S101, the screen transmission unit 112 receives a notification that the transfer-out operation has been selected via the network N. In response to this notification, the screen transmission unit 112 refers to the work flow data 111a shown in FIG. 6, and transmits to the terminal 100 screen information showing a target person search screen SC12 identified by a screen ID "SC12" associated with the "Step 2" to be performed next.

[0114] The target person search screen SC12 is a screen for searching for a person to process a specified type of work, and the person to process the work is set by inputting information on this screen. For example, if a moving-out work is set as the target work in step S101, the target person search screen SC12 functions as a screen for setting the resident who will move out.

[0115] Referring again to FIG. The input receiving unit 102 receives user input on the operation screen displayed in step S103, and holds operation information including the received input and the time of input. When the process corresponding to the displayed operation screen is completed, the input receiving unit 102 receives a process end instruction from the worker (step S104). The process end instruction is an instruction to end the process.

[0116] For example, when the subject search screen SC12 shown in FIG. 12 is displayed in step S103, the input receiving unit 102 receives the number of subjects and the names of the subjects input by the worker according to the subject search screen SC12.

[0117] Then, when the input is completed, the "Search" button is pressed, whereby the input receiving unit 102 receives a process end instruction from the worker.

[0118] When the "Search" button is pressed, the terminal 100 should inquire of the server that manages the residents of the group and confirm that the person corresponding to the entered target name is registered. If the person is registered, the process proceeds to the next step, and if the person is not registered, the terminal 100 should prompt the user to re-enter the target name, for example by displaying a target search screen SC12 along with a message to that effect.

[0119] Referring again to FIG. The input receiving unit 102 further holds the work log of the process processed in the immediately preceding steps S103 and S104 as a terminal log (step S105). The terminal log held in step S105 includes, for example, the start time and end time of the process. The start time of the process is the time (date and time) when step S103 was performed, and the end time is the time (date and time) when the process end instruction was received in step S104 and it became possible to proceed to the next process.

[0120] The terminal log also includes information received by the input receiving unit 102 during steps S103 to S104. For example, the terminal log of a process corresponding to the target person search screen SC12 includes the number of targets and the target person names input to the target person search screen SC12. The work log of the process also includes the time (date and time) when these were input.

[0121] Furthermore, the terminal log includes error information detected by the input receiving unit 102 in each step in the processing of the target task.

[0122] For example, assume that a transfer-out operation is set in step S101 by a worker who has logged in with notification acceptance authority, and steps S104 to S105 corresponding to the target person search screen SC12 are performed. In this case, steps S103 to S105 corresponding to steps 3 to 5 included in the transfer-out operation are successively executed (loop A; step S102).

[0123] As a result, in step S103, the display unit 104 sequentially displays a required document confirmation screen SC13, an identity confirmation screen SC14, and an acceptance screen SC15, as shown in FIG.

[0124] Here, the identity verification screen SC14 includes a “save data” button. When this button is pressed, data including documents for identity verification is generated by a camera or the like and stored in the terminal 100 or the server 101.

[0125] After receiving the input for each operation screen, the input receiving unit 102 receives a process end instruction from the worker in step S104. In the example shown in Fig. 12, the input receiving unit 102 receives the process end instruction by receiving an input of a button corresponding to the start point of the arrow connecting each operation screen.

[0126] In step S105, the input receiving unit 102 further holds a terminal log of the process carried out in the immediately preceding steps S103 and S104.

[0127] The terminal log creating unit 105 creates a terminal log by combining the terminal logs of the respective processes held by the input receiving unit 102 in steps S101 to S104 (step S106).

[0128] The terminal log generated in step S106 is data including a history of processes and operations performed on the terminal 100 used by the worker.

[0129] FIG. 13 illustrates a first example of a terminal log according to the present embodiment.

[0130] The terminal log shown in Figure 13 is an example of a terminal log created in response to processing and operations performed by a worker with worker ID "A001" on terminal 100_a1 with terminal ID "a1" by referring to the series of operation screens SC11 to SC15 shown in Figure 12.

[0131] The terminal log shown in FIG. 13 includes a task type, a target person ID, a processing amount, an organization ID, a worker ID, a terminal ID, and history information.

[0132] The task type included in the terminal log is information indicating the type of task related to the terminal log, and corresponds to the task ID.

[0133] The subject ID included in the terminal log is information for identifying the subject of the work related to the terminal log, and in this embodiment, indicates the subject's name. Note that the subject ID may be the subject's personal number, etc.

[0134] The processing amount included in the terminal log is information indicating the amount processed in the task related to the terminal log, and in this embodiment indicates the number of people involved in the task.

[0135] The organization ID included in the terminal log is the organization ID of the organization that manages the terminal 100 that was used to process the task related to the terminal log.

[0136] The worker ID included in the terminal log is a worker ID corresponding to the worker who performed the work related to the terminal log.

[0137] The terminal ID included in the terminal log is the terminal ID corresponding to the terminal 100 used to process the task related to the terminal log.

[0138] The history information included in the terminal log indicates the history of the processes and operations performed at the terminal 100 to process the steps included in the work related to the terminal log.

[0139] The terminal log history information shown in Fig. 13 is an example of history information related to work performed by a worker whose authority is the report reception authority. In this history information, the process ID, work date, start time, end time, correction information, and system error information are associated with each other.

[0140] The process ID is a process ID corresponding to the process included in the work related to the terminal log. The process IDs shown in Fig. 13 are the process IDs "Process 1" to "Process 5" corresponding to the notification acceptance authority among the processes constituting the transfer-out work.

[0141] The work date, start time, and end time indicate the work date, start time, and end time, respectively, when the process corresponding to the associated process ID was processed.

[0142] The correction information is information about a correction made by an operator in processing a process corresponding to the associated process ID. The correction information shown in FIG. 13 includes "p001" associated with the process ID "Process 1." "p001" is an example of a code that is predetermined according to the content of the correction. Such correction information indicates that a correction has been made by an operator and the content of the correction.

[0143] In addition, in the terminal log shown in Fig. 13, "-" indicates a blank. Therefore, in this terminal log, it is shown that no correction by the worker occurred in the processes with the process IDs "Process 2" to "Process 5".

[0144] The system error information is information related to a system error that occurred during processing of a process corresponding to the associated process ID.

[0145] In the terminal log shown in FIG. 13, all the system error information is blank, which indicates that no system errors occurred in any of the processes that were processed when the terminal log was created.

[0146] When a system error occurs, for example, in the terminal log, a code that is predetermined according to the system error may be associated with a process ID corresponding to the process in which the system error occurred, making it possible to indicate the process in which the system error occurred and the content of the system error.

[0147] Referring again to FIG. Terminal log creating section 105 transmits the terminal log created in step S106 to server 101 (step S107), and ends the terminal processing.

[0148] Here, the transfer-out work is carried out by a worker with decision-making authority for the processes corresponding to process IDs "Process 6" to "Process 7", following the processes corresponding to process IDs "Process 1" to "Process 5". The terminal processing for processing the processes corresponding to these process IDs "Process 6" to "Process 7" will be explained with reference to the drawings. In the following explanation, for the sake of simplicity, mainly differences from the terminal processing for processing the processes corresponding to process IDs "Process 1" to "Process 5" will be explained.

[0149] FIG. 14 shows an example of screen transitions on terminal 100 when a worker with decision-making authority processes the steps that correspond to the step IDs "Step 6" to "Step 7" corresponding to the decision-making authority among the steps that constitute the transfer-out work, with the transfer-out work being the target work.

[0150] That is, referring to the workflow data 111a in Fig. 6, the process IDs "Process 6" to "Process 7" are associated with the screen IDs "SC11" and "SC16". Therefore, in terminal processing when a transfer-out work is performed by a worker with decision-making authority, the work selection screen SC11 is displayed on the display unit 104 as an operation screen identified by the screen ID "SC11". The input reception unit 102 receives the type of work according to the work selection screen SC11 (step S101) and retains a terminal log related to the processing of process 6. The terminal log retained here is the terminal log described above for the example of process 1, but with the terminal log replaced with process 6.

[0151] Next, the display unit 104 displays the decision screen SC16 as an operation screen (step S103). When either the "Approve" or "Return" button included in the decision screen SC16 is pressed, the input receiving unit 102 receives a process end instruction (step S104).

[0152] "Approve" is pressed when there are no defects in the received content and the notification is approved.

[0153] "Return" is pressed when an error is found in the accepted content. In this case, the input receiving unit 102 receives the process and the details of the error that are input to the "Process with Error" column and the "Details of Error" column of the approval screen SC16, respectively.

[0154] In the example of the approval screen SC16 shown in FIG. 14, a defect has been found in the identity verification step (step with step ID "Step 4") in that the data including the identity verification document is unclear.

[0155] The terminal log information does not have to include error information. Even if the terminal log information includes error information, the error information may be at least one of correction information, defect specification information, and system error information.

[0156] The terminal log creating unit 105 creates a terminal log by combining the terminal logs of the respective processes held by the input receiving unit 102 in steps S101 to S104 (step S106).

[0157] FIG. 15 shows a second example of the terminal log according to the present embodiment.

[0158] The terminal log shown in Figure 15 is an example of a terminal log created in response to processing and operations performed by a worker with worker ID "A005" on terminal 100_a2 with terminal ID "a2" by referring to the series of operation screens SC11, SC16 shown in Figure 14.

[0159] The contents of each item included in the terminal log shown in FIG. 15 are generally similar to the corresponding items in the terminal log shown in FIG. 13, except for the history information.

[0160] The terminal log history information shown in Fig. 15 is an example of history information corresponding to a process performed by a worker whose authority is decision-making authority. In addition to the same items as those in the history information shown in Fig. 13, this history information is associated with defect identification information.

[0161] The defect specification information is information for specifying a defect that was found in the decision-making process of the process ID "Process 7", and includes information indicating the process in which the defect was found and the details of the defect. The defect specification information is set when the defect is found.

[0162] In the defect identification information shown in Fig. 15, the defect identification information "Process 4 (unclear data)" is associated with the process ID "Process 7". This corresponds to the discovery of a defect in the identity verification process (Process ID "Process 4") in the decision making process with the process ID "Process 7", as described above with reference to Fig. 14.

[0163] By carrying out such terminal processing, it is possible to create a terminal log relating to the steps that have been processed at the terminal 100 among the steps included in the type of work specified by the logged-in worker at the terminal 100.

[0164] (Log collection process) 16 is a flowchart showing an example of the log collection process according to the present embodiment. The log collection process is a process for creating and storing an operation log based on the terminal logs of the organizations A to C managed by the server 101.

[0165] The log collection process is preferably performed at a predetermined time, for example, when the terminal log transmitted in step S107 is acquired.

[0166] The terminal log acquisition unit 113 acquires the terminal log transmitted in step S107 from the terminal 100 via the network N (step S201).

[0167] The merge determination unit 116 refers to the merge specification data 115a and determines whether or not there is a merge target in the terminal log acquired in step S201 (step S202).

[0168] In detail, the merge determination unit 116 determines that there is a merge target when the acquired log of the merge specification data 115a contains a log that matches the type of work and the process included in the terminal log acquired in step S201. Also, the merge determination unit 116 determines that there is no merge target when the acquired log of the merge specification data 115a does not contain a log that matches the type of work and the process included in the terminal log acquired in step S201.

[0169] For example, the terminal log shown in Fig. 13 includes logs related to the process IDs "Process 1" to "Process 4" of the work ID "Transfer-out". The process IDs "Process 1" to "Process 4" of the work ID "Transfer-out" are not included in the acquired log of the merge specification data 115a shown in Fig. 8. Therefore, when the terminal log shown in Fig. 13 is acquired in step S201, the merge determination unit 116 refers to the merge specification data 115a shown in Fig. 8 and determines that there are no merge targets.

[0170] Also, for example, the terminal log shown in Fig. 15 includes logs related to the process IDs "Process 6" to "Process 7" of the work ID "Transfer-out". The process IDs "Process 6" to "Process 7" of the work ID "Transfer-out" are included in the acquired log of the merge specification data 115a shown in Fig. 8. Therefore, when the terminal log shown in Fig. 15 is acquired in step S201, the merge determination unit 116 determines that there is a merge target by referring to the merge specification data 115a shown in Fig. 8.

[0171] Referring again to FIG. If it is determined that there is a work log to be combined (step S202; Yes), log generating unit 117 acquires the work log to be combined from work log storage unit 114 (step S203).

[0172] In detail, for example, the log generating unit 117 identifies a log to be combined that is associated in the combination specification data 115a with an acquired log that matches the type and step of the work included in the terminal log acquired in step S201. The log generating unit 117 acquires from the work log storage unit 114 a work log that includes the type and step of the work identified by the identified log to be combined.

[0173] The log generating unit 117 identifies, from among the acquired work logs, work logs having the same work type and target person ID as the terminal log acquired in step S201, as work logs to be combined.

[0174] If there are multiple work logs obtained from the work log memory unit 114 that have the same work type and target ID as the terminal log obtained in step S201, the most recently created work log may be identified as the work log to be merged.

[0175] If it is determined that there are no items to be combined (step S202; No), or after step S203, the log generation unit 117 generates a work log (step S204) and stores the generated work log in the work log memory unit 114 (step S205), whereby the log generation unit 117 terminates the log collection process.

[0176] In detail, for example, the work log may have a format different from that of the terminal log, as described later with reference to Figures 17A and 17B. In step S204, which is performed when it is determined that there is no target to be combined (step S202; No), the log generating unit 117 generates a work log by appropriately changing the format of the terminal log acquired in step S201.

[0177] If the format of the terminal log is not changed, step S204 may be omitted if it is determined that there is no target to be combined.

[0178] This allows the server 101 to generate and store an operation log corresponding to the terminal log created in each of the terminals 100 managed by the organizations A to C.

[0179] In addition, when processing a task that includes multiple steps shared by different workers, a work log corresponding to a terminal log that corresponds to a portion of the multiple steps included in the task (for example, an upstream step portion) can also be generated and stored in server 101.

[0180] In step S204 performed after step S203, log generation unit 117 generates a work log by combining the terminal log acquired in step S201 and the work log acquired in step S203.

[0181] That is, the log generating unit 117 generates a statistical processing log by combining the logs of a series of steps that constitute the target work from the logs for each step acquired from the terminals 100 of the organizations A to C.

[0182] As shown in Figures 17A and 17B, the work log includes a work type, a target user ID, a processing amount, and history information. Figures 17A and 17B are diagrams showing an example of a work log according to the present embodiment, and are examples of a work log generated by combining the terminal logs shown in Figures 13 and 15.

[0183] The work type, subject ID, and processing amount included in the work log are common to the combined terminal log and work log, even if the work log is generated by combining the terminal log and the work log to be combined. Therefore, the work type, subject ID, and processing amount included in the work log are the same as the work type, subject ID, and processing amount included in the terminal log, respectively.

[0184] That is, the task type included in the work log is information indicating the type of task related to the work log, and corresponds to the task ID. The subject ID included in the work log is information for identifying the subject of the task related to the work log, and in this embodiment indicates the subject's name. The processing volume included in the work log is information indicating the volume to be processed in the task related to the work log, and in this embodiment indicates the number of subjects of the task.

[0185] The history information included in the work log indicates the history of processes and operations performed at one or more terminals 100 to process the steps included in the work related to the work log.

[0186] In the history information shown in FIGS. 17A and 17B, a process ID, a group ID, a worker ID, a terminal ID, a work date, a start time, an end time, correction information, defect information, and system error information are associated with each other.

[0187] If a work log is generated by combining a terminal log and a work log to be combined, the process ID included in the work log is the process ID included in the terminal log from which it was generated and the work log to be combined. If a work log is generated from only one terminal log, the process ID included in the work log is the process ID included in the terminal log from which it was generated.

[0188] The organization ID is the organization ID of the organization that manages the terminal 100 used when processing the process corresponding to the associated process ID.

[0189] The worker ID is a worker ID corresponding to a worker of a process corresponding to the associated process ID.

[0190] The terminal ID is a terminal ID corresponding to the terminal 100 used to process the process corresponding to the associated process ID.

[0191] The work date, start time, and end time indicate the work date, start time, and end time, respectively, when the process corresponding to the associated process ID was processed.

[0192] The correction information is information related to corrections made by an operator in the processing of a process corresponding to the associated process ID.

[0193] The defect information is information about a defect found in the processing of a process corresponding to the associated process ID, and indicates the process in which the defect was found and the content of the defect.

[0194] When the terminal log from which the work log was created contains deficiency-specific information, the deficiency information is set based on the deficiency-specific information.

[0195] For example, the terminal log shown in FIG. 15 includes deficiency identification information, which indicates that a deficiency called "unclear data" was found in the identity verification process (process ID "Process 4"). In the log information, the content of the deficiency is set in the deficiency information associated with the process identified by the deficiency identification information. In the log information shown in FIG. 17B, an example is shown in which the content of the deficiency is set by a predetermined code "q001", but the method of setting the content of the deficiency may be changed as appropriate. The deficiency information makes it possible to identify the process in which the deficiency was found and the content of the deficiency.

[0196] The system error information is information related to a system error that occurred during processing of a process corresponding to the associated process ID.

[0197] The correction information, deficiency information, and system error information contained in the work log are examples of error information contained in the work log, and the error information does not have to be included in the work log, and may be one or more of the correction information, deficiency information, and system error information.

[0198] In this way, when processing a task that includes multiple steps shared by different workers, the terminal log for a portion of the task (e.g., a downstream step portion) is combined with the task log for the other portion of the task (e.g., an upstream step portion) that has already been stored for the common task. This allows a task log for each task to be generated and stored in the server 101.

[0199] So far, the log collection process has been described. By performing the log collection process, the terminal logs created in the terminals 100 managed by the groups A to C managed by the server 101 can be collected and stored in the server 101 as an operation log.

[0200] In particular, by combining the terminal log and the work log, a work log including a series of steps some of which were processed by different workers or terminals 100 can be compiled into a single work log.

[0201] In the present embodiment, an example has been described in which, when tasks are processed by different workers and terminals 100, the workers and terminals 100 belong to the same organization. However, tasks may be processed by workers belonging to different organizations or terminals 100 managed by different organizations.

[0202] For example, it is conceivable that a moving-out operation and a moving-in operation can be managed as one operation related to a resident's change within a country. Even in such a case, by combining the processes processed by different organizations in a manner similar to the log collection process described above, a log of the operation including a series of processes related to a resident's change within a country can be generated as a single operation log and stored in the server 101. This makes it possible to evaluate operations processed by multiple organizations as an operation target.

[0203] (Work management processing) 18 is a flowchart showing an example of a work management process according to the present embodiment. The work management process generates evaluation data including an evaluation result regarding the work efficiency of an evaluation target based on the work logs of organizations A to C managed by server 101.

[0204] The work management process may be executed at an appropriate time after the end of the period to be evaluated, depending on the period from the start to the end of the period, which is determined appropriately.

[0205] Typically, the evaluation data is generated monthly, semi-annually, or annually. In the case where the evaluation data is generated monthly, for example, a predetermined day of each month may be specified as the end time of the target period, and the corresponding day of the previous month may be specified as the start time. In the case where the evaluation data is generated semi-annually or annually, for example, one or two predetermined days of each year may be specified as the end time of the target period, and the corresponding day one year or six months ago may be specified as the start time.

[0206] The evaluation target receiving unit 118 acquires a target task input by a user (step S301).

[0207] For example, the evaluation target receiving unit 118 acquires a moving-out operation or a moving-in operation as a work target based on an input from a user.

[0208] The criteria acquisition unit 119 acquires, from the work log storage unit 114, work logs related to the target work acquired in step S301, among the work logs included in the target period of evaluation, as logs for statistical processing (step S302).

[0209] For example, when a moving-out operation is acquired as the operation target in step S301, the criteria acquisition unit 119 acquires the operation logs related to the moving-out operation from among the operation logs stored in the operation log storage unit 114. As a result, the operation logs related to the moving-out operation processed in the target period by the groups A to C are acquired.

[0210] The reference acquisition unit 119 acquires reference data by performing statistical processing on the statistical processing log acquired in step S302 (step S303).

[0211] For example, assume that a work log related to the transfer-out work is acquired as a statistical processing log in step S302.

[0212] As the statistical processing in this case, for example, the criterion acquisition unit 119 obtains the number of statistical processing logs obtained in step S302. As a result, the number of transfer-out operations processed in the target period in the groups A to C is obtained.

[0213] As an example of statistical processing, the reference acquisition unit 119 obtains the work time (required time) required to process the transfer-out work from the start time and end time of the entire transfer-out work for each of the statistical processing logs obtained in step S302. Then, the reference acquisition unit 119 obtains, for the entire transfer-out work, the average required time, the shortest required time, the distribution of required times, and the range of required times within which the deviation value of the required times in the distribution is a predetermined range.

[0214] This makes it possible to calculate the average time required for all transfer operations processed by groups A to C during the target period, the time required for the most efficient processing, the distribution of times required, and the general time required to process transfer operations.

[0215] As an example of statistical processing, the reference acquisition unit 119 separates the statistical processing logs acquired in step S302 by processing amount. Then, for each of the statistical processing logs separated by processing amount, the reference acquisition unit 119 obtains the work time (required time) required for processing the transfer-out work for each processing amount from the start time and end time of the entire transfer-out work. As described above, the reference acquisition unit 119 obtains the average value, shortest time, distribution, and range of required time within a predetermined range of deviation value for the entire transfer-out work for each processing amount. That is, the reference acquisition unit 119 obtains reference data for each processing amount.

[0216] This makes it possible to determine the average time required, the time required when processing most efficiently, the distribution of required times, and the general time required to process transfer operations for all transfer operations processed by groups A to C during the target period, for each processing volume.

[0217] Furthermore, as a statistical process, for example, the reference acquisition unit 119 obtains the work time (required time) required to process each process constituting the transfer-out work from the start time and end time of each process for each statistical process log obtained in step S302. Then, similar to the case of the required time for the entire transfer-out work, the reference acquisition unit 119 obtains the average value, shortest time, distribution, and range of required time within a predetermined range of deviation for each process. That is, the reference acquisition unit 119 obtains reference data for each process.

[0218] This makes it possible to determine the average time required for each process that makes up the transfer-out work processed by groups A to C during the target period, the time required when the work is processed most efficiently, the distribution of times required, and the general time required to process the transfer-out work.

[0219] Furthermore, as a statistical process, for example, the reference acquisition unit 119 obtains the work time (required time) for each processing amount required for processing each process constituting the transfer-out work for each statistical process log divided by processing amount. Then, as described above, the reference acquisition unit 119 obtains the average value, shortest time, distribution, and required time range within a predetermined range of deviation value for each processing amount and each process.

[0220] This makes it possible to determine, for each process that makes up the transfer-out work processed by groups A to C during the target period, the average time required, the time required when processing is most efficient, the distribution of required times, and the general time required to process the transfer-out work, for each processing volume.

[0221] Furthermore, as a statistical process, for example, the reference acquisition unit 119 obtains the number of pieces of error information contained in each statistical process log, and the number of pieces of correction information, deficiency information, and system error information contained in the error information. Also, based on the error information contained in the statistical process log, the reference acquisition unit 119 obtains the number of pieces of error information, and the number of pieces of correction information, deficiency information, and system error information contained in the error information for each process, processing amount, and combination of process and processing amount that constitute the transfer-out work. In other words, the reference data includes the number of errors that occurred in relation to the target work.

[0222] This makes it possible to determine the number of errors (correction information, deficiency information, system error information, and the total of all of these) that occurred for the entire transfer-out work carried out by groups A to C during the target period, for each process, and for the entire transfer-out work for each process, and for each process.

[0223] The evaluation target receiving unit 118 acquires the target subject input by the user (step S304).

[0224] For example, the evaluation target receiving unit 118 acquires, based on the user's input, the group ID "A" corresponding to group A, the terminal ID "a1" corresponding to the terminal 100_a1, the worker ID "A001", and the like as task subjects. This allows the group A, the terminal 100_a1, and the worker corresponding to the worker ID "A001" to be identified as target subjects.

[0225] The evaluation target log acquisition unit 120 acquires, as an evaluation target log, the work log related to the target work of the target subject acquired in step S304 (step S305).

[0226] For example, assume that the moving-out task is acquired as the task target in step S301, and the organization A is acquired as the target subject in step S304. In this case, the evaluation target log acquisition unit 120 acquires the task logs related to the moving-out task and the organization A from the task log storage unit 114 as the evaluation target logs.

[0227] The evaluation data generating unit 121 generates evaluation data based on the evaluation target log acquired in step S305 (step S306).

[0228] For example, assume that in step S305, the work log related to the transfer operation and group A is acquired as the evaluation target log.

[0229] As an example of the statistical processing in this case, the evaluation data generating unit 121 finds the number of evaluation target logs acquired in step S305. This finds the number of transfer operations processed in the target period in group A.

[0230] As a statistical process, for example, the evaluation data generating unit 121 obtains the work time (required time) required to process the transfer-out work from the start time and end time of the entire transfer-out work for each of the evaluation target logs acquired in step S305. Then, the evaluation data generating unit 121 obtains, for the entire transfer-out work, the average required time, the shortest and longest required times, the distribution of required times, and the range of required times within which the deviation value of the required times in the distribution is a predetermined range.

[0231] This makes it possible to determine the average time required for all transfer operations processed by group A during the target period, the time required for the most efficient processing, the time required for the least efficient processing, the distribution of times required, and the general time required to process transfer operations.

[0232] As an example of statistical processing, the evaluation data generating unit 121 divides the evaluation target logs acquired in step S305 by processing amount. Then, for each of the evaluation target logs divided by processing amount, the evaluation data generating unit 121 calculates the work time (required time) required for processing the transfer-out work for each processing amount from the start time and end time of the entire transfer-out work. As described above, the evaluation data generating unit 121 calculates the average value, shortest time, longest time, distribution, and required time range in which the deviation value is a predetermined range for the entire transfer-out work for each processing amount. That is, the evaluation data generating unit 121 generates evaluation data for each processing amount based on the evaluation target logs.

[0233] This makes it possible to determine, for all transfer operations processed by group A during the target period, the average time required, the time required for the most efficient processing, the time required for the least efficient processing, the distribution of times required, and the general time required to process transfer operations for each processing volume.

[0234] Furthermore, as a statistical process, for example, the evaluation data generation unit 121 calculates the work time (required time) required to process each process constituting the transfer-out work from the start time and end time of each process for each of the evaluation target logs acquired in step S305. Then, similar to the case of the required time for the entire transfer-out work, the evaluation data generation unit 121 calculates the average value, shortest time, longest time, distribution, and range of required time within a predetermined range of deviation value for each process. That is, the evaluation data generation unit 121 generates evaluation data for each process related to the evaluation target based on the evaluation target log.

[0235] This makes it possible to determine, for each process that makes up the transfer-out work processed by group A during the target period, the average time required, the time required when the work is processed most efficiently, the time required when the work is processed least efficiently, the distribution of times required, and the general time required to process the transfer-out work.

[0236] Furthermore, as a statistical process, for example, the evaluation data generating unit 121 obtains the work time (required time) for each processing amount required to process each process constituting the transfer-out work for each evaluation target log divided by processing amount. Then, as described above, the evaluation data generating unit 121 obtains the average value, shortest time, longest time, distribution, and range of required time within a predetermined range of deviation value for each processing amount and each process.

[0237] This makes it possible to determine, for each process that makes up the transfer-out work processed by group A during the target period, the average required time, the required time when the work is most efficient, the required time when the work is least efficient, the distribution of required times, and the general required time for processing the transfer-out work, for each processing volume.

[0238] Furthermore, as a statistical process, for example, the evaluation data generation unit 121 obtains the number of pieces of error information contained in each of the logs to be evaluated, and the number of pieces of correction information, deficiency information, and system error information contained in the error information. Also, based on the error information contained in the logs to be evaluated, the evaluation data generation unit 121 obtains the number of pieces of error information, and the number of pieces of correction information, deficiency information, and system error information contained in the error information for each process, each processing amount, and each combination of process and processing amount that constitutes the transfer-out work. In other words, the evaluation data includes the number of errors that occurred in relation to the target work performed by the evaluation target.

[0239] This makes it possible to determine the number of errors (correction information, deficiency information, system error information, and the total of all of these) that occurred for the entire transfer-out work processed by Group A during the target period, for each process, and for the entire transfer-out work for each process, and for each process.

[0240] The evaluation unit 122 generates evaluation data based on the reference data acquired in step S303 and the evaluation data generated in step S306 (step S307). The evaluation unit 122 may output the generated evaluation data. The output may be transmission of the evaluation data to the terminal 100 or printing of the evaluation data on paper or the like.

[0241] An example of the evaluation data according to this embodiment is shown in Figures 19A and 19B. The evaluation data shown in Figures 19A and 19B is an example of the evaluation data in the case where the transfer work and group A are the evaluation targets.

[0242] The evaluation data includes a summary (see FIG. 19A) indicating an overall evaluation of the transfer-out work, and a detailed evaluation (see FIG. 19B) indicating evaluations of each part of the transfer-out work.

[0243] 19B, the detailed evaluation is classified by the amount of processing, and the corresponding post-statistical processing value is associated with the detailed evaluation. That is, the evaluation unit 122 generates evaluation data for each amount of processing by using the reference data and the evaluation data.

[0244] As can be seen by referring to the examples of Figures 19A and 19B, the evaluation unit 122 generates evaluation data in which the corresponding values ​​after statistical processing of the reference data and the evaluation data are associated with each other. By referring to such evaluation data, it is possible to easily grasp the degree of the task efficiency of the target subject in the target task and take measures to improve the task efficiency. Therefore, it is possible to support the improvement of task efficiency.

[0245] In the examples shown in FIGS. 19A and 19B, the numbers of transfer-out operations processed in the target period are associated with each of the organizations A to C and the organization A.

[0246] In addition, the time required for the group A to complete each process is associated with the average time required for the groups A to C to complete each process. That is, the evaluation unit 122 generates evaluation data for each process related to the evaluation target by using the reference data and the evaluation data for which the processes are common.

[0247] By referring to such evaluation data, it is possible to easily grasp the degree of the subject's work efficiency in each process of the target work and take measures to improve the work efficiency for each process, thereby making it possible to support the improvement of work efficiency.

[0248] Although not shown, the time required for the group A to complete the entire transfer-out operation may be associated with the average time required for the groups A to C to complete the operation.

[0249] Furthermore, the evaluation data generating unit 121 compares the difference between the corresponding values ​​after statistical processing between the reference data and the evaluation data with a predetermined threshold value or range, and attaches warning information based on the comparison result.

[0250] For example, in Fig. 19A, process 4 is hatched. This indicates that warning information has been added in response to the difference (deviation) between the time required to process process 4 by group A and the average time required to process process 4 by groups A to C being equal to or greater than a threshold value.

[0251] 19B, process 4, which has a processing volume of 2 people, is hatched. This indicates that, in a transfer operation in which the processing volume is 2 (people), the difference (deviation) between the time required for group A to complete process 4 and the average time required for groups A to C to complete process 4 is equal to or greater than a threshold, and thus warning information is attached.

[0252] By referring to such warning information, the subject can easily grasp the part of the target task where the task efficiency is poor and take measures to improve the task efficiency. Therefore, it is possible to support the improvement of task efficiency.

[0253] 19A shows an example that includes the total number of errors in group A and the number of errors for each process. In addition, below the total number of errors in group A, the average value obtained by dividing the total number of errors that occurred in groups A to C by the number of groups is included in parentheses, which corresponds to the total number of errors in group A.

[0254] Below the number of errors per process, the average number of errors per process that occurred in groups A to C divided by the number of groups is included in parentheses, which corresponds to the number of errors per process in group A.

[0255] That is, the evaluation unit 122 generates the evaluation data using the number of errors contained in each of the reference data and the evaluation data.

[0256] Although not shown, the evaluation data may be generated using the number of errors categorized by type of error, such as corrections, deficiencies, and system errors.

[0257] By referring to the evaluation data including the number of errors, it is possible to grasp the occurrence status of errors and take measures to reduce errors, thereby helping to improve work efficiency.

[0258] Although one embodiment and modified examples of the present invention have been described above, the present invention is not limited to these. For example, the present invention also includes a form in which some or all of the embodiment and modified examples described so far are appropriately combined, and a form in which the form is appropriately modified.

[0259] One or all of the above-described embodiments can be described as, but are not limited to, the following supplementary notes.

[0260] 1. A reference acquisition means for acquiring reference data obtained by performing statistical processing on a statistical processing log, which is a log related to a first task; an evaluation target log acquisition means for acquiring an evaluation target log which is a log related to the first work performed by a first organization; an evaluation data generating means for generating evaluation data for evaluating an evaluation target set in relation to the first organization based on the evaluation target log; an evaluation means for generating evaluation data including an evaluation result for the evaluation target using the reference data and the evaluation data; Work management device. 2. The statistical processing log includes logs related to the first work performed on each terminal of a plurality of organizations. 1. A work management device as described above in claim 1. 3. The first operation is composed of a plurality of steps, The log relating to the first work includes a log for each of the steps. 3. The work management device according to claim 1 or 2. 4. The first operation is performed on a terminal of each of the plurality of organizations; The method further includes a log generating unit that generates the statistical processing log by combining logs of a series of steps that constitute the first work from among the logs for each step acquired from the terminals of the plurality of organizations. 3. The work management device according to claim 3. 5. The reference acquisition means acquires the reference data for each of the steps; The evaluation data generating means generates the evaluation data for each process related to the evaluation object based on the evaluation object log, The evaluation means generates the evaluation data for each process related to the evaluation target by using the reference data and the evaluation data for the common process. 5. The work management device according to claim 3 or 4. 6. The log related to the first work includes a processing amount indicating an amount of objects processed in the first work; The reference acquisition means acquires reference data for each of the processing amounts, the evaluation data generating means generates the evaluation data for each of the processing amounts based on the evaluation target log; The evaluation means generates evaluation data for each of the amounts of processing using the reference data and the evaluation data, which have the same amount of processing. 6. A work management device according to any one of 1 to 5 above. 7. The evaluation target is the first organization, a terminal managed by the first organization, or a worker performing the first task in the first organization. A work management device according to any one of 1 to 6 above. 8. The log relating to the first task includes a task time, The reference acquisition means acquires the reference data obtained by performing the statistical processing on the operation time included in the statistical processing log, The evaluation data generating means generates the evaluation data based on the operation time included in the evaluation target log, The evaluation means generates the evaluation data by using the task times included in the reference data and the evaluation data. A work management device according to any one of 1 to 7 above. 9. The log relating to the first work includes error information relating to an error that occurred in relation to the first work; The reference data includes a number of errors made in connection with the first task; The evaluation data includes a number of errors made in relation to the first task performed by the evaluation subject, The evaluation means generates the evaluation data by using the number of errors included in each of the reference data and the evaluation data. A work management device according to any one of 1 to 8 above. 10. The error information includes at least one of correction information regarding a correction made by a worker during the processing of the first task, deficiency information regarding a defect found in a confirmation step included in the first task, and system error information regarding a system error that occurred during the processing of the first task. 10. A work management device according to any one of 1 to 9 above. 11. The first operation is a transfer-out or transfer-in operation at the government office of the organization. A work management device according to any one of 1 to 10 above. 12. Obtaining reference data obtained by performing statistical processing on a statistical processing log, which is a log related to the first work; Acquiring an evaluation target log, which is a log related to the first work performed by a first organization; generating evaluation data for evaluating an evaluation target set in relation to the first organization based on the evaluation target log; generating evaluation data including an evaluation result for the evaluation target using the reference data and the evaluation data. Work management methods. 13. On the computer, 13. A program for executing the work management method according to claim 12. [Explanation of symbols]

[0261] 100, 100_a1~a3, 100_b, 100_c1~c2 Terminal 101 Server 102 Input reception section 103 Terminal communication unit 104 Display section 105 Terminal Log Creation Department 106 Terminal Management Unit 107 Log Collection Unit 108 Work Evaluation Department 109 Operator memory section 109a Worker Data 110 Login processing section 111 Workflow memory unit 111a Workflow Data 112 Screen transmission unit 113 Terminal log acquisition unit 114 Work Log Memory Unit 115 Connection regulation storage section 115a Combined Regulation Data 116 Connection determination section 117 Log Generation Unit 118 Evaluation Reception Department 119 Standards Acquisition Department 120 Evaluation target log acquisition unit 121 Evaluation data generation unit 122 Evaluation Section

Claims

1. An evaluation target log acquisition means for acquiring an evaluation target log, which is a log related to the first work performed by a first organization; an evaluation data generating means for generating evaluation data for evaluating an evaluation target set in relation to the first organization based on the evaluation target log; and an evaluation means for generating evaluation data including an evaluation result for the evaluation target using the evaluation data and multiple organization data generated based on logs related to the first work performed on each terminal of a plurality of organizations. Work management device.

2. the first work is composed of a plurality of steps, The log relating to the first work includes a log for each of the steps. The work management device according to claim 1 .

3. the first work is performed on a terminal of each of the plurality of organizations; The system further includes a log generating unit that generates the log by combining logs of a series of steps that constitute the first work from the logs for each step acquired from the terminals of the plurality of organizations. The work management device according to claim 2 .

4. The multiple organization data is data generated for each of the processes, the evaluation data generating means generates the evaluation data for each process related to the evaluation object based on the evaluation object log; The evaluation means generates the evaluation data for each process related to the evaluation target using the data for the multiple organizations having the common process and the evaluation data. The work management device according to claim 2 or 3.

5. the log related to the first work includes a processing amount indicating an amount of an object to be processed in the first work; the multi-organization data is data generated for each of the processes, the evaluation data generating means generates the evaluation data for each of the processing amounts based on the evaluation target log; The evaluation means generates evaluation data for each of the processing amounts using the multi-organization quasi-data having the same processing amount and the evaluation data. The work management device according to any one of claims 1 to 4.

6. the log relating to the first task includes a task time; the multiple organization data is data generated based on the work time included in the log, the evaluation data generation means generates the evaluation data based on the operation time included in the evaluation target log; The evaluation means generates the evaluation data using the work times included in the multi-organization data and the evaluation data. The work management device according to any one of claims 1 to 5.

7. the log relating to the first work includes error information relating to an error that occurred in relation to the first work; the multi-organization data is data generated based on the number of errors that occurred in relation to the first work, the evaluation data is data generated based on the number of errors made in relation to the first task performed by the evaluation subject, The evaluation means generates the evaluation data based on the number of errors included in the multi-group data and the evaluation data. The work management device according to any one of claims 1 to 6.

8. Acquiring an evaluation target log, which is a log related to the first work performed by a first organization; generating evaluation data for evaluating an evaluation target set in relation to the first organization based on the evaluation target log; generating evaluation data including an evaluation result for the evaluation target using the evaluation data and multi-organization data generated based on logs related to the first work performed on each terminal of a plurality of organizations. Work management methods.

9. On the computer, A program for executing the work management method according to claim 8.

Images