Management device, method for controlling management device, program, and storage medium

Abstract

To prevent a situation where, when an MFP and a DFE connected to the MFP are connected to the same network, operation information on actually one MFP is displayed as if it is operation information on separate MFPs.SOLUTION: An information collection PC 104 performs a search in a network 106, and when an MFP 101 and a DFE 102 connected to the MFP 101 and transmitting print data to the MFP 101 are found out through the search, collects and stores operation information from any one of the MFP 101 and the DFE 102.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to operation management of a system in which an image processing device and a control device that is connected to the image processing device and transmits print data to the image processing device are connected to the same network. [Background technology]

[0002] In recent years, many image processing devices such as printers, scanners, fax machines, and multi-function printers (hereinafter referred to as "MFPs") that combine these functions have become equipped with network communication functions. MFPs with communication functions communicate with servers and PCs on the network, enabling functions such as sending scanned data from the MFP to the PC.

[0003] On the other hand, for professional use products aimed at printing companies and design offices, there is a demand for more advanced print control than office products, such as image processing and print job scheduling. This type of advanced print control is possible by connecting a control device called a Digital Front End controller (hereinafter referred to as "DFE") to the MFP. Printing companies and design offices often connect DFEs to their MFPs.

[0004] The DFE and MFP each have device information in their respective control units, but there is a demand for centralized management of the device information that is managed in a distributed manner by the respective control units of the DFE and MFP. Patent Document 1 proposes a technique in which, in a configuration in which a DFE connected to an MFP is connected to a network, the DFE acquires device information from the MFP in response to a request from a device management device, merges it with its own device information, and responds. This makes it possible to centralize management of the device information that is managed in a distributed manner by the DFE and MFP. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2020-091370 A Summary of the Invention [Problem to be solved by the invention]

[0006] However, there may be a case where a DFE is connected to the MFP and both the MFP and the DFE are connected to the same network. In this case, operation information is collected from both the MFP and the DFE and transmitted to the management device. For this reason, the management device manages the MFP and the DFE as two separate devices. Although the device whose operation status is to be managed is a single MFP, there is an issue in that the user sees two identical devices.

[0007] The present invention has been made to solve the above problems, and has an object to provide a mechanism that enables a management device to manage the operation of an image processing device without duplication in a system in which an image processing device and a control device that is connected to the image processing device and transmits print data are connected to the same network. [Means for solving the problem]

[0008] The present invention comprises a management means for managing operation information collected from devices found by searching a network, and a control means for generating information indicating the operation status of the devices based on the operation information managed by the management means, wherein when operation information of an image processing device and operation information of a control device connected to the image processing device and transmitting print data to the image processing device are collected, the management means associates and manages the operation information, and the control means combines the associated and managed operation information of the image processing device and the operation information of the control device, and generates information indicating the operation status of a device based on the combined operation information. Effect of the Invention

[0009] According to the present invention, in a system in which an image processing device and a control device that is connected to the image processing device and transmits print data to the image processing device are connected to the same network, a management device can manage the operation of the image processing device without duplication. This makes it possible to prevent operation information of a single MFP from being displayed as if it were operation information of separate MFPs. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing an example of a connection environment of an apparatus operation management system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram showing an example of the hardware configuration of an MFP and a DFE. [Diagram 3] FIG. 2 is a block diagram showing an example of the hardware configuration of an information collection PC. [Figure 4] FIG. 2 is a block diagram showing an example of a hardware configuration of the device operation management apparatus. [Diagram 5] FIG. 2 is a block diagram showing an example of the configuration of a processing function of an information collection PC. [Figure 6] FIG. 2 is a block diagram showing an example of a configuration of a processing function of the device operation management apparatus; [Figure 7] 4A to 4C are diagrams showing data structures of a device list, transmission operation information, and operation information according to the first embodiment. [Figure 8] 6 is a flowchart showing an example of processing of an information collection PC in the first embodiment. [Figure 9] FIG. 13 is a diagram showing an example of a setting screen for an information collection PC according to the second embodiment. [Figure 10] 11 is a flowchart showing an example of a process of an information collection PC in the second embodiment. [Figure 11] FIG. 13 is a diagram showing an example of an operation status screen in the third embodiment. [Figure 12] FIG. 13 is a diagram showing an example of detailed information display of a device according to the third embodiment. [Figure 13A] 4A to 4C are diagrams showing data structures of a device list and transmission operation information according to the first embodiment. [Figure 13B] FIG. 4 is a diagram showing a data structure of operation information according to the first embodiment. [Figure 14A] 13 is a flowchart showing an example of a process of an equipment operation management device according to the third embodiment. [Figure 14B] 13 is a flowchart showing an example of a process of an equipment operation management device according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the configurations shown in the following embodiments are merely examples, and the present invention is not limited to the configurations shown in the drawings.

