WO2023127040A1 - Ｓｃａｄａウェブｈｍｉクライアント装置およびｓｃａｄａウェブｈｍｉシステム - Google Patents

Ｓｃａｄａウェブｈｍｉクライアント装置およびｓｃａｄａウェブｈｍｉシステム Download PDF

Info

Publication number
WO2023127040A1
WO2023127040A1 PCT/JP2021/048631 JP2021048631W WO2023127040A1 WO 2023127040 A1 WO2023127040 A1 WO 2023127040A1 JP 2021048631 W JP2021048631 W JP 2021048631W WO 2023127040 A1 WO2023127040 A1 WO 2023127040A1
Authority
WO
WIPO (PCT)
Prior art keywords
hmi
screen
web browser
web
specific operation
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2021/048631
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
亮 清水
章 野島
伸夫 清水
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Toshiba Mitsubishi Electric Industrial Systems Corp
Original Assignee
Toshiba Mitsubishi Electric Industrial Systems Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Toshiba Mitsubishi Electric Industrial Systems Corp filed Critical Toshiba Mitsubishi Electric Industrial Systems Corp
Priority to US18/260,937 priority Critical patent/US20250076861A1/en
Priority to PCT/JP2021/048631 priority patent/WO2023127040A1/ja
Priority to JP2023511674A priority patent/JP7409559B2/ja
Priority to CN202180088412.3A priority patent/CN116710865B/zh
Priority to TW111127054A priority patent/TWI845989B/zh
Publication of WO2023127040A1 publication Critical patent/WO2023127040A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Program-control systems
    • G05B19/02—Program-control systems electric
    • G05B19/04—Program control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Program control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0428—Safety, monitoring
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/24—Pc safety
    • G05B2219/24215—Scada supervisory control and data acquisition

