Information processing device, workflow management method, and program

Abstract

To solve the problem in that, in a case where trouble occurs at a plurality of places, unnecessary retention occurs in another process depending on a process to be preferentially handled.SOLUTION: An information processing device for managing a workflow is provided. The device stores workflow information indicating processes included in the workflow and an order of the processes; when a job is executed in accordance with the workflow, identifies an error-related job in which an error has occurred and an error process in which the error has occurred; when a plurality of errors are identified, identifies, for each of the error-related jobs, the number of dependent processes, among processes downstream of each of the error processes, in which processing is executed using a plurality of work-in-process items; and determines, as a priority process, an error process in which the number of dependent processes is larger than that of the other error processes.SELECTED DRAWING: Figure 16

Description

[Technical Field]

[0001] The present invention relates to an information processing apparatus and a workflow management method and program for managing warning notifications of job retention in each process in an offline process such as commercial printing, which is a management target. [Background technology]

[0002] In commercial printing, the process from "order placement" to "printing process" is managed and visualized using printing workflow software. The status of online post-processing machines connected to a network is also managed and visualized by collecting information via the network. By visualizing the status of each processing machine, the work status of each process can also be obtained. Patent Document 1 describes a system that can easily and appropriately adjust the execution order when multiple orders are placed. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-174032 Summary of the Invention [Problem to be solved by the invention]

[0004] Depending on the process, work may be performed using multiple deliverables, such as by combining deliverables from other processes. In such processes, a nearby storage area is prepared, and deliverables that arrive at the storage area first will wait there until the deliverables required for the work arrive. Deliverables from other processes waiting for the arrival of such deliverables are called work in progress. As the number of backlogged jobs increases, work in progress is stored in the storage area. If problems occur in multiple processes, jobs will be backlogged, and if they are not handled in the appropriate order, the work in progress will increase and put pressure on the storage area. This can lead to issues such as difficulty storing work in progress and difficulty finding the necessary work in progress when deliverables arrive. Therefore, it is necessary to appropriately determine which processes to prioritize or the order of processes.

[0005] In the method described in Patent Document 1, the execution order of element processes of a workflow is determined based on the order of print jobs, delivery dates, etc. Then, when a failure occurs in a device of an element process of a workflow, the execution order of element processes downstream of the suspended element process in the workflow whose execution has been suspended is adjusted so that other workflows are given priority. However, Patent Document 1 does not consider how to deal with the case where multiple processes fail simultaneously, and there is a problem in that it is unable to respond appropriately in such a case.

[0006] Therefore, the present invention aims to provide a management system, management method, and program that prevents processing backlogs by determining priority processes for workers to respond to in the event of trouble occurring at multiple locations. [Means for solving the problem]

[0007] In order to achieve the above object, according to one aspect of the present invention, there is provided an information processing apparatus for managing a workflow, comprising: a storage means for storing workflow information indicating steps included in the workflow and their order; a first identifying means for identifying an error-related job and an error process in which an error has occurred when a job is being executed according to a workflow; a second specifying means for specifying, for each error-related job, the number of dependent processes that are executed using multiple work-in-progress among processes downstream of each error process when multiple errors are specified by the first specifying means; a determining means for determining, as a priority process, an error process having a larger number of dependent processes identified by the second identifying means than the other processes; An information processing device is provided, comprising: [Effects of the Invention]

[0008] According to the present invention, by determining a priority process for workers to deal with in a case where trouble occurs at multiple locations, it is possible to prevent processing from being delayed. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating the configuration of an image forming system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a hardware configuration diagram of the information processing apparatus according to the embodiment. [Figure 3] FIG. 2 is a software configuration diagram of the information processing apparatus according to the present embodiment. [Figure 4] The print job management screen of the print workflow application. [Figure 5] FIG. 4 is a diagram showing a print job information table stored in print job information data. [Figure 6] 10A and 10B are diagrams showing a product information table and a workflow information table stored in print job information data. [Figure 7] FIG. 1 is a diagram showing an example of the configuration of a location management system according to an embodiment of the present invention. [Figure 8] FIG. 2 is a block diagram showing an example of the configuration of a tag reader according to the present embodiment. [Figure 9] FIG. 2 is a block diagram showing an example of the configuration of a user terminal included in the mobile system of the present embodiment. [Figure 10] FIG. 2 is a block diagram showing an example of the configuration of a management server according to the present embodiment. [Figure 11]3A to 3C are diagrams showing examples of the configurations of an article table, a location table, a reader table, a user table, a movement amount table, and a tag detection table according to the present embodiment. [Figure 12] FIG. 1 is a diagram showing an example of the configuration of a process control system according to an embodiment of the present invention. [Figure 13] 3A to 3C are diagrams showing examples of the configurations of a job table, a process position table, and a job status table according to the present embodiment. [Figure 14] FIG. 2 is a diagram showing an example of the configuration of a process management service according to the present embodiment. [Figure 15] FIG. 2 is an overall flow diagram of the present embodiment. [Figure 16] FIG. 2 is an overall flow diagram of determining a priority process according to the present embodiment. [Figure 17] FIG. 10 is a flowchart for determining a priority process using the number of remaining dependent processes according to the present embodiment. [Figure 18] FIG. 10 is a diagram showing an example of determining a priority process using the number of remaining dependent processes according to the present embodiment. [Figure 19] FIG. 10 is a flowchart showing a modified example of the process priority determination flow according to the present embodiment, taking into consideration work in progress. [Figure 20] FIG. 2 is a diagram showing an example of a work-in-progress storage area according to the present embodiment. [Figure 21] FIG. 10 is a flowchart showing a modified example of the worker determination process according to the present embodiment. [Figure 22] FIG. 10 is a flowchart showing a modified example of the present embodiment for determining a worker by taking into consideration the worker's history. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the invention claimed. Although multiple features are described in the embodiments, not all of these multiple features are necessarily essential to the invention, and multiple features may be combined arbitrarily. Furthermore, in the accompanying drawings, the same reference numerals are used to designate the same or similar components, and redundant explanations will be omitted.

[0011] Each step in the flowchart is indicated by a reference number beginning with S.

[0012] [Embodiment 1] In this embodiment, the judgment value used for the congestion warning notification is variable based on the cause of the congestion that occurs in each process. This makes it possible to identify the cause of the job congestion and the cause of its frequent occurrence, and to issue a warning notification at an appropriate time to resolve the job congestion.

[0013] [Image formation system configuration] FIG. 1 is a diagram illustrating an example of the configuration of an image forming system according to an embodiment of the present invention. This image forming system also functions as a workflow management system for managing the execution of a workflow. In this example, a workflow is a processing flow composed of successive elemental processes for producing a printed product (also called a commercial product). The object processed (or executed) according to the workflow is called a job, and a printing workflow is specifically called a print job. The workflow of this embodiment includes, as elemental processes, a printing process typically performed by a printing device and post-processing processes sequentially performed on the output of the printing process. The post-processing processes include post-processing processes performed by post-processing devices, such as lamination, binding, and cutting, as well as post-processing processes performed by workers, such as inspection, packaging, and shipping. Of course, a single product does not necessarily require all of these processes; only some of them may be required. The workflow management system of FIG. 1 can define and manage workflows. However, this embodiment will mainly focus on managing the workflow during execution, and workflow configuration will be explained as needed. Workflow configuration includes, for example, the processes and their order, and the setting values (parameters) for each process. In the present embodiment, the following mainly describes the function of managing the progress of a job when the job is executed according to a predefined workflow, among the functions of the workflow management system.

[0014] The workflow management system of this embodiment includes an information processing device 101, an image forming device 102, a post-processing device 103, a position management system 700, and a process management system 1200. The information processing device 101, the image forming device 102, the position management system 700, and the process management system 1200 are connected to one another via a network 100. The position management system 700 and the process management system 1200 will be described later with reference to FIGS. 7 and 12. The image forming device 102 analyzes print data transmitted from the information processing device 101 and the like, converts it into a dot image for printing, page by page. The printed matter output from the image forming device 102 is handed over to the post-processing device 103 by an operator, or is handed over to the post-processing device 103 via a belt conveyor (not shown).

[0015] The post-processing device 103 is an offline device that operates independently without communicating with the image forming device 102 or the information processing device 101. The post-processing device 103 performs processes such as cutting, laminating, folding, and binding on printed materials to be processed that are placed in a predetermined position. It is also possible to use multiple post-processing devices to perform cutting after binding. Note that while FIG. 1 illustrates one each of the information processing device 101, image forming device 102, and post-processing device 103, any number of each device may be provided. For example, printed materials output by multiple image forming devices may be processed by multiple post-processing devices 103. Furthermore, a separate post-processing device 103 may be provided for each post-processing step.

[0016] In-process items of a job, such as output from a printing process or output from a post-processing process, are transported by, for example, a worker to the location of the next process, where processing in that process is carried out. If a job is currently being processed at that time, the system waits for the job to be completed. In this embodiment, a wireless tag is attached to the in-process item or returnable box, and the latest location of the in-process item is identified based on the link between the job and the wireless tag, thereby identifying the latest process of the job, i.e., the process currently being processed or awaiting processing. The configuration is described below.

[0017] [Hardware configuration of information processing device] 2 is a diagram showing an example of the hardware configuration of the information processing device 101. A central processing unit (CPU or processor) 201 reads control programs stored in a read-only memory (ROM) 202 or a hard disk drive (HDD) 204 and executes various control processes. A random access memory (RAM) 203 is used as a temporary storage area such as the main memory or work area of the CPU 201. The HDD 204 stores image data and various programs. Note that the configuration may include another storage device such as a solid-state drive (SSD) instead of or in addition to the HDD.