[0012] [First embodiment] <Configuration of the equipment operation management system> FIG. 1 is a diagram showing an example of a connection environment of an apparatus operation management system according to an embodiment of the present invention. 1, the device operation management system of this embodiment (hereinafter also referred to as "this system") includes an MFP (Multi Function Printer) 101 and a DFE (Digital Front End controller) 102. The system also includes a client PC 103, an information collection PC 104, and a device operation management device 105.

[0013] The MFP 101, the DFE 102, the client PC 103, and the information collection PC 104 are communicably connected via a network 106. The DFE 102 and MFP 101 are connected via an internal interface 107 that transfers images at high speed.

[0014] In this system, a print job is transmitted from client PC 103 to DFE 102 via network 106. DFE 102 sequentially performs rasterization processing on the print jobs received from client PC 103 via network 106, and transfers the rasterized image data (also called print data) to MFP 101 via internal interface 107. MFP 101 performs necessary processing on the rasterized image data received from DFE 102 via internal interface 107, and prints it out on actual paper.

[0015] It is also possible for client PC 103 to send print jobs for offices to MFP 101 via network 106. MFP 101 sequentially processes print jobs received from client PC 103 and prints out the print jobs on actual paper using marking engine 220 (FIG. 2). MFP 101 can also perform copying (copy job) using a connected scanner and send scanned results to client PC 103 (send job). MFP 101 can also print facsimile (hereinafter "fax") data received via a telephone line (not shown) (fax job).

[0016] The DFE 102 communicates with the MFP 101, and acquires and manages information such as the serial number and product name of the MFP 101. The DFE 102 also manages job execution information that has been executed by itself.

[0017] The information collection PC 104 is an information processing device that searches for devices connected to the network 106 and registers them in a device list, which will be described later. The information collection PC 104 collects and stores information on the devices registered in the device list via the network 106. The information collection PC 104 also transmits the collected and stored information to the device operation management device 105.

[0018] The device operation management apparatus 105 displays information that printing administrators view daily for the purpose of managing the productivity and operation rate of multiple MFPs. The device operation management apparatus 105 has means for receiving information from the information collection PC 104, storing it, and preparing to display the device operation status. The device operation management apparatus 105 may be realized by a single computer or by multiple computers. The device operation management apparatus 105 may be configured to be realized using, for example, cloud services or the like.

[0019] The client PC 103 accesses the device operation management apparatus 105 and displays the information prepared for display by the device operation management apparatus 105. As a result, the printing administrator can view the operation status of the desired device. The client PC 103 is, for example, various information processing devices such as a personal computer, a tablet terminal, and a smartphone.

[0020] <Device configurations of MFP101 and DFE102> FIG. 2 is a block diagram showing an example of the hardware configuration of MFP101 and DFE102. MFP101 has a controller unit including a CPU 211, a RAM 212, and an HDD 213. Further, MFP101 includes a marking engine 220, a scanner 221, an image processing unit 216, an image processing I / F unit 217, a device I / F unit 218, and a network I / F unit 214. Various programs are stored in the HDD 213 or the like, and are read into the RAM 212 and executed by the CPU 211 as needed.

[0021] DFE102 has a controller unit including a CPU 201, a RAM 202, and an HDD 203. Further, DFE102 includes an image processing unit 205, an image processing I / F unit 206, and a network I / F unit 204. Various programs are stored in the HDD 203 or the like, and are read into the RAM 202 and executed by the CPU 201 as needed. DFE102 functions as a control device that provides functions to MFP101. As described above, a system in which MFP 101 and DFE 102 are connected can be said to be a system in which a plurality of control units are connected to an operating device. Both the MFP 101 and the DFE 102 may include a display / operation device (not shown) as necessary.

[0022] <Device configuration of the information collection PC 104 and the device operation management device 105> FIG. 3 is a block diagram showing an example of a hardware configuration of an information collection PC. The information collection PC 104 has a CPU 301, a RAM 302, a HDD 303, and a network I / F unit 304. The hardware such as the CPU 301, the RAM 302, and the HDD 303 constitute a so-called computer. Various programs are stored in the HDD 303, etc., and are read by the CPU 301 into the RAM 302 as necessary to be controlled and executed.

[0023] FIG. 4 is a block diagram showing an example of a hardware configuration of the device operation management device 105. As shown in FIG. The device operation management device 105 has a CPU 401, a RAM 402, a HDD 403, and a network I / F unit 404. The hardware such as the CPU 401, the RAM 402, the HDD 403, etc. constitute a so-called computer. Various programs are stored in the HDD 403, etc., and are called into the RAM 402 by the CPU 401 as necessary and are controlled and executed.

