JP6817153B2 - Alarm notification system and alarm notification method - Google Patents

Description

The present invention relates to an alarm notification system and an alarm notification method.

When an abnormality occurs in equipment such as a manufacturing line of an industrial system, it has been conventionally used to notify a maintenance person of the occurrence of the abnormality as an alarm. The content to be notified as an alarm includes the fact that an abnormality has occurred and information on the occurrence of the abnormality.

An alarm notification system applied to a conventional industrial system is described in, for example, Patent Document 1.
The technique described in Patent Document 1 notifies an alarm by sending an e-mail from the monitoring device to the maintenance terminal owned by the maintenance person when the monitoring device detects an abnormality of the monitoring target. Is. The information included in the alarm includes the URL (Uniform Resource Locator) of the WEB (World Wide Web) server function that the monitoring device has and is provided as a hyperlink.

By accessing the monitoring device from the notified URL, the maintenance terminal that has received the e-mail can display information on the abnormality and control the monitoring target. The maintenance terminal to which the alarm is notified is determined by the content of the abnormality. Then, if there is no response even after a certain period of time has passed from the notification of the alarm to the maintenance terminal, re-notification is performed.

In the technique described in Patent Document 1, the maintenance terminal to be notified of the alarm is determined in advance for each abnormality, but in addition to such a technique, for example, a maintenance terminal owned by a maintenance person A method of selecting a maintenance terminal to send an e-mail based on the location information has also been proposed.
Further, as a maintenance terminal used by a maintenance person, it is considered to use a glasses-type wearable terminal to directly display the content of the abnormality in the field of view of the maintenance person.

Japanese Unexamined Patent Publication No. 2003-5827

In the manufacturing line of an industrial system, a system that notifies the maintenance staff of an alarm to a mobile terminal owned by the maintenance staff is useful as a means of immediately notifying the maintenance staff of an abnormality that occurs during manufacturing and prompting countermeasures. is there. Here, an abnormality is not only a stoppage of production equipment operating on a simple production line, but also a product that occurs in the process of manufacturing a product, such as insufficient pressure when crimping parts to the product or dropping the product during visual inspection. Includes any event that causes the product to be judged as defective.

On the other hand, it is important to meet the following requirements 1, 2 and 3 when alarm notification is sent on the manufacturing line of an industrial system.
[Requirement 1] It is necessary to perform so-called hands-free so that maintenance personnel can receive and confirm alarm notifications without interrupting the work being executed.
[Requirement 2] It is necessary to be able to dynamically set the alarm received by the maintenance person for each terminal.
[Requirement 3] Notification to maintenance personnel needs to be made in real time.

Of these three requirements, the above [Requirement 1] is a requirement for ensuring the safety of maintenance personnel. [Requirement 2] is required because the content of the abnormality to be dealt with differs depending on the position and scope of responsibility of the maintenance person, or because the number of terminals used also changes depending on the amount of work on the day and the production line engaged. It is a requirement. For example, one maintenance person may be in charge of maintenance of two production lines, one production line may be in charge of two maintenance persons, one person may be in charge of abnormal handling of production equipment, and the other. A person may be in charge of handling abnormalities in product inspection. In this way, which alarm should be received by which terminal differs depending on the situation, so it is necessary for each maintenance person to be able to set which alarm is to be received for each terminal.

Further, [Requirement 3] is a requirement for minimizing the production of a product that may be defective. Many processes are automated in the production line of the industrial system, and mass production is realized by operating continuously. Therefore, for example, continuing to manufacture a product while an abnormality has occurred in the production equipment requires measures such as additional inspection and disposal of the product manufactured during that period, which is a factor that pushes up the production cost. Therefore, the maintenance staff needs to be notified in real time.

For these requirements, for example, the hands-free requirement of [Requirement 1] can be satisfied by applying a glasses-type wearable terminal as a maintenance terminal. However, the eyeglass-type wearable terminals currently in practical use are larger in size and heavier than ordinary eyeglasses, and cannot be said to be comfortable to wear. Therefore, at present, it is not preferable to have a maintenance person always wear a glasses-type wearable terminal for alarm notification.

Further, regarding [Requirement 2], for example, as described in Patent Document 1, the maintenance terminal to be the notification destination of the alarm is determined in advance for each abnormality content, and the management for determining the maintenance terminal to be the notification destination is performed. If it can be done properly, it can be dealt with. However, in reality, as mentioned above, the number of terminals used varies depending on the amount of work done on that day and the production line in which they are engaged, so it is necessary to change the maintenance terminal that notifies each day. Has a problem that it takes a lot of time and effort to change the notification terminal.

