SCADA webpage HMI system

Abstract

A memory of the HMI server device stores image data of an HMI screen, screen operation right information, and component operation right information. The screen operation right information specifies whether or not an HMI screen can be operated for each HMI screen displayed on the web browser according to the operation location. The component operation right information specifies, for each HMI screen, whether or not the operation of the specific operation component on the HMI screen is possible in accordance with the operator's duty. A processor of the HMI server device executes a web server capable of transmitting image data, screen operation right information, and component operation right information to a web browser. A memory of the HMI client device stores image data, screen operation right information, and component operation right information from the web server. A processor of the HMI client device applies operation permission specified in the screen operation right information to a plurality of operation components on the HMI screen, preferentially applies operation permission specified in the component operation right information according to the job to a specific operation component, and draws the HMI screen on the web browser.

Description

Technical Field

[0001] The present disclosure relates to a SCADA web HMI system. Background Art

[0002] SCADA (Supervisory Control And Data Acquisition) is well known as a mechanism for monitoring and controlling social infrastructure systems, such as steel rolling systems, power transmission and transformation systems, water and sewage treatment systems, building management systems, and road systems.

[0003] SCADA is a type of industrial control system that uses computers to monitor systems, control processes, and collect data. In SCADA, immediate responsiveness (real-time) that matches the processing performance of the system is required.

[0004] SCADA includes HMI (Human Machine Interface), monitoring control system, remote input and output device (RIO), and communication base station as subsystems.

[0005] HMI is a mechanism that displays the data of the monitored device to the operator so that the operator can monitor and control the monitored device. The monitoring control system is composed of Programmable Logic Controller (PLC) and the like. The monitoring control system collects the data of the monitored device and sends control instructions to the monitored device. The remote input and output device is connected to the sensor installed in the monitored device, converts the sensor signal into digital data, and sends the digital data to the monitoring control system. The communication base station connects the monitoring control system with the remote input and output device.

[0006] As an example of a SCADA HMI subsystem, a system including an HMI client device and an HMI server device is disclosed in Patent Document 1. In a conventional SCADA such as Patent Document 1, the HMI server device sends data received from a PLC to the HMI client device. The HMI client device includes a computer body, input devices such as a keyboard and a mouse, and a monitor, and displays an HMI screen on the monitor. In addition, the applicant has also recognized the following Patent Document 2 related to the present disclosure.

[0007] In the HMI subsystem of Patent Document 1, one HMI client device is required to display one HMI screen. From the viewpoint of reducing costs, installation space, failure rate, and communication load, it is desirable to be able to use multiple HMI screens simultaneously in one HMI client device.

[0008] Prior art literature

[0009] Patent Literature

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

[0011] Patent Document 2: Japanese Patent Application Publication No. 2019-114090 Summary of the invention

[0012] Problems to be solved by the invention

[0013] The inventor of the present application has conducted in-depth research and developed a browser-based SCADA HMI subsystem. According to this, the HMI screen can be realized as a web application that operates on a web browser. Therefore, multiple web browsers can be executed in one HMI client device and each web browser can display the HMI screen.

[0014] The study applies this browser-based SCADA HMI subsystem to the production line of industrial plants. In large-scale plants such as industrial plants, the production line is divided into multiple parts, and a studio (operating station) is set up for each part. An HMI client device that executes a web browser that draws the HMI screen is configured in each studio. An HMI server device that executes a web server that communicates with each web browser is configured in the electrical room.

[0015] The web browser of the HMI client device of the first part should be able to operate the HMI screen related to the equipment of the first part, and the web browser of the HMI client device of the second part should be able to operate the HMI screen related to the equipment of the second part. Therefore, the operation right is basically set for each HMI screen displayed by the web browser of each HMI client device according to the operation location of the HMI client device, that is, according to the part where the HMI client device is installed.

[0016] However, it is clear that it is not enough to set whether the operation is allowed or not according to each HMI screen based on the operation location of the HMI client device, and there is a risk of compromising the safety of the monitored equipment and machinery and then the industrial equipment. For example, the positions of multiple operators operating the HMI screen are not necessarily the same, and there are cases where the positions of multiple operators are different. In this case, some of the multiple operating components on the HMI screen (specific operating components) are required to be able to be operated by the operator but not by the equipment operator. In order to meet this requirement, it is necessary to set more detailed operating rights for each HMI screen.

[0017] The present disclosure is made to solve the above-mentioned problems. The purpose of the present disclosure is to provide a SCADA web HMI system that can set the operation rights for each HMI screen according to the operator's position while being based on the function of setting the operation rights for each HMI screen according to the operation location of the HMI client device.

[0018] Means for solving problems

