Management system, management method, and program

Abstract

To solve the problem in which counting jobs that are waiting to be processed without taking account of abandoned jobs results in a deviation from an actual state.SOLUTION: Provided is a management system for managing steps of managed objects to which wireless tags are attached based on identification information of the wireless tags and detection positions of the wireless tags. The system is configured to: store association information in which the managed objects are associated with the identification information of the wireless tags; set, for each step, an abandoned period during which each managed object is abandoned until the step is executed; identify the number of managed objects for each step corresponding to the detection positions based on the identification information of the wireless tags and the detection positions of the wireless tags; identify, for each step, the number of managed objects excluding the number of managed objects that are being abandoned for the step from the identified number of managed objects; and output the identified number of managed objects for each step.SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] The present invention relates to a management system, a management method, and a program for managing the number of management targets, such as waiting jobs in processes such as commercial printing.

Background Art

[0002] Regarding the process from "order reception" to "printing process" in commercial printing, it is managed and visualized by printing workflow software. Also, regarding online post-processing machines connected to the network, the status is managed and visualized by collecting information via the network. On the other hand, in the manufacturing process in a factory, a technique has been proposed for managing whether work is being performed in a reverse order of the work process or whether more work time than necessary is being spent in the process by using a technique capable of detecting the position information of parts (Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] According to the technique disclosed in Patent Document 1, even if the devices for performing the processing in each process are offline, it is possible to visualize the status of work performed in each process based on the position information of the parts moving through the manufacturing process. However, in the printing process of commercial printing, depending on the attributes of the jobs to be printed and the types of processes, there may be processes in which sequential work is carried out, or there may be a case where it is necessary to elapse a certain period of time (leave it unattended) before starting the processing of a certain process. In view of such a situation, it has been difficult to visualize the status of jobs to be processed in each process, including offline work processes.

[0005] The present invention has been made in view of the above-described conventional examples, and an object thereof is to realize management that takes into account the idle time for each process to be managed, such as a job.

Means for Solving the Problems

[0006] To achieve the above object, the present invention has the following configuration. That is, according to one aspect of the present invention, there is provided a management system for managing a process to be managed to which a wireless tag is attached based on identification information of the wireless tag and a detection position of the wireless tag, storage means for storing association information associating the management target with the identification information of the wireless tag; setting means for setting, for each process, an idle period during which each management target is left until the execution of the process; first specifying means for specifying the number of management targets for each process corresponding to the detection position based on the identification information of the wireless tag and the detection position of the wireless tag; second specifying means for specifying, for each process, the number of management targets obtained by excluding the number of management targets being left from the number of management targets specified by the first specifying means; output means for outputting, for each process, the number of management targets specified by the second specifying means A management system characterized by having the above is provided.

Effects of the Invention

[0007] According to the present invention, it becomes possible to realize management that takes into account the idle time for each process to be managed.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6A

Figure 6B

Figure 7

Figure 8

Figure 9

Figure 10A

Figure 10B

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Modes for Carrying Out the Invention

[0009] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims. Although a plurality of features are described in the embodiments, not all of these plurality of features are essential to the invention, and the plurality of features may be arbitrarily combined. Further, in the accompanying drawings, the same or similar configurations are given the same reference numerals, and redundant descriptions are omitted.

[0010] <First Embodiment> FIG. 1 is a diagram showing an example of a system configuration showing an embodiment of the present invention. This system is a workflow management system, and a workflow is, in this example, a flow of processing composed of continuous steps for producing a printed product (also called a commercial material). An object to be processed (or executed) according to a workflow is called a job, and particularly for a printing workflow, it is called a printing job. The workflow of the present embodiment includes a printing process executed by a normal printing apparatus and a post-processing process sequentially executed on the output of the printing process. The post-processing process includes a post-processing process by a post-processing apparatus such as lamination, bookbinding, and cutting, and a post-processing process by an operator such as inspection, packing, and shipping. Of course, one product does not necessarily require all of these processes and may be only a part of them. In the workflow management system of FIG. 1, the definition and management of the workflow can be performed. In the present embodiment, the explanation mainly focuses on the management at the time of execution, and the setting of the workflow will be briefly explained as necessary. The setting of the workflow includes, for example, steps and their order, and setting values (parameters) in each step. Further, in the present embodiment, the setting values in each step include the presence or absence of leaving unattended and the leaving unattended time. Hereinafter, in the present embodiment, among the functions of the workflow management system, the function of managing the progress of a job when executing the job according to a defined printing workflow will be mainly described.

[0011] ●System Configuration The management system of this embodiment includes an information processing device 101, an image forming device 102, a post-processing device 103, and a location management system 104. The information processing device 101, the image forming device 102, and the location management system 104 are connected to each other via a network 100. The location management system 104 will be described with reference to FIG. 4 which will be described later. The image forming device 102 analyzes print data transmitted from the information processing device 101 or the like, converts it into dot images page by page, and prints it. For this reason, the image forming device 102 may also be called a printing device. The printed matter output from the image forming device 102 is passed to the post-processing device 103 by an operator's hand carry (manual work), or is passed to the post-processing device 103 via a belt conveyor (not shown). The post-processing device 103 is configured offline to operate independently without communicating with the image forming device 102 or the information processing device 101. The post-processing device 103 performs processing such as cutting, laminating, folding, or binding on the passed printed matter. It is also possible to bind and then cut using a plurality of post-processing devices. Note that in FIG. 1, one information processing device 101, one image forming device 102, and one post-processing device 103 are each illustrated, but any number of each device may be arranged. For example, printed matter output by a plurality of image forming devices may be processed by a plurality of post-processing devices 103. Note that the post-processing device 103 may be an online device connected to the network 100 as long as it is not a so-called in-line device into which the printed sheets discharged from the image forming device 102 are input via a conveyance path.

[0012] The print job (simply referred to as "job") to be managed by this management system is usually input to and started by the image forming apparatus 102, and a product (finished product) is manufactured through the necessary post - processing steps from the image forming step, and further ends in processes such as packaging and shipping of the product. From the start to the end of the job, it becomes the object of management by the management system in each step, and the jobs in each step are grasped. More specifically, for example, an article tag composed of an RFID tag (wireless tag) attached to the in - process material corresponding to the job is detected by a tag reader to identify its position. The identification information (ID) of the article tag is associated with each job. The tag reader of the position management system 104 is carried and moved by the operator, and detects a position tag, which is a wireless tag arranged in advance at a position corresponding to each step, and an article tag attached to the in - process material to identify the position of the article tag. Here, the in - process material refers to the commercial material whose workflow has not been completed in this example. When the position of the article tag is identified, if the position is included within the area defined for each step, the article tag or the in - process material to which it is attached is determined to be in that step. The area defined for each step includes a processing area where the processing of that step is executed and a processing - waiting area where jobs waiting for execution and jobs left unattended are placed.

[0013] The association between the job and the article tag is made particularly before the article tag is attached to the job when the job is executed. For example, a printing device having an RFID reader may print the tag ID of the RFID tag on a sheet with an attached RFID tag placed on the paper feed unit, along with a separately input job ID (or further, a commercial material ID and a commercial material name), and use it as the article ID to be attached to the job. At this time, the associated tag ID and job ID may be registered in the process management table shown in FIG. 8(A) by, for example, the print workflow application described later.

