SCADA web-based HMI client device and SCADA web-based HMI system

Abstract

The SCADA web-based HMI client device includes a processor and a memory. The memory stores image data, screen operation permission information, and exception information received from a web server for monitoring the HMI screen in an industrial plant. The screen operation permission information determines whether each web browser can operate the HMI screen. The exception information determines whether each web browser can operate specific operating components on the HMI screen. The processor prioritizes applying the operation permission settings determined by the exception information to the specific operating components on the HMI screen, and applies the operation permission settings determined by the screen operation permission information to the operating components other than the specific operating components on the HMI screen, performing screen rendering processing to display the HMI screen on the web browser.

Description

Technical Field

[0001] This disclosure relates to SCADA web HMI client devices and SCADA web HMI systems. Background Technology

[0002] SCADA (Supervisory Control and Data Acquisition) is well-known as a mechanism for monitoring and controlling social infrastructure systems. These systems include steel rolling mills, power transmission and transformation systems, water supply and drainage systems, building management systems, and road systems.

[0003] SCADA is a type of industrial control system that performs system monitoring, process control, and data collection via computer. SCADA requires real-time responsiveness to match the system's processing capabilities.

[0004] SCADA typically consists of the following subsystems.

[0005] (1) HMI (Human Machine Interface)

[0006] HMI is an organization that provides data from the monitored device to the operator, enabling the operator to monitor and control the monitored device.

[0007] (2) Monitoring and Control System

[0008] The monitoring and control system consists of a programmable logic controller (PLC), etc. It collects data from the monitored devices and sends control commands to them.

[0009] (3) Remote Input Output (RIO)

[0010] The remote input / output device connects to the sensor installed on the monitored device, converts the sensor signal into digital data, and sends the digital data to the monitoring and control system.

[0011] (4) Communication infrastructure

[0012] Communication infrastructure connects monitoring and control systems with remote input / output devices.

[0013] As an example of a SCADA HMI subsystem, Patent Document 1 discloses a system comprising an HMI client device and an HMI server device. In conventional SCADA systems like those in Patent Document 1, the HMI server device sends data received from the PLC to the HMI client device. The HMI client device includes a computer, input devices such as a keyboard and mouse, and a monitor, on which an HMI screen is displayed.

[0014] In addition, as documents associated with this disclosure, including the aforementioned documents, the applicant has identified the following documents.

[0015] Existing technical documents

[0016] Patent documents

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

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

[0019] The problem that the invention aims to solve

[0020] In the HMI subsystem of Patent Document 1 mentioned above, one HMI client device is required to display one HMI screen. From the viewpoints of reducing costs, setup space, failure rate, and communication load, it is desirable to be able to use multiple HMI screens simultaneously with one HMI client device.

[0021] The inventors of this application conducted specific research, resulting in the development of a browser-based SCADA HMI subsystem. This allows HMI displays to be displayed as a web application operating on a web browser. Therefore, it is possible to run multiple web browsers on a single HMI client device, with each web browser displaying the HMI screen.

[0022] The application of such a browser-based SCADA HMI subsystem to an industrial production line was studied. The large-scale plant, such as the industrial production line, is divided into multiple sections, each with an operation room (pulpit). Each operation room contains an HMI client device that executes a web browser to display the HMI screen. An HMI server device, which communicates with each web browser, is located in the electrical room.

[0023] The dedicated HMI screens related to the equipment in segment 1 should be operable through the web browser of the HMI client device in segment 1, and the dedicated HMI screens related to segment 2 should be operable through the web browser of the HMI client device in segment 2. In other words, setting operational rights on an HMI screen unit basis in each web browser is fundamental. This is because large-scale factories have thousands of operational signals, making it impossible to manage operational rights on an HMI screen part basis.

[0024] However, there are also cases where an intermediate device is set up between the first and second segments. In such cases, a shared HMI screen is required, encompassing the output device of the first segment, the intermediate device, and the input device of the second segment. This shared HMI screen is used by both the HMI client devices of the first and second segments.

[0025] In this scenario, from segment 1, one can operate the operating components on the shared HMI screen related to the device in segment 1, but not the operating components related to the device in segment 2. Conversely, from segment 2, one can operate the operating components on the shared HMI screen related to the device in segment 2, but not the operating components related to the device in segment 1. Regarding intermediate devices, there are cases where operation can be performed from either segment. Therefore, regarding the shared HMI screen, simply setting operating rights at the HMI screen unit level is insufficient; it is necessary to assign appropriate operating rights at the unit level.

[0026] The present invention was made to solve the aforementioned problems, and its purpose is to provide a SCADA web page HMI client device and a SCADA web page HMI system, which in principle can set operation rights for each web browser on an HMI screen unit, and as an exception, can set operation rights for each web browser on an operation component unit basis for specific operation components on the HMI screen.

[0027] Methods used to solve problems

[0028] The first technical solution is associated with the SCADA web-based HMI client device.

[0029] The aforementioned SCADA web-based HMI client device executes at least one web browser to communicate with the web server.

[0030] The aforementioned SCADA web-based HMI client device includes a processor, memory, and a monitor.

[0031] The aforementioned memory stores image data, screen operation permission information, and exception information received from the aforementioned web server for monitoring the HMI screen of the industrial plant. Specifically, the screen operation permission information specifies whether each web browser can operate the aforementioned HMI screen. The exception information specifies whether each web browser can operate specific operating components on the aforementioned HMI screen. These specific operating components are a subset of multiple operating components on the aforementioned HMI screen.

[0032] The processor is configured to perform the web browser and screen rendering processes displayed on the monitor.

[0033] The above-described screen rendering process preferentially applies the operability settings configured by the above-described exception information to the specific operation components on the above-described HMI screen, and applies the operability settings configured by the above-described screen operation right information to the operation components other than the specific operation components among the above-described multiple operation components on the above-described HMI screen, and renders the above-described HMI screen on the above-described web browser.

[0034] The second technical solution is associated with the SCADA web-based HMI system.

[0035] The aforementioned SCADA web-based HMI system includes an HMI server device that executes a web server and an HMI client device that executes at least one web browser that communicates with the aforementioned web server.

[0036] The aforementioned HMI server device includes a server processor and server memory.

[0037] The server's memory stores image data, screen operation permission information, and exception information used to monitor the HMI screen in the industrial plant. The screen operation permission information specifies whether each web browser can operate the HMI screen. The exception information specifies whether each web browser can operate specific operating components on the HMI screen. These specific operating components are a subset of multiple operating components on the HMI screen.

[0038] The aforementioned server processor is configured to execute the aforementioned web server, which is capable of sending the aforementioned image data, the aforementioned screen operation right information, and the aforementioned exception information to the aforementioned web browser.

[0039] The aforementioned HMI client device includes a client processor, client memory, and a monitor.

[0040] The aforementioned client-side storage stores the aforementioned image data, the aforementioned screen operation rights information, and the aforementioned exception information received from the aforementioned web server.

[0041] The aforementioned client processor is configured to execute the web browser and screen rendering processes displayed on the aforementioned monitor.

[0042] The above-described screen rendering process preferentially applies the operability settings configured by the above-described exception information to the specific operation components on the above-described HMI screen, and applies the operability settings configured by the above-described screen operation right information to the operation components other than the specific operation components among the above-described multiple operation components on the above-described HMI screen, and renders the above-described HMI screen on the above-described web browser.

[0043] Invention Effects

[0044] According to this disclosure, in principle, operational permissions for each web browser can be assigned on an HMI screen unit basis. As an exception, operational permissions for specific operational components on the HMI screen can be assigned to each web browser on an operational component unit basis. Therefore, operational permissions for each web browser can be effectively managed on an HMI screen unit basis, and, as needed, operational permissions for each web browser can be managed on an operational component unit unit basis as an exception. Attached Figure Description

[0045] Figure 1 This is a diagram illustrating an example of the configuration of a hot rolling production line for implementing the relevant embodiments.

[0046] Figure 2 This is a diagram illustrating an example of a shared HMI screen used to explain an implementation method.

[0047] Figure 3 This is a block diagram illustrating the general functions of an HMI server device and an HMI client device according to an embodiment.

[0048] Figure 4 This is a diagram illustrating an example of an operation right table related to an implementation method.

[0049] Figure 5 This is a diagram illustrating an example of an exception table related to the implementation method.

[0050] Figure 6 This is a flowchart used to explain the screen depiction process related to the implementation method.

[0051] Figure 7 This is a block diagram illustrating an example of the hardware configuration of a SCADA web-based HMI system according to an implementation method. Detailed Implementation

[0052] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Furthermore, common elements in the various figures are given the same reference numerals, and repeated descriptions are omitted.

[0053] Implementation method.

[0054] 1. Production lines in industrial systems