[0018] The keyboard 205 is an input device that serves as an instruction input unit, and issues control command instructions, text input, etc. to applications (described later). The pointing device 206 is also an input device that serves as an instruction input unit together with the keyboard 205, and issues control command instructions to applications (described later).

[0019] The display 207 is an output device that serves as a display unit, and displays commands input from the keyboard 205 or pointing device 206, the status of applications (described later), and the like. The network I / F 208 connects the information processing device 101 to a network (such as a LAN, an intranet, or the Internet). A user interface (UI) is provided by the display 207, keyboard 205, and pointing device 206. The information processing device 101 transmits and receives various types of information to and from other devices on the network using the network I / F 208.

[0020] The position management system 700 and the process management system 1200 may also have the same hardware as the information processing device 101. Furthermore, the image forming device 102 and the post-processing device 103 may also have the same hardware as the information processing device 101 with respect to a control unit that processes information. However, the image forming device 102 and the post-processing device 103 each further have mechanisms for printing and post-processing and their control units. Furthermore, since the post-processing device 103 is an offline device in this embodiment, it does not need to have a network I / F 208.

[0021] [Software configuration of information processing device] 3 is a diagram showing an example of the software configuration of the information processing device 101. A print workflow application 301 is a program module that is installed and operates on the HDD 204 of the information processing device 101, loaded into the RAM 203 at the time of execution, and executed by the CPU 201. The print workflow application 301 has a UI unit 302, a print job management unit 303, a print job control unit 304, a print processing unit 305, and a device management unit 306.

[0022] The UI unit 302 constructs a graphical user interface (GUI) and receives various input operations from the user, and issues instructions to execute the corresponding processes. The print job management unit 303 accesses print job information data 307 (described later) and executes reference to various information of the print job that the print workflow application 301 transmits to the image forming apparatus 102 . A print job control unit 304 controls the execution of various functions (such as sending, editing, and deleting a print job) for a print job in the print workflow application 301. In response to a print job transmission instruction received from the print job control unit 304, the print processing unit 305 transmits the content data and job ticket data of the print job to the image forming apparatus 102. The device management unit 306 manages various information (including identification names, addresses, etc.) of the image forming apparatus 102 to which the print workflow application 301 sends a print job. The print job information data 307 is a database that manages information related to print jobs (a print job information table and a product information table) described later. The print job information table will be described later in FIG. 5. The product information table will be described later in FIG. 6(A).

[0023] The print workflow application 301 is assumed to be installed and run on the HDD 204 of the information processing device 101, but may also be configured on the cloud and provided as a cloud service by being accessed from a web browser on the information processing device 101. Furthermore, the print job information data 307 need not only be configured to be stored on the HDD 204 of the information processing device 101, but may also be stored in another information processing device connected via a network (such as a database server (including on the cloud)).

[0024] [Print job management screen configuration] FIG. 4 is a diagram showing an example of a print job management screen of the print workflow application 301. As shown in FIG.

[0025] When the print operator instructs the information processing apparatus 101 to execute the print workflow application 301, the CPU 201 loads the program of the print workflow application 301 into the RAM 203 and executes it. The instruction may be given via the keyboard 205 or the pointing device 206. This starts the print workflow application 301. When the print workflow application 301 starts, the UI unit 302 displays a print job management screen 401 as shown in FIG. 4 on the display 207. Here, the print workflow application 301 may be provided by a cloud service. In that case, the print job management screen 401 may be displayed on the web browser on the information processing apparatus 101 by accessing the cloud service from the web browser.

[0026] The print job management screen 401 shows the print job management screen in the print workflow application 301. The function menu 402 shows a menu of functions that can be executed on the print job management screen 401. The function menu 402 has a print button 403 and a delete button 405. The print button 403 is a button for issuing a print instruction for a print job (an instruction for actual printing). Actual printing is a term used in contrast to preliminary printing for proofreading or proof printing, and is the printing of a printed material that will become a product after proofreading. The delete button 405 is a button for issuing an instruction to delete a print job. Note that the function menu 402 may also have an edit button or the like for issuing an instruction to edit a print job.

[0027] The print job list 406 shows a list displaying a list of print jobs managed by the print workflow application 301. The print workflow application 301 accesses and acquires print job information stored in the print job information data 307 via the print job management unit 303, and displays the print jobs to be printed in the print job list 406. Therefore, print job information other than the information exemplified in Fig. 4 may be displayed in the print job list 406. The print operator selects a print job displayed in the print job list 406 with the pointing device 206 or the like, and issues a print instruction, a delete instruction, an edit instruction, or the like to the selected print job by pressing a function button arranged in the function menu 402.

[0028] The device list 407 displays a list of image forming devices managed as output destinations by the print workflow application 301. The print workflow application 301 acquires, via the device management unit 306, information on the image forming devices 102 that are communicably connected via the network 100 or the like, and displays the information in the device list 407.

[0029] [Print Job Table Configuration] Fig. 5 is a diagram showing an example of a print job information table 501 stored in the print job information data 307. In the example shown in Fig. 5, the print job information table 501 has fields such as a job ID, a deliverable number, a product name, the number of copies, a content name, an order date, and a scheduled shipping date. The product name is a value linked to detailed print setting (print attribute) information defined in the product information table shown in Fig. 6(A) described later. The content name is link information to a file name that serves as content data used when printing the print job.

[0030] [Product information table configuration] FIG. 6A shows an example of a product information table 601 stored in the print job information data 307. The product information table 601 defines detailed settings related to printing (such as output paper size, finished size, paper type, orientation, single-sided / double-sided, stapling, punching, folding, binding, trimming, and paper output destination). The product information table 601 is created in advance by an installer, such as a system engineer, when the print workflow application 301 is installed, in accordance with the order details of the print product handled by the print workflow application 301. The print job management unit 303 retrieves detailed print settings from the product information table using the product name described above as a key. For example, if the product name is "Saddle-stitched, imposed, A4, double-sided, landscape," the retrieved settings include output paper size "320 x 450," paper type "high-quality paper," ..., single-sided / double-sided "double-sided," ..., binding "ON," saddle-stitching "ON," trimming "ON," and lamination "ON." These settings determine the workflow's elemental steps, their order, and the settings for each elemental step (print settings, post-processing settings, etc.).

[0031] [Workflow Information Table] FIG. 6B shows a workflow information table, in which a workflow including multiple element processes is defined. The workflow information table may be stored in the print job information data 307, but may also be stored elsewhere. The workflow information table stores a "workflow ID (WFID)" that uniquely identifies the workflow and the processing order of each process. Taking "WF001" in FIG. 6B as an example, a workflow is defined in which each process is processed in the order of [Print] → [Binding] → [Cutting] → [Inspection] → [Delivery]. The information in the product information table in FIG. 6A and the workflow information table in FIG. 23 is set in advance by a print operator or administrator using the UI (not shown) of the print workflow application 301. While FIG. 6B illustrates an example of a serial workflow, a workflow combining multiple components can also be generated or set based on the detailed information table 601, as shown in FIG. 18. Note that the "leave" for each process in FIG. 23 refers to the time left before each process is executed, but all of these leave times may be set to 0, indicating that no leave is performed. In this case, there is no need to set a timeout. The progress of a job is managed according to the workflow information table. This workflow is presented to the worker, who then moves the output (work in progress) of each process to the next process in accordance with the workflow and executes the processing of that process.

[0032] In a serial workflow, jobs and workflows may correspond one-to-one, but when multiple components are combined to generate a deliverable, the series of processes for generating each component may be called a job.

[0033] [Location management system configuration] FIG. 7 is a diagram showing an example of the configuration of a location management system 700 according to this embodiment. The location management system 700 is a system that manages item data in a database. Here, the items refer to work-in-progress items in each process of a job to be managed, and more specifically, may be cases that house the work-in-progress items. Alternatively, the work-in-progress items themselves may be the items to be managed, regardless of whether they are housed in a case. For example, the former may be used in the case of printed materials that will be completed as booklets or multiple copies of printed materials, while the former may be used in the case of printed materials that are managed sheet by sheet.

[0034] The location management system 700 includes location tags 707 installed at different locations, item tags 709a and 709b attached to items, at least one tag reader 705b, a mobile system 714, and a management server 701. It may further include an information processing device 101 as a terminal. The mobile system 714, tag reader 705b, and management server 701 are connected to a network 100. The network 100 may be a wired network, a wireless network, or any combination thereof. Examples of the network 100 include the Internet, an intranet, an intranet, and a cloud network.

[0035] Location tag 707 is a wireless device that is installed at each location where a reader may store an item in location management system 700, and has unique tag identification information (hereinafter referred to as tag ID) 708 embedded in the tag. The installation location of location tag 707 may be fixed or may be changeable at each location.

[0036] Item tags 709a, 709b are wireless devices attached to each item managed by the position management system 700, and have unique tag identification information (hereinafter, tag ID) 710a, 710b embedded in the tag. As an example of linking a job and an item tag, Fig. 7 shows an example in which item tag 709a is attached to a returnable box 711a that stores a job when it is moved between work processes, and an example in which item tag 709b is attached to a work instruction sheet 711b for issuing work instructions, but this is not limiting. Here, when items with item tags attached, such as returnable box 711a and work instruction sheet 711b, are transported by a reader or moved automatically, item tags 709a, 709b also move along with the items.