[0019] The first viewpoint relates to a SCADA web page HMI system. The SCADA web page HMI system includes an HMI server device that executes a web page server, and a plurality of HMI client devices that execute at least one web page browser that communicates with the web page server. The HMI server device includes a server processor and a server memory. The server memory stores image data, screen operation right information, and component operation right information of an HMI screen used to monitor an industrial plant. The screen operation right information specifies whether the HMI screen can be operated according to each HMI screen displayed on the web page browser according to the operation location of the HMI client device. The component operation right information specifies whether a part of the multiple operation components on the HMI screen, that is, a specific operation operation component, can be operated according to each HMI screen displayed on the web page browser according to the position of the operator of the HMI client device. The server processor is configured to execute the web page server that can send image data, screen operation right information, and component operation right information to the web page browser. The HMI client device includes a client processor, a client memory, and a monitor. The client memory stores image data, screen operation right information, and component operation right information received from the web page server. The client processor is configured to execute a web page browser displayed on the monitor and screen drawing processing. The screen drawing process is to apply the operation permissions specified in the screen operation right information to multiple operating components on the HMI screen, and preferentially apply the operation permissions specified according to the position in the component operation right information to specific operating components on the HMI screen, and draw the HMI screen on the web browser.

[0020] The second viewpoint has the following features in addition to the first viewpoint. The screen operation right information further specifies whether the HMI screen can be operated according to the position of the operator of the HMI client device and for each HMI screen displayed on the web browser. The component operation right information further specifies whether a part of the multiple operation components on the HMI screen, i.e., a specific operation component, can be operated according to each HMI screen displayed on the web browser, according to the operation location of the HMI client device.

[0021] The third viewpoint has the following features in addition to the first or second viewpoint: The screen drawing process is to draw the specific operating component in an inoperable state on the web browser, and draw the operating components other than the specific operating component among the multiple operating components in an operable state on the web browser, when the screen operation right information allows the operation of the HMI screen on the web browser, and the component operation right information does not allow the operation of the specific operating component on the web browser.

[0022] The fourth viewpoint has the following features in addition to the first or second viewpoint: When the screen operation right information does not allow the HMI screen to be operated on the web browser, and the part operation right information allows the operation of the specific operation part on the web browser, the specific operation part is drawn on the web browser in an operable state, and the operation parts other than the specific operation part among the plurality of operation parts are drawn on the web browser in an inoperable state.

[0023] Effects of the Invention

[0024] According to the present disclosure, when an HMI screen is drawn on a web browser, the operation permissions specified in the screen operation right information are applied to multiple operation components on the HMI screen, and the operation permissions specified in the component operation right information according to the position are preferentially applied to specific operation components on the HMI screen. Therefore, the operation rights are set for each HMI screen according to the operation location of the HMI client device, and the operation rights of the specific operation components on the HMI screen are preferentially set for each HMI screen according to the operator's position. As a result, more detailed operation rights are set for each HMI screen, so that the safety of the monitored plant can be prevented from being damaged. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 This is a diagram for explaining a configuration example of a hot rolling line to which the SCADA web HMI system according to the embodiment is applied.

[0026] Figure 2 This is a block diagram illustrating an outline of functions of an HMI server device and an HMI client device constituting a SCADA web HMI system.

[0027] Figure 3 (a) is a diagram showing an example of an HMI screen related to a roughing mill, and (b) is a diagram showing an example of an HMI screen related to a finishing mill.

[0028] Figure 4 This is a diagram showing an example of a screen operation right (operation location) table.

[0029] Figure 5 This is a diagram showing an example of a screen operation right (position) table.

[0030] Figure 6 This is a diagram showing an example of a component operation right (operation location) table.

[0031] Figure 7 This is a diagram showing an example of a component operation right (position) table.

[0032] Figure 8 This is a flowchart for explaining the screen drawing process according to the embodiment.

[0033] Fig. 9 This is a block diagram showing a hardware configuration example of a SCADA web HMI system according to an embodiment. DETAILED DESCRIPTION

[0034] Hereinafter, with reference to the accompanying drawings, the SCADA webpage HMI system of the embodiment of the present disclosure is described by taking the case where it is applied to a hot rolling line RL as an example. The hot rolling line RL is an example of a production line of an industrial system. In addition, the same reference numerals are marked on the common elements in each figure and repeated descriptions are omitted.

[0035] Figure 1 This is a diagram for explaining a configuration example of a hot rolling line RL to which the SCADA web HMI system 1 according to the embodiment is applied. Figure 2 This is a block diagram illustrating an outline of functions of an HMI server device and an HMI client device constituting a SCADA web HMI system. Figure 3 (a) is a diagram showing an example of an HMI screen related to a rough rolling mill. Figure 3 (b) is a diagram showing an example of an HMI screen related to a finishing mill.

[0036] The hot rolling line RL rolls a rolled material Mr such as a metal material into a desired plate thickness and plate width. The hot rolling line RL includes a heating furnace 2, a rough rolling mill 3, an intermediate equipment 4, a finishing mill 5, a water cooling device 6, a coiler 7, and a roller table (not shown) for conveying the rolled material Mr therebetween.

[0037] The heating furnace 2 heats the rolled material Mr. The heated rolled material 1 is extracted onto the roller table. The extracted rolled material Mr is a block of metal to be formed, called a slab. The rough rolling mill 3 is provided downstream of the heating furnace 2. The rough rolling mill 3 has a single or multiple (two in this embodiment) rolling stands. The rough rolling mill 3 rolls the rolled material Mr multiple times in the forward direction (from upstream to downstream) and the reverse direction (from downstream to upstream).

