Computer program, management method, and management device

Abstract

To provide a computer program, a management method, and a management device that determine whether or not a member should be replaced before a printer is rented out.SOLUTION: The management device refers to history data indicating history information including usage histories of printers of each of a plurality of users. The management device uses, for each of a plurality of members included in a target printer to be rented to a target user, the history information and a scheduled rental period to determine whether or not the member satisfies a replacement condition indicating that the member should be replaced before the target printer is rented to the target user.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present specification relates to a technique for managing rental printers. [Background technology]

[0002] Printers such as copiers and multifunction machines have been used for some time. Patent Document 1 discloses a maintenance service for copiers. Specifically, when a copier detects an abnormality using a fault diagnosis function, it transmits the details of the abnormality to a management server, and the management server transmits the details of the repair, the names of the necessary parts, and the quantities thereof to a mobile phone of a service technician. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2002-041691 A Summary of the Invention [Problem to be solved by the invention]

[0004] In recent years, printer rental services have been provided. In rental services, printers are repeatedly rented and returned. During the rental period, a malfunction may occur in a component included in the printer. In this case, the user may have to purchase and replace the component himself or request repairs from an administrator, which may be a burden on the user. If the components are replaced before the printer is rented out, malfunctions during the rental period can be suppressed. However, there is room for improvement in determining whether or not to replace the components.

[0005] This specification discloses a technique for determining whether a part should be replaced before a printer is rented out. [Means for solving the problem]

[0006] The technology disclosed in this specification can be realized in the following application examples.

[0007] [Application Example 1] A computer program for a computer that manages printers for loan, the computer implementing a first reference function that references historical data indicating historical information including the usage history of each of a plurality of users' printers, and a judgment function that uses the historical information and a planned loan period to judge whether each of a plurality of components contained in a target printer to be loaned to a target user satisfies an exchange condition indicating that the target printer should be exchanged before being loaned to the target user.

[0008] According to this configuration, it is possible to appropriately determine whether or not each of the multiple components included in the target printer satisfies the replacement conditions. [Application example 2] The computer program according to Application Example 1, The judgment function is determining a projected usage amount for the planned rental period using the historical information and the planned rental period; a condition determination process for determining whether a component included in the plurality of components satisfies the replacement condition using the predicted usage amount; A computer program that executes [Application example 3] The computer program according to Application Example 2, The determination process includes, when a first condition is satisfied indicating that the history information includes a history of a first type of usage over a same period, which is a usage by the target user during a period of a past year that is the same as a period of interest that is included in the scheduled rental period, determining the predicted usage using the first type of usage over a same period. Computer program. [Application example 4] The computer program according to application example 2 or 3, The determination process includes a process of determining the predicted usage amount using the first type of past usage amount when a second condition is satisfied, which indicates that the history information does not include a history of a first type of usage amount for the same period, which is the usage amount by the target user during a period of a past year that is the same as a period of interest that is included in the scheduled rental period, but includes a history of a first type of past usage amount, which is the past usage amount by the target user. Computer program. [Application example 5] A computer program according to any one of application examples 2 to 4, The determination process includes, when a third condition is satisfied indicating that the history information does not include a history of past usage by the target user, but includes a history of a second type of usage over a same period, which is a usage by a user different from the target user during a period of a past year that is the same as a period of interest included in the scheduled rental period, the process of determining the predicted usage using the second type of usage over a same period. Computer program. [Application Example 6] A computer program according to any one of application examples 2 to 5, the determination process includes a process of determining, when the predicted usage amount is less than a reference usage amount, the predicted usage amount as the reference usage amount. Computer program. [Application Example 7] The computer program according to any one of Application Examples 2 to 6, further comprising: A second reference function is implemented in the computer to reference component usage data indicating an accumulated usage amount of each of the plurality of components included in the target printer; the condition determination process includes a process of determining that a first attention component included in the plurality of components satisfies the replacement condition when a sum of the accumulated usage amount and the predicted usage amount of the first attention component exceeds an upper limit usage amount associated with the first attention component, Computer program. [Application Example 8] The computer program according to Application Example 7, further comprising: A third reference function is implemented in the computer to reference member error data indicating the cumulative number of errors of each of the plurality of members included in the target printer; The condition determination process includes a process of determining that a second attention component included in the plurality of components satisfies the replacement condition when the cumulative number of errors of the second attention component exceeds an error threshold value. A computer program that causes the computer to realize the above. [Application Example 9] The computer program according to Application Example 8, further comprising: a fourth reference function for referring to replacement data indicating a replaced component among the plurality of components included in the target printer; an updating function for updating both the accumulated usage amount of the replaced component and the accumulated number of errors to zero; A computer program that causes the computer to realize the above. [Example 10] The computer program according to any one of application examples 1 to 9, further comprising: causing the computer to realize an output function of outputting target component data indicating target components that are determined to satisfy the exchange condition among the plurality of components included in the target printer; Computer program. [Application Example 11] A method for managing a rental printer, comprising: a first reference step of referring to history data indicating history information including the use history of the printer of each of a plurality of users; a determination step of determining, for each of a plurality of components included in the target printer to be lent to the target user, whether or not the component satisfies an exchange condition indicating that the component should be exchanged before the target printer is lent to the target user, using the history information and a scheduled lending period; A management method comprising: [Application Example 12] A management device for managing rental printers, a first reference unit that references history data indicating history information including the usage history of each of a plurality of users of the printer; a determination unit that determines, for each of a plurality of components included in a target printer to be lent to a target user, whether or not the component satisfies an exchange condition indicating that the component should be exchanged before the target printer is lent to the target user, using the history information and a scheduled lending period; A management device comprising:

[0009] The technology disclosed in this specification can be realized in various forms, such as a management method and management device, a computer program for realizing the functions of those methods or devices, a recording medium on which that computer program is recorded (e.g., a non-transitory recording medium), etc. [Brief description of the drawings]

[0010] [Figure 1]FIG. 1 is a block diagram showing the configuration of a system 1000. [Diagram 2] 1 is a schematic diagram of a print execution unit 900 of a printer 100. FIG. [Diagram 3] 13A to 13D are diagrams illustrating examples of management data. [Figure 4] FIG. 4 is an explanatory diagram showing an example of management data. [Diagram 5] 10 is a flowchart illustrating an example of a printer information transmission process. [Figure 6] 13 is a flowchart illustrating an example of a management process. [Figure 7] 10 is a flowchart illustrating an example of a process for determining an estimated number of pages to be printed. [Figure 8] 10 is a flowchart illustrating an example of a process for determining an estimated number of pages to be printed. [Figure 9] 13 is a flowchart illustrating an example of an exchange condition determination process. [Figure 10] 13 is a flowchart illustrating an example of an exchange condition determination process. [Figure 11] 13 is a flowchart illustrating an example of post-exchange processing. [Figure 12] FIG. 2 is a schematic diagram illustrating an example of an inkjet type print execution unit. [Figure 13] 13A shows an example of the third data DB3b, and FIG. 13B shows an example of the fifth data DB5b. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] A. First Example: A-1. System 1000 Configuration: 1 is a block diagram showing the configuration of a system 1000. The system 1000 includes a printer 100, a user terminal 200, a management terminal 300, and a management server 500. The management terminal 300 and the management server 500 are connected to the Internet IT. The printer 100 and the user terminal 200 are connected to a local area network LN. The local area network LN is connected to the Internet IT. The management terminal 300 can communicate with the management server 500 via the Internet IT. The printer 100 and the user terminal 200 can communicate with the management server 500 via the local area network LN and the Internet IT.

[0012] The printer 100 includes a CPU 110, a storage device 115, a display unit 140, an operation unit 150, a print execution unit 900, and a communication interface 180. These elements are connected to each other via a bus. The storage device 115 includes a volatile storage device 120 and a non-volatile storage device 130. The printer 100 is an example of a rental printer.

[0013] The display unit 140 is a device that displays images, and is, for example, a liquid crystal display. The operation unit 150 is a device that receives operations by a user, and includes, for example, a touch panel that is overlaid on the display unit 140. A user can input various instructions to the printer 100 by operating the operation unit 150. The communication interface 180 is an interface for communicating with other devices (for example, a wired LAN interface, an IEEE802.11 wireless interface). In this embodiment, the communication interface 180 is connected to a local area network LN. The print execution unit 900 is a device that prints an image on paper (an example of a print medium) using a printing material in a predetermined manner. Details of the print execution unit 900 will be described later.

[0014] The CPU 110 is an example of a data processing device. The volatile storage device 120 is, for example, a DRAM, and the non-volatile storage device 130 is, for example, a flash memory. The non-volatile storage device 130 stores a program PG1. The CPU 110 executes various processes by executing the program PG1. The CPU 110 temporarily stores various intermediate data used in the execution of the program PG1 in a storage device 115 (for example, the volatile storage device 120 or the non-volatile storage device 130). Details of the processes executed by the CPU 110 will be described later. In this embodiment, the program PG1 is stored in advance in the non-volatile storage device 130 as firmware by the manufacturer of the printer 100.

[0015] In this embodiment, multiple printers are used for lending. Hereinafter, it is assumed that the multiple printers for lending have the same configuration as printer 100. Hereinafter, when there is no need to distinguish between individual printers, the printers will also be referred to as printer 100.

