Print management device, print management system, print management method and computer readable medium

A print management device includes: a receiving unit that receives a print instruction to perform print of an electronic document on recording media; a canceling unit that cancels the print caused to be performed by the print instruction received by the receiving unit, in accordance with a canceling instruction of the print by an operator; and a recording unit that records the number of the recording media or the number of faces of the recording media, if the print caused to be performed by the print instruction received by the receiving unit is canceled by the canceling unit, the print on the recording media being canceled.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is based on and claims priority under 35 USC §119 from Japanese Patent Application No. 2010-118128 filed May 24, 2010.

BACKGROUND

1. Technical Field

The present invention relates to a print management device, a print management system, a print management method and a computer readable medium storing a program.

2. Related Art

There is known a printer device having a function that speeds print when documents being on print standby are stagnant without being outputted for a long time.

There is also known a print system whose object is to efficiently delete unnecessary image data by easily distinguishing necessary image data from unnecessary image data.

SUMMARY

According to an aspect of the present invention, there is provided a print management device including: a receiving unit that receives a print instruction to perform print of an electronic document on recording media; a canceling unit that cancels the print caused to be performed by the print instruction received by the receiving unit, in accordance with a canceling instruction of the print by an operator; and a recording unit that records the number of the recording media or the number of faces of the recording media, if the print caused to be performed by the print instruction received by the receiving unit is canceled by the canceling unit, the print on the recording media being canceled.

DETAILED DESCRIPTION

Exemplary embodiments of the present invention will be described below in detail with reference to the accompanying drawings.

FIG. 1is a diagram showing an example of an overall configuration of a computer system, serving as an example of a print management system, according to the present exemplary embodiments.

As shown inFIG. 1, the computer system is configured by image forming apparatuses10a,10band10c, an aggregate server30and terminal devices50a,50band50cthat are connected to a network80. Although the image forming apparatuses10a,10band10care shown inFIG. 1, these image forming apparatuses may be referred to as image forming apparatuses10if they do not need to be distinguished. Although only three image forming apparatuses10are shown inFIG. 1, four or more image forming apparatuses10may be provided. Furthermore, although the terminal devices50a,50band50care shown inFIG. 1, these terminal devices may be referred to as terminal devices50if they do not need to be distinguished. Although only three terminal devices50are shown inFIG. 1, four or more terminal devices50may be provided.

Each image forming apparatus10is an apparatus that prints an image of document data, which is an example of an electronic document, on a recording medium and outputs the image as a printed document. The image forming apparatus10may include only a printer function, or include a scanner function and a facsimile function in addition to the printer function.

The aggregate server30is a server computer that aggregates information managed by each of the image forming apparatuses10and provides an aggregate result for each of the terminal devices50. As the aggregate server30, for example, a computer such as a personal computer, a work station or the like may be used.

Each terminal device50is a computer device that instructs the image forming apparatus10to print document data. As the terminal device50, for example, a computer such as a personal computer, a work station or the like may be used.

The network80is a communication means used for exchanging various kinds of information. As the network80, the Internet and a local area network (LAN) are exemplified.

In the present specification, electronic data serving as a source of an image recorded on a recording medium is described as “document data.” However, the implication of the “document data” is not limited to computerized data of a “document” including texts. For example, the “document data” includes image data, such as a picture, a photograph and a drawing (irrespective of raster data or vector data), data recorded by database management software or spreadsheet software, and other printable electronic data.

Additionally, in the present specification, a “recording medium” may be made of any material as long as an image is printable on the medium. Although a representative example of the recording medium is paper, an OHP sheet, a metal plate and the like may also be used.

In recent years, awareness of environmental issues has been raised. Also in a computer system as described above, it is required that the amount of reduction in recording media and the like used in the image forming apparatuses10should be recognized on a user side. Thus, in the present exemplary embodiments, recording media and the like whose consumption has been restrained are counted by a counter.

Hereinafter, a description will be given in the following order: the image forming apparatus10that manages a counter of recording media and the like whose consumption has been restrained; and the aggregate server30that aggregates information on counters managed by the image forming apparatuses10.

FIG. 2is a diagram showing an example of a hardware configuration of the image forming apparatus10.

As shown inFIG. 2, the image processing apparatus10includes a central processing unit (CPU)11, a random access memory (RAM)12, a read only memory (ROM)13, a hard disk drive (HDD)14, an operation panel15, an image capturing unit16, an image forming unit17and a communication interface controller (hereinafter, referred to as a “communication I/F controller”)18.

The CPU11loads various programs stored in the ROM13and the like into the RAM12, and then executes the programs, thereby to implement functions to be described later.

The RAM12is a memory that is used as a working memory or the like for the CPU11.

The ROM13is a memory that stores, therein, the various programs executed by the CPU11.

The HDD14is, for example, a magnetic disk device that stores, therein, image data captured by the image capturing unit16, image data used for image formation in the image forming unit17, and the like.

The operation panel15is, for example, a touch panel that displays various kinds of information and receives an operation input by a user.