[0055] Reference Figure 1 An example of an industrial system production line is used as an application of a SCADA web-based HMI system. Figure 1 This is a diagram illustrating an example of the configuration of a hot rolling production line for implementing the relevant embodiments.

[0056] During processing by the hot rolling production line, the metal material 1 is drawn to a thinner thickness, and its dimensions and temperature are controlled toward the desired target values. The hot rolling production line includes a heating furnace 2, a roughing mill 3, intermediate equipment 4, a finishing mill 5, a water cooling device 6, a coiler 7, and a roller table (not shown) that transports the material 1 between them.

[0057] The heating furnace 2 heats the rolled material 1. The heated rolled material 1 is then pulled onto the roller conveyor. When it comes out of the heating furnace 2, the rolled material 1 is a formed metal block called a slab.

[0058] The roughing mill 3 is located downstream of the heating furnace 2. The roughing mill 3 has a single rolling stand or multiple rolling stands. The roughing mill 3 rolls the workpiece 1 multiple times in the forward direction (from upstream to downstream) and the reverse direction (from downstream to upstream).

[0059] Intermediate equipment 4 is located downstream of roughing mill 3. Intermediate equipment 4 includes edge heater, bar heater, coil box, etc.

[0060] The finishing mill 5 is located downstream of the intermediate equipment 4. The finishing mill 5 has multiple rolling stands and rolls the workpiece 1 unidirectionally from upstream to downstream. Through finishing rolling, the final quality related to the dimensions of the workpiece 1, such as thickness and width, is determined.

[0061] A water cooling device 6 is located downstream of the finishing mill 5. Water is injected into the rolled stock 1 in the water cooling device 6. The rolled stock 1 is cooled to the target temperature by the water cooling device 6.

[0062] The coiling machine 7 is located downstream of the water cooling device 6. The rolled material 1, cooled by the water cooling device 6, is guided downward by pinch rollers and wound onto the coiling machine 7 to form a coil-shaped product.

[0063] Each of the aforementioned devices (2-7) is connected to the PLC8 via a motor or drive unit. The PLC8 is connected to the computer 10 located in the computer room via the control LAN9. The computer 10 calculates the set values ​​for each device (2-7) based on the rolling plan for the rolled material 1 and sends them to the PLC8. The PLC8 controls each device (2-7) based on the set values.

[0064] Furthermore, PLC 8 is connected to HMI server device 12 located in the electrical room via information LAN 11, such as Ethernet (registered trademark). PLC 8 periodically sends packets containing block data to information LAN 11 via multicast or broadcast. Block data is a collection of PLC signals. A single block of data contains tens to hundreds of PLC signals. PLC signals include input / output signals (including actuator control signals and sensor detection signals) and alarm signals. In addition, PLC 8 receives control signals related to each device from HMI server device 12.

[0065] The large-scale plant, like the hot rolling production line described above, is divided into multiple sections. Each section has an operating room (control console). RM (Roughing Mills) control console 13 is the operating room for the section with the roughing mill 3. FM (Finishing Mills) control console 14 is the operating room for the section with the finishing mill 5. DC (Down Coiler) control console 15 is the operating room for the section with the coiling machine 7.

[0066] Each operating room is equipped with an HMI client device 16 capable of operating each HMI screen via a web browser. The web browser of HMI client device 16a on the RM console 13 allows operation of a dedicated HMI screen related to the roughing mill 3. The web browser of HMI client device 16b on the FM console 14 allows operation of a dedicated HMI screen related to the finishing mill 5. The web browser of HMI client device 16c on the DC console 15 allows operation of a dedicated HMI screen related to the coiling machine 7. In other words, setting operating authority for each web browser on an HMI screen unit basis is fundamental. This is because large-scale plants have thousands of operating signals, making it impossible to set operating authority on an operating component unit basis on the HMI screen. Furthermore, in this specification, without distinguishing between the various HMI client devices (16a, 16b, 16c), they are simply referred to as HMI client device 16.

[0067] In addition, an intermediate device 4 is installed between the roughing mill 3 and the finishing mill 5. In this case, it is necessary to... Figure 2 The example includes a shared HMI screen 17 for the exit equipment of the roughing mill 3, the intermediate equipment 4, and the inlet equipment of the finishing mill 5. The shared HMI screen 17 is used by both the RM control console 13 and the FM control console 14.