Further, regarding the real-time property of [Requirement 3], for example, in the technique described in Patent Document 1, an alarm is notified in real time by e-mail, and if there is no response from the notified terminal for a certain period of time, it is electronically sent to another destination. I try to send an email. Therefore, there is no problem if the maintenance person can immediately check the content of the notification on the terminal that sent the first e-mail, but if the first e-mail has not arrived, the response will be delayed. In particular, many metal production facilities are operating on the production line of industrial systems, and the radio wave environment is noisy and of low quality, so e-mail does not reach the terminals owned by maintenance personnel on the production line. Can happen.
As described above, no conventional alarm notification system meets the above-mentioned three requirements.

An object of the present invention is to provide an alarm notification system and an alarm notification method capable of dynamically changing a terminal that receives an alarm according to a situation.

In order to solve the above problems, for example, the configuration described in the claims is adopted.
The present application includes a plurality of means for solving the above problems. For example, a notification delivery server that generates an alarm based on the occurrence of an alarm target event and a notification delivery destination of the alarm generated by the notification delivery server. It is provided with a message broker that determines and sends an alarm to the determined delivery destination, and a notification receiving client that is wirelessly connected to the message broker via an access point and receives an alarm transmitted by the message broker.
Then, the notification distribution server sends a list of subject information related to the alarm to the message broker when the system starts, and the message broker sends a list of subject information related to the alarm information to the notification receiving client at the start of business to notify the message. The receiving client receives the list of subject information about the alarm sent from the message broker at the start of business, and when there is a subject selection from the received list, sends the information of the selected subject to the message broker. I made it register with the message broker.

According to the present invention, it is possible to realize an alarm notification system that can dynamically change the alarm received dynamically according to the situation. For example, it can be applied to a production line of an industrial system having a low quality radio wave environment to notify an appropriate alarm. Will be able to.
Issues, configurations and effects other than those described above will be clarified by the description of the following embodiments.

It is a block diagram of the whole system by the 1st Embodiment example of this invention. It is a block diagram which shows the functional structure of the whole system by the 1st Embodiment of this invention. It is a block diagram which shows the example of the notification delivery server and the message broker by the example of 1st Embodiment of this invention. It is a block diagram which shows the example of the wearable terminal by the example of 1st Embodiment of this invention. It is a block diagram which shows the example of the smartphone by the example of 1st Embodiment of this invention. It is explanatory drawing which shows the master information by the 1st Embodiment example of this invention. It is explanatory drawing which shows the client information by the 1st Embodiment example of this invention. It is explanatory drawing which shows the user information by the 1st Embodiment example of this invention. It is a sequence diagram which shows the processing example at the time of system start-up according to the 1st Embodiment example of this invention. It is a sequence diagram which shows the processing example at the time of use setting by the 1st Embodiment example of this invention. It is a sequence diagram which shows the processing example at the time of business start by the 1st Embodiment example of this invention. It is a sequence diagram which shows the processing example at the time of abnormality occurrence by the example of 1st Embodiment of this invention. It is a sequence diagram which shows the processing example at the time of wireless network disconnection and the end of business by the example of 1st Embodiment of this invention. It is a block diagram of the whole system by the 2nd Embodiment of this invention. It is a block diagram which shows the example of the notification delivery server and the message broker by the example of the 2nd Embodiment of this invention. It is a block diagram which shows the example of the wearable terminal by the 2nd Embodiment of this invention. It is explanatory drawing which shows the master information by the 2nd Embodiment of this invention. It is explanatory drawing which shows the client information by the 2nd Embodiment of this invention. It is a sequence diagram which shows the processing example at the time of system start-up according to the 2nd Embodiment example of this invention. It is a sequence diagram which shows the processing example at the time of use setting by the 2nd Embodiment example of this invention. It is a sequence diagram which shows the processing example at the time of business start by the 2nd Embodiment example of this invention. It is a sequence diagram which shows the processing example at the time of abnormality occurrence by the 2nd Embodiment example of this invention.

<1. Example of the first embodiment>
Hereinafter, examples of the first embodiment of the present invention will be described with reference to FIGS. 1 to 13.
[1-1. System-wide configuration]
FIG. 1 is a physical configuration diagram of an alarm notification system according to an example of the first embodiment of the present invention. The example shown in FIG. 1 is an example when the alarm notification system is applied to a manufacturing line of an industrial system.
A production line 1100 (1100a: A line to 1100b: B line) exists in the workshop 1000, and an intelligent camera 1400 (1400a to 1400f) capable of detecting an abnormality in the equipment is attached to the production equipment of each line. Has been done. The intelligent camera 1400 includes an alarm output unit 1410 (FIG. 2) that photographs the equipment to be monitored, determines the presence or absence of an abnormality in the equipment from the captured image, and outputs an alarm if there is an abnormality.

There is one maintenance person 1500 (1500a-1500b) for each line as a person to deal with the abnormality detected by the intelligent camera 1400, and the maintenance person 1300 is in the laboratory for the purpose of supervising the maintenance person 1500. There is one person in. The maintenance staff 1500 and the maintenance manager 1300 wear watch-type wearable terminals 1600 (1600a to 1600c), and the terminals 1600 perform wireless communication through an access point 1200 installed in the laboratory. The wearable terminal 1600 functions as a notification receiving client 1610 (FIG. 2) described later.

A smartphone 2100 and a computer 2200 are provided in the server room 2000. The smartphone 2100 is paired with the wearable terminal 1600. Maintenance software 2110 (FIG. 2) is mounted on the smartphone 2100. Although FIG. 1 shows an example in which the smartphone 2100 exists in the server room 2000, for example, a maintenance manager 1300 or a maintenance manager 1500 may possess the smartphone 2100. The computer 2200 functions as a notification distribution server 2210 and a message broker 2220 (FIG. 2), which will be described later.
The access point 1200, the intelligent camera 1400, and the computer 2200 are connected to the wired network 3000, and they can communicate with each other, including the wearable terminal 1600 that uses the access point 1200.

FIG. 2 is a block diagram showing the functions of the alarm notification system.
The computer 2200 functions as a notification distribution server 2210 and a message broker 2220. In addition, the wearable terminal 1600 functions as a notification receiving client 1610. Further, maintenance software 2110 is mounted on the smartphone 2100.

The notification distribution server 2210 has a subject determination unit 2212, a master information holding unit 2213, a client information holding unit 2211, and a broker connection information holding unit 2214.
The subject determination unit 2212 determines the subject which is the explanatory information of the received alarm.
The master information holding unit 2213 holds master information which is a set of elements constituting the subject. In the example of the present embodiment, the master information is composed of the line name list 100, for example, as shown in FIG.

The client information holding unit 2211 holds client information which is information about a component of the subject of the alarm received by the notification receiving client 1610. In the example of the present embodiment, the client information is configured as a correspondence table 200 of the line name and the client ID uniquely indicating the notification receiving client, as shown in FIG. 7, for example.
The broker connection information holding unit 2214 holds broker connection information which is connection information to the message broker 2220.
The details of the information (table) shown in FIGS. 6 and 7 will be described later.

The message broker 2220 includes a user information holding unit 2221, a distribution destination determination unit 2222, a distribution information holding / retransmitting unit 2223, a distribution information holding unit 2224, and a disconnection detecting unit 2225.
The user information holding unit 2221 holds the subject of the distribution information received by the user of the message broker 2220 and the connection information to the user. Here, the subject of the distribution information and the connection information to the user are collectively referred to as "user information". As shown in FIG. 8, for example, the user information is indicated by a correspondence table between the subject of the distribution information received by the user and the IP address of the user. Details of the user information shown in FIG. 8 will be described later.

The delivery destination determination unit 2222 determines the delivery destination of the delivery information.
The distribution information holding / resending unit 2223 holds the distribution information and retransmits the distribution information as needed.
The distribution information holding unit 2224 holds the actual distribution information.
The disconnection detection unit 2225 detects that the network connection between the notification receiving client 1610 and the message broker 2220 has been disconnected. In this system, the notification receiving client 1610 always connects to the message broker 2220 via a network during operation. Therefore, the disconnection detection unit 2225 detects the disconnection of the wireless connection, for example, when the wearable terminal 1600 moves to a place where the radio wave from the access point 1200 does not reach, or when the wearable terminal 1600 runs out of battery, the power is turned off. Is expected.

The notification receiving client 1610 includes an alarm holding unit 1611, a master information holding unit 1612, a client information holding unit 1613, and a broker connection information holding unit 1614.
The alarm holding unit 1611 holds the message transmitted from the message broker 2220.
The master information holding unit 1612 holds master information which is a set of elements constituting the subject.
The client information holding unit 1613 holds the client information which is a component of the subject of the alarm received by the notification receiving client 1610.
The broker connection information holding unit 1614 holds broker connection information which is connection information to the message broker 2220.

The maintenance software 2110 has an input unit 2111 used when inputting something to the notification receiving client 1610. The input unit 2111 functions as an input to the notification receiving client 1610. When the smartphone 2100 executes the maintenance software 2110, the smartphone 2100 and the wearable terminal 1600 are wirelessly connected. In this case, the smartphone 2100 and the wearable terminal 1600 perform wireless communication using the short-range wireless module 2106 (FIG. 5) described later. As the short-range wireless module 2106, for example, Bluetooth (registered trademark) is used, and communication is performed only with a partner paired in advance.

