Management system, management method, and program

Abstract

To provide a management system, a management method, and a program for managing processes in a workflow to perform warning notification at an appropriate timing to solve accumulation of jobs.SOLUTION: A method is executed in a management system comprising detection means that is provided with tags capable of reading information in a non-contact manner and moving with a product in a device corresponding to processes forming a workflow, and detects the tags arranged in association with the device, and the method includes the steps of: managing the progress of the processes in the workflow; specifying the number of jobs accumulated in the processes on the basis of a result of detection of the tags and the workflow, and when the specified number of accumulated jobs exceeds a predetermined value, performing warning notification; and making the predetermined value variable on the basis of the cause of the accumulation of the jobs in the processes.SELECTED DRAWING: Figure 14

Description

[Technical field]

[0001] The present invention relates to a management system, a management method, and a program for managing workflow processes. [Background technology]

[0002] In commercial printing, the process from "order placement" to the "printing process" is managed and visualized by printing workflow software. In addition, the status of online post-processing machines connected to the 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.

[0003] Patent Document 1 discloses a method for calculating travel time from the location information of equipment and workers. When an abnormality occurs in equipment, the travel time is used to enable an appropriate worker to respond. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2022-83570 Summary of the Invention [Problem to be solved by the invention]

[0005] The method described in Patent Document 1 focuses on travel time and can instruct the most appropriate worker to respond when a warning occurs. This can be said to be one of the aims of minimizing the impact of waiting for work in the process that occurs within the plant when a warning occurs. However, there is an issue that although a worker is instructed to respond when a warning occurs, there are cases where the cause of the warning cannot be resolved by the arrival of the worker.

[0006] Therefore, an object of the present invention is to enable a warning notification to be issued at an appropriate timing to resolve the congestion. [Means for solving the problem]

[0007] In order to solve the above problems, the management system of the present invention has a tag that can read information non-contactly so that it can move along with the deliverables in an apparatus corresponding to a process that makes up a workflow, and has a detection means for detecting the tag arranged in correspondence with the apparatus, a management means for managing the progress of the processes in the workflow, and a notification means for identifying the number of jobs waiting to be processed in the process based on the detection result of the tag detected by the detection means and the workflow, and for issuing a warning notification when the identified number of jobs waiting to be processed exceeds a predetermined value, and is characterized in that the predetermined value is made variable based on the cause of the jobs being stuck in the process. Effect of the Invention

[0008] According to the present invention, it is possible to issue a warning notification at an appropriate timing to eliminate congestion. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a configuration diagram of an image forming system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a hardware configuration diagram of the information processing apparatus according to the embodiment. [Diagram 3] FIG. 2 is a software configuration diagram of the information processing apparatus according to the embodiment. [Figure 4] The print job management screen of the print workflow application. [Diagram 5] FIG. 4 is a diagram showing a print job information table stored in print job information data. [Figure 6] FIG. 11 is a diagram showing a product information table stored in the print job information data. [Figure 7] FIG. 1 is a diagram showing an example of the configuration of a position 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 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 a configuration of a management server according to the present embodiment. [Figure 11] 3A to 3C are diagrams showing examples of the configurations of an item 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 management 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, a job status table, a process arrival table, and a process stuck table according to the embodiment. [Figure 14] FIG. 11 is a flow diagram showing a change of a retention determination value according to the present embodiment. [Figure 15] FIG. 11 is a flow diagram showing a process when an item is insufficient according to a modified example of the embodiment. [Figure 16] FIG. 13 is a diagram showing an example of a table representing a configuration having a plurality of retention determination values ​​according to the embodiment; [Figure 17] FIG. 11 is a flowchart illustrating a modification of the stay determination value change in the embodiment. [Figure 18] FIG. 11 is a flowchart of a modification of the embodiment that takes into account the worker level and indicates changes to the retention determination value. [Figure 19] FIG. 4 is a diagram showing an example of a table showing the work level of a worker and the work time for each process in the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0011] The following examples do not necessarily limit the present invention. Furthermore, not all of the combinations of features described in the examples are essential to the solution of the present invention, and multiple features may be combined arbitrarily. Furthermore, in the accompanying drawings, the same reference numbers are used for the same or similar configurations, and duplicate explanations are omitted. Furthermore, each process (step) in the flow chart is indicated by a reference number beginning with S. EXAMPLES

[0012] In this embodiment, the judgment value used for the congestion warning notification is made 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 timing to resolve the job congestion.

[0013] [Image formation system configuration] FIG. 1 is a block diagram illustrating the hardware configuration of an image processing device 1 according to an embodiment of the present invention.

[0014] FIG. 1 is a diagram showing an example of the configuration of an image forming system according to an embodiment of the present invention.

