JPH0756960A - Facility equipment usage history collection device - Google Patents

Abstract

PURPOSE:To group a usage history in accordance with on-load status concentrically by detecting an operation execution instruction from a control and integrating as the usage history, and evaluating by collecting updated latest usage history information classified by every equipment. CONSTITUTION:The usage history information in history memory 3a, 3b provided at facility equipment 2a, 2b, respectively are updated at need by an update controller 9 based on actual using time or the number of times of usage detected by a usage status detector 5. The usage status detector 5 monitors the operation execution instruction and an operation completion confirming signal for the facility equipment 2a, 2b from a controller 1, and detects the on-load status of the facility equipment. The update controller 9 updates the usage history information by integrating the usage time or the number of times of usage detected by the usage status detector 5 with the usage history information accumulated in the history memory 3a, 3b, and a reliability evaluation device 8 classified by every equipment predicts the deterioration of each equipment due to secular change from the usage history information of the facility equipment 2a, 2b stored in a history data base 7.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a facility equipment use history collecting device used for centrally managing the use history of facility equipment.

[0002]

2. Description of the Related Art In a production facility such as a robot or machine tool in a production facility such as a factory, and a facility device such as a control device for controlling and managing them, connected by a network, a so-called FA system, use of each device The history is an important guideline for predicting the occurrence of equipment failure, preventing serious failure accidents that affect the entire system, and managing and operating the entire system.

Conventionally, in order to grasp and manage the use history of each facility equipment of such FA system, depending on the device, particularly in the case of a computer or the like, it is necessary to look at the operating time of the CPU which is automatically integrated by the system command. This is used as the usage history because some types of equipment and devices are capable of automatically counting the number of operations and displaying them on a counter. In addition, in the facility equipment that does not have such a function of counting the operating status, the number of working days and the working time from the use start date and time of each equipment are specified for each specific period, or as shown in FIG. The start date and end date of use of the equipment were recorded in a book, the usage history of each equipment was grasped, and the equipment was managed and operated.

In order to diagnose whether or not the conventional equipment moves properly, or to diagnose the cause of a failure, a portion of the equipment that is likely to be loaded is predicted at the time of design, and the load is predicted based on the prediction at the time of design. Decide a rule (this is called a general rule) for diagnosing a part that is prone to damage, or a part that is prone to failure in some cases, and diagnose equipment according to this rule.
In each facility device, the part to which the load is likely to be applied varies depending on the environment in which it is installed, the connection of an additional configuration different from the basic configuration, and the operating conditions. In other words, each device has its own characteristic failure habit, so it is necessary to carefully diagnose this part. Therefore, from the usage history of the equipment described above, find the usage status unique to that equipment,
A diagnostic rule (this is called a local rule) unique to each device is created, and this is added to the general rule to diagnose the equipment.

FIG. 9 is a block diagram showing a configuration of an equipment diagnostic apparatus 100 for performing this conventional diagnosis. In the diagnostic rule section 101, a general rule at the time of design and a local rule unique to each device are distinguished. The configuration data of the connected robots 11, 12 and 13 is stored in the mechanical configuration data section 102. Then, the signal detection unit 57 detects a control signal or a failure signal of the robot controller 10, and the inference engine 104 diagnoses the equipment according to the diagnosis rule to determine whether the equipment is normal or where the cause of the failure is. Is being diagnosed.

[0006]

However, in the conventional method of grasping and managing the usage history of the equipment as described above, the worker checks the usage period and the display of the counter for each equipment. I have to turn around and also FA
To manage each equipment as a whole system,
It is necessary to calculate the usage history individually for each device and collect statistics as a whole. Therefore, a large F
In the case of the A system, this alone requires a lot of labor, which makes it difficult to perform efficient management and operation, which is a problem in grasping the usage status of the equipment as the entire system.

Further, only by grasping the period from the start of use, the operating time, etc., the load status due to the actual operation of the equipment is not always accurately expressed, but for example, the operating status. In the case of an operating device that has a movable part even during energization indicating that, the deterioration and wear due to aging due to the operation of the movable part, and the energization time indicating that it is simply operating are not always required. In the case of equipment that is not in a proportional relationship and has a long period (or time) during energization but a short actual operating time (or number of times), there is a considerable period of inactivity. As a result, there is a problem in that the usage history used for managing and operating each equipment does not represent the load status of the actually operating equipment.