[0014] In the above description, the job has been described as the object to be managed. However, the management unit is not limited to jobs. Since what is directly managed is the position of each item tag, an object (or management unit) to which an item tag is attached may be used as the management target. The position management system 104 will be described with reference to FIG. 4.

[0015] ● Hardware Configuration of Information Processing Apparatus FIG. 2 is a diagram showing an example of the hardware configuration of the information processing apparatus 101. The central processing unit (CPU) 201 reads a control program stored in the read-only memory (ROM) 202 or the hard disk drive (HDD) 204 and executes various control processes. The random access memory (RAM) 203 is used as a temporary storage area such as the main memory and work area of the CPU 201. The HDD 204 stores image data and various programs. The various programs stored include programs for realizing the procedures of the flowcharts in FIGS. 5, 10A, 10B, 12, 15, and 17. Note that a configuration including another storage device such as a solid state drive (SSD) instead of or in combination with the HDD 204 may also be used.

[0016] The keyboard 205 is an input device that is an instruction input unit, and instructs control commands and text input to an application described later. The pointing device 206 is an input device that is an instruction input unit together with the keyboard 205, and instructs control command instructions to an application described later. The display 207 is an output device that is a display unit, and displays commands input from the keyboard 205 and the pointing device 206 and the state of an application described later. Further, the display 207 can display the state of a job that is the management target of the management system, for example, the number of management targets for each process. The network I / F 208 connects the information processing apparatus 101 to a network (LAN, intranet, Internet, etc.). The information processing apparatus 101 transmits and receives various information to and from other devices on the network using the network I / F 208.

[0017] In addition to the configuration shown in FIG. 2, the image forming apparatus 102 includes an image forming unit such as an electrophotographic method or an inkjet method for forming an image on a cut sheet or a roll sheet supplied from a paper feeding unit, and a conveyance mechanism for conveying the sheet from the paper feeding unit to the paper discharging unit. By this mechanism, the image forming apparatus 102 can execute a print job to form an image on the sheet, and can discharge and stack the sheet on which the image is formed to the paper discharging unit, for example, in units of print jobs. The discharged sheet bundle being processed is transferred to a post-processing step, for example, in units of jobs. An article tag is attached to this sheet bundle, and its position is managed. Therefore, in the image forming step, the print job itself executed by the image forming apparatus 102 is managed, but in the post-processing step, the job is managed via the article tag. The article tag may be provided with identification information such as text or an image that can be read by an operator and that can identify the management target, that is, the job. Note that the image forming apparatus 102 does not necessarily have to have a pointing device 206 or an HDD 204.

[0018] In addition to the configuration shown in FIG. 2, the post-processing apparatus 103 also has a mechanism according to the type of post-processing for each apparatus. The post-processing apparatus 103 does not necessarily have to have a pointing device 206 or an HDD 204, nor does it necessarily have to have a network I / F 208. Printed materials by the image forming apparatus 102 and output materials of other post-processing apparatuses (that is, semi-finished products being processed) are placed on the paper feeding unit of the post-processing apparatus 103, for example, in units of jobs, and post-processing is performed. The output of the post-processing apparatus 103 becomes a product to be shipped or a semi-finished product to be further processed by the next-stage post-processing. Note that the post-processing step includes steps performed manually without using the post-processing apparatus 103. The management system of the present embodiment manages management targets such as jobs including such manual steps.

[0019] ●Software Configuration of Information Processing Apparatus FIG. 3 is a diagram showing an example of the software configuration of the information processing apparatus 101. The printing workflow application 301 is a program module that is installed and operates on the HDD 204 of the information processing device 101, is loaded into the RAM 203 during execution, and is executed by the CPU 201. The printing workflow application 301 includes a user interface (UI) unit 302, a print job management unit 303, a print job control unit 304, a printing processing unit 305, a device management unit 306, and a process management unit 307.

[0020] The UI unit 302 constructs a graphical user interface (GUI) and accepts various input operations from the user, and issues an execution instruction for corresponding processing. The print job management unit 303 accesses the print job information data 308 described later and executes a reference to various information of the print job that the printing workflow application 301 transmits to the image forming apparatus 102. The print job control unit 304 controls the execution of various functions (such as transmission, editing, and deletion of print jobs) for the print jobs in the printing workflow application 301. In response to a print job transmission instruction received from the print job control unit 304, the printing processing unit 305 transmits the content data and job ticket data of the print job to the image forming apparatus 102.

[0021] The device management unit 306 manages various information (including identification names, addresses, etc.) of the image forming apparatus 102 that is the target for transmitting print jobs from the printing workflow application 301. The process management unit 307 controls various processes for visualizing the status of jobs processed in each process (including offline processes) in the printing factory.

[0022] The print job information data 308 is a database that manages information related to the print jobs described later (print job information tables, commercial material information tables, workflow information tables). Note that each table will be described with reference to FIG. 7 later. The project management information data 309 is a database that manages information related to project management (project management table, project area table) to be described later. Each table will be described with reference to FIG. 8 to be described later. The map data 310 is a database that stores map information of the printing site managed by the project management function of the printing workflow application 301. The map information shall be registered in advance by the administrator of the printing site from the UI (not shown) of the printing workflow application 301. The map information includes information visually showing the layout of areas of each process in the printing factory, but the shown layout does not have to be exact.

[0023] The printing workflow application 301 is assumed to be installed and operate on the HDD 204 of the information processing device 101, but it may be configured on the cloud and provided as a cloud service by accessing it from the web browser of the information processing device 101. Also, the print job information data 308, the project management information data 309, and the map data 310 may be stored not only in the HDD 204 of the information processing device 101 but also in other information processing devices connected by a network. Other information processing devices include a database server (including those on the cloud).

[0024] ● Location Management System FIG. 4 is a diagram showing an example of the configuration of the location management system 104 in the present embodiment. The location management system 104 is a system that manages item data to be managed in a database. The location management system 104 includes location tags 404 installed at different locations, item tags 406a, 406b attached to items, at least one tag reader 403, and a management server 401. The tag reader 403 and the management server 401 are connected to the 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.

[0025] The location tag 404 is a wireless device (wireless tag) installed at each location where a reader may store an article in the location management system 104, and has unique tag identification information (hereinafter referred to as tag ID) 405 embedded therein. The installation location of the location tag 404 is predefined within the location management system 104, but may be changeable at each location.

[0026] The article tags 406a and 406b are wireless devices (wireless tags) attached to each of the articles managed in the location management system 104, and store tag identification information (hereinafter referred to as tag ID) 407a and 407b unique to each tag in the memory embedded in the tag. In FIG. 4, as an example of associating a printed job with an article tag, an example of attaching the article tag 406a to a transit case 408a that stores a job when moving between work processes and an example of attaching the article tag 406b to a work instruction sheet 408b for giving a work instruction are shown, but the present invention is not limited thereto. Here, when the article tags are attached to articles such as the transit case 408a and the work instruction sheet 408b and the articles are transported by a reader or automatically moved, the article tags 406a and 406b also move together with the articles.

