Information processing device

Abstract

One objective is to efficiently resolve the cause of an abnormal situation when the abnormal situation occurs in a robot. An information processing device 1 according to one aspect of the present invention is connected to an industrial machine 8, which is equipped with a sensor 81, 83, 85 or a control unit 9 that controls the industrial machine 8.The information processing device 1 comprises a storage unit 6, which stores initial table data in which a multitude of anomaly causes are associated with a multitude of abnormal situations relating to the operation of the industrial machine 8; an anomaly monitoring unit 24, which monitors the occurrence of an abnormal situation in the industrial machine 8 based on data output by the sensor 81, 83, 85; a cause identification unit 25, which identifies a cause of the abnormal situation with reference to the initial table data; and a display control unit 29, which causes a display unit to show details of the abnormal situation and the identified cause of the abnormal situation.

Description

Technical area

[0001] The present invention relates to an information processing device having a monitoring function for an industrial machine. State of the art

[0002] Nowadays, robots are indispensable in factories and the like. Robots are equipped with various sensors such as vision sensors and force sensors. By utilizing the output data of the various sensors present in the robot, the operation time of the robot can be identified and the current position of the robot can be detected. In addition, by utilizing the output data of the various sensors in the robot, it is possible to monitor the occurrence of a situation where the robot is unable to perform correct operation according to an operation program due to an unintentional large load on the robot during operation, vibration of the robot, or sudden stop of the robot, etc., that is, an abnormal situation. For example, an industrial robot with a monitoring function such as abnormality detection is known (e.g., Patent Document 1).When an abnormal situation occurs in a robot, the operator must investigate the cause of the abnormal situation, make a countermeasure plan, and prevent the same abnormal situation from occurring again.

[0003] Traditionally, to identify the cause of an abnormal situation, the operator would confirm the execution log record recorded for each operation and output data from various sensors while switching between various screens related to the robot's operation control provided by the robot. Furthermore, the operator would establish a countermeasure plan to address the identified cause by referring to a manual or similar, adjust setting information such as the robot's operating parameters, actually operate the robot with the adjusted setting information, and confirm whether the same abnormal situation would occur again. Citation listPatent documents

[0004] Patent Document 1: Unexamined Japanese Patent Application Publication No. 2015-229224 Summary of the inventionThe problem to be solved by the invention

[0005] However, when an abnormal situation occurs, it is inefficient to confirm the sensor output data and execution history data while switching between the robot's various screens, which may delay the determination of the cause of the abnormal situation or lead to an incorrect diagnosis. Furthermore, to formulate a countermeasure plan to resolve the cause of the abnormal situation, it is necessary to first identify the cause of the abnormal situation and then consult manuals, academic materials, etc., which requires a lot of time to resolve the cause of the abnormal situation. Therefore, it is desirable to develop a technology that can efficiently resolve the cause of an abnormal situation when the abnormal situation occurs in a robot. Solution to the problem

[0006] An information processing device according to one aspect of the present invention is connected to an industrial machine equipped with a sensor or a control unit for controlling the industrial machine. The information processing device includes a storage unit that stores first table data in which a plurality of abnormality causes are associated with a plurality of abnormal situations related to the operation of the industrial machine, an abnormality monitoring unit that monitors the occurrence of an abnormal situation in the industrial machine based on data output from the sensor, a cause identification unit that identifies a cause of the abnormal situation with reference to the first table data, and a display control unit that causes a display unit to display details of the abnormal situation and the identified cause of the abnormal situation. Short description of the drawings Fig. 1 shows a robot system having an information processing apparatus according to the present embodiment. Fig. 2 is a block configuration diagram of the Fig. 1 shown information processing device. Fig. 3 shows an example of a memory unit according to Fig. 2 stored cause identification table. Fig. 4 shows an example of a memory unit according to Fig. 2 stored countermeasure plan identification table. Fig. Figure 5 shows an example of an execution history screen displayed on a display unit used in Fig. 2 is shown. Fig. Figure 6 shows an example of a cause confirmation screen that appears on the execution history screen in Fig. 5 is displayed. Fig. Figure 7 shows an example of a countermeasure plan confirmation screen displayed on the execution history screen in Fig. 6 is displayed. Fig. Figure 8 shows an example of an enlarged screen that is displayed as a result of a user operation on the Fig. The execution history screen shown in Figure 6 appears. Fig. 9 shows another example of the cause confirmation screen that appears on the Fig. The execution history screen shown in Figure 6 appears. Fig. 10 is a flowchart showing an example of the procedure for monitoring the processing by the Fig. 1 shows the information processing device shown. Detailed description of the invention