[0068] In this case, the operating components 18 related to the roughing mill 3 on the shared HMI screen 17 can be operated from the RM console 13, but the operating components 19 related to the finishing mill 5 cannot be operated. Conversely, the operating components 19 related to the finishing mill 5 on the shared HMI screen 17 can be operated from the FM console 14, but the operating components 18 related to the roughing mill 3 cannot be operated. There are cases where the operating components 20 related to the intermediate equipment 4 can be operated from both consoles. For example, for the coil box, which is the intermediate equipment 4, winding is operated from the RM console 13, and unwinding is operated from the FM console 14. Therefore, regarding the shared HMI screen 17, it is not sufficient to simply set the operating rights on an HMI screen unit basis; it is necessary to assign appropriate operating rights on an operating component unit basis.

[0069] Therefore, in the SCADA web page HMI system of this embodiment, in principle, operation rights can be set for each web browser on an HMI screen unit basis. In addition, operation rights for specific operation components on the HMI screen can be set for each web browser on an operation component unit basis.

[0070] 2. SCADA web-based HMI system

[0071] Reference Figures 3-5 The SCADA web-based HMI system of this embodiment will be described. The SCADA web-based HMI system includes an HMI server device 12 and an HMI client device 16 that are interconnected via an information LAN 11.

[0072] 2-1. Structure of HMI Server Device

[0073] Figure 3 The HMI server device 12 shown transmits and receives PLC signals and control signals with PLC 8, and also executes a web server. The HMI server device 12 is described below. Figure 7 As shown, the system includes a processor 61 that performs various processes and a memory 62 that stores various information. The processor 61 executes programs stored in the memory 62, functioning as both the PLC signal processing unit 21 and the web server processing unit 22. The PLC signal processing unit 21 and the web server processing unit 22 can send and receive data through inter-process communication.

[0074] The PLC signal processing unit 21 periodically sends PLC signals received from PLC8 to each web browser 36 (web browser processing unit 31) via the web server processing unit 22. In addition, the PLC signal processing unit 21 sends control signals received from each web browser 36 via the web server processing unit 22 to PLC8.

[0075] The web server processing unit 22 can communicate with the web browsers 36 (web browser processing unit 31) of each HMI client device 16 using HTTP (Hypertext Transfer Protocol), HTTPS (Hypertext Transfer Protocol Secure), and WebSocket. The web server processing unit 22 sends content according to requests from each web browser 36 (web browser processing unit 31). The content includes HTML files (illustration omitted), SVG (Scalable Vector Graphics) files 25 which are image data for each HMI screen, a part library 26 describing the actions for each part type, an operation rights table 27, and an exception table 28.

[0076] Component library 26 contains a collection of scripts that describe actions for each component type. Scripts are JavaScript (registered trademark) programs defined for each component type. Scripts can be executed on various web browsers 36 as needed, provided with parameter values ​​(e.g., the presence or absence of operation rights as defined in operation rights table 27 and exception table 28).

[0077] The operation rights table 27 contains screen operation rights information for each web browser 36, which sets whether each HMI screen 37 can be operated (operation is allowed or not allowed).

[0078] Figure 4 This is a diagram illustrating an example of the operation rights table 27. “G10” to “G13” are the screen names of each HMI screen 37. “RM1_1” is the browser name of the first web browser 36a executed by HMI client device 16a. “RM1_2” is the browser name of the second web browser (not shown) executed by HMI client device 16a. “FM1_1” is the browser name of the first web browser 36b executed by HMI client device 16b, and “FM1_2” is the browser name of the second web browser (not shown) executed by HMI client device 16b. As an example, the browser name is a combination of the computer's device name and the monitor number. Figure 4 In the example shown, web browser 36a (RM1_1) has the right to operate HMI screen 37a (G10), while web browser 36b (FM1_1) does not have the right to operate HMI screen 37b (G10).

[0079] As described above, in principle, operation rights are set in HMI screen units as defined by operation rights table 27, but for specific HMI screens (shared HMI screen 17) Figure 1 , Figure 2 However, exceptions require setting operation rights on a per-operation-component basis. Exception Table 28 contains exception information for setting whether operation rights (operation is permitted or not permitted) are allowed for specific operation components on each HMI screen 37 for each web browser 36. A specific operation component is one of a set of operation components on the HMI screen 37.

