Workflow management system, workflow management method, and program

Abstract

An object is to provide a workflow management system suitable for use in actual business operations. **Solution** A workflow management system comprising: a display unit that displays a workflow generation screen; a generation unit that generates a workflow related to a workflow based on a generation instruction input via the workflow generation screen; a data registration unit that, when receiving an execution instruction for the workflow, generates execution information including the execution status of one or more steps included in the workflow and registers the execution information in association with the workflow; the display unit displays a screen showing the flowchart of the workflow and the execution status; two or more pieces of the execution information are associated with the workflow; a workflow management system.

Description

Technical Field

[0001] The present invention relates to a workflow management system, a workflow management method, and a program.

Background Art

[0002] Conventionally, systems for creating workflows have been developed.

[0003] For example, Patent Document 1 discloses a workflow creation / change support system that can improve the efficiency of workflow creation / change.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In actual business, it is assumed that the same flow can be run simultaneously for multiple cases, etc. However, Patent Document 1 could not execute and manage multiple of the same flows.

Means for Solving the Problems

[0006] In view of the above-described situation, an object of the present invention is to provide a workflow management system suitable for use in actual business.

Effects of the Invention

[0007] [1] A workflow management system, a display unit that displays a workflow generation screen, a generation unit that generates a workflow based on a generation instruction input via the workflow generation screen, Upon receiving an instruction to execute a workflow, a data registration unit generates execution information including the execution status of one or more steps included in the workflow and registers it in association with the workflow. The display unit displays a screen showing the flowchart of the workflow and the execution status. Two or more pieces of the execution information are associated with the workflow. Workflow management system. [2] The workflow management system further includes a reception unit. The reception unit receives a designation of a workflow for list display. Based on the execution information related to the designated workflow, the display unit displays a list of the execution status of the workflow. The execution status list displays the execution status of the workflow based on the execution status for each step. The workflow management system according to [1]. [3] The workflow includes steps for executing tasks. The execution information includes charge information regarding the charge for each task. The execution status is the execution status for each step, Based on the execution information of the designated person in charge, the display unit displays a list of tasks assigned to the designated person in charge. The workflow management system according to [1] or [2]. [4] The workflow management system further includes a reception unit and an execution status management unit. Based on the execution information, the display unit displays a task execution screen for executing the tasks of the steps whose execution status is in progress on the user terminal of the person in charge. The reception unit receives task execution information input via the task execution screen. The execution status management unit sets the execution status of the step to completed. The workflow management system according to [3]. [5] The workflow includes steps for executing tasks. The execution information includes the execution status for each step of executing a task. The display unit receives a designation of an aggregation axis and displays, based on the execution information, a dashboard screen showing an aggregation result of the execution status of tasks on the designated aggregation axis. The workflow management system according to any one of [1] to [4]. [6] The workflow management system further includes a reception unit. The reception unit receives registration of a maintenance person in charge of a workflow for each workflow. The display unit causes a maintenance reminder to be displayed on the user terminal of the maintenance person in charge. The workflow management system according to any one of [1] to [5]. [7] The generation instruction is an instruction sentence in natural language, The generation unit transmits the generation instruction to a generation device. Based on the setting information received from the generation device, the workflow information including one or more pieces of step information related to steps included in the workflow is generated. The workflow management system according to any one of [1] to [6]. [8] A workflow management method executed by a computer, A display step of displaying a workflow generation screen, A generation step of generating a workflow based on a generation instruction input via the workflow generation screen, When an execution instruction for a workflow is received, an execution information including the execution status of one or more steps included in the workflow is generated and registered in association with the workflow. In the display step, a screen showing the flowchart of the workflow and the execution status is displayed. Two or more pieces of the execution information are associated with the workflow. Workflow management method. [9] A computer program for causing the computer to execute the workflow management method according to [8].

[0008] According to the invention according to [1], the execution status of the same workflow can be managed simultaneously for multiple cases, etc.

[0009] According to the invention according to [2], even when multiple executions of the same workflow are in progress, a list display and management of the multiple execution statuses related to the same workflow can be performed.

[0010] According to the invention according to [3], the status of the tasks that the person in charge of executing the tasks related to the workflow is in charge of can be displayed and managed in a list.

[0011] According to the invention according to [4], the person in charge to whom the tasks in the workflow are assigned can execute the tasks, and the execution status of the workflow can be managed in accordance with the execution.

[0012] According to the invention according to [5], the execution status of the tasks can be easily grasped.

[0013] According to the invention according to [6], continuous maintenance of the workflow by the maintenance person in charge can be performed.

[0014] According to the invention according to [7], a workflow can be automatically generated based on an instruction in natural language.

Brief Description of the Drawings

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Best Mode for Carrying Out the Invention