[0027] In the following description, when it is not necessary to distinguish between the article tags 406a and 406b from each other, the alphabet at the end of the reference numeral is omitted, and these are collectively referred to as the article tag 406. The same applies to the tag ID 407 (407a, 407b), the article 408 (408a, 408b), and other elements hereinafter.

[0028] In this embodiment, each of the tags such as the position tag 404 and the article tag 406 is assumed to be a passive RFID tag (passive tag). A passive tag is composed of a small IC (Integrated Circuit) chip with a built-in memory and an antenna, and stores identification information for identifying the tag and other information in the memory. In this specification, the identification information is simply referred to as an ID, and the identification information for identifying a tag is also referred to as a tag ID. Note that the tag ID may be regarded as information for identifying the object to which the tag is attached. The IC chip of the passive tag operates using the energy of the electromagnetic wave radiated from the 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.

[0029] Note that in other embodiments, each tag may be an active RFID tag. When actively (e.g., periodically) transmitting information to the surroundings using the power from the battery built in each tag, the tag may be called a beacon tag. In still another embodiment, each tag may be a wireless device that responds to a signal from a reader and returns information in, 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.

[0030] The tag reader 403 is a reading device capable of reading information stored in a wireless device such as an RFID tag. The tag reader 403 can detect the article 408 by, for example, reading the tag ID 407 from the article tag 406 attached to the article 408. Also, the tag reader 403 can detect the article tag 406 and the position tag 404 while moving within the location 409 by being carried by the operator 402. The reader 403 executes reading periodically or in response to some trigger such as a user operation, and transmits the tag reading result to the management server 401. The tag reader 403 may be directly communicable with the management server 401, or may be indirectly communicable with the management server 401 via some relay device.

[0031] Further, the tag reader 403 includes an acceleration / gyro sensor, a geomagnetic sensor, etc. The acceleration / gyro sensor measures the acceleration and angular acceleration applied to the tag reader 403 in the device coordinate system unique to the tag reader 403 and outputs acceleration data and angular acceleration data. The geomagnetic sensor measures the orientation of the tag reader 403 in real space and outputs orientation data.

[0032] Based on the data from the acceleration / gyro sensor and the geomagnetic sensor, the tag reader 403 can measure the relative movement amount of the tag reader 403 by accumulating the acceleration while converting the direction of the acceleration of the tag reader 403 into the direction in the coordinate system of real space. The measurement of this movement amount may be performed according to any known self-position estimation method. This relative movement amount may be a two-dimensional vector in a plane parallel to the ground plane (floor surface), or may be a three-dimensional vector including a component in the height direction. The reference position for measuring the relative movement amount may be, for example, the position of the tag reader 403 at the time when the tag reader 403 is activated, and that position may be a predetermined position. Note that the tag reader 403 may receive the movement amount of the tag reader 403 measured by an external device from that external device. In this way, the tag reader 403 can identify its own movement amount. The management server 401 is an information processing device that manages the position information and other information of a plurality of articles 408 in a database. The management server 401 may be implemented as an application server, a database server, or a cloud server, for example, using a high-performance general-purpose computer. The management server 401 receives the tag reading result from the tag reader 403 and updates the database based on the received tag reading result. The position information data managed by the management server 401 will be described in detail with reference to FIG. 9 described later.

[0033] FIG. 4 shows a single management server 401. However, the functions of the management server 401, which will be described in detail later, may be provided by a single device, or may be provided by a plurality of physically separate devices cooperating with each other. Further, in the present embodiment, an example in which the management server 401 holds a database will be described. However, a device separate from the management server 401 may hold part or all of the database. For example, some data may be held by the tag reader 403.

[0034] ● Visualization processing of steps for each job FIG. 5 is a flowchart showing a process of visualizing the status of jobs in each process in consideration of the job waiting time (or waiting period) by the print workflow application 301. Each processing step will be described. Note that the waiting in the present embodiment means that a designated job waits for the start of a designated process for a designated time (referred to as the waiting time or waiting period) in the designated process, and does not mean abandonment of the job. In each process, since the execution entity (person or post-processing device) of the process is working, a job that has completed the previous process may be placed in a queue and wait until the start of the next process. To distinguish this from the waiting of a job in such a queue, the waiting outside the queue for a specified period is called waiting. Also, waiting including waiting and standing by is called waiting for processing. A job that is left waiting for a certain process is placed in the queue for that process and processed after the waiting period has elapsed. The purpose of waiting is, for example, electrostatic discharge, drying after processing, or placing work in progress that has been processed during the idle time of the device. The process to be left waiting and the waiting period may be specified by the information processing device 101 when generating the job. Further, the job included in the job list described later may be edited, and the process to be left waiting and the waiting time may be set by the editing.

[0035] For example, an operator selects a job, selects a process to be left idle from among the processes included in the selected job, and sets an idle period for the selected process to be left idle. The idle period may be set, for example, by the length of time. The start of the idle period may be the time of completion of the process immediately preceding the process for which idling is set. However, when it is difficult to specify the time of completion of the process, the time when the in-process item of the job to be left idle is detected in the storage area (processing waiting area) for the in-process items prepared for the process for which idling is set may be used as the start time of the idle period. In the following description, the in-process item of a printing job (also simply referred to as a job) may be referred to as an in-process job.

[0036] The process of FIG. 5 is carried out by the CPU 201 of the information processing apparatus 101 executing a program stored in a memory such as the RAM 203. Also, the process of FIG. 5 may be started in response to an execution instruction of the print workflow application 301. Although the execution entity on the hardware for this process is the CPU 201, in terms of software configuration, the software module shown in FIG. 3 realized by the CPU 201 executing a program is the main body. Therefore, in the following description, the software module will be described as the main body.

[0037] In S501, the UI unit 302 determines whether there is a display request for the process management view. If there is a display request for the process management view, the process proceeds to S502. If there is no display request for the process management view, the process returns to S501 and the process is repeated. Also, when proceeding to S502, before S502, the counters for the number of jobs in processing, waiting for processing, and being left idle for each process are initialized to 0. Note that the process of FIG. 5 may be started triggered by a display request for a process management view that visualizes the job status during the execution of the print workflow application 301. In that case, S501 becomes unnecessary.

[0038] ● UI Screen of Print Workflow Application Here, FIGS. 6A and 6B show an example of the UI screen 601 of the printing workflow application 301. When the execution of the printing workflow application 301 is instructed by a printing operator (worker) via the keyboard 205 or the pointing device 206 in the information processing apparatus 101, the CPU 201 loads and executes the program in the RAM 203. Thereby, the printing workflow application 301 is launched. When the printing workflow application 301 is launched, the UI unit 302 displays a print job management screen 602 as shown in FIG. 6A on the display 207. Here, the printing workflow application 301 may be provided as a cloud service. In that case, by accessing the cloud service from the web browser on the information processing apparatus 101, a print job management view screen 602 may be displayed on the web browser.

[0039] FIG. 6A shows a display example in which a print job management view screen 602 is displayed on the main screen 601 of the printing workflow application. The print job management view screen 602 is displayed according to the selection of a tab for displaying the print job management view screen 602, and includes a tab for displaying a process management view screen 603 in the screen. Further, the print job management view screen 602 includes a function menu 604, a print job list 607, and a device list 608. In the function menu 604, a print button 605 and a delete button 606 are arranged. The print button 605 is a button for giving an instruction to print a print job (instruction for production printing). Production printing is a term for proof printing or configuration printing for proofreading, and is printing of a printed matter that becomes a product, which is carried out after proofreading. The delete button 606 is a button for giving an instruction to delete a print job. Note that an edit button or the like for giving an instruction to edit a print job may be provided in the function menu 604.

[0040] The print job list 607 shows a list in which a list of print jobs to be managed by the print workflow application 301 is displayed. The UI unit 302 accesses the information of the print jobs stored in the print job information data 308 via the print job management unit 303, and displays the print jobs to be printed on the print job list 607. The print operator selects the print jobs displayed on the print job list 607 with a pointing device 206 or the like, and issues print instructions, deletion instructions, editing instructions, etc. to the print jobs by pressing the function buttons arranged on the function menu 604. The editing that can be performed when an editing instruction is given includes the setting of leaving for each job and process as described above.

[0041] The device list 608 shows a list of image forming apparatuses that the print workflow application 301 manages as output destinations. The print workflow application 301 acquires the information of the image forming apparatuses that are communicably connected via the network 100 or the like via the device management unit 306, and displays it on the device list 608.

[0042] FIG. 6B shows an example of the process management view screen 603. This screen is displayed when the process management view tab is pressed. The process management view screen 603 includes the map view process management view screen 609. The map view 609 is a screen for displaying the status of each process at the printing site. The process management unit 307 accesses the map data 310 and is displayed based on the previously registered map information. In the present embodiment, a map view in which the lamination process 610, the cutting process 613, the inspection process 617, and the packing process 621 are arranged is displayed. Also, in each process, a workbench for arranging in-process jobs, equipment and tables for performing the work of each process, etc. are arranged on the map. The objects 611, 615, 619, 622 show examples of UI displays indicating the number of in-process jobs that can be processed in each process and are arranged on the workbench. Here, the in-process waiting means waiting for the process placed in the waiting queue waiting for the completion of the job being processed in each process. The objects 612, 616, 620, 623 show examples of UI displays indicating the ID and the number of jobs being processed in each process. The objects 614, 618 show examples of UI displays indicating the number of jobs left unattended for a certain period of time for processing in each process. These UI displays are controlled by the process management unit 307 accessing the process management information data 309, and the details will be described later.

[0043] ● Visualization processing of the process for each job (continued) In S501, when the UI unit 302 detects that the process management view tab button 603 has been pressed (or touched), it determines that there is a display request for the process management view.

[0044] In that case, in S502, the process management unit 307 acquires the detection information of the article tag. The process management unit 307 accesses the management server 401 and acquires the location management information managed by the location management system 104.

[0045] ● Location management information FIG. 9 shows the location management information data managed by the management server 401. FIG. 9(A) shows the definition table of the RFID tags managed by the location management system 104. The tag definition table stores the "tag ID" for each RFID tag, the "type" (defining whether it is an item tag or a location tag), and in the case of a location tag, the "coordinate" information defining the location. These pieces of information are registered in advance for using the RFID tags in the location management system 104. The tag ID stores the unique identification information (ID) stored in the RFID tag and included in the output signal.

[0046] FIG. 9(B) shows the tag detection information table that stores the information of the tag ID 407 detected by the tag reader 403 managed by the location management system 104. The tag detection information table stores the "detection time" when the tag reader 403 detects an item tag, the "tag ID" of the detected item tag, and the "reader ID" identifying the tag reader 403 that detected the item tag. Also, the "reference tag ID" indicating the location information of the detected tag ID and the "movement amount" from the reference tag ID are stored together. The "reference tag ID" stores the tag ID indicating the location tag detected together with the item tag, and the "movement amount" stores the relative position from the location indicated by the location tag (i.e., the deviation from the position of the location tag). This may be, for example, the relative position based on its own movement amount detected by the above-described tag reader 403. Since the movement amount measured by the tag reader 403 is the relative position with respect to the specified reference position, if the relative positions of each location tag with respect to the reference position are specified, the relative position of the tag reader with respect to the location tag can be specified by the difference between them.

[0047] As another example, the "movement amount" may record the relative position of the item tag detected simultaneously with the location tag with respect to the location tag. For example, if the tag reader 403 is provided with a plurality of antennas, the position of the transmitting RFID tag can be specified based on the phase difference of the signals received from the RFID tag by each antenna. In that case, the difference between the position of the specified location tag and the position of the item tag becomes the relative position of the item tag with respect to the location tag.

[0048] For the tag detection information table in FIG. 9(B), information is added each time the tag ID 407 is detected by the tag reader 403. Old detection information that has passed a certain period may be deleted from the table. The deletion may occur, for example, when the tag ID of a certain article tag detected together with the tag ID of the position tag A corresponding to a certain process is then detected together with the tag ID of another position tag B corresponding to a subsequent process. In that case, the detection information for the article tag detected together with the tag ID of the position tag A becomes the target of deletion. At this time, the detection times may be compared, and it may be conditional that the article tag is detected later in a subsequent process than in a previous process. In S502, the process management unit 307 refers to the tag detection information table in FIG. 9(B) and acquires the information. The information acquired here may be one record in the tag detection information table. The article tag corresponding to the tag ID included in the acquired record is also called the target tag, and its tag ID is also called the target tag ID. The order of attention may be, for example, in the order of the latest detection time. Also, when multiple records with the same tag ID are obtained in the process of FIG. 5, only the record with the latest acquisition time may be targeted, and the other records may be ignored.

[0049] In S503, the process management unit 307 acquires the position information of the job. FIG. 8 shows the process management information stored in the process management information data 309. FIG. 8(A) shows the process management table, which is a table for storing the status of the jobs managed in the process management view. The process management table stores the information of "job ID" associated with the "tag ID". The process management table also stores the "detection area" of the tag, the "product material" of the job, the current "process", a "neglected job" flag for recording whether the job is neglected, and the information of "first detection date and time" for recording the date and time when the job is detected for the first time as the current process. Here, regarding the method of associating the "tag ID" with the "job ID", it may be performed as described above, or the association may be performed by sequentially reading the barcode attached to the circular or work instruction sheet, etc. and the barcode attached to the job. The method is not particularly limited here. In any case, the information of "tab ID" and "job ID" that has been associated in advance via the process management unit 307 is stored in the process management table. Further, the product material ID may also be registered and stored together with the tag ID and the job ID. Their storage may be at the time when the article tag corresponding to the job is created or at the time when the job is attached. The process management unit 307 obtains the information of the tag detection information table in FIG. 9(B) acquired via the management server 401 and the information of the process management table in FIG. 8(A), and associates the detected tag ID with the job ID to obtain the information of the position where the "job ID" is detected. Here, the job corresponding to the target tag is also called the target job, and its job ID is called the target job ID.

[0050] In S504, the process management unit 307 refers to the process area table to acquire the association information between the position tag and the process. FIG. 8(B) shows the process area table, which defines the relationship between the "area name" and "process" managed in the process management view, and the "tag ID" of the position tag indicating the position of the area. Further, the information of "area range" is also defined to determine the range of several centimeters in radius from the coordinates of the position tag as the area. The process area table may be registered when the position tag is arranged in the factory.

