JP2016119524A - Apparatus management system, apparatus management device, control method of apparatus management system, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an apparatus management system capable of identifying an electronic apparatus having the possibility of fault occurrence without detecting an error and giving notice so as not to cause a fault in the identified electronic apparatus.SOLUTION: In an apparatus management system 100, a plurality of electronic apparatuses 103 and an apparatus management device 101 for managing the electronic apparatuses are communicatively connected. The apparatus management system includes: fault management information storage means for managing a situation in which a fault occurs in the electronic apparatus; electronic apparatus identification means for identifying an electronic apparatus in which a fault occurs from the electronic apparatuses stored in the fault management information storage means; and notification means for giving notice of the possibility that a fault occurs in the electronic apparatus.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a device management system, a device management apparatus, a device management system control method, and a program.

  Conventionally, in an electronic device such as a printing apparatus or a multifunction device, when an error occurs in the electronic device, an error message is output to the device body or an error is notified to a predetermined contact address. ing.

  In addition, a management system in which a management device remotely monitors the status of devices such as a printing device and a multifunction peripheral and detects a failure status is conventionally known. In this management system, the management apparatus performs processing for arranging a service person who performs maintenance work of the image forming apparatus.

  For example, Patent Literature 1 proposes a technique for automatically collecting the operating status of devices installed at each user destination in a service center using an existing network service and performing service activities.

JP 2002-73799 A

  In Patent Literature 1, when an abnormality or an abnormal prior event occurs during operation of an installed device, the information is transmitted to an information management apparatus, and repairs are arranged with a service person based on the information.

  However, in an electronic device such as a multifunction peripheral or a printer, a failure (failure) may occur even if an error (abnormality or abnormal pre-event) does not occur. That is, there are cases where an error code is not issued as an error and the operation of the device becomes strange, or an error occurs when certain processing is performed without an error.

  In such a case, since the occurrence of an error cannot be recognized on the device side, a warning display on the operation unit and failure information transmission to an external computer cannot be performed. In general, it takes time for development and distribution to apply a fault correction program.

  For this reason, there is a risk that a failure will occur and damage will occur before all users who use the electronic device are not aware until the correction program is applied. In some cases, it is desirable to refrain from using the device depending on the degree of damage.

  Therefore, in view of the above-described problems, the present invention can identify an electronic device that may cause a failure without detecting an error, and can provide notification that the failure does not occur in the specified electronic device. The object is to provide a device management system.

  A device management system in which an electronic device and a device management apparatus that manages the electronic device are connected to be communicable, a failure management information storage unit that manages a situation where a failure occurs in the electronic device, and the failure management An electronic device specifying means for specifying an electronic device in which a failure of the electronic device stored in the information means occurs; and a notification means for notifying that a failure may occur in the electronic device. And

  The present invention provides an apparatus management system capable of identifying an electronic apparatus that may cause a failure without detecting an error and performing a notification so that no failure occurs in the identified electronic apparatus. Is possible.

