TWI732633B - Scada web hmi server and scada web hmi system - Google Patents

Abstract

An object of the present invention is to provide a SCADA web HMI server which is capable of limiting the scope of alarm notification by each browser. The web HMI server (10) transmits and receives signals with a plurality of web browsers (21). Executing-browser management process (12) manages the executing-browser-name of the executing-web-browser among the plurality of web browsers (21). The alarm group acquisition process (14) acquires the alarm group name of the alarm group which the alarm signal received from the PLC (2) belongs to. Candidate browser extraction process (16) extracts a plurality of candidate browser names, which are the browser names of said plurality of web browsers related to said alarm group name acquired before, from the alarm group information (17). Alarm-displaying signal transmission process (18) transmits the alarm-displaying signal to said web browser corresponding to the browser name which is consistent with said executing-browser-name among said plurality of candidate browser names.

Description

SCADA network HMI server and SCADA network HMI system

The present invention relates to a SCADA network HMI server and a SCADA network HMI system for implementing a browser-based SCADA HMI.

It is well known that SCADA (Supervisory Control And Data Acquisition) is used as a framework for monitoring and controlling social infrastructure systems. The social infrastructure system is: steel rolling system, power transmission and transformation system, water and sewage treatment system, building management system, road system, etc.

SCADA is a kind of industrial control system, which performs system monitoring and process control performed by computers. In SCADA, rapid response (immediateness) corresponding to the processing performance of the system is required.

SCADA generally consists of the following sub-systems.

(1) HMI (Human Machine Interface)

The HMI system prompts the operator with the data of the target manufacturing process (monitoring target device) so that the operator can monitor and control the processing mechanism. For example, Patent Document 1 discloses a SCADA HMI with an HMI screen operating on a SCADA client. In addition, Patent Document 2 discloses a plant monitoring device, which is constituted by a plurality of monitors provided with a plurality of monitors displaying an HMI screen.

(2) Monitoring and control system

The monitoring and control system collects signal information on the process and sends control commands to the process. It is constituted by PLC (Programable Logic Controller) etc.

(3) Remote Input Output (Remote Input Output: RIO)

The remote input and output device is connected with the sensor set in the manufacturing process, and converts the signal of the sensor into digital data, and transmits the digital data to the monitoring and control system.

(4) Communication infrastructure

The communication infrastructure connects the monitoring and control system with remote input and output devices.

Patent Document 1: Japanese Patent Application Publication No. 2017-27211

Patent Document 2: Japanese Patent Application Laid-Open No. 6-339184

The SCADA client of Patent Document 1 operates with a high-performance computer that can execute monitoring and control logic. In addition, when multiple SCADA clients are installed, a high-performance computer with the number of SCADA clients must be prepared, and monitoring and control logic must be installed individually. In addition, when the SCADA client is configured with multiple monitors, monitoring control logic must be installed on each HMI screen displayed on the monitor. Therefore, we are eagerly looking forward to the cost reduction of SCADA HMI.

In order to reduce the cost of SCADA HMI, the inventors of this case are striving to develop a browser-based HMI server system. By implementing the network application programming of the monitoring control logic on the server, there is no need to install individual monitoring and control logic in the client terminal (network terminal). The client terminal only needs to display the results of the monitoring and control logic processed by the server on the web browser Will suffice. Therefore, it is sufficient for the client terminal to use a computer with a lower specification that enables the web browser to operate. In addition, the system can be monitored and controlled even on portable terminals such as tablets. In this way, a configuration in which a plurality of client terminals are connected to the server can be realized at low cost. In addition, network terminals that do not contain monitoring and control logic are collectively referred to as thin clients.

In addition, the configuration of multiple monitors can also be realized at low cost. The web browser displayed on each monitor only displays the results of the monitoring control logic processed by the server. According to the structure of multiple monitors, one mouse and keyboard can operate the HMI screen displayed on multiple monitors, and improve the efficiency of monitoring and control. According to these configurations, the price of the system can also be suppressed more than the conventional integrated server and client configuration.

By the way, the large-scale machinery system has multiple programs. Each program is managed by different operators. Therefore, when an alarm indicating a process abnormality occurs under a certain procedure, the alarm is notified to an operator who does not manage that procedure. For the operator, there is too much information, which will reduce the operator's operating efficiency. Therefore, it is important to only notify the alarms related to the program managed by the operator.

In the browser-based HMI subsystem as described above, the server does not manage a single monitor. The server manages multiple web browsers that display the monitoring screen of the machine. In the case of selecting an alarm signal and notifying the operator, the server must control the alarm signal in a unit of a web browser.

The present invention is developed to solve the above-mentioned problems. The object of the present invention is to provide a SCADA network HMI server and a SCADA network HMI system that can limit the alarm notification range in units of browsers when communicating with a plurality of network browsers displaying machine monitoring screens.

In order to achieve the above object, the SCADA network HMI server device and the SCADA network HMI system of the present invention are constructed as follows.

The SCADA network HMI system is equipped with: multiple SCADA network HMI servers. Each SCADA network HMI server receives the alarm signal from the programmable logic controller (PLC), and transmits and receives the signal with a plurality of network browsers that display the machine monitoring screen.

The aforementioned SCADA network HMI server has: at least one processor; and a memory for storing programs. The aforementioned program is executed by the aforementioned at least one processor, so that the aforementioned at least one processor executes processing including the following processing.

The running browser management process is to manage the name of the running browser of the running network browser among the aforementioned plural network browsers that communicate with the HMI server of the own SCADA network.

The alarm group acquisition process is to obtain the alarm group name of the alarm group to which the alarm signal received from the PLC belongs.

The candidate browser extraction process is to extract multiple candidate browser names from the alarm group information. The alarm group information associates the alarm group name of the aforementioned alarm group with the browser names of the multiple web browsers belonging to the aforementioned alarm group , The plurality of candidate browser names are the browser names of the aforementioned plurality of web browsers that are associated with the aforementioned obtained alarm group name.

