Image processing apparatus, method, and program

Abstract

To reduce a burden on management of a component by a manager as compared with a configuration in which only information indicating a lifetime of the component is displayed on one screen.SOLUTION: The image processing apparatus includes an acquisition unit configured to acquire information on a component of the image processing apparatus, and a control unit configured to display information on a lifetime estimated for the component together with method information corresponding to a method used for the estimation, and the control unit is configured to display any information on the lifetime of the component estimated at each of a plurality of time points.SELECTED DRAWING: Figure 35

Description

[Technical Field]

[0001] The present disclosure relates to an image processing device, a method, and a program. [Background technology]

[0002] Conventionally, there has been known a technique for providing a manager of an image processing device, such as a serviceman who maintains the image processing device, with information indicating the lifespan of a part so that the manager can manage the parts, such as determining whether or not parts need to be replaced. Patent Document 1 discloses that when displaying the lifespan of a part, a prediction formula used to predict the lifespan of the part can be changed, and information on the predicted lifespan is displayed on a single screen. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2020-95149 Summary of the Invention [Problem to be solved by the invention]

[0004] However, with a configuration in which only information indicating the lifespan of a part is displayed on one screen, as in the technology described in Patent Document 1, there are cases in which the administrator cannot determine the processing required for managing the part, such as determining whether or not to replace the part, by simply checking this screen. In such cases, the administrator must personally obtain the information required to determine the processing required for managing the part, which could increase the burden on the administrator in managing the parts. The present disclosure aims to reduce the burden on the administrator in managing parts compared to a configuration in which only information indicating the lifespan of parts is displayed on one screen. [Means for solving the problem]

[0005] An image processing device according to one embodiment of the present disclosure is an image processing device comprising: an acquisition means for acquiring information regarding a component of the image processing device; and a control means for displaying information regarding an estimated lifespan of the component together with method information according to the method used for the estimation, wherein the control means displays information regarding the estimated lifespan of the component at each of a plurality of points in time. [Effects of the Invention]

[0006] According to the present disclosure, the burden on the administrator to manage parts can be reduced compared to a configuration in which only information indicating the lifespan of parts is displayed on one screen. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a diagram showing the configuration of a system including an image processing apparatus according to a first embodiment. [Figure 2] FIG. 2 is a block diagram showing a hardware configuration of the image processing apparatus. [Figure 3] FIG. 2 is a block diagram showing an example of processing functions related to the present embodiment. [Figure 4] FIG. 10 is a diagram illustrating an example of a top screen when an abnormality occurs in the image processing device. [Figure 5] FIG. 10 is a diagram illustrating an example of a top screen when there is no abnormality in the image processing device. [Figure 6] FIG. 10 is a diagram showing a part life screen. [Figure 7] FIG. 10 is a diagram showing a status details screen. [Figure 8] FIG. 10 is a diagram showing a trouble detection screen. [Figure 9] FIG. 10 is a diagram showing a stain details screen. [Figure 10] FIG. 10 is a diagram showing an error screen. [Figure 11] FIG. 10 is a diagram showing an error details screen. [Figure 12] FIG. 10 is a diagram showing a jam screen. [Figure 13] FIG. 10 is a diagram showing a jam details screen. [Figure 14]FIG. 10 is a diagram showing a temperature change screen. [Figure 15] FIG. 10 is a diagram showing a humidity change screen. [Figure 16] FIG. 10 is a diagram showing a print count screen. [Figure 17] FIG. 10 is a diagram showing a cassette history screen. [Figure 18] Shows historical data used to display part life information. [Figure 19] This shows the history data used to display information on trouble detection. [Figure 20] Indicates the history data used to display error information. [Figure 21] 10 shows historical data used to display jam information. [Figure 22] This shows temperature data used to display temperature change information. [Figure 23] This shows humidity data used to display humidity change information. [Figure 24] This indicates the data of the number of printed sheets used to display information on the number of printed sheets. [Figure 25] The cassette operation data used to display the cassette history information is shown. [Figure 26] 10 is a flowchart illustrating an example of a top screen display process including a status monitor startup process. [Figure 27] 27 is a flowchart continuing from FIG. 26. [Figure 28] 28 is a flowchart continuing from FIG. 27. [Figure 29] 18 is a flowchart showing an example of a screen transition process in response to an operation to switch between the screens of FIGS. 4 to 17. [Figure 30] 30 is a flowchart continuing from FIG. 29. [Figure 31] 31 is a flowchart showing the continuation of FIG. 30. [Figure 32] FIG. 10 is a diagram illustrating history data according to the second embodiment. [Figure 33]FIG. 10 is a flowchart showing the flow of a lifespan estimation process. [Figure 34] FIG. 10 is a flowchart showing the flow of a life display process. [Figure 35] FIG. 10 is a diagram showing a parts life screen according to the second embodiment. [Figure 36] FIG. 10 is a diagram showing a part lifespan screen according to a first modified example. [Figure 37] FIG. 10 is a diagram showing a part lifespan screen according to a second modified example. [Figure 38] FIG. 10 is a diagram illustrating a state details screen according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Not all of the features in the embodiments of the present disclosure are essential, and multiple features may be combined as desired. Furthermore, the configurations shown in the following embodiments are merely examples, and the present disclosure is not limited to the illustrated configurations. In the drawings, the same reference symbols are used to designate the same or similar configurations, and redundant explanations will be omitted.

[0009] <System configuration> FIG. 1 is a diagram showing the configuration of an information processing system 1 according to the first embodiment. The information processing system 1 of this embodiment includes an image processing device 103, a server PC (personal computer) 101, and a client PC 102. The image processing device 103, the server PC 101, and the client PC 102 are connected to one another via a network.

[0010] The network is a communication network realized by, for example, any one or a combination of a LAN, a WAN, a telephone line, a dedicated digital line, an ATM, a frame relay line, a cable television line, a wireless line for data broadcasting, etc. Multiple image processing devices 103 may be installed in one local area.

[0011] The image processing device 103 is a multi-function copier (MFP: Multi-Function Peripheral). That is, the image processing device 103 has a print function, a copy function, a facsimile transmission function, a scan function, and the like. The image processing device 103 has not only a function for copying paper documents but also a function for printing print data sent from an external printer driver. The image processing device 103 also has a function (SEND function) for reading paper documents and sending the image data to an external file server or email address. Furthermore, the image processing device 103 also has a function (remote copy function, facsimile transmission function) for sending data to another image processing device and printing it at the destination image processing device.

[0012] The image processing device 103 is connected via Ethernet (registered trademark) (not shown), but this is merely an example. All information processing devices other than the image processing device 103 (server PC 101, client PC 102) may be configured as the same computer. Alternatively, these information processing devices may be implemented in the image processing device 103, so that the information processing system 1 is configured only by the image processing device 103. The information processing device used in this embodiment is not limited to a PC, and may be a terminal device other than a PC or a smartphone. The printing method of the image processing device 103 used in this embodiment may be an electrophotographic method, an inkjet method, or another method.

[0013] <Hardware configuration of image processing device> 2 is a block diagram showing the hardware configuration of the image processing device 103. The image processing device 103 includes a controller unit 200, an operation unit 212, various sensors 255, a scanner 270, and a printer 295.

[0014] The controller unit 200 is connected to a scanner 270 which is an image input device and a printer 295 which is an image output device, and is also connected to Ethernet (registered trademark) or a public line to input and output image information and device information.

[0015] The controller unit 200 has a CPU 201, a RAM 202, a ROM 203, an HDD (hard disk drive) 204, and an operation unit I / F 206. The controller unit 200 also has a network I / F 210, a modem 250, an SRAM 209, an image bus I / F 205, and an RTC (real-time clock) 211. Each of these units is connected to a system bus 207.

[0016] Furthermore, the controller unit 200 has a RIP (raster image processor) 260, a device I / F 220, a scanner image processing unit 280, a printer image processing unit 290, an image rotation unit 230, and an image compression / decompression unit 240. Each of these units is connected to an image bus 208.

[0017] The CPU 201 is a controller that controls the image processing device 103 . The RAM 202 is a system work memory for the CPU 201 to operate, and also serves as an image memory for temporarily storing image data. The ROM 203 is a boot ROM, which stores the boot program of the system. The HDD 204 stores system software, applications, and image data.

[0018] It should be noted that a PLD (Programmable Logic Device) such as an FPGA (Field Programmable Gate Array) may be used instead of the CPU 201. Alternatively, an ASIC (Application Specification Integrated Circuit) or a DSP (Digital Signal Processor) may be used. It is also possible to use a device having a storage medium other than the HDD 204. Examples of storage media other than the HDD 204 include flash memory, an SSD (Solid State Drive), an optical storage medium, and a magneto-optical storage medium.

[0019] The operation unit I / F 206 is an interface unit with an operation unit 212 having a touch panel, and outputs image data to be displayed on the operation unit 212 to the operation unit 212. The operation unit I / F 206 also transmits information input by the user from the operation unit 212 to the CPU 201. The network I / F 210 connects to a network and inputs and outputs information.

[0020] The MODEM 250 connects to the public line and inputs and outputs information. The SRAM 209 is a non-volatile recording medium capable of high speed operation. The RTC 211 continues to count the current time even when the controller unit 200 is not powered on.

[0021] The image bus I / F 205 is a bus bridge that connects the system bus 207 and an image bus 208 that transfers image data at high speed and converts the data structure. The image bus 208 is configured by, for example, a PCI bus or IEEE1394.

[0022] The RIP 260 converts the PDL code into a bitmap image.

[0023] The device I / F 220 connects to various sensors 255 and acquires the status of the image processing device. The device I / F 220 also connects the scanner 270 and printer 295 to the controller unit 200, and performs synchronous / asynchronous conversion of image data.

[0024] The scanner image processing unit 280 corrects, processes, and edits the input image data. The printer image processing unit 290 performs correction (printer correction), resolution conversion, etc. on the print output image data. The image rotation unit 230 rotates the image data. The image compression / decompression unit 240 performs image compression and decompression processing.

[0025] <Software configuration of image processing device> 3 is a block diagram showing an example of processing functions related to this embodiment among the units in the image processing device 103. As explained in the explanation of FIG. 2, the CPU 201 executes part or all of a program stored in the ROM 203 on the RAM 202, thereby realizing the functions of the functional units described below and the processing related to the flowcharts described below.

[0026] The display unit 302 displays the status and operation menu of the image processing device 103 on the operation unit 212. The input unit 303 accepts operation instructions from the user. The history management unit 304 processes information and stores, in a history DB, status information and history (usage history) information of the image processing device 103. The history management unit 304 is an example of a management unit that manages status information and history information of the image processing device. The control unit 301 controls the display unit 302, the input unit 303, and the history management unit 304. The control unit 301, or mainly the CPU 201, is an example of a processing unit that performs processing based on the status information and history information managed by the management unit. The control unit 301, or mainly the CPU 201, can also be considered as an example of a control unit that controls processing.

[0027] <Screen configuration according to the embodiment> Next, the status monitor screen that displays the status and history of the image processing device 103 for service personnel will be described with reference to Figures 4 to 15. The status monitor screen is a screen that is displayed on the operation unit 212 of the image processing device 103, but it is not intended for general users and is therefore a screen that can only be activated by a special operation. Furthermore, each screen data described in Figures 4 to 15 is displayed based on data recorded in the history management unit 304.

[0028] FIG. 4 is a diagram showing an example of a top screen 400 when an abnormality occurs in the image processing device 103. The display unit 302 displays the location and type of the abnormality in the image processing device as an icon (icon image) mapped on a cross-sectional view 401 of the image processing device. The cross-sectional view 401 is an example of a schematic diagram that shows an image processing device. The cross-sectional view 401 also shows the paper transport path, allowing a service technician to know whether the abnormality is likely to affect the use of the main functions of the image processing device, such as scanning and printing. The paper transport path is shown by a dotted line in the cross-sectional view 401, but may be shown by other lines or diagrams.

[0029] The legend 402 for the type of abnormality indicates the type and content of the icon that is mapped and displayed on the cross-sectional view 401. The type indicates whether a deteriorated part needs to be replaced, whether a check is required due to a problem, whether there is a location where jamming is occurring or occurs frequently, etc. The relationship between the abnormality information (content, type, etc.) and the coordinates of the location where the abnormality occurred on the cross-sectional view 401 is predetermined at a 1:1 or multiple:1 ratio.

[0030] The display unit 302 displays information related to abnormalities among the status information and history information of the image processing apparatus on a top screen 400, dividing the information into a plurality of different categories. The plurality of categories include, for example, part life 403, trouble detection 404, error 405, jam 406, and usage status (usage status button) 407. In this embodiment, of these categories, the categories of information related to abnormalities in the status are classified into part life 403, trouble detection 404, error 405, and jam 406. On the other hand, the history is displayed on the top screen 400 as a category called usage status (usage status button) 407. As will be described later, the history will be further divided into a plurality of categories and displayed on a screen other than the top screen 400.

[0031] The areas where part life 403, trouble detection 404, error 405, and jam 406 are displayed are notification areas that display (notify) information about abnormalities occurring in the image processing device 103. These notification areas include buttons for transitioning to detailed screens, and for example, the entire notification area is an operation area that accepts user operations.

[0032] The usage status button 407 is also an operation area that accepts user operations, but does not have a notification area. As will be described later, the usage status button 407 has a function of accepting operations for further dividing the usage status (history information) into multiple categories and displaying them (FIGS. 14 to 17). Note that the usage status may also be configured to have predetermined criteria for determining abnormalities, and information about the abnormalities may be notified on the top screen 400, similar to the other notification areas.

[0033] Display information relating to abnormalities displayed by category, such as part life 403, trouble detection 404, error 405, jam 406, and usage status button 407, is an example of first display information. On the other hand, display information of icons mapped and displayed on cross-sectional view 401 is an example of second display information. In this way, display content based on both the display information of each notification area (and usage status button 407) and the display information of the icons on cross-sectional view 401 (which may also include legend 402) is displayed as a single screen, which is top screen 400.

[0034] Since the content that can be displayed in each notification area is limited by the screen area, abnormalities with the highest priority are displayed from the top, and if there is not enough information to display, the number of remaining abnormalities is displayed as "Other." In other words, the information about the abnormalities is displayed in a mixture of one or more display targets (a predetermined number) and one or more hidden targets (which cannot be displayed on one screen). For hidden targets, only the number of such targets is displayed. The predetermined number of display targets is, for example, two or three, but it may also be one, four or more. Meanwhile, both icons indicating display targets and icons indicating hidden targets are displayed on the cross-sectional view 401.

[0035] Furthermore, the top screen 400 may also display information about abnormalities that are not displayed on the cross-sectional view 401 and whose location within the image processing device 103 cannot be identified. Information about abnormalities whose location within the image processing device 103 cannot be identified includes, for example, system errors. Information about such abnormalities whose location cannot be identified may be notified, for example, as a category of error 405, or may be notified as another category, such as a category not described here.

[0036] Priorities are set for information about abnormalities, and the order of priorities is predetermined. Information about abnormalities includes, for example, abnormalities that require action and abnormalities for which action is recommended. The priority of abnormalities that require action is set higher than the priority of abnormalities for which action is recommended. For example, the priority of part life 403 is set such that "replacement required" is set higher than "replacement recommended," and if the priorities are at the same level, the order follows that of the part life screen, which will be described later.

[0037] Regarding the priority of the trouble detection 404, "check required" is set higher than "check recommended", and if there are the same levels, the order of priority will follow the order of the trouble detection screen described later.

[0038] Errors 405 are displayed in descending order of the date and time of occurrence of currently occurring errors. For errors 405, the order of priority may be set to descending order of the date and time of occurrence as described above, or the order of priority may be set to ascending order of the date and time of occurrence. Alternatively, the order of priority may be set based on other criteria.

[0039] The priority of jam 406 is set higher for "jam occurring" (an abnormality that requires action) than for "frequent jams" (an abnormality for which action is recommended), and if the levels are the same, they are displayed in descending order of the date and time of occurrence, just like the jam screen described below. The priority of information relating to abnormalities in each category may be set in three or more stages.

[0040] In the example of FIG. 4, Parts Life 403 indicates with icons corresponding to legend 402 that drum unit Y needs to be replaced, and that drum unit M and drum unit C are nearing the time to replace them (replacement recommended). In other words, the icon image differs depending on the priority. Parts Life 403 also indicates that there is one part in "Other" that is nearing the end of its life, i.e., its expiration date. Pressing the notification area of ​​Parts Life 403 (or the band-shaped button labeled "Parts Life" at the top of the notification area) transitions to a Parts Life screen, which will be described later.

[0041] When there is information about a plurality of abnormalities corresponding to the same location on the cross-sectional view 401, an icon corresponding to the abnormality with the highest priority is displayed.

[0042] 4, Trouble Detection 404 uses icons to indicate that there are two items that need to be checked and one item that is recommended to be checked. When the notification area of ​​Trouble Detection 404 or the button at the top of the notification area is pressed, the screen transitions to the Trouble Detection screen, which will be described later.

[0043] In the example of Figure 4, Error 405 uses an icon to indicate that there are two errors currently occurring. No icon is displayed for Error 405 because many system errors cannot be determined to be located at a specific position on the cross-sectional view. Pressing the notification area for Error 405 or the button at the top of that notification area will take you to the error screen, which will be described later.

[0044] 4, Jam 406 uses icons to indicate that there is one active jam, one frequent jam, and two other notifications. When the notification area for Jam 406 or the button at the top of the notification area is pressed, the screen transitions to a jam screen, which will be described later.

[0045] A usage status button 407 is a button for transitioning to a usage status screen, which will be described later.

[0046] FIG. 5 is a diagram showing an example of the top screen 400 when there are no abnormalities in the image processing device 103. Because there are no abnormalities in the cross-sectional view 401, no icons are displayed in the legend 402. Each notification area (403 to 406) displays "No Notification," allowing the service technician to recognize at a glance that there are no abnormalities. In this way, the service technician can obtain information from the top screen 400 about whether or not there is an abnormality in the entire image processing device, as well as the location and details of the abnormality, so that the service technician can quickly identify areas that require attention and begin work immediately. The service technician can also consider efficient work procedures, such as treating abnormalities that are close to each other on the cross-sectional view 401 together.

[0047] FIG. 6 shows a parts lifespan screen 500 that is displayed when the parts lifespan button 403 on the top screen 400 is pressed. At the top of the screen, there are displayed buttons for switching between screens: a back button 501, a parts lifespan button 502, a trouble detection button 503, an error button 504, a jam button 505, and a usage status button 506. The back button 501 is a button for returning to the top screen. Pressing the trouble detection button 503, the error button 504, the jam button 505, or the usage status button 506 transitions to the corresponding detailed screen. These buttons 501 to 506 are also displayed on each detailed screen (described later), allowing the service technician to easily move between the detailed screens. This makes it easier to deduce the cause of an abnormality by comparing the information displayed on each screen.

[0048] The part life screen 500 also displays the cross section 401 and legend 402, but the icons displayed are limited to parts.

[0049] Parts list 507 displays a list showing the status of replacement parts. Each column of parts list 507 displays the "part name," "status," and "number of sheets used" of paper that has been passed (used) after the part was replaced. Just to be clear, the status of parts is not a concept that completely matches the "status information" that is managed and displayed by the above categories, but rather refers to the information on the status of parts within the overall status information.

[0050] In the parts list 507, the "status" is displayed as a four-level meter icon according to the status value of the part. For example, level "0" indicates an indefinite state immediately after part replacement, level "1" indicates a status value of 0-79%, level "2" indicates a status value of 80-99%, and level "3" indicates a status value of 100% or more, and each level meter icon is displayed. The current status value is also displayed numerically to the right of the level meter. This status value increases as the part deteriorates, and is preset so that the value at which replacement is necessary is 100%. Parameters used to calculate the status value include, for example, the number of parts used after replacement, and the current value and resistance value of each part.

[0051] When the status value level is "2," a replacement recommended icon is displayed on the left side of the list, indicating that the corresponding part is nearing its expiration date. In the example in Figure 6, "Drum Unit M," "Drum Unit C," and "Cassette Roller 1" are in a state where replacement is recommended. When the status value level is "3," a replacement required icon is displayed on the left side of the list, indicating that the corresponding part has reached its expiration date. In the example in Figure 6, "Drum Unit Y" is in a state where replacement is required.

[0052] When a service technician replaces a part, the replacement of the part is detected and the status value temporarily returns to the no-data level "0." Therefore, the icons indicating that the part needs to be replaced or is recommended for the replaced part are hidden from the cross-sectional view 401 and parts list 507. Unlike the notification area for part life 403 on the top screen 400, parts list 507 displays all parts managed by the service technician, regardless of whether there is an abnormality. Therefore, the status values ​​of parts that do not yet require replacement can also be checked. The parts list 507 can be scrolled up and down to display the status of all parts.

[0053] The status details button 508 is a button for transitioning to a screen that displays a graph of the transition of the status value of the part selected in the parts list 507.

[0054] FIG. 7 shows a status details screen 510 that is displayed when the status details button 508 is pressed. A status transition graph 511 shows the daily transition of the status value of the selected part. A reference line is displayed on the graph at 100%, the point at which part replacement is required. A display period 512 is a pull-down menu that switches the graph display period between 30 days and 180 days. The display period 512 is not limited to 30 days or 180 days. A close button 513 is a button that closes the status details screen 510 and returns to the part lifespan screen 500.

[0055] The example in FIG. 7 shows a condition transition graph 511 for "drum unit Y" on the part lifespan screen 500, allowing the user to view the daily transitions until the condition value exceeds 100%. This allows the service technician to estimate whether the deterioration has progressed as expected, or whether the deterioration of the part has progressed rapidly due to a defective part or environmental change. The example in FIG. 7 shows an example in which the condition value has exceeded the expiration date of the part, but for parts that have not yet reached their expiration date, the service technician can predict from the slope of the graph how many days remain until the part's expiration date. This allows the service technician to determine whether a replacement part should be brought during the next visit and prepare the replacement part.

[0056] 8 shows a trouble detection screen 600 that is displayed when trouble detection 404 on the top screen 400 is pressed, or when trouble detection button 503 on each detailed screen is pressed. Buttons 501 to 506 arranged at the top of the screen have the same functions as buttons 501 to 506 shown in FIG.

[0057] The trouble detection screen 600 also displays the cross section 401 and the legend 402, but the icons displayed are limited to those indicating whether or not a trouble check is required.

[0058] Trouble list 601 displays a list of problems that service personnel often need to deal with and their details. "Dirt on ADF optical unit" and "Dirt on reader optical unit" display information on whether cleaning of the optical unit is required. ADF is an abbreviation for Automatic Document Feeder. For example, the degree of dirt on a mirror is detected from the value of the mirror's reflected light obtained by an optical sensor. As with the part life status value and status level described above, the dirt level [%], with 100% being the standard value for when cleaning is required, and the dirt level, which is a level meter icon with four levels according to the dirt level, are displayed. Information on whether or not action is required is displayed based on this dirt level or dirt level.

[0059] Specifically, for example, if the level of dirt is indefinite, a level "0" icon is displayed. If the level of dirt is 0-79%, a level "1" icon is displayed. If the level of dirt is 80-99%, a level "2" icon is displayed. If the level of dirt is 100% or more, a level "3" icon is displayed. If the level of dirt is level "2", a check recommended icon indicating that cleaning is recommended is displayed at the left end of the list. If the level of dirt is level "3", a check required icon indicating that cleaning is required is displayed at the left end of the list.

[0060] Additionally, messages regarding the target / content of the trouble list 601 change depending on the level. For example, level "0" displays "No data," level "1" displays "Good," level "2" displays "Dirty," and level "3" displays "Severely Dirty." Regarding dirt on the optical unit, by selecting one item in the trouble list 601 and pressing the dirt details button 602, a graph showing the progress of the dirt level (explained later in FIG. 9) can be viewed.