1 is a system configuration diagram illustrating an example of a configuration of a device management system according to an embodiment of the present invention. It is a hardware block diagram of the information processing apparatus applicable to the apparatus management apparatus which concerns on embodiment of this invention. FIG. 2 is a hardware configuration diagram of a controller unit of a multifunction peripheral that can be applied to an electronic device according to an embodiment of the present invention. It is a functional block diagram which shows an example of the functional structure in the apparatus management system in embodiment of this invention. It is a figure which shows an example of the failure management screen in the apparatus management system in embodiment of this invention. It is a flowchart which shows an example of the failure generation apparatus specific process in the apparatus management system in embodiment of this invention. It is a figure which shows an example of the failure generation apparatus information screen in the apparatus management system in embodiment of this invention. It is a figure which shows an example of apparatus management DB in the apparatus management system in embodiment of this invention. It is a figure which shows an example of failure management DB of the apparatus management system in embodiment of this invention. It is a flowchart which shows an example of the failure information update process of the electronic device in the apparatus management system in embodiment of this invention. It is a flowchart which shows an example of the process at the time of utilization of the electronic device in the apparatus management system in embodiment of this invention. It is a figure which shows an example of the failure warning screen in the apparatus management system in embodiment of this invention. It is a figure which shows an example of the degeneration confirmation screen in the apparatus management system in embodiment of this invention. It is a figure which shows an example of the degeneration cancellation | release confirmation screen in the apparatus management system in embodiment of this invention. It is a flowchart which shows an example of the process at the time of the system change of the electronic device in the apparatus management system in embodiment of this invention. It is a figure which shows an example of the system change confirmation screen of the apparatus management system in embodiment of this invention.

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

  FIG. 1 is a system configuration diagram illustrating an example of a configuration of a device management system according to an embodiment of the present invention.

  In the device management system 100, a device management apparatus 101, one or a plurality of multifunction device management PCs (client terminals) 102, and one or a plurality of electronic devices (such as a multifunction device) 103 are connected to a local area network (LAN: not shown). It is the structure connected so that communication is possible.

  The device management apparatus 101 manages information related to setting values set for the electronic device 103 and possible failures, and acquires information directly from the electronic device 103 or managed by the MFP management PC 102. Then, it is stored in each table prepared for itself.

  The MFP management PC 102 can also operate as a normal client terminal, and can connect to the device management apparatus 101 to access information managed by the device management apparatus. It is also possible to perform printing or the like.

  Then, the device management apparatus 101 transmits failure information to an electronic device that may cause a failure based on these pieces of information, and if necessary, reduces the functionality so that no failure occurs. Let it be done.

  FIG. 2 is a hardware configuration diagram of an information processing apparatus applicable to the device management apparatus 101 according to the embodiment of the present invention.

  In FIG. 2, reference numeral 201 denotes a CPU that comprehensively controls each device and controller connected to the system bus 204. Further, the ROM 202 or the external memory 211 is necessary to realize a BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as an OS), which is a control program of the CPU 201, or a function executed by each server or each PC. Various programs to be described later are stored.

  A RAM 203 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program or the like necessary for execution of processing from the ROM 202 or the external memory 211 into the RAM 203 and executing the loaded program.

  An input controller 205 controls input from a keyboard (KB) 209 or a pointing device such as a mouse (not shown). A video controller 206 controls display on a display device such as a CRT display (CRT) 210. In FIG. 2, although described as CRT 210, the display device is not limited to the CRT, but may be another display device such as a liquid crystal display. These are used by the administrator as needed.

  Reference numeral 207 denotes a memory controller, which is stored in an external storage device (hard disk (HD)), flexible disk (FD), or PCMCIA card slot for storing a boot program, various applications, font data, user files, editing files, various data, and the like. Controls access to an external memory 211 such as a compact flash (registered trademark) memory connected via an adapter.

  A communication I / F controller 208 connects and communicates with an external device via a network (for example, the LAN 400 shown in FIG. 1), and executes communication control processing in the network. For example, communication using TCP / IP is possible.

  Note that the CPU 201 enables display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example. In addition, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the CRT 210.

  Various programs to be described later for realizing the present invention are recorded in the external memory 211 and executed by the CPU 201 by being loaded into the RAM 203 as necessary. Furthermore, definition files and various information tables used when executing the program are also stored in the external memory 211, and a detailed description thereof will be described later.

  FIG. 3 is a hardware configuration diagram of a controller unit of a multifunction peripheral that can be applied to the electronic device 103 according to the embodiment of the present invention.

  In FIG. 3, reference numeral 316 denotes a controller unit which is connected to a scanner 314 functioning as an image input device and a printer unit 312 functioning as an image output device, while being connected to a LAN or a public line (WAN) (for example, PSTN or ISDN). By connecting, image data and device information are input and output.

  In the controller unit 316, reference numeral 301 denotes a CPU, which is a processor that controls the entire system. A RAM 302 is a system work memory for the CPU 301 to operate, and is also a program memory for recording a program and an image memory for temporarily recording image data.

  A ROM 303 stores a system boot program and various control programs. A hard disk drive (HDD) 304 stores various programs for controlling the system, image data, and the like.

  An operation unit interface (operation unit I / F) 307 is an interface unit with the operation unit (keyboard) 308. Further, the operation unit I / F 307 serves to transmit the key information (for example, pressing of the start button) input from the operation unit 308 to the CPU 301.

  Reference numeral 305 denotes a network interface (Network I / F), which is connected to a network (LAN). In addition, wireless communication is also possible, and connection is made with other devices by communication using infrared rays, Bluetooth (registered trademark), or Wi-Fi (registered trademark). Input and output data. A modem (MODEM) 306 is connected to a public line and inputs / outputs data such as FAX transmission / reception.

  Reference numeral 318 denotes an external interface (external I / F), which is an I / F unit that accepts external inputs such as USB, IEEE 1394, printer port, and RS-232C. In this embodiment, an IC card for a portable terminal required for authentication A card reader 319 for reading (storage medium) is connected to the external I / F 318. The CPU 301 can control reading of information from the IC card of the mobile terminal by the card reader 319 via the external I / F 318, and can acquire information read from the IC card of the mobile terminal. The above devices are arranged on the system bus 309.

  Reference numeral 320 denotes an image bus interface (IMAGE BUS I / F), which is a bus bridge that connects the system bus 309 and an image bus 315 that transfers image data at high speed and converts the data structure.

  The image bus 315 is configured by a PCI bus or IEEE1394. The following devices are arranged on the image bus 315.

  A raster image processor (RIP) 310 develops vector data such as a PDL code into a bitmap image. A printer interface (printer I / F) 311 connects the printer unit 312 and the controller unit 316 and performs synchronous / asynchronous conversion of image data. A scanner interface (scanner I / F) 313 connects the scanner 314 and the controller unit 316 and performs synchronous / asynchronous conversion of image data.

  Reference numeral 317 denotes an image processing unit that corrects, processes, and edits input image data, and performs multifunction device correction, resolution conversion, and the like on print output image data. In addition to this, the image processing unit 317 performs image data rotation and compression / decompression processing such as JPEG for multi-valued image data and JBIG, MMR, MH for binary image data.

  The scanner 314 illuminates an image on paper as a document and scans it with a CCD line sensor, thereby converting it into an electrical signal as raster image data. The original paper is set on the tray of the original feeder, and when the apparatus user gives a reading start instruction from the operation unit 308, the CPU 301 gives an instruction to the scanner 314, and the feeder feeds the original paper one by one to read the original image. I do.

  The printer unit 312 is a part that converts raster image data into an image on paper. The method is an electrophotographic method using a photosensitive drum or a photosensitive belt, and ink is ejected from a micro nozzle array directly on the paper. There is an inkjet method for printing an image, but any method may be used. The activation of the printing operation is started by an instruction from the CPU 301. The printer unit 312 has a plurality of paper feed stages so that different paper sizes or different paper orientations can be selected, and has a paper cassette corresponding thereto.

  The operation unit 308 has an LCD display unit, and a touch panel sheet is pasted on the LCD. The operation unit 308 displays an operation screen of the system. When a displayed key is pressed, the position information is displayed on the operation unit I / F 307. To the CPU 301 via The operation unit 308 includes, for example, a start key, a stop key, an ID key, a reset key, and the like as various operation keys.

  The display unit has a different display performance depending on the multifunction device. The multifunction device can be operated via a touch panel. The multifunction device is simply equipped with a liquid crystal display and displays a character string (displays the print status and printed document name). Thus, the present invention is constituted.

  Here, the start key of the operation unit 308 is used when starting a document image reading operation. At the center of the start key, there are two color LEDs, green and red, which indicate whether or not the start key can be used. Further, the stop key of the operation unit 308 functions to stop the operation in operation. The ID key of the operation unit 308 is used when inputting the user ID of the user. The reset key is used when initializing settings from the operation unit.

  The card reader 319 reads information stored in an IC card (which may be provided in the portable terminal as an IC chip) under the control of the CPU 301, and reads the read information via the external I / F 318. To notify. Further, the card reader 319 corresponds to the NFC communication standard, and is configured to be able to read and write to an IC card or an IC chip of a portable terminal.

  Note that when an NFC standard-compliant portable terminal is held over an NFC standard-compliant card reader, authentication is performed and the portable terminal and the multifunction device are paired. Then, it is possible to establish communication (P2P) between the held portable terminal and the multifunction device to perform data communication. In addition, it is possible to take over communication (handover) to Bluetooth (registered trademark) or Wi-Fi (registered trademark), which are high-speed communication standards, and to perform communication between the portable terminal and the multifunction peripheral. For example, by holding the portable terminal over a card reader, an image stored in the portable terminal can be transmitted to the multifunction peripheral. The details of the NFC communication standard are conventional techniques, and thus the description thereof will be omitted.

  In the electronic device 103 described above, a platform for controlling the electronic device 103 exists, and an authentication application for communicating with an authentication server (not shown) is operating on the platform.

  The authentication application is stored in the HDD 304. An area on the HDD 304 is secured for a login context that is managed by the platform and stores user information at the time of login, and various setting information.

  On the platform, an application in which the main body function of the multifunction machine 103 is extended is installed and operated. These applications are executed using the platform API.

  Through this platform, each function of the multifunction peripheral can be controlled.

  In addition, the MFP 103 also stores a Web browser, and can also cooperate with the Web system. In this case, the screen received from the web application server is displayed using a web browser.

  A command instructed on the Web browser is requested to the Web application server, and an operation (scanning or print processing) can be executed by the MFP 103 by receiving the command from the Web application server.

  With the above-described configuration, the multi-function peripheral 103 can transmit the image data read from the scanner 314 to the LAN, and print out the print data received from the LAN using the printer unit 312.

  Further, the image data read from the scanner 314 can be faxed to the public line by the modem 306, and the image data received by fax from the public line can be output by the printer unit 312.

  FIG. 4 is a functional configuration diagram illustrating an example of a functional configuration in the device management system according to the embodiment of the present invention.

  The device management system 401 includes a failed device identification unit 402, a failure information notification unit 403, a failure function degeneration control unit 404, a device management DB 405, a failure information management DB, and a system change management unit 407.

  The faulty device specifying unit 402 specifies an electronic device that may cause a fault in the device management system. The possibility of occurrence of a failure means that a failure may occur when a specific operation is performed instead of an error state in which the device cannot be used at the present time.

  The failure information notification unit 403 is a function for notifying an electronic device that is identified as having a possibility of a failure in the failed device specifying unit 402. The administrator can be notified by e-mail or the like, or can be directly displayed on the display unit of the electronic device.

  The failure function degeneration control unit 404 performs control to degenerate a predetermined function in a device in which a failure may occur. It is used when a failure can be avoided by invalidating a predetermined function.

  The device management DB 405 stores information on electronic devices managed by the device management system. As will be described with reference to FIG. 8, this information may be input by an administrator, or may be acquired by communicating with an electronic device.

  The failure information management DB 405 is described with reference to FIG. 9, but is configured with conditions and the like regarding the possibility of failure. The device management apparatus stores all failure information, and the electronic device has failure information related to the electronic device.

  The system change management unit 407 is processed when a system change is performed on an electronic device. If the system change causes a failure to occur, the system change is performed. It can be controlled not to do so.

  FIG. 5 is a diagram illustrating an example of a failure management screen in the device management system according to the embodiment of the present invention.

  The failure management screen 500 is a screen displayed on the client PC 102 or the like when an administrator or a user accesses a predetermined menu of the device management system.

  The failure information list 501 is a list that displays a correspondence table between the failure content 506 and the degeneration function 507. What is given to this unique NO is one piece of failure information.

  The failure content 506 is a failure that may occur in the corresponding device, and the degradation function 507 is a function that can prevent the occurrence of a failure by degrading the function (so that it cannot be used). That is.

  An add button 502 is a button for adding failure information to the failure information list 501, and a change button 503 is a button for changing the failure information selected in the failure information list 502 of the failure list 501. When the add button 502 and the change button 503 are pressed, a failure information detail screen 510 is displayed. When the delete button 504 is pressed, the selected failure information is deleted.

  When the failure occurrence device information 505 is pressed, an electronic device that may cause a failure is identified from the electronic devices managed by the device management system based on the conditions set on the failure information detail screen 501. 7, a faulty device information screen described later is displayed.

  The failure information detail screen 510 is a screen for performing detailed settings corresponding to the failure information. The fault contents 511, first aid information 512, fault information distribution condition formula 513, fault occurrence condition formula 514, condition list 515, and degenerate device name list 518 are set.

  In accordance with the conditions set here, the device management system identifies a device that may cause a failure.

  The failure content 511 is a text box for inputting the failure content. The content input here is displayed in the failure content 506. The first aid information 512 is information that can be freely input by the administrator or the user, and is used as a message to the electronic device or a user of the electronic device together with the content entered in the failure content 511. It is desirable to write first aid information for the failure.

  The failure information distribution conditional expression 513 is a text box for inputting a conditional expression for distributing failure information. In the example, since “1” is input, the failure information is distributed to the electronic device that matches the condition set to NO “1” in the condition list 515.

  The failure occurrence conditional expression 514 is a text box for inputting a conditional expression in which a failure occurs.

