JPH11188584A6 - Operation management apparatus, operation management method, and storage medium - Google Patents

Abstract

[PROBLEMS] Conventionally, when trouble occurs in a production line facility, the occurrence of the trouble is notified by turning on an alarm device such as a patrol light, but the detailed contents are assumed by checking the trouble code displayed on the operation panel. The cause was sequentially examined and responded. This work is based on empirical judgment, and there is a problem that an operator unfamiliar with the apparatus takes time for trouble recovery.
Operational data of facilities constituting a production line is collected, analysis of the operational data is performed to determine whether or not a trouble has occurred in the facility, and a trouble occurrence point is specified. The identified trouble occurrence locations are identified and displayed, and the corresponding cause items are displayed in order in descending order of the number of trouble occurrences that have occurred in the past. The said subject was solved by alert | reporting a trouble occurrence location and a cause by a combination display.
[Selection] Figure 6

Description

[0001]
Detailed Description of the Invention
BACKGROUND OF THE INVENTION
The present invention relates to an operation management device, an operation management method, and a storage medium for performing operation management of equipment devices constituting an automation line.
[0002]
[Prior art]
When trouble occurs in the normal production line, an alarm device such as a patrol light is activated to notify the operator of the trouble. An operator sees this and restores the troubled device, but at a glance, it may not be clear at which part of the device the trouble has occurred. In order to support the work, there is an apparatus that displays a phenomenon by displaying a trouble code on an operation panel attached to the equipment as shown in 201 of FIG. The operator compares the trouble code displayed in 201 with a trouble code correspondence table such as 202 to find out what trouble has occurred, and starts repair work. However, workers who are unfamiliar with the device know what trouble is occurring in this device, but it takes time to find out where it occurred and it takes time to recover the trouble. .
[0003]
[Problems to be solved by the invention]
Furthermore, as the devices become more complex and sophisticated, the types of troubles increase, and even though the trouble part is known, the cause of the trouble is occurring because the cause is unknown. In other words, the type and cause of the trouble is not necessarily a one-to-one correspondence with the equipment in which the trouble has occurred, and skill is required to investigate and resolve the cause, making rapid troubleshooting difficult. .
[0004]
[Means for Solving the Problems]
The present invention has been made in view of the above problems, and provides an operation management device and an operation management method that support trouble recovery work on a production line, thereby shortening the time until trouble recovery and preventing a reduction in the operation rate of the production line. The purpose is to do. For example, the identification display of trouble locations as shown in FIG. 5 and FIG. 6 and the display of the causes thereof are specifically listed, so that quick recovery work can be started regardless of empirical judgment.
[0005]
In order to solve the above problems, the present invention has the following configuration.
[0006]
That is, data collection means for collecting the operation data of the equipment constituting the production line, analyzing the operation data collected by the data collection means, determining whether or not trouble occurs in the equipment, Data analysis means for specifying the trouble, and a trouble display processing means for displaying in combination the identification display of the trouble occurrence location specified based on the result of the analysis and the cause of the trouble corresponding to the trouble occurrence location .
[0007]
The operation management device further includes trouble data storage means for storing display data for identifying and displaying the identified trouble occurrence location.
[0008]
Further, the operation management device further stores a trouble cause input processing means for inputting a trouble cause assumed for each trouble occurrence location, and a trouble cause input processed by the trouble cause input processing means. Trouble cause storage means.
[0009]
Further, the analysis means further analyzes the operation data of a plurality of facilities connected via a network, determines the presence / absence of a facility in which a trouble has occurred, and specifies the location where the trouble has occurred.
[0010]
The trouble display processing means further accumulates the number of times of the selection input when a true trouble cause is selected and inputted from among the displayed trouble causes, and the trouble is accumulated when a trouble occurs next. Causes of trouble are displayed in descending order.
[0011]
Further, the operation data is stored as data for clearly indicating a trouble occurrence location in a register provided for each facility.
[0012]
Further, the trouble display processing means colors and displays the trouble occurrence location in order to identify the trouble occurrence location of the equipment.
[0013]
In addition, a data collection process for collecting the operation data of the equipment constituting the production line, and the operation data collected by the data collection process are analyzed to determine whether or not trouble occurs in the equipment. A data analysis step for identifying the trouble, a trouble display processing step for displaying a combination of the trouble occurrence location identified based on the result of the analysis and the cause of the trouble corresponding to the trouble occurrence location. .
[0014]
The operation management method further includes a trouble data storage step of storing display data for identifying and displaying the identified trouble occurrence location.
[0015]
Further, the operation management method further stores a trouble cause input processing step for input processing of a trouble cause assumed for each trouble occurrence location, and a trouble cause input processed by the trouble cause input processing step. A trouble cause storage step.
[0016]
Further, the analysis step further analyzes the operation data of a plurality of facilities connected via a network, determines the presence / absence of a facility in which a trouble has occurred, and identifies the location where the trouble has occurred.
[0017]
Further, the trouble display processing step further accumulates the number of times of the selection input when a true trouble cause among the displayed trouble causes is selected and input, and when the trouble occurs next, the accumulation is performed. Causes of trouble are displayed in descending order.
[0018]
Further, the operation data is stored as data for clearly indicating a trouble occurrence location in a register provided for each facility.
[0019]
The trouble display processing step colors and displays the trouble occurrence location in order to identify the trouble occurrence location of the equipment.
[0020]
In addition, the data collection means for collecting the operation data of the equipment constituting the production line, the operation data collected by the data collection means are analyzed, the presence or absence of trouble occurrence of the equipment is determined, and the trouble occurrence location A data analysis means for specifying the trouble, a trouble display processing means for displaying in combination the identification display of the trouble occurrence location specified based on the result of the analysis and the cause of the trouble corresponding to the trouble occurrence location, It has a program to make it function.
[0021]
DETAILED DESCRIPTION OF THE INVENTION
[Embodiment 1] A first embodiment of the present invention will be described below with reference to the drawings.
[0022]
FIG. 1 is a system configuration diagram of an operation management apparatus according to the present invention. In FIG. 1, 101A to 101C are equipment devices (hereinafter “equipment”) constituting a production line. As shown in FIG. 1, it is possible to use a plurality of facilities that are targets of operation management. Reference numeral 102 denotes a network for sucking up operation data of equipment, and the operation management apparatus and equipment (101A, B, C) constituting the production line are connected via the network. Reference numeral 103 denotes data collection means for collecting equipment operation data via the network 102, and 104 denotes analysis means for analyzing whether or not an abnormality has occurred in the equipment from the collected operation data.
[0023]
The definition of how the equipment that is the target of operation management constitutes the production line is managed by the data collection means 103 via the input means 109 and stored in the secondary storage means 111. The secondary storage unit 111 is a storage device such as a RAM or a hard disk, and stores line configuration information according to the definition. The data collection means 103 reads equipment operation data based on the line configuration information.
[0024]
Reference numeral 105 denotes trouble display processing means that is activated by the analysis means 104 when it is determined that an abnormality has occurred in the equipment, and performs display processing of the equipment that has caused the trouble.
[0025]
Reference numeral 106 denotes trouble data storage means for storing data for indicating a trouble occurrence location of each facility. This is a database for storing equipment display data in which trouble has occurred based on the analysis result of the analysis means.
[0026]
Reference numeral 107 denotes a trouble cause input means for inputting the cause of the trouble that has occurred, and reference numeral 108 denotes a trouble cause storage means for saving the trouble cause input processed by the trouble input processing means 107. This is a database of input of possible causes for trouble.
[0027]
Reference numeral 109 denotes an input means such as a keyboard or a mouse. Reference numeral 110 denotes display means such as a display.
[0028]
Next, a specific operation of the operation management apparatus from when a trouble occurs in the facility until the cause of the trouble is displayed on the display means 110 will be described with reference to the flowchart of FIG.
[0029]
In step S301, the data collection unit 103 periodically reads the contents of the register provided in each facility. Each of the facilities (101A to 101C) has a memory for storing the operating state, and when a trouble occurs, a bit indicating the trouble occurrence is set in a designated register of the memory.
[0030]
The configuration will be described with reference to FIG. Here, one register is composed of 16 bits, and a trouble name is defined in a one-to-one relationship with each bit. At this time, when trouble A occurs in the facility, 1 is set to the 0th bit of the register of the address D001. By analyzing the bit data of the register, it is possible to confirm what kind of trouble has occurred in the facility.
[0031]
The data analysis unit 104 refers to a register in which trouble data is stored for each facility (101A to 101C) collected by the data collection unit (S302), and determines whether a trouble has occurred (S303). . For example, if trouble occurs in the limit sensor of the XY table, the trouble A is stored as data other than “0”.
[0032]
When the value of the referenced register is 0 (S303-No), it is determined that the normal operation is being performed or the trouble has been canceled, and the process proceeds to step S308. If the value of the register is other than 0 (S303-Yes), it is determined that a trouble has occurred because some bit is set, and the trouble display processing means 105 is activated (S304).
[0033]
The activated trouble display processing means 105 determines which equipment has trouble from the address data in which bit data other than 0 is stored, and specifies the equipment (S304).
[0034]
In the case where the line is composed of facilities 802, 803, 804, and 805 (FIG. 8), the trouble display processing means 105 displays “trouble occurrence” characters in order to identify and display the troubled equipment on the display means 110. It is displayed (S305). Here, the line configuration data (S309) is referred to.
[0035]
By displaying the trouble occurrence, it is possible to easily confirm which equipment has the trouble. Furthermore, the content of this trouble is selected and input from the input means 109 to the “trouble occurrence” display portion on the display means 110, and the screen is switched to display a screen for providing more detailed information ( FIG. 6).
[0036]
In step S 306, it is determined whether or not the operator has selected this “trouble occurrence” character by the input means 109. If it is selected (S306-Yes), the process proceeds to step S307.
[0037]
At this time, the trouble display processing means 105 specifies the facility causing the trouble by the address data (FIG. 4). For the identified equipment, the trouble display screen of the equipment stored in the trouble data storage means 106 is read and displayed (S307, S310). Further, the trouble location is specified by the bit data (FIG. 4), and the cause of trouble corresponding to each bit is read from the trouble cause storage means 108 and displayed (S307, S311). As a result, the display as shown in FIG. 6 can be made by combining the trouble occurrence location and the cause of the equipment from the trouble display of the equipment and the assumed trouble cause display.
[0038]
In FIG. 6, reference numeral 601 is an enlarged view of the trouble occurrence facility, and 602 is colored to identify and display the trouble occurrence location. Reference numeral 603 represents the name of the trouble that has occurred, and 604 represents the cause of the trouble that has occurred. The trouble cause data read here is input in advance by the trouble cause input means 108, but the operator can add, delete, or change the cause of the trouble by activating the trouble cause input means 108 whenever necessary. Is possible. The operator looks at this screen to identify the location where the trouble has occurred, and further performs recovery work that should be dealt with from the cause of the trouble.
[0039]
Even after the trouble occurs, the register value is periodically referred to. When the register value is “0”, the trouble location and the cause display are deleted (S308).
[0040]
[Effect of Embodiment 1] When trouble occurs in the equipment constituting the production line, by displaying the trouble occurrence location and the cause in combination, the problem can be solved without relying on empirical knowledge. Extraction is possible, and it is possible to shorten the time required for identifying the trouble occurrence point and investigating the cause of the trouble when performing the recovery work. Furthermore, since useless work time is eliminated, the facility is kept in the shortest state, so that the production rate of the production line can be prevented from being lowered.
[0041]
[Embodiment 2] In the first embodiment, the cause item data is listed based on the data input order. However, in the second embodiment, the occurrence frequency data is combined and combined with the occurrence frequency data to display the items in order of the occurrence frequency. To do.
[0042]
FIG. 7 shows the data structure of cause data items stored in the trouble cause data storage means and the number of selections for each item.
[0043]
The “number of times of selection” is that the item that was the cause of the true failure is input from the input unit 109 among the causes 604 displayed as the cause of the failure part of the failure facility, and stored in the trouble cause storage unit 108. The cumulative number of times.
[0044]
In the first embodiment, the data structure of the trouble cause data is only the trouble cause item (701). However, the trouble number data is combined with the data structure of the trouble cause storage means 108, and the cumulative value of the trouble occurrence number is stored in the database. (702).
[0045]
The true cause is selected and input by the operator via the input means 109 from the trouble causes (604 in FIG. 6) displayed by the trouble display processing means 105 (S901: FIG. 9) (S902). The accumulated value of the number of selections is counted up (S903) and stored in the trouble data storage unit (S904). Next, when a similar trouble occurs, the trouble display processing means 105 ranks the data string 702 in order of the frequency of occurrence when reading trouble cause data from the trouble cause storage means 106 (S905). Many trouble causes (selected as true causes by the worker) are displayed on the display means 110 (S901). Reference numerals 703 and 704 in FIG. 7 indicate data strings in which trouble causes are ordered in descending order of selection frequency. In step S901, the displayed cause data is displayed based on the ordered 703 and 704.
[0046]
[Effects of the second embodiment] By displaying the cause when trouble occurs in the equipment constituting the production line and displaying the rank in consideration of the number of occurrences, it is possible to cope with the cause of the high probability of trouble occurrence It becomes. By ordering items, the working time can be further shortened. The production management apparatus that feeds back site information to the system and provides information based on the result includes the function as an expert system.
[0047]
The time required to identify the location of trouble and to investigate the cause of the trouble during the recovery work is reduced, and unnecessary work time is eliminated, so that the facility is kept in a minimum state and the production line operating rate is prevented from being lowered. .
[0048]
In addition, the accumulated trouble occurrence frequency data cultivated here becomes data that should be called a problem in operation of the equipment, and can be valuable field data in the in-house production of the next model equipment development.
[0049]
[Other Embodiments]
Another object of the present invention is to supply a storage medium storing software program codes for implementing the functions of the above-described embodiments to a system or apparatus, and the computer (or CPU or MPU) of the system or apparatus stores the storage medium. Needless to say, this can also be achieved by reading and executing the program code stored in the.
[0050]
In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the storage medium storing the program code constitutes the present invention.
[0051]
As a storage medium for supplying the program code, for example, a floppy disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.
[0052]
Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) operating on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.
[0053]
Further, after the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing.
[0054]
When the present invention is applied to the above-mentioned storage medium, the program code corresponding to the flowchart described above is stored in the storage medium. In brief, each module shown in the memory map example of FIG. Is stored in a storage medium. That is, the program codes of at least the “data collection module 1001”, “data analysis module 1002”, “trouble display processing module 1003”, and “trouble cause input processing module 1004” may be stored in the storage medium.
[0055]
【The invention's effect】
According to the present invention, it is possible to shorten the time required for identifying the trouble location and investigating the cause of the trouble when performing trouble recovery work by displaying the cause of the trouble together with the trouble occurrence location in the facility where the trouble has occurred. , Thereby preventing a reduction in the production rate of the production line.
[0056]
In addition, when trouble occurs in the facility, it is possible to further reduce the time required to identify the cause of the trouble by displaying in the order of causes that have occurred in the past, and the trouble recovery work can be shortened.
[0057]
[Brief description of the drawings]
FIG. 1 is a diagram showing a system configuration of an operation management apparatus.
FIG. 2 is an explanatory diagram showing a trouble code and a correspondence table displayed on an operation panel.
FIG. 3 is a flowchart showing a processing procedure until trouble display is performed.
FIG. 4 is an explanatory diagram illustrating a configuration of a trouble register.
FIG. 5 is an explanatory diagram of a trouble location display in trouble equipment.
FIG. 6 is an explanatory diagram of a trouble facility display screen.
FIG. 7 is an explanatory diagram of a data configuration of a cause of trouble.
FIG. 8 is a diagram showing a display screen when a trouble occurs on the operation management system.
FIG. 9 is a flowchart for accumulating, storing, and displaying the number of trouble occurrences.
FIG. 10 is a diagram showing a memory map stored in a storage medium in the present embodiment.
[Explanation of symbols]
101A equipment 103 data collection means 104 data analysis means 105 trouble display processing means 107 trouble cause input processing means