[0016] The management server 500 executes a process for managing a plurality of printers 100 for rental. The management server 500 includes a CPU 510, a storage device 515, and a communication interface 580. These elements are connected to each other via a bus. The storage device 515 includes a volatile storage device 520 and a non-volatile storage device 530.

[0017] The communication interface 580 is an interface for communicating with other devices (for example, a wired LAN interface, or an IEEE802.11 wireless interface). In this embodiment, the communication interface 580 is connected to the Internet IT.

[0018] The CPU 510 is an example of a data processing device. The volatile storage device 520 is, for example, a DRAM, and the nonvolatile storage device 530 is, for example, a flash memory. The nonvolatile storage device 530 stores a program PG5 and management data DB1-DB5. The portions of the storage area of ​​the nonvolatile storage device 530 that store the management data DB1-DB5 are called storage areas A1-A5, respectively. The CPU 510 executes the program PG5 to execute a process for managing the rental printers. The CPU 510 temporarily stores various intermediate data used in the execution of the program PG5 in a storage device 515 (for example, the volatile storage device 520 or the nonvolatile storage device 530). The process executed by the CPU 510 and the management data DB1-DB5 will be described in detail later.

[0019] The management terminal 300 is a terminal device (e.g., a smartphone, a tablet computer, etc.) of an operator who performs maintenance on multiple printers. The operator can operate the management terminal 300 to control various processes provided by the management server 500. The management terminal 300 comprises a CPU 310, a storage device 315, a display unit 340, an operation unit 350, and a communication interface 380. These elements are connected to each other via a bus. The storage device 315 includes a volatile storage device 320 and a non-volatile storage device 330.

[0020] The display unit 340 is a device that displays images, such as a liquid crystal display. The operation unit 350 is a device that receives operations by a user, such as a touch panel that is overlaid on the display unit 340. The user can input various instructions to the management terminal 300 by operating the operation unit 350.

[0021] The communication interface 380 is an interface for communicating with other devices (for example, a wired LAN interface, or an IEEE802.11 wireless interface). In this embodiment, the communication interface 380 is connected to the Internet IT.

[0022] The CPU 310 is an example of a data processing device. The volatile storage device 320 is, for example, a DRAM, and the non-volatile storage device 330 is, for example, a flash memory. The non-volatile storage device 330 stores a program PG3. The CPU 310 executes the program PG3 to function as a management application that controls the processing provided by the management server 500 (details will be described later).

[0023] CPU310 temporarily stores various intermediate data used in the execution of program PG3 in a storage device (for example, volatile storage device 320 or non-volatile storage device 330). In this embodiment, program PG3 of the management application is provided by a server (not shown). Alternatively, program PG3 may be provided by a portable recording medium such as a memory card.

[0024] The user terminal 200 is a terminal device of a user who uses the printer 100 (for example, a smartphone, a tablet computer, etc.). The user can operate the user terminal 200 to cause the printer 100 to print an image. In this embodiment, the hardware configuration of the user terminal 200 is the same as the hardware configuration of the management terminal 300. The user terminal 200 includes a CPU 210, a storage device 215, a display unit 240, an operation unit 250, and a communication interface 280. These elements are connected to each other via a bus. The storage device 215 includes a volatile storage device 220 and a non-volatile storage device 230. The configurations of the elements 210, 220, 230, 240, 250, and 280 of the user terminal 200 are the same as the configurations of the elements 310, 320, 330, 340, 350, and 380 of the management terminal 300, respectively. In this embodiment, the communication interface 380 is connected to a local area network LN. The non-volatile storage device 230 stores a program PG2. The CPU 210 executes the program PG2 to perform a function as a print application that causes the printer 100 to print an image. In this embodiment, the print application program PG2 is provided by a server (not shown). Alternatively, the program PG2 may be provided by a portable recording medium such as a memory card.

[0025] A-2. Configuration of the print execution unit 900: 2 is a schematic diagram of the print execution unit 900 of the printer 100. In this embodiment, the print execution unit 900 is a laser-type color printing device. The printer 100 includes a body 102 and the print execution unit 900 housed within the body 102. The print execution unit 900 includes a scanner unit 903, a process unit 904, a transfer unit 905, a fixing unit 906, and a paper feed unit 990.

[0026] As indicated by the dashed line, the scanner unit 903 irradiates a laser beam based on image data toward a photosensitive drum 907 of the process unit 904, thereby exposing the photosensitive drum 907. Hereinafter, the scanner unit 903 will also be referred to as an exposure device 903.

[0027] The process unit 904 includes four sets of a photosensitive drum 907, a Scorotron charger 908, a drum cleaning roller 909, and a developing cartridge 910. The four sets correspond to yellow Y, magenta M, cyan C, and black K, respectively, and are arranged in that order from front to rear (from left to right in the figure). The developing cartridge 910 contains toner of the corresponding color, and includes a developing roller 911 and a supply roller 912.

[0028] The transfer unit 905 includes a drive roller 913, a driven roller 914, a conveyor belt 915, and four transfer rollers 916. The conveyor belt 915 is wound around the drive roller 913 and the driven roller 914 so that an upper portion of the conveyor belt 915 contacts each of the four photosensitive drums 907. The four transfer rollers 916 correspond to the four photosensitive drums 907, respectively. The transfer rollers 916 are disposed below the corresponding photosensitive drums 907 with the upper portion of the conveyor belt 915 sandwiched therebetween.

[0029] The paper feed unit 990 is disposed in front of the transfer unit 905, and includes a drive roller 991, a driven roller 992 in contact with the drive roller 991, and a rotation sensor 999 that detects the rotation of the drive roller 991. The paper feed unit 990 supplies paper stored in a paper feed tray (not shown) to the process unit 904. Although not shown, in this embodiment, the printer 100 includes two paper feed trays. A paper feed unit 990 is provided for each paper feed tray. In FIG. 2, one paper feed unit 990 is shown as a representative.

[0030] The fixing unit 906 is disposed behind the transfer unit 905 , and includes a heating roller 917 and a pressure roller 918 that contacts the heating roller 917 .

[0031] When the print execution unit 900 executes printing, the scorotron charger 908 uniformly charges the surface of the photosensitive drum 907. The scanner unit 903 exposes the surface of the photosensitive drum 907. As a result, an electrostatic latent image based on image data is formed on the surface of the photosensitive drum 907. The supply roller 912 supplies toner in the development cartridge 910 to the development roller 911. The development roller 911 supplies toner to the electrostatic latent image on the surface of the photosensitive drum 907. As a result, a toner image is carried on the surface of the photosensitive drum 907. The paper feed unit 990 supplies paper P from a paper feed tray (not shown) between the frontmost photosensitive drum 907 (the yellow photosensitive drum 907 in this embodiment) and the conveyor belt 915. The paper P is conveyed from the front to the rear by the conveyor belt 915. The toner image on the photosensitive drum 907 is transferred to the paper P by sandwiching the paper P between the photosensitive drum 907 and a transfer roller 916. After the four-color toner image has been transferred, the paper P passes between a heating roller 917 and a pressure roller 918. The toner image on the paper P is thermally fixed to the paper P by the heat and pressure applied by the heating roller 917 and the pressure roller 918. The paper P is then discharged onto the paper output tray 104. After the toner image has been transferred, the toner remaining on the photosensitive drum 907 is collected by the corresponding drum cleaning roller 909.

[0032] 3(A)-3(D) and FIG. 4 are explanatory diagrams showing examples of management data used to manage printers for loan. FIG. 3(A) shows an example of the first management data DB1 (also simply called the first data DB1). The first data DB1 shows the correspondence between a user identifier UID, a loan printer identifier PIDx, and a history data identifier UDID. The user identifier UID is identification information of a user. The loan printer identifier PIDx is identification information of a printer loaned to a user. If the user is not currently borrowing a printer, the loan printer identifier PIDx is blank. The history data identifier UDID is an identifier of individual user data indicating the user's usage history of the printer. If the user has never used the printer to print, the history data identifier UDID is blank.

[0033] FIG. 3B shows an example of the second management data DB2 (also simply referred to as the second data DB2). The second data DB2 is data showing the usage history of the printer. The second data DB2 shows the correspondence between the rental period PP and the number of printed pages NP. In this embodiment, the rental period PP is expressed by a combination of the year and the month.

[0034] The second data DB2 includes a plurality of individual user data corresponding to a plurality of users. FIG. 3(B) shows an example of individual user data DB2Ua associated with a first user Ua in the second data DB2. The individual user data is a portion of the second data DB2 that indicates the usage history of one user. A unique identifier is assigned to the individual user data. The identifier of the individual user data is associated with a history data identifier UDID (FIG. 3(A)). Hereinafter, the second data DB2 is also referred to as history data DB2. The individual user data is also referred to as user history data. History information indicated by the history data DB2 is also referred to as history information DB2i.

[0035] FIG. 3C shows an example of the third management data DB3 (also simply referred to as the third data DB3). The third data DB3 shows the correspondence between the part number PNB, the part name PNM, and the durable page count NsU. The part number PNB is identification information of the part of the printer 100. In this embodiment, the part number PNB is an integer starting from 1. The part name PNM is the name of the part. The durable page count NsU is an estimate of the life of the part and is expressed in the number of printed pages. If the number of printed pages from the start of use of the part exceeds the durable page count NsU, it is preferable to replace the part. The durable page count NsU of each part (and thus the third data DB3) is predetermined by the manufacturer of the printer 100. A plurality of parts that can be replaced before lending are registered in the third data DB3 in advance.