[0080] Figure 5 This is a diagram representing an example of exception table 28. "G11" is a shared HMI screen 17, which is one of HMI screens 37. Figure 2 The screen name. Regarding shared HMI screen 17 (G11) in operation right table 27 ( Figure 4 In this context, operation rights are not allowed for all web browsers 36. However, for specific operation units (1_PL, 2_PL, 3_PL) on the shared HMI screen 17 (G11), operation rights are set on a unit-by-unit basis by exception table 28. Web browser 36a (RM1_1) has operation rights for operation units 18 (1_PL) and 19 (3_PL), but not for operation unit 20 (2_PL). Web browser 36b (FM1_1) has operation rights for operation units 20 (2_PL) and 19 (3_PL), but not for operation unit 18 (1_PL).

[0081] That is, Exception Table 28 defines that: the web browser 36a (RM1_1) from the RM console can only operate operating parts 18 (1_PL) related to the roughing mill 3 and operating parts 20 (2_PL) related to the intermediate equipment 4; the web browser 36b (FM1_1) from the FM console can only operate operating parts 19 (3_PL) related to the finishing mill 5 and operating parts 20 (2_PL) related to the intermediate equipment 4. Furthermore, operating rights (including blanks) for operating parts not defined by Exception Table 28 follow the definitions in Operating Rights Table 27.

[0082] 2-2. Structure of HMI Client Device

[0083] Back Figure 3 Continuing the explanation, the HMI client device 16 (16a, 16b) includes processing circuitry 30 (30a, 30b) (including those described later). Figure 7The processor 71 shown performs various processes, the memory 72 stores various information, and the monitor 35 (35a, 35b) executes the program stored in the memory 72. The processor 71 functions as a web browser processing unit 31 (31a, 31b) by executing the program stored in the memory 72. In addition, in this specification, unless otherwise distinguished from the reference numerals 30a to 37a, they are abbreviated as 30 to 37.

[0084] The web browser processing unit 31 executes according to each web browser 36. The web browser 36 displays an HMI screen 37 for monitoring and controlling the industrial plant. The HMI screen 37 is switched to other HMI screens 37 by the operator's operation. Multiple components are arranged in the HMI screen 37. Components include, for example, an operation component for sending control signals to the PLC 8 in response to the operator's operation, a display component for displaying changes in status (value, character, color, shape) in response to the received PLC signals, and a screen transfer component for switching to other HMI screens, etc.

[0085] Each web browser 36 (web browser processing unit 31) receives the aforementioned HTML file, SVG file 25, component library 26, operation right table 27, exception table 28, etc., from the web server processing unit 22 upon startup and stores them in the memory 72. Based on these, the web browser 36 displays the HMI screen 37 configured with the components. Furthermore, in order to always obtain the latest files from the web server processing unit 22 upon startup, each web browser 36 operates in a mode without using caching.

[0086] The web browser processing unit 31 reads the operation right table 27 received from the HMI server device 12 and determines whether the operation of each HMI screen 37 is possible (whether the operation right exists) for each web browser 36. In addition, the web browser processing unit 31 reads the exception table 28 received from the HMI server device 12 and determines whether the operation of a specific operation button on the HMI screen 37 (shared HMI screen 17) is possible for each web browser 36.

[0087] Then, the web browser processing unit 31 performs screen rendering processing 32. The screen rendering processing 32 preferentially applies the operation permission setting set by the exception table 28 to specific operation components on the HMI screen 37, and applies the operation permission setting set by the operation permission table 27 to operation components other than specific operation components among the multiple operation components on the HMI screen 37, and renders the HMI screen 37 on the web browser 36.

[0088] Specifically, the web browser processing unit 31 executes the script for each component type included in the component library 26, based on the component types of the components configured in the HMI screen 37. Here, the operation components whose actions change according to the presence or absence of operation rights (parameter values) in the pervasive script will be explained.

[0089] Regarding the operating components, if the operation right table 27 indicates that the web browser 36 does not allow operation of the HMI screen 37, then in principle, all operating components configured in the HMI screen 37 of the web browser 36 will be depicted as inoperable. Conversely, if the operation right table 27 indicates that the web browser 36 allows operation of the HMI screen 37, then in principle, all operating components configured in the HMI screen 37 of the web browser 36 will be depicted as operable.

[0090] As an exception, if an operation right is defined for a specific operating component of a particular HMI screen 37 (shared with HMI screen 17) in Exception Table 28, the operation right defined in Exception Table 28 shall prevail for that specific operating component. For operating components not defined in Exception Table 28, the operation right defined in Operation Right Table 27 shall apply.

[0091] Furthermore, in the inoperable state, the operating component does not accept the operator's actions (such as mouse clicks). In the operable state, the operating component accepts the operator's actions and sends the corresponding control signal to the HMI server device 12.

[0092] 3. Example of HMI client device processing

[0093] Reference Figures 4-6 The description of the HMI screen 37 in each web browser 36 corresponding to the presence or absence of operating rights is explained in detail. Figure 4 This is a diagram illustrating an example of the aforementioned operation weight table 27. Figure 5 This is a diagram illustrating one example of the exceptions in Table 28 mentioned above. Figure 6 This is a flowchart used to illustrate a processing example of HMI client device 16.

[0094] exist Figure 6 In step S100, the HMI client device 16 executes the web browser 36. Regardless of the final position and size of the web browser 36, the web browser processing unit 31 displays the web browser 36 on a predetermined monitor 35 with a predetermined initial position and initial size.

[0095] In step S110, each web browser 36 retrieves content from the HMI server device 12. This content includes the aforementioned HTML file, SVG file 25, component library 26, access control table 27, and exception table 28. Furthermore, the component library 26, access control table 27, and exception table 28 are only required to be retrieved upon startup of the web browser 36.

[0096] In steps S120 to S220, the web browser processing unit 31 draws the HMI screen 37 specified in the web browser 36 according to the operation right table 27 and the exception table 28.

[0097] The web browser processing unit 31 refers to the operation right table 27 to determine whether the web browser 36 has the operation right for the HMI screen 37 (step S120). If it has the operation right, it determines whether there is any exception information for the HMI screen 37 in the exception table 28 (step S130). If there is no exception information, the web browser processing unit 31 displays all the operation components on the HMI screen 37 in an operable state (step S140).

[0098] As an example of step S140, this example shows the display of HMI screen 37a (G10) on a web browser 36a (RM1_1). Figure 4 In the operation rights table 27, the web browser 36a (RM1_1) is allowed to operate the HMI screen 37a (G10) (has operation rights). Furthermore, in Figure 5 There are no exceptions for HMI screen 37a (G10) in exception table 28. Therefore, in web browser 36a (RM1_1), all operation buttons on HMI screen 37a (G10) are depicted in an operable state.

[0099] On the other hand, in step S130, if it is determined that there is exception information in the exception table 28 regarding the HMI screen 37, the processing in step S150 is performed. In step S150, the web browser processing unit 31 determines whether the operation of each specific operation component on the HMI screen 37 is possible. The specific operation components that are allowed to operate are depicted in an operable state (step S160). On the other hand, the specific operation components that are not allowed to operate are depicted in an inoperable state (step S170). In addition, operation components that are not defined in the exception table 28 are depicted in an operable state according to the definition in the operation right table 27.

[0100] Back Figure 6Step S120 will be explained further. In step S120, if it is determined that the web browser 36 does not have the right to operate the HMI screen 37, the processing in step S180 is executed. In step S180, it is determined whether there is any exception information for the HMI screen 37 in the exception table 28. If there is no exception information, the web browser processing unit 31 displays all the operating components on the HMI screen 37 as inoperable (step S200).

[0101] As an example of step S200, this example shows the display of HMI screen 37a (G12) on a web browser 36a (RM1_1). Figure 4 In the operation rights table 27, the web browser 36a (RM1_1) does not allow operation of the HMI screen 37a (G12) (it has no operation rights). Therefore, in the web browser 36a (RM1_1), all operation buttons on the HMI screen 37a (G12) are depicted as inoperable.

[0102] On the other hand, in step S180, if it is determined that there is exception information regarding the HMI screen 37 in the exception table 28, the processing in step S190 is executed. In step S190, the web browser processing unit 31 determines whether the operation of each specific operation component on the HMI screen 37 is possible. Specific operation components that are allowed to operate are depicted in an operable state (step S210). On the other hand, specific operation components that are not allowed to operate are depicted in an inoperable state (step S220). In addition, operation components that are not defined in the exception table 28 are depicted in an inoperable state according to the definition in the operation right table 27.

[0103] For example, in Figure 4 In the operation rights table 27, web browser 36a (RM1_1) is not allowed. Figure 2 The operation of the shared HMI screen 17 (G11) (without operation rights), but... Figure 5 Exception table 28 defines exception information regarding shared HMI screen 17 (G11). Therefore, the exception information takes precedence. Figure 5 Exception Table 28 specifies that certain operating components (1_PL, 2_PL) are allowed to operate (have operating rights) on the shared HMI screen 17 (G11). Therefore, in the web browser 36a, the specific operating components (1_PL, 2_PL) on the shared HMI screen 17 (G11) are depicted as operable, while other operating components (including 3_PL) are depicted as inoperable.

[0104] As explained above, if the operation of the HMI screen 37 performed by the web browser 36 is permitted in the operation permission table 27, and the operation of a specific operation component of the HMI screen 37 performed by the web browser 36 is not permitted in the exception table 28, the web browser processing unit 31 will depict the specific operation component as inoperable on the web browser 36, and depict the operation components other than the specific operation component as operable on the web browser 36.

[0105] Furthermore, if the operation of the HMI screen 37 performed by the web browser 36 is not permitted in the operation rights table 27, but the operation of a specific operation component of the HMI screen 37 performed by the web browser 36 is permitted in the exception table 28, the web browser processing unit 31 will depict the specific operation component in an operable state on the web browser 36, and depict operation components other than the specific operation component in an inoperable state on the web browser 36.

[0106] By the way, in the above Figure 6 The flowchart describes the HMI screen 37 when the web browser 36 starts. However, there are also cases where pressing the screen transition button will switch to another HMI screen 37. In this case, the web browser processing unit 31 obtains the HTML file and SVG file 25 related to the other HMI screen 37 from the HMI server device 12 and performs the processing after step S120.

[0107] 4. Effects

[0108] As explained above, according to the SCADA web-based HMI system of this embodiment, in principle, it is possible to assign operation rights to each web browser on an HMI screen unit basis. Therefore, by creating a dedicated HMI screen for each segment and assigning operation rights to the web browsers of each segment's dedicated HMI screen, it is possible to effectively manage the operation rights of thousands of operation signals in a large-scale factory on an HMI screen unit basis.

[0109] Furthermore, it is possible to exceptionally assign operation rights to specific operation components on the HMI screen to each web browser 36 on a per-component basis. Thus, when displaying the same HMI screen using both the first and second segment web browsers, different operation rights can be assigned to specific operation components between the two web browsers. Therefore, it is possible to share a single HMI screen with appropriate operation rights corresponding to each segment.

[0110] 5. Hardware Configuration Example

[0111] Figure 7 This is a block diagram illustrating an example of the hardware configuration of the HMI server device 12 and the HMI client device 16.

[0112] The various processes of the HMI server device 12 described above are implemented by processing circuitry. The processing circuitry is composed of a processor 61, a memory 62, and a network interface 63 connected together. The processor 61 executes various programs stored in the memory 62 to implement the various functions of the HMI server device 12. The memory 62 includes a main storage device and an auxiliary storage device. The memory 62 pre-stores the aforementioned HTML file, SVG file 25, component library 26, operation right table 27, and exception table 28. The network interface 63 is communicatively connected to other devices within the same network via an information LAN 11.

[0113] The various processes of the HMI client device 16 described above are implemented by a processing circuit. The processing circuit is composed of a processor 71, a memory 72, a network interface 73, an input interface 74, and a monitor 35 connected together. The processor 71 executes various programs stored in the memory 72 to realize the various functions of the HMI client device 16. The memory 72 includes a main storage device and an auxiliary storage device. The network interface 73 is communicatively connected to other devices within the same network via an information LAN 11. The input interface 74 is a set of input devices consisting of a keyboard, mouse, touch panel, etc.

[0114] The embodiments of the present invention have been described above, but the present invention is not limited to the above-described embodiments, and can be implemented in various modifications without departing from the spirit of the present invention. In the above embodiments, the number, quantity, amount, range, etc., of each element are mentioned; unless specifically stated or obviously specified in principle, the present invention is not limited to those stated quantities. Furthermore, the structures, etc., described in the above embodiments are not necessarily essential to the present invention unless specifically stated or obviously specified in principle.

[0115] Label Explanation

[0116] 1. Rolled material

[0117] 2 Heating Furnace

[0118] 3. Roughing mill

[0119] 4. Intermediate equipment

[0120] 5 Finishing mill

[0121] 6. Water cooling device

[0122] 7. Coil machine

[0123] 8PLC

[0124] 9 Control LAN

[0125] 10 Computers

[0126] 11 Information LAN

[0127] 12 HMI server devices

[0128] 13 RM Control Panel

[0129] 14 FM console

[0130] 15 DC Control Console

[0131] 16, 16a, 16b, 16c HMI client devices

[0132] 17 Shared HMI screen

[0133] Operating components 18, 19, and 20

[0134] 21 PLC Signal Processing Department

[0135] 22 Web Server Processing Department

[0136] 25 SVG files

[0137] 26 Components Library

[0138] 27. Operational Rights Table

[0139] 28 Exceptions

[0140] Processing circuits 30, 30a, and 30b

[0141] 31, 31a, 31b Web Browser Processing Department

[0142] 32, 32a, 32b Image rendering processing

[0143] 35, 35a, 35b monitors

[0144] 36, 36a, 36b web browsers

[0145] HMI screens 37, 37a, and 37b

[0146] 61 and 71 processors

[0147] 62, 72 memory

[0148] Network interfaces 63 and 73

[0149] 74 Input Interfaces

Claims

1. A SCADA web HMI client device that executes at least one web browser that communicates with a web server, characterized by the SCADA web HMI client device having a processor, a memory, and a monitor; the HMI client device being configured for each of a plurality of sections of an industrial plant; the memory storing image data of an HMI screen for monitoring the industrial plant, screen operation right information that sets, for each web browser, whether or not the HMI screen can be operated, and exception information that sets, for each web browser, whether or not a specific operation component on the HMI screen can be operated, the specific operation component being a part of a plurality of operation components on the HMI screen, received from the web server; the processor being configured to execute the web browser displayed on the monitor; perform screen drawing processing in which, for the specific operation component on the HMI screen, the operability set by the exception information is applied preferentially, for operation components on the HMI screen other than the specific operation component, the operability set by the screen operation right information is applied, and the HMI screen is drawn on the web browser, whereby in the web browser of the HMI client device configured in each of the plurality of sections, the HMI screen corresponding to the equipment of the section can be operated.

2. The SCADA web HMI client device according to claim 1, characterized in that in the screen drawing processing, in a case where the operation of the HMI screen by the web browser is not allowed in the screen operation right information and the operation of the specific operation component by the web browser is allowed in the exception information, the specific operation component is drawn on the web browser in an operable state; operation components on the web browser other than the specific operation component are drawn in an inoperable state.

3. The SCADA web HMI client device according to claim 1 or 2, characterized in that in the screen drawing processing, in a case where the operation of the HMI screen by the web browser is allowed in the screen operation right information and the operation of the specific operation component by the web browser is not allowed in the exception information, the specific operation component is drawn on the web browser in an inoperable state; operation components on the web browser other than the specific operation component are drawn in an operable state.

4. A SCADA web HMI system having an HMI server device that executes a web server and an HMI client device that executes at least one web browser that communicates with the web server, characterized by the HMI server device having a server processor and a server memory; The HMI client device described above is configured for each of a plurality of sections of an industrial plant; The server memory described above stores image data of an HMI screen for monitoring the industrial plant, screen operation right information that sets whether or not the HMI screen can be operated for each web browser, and exception information that sets whether or not a specific operation component on the HMI screen can be operated for each web browser, the specific operation component being a part of a plurality of operation components on the HMI screen; The server processor described above is configured to execute the web server that can transmit the image data, the screen operation right information, and the exception information to the web browser; The HMI client device described above includes a client processor, a client memory, and a monitor; The client memory described above stores the image data, the screen operation right information, and the exception information received from the web server; The client processor described above is configured to, execute the web browser displayed on the monitor; execute a screen drawing process in which the specific operation component on the HMI screen is preferentially applied with the operability set by the exception information, the operation components on the HMI screen other than the specific operation component are applied with the operability set by the screen operation right information, and the HMI screen is drawn on the web browser, whereby the HMI screen corresponding to the device of the section can be operated in the web browser of the HMI client device configured in each of the plurality of sections.

5. The SCADA web HMI system according to claim 4, wherein the screen drawing process, in a case where the operation of the HMI screen by the web browser is not allowed in the screen operation right information and the operation of the specific operation component by the web browser is allowed in the exception information, the specific operation component is drawn on the web browser in an operable state; the operation components on the HMI screen other than the specific operation component are drawn on the web browser in a non-operable state.

6. The SCADA web HMI system according to claim 4 or 5, wherein the screen drawing process, in a case where the operation of the HMI screen by the web browser is allowed in the screen operation right information and the operation of the specific operation component by the web browser is not allowed in the exception information, the specific operation component is drawn on the web browser in a non-operable state; the operation components on the HMI screen other than the specific operation component are drawn on the web browser in an operable state.

Images