JP4830429B2 - Image forming apparatus, apparatus and method for managing the number of image formations in image forming apparatus, and computer program - Google Patents

Description

  The present invention relates to an image forming apparatus that manages the number of image formations using a billing counter, a management apparatus and management method for the number of image formations in the image forming apparatus, and a computer program. The present invention relates to an image forming apparatus for subtracting the number of times of image formation from a normal number of image formations counted by a billing counter, a management apparatus and management method for the number of image formations in the image forming apparatus, and a computer program.

  More specifically, the present invention relates to an image forming apparatus that performs an appropriate deduction process in response to a job that occurs in the foreground or background during maintenance work, a management apparatus and management method for the number of image formations in the image forming apparatus, and a computer An image forming apparatus that performs appropriate deduction processing while executing interrupt printing by a foreground job generated during maintenance work, a management apparatus and management method for the number of image formations in the image forming apparatus, and a computer・ Regarding the program.

  In modern society where documentation is important, image forming apparatuses capable of reproducing images with high resolution and high quality have been deeply penetrated into the living environment for a long time. This type of image forming apparatus originally copied a black-and-white image of a scanned document onto printing paper. However, as copy forms such as color copying, enlargement, and reduction diversify, Resolution and quality have been improved. In addition to the copying function, complex copying machines equipped with a plurality of functions such as a printer, a facsimile machine, and a content service have become widespread.

  Many of this type of image forming apparatus are procured under a lease contract, and a vendor uses a billing counter to count the number of image formations and charges a customer for a usage fee.

  In addition, even when the automatic density adjustment function is activated, the image forming device changes its image quality due to the environment (temperature, humidity, etc.), supply status (photoreceptor fatigue), and changes over time. To do. The electrophotographic process corresponding to the engine portion of the image forming apparatus has a complicated structure, and it is difficult for the customer to adjust it arbitrarily. For this reason, in most cases, a maintenance contract is made between the customer and the vendor in which a customer engineer regularly visits the installation site of the image forming apparatus to perform maintenance.

  During maintenance work of the image forming device, test copy and test print (hereinafter referred to as “test copy”) are performed to check the normal operation of the device and image quality, and various reports are printed. To do. For example, an image forming apparatus that prints out a report when a maintenance operation is performed has been proposed (for example, see Patent Document 1).

  Here, if the number of copies made for maintenance purposes is added to the billing counter, the amount charged for the maintenance contract becomes an unfavorable amount for the customer, so deduction processing is necessary. This deduction process basically writes down the billing counter when the customer engineer visits, and subtracts the counter value at the time of the visit from the billing counter value at the end of the maintenance. Deducted as the number of sheets.

  In general, when a customer engineer performs a maintenance work, the customer engineer reports the contents of the maintenance work to the company (see Fig. 32), or records the maintenance work for the customer "maintenance complete" “Report” (see FIG. 33) is entered, but in the vicinity of the middle part of each form, an “end meter” that writes the value of the billing counter at the end of the maintenance, and the counter value at the time of visit “ The “visit meter” column is provided, and the value obtained by subtracting the visit meter from the end meter is written in the “maintenance work” column as a deduction target.

  It is troublesome for the customer engineer to perform such deduction processing manually, and mistakes are likely to occur. Also, when various reports such as service reports and maintenance completion reports are issued on the image forming apparatus that has undergone maintenance, the value of the end meter must be entered in consideration of the number of reports when creating the report. It is easy to make a calculation mistake.

  It is necessary to save the trouble of the customer engineer and perform the deduction processing accurately. For this reason, an image forming apparatus that stops the counter at the time of trial copying (see, for example, Patent Document 2) or the number of image formations performed by the user by subtracting the number of maintenance image formations performed by a serviceman from the total number of image formations is calculated. A proposal has been made regarding a management system for image forming apparatuses (see, for example, Patent Document 3).

  Also, during maintenance, an ordinary counter is stopped and an image forming apparatus having a separate test / copy counter (see, for example, Patent Document 4) or printing when it is determined that there is a problem with print image quality. There has been proposed a system (for example, see Patent Document 5) that switches the counter of the number of sheets to one for maintenance.

  However, in the case of a complex copying machine equipped with a plurality of functions such as a printer and a facsimile, even during maintenance work, such as facsimile reception and network printing via an external connection line such as a LAN or a public line. There is a possibility that a background job is started or operated inside the multifunction peripheral or the like. In addition, during the maintenance work, there may be a foreground job that the user directly instructs and requests on the operation panel of the multifunction peripheral such as an emergency copy of the customer. Corresponding to these interrupt prints during maintenance work, the number of image formations not subject to subtraction is counted in the maintenance counter, and accurate subtraction cannot be performed. When a customer engineer tries to perform a deduction process by hand calculation, the calculation becomes more complicated and it is easy to make a calculation mistake. In addition, if the facsimile reception is performed a plurality of times during the maintenance work, the possibility of making a calculation error increases accordingly. Of course, these interrupt prints interfere with maintenance work for customer engineers.

  For example, a foreground job requested by a network print or user pointing to an operation panel such as a multifunction device will cause the customer to refrain from starting during maintenance work, and the customer will restart the job after maintenance is complete. That's fine. Further, by removing the jack during the maintenance work or disconnecting the LAN to suppress the start of jobs such as interrupt printing, the customer engineer can concentrate on the maintenance work and easily perform the deduction processing accurately. However, it is difficult for a customer to suppress a copy or a PC print that the customer wants to make urgently for the convenience of the vendor side of maintenance. Also, jobs such as facsimile reception prints are highly important and urgent, and it is not preferable to give the customer the unexpected disadvantage of being unable to receive them for the convenience of the vendor. If the transmission source facsimile cannot perform reception processing while redialing is activated, data will be lost and recovery will not be possible. Therefore, even during maintenance work, facsimile reception and other highly important and urgent background jobs should be activated.

  As part of the maintenance work, there are situations in which the customer is requested to make a PC print or the customer makes an emergency copy during the maintenance work. In such a case, if a large amount of printing is performed, more than necessary deductions are made. The number of times of image formation by these interrupt prints should be excluded from the deduction target and the normal billing count should be performed. If deductions are not done correctly, it will be detrimental to customers and vendors.

  For example, an image forming apparatus that sets a grace value for a counter has been proposed (see, for example, Patent Document 6). In this case, execution of the image forming operation for the test purpose is allowed until the counter value becomes 0, and the customer can be freed from the disadvantage due to the increase in the unfairness of the counter value. The deduction process is not exactly performed according to the situation.