The alarm display signal transmission processing is to transmit the alarm display signal to the aforementioned web browser corresponding to the browser name among the aforementioned plural candidate browser names which is consistent with the aforementioned browser name in execution.

The web browser that receives the alarm display signal displays the content of the alarm display signal on the machine monitoring screen.

According to the present invention, alarms are classified into alarm groups, and the web browser used by the operator is defined in advance which alarm group is to be monitored, so that only necessary alarms can be notified to the web browser. According to the present invention, the range of alarm notification can be limited in units of browsers.

In the previous SCADA HMI, the alarm notification range can only be set roughly on a server basis, but according to the present invention, a browser-based fine operation can be performed, and the operator in charge of each program can only be notified of the required Alert information.

Furthermore, each SCADA network HMI server manages the running browser that communicates with its own server, and only sends an alarm display signal to the running browser among the candidate browsers that are associated with the alarm signal. Therefore, no alert display information will be sent to non-executing web browsers. In this way, unnecessary processing regarding non-executing browsers can be reduced.

The web browser communicates with the server, and the monitoring control logic is a browser-based configuration executed by the server. Therefore, changes in the hardware configuration such as changes in the number of monitors will not affect the system design (alarms). Display or not and/or button operation authority). Therefore, the engineering cost can be reduced, and the freedom of system design can be improved. There is no need to change the setting of the number of monitor connections during maintenance and/or replacement at the customer's site.

By being composed of multiple monitors, the system construction price can be suppressed. By streamlining the client structure, it is possible to integrate functions on the server, replace inexpensive computers, and/or import tablets and other mobile-enabled terminals.

1: HMI

2: PLC

3: Computer network

10, 10a, 10b: network HMI server

100a, 200a: processor

100b, 200b: memory

100c, 200c: network interface

100d, 200d: input interface

100e, 200e: display

11: HMI server application

12: Browser management processing during execution

13, 13a, 13b: running browser information

14: Alarm group acquisition processing

15: Alarm item information

16: Candidate browser extraction processing

17: Alert group information

18: Alarm display signal transmission processing

19: Alarm information

20: HMI terminal

21, 21a, 21b, 21c, 21d: web browser

61a: First pass processing

61b: second pass processing

62a: The first confirmation candidate browser extraction process

62b: Second confirmation candidate browser extraction process

63: Alert confirmation group information

64a: The first confirmation completes the signal transmission processing

64b: The second confirmation completes the signal transmission processing

65: Alarm confirmation data

ALM101: Alarm signal

FIG. 1 is a diagram for explaining the system configuration of SCADA in Embodiment 1 of the present invention.

FIG. 2 is a block diagram for explaining the functions of the web browser and HMI server application of the first embodiment of the present invention.

FIG. 3 is a diagram showing an example of alarm item information of Embodiment 1 of the present invention.

FIG. 4 is a diagram showing an example of alarm group information of Embodiment 1 of the present invention.

FIG. 5 is a diagram for explaining the signal processing of the SCADA network HMI server of Embodiment 1 of the present invention.

Fig. 6 is a block diagram for explaining the functions of the web browser and the HMI web application of the second embodiment of the present invention.

FIG. 7 is a diagram showing an example of alarm confirmation group information in the second embodiment of the present invention.

FIG. 8 is a diagram for explaining the signal processing of the SCADA network HMI server of Embodiment 2 of the present invention.

Figure 9 is a block diagram showing an example of the hardware configuration of the HMI terminal and the network HMI server.

Hereinafter, the embodiments of the present invention will be described in detail with reference to the drawings. However, when referring to the number, quantity, amount, range, etc. of each element in the implementation types shown below, except for cases where the number is clearly stated or clearly stated in principle, the reference The number of and is not intended to limit the present inventor. In addition, the structure and the like described in the embodiments shown below are not necessarily essential to the present invention, except in cases where the structure is clearly indicated or is clearly indicated in principle. In addition, the same reference numerals are given to elements common in the respective drawings, and repeated descriptions are omitted.

Implementation type 1.

<Overall composition>

Figure 1 is a diagram used to illustrate the SCADA system structure. The SCADA system has the following as subsystems: Human Machine Interface (HMI) 1, Programmable Logic Controller (PLC) as a monitoring and control system 2, communication infrastructure, RIO. The SCADA system is connected to the monitoring target device via PLC 2 or RIO.

The description of the PLC 2 (monitoring and control system), the communication infrastructure, and the RIO is omitted because it has been described in the prior art. The monitoring target device is a sensor, an actuator, etc. that constitute a monitoring control target machine tool.

HMI 1 (SCADA network HMI system) is provided with: a plurality of SCADA network HMI servers 10 (hereinafter referred to as: network HMI server 10), and HMI terminals 20.

A plurality of network HMI servers 10 are connected to a plurality of PLCs 2 via a computer network 3. When there is no need to distinguish the situation of each network HMI server, it is only recorded as the network HMI server 10. The network HMI server 10 is connected to the HMI terminal 20 via a computer network. The network HMI server 10 can also be connected to a plurality of HMI terminals 20. When there is no need to distinguish the situation of each HMI terminal, it is only described as the HMI terminal 20.

The HMI terminal 20 is a simplified client that does not include monitoring and control logic, and can execute at least one web browser 21. Specifically, the HMI terminal 20 is equipped with at least one monitor (display 200e in FIG. 9). The HMI terminal 20 is connected to a monitor to display a web browser 21 in a full-screen manner. The web browser 21 displays the machine monitoring screen (HMI screen). When the HMI terminal 20 has a plurality of monitors, the HMI terminal 20 displays the web browser 21 in a full-screen manner on each monitor. That is, the HMI terminal 20 executes a plurality of web browsers 21.