Further, the diagnosis rule for diagnosing the equipment is not sufficient for one equipment even if the equipment is of the same type, in order to make a diagnosis in consideration of the load status peculiar to each equipment. Therefore, in order to add a diagnostic rule specific to each device to each device, it is necessary to construct a diagnostic rule for each of the equipment devices. Therefore, there is a problem that a lot of time and labor are required. When constructing this diagnostic rule, it is created by grasping what kind of failure habits are caused based on the usage history of each equipment and device, so the usage history itself is It is premised that the load situation is correctly grasped, and as described above, there is a possibility that the usage history itself may not be grasped sufficiently, so it is difficult to construct an accurate diagnostic rule for the equipment itself. There was also a problem that there was.

Therefore, an object of the present invention is to provide facility equipment capable of grasping the usage history more closely matched to the load status due to actual operation in each equipment equipment in the FA system and performing centralized management. It is to provide a usage history collecting device.

[0010]

The present invention for achieving the above object provides a use history collecting device for equipment, which is operated by an operation execution command from a control device for controlling a plurality of equipment, Usage history storage means for storing usage history information of each equipment for each of the plurality of equipment, and operation execution commands for the plurality of equipment from the control device are monitored to detect the usage status of the equipment. And a usage history information stored in the usage history storage means by integrating the usage status detected by the usage status detection means with the usage history information stored in the usage history storage means. And usage history information updating means for updating the usage history information, and usage history management means for collecting the usage history information in the usage history storage means and managing the usage history for each of the facility devices. Door is equipment use history collection apparatus according to claim.

Further, according to the present invention, the usage history storage means provided for each of the plurality of equipments has information defining a failure state and a cause of failure of the equipment. It is a facility equipment usage history collection device described.

[0012]

In the facility equipment use history collecting apparatus of the present invention configured as described above, the use history storage means is provided for each of the plurality of facility equipment, so that the use history of each facility equipment from the start of use is recorded. It can be stored as usage history information, and by the usage status detection means, monitor the operation execution command from the control device to the equipment, and detect the actual operation time, the number of operations or the failure state as the usage of the equipment, By using the usage history information updating means to integrate the usage history information stored in the usage history storage means and updating the usage history information stored in the usage history storage means As the device use history, the use history of each facility device can always be grasped as the latest use history.

Then, by collecting the usage history information by the usage history management means, the usage history of each equipment is centrally managed as the usage history of the load state due to the actual operation of each equipment. Is.

Further, since the use history storage means of the present invention has information defining the failure state and the cause of failure of the equipment, the failure characteristic of the equipment can be diagnosed. .

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below with reference to the accompanying drawings. Example 1 FIG. 1 is a block diagram showing an example of equipment provided with a facility equipment usage history collection device of the present invention.

In this equipment, the control device 1 issues an operation execution command to each equipment 2a and 2b, and each equipment 2
A and 2b are controlled.

Further, as a facility equipment use history collection device according to the present invention, a history memory 3a which is a use history storing means for storing use history information of each equipment 2a and 2b.
And 3b, and each equipment 2a, 2b from the control device 1.
Usage command for detecting the operation execution command to the device, and the usage history detector 5 which is the usage status detection means for detecting the actual operation time or the number of times of operation of each equipment, and the usage history for updating the usage history information in the usage history memories 3a and 3b An update controller 9 which is information updating means, a usage history database 7 and a device-based reliability evaluation device 8 which constitute usage history management means are provided.

The function of each part of the equipment device use history collection device according to the present invention will be described. First, the history memories 3a and 3b are provided in the equipment devices 2a and 2b, respectively, and are detected by the use state detector 5. Based on the actual use time or the number of times of use, the update controller 9 updates the use history information, which is the stored content, at any time. The history memory is preferably a readable / writable non-volatile memory such as a magnetic disk, a magnetic card, or an IC memory card. In the illustrated case, the history memories 3a and 3b are attached to the respective equipments 2a and 2b, but this does not have to be attached in particular, and may be in the control device, for example. ,
It may be located in a completely different place, and may be installed in a corresponding form so that the usage history of each facility device can be stored. However, when considering the transfer of equipment, it is more convenient to attach the equipment to each equipment than to install them separately.

Next, the usage condition detector 5 completes its operation in response to the operation execution command from the control device 1 to each equipment 2a and 2b and each equipment 2a and 2b to this operation execution instruction. Monitor the confirmation signal to inform that
By counting the time during this time by the attached timer 4, the actual use time in which the equipment is actually operating with a load on the equipment is detected as an operating condition.

When it is preferable to detect the operating status of the equipment as the number of times rather than the operating status as the time, for example, ON / O such as a switch.
Detects the number of FFs and the number of repetitive movements as the usage status for equipment that performs repetitive movements, such as equipment that moves from one position to another and returns to the original position. To do.

The detected usage time and usage count are temporarily stored for use in updating usage history information, which will be described later.

Normally, in the equipment in which the equipment and the control device are separated from each other as in the present embodiment, it is indicated by the control device side that the operation is completed in response to the operation execution command from the control device. For confirmation, the equipment device outputs a confirmation signal notifying that the operation is completed. Therefore, by detecting this confirmation signal, the time or the number of times that the equipment is actually operated can be counted as the operation status due to the fact that the equipment is loaded and operated. When such a confirmation signal is not output, the time required for the operation is set in advance, and the time is counted as the time after the operation execution instruction is detected, so that the operation time can also be obtained. Good,
In the case of the number of times, it may be counted by detecting the operation execution instruction.

Further, the usage history detector 5 is input with information such as replacement of parts of each equipment and a resting state due to a failure, so that the equipment actually starts operating or is in a resting state. It also counts the period of non-operation.

Next, the update controller 9 reads and writes the usage history information accumulated in the history memory 3a or 3b, and the history memory 3a or 3b.
The usage history information accumulated in the above is accumulated with the usage time or the number of times of usage detected by the usage status detector 5, the usage history information is updated, and the history memory 2a or 3b is again written and stored therein. Device-based reliability evaluation device 8
In response to the request, the usage history information stored in the history memory 3a or 3b is read and supplied.
Note that it is preferable to use wireless communication to transfer information between the update controller 9 and the history memories 3a and 3b. This is because it is possible to avoid interference with other equipment and freely arrange the equipment without worrying about the wiring of the equipment. Of course, if there is radio interference, connect by wire.

Next, the device-based reliability evaluation device 8 is connected to the update controller 9 from the network 6 load,
It has a history database 7 for keeping track of the usage history of each equipment 2a, 2b in the entire equipment, and from the usage history information of each equipment 2a, 2b stored in this history database 7, the equipment Another reliability is evaluated, and deterioration or wear due to aging of each device, which is one of the causes of failure, is predicted.

A history database (abbreviated as history D / B in the case of FIG. 7) 7 has a facility database 2a and 2 respectively.
The use history information of b is updated by the update controller 9 in response to a request from the device-based reliability evaluation apparatus 8 for each history memory 3a, 3
Read from b and always store the latest one. Then, the device-based reliability evaluation device 8 is used from time to time or as needed, from the history database 7 to the facility devices 2a and 2b.
The usage history information of is read and the reliability of each device is evaluated. For this reliability evaluation, for example, the failure strength rate, the failure frequency rate, the MTBF (mean failure interval), etc. are evaluated.
It also outputs a list of equipment that is actually used and equipment that is idle.

The evaluation of the above-described evaluation items is performed by integrating the usage history of the most heavily loaded part of each equipment. For example, in the case of a robot,
The parts that are most heavily loaded are the reduction gears, bearings, wiring and piping, and thermal stress in high-voltage circuits.The history used to evaluate failures in these parts is the integration time of the servo power supply that operates the robot. To obtain.
In automated equipment, contact relays, contact switches and sensors, operation buttons, sliding parts of pneumatic cylinders,
Since the load is applied to the sliding parts of the hydraulic cylinder, the bearings of the motor, the bearings of the movable parts, etc., there is an operation command to each device from the number of operation inputs, the cycle, and the number of step starts depending on the number of times the operation button is pressed as usage history. It is judged that the operation time or the number of times of operation of the part is added up.