[1-2. Detailed configuration of each device]
FIG. 3 shows the configuration of a computer 2200 that functions as a notification distribution server 2210 and a message broker 2220.
The computer 2200 has a main storage unit 2201, a processor 2203, a wired LAN module 2204, and a secondary storage unit 2205 as hardware. The notification distribution server 2210 and the message broker 2220 are realized as processes in the operation process group 2202 existing in the main storage unit 2201, and are operated by the processor 2203.
The master information and the broker connection information, which are the information used by the notification distribution server 2210 and the message broker 2220, are held in the master information holding unit 2213 and the broker connection information holding unit 2214. The master information holding unit 2213 and the broker connection information holding unit 2214 are placed in the secondary storage unit 2205, and are read into the area of each process of the main storage unit 2201 by the processor 2203 as needed.

All other components are placed in the area of each process in the main memory 2201. When the notification distribution server 2210 and the message broker 2220 communicate with the outside, the wired LAN module 2204 is used.

FIG. 4 shows the configuration of the wearable terminal 1600.
The wearable terminal 1600 has a main storage unit 1601, a touch panel display 1603, a processor 1604, a wireless LAN module 1605, a short-range wireless module 1606, and a secondary storage unit 1607 as hardware.
The notification receiving client 1610 is realized as a process in the operating process group 1602 existing in the main storage unit 1601, and is operated by the processor 1604. The master information holding unit 1612, the client information holding unit 1613, and the broker connection information holding unit 1614 that hold the non-volatile information used by the notification receiving client 1610 are placed in the secondary storage unit 1607. Then, these pieces of information are read into the process area of the notification receiving client 1610 in the main storage unit 1601 by the processor 1604 as needed. All other components are placed in the process area of the notification receiving client 1610 in the main storage unit 1601.

Further, when the notification receiving client 1610 communicates with the outside, the wireless LAN module 1605 is used. However, when communicating with the paired smartphone 2100, the short-range wireless module 1606 is used. Further, when the notification receiving client 1610 accepts the input from the user, the touch panel display 1603 is used.

FIG. 5 is a diagram showing the configuration of the smartphone 2100.
The smartphone 2100 has a main storage unit 2101, a touch panel display 2103, a processor 2104, a wireless LAN module 2105, a short-range wireless module 2106, and a secondary storage unit 2107 as hardware.
The maintenance software 2110 is realized as a process in the operating process group 2102 existing in the main storage unit 2101, and is operated by the processor 2104. All the components of the maintenance software 2110 are placed in the process area of the maintenance software 2110 in the main memory 2101. Further, when the maintenance software 2110 communicates with the paired wearable terminal 1600, the short-range wireless module 2106 is used. Further, when the maintenance software 2110 accepts input from the user, the touch panel display 2103 is used.

[1-3. Specific example of information]
Next, an example of the information held by the notification distribution server 2210 and the message broker 2220 will be described.
FIG. 6 is a table showing a list 100 of line names, which is information held by the master information holding unit 2213 of the notification distribution server 2210. Here, it has information on two line names, A line and B line.
FIG. 7 is a table showing the client information 200 held by the client information holding unit 2211 of the notification distribution server 2210.
The client information 200 includes information on the client ID to be notified for each line name. In the example of FIG. 7, the A line has the information of the client 1 (element 210a) and the client 3 (element 210c), and the B line has the information of the client 2 (element 210b) and the client 3 (element 210c).

FIG. 8 is a table showing the user information 300 held by the user information holding unit 2221 of the message broker 2220.
The user information 300 is a correspondence table between the subject of the distribution information received by the user and the IP address of the user, and each subject has an IP address of the distribution destination. For example, "/ client connection" has the IP address 310 of the notification distribution server 2210, and "/ client disconnection" also has the IP address 310 of the notification distribution server 2210. Further, as the "/ master distribution" information, the IP addresses 330a, 330b, 330c of the respective clients 1, 2, and 3 are provided. Further, the "/ A line" has the IP addresses 340a and 340c of the clients 1 and 3, and the "/ B line" has the IP addresses 340b and 340c of the clients 2 and 3.

[1-4. Operation example]
Hereinafter, the operation of the alarm notification system in the embodiment of the present embodiment will be described by dividing into phases at the time of system start-up, use setting, business start, abnormality detection, wireless network disconnection, and business end.
[1-4-1. At system startup]
FIG. 9 is a sequence diagram showing an operation at the time of system startup.
The notification distribution server 2210 transmits the master information to the message broker 2220 with the subject "master distribution" and the "delivery registration flag" added (step S11). Since the message broker 2220 has the "delivery flag at the time of reception registration" added to the received master information, the delivery information holding / retransmitting section 2223 saves the master information in the delivery information holding section 2224 (step S12).

The notification distribution server 2210 receives and registers the subject "notification receiving client connection" and "notification receiving client disconnection" with the message broker 2220 (step S13). The message broker 2220 stores the requested reception registration information in the user information holding unit 2221 (step S14). As a result, the elements 310 and 320 shown in FIG. 8 are registered in the message broker 2220.