The network HMI server 10 includes the functions of the HMI terminal 20 and can execute a network browser 21. Specifically, the network HMI server 10 is equipped with at least one monitor (display 100e in FIG. 9). The network HMI server 10 is a monitor that displays a network browser 21 in a full-screen manner. The web browser 21 displays the machine monitoring screen (HMI screen). When the network HMI server 10 has a plurality of monitors, the network HMI server 10 displays the network browser 21 in a full-screen manner on each monitor. That is, the network HMI server 10 executes a plurality of network browsers 21.

The network HMI server 10 executes the HMI server application program 11. The HMI server application 11 has a network server function for communicating with the HMI terminal 20 and an I/O server function for communicating with the PLC 2 (application server function). The HMI terminal 20 executes a web browser 21. The HMI 1 belonging to the execution environment operates as a script (for example, JavaScript (registered trademark)) that coordinates actions on the web browser 21, and a web application of the HMI server application 11 that contains monitoring and control logic. .

In response to the signal data received from the PLC 2, the network HMI server 10 transmits a signal for changing the state of the parts arranged on the machine monitoring screen to the network browser 21. The network HMI server 10 receives control commands from the network browser 21 and transmits them to the PLC 2.

<HMI Server Application>

2 to 4, the characteristic processing of the HMI server application 11 executed by the network HMI server 10 of implementation type 1 will be described.

As shown in FIG. 9 described later, the network HMI server 10 includes at least one processor 100a and a memory 100b for storing programs. The program is executed by the processor 100a, and the processor 100a executes the processing including the following processes.

The HMI server application program 11 executed by the network HMI server 10 generates a communication object for communicating with the network browser 21 and a communication object for communicating with the PLC 2 when the program starts. In the example of FIG. 2, the network HMI server 10 transmits and receives signals with the network browser 21a and the network browser 21b. In addition, the network HMI server 10 receives an alarm signal from the PLC 2. When it is not necessary to distinguish the situation of each web browser, it is only recorded as web browser 21.

The HMI server application 11 transmits the contents corresponding to the machine monitoring screen (HMI screen) requested from the web browser 21 to the web browser 21. The web browser 21 receives the content and displays the HMI screen. The content includes: SVG data, screen information.

The web browsers 21a and 21b display machine monitoring screens. In the example of FIG. 2, the web browsers 21a and 21b display the screen G1. The screen G1 is equipped with alarm display parts that display the alarm status, and a confirmation button (button). The machine monitoring screen displayed by each web browser 21 can be freely changed by an operator's operation.

In addition, the HMI server application program 11 reads: alarm item information 15 and alarm group information 17 when the program starts.

The alarm item information 15 is information that associates at least the alarm signal name of the alarm signal with the alarm group name of the alarm group to which the alarm signal belongs. The alarm signals that are likely to occur are classified into one of the alarm groups. An example of the alarm item information 15 is shown in FIG. 3. In the example of FIG. 3, the alarm item information 15 is information that associates the name of the alarm item, the name of the alarm group, the alarm level, and the comment.

The alarm group information 17 is information predetermined in order to limit the alarm notification range. Specifically, the alarm group information 17 is information that associates the alarm group name of the alarm group with the browser names of a plurality of web browsers belonging to the alarm group. Fig. 4 shows an example of alarm group information 17.

Here, the browser name included in the alarm group information 17 is explained. The name of each browser is a unique name. In order to identify each web browser in HMI 1, each web browser is given a browser name according to the following rules.

Browser name = machine name + "_" + serial number of the browser

In addition, a web browser is displayed on a monitor (display) in full screen, so the monitor and the web browser correspond one-to-one. Therefore, the browser name is also called the monitor name. When the machine name of the network HMI server 10 is included in the browser name, the network browser is executed on the network HMI server 10. When the machine name of the HMI terminal 20 is included in the browser name, the web browser is a browser executed on the simplified client (HMI terminal 20). The network HMI server 10 and the HMI terminal 20 have unique machine names.

The running browser management processing 12 manages the running browser name of the running web browser among the plural web browsers 21 communicating with the own network HMI server 10. When the running browser management process 12 is running the web browser 21a and the web browser 21b, the browser name of the web browser 21a and the web browser 21b are memorized as the running Browser information 13. The running browser information 13 is updated when, for example, the web browser 21 is started or when the web browser 21 ends.

The alarm group obtaining process 14 obtains the alarm group name of the alarm group to which the alarm signal received from the PLC 2 belongs from the alarm item information 15.

The candidate browser extraction process 16 is to extract a plurality of candidate browser names from the alarm group information 17, and the plurality of candidate browser names are a plurality of web browsers associated with the alarm group name obtained by the alarm group obtaining process 14 The name of the browser. In the example in Figure 4, if the alarm group name In the case of FM, the selected multiple candidate browser names are: FMHMI_1_1, FMHMI_1_2, FMHMI_2_1, FMHMI_3_1, FMHMI_3_2.

The alarm display signal transmission processing 18 transmits the alarm display signal to the web browser 21 corresponding to the browser name that is consistent with the browser name in execution among the plurality of candidate browser names. For one example, the plural candidate browser names are: FMHMI_1_1, FMHMI_1_2, FMHMI_2_1, FMHMI_3_1, FMHMI_3_2. The browser names during execution are: FMHMI_1_1, FMHMI_1_2, FMHMI_2_1. At this time, the alarm display information is sent to FMHMI_1_1, FMHMI_1_2, FMHMI_2_1.

The web browser 21 that receives the alarm display signal displays the content of the alarm display signal in the alarm display part on the machine monitoring screen.

In addition, regardless of whether the web browser 21 is executed by the web HMI server 10 or the web browser 21 is executed by the HMI terminal 20, the processing content is the same.

In addition, when the HMI server application 11 detects that the web browser 21 is activated, it must transmit the alarm data 19 required by the web browser 21 to the web browser 21.

