Information processing device and program

The information processing device addresses the issue of decreased worker awareness in conventional workflow systems by calculating average task completion times and sending timely notifications, thereby reducing task omissions and delays.

JP2026053081APending Publication Date: 2026-03-25TOSHIBA TEC KK
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-09-12
Publication Date
2026-03-25

AI Technical Summary

Technical Problem

Conventional workflow systems mechanically send notifications at fixed timings, leading to decreased worker awareness and increased instances of work omissions and delays.

Method used

An information processing device that calculates the average time for task completion based on worker history and sends notifications to workers who have not yet performed their tasks at appropriate timings using the calculated average time.

Benefits of technology

Improves worker awareness of tasks by sending timely notifications, reducing the occurrence of missed or delayed tasks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026053081000001_ABST
    Figure 2026053081000001_ABST
Patent Text Reader

Abstract

We provide an information processing device and program that can support workflow operations. [Solution] The information processing device of the embodiment includes a calculation unit that calculates the average time from when a worker is assigned a turn until the worker executes the work for each type of work, based on a work history that associates the type of work performed by the worker with the date and time the work was executed, for each workflow that defines the assignment order of tasks to be performed sequentially among multiple workers, and a notification unit that notifies workers who have not yet performed a task at a timing based on the average time corresponding to the type of work.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present invention relate to an information processing apparatus and a program.

Background Art

[0002] In an organization such as a company, a workflow system is known that circulates document data such as various application forms for approval and settlement. In the workflow system, for example, when creating an application form, the drafter inputs necessary items by multiple-choice using a pull-down menu or text input by free description. When the work by the drafter is completed, the document data is circulated to workers such as checkers and approvers according to the circulation route.

[0003] By the way, in the conventional workflow system, there are some that send a notice to prompt the execution of work to workers who perform work such as approval when a request occurs or when a due date is exceeded. However, since the conventional workflow system mechanically sends a notice at a fixed timing, the awareness of the workers regarding the notice decreases, and there are cases where the effect is low against the occurrence of work omissions and delays. Therefore, a technology capable of providing work support to reduce the occurrence of work omissions and delays is demanded.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the embodiments of the present invention is to provide an information processing apparatus and a program capable of providing work support for a workflow.

Means for Solving the Problems

[0005] The information processing device of this embodiment includes a calculation unit that, for each workflow defining the assignment order of tasks to be performed sequentially among multiple workers, calculates the average time from when a worker is assigned a turn until the worker performs the task, based on a work history that associates the type of task performed by the worker with the date and time the task was performed, and a notification unit that notifies workers who have not yet performed a task at a timing based on the average time corresponding to the type of task. [Brief explanation of the drawing]

[0006] [Figure 1] Figure 1 is a block diagram illustrating a business support system according to an embodiment. [Figure 2] Figure 2 shows an example of the data configuration of the workflow storage area according to the embodiment. [Figure 3] Figure 3 is a flowchart showing an example of the workflow management process performed by the server in this embodiment. [Figure 4] Figure 4 is a flowchart showing an example of the process performed by the server in the embodiment for calculating the average working time. [Figure 5] Figure 5 is a flowchart showing an example of the processing related to the alert notification performed by the server in the embodiment. [Modes for carrying out the invention]

[0007] Embodiments will be described below with reference to the drawings. In each drawing, the same reference numerals are used for identical components whenever possible, and redundant explanations are omitted.

[0008] Figure 1 is a block diagram illustrating a business support system 1 according to an embodiment. The business support system 1 includes a server 10 and a user terminal 20.

[0009] The server 10 and the user terminals 20 are connected to each other via network N, enabling communication. For example, network N consists of one or more networks from among various networks such as the Internet, mobile communication networks, and LANs (Local Area Networks). The one or more networks may include wireless networks or wired networks. The number of user terminals 20 included in the business support system 1 is not limited to the illustrated example.