[0015] The system configuration 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 each other via a network 100. The position management system 700 and the process management system 1200 will be described later with reference to FIG. 7 and FIG. 12. The image forming device 102 analyzes print data transmitted from the information processing device 101 and the like, converts the data into a dot image page by page, and prints the data. The printed matter output from the image forming device 102 is handed over to the post-processing device 103 by an operator's hand carry, or is handed over to the post-processing device 103 via a belt conveyer (not shown). The post-processing device 103 is configured as 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 bookbinding on the handed-over printed matter. It is also possible to use multiple post-processing devices to bind and then cut the sheets. Although one each of the information processing device 101, image forming device 102, and post-processing device 103 is illustrated in Fig. 1, any number of each device may be arranged. For example, printed materials output by multiple image forming devices may be processed by multiple post-processing devices 103.

[0016] [Hardware configuration of information processing device] FIG. 2 is a diagram illustrating an example of a hardware configuration of the information processing device 101. As shown in FIG.

[0017] The CPU 201 reads out control programs stored in the ROM 202 or HDD 204 and executes various control processes. The RAM 203 is used as a temporary storage area such as the main memory and work area of ​​the CPU 201. The hard disk drive (HDD) 204 stores image data and various programs. Note that the configuration may include other storage devices such as a solid state drive (SSD) instead of or in combination with 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 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] A display 207 is an output device that is a display unit, and displays commands input from the keyboard 205 or pointing device 206, the state of applications described below, etc. A network I / F 208 connects the information processing device 101 to a network (such as a LAN, an intranet, or the Internet). The information processing device 101 uses the network I / F 208 to transmit and receive various information to and from other devices on the network.

[0020] [Software configuration of information processing device] FIG. 3 is a diagram illustrating an example of the software configuration of the information processing device 101. The print workflow application 301 is a program module that is installed and operates in the HDD 204 of the information processing apparatus 101, is loaded into the RAM 203 at the time of execution, and is executed by the CPU 201.

[0021] The print workflow application 301 includes 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.

[0023] A 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.

[0024] 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.

[0025] 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.

[0026] The device management unit 306 manages various information (such as an identification name and an address) of the image forming device to which the print workflow application 301 sends a print job.

[0027] The print job information data 307 is a database for managing information related to print jobs (a print job information table and a product information table) which will be described later. The print job information table will be described later in FIG. 6. The product information table will be described later in FIG. 6.

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

[0029] [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.

[0030] When the print operator instructs the information processing apparatus 101 to execute the print workflow application 301 via the keyboard 205 or pointing device 206, the CPU 201 loads a program into the RAM 203 and executes it. This starts the print workflow application 301. When the print workflow application 301 starts, the UI unit 302 displays a print job management screen as shown in Fig. 4 on the display 207. Here, the print workflow application 301 may access a cloud service from a web browser on the information processing apparatus 101, so that the print job management screen is displayed on the web browser.

[0031] A print job management screen 401 shows a print job management screen in the print workflow application 301. A function menu 402 shows a menu of functions that can be executed on the print job management screen 401. A print button 403 and a delete button 405 are arranged on the function menu 402. The print button 403 is a button for issuing a print instruction for a print job (an instruction for actual printing). The delete button 405 is a button for issuing an instruction to delete a print job. Note that an edit button or the like for issuing an instruction to edit a print job may also be provided on the function menu 402.

[0032] 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 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. The print operator selects a print job displayed in the print job list 406 with the pointing device 206 or the like, and issues print instructions, deletion instructions, editing instructions, etc. to the print job by pressing a function button arranged in the function menu 402.

[0033] 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 information on image forming devices communicably connected via the network 100 or the like via the device management unit 306, and displays the information in the device list 407.

[0034] [Print job table configuration] FIG. 5 is a diagram showing an example of a print job information table stored in the print job information data 307. As shown in FIG.

[0035] In the example shown in Fig. 5, the print job information table has items such as job ID, product number, product name, number of copies, content name, order date, and 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, which will be described later. The content name is link information to a file name that is the content data used when printing the print job.

[0036] [Product information table configuration] FIG. 6 is a diagram showing an example of a product information table stored in the print job information data 307. As shown in FIG.

[0037] In the product information table, detailed setting values ​​related to printing (output paper size, finished size, paper type, orientation, single-sided / double-sided, stapling, punching, folding, binding, trimming, paper output destination, etc.) are defined. The product information table is created in advance by an installer such as a system engineer when the print workflow application 301 is installed, according to the order contents of the print material handled by the print workflow application 301. The print job management unit 303 acquires detailed print settings from the product information table using the above-mentioned product name as a key. For example, an example of a product name "saddle-stitched imposition_A4_double-sided_landscape" will be described. In this case, the following settings are acquired: output paper size "320×450", paper type "high-quality paper", single-sided / double-sided "double-sided", binding "ON", saddle-stitching "ON", trimming "ON", and lamination "ON".

[0038] [Location management system configuration] FIG. 7 is a diagram showing an example of the configuration of a location management system 700 according to the present invention. The location management system 700 is a system that manages item data in a database. The location management system 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, a management server 701, and an information processing device 101. The mobile system 714, the tag reader 705b, the management server 701, and the information processing device 101 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.

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

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

[0041] 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 numerals will be omitted and these 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.

[0042] In an embodiment of the present invention, each of the tags such as the position tag 707 and the item tag 709 is 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 for identifying the tag in the memory. In this specification, the identification information is also simply called ID, and the identification information for identifying the tag is also called tag ID. Note that the tag ID may be considered as information for identifying 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.

[0043] In another embodiment, each tag may be an active RFID tag. When each tag actively (for example, 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 returns information, for example, by 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.

[0044] 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 executes 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 described later). An example of a specific configuration of the tag reader 705 will be further described later.

[0045] In the example shown in Fig. 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 by the location management system 700. An example of a specific configuration of the user terminal 706 will be further described later.

[0046] 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 a plurality of items 711. The management server 701 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 701 receives tag reading results from the tag reader 705, and updates the database based on the received tag reading results.

[0047] 7 shows a single management server 701, 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. In addition, in this embodiment, an example in which the management server 701 holds the database will be described, 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.

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

[0049] [Tag reader configuration] 8 is a block diagram showing an example of the configuration of tag reader 705 in the present invention. 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.

[0050] The control unit 801 is composed of a memory that stores a computer program, and one or more processors (e.g., a CPU (Central Processing Unit)) that execute the computer program. The control unit 801 controls the overall function of the tag reader 705 described in this specification. For example, the control unit 801 causes the reading unit 806 to execute reading of an RFID tag within a 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 80. In addition, the control unit 801 causes the measurement unit 804 to measure the position of the tag reader 705 in parallel with reading the RFID tag, and stores the measurement result in the storage unit 802. Then, the control unit 801 transmits the read result data and the 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 called the reader ID) of the own device.