[0016] Hereinafter, a more detailed description will be given with reference to the accompanying drawings. The drawings show preferred embodiments. However, it can be implemented in many different forms and is not limited to the embodiments described in this specification.

[0017] For example, in this embodiment, the configuration, operation, etc. of the workflow management system will be described. However, the same effects can also be achieved by the method, apparatus, computer program, etc. executed. The program may be provided as a non-transitory computer-readable recording medium or may be provided so as to be downloadable from an external server.

[0018] In this embodiment, an example will be described in which a user of the workflow management system belonging to a company and performing work on-site creates a workflow and performs work using the created workflow. Further, the workflow management system in this embodiment is a workflow management system that can handle cases where the same workflow is executed multiple times, for example, when responding to inquiries in the same workflow for multiple customers. Note that the range of information that can be viewed and the range of operations that can be performed by the user of the workflow management system may differ depending on the position, etc.

[0019] A workflow is a flow of processing related to work. The workflow in this embodiment includes one or more steps, and the processing for each step is executed in order to realize the flow of processing of the work related to the workflow. Further, the workflow in this embodiment includes either or both of steps related to processing (task execution processing) executed by a person such as a user and steps related to processing (automation processing) automatically executed by the function of a computer.

[0020] In this embodiment, the workflow system can further execute the processes included in the workflow by using tools such as an API (Application Programming Interface) to utilize functions of tool providing systems such as chat, invoice creation, and cloud storage. When the workflow management system includes a process of providing data obtained from a specific tool providing system in the workflow to another tool providing system, such as registering data input by a customer via a form in a customer information management system, the workflow management system performs processes for cooperation of a plurality of tool providing systems by obtaining and registering data from other tool providing systems.

[0021] Also, in this embodiment, the process in the case where the workflow management system uses an API or the like to generate a workflow using the function of a generation system will be described. However, for example, the workflow management device itself may have a function of performing a process related to generating a workflow based on a natural language instruction.

[0022] <System Configuration> FIG. 1 is a block diagram showing the configuration of a system according to an embodiment. As shown in FIG. 1, the workflow management system 0 includes a workflow management device 1 and a user terminal 2, which are configured to be communicable via a network 5. In FIG. 1, only one user terminal 2 is illustrated, but there may be a plurality of user terminals.

[0023] Also, in this embodiment, the workflow management device 1 is communicably connected to an external generation system 3 and a tool providing system 4 via a network 5, and is configured to be able to execute processes related to generating a workflow and using functions of tools.

[0024] As the workflow management device 1, one or more server devices such as a general-purpose server or a personal computer can be used.

[0025] As the user terminal 2, terminal devices such as personal computers, smartphones, and tablet terminals can be used. The user terminal 2 connects to the workflow management device 1 by executing a workflow management device utilization program, and executes processing related to the management of the workflow described later. In the present embodiment, the workflow management device utilization program is a browser application pre-installed or pre-downloaded on the user terminal 2, but it may also be a client application downloaded from a program providing device (not shown).

[0026] The generation system 3 includes a generation device 31. As the generation device 31, server devices such as general-purpose servers and personal computers can be used. When the generation device 31 receives instructions in natural language such as a large language model, it stores a model that outputs an answer, and uses this model (generation model) to perform processing related to the generation of a workflow. In the present embodiment, processing related to the generation of a workflow is performed using the generation model stored in the generation device 31, but the workflow management device 1 itself may store the generation model and perform processing related to the generation of a workflow. The generation model in the present embodiment is a model that has pre-loaded structured data and has been trained to generate data related to a structured flow when receiving instructions regarding the generation of a workflow in natural language.

[0027] The tool providing system 4 includes a tool providing device 41. As the tool providing device 41, server devices such as general-purpose servers and personal computers can be used. In FIG. 1, only one tool providing system 4 and tool providing device 41 are shown, but there may be a plurality of them.

[0028] The network 5 is an IP (Internet Protocol) network, but there are no restrictions on the type of communication protocol, the type of network, etc.

[0029] <Hardware Configuration> FIG. 2 is a hardware configuration diagram of the workflow management device 1 and the user terminal 2.

[0030] FIG. 2(a) is a hardware configuration diagram of the workflow management device 1. As shown in FIG. 2(a), the workflow management device 1 includes a processing unit 101, a storage unit 102, and a communication unit 103, and is used to exert the functions of each part and each process.

[0031] The processing unit 101 has a processor such as a CPU capable of executing an instruction set, and executes an OS, a workflow management program, etc. The storage unit 102 has a volatile memory such as a RAM capable of storing an instruction set, and a non-volatile recording medium such as an HDD or an SSD capable of recording an OS, a workflow management program, etc. Note that the storage unit 102 may be provided in a distributed manner in a plurality of server devices or the like. The communication unit 103 has an interface for connecting to the network 5, executes communication control with the network 5, and performs input / output of information.