Since “1 * 2 * 3” has been input, there is a possibility that a failure will occur in the items that satisfy all of “1”, “2”, and “3” in the condition list 515.

  In the condition list 515, conditions that can be used in the failure information distribution conditional expression 513 and the failure occurrence conditional expression 514 are set.

  For example, in this example, the failure information is distributed to an electronic device having the condition NO1 “product name is MFP_A (product name = MFPA)”, and the condition (combination) where the failure occurs is the condition NO1 “product name is MFP_A. (Product name = MFP_A) ”and condition NO2“ firmware version is 1.2.0 (firmware version = 1.2.0) ”and condition NO3“ extended application X is installed (extended application = X) ” Is input as a setting generated in an electronic device satisfying "."

  An add button 516 adds a condition to the condition list, and a delete button 517 deletes the condition of the selected row in the list.

  The degenerate function name list 518 is a list for inputting the function name and execution authority of the function to be degenerated in an electronic device that may cause a failure. In the example of the failure management screen 500, the degraded function scan is set for the MFP_A with the failure NO “1”, but the degraded function is not set for the LBP_X with the failure NO “2”.

  An add button 519 adds a reduction function to the reduction function name list 518, and a delete button 520 deletes the reduction function of the selected row in the list.

  When the OK button 521 is pressed, the failure information input above is saved in the failure management DB shown in FIG. A cancel button 522 cancels editing of failure information and returns to the failure management screen.

  FIG. 6 is a flowchart illustrating an example of a faulty device specifying process in the device management system according to the embodiment of the present invention.

  It is a flowchart which shows an example of the process which produces | generates the information of the electronic device which may generate | occur | produce a failure among the electronic devices managed in the apparatus management system which concerns on this invention. For example, it may be executed after either the failure information DB or the device management DB is updated, or may be started by receiving an execution command by the administrator or the user.

  In step S601, electronic device information is acquired from the device management DB. In step S602, failure information is acquired from the failure management DB. FIG. 8 shows an example of the device management DB, and FIG. 9 shows an example of the failure management DB.

  FIG. 8 is a diagram illustrating an example of a device management DB in the device management system according to the embodiment of the present invention.

  The device management DB 800 stores a customer name 801, a serial number 802, a model name 803, an IP address / host name 804, a firmware Ver 805, an extended application 806, and an administrator mail address 807.

  The contents stored here can be used in the condition list 515 in FIG. For example, in the example of FIG. 5, “model name = MFP_A” * “firmware = 1.2.0” “extended application = X” is a condition in the failure occurrence conditional expression 514, so the serial numbers “AAA00001” “ Three of "AAA00002" and "AAA00100" meet the conditions.

  Further, since “1: product name = MFP_A” in the failure information distribution condition formula 503, two cases “AAA00001” and “AAA00100” correspond to the above three.

  Further, when distributing failure information, the administrator mail address 807 can be used.

  FIG. 9 is a diagram showing an example of a failure management DB of the device management system in the embodiment of the present invention.

  The failure management DB 900 (failure management information storage means) stores NO 901, failure display information 902, first aid information 903, distribution conditions 904, occurrence conditions 905, a degeneration function 905, and degeneration authority failure management information. This content stores the content set on the failure information screen 500 of FIG.

  The contents set in NO1 are as described in FIG. 5 and the setting screen is not shown, but NO2 is also set in the failure information screen 500 in FIG. Returning to the description of FIG.

  In step S603, the electronic device and the failure information matching the distribution conditions are combined and stored from the device management information and the failure management information (electronic device specifying means). A dedicated database may be provided, or management may be performed by adding a flag to the device management DB, for example.

  FIG. 7 is a diagram showing an example of a faulty device information screen in the device management system according to the embodiment of the present invention.

  The faulty device information screen 700 is a screen image displayed on the client PC 102 used by the administrator or user.

  The failure information 701 displays the contents stored in the failure display information 902 of the failure management DB. The electronic device list 702 displays information on electronic devices that are determined to have the distribution conditions matched in step S603 of FIG.

  In the embodiment, since the distribution condition (failed device distribution condition 513) is “MFP_A”, items matching this are displayed as a list.

  A mail delivery button 703 to the administrator is a button for sending mail to the administrator of the row selected in the list of the electronic device list 702. The email text to be sent is generated with the failure management DB failure information, first-aid measure information, degeneration information, and relevant device information. Although not described in this form, the generated body text can be freely used. It may be editable. Note that this mail warning is mainly effective for printers that do not have an operation unit.

  FIG. 10 is a flowchart illustrating an example of failure information update processing for an electronic device in the device management system according to the embodiment of the present invention.

  When the electronic device 103 receives the failure information from the device management apparatus 101, the processing is started. The failure information may be acquired spontaneously by the electronic device 103 or may be transmitted from the device management apparatus 01.

  In step S1001, failure occurrence information of an electronic device as shown in FIG. 7 is acquired from the device management apparatus 101 by HTTP communication or the like.

  In step S1002, the acquired failure information is acquired from the failure information DB that has already been distributed and stored on the HDD of the electronic device.

  In step S1003, it is confirmed whether the failure information acquired in S1001 and S1002 has an update. If the fault information is updated, the process ends in S1004. If the fault information is not updated, the process is terminated.

  In step S1004, the failure information DB on the HDD of the electronic device is updated with the information in S1001. Here, even if the failure information remaining in the failure information DB of the electronic device in S1002 is not in the failure information DB of the device management apparatus in S1001, but the degeneration status in the failure information DB has already been reduced, it will be described later. Since the information is necessary for performing the degeneration cancellation shown in FIG. 11, the information is left as it is without being deleted from the failure information DB.

  The failure information DB includes both the device management apparatus and the electronic device. The failure information DB (first failure information DB) illustrated in FIG. 9 is included in the device management apparatus, and the entire device management system. The failure information is stored. On the other hand, the failure information DB (second failure information DB) possessed by the electronic device stores failure information related to the electronic device. For example, in the table shown in FIG. Is the only thing that is remembered.

  Therefore, what is updated in step S1004 is the failure management DB (second failure management DB) of the electronic device.

  FIG. 11 is a flowchart showing an example of processing at the time of using an electronic device in the device management system according to the embodiment of the present invention.

  The process is started when the user operates the electronic device. In step S1101, a failure information DB on the HDD of the electronic device is acquired. This information is synchronized with the failure management DB of the device management apparatus as needed by the processing described in FIG.

  In step S1102, environmental information held by the electronic device is acquired. These pieces of information are updated when there is a change in the electronic device system. The acquired environment information is information managed by the device management DB 800.

  In step S1103, the failure information including the product name, firmware, and extended application acquired in steps S1101 and S1102 is compared with the environment information to check whether the failure occurrence condition is met. If the failure occurrence condition is met, the process proceeds to S1104. If not, the process proceeds to S1110.

  In step S1104, a failure warning screen (UI) is displayed to notify the user that a failure may occur in the electronic device. An example of the failure warning screen will be described with reference to FIG.

  FIG. 12 is a diagram illustrating an example of a failure warning screen in the device management system according to the embodiment of the present invention.

  The failure warning screen 1200 displays failure information and countermeasure information stored in the failure management DB. In this case, it is desirable to use the failure management DB stored in the electronic device, but the latest information may be acquired from the device management apparatus and displayed. When the OK button 1202 is pressed, this screen is closed.

  In step S1105, whether the failure information acquired in S1101 has a function degeneration setting (function specifying means), or if there is a degeneration setting, the user who is logged in to the electronic device belongs to a group authorized to execute the degeneration. Whether the user is a user or a user (authority determination means), and further confirms whether the corresponding function has not been degraded.

  If there is an unexecuted degeneration setting and its execution authority, the process advances to step S1106. Otherwise, the process ends.

  In step S1106, a reduction confirmation screen (UI) is displayed in order to confirm with the user who is the operator whether or not to perform the reduction set in the failure management server. An example of the degeneration confirmation screen will be described with reference to FIG.

  FIG. 13 is a diagram showing an example of a degeneration confirmation screen in the device management system according to the embodiment of the present invention.

  The degradation confirmation screen 1300 displays a message in the message column 1301 as to whether or not to invalidate a degradable function. When the yes button 1302 is pressed, the function is invalidated, and when the no 1303 is pressed, the function is not invalidated.

  In step S1107, the content selected on the degradation confirmation screen is determined. If “yes” is selected, the process advances to step S1108. If “no” is selected, the process ends.

  In step S1108, the set function is degenerated. Examples of the degenerate function include a scan function, a print function, a FAX transmission function, a FAX reception function, a scan data transmission function, and an extended application function. In the present embodiment, the scan function is reduced as set by the reduction function 906 in FIG. Specifically, processing for invalidating (unusable) the scanning function of the electronic device is performed (function control means).

  In step S1109, the result of S1108 is stored (not shown) in the failure information DB of the electronic device as a degeneration execution status. This is the end of the process.

  On the other hand, the system in step S1110 is a processing system that recovers from a situation where a failure occurs and restarts the function once degenerated.

  First, in step S1110, it is confirmed whether the degradation status of the failure information DB on the electronic device HDD acquired in S1101 has been executed and the user who has logged in to the electronic device has the authority to execute the degeneration. If YES in step S1111, the process ends.

  In step S1111, a degeneration cancellation confirmation screen (UI) is displayed. An example of the degeneration cancellation confirmation screen will be described with reference to FIG.

  FIG. 14 is a diagram showing an example of a degeneration cancellation confirmation screen in the device management system according to the embodiment of the present invention.

  The degeneration cancellation confirmation screen 1400 displays, in the message column 1401, a message that the failure has been recovered and a message that indicates whether to enable (restore) the function that has been degenerated. When the YES button 1402 is pressed, the function is enabled, and when the NO 1403 is pressed, the function remains in a disabled state T.

  In step S1112, the content selected on the degeneration cancellation confirmation screen is determined. If “yes” is selected, the process proceeds to step S1113, and if “no” is selected, this process ends.

  In step S1113, the degeneration is canceled and the function is enabled (enabled). In step S1114, the degeneration status of the failure information DB of the electronic device is updated to recovery. This is the end of the process.

  By executing such a process, for example, when logging in and using an electronic device such as a multifunction device, the user is warned of the risk of failure, and the function in question can be reduced. , Can suppress the spread of damage.

  FIG. 15 is a flowchart illustrating an example of a system change process of an electronic device in the device management system according to the embodiment of the present invention.

  It is an example of the process performed in order to warn that there is a possibility that a failure may occur on the system after the change when changing the system setting of the electronic device according to the present invention. Examples of system setting change include firmware installation, extension application installation, and network setting change.

  In step S1501, the information of the failure information DB stored on the HDD of the electronic device is acquired. In step S1502, environmental information after the system change of the electronic device is acquired.

  In step S1503, it is checked whether the environment after the system change in S1502 matches the failure occurrence condition in S1501. If they match, the process proceeds to step S1504, and if not, the process proceeds to step S1506.

  In step S1504, a system change confirmation screen (UI) for confirming whether or not the system setting change is continued although a failure may occur is displayed. An example of the system change confirmation screen will be described with reference to FIG.

  FIG. 16 is a diagram showing an example of a system change confirmation screen of the device management system according to the embodiment of the present invention.

  The system change confirmation screen 1600 displays in the message column 1601 a failure message that may occur and a text message that confirms whether to accept the failure information and continue the change. When the YES button 1602 is pressed, the system change is continued, and when the NO button 1603 is pressed, the system is not changed.

  In step S1505, the content selected on the system change confirmation screen is determined. If “yes” is selected, the process advances to step S1506. If “no” is selected, the process ends.

  In step S1506, various system changes of the electronic device that are determined to be satisfactory are executed (update control means). Here, this process is completed. The changed system information is collected by the device management system and stored in the device management DB 800 of the device management apparatus.

  Then, in the device management apparatus, the above-described processing of FIG. 6 is executed, and the failure electronic device information is updated.

  As described above, even when the user changes the system setting, the expansion of damage can be suppressed by warning the user of the risk that a failure will occur after the change.

  In addition, the present invention can take the form of, for example, a system, apparatus, method, program, storage medium, or the like. Specifically, the present invention may be applied to a system including a plurality of devices. In addition, the present invention may be applied to an apparatus composed of one device.

  The program according to the present invention is a program that allows a computer to execute (read) each processing method, and the storage medium according to the present invention stores a program that allows the computer to execute each processing method.

  The program in the present invention may be a program for each processing method of each device.

  As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by performing reading.

  In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program constitutes the present invention.

  As a recording medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk or the like can be used.

  Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS or the like operating on the computer based on an instruction of the program is a part of the actual processing or It goes without saying that the case where the functions of the above-described embodiments are realized by performing all of the above processing is also included.

  Furthermore, after the program read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus.

  In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention. In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

