JP6961850B1 - Operation monitoring device and operation monitoring method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To present to a user information contributing to improvement of productivity and quality in a factory. An operation monitoring device detects a problem event that has occurred in a device on a production line based on a sensor record database, records the detected problem event in a problem event table in association with the time of occurrence, and the problem. The problem event detection unit that selects the problem event recorded in the event table and the time of occurrence of the selected problem event on the operation state transition diagram showing the time-series operating state of the device are the time of the operating state transition diagram. The problem event detection unit is associated with the detected problem event, including a display control unit for displaying on the axis and an operation reception unit for allowing the user to input the cause of the problem event in which the occurrence time is displayed. The input cause of the occurrence is recorded in the problem event table. [Selection diagram] Fig. 1

Description

The present invention relates to an operation monitoring device and an operation monitoring method.

For the purpose of improving productivity and quality in factories, in factories with mature processes, forms (daily production report, equipment management records, quality) that associate quantitative data that can be obtained from factory equipment with information input by workers, etc. Records, etc.) are systematically operated and managed.

On the other hand, in emerging factories, quantitative data can be obtained from factory equipment, but it is often not systematically operated and managed as a form, which hinders the improvement of productivity and quality.

Regarding the acquisition of quantitative data from factory equipment, for example, Patent Document 1 describes a power data acquisition unit 11 for acquiring time-series data of physical quantities consumed or generated when the production equipment 3 executes processing, and electric power. From the time-series data acquired by the data acquisition unit 11, the operation information of the production equipment 3 is obtained by using the one-cycle detection unit 21 that detects the time-series data at a predetermined time and the time-series data detected by the one-cycle detection unit 21. An operation information output device including an operation information acquisition unit 20 to be acquired is described.

Japanese Unexamined Patent Publication No. 2010-250382

The operation information output device described in Patent Document 1 has a problem that is considered to be a cause of deterioration of a key performance indicator (hereinafter referred to as a production KPI (Key Performance Indicator)) related to production based on quantitative data acquired from factory equipment. The event can be detected. However, since there is no established method for efficiently associating and managing the information recorded by workers, such as the cause of the detected problem event and the coping method, the detected problem event is produced in the factory. It cannot be fully utilized for improving sex and quality.

The present invention has been made in view of such a situation, and an object of the present invention is to be able to present to a user information that contributes to improvement of productivity and quality in a factory.

The present application includes a plurality of means for solving at least a part of the above problems, and examples thereof are as follows.

In order to solve the above problem, the operation monitoring device according to one aspect of the present invention acquires sensor information indicating the state of the device arranged on the production line, and associates the acquired sensor information with the time to create a sensor performance database. The problem event that occurred in the device of the production line is detected based on the sensor information acquisition unit accumulated in the sensor information acquisition unit and the sensor record database, and the detected problem event is recorded in the problem event table in association with the occurrence time. , The problem event detection unit that selects the problem event recorded in the problem event table and the operation state transition diagram showing the operation state of the device in time series are displayed, and the selected problem event occurrence time is operated. It includes a display control unit that displays on the time axis of the state transition diagram, and an operation reception unit that allows the user to input the cause of the problem event whose occurrence time is displayed on the time axis of the operating state transition diagram. The problem event detection unit is characterized in that the input cause of occurrence is recorded in the problem event table in association with the detected problem event.

According to the present invention, it is possible to present to the user information that contributes to the improvement of productivity and quality in the factory.

Issues, configurations, and effects other than those described above will be clarified by the description of the following embodiments.

FIG. 1 is a diagram showing a configuration example of an operation monitoring device according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of a KPI problem event DB (database). FIG. 3 is a diagram showing an example of a KPI cause tracking master DB. FIG. 4 is a flowchart illustrating an example of the operation monitoring process. FIG. 5 is a diagram showing a display example of the production KPI screen. FIG. 6 is a diagram showing a display example of the operating state transition screen. FIG. 7 is a diagram showing a display example of the cause input screen. FIG. 8 is a diagram showing a display example of the cause code mark. FIG. 9 is a diagram showing a display example of the problem event cause display column. FIG. 10 is a diagram showing a display example of the cause code Pareto chart.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In addition, in all the drawings for explaining the embodiment, in principle, the same members are designated by the same reference numerals, and the repeated description thereof will be omitted. Further, in the following embodiments, it goes without saying that the components (including element steps and the like) are not necessarily essential unless otherwise specified or clearly considered to be essential in principle. stomach. In addition, when saying "consisting of A", "consisting of A", "having A", and "including A", other elements are excluded unless it is clearly stated that it is only that element. It goes without saying that it is not something to do. Similarly, in the following embodiments, when the shape, positional relationship, etc. of a component or the like is referred to, the shape, etc. It shall include those similar to or similar to.