[0051] The storage unit 802 may include any type of storage medium, such as a semiconductor memory such as a ROM (Read Only Memory) or a RAM (Random Access Memory), 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.

[0052] 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 WLAN interface for communicating with a WLAN (Wireless Local Area Network) 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 USB (Universal Serial Bus) interface).

[0053] 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-position estimation technique also called PDR (Pedestrian Dead Reckoning), 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 when the tag reader 705 is started. 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. The gyro sensor 804b measures the angular velocity of the tag reader 705, i.e., the change in the attitude of the tag reader 705, and outputs second sensor data. The geomagnetic sensor 804c measures the orientation of the tag reader 705 in real space, and outputs third sensor data. Based on the sensor data from these sensors, the measurement unit 804 can measure the relative movement amount of the tag reader 705 by accumulating the acceleration while converting the direction of the acceleration of the tag reader 705 into a direction in the coordinate system of the real space. The relative movement amount output from the measurement unit 804 to the control unit 801 may be a two-dimensional vector in a horizontal plane, or may be a three-dimensional vector including a component in the height direction.

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

[0055] Note that instead of tag reader 705 including measurement unit 804, portable system 714 may include a measurement device separate from tag reader 705 (eg, capable of measuring the amount of relative movement using self-location estimation technology).

[0056] 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 a voice input interface such as a microphone.

[0057] The reading unit 806 is a unit capable of reading information stored in each of the position tags 707 and the article 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 the TX terminal to the power amplifier 808 in accordance with 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, and the higher the amplification factor, the higher the output intensity of the electromagnetic wave radiated from the tag reader 705. The filter 809 may be, for example, a low-pass filter, which removes unnecessary low-frequency components of the transmission signal amplified by the power amplifier 808. 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 an 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. 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. Then, the canceller 814 extracts a desired signal component of the received signal to be output to the RX terminal of the RF controller 807 by canceling the carrier wave component of the transmitted signal based on CARRIER_CANCEL.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.

[0058] [User terminal configuration] 9 is a block diagram showing an example of the configuration of a user terminal 706 included in a portable system 714 according to 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.

