JP2005038106A - Information management device, information management method, information management program and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce a burden of print log analysis processing in an information management device for managing print logs about printers. <P>SOLUTION: The information management device, which manages print logs of printing executed by printers or/and printing requested from printers by client devices of the printers, comprises a merged print log generation means for merging the plurality of print logs to generate merged print logs, and a merged print log management means for managing the merged print logs. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a server computer that manages a print log relating to a printing apparatus such as a printer, a copy, a facsimile, a multifunction peripheral, or a multifunction peripheral, an information management apparatus such as a personal computer, an information management method, an information management program, and a recording medium.
[0002]
[Prior art]
As a method for managing print logs related to printing devices such as printers, copiers, facsimiles, multifunction peripherals, and multi-function peripherals, the print log is managed by the printing device, and the print log is managed by the print server related to the printer function of the printing device. In addition to this technique, there is a technique for managing a print log with a print log management server. The background to the use of the print log management server is the centralized management of print logs, which has increased with the spread of network printers that do not require a print server and the increase in the size of printing systems consisting of printing devices and their client PCs. There is a necessity. These print logs are used for calculating a charge amount associated with the use of the printing device.
[0003]
[Patent Document 1]
Japanese Patent Laid-Open No. 11-205498
[Patent Document 2]
Japanese Patent Laid-Open No. 11-242576
[Problems to be solved by the invention]
However, when the print log is managed by the print log management server as described above, if the printing system becomes large, the total amount of the print log increases, and the analysis process of the print log takes an enormous amount of time. There is a drawback.
[0006]
Therefore, an object of the present invention is to reduce the burden of print log analysis processing on an information management apparatus that manages a print log related to a printing apparatus.
[0007]
[Means for Solving the Problems]
An invention (information management apparatus) according to claim 1 is an information management apparatus for managing a print log of printing executed by a printing apparatus and / or a printing log requested by a client apparatus of the printing apparatus to the printing apparatus. A merged print log generating unit that generates a merged print log by merging the print logs; and a merged print log managing unit that manages the merged print log.
[0008]
The invention (information management apparatus) according to claim 2 relates to the invention (information management apparatus) according to claim 1, wherein the merged print log generation unit merges a plurality of print logs, and the plurality of print logs. A merged print log that holds the sum of the print amounts is generated.
[0009]
The invention (information management apparatus) according to claim 3 relates to the invention (information management apparatus) according to claim 1 or 2, wherein the merged print log generation unit holds the print amount and the print condition. Therefore, a plurality of print logs that hold common print conditions are merged, and a merged print log that holds the total print amount of the plurality of print logs and print conditions common to the plurality of print logs is generated.
[0010]
The invention according to claim 4 (information management apparatus) relates to the invention (information management apparatus) according to any one of claims 1 to 3, wherein the merged print log is used and the use status of the printing apparatus is confirmed. Usage status information generating means for generating usage status information as such information, and usage status information output means for outputting the usage status information.
[0011]
The invention according to claim 5 (information management apparatus) relates to the invention (information management apparatus) according to any one of claims 1 to 4, wherein the merged print log is used to accompany the use of the printing apparatus. Charge information generating means for generating charge information, which is information related to charge, and charge information output means for outputting the charge information.
[0012]
An invention (information management method) according to claim 6 is an information management method for managing a print log of printing executed by a printing apparatus and / or a printing log requested by a client apparatus of the printing apparatus to the printing apparatus. A merged print log generating step for generating a merged print log by merging the print logs; and a merged print log managing step for managing the merged print log.
[0013]
The invention according to claim 7 (information management method) relates to the invention according to claim 6 (information management method), wherein the merged print log generation stage includes a plurality of print logs for the print log holding the print amount. Are merged to generate a merged print log that holds the sum of the print amounts of the plurality of print logs.
[0014]
The invention according to claim 8 (information management method) relates to the invention (information management method) according to claim 6 or 7, wherein the merged print log generation stage stores the print amount and print conditions. Therefore, a plurality of print logs that hold common print conditions are merged, and a merged print log that holds the total print amount of the plurality of print logs and print conditions common to the plurality of print logs is generated.
[0015]
The invention (information management method) according to claim 9 relates to the invention (information management method) according to any one of claims 6 to 8, wherein the merged print log is used and the use status of the printing apparatus is determined. A usage status information generation stage for generating usage status information as such information; and a usage status information output stage for outputting the usage status information.
[0016]
The invention (information management method) according to claim 10 relates to the invention (information management method) according to any one of claims 6 to 9, wherein the merged print log is used and the printing apparatus is used. A billing information generation step for generating billing information, which is information related to billing, and a billing information output step for outputting the billing information.
[0017]
An invention (information management program) according to an eleventh aspect is an information management program for causing a computer to execute the information management method according to any one of the sixth to tenth aspects.
[0018]
The invention (recording medium) described in claim 12 is a recording medium on which an information management program for causing a computer to execute the information management method according to any one of claims 6 to 10 is recorded.
[0019]
DETAILED DESCRIPTION OF THE INVENTION
An example of an embodiment of the present invention will be described.
[0020]
FIG. 1 shows a large-scale printing system 101 according to the present invention. The large-scale printing system 101 in FIG. 1 includes a plurality of networks 111 (subscripts 1 to L are used for distinction). Each network 111 is connected to a printing device 121 (subscripts 1 to M are used for distinction) and a client PC (personal computer) 122 (subscripts 1 to N are used for distinction). Further, a relay server 123 is connected to each network 111, and each relay server 123 is connected to a print log management server 124 via a telephone line 112 or the like.
[0021]
The network 111 that appears in FIG. 1 is, for example, an Ethernet (registered trademark) LAN, and the printing device 121, client PC 122, and relay server 123 that appear in FIG. 1 are, for example, LAN interfaces such as Ethernet (registered trademark) cards. Is provided.
[0022]
Specific examples of the printing device 121 appearing in FIG. 1 include a printer, a copy, a facsimile, a multifunction peripheral, a multifunction peripheral, and the like. A multifunction peripheral or a multifunction peripheral is a device that realizes functions as a printer, a copy, a facsimile, and a scanner with a single device.
[0023]
A client PC 122 appearing in FIG. 1 is, for example, a personal computer in which a printer driver related to the printer function of the printing device 121 is installed. The relay server 123 that appears in FIG. 1 is, for example, a server computer in which software for relay processing described later is installed. The print log management server 124 that appears in FIG. 1 is, for example, a server computer in which software for print log management processing described later is installed.
[0024]
When a user who is a management target in the large-scale printing system 101 in FIG. 1 requests a printing process from the client PC 122 to the printing device 121, the print log (who, what, what, how many sheets, how and how) Such information regarding the print amount and print conditions during the print processing is transferred from the client PC 122 (or the printing device 121) to the relay server 123. Similarly, when the user to be managed in the large-scale printing system 101 in FIG. 1 uses the copy function or the facsimile function in the printing device 121, the print log is received from the printing device 121 or its card reader. It is transferred to the relay server 123. The contents described in this paragraph relate to processing exchanged in the same network 111.
[0025]
The relay server 123 accumulates the print log in the network 111 to which the relay server 123 is connected. When the print log management server 124 requests the print log transfer process, the relay server 123 stores the accumulated print log. Transfer to the print log management server 124. This is relay processing by the relay server 123.
[0026]
The present invention can be applied not only to the large-scale printing system 101 as shown in FIG. 1 but also to the printing system 102 as shown in FIG. The printing system 102 in FIG. 2 includes a network 111, and the network 111 includes a printing device 121 (subscripts 1 to M are used for the sake of distinction) and a client PC (personal computer) 122 (subscripts 1 to N are distinguished. Used for convenience). A print log management server 124 is further connected to the network 111.
[0027]
(First embodiment)
A first embodiment relating to the print log management server 124 of FIG. 1 will be described based on the flowchart of FIG.
[0028]
First, the print log management server 124 collects print logs from the printing device 121 and the client PC 122 that are management targets in the large-scale printing system 101 of FIG. 1 through the relay server 123 (S11). Even if the print log management server 124 collects the print log from the printing device 121 or the client PC 122 in “PULL type”, the printing device 121 or the client PC 122 transfers the print log to the print log management server 124. "PUSH type" may be used.
[0029]
Subsequently, the print log management server 124 accumulates (S12) and manages the print logs collected by the above collection method in a storage area of a built-in storage device (hard disk drive, flash memory, etc.). FIG. 4 shows an example of a print log stored in the print log management server 124. Each print log in FIG. 4 holds the print amount and print conditions at the time of one printing process, and corresponds to the history of one printing process at a time. These print logs correspond to all print logs related to all printing devices 121 and all client PCs 122 that are managed by the large-scale printing system 101 in FIG. 1, and as the number of printing devices 121 and client PCs 122 increases, The amount will be enormous.
[0030]
Subsequently, the print log management server 124 merges the print logs with respect to the accumulated print logs according to the specified condition, and generates a merged print log by merging a plurality of print logs (S13). Here, the specified condition is, for example, a condition such as “the print conditions“ function ”,“ paper size ”, and“ color ”are the same for the print processing of each user relating to each day”. It may be fixed or arbitrarily designated by the user. As in the above example, regarding print processing within the same fixed period related to the same user, the print logs having the same predetermined print condition are merged (the designated condition is fixed in this way It would be convenient to be able to specify a specified condition in Alternatively, it may be related to print processing related to users belonging to the same user group (the same company, the same company department, etc.) rather than the print processing related to the same user.
[0031]
FIG. 5 shows an example of a merged print log generated by the print log management server 124. More specifically, the merged print log “A” in FIG. 5 is obtained by merging the print logs “1”, “4”, and “5” in FIG. The number of prints “60” of “A” in FIG. 5 is the sum of the numbers of prints “10”, “20”, and “30” of “1”, “4”, and “5” in FIG.
The function “Print” paper size “A4” color “Monochrome” of “A” in FIG. 5 is the common function “Print” paper size “A4” color “Monochrome” of “1” “4” “5” in FIG. It is derived from. Similarly, the merged print log “B” in FIG. 5 is obtained by merging the print logs “2” and “6” in FIG. 4, and the merged print log “C” in FIG. 5 is the print log in FIG. “3” and “9” are merged.
[0032]
Subsequently, the print log management server 124 manages the generated merged print log by accumulating (S14) in a storage area of a built-in storage device (such as a hard disk drive or a flash memory). Note that “D”, “E”, and “F” in FIG. 5 are print logs in which no merge partner exists, and are managed together with the merge print log.
[0033]
In general, printing conditions during printing processing are largely biased, and the same printing conditions (for example, “Print, A4, Monochrome, single-sided printing, no aggregation”, etc.) are performed rather than printing under different printing conditions each time. Printing is executed by the printing conditions). Although what kind of printing conditions are selected often differs among users, they are often the same for individual users. For this reason, the merged print log tends to be overwhelmingly small compared to a huge amount of print log.
[0034]
By repeating the processes from S11 to S14, the merged print log is accumulated in the print log management server 124. At this time, the print log of FIG. 4 may be automatically deleted if it is not necessary to save it. For example, if the number of printed pages for each month is stored, if it is not necessary to store the number of printed pages for each day, it is not necessary to store the print log itself of FIG. Save the log (of course, save the print log where there was no merge partner). However, for example, if a function such as searching for a user who performed printing at a certain date and time is required, the print log of FIG. 4 needs to be saved.
[0035]
Here, a first embodiment of the print log management server 124 of FIG. 1 will be described based on the functional block diagram of FIG. As shown in FIG. 6, the print log management server 124 includes a print log collection unit 601, a print log management unit 602, a merged print log generation unit 603, a merged print log management unit 604, and a total information generation unit 605. , And a functional block such as a total information output unit 606. Here, the functions related to these functional blocks are realized by software for print log management processing installed in the print log management server 124.
[0036]
A print log collection unit 601, a print log management unit 602, a merged print log generation unit 603, and a merged print log management unit 604 are functional blocks that execute the processes of S11, S12, S13, and S14, respectively. That is, the print log collection unit 601 collects print logs, the print log management unit 602 accumulates and manages the print logs, and the merged print log management unit 603 merges the print logs to merge the merged print logs. The merged print log management unit 604 accumulates and manages the merged print log.
[0037]
The total information generation unit 605 is a functional block that generates arbitrary total information by using the stored merged print log for total processing. For example, total information such as “total number of single-sided printing and total number of double-sided printing in a certain company department in a certain month” is generated.
[0038]
The total information output unit 606 is a functional block that outputs the generated total information. Specific examples of the output mode include display on a display, transmission of a file, printing on paper, and the like. The total information may be output in characters, or may be output as a diagram, table, graph, or the like. When displayed on the display, it may be displayed on the display of the print log management server 124 or may be displayed remotely on the display of another PC. In the latter case, for example, Web server software is installed in the print log management server 124 so that the total information can be browsed by a Web browser on the display of another PC.
[0039]
If analysis processing such as the above-described totalization processing is executed using a print log as shown in FIG. 4, it takes a long time because the amount of the processing is huge. However, as in the first embodiment, if the analysis process such as the above-described aggregation process is executed using the merged print log as shown in FIG. 5, the burden of the analysis process can be reduced and the efficiency can be reduced. Is. Such a situation is the same when analysis processing such as the above-described totalization processing is executed by a server other than the print log management server 124 of FIG.
[0040]
(Second embodiment)
A second embodiment relating to the print log management server 124 of FIG. 1 will be described based on the flowchart of FIG.
[0041]
In the second example, the total information generation unit 605 of FIG. 6 in the first example generates information related to the usage status of the printing device 121 (hereinafter referred to as “use status information”) as the total information, and the total information In this embodiment, the output unit 606 outputs the usage status information. For example, when the user wants to know the number of printed pages per month for each user of the printing device 121 or each corporate department constituting the large-scale printing system 101 of FIG. 1, the “use / status information generation / output function” of the print log management server 124 is used. Can be used.
[0042]
Examples of usage status information include the usage status of the printing device 121, such as the number of printed pages for each user in “Monochrome / Color” for each month and the number of printed pages for each “quarterly” for each corporate department. Various examples are presented from various angles. As an example of utilization status information, the number of copies for Mr. A in a month was 20 and the number of copies for Mr. B in that month was 20. "A is 20 for single-sided printing, B is 20 for double-sided printing, and A is contributing to TCO (Total Cost of Ownership) reduction. It has been understood.
[0043]
Here, the operation flow of the print log management server 124 will be described with reference to FIG. When an operation for requesting generation / output of usage status information of the printing device 121 is input (S21), the print log management server 124 generates usage status information using the accumulated merged print log (S22). ) For example, an operation for requesting generation / output of usage status information and an operation for specifying what usage status information is generated / output prior to the operation are displayed on the display of the print log management server 124, for example. The displayed GUI can be input using the keyboard and mouse of the print log management server 124. Input may be made from a client terminal of the print log management server 124. Subsequently, the print log management server 124 outputs the generated usage status information (S23).
[0044]
If the above-described usage status information generation process is executed using a print log as shown in FIG. 4, it takes a huge amount of time because the amount is enormous. However, if the above-described usage status information generation process is executed using the merged print log as shown in FIG. 5 as in the second embodiment, the load of the generation process can be reduced and efficient. It is. For example, the time from the operation of S21 to the output of S23 is shortened.
[0045]
(Third embodiment)
A third embodiment of the print log management server 124 of FIG. 1 will be described based on the flowchart of FIG.
[0046]
In the third embodiment, the tabulation information generation unit 605 in FIG. 6 in the first embodiment generates information related to billing (hereinafter referred to as “billing information”) associated with the use of the printing device 121 as tabulation information, and tabulates it. In this embodiment, the information output unit 606 outputs the billing information. For example, if the user wants to know the monthly billing amount for each user of the printing device 121 and each company department constituting the large-scale printing system 101 of FIG. 1, the “billing information generation / output function” of the print log management server 124 is used. Can be used.
[0047]
Examples of billing information include billing associated with the use of the printing device 121, such as the billing amount for each user “by monochrome / color” and the billing amount by “printing device” for each quarter of each corporate department. There are various examples that present the situation from various angles.
[0048]
Here, the operation flow of the print log management server 124 will be described with reference to FIG. When an operation for requesting generation / output of billing information of the printing device 121 is input (S31), the print log management server 124 generates billing information using the stored merged print log (S32). . For example, an operation for requesting generation / output of accounting information and an operation for designating what accounting information is generated / output prior to the operation are displayed on the display of the print log management server 124, for example. The GUI can be input using the keyboard and mouse of the print log management server 124. Input may be made from a client terminal of the print log management server 124. Subsequently, the print log management server 124 outputs the generated billing information (S33).
[0049]
If the above-described billing information generation process is executed using a print log as shown in FIG. 4, it takes an enormous amount of time because the amount is enormous. However, if the billing information generation process described above is executed using the merged print log as shown in FIG. 5 as in the third embodiment, the burden of the generation process can be reduced, which is efficient. is there. For example, the time from the operation of S31 to the output of S33 is shortened. Where the management of charging is regarded as important in the business of the printing device 121, the third embodiment has an advantage of efficient management of charging.
[0050]
(Modification)
The print log management server 124 in FIG. 1 is an example of an embodiment of an “information management apparatus” according to the present invention. Information management executed by the print log management server 124 in FIG. It is an example of embodiment of "information management method."
[0051]
The print log management processing software installed in the print log management server 124 in FIG. 1 is an example of an embodiment of the “information management program” according to the present invention, and the print log management server 124 in FIG. A computer-readable recording medium such as a CD-ROM on which software for print log management processing installed in the computer is recorded is an example of an embodiment of a “recording medium” according to the present invention.
[0052]
【The invention's effect】
Thus, the present invention makes it possible to reduce the burden of print log analysis processing on an information management apparatus or the like that manages a print log related to a printing apparatus.
[Brief description of the drawings]
FIG. 1 represents a large-scale printing system according to the present invention.
FIG. 2 represents a printing system according to the present invention.
FIG. 3 is a flowchart for explaining the first embodiment;
FIG. 4 illustrates an example of a print log.
FIG. 5 shows an example of a merged print log.
FIG. 6 is a functional block diagram for explaining the first embodiment;
FIG. 7 is a flowchart for explaining a second embodiment;
FIG. 8 is a flowchart for explaining a third embodiment;
[Explanation of symbols]
101 Large-scale printing system 102 Printing system 111 Network 112 Telephone line 121 Printing device 122 Client PC
123 Relay server 124 Print log management server 601 Print log collection unit 602 Print log management unit 603 Merged print log generation unit 604 Merged print log management unit 605 Total information generation unit 606 Total information output unit