JP 2003-244375 A JP-A-6-95463 JP-A-8-152826 JP 2000-352912 A Japanese Patent Laid-Open No. 2003-94783 JP 2003-15487 A

  An object of the present invention is to provide an excellent image forming apparatus capable of appropriately subtracting the number of image formations during maintenance from the normal number of image formations counted by a billing counter, and management of the number of image formations in the image forming apparatus. An apparatus, a management method, and a computer program are provided.

  A further object of the present invention is to provide an excellent image forming apparatus capable of performing appropriate deduction processing while corresponding to a job generated in the foreground or background during maintenance work, an image forming frequency management apparatus in the image forming apparatus, and A management method and a computer program are provided.

  A further object of the present invention is to provide an excellent image forming apparatus and an image forming frequency management apparatus in an image forming apparatus capable of performing appropriate deduction processing while executing interrupt printing by a foreground job generated during maintenance work. And a management method and a computer program.

  The first aspect of the present invention is an image forming apparatus that outputs image information and manages the number of image formations, and forms image information on a medium. The image forming means to perform, the counter for counting the number of times of image formation performed by the image forming means, the maintenance counter for counting the number of times of image formation performed by the image forming means during maintenance work, and the image forming means A job history storage unit that stores the history of the job performed, a job history display unit that displays the history of the job stored in the job history storage unit, and a subtraction or deduction for the job history displayed on the job history display unit The job deduction / non-deduction designation means for designating non-deduction, and the maintainer based on the designated content via the job deduction / non-deduction designation means. An image forming apparatus characterized by comprising a maintenance counter updating means for updating the counter value of the scan counter.

  In an image forming apparatus with a lease contract, a vendor uses a billing counter to count the number of image formations and charge a customer for a usage fee. In many cases, a maintenance contract is signed with a vendor in which a customer engineer regularly visits the installation site of the image forming apparatus to perform maintenance.

  Further, if the test print performed at the time of maintenance work is also counted by the billing counter, the amount charged for the maintenance contract will be unfavorable for the customer, so it is necessary to properly deduct it. For example, a normal counter may be stopped at the time of maintenance, and a separate maintenance counter for counting test copies may be provided. However, even during maintenance work, a job is requested in the foreground or background, and the value of the maintenance counter may become inaccurate due to interrupt printing or the like.

  For example, there is a situation where the customer wants to make an emergency copy during the maintenance work, but there is a problem in having the customer refrain from copying for the convenience of the vendor side of the maintenance work. Alternatively, by removing the jack during maintenance work so that jobs do not occur in the background, the customer engineer can concentrate on the maintenance work and perform deduction processing accurately. However, if a job with high importance or urgency is restrained by the convenience of the vendor, the disadvantage to the customer becomes excessive.

  In addition, as part of maintenance work, customers may be asked to make a PC print. In such a case, if a large amount of printing is performed, it will be deducted more than necessary, so it should be excluded from the deduction object and normal billing count should be performed.

  Therefore, in the image forming apparatus according to the first aspect of the present invention, the history of the executed job is stored, the job history is displayed after the maintenance work is completed, and each job is deducted or non-deducted on the display screen. Directly specify what should be done. Therefore, it is possible to designate interrupt prints made by foreground job requests such as urgent copies and PC prints that occur due to customer's convenience during maintenance work as non-deductible targets, and the number of image formations is a maintenance counter. By subtracting from, appropriate deduction processing can be performed.

  In addition, there are cases where the image forming apparatus connects multiple lines as a facsimile function, and if the line is pulled out to restrict jobs during maintenance work, it takes a lot of time to connect the line as it was at the end of the maintenance work. It ’s hard. According to the present invention, since it is not necessary to disconnect the line, such a situation can be avoided.

  Here, the maintenance counter updating means may limit the number of times of image formation related to the job to be subtracted to be subtracted. In order to confirm the operation at the end of maintenance, the customer may be asked to execute a test print. Customers may print a large amount of presentation materials along with test prints, but only the first page is meaningful for operation confirmation, so the deduction target is a specific number of pages in the total number of test prints. By limiting, fair and proper deduction processing can be performed.

  According to a second aspect of the present invention, there is provided a management device that manages the number of times of image formation in an image forming apparatus, the connection means connected to the image forming apparatus, the number of times of image formation executed by the image forming apparatus, and Job history acquisition means for acquiring the job history, job history display control means for controlling display of the acquired job history, and designation of deduction or non-deduction for the job history displayed and controlled by the job history display control means. A management apparatus comprising: a job deduction / non-deduction designation unit to be received; and a deduction processing unit that calculates the number of image formations to be deducted based on a designation content via the job deduction / non-deduction designation unit. .

  It may be difficult to update the firmware of the image forming apparatus main body such as a conventional machine. The management apparatus according to the second aspect of the present invention operates as, for example, a maintenance terminal externally connected to the image forming apparatus, calls a history of jobs under maintenance work, and designates deduction or non-deduction for each job. By doing so, it is possible to accurately grasp the number of image formations to be subtracted during the maintenance work. Therefore, it is possible to designate interrupt prints made by foreground job requests such as urgent copies and PC prints that occur due to customer's convenience during maintenance work as non-deductible targets, and the number of image formations is a maintenance counter. By subtracting from, appropriate deduction processing can be performed.

  The deduction processing unit may limit the number of image formations to be deducted for a job designated as a deduction target via the job deduction / non-deduction designation unit. As a confirmation of operation at the end of maintenance, the customer may be asked to execute a test print, but only the first page is meaningful for operation confirmation. By limiting to the number, fair and appropriate deduction processing can be performed.

  The management apparatus according to the second aspect of the present invention may further include report print instruction means for instructing printing of a work result report made on the image forming apparatus. In such a case, the deduction processing unit calculates the number of image formations to be deducted in consideration of the number of image formations executed by the image forming apparatus in response to an instruction from the report print instruction unit. It is possible to accurately subtract the meter including the number of times of image formation of the report of the maintenance result.

  According to a third aspect of the present invention, there is provided a computer program written in a computer readable format so as to execute management of the number of image formations in an image forming apparatus that outputs image information on a computer system. Counting procedure for counting the number of image formations performed by the image forming apparatus for the computer system, a maintenance counting procedure for counting the number of image formations performed by the image forming apparatus during maintenance work, and the image forming apparatus The job history storage procedure for storing the history of jobs executed by the job history, the job history display procedure for displaying the job history stored by the job history storage procedure, and the job history displayed in the job history display procedure are deducted. Or a job deduction / non-deduction designation procedure for designating non-deduction, and Is a computer program characterized by executing the steps counter update maintenance updates the count value of the counter for maintenance on the basis of the specified content in Bed net and non-net specified procedure.

  The computer program according to the third aspect of the present invention defines a computer program described in a computer-readable format so as to realize predetermined processing on a computer system. In other words, by installing the computer program according to the third aspect of the present invention in the computer system, a cooperative action is exhibited on the computer system, and the image formation according to the first aspect of the present invention is performed. The same effect as the apparatus can be obtained.

  According to a fourth aspect of the present invention, there is provided a computer program written in a computer-readable format so that management of the number of image formations in an image forming apparatus that outputs image information is executed on a computer system. Job history acquisition procedure for controlling the display of the acquired job history and the job history acquisition procedure for acquiring the number of image formations and job history executed by the image forming apparatus via a predetermined communication line to a computer system Based on the control procedure, the job deduction / non-deduction designation procedure that receives designation of deduction or non-deduction for the job history displayed and controlled by the job history display control procedure, and the specified contents through the job deduction / non-deduction designation procedure And a deduction processing procedure for calculating the number of image formations to be deducted. A gram.

  The computer program according to the fourth aspect of the present invention defines a computer program described in a computer-readable format so as to realize predetermined processing on a computer system. In other words, by installing the computer program according to the fourth aspect of the present invention in the computer system, a cooperative action is exhibited on the computer system, and the management apparatus according to the second aspect of the present invention The same effect can be obtained.

  According to the present invention, an excellent image forming apparatus capable of appropriately subtracting the number of image formations during maintenance from the normal number of image formations counted by a billing counter, and management of the number of image formations in the image forming apparatus An apparatus, a management method, and a computer program can be provided.

  Further, according to the present invention, an excellent image forming apparatus and an image forming frequency management apparatus in an image forming apparatus capable of performing appropriate deduction processing while corresponding to a job generated in the foreground or background during maintenance work. And a management method and a computer program can be provided.

  In addition, according to the present invention, an excellent image forming apparatus capable of performing appropriate deduction processing while executing interrupt print by a foreground job generated during maintenance work, and management of the number of image formations in the image forming apparatus An apparatus, a management method, and a computer program can be provided.

  According to the image forming apparatus of the present invention, a job that should not be deducted, such as an emergency copy or a PC print, generated due to customer's convenience during maintenance work is specified on the screen, and the number of times of image formation is determined. By subtracting from the maintenance counter, appropriate deduction processing can be performed.

  Even if it is difficult to update the firmware of the image forming apparatus main body such as a conventional machine, the history of the job under maintenance work is called on the maintenance terminal, and deduction or non-deduction is designated for each job. This makes it possible to accurately grasp the number of image formations to be subtracted during the maintenance work.

  In addition, as an operation check at the end of maintenance, the customer may be asked to execute a test print. Customers may print a large amount of presentation materials along with test prints, but only the first page is meaningful for operation confirmation, so the deduction target is a specific number of pages in the total number of test prints. By limiting, fair and proper deduction processing can be performed.

  Further, according to the present invention, it is possible to perform accurate subtraction processing including the number of times of image formation of the report print of the maintenance result.

  Other objects, features, and advantages of the present invention will become apparent from more detailed description based on embodiments of the present invention described later and the accompanying drawings.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 schematically shows the overall configuration of an FWS (Field Work Support) system that centrally manages maintenance information of multifunction peripherals by customer engineers.

  The image forming apparatus is a multi-function machine equipped with a plurality of functions such as a printer, a facsimile, and a content service in addition to a copying function. In the embodiment described below, the image forming apparatus for which a lease contract and a maintenance contract are made with a vendor is particularly targeted, and a customer engineer visits the image forming apparatus regularly to perform maintenance. Is done. The multifunction peripheral is connected to a wide area network such as the Internet or a public telephone network. In the figure, only one image forming apparatus is drawn for simplification of the drawing, but in reality there are innumerable image forming apparatuses.

  The image forming apparatus can execute jobs such as copy, print, network print, scan, facsimile, mail, media print, and content print in response to a job request from a user. In addition to requesting individual jobs independently, multi-jobs combining two or more jobs such as scan + print and content download + print may be required. When the image forming apparatus executes a job, a service is provided to the user, and the user is charged for the service (in this sense, “job execution” and “service in the image forming apparatus”). "Providing" is almost synonymous).

  Multifunction devices are installed in user offices, convenience stores, and the like according to lease contracts with vendors. A user can directly input a job such as copying, facsimile transmission or reception, network printing, or content downloading from an operation panel provided in the multifunction peripheral. Alternatively, a job requested from a personal computer or the like via a network can be transferred to the multifunction device.

  A billing counter is attached to the multifunction peripheral, and the number of times of image formation is counted each time a job such as copying or printing is executed, and a usage fee charged to the user is calculated based on the count value. In addition to simply counting the number of ejected sheets, the counting method can adopt a counting method according to the difference in image forming mode such as sheet size and monochrome / color.

  The image forming engine of the multifunction machine is configured by an electrophotographic process, for example. Even if an automatic density adjustment function is installed on the multifunction device, the image quality changes due to the influence of the environment (temperature, humidity, etc.) in which it is installed and the change in the supply status (photoconductor fatigue), etc. Therefore, a maintenance contract is made between the vendor and the user so that the customer engineer regularly visits the installation site of the image forming apparatus and performs maintenance.

  This multi-function device is connected to a FWS server installed by a vendor via a wide area network such as the Internet. When a customer engineer visits and performs maintenance work on the multifunction peripheral, various maintenance information is notified (that is, reported) from the multifunction peripheral (or a maintenance terminal connected to the multifunction peripheral) to the FWS server. As a result, the vendor can grasp the status of the MFP, and provide users with appropriate maintenance, automatic ordering of consumables, meter counts, and automatic billing. be able to.

  FIG. 2 schematically illustrates the hardware configuration of the multifunction peripheral 100. Hereinafter, each part in the apparatus 100 will be described.

  A CPU (Central Processing Unit) 101 is a central controller that comprehensively controls the operation in the apparatus 100, and controls programs under an execution environment provided by the operating system, such as copying, facsimile transmission / reception, and network printing. Main control is performed with respect to various image forming operations and charge processing for the price associated with the image forming processing. In this embodiment, a billing counter process that counts the number of times an image is formed during execution of a normal image forming process, a maintenance process that starts and ends a maintenance operation, a test print that is performed during maintenance work, and various report prints A program such as a maintenance counter process that counts the number of image formations to be subtracted and a maintenance counter update process that takes into account interrupt prints caused by background jobs and foreground jobs that occur during maintenance work is executed. An appropriate deduction process for the billing counter can be performed by the maintenance counter process and its update process. Details of this point will be described later. The CPU 101 is interconnected with each device in the apparatus 100 via the bus 102.

  A ROM (Read Only Memory) 103 is composed of a read-only semiconductor memory device, and each control program and fixed data for performing service providing operations such as network printing and billing processing associated with service execution are permanent. Has been written. For example, firmware that executes the above-described billing counter processing, maintenance processing, maintenance counter processing and update processing thereof, deduction processing for the billing counter, and the like is stored in the ROM 103. Of course, the ROM 103 can also be configured using a device capable of electrically rewriting stored data, such as a flash memory, and the program and fixed data may be updated as necessary. The fixed data is unique information that does not need to be rewritten, such as a serial number, a manufacturing number, a manufacturing date, and a manufacturing factory name that physically identifies the multifunction peripheral 100.

  A RAM (Random Access Memory) 104 is composed of a rewritable semiconductor memory device, and loads a control program executed by the CPU 101 from the ROM 102, temporarily stores environment variables and system variables during program execution, and the like. Used as system memory for operation. The RAM 104 can be used as a page memory for image processing.

  An NVRAM (Non-Volatile RAM) 105 is composed of a rewritable memory such as a flash memory that does not lose its stored contents even in a non-powered state, and includes security data, other nonvolatile data, image quality adjustment, and various counters (described later). It is used to store various setting parameters, various histories at the time of service execution, histories charged for service charges, and the like.

  The HDD 106 is a large-capacity external storage device composed of a magnetic recording type fixed disk. The HDD 106 accumulates image data read from an original, stores various job histories when the image forming process is executed, and is executed by the CPU 101. Used to install programs to do.

  The image processing unit 107 performs various kinds of image processing such as expansion / compression processing and image quality adjustment on image data read from a document or image data downloaded via a network. For example, the image processing unit 107 can be configured by using ASIC (Application Specific Integrated Circuit).

  The multi-function device 100 shown in FIG. 1 includes a display unit 110 including a liquid crystal display as a user interface 109 and a hardware key such as a start / stop / ten key (or a touch panel that also functions as the display unit 110). A unit 111 is provided, and these are connected to the bus 102 via the UI interface 108. However, the CPU 101 may be configured to directly control the display unit 110 and / or the operation unit 111 of the user interface 109 without using the UI interface 108.

  The user can directly input job instructions such as copying, facsimile transmission / reception, and content download via the user interface 109.

  In addition, the customer engineer can start maintenance work and maintenance counter processing, update maintenance counter processing, test print during maintenance work, print various report reports, and send to the FWS server via the user interface 109. It is possible to input instructions such as network transmission and interrupt printing during maintenance work. In the maintenance counter update process, the job history stored in the HDD 106 or the like is displayed on the display unit 110, and the customer engineer specifies deduction or non-deduction for each job on the display screen.

  Various external devices, network interfaces, and the like are connected to the bus 102 via the communication interface 112.

  The LAN interface 113 provides a LAN port, such as 10 / 1000Base-T, through which the MFP 100 is network-connected in accordance with a predetermined protocol by IEEE (Institut of Electrical and Electronics Engineers). A wireless LAN can also be included. The multi-function device 100 can connect to an external network such as the Internet through a LAN and access a desired information resource. In addition, the multifunction device 100 can perform various services such as copying, facsimile transmission / reception, content search and other content processing, and network printing from a personal computer (PC) or a portable terminal (none of which is shown) used by the user. It is possible to receive a job instruction defining the contents and execute the service according to the instruction. In the present embodiment, the LAN interface 113 is used to connect to an FWS server on the Internet. Various maintenance information can be notified to the FWS server when the customer engineer performs maintenance work on the multifunction peripheral.

  The multi-function device 100 is equipped with an IC card read / write device to perform non-contact and short-range communication with the IC card, and is connected to the bus 102 via the RS232C or other serial interface 114. Between the IC card and the IC card read / write device, non-contact and short-distance communication is carried out while maintaining high tamper resistance through a predetermined mutual authentication process on a transmission path using electromagnetic coupling, electromagnetic induction, or radio wave communication. be able to. The multi-function device 100 charges the service fee from the IC card or charges the IC card.

  A USB (Universal Serial Bus) interface 115 conforms to, for example, USB 1.1 or USB 2.0, and can be used when a peripheral device is externally connected or locally connected to a personal computer or the like. For example, a customer engineer can connect a maintenance terminal (not shown) to the multifunction machine 10 via the USB interface 115. The above-described maintenance counter update processing and deduction processing can be realized by rewriting the firmware in the ROM 103. However, if it is difficult to update the firmware because of the conventional machine, a maintenance job is performed on the maintenance terminal. The history can be called and deduction or non-deduction can be designated for each job.

  The modem 116 is a modem that performs mutual conversion between signals on the computer and signals on the public line. The modem 116 connects to a public line such as a facsimile, and performs normal facsimile transmission / reception, time designation transmission, and other various facsimiles. Provide functionality.

  The coin kit 117 has a receiving port for receiving cash such as coins and banknotes, a cash storage unit for storing the cash inserted through the receiving port, a counter for the amount charged and collected after counting the amount of the input and the remaining amount And a display unit for displaying the remaining amount or the amount currently collected.

  The device interface 118 is composed of, for example, RS422, and implements an interface protocol for connecting various devices constituting the multi-function peripheral 100 to the bus 102.

  Examples of the devices constituting the multifunction peripheral include a reading device unit 119 that reads an image from a document, and a printing device unit 120 that prints and outputs an image on a sheet.

  The reading device unit 119 is generally configured by a combination of a platen on which a document is placed and a scan for reading an image, and may be an automatic document reading device. The read image is appropriately subjected to image processing in the image processing unit 107 and output to the printing apparatus unit 120 or stored in the HDD 106.

  The printing apparatus unit 120 includes, for example, an electrophotographic print engine unit. The electrophotographic process includes a plurality of sub-processes such as charging of an electrophotographic photosensitive member, exposure of a scanned original image, development, that is, toner superimposition on the photosensitive member, toner transfer and fixing on a sheet, and cleaning of the photosensitive member. However, the configuration of the print engine itself is not directly related to the gist of the present invention and will not be described further here.

  When the sheet printed by the printing apparatus unit 120 is discharged, it is stored in the discharged sheet storage unit 121. The discharge sheet storage unit 121 can also be configured using a general discharge tray.

  FIG. 3 schematically shows a software configuration for controlling operations on the multifunction machine. As shown in the figure, the control software includes an operating system (OS) layer, a middleware layer, a functional module layer, and an application layer.

  The OS is a built-in real-time OS, and a general-purpose one manufactured for a multi-function peripheral can be used.

  The middleware is a layer that mediates between the OS and the function module, and is positioned above the general-purpose OS, suppresses the influence specific to hardware, and has a common API (Application Programming Interface) for the upper module such as a job or a function module. This is a group of modules to be provided. By interposing such a software hierarchy, it is possible to suppress the influence of a change in the implementation to the functional module or the job level hierarchy when the hardware or OS in the multifunction peripheral 100 is changed.

  The system manager is a module that manages the core of the multifunction peripheral 100 such as status / resource management, job management, file management, buffer management, timer management, job log management, and various log management. Also provided to functional modules.

  The device driver and library are a group of modules that provide the functions of the external system and hardware to the function modules, and control various protocols and various devices at a lower level.

  In the present embodiment, the MFP 100 manages a normal use state, a special state for maintenance, a special state for performing a diagnostic function, and the like based on the concept of mode. The mode library provides this management function to each function module.

  A mailer provides a general electronic mail protocol function, and performs, for example, transmission / reception of IFAX and communication with an FWS server.

  The DV library provides the number of printed DV sheets, that is, a counter control function. An accessory driver is a driver for an authentication device such as a card reader or a management device.

  The device driver and library further include modules (not shown) that perform interface control with facsimile communication modem control, LAN control, HDD access control, reading device 119, printing device 120, user interface 109, and the like. is there.

  The functional modules are configured by a module group that notifies request processing, communication processing with the user interface 109, image processing for realizing an application, and various states to a remote device. Hereinafter, individual modules of the functional module group will be described.

  A request manager performs a request process and a communication process between the user interface 109 and the request manager. The output device controller (Output Device Cont) controls the printing device. The input device controller (Input Device Cont) controls the reading device. A spool controller (SpoolCont) controls accumulation. The Decomposer prints print data and performs conversion processing to an intermediate representation. A report generator (Report Gen) performs various report creation processes such as a service report and a maintenance completion report at the end of the maintenance work. The facsimile controller (FaxCont) performs facsimile communication control. An authentication manager performs authentication management. The HTTP controller performs notification processing such as various states to a remote device using the HTTP protocol. An SNMP controller (SNP PC Controller) performs notification processing of various states and the like on a remote device by SNMP (Simple Network Management Protocol). The LAN controller (LANCont) performs communication control on the LAN.

  The application is a function processing layer provided to the user such as copying, facsimile, and scanner.

  For example, when performing authentication using an IC card, if there is a user authentication operation instruction from the accessory driver and an intermodule message notification regarding information in the IC card read by the card reader, the authentication driver is stored in the NVRAM 105. The user management table is accessed and authentication processing is performed.

  After that, when a copy is instructed by the user, the request manager that has received the instruction via the user interface 109 checks the set values such as the document size and the paper size and sets them as copy job activation information. The system manager API is used to check system information necessary for starting the copy, such as status / resource management information. If there is no problem, the system manager is requested to start the application. The system manager performs scheduling control and starts an application according to a predetermined schedule.

  As a result, the copy of the application layer is activated, and the copy performs a current reading control instruction to the input device controller, an instruction to store the read image data to the spool controller, and a print control instruction to the output device controller. Thus, a copy function is provided to the user.

  In a maintenance contract for a multifunction device, it is necessary to properly deduct test prints and various report prints that are executed during maintenance work so that the billing amount is not disadvantageous for the user. In addition, a maintenance counter that counts the number of image formations during maintenance work is provided. However, during maintenance work, customers may be requested to foreground jobs such as urgent copies and PC prints, and the maintenance counter counts the number of image formations that should be excluded from the deduction. Will be deducted. Nonetheless, it is not appropriate to reject a customer's critical or urgent job for maintenance reasons.

  In the present invention, when a job request is generated in the foreground due to the customer's convenience during maintenance work and an interrupt print is executed, the test copy and various report prints made by the customer engineer are distinguished from the non-deductible items. As a result, the deduction processing is accurately performed. The details of the deduction processing will be described below together with the maintenance work flow.

  The maintenance work includes phases of a maintenance start instruction, a maintenance work instruction, and a maintenance end instruction. The general operation in each phase is as follows.

