WO2025032635A1 - Ｓｃａｄａウェブｈｍｉシステム - Google Patents

Ｓｃａｄａウェブｈｍｉシステム Download PDF

Info

Publication number
WO2025032635A1
WO2025032635A1 PCT/JP2023/028568 JP2023028568W WO2025032635A1 WO 2025032635 A1 WO2025032635 A1 WO 2025032635A1 JP 2023028568 W JP2023028568 W JP 2023028568W WO 2025032635 A1 WO2025032635 A1 WO 2025032635A1
Authority
WO
WIPO (PCT)
Prior art keywords
hmi
screen
web browser
web
client device
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.)
Pending
Application number
PCT/JP2023/028568
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.)
TMEIC Corp
Original Assignee
TMEIC 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 TMEIC Corp filed Critical TMEIC Corp
Priority to JP2024549742A priority Critical patent/JP7736209B2/ja
Priority to PCT/JP2023/028568 priority patent/WO2025032635A1/ja
Priority to CN202380058560.XA priority patent/CN119790358A/zh
Priority to TW112146115A priority patent/TWI885608B/zh
Publication of WO2025032635A1 publication Critical patent/WO2025032635A1/ja
Anticipated expiration legal-status Critical
Pending 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

Definitions

  • This disclosure relates to 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 sewerage treatment systems, building management systems, road systems, etc.
  • SCADA is a type of industrial control system that uses computers to monitor systems, control processes, and collect data. SCADA requires responsiveness (real-time performance) that matches the processing performance of the system.
  • SCADA has the following subsystems: HMI (Human Machine Interface), monitoring and control system, remote input/output device (RIO), and communications infrastructure.
  • HMI Human Machine Interface
  • RIO remote input/output device
  • HMI is a mechanism that presents data from monitored devices to an operator, enabling the operator to monitor and control the monitored devices.
  • a monitoring and control system is composed of devices such as Programmable Logic Controllers (PLCs).
  • PLCs Programmable Logic Controllers
  • the monitoring and control system collects data from monitored devices and sends control commands to the monitored devices.
  • the remote input/output device connects to sensors installed in the monitored devices, converts the sensor signals into digital data, and sends the digital data to the monitoring and control system.
  • the communications infrastructure connects the monitoring and control system to the remote input/output devices.
  • Patent Document 1 discloses a system that includes an HMI client device and an HMI server device.
  • the HMI server device transmits data received from a PLC to the HMI client device.
  • the HMI client device has a computer main body, input devices such as a keyboard and mouse, and a monitor, and displays one HMI screen on the monitor.
  • Patent Document 2 below as being related to the present disclosure.
  • one HMI client device is required to display one HMI screen. From the perspective of reducing costs, installation space, failure rates, and communication load, it is desirable to be able to use multiple HMI screens simultaneously with one HMI client device.
  • a browser-based SCADA HMI subsystem to a production line in an industrial plant.
  • the production line is divided into multiple sections, with an operator's cab (pulpit) provided for each section.
  • an HMI client device is placed that runs a web browser that displays the HMI screen.
  • an HMI server device is placed that runs a web server that communicates with each web browser.
  • the web browser of the HMI client device in the first section should be able to operate the HMI screen related to the equipment in the first section
  • the web browser of the HMI client device in the second section should be able to operate the HMI screen related to the equipment in the second section.
  • the basic principle is to set operation rights for each HMI screen displayed in the web browser of each HMI client device according to the operating location of the HMI client device, i.e. according to the section in which the HMI client device is installed.
  • the purpose of this disclosure is to provide a SCADA web HMI system that is based on the function of setting operation rights for each HMI screen according to the operating location of the HMI client device, and that is capable of setting operation rights for each HMI screen according to the operator's job duties.
  • the first aspect relates to a SCADA web HMI system.
  • the SCADA web HMI system includes an HMI server device that executes a web server, and a plurality of HMI client devices that execute at least one web browser that communicates with the web server.
  • the HMI server device includes 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 part operation right information.
  • the screen operation right information determines whether or not an HMI screen can be operated for each HMI screen displayed in the web browser depending on the operation location of the HMI client device.
  • the part operation right information determines whether or not a specific operation part, which is a part of a plurality of operation parts on an HMI screen, can be operated for each HMI screen displayed in the web browser depending on the job of an operator of the HMI client device.
  • the server processor is configured to execute the web server that can transmit image data, screen operation right information, and part operation right information to the web 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 part operation right information received from the web server.
  • the client processor is configured to execute a web browser displayed on the monitor and a screen drawing process.
  • the screen drawing process applies the operation permission defined in the screen operation right information to multiple operation parts on the HMI screen, and also applies the operation permission defined in the part operation right information according to the job to specific operation parts on the HMI screen with priority, thereby drawing the HMI screen on the web browser.
  • the second viewpoint has the following features in addition to those of the first viewpoint.
  • the screen operation right information further determines whether the HMI screen can be operated for each HMI screen displayed in the web browser, depending on the job of the operator of the HMI client device.
  • the part operation right information further determines whether a specific operation part, which is a part of multiple operation parts on the HMI screen, can be operated for each HMI screen displayed in the web browser, depending on the operation location of the HMI client device.
  • the third viewpoint has the following feature in addition to the first or second viewpoint:
  • the screen drawing process draws the specific operation part in an inoperable state on the web browser and draws operation parts of the multiple operation parts other than the specific operation part in an operable state on the web browser.
  • the fourth viewpoint has the following feature in addition to the first or second viewpoint:
  • the screen drawing process draws the specific operation part in an operable state on the web browser, and draws operation parts of the multiple operation parts other than the specific operation part in an inoperable state on the web browser.
  • the operation permission defined in the screen operation right information is applied to multiple operation parts on the HMI screen, and the operation permission defined in the part operation right information according to job function is applied preferentially to specific operation parts on the HMI screen. Therefore, operation rights are set for each HMI screen according to the operation location of the HMI client device, and operation rights for specific operation parts on the HMI screen are set preferentially for each HMI screen according to the job of the operator. This allows more detailed operation rights to be set for each HMI screen, preventing the safety of the monitored plant from being compromised.
  • FIG. 1 is a diagram for explaining a configuration example of a hot rolling line to which a SCADA web HMI system according to an embodiment is applied; 1 is a block diagram illustrating an example of an overview of functions of an HMI server device and an HMI client device that constitute a SCADA web HMI system.
  • FIG. 2A is a diagram showing an example of an HMI screen related to a roughing mill
  • FIG. 2B is a diagram showing an example of an HMI screen related to a finishing mill.
  • FIG. 13 is a diagram showing an example of a screen operation authority (operation location) table.
  • FIG. 13 is a diagram showing an example of a screen operation authority (job) table.
  • FIG. 13 is a diagram showing an example of a part operating right (operating place) table.
  • FIG. 13 is a diagram showing an example of a parts operation right (job) table.
  • 11 is a flowchart illustrating a screen drawing process according to an embodiment.
  • 1 is a block diagram showing an example of a hardware configuration of a SCADA web HMI system according to an embodiment;
  • the hot rolling line RL is an example of a production line in an industrial system. Note that elements that are common to each figure will be given the same reference numerals and duplicate explanations will be omitted.
  • FIG. 1 is a diagram for explaining an example of the configuration of a hot rolling line RL to which a SCADA web HMI system 1 according to an embodiment is applied.
  • FIG. 2 is a block diagram illustrating an example of the functions of an HMI server device and an HMI client device that constitute the SCADA web HMI system.
  • FIG. 3(a) is a diagram showing an example of an HMI screen related to a roughing mill
  • FIG. 3(b) is a diagram showing an example of an HMI screen related to a finishing mill.
  • the hot rolling line RL rolls the material Mr, such as a metal material, to the desired thickness and width.
  • the hot rolling line RL is equipped with the following equipment: 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 Mr between them.
  • the heating furnace 2 heats the material to be rolled Mr.
  • the heated material to be rolled 1 is extracted onto a roller table.
  • the extracted material to be rolled Mr is a formed block of metal 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 material to be rolled Mr multiple times in the forward direction (from upstream to downstream) and reverse direction (from downstream to upstream).
  • 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 multiple rolling stands (eight in this embodiment). The finishing mill 5 rolls the rolled material Mr in one direction from upstream to downstream.
  • the water cooling device 6 is provided downstream of the finishing rolling mill 5.
  • the water cooling device 6 injects water into the rolled material Mr to cool it 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 wound by the coiler 7 to become a coiled product.
  • Each of the equipment 2-7 described above has an actuator such as an electric motor or a drive device.
  • various sensors (not shown) are provided as measuring devices at key points in the rolling line RL. The various sensors sequentially measure the state of the rolled material Mr and each of the equipment 2-7.
  • These actuators and sensors are connected to the PLC 8 via a control LAN 91.
  • the PLC 8 is connected to a computer 10 arranged in a computer room via the control LAN 91.
  • the computer 10 calculates the setting values for each of the equipment 2-7 based on the rolling plan for the rolled material Mr and transmits the setting values to the PLC 8.
  • the PLC 8 controls the actuators of each of the equipment 2-7 based on the setting values received from the computer 10 and the control signals received from the HMI client device 12 described later via the HMI server device 11.
  • the SCADA Web HMI system 1 comprises the PLC 8, an HMI server device 11 located in the electrical room, and an HMI client device 12.
  • the PLC 8, HMI server device 11, and HMI client device 12 are connected via an information LAN 92 such as Ethernet (registered trademark).
  • the PLC 8 periodically transmits packets including block data to the information LAN 92 by multicast or broadcast.
  • Block data is a collection of PLC signals.
  • One block data contains tens to hundreds of PLC signals.
  • the PLC signals include input/output signals and alarm signals.
  • the input/output signals are generated by the operation of the HMI client device 12, and include control signals for controlling the actuators of each piece of equipment 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”).
  • the PLC 8 receives the above control signals, which are generated by the operation of operation parts on the HMI screen 17 (described later) of the HMI client device 12, from the HMI server device 11.
  • the hot rolling line RL is divided into multiple sections (two in this embodiment) corresponding to the equipment 2 to 7. Each section has an operator's cab (pulpit).
  • the section having the roughing mill 3 has an RM (Roughing Mills) operator's cab 13.
  • the section having the finishing mill 5 has an FM (Finishing Mills) operator's cab 14.
  • the number of sections and operator's cabs may each be three or more.
  • Each cab 13, 14 is equipped 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 the HMI screen 17a, 17b is displayed on the displayed web browser 16a, 16b.
  • the reference numbers 12a, 15a to 17a and the reference numbers 12b, 15b to 17b they will simply be referred to as 12, 15 to 17.
  • the HMI client device 12a in the RM cab 13 displays an HMI screen 17a related to the roughing mill 3 on a web browser 16a, and allows the user to operate the displayed HMI screen 17a (specifically, at least one part displayed on the HMI screen 17a).
  • This HMI client device 12a can also execute a web browser 16b and display other HMI screens 17b on the web browser 16b, but in principle, it is required that the HMI screen 17b be inoperable.
  • the HMI client device 12b in the FM cab 14 displays an HMI screen 17b related to the finishing mill 5 on a web browser 16b, and allows the user to operate the displayed HMI screen 17b.
  • This HMI client device 12b can also execute a web browser 16a and display other HMI screens 17a on the web browser 16a, but in principle, it is required that the HMI screen 17a be inoperable. Therefore, in this embodiment, the screen operation authority (operation location) table 25 shown in FIG. 4, which will be described later, is used to set the screen operation authority for each HMI screen 17 (G10, G11, G11) according to the operation location of the HMI client device 12.
  • the duties of the multiple operators who operate the HMI client device 12 are not necessarily the same, and the duties of the multiple operators may be different.
  • the duties include an operator who performs manual operations (manual intervention) on equipment, and a facility manager who performs maintenance including repairs to equipment and replacement of components.
  • the screen operation rights (duties) table 26 shown in FIG. 5, which will be described later, is used to set the screen operation rights for each HMI screen 17 (G10, G11, G11) according to the duties of the operator who logged in to the HMI client device 12.
  • the operation rights (operation possibility) of specific operation parts based on the operation location are set using a part operation rights (operation location) table 27 shown in Figure 6, which will be described later.
  • different operators may operate the same HMI screen 17.
  • specific operation parts for performing manual operations can be operated by operators but not by equipment personnel.
  • specific operation parts for performing maintenance such as roll replacement can be operated by equipment personnel but not by operators. Therefore, in this embodiment, the operation rights (operational ability) of specific operation parts by job are set using the part operation rights (job) table 28 shown in Figure 7, which will be described later.
  • the HMI server device 11 shown in FIG. 2 transmits and receives PLC signals to and from the PLC 8, and also runs a web server.
  • the HMI server device 11 has a processor 111 that executes various processes, and a memory 112 in which various information is stored.
  • the processor 111 and the memory 112 correspond to the server processor and server memory, respectively, in the claims.
  • the processor 111 executes a program stored in the memory 112, causing the processor 111 to function 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 transmit and receive data to and from each other through inter-process communication.
  • the PLC signal processing unit 21 periodically receives a PLC signal including a sensor detection signal from the PLC 8, and transmits the received PLC signal to the web browser processing unit 31 (each web browser 16) via the web server processing unit 22.
  • the PLC signal processing unit 21 also 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 transmits the received PLC signal to the PLC 8.
  • the web server processing unit 22 can communicate with the web browser 16 (web browser processing unit 31) of each HMI client device 12 using HTTP (Hypertext Transfer Protocol), HTTPS (Hypertext Transfer Protocol Secure), and WebSocket.
  • the web server processing unit 22 transmits 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 which is image data for each HMI screen 17, a parts library 24, a screen operation rights (operation location) table 25, a screen operation rights (job) table 26, a parts operation rights (operation location) table 27, and a parts operation rights (job) table 28.
  • the parts library 24 includes a collection of scripts that describe operations for each type of part (hereinafter referred to as "part type") displayed on the HMI screen 17.
  • a script is a JavaScript (registered trademark) program defined for each part type.
  • the script is given parameter values as necessary and can be executed on each web browser 16.
  • the parameter values include, for example, the presence or absence of screen operation rights defined in the screen operation rights (operation location) table 25 and the screen operation rights (job) table 26, and the presence or absence of specific part operation rights defined in the part operation rights (operation location) table 27 and the part operation rights (job) table 28.
  • FIG. 4 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 defines the presence or absence of screen operation right for each HMI screen 17 (whether operation is permitted or not) according to the operation location of the HMI client devices 12a, 12b, specifically, according to the RM driver's cab 13 and FM driver's cab 14 in which the HMI client devices 12a, 12b are installed.
  • "G10" to "G12" are the screen names of the HMI screens 17 displayed on the web browser 16 executed by each HMI client device 12.
  • "G10" is the screen name of the HMI screen 17a shown in FIG.
  • G11 is the screen name of the HMI screen 17b shown in FIG. 3(b).
  • the HMI client device 12a operated in the RM cab 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.
  • the HMI client device 12b operated in the FM cab 14 has the screen operation right to operate the HMI screen 17b (G11) on the web browser 16b, but does not have the operation right to operate the HMI screen 17 (G10, G12) on the web browser 16.
  • FIG. 5 is a diagram showing an example of the screen operation right (job) table 26.
  • the screen operation right (job) table 26 contains screen operation right (job) information that defines the presence or absence of screen operation rights for each HMI screen 17 (whether operation is permitted or not) according to the job of the operator logged in to the HMI client device 12, specifically, according to the operation manager and equipment manager.
  • screen operation right (job) information that defines the presence or absence of screen operation rights for each HMI screen 17 (whether operation is permitted or not) according to the job of the operator logged in to the HMI client device 12, specifically, according to the operation manager and equipment manager.
  • an operation manager logs in
  • he or she has screen operation rights to operate all HMI screens 17 (G10, G11, G12).
  • an equipment manager logs in he or she has screen operation rights to operate the HMI screen 17 (G11), but does not have screen operation rights to operate the HMI screens 17 (G10, G12).
  • FIG. 6 is a diagram showing an example of a part operation right (operation location) table 27.
  • the part operation right (operation location) table 27 includes part operation right (operation location) information that defines the presence or absence of operation right (operability) of specific parts displayed on each HMI screen 17 according to the operation location of the HMI client devices 12a, 12b, specifically, according to the RM driver's cab 13 and FM driver's cab 14 in which the HMI client devices 12a, 12b are installed.
  • part operation right (operation location) table 27 includes part operation right (operation location) information that defines the presence or absence of operation right (operability) of specific parts displayed on each HMI screen 17 according to the operation location of the HMI client devices 12a, 12b, specifically, according to the RM driver's cab 13 and FM driver's cab 14 in which the HMI client devices 12a, 12b are installed.
  • the HMI client device 12a operated in the RM driver's cab 13 has a specific operation part (1_PL) on the HMI screen 17 (G10) designated as inoperable, and a specific operation part (3_PL) on the HMI screen 17 (G11) designated as operable.
  • the HMI client device 12b operated in the FM driver's cab 14 has a specific operation part (1_PL) on the HMI screen 17 (G10) designated as operable, and a specific operation part (2_PL) on the HMI screen 17 (G11) designated as inoperable.
  • the part operation right (job) table 28 includes part operation right (job) information that defines the presence or absence of operation rights (operability) of specific parts displayed on each HMI screen 17 according to the job of the operator logged in to the HMI client device 12, specifically, according to the operator and the equipment manager.
  • the specific operation part (1_PL) on the HMI screen 17 (G11) is specified as operable, and the specific operation parts (4_PL, 5_PL) are specified as inoperable.
  • the specific operation part (1_PL) is, for example, an operation part for performing manual operation (manual intervention).
  • the specific operation part (1_PL) on the HMI screen 17 (G11) is specified as inoperable, and the specific operation parts (4_PL, 5_PL) are specified as operable.
  • the specific operation parts (4_PL, 5_PL) are, for example, operation parts for performing maintenance.
  • the HMI client device 12 (12a, 12b) includes a processing circuit 30 (30a, 30b) and a monitor 15 (15a, 15b).
  • the processing circuit 30 includes a processor 121 that executes various processes and a memory 122 in which various information is stored.
  • the processor 121 and the memory 122 correspond to the client processor and client memory, respectively, in the claims.
  • the processor 121 executes a program stored in the memory 122, causing the processor 121 to function as a web browser processing unit 31 (31a, 31b).
  • 30-31 when there is no need to distinguish between the reference symbols 30a-31a and 30b-31b, they will simply be referred to as 30-31.
  • the web browser processing unit 31 is executed for each web browser 16.
  • the web browser 16 renders 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 parts are arranged on the HMI screen 17.
  • the parts include, for example, operation parts (1_PL, 2_PL, 3_PL, ...) for sending control signals to the PLC 8 in response to the operation of the operator, display parts whose display state (numbers, characters, colors, shapes) changes in response to the received PLC signal, screen transition parts for switching to another HMI screen, and the like.
  • the operation parts include specific operation parts (1_PL, 2_PL, 3_PL, ..., 5_PL) whose operatability is determined in the part operation authority (operation location) table 27 and the part operation authority (job) table 28 as described above.
  • the web browser processing unit 31 receives the above-mentioned HTML file, SVG file 23, parts library 24, screen operation authority (operation location) table 25, screen operation authority (job) table 26, part operation authority (operation location) table 27, part operation authority (job) table 28, etc. from the web server processing unit 22 and stores them in the memory 122.
  • Each web browser 16 (web browser processing unit 31) also acquires the job of the operator who logged in to the HMI client device 12 and stores it in the memory 122.
  • the job of the operator can be acquired, for example, by referring to a group user list in which the login IDs and jobs of multiple operators are registered together.
  • the web browser 16 draws the HMI screen 17 on which multiple parts including operation parts (including specific operation parts) and display parts are arranged. Each web browser 16 also runs in a mode that does not use a cache in order to always acquire the latest files from the web server processing unit 22 at startup.
  • the web browser processing unit 31 reads the screen operation authority (operation location) table 25 received from the HMI server device 11, and determines whether each HMI screen 17 can be operated (whether or not operation authority exists) by the operation location for each web browser 16.
  • the web browser processing unit 31 also reads the screen operation authority (job) table 26 received from the HMI server device 11, and determines whether each HMI screen 17 can be operated (whether or not operation authority exists) by the job for each web browser 16.
  • the web browser processing unit 31 reads the part operation right (operation location) table 27 received from the HMI server device 11 and determines whether specific operation parts (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.
  • the web browser processing unit 31 also reads the part operation right (job) table 28 received from the HMI server device 11 and determines whether specific operation parts (1_PL, 2_PL, 3_PL, ..., 5_PL) on the HMI screen 17 (G11) can be operated according to the job of the operator logged in to the HMI client device 12.
  • the web browser processing unit 31 further executes a screen drawing process 32.
  • the screen drawing process 32 preferentially applies the operation rights (operation possibility) according to the operation location and the operator's job defined in the part operation rights (operation location) table 27 and the part operation rights (job) table 28 to the specific operation parts (1_PL, 2_PL, 3_PL, ..., 5_PL) on the HMI screen 17 (G11), and applies the screen operation rights (operation possibility) defined in the screen operation rights (operation location) table 25 and the screen operation rights (job) table 26 to the operation parts (6_PL, ...) other than the specific operation parts on the HMI screen 17, to draw the HMI screen 17 (G11) on the web browser 16.
  • the web browser processing unit 31 executes the script for each part type contained in the above-mentioned parts library 24 according to the part type of the part placed on the HMI screen 17 (G11).
  • the operation parts among the part types, whose behavior changes depending on the presence or absence (parameter value) of screen operation rights and part operation rights passed to the script.
  • part operation rights (operation location) table 27 and the part operation rights (job) table 28 if operation rights are defined for specific operation parts (1_PL, 2_PL, 3_PL, ..., 5_PL) of the HMI screen 17 according to the operation location and the job of the operator, the operation rights defined in the part operation rights (operation location) table 27 and the part operation rights (job) table 28 are applied preferentially to the specific operation parts. For operation parts not defined in the part operation rights (operation location) table 27 and the part operation rights (job) table 28, the operation rights defined in the screen operation rights (operation location) table 25 and the screen operation rights (job) table 26 are applied.
  • the operation parts do not accept operations (e.g. mouse clicks) by operators, including those in charge of operations (operators) and equipment personnel.
  • the operation parts accept operations by operators and send control signals corresponding to those operations to the HMI server device 11.
  • the web browser processing unit 31 dynamically sets screen operation rights and part operation rights for each HMI screen 17 displayed on each web browser 16 in accordance with the received PLC signal.
  • the screen operation rights (operation location) table 25, screen operation rights (job) table 26, part operation rights (operation location) table 27, and part operation rights (job) table 28 are referenced, so a detailed explanation will be omitted.
  • FIG. 8 is a flowchart for explaining an example of the drawing process of the HMI client device 12.
  • 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 the default monitor 15 at a predetermined initial position and size, regardless of the position and size of the web browser 16 when it is closed.
  • each web browser 16 obtains the job of the logged-in operator from the operator's login ID, and also obtains content from the HMI server device 12.
  • the content includes the above-mentioned HTML file, SVG file 23, parts library 24, screen operation rights (operation location) table 25, screen operation rights (job) table 26, parts operation rights (operation location) table 27, and parts operation rights (job) table 28. Note that the parts library 24 and each of the tables 25 to 28 need only be obtained when the web browser 16 is started.
  • the web browser processing unit 31 renders the HMI screen 17 specified in the web browser 16 according to the screen operation rights (operation location) table 25, screen operation rights (job) table 26, part operation rights (operation location) table 27, and part operation rights (job) table 28 obtained in step S2 above.
  • the web browser processing unit 31 refers to the screen operation authority (operation location) table 25 and determines whether or not the operation location of the HMI client device 12 has screen operation authority for the HMI screen 17 (step S3). If the operation location does not have screen operation authority, the process proceeds to step S9. On the other hand, if the operation location has screen operation authority, the process proceeds to step S4.
  • step S4 the screen operation rights (job) table 26 is referenced to determine whether or not the job acquired in step S2 has screen operation rights for the HMI screen 17. If the job does not have screen operation rights, the process proceeds to step S9. On the other hand, if the job does have screen operation rights, the process proceeds to step S5.
  • step S5 the part operation right (operation location) table 27 is referenced to determine whether or not there is a specific operation part that is designated as inoperable due to the operation location. If there is a specific operation part that is designated as inoperable due to the operation location, the process proceeds to step S8. On the other hand, if there is no specific operation part that is designated as inoperable due to the operation location, the process proceeds to step S6.
  • step S6 the part operation rights (job) table 28 is referenced to determine whether there are any specific operation parts that have been designated as inoperable by the job. If there are any specific operation parts that have been designated as inoperable by the job, the process proceeds to step S8. On the other hand, if there are no specific operation parts that have been designated as inoperable by the job, the web browser processing unit 31 renders all operation parts on the HMI screen 17 in an operable state (step S7). After that, this routine is temporarily terminated.
  • step S8 the specific operation part on the HMI screen 17 is rendered in an inoperable state, and operation parts other than the specific operation part are rendered in an operable state (step S8). After that, this routine is temporarily terminated.
  • step S9 the part operation right (operation location) table 27 is referenced to determine whether or not there is a specific operation part that has been designated as operable by the operation location. If there is a specific operation part that has been designated as operable by the operation location, the process proceeds to step S12. On the other hand, if there is no specific operation part that has been designated as operable by the operation location, the process proceeds to step S10.
  • step S10 the part operation rights (job) table 28 is referenced to determine whether or not there is a specific operation part designated as operable by the job. If there is a specific operation part designated as operable by the job, the process proceeds to step S12. On the other hand, if there is no specific operation part designated as operable by the job, the process proceeds to step S11.
  • step S11 the web browser processing unit 31 renders all operational parts on the HMI screen 17 in an inoperable state (step S11). After that, this routine ends for the time being.
  • step S12 the web browser processing unit 31 renders the specific operation part on the HMI screen 17 in an operable state, and renders operation parts other than the specific operation part in an inoperable state (step S12). After that, this routine is temporarily terminated.
  • the web browser processing unit 31 draws the specific operation part in an inoperable state on the web browser 16 and draws operation parts other than the specific operation part in an operable state on the web browser 16.
  • the flowchart in Figure 8 described above describes the drawing of the HMI screen 17 when the web browser 16 is started. This makes it possible to statically set the presence or absence of screen operation rights and operation rights for operation parts on the HMI screen 17 for each HMI screen 17.
  • an operator may press a screen transition button on the HMI screen 17 to transition to another HMI screen 17.
  • the web browser processing unit 31 newly acquires the HTML file and SVG file 23 related to the other HMI screen 17 from the HMI server device 12, and executes the processing from step S3 onwards, thereby statically setting the presence or absence of screen operation rights and part operation rights for each HMI screen 17.
  • the operation permissions defined in the screen operation rights (operation location) table 25 are applied to multiple operation parts on the HMI screen 17, and the operation permissions defined according to the job in the part operation rights (job) table 28 are applied preferentially to specific operation parts on the HMI screen 17. Therefore, operation rights are set for each HMI screen 17 according to the operation location of the HMI client device 12, and operation rights for specific operation parts are set preferentially for each HMI screen 17 according to the job of the operator. As a result, more detailed operation rights are set for each HMI screen 17, which makes it possible to prevent the safety of the equipment 2 to 7 being monitored and the hot rolling line RL from being compromised.
  • FIG. 9 is a block diagram showing an example of the hardware configuration of the HMI server device 11 and the HMI client device 12.
  • the processing circuit is configured by connecting a processor 111, a memory 112, and a network interface 113.
  • the processor 111 as a server processor realizes each function of the HMI server device 11 by executing various programs stored in the memory 112 as a server memory.
  • the memory 112 includes a main storage device and an auxiliary storage device.
  • the memory 112 stores in advance the above-mentioned HTML file, SVG file 23, part library 24, screen operation authority (operation location) table 25, screen operation authority (job) table 26, part operation authority (operation location) table 27, and part operation authority (job) 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 with each other.
  • the above-mentioned processes of the HMI client device 12 are realized by the processing circuit 30.
  • the processing circuit 30 is configured by connecting a processor 121, a memory 122, a network interface 123, an input interface 124, and a monitor 125.
  • the processor 121 realizes 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 with them.
  • the input interface 124 is a set of input devices consisting of a keyboard, a mouse, a touch panel, etc.
  • the present disclosure is not limited to the above embodiments and can be implemented in various modifications without departing from the spirit of the present disclosure.
  • the duties of an operator include an operator and an equipment operator, but in addition to these operators and equipment operators, the duties can also include a safety officer who is permitted to operate all specific operation parts.
  • operators may be divided into multiple groups according to their level of proficiency in manual operation. For example, operators may be divided into senior operators (senior operators) who are highly skilled in manual operation, and junior operators (junior operators) who are less skilled than the senior operators.
  • the present disclosure can be applied, for example, to cases in which the duties of an operator include senior operators, junior operators, equipment officers, and safety officers.
  • the duties of the operators can be configured to include senior operators who are highly skilled in manual operations, and junior operators who are less skilled than the senior operators. In this case, too, it is possible to restrict the operation of specific operating parts by junior operators, and as a result, as in the above embodiment, it is possible to prevent the safety of the equipment being monitored, and ultimately the hot rolling line RL, from being compromised.
  • 1...SCADA web HMI system 2...heating furnace, 3...roughing mill, 4...intermediate equipment, 5...finishing mill, 6...water cooling device, 7...coiler, 8...PLC, 91...control LAN, 92...information LAN, 10...computer, 11...HMI server device, 12, 12a, 12b...HMI client device, 13...RM operator's cab, 14...FM operator's cab, 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...parts library, 25...screen operation authority (operation location) table, 26...screen operation authority (job) table, 27...part Part operation authority (operation location) table, 28...
  • Part operation authority (job) 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 parts, 1_PL, 2_PL, 3_PL, 4_PL, 5_PL... Specific operation parts

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • User Interface Of Digital Computer (AREA)
  • Storage Device Security (AREA)
PCT/JP2023/028568 2023-08-04 2023-08-04 Ｓｃａｄａウェブｈｍｉシステム Pending WO2025032635A1 (ja)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2024549742A JP7736209B2 (ja) 2023-08-04 2023-08-04 Ｓｃａｄａウェブｈｍｉシステム
PCT/JP2023/028568 WO2025032635A1 (ja) 2023-08-04 2023-08-04 Ｓｃａｄａウェブｈｍｉシステム
CN202380058560.XA CN119790358A (zh) 2023-08-04 2023-08-04 Scada网页hmi系统
TW112146115A TWI885608B (zh) 2023-08-04 2023-11-28 Scada web hmi系統

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/028568 WO2025032635A1 (ja) 2023-08-04 2023-08-04 Ｓｃａｄａウェブｈｍｉシステム

Publications (1)

Publication Number Publication Date
WO2025032635A1 true WO2025032635A1 (ja) 2025-02-13

Family

ID=94534096

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/028568 Pending WO2025032635A1 (ja) 2023-08-04 2023-08-04 Ｓｃａｄａウェブｈｍｉシステム

Country Status (4)

Country Link
JP (1) JP7736209B2 (https=)
CN (1) CN119790358A (https=)
TW (1) TWI885608B (https=)
WO (1) WO2025032635A1 (https=)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014225234A (ja) * 2013-03-15 2014-12-04 フィッシャー−ローズマウント システムズ，インコーポレイテッド 場所アウェアモバイル制御デバイスでプロセスプラントを制御するための方法及び装置
JP2019114090A (ja) * 2017-12-25 2019-07-11 三菱電機株式会社 監視制御システム
JP2020518903A (ja) * 2017-04-20 2020-06-25 サウジ アラビアン オイル カンパニー 遠隔端末ユニットからｓｃａｄａネットワークへのアクセスの保護
WO2023127040A1 (ja) * 2021-12-27 2023-07-06 東芝三菱電機産業システム株式会社 Ｓｃａｄａウェブｈｍｉクライアント装置およびｓｃａｄａウェブｈｍｉシステム

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010131069A1 (en) * 2009-05-11 2010-11-18 Clipper Windpower, Inc. Fiber optic distributed input/output system for wind turbine
US10613567B2 (en) * 2013-08-06 2020-04-07 Bedrock Automation Platforms Inc. Secure power supply for an industrial control system
US10955831B2 (en) * 2018-12-26 2021-03-23 Nozomi Networks Sagl Method and apparatus for detecting the anomalies of an infrastructure
EP3960396A1 (en) * 2020-08-31 2022-03-02 Siemens Aktiengesellschaft Enhancement of human-machine interface (hmi) for controlling a robot

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014225234A (ja) * 2013-03-15 2014-12-04 フィッシャー−ローズマウント システムズ，インコーポレイテッド 場所アウェアモバイル制御デバイスでプロセスプラントを制御するための方法及び装置
JP2020518903A (ja) * 2017-04-20 2020-06-25 サウジ アラビアン オイル カンパニー 遠隔端末ユニットからｓｃａｄａネットワークへのアクセスの保護
JP2019114090A (ja) * 2017-12-25 2019-07-11 三菱電機株式会社 監視制御システム
WO2023127040A1 (ja) * 2021-12-27 2023-07-06 東芝三菱電機産業システム株式会社 Ｓｃａｄａウェブｈｍｉクライアント装置およびｓｃａｄａウェブｈｍｉシステム

Also Published As

Publication number Publication date
JPWO2025032635A1 (https=) 2025-02-13
CN119790358A (zh) 2025-04-08
TWI885608B (zh) 2025-06-01
TW202507441A (zh) 2025-02-16
JP7736209B2 (ja) 2025-09-09

Similar Documents

Publication Publication Date Title
JP3085252B2 (ja) 遠隔操作カメラ映像中継システム
JP7245741B2 (ja) Ｓｃａｄａウェブｈｍｉサーバおよびｓｃａｄａウェブｈｍｉシステム
DE112013007104B4 (de) Überwachungssystem, Gebäudemanagementgerät, Überwachungsverfahren und Programm
EP3070556B1 (de) Verfahren, recheneinrichtung, benutzer-einheit und system zum parametrieren eines elektrischen gerätes
US20120253525A1 (en) Air-conditioning controlling system
US12436524B2 (en) SCADA web HMI client device and SCADA web HMI system
JP7736209B2 (ja) Ｓｃａｄａウェブｈｍｉシステム
JP7409559B2 (ja) Ｓｃａｄａウェブｈｍｉクライアント装置およびｓｃａｄａウェブｈｍｉシステム
JPWO2023281663A5 (https=)
TW202345014A (zh) Ｓｃａｄａ網頁ｈｍｉ用戶裝置及ｓｃａｄａ網頁ｈｍｉ系統
JP7117984B2 (ja) 機械操作管理装置
JP5721762B2 (ja) 設備管理システム、監視装置および監視プログラム
JP5743648B2 (ja) 管理装置及び設備管理システム
JPH1124710A (ja) 分散制御システム
DE102020214086A1 (de) Kommunikationssteuerung
JPWO2025032635A5 (https=)
TWI821981B (zh) SCADA Web HMI系統
JP3884549B2 (ja) 状態監視システム
JP3668768B2 (ja) プラント運転監視システム
DE102012224255A1 (de) Werkssicherheits-Verwaltungsvorrichtung, Verwaltungsverfahren und Verwaltungsprogramm
JP4160768B2 (ja) Ｎｃ工作機械の管理方法
JP2013077092A (ja) プラント監視制御装置
JP2007109022A (ja) 監視・制御システム
JP3605142B2 (ja) 圧延ラインの異常診断方法
Borthwick et al. Implementation of a PC-based operator interface for a paper machine drive

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2024549742

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2024549742

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202380058560.X

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 202517013572

Country of ref document: IN

WWP Wipo information: published in national office

Ref document number: 202517013572

Country of ref document: IN

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

Ref document number: 23948356

Country of ref document: EP

Kind code of ref document: A1

WWP Wipo information: published in national office

Ref document number: 202380058560.X

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE