JP2001084276A - Failure-monitoring system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To notify a preliminarily specified monitor of a failure before the failure is manifested by a collecting and analyzing information and data about a daily operational situation. SOLUTION: This system is provided with a database 2 storing product operational situation data, a parameter table 3 arranging failure occurrence predictive algorithm and a failure occurrence predictive condition as parameters, a failure occurrence predicting part 4, which collects the number of failure data cases from the database 2 according to the failure occurrence predictive algorithm read by referring to the table 3 and discriminates, whether the number of failure data cases meets the failure occurrence predictive condition, and a mail transmitting part 5 which receives alert message transmission notification from the part 4, when the number of failure data cases meets the failure occurrence predictive condition, refers to the table 3 and transmits an alert message to an alert notification destination.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a fault monitoring system for monitoring the operating status of a plurality of products in a market, predicting the occurrence of a fault, and preventing the fault before it occurs and preventing the expansion when a fault occurs.

[0002]

2. Description of the Related Art Conventionally, after a product has been put on the market, whether the product is operating normally, or whether any failure factors are latent or already apparent, is mainly determined by periodic patrol inspections and customer inspections. Monitoring was made by contacting the operator with a failure or claim.

[0003]

The monitoring of trouble factors that are latent in a product put on the market is based on information and data on the daily operation status of many identical products or similar products delivered to many customers. However, since the trouble monitor must collect and analyze the problem, there is a problem that a great deal of labor and time are required.

It is an object of the present invention to provide a fault monitoring system that collects and analyzes information and data relating to daily operating conditions and notifies a specified monitoring person before a fault becomes apparent.

[0005]

In order to achieve the above object, a fault monitoring system according to the present invention comprises a database for accumulating product operation status data, a fault occurrence prediction algorithm, and a fault occurrence prediction condition. The data table is obtained by a parameter table in which the parameters are arranged as parameters and a fault occurrence prediction algorithm selected with reference to the parameter table.
A failure occurrence prediction unit that collects the number of failure data from the data and determines whether the failure occurrence prediction condition is satisfied, and a warning message from the failure occurrence prediction unit when the number of failure data meets the failure occurrence prediction condition. -Receive notification of page
A mail sending unit for sending a warning message to an alarm notification destination with reference to the table.

[0006]

Embodiments of the present invention will be described with reference to the drawings. Elements common to the drawings are denoted by the same reference numerals. FIG. 1 is a configuration diagram of the fault monitoring system of the present invention. The fault monitoring system 1 includes an operation information database 2 (hereinafter, referred to as database 2) and a parameter database.
Cable 3, a failure occurrence predicting unit 4, and a mail transmitting unit 5,
The failure prediction unit 4 collects the number of failure data from the database 2 by using a failure prediction algorithm selected with reference to the parameter table 3 and determines whether the failure prediction condition is satisfied. If the number of fault data satisfies the fault occurrence prediction condition, a notification of a warning message is output to the notification mail transmitter 5, and the mail transmitter 5 receives the parameter.
A warning message is transmitted to the warning notification destination with reference to Table 3.

In the present embodiment, the database 2 is hard-wired.
And the parameter table 3 is stored in the memory 7, and the fault occurrence predicting unit 4 and the mail transmitting unit 5 are connected to the CP.
Build with U8. The memory 7 also stores a failure occurrence prediction algorithm, a warning message, and an alarm notification destination corresponding to the parameters of the parameter table.

FIG. 2 is an explanatory diagram of a fault information database format. The hard disk 6 has information on product history such as the customer name, product name, model number, serial number, date of manufacture, etc. shown in FIG. 2, and inspection items and problems when maintenance and inspection are performed. , Information on maintenance history such as actions, date and time of occurrence when a failure occurs, failure classification, phenomenon,
Language data or code data is accumulated in accordance with a predetermined format in association with information relating to a trouble history such as a treatment.

FIG. 3 is an explanatory diagram of the parameter table. The memory 7 has information on items shown in FIG. 3, such as a failure occurrence prediction algorithm, monitoring start date, monitoring end date, product type, delivery destination, error code, coefficients as failure occurrence prediction conditions, The parameters are assigned to the alarm message format, the alarm notification destination, etc., respectively, and the parameter table 3 is stored in a file format for recording all the parameters in the row direction.

Next, the operation will be described with reference to FIG. FIG. 4 is a flowchart showing the operation of the fault monitoring system.
It is.

In step S1, the CPU 8 sets the parameter
Referring to Table 3, a failure occurrence prediction algorithm is selected. For example, it is assumed that the failure occurrence prediction algorithm for record NO1 shown in FIG. 3 is selected, "P2 error in P1 month / P3 delivery destination, P4 error in previous month ...".

In step S2, the CPU 8 collects failure data from the hard disk 6 into the memory 7 by referring to the parameter table 3 by a failure occurrence prediction algorithm.
In the case of the example, the failure occurrence prediction algorithm includes “P2 model / P3 delivery destination in P1 month, P4 error in previous month.
.. ", The data corresponding to the items corresponding to the parameters P1 to P4 are collected in the memory 7 from the database shown in FIG. The fault data applicable to the item corresponding to the parameter P4 is "error code" in FIG.
The number of cases.

In step S3, the CPU 8 compares whether the number of collected "error codes" satisfies the failure prediction condition of the parameter P5.

In step S4, the CPU 8 executes the "error
If the number of "C" satisfies the failure occurrence prediction condition, the process branches to step S5; otherwise, the process ends.

In step S5, the CPU 8 sets the parameter
With reference to the parameters P6 and P to P9 of the cable 3, the alarm message and the alarm notification destination (previously specified monitor) are read out, the alarm message is transmitted through the LAN 9, and the process is terminated.

According to the present embodiment, the fault monitoring system is started at a fixed time every day and is operated 24 hours a day, 365 days a year, thereby enabling continuous monitoring and early prediction of fault occurrence.

[0017]

Since the present invention is configured as described above, it has the following effects. By providing a database for storing product operation status data,
Labor and man-hours for information collection can be reduced.

Since the failure occurrence prediction condition is made a parameter, the parameter can be changed without changing the software, so that a flexible failure prediction can be made.

By automating the analysis of the operation information for predicting the occurrence of a failure and the processing of predicting the occurrence of a failure, labor and man-hours for analysis and processing can be reduced.

When a failure occurrence prediction condition is satisfied, a warning message is automatically sent by e-mail, so that prompt failure prevention measures can be taken.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a fault monitoring system according to the present invention.

FIG. 2 is an explanatory diagram of a failure information database format.

FIG. 3 is an explanatory diagram of a parameter table.

FIG. 4 is a flowchart showing the operation of the fault monitoring system.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Fault monitoring system 2 Operation information database 3 Parameter table 4 Fault occurrence prediction part 5 Mail transmission part

Claims (1)

[Claims] 1. A database for accumulating product operation status data, a parameter table in which a failure prediction algorithm and a failure prediction condition are arranged as parameters, and the parameter table. A failure occurrence prediction unit that collects the number of failure data from the database and determines whether the failure occurrence prediction condition is satisfied by a failure occurrence prediction algorithm selected with reference to FIG. Receives a warning message transmission notification from the failure occurrence prediction unit when the failure occurrence prediction condition is satisfied,
A failure sending system for sending a warning message to an alarm notification destination by referring to the parameter table.