[0007] An information processing apparatus according to the present embodiment will be described below with reference to the drawings. In the following description, components having substantially the same function and configuration are denoted by the same reference numerals, and repetitive descriptions are given only when necessary.

[0008] An information processing device according to the present embodiment is a computer device having a function of monitoring an industrial machine operating according to an operation program, a function of identifying an abnormal cause of the abnormal situation and notifying the user when an abnormal situation related to operation occurs in the industrial machine, a function of identifying a countermeasure plan for resolving the abnormal cause of the abnormal situation that has occurred in the industrial machine and notifying the user, and a function of providing a screen that allows the user to easily confirm the operation status of the industrial machine. In the present embodiment, a robot device is described as an example of the industrial machine.However, the industrial machine may be a machine tool, a welding device, or the like, and is not limited to a robot device. Typically, the information processing device according to the present embodiment is configured as follows.

[0009] As in Fig. 1, an information processing device 1 according to the present embodiment is connected to a robot device 7. The robot device 7 includes a robot arm mechanism 8 and a controller 9 that controls the robot arm mechanism 8. In the present embodiment, the information processing device 1 is connected to the controller 9. The robot arm mechanism 8 includes various sensors, such as a force sensor 81 for detecting a load applied to an end effector, a vision camera 83 for capturing an image of a workpiece W or the like, and an encoder 85 for detecting the rotation position of a motor. The types of sensors are not limited to these. Output data of various sensors provided in the robot arm mechanism 8 are input to the information processing device 1 via the controller 9 according to the present embodiment.

[0010] As in Fig. As shown in Figure 2, the information processing device 11 according to the present embodiment is configured by connecting hardware such as an operation unit 3, a display unit 4, a communication unit 5, and a storage unit 6 to a processor 2 (such as a CPU). The information processing device 11 is constituted by a PC, a tablet, a smartphone, or the like.

[0011] The operation unit 3 includes an input device such as a keyboard, a mouse, a jog dial, or a touch panel. The user can input various types of information into the information processing device 1 via the operation unit 3. The various types of information include user operations on the execution history screen. The user operations on the execution history screen include a parameter selection operation, an execution history log selection operation, selection operations of various buttons, and the like. The display unit 4 includes a display device such as an LCD. The display unit 4 displays an execution history screen, a pop-up screen, and the like under the control of the display control unit 29. The communication unit 5 controls the transmission and reception of data to and from the robot device 7.Through the processing of the communication unit 5, the information processing device 1 receives from the robot device 7 operation information about the robot device 7, which is operated according to the operation program 62. The operation information includes information about the operation date and time, information about the operation time, sensor data acquired during operation, information identifying the operation program used, event information indicating the operation content, and the like.

[0012] The storage unit 6 includes a storage device such as an HDD or SSD. A monitoring program 61 for monitoring the robot device 7, an operation program 62 for the robot device 7, three-dimensional model data 63, and table data 64 are stored in advance in the storage unit 6. The three-dimensional model data 63 include data of the three-dimensional model of the robot device 7 and data of the three-dimensional model of the workpiece. Typically, the three-dimensional model data 63 are provided by CAD data.

[0013] The data of Table 64 includes data from a first table (hereinafter referred to as the "cause identification table") used to identify the abnormal cause of the abnormal situation, and data from a second table (hereinafter referred to as the "countermeasure plan identification table") used to identify the countermeasure plan for the abnormal cause. Of course, the cause identification table and the countermeasure plan identification table can be provided as a single, combined table.