[0051] In S505, the process management unit 307 identifies the process and area at the time of detecting the target job based on the position information of the target job acquired in S503 and the position information of the process acquired in S504. The process management unit 307 determines whether the amount of movement (i.e., relative position) from the reference tag ID acquired from the tag detection information table in FIG. 9(B) falls within the area range of the tag ID (identical to the reference tag ID) in the process area table in FIG. 8(B). If it falls within the area range, the target job is determined to be a job existing in the area and process. Note that the area corresponding to one process includes the area being processed and the area waiting for processing of that process. In S505, not only the process but also the area where the job is placed is identified.

[0052] In S506, the process management unit 307 determines whether the target job is the first detection in the current process. The process management unit 307 determines that it is the first detection in the changed process when the current process corresponding to the target job has changed from the value of "process" in the process management table in FIG. 8(A). If it is the first detection, it proceeds to S507; if it is not the first detection, it proceeds to S510.

[0053] In S507, the process management unit 307 determines whether a holding time is set for the process of the target job. For this purpose, the process management unit 307 accesses the print job information data 308 via the print job management unit 303 and acquires the job information data in FIG. 7(A). FIG. 7(A) shows a job information table and stores information on jobs printed by the print workflow application 301. The job information data is information in which the print settings in the print process of each job are registered. The job information data may be registered at the time of setting the workflow. The print job information data 308 stores print settings such as a "job ID" that uniquely identifies a job, a "commodity ID" indicating commodity information, the "number of copies" at the time of printing, the "output printer", the specified "paper type", a "content name" indicating original data, and the "print date and time".

[0054] Figure 7(B) shows the commercial material information table, which defines the print format and other details of the job. The commercial material information table stores a "commercial material ID" that uniquely identifies the commercial material, an arbitrary "commercial material name", an "output paper size" indicating the print format, a "finished size", a "paper type", an "orientation", and a "single-sided / double-sided" setting. Additionally, "staple", "punch", "fold", "binding", "saddle stitch", "cutting", "lamination", "inspection", and a "WFID" indicating the workflow of the commercial material are stored.

[0055] Figure 7(C) shows the workflow information table, which defines the workflow of the job. It stores a "workflow ID (WFID)" that uniquely identifies the workflow and the processing order of each step. Taking "WF001" in Figure 7(C) as an example, a workflow is defined where each step is processed in the order of [Printing] → [Binding] → [Cutting] → [Inspection] → [Delivery]. Also, in Figure 7(C), information on the idle time set for each step is stored.

[0056] Taking "WF002" in Figure 7(C) as an example, it is a workflow where the processing is done in the order of [Printing] → [Inspection], but it shows that an idle time of 420 minutes is set before starting the [Inspection] step. This is because it is necessary to leave the paper for this time to remove the static electricity generated in the paper bundle before setting the paper on the inspection machine in the [Inspection] step after printing. Similarly, in "WF003", it shows that an idle time of 1440 minutes is set before starting the [Cutting] step. This is because it is necessary to leave the laminated paper for this time to dry it before cutting with the cutting machine. Each piece of information in the commercial material information table in Figure 7(B) and the workflow information table in Figure 7(C) is assumed to be set in advance by the printing operator or administrator using the UI etc. (not shown) of the print workflow application 301.

[0057] In S507, using the job ID as a key, the values of the product ID and WFID are specified, and with the specified workflow ID, it is determined whether a waiting time is set for the area and process specified in S505 by referring to the workflow information table in Fig. 7(C). To specify the WFID using the job ID as a key, the product ID corresponding to the job ID can be obtained from the job information data in Fig. 7(A), and the workflow ID associated with the product ID can be obtained from the product information table in Fig. 7(B). Thus, the waiting process and waiting time set for the workflow can be specified from the job ID. Since the waiting time is the time to wait for the job before performing the process of the step, if the position of the specified job is within the processing waiting area for waiting for the step, it is determined that the waiting for the step is set and the waiting time is set. For example, if a waiting time of 1440 minutes is set for the cutting step, it is determined that the waiting time is set when the specified area is "waiting for cutting" and the step is "cutting". On the other hand, if the specified area is "cutting" and the step is "cutting", it is determined that the waiting time is not set. The same applies to other steps (such as lamination, inspection, etc.). If it is determined that a waiting time is set for the target job, the process proceeds to S508; if not, it proceeds to S513. Note that "waiting for cutting" is the processing waiting area for the "cutting" step, and "cutting" is the processing area during the "cutting" step. The same applies to other steps.

[0058] In S508, the process management unit 307 sets the waiting job attribute of the target job ID to ON. The value of "waiting job" for the target job ID in the process management table in Fig. 8(A) is set to ON. In S509, the process management unit 307 stores the first detection date and time of the target job ID. The "detection time" in the tag detection information in Fig. 9(B) is stored in the "first detection date and time" corresponding to the target job ID in the process management table in Fig. 8(A). In S510, the process management unit 307 determines whether a suspension job attribute is assigned to the target job ID. The process management unit 307 refers to the value of "Suspended Job" of the target job ID in the process management table of Fig. 8(A). If it is ON, it determines that the suspension attribute is assigned and proceeds to S511. If it is not ON, it proceeds to S513. In S511, the process management unit 307 determines whether the detection time of the target job ID is within the suspension time. The process management unit 307 determines whether the "detection time" is within the "suspension time" from the "first detection date and time" based on the "detection time" of the tag detection information in Fig. 9(B), the "first detection date and time" in Fig. 8(A), and the "suspension time" set for the current process of the target job ID. If it is determined to be within the suspension time, it proceeds to S512. Also, if the suspension time has elapsed, it is determined that the suspension time has elapsed and it proceeds to S513. If the suspension time for the target process is not set, it may be determined that the suspension time has elapsed and it proceeds to S513. In S512, the process management unit 307 counts the target job ID as a count target for the suspended jobs in the current process of the target job. This count of the number of suspended jobs is performed for each process. In S513, the fixed management unit 307 sets the target job ID as a count target for the jobs waiting for processing or being processed in the current process of the target job according to the area where the target job is placed. This count of the number of jobs waiting for processing or being processed is performed for each process. If the value of "Suspended Job" in the process management table of Fig. 8(A) for the target job ID is ON, it is set back to OFF.

[0059] In S514, the process management unit 307 updates the information in the process management table of FIG. 8(A) for the target tag. FIG. 8(C) shows the state where the information is updated based on the tag detection information of FIG. 9(B) with respect to FIG. 8(A). For example, "Job003" exists in the cutting-waiting area, indicating that it has been left in a state where the cutting process has not started yet. If the information in the process management table has been sequentially updated in the previous processes, it is not necessary to update it again here. However, if the information in the process management table has not been updated sequentially in the previous processes and only intermediate data has been created, the information in the process management table is updated here using the intermediate data.

[0060] In S514-2, the process management unit 307 determines whether the processing of FIG. 5 has been completed for all records of the position management information data (FIG. 9(B)), that is, for all jobs whose current positions are managed. If there are un-targeted records remaining, the tag ID included in one of them is used as a new target tag, and the process repeats from S503. If the processing of FIG. 5 has been completed for all records, the process branches to S515.