Definitions

  • This disclosure relates to a SCADA Web HMI client device and a SCADA Web HMI system.
  • SCADA Supervisory Control And Data Acquisition
  • Social infrastructure systems include steel rolling systems, power transmission and transformation systems, water and sewage treatment systems, building management systems, and road systems.
  • SCADA is a type of industrial control system that performs system monitoring, process control, and data collection by computer. SCADA requires responsiveness (real-time capability) matching the processing performance of the system.
  • SCADA generally consists of the following subsystems.
  • HMI Human Machine Interface
  • An HMI is a mechanism that presents monitored device data to an operator and allows the operator to monitor and control the monitored device.
  • Supervisory Control System The supervisory control system is composed of a Programmable Logic Controller (PLC) or the like. The supervisory control system collects data of monitored devices and sends control commands to the monitored devices.
  • PLC Programmable Logic Controller
  • RIO Remote Input Output
  • the remote input/output device connects to a sensor installed in the monitoring target device, converts the signal of the sensor into digital data, and sends the digital data to the supervisory control system.
  • Communication infrastructure The communication infrastructure connects the supervisory control system and remote input/output devices.
  • Patent Literature 1 discloses a system comprising an HMI client device and an HMI server device.
  • the HMI server device transmits the data received from the PLC to the HMI client device.
  • the HMI client device has a computer main body, an input device such as a keyboard and a mouse, and a monitor, and displays one HMI screen on the monitor.
  • Applicants are aware of the documents listed below, including the above documents, as relevant to the present disclosure.
  • the HMI subsystem according to Patent Document 1 described above requires one HMI client device to display one HMI screen. From the viewpoint of reducing cost, installation space, failure rate, and communication load, it is desirable to be able to use multiple HMI screens simultaneously with one HMI client device.
  • an HMI screen can be realized as a web application that operates on a web browser. Therefore, one HMI client device can execute a plurality of web browsers and display an HMI screen on each web browser.
  • a large-scale plant such as a production line of an industrial system is divided into a plurality of sections, each section having an operator's cab (pulpit).
  • Each driver's cab is equipped with an HMI client device that runs a web browser that renders HMI screens.
  • An HMI server device running a web server that communicates with each web browser is located in the electrical room.
  • the web browser of the HMI client device of the first section can operate a dedicated HMI screen related to the equipment of the first section
  • the web browser of the HMI client device of the second section can operate a dedicated HMI screen related to the second section.
  • the operation authority is set for each web browser for each HMI screen. This is because there are several thousands of operation signals in a large-scale plant, and it is impossible to manage the operation right for each operation part on the HMI screen.
  • intermediate equipment may be provided between the first section and the second section.
  • a shared HMI screen is required that includes the outgoing and intermediate equipment of the first section and the incoming equipment of the second section.
  • the shared HMI screen is used by both the first section HMI client device and the second section HMI client device.
  • the operation parts related to the equipment of the first section on the shared HMI screen may be operated, but the operation parts related to the equipment of the second section should not be operated.
  • the operating parts relating to the equipment of the second section may be operated, but the operating parts relating to the equipment of the first section should not be operated.
  • Intermediate facilities may be operated from both sections. Therefore, as for the shared HMI screen, it is not enough to define the operation authority for each HMI screen, and it is necessary to give the appropriate operation authority for each operation part.
  • the present invention has been made to solve the above-mentioned problems. In principle, it is possible to set the operation authority for each web browser for each HMI screen. It is an object of the present invention to provide a SCADA web HMI client device and a SCADA web HMI system that can set the operation authority for each web browser on a per unit basis.
  • the first aspect relates to SCADA Web HMI client devices.
  • the SCADA Web HMI client device runs at least one web browser that communicates with a web server.
  • the SCADA Web HMI client device comprises a processor, memory and monitor.
  • the memory stores image data of an HMI screen for monitoring an industrial plant, screen operating authority information, and exception information received from the web server.
  • the screen operation authority information determines whether or not the HMI screen can be operated for each web browser.
  • the exception information determines whether or not the specific operation part on the HMI screen can be operated for each web browser.
  • the specific operation parts are some of the operation parts on the HMI screen.
  • the processor is configured to execute the web browser displayed on the monitor and a screen rendering process.
  • the screen drawing process preferentially applies the operability determined in the exception information to the specific operation parts on the HMI screen, and performs operations other than the specific operation parts on the HMI screen among the plurality of operation parts on the HMI screen.
  • the HMI screen is drawn on the web browser by applying the operation propriety determined in the screen operation authority information to the parts.
  • a second aspect relates to the SCADA Web HMI system.
  • the SCADA web HMI system comprises an HMI server device running a web server and an HMI client device running at least one web browser communicating with the web server.
  • 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 operating authority information, and exception information.
  • the screen operation authority information determines whether or not the HMI screen can be operated for each web browser.
  • the exception information determines whether or not the specific operation part on the HMI screen can be operated for each web browser.
  • the specific operation parts are some of the operation parts on the HMI screen.
  • the server processor is configured to run the web server capable of transmitting the image data, the screen operation authority information, and the exception 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 authority information, and the exception information received from the web server.
  • the client processor is configured to execute the web browser displayed on the monitor and a screen drawing process.
  • the screen drawing process preferentially applies the operability determined in the exception information to the specific operation parts on the HMI screen, and performs operations other than the specific operation parts on the HMI screen among the plurality of operation parts on the HMI screen.
  • the HMI screen is drawn on the web browser by applying the operation propriety determined in the screen operation authority information to the parts.
  • the operation authority can be set for each web browser for each HMI screen.
  • operation authority can be set for each web browser for each operation part. Therefore, the operation authority of each web browser can be managed efficiently in units of HMI screens, and the operation authority of each web browser can be exceptionally managed in units of operation parts as needed.
  • FIG. 4 is a diagram for explaining an example of a shared HMI screen according to the embodiment
  • FIG. 3 is a block diagram illustrating an overview of functions possessed by an HMI server device and an HMI client device according to the embodiment
  • FIG. It is a figure for demonstrating an example of the operation authority table which concerns on embodiment.
  • 6 is a flowchart for explaining screen drawing processing according to the embodiment
  • 1 is a block diagram showing a hardware configuration example of a SCADA web HMI system according to an embodiment
  • FIG. 1 is a diagram for explaining a configuration example of a hot rolling line according to an embodiment.
  • a metal material to be rolled 1 is thinned while being processed in a hot rolling line, and the size and temperature of the material are controlled to desired target values.
  • the hot rolling line includes a heating furnace 2, a rough rolling mill 3, an intermediate facility 4, a finishing rolling mill 5, a water cooling device 6, a coiler 7, and a roller table (not shown) that conveys the material to be rolled 1 therebetween. ).
  • the heating furnace 2 raises the temperature of the material 1 to be rolled.
  • the heated material 1 to be rolled is extracted onto the roller table.
  • the material to be rolled 1 is a formed mass of metal called a slab.
  • the rough rolling mill 3 is provided downstream of the heating furnace 2 .
  • the roughing mill 3 comprises a single rolling stand or multiple rolling stands.
  • the rough rolling mill 3 rolls the material to be rolled 1 multiple times in the forward direction (from upstream to downstream) and in the reverse direction (from downstream to upstream).
  • the intermediate equipment 4 is provided downstream of the roughing mill 3 .
  • the intermediate equipment 4 includes edge heaters, bar heaters, coil boxes, and the like.
  • the finishing rolling mill 5 is provided downstream of the intermediate equipment 4 .
  • the finishing mill 5 includes a plurality of rolling stands, and rolls the material 1 to be rolled in one direction from upstream to downstream.
  • the finish rolling determines the final quality of the material 1 to be rolled in terms of size such as thickness and width.
  • the water cooling device 6 is provided downstream of the finishing mill 5 .
  • the water cooling device 6 injects water into the rolled material 1 to be rolled.
  • the material to be rolled 1 is cooled to a target temperature by a water cooling device 6 .
  • the coiler 7 is provided downstream of the water cooling device 6.
  • the material to be rolled 1 cooled by the water cooling device 6 is wound around a coiler 7 while being guided downward by pinch rolls to form a coiled product.
  • Each device (2 to 7) described above is connected to the PLC 8 via an electric motor or drive device.
  • the PLC 8 connects to a computer 10 located in the computer room via a control LAN 9 .
  • the computer 10 calculates set values for each device (2 to 7) based on the rolling plan for the material 1 to be rolled, and transmits the set values to the PLC8.
  • the PLC 8 controls each device (2-7) based on the set values.
  • the PLC 8 connects to the HMI server device 12 placed in the electrical room via an information LAN 11 such as Ethernet (registered trademark).
  • the PLC 8 periodically transmits packets containing block data to the information LAN 11 by multicast or broadcast.
  • Block data is a set of PLC signals.
  • One block data includes tens to hundreds of PLC signals.
  • PLC signals include input/output signals (including actuator control signals and sensor detection signals) and alarm signals.
  • the PLC 8 also receives control signals for each device from the HMI server device 12 .
  • a large-scale plant like the hot rolling line mentioned above is divided into multiple sections. Each section has a cab (pulpit).
  • the RM (Roughering Mills) pulpit 13 is the cab of the section with the roughing mill 3 .
  • the FM (Finishing Mills) pulpit 14 is the cab of the section having the finishing mill 5 .
  • a DC (Down Coiler) pulpit 15 is the operator's cab of the section having the coiler 7 .
  • Each cab is equipped with an HMI client device 16 that can operate each HMI screen on a web browser.
  • a dedicated HMI screen for the roughing mill 3 can be operated on the web browser of the HMI client device 16 a of the RM pulpit 13 .
  • the web browser of the HMI client device 16b of the FM pulpit 14 can operate a dedicated HMI screen regarding the finishing mill 5.
  • FIG. A dedicated HMI screen for the coiler 7 can be operated on the web browser of the HMI client device 16 c of the DC pulpit 15 . That is, basically, the operation authority is set for each web browser for each HMI screen. This is because there are several thousands of operation signals in a large-scale plant, and it is impossible to manage the operation right for each operation part on the HMI screen.
  • the HMI client devices (16a, 16b, 16c) are simply referred to as HMI client devices 16 when not distinguished.
  • intermediate equipment 4 is provided between the rough rolling mill 3 and the finishing rolling mill 5 .
  • Shared HMI screen 17 is used by both RM pulpit 13 and FM pulpit 14 .
  • the operating parts 18 related to the roughing mill 3 on the shared HMI screen 17 may be operated, but the operating parts 19 related to the finishing mill 5 should not be operated.
  • the operational parts 19 related to the finishing mill 5 on the shared HMI screen 17 may be operated, but the operational parts 18 related to the roughing mill 3 should not be operated.
  • the operating parts 20 for intermediate equipment 4 may be operated from both pulpits.
  • the intermediate equipment 4 the coil box is operated from the RM pulpit 13 for winding and from the FM pulpit 14 for payout. Therefore, regarding the shared HMI screen 17, it is not enough to just set the operation authority for each HMI screen, and it is necessary to give the appropriate operation authority for each operation part.
  • the operation authority can be set for each web browser for each HMI screen. It was decided that the operation right could be set to
  • FIG. 1 A SCADA Web HMI system according to the present embodiment will be described with reference to FIGS. 3 to 5.
  • FIG. The SCADA web HMI system comprises an HMI server device 12 and an HMI client device 16 interconnected via an information LAN 11 .
  • the HMI server device 12 shown in FIG. 3 transmits and receives PLC signals and control signals to and from the PLC 8, and runs a web server.
  • the HMI server device 12 includes a processor 61 that executes various processes and a memory 62 that stores various information, as shown in FIG. 7, which will be described later.
  • the processor 61 executes the programs stored in the memory 62 so that the processor 61 functions as the PLC signal processing section 21 and the web server processing section 22 .
  • the PLC signal processing unit 21 and the web server processing unit 22 can mutually transmit and receive data through inter-process communication.
  • the PLC signal processing unit 21 periodically transmits the PLC signal received from the PLC 8 to each web browser 36 (web browser processing unit 31) via the web server processing unit 22. Also, the PLC signal processing unit 21 transmits control signals received from each web browser 36 via the web server processing unit 22 to the PLC 8 .
  • the web server processing unit 22 can communicate with the web browser 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 transmits content in response to requests from each web browser 36 (web browser processing unit 31).
  • Contents include HTML files (not shown), SVG (Scalable Vector Graphics) files 25 that are image data for each HMI screen, parts library 26 that describes operations for each part type, operation authority table 27, and exception table. 28.
  • the parts library 26 contains a set of scripts describing actions for each part type.
  • a script is a JavaScript (registered trademark) program defined for each part type.
  • the script can be executed on each web browser 36 given parameter values (for example, presence or absence of operation authority defined in the operation authority table 27 and the exception table 28) as necessary.
  • the operation authority table 27 indicates, for each web browser 36, whether or not each HMI screen 37 can be operated (whether there is an operation authority (whether operation is permitted) or whether there is no operation authority (whether operation is permitted)). Includes defined screen operation right information.
  • FIG. 4 is a diagram showing an example of the operation authority table 27.
  • “G10” to “G13” are screen names of the respective HMI screens 37 .
  • “RM1_1” is the browser name of the first web browser 36a executed by the HMI client device 16a.
  • “RM1_2” is the browser name of the second web browser (not shown) executed by the HMI client device 16a.
  • “FM1_1” is the browser name of the first web browser 36b executed by the HMI client device 16b
  • “FM1_2” is the browser name of the second web browser (not shown) executed by the HMI client device 16a.
  • the browser name is a combination of the device name of the computer and the monitor number.
  • the web browser 36a (RM1_1) has the right to operate the HMI screen 37a (G10)
  • the web browser 36b (FM1_1) does not have the right to operate the HMI screen 37b (G10).
  • the operation authority is set for each HMI screen as defined in the operation authority table 27. Exceptionally, it is necessary to set the operation authority for each operation part.
  • the exception table 28 indicates, for each web browser 36, whether or not the specific operation part on each HMI screen 37 can be operated (whether there is an operation right (whether the operation is permitted) or whether there is no operation right (whether the operation is permitted). or))).
  • a specific operation part is a part of the operation parts on the HMI screen 37 .
  • FIG. 5 is a diagram showing an example of the exception table 28.
  • FIG. “G11” is the screen name of the shared HMI screen 17 (FIG. 2), which is one of the HMI screens 37 . All web browsers 36 are not permitted to operate the shared HMI screen 17 (G11) in the operation right table 27 (FIG. 4). However, for the specific operation parts (1_PL, 2_PL, 3_PL) on the shared HMI screen 17 (G11), the exception table 28 sets the operation authority for each operation part.
  • the web browser 36a (RM1_1) has the right to operate the operational parts 18 (1_PL) and 19 (3_PL), but does not have the right to operate the operational part 20 (2_PL).
  • the web browser 36b (FM1_1) has the right to operate the operational parts 20 (3_PL) and 19 (3_PL), but does not have the right to operate the operational part 18 (1_PL).
  • the HMI client device 16 (16a, 16b) includes a processing circuit 30 (30a, 30b) (including a processor 71 for executing various processes and a memory 72 for storing various information shown in FIG. 7 described later), a monitor 35 ( 35a, 35b).
  • the processor 71 functions as the web browser processing section 31 (31a, 31b).
  • the reference numerals 30a to 37a and the reference numerals 30b to 37b are not distinguished, they are simply referred to as 30 to 37.
  • the web browser processing unit 31 is executed for each web browser 36.
  • a web browser 36 renders an HMI screen 37 for monitoring and controlling the industrial plant.
  • the HMI screen 37 is switched to another HMI screen 37 by operator's operation.
  • a plurality of parts are arranged on the HMI screen 37 .
  • the parts include, for example, operation parts for transmitting control signals to the PLC 8 according to operator's operations, display parts whose display state (numerical value, character, color, shape) changes according to the received PLC signal, and other HMI Including screen transition parts for switching between screens.
  • Each web browser 36 receives the above-described HTML file, SVG file 25, parts library 26, operation authority table 27, exception table 28, and the like from the web server processing unit 22 at startup, and memorize to Based on these, the web browser 36 renders the HMI screen 37 on which the parts are arranged. Also, each web browser 36 is executed in a cache-free mode so as to always obtain the latest files from the web server processing unit 22 when activated.
  • the web browser processing unit 31 reads the operation authority table 27 received from the HMI server device 12 and determines whether or not each HMI screen 37 can be operated (whether or not there is an operation authority) for each web browser 36 .
  • the web browser processing unit 31 also reads the exception table 28 received from the HMI server device 12 and determines whether or not the specific operation button on the HMI screen 37 (shared HMI screen 17) can be operated for each web browser 36.
  • the web browser processing unit 31 executes screen drawing processing 32 .
  • the screen drawing process 32 preferentially applies the operability defined in the exception table 28 to the specific operation parts on the HMI screen 37, and the operation parts other than the specific operation parts among the operation parts on the HMI screen 37 are:
  • the HMI screen 37 is drawn on the web browser 36 by applying the operation propriety defined in the operation authority table 27 .
  • the web browser processing unit 31 executes a script for each part type included in the parts library 26 described above, according to the part type of the parts arranged on the HMI screen 37 .
  • the parts types operation parts whose actions change according to the presence or absence of the operation authority (parameter value) passed to the script will be described.
  • operation parts if the web browser 36 is not permitted to operate the HMI screen 37 in the operation authority table 27, in principle, all the operation parts arranged on the HMI screen 37 of the web browser 36 are rendered in an inoperable state. be. Further, when the operation authority table 27 permits the web browser 36 to operate the HMI screen 37, in principle, all the operation parts arranged on the HMI screen 37 of the web browser 36 are drawn in an operable state.
  • the exception table 28 defines operation rights for specific operation parts of a specific HMI screen 37 (shared HMI screen 17)
  • the operation rights defined in the exception table 28 are preferentially applied to the specific operation parts. be done.
  • the operation authority defined in the operation authority table 27 is applied.
  • the operation parts do not accept the operator's execution operations (for example, mouse clicks).
  • the operation part accepts an operator's execution operation and transmits a control signal corresponding to the operation to the HMI server device 12 .
  • FIGS. 4 to 6 the drawing of the HMI screen 37 in each web browser 36 according to the presence or absence of the operation right will be specifically described.
  • FIG. 4 is a diagram showing an example of the operation authority table 27 described above.
  • FIG. 5 is a diagram showing an example of the exception table 28 described above.
  • FIG. 6 is a flow chart for explaining a processing example of the HMI client device 16. As shown in FIG.
  • step S100 of FIG. 6 the HMI client device 16 executes the web browser 36.
  • the web browser processing unit 31 displays the web browser 36 on the default monitor 35 at a predetermined initial position and initial size regardless of the position and size when the web browser 36 is terminated.
  • each web browser 36 acquires content from the HMI server device 12.
  • the contents include the HTML file, SVG file 25, parts library 26, operation authority table 27, and exception table 28 described above.
  • the parts library 26, the operation right table 27, and the exception table 28 need only be obtained when the web browser 36 is activated.
  • the web browser processing unit 31 draws the HMI screen 37 specified by the web browser 36 according to the operation authority table 27 and the exception table 28.
  • the web browser processing unit 31 refers to the operation authority table 27 and determines whether or not the web browser 36 has the authority to operate the HMI screen 37 (step S120). If there is the operation right, it is determined whether or not there is 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 draws all the operation parts on the HMI screen 37 in an operable state (step S140).
  • step S140 an example of displaying the HMI screen 37a (G10) on the web browser 36a (RM1_1) is shown.
  • the web browser 36a (RM1_1) is permitted to operate the HMI screen 37a (G10) (with operation authority).
  • Exception table 28 in FIG. 5 does not include exception information for HMI screen 37a (G10). Therefore, all operation buttons on the HMI screen 37a (G10) are drawn in the operable state on the web browser 36a (RM1_1).
  • step S150 determines whether each specific operation part on the HMI screen 37 can be operated. Specific operation parts that are permitted to be operated are drawn in an operable state (step S160). On the other hand, the specific operation parts that are not permitted to be operated are drawn in an inoperable state (step S170). Operation parts that are not defined in the exception table 28 are rendered in an operable state according to the definition in the operation authority table 27 .
  • step S180 it is determined whether or not there is exception information for the HMI screen 37 in the exception table . If there is no exception information, the web browser processing unit 31 renders all the operation parts on the HMI screen 37 in an inoperable state (step S200).
  • step S200 an example of displaying the HMI screen 37a (G12) on the web browser 36a (RM1_1) is shown.
  • the web browser 36a (RM1_1) is not permitted to operate the HMI screen 37a (G12) (no operation authority). Therefore, all the operation buttons on the HMI screen 37a (G12) are rendered in an inoperable state on the web browser 36a (RM1_1).
  • step S190 determines whether each specific operation part on the HMI screen 37 can be operated.
  • a specific operation part that is permitted to be operated is drawn in an operable state (step S210).
  • the specific operation parts that are not permitted to be operated are drawn in an inoperable state (step S220).
  • Operation parts not defined in the exception table 28 are rendered in an inoperable state according to the definition of the operation authority table 27 .
  • the Web browser 36a (RM1_1) is not permitted to operate the shared HMI screen 17 (G11) in FIG. defines exception information about the shared HMI screen 17 (G11). Therefore, exception information is preferentially applied.
  • operation of the specific operation parts (1_PL, 2_PL) is permitted (with operation right) for the shared HMI screen 17 (G11). Therefore, in the web browser 36a, the specific operation parts (1_PL, 2_PL) on the shared HMI screen 17 (G11) are drawn in an operable state, and the other operation parts (including 3_PL) are drawn in an inoperable state. .
  • the web browser processing unit 31 allows the operation of the HMI screen 37 by the web browser 36 in the operation authority table 27, and allows the operation of the HMI screen 37 by the web browser 36 in the exception table 28. is not permitted, the specific operation parts are drawn in the web browser 36 in an inoperable state, and the operation parts other than the specific operation parts are drawn in the web browser 36 in an operable state.
  • the web browser processing unit 31 determines that the web browser 36 is not permitted to operate the HMI screen 37 in the operation authority table 27 and that the web browser 36 is permitted to operate specific operation parts of the HMI screen 37 in the exception table 28. If so, the specific operation parts are drawn in the web browser 36 in an operable state, and the other operation parts are drawn in the web browser 36 in an inoperable state.
  • the rendering of the HMI screen 37 when the web browser 36 is activated has been described.
  • the screen transition button may be pressed to transition to another HMI screen 37 .
  • the web browser processing unit 31 newly acquires the HTML file and SVG file 25 related to the other HMI screen 37 from the HMI server device 12, and executes the processes from step S120.
  • the operation authority can be set for each web browser for each HMI screen. According to this, by creating a dedicated HMI screen for each section and setting the operation authority of the dedicated HMI screen to the web browser of each section, the operation authority of thousands of operation signals of a large-scale plant can be displayed on the HMI screen. Efficient management in units. As an exception, for specific operation parts on the HMI screen, the operation authority can be set for each web browser 36 for each operation part. According to this, when the same HMI screen is displayed by the web browser of the first section and the web browser of the second section, the web browser of the first section and the web browser of the second section have different operation rights for the specific operation parts. can be set. Therefore, one HMI screen can be shared with an appropriate operation right according to the section.
  • FIG. 7 is a block diagram showing a hardware configuration example of the HMI server device 12 and the HMI client device 16. As shown in FIG.
  • Each process of the HMI server device 12 described above is realized by a processing circuit.
  • the processing circuit is configured by connecting a processor 61 , a memory 62 and a network interface 63 .
  • the processor 61 implements each function of the HMI server device 12 by executing various programs stored in the memory 62 .
  • Memory 62 includes a main memory and an auxiliary memory.
  • the memory 62 stores in advance the HTML file, the SVG file 25, the parts library 26, the operation authority table 27, and the exception table 28 described above.
  • the network interface 63 is communicably connected to other devices within the same network via the information LAN 11 .
  • Each process of the HMI client device 16 described above is realized by a processing circuit.
  • the processing circuit is configured by connecting a processor 71, a memory 72, a network interface 73, an input interface 74, and a monitor .
  • the processor 71 realizes each function of the HMI client device 16 by executing various programs stored in the memory 72 .
  • Memory 72 includes a main memory and an auxiliary memory.
  • the network interface 73 is communicably connected to other devices within the same network via the information LAN 11 .
  • the input interface 74 is a set of input devices including a keyboard, mouse, touch panel, and the like.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • User Interface Of Digital Computer (AREA)
  • Testing And Monitoring For Control Systems (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)