The image capturing unit16captures an image recorded on a recording medium such as paper. The image capturing unit16herein is, for example, a scanner. The scanner to be used may employ one of the following two systems: a CCD system in which reflected light of light emitted from a light source and directed at an original is reduced by a lens and is then received by charge coupled devices (CCD); and a CIS system in which reflected light of light beams sequentially emitted from LED light sources and directed at an original is received by a contact image sensor (CIS).

The image forming unit17forms an image on a recording medium. The image forming unit17herein is, for example, a printer. The printer to be used may employ one of the following two systems: an electrophotographic system in which an image is formed by transferring toner attached to a photoconductive drum onto a recording medium; and an ink jet system in which an image is formed by ejecting ink onto a recording medium.

The communication I/F controller18transmits and receives various kinds of information to and from other devices through the network80.

In the present exemplary embodiments, a print management unit20, serving as an example of a print management device that counts and manages recording media and the like whose consumption has been restrained, is achieved in the image processing apparatus10by the CPU11loading a program stored in the ROM13into the RAM12, and executing the program.

Hereinafter, this print management unit20will be described in exemplary embodiments according to timing at which recording media and the like are saved, for example.

The first exemplary embodiment is an exemplary embodiment in which a print job is canceled before print of document data is started, in a case where the document data is not stored in the image forming apparatus10after a user enters the print job into the image forming apparatus10, the print job being an instruction to print the document data.

First, a description will be given of a functional configuration of the print management unit20according to the first exemplary embodiment.

FIG. 3is a block diagram showing an example of a functional configuration of the print management unit20according to the first exemplary embodiment.

As shown inFIG. 3, the print management unit20includes a receiving unit21, a print controller25, a counter updating unit27, a counter memory28and a counter informing unit29. Among these, the counter memory28is implemented by the HDD14(seeFIG. 2), for example. The receiving unit21, the print controller25, the counter updating unit27and the counter informing unit29are achieved by the CPU11(seeFIG. 2) loading a program stored in the ROM13(seeFIG. 2) into the RAM12(seeFIG. 2) and executing the program.

The receiving unit21receives a print job from the terminal device50. The print job herein is a unit of processing executed in the image forming apparatus10on the basis of print instruction information that is an instruction to print document data. In the present specification, the print instruction information may be referred to as print job. Additionally, the receiving unit21may also receive cancel instruction information that is an instruction to cancel the print job. In the first exemplary embodiment, the print job is used as an example of a print instruction, and the receiving unit21is provided as an example of a receiving unit that receives the print instruction.

The print controller25controls print of document data by executing the print job received by the receiving unit21. Additionally, if the receiving unit21receives the cancel instruction information before the start of print, the print controller25performs control so that the print job received by the receiving unit21is canceled. In the first exemplary embodiment, the print controller25is provided as an example of a canceling unit that cancels print.

The counter updating unit27updates the value of a printed document reducing counter and the value of a staple needle reducing counter that are stored in the counter memory28, if a print job is canceled. In the first exemplary embodiment, the counter updating unit27is provided as an example of a recording unit that records the number of recording media or the number of faces of recording media, print on the recording media being canceled.

The counter memory28stores, therein, the value of the printed document reducing counter and the value of the staple needle reducing counter. The printed document reducing counter is a memory area for counting the number of recording media or the number of faces of recording media whose consumption has been restrained by canceling a print job before a printed document is outputted. The staple needle reducing counter is a memory area for counting the number of staple needles whose consumption has been restrained by canceling a print job before a printed document is outputted, in a case where staple binding is designated in the print job.

The counter informing unit29informs external devices of the value of the printed document reducing counter and the value of the staple needle reducing counter that are stored in the counter memory28. In the first exemplary embodiment, the counter informing unit29is provided as an example of an outputting unit that outputs information on the number of recording media or the number of faces of recording media.

Next, a description will be given of an operation of the print management unit20according to the first exemplary embodiment.

FIG. 4is a flowchart showing an operation example of the print management unit20according to the first exemplary embodiment. In this operation example, sheets are used as the recording media, and the number of sheets is counted by the printed document reducing counter.

In the print management unit20, the receiving unit21first receives a print job from the terminal device50(Step201). Here, it is assumed that the print job includes: a user ID which is identification information on a user who provides an instruction of print; the size of sheets on which the print is performed; a classification indicating whether the print is performed in color or monochrome; and the like.

Next, the print controller25determines whether the print is started by execution of the print job (Step205). Since the print job received by the receiving unit21is delivered to an image processor (not shown) and the image forming unit17(seeFIG. 2) through the print controller25, the print controller25recognizes a status indicating whether the print is started. Thus, the print controller25makes the determination in Step205on the basis of this status.

As a result, if it is determined that the print is started, the processing is finished.

On the other hand, if it is determined that the print has not been started yet because of a print standby or the like, the print controller25determines whether an instruction to cancel the print job is provided (Step206). In the first exemplary embodiment, it is assumed that cancel of a print job is also made through the terminal device50. Thus, in Step206, the print controller25determines whether the receiving unit21receives cancel instruction information.

