Monitoring device

Abstract

A monitoring device according to the present disclosure comprises: a monitoring unit configured to monitor the occurrence of an anomaly in each of a plurality of industrial machines; a calculation unit configured to calculate a priority for an industrial machine in which an anomaly has occurred, based on the number of days remaining from the current date until a date on which maintenance work must begin;and a display unit configured to display a graphic symbol representing an industrial machine with a priority within a predetermined number of top priorities among the industrial machines in which an anomaly has occurred, in a different display mode than a graphic symbol representing an industrial machine with a priority outside the predetermined number of top priorities among the industrial machines in which an anomaly has occurred, and a graphic symbol representing an industrial machine in which no anomaly has occurred.

Description

Technical field

[0001] The present disclosure relates to a monitoring device with a function for monitoring an industrial machine, for example a robot. State of the art

[0002] A robot monitoring system is known that monitors the operational status of a robot, for example, predictive maintenance using an algorithm to predict a malfunction of a robot used in a production factory or the like, preventive maintenance to notify when a part needs to be replaced according to a predetermined replacement period (e.g., a battery attached to the robot), and the detection of anomalies. In the robot monitoring system, information about a robot being monitored is displayed on a system-specific user interface to notify a system manager, plant manager, or similar person that the robot's operational status has changed.For example, patent literature 1 discloses a method for displaying information about a robot under monitoring by arranging the information on a map according to its location. This method allows the user to immediately identify the location of any robot experiencing an anomaly. However, particularly when monitoring numerous robots, a large amount of information is displayed on the map; therefore, it becomes difficult to identify robots experiencing anomalies and to prioritize which robot should be investigated or serviced. List of citations from patent literature

[0003] Patent literature 1: Japanese unexamined patent application publication no. 2005-107671 Summary of the invention; Problem to be solved by the invention

[0004] A technique should be proposed to counteract the reduction in efficiency during maintenance work performed by users. Solution to the problem

[0005] A monitoring device according to the present disclosure comprises: a monitoring unit configured to monitor the occurrence of an anomaly in each of a plurality of industrial machines; a calculation unit configured to calculate a priority for an industrial machine in which an anomaly has occurred, based on the number of days remaining from the current date until a date on which maintenance work must begin;and a display unit configured to display a graphic symbol representing an industrial machine with a priority within a predetermined number of top priorities among the industrial machines in which an anomaly has occurred, in a different display mode than a graphic symbol representing an industrial machine with a priority outside the predetermined number of top priorities among the industrial machines in which an anomaly has occurred, and as a graphic symbol representing an industrial machine in which no anomaly has occurred. Brief description of the drawings Fig. Figure 1 shows a robot monitoring system comprising a monitoring device according to the present embodiment. Fig. 2 is a hardware configuration diagram of the in Fig. 1. Monitoring device shown. Fig. 3 is a function block diagram of the in Fig. 1. Monitoring device shown. Fig. Figure 4 shows an example of a table for managing the anomaly history, which is used in a Fig. The storage unit shown in section 3 is stored. Fig. Figure 5 shows an example of a monitoring screen displayed on a [unclear text] Fig. The display unit shown in section 3 is displayed. Fig. Figure 6 shows an example of a display settings screen, which is located on the screen shown in Fig. The display unit shown in section 3 is displayed. Fig. Figure 7 shows an example of a maintenance days setting screen, which is located on the in Fig. The display unit shown in section 3 is displayed. Fig. Figure 8 is a flowchart showing an example of the monitoring processing sequence by the monitoring device according to the present embodiment. Fig. Figure 9 shows another example of the monitoring screen, which is located on the [unclear text]. Fig. The display unit shown in section 3 is displayed. Fig. 10 shows a state in which a cursor is on the first robot symbol on the in Fig. 9 is placed on the surveillance screen shown. Fig. 11 shows a state in which a cursor is on a second robot symbol on the screen. Fig. 9 is placed on the surveillance screen shown. Detailed description of the invention

[0006] The following describes a monitoring device according to the present embodiment with reference to the drawings. In the following description, components that have essentially the same function and configuration are designated by the same reference numerals, and repeated descriptions are given only where necessary.

[0007] A monitoring device according to the present embodiment (hereinafter referred to simply as the "monitoring device") is a computer device with a monitoring function for detecting the occurrence of an anomaly in a robot and a display function for presenting the robot in which the anomaly has occurred to the user. A feature of the monitoring device is that robots in which an anomaly has occurred are prioritized for maintenance and presented to the user, distinguishing between robots with higher priority, those with lower priority, and those in which no anomaly has occurred in the first place. By viewing a screen displayed on the monitoring device, the user can identify which robot has a high priority for maintenance and intuitively grasp which of the robots with an anomaly should be serviced first.This enables efficient robot maintenance even with a limited number of workers.

[0008] In the present embodiment, the terms are defined as follows.

[0009] Robots: A robot is an example of an industrial machine that needs to be monitored. The term "industrial machine" is not limited to robots and can include machine tools, welding equipment, servo guns, and the like.