[0037] In the following description, when it is not necessary to distinguish between the item tags 709a and 709b, the alphabet at the end of the reference numeral will be omitted and they will be collectively referred to as the item tag 709. The same applies to the tag readers 705 (705a, 705b), tag IDs 710 (710a, 710b), items 711 (711a, 711b), and other subsequent elements.

[0038] In an embodiment of the present invention, each of the tags, such as the position tag 707 and the item tag 709, is assumed to be a passive RFID tag (passive tag). A passive tag is composed of a small IC (Integrated Circuit) chip with built-in memory and an antenna, and stores identification information and other information that identifies the tag in the memory. In this embodiment, the identification information is simply referred to as an ID, and the identification information that identifies the tag is also referred to as a tag ID. Note that the tag ID may also be considered as information that identifies the object to which the tag is attached. The IC chip of the passive tag operates using the energy of electromagnetic waves emitted from a tag reader, modulates the tag ID and other information stored in the memory into an information signal, and transmits (returns) the information signal from the antenna.

[0039] In another embodiment, each tag may be an active RFID tag. When each tag actively (e.g., periodically) transmits information to the surroundings using power from a built-in battery, the tag may be called a beacon tag. In yet another embodiment, each tag may be a wireless device that responds to a signal from a reader and transmits information back using, for example, the NFC (Near Field Communication) method or the Bluetooth (registered trademark) method. Each tag may be called by any name, such as an IC tag, an IC card, or a responder. The location tab 707 and the item tag 709 may also be called a wireless tag or a wireless device.

[0040] The portable system 714 includes at least a tag reader 705a. The tag reader 705 is a reading device capable of reading information stored in a wireless device such as an RFID tag. The tag reader 705 can detect an item 711, for example, by reading a tag ID 710 from an item tag 709 attached to the item 711. The tag reader 705 performs reading periodically or in response to some trigger such as a user operation, and transmits the tag reading result to the management server 701. The tag reader 705 may be capable of communicating directly with the management server 701, or may be capable of communicating indirectly with the management server 701 via some relay device (for example, a user terminal 706, which will be described later). An example of a specific configuration of the tag reader 705 will be further described later.

[0041] 7, the mobile system 714 further includes a user terminal 706. The user terminal 706 may be any type of terminal device or information processing device, such as a notebook PC (Personal Computer), a tablet PC, a smartphone, or a smart watch. The user terminal 706 may be used for interaction with the user 704 via the location management system 700. An example of a specific configuration of the user terminal 706 will be further described later.

[0042] The management server 701 is an information processing device that manages, in a database, status, location information, and other information related to the inspection of multiple items 711. The management server 701 may be implemented as an application server, database server, or cloud server using, for example, a high-performance general-purpose computer. The hardware of the management server 701 may be that shown in FIG. 2. The management server 701 receives tag reading results from the tag reader 705 and updates the database based on the received tag reading results.

[0043] 7 shows a single management server 701, but the functions of the management server 701, which will be described in detail later, may be provided by a single device, or may be provided by multiple physically separate devices working together. Also, in this embodiment, an example will be described in which the management server 701 holds the database, but a device separate from the management server 701 may hold part or all of the database. For example, some of the data may be held by a wireless device (e.g., a location tag or an item tag), a tag reader 705, or a user terminal 706.

[0044] 7 shows an example in which portable system 714 includes tag reader 705a and user terminal 706, which are separate devices. However, portable system 714 is not limited to this example. For example, tag reader 705a may have some or all of the functions of user terminal 706, which will be described later, and user terminal 706 may have some or all of the functions of tag reader 705a, which will be described later. Furthermore, the functions of management server 701 described in this embodiment may be implemented in user terminal 706.

[0045] [Tag reader configuration] 8 is a block diagram showing an example of the configuration of tag reader 705 in this embodiment. Referring to Fig. 8, tag reader 705 includes a control unit 801, a storage unit 802, a communication unit 803, a measurement unit 804, an operation unit 805, and a reading unit 806.

[0046] The control unit 801 has a memory for storing a computer program and one or more processors (e.g., a CPU) for executing the computer program. The control unit 801 controls the overall functions of the tag reader 705 described in this embodiment. For example, the control unit 801 causes the reading unit 806 to read an RFID tag within the tag reading range, and temporarily stores the read information, the read time, and the signal reception level as read result data in the storage unit 802. In addition, in parallel with reading the RFID tag, the control unit 801 causes the measurement unit 804 to measure the position of the tag reader 705 and stores the measurement result in the storage unit 802. The control unit 801 then transmits the read result data and measurement result data stored in the storage unit 802 to the management server 701 via the communication unit 803, together with the reader identification information (also referred to as a reader ID) of the own device.

[0047] The storage unit 802 may include any type of storage medium, such as a semiconductor memory such as a ROM or RAM, an optical disk, or a magnetic disk. In this embodiment, the storage unit 802 stores the above-mentioned reading result data, measurement result data, and the reader ID of the tag reader 705.

[0048] The communication unit 803 is a communication interface for the tag reader 705 to communicate with the management server 701. For example, the communication unit 803 may be a wireless local area network (WLAN) interface for communicating with a WLAN access point, or a cellular communication interface for communicating with a cellular base station. The communication unit 803 may also be a connection interface for connecting to a relay device (for example, a Bluetooth (registered trademark) interface or a universal serial bus (USB) interface).

[0049] The measurement unit 804 is a unit capable of measuring the position of the tag reader 705. In this embodiment, the measurement unit 804 measures the relative movement amount of the tag reader 705 from a certain reference position using a self-location estimation technology also known as pedestrian relative positioning (PDR), and outputs the measured movement amount to the control unit 801. The reference position for measuring the relative movement amount may be, for example, the position of the tag reader 705 at the time the tag reader 705 is activated. The relative movement amount of the tag reader 705 may be treated as a relative position. For example, the measurement unit 804 includes a three-axis acceleration sensor 804a, a gyro sensor 804b, and a geomagnetic sensor 804c. The three-axis acceleration sensor 804a measures the acceleration applied to the tag reader 705 in a device coordinate system specific to the tag reader 705, and outputs first sensor data. Gyro sensor 804b measures the angular velocity of tag reader 705, i.e., the change in attitude of tag reader 705, and outputs second sensor data. Geomagnetic sensor 804c measures the orientation of tag reader 705 in real space, and outputs third sensor data.

[0050] Based on the sensor data from these sensors, measurement unit 804 can measure the relative movement amount of tag reader 705 by accumulating the acceleration while converting the direction of the acceleration of tag reader 705 into a direction in the coordinate system of real space. The relative movement amount output from measurement unit 804 to control unit 801 may be a two-dimensional vector in a horizontal plane, or a three-dimensional vector that also includes a component in the height direction.

[0051] As will be described later, in this embodiment, the location coordinates of the installation location of each location tag 707 are known and registered in a database. Therefore, the current absolute location (position coordinates) of the tag reader 705 can be estimated based on the relative movement amount from the time when the tag reader 705 detected a certain location tag 707 to the current time and the known location coordinates of the location tag 707. In this embodiment, an example in which the management server 701 estimates the absolute location of the tag reader 705 will be mainly described. However, the control unit 801 or the measurement unit 804 of the tag reader 705 may access a database to estimate the absolute location of the tag reader 705. In other embodiments, the measurement unit 804 may measure the current geographical location of the tag reader 705 using a global positioning system (GNSS) such as a global positioning system (GPS). In still another embodiment, the measurement unit 804 may perform base station positioning or wireless LAN positioning, which estimates the current location using the known location coordinates of the connected base station or wireless LAN access point.

[0052] Note that instead of tag reader 705 including measurement unit 804, mobile system 714 may include a measurement device separate from tag reader 705 (for example, capable of measuring the amount of relative movement using a self-position estimation technique such as PDR).

[0053] The operation unit 805 accepts operations by the user 704. The operation unit 805 includes, for example, a physical input device such as a button, switch, or lever arranged on the housing of the tag reader 705. The operation unit 805 accepts operations by the user 704 via the input device and outputs an operation signal to the control unit 801. The operation unit 805 may also include an audio input interface such as a microphone.

[0054] The reading unit 806 is a unit capable of reading information stored in each of the position tags 707 and item tags 709 under the management of the position management system 700. Referring to FIG. 8 , the reading unit 806 includes an RF controller 807, a power amplifier 808, a filter 809, a first coupler 810, a second coupler 811, an antenna 812, a power detection unit 813, and a canceller 814. The RF controller 807 outputs a transmission signal (e.g., a signal modulated in the UHF band) from its TX terminal to the power amplifier 808 under the control of the control unit 801. The power amplifier 808 amplifies the transmission signal input from the RF controller 807 and outputs it to the filter 809. The amplification factor of the transmission signal here may be variably controllable; the higher the amplification factor, the stronger the output intensity of the electromagnetic waves radiated from the tag reader 705. The filter 809 may be, for example, a low-pass filter, which removes unnecessary low-frequency components from the transmission signal amplified by the power amplifier 808.

