JP2014228895A - Replacement time calculation program, information processing apparatus, and replacement time calculation method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To calculate an appropriate component replacement time for reducing work man-hour or cost.SOLUTION: A computer receives a failure notification including operation temperature of a faulty component of a device to be managed, and operation time of the component until a failure, records the operation temperature and the operation time in association with each other in a database, calculates an average of the operation time for each operation temperature when the number of received failure notifications exceeds a threshold, and transmits the average to the device to be managed.

Description

  The present invention relates to an exchange time calculation program, an information processing apparatus, and an exchange time calculation method.

  In preventive replacement of parts used in computer devices, replacement times are calculated and set based on mean time between failures (MTBF) and failure rates at the time of development of products such as computer devices.

JP 2012-145977 A JP 2002-352024 A

  Devices such as computers vary in operating time and temperature at the installation location for each user who uses them. In addition, components such as hard disks and memories mounted on computers are made up of semiconductor components that have temperature characteristics such as being susceptible to failure (deterioration, etc.) at high temperatures. Come.

  However, since the part replacement time is presented based on information calculated at the time of product development, the system operating time and temperature for each user actually used are not reflected as conditions for determining the replacement time. .

  In other words, maintenance such as inspection and parts replacement is not necessarily performed at an appropriate timing, inspection is performed in a shorter period than the suggested cycle, and parts that do not need to be replaced are replaced (parts are compared). Operating at a low temperature) and cases where replacement is too late and leads to component failure before preventive maintenance (a case where the component is operating at a relatively high temperature). For this reason, there exists a problem which the work man-hour and cost which are spent for inspection and parts replacement | exchange increase.

  An object of the present invention is to calculate an appropriate part replacement time for reducing work man-hours and costs.

  A replacement time calculation program according to an embodiment includes a computer connected to a management target device via a network, and a failure notification including an operating temperature at the time of failure of a component of the management target device and an operation time until the failure of the component And records the operating temperature and the operating time in association with each other in the database, and calculates the average of the operating time for each operating temperature when the number of received failure notifications exceeds a threshold, Is transmitted to the device to be managed.

  According to the program of the embodiment, the part replacement time for each temperature can be calculated. The administrator replaces parts based on the replacement time corresponding to the actual user environment (operating temperature), and replaces parts that are expected to have a usable remaining period. In addition, the number of cases leading to component failure can be reduced, and the number of work steps and costs spent on inspection and replacement of components can be reduced.

1 is a configuration diagram of a system according to an embodiment. It is a block diagram of the server which concerns on embodiment. It is a figure which shows the example of a failure notification. It is a block diagram of the maintenance center which concerns on embodiment. It is a figure which shows the example of components management DB. It is a figure which shows the example of components management DB. It is a figure which shows the process of calculation of the average operation time for every temperature. It is a flowchart of the process of the system which concerns on embodiment. It is a detailed flowchart of component management DB update processing. It is a detailed flowchart of the average operation time calculation process for every temperature. It is a block diagram of information processing apparatus (computer).