First, the HMI server application 11 can know the alarm group to which the web browser 21 belongs from the web browser number of the web browser 21. Next, the HMI server application 11 obtains the current status (occurrence/reset) of all alarms of the alarm group. The HMI server application 11 transmits the information to the web browser 21.

<Signal processing flow>

Referring to the example shown in FIG. 5, the signal processing flow of Embodiment 1 will be described.

Fig. 5 is a diagram showing an example of HMI 1 (SCADA network HMI system) deployed in the hot rolling production line. The hot rolling production line is a kind of steel rolling system. The hot rolling production line is equipped with: rough rolling (RM: Roughering Mills section, finishing mills (FM: Finishing Mills) section, coil (DC: Down Coiler) section. Each section is equipped with an operation room (PULPIT).

The hot rolling production line shown in Fig. 5 is equipped with: RM operating room (RM: Roughing Mills), FM operating room (FM: Finishing Mills), and DC operating room (DC: Down Coiler). In addition, the hot rolling and rolling production line is equipped with: SV room (SV: Supervisory, monitoring).

Each of the RM operation room, FM operation room, DC operation room, and SV room is equipped with at least one network HMI server 10. RMHMI is a network HMI server 10 installed in the RM operating room. FMHMI 1 and FMHMI 3 are network HMI servers 10 installed in the FM operation room. FMHMI 2 is an HMI terminal 20 installed in the FM operation room. DCHMI is a network HMI server 10 installed in the DC operation room. SVHMI is a network HMI server 10 installed in the SV room.

RMHMI_1 and RMHMI_2 are the browser names of the web browser 21 executed by RMHMI. FMHMI_1_1 and FMHMI_1_2 are the browser names of the web browser 21 executed by FMHMI 1. FMHMI_2_1 is the browser name of the web browser 21 executed by FMHMI 2. FMHMI_3_1 and FMHMI_3_2 are the browser names of the web browser 21 executed by FMHMI 3. DCHMI_1 and DCHMI_2 are the browser names of the web browser 21 executed by DCHMI. SVHMI_1 and SVHMI_2 are the browser names of the web browser 21 executed by SVHMI.

Each network HMI server 10 executes the same processing described in FIG. 2. Therefore, the alarm item information 15 and the alarm group information 17 of each network HMI server 10 are the same. In addition, the browser management process 12 is the same during the execution of each network HMI server 10, but the network browser 21 that communicates with the own network HMI server 10 is different, so the browser information 13 is different during execution. The name of the running browser included is different in each network HMI server 10.

Specifically explain. All the web browsers shown in Figure 5 are running. The running browser information of RMHMI 13 includes: RMHMI_1 and RMHMI_2. The running browser information 13 of FMHMI 1 includes: FMHMI_1_1, FMHMI_1_2, FMHMI_2_1. The running browser information of FMHMI 3 includes: FMHMI_3_1 and FMHMI_3_2. The running browser information of DCHMI 13 includes: DCHMI_1 and DCHMI_2. The running browser information of SVHMI 13 includes: SVHMI_1 and SVHMI_2.

FIG. 5 is a diagram for explaining the processing of each network HMI server 10 that receives an alarm signal from the PLC 2.

In step S1, an alarm signal (ALM101) is transmitted from the PLC 2, and each network HMI server 10 receives the alarm signal.

In steps S2a to S2e, each network HMI server 10 executes the alarm group acquisition process 14. Each alarm group acquisition process 14 is obtained from the alarm item information 15 shown in FIG. 3: the alarm group name (FM) of the alarm group to which the alarm signal (ALM101) received from the PLC 2 belongs.

In steps S3a to S3e, each network HMI server 10 executes the candidate browser extraction process 16. Each candidate browser extraction process 16 extracts a plurality of candidate browser names (FMHMI_1_1, FMHMI_1_2, FMHMI_2_1, FMHMI_3_1, FMHMI_3_2) from the alarm group information 17 shown in FIG. FM) The browser name of the multiple web browsers associated with it.

In steps S4a to S4e, each network HMI server 10 extracts: among a plurality of candidate browser names, the name of the browser that is consistent with the name of the running browser. Explain each step.

In step S4a, the names of the browsers in the execution of RMHMI are: RMHMI_1, RMHMI_2, and there is no browser name consistent with the candidate browser names extracted in step S3a.

In step S4b, the names of the browsers in the execution of FMHMI 1 are: FMHMI_1_1, FMHMI_1_2, FMHMI_2_1, and the names of the browsers consistent with the candidate browser names extracted in step S3b are: FMHMI_1_1, FMHMI_1_2, FMHMI_2_1.

In step S4c, the names of the browsers during the execution of FMHMI 3 are: FMHMI_3_1, FMHMI_3_2, and the names of the browsers consistent with the candidate browser names extracted in step S3c are: FMHMI_3_1, FMHMI_3_2.

In step S4d, the browser names in the execution of DCHMI are: DCHMI_1, DCHMI_2, and there is no browser name consistent with the candidate browser names extracted in step S3d.

In step S4e, the browser names in the execution of SVHMI are: SVHMI_1, SVHMI_2, and there is no browser name consistent with the candidate browser names extracted in step S3e.

In this way, for FMHMI 1 and FMHMI 3, among the plural candidate browser names, there are browser names that are consistent with the names of the browsers in execution.

Then, FMHMI 1 executes the processing of step S5b. FMHMI 3 executes the processing of step S5c.

In step S5b, the alarm display signal transmission processing 18 of FMHMI 1 transmits the alarm display signal to the web browser 21 corresponding to each browser name (FMHMI_1_1, FMHMI_1_2, FMHMI_2_1).

In step S5c, the alarm display signal transmission processing 18 of FMHMI 3 transmits the alarm display signal to the web browser 21 corresponding to each browser name (FMHMI_3_1, FMHMI_3_2).

