JP2009277090A - Pc protection/maintenance system, pc protection/maintenance method, and pc protection/maintenance program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technology that allows the efficient and inexpensive operation of a spare machine and further shortens an operation stop time of an end user caused by PC failures more than a conventional art. <P>SOLUTION: A PC protection/maintenance system 100 includes a scheduling means 110 which specifies a protection target PC whose failure occurrence probability within a prescribed period of time exceeds a prescribed value and sets rental days for repair days of the protection target PC into a rental situation of a corresponding spare machine, a restoring means 111 which transmits a command for restoring backup data of the protection target PC into the correspondence scheduled spare machine to a device that manages backup data of the protection target PC, and a data update management means 112 that executes processing for recording a user ID of the protection target PC as a user ID of the correspondence scheduled spare machine in a PC use-situation table 125, processing for adding a failure history of a repaired part about the protection target PC after the elapse of the repair days corresponding to the rental days, processing for updating the use situation of the repaired part to an unused state, and processing for clearing the user ID set into the protection target PC. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a PC preventive maintenance system, a PC preventive maintenance method, and a PC preventive maintenance program. More specifically, the present invention relates to efficient and low-cost operation of spare machines and reduction of end-user work stoppage time due to PC failure. It relates to technology that enables Further, the present invention includes operations for devices other than PCs, that is, devices that are lent to members such as employees.

  The number of PCs (Personal Computers) lent to employees at companies and the like becomes enormous depending on the company size. Therefore, it is necessary to devise appropriate measures when managing such PCs. Accordingly, as a maintenance management technique, for example, a service staff information support system including a service center apparatus that supports maintenance work of a service staff who performs maintenance services on field installation equipment installed at a maintenance site, the service center The equipment has an electronic manual database that stores work procedure manual contents information. When a failure notification is received from the on-site equipment, failure analysis, cause prediction and work procedure search are performed, and analysis result information is obtained. In addition, a service staff information support system (see Patent Document 1), which transmits the work procedure manual content information obtained by the search to a stationary personal computer at the maintenance site, has been proposed.

