System and Method

Abstract

This aims to prevent equipment using a component from becoming unusable before the scheduled maintenance date, when the expected end date of a component's lifespan is earlier than the scheduled maintenance date. [Solution] The system comprises a calculation means for calculating the expected end date of the lifespan of a component included in the target device based on internal information; a maintenance date setting means for setting a scheduled maintenance date for the component; and an execution means for remotely executing instructions to adjust parameters in the target device to prevent errors related to the lifespan of the component until the scheduled maintenance date, if the expected end date calculated by the calculation means is earlier than the scheduled maintenance date set for the component by the maintenance date setting means.

Description

Technical Field

[0001] The present invention relates to a system and a method.

Background Art

[0002] There is a technology for identifying the state related to the lifespan of equipment, such as signs of failure of equipment such as image forming devices. Patent Document 1 discloses a technology for determining the magnitude of the failure risk of a target device after determining that it is in a failure warning state and notifying the determination result. [[ID=I3]]

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, when calculating the expected date of reaching the lifespan of parts included in equipment and setting the scheduled maintenance date of parts, there are cases where the expected date of reaching the lifespan of parts is earlier than the scheduled maintenance date of parts. In this case, if the equipment using the parts becomes unusable until the scheduled maintenance date of the parts, it will be inconvenient for the user of the equipment. An object of the present invention is to suppress the situation where the equipment using the parts becomes unusable until the scheduled maintenance date when the expected date of reaching the lifespan of the parts is earlier than the scheduled maintenance date of the parts.

Means for Solving the Problems

[0005] To solve the above problems, the present invention provides a system comprising: information acquisition means for acquiring internal information of a target device; calculation means for calculating an estimated date for the end of life of a component included in the target device based on the internal information; maintenance date setting means for setting a scheduled maintenance date for the component; and execution means for remotely executing instructions for parameter adjustment in the target device so as not to cause errors related to the life of the component until the scheduled maintenance date, if the estimated date for the end of life calculated by the calculation means is earlier than the scheduled maintenance date set for the component by the maintenance date setting means. [Effects of the Invention]

[0006] According to the present invention, when the expected end date of a component's lifespan is earlier than the scheduled maintenance date for that component, it is possible to prevent the equipment using the component from becoming unusable before the scheduled maintenance date. [Brief explanation of the drawing]

[0007] [Figure 1] This is an overall diagram of the management system. [Figure 2] This is a diagram showing the hardware configuration of the device. [Figure 2-2] This diagram shows the server's hardware configuration. [Figure 3] This diagram shows the functional configuration of the server. [Figure 4] This sequence diagram shows the flow of processing performed by the equipment, the lifespan calculation server, the adjustment management server, the schedule management server, and the administrator. [Figure 5] This is a diagram showing the job submission screen. [Figure 6] This is a flowchart illustrating the flow of the device execution process. [Figure 7] This is a diagram showing the contents of the relationship table. [Figure 8] This is a flowchart illustrating the flow of the adjustment process. [Figure 9] This is a diagram showing the adjustment request screen. [Figure 10] It is a flowchart showing the flow of adjustment execution processing. [Figure 11] It is a diagram showing the scheduled date reception screen. [Figure 12] It is a flowchart showing the flow of scheduled execution processing. [Figure 13] It is a flowchart showing the flow of scheduled date request processing. [Figure 14] It is a diagram showing the scheduled mail screen. [Figure 15] It is a flowchart showing the flow of adjustment instruction processing. [Figure 16] It is a diagram showing the adjustment mail screen. [Figure 17] It is a flowchart showing the flow of adjustment processing. [Figure 18] It is a flowchart showing the flow of adjustment processing. [Figure 19] It is a flowchart showing the flow of adjustment instruction processing. [Figure 20] It is a flowchart showing the flow of scheduled date request processing. [Figure 21] It is a diagram showing the adjustment mail screen. [Figure 22] It is a diagram showing the scheduled mail screen.

Embodiments for Carrying Out the Invention

[0008] Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is an overall configuration diagram of the management system 1. The management system 1 as an example of the system is a system that manages a device by adjusting parameters set in the device regarding the operation of a component so that the device using the component can be used until the day when the component included in the device is scheduled to be maintained. Hereinafter, the day when the component is scheduled to be maintained may be referred to as the maintenance scheduled date. Management system 1 comprises equipment 100, a lifespan calculation server 400, an adjustment management server 500, and a schedule management server 600. Equipment 100, the lifespan calculation server 400, the adjustment management server 500, and the schedule management server 600 are connected via a network 700.

[0009] Device 100, as an example of a target device, is a device managed by management system 1. Hereinafter, device 100 is assumed to be a multifunction peripheral (MFP) with functions such as printing, faxing, copying, scanning, and data transmission. However, device 100 is not limited to image forming apparatus such as a multifunction device, and may be a device other than an image forming apparatus. The device 100 of this embodiment is equipped with a plurality of components (not shown) and a sensor (not shown) that periodically detects the state of each component. Examples of component states detected by the sensor include the component's temperature, the voltage applied to the component, and the number of times the component has operated. Each time the sensor detects the state of a component, the device 100 transmits device information, which is information about the device 100, to the lifespan calculation server 400. This device information includes state information indicating the state detected by the sensor of the device 100, and identification information that identifies the device 100. The state information can also be considered as internal information, which is information about the inside of the device 100.

[0010] Device 100 transmits device information, including untransmitted status information, to the lifespan calculation server 400 at predetermined intervals. The predetermined interval can be any time, but for example, it is one hour. The frequency and timing of device 100's transmission of device information may be set by operations on the device 100's administrator's touch panel 107 or by operations on a terminal (not shown) held by the administrator. Furthermore, the status information can be in any format, such as CSV (Comma Separated Values), XML (Extensible Markup Language), or JSON (JavaScript Object Notation). The status information is also used to calculate the expected date when the components of device 100 will reach the end of their lifespan, and to detect signs of failure in the components of device 100, as will be described later. Therefore, the status information does not have to be the information generated by the sensor of device 100 itself, as long as it contains information that enables the calculation of lifespan and the detection of signs of failure. Furthermore, the identification information for device 100 may be any information that can identify device 100, such as the serial number of device 100.

[0011] In the illustrated example, the management system 1 is equipped with three devices 100, but it is not limited to this. The number of devices 100 equipped in the management system 1 can be any number, as long as there is one or more.

[0012] The lifespan calculation server 400 uses the status information contained in the equipment information obtained from the equipment 100 to calculate the expected date on which the components of equipment 100 will reach the end of their lifespan. The expected date on which the components of equipment 100 will reach the end of their lifespan may be referred to as the expected lifespan end date below. Furthermore, if the expected lifespan end date of a component is earlier than the scheduled maintenance date for that component, the lifespan calculation server 400 instructs the administrator of equipment 100 to adjust the parameters set for the operation of the component in the equipment.

[0013] The adjustment management server 500 manages the parameters of the equipment 100, which is the target of adjustment by the management system 1. Furthermore, when the lifespan calculation server 400 is instructed to adjust the parameters of equipment 100, the adjustment management server 500 accepts the settings for the parameter adjustments made by the administrator. The adjustment management server 500 then transmits the accepted settings as an adjustment instruction to equipment 100, causing equipment 100 to adjust its parameters.

[0014] The schedule management server 600 manages the scheduled maintenance dates for parts. The schedule management server 600 accepts settings for the scheduled maintenance dates of parts from the administrator. In addition, when the schedule management server 600 receives a request from the lifespan calculation server 400 for information indicating the scheduled maintenance dates of parts, it sends the requested information to the lifespan calculation server 400. The information indicating the scheduled maintenance dates of parts may be referred to as scheduled date information below.

[0015] The lifespan calculation server 400, the adjustment management server 500, and the schedule management server 600 may be configured on a single computer or implemented through distributed processing by multiple computers. Furthermore, the lifespan calculation server 400, the adjustment management server 500, and the schedule management server 600 may be implemented on virtual hardware provided by cloud computing.

[0016] Network 700 is not particularly limited in type, as long as it is capable of transmitting and receiving data. Examples of Network 700 include the Internet, LAN (Local Area Network), WAN (Wide Area Network), telephone lines, dedicated digital lines, ATM and frame relay lines, cable television lines, and wireless lines for data broadcasting. Furthermore, the communication lines used for transmitting and receiving data may be wired or wireless.

[0017] Figure 2 shows the hardware configuration of device 100. Device 100 includes a CPU 101, RAM 102, ROM 103, input control I / F 104, display control I / F 105, and storage device I / F 106. Device 100 also includes a touch panel 107, display 108, storage device 109, scanner 110, printer 111, and communication I / F controller 113. The CPU 101, RAM 102, ROM 103, input control I / F 104, display control I / F 105, storage device I / F 106, and communication I / F controller 113 are each connected via a bus 112.