[0010] Server 10 is an example of an information processing device. Server 10 collects data and processes the collected data. Server 10 is connected to the user terminal 20 via network N in a communicative manner. Server 10 receives various data from the user terminal 20 and outputs various data to the user terminal 20. Server 10 is an example of an information processing device. An example configuration of Server 10 will be described later. Server 10 may also be a server used in a cloud service.

[0011] Server 10 provides a workflow service for processing applications and other documents from creation to approval or settlement. The workflow service provides, for example, a workflow for creating and managing document data. The workflow includes a series of tasks in which the drafter creates document data and circulates the document data to the next worker according to a predetermined circulation route. Creating document data includes entering necessary information and attaching necessary documents. Circulation includes notifying the next worker. The next worker verifies the document data created by the drafter. The next worker may include a seal impressioner and an approver. The worker may also include the drafter.

[0012] A workflow service may include multiple workflows. A workflow defines the assignment sequence of tasks to be performed sequentially by multiple workers. Workflows are configured, for example, for each task that can be viewed or worked on by multiple workers within an organization. An organization may include workers who perform tasks from the start to the completion of a workflow. An organization may be, for example, a company, corporation, or office. An organization is not limited to the above and may also be a community containing multiple workers. A workflow may include, for example, a series of tasks such as drafting, approving, and approving. A workflow may include, for example, the creation of various application forms such as travel expense claims and equipment usage requests, the creation of reports, and the creation of request forms. A workflow may include information sharing within an organization. Workflows may be configured for each task, each task, or each topic.

[0013] User terminal 20 is a device capable of communicating with other electronic devices. User terminal 20 is a device used by the drafter and workers of the workflow. The drafter is also referred to as the creator of document data in the workflow. For example, user terminal 20 is a PC (Personal Computer), smartphone, or tablet device, but is not limited to these. Users of user terminal 20 use the workflow service through user terminal 20.

[0014] Next, an example configuration of server 10 will be described. As shown in Figure 1, server 10 is a device that includes a processing circuit 11, main memory 12, auxiliary storage device 13, and communication interface (I / F) 14. Each part of server 10 is connected to each other so that signals can be input and output.

[0015] The processing circuit 11 is a processor that corresponds to the central part of the server 10 and comprehensively controls the operation of the server 10. The processing circuit 11 is an element that constitutes the computer of the server 10. For example, the processing circuit 11 is a CPU (Central Processing Unit), but is not limited to this. The processing circuit 11 may be composed of various circuits such as an RTC (Real Time Clock) that can measure the current date and time.

[0016] The processing circuit 11 loads a program pre-stored in the main memory 12 or auxiliary storage device 13 into the main memory 12. The program is a program that enables the processing circuit 11 of the server 10 to implement the various parts described later. The processing circuit 11 performs various operations by executing the program loaded into the main memory 12.

[0017] Main memory 12 corresponds to the main memory portion of server 10. Main memory 12 is an element that constitutes the computer of server 10. Main memory 12 includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area of ​​main memory 12, the operating system or programs are stored. Main memory 12 uses the volatile memory area as a work area where data is rewritten as appropriate by the processing circuit 11. For example, main memory 12 includes ROM (Read Only Memory) as a non-volatile memory area. For example, main memory 12 includes RAM (Random Access Memory) as a volatile memory area. Main memory 12 stores programs.

[0018] The auxiliary storage device 13 corresponds to the auxiliary storage portion of the server 10. The auxiliary storage device 13 is an element that constitutes the computer of the server 10. The auxiliary storage device 13 is an EEPROM (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive), etc. The auxiliary storage device 13 stores the above-mentioned program, data used by the processing circuit 11 in performing various processes, and data generated by the processing in the processing circuit 11. The auxiliary storage device 13 stores the above-mentioned program.

[0019] The auxiliary memory device 13 stores a workflow storage area 131. In this example, assume that the workflow is a flow in which the creator creates document data and circulates it to the operator. The document data is draft data created by the drafter of the workflow. For example, when the workflow is the creation of an application form, the document data represents the input data of the application form.