[0014] As in Fig. As shown in Figure 3, the cause identification table links a plurality of abnormal causes to abnormal situations related to the operation of the robot. For example, an abnormal situation is linked to an abnormal cause, such as the abnormal cause “B21” being linked to the abnormal situation “A2”. For an abnormal situation, multiple abnormal causes can be considered. Therefore, multiple abnormal causes can be linked to an abnormal situation, such as the abnormal causes “B11”, “B12”, “B13”, and “B14” being linked to the abnormal situation “A1”. When multiple abnormal causes are considered for an abnormal situation, it is desirable that at least one abnormal cause can be identified from the multiple abnormal causes. Therefore, a condition for identifying a cause can be linked to an abnormal cause, such as:four conditions for identifying causes “C11”, “C12”, “C13” and “C14” which are associated with four causes of anomalies “B11”, “B12”, “B13” and “B14”.

[0015] As in Fig. As shown in Figure 4, in the countermeasure plan identification table, multiple countermeasure plans are associated with multiple anomaly causes. For example, one countermeasure plan is associated with one anomaly cause, such as countermeasure plan "D11" being associated with anomaly cause "B11." Of course, there can be multiple countermeasure plans for one anomaly cause. Therefore, multiple countermeasure plans can be associated with one anomaly cause, such as countermeasure plans "D121" and "D122" being associated with anomaly cause "B12."

[0016] As in Fig. 2, when the monitoring program 61 stored in the storage unit 6 is executed by the processor, the information processing device 1 serves as a virtual space generation unit 21, a model arrangement unit 22, a simulation execution unit 23, an abnormality monitoring unit 24, a cause identification unit 25, a countermeasure plan identification unit 26, an execution history generation unit 27, a display parameter setting unit 28, and a display control unit 29.

[0017] The virtual space generation unit 21 generates a virtual space in software that three-dimensionally represents an operating space in which the robot device operates. The virtual space generated by the virtual space generation unit 21 is displayed in a simulation display area of ​​the execution history screen generated by the display control unit 29.

[0018] The model arrangement unit 22 arranges a three-dimensional model of the robot device 7 (hereinafter referred to as the robot model) and a three-dimensional model of the workpiece (hereinafter referred to as the workpiece model) in the virtual space generated by the virtual space generation unit 21 and displayed on the execution history screen. The robot model and the workpiece model are arranged in the virtual space to correspond to the positional relationship between the robot and the workpiece in the actual operation space.

[0019] The simulation execution unit 23 performs a simulation operation for operating the robot model in the virtual space generated by the virtual space generation unit 21 and displayed on the execution history screen according to the operation program 62 or according to a user instruction by the operation unit 3 in the simulation. For example, the following display can be realized by the processing of the simulation execution unit 23. For example, a robot model displayed in the simulation display area of ​​the execution history screen can be displayed as a moving image in synchronization with the actual operation of the robot device 7. In addition, a robot model reproducing the operation of the robot device 7 at the time of task execution according to an execution history log selected by a user operation on the execution history screen can be displayed as a moving image.Furthermore, the output of the sensors at the time of execution of a task can be reproduced and displayed according to an execution history log selected by a user operation on the execution history screen.

[0020] The anomaly monitoring unit 24 monitors the occurrence of an abnormal situation of the robot device 7. Typically, the anomaly monitoring unit 24 identifies that an abnormal situation has occurred in the robot device 7 based on output data from various sensors provided in the robot device 7. Note that the anomaly monitoring unit 24 may be configured to monitor the occurrence of an abnormal situation of the robot device 7 based on the setting information of the sensors, the setting information of the robot device 7, and the like.

[0021] The cause identification unit 25 refers to the cause identification table to identify the abnormal cause of the abnormal situation that has occurred. When there are multiple abnormal causes of an abnormal situation, the cause identification unit 25 identifies at least one abnormal cause from the multiple abnormal causes based on the outputs of various sensors provided in the robot device 7. For example, in the cause identification table, multiple abnormal causes such as "contact with an obstacle," "motor failure," and "incorrect setting information" are associated with an abnormal situation such as "robot device stop" of the robot device 7.For example, based on the output data of the force sensor and the vision camera provided in the robot device 7, it is possible to identify whether the abnormal cause of the robot device 7 stopping is "contact with an obstacle." Similarly, based on the output data of the encoder that detects the rotation of the motor provided in the robot device 7, the cause identification unit 25 can determine whether the abnormal cause of the robot device 7 stopping is "motor failure." If the abnormal cause is neither "contact with an obstacle" nor "motor failure," the cause identification unit 25 can identify "incorrect setting information" as the abnormal cause of the robot device 7 stopping.