<Structure example of operation monitoring device 10 according to one embodiment of the present invention>
FIG. 1 shows a configuration example of an operation monitoring device 10 according to an embodiment of the present invention.

The operation monitoring device 10 detects a problem event that could be a cause of a decrease in production KPI in the factory based on the quantitative data obtained from the factory equipment, and causes the user to input the cause of the detected problem event and the countermeasures. It is for recording and displaying these in association with each other.

The operation monitoring device 10 includes each functional block of a processing unit 11, a storage unit 12, an input unit 13, an output unit 14, and a communication unit 15.

The operation monitoring device 10 includes a processor such as a CPU (Central Processing Unit), a memory such as a DRAM (Dynamic Random Access Memory), a storage such as an HDD (Hard Disk Drive) and an SSD (Solid State Drive), a keyboard, a mouse, a touch panel, and the like. It consists of an input device, an output device such as a display, and a general computer such as a personal computer provided with a communication module such as a NIC (Network Interface Card).

The processing unit 11 is realized by a computer processor. The processing unit 11 has functional blocks of an information acquisition unit 111, a production KPI calculation unit 112, a problem event detection unit 113, an operation reception unit 114, and a display control unit 115. These functional blocks are realized by the processor of the computer executing a predetermined program loaded in memory. However, a part or all of these functional blocks may be realized as hardware by an integrated circuit or the like. Further, a part or all of these functional blocks may be arranged on a so-called cloud server.

The information acquisition unit 111 connects to the sensor 32 provided in the equipment (plurality of devices) 31 arranged in the production line 30 via the communication unit 15 and the network 20, and obtains the equipment 31 state detected by the sensor 32. Acquire the sensor information (quantitative data) to be represented.

The information acquisition unit 111 records the acquired sensor information in the sensor record DB 121 of the storage unit 12 in association with the time. In addition to whether each device of the equipment (plurality of devices) 31 is in operation or stopped, the sensor 32 can be used for exchanging lots of members input to each device as a processing target, and for a machine operator. Changes, production numbers of each device, temperature, pressure, sound, and vibration, and abnormalities of processed products output from each device (dimensional abnormalities, transport position abnormalities, etc.) can be detected.

The production KPI calculation unit 112 refers to the sensor performance DB 121, calculates a plurality of types of production KPIs for each time zone having a predetermined time width (for example, one hour width) in each process, and produces production KPI information 1221 ( As FIG. 2), it is recorded in the KPI problem event DB 122. For example, the production KPI calculation unit 112 calculates the production amount, lead time, operating rate, defect rate, overall equipment effectiveness, etc. as the production KPI.

The problem event detection unit 113 refers to the sensor record DB 121, detects the problem event in the production line 30, and records the problem event table 1222 showing the detection result in the KPI problem event DB 122 of the storage unit 12. For example, the problem event detection unit 113 detects device stoppage, device work efficiency decrease, defective disposal, reprocessing, retention, machine side worker absence, machine side worker efficiency decrease, and the like as problem events in the production line 30. .. Further, the problem event detection unit 113 selects from the problem event table 1222 the problem event that occurred in the time zone in which the production KPI selected by the user is decreasing and the predetermined time immediately before that (for example, 30 minutes ago). Further, the problem event detection unit 113 refers to the KPI cause-related table 1231 (FIG. 3), and further selects the selected problem events that can cause the type of production KPI selected by the user.

The operation reception unit 114 receives various operations input by the user using the input unit 13. The display control unit 115 refers to each DB of the storage unit 12 to generate various screens (for example, the production KPI screen 200 (FIG. 5)) and displays them on the display of the output unit 14. The generated various screens can be displayed on the display of the information terminal 40 connected via the communication unit 15 and the network 20.

The storage unit 12 is realized by the memory and storage of the computer. The storage unit 12 stores the sensor record DB 121, the KPI problem event DB 122, the KPI cause tracking master DB 123, and the process master DB 124. Information other than these may be stored in the storage unit 12.

The sensor record DB 121 records time-series sensor information acquired by the information acquisition unit 111.