[0038] The intermediate equipment 4 is provided between the roughing mill 3 and the finishing mill 5. The intermediate equipment 4 includes an edge heater, a bar heater, a coil box, etc. The finishing mill 5 is provided downstream of the intermediate equipment 4. The finishing mill 5 has a plurality of (eight in this embodiment) rolling stands. The finishing mill 5 rolls the rolled material Mr in one direction from upstream to downstream.

[0039] The water cooling device 6 is provided downstream of the finishing mill 5. In the water cooling device 6, water is poured into the rolled material Mr to cool the rolled material Mr to a target temperature. The coiler 7 is provided downstream of the water cooling device 6. The rolled material Mr cooled by the water cooling device 6 is coiled by the coiler 7 to form a coiled product.

[0040] Each of the above-mentioned equipment and machines 2 to 7 has an actuator such as a motor and a driver device. In addition, various sensors (not shown) are provided as measuring devices at important positions of the rolling production line RL. Various sensors measure the status of the rolled material Mr and each of the equipment and machines 2 to 7 in turn. These actuators and sensors are connected to PLC8 via the control LAN91. PLC8 is connected to a computer 10 configured in a computer room via the control LAN91. The computer 10 calculates the set value for each of the equipment and machines 2 to 7 based on the rolled material Mr set for each of the equipment and machines 2 to 7, and sends the set value to PLC8. PLC8 controls the actuators of each of the equipment and machines 2 to 7 based on the set value received from the computer 10 and the control signal received from the HMI client device 12 described later via the HMI server device 11.

[0041] The SCADA web HMI system 1 includes the above-mentioned PLC 8, an HMI server device 11 disposed in an electrical room, and an HMI client device 12. The PLC 8, the HMI server device 11, and the HMI client device 12 are connected via an information LAN 92 such as Ethernet (registered trademark).

[0042] PLC8 periodically sends data packets containing block data to information LAN92 by multicast or broadcast. Block data is a collection of PLC signals. One block data contains dozens to hundreds of PLC signals. PLC signals include input / output signals and alarm signals. Input / output signals are generated by the operation of HMI client device 12, and include control signals for controlling actuators of each equipment machine 2 to 7 (hereinafter also referred to as "actuator control signals"), and detection signals measured by each sensor (hereinafter also referred to as "sensor detection signals"). PLC8 receives the above-mentioned control signals generated by the operation of the operating components on the HMI screen 17 described later of the HMI client device 12 from the HMI server device 11.

[0043] The hot rolling line RL is divided into a plurality of (two in this embodiment) parts corresponding to the equipment machines 2 to 7. Each part has a workroom (operating station). The part with the roughing mill 3 has an RM (Roughering Mills) workroom 13. The part with the finishing mill 5 has an FM (Finishing Mills) workroom 14. In addition, the number of parts and workrooms can be more than three.

[0044] Each studio 13, 14 is provided with an HMI client device 12a, 12b having a monitor 15a, 15b. The monitor 15a, 15b of the HMI client device 12a, 12b displays a web browser 16a, 16b, and an HMI screen 17a, 17b is displayed on the displayed web browser 16a, 16b. In addition, in this specification, when the reference numerals 12a, 15a to 17a and the reference numerals 12b, 15b to 17b are not distinguished, they are simply denoted as 12, 15 to 17.

[0045] In the HMI client device 12a of the RM studio 13, an HMI screen 17a related to the roughing mill 3 is displayed on a web browser 16a, and it is set to be able to operate the displayed HMI screen 17a (specifically, at least one component displayed on the HMI screen 17a). In the HMI client device 12a, a web browser 16b is executed, and other HMI screens 17b can also be displayed on the web browser 16b, but in principle, it is required that the HMI screen 17b cannot be operated. Similarly, in the HMI client device 12b of the FM studio 14, an HMI screen 17b related to the finishing mill 5 is displayed on a web browser 16b, and it is set to be able to operate the displayed HMI screen 17b. In the HMI client device 12b, a web browser 16a is executed, and other HMI screens 17a can also be displayed on the web browser 16a, but in principle, it is required that the HMI screen 17a cannot be operated. Therefore, in the present embodiment, the later-described Figure 4 The screen operation right (operation location) table 25 shown sets the screen operation right of each HMI screen 17 ( G10 , G11 , G12 ) according to the operation location of the HMI client device 12 .

[0046] However, the positions of multiple operators operating the HMI client device 12 are not necessarily the same, and there may be cases where multiple operators have different positions. Positions include operators who perform manual operations (manual intervention) on equipment and machinery, equipment operators who perform maintenance including repairs of equipment and machinery and replacement of components, and the like. Moreover, among the multiple HMI screens 17 (G10, G11, G12) displayed by the HMI client device 12, the HMI screen 17 (G10) is sometimes required to be able to be operated by the operator, and cannot be operated by the equipment operator. Therefore, in this embodiment, the following is used Figure 5 The screen operation right (position) table 26 shown sets the screen operation right of each HMI screen 17 ( G10 , G11 , G12 ) according to the position of the operator who logs in to the HMI client device 12 .