[0020] FIG. 2 is a diagram showing an example of the data configuration of the workflow storage area 131 according to the embodiment. The workflow storage area 131 includes information such as, for example, a workflow ID, document data, a workflow type, a circulation route, and a work deadline.

[0021] The workflow ID is an identifier for identifying the workflow, and a unique ID is assigned to each workflow. The document data is the document data created by the drafter of the workflow or information indicating the storage location of the document data. The workflow type is information indicating the type of document data such as an application form, that is, the type of the workflow.

[0022] The circulation route includes node IDs (hereinafter also referred to as nodes) indicating the circulation order for circulating the document data to the operator, in other words, the assignment order of the work. The operator is the person who performs the work on the document data of the workflow. The node holds information such as, for example, a numerical value indicating the circulation order. For example, when circulating to three operators, nodes 1 to 3 are stored in the circulation route.

[0023] Information such as a user ID, an assignment date and time, and a work history is stored in association with each node. The user ID is identification information that uniquely identifies the operator. The assignment date and time is information indicating the date and time when the circulation of the document data is assigned to the operator of the node, in other words, the date and time when the work is assigned to the operator. For example, the date and time when the circulation of the workflow starts is registered as the assignment date and time of the node at the top of the circulation order. Also, the date and time when the approval work described later is executed at the previous node is registered as the assignment date and time of the node at the shift to the next order other than the second from the top of the circulation order.

[0024] The work history includes the type of work performed on the document data, the date and time of work execution (execution date and time), etc. Examples of the type of work include creation, update, modification, approval, and rollback. The type of work is set according to the type of workflow, etc. The type of work may also be set according to the authority of the worker, etc. When multiple works are executed on the same node due to rollback from the next-order node, etc., the work history of the node records the combination of the type of work and the work date and time in the order of execution. Hereinafter, among the works that can be executed by the worker, the work that advances the order to the next-order worker and the work that approves the work executed in the previous order are also referred to as "approval work".

[0025] The work deadline is information such as the year, month, day, and time indicating the deadline for completing the execution of the workflow. The work deadline may be set by the drafter, or a predetermined period may be set based on the creation date and time of the drafted data. Also, the work deadline may be set for each node.

[0026] The workflow storage area 131 may include other information related to the workflow. For example, the workflow storage area 131 may include rank information such as importance and urgency for each workflow. Also, the workflow storage area 131 may store the work status of the workflow. The work status indicates the status of the work on the workflow. The work status indicates, for example, whether the work of all workers has been completed or is in an unfinished state. The information related to the workflow can be updated as appropriate.

[0027] The auxiliary storage device 13 includes an average work time storage area 132. The average work time storage area 132 stores average work time information. The average work time information can be updated as appropriate according to the work performance of each worker.

[0028] Average work time information is information that associates work type with average work time. Work type refers to the type of work performed at each node of the workflow. Average work time is the average time from when a work type becomes ready to be executed until it is actually executed. Average work time information stores the average work time associated with approval work types among multiple work types.

[0029] The average work time storage area 132 may include information other than average work time information related to work type. For example, the average work time storage area 132 may include other average work time information (hereinafter also referred to as WF average work time information) that associates the average work time for each workflow type. The average work time in the WF average work time information is the average of the time from when the workflow circulation starts until the approval work at the last node is performed.

[0030] The auxiliary storage device 13 may store areas other than the workflow storage area 131 and the average work time storage area 132. The auxiliary storage device 13 may also store a user management area that stores and manages the user IDs of workers, including the drafter. The user management area stores user management information, such as the user's affiliation, job title, and authority, associated with each user's user ID.

[0031] The communication interface 14 includes various interfaces that enable the server 10 to communicate with other devices via the network N, in accordance with a predetermined communication protocol.

[0032] The hardware configuration of server 10 is not limited to the configuration described above. Server 10 may, as appropriate, omit or change the above-described components and add new components.

[0033] Next, we will describe the functional configuration implemented in the processing circuit 11 described above.