[0032] FIG. 2(b) is a hardware configuration diagram of the user terminal 2. As shown in FIG. 2(b), the user terminal 2 has a processing unit 201, a storage unit 202, a communication unit 203, an input unit 204, and an output unit 205, and is used to exert the functions of each part and each process.

[0033] The processing unit 201 has a processor such as a CPU capable of executing an instruction set, and executes programs such as an OS and a workflow management device utilization program. The storage unit 202 has a volatile memory such as a RAM capable of storing an instruction set, and a non-volatile recording medium such as an HDD or an SSD capable of recording an OS and application programs (such as a workflow management device utilization program) that can use a plurality of services including a workflow management service. The communication unit 203 has an interface for connecting to the network 5, executes communication control with the network 5, and performs input / output of information. The input unit 204 has an input device such as an operation input device capable of input processing, such as a touch panel or a keyboard. The output unit 205 has an output device such as a display device capable of display processing, such as a display.

[0034] <Data configuration in the workflow management system 0> Hereinafter, an example of the data configuration of the data used in the workflow management system 0 in the present embodiment will be described. The various data described later are stored in the storage unit 102 and used for various processes executed in the processing unit 101.

[0035] The user information is information about a user who belongs to a company and uses the workflow management system 0. In the present embodiment, the user information includes the user's identification information (such as user ID), user name, email address, and organization information related to the organization to which the user belongs, etc. Note that an email address may be used as the user's identification information. Note that permissions such as the range that can be viewed and the range that can be operated may be set for each user. For example, a user with a higher-level permission such as a supervisor may be configured to be able to view and operate the information of users such as their subordinates.

[0036] In the present embodiment, the user is identified by logging in using the identification information (such as user ID) and password in advance. Therefore, in the processes described later, the processes are performed using the user information of the user specified by the identification information input in the pre-performed login and information related to the workflow such as the associated execution information.

[0037] Workflow information is information about a workflow generated based on various settings (generation instructions) input by a user, and includes a workflow name. Further, the workflow information includes one or more pieces of step information regarding steps included in the workflow, and includes relationship information regarding the relationship between steps such as the execution order of steps and the execution dependency such that execution starts when a specific step is completed. The relationship information may be information regarding the position and connection relationship of steps in a flowchart. Further, the workflow information further includes start conditions. For example, when conditions set in the start conditions are satisfied, such as when the "start button" is pressed or an inquiry email is received, the execution of the workflow starts. In the present embodiment, the workflow information is stored in association with user information of a maintenance user who is responsible for maintaining the workflow using identification information such as a user ID. In business, in order to review the workflow and always perform business in an optimal way, the maintenance user performs confirmation, correction, etc. as maintenance of the workflow associated with himself / herself.

[0038] Step information is information regarding one or more steps included in a workflow, and includes a processing type. The processing type is the type of processing executed in a step, and in the present embodiment, includes processing executed by a person (task execution processing) and automated processing. Further, even the automated processing includes processing related to a tool and processing not using a tool. The processing using a tool is processing that utilizes functions of a tool providing device 41 such as data acquisition, input, and message transmission, which is executed by accessing the tool providing device 41. Further, the step information in the present embodiment includes different information depending on the type of processing (processing type) executed in the step. Further, when referring to information in other steps, such as using the result of processing executed in another step in a step, the step information may include reference source step information regarding the reference source step. Note that the reference source step information includes identification information of the reference source step and information specifying which data of the reference source step is to be referred to.

[0039] In the present embodiment, the step information related to the process (task execution process) executed by a person includes step identification information, step name, process type, person-in-charge information, and process content information. The person-in-charge information is information related to the person in charge of the task. In the present embodiment, it includes either or both of information for identifying the person in charge of the task (such as user name or user ID) and information for identifying the organization in charge (such as organization name or organization ID). In the present embodiment, the step information is associated with user information or the like using the person-in-charge information. Note that the person in charge set in the workflow information at the time of creation (person in charge at creation) may be different from the person in charge who actually executes the task (person in charge of execution). The process content information in the task execution process is information related to the content of the task to be executed. For example, in the case of a data input operation, it is the items to be input and the data format of the items (such as character string or number). Further, the step information related to the task execution process may include information related to the task such as the deadline of the task. When referring to information of other steps, such as displaying the data input in the previous step when displaying the task execution screen, the process content information related to the task execution process may include the reference source step information.