Maintenance start instruction:
Enter CE (customer engineer) password Enter maintenance mode → Set maintenance mode flag Maintenance start processing
Maintenance counter operation starts
Enter maintenance details for creating reports End of maintenance mode transition

During maintenance work:
When Passive Service is requested, check whether it can be started. Startup not possible 1 → Rejected, notify the requesting user Startup not possible 2 → Receive without starting, handle as a waiting job Startable → Job start
→ Do not add the start job print to the maintenance counter. Billing counter only.
Active Service determines that it is for maintenance, and increases the billing counter and the maintenance counter. Here, Passive Service is a service that starts in the background. On the other hand, the Active Service is a service directly requested by the user through the operation on the operation unit 111 and needs to be activated immediately. Therefore, it can be determined that the Active Service instructed from the operation unit 111 during the maintenance work is requested by the customer engineer for maintenance.

Maintenance end instruction Report creation process → Service report, machine history table (the latter can be selected)
Service report creation process Report item creation from input contents at the time of mode transition Machine history table creation process Report item creation from input contents at the time of mode transition Notification to the FWS server Note that the machine history table is a history of maintenance work by the customer engineer It leaves the result of inspecting the machine, and many items such as meter information are common with the service report.

  FIG. 4 shows a schematic procedure of a maintenance operation in the MFP according to the present embodiment in the form of a flowchart.

  First, a predetermined maintenance mode transition process (described later) is performed, and the multifunction device transitions from the normal mode to the maintenance mode (step S1).

  When there is a job activation request in the maintenance mode (step S2), a predetermined job activation determination process (described later) is performed (step S3), and whether or not the job can be activated is determined (step S4).

  If the job activation is permitted, the job is executed (step S5), and then a job completion process is performed (step S6). Since job execution is a general matter, the description is omitted here. Further, job end processing will be described later.

  Thereafter, until a maintenance end instruction is input from the customer engineer (step S7), the process returns to step S2, and job start control is continued under the maintenance mode.

  When there is a maintenance end instruction, a transition process (described later) to a predetermined normal mode is performed (step S8), and the entire processing routine is ended.

  FIG. 5 shows a processing procedure for shifting to the maintenance mode, which is executed in step S1, in the form of a flowchart. FIG. 6 shows an operation sequence at the time of shifting to the maintenance mode.

  When the customer engineer performs a predetermined operation for entering the maintenance mode (for example, pressing the start button for a long time on the operation unit 111), the user interface 109 performs an operation for shifting to the maintenance mode. Determines that the user has been instructed and requests the password.

  When this password is requested, the authentication manager checks the CE (customer engineer) password via the user interface 109 and the request manager. If the authentication result is OK, a process for shifting to the maintenance mode is started to perform the maintenance process.

  The request manager calls the mode library to request mode transition. At this time, almost simultaneously, the user interface 109 is notified that the mode transition state has been entered. Upon receiving this notification, the user interface 109 puts the operation unit 111 into a locked state. This is because, in this state, unless the user request such as the user interface 109 is locked, the mode transition process may cross the user request.

  Specifically, when a service that cannot be started after the mode transition is requested, the mode activation process is not completed during the mode transition process, so the service activation process is started. On the other hand, when the mode transition process is completed, the service is in an inconsistent state that cannot be activated. In order to avoid such a case, the request is locked as described above. Such processing is not limited to the user interface 109, but also to a LAN controller that accepts a request via a LAN.

  Next, the entry condition is checked to see if the various states of the current multifunction peripheral satisfy the condition for shifting to the maintenance mode (step S11). Since what kind of conditions should be checked is a design matter, description thereof is omitted here.

  If this entry condition is not satisfied, it is notified to the customer engineer via the user interface 109 that the migration is impossible (step S16).

  If the entry condition is satisfied, a flag indicating that the maintenance mode is entered is turned on (step S12), and a maintenance counter (see Table 11 described later) is started, that is, reset and counted. A possible state is set (step S13). Then, the result of satisfying the entry condition is notified to the related module (notifying the mode transition state).