The web browser 21 that receives the alarm display signal displays the content of the alarm display signal on the alarm display part of the machine monitoring screen.

On the other hand, with regard to RMHMI, DCHMI, and SVHMI, there is no browser name that matches the name of the running browser among the plural candidate browser names. Therefore, the RMHMI, DCHMI, and SVHMI systems do not transmit an alarm display signal and terminate the processing.

As explained above, the network HMI server 10 of implementation type 1 categorizes alarms into alarm groups, and defines in advance which alarm group is set in the web browser used by the operator, so that only Necessary alarm notifications to the web browser. The network HMI server 10 can limit the range of alarm notifications by browser as a unit, and can notify only the required alarm information to the operators in charge of each section. Therefore, the operator can efficiently monitor the alarm.

In addition, the processing on each network HMI server 10 is the same, so the installed programs are the same. In addition, it will not affect the increase or decrease in the number of web browsers communicating with the server.

Incidentally, in the system of the above-mentioned implementation type 1, the situation where all the web browsers 21 are running is explained. However, there are also some web browsers 21 that are not running. In this case, the browser name of the non-running web browser will not be included in the running browser information13. Therefore, no warning display signal will be sent to a non-executing web browser. In this way, unnecessary processing regarding non-executing browsers can be reduced. In addition, this point is also the same in the following implementation types.

Implementation type 2.

Implementation type 2 is about the commonality of alarm confirmation operations. Referring to the examples shown in FIGS. 6 to 8, the second embodiment of the present invention will be described. The system of this embodiment can be realized by causing a plurality of network HMI servers 10 to execute the processing of FIG. 6 described later in the configuration of FIG. 1.

In the SCADA network HMI system of the above-mentioned implementation type 1, the range of alarm notification can be limited, so the operator can efficiently monitor the alarms that are only related to the area in charge.

By the way, the operator who has confirmed the occurrence of the alarm must perform the confirmation operation. Through the confirmation operation, the display status of the alarm changes from UNACK (before confirmation) to ACK (after confirmation). When there are multiple web browsers in the area where the operator is responsible, the operator has to perform confirmation operations on each web browser inefficiently.

Therefore, in the second embodiment, the commonality of the alarm confirmation operation is sought. When the alarm confirmation operation is performed on one web browser, the confirmation operation is automatically reflected on the other specified web browsers.

<HMI Server Application>

6 to 8, the characteristic processing of the HMI server application 11 executed by each network HMI server 10 of the implementation type 2 will be described.

As shown in FIG. 6, the plurality of network HMI servers 10 include a first network HMI server 10a and a second network HMI server 10b. The first network HMI server 10a and the second network HMI server 10b have the same structure and function as the network HMI server 10 described in FIG. 2, so the description of the common structure and function is omitted. In addition, the SCADA network HMI system can also have more than three network HMI servers 10. When there is no need to distinguish between the network HMI servers, it is only recorded as the network HMI server 10.

The first network HMI server 10a is in addition to the addition of: first delivery processing 61a, first confirmation candidate browser extraction processing 62a, alarm confirmation group information 63, first confirmation completion signal transmission processing 64a, and alarm confirmation data 65 Others are the same as the network HMI server 10 in FIG. 2.

The second network HMI server 10b is in addition to the addition of: second transfer processing 61b, second confirmation candidate browser extraction processing 62b, alarm confirmation group information 63, second confirmation completion signal transmission processing 64b, and alarm confirmation data 65 Others are the same as the network HMI server 10 in FIG. 2.

The first network HMI server 10a transmits and receives signals with the network browser 21a and the network browser 21b. Similarly, the web HMI server 10b transmits and receives signals with the web browser 21c and the web browser 21d. The network HMI server 10a and the network HMI server 10b transmit and receive signals via the computer network 3. When there is no need to distinguish between web browsers, it is only recorded as web browser 21.

At the beginning of each HMI server application program 11, in addition to the alarm item information 15 and the alarm group information 17 described in the implementation pattern 1, it also reads the alarm confirmation group information 63.

The alarm confirmation group information 63 is information of a plurality of web browsers 21 that have previously determined the common alarm confirmation operation. Specifically, the alarm confirmation group information 63 is information that associates the name of the alarm confirmation group of the alarm confirmation group with the browser names of a plurality of web browsers belonging to the alarm confirmation group. FIG. 7 shows an example of the alarm confirmation group information 63.

The running browser management processing 12 performed by the first network HMI server 10a and the second network HMI server 10b are the same, but the network browser 21 communicated by each server is different, so browse during execution The name of the running browser contained in the browser information is different. That is, the running browser information 13a of the first network HMI server 10a includes the browser name of the network browser 21a and the browser name of the network browser 21b. The running browser information 13b of the second network HMI server 10b includes: the browser name of the network browser 21c and the browser name of the network browser 21d.

The machine monitoring screens displayed in the web browsers 21a to 21d of FIG. 6 on the full screen are equipped with alarm display parts and confirmation buttons in the same way as the web browser 21 of FIG. 2. When the confirmation button is pressed, an alarm response signal is transmitted from the web browser 21. The HMI server application 11 of the network HMI server 10 communicating with the network browser 21 receives the alarm response signal.

When the first transmission processing 61a receives an alarm response signal in response to the alarm display signal from the web browser (21a or 21b) communicating with the first network HMI server 10a, it transmits the alarm response signal to The second network HMI server 10b.

When the second transmission process 61b receives the alarm response signal in response to the alarm display signal from the web browser (21c or 21d) communicating with the second network HMI server 10b, it transmits the alarm response signal To the first network HMI server 10a.

The first transfer process 61a and the second transfer process 61b are processes implemented in the same program. That is, when the transmission processing of the network HMI server 10 receives the alarm response signal in response to the alarm display signal from the web browser communicating with its own server, it transmits the alarm response signal to other Network HMI server.