[0047] In addition, regarding specific operating components (described later) displayed on the HMI screen 17, it is sometimes required that the HMI client device 12 that does not have the screen operation right based on the operation location can operate. On the contrary, regarding specific operating components, it is sometimes required that the HMI client device 12 that has the screen based on the operation location cannot operate. Therefore, in this embodiment, the HMI client device 12 described later is used. Figure 6 The component operation right (operation location) table 27 shown sets the operation right (operation permission) of a specific operation component based on the operation location.

[0048] In addition, there are cases where different operators operate the same HMI screen 17. For example, a specific operating component for manual operation is sometimes required to be operated by the operator in charge of the operation and cannot be operated by the equipment operator. For example, a specific operating component for maintenance such as roller replacement is sometimes required to be operated by the equipment operator and cannot be operated by the operator in charge. Therefore, in this embodiment, the following is used Figure 7 The component operation right (position) table 28 shown sets the operation right (operation permission) of a specific operation component based on the position.

[0049] Figure 2 The HMI server device 11 shown in the figure sends and receives PLC signals with PLC8 and executes the web server. The HMI server device 11 is described later. Fig. 9As shown, there is a processor 111 for executing various processes and a memory 112 for storing various information. The processor 111 and the memory 112 correspond to the server processor and the server memory in the claims, respectively. By executing the program stored in the memory 112 by the processor 111, the processor 111 functions as a PLC signal processing unit 21 and a web server processing unit 22. The PLC signal processing unit 21 and the web server processing unit 22 can send and receive data to each other through inter-process communication.

[0050] The PLC signal processing unit 21 periodically receives a PLC signal including a sensor detection signal from the PLC 8, and sends the received PLC signal to the web browser processing unit 31 (each web browser 16) via the web server processing unit 22. In addition, the PLC signal processing unit 21 receives a PLC signal including an actuator control signal from each web browser 16 of the HMI client device 12 via the web server processing unit 22, and sends the received PLC signal to the PLC 8.

[0051] The web server processing unit 22 can communicate using the web browser 16 (web browser processing unit 31) of each HMI client device 12, HTTP (Hypertext Transfer Protocol), HTTPS (Hypertext Transfer Protocol Secure), and WebSocket. The web server processing unit 22 sends all or part of the content in response to a request from each web browser 16 (web browser processing unit 31). The content includes an HTML file (not shown), an SVG (Scalable Vector Graphics) file 23 that is image data of each HMI screen (HMI Screen) 17, a component library 24, a screen operation right (operation location) table 25, a screen operation right (position) table 26, a component operation right (operation location) table 27, and a component operation right (position) table 28.

[0052] The component library 24 includes a collection of scripts that describe actions for each type of component displayed on the HMI screen 17 (hereinafter referred to as "component type"). The script is a JavaScript (registered trademark) program defined for each component type. The script is assigned parameter values ​​as needed and can be executed on each web browser 16. The parameter values ​​include, for example, the presence or absence of screen operation rights specified in the screen operation rights (operation location) table 25 and the screen operation rights (position) table 26, and the presence or absence of specific component operation rights specified in the component operation rights (operation location) table 27 and the component operation rights (position) table 28.

[0053] Figure 41 is a diagram showing an example of a screen operation right (operation location) table 25. The screen operation right (operation location) table 25 includes screen operation right (operation location) information that specifies the presence or absence of screen operation rights (whether operation is permitted) for each HMI screen 17 according to the operation location of the HMI client device 12a, 12b, specifically, according to the RM studio 13, FM studio 14 provided for the HMI client device 12a, 12b. "G10" to "G12" are screen names of the HMI screen 17 displayed on the web browser 16 executed by each HMI client device 12. "G10" is Figure 3 The screen name of the HMI screen 17a shown in (a) is "G11". Figure 3 The screen name of the HMI screen 17b shown in (b). Figure 4 In the example shown, the HMI client device 12a operated in the RM studio 13 has the screen operation right to operate the HMI screen 17a (G10) on the web browser 16a, but does not have the screen operation right to operate the HMI screen 17 (G11, G12) on the web browser 16. In addition, the HMI client device 12b operated in the FM studio 14 has the screen operation right to operate the HMI screen 17b (G11) on the web browser 16b, but does not have the screen operation right to operate the HMI screen 17 (G10, G12) on the web browser 16.

[0054] Figure 5 2 is a diagram showing an example of the screen operation right (position) table 26. The screen operation right (position) table 26 includes screen operation right (position) information that specifies the screen operation right (or position) for each HMI screen 17 (whether the operation is permitted) according to the position of the operator logged into the HMI client device 12, specifically, the operator in charge of operation and the operator in charge of equipment. Figure 5 In the example shown, when the operator is logged in, he / she has the screen operation right to operate all HMI screens 17 (G10, G11, G12). When the equipment operator is logged in, he / she has the screen operation right to operate the HMI screen 17 (G11), but does not have the screen operation right to operate the HMI screens 17 (G10, G12).