[0024] <Processing function configuration of information collection PC 104> FIG. 5 is a block diagram showing an example of the configuration of the processing functions of the information collection PC 104. As shown in FIG. Each software module of the information collection PC 104 shown in Fig. 5 is stored in the HDD 303 of the information collection PC 104, and functions by being read into the RAM 302 as necessary and being controlled and executed by the CPU 301. Note that, in the information collection PC 104, one CPU 302 executes each process shown in the flowcharts described below, but other configurations are also possible. For example, each process shown in the flowcharts described below can be executed by multiple processors and memories working together. Also, some processes such as sending and receiving data are realized in cooperation with hardware circuits such as a communication interface.

[0025] The network management unit 501 uses the network I / F unit 304 to communicate with devices connected to the network 106, such as the DFE 102, the MFP 101, and the client PC 103, via the network 106, and with a device operation management device 105 on the cloud.

[0026] The device discovery processing unit 502 is a software module that searches for devices connected to the network 106, and is executed, for example, periodically, when a new setting is made, or when a new device is added, and registers operational management target devices on the network in an device list described later.

[0027] The device operation information collection processing unit 503 is a software module that collects operation information from devices subject to operation management registered in the device list. The collected operation information is stored in a data storage unit 505. The data storage unit 505 stores information on the HDD 303 of the information collection PC 104, but may store information in a predetermined storage area such as the RAM 302 or an external storage area. The device operation information transmission processing unit 504 is a software module that periodically transmits the device operation information collected by the device operation information collection processing unit 503 and stored in the data storage unit 505 to the device operation management device 105 .

[0028] <Processing Functional Configuration of the Equipment Operation Management Device 105> FIG. 6 is a block diagram showing an example of the configuration of the processing functions of the equipment operation management device 105. As shown in FIG. Each software module of the device operation management device 105 shown in Fig. 6 is stored in the HDD 403 of the device operation management device 105, and functions by being read into the RAM 402 as necessary and being controlled and executed by the CPU 401. Note that the device operation management device 105 is configured such that one CPU 401 executes each process shown in the flowcharts described below, but other configurations are also possible. For example, each process shown in the flowcharts described below can be executed by multiple processors and memories working together. Also, some processes such as data transmission and reception are realized in cooperation with hardware circuits such as a communication interface.

[0029] A network management unit 601 uses the network I / F unit 404 to communicate with the information collection PC 104 and the client PC 103, as well as with devices on the Internet. The operation information reception processor 602 is a software module that receives operation information transmitted from the information collection PC 104 . The device operation information management unit 603 is a software module that appropriately manages the device operation information received by the operation information reception processing unit 602 and stores it in a data storage unit 605. Note that the data storage unit 605 stores information on the HDD 403 of the device operation management device 105, but may store the information in a predetermined storage area such as the RAM 402 or an external storage area.

[0030] The device operation information display processing unit 604 is a software module for displaying the device operation information managed by the device operation information management unit 603 on the client PC 103 or a device on the Internet. The device operation information display processing unit 604 generates information indicating the device operation status based on the device operation information managed by the device operation information management unit 603 (prepares a display screen indicating the device operation status).

[0031] FIG. 7A is a diagram showing an example of the data structure of a device list managed by the device operation information management unit 603 in the first embodiment. The device list is made up of information on multiple devices to be managed (hereinafter referred to as "device 702"). Each device 702 is made up of device information 703 and MFP information 705. The device information 703 stores information 704 such as the product name and serial number of the relevant device. The MFP information 705 stores information 706 such as the IP address and MAC address of the relevant MFP.

[0032] FIG. 7B is a diagram showing an example of the data structure of the transmission operation information 711 transmitted from the MFP 101 to the information collection PC 104. As shown in FIG. The transmission performance information 711 includes information 712 such as the serial number, date and time, product name, counter information, job type, job type details, job count information since the previous transmission, and print count information for each job.

[0033] FIG. 7C is a diagram showing an example of a data structure of operation information managed by the device operation information management unit 603 in the first embodiment. Operation information 721 is managed for each device serial number 722, and is made up of a total number of jobs 724 and a total number of pages 725 for each job type 723. The job types 723 include print jobs, copy jobs, fax jobs, and scan jobs.

[0034] 8 is a flowchart showing an example of processing for searching for devices on a network and registering them in a device list in the device searching processing unit 502 in the information collection PC 104 in the first embodiment. That is, the processing of this flowchart is realized by the CPU 301 of the information collection PC 104 loading a program stored in the HDD 303 or the like into the RAM 302 as necessary and executing it.

[0035] In S801, the device search processing unit 502 searches for devices via the network 106 connected to the network I / F unit 304. For example, the device search processing unit 502 broadcasts a search packet. Note that multicast may be used instead of broadcast. Next, in S 802 , the device search processing unit 502 acquires device information of the device that responded to the search in S 801 above, and stores the information in the memory 302 or HDD 303 via the data storage unit 505 .

[0036] Next, in S803, the device discovery processing unit 502 determines whether the corresponding device information has been registered in the device list. If the device information has been registered (Yes in S803), the device discovery processing unit 502 ends the processing of this flowchart.