When the first confirmation candidate browser extraction process 62a receives the alarm response signal from the web browser (21a or 21b) communicating with the first network HMI server 10a or the second network HMI server 10b, it will The alarm confirmation group information 63 extracts the browser name other than the transmission source browser name of the alarm confirmation group belonging to the transmission source browser name of the web browser that transmitted the alarm response signal. Here, "a browser name other than the name of the source browser belonging to the alert confirmation group" is referred to as the "confirmation candidate browser name".

For one example, the first network HMI server 10a is FMHMI 1, and the second network HMI server 10b is FMHMI 3. The source of the web browser that sends the alarm response signal The browser name is FMHMI_2_1. At this time, the alert confirmation group to which the browser name of the transmission source belongs is GROUP2. At this time, confirm that the candidate browser names are: FMHMI_1_1, FMHMI_1_2, FMHMI_3_1, FMHMI_3_2.

When the second confirmation candidate browser extraction process 62b receives the alarm response signal from the web browser (21c or 21d) communicating with the second network HMI server 10b or the first network HMI server 10a, it will receive the alarm response signal from The alarm confirmation group information 63 extracts the browser name other than the transmission source browser name of the alarm confirmation group belonging to the transmission source browser name of the web browser that transmitted the alarm response signal.

For one example, the first network HMI server 10a is FMHMI 1, and the second network HMI server 10b is FMHMI 3. The source browser name of the web browser that sends the alarm response signal is FMHMI_2_1. At this time, the alert confirmation group to which the name of the source browser belongs is: GROUP2. At this time, confirm that the candidate browser names are: FMHMI_1_1, FMHMI_1_2, FMHMI_3_1, FMHMI_3_2.

The first confirmation candidate browser extraction process 62a and the second confirmation candidate browser extraction process 62b are processes implemented by the same program. That is, the processing of extracting confirmation candidate browsers of the network HMI server 10 is that when the alarm response signal is received, it extracts the transmission source belonging to the web browser that sent the alarm response signal from the alarm confirmation group information 63 The name of the browser other than the browser name of the transmission source of the alert confirmation group to which the browser name belongs.

The first confirmation completion signal transmission processing 64a is to transmit the alarm confirmation completion signal to: among the confirmation candidate browser names, the network corresponding to the browser name that is consistent with the running browser name of the first network HMI server 10a Road browser.

For one example, confirm that the candidate browser names are: FMHMI_1_1, FMHMI_1_2, FMHMI_3_1, FMHMI_3_2. The running browser names of the first network HMI server 10a (FMHMI 1) are: FMHMI_1_1, FMHMI_1_2, FMHMI_2_1. At this time, the alarm confirmation completion signal will be sent to: FMHMI_1_1, FMHMI_1_2.

The second confirmation completion signal transmission processing 64b is to transmit the alarm confirmation completion signal to: among the confirmation candidate browser names, the network corresponding to the browser name that is consistent with the running browser name of the second network HMI server 10b Road browser.

For one example, confirm that the candidate browser names are: FMHMI_1_1, FMHMI_1_2, FMHMI_3_1, FMHMI_3_2. The running browser names of the second network HMI server 10b (FMHMI 3) are: FMHMI_3_1, FMHMI_3_2. At this time, the alarm confirmation completion signal will be sent to: FMHMI_3_1, FMHMI_3_2.

The first confirmation completion signal transmission process 64a and the second confirmation completion signal transmission process 64b are processes realized by the same program. That is, the confirmation completion signal transmission process of the network HMI server 10 is to transmit the alarm confirmation completion signal to: among the names of the confirmation candidate browsers, the names of the running browsers of the own network HMI server 10 are consistent The web browser corresponding to the browser name.

The web browser 21 that has received the alarm confirmation completion signal changes the alarm display displayed on its machine monitoring screen to the confirmation completion state.

In addition, regardless of whether it is executed by the network HMI server 10 or the HMI terminal 20 is executed by the network browser 21, the processing content is the same.

In addition, when the HMI server application 11 detects that the web browser 21 is activated, it must transmit the alarm data 19 and the alarm confirmation data 65 required by the web browser 21 to the web browser 21.

First, the HMI server application 11 can know the alarm group and the alarm confirmation group to which the web browser 21 belongs from the web browser number of the web browser 21. Next, the HMI server application 11 obtains the current status (occurrence/reset) of all alarms of the alarm group. In addition, the HMI server application 11 obtains the confirmation status (unconfirmed/confirmed) of each alarm in the alarm confirmation group. The HMI server application 11 sends the information to the web browser 21.

<Signal processing flow>

Referring to the example shown in FIG. 8, the signal processing flow of Embodiment Mode 2 will be described.

FIG. 8 is a diagram showing an example of HMI 1 (SCADA network HMI system) deployed in the hot rolling and rolling production line. The system configuration shown in FIG. 8 is the same as that in FIG. 5, and repeated descriptions are omitted.

In the signal processing of Fig. 5, the alarm signal ALM101 is transmitted to each network HMI server 10, and the alarm is displayed in the alarms of FMHMI_1_1, FMHMI_1_2, FMHMI_2_1, FMHMI_3_1, FMHMI_3_2 as the browser in execution, which belongs to the alarm group FM Show parts. The signal processing illustrated in FIG. 8 continues the signal processing illustrated in FIG. 5 described in the first embodiment. With reference to Figure 8, description: In the web browser FMHMI_2_1, the operator responds to the ALM101 to press the confirmation button, and then reflects the processing flow of the confirmation operation in the designated browser.

FMHMI 1 corresponds to the first network HMI server 10a. The RMHMI, FMHMI 3, DCHMI, and SVHMI systems correspond to the second network HMI server 10b.

In step S10, when the operator presses the confirmation button related to ALM101 of the web browser FMHMI_2_1, the alarm response signal will be transmitted to FMHMI 1.