[0055] Figure 6 1 is a diagram showing an example of a component operation right (operation location) table 27. The component operation right (operation location) table 27 includes component operation right (operation location) information that specifies the presence or absence of operation rights (operation permission or non-operation permission) of specific components displayed on each HMI screen 17 according to the operation location of the HMI client device 12a, 12b, specifically, according to the RM studio 13, FM studio 14 provided for the HMI client device 12a, 12b. Figure 6In the example shown, in the HMI client device 12a operated in the RM studio 13, the specific operating component (1_PL) on the HMI screen 17 (G10) is designated as inoperable, and the specific operating component (3_PL) on the HMI screen 17 (G11) is designated as operable. In addition, in the HMI client device 12b operated in the FM studio 14, the specific operating component (1_PL) on the HMI screen 17 (G10) is designated as operable, and the specific operating component (2_PL) on the HMI screen 17 (G11) is designated as inoperable.

[0056] Figure 7 1 is a diagram showing an example of a component operation right (position) table 28. The component operation right (position) table 28 includes component operation right (position) information that specifies the presence or absence of operation rights (operation permission or non-operation permission) of specific components displayed on each HMI screen 17 according to the position of the operator logged into the HMI client device 12, specifically, according to the operator in charge of operation and the operator in charge of equipment. Figure 7 In the example shown, when the operator is logged in, the specific operating components (1_PL) on the HMI screen 17 (G11) are designated as operable, and the specific operating components (4_PL, 5_PL) are designated as inoperable. The specific operating components (1_PL) are, for example, operating components for performing manual operations (manual intervention). In addition, when the equipment operator is logged in, the specific operating components (1_PL) on the HMI screen 17 (G11) are designated as inoperable, and the specific operating components (4_PL, 5_PL) are designated as operable. The specific operating components (4_PL, 5_PL) are, for example, operating components for performing maintenance.

[0057] The HMI client device 12 (12a, 12b) includes a processing circuit 30 (30a, 30b) and a monitor 15 (15a, 15b). The processing circuit 30 is described below. Fig. 9 As shown, it includes a processor 121 that performs various processes and a memory 122 that stores various information. The processor 121 and the memory 122 correspond to the client processor and the client memory of the claims, respectively. By executing the program stored in the memory 122 by the processor 121, the processor 121 functions as a web browser processing unit 31 (31a, 31b). In addition, in this specification, when the reference numerals 30a to 31a and the reference numerals 30b to 31b are not distinguished, they are simply recorded as 30 to 31.

[0058] The web browser processing unit 31 is executed according to each web browser 16. The web browser 16 depicts an HMI screen 17 for monitoring and controlling the hot rolling line RL. The HMI screen 17 is switched to another HMI screen 17 by the operation of the operator. A plurality of components are arranged on the HMI screen 17. The components include, for example, operating components (1_PL, 2_PL, 3_PL, ···) for sending control signals to the PLC 8 according to the operation of the operator, display components that change the display state (numerical value, character, color, shape) according to the received PLC signal, and screen transition components that switch to other HMI screens. Among the operating components, as described above, the component operating rights (operating location) include specific operating components (1_PL, 2_PL, 3_PL, ···, 5_PL) whose operability is specified by Table 27 and the component operating rights (position) table 28.

[0059] When each web browser 16 is started, the web browser processing unit 31 receives the above-mentioned HTML file, SVG file 23, component library 24, component library 25, screen operation right (operation location) table 25, screen operation right (position) table 26, component operation right (operation location) table 27, component operation right (position) table 28, etc. from the web server processing unit 22, and stores them in the memory 122. In addition, each web browser 16 (web browser processing unit 31) obtains the position of the operator logged in to the HMI client device 12, and stores it in the memory 122. The position of the operator can be obtained by referring to a group user list in which the login IDs and positions of a plurality of operators are collectively registered, for example. In addition, based on these, the web browser 16 draws the HMI screen 17 in which a plurality of components including operation components (including specific operation components) and display components are arranged. In addition, in order to always obtain the latest file from the web server processing unit 22 at the time of startup, each web browser 16 is executed in a mode that does not use cache.

[0060] The web browser processing unit 31 reads the screen operation right (operation location) table 25 received from the HMI server device 11, and determines whether the operation of each HMI screen 17 is possible (whether there is operation right) based on the operation location for each web browser 16. In addition, the web browser processing unit 31 reads the screen operation right (position) table 26 received from the HMI server device 11, and determines whether the operation of each HMI screen 17 is possible (whether there is operation right) based on the position for each web browser 16.

[0061] At the same time, the web browser processing unit 31 reads the component operation right (operation location) table 27 received from the HMI server device 11, and determines whether the specific operation components (1_PL, 2_PL, 3_PL, . . . , 5_PL) on the HMI screen 17 (for example, G11) can be operated according to the operation location for each web browser 16. In addition, the web browser processing unit 31 reads the component operation right (position) table 28 received from the HMI server device 11, and determines whether the specific operation components (1_PL, 2_PL, 3_PL, . . . , 5_PL) on the HMI screen 17 (G11) can be operated according to the position of the operator logged in to the HMI client device 12.