[0061] In S515, the process management unit 307 refers to the information in the process management table of FIG. 8(A) (FIG. 8(C)) and determines whether there is a processing-waiting area where the number of jobs exceeds the threshold. The process management unit 307 calculates the number of jobs existing in the process waiting area (e.g., "lamination waiting" or "cutting waiting") in the "detection area" of FIG. 8(C). If the number of jobs that exist in the same processing-waiting area and whose idle job attribute is not ON exceeds the threshold, it is determined that there is a processing-waiting area that exceeds the threshold, and the process proceeds to S516. If not, the process proceeds to S517. Note that the threshold is predefined by the system. In S516, the process management unit 307 changes the display format of the number of jobs in the processing-waiting area that exceeds the threshold determined in S515 to an alert state. In S517, the process management unit 307 updates the count display of the number of jobs being processed, waiting for processing, and being idle in each process of the process management view based on the information in the process management table of FIG. 8(A) (FIG. 8(C)).

[0062] As an example, the number of jobs waiting for processing display 611 in the lamination process of FIG. 6B is the value obtained by counting the number of jobs where the "detection area" in the process management table of FIG. 8(A) (FIG. 8(C)) is "waiting for lamination" and the "idle job" is "OFF". On the other hand, the number of idle jobs display 614 in the cutting process of FIG. 6B is the value obtained by counting the number of jobs where the "detection area" in the process management table of FIG. 8(A) (FIG. 8(C)) is "waiting for cutting" and the "idle job" is "ON". Also, the number of jobs waiting for processing display 619 in the inspection process of FIG. 6B is the value obtained by counting the number of jobs where the "detection area" in the process management table of FIG. 8(A) (FIG. 8(C)) is "waiting for inspection" and the "idle job" is "OFF", but it exceeds the system threshold. Therefore, the display format is set to an alert state (expressed as diagonal lines as an example). The display format in the alert state may be in another form such as changing the color or highlighting. Note that the tag detection information (FIG. 9(B)) detected by the tag reader is updated sequentially. Therefore, during the display of the process management view, the processing of this flowchart (after S502 including the initialization of the job number counter for each process) may be executed at regular intervals to reflect the updated tag detection information.

[0063] By performing the above processing and using the position information that can be detected by the RFID tag, it becomes possible to visualize the status of jobs in each process (especially offline processes). Also, when the idle time of a job is set, it is possible to control so that it is not counted as a job waiting for processing during the idle time. Furthermore, it is also possible to visualize the fact that there is an idle job as the status of the jobs in the process.

[0064] [Modification Example] The position management system shown in Fig. 4 identifies the position of the article tag by placing the position tag at the position corresponding to each process. On the other hand, the reader 403 may be placed at the position of each process, and the position of each reader 403 may be specified in advance. By configuring in this way, the process can be identified according to the reader that has detected the article tag. In this case, it is not necessary to place the position tag.

[0065] <Second Embodiment> The second embodiment of the present invention will be described. Note that the description of the same configuration as that of the first embodiment will be omitted. In the first embodiment, it was premised that both the job waiting in one process and the job left in that process were placed in the process waiting area. In the second embodiment, the processing when an area for leaving jobs (leaving area) is separately defined will be described.

[0066] Figs. 10A and 10B are flowcharts showing the process of visualizing the status of jobs in each process considering the job leaving time. The same reference numerals are used for the same processes as in Fig. 5. The description of the steps common to Fig. 5 is simplified, but the same steps with the same reference numerals perform the same processes as in Fig. 5. Each processing step will be described. The flow of Fig. 10 is obtained by adding the processes of S1001 to S1006 to the flow of Fig. 5, but the process identification process common to the embodiments described later is summarized in Fig. 10B and reconfigured to be called from the process of Fig. 10A. Here, S1001 to S1006, which are particularly characteristic of this embodiment, will be described. Also, Figs. 10A and 10B are referred to as Fig. 10, and they are not distinguished in the description.

[0067] After the process of S501, the process identification process of FIG. 10B is executed at S501-2. In S1001, the process management unit 307 acquires the association information between the attention position tag and the process. S1001 is a step that replaces S504 in FIG. 5, and the process area table to be referred to is FIG. 11(A) instead of FIG. 8(B). FIG. 11(A) shows the process area table. In FIG. 11(A), a dedicated area named "storage location" for placing jobs for storage is additionally defined in the "area name". Since the storage location is not directly associated with the process, "process" is empty, but the information of "tag ID" and "area range" of the position tag indicating the position is defined in the same way as other areas.

[0068] In S1002 following S1001, the process management unit 307 identifies the process of the job based on the position information of the job acquired at S503 and the position information of the process acquired at S1001. S1002 is a step that replaces S504 in FIG. 5, and the process area table to be referred to is FIG. 11(A) instead of FIG. 8(B). The process management unit 307 determines whether the movement amount from the reference tag ID acquired from the tag detection information table in FIG. 9(B) is within the area range of the tag ID (identical to the reference tag ID) in the process area table of FIG. 11(A). If it is within the area range, the job of interest is determined to be a job existing in that area and the process corresponding to that area. Here, if the job is determined to be a job existing in the "storage location", the process is indeterminate.

[0069] In S1003 following S1002, the process management unit 307 determines whether the job of interest is detected in the "storage location". If it is determined that the job of interest is detected in the "storage location", the process proceeds to S1004, and if it is detected outside the "storage location", the process proceeds to S506.

[0070] In S1004, the process management unit 307 identifies the process in which the target job is being left unattended. The process management unit 307 identifies the process from the detection area before the target job is detected at the "placement location" and the workflow information of the target job. For example, if the detection area before the job is detected at the "placement location" is "during lamination" and the workflow information of the job proceeds from the "lamination" process to the "cutting" process, it is identified as being left unattended during the "cutting" process. Note that the method of identification is not limited to the above-described method. For example, the printing operator may be allowed to specify the process via a UI (not shown). The identified process is stored in association with the target job.

[0071] After counting the number of jobs in S512 or S513, in S1005, the process management unit 307 updates the information in the process management table. FIG. 11(B) shows the updated information in the process management table of the present embodiment. For example, for "Job003", the detection area is the "placement location", but the process specified in S1004 is stored in the process.

[0072] In S1006 following S516, the process management unit 307 updates the count display of the number of jobs being processed, the number of jobs waiting to be processed, and the number of jobs being left unattended in each process in the process management view based on the information in the process management table of FIG. 11-B. Here, when the "detection area" in the process management table is the "placement location", it is counted as the job being left unattended in the process indicated by the "process". For example, "Job003" in FIG. 11(B) is counted as the job being left unattended in the cutting process. Note that even if the "detection area" is the "placement location", if the elapsed time of being left unattended has passed, it is counted as the number of jobs waiting to be processed in the process.

[0073] Also in the present embodiment, the display example may be as shown in FIG. 6B. That is, for the job being left unattended, it is clearly displayed as being left unattended near the process name as the job being left unattended in the process where it is left. Alternatively, the placement location of the job being left unattended may also be shown on the map of FIG. 6B, and the process name and the number of jobs being left unattended in that process may be displayed therein.