[0040] In this embodiment, the step information related to the automation process includes step identification information, step name, process type, and process content information. Note that the process type related to the automation process is, for example, "judgment", "waiting", etc. for an automation process that does not use a tool, and for a process related to a tool, it is "mail application", "chat tool", "invoice creation tool", etc., and may further include more detailed process content (for example, mail sending using a mail application, etc.). The process content information related to the automation process is information regarding settings on what kind of process to execute, which differs depending on the process type, and includes information regarding the processing target and details of the process performed on the processing target. The process content information in this embodiment is, for example, the conditions in judgment for a judgment based on the results of other steps, the period to wait, the content of the message in sending a mail or message, the acquisition source in the case of data acquisition, information regarding the content of the data to be registered in a tool such as cloud storage and the registration destination, etc. Also, for example, when executing a process using information from other steps, such as displaying data input in a form obtained in other steps in a chat, the process content information related to the automation process may include the source step information. Further, when the process is executed on the condition of reaching a specified time, the process content information may include information regarding the start time, etc.

[0041] Execution information is information related to the execution of a workflow, and includes an execution name such as a case name, and step execution information related to the execution of each step included in the workflow. The step execution information includes the execution status of each step (in execution / awaiting / complete / failed / canceled, etc.), and is stored in association with the step information related to the corresponding step. Further, the step execution information may include execution result information related to the result of the execution of the process in the step (for example, input data, acquired data, etc.). The execution result information is information related to the result of the execution of the process for each step, and includes, for example, data acquired in the process and the result of the determination. Further, the execution result information includes the start date and time when the execution status of the step becomes in execution, and the completion date and time when the execution status of the step becomes complete, and may also include information related to the date and time when the execution status in the step is changed. For example, since the person in charge set at the time of creating the workflow (person in charge at creation time) may be busy and unable to respond at the time of executing the workflow, and it may be necessary to assign the person in charge to another user, in this embodiment, the step execution information related to the workflow including the processes executed by a person includes the person-in-charge information related to the person in charge (person in charge of execution) who executes the task for each step. Note that when the person in charge set at the time of creating the workflow is in charge of executing the task as it is (the person in charge at creation time is the person in charge of execution), the person-in-charge information at the time of creation acquired from the workflow information may be used as the person-in-charge information included in the execution information (person-in-charge information related to the person in charge of execution), or the execution information may not include the person-in-charge information. Note that the execution status and person-in-charge information for each step are stored in association with the step information related to the corresponding step.

[0042] Since the workflow may be changed after it is created, in the present embodiment, when an instruction to execute the workflow is given, the workflow management apparatus 1 copies the workflow information at the start time of execution, registers the copied workflow information in association with the generated execution information, and performs processing related to the execution of the workflow using the copied workflow information. Therefore, in the present embodiment, the execution information associated with the workflow information is further associated with the workflow information at the start time of execution obtained by copying at the start time of execution. The workflow management apparatus 1 performs processing related to the execution of the workflow using the workflow information at the start time of execution obtained by copying the workflow information at the time when the execution instruction is given, so that even if some change is made to the original workflow, the processing can be executed without problems. However, if it is not assumed that the original workflow will be changed, the processing related to the execution of the workflow may be configured to be performed using the workflow information of the original workflow.

[0043] <Functional Configuration of Workflow Management System 0> In FIG. 1, the functional configuration in the workflow management system 0 is further shown. As shown in FIG. 1, the workflow management apparatus 1 includes a display unit 11, a reception unit 12, a generation unit 13, a data registration unit 14, an execution unit 15, and an execution status management unit 16. This is realized by the information processing by software (a workflow management program stored temporarily or non-temporarily in the storage unit 102) being specifically realized by hardware (the processing unit 101 or the like). Further, devices such as the user terminal 2 and the tool providing apparatus 41 may include part or all of the functional configurations described later and execute part or all of the processing described later.

[0044] The display unit 11 performs a process of displaying various screens such as a workflow generation screen and a task execution screen based on the workflow generated in the generation unit 13 or various information stored in the storage unit 102 such as workflow information and execution information. In the present embodiment, the display unit 11 executes, as a process for displaying a screen, a process of transmitting various data including HTML data necessary for screen display to the user terminal 2, but other processes may be executed as a process for displaying a screen.

[0045] The reception unit 12 receives various inputs such as a generation instruction input in the user terminal 2, and performs a process of passing them to other functional configurations such as the generation unit 13 or storing them in the storage unit 102. In the present embodiment, the reception unit 12 stores various settings included in the generation instruction in the storage unit 102 as workflow information.

[0046] The generation unit 13 performs a process of generating a workflow based on the generation instruction received from the user terminal 2. In the present embodiment, the generation unit 13 executes, as a process of generating a workflow, a process of generating a flowchart of the workflow based on the received generation instruction, but a process of generating structured flowchart information may be executed as a process of generating a workflow. Note that the generation unit 13 receives, as a generation instruction, settings regarding steps included in the workflow received from the user terminal 2 and the relationship between the steps, and generates a workflow based on the received generation instruction. Further, the generation unit 13 may store various settings (generation instructions and setting information) regarding the workflow in the storage unit 102 as workflow information.