PCT/JP2021/048631 2021-12-27 2021-12-27 Ｓｃａｄａウェブｈｍｉクライアント装置およびｓｃａｄａウェブｈｍｉシステム Ceased WO2023127040A1 (ja)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US18/260,937 US20250076861A1 (en) 2021-12-27 2021-12-27 Scada web hmi client apparatus and scada web hmi system
PCT/JP2021/048631 WO2023127040A1 (ja) 2021-12-27 2021-12-27 Ｓｃａｄａウェブｈｍｉクライアント装置およびｓｃａｄａウェブｈｍｉシステム
JP2023511674A JP7409559B2 (ja) 2021-12-27 2021-12-27 Ｓｃａｄａウェブｈｍｉクライアント装置およびｓｃａｄａウェブｈｍｉシステム
CN202180088412.3A CN116710865B (zh) 2021-12-27 2021-12-27 Scada网页hmi客户端装置及scada网页hmi系统
TW111127054A TWI845989B (zh) 2021-12-27 2022-07-19 Scada web hmi 用戶端裝置及scada web hmi 系統

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/048631 WO2023127040A1 (ja) 2021-12-27 2021-12-27 Ｓｃａｄａウェブｈｍｉクライアント装置およびｓｃａｄａウェブｈｍｉシステム

Publications (1)