[0022] The countermeasure plan identification unit 26 refers to the countermeasure plan identification table to identify a countermeasure plan for resolving the identified abnormality cause. For example, in the countermeasure plan identification table, a countermeasure plan "obstacle removal" is linked to the abnormality cause "obstacle contact" of the robot device 7. Furthermore, the countermeasure plans "confirmation of motor setting information" and "motor replacement" are linked to the abnormality cause "motor failure" of the robot device 7. If the abnormality cause identified by the cause identification unit 25 is "obstacle contact," the countermeasure plan identification unit 26 refers to the countermeasure plan identification table and identifies the countermeasure plan "obstacle removal."Similarly, if the abnormality cause identified by the cause identification unit 25 is "engine failure," the countermeasure plan identification unit 26 refers to the countermeasure plan identification table and identifies the countermeasure plans "confirmation of engine setting information" and "engine replacement."

[0023] The execution history generation unit 27 creates an execution history log including an operation date and time, an event, a status, an operation program, and the like. For example, the execution history log is created each time a predetermined task is executed. The operation date and time, the operation time, the event, and the like are identified based on the operation information received from the robot device 7. The status includes "normal" and "abnormal." Tasks for which no abnormal situation has been identified by the anomaly monitoring unit 24 are assigned the status "normal," and tasks for which an abnormal situation has been identified are assigned the status "abnormal." This distinguishes execution history logs in which an abnormal situation has occurred from other execution history logs.Of course, execution history logs in which an abnormal situation has occurred can be automatically displayed in a detailed information display area 140 so that they can be distinguished from other execution history logs. Furthermore, the display mode of the execution history logs in which an abnormal situation has occurred and the display mode of other execution history logs can be changed by color, design, pattern, or the like. The execution history log corresponding to a task in which an abnormal situation has occurred includes an abnormality cause identified by the cause identification unit 25 and a countermeasure plan identified by the countermeasure plan identification unit 26.

[0024] The display parameter setting unit 28 sets parameters to be displayed on the execution history screen according to a user instruction via the operation unit 3. The parameters include raw data of each sensor provided in the robot device 7 and data obtained by performing predetermined processing on the raw data of each sensor.

[0025] The display control unit 29 generates an execution history screen related to the result of the execution of the operation program 62 by the robot device 7 according to a predetermined format, and causes the display unit 4 to display the execution history screen. The execution history screen generated by the display control unit 29 will be described below with reference to Fig. 5 described.

[0026] Fig. 5 shows an example of the execution history screen generated by the display control unit 29. As in Fig. 5, the execution history screen 100 includes a simulation display area 110, an execution history display area 120, a parameter display area 130, a detailed information display area 140, a playback button 160, and an update button 170.

[0027] In the simulation display area 110, a virtual space is displayed in which a robot model and a workpiece model are arranged. For example, the robot model displayed in the virtual space operates synchronously with the operation of the actual robot device 7. When the playback button 160 is clicked in a state where an execution history log is selected by the user, the task corresponding to the execution history log is reproduced by simulation, and the robot model displayed in the simulation display area 110 performs the operation corresponding to the execution history log. At this time, the outputs of the sensors are also reproduced, and the sensor outputs reproduced by simulation are displayed in the parameter display area 130.For example, the user may select an execution history log in which an abnormal situation occurred and click the playback button 160 to confirm by simulation the operation of the robot device 7 and the outputs of the sensors when the abnormal situation occurred.

[0028] The execution history display area 120 displays a list of execution history logs created by the execution history generation unit 27. Among the execution history logs in the list, the execution history logs in which an abnormal situation has occurred are preferably distinguished from other execution history logs. While the robot device 7 is operating, the execution history screen 100 is periodically updated, and the execution history logs displayed in the execution history display area 120 are added sequentially. The execution history screen 100 is also updated when the user clicks the playback button 160.