Next, the following items regarding maintenance are input from the user interface 109 (step S14).
・ Treatment purpose (periodic inspection, failure diagnosis, replacement of consumables, etc.)
・ Measures (XX replacement, jam removal, parts replacement, firmware version update, etc.)
・ Defect contents (Select from comment description, error history, job history)

  The inputted maintenance information is written in the NVRAM 105 and temporarily held (step S15).

  When the above steps are completed, the customer engineer is notified through the user interface 109 that the transition to the maintenance mode is completed, and the display unit 110 is displayed in the maintenance mode. Normally, in the maintenance mode, a black and white reversed display state is set so that it can be understood.

  In maintenance mode, customer engineers can print test copies, test prints, error history reports, and job history reports to check operation and image quality in addition to checking and replacing hardware parts. To do.

  At this time, an interrupt print such as a customer's PC print or a customer's business partner's facsimile reception print may occur. Therefore, it is necessary to update the maintenance counter in order to perform appropriate deduction processing for making the number of interrupt prints non-deductible.

  Next, the determination of whether or not to start the service during the maintenance work and the counting process will be described. Prior to that, the service control and parameters for performing the control will be described.

  The software of the MFP 100 according to the present embodiment uses the following three types of parameters, URP, SCB, and VDP, for control. FIG. 7 conceptually shows how to use each parameter. However, the figure shows an example of generating a monitor report at the time of facsimile transmission.

  URP (User Request Parameter) is a parameter set by an operation when the user (customer) operates the user interface 109 to instruct a start. For example, parameters necessary for a job request, such as paper size, number of copies, and magnification, correspond to this.

  The SCB (Service Control Block) is a parameter for performing service control, and corresponds to, for example, a job state, a job startable mode, and resource information.

  A VDP (Virtual Display Parameter) is a parameter generated based on the URP, and changes a parameter that has changed in a job operation process at a predetermined timing. The notification of the user interface 109, HTTP, SNMP, etc. can be notified in real time by referring to this at a predetermined timing.

  Although not shown, a parameter called JLP is also provided for the job history of the application. JLP (Job Log Parameter) is a parameter that is generated to take a job history at the end of service, and is generated by copying a part of URP, SCB, and VDP. This JLP is controlled by the FIFO and stored in the NVRAM 105. When the JLP exceeds a predetermined amount, it is moved to the HDD 106 and a new job history is stored in the NVRAM 105 again.

  FIG. 8 shows a schematic configuration of URP. As shown in the figure, the URP is composed of a common part and a specific part depending on the application type.

  The common part has the ID, type, and error code of the URP itself. Since only URP is created at the time of parameter check error, the part copied to the JLP is a copy of the common part for this reason. Table 1 shows a specific data configuration example of the URP application type common part.

  In addition, the unique part of URP has user setting parameters for each application such as copying and facsimile transmission. Tables 2 and 3 show specific data configuration examples of the unique parts in copying and facsimile transmission, respectively.

  FIG. 9 shows a schematic configuration of the SCB. As shown in the figure, the SCB is also composed of a common part and a specific part according to the application type, like the URP. Table 4 shows a specific data configuration example of the application type common part of the SCB.

  The unique part of the SCB includes application status, type, stop / hold type, error code, SCB ID, pointer information to each parameter, and the like, and further includes phase management information. Table 5 shows a specific data configuration example (in the case of copying) of the SCB application type specific part.

  FIG. 10 shows a schematic configuration of the VDP. As shown in the figure, VDP is also composed of a common part and a specific part depending on the application type, like URP and SCB. Table 6 shows a specific data configuration example of the VDP application type common part.

  The VDP is generated based on the URP. For example, in the case of copying, VDP has progress information such as the total number of printed sheets (number of original sheets × number of copies), the number of read sheets, the number of printed sheets, and the like, and has data indicating the current state of the application. . Table 7 shows a specific data configuration example of the VDP application type specific part (in the case of copying).

  Here, returning to FIG. 7, the relationship between the above three types of parameters and application control will be described.

  When the user selects the Fax menu on the operation unit 111, selects a destination, etc., and presses the start button, the parameter selected by the user is notified to the request manager.

  The request manager generates a URP, sets the parameter and automatic setting selected by the user in the URP, and checks whether there is an invalid parameter. If there is no problem in the parameters, SCB and VDP are secured through the system manager API. The parameter check is performed by the request manager, but the prohibition process is naturally performed even at the level of the user interface 109.

  During the securing and checking period of SCB and VDP, task switching is not performed and the request manager occupies processing. The reason is that when a task is switched when securing or checking resources (described later), the resource that is scheduled to be secured in the next step becomes unavailable during the task switch. This is because there is a possibility of becoming. Furthermore, the SCB and VDP securing and checking processes are performed by the request manager because there is no occurrence of a cross sequence in the outermost module.

  The SCB is generated based on the URP, and is further set by adding resource information and phase information that the system manager has in advance. Resource information is roughly classified into three types: exclusive resources, machine state resources, and application unique resources.

  Exclusive resources, such as print engines, scanners, and modem public lines, are occupied during use, so resources that can be used exclusively or semaphore resources that have limited sharing (for example, encoding processing for image processing) Multiplicity, etc.).

  The machine state resource is a software resource such as an application management memory and a storage memory capacity, and a mode resource indicating that the multifunction peripheral is in an application regulation mode.

  The application unique resource is resource information that accompanies the activation of a specific application, and includes application unique resources such as a copy card not installed, frequency, and insufficient balance. Application phase transition conditions are also included in this resource.

  Since the above description of resources is general in terms of embedded control, descriptions other than those relating to the gist of the present invention are omitted.

  The prohibition of application activation in the maintenance mode, which is one of the points of the present invention, is generated based on the mode resource application restriction information among the resource information of the system manager when the SCB is generated. .

  Table 8 shows a job list describing the mode resource restriction information for each application. In the same table, a record is provided for each application, and the mode in which startup is not possible, and whether the number of image formations is deducted when the job is executed in the maintenance mode (that is, whether the job is to be deducted) Is done.

  According to Table 8, it becomes a quick reference table for confirming whether it is a mode that cannot be activated for each application or whether it is a deduction target. In this embodiment, even if a job is executed during maintenance work, it can be designated as a non-deductible target while referring to the job history, so that the number of prints is not added to the maintenance counter. The application need not be restricted from being disabled when in maintenance mode.

  Table 9 shows a quick reference table format for confirming applications whose activation is prohibited for each mode. From the table, for example, it can be confirmed that activation of applications such as PC printing and PC printing / security reception is prohibited under the maintenance mode.

  Such information is stored in phase Info [x]. It is stored in McStatus res (x is the number of phases constituting the Service), and it is determined whether or not it can be activated during maintenance work based on this information. For example, when setting the parameters of the SCB for facsimile transmission, as shown in Table 8, information that activation is not possible during maintenance, diagnosis, and remote maintenance is set. Further, whether the activated application is a deduction object or a non-deduction object is similarly set to Apl CountStatus from the application restriction information of the mode resource of the resource information that the system manager has.

  Next, based on the generated resource information, it is determined whether the first phase is Active or Passive. This is because Active is a phase that needs to be started immediately, and immediately determines whether resources can be secured and whether a job can be started (hereinafter referred to as “resource check”). On the other hand, since Passive may be activated later, at that time, it is not determined whether to secure resources.

  In the case of Passive, the release of resources in the current phase and the resource check in the next phase occur after each phase. On the other hand, in the case of Active, the resource check of the continuous Active phase is performed at the time of the resource check of the first phase.

  Table 10 shows some contents related to the resource determination of the SCB for facsimile transmission shown in FIG. Since the first “Scan & Store” phase (Scan & Store in Table 10) performed by the scan controller is Active (the notation in Table 10 is ACT), the mode resource check is performed in the request manager activation request processing. The resources are secured and checked in the order of VDP generation, exclusive resource reservation, and storage memory reservation.

  Table 10 shows the result of resource determination at the time of facsimile transmission shown in FIG. Since the Scan & Accumulation phase performed first by the scan controller is Active, in the request manager activation request processing, the mode resource check, VDP generation, exclusive resource allocation, and storage memory allocation are performed in this order. Reserve and check resources.

  First, it is determined whether or not the mode is a non-startable mode from the non-startable mode set in the SCB by checking the mode resource. If the activation is possible, the process proceeds to the next step. If the activation is impossible, the process is terminated without being activated.

  For example, in the case of facsimile transmission, information indicating that the activation in the maintenance mode is not possible is set in the SCB as shown in Table 10 in accordance with the settings in Table 8, so that the activation is impossible and the process ends. On the other hand, since copying and facsimile reception are not activated in the maintenance mode, such information is not set in the SCB and it is determined that activation is possible, and the process proceeds to the next step.

  Next, VDP is generated. Since URP and SCB have already been secured for application management, if VDP can be generated, management memory is secured and the check is completed. If the management memory cannot be secured, the process is terminated without starting.

  Next, exclusive resources such as the scanner, the RAM 104, and the HDD 106 are secured. If the exclusive resource can be secured, the process proceeds to the next step. If the exclusive resource cannot be secured, the process is terminated without being activated.

  Next, a memory for storage is secured by generating a file using the file system of the OS. If it can be secured, the process proceeds to the next step. If it cannot be secured, it is determined that the memory is insufficient and the process is terminated without being started.

  In the subsequent phases, if there is an active phase, the above exclusive resource is secured. In the example shown in FIG. 7, since this is Passive, this process is not performed. However, when copying and printing without performing the accumulation process, all phases are set to Active. Do.

  As described above, the resource is secured and checked. Note that when the first phase is Passive, no resource is secured and checked.

  Subsequently, the SCB is put in a waiting queue for scheduling. The wait queue includes an idle, ready-active, ready-passive, run, wait (time designation) queue, and the like.

  Idle is an unused SCB link, and is designed so that the number of queues is equal to the maximum number of applications that can be accepted by software in the hardware configuration of the multifunction peripheral 100. Further, Ready-Active is an SCB link of an active application, and Ready-Passive is an SCB link of a passive application. Run is the SCB link of the application in the running state, and the number of queues is designed so that the maximum number of software that can be executed simultaneously in the hardware configuration of the multifunction peripheral 100 is reached.

  In the example shown in FIG. 7, the facsimile transmission is arranged in Ready-Active.

  Then, the request manager makes an application activation request to the system manager. The system manager performs scheduling by using this event as a trigger.

  If the first phase is Active, the resource check has already been completed, so the application is changed to the Run queue and a job activation instruction is issued to the Fax module. When the Fax module receives this event, it instructs each functional module such as the scanner controller, fax controller, report generator, printer controller, etc. to control each phase based on the SCB and reflects the result in the VDP. Let

  During execution of each phase, the application such as Fax updates only the SCB application-specific information, and the system manager updates only the SCB common information, thereby realizing SCB exclusive control.

  At the end of each phase, an application status notification is notified to the system manager. The system manager uses this as a trigger to move to the next phase start processing.

  If the next phase is Passive, the current resource is released, the resource check for the next phase is performed, and the SCB is placed in the Ready-Passive queue. If the next phase is Active, the resource has already been implemented at the time of request manager activation request processing, so the resource check is not performed and the next phase processing is started as it is.

  In the example shown in FIG. 7, the subsequent reading & communication, report creation & storage, and reading & P printing are all processed as a passive phase.

  When the above process ends, the application generates a JLP based on the contents of the SCB and VDP, and ends the process.

  FIG. 11 shows, in the form of a flowchart, a processing procedure for determining whether or not to start a job, which is executed when a background job is generated during the maintenance mode. This processing routine corresponds to the processing executed in step S3 of the flowchart shown in FIG.

  First, URP is set (step S21), and URP parameters are checked (step S22). If the URP parameter check fails, a result indicating that the job cannot be started is returned (step S26).

  On the other hand, if the URP parameter check is successful, an SCB is subsequently set (step S23), and a resource check is performed (step S24). If the resource check is successful, the result of job activation permission is returned (step S25). If the resource check fails, a result indicating that the job cannot be started is returned (step S26).

  FIG. 12 shows the procedure of the resource check process performed in step S24 in the form of a flowchart.

  First, mode resource check processing is performed (step S31), and the check result is determined (step S32). If the mode resource check fails, a result indicating that the resource check has failed is returned.

  Subsequently, VDP generation processing is performed (step S33), and it is determined whether or not the VDP has been successfully generated (step S34). If the VDP generation fails, a result indicating that the resource check has failed is returned.

  Subsequently, the exclusive resource is secured (step S35), and it is determined whether or not the exclusive resource was successfully secured (step S36). If the exclusive resource allocation fails, a result indicating that the resource check has failed is returned.

  Subsequently, the storage memory is secured (step S37), and it is determined whether or not the storage memory can be secured safely (step S38). If the storage memory allocation fails, a result indicating that the resource check has failed is returned.

  Since the VDP generation process in step S33, the exclusive resource securing process in step S25, and the storage memory securing process in step S37 are general processes, detailed description thereof is omitted.

  FIG. 13 shows the processing procedure of the mode / resource check executed in step S31 in the form of a flowchart.

  First, the current mode and mode reading are performed (step S41).

  Next, it is checked whether or not the mode is being changed (step S42). If the mode is being changed, a result indicating that the mode resource check has failed is returned.

  Next, it is checked whether or not it is a start-disabled mode (step S43). Here, if the mode is not startable, a result indicating that the mode resource check has failed is returned.

  If the above check is successful, a result indicating that the mode resource check is successful is returned.

  FIG. 14 shows a processing procedure for ending a job started during the maintenance mode in the form of a flowchart. This processing routine corresponds to the processing executed in step S6 of the flowchart shown in FIG.

  First, the VDP is finally updated (step S51), and then the SCB is collected and updated by reflecting the VDP value (step S52).

  Next, JPL is acquired (step S53), and JPL is set (step S54). JPL is ring buffer controlled, acquires the oldest log, and writes the information of the job that has been completed this time.

  Then, after releasing the VDP and SCB, the exclusive resource is released, and this processing routine ends.

  Next, the counter process will be described. Since the processing related to printing is the same as that of normal printing, copying machines, and multifunction machines, description thereof is omitted here.

  FIG. 15 shows a counter processing sequence and a processing flow in the DV library, taking as an example a case where a monitor report is generated after facsimile transmission. Table 11 shows a list of counters.

  The Fax module, which has received the print processing progress notification of the completion of one-page printing from the printer controller, appropriately updates parameters such as the current print count of the SCB, and then calls the counter control DV library.

  At this time, the deduction / non-deduction classification, application type, printed paper size, and color mode at the time of printing are passed to the DV library based on the SCB parameters.

  As shown in Table 11, the DV library holds and controls a plurality of counters corresponding to the target application, color type, billing or maintenance counter type, and paper size classification in the NVRAM 105, and the parameters passed The counter to be increased is specified and increased based on the above.

  The billing or maintenance counter type is a counter that billing counts all billing including deduction and non-deduction, and the maintenance counter counts the number of prints to be subtracted due to maintenance or the like.