In the present embodiment, a dedicated history database 7 is attached to the equipment-based reliability evaluation device 8, but this is to make it possible to evaluate the reliability at any time, and the present invention is not always necessary. For example, the reliability evaluation may be performed by directly extracting the usage history information from the history memories 3a and 3b for reliability evaluation without providing the history database 7. However, in that case, the history memory 3 in which the reliability evaluation is being performed
During reading of the usage history information from a and 3b, inconvenience occurs such that the history memories 3a and 3b cannot be updated. Therefore, it is preferable to have an independent history database 7 as in this embodiment if possible. .

Next, the operation of collecting the use history of each equipment in the equipment provided with the equipment use history collection device of the present invention will be described with reference to the flow chart shown in FIG.

First, when the equipments 2a and 2b are installed, the fact that the equipments 2a and 2b are installed in the usage status detector 5 is input as an initial input (S1).

The entire facility is in operation and the facility equipment 2a or 2
An operation execution command is issued from the control device 1 to b, and the timer 4 is operated by detecting the operation execution command and the equipment to which the equipment is to be used (S2) (S3).

Then, the use status detector 5 detects a confirmation signal of operation completion (S4) to stop the timer 4 (S5), and the time between these is set as the actual use time.
It is temporarily stored together with which equipment is operated (S6).

Next, the usage history information is read from the history memory 3a or 3b of the equipment in which the update controller 9 has operated, the actual usage time temporarily stored in the usage status detector 5 is added to the usage history information, and the addition is made. The usage history is updated by writing the used usage history information in the history memory 3a or 3b (S7).

This update of the usage history can be carried out at any time by being triggered by the temporary storage, so that the latest usage history can always be stored in the history memory 3a or 3b. In the flow chart described above, the usage time is collected as a log, but the usage history may be the number of times of use.

Next, the operation of evaluating the reliability based on the collected usage history will be described with reference to the flow chart shown in FIG.

For the reliability evaluation for each device, first, as described above, the history memories 3a and 3 are classified by the facility devices 2a and 2b.
The usage history information stored in b is classified and stored in the history database 7 attached to the equipment-based reliability evaluation device 8 for each equipment of all equipment in the equipment. This includes
In response to a request from the device-based reliability evaluation apparatus 8, the latest usage history information is read from the history memories 3a and 3b through the network 6 using the usage history information reading function of the update controller 9 and stored in the history database 7 ( S11).

Next, the equipment to be evaluated is selected (S12), the usage history information of the selected equipment is read from the history database 7, and the evaluation of each evaluation item is executed (S1).
3), and outputs the result (S14).

As described above, the evaluation items include, for example, the failure strength rate, the failure frequency rate, and the MTBF, and the evaluation method is as described above. In addition to the evaluation, the operating state of the equipment actually used and a list of the equipment that is not in operation are output.

It should be noted that the use history information for each equipment 2a, 2b of the history database 7 used for this reliability evaluation is updated every time the information in the history memories 3a, 3b of each equipment is updated. Alternatively, it may be obtained from the history memories 3a and 3b again each time the reliability evaluation is performed.

Embodiment 2 Next, an embodiment in which the facility equipment use history collection device of the present invention is applied as a facility equipment diagnostic device will be described.

FIG. 4 is a diagram showing the configuration of the diagnostic device according to the second embodiment.

As shown in the figure, each of the robots 11, 12 and 13, which are equipments, stores local rule storage units 21, 22 and 23 to which usage history storage means is applied and mechanical configuration data of each robot. The mechanical diagnostic data storage units 31, 32, and 33 are provided, and the facility diagnostic device 50 includes a general rule 51, which is a diagnostic rule at the time of design, and local rules collected from the local rule storage units 21, 22, and 23. Is stored for use during diagnosis, a local rule storage area 52 is stored, a mechanical configuration data storage area 53 is stored for use during diagnosis of robot mechanical configuration data, a general rule and each robot are stored. An inference engine with a function as a usage history management means that diagnoses each robot based on the collected local rules. 54, a local rule processing unit 55 that is a usage history updating unit that creates and updates a new local rule when a general rule or an existing local rule cannot be diagnosed, a local rule storage unit 21 in each robot, 22 and 23 and the mechanical configuration data storage units 31, 32 and 33, each local rule and each mechanical configuration data is collected, and when the update is performed, the updated rules and data are written in the respective storage units. I / O processing unit 56 and robot controller 1
It is composed of a signal detecting section 57 which is a use status detecting means for monitoring a control signal and a failure signal from 0.