[0037] On the other hand, if the device has not yet been registered (No in S803), the device discovery processing unit 502 advances the process to S804. In S804, the device discovery processing unit 502 judges whether the device information acquired in S802 is device information of an MFP. If the device information is not device information of an MFP (No in S804), the device discovery processing unit 502 ends the process of this flowchart without adding the device information acquired in S802 to the device list.

[0038] On the other hand, if it is determined that the information is device information of an MFP (Yes in S804), the device discovery processing unit 502 advances the process to S805. In S805, the device discovery processing unit 502 adds the device information acquired in S802 to the device list. In detail, the device discovery processing unit 502 adds information 702 to 706 to the device list 701 configured as shown in Fig. 7(a) based on the device information acquired in S802. After the process of S805, the device discovery processing unit 502 ends the process of this flowchart.

[0039] The device list registered as above is stored in the data storage unit 505 and transmitted to the device operation management device 105, and managed by the device operation information management unit 603 of the device operation management device 105. The device operation information collection processing unit 503 of the information collection PC 104 collects operation information such as that shown in FIG. 7(b) from the devices registered in the above-mentioned device list, and stores the collected operation information in the data storage unit 505. The device operation information transmission processing unit 504 transmits the operation information stored in the data storage unit 505 to the device operation management device 105. The device operation information management unit 603 of the device operation management device 105 manages the operation information of the MFP 101 (including the serial number of the MFP) as shown in FIG. 7(b) received from the information collection PC 104, in a data structure as shown in FIG. 7(c) based on the serial number.

[0040] As described above, according to the first embodiment, in a printing system in which an MFP and a DFE are connected to the same network, it is possible for an apparatus operation management device to manage the operation status of the same MFP without duplication. This makes it possible to prevent operation information of a single MFP from being displayed as if it were operation information of separate MFPs.

[0041] Second Embodiment In the above first embodiment, a configuration has been described in which a searched MFP is registered in a device list, and a DFE connected to the MFP is controlled so as not to be registered in the device list, thereby making it possible to manage operation information without duplication. Note that some users may wish to manage the operation information of DFEs in detail, and an embodiment that satisfies this wish will be described below.

[0042] 9 is a diagram showing an example of a setting screen for the information collection PC 104 in the second embodiment. This screen is actually displayed on the display unit of the client PC 103 by accessing the information collection PC 104 from the client PC 103, and is instructed by a user such as a printing manager.

[0043] Setting screen 901 is a screen that allows the user to select and set in advance the source from which device operation information is acquired. The user selects the source from which device operation information is acquired using radio buttons 902 and 903. When acquiring device operation information from MFP 101, radio button 902 is selected. On the other hand, when acquiring device operation information from DFE 102, radio button 902 is selected. By selecting either radio button 902 or 903 and pressing a "Yes" button 904, the settings on setting screen 901 can be validated and setting screen 901 can be closed. This setting is stored in HDD 303 of information collection PC 104. Also, by pressing a "Cancel" button 905, the settings on setting screen 901 can be invalidated and setting screen 901 can be closed.

[0044] 7A is read as "device information acquisition source information." When the DFE 102 is set as the device operation information acquisition source on the setting screen 901, the transmission operation information transmitted from the DFE 102 to the information collection PC 104 includes the serial number of the MFP 101, which the DFE 102 acquires from the MFP 101 and manages.

[0045] 10 is a flowchart showing an example of processing for searching for devices on a network and registering them in a device list in the device searching processing unit 502 in the information collection PC 104 in the second embodiment. That is, the processing of this flowchart is realized by the CPU 301 of the information collection PC 104 loading a program stored in the HDD 303 or the like into the RAM 302 as necessary and executing it.

[0046] First, steps S1001 to S1003 are the same as steps S801 to S803 in FIG. 8, and therefore a description thereof will be omitted. In S1004, the device discovery processing unit 502 determines from the device information acquired in S1002 whether the device information is device information of an MFP or device information of a DFE, and determines whether the device corresponding to the device information matches the device operation information acquisition source set on screen 901 in Fig. 9. If they do not match (No in S1004), the device discovery processing unit 502 ends the processing of this flowchart without adding the device information acquired in S1002 above to the device list.

[0047] On the other hand, if it is determined that the device corresponding to the device information acquired in S1002 matches the device information acquisition source (Yes in S1004), the device discovery processing unit 502 advances the process to S1005. In S1005, the device discovery processing unit 502 adds the device information acquired in S1002 to the device list. In detail, the device discovery processing unit 502 adds information 702 to 706 to the device list 701 configured as described above, based on the device information acquired in S1002. After the process of S1005, the device discovery processing unit 502 ends the process of this flowchart.