[0018] The CPU (Central Processing Unit) 101 controls the entire device 100. The RAM (Random Access Memory) 102 is a volatile memory and is used as the CPU 101's main memory, work area, and other temporary storage areas. The ROM (Read Only Memory) 103 is a non-volatile memory and stores images, other data, and various programs for the CPU 101 to operate in predetermined areas. The CPU 101 controls various parts of the device 100, for example, by using the RAM 102 as work memory according to a program stored in the ROM 103. Note that the program for the CPU 101 to operate is not limited to being stored in the ROM 103, but may also be stored in the storage device 109. The communication I / F controller 113 communicates with external devices via the network 700 based on the control of the CPU 101. The input control I / F 104 receives information input from the user's operation of the device 100, generates control signals according to the operation, and transmits the generated control signals to the CPU 101. This allows the CPU 101 to be controlled based on control signals, enabling the device 100 to operate in response to user input. Examples of input control interfaces 104 include a mouse, keyboard, and hard keys. The touch panel 107 is an input device that outputs coordinate information corresponding to the position on the screen where the user touches it. This touch panel 107 may also be used as the input control interface 104. The display control interface 105 outputs display signals to the display 108 for displaying images. Based on the display control signals generated by the CPU 101, the display control interface 105 may display a GUI screen constituting a GUI (Graphical User Interface) on the display 108. The touch panel 107 may be integrated with the display 108. A storage device 109, such as an HDD (Hard Disk Drive) or flash memory, is connected to the storage device interface 106. The storage device 109 reads and writes data based on the control of the CPU 101. The storage device 109 may be used instead of RAM 102 or ROM 103.

[0019] The scanner 110 reads the document and generates image data based on the control of the CPU 101. The scanner 110 also stores the generated image data in the storage device 109 via the storage device interface 106. The printer 111 prints the image data stored in the storage device 109 based on the control of the CPU 101. The components managed by the management system 1 of this embodiment include components used in the scanner 110 and components used in the printer 111. When the scanner 110 or printer 111 is in operation, counter information, which indicates the number of times the components used in the scanner 110 or printer 111 have been operated, is updated. The updated counter information, in other words, the number of times the components have been operated, is detected by a sensor (not shown) of the aforementioned device 100.

[0020] Figure 2-2 shows the hardware configuration of the lifespan calculation server 400, the adjustment management server 500, and the scheduling management server 600. Note that when explaining the lifespan calculation server 400, the adjustment management server 500, and the scheduling management server 600 without specific distinction, they may simply be referred to as "servers." The server comprises a CPU 701, RAM 702, ROM 703, input control I / F 704, display control I / F 705, storage device I / F 706, touch panel 707, display 708, storage device 709, and communication I / F controller 713. The CPU 701, RAM 702, ROM 703, input control I / F 704, display control I / F 705, storage device I / F 706, and communication I / F controller 713 are each connected via a bus 712.

[0021] The CPU 701 controls the entire server. RAM 702 is volatile memory and is used as the CPU 701's main memory, work area, and other temporary storage areas. ROM 703 is non-volatile memory and stores images, other data, and various programs for the CPU 701 to operate in predetermined areas. The CPU 701 controls various parts of the server, for example, by using RAM 702 as work memory according to a program stored in ROM 703. Note that the program for the CPU 701 to operate is not limited to being stored in ROM 703, but may also be stored in the storage device 709. The communication I / F controller 713 communicates with external devices via the network 700 based on the control of the CPU 701. The input control I / F 704 receives information input from user operations on the server, generates control signals corresponding to the operations, and transmits the generated control signals to the CPU 701. This allows the CPU 701 to be controlled based on the control signals, realizing server operation in response to user operations. Examples of input control I / F 704 include a mouse, keyboard, and hard keys. The touch panel 707 is an input device that outputs coordinate information corresponding to the position on the screen that is touched by the user. This touch panel 707 may be used as the input control I / F 704. The display control I / F 705 outputs a display signal to the display 708 for displaying an image. The display control I / F 705 may display a GUI screen that constitutes the GUI on the display 708 based on the display control signal generated by the CPU 701. The touch panel 707 may be provided as an integral part of the display 708. A storage device 709, such as an HDD or flash memory, is connected to the storage device I / F 706. The storage device 709 reads and writes data based on the control of the CPU 701. The storage device 709 may be used instead of RAM 702 or ROM 703.

[0022] Figure 3 shows the functional configuration of the server. The lifespan calculation server 400 includes a transmitting / receiving unit 401, a storage unit 402, a calculation unit 403, a detection unit 404, and a control unit 405. As an example of an information acquisition means, the transmitting / receiving unit 401 transmits and receives information to and from an external device. For example, the transmitting / receiving unit 401 receives device information from device 100. The memory unit 402 stores information such as device information. As an example of a calculation method, the calculation unit 403 calculates the estimated end date of the lifespan of the components of the equipment 100 using the state information contained in the equipment information acquired from the equipment 100. The calculation unit 403 may use any method for calculating the estimated end date of the component's lifespan, such as a calculation method based on predetermined rules or a calculation method based on machine learning results. The information indicating the estimated end date of the component's lifespan calculated by the calculation unit 403 is stored in the storage unit 402. The calculation unit 403 calculates the estimated end date for each piece of equipment 100 and each component. Furthermore, the calculation unit 403 may calculate the estimated end date of the component's lifespan for each piece of state information contained in the equipment information each time equipment information is acquired. Also, the calculation unit 403 may calculate the estimated end date of the component's lifespan for each piece of state information not used in the calculation at predetermined intervals. The predetermined interval can be any time, but for example, it could be 1 hour.

[0023] The detection unit 404 detects signs of failure in the components of the equipment 100. The detection unit 404 may also detect signs of failure from the expected end date of the component's lifespan, such as detecting whether the expected end date of the component's lifespan is before a predetermined period from the present. Alternatively, the detection unit 404 may detect signs of failure from status information. When the detection unit 404 detects signs of failure in a component, it notifies the control unit 405 of the detection result. The detection unit 404 detects signs of failure in each component of the equipment 100. The detection unit 404 may also detect signs of failure in a component each time the expected end date of the component's lifespan is calculated by the calculation unit 403. Alternatively, the detection unit 404 may detect signs of failure in a component at predetermined intervals. The predetermined interval can be any time, but for example, it may be 1 hour. As an example of an execution method, the control unit 405, when the detection unit 404 detects signs of failure in a component, obtains scheduled date information from the scheduled management server 600 and compares the scheduled maintenance date of the component identified from the obtained scheduled date information with the expected end date of the component's lifespan. If the expected end date of the component's lifespan is earlier than the scheduled maintenance date of the component, the control unit 405 instructs the administrator to adjust the parameters set in the equipment regarding the operation of the component.

[0024] The transmitting / receiving unit 401 is implemented by the communication I / F controller 713. The storage unit 402 is implemented by the RAM 702, ROM 703, and storage device 709. The calculation unit 403, detection unit 404, and control unit 405 are implemented by the CPU 701 loading a program stored in the ROM 703 or storage device 709 into the RAM 702 and executing it. Alternatively, an application may be provided on the lifespan calculation server 400, and the functions of the calculation unit 403, detection unit 404, and control unit 405 may be realized by the operation of this application.

[0025] The adjustment management server 500 includes a transmitting / receiving unit 501, a storage unit 502, and a control unit 503. The transmitting / receiving unit 501 transmits and receives information to and from external devices. For example, the transmitting / receiving unit 501 transmits information to the lifespan calculation server 400 indicating the parameters of the equipment to be adjusted so that the equipment using this part can be used by the scheduled maintenance date of the part. The information indicating the parameters of the equipment 100 to be adjusted so that the equipment using this part can be used by the scheduled maintenance date of the part may be referred to as adjustment information below. The transmitting / receiving unit 501 also transmits information to the equipment 100 indicating the settings set by the administrator as adjustments to the parameters of the equipment 100. The memory unit 502 stores information such as adjustment information for each component. The contents of the information stored in the memory unit 502 will be described in detail later. When the control unit 503 receives a request for adjustment information from the lifespan calculation server 400, it transmits the adjustment information stored in the storage unit 502 to the lifespan calculation server 400 via the transmission / reception unit 501. The control unit 503 also accepts the settings of the parameter adjustments for the device 100 from the administrator and transmits the received settings as an adjustment instruction to the device 100 via the transmission / reception unit 501, thereby causing the device 100 to adjust its parameters.

[0026] The transmitting / receiving unit 501 is implemented by the communication I / F controller 713. The storage unit 502 is implemented by the RAM 702, ROM 703, and storage device 709. The control unit 503 is implemented by the CPU 701 loading a program stored in the ROM 703 or storage device 709 into the RAM 702 and executing it. Alternatively, an application may be provided on the adjustment management server 500, and the functions of the control unit 503 may be realized by the operation of this application.