The data structure of the local rule and mechanical configuration data used is as shown in FIGS. 5 and 6, for example. The data structure of the local rule (see FIG. 5) is for which robot the local rule belongs to. Robot ID for identifying whether the local rule is changed, a change flag for indicating that the local rule has been changed, and a local rule part defining a failure state and a cause of failure. Part B is if (A)
It is defined like the then (B).

The mechanical configuration data (see FIG. 6) includes information such as a robot ID for identifying the robot, types of axes, amplifiers and motors, I / O No and I / O.
It consists of comments.

The operation of the equipment diagnostic device 50 is as follows. First, when the diagnostic device is activated, the I / O processing unit 56 causes the robot 1 to operate.
Local rule storage unit 2 attached to 1, 12, 13
The local rules are collected from 1, 22, and 23 and stored in the local rule storage area 52, respectively. Similarly,
The mechanical configuration data of each robot is collected and stored in the mechanical configuration data storage area 53. The rules and data stored in the local rule storage area 52 and the mechanical configuration data storage area 53 are stored so as to identify which robot they belong to, as shown in the data structure.

In the diagnosis of each robot, the signal detection unit 57 detects the control signal or the failure signal in the controller of the robot, detects the operation signal of each robot or the failure signal at the time of the robot failure, and detects the control signal or the failure. The inference engine 54 compares the signal with the general rule and the local rule to diagnose each robot.

If the general rule or the existing local rule alone cannot be used for accurate diagnosis, the local rule processing unit 55 makes the general rule (or the existing local rule) redundant. Is created and registered in the local rule storage area 52, and the local rule is updated. At this time, the update flag of the local rule of the corresponding robot is set to "1" indicating that the rule has been updated.

When the diagnosis is completed, the local rule in the local rule storage area 52 in which the local rule has been changed is stored in the local rule storage section of the corresponding robot.
It is stored through the / O processing unit 56.

As a result, from the next time onward, accurate diagnosis can be performed by the new local rule.

The above operation will be described with reference to the flowchart shown in FIG.

First, the equipment diagnostic device is started (S5).
0), the I / O processing unit collects respective mechanical configuration data and local rules from all the robots and stores them in a predetermined storage area (S51).

Next, when a failure occurs, the general rule, the local rule, and the mechanical configuration data are read out to make a diagnosis (S52).

It is judged whether or not the diagnosis result is obtained (S5
3) If no diagnostic result is obtained, search for a rule that has a place where the diagnostic result could not be specified in the execution part, register the reverse of the condition part of the rule as a local rule, and The change flag is set to "1" (S54).

When the diagnosis result is obtained, it is judged whether or not the diagnosis end processing is to be performed (S56), and when it is ended, the change flag of the local rule is checked (S67) and the change flag is "1". Overwrite the local rule of “” with the local rule of the corresponding robot (S58)
End the diagnosis.

Here, a more specific diagnostic operation will be described by taking a robot having a three-axis structure as an example. The robots 11, 12 and 13 are of the same type and have a three-axis structure, and each axis is operated at the limit of motor power.

As a general rule for diagnosing the robots 11, 12 and 13, it is predicted at the time of design that the first axis (gravitational axis) of the robot of this kind is most loaded. Therefore, a failure result of positioning failure is expected due to the failure of the gravity axis.

As a general rule for this, a rule indicating that a positioning failure due to the gravity axis is likely to occur is described as follows. if (gravitational axis) then (positioning failure is likely to occur) This rule defines that the result of the execution unit B occurs if the cause of the condition A is as described above.

However, since only the robot 11 has a wider working range than the other robots 12 and 13 and the movable amount of the third axis is operated at the limit of its specification, the gravity axis is actually the cause. In the case where the positioning error is more likely to occur due to the third axis than in the case where the positioning error occurs, the failure called positioning failure occurs. As for the cause of the faulty result of the execution part such as the positioning failure, only the rule having a condition part called the gravity axis is prescribed, so it is diagnosed whether or not the gravity axis is a failure. However, in reality, there is no problem with the gravity axis, and the cause of failure cannot be identified after all.

Therefore, a rule having an execution part that causes a positioning error is searched from the general rule (and the local rule if it already exists), the condition part of the rule is reversed, and the gravity axis Create a local rule that can diagnose other axes. Specifically, the rule is if (! Gravity axis) then (positioning failure is likely to occur) (however ,! Indicates that it has been reversed).