In addition, “meter category on service” in Table 11 indicates a category of meters notified to the customer. This meter is divided into
・ Meter 1 Full Color (full color)
・ Meter 2 Simple Color (single color)
・ Meter 3 BW (black and white)
When the operator operates the operation unit 111 to confirm the meter value, the count values of the respective meter sections are totaled and displayed on the display unit 110.

  Further, the paper size classification is for determining and classifying paper sizes having different count units and charging units based on a predetermined paper size standard. In the present embodiment, the A3 size is used as a reference, and the classification is A3 or more and less than A3. In this way, by supporting the paper size classification, it is possible to provide more detailed aggregate information in cooperation with external client or server software.

  When each of the meters 1 to 3 is counted, in order to match the count unit for each counter, the count value of A3 or more is counted by a predetermined multiple (in this embodiment, twice) based on the section of less than A3.

  For example, in the example shown in FIG. 15, since the monitor report is a report that is automatically activated, an automatic report is set as the application type of the SCB. Therefore, the counters of the target applications Print and Report in Table 11 are counted up.

  Further, the monitor report has the color type set to black and white (notation in Table 11 is BW), the deduction type is non-deductible, and the paper size is A4 size parameter set to SCB. The billing counter of counter ID010 to be incremented is passed to the DV library together with the information, and can be specified.

  In addition, when a customer engineer tests and copies an A3 size chart during maintenance, the application type is copy, the color type is Full Color, the deduction type is deduction, and the paper size category is A3 or more, and the counter ID 013 is increased. Billing counters and maintenance counters with counter ID 015 can be specified.

  Such a counting process is repeated for the number of prints.

  When the counter has finished counting up, the DV library returns the increased counter ID and the increment as a return.

  Based on the value, the Fax module updates the VDP counter information (see Table 6), that is, increases the count-up information of the corresponding counter.

  Eventually, since this VDP information remains in the JLP, counter information for each job remains in the job history information.

  Next, processing when maintenance work is completed will be described.

  The maintenance end operation is started by a predetermined operation on the operation unit 111 (for example, pressing the start button for a long time, pressing the button on the touch panel for maintenance end, etc.). FIG. 16 shows a processing procedure for starting mode transition when the maintenance work is completed in the form of a flowchart. This corresponds to step S8 in the flowchart shown in FIG.

  When receiving the maintenance end instruction, the user interface 109 notifies the request manager of this. When the system manager recognizes that the maintenance end instruction has been received via the request manager, the system manager notifies the user interface 109 or a module that receives an activation request for an application such as a LAN or a modem to lock the activation request ( Step S61). This is because, since the calculation process of the counter value is included in the report (described later), when the maintenance end process is performed, the job request is temporarily closed so that the count value is not changed any more. Further, the user interface 109 prohibits acceptance of an interrupt key so that no new print processing occurs during the processing.

  Next, the user interface 109 displays the job history after the transition to the maintenance mode via the display unit 110. The customer engineer directly designates, for each job, whether the print executed during the maintenance mode is deduction or non-deduction through the job history display screen. Based on this designation result, the number of subtracted or non-deducted sheets is increased or decreased to correct the maintenance counter (step S62). Details of the operation of displaying the job history after the maintenance work and directly specifying whether each job should be deducted or not deducted on the display screen will be described later.

  Next, the customer engineer is requested to confirm via the user interface 109 whether to print only the service report or whether to print the machine history table together with the service report (step S63).

  If the machine history table is not created, service report creation processing is performed (step S68). When creating a machine history table, a service report creation process is executed (step S64), and then a machine history table creation process is executed (step S64).