In addition to obtaining a member identification number from the customer, the customer database is searched based on the identification number to grasp the system configuration of the customer's personal computer, and the trouble status is confirmed to the personal computer user. A status check step, a fault history database is searched based on the grasped system configuration, a symptom, a cause and a measure are displayed for each model, and a measure advice step for advising a customer of a measure corresponding to the trouble status; When the trouble is not recovered by the above measures, an engineer selection step for selecting an optimal engineer from a plurality of engineers based on the distance to the customer and a schedule, and command information for transmitting commands and information to the selected engineer A personal computer comprising a transmission step. Such Yutasapoto method (see Patent Document 2) it has been proposed.
JP 2006-215616 A JP 2000-181968 A

  By the way, when a failure occurs in a PC lent to employees, a maintenance department of the PC generally receives a notice from the employee and lends a spare machine to the employee. When such a response is assumed, for example, when a number of failed PCs occur at the same time, it is expected that there will be a shortage of spare machines lent to employees. Employees who could not get a replacement PC due to a shortage of spare machines would have to stop the work being processed on the PC for a long time, and it would be unavoidable to reduce the work efficiency. On the other hand, if a large number of spare machines are prepared so as to avoid such a situation, the result is an increase in the PC operation cost.

  In addition, when management data such as a use history and a failure history is recorded for a PC (including a spare machine), for example, when the faulty PC and the spare machine are exchanged, the management is accompanied by the exchange. If the data is not properly updated, the management data may not match the actual status of the corresponding PC. As a result, the accuracy of processing using the management data (eg, failure prediction) also decreases, which may make it difficult to implement PC preventive maintenance itself.

  Therefore, the present invention has been made in view of the above-described problems, and is a technology that enables efficient and low-cost operation of a spare machine, and that can reduce the work stoppage time of an end user due to a PC failure than before. For the purpose of provision.

  The PC preventive maintenance system according to the present invention includes a communication means for communicating with other devices, a PC usage status table for storing PC usage status data, and a PC failure prediction information table for storing a failure occurrence probability on a predetermined date of the PC. And a spare unit schedule table for storing data on the lending status of spare units of PCs, and data of failure occurrence probability of each PC is read out from the PC failure prediction information table, and predetermined data is stored in the data. The prevention target PC whose failure occurrence probability within the period is equal to or greater than a predetermined value is identified, the spare machine of the prevention target PC is searched in the spare machine schedule table, and the number of repair days of the prevention target PC in the rental status of the spare machine Set the lending date of minutes, access the scheduling unit and the spare machine schedule table, and check the lending status after the present Identify the backup target machine that has a loan date for the prevention target PC, and restore the backup data of the prevention target PC to the corresponding standby machine for the device that manages the backup data of the prevention target PC An instruction to transmit via the communication means, a process of recording a user ID of the PC to be prevented as a user ID of the scheduled spare machine in the PC usage status table, and corresponding to the lending date The process of adding the failure history of the repaired part for the PC to be prevented after the repair days have passed, the process of updating the usage status of the repaired part to an unused state, and the user ID set for the PC to be prevented And a data update management means for performing a clearing process.

  Further, the PC preventive maintenance system monitors the lending status of the scheduled spare machine corresponding to the PC usage status table, detects the arrival of a predetermined number of days before the lending date set for the scheduled standby machine, In accordance with this detection, it may further comprise a shipping instruction means for transmitting a shipping instruction for the scheduled spare machine to the user of the PC to be prevented via the communication means to the terminal of the shipping manager of the spare machine. Good.

  In the PC preventive maintenance system, the storage means stores a logistic regression analysis application, reads usage status data of each PC from the PC usage status table, and stores a plurality of types of data included in the usage status data. A failure prediction unit is provided that inputs the logistic regression analysis application called from the storage unit as an independent variable, acquires a failure occurrence probability of each PC as a dependent variable on a predetermined day, and stores it in the PC failure prediction information table. It is good.

  Further, in the PC preventive maintenance system, the failure prediction means communicates with the PC being used by the user at predetermined intervals by the communication means, notifies the acquisition request for the usage status data of the corresponding PC, and responds to the acquisition request. The usage status data returned by the corresponding PC may be stored in the PC usage status table.

  Further, in the PC preventive maintenance system, the PC failure prediction information table stores a failure occurrence probability and a failure location on a predetermined date of the PC in association with each other, and the storage means stores each failure location of the PC. A PC repair days table storing data of necessary repair days is stored, and the scheduling means specifies a failure location in the PC to be prevented from the PC failure prediction information table, and the failure location data specified here Is compared with the PC repair days table, the repair days required for repairing the corresponding failure part are specified, and the loan status of the spare machine of the PC to be prevented in the spare machine schedule table is set as the loan days for the repair days. It may be set.

  In addition, the PC preventive maintenance system communicates with a device that manages backup data of the PC to be prevented by the communication unit, and the update frequency of backup data managed by the device by the storage unit is less than a predetermined standard The backup data user PC specified here is inquired of the scheduling means whether the failure occurrence probability within a predetermined period is equal to or higher than a predetermined value, and the failure occurrence probability within the predetermined period in the PC A backup promoting means may be provided for transmitting a backup processing reminder notification to the PC via the communication means when an answer is received from the scheduling means that the value is greater than or equal to a predetermined value.

  In the PC preventive maintenance method of the present invention, a computer stores communication means for communicating with other devices, a PC usage status table for storing PC usage status data, and a failure occurrence probability on a predetermined date of the PC. A storage unit for storing a PC failure prediction information table and a spare machine schedule table for storing PC spare machine lending status data, and a failure occurrence probability of each PC is determined from the PC failure prediction information table. Read the data, identify the PC to be prevented whose failure probability within a predetermined period is greater than or equal to a predetermined value from the data, search the spare machine schedule table for the spare machine of the PC to be prevented, and rent the spare machine A process of setting a loan date corresponding to the number of repair days of the PC to be prevented in the situation, and accessing the spare machine schedule table, A corresponding spare machine with a loan date for the preventive target PC set in the situation is identified, and the backup data of the preventive target PC is stored in the corresponding preparatory spare for the apparatus that manages the backup data of the preventive target PC. A process of transmitting an instruction to restore to a machine via the communication means, a process of recording a user ID of the PC to be prevented as a user ID of the corresponding scheduled spare machine in the PC usage status table, and the lending date A process of adding a failure history of the repaired part of the prevention target PC after the corresponding repair days have elapsed, a process of updating the usage status of the repaired part to an unused state, and a user ID set in the prevention target PC And a process of clearing.

  The PC preventive maintenance program of the present invention includes a communication means for communicating with other devices, a PC usage status table for storing PC usage status data, and a PC failure prediction for storing a failure occurrence probability on a predetermined date of the PC. A computer having an information table and a spare machine schedule table for storing data on the lending status of spare machines for PCs is stored in the computer with failure probability data for each PC from the PC failure prediction information table. Read, identify the prevention target PC whose failure occurrence probability within a predetermined period is equal to or greater than a predetermined value from the data, search the spare machine schedule table for the spare machine of the prevention target PC, and check the lending status of the corresponding spare machine Setting a lending date corresponding to the number of repair days for the PC to be prevented, accessing the spare machine schedule table, Identify the scheduled spare machine for which the loan date for the prevention target PC is set in the lending status of descending, and store the backup data of the prevention target PC for the device that manages the backup data of the prevention target PC A step of transmitting an instruction to restore to a corresponding scheduled spare machine via the communication means, a process of recording a user ID of the prevention target PC as a user ID of the scheduled corresponding spare machine in the PC usage status table, For the prevention target PC after the repair days corresponding to the lending date, a process of adding a failure history of the repaired part, a process of updating the usage status of the repaired part to an unused state, and the prevention target PC are set. And clearing the user ID.

  In addition, the problems disclosed by the present application and the solutions thereof will be clarified by the embodiments of the present invention and the drawings.

  As described above, in the present invention, devices other than the PC may be targeted.

  According to the present invention, an efficient and low-cost operation of a spare machine is possible, and an end user's business stoppage time due to a PC failure can be reduced as compared with the prior art.

