Network system, printer supervising method and memorizing medium

Abstract: A network system includes at least one server PC, at least one client PC having a printer and at least one supervisor PC respectively connected to a network. Print log is stored in a client PC every time when a printing request to a printer is made in the client PC. A server PC periodically collects the stored print logs. A supervisor PC can aggregate printer usage contents per application or time zone based on the collected print log.

Description: BACKGROUND OF THE INVENTION Field of the invention The present invention relates to a network system, a printer supervising method and a memorizing medium. Discussion of the Background Recently, a supervising tool for minimizing total cost of ownership (hereinafter referred to as TCO) is sold, and recognition of an owner and a supervisor of each company that the TCO is minimized is enhanced. There has been heretofore needs for minimizing both cost and charge on FAX transmission or a number of copy sheets made by a copier, and its supervising tool has been sold. Further, as a prior art capable of supervising a number of printing sheets made by a printer, a supervising tool, which collects print log of a network printer in a client computer, stores the print log in a server, and aggregates thereof, is sold. With this supervising tool, print log can be aggregated per department of a company or printer, when the print logs are collected. However, even though analysis of a time zone when a printer is frequently utilized and application frequently used are required, the above-mentioned conventional supervising tool for supervising a number of prints is impossible to execute such analysis. European patent application EP 0598504, teaches a system and a method by which network printer statistics is collected and stored in a central logging device. The statistics collected relate to times of usage and number of pages used. SUMMARY OF THE INVENTION Accordingly, an object of the present invention is to address and resolve such problems and provide a network system including a print log generating device provided in a client computer for generating print log having printer usage contents when a printing request is made in the client computer, a print log storing device for storing the print log therein, a collecting device for collecting the print log in a computer server, and an aggregating device for aggregating the usage contents per prescribed category. In another aspect of the present invention, a display apparatus configured to display a result of the aggregation is connected to the network. In still another aspect of the present invention, a name of the printer, a print requesting time period and a name of an application are included in the printer usage contents. In still another aspect of the present invention, the category is a time zone when a print request is made, or an application, with which a printer is used. In still another aspect of the present invention, the print log generating device and the print log-storing device are provided in the client computer. In still another aspect of the present invention, the collecting device is provided in the computer server. In still another aspect of the present invention, the collecting device periodically collects print log from the client computer. In still another aspect of the present invention, the aggregating device is provided in the supervisor computer. In still another aspect of the present invention, the display device is provided in the supervisor computer. BRIEF DESCRIPTION OF THE DRAWINGS A more complete appreciation of the present invention and many of the attendant advantages thereof will be readily obtained as the same becomes better understood by the following detailed description when considered in connection with the accompanying drawings, wherein: Fig. 1 is a block diagram illustrating one example of a schematic system composition of a network system of the present invention; Fig. 2 is a block diagram illustrating electrical connection in a PC, such as a server PC, a client PC and a supervisor PC, of the network system; Fig. 3 is a flowchart illustrating an operation of the client PC for collecting print log; Fig. 4 is a block diagram illustrating a constitution of the print log; Fig. 5 is a flowchart illustrating an operation executed in the client PC for setting user information; Fig. 6 is a conceptual diagram illustrating relation between a software and log data stored in the client PC; Fig. 7 is a flowchart illustrating an operation of the client PC for periodically transmitting print log to the server PC; Fig. 8 is a flowchart illustrating an operation of the server PC for periodically receiving print log from the client PC; Fig. 9 is a plan view illustrating one example of an operation screen displayed on a displaying apparatus of the supervisor PC; Fig. 10 is a flowchart illustrating an operation of the supervisor PC for taking in print log; Fig. 11 is a flowchart illustrating an operation of the server PC for transmitting print log to the supervisor PC; Fig. 12 is a plan view illustrating an example of print log stored in the supervisor PC and displayed on the displaying apparatus of the supervisor PC; Fig. 13 is a plan view illustrating an exemplary image of a screen display displaying a result of aggregation, which is executed by the supervisor PC, of usage contents of a printer per department; Fig. 14 is a plan view illustrating an exemplary image of a screen display displaying a result of aggregation, which is executed by the supervisor PC, of usage contents of a printer per printer; Fig. 15 is a plan view illustrating an exemplary image of a screen display displaying a result of aggregation, which is executed by the supervisor PC, of usage contents of a printer per application; Fig. 16 is a plan view illustrating an exemplary image of a screen display displaying a result of aggregation, which is executed by the supervisor PC, of usage contents of a printer per time zone; Fig. 17 is also a plan view illustrating an exemplary image of a screen display displaying a result of aggregation, which is executed by the supervisor PC, of usage contents of a printer per time zone; and Fig. 18 is also a plan view illustrating an exemplary image of a screen display displaying a result of aggregation, which is executed by the supervisor PC, of usage contents of a printer per time zone. DESCRIPTION of THE PREFERRED EMBODIMENTS Referring now to the drawing, wherein like reference numerals designate identical or corresponding parts throughout several views. Fig 1 is a block chart illustrating a skeleton of a system constitution of a network system 1 as one embodiment of the present invention. As illustrated in Fig. 1, a server personal computer (hereinafter referred to as a server PC) 3, a plurality of client personal computers (hereinafter referred to as client PCs) 4, 4, and a supervisor personal computer (hereinafter referred to as a supervisor PC) 5 as one of client PCs 4 may be respectively connected to a LAN (Local Area Network) 2 as a network in this network system 1. Further, a plurality of printers 7, 7 and may be respectively connected to the LAN 2 either directly or via a printer server 6 (or other PC) as a host computer. Fig. 2 is a block chart explaining electrical connection in the server PC 3, the client PC 4 and the supervisor PC 5. As illustrated in Fig. 2, in each PC 3, 4 and 5, a CPU (Central Processing Unit) 8 may be connected to a memory section 9 as a memorizing apparatus such as a ROM (Read Only Memory), a RAM (Random Access Memory), with a bus 10. Further, a CD-ROM (Compact Disc-Read Only Memory) drive control section 12 for controlling a CD-ROM drive 11 which reads a CD-ROM as a memorizing medium, and an input/output control section 15 for controlling both an input apparatus 14, such as a keyboard and a mouse, and a displaying apparatus 13, such as CRT (Cathode Ray Tube), may be connected to the bus 10. Also, a hard disc control section 17 for controlling a hard disc 16 and a LAN control section 19 for connecting the PCs 3, 4 and 5 may be connected to the LAN 2. An operation system (hereinafter referred to as an OS), such as windows95/98 and Windows NT (TMs of Micro Soft Company Limited), and a variety of applications operable on the OS may be stored in each hard disc 16 of the server PC 3, client PC 4 and supervisor PC 5. Especially, a later mentioned printer-print-log-supervising tool may be utilized as one of applications. Namely, client use software of the printer print log-supervising tool may be stored in the client PC 4 from the CD-ROM 18 stored in the CD-ROM drive 11. Also, server use software of the printer print log-supervising tool may be stored in the server PC 3 from the CD-ROM 18 stored in the CD-ROM drive 11. Further, supervisor use software of the printer print log-supervising tool may be stored in the supervisor PC 5 from the CD-ROM 18 stored in the CD-ROM drive 11. In the above-mentioned network system 1, an operation executed by the client PC 4 according to the client use software of the printer print log-supervising tool is explained. Fig. 3 is a flowchart illustrating such an operation. Firstly, when printing by a printer 7 is requested (in step S4) in a client PC 4 (i.e., yes in step S1), print log information may be collected (in step S2), and may be registered in a print log area 20 (refer to Fig. 2) constituted within the hard disc 16 of the client PC 4 with it being edited (in step S3). Fig. 4 is a block chart illustrating a constitution of the print log. As illustrated in Fig. 4, the print log 21 may be constituted with a user name 22, a user belonging department name 23, a PC name 24 of the user using client PC 4, log server information 25, and other log information 26. Among those, the name 22, the department name 23, the PC name 24 and the log server information 25 may be respectively constituted with user information set by a user using the supervisor PC 5. Fig. 5 is a flowchart for illustrating a setting operation for setting the user information. Namely, when user information setting command is inputted with an inputting apparatus 14 of the supervisor PC 5 (i.e., Yes in step S11), a user information inputting/setting screen may be displayed on a display apparatus 13 (in step S12). After that, when the user inputs a name 22, a department name 23, and log server information 25 according to instruction of the inputting/setting screen (i.e., Yes in step S13), a PC name 24 of the client PC 4 may then be read (in step S14). These set data, i.e., the name 22, the department name 23, the log server information 25 and the PC name 24 may be displayed on the display apparatus 13 (in step S15). If the set contents are correct, i.e., the user executes a prescribed operation with the inputting apparatus 14 according to the instruction on the screen (i.e., Yes in step S16), the data of the name 22, the department name 23, the log server information 25 and the PC name 24 may be stored in a prescribed area of a hard disc 16 (in step S17). If the set contents are not correct, i.e., the user executes a prescribed operation with the inputting apparatus 14 according to the instruction on the screen in a manner different from the above (i.e., No in step S16), the process returns to step S12 and an operation may be replayed. Such a setting operation for setting user information can be executed with a supervisor use software as (of) a printer print log supervising tool with the supervisor PC 5. A variety of log data may be included in the other log information 26. However, a variety of log data can be collected from software stored in the hard disc 16 or the like of the client PC 4. Fig. 6 is a conception-illustrating diagram illustrating a specific operation for collecting log data of print log. Namely, when an OS is Windows 95 or 98 and print data is conveyed from an application to a printer driver via GDI, information as to the followings can be obtained. Namely, a user name, a computer name, a printer name, a printer driver name, an output destination port name, a document name, an application name, a number of print pages, sheet size, sheet direction, print resolution, monochrome/color distinction, simplex/duplex distinction, and a number of units. As information obtainable from spooler, information as to the followings can be obtained when the OS is Windows 95 or 98. Namely, print data size, a print requesting time period, a print start time period, a print terminating time period, status, an output form, a print processor and priority. When the OS is Windows NT 4.0, information as to the followings can be obtained. Namely, a user name, a computer name, a printer name, a printer driver name, an output destination port name, a document name, an application name, a number of print pages, sheet size, sheet direction, print resolution, monochrome/color distinction, simplex/duplex distinction, and a number of units, print data size, a print requesting time period, a print start time period, a print terminating time period, status, an output form, a print processor and priority. The print log collected in step S2 and stored in the print log area 20 of the client PC 4 in step S4 may be periodically transmitted to the server PC 3. Next, such an operation is described below. Fig. 7 is a flowchart illustrating an operation of the client PC 4 for periodically transmitting print log to the server PC 3. As illustrated in Fig. 7, when a prescribed time has elapsed (i.e., Yes in step S21), inquiry whether no problem may occur if log data is transmitted is made to the server PC 3 (in step s22). This inquiry may be repeated (i.e., NO in step S23) until the server PC 3 responds (in later mentioned step S32). If the response is made (i.e., Yes in step S23), log data of the print log may be transmitted (in step S24). Fig. 8 is a flowchart illustrating an operation of the server PC 3 for periodically receiving the print log from the client PC 4. Namely, as illustrated in Fig. 8, when inquiry (in step S22) is made from the client PC 4 (in step S31), it may return a response representing that collection of log data is commenced to the client PC 4 (in step S32). Then, it may receive the log data of the print log from the client PC 4 (in step S33), and may store the print log in a print log area 20 (refer to Fig. 2) constituted in the hard disc 16 of the server PC 3 (in step S34). Such operation may be repeated until the final log (i.e., No in step S35). The process may return to step S31 when the final log data has been stored in the print log area 20 (i.e., Yes in step S35). Further, the print log may be directly made into database when it is stored in the print log area 20 of the server PC 3. Thus, a collecting device can be realized by the above-mentioned operation executed in step S34. Fig. 9 illustrates an example of an operation screen displayed on a displaying apparatus 13 of the supervisor PC 5 using supervisor use software as (of) a printer print log supervising tool. This supervisor use software may operate on the Windows 98. The supervisor PC 5 may start an operation illustrated in Fig. 10 when an intake icon 31 is clicked through the operation screen illustrated in Fig. 9. Namely, as illustrated in Fig. 10, an inquiry as a request for transmitting log data may be made to the server PC 3 (in step S41). This inquiry may be repeated (i.e., No in step S42) until a response is made from the server PC 3 (in later mentioned step S52). When the response is made (i.e., Yes in step 42), log data of print log may be received (in step S43) and stored in a print log area 20 (refer to Fig. 2) constituted in a hard disc 16 of the supervisor PC 5 (in step S44). An operation executed by the server PC 3 in the above-mentioned situation is now described. Namely, as illustrated in Fig. 11, when inquiry (in the above-mentioned step S41) is received from the supervisor PC 5 (i.e., Yes in step S51), it may return a response indicating about start of collecting print log (in step S52). Then, it may transmit the log data of the print log stored in the print log area 20 of the server PC 3 to the supervisor PC 5 (in step S53). This transmission is continued until the final log (i.e., No in step S54), a process may return to step S51 when the final log has been transmitted (i.e., Yes in step S54). Fig. 12 illustrates an example of a display of print log (having been made into database in the server PC 3) stored in the print log area 20 of the supervisor PC 5 is displayed on the displaying apparatus 13 of the supervisor PC 5. In the screen illustrated in Fig. 12, usage contents of the printer 7 can be aggregated as desired when one of the following icons is clicked and the operation illustrated in Fig. 10 is executed based on the log data of the print log stored in the print log area 20 of the supervisor PC 5. Such icons may include a department icon 32, a printer icon 33, an application icon 34, and a time zone icon 35. Namely, an aggregation device can be realized. Firstly, a prescribed wizard screen may be displayed when the department icon 32 is clicked. Usage contents of a printer 7 may be aggregated per department of a business establishment employing the network system 1 based on print log collected by the server PC 3, when an operation is executed according to instruction of the wizard display. Fig. 13 illustrates an example of an image of a screen display displaying the result of the aggregation per department. An aggregation result of a third development department may be displayed in the example of Fig. 13. Further, when the printer icon 33 is clicked, a prescribed wizard screen may be displayed. Usage contents of a printer 7 may be aggregated per printer connected to the network system 1 based on print log collected by the server PC 3, when an operation is executed according to instructions of the wizard screen. Fig. 14 is an example showing an image of a screen display displaying a result of the aggregation per printer 7. In the example of Fig. 14, an aggregation result of a printer named A may be displayed. Further, when the application icon 34 is clicked, a prescribed wizard screen may be displayed. Usage contents of a printer 7 may be aggregated per application utilized in the network system 1 based on print log collected by the server PC 3, when an operation is executed according to instruction on the wizard screen. Fig. 15 is an example showing an image of the screen display displaying a result of the aggregation per application. In the example of Fig. 15, aggregation results of applications of a word processor A and a table calculation B may be displayed. Further, when the time zone icon 35 is clicked, a prescribed wizard screen may be displayed. Usage contents of the printer 7 may be aggregated per time zone based on print log collected by the server PC 3, when an operation is executed according to instruction on the wizard screen. Aggregation can be executed in three ways when a prescribed operation is executed on the wizard screen. Namely, first, print requesting time periods included in print log as log data are classified into time zone sorts, and a number of printed pages printed during applicable term can be accumulated and aggregated. Fig. 16 is an example showing an image of a screen display showing an aggregation result in the case. Second, print requesting time periods included in print log as log data may be classified into time zone sorts, and an operation rate during an applicable term can be aggregated in average. Fig. 17 is an example showing an image of a screen display showing an aggregation result in the case. The operation rate may be calculated as follows and represented by percentage. [(Accumulated print operating time period) / (A period of a time zone) x (A number of aggregation executed days)] x 100 Third, print requesting time periods included in print log as log data may be classified into time zone sorts, and an average and maximal value of a waiting time period during an applicable term can be aggregated. Fig. 18 is an example showing an image of the screen display showing an aggregation result in the case. The average may be calculated as follows and represented by second. (Accumulated print waiting time period / a number of printed times) According to the above described network system 1, since usage contents of a printer 7 can be aggregated per time zone based on print log collected, a time zone when the printer 7 is frequently utilized can be readily seized. Further, since usage contents of a printer 7 can be aggregated per application utilized in the network system 1 based on collected print log, an application, with which the printer 7 is frequently utilized, can be readily seized. Since the invention described in claim 1 can aggregate usage contents of a printer per time zone based on collected print log, a time zone when a printer is frequently used can be readily seized. Since the invention described in claim 2 can aggregate usage contents per application utilized in a network of a printer, an application, with which a printer is frequently utilized, can be readily seized. Since the invention claimed in claim 3 can aggregate usage contents per time zone, a time zone when a printer is frequently utilized can be readily seized. Since the invention claimed in claim 4 can aggregate usage contents per application utilized in the network of a printer, an application, with which a printer is frequently utilized, can be readily seized. The invention claimed in claim 5 can aggregate usage contents based on collected print log per time zone, a time zone when a printer is frequently utilized can be readily seized. Since the invention claimed in claim 6 can aggregate usage contents based on print log collected in a network system of a printer, an application with which a printer is frequently utilized can be readily seized. Numerous additional modifications and variations of the present invention are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims, the present invention may be practiced otherwise that as specifically described herein. The print log represents in particular a summary of printer activity in connection with a print request. The printer activity may be categorized for example in the following categories: Number of pages printed, monochrome or color print out, time needed to print out or to execute the print requests, kind or size of sheets used (paper sheets or film), amount of printing material (e.g. toner or ink) used, the date and time of usage, duration of usage, time zone of usage, name of user, departments, and/or workstation, etc. The summary of the printer activities preferably represent information about the usage of the printer and represents in particular "usage contents". In particular the "print log" has "usage contents" relating to a particular print request for a particular user or relating to a particular print activity. A collecting device preferably collects the print logs. The information in the print logs (usage contents) of the collected print logs is preferably arranged in accordance to print logs. Advantageously a "aggregation device" is provided which sorts and/or collects the usage contents such that the usage contents is categorized according to particular categories which may be predefined. In particular, different categories may be related to each other and the number of invents belonging to certain categories, which are related to each other, may be calculated. For instance, the number of print outs may be calculated which are related to a particular user, which are monochrome and which have been performed in a particular time zone. Thus the aggregation device allows to give a survey about particular categories. In particular, intersections between different categories may be calculated and displayed. Further embodiments of advantage are as follows: A network system, in which a server, a client and a printer are connected to a network, characterized in that it includes a collecting device for collecting print log of the each client and an aggregating device for aggregating usage contents of the printer per time zone based on the collected print log. A network system, in which a server, a client and a printer are connected to a network, characterized in that it includes a collecting device for collecting print log of the each client and an aggregating device for aggregating usage contents of the printer per application based on the collected print log. A printer supervising method for aggregating usage contents of a printer in a network system, in which a server, a client and a printer are connected to a network, characterized in that said aggregation is executed per time zone based on the collected print log. A printer supervising method for aggregating usage contents of a printer in a network system, in which a server, a client and a printer are connected to a network, characterized in that said aggregation is executed per application based on the collected print log. A memorizing medium readable for a server and a client and storing program for enabling the server or the client aggregates usage contents of a printer in network system, in which a server, a client and a printer are connected to a network, based on print log collected from the each client, characterized in that said aggregation is executed per time zone. A memorizing medium readable for a server and a client and storing program having the server or the client aggregates usage contents of a printer in network system, in which a server, a client and a printer are connected to a network, based on print log collected from the each client, characterized in that said aggregation is executed per application utilized in the network system of the printer.

Claims: A network system including at least one computer server (3), at least one client computer (4) having a printer (7) and at least one supervisor computer (5) respectively connected to a network, said network system comprising: a print log generating device configured to generate (9) print log (21) having printer usage contents when a printing request is made in at least one client computer; a print log storing device configured to store the print log; a collecting device configured to collect said print log; the network system characterised by : an aggregating device configured to aggregate usage contents of the printer per prescribed category; and a display apparatus (13) configured to display a result of the aggregation, wherein said printer usage contents include a name of the printer, a print requesting time period and a name of an application. A network system as claimed in claim 1, wherein, said category is a time zone when a print request is made. A network system as claimed in claim 1, wherein, said category is an application, with which a printer is used. A network system as claimed in claim 1, wherein, said print log generating device and the print log storing device are provided in the at least one client computer. A network system as claimed in claim 1, wherein, said collecting device is provided in the at least one computer server. A network system as claimed in claim 4, wherein, said collecting device periodically collects print log from said client computer. A network system as claimed in claim 1, wherein, said aggregating device is provided in the at least one supervisor computer. A network system as claimed in claim 1, wherein, said display device (13) is provided in the at least one supervisor computer. A method for aggregating usage contents of a printer of each client computer connected to a network system, comprising steps of: generating a print log having printer usage contents when a print request is made in a client computer; storing said print log; collecting said print log; said method characterised by the steps of: aggregating usage contents of the printer per prescribed category; and displaying a result of said aggregation, wherein said printer usage contents include a name of the printer, a print requesting time period and a name of an application. A method as claimed in claim 9, wherein said category is a time zone when a printer is utilized. A method as claimed in clam 9, wherein, said category is an application, with which a printer is utilized. A computer readable medium for at least one computer server, at least one client computer and at least one supervisor computer respectively connected to a network system, having a program recorded thereon, where the program is to make the at least one client computer to generate a print log having printer usage contents, to make the at least one server computer to collect said print log from the at least one client computer and to make the at least one supervisor computer to aggregate the printer usage contents per prescribed category and to make a display apparatus to display a result of the aggregation, wherein said printer usage contents include a name of the printer, a print requesting time period and a name of application. A medium as claimed in claim 12, wherein said category is a time zone when a print request is made. A medium as claimed in claim 12, wherein said category is an application, with which a printer is used. Program which, if loaded in a computer or when running on a computer, performs the method as claimed in claims 9 to 11.

Inventors: OKADA YASUSHI, OKADA, YASUSHI
Applicants: RICOH KK, RICOH COMPANY, LTD.
Application year: 2000
Main classification: H04L29
IPC codes: G06F11, G06F13, H04L29, G06F3, B41J29