If it is not determined that an instruction to cancel the print job is provided, the processing returns to Step205. Then, the print controller25repeats the determination in Step206until the print is started.

If it is determined that an instruction to cancel the print job is provided before the print is started, the print controller25cancels the print job (Step207). That is, the print controller25causes the print job received by the receiving unit21to disappear and performs control so that the print job is not delivered to the image processor (not shown) and the image forming unit17(seeFIG. 2).

Next, the counter updating unit27calculates the number of sheets that are supposed to be printed if the canceled print job is executed (Step209). Here, the number of sheets may be calculated on the basis of the number of pages of document data to be printed and print setting of the print job. For example, suppose that the number of pages of document data is ten, and duplex print and setting by which two pages of the document data are put together in one face of a sheet are designated in the print job. Then, the number of sheets is three.

The counter updating unit27then counts up the value of the printed document reducing counter stored in the counter memory28by the number of sheets calculated in Step209(Step210). Since the print job includes a user ID, the size of sheets and a classification of color or monochrome, this count up may be performed for each of these attributions.

Subsequently, the counter updating unit27calculates the number of staple needles that are supposed to be used if the canceled print job is executed (Step211). Here, the number of staple needles may be calculated on the basis of setting about stable binding in the print job. For example, suppose that staple binding for each of copies and staple binding at two positions on one edge of the sheets are designated in the print job. Then, the number of staple needles is two.

The counter updating unit27then counts up the value of the staple needle reducing counter stored in the counter memory28by the number of staple needles calculated in Step211(Step212). Since the print job includes a user ID, the size of sheets and a classification of color or monochrome, this count up may be performed for each of these attributions.

After that, the counter informing unit29informs a user of the value of the printed document reducing counter and the value of the staple needle reducing counter that are stored in the counter memory28(Step213). In this case, various methods are conceivable as a method to inform a user of the values of the counters. Firstly, there is a method in which a document with the values of the counters printed thereon is outputted as a counter report when a user provides an instruction through the operation panel15(seeFIG. 2). Secondly, there is a method in which the values of the counters are outputted to the aggregate server30, so that an aggregate result by the aggregate server30may be acquired from the terminal device50. Thirdly, there is a method in which an application program to refer to the values of the counters is operated in the terminal device50, so that the values of the counters may be referred to through this application program.

In this operation example, the number of sheets is calculated in Step209, and the count up by the number of sheets is made in Step210. However, the number of faces of sheets may be used instead of the number of sheets. The number of faces herein is not the number of faces of an electronic document, but the number of faces of sheets. That is, the number of faces obtained by counting the front and rear faces of a sheet individually is the number of faces of sheets. The number of faces of sheets may also be calculated on the basis of the number of pages of document data to be printed and print setting of the print job. For example, suppose that the number of pages of document data is ten, and duplex print and setting by which two pages of the document data are put together in one face of a sheet are designated in the print job. Then, the number of faces of sheets is five.

The description of the first exemplary embodiment is now finished.

In the first exemplary embodiment, staple needles are taken as an example of consumption material other than sheets, and a description is given of processing to count the number of staple needles whose use has been restrained. However, the present invention is not limited to this. For example, other metal pieces used for bookbinding or adhesive material, such as paste and adhesive tapes, may be regarded as consumption material other than sheets, and the number of metal pieces or the amount of adhesive material whose use has been restrained may be recorded. Instead, image forming material such as toner may be regarded as consumption material other than sheets, and the amount of image forming material whose use has been restrained may be recorded.

Additionally, although both of the printed document reducing counter and the staple needle reducing counter are counted up in the first exemplary embodiment, these counters may be configured so that at least any one of the counters counts up.

The second exemplary embodiment is an exemplary embodiment in which a print job for stored and unprinted document data is canceled, in a case where the document data is stored in the image forming apparatus10after a user enters the print job into the image forming apparatus10, the print job being an instruction to print the document data.

First, a description will be given of a functional configuration of the print management unit20according to the second exemplary embodiment.

FIG. 5is a block diagram showing an example of a functional configuration of the print management unit20according to the second exemplary embodiment.

As shown inFIG. 5, the print management unit20includes the receiving unit21, a document data memory22, an operation receiving unit24, the print controller25, a document data deleting unit26, the counter updating unit27, the counter memory28and the counter informing unit29. Among these, the document data memory22and the counter memory28is implemented by the HDD14(seeFIG. 2), for example. The receiving unit21, the operation receiving unit24, the print controller25, the document data deleting unit26, the counter updating unit27and the counter informing unit29are achieved by the CPU11(seeFIG. 2) loading a program stored in the ROM13(seeFIG. 2) into the RAM12(seeFIG. 2) and executing the program.

The receiving unit21receives a print job from the terminal device50. The print job herein is a unit of processing executed in the image forming apparatus10on the basis of print instruction information that is an instruction to print document data, as described in the first exemplary embodiment. In the present specification, the print instruction information may be referred to as print job. Additionally, the receiving unit21stores, in the document data memory22, the document data of which an instruction of print is provided by the print job. In the second exemplary embodiment, the print job is used as an example of a print instruction, and the receiving unit21is provided as an example of a receiving unit that receives the print instruction.