In step S11, when the transmission process of FMHMI 1 (first transmission process 61a) receives an alarm response signal from FMHMI_2_1, the alarm response signal will be transmitted to other network HMI servers (RMHMI, FMHMI 3, DCHMI, SVHMI).

In steps S12a to S12e, each network HMI server 10 executes a process of extracting a confirmed candidate browser (62a, 62b).

In step S12b, the first confirmation candidate browser extraction process 62a of FMHMI 1 is that when the alarm response signal is received from FMHMI_2_1, it extracts from the alarm confirmation group information 63 shown in FIG. 7: it belongs to the transmission of the alarm response signal The browser name (FMHMI_1_1, FMHMI_1_2, FMHMI_3_1, FMHMI_3_2) other than the transmission source browser name (FMHMI_2_1) of the alarm confirmation group (GROUP2) to which the transmission source browser name (FMHMI_2_1) belongs to. The "browser name other than the name of the source browser belonging to the alert confirmation group" is called "the name of the candidate browser for confirmation".

In steps S12a, S12c, S12d, and S12e, each network HMI server 10 (RMHMI, FMHMI 3, DCHMI, SVHMI) receives the alarm response signal from the first network HMI server FMHMI 1.

The second confirmation candidate browser extraction process 62b extracts the confirmation candidate browser names (FMHMI_1_1, FMHMI_1_2, FMHMI_3_1, FMHMI_3_2) when the alarm response signal is received, similarly to the first confirmation candidate browser extraction process 62a.

In steps S13a to S13e, each network HMI server 10 extracts: a browser name that is consistent with the running browser name among a plurality of confirmed candidate browser names.

In step S13a, the names of the browsers during the execution of RMHMI are: RMHMI_1 and RMHMI_2, and there is no browser name consistent with the names of the confirmed candidate browsers extracted in step S12a.

In step S13b, the names of the browsers during the execution of FMHMI 1 are: FMHMI_1_1, FMHMI_1_2, and FMHMI_2_1, and the names of the browsers consistent with the names of the confirmed candidate browsers extracted in step S12b are: FMHMI_1_1 and FMHMI_1_2.

In step S13c, the names of the browsers during the execution of FMHMI 3 are: FMHMI_3_1 and FMHMI_3_2, and the names of the browsers that are consistent with the names of the confirmed candidate browsers extracted in step S12c are: FMHMI_3_1 and FMHMI_3_2.

In step S13d, the names of the browsers during the execution of DCHMI are: DCHMI_1 and DCHMI_2, and there is no browser name consistent with the names of the confirmed candidate browsers extracted in step S12d.

In step S13e, the browser names during the execution of SVHMI are: SVHMI_1 and SVHMI_2, and there is no browser name consistent with the names of the confirmed candidate browsers extracted in step S12e.

In this way, for FMHMI 1 and FMHMI 3, among the plural confirmed candidate browser names, there are browser names that are consistent with the names of the browsers in execution.

Therefore, FMHMI 1 executes the processing of step S14b, and FMHMI 3 executes the processing of step S14c. On the other hand, with regard to RMHMI, DCHMI, and SVHMI, there is no browser name that matches the name of the running browser among the plural confirmed candidate browser names. Therefore, RMHMI, DCHMI, and SVHMI finish processing.

In step S14b, the first confirmation completion signal transmission processing 64a of FMHMI 1 transmits the alarm confirmation completion signal to the web browser 21 corresponding to each browser name (FMHMI_1_1, FMHMI_1_2).

In step S14c, the second confirmation completion signal transmission processing 64b of FMHMI 3 transmits the alarm confirmation completion signal to the web browser 21 corresponding to each browser name (FMHMI_3_1, FMHMI_3_2).

The web browser 21 that has received the alarm confirmation completion signal changes the alarm display displayed on its machine monitoring screen to the confirmation completion state.

As explained above, the implementation of the SCADA network HMI system (HMI 1) of type 2 when a web browser is used for alarm confirmation operations, it belongs to other web browsers in the same alarm confirmation group as the web browser The device can also automatically reflect the confirmation operation. In this way, when there are multiple web browsers in the section that the operator is responsible for, the operator does not need to confirm the operation of each web browser, and the operating efficiency of the operator can be improved.

In addition, the processing on each network HMI server 10 is the same, so the installed programs are the same. In addition, it will not affect the increase or decrease in the number of web browsers communicating with the server.

Incidentally, in the system of the above-mentioned implementation type 2, the description is made for the situation where all the web browsers 21 are in execution. However, there are also some web browsers 21 that are not running. In this case, the browser name of the non-running web browser will not be included in the running browser information 13. Therefore, the alarm confirmation completion signal will not be sent to the non-executing web browser. In this way, unnecessary processing regarding non-executing browsers is reduced. In addition, this point is also the same in the following implementation types.

<Example of hardware configuration>

FIG. 9 is a block diagram showing an example of the hardware configuration of the network HMI server 10 and the HMI terminal 20.

The above-mentioned processing of the network HMI server 10 is realized by a processing circuit. The processing circuit is formed by connecting a processor 100a, a memory 100b, a network interface 100c, an input interface 100d, and at least one display 100e. The processor 100a executes various programs stored in the memory 100b, thereby realizing various functions of the network HMI server 10. The network interface 100c is a device that is connected to the PLC 2 and the HMI terminal 20 via a computer network, and can transmit and receive PLC signals and control commands. The input interface 100d is an input device such as a keyboard, a mouse, and a touch panel. A plurality of displays 100e may be installed.

Each processing of the HMI terminal 20 described above is realized by a processing circuit. The processing circuit is formed by connecting a processor 200a, a memory 200b, a network interface 200c, an input interface 200d, and at least one display 200e. The processor 200a executes various programs stored in the memory 200b, thereby realizing various functions of the HMI terminal 20. The network interface 200c is a device that is connected to the network HMI server 10 and can transmit and receive PLC signals and control commands. The input interface 200d is an input device such as a keyboard, a mouse, and a touch panel. The display 200e can also be provided with a plurality of units. In addition, the HMI terminal 20 may be a portable terminal such as a tablet.