[0034] The processing circuit 11 implements the workflow management unit 111, the analysis processing unit 112, and the notification processing unit 113. Each part implemented in the processing circuit 11 can also be called a function. Each part implemented in the processing circuit 11 can also be said to be implemented in the control unit, which includes the processing circuit 11 and the main memory 12.

[0035] The workflow management unit 111 manages the workflow. The workflow management unit 111 stores the document data created by the drafter in the workflow storage area 131, associating it with the workflow ID, workflow type, circulation route, deadline, etc. The workflow type may be set by the drafter, or it may be set by the workflow management unit 111 according to the created document data. The circulation order, number of circulations (number of nodes), and user ID included in the circulation route may be set by the drafter, or it may be automatically set by the workflow management unit 111 according to the drafter's affiliation, WD type, etc. The deadline may be set by the drafter, or it may be automatically set by the workflow management unit 111 according to the current date and time, WD type, etc.

[0036] The workflow management unit 111 provides the workflow stored in the workflow storage area 131 to the workers with user IDs set at each node of the circulation route. Specifically, the workflow management unit 111 provides the document data included in the workflow to the user terminal 20 operated by the workers with user IDs set at each node of the circulation route, making it viewable and operable. The workflow management unit 111 also accepts operations (tasks) on the document data from the workers in the order of the circulation sequence set at each node. The workflow management unit 111 may also provide the user terminal 20 with a screen (user interface) to support operations on the workflow.

[0037] When the workflow management unit 111 receives an operation on the workflow from the user terminal 20, it registers the results of the work corresponding to the operation in the work history of the workflow storage area 131. Specifically, when the workflow management unit 111 receives an operation on document data, it registers the type of work corresponding to the operation and the date and time the operation was performed (work date and time) in the work history of the node associated with the user ID of the worker who performed the operation, among the nodes set in the circulation route. When the user terminal 20 accesses the server 10, it sends the user ID of the worker operating its terminal to the server 10.

[0038] Furthermore, the workflow management unit 111 advances the circulation order to the next level or returns it to the previous level depending on the operation content (type of work) received from the worker. For example, if it receives an operation to return a document, the workflow management unit 111 returns the circulation order to the previous level. For example, if it receives an operation to perform an approval work such as approval, the workflow management unit 111 advances the circulation order to the next level. When advancing the circulation order to the next level, the workflow management unit 111 registers the date and time of the work performed at the previous level node when the approval work was performed at the next level node's assignment date and time.

[0039] The analysis processing unit 112 is an example of a calculation unit and calculation means. The analysis processing unit 112 calculates the average work time for each type of work. Based on the work history of each workflow recorded in the workflow storage area 131, the analysis processing unit 112 calculates the average work time for each type of work from the time the worker is assigned a turn until the worker performs the work.

[0040] Specifically, the analysis processing unit 112 accumulates the elapsed time from the node's assignment date and time to the date and time the approval work was performed for each type of approval work registered in the work history of each node. Then, the analysis processing unit 112 calculates the average work time for each type of approval work by dividing the accumulated time for each type of approval work (cumulative time) by the total number of nodes from which work time for that type was collected. Once the average work time is calculated, the analysis processing unit 112 stores the average work time in the average work time storage area 132, associating it with the type of approval work.

[0041] If multiple approval tasks are registered in the work history of the same node due to reasons such as rejection, the analysis processing unit 112 may accumulate the time from the assignment date and time to the latest work date and time, or it may accumulate the time up to the oldest work date and time. For example, as a method of accumulating when multiple approval tasks are registered, the system may be configured to allow selection whether to use the latest or the oldest work date and time for the accumulation.

[0042] The analysis processing unit 112 may also calculate the average work time for each type of workflow. In this case, the analysis processing unit 112 accumulates the time from the assignment date and time of the first node to the work date and time of the approval work recorded in the work history of the last node for each type of workflow in which each worker's work has been completed. The analysis processing unit 112 then calculates the average work time for each type of workflow (WF average work time) by dividing the accumulated time for each type of workflow (cumulative time) by the total number of workflows from which work time for that type was collected. Once the analysis processing unit 112 has calculated the WF average work time, it stores the average work time in the average work time storage area 132, associating it with the type of approval work.