[0027] The schedule management server 600 includes a transmitting / receiving unit 601, a storage unit 602, and a control unit 603. The transmitting / receiving unit 601 transmits and receives information to and from external devices. For example, the transmitting / receiving unit 601 transmits scheduled date information to the lifespan calculation server 400. The memory unit 602 stores information such as the scheduled date. As an example of a means for setting maintenance dates, the control unit 603 accepts the setting of the maintenance schedule date for a part by the administrator, sets the maintenance schedule date, and generates the schedule date information. Furthermore, when the control unit 603 receives a request for the schedule date information from the lifespan calculation server 400, it transmits the schedule date information to the lifespan calculation server 400 via the transmission / reception unit 601 in accordance with the request.

[0028] The transmitting / receiving unit 601 is implemented by the communication I / F controller 713. The storage unit 602 is implemented by the RAM 702, ROM 703, and storage device 709. The control unit 603 is implemented by the CPU 701 loading a program stored in the ROM 703 or storage device 709 into the RAM 702 and executing it. Alternatively, an application may be provided on the schedule management server 600, and the functions of the control unit 603 may be realized through the operation of this application.

[0029] Figure 4 is a sequence diagram showing the flow of processing performed by the device 100, the lifespan calculation server 400, the adjustment management server 500, the schedule management server 600, and the administrator. First, device 100 transmits device information, including status information that has not yet been transmitted, to the lifespan calculation server 400 (step 301, which may be referred to as "S" below). The control unit 405 of the lifespan calculation server 400 calculates the estimated date on which the component will reach the end of its lifespan based on the equipment information transmitted from the equipment 100 (S302). The detection unit 404 of the lifespan calculation server 400 detects signs of failure in a component (S303). In the following, it is assumed that no maintenance schedule has been set for the component for which signs of failure have been detected in the detection unit 404. If the detection unit 404 detects signs of failure in a component, the control unit 405 of the lifespan calculation server 400 requests scheduled date information from the administrator (S304). In this case, the control unit 405 sends information to the administrator's terminal (not shown) to instruct the administrator to set a scheduled maintenance date for the component.

[0030] The administrator sets the maintenance schedule for the parts by operating the administrator's terminal (not shown) (S305). The settings made by the administrator are notified to the schedule management server 600 from the administrator's terminal (not shown). The control unit 603 of the schedule management server 600 receives the setting of the maintenance schedule date for the parts by the administrator and generates the schedule date information, then sends the generated schedule date information to the lifespan calculation server 400 (S306). The lifespan calculation server 400 compares the estimated lifespan of the component calculated in step 302 with the scheduled maintenance date of the component sent from the schedule management server 600 in step 306 (S307). Hereafter, it is assumed that the estimated lifespan of the component is earlier than the scheduled maintenance date of the component. The component that is the subject of comparison in step 307 may be referred to as the comparison component below.

[0031] The control unit 405 of the lifespan calculation server 400 requests adjustment information related to the comparison target component from the adjustment management server 500 (S308). Hereinafter, it is assumed that the adjustment information corresponding to the comparison target component is stored in the storage unit 502 of the adjustment management server 500. The adjustment management server 500 transmits the adjustment information stored in the memory unit 502, which corresponds to the comparison target component, to the lifespan calculation server 400 (S309). The control unit 405 of the lifespan calculation server 400 instructs the administrator to adjust the parameters set in the equipment regarding the operation of the comparison component (S310). In this case, the control unit 405 sends information to the administrator's terminal (not shown) to instruct the administrator to adjust the parameters.

[0032] The administrator sets the parameters configured on the equipment regarding the operation of the comparison component by operating the administrator's terminal (not shown) (S311). The settings made by the administrator are notified to the adjustment management server 500 from the administrator's terminal (not shown). When the control unit 503 of the adjustment management server 500 receives the setting of parameter adjustments from the administrator, it transmits information indicating the received content to the device 100, thereby instructing the device 100 to adjust the parameters according to the content set by the administrator (S312). When the device 100 adjusts its parameters in response to instructions from the adjustment management server 500, it sends information indicating the adjustments to the adjustment management server 500 (S313). When the control unit 503 of the adjustment management server 500 acquires information indicating the parameter adjustments made by the device 100 via the transmitting / receiving unit 501, it transmits the acquired information indicating the adjustments to the administrator's terminal (not shown) via the transmitting / receiving unit 501 (S314).

[0033] Figure 5 shows the job reception screen 800. The job reception screen 800 is a screen that receives job instructions from the user to the device 100. The job reception screen 800 is displayed on the display 108 of the device 100. The job reception screen 800 displays a reception unit 801 for each job. When a reception unit 801 is selected by the user, the job corresponding to the selected reception unit 801 is executed.

[0034] Figure 6 is a flowchart showing the flow of the device execution process. The device execution process is a process performed in device 100. In this embodiment, the device execution process starts when the execution conditions defined for device 100 are met. The execution conditions are three: reaching the time for transmitting device information, receiving instructions from the adjustment management server 500 to adjust the parameters of device 100, and selecting the reception unit 801 on the job reception screen 800 (see Figure 5). When any of these three execution conditions are met, the device execution process starts. Device 100 determines whether or not the time for transmitting device information has been reached (S401). When the time for transmitting device information is reached (Yes in S401), device 100 transmits device information, including any untransmitted status information, to the lifespan calculation server 400 (S402). The process in step 402 is the same as the process in step 303 in Figure 4.

[0035] Furthermore, if the time for transmitting the device information has not yet arrived (No in S401), the device 100 determines whether or not it has received instructions for parameter adjustment from the adjustment management server 500 (S403). When device 100 receives instructions for parameter adjustment from the adjustment management server 500, it adjusts the parameters according to the instructions (S404). More specifically, device 100 changes the set parameters to the values ​​indicated in the instructions. When the device 100 adjusts the parameters, it sends information indicating the adjustments to the adjustment management server 500 (S405). The process in step 405 is the same as the process in step 313 in Figure 4.

[0036] If device 100 has not received instructions for parameter adjustment from the adjustment management server 500 (No in S403), the selection of the reception unit 801 on the job reception screen 800 means that the execution conditions have been met. In this case, device 100 executes the processing corresponding to the selected reception unit 801 (S406). The device 100 updates counter information indicating the number of times the components used in the process performed in step 406 have been operated (S407). The sensor (not shown) of device 100 detects the state of a component, such as the number of times the component has been operated, and generates state information (S408).

[0037] Figure 7 shows the contents of the relationship table. The relationship table shows the relationship between the components included in the equipment 100 and the parameters of the equipment 100 that are subject to adjustment when the expected end date of the component's lifespan is earlier than the scheduled maintenance date for the component. The relationship table is stored in the storage unit 502 of the adjustment management server 500. The relationship table shows "parts," "adjustment details," "settings," and "concerns." More specifically, the relationship table shows the "adjustment details," "settings," and "concerns" associated with each "part."

[0038] The term "parts" indicates the parts included in the device 100 that are subject to adjustment. The "Adjustment Details" section shows the adjustments made by changing the parameters. The "Setting Value" column shows the setting value as the change to the parameter. The "Adjustment Details" column in the relationship table mentioned above shows the adjustments made when the parameter of device 100 is changed to the "Setting Value". The "Concerns" section outlines concerns regarding the operation of the "Component" when the parameters of device 100 are changed to the "Settings".

[0039] In this embodiment, the "adjustment content" when the parameters of the device 100 are changed to the "set value" is the adjustment content to suppress the occurrence of a fatal error related to the "part" before the scheduled maintenance date of the "part". Furthermore, the "adjustment content" to suppress the occurrence of a fatal error related to the "part" includes the "adjustment content" to suppress the occurrence of a fatal error related to the "part" after it has reached the end of its lifespan, and the "adjustment content" to extend the day on which the "part" reaches the end of its lifespan. Examples of "adjustment content" to suppress the occurrence of a fatal error related to the "part" include "operation settings after the K cartridge lifespan is reached" for the "K cartridge" and "operation settings after the CMY cartridge lifespan is reached" for the "CMY cartridge". Examples of "adjustment content" to extend the day on which the "part" reaches the end of its lifespan include "reducing the stapleless stapling pressure" for the "stapleless stapling unit". More specifically, the "adjustment content" to extend the day on which the "part" reaches the end of its lifespan includes the "adjustment content" shown in the relationship table, excluding the "adjustment content" to suppress the occurrence of a fatal error related to the "part" after it has reached the end of its lifespan. Furthermore, adjustments made to suppress the occurrence of critical errors related to parts can also be seen as adjustments made to suppress wear and tear on those parts.