[1-4-2. At the time of usage setting]
FIG. 10 is a sequence diagram showing an operation at the time of usage setting.
The maintenance person 1500 and the maintenance person 1300 using the wearable terminal 1600 edit the broker connection information of the broker connection information holding unit 1614 of the notification receiving client 1610 through the input unit 2111 of the maintenance software 2110 (step S21). However, if the broker connection information has not changed since the last use, there is no need to edit it.

The notification receiving client 1610 receives and registers the subject "master delivery" with the message broker 2220 (step S22). The message broker 2220 stores the requested reception registration information in the user information holding unit 2221 (step S23). Specifically, the elements 330a to 330c in FIG. 8 are stored.

Next, the message broker 2220 saves the master information with the "delivery registration flag at the time of reception registration" added to the subject of the "master delivery" sent from the notification delivery server 2210 in the process at the time of system startup as the delivery information. Therefore, the master information is transmitted to the notification receiving client 1610 (step S24). The notification receiving client 1610 stores the received master information in the master information holding unit 1612. The master information held in the master information holding unit 1612 is displayed on the touch panel display 1603 of the wearable terminal 1600. The master information displayed at this time is, for example, information on a list of line names as shown in FIG.

The maintenance person 1500 and the maintenance person 1300 who use the wearable terminal 1600 select a line name from the displayed master information (step S25). The notification receiving client 1610 stores the selected line name as client information in the client information holding unit 1613 together with the client ID that uniquely identifies the notification receiving client. Specifically, the elements 210a to 210c shown in FIG. 7 are stored in the respective wearable terminals 1600.

[1-4-3. At the start of business]
FIG. 11 is a sequence diagram showing an operation at the start of business.
The notification receiving client 1610 adds the subject “client connection” and transmits the client information (FIG. 7) held by the client information holding unit 1613 to the message broker 2220 (step S31). The message broker 2220 scans the user information holding unit 2221 and checks whether or not the subject "client connection" is registered for reception (step S32). Here, since the notification distribution server 2210 is registered for reception when the system is started, the client information is transmitted to the notification distribution server 2210 (step S33). The notification distribution server 2210 saves the received client information in the client information holding unit 2211 (step S34). Therefore, the client information holding unit 2211 stores the client information of all the notification receiving clients 1610, that is, the elements 210a to 210c in FIG. 7.

Further, the notification receiving client 1610 transmits the client information to the message broker 2220 with the subject "notification receiving client disconnection" and "disconnection delivery flag" added (step S35). Since the message broker 2220 has the "disconnection flag" added, the distribution information holding / retransmitting unit 2223 saves the received client information in the distribution information holding unit 2224 (step S36).
Further, the notification receiving client 1610 receives and registers the subject "/ line name" with the message broker 2220 based on the client information (step S37). The message broker 2220 stores the requested reception registration information in the user information holding unit 2221 (step S38). Here, the elements 340a to 340c in FIG. 8 are stored.

[1-4-4. When an abnormality occurs]
FIG. 12 is a sequence diagram showing an operation when an abnormality occurs.
The intelligent camera 1400 that monitors the production line detects the occurrence of an abnormality and transmits an alarm to the notification distribution server 2210 (step S41). The notification distribution server 2210 determines on which line the alarm has occurred by the subject determination unit 2212, and examines whether the notification receiving client that receives the alarm on that line is stored in the client information holding unit 2211 (step S42). .. Here, when the notification receiving client 1610 that receives the alarm of the line is saved, the subject "/ line name" is added to the delivery destination determined in the alarm delivery destination determination process to send the alarm message broker 2220. (Step S43). In this way, the notification distribution process is performed from the notification distribution server 2210 to the message broker 2220.

The message broker 2220 scans the user information of the user information holding unit 2221, checks whether the subject "/ line name" is registered for reception, and performs an alarm delivery destination determination process (step S44). Here, since the specific notification receiving client 1610 has been registered for reception at the start of the business described above, the alarm is transmitted to the corresponding notification receiving client 1610 (step S45). The notification receiving client 1610 holds the received alarm by the alarm holding unit 1611 and presents it to the user as alarm information (step S46). For example, an abnormal line name is displayed on the touch panel display 1603 of the wearable terminal 1600.

[1-4-5. When wireless network is disconnected]
FIG. 13 is a sequence diagram showing operations when the wireless network is disconnected and when the business is completed.
When the wireless network is disconnected, the disconnection detection unit 2225 of the message broker 2220 detects the disconnection with the notification receiving client 1610 (step S51). At this time, the message broker 2220 deletes the reception registration information of the disconnected notification reception client 1610 from the user information of the user information holding unit 2221 (step S52).

Further, here, the client information to which the "disconnection flag" is added to the subject of "client disconnection" is stored in the distribution information holding unit 2224, and the notification distribution server 2210 sets the subject "client disconnection" at the time of system startup. Is registered for reception. Therefore, the message broker 2220 transmits the deleted client information to the notification distribution server 2210 (step S53).
The notification distribution server 2210 that has received this information deletes the same information as the received client information from the client information held by the client information holding unit 2211 (step S54).