In the KPI problem event DB 122, the production KPI information 1221 representing the values of various production KPIs for each time zone in each process calculated by the production KPI calculation unit 112 is recorded. Further, in the KPI problem event DB 122, a problem event table 1222 including information on the problem event in the production line 30 detected by the problem event detection unit 113 is recorded.

FIG. 2 shows an example of the problem event table 1222 recorded in the KPI problem event DB 122. In the problem event table 1222, as the detection result by the problem event detection unit 113, the problem code representing the problem event that has occurred, the start date and time and the end date and time of the problem event, are shown in association with the device code representing each device forming the equipment 31. And the cause code is recorded. The cause code is information indicating the cause of the problem event and is input by the user.

Return to FIG. In the KPI cause tracking master DB 123, the KPI cause-related table 1231, the KPI table 1232, the problem table 1233, and the cause table 1234 (all of FIG. 3) used for tracking the cause of the decrease in the production KPI are recorded in advance. There is.

FIG. 3 shows an example of the KPI cause related table 1231, the KPI table 1232, the problem table 1233, and the cause table 1234 recorded in the KPI cause tracking master DB 123.

The KPI cause-related table 1231 represents a problematic event that can cause a decrease in production KPI. In other words, the KPI cause-related table 1231 excludes in advance problem events that cannot be logical as the cause of the decrease in the specific production KPI among the problem events that can occur, and causes the decrease in the production KPI. This is to enable quicker tracking of problematic events. In the KPI cause-related table 1231, a problem code representing a problem event that can cause a decrease in the production KPI represented by the KPI code is recorded in association with the KPI code representing the type of production KPI. The KPI cause related table 1231 can be edited by the user.

In the KPI table 1232, the names of production KPIs and the like are recorded in association with various KPI codes. The KPI table 1232 is used to generate the production KPI screen 200.

In the problem table 1233, the names of problem events and the like are recorded in association with the problem code. In the cause table 1234, the cause of the problem event is recorded in association with the cause code. The cause table 1234 is used to display the correspondence between the cause code and the cause of the problem event to the user who selectively inputs the cause code on the cause input screen 220.

Return to FIG. In the process master DB 124, the arrangement of devices belonging to a plurality of processes (also referred to as shops) in the production line 30, a worker, a member to be processed, and the like are recorded in association with each other.

The input unit 13 is realized by an input device of a computer. The input unit 13 is for the user to input various operations. The output unit 14 is realized by a computer display. The output unit 14 displays various screens.

The communication unit 15 is realized by a communication module of a computer. The communication unit 15 connects to the sensor 32 and the information terminal 40 of the production line 30 via the network 20 and communicates predetermined data.

The network 20 is a two-way communication network including a LAN (Local Area Network), a WAN (Wide Area Network), a mobile phone communication network, and the like.

The production line 30 includes equipment 31 composed of a plurality of devices and sensors 32 provided for each device. The production line 30 is divided into a plurality of processes (also referred to as shops), and a plurality of devices are arranged in each process.

The information terminal 40 is composed of a general computer and is used by users of various management levels such as a supervisor, a person in charge, a maintenance person, and a machine-side worker of the production line 30. The information terminal 40 can display various screens generated by the operation monitoring device 10.

<Operation monitoring process by operation monitoring device 10>
Next, FIG. 4 is a flowchart illustrating an example of the operation monitoring process by the operation monitoring device 10.

As a premise, it is assumed that the sensor record DB 121 of the storage unit 12 records the time-series sensor information acquired by the information acquisition unit 111 from the sensor 32 of the production line 30 so far. Further, it is assumed that the production KPI calculation unit 112 calculates various production KPIs for each time zone based on the sensor record DB 121 up to the present and records them in the KPI problem event DB 122. Further, the problem event detection unit 113 detects the problem event that has occurred in each device of the production line 30 based on the sensor record DB 121 up to now, and the problem event table 1222 showing the detection result is the KPI problem event of the storage unit 12. It is assumed that it is recorded in DB 122.

The operation monitoring process is started, for example, in response to a predetermined start operation from the user.

First, the display control unit 115 includes a production KPI change diagram 204 showing time-series changes of various production KPIs in each process with reference to the production KPI information 1221 recorded in the KPI problem event DB 122 of the storage unit 12. The production KPI screen 200 (FIG. 5) is generated and displayed on the display as the output unit 14 (step S1).