[0061] In the trouble list 601, whether or not there is an abnormality in each cassette is displayed along with the details of the abnormality. It is determined that an abnormality has occurred in the cassette mainly when a misalignment of the paper regulation plate (guide) inside the cassette is detected. If there is an abnormality in the cassette, the message "Check required" is displayed in the list, and if there is no abnormality, the message "None" is displayed.

[0062] The treated button 603 can be pressed when the optical unit or cassette "needs checking" or "check recommended." After cleaning the optical unit, if the service technician selects the target optical unit in the trouble list 601 and presses the treated button 603, the contamination level returns to "0." As a result, the "check required" or "check recommended" icon disappears from the cross-sectional view 401 and the trouble list 601. Furthermore, if the service technician checks the cassette, selects the target cassette in the trouble list 601 and presses the treated button 603, the display returns to showing no abnormalities. As a result, the "check required" icon disappears from the cross-sectional view 401 and the trouble list 601.

[0063] 9 is a diagram showing a dirt details screen 610 that is displayed when the dirt details button 602 for the optical unit is pressed. A dirt transition graph 611 shows the daily change in the dirt level of the optical unit selected in the trouble list 601. A reference line is displayed on the graph at 100%, the point at which cleaning becomes necessary. A display period 612 is a pull-down menu that switches the graph display period between 30 days and 180 days. A close button 613 is a button that closes the dirt details screen 610 and returns to the trouble detection screen 600.

[0064] The example in Figure 9 shows a dirt transition graph 611 for "Reader optical unit dirt" on the trouble detection screen 600, which shows the daily progress until the dirt level reaches 81%, indicating that a check is recommended. From the slope of this graph, a service technician can predict how many days it will take to reach a level where cleaning will be necessary. This allows the service technician to determine whether they should bring cleaning tools with them on their next visit and make preparations accordingly.

[0065] 10 is a diagram showing an error screen 700 that is displayed when error 405 on top screen 400 is pressed or when error button 504 on each detail screen is pressed. Buttons 501 to 506 arranged at the top of the screen have the same functions as buttons 501 to 506 shown in FIGS. 6 and 8.

[0066] The error list 701 displays a list of the history of errors that have occurred in the image processing device 103. For each error, the error list 701 displays the date and time the error occurred, the time it was recovered from, and the error code and its title as details. Errors on the first and second lines that do not display the recovery time indicate that the error is still occurring. For example, by selecting one error in the error list 701 and pressing the error details button 702, detailed information about the selected error can be confirmed.

[0067] FIG. 11 shows an error details screen 710 that is displayed when the error details button 702 is pressed. The error code 711 indicates the error code that identifies the selected error. The error information 712 displays the title, description, and solution of the error. The page forward button 713 is a button for switching pages when there are multiple pages of error information. The close button 714 is a button for closing the error details screen 710 and returning to the error screen 700. The service technician can check the currently occurring error and its contents from this screen.

[0068] 12 is a diagram showing a jam screen 800 that is displayed when jam 406 on the top screen 400 is pressed or when jam button 505 on each detail screen is pressed. Buttons 501 to 506 arranged at the top of the screen have the same functions as buttons 501 to 506 shown in FIGS. 6, 8, and 10.

[0069] The jam screen 800 also displays the cross section 401 and the legend 402, but the icons displayed are limited to those indicating jams that are currently occurring or frequent jams.

[0070] The jam list 801 displays a list of jam histories. For each jam, the jam list 801 displays the jam occurrence date, jam occurrence time, and recovery time, along with the jam code, jam type, sensor number, and the accumulated number of occurrences of the same jam code. A jam in the first row, which does not display a recovery time, indicates that the jam is still occurring, and an icon indicating that a jam is occurring is displayed at the left end of the jam list 801. A jam with a cumulative number of occurrences exceeding a predetermined number, as in the jam histories in the second and fourth rows, is determined to be a frequent jam, and a frequent jam icon is displayed at the left end of the list. In the example of FIG. 12, a jam that has occurred 10 or more times is determined to be a frequent jam. If there are multiple histories with the same jam code, only the most recent one is displayed on the list. This makes it easier to understand the type of jam that has occurred. By selecting one jam from the jam list 801 and pressing the jam details button 802, detailed information about the selected jam can be viewed.

[0071] The reset button 803 is a button for clearing the jam history that is being displayed. A service technician uses the reset button 803 when he or she has finished checking for an ongoing or frequent jam and wishes to delete the notification. When the reset button 803 is pressed, the date and time in the reset date and time 804 is updated, and the jam list 801 now displays the jam history from the reset date and time 804 onwards.

[0072] 13 is a diagram showing a jam details screen 810 that is displayed when the jam details button 802 is pressed. Jam details 811 displays the jam code and type of jam selected in the jam list 801. Sensor number 812 displays the jam code and the sensor number associated with the location where the jam occurred.

[0073] Jam details list 813 displays the history of jams with the same jam content 811 (i.e., jam code and jam type) in chronological descending order. Jam details list 813 displays the cumulative number, occurrence date, occurrence time, recovery time, paper feed position, paper feed counter, and paper feed size. The paper feed position is the position of the paper when the jam occurred. The number shown in the "paper feed counter" is the number of sheets fed from the paper feed position when the jam occurred. The paper feed size is the size of the paper supplied. In jam list 801 in FIG. 12, the same jam code is aggregated and displayed as the most recent jam, making it easy to see the variations in jams that have occurred. However, jam details list 813 in FIG. 13 makes it easier to see the frequency of occurrence of the same jam. Jam details list 813 can be scrolled up and down when there are a large number of items.

[0074] The close button 814 is a button for closing the jam details screen 810 and returning to the jam screen 800. Since the service technician can know not only the current jam but also the locations where jams have frequently occurred in the past and their frequency, the technician can consider cleaning or replacing surrounding parts in the locations where jams have occurred or occur frequently.

[0075] 14 to 17 each show a usage status screen 900 that is displayed when the usage status button 407 on the top screen 400 or the usage status button 506 on each detailed screen is pressed. The right side of the usage status screen 900 displays a temperature button 901, a humidity button 902, a number of prints button 903, and a cassette history button 904, which transition to each usage status screen. These buttons 901 to 904 are displayed on each usage status screen 900 shown in FIGS. 14 to 17, allowing the service technician to easily navigate between the various usage status screens 900. Furthermore, by using the back button 501 to the usage status button 506, the service technician can easily navigate between the part life screen 500, the trouble detection screen 600, the error screen 700, the jam screen 800, and the usage status screen 900. This allows the service technician to easily compare the abnormality information with the usage status and easily deduce the cause of the abnormality.

[0076] 14 is a diagram showing a temperature change screen that is displayed when a temperature button 901 on the usage status screen 900 is pressed. A temperature change graph 905, with the vertical axis representing temperature (°C) and the horizontal axis representing time, shows a one-day chart of temperatures inside (inside) and outside (outside) the image processing device at 10-minute intervals. A date change button 906 is a button for changing the date of the displayed graph. By pressing the date change button 906 and selecting a date, data from up to one month ago can be displayed.

[0077] The temperature change graph 905 displays the upper and lower limits of the standard temperature range as dotted lines, and if the temperature is outside the standard range, it can be determined that the environment needs to be reviewed. Furthermore, the service technician can compare the period on the temperature change screen in Figure 14 that is the same as the period during which a jam occurred on the error screen 700 in Figure 10 or the jam screen 800 in Figure 12, for example, to check whether the temperature change is the cause of the error or jam.

[0078] 15 is a diagram showing a humidity change screen that is displayed when the humidity button 902 on the usage status screen 900 is pressed. The humidity change graph 907 shows humidity (%) on the vertical axis and time on the horizontal axis, and shows the humidity inside and outside the aircraft for one day at 10-minute intervals. The date change button 908 is a button that changes the date of the displayed graph, and can display data from up to one month ago.

[0079] The humidity change graph 907 displays the upper and lower limits of the standard humidity range as dotted lines, and if the humidity is outside the standard range, it can be determined that the environment needs to be reviewed. Also, the service technician can compare the period in which a jam occurred on the jam screen 800 in Fig. 12 with the same period on the humidity change screen in Fig. 15 to confirm whether humidity changes are the cause of the jam.

[0080] 16 is a diagram showing the print count screen that is displayed when the print count button 903 on the usage status screen 900 is pressed. A print count graph 909 shows the number of prints (sheets) on the vertical axis and time on the horizontal axis.

[0081] The display period switch button 910 is a button for changing the display period of the graph to one month or one day. The date switch button 911 is a button for switching the date on which the graph is displayed. When "Month" is selected with the display period switch button 910, one month's worth of data is displayed in one-day intervals, and the selection made with the date switch button 911 switches between displaying monthly data. In this case, the date switch button 911 displays the year and month, and the horizontal axis of the print count graph 909 is displayed in days (rather than "time" as shown in the example of FIG. 16).

[0082] On the other hand, when "day" is selected with the display period switch button 910, one day's worth of data is displayed at one-hour intervals, as shown in the example of Fig. 16, and the data for each day can be switched and displayed by selecting with the date switch button. In this case, the date switch button 908 displays the year, month, and day, and the horizontal axis of the print count graph 909 is displayed in time (hour) units.

[0083] For example, if it is estimated from the parts lifespan screen 500 in Fig. 6 that the expiration date of a part will be reached earlier than expected, the following inference can be made: That is, if a service technician confirms from the print count graph 909 in Fig. 16 that a large amount of printing was done just before the expiration date, the technician can infer that the large amount of printing may be the cause of the earlier expiration date of the part.

[0084] 17 is a diagram showing a cassette history screen that is displayed when the cassette history button 904 on the usage status screen 900 is pressed. A cassette history list 912 displays the operation history for a cassette in chronological order. A cassette switch button 913 is a button for selecting the target cassette displayed in the cassette history list 912. For example, if a jam or error occurs, a service technician can make the following observations by checking the cassette history in the cassette history list 912. That is, the service technician can determine whether the jam or error was caused by an operation or setting mistake by the user using this image processing apparatus, or whether the malfunction was caused by some other factor other than the user's operation or setting mistake.

[0085] <History data configuration> Next, we will explain the data recorded in the history management unit 304, which manages the data displayed on the status monitor screen mentioned above. The history management unit 304 organizes values ​​and settings acquired from the various sensors 255, scanner 270, and / or printer 295 via the device I / F 220 in Fig. 2 into necessary information and saves it in the HDD 204 or RAM 202. Note that "history data" here refers to the history data of both "status information (parts lifespan, trouble detection, errors, jams)" and "history information (usage status)."

[0086] 18 shows history data used to display information about the lifespan of a part. This history data includes a number (No.) 1001, a part name 1002, and history data 1003 of the part's condition. Number 1001 indicates the order in which the parts are arranged in this history data. The status history data 1003 includes, for example, the date the data was acquired, the status level of the part, the status value [%], and the number of sheets used. The status history data 1003 is saved for each day. The status level, status value, and number of sheets used are as described above in the explanation of parts list 507 in FIG.

[0087] In the condition history data 1003, parts with a condition level of "3" are displayed as parts requiring replacement in the cross-sectional view 401 and part lifespan 403 of FIG. 4. Parts with a condition level of "2" are displayed as parts recommended for replacement in the cross-sectional view 401 and part lifespan 403 of FIG. 4. All parts listed in the part name 1002 and their status are displayed in the parts list 507 of FIG. 6 in the order of their numbers 1001. The condition history data 1003 is also used to display the condition transition graph 511 of FIG. 7. For example, because the display period can be 30 days or 180 days, at least 180 days' worth of data is retained. When a part replacement by a service technician is detected, the condition level of the replaced part becomes "0." A condition level of "0" indicates that the value is indefinite after the part replacement. Furthermore, there is no data for the status value [%] and number of sheets used. As described above, the part lifespan history data of FIG. 18 is used to display the part lifespan on each screen.