[0047] The generation unit 13 further receives, from the user terminal 2, a sentence described in natural language regarding what workflow is to be generated by the user as a generation instruction, and transmits the received generation instruction to the generation device 31. When the generation device 31 generates setting information related to the parameters of the workflow, the generation unit 13 receives the setting information from the generation device 31 and generates a workflow based on the received setting information. In the present embodiment, the generation device 31 is a device that stores a generation model that has previously loaded structured data related to the flow. The generation device 31 uses the generation model to generate data (setting information) related to the structured workflow based on the data of the template workflow and transmits it to the workflow management device 1. The setting information is information related to the parameters of the workflow, and includes parameters related to the steps included in the workflow and parameters related to the relationship between the steps. Further, the setting information may include any information as long as it is information related to the parameters of the workflow information and the step information, such as information related to the type of tool to be used and the content of the process as information related to the automation process.

[0048] When the reception unit 12 receives an execution instruction for the workflow, the data registration unit 14 generates execution information for the workflow and stores it in the storage unit 102 in association with the workflow information related to the workflow for which the execution instruction has been given. Further, the data registration unit 14 stores the execution status for each step included in the generated execution information and the person-in-charge information related to the person in charge in association with the step information related to the corresponding step.

[0049] The execution unit 15 executes the processes included in the workflow based on the workflow information and the step information included in the workflow information. In particular, the execution unit 15 executes the processes in the automated steps included in the workflow. Note that if the process is related to a tool, the execution unit 15 transmits a request for executing the process to the tool providing device 41. If the process does not use the tool, the execution unit 15 performs processes such as data processing and judgment based on the acquired data as processes for executing the processes in the automated steps. In the present embodiment, as the process in the automated step, the execution unit 15 requests the tool providing device 41 to perform processes such as sending emails and messages using a mail application or a chat tool, and acquiring and registering data as processes in a database system such as a cloud storage or a customer management system. Further, for example, when there is a value obtained as a result of execution, such as judgment based on the results of other steps or acquisition of data from a tool being performed as a process in the step, the execution unit 15 may store information (execution result information) regarding the result of execution of the step, which is included in the step execution information, in the storage unit 102. Also, in the present embodiment, the execution unit 15 uses the functions of another system (tool providing system 4) by using an API, but may perform operations on the tool providing system 4, such as data input and output, as processes in the step by using RPA (Robotic Process Automation).

[0050] The execution status management unit 16 performs a process of updating the execution status for each step included in the execution information in accordance with the progress of the workflow. In the present embodiment, when the process in a step is a task execution process, when the reception unit 12 receives task execution information which is execution result information related to the execution of a task, the execution status management unit 16 sets the execution status of the step related to the task as completed. Further, when the step is an automated process, the execution status management unit 16 sets the execution status of the step as completed when the process related to the step is completed. Further, the execution status management unit 16 may change the execution status of a step based on a report regarding the execution status received from the user terminal 2, or for example, if an input of "business negotiation established" by the user is received, it is set as completed, and if an input of "business negotiation failed" is received, it is set as failed, etc., and the execution status of the step may be changed based on the execution result information (task execution information) obtained as a result of the execution of the executed step.

[0051] <Workflow management method> Hereinafter, the process related to the management of the workflow will be described with reference to FIGS. 3 and 5. FIGS. 3 and 5 are flowcharts of the process related to the management of the workflow in the present embodiment. Note that the flow of the process shown in FIGS. 3 and 5 is an example, and the process may be executed in a flow different from the example shown in the figures.

[0052] Hereinafter, the process related to the generation of the workflow will be described with reference to FIG. 3. In step S101, the display unit 11 causes the user terminal 2 to display a workflow generation screen. In step S201, the user terminal 2 receives various settings input via the displayed workflow generation screen as generation instructions and transmits them to the workflow management device 1. The generation unit 13 generates a workflow based on the generation instructions received from the user terminal 2 (S102). The display unit 11 performs a process of displaying the workflow generated by the generation unit 13 (S103). Further, a process related to the modification of the workflow may be performed in the same procedure as the workflow generation process shown here.

[0053] FIG. 4 is an example of a screen display of a workflow generation screen displayed on the user terminal 2 by the display unit 11. In the present embodiment, processing related to the modification of the workflow is performed using a screen having the same configuration as the workflow generation screen shown in FIG. 4.

[0054] The workflow generation screen W1 shown in FIG. 4(a) is a screen for generating a workflow, and includes a workflow element display area W11 and a workflow display area W12. Note that the workflow generation screen W1 shown in FIG. 4(a) is an example of a screen display at a stage where no step is selected.