Next, each item stored at the time of report creation is read and converted into text data.
Then, an e-mail header addressed to the FWS server is created and encrypted, and notified to the FWS server as an e-mail (step S66).

  Now that the work associated with the end of the maintenance is completed, the process to move to the normal mode is performed next, the flag information indicating that the machine is in the maintenance mode, the maintenance counter is reset, and the process shifts to the normal mode. (Step S67).

  In the service report creation process, the contents of the service report are displayed, displayed on the user interface 109 sequentially, and the contents are confirmed, added, and changed. However, the unique information of the MFP installed at the customer site is not changed. FIG. 17 shows the procedure of the service / report creation process executed in steps S64 and S68 in the form of a flowchart.

  Information is read from the ROM 103 or the NVRAM 105 (step S71), displayed on the display unit 110 (step S72), and the content is confirmed. Items to be checked here include customer management ID, model code, machine number, service classification, and the like. When the customer engineer confirms (approves) each of the above items (step S73), it is temporarily stored in the RAM 104 and held so that it can be printed in the corresponding column in the report (step S74).

  In order to retain the items in the report for printing, the RAM 104, the NVRAM 105, and the HDD 106 can be used. Even when an abnormality such as NVRAM 105 or HDD 106 that causes a power interruption occurs, it is preferable that the storage means can hold the data of the item.

  Next, information at the start of the maintenance work is read (step S75), and items to be automatically set are set from the maintenance information (step S76).

  Items to be set and confirmed from information at the start of maintenance work can include a purpose code and an error code. The purpose code is set from the entered treatment purpose (periodic inspection, failure diagnosis, consumable replacement, etc.) and confirms the content of the failure information treatment. The error code is set from the entered defect content (selected from comment description, error history, and job history), and the error code at the time of occurrence of the defect is set from the error history.

  Items that are automatically set from the maintenance information can include failure information treatment content and next work memo. The failure information treatment content includes error content and treatment code. As the error content, the error content stored in advance corresponding to the error code is described. As the treatment contents, a treatment code stored in advance and the treatment contents corresponding to the error code are described. When additional treatment is required, the treatment content is additionally input from the operation unit 110 or the like. Further, in the case of inspection or firmware version update in the ROM 103, since there is no error code, the code and contents are additionally input. The next work memo describes the parts used, the reason for consumables used, the reason for consumables, and the like. These set pre-stored replacement parts corresponding to error codes. As a result, when an input is made to the FWS server, parts are automatically ordered. If there are additional parts, enter them. When there are parts on hand and the work is completed, the parts are deleted.

  Additional items to be entered as maintenance information include customer engineer employee number, maintenance reception date, reception time, travel time to work site, visit date, maintenance work start time and end time, failure You can list cut-off time, diagnosis / repair / inspection time, etc. As the visit date and the start time, the date and time when the maintenance mode is entered may be automatically set. In addition, the user interface 109 notifies that the time obtained by adding the diagnosis / repair / inspection time to the failure separation time is set in the range of the total work time. Further, since miscopy information received from customers is also subject to deduction, meter 1, meter 2, and meter 3 for counting miscopy are input.

  Then, the maintenance information and the items automatically set from the maintenance information are displayed on the display unit 110 (step S77), and the contents are confirmed. When the customer engineer confirms (approves) each of the above items (step S78), these items are temporarily stored in the RAM 104 and held so that they can be printed in the corresponding columns in the report (step S79). If approval cannot be obtained, a change item setting process is performed (step S92), the process returns to step S57, and item display and confirmation are performed again.

  Next, the meter information is read (step S80), and an end meter calculation process (step S81), a maintenance work meter calculation process (step S82), and a visit meter calculation process (step S83) are performed.

  Then, the automatically calculated meter information is displayed on the display unit 110 (step S64), and the contents are confirmed. When the customer engineer confirms (approves) each of the above items (step S85), these items are temporarily stored in the RAM 104, filled in the corresponding columns in the report, and stored in the HDD 106 (step S86). If approval cannot be obtained, the meter information change item setting process is performed (step S93), and the process returns to step S83 to display and confirm the item again.

  Next, an item to be separately input by handwriting is displayed on the display unit 109 (step S87), and the customer engineer is prompted to input by handwriting from the operation unit 110. Separately, an item to be input by handwriting is a return time or the like. When handwritten input is performed (step S88), these are temporarily stored in the RAM 104, filled in the corresponding fields in the report, and stored in the HDD 106 (step S89).

  Then, a report is created using the information written in steps S74, S79, S86, and S89, and stored in the HDD 106 (step S90). Thereafter, the process proceeds to the reading and printing phase, and the service report is printed (step S91). Further, when the creation of the machine history table is instructed, it is created in the same manner as the service report, but the description is omitted here.

  FIG. 18 shows a detailed procedure of the end meter calculation process executed in step S81 in the form of a flowchart.

  First, the counter ID, end meter 1, end meter 2, and end meter 3 are initialized. Specifically, the end meter 1, the end meter 2, and the end meter 3 are reset to 0, and processing is performed from the first counter ID001 (step S101).

  Next, since only the billing counter is counted by the end meter, it is determined whether the count type of the counter is billing (step S102). If it is not billing, it is determined whether or not the counting operation has been completed for all counters (step S114). If billing is performed, it is determined whether the counter meter category is category 1 (step S103). If not, the meter classification 2 is determined (step S107).

  If it is meter category 1, the paper size category is determined (step S104). If it is A3 or larger, the count value is doubled as described above and the end meter 1 is totaled (step S104). In S105), if it is less than A3, the end meter 1 is counted as it is (Step S106).

  Similarly, in the case of meter category 2, the paper size category is determined (step S108), and the end meter 2 is counted for A3 or larger size (step S109). (Step S110).

  If neither meter category 1 nor 2 is determined, similarly to meter category 3, the paper size category is determined (step S111), and the end meter 2 is tabulated for sizes larger than A3 (step S112). The end meter 3 is counted as it is (step S113).

  When the above processing is completed, it is determined whether the counting work has been completed for all counters (step S114). If the counting has not been completed, the count type is determined for the next counter ID counter (step S115). The same processing is performed from (Step S102), and if not, meter correction processing is performed (Step S116), and counting of the end meter 1, the end meter 2, and the end meter 3 is completed.

  The meter correction process is a process for correcting each end meter by adding an expected billing count value of a service report or machine history table to be executed in the future, and details thereof will be described later.

  FIG. 19 shows a detailed procedure of the maintenance meter calculation process executed in step S82 in the form of a flowchart.

  The way of counting is the same as the counting process of the end meter, and the counter ID, the maintenance meter 1, the maintenance meter 2, and the maintenance meter 3 are initialized (step S121).

  Next, since only the maintenance counter is counted by the maintenance meter, it is determined whether or not the count type of the counter is maintenance (step S122). If it is not maintenance, the counting work is completed for all the counters. (Step S134).

  If the counter type is maintenance, it is subsequently determined whether the meter category of the counter is category 1 (step S123). If not, meter category 2 is determined (step S127).

  If it is meter category 1, the paper size category is determined (step S124), and maintenance meter 1 with a size of A3 or larger is totaled (step S125). If less than A3, maintenance meter 1 is totaled as it is. (Step S126).

  Similarly, in the case of the meter category 2, the paper size category is determined (step S128), and the maintenance meter 2 is aggregated at a size larger than A3 (step S129). (Step S130).

  If neither meter category 1 nor 2 is selected, the paper size category is similarly determined as meter category 3 (step S131), and maintenance meter 2 is tabulated for sizes larger than A3 (step S132). Then, the maintenance meter 1 is totaled as it is (step S133).

  When the above processing is completed, it is determined whether the counting work has been completed for all counters (step S134). If the counting has not been completed, the count type determination is performed for the counter of the next counter ID (step S135). From (step S122), the same processing is performed. If not, meter correction processing is performed (step S136), and the counting of the maintenance meter 1, the maintenance meter 2, and the maintenance meter 3 is completed.

  FIG. 20 shows the procedure of meter correction processing executed in step S116 of the flowchart shown in FIG. 18 and step S136 of the flowchart shown in FIG. 19 in the form of a flowchart.

  In the meter correction process, it is checked whether the machine history table is instructed to be printed (step S141). If the machine history table is not instructed to be printed, the service report meter is determined and increased (step S142). .

  Further, when the machine history table is instructed to be printed, the service report meter confirmation and increase processing (step S143) and the machine history table meter determination and increase processing (step S144) are performed to correct the meter. The process ends.

  FIG. 21 shows the procedure of meter determination and increase processing in the form of a flowchart.

  In the meter determination and increase processing, first, the service startup parameters (“application type”, “color type”, “deduction type” (deduction and non-deduction) stored in the program as resource information possessed by the system manager, etc. Distinction), “number of prints” (the number of prints is determined in advance for report services), and “paper size” (paper size for printing the report)) based on the designation of the service report and the machine history table, The corresponding service activation parameter is read (step S151).

  As is clear from the list of counters shown in Table 11, “application type”, “color type”, “deduction type” (distinguishment between deduction and non-deduction), “paper size classification” (specified from paper size) from the read parameters. ) And the counter ID that is actually increased during printing is specified (step S152).

  Next, the increment value of the counter is calculated at the time of actual printing based on the number of printed reports and a predetermined multiple of the “paper size classification” of the counter, which in this embodiment is twice as described above (step S153). ).

  Next, since the meter classification N (N = 1 to 3) can be uniquely identified from the counter ID, either the end meter N or the maintenance meter N is identified based on this (Step) In step S154, the increment of the previously determined counter is added to increase the meter (step S155).

  FIG. 22 shows the detailed procedure of the visit meter calculation process executed in step S83 in the form of a flowchart.

  The visit meter can be calculated by taking the difference between the end meter N and the maintenance meter N for each visit meter N (step S161, step S162, step S163).

  In the service report creation processing procedure shown in FIG. 17, a report for printing a service report or the like is created after steps S74, S79, S86, and S89. The application is started from step S80. It may be done before. In this case, when the application is started and the paper size is determined and scheduling is performed, control is performed so that the application waits for execution until “meter value determination and report start instruction wait”.

  In the case of such a modification, the parameters for correction shown in FIG. 20 are read from the SCB of the application waiting for execution start, the calculation process of each meter is completed based on the parameters, and the process of step S89 ends. When is confirmed, the execution waiting state is canceled and report generation is started.

  Normally, in an automatic report or the like, when a sheet that matches the sheet size of the report print is not stored in the tray, another sheet size that can be automatically printed can be selected and printed. In the above-described modification, even in such a case, the other paper size selected is stored in the SCB, and meter correction processing corresponding to the paper size is possible.

  In addition, in the case of a device with a sensor that detects the remaining amount of paper in the tray, in the situation where the sensor detects that the remaining paper is about to run out, you can select another size paper in the same way, Paper out-of-paper is reduced and meter correction processing according to the paper size is possible.

  When printing a service report, the report print priority is set to high. This is because if the interrupt printing or the like is performed while the report is being printed, the meter value to be subtracted becomes inaccurate, so that the job interruption is suppressed by setting the priority higher.

  In addition, if a jam occurs when creating a service report or machine history table, an accurate meter cannot be counted, so everything is re-executed from the service report meter calculation.

  An example of a service report is as shown in FIG. In the example shown in the figure, there are only two copies of the technical center bank and customer copy, but when you need a sales office copy and issuer copy (both basic contents are the same as the technical center line) The number of prints is four.

  FIG. 23 shows, in the form of a flowchart, the processing procedure for notifying the FWS server of the service report, which is executed in step S66 of the flowchart shown in FIG.

  When each item stored in the service report creation process shown in FIG. 17 is read (step S171), the report data is converted into text data (step S172).

  Next, an e-mail header addressed to the FWS server is created in the text data (step S173), the mail document is further encrypted (step S174), and is sent as an e-mail to the FWS server (step S175).

  By notifying the service report to the FWS server according to the processing procedure shown in FIG. 23, when the work accompanying the end of the maintenance is completed, the process for shifting to the normal mode is performed. FIG. 24 shows the procedure of the mode transition process executed in step S67 of the flowchart shown in FIG. 16 in the form of a flowchart.

  In this migration process, first, entry conditions are checked (step S181). If this check fails, a result indicating that the mode cannot be changed is returned (step S185).

  On the other hand, if the entry condition check is successful, then the flag information indicating that the maintenance mode is entered is reset (step S182), the maintenance counter is further reset (step S183), and the maintained maintenance information is retained. The information is cleared (step S184), and the mode is changed to the normal mode.

  In the present embodiment, a job history is displayed on the display unit 110 after the maintenance work is completed, and whether or not each job should be deducted or not deducted is specified on the display screen via the user interface 109 ( (See step S62 in FIG. 16). Therefore, it is possible to designate interrupt prints made by foreground job requests such as urgent copies during maintenance work as non-deductible items and reduce the number of image formations from the maintenance counter. Thus, appropriate deduction processing can be performed.

  Hereinafter, an operation for displaying the job history after the maintenance mode via the user interface 109 and increasing / decreasing the number of deductions and the number of non-deductions for each job will be described.

  First, the customer engineer instructs the request manager to display a completed job list via the user interface 109. In response to this, the request manager checks the job history list, passes the job history list to the user interface 109, and displays the job history after the maintenance mode on the display screen of the display unit 110 (FIG. 26). checking).

  Next, when the display portion of each job on the touch panel type operation unit 110 is pressed, details about the designated job are displayed as shown in FIG. The example shown in FIG. 27 is a test copy for image quality confirmation.

  If a fax is received from a customer during maintenance work, it is counted as non-deductible as shown in FIG.

  Further, at the end of the maintenance, when the customer engineer asked the customer to perform a PC print as an operation check, for example, it is assumed that the customer instructed 20 prints just because there is a conference print. FIG. 29 shows an example in which details of the job history are displayed.

  As for the confirmation print, 20 sheets are subtracted from too many sheets. Since only the first few prints are meaningful as confirmation prints, each meter is selected on the touch panel, and the count value to be subtracted is corrected with the up / down buttons or the numeric keypad.

  In the job history display screen shown in FIG. 29, there are too many full-color prints and 10 black-and-white (BW) prints performed as test copies. Select these counter values and press the countdown button. Reduce the number of deductions to one. Then, as shown in FIG. 30, nine sheets reduced as the number of deductions are added as the non-deduction number.

  The above operation is realized in the multi-function device 100 by the following processing procedure. FIG. 25 shows a job history display and correction sequence and flow.

