Information processing device, control method for information processing device, and program

The workflow processing server integrates manual and automated tasks to manage workflow progress, addressing visibility issues in outsourcing scenarios and ensuring uninterrupted tracking.

JP2026066728APending Publication Date: 2026-04-17CANON KK
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
CANON KK
Filing Date
2024-10-07
Publication Date
2026-04-17

AI Technical Summary

Technical Problem

Existing workflow automation systems struggle to manage the progress of operations when manual tasks are involved, particularly in outsourcing scenarios, leading to interruptions in workflow visibility and management.

Method used

A workflow processing server that defines manual operations as a first workflow, links tasks to an input interface for progress tracking, and integrates with automated workflows to manage the overall operation status.

Benefits of technology

Enables continuous management of workflow progress even with manual operations, ensuring uninterrupted visibility and tracking of outsourced tasks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026066728000001_ABST
    Figure 2026066728000001_ABST
Patent Text Reader

Abstract

Even in situations where manual operation involving human hands may be required, the overall progress of the work can be managed in a more optimal manner. [Solution] The workflow processing server 200 defines the first task, which is performed manually, as a first workflow containing one or more tasks. The workflow processing server 200 controls the display of buttons 513 to 517, each individually associated with one or more tasks included in the first workflow. The workflow processing server 200 accepts input of the progress status of each of the one or more tasks from the user via the button associated with that task. The workflow processing server 200 manages the execution status of the series of tasks as a workflow related to the series of tasks by connecting the first workflow to a part of the second workflow defined for the second task, which is automated, among the series of tasks.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus, a control method for the information processing apparatus, and a program.

Background Art

[0002] In recent years, efforts have been made to improve work efficiency by automating the workflows of various regular operations. For example, systems that support workflow automation have also been proposed. Such a system manages individual processing units executed as workflows as tasks, and in some cases, even tasks performed manually by a user can be defined by replacing them with computer processing as the tasks. Also, by using such a system, for example, a user can define a workflow by sequentially selecting icons associated with desired tasks via a UI (User Interface) provided by the system. Further, the system manages such that tasks associated with the icons are sequentially executed in accordance with the order of the icons selected via the UI when defining the workflow. With such a mechanism, it becomes possible to automate and improve the efficiency of desired operations. Also, since it becomes possible to visualize the so-called progress status, such as which task of the workflow is being executed at each time, via the UI provided to the system, an effect of improving the progress management of operations can also be expected.

[0003] One example of a workflow requiring automation is one that involves tasks using a multifunction printer (for example, tasks that specify print or scan instructions for the multifunction printer). Specifically, in the commercial printing market, printing tasks can arise in response to diverse user order information. Printing companies are improving work efficiency by automating such printing workflows. Furthermore, in office environments, mechanisms have been proposed that enable the automation of routine workflows, including scanning and printing, to suit the user's tasks. Patent Document 1 discloses a technology that enables the automation of tasks by associating tasks that meet predetermined conditions with a workflow. [Prior art documents] [Patent Documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2023-24416 [Overview of the project] [Problems that the invention aims to solve]

[0005] Depending on the industry and market, workflows may involve tasks that are outsourced to external vendors. For example, in the commercial printing market, if a client requests foil stamping (applying gold or silver foil to paper) or gloss finishing (laminating a film onto the paper surface to give it shine and strength), the printing company may outsource these processes to a subcontractor. When such workflows involving outsourcing occur, manual operations involving human intervention, such as communicating the details of the outsourcing by phone or in person, may be required. When tasks that are difficult to automate by computer occur, the task processing of the overall workflow may be interrupted at the point where manual operations (non-automated processing) are performed. In such situations, it may be difficult to visualize the progress of the work from the point where the task processing of the workflow is interrupted (the part where manual operations are performed).

[0006] In view of the above problems, the present invention aims to enable the management of the overall progress of operations in a more favorable manner, even in situations where manual operation by human hands may occur. [Means for solving the problem]

[0007] The concession processing device according to the present invention is characterized by comprising: a definition means for defining a first operation performed manually among a series of operations as a first workflow including one or more tasks; a display control means for controlling the display of an input interface to which each of the one or more tasks included in the first workflow is individually linked; a reception means for receiving input from a user regarding the progress status of each of the one or more tasks on which the input interface is displayed; and a management means for managing the execution status of a series of operations as a workflow related to the series of operations by connecting the first workflow to a part of a second workflow defined for a second operation that has been automated among the series of operations. [Effects of the Invention]

[0008] According to the present invention, even in situations where manual operation by human hands may occur, it becomes possible to manage the progress of the entire operation in a more favorable manner. [Brief explanation of the drawing]