[0088] 19 shows history data used to display information on trouble detection. This history data includes a number (No.) 1101, a target 1102, and trouble history data 1103. The number 1101 indicates the order of the troubles in this history data, and the object 1102 indicates the name or content of the trouble. The trouble history data 1103 includes the date when the data was acquired, the dirt level, the dirt degree [%], and the detected abnormality of the cassette. The contamination level, contamination degree [%], and cassette abnormality detection are as described above in the explanation of the trouble list 601 in FIG.

[0089] In the case of optical units, the data includes the date the data was acquired, the contamination level, and the contamination degree [%], and this data is saved by day. An optical unit with a contamination level of "3" is displayed in the cross section 401 and trouble detection 404 of FIG. 4 as a problem that requires checking. An optical unit with a contamination level of "2" is displayed in the cross section 401 and trouble detection 404 of FIG. 4 as a problem that is recommended to be checked. In addition, trouble history data 1103 related to optical units is used to display the contamination transition graph 611 of FIG. 9. Since the display period can be 30 days or 180 days, at least 180 days' worth of data is saved.

[0090] In the case of cassettes, the history data 1103 for each trouble includes the date the data was acquired and whether or not an abnormality was detected, and this data is saved by day. Cassettes for which an abnormality has been detected are displayed in the cross section 401 and trouble detection 404 in Figure 4 as troubles that require checking. The troubles and their status (degree and level of contamination) for all objects 1102 are displayed in the trouble list 601 in Figure 9 in the order of number 1101.

[0091] When a service technician selects one of the targets in the trouble list 601 in FIG. 8 and presses the "Resolved" button 603, the value relating to the status of the trouble for that target is updated to the following value. That is, if the trouble for that target is dirt on the optical unit, the dirt level value becomes level "0," which is in an undefined state. In that case, there is no dirt level [%] data. If the trouble for that target is with the cassette, the abnormality detection is updated to "none." As described above, the trouble detection history data in FIG. 19 is used to display trouble detection on each screen.

[0092] 20 shows history data used to display error information. This history data includes an error code 1201, an error title 1202, an occurrence date 1203, an occurrence time 1204, and a recovery time 1205. The error code 1201 is a code for identifying an error. The occurrence date 1203 and the occurrence time 1204 are the date and time when the error occurred, respectively. The recovery time 1205 is the time when the error was resolved. An error for which the recovery time 1205 is not recorded is displayed as an ongoing error in the error 405 in Figure 4.

[0093] The history data in Fig. 20 is displayed in the error list 701 in Fig. 10 in descending order of occurrence date 1203 and occurrence time 1204. Although not shown in Fig. 20, content corresponding to each error code in error code 1201 is stored in HDD 204 and is displayed on the error details screen in Fig. 11. As described above, the error history data in Fig. 20 is used to display errors on each screen.

[0094] 21 shows history data used to display jam information. This history data includes a jam code 1301, a type 1302, a sensor 1303, an occurrence date 1304, an occurrence time 1305, a recovery time 1306, a cumulative number 1307, a paper feed position 1308, a paper feed counter 1309, and a paper feed size 1310.

[0095] The jam code 1301 is a code for identifying a jam. The type 1302 is the type of jam corresponding to the jam code. There are various types of type 1302, such as DELAY (delay) when the sensor does not detect the paper even after the expected time has passed, STNRY (stagnation) when the sensor continues to detect the paper for the expected time or longer, and DOUBLE (double feed) when the ADF sensor detects double feed of paper. The sensor 1303 is the number of the sensor that detected the jam. The occurrence date 1304 and occurrence time 1305 are the date and time when the jam occurred, respectively. The recovery time 1306 is the time when the jam was cleared. A jam for which the recovery time 1306 is not recorded is displayed as an ongoing jam in the cross section 401 and jam 406 in FIG. 4.

[0096] The cumulative number 1307 is the number of jams that have occurred with the same jam code. The number of jams that have occurred since the reset date and time 804 in Fig. 12 is counted up as the cumulative number. For example, if the cumulative number reaches a predetermined number (here, 10 or more), it is determined to be a multiple jam, and is displayed in the cross section 401 and jam 406 in Fig. 4. A paper feed position 1308 is the position where the jammed paper was fed. A paper feed counter 1309 indicates the number of sheets of paper fed from the paper feed position.

[0097] The history data in FIG. 21 is displayed in the jam list 801 in FIG. 12 in descending order of occurrence date 1304 and occurrence time 1305. In this case, as described above, only the most recent jam with the same jam code is displayed. The history with the same jam code is displayed on the jam details screen in FIG. 13. Note that when the reset button 803 is pressed in FIG. 13, the jam history before the date and time of pressing is deleted. As described above, the jam history data in FIG. 21 is used to display jams on each screen.

[0098] Each piece of history data in FIGS. 20 and 21 may also have a serial number such as the numbers 1001 and 1101 of the history data shown in FIGS.

[0099] 22 to 25 show data used to display the usage status information (temperature, humidity, number of printed sheets, and cassette history), which is the history information.

[0100] 22 shows temperature data used to display information on temperature changes. This data includes a date 1401, a time 1402, an inside 1403, and an outside 1404. Date 1401 indicates the date when the temperature data was acquired, and for example, one month's worth of data is saved. Time 1402 indicates the time when the temperature data was acquired, and for example, data is saved at 10-minute intervals. Temperature data acquired by a thermometer installed inside the machine (not shown) is stored in the inside 1403. Temperature data acquired by a thermometer installed outside the machine (not shown) is stored in the outside 1404. The above data shown in FIG. 22 is used to display the temperature change graph 905 in FIG.

[0101] 23 shows humidity data used to display information on humidity changes. This data includes a date 1411, a time 1412, an inside 1413, and an outside 1414. Date 1411 indicates the date when humidity data was acquired, and for example, one month's worth of data is saved. Time 1412 indicates the time when humidity data was acquired, and for example, data is saved at 10-minute intervals. Temperature data acquired by a hygrometer installed inside the machine (not shown) is stored in the inside 1413. Temperature data acquired by a hygrometer installed outside the machine (not shown) is stored in the outside 1414. The above data shown in FIG. 23 is used to display the humidity change graph 907 in FIG.

[0102] 24 shows data on the number of printed sheets used to display information on the number of printed sheets. This data includes a date 1421, a time 1422, and a number of printed sheets 1423. The date 1421 indicates the date when the print count data was acquired, and the time 1422 indicates the time when the print count data was acquired. The number of printed sheets 1423 indicates the number of printed sheets printed by the image processing device 103 . For example, the data of the date 1421, the time 1422, and the number of printed sheets 1423 for one month are stored at one-hour intervals. The above data shown in FIG. 24 is used to display the print count graph 909 in FIG.

[0103] 25 shows cassette operation data used to display cassette history information. This data is saved when a user closes a cassette in the image processing device 103 or changes the media (i.e., paper). This data includes a date 1431, a time 1432, a cassette 1433, and a cassette operation 1434. The date 1431 indicates the date when the cassette operation was performed. The time 1432 indicates the time when the cassette operation was performed. The cassette 1433 indicates information about the location of the operated cassette. In the cassette operation 1434, when an operation to close the cassette is performed, information "cassette closed" is saved. Also, when an operation to change the media is performed, "media change" and the changed paper size and paper type are saved. A predetermined number of data items (for example, up to 300 items) are saved as cassette history information. The above data shown in FIG. 25 is used to display the cassette history list 912 in FIG.

[0104] The cassette operation data is not limited to cassette operation, and manual feed operation data may also be saved.

[0105] <Processing performed by the image processing device> 26 to 28 are flowcharts showing an example of the display process of the top screen (FIG. 4) including the startup process of the status monitor. A program (for example, firmware) that realizes this process is stored in the HDD 204 of the image processing device 103, called into the RAM 202, and executed by the CPU 201.

[0106] This process is started when the CPU 201 receives an input of a special command for starting the status monitor via the operation unit 212 from a service person.

[0107] In S1501, the CPU 201 refers to the device configuration information (not shown) of the image processing apparatus stored in the RAM 202.

[0108] In S1502, the CPU 1501 determines the cross-sectional view to be displayed on each screen. For example, the cross-sectional view to be displayed changes depending on whether a scanner, a paper feed option, or a paper output option is installed. When a common program is used among multiple image processing apparatuses, the CPU 1501 may switch to a cross-sectional view that is suitable for the model according to the model information. This is because the positions of the paper transport path, parts, and jam sensors may differ depending on the model of the image processing apparatus.

[0109] In S1503, the CPU 201 refers to the part life history data shown in FIG.

[0110] In S1504, the CPU 201 determines whether or not there are any parts whose status level is "2" or higher as a result of the reference in S1503.

[0111] If the determination result in S1504 is NO, in S1505, the CPU 201 determines that there is no part life icon to be displayed in the cross-sectional view 401 in Fig. 4 and that "No notification" will be displayed in the notification area of ​​the part life 403. If the determination result is YES, in S1506, the CPU 201 obtains information on parts that require replacement and have a status level of "3" from the part life history data.

[0112] In S1507, the CPU 201 acquires information on parts recommended for replacement with a condition level of "2" from the part life history data. The order of S1506 and S1507 may be reversed.

[0113] In S1508, the CPU 201 displays the icons indicating the need for replacement and / or recommended replacement of the parts requiring notification, acquired in S1506 and S1507, at the corresponding coordinates on the cross-sectional view 401.

[0114] In S1509, the CPU 201 displays the parts requiring notification, acquired in S1506 and S1507, in descending order of priority. The priority is set such that parts requiring replacement (status level "3") are higher than parts recommended for replacement (status level "2"). In the case of parts with the same level, they are displayed in the order of number 1001 in FIG. 18.

[0115] In S1510, CPU 201 determines whether the number of parts to be notified is greater than the number of parts (e.g., three) that can be displayed in the notification area of ​​part life 403. If the determination result is NO, the process proceeds to S1512. If the determination result is YES, in S1511, CPU 201 displays the notifications that cannot be displayed with the characters "Other:" and the number of notifications.

[0116] In S1512, the CPU 201 refers to the trouble detection history data shown in FIG.

[0117] In S1513, the CPU 201 determines, as a result of the reference in S1512, whether or not there is a problem with the optical unit where the contamination level is "2" or higher and / or there is a cassette abnormality.

[0118] If the determination result is NO, in S1514, the CPU 201 determines that there is no trouble detection icon to be displayed in the cross-sectional view 401 of Fig. 4 and that "No notification" will be displayed in the notification area of ​​the trouble detection 404. If the determination result is YES, in S1515, the CPU 201 obtains information on optical units with a contamination level of "3" and / or cassettes with abnormalities from the trouble detection history data.

[0119] In S1516, the CPU 201 acquires information about optical units whose status level is “2” from the trouble detection history data. The order of S1515 and S1516 may be reversed.

[0120] In S1517, the CPU 201 displays the icons indicating that check is required and / or that check is recommended for the trouble requiring notification, which were acquired in S1515 and S1516, at the corresponding coordinates on the cross-sectional view 401.

[0121] In S1518, the CPU 201 displays the troubles that require notification, acquired in S1515 and S1516, in descending order of priority. The priority is set such that check required (soil level "3") is higher than check recommended (soil level "2"), and if the levels are the same, the troubles are displayed in the order of number 1101 in FIG. 19.

[0122] In S1519, CPU 201 determines whether the number of troubles to be notified is greater than the number of troubles (e.g., three) that can be displayed in the notification area of ​​trouble detection 404. If the determination result is NO, the process proceeds to S1521. If the determination result is YES, in S1520, CPU 201 displays the notifications that cannot be displayed with the text "Other:" and the number of notifications.

[0123] In S1521, the CPU 201 refers to the error history data stored in the HDD 204 and shown in FIG.

[0124] In S1522, the CPU 201 determines, as a result of the reference in S1521, whether or not there is a currently occurring error for which the recovery time 1205 in FIG. 20 is not registered.