[0055] The first coupler 810 distributes the transmission signal that has passed through the filter 809 to the coupler 811 and the power detection unit 813. The second coupler 811 outputs the transmission signal input from the first coupler 810 to the antenna 812, and outputs the reception signal input from the antenna 812 to the RF controller 807. The antenna 812 transmits the transmission signal input from the coupler 811 into the air as an electromagnetic wave. The antenna 812 also receives a signal returned from an RFID tag present within the reading range of the tag reader 705 in response to the transmission signal, and outputs the reception signal to the coupler 811. As one example, the antenna 812 may be an omnidirectional antenna. As another example, the antenna 812 may be a directional antenna whose beam direction can be variably controlled.

[0056] The power detection unit 813 detects the power level of the signal input from the first coupler 810 and outputs a signal RF_DETECT indicating the detected power level to the control unit 801. The canceller 814 receives a signal CARRIER_CANCEL indicating the power level of the carrier wave from the control unit 801. The canceller 814 then cancels the carrier wave component of the transmission signal based on CARRIER_CANCEL, thereby extracting the desired signal component of the reception signal to be output to the RX terminal of the RF controller 807. The RF controller 807 demodulates the signal input from the RX terminal, acquires the tag ID and other information returned from the RFID tag, and outputs the acquired information to the control unit 801. The RF controller 807 also measures the reception level (also called reception intensity) of the signal input from the RX terminal and outputs the measurement result to the control unit 801.

[0057] [User device configuration] 9 is a block diagram showing an example of the configuration of a user terminal 706 included in a mobile system 714 of the present invention. Referring to FIG. 9, the user terminal 706 includes a control unit 901, a storage unit 902, a communication unit 903, an image capturing unit 904, an operation unit 905, a display unit 906, an audio output unit 907, and a vibration unit 908.

[0058] The control unit 901 includes a memory for storing computer programs and one or more processors for executing the computer programs. The processor may be a CPU or an integrated circuit (IC) such as a microcontroller (e.g., a single-chip microcomputer). The control unit 901 may include a timer circuit or a software timer for measuring time. The control unit 901 controls the overall functions of the user terminal 706 described in this embodiment. For example, when the location of an item 711 is inspected in the location management system 700, the control unit 901 displays a screen on the display unit 906 that displays the current location of the portable system 714 and the locations of surrounding items. The location of the item to be inspected is indicated on this screen, and the user 704 is guided to the location of the item. Some examples of screens for guiding the user 704 to the location of the item will be further described below.

[0059] The storage unit 902 may include any type of storage medium, such as a semiconductor memory such as a ROM or RAM, an optical disk, or a magnetic disk. In this embodiment, the storage unit 902 temporarily stores, for example, a map image and location information (of the mobile system 714 and the item 711) received from the management server 701 (described later) for on-screen display.

[0060] The communication unit 903 is a communication interface for the user terminal 706 to communicate with the management server 701. For example, the communication unit 903 may be a WLAN interface or a cellular communication interface. Although not shown in FIG. 9, the user terminal 706 may further include a connection interface (for example, a Bluetooth (registered trademark) interface or a USB interface) for connecting to a peripheral device.

[0061] The image capturing unit 904 is a so-called camera unit that captures images of the real space and generates image data of still or moving images. The image capturing unit 904 outputs the generated image data to the control unit 901. For example, the image data generated by the image capturing unit 904 may be used for optical character recognition (OCR) or for reading visible codes such as barcodes or QR codes (registered trademark).

[0062] The operation unit 905 accepts operations and information input by the user 704. The operation unit 905 includes input devices such as a touch sensor, a keypad, a keyboard, a button, or a pointing device. The operation unit 905 accepts operations by the user 704 via the input devices and outputs operation signals to the control unit 901. The operation unit 905 may further include other types of input devices, such as a voice input interface like a microphone or a sensor that detects vibrations.

[0063] The display unit 906 displays images and information. The display unit 906 may be, for example, a liquid crystal display (LCD) or an organic electroluminescence (OLED). The audio output unit 907 outputs audio. The audio output unit 907 may be, for example, a speaker. The vibration unit 908 vibrates the user terminal 706. The vibration unit 908 may be, for example, a vibrator including an eccentric motor. One or more of the display unit 906, the audio output unit 907, and the vibration unit 908 may function as an alarm unit 909 that notifies the user 704. Although not shown in FIG. 9 , a notification function similar to the above-mentioned alarm unit 909 may be provided in the tag reader 705.

[0064] [Management Server Configuration] 10 is a block diagram showing an example of the configuration of the management server 701 in this embodiment. Referring to FIG. 10, the management server 701 includes a communication unit 1003, an item database (DB) 1001, and a management unit 1002.

[0065] The communication unit 1003 is a communication interface that allows the management server 701 to communicate with other devices. The communication unit 1003 may be a wired communication interface or a wireless communication interface. In this embodiment, the communication unit 1003 communicates with the mobile system 714 (e.g., one or both of the tag reader 705a and the user terminal 706). The item DB 1001 is a database that stores status, location information, and other information related to the inspection of multiple items under the management of the system. In this embodiment, the item DB 1001 includes an item table 1004, a location table 1005, a reader table 1006, a user table 1007, a movement amount table 1008, and a tag detection table 1009. The management unit 1002 is a collection of multiple software modules that provide management functions for managing data in the item DB 1001. Each software module may be operated by one or more processors (not shown) of the management server 701 executing a computer program stored in a memory (not shown). In this embodiment, the management unit 1002 includes a position estimation unit 1011 .

[0066] [Table configuration] 11A to 11F show examples of the configurations of an item table 1004, a location table 1005, a reader table 1006, a user table 1007, a movement amount table 1008, and a tag detection table 1009 of the item DB 1001, respectively.

[0067] The item table 1004 has six data items: tag ID 1111, item ID 1112, name 1113, type 1114, location 1115, and coordinates 1116. The tag ID 1111 is identification information that uniquely identifies the item tag 709 attached to each item 711 that is under the management of the system and is a managed item. The value of the tag ID 1111 is the same as the value of the tag ID stored internally in the corresponding item tag 709. The item ID 1112 is identification information that uniquely identifies each item 711. The name 1113 indicates the name of each item 711. The type 1114 indicates the type into which each item 711 is classified.

[0068] The values of the name 1113 and type 1114 of each item 711 may be determined by a user and registered in advance via a user interface provided by the management unit 1002. Alternatively, the values of the name 1113 and type 1114 may be stored in the item tag 709 as item-related information and read by the tag reader 705. In the latter case, the management server 701 may receive the values of the name 1113 and type 1114 of each item 711 from the tag reader 705 in response to the initial tag reading from the item tag 709 of the item 711, and register them in the item table 1004. The location 1115 indicates the location where each item 711 was last detected by the tag reader 705, using a location ID that identifies the location. The coordinates 1116 indicate the location coordinates of a point where each item 711 is estimated to be located. As will be described later, the values of location 1115 and coordinates 1116 can be updated by the position estimation unit 1011 when the movement of an item is detected by the tag reader 705. For example, a record in the item table 1004 is added when a new managed item is generated, and the values of the items from tag ID 1111 to type 1114 may be registered according to the association between the item tag 709 and the managed item 711. Furthermore, according to this association, the item tag 709 with tag ID 1111 is attached to the item 711 with the associated item ID 1112. When the managed item is completed and shipped and is no longer under management, the corresponding record in the item table 1004 may be deleted.

[0069] The location table 1005 has six data items: tag ID 1121, location ID 1122, name 1123, coordinates 1124, map image 1125, and scale 1126. The tag ID 1121 is identification information that uniquely identifies the location tag 707 installed at each location 712 under the management of the system. The value of the tag ID 1121 is the same as the tag ID value stored internally in the corresponding location tag 707. The location ID 1122 is identification information that uniquely identifies each location 712. The name 1123 indicates the name of each location 712. The coordinates 1124 indicate the location coordinates of the installation location of the location tag 707 installed at each location 712. The map image 1125 is a data item in which map image data of each location 712 is stored. Instead of the map image data itself, address information or identification information that identifies the map image data may be used. The scale 1126 indicates a ratio for converting a distance on the map of the map image 1125 into a distance in real space (e.g., how many meters one pixel of the image corresponds to in real space). The map image data stored in the map image 1125 may be acquired from an external data source or uploaded by a user and updated as needed. For example, a record in the location table 1005 is added when a new managed location is added, and the values of the items from the tag ID 1121 to the scale 1126 may be registered according to the association between the location tag 707 and the managed location 712. Furthermore, according to this association, the location tag 709 with the tag ID 1121 is attached to the location 712 with the associated location ID 1122. When a managed location is deleted, the corresponding record in the location table 1005 may be deleted. For example, if the location ID 1122 is used as identification information for each process and the process name is registered as the location name 1123, the location tag 707 and the process can be linked using the location table 1005.

[0070] The reader table 1006 has three data items: reader ID 1131, name 1132, and user 1133. The reader ID 1131 is identification information that uniquely identifies each tag reader 705 used in the system. The name 1132 represents the name of each reader. The user 1133 represents the user 704 who uses the tag reader 705 by the value of the user ID 1141 in the user table 1007. For example, a record in the reader table 1006 may be added when a new tag reader 705 is introduced, and the values of each item may be registered, and the record may be updated when the registered content, for example, the name or user, is changed. Furthermore, when a tag reader 705 is removed from the system, the corresponding record in the reader table 1006 may be deleted.