[0055] The workflow element display area W11 is an area for selecting workflow elements related to processes included in the workflow. In the present embodiment, in the workflow element display area W11, the process type of the step arranged in the workflow can be selected, but other settings may be configured. In the example shown in FIG. 4(a), the major classification of the process type is displayed. For example, by pressing the "link button", detailed process types such as a mail application and a chat tool can be selected and arranged in the workflow display area W12.

[0056] The workflow display area W12 is an area for displaying the workflow. The workflow display area W12 may display a workflow being created or a completed workflow. Further, when the workflow is generated by the generation unit 13 based on the setting information acquired from the generation device 31, the workflow display area W12 may display the generated workflow.

[0057] In this embodiment, the user arranges workflow elements related to tasks, automated processes, etc. in the workflow element display area W11 in the workflow display area W12 by means of a drag-and-drop operation, and inputs various settings related to the workflow, such as the steps included in the workflow and the order of execution of the steps, by connecting the workflow elements to each other. The user terminal 2 receives various settings related to the workflow input by the user as generation instructions and transmits them to the workflow management device 1. In this embodiment, the user terminal 2 transmits a generation instruction when the "Save" button is pressed, but a generation instruction may be transmitted each time an operation by the user is performed, such as when a drag-and-drop operation is performed. In this embodiment, the generation unit 13 generates a workflow based on the input generation instruction, and the display unit 11 displays the generated workflow, whereby a screen as shown in Fig. 4(a) is displayed.

[0058] In the workflow element display area W11 of Fig. 4(a), it is further possible to select a lane as a workflow element. A lane is a lane for classifying the processing in a workflow. In this embodiment, lanes are divided for each person in charge (person in charge organization or person in charge), but lanes may be divided by classification based on the content of processing, such as the type of tool used. Also, in this embodiment, when arranging the lanes, the person in charge (person in charge organization or person in charge) is set for each lane, and the person in charge (person in charge organization or person in charge) set at this time may be registered in the step information or step execution information as the person in charge of the steps (especially tasks) included in the lane.

[0059] The workflow generation screen W1’ shown in FIG. 4(b) is an example of the screen display when the task execution step with the step name “Request” among the steps displayed on the screen is selected by being pressed. The workflow generation screen W1’ includes a step setting input area W13. The step setting input area W13 is an area for inputting settings for each step included in the workflow. The step setting input area W13 shown in FIG. 4(b) is an example when the task execution step is selected, and accepts a step name (task name), a task content description, an in-charge organization, an in-charge person, a deadline, reference items, and input items. In the present embodiment, various settings for each step input in the step setting input area W13 are included in the generation instruction and transmitted to the workflow management device 1, and stored in the storage unit 102 as step information. Note that the items that can be input in the step setting input area W13 differ depending on the type of process. For example, in the case of sending an email or a message, it is the recipient and the content to be sent (specifying and referring to other steps when using the results of other steps), in the case of data acquisition, it is the storage location and items of the acquisition source (specifying and referring to other steps when using the results of other steps), in the case of data registration, it is the items of the data to be registered and the storage location and items of the registration destination (specifying and referring to other steps when registering the results of other steps), in the case of determination, it is the data to be determined (specifying and referring to other steps when using the results of other steps) and the determination conditions, and in the case of data processing such as OCR (Optical Character Reader), it is the data to be processed, etc.

[0060] In the step setting input area W13, when the "+" button displayed on the right side of the reference item is pressed, an input field for inputting settings related to the reference item is added, and the specification of other steps to be referred to and the settings related to the item to be referred to can be accepted. Similarly, when the "+" button on the right side of the input item is pressed, an input field for inputting settings related to the input item is added, and the item name and data format can be accepted. Various settings for each step input in the step setting input area W13 when the processing type is task execution processing are used for the display of the task execution screen as shown in Fig. 6(a).

[0061] Hereinafter, the processing related to the execution of the workflow will be described with reference to Fig. 5. In step S211, when an execution instruction for the workflow is transmitted from the user terminal 2, the data registration unit 14 generates execution information and registers the generated execution information in association with the workflow information of the workflow for which execution is instructed (S111). In the example shown in Fig. 5, the execution of the workflow is started based on an instruction from the user terminal 2. However, for example, the workflow may be started by satisfying set conditions such as receiving an email or a message, or reaching the date and time set as the start date and time of the workflow. At this time, the workflow management device 1 may further include a start determination unit, and the start determination unit may be configured to determine the start based on the start conditions included in the workflow information and issue an execution instruction to the data registration unit 14. The execution unit 15 executes the processing related to the step based on the step information (S112). The execution status management unit 16 updates the execution status based on the result of the execution of the processing in the step (execution result information) (S113). The workflow management device 1 repeatedly executes the processing related to the execution of the step and the change of the execution status (S112 to S113) until all the steps included in the workflow are completed.