[0009] [Figure 1] This diagram shows an example of the system configuration of an information processing system. [Figure 2] This diagram shows an example of the hardware configuration of a workflow processing server. [Figure 3] This is a sequence diagram showing an example of the processing performed by the workflow processing server. [Figure 4] This diagram shows an example of the display screen for an outsourcing workflow application. [Figure 5] This diagram shows an example of a task status management screen. [Figure 6] This flowchart shows an example of the processing performed by a workflow processing server. [Figure 7] This diagram shows an example of the display screen of a printing company's workflow application. [Figure 8] This flowchart shows an example of the processing performed by a workflow processing server. [Modes for carrying out the invention]

[0010] Preferred embodiments of this disclosure will be described in detail below with reference to the attached drawings. In this specification and the drawings, components having substantially the same functional configuration are denoted by the same reference numerals, and redundant descriptions will be omitted.

[0011] Referring to Figure 1, an example of the system configuration of an information processing system according to one embodiment of this disclosure will be described. The information processing system according to this embodiment includes a workflow processing server 200 and a multifunction device 100. The workflow processing server 200 is implemented by an information processing device (computer) having communication functions and is connected to the multifunction device 100 via a network such as a LAN (Local Area Network). The workflow processing server 200 is also configured to be connectable to the Internet 101. The multifunction device 100 corresponds to a device having multiple functions such as a scanner function, a printer function, a copier function, and a fax function.

[0012] Referring to Figure 2, an example of the hardware configuration of the workflow processing server 200 will be described. The CPU (Central Processing Unit) 201 controls the operation of the entire workflow processing server 200 by loading and executing the control program stored in the ROM (Read Only Memory) 202. The RAM (Random Access Memory) 203 is used as a temporary storage area for the CPU 201's main memory, work area, etc. The RAM 203 is also used as the area where the control program is loaded to make it executable by the CPU 201. The keyboard and mouse 204 represent an example of an input interface for receiving user instructions to the workflow processing server 200. The provision of the keyboard and mouse 204 enables smooth operation of user commands to the workflow processing server 200.

[0013] The network communication unit 205 is a communication interface for connecting the workflow processing server 200 to the network. USB (Universal Serial Bus) 206 is a connection interface for connecting various peripheral devices to the workflow processing server 200. The HDD (Hard Disk Drive) 207 is a recording medium that stores various types of data. The HDD 207 is connected to the workflow processing server 200 via a connection interface such as SCSI or IDE. In addition, in the workflow processing server 200 according to this embodiment, state management information 208 is stored in the HDD 207. The state management information 208 is information used for managing the status of orders to external vendors (hereinafter also referred to as outsourcing), as described later with reference to Figure 5.

[0014] The graphics board 209 is a component for displaying images, such as moving images and still images, on the display 210. The display 210 is an output interface for presenting various information to the user by displaying it as an image. In the workflow processing server 200 according to the present embodiment, the operation screen of the workflow processing server 200 is presented to the user via the display 210, and the display of the operation screen is updated according to the operation from the user.

[0015] Referring to FIG. 3, an example of the processing of the workflow processing server 200 according to the present embodiment will be described together with an example of the procedure flow related to the management of the workflow using the workflow processing server 200. In the example shown in FIG. 3, for the sake of convenience, it is assumed that the user 301 requests binding and delivery to the employee 304 of the printing company 302 via the workflow processing server 200, and the employee 304 outsources some of the work to the subcontracting company 303. Also, while the description will focus on the processing flow of the workflow processing server 200, in the case where manual operation via human hands occurs, the relationship between the work of the employee 304 of the printing company 302 and the workflow processing server 200 will be described with reference to FIGS. 4 and 5. Although details will be described later, the workflow processing server 200 according to the present embodiment provides a mechanism that enables continuous implementation of the progress management of outsourcing even in a situation where an outsourcing work, which is a manual operation via human hands, occurs.

[0016] In S311, the workflow processing server 200 installed in the printing company 302 receives the binding and delivery request from the user 301 indicated by reference sign S310 and accepts the request. Regarding the content of the binding request, for example, it is received as information input in accordance with a predetermined format via the homepage, and is directly input to the workflow processing server 200 without human intervention. In S312, the workflow processing server 200 analyzes the content of the request accepted in S311. For example, the workflow processing server 200 acquires information (name, address, email address, etc.) for identifying the user 301 and information related to printing processing such as the manuscript and the binding method from the content of the accepted request. In S313, the workflow processing server 200 checks whether the received order request contains request information for a predetermined process. The predetermined process in the present disclosure corresponds to a process that is additionally performed other than printing, such as foil stamping in which foil such as gold or silver is attached to paper, or gloss processing in which a film is laminated on the surface of paper to give luster and strength. In particular, a special process that requires dedicated equipment may be applicable. In the present embodiment, for the sake of convenience, the work of this predetermined process is managed as work that is the subject of an order placed outside the printing company 302 (outsourced work), and it is assumed that the workflow processing server 200 is also set to handle the same work as the subject of outsourcing. In S314, the workflow processing server 200 requests the multifunction machine 100 to perform a printing process and executes the production of a printed matter.