[0048] The device list registered as above is stored in the data storage unit 505 and transmitted to the device operation management device 105, where it is managed by a device operation information management unit 603 of the device operation management device 105. Furthermore, the device operation information collection processing unit 503 of the information collection PC 104 collects operation information from the devices registered in the above-mentioned device list, and the device operation information transmission processing unit 504 transmits the collected operation information to the device operation management device 105. The device operation information management unit 603 of the device operation management device 105 manages the operation information (including the serial number of the MFP) of the MFP 101 or DFE 102 received from the information collection PC 104 in a data structure as shown in FIG. 7(c) based on the serial number.

[0049] As described above, according to the second embodiment, it is possible to manage operation information for the same MFP without duplication, using operation information acquired from a device selected and set as a device information acquisition source. Note that by a printing manager or the like selecting and setting a DFE as a device information acquisition source, it becomes possible to manage the operation information of the DFE in detail.

[0050] Third Embodiment In the first and second embodiments, when a network is searched and an MFP and a DFE connected to the MFP are found, operation information is collected from either the MFP or the DFE. Then, the device operation management device 105 uses the collected information to manage the device operation information. That is, a configuration has been described in which operation information collected from either the MFP or the DFE is used to manage operation information without duplication for the same MFP. Since the DFE and the MFP execute different jobs, there has been a demand from users who wish to perform detailed analysis of the number of printed sheets and the number of jobs to manage the operation information of the MFP and the DFE in an integrated manner. In this embodiment, a configuration will be described in which the operation information of the MFP and the DFE is managed in an integrated manner. In this embodiment, the information collection PC 104 collects operation information from both the MFP 101 and the DFE 102.

[0051] FIG. 11 is a diagram showing an example of an operational status screen on which display contents prepared in the device operational information display processing unit 604 according to the third embodiment are displayed on the client PC 103. In FIG. On operation status screen 1101, a device list is displayed in device list 1102 on the left side of the screen. MFP 101 and DFE 102 are recognized as separate devices on the network, but in this device list, information is displayed as one device. In the example of Fig. 11, "AB-Cx00" displayed at the top of device list 1102 is a device made up of MFP 101 and DFE 102, but is displayed as one device. The MFP 101 and DFE 102 are connected by internal interface 107, and each transmits transmission operation information including the same serial number to information collection PC 104. The consumables information display 1103 displays the remaining amount of consumables.

[0052] When any device is selected from the device list displayed in the device list 1102 and specified (for example, by double-clicking), detailed information about that device is displayed, for example, as shown in 1204 in FIG.

[0053] FIG. 12 is a diagram showing an example of detailed device information display in the third embodiment. In the detailed information 1204, the total number of print jobs and the number of pages are displayed by combining (integrating) information on the execution of the jobs by both the MFP 101 and the DFE 102 that constitute the device selected in the device list 1102.

[0054] 13A and 13B are diagrams showing examples of data structures of a device list, transmission operation information, and operation information according to the third embodiment. Hereinafter, Fig. 13A and Fig. 13B will be collectively referred to simply as "Fig. 13".

[0055] FIG. 13A shows an example of the data structure of a device list managed by the device operation information management unit 603. As shown in FIG. The device list 1301 is made up of information on a plurality of devices (hereinafter, “devices 1302”). Each device 1302 is made up of device information 1303, MFP information 1305, and DFE information 1307.

[0056] Device information 1303 stores device information 1304 common to the MFP and DFE, such as a serial number or engine name acquired from the MFP or DFE. For counter information, more accurate information acquired from the MFP 101 may be used. MFP information 1305 stores MFP-specific information 1306, such as the IP address and MAC address of the MFP. Similarly, DFE information 1307 stores DFE-specific information 1308, such as the DFE product name, IP address, and MAC address of the DFE.

[0057] In addition, the device discovery processing unit 502 in the third embodiment searches for devices on the network 106 (similar to S801 in FIG. 8), acquires device information of devices that have responded (similar to S802), and stores the information in the memory 302 or HDD 303 via the data storage unit 505. Furthermore, if the device information has not been registered in the device list (similar to S803), the device discovery processing unit 502 adds information 1302 and subsequent items to the device list 1301 configured as shown in FIG. 13(a) based on the acquired device information. At this time, if the acquired device information is device information of an MFP, MFP information 1305-1306 is added, and if the acquired device information is device information of a DFE, DFE information 1307-1308 is added.

[0058] The device list registered as above is stored in the data storage unit 505 and transmitted to the device operation management device 105, where it is managed by the device operation information management unit 603 of the device operation management device 105. In addition, the device operation information collection processing unit 503 of the information collection PC 104 collects operation information from the devices registered in the above-mentioned device list, and the device operation information transmission processing unit 504 transmits the collected operation information to the device operation management device 105.

[0059] FIG. 13B shows an example of the data structure of the transmission operation information 1311 transmitted from the MFP 101 or the DFE 102 to the information collection PC 104. In FIG. The transmission performance information 1311 includes information 1312 such as a serial number, date and time, product name, counter information, job type, job type details, and number of printed sheets for each job. The serial number included in the transmission performance information transmitted from the DFE 102 to the information collection PC 104 corresponds to the serial number of the MFP 101 that the DFE 102 acquires from the MFP 101 and manages.