[0040] Furthermore, the "Adjustment Details" associated with "Fixing Belt" in the relational table show "Attachment / Detachment of Heating Uniform Belt (52-81)", "Attachment / Detachment of Heating Uniform Belt (82-105)", and "Attachment / Detachment of Heating Uniform Belt (106~)". Here, "Attachment / Detachment of Heating Uniform Belt (52-81)" refers to a basis weight of 52 g / m². 2 More than 81g / m 2The following refers to the attachment and detachment of the heat distribution belt when the paper specified below is used for printing. Furthermore, "attachment and detachment of the heat distribution belt (82-105)" refers to a basis weight of 82 g / m². 2 More than 105g / m 2 The following refers to the attachment and detachment of the heat distribution belt when the paper specified below is used for printing. Furthermore, "attachment and detachment of the heat distribution belt (106~)" refers to a basis weight of 106 g / m². 2 This refers to the attachment and detachment of the heat distribution belt when the paper described above is used for printing.

[0041] Furthermore, in this embodiment, when the lifespan calculation server 400 detects signs of failure in a specific component, the adjustment management server 500 receives a request from the lifespan calculation server 400 for adjustment information targeting that specific component. In this case, the adjustment management server 500 determines whether or not adjustment information targeting the specific component exists by checking whether or not the requested component is shown in the "Components" column of the relationship table. If the specific component is shown in the "Components" column of the relationship table, the adjustment management server 500 sends the "Components," "Adjustment Details," "Setting Values," and "Concerns" related to the specific component to the lifespan calculation server 400 as adjustment information for that specific component.

[0042] Figure 8 is a flowchart showing the flow of the adjustment process. The adjustment process is a process in which the lifespan calculation server 400 instructs the adjustment of parameters of the equipment 100. In this embodiment, the adjustment process is started at predetermined intervals. The predetermined interval can be any time, but for example, it is 1 hour. The adjustment process is performed for each piece of equipment 100 installed in the management system 1. The control unit 405 of the lifespan calculation server 400 determines whether or not there are any components that have been detected by the detection unit 404 as showing signs of failure (S601). If there are no components that have been detected by the detection unit 404 as showing signs of failure (No in S601), the adjustment process ends.

[0043] Furthermore, if the detection unit 404 detects any components showing signs of failure (Yes in S601), the process proceeds to the next step. The control unit 405 determines whether any of the components showing signs of failure have not yet undergone the determination in step 606 (described later) regarding the latest estimated lifespan date calculated by the calculation unit 403 (S602). If the determination in step 606 has been performed for the latest estimated lifespan date for any of the components showing signs of failure (No in S602), the adjustment process ends. Furthermore, if there is a component among those in which signs of failure have been detected that has not yet undergone the determination in step 606 regarding its latest estimated lifespan (Yes in S602), the process proceeds to the next step. The control unit 405 determines that one component among those in which signs of failure have been detected that has not yet undergone the determination in step 606 regarding its latest estimated lifespan will be the component to be determined (S603). The component determined to be the component to be determined in step 603 may be referred to as the component to be determined below.

[0044] The control unit 405 determines whether or not there is scheduled date information indicating the scheduled maintenance date for the component to be judged (S604). The control unit 405 requests scheduled date information for the component to be judged from the scheduled management server 600, and makes the determination in step 604 based on whether or not the requested scheduled date information exists in the scheduled management server 600. If no scheduled date information exists for the component to be evaluated (No in S604), the control unit 405 requests scheduled date information from the schedule management server 600 (S605). The process in step 605 is the same as the process in step 304 in Figure 4. That is, after this process, the administrator sets the scheduled maintenance date for the component, and scheduled date information indicating the set scheduled maintenance date is generated in the schedule management server 600.

[0045] Furthermore, if scheduled date information exists for the component to be evaluated (Yes in S604), the control unit 405 obtains the scheduled date information for the component to be evaluated from the schedule management server 600. The control unit 405 then determines whether the latest estimated end date of the component to be evaluated is earlier than the scheduled maintenance date for the component to be evaluated (S606). If the latest estimated end date of the component to be judged is earlier than the scheduled maintenance date of the component to be judged (Yes in S606), the control unit 405 determines whether or not it is possible to adjust the parameters of the equipment 100 related to the component to be judged (S607). The control unit 405 requests adjustment information related to the component to be judged from the adjustment management server 500, and makes the determination in step 607 depending on whether or not the requested adjustment information exists in the adjustment management server 500.

[0046] If adjustment information for the component to be judged exists in the adjustment management server 500 (Yes in S607), the control unit 405 acquires the adjustment information for the component to be judged and performs adjustment instruction processing (S608). As will be described in detail later, this adjustment instruction processing instructs the administrator to adjust the parameters of the equipment 100 related to the component to be judged. Furthermore, if adjustment information for the component to be judged does not exist in the adjustment management server 500 (No in S607), the control unit 405 performs a scheduled date request process (S609). As will be explained in detail later, this scheduled date request process requests the administrator to adjust the scheduled maintenance date for the component to be judged.

[0047] If the estimated end date of the component to be judged is earlier than the scheduled maintenance date of the component to be judged (No in S606), the process proceeds to the next step after step 608 or after step 609. The control unit 405 determines whether the latest estimated end date of any component for which signs of failure have been detected has been determined in step 606 (S610). If, among the components in which signs of failure have been detected, there are any components for which the latest estimated lifespan end date has not yet been determined in step 606 (indicated as No in S610), the process from step 603 is repeated. In other words, until the latest estimated lifespan end date of any component in which signs of failure have been detected is determined in step 606, the process from step 603 to step 609 is performed for each undetermined component. Furthermore, if any component showing signs of failure has been determined in step 606 regarding its latest estimated lifespan (Yes in S610), the adjustment process is terminated.

[0048] Furthermore, after steps 603 to 609 have been performed on a specific component in which signs of failure have been detected, if new status information is generated for this specific component, the equipment information including the new status information is transmitted from the equipment 100 to the lifespan calculation server 400. In this case, the calculation unit 403 of the lifespan calculation server 400 calculates a new estimated lifespan date from the status information included in the new equipment information. However, the newly calculated estimated lifespan date has not been subjected to any judgment in the adjustment process. Therefore, in the next adjustment process, steps 603 to 609 are performed on the newly calculated estimated lifespan date provided by the calculation unit 403. In other words, for a component in which signs of failure have been detected, the adjustment process is performed on the newly calculated estimated lifespan date each time a new estimated lifespan date is calculated.

[0049] Figure 9 shows the adjustment request screen 900. The adjustment request screen 900 is a screen that accepts settings from the administrator for the adjustment details of the parameters of the device 100. In this embodiment, the adjustment management server 500 uses a relationship table to display the adjustment request screen 900 on the administrator's terminal (not shown). However, the adjustment management server 500 may also display the adjustment request screen 900 on the display 108 of the adjustment management server 500. The adjustment request screen 900 displays a customer display section 901, an equipment display section 902, a component display image 905, and an adjustment display section 906.

[0050] The customer display unit 901 shows information identifying the user who is a customer of the equipment 100 for which parameter settings can be accepted on the adjustment acceptance screen 900. The device display unit 902 shows information identifying the device 100 for which parameter settings can be accepted on the adjustment acceptance screen 900. The component display image 905 shows information about the component that is adjusted by the parameter settings of the device 100. The component display image 905 shows a component display section 903 for each component that is adjusted by the parameter settings of the device 100. The component display section 903 shows the name of the component, the estimated date on which the component's lifespan will end, and the scheduled maintenance date for the component.

[0051] The adjustment display unit 906 shows the adjustment details for the parameters of the device 100. The adjustment display unit 906 is also shown for each component. Each adjustment display unit 906 shows the component name, target parameter, and setting value. In the illustrated example, the component whose information is shown in the upper component display unit 903 corresponds to the component whose information is shown in the upper adjustment display unit 906 of the two adjustment display units 906. Similarly, the component whose information is shown in the lower component display unit 903 corresponds to the component whose information is shown in the lower adjustment display unit 906 of the two adjustment display units 906. The component name, target parameter, and setting value in the adjustment display unit 906 correspond to the "component," "adjustment details," and "setting value" information in the relationship table (see Figure 7), respectively. When the control unit 503 of the adjustment management server 500 receives an instruction from the lifespan calculation server 400 to adjust the parameters of the equipment 100, it displays the information from the relationship table related to the instructed part as adjustment information on the adjustment display unit 906. Furthermore, the parts on which information is displayed as part display unit 903 and adjustment display unit 906 are parts on which adjustment instruction processing (see step 608 in Figure 8) is performed during the adjustment process. In other words, the parts on which information is displayed as part display unit 903 and adjustment display unit 906 are parts on which the expected end date of life is earlier than the scheduled maintenance date and on which adjustment information exists.

[0052] Furthermore, the adjustment display unit 906 shows the individual reception unit 908. When the individual reception unit 908 is selected by the administrator, the settings for the parameter adjustments of the device 100 shown on the adjustment display unit 906 targeting the selected individual reception unit 908 are received by the control unit 503 of the adjustment management server 500. Furthermore, the adjustment request screen 900 displays the batch request unit 910. When the batch request unit 910 is selected by the administrator, the settings for the parameter adjustments for each component shown on the adjustment display unit 906 displayed on the adjustment request screen 900 are all accepted by the control unit 503.