[0059] The control unit 901 includes a memory that stores a computer program, and one or more processors that execute the computer program. The processor may be a CPU, or may be an IC (Integrated Circuit) such as a microcontroller (e.g., a one-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 function of the user terminal 706 described in this specification. For example, when the location of the item 711 is inspected in the location management system 1, the control unit 901 causes the display unit 906 to display a screen that displays the current location of the portable system 714 and the locations of the items present in the vicinity. 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 later.

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

[0061] 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.

[0062] The photographing unit 904 is a so-called camera unit that photographs the state of the real space and generates image data of a still image or a video. The photographing unit 904 outputs the generated image data to the control unit 901. For example, the image data generated by the photographing unit 904 may be used for optical character recognition or for reading a visible code such as a barcode or a QR code (registered trademark).

[0063] 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 such as a microphone or a sensor that detects vibration.

[0064] The display unit 906 displays images and information. The display unit 906 may be, for example, an LCD (Liquid Crystal Display) or an OLED (Organic Light-Emitting Diode). 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.

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

[0066] The communication unit 1003 is a communication interface for 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 regarding 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 a management function 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 .

[0067] [Table composition] 11A to 11F respectively 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.

[0068] The item table 1004 has six data items: a tag ID 1111, an item ID 1112, a name 1113, a type 1114, a location 1115, and coordinates 1116. The tag ID 1111 is identification information that uniquely identifies the item tag 709 attached to each item 711 under the management of the system. 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. 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 the point where each item 711 is estimated to be located. The values ​​of the location 1115 and the coordinates 1116 may be updated by the location estimation unit 1011 when the movement of the item is detected by the tag reader 705, as will be described later.

[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 in each of the locations 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 in each location 712. The map image 1125 is a data item in which map image data of each location 712 is stored. The scale 1126 indicates a ratio for converting a distance on the map of the map image 1125 into a distance in real space (for example, how many meters one pixel of the image corresponds to in real space). Note that the map image data stored in the map image 1125 may be obtained from an external data source or uploaded and updated by the user at any time necessary.

[0070] Reader table 1006 has three data items: reader ID 1131, name 1132, and user 1133. Reader ID 1131 is identification information that uniquely identifies each tag reader 705 used in the system. Name 1132 indicates the name of each reader. User 1133 indicates user 704 who uses tag reader 705 by the value of user ID 1141 in user table 1007.

[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 of the users 704 who use the location management system 700. The name 1142 indicates 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 when each user 704 logs in to the system. In addition, it is also possible to link the user 704 with the user ID 1141 by attaching an item tag 709 to the user 704. In this example, the item tag 709 is attached, but it is also possible to adopt a configuration in which the tag is distinguished between for a "user" and for an "item," and the configuration of the table may change accordingly.

[0072] The movement amount table 1008 is a table for accumulating 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 the 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 in the form of a two-dimensional vector in the coordinate system of the real space.

[0073] The tag detection table 1009 is a table for accumulating 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 for identifying the tag reader 705 that performed tag reading 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. Detected position 1165 represents the position coordinates of the location where tag reader 705 was present when tag reading from item tag 709 was performed (i.e., the detected position of item tag 709 and corresponding item 711).

[0074] [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.

[0075] The process management system 1200 is a system that generates a process management screen as a 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 on the image forming device 102, the post-processing device 103, and the processes performed by each device within the area of ​​the printing factory.

[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 position table 1205, and the job DB 1207 includes a job status table 1208.

[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 a 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 position management system 700, a job management service 1206, and a process DB 1203 and transmits the information to the process management UI 1201.

[0078] The process location table 1205 is a table that manages information on each process 1321 within the area of ​​the printing factory and the coordinates 1322 of each process. In this table, coordinate information is defined in advance as to 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 readers 705c, 705d, and 705e for each process from the item table 1004 of the management server 701. It identifies which process in the area of ​​the printing factory the tag ID 710 is located in based on the acquired tag ID coordinates 1116 and the information in the process location table 1205. Here, as a method of identifying the process, for example, it is possible to calculate the distance between the coordinates in the process location table 1205 and the coordinates 1116 of the tag ID, and determine that the tag ID is located in that process if the distance is equal to or less than a threshold value. 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 ID is present in that process.

[0079] The job status table 1208 is a table for managing a job ID 1331 and a job status 1332. Here, a job in which the job status 1332 indicates that production has been completed indicates that all processes have been completed, and a job in which the job status 1332 indicates that printing has been completed and processing is being performed in an offline process.

[0080] The process arrival table 1209 is a table for managing each process 1321 within the area of ​​the printing factory and the details of tags that arrive at each process. At this process, the item tag 709 arriving at each process is read to obtain information on the arriving item. This table will be described later, but is created for each job when the process management service 1202 determines that a backlog has occurred.

[0081] The process backlog table 1210 is a table for managing the causes of backlog determined by the process management service 1202. Each process manages this table and collects the causes of backlog when a backlog occurs.

[0082] [Process table overview] 13(A) to (E) show examples of a job table 1204, a process position table 1205, a job status table 1208, a process arrival table 1209, and a process stuck table 1210 in the present invention. The job table 1204 includes items of a tag ID 1311 and a job ID 1312, and is a table for managing a tag ID 710 of an item tag 709 attached to an item 711 in FIG. 7 in association with a job ID of a job stored in the item 711. The tag ID 710 and the job ID may be linked by sequentially reading a barcode attached to the item 711, such as a returnable box or a work instruction sheet, and a barcode attached to the job. The linking method is not limited here.

[0083] The process location table 1205 includes items for each process 1321 within the area of ​​the printing factory and the coordinates 1322 of each process. The job status table 1208 includes items for job ID 1331 and job status 1332.

[0084] The process arrival table 1209 includes the items of tag ID 1341, ID type 1342, name 1343, quantity 1344, arrival time 1345, previous process work 1346, and previous process end time 1347. The ID type 1342 specifies whether the item is an item or a user representing a worker from the arrived tag ID 1341. The name 1344 indicates the name 1113 or 1142 that can be acquired from the item ID 1122 or user ID 1141 linked to the tag ID 1341. The quantity 1344 indicates the quantity of the item when the ID type 1342 is an item. The arrival time 1345 indicates the time when the item or user arrives at the process that manages the process arrival table 1209. The previous process work 1346 indicates which process the item was working at before arriving at the process. The previous process end time 1347 indicates the end time of the work at the previous process that arrives at the current process when the ID type 1342 is an item.

[0085] The process delay table 1210 includes items of a delay cause 1351 and a main delay count 1352. The delay cause 1351 indicates a delay cause that occurs in each process. Items of the delay cause include, but are not limited to, an item 711 linked to an arriving tag ID 710 and a user. The actual determination of the delay cause will be described in an embodiment below.

[0086] In addition to the above figures, the first embodiment will be described with reference to Fig. 14. Fig. 14 is a flowchart showing the display processing of the process management screen.

[0087] In S1401, it is confirmed whether the number of jobs in each process collected by the process management service 1202 exceeds a retention determination value. If it exceeds the retention determination value, the process proceeds to S1402, and if it does not exceed the retention determination value, the process returns to S1401 again when the screen is displayed.

[0088] In S1402, the conditions for performing the work are confirmed for the process determined to be stuck. The tag readers 705c, 705d, and 705e read the item tag 709. By reading the item tag 709, arrival status data for the user 704 performing the work in the process and the item 711 can be obtained. The obtained data is added to and managed in the process arrival table 1209. If all the items 711 and users 704 performing the work required for the job are present, the process proceeds to S1403, and if not, the process proceeds to S1404.

[0089] If all the conditions necessary for job execution are met in S1403, it can be determined that the process is in a workable environment. However, since a job is being held up, it is considered that an unusual current situation has occurred. For example, it is considered that the work speed is slower than expected due to a breakdown in the device used in the process, or the worker is unfamiliar with the work, but this is not limited to this. Since it is considered necessary to check the current situation and respond according to the situation, a warning that is unusual is issued and a notification is given. The notification can be, but is not limited to, a message displayed on the UI to prompt the user, or an icon displayed so that the user can easily identify the situation at a glance.

[0090] In S1404, the system waits for the arrival of all of the items 711 required for the job and the item tag 709 indicating the user 704 who will perform the work. When the item tag 709 is detected and all the necessary conditions are met, the system checks the condition with the latest arrival time 1345. In this embodiment, the latest condition is called condition A. If condition A depends on other processes, the system transitions to S1405, and if it does not depend on other processes, the system transitions to S1406. The determination of the dependency on other processes is assumed to be based on a table, but is not limited to this. An example of the case where a table is assumed is shown below. In advance, in the printing process, it is determined whether the deliverable of each process will affect the process after the process. At this time, the following are candidates for determining whether the process will have an impact, such as a process that takes a significant amount of time to work, a process that requires multiple conditions to be met, or a process that requires a certain level of skill, but is not limited to this. In addition, a configuration is adopted in which the dependent processes are determined in advance, but a configuration is also possible in which the dependent processes are determined automatically, such as by automatically acquiring the work time on site and judging the process based on a certain standard. The pre-process operation 1346 of condition A is compared with the above table, and if it is dependent on another process, it is determined that it is dependent.

[0091] In S1405, it is determined that the work of the process is delayed due to the influence of the previous process task 1346, causing a job backlog. Items that affect the subsequent process are recorded and managed as main causes in the backlog cause 1351 of the process backlog table 1210 of the previous process indicated by the previous process task 1346.

[0092] In S1406, condition A is recorded and managed as a cause of job backlog due to work delay in the process backlog table 1210 for the process in the item of backlog cause 1351 corresponding to condition A. For example, assume that condition A is related to a user. In this case, the value of main backlog count 1352 corresponding to the user in backlog cause 1351 is increased. When determining whether it is the main cause of backlog, if it falls below the current backlog judgment value, condition A is regarded as the main cause, but this is not limited to this. For example, it is also possible to calculate the average processing volume of jobs in the process, and determine that condition A is the main cause if the current average processing volume returns to the normal range.

[0093] At S1407, obtain the total number of delay factors 1351 recorded in the process delay table 1210 of the process. This value indicates the number of times the delay determination value has been exceeded in the process. Whether a certain amount has been obtained means that the delay determination has been made a certain number of times. Assume a predetermined numerical value for the certain number of times, but it is not limited to this. It can be changed for each unit of time such as daily or weekly according to the situation of each factory. If the certain number of times has been obtained, proceed to S1408; if not, end.

[0094] At S1408, by checking the breakdown of the process delay table 1210 of the process, change the value used for the delay determination. Determine whether to increase or decrease the determination value based on the content of each item. For example, assume that from the breakdown of the process delay table 1210, the main delay times 1352 are obtained as item A XX times, item B YY times, and the user ZZ times for the delay factor 1351. Assume the relationship XX < YY < ZZ times. In this case, since it can be analyzed that the delay determination due to the user (operator)'s arrival delay is the most frequent factor, a decision is made to decrease the determination value. At this time, the increase or decrease value is assumed to be a fixed value, but it is not limited to this. For example, record the maximum number of delays when a delay warning occurs. By obtaining the difference between this maximum number of delays and the determination value at each delay, the average excess number at the time of delay occurrence can be obtained. An example is considered where the determination value is changed by this average excess number. Also, depending on the delay factor, it is conceivable to increase rather than decrease the determination value.

[0095] <Effect of Example 1> In this example, when a warning notification of job delay is issued, identify and accumulate the main causes of the delay. By using this accumulated information to increase or decrease the determination value used for the delay determination, the warning notification can be changed. The warning notification can consider various things such as the display of a message, the change of an icon, and the change of color. As a result, it is expected that a more appropriate warning notification can be given and unnecessary delays can be reduced.

[0096] [Modification Example 1-1] In the first embodiment, it is determined whether a certain amount of main causes of the current stagnation has been acquired for the process for which the stagnation determination has been performed in S1407. However, as shown in S1404, if the process depends on another process, the main causes of the stagnation for that process should be added, but in the first embodiment, no determination is made.

[0097] A case where a main cause of retention is added to a dependent preceding process in S1404 will be described.

[0098] In S1407, it is confirmed whether a certain amount of data is obtained for the previous process in which the main cause of the retention has been added. The subsequent transition is the same as in the first embodiment.

[0099] <Effects of Modification 1-1> In this modified example, it is assumed that a main cause of congestion due to dependency on other processes is added. In the first embodiment, the judgment value of the process where a warning due to job congestion has occurred is changed. However, when a main cause is added to a process that is dependent on other processes, the judgment value cannot be changed until a job congestion occurs in that process. In this modified example, the congestion judgment value of the previous process can be changed in response to the occurrence of a job congestion in the process due to dependency on other processes. This is expected to have the effect of reducing unnecessary congestion, including in the previous process.

[0100] [Variation 1-2] In the first embodiment, if the arrival information of the item tag 709 is satisfied in S1402, an unusual warning notification for the process is issued in S1403. However, the present invention is not limited to an unusual warning notification for the process, and can also issue warning notifications for other processes. An example in which there is a partial shortage of items will be described using the flowchart in Fig. 15. Fig. 15 is a flowchart that is executed after it is determined in S1402 that there are no missing conditions for the work.

[0101] In S1501, job information is obtained using the job ID 1312 linked by the tag ID 1341. The required quantity of each item is calculated using the production quantity in the job information.

[0102] In S1502, the calculated quantity is used to check whether the quantity 1344 of the items that have arrived at the process is the amount required for the work. If there is no shortage, the process proceeds to S1403, and the same process as in Example 1 is performed. If there is a shortage, the process proceeds to S1503.

[0103] In S1503, if there is a shortage of items, it is considered that the work in the previous process did not go well. An unusual warning is notified to the previous process. As described above, various unusual warning notifications are possible.

[0104] In S1504, it is confirmed whether or not a held job has been executed in the process. If the held job has been executed, the unusual warning notification is terminated, and if the held job has not been executed, the notification is continued.

[0105] <Effects of Modification 1-2> In this modified example, it is assumed that there is a shortage of items necessary for work. In the first embodiment, it is possible to issue a warning notice that is different from the usual in the process, but it is not possible to issue a notice in the previous process. In this modified example, when there is a shortage of items, it is possible to issue a warning notice that is different from the usual in the previous process. This makes it possible to issue a warning with a high degree of urgency in the previous process.

[0106] [Variation 1-3] In the first embodiment, if the arrival information of the item tag 709 is satisfied in S1402, a warning notification that is out of the ordinary for the process is issued in S1403. However, in the present invention, the warning notification is not limited to an out of the ordinary warning notification for the process, and warning notifications for other processes can also be issued. Take the case where there is a problem in the transportation process as an example.

[0107] In S1403, the arrival time 1345 and previous process end time 1347 contained in the process arrival table 1209 are obtained. The transport time from the previous process to the process in question can be calculated from the difference between the two. It is checked whether this transport time indicates an abnormal value. Possible reference values ​​for transport time include, but are not limited to, measuring and storing the transport time between processes in advance, or calculating and storing an average transport time from the transport times of other jobs. If the value is abnormal, it is determined that there is a problem with the transport, and an unusual warning is sent to the previous process.

[0108] <Effects of Modifications 1-3> In this modified example, it is assumed that there is a problem with transportation. In the first embodiment, it was possible to issue a warning notice different from the usual one at the process, but it was focused on arrival information and it was not possible to notify of transportation problems. In this modified example, when there is a problem with transportation to the process, it is possible to notify at the previous process. This makes it possible to notify of transportation problems as a type of high-urgency warning at the previous process.

[0109] [Variation 1-4] In this embodiment, in S1408, the value used for the backlog determination is changed by checking the details of the process backlog table 1210 for the process. However, a configuration in which multiple determination values ​​for backlog determination are held can also be adopted. FIG. 16 shows a backlog determination table 1601. The backlog determination table 1601 includes a determination value 1611 and a backlog cause 1621, and is created and managed for each process. The determination value 1611 indicates a value used for determination when issuing a warning notice of a job backlog. The backlog cause 1621 indicates a condition that is insufficient to perform work. In the initial state, the same value is entered in the table, and when increasing or decreasing the determination value, the determination value 1611 and the backlog cause 1621 are rewritten as a set. In the example of this table, a warning notice is usually issued when the number of backlogged jobs exceeds 10. However, a warning notice is issued when the arrival of the user is delayed and the number of backlogged jobs exceeds 8. Here, the backlog cause 1621 in the default condition is described as normal, but is not limited to this. Also, in this example table, there are two judgment values ​​1611, but there may be more.

[0110] If it is decided in S1408 to change the warning judgment value, the changed value is set as the judgment value 1611, and the cause with the most congestion judgments is set as the congestion cause 1621. Then, these are stored and managed in the congestion judgment table 1601.

[0111] <Effects of Modifications 1-4> In this modified example, a configuration is assumed in which multiple congestion judgment values ​​are held. In the first embodiment, it was decided to increase or decrease the congestion judgment value depending on the main cause of the congestion. However, while this is effective when a job is stuck in the process due to the main cause of the congestion, there is a possibility that the effect is less than expected for job congestion due to influences other than the main cause of the congestion. In this modified example, by having multiple congestion judgment values, it is possible to make a congestion judgment corresponding to a deficiency in each condition. As a result, it is possible to expect the effect of issuing a more appropriate warning notification and reducing unnecessary congestion.

[0112] [Variation 1-5] In this embodiment, in S1406, condition A, which was last registered in the process arrival table 1209, is determined to be the main cause of the delay. However, it is also possible that the delay is determined to be due to some items arriving early, even though there is no problem with the process preceding the process in question. Figure 17 shows a flowchart after it is determined in S1402 that there is a missing condition. Note that the steps explained in Figure 14 are omitted.

[0113] In S1701, the arrival time 1345 of the condition registered first in the process arrival table 1209 is acquired. In this modified example, the condition registered first is condition 1. The arrival time 1345 of condition 1 is compared with the arrival time 1345 of other conditions to confirm whether it is appropriate. Various methods can be considered for determining whether it is appropriate. A designated time is determined in advance, and if the arrival time 1345 registered next to condition 1 arrives after the designated time has elapsed and the time from that to the arrival time 1345 of condition A is within the designated time, it is considered to be inappropriate, but is not limited to this. For example, if the above-mentioned condition is met, but there is a reason that the production was intentionally made earlier in consideration of the work process of the entire factory, it is determined to be appropriate. If it is appropriate, the process proceeds to S1406, and if it is not appropriate, the process proceeds to S1702.

[0114] In S1702, the main stay count 1352 is recorded in the corresponding stay cause 1351 in the process stay table 1210 corresponding to the process preceding the condition 1.

[0115] <Effects of Modification 1-5> In this embodiment, a case where an item arrives early is assumed. In the first embodiment, the last-arrival condition is focused on. However, as described above, there are cases where focusing on the last-arrival condition is insufficient. In this modified example, by also checking the first-arrival condition, a configuration can be adopted in which the warning of the previous process is delayed, making it possible to perform a more optimal warning notification.

[0116] [Variation 1-6] In this embodiment, in S1406, the condition A last registered in the process arrival table 1209 is determined as the main cause of the congestion. Also, in S1407, if a certain amount of the main causes of the congestion can be acquired, in S1408, the congestion judgment value is changed. However, it can be assumed that it is better to notify additional information at the time of the congestion judgment depending on each process or operator.

[0117] 18 shows a configuration for acquiring additional information as an additional flow from S1406 to S1408. Note that the steps explained in FIG. 14 are omitted.

[0118] In S1801, the work time when work is started is obtained. FIG. 19 shows worker work progress tables 1901, 1902. This table includes user 1911, level 1912, and work time 1913. Level 1912 indicates the work level of the worker. In this example, the levels are divided into two stages, ordinary and skilled, but the names and number of stages are not limited to these. Based on the table information, an analysis is performed to see if there is a difference in work time between workers at each level. The existence of a difference can be determined by, for example, whether there is a difference of a specified amount of time in the average work time of workers at each level, but is not limited to this.

[0119] In S1802, if it is determined that there is a difference in the work time, a notification is issued to encourage the work of the worker with a higher level in the process. The notification method is assumed to be a display of a message, but is not limited to this, and various methods are also assumed, such as changing an icon or sending a notification only to a specified terminal.

[0120] <Effects of Modification 1-6> In this modification, a warning notification is assumed to be given with attention to the level of the worker, so that a warning notification can be given to an appropriate worker.

[0121] According to the embodiment described above, the threshold value used for stagnation determination can be varied depending on the cause of past stagnation, thereby making it possible to issue a warning notification at an appropriate timing for eliminating the stagnation.

[0122] The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a 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 implements one or more of the functions.

[0123] The disclosure of this embodiment includes the following management system, management method, and program.

[0124] (Item 1) A tag capable of contactlessly reading information is provided so as to be movable together with a deliverable in a device corresponding to a step constituting a workflow; A detection means for detecting the tag arranged in association with the device; A management means for managing the progress of steps in the workflow; a notification means for specifying the number of jobs in the process based on a result of detection of the tag by the detection means and the workflow, and for issuing a warning notification when the specified number of jobs in the process exceeds a predetermined value; A management system which makes the predetermined value variable based on a cause of a job being held up in the process.

[0125] (Item 2) 2. The management system according to item 1, wherein the cause of the delay includes at least a delay in arrival of a worker.

[0126] (Item 3) 3. The management system according to item 1 or 2, wherein the cause of the delay includes at least a processing delay in a process preceding the process.

[0127] (Item 4) 4. The management system according to any one of items 1 to 3, wherein the detection means is provided in association with a device corresponding to each of a plurality of steps constituting the workflow.

[0128] (Item 5) 5. The management system according to any one of items 1 to 4, wherein the tag is attached to a box capable of storing the deliverable.

[0129] (Item 6) 5. The management system according to any one of items 1 to 4, wherein the tag is attached to a medium indicating a procedure of the workflow.

[0130] (Item 7) 7. The management system according to any one of items 1 to 6, wherein the device is an offline post-processing device.

[0131] (Item 8) The image forming apparatus further includes an acquisition unit for acquiring a result of reading the code information printed on the printed matter output by the image forming apparatus and a result of reading the tag, The management system according to any one of items 1 to 7, characterized in that the workflow job and the tag are associated with each other based on the result of reading the code information and the result of reading the tag acquired by the acquisition means.

[0132] (Item 9) 9. The management system according to any one of items 1 to 8, wherein the tag is an RFID (Radio Frequency Identification) tag.

[0133] (Item 10) A management method executed in a management system including a tag capable of reading information in a non-contact manner, the tag being provided so as to be movable together with a deliverable in a device corresponding to a process constituting a workflow, the management system including a detection means for detecting the tag provided in association with the device, the method comprising: a management process for managing the progress of the processes in the workflow; a notification step of specifying the number of jobs waiting in the process based on the result of detection of the tag by the detection means and the workflow, and issuing a warning notification when the specified number of jobs waiting in the process exceeds a predetermined value; A management method comprising making the predetermined value variable based on a cause of a job being held up in the process.

[0134] (Item 11) 11. A program for causing a computer to execute each step of the management method according to item 10.

Claims

1. A tag capable of reading information in a non-contact manner is provided so as to be movable together with a deliverable in a device corresponding to a step constituting a workflow; a detection means for detecting the tag arranged in association with the device; A management means for managing the progress of steps in the workflow; a notification means for specifying the number of jobs in the process based on a result of detection of the tag by the detection means and the workflow, and for issuing a warning notification when the specified number of jobs in the process exceeds a predetermined value; A management system which makes the predetermined value variable based on a cause of a job being held up in the process.

2. 2. The management system according to claim 1, wherein the cause of the delay includes at least a delay in arrival of a worker.

3. 2. The management system according to claim 1, wherein the cause of the delay includes at least a processing delay in a process preceding the process.

4. 2. The management system according to claim 1, wherein the detection means is provided in association with a device corresponding to each of a plurality of steps constituting the workflow.

5. 2. The management system according to claim 1, wherein the tag is attached to a box capable of storing the deliverable.

6. 2. The management system according to claim 1, wherein the tag is attached to a medium indicating a procedure of the workflow.

7. 2. The management system according to claim 1, wherein the device is an offline post-processing device.

8. The image forming apparatus further includes an acquisition unit for acquiring a result of reading the code information printed on the printed matter output by the image forming apparatus and a result of reading the tag, 2. The management system according to claim 1, wherein the workflow job and the tag are associated with each other based on the result of reading the code information and the result of reading the tag acquired by the acquisition unit.

9. 2. The management system according to claim 1, wherein the tag is a radio frequency identification (RFID) tag.

10. A management method executed in a management system including a tag capable of reading information in a non-contact manner, the tag being provided so as to be movable together with a deliverable in a device corresponding to a process constituting a workflow, the management system including a detection means for detecting the tag provided in association with the device, the method comprising: a management process for managing the progress of the processes in the workflow; a notification step of specifying the number of jobs waiting in the process based on the result of detection of the tag by the detection means and the workflow, and issuing a warning notification when the specified number of jobs waiting in the process exceeds a predetermined value; A management method comprising making the predetermined value variable based on a cause of a job being held up in the process.

11. A program for causing a computer to execute each step of the management method according to claim 10.

Images