[0060] FIG. 13C shows an example of the data structure of the operation information managed by the device operation information management unit 603. The operation information 1321 is managed for each piece of information about an apparatus (hereinafter, “apparatus 1322”). Each apparatus 1322 is made up of apparatus information 1323, MFP operation information 1325, and DFE operation information 1336.

[0061] In the device information 1323, information 1324 such as serial numbers, counter information, and expendable information is managed.

[0062] The MFP operation information 1325 is based on operation information collected from the MFP and is made up of the total number of jobs and the total number of pages for each job type, such as print jobs 1326, copy jobs 1333, scan jobs 1334, and FAX jobs 1335.

[0063] Note that the print job 1326 is further classified into a DFE job 1327 and an MFP job 1328. The DFE job 1327 is print job information input from the DFE 102 to the MFP 101. The DFE job 1327 is made up of a total job number 1329 and a total page number 1330. Similarly, the MFP job 1328 is made up of a total job number 1331 and a total page number 1332.

[0064] The DFE performance information 1336 is based on performance information collected from the DFE. The DFE performance information 1336 is made up of a print job 1337 and a scan job 1340. A print job 1337 is composed of a print detailed type PDF (Portable Document Format) job 1338 and a PostScript job 1339, and the total number of jobs and the total number of pages are managed for each job.

[0065] The scan job 1334 manages the total number of jobs and the total number of pages for each job as combined information of scan jobs performed by the MFP and scan jobs performed in response to instructions from the DFE. At least the DFE job 1327 and the print job 1337 include update date and time information (not shown).

[0066] The device operation information management unit 603 of the device operation management device 105 associates the operation information (including the serial numbers of the MFPs) of the MFP 101 and DFE 102 as shown in Fig. 13(b) received from the information collection PC 104 with the serial numbers and manages them in a data structure as shown in Fig. 13(c). At this time, it is assumed that the serial numbers included in the operation information collected from the MFP 101 and the operation information collected from the DFE 102 match. That is, the operation information of the MFP 101 and the operation information of the DFE 102 are managed in association with each other using the serial numbers as a key.

[0067] 14A and 14B are flowcharts showing an example of processing for creating operation information to be displayed on the client PC 103 in the device operation management device 105 in the third embodiment by the device operation information display processing unit 604. The processing shown in Fig. 14A and 14B is realized by the CPU 401 of the device operation management device 105 loading a program stored in the HDD 403 or the like into the RAM 402 as necessary and executing it.

[0068] First, in S1401, the device operation information display processing unit 604 requests the device operation information management unit 603 to acquire operation information (MFP operation information 1325 and DFE operation information 1336) of any device in the device list. Hereinafter, the device from which operation information is acquired is referred to as the “corresponding device.”

[0069] In S1402, the device operation information display processing unit 604 checks whether operation information has been acquired up to the end of the device list. If operation information has not been acquired up to the end of the device list, that is, if there is a device in the device list for which operation information has not been acquired yet (No in S1402), the device operation information display processing unit 604 proceeds to S1403. In this case, the operation information of the device requested in S1401 can be acquired.

[0070] In S1403 to S1405, the device operation information display processing unit 604 creates display information by synthesizing the MFP operation information 1325 and the DFE operation information 1336 acquired in S1401 above. Each step will be explained below.

[0071] In S1403, the device operation information display processing unit 604 creates print job operation display information for the relevant device using the operation information acquired in S1401 above. Details of this process will be described with reference to FIG. 14B. Next, in S1404, the device operation information display processing unit 604 creates scan job operation display information for the relevant device using the operation information acquired in S1401 above. Next, in S1405, the device operation information display processing unit 604 creates operation display information for other jobs such as the FAX job 1335 of the relevant device using the operation information acquired in S1401 above.

[0072] Next, in S1406, the device operation information display processing unit 604 requests the device operation information management unit 603 to acquire the operation information of the next device from the device operation information management unit 603, and moves the process to S1402. Here, if operation information has already been obtained up to the end of the device list, that is, if there is no information about devices in the device list for which operation information should be obtained (Yes in S1402), the device operation information display processing unit 604 terminates the processing of this flowchart.

[0073] The operation display information generated (prepared for display) by the device operation management device 105 as described above is transmitted to the client PC 103 in response to a request from the client PC 103 and is displayed on the client PC 103 .

[0074] FIG. 14B is a flowchart showing details of the print job operation table information creation process in S1403 of FIG. 14A. First, in S1411, the device operation information display processing unit 604 compares the DFE jobs 1327 in the MFP operation information 1325 with the print jobs 1337 in the DFE operation information 1336 to confirm whether they match. Here, if the total number of jobs and the total number of pages in the DFE jobs 1327 in the MFP operation information 1325 and the print jobs 1337 in the DFE operation information 1336 are equal, it is determined that they match. If they match (Yes in S1411), the device operation information display processing unit 604 advances the process to S1414.