[0062] Then, the web browser processing unit 31 executes the screen drawing process 32. The screen drawing process 32 preferentially applies the operation rights (operation permission) corresponding to the operation location and the position of the operator specified in the component operation right (operation location) table 27 and the component operation right (position) table 28 to the specific operation components (1_PL, 2_PL, 3_PL, . . ., 5_PL) on the HMI screen 17 (G11), and applies the screen operation rights (operation permission) specified in the screen operation right (operation location) table 25 and the screen operation right (position) table 26 to the operation components other than the specific operation components on the HMI screen 17, and draws the HMI screen 17 (G11) on the web browser 16.

[0063] Specifically, the web browser processing unit 31 executes the script for each component type contained in the above-mentioned component library 24 according to the component type of the component configured on the HMI screen 17 (G11). Here, among the component types, the operation components whose actions change according to the presence or absence of the screen operation right and component operation right (parameter value) passed to the script are described.

[0064] Regarding the operation components (1_PL, 2_PL, 3_PL, 4_PL, . . . ), in the screen operation right (operation location) table 25 and the screen operation right (position) table 26, when the operation of the HMI screen 17 is not permitted in the web browser 16, in principle, all the operation components arranged on the HMI screen 17 of the web browser 16 are drawn in an inoperable state. In addition, in the screen operation right (operation location) table 25 and the screen operation right (position) table 26, when the operation of the HMI screen 17 is permitted in the web browser 16, in principle, all the operation components arranged on the HMI screen 17 of the web browser 16 are drawn in an operable state.

[0065] At the same time, in the component operation right (operation location) table 27 and the component operation right (position) table 28, when the operation right is defined for the specific operation components (1_PL, 2_PL, 3_PL, . . . , 5_PL) of the HMI screen 17 according to the operation location and the position of the operator, the operation right defined in the component operation right (operation location) table 27 and the component operation right (position) table 28 is applied to the specific operation components. For the operation components not defined in the component operation right (operation location) table 27 and the component operation right (position) table 28, the operation right defined in the screen operation right (operation location) table 25 and the screen operation right (position) table 26 is applied.

[0066] In addition, in the inoperable state, the operating component does not accept the execution operation (such as mouse click) of the operator including the operator (operator) and the equipment operator. In the operable state, the operating component accepts the execution operation of the operator and sends the control signal corresponding to the operation to the HMI server device 11.

[0067] In addition, when the HMI client device 12 receives a PLC signal from the HMI server device 11, the web browser processing unit 31 dynamically sets the screen operation right and the component operation right according to each HMI screen 17 displayed on each web browser 16 based on the received PLC signal. In this case, the screen operation right (operation location) table 25, the screen operation right (position) table 26, the component operation right (operation location) table 27, and the component operation right (position) table 28 are also referred to as described above, so detailed description is omitted.

[0068] Next, refer to Figure 8 , description of the HMI screen 17 in each web browser 16 according to the presence or absence of the operation right will be specifically described. Figure 8 This is a flowchart for explaining an example of the drawing process of the HMI client device 12 .

[0069] When the operator logs in to the HMI client device 12, Figure 8 The operator's position is an operator in charge of operation or an operator in charge of equipment. In step S1, the HMI client device 12 executes (starts) the web browser 16. The web browser processing unit 31 displays the web browser 16 on a predetermined monitor 15 at a predetermined initial position and initial size regardless of the position and size of the web browser 16 when it is closed.

[0070] In step S2, each web browser 16 obtains the position of the logged-in operator based on the login ID of the operator, and obtains the content from the HMI server device 12. The content includes the above-mentioned HTML file, SVG file 23, component library 24, screen operation right (operation location) table 25, screen operation right (position) table 26, component operation right (operation location) table 27, and component operation right (position) table 28. It is sufficient to obtain the component library 24 and each table 25 to 28 only when the web browser 16 is started.

[0071] In steps S3 to S12, the web browser processing unit 31 draws the specified HMI screen 17 on the web browser 16 according to the screen operation rights (operation location) table 25, the screen operation rights (position) table 26, the component operation rights (operation location) table 27 and the component operation rights (position) table 28 obtained in the above step S2.

[0072] The web browser processing unit 31 refers to the screen operation right (operation location) table 25 to determine whether there is screen operation right for the HMI screen 17 based on the operation location of the HMI client device 12 (step S3). If there is no screen operation right based on the operation location, the process proceeds to step S9. On the other hand, if there is screen operation right based on the operation location, the process proceeds to step S4.

[0073] In step S4, the screen operation right (position) table 26 is referenced to determine whether there is screen operation right for the HMI screen 17 based on the position acquired in step S2. If there is no screen operation right based on the position, the process proceeds to step S9. On the other hand, if there is screen operation right based on the position, the process proceeds to step S5.

[0074] In step S5, the table 27 of component operation rights (operation location) is referred to to determine whether there is a specific operation component that is designated as inoperable based on the operation location. If there is a specific operation component that is designated as inoperable based on the operation location, the process proceeds to step S8. On the other hand, if there is no specific operation component that is designated as inoperable based on the operation location, the process proceeds to step S6.