--- System configuration ---
Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a network configuration diagram including a PC preventive maintenance system 100 according to the present embodiment, and FIG. 2 is a diagram illustrating a hardware configuration example of the PC preventive maintenance system 100 according to the present embodiment. A PC preventive maintenance system 100 (hereinafter, system 100) according to the present embodiment is a computer system that enables efficient and low-cost standby machine operation and reduction of end-user work stoppage time due to a PC failure.

  The system 100 reads the program 102 stored in the storage means 101 such as a nonvolatile memory into the memory 103 and executes it by the CPU 104 as an arithmetic unit in order to realize the function of executing the PC preventive maintenance method. Further, the system 100 is provided with an input interface 105 such as various buttons and a keyboard generally provided in a computer device and an output interface 106 such as an LED and a display as necessary, and further, a PC 200 via a network 140, shipping A communication unit 107 that performs communication with the administrator terminal 300, the backup management server 400, and the like may be included.

  Next, the means that the system 100 configures and holds based on the program 102 will be described. Each means may be provided integrally in one server device or the like, but is distributed and arranged in a computer group (including the server device corresponding to the system 100) arranged on the network 140, and one of the server devices (system 100). An example of collaboration under the leadership of The system stores tables 125 to 130 described later in the storage unit 101.

  The system 100 reads out the failure occurrence probability data of each PC from the PC failure prediction information table 126, identifies the prevention target PC having a failure occurrence probability within a predetermined period from the data, and A scheduling unit 110 is provided that searches the spare machine schedule table 129 for a spare machine of the prevention target PC, and sets a rental date corresponding to the number of repair days of the prevention target PC in the rental status of the spare machine.

  In addition, the system 100 accesses the spare machine schedule table 129, identifies the corresponding spare machine for which the loan date for the prevention target PC is set in the lending status after the present, and backs up the prevention target PC A restore unit 111 is provided that transmits an instruction to restore the backup data of the prevention target PC to the corresponding scheduled backup machine via the communication unit 107 to the backup management server 400 that manages data.

  Further, the system 100 records the user ID of the PC to be prevented as the user ID of the scheduled spare machine in the PC usage status table 125, and the prevention target after the repair days corresponding to the rental date have elapsed. Data for performing a process of adding a failure history of the repaired part of the PC, a process of updating the usage status of the repaired part to an unused state, and a process of clearing the user ID set in the prevention target PC Update management means 112 is provided.

  Further, the system 100 monitors the lending status of the corresponding scheduled spare machine in the PC usage status table 125, detects the arrival of a predetermined number of days before the lending date set for the corresponding scheduled spare machine, In accordance with the detection, a shipping instruction unit 113 is provided for transmitting a shipping instruction of the scheduled spare machine to the user of the PC to be prevented via the communication unit 107 to the terminal 300 of the shipping manager of the spare machine. It is good.

  The storage unit 101 may store a logistic regression analysis application 120. In this case, the system 100 reads the usage status data of each PC from the PC usage status table 125, and the logistic regression analysis application called from the storage means 101 as a plurality of types of data included in the usage status data as independent variables. It is also possible to provide failure prediction means 114 that takes 120 as an input, acquires the failure occurrence probability of each PC as a dependent variable on a predetermined day, and stores it in the PC failure prediction information table 126.

  The failure prediction unit 114 communicates with the PC in use by the user at a predetermined period by the communication unit 107, notifies the usage status data acquisition request of the corresponding PC, and returns the corresponding PC in response to the acquisition request. The usage status data thus stored may be stored in the PC usage status table 125.

  The PC failure prediction information table 126 may store a failure occurrence probability and a failure location on a predetermined date of the PC in association with each other. At this time, it is assumed that the storage means 101 stores a PC repair day table 127 that stores data on the number of repair days required for each failure location of the PC.

  In this case, the scheduling unit 110 identifies a failure location in the PC to be prevented from the PC failure prediction information table 126, collates the data of the identified failure location with the PC repair days table 127, and determines the corresponding failure. The number of repair days required for repairing the location may be specified, and the rental date corresponding to the number of repair days may be set as the spare status of the spare machine of the PC to be prevented in the spare machine schedule table 129.

  The system 100 communicates with the backup management server 400 that manages backup data of the PC to be prevented by the communication means 107, and the update frequency of backup data managed by the storage means by the backup management server 400 is predetermined. The data below the standard is specified, and with respect to the PC of the user of the backup data specified here, the scheduling means 110 is inquired whether the failure occurrence probability within a predetermined period is equal to or higher than a predetermined value, and within the predetermined period in the PC When a response that the failure occurrence probability is greater than or equal to a predetermined value is obtained from the scheduling unit 110, the backup promotion unit 115 may be provided that transmits a reminder notice of backup processing to the PC via the communication unit 107. Good.

  The units 110 to 115 in the system 100 described so far may be realized as hardware, or as a program stored in an appropriate storage unit 101 such as a memory or an HDD (Hard Disk Drive). Also good. In this case, the CPU 103 of the system 100 reads the corresponding program 102 from the storage unit 101 to the memory 103 and executes it in accordance with the program execution.