(Procedure 1) Upon receiving a maintenance end instruction from the user interface 109, the request manager reads the history of jobs after the maintenance mode using the API of the system manager.

(Procedure 2) The read job history information is transmitted to the user interface 109.

(Procedure 3) Upon receiving the notification, the user interface 109 displays the job history information as shown in FIG.

(Procedure 4) The customer engineer performs an operation of changing the counter value on the job history screen as shown in FIG. If “OK” is selected, the request manager is notified of the changed job Uid, counter ID, and changed counter value information.

(Procedure 5) The request manager determines the counter ID based on the notified information (specifically, the counter ID to be corrected based on the application type and color type information in the job history of the specified job) To determine). Then, it notifies the system manager, corrects the JPL that is the log information of the corresponding Uid, and calls the DV library to change the counter value of the corresponding counter ID.

(Procedure 6) When the customer engineer corrects the counter value and then presses “OK” on the job history screen shown in FIG. 26, the job history display confirmation work is completed, and the process proceeds to the next step.

(Procedure 7) On the other hand, if the customer engineer has performed an operation of changing the counter value on the job history screen as shown in FIG. 30, but does not “OK”, the meter information before update (non-deductible counter value, The deduction counter value) is temporarily held. Then, it is determined whether the specified meter is deducted or non-deductible, and in each case, it is determined whether or not the counter should be subtracted, and the addition and non-deduction of the deduction counter is performed according to the determination result. Counter subtraction is performed. After these counter processes are performed, if the value of the deduction counter or the non-deduction counter is 0 or more, the job history screen is updated and the input of the customer engineer's counter value marching operation is awaited. Further, when the value of the deduction counter or the non-deduction counter becomes less than 0, an NG notification is sent to the customer engineer.

  After correcting the maintenance counter in this way, the user engineer is prompted to confirm whether to print the service report only or print the service report + machine history table to the customer engineer. Ask. Then, the service report creation process shown in FIG. 17 is performed. Subsequent report creation & printing and FWS notification are as described above.

  With the above configuration, even when a customer makes an emergency copy during maintenance, or when there are more PC prints requested for operation confirmation than necessary, deductions and non-deductions can be properly cleared and reports can be generated. it can.

  Such maintenance counter update processing and deduction processing can be realized by rewriting firmware stored in the ROM 103 in the multifunction peripheral 100. However, it may be difficult to update the firmware because it is a conventional machine. In order to give the same type of functions to multifunction devices sold and installed in the past, it is necessary to make major changes to the firmware, such as adding maintenance counters, adding user interface screens, and changing job and resource controls. It's not easy. FIG. 31 shows another configuration example of the FWS system that solves this problem. Hereinafter, an operation procedure on the illustrated system will be described.