[0036] FIG. 3(D) shows an example of the fourth management data DB4 (also simply referred to as the fourth data DB4). The fourth data DB4 shows the correspondence between the printer identifier PID and the first cumulative number of printed pages Np1. The printer identifier PID is identification information of the printer. This printer identifier PID is set as the lending printer identifier PIDx in the first data DB1 (FIG. 3(A)). The first cumulative number of printed pages Np1 is the cumulative value of the number of pages printed using the printer (hereinafter, the first cumulative number of printed pages Np1 is also referred to as the printer cumulative value Np1). The printer cumulative value Np1 is counted without being reset, regardless of whether or not a part of the printer has been replaced.

[0037] 4 shows an example of the fifth management data DB5 (also simply referred to as the fifth data DB5). The fifth data DB5 is data indicating the usage amount of each of a plurality of parts of the printer. The fifth data DB5 indicates the correspondence between the part number PNB, the part name PNM, the second cumulative number of printed pages Np2, the cumulative number of errors Ne, the cumulative number of cleanings Nc, and the replacement flag F.

[0038] The fifth data DB5 includes multiple individual printer data corresponding to multiple printers. Fig. 4 shows an example of the individual printer data DB5Pa in the fifth data DB5 that is associated with the first printer Pa. The individual printer data is a portion of the fifth data DB5 that indicates information about one printer.

[0039] The individual printer data DB5Pa (more generally, the fifth data DB5) has registered therein the same parts as those registered in the third data DB3 (FIG. 3C). The second cumulative number of printed pages Np2 is the cumulative value of the number of pages printed using the corresponding parts (hereinafter, the second cumulative number of printed pages Np2 is also referred to as the part cumulative value Np2). The cumulative number of errors Ne is the cumulative number of errors related to the corresponding parts. The cumulative number of cleanings Nc is the cumulative number of cleanings related to the corresponding parts. The replacement flag F indicates whether or not a replacement condition indicating that a part should be replaced is met. A replacement flag F of "1" indicates that the replacement condition is met, and a replacement flag F of "0" indicates that the replacement condition is not met. Note that the rightward arrow and the numerical value to the right of the arrow in FIG. 4 indicate a change in value due to a part replacement, which will be described later. Np2, Ne, Nc, and F are reset to zero in response to the replacement of the corresponding parts. That is, Np2, Ne, Nc, and F indicate values ​​after the last part replacement.

[0040] As shown in Fig. 4, the fifth data DB5 includes a plurality of parts DP1-DP4. The part usage data DP1 indicates the correspondence between PNB and Np2. The part error data DP2 indicates the correspondence between PNB and Ne. The part cleaning data DP3 indicates the correspondence between PNB and Nc. The part replacement data DP4 indicates the correspondence between PNB and F.

[0041] A-3. Printer information transmission process: Fig. 5 is a flowchart showing an example of the printer information transmission process. The printer information transmission process is a process for registering the usage history of the printer 100 in the management server 500. After the printer 100 is lent to a user, the CPU 110 of the printer 100 starts the process of Fig. 5 in response to the start-up of the printer 100 by the user.

[0042] In S110, the CPU 110 executes a user registration process. The user who borrows the printer 100 inputs his / her user identifier UID (also called the noted user identifier UID) to the printer 100 by operating the operation unit 150. The CPU 110 transmits registration data indicating the noted printer identifier PID, which is the printer identifier PID of the printer 100, and the noted user identifier UID to the management server 500. The CPU 510 of the management server 500 uses the registration data from the printer 100 to update the first data DB1 (FIG. 3(A)). If the noted user identifier UID has already been registered in the first data DB1, the CPU 510 sets the lending printer identifier PIDx associated with the noted user identifier UID to the noted printer identifier PID. If the noted user identifier UID is not registered in the first data DB1, that is, if the user is a new user, the CPU 510 adds the correspondence between the noted user identifier UID and the noted printer identifier PID to the first data DB1.

[0043] Note that user data indicating the noted user identifier UID may be stored in the storage device 115 (e.g., non-volatile storage device 130) of the printer 100 before the printer 100 is handed over to the user. In S110, the CPU 110 of the printer 100 may refer to the user data to obtain the noted user identifier UID. The CPU 110 of the printer 100 may also perform authentication using a password or a secret key to allow the user to use the printer 100.

[0044] After S110, the CPU 110 of the printer 100 repeatedly executes the determination processes of S120, S140, and S160 described below (for example, S120, S140, and S160 are executed multiple times a day).

[0045] In S120, the CPU 110 determines whether the printer 100 has printed since the previous S120. If the determination result in S120 is Yes, in S130, the CPU 110 transmits usage data indicating information regarding the usage history of the printer 100 to the management server 500. In this embodiment, the usage data indicates the noted user identifier UID, the noted printer identifier PID, the number of printed pages, and the year and month of printing. The number of printed pages is the number of pages printed after the previous S120. The usage data may further indicate various information regarding printing, such as the paper size used for printing.

[0046] S135 is a process performed by management server 500 in response to receipt of the usage data. CPU 510 of management server 500 uses the usage data to update second data DB2 (FIG. 3(B)), fourth data DB4 (FIG. 3(D)), and fifth data DB5 (FIG. 4). The specific process is as follows.

[0047] CPU 510 updates the individual user data corresponding to the noted user identifier UID indicated by the usage data in history data DB2 (FIG. 3(B)). Specifically, CPU 510 adds the number of printed pages indicated by the usage data to the number of printed pages NP associated with the rental period PP including the year and month of printing indicated by the usage data. CPU 510 searches for the individual user data corresponding to the noted user identifier UID by referring to first data DB1 (FIG. 3(A)).

[0048] CPU 510 refers to fourth data DB4 (FIG. 3(D)), and adds the number of printed pages indicated by the usage data to first cumulative number of printed pages Np1 associated with the target printer identifier PID indicated by the usage data.

[0049] CPU 510 updates the individual printer data corresponding to the target printer identifier PID indicated by the usage data in fifth data DB5 (FIG. 4). Specifically, CPU 510 adds the number of printed pages indicated by the usage data to part cumulative value Np2 of all parts.

[0050] If the user with the noted user identifier UID has not printed anything, the history data DB2 does not include individual user data corresponding to the noted user identifier UID. In this case, the CPU 510 of the management server 500 generates new individual user data associated with the noted user identifier UID and adds it to the second data DB2. The CPU 510 then sets the history data identifier UDID associated with the noted user identifier UID in the first data DB1 (FIG. 3(A)) as the identifier of the generated individual user data.

[0051] After S130 (FIG. 5), the CPU 110 of the printer 100 proceeds to S140. This proceeding may be performed without waiting for completion of S135, or may be performed after completion of S135. If the printer 100 has not performed printing after the previous S120 (S120: No), the CPU 110 proceeds to S140 without executing S130.

[0052] In S140, CPU 110 determines whether an error has occurred in printer 100 since the previous S140. Printer 100 is configured to detect various errors. For example, rotation sensor 999 of paper feed unit 990 (FIG. 2) is equipped with an encoder and detects the rotation of drive roller 991. When rotation sensor 999 detects that drive roller 991 has stopped rotating during paper feed, the detected rotation stop indicates a paper feed jam error. Although not shown, printer 100 is equipped with a detection device for detecting not only paper feed jams but also various other errors (e.g., laser failure, etc.).

[0053] If the determination result in S140 is Yes, in S150, the CPU 110 transmits error history data indicating information regarding the error to the management server 500. In this embodiment, the error history data indicates the target printer identifier PID, the number of errors that have occurred since the previous S140, and the classification of each error. The classification of the error is determined from a plurality of predetermined classifications according to the content of the error that has occurred. The plurality of error classifications include various classifications such as paper feed jam, laser failure, etc.

[0054] S155 is a process performed by the management server 500 in response to receiving the error history data. The CPU 510 of the management server 500 updates the individual printer data corresponding to the target printer identifier PID indicated by the error history data, among the fifth data DB5 (FIG. 4). Specifically, the CPU 510 adds "1" to the cumulative error count Ne of the part number PNB associated with the error classification for each error. The correspondence between the error classification and the part number PNB is determined in advance. For example, the paper feed unit 990 is associated with a paper feed jam, and the exposure device 903 is associated with a laser failure. Note that two or more part numbers PNB related to one error classification may be associated with that classification.

[0055] After S150 (FIG. 5), the CPU 110 of the printer 100 proceeds to S160. This proceeding may be performed without waiting for completion of S155, or may be performed after completion of S155. If no error has occurred after the previous S140 (S140: No), the CPU 110 proceeds to S160 without executing S150.

[0056] In S160, the CPU 110 judges whether cleaning has been performed after the previous S160. Cleaning is a process for removing foreign matter (e.g., printing material such as toner) attached to parts of the printer 100. The printer 100 may automatically perform cleaning. For example, the CPU 110 cleans the paper feed unit 990 and the fixing unit 906 by transporting paper P without printing. Also, the user may perform cleaning. For example, the user cleans the exposure unit 903 by wiping the exposure unit 903 with a cloth. In this embodiment, cleaning is performed in response to a user's instruction. For example, the user instructs the printer 100 to perform cleaning in response to finding toner stains on a printed matter. Also, the user disassembles the printer 100 and cleans parts such as the exposure unit 903. Alternatively, the CPU 110 may automatically start cleaning. For example, the CPU 110 may periodically perform cleaning (e.g., transporting paper P without printing). When the user cleans a part, the user inputs information indicating the classification of the cleaning by operating the operation unit 150. The classification of the cleaning is determined from a plurality of predetermined classifications according to the contents of the cleaning. The plurality of cleaning classifications include various classifications such as transporting the paper P and wiping the exposure unit 903.