--- Example of table structure ---
Next, the structure of the table used by the system 100 in this embodiment will be described. FIG. 3 is a diagram showing an example of the data structure of the PC usage status table 125 of this embodiment. FIG. 4 shows (a) the PC failure prediction information table 126, (b) the PC repair days table 127, ( FIG. 5 is a diagram showing each data structure example of the failure PC repair schedule table 128, and FIG. 5 is a data structure example of (a) the spare machine schedule table 129 and (b) the end user attribute table 130 of this embodiment. FIG.

  The C usage status table 125 is a table for storing PC usage status data. The C usage status table 125 includes, for example, the PC management number as a key, the manufacturer name of the PC, the employee number as the user ID, the usage period of the hard disk drive (hereinafter referred to as HDD) provided in the PC, the usage period of the CPU, and the HDD usage period. Start-up time (example: daily average), CPU operation rate (example: daily average), number of times taken out to the outside, repair history (number of repairs), spare machine flag (operated by the user: 0, spare machine) As standby: 1), HDD temperature (example: average during operation), read error rate (average), seek error rate (average), start button long press (ex. Last week), CTRL + alt + Del press count (latest) A set of records associated with data such as one week).

  The PC failure prediction information table 126 is a table that stores the failure occurrence probability of a PC on a predetermined day. The PC failure prediction information table 126 includes, for example, the PC management number as a key, the manufacturer name of the PC, the failure prediction date of the PC (eg, the date when the failure occurrence probability reaches a predetermined level or more), and the failure on the predetermined date. This is a set of records in which data such as the probability of occurrence, the cause of failure at that time, and the backup flag (backup target = “1” for PCs near the failure occurrence, “0” for other PCs) are associated.

  The PC repair days table 127 is a table that stores data on the number of repair days required for each failure location of the PC. This PC repair days table 127 is, for example, a collection of records in which data such as failure causes (failure causes) and repair days is associated with the name of the PC manufacturer as a key.

  The failed PC repair schedule table 128 is a table that stores repair schedules of failed PCs. The failure PC repair schedule table 128 is, for example, a collection of records in which data such as the repair days, the repair start date, and the repair completion date are associated with the PC management number of the PC to be repaired or being repaired as a key. .

  The spare machine schedule table 129 is a table for storing data on the lending status of spare machines of the PC. The spare machine schedule table 129 is, for example, a collection of records in which the spare machine name is associated with the date and the PC management number of the PC that has become the spare machine.

  The end user attribute table 130 is a table for storing attribute data of PC users. The end user attribute table 130 is, for example, a collection of records in which data such as employee numbers of employees who are lent and using PCs, their department names, job types, genders, and years of service are associated with each other.