[0071] The user table 1007 has two data items: a user ID 1141 and a name 1142. The user ID 1141 is identification information that uniquely identifies each user 704 who uses the location management system 700. The name 1142 represents the name of each user. Although not shown in FIG. 11(D), the user table 1007 may further include authentication information (e.g., a password) used by each user 704 when logging in to the system. It is also possible to associate the user 704 with the user ID 1141 by attaching an item tag 709 to the user 704. While an item tag 709 is attached in this example, tags can also be configured to distinguish between "user" and "item," and the table configuration may change accordingly. For example, each item in the user table 1007 may be registered when a new user 704 is added and updated when the registered name or user is changed. Furthermore, when a user 704 is deleted from the system, the corresponding record in the user table 1007 may be deleted.

[0072] The movement amount table 1008 is a table for storing records of measurement result data received from the tag reader 705 (hereinafter referred to as measurement result records). The movement amount table 1008 has three data items: measurement time 1151, reader ID 1152, and movement amount 1153. The measurement time 1151 indicates the time when measurement was performed for the measurement result indicated by each measurement result record. The reader ID 1152 is identification information that identifies the tag reader 705 that performed the measurement for the measurement result indicated by each measurement result record. The movement amount 1153 indicates the relative movement amount as a measurement result. Here, the movement amount 1153 indicates the relative movement amount with respect to a reference position in the form of a two-dimensional vector in a coordinate system of real space.

[0073] The tag detection table 1009 is a table for storing records of read result data received from the tag reader 705 (hereinafter referred to as read result records). The tag detection table 1009 has five data items: read time 1161, tag ID 1162, reader ID 1163, reception level 1164, and detection position 1165. The read time 1161 indicates the time when the tag ID was read for each read result record. The tag ID 1162 indicates the tag ID read for each read result record. The reader ID 1163 is identification information that identifies the tag reader 705 that read the tag for each read result record. The reception level 1164 indicates the reception level of the signal received by the tag reader 705 when reading the tag for each read result record. The detection position 1165 represents the position coordinates of the location where the tag reader 705 was located when tag reading from the item tag 709 was performed (ie, the detection position of the item tag 709 and the corresponding item 711).

[0074] For example, a predetermined position where position information has been measured in advance may be determined as a reference position, and when tag reader 705 is used, the power may be turned on at that reference position to measure the amount of relative movement based on that position. The position information of the reference position may be stored in position estimation unit 1011 or item DB 1001, and the absolute position of tag reader 705 may be determined by adding the relative position measured by tag reader 705 to that reference position. This is just one example, and once measurement of the relative position from the reference position begins, the measurement may continue without initializing the relative position even if the main power is turned off. Of course, if tag reader 705 has a positioning function that identifies position coordinates, such as a high-precision GNSS receiver, the measured position information may be recorded as movement amount 1153.

[0075] [Process control system overview] FIG. 12 is a diagram showing an example of the configuration of a process control system 1200 according to the present invention. The process management system 1200 is a system that generates a process management screen in response to a process management screen request received from a web browser on the information processing device 101. Here, the process management screen is a screen that displays information about the image forming devices 102 and post-processing devices 103 within the area of the printing factory, and about the processes performed by each device.

[0076] The process management system 1200 includes a process management UI 1201, a process management service 1202, a process database (DB) 1203, a job management service 1206, and a job database (DB) 1207. The process DB 1203 includes a job table 1204 and a process location table 1205, and the job DB 1207 includes a job status table 1208. The process location table 1205 is a table that links the tag reader 705 with a process when the tag reader 705 is installed at a fixed position corresponding to each process. However, this is used in a modified example described later and is not used in this embodiment. In this embodiment, the tag reader 705 is used as a tag reader that is carried by the worker and moves around, and therefore, as explained above, the position tag 707 is detected to identify the process to which the job to which the item tag 709 is attached belongs.

[0077] When the process management UI 1201 receives a process management screen request from the information processing device 101, it generates a process management screen based on information collected by the process management service 1202 and transmits it to the information processing device 101. In response to the request from the process management UI 1201, the process management service 1202 obtains information from the location management system 700, job management service 1206, and process DB 1203 and transmits the information to the process management UI 1201.

[0078] [Table Overview] 13A to 13C show examples of the job table 1204, the process position table 1205, and the job status table 1208 in this embodiment.

[0079] The job table 1204 includes items of tag ID 1311 and job ID 1312, and is a table for managing the tag ID 710 of the item tag 709 attached to the item 711 in Fig. 7 in association with the job ID of the job stored in the item 711. The tag ID 710 may be linked with the job ID by sequentially reading the barcode attached to the item 711, such as a returnable box or a work instruction sheet, and the barcode attached to the job. The linking method is not limited here.

[0080] The process location table 1205 includes items for each process 1321 within the area of the printing factory and coordinates 1322 for each process. The process location table 1205 is a table that manages information for each process 1321 within the area of the printing factory and coordinates 1322 for each process. This table defines coordinate information in advance, indicating where each process is located within the area of the printing factory. The process management service 1202 acquires tag ID information 1111 and its coordinates 1116 detected by the tag reader 705 installed for each process from the item table 1004 of the management server 701. The process in the area of the printing factory in which the tag ID 710 is located is identified based on the acquired tag ID coordinates 1116 and the information in the process location table 1205. Here, as a method for identifying the process, for example, the distance between the coordinates in the process location table 1205 and the tag ID coordinates 1116 may be calculated, and if the distance is less than a threshold, it may be determined that the tag ID 710 is located within that process. Alternatively, the coordinates 1322 in the process position table 1205 may be specified as an area such as (X1, Y1) to (X11, Y11), and if the coordinates 1116 of the detected tag ID are within that area, it may be determined that the tag is present in that process.

[0081] The job status table 1208 includes items for job ID 1331 and job status 1332. The job status table 1208 is a table for managing the job ID 1331 and job status 1332. Here, a job with a job status 1332 of "End of production" indicates that all processes have been completed, and a job with a job status of "Finished printing" indicates that printing has been completed and processing is being carried out in an offline process. A job with an item tag 709 attached and whose process is managed based on the detected position may be, for example, a job with a status of "Finished printing" that is being processed in an offline process. Jobs before printing and jobs in the middle of printing can be managed without attaching an item tag 709, because the status can be acquired by the image forming apparatus 101 connected online.

[0082] [Process management services] FIG. 14 shows an example of the process management service 1202 in this embodiment. The process management service 1202 includes an error process management unit 1401, a dependent process management unit 1402, and a priority process determination unit 1403. Here, a priority process is a process that has the highest priority for dealing with a fault or error when a fault or error occurs simultaneously in one or more processes and causes the processes to stop. In other words, it is a process that can quickly return a process from a stopped state to an operating state.

[0083] The error process management unit 1401 includes a job identification unit 1411 and a process identification unit 1412. When work is stalled at a process, the job identification unit 1411 is used to identify the error-related job, and the downstream process of the error process in the workflow is identified from the job information of the identified error-related job. An error process is a process in which an error has occurred, and is assumed to be a work stall, but is not limited to this and may also include equipment failure. An order job refers to a job that includes component information necessary to create a deliverable. An error-related job refers to such a job that includes an error process in the workflow and whose execution of the error process has not been completed. A downstream process refers to a process that is performed after the process of interest, as will be described below using an example.

[0084] The error process may be identified as follows. For example, if the error process is a process performed by a device connected online to the information processing device 101, such as the image forming device 102, the information processing device 101 can acquire error information sent from that device online. Therefore, the error process can be identified based on the error information acquired online. The processes from which error information can be acquired may be limited to printing processes.

[0085] On the other hand, if an error can be detected in a post-processing process performed by an offline device, error information occurring there can also be obtained in the post-processing process. One method for this is, for example, to provide error information online. That is, offline post-processing devices are often configured to detect errors and notify them with a lamp or sound. Therefore, such an error detection signal can be configured to be transmitted to the information processing device 101 as error information. Alternatively, an error notification notified by a lamp or sound can be detected by a sensor and transmitted to the information processing device 101 as online error information. Alternatively, the processing time required for each process is largely determined by the processing volume of each job. Therefore, the information processing device 101 can estimate the required time for each process and job, and if there is a job that is being executed beyond the estimated required time, it can assume that an error has occurred in that process and generate error information indicating the occurrence of an error in that process.

[0086] The dependent process management unit 1402 includes a dependent process determination unit 1421, and for a job in progress, references, for example, the print job information table 501 and the product information table 601 to identify dependent processes that are processes that use multiple parts. Multiple parts are work-in-progress obtained through multiple processes; for example, a bookbinding process that combines a cover and a body (the body part) to bind a book is a dependent process that binds a book using work-in-progress from the process that produces the cover and the process that produces the body. Of the dependent processes, those downstream of the error process are called remaining dependent processes, and the dependent process management unit particularly identifies remaining dependent processes for each job.

[0087] The first embodiment will be described using the above figures. FIG. 15 is a flowchart showing the process when an error occurs in the post-processing step, particularly in the flow of the workflow management procedure proposed herein. In the workflow management procedure, jobs to be executed are generated and registered, and can be executed or deleted on the print management screen of FIG. 4. For a selected job, the item tag attached to the work-in-progress can be detected and the current step can be identified and managed from its location. Management can be performed, for example, by displaying job identification information corresponding to the item tag on a floor plan of the work site according to the step. The process of FIG. 15 represents a process for dealing with a step in the management procedure in which an error has occurred. The process of FIG. 15 is realized, for example, by the CPU 201 of the information processing device 101 executing a program loaded into the RAM 203. In other words, the CPU 201 of the information processing device 101 is responsible for executing each step in FIG. 15.