[0125] If the determination result is NO, in S1523, it is determined to display "No notification" in the notification area of ​​the error 405. If the determination result is YES, in S1524, the CPU 201 obtains information about the currently occurring error for which the recovery time 1205 is not registered from the error history data.

[0126] In step S1525, the CPU 201 displays the errors that require notification, acquired in step S1524, in descending order of acquisition.

[0127] In S1526, CPU 201 determines whether the number of errors to be notified is greater than the number of errors (for example, two) that can be displayed in the notification area of ​​error 405. If the determination result is NO, the process proceeds to S1528. If the determination result is YES, in S1527, CPU 201 displays the notifications that cannot be displayed with the text "Other:" and the number of notifications.

[0128] In S1528, the CPU 201 refers to the jam history data stored in the HDD 204 and shown in FIG.

[0129] In S1529, the CPU 201 determines, as a result of the reference in S1528, whether there is a currently occurring jam for which the jam recovery time 1306 in FIG. 21 is not registered, or whether there is a frequent jam with the cumulative number 1307 of 10 or more.

[0130] If the determination result is NO, in S1530, the CPU 201 determines that there is no jam icon to be displayed in the cross-sectional view 401 of Fig. 4 and that "No notification" is to be displayed in the notification area of ​​the jam 406. If the determination result is YES, in S1531, the CPU 201 obtains information about an occurring jam for which the recovery time 1306 is not registered from the jam history data.

[0131] In S1532, the CPU 201 acquires information on frequent jams where the cumulative number 1307 is 10 or more from the jam history data. The order of S1531 and S1532 may be reversed. Note that if multiple pieces of data with the same jam code are registered in the jam history data in Fig. 21, the latest piece of information is acquired.

[0132] In step S1533, the CPU 201 displays the icons indicating that a jam is occurring and / or that there are many jams that require notification, which were acquired in steps S1531 and S1532, at the corresponding coordinates on the cross-sectional view 401.

[0133] In S1534, the CPU 201 displays the jams that require notification, acquired in S1531 and S1532, in descending order of priority. Current jams are set higher in priority than frequent jams. If the priority levels are the same, the information is displayed in descending order of acquisition, for example. Furthermore, if there is a jam that is both current and frequent, the information about the current jam is displayed first.

[0134] In S1535, the CPU 201 determines whether the number of jams to be notified is greater than the number of jams (for example, two) that can be displayed in the notification area of ​​the jam 406. If the determination result is NO, the process proceeds to S1537. If the determination result is YES, in S1536, the CPU 201 displays the notifications that cannot be displayed with the characters "Other:" and the number of notifications.

[0135] In S1537, CPU 201 displays the display content determined in S1501 to S1536 on the screen of operation unit 212. That is, top screen 400 of the status monitor in FIG. 4 is displayed.

[0136] 26 to 28, the cross-sectional view 401 and the notification area (403 to 406) can be used to display the abnormality of the image processing device 103 and its location that the on-site service technician needs to check urgently. This allows the service technician to see the entire picture of the abnormality of the image processing device and its location on a single screen, the top screen 400. As a result, the efficiency of the work of checking the location of abnormalities by the service technician, who is required to respond quickly on-site, is improved. Furthermore, the service technician can identify an area where two or more abnormalities are concentrated from the cross-sectional view 401 and consider efficient subsequent work procedures, such as working on the concentrated abnormalities together.

[0137] As described above, according to this embodiment, the information necessary for maintenance work on the image processing device 103, particularly information regarding abnormalities occurring in the device and the location of the abnormalities, can be efficiently displayed within a limited screen area, thereby improving the work efficiency of service personnel.

[0138] Furthermore, the service technician can also estimate the correlation between the occurrence of multiple abnormalities from the relative positions of the abnormalities in the cross-sectional view 401. For example, if a notification that cassette roller 1 needs to be replaced and a notification that there are frequent jams in the vicinity are received at the same time, in a similar time period, or in a similar time period, it can be determined that there is a high possibility that the frequent jams will be resolved by replacing cassette roller 1.

[0139] Next, an example of screen transition processing in response to an operation in which a service technician operates the operation unit 212 to switch between the screens shown in Figures 4 to 17 after the top screen 400 of the status monitor is displayed will be described. Figures 29 to 31 are flowcharts showing this processing. A program (for example, firmware) that realizes this processing is stored in the HDD 204 of the image processing device 103, called into the RAM 202, and executed by the CPU 201.

[0140] This process is started when the CPU 201 receives an input from a service technician via the operation unit 212 while the screens of FIGS. 4 to 17 are displayed on the operation unit 212.

[0141] When the CPU 201 detects that a button on the screen has been pressed, in S1601 it determines which button shown in FIGS. 4 to 17 has been pressed.

[0142] First, we will explain the case where the pressed button is the notification area of ​​part lifespan 403 or part lifespan button 502. If the button pressed in S1601 is the notification area of ​​part lifespan 403 or part lifespan button 502, the determination result in S1601 is "part lifespan," and the process proceeds to S1602.

[0143] In S1602, the CPU 201 refers to the part life history data shown in FIG.

[0144] In S1603, the CPU 201 displays the parts life screen 500 of FIG. 6 on the operation unit 212 in accordance with the parts life history data referenced in S1602. At this time, the cross-sectional view 401 displays an icon corresponding to the abnormality related to the parts life determined in S1508 of FIG. 26. Other icons (icons corresponding to abnormalities related to trouble detection or jams) are not displayed. In addition, the parts list 507 displays the status of all parts listed in the parts life history data shown in FIG. 18.

[0145] After the parts lifespan screen 500 is displayed in S1603, when the CPU 201 detects that a button on the screen has been pressed, it determines in S1604 which button on the parts lifespan screen 500 has been pressed.

[0146] If the button pressed in S1604 is the detailed status button 508, the determination result in S1604 is "detailed status", and the process proceeds to S1605.

[0147] In S1605, the CPU 201 refers to the history data 1003 (that is, data used to create a graph) of the state of the part selected in the parts list 507 from the history data of the part lifespan shown in FIG.

[0148] In S1606, the CPU 201 creates a graph of the status value [%] according to the time series of dates in the status history data 1003 referenced in S1605, and displays the status details screen 510 in Fig. 7. At this time, data for the display period specified in the display period 512 is displayed as a status transition graph 511. After the status details screen 510 is displayed, the close button 513 is pressed to return to the part life screen 500 (not shown). Thereafter, the process returns to waiting for a determination in S1601.

[0149] If the button pressed in S1604 is other than the detailed status button 508, the determination result in S1604 is "other", and the process proceeds to S1601 to determine which of the buttons 501 to 506 was pressed.

[0150] Next, a description will be given of the case where the pressed button is in the notification area of ​​trouble detection 404 or the trouble detection button 503. If the pressed button in S1601 is in the notification area of ​​trouble detection 404 or the trouble detection button 503, the determination result in S1601 is "trouble detected," and the process proceeds to S1607.

[0151] In S1607, the CPU 201 refers to the trouble detection history data shown in FIG.

[0152] In S1608, the CPU 201 displays the trouble detection screen 600 of Fig. 8 on the operation unit 212 in accordance with the trouble detection history data referenced in S1607. At this time, an icon corresponding to the abnormality related to the trouble detection determined in S1517 of Fig. 27 is displayed in the cross-sectional view 401. Other icons (icons corresponding to abnormalities related to part life or jams) are not displayed. In addition, the trouble list 601 displays the status of all troubles listed in the trouble detection history data shown in Fig. 19.

[0153] After the trouble detection screen 600 is displayed in S1608, when the CPU 201 detects that a button on the screen has been pressed, it determines in S1609 which button on the trouble detection screen 600 has been pressed.

[0154] If the button pressed in S1609 is the dirt details button 602, the determination result in S1609 is "dirt details," and the process proceeds to S1610. In S1610, the CPU 201 refers to the trouble history data 1103 (i.e., data used to create a graph) of the optical unit trouble selected in the trouble list 601 from the trouble detection history data shown in Fig. 19 .

[0155] In S1611, the CPU 201 creates a graph of the dirt level [%] according to the time series of dates in the trouble history data 1103 referenced in S1610, and displays the dirt details screen 610 of Fig. 9. At this time, data for the display period specified in the display period 612 is displayed as a dirt transition graph 611. After the dirt details screen 610 is displayed, the close button 613 is pressed to return to the trouble detection screen 600 (not shown). Then, the process returns to waiting for a judgment in S1601.

[0156] If the button pressed in S1609 is the treated button 603, the determination result in S1609 is "treated", and the process proceeds to S1612. In S1612, the CPU 201 executes a treated process for the trouble selected in the trouble list 601. If the trouble selected in the trouble list 601 is the optical unit, the CPU 201 resets the contamination level in the trouble history data 1103 to the initial value of "0". If the trouble selected in the trouble list 601 is the cassette, the CPU 201 resets the abnormality detection in the trouble history data 1103 to the initial value of "none". Thereafter, the CPU 201 displays the trouble detection screen 600 reflecting the latest trouble detection history data.

[0157] If the button pressed in S1609 is neither the stain details button 602 nor the treated button 603, the determination result in S1609 is “other.” In this case, the process proceeds to S1601 to determine which of the buttons 501 to 506 was pressed.

[0158] Next, a description will be given of the case where the pressed button is in the notification area for error 405 or the error button 504. If the pressed button in S1601 is in the notification area for error 405 or the error button 504, the determination result in S1601 is "error", and the process proceeds to S1613.

[0159] In S1613, the CPU 201 refers to the error history data stored in the HDD 204 and shown in FIG.

[0160] In S1614, the CPU 201 displays the error screen 700 of Fig. 10 on the operation unit 212 in accordance with the error history data referenced in S1613. At this time, the error list 701 displays all errors listed in the error history data shown in Fig. 20.

[0161] After the error screen 700 is displayed in S1614, if the CPU 201 detects that a button on the screen has been pressed, it determines in S1615 which button on the error screen 700 has been pressed.

[0162] If the button pressed in S1615 is the error details button 702, the determination result in S1615 is "error details," and the process proceeds to S1616. In S1616, the CPU 201 refers to detailed information (not shown) registered in the HDD 204 regarding the error code selected in the error list 701.

[0163] In S1617, CPU 201 uses the error information referenced in S1616 to display error details screen 710 of Fig. 11. After the error details screen 710 is displayed, the close button 714 is pressed to return to the error screen 700 (not shown). Thereafter, the process returns to waiting for a determination in S1601.

[0164] If the button pressed in S1615 is other than the error details button 702, the determination result in S1615 is “other.” In this case, in the determination in S1601, it is determined which of the buttons 501 to 506 was pressed.

[0165] Next, a description will be given of the case where the pressed button is the notification area of ​​jam 406 or the jam button 505. If the pressed button in S1601 is the notification area of ​​jam 406 or the jam button 505, the determination result in S1601 is "jam", and the process proceeds to S1618.

[0166] In S1618, the CPU 201 refers to the jam history data stored in the HDD 204 and shown in FIG.

[0167] In S1619, the CPU 201 displays the jam screen 800 of FIG. 12 on the operation unit 212 in accordance with the jam history data referenced in S1618. At this time, the cross-sectional view 401 displays an icon corresponding to the jam-related abnormality determined in S1533 of FIG. 28. Other icons (icons corresponding to abnormalities related to part life or trouble detection) are not displayed. Furthermore, the jam list 801 displays only the most recent data for each jam code from the jam history data shown in FIG. 21. In other words, for data of the same jam code, only the most recent item is displayed in the jam list 801.

[0168] After the jam screen 800 is displayed in S1619, if the CPU 201 detects that a button on the screen has been pressed, then in S1620 it is determined which button on the jam screen 800 has been pressed. If the button pressed in S1620 is the jam details button 802, the determination result in S1620 is "jam details," and the process proceeds to S1621.

[0169] In S1621, the CPU 201 refers to the data that matches the jam code of the jam selected in the jam list 801 from the jam history data shown in FIG.