Claims (12)

An information management device for managing a print log of printing executed by a printing device and / or printing requested by a client device of the printing device to the printing device,
An information management apparatus comprising: a merged print log generation unit that generates a merged print log obtained by merging a plurality of the print logs; and a merged print log management unit that manages the merged print log. The merged print log generating unit merges a plurality of print logs with respect to the print log holding the print amount, and generates a merged print log holding the sum of the print amounts of the plurality of print logs. The information management apparatus according to claim 1. The merged print log generation unit merges a plurality of print logs that hold common print conditions for the print logs that hold print amounts and print conditions, and sums the print amounts of the plurality of print logs and The information management apparatus according to claim 1, wherein a merged print log that holds a plurality of print logs and common print conditions is generated. Utilizing the merged print log, usage status information generating means for generating usage status information, which is information related to the usage status of the printing apparatus, and usage status information output means for outputting the usage status information are provided. The information management apparatus according to any one of claims 1 to 3. Charging information generating means for generating charging information, which is information relating to charging associated with use of the printing apparatus, using the merged print log; and charging information output means for outputting the charging information. The information management device according to any one of claims 1 to 4. An information management method for managing a print log of printing executed by a printing apparatus and / or printing requested by a client apparatus of the printing apparatus to the printing apparatus,
An information management method comprising: a merged print log generation step for generating a merged print log obtained by merging a plurality of the print logs; and a merged print log management step for managing the merged print log. In the merged print log generation step, a plurality of print logs are merged with respect to the print log that holds a print amount, and a merged print log that holds a sum of print amounts of the plurality of print logs is generated. The information management method according to claim 6. In the merged print log generation step, a plurality of print logs that hold common print conditions are merged for the print logs that hold print quantities and print conditions, and the sum of print quantities of these print logs and these The information management method according to claim 6, wherein a merged print log that holds a plurality of print logs and common print conditions is generated. Using the merged print log, and including a usage status information generation stage for generating usage status information, which is information related to the usage status of the printing apparatus, and a usage status information output stage for outputting the usage status information. The information management method according to any one of claims 6 to 8. A billing information generation step for generating billing information, which is information related to billing associated with the use of the printing apparatus, using the merged print log, and a billing information output step for outputting the billing information are provided. The information management method according to any one of claims 6 to 9. The information management program which makes a computer perform the information management method of any one of Claims 6 thru | or 10. 11. A recording medium on which an information management program for causing a computer to execute the information management method according to claim 6 is recorded.

Images