[0088] In S1501, a priority process is determined. In S1502, a corresponding worker is determined for the process determined as the priority process. S1502 is optional in this embodiment, and an example in which S1502 is skipped will be described here.

[0089] In S1503, the CPU 201 outputs a message indicating the determined priority process. In S1503, for example, the message may be displayed on the UI screen shown in FIG. 4 or on a UI screen transitioning from the screen in FIG. 4. Furthermore, if the workers have terminals, messages including at least information indicating the priority process may be transmitted from the information processing device 101 to the terminals owned by all the workers. These messages may further include information indicating the type of error occurring in the priority process. These messages may further include information indicating the job in which the error occurred.

[0090] Priority process determination processing FIG. 16 shows a flowchart for determining the priority process performed in S1501. In S1601, the CPU 201 receives signals from the position tag 707 and the item tag 709 using the tag reader 705, and obtains the tag ID 1311 included in the received information.

[0091] In S1602, the CPU 201 identifies the process linked to the tag ID 1311 of the position tag 707 acquired in S1601. The CPU 201 acquires the job ID 1312 linked to the tag ID 1311 of the item tag 709 acquired in S1601 from the job table 1204, thereby identifying the job of that process. Because the setting position of the position tag 707, i.e., the process, is known, the process of the job linked to the detected item tag can be identified from the tab ID of the position tag 707 based on the tag ID of the item tag received together with the tag ID of the position tag 707. Note that in the following description, work in progress in the middle of processing a job may also be referred to as a job.

[0092] In step S1603, the CPU 201 acquires the error occurrence status for each process from the error process management unit 1401. The occurrence of an error in each process can be detected, for example, from error information from the device (post-processing device) for each process, or from error information generated from monitored images or audio of the device for each process. Alternatively, the occurrence of an error can be detected from error information generated when the job retention time for each process exceeds the estimated required time for that process, or from error information notified when an operator operates an error notification switch provided for each process. The process in which an error occurred can be identified by including identification information for identifying each process in the error information. An error process may include a process in which processing was stopped due to an occurrence of a circumstance that necessitated stopping the processing of that process. For example, if a post-processing process that uses consumables is stopped due to a shortage of consumables, this condition may be notified to the information processing device 101 as error information.

[0093] In S1604, the CPU 201 checks whether there is an error process. If there is an error process, the process proceeds to S1605. If not, there is no error currently occurring, so there is no need to determine a priority process, and the process ends.

[0094] In S1605, the CPU 201 determines whether multiple error processes have occurred. If errors have occurred in multiple processes, the process proceeds to S1607, and if not, that is, if an error has occurred in only one process, the process proceeds to S1606.

[0095] In step S1606, since there is only one error process, the CPU 201 determines the error process as a priority process and stores, for example, identification information indicating the priority process. For the error process of the job determined as the priority process, priority is given to error handling by a worker or the like.

[0096] In S1607, the CPU 201 uses the job identification unit 1411 to identify an error-related job for each of the multiple error processes, and uses the process identification unit 1412 to acquire downstream processes from the job. S1607 is performed by the error process management unit 1401 in software. For jobs currently being executed, whether the printing process is identified by the image forming apparatus 102 or the post-processing process is identified by the wireless tag of the work-in-progress, is a process waiting to be executed or currently being executed. Therefore, in S1607, for example, by focusing on each job currently being executed, a job whose workflow includes an error process and whose currently being executed or awaiting execution process is the error process or an upstream process may be identified as an error-related job. Then, for each identified error-related job, downstream processes from the error process may be identified.

[0097] In S1608, the CPU 201 determines a priority process from among the multiple error processes.

[0098] ●Determining priority processes A flowchart of the priority process determination performed in S1608 is shown in Fig. 17. In the explanation of Fig. 17, although the execution entity on the hardware side is the CPU 201, the software module realized by the CPU 201 will be explained as the execution entity.

[0099] In S1701, the dependent process determination unit 1421 acquires the number of remaining dependent processes for each error-related job. The number of remaining dependent processes is the number of dependent processes downstream of the error process for the error-related job in question. In S1701, the dependent process determination unit 1421 counts the number of remaining dependent processes for each of the multiple error-related jobs, and if there is one error-related job with the largest number of remaining dependent processes (or more than any other), the process branches to S1702. If there are multiple error-related jobs with the largest number of remaining dependent processes, the process transitions to S1703.

[0100] If it is determined in S1702 that the remaining dependent process counts are different, the priority process determination unit 1403 identifies and stores the error process of the job with the largest (or largest) remaining dependent process count as the priority process. In this case, if there are three or more error processes, each error process may be prioritized. For example, the highest priority may be assigned to the process with the largest number of remaining dependent processes. In a dependent process, work-in-progress from a process that is not directly affected by the error process is processed together with work-in-progress from the error process or its downstream process. Therefore, in a dependent process, work-in-progress from a process that is not directly affected by the error process will be held up while waiting for work-in-progress from the error process or its downstream process. Therefore, when an error process occurs, the job with the largest remaining dependent process count may have the largest number of work-in-progress from processes that are not directly affected by the error process. Therefore, the error process included in the job (or its workflow) with the largest remaining dependent process count is determined to be the priority process. If a plurality of error processes occur in one job, the number of remaining dependent processes may be identified for the most upstream error process, and a priority process may be identified based on that number.

[0101] In S1703, the process identification unit 1412 acquires the number of processes downstream of each error-related job. A downstream process refers to the number of processes to be performed from the process of interest until the product is completed, and the number of processes downstream of the error process is specifically called the number of remaining processes. Unlike dependent processes, downstream processes are identified regardless of whether work-in-progress is used by processes that are not affected by the error process. Specific examples will be described later. If the number of remaining processes differs for each job, the process branches to S1704; if the number is the same, the process transitions to S1705. In S1703, if there are multiple error-related jobs with the largest number of remaining processes, the process branches to S1705; otherwise, the process may branch to S1704.

[0102] In S1704, the priority process determination unit 1403 determines the error process of the error-related job having the largest number of remaining processes as a priority process, and stores the identification information of the priority process.

[0103] In step S1705, the priority process determination unit 1403 determines the error process of the job that has the longest post-recovery work time, from the time the error process is recovered until the job is completed, as the priority process. A long work time may mean longer than others or the longest. To compare work times, the post-recovery work time is estimated based on past similar job information. For example, the average processing time for each process is obtained and then multiplied by the number of remaining processes to obtain an estimated work time. Alternatively, the average time for each process type may be added for each downstream process of each error-related job to obtain the post-recovery work time for each job. Furthermore, the amount of movement (or movement time) between processes may be added, but this is not limited to this. For example, the workflow management application may store the time from when a job moves to a certain process until it moves to the next process for each process, and the accumulated value may be divided by the number of processes in that process to use as the average processing time for each process. Because this value includes the time spent moving between processes, there is no need to add the time spent moving between processes. Furthermore, some or all of the factors used in the work time prediction described above may be used.

[0104] Furthermore, in the procedure of Fig. 17, if multiple errors occur in one job, the processing of Fig. 17 may be performed by focusing on the most upstream error step. The processing of Fig. 17 can also be described as follows. That is, in S1701 of Fig. 17, the number of remaining dependent steps for each error step may be identified according to the workflow of each error-related job, and the error step with the largest number of remaining dependent steps may be set as the priority step. Similarly, in S1704 and S1705, the error step with the largest number of remaining steps or the largest estimated processing time may be set as the priority step.

[0105] ●Explanation of specific examples The above flowchart will be explained using an example of a book order in Figure 18. Note that the bookbinding process is one specific example and is not limited to this. This diagram receives book orders and manages actual jobs. The thick black solid line frames on the left side indicate each job, and the black dotted line frames and black solid line frames indicate each process operation included in each job.

[0106] From the perspective of cover job 1801, work is performed in printing process 1811, cutting process 1812, and hardcover process 1813, and then in binding process 1814, it waits for the arrival of the book bodies from cutting process 1821. After the book bodies arrive, work is performed in binding process 1814 and cutting process 1815, and then in the next binding process 1816, it waits for the arrival of the cover from cutting process 1831. After the cover arrives, work is performed in binding process 1816, and in the next binding process 1817, it waits for the arrival of the obi from cutting process 1841, and then work is performed in binding process 1817 until the job is completed. After that, work is performed in processes such as inspection and packaging.

[0107] The downstream process mentioned above refers to the work that occurs after the process of interest. For example, if hardcover 1813 is the process of interest (error process), the downstream processes are bookbinding process 1814, cutting process 1815, bookbinding process 1816, and bookbinding process 1817, and these processes are considered to be the remaining processes. Therefore, the number of remaining processes is 4. Furthermore, when working at each bookbinding process, work in progress from multiple processes is required, and such processes are considered dependent processes and are represented by black solid lines. For example, if hardcover 1813 is the process of interest, the dependent processes are bookbinding process 1814, bookbinding process 1816, and bookbinding process 1817, and these processes are considered to be the remaining dependent processes. In this case, the number of remaining dependent processes is 3. Similarly, from the perspective of the main body (color) job, if printing process 1822 is the process of interest (error process), the number of remaining dependent processes is 4.

[0108] For example, if a problem occurs only in the printing step 1811 of the cover job 1810, processing equivalent to S1606 is performed. If a problem occurs in the printing step 1811 of the cover job 1810 and the printing step 1822 of the body (color) job, comparing the remaining number of dependent steps, the body (color) job has 4 and the cover job has 3. Therefore, processing equivalent to S1702 is performed, which gives priority to the body (color) job with the greatest number of remaining dependent steps. As a result, the printing step 1822 is determined to be the priority step.