[0017] In S315, the workflow processing server 200 determines whether there is a request for a predetermined process based on the confirmation result in S313. If the workflow processing server 200 determines in S315 that there is no request for a predetermined process, the process proceeds to S316. In S316, the workflow processing server 200 sends the printed matter to the factory automatic line and automatically performs delivery processing such as packing in envelopes and attaching destination labels to the user 301. After that, as indicated by attaching the symbol S337, when the user 301 receives the work product, a series of workflows ends. The processing of the printing company 302 described above corresponds to an example of processing assuming work in which "manual operation via hands" does not occur. Therefore, it corresponds to a case where the workflow processing server 200 can hold information for progress management and manage which process of the entire workflow is being performed (a case where progress management is possible).

[0018] On the other hand, if the workflow processing server 200 determines in S315 that there is a request for a predetermined process, the process proceeds to S317. In S317, the workflow processing server 200 initializes all task states to an unexecuted state. In S318, the workflow processing server 200 notifies employee 304 of printing company 302 (a user managed as an employee of printing company 302) that an outsourcing task for a specified processing has occurred. Upon receiving this notification, employee 304 begins the outsourcing task of requesting the specified processing from subcontractor 303. In Figure 3, among the series of procedures labeled S319 to S335, the tasks primarily performed by employee 304 are those that involve "manual operation via human intervention." For example, when employee 304 of printing company 302 requests subcontractor 303 to perform outsourced processing by telephone or verbally, it is difficult to automate this task using the workflow processing server 200. Furthermore, it is difficult for the workflow processing server 200 to automatically sense the progress and manage the progress of such tasks. In light of the above, this embodiment proposes a mechanism that enables the workflow processing server 200 to grasp the business processes that are manually operated by humans and to check the progress status of each business process, thereby ensuring that the management of the progress status of the outsourced work workflow is not interrupted.

[0019] As an example of a mechanism to ensure uninterrupted management of workflow progress, the outsourced work process is broken down into individual tasks (processes or operations) and defined as tasks, and the status of each task can be checked using the outsourced workflow application display screen 400. Figure 4 shows an example of the outsourced workflow application display screen 400 configured as a GUI (Graphical User Interface). In the outsourced workflow application display screen 400, as described above, each task is defined for the outsourced work, each task is individually linked to an icon, and information (GUI) is displayed with arrows connecting each icon according to the execution order of each task. By displaying this information, the outsourced workflow application display screen 400 visually presents the flow and progress of the outsourced work to the user (in this embodiment, an employee 304 of the printing company 302) in an easily identifiable manner. Specifically, the workflow processing server 200 updates the display of the icon associated with each task (process or operation) according to the status of that task. With this control applied, the display on the outsourced workflow application screen 400 is automatically updated according to the progress of the work, and the progress of each task can be checked on the outsourced workflow application screen 400.

[0020] Here, we will explain task definition using a concrete example of outsourced work. In the example shown in Figure 3, the business process of outsourced work performed by employee 304 of printing company 302 is broken down into processes and tasks indicated as "requesting specified processing (S319)", "checking the estimated price (S324)", "requesting (S329)", and "receiving deliverables (S334)". In the example shown in Figure 4, these processes and tasks are defined as tasks, and each task is presented linked to an icon. The specified processing estimate request task icon 401, the specified processing estimate receipt task icon 402, the request task icon 404, and the deliverables receipt task icon 405 shown in Figure 4 correspond to the icons linked to each of the above tasks. Furthermore, task processing branch 403 is an icon positioned to enable branching for changing the tasks to be performed thereafter, depending on the result of the determination of whether the estimated price, indicated by the code S327 in Figure 3, is below the predetermined price. If task processing branch 403 determines that it is below the predetermined price, the task linked to the request task icon 404 (the "request" task indicated by the code S329 in Figure 3) becomes the next task to be performed. On the other hand, if task processing branch 403 determines that it is not below the predetermined price, the process returns to the execution stage of the task linked to the predetermined processing estimate request task icon 401 (the "request predetermined processing" task indicated by the code S319 in Figure 3).

[0021] The "In Progress" indicator 406 is a mark indicating that the task associated with the target icon is currently running. In the example shown in Figure 4, the "In Progress" indicator 406 is displayed in association with the requested task icon 404, indicating that the "requested" task, indicated by the code S329 in Figure 3, is currently running. In this way, the "In Progress" indicator 406 is displayed for icons associated with running tasks, allowing users to confirm that the task is in progress (in other words, the progress of the outsourced work).