Then, the formed rule is stored in the local rule storage area and the change flag is set to "1".

At the end of diagnosis, the local rule with the change flag of "1" is stored in the local rule storage section of the corresponding robot. Therefore, a more accurate diagnosis result can be obtained.

As described above, each robot is used as a local rule, which is a unique diagnostic rule necessary for diagnosing a usage history that differs depending on the usage status of the robot such as the characteristic failure status of the robot and its cause. By storing and storing the data, when the robot is moved or its operation is changed, appropriate robot diagnosis can be performed without checking the usage status of the robot and creating new local rules specific to the robot. It becomes possible to do.

[0063]

As described above, the facility equipment use history collection device of the present invention is a facility equipment use history collection device that operates according to an operation execution command from a control device that controls a plurality of facility devices. The operating history storage means for storing the usage history information for each of the plurality of equipment devices is provided, and the operation execution command from the control device to the plurality of equipment devices is monitored, and the actual operation time or the number of times of operation of the equipment device is monitored. Is detected by the usage status detection means, and this is integrated as a usage history, and the usage history information updating means updates the usage history information in the usage history storage means, and the latest usage history information is collected for each device to obtain the usage history. Since it was decided to evaluate by management means, reliability evaluation for each equipment and centralized management of the inventory status of suspended equipment, and deterioration and wear of equipment due to aging Etc. to predict, it can help prevent failure.

Further, by providing the usage history storage means for each equipment, it is possible to know the usage history of the equipment even when it is used for other equipment by moving or changing the arrangement of the equipment. Therefore, it is possible to perform an appropriate facility diagnosis.

[Brief description of drawings]

FIG. 1 is a block diagram of equipment of an embodiment using an equipment device usage history collection device of the present invention.

FIG. 2 is a flowchart for explaining a usage history collecting operation according to an embodiment using the equipment device usage history collecting device of the present invention.

FIG. 3 is a flowchart for explaining a reliability evaluation operation according to an embodiment using the equipment device usage history collection device of the present invention.

FIG. 4 is a block diagram of an equipment diagnostic device of an embodiment using the equipment device usage history collection device of the present invention.

FIG. 5 is a diagram illustrating a data structure of a local rule.

FIG. 6 is a diagram for explaining a data structure of mechanical configuration data.

FIG. 7 is a flow chart for explaining a facility diagnosis operation according to an embodiment using the facility equipment use history collection device of the present invention.

FIG. 8 is a diagram showing an example of a conventional book for grasping a usage history.

FIG. 9 is a block diagram showing a configuration of a conventional equipment device diagnosis apparatus.

[Explanation of symbols]

1 ... Control device, 2a, 2b
… Facilities equipment 3a, 3b… History memory,
4 ... Timer, 5 ... Usage detector,
6 ... network, 7 ... history database,
8 ... Device-based reliability evaluation device, 9 ... Update controller, 10 ... Controller, 1
1, 12, 13 ... Robot, 21, 22, 23 ... Local rule storage unit 31, 31, 32, 33 ... Mechanical configuration data storage unit, 50 ... Facility diagnostic device, 51 ... General rule,
52 ... Local rule storage area, 5
3 ... Mechanical configuration data storage area, 54 ... Inference engine, 55 ... Local rule processing unit, 5
6 ... I / O processing unit, 57 ... Signal detection unit.

Claims (2)

[Claims] 1. A usage history collection device for equipment that operates according to an operation execution command from a control device that controls a plurality of equipment, wherein usage history information for each equipment is provided for each of the plurality of equipment. A usage history storage means for storing the usage history, a usage status detection means for monitoring an operation execution command from the control device to the plurality of equipment devices, and detecting a usage status of the equipment equipment; Usage history information updating means for integrating the usage history information stored in the usage history storage means and updating the usage history information stored in the usage history storage means, and the usage history storage means. 2. A facility device use history collecting device, comprising: a use history management unit that collects the use history information of 1. and manages a use history for each of the facility devices. 2. The facility according to claim 1, wherein the use history storage means provided for each of the plurality of facility devices has information defining a failure state and a cause of failure of the facility device. Equipment usage history collection device.