[0062] FIG. 6(a) is a diagram showing an example of the screen display of the task execution screen W2 displayed on the user terminal 2. The task execution screen W2 is a screen for the user to execute a task, which is displayed based on the step information. In the example shown in FIG. 6(a), it is a screen for receiving input regarding items (request title and request content) requested to be input in the step information. When the "Complete" button is pressed, the input content is transmitted to the workflow management device 1 as task execution information. Further, when it is set in the step information to refer to information of other steps, the task execution screen W2 displays execution result information in other steps, such as the content input in other steps.

[0063] FIG. 6(b) is an example of the screen display of the execution status list display screen W3 displayed by selecting a workflow. The display unit 11 displays the execution status list display screen W3 as shown in FIG. 6(b) based on the workflow information of the selected workflow and the execution information associated with the workflow information. Further, the display unit 11 may use other data associated with the workflow information regarding the selected workflow for screen display. The execution status list display screen W3 is a screen for displaying a list of execution statuses, and displays the flowchart of the workflow of the selected case in the execution status list. Further, an icon indicating the execution status such as completed or in execution is displayed in the upper right of the icon for each step in the flowchart of the selected case. Furthermore, based on the execution status for each step included in the step execution information, the execution status of the workflow is displayed beside the case name. In the present embodiment, the execution status of the workflow is further determined by the position of the step in the workflow specified by the execution status for each step and the relationship information according to whether all steps of the workflow are completed, the latest step is in progress (being executed), etc.

[0064] FIG. 7(a) is an example of the screen display of a task list display screen W4 for displaying a list of tasks. The display unit 11 displays the task list display screen W4 based on the step information and the execution information. Further, information associated with the execution information such as workflow information may be used for the screen display. In particular, the display unit 11 uses the step information and the step execution information related to the task execution process to display the task list display screen W4 as shown in FIG. 7(a). The task list display screen W4 includes a search condition input area W41 and a task list W42. The search condition input area W41 is an element of the screen display for inputting the conditions (search conditions) of the tasks to be displayed in the task list. In the present embodiment, the team (organization) and the conditions related to the execution status can be received as search conditions. The search condition input area W41 may receive conditions such as the person in charge as conditions for searching for tasks. The task list W42 is a list of tasks, and displays the workflow name based on the workflow information, the task name (step name), the person in charge, the status (execution status), the time of task generation, and the deadline. The display unit 11 displays a list of information related to the tasks that meet the conditions based on the search conditions input in the search condition input area W41.

[0065] The display unit 11 receives the aggregation axis input on the user terminal 2, aggregates the execution status according to the aggregation axis based on the step execution information, and displays a dashboard screen showing the aggregation result of the execution status. The aggregation axis is the axis for aggregating the execution status of tasks. In this embodiment, it is an aggregation axis including any one or more items among the person in charge, the responsible organization, the type of execution status (pending, in execution, completed, failed, canceled, etc.), the start date of the task, the completion date of the task, the category of the task, the number of days overdue, and the priority. The workflow management device 1 aggregates the number of tasks in the case status corresponding to the conditions set by the user as the aggregation axis (for example, the number of tasks not started (not completed) by a certain team during a specific period), and displays it on the dashboard screen. At this time, the display unit 11 displays a dashboard screen including an aggregation axis input area for inputting the aggregation axis and the aggregation result of the execution status in the aggregation axis input in the aggregation axis input area. Also, for example, the aggregation results of the execution status on different aggregation axes, such as the aggregation result when the type of execution status is "in execution" and the aggregation result when it is "completed", may be respectively displayed on the dashboard screen.

[0066] FIG. 7(b) is an example of the screen display of the dashboard screen W5 for displaying the execution status of tasks. The display unit 11 displays a screen as shown in FIG. 7(b) based on the step execution information including the execution status. In the example shown in FIG. 7(b), the dashboard screen W5 is a screen for displaying the status of tasks assigned to a specific person in charge, which is displayed based on the step execution information of the tasks assigned to the specific person in charge. However, for example, it may be a screen for displaying the execution status of tasks assigned to users belonging to a specific organization, based on the step execution information of the tasks assigned to the users in the specified group. In the dashboard screen W5 shown in FIG. 7(b), the number of tasks (aggregation result of the execution status) for each type of execution status (pending, in progress, completed, failed, canceled) is displayed. In the example shown in FIG. 7(b), the numbers displayed at the upper part of the screen are the number of tasks for each type of execution status at the time of aggregation, but the number of tasks for each type of execution status at the specified point in time may be displayed. Also, the graph of the task execution status at the lower part of the screen is a graph for displaying the execution status of tasks for each unit period (one week in the example shown in FIG. 7(b)). Here, the execution status at the end of the unit period of tasks started after the start time of the unit period is used for the aggregation of the number of cases. However, simply, the number of cases for each type of execution status of the tasks at the end time of the unit period may be displayed. Also, in the example shown in FIG. 7(b), an example is described where the type of execution status and the person in charge are set as the aggregation axes and the aggregation result is displayed as a numerical value and a bar graph. However, there is no limitation on the display format of the aggregation result on the dashboard screen W5. For example, it may be a pie chart, a line graph, or other general graph expressions or table formats, etc.