At the end of business, the wireless network disconnection detection in step S51 of FIG. 13 becomes the wireless network disconnection detection based on the business termination. Then, the processes of steps S52 to S54 are executed in the same manner as when the wireless network is disconnected as shown in FIG.

According to the alarm notification system of the first embodiment described above, when an abnormality occurs, the alarm for the occurrence of the abnormality is surely and quickly installed by the maintenance manager 1300 and the maintenance staff 1500 of the line where the abnormality has occurred. It reaches the wearable terminal 1600. Since the wearable terminal 1600 can check the display without interrupting the work, the alarm can be checked hands-free.

Further, according to the alarm notification system of the first embodiment, it is not necessary to preset the type of alarm to be received, and an alarm notification system capable of dynamically changing the alarm to be received according to the situation is realized. That is, the notification receiving client 1610 that receives the alarm can be registered in the usage setting, and the alarm can always be transmitted to the necessary notification receiving client 1610.
Further, the message broker 2220 can detect the disconnection with the notification receiving client 1610 and prevent the notification receiving client 1610 from being notified of the alarm when the wireless connection is disconnected. Therefore, the message broker 2220 can find out the situation where the alarm cannot be notified, and can take measures such as dynamically changing the wearable terminal 1600 that receives the alarm according to the situation, so that the wearable terminal 1600 can be reliably notified of the alarm in real time. become.

<2. Example of the second embodiment>
Next, an example of the second embodiment of the present invention will be described with reference to FIGS. 14 to 22. In FIGS. 14 to 22, the same parts as those in FIGS. 1 to 13 described in the first embodiment are designated by the same reference numerals, and duplicate description will be omitted.

In the first embodiment described above, the line name in which the alarm occurred is used as the subject that is the explanatory information of the alarm, and the alarm is notified to all the wearable terminals 1600 that receive the same subject at the same time. It was a thing. On the other hand, in the second embodiment, not only the line name but also the classification of the generated abnormality is treated as the subject, and the order of alarm notification can be selected according to the priority.

[2-1. System-wide configuration]
FIG. 14 is a functional configuration diagram of the alarm notification system in the example of the present embodiment.
The notification distribution server 2210 has a response information holding unit 2215 that holds the response information received from the notification receiving client 1610, and an alarm information holding unit 2116 that holds the alarm information that is the history of the received alarms. Other configurations are the same as those of the alarm notification system shown in FIG.

[2-2. Detailed configuration of each device]
FIG. 15 shows the configuration of the computer 2200 in FIG.
The alarm information (alarm generated by the intelligent camera 1400) used by the notification distribution server 2210 is held in the alarm information holding unit 2216 of the secondary storage unit 2205. This alarm information is written to the area of the notification distribution server 2210 in the main storage unit 2201 by the processing of the processor 2203.

FIG. 16 shows the configuration of the wearable terminal 1600 in FIG.
The response information used by the notification receiving client 1610 is stored in the response information holding unit 1615 in the process area of the notification receiving client 1610 in the main storage unit 1601.

[2-3. Specific example of information]
Next, an example of the information held in the notification distribution server 2210 and the message broker 2220 will be described.
FIG. 17 shows the master information held by the master information holding unit 2213 in the present embodiment. Here, as shown in FIG. 17, it is composed of a line name list 410, an abnormality classification list 420, and a correspondence table 430 between the name of the position performing maintenance and the notification priority for notifying the alarm. To. The abnormality classification list 420 has two classifications, equipment abnormality and inspection abnormality. In the correspondence table 430, the maintenance person has the notification priority 1 and the maintenance person has the notification priority 2.

FIG. 18 shows the client information held by the client information holding unit 2211 in the present embodiment.
Here, the client information is configured as a correspondence table 500 with a line name, an abnormality classification, a notification priority, and a client ID that uniquely indicates a notification receiving client.

[2-4. Operation example]
Next, the operation of the alarm notification system will be described with reference to the sequence diagrams of FIGS. 19 to 22.
In the sequence diagrams of FIGS. 19 to 22, the same step numbers are assigned to the same processing operations as those described in FIGS. 9 to 12 of the first embodiment.

FIG. 19 is a sequence diagram showing an operation at the time of system startup.
At the time of system startup, the subjects that the notification distribution server 2210 registers for reception with the message broker 2220 in step S13'are "client connection", "client disconnection", and "client response". The message broker 2220 stores the requested reception registration information in the user information holding unit 2221 (step S14).