[0043] The timing at which the analysis processing unit 112 calculates the average work time is not particularly fixed and can be set arbitrarily. For example, the analysis processing unit 112 may calculate the average work time at a predetermined interval (e.g., every day, every month, etc.). Alternatively, the analysis processing unit 112 may calculate the average work time in response to an operation from the operator.

[0044] The notification processing unit 113 is an example of a notification unit and notification means. Based on the workflow stored in the workflow storage area 131, the notification processing unit 113 sends a notification (hereinafter also called a warning notification) to workers who have not yet performed a task, prompting them to perform the task, at a timing based on the average work time corresponding to the type of task. Workers who have not yet performed a task are workers on nodes where an assigned date and time have been registered, but no approved task is recorded in the work history. Note that workers who have not yet performed a task may be classified as "work not started" if their work history is empty, and as "work started" if the latest work type recorded in their work history is something other than an approved task.

[0045] Specifically, the notification processing unit 113 issues a warning notification when a predetermined time has elapsed from the assignment date and time of a node to which a worker who has not yet performed work is assigned, based on the average work time of the type of approval work performed at that node. For example, the notification processing unit 113 issues a warning notification when X% of the average work time has elapsed from the assignment date and time. As an example, the notification processing unit 113 issues a warning notification when 50% or 80% of the average work time has elapsed from the assignment date and time.

[0046] The content of the warning notification can be set arbitrarily, but for example, it may include a message indicating that the warning was issued based on the average working time or a time based on the average working time.

[0047] Furthermore, the timing of alert notifications based on average work time can be arbitrarily set. For example, alert notifications may be issued at two points: when 50% and 80% of the average work time have elapsed. In this case, different alert notifications may be issued depending on the elapsed time. For example, the notification processing unit 113 may change the content and display format of the notification message depending on the elapsed time.

[0048] Furthermore, the content and timing of warning notifications may differ for workers who have not yet started work and those who have already started work. For example, the notification processing unit 113 determines whether a worker has not yet started work or has already started work based on their work history when a predetermined time based on the average work time has elapsed since the date and time when the worker was assigned a turn. The notification processing unit 113 may then switch the content of the warning notification according to the determination result.

[0049] Furthermore, for example, the notification processing unit 113 may issue a warning notification when 50% of the average work time has elapsed from the assigned time to the worker who has not yet started work, and when 80% of the average work time has elapsed from the assigned time to the worker who has already started work.

[0050] Furthermore, the notification processing unit 113 may issue a warning notification when the average work time (100% of the time) has elapsed from the assigned date and time. When issuing a warning notification at the time when the average work time has elapsed, it is preferable to issue a warning notification with different content than the warning notification issued at the time when the average work time has not elapsed. For example, the notification processing unit 113 may make the content of the notification message and the display format different depending on whether or not the average work time has elapsed (exceeded).

[0051] The notification to the worker will be sent via the user terminal 20, but the method of notification is not particularly restricted. For example, the notification processing unit 113 may display the notification on the workflow viewing screen. Alternatively, information for displaying the notification may be output to the user terminal 20. As an example, the notification processing unit 113 may output information for displaying the notification to the user terminal 20 using email or short message service.

[0052] As described above, the server 10 of this embodiment issues notifications to encourage the execution of tasks based on the average work time derived from each worker's work performance. This allows the server 10 to issue notifications to encourage the execution of tasks at a timing appropriate to the environment in which the workflow is provided and the type of work actually being performed, thereby improving workers' awareness of notifications. Consequently, the server 10 can provide work support that reduces the occurrence of missed or delayed tasks.

[0053] The following describes the processing procedure performed by the business support system 1. In the following explanation focusing on server 10, server 10 may be read as processing circuit 11. Furthermore, the processing procedure described below is merely an example, and each process may be modified as much as possible. In addition, steps in the processing procedure described below can be omitted, replaced, or added as appropriate, depending on the embodiment.