[0053] In addition, there may be multiple parameters that are candidates for adjustment for a single component of the device 100. In this case, history information indicating the user's usage history of the device 100 is generated in the device 100, and the device information periodically transmitted from the device 100 may include this history information. Then, depending on the usage status of the device 100 identified from this history information, the parameter to be adjusted from among the multiple parameters of the device 100 related to a single component may be determined. In this case, the acquisition of device information and the determination of the parameter according to the usage status of the device 100 may be performed by the control unit 405 of the lifespan calculation server 400, or by the control unit 503 of the adjustment management server 500. An example of a method for determining the parameters to be adjusted according to the usage status of equipment 100 is described below. The control unit 405 of the lifespan calculation server 400 sends a request for adjustment information related to the "fixing belt" along with the equipment information to the adjustment management server 500. The control unit 503 of the adjustment management server 500 uses the history information included in the acquired equipment information to determine the usage status of equipment 100 by the user, and determines that the basis weight is 82 g / m². 2 More than 105g / m 2The following describes the situation in which printing is being performed using a specific type of paper. In this case, the control unit 503 determines the parameters of the equipment 100 that will have the greatest effect from adjustment, based on the identified usage situation, to be the target of adjustment. More specifically, the control unit 503 transmits "Attachment / Detachment of Heating Belt (82-105)" from the relationship table, and the "Parts," "Setting Values," and "Concerns" associated with this "Adjustment Details," as adjustment information to the lifespan calculation server 400. The control unit 405 of the lifespan calculation server 400 then instructs the adjustment of the parameters identified from the adjustment information obtained from the adjustment management server 500. Furthermore, the control unit 503 of the adjustment management server 500 displays "Attachment / Detachment of Heating Belt (82-105)" and the "Parts" and "Setting Values" associated with this "Adjustment Details" on the adjustment display unit 906 of the adjustment reception screen 900 as the adjustment details set for the administrator.

[0054] Figure 10 is a flowchart showing the flow of the adjustment execution process. The adjustment execution process is performed by the adjustment management server 500. In this embodiment, the adjustment execution process is started when the execution conditions defined in the adjustment management server 500 are met. The execution conditions are three: the display of the adjustment reception screen 900 is instructed, adjustment information is requested, and the adjustment of the parameters of the equipment 100 is instructed. When any of these three execution conditions is met, the adjustment execution process is started. The control unit 503 of the adjustment management server 500 determines whether or not there has been an instruction to display the adjustment request screen 900 (S801). The control unit 503 makes the determination in step 801 based on whether or not the administrator has instructed the administrator to display the adjustment request screen 900 through an operation on the administrator's terminal (not shown) or the adjustment management server 500. If there has been an instruction to display the adjustment request screen 900 (Yes in S801), the control unit 503 displays the adjustment request screen 900 (S802).

[0055] Furthermore, if there is no instruction to display the adjustment request screen 900 (No in S801), the control unit 503 determines whether or not adjustment information has been requested from the lifespan calculation server 400 (S803). If adjustment information has been requested (Yes in S803), the control unit 503 sends the adjustment information related to the requested part to the lifespan calculation server 400 (S804). Furthermore, if no adjustment information is requested (No in S803), it means that the execution conditions have been met because the administrator has selected the individual reception unit 908 or the batch reception unit 910 on the adjustment reception screen 900 (see Figure 9) and instructed the device 100 to adjust its parameters. In this case, the control unit 503 instructs the device 100 to adjust its parameters according to the settings set by the administrator by sending information indicating the parameter adjustment details set by the administrator to the device 100 (S805).

[0056] Figure 11 shows the scheduled date reception screen 1100. The scheduled date reception screen 1100 is a screen that accepts settings from the administrator for the scheduled maintenance date of a part. In this embodiment, the schedule management server 600 displays the scheduled date reception screen 1100 on the administrator's terminal (not shown). However, the schedule management server 600 may also display the scheduled date reception screen 1100 on the display 108 of the schedule management server 600. The scheduled date reception screen 1100 displays a customer display section 1101, an equipment display section 1102, a component display image 1105, a setting section 1106, a batch setting section 1108, and a reception section 1107.

[0057] The customer display unit 1101 shows information identifying the user who is a customer of the equipment 100 for which the scheduled maintenance date can be set on the scheduled date acceptance screen 1100. The device display unit 1102 shows information identifying the device 100 for which the scheduled maintenance date can be set on the scheduled date acceptance screen 1100. The part display image 1105 shows information about the parts for which a maintenance schedule has been set. The part display image 1105 shows a part display section 1103 for each part for which a maintenance schedule has been set. The part display section 1103 shows the name of the part, the estimated date on which the part's lifespan will end, and the scheduled maintenance date for the part. However, the part display section 1103 does not show a scheduled maintenance date for parts for which no maintenance schedule has been set.

[0058] The setting unit 1106 accepts input for the scheduled maintenance date. The setting unit 1106 is shown for each component. In the illustrated example, the component for which information is displayed in the upper component display unit 1103 of the two component display units 1103 corresponds to the component for which information is displayed in the upper setting unit 1106 of the two setting units 1106. Similarly, the component for which information is displayed in the lower component display unit 1103 of the two component display units 1103 corresponds to the component for which information is displayed in the lower setting unit 1106 of the two setting units 1106. In the illustrated example, the upper component display unit 1103 in the diagram has the scheduled maintenance date entered, while the lower component display unit 1103 does not have the scheduled maintenance date entered.

[0059] The batch setting unit 1108 accepts input instructions for batch setting of maintenance schedule dates. Reception desk 1107 accepts requests to set maintenance schedules. In the illustrated example, the batch setting unit 1108 is not selected, and the reception unit 1107 is selected. In this case, the maintenance schedule for the part corresponding to the upper part display unit 1103 of the two part display units 1103 (stapleless binding unit) is received by the control unit 603 of the schedule management server 600. On the other hand, the maintenance schedule for the part corresponding to the lower part display unit 1103 of the two part display units 1103 (paper feed solenoid) is not set. Furthermore, in the illustrated example, if the batch setting unit 1108 is selected and the reception unit 1107 is selected, the control unit 603 receives a batch setting of the maintenance schedule dates for the parts corresponding to each of the two part display units 1103.

[0060] Figure 12 is a flowchart showing the flow of the scheduled execution process. The scheduled execution process is performed by the schedule management server 600. In this embodiment, the scheduled execution process starts when the execution conditions defined in the schedule management server 600 are met. The execution conditions are three: a request for scheduled date information, an instruction to display the scheduled date reception screen 1100, and an instruction to set a maintenance scheduled date. When any of these three execution conditions are met, the scheduled execution process starts. The control unit 603 of the schedule management server 600 determines whether or not it has received a request for scheduled date information from the lifespan calculation server 400 (S1001). If scheduled date information is requested (Yes in S1001), the control unit 603 sends the scheduled date information for the requested part to the lifespan calculation server 400 (S1002).

[0061] Furthermore, if no scheduled date information is requested (No in S1001), the control unit 603 determines whether or not there has been an instruction to display the scheduled date reception screen 1100 (S1003). The control unit 603 makes the determination in step 1003 based on whether or not the administrator has instructed the administrator to display the scheduled date reception screen 1100 through an operation on the administrator's terminal (not shown) or the schedule management server 600. If there has been an instruction to display the scheduled date reception screen 1100 (Yes in S1103), the control unit 603 displays the scheduled date reception screen 1100 (S1104). Furthermore, if there is no instruction to display the scheduled date reception screen 1100 (No in S1003), it means that the execution conditions have been met because the administrator selected the reception unit 1107 on the scheduled date reception screen 1100 (see Figure 11) and instructed the setting of the maintenance schedule. In this case, the control unit 603 determines the maintenance schedule for each instructed part according to the instructions (S1105).

[0062] Figure 13 is a flowchart showing the flow of the scheduled date request process (see S609 in Figure 8). The scheduled date request process is a process in which the lifespan calculation server 400 requests the administrator to adjust the scheduled maintenance date for the parts. The control unit 405 of the lifespan calculation server 400 obtains the email address of the person in charge (administrator) who is scheduled to maintain the equipment 100 on the scheduled maintenance date (S1201). In this embodiment, the storage unit 402 stores the email address of each person in charge. The control unit 405 includes the URL of the scheduled date reception screen 1100 in the email body (S1202). The control unit 405 includes a message in the email body requesting adjustment of the maintenance schedule (S1203). The control unit 405 sends an email to the email address obtained in step 1201 (S1204).