[0029] In the parameter display area 130, the parameters selected by the user are displayed in a chart format. The parameters include time series data from sensors and data obtained by performing predetermined calculation processing on the time series data from sensors. The display format can be a chart format or a table format.

[0030] The detailed information display area 140 displays detailed information of the execution history log. The detailed information display area 140 can automatically display an execution history log corresponding to a task in which an abnormal situation occurred, or display an execution history log selected by the user from the execution history log list displayed in the execution history display area 120. When the execution history log displayed in the detailed information display area 140 is that of a task in which an abnormal situation occurred, a cause confirmation button 141 for confirming the details of the abnormal situation and the cause of the abnormality, and a countermeasure plan confirmation button 143 for confirming a countermeasure plan for resolving the cause of the abnormality are displayed.

[0031] As in Fig. As shown in Figure 6, when the user clicks the cause confirmation button 141 by operating the cursor 200, a cause confirmation screen 341 with the text relating to the details of the abnormal situation and the cause of the abnormality appears on the execution history screen 100. Note that the cause confirmation screen 341 can be displayed in an enlarged form on the execution history screen 100. In addition, the cause confirmation screen 341 is automatically displayed on the execution history screen 100 when an abnormal situation occurs in a predetermined task in the monitoring processing to be described later. As shown in Fig. For example, as shown in Figure 6, the cause confirmation screen 341 displays an error code "0001," the details of the abnormal situation "the robot device 7 has stopped," which is also an explanation of the error code, and the abnormal cause "failure of the robot device 7." The user can immediately grasp the details of the abnormality by viewing the cause confirmation screen 341.

[0032] As in Fig. As shown in Figure 7, when the user clicks the countermeasure plan confirmation button 143 by operating the cursor 200, a countermeasure plan confirmation screen 343 appears with the text of the countermeasure plan for resolving the anomaly cause. Note that the countermeasure plan confirmation screen 343 can be displayed in an enlarged form in the execution history screen 100. As shown in Fig. As shown in Figure 7, the countermeasure plan confirmation screen 343 displays, for example, the countermeasure plans "Confirmation of Motor Setting Information" and "Motor Replacement" for the error code "0001" according to the details of the abnormality. These are displayed according to a preset priority order. In other words, the user can Fig. Confirm the countermeasure plan confirmation screen 343 shown in Fig. 7 and implement the countermeasure plans in the order of “confirmation of the motor setting information” and “replacement of the motor”, and understand which countermeasure plan should be considered and implemented first.

[0033] As in Fig. As shown in Figure 8, when the user selects a chart displayed in the parameter display area 130 by operating the cursor 200, an enlarged screen 330 of the selected chart appears on the execution history screen 100. The enlarged screen 330 can be displayed enlarged within the execution history screen 100. The user can confirm the enlarged screen 330 to examine the chart displayed in the parameter display area 130 in detail.

[0034] As in Fig. As shown in Figure 9, the parameter types displayed in the parameter display area 130 can be changed according to a user command. The user can know parameters that may be factors for the occurrence of an abnormal situation when the operation program 62 is tried on the robot device 7. In such a case, by previously setting the parameters to be displayed on the execution history screen 100, when an abnormal situation occurs, it is possible to immediately grasp the parameters that are highly likely to cause the abnormal situation.

[0035] The monitoring processing by the information processing apparatus 1 according to the present embodiment will be described below with reference to Fig. 10 described.

[0036] The monitoring processing by the information processing device 1 is executed when the robot device 7 starts a predetermined task based on the operation program 62. First, the information processing device 1 generates an execution history screen 100 (S11) and displays it on the display unit 4 (S12). The information processing device 1 receives from the robot device 7 operation information generated by the robot device 7 after completion of the predetermined task (S13) and identifies whether or not an abnormal situation has occurred based on sensor data included in the operation information (S14).