[0054] Figure 3 is a flowchart showing an example of the workflow management process performed by the server 10 in this embodiment.

[0055] First, the workflow management unit 111 determines whether or not it has received a workflow creation operation from the user terminal 20 operated by the drafter (step S11). If the workflow creation operation is not received (step S11; No), the workflow management unit 111 proceeds to step S13.

[0056] On the other hand, if the workflow creation operation is accepted in step S11 (step S11; Yes), the workflow management unit 111 registers the created workflow in the workflow storage area 131 (step S12) and proceeds to step S13. Specifically, the workflow management unit 111 stores the document data created by the drafter in the workflow storage area 131, associating it with the circulation route, etc. At this time, the workflow management unit 111 assigns the work to the first worker by registering the current date and time when the workflow was registered at the assignment date and time of the first node in the circulation sequence.

[0057] Furthermore, the workflow management unit 111 may, in cooperation with the notification processing unit 113, send a warning notification to the user ID (worker) associated with the first node in the circulation sequence, prompting them to perform the task.

[0058] Next, the workflow management unit 111 determines whether or not it has received an operation (hereinafter referred to as a circulation operation) on document data included in any workflow from the user terminal 20 operated by the worker (step S13). If no circulation operation is received (step S13; No), the workflow management unit 111 returns to step S11.

[0059] Meanwhile, when the workflow management unit 111 receives a circulation operation (step S13; Yes), it records the type of work corresponding to the operation and the date and time of the work in the work history of the node corresponding to the user ID of the worker who performed the operation, among the nodes included in the circulation flow of the workflow that was the target of the operation (step S14). Then, the workflow management unit 111 returns to step S11.

[0060] Furthermore, when the workflow management unit 111 receives a circulation operation corresponding to an approval task, it assigns the task to the next-ranked worker by registering the work date and time of the approval task at the assignment date and time of the next-ranked node. In this case, the workflow management unit 111 may also work in cooperation with the notification processing unit 113 to send a warning notification to the user ID (worker) associated with the next-ranked node, urging them to perform the task.

[0061] Figure 4 is a flowchart illustrating an example of the process performed by the server 10 in this embodiment for calculating the average work time. The analysis processing unit 112 sequentially targets the workflows stored in the workflow storage area 131 for this process. The analysis processing unit 112 may also target workflows for which all workers' approval work has been completed.

[0062] First, the analysis processing unit 112 refers to the assignment date and time and work history of each node included in the workflow circulation flow, and accumulates the elapsed time from the assignment date and time to the work date and time when the approval work was performed for each type of approval work (step S21).

[0063] Next, the analysis processing unit 112 calculates the average work time for each type of approval work by dividing the cumulative time for each type of approval work by the total number of nodes from which the work date and time for that type was collected (step S22). Then, the analysis processing unit 112 associates the type of approval work with the average work time calculated for that type and stores it in the average work time storage area 132 (step S23).

[0064] The analysis processing unit 112 may calculate the average WF work time by accumulating the time from the assignment date and time of the first node to the work date and time when the approval work was performed at the last node for each workflow targeted for processing, for each type of workflow, and dividing by the total number of workflows of that type.

[0065] Figure 5 is a flowchart showing an example of the processing related to alert notifications performed by the server 10 of the embodiment. The notification processing unit 113 sequentially targets incomplete workflows among those stored in the workflow storage area 131 for this processing.

[0066] First, the notification processing unit 113 identifies nodes included in the workflow's work flow that have an assigned date and time registered, but for which approval work is not recorded in the work history (step S31).

[0067] Next, the notification processing unit 113 refers to the average work time storage area 132 and identifies the average work time corresponding to the type of approval work performed at the identified node (step S32). Then, the notification processing unit 113 calculates the elapsed time from the allocation date and time of the identified node to the current date and time (step S33).