The document data memory22stores, therein, the document data of which an instruction of print is provided by the print job until a user provides the instruction of the print through the operation panel15(seeFIG. 2). In the second exemplary embodiment, the document data memory22is provided as an example of a memory that stores an electronic document.

The operation receiving unit24receives information on a user operation through the operation panel15(seeFIG. 2). In particular, the operation receiving unit24may receive cancel instruction information that is an instruction to cancel a print job.

The print controller25controls print of document data by executing a print job for the document data stored in the document data memory22. Additionally, if the operation receiving unit24receives cancel instruction information, the print controller25performs control so that the print job is canceled. In the second exemplary embodiment, the print controller25is provided as an example of a canceling unit that cancels print.

The document data deleting unit26deletes document data if a print job for the document data stored in the document data memory22is canceled. In the second exemplary embodiment, the document data deleting unit26is provided as an example of a deleting unit that deletes an electronic document.

The counter updating unit27updates the value of a stored document reducing counter stored in the counter memory28, if a print job is canceled. In the second exemplary embodiment, the counter updating unit27is provided as an example of a recording unit that records the number of recording media or the number of faces of recording media, print on the recording media being canceled.

The counter memory28stores, therein, the value of the stored document reducing counter. The stored document reducing counter is a memory area for counting the number of recording media or the number of faces of recording media whose consumption has been restrained by canceling a print job in a state where document data is stored.

The counter informing unit29informs external devices of the value of the stored document reducing counter stored in the counter memory28. In the second exemplary embodiment, the counter informing unit29is provided as an example of an outputting unit that outputs information on the number of recording media or the number of faces of recording media.

Next, a description will be given of an operation of the print management unit20according to the second exemplary embodiment.

FIG. 6is a flowchart showing an operation example of the print management unit20according to the second exemplary embodiment. In this operation example, sheets are used as the recording media, and the number of sheets is counted by the stored document reducing counter.

In the print management unit20, the receiving unit21first receives a print job from the terminal device50(Step221). Here, it is assumed that the print job includes: a user ID which is identification information on a user who provides an instruction of print; the size of sheets on which the print is performed; a classification indicating whether the print is performed in color or monochrome; and the like. The receiving unit21stores, in the document data memory22, the document data of which an instruction of print is provided by the print job (Step222).

Next, the print controller25determines whether an instruction to cancel a print job for specific document data in the document data memory22is provided (Step226). In the second exemplary embodiment, it is assumed that cancel of a print job is made through the operation panel15(seeFIG. 2). Thus, in Step226, the print controller25determines whether the operation receiving unit24receives cancel instruction information.

As a result, if it is not determined that an instruction to cancel the print job is provided, the processing is finished.

On the other hand, if it is determined that an instruction to cancel the print job is provided, the print controller25cancels the print job (Step227). That is, the print controller25causes the print job for the above-mentioned specific document data to disappear and performs control so that the print job is not delivered to the image processor (not shown) and the image forming unit17(seeFIG. 2). Then, the document data deleting unit26deletes the above-mentioned specific document data in the document data memory22(Step228).

Next, the counter updating unit27calculates the number of sheets that are supposed to be printed if the canceled print job is executed (Step229). Here, the number of sheets may be calculated on the basis of the number of pages of document data to be printed and print setting of the print job. For example, suppose that the number of pages of document data is ten, and duplex print and setting by which two pages of the document data are put together in one face of a sheet are designated in the print job. Then, the number of sheets is three.

The counter updating unit27then counts up the value of the stored document reducing counter stored in the counter memory28by the number of sheets calculated in Step229(Step230). Since the print job includes a user ID, the size of sheets and a classification of color or monochrome, this count up may be performed for each of these attributions.

After that, the counter informing unit29informs a user of the value of the stored document reducing counter stored in the counter memory28(Step233). In this case, various methods are conceivable as a method to inform a user of the value of the counter, as described in the first exemplary embodiment.

In this operation example, the number of sheets is calculated in Step229, and the count up by the number of sheets is made in Step230. However, the number of faces of sheets may be used instead of the number of sheets. The number of faces herein is not the number of faces of an electronic document, but the number of faces of sheets. That is, the number of faces obtained by counting the front and rear faces of a sheet individually is the number of faces of sheets. The number of faces of sheets may also be calculated on the basis of the number of pages of document data to be printed and print setting of the print job. For example, suppose that the number of pages of document data is ten, and duplex print and setting by which two pages of the document data are put together in one face of a sheet are designated in the print job. Then, the number of faces of sheets is five.

The description of the second exemplary embodiment is now finished.

In the second exemplary embodiment, it is not mentioned which of the following cases is assumed: a case where document data that has never been printed and is stored is deleted; or a case where document data that has already been printed but is still stored for additional print or the like is deleted.

Among these cases, the former case results in restraint of print of document data on recording media. Thus, it is natural to count up the stored document reducing counter. Accordingly, the second exemplary embodiment may be regarded as an exemplary embodiment for document data that has never been printed and is stored.