[0074] By performing the above processing, even when the placement location of the job to be left unattended is defined separately, it becomes possible to count the job in the process of the job's step as an unattended job.

[0075] <Third Embodiment> The third embodiment of the present invention will be described. This embodiment is based on the first embodiment or the second embodiment. In this embodiment, when a job in the unattended area is moved to the in-process or waiting-for-processing area, a warning regarding this is output. That is, the unattended job is placed in the unattended area. Regarding this embodiment as well, the description of the same configuration as that of the first embodiment and the second embodiment will be omitted. In the third embodiment, the warning process when a job during the unattended period is used for the process of the step will be described.

[0076] FIG. 12 is a flowchart showing the process of visualizing the status of jobs in each step considering the job's unattended time. Regarding the same process as in FIGS. 5 and 10, the same reference numerals will be used for the description. Each processing step will be described.

[0077] When the process management unit 307 determines in S507 that an unattended time is set for the current step of the job of interest, it branches to S1201. In S1201, the process management unit 307 determines whether the area where the job of interest is detected is the in-process area of the step and whether the detection time is within the unattended time before the start of the processing of the current step of the job of interest. The detection time is the detection time obtained from the tag detection information table in FIG. 9(B) for the tag of interest. For example, when the "processing area" where the job of interest is detected is "during inspection" and an unattended time for inspection is set in the workflow setting of the detected job, it is determined whether the unattended time has elapsed since the first detection time of "waiting for inspection".

[0078] In S1201, if the area where the target job is detected is the processing area and the elapsed time of the target job in the current process has not passed, it is determined that the target job has moved to the processing or waiting for processing of the current process within the elapsed time, and the process proceeds to S1202. On the other hand, in S1201, if the area where the target job is detected is not the processing area or the elapsed time of the target job in the current process has passed, the process branches to S508. If the elapsed time has already passed, it may branch to S513, but since the determination is also made in S511, here it branches to S508. The elapsed time can be determined based on the first detection time of "waiting for inspection".

[0079] The aforementioned "during inspection" is an example, and the same judgment applies to other processes (such as lamination, cutting, etc.). The first detection time may be obtained from the process management table in Fig. 8(C) or Fig. 11(B). Also, the workflow setting including the notification time for each process can be obtained from the workflow information table in Fig. 7(C). In S1202, the process management unit 307 assigns a warning flag to the target job. The warning flag may be assigned to the current process of the target job. In S1203 following S512, the process management unit 307 updates the information in the process management table. Fig. 13 shows the updated information in the process management table in this embodiment. A new warning column is added to the process management table of this embodiment, and in S1202, a warning flag is assigned to this warning column of the target job. For example, for "Job002", since the detection area is "during inspection" but the elapsed time for the start of inspection has not passed, the [Warning] flag for warning about the start of the inspection operation is set to ON.

[0080] In S1204 following S516, the process management unit 307 refers to the process management table to determine whether there is a job with the [Warning] flag ON. If there is a job with the [Warning] flag ON, the process proceeds to S1205; if not, the process proceeds to S1006. In S1205, the process management department 307 refers to the process management table and performs a warning display for jobs with the [Warning] flag ON. FIG. 14 shows an example of the warning display. Message 1401 is a warning display for the start of inspection of Job002. This warning is displayed within the process management view, but it may also be notified to a terminal or the like in the hands of the operator at the printing site.

[0081] By performing the above processing, it becomes possible to perform a warning display when starting to process a job during the idle time. This can reduce the work mistakes of the printing operator.

[0082] Note that in this embodiment, it is a warning process when moving a job during the idle time to the process being processed, but it may be allowed to move the job during the idle time to the idle place described in the second embodiment. When many jobs are placed near the workbench of the process, a case where the job to be placed is evacuated to another idle place can be considered. In this case, even after moving to the idle place, the initial detection time shall inherit the detection time of the previous place. This makes it possible to correctly calculate the idle time. Also, when an idle area is provided as in the second embodiment, the determination in S1201 may be a determination of "whether the detection position of the target job is not in the idle area and it is during the idle period". By doing so, it is also possible to output a warning for a job that has been moved from the idle area to the process waiting area during the idle period.

[0083] <Fourth Embodiment> The fourth embodiment of the present invention will be described. Note that the description of the same configuration as that of the first embodiment, the second embodiment, and the third embodiment will be omitted. In the fourth embodiment, the process of making the idle time of the process variable according to the printing attributes and the process of making it changeable during printing execution will be described.

[0084] FIG. 15 is a flowchart showing a process of visualizing the status of jobs in each process considering the job idle time. For the same processes as in FIGS. 5, 10, and 12, the same reference numerals are used for explanation. Each processing step will be described.

[0085] In this embodiment, S1501 is a step that replaces S511 in FIG. 12. In S1501, the process management unit 307 determines whether the detection time of the target job ID with the idle job attribute is within the idle time. The process management unit 307 determines whether it is within the idle time based on the "detection time" of the tag detection information in FIG. 9(B), the "first detection date and time" in FIG. 8(A), and the "idle time" set for this process of the job ID. Here, FIG. 16 shows the job information data of this embodiment. FIG. 16(A) shows the workflow information table of this embodiment. In "WF002", two types of idle times (A: 420 minutes, B: 120 minutes) are set for the inspection process. This is a setting for making the idle time variable according to the printing conditions. FIG. 16(B) is a table of the condition settings for idle times A and B. Idle time A is for the case where the paper type is top coat and the output printer is iPR Vxxxxx, and idle time B is for the case where the paper type is coated cardboard and the output printer is iPR Cxxx. It is possible to make the idle time variable according to the printing settings of the job and their combinations. When determining whether the detection time of the target job is within the idle time in S1501, the printing setting information of the target job is acquired, and the idle time that matches the conditions shown in FIG. 16 is used.

[0086] FIG. 17 is a flowchart showing a process of temporarily setting the idle time when a job is printed. Each processing step will be described. The management procedure in FIG. 15 targets the output by the print job executed according to the procedure in FIG. 17.

[0087] In S1701, the UI unit 302 receives an instruction for conditional printing processing. FIG. 18(A) shows a print job management view 602 of a print workflow application. The print job management view 602 includes a conditional print button 1801. In S1701, with one or more jobs selected in the job list 607, the UI unit 302 receives a press of the conditional print button 1801 via the UI unit 302.

[0088] In S1702, the UI unit 302 displays a conditional print screen. FIG. 18(B) shows an example of a conditional print screen. The conditional print screen 1802 includes a placement area designation box 1803, a placement time setting box 1804, and a print execution button 1805. The placement area may indicate a process where placement is set. A print operator or administrator can set the area (or process) for placement and the placement time for the job specified in S1701 on this screen.

[0089] In S1703, the UI unit 302 receives an execution instruction for conditional printing. When the UI unit 302 receives a press of the execution button 1805 for conditional printing via the UI unit 302, it transmits information on the specified placement area (i.e., the process to be placed) and the placement time to the print job management unit 303.

[0090] In S1704, the print job management unit 303 determines whether a placement time has been set when the conditional printing in S1703 is executed. If information on a placement area and a placement time with some valid value set in S1703 is obtained, it is determined that the placement time has been set, and the process proceeds to S1705. If the placement area and the placement time have not been set, the process proceeds to S1706.