FIG. 5 shows a display example of the production KPI screen 200. On the production KPI screen 200, a date selection field 201 for the user to select and input a date, a process selection field 202 for selecting and inputting a process, and a production KPI selection field 203 for selecting and inputing a type of production KPI. Is provided. Then, on the production KPI screen 200, the production KPI change diagram 204 corresponding to the date, process, and type of production KPI selected and input in the date selection field 201, the process selection field 202, and the production KPI selection field 203 is displayed by a bar graph. Will be done. The production KPI change diagram 204 is not limited to the bar graph, and may be displayed by another graph such as a line graph.

The user can select a time zone in which he / she wants to track the cause of the decrease in the production KPI by selecting, for example, the bar in the production KPI change diagram 204 displayed as a bar graph.

Return to FIG. Next, the operation reception unit 114 receives a time zone selection operation from the user for the production KPI change diagram 204 on the production KPI screen 200 (step S2).

Hereinafter, the user indicates the third process in the process selection column 202 of the production KPI screen 200, the operating rate in the production KPI selection column 203, and the time zone from 10:00 to 11:00 in the production KPI change diagram 204. The description continues as selected.

Next, the problem event detection unit 113 refers to the time zone selected by the user and the predetermined time immediately before that (for example, 30 minutes), that is, the process master DB 124, and the process selected by the user (in this case, the first step). The device arranged in (3 steps) is specified, and the problem event that occurred between 09:30 and 11:00 in the specified device is selected from the problem event table 1222 (step S3). Next, the problem event detection unit 113 refers to the KPI cause-related table 1231, and can be the cause of the type of production KPI (in this case, the operating rate) selected by the user among the problem events selected in step S3. Those are further selected (step S4).

Next, the display control unit 115 generates an operating state transition screen 210 (FIG. 6) that displays the problem event selected in step S4, and displays it on the display as the output unit 14 (step S5).

FIG. 6 shows a display example of the operating state transition screen 210. The process display column 211, the operating state transition diagram 212, and the Pareto diagram display button 215 are displayed on the operating state transition screen 210. The process display column 211 shows the process (in this case, the third process) selected by the user in the process selection column 202 of the production KPI screen 200 (FIG. 5).

The operating state transition diagram 212 shows a time-series operating state of a plurality of devices (in the case of FIG. 6, devices M001 to M010 in the third process) arranged in a process selected by the user. A solid line is displayed during the time when each device is operating, and during the time when the problem event occurs, the problem event mark 213,214, which can be specified during the time when the problem event does not occur, is displayed. Is displayed.

The problem event mark 213 represented by a thick solid line indicates that the user is requested to input the cause of the problem event, and when the user selects the problem event mark 213, the cause input screen 220 (FIG. 7) is displayed. Is displayed. The problem event mark 214 represented by the thick broken line indicates that the user is not requested to input the cause of the problem event. As for the problem event that does not require the cause input, for example, it is assumed that the problem event occurs in advance and the time of occurrence is registered in advance. The problem event marks 213 and 214 may be distinguished by changing the color or blinking one of them, in addition to the method of distinguishing between the solid line and the wavy line.

The Pareto chart display button 215 is a button for instructing the display of the Pareto chart showing the frequency of occurrence of the cause of the problem event in the process and the type of production KPI selected by the user. When the Pareto chart display button 215 is operated, the cause code Pareto chart 250 (FIG. 10) is displayed superimposed on the operating state transition diagram 212.

The user can change the selected process in the process display field 211, and the operating state transition diagram 212 is also changed according to the process change.

Return to FIG. Next, the operation reception unit 114 determines whether or not the user has selected any of the problem event marks 213 displayed in the operation state transition diagram 212 of the operation state transition screen 210 (step S6), and whichever When it is determined that the problem event mark 213 is not selected by the user (NO in step S6), the determination is repeated. Then, when the operation reception unit 114 determines that any of the problem event marks 213 is selected by the user (YES in step S6), the display control unit 115 then determines that the problem event mark 213 selected by the user. The cause input screen 220 (FIG. 7) is popped up nearby (step S7).

FIG. 7 shows a display example of the cause input screen 220 displayed in a pop-up. On the cause input screen 220, the occurrence time of the problem event corresponding to the problem event mark 213 selected by the user (10:45 to 11:00 in the case of the figure), the device code (M01 in the case of the figure), The name of the problem event (in the case of the figure, the device is stopped) and the cause selection column 221 are displayed. The cause selection field 221 is for the user to select and input a cause code indicating the cause of the problem event. The user can display the cause table 1234 (FIG. 3) on the screen by performing a predetermined operation, and can select and input the cause code in the cause selection field 221 while referring to the cause table 1234. can.