[0067] In addition, maintenance personnel are registered for each workflow, and the display unit 11 causes the registered maintenance-responsible user terminal 2 to display a notification for reminding maintenance. In this embodiment, the maintenance notification is configured to be displayed periodically, but it may be configured to be notified based on other conditions. Further, the display unit 11 may display a workflow generation screen W1 as shown in FIG. 4 in the notification to the maintenance personnel, prompt the confirmation and correction of the workflow, or prompt maintenance by displaying a message. Further, the workflow management device 1 may further include an advice generation unit, generate an instruction text based on the workflow information, transmit it to the generation device 31, and the display unit 11 may display the advice generated by the generation device 31 on the user terminal 2 as a notification. Further, the display unit 11 may display advice regarding the workflow to be created, for example, advise to create a workflow regarding the creation of an invoice if the workflow around the invoice is not well-organized based on the created workflow. At this time, the generation device 31 may be processed to generate advice regarding a workflow that is better generated in the same manner as the generation of maintenance advice.

Explanation of Signs

[0068] 0 Workflow management system 1 Workflow management device 11 Display unit 12 Reception unit 13 Generation unit 14 Data registration unit 15 Execution unit 16 Execution status management unit 101 Processing unit 102 Storage unit 103 Communication unit 2 User terminal 3 Generation system 3 31 Generation device 31 4 Tool provision system 41 Tool provision device

Claims

1. 1. A workflow management system, comprising: a display unit that displays a workflow generation screen; a generation unit that generates a workflow and registers workflow information based on a generation instruction input via the workflow generation screen; a data registration unit that, when receiving an execution instruction for a workflow to start a case, generates execution information for each case, the execution information including an execution status of one or more steps included in the workflow for which the execution instruction has been given and a case name, and registers the execution information in association with the workflow information of the workflow for which the execution instruction has been given; A reception unit that receives a designation of a workflow to be displayed as a list, The execution information for two or more cases is associated with the workflow information; the display unit displays an execution status list display screen including a list of case names of cases executed for the specified workflow, based on workflow information related to the specified workflow and the execution information associated with the workflow information; the execution status list display screen is a screen showing a flowchart including an execution status for each step of the case executed in relation to the specified workflow; Workflow management system.

2. The workflow includes a step of executing a task, The execution information includes: responsibility information regarding a person in charge of each task; The execution status is a status of execution for each step, The display unit displays a list of tasks handled by a designated person in charge based on the execution information of the designated person in charge. The workflow management system of claim 1 .

3. The workflow management system further comprises an execution status management unit, The display unit displays a task execution screen for executing a task of a step whose execution status is being executed on a user terminal of a person in charge based on the execution information; the receiving unit receives task execution information input via the task execution screen; The execution status management unit sets the execution status of the step to be complete. The workflow management system of claim 2 .

4. The workflow includes a step of executing a task, the execution information includes the execution status for each step of executing a task; the display unit receives a designation of an aggregation axis, and displays a dashboard screen showing an aggregation result of the execution status of the tasks on the designated aggregation axis based on the execution information. The workflow management system of claim 1 .

5. The reception unit receives registration of a workflow maintenance person for each workflow, The display unit displays a maintenance reminder on the user terminal of the maintenance person. The workflow management system of claim 1 .

6. The generation instruction is an instruction sentence in a natural language, The generation unit transmits the generation instruction to a generation device; generating the workflow information including one or more pieces of step information related to steps included in the workflow based on the setting information received from the generating device; The workflow management system of claim 1 .

7. 1. A computer-implemented method for managing workflow, comprising: a display step of displaying a workflow generation screen; a generation step of generating a workflow and registering workflow information based on a generation instruction input via the workflow generation screen; a data registration process for, when receiving an execution instruction for a workflow to start a case, generating execution information for each case, the execution information including an execution status of one or more steps included in the workflow for which the execution instruction has been given and a case name, and registering the execution information in association with the workflow information of the workflow for which the execution instruction has been given; A receiving step of receiving a designation of a workflow for displaying a list, The execution information for two or more cases is associated with the workflow information; In the display step, an execution status list display screen including a list of case names of cases executed for the designated workflow is displayed based on workflow information related to the designated workflow and the execution information associated with the workflow information, the execution status list display screen is a screen showing a flowchart including an execution status for each step of the case executed in relation to the specified workflow; Workflow management methods.

8. A computer program product that causes a computer to execute the workflow management method according to claim 7.

Images