Hereinafter, embodiments will be described with reference to the drawings.
FIG. 1 is a configuration diagram of a system according to an embodiment.

  The system 101 includes a server 201-i (i = 1 to n) and a maintenance center 301. The server 201 and the maintenance center 301 are connected via a network such as a local area network (LAN) or a wide area network (WAN).

  The server 201 is a device that executes various types of information processing. The server 201 is an example of an information processing device. The server 201 is a device that is managed by the maintenance center 301.

  The server 201 stores the replacement standard (replacement time) of each component included in the server 201, checks the operation time and replacement time of each component, and checks a predetermined condition (for example, when the operation time exceeds the replacement time, If the operating time is close to the replacement time, etc., the administrator is notified that the parts should be replaced (for example, a message is displayed on the display of the server 201 or an e-mail is sent to the administrator). To do.

  When a failure occurs, the server 201 transmits a failure notification including information regarding the failure (part name, manufacturing lot, temperature, operation time, etc.) to the maintenance center 301.

The maintenance center 301 receives a failure notification from the server 201 and calculates an average operating time for each temperature of the component. The maintenance center 301 transmits the calculated average operation time to the server 201.
The maintenance center 301 is an information processing apparatus such as a server, for example.

  The server 201 uses the average operating time received from the maintenance center 301 as the replacement reference (replacement time) because there is no difference between the temperature at the time of the failure and the operating temperature. If the exchange time has already been stored, the server 201 updates the received average operating time as a new exchange time.

As described above, the server 201 checks the operation time and replacement time of each component, and if a predetermined condition is satisfied, notifies the administrator that the component should be replaced.
When the administrator is notified of component replacement from the server 201, the administrator replaces the component.

  This reduces the number of cases where parts that can be used for the remaining remaining period are replaced and cases where replacement is too late and leads to part failure before preventive maintenance, reducing the work man-hours and costs spent on inspection and parts replacement. it can.

FIG. 2 is a configuration diagram of the server according to the embodiment.
The server 201-i includes a processing unit 211-i, a component information storage unit 221-i, and a sensor unit 231-i.

The processing unit 211-i is a processing device that executes various processes.
The processing unit 211-i includes a failure detection unit 212-i, an information collection unit 213-i, and an information transmission unit 214-i.

The failure detection unit 212-i detects a failure of a component included in the server 201-i.
The information collection unit 213-i collects information on the failed component and generates a failure notification. The content of the failure notification is acquired from the component information storage unit 221-i and the sensor unit 231-i.

FIG. 3 is a diagram illustrating an example of failure notification.
The failure notification includes the server, part name, production lot, temperature, and operation time.
The server is an identifier that identifies the server 201. The identifier is assigned to the server 201 in advance.

The part name is the name or type of the part.
The production lot indicates a production lot of parts.
The temperature is the temperature of the component when a failure is detected.
The operation time is the total operation time of the parts, that is, the time during which the parts have operated without failure.

  The information transmission unit 214-i transmits the failure notification generated by the information collection unit 213-i to the maintenance center 301. Note that the information transmission unit 214-i is not limited to the time of failure detection, but also includes information on the components included in the server 201 (including the server, component name, manufacturing lot, temperature, and operation time as in the case of the failure notification). You may send to. As a result, the maintenance center 301 stores the received information on the components of each server 201 and can obtain the information on the components of all the servers 201 as well as the server 201 in which a failure has been detected.

  The component information storage unit 221-i stores information on components included in the server 201-i. The component information storage unit 221-i is, for example, a semiconductor chip called Serial Presence Detect (SPD) mounted on a memory.

  The component information storage unit 221-i stores information such as a component name, a manufacturing lot, an operating time, and a temperature. The part name is the name or type of the part. The production lot indicates a production lot of parts. The operation time is the total operation time of the parts, that is, the time during which the parts have operated without failure. The temperature is the temperature of the part.

  The sensor unit 231-i is a sensor that measures the operating temperature of the component. The sensor unit 231-i notifies the information collection unit 214-i of the measured temperature. Further, the sensor unit 231-i may notify and store the measured temperature in the component information storage unit 221-i.

FIG. 4 is a configuration diagram of the maintenance center according to the embodiment.
The maintenance center 301 includes a processing unit 311 and a storage unit 321.

The processing unit 311 is a processing device that executes various processes.
The processing unit 311 includes an information acquisition unit 312, a database (DB) processing unit 313, a condition determination unit 314, a statistical processing unit 315, and a transmission unit 316.

The information acquisition unit 312 receives a failure notification from the server 201.
The DB processing unit 313 reads and writes the component management DB 331.

The condition determination unit 314 determines whether or not the condition for calculating the average operation time for each temperature is satisfied.
The statistical processing unit 315 calculates an average operating time for each temperature.
The transmission unit 316 transmits the calculated average operation time to the server 201.

The storage unit 321 is a storage device that stores data. The storage unit 321 is, for example, a magnetic disk device (hard disk drive (HDD)), a solid state drive (SSD), or the like.
The storage unit 321 stores a component management DB 331.

5A and 5B are diagrams illustrating examples of the component management DB.
5A shows the component management DB when the failure notification is received and the content of the failure notification is described, and the component management DB 331-2 of FIG. 5B shows the component when the average operation time is calculated. The management DB is shown.

  In the component management DB 331, a server, a component name, a manufacturing lot, a quality control target value, a cumulative number of failure notifications up to now, a temperature, an operating time, and an average operating time are described in association with each other.

The server is an identifier that identifies the server 201.
The part name is the name or type of the part.
The production lot indicates a production lot of parts.

  The quality control target value is a threshold value used for determining whether to calculate the average operation time. The quality control target value is set for each production lot of the part name. For example, in the parts management DB 331-1 shown in FIG. 5A, the quality control target value for part name = memory manufacturing lot = A is 5000, the quality control target value for manufacturing lot = B is 7000, and the quality control target value for manufacturing lot = C. Is 6000.

  The cumulative number of failure notifications to date is the number of failure notifications received so far. The cumulative number of failure notifications up to now is counted for each production lot of the part name. As shown in FIG. 5A, when the failure notification is received and the content of the failure notification is described, the record is incremented by 1 for each record in each manufacturing lot in the order in which the records are described in the manufacturing lot column. The number is written as follows. As shown in FIG. 5B, when the average operation time is calculated, the number of failure notifications received so far corresponding to the production lot of the part name is described.

The temperature is the temperature at the time of failure detection.
The operation time is the total operation time of the parts, that is, the time during which the parts have operated without failure.
The average operation time is an average of the operation times of the parts having the corresponding temperature.

FIG. 6 is a diagram illustrating processing for calculating the average operating time for each temperature.
In FIG. 6, a case will be described in which the maintenance center 301 receives the failure notification 251-j from the server j (j = 1 to 9) and calculates the average operating time for each temperature based on the failure notification 251-j.

First, a failure notification 251-j is notified from the server j to the maintenance center 301.
The maintenance center 301 receives the failure notification 251-j and records the content of the failure notification 251-j in the component management DB 331.

  The contents of the failure notification 251-1 are server = 1, component name = memory, production lot = A, operation time = 30000H, temperature = 26 degrees.

  The contents of the failure notification 251-2 are server = 2, part name = memory, production lot = A, operation time = 20000H, temperature = 28 degrees.

  The contents of the failure notification 251-3 are server = 3, part name = memory, production lot = A, operation time = 27000H, temperature = 26 degrees.

  The contents of the failure notification 251-4 are server = 4, part name = memory, production lot = A, operating time = 22000 H, temperature = 28 degrees.

  The contents of the failure notification 251-5 are server = 5, part name = memory, production lot = A, operation time = 15000H, temperature = 30 degrees.

  The contents of the failure notification 251-6 are server = 6, part name = memory, production lot = A, operation time = 16000H, temperature = 30 degrees.

  The contents of the failure notification 251-7 are server = 7, part name = memory, production lot = A, operation time = 27000H, temperature = 26 degrees.

  The contents of the failure notification 251-8 are server = 8, part name = memory, production lot = A, operation time = 14000H, temperature = 30 degrees.

  The contents of the failure notification 251-9 are server = 9, part name = memory, production lot = A, operation time = 21000H, temperature = 28 degrees.

  When the number of failure notifications exceeds the quality control target value, the maintenance center 301 calculates the average operating time for each temperature. Here, nine failure notifications 251-1 to 251-9 are received, and the number of failure notifications (= 9) exceeds the quality control target value.

  Since the temperatures of the failure notifications 251-1, 251-3, and 251-7 are 26 degrees, the maintenance center 301 calculates the average operating time of the failure notifications 251-1, 251-3, and 251-7. Thereby, the average operation time when the temperature is 26 degrees is calculated as 28000 (= (30000 + 27000 + 27000) / 3) H.

  Similarly, the average operation time when the temperature is 28 degrees is calculated as 21000H, and the average operation time when the temperature is 30 degrees is calculated as 15000H.

FIG. 7 is a flowchart of processing of the system according to the embodiment.
Here, a case where a failure has occurred in the server 201-1 will be described. Note that the processing of the servers 201-2 to 201-i is the same as that of the server 201-1, and a description thereof will be omitted.

In step S501, the quality control target value is input to the maintenance center 301.
In step S502, the component management DB 331 is expanded in the storage unit 321.

In step S503, the server 201-1 starts operation.
In step S504, it is assumed that a failure has occurred in a component in the server 201-1. The failure detection unit 212-1 detects a failure of the component.

  In step S505, the information collection unit 213-1 acquires information regarding the failed component from the component information storage unit 221-1. In addition, the information collection unit 213-1 acquires the current temperature, that is, the temperature at the time of failure, from the sensor unit 231-1. The information collection unit 213-1 creates a failure notification based on the collected information. The temperature may use information stored in the component information storage unit 221-1. The contents of the failure notification are as described with reference to FIG. Then, the information transmission unit 214 notifies the maintenance center 301 of a failure notification.

  Thereafter, step S506 is executed in the server 201-1, and steps S508 to S510 are executed in the maintenance center 301, respectively.

  In step S506, the user stops the server 201-1 and replaces the failed part. Then, the control returns to step S503, and the server 201-1 starts operation.

  In step S508, the information acquisition unit 312 receives a failure notification. The DB processing unit 313 performs component management DB update processing. Details of the component management DB update process will be described later.

  In step S509, the condition determination unit 314 compares the quality management target value in the component management DB with the cumulative number of failure notifications up to now for each component name and each production lot. If the cumulative number of failure notifications is less than or equal to the quality control target value, the process ends. If the cumulative number of failure notifications is greater than the quality management target value, control proceeds to step S510.

  In step S510, the statistical processing unit 315 performs an average operation time calculation process for each temperature. Details of the average operation time calculation process for each temperature will be described later.

  In step S511, the transmission unit 316 transmits the exchange reference information to the server 201. The replacement standard information includes a part name, a manufacturing lot, a temperature, and a calculated average operating time. Note that the transmission unit 316 transmits the replacement reference information to the server 201 having the same part name, production lot, and temperature as the part name, production lot, and temperature corresponding to the calculated average operating time. The maintenance center 301 receives and stores information (part name, manufacturing lot, temperature, etc.) of the parts included in each server 201 from each server 201, and the transmission unit 316 stores information on the parts included in each server 201. The server 201 that transmits the exchange reference information is determined. Further, the transmission unit 316 may transmit the exchange reference information to all the servers 201.

  The server 201 that has received the exchange reference information stores the exchange reference information in the server 201. The server 201 sets the average operation time as the replacement time. In addition, when the server 201 has already stored the replacement time corresponding to the part name, the manufacturing lot, and the temperature included in the replacement reference information, the server 201 updates the received average operating time as a new replacement time.

As described above, the server 201 checks the operation time of each component and the replacement time corresponding to the component name, manufacturing lot, and temperature of the component. If the predetermined condition is satisfied, the server 201 replaces the component with the administrator. Notify that you should.
When the administrator is notified of component replacement from the server 201, the administrator replaces the component.

FIG. 8 is a detailed flowchart of the component management DB update process.
FIG. 8 corresponds to step S508 in FIG.
In step S601, the information acquisition unit 311 receives a failure notification.

  In step S <b> 602, the DB processing unit 313 checks whether or not the part management DB 331 has the same part name and manufacturing lot item as the part name and manufacturing lot included in the failure notification. If the part management DB 331 has the same part name and manufacturing lot item as the part name and manufacturing lot included in the failure notification, the control proceeds to step S604, and the same part name and manufacturing lot as the part name and manufacturing lot included in the failure notification. If the production lot item is not in the parts management DB 331, the control proceeds to step S603.

  In step S603, the DB processing unit 313 describes the server, part name, manufacturing lot, temperature, and operation time included in the failure notification in the bottom column of the part management DB 331. Furthermore, the DB processing unit 313 writes the quality control target value corresponding to the part name and the manufacturing lot included in the failure notification in the bottom column of the part management DB 331.

  In step S604, the DB processing unit 313 displays the server, part name, manufacturing lot, temperature, and operation included in the failure notification in the bottom column of the component management DB 331 corresponding to the component name and manufacturing lot included in the failure notification. Enter the time.

  In step S605, the DB processing unit 313 describes “accumulated number of failure notifications to date” corresponding to the record described in step S603 or step S604. Specifically, the DB processing unit 313 indicates the number of the part name and the manufacturing lot column corresponding to the record as the “accumulated number of failure notifications to date” corresponding to the described record. Describe.

FIG. 9 is a detailed flowchart of the average operation time calculation process for each temperature.
FIG. 9 corresponds to step S510 in FIG.

  In step S701, the statistical processing unit 315 refers to the component management DB 331, and calculates the number of failure notifications (records) for each temperature of the records corresponding to the part name and the production lot that satisfy the quality management target value <the failure notification cumulative number. calculate. For example, in FIGS. 5A and 5B, the number of failure notifications for parts name = memory and manufacturing lot = A temperature = 30 degrees is two.

  In step S <b> 702, the statistical processing unit 315 refers to the component management DB 331, and calculates the total operation time for each temperature of the record corresponding to the component name and the production lot that satisfy the quality management target value <the failure notification cumulative number. For example, in FIGS. 5A and 5B, the total of the operation time when the part name = memory and the production lot = A temperature = 30 degrees is 13000 (= 8000 + 5000).

  In step S703, the statistical processing unit 315 divides the total operation time for each temperature by the number of failure notifications for each temperature, and calculates an average operation time for each temperature. For example, in FIGS. 5A and 5B, the average operation time when the part name = memory and the production lot = A temperature = 30 degrees is 6500 (= 13000/2). The statistical processing unit 315 describes the calculated operation time for each temperature in the component management DB 331.

FIG. 10 is a configuration diagram of an information processing apparatus (computer).
The server 201 and the maintenance center 301 of the embodiment are realized by an information processing apparatus 1 as shown in FIG. 10, for example.

  The information processing apparatus 1 includes a CPU 2, a memory 3, an input unit 4, an output unit 5, a storage unit 6, a recording medium drive unit 7, and a network connection unit 8, which are connected to each other by a bus 9.

  The CPU 2 is a central processing unit that controls the entire information processing apparatus 1. The CPU 2 corresponds to the processing units 211 and 311.

  The memory 3 is a Read Only Memory (ROM) or Random Access Memory (RAM) that temporarily stores a program or data stored in the storage unit 6 (or the portable recording medium 10) during program execution. It is memory. The CPU 2 executes the various processes described above by executing a program using the memory 3.

  In this case, the program code itself read from the portable recording medium 10 or the like realizes the functions of the embodiment.

The input unit 4 is, for example, a keyboard, a mouse, a touch panel, or the like.
The output unit 5 is, for example, a display, a printer, or the like.

  The storage unit 6 is, for example, a magnetic disk device, an optical disk device, a tape device, or the like. The information processing apparatus 1 stores the above-described program and data in the storage unit 6 and reads them into the memory 3 and uses them as necessary.

The storage unit 6 corresponds to the storage unit 321.
The recording medium driving unit 7 drives the portable recording medium 10 and accesses the recorded contents. As the portable recording medium, any computer-readable recording medium such as a memory card, a flexible disk, a compact disk read only memory (CD-ROM), an optical disk, and a magneto-optical disk is used. The user stores the above-described program and data in the portable recording medium 10 and reads them into the memory 3 and uses them as necessary.

  The network connection unit 8 is connected to an arbitrary communication network such as a LAN or WAN, and performs data conversion accompanying communication.

DESCRIPTION OF SYMBOLS 101 System 201 Server 211 Processing part 212 Failure detection part 213 Information collection part 214 Information transmission part 221 Parts information storage part 231 Sensor part 301 Maintenance center 311 Processing part 312 Information acquisition part 313 DB processing part 314 Condition determination part 315 Statistical processing part 316 Transmission unit 321 Storage unit 331 Component management DB
401 network

Claims (4)

A failure notification including an operating temperature at the time of failure of a component of the managed device and an operation time until the failure of the component is received from the managed device to a computer connected to the managed device via a network,
Record the operating temperature and the operating time in association with each other in a database;
When the number of received failure notifications exceeds the threshold, calculate the average of the operating time for each operating temperature,
An exchange time calculation program for executing a process of transmitting the average to the managed device. The failure notification further includes a part name of the part and a production lot of the part,
In the recording process, the part name, the manufacturing lot, the operating temperature, and the operation time are recorded in the database in association with each other,
In the process of calculating the average, the number of records of the same part name and manufacturing lot as the part name and manufacturing lot of the received fault notification recorded in the database corresponds to the part name and manufacturing lot of the received fault notification. The replacement time calculation program according to claim 1, wherein an average of the operation time for each of the operating temperatures is calculated within a part name and a manufacturing lot of the received failure notification when a threshold value to be exceeded is exceeded. An information processing apparatus connected to a management target apparatus via a network,
A receiving unit that receives from the managed device a failure notification including an operating temperature at the time of failure of the component of the managed device and an operation time until the time of the failure of the component;
A storage unit for storing a database described in association with the operating temperature and the operation time;
When the number of received failure notifications exceeds a threshold, a calculation unit that calculates an average of the operation time for each operating temperature;
A transmission unit for transmitting the average to the managed device;
An information processing apparatus comprising: An exchange time calculation method executed by an information processing apparatus connected to a management target apparatus via a network,
A failure notification including an operating temperature at the time of failure of a component of the managed device and an operation time until the failure of the component is received from the managed device;
Record the operating temperature and the operating time in association with each other in a database;
When the number of received failure notifications exceeds the threshold, calculate the average of the operating time for each operating temperature,
An exchange time calculation method including a process of transmitting the average to the management target device.