Return to FIG. Next, the operation reception unit 114 determines in the cause selection field 221 of the cause input screen 220 whether or not the selection input of the cause code by the user is completed (step S8), and the selection input of the cause code is completed. If it is determined that it is not (NO in step S8), the determination is repeated. Then, when the operation reception unit 114 determines that the selection input of the cause code by the user has been completed (YES in step S8), the problem event detection unit 113 then responds to the cause code selected and input by the user. Record in the problem event table 1222 of the KPI problem event DB 122 as the cause code of the problem event to be performed (step S9).

Next, the operation reception unit 114 determines whether or not all the problem event marks 213 displayed in the operation state transition diagram 212 of the operation state transition screen 210 have been selected by the user (step S10), and all of them. When it is determined that the user has not selected the problem event mark 213 (NO in step S10), the process is returned to step S6, and steps S6 and subsequent steps are repeated. After that, when the operation reception unit 114 determines that all the problem event marks 213 have been selected by the user, the operation monitoring process is terminated.

According to the operation monitoring process described above, it is possible to present the problem event that could have caused the decrease in the production KPI to the user and have the user select and input the cause.

<Display of operation state transition screen 210 after inputting cause code>
Next, FIG. 8 shows a display example of the operating state transition screen 210 after inputting the cause code. After the cause code is input in association with the problem event mark 213, the cause code mark 230 is displayed adjacent to the problem event mark 213. The cause code mark 230 is displayed in a predetermined color for each code so that the difference between the codes can be instantly identified, and the cause code is displayed inside the cause code mark 230. Therefore, when the user sees the cause code mark 230 displayed in the operation state transition diagram 212 of the operation state transition screen 210, for example, the problem event occurs due to a different cause, or the problem event occurs due to the same cause. It is possible to intuitively grasp that it is continuous.

Then, when the user selects the cause code mark 230 (mouseover may be used), the problem event cause display column 240 (FIG. 9) is popped up adjacent to the cause code mark 230.

FIG. 9 shows a display example of the problem event cause display column 240. In the problem event cause display field 240, the cause code input by the user (A013 in the case of the figure) and the cause represented by the cause code (chocolate stop in the case of the figure) are displayed. In addition, the user can input an arbitrary character string such as the details of the cause and the coping method in the problem event cause display field 240. The input arbitrary character string is recorded in the problem event table 1222 by the problem event detection unit 113 in association with the corresponding problem event.

Next, FIG. 10 shows a display example of the cause code Pareto FIG. 250 that is superimposed and displayed on the operating state transition screen 210 in response to the operation of the Pareto chart display button 215 of the operating state transition screen 210.

Cause code Pareto FIG. 250 is provided with a period selection field 251 for setting an aggregation period of occurrence frequency. Cause code Pareto In FIG. 250, the causes (cause codes) of problem events corresponding to the process selected by the user and the type of production KPI in the period selected in the period selection field 251 are normal in descending order of frequency of occurrence. It is converted and displayed.

By referring to the cause code Pareto chart 250, the user can grasp the cause of the problem event that could have caused the production KPI to decrease.

The present invention is not limited to the above-described embodiment, and various modifications are possible. For example, the above-described embodiment has been described in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to the one including all the described configurations. Further, it is possible to replace or add a part of the configuration of one embodiment with the configuration of another embodiment.

Further, each of the above configurations, functions, processing units, processing means and the like may be realized by hardware by designing a part or all of them by, for example, an integrated circuit. Further, each of the above configurations, functions, and the like may be realized by software by the processor interpreting and executing a program that realizes each function. Information such as programs, tables, and files that realize each function can be placed in a memory, a recording device such as a hard disk or SSD, or a recording medium such as an IC card, SD card, or DVD. In addition, the control lines and information lines indicate those that are considered necessary for explanation, and do not necessarily indicate all the control lines and information lines in the product. In practice, it can be considered that almost all configurations are interconnected.