On the other hand, in the latter case, since document data that has already been printed is deleted, it may be considered that the latter case does not make a large contribution to restraint of print of document data on recording media. Accordingly, the stored document reducing counter may be configured so as not to count up in such a case. Specifically, for each piece of stored document data, a flag is provided to indicate whether the corresponding piece of document data has already been printed. The stored document reducing counter may be configured so as not to count up when document data is deleted, if the flag corresponding to the document data indicates that the document data has already been printed.

Additionally, although only the stored document reducing counter is counted up in the second exemplary embodiment, the printed document reducing counter of the first exemplary embodiment and a counter for consumption material such as the staple needle reducing counter of the first exemplary embodiment may also be counted up, in addition to the stored document reducing counter.

Furthermore, in the second exemplary embodiment, it is assumed that stored document data is deleted by a user operation. However, deletion by a user operation may not be assumed. For example, the stored document reducing counter may be counted up, even in a case where the document data deleting unit26automatically deletes document data whose storing period has passed. Here, the storing period is an example of a predetermined time period. Instead, the stored document reducing counter may be counted up, when the document data deleting unit26automatically deletes document data because free space in the document data memory22has decreased.

The third exemplary embodiment is an exemplary embodiment in which a print job for stored document data is canceled during print of the document data, in a case where the document data is stored in the image forming apparatus10after a user enters the print job into the image forming apparatus10, the print job being an instruction to print the document data.

First, a functional configuration of the print management unit20according to the third exemplary embodiment is the same as that of the print management unit20according to the second exemplary embodiment. Thus, a description thereof is omitted.

Next, a description will be given of an operation of the print management unit20according to the third exemplary embodiment.

FIG. 7is a flowchart showing an operation example of the print management unit20according to the third exemplary embodiment. In this operation example, sheets are used as the recording media, and the number of sheets is counted by the stored document reducing counter.

In the print management unit20, the receiving unit21first receives a print job from the terminal device50(Step241). Here, it is assumed that the print job includes: a user ID which is identification information on a user who provides an instruction of print; the size of sheets on which the print is performed; a classification indicating whether the print is performed in color or monochrome; and the like. The receiving unit21stores, in the document data memory22, the document data of which an instruction of print is provided by the print job (Step242).

Next, the print controller25executes a print job for specific document data in the document data memory22, thereby to start printing the document data (Step244). The print controller25then determines whether print of the document data is finished (Step245). Since the print job received by the receiving unit21is delivered to the image processor (not shown) and the image forming unit17(seeFIG. 2) through the print controller25, the print controller25recognizes a status indicating whether the print is finished. Thus, the print controller25makes the determination in Step245on the basis of this status.

As a result, if it is determined that the print is finished, the processing is finished.

On the other hand, if it is determined that the print has not been finished yet, the print controller25determines whether an instruction to cancel the print job for the above-mentioned specific document data is provided (Step246). In the third exemplary embodiment, it is assumed that cancel of a print job is made through the operation panel15(seeFIG. 2). Thus, in Step246, the print controller25determines whether the operation receiving unit24receives cancel instruction information.

If it is not determined that an instruction to cancel the print job for the above-mentioned specific document data is provided, the processing returns to Step245. Then, the print controller25repeats the determination in Step246until the print of the above-mentioned specific document data is finished.

If it is determined that an instruction to cancel the print job for the above-mentioned specific document data is provided before the print of the document data is finished, the print controller25cancels the print job (Step247). That is, the print controller25causes the print job for the above-mentioned specific document data to disappear and controls the image processor (not shown) and the image forming unit17(seeFIG. 2) so that these units do not execute the print job delivered thereto. Then, the document data deleting unit26deletes the above-mentioned specific document data in the document data memory22(Step248).

Next, the counter updating unit27calculates the number of sheets that are supposed to be printed if the canceled print job is executed (Step249). Here, the number of sheets may be calculated on the basis of the number of pages of document data to be printed and print setting of the print job. For example, suppose that the number of pages of document data is ten, and duplex print and setting by which two pages of the document data are put together in one face of a sheet are designated in the print job. Then, the number of sheets is three.

The counter updating unit27then counts up the value of the stored document reducing counter stored in the counter memory28by the number of sheets calculated in Step249(Step250). Since the print job includes a user ID, the size of sheets and a classification of color or monochrome, this count up may be performed for each of these attributions.

In Step249, the number of sheets designated by the print job, namely, a total number of the number of printed sheets and the number of sheets, print of which is canceled, is calculated. Then, in Step250, the value of the stored document reducing counter is counted up by this calculated total number. For example, suppose that the number of sheets on which document data is supposed to be printed is ten. Then, even if the print job is canceled at a time point when the sixth sheet is printed, the stored document reducing counter is counted up by ten, which is the number of sheets on which print is supposed to be performed.