[0091] In S1705, the print job management unit 303 creates a workflow information table based on the received idle area and idle time. FIG. 19 shows the print job information data 308 of this embodiment. FIG. 19(A) shows a job information table, and a temporary WFID is assigned to the job ID of the job specified in S1701. For example, for Job004, a temporary WFID "WF004" is associated. FIG. 19(B) shows a workflow information table, and workflow information is created based on the information received in S1703. Here, a WFID "WF004" is created, and an idle time of 1440 minutes is set in the binding process. By this process, temporary workflow information is created for the job. Although a workflow is also associated with the merchandise information linked to the job, when a temporary workflow is created, it operates to preferentially use the temporary workflow.

[0092] In S1706, the print processing unit 305 prints the specified job on the output printer. The temporary workflow may be deleted when the job is completed in production.

[0093] By the above processing, it becomes possible to make the idle time of the process variable depending on the print attributes. Also, even if the idle time is not set in advance as merchandise information, it is possible to perform processing that enables the idle time to be temporarily changed at the time of print execution.

[0094] Furthermore, according to the idle time set at the time of execution of the print job, the job process can be managed by excluding the job during its idle time from the jobs waiting for processing.

[0095] [Other Embodiments] The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiment 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. It can also be realized by a circuit (for example, an ASIC) that realizes one or more functions.

[0096] ● Summary of Embodiments Summarizing the above embodiments, the following inventions are included. (Item 1) A management system for managing a process of a management target to which a wireless tag is attached based on identification information of the wireless tag and a detection position of the wireless tag, storage means for storing association information associating the management target with the identification information of the wireless tag; setting means for setting, for each process, a lapse period during which each management target is left until execution of the process; first specifying means for specifying the number of management targets for each process corresponding to the detection position based on the identification information of the wireless tag and the detection position of the wireless tag; second specifying means for specifying, for each process, the number of management targets obtained by excluding the number of management targets being left for the process from the number of management targets specified by the first specifying means; output means for outputting, for each process, the number of management targets specified by the second specifying means A management system characterized by comprising the above. (Item 2) The management system according to Item 1, wherein the output means further outputs the number of management targets being left for each process A management system characterized by the above. (Item 3) The management system according to Item 1 or 2, wherein the management target is detected at a position corresponding to a leaving area where the management target being left for each process is left until execution of the process, and when the management target is being left for the process, the output means outputs the number of management targets detected in the leaving area as the number of management targets being left for the process A management system characterized by the above. (Item 4) The management system according to any one of Items 1 to 3, When the output means detects that the management target is being processed in a specific process during the set idle period, the output means outputs a warning indicating that the management target has been processed during the idle period for the management target. A management system characterized by the above. (Item 5) The management system according to any one of Items 1 to 4, wherein the management target is a print job executed by a printing device, and the setting means sets the idle period according to the print settings of the print job. A management system characterized by the above. (Item 6) The management system according to Item 5, wherein the print settings include the printing device that executes the print job and the type of sheet printed by the print job. A management system characterized by the above. (Item 7) The management system according to any one of Items 1 to 6, wherein the management target is a print job, and the setting means can set the idle period for the designated process of the print job when the print job is executed. A management system characterized by the above. (Item 8) The management system according to any one of Items 1 to 7, wherein the output means displays the number of management targets for each process on a user interface. A management system characterized by the above. (Item 9) A program for causing a computer to function as the management system according to any one of Items 1 to 8. (Item 10) A management method by a management system that manages the process of a management target to which a wireless tag is attached based on the identification information of the wireless tag and the detection position of the wireless tag. The management system includes a storage means, a setting means, a first specifying means, a second specifying means, and an output means. The memory means stores association information associating the management target with the identification information of the wireless tag. For each process, the setting means sets a waiting period during which each of the management targets is left until the execution of the process. Based on the identification information of the wireless tag and the detection position of the wireless tag, the first specifying means specifies the number of management targets for each process corresponding to the detection position. For each process, the second specifying means specifies the number of management targets obtained by excluding the number of management targets that are being left for the process from the number of management targets specified by the first specifying means. The output means outputs the number of management targets specified by the second specifying means for each process. A management method characterized by the above.

[0097] The present invention is not limited to the above embodiments, and various changes and modifications can be made without departing from the spirit and scope of the invention. Therefore, claims are attached to disclose the scope of the invention.

Explanation of reference numerals

[0098] 101 Information processing apparatus, 102 Image forming apparatus, 103 Post-processing apparatus, 104 Position management system

Claims

1. A management system for managing a process of a management target to which a wireless tag is attached based on identification information of the wireless tag and a detection position of the wireless tag, a storage means for storing association information associating the management target with the identification information of the wireless tag; a setting means for setting, for each process, a leaving period during which each of the management targets is left until the execution of the process; a first specifying means for specifying the number of the management targets for each process corresponding to the detection position based on the identification information of the wireless tag and the detection position of the wireless tag; a second specifying means for specifying, for each process, the number of the management targets obtained by excluding the number of the management targets left in the process from the number of the management targets specified by the first specifying means; and an output means for outputting, for each process, the number of the management targets specified by the second specifying means A management system characterized by comprising.

2. The management system according to claim 1, wherein the output means further outputs the number of the management targets left in each process. A management system characterized by that.

3. The management system according to claim 2, wherein the management target is detected at a position corresponding to a leaving area where the management target left in each process is left until the execution of the process, and when the management target is left in the process, the output means outputs the number of the management targets detected in the leaving area as the number of the management targets left in the process. A management system characterized by that.

4. The management system according to claim 1, wherein when the management target is detected as being in the process during the leaving period set for a specific process, the output means outputs a warning indicating that the management target has been processed during the leaving period for the management target. A management system characterized by that.

5. The management system according to claim 1, wherein the management target is a print job executed by a printing device, and the setting means sets the leaving period according to the print setting of the print job. A management system characterized by that.

6. The management system according to claim 5, wherein the print setting includes a printing device that executes the print job and a type of a sheet printed by the print job. A management system characterized by that.

7. The management system according to claim 1, wherein the management target is a print job, The setting means can set the waiting period for each specified process of the printing job when the printing job is executed. A management system characterized by this.

8. The management system according to claim 1, The output means displays the number of the management targets for each process on a user interface. A management system characterized by this.

9. A program for causing a computer to function as the management system according to any one of claims 1 to 8.

10. A management method by a management system that manages the process of a management target to which a wireless tag is attached based on the identification information of the wireless tag and the detection position of the wireless tag. The management system includes a storage means, a setting means, a first specifying means, a second specifying means, and an output means. The storage means stores association information associating the management target with the identification information of the wireless tag. The setting means sets, for each process, a waiting period during which each management target is left until the execution of the process. The first specifying means specifies the number of management targets for each process corresponding to the detection position based on the identification information of the wireless tag and the detection position of the wireless tag. The second specifying means specifies, for each process, the number of management targets obtained by excluding the number of management targets being left for the process from the number of management targets specified by the first specifying means. The output means outputs the number of management targets specified by the second specifying means for each process. A management method characterized by this.

Images