DESCRIPTION OF SYMBOLS 100 Device management system 101 Device management apparatus 102 MFP management PC
103 Electronic equipment 201 CPU
202 ROM
203 RAM
204 System bus 205 Input controller 206 Video controller 207 Memory controller 208 Communication I / F controller 209 KB
210 CRT
211 External memory (HD / FD)
301 CPU
302 RAM
303 ROM
304 HDD (Hard Disk Drive)
305 NetWork I / F (network interface)
306 MODEM
307 Operation unit I / F (interface)
308 Operation unit 309 System bus 310 RIP (raster image processor)
311 Printer I / F (Printer Interface)
312 Printer unit 313 Scanner I / F (interface)
314 Scanner unit 315 Image bus 316 Controller unit 317 Image processing unit 318 External I / F (interface)
319 Card Reader 320 IMAGE BUS I / F (Image Bus Interface)

Claims (8)

An apparatus management system in which an electronic apparatus and an apparatus management apparatus that manages the electronic apparatus are connected to be communicable,
Fault management information storage means for managing a situation in which a fault occurs in the electronic device;
Electronic device identifying means for identifying an electronic device in which a failure of the electronic device stored in the failure management information storage means occurs;
A notification means for notifying that there is a possibility of failure in the electronic device;
A device management system comprising: A function specifying means for specifying a function causing a failure of the electronic device;
The device management system according to claim 1, wherein the notification unit notifies that the function is not used. A function control unit that receives the notification by the notification unit and disables the function in which the failure occurs;
The device management system according to claim 1, further comprising: Further comprising authority determining means for determining whether an operator of the electronic device has authority to disable the function;
The device according to claim 3, wherein the function control unit controls the device to be unusable when it is determined by the authority determination unit that the device has the authority to disable the device. Management system.   The function control means receives the notification that the function is not used by the notification means, and uses the function when the function is already disabled and the electronic device does not fail. 5. The device management system according to claim 3, wherein the device management system is controlled to a possible state.   When a system change is performed on the electronic device, the electronic device further includes an update control unit configured to acquire a new configuration of the electronic device and control not to perform an update when a failure occurs. The device management system according to any one of claims 1 to 5. An electronic device and a device management apparatus that manages the electronic device are communicably connected to each other, and is a control method for a device management system having a failure management information storage unit that manages a situation in which a failure occurs in the electronic device,
An electronic device identification step for identifying an electronic device in which a failure of the electronic device stored in the failure management information storage means occurs;
A notification step of notifying that there is a possibility of failure in the electronic device;
A device management system comprising: An electronic device and a device management apparatus that manages the electronic device are communicably connected to each other, and are a program that can be read by a device management system having a failure management information storage unit that manages a situation in which a failure occurs in the electronic device. And
The device management system;
Electronic device identifying means for identifying an electronic device in which a failure of the electronic device stored in the failure management information storage means occurs;
A notification means for notifying that there is a possibility of failure in the electronic device;
A program for causing a device management system to function.

Images