Instead, in Step249, the number of sheets, print of which is canceled, namely, a number obtained by subtracting the number of printed sheets from the number of sheets designated by the print job may be calculated. Then, in Step250, the value of the stored document reducing counter may be counted up by this calculated number. In this case, for example, if the number of sheets on which document data is supposed to be printed is ten and if the print job is canceled at a time point when the sixth sheet is printed, then the stored document reducing counter is counted up by four, which is the number of sheets, print of which is canceled.

After that, the counter informing unit29informs a user of the value of the stored document reducing counter stored in the counter memory28(Step253). In this case, various methods are conceivable as a method to inform a user of the value of the counter, as described in the first exemplary embodiment.

In this operation example, the number of sheets is calculated in Step249, and the count up by the number of sheets is made in Step250. However, the number of faces of sheets may be used instead of the number of sheets. The number of faces herein is not the number of faces of an electronic document, but the number of faces of sheets. That is, the number of faces obtained by counting the front and rear faces of a sheet individually is the number of faces of sheets. The number of faces of sheets may also be calculated on the basis of the number of pages of document data to be printed and print setting of the print job. For example, suppose that the number of pages of document data is ten, and duplex print and setting by which two pages of the document data are put together in one face of a sheet are designated in the print job. Then, the number of faces of sheets is five.

The description of the third exemplary embodiment is now finished.

The third exemplary embodiment avoids the following impropriety: when a print job having a large number of prints is canceled at an initial stage during the print, a large number of print outputs are restrained; however, this result is not reflected unless the stored document reducing counter is counted up. Accordingly, the print management unit20may employ a configuration in which the stored document reducing counter is counted up only if one of the following conditions or the like is satisfied: the number of sheets on which print is supposed to be performed is larger than a threshold value Th1and the number of printed sheets is smaller than a threshold value Th2(where Th1>Th2); or a ratio of the number of printed sheets to the number of sheets on which print is supposed to be performed is smaller than a threshold value Th3.

Additionally, although only the stored document reducing counter is counted up in the third exemplary embodiment, the printed document reducing counter of the first exemplary embodiment and a counter for consumption material such as the staple needle reducing counter of the first exemplary embodiment may also be counted up, in addition to the stored document reducing counter.

Furthermore, in the third exemplary embodiment, it is assumed that stored document data is deleted by a user operation. However, deletion by a user operation may not be assumed. For example, the stored document reducing counter may be counted up, even in a case where the document data deleting unit26automatically deletes document data whose storing period has passed. Here, the storing period is an example of a predetermined time period. Instead, the stored document reducing counter may be counted up, when the document data deleting unit26automatically deletes document data because free space in the document data memory22has decreased.

The fourth exemplary embodiment is an exemplary embodiment in which an instruction to print document data is provided to store the document data in the image forming apparatus10once; however the document data is deleted when a user has no intention of printing the document data because the document data is stored by an operation error or the like, or when there is a need to modify the document data after the document data is stored.

First, a description will be given of a functional configuration of the print management unit20according to the fourth exemplary embodiment.

FIG. 8is a block diagram showing an example of a functional configuration of the print management unit20according to the fourth exemplary embodiment.

As shown inFIG. 8, the print management unit20includes the receiving unit21, the document data memory22, a deletion determining unit23, the operation receiving unit24, the print controller25, the document data deleting unit26, the counter updating unit27, the counter memory28and the counter informing unit29. Among these, the document data memory22and the counter memory28are implemented by the HDD14(seeFIG. 2), for example. The receiving unit21, the deletion determining unit23, the operation receiving unit24, the print controller25, the document data deleting unit26, the counter updating unit27and the counter informing unit29are achieved by the CPU11(seeFIG. 2) loading a program stored in the ROM13(seeFIG. 2) into the RAM12(seeFIG. 2) and executing the program.

The receiving unit21receives a print job from the terminal device50. The print job herein is a unit of processing executed in the image forming apparatus10on the basis of print instruction information that is an instruction to print document data, as described in the first exemplary embodiment. In the present specification, the print instruction information may be referred to as print job. Additionally, the receiving unit21stores, in the document data memory22, the document data of which an instruction of print is provided by the print job. In the fourth exemplary embodiment, the print job is used as an example of a print instruction, and the receiving unit21is provided as an example of a receiving unit that receives the print instruction.

The document data memory22stores, therein, the document data of which an instruction of print is provided by the print job until a user provides an instruction of print through the operation panel15(seeFIG. 2).

The deletion determining unit23determines whether the following document data has already been stored in the document data memory22: document data of which an instruction of print is provided by the same user as the one who provides an instruction to print document data newly stored in the document data memory22; and document data based on the same document as that of the newly stored document data. If such document data has already been stored, the deletion determining unit23inquires whether the document data is made to be deleted. In the fourth exemplary embodiment, the deletion determining unit23is provided as an example of an inquiring unit that inquires whether or not deletion of any one of plural electronic documents is allowed.

The operation receiving unit24receives information on a user operation through the operation panel15(seeFIG. 2). In particular, the operation receiving unit24may receive document data deleting instruction information inputted in response to an inquiry made by the deletion determining unit23.