[0057] If the determination result in S160 is Yes, in S170, the CPU 110 transmits cleaning history data indicating information related to cleaning to the management server 500. In this embodiment, the cleaning history data indicates the target printer identifier PID, the number of cleanings performed since the previous S160, and the classification of each cleaning.

[0058] S175 is a process performed by the management server 500 in response to receipt of the cleaning history data. The CPU 510 of the management server 500 updates the individual printer data corresponding to the target printer identifier PID indicated by the cleaning history data, among the fifth data DB5 (FIG. 4). Specifically, the CPU 510 adds "1" to the cumulative cleaning count Nc of the part number PNB associated with the cleaning classification for each cleaning. The correspondence between the cleaning classification and the part number PNB is determined in advance. For example, the paper feed unit 990 and the fixing unit 906 are associated with the transport of the paper P, and the exposure unit 903 is associated with the wiping of the exposure unit 903.

[0059] After S170 (FIG. 5), CPU 110 of printer 100 proceeds to S120. This may be done without waiting for completion of S175, or may be done after completion of S175. If cleaning has not been performed after the previous S160 (S160: No), CPU 110 proceeds to S120 without executing S170. Thereafter, CPU 110 repeats the above-mentioned process. This allows CPU 510 of management server 500 to update data DB1, DB2, DB4, and DB5 to show the latest information.

[0060] A-4. Management Process: FIG. 6 is a flowchart showing an example of the management process. The management process is a process for preparing a target printer, which is a printer to be lent to a user, before lending it out. As described below, the target printer is selected from a plurality of printers available for lending. The plurality of printers available for lending are not limited to new printers, but include printers that have been returned from past lending. If the target printer is a returned printer, each of the plurality of parts of the target printer may be worn out due to past use. In the process of FIG. 6, the management server 500 extracts parts that may cause malfunctions during the new lending period from the plurality of parts included in the target printer. The worker replaces the extracted parts with new parts without replacing the parts that were not extracted.

[0061] In S205, the worker starts the management application by operating the operation unit 350 of the management terminal 300 (FIG. 1). Furthermore, the worker inputs the target user identifier and the planned lending period (also called the planned lending period) into the management application by operating the operation unit 350. The target user identifier is the user identifier UID of the target user who is the user who will borrow the printer (also called the target user identifier UID). The planned lending period is the lending period requested by the target user. In this embodiment, the lending period is a continuous period and is represented by a combination of years and months. The lending period may be a period of two months or more, such as "January to June of 2021". In S207, the CPU 310 transmits start instruction data indicating the target user identifier UID and the planned lending period to the management server 500.

[0062] In S210, the CPU 510 of the management server 500 executes a process for determining the predicted number of pages to be printed in response to the start instruction data. The predicted number of pages to be printed is a predicted value of the number of pages to be printed by the target user during the planned lending period. FIGS. 7 and 8 are flowcharts showing an example of the process for determining the predicted number of pages to be printed. FIG. 8 shows the process continued from FIG. 7.

[0063] In S310, the CPU 510 of the management server 500 refers to the start instruction data and acquires the target user identifier UID and the planned lending period. In S330, the CPU 510 initializes the target month to the first month of the planned lending period, and initializes the candidate page count to zero.

[0064] In S340, the CPU 510 refers to the first data DB1 (FIG. 3(A)) and searches for user history data (e.g., user history data DB2Ua) associated with the target user identifier UID in the history data DB2 (FIG. 3(B)). In S345, the CPU 510 determines whether or not the user history data associated with the target user identifier UID has been detected.

[0065] The fact that the data to be detected is not detected indicates that the past usage history of the target user identifier UID is not detected. In this case (S345: No), in S350, CPU 510 refers to the history data DB2 and acquires the number of printed pages NP in the target month of other users different from the target user identifier UID. In S355, CPU 510 determines the number of added pages to be the average value of the number of printed pages NP in the target month of other users. For example, if the target month is February, CPU 510 refers to the user history data of all other users in the history data DB2 and calculates the average value of the number of printed pages NP in February of all other users. After S355, CPU 510 proceeds to S390 in FIG. 8.

[0066] If the user history data associated with the target user identifier UID is detected (S345: Yes), in S360, the CPU 510 refers to the user history data of the target user identifier UID in the history data DB2 (FIG. 3(B)) and searches for the usage history (specifically, the number of printed pages NP) of the target user identifier UID in the past year. In S365, the CPU 510 judges whether the usage history of the target user identifier UID in the past year and the month of interest has been detected. If the data to be detected is detected (S365: Yes), in S370, the CPU 510 refers to the history data DB2 and acquires the number of printed pages NP of the target user identifier UID in the past year and the month of interest. In S375, the CPU 510 determines the number of added pages to be the average value of the number of printed pages NP of the target user identifier UID in the past year and the month of interest. After S375, the CPU 510 proceeds to S390 in FIG. 8.

[0067] If no usage history for the target user identifier UID in the target month of the past year is detected (S365: No), in S380, CPU 510 refers to history data DB2 (FIG. 3(B)) and acquires the number of printed pages NP for the target user identifier UID over the entire past period. In S385, CPU 510 determines the number of additional pages to be the average number of printed pages NP for the target user identifier UID over the entire past period. After S385, CPU 510 proceeds to S390 in FIG. 8.

[0068] In S390 (FIG. 8), the CPU 510 adds the additional page number to the candidate page number to update the candidate page number. The additional page number is determined in any one of S355, S375, and S385 in FIG. 7. In S400, the CPU 510 adds "1" to the month of interest to update the month of interest. In S410, the CPU 510 judges whether the updated month of interest is within the planned lending period. If the month of interest is within the planned lending period (S410: Yes), the CPU 510 proceeds to S340 in FIG. 7 to execute processing for the new month of interest. If the updated month of interest is outside the planned lending period (S410: No), that is, if processing for all months within the planned lending period has been completed, the CPU 510 proceeds to S420. At this stage, the candidate page number indicates the sum of the additional page numbers for all months within the planned lending period.

[0069] In S420, CPU 510 determines whether the candidate page number is less than the reference page number. The reference page number indicates a guideline for the minimum number of pages that can be printed without any problems. In this embodiment, the reference page number is determined in advance (for example, 1000 pages). If the candidate page number is less than the reference page number (S420: Yes), in S430, CPU 510 determines the predicted print page number as the reference page number, and ends the processing of FIGS. 7 and 8 (i.e., S210 in FIG. 6). If the candidate page number is equal to or greater than the reference page number (S420: No), in S440, CPU 510 determines the predicted print page number as the candidate page number, and ends the processing of FIGS. 7 and 8 (i.e., S210 in FIG. 6).

[0070] An example of the number of additional pages determined in S375 and S385 in FIG. 7 is shown below. Here, the planned lending period is assumed to be "January to June 2021." The user history data DB2Ua in FIG. 3(B) indicates the history of the target user identifier UID. The correspondence between the month of interest, the number of additional pages, and the year and month used to calculate the additional pages is as follows: Month of interest: Number of additional pages: Year and month used for calculation (number of printed pages) 1: 500:January 2018 (500) 2: 400: February 2018 (500), February 2019 (300) 3: 2500: March 2018 (2000), March 2019 (3000) 4: 1500: April 2018 (1000), April 2019 (2000) 5: 500: May 2019 ( 500) 6:1225:All period When the above number of added pages from January to June is used in S440 of FIG. 8, the predicted number of printed pages is the sum of the number of added pages from January to June, which is 6,625 pages.

[0071] In S220 of Fig. 6, the CPU 510 of the management server 500 executes an exchange condition determination process. Fig. 9 and Fig. 10 are flowcharts showing an example of the exchange condition determination process. Fig. 10 shows a continuation of the process in Fig. 9.

[0072] In S520, the CPU 510 of the management server 500 selects a target printer to be lent to the target user from among the multiple printers available for lending. As described below, among the multiple parts of the target printer, parts that satisfy replacement conditions are replaced before the target printer is lent. Therefore, the CPU 510 may randomly select the target printer from among the multiple printers available for lending, without searching for a printer suitable for the target printer from among the multiple printers available for lending.

[0073] The printers available for loan are the remaining printers after removing the printer currently being loaned from all printers available for loan. A list of the identifiers PID of all printers available for loan is determined in advance (also called the all printer list). The identifiers PID of the printer currently being loaned are set to the loaned printer identifiers PIDx in the first data DB1 (FIG. 3(A)). Hereinafter, the printer identifier PID of the target printer selected in S520 is also called the target printer identifier PID.

[0074] In S530, CPU 510 refers to fourth data DB4 (FIG. 3(D)) and acquires printer cumulative value Np1 of the target printer. In S535, CPU 510 judges whether printer cumulative value Np1 of the target printer is equal to or greater than upper limit number Np1U. Upper limit number Np1U is a page number indicating the life of the printer, and is determined in advance. If printer cumulative value Np1 is equal to or greater than upper limit number Np1U (S535: Yes), in S540, CPU 510 executes processing to discard the target printer. For example, CPU 510 deletes the printer identifier PID of the target printer from the all printer list. After S540, CPU 510 proceeds to S520 and selects another printer.