The embodiments of the present invention have been described above, but the present invention is not limited to the above embodiments, and various modifications can be made and implemented without departing from the spirit of the present invention.

10: Network HMI server

11: HMI server application

12: Browser management processing during execution

13: Running browser information

14: Alarm group acquisition processing

15: Alarm item information

16: Candidate browser extraction processing

17: Alert group information

18: Alarm display signal transmission processing

19: Alarm information

21a, 21b: Web browser

Claims (6)

A SCADA network HMI server that receives alarm signals from a programmable logic controller (PLC), and transmits and receives signals with a plurality of network browsers that display machine monitoring screens. In the aforementioned SCADA network HMI server It is provided with: at least one processor; and a memory for a memory program; wherein the aforementioned program is executed by the aforementioned at least one processor, so that the aforementioned at least one processor executes the following processes: browser management processing during execution, management Among the aforementioned plural web browsers, the name of the running browser of the running web browser; the alarm group acquisition process is to obtain the alarm group name of the alarm group to which the aforementioned alarm signal received from the aforementioned PLC belongs; candidate browsers are extracted The processing is to extract a plurality of candidate browser names from the alarm group information. The aforementioned alarm group information associates the alarm group name of the aforementioned alarm group with the browser names of a plurality of web browsers belonging to the aforementioned alarm group. The candidate browser name is the browser name of the plurality of web browsers associated with the obtained alarm group name; and the alarm display signal transmission process is to send the alarm display signal to the plurality of candidate browser names. The aforementioned web browser corresponding to the browser name with the same browser name during the aforementioned execution. A SCADA network HMI system, which is equipped with: receiving alarm signals from a programmable logic controller (PLC), and interacting with multiple network browsers that display machine monitoring screens A plurality of SCADA network HMI servers for signal transmission and reception, in the aforementioned SCADA network HMI system: the aforementioned plurality of SCADA network HMI servers each have: at least one processor; and a memory for storing programs; wherein, the aforementioned The program is executed by the aforementioned at least one processor, so that the aforementioned at least one processor executes the following processes: the browser management process during execution, which manages the aforementioned plural networks that communicate with the HMI server of its own SCADA network In the browser, the name of the running browser of the running web browser; the alarm group acquisition process, to obtain the alarm group name of the alarm group to which the alarm signal received from the aforementioned PLC belongs; the candidate browser extraction process is from the alarm group The information extracts a plurality of candidate browser names. The aforementioned alarm group information associates the alarm group name of the aforementioned alarm group with the browser names of a plurality of web browsers belonging to the aforementioned alarm group, and the aforementioned plural candidate browser names are related to The browser name of the plurality of web browsers to which the obtained alarm group name is associated; and the alarm display signal transmission process is to send the alarm display signal to the plurality of candidate browser names and the name of the running browser The aforementioned web browser corresponding to the same browser name. The SCADA network HMI system according to claim 2, wherein the plurality of SCADA network HMI servers include: a first network HMI server, and a second network HMI server; the aforementioned first network HMI server The aforementioned program of the server causes the aforementioned at least one processor to execute processing including the following processing: the first transfer processing is when the aforementioned alarm is received from the aforementioned web browser communicating with the aforementioned first network HMI server When displaying the alarm response signal in response to the signal, the aforementioned alarm response signal is transmitted to the aforementioned second network HMI server; the first confirmation candidate browser extraction process is from the communication with the aforementioned first network HMI server When the aforementioned web browser or the aforementioned second web HMI server receives the aforementioned alarm response signal, extract the alarm confirmation from the alarm confirmation group information that belongs to the source browser name of the aforementioned web browser that sent the aforementioned alarm response signal The name of the browser other than the name of the aforementioned source browser of the group, the aforementioned alarm confirmation group information associates the name of the alarm confirmation group of the alarm confirmation group with the browser names of a plurality of web browsers belonging to the aforementioned alarm confirmation group; And the first confirmation completion signal transmission process is to transmit the alarm confirmation completion signal to: among the browser names other than the aforementioned transmission source browser name belonging to the aforementioned alarm confirmation group and the aforementioned running browser of the aforementioned first network HMI server The web browser corresponding to the browser name with the same browser name; and the aforementioned program of the aforementioned second network HMI server causes the aforementioned at least one processor to execute processing including the following processing: The second transmission process is to transmit the alarm response signal to the second network when the alarm response signal in response to the alarm display signal is received from the web browser that communicates with the second network HMI server. A network HMI server; the second confirmation candidate browser extraction process is based on receiving the aforementioned alarm response from the aforementioned web browser or the aforementioned first network HMI server communicating with the aforementioned second network HMI server When the signal is sent, extract from the aforementioned alarm confirmation group information that belongs to the source browser name of the aforementioned web browser that sent the aforementioned alarm response signal and a browser name other than the aforementioned source browser name of the alarm confirmation group to which the aforementioned source browser name belongs; and the second confirmation The signal transmission process is completed, and the alarm confirmation completion signal is transmitted to: among the browser names other than the transmission source browser name belonging to the alarm confirmation group, the browser whose name is the same as the browser name in the execution of the second network HMI server The web browser corresponding to the browser name. The SCADA network HMI system of claim 2, wherein the web browser that receives the alarm display signal displays the content of the alarm display signal on the machine monitoring screen. The SCADA network HMI system according to claim 3, wherein the web browser that receives the alarm confirmation completion signal changes the alarm display displayed on the machine monitoring screen to the confirmation completion state. The SCADA network HMI system described in any one of Claims 2 to 5 is provided with: a Human Machine Interface (HMI) terminal, which is connected to any one of the aforementioned network HMI servers Computer network connection, and running the aforementioned web browser.

Images