The print controller25controls print of document data by executing a print job for the document data stored in the document data memory22. Additionally, if the operation receiving unit24receives document data deleting instruction information that is an instruction to delete document data, the print controller25performs control so that the print job for the document data is canceled. In the fourth exemplary embodiment, the print controller25is provided as an example of a canceling unit that cancels print.

The document data deleting unit26deletes document data if a print job for the document data stored in the document data memory22is canceled. In the fourth exemplary embodiment, the document data deleting unit26is provided as an example of a deleting unit that deletes an electronic document.

The counter updating unit27updates the value of the stored document reducing counter stored in the counter memory28, if a print job is canceled. In the fourth exemplary embodiment, the counter updating unit27is provided as an example of a recording unit and a first recording unit that record the number of recording media or the number of faces of recording media, print on the recording media being canceled.

The counter memory28stores, therein, the value of the stored document reducing counter. The stored document reducing counter is a memory area for counting the number of recording media or the number of faces of recording media whose consumption has been restrained by canceling a print job in a state where document data is stored.

The counter informing unit29informs external devices of the value of the stored document reducing counter stored in the counter memory28. In the fourth exemplary embodiment, the counter informing unit29is provided as an example of an outputting unit that outputs information on the number of recording media or the number of faces of recording media.

Next, a description will be given of an operation of the print management unit20according to the fourth exemplary embodiment.

FIG. 9is a flowchart showing an operation example of the print management unit20according to the fourth exemplary embodiment. In this operation example, sheets are used as the recording media, and the number of sheets is counted by the stored document reducing counter.

In the print management unit20, the receiving unit21first receives a print job from the terminal device50(Step261). Here, it is assumed that the print job includes: a user ID which is identification information on a user who provides an instruction of print; the size of sheets on which the print is performed; a classification indicating whether the print is performed in color or monochrome; and the like. The receiving unit21stores, in the document data memory22, the document data of which an instruction of print is provided by the print job (Step262).

Next, the deletion determining unit23searches the document data memory22for document data that is stored because a user who has provided an instruction to print the document data newly stored in Step262provided an instruction of print in the past (Step263). When the search has succeeded, the deletion determining unit23determines whether the searched document data is document data (hereinafter, referred to as “stored same document data”) based on the same document as that of the document data newly stored in Step262(Step264). Such determination is made because there are plural pieces of document data based on the same document if document data having been stored once is modified and the modified document data is also stored, for example. Here, the determination whether the searched document data is the stored same document data may be made by determining whether the whole of or a part of the names of document data is the same, for example.

If it is determined that the searched document data is the stored same document data in Step264, the deletion determining unit23inquires whether the stored same document data is made to be deleted, through the operation panel15(seeFIG. 2), for example (Step265).

Then, the print controller25determines whether an instruction to delete the stored same document data is provided (Step266). In the fourth exemplary embodiment, it is assumed that deletion of document data is made through the operation panel15(seeFIG. 2). Thus, in Step266, the print controller25determines whether the operation receiving unit24receives document data deleting instruction information.

As a result, if it is determined that an instruction to delete the stored same document data is provided, the print controller25cancels the print job for the stored same document data (Step267). That is, the print controller25causes the print job for the stored same document data to disappear and performs control so that the print job is not delivered to the image processor (not shown) and the image forming unit17(seeFIG. 2). Then, the document data deleting unit26deletes the stored same document data in the document data memory22(Step268).

Next, the counter updating unit27calculates the number of sheets that are supposed to be printed if the canceled print job is executed (Step269). Here, the number of sheets may be calculated on the basis of the number of pages of document data to be printed and print setting of the print job. For example, suppose that the number of pages of document data is ten, and duplex print and setting by which two pages of the document data are put together in one face of a sheet are designated in the print job. Then, the number of sheets is three.

The counter updating unit27then counts up the value of the stored document reducing counter stored in the counter memory28by the number of sheets calculated in Step269(Step270). Since the print job includes a user ID, the size of sheets and a classification of color or monochrome, this count up may be performed for each of these attributions.

After that, the counter informing unit29informs a user of the value of the stored document reducing counter stored in the counter memory28(Step273). In this case, various methods are conceivable as a method to inform a user of the value of the counter, as described in the first exemplary embodiment.

In this operation example, the number of sheets is calculated in Step269, and the count up by the number of sheets is made in Step270. However, the number of faces of sheets may be used instead of the number of sheets. The number of faces herein is not the number of faces of an electronic document, but the number of faces of sheets. That is, the number of faces obtained by counting the front and rear faces of a sheet individually is the number of faces of sheets. The number of faces of sheets may also be calculated on the basis of the number of pages of document data to be printed and print setting of the print job. For example, suppose that the number of pages of document data is ten, and duplex print and setting by which two pages of the document data are put together in one face of a sheet are designated in the print job. Then, the number of faces of sheets is five.

The description of the fourth exemplary embodiment is now finished.

In the fourth exemplary embodiment, when document data is newly stored, determination is made whether plural pieces of document data based on the same document have come to be stored. However, the present invention is not limited to this. For example, when document data is newly stored, determination is made whether plural pieces of document data that are associated with each other have come to be stored.