[0075] If the printer cumulative value Np1 is less than the upper limit number Np1U (S535: No), the CPU 510 extracts parts that satisfy a replacement condition indicating that the target printer should be replaced before being lent to the target user (details will be described later). To determine the replacement condition, the CPU 510 refers to the individual printer data (e.g., data DB5Pa) associated with the target printer identifier PID in the fifth data DB5 (FIG. 4). Hereinafter, the individual printer data associated with the target printer identifier PID in the fifth data DB5 is also referred to as the target printer data. In the following description, the data DB5Pa in FIG. 4 is the target printer data (also referred to as the target printer data DB5Pa). In addition, the predicted number of printed pages is assumed to be 6625 pages in the above calculation example.

[0076] At S550 (FIG. 9), CPU 510 initializes the target part number to "1". At S560, CPU 510 references target printer data DB5Pa (FIG. 4) to acquire parameters Np2, Ne, and Nc associated with the target part number. Specifically, CPU 510 references part usage data DP1 to acquire part cumulative value Np2, references part error data DP2 to acquire cumulative error count Ne, and references part cleaning data DP3 to acquire cumulative cleaning count Nc. CPU 510 also references third data DB3 (FIG. 3(C)) to acquire durable page count NsU associated with the target part number.

[0077] In S570, the CPU 510 judges whether the sum Ns of the part cumulative value Np2 and the predicted number of printed pages Npx exceeds the number of useful pages NsU. The sum Ns exceeding the number of useful pages NsU indicates that the first cumulative number of printed pages Np1 of the target part number is likely to exceed the number of useful pages NsU during the planned lending period. If the judgment result in S570 is Yes, the CPU 510 sets the replacement flag F associated with the target part number of the target printer data DB5Pa (FIG. 4) to "1" in S600. After S600, the CPU 510 proceeds to S610 in FIG. 10. For example, in the example in FIG. 4, the sum Ns (41625 pages) of the Np2 (35000 pages) and Npx (6625 pages) of the transfer roller exceeds NsU (40000 pages (FIG. 3(C))). Therefore, the replacement flag F of the transfer roller is set to "1".

[0078] If the determination result in S570 is No, then in S580, the CPU 510 determines whether the cumulative error count Ne exceeds the error threshold NeU. In this embodiment, the error threshold NeU is determined in advance (for example, NeU=10). If the cumulative error count Ne exceeds the threshold NeU, there is a high possibility that the part corresponding to the target part number has a defect. If the determination result in S580 is Yes, then the CPU 510 sets the replacement flag F of the target part number to "1" in S600, and proceeds to S610 (FIG. 10). For example, in the example of FIG. 4, the cumulative error count Ne (11) of the paper feed unit (tray 2) exceeds the threshold NeU (10). Therefore, the replacement flag F of the paper feed unit (tray 2) is set to "1."

[0079] If the determination result in S580 is No, then in S590, the CPU 510 determines whether the cumulative cleaning count Nc exceeds the threshold value NcU. In this embodiment, the threshold value NcU is determined in advance (for example, NcU=10). If the cumulative cleaning count Nc exceeds the threshold value NcU, there is a high possibility that the component corresponding to the target component number is dirty. If the determination result in S590 is Yes, then the CPU 510 sets the replacement flag F of the target component number to "1" in S600, and proceeds to S610 (FIG. 10). For example, in the example of FIG. 4, the cumulative cleaning count Nc (12) of the exposure unit exceeds the threshold value NcU (10). Therefore, the replacement flag F of the exposure unit is set to "1."

[0080] If the determination result in S590 is No, the CPU 510 proceeds to S610 (FIG. 10).

[0081] In S610, CPU 510 adds "1" to the target part number to update the target part number. In S620, CPU 510 determines whether the updated target part number is present in the parts list. The parts list is a list of all parts that are the subject of the exchange condition determination process. In this embodiment, the parts list is a list of multiple parts registered in data DB3, DB5 (FIGS. 3(C) and 4).

[0082] If the target part number is present in the parts list (S620: Yes), CPU 510 proceeds to S560 (FIG. 9) and processes the new target part number. If the target part number is not present in the parts list (S620: No), that is, when processing of all parts is completed, CPU 510 ends the processing in FIGS. 9 and 10 (i.e., S220 in FIG. 6).

[0083] 6, the CPU 510 of the management server 500 generates target part data indicating a list of target parts that satisfy the replacement conditions. In this embodiment, the CPU 510 references the target printer data (e.g., data DB5Pa) in the fifth data DB5 (FIG. 4) and generates, as the target part data, a list of part numbers PNB of parts having a replacement flag F of "1". The CPU 510 then outputs the generated target part data to the management terminal 300. The CPU 310 of the management terminal 300 references the received target part data and displays the list of target parts on the display unit 340 (not shown).

[0084] In S240, the worker confirms the target parts to be replaced by observing the list of target parts displayed on display unit 340. Then, the worker disassembles the target printer and replaces the target parts with new parts.

[0085] In S250, the worker inputs the part number PNB of the replaced part into the management terminal 300 by operating the operation unit 350. In S260, the CPU 310 of the management terminal 300 transmits replacement data indicating the input part number PNB to the management server 500.

[0086] In S270, the CPU 510 of the management server 500 executes post-replacement processing in response to receiving the replacement data. FIG. 11 is a flowchart showing an example of the post-replacement processing. In S710, the CPU 510 acquires the replacement data. In S720, the CPU 510 initializes the target part number to "1". In S725, the CPU 510 refers to the replacement data and searches for the target part number. In S730, the CPU 510 judges whether or not the part corresponding to the target part number has been replaced. If the target part number is searched for from the replacement data, the judgment result in S730 is Yes. In this case, in S740, the CPU 510 updates the target printer data (for example, data DB5Pa) in the fifth data DB5 (FIG. 4). Specifically, the CPU 510 sets the part cumulative value Np2, the cumulative number of errors Ne, the cumulative number of cleanings Nc, and the replacement flag F to "zero" for the target part number. In the example of FIG. 4, the "transfer roller", the "paper feed unit (tray 2)", and the "exposure unit" are replaced. Then, Np2, Ne, Nc, and F of these parts are set to zero. Then, the CPU 510 proceeds to S750.

[0087] If the target part number is not found in the replacement data, that is, if the part corresponding to the target part number has not been replaced (S730: No), the CPU 510 proceeds to S750 without executing S740.

[0088] At S750, CPU 510 adds "1" to the target part number to update the target part number. At S760, CPU 510 determines whether the updated target part number is present in the parts list. The determination condition at S760 is the same as the determination condition at S620 in FIG. 10. If the target part number is present in the parts list (S620: Yes), CPU 510 proceeds to S725 and executes processing of the new target part number. If the target part number is not present in the parts list (S760: No), that is, if processing of all parts has been completed, CPU 510 ends the processing of FIG. 11 (i.e., S270 in FIG. 6). With the above, the processing of FIG. 6 ends.

[0089] As described above, in this embodiment, the CPU 510 of the management server 500 executes the following processing according to the program PG5. At S210 in FIG. 6 (specifically, S350, S370, and S380 in FIG. 7), the CPU 510 refers to the history data DB2 (FIG. 3B). The history data DB2 indicates history information DB2i including the use history of the printer of each of the multiple users. At S210 and S220 in FIG. 6, the CPU 510 uses the history information DB2i and the scheduled lending period to determine whether or not each of the multiple parts included in the target printer satisfies the replacement condition. The replacement condition indicates that the target printer should be replaced before it is lent to the target user. As described above, the CPU 510 can appropriately determine whether or not each of the multiple parts included in the target printer satisfies the replacement condition.

[0090] In S210 of Fig. 6, as described in Fig. 7 and Fig. 8, the CPU 510 determines the predicted number of pages to be printed Npx during the planned lending period using the history information DB2i and the planned lending period. In S220 of Fig. 6, as described in Fig. 9 and Fig. 10, the CPU 510 determines whether the part satisfies the replacement conditions using the predicted number of pages to be printed Npx. By using the predicted number of pages to be printed Npx, the CPU 510 can appropriately determine whether the part satisfies the replacement conditions.

[0091] The first condition C1 in FIG. 7 is a condition that S345: Yes and S365: Yes are satisfied. The first condition C1 indicates that the history information DB2i includes a history of the first type of usage during the same period. In this embodiment, the first type of usage during the same period is the number of pages printed NP by the target user in a month of a past year that is the same as a month of interest included in the scheduled lending period. When the first condition C1 is satisfied (S345: Yes, S365: Yes), as described in S370, S375, S390, and S440 (FIGS. 7 and 8), the CPU 510 uses the first type of usage during the same period to determine the predicted number of pages printed Npx (in this embodiment, the predicted number of pages printed Npx is determined using the average value of the first type of usage during the same period (S375)). It is estimated that the user will print about the same number of pages as the number of pages printed NP during the same month of the past year in the month of interest included in the scheduled lending period. Therefore, the CPU 510 can appropriately determine the predicted number of printed pages Npx by using the first type usage amount for the same period.