[0109] If a problem occurs in the printing process 1811 of the cover job and the cutting process 1821 after temporary fastening of the body (color) job, the number of remaining dependent processes for both will be 3. Therefore, when the number of remaining processes is compared in the process equivalent to S1703, the former is 6 and the latter is 4. As a result, the cover job is given priority in the process equivalent to S1704, and the printing process 1811 is determined as the priority process.

[0110] Furthermore, in step S1503 of FIG. 15, the determined priority process is output in such a manner that it is displayed on the UI of the information processing device 101 or on the worker's terminal.

[0111] <Effects of the First Embodiment> In this embodiment, when an error occurs in a process, the priority process is determined taking into account the number of dependent processes, the number of processes, or the working time. This makes it possible to appropriately indicate the order in which to deal with the error process. As a result, it is possible to deal with the error process while minimizing the impact on other jobs, and it is expected to be effective in preventing unnecessary backlogs.

[0112] [Variation 1-1] In the first embodiment, the priority process was determined in S1608 based on the number of remaining dependent processes. However, if there are sufficient work-in-progress items, the priority process may be determined regardless of the number of remaining dependent processes. Here, the case where there are sufficient work-in-progress items is assumed to be when the quantity of work-in-progress items exceeds a threshold value, but this is not limited to this, and the priority process may also be determined based on the remaining storage capacity or the ratio of blank area in the work-in-progress storage area. Furthermore, the threshold value for the quantity of work-in-progress items may be 0.

[0113] The flow of the modified example showing the above embodiment is shown in Fig. 19. The process shown in Fig. 19 is executed by the CPU 201 of the information processing device 101.

[0114] In S1901, the dependent process management unit 1402 acquires work-in-progress information for a process determined to be a dependent process. Work-in-progress information may include, but is not limited to, the aforementioned quantity, the remaining storage capacity of the work-in-progress storage area, and the ratio of blank space. An example of a work-in-progress storage area is shown in FIG. 20. A work-in-progress storage area 2001 is installed near each process device 2002. It stores job deliverables awaiting processing, i.e., work-in-progress. A tag reader 705 is installed in the work-in-progress storage area 2001, and the detection range of the tag reader 705 defines the work-in-progress storage area 2001. If an item tag 709 is present within the detection range of the tag reader 705, the tag ID 710 is acquired, and the item 711 is acquired. Alternatively, the number of item tags 709 detected together with the position tag 707 may be considered the quantity of work-in-progress.

[0115] In S1902, it is determined whether or not a certain amount of work in progress exists. The criterion for this determination is assumed to be whether or not there is a certain value or more, but this is not the only possible criterion. For example, it is possible to set a standard value for each process or to compare the amount of work in progress of each dependent process. If there is a certain amount, the process proceeds to S1904, and if not, the process proceeds to S1903.

[0116] In S1903, since the amount of work in progress does not exist to a certain number, the process shown in Fig. 17 of the first embodiment is performed. Details have been described above and will be omitted here.

[0117] In S1904, if a certain amount exists, it can be confirmed that the amount of arriving goods and work in progress combined is sufficient to proceed with the work. Therefore, priority is given to error processes of jobs where a sufficient amount of work in progress exists, regardless of the number of remaining dependent processes. If there are multiple applicable processes, the process in S1903 can be performed on those processes to determine the priority process based on the number of remaining dependent processes, etc., or the error process with the largest amount of work in progress can be determined as the priority.

[0118] <Effects of Modification 1-1> In this modified example, we consider the amount of work-in-progress. In the first embodiment, the priority process was determined by focusing on the number of remaining dependent processes and the number of remaining processes. This was intended to prevent delays due to waiting for the arrival of parts necessary to create the deliverable. However, if there is sufficient work-in-progress, the impact of delays due to a parts shortage is minor. In this modified example, by incorporating the perspective of work-in-progress, we can expect to be able to determine priority processes more effectively to reduce delays. We can also expect to be able to prevent pressure on the work-in-progress storage area.

[0119] [Variation 1-2] In the first embodiment and the modified example 1-1, a method for determining a priority process was described. The worker may be determined as in S1502, which was described as being skipped as an option in the first embodiment. The worker may be determined by providing a worker determination unit in the error process management unit 1401 in the process management service 1202 and adding a configuration for determining a worker. A flowchart with the above-mentioned embodiment added is shown in FIG. 21. The process in FIG. 21 is executed by the CPU 201 of the information processing device 101.

[0120] In S2101, the worker determination unit acquires information about the worker currently working. The worker information includes identification information about the worker currently in the work area who is available to work and location information indicating the worker's location. It may also include the destination of a message to be sent to the worker's terminal. For example, when entering or leaving the work area, the worker inputs identification information recorded on an ID card or the like into the information processing device 101 using a card reader. This identifies the worker in the work area. Furthermore, if the worker carries a tag reader 705, the tag reader and the worker can be associated in advance, and the location of the tag reader can be identified as the worker's location. This association may be entered by the worker when using the tag reader 705. If a tag reader is fixedly installed at the work area of each process, for example, each worker may also carry a worker tag that identifies the worker, and the worker's location can be estimated from the ID of the worker tag detected by each tag reader.

[0121] In S2102, it is determined whether there are multiple actual workers. If there is one worker, the process proceeds to S2103, and if there are multiple workers, the process proceeds to S2104.

[0122] In S2103, since there is only one worker, this worker is assigned to handle the priority process.

[0123] In S2104, the worker determination unit acquires the position information of each worker.

[0124] In S2105, the travel distance for each worker when they travel to the priority process determined in S1501 is calculated or acquired. While the travel distance is assumed to be distance, it is not limited to this and may be calculated from the perspective of time. In the latter case, for example, the end time of the current work being performed may be taken into consideration in addition to the travel time. The travel distance is calculated using one or more of these factors. Furthermore, the travel distance may not be the straight-line distance between the worker's position and the location of the priority process, but may be the travel distance within the work site. For example, by determining in advance the routes that can be traveled within the work site, the shortest distance along those routes from each worker to the location of the priority process may be determined as the travel distance for each worker.

[0125] In S2106, the worker with the smallest movement amount is determined as the worker.

[0126] Once the worker is determined as described above, in S1503 of FIG. 15, the CPU 201 may output a message associating the determined worker with the priority process. In S1503, for example, the message may be displayed on the UI screen shown in FIG. 4 or a UI screen transitioning from the screen of FIG. 4. Furthermore, if the worker has a terminal, a message including at least information indicating the priority process may be sent from the information processing device 101 to the terminal of the determined worker. These messages may further include information indicating the type of error occurring in the priority process. These messages may further include information indicating the job in which the error occurred. The process may be displayed by displaying the location where the priority process is performed, its name, etc. <Effects of Modifications 1-2> In this modification, a configuration has been added in which a worker is selected after the priority process has been determined. This allows the selection of a worker suited to the priority process, which is expected to result in a quick response, i.e., quick resolution of errors. This also prevents unnecessary backlogs of work-in-progress.

[0127] [Variation 1-3] In Modification 1-2, a configuration for determining a worker corresponding to a priority process is added. However, when focusing on the amount of movement, it is conceivable that a worker with no or little experience in error handling work may be assigned. Therefore, when determining the worker in S1502, a configuration may be adopted in which the worker is determined based on past work history. The flow of this modification illustrating the above configuration is shown in FIG. 22. FIG. 22 is executed by the CPU 201 of the information processing device 101. FIG. 22 also shows details of S1502, which replaces FIG. 21.

[0128] In S2201, the worker determination unit acquires the past work history of each worker. It is assumed that the work history is acquired from information detected by tag reader 705 provided in each process, but this is not limited to this. The past work history of each worker is accumulated when the worker handles an error. This may be input by a manager or the worker himself. For example, the work history may include the identification information of the worker and the identification information of the corresponding process. It may also include the type of error that was handled.

[0129] In S2202, the priority process and the movement amount of the worker are calculated. This may be the same method as the movement amount calculation method shown in S2104 to S2106, but is not limited to this.

[0130] In S2203, the worker determination unit determines a worker based on the amount of movement and the work history. First, using the amount of movement as a criterion, the worker with the smallest amount of movement is provisionally assigned as the worker for the priority process in the same manner as in Figure 21. If the work history of the provisionally determined worker does not contain any records of work for the priority process, the worker with the next smallest amount of movement is assigned to the priority process. This is repeated until a worker with experience working for the priority process is found. If a worker with experience working for the priority process is found, that worker is determined to be the worker for the priority process. If a worker with experience working for the priority process is not found, the first provisionally determined worker may be determined to be the person in charge. Alternatively, it is also possible to not select a worker who has not performed the work a certain number of times as a worker.

[0131] <Effects of Modifications 1-3> In this modification, we assume a configuration in which work history information is taken into consideration when selecting workers, and workers with no work experience are excluded. Unlike modification 1-2, it is possible to assign workers who have experience working in the process. This is expected to have the effect of reducing the impact of worker delays on priority processes.

[0132] [Variation 1-4] In the above configuration, a worker carries a tag reader and moves around, detecting the position tag and the item tag to identify the process of the job to which the item tag is attached. Alternatively, tag readers may be fixedly placed at positions corresponding to each process, and the process of the job to which the item tag is attached may be identified based on the tag reader that detected the item tag. To do this, the process is identified by referring to the process location table 1205 shown in FIGS. 12 and 13(B). For example, in S1601 of FIG. 16, a pair of the tag reader for each process and the tag ID of the item tag detected by the tag reader is acquired. The acquired information includes the location of the item tag. Therefore, the process location table 1205 is referenced to identify the process within a predetermined range from the coordinates of the detected item tag. This allows the process to which the item tag belongs to to be identified.