[0075] In step S6, the component operation right (position) table 28 is referenced to determine whether there is a specific operation component that is designated as inoperable based on the position. If there is a specific operation component that is designated as inoperable based on the position, the process proceeds to step S8. On the other hand, if there is no specific operation component that is designated as inoperable based on the position, the web browser processing unit 31 draws all the operation components on the HMI screen 17 in an operable state (step S7). After that, this routine is temporarily terminated.

[0076] In step S8, the specific operating components on the HMI screen 17 are drawn in an inoperable state, and the operating components other than the specific operating components are drawn in an operable state (step S8). Thereafter, this routine is temporarily terminated.

[0077] In step S9, the component operation right (operation location) table 27 is referenced to determine whether there is a specific operation component designated as operable based on the operation location. If there is a specific operation component designated as operable based on the operation location, the process proceeds to step S12. On the other hand, if there is no specific operation component designated as operable based on the operation location, the process proceeds to step S10.

[0078] In step S10, the component operation right (position) table 28 is referenced to determine whether there is a specific operation component that is designated as operable based on the position. If there is a specific operation component that is designated as operable based on the position, the process proceeds to step S12. On the other hand, if there is no specific operation component that is designated as operable based on the position, the process proceeds to step S11.

[0079] In step S11, the web browser processing unit 31 draws all the operating components on the HMI screen 17 in an inoperable state (step S11). Thereafter, this routine is temporarily terminated.

[0080] In step S12 , the web browser processing unit 31 draws the specific operating components on the HMI screen 17 in an operable state, and draws the operating components other than the specific operating components in an inoperable state (step S12 ). Thereafter, this routine is temporarily terminated.

[0081] The processing of steps S1 to S12 described above is performed every time the operator logs in to the HMI client device 12 and starts the web browser 16 .

[0082] According to the routine described above, when the screen operation right (operation location) table 25 allows operation of the HMI screen 17 based on the operation location, but the component operation right (position) table 28 does not allow operation of a specific operation component based on the position, the web browser processing unit 31 depicts the specific operation component in an inoperable state on the web browser 16, and depicts operation components other than the specific operation component in an operable state on the web browser 16.

[0083] In the above Figure 8In the flowchart of FIG. 1 , the drawing of the HMI screen 17 when the web browser 16 is started is explained. Thus, the screen operation right and the existence of the operation right of the operation components on the HMI screen 17 can be statically set for each HMI screen 17. Sometimes, in the logged-in state, the operator presses the screen transition button on the HMI screen 17 to change to another HMI screen 17. In this case, the web browser processing unit 31 newly obtains the HTML file and SVG file 23 related to the other HMI screen 17 from the HMI server device 12, and executes the processing after step S3, thereby statically setting the existence of the screen operation right and the component operation right for each HMI screen 17.

[0084] After the screen operation rights and component operation rights are statically set in this way, the HMI client device 12 receives a PLC signal from the HMI server device 11 and executes the processing of steps S2 to S12 to statically set the screen operation rights and component operation rights for each HMI screen 17 .

[0085] As described above, according to the present embodiment, when the HMI screen 17 is drawn on the web browser 16, the operation permissions specified in the screen operation rights (operation location) table 25 are applied to a plurality of operation components on the HMI screen 17, and the operation permissions specified according to the position in the component operation rights (position) table 28 are preferentially applied to specific operation components on the HMI screen 17. Therefore, the operation rights are set for each HMI screen 17 according to the operation location of the HMI client device 12, and the operation rights of specific operation components are preferentially set for each HMI screen 17 according to the position of the operator. Thus, more detailed operation rights are set for each HMI screen 17, so that the safety of the monitored equipment 2 to 7 and, moreover, the hot rolling line RL can be prevented from being damaged.

[0086] Fig. 9 This is a block diagram showing a hardware configuration example of the HMI server device 11 and the HMI client device 12 .

[0087] Each process of the above-mentioned HMI server device 11 is realized by a processing circuit. The processing circuit is composed of a processor 111, a memory 112, and a network interface 113 connected to each other. The processor 111 as a server processor executes various programs stored in the memory 112 as a server memory, thereby realizing each function of the HMI server device 11. The memory 112 includes a main storage device and an auxiliary storage device. The memory 112 pre-stores the above-mentioned HTML file, SVG file 23, component library 24, screen operation right (operation location) table 25, screen operation right (position) table 26, component operation right (operation location) table 27, and component operation right (position) table 28. The network interface 113 is connected to other devices in the same network via the information LAN 92 so as to be able to communicate.

[0088] Each process of the HMI client device 12 is implemented by the processing circuit 30. The processing circuit 30 is composed of a processor 121, a memory 122, a network interface 123, an input interface 124, and a monitor 125 connected together. The processor 121 implements each function of the HMI client device 12 by executing various programs stored in the memory 122. The memory 122 includes a main storage device and an auxiliary storage device. The network interface 123 is connected to other devices in the same network via the information LAN 92 so as to be able to communicate. The input interface 124 is a group of input devices composed of a keyboard, a mouse, a touch panel, etc.