[0022] Another example of a mechanism to ensure uninterrupted management of workflow progress is a task status management screen 500 that allows users to check whether each business process has been executed and to receive instructions indicating that it has been executed. Figure 5 shows an example of a task status management screen 500 configured as a GUI. As shown in Figure 5, the task status management screen 500 includes a task status display area 501, a status management button display area 502, and a memo information display area 503. The task status display area 501 displays the name of the target task and information indicating the status of that task. Task status displays 509, 510, 511, and 512 each indicate the status of the target task, and the display is updated according to the status of the task. The status management button display area 502 is an area where buttons are displayed to accept manual input regarding the execution status of the target task. Each button displayed in the status management button display area 502 corresponds to an example of an input interface for receiving input on the progress status of the target task (for example, input related to task completion) from the user (in this embodiment, an employee 304 of the printing company 302). Details of buttons 513, 514, 515, 516, and 517 displayed in the status management button display area 502 in the example shown in Figure 5 will be described separately in detail with reference to Figures 3 and 6, along with the content of the processing performed when each button is operated. The memo information display area 503 is an area for managing various pieces of information related to the target task, linked as additional information. Specific examples of the information registered in the memo information display area 503 will be described later. In this embodiment, in order to enable progress confirmation of outsourced work, the status of each task in the outsourced work workflow defined in the example shown in Figure 4 can be manually entered. The workflow processing server 200 accepts input of the progress status for each business process of the outsourced work via the task status management screen 500, thereby managing the progress status so as not to be interrupted by "manual operation by a human being" (non-automated processing).

[0023] In the example shown in Figure 5, the task status management screen 500 manages the outsourced work process 504 as an outsourced task, dividing it into a prescribed processing estimate request management part 505, a prescribed processing estimate receipt management part 506, an order management part 507, and a deliverable receipt management part 508. Each of these parts is linked to the prescribed processing estimate request task icon 401, prescribed processing estimate receipt task icon 402, order task icon 404, and deliverable receipt task icon 405 shown in Figure 4. With this configuration, the workflow processing server 200 can manage changes in the status of each task.

[0024] In the following description, the workflow process for managing progress and the like using the outsourced workflow app display screen 400 shown in FIG. 4 and the task status management screen 500 shown in FIG. 5 is also referred to as the outsourced workflow process 600. In the example shown in FIG. 4, in order to indicate that it is an icon constituting the outsourced workflow process 600 (in other words, manually operated through human hands), a mark of the character "person" is attached to the target icon. Also, for the automated workflow process described later with reference to FIG. 7, in order to distinguish it from the outsourced workflow process 600, a mark of the character "person" is not attached to the target icon. Regarding the details of the task status management screen 500 shown in FIG. 5, it will be described in conjunction with the content of the processing of the part to be described later among the series of processes shown in FIG. 3. Note that the outsourced workflow process 600 corresponds to an example of the first workflow, and the work performed manually defined as the outsourced workflow process 600 corresponds to an example of the first work.

[0025] Here, refer to FIG. 3 again. The employee 304 of the printing company 302 makes a quotation request for a subcontractor 303 regarding a predetermined process by phone or the like in S319. After finishing the procedure, in S320, the quotation request button 513 of the predetermined process quotation request management part 505 shown in FIG. 5 is pressed. When the workflow processing server 200 detects that the quotation request button 513 has been pressed, in S322, it changes the state of the predetermined process quotation request task it manages from the unexecuted state to the executed state. In the example shown in FIG. 5, the state where the task status display 509 is displayed as "completed" indicates that the predetermined process quotation request management part 505 is in the executed state. Also, in the memo column 518 of the predetermined process quotation request management part 505, registration of information related to the target task, such as the content of the quotation request for the subcontractor 303, may be allowed.

[0026] Subcontractor 303 receives a request for a quote for specified processing from employee 304 of printing company 302 in S321, calculates the estimated price, and returns the estimated price to employee 304 in S323. In S324, employee 304 of printing company 302 receives the above-mentioned estimated price from subcontractor 303, checks the estimated price, and in S325 presses the estimate reception button 514 of the prescribed processing estimate reception management part 506 shown in Figure 5. When the workflow processing server 200 detects that the estimate reception button 514 has been pressed, in S326 it changes the status of the predetermined processing estimate reception task it manages from not executed to executed. In the example shown in Figure 5, the status of the task status display 510, which is displayed as "Completed," indicates that the predetermined processing estimate reception management part 506 is in the executed state. In addition, information 532 indicating the estimated price returned by the subcontractor 303 may be registered and managed in the memo field 519 of the predetermined processing estimate reception management part 506. Furthermore, information 531 indicating the desired price requested by the employee 304 of the printing company 302 may be registered in advance so that it can be compared with the estimated price registered as information 531.

[0027] Next, in S327, employee 304 of printing company 302 makes a determination as to whether the estimated price is below the specified price. If employee 304 determines in S327 that the estimated price is below the specified price, in S329 he formally requests the subcontractor 303 to perform the specified processing, and in S330 he presses the "Place Order" button 515 in the request management part 507 shown in Figure 5. When the workflow processing server 200 detects that the "Place Order" button 515 has been pressed, it changes the status of the request task it manages in S332 from "Not Executed" to "Executed".