[0133] [Other Examples] The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program.The present invention can also be realized by a circuit (e.g., ASIC) that realizes one or more functions.

[0134] Summary of embodiments The above embodiments can be summarized as follows: (Item 1) An information processing device for managing a workflow, a storage means for storing workflow information indicating steps included in the workflow and their order; a first identifying means for identifying an error-related job and an error process in which an error has occurred when a job is being executed according to a workflow; a second specifying means for specifying, for each error-related job, the number of dependent processes that are executed using multiple work-in-progress among processes downstream of each error process when multiple errors are specified by the first specifying means; a determining means for determining, as a priority process, an error process having a larger number of dependent processes identified by the second identifying means than the other processes; An information processing device comprising: (Item 2) Item 1. The information processing device according to item 1, When there are a plurality of error processes having a larger number of dependent processes than the other processes, the number of downstream processes downstream of each error process is identified. The determining means determines, as a priority process, an error process having a larger number of downstream processes identified by the third identifying means than the other processes. 1. An information processing device comprising: (Item 3) Item 2. The information processing device according to item 2, When there are a plurality of error processes having a greater number of downstream processes than the others, the method further comprises an estimation means for estimating, for each error-related job, the post-recovery work time from when the error in each error process is recovered until the job is completed, The determining means determines an error process of a job whose working time estimated by the estimating means is longer than the other processes as a priority process. 1. An information processing device comprising: (Item 4) The information processing device according to any one of items 1 to 3, The method further includes an output means for outputting the determined priority process. 1. An information processing device comprising: (Item 5) The information processing device according to any one of items 1 to 4, a fourth identification means for identifying the location of each worker; and a worker determination means for determining a worker to handle an error in the priority process based on the determined work location of the priority process and the location of the worker. 1. An information processing device comprising: (Item 6) Item 5. The information processing device according to item 5, further comprising a history means for accumulating the work history of each worker; The worker determination means excludes workers who have no experience in working on the error in the priority process based on the work history from the workers who will handle the error in the priority process. 1. An information processing device comprising: (Item 7) Item 5 or 6, the information processing device according to item 5 or 6, The system further includes an output unit for outputting the determined priority process and the worker. 1. An information processing device comprising: (Item 8) Item 4 or 7, the information processing device according to item 4 or 7, The output means includes a user interface for displaying the contents of the output. 1. An information processing device comprising: (Item 9) Item 4 or 7, the information processing device according to item 4 or 7, The output means includes a means for notifying the contents of the output to a terminal of a worker. 1. An information processing device comprising: (Item 10) Item 10. The information processing device according to any one of items 1 to 9, The information processing device is connected by communication with an image forming device and a tag reader that detects an article tag, which is a wireless tag attached to an in-process item for each job; The first specifying unit specifies the error-related job and the error process for the image forming process based on an error notification from the image forming apparatus executing a job, and for the post-processing process based on a process being processed or waiting to be processed and error information for the process, which are specified from a signal of the item tag associated with each job and received from the tag reader. 1. An information processing device comprising: (Item 11) Item 11. The information processing device according to item 10, The tag reader also detects signals from position tags, which are wireless tags provided at each location in the post-processing process; The first specifying means specifies the process in progress or waiting for processing, for the post-processing process, from the signal of the item tag and the signal of the position tag received from the tag reader carried by the worker. 1. An information processing device comprising: (Item 12) Item 11. The information processing device according to item 10, the tag reader is provided at each location of the post-processing step, The first identifying means identifies the process in progress or waiting for processing based on the tag reader that receives the signal from the item tag, for the post-processing process. 1. An information processing device comprising: (Item 13) A workflow management method using an information processing device having a storage means, a first specifying means, a second specifying means, a third determining means, and a determining means, the storage means stores workflow information indicating steps included in the workflow and their order; the first identifying means identifies an error-related job and an error process in which an error occurred while a job is being executed according to a workflow, When a plurality of errors are identified by the first identification means, the second identification means identifies, for each error-related job, the number of dependent processes that are executed using a plurality of work-in-progress among processes downstream of each error process; The determining means determines, as a priority process, an error process having a larger number of dependent processes identified by the second identifying means than the other processes. A workflow management method comprising: (Item 14) A program for causing a computer to execute a workflow management method, the workflow management method comprising: Save workflow information that indicates the steps included in the workflow and their order; Identifying an error-related job and an error process in which an error occurred while a job is being executed according to a workflow, If multiple errors are identified, for each error process, the number of dependent processes downstream of the error process that are executed using multiple work-in-progress items is identified for each error-related job; determining an error process having a greater number of identified dependent processes as a priority process. A program characterized by:

[0135] The present invention is not limited to the above-described embodiments, and various changes and modifications can be made without departing from the spirit and scope of the invention. Therefore, the following claims are appended to apprise the public of the scope of the invention. [Explanation of symbols]

[0136] 101 information processing device, 102 image forming device, 103 post-processing device, 700 position control system, 1200 process control system

Claims

1. An information processing device for managing a workflow, a storage means for storing workflow information indicating steps included in the workflow and their order; a first identifying means for identifying an error-related job in which an error has occurred and an error process in which an error has occurred when a job is being executed according to a workflow; a second specifying means for specifying, for each error-related job, the number of dependent processes that are executed using multiple work-in-progress among processes downstream of each error process when multiple errors are specified by the first specifying means; a determining means for determining, as a priority process, an error process having a larger number of dependent processes identified by the second identifying means than the other processes; An information processing device comprising:

2. 2. The information processing device according to claim 1, When there are a plurality of error processes having a larger number of dependent processes than the other processes, the number of downstream processes downstream of each error process is identified. The determining means determines, as a priority process, an error process having a larger number of downstream processes identified by the third identifying means than the other processes.

1. An information processing device comprising:

3. 3. The information processing device according to claim 2, When there are a plurality of error processes having a greater number of downstream processes than the others, the method further comprises an estimation means for estimating, for each error-related job, the post-recovery work time from when the error in each error process is recovered until the job is completed, The determining means determines an error process of a job whose working time estimated by the estimating means is longer than the other processes as a priority process.

1. An information processing device comprising:

4. 2. The information processing device according to claim 1, The method further includes an output means for outputting the determined priority process.

1. An information processing device comprising:

5. 2. The information processing device according to claim 1, a fourth identification means for identifying the location of each worker; and a worker determination means for determining a worker to handle an error in the priority process based on the determined work location of the priority process and the location of the worker.

1. An information processing device comprising:

6. 6. The information processing device according to claim 5, further comprising a history means for accumulating the work history of each worker; The worker determination means excludes workers who have no experience in working on the error in the priority process based on the work history from the workers who will handle the error in the priority process.

1. An information processing device comprising:

7. 6. The information processing device according to claim 5, The system further includes an output unit for outputting the determined priority process and the worker.

1. An information processing device comprising:

8. 8. The information processing device according to claim 4, The output means includes a user interface for displaying the contents of the output.

1. An information processing device comprising:

9. 8. The information processing device according to claim 4, The output means includes a means for notifying the contents of the output to a terminal of a worker.

1. An information processing device comprising:

10. 2. The information processing device according to claim 1, The information processing device is connected by communication with an image forming device and a tag reader that detects an article tag, which is a wireless tag attached to an in-process item for each job; The first specifying unit specifies the error-related job and the error process for the image forming process based on an error notification from the image forming apparatus executing the job, and for the post-processing process based on the process being processed or waiting to be processed and error information for the process specified from the signal of the item tag associated with each job received from the tag reader.

1. An information processing device comprising:

11. The information processing device according to claim 10, The tag reader also detects signals from position tags, which are wireless tags provided at each location in the post-processing process; The first specifying means specifies the process in progress or waiting for processing, for the post-processing process, from the signal of the item tag and the signal of the position tag received from the tag reader carried by the worker.

1. An information processing device comprising:

12. The information processing device according to claim 10, the tag reader is provided at each location of the post-processing step, The first specifying means specifies the process in progress or waiting for processing based on the tag reader that receives the signal from the item tag, for the post-processing process.

1. An information processing device comprising:

13. A workflow management method using an information processing device having a storage unit, a first specifying unit, a second specifying unit, a third determining unit, and a determining unit, the storage means stores workflow information indicating steps included in the workflow and their order; the first identifying means identifies an error-related job in which an error occurred and an error process in which an error occurred when a job is being executed in accordance with a workflow, When a plurality of errors are identified by the first identification means, the second identification means identifies, for each error-related job, the number of dependent processes that are executed using a plurality of work-in-progress among processes downstream of each error process; The determining means determines an error process having a large number of dependent processes identified by the second identifying means as a priority process. A workflow management method comprising:

14. A program for causing a computer to execute a workflow management method, the workflow management method comprising: Save workflow information that indicates the steps included in the workflow and their order; Identifying an error-related job and an error process in which an error occurred while a job is being executed according to a workflow, If multiple errors are identified, for each error process, the number of dependent processes downstream of the error process that are executed using multiple work-in-progress items is identified for each error-related job; determining an error process having a large number of identified dependent processes as a priority process. A program characterized by:

Images