[0092] The second condition C2 in FIG. 7 is a condition in which S345: Yes and S365: No are satisfied. The second condition C2 indicates that the history information DB2i does not include the history of the first type usage during the same period, but includes the history of the first type past usage. In this embodiment, the first type past usage is the number of pages NP printed in the past by the target user. When the second condition C2 is satisfied (S345: Yes, S365: No), as described in S380, S385, S390, and S440 (FIGS. 7 and 8), the CPU 510 uses the first type past usage to determine the predicted number of pages Npx to be printed (in this embodiment, the predicted number of pages Npx to be printed is determined using the average value (S385) of the first type past usage). The number of pages NP to be printed may vary greatly among multiple users. In this embodiment, when the second condition C2 is satisfied, the CPU 510 determines the predicted number of pages to be printed Npx for the target user using the number of pages to be printed in the past NP of the target user, not the number of pages to be printed in the past NP of other users different from the target user. Therefore, the CPU 510 can appropriately determine the predicted number of pages to be printed Npx.

[0093] The third condition C3 in FIG. 7 is a condition that results in S345: No. The third condition C3 indicates that the history information DB2i does not include the history of the number of pages printed NP in the past by the target user. In this embodiment, the history data DB2 (FIG. 3(B)) shows the history of the number of pages printed NP for a past period of more than one year for many users. Therefore, the history data DB2 includes the history of the number of pages printed NP by a user other than the target user for any month. Therefore, the third condition C3 indicates that the history information DB2i does not include the history of the number of pages printed NP in the past by the target user, but includes the history of the second type of usage during the same period. In this embodiment, the second type of usage during the same period is the number of pages printed NP by a user other than the target user in a month of a past year that is the same month as the month of interest that is included in the scheduled lending period.

[0094] When the third condition C3 is satisfied (S345: No), as explained in S350, S355, S390, and S440 (FIGS. 7 and 8), the CPU 510 uses the second type usage amount for the same period to determine the predicted number of printed pages Npx (in this embodiment, the predicted number of printed pages Npx is determined using the average value of the second type usage amount for the same period (S355)). The number of printed pages NP can be significantly affected by the month. In the month of interest, the number of printed pages NP is expected to be approximately the same as the number of printed pages NP for the same month of the past year. In this embodiment, when the third condition C3 is satisfied, the CPU 510 determines the predicted number of printed pages Npx using the number of printed pages NP for the same month as the month of interest (i.e., the second type usage amount for the same period), not the number of printed pages NP for a month different from the month of interest. Therefore, the CPU 510 can appropriately determine the predicted number of printed pages Npx.

[0095] As described in S420 and S430 of FIG. 8, when the predicted number of pages to be printed Npx is less than the reference number of pages, the CPU 510 determines the predicted number of pages to be printed Npx as the reference number of pages. When the predicted number of pages to be printed Npx is excessively small, the determination of the replacement conditions performed using the predicted number of pages to be printed Npx may be performed inappropriately. For example, it may be determined that a part that may cause a malfunction during the rental period does not satisfy the replacement conditions. In this embodiment, the CPU 510 can suppress such a determination.

[0096] In S560 of FIG. 9, the CPU 510 refers to the part usage data DP1 (FIG. 4) indicating the part cumulative value Np2 (an example of the cumulative usage of the part) of each of the multiple parts included in the target printer. The replacement condition determination process (FIGS. 9 and 10) includes the processes of S570 and S600. If the condition of S570 is satisfied, the CPU 510 executes S600, that is, determines that the part of the target part number satisfies the replacement condition. The condition of S570 is that, for the target part number, the sum Ns of the part cumulative value Np2 and the predicted number of printed pages Npx associated with the target part number exceeds the number of durable pages NsU associated with the target part number. From the above, the CPU 510 can appropriately determine that the part that may cause a malfunction within the planned lending period satisfies the replacement condition. The predicted number of printed pages Npx is an example of the predicted usage. The number of durable pages NsU is an example of the upper limit usage.

[0097] In S560 of Fig. 9, CPU 510 refers to part error data DP2 (Fig. 4) indicating the cumulative number of errors Ne for each of a plurality of parts included in the target printer. The replacement condition determination process (Figs. 9 and 10) also includes the processes of S580 and S600. If the condition of S580 is satisfied, CPU 510 executes S600, that is, determines that the part with the target part number satisfies the replacement condition. The condition of S580 is that, for the target part number, the cumulative number of errors Ne associated with the target part number exceeds the error threshold NeU. From the above, CPU 510 can appropriately determine that a part that may have a defect satisfies the replacement condition.

[0098] 11, CPU 510 refers to replacement data indicating part number PNB of the replaced part among the multiple parts included in the target printer. Then, in S740, CPU 510 updates both the part cumulative value Np2 and the cumulative error count Ne of the replaced part to zero (thereby updating part usage data DP1 and part error data DP2). Therefore, CPU 510 can appropriately execute the next replacement condition determination process for the target printer by referring to part usage data DP1 and part error data DP2.

[0099] 6, CPU 510 outputs target part data indicating target parts that are determined to satisfy the replacement conditions among multiple parts included in the target printer. The output target part data can be used for various processes such as replacing the target parts. In this embodiment, the target part data is output to management terminal 300. Management terminal 300 refers to the target part data and displays a list of target parts on display unit 340. Therefore, an operator can easily confirm the parts to be replaced by observing display unit 340.

[0100] The CPU 210 of the user terminal 200 may execute various processes for using the printer 100. For example, the CPU 210 may execute a process for registering a user in the management server 500. This function may be realized by the program PG2 or another program.

[0101] B. Second Example: The printer for loan may be an inkjet printer. The printer information transmission process in Fig. 5 and the management process in Fig. 6 are also applicable to inkjet printers.

[0102] 12 is a schematic diagram showing an example of an inkjet type print execution unit 900b. This print execution unit 900b has a print head 410 (also simply called the head 410), a first moving device 430, a second moving device 440, and an ink supply unit 450.

[0103] The first moving device 430 includes a carriage 433, a sliding shaft 434, a belt 435, and a plurality of pulleys 436 and 437. The carriage 433 carries the head 410. The sliding shaft 434 holds the carriage 433 so that it can reciprocate along the main scanning direction (a direction parallel to the Dx direction). The belt 435 is wound around the pulleys 436 and 437, and a portion of the belt 435 is fixed to the carriage 433. The pulley 436 is rotated by the power of a main scanning motor (not shown). When the main scanning motor rotates the pulley 436, the carriage 433 moves along the sliding shaft 434. This realizes main scanning, which moves the head 410 along the main scanning direction relative to the paper P.

[0104] The second moving device 440 includes a platen PT configured to support the paper P, a first transport roller 441 and a second transport roller 442 configured to hold the paper P arranged on the platen PT, and a transport motor (not shown) that drives the rollers 441 and 442. The paper P is supplied to the second moving device 440 from a paper tray (not shown) by a paper feed roller (not shown). The paper P supplied to the second moving device 440 is sandwiched between the first transport roller 441 and a driven roller (not shown) that is paired with the first transport roller 441, and is transported in the sub-scanning direction Dy by these rollers. The transported paper P is sandwiched between the second transport roller 442 and a driven roller (not shown) that is paired with the second transport roller 442, and is transported in the sub-scanning direction Dy by these rollers.

[0105] The ink supply unit 450 includes a cartridge mounting unit 451, a tube 452, and a buffer tank 453. Four ink cartridges KC, YC, CC, and MC for the four colors of KYCM are detachably mounted in the cartridge mounting unit 451. The tube 452 is a flexible pipe that serves as an ink flow path connecting the cartridge mounting unit 451 and the buffer tank 453. The ink in each ink cartridge is supplied to the head 410 via the cartridge mounting unit 451, the tube 452, and the buffer tank 453.

[0106] Although not shown, the print head 410 has four nozzle groups for the four colors of KYCM. The print head 410 forms dots in a band area extending in the main scanning direction on the paper P by ejecting ink droplets from the nozzles during main scanning (also called partial printing). The print execution unit 900b prints an image on the paper P by repeating partial printing and transporting the paper P.

[0107] FIG. 13(A) shows an example of the third data DB3b, and FIG. 13(B) shows an example of the individual printer data DB5bPa of the fifth data DB5b. The parts to be processed in the exchange condition determination process are selected from the multiple parts of the print execution unit 900b (FIG. 12). In the examples of FIG. 13(A) and FIG. 13(B), the print head, the transport roller, and the carriage are the processing targets. The print execution unit 900b is configured to execute a cleaning process in which ink droplets are ejected from multiple nozzles of the print head 410 toward an ink receiving unit (e.g., a sponge) not shown. The cumulative cleaning count Nc of the print head 410 indicates the cumulative number of times this cleaning process has been performed.

[0108] C. Variations:

[0109] (1) The method of determining the predicted number of pages to be printed may be various methods for determining a predicted value of the number of pages to be printed during the planned lending period, instead of the methods in Figures 7 and 8. For example, in S355, S375, and S385 in Figure 7, the number of additional pages may be various values, such as a median or a mode, instead of an average value, calculated according to a predetermined function using one or more numbers of pages to be printed NP.