[0028] On the other hand, if employee 304 of printing company 302 determines in S327 that the quoted price is higher than the predetermined price, in S328, they press the "Do not place order" button 516 in the request management part 507 shown in Figure 5. In this case, the series of procedures reverts to the point where the processing in S317 is executed, and employee 304 will either renegotiate with the subcontractor 303 as before, or conduct separate negotiations with another subcontractor 303. If the workflow processing server 200 detects that the "Do not place order" button 516 has been pressed, it will leave the status of the request tasks it manages in the "not executed" state. Then, in S317, the workflow processing server 200 will initialize the status of the predetermined processing estimate request task and the predetermined processing estimate reception task, which were previously changed to the "executed" state, back to the "not executed" state. In the example shown in Figure 5, the task status display 511 showing "Not yet executed" indicates that employee 304 has not yet decided whether or not to place an order and has not pressed the button, thus indicating that the requested task is not yet executed. Similarly, the execution display 406 in the example shown in Figure 4 also shows a progress status equivalent to that in the example shown in Figure 5, indicating that employee 304 has not yet decided whether or not to place an order, and thus the requested task is displayed as "In progress."

[0029] In the example described above, we explained an example where a person (an employee 304 of the printing company 302) makes the determination of whether the estimated price in S327 is higher than the predetermined price. However, it is also possible to have the workflow processing server 200 make this determination automatically. In this case, the workflow processing server 200 should compare the desired price information 531 registered in the memo field 519 with the estimated price information 532, and automatically execute the processing required when the "Place Order" button 515 or the "Do Not Place Order" button 516 is pressed, depending on the comparison result.

[0030] Subcontractor 303 receives a formal request for specified processing from employee 304 of printing company 302 in S331, carries out the production of deliverables using said specified processing, and delivers the produced deliverables to printing company 302 in S333. Employee 304 of printing company 302 receives the deliverables from subcontractor 303 in S334, and presses the receive button 517 of the deliverable receipt management part 508 shown in Figure 5 in S335. When the workflow processing server 200 detects that the receive button 517 has been pressed, it changes the status of the receive task it manages in S336 from not executed to executed. In the example shown in Figure 5, the status of the task status indicator 512, which is displayed as "Not yet executed," indicates that employee 304 has not pressed the accept button 517, and the status of the accepted task is not yet executed.

[0031] In S316, employee 304 of printing company 302 delivers the pre-processed deliverables received from subcontractor 303 in S334 to user 301, the client. Then, in S337, when user 301 receives the deliverables from employee 304 of printing company 302, the series of procedures shown in Figure 3 are completed.

[0032] Referring to Figure 6, an example of the processing of the workflow processing server 200 will be explained, focusing particularly on the parts related to the outsourced workflow processing 600. In the example shown in Figure 3, the explanation focused mainly on the procedures and operations performed by employee 304 of the printing company 302. In contrast, the example shown in Figure 6 will explain the operation of the workflow processing server 200 (the operation realized by the execution of a program) in response to the operation of the employee 304. Note that the series of processes shown in Figure 6 are realized by the program stored in ROM 202 being loaded into ROM 202 and executed by CPU 201.

[0033] In S601, the workflow processing server 200 executes a state initialization process. Specifically, the workflow processing server 200 controls the display of task status indicators 509, 510, 511, and 512 on the task status management screen 500 to be set to "Not yet performed". The workflow processing server 200 also registers the status of the specified processing estimate request task, specified processing estimate reception task, request task, and received task as "Not yet performed". Furthermore, the workflow processing server 200 controls the display of the running indicator 406 for each task icon on the outsourcing workflow application display screen 400 to be hidden. In S602, the workflow processing server 200 displays an "in progress" indicator 406 linked to the specified processing estimate request task icon 401 on the outsourcing workflow application display screen 400. Then, in S603, the workflow processing server 200 waits for an operation on the quote request button 513 on the task status management screen 500. When the workflow processing server 200 detects that the quote request button 513 has been pressed, it proceeds to S604. In S604, the workflow processing server 200 controls the execution indicator 406, which is linked to the specified processing estimate request task icon 401 on the outsourcing workflow application display screen 400, so that it is hidden. Then, the workflow processing server 200 changes the status of the specified processing estimate request task to the completed status. Finally, the workflow processing server 200 controls the task status indicator 509 on the task status management screen 500 so that it is displayed as "Completed," indicating that the task in question has been completed.

[0034] In S605, the workflow processing server 200 displays an "in progress" indicator 406 linked to the specified processing estimate receipt task icon 402 on the outsourcing workflow application display screen 400. Then, in S606, the workflow processing server 200 waits for an operation on the estimate reception button 514 on the task status management screen 500. When the workflow processing server 200 detects that the estimate reception button 514 has been pressed, it proceeds to S607. In S607, the workflow processing server 200 controls the execution indicator 406, which is linked to the specified processing estimate receipt task icon 402 on the outsourcing workflow application display screen 400, so that it is hidden. Then, the workflow processing server 200 changes the status of the specified processing estimate receipt task to the completed status. Finally, the workflow processing server 200 controls the task status indicator 510 on the task status management screen 500 so that it is displayed as "Completed," indicating that the task in question has been completed.