[0010] Robot Symbol: A robot symbol is a graphical symbol that schematically represents a robot. Each robot symbol is assigned an identification number. When the cursor is placed on a robot symbol, the system determines whether the robot corresponding to that symbol meets a predetermined condition. If the condition is met, text is displayed explaining the anomaly details or similar information.

[0011] Anomaly: An anomaly indicates a condition in which the industrial machine requires maintenance. This condition encompasses situations where the robot is currently functioning normally, but continued operation without maintenance could lead to a robot malfunction or a defect in the workpiece produced by the robot. Such a condition corresponds to a situation in which a robot component failure is expected in the near future or when the time has come to replace a robot component. Of course, the condition requiring maintenance can also include situations in which the robot is no longer functioning normally, such as a situation in which a robot component has failed.

[0012] Priority: A priority indicates the order in which maintenance work should be performed on robots that have experienced an anomaly. A high priority means that the maintenance is urgent and should be carried out as soon as possible. Typically, the priority is calculated based on the number of days remaining from the current date until the target due date.

[0013] Maintenance work: Maintenance work encompasses various types of tasks required from the occurrence of an anomaly until the completion of the actual work by the worker, such as the worker's actual tasks, worker organization, schedule adjustments, ordering spare parts, and processing internal approvals. It should be noted that the term "maintenance work" can also refer only to the worker's actual maintenance tasks.

[0014] Number of Maintenance Days: The number of maintenance days is the number of days required for maintenance work. Typically, this includes the time needed by the worker for the actual maintenance work, as well as the time required for various tasks before maintenance begins. Although a value recommended by the maintenance company or similar entity is pre-registered as the number of maintenance days, the user can adjust this number. For example, the number of maintenance days recommended by the maintenance company or similar entity is the number of days required by the worker for the actual maintenance work.In the present embodiment, the pre-registered number of maintenance days is referred to as the initial maintenance day value, while the user-set maintenance day value is referred to as the set maintenance day value. If no distinction between them is necessary, they are simply referred to as the maintenance day value.

[0015] Absolute due date: The absolute due date is the date by which maintenance must be performed. The absolute due date is the date on which a robot malfunction is to be expected and the robot could actually fail if no maintenance is performed by this date.

[0016] Target due date: The target due date is the date on which maintenance work must begin. It is determined by considering the number of maintenance days and is typically calculated by counting back the maintenance days from the absolute due date. Therefore, if maintenance work can begin before the target date, it reliably prevents the absolute due date from being reached during maintenance and a malfunction from occurring. The target date differs significantly from the absolute due date mentioned above.

[0017] Number of grace days for maintenance: The number of grace days for maintenance is the number of days from the date the anomaly occurred until the absolute due date.

[0018] Typically, the monitoring device is configured as follows. As shown in Fig. As shown in Figure 1, a robot monitoring system 1 comprises a plurality of robots 3 to be monitored and a monitoring device 2 that monitors the occurrence of anomalies in the plurality of robots 3. The plurality of robots 3 is connected to the monitoring device 2 via a network 10, such as a local area network or the internet. In the present embodiment, the plurality of robots 3 are connected to the monitoring device 2. However, the configuration of the robot monitoring system 1 is not limited to this. For example, an information processing device can be provided for each factory, which collects data from the plurality of robots 3 installed in that factory, and several information processing devices corresponding to the plurality of factories can be connected to the monitoring device.

[0019] As in Fig. As shown in Figure 2, the monitoring device 2 is configured such that hardware components, including an input device 12, a display device 13, a communication device 14, and a storage device 15, are connected to a processor 11, for example, a CPU, via a data and control bus. The input device 12 is implemented as a keyboard, mouse, jog wheel, or the like. The user can input various types of information into the monitoring device 2 via the input device 12. The display device 13 is implemented as an organic EL display, an LCD, or the like. Under the control of the processor 11, the display device 13 shows various screens. Under the control of the processor 11, the communication device 14 sends and receives data to and from the multiple robots 3. The storage device 15 is implemented as an HDD, an SSD, or the like.The storage device 15 stores a monitoring program for monitoring the occurrence of an anomaly in the robot 3 and for displaying information about the anomaly status in the robot 3.

[0020] As in Fig. As shown in Figure 3, when the monitoring program stored in the storage device 15 is executed by the processor 11, the monitoring device 2 functions as an input unit 21, a display unit 22, a data receiving unit 23, a storage unit 24, a monitoring unit 25, a screen creation unit 27, a display count setting unit 28, a display element setting unit 29, a maintenance day count setting unit 30 and a determination unit 31.

[0021] The input unit 21 is defined by the function of the in Fig. The input device 12 shown in Figure 2 is implemented. The input unit 21 sends a user operation to the monitoring device 2 via the input device 12. For example, the following instructions are sent from the input unit 21 to the monitoring device 2: an instruction to switch the screen, an instruction to set the number of robot symbols to display, an instruction to set display elements, an instruction to set a format, an instruction to set the number of maintenance days, and an instruction to select a specific robot symbol displayed on the screen.