Publication Number Publication Date
WO2023127040A1 true WO2023127040A1 (ja) 2023-07-06

Family

ID=86998338

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/048631 Ceased WO2023127040A1 (ja) 2021-12-27 2021-12-27 Ｓｃａｄａウェブｈｍｉクライアント装置およびｓｃａｄａウェブｈｍｉシステム

Country Status (5)

Country Link
US (1) US20250076861A1 (https=)
JP (1) JP7409559B2 (https=)
CN (1) CN116710865B (https=)
TW (1) TWI845989B (https=)
WO (1) WO2023127040A1 (https=)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPWO2025032635A1 (https=) * 2023-08-04 2025-02-13
TWI913757B (zh) 2023-12-20 2026-02-01 日商Ｔｍｅｉｃ股份有限公司 基於網路的ｈｍｉ子系統及用戶端安裝器

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS6344202A (ja) * 1986-08-11 1988-02-25 Toshiba Corp プラント運転装置
JP2010020600A (ja) * 2008-07-11 2010-01-28 Digital Electronics Corp 制御システム
WO2014020754A1 (ja) * 2012-08-03 2014-02-06 東芝三菱電機産業システム株式会社 プラント制御監視システム
JP2021022071A (ja) * 2019-07-25 2021-02-18 東芝三菱電機産業システム株式会社 Ｓｃａｄａウェブｈｍｉサーバ装置

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2851914B2 (ja) * 1990-04-24 1999-01-27 株式会社日立製作所 オペレータズコンソール用表示装置
JP2003023676A (ja) * 2001-07-10 2003-01-24 Hitachi Ltd 遠隔操作システム
US7925611B1 (en) * 2003-09-25 2011-04-12 Rockwell Automation Technologies, Inc. Graphical user interface
JP2006155522A (ja) * 2004-12-01 2006-06-15 Canon Inc Ｗｅｂブラウザの操作方法及び操作装置
US8817021B1 (en) * 2011-11-11 2014-08-26 Google Inc. System for writing, interpreting, and translating three-dimensional (3D) scenes
TW201349133A (zh) * 2012-07-17 2013-12-01 Ege Technology Co Ltd 雲端控制門禁管理系統及其認證方法
JP6281175B2 (ja) * 2012-12-07 2018-02-21 株式会社ジェイテクト Ｐｌｃ通信システム
DE112014006838T5 (de) * 2014-07-29 2017-04-20 Mitsubishi Electric Corporation Anzeigenbetriebssystem
JP6157548B2 (ja) * 2015-09-25 2017-07-05 株式会社コンテック 監視画像の作成装置、作成プログラムおよび作成方法
US9923993B2 (en) * 2015-11-02 2018-03-20 Rockwell Automation Technologies, Inc. Self-describing diagnostic data for presentation on mobile devices
JP6578901B2 (ja) * 2015-11-13 2019-09-25 株式会社デンソー 表示制御装置
US20180059921A1 (en) * 2016-09-01 2018-03-01 Honeywell International Inc. Custom gui control for visualizing field data
WO2018087864A1 (ja) * 2016-11-10 2018-05-17 三菱電機株式会社 情報表示装置及び情報表示システム並びに表示画面制御方法
JP7064991B2 (ja) * 2018-07-30 2022-05-11 三菱重工業株式会社 燃料プールおよび燃料プールのライニング施工方法
CN109068071A (zh) * 2018-09-18 2018-12-21 爱普（福建）科技有限公司 基于Web的工程画面的编辑系统
JP6552775B1 (ja) * 2018-10-31 2019-07-31 東芝三菱電機産業システム株式会社 ハイブリッドレンダリングｈｍｉ端末装置
WO2020090033A1 (ja) * 2018-10-31 2020-05-07 東芝三菱電機産業システム株式会社 ＳＣＡＤＡ Ｗｅｂ ＨＭＩシステム
JP7161954B2 (ja) * 2019-02-01 2022-10-27 株式会社荏原製作所 制御システム、制御システムのプログラムを記録した記録媒体、および制御システムの方法
CN111949904B (zh) * 2019-05-16 2024-06-11 深圳市雅阅科技有限公司 一种基于浏览器的数据处理方法、装置以及终端
JP7245741B2 (ja) * 2019-07-25 2023-03-24 東芝三菱電機産業システム株式会社 Ｓｃａｄａウェブｈｍｉサーバおよびｓｃａｄａウェブｈｍｉシステム
CN116034338A (zh) * 2021-07-07 2023-04-28 东芝三菱电机产业系统株式会社 Scada网页hmi系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS6344202A (ja) * 1986-08-11 1988-02-25 Toshiba Corp プラント運転装置
JP2010020600A (ja) * 2008-07-11 2010-01-28 Digital Electronics Corp 制御システム
WO2014020754A1 (ja) * 2012-08-03 2014-02-06 東芝三菱電機産業システム株式会社 プラント制御監視システム
JP2021022071A (ja) * 2019-07-25 2021-02-18 東芝三菱電機産業システム株式会社 Ｓｃａｄａウェブｈｍｉサーバ装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPWO2025032635A1 (https=) * 2023-08-04 2025-02-13
WO2025032635A1 (ja) * 2023-08-04 2025-02-13 株式会社Tmeic Ｓｃａｄａウェブｈｍｉシステム
JP7736209B2 (ja) 2023-08-04 2025-09-09 株式会社Tmeic Ｓｃａｄａウェブｈｍｉシステム
TWI913757B (zh) 2023-12-20 2026-02-01 日商Ｔｍｅｉｃ股份有限公司 基於網路的ｈｍｉ子系統及用戶端安裝器