[0037] If the information processing device 1 detects that an abnormal situation has occurred in the task (S14; YES), the information processing device 1 refers to the cause identification table to identify the cause of the abnormality (S15). Next, a countermeasure plan for resolving the cause of the abnormality is retrieved by referring to the countermeasure plan identification table (S16). Then, the information processing device 1 creates an execution history log corresponding to the task based on the operation information received from the robot device 7, the cause of the abnormality, and the countermeasure plan (S17), and updates the execution history screen 100 (S18). Through the process of step S18, the execution history log created in step S17 is added to the execution history display area 120 of the execution history screen 100.Further, the information processing device 1 opens the cause confirmation screen 341 to inform the user of the abnormal situation and the cause of the abnormality (S19). Note that during step S19, the information processing device 1 may open the countermeasure plan confirmation screen 343 together with the cause confirmation screen 341.

[0038] If it cannot be determined in step S14 that an abnormal situation has occurred, that is, if the task is completed normally (S14; NO), the information processing device 1 creates an execution history log corresponding to the task based on the operation information received from the robot device 7 (S20) and updates the execution history screen 100 (S21). Through the process of step S18, the execution history log created in step S17 is added to the execution history display area 120 of the execution history screen 100.

[0039] Each time the predetermined task is executed by the robot device 7, the processes from step S13 to step S21 are executed (S22; NO). After the robot device 7 completes a series of tasks, the screen processing is completed (S22; YES).

[0040] According to the information processing apparatus 1 of the present embodiment, the following effects are achieved.

[0041] The information processing device 1 according to the present embodiment includes a cause identification table in which abnormal causes are linked to abnormal situations. When an abnormal situation occurs in the monitored robot device 7, the cause confirmation screen 341 is automatically displayed to inform the user of the abnormal cause of the abnormal situation. By viewing the cause confirmation screen 341 displayed on the display unit 4, the user can understand that an abnormal situation has occurred and immediately confirm the abnormal cause of the abnormal situation. When an abnormal situation occurs, the time required to confirm the abnormal cause can be shortened than before, and the abnormal situation can be efficiently resolved.

[0042] In response to a user operation, the information processing device 1 displays a countermeasure plan confirmation screen 343 containing a countermeasure plan for resolving the cause of the abnormality on the execution history screen 100. The user can confirm the countermeasure plan by simply operating the execution history screen 100 to display the countermeasure plan confirmation screen 343. This contributes to the efficient resolution of abnormal situations.

[0043] The information processing device 1 also displays the execution history screen 100 as shown in Fig. 5, which collectively displays the simulation screen, the list of execution history logs, a diagram related to the parameters set by the user, and details of an execution history log. When an abnormal situation occurs during the execution of a particular task by the robot device 7, the details of the execution history log of the task are displayed in a detailed information display area 140, and the cause confirmation button 141 for confirming the cause of the abnormality and the countermeasure plan confirmation button 143 for confirming the countermeasure plan for the cause of the abnormality are displayed together with the details of the abnormal situation. By pressing the cause confirmation button 141, the user can display the cause confirmation screen 341 ( Fig. 6) displayed on the execution history screen 100 to confirm the details and cause of the abnormal situation. Similarly, by pressing the countermeasure plan confirmation button 143, the user can display the countermeasure plan confirmation screen 343 ( Fig. 7) displayed on the execution history screen 100 to confirm the countermeasure plan for the cause of the anomaly. Furthermore, by operating the execution history screen 100, the user can display the diagram or the enlarged screen 330 ( Fig. 8) of the simulation screen displayed on the execution history screen 100 to investigate the cause of the anomaly in detail.

[0044] As described above, the user can confirm the execution history, confirm the occurrence of an abnormal situation and the cause of the abnormality, confirm the countermeasure plan, and examine the details thereof simply by viewing the execution history screen 100 and operating the execution history screen 100 as needed, so that abnormal situations can be efficiently resolved. In particular, since the cause confirmation screen 341, the countermeasure plan confirmation screen 343, and the enlarged screen 330 appear on the execution history screen 100, it is possible to return to the execution history screen 100 simply by closing each appearing screen when the confirmation of each screen is completed.Therefore, compared with the case where the user confirms the details while switching pages, the user can solve abnormal situations with high usability and high efficiency.