(Procedure 1) A maintenance PC used by a customer engineer is connected to the multifunction peripheral, and job history data and counter values are downloaded from the maintenance PC.

(Procedure 2) On the maintenance PC, an application for confirming and correcting the job history is started, and the job history is displayed on the display screen in the same manner as shown in FIGS. Correct the counter value. Whether the application activated during the maintenance mode is deducted or not deducted is determined by having data corresponding to Table 8 on the PC side.

(Procedure 3) The maintenance PC uses 3. Correct based on the counter value corrected in the job history.

(Procedure 4) Based on the above, service report and machine history table document data are created, and a printout instruction is issued from the maintenance PC to the multi-function peripheral. However, the report print is included in the deduction as described above.

(Procedure 5) Next, the service report data is transferred from the maintenance PC to the FWS server via a transfer medium such as the Internet (including removable media such as an intranet, FDD, and USB memory).

  As described above, by correcting the deduction and non-deduction counter values on the PC side that has taken up the job history and counter values, appropriate counter deductions can be realized without changing the firmware even in the conventional model. .

  Further, the above-described operation using the maintenance PC may of course be performed in the form of remote maintenance.

  The present invention has been described in detail above with reference to specific embodiments. However, it is obvious that those skilled in the art can make modifications and substitutions of the embodiment without departing from the gist of the present invention. That is, the present invention has been disclosed in the form of exemplification, and the contents described in the present specification should not be interpreted in a limited manner. In order to determine the gist of the present invention, the claims should be taken into consideration.

FIG. 1 is a diagram schematically showing the overall configuration of an FWS system that centrally manages maintenance information of a multifunction machine by a customer engineer. FIG. 2 is a diagram schematically illustrating the hardware configuration of the multifunction peripheral 100. FIG. 3 is a diagram schematically illustrating a software configuration for controlling operations on the multifunction peripheral. FIG. 4 is a flowchart showing a schematic procedure of the maintenance operation. FIG. 5 is a flowchart showing a processing procedure for the MFP 100 to shift to the maintenance mode. FIG. 6 is a diagram showing an operation sequence when the multifunction peripheral 100 shifts to the maintenance mode. FIG. 7 is a diagram for explaining the concept of parameters used in the multifunction peripheral 100. FIG. 8 is a diagram showing a schematic data structure of URP. FIG. 9 is a diagram showing a schematic data structure of the SCB. FIG. 10 is a diagram showing a schematic data configuration of VDP. FIG. 11 is a flowchart showing a processing procedure for determining whether or not a job can be activated when a background job is generated during the maintenance mode. FIG. 12 is a flowchart showing the procedure of the resource check process. FIG. 13 is a flowchart showing the mode resource check processing procedure. FIG. 14 is a flowchart showing a procedure of job end processing. FIG. 15 is a diagram showing a counter processing sequence and a processing flow in the DV library. FIG. 16 is a flowchart showing a processing procedure for starting mode transition when the maintenance work is completed. FIG. 17 is a flowchart showing the procedure of the service / report creation process. FIG. 18 is a flowchart showing a detailed procedure of the end meter calculation process. FIG. 19 is a flowchart showing a detailed procedure of the maintenance meter calculation process. FIG. 20 is a flowchart showing the procedure of meter correction processing. FIG. 21 is a flowchart showing the procedure of meter determination and increase processing. FIG. 22 is a flowchart showing a detailed procedure of the visit meter calculation process. FIG. 23 is a flowchart showing a processing procedure for notifying a service report to the FWS server. FIG. 24 is a flowchart showing a procedure of a mode transition process for returning from the maintenance mode to the normal mode. FIG. 25 is a diagram illustrating a job history display and correction sequence and flow. FIG. 26 is a diagram for explaining an operation of displaying the job history after the maintenance mode and increasing / decreasing the number of deductions and the number of non-deductions for each job. FIG. 27 is a diagram for explaining an operation of displaying the job history after the maintenance mode and increasing / decreasing the number of deductions and the number of non-deductions for each job. FIG. 28 is a diagram for explaining an operation of displaying the job history after the maintenance mode and increasing / decreasing the number of deductions and the number of non-deductions for each job. FIG. 29 is a diagram for explaining an operation of displaying the job history after the maintenance mode and increasing / decreasing the number of deductions and the number of non-deductions for each job. FIG. 30 is a diagram for explaining an operation for displaying the job history after the maintenance mode and increasing / decreasing the number of deductions and the number of non-deductions for each job. FIG. 31 is a diagram showing a modification of the FWS system. FIG. 32 is a diagram showing a configuration example of a service report. FIG. 33 is a diagram showing a configuration example of a maintenance completion report.

Explanation of symbols

100 ... MFP 101 ... CPU
102 ... Bus 103 ... ROM
104 ... RAM
105 ... NVRAM
106 ... HDD
DESCRIPTION OF SYMBOLS 107 ... Image processing part 108 ... UI interface 109 ... User interface 110 ... Display part 111 ... Operation part 112 ... Communication interface 113 ... LAN interface 114 ... Serial interface 115 ... USB interface 116 ... Modem 117 ... Coin kit 118 ... Device * Interface 119... Reading device unit 120... Printing device unit 121.

Claims (6)

An image forming apparatus that outputs image information and manages the number of image formations,
Image forming means for forming image information on a medium;
A counter that counts the number of image formations performed by the image forming unit;
A maintenance counter for counting the number of image formations performed by the image forming means during maintenance work;
Job history storage means for storing a history of jobs executed by the image forming means;
Job history display means for displaying a history of jobs during maintenance work stored in the job history storage means;
Job deduction / non-deduction designation means for designating deduction or non-deduction for the job history job displayed on the job history display means;
Maintenance counter control means for not adding the number of times of image formation of the job designated as the object of non-deduction by the job deduction / non-deduction designation means to the maintenance counter;
An image forming apparatus comprising: A management device for managing the number of image formations in an image forming device,
Connection means for connecting to the image forming apparatus;
Job history acquisition means for acquiring the number of image formations and job history executed by the image forming apparatus;
Job history display control means for controlling the display of the acquired job history;
Job deduction / non-deduction designation means for receiving designation of deduction or non-deduction for jobs in the job history under maintenance controlled by the job history display control means;
A deduction processing unit that does not add the number of image formations of a job designated as a non-deduction target by the job deduction / non-deduction designation unit to the number of image formations executed by the image forming apparatus;
A management apparatus comprising: A method of managing the number of image formations in an image forming apparatus that outputs image information,
A counting step for counting the number of times of image formation performed by the image forming apparatus;
A maintenance counting step for counting the number of times of image formation performed by the image forming apparatus during maintenance work;
A job history storage step for storing a history of jobs executed by the image forming apparatus;
A job history display step for displaying a history of the job during the maintenance work saved by the job history saving step;
Job deduction / non-deduction designation step for designating deduction or non-deduction for the job history job displayed in the job history display step;
A maintenance counter control step that does not add to the maintenance counter the number of image formations of the job designated as a non-deductible target in the job deduction / non-deduction designation step;
A method for managing the number of image formations in an image forming apparatus. A method of managing the number of image formations in an image forming apparatus that outputs image information,
A job history acquisition step of acquiring the number of image formations and job history executed by the image forming apparatus via a predetermined communication line;
A job history display control step for controlling the display of the acquired job history;
Job deduction / non-deduction designation means for receiving designation of deduction or non-deduction for jobs in the job history during the maintenance work whose display is controlled in the job history display control step;
A deduction processing step of not adding the number of image formations of the job designated as a non-deduction target in the job deduction / non-deduction designation step to the number of image formations executed by the image forming apparatus;
A method for managing the number of image formations in an image forming apparatus. A computer program for receiving an instruction from a user through a user interface including a display unit and an operation unit, and outputting the image information using a printing apparatus unit that forms image information on a medium according to the instruction. ,
Computer
A counter for counting the number of times of image formation executed by the printing apparatus unit;
A maintenance counter that counts the number of image formations performed by the printing apparatus during maintenance work;
Job history storage means for storing a history of jobs executed by the printing apparatus unit;
Job history display control means for displaying on the display section a history of a job during maintenance work stored in the job history storage means;
Job deduction and non deductible specification control means for receiving a designation of deduction or non deductible via the operating unit against the job of job history is displayed on the display unit,
Maintenance counter control means for not adding the number of image formations of the job designated as non-deductible by the job deduction / non-deduction designation control means to the maintenance counter;
Computer program to function as A computer program for managing the number of image formations in an image forming apparatus that outputs image information,
Computer
Job history acquisition means for acquiring the number of times of image formation executed by the image forming apparatus and the history of the job via a connection means;
Job history display control means for controlling the display of acquired job history,
Job deduction / non-deduction designation means for receiving designation of deduction or non-deduction for jobs in the job history during maintenance work controlled by the job history display control means,
A deduction processing unit that does not add the number of image formations of a job designated as a non-deduction target by the job deduction / non-deduction designation unit to the number of image formations executed by the image forming apparatus;
Computer program to function as

Images