[0063] Figure 14 shows the scheduled email screen 1300. The scheduled email screen 1300 is a screen that shows the content of the email sent from the lifespan calculation server 400 when the scheduled date request process (see Figure 13) is executed. The scheduled email screen 1300 shows the subject section 1301, the recipient section 1302, and the body section 1303. The subject line 1301 shows the subject of the email. In the example shown, the subject line 1301 shows the text "Request for Adjustment of Maintenance Schedule" and the identification information of the equipment 100 whose maintenance schedule is to be adjusted. The recipient field 1302 shows the email address of the person in charge.

[0064] Section 1303 of the main text contains text indicating that the maintenance schedule needs to be adjusted, and the URL for the schedule request screen 1100. Section 1303 also contains the text "Please adjust the maintenance schedule using the following URL," which indicates a request for adjustment of the maintenance schedule. If a URL is selected in the main text section 1303, or if a URL is entered in the main text section 1303, the scheduled date confirmation screen 1100 will be displayed.

[0065] Figure 15 is a flowchart showing the flow of the adjustment instruction process (see S608 in Figure 8). The adjustment instruction process is the process in which the lifespan calculation server 400 instructs the administrator to adjust the parameters of the equipment 100. The control unit 405 of the lifespan calculation server 400 obtains the email address of the person in charge (administrator) of the equipment 100 whose parameters are to be adjusted from the storage unit 402 (S1401). The control unit 405 includes the URL of the adjustment request screen 900 in the email body (S1402). The control unit 405 includes a message in the email body instructing the adjustment of the parameters of the device 100 (S1403). The control unit 405 sends an email to the email address obtained in step 1401 (S1404).

[0066] Figure 16 shows the adjustment email screen 1500. The adjustment email screen 1500 is a screen that displays the content of the email sent from the lifespan calculation server 400 when the adjustment instruction process (see Figure 15) is executed. The adjustment email screen 1500 shows the subject section 1501, the recipient section 1502, and the body section 1503. The subject line 1501 shows the subject of the email. In the illustrated example, the subject line 1501 shows the text "Parameter Adjustment Instructions" and the identification information of the device 100 whose parameters are to be adjusted. The recipient field 1502 shows the email address of the person in charge.

[0067] Section 1503 of the main text shows text indicating that the parameters of device 100 need to be adjusted, and the URL of the adjustment request screen 900. Section 1503 also shows the text "Please adjust the parameters from the following URL," which indicates instructions for adjusting the parameters of device 100. If a URL is selected in the main text section 1503, or if a URL is entered in the main text section 1503, the adjustment request screen 900 will be displayed.

[0068] As described above, in this embodiment, the estimated date of reaching the end of the lifespan calculated by the calculation unit 403 of the lifespan calculation server 400 may be earlier than the scheduled maintenance date set for the component by the control unit 603 of the schedule management server 600. In this case, the control unit 405 of the lifespan calculation server 400 remotely issues instructions to adjust parameters in the device 100 to prevent errors related to the component's lifespan until the scheduled maintenance date. One example of adjusting parameters to prevent errors related to the component's lifespan until the scheduled maintenance date is by setting the "setting values" shown in the relationship table in the device 100. Another example of remote execution of adjustment instructions is the instruction to the administrator by the control unit 405 of the lifespan calculation server 400, or the instruction to the device 100 by the control unit 503 of the adjustment management server 500. In this case, the parameters of the device 100 are adjusted based on the instructions, which prevents errors related to the lifespan of the parts from occurring before the scheduled maintenance date. Therefore, if the expected end date of the part's lifespan is earlier than the scheduled maintenance date for the part, it is prevented that the device 100 using the part will become unusable before the scheduled maintenance date.

[0069] Furthermore, even if the estimated end date of a particular component is after the scheduled maintenance date, there are certain cases in which the estimated end date of that component may subsequently become earlier than the scheduled maintenance date. One such case is when, after the estimated end date of a particular component was after the scheduled maintenance date, the wear and tear on the component increases due to increased usage of the equipment 100, resulting in a newly calculated estimated end date earlier than the scheduled maintenance date. Another specific case is when, after the estimated end date of a particular component was after the scheduled maintenance date, the scheduled maintenance date is delayed due to reasons such as the administrator's convenience or the inability to procure the replacement component in time for maintenance. Even in such cases, as described above, in this embodiment, the estimated end date of the component for which signs of failure have been detected is updated, and each time the estimated end date is updated, an adjustment process (see Figure 8) is performed on the latest estimated end date. Therefore, even if the estimated lifespan or scheduled maintenance date is changed, if this change causes the estimated lifespan of a component to be earlier than the scheduled maintenance date, the parameters of the equipment 100 will be instructed to be adjusted. Thus, even if the estimated lifespan or scheduled maintenance date is changed, the situation in which the equipment using the component becomes unusable before the scheduled maintenance date due to the estimated lifespan of the component being earlier than the scheduled maintenance date is suppressed.

[0070] Furthermore, in this embodiment, the parameter adjustments instructed by the control unit 405 are adjustments related to the operation of components when components are used in conjunction with the operation of the device 100. As adjustments related to the operation of components when components are used in conjunction with the operation of the device 100, the adjustments made when the parameters of the device 100 are set to the "set values" in the relational table include each "adjustment content" associated with the "set values". Specifically, each "adjustment content" includes setting the operation after the K cartridge life is reached, setting the operation after the CMY cartridge life is reached, reducing the stapleless binding pressure of the stapleless binding unit, and turning the flying start temperature control in the fuser ON or OFF. In addition, each "adjustment content" includes setting the standby mode duration in the fuser film or pressure roller, setting the contact or separation distance of the rollers, attaching or detaching the heat distribution belt in the fuser belt, and setting the dark area target potential in the C, M, Y, or Bk photosensitive drums. In addition, each "adjustment content" includes the automatic refresh level of the fuser belt in the fuser refresh roller or the pressure roller in the pressure roller, and the setting (frequency) of the fuser belt refresh in the fuser refresh roller. Furthermore, each "adjustment setting" includes the setting for the number of times the blade holder is used on the cutting blade holder. In this case, even if parts are used in conjunction with the operation of equipment 100 until the scheduled maintenance date, the occurrence of errors related to the lifespan of the parts before the scheduled maintenance date is suppressed.

[0071] Furthermore, in this embodiment, the device 100 includes multiple components, and each of these components has a parameter associated with it that is to be adjusted in the device 100 (see Figure 7). The control unit 405 of the lifespan calculation server 400 then executes an instruction to adjust the parameter associated with the component whose expected lifespan is earlier than the scheduled maintenance date. In this case, the administrator does not need to decide which parameter to adjust in the device 100. However, the administrator may determine which parameter to adjust to in device 100 by performing an operation on the administrator's terminal (not shown) or server, and the adjustment of the determined parameter may be performed in device 100.

[0072] Furthermore, in this embodiment, it was explained that when there are multiple parameters that are candidates for adjustment of a device 100 relating to a single component, the parameter of the device 100 that will have the greatest effect from the adjustment may be determined to be the target of adjustment, taking into account the usage status of the device 100. That is, when there are multiple parameters related to suppressing the occurrence of errors related to the lifespan of a component, the control unit 405 executes an instruction to adjust one of the multiple parameters according to the history information. In this case, by taking into account the usage trends of equipment 100, it is possible to suppress the occurrence of errors related to the lifespan of parts before the scheduled maintenance date.

[0073] (Variation 1) Next, a modified example of management system 1 (modified example 1) will be described. In this embodiment, it has been explained that if the expected end date of a component's lifespan is earlier than the scheduled maintenance date for that component, the device 100's parameters are instructed to be adjusted, but this is not limited to this. Figure 17 is a flowchart showing the flow of the adjustment process as an example of modification 1. Note that steps 1701 to 1705 in the adjustment process as Modification Example 1 are the same as steps 601 to 605 in the adjustment process shown in Figure 8.

[0074] If scheduled date information exists for the component to be judged (Yes in S1704), the control unit 405 determines whether or not it is possible to adjust the parameters of the equipment 100 related to the component to be judged (S1706). The process in step 1706 is the same as the process in step 607 in the adjustment process shown in Figure 8. Depending on the result of the process in step 1706, either an adjustment instruction process (S1707) or a scheduled date request process (S1708) is performed. The processes in steps 1707 and 1708 are the same as the processes in steps 608 and 609 in the adjustment process shown in Figure 8. In other words, in Modification 1, adjustment instruction processing or scheduled date request processing is performed regardless of whether the expected date of reaching the end of the part's lifespan is earlier than the scheduled maintenance date for the part. Furthermore, the process in step 1709 of the adjustment process, as shown in Modification 1, is the same as the process in step 610 of the adjustment process shown in Figure 8.

[0075] Furthermore, the control unit 405 of the lifespan calculation server 400 may perform adjustment instruction processing or scheduled date request processing if the user's usage of the equipment 100 is in a specific situation, regardless of whether the estimated date of the component's lifespan ending is earlier than the scheduled maintenance date for the component. Examples of specific situations include usage conditions in which, when the parameters of the equipment 100 are adjusted, the "concerns" shown in the relational table as concerns arising from the adjustment are less likely to occur.