[0089] The above describes the embodiments of the present disclosure, but the present disclosure is not limited to the above embodiments and can be implemented in various ways without departing from the main purpose of the present disclosure. For example, in the above embodiments, the case where the operator's position includes an operator and a device operator is described as an example, but the position may also include a safety officer who allows the operation of all specific operating components in addition to these operators and device operators. In addition, operators may be divided into multiple groups according to the proficiency of manual operation. For example, operators may be divided into older operators with higher proficiency in manual operation (older operators) and younger operators with lower proficiency than older operators (young operators). The present disclosure can be applied, for example, to the case where the operator's position includes a senior operator, a junior operator, a device operator, and a safety officer.

[0090] In addition, for example, it is possible to configure that the operator's position includes a senior operator with high proficiency in manual operation and a junior operator with lower proficiency than the senior operator, when the operator in charge of the equipment does not operate the HMI client device 12. In this case, the operation of specific operating components by the junior operator can be restricted, and as a result, the safety of the monitored equipment and thus the hot rolling line RL can be prevented from being damaged in the same way as in the above-mentioned embodiment.

[0091] Furthermore, in the above-described embodiment, although the case of monitoring the equipment of the hot rolling line RL is described as an example, the present invention can also be applied to the case of monitoring the equipment of other industrial plants.

[0092] In addition, when the number, quantity, amount, range, etc. of each element is mentioned in the above embodiments, the present disclosure is not limited to the mentioned number unless it is specifically stated or it is clearly determined in principle to be the number. In addition, the structure etc. described in the above embodiments are not essential to the present disclosure unless it is specifically stated or it is clearly determined in principle to be the number.

[0093] Description of Reference Numerals

[0094] 1…SCADA web HMI system, 2…heating furnace, 3…roughing mill, 4…intermediate equipment, 5…finishing mill, 6…water cooling device, 7…winding machine, 8…PLC, 91…control LAN, 92…information LAN, 10…computer, 11…HMI server device, 12, 12a, 12b…HMI client device, 13…RM studio, 14…FM studio, 15, 15a, 15b…monitor, 16, 16a, 16b…web browser, 17, 17a, 17b…HMI screen, 21…PLC signal processing unit, 22…web server processing unit, 23…SVG file, 24…component library, 25…screen operation right (operation location) table, 26…screen operation right (position) table, 2 7…component operation rights (operation location) table, 28…component operation rights (position) table, 30, 30a, 30b…processing circuit, 31, 31a, 31b…web browser processing unit, 32, 32a, 32b…screen drawing processing, 111, 121…processor, 112, 122…memory, 113, 123…network interface, 124…input interface, RL…hot rolling line, Mr…rolled material, G10, G11, G12…screen name, RM1_1, RM1_2, FM1_1, FM1_2…browser name, 1_PL, 2_PL, 3_PL, 4_PL, 5_PL, ···…operation component, 1_PL, 2_PL, 3_PL, 4_PL, 5_PL…specific operation component.

Claims

1. A SCADA web HMI system comprising an HMI server device executing a web server, and a plurality of HMI client devices executing at least one web browser communicating with the web server, wherein: The HMI server device comprises a server processor and a server memory. The server memory stores image data of an HMI screen for monitoring an industrial plant, screen operation right information, and component operation right information. The screen operation right information specifies whether the HMI screen can be operated according to the operation location of the HMI client device and for each HMI screen displayed on the web browser. The component operation right information specifies whether a part of a plurality of operation components on the HMI screen, i.e., a specific operation component, can be operated according to the position of the operator of the HMI client device and the HMI screen displayed on the web browser. The server processor is configured to execute the web server capable of sending the image data, the screen operation right information, and the component operation right information to the web browser. The HMI client device comprises a client processor, a client memory and a monitor. The client memory stores the image data, the screen operation right information and the component operation right information received from the web server, The client processor is configured as follows: executing the web browser displayed on the monitor, The following screen drawing processing is performed: the operation permissions specified in the screen operation right information are applied to the multiple operating components on the HMI screen, and the operation permissions specified in the component operation right information according to the position are preferentially applied to the specific operating component on the HMI screen, and the HMI screen is drawn on the web browser.

2. The SCADA web page HMI system as claimed in claim 1, wherein: The screen operation right information further specifies whether the HMI screen can be operated according to the position of the operator of the HMI client device and according to each HMI screen displayed on the web browser. The component operation right information further specifies whether or not a part of a plurality of operation components on the HMI screen, namely, a specific operation component, is operable for each HMI screen displayed on a web browser, according to the operation location of the HMI client device.

3. The SCADA webpage HMI system according to claim 1 or 2, wherein: The picture drawing process is as follows: When the screen operation right information allows the web browser to operate the HMI screen, and the component operation right information does not allow the web browser to operate the specific operation component, The specific operating component is depicted in the web browser in an inoperable state, An operation member other than the specific operation member among the plurality of operation members is drawn in the web browser in an operable state.

4. The SCADA webpage HMI system according to claim 1 or 2, wherein: The picture drawing process is as follows: When the screen operation right information does not allow the web browser to operate the HMI screen, and the component operation right information allows the web browser to operate the specific operation component, The specific operating component is depicted in the web browser in an operable state, An operation member other than the specific operation member among the plurality of operation members is drawn in the web browser in an inoperable state.

Images