[0035] In S608, the workflow processing server 200 displays the "In Progress" indicator 406, which is linked to the requested task icon 404 on the outsourced workflow application display screen 400. In steps S609 and S610, the workflow processing server 200 waits for an operation on either the "Place Order" button 515 or the "Do Not Place Order" button 516 on the task status management screen 500. Specifically, in step S609, the workflow processing server 200 determines whether the "Place Order" button 515 has been pressed. If the workflow processing server 200 determines in step S609 that the "Place Order" button 515 has not been pressed, it proceeds to step S610. In step S610, the workflow processing server 200 determines whether the "Do Not Place Order" button 516 has been pressed. If the workflow processing server 200 determines in step S610 that the "Do Not Place Order" button 516 has not been pressed, it proceeds to step S609 and executes the determination process in step S609 again. Then, if the workflow processing server 200 determines in S609 that the "Place Order" button 515 has been pressed, it proceeds to S611. On the other hand, if the workflow processing server 200 determines that the "Do not place order" button 516 was pressed in S610, it proceeds to S601. In this case, the processing from S601 onwards will be executed again. In S611, the workflow processing server 200 controls the execution indicator 406, which is associated with the requested task icon 404 on the outsourced workflow application display screen 400, to be hidden. Then, the workflow processing server 200 changes the status of the requested task to the completed status. Finally, the workflow processing server 200 controls the task status indicator 511 on the task status management screen 500 to display as "Completed," indicating that the task in question has been completed.

[0036] In S612, the workflow processing server 200 displays the "In Progress" indicator 406, linked to the deliverable receipt task icon 405 on the outsourced workflow application display screen 400. Then, in S613, the workflow processing server 200 waits for an operation on the receive button 517 on the task status management screen 500. When the workflow processing server 200 detects that the receive button 517 has been pressed, it proceeds to S614. In S614, the workflow processing server 200 controls the execution indicator 406, which is linked to the deliverable receipt task icon 405 on the outsourced workflow application display screen 400, so that it is hidden. Then, the workflow processing server 200 changes the status of the received task to the completed status. Finally, the workflow processing server 200 controls the task status indicator 512 on the task status management screen 500 so that it is displayed as "Completed," indicating that the task in question has been completed, and terminates the series of processes shown in Figure 6 as the outsourced workflow processing 600.

[0037] FIG. 7 is a diagram showing an example of a display screen 700 of a printing company workflow application configured as a GUI. In the printing company workflow application display screen 700, each task of the operations of the printing company 302 is individually associated with an icon, and the flow and progress of the operations of the printing company 302 are visually presented in an identifiable manner by the display information connecting the icons with arrows. The workflow processing server 200 updates the display of the icon associated with the task according to the status of each task (processing or operation). By applying such control, the display of the printing company workflow application display screen 700 is automatically updated according to the progress of the operations, and it becomes possible to check the progress such as which task is being executed on the printing company workflow application display screen 700.

[0038] The user order task icon 701, the order information identification task icon 702, the predetermined processing information check task icon 703, the deliverable generation task icon 704, and the delivery task icon 706 show each task of the operations of the printing company 302 as icons. These icons are icons associated with each task of the operations that can be automated without manual intervention, and do not have a mark of the character "person" indicating that it is "manually operated through human hands". Hereinafter, as exemplified as icons 701, 702, 703, 704, and 706 in FIG. 7, a task definition is made, and the flow of the process corresponding to the operations automated without manual intervention is also referred to as an automated workflow process. When each task constituting the automated workflow process is completed, the workflow processing server 200 changes the status of the task managed by itself from an unexecuted state to an executed state. That is, for the automated workflow process, the workflow processing server 200 automatically grasps the progress situation without an instruction for manual status change from the user, unlike the status management of each task through the task status management screen 500 exemplified in FIG. 5.

[0039] Hereinafter, each component of the printing company workflow application display screen 700 shown in FIG. 7 will be described in more detail. The user order task icon 701 corresponds to the icon that is defined and associated with the process in which the workflow processing server 200 receives a bookbinding request from user 301, as indicated by the code S311 in Figure 3. The order information identification task icon 702 corresponds to the icon associated with the process of analyzing the contents of a bookbinding request received by the workflow processing server 200, which is defined as a task and shown with the code S312 in Figure 3. The predetermined processing information check task icon 703 corresponds to the icon that is defined and associated with the process of checking whether the content of the order received by the workflow processing server 200 includes information on predetermined processing, as indicated by the code S313 in Figure 3. The deliverable generation task icon 704 corresponds to the icon that is defined and associated with the process shown in Figure 3, labeled S314, where the workflow processing server 200 requests the multifunction printer 100 to perform a print operation and generate a printed document. The delivery task icon 706 corresponds to the icon associated with the delivery process, which is defined as a task in Figure 3, indicated by the code S316, where the workflow processing server 200 sends printed materials to the factory's automated line and performs tasks such as stuffing envelopes and attaching address labels to deliver them to user 301.