[0076] This section describes an example of when the user's usage of device 100 is instructed to adjust the parameters of device 100. Device 100 periodically transmits device information, including history information showing the user's usage history, to the lifespan calculation server 400. Upon receiving the device information, the lifespan calculation server 400 identifies the usage status of device 100 from the history information included in the device information. The control unit 405 then determines whether the identified situation is such that adjustments to the parameters of a component showing signs of failure are unlikely to cause "concerns" as a result of the adjustments. If the control unit 405 determines that adjustments are unlikely to cause "concerns," it instructs the adjustment of the parameters of device 100 related to the component, regardless of whether the expected end date of the component's lifespan is before the scheduled maintenance date for the component. For example, the control unit 405 identifies from the history information a situation in which the number of sheets of paper bound into the stapleless binding unit tends to be less than or equal to a predetermined number, as a usage status for the stapleless binding unit, which is a component in which signs of failure have been detected. The predetermined number of sheets can be any number, but for example, it may be 5 sheets. In this case, the control unit 405 determines that the "concern" of "reduction in the number of sheets that can be bound," which occurs when the parameter adjustment of the equipment 100 related to the stapleless binding unit, "reduction in stapleless binding pressure," is performed, is unlikely to occur based on the user's usage. In this case, the control unit 405 instructs the adjustment of the parameters of the equipment 100 related to the stapleless binding unit, regardless of whether the expected end date of the stapleless binding unit is before the scheduled maintenance date for this stapleless binding unit. Furthermore, for example, the control unit 405 identifies from the history information that paper with low adhesive properties is being used for feeding the "paper feed roller," which is a component where signs of failure have been detected. In this case, the control unit 405 determines that the "concern" of "the risk of overlapping paper feeding with paper that has frayed edges or paper with adhesive properties," which occurs when the "contact / separation setting," a parameter adjustment for the equipment 100 related to the "paper feed roller," is made, is unlikely to occur. In this case, the control unit 405 instructs the adjustment of the parameters of the equipment 100 related to the paper feed roller, regardless of whether the expected end date of the paper feed roller's lifespan is before the scheduled maintenance date for the paper feed roller.

[0077] As described above, in this embodiment, there are cases where certain conditions are met regarding the relationship between the usage status of the equipment 100 identified from the history information and the parameters to be adjusted in the equipment 100. In this case, the control unit 405 of the lifespan calculation server 400 executes an instruction to adjust the parameters even if the expected lifespan is after the scheduled maintenance date. The conditions include the fact that the usage status of the equipment 100 identified from the history information is such that, if the parameters related to the component for which signs of failure have been detected are adjusted, it is unlikely that any "concerns" will arise as a result of the adjustment. In this case, by taking into account the usage status of the device 100 and the relationship between the parameters to be adjusted in the device 100, it is possible to suppress the occurrence of errors related to the lifespan of the components.

[0078] Furthermore, the conditions defined regarding the relationship between the usage status of device 100 identified from the historical information and the parameters to be adjusted in device 100 are not limited to the above example. The "Concerns" column in the relationship table may indicate concerns that are unlikely to occur even if the parameters of equipment 100 are adjusted under specific usage conditions identified from the historical information. Furthermore, the relationship table may associate a "part" where signs of failure have been detected with a predetermined "concern" that is unlikely to occur even if the parameters of equipment 100 are adjusted under usage conditions identified from the historical information. In this case, the control unit 405 of the lifespan calculation server 400 may instruct the adjustment of the parameters associated with the unlikely "concern," regardless of whether the expected lifespan end date of this "part" is before the scheduled maintenance date. In this case, the fact that the relationship table associates a "part" where signs of failure have been detected with a predetermined "concern" that is unlikely to occur even if the parameters of equipment 100 are adjusted under usage conditions identified from the historical information is just one example of a condition.

[0079] (Modification 2) Next, we will explain a modified version of management system 1 (modified version 2). Figure 18 is a flowchart showing the flow of the adjustment process as a modified example 2. Furthermore, steps 1801 to 1806 in the adjustment process, which is an example of modified example 2, are the same as steps 601 to 606 in the adjustment process shown in Figure 8. If the latest estimated end date of the component to be judged is earlier than the scheduled maintenance date of the component to be judged (Yes in S1806), proceed to the next step. The control unit 405 determines whether the scheduled maintenance dates for multiple components, including the component to be judged, are set to the same day (S1807). The control unit 405 makes the determination in step 1807 by obtaining scheduled date information for each component included in the device 100 from the schedule management server 600. Furthermore, regardless of whether the reception unit 1107 is selected when the batch setting unit 1108 on the scheduled date reception screen 1100 is selected, if the scheduled maintenance dates for multiple parts, including the part to be judged, are set to the same day, a positive result is obtained (Yes in S1807).

[0080] If the maintenance schedules for multiple parts, including the part to be judged, are set collectively (Yes in S1807), the control unit 405 forces adjustment of the parameters of the equipment 100 related to the part to be judged or changes the maintenance schedule for the part to be judged (S1808). After step 1808, or if the maintenance schedule for multiple parts including the part to be judged has not been set collectively (No in S1807), proceed to step 1809. Furthermore, the processing in steps 1809 to 1812 is the same as the processing in steps 607 to 610 in the adjustment process shown in Figure 8.

[0081] Figure 19 is a flowchart showing the flow of the adjustment instruction process as a modified example 2 (see S1810 in Figure 18). The control unit 405 of the lifespan calculation server 400 obtains the email address of the person in charge (administrator) of the equipment 100 whose parameters are to be adjusted from the storage unit 402 (S1901). The control unit 405 includes the URL of the adjustment request screen 900 in the email body (S1902). The control unit 405 includes a message in the email body instructing the adjustment of the parameters of the device 100 (S1903).

[0082] The control unit 405 determines whether the maintenance schedules for multiple components have been set together (S1904). If the maintenance schedules for multiple parts are set together (Yes in S1904), the control unit 405 will include a note in the email body indicating that the maintenance schedules for multiple parts are set together (S1905). After step 1905, or if the maintenance schedules for multiple parts have not been set together (No in S1904), the control unit 405 sends an email to the email address obtained in step 1901 (S1906).

[0083] Figure 20 is a flowchart illustrating the process of processing a scheduled date request (see S1811 in Figure 18) as a modified example 2. The control unit 405 of the lifespan calculation server 400 obtains the email address of the person (administrator) who is scheduled to perform maintenance on the equipment 100 on the scheduled maintenance date (S2001). The control unit 405 includes the URL of the scheduled date reception screen 1100 in the email body (S2002). The control unit 405 includes a message in the email body requesting adjustment of the maintenance schedule (S2003).

[0084] The control unit 405 determines whether the maintenance schedules for multiple components have been set together (S2004). If the maintenance schedules for multiple parts are set together (Yes in S2004), the control unit 405 will include a note in the email body indicating that the maintenance schedules for multiple parts are set together (S2005). After step 2005, or if the maintenance schedules for multiple parts have not been set together (No in S2004), the control unit 405 sends an email to the email address obtained in step 2001 (S2006).

[0085] Figure 21 shows the adjustment email screen 1500 as a modified example 2. In the second variation, the body of the adjustment email screen 1500, section 1503, contains the text "Please be sure to adjust the parameters from the following URL," which compels the user to adjust the parameters of the device 100. The body of the email also contains the text "Please note that a single maintenance schedule has been set for the device in question," indicating that maintenance dates for multiple components have been set together. In the modified example 2, when an adjustment instruction process is performed, an email containing the content shown in Figure 21 may be periodically sent to the administrator's email address until the parameters of the device 100 are adjusted.

[0086] Figure 22 shows a modified example, the schedule email screen 1300. As a variation 2, the subject line 1301 of the scheduled email screen 1300 shows the text "Instruction to adjust maintenance schedule". Furthermore, section 1303 of the main text contains the text, "Please be sure to adjust your maintenance schedule using the following URL," which compels users to adjust their maintenance schedule. Also, section 1303 contains the text, "Please note that a single maintenance schedule has been set for the equipment in question," which indicates that maintenance schedules for multiple parts have been set together. In the modified example 2, if a scheduled date request is processed, an email containing the content shown in Figure 22 may be periodically sent to the administrator's email address until the parameters of the device 100 are adjusted.

[0087] As described above, if maintenance dates later than the expected end date are set for multiple parts collectively, the control unit 405 notifies the administrator that adjustment of parameters or maintenance dates is required. In this case, the administrator can be reminded to make adjustments to the multiple parts for which maintenance dates later than the expected end date are set collectively.