10 ... Operation monitoring device, 11 ... Processing unit, 111 ... Information acquisition unit, 112 ... Production KPI calculation unit, 113 ... Problem event detection unit, 114 ... Operation reception unit, 115 ... Display control unit, 12 ... Storage unit, 121 ... Sensor record DB, 122 ... KPI problem event DB, 1221 ... Production KPI information, 1222 ... Problem event table, 123 ... -KPI cause tracking master DB, 1231 ... KPI cause related table, 1232 ... KPI table, 1233 ... problem table, 1234 ... cause table, 124 ... process master DB, 13 ... input Unit, 14 ... Output unit, 15 ... Communication unit, 20 ... Network, 30 ... Production line, 31 ... Equipment, 32 ... Sensor, 40 ... Information terminal, 200 ...・ ・ Production KPI screen, 201 ・ ・ ・ Date selection field, 202 ・ ・ ・ Process selection field, 203 ・ ・ ・ Production KPI selection field, 204 ・ ・ ・ Production KPI change diagram, 210 ・ ・ ・ Operating state transition screen, 211・ ・ ・ Process display field, 212 ・ ・ ・ Operating state transition diagram, 213,214 ・ ・ ・ Problem event mark, 215 ・ ・ ・ Pareto diagram display button, 220 ・ ・ ・ Cause input screen, 221 ・ ・ ・ Cause selection field , 230 ... cause code mark, 240 ... problem event cause display column, 250 ... cause code pallet diagram, 251 ... period selection column

Claims (8)

A sensor information acquisition unit that acquires sensor information that represents the state of the equipment placed on the production line, associates the acquired sensor information with the time, and stores it in the sensor record database.
The problem event that occurred in the apparatus of the production line was detected based on the sensor record database, and the detected problem event was recorded in the problem event table in association with the occurrence time and recorded in the problem event table. A problem event detection unit that selects problem events and
A display control unit that displays an operating state transition diagram showing the time-series operating state of the device and displays the time of occurrence of the selected problem event on the time axis of the operating state transition diagram.
It is provided with an operation reception unit that allows the user to input the cause of the problem event in which the occurrence time is displayed on the time axis of the operation state transition diagram.
The problem event detection unit is an operating state monitoring device that records the input cause of occurrence in the problem event table in association with the detected problem event. The operating condition monitoring device according to claim 1.
A production KPI calculation unit that calculates a production KPI in the production line based on the sensor performance database is provided.
The problem event detection unit is characterized by selecting the problem event that occurred in the time zone selected by the user based on the calculated time-series change of the production KPI from the problem event recorded in the problem event table. Operation status monitoring device. The operating condition monitoring device according to claim 1.
A production KPI calculation unit that calculates production KPIs on the production line based on the sensor performance database, and
A KPI cause-related table showing a correspondence relationship between the type of the production KPI that can be calculated by the production KPI calculation unit and the problem event that can cause a decrease in the production KPI is provided.
The problem event detection unit refers to the KPI cause-related table, and selects the problem event corresponding to the type of the production KPI selected by the user from the problem event recorded in the problem event table. Operation status monitoring device. The operating condition monitoring device according to claim 1.
The display control unit refers to the problem event table and displays the cause of the problem event adjacent to the time of occurrence of the problem event displayed on the time axis of the operating state transition diagram. Operation status monitoring device. The operating condition monitoring device according to claim 1.
The operation reception unit causes the user to select and input a cause code indicating the cause of the problem event in which the occurrence time is displayed on the time axis of the operation state transition diagram.
The display control unit refers to the problem event table and displays the cause code selected and input by the user adjacent to the occurrence time of the problem event displayed on the time axis of the operating state transition diagram. An operating status monitoring device characterized by this. The operating condition monitoring device according to claim 5.
The display control unit is an operating condition monitoring device characterized in that the cause code is displayed in a predetermined color for each code. The operating condition monitoring device according to claim 1.
The operation reception unit causes the user to input an arbitrary character string related to the problem event whose occurrence time is displayed on the time axis of the operating state transition diagram.
The display control unit displays the arbitrary character string input by the user adjacent to the occurrence time of the problem event displayed on the time axis of the operating state transition diagram. Monitoring device. This is an operating status monitoring method using an operating status monitoring device.
Acquires sensor information that indicates the status of the equipment placed on the production line.
The acquired sensor information is associated with the time and accumulated in the sensor record database.
Based on the sensor performance database, a problem event that occurred in the device of the production line was detected.
The detected problem event is recorded in the problem event table in association with the time of occurrence.
Select the problem event recorded in the problem event table and select
The operation state transition diagram showing the time-series operating state of the device is displayed, and the time of occurrence of the selected problem event is displayed on the time axis of the operating state transition diagram.
The user is made to input the cause of the problem event whose occurrence time is displayed on the time axis of the operating state transition diagram.
An operating state monitoring method including a step of recording the input cause of occurrence in the problem event table in association with the detected problem event.

Images