[0110] When the determination result of S345 in FIG. 7 is No, the CPU 510 may further refer to the history data DB2 (FIG. 3(B)) to search for the number of printed pages NP (i.e., the second type usage during the same period) by other users other than the target user in a month of a past year that is the same month as the month of interest included in the planned lending period. Then, when the second type usage during the same period is searched, the CPU 510 may execute S350 and S355. When the second type usage during the same period is not searched, the CPU 510 may determine the number of added pages by various methods. For example, the CPU 510 refers to the history data DB2 to acquire the number of printed pages NP of other users in the entire past period. Then, the CPU 510 determines the number of added pages using the acquired number of printed pages NP (for example, the average value, median, or mode of the acquired number of printed pages NP). According to this configuration, when the history information DB2i does not include the second type usage during the same period, the CPU 510 can determine an appropriate predicted number of printed pages Npx.

[0111] 7, the CPU 510 may determine the number of additional pages using the number of printed pages NP for the entire period in the past of the other users, regardless of whether the history information DB2i includes the second type usage amount for the same period (for example, the average value, the median value, the most frequent value, etc.). Also, S365, S370, and S375 in FIG. 7 may be omitted. For example, if the determination result in S345 is Yes, the CPU 510 may execute S380 and S385. Also, regardless of whether the history information DB2i (FIG. 3(B)) includes the usage history of the target user, the CPU 510 may determine the number of additional pages using the number of printed pages NP for the entire period of each of multiple users including the target user and other users (for example, the average value, the median value, the most frequent value, etc.). Here, the CPU 510 may use the number of printed pages NP for the target month instead of the entire period.

[0112] In either case, each of the multiple users may be associated with one of multiple categories (e.g., multiple categories corresponding to multiple business types). When using the print page count NP of other users different from the target user, CPU 510 may use the print page count NP of other users included in the same category as the target user, rather than using the print page count NP of other users included in a category different from the category of the target user.

[0113] 8 may be omitted. CPU 510 may use a period of interest of various lengths included in the planned lending period, such as a day of interest or a week of interest, instead of a month of interest, to determine the number of additional pages and, in turn, the predicted number of pages to be printed Npx. The processes in FIGS. 7 and 8 are applicable to various periods of interest.

[0114] (2) The multiple printers for loan may include multiple models of printers. For example, the multiple models of printers for loan may include the following four models: (A) First-class laser type (B) Type 2 laser type (C) First-class inkjet type (D) Type 2 Inkjet A user may borrow a printer of any model among a number of models. The usage history of a target user may include, for example, the usage history of each of the following four printers: (A) First printer (first type laser type) (B) Second printer (first type laser type) (C) 3rd printer (type 2 laser type) (D) 4th printer (Type 1 inkjet type) (The first and second printers are the same type 1 laser printer.)

[0115] Here, the method of recording the printer usage history (FIG. 3(B)) (FIG. 5: S135) may be various methods. The history recording method may be, for example, any of the following three history recording methods. Regardless of which history recording method is adopted, the management process (particularly the process of determining the predicted number of pages to be printed) may be the same as the process in the above embodiment (FIGS. 6-10) or the process in the modified example, except that the history data referenced is different.

[0116] The first history recording method is a method of recording the printer usage history using the history data for each printer model (FIG. 3(B)). The correspondence between the first to fourth printers and the history data used to record the usage history is as follows: (A) First printer (first type laser type): First history data (B) Second printer (first type laser type): First history data (C) 3rd printer (type 2 laser): 2nd history data (D) 4th printer (1st type inkjet type): 3rd history data Since the first printer and the second printer are the same first type laser printer, the CPU 510 records the usage history of the first printer and the usage history of the second printer in a common first history data. The first to third history data do not distinguish between individual printers. The first to third history data are all included in individual user data associated with the same target user. When the target user borrows a new printer, the CPU 510 refers to the history data associated with the model of the printer requested by the target user to determine the predicted number of pages to be printed. The correspondence between examples of printer models and the referenced history data is as follows: (A) First-class laser type: First historical data (B) First-class inkjet type: Third history data (C) Type 2 Inkjet: History data of other users' Type 2 Inkjet Since the individual user data of the target user does not include historical data of the second type inkjet type, the CPU 510 refers to historical data of the second type laser type of other users for the second type inkjet type (FIG. 7: S345: No).

[0117] The second history recording method is a method of recording the usage history of all printers using one common history data. The correspondence between the first to fourth printers and the history data used to record the usage history is as follows: (A) First printer (first type laser type): fourth history data (B) Second printer (first type laser type): fourth history data (C) 3rd printer (type 2 laser): 4th history data (D) 4th printer (1st type inkjet type): 4th history data CPU 510 records the usage history of all printers in a common fourth history data. The fourth history data does not distinguish between individual printers. The fourth history data is included in individual user data associated with the target user. When the target user borrows a new printer, CPU 510 refers to the fourth history data to determine the predicted number of pages to be printed, regardless of the printer model and printing method requested by the target user. The correspondence between examples of printer models and the referenced history data is as follows: (A) First-class laser type: Fourth historical data (B) First-class inkjet type: Fourth historical data (C) Type 2 Inkjet Type: 4th History Data

[0118] The third history recording method is a method of recording the printer usage history using the history data for each printing method of the printer. The correspondence between the above first to fourth printers and the history data used to record the usage history is as follows. (A) First printer (first type laser type): fifth history data (B) Second printer (first type laser type): fifth history data (C) 3rd printer (type 2 laser): 5th history data (D) 4th printer (1st type inkjet type): 6th history data The fifth historical data indicates the usage history of a laser printer, and the sixth historical data indicates the usage history of an inkjet printer. The fifth and sixth historical data do not distinguish between individual printers. The fifth and sixth historical data are both included in individual user data associated with the same target user. When the target user borrows a new printer, the CPU 510 refers to the historical data associated with the printing method of the printer requested by the target user to determine the predicted number of pages to be printed. The correspondence between examples of printer models and the referenced historical data is as follows: (A) First-class laser type: 5th historical data (B) Type 1 Inkjet Type: 6th History Data (C) Type 2 Inkjet Type: 6th History Data

[0119] (3) The exchange conditions are not limited to those shown in Figures 9 and 10, and may be various conditions determined using history information DB2i including the usage history of the printer for each of multiple users and the planned rental period. For example, S580 in Figure 9 may be omitted. In this case, part error data DP2 may be omitted from the fifth data DB5, DB5b (Figures 4, 13(B)). In S740 in Figure 11, the reset of the cumulative error count Ne may be omitted. Also, S590 in Figure 9 may be omitted. In this case, part cleaning data DP3 may be omitted from the fifth data DB5, DB5b. In S740 in Figure 11, the reset of the cumulative cleaning count Nc may be omitted.

[0120] (4) In determining whether the replacement condition is satisfied, various parameters indicating the amount of usage may be used, not limited to the number of printed pages. As the amount of usage, various parameters indicating the amount of printing may be used, such as the "number of printed pages," the "number of times the printing material cartridge has been replaced," the "number of rotations of the roller," the "amount of printing material (ink, toner, etc.) used," and the "operating time of the printer." As the "amount of printing material used," for example, the "total number of printed dots (also called dot count)" may be used.

[0121] In the above embodiment, the predicted number of pages to be printed Npx is common to a plurality of parts and indicates the predicted usage of each of the plurality of parts. The CPU 510 determines the predicted number of pages to be printed Npx in S210 of FIG. 6, thereby determining the predicted usage of each of the plurality of parts.

[0122] Alternatively, the CPU 510 may determine the predicted usage for each part. For example, the number of rotations or the number of printed pages may be used as the usage of a roller such as the drive roller 991 (FIG. 2). The dot count or the cumulative number of cleanings may be used as the usage of the print head 410 (FIG. 12). The cumulative movement distance or the number of printed pages may be used as the usage of the carriage 433. Here, the history information indicated by the history data may indicate the history of the usage of each of the multiple parts. The CPU 510 can determine the predicted usage of each of the multiple parts using such history information and the planned lending period. For example, the CPU 510 may determine the predicted usage of each part by executing the processes of FIGS. 7 and 8 for each part. In the process of S220 in FIG. 6 (for example, S570 in FIG. 9), the CPU 510 uses the predicted usage associated with the target part to determine whether the target part satisfies the replacement condition.

[0123] In this way, CPU 510 may use one predicted usage amount in common for determining replacement conditions for each of a plurality of parts, or alternatively, CPU 510 may use the predicted usage amount in determining replacement conditions for a part associated with the predicted usage amount.

[0124] (5) The parts targeted by the replacement condition determination process (FIG. 6: S220) are not limited to the parts described in FIG. 3(C) and FIG. 13(A), but may be any part included in the printer. Also, containers that contain printing materials such as ink and toner (e.g., developer cartridge 910 (FIG. 2), ink cartridges MC, CC, YC, KC (FIG. 12), etc.) may be replaced according to the determination results of the replacement condition determination process. In this way, various parts included in the printer may be targeted by the replacement condition determination process.

[0125] (6) In S230 of Fig. 6, CPU 510 may output target part data (more generally, target component data indicating target components that satisfy the exchange conditions) to various devices instead of management terminal 300. For example, CPU 510 may output the target component data to storage device 515 (e.g., non-volatile storage device 530) inside management server 500, or to an external storage device connected to management server 500 (in this case, CPU 510 stores the target component data in the storage device). CPU 510 may also output the target component data to a display device such as a liquid crystal display (in this case, CPU 510 causes information indicating the target component to be displayed on the display device).