Additionally, although only the stored document reducing counter is counted up in the fourth exemplary embodiment, the printed document reducing counter of the first exemplary embodiment and a counter for consumption material such as the staple needle reducing counter of the first exemplary embodiment may also be counted up, in addition to the stored document reducing counter.

FIG. 10is a table showing a specific example of values of the counters recorded in the above-mentioned first to fourth exemplary embodiments. In the above-mentioned first to fourth exemplary embodiments, a print job includes a user ID, the size of sheets and a classification of color or monochrome, and the count is performed for each of these attributions. Thus,FIG. 10also shows a counter that records counted values for each user ID, each size of sheets and each classification of color or monochrome.

Since any one of the printed document reducing counter, the staple needle reducing counter and the stored document reducing counter has the same format,FIG. 10shows only one format. However, for the printed document reducing counter and the stored document reducing counter, the counted value is the number of recording media or the number of faces of recording media. Meanwhile, for the staple needle reducing counter, the counted value is the number of staple needles.

Various methods are conceivable as a method to inform a user of the values of the above-mentioned counters, as described above. Among these, there is a method in which the aggregate server30aggregates the values of the counters of each image forming apparatus10, and provides the result to each terminal device50.

Thus, a description will be given of the aggregate server30that is an example of an information aggregate device performing such an operation.

FIG. 11is a diagram showing an example of a hardware configuration of the aggregate server30.

As shown inFIG. 11, the aggregate server30includes a central processing unit (CPU)31, a main memory32and a magnetic disk device (HDD: Hard Disk Drive)33. Here, the CPU31executes an operating system (OS) and various kinds of software such as application, and achieves various functions to be described below. The main memory32is a memory area that stores various kinds of software, data used for executing the software, and the like. The magnetic disk device33is a memory area that stores input data to various kinds of software, output data from various kinds of software, and the like.

Furthermore, the aggregate server30includes a communication interface34(denoted by “communication I/F” inFIG. 11) that performs communication with external devices, a display mechanism35including a video memory, a display and the like, and an input device36such as a keyboard, a mouse or the like.

Next, a description will be given of a functional configuration of the aggregate server30according to the first to fourth exemplary embodiments.

FIG. 12is a block diagram showing an example of a functional configuration of the aggregate server30according to the first to fourth exemplary embodiments.

As shown inFIG. 12, the aggregate server30includes a receiving unit41, a counter updating unit47, a counter memory48and a counter informing unit49. Among these, the counter memory48is implemented by the magnetic disk device33(seeFIG. 11), for example. The receiving unit41, the counter updating unit47and the counter informing unit49are achieved by the CPU31(seeFIG. 11) loading a program stored in the magnetic disk device33(seeFIG. 11) into the main memory32(seeFIG. 11) and executing the program.

The receiving unit41receives values of the printed document reducing counter, the stored document reducing counter and the staple needle reducing counter that are managed by each image forming apparatus10. In the first to fourth exemplary embodiments, the receiving unit41is provided as an example of a reception unit that receives the number of recording media or the number of faces of recording media.

The counter updating unit47updates the values of the printed document reducing counter, the stored document reducing counter and the staple needle reducing counter that are stored in the counter memory48, on the basis of the values of the printed document reducing counter, the stored document reducing counter and the staple needle reducing counter that are received by the receiving unit41. In the first to fourth exemplary embodiments, the counter updating unit47is provided as an example of a second recording unit that records information obtained by aggregating the number of recording media or the number of faces of recording media.

The counter memory48stores, therein, an aggregate result of the values of the printed document reducing counter, the stored document reducing counter and the staple needle reducing counter.

The counter informing unit49informs external devices of the values of the printed document reducing counter, the stored document reducing counter and the staple needle reducing counter that are stored in the counter memory48.

The aggregate server30operates in the following way.

Specifically, the receiving unit41first receives the values of the printed document reducing counter, the stored document reducing counter and the staple needle reducing counter from each image forming apparatus10, and delivers the values to the counter updating unit47.

The counter updating unit47then counts up the values of the printed document reducing counter, the stored document reducing counter and the staple needle reducing counter that are stored in the counter memory48, by the values of the printed document reducing counter, the stored document reducing counter and the staple needle reducing counter that are delivered from the receiving unit41, thereby to aggregate the values of the counters. Since the values of the counters are recorded for each user in the first to fourth exemplary embodiments, also here, aggregate for each user may be performed over the image forming apparatuses10. Instead, it is conceivable that the receiving unit41receives, from each image forming apparatus10, identification information of each image forming apparatus10together with the values of the counters, and the counter updating unit47aggregates for each image forming apparatus10by using this identification information.

After that, the counter informing unit49outputs, to the terminal devices50, the values of the printed document reducing counter, the stored document reducing counter and the staple needle reducing counter that are stored in the counter memory48, in response to a request from each terminal device50.

The program that achieves the first to fourth exemplary embodiments may be provided not only by a communication unit but also by being stored in a recording medium such as a CD-ROM.