FIG. 20 is a sequence diagram showing an operation at the time of usage setting.
At the time of setting the use, in step S25', the maintenance person 1500 and the maintenance person 1300 select the line name, the abnormality classification, and their job title from the master information held by the master information holding unit 1612 by the wearable terminal 1600. .. The notification receiving client 1610 stores the selected line name, the abnormality classification, the notification priority corresponding to the job title, and the ID uniquely identifying the notification receiving client as client information. This client information is held in the client information holding unit 1613 of the wearable terminal 1600.

FIG. 21 is a sequence diagram showing an operation at the start of business.
At the start of business, the notification receiving client 1610 receives and registers the subject "/ line name / abnormality classification / notification priority / client ID" with the message broker 2220 based on the client information held by the client information holding unit 1613. (Step S37'). The message broker 2220 stores the requested reception registration information in the user information holding unit 2221 (step S38').

FIG. 22 is a sequence diagram showing an operation when an abnormality occurs.
The intelligent camera 1400 that monitors the production line detects the occurrence of an abnormality and transmits an alarm to the notification distribution server 2210 (step S41'). At this time, the notification distribution server 2210 adds an alarm ID that can uniquely identify the received alarm and stores it in the alarm information holding unit 2216. In addition, it is determined which abnormality classification the alarm occurred in which line, and it is examined whether or not the notification receiving client 1610 that receives the alarm of the abnormality classification of the line is stored in the client information holding unit 2211. (Step S42'). Here, when the notification receiving client 1610 that receives the alarm of the abnormality classification of the line is stored, the subject "/ line" is used by using the information of the notification receiving client having the highest notification priority among them. An alarm is transmitted to the message broker 2220 with "name / abnormality classification / notification priority / client ID" added (step S43').

The message broker 2220 scans the user information of the user information holding unit 2221 and checks whether or not the subject "/ line name / abnormality classification / notification priority / client ID" is registered for reception (step S44'). .. Here, since the notification receiving client 1610 has registered the reception at the start of the business described above, the alarm is transmitted to the notification receiving client 1610 (step S45'). The notification receiving client 1610 presents the received alarm to the user (step S46'). For example, the touch panel display 1603 of the wearable terminal 1600 displays an abnormal line name and an abnormal classification.

Further, at the same time as presenting the alarm to the user, the notification receiving client 1610 receives the input that can be handled or cannot be handled by the touch panel operation or the like, and creates the response information to be held by the response information holding unit 1615. When the response information holding unit 1615 registers the response information, the notification receiving client 1610 transmits the response information to the message broker 2220 by adding the subject “client response” and the alarm ID attached to the alarm (step S46). ). The message broker 2220 that has received the response information scans the user information holding unit 2221 and checks whether the subject "client response" is registered for reception (step S47). Here, since the notification distribution server 2210 receives and registers when the system is started, the response information is transmitted to the notification distribution server 2210 (step S48).
The notification distribution server 2210 holds the received response information in the response information holding unit 2215. Then, the notification distribution server 2210 confirms the content of the response information held by the response information holding unit 2215 (step S49). Here, if the response information can be handled, the process ends.

If the response information cannot be handled, the processes from step S42'to step S49 are repeated. That is, the alarm information held in the alarm information holding unit 2216 is acquired based on the alarm ID added to the response information. Further, the subject determination unit 2212 determines in which line the alarm occurred and which abnormality classification corresponds to, and the notification receiving client 1610 that receives the alarm of the abnormality classification of the line is stored in the client information holding unit 2211. Find out if it is done.

Then, when the notification receiving client 1610 that receives the alarm is saved, the subject "/ line name / abnormality classification" is based on the information of the notification receiving client 1610 having the next highest priority after the previous transmission. / Notification priority / Client ID ”is added and an alarm is sent to the message broker 2220. If the information of the notification receiving client 1610 having the next highest priority does not exist, the process of transmitting the alarm again is performed using the information of the notification receiving client 1610 having the highest priority.
After that, the alarm transmission process is repeated until the response on the notification receiving client 1610 becomes available.

As described above, according to the alarm notification system of the second embodiment, the maintenance personnel of the production line of the industrial system receive the alarm hands-free and perform the maintenance work as in the first embodiment. Is possible.
Further, according to the second embodiment, not only the line name but also the information of the abnormality classification and the notification priority can be used to notify the notification receiving client 1610 having a high notification priority for each abnormality classification. Become. Then, when the notification receiving client 1610 having the highest priority cannot respond, an alarm is transmitted to the notification receiving client 1610 having the next priority, and the alarm can be reliably notified in real time. If the notification receiving client 1610 having a low priority does not exist, the alarm is resent to the notification receiving client 1610 that cannot respond, and an appropriate alarm can be notified.

<4. Modification example>
It should be noted that the examples of the embodiments described so far are merely suitable examples, and the present invention is not limited to the examples of the embodiments described here. For example, the master information may be configured as a list of combinations of personal names and themes registered as presets, and the notification receiving client may dynamically determine the alarm type to be received by selecting from the list.

Further, in each of the embodiments described so far, the client terminal that gives an alarm notification is a wristwatch-type wearable terminal worn by a maintenance person or the like, but the form of the wearable terminal is not limited to the wristwatch-type. For example, it may be a glasses-type wearable terminal. Alternatively, another form of terminal such as a smartphone may be possessed by a maintenance person or the like and used as a client terminal for alarm notification. However, it is preferable to use a wearable terminal such as a wristwatch because it can be handled hands-free.

Further, the present invention is not limited to the above-described embodiment, and includes various modifications. 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 those having all the described configurations. Further, it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment or modification, and the configuration of one embodiment may be replaced with another embodiment or modification. It is also possible to replace it with the example configuration. Further, it is possible to add / delete / replace a part of the configuration of the embodiment with another configuration.

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 and functions 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 hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a 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.

1000 ... Workshop, 1100 ... Production line, 1200 ... Access point, 1300 ... Maintenance manager, 1400 ... Intelligent camera, 1410 ... Alarm output unit, 1500 ... Maintenance staff, 1600 ... Wearable terminal, 1601 ... Main storage unit, 1602 ... Operation process group, 1603 ... Touch panel display, 1604 ... Processor, 1605 ... Wireless LAN module, 1606 ... Short-range wireless module, 1607 ... Secondary storage unit, 1610 ... Notification reception client, 1611 ... Alarm holding unit, 1612 ... Master Information holding unit, 1613 ... Client information holding unit, 1614 ... Broker connection information holding unit, 1615 ... Response information holding unit, 2000 ... Server room, 2100 ... Smartphone, 2101 ... Main storage unit, 2102 ... Operating process group, 2103 ... Touch panel Expression display, 2104 ... Processor, 2105 ... Wireless LAN module, 2106 ... Short-range wireless module, 2107 ... Secondary storage unit, 2110 ... Maintenance software, 2111 ... Input unit, 2116 ... Alarm information holding unit, 2200 ... Computer, 2201 ... Main storage unit 2202 ... Operating process group 2203 ... Processor 2204 ... Wired LAN module 2205 ... Secondary storage unit 2210 ... Notification distribution server, 2211 ... Client information holding unit 2212 ... Subject determination unit, 2213 ... Master information Holding unit, 2214 ... Broker connection information holding unit, 2215 ... Response information holding unit, 2216 ... Alarm information holding unit, 2220 ... Message broker, 2221 ... User information holding unit, 2222 ... Delivery destination determination unit, 2223 ... Delivery information holding -Retransmission unit, 2224 ... Distribution information holding unit, 2225 ... Disconnection detection unit, 3000 ... Wired network

Claims (5)

A notification distribution server that determines alarm notification based on the occurrence of an alarm target event,
A message broker that determines the delivery destination of the alarm that is determined to be notified by the notification delivery server and sends the alarm to the determined delivery destination.
A notification receiving client that is wirelessly connected to the message broker via an access point and receives the alarm transmitted by the message broker.
The notification distribution server sends a list of subject information related to the alarm to the message broker when the system starts up.
The message broker sends a list of subject information regarding alarm information to the notification receiving client at the start of business.
The notification receiving client receives a list of subject information regarding an alarm sent from the message broker at the start of business, and when a subject is selected from the received list, the information of the selected subject is sent to the message. An alarm notification system that is sent to a broker and registered with the message broker . The notification distribution server has a subject determination unit that dynamically determines a subject related to an alarm from an alarm target event that has occurred.
The alarm notification system according to claim 1, wherein the subject determination unit adds the determined subject to an alarm and supplies the determined subject to the message broker. The alarm notification system according to claim 2, wherein the message broker has a delivery destination determination unit that determines a notification reception client of an alarm transmission destination according to a subject attached to the received alarm. The alarm notification system according to any one of claims 1 to 3 , wherein the notification receiving client is composed of a wearable terminal worn by an operator. Notification delivery processing that determines alarm notification based on the occurrence of an alarm target event,
The alarm delivery destination determination process of determining the delivery destination of the alarm determined to be notified by the notification delivery process and transmitting the alarm to the determined delivery destination,
In the access point by wireless connection notification recipient client, we see containing and a alarm transmission process of transmitting the alarm to the notification recipient client of the delivery destination determined by the alarm delivery destination determining process,
In the notification delivery process, a list of subject information related to the alarm is sent to the alarm delivery destination determination process when the system is started.
In the alarm delivery destination determination process, a list of subject information related to alarm information is sent to the alarm transmission process at the start of business.
In the alarm transmission process, a list of subject information related to the alarm sent in the alarm transmission process at the start of business is received, and when a subject is selected from the received list, the information of the selected subject is used. An alarm notification system that is sent to the alarm delivery destination determination process for registration .

Images