Claims (15)

Data collection means for collecting operation data of the equipment constituting the production line;
Analyzing the operation data collected by the data collection means, determining whether or not trouble has occurred in the equipment, and data analysis means for specifying the trouble occurrence location;
Trouble display processing means for displaying in combination the identification display of the trouble occurrence location identified based on the result of the analysis and the trouble cause corresponding to the trouble occurrence location;
An operation management device characterized by comprising: The operation management apparatus according to claim 1, further comprising trouble data storage means for storing display data for identifying and displaying the identified trouble occurrence location. The operation management device further includes trouble cause input processing means for inputting a cause of trouble assumed for each trouble occurrence point,
Trouble cause storage means for storing the trouble cause input processed by the trouble cause input processing means;
The operation management apparatus according to claim 1, further comprising: The analysis unit further analyzes operation data of a plurality of facilities connected via a network, determines whether or not there is a facility in which a trouble has occurred, and identifies a location where the trouble has occurred. The operation management device described. The trouble display processing means further accumulates the number of selected inputs when a true trouble cause is selected and inputted from among the displayed trouble causes, and the accumulated when the trouble occurs next. The operation management apparatus according to claim 1, wherein trouble causes are displayed in descending order. The operation management apparatus according to claim 1, wherein the operation data is stored as data for clearly indicating a trouble occurrence location in a register provided for each facility. The operation management apparatus according to claim 1, wherein the trouble display processing means displays the trouble occurrence portion in a colored manner so as to identify the trouble occurrence portion of the facility. A data collection process for collecting operation data of the equipment constituting the production line;
Analyzing the operation data collected by the data collection step, determining whether or not trouble has occurred in the equipment, and a data analysis step for identifying a trouble occurrence point;
A trouble display processing step for displaying in combination the identification display of the trouble occurrence location identified based on the result of the analysis and the cause of the trouble corresponding to the trouble occurrence location,
An operation management method characterized by comprising: The operation management method according to claim 8, further comprising a trouble data storage step of storing display data for identifying and displaying the identified trouble occurrence location. The operation management method further includes a trouble cause input processing step for inputting a trouble cause assumed for each trouble occurrence point,
A trouble cause storing step for storing the cause of the trouble input by the trouble cause input processing step;
The operation management method according to claim 8, further comprising: 9. The analysis step further includes analyzing operation data of a plurality of facilities connected via a network, determining the presence or absence of a facility in which a trouble has occurred, and identifying the occurrence location of the trouble. The operation management method described. The trouble display processing step further accumulates the number of selection inputs when a true trouble cause is selected and inputted from among the displayed trouble causes, and then accumulates the trouble when a trouble occurs next. The operation management method according to claim 8, wherein trouble causes are displayed in descending order. The operation management method according to claim 8 or 11, wherein the operation data is stored as data for clearly indicating a trouble occurrence location in a register provided for each facility. 9. The operation management method according to claim 8, wherein in the trouble display processing step, the trouble occurrence place is colored and displayed in order to identify the trouble occurrence place of the facility. Data collection means for collecting operation data of the equipment constituting the production line;
Analyzing the operation data collected by the data collection means, determining whether or not trouble has occurred in the equipment, and data analysis means for specifying the trouble occurrence location;
Trouble display processing means for displaying in combination the identification display of the trouble occurrence location identified based on the result of the analysis and the trouble cause corresponding to the trouble occurrence location;
A storage medium comprising a program for causing a computer to function.