Also Published As

Publication number Publication date
CN116710865A (zh) 2023-09-05
US20250076861A1 (en) 2025-03-06
JPWO2023127040A1 (https=) 2023-07-06
JP7409559B2 (ja) 2024-01-09
TW202326326A (zh) 2023-07-01
CN116710865B (zh) 2026-01-30
TWI845989B (zh) 2024-06-21

Similar Documents

Publication Publication Date Title
TWI732633B (zh) Ｓｃａｄａ網路ｈｍｉ伺服器及ｓｃａｄａ網路ｈｍｉ系統
JP7409559B2 (ja) Ｓｃａｄａウェブｈｍｉクライアント装置およびｓｃａｄａウェブｈｍｉシステム
TWI853271B (zh) Scada web hmi用戶裝置及scada web hmi系統
CN104508583A (zh) 工厂控制监视系统
DE10105668B4 (de) Internet-Inline-Steuereinrichtung für eine Strickmaschine
JP7736209B2 (ja) Ｓｃａｄａウェブｈｍｉシステム
TWI827482B (zh) Ｓｃａｄａ網頁ｈｍｉ用戶裝置及ｓｃａｄａ網頁ｈｍｉ系統
JPWO2023281663A5 (https=)
JPWO2025032635A5 (https=)
EP4062240B1 (de) Fernsteuerung einer anlage zum herstellen und/oder behandeln eines walzguts aus metall
KR102379794B1 (ko) 압연 조업 지원 시스템
DE102012224255A1 (de) Werkssicherheits-Verwaltungsvorrichtung, Verwaltungsverfahren und Verwaltungsprogramm
JP2005055965A (ja) プラント状態監視方法及びプラント監視装置
AT501786B1 (de) Steuereinrichtung für eine spritzgiessmaschine
JP2012027809A (ja) 監視制御装置
DE112014007121B4 (de) Anlagensystem und Steuerungsvorrichtung
CN211653492U (zh) 一种棒材生产线集控系统
JP7477402B2 (ja) 制御装置および方法
JP3394837B2 (ja) 圧延機の制御方法
EP1390821A2 (de) Verfahren zur führung eines stahlverarbeitungsprozesses, insbesondere eines warmwalzprozesses
JPH05244668A (ja) 時刻同期型遠方監視制御装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2023511674

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202317043045

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 202180088412.3

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 18260937

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 12023551927

Country of ref document: PH

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21969924

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21969924

Country of ref document: EP

Kind code of ref document: A1

WWP Wipo information: published in national office

Ref document number: 18260937

Country of ref document: US