[0075] In S1414, the device operation information display processing unit 604 uses the information of the print job 1337 in the DFE operation information 1336. In this case, in the next S1415, the device operation information display processing unit 604 adds up the MFP job 1328 in the MFP operation information 1325 and the print job 1337 in the DFE operation information 1336 to obtain total print job operation information for the entire device. By performing this processing, it is possible to integrate the results of print jobs executed by the MFP alone, without going through the DFE, with the printing results managed by the DFE. For example, it becomes possible to correctly count the results of status prints that print the status information of the MFP, and the results of print jobs that the MFP received directly from a mobile terminal or the like and printed.

[0076] On the other hand, if the DFE job 1327 in the MFP operation information 1325 and the print job 1337 in the DFE operation information 1336 do not match (No in S1411), the device operation information display processing unit 604 advances the process to S1412.

[0077] In S1412, the device operation information display processing unit 604 compares the times when the operation information was received from the device for the DFE job 1327 in the MFP operation information 1325 and the print job 1337 in the DFE operation information 1336, and determines which information is the latest. If the print job 1337 in the DFE operation information 1336 is newer (DFE in S1412), the device operation information display processing unit 604 advances the process to S1414.

[0078] On the other hand, if the DFE job 1327 in the MFP operation information 1325 is newer (if MFP in S1412), the device operation information display processing unit 604 advances the process to S1413. In S1413, the device operation information display processing unit 604 uses the information of the DFE job 1327 in the MFP operation information 1325. In this case, in the next S1415, the device operation information display processing unit 604 adds up the MFP job 1328 in the MFP operation information 1325 and the DFE job 1327 in the MFP operation information 1325 to obtain total print job operation information of the entire device.

[0079] Next, in S 1416 , the device operation information display processing unit 604 acquires detailed job information (information on the PDF job 1338 and PostScript job 1339 ) in the print job 1337 in the DFE operation information 1336 .

[0080] Next, in S1417, the device operation information display processing unit 604 calculates the percentage of each job from the print job operation total calculated in S1415 above and the detailed job information acquired in S1416 above, and creates information required for display. At this time, a display screen is generated so that the percentage of each job is displayed in descending order of the number of jobs. In the detailed display screen, a display screen is generated so that the percentages of PDF jobs 1338 and PostScript jobs 1339 are also displayed. In addition, a display screen is generated so that the percentage of jobs that went through the DFE within the same job type and the percentage of jobs that were processed by the MFP without going through the DFE can be seen.

[0081] After the process of S1417, the device operation information display processing unit 604 ends the process of this flowchart. In this way, for the overlapping portion between the operation information of the MFP 101 and the operation information of the DFE 102, the operation information is synthesized (integrated) using either operation information.

[0082] As described above, in this embodiment, when displaying the type of printed job, the operation information of both the MFP and the DFE is combined and displayed. At this time, the number of copy jobs and the number of FAX jobs executed by the MFP are obtained from the MFP operation information. On the other hand, the print jobs executed by the DFE are obtained from the DFE operation information.

[0083] As described above, according to the third embodiment, in a printing system in which an MFP and a DFE are connected to the same network, the device operation management device can manage operation information for the same MFP without duplication and appropriately integrate and manage distributed job information. This makes it possible to prevent operation information for one MFP from being displayed as if it were operation information for separate MFPs.

[0084] Since the jobs executed by the DFE and the MFP are different, in order to perform a detailed analysis of the number of printed sheets and the number of jobs, both MFP operation information and DFE operation information are required. In this embodiment, both pieces of operation information are combined to create display information. This makes it possible to perform a detailed analysis of the number of printed sheets and the number of jobs.

[0085] In the above example, when information of the same job type, such as a print job, is present in both the MFP operation information and the DFE operation information, the information is added together to determine the total for that job type. However, whether or not information of the same job type in the MFP operation information and the DFE operation information is added together to determine the total may be switched by a user setting.

[0086] Furthermore, when information of the same PDL (Page Description Language) type is present in both the MFP operation information and the DFE operation information, these may be added together to obtain a total. Then, a display screen is generated to display each PDL job type in descending order of frequency. Furthermore, when a detailed display instruction is given, the ratio of jobs of each PDL type may be displayed. Also, the ratio of jobs that went through the DFE within a PDL type and the ratio of jobs that were processed by the MFP without going through the DFE may be displayed so that the user can see. Note that whether or not to add together information of the same PDL type in the MFP operation information and the DFE operation information may be switched by a user setting.