[0045] As long as the output data of various sensors provided in the robot arm mechanism 8 can be input to the information processing device 1 according to the present embodiment, the system configuration is not limited to the above. For example, the information processing device 1 according to the present embodiment can be connected to the robot arm mechanism 8, and the output data of various sensors can be directly input to the information processing device 1 according to the present embodiment. Alternatively, the functions of the information processing device 1 according to the present embodiment can be realized in the control unit 9 that controls the robot arm mechanism 8.

[0046] A feature of the information processing device 1 according to the present embodiment is that, when an abnormal situation occurs, the information processing device 1 can inform the user of the details of the abnormal situation and the cause of the abnormality. As long as this feature can be realized in the information processing device 1, the other processes do not necessarily have to be executed in the information processing device 1. In the present embodiment, for example, the information processing device 1 executes the process of identifying the abnormal situation and the process of creating the execution history log. However, the robot device 7 can execute the process of identifying the abnormal situation and the process of creating the execution history log, and the information processing device 1 can receive the execution result.

[0047] Although embodiments of the present invention have been described in detail, the present invention is not limited to the above-described individual embodiments. The present embodiments may be subjected to various additions, substitutions, modifications, partial deletions, etc., without departing from the gist of the invention or the idea and spirit of the present invention as set forth in the claims and their equivalents. For example, in the above-described embodiments, the order of operations and the order of processes are exemplified, and the present invention is not limited thereto. The same applies to the use of numerical values ​​or formulas in describing the above-described embodiments. Explanation of reference symbols

[0048] 100: Execution history screen, 110: Simulation display area, 120: Execution history display area, 130: Parameter display area, 140: Detailed information display area, 141: Cause confirmation button, 143: Countermeasure plan confirmation button, 160: Playback button, 170: Refresh button, 200: Cursor. QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited patent literature

[0000] JP 2015- 229 224

[0004]

Claims

[1] An information processing device connected to an industrial machine, which is equipped with a sensor or a control unit for controlling the industrial machine, the information processing device comprising: a storage unit configured to store first table data in which a plurality of anomaly causes are associated with abnormal situations related to the operation of the industrial machine; an anomaly monitoring unit configured to monitor the occurrence of an abnormal situation in the industrial machine based on the data output by the sensor; a cause identification unit configured to identify a cause of the abnormal situation with reference to the first table data; and a display control unit configured to cause a display unit to display details of the abnormal situation and the identified cause of the abnormal situation. [2] The information processing apparatus according to claim 1, wherein the display control unit causes the display unit to display, based on the occurrence of the abnormal situation, the details of the abnormal situation and the cause of the identified cause of the abnormal situation. [3] The information processing apparatus according to claim 1, wherein the display control unit causes the display unit to display an execution history screen including execution history information items representing operation history records executed by the industrial machine, and causes a screen for notifying the details of the abnormal situation and the identified cause of the abnormal situation to appear on the execution history screen in response to a user operation on the execution history screen. [4] The information processing apparatus according to claim 3, wherein the display control unit causes the execution history information items in which an abnormal situation has occurred to be displayed in a manner different from other execution history information items. [5] The information processing apparatus according to claim 3, wherein the storage unit stores second table data in which a plurality of countermeasure plans for solving an abnormality cause are associated with each of the plurality of abnormality causes, the information processing device further comprises a countermeasure plan identification unit configured to refer to the second table data and identify a countermeasure plan for resolving the abnormal situation, and the display control unit causes a screen for notifying a countermeasure plan for correcting the cause of the anomaly to appear on the execution history screen in response to a user operation. [6] The information processing apparatus according to claim 3, wherein the display control unit causes a three-dimensional model of the industrial machine and time series data to be displayed on the execution history screen based on an output of the sensor. [7] The information processing apparatus according to claim 6, wherein the display control unit controls the display of the three-dimensional model and the time series data to reflect an operation of the industrial machine and an output of the sensor according to an execution history information item selected by a user operation on the execution history screen. [8] The information processing apparatus according to claim 3, wherein the display control unit causes a parameter selected according to a user instruction to be displayed on the execution history screen. [9] Information processing apparatus according to claim 1, wherein in the first table data, the multitude of anomaly causes are linked to an anomalous situation of the anomalous situations, and the cause identification unit identifies an anomaly cause for the abnormal situation from among the plurality of anomaly causes based on an output of the sensor.

Images