[0040] The task icon 401 for requesting a predetermined processing estimate, the task icon 402 for receiving a predetermined processing estimate, the task processing branch 403, the request task icon 404, and the task icon 405 for receiving deliverables are the same as the icons on the outsourcing workflow application display screen 400 shown in Figure 4. Furthermore, the workflow processing indicated by these icons corresponds to the outsourcing workflow processing 600 described above. The outsourced workflow process 600 is connected via the task processing branch 705 to the automated workflow processes (workflow processes indicated by icons 701, 702, 703, 704, and 706) which represent automated processing flows that do not involve human intervention. Task processing branch 705 corresponds to the icon, denoted as S315 in Figure 3, which is a task defined and associated with the workflow processing server 200, which makes a decision regarding the switching of subsequent processes based on the result of checking whether or not there is request information for a predetermined processing. If the content of the received request includes request information for a predetermined processing, the workflow processing shown on the connected outsourcing workflow application display screen 400 is started. On the other hand, if the content of the received request does not include request information for a predetermined processing, the task associated with the delivery task icon 706 is started. The automated workflow described above corresponds to an example of the second workflow, and the automated work specified as the automated workflow process corresponds to an example of the second work.

[0041] Referring to Figure 8, an example of the processing of the workflow processing server 200 will be explained, focusing particularly on the control portion that ensures the continuous execution of the business workflow of the printing company 302, including outsourcing. Specifically, as explained with reference to Figure 7, Figure 8 shows that the outsourced workflow processing 600, shown on the outsourced workflow application display screen 400, is connected to the automated workflow processing, and a series of processes are executed. The series of processes shown in Figure 8 are realized by the program stored in ROM 202 being loaded into ROM 202 and executed by CPU 201.

[0042] In S801, the workflow processing server 200 performs state initialization processing. Specifically, the workflow processing server 200 controls the execution status indicator for each task icon (for example, the execution status indicator 406 for the requested task icon 404 as exemplified in Figure 4) to be hidden. In S802, the workflow processing server 200 displays the "In Progress" indicator 406, linked to the user order task icon 701 on the printing company workflow application display screen 700. In S803, the workflow processing server 200 stores the received information of the bookbinding request received from user 301. The processing in S803 corresponds to the processing indicated by the symbol S311 in the example shown in Figure 3.

[0043] In S804, the workflow processing server 200 moves the running indicator 406 so that it is linked to the order information identification task icon 702 on the printing company workflow application display screen 700 and displayed accordingly. In S805, the workflow processing server 200 analyzes the received information of the bookbinding request received from user 301, and acquires and stores information to identify user 301, as well as information related to printing processes such as the original document and bookbinding method. The process in S805 corresponds to the process indicated by the symbol S312 in the example shown in Figure 3.

[0044] In S806, the workflow processing server 200 moves the running display 406 so that it is linked to the predetermined processing information check task icon 703 on the printing company workflow application display screen 700. In S807, the workflow processing server 200 analyzes the received information of the bookbinding request received from user 301 and checks whether the request contains information about a predetermined processing. The processing in S807 corresponds to the processing indicated by the symbol S313 in the example shown in Figure 3.

[0045] In S808, the workflow processing server 200 moves the running indicator 406 so that it is linked to the deliverable generation task icon 704 on the printing company workflow application display screen 700 and displayed accordingly. In S809, the workflow processing server 200 requests the multifunction printer 100 to perform a print operation and generates a printed document. The process in S809 corresponds to the process indicated by the reference numeral S314 in the example shown in Figure 3.

[0046] In S810, the workflow processing server 200 determines whether or not a request for a specific processing is being made, based on the confirmation results in S807. If the workflow processing server 200 determines in S810 that a request for a predetermined processing exists, it proceeds to S600. Specifically, the workflow processing server 200 calls the outsourced workflow processing 600 connected to the automated workflow processing on the printing company workflow application display screen 700 shown in Figure 7. Then, once the outsourced workflow processing 600 (the series of processes shown in Figure 6) is completed, the workflow processing server 200 proceeds to S811. On the other hand, if the workflow processing server 200 determines in S810 that there is no request for the specified processing, it proceeds to S811. The process in S810 corresponds to the process indicated by the reference numeral S315 in the example shown in Figure 3.

[0047] In S811, the workflow processing server 200 moves the running indicator 406 to the delivery task icon 706 on the printing company workflow application display screen 700 so that the running indicator 406 is displayed in association with it. In S812, the workflow processing server 200 sends the printed materials to the factory automated line and automatically performs delivery processing such as envelope stuffing and address labeling for user 301. However, if the outsourced workflow processing 600 is executed, some tasks, such as sending the printed materials to the factory automated line, may be performed manually. The process in S812 corresponds to the process indicated by the reference numeral S316 in the example shown in Figure 3. With the above steps completed, the series of processes shown in Figure 8 is finished.