[0068] Next, the notification processing unit 113 determines whether or not to issue a warning notification based on the elapsed time up to the current date and time calculated in step S33 and the average work time identified in step S32 (step S34). For example, the notification processing unit 113 determines whether the elapsed time from the assigned date and time has exceeded 80% of the average work time, and if it has exceeded that, it determines to issue a notification.

[0069] If it is determined in step S32 to issue a notification (step S35; Yes), the notification processing unit 113 issues a warning notification to the worker with the user ID associated with the node identified in step S31 (step S36), and then terminates this process. If it is determined in step S32 not to issue a notification (step S35; No), then this process terminates.

[0070] As described above, for each workflow that defines the sequential assignment order of tasks to be performed by multiple workers, the server 10 of this embodiment calculates the average time from when a worker is assigned a turn until the worker performs the task, based on the work history which associates the type of task performed by the worker with the date and time the task was performed. The server 10 then notifies workers who have not yet performed a task at a timing based on the average time corresponding to that type of task.

[0071] As a result, Server 10 issues alert notifications at a timing appropriate to the environment in which the workflow is provided and the type of work actually being performed, thereby improving the awareness of notifications among workers who have not yet performed the work. Therefore, Server 10 can provide work support that reduces the occurrence of missed or delayed tasks.

[0072] The embodiments described above can also be modified and implemented as appropriate by changing some of the configurations or functions of each of the devices described above. Therefore, several modifications of the embodiments described above will be described below as other embodiments. In the following, we will mainly describe the differences from the embodiments described above, and will omit detailed explanations of points that are common with what has already been described. Furthermore, the modifications described below may be implemented individually or in combination as appropriate.

[0073] (Variation 1) In the embodiment described above, the server 10 is configured to send alert notifications to the workers who actually perform the workflow tasks (hereinafter also referred to as "workers"), but the recipients of the alert notifications are not limited to the workers. For example, the notification processing unit 113 may send alert notifications to the supervisor of the organization to which the worker belongs, along with the workers themselves, based on user management information that associates information such as each user's affiliation, job title, and authority.

[0074] For example, the notification processing unit 113 will issue a warning notification to the person in charge when 50% or 80% of the average work time has elapsed since the assigned date and time, and when 100% of the average work time has elapsed. The system may be configured to send a warning notice to the person in charge and their supervisor once a certain period of time has elapsed.

[0075] Furthermore, for example, the notification processing unit 113 may be configured to send a warning notification to the person in charge if the importance level associated with the workflow is "normal," and to send a warning notification to both the person in charge and their supervisor if the importance level is "important" or "urgent."

[0076] According to the modified server 10, the recipient of alert notifications can be changed based on the elapsed time based on the average work time and the workload of the workflow, thereby enabling effective alert notifications.

[0077] (Modification 2) In the embodiment described above, the server 10 is configured to issue a warning notification based on the average working time for approval tasks, but it is not limited to this configuration, and a warning notification may also be issued based on the average working time for WF tasks.

[0078] In this case, for example, the notification processing unit 113 identifies the average WF work time corresponding to the type of incomplete workflow among the workflows stored in the workflow storage area 131. Next, the notification processing unit 113 determines whether the time based on the identified average WF work time has elapsed since the assignment date and time of the first node in the circulation route of that workflow. For example, the notification processing unit 113 determines whether the time based on 50%, 80%, or 100% of the average WF work time has elapsed. If the notification processing unit 113 determines that the time based on the average WF work time has elapsed, it issues a warning notification to the worker who has not yet performed the above-mentioned task.

[0079] Furthermore, if the time elapsed from the initial node assignment date to the average WF work time (100% of the time) exceeds the work deadline, it is preferable that the notification processing unit 113 adjusts the elapsed time percentage based on the average WF work time so as to issue one or more warning notifications before the work deadline.

[0080] As described above, according to the server 10 of this modified version, it is possible to provide workers with a warning notification to encourage them to perform their work based on the average WF work time derived from the workers' work performance.

[0081] (Other embodiments) The information processing device may be implemented as a single device, such as server 10, or as multiple devices with distributed functions. In the latter case, the information processing device includes the meaning of an information processing system composed of multiple devices.