--- Processing flow example 1 (Failure prediction) ---
Hereinafter, the actual procedure of the PC preventive maintenance method according to the present embodiment will be described with reference to the drawings. Various operations corresponding to the PC preventive maintenance method described below are realized by the program 102 that the system 100 reads out to the memory 103 and executes. The program 102 includes codes for performing various operations described below.

  FIG. 6 is a flowchart showing a processing procedure example 1 of the PC preventive maintenance method of the present embodiment. First, failure prediction processing by the system 100 will be described. In this case, the failure predicting unit 114 of the system 100 communicates with the PC 200 being used by the user by the communication unit 107 every predetermined period, and notifies the usage status data acquisition request of the PC 200 (s100). Then, the usage status data returned by the corresponding PC 200 in response to the acquisition request is stored in the PC usage status table 125 (s101).

  The usage status data obtained from the PC 200 includes, for example, the PC management number of the PC 200, the manufacturer name, the employee number as a user ID, the HDD startup time (eg, daily average), and the CPU operating rate (eg, daily). Average), HDD temperature (example: average during operation), read error rate (average), seek error rate (average), number of long presses of the start button (example: last week), number of CTRL + alt + Del presses (last week), etc. Is given. On the other hand, data such as the HDD usage period, CPU usage period, number of times taken out to the outside, repair history (number of repairs) is not acquired by communication from the PC 200, but the system 100 performs the PC preventive maintenance method. The data is updated while executing.

  Next, the failure prediction means 114 of the system 100 reads the usage status data of each PC from the PC usage status table 125 to the memory 103 (s102). Further, the end user attribute data is read from the end user attribute table 130 to the memory 103 using the employee number included in the usage status data read here as a key (s103).

  Subsequently, the failure prediction unit 114 calls the logistic regression that is called from the storage unit 101 as a plurality of types of data included in the usage status data read into the memory 103 and the end user attribute data corresponding thereto. Using the input of the analysis application 120, the failure occurrence probability of each PC as a dependent variable on a predetermined day is calculated (s104). A plurality of types of data included in the usage status data and the corresponding end user attribute data as the independent variables, for example, HDD temperature, read error rate, seek error rate, user job type, etc. are mainly assumed, Of course, other types of data items may be employed. As the logistic regression analysis application 120, an existing application for logistic regression analysis may be adopted.

  The failure prediction means 114 acquires failure occurrence probability data on the predetermined day as an analysis result from the logistic regression analysis application 120, and stores this in the PC failure prediction information table 126 (s105).