[0048] <Other Embodiments> The present invention can also be realized by supplying a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (e.g., an ASIC) that implements one or more functions. Furthermore, the embodiments described above are merely examples and do not limit the scope of application of the technology according to one embodiment of this disclosure. As a specific example, the technology according to one embodiment of this disclosure can be applied to any business where manual operation by a human is possible, not limited to business operations to which a multifunction printer is applied. In such cases, similar to the embodiments described above, at least one task can be defined for a series of operations performed by manual operation by a human, and then managed as a workflow (equivalent to the outsourced workflow processing 600 mentioned above) that includes that task.

[0049] Furthermore, the disclosure of this embodiment includes the following configurations, methods, and programs. (Configuration 1) An information processing device characterized by comprising: a definition means for defining a first task, which is performed manually, as a first workflow including one or more tasks; a display control means for controlling the display of an input interface to which each of the one or more tasks included in the first workflow is individually linked; a reception means for receiving instructions from a user regarding the completion of each of the one or more tasks via the input interface to which the task is linked; and a management means for managing the execution status of a series of tasks as a workflow related to the series of tasks by connecting the first workflow to a part of a second workflow defined for a second task, which is automated, among the series of tasks. (Configuration 2) The information processing apparatus according to Configuration 1, characterized in that the display control means controls the display of the input interface associated with each of the one or more tasks in accordance with the execution order of the one or more tasks. (Configuration 3) The information processing device according to Configuration 1 or 2, wherein the receiving means accepts registration of information related to the task for which an instruction regarding completion has been received. (Configuration 4) The information processing apparatus according to Configuration 3, wherein the receiving means accepts registration of deliverables of at least some tasks as information relating to those tasks. (Method 1) A control method for an information processing device, comprising: a definition step of defining a first task performed manually among a series of tasks as a first workflow including one or more tasks; a display control step of controlling the display of an input interface to which each of the one or more tasks included in the first workflow is individually linked; a reception step of receiving instructions from a user regarding the completion of each of the one or more tasks via the input interface to which the task is linked; and a management step of managing the execution status of a series of tasks as a workflow related to the series of tasks by connecting the first workflow to a part of a second workflow defined for a second task that has been automated among the series of tasks. (Program 1) A program for causing a computer to function as an information processing device, comprising: a definition means for defining a first task, which is performed manually, as a first workflow including one or more tasks; a display control means for controlling the display of an input interface to which each of the one or more tasks included in the first workflow is individually linked; a reception means for receiving instructions from a user regarding the completion of each of the one or more tasks via the input interface to which the task is linked; and a management means for managing the execution status of a series of tasks as a workflow related to the series of tasks by connecting the first workflow to a part of a second workflow defined for a second task, which is automated, as part of the series of tasks. [Explanation of symbols]

[0050] 200 Workflow Processing Servers 500 Task Status Management Screen 700 Printing company workflow app display screen

Claims

1. A definition means for defining the first task, which is performed manually, as a first workflow containing one or more tasks, among a series of tasks, A display control means that controls the display of an input interface to which each of the one or more tasks included in the first workflow is individually linked, A receiving means that receives input of the progress status of each of the one or more tasks from the user via the input interface to which the task is associated, A management means for managing the execution status of the series of tasks as a workflow related to the series of tasks, by connecting the first workflow to a part of the second workflow defined for the second task which has been automated among the series of tasks, An information processing device characterized by having

2. The information processing apparatus according to claim 1, characterized in that the display control means controls the display so that the input interface associated with each of the one or more tasks is displayed in accordance with the execution order of the one or more tasks.

3. The information processing apparatus according to claim 1 or 2, characterized in that the receiving means accepts registration of information related to the task for which the input of the progress status has been received.

4. The information processing apparatus according to claim 3, wherein the receiving means accepts registration of deliverables of at least some tasks as information relating to those tasks.

5. A method for controlling an information processing device, A definition step defines the first task in a series of operations, which is performed manually, as a first workflow containing one or more tasks, A display control step that controls the display so that the input interface to which each of the one or more tasks included in the first workflow is individually linked is displayed, A receiving step in which the user inputs the progress status of each of the one or more tasks mentioned above via the input interface to which the task is associated, A management step is established to manage the execution status of the series of tasks as a workflow related to the series of tasks, by connecting the first workflow to a part of the second workflow defined for the second task which has been automated among the series of tasks, A control method for an information processing device, characterized by including the following:

6. Computers, A definition means for defining the first task, which is performed manually, as a first workflow containing one or more tasks, among a series of tasks, A display control means that controls the display of an input interface to which each of the one or more tasks included in the first workflow is individually linked, A receiving means that receives input of the progress status of each of the one or more tasks from the user via the input interface to which the task is associated, A management means for managing the execution status of the series of tasks as a workflow related to the series of tasks, by connecting the first workflow to a part of the second workflow defined for the second task which has been automated among the series of tasks, A program for causing an information processing device to function, characterized by having the following features.

Citation Information

Patent Citations

  • Electronic commerce support system, electronic commerce support method and program

    JP2023024416A