[0082] The embodiments described above may apply not only to the apparatus but also to the methods performed by the apparatus. The embodiments described above may apply to a program that can cause the computer of the apparatus to perform each function. The embodiments described above may apply to a recording medium that stores the program. The embodiments described above may apply not only to the system but also to the methods performed by multiple elements included in the system.

[0083] A processing circuit includes one or more circuits that perform multiple processes through multiple functions. For example, the circuit may be, but is not limited to, a processor, an ASIC (Application Specific Integrated Circuit), or an FPGA (Field-Programmable Gate Array).

[0084] Each of the one or more circuits that make up a processing circuit performs one or more of the multiple processes. If the processing circuit consists of a single circuit, the single circuit performs all of the multiple processes. If the processing circuit consists of multiple circuits, each of the multiple circuits performs some of the multiple processes. Some of the multiple processes may be one of the multiple processes, or two or more of the multiple processes. If the processing circuit consists of multiple circuits, the multiple circuits may be contained in a single device, or they may be distributed across multiple devices.

[0085] The program may be transferred while stored in the device, or it may be transferred without being stored in the device. In the latter case, the program may be transferred via a network, or it may be transferred while recorded on a recording medium. The recording medium is a non-temporary tangible medium. The recording medium is a computer-readable medium. The recording medium can be any medium that is capable of storing a program and is readable by a computer, such as a CD-ROM or memory card, and its form is not limited.

[0086] Although embodiments of the present invention have been described in detail above, the above description is merely illustrative in all respects of the present invention. Needless to say, various improvements and modifications can be made without departing from the scope of the present invention. In other words, when implementing the present invention, specific configurations may be adopted as appropriate depending on the embodiment.

[0087] In short, this invention is not limited to the embodiments described above, and in the implementation stage, the components can be modified and materialized without departing from the gist of the invention. Furthermore, various inventions can be formed by appropriately combining the multiple components disclosed in the embodiments. For example, some components may be deleted from all the components shown in the embodiments. Moreover, components from different embodiments may be appropriately combined. [Explanation of Symbols]

[0088] 1. Business support system 10 servers 11 Processing Circuit 111 Workflow Management Department 112 Analytical Processing Unit 113 Notification Processing Unit 131 Workflow Storage 132 Average working time storage area 20 User Terminals [Prior art documents] [Patent Documents]

[0089] [Patent Document 1] Japanese Patent Publication No. 2021-056962

Claims

1. For each workflow that defines the assignment order of tasks to be performed sequentially by multiple workers, a calculation unit calculates the average time from when the worker is assigned a turn until the worker performs the task, based on a work history that associates the type of task performed by the worker with the date and time the task was performed. A notification unit that notifies workers who have not yet performed a task at a timing based on the average time corresponding to the type of task, An information processing device equipped with the following features.

2. The calculation unit calculates the average time for each type of task that the worker can perform, whether it is a task that is passed on to the next worker in line or a task that is performed in a preceding line. The information processing apparatus according to claim 1.

3. The notification unit will notify the worker if the work has not been performed when a predetermined time based on the average time has elapsed from the date and time when the worker was assigned a turn. The information processing apparatus according to claim 1.

4. The notification unit, when a predetermined time based on the average time has elapsed from the date and time the worker was assigned a turn, determines whether the work has not yet been started or has been started based on the worker's work history, and switches the notification content according to the determination result. The information processing apparatus according to claim 1.

5. The notification unit changes the notification destination according to the importance of the workflow. The information processing apparatus according to claim 1.

6. The computer of the information processing device, For each workflow that defines the assignment order of tasks to be performed sequentially by multiple workers, a calculation means calculates the average time from when the worker is assigned a turn until the worker performs the task, based on a work history that associates the type of task performed by the worker with the date and time the task was performed. A notification means for notifying workers who have not yet performed a task at a timing based on the average time corresponding to the type of task, A program to make it work.

Citation Information

Patent Citations

  • Workflow support device, method for supporting workflow, and program

    JP2021056962A