[0170] In S1622, the CPU 201 uses the data that matches the jam code referenced in S1621 to display the jam details screen 810 of Fig. 13. After the jam details screen 810 is displayed, the close button 814 is pressed to return to the jam screen 800 (not shown). Thereafter, the process returns to waiting for a determination in S1601.

[0171] If the button pressed in S1620 is the reset button 803, the determination result in S1620 is "reset", and the process proceeds to S1623.

[0172] In S1623, the CPU 201 deletes the jam history data in Fig. 21 and updates the date and time of the reset date and time 804 (Fig. 12) to the date and time when the reset button was pressed. After that, the jam screen 800 reflecting the latest jam history data in Fig. 21 is displayed.

[0173] If the pressed button in S1623 is neither the jam details button 802 nor the reset button 803, the determination result in S1623 is “other.” In this case, in the determination in S1601, it is determined which of the buttons 501 to 506 was pressed.

[0174] Next, a description will be given of the case where the pressed button is the usage status button 407 or the usage status button 506. If the pressed button in S1601 is the usage status button 407 or the usage status button 506, the determination result in S1601 is "usage status," and the process proceeds to S1624.

[0175] In S1624, CPU 201 determines which button was pressed on usage status screen 900 of Fig. 14 (to Fig. 17). The button selected as the initial value on usage status screen 900 is temperature button 901. Therefore, when transitioning from a screen other than usage status screen 900, the determination result in S1624 is "temperature," and processing proceeds to S1625.

[0176] In S1625, the CPU 201 refers to the temperature data stored in the HDD 204 and shown in FIG.

[0177] In S1626, the CPU 201 creates a temperature change graph 905 (FIG. 14) for the inside of the apparatus 1403 and the outside of the apparatus 1404 based on the temperature data referenced in S1625 in chronological order of the date 1401 and the time 1402. At this time, the CPU 201 creates a graph for the date specified by the date switching button 906. Then, the CPU 201 displays the temperature change screen of FIG. 14 on the operation unit 212. Thereafter, the process returns to waiting for a determination in S1624.

[0178] If the button pressed in S1624 is the humidity button 902, the determination result in S1624 is "humidity", and the process proceeds to S1627. In S1627, the CPU 201 refers to the humidity data stored in the HDD 204 and shown in FIG.

[0179] In S1628, the CPU 201 creates a humidity change graph 907 (FIG. 15) for inside the apparatus 1413 and outside the apparatus 1414 based on the temperature data referenced in S1627 in chronological order of date 1411 and time 1412. At this time, the CPU 201 creates a graph for the date specified by the date switching button 908. Then, the CPU 201 displays the humidity change screen of FIG. 15 on the operation unit 212. Thereafter, the process returns to waiting for a determination in S1624.

[0180] If the button pressed in S1624 is the print count button 903, the determination result in S1624 is "print count", and the process proceeds to S1629. In S1629, the CPU 201 refers to the print count data stored in the HDD 204 and shown in FIG.

[0181] In S1630, the CPU 201 creates a print count graph 909 (FIG. 16) for the number of prints 1423 based on the print count data referenced in S1629 in chronological order of date 1421 and time 1422. If "Day" is selected with the display period switch button 910 in FIG. 16, a graph of the number of prints for one day is created with the time in one-hour increments. If "Month" is selected with the display period switch button 910, a graph of the number of prints for one month is created with the time in one-day increments. The CPU 201 then displays the print count screen of FIG. 16 on the operation unit 212. Thereafter, the process returns to waiting for a determination in S1624.

[0182] If the button pressed in S1624 is the cassette history button 904, the determination result in S1624 is "cassette history", and the process proceeds to S1631. In S1631, the CPU 201 refers to the cassette operation data stored in the HDD 204 and shown in FIG.

[0183] In S1632, the CPU 201 creates a cassette history list 912 of the cassette operation data 1424 by chronologically sorting the cassette operation data referenced in S1631 by date 1431 and time 1432. Here, the CPU 201 extracts data of the cassette selected with the cassette switching button 913 in FIG. 17 to create the cassette history list 912. For example, since "cassette 1" is selected with the cassette switching button 913 in FIG. 17, the CPU 201 extracts data of "cassette 1" in the cassette 1433 in FIG. 25 to create the cassette history list 912. Then, the CPU 201 displays the cassette history screen of FIG. 17 on the operation unit 212. Thereafter, the process returns to waiting for a determination in S1624.

[0184] If the button pressed in S1624 is other than the temperature button 901, humidity button 902, number of prints button 903, or cassette history button 904, the determination result in S1624 is "other." In this case, in the determination in S1601, it is determined which of the buttons 501 to 506 was pressed.

[0185] 6 to 17 include a return to top button 501. When the return to top button 501 is pressed, the determination in S1601 becomes "return to top," and the process proceeds to S1633.

[0186] In S1633, the CPU 201 executes the top screen display process of FIGS. 26 and 27, and displays the top screen 400.

[0187] Finally, a case where an operation (not shown) to end the status monitor is input on the screens of Figures 4 to 17 will be described. In S1601, when CPU 201 detects an operation to end the status monitor, the determination result of S1601 becomes "end." Then, in S1634, processing is executed to end the display of the status monitor.

[0188] 29 to 31, the service technician can transition from the top screen 400 in FIG. 4 to the parts life screen 500, trouble detection screen 600, error screen 700, jam screen 800, and usage status screen 900 to check detailed information. This allows the service technician to quickly display these screens from the top screen 400 and gather the information necessary for troubleshooting. Furthermore, by using buttons 502 to 506 to move back and forth between these screens, the service technician can infer the cause of the abnormality from the related information on each screen and consider countermeasures based on that information. Furthermore, the service technician can infer when an abnormality will occur in areas that have not yet become abnormal (mainly due to the end of parts life and dirt on the optical unit) and make preparations for that occurrence.

[0189] As described in the above embodiment, predetermined criteria for determining an abnormality may also be set for the usage status (history information). In this case, the display unit 302 displays an area for notifying information about an abnormality in the usage status on the top screen 400, similar to the notification areas for the part life 403 and the error 405. The display unit 302 may also display an icon corresponding to the information about the abnormality on the cross-sectional view 401. For example, with regard to temperature, if the current temperature exceeds the reference range indicated by the upper and lower dotted lines in the temperature change graph 905 of FIG. 14, it may be determined to be abnormal and a notification may be sent that the current temperature is abnormal. In this case, for example, an icon corresponding to the temperature abnormality may be displayed at a predetermined position on the cross-sectional view 401, for example, around or near the cross-sectional view 401. The same applies to humidity. For example, with regard to the number of printed sheets, if the number of printed sheets exceeds a threshold, it may be determined to be abnormal. Multiple thresholds may be set in stages as the temperature criteria and the threshold for the number of printed sheets.

[0190] Furthermore, in this embodiment, for example, temperature and humidity are configured to be elements within the category of usage status, but for example, "environment" may be provided as a separate category of status information, and temperature and humidity may be elements within that category. In this case, for example, in Figures 4 and 6, "environment" may be provided as a status category, and when the "environment" button is pressed, a screen and button for displaying details of the temperature or humidity may be displayed.

[0191] In this embodiment, the usage status (usage status button 407) is displayed as one category on the top screen 400 shown in Fig. 4. However, instead of the usage status button 407, the top screen 400 may display a temperature button 901, a humidity button 902, a number of prints button 903, and a cassette history button 904 (Fig. 14).

[0192] In addition, in this embodiment, pressing the usage status button 407 on the top screen 400 shown in Fig. 4 causes a transition to another screen (Figs. 14 to 17). However, pressing the usage status button 407 may also cause a screen corresponding to Fig. 14, 15, 16, or 17 to be displayed as a pop-up superimposed on the top screen 400.

[0193] Next, an information processing system 1 of a second embodiment will be described. The information processing system 1 of the second embodiment is common to the information processing system 1 of the first embodiment in that the image processing device 103 displays information related to the lifespan of a component. On the other hand, the information processing system 1 of the second embodiment differs from the information processing system 1 of the first embodiment in that the image processing device 103 displays information related to the lifespan of the component together with information according to the method used to estimate the lifespan. More specifically, the image processing device 103 estimates the lifespan of the component of the image processing device 103 using a preset method, but in the second embodiment, the image processing device 103 displays information related to the method used to estimate the lifespan of the component together with the information related to the lifespan. Regarding the second embodiment, only the configurations different from the first embodiment will be described, and a description of the same configurations as the first embodiment will be omitted.

[0194] Fig. 32 is a diagram showing history data according to the second embodiment. The history data shown in Fig. 32 is history data used to display information about part lifespans. The history data shown in Fig. 32 is stored in the history management unit 304. The part status history data 1003 included in the history data shown in FIG. 32 shows a history of "versions." A "version" is the format of a method used to estimate the lifespan of a part. In the illustrated example, "V1.0" and "V2.0" are shown as "versions," with "V2.0" being a more recent format than "V1.0." More specifically, "V1.0" is the version of the lifespan estimation method before the update, and "V2.0" is the version of the lifespan estimation method after the update. "V1.0" is a method for estimating the lifespan of a part from, for example, the "number of sheets used" of paper used after the part is replaced. Furthermore, "V2.0" is a method for estimating the lifespan of a part from information detected by various sensors 255 regarding the state of the part, such as the current value of the part or the resistance value of the part.

[0195] In this embodiment, the method for estimating the lifespan of a part may be updated in the server PC 101. When an update occurs, information indicating the method for estimating the lifespan of a part is transmitted from the server PC 101 to the image processing device 103 in a lifespan estimation process described below, and the latest information indicating the method for estimating the lifespan of a part is stored in the history management unit 304 of the image processing device 103. 32, the latest "version" of "drum unit Y," "drum unit M," "drum unit C," "drum unit K," "cassette roller 1," "cassette roller 2," and "cassette roller 3" is shown as "V2.0." The latest "version" of "outer secondary transfer roller" is shown as "V1.0." In this embodiment, the method for estimating the lifespan of a component is updated for each component of the image processing device 103, so the latest "version" may differ for each component. The information indicating the type of method used to estimate the lifespan of a part, shown as "version" in FIG. 32, may be referred to as type information below.

[0196] 33 is a flowchart showing the flow of the lifespan estimation process. The lifespan estimation process is a process in which the image processing device 103 estimates the lifespan of components of the image processing device 103. The lifespan estimation process is started at predetermined time intervals. The predetermined time may be any time, for example, 24 hours. However, the lifespan estimation process may also be started in response to an instruction from a user of the image processing device 103. The control unit 301 of the image processing apparatus 103 acquires estimation method information from the server PC 101 (S1901). The estimation method information is information indicating a method for estimating the lifespan of a part. The control unit 301 determines whether the lifespan estimation method identified from the acquired estimation method information has been updated from the method used to estimate the lifespan of the part and stored in the history management unit 304 (S1902). The control unit 301 determines whether the method has been updated based on whether the type of the lifespan estimation method identified from the acquired estimation method information is different from the latest type indicated in the history data (see FIG. 32) stored in the history management unit 304.

[0197] If the method has been updated (YES in S1902), the history management unit 304 saves the acquired estimation method information in the control unit 301 by overwriting the contents of the history data (see FIG. 32) (S1903). If the method has not been updated (NO in S1902), or after step 1903, the control unit 301 acquires part information (S1904). The part information is information used by the control unit 301 to estimate the lifespan of a part. The part information includes information indicating the number of sheets of paper used and information detected by the various sensors 255 regarding the state of the part. Examples of information detected by the various sensors 255 include information indicating the current value of the part and information indicating the resistance value of the part. The control unit 301 may acquire the part information from the server PC 101, or may acquire the part information within the image processing device 103.