[0087] Furthermore, multiple applications may be prepared as the device operation information display processing unit 604, and whether or not to add up and the operation information used for display may differ for each application. For example, a first application controls the display of the operation status based on the sum of the MFP operation information and the DFE operation information. A second application controls the display of the operation status based on the MFP operation information in order to manage jobs executed by the MFP without going through the DFE. A third application requires management on a print job basis, and therefore controls the display of the operation status based on information on the DFE side. The client PC 103 can display the desired operation status by accessing the URL of the application for which the operation status is to be displayed.

[0088] In the above embodiments, the information collection PC 104 generates the device list and collects and transmits the operation information, but the same control may be performed by the MFP 101 or the DFE 102. In other words, the MFP 101 or the DFE 102 may have the function of the information collection PC 104 described above. In addition, the collection control of operation information provided by PC 104, the integrated management control of operation information provided by management device 105, the generation of screens related to the operation information, and the provision to client PCs may be realized as a single server or a single cloud service.

[0089] As described above, in a printing system in which the MFP 101 and DFE 102 are connected to the same network, the device operation management device 105 can perform operation management for the same MFP without duplication, and can integrate and manage distributed job information. In other words, duplicate printing devices will no longer be displayed, and the status of jobs executed separately by the MFP and DFE can be synthesized and displayed, reducing network communication charges. In other words, it becomes possible to appropriately manage the operating status of operating devices in a system in which multiple control units are connected to an operating device.

[0090] It goes without saying that the configurations and contents of the various data described above are not limited to those described above, and the data may have various configurations and contents depending on the application and purpose. Although one embodiment has been described above, the present invention can be embodied, for example, as a system, an apparatus, a method, a program, a storage medium, etc. Specifically, the present invention may be applied to a system composed of multiple devices, or may be applied to an apparatus composed of a single device. Furthermore, any combination of the above-described embodiments is also included in the present invention.

[0091] (Other embodiments) 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. Furthermore, the present invention may be applied to a system made up of a plurality of devices, or to an apparatus made up of a single device. The present invention is not limited to the above-mentioned embodiment, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and are not excluded from the scope of the present invention. In other words, the present invention includes all configurations that combine the above-mentioned embodiments and their modifications. [Explanation of symbols]

[0092] 101 MFP 102 DFE 103 Client PC 104 Information Gathering PC 105 Equipment operation management device

Claims

1. a management means for managing operation information collected from devices found by searching the network; a control unit that generates information indicating an operating status of the device based on the operating information managed by the management unit; the management means, when operation information of the image processing device and operation information of a control device connected to the image processing device and transmitting print data to the image processing device are collected, manages the operation information in association with each other; The management device is characterized in that the control means combines operation information of the image processing device and operation information of the control device that are managed in association with each other, and generates information indicating the operation status of a device based on the combined operation information.

2. The management device described in claim 1, characterized in that when the control means combines the operation information of the image processing device and the operation information of the control device, for any overlapping parts between the operation information of the image processing device and the operation information of the control device, it uses either of the operation information.

3. 3. The management device according to claim 2, wherein the control means uses the operation information of the control device for a portion where the operation information of the image processing device and the operation information of the control device overlap.

4. The management device according to claim 2, characterized in that, for any overlapping parts between the operation information of the image processing device and the operation information of the control device, the control means uses the latest operation information of either of the operation information for that part.

5. 5. The management device according to claim 1, further comprising a collection unit that acquires operation information of the image processing device from the image processing device and collects operation information of the control device from the control device.

6. The management device described in claim 5, characterized in that the control means generates information indicating the operating status of a device based on the combined operation information when identification information contained in the operation information of the image processing device collected by the collection means matches identification information contained in the operation information of the control device collected by the collection means.

7. A management device as described in any one of claims 1 to 6, characterized in that when information of a Digital Front End controller (DFE) job among print jobs included in the operation information of the image processing device matches information of a print job included in the operation information of the control device, the control means combines the operation information of the image processing device and the operation information of the control device.

8. A management device as described in any one of claims 1 to 6, characterized in that when the total number of jobs and the total number of pages indicated by the information of Digital Front End controller (DFE) jobs among the print jobs included in the operation information of the image processing device are equal to the total number of jobs and the total number of pages indicated by the information of print jobs included in the operation information of the control device, the control means combines the operation information of the image processing device with the operation information of the control device.

9. A method for controlling a management device, comprising: a storage step of storing, in a predetermined storage area, operation information collected from devices found by searching the network; generating information indicating an operational status of the device based on the operational information stored in the predetermined storage area; In the case where operation information of the image processing device and operation information of a control device that is connected to the image processing device and transmits print data to the image processing device are collected, the operation information is stored in association with each other in the predetermined storage area; A control method for a management device, characterized in that in the generation process, operation information of the image processing device and operation information of the control device stored in association with each other in the specified memory area are combined, and information indicating the operating status of a device is generated based on the combined operation information.

10. A program for causing a computer to function as each of the means of the management device according to any one of claims 1 to 8.

11. A computer-readable storage medium storing a program for causing a computer to function as each of the means of the management device according to any one of claims 1 to 8.

Images