[0022] The display unit 22 is operated by the function of the in Fig. The display device 13 shown in Figure 2 is implemented. The display unit 22 shows the monitoring screen, the display settings screen, the maintenance day setting screen, and the like, which are created by the screen creation unit 27. Details of these screens are described later.

[0023] The data receiving unit 23 is operated by the function of the in Fig. The communication device 14 shown in Figure 2 is implemented. The data receiving unit 23 receives sensor data from the robot 3 along with a factory ID for identifying the factory and a robot ID for identifying the robot 3 as information required to diagnose whether an anomaly has occurred or not.

[0024] The storage unit 24 is defined by the function of the in Fig. The storage device 15 shown in Figure 2 implements this. The storage unit 24 stores various types of information required for processing (monitoring processing) related to the monitoring program. For example, the storage unit 24 stores a table for managing the anomaly history, which compiles information about anomalies that have occurred in the robots 3. In addition, the storage unit 24 stores a variety of diagnostic programs corresponding to a variety of diagnostic functions. Furthermore, for each of the different types of diagnostic functions, the storage unit 24 stores the number of grace days for maintenance, the initial value of the number of maintenance days, and the set value of the maintenance days.Storage unit 24 also stores format data, material data, and the like for the screens created by screen creation unit 27, such as a monitoring screen, a display settings screen, a maintenance day count settings screen, and the like. The material data includes, for example, data on the robot symbol, data on the first marker, and data on the second marker.

[0025] The monitoring unit 25 monitors for the occurrence of an anomaly in the robot 3. In particular, the monitoring unit 25 has a variety of diagnostic functions for diagnosing the occurrence of an anomaly in the robot 3. The variety of diagnostic functions is implemented by executing several diagnostic programs that are stored in the memory unit 24.

[0026] For example, the monitoring unit 25, with a reduction gear deterioration diagnostic function, diagnoses the deterioration state of the reduction gear based on sensor data received from an encoder located in the robot 3. If the deterioration state of the reduction gear exceeds a threshold, the monitoring unit 25 diagnoses that an anomaly has occurred in the robot 3.

[0027] For example, in a battery replacement notification function, the monitoring unit 25 diagnoses that it is time to replace the battery based on the number of days or the operating time of robot 3 since the last replacement. When the time for battery replacement has arrived, the monitoring unit 25 diagnoses that an anomaly has occurred in robot 3.

[0028] The numerous diagnostic functions include a function for diagnosing motor torque, an arc welding condition, a servo gun, a cable replacement notification, a lubricant replacement notification, and similar functions. When the monitoring unit 25 diagnoses an anomaly in robot 3, a robot ID to identify the robot in which the anomaly occurred, details of the anomaly, an anomaly code corresponding to the anomaly details, and the date and time of the anomaly's occurrence are recorded in the anomaly history management table.

[0029] Calculation unit 26 calculates the priority based on the number of days remaining from the current date to the target due date. Specifically, calculation unit 26 calculates the number of remaining days by subtracting the initial maintenance day count and the number of days elapsed since the anomaly occurred from the maintenance grace period, and then calculates the priority in descending order of the number of remaining days. If the number of remaining days is the same, the priority is determined based on the number of maintenance days. Specifically, if the number of remaining days is the same, the priority is determined in descending order of the number of maintenance days.It should be noted that if the number of maintenance days is set by the user, the calculation unit 26 replaces the initial value of the number of maintenance days with the set value of the number of maintenance days in order to calculate the number of remaining days.

[0030] The screen creation unit 27 uses the format and material data stored in the memory unit 24 to create a monitoring screen to notify the user of the status of an anomaly in robot 3, a display settings screen to receive user settings related to the display, a maintenance days settings screen to receive user settings related to the number of maintenance days, and a pop-up screen with detailed information about the anomaly. The pop-up screen is created when the determination unit 31 makes a positive determination, and the pop-up screen includes detailed information about the anomaly that occurred in robot 3, corresponding to the robot symbol for which the positive determination was made. The screen created by the screen creation unit 27 is displayed on the display unit 22.

[0031] The Display Count setting unit 28 sets a display number based on a user operation on the display settings screen. The display number corresponds to the number of robot icons to be shown in a display mode corresponding to a predetermined number of high priorities, indicating that the maintenance priority is high. The Display Element setting unit 29 sets display elements based on a user operation on the display settings screen. The display elements are detailed information about the anomaly, such as anomaly details, an anomaly code, a maintenance procedure, and the number of days remaining. The Maintenance Days Count setting unit 30 sets a preset value for the number of maintenance days based on a user operation on the Maintenance Days Count setting screen.When the cursor is placed on a robot icon displayed on the monitoring screen, the determination unit 31 determines whether the robot 3 represented by the robot icon meets a predetermined condition. Specifically, the determination unit 31 determines that the predetermined condition is met if the robot 3 corresponding to the robot icon is within the priority ranges individually defined for the anomaly details, anomaly code, maintenance procedure, and number of days remaining. If the display targets for the anomaly details, anomaly code, maintenance procedure, and number of days remaining are as shown in... Fig. Given that 6 priorities are set, it is determined that the robots 3 with priorities within the first 10 meet the predetermined condition and that the robots 3 with priorities 11 or lower do not meet the predetermined condition.