[0126] (7) In S210 and S220 in FIG. 6 (for example, S340, S350, S370, and S380 in FIG. 7 and S530 and S560 in FIG. 9), the CPU 510 of the management server 500 refers to data by reading at least a portion of the data from the storage area of ​​the nonvolatile storage device 530. For example, in S380 in FIG. 7, the CPU 510 refers to the history data DB2 by reading at least a portion of the history data DB2. The reference of data is not limited to reading data, and may include various other processes. For example, the data DB1-DB5 may be managed by a data management device (for example, a database server) different from the management server 500. The CPU 510 of the management server 500 transmits a query to the database server inquiring about information indicated by the data (for example, the history data DB2). The database server transmits data indicating the information requested by the query to the management server 500. In this manner, the reference of data may be performed by transmitting a query. In this case, in S130, S150, and S170 of FIG. 5, the CPU 110 of the printer 100 transmits data to the database server instead of the management server 500. In S135, S155, and S175, the database server uses the data from the printer 100 to update various data (e.g., data DB2, DB4, DB5, etc.). The function of the database server may be realized by the management server 500. The CPU 510 may operate as a database processing unit by executing a program different from the program PG5. In this case, in S210 and S220 of FIG. 6, the CPU 510 may transmit a query to the database processing unit operating on the management server 500. In general, the "data referencing process" may be various processes for acquiring data indicating at least a part of the information indicated by the data.

[0127] (8) The printer may have various configurations capable of printing images, instead of the configurations of Figures 2 and 12. For example, the printer may be a printer that uses a printing material of one color (e.g., black K). The printer may also be various devices having a print execution unit configured to perform printing. For example, the printer may be a device including a print execution unit and a read execution unit, such as a multifunction device, a copy machine, or a facsimile machine. The read execution unit is a device that optically reads an original document and generates image data of the read original document.

[0128] (9) Instead of the management server 500, various other devices may determine whether or not the printer components satisfy the exchange conditions. For example, the management terminal 300 may execute the processes of S210 and S220 in FIG. 6 instead of the management server 500. Here, the management server 500 may function as a database server that manages data DB1-DB5. The CPU 310 of the management terminal 300 can obtain various information from the management server 500 by sending a query to the management server 500. Also, multiple devices (e.g., computers) that can communicate with each other via a network may share a part of the processing function of determining whether or not the printer components satisfy the exchange conditions, and may provide the processing function as a whole (a system equipped with these devices corresponds to the management device).

[0129] In each of the above embodiments, a part of the configuration realized by hardware may be replaced by software, and conversely, a part or all of the configuration realized by software may be replaced by hardware. For example, the function of the exchange condition determination process (S220) in FIG. 6 may be realized by a dedicated hardware circuit.

[0130] Furthermore, when some or all of the functions of the present invention are realized by a computer program, the program can be provided in a form stored in a computer-readable recording medium (e.g., a non-transitory recording medium). The program can be used in a state stored in the same or a different recording medium (computer-readable recording medium) from when it was provided. The "computer-readable recording medium" is not limited to portable recording media such as memory cards and CD-ROMs, but may also include internal storage devices within a computer, such as various ROMs, and external storage devices connected to a computer, such as a hard disk drive.

[0131] The present invention has been described above based on examples and modifications, but the above-described embodiments of the invention are intended to facilitate understanding of the present invention and are not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit of the invention, and equivalents thereof are included in the present invention. [Explanation of symbols]

[0132] 100... printer, 102... body, 104... paper output tray, 110... CPU, 115... storage device, 120... volatile storage device, 130... non-volatile storage device, 140... display unit, 150... operation unit, 180... communication interface, 200... user terminal, 210... CPU, 215... storage device, 220... volatile storage device, 230... non-volatile storage device, 240... display unit, 250... operation unit, 280... communication interface, 300... management terminal, 310... CPU, 3 15...storage device, 320...volatile storage device, 330...non-volatile storage device, 340...display unit, 350...operation unit, 380...communication interface, 410...print head, 414...head drive unit, 430...second movement device, 433...carriage, 434...sliding shaft, 435...belt, 436...pulley, 440...first movement device, 441...first conveyor roller, 442...second conveyor roller, 450...ink supply unit, 451...cartridge mounting unit, 452...tube, 45 3...buffer tank, 490...control unit, 500...management server, 510...CPU, 515...storage device, 520...volatile storage device, 530...non-volatile storage device, 580...communication interface, 900, 900b...print execution unit, 903...scanner unit (exposure device), 904...process unit, 905...transfer unit, 906...fixing unit, 907...photosensitive drum, 908...scorotron type charger, 909...drum cleaning roller, 910...development Cartridge, 911...developing roller, 912...supply roller, 913...driving roller, 914...driven roller, 915...conveyor belt, 916...transfer roller, 917...heating roller, 918...pressure roller, 990...paper feed unit, 991...driving roller, 992...driven roller, 999...rotation sensor, PT...platen, 1000...system, P...paper, MC, CC, YC, KC...ink cartridge, LN...local area network, IT...Internet

Claims

1. A computer program for managing a rental printer, comprising: a first reference function for referencing history data indicating history information including the use history of each of a plurality of users of the printer; a determination function that uses the history information and the scheduled rental period to determine whether or not each of a plurality of components included in the target printer to be rented to the target user satisfies an exchange condition indicating that the component should be exchanged before the target printer is rented to the target user; This is realized on a computer. The judgment function is determining a projected usage amount for the planned rental period using the historical information and the planned rental period; a condition determination process for determining whether a component included in the plurality of components satisfies the replacement condition using the predicted usage amount; A computer program that executes

2. 2. A computer program according to claim 1, comprising: The determination process includes, when a first condition is satisfied indicating that the history information includes a history of a first type of concurrent usage amount, which is a usage amount by the target user during a period of a past year that is the same as a period of interest that is included in the scheduled rental period, determining the predicted usage amount using the first type of concurrent usage amount. Computer program.

3. A computer program according to claim 1 or 2, The determination process includes a process of determining the predicted usage amount using the first type of past usage amount when a second condition is satisfied, which indicates that the history information does not include a history of a first type of usage amount for the same period, which is a usage amount by the target user during a period of a past year that is the same as a period of interest that is included in the scheduled rental period, but includes a history of a first type of past usage amount, which is a past usage amount by the target user. Computer program.

4. A computer program according to any one of claims 1 to 3, The determination process includes, when a third condition is satisfied, indicating that the history information does not include a history of past usage by the target user, but includes a history of a second type of concurrent period usage, which is a usage by a user different from the target user during a period of a past year that is the same as a period of interest that is included in the scheduled rental period, determining the predicted usage using the second type of concurrent period usage. Computer program.

5. A computer program according to any one of claims 1 to 4, the determination process includes a process of determining, when the predicted usage amount is less than a reference usage amount, the predicted usage amount as the reference usage amount. Computer program.

6. A computer program according to any one of claims 1 to 5, further comprising: a second reference function for referencing component usage data indicating an accumulated usage amount of each of the plurality of components included in the target printer; the condition determination process includes a process of determining that a first attention component included in the plurality of components satisfies the replacement condition when a sum of the accumulated usage amount and the predicted usage amount of the first attention component exceeds an upper limit usage amount associated with the first attention component, Computer program.

7. 7. A computer program as claimed in claim 6, further comprising: a third reference function for referencing member error data indicating a cumulative number of errors of each of the plurality of members included in the target printer; the condition determination process includes a process of determining that a second attention component included in the plurality of components satisfies the replacement condition when the cumulative number of errors of the second attention component exceeds an error threshold value, A computer program that causes the computer to realize the above.

8. 8. A computer program as claimed in claim 7, further comprising: a fourth reference function for referring to replacement data indicating a replaced component among the plurality of components included in the target printer; an updating function for updating both the accumulated usage amount of the replaced component and the accumulated number of errors to zero; A computer program that causes the computer to realize the above.

9. A computer program according to any one of claims 1 to 8, further comprising: causing the computer to realize an output function of outputting target component data indicating target components that are determined to satisfy the exchange condition among the plurality of components included in the target printer; Computer program.

10. A computer program for managing a rental printer, comprising: a first reference function for referencing history data indicating history information including the use history of each of a plurality of users of the printer; a determination function that uses the history information and the scheduled rental period to determine whether or not each of a plurality of components included in the target printer to be rented to the target user satisfies an exchange condition indicating that the component should be exchanged before the target printer is rented to the target user; an output function for outputting target component data indicating target components that are determined to satisfy the replacement condition among the plurality of components included in the target printer; A computer program that enables a computer to realize the above.

11. A method for managing a rental printer, comprising: a first reference step of referring to history data indicating history information including the use history of the printer of each of a plurality of users; a determination step of determining, for each of a plurality of components included in the target printer to be lent to the target user, whether or not the component satisfies an exchange condition indicating that the component should be exchanged before the target printer is lent to the target user, using the history information and a scheduled lending period; an output step of outputting target component data indicating target components that are components determined to satisfy the exchange condition among the plurality of components included in the target printer; A management method comprising:

12. A management device for managing rental printers, a first reference unit that references history data indicating history information including the use history of the printer of each of a plurality of users; a determination unit that determines, for each of a plurality of components included in a target printer to be lent to a target user, whether or not the component satisfies an exchange condition indicating that the component should be exchanged before the target printer is lent to the target user, using the history information and a scheduled lending period; an output unit that outputs target component data indicating target components that are determined to satisfy the replacement condition among the plurality of components included in the target printer; A management device comprising:

Images