[0198] The control unit 301 estimates the lifespan of the part from the part information using the method indicated in the estimation method information (S1905). More specifically, the control unit 301 estimates the lifespan of the part by calculating the condition value and condition level of the part. That is, the condition value and condition level of the part are regarded as the lifespan of the part. Furthermore, the calculation of the condition value and condition level of the part is regarded as an estimate of the lifespan of the part. The history management unit 304 stores the information indicating the lifespan of the parts by recording the information indicating the lifespan of the parts estimated by the control unit 301 in the history data (see FIG. 32) (S1906). At this time, the history management unit 304 also records the parts information acquired by the control unit 301 in the history data.

[0199] In the above description, the control unit 301 of the image processing device 103 acquires the estimation method information from the server PC 101 in the lifespan estimation process, but this is not limiting. The estimation method information may be updated in the ROM 203 or HDD 204 of the image processing device 103, and the control unit 301 may acquire the latest estimation method information stored in the image processing device 103. Furthermore, the lifespan estimation process may be performed for each component, or may be performed collectively for all components recorded in the history data. When the lifespan estimation process is performed collectively for all components, for example, each step of the lifespan estimation process is performed sequentially for each component.

[0200] 34 is a flowchart showing the flow of the lifespan display process. The lifespan display process is a process in which the image processing device 103 displays a part lifespan screen 500, which will be described later. In this embodiment, the lifespan display process is started by pressing the part lifespan 403 button (see FIG. 4) or the part lifespan button 502 (see FIG. 8). The control unit 301 of the image processing device 103 extracts information indicating the latest history for each part from the history data (see FIG. 32) stored in the history management unit 304 (S2001). Note that the information indicating the latest history for each part extracted by the control unit 301 may hereinafter be referred to as latest history information.

[0201] The control unit 301 determines whether or not model information that satisfies the display conditions exists (S2002). The display conditions are conditions used by the control unit 301 to determine whether or not information about the method used to estimate the lifespan of a part is to be displayed on the part lifespan screen 500. In this embodiment, the display conditions are determined to be that a highly accurate estimation method was used to estimate the lifespan of a part. More specifically, the display conditions are that a method with a model number of "V2.0" was used to estimate the lifespan indicated in the history data. The control unit 301 determines whether or not model information that satisfies the display conditions exists based on whether or not model information indicated as "V2.0" exists in the model information for each part included in the latest history information.

[0202] If model information that satisfies the display conditions exists (YES in S2002), the control unit 301 generates information suggesting the method used to estimate the life of the part associated with the model information that satisfies the display conditions (S2003). If there is no model information that satisfies the display conditions (NO in S2002), or after step 2004, the process proceeds to the next step. The control unit 301 displays the parts life screen 500 on the display unit 302, which includes the "part name," "condition level," "condition value," and "number of sheets used" for each part shown in the latest history information (S2004). Also, if information has been generated in step 2003, the control unit 301 displays the generated information on the parts life screen 500, consecutively to the "part name" that indicates the target part.

[0203] 35 is a diagram showing a part lifespan screen 500 according to the second embodiment. This part lifespan screen 500 is displayed when the lifespan display process (see FIG. 34) is performed. In this embodiment, a method suggestion image 1701 is displayed in the parts list 507 on the parts life screen 500. The method suggestion image 1701, which is an example of method information, is an image that suggests the method used to estimate the life of the part. In this example, the method suggestion image 1701 suggests that the life of the part was estimated by a method with higher estimation accuracy among multiple methods. In the illustrated example, a "*" mark is displayed as the method suggestion image 1701.

[0204] Method suggestion image 1701 is information generated in step 2003 of the lifespan display process (see FIG. 34). In this embodiment, the latest model information associated with "drum unit Y," "drum unit M," "drum unit C," "drum unit K," and "cassette roller 1," among the components whose information is displayed in parts list 507, is "V2.0" (see FIG. 32). Therefore, the model information associated with these components satisfies the display conditions (see step 2002 in FIG. 34), and method suggestion image 1701 is displayed immediately following the names of these components in parts list 507. On the other hand, the latest model information associated with the "secondary transfer outer roller" is "V1.0," which does not satisfy the display conditions. Therefore, the legal suggestion image 1701 for the "secondary transfer outer roller" is not displayed in the parts list 507.

[0205] Next, a modified example of the part lifespan screen 500 will be described. The part lifespan screen 500 of this embodiment is not limited to the configuration shown in FIG. 35. In the following, it is assumed that the type of the method used to estimate the lifespan of the part "drum unit Y" is "V3.0," which is a newer type than "V1.0" and "V2.0." It is also assumed that the types of the methods used to estimate the lifespan of parts other than "drum unit Y" are the same as those shown in FIG. 32.

[0206] (Variation 1) 36 is a diagram showing a parts lifespan screen 500 according to Modification 1. In the parts list 507 of the parts lifespan screen 500 according to Modification 1, a method suggestion image 1701 is displayed for each part. In addition, in Modification 1, the display condition (see step 2002 in FIG. 34) is that the latest model information indicates a certain model, and the model information of all parts satisfies the display condition. Therefore, in the parts list 507, the method suggestion image 1701 is displayed in association with the name of each part.

[0207] Furthermore, in Modification Example 1, method suggestion image 1701 displays a version name indicating the model of the method used to estimate the lifespan of the part. In the illustrated example, method suggestion image 1701 for "drum unit Y" displays the text "(V3.0)." Furthermore, method suggestion images 1701 for "drum unit M," "drum unit C," "drum unit K," and "cassette roller 1" display the text "(V2.0)." Furthermore, method suggestion image 1701 for "secondary transfer outer roller" displays the text "(V1.0)."

[0208] (Variation 2) FIG. 37 is a diagram showing a part lifespan screen 500 according to Modification 2. In parts list 507 on part lifespan screen 500 according to Modification 2, method suggestion images 1701 are displayed only for "drum unit Y" and "secondary transfer outer roller." In addition, in Modification 2, a display condition (see step 2002 in FIG. 34) is set such that the latest model information indicates a model that is newer or older than "V2.0." Therefore, "V3.0," which is the model information for "drum unit Y," and "V1.0," which is the model information for "secondary transfer outer roller," satisfy the display condition, and method suggestion images 1701 are displayed for each of "drum unit Y" and "secondary transfer outer roller."

[0209] Furthermore, in Modification Example 2, method suggestion image 1701 displays information indicating the accuracy of the method used to estimate the lifespan of the part. In the illustrated example, method suggestion image 1701 for "drum unit Y" displays the text "High accuracy." This text suggests that the accuracy is higher than the "V2.0" model established as the accuracy standard for the method used to estimate the lifespan of the part. Furthermore, method suggestion image 1701 for "outer secondary transfer roller" displays the text "Conventional accuracy," suggesting that the accuracy is lower than the "V2.0" model established as the accuracy standard.

[0210] In addition, in Modification 2, only the method suggestion image 1701 for "high accuracy" may be displayed on the part lifespan screen 500. Also, the part lifespan screen 500 may display a method suggestion image 1701 that suggests an accuracy lower than "high accuracy" but higher than "conventional accuracy," such as that corresponding to version "V2.0." An example of a method suggestion image 1701 that suggests an accuracy lower than "high accuracy" but higher than "conventional accuracy" is a method suggestion image 1701 that displays the text "intermediate accuracy." Also, the text "low accuracy" may be displayed as the method suggestion image 1701 corresponding to version "V1.0."

[0211] Fig. 38 is a diagram showing a status details screen 510 of this embodiment. Note that the status details screen 510 shown in Fig. 38 is the status details screen 510 that is displayed when the status details button 508 is pressed with "drum unit Y," "drum unit C," and "outer secondary transfer roller" selected in the parts list 507 (see Fig. 37, etc.). In the example below, the model number of the method used to estimate the lifespan of the "secondary transfer outer roller" was "V1.0," regardless of when the lifespan estimation was performed. The model number of the method used to estimate the lifespan of all parts other than the "secondary transfer outer roller" and "drum unit Y" was "V1.0" until February 4, 2024, and "V2.0" from February 5 onward. The model number of the method used to estimate the lifespan of "drum unit Y" was "V1.0" until February 4, 2024, "V2.0" from February 5 to February 11, and "V3.0" from February 12 onward.

[0212] 38 displays a type identification image 3801. The type identification image 3801 is an image for identifying the type of method used to calculate the condition value of the part shown in the condition transition graph 511. In the illustrated example, the type identification image 3801 indicates, for each type of line shown in the condition transition graph 511, "V1.0," "V2.0," or "V3.0," which is the type of method used to calculate the condition value of the part. Here, the type identification image 3801 and the condition transition graph 511 are regarded as method information corresponding to the method used to estimate the lifespan of the part.

[0213] The state transition graph 511 also shows lines indicating the transition of the state values ​​of "drum unit Y," "drum unit C," and "outer secondary transfer roller." Here, in the state transition graph 511, the "outer secondary transfer roller" is shown only by lines of the type for which the model number specified by the model identification image 3801 is "V1.0." Therefore, by looking at the state transition graph 511, a manager of the image processing device 103, such as a serviceman, can recognize that the model number of the method used to estimate the lifespan of the "outer secondary transfer roller" is "V1.0," regardless of when the lifespan was estimated.

[0214] Furthermore, in status transition graph 511, "drum unit C" is shown by a type line in which the model type identified from model identification image 3801 is "V1.0" from January 1 to February 4, 2024. Furthermore, "drum unit C" is shown by a type line in which the model type identified from model identification image 3801 is "V2.0" from February 5 to February 16, 2024. Therefore, by looking at status transition graph 511, the administrator of image processing device 103 recognizes that the model type of the method used to estimate the life of "drum unit C" is "V1.0" until February 4, 2024, and "V2.0" from February 5 onwards.

[0215] Furthermore, in the status transition graph 511, "drum unit Y" is indicated by a type line where the model type identified from the model identification image 3801 is "V1.0" from January 1 to February 4, 2024. Furthermore, "drum unit Y" is indicated by a type line where the model type identified from the model identification image 3801 is "V2.0" from February 5 to February 11, 2024. Furthermore, "drum unit Y" is indicated by a type line where the model type identified from the model identification image 3801 is "V3.0" from February 12 to February 16, 2024. Therefore, by looking at the status transition graph 511, the administrator of the image processing device 103 recognizes that the model type of the method used to estimate the life of "drum unit Y" will be "V1.0" until February 4, 2024. The administrator also recognizes that the model of the method used to estimate the lifespan of "Drum Unit Y" is "V2.0" from February 5th to February 11th, 2024, and "V3.0" from February 12th onwards.

[0216] In response to pressing the status details button 508, the control unit 301 acquires history data 1003 including the version history (see S1605 in FIG. 29), and generates the status details screen 510 shown in FIG. 38 and displays it on the display unit 302 (see S1606). Furthermore, the method of displaying information corresponding to the method used to estimate the lifespan of a part in the state transition graph 511 is not limited to the above-described example. In the state transition graph 511, a line of a color corresponding to the method used to estimate the lifespan of a part may be displayed. In addition, in the state transition graph 511, a line of a thickness corresponding to the method used to estimate the lifespan of a part may be displayed. In other words, in the state transition graph 511, any type of graph may be displayed as long as the history of the method used to estimate the lifespan of a part can be recognized. Furthermore, the state detail screen 510 may display a state transition graph 511 for all parts shown in the parts list 507 on the parts life screen 500 .

[0217] Furthermore, the configuration for displaying the history of the method for estimating the lifespan of a part on the status details screen 510 is not limited to the example described above. On the status details screen 510, the type identification image 3801 may show, for each component whose information is shown in the status transition graph 511, the period during which this method was used for each type of method used to estimate the lifespan. Furthermore, the status details screen 510 does not need to identify all methods by which the lifespan has been estimated. For example, the status details screen 510 may identify the period in which the method was used for only the methods identified from the model information that satisfies the display conditions (see S2002 in FIG. 34). Even in this case, for each time point at which the lifespan is estimated, it is identified whether the method used to estimate the lifespan is a method identified from the model information that satisfies the display conditions. Then, if there are two times at which different methods were used to estimate the lifespan, it is identified that the methods used to estimate the lifespan at these two times were different.