[0088] In this embodiment, it was explained that a maintenance schedule date later than the expected lifespan date may be set individually for a single component. It was also explained that when the expected lifespan date of a component is after the maintenance schedule date, the usage of the equipment 100 may be such that adjustments to the component's parameters are unlikely to cause any "concerns" due to those adjustments. Furthermore, it was explained that a maintenance schedule date later than the expected lifespan date may be set collectively for multiple components. Here, the control unit 405 of the lifespan calculation server 400 may differentiate the manner of notification to the administrator depending on which of these three situations occurs. For example, if a maintenance schedule is set individually for a single component that is later than the expected end date of its lifespan, the control unit 405 may recommend that the administrator adjust the parameters in the equipment 100. For instance, the control unit 405 may send an adjustment email 1500 to the administrator with the text "Parameter adjustment recommended" in the body section 1503. Furthermore, for example, if the expected end date of a component's lifespan falls after the scheduled maintenance date, the usage of the equipment 100 may be such that adjustments to the component's parameters are unlikely to cause any "concerns." In this case, the control unit 405 may propose to the administrator that the parameters of the equipment 100 be adjusted. For example, the control unit 405 may send an adjustment email 1500 to the administrator with the text "We propose parameter adjustments" in the body section 1503. Furthermore, for example, if maintenance schedules are set for multiple parts collectively, and these are later than the expected end date of life, the control unit 405 may compel the administrator to adjust the parameters in the equipment 100. For example, the control unit 405 may send an adjustment email 1500 to the administrator with the text "Please be sure to adjust the parameters" in the body section 1503.

[0089] In this embodiment, the device 100 is described as transmitting device information to the lifespan calculation server 400 at predetermined intervals, but this is not limited to this. For example, whenever the device 100 generates the latest status information, it may send device information including the generated latest status information to the lifespan calculation server 400.

[0090] Furthermore, although this embodiment describes the control unit 405 of the lifespan calculation server 400 instructing the administrator to adjust the parameters of the device 100, the embodiment is not limited to this. The control unit 405 may instruct the device 100 to adjust its parameters. In this case, the device 100 adjusts its parameters upon receiving instructions from the lifespan calculation server 400. Therefore, if the expected end date of a component's lifespan is earlier than the scheduled maintenance date, the parameters of the device 100 are adjusted without requiring any action from the administrator. The instruction from the control unit 405 to the device 100 to adjust its parameters is also considered as a remote execution of an instruction to adjust the parameters in the device 100.

[0091] Furthermore, although this embodiment describes the lifespan calculation server 400 instructing the adjustment of the parameters of the device 100, it is not limited to this. If the estimated end date of a component's lifespan is earlier than the scheduled maintenance date, the control unit 503 of the adjustment management server 500 may instruct the administrator or the device 100 to adjust the parameters of the device 100 without the lifespan calculation server 400 issuing an adjustment instruction. Furthermore, the instruction from the control unit 503 to the administrator or the device 100 to adjust the parameters can be considered as a remote execution of an instruction to adjust the parameters on the device 100.

[0092] Furthermore, in this embodiment, the estimated end date of life and the scheduled maintenance date are compared only for parts in which signs of failure have been detected (see S601, S606, etc. in Figure 8), but the embodiment is not limited to this. For example, if the estimated end date of a component's lifespan is earlier than a predetermined period from the present, the estimated end date and the scheduled maintenance date may be compared. The predetermined period can be any period, but for example, it could be two months. Furthermore, for any component for which an estimated end date has been calculated, the estimated end date and the scheduled maintenance date may be compared. In other words, the estimated end date and the scheduled maintenance date may be compared regardless of whether or not signs of failure have been detected in the component.

[0093] The present invention also includes cases in which a software program that realizes the functions of the above-described embodiments is supplied directly from a recording medium or via wired / wireless communication to a system or device having a computer capable of executing the program, and the program is executed. Therefore, in order to realize the functional processing described above in relation to the present invention using a computer, the program code itself supplied to and installed on the computer also realizes the present invention. In other words, the computer program itself for realizing the functional processing of the present invention is also included in the present invention. In this case, the form of the program is not limited as long as it has the functionality of a program, such as object code, a program executed by an interpreter, or script data supplied to an OS. As a recording medium for supplying the program, for example, a hard disk, a magnetic recording medium such as magnetic tape, an optical / magneto-optical storage medium, or a non-volatile semiconductor memory may be used. Furthermore, as a method of supplying the program, a method can be considered in which a computer program forming the present invention is stored on a server on a computer network, and a connected client computer downloads the computer program and programs it. Furthermore, based on the instructions of the program code, an operating system or similar device running on the computer may perform some or all of the actual processing, thereby realizing each of the functions of the embodiment described above. In addition, the program code read from the storage medium may be written to the memory of a function expansion board inserted into the computer or a function expansion unit connected to the computer. Then, based on the instructions of that program code, a CPU or similar device in that function expansion board or function expansion unit may perform some or all of the actual processing. Even in this case, each of the functions of the embodiment described above will be realized.

[0094] This embodiment includes the following configuration. (Composition 1) Information acquisition means for acquiring internal information of the target device, A calculation means for calculating the expected date of reaching the end of the lifespan of a component included in the target device based on the aforementioned internal information, Maintenance date setting means for setting the scheduled maintenance date for the aforementioned parts, If the estimated lifespan end date calculated by the calculation means is earlier than the scheduled maintenance date set for the component by the maintenance date setting means, the execution means remotely executes instructions to adjust the parameters of the target device so as to prevent errors related to the lifespan of the component until the scheduled maintenance date. A system equipped with these features. (Configuration 2) The system according to configuration 1, wherein the parameter adjustment is an adjustment related to the operation of the component when the component is used in conjunction with the operation of the target device. (Composition 3) The aforementioned device includes multiple components, Each of the aforementioned multiple components is pre-associated with a parameter corresponding to that component as the object to be adjusted in the target device. The system according to configuration 1 or 2, wherein the execution means executes an instruction to adjust the parameters associated with the part whose expected lifespan is earlier than the scheduled maintenance date. (Composition 4) The information acquisition means acquires historical information relating to the user's usage history of the target device. The execution means is a system according to any one of configurations 1 to 3, wherein, when there are multiple parameters related to suppressing the occurrence of errors related to the lifespan of the component, it executes an instruction to adjust one of the multiple parameters according to the history information. (Composition 5) The information acquisition means acquires historical information relating to the user's usage history of the target device. The execution means is a system according to any one of configurations 1 to 4, which executes the parameter adjustment instruction even if the expected end date is after the scheduled maintenance date, when the conditions defined regarding the relationship between the usage status identified from the history information and the parameters to be adjusted in the target equipment are met.

[0095] Although the present invention has been described in detail above based on its preferred embodiments, the present invention is not limited to the above embodiments, and various modifications are possible in accordance with the spirit of the present invention, and these modifications are not excluded from the scope of the present invention. [Explanation of Symbols]

[0096] 1...Management system, 100...Equipment, 400...Lifespan calculation server, 500...Adjustment management server, 600...Schedule management server

Claims

1. Information acquisition means for acquiring internal information of the target device, A calculation means for calculating the expected date of reaching the end of the lifespan of a component included in the target device based on the aforementioned internal information, Maintenance date setting means for setting the scheduled maintenance date for the aforementioned parts, If the estimated lifespan end date calculated by the calculation means is earlier than the scheduled maintenance date set for the component by the maintenance date setting means, the execution means remotely executes instructions to adjust the parameters of the target device so as to prevent errors related to the lifespan of the component until the scheduled maintenance date. A system equipped with these features.

2. The system according to claim 1, wherein the parameter adjustment is an adjustment relating to the operation of the component when the component is used in conjunction with the operation of the target device.

3. The aforementioned device includes multiple components, Each of the aforementioned multiple components is pre-associated with a parameter corresponding to that component as the object to be adjusted in the target device. The system according to claim 1, wherein the execution means executes an instruction to adjust the parameters associated with the part whose expected lifespan is earlier than the scheduled maintenance date.

4. The information acquisition means acquires historical information relating to the user's usage history of the target device. The system according to claim 1, wherein the execution means, when there are multiple parameters related to suppressing the occurrence of errors affecting the lifespan of the component, executes an instruction to adjust one of the multiple parameters according to the history information.

5. The information acquisition means acquires historical information relating to the user's usage history of the target device. The system according to claim 1, wherein the execution means executes an instruction to adjust the parameter if the expected end date is after the scheduled maintenance date, provided that the conditions defined regarding the relationship between the usage status identified from the history information and the parameter to be adjusted in the target device are met.

6. The process of acquiring internal information of the target device, A step of calculating the expected date on which the lifespan of the components included in the target equipment will be reached based on the aforementioned internal information, The process of setting a scheduled maintenance date for the aforementioned parts, If the calculated estimated lifespan date is earlier than the scheduled maintenance date set for the component, the process includes remotely executing instructions to adjust the parameters of the target device so as to prevent errors related to the lifespan of the component until the scheduled maintenance date, A method having.

Images