--- Processing flow example 2 (scheduling) ---
Next, the scheduling process of the spare machine will be described. FIG. 7 is a flowchart showing a processing procedure example 2 of the PC preventive maintenance method of the present embodiment. Here, the scheduling means 110 of the system 100 reads out the failure occurrence probability data of each PC from the PC failure prediction information table 126, and the prevention target PC whose failure occurrence probability within a predetermined period is equal to or more than a predetermined value from the data. Is specified (s200). In the example of FIG. 4A, two PCs having PC management numbers “PC001” and “PC002” are assumed as PCs having a probability of failure of “50%” or more at “2008/1/22”. The scheduling means 110 can be specified.

  Next, the scheduling unit 110 determines whether or not the prevention target PC specified in step s200 exists (s201). If the number of prevention target PCs is zero (s201: Yes), the process ends. On the other hand, if the number of PCs to be prevented is not zero (s201: No), the backup flag is set to “1” in the record of the PC in the PC failure prediction information table 126 (s202).

  Subsequently, the scheduling unit 110 specifies the failure location and manufacturer in the PC to be prevented from the PC failure prediction information table 126, and collates the specified manufacturer and failure location data with the PC repair days table 127. Then, the number of repair days required for repairing the corresponding failure part of the corresponding manufacturer is specified (s203). In the above example, the cause of failure in the two PCs with PC management numbers “PC001” and “PC002” is “HDD” and “CPU” respectively, and the manufacturer names are “H” and “H”. is there. If these data are collated with the PC repair days table 127, the repair days can be identified as “5 days”.

  In addition, the scheduling unit 110 checks the failure prediction date of the prevention target PCs “PC001” and “PC002” in the PC failure prediction information table 126. For example, the PC with the earlier failure prediction date (“PC001” is “2008 / Read the spare machine lending status data from the spare machine schedule table 129 in order from 1/24 "and" PC002 "is" 2008/1/26 ", so" PC001 "). It is checked whether the spare machine has a vacancy (s204). Here, since the spare machine 001 “PC101” is available in the spare machine schedule table 129 (s205: Yes), the failure prediction date of the prevention target PC “PC001” is set as the schedule of the spare machine “PC101”. A loan date for “5 days” of repair days from “2008/1/24” (set to “0” in the schedule) is set (s206). On the other hand, if it is determined in step s204 that there are no spare machines (s205: No), for example, the shipping manager terminal 300 is notified that there are not enough spare machines (s207) and the process is terminated. To do.

  Further, the scheduling means 110 returns the PC to be prevented “PC001” from the repair after the repair days “5 days”, that is, “2008/1/29” five days after “2008/1/24”. Then, the PC management number “PC001” is set as the spare machine ID in the column after “2008/1/29” in the spare machine schedule table 129 (s208). The scheduling unit 110 performs the same process for the prevention target PC “PC002” following the prevention target PC “PC001”, and if the spare machine is assigned to all the prevention target PCs (s209: Yes). Exit. On the other hand, if a spare machine has not been assigned to all PCs to be prevented (s209: No), the process returns to step 205.

  By performing such scheduling, a PC that is estimated to be out of order is repaired, while a spare machine is lent to the user of the PC, and the PC that has been sent for repair returns from repair. Then, as a new spare machine is registered, the PC and spare machine that are regularly used by the user circulate in a predetermined period based on the failure occurrence probability and the number of repair days.

--- Processing flow example 3 ---
Next, backup of data on the prevention target PC and restoration of the backup data will be described. FIG. 8 is a flowchart showing a processing procedure example 3 of the PC preventive maintenance method of the present embodiment. Here, the restoration means 111 of the system 100 accesses the spare machine schedule table 129, and for example, the lending date for the prevention target PCs “PC001” and “PC002” is added to the lending status after “2008/1/23”, for example. To be supported are specified as “PC101” and “PC102” (s300). Alternatively, the PC failure prediction information table 126 is accessed, and the prevention target PCs “PC001” and “PC002” whose backup flag is “1” are specified.

  The restore means 111 searches the schedule table 129 for the lending date of the scheduled spare machines “PC101” and “PC102” (s301), and “2008/1/24” the day after “2008/1/23” today. The corresponding scheduled spare machine “PC101” for which the lending schedule is set is specified (s302: Yes). Then, the backup flag is set to “0” in the PC failure prediction information table 126 for the PC = prevention target PC “PC001” of the user to whom the corresponding scheduled spare machine “PC101” specified here is lent (s303). In addition, if the corresponding scheduled spare machine for which the rental schedule is set on “2008/1/24” the day after “2008/1/23” is not identified today (s302: No), the prevention target PC with a high probability of failure occurrence Steps s303 to s306 are executed in this order (s308).

  Next, the restoration unit 111 restores the backup data of the prevention target PC “PC001” to the corresponding scheduled spare machine “PC101” for the backup management server 400 that manages the backup data of the prevention target PC “PC001”. Is transmitted via the communication means 107 (s304).

  Further, the dispatch instruction means 113 of the system 100 monitors the lending status of the corresponding scheduled spare machine “PC101” in the PC usage status table 125, and the lending date set for the corresponding scheduled spare machine “PC101”. Detecting the arrival of a predetermined number of days before “2008/1/24” (for example, the number of days required for shipping the spare machine), and in response to this detection, the spare machine to be supported for the user of the PC “PC001” to be prevented A dispatch instruction of “PC 101” is transmitted to the dispatch manager terminal 300 via the communication means 107 (s305).

  Further, after the sending instruction is transmitted, the sending instruction unit 113 sets the spare machine flag of the scheduled spare machine “PC101” to be “0” in the PC usage status table 125 (s306). Further, the data update management means 112 of the system 100 records the user ID of the prevention target PC “PC001” as the user ID of the corresponding scheduled spare machine “PC101” in the PC usage status table 125 (s307).

--- Processing flow example 4 ---
Next, processing when the prevention target PC returns from repair will be described. FIG. 9 is a flowchart showing a processing procedure example 3 of the PC preventive maintenance method of the present embodiment. In this case, the data update management means 112 of the system 100 first identifies the PCs “PC001” and “PC002” whose backup flag is “1” in the PC failure prediction information table 126 (s400). Further, the repair completion date of the PCs “PC001” and “PC002” specified here is read from the spare machine schedule table 129 or the failure PC repair schedule table 128 (s401). In the above example, the repair completion dates of “PC001” and “PC002” are “2008/1/28” and “2008/1/30”.

  The data update management means 112 compares the repair completion dates “2008/1/28” and “2008/1/30” with today's date, for example, “2008/1/29”, and the repair completion date is The PC “PC001” is specified (s402: Yes). On the other hand, when the repair-completed PC cannot be identified at the present time (s402: No), the process is terminated.

  For the repair completed PC “PC001” specified in step s402, the data update management means 112 sets the spare machine flag in the PC usage status table 125 to “1” (s403). In other words, PC “PC001” that returned from the failure was set as a spare machine. Next, the data update management means 112 increments the failure history of the PC “PC001” (preferably “HDD” which is the repaired part of “PC001”) in the PC usage status table 125 (s404). Further, the usage period for the “HDD” is set to “0 days” in order to update the usage status of the repair location “HDD” to an unused state (s405). Furthermore, the employee number “A001” set in the PC “PC001” in the PC usage status table 125 is cleared (s406), and the process is terminated.

--- Other examples ---
In addition to the above-described example, for example, if a failure occurrence date is approaching for a PC whose backup data is taken only at a predetermined frequency or less, the system 100 prompts the backup processing to be executed before the failure occurs. It is preferable to perform the processing. If such a process is additionally performed by the system 100, from the viewpoint of PC preventive maintenance, it is not possible to secure backup data before the PC fails and to establish advance maintenance for the cause of the failure. Meaningful.

  In this case, the backup promoting unit 115 of the system 100 communicates with the backup management server 400 that manages the backup data of the PC to be prevented by the communication unit 107, and the backup management server 400 manages it by the storage unit. Identify the backup data whose update frequency is below a predetermined standard. Of course, in this case, the backup management server 400 manages the backup data, the PC management number of the PC that originated the backup data, and the data of the backup processing date in the storage device. The backup promotion unit 115 reads the data of the backup processing date in the storage unit of the backup management server 400, and if the processing date is more than a predetermined number of days before the current day, the backup frequency is low, and the corresponding backup Identify the data.

  The backup facilitating unit 115 inquires of the scheduling unit 110 whether or not the failure occurrence probability within a predetermined period is greater than or equal to a predetermined value for the PC management number of the specified backup data, and the occurrence of a failure within the predetermined period in the PC When an answer that the probability is greater than or equal to a predetermined value is obtained from the scheduling means 110, a reminder notice of backup processing (including a notice of the date of occurrence of failure) is transmitted to the PC via the communication means 107. The user of this PC can browse the reminder notice and recognize that the failure date is near and the necessity of backup processing.

  As described above, according to the present embodiment, it is possible to operate the spare machine efficiently and at a low cost, and it is possible to reduce the work stoppage time of the end user due to the PC failure.

  As mentioned above, although embodiment of this invention was described concretely based on the embodiment, it is not limited to this and can be variously changed in the range which does not deviate from the summary.

It is a network block diagram including the PC preventive maintenance system in this embodiment. It is a figure which shows the hardware structural example of the PC preventive maintenance system of this embodiment. It is a figure which shows the example of a data structure of the PC utilization condition table of this embodiment. It is a figure which shows each data structure example of (a) PC failure prediction information table of this embodiment, (b) PC repair days table, (c) failure PC repair schedule table. It is a figure which shows each data structure example of (a) spare machine schedule table and (b) end user attribute table of this embodiment. It is a flowchart which shows the process procedure example 1 of the PC preventive maintenance method of this embodiment. It is a flowchart which shows the process procedure example 2 of the PC preventive maintenance method of this embodiment. It is a flowchart which shows process sequence example 3 of the PC preventive maintenance method of this embodiment. It is a flowchart which shows process sequence example 4 of the PC preventive maintenance method of this embodiment.

Explanation of symbols

100 PC preventive maintenance system 101 storage means 102 program 103 memory 104 CPU
105 Input Interface 106 Output Interface 107 Communication Unit 110 Scheduling Unit 111 Restore Unit 112 Data Update Management Unit 113 Shipping Instruction Unit 114 Failure Prediction Unit 115 Backup Promotion Unit 120 Logistic Regression Analysis Application 125 PC Usage Status Table 126 PC Failure Prediction Information Table 127 PC Repair days table 128 Failure PC repair schedule table 129 Spare machine schedule table 130 End user attribute table 140 Network 200 PC
300 Shipping manager terminal 400 Backup management server

Claims (8)

Communication means for communicating with other devices;
A PC usage status table for storing PC usage status data, a PC failure prediction information table for storing failure occurrence probabilities on a predetermined date of the PC, a spare machine schedule table for storing data on lending status of spare PC machines, Storage means for storing
Data of failure occurrence probability of each PC is read from the PC failure prediction information table, a prevention target PC having a failure occurrence probability within a predetermined period is specified from the data, and a spare machine of the prevention target PC is selected. Scheduling means for searching in the spare machine schedule table and setting a loan date corresponding to the number of repair days of the PC to be prevented in the loan status of the spare machine,
For an apparatus that accesses the spare machine schedule table, identifies a corresponding spare machine for which the loan date for the prevention target PC is set in the lending status after the present, and manages backup data of the prevention target PC A restore unit that transmits an instruction to restore the backup data of the PC to be prevented to the corresponding scheduled backup machine via the communication unit;
In the PC usage status table, the process of recording the user ID of the PC to be prevented as the user ID of the scheduled spare machine, and the failure history of the repair location of the PC to be prevented after the repair days corresponding to the loan date A data update management means for performing a process of adding a repair status, a process of updating the usage status of the repaired part to an unused state, and a process of clearing the user ID set in the prevention target PC,
PC preventive maintenance system characterized by comprising.   Monitor the lending status of the scheduled spare machine in the PC usage status table, detect the arrival of a predetermined number of days before the lending date set for the scheduled standby machine, and in accordance with this detection, the prevention target 2. The apparatus according to claim 1, further comprising: a shipping instruction unit that transmits a shipping instruction of the scheduled spare device to a PC user via the communication unit to a terminal of a shipping manager of the standby device. PC preventive maintenance system. The storage means stores a logistic regression analysis application,
Read the usage status data of each PC from the PC usage status table, and input a plurality of types of data included in the usage status data as independent variables to the logistic regression analysis application called from the storage means, and each PC as a dependent variable 3. The PC preventive maintenance system according to claim 1, further comprising: a failure prediction unit that acquires a failure occurrence probability on a predetermined date of the date and stores the failure occurrence probability in the PC failure prediction information table.   The failure prediction means communicates with the PC being used by the user by the communication means every predetermined period, notifies the acquisition request of the usage status data of the corresponding PC, and the usage status returned by the corresponding PC in response to the acquisition request The PC preventive maintenance system according to claim 3, wherein data is stored in the PC usage status table. The PC failure prediction information table stores a failure occurrence probability and a failure location on a predetermined date of the PC in association with each other,
The storage means stores a PC repair days table storing data of repair days required for each PC failure location,
The scheduling means identifies a failure location in the PC to be prevented from the PC failure prediction information table, collates the identified failure location data with the PC repair days table, and is necessary for repairing the failure location. The number of repair days is specified, and the rental date corresponding to the number of repair days is set in the rental status of the spare machine of the PC to be prevented in the spare machine schedule table. The described PC preventive maintenance system.   The communication means communicates with the device managing backup data of the PC to be prevented by the communication means, and the backup data managed by the storage means by the device is specified with an update frequency of a predetermined standard or less, and specified here. For the backup data user's PC, the scheduling means is inquired whether the failure occurrence probability within a predetermined period is equal to or higher than a predetermined value, and the reply that the failure occurrence probability within the predetermined period on the PC is higher than a predetermined value 6. The PC prevention according to claim 1, further comprising backup promotion means for transmitting a reminder notice of backup processing to the PC through the communication means when the scheduling means is obtained from the scheduling means. Maintenance system. Computer
Communication means for communicating with other devices, a PC usage status table for storing PC usage status data, a PC failure prediction information table for storing a failure occurrence probability on a predetermined date of the PC, and a lending status of spare PCs A spare machine schedule table for storing the data, and storage means for storing the data,
Data of failure occurrence probability of each PC is read from the PC failure prediction information table, a prevention target PC having a failure occurrence probability within a predetermined period is specified from the data, and a spare machine of the prevention target PC is selected. Searching in the spare machine schedule table, and setting a loan date corresponding to the number of repair days of the prevention target PC in the loan status of the spare machine,
For an apparatus that accesses the spare machine schedule table, identifies a corresponding spare machine for which the loan date for the prevention target PC is set in the lending status after the present, and manages backup data of the prevention target PC , A process of transmitting an instruction to restore backup data of the prevention target PC to the corresponding scheduled spare machine via the communication unit;
In the PC usage status table, the process of recording the user ID of the PC to be prevented as the user ID of the scheduled spare machine, and the failure history of the repair location of the PC to be prevented after the repair days corresponding to the loan date A process of adding a repair status, a process of updating the usage status of the repaired part to an unused state, a process of clearing the user ID set in the prevention target PC,
PC preventive maintenance method characterized by executing. Communication means for communicating with other devices, a PC usage status table for storing PC usage status data, a PC failure prediction information table for storing a failure occurrence probability on a predetermined date of the PC, and a lending status of spare PCs In a computer comprising a spare machine schedule table for storing data, and storage means for storing
Data of failure occurrence probability of each PC is read from the PC failure prediction information table, a prevention target PC having a failure occurrence probability within a predetermined period is specified from the data, and a spare machine of the prevention target PC is selected. Searching in the spare machine schedule table and setting a loan date corresponding to the number of repair days of the prevention target PC in the loan status of the spare machine; and
For an apparatus that accesses the spare machine schedule table, identifies a corresponding spare machine for which the loan date for the prevention target PC is set in the lending status after the present, and manages backup data of the prevention target PC Sending an instruction to restore the backup data of the prevention target PC to the corresponding scheduled spare machine via the communication means;
In the PC usage status table, the process of recording the user ID of the PC to be prevented as the user ID of the scheduled spare machine, and the failure history of the repair location of the PC to be prevented after the repair days corresponding to the loan date A process of adding the repair status, a process of updating the usage status of the repaired part to an unused state, a step of clearing the user ID set in the prevention target PC,
PC preventive maintenance program characterized by causing

Images