[0218] As described above, in this embodiment, the control unit 301 of the image processing device 103 acquires information about the components of the image processing device 103. Therefore, the control unit 301 can also be regarded as an acquisition unit. Examples of information about the components of the image processing device 103 include history data, estimation method information, and part information. That is, the acquisition unit's acquisition of information about the components of the image processing device 103 includes the acquisition unit's acquisition of information about the components of the image processing device 103 from a device other than the image processing device itself. The acquisition unit's acquisition of information about the components of the image processing device 103 also includes the acquisition unit's acquisition of information about the components of the image processing device 103 generated in the image processing device itself. The control unit 301 also displays information about the estimated lifespan of the components together with method information corresponding to the method used for the estimation (see FIGS. 35 to 38). Furthermore, the control unit 301 displays all of the information about the lifespan of the components estimated at each of multiple time points (see FIGS. 9 and 38). Examples of information about the lifespan include information indicating the condition of the components, information indicating the condition level of the components, and the like. In this case, compared to a configuration in which only information indicating the lifespan of a part is displayed on one screen, the administrator does not need to obtain the method information himself / herself, which reduces the burden on the administrator in managing parts, such as determining whether or not to replace the part.

[0219] In this embodiment, the control unit 301 displays information about the estimated lifespan of a part and method information on a single screen, such as the part lifespan screen 500 and the status details screen 510, but this is not limited to this. The control unit 301 may display the information about the estimated lifespan of the part and the method information on separate screens, as long as both are displayed together. For example, the control unit 301 may simultaneously display a first screen showing the information about the estimated lifespan of the part and a second screen showing the method information.

[0220] In this embodiment, the lifespan is estimated based on an index that changes depending on the use of the image processing device 103. Examples of the index include the number of sheets used, the current value of the component, and the resistance value of the component. There are multiple methods for estimating the lifespan, which differ depending on the index used for the estimation. In this case, the administrator can be made aware of information according to the index used to estimate the lifespan.

[0221] In this embodiment, the control unit 301 displays information about the lifespan of each of the plurality of parts, and also displays method information for parts whose lifespans have been estimated by a predetermined method (see FIGS. 35 and 37). An example of the predetermined method is a method identified from model information that satisfies a display condition. In this case, compared to a configuration in which all of the method information for each of a plurality of parts is displayed, the administrator can emphasize the method information to be displayed.

[0222] In this embodiment, the control unit 301 also displays information about the life span and method information for each of the multiple parts (see FIGS. 36 and 38). In this case, it is possible to prevent the method information from not being displayed for a part for which the administrator needs the method information.

[0223] In this embodiment, the control unit 301 displays information about the lifespan of the part estimated at each of a plurality of points in time and method information on one screen (see FIG. 38). In this case, the administrator can be made aware of changes over time in the estimated lifespan of a part, along with information about the method used to estimate the lifespan.

[0224] In this embodiment, the control unit 301 also displays information about the lifespan estimated at each of a plurality of points in time for each of a plurality of parts on one screen on which the method information is displayed (see FIG. 38). In this case, the manager can be made aware of information about the lifespan estimated at each of a plurality of points in time for each part.

[0225] In this embodiment, the multiple time points include a first time point and a second time point that is later than the first time point. Examples of the first time point include January 29, 2024 and February 4, 2024. Examples of the second time point include February 5, 2024 and February 12, 2024. If the method used for estimation of a part at the first time point is different from that used at the second time point, the control unit 301 displays information indicating that the method used at the first time point is different from that used at the second time point on a screen that displays the method information (see FIG. 38). Examples of information indicating that the method used at the first time point is different from that used at the second time point include a status transition graph 511 displayed by a line of the type shown in the model identification image 3801 on the status detail screen 510. In this case, the administrator can be made aware of changes over time in the estimated lifespan of the part, along with the history of the method used to estimate the lifespan.

[0226] The configuration of the method suggestion image 1701 is not limited to the example described above. For example, the method suggestion image 1701 may display a number of marks corresponding to the number of versions of the method used to estimate the lifespan of the part, thereby allowing the administrator to recognize the accuracy of the method used to estimate the lifespan of the part. As an example, if the version is "V1.0", "*" may be displayed as the method suggestion image 1701, and if the version is "V2.0", "**" may be displayed as the method suggestion image 1701. Furthermore, if the version is "V3.0", "***" may be displayed as the method suggestion image 1701.

[0227] Also, although it has been described that the method suggestion image 1701 is displayed consecutively to the part name in the parts list 507 of the parts life screen 500, this is not limiting. The method suggestion image 1701 may also be displayed consecutively to the status level, status value, etc. in the parts list 507 of the parts life screen 500. In other words, the method suggestion image 1701 may be displayed in any manner as long as it is displayed in association with information related to the part.

[0228] Furthermore, the information indicating the type of method used to estimate the lifespan of a component is not limited to the above-described example. For example, instead of the above-described versions "V1.0," "V2.0," and "V3.0," an indicator such as "low," "medium," or "high" indicating the accuracy of the lifespan estimation method may be provided as the information indicating the type of method used to estimate the lifespan of a component. In other words, the information indicating the type of method used to estimate the lifespan of a component may be any information that identifies the type of lifespan estimation method.

[0229] Furthermore, the information displayed in the parts list 507 on the parts lifespan screen 500 is not limited to the example described above. Parts list 507 may show all of the indicators used by control unit 301 to estimate the lifespan of each component. For example, control unit 301 may display "number of sheets used" in parts list 507 for components whose lifespans have been estimated using the method of version "V1.0," such as the "outer secondary transfer roller." Furthermore, control unit 301 may display the current value and resistance value of each component in parts list 507 for components whose lifespans have been estimated using the method of version "V2.0," such as "drum unit Y" and "drum unit C."

[0230] Furthermore, the state transition graph 511 may be a graph showing a transition of a state level instead of a graph showing a transition of a state value. In other words, the state transition graph 511 may be a graph showing a transition of information related to the estimated lifespan of a part. Furthermore, it is sufficient that state transition graph 511 shows information about the lifespan estimated at at least two points in time. That is, when control unit 301 causes information about the lifespan of a part estimated at each of a plurality of points in time to be displayed, it includes causing information about the lifespan of a part estimated at each of at least two points in time to be displayed.

[0231] In addition, in the present embodiment, the image processing device 103 acquires information about the components of the image processing device 103 and displays the information about the lifespan together with the method information. However, the present invention is not limited to this. For example, the server PC 101 may have the configuration shown in Fig. 3. The server PC 101 may acquire information about the components of the image processing device 103 from the image processing device 103 and display the information about the lifespan together with the method information. Furthermore, the lifespan of a part is not limited to being estimated by the image processing device 103. The lifespan of a part may be estimated by the server PC 101. In this case, the server PC 101 may display information indicating the estimated lifespan on the server PC 101, or may transmit the information to the image processing device 103 to be displayed on the display unit 302 of the image processing device 103.

[0232] The present invention also includes cases where a software program that realizes the functions of each of the above-described embodiments is supplied to a system or device having a computer that can execute the program directly from a recording medium or via wired / wireless communication, and the program is executed. Therefore, the program code itself, supplied and installed on a computer to implement the functional processes described above, also embodies the present invention. In other words, the computer program itself for implementing the functional processes of the present invention is also included in the present invention. In this case, the program may take any form, such as object code, a program executed by an interpreter, or script data supplied to an OS, as long as it has the program's functionality. Recording media for providing the program may include, for example, a hard disk, a magnetic recording medium such as a magnetic tape, an optical / magneto-optical storage medium, or a non-volatile semiconductor memory. Another possible method for providing the program is to store the computer program forming the present invention on a server on a computer network, and then download the computer program to a connected client computer.

[0233] The present disclosure includes the following configurations. (Configuration 1) acquiring means for acquiring information about components of the image processing device; a control means for displaying information relating to the estimated lifespan of the component together with method information according to the method used for the estimation; Equipped with The control means displays information about the lifespan of the component estimated at each of a plurality of points in time. (Configuration 2) the lifespan is estimated based on an index that changes depending on use of the image processing device; 2. The image processing device according to configuration 1, wherein the method includes a plurality of methods that differ depending on the index used for the estimation. (Configuration 3) 3. The image processing device according to claim 1, wherein the control means displays the information regarding the lifespan for each of a plurality of parts, and displays the method information for a part of the plurality of parts whose lifespan has been estimated by a predetermined method. (Configuration 4) 4. The image processing device according to any one of configurations 1 to 3, wherein the control means displays the information regarding the lifespan and the method information for each of a plurality of parts. (Configuration 5) 5. The image processing device according to any one of configurations 1 to 4, wherein the control means displays the information about the lifespan of the part estimated at each of the plurality of time points and the method information on one screen. (Configuration 6) 6. The image processing device according to claim 5, wherein the control means causes the information about the lifespan estimated at each of the plurality of time points for each of the plurality of parts to be displayed on the one screen on which the method information is displayed. (Configuration 7) The plurality of time points include a first time point and a second time point that is later than the first time point, The image processing device according to configuration 5, wherein, when the method used for the estimation of the part at the first time point is different from the method used for the estimation of the part at the second time point, the control means displays information indicating that the method used for the estimation of the part at the first time point is different from the method used for the estimation of the part at the second time point on the first screen on which the method information is displayed. (Configuration 8) acquiring means for acquiring information about components of the image processing device; and a control means for displaying information relating to the estimated lifespan of the component together with method information according to the method used for the estimation. (Configuration 9) obtaining information about components of the image processing device; displaying information about the estimated lifespan of the component together with method information according to the method used for the estimation; Equipped with displaying information about the estimated life of the component at each of a plurality of time points; A method comprising: (Configuration 10) On the computer, obtaining information about components of the image processing device; a function of displaying information about the estimated lifespan of the component together with method information according to the method used for the estimation; a function of displaying information about the lifespan of the component estimated at each of a plurality of time points; A program to make this happen. [Explanation of symbols]

[0234] 1...information processing system, 101...server PC, 102...client PC, 103...image processing device

Claims

1. acquiring means for acquiring information about components of the image processing device; a control means for displaying information relating to the estimated lifespan of the component together with method information according to the method used for the estimation; Equipped with The control means displays information about the lifespan of the component estimated at each of a plurality of points in time.

2. the lifespan is estimated based on an index that changes depending on use of the image processing device; The image processing device according to claim 1 , wherein the method includes a plurality of methods that differ depending on the index used for the estimation.

3. 2. The image processing device according to claim 1, wherein the control means displays the information regarding the lifespan for each of a plurality of parts, and displays the method information for a part of the plurality of parts whose lifespan has been estimated by a predetermined method.

4. The image processing apparatus according to claim 1 , wherein the control means displays the information regarding the life span and the method information for each of a plurality of parts.

5. The image processing apparatus according to claim 1 , wherein the control means displays the information about the lifespan of the part estimated at each of the plurality of points in time and the method information on one screen.

6. 6. The image processing device according to claim 5, wherein the control means causes the information about the lifespan estimated at each of the plurality of time points for each of the plurality of parts to be displayed on the one screen on which the method information is displayed.

7. the plurality of time points includes a first time point and a second time point that is later than the first time point, 6. The image processing device according to claim 5, wherein, when the method used for the estimation of the part at the first time point is different from the method used for the estimation of the part at the second time point, the control means displays information indicating that the method used for the estimation of the part at the first time point is different from the method used for the estimation of the part at the second time point on the one screen on which the method information is displayed.

8. acquiring means for acquiring information about components of the image processing device; and a control means for displaying information relating to the estimated lifespan of the component together with method information according to the method used for the estimation.

9. obtaining information about components of the image processing device; displaying information about the estimated lifespan of the component together with method information according to the method used for the estimation; Equipped with displaying information about the estimated life of the component at each of a plurality of time points; A method comprising:

10. On the computer, obtaining information about components of the image processing device; a function of displaying information about the estimated lifespan of the component together with method information according to the method used for the estimation; a function of displaying information about the lifespan of the component estimated at each of a plurality of time points; A program to make this happen.

Images