[0032] Fig. Figure 4 shows an example of the anomaly history management table. This table manages information about robot 3, which experienced an anomaly. For example, the table links a plant ID, robot ID, anomaly details, an anomaly code, the date and time the anomaly occurred, and a maintenance status with a history ID to uniquely identify each anomaly history record. The anomaly details are information that indicates the diagnostic function that diagnosed the anomaly in robot 3. The anomaly code is used to identify the specific details of the anomaly. The maintenance status indicates whether or not maintenance was performed, with "maintained" indicating that maintenance was carried out and "not maintained" indicating that no maintenance was performed.When an anomaly in robot 3 is diagnosed by monitoring unit 25, a plant ID, a robot ID, anomaly details, an anomaly code, the date and time of the anomaly occurrence, and a maintenance status are recorded in the anomaly history management table. Initially, the maintenance status is recorded as "not serviced." When an input is received indicating that maintenance has been performed, the maintenance status is updated from "not serviced" to "serviced."

[0033] The following describes the monitoring screen displayed on display unit 22 with reference to Fig. 5 described. Fig. Figure 5 shows an example of the monitoring screen. The one in Fig. The monitoring screen 110 shown in Figure 5 is displayed in response to clicking "Factory 1" in a navigation tree 200, which is permanently present on each of the screens comprising the monitoring page. Monitoring screen 110 is a screen that displays to the user the status of any anomaly occurring in robot 3, which is located in the factory according to "Factory 1". As shown in Fig. As shown in Figure 5, for example, a multitude of robot symbols 115, each corresponding to several robots 3, are displayed on the monitoring screen 110. The multitude of robot symbols 115 are arranged in multiple positions according to the actual layout information. In the Fig. The display modes of the numerous robot symbols 115 shown on the monitoring screen 110 do not differ from one another. This means that no anomaly has occurred in the multiple robots 3 arranged in the factory according to "Factory 1".

[0034] The following describes the display settings screen shown on display unit 22 with reference to Fig. 6 described. Fig. Figure 6 shows an example of the display settings screen. The one in Fig. The display settings screen 120 shown in Figure 6 appears when "Display settings" is clicked in the navigation tree 200. The display settings screen 120 is a screen for receiving display conditions from the user, such as the number of displays, the display element, and the format.

[0035] As in Fig. As shown in Figure 6, the display settings screen 120 is equipped with an input field 121 for receiving the display number (a predetermined number of high priorities) and a pull-down menu 122 for receiving a display mode. The pull-down menu 122 is used to set a display mode, which is selected by the user from a variety of display mode types. Fig. 6. The display of a "first marker" on the robot symbols 115 is set according to the robots 3 with priorities in the top 5. This means that the robot symbols 115 corresponding to the robots 3 with priorities in the top 5 are displayed in a different display mode than the robot symbols 115 corresponding to the robots 3 with priorities outside the top 5, and the robot symbols 115 corresponding to the robots 3 where no anomaly has occurred.

[0036] It should be noted that the robot symbols 115, which correspond to robots 3 with low maintenance priorities and indicate low priorities outside the predetermined number of peak priorities, may be displayed in a different display mode than the robot symbols 115, which correspond to robots 3 where no anomaly has occurred. As in Fig. As shown in Figure 6, the display settings screen 120 is provided with a selection field 123 to receive a user's selection as to whether the robot symbols 115 corresponding to the robots 3 with low priorities (outside the predetermined number of peak priorities) should be displayed in a different display mode than the robot symbols 115 corresponding to the robots 3 for which no anomaly has occurred, and a pull-down menu 125 for selecting a display mode. Fig. 6. A "second marker" is displayed on the robot symbols 115 that correspond to robots 3 with priorities outside the top 5 (i.e., 6th or lower). This means that the robot symbols 115 corresponding to robots 3 with low maintenance priorities, indicating sixth or lower priority, are displayed in a different display mode than the robot symbols 115 corresponding to robots 3 with high maintenance priorities, indicating priorities within the top 5, and the robot symbols 115 corresponding to robots 3 where no anomaly has occurred.

[0037] As in Fig. As shown in Figure 6, the display settings screen 120 is equipped with four input fields 126, 127, 128, 129 and four toggle switches 130, 131, 132, 133, which correspond to the four display elements: anomaly details, anomaly code, maintenance procedure, and number of days remaining. The four toggle switches 130, 131, 132, 133 are used to determine which display elements should be shown for the robots 3 in which an anomaly has occurred. For example, if toggle switch 130 is set to "Hide," the "Anomaly Details" display element will not be shown for any robot 3. The four input fields 126, 127, 128, 129 receive input for the number of robots 3 for which the anomaly details, anomaly code, maintenance procedure, and number of days remaining should be displayed.

[0038] For example, in Fig. As shown in Figure 6, a numeric value "3" is entered into input field 126, which corresponds to the "Anomaly Details" display element, and the toggle switch 130, which corresponds to the "Anomaly Details" display element, shows "Show". This means that the anomaly details for robots 3 with priorities within the first three are displayed, and the anomaly details for robots 3 with the fourth or lower priority are not displayed. According to the setting in Fig. The six displayed display elements show, for the first-priority robot 3, all display elements for anomaly details, anomaly code, maintenance procedure, and number of days remaining; for the second-priority robot 3, three display elements are shown: anomaly details, anomaly code, and number of days remaining; for the third-priority robot 3, two display elements are shown: anomaly details and number of days remaining; and for the fourth through tenth-priority robots 3, only the number of days remaining is shown. Thus, the higher the priority of the robot 3, the more display elements are shown. This allows the user to intuitively grasp the priorities of the robot 3 robots that have experienced anomalies based on the number of displayed elements.

[0039] As in Fig. As shown in Figure 6, the display settings screen 120 contains four pull-down menus 134, 135, 136, and 137, each corresponding to four formats. In each of the four pull-down menus 134, 135, 136, and 137, an option selected by the user from a variety of choices is set. Fig. 6. The formats “font color”, “background”, “size” and “position” are each set to “black”, “white”, “10.5” and “top”.

[0040] The following describes the maintenance day count setting screen displayed by display unit 22, with reference to Fig. 7 described. Fig. Figure 7 shows an example of the maintenance days setting screen. The one in Fig. The maintenance day setting screen 140, shown in Figure 7, is displayed when "Maintenance Day Setting" is clicked in navigation tree 200. The maintenance day setting screen 140 is a screen for receiving a user-defined value for the number of maintenance days.

[0041] As in Fig. As shown in Figure 7, the Maintenance Days Setting Screen 140 displays the number of grace days for maintenance, a set value for the number of maintenance days, and an initial value for the number of maintenance days in conjunction with a diagnostic function name. The Maintenance Days Setting Screen 140 is equipped with a variety of input fields 141, 142, 143, 144, and 145, each corresponding to several diagnostic functions. Input fields 141, 142, 143, 144, and 145 receive set values ​​for a variety of maintenance days, corresponding to several diagnostic functions. For example, in Fig. As shown in Figure 7, input field 141, corresponding to the function name "A Diagnosis," contains the numerical value "7." This indicates that the set value for the number of maintenance days for robot 3, for which an anomaly was diagnosed by the diagnostic function "A Diagnosis," is set to 7 days. The remaining maintenance days for robot 3 are calculated using the grace period of "21 days" and the set value for the number of maintenance days, "7 days." Input field 143, corresponding to the diagnostic function name "C-Replacement," is empty. This means that the set value for the number of maintenance days for robot 3, for which an anomaly was diagnosed by the diagnostic function "C-Replacement," is not set.To calculate the remaining days of operation for Robot 3, the grace period for maintenance (25 days) and the initial maintenance day count (2 days) are used. The initial maintenance day count is the minimum number of days required for maintenance. Based on this initial maintenance day count, the user can set a custom value by adding the days required within their own company, such as those needed for processing internal approvals. This reduces the risk of Robot 3 needing to be stopped due to lengthy processing times within the user's company.

[0042] The monitoring processing by the monitoring device 2 is described below with reference to Fig. 8 described.

[0043] Fig. Figure 8 is a flowchart illustrating an example of monitoring processing by the monitoring device 2 according to the present embodiment. Upon receiving an instruction to start monitoring processing, the monitoring device 2 initiates monitoring processing for each of the robots 3. Specifically, the monitoring device 2 displays a monitoring screen (S11) and monitors for the occurrence of an anomaly (S12). For example, in step S12, the occurrence of an anomaly in the robot 3 is diagnosed based on sensor data received from the robot 3. If the occurrence of an anomaly in the robot 3 is diagnosed (S13; Yes), the monitoring device 2 calculates the priority of each of the robots 3 for which the occurrence of an anomaly has been diagnosed and for which no maintenance has been performed (S14) and updates the monitoring screen (S15).The process in step S15 changes the display mode of the robot icons corresponding to robots 3 with priorities within a predetermined number of peak priorities, and the display mode of the robot icons corresponding to robots 3 with priorities outside the predetermined number of peak priorities, on the monitoring screen. Note that the monitoring screen remains unchanged until a new anomaly occurs in a robot 3 (S13; No). The monitoring device 2 repeatedly executes the processes from step S12 to step S15—that is, processing the monitoring for the occurrence of an anomaly in each of the robots 3 and updating the monitoring screen in response to the occurrence of a new anomaly—until an instruction to terminate the monitoring processing is received (S16; No).The monitoring device 2 terminates the monitoring processing in response to receiving the instruction to terminate monitoring processing (S16; Yes). The monitoring processing described above updates the monitoring screen displayed on the display unit 22 each time a new anomaly occurs in a robot 3, and changes the display modes of the multiple robot icons corresponding to the multiple robots 3.

[0044] The effects of the monitoring device 2 according to the present embodiment are described below with reference to Fig. 9, Fig. 10 and Fig. 11 described. Fig. Figure 9 shows another example of the monitoring screen. Fig. 10 shows a state in which a cursor is on the first robot symbol on the Fig. 9 is placed on the surveillance screen shown. Fig. 11 shows a state in which a cursor is on a second robot symbol on the in Fig. 9 is placed on the surveillance screen shown. Fig. 9 shows a monitoring screen when an anomaly has occurred in eleven robots 3.

[0045] The purpose of displaying robots 3 that have experienced anomalies is to prompt the user to perform maintenance on them. Therefore, if the number of maintenance personnel is limited, it is not always necessary to display all robots 3 with anomalies simultaneously, as it is not possible to perform maintenance on many robots 3 at once. In particular, if many robots 3 have experienced anomalies, a great deal of information would have to be displayed on the monitoring screen to present the user with all affected robots 3. This can confuse the user and potentially reduce the efficiency of the maintenance work performed by the user.Because many Robot 3 units have experienced anomalies, the process of determining the maintenance sequence can be delayed. Furthermore, a large number of Robot 3 units with lower maintenance priorities may be serviced before those with higher priorities, potentially leading to delayed maintenance and resulting in Robot 3 units being out of service.

[0046] The monitoring device 2 of the present embodiment uses a refined approach regarding the content and method of the display on the monitoring screen, which indicates the status of an anomaly occurrence in each robot 3, in order to counteract a reduction in efficiency during maintenance work by the user. One of these refinements is to avoid displaying excessive information on the monitoring screen 160.

[0047] As in Fig. As shown in Figure 9, a first marker 161 is placed over the robot symbols 115, which correspond to the robots 3 with priorities within the predetermined number of top priorities among the robots 3 where an anomaly has occurred. Thus, the robot symbols 115 corresponding to the robots 3 with high maintenance priority are displayed in a different display mode than the robot symbols 115 corresponding to the robots 3 with lower maintenance priority, and the robot symbols 115 corresponding to the robots 3 where no anomaly has occurred. This allows the user to intuitively recognize that the robot 3 corresponding to the robot symbol 115 on which the first marker 161 is placed on the monitoring screen 160 is the robot 3 with high maintenance priority, and to determine the maintenance sequence appropriately and quickly.This improves the feasibility of maintenance work and reduces the risk of the deadline being reached without maintenance.

[0048] Furthermore, it shows Fig. 10, when a cursor 300 is placed on the first robot symbol 115, on which the first marker 161 on the monitoring screen 160 is placed, a pop-up screen 165 appears, describing detailed information about the anomaly that occurred in the robot 3 corresponding to the first robot symbol 115. Similarly, as in Fig. As shown in Figure 11, when the cursor 300 is placed on the second robot symbol 115, on which the first marker 161 on the monitoring screen 160 is placed, a pop-up screen 167 is displayed describing detailed information about the anomaly that occurred in robot 3, represented by the second robot symbol 115. As described above, the monitoring screen 160 does not always display detailed information about the anomaly, such as the anomaly details, the anomaly code, the maintenance procedure, and the number of days remaining, but it does display detailed information about the anomaly that occurred in robot 3, represented by robot symbol 115, when the cursor 300 is placed on robot symbol 115.This means that, unless a specific action is performed, only a large number of robot icons 115 in display modes corresponding to their maintenance priorities can be shown on the monitoring screen 160, and the user can reliably identify the robot icons 115 that correspond to the robots 3 with high maintenance priorities. This reduces the risk of overlooking a robot 3 with a high maintenance priority due to the large amount of information displayed on the monitoring screen 160.

[0049] The user can display detailed information about an anomaly that has occurred in robot 3, represented by robot symbol 115, simply by placing cursor 300 on robot symbol 115, instead of having to perform a cumbersome operation such as switching to another screen. This allows the user to review the detailed information without significant time and effort, compared to when the detailed information is always displayed. Furthermore, by displaying only the detailed information about the anomaly that has occurred in robot 3, represented by a specific robot symbol, it prevents misinterpretations of the detailed information and can improve the feasibility of maintenance work.

[0050] Furthermore, the pop-up screen displays 165 in Fig. 10 all display elements of the anomaly details, the anomaly code, the maintenance procedure and the number of days remaining, while the popup screen 167 in Fig. 11 only displays the number of days remaining. As described above, robots 3, represented by robot symbols 115 with many display elements, have a higher priority than robots 3, represented by robot symbols 115 with few display elements. The user can determine the priority of robot 3, represented by robot symbol 115, to some extent based on the number of display elements shown when the cursor 300 is placed on the robot symbol. Knowing the priority allows the user to establish a more suitable sequence for maintenance work, although knowing the exact priority is not necessary.

[0051] It should be noted that on the monitoring screen 160, the numerous robot symbols 115, corresponding to the numerous robots 3, are arranged according to the actual layout information. This allows the user to intuitively identify which robot 3 in the factory has experienced an anomaly. This saves time and effort in checking the robot 3 in which an anomaly has occurred and improves the feasibility of maintenance work.

[0052] Furthermore, as in the present embodiment, a second marking 163 can be placed over the robot symbols 115 that correspond to the robots 3 with priorities outside the predetermined number of top priorities among the robots 3 in which an anomaly has occurred, so that the robot symbols 115 that correspond to the robots 3 with lower maintenance priorities are displayed in a different display mode than the robot symbols 115 that correspond to the robots 3 in which no anomaly has occurred.

[0053] The user can intuitively recognize that the robots 3 corresponding to robot symbols 115, on which the second markers 163 are superimposed on the monitoring screen 160, are those robots 3 with a low maintenance priority but which have experienced an anomaly. This allows maintenance work to be performed on a robot 3 with a low maintenance priority, even if it has many days remaining and a low maintenance priority, as long as the details of its anomaly match those of the high-priority robots 3. This also facilitates the creation of long-term maintenance plans, thus improving the overall efficiency of maintenance operations.

[0054] The monitoring device 2 according to the present embodiment has a monitoring function for monitoring the occurrence of an anomaly in robots 3 and a display function for presenting to the user the robots 3 in which an anomaly has occurred. However, a feature of the monitoring device 2 according to the present embodiment lies in the display function. Therefore, the display function and the monitoring function of the monitoring device 2 according to the present embodiment can be distributed across a plurality of devices.That is, the robot monitoring system 1 can be formed from a plurality of robots 3, a monitoring device 2 which is connected to the plurality of robots 3 and configured to monitor the occurrence of an anomaly in each robot 3, and a display device which is connected to the monitoring device 2 and configured to present to the user the robots 3 in which an anomaly has occurred.

[0055] The monitoring device 2 according to the present embodiment has a function for diagnosing the occurrence of an anomaly. However, if the robot 3 itself has the function for diagnosing the occurrence of an anomaly, the monitoring device 2 according to the present embodiment does not need to have this function. In this case, the data receiving unit 23 receives anomaly information from the robot 3, which includes the plant ID, the robot ID, the anomaly details, the anomaly code, and the date and time of the anomaly's occurrence. The received anomaly information is recorded in the anomaly history management table.

[0056] In the present embodiment, a marker is placed over the robot symbol to change its display mode. However, as long as the display mode of the robot symbol can be changed, i.e., the user can distinguish the robots 3 with high maintenance priority from the other robots 3, the type of display mode is not limited to these. For example, the display mode of the robot symbol can be changed based on the blinking speed of the robot symbol, the color of the background of the robot symbol, or the like.When the robot icon blink rate is used, robot icons corresponding to robots with priorities within the predetermined number of peak priorities can blink at a first speed; robot icons corresponding to robots with priorities outside the predetermined number of peak priorities can blink at a second speed, which is lower than the first speed; and robot icons corresponding to robots where no anomaly has occurred can be set to not blink at all. It should be noted that the robot icons can be displayed in different modes depending on their priority. For example, the higher the priority, the faster the robot icons blink.

[0057] In the present embodiment, when a cursor is placed on a robot icon, the anomaly details, the anomaly code, the date and time of the anomaly occurrence, and the number of days remaining for the anomaly occurring in robot 3 represented by the robot icon (detailed information about the anomaly) are displayed on a pop-up screen. However, the method for displaying the detailed information about the anomaly is not limited to this. For example, placing the cursor on a robot icon can display detailed information about the anomaly occurring in robot 3 represented by the robot icon on the monitoring screen instead of a separate screen. Furthermore, if sufficient space is available to display detailed information about the anomaly, it is possible to display the detailed information about the anomaly at any time.

[0058] The following appendices provide further explanation with regard to the present embodiment and modification. (Annex 1)

[0059] A monitoring device 2 comprises: a monitoring unit 25 configured to monitor the occurrence of an anomaly in each of a plurality of industrial machines 3; a calculation unit 26 configured to calculate a priority for an industrial machine 3 in which the anomaly has occurred, based on a number of days remaining from the current date until a date on which maintenance work must begin;and a display unit 22, which is configured to display a graphic symbol representing an industrial machine 3 with a priority within a predetermined number of peak priorities among the industrial machines 3 in which the anomaly occurred, in a different display mode than a graphic symbol representing an industrial machine 3 with a priority outside the predetermined number of peak priorities among the industrial machines 3 in which the anomaly occurred, and a graphic symbol representing an industrial machine 3 in which the anomaly did not occur. (Annex 2)

[0060] In the monitoring device 2 according to Annex 1, the display unit 22 shows the graphic symbol representing the industrial machine 3 with a priority outside the specified number of peak priorities or top priorities among the industrial machines 3 in which the anomaly occurred, in a different display mode than the graphic symbol representing the industrial machine 3 in which the anomaly did not occur. (Annex 3)

[0061] In the monitoring device 2 according to Annex 1 or 2, the calculation unit 26 calculates the number of remaining days by subtracting an initial value for the number of days required for maintenance and the number of days elapsed since the occurrence of the anomaly from the number of days between the occurrence of the anomaly and the time at which a malfunction may occur due to the anomaly. (Annex 4)

[0062] In the monitoring device 2 according to Annex 3, the calculation unit 26 calculates the number of remaining days by replacing the initial value with a number of days specified by the user. (Annex 5)

[0063] In the monitoring device 2 according to Annex 3 or 4, the calculation unit 26 calculates the priority based on the duration of the days required for the maintenance work, if the number of remaining days is the same. (Annex 6)

[0064] The monitoring device 2 according to one of Annexes 1 to 5 further comprises a display count setting unit 28, which is configured to set the predetermined number according to a user instruction. (Annex 7)

[0065] The monitoring device 2 according to any one of Annexes 1 to 6 further comprises a display element setting unit 29 which is configured to set a display element relating to the anomaly for the industrial machine 3 in which the anomaly occurred, wherein the display unit 22 displays the display element set by the display element setting unit 29 together with the graphic symbol corresponding to the industrial machine 3 in which the anomaly occurred. (Annex 8)

[0066] In the monitoring device 2 according to Annex 7, when a user selects the graphic symbol corresponding to the industrial machine 3 in which the anomaly occurred, the display unit 22 shows a display element relating to the anomaly that occurred in the selected industrial machine 3 and that is set by the display element setting unit 29. (Annex 9)

[0067] In the monitoring device 2 according to Annex 7 or 8, the display element setting unit 29 specifies a number of industrial machines 3 for which the display element is to show the anomaly. (Annex 10)

[0068] In the monitoring device 2 according to one of Annexes 7 to 9, the display element relating to the anomaly includes at least one of the following elements: anomaly details, an anomaly code, a maintenance procedure and the number of days remaining.

[0069] While embodiments of the present disclosure have been described in detail, the present disclosure is not limited to the individual embodiments described above. These embodiments may be subjected to various additions, substitutions, modifications, partial deletions, etc., without departing from the essence of the invention or the idea and spirit of the present invention as derived from the content of the claims and their equivalents. For example, the embodiment described above shows the sequence of operations and the sequence of processes as examples, and the sequences are not limited to these. The same applies where numerical values ​​or formulas are used in the description of the embodiments described above. Explanation of reference symbols

[0070] 1: Robot monitoring system, 2: Monitoring device, 3: Robot, 10: Network, 11: Processor, 12: Input device, 13: Display device, 14: Communication device, 15: Storage device, 21: Input unit, 22: Display unit, 23: Data receiving unit, 24: Storage unit, 25: Monitoring unit, 26: Computing unit, 27: Screen generation unit, 28: Display count setting unit, 29: Display element setting unit, 30: Maintenance day count setting unit, 31: Destination unit QUOTES INCLUDED IN THE DESCRIPTION

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

[0000] JP 2005-107671

[0003]

Claims

[1] A monitoring device comprising: a monitoring unit configured to monitor for the occurrence of an anomaly in any of a variety of industrial machines; a calculation unit configured to calculate a priority for an industrial machine in which the anomaly occurred, based on the number of days remaining from a current date until a date on which maintenance must begin; and a display unit configured to display a graphic symbol representing an industrial machine with a priority within a predetermined number of top priorities among the industrial machines in which the anomaly occurred, in a different display mode than a graphic symbol representing an industrial machine with a priority outside the predetermined number of top priorities among the industrial machines in which the anomaly occurred, and as a graphic symbol representing an industrial machine in which no anomaly occurred. [2] The monitoring device according to claim 1, wherein the display unit displays the graphic symbol representing the industrial machine with a priority outside the predetermined number of peak priorities among the industrial machines in which the anomaly has occurred in a different display mode than the graphic symbol representing the industrial machine in which the anomaly has not occurred. [3] The monitoring device according to claim 1 or 2, wherein the calculation unit calculates the number of days remaining by subtracting from a number of days from the date of occurrence of the anomaly to a date on which a malfunction due to the anomaly may occur both an initial value for the number of days required for maintenance and the number of days that have passed since the date of occurrence of the anomaly. [4] The monitoring device according to claim 3, wherein the calculation unit calculates the number of days remaining by replacing the initial value with a number of days specified by the user. [5] The monitoring device according to claim 3 or 4, wherein the calculation unit calculates the priority based on the duration of the days required for the maintenance work when the number of remaining days is the same. [6] The monitoring device according to any one of claims 1 to 5, which further comprises: A display count setting unit that is configured to set the predetermined number according to a user instruction. [7] The monitoring device according to any one of claims 1 to 6, which further comprises: a display element setting unit that is configured to set a display element in relation to the anomaly for the industrial machine in which the anomaly occurred, wherein the display unit displays the display element set by the display element setting unit together with the graphic symbol that corresponds to the industrial machine in which the anomaly occurred. [8] Monitoring device according to claim 7, wherein when a user selects the graphic symbol corresponding to the industrial machine in which the anomaly occurred, the display unit displays a display element relating to the anomaly that occurred in the selected industrial machine and which is set by the display element setting unit. [9] Monitoring device according to claim 7 or 8, wherein the display element setting unit specifies a number of industrial machines to be displayed to the display element with respect to the anomaly. [10] Monitoring device according to one of claims 7 to 9, wherein the display element with respect to the anomaly comprises at least one of the following elements: anomaly details, an anomaly code, a maintenance method and the number of days remaining.

Images