JP2004178324A - Information processing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enhance the degree of freedom of analyzing and displaying a printing state, thereby reducing the burden of totaling of a utilization state and ensuring easy effective understanding of the printing state. <P>SOLUTION: The information processing system comprises an information processing client which issues a job to an image processing device and generates job information on the job, and an information processing server which acquires the job information from the information processing client and records the job information therein. The information processing client allows a dialog 2601 for promoting the input of a management code for the job to be displayed, and transmits the management code and the job information to the information processing server. The information processing server acquires the management code and the job information from the information processing client, and counts the job information based on the acquired management code. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a technique for managing job information.
[0002]
[Prior art]
2. Description of the Related Art Conventionally, a job management method for an information processing system that acquires and manages job information has been developed, and job information executed by a peripheral device has been collected.
[0003]
In general, the job information collected as described above is displayed in a table or a graph, and is used for grasping and examining a use situation (for example, see Patent Document 1). When displaying in a table or a graph, the usage status (number of prints, paper size, paper type, etc.) is displayed for each user or department. Further, attributes such as "department" and "affiliation" are defined, users are grouped by the attribute, and the use status is displayed in a table or a graph in units of the attribute.
[0004]
[Patent Document 1]
JP-A-2002-116899 [0005]
[Problems to be solved by the invention]
However, there is a case where the totaling and displaying in units of users or in units of “department” and “affiliation” to which the user belongs is not enough.
[0006]
For example, law firms and the like usually perform business management such as summing up the printing costs incurred for each job, and there is a need to redo the counting for each job from the counting result for each user who performed printing. I will. In addition, since the user who has performed the printing is not always engaged in the job, it has been difficult to determine which job to print from the user information.
[0007]
SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned problems, and reduces the load of the use status tallying process by increasing the degree of freedom in analyzing and displaying the printing status, and easily and effectively grasping the printing status. The purpose is to do.
[0008]
[Means for Solving the Problems]
In order to achieve the above object, a system according to the present invention comprises:
An information processing client that generates a job for the image processing apparatus and generates job information related to the job;
An information processing server that acquires and records the job information from the information processing client;
An information processing system including
The information processing client,
Display control means for displaying a screen for designating a management code usable by the user in response to a print instruction from the user;
Transmission means for transmitting the management code and the job information input on the screen displayed by the display control means to the information processing server,
Has,
The information processing server,
Acquiring means for acquiring the management code and the job information from the information processing client;
Tabulation means for tabulating the job information based on the management code acquired by the acquisition means,
It is characterized by having.
[0009]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, preferred embodiments of the present invention will be illustratively described in detail with reference to the drawings. However, the components described in this embodiment are merely examples, and are not intended to limit the scope of the present invention only thereto.
[0010]
<System configuration>
FIG. 1A is a diagram illustrating an example of an information processing system as a preferred embodiment in which an information processing method according to the present invention can be implemented.
[0011]
The information processing system includes at least one information processing client, one information processing server, and one image processing apparatus. However, in FIG. 1A, client computers 1001 to 1003 are used as first information processing apparatuses, and second computers are used as second information processing apparatuses. A server computer 2000, printers 108 to 110 as an image processing apparatus, a facsimile, a copier, and an MFP (multifunction printer) having these functions in combination are exemplarily illustrated.
[0012]
These devices are connected by a local area network (hereinafter simply referred to as a network) 3000 constructed by Ethernet (registered trademark) or the like, and can communicate with each other.
[0013]
The client computers 1001 to 1003 are used by each user. The server computer 2000 is a control computer that manages the client computer 1001 and the printer 110 existing on the network 3000 and remotely controls the client computer 1001 and the printer 110. The difference between the client computers 1001 to 1003 and the server computer 2000 is that a job account client program (to be referred to as a job account client hereinafter) is executed on the device, or a job account server program (to be referred to as a job account server program hereinafter). Job account server) is executed, and there is no difference in hardware.
[0014]
As will be apparent from the description below, the server computer 2000 is for management by an administrator, and the users such as the client computers 1001 to 1003 do not need to know the existence.
[0015]
Although three client computers are shown in the figure as client computers used by general users, the number of the client computers is not limited to this number. A plurality of computers may be connected to the network 3000, or they may not be connected to a printer.
[0016]
Although various types of image processing apparatuses may be included in the present system, in the present embodiment, the printers 108 to 110 will be specifically described as examples.
[0017]
The printer 108 has a function of printing data received from the client computers 1001 to 1003, but does not have a function of outputting information of a job performed by the printer 108 to an external device.
[0018]
It is assumed that the printer 109 has a function of notifying the client computers 1001 to 1003 of a print result such as the total number of discharged pages relating to the job at the end of the job, in addition to the function of the printer 108.
[0019]
The printer 110 has a function of storing job information in a memory in the printer after printing, and outputting the job information in response to a request from the server computer 2000.
[0020]
The server computer 2000 records a job log handled by a client computer via the network 3000, selects a specific job log in response to a request from a browsing applicant, and selects by unit period, device, and job issuer. And so on.
[0021]
In the present embodiment, TCP / IP is used as the protocol of the network 3000. However, any protocol may be used as long as the following functions are realized.
[0022]
<System software configuration>
FIG. 1B is a diagram illustrating a software configuration of the information processing system.
[0023]
The client computers 1001 to 1003 include an application 102, a hook module 103, a GDI 104 (a subsystem for processing graphic drawing), a printer driver 105, a spooler 106, a transmission / reception module 107, and a job account client 118.
[0024]
Among these, the application 102 is an image processing application that captures or processes image data, a word processor application that creates document data, and the like, and operates on an operation system (not shown). The GDI 104 and the transmission / reception module 107 are modules included in the operation system. Further, the printer driver 105 is a program prepared by a printer maker according to the printer controlled by the client computers 1001 to 1003, and operates in a bridge between the printers such as the printers 108 to 110 and the application 102. The spooler 106 is a temporary storage area secured by the printer driver 105.
[0025]
On the other hand, the server computer 2000 includes a job account server 121. The job account server 121 includes a job log merge module 123, a job log storage module 124, a job log reception module 122, a job log totalization module 125, an ID generation module 126, Includes non-target database 129.
[0026]
Next, operations in the client computers 1001 to 1003 and the server computer 2000 will be described.
[0027]
When the client computer 1001 to 1003 issues a print instruction to the application 102, the application 102 makes a GDI call for drawing.
[0028]
The hook module 103 is incorporated together with the job account client 118, and hooks (monitors and recognizes) GDI calls and accumulates information such as which GDI call was called with what parameters and the number of times called. For example, the number of discharged sheets or the number of pages of the job issued by the application 102 is acquired by counting an API (application programming interface) for performing a page break or discharging. The history created based on this information is passed to the job account client 118 as the hook log 111. The hook module 103 can also change the document name based on a prescribed criterion. The document name and this change processing will be described later.
[0029]
FIG. 7 is a diagram illustrating an example of the hook log 111. In the hook log, JobId, application name, number of logical pages, and document name can be acquired. The JobId can be acquired from the GDI when instructing the GDI to start printing, and can uniquely specify a print job of the client computers 1001 to 1003.
[0030]
Referring back to FIG. 1B, the printer driver 105 converts the GDI call into print data that can be interpreted by the printer according to the print settings, passes the print data to the spooler 106, extracts print information from the converted contents, and outputs the print information as a driver log 112 as a job account client. Hand over to 118.
[0031]
FIG. 8 is a diagram showing an example of the driver log 112. The driver log 112 is history information that the job account client can acquire from the driver when printing is performed. As the driver log 112, it is possible to acquire JobId, which is an identifier of a job related to print execution, paper size of print data included in the job, N-up information, information on the number of physical pages, and information on both sides and one side. The paper size, N-up, number of physical pages, and single-sided and single-sided information are acquired from the print settings set by printing to the printer driver or by default. N-up is a setting of how many logical pages are allocated to a sheet. The number of physical pages is a unit for counting one side of a sheet output at the time of printing as 1.
[0032]
For example, if there are four logical pages and 2-up printing processing is performed in double-sided printing, the number of physical pages becomes two. Then, the physical page is printed on the front and back of the sheet, and one sheet is output and discharged. The first and second logical pages are printed on the table, and the third and fourth logical pages are printed on the back.
[0033]
Referring back to FIG. 1B, the job account client 118 periodically monitors the spooler and, if there is a spooled job, obtains the information of the job by using the API to obtain the number of sheets discharged or the number of pages of the job. To get. The obtained job information is passed to the job account client 118 as the API log 113.
[0034]
FIG. 9 is a diagram illustrating an example of the API log 113. As the API log 113, a JobId, a job owner name (user name), and a spool data size can be acquired.
[0035]
The transmission / reception module 107 communicates with one of the printers designated by the application, such as the printers 108 to 110, and transmits print data when the printer is in a ready state. At this time, for example, if a command of Printer Job Language (HP) is used, it is possible to acquire the number of pages ejected by the job after the printer 109 completes ejection of all pages of the print job. It is possible. The transmission / reception module 107 (port monitor) 107 sends job information such as the number of pages received from the printer 109 to the job account client 118. A print log created based on this information is called a monitor log 114.
[0036]
FIG. 10 is a diagram illustrating an example of the monitor log 114. JobId can be acquired as the monitor log 114. When transmitted to the printer 108, the number of discharged pages and the number of discharged sheets can be additionally obtained.
[0037]
In each of the hook log 111, the driver log 112, the API log 113, and the monitor log 114, an area for recording flag information indicating whether the job has been processed and information indicating the type of log are provided.
[0038]
The job account client 118, which is a software module executed by the CPU in the client computer, includes a job log merge module 116 and a job log transmission module 117 for collecting logs related to various printing processes and transmitting the logs to the job account server 121. .
[0039]
The job log merge module 116 in FIG. 1B merges the hook log 111, the driver log 112, the API log 113, and the monitor log 114, and usually sends a merge log 127 to the job log transmission module 117 every time the merge processing is completed. FIG. 12 is a diagram illustrating an example of the merge log 127 when the logs illustrated in FIGS. 7 to 10 are merged. As shown in the drawing, the merge log 127 includes items of a hook log 111, a driver log 112, an API log 113, and a monitor log 114, and a management code. The job information in FIG. 12 includes the job ID issued for the job, the name of the application that generated the document included in the job, the number of logical pages of the job, the document name included in the job, the start time of the job, and the job start time. End time, paper size used by the job, number of N-UPs used in the job, number of physical pages of the job, whether the job uses double-sided printing or single-sided printing, job owner name (user name), etc. Of the job. These total information is used by the job account server to perform total processing for each user, each department, and each management code.
[0040]
Although the management code is shown as being included in the merge log 127 here, the present invention is not limited to this. Job information such as the number of pages and the management code are separately stored in the server computer 2000. May be sent. In that case, the management code is not included in the merge log 127, and the job log merge module 123 of the server computer 2000 merges the management code with another log to generate the final log 128.
[0041]
The job log transmission module 117 transmits the log to the job log reception module 122 periodically or in response to a request from the job log reception module 122. At this time, the job log transmitting module 117 may transmit the log to the job log receiving module 122 by controlling the transmitting / receiving module 107 provided by the OS. Note that the job account client 118 may set a priority order to select any of the hook log 111, the driver log 112, the API log 113, and the monitor log 114, and may transmit any of them to the job account server 121. it can.
[0042]
Next, the operation of the job account server 121 will be described.
[0043]
The job log receiving module 122 acquires and accumulates the job transmitted from the job log transmitting module 117. When a network printer such as the printer 110 that internally stores job information exists on a network, the job log receiving module 122 defines the protocol with the printer and communicates with the printer, thereby directly transmitting the job information from the printer to the device. It can be obtained as the log 115.
[0044]
In other words, the printer 110 periodically polls the printer 110 and, if there is any job information that has not been acquired yet, acquires it as the device log 115. Although the device log 115 is stored in the RAM or the HD in the printer 110, it is not desirable to store all information such as the document name transmitted from the transmission / reception module 107 to the printer due to the limitation of the storage capacity. FIG. 13 is a diagram illustrating an example of the device log 115 when a job is transmitted from the client computer on which the hook module 103 operates to the printer 110. FIG. 14 is a diagram illustrating an example of the device log 115 when a job is transmitted to the printer 110 from a client computer on which the hook module 103 does not operate.
[0045]
The job log merge module 123 merges the merge log 127 sent from the job account client with the device log 115 to generate a final log 128. FIG. 17 is a diagram showing an example of the final log 128 when the merge log 127 shown in FIG. 12 and the device log 115 shown in FIG. 13 are merged.
[0046]
The job log storage module 124 receives the final log 128 from the job log merge module 123, refers to the non-processing target database 128, and stores it in the HD 206 or the like if it is not a processing target. The job log totaling module 125 performs totaling processing such as obtaining the number of print pages for each unit period or obtaining the number of print pages for each owner according to an instruction from the viewer.
[0047]
The ID generation module 126 issues an ID for uniquely identifying the client computers 1001 to 1003. Here, a four-digit character string in which each digit can take 26 values from a to z is changed in the order of aaa, aaab, ..., zzzy, zzzz in accordance with the request of the hook module 103, and the client Issue so that it can be uniquely identified. Here, the new document name is created using a combination of the host and the job ID. However, a method may be adopted in which a unique new document name (to be described later) unique to the entire printing system is unified by the job account server.
[0048]
Here, in the client computers 1001 to 1003, four logs of the hook log 111, the driver log 112, the API log 113, and the monitor log 114 are created for one print job. There is not always one log. For example, if the application 102 sends print data directly to the spooler 106, the hook log 111 and the driver log 112 cannot be obtained. If a protocol is not defined between the printer driver 105 and the job account client 118, the driver log 112 cannot be obtained. If there is no function of notifying the transmission / reception module 107 of the number of discharged pages as in the printer 108, the discharged page information of the monitor log 114 cannot be obtained. However, by acquiring a log in a plurality of processes related to a job, even if it is impossible to acquire a log in a part of the process, the probability of acquiring the log is increased overall.
[0049]
In the information processing system as described above, whether the log as the job information acquired from the client computers 1001 to 1003, the printer 110, or the like should be recorded based on the log generation process (port information or driver information). Is determined, and only the log determined to be subjected to the recording process is recorded in the server computer 2000.
[0050]
<Hardware configuration of each computer>
FIG. 2 is a block diagram illustrating an example of a hardware configuration of any of the client computers 1001 to 1003 and the server computer 2000. As described above, the client computers 1001 to 1003 and the server computer 2000 do not differ in the basic hardware configuration, and each computer has the following configuration.
[0051]
In FIG. 2, reference numeral 201 denotes a CPU, that is, a central processing unit, which controls the entire computer and performs arithmetic processing. Reference numeral 202 denotes a ROM, that is, a read-only memory, which is a storage area for storing information of a system startup program. Reference numeral 203 denotes a RAM, that is, a random access memory, which is a data storage area with no usage restriction. A keyboard control unit (KBC) 204 receives input data from the keyboard and transmits the data to the CPU 201. A display control unit 205 controls display on a CRT, a liquid crystal display, or the like. Reference numeral 206 denotes an HD, that is, a hard disk. The HD 206 stores and stores programs and data, and references or loads them to the RAM 203 as needed at the time of execution. A communication unit 207 is used for communication with other computers and peripheral devices connected to the network. The communication unit 207 is controlled by the transmission / reception module 107, the job log transmission module 117, and the like in FIG. Reference numeral 208 denotes a system bus, which is a data path between the hardware described above.
[0052]
The application 102, the hook module 103, the GDI 104, the printer driver 105, the transmission / reception module 107, the software module such as the job account client 118, and the operation system and the communication control program shown in FIG. 1B are loaded into the RAM 203 from the HD 205 and the ROM 202. , Is executed by the CPU 201.
[0053]
Note that another storage device may be provided instead of the HD 205 shown in FIG. 2 or in addition to the HD 205. As another storage device, a nonvolatile storage memory or the like can be considered.
[0054]
<Hardware configuration of each printer>
FIG. 3 is a block diagram illustrating an example of a configuration of the printers 108 to 110 configuring the information processing system. In FIG. 3, reference numeral 305 denotes a controller for controlling the entire printer. The controller 305 includes a CPU 301, a ROM 302, a RAM 303, and an HD 304.
[0055]
The CPU 301 is a central processing unit that controls the entire printer, performs arithmetic processing, and the like. The ROM 302 is a read-only memory and includes a storage area for information on a system startup program and the like. The RAM 303 is a random access memory and includes a data storage area with no usage restriction. The HD 304 is a hard disk, and includes a storage area for securing programs and data that may be rewritten even after the printer power is turned off.
[0056]
The RAM 303 has a storage area in which programs such as an operating system and communication control and engine control are loaded and executed. The print engine 306 performs a printing operation and an image reading operation under the control of the controller. The communication unit 307 communicates with a client computer or a server computer via a network. The operation unit 308 is a unit for performing an interactive setting operation with the user. The system bus 309 is to be a data path between the above-described components.
[0057]
<RAM Configuration of Server Computer and Its Realization Method>
FIG. 4 is a diagram showing the memory map 40 in the RAM 203 inside the client computer 1000.
[0058]
In the server computer 2000, the basic I / O program 41, the operating system 42, and the application 102 are loaded into the RAM 203 as shown in FIG. In the RAM 203 of the server computer 2000, in addition to the above, related data 44 generated as a result of the execution of the application 102 is stored, and a work area 45 used by another program is prepared.
[0059]
The software configuration of the server computer 2000 as shown in FIG. 1B can be realized by installing the job account server 121 from outside. As a method of installation, in addition to a method of downloading via a network such as the Internet, a method of installing from a portable removable storage medium can be adopted.
[0060]
For example, as shown in FIG. 6, a method of reading the CD-ROM 60 into the CD-ROM drive 208 of the server computer 2000 corresponds to this. In this case, as shown in FIG. 5, in the storage area 50 of the CD-ROM 60, volume information 51, directory information 52, an execution file 53, and a related data file 54 are recorded.
[0061]
The execution file 53 includes an installation program of the job account server 121.
[0062]
When the CD-ROM 60 is set in the CD-ROM drive 61, the execution file 53 is executed under the control of the operating system 42 and the basic I / O program 41, and a program module for realizing the job account server 121 and the like. The relevant data is read from the CD-ROM 60 and stored in the HD 206. Here, the program modules for realizing the job account server 121 include the modules 122 to 126 shown in FIG. 1B.
[0063]
Of course, the storage medium is not limited to a CD-ROM, but may be a DVD, FD, or the like.
[0064]
<Operation of hook module>
FIG. 15 is a flowchart showing the processing performed by the hook module 103.
[0065]
In step S1501, the hook module 103 acquires and determines whether or not the printer at the printing destination has the device log according to a predetermined device management protocol. Proceed to. If the hook module 103 determines that the printer does not have the device log, the process ends.
[0066]
In step S1502, the hook module 103 determines whether or not the client ID has been obtained. If the client ID has been obtained, the process proceeds to step S1504. If not, the process advances to step S1503. Here, the client ID is identification information issued by the ID generation module 126 and capable of uniquely identifying the client computers 1001 to 1003. Here, in step S1503, it is assumed that the hook module 103 communicates with the ID generation module 126 and acquires an ID for uniquely identifying the client computer from the ID generation module 126.
[0067]
In step S1504, an in-client JOBID that uniquely identifies a job in the client computer is created. Here, it is assumed that numerical values from 0001 to 9999 are issued in order.
[0068]
In step S1505, the hook module 103 combines the client ID determined to have been acquired in step S1503 with the in-client JobID created in step S1504, and creates a new document name, which is an example of new identification information uniquely determined in the printing system. Create
[0069]
In step S1506, the hook module 103 stores the original document name passed from the application in the item “original document name” of the hook log. In step S1507, the document name is replaced with the new document name in step S1505. As a result, the new document name is passed to GDI as the document name. It is preferable that the processing in the printer driver 105, spooler 106, transmission / reception module 107, and printer 110, which is the latter stage of the GDI processing, be such that the document names are all processed with the new document names.
[0070]
Here, the reason why the new document name is created is that when merging job information acquired from the printing apparatus, it is difficult to directly use the JobID as a key for the merge process. For example, since a part of the specification of the job management method is not disclosed, when using the account server A developed by the company A, the account server developed by the company A acquires the JobID from the printer developed by the company B. Often cannot. In other words, even if the job information is acquired from a printer corresponding to an unexpected job management method, the job ID is not often included in the acquired job information, and cannot be used by merging the job information. However, a document name produced by an OS or an application in a client computer and transmitted to a printer can often be acquired as job information.
[0071]
Therefore, it is conceivable to manage, as the identification information, a document name that can be managed on the client side instead of the job ID and that can be obtained from the printer side as a key of the job information, instead of the Job ID. However, if the conventional document name is used as it is, a problem occurs. The client OS or application can generally manage more than eight characters, and a commonly used OS can assign a document name of up to 255 characters. The printer can manage up to eight characters as described above. In general, a document name that can be used in the job management method is up to eight characters. With this configuration, if a document name of eight characters or more is given on the client side, even if the document name given by the OS or application on the client side is different, jobs with the same document name coexist in the printer. And confusion arises. Therefore, the host ID is issued on the account server side and used in combination with the document name issued on the client side.
[0072]
As a result, a new document name uniquely managed in the printing system including the client computer and the printer, which is managed by the account server within eight characters, is completed. Then, this new document name can be used for job identification instead of the job ID. Once a new document name is generated on the client side, the printer, client, and account server can use this document name as a job identifier.
[0073]
<Operation of client side job log merge module>
FIG. 11 is a flowchart illustrating a process of merging logs by the job log merge module 116.
[0074]
The job log merge module 116 receives the logs such as the hook log 111, the driver log 112, the API log 113, and the monitor log 114, and records the contents on the HD 206 and the like. Then, the following processing is started periodically at a preset cycle, and the merging processing is performed for each job. In the present embodiment, log merging (merging processing) is performed using a job ID as a key. However, merging may be performed using a document data name or a new document data name described later as a key.
[0075]
In the following processing, the job log merge module 116 determines the earliest start time among the start times indicated by the entries of the start time information and the completion time information included in the hook log, the driver log, the API log, and the monitor log, respectively. Identify the latest completion time. As described above, each piece of time information is stored as job information that has been merged and merged.
[0076]
First, in step S1101, the job log merge module 116 searches and specifies whether there is a monitor log (see FIG. 10) for which the processed flag is not set to YES, that is, whether there is an unprocessed monitor log. If there is a monitor log for the process, the process proceeds to step S1102.
[0077]
In step S1102, the job log merge module 116 copies the monitor log specified as unprocessed in step S1101 to another temporary storage area, and sets this as the log A.
[0078]
In step S1103, the job ID is acquired from the log A. In step S1104, the job log merge module 116 determines whether there is a log that has not been merged yet, that is, an unprocessed log among logs corresponding to the JobID acquired in step S1103 based on the JobID. The determination is made by searching and specifying each of the hook log, the driver log, and the API log. If it is determined in step S1104 that there is no unprocessed log, the process ends. If the job log merge module 116 determines that there is an unprocessed log in step S1104, the job log merge module 116 proceeds to step S1105, where the JobID determined to be unprocessed in step S1104 (here, for convenience) N) to determine whether there is a log with a JobID equal to the log of the hook log 111, the driver log 112, and the API log 113 based on the JobID.
[0079]
If there is no log with a JobID equal to N in the hook log 111, the driver log 112, and the API log 113 in step S1105, the process advances to step S1108. If the job ID equal to N is found in any of the logs in step S1105, the process proceeds to step S1106. Here, for example, in step S1105, N may be set to N by identifying the JobIDs included in the unprocessed log A in ascending order.
[0080]
In step S1106, the job log merge module 116 determines, for each item of the log corresponding to the JobIDN of the log A (job information included in each log acquired for the JobIDN) specified in step S1105, among the items included in the log B. It is determined whether or not there is any item not in the log A. If it is determined in step S1106 that there is no item in the log B that does not exist in the log A, the job log merge module 116 performs the process in step S1108. If it is determined in step S1106 that there is an item in the log B that is not in the log A, the process proceeds to step S1107, and the job log merge module 116 determines an item in the log B that is not in the log A for the job IDN in the log A. To add the data stored in the log A. Here, the processing completion flag of the merge log 127 created by adding the item of the log B to the log A is set to “YES”, and the process proceeds to step S1108. Subsequently, the type item of the merge log is set to “merge”.
[0081]
In step S1104 subsequent to step S1108, if it is determined that the processing has been completed for all JobIDs related to log A, the processing ends.
[0082]
<Operation of the server-side job log merge module>
FIG. 16 is a flowchart illustrating a process of merging logs by the job log merge module 123 and creating a final log 128.
[0083]
In step S1601, the job log merge module 123 searches for an unprocessed merge log, and if so, proceeds to step S1602. If not, the process ends.
[0084]
In step S1602, the job log merge module 123 determines whether the printer has a device log, and if so, proceeds to step S1603. If not, the process proceeds to step S1607.
[0085]
In step S1603, the job log merge module 123 searches the unprocessed device log for a document name item having the same log as the merge log in step S1601 to determine whether there is a log. If it determines that there is, the process proceeds to step S1604. If it is determined that there is no log that is the same as the merge log in step S1601, the process ends. In step S1604, the job log merge module 123 replaces or adds the number of discharged pages and the number of discharged pages of the device log with the merge log.
[0086]
In step S1605, the job log merge module 123 replaces the document name with the original document name. In the example of FIG. 13, “document name: 2001 annual report, original document name: abcd0001”.
[0087]
In step S1606, the job log merge module 123 deletes the original document name of the merge log 127 to make it the final log 128. In step S1607, the job log merge module 123 passes the final log 128 to the job log storage module 124.
[0088]
<Log aggregation and analysis processing>
Next, a log totaling / analyzing process performed by the job log totaling module 125 will be described.
[0089]
FIGS. 18 and 19 are diagrams showing various processes and settings that can be performed on the recorded log information. The "process" menu includes a process of "totaling" the collected print logs and a process of displaying the result of "analysis". The “Settings” menu includes settings for performing “List / Edit” and other “Settings”.
[0090]
The “aggregate” menu in the “process” menu includes a process of displaying the aggregated result using “department / user”, “device”, “paper size”, and “management code” as keys. Here, the management code is a code for managing log information, and is used by a user to freely classify log information. In other words, the user separates the log information into, for example, work units, separately from the user identification information of the user and the department identification information of the department to which the user belongs (these user identification information and department identification information are referred to as user identification information). Has code to manage. Therefore, the user can freely specify to which management code the log information relating to the print processing performed by the user belongs.
[0091]
In the "Analysis" menu in the "Process" menu, the totalization results are analyzed and graphed by "Usage status", "Usage rate by use", "Department / user upper limit", "Management code upper limit", etc. Processing is included.
[0092]
The “list / edit” menu in the “setting” menu includes settings such as “department / user”, “device”, “management code”, and “job history”. The setting for grouping users into departments is made by “department / user”, and the setting for grouping users by management code is made by “management code”.
[0093]
The “Settings” menu in the “Settings” menu includes settings such as “Paper”, “Paper Unit Price”, and “Environment”.
[0094]
FIGS. 20A and 20B are diagrams showing a result of setting “department / user” and “management code” in the “list / edit” menu in the “setting” menu. As shown in FIG. 20A, “development section 1”, “development section 2”, and “development section 3” are defined as sections, and “Suzuki, Saito, Tanaka”, “Takahashi, Yamamoto” are members of each section. "And" Ouchi, Sawaki "are registered as users. Further, as shown in FIG. 20B, three management codes “1001,” “1002,” and “1003” are defined, and as members thereof, “Suzuki, Saito, Tanaka, Takahashi, Yamamoto”, “Ouchi” , Sawaki "and" Takahashi, Yamamoto, Tanaka "are registered. Here, for example, it is assumed that the management code indicates the number of the work unit. It is defined, for example, when work personnel are composed of personnel who cross departments. Here, the members of the management code “1001” are registered with the personnel of “development section 1” and “development section 2” in terms of department, and represent the code numbers of the work performed by the personnel of these two departments. ing. Similarly, the management codes “1002” and “1003” are also composed of personnel beyond the departmental frame. According to FIG. 20B, Mr. Tanaka can use two management codes “1001” and “1003”. In the management code input dialog of FIG. 26, available management codes are displayed, and the user selects and specifies the management code from a list box.
[0095]
FIG. 21 shows an analysis result of the printing process for each department / user. This is displayed by selecting the menu of “processing menu” / “analysis” / “department / user upper limit” in FIG. Here, the number of prints per week and the ratio of the number of prints to the upper limit are displayed for each department / user from 2002/09/29 to 2002/10/27.
[0096]
FIG. 22 is a graph showing the printing status of “Development Section 1 / Mr. Suzuki” in “Department / User” in FIG. 21 for each use date. By displaying the printing status of a specific user in a graph, it is possible to grasp the printing status of the specific user at each time.
[0097]
FIG. 23 shows an analysis result of the printing process for each management code. This is displayed by selecting the menu of “processing menu” / “analysis” / “management code upper limit value” in FIG. In order to perform aggregation and analysis using this management code, it is necessary to determine to which management code the print job is assigned. This is dealt with by displaying a management code input dialog at the time of printing and allowing the user to select and input a management code.
[0098]
The user inputs a management code by selecting and specifying an available management code at the time of printing.
[0099]
The user who has performed the printing does not bear the print job as an expense, but can enter the management code for each work unit, so that the print job can be assigned to the group that should actually own the print job.
[0100]
FIG. 24 is a diagram in which the printing status with respect to the upper limit value of the management code “1001” is analyzed and displayed as a graph. The printing status for each period of the group indicated by the management code “1001” can be specified. Together with the function of FIG. 23, it is possible to clarify the printing situation in units of “management code” expressing a unit of work.
[0101]
The user who performs the printing process is grouped into two attributes, a first (department) and a second (management code), and is different from the user who performed the printing process or the first attribute (department) to which the user belongs. By specifying the second attribute (management code) in the print job at the time of printing, and performing analysis / aggregation display using the second attribute (management code) as a key, the printing status that is more convenient for the printing process is specified. Can be performed. Further, by suppressing printing using the upper limit value based on the second attribute (management code), more flexible print management becomes possible.
[0102]
FIG. 25 is a flowchart of the print suppression processing using the management code. An upper limit is set for each management code, and a limit is imposed on the total number of printed sheets of the group belonging to the management code. This setting can be made in "Setting Menu": "List / Edit"-"Management Code" in FIG. The details of the print suppression processing using the management code will be described with reference to FIGS.
[0103]
When a print instruction is issued, in step S2501, a management code input dialog 2601 shown in FIG. 26 is displayed as a pop-up on a display device (not shown) of each of the client computers 1001 to 1003. Step S2502 is processing for designating a management code in the displayed management code input dialog. From the list of registered management codes, select the management code to be assigned to the print job. If the input (selection and designation of the management code) is not performed, a default management code is designated in step S2504. This default value can be specified in “setting menu”: “setting”-“environment” in FIG. 19 in the combination of the management code and the user registered in the table of FIG.
[0104]
In step S2505, the server computer 2000 checks whether the number of prints of the designated management code has reached the upper limit.
[0105]
If the upper limit has been reached, the server computer 2000 notifies the client computers 1001 to 1003 of the fact. In step S2507, a message is displayed to the user to notify that printing cannot be performed. If the upper limit has not been reached, the flow advances to step S2506 to execute print processing. Step S2508 is processing for updating the total number of printed sheets in the designated management code.
[0106]
In step S2509, the print log and the management code are transmitted to the server computer 2000. As described above, by setting the upper limit of the number of prints for each management code and enabling the printing process to be suppressed, it is possible to save the user's trouble of recounting the number of prints and to provide a more convenient printing suppression function. be able to.
[0107]
Here, in the comparison process between the upper limit of the management code and the number of prints, if the total number of prints of all users having the same management code reaches the upper limit of the management code, printing is suppressed. Alternatively, printing may be suppressed when the number of prints of each user having the same management code reaches the set upper limit of the management code.
[0108]
Further, in the present embodiment, the management code has been described as a code indicating the content of the job, but the meaning of the management code is not limited to this. For example, a code representing the purpose of image formation or the like may be used. That is, the management code can be defined as a code for generating a classification that cannot be separated based on information (a type of a user or an image processing apparatus) included in conventional job information.
[0109]
Further, the user may be able to define a new management code in the client computer. In this case, a table for associating the management code with the user may be newly created in the database shown in FIG.
[0110]
(Other embodiments)
The processing shown in the flowcharts shown in the respective drawings (FIGS. 11, 15, 16, and 25, etc.) in the present embodiment, and the respective modules shown in FIG. 1 are executed by the respective computers by a program installed from the outside. You. In this case, the present invention is applicable even when a group of information including a program is supplied to the client computer from a storage medium such as a CD-ROM, a flash memory, or an FD, or from an external storage medium via a network. Things.
[0111]
As described above, the storage medium storing the program codes of the software for realizing the functions of the above-described embodiments is supplied to the system or the apparatus, or is downloaded from an external server (not shown), so that the system or the apparatus is obtained. It is needless to say that the object of the present invention can also be achieved when the computer (or CPU or MPU) reads and executes the program code stored in the storage medium.
[0112]
In this case, the program code itself such as a job account server or a job account client program read from the storage medium realizes the novel function of the present invention, and the storage medium storing the program code constitutes the present invention. Will do. As a storage medium for supplying the program code, for example, a floppy disk, hard disk, optical disk, magneto-optical disk, DVD, CD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, or the like can be used.
[0113]
When the computer executes the readout program code, not only the functions of the above-described embodiments are realized, but also an OS (Operating System) running on the computer based on the instruction of the program code. It goes without saying that a part or all of the actual processing is performed and the functions of the above-described embodiments are realized by the processing. Further, a program code transmitted from a predetermined external server device (not shown) via a network or read from a storage medium is used for a function expansion board inserted into a computer or a function expansion board connected to a computer. After being written into the memory provided in the unit, the CPU or the like provided in the function expansion board or the function expansion unit performs part or all of the actual processing based on the instruction of the program code, and the processing performs the processing of the above-described embodiment. It goes without saying that the case where the function is realized is included.
[0114]
Hereinafter, embodiments of the present invention will be described.
[0115]
[Embodiment 1]
An information processing client that generates a job for the image processing apparatus and generates job information related to the job;
An information processing server that acquires and records the job information from the information processing client;
An information processing system including
The information processing client,
Display control means for displaying a screen for designating a management code usable by the user in response to a print instruction from the user;
Transmission means for transmitting the management code and the job information input on the screen displayed by the display control means to the information processing server,
Has,
The information processing server,
Acquiring means for acquiring the management code and the job information from the information processing client;
Tabulation means for tabulating the job information based on the management code acquired by the acquisition means,
An information processing system comprising:
[0116]
[Embodiment 2]
The information processing system according to claim 1, wherein the information processing server has means for storing user identification information for identifying the user and the management code in association with each other.
[0117]
[Embodiment 3]
The information processing server,
An upper limit storage unit storing an upper limit of use of the image processing apparatus in association with the management code;
Determining means for determining whether or not the value exceeds the upper limit when the job is executed, based on a result of the counting by the counting means;
Notification means for notifying the information processing client of the determination result of the determination means,
The information processing system according to the first embodiment, comprising:
[0118]
[Embodiment 4]
The aggregation means can aggregate the job information based on the user identification information and the management code,
The information processing server,
Upper limit value storage means storing an upper limit value of use of the image processing apparatus in association with the management code and user identification information,
Determining means for determining whether or not the value exceeds the upper limit when the user executes the job, based on a result of the counting by the counting means;
The information processing system according to the second embodiment, comprising:
[0119]
[Embodiment 5]
The information processing system according to the second embodiment, wherein the counting means can select and count any one of the user identification information and the management code.
[0120]
[Embodiment 6]
An information processing client that generates a job for the image processing apparatus and generates job information related to the job;
An information processing server that acquires and records the job information from the information processing client;
An information processing system including
The information processing client,
Display control means for displaying a screen for designating a management code usable by the user in response to a print instruction from the user;
A transmission unit configured to transmit a management code input on a displayed screen and the job information including user identification information to the information processing server;
Has,
The information processing server,
An acquisition unit configured to acquire the management code and the job information including the user identification information from the information processing client;
Counting means for counting the job information in the management code unit or the user identification information unit in accordance with the specification;
An information processing system comprising:
[0121]
[Embodiment 7]
An information processing apparatus that generates a job for the image processing apparatus and generates job information related to the job,
Display control means for displaying a screen for designating a management code usable by the user in response to a print instruction from the user;
Transmission means for transmitting the management code and the job information input on the screen displayed by the display control means,
An information processing apparatus comprising:
[0122]
[Embodiment 8]
An information processing apparatus that manages job information on a job for an image processing apparatus,
Acquisition means for acquiring a management code and the job information usable by a user,
Tabulation means for tabulating the job information based on the management code,
An information processing apparatus comprising:
[0123]
[Embodiment 9]
An information processing method for managing job information related to a job issued from an information processing apparatus to an image processing apparatus,
In the information processing apparatus, a step of displaying a screen for specifying a management code that can be used by a user for the job;
An acquisition step of acquiring the management code and the job information from the information processing apparatus;
A counting step of counting the job information based on the management code acquired in the acquiring step,
An information processing method comprising:
[0124]
[Embodiment 10]
A program for managing job information related to a job issued from an information processing apparatus to an image processing apparatus,
On the computer,
An acquisition step of acquiring a management code and the job information usable by a user for the job;
A counting step of counting the job information acquired based on the management code;
A program characterized by executing
[0125]
[Embodiment 11]
A computer-readable storage medium storing the program according to claim 10.
[0126]
【The invention's effect】
According to the present invention, by increasing the degree of freedom in analyzing and displaying the printing status, it is possible to reduce the load of the usage status tallying process and to easily and effectively grasp the printing status.
[Brief description of the drawings]
FIG. 1A is a diagram illustrating a configuration of a job account system according to an example of an embodiment of the present invention.
FIG. 1B is a diagram showing a configuration of a job account system showing an example of an embodiment of the present invention.
FIG. 2 is a block diagram showing an example of a configuration of a client computer and a server computer constituting the job account system shown in FIG.
FIG. 3 is a block diagram illustrating an example of a configuration of a printer included in the job account system illustrated in FIG.
FIG. 4 is a diagram illustrating an example of a memory map of the job account system illustrated in FIG.
FIG. 5 is a diagram illustrating a configuration of an FD storing a job account program and related data according to an embodiment of the present invention;
FIG. 6 is an example of an embodiment of the present invention, showing an example of loading a job account program and related data recorded on an FD into a computer system.
FIG. 7 is a diagram illustrating an example of a hook log according to the embodiment of the present invention.
FIG. 8 is a diagram illustrating an example of a driver log according to the embodiment of the present invention.
FIG. 9 is a diagram illustrating an example of an API log according to the embodiment of this invention.
FIG. 10 is a diagram showing an example of a monitor log according to the embodiment of the present invention.
FIG. 11 is a flowchart illustrating an example of a procedure for merging logs according to the embodiment of this invention.
FIG. 12 is a diagram illustrating an example of a merge log according to the embodiment of this invention.
FIG. 13 is a diagram illustrating an example of a device log according to the embodiment of the present invention.
FIG. 14 is a diagram illustrating an example of a device log according to the embodiment of this invention.
FIG. 15 is a flowchart illustrating an example of a procedure for changing a document name according to the embodiment of this invention.
FIG. 16 is a flowchart illustrating an example of a procedure for merging logs and creating a final log according to the embodiment of this invention.
FIG. 17 is a diagram illustrating an example of a final log according to the embodiment of this invention.
FIG. 18 is a diagram illustrating an example of a processing menu according to the embodiment of the present invention.
FIG. 19 is a diagram illustrating an example of a setting menu according to the embodiment of the present invention.
FIG. 20 is a diagram illustrating an example of user registration by a department and user registration by a management code in the embodiment of the present invention.
FIG. 21 is a diagram showing an analysis result of an upper limit value and a printing status using a department / user as a key according to the embodiment of the present invention.
FIG. 22 is a diagram showing an analysis and graph display of a printing status of a specific department / user according to the embodiment of the present invention.
FIG. 23 is a diagram showing an upper limit value using a management code as a key and an analysis result of a printing situation in the embodiment of the present invention.
FIG. 24 is a diagram showing an analysis and graph display of a printing status of a certain management code in the embodiment of the present invention.
FIG. 25 is a flowchart of a print suppression process using a management code according to the embodiment of the present invention.
FIG. 26 is a diagram showing a dialog for inputting a management code at the time of printing according to the embodiment of the present invention.
[Explanation of symbols]
111 Hook log 112 Driver log 113 API log 114 Monitor log 115 Device log 116 Job log merge module 117 Job log transmission module 118 Job account client 121 Job account server 122 Job log reception module 123 Job log merge module 124 Job log recording module 125 Job log Aggregation module 126 ID generation module

Claims (1)

An information processing client that generates a job for the image processing apparatus and generates job information related to the job;
An information processing server that acquires and records the job information from the information processing client;
An information processing system including
The information processing client,
Display control means for displaying a screen for designating a management code usable by the user in response to a print instruction from the user;
Transmission means for transmitting the management code and the job information input on the screen displayed by the display control means, to the information processing server,
Has,
The information processing server,
Acquiring means for acquiring the management code and the job information from the information processing client;
Tabulation means for tabulating the job information based on the management code acquired by the acquisition means,
An information processing system comprising:

Images