JP7790634B2 - SCADA Web HMI System - Google Patents

Description

The present invention relates to a SCADA web HMI system.

SCADA (Supervisory Control and Data Acquisition) is known as a mechanism for monitoring and controlling social infrastructure systems. Social infrastructure systems include, for example, steel rolling systems, power transmission and transformation systems, water and sewerage treatment systems, building management systems, and road systems. SCADA is a type of industrial control system that uses computers to monitor systems and control processes. SCADA requires responsiveness (real-time performance) that matches the system's processing performance.

SCADA's subsystems include an HMI (Human Machine Interface), a monitoring and control system, a Remote Input/Output (RIO), and a communications infrastructure.

HMI is a mechanism that displays data on the target process (monitored device) and components such as operation buttons (also called "operation components" or "items") on the HMI screen, allowing an operator to monitor the process and operate the operation buttons to control the target process. The monitoring and control system collects signal data (PLC signals) from the process and sends control commands to the process. The monitoring and control system is composed of a PLC (Programmable Logic Controller). The remote input/output device connects to sensors installed within the process, converts the sensor signals into digital data, and sends that digital data to the monitoring and control system. The communication infrastructure connects the monitoring and control system to the remote input/output device.

In a SCADA system with this configuration, it is necessary to accurately transmit operation and display signals between the supervisory control system (PLC) and the HMI. To achieve this, it is necessary not only to associate display components on the HMI screen with operation and display signals, but also to properly manage address information for sending and receiving operation and display signals, such as the item names of operation and display signals and the addresses of operation and display signals stored in the supervisory control system (PLC) and the HMI, respectively.

In recent years, industrial control systems have become larger in scale as plants have become larger. Large-scale industrial control systems handle address information assigned to tens of thousands or even hundreds of thousands of items.

However, if the HMI screen designer had to manually assign the signal names of the operation signals and display signals, as well as the addresses of the operation signals and display signals stored in the monitoring control system (PLC) and HMI, this would place a huge burden on the designer, require a huge amount of work time, and be a cause of work errors.

In order to reduce such work time and work errors, for example, the design support device described in Patent Document 1 has the function of automatically assigning addresses for sending and receiving operation signals and display signals between a monitoring control system (PLC) and an HMI connected via a network.

Japanese Patent Application Publication No. 2011-81430

However, there are cases where a new HMI screen being created contains a new component (a new component linked to the same operation signal or display signal) that is identical to an existing component placed on an existing HMI screen. In such cases, even if a PLC address was assigned to the existing component, a different PLC address was assigned to the new component. This required changes to the PLC software, resulting in increased designer time. Furthermore, as the number of PLC addresses increased, the address space within the PLC also expanded, creating the problem of an increased amount of data being sent and received from the PLC.

This disclosure has been made to solve the problems described above. Its purpose is to provide a SCADA web HMI system that, when adding or modifying an HMI screen, does not require changes to the PLC software when adding only new components that perform the same processing as existing components, thereby reducing the designer's work time and minimizing the address space used within the PLC and the amount of data sent and received from the PLC.

The first aspect relates to a SCADA web HMI system. The SCADA web HMI system updates the display state of at least one component displayed on an HMI screen on a web browser based on a display signal corresponding to a signal received from a PLC, and is capable of sending an operation signal corresponding to the operation of the at least one component to the PLC. The SCADA web HMI system includes an HMI design device that creates multiple HMI screens, and the HMI design device has address allocation means that assigns addresses to all components on the created HMI screens. The SCADA web HMI system also includes an address reuse source designation means and an address reuse means. The existing HMI screen is designated as the first screen, the HMI screen to be added or modified is designated as the second screen, the components on the first screen are designated as existing components, and the components on the second screen are designated as new components. The address reuse source designation means designates the existing component from which the address will be reused for the new component to which the address will be reused. The address reuse means is for specifying an existing part as a source of address reuse for the new part by the address reuse source specifying means, and for performing the same processing for the new part and the existing part, and reuses the address of the existing part for the new part when an address has already been assigned to the existing part by the address assignment means. The web browser displays an HMI screen, updates the display of the existing part on the first screen and the new part on the second screen based on a common display signal, and transmits operation signals according to operations of the existing part and the new part to a common address of the PLC.

The second aspect has the following additional features in addition to the first aspect: The existing and new components are display components that update the display state on the first screen and the second screen based on a display signal, or operation components that send operation signals to the PLC.

The third aspect has the following characteristics in addition to the first or second aspect: The SCADA web HMI system further includes an address reuse result generation means for generating address reuse information that describes the part names of existing parts and the part names of new parts.

According to this disclosure, new components that perform the same processing as existing components can be assigned addresses that are shared with existing components. This eliminates the need to implement processing to operate new components in the PLC software; new components can be operated based on the addresses of existing components. This allows designers to change only the HMI screen without changing the PLC software, reducing their work time. Furthermore, the address area used within the PLC and the amount of data sent and received by the PLC can be kept to a minimum.

FIG. 1 is a diagram showing the configuration of a SCADA web HMI system according to an embodiment. FIG. 2 is a block diagram showing an example of the hardware configuration of a SCADA web HMI design device and a SCADA web HMI execution device. FIG. 2 is a block diagram for explaining main processes executed in an engineering tool and a web browser. FIG. 10 is a diagram illustrating an example of a drawing creation screen displayed by an engineering tool. 10A and 10B are diagrams showing examples of a first screen and a second screen which are HMI screens created by a drawing process. Fig. 6(a) is a diagram showing an example of on-screen component information of the first screen shown in Fig. 5. Fig. 6(b) is a diagram showing an example of on-screen component information of the second screen shown in Fig. 5. FIG. 10 is a diagram showing an example of in-screen component information of the second screen after the address reuse source is input; 10 is a flowchart illustrating the flow of an address allocation process 14. FIG. 10 is a diagram illustrating an example of an allocation processing rule. FIG. 10 is a diagram showing an example of in-screen component information of the first screen after the address allocation process is executed. FIG. 10 is a diagram showing an example of in-screen component information of the second screen after the address allocation process and the address diversion process are executed. FIG. 10 is a diagram illustrating an example of address reuse information generated after executing address reuse processing.

Embodiments of the present disclosure will be described in detail below with reference to the drawings. However, when reference is made to the number, quantity, amount, range, etc. of each element in the embodiments shown below, the present invention is not limited to the mentioned numbers unless specifically stated otherwise or clearly specified in principle. Furthermore, structures, etc. described in the embodiments shown below are not necessarily essential to the present disclosure unless specifically stated otherwise or clearly specified in principle. Elements common to each figure will be assigned the same reference numerals, and duplicate explanations will be omitted.

<Overall system>
1 is a diagram showing the configuration of a SCADA web HMI system according to an embodiment. The SCADA web HMI system includes a SCADA web HMI design device (hereinafter also referred to as "HMI design device") 1, which is an HMI development environment. The SCADA web HMI system includes, as subsystems, a SCADA web HMI execution device ( hereinafter also referred to as " HMI execution device " ) 3, which is an HMI execution environment, a monitoring and control system 4, a communications infrastructure 5, a remote input/output device (RIO) 6, and a monitored device 7.

The monitoring and control system 4 includes a programmable logic controller (PLC) that has an internal address area 41. The communication infrastructure 5 connects the monitoring and control system 4 to a remote input/output device. The remote input/output device 6 connects to a sensor installed in the monitored device 7, converts the sensor signal into digital data, and sends the digital data to the monitoring and control system 4. The monitored device 7 is a sensor, actuator, etc. that constitutes the plant.

<HMI design equipment>
The HMI design device 1 executes an engineering tool 10. The engineering tool 10 has a function for creating and editing drawings, a function for saving drawing data in Scalable Vector Graphics (SVG) format, and extended functions. The drawing creation and editing functions and the SVG data saving function are realized, for example, by Microsoft Visio (registered trademark). The HMI design device 1 is equipped with a GUI as a user interface for executing the engineering tool 10. The engineering tool 10 generates interface information 21 and HMI screen data 22 required to operate the HMI execution device 3, which is the HMI execution environment. The interface information 21 and HMI screen data 22 constitute web HMI data 2.

Figure 2 is a block diagram showing an example of the hardware configuration of the SCADA web HMI design device 1 and the SCADA web HMI execution device 3. Figure 3 is a block diagram for explaining the main processes executed in the engineering tool 10 and the web browser 32.

The processes of the HMI design device 1, which will be described later, are realized by the processing circuit shown in Figure 2. The processing circuit is composed of at least one processor 1a, memory 1b, display 1c, and input/output interface 1d connected to one another. Memory 1b stores programs describing the processes executed by the engineering tool 10. Input/output interface 1d includes input devices such as a keyboard and mouse, and an output device capable of outputting web HMI data 2 as a file. Processor 1a executes the programs read from memory 1b to realize the processes of the HMI design device 1, which will be described later.

As shown in Figure 3, the engineering tool 10 is capable of executing the following main processes: drawing process 11, component data generation process 12, in-screen component information generation process 13, address allocation process 14, interface information generation process 15, and HMI screen data generation process 16. Each process executed by the engineering tool 10 is described below.

(Drawing processing)
First, the drawing process 11 for creating drawings to be used as HMI screens will be described with reference to Figures 4 and 5. Figure 4 shows an example of a drawing creation screen 100 displayed by the engineering tool 10. The drawing creation screen 100 is displayed on the display 1c.

The drafting process 11 displays, on the drawing creation screen 100, a stencil area 101 in which prototypes (master shapes) 101a, 101b, and 101c of multiple components required to create a drawing are arranged, and a drafting area 102 in which drawings for the HMI screen are drawn. In the drafting process 11, the designer operates the input/output interface 1d to select a prototype from the stencil area 101 and place the selected prototype in the drafting area 102. In the example shown in Figure 4, the prototype 101a of a two-choice button item in the stencil area 101 is dragged and dropped into the drafting area 102, thereby placing the two-choice button item 102a in the drafting area 102.

Figure 5 shows an example of a first screen G100 and a second screen G200, which are HMI screens created by the drawing process. An alternative button item 111 is placed on the first screen G100, and an alternative button item 112 is placed on the second screen G200 in a different position from the first screen G100. The first screen G100 corresponds to an existing screen in the claims, and the second screen G200 corresponds to a new screen in the claims. The alternative button item 111 corresponds to an existing part in the claims, and the alternative button item 112 corresponds to a new part in the claims.

(Parts data generation process)
Next, a description will be given of the component data generation process 12. The component data generation process 12 automatically generates unique component data when a component is placed in the drawing area 102 shown in Fig. 4. Although not shown, the component data is data that associates placement information of the component placed in the drawing area 102 with a component identifier, an attribute identifier, and a component type.

Layout information is static screen display data such as the shape, position, and size of parts placed in the drawing area 102, and is information that does not change the appearance of the parts regardless of the value of the received PLC signal. Layout information can be changed in the drawing area 102. Component identifiers are unique identifiers that identify each component placed on a single drawing, such as component numbers. Attribute identifiers are identifiers that indicate the dynamic display attributes of the component.

The component data generation process 12 generates a "component name" by combining the screen identifier G100, G200 of the HMI screen and the component identifier 1PL2, and generates an "item name" by combining the component name and attribute identifier. The item name is unique within the SCADA web HMI system.

The component data generation process 12 generates one "component type" for each component. For example, a component type of "PL" is generated for an operation component, and a component type of "SL" is generated for a lamp display component.

(In-screen component information generation process)
Next, the on-screen component information generation process 13 will be described with reference to Fig. 6. Fig. 6(a) is a diagram showing an example of on-screen component information 131 of the first screen G100 shown in Fig. 5. Fig. 6(b) is a diagram showing an example of on-screen component information 132 of the second screen G200 shown in Fig. 5.

The on-screen component information generation process 13 is executed when component data is generated by the component data generation process 12. The on-screen component information generation process 13 generates tabular on-screen component information 131, 132 for each screen G100, G200. The on-screen component information 131, 132 contains, for each component, the component name, component type, and item names of operation signals and display signals. The addresses of the operation signals and display signals are recorded after the address allocation process 14, described below, is executed.

Here, the part name from which the address is to be reused is manually entered by the HMI screen designer using the input/output interface 1d when executing the address reuse process 140 described below and before executing the address allocation process 14. Therefore, the input/output interface 1d corresponds to the "address reuse source designation means" in the claims. Figure 7 is a diagram showing an example of the in-screen part information 132 for the second screen G200 after the part name of the first screen G100 has been entered as the address reuse source.

When executing the address reuse process 140 in the address allocation process 14 described below, a "source address component name" is specified for each component to associate the component with the source address. In the example shown in FIG. 7 , the in-screen component information 132 for the second screen G200 is edited, and the component name of the operation component placed on the first screen G100, "G100_1PL2," is entered in the "source address component name" field. Here, the component name "G200_1PL2" of the destination address and the component name "G100_1PL2" of the source address are of the same component type PL and perform the same processing. "Performing the same processing" means that they are linked to the same operation signal or display signal.

(Address allocation process)
Next, the address allocation process 14 will be described with reference to Figures 8 to 10. The address allocation process 14 is executed by the designer of the HMI screen. The address allocation process 14 allocates addresses to all components on each of the screens G100 and G200. Figure 8 is a flowchart for explaining the flow of the address allocation process 14. Figure 9 is a diagram showing an example of an allocation process rule 141. Figure 10 is a diagram showing an example of intra-screen component information 131 for the first screen G100 after the address allocation process 14 has been executed. The address allocation process 14 corresponds to the "address allocation means" in the claims.

When the routine shown in FIG. 8 is executed, first, the on-screen component information 131, 132 generated by the on-screen component information generation process 13 is read (step S10). Next, the number of component names in the on-screen component information 131, 132 is assigned to the variable N, and "1" is assigned to the counter variable i as an initial value (step S11). Next, the allocation processing rule 141 for allocating addresses is read (step S12). As shown in FIG. 9, the allocation processing rule 141 defines the association between the number of bits of an operation signal and the number of bits of a display signal for each component type. In the example shown in FIG. 9, the number of bits of an operation signal and the number of bits of a display signal corresponding to the component type are defined. The engineering tool 10 has the allocation processing rule 141. The allocation processing rule 141 is stored in memory 1b.

Next, it is determined whether the value of counter variable i is less than N (step S13). If the value of counter variable i is less than N, it is determined whether an address reuse source has been specified (step S14). If an address reuse source has been specified, the process proceeds to step S17, described below, and address reuse processing 140, described below, is executed. If an address reuse source has not been specified, the process proceeds to step S15. The processing of step S14 corresponds to the "address reuse source designation means" in the claims.

In step S15, an address is assigned from the in-screen component information corresponding to the i-th component name among the in-screen component information 131, 132, based on the allocation processing rule 141. Specifically, from the in-screen component information corresponding to the i-th component name, an address is assigned to the operation signal to be sent from the SCADA web HMI execution device 3 to the monitoring and control system (PLC) 4, based on the number of bits of the operation signal and the number of bits of the display signal included in the allocation processing rule 141 read out in step S12 above, and an address is assigned to the display signal to be sent from the monitoring and control system (PLC) 4 to the SCADA web HMI execution device 3. Then, i+1 is assigned to the variable i, and the process returns to step S13.

The address allocation process 14 can be executed for each of the screens G100 and G200. When the address allocation process 14 is executed for the first screen G100, addresses are respectively allocated to the item names "G100_1PL1_CMD" and "G100_1PL2_CMD" of the operation signals of the part name "G100_1PL2" and the item names "G100_1PL1_SL" and "G100_1PL2_SL" of the display signals based on the allocation process rule 141, as shown in FIG.

The address allocation process 14 has an address diversion process 140 that includes steps S17 to S24. As shown in Fig. 3 , the address diversion process 140 is executed as part of the address allocation process 14. The address diversion process 140 can divert an address from an operation item arranged on the first screen G100 to an operation item on the second screen G200.

( Address reuse processing)
The address diversion process 140 will be described with reference to Figures 11 and 12. The address diversion process 140 corresponds to the "address diversion source designation means" and the "address diversion means" in the claims.

The address diversion process 140 is executed when it is determined in step S13 that the value of the counter variable i is less than N and when it is determined in step S14 that an address diversion source has been designated.

In step S17, it is determined based on the on-screen component information whether the component type of the address source and the component type of the address destination are the same. If the component type of the address source and the component type of the address destination are different, the process proceeds to step S22, where an error message is displayed, and the routine ends. If the component types are the same, the process proceeds to step S18.

In step S18, it is determined whether an address has already been assigned to the component from which the address is to be reused, based on the in-screen component information 131 of the first screen G100. If an address has not been assigned to the component from which the address is to be reused, the process proceeds to step S22 above. If an address has already been assigned to the component from which the address is to be reused, the process proceeds to step S19.

In step S19, the same address as the address source component is allocated to the address destination component. Fig. 11 is a diagram showing an example of the in-screen component information 132 for the second screen G200 after the address allocation process 14 and the address diversion process 140 have been executed. As shown in Fig. 11, addresses that are the same as those allocated to components on the first screen G100 are allocated to components on the second screen G200. When the address diversion process 140 is executed in the address allocation process 14, the component name "G100_1PL2" of the address source is used to associate each component with the address source component.

Next, the number of part names whose addresses have been reused is assigned to variable k (step S20). Next, i+k is assigned to variable i (step S21), and the process returns to step S13. Continuing to execute the address allocation process 14, if it is determined in step S13 that the value of counter variable i is equal to or greater than N, the process proceeds to step S23.

In step S23, as shown in Figures 10 and 11, the address allocation results are added to the on-screen component information 131, 132. Next, address diversion information is generated (step S24). Figure 12 is a diagram showing an example of address diversion information 142 generated after executing address diversion processing 140. The address diversion information 142 makes it possible to associate and store the component name of the address diversion source with the component name of the address diversion destination. The processing of step S24 corresponds to the "address diversion result generation means" in the claims. After step S24, this routine is terminated.

(Interface information generation process)
After the address allocation process 14 is completed, the interface information generation process 15 generates interface information 21 in a format readable by the SCADA web HMI execution device 3 based on the on-screen component information. The interface information 21 is information that defines the relationship between the names and addresses of the items of operation signals sent from the SCADA web HMI execution device 3 to the monitoring control system (PLC) 4 and display signals sent from the monitoring control system (PLC) 4 to the SCADA web HMI execution device 3.

(HMI screen data generation process)
The HMI screen data generation process 16 generates HMI screen data 22 in a format that can be read by the SCADA web HMI execution device 3 based on the layout information of each component generated by the component data generation process 12 .

The web HMI data 2, which includes the interface information 21 and HMI screen data 22 generated by the engineering tool 10 in this way, is information that can be read by the SCADA web HMI execution device 3. The SCADA web HMI execution device 3 updates the display of HMI screens such as the first screen G100 and the second screen G200 based on the web HMI data 2. Specifically, the HMI screen display is updated based on the HMI screen data 22, which is static information such as the shape, position, and size of the components, and the values received from the PLC 4, which is dynamic information. The address information assigned to the display items and operation items of each component on the HMI screen is defined by the interface information 21.

<HMI execution device>
The processing of the HMI execution device 3 is realized by a processing circuit shown in Figure 2. The processing circuit includes at least one processor 3a, a memory 3b, a display 3c, an input/output interface 3d, and a network interface 3e. The memory 3b stores programs describing the processing to be executed by the HMI execution device 3. The input/output interface 3d includes input devices such as a keyboard and a mouse, and a device capable of reading web HMI data 2 (interface information 21 and HMI screen data 22). The network interface 3e is a device that connects to the monitoring and control system 4 and can send and receive signal data and control commands. The processor 3a executes the programs read from the memory 3b to realize each of the processing operations of the HMI execution device 3, which will be described later.

(Web server)
The web server 31 reads the web HMI data 2. The web server 31 arranges the interface information 21 and HMI screen data 22 of the web HMI data 2 as HMI web runtime content, enabling signals to be transmitted and received between the web browser 32 and the monitoring and control system (PLC) 4.

The processing of the HMI server runtime 311 running on the web server 31 is as follows. That is, the HMI server runtime 311 incorporates an application server and supplies HMI web runtime content to the web browser 32. The HMI server runtime 311 communicates with the monitoring and control system 4 (PLC), and if a PLC signal received from the monitoring and control system 4 is a signal related to the HMI screen currently displayed on the web browser 32, it transmits the PLC signal to the web browser 32. The HMI server runtime 311 transmits signal data from the monitored device 7 to the HMI web runtime 321, and also transmits control commands from the HMI web runtime 321 to the monitoring and control system 4.

(Web browser)
The processing of the web browser 32 will be described with reference to FIG. 3 . The web browser 32 reads the web HMI data 2 (interface information 21 and HMI screen data 22) and displays an HMI screen for monitoring the plant on the web browser 32. The HMI screen displays components (parts) that display the status of the monitored device 7 and components (parts) for operating the monitored device 7 via the monitoring and control system 4. The web browser 32 can display and update the HMI screen in response to signals received from the monitoring and control system (PLC) 4. The web browser 32 changes the appearance of the components displayed on the HMI screen in response to values of PLC signals received from the monitoring and control system 4 via the web server 31.

The alternative button items 111, 112 arranged on the first screen G100 and the second screen G200 displayed as HMI screens operate based on address information written in the interface information 21. For the alternative button items 111, 112 arranged on the first screen G100 and the second screen G200, common address information is defined by the address reuse process 140 described above for the operation signal from the HMI execution device 3 to the monitoring control system (PLC) 4 and the display signal from the monitoring control system (PLC) 4 to the SCADA web HMI execution device 3. Therefore, if PLC software corresponding to the alternative button item 111 on the first screen G100 is created, there is no need to create PLC software corresponding to the alternative button item 112 on the second screen G200, thereby reducing the work time of the PLC software designer.

As described above, according to this embodiment, the address allocation process 14 has an address reuse process 140, which allows new components that perform the same processing as existing components to be assigned addresses that are shared with existing components. This eliminates the need to implement processing to operate new components in the PLC software, and allows new components to operate based on the addresses of existing components. This means that only the second screen G200 can be changed without changing the PLC software, thereby reducing the designer's work time. Furthermore, the address area 41 used within the PLC 4 and the amount of data sent and received by the PLC 4 can be kept to a necessary minimum.

Although the embodiments have been described above, the present disclosure is not limited to the above embodiments and can be implemented in various modifications within the scope of the spirit of the present disclosure. For example, the above embodiments have been described using an example in which a new second screen G200 separate from an existing first screen G100 is created (added), but the present disclosure can also be applied when the first screen G100 is modified to create the second screen G200.

In the above embodiment, we have explained an example in which all part names from which addresses are to be reused are manually entered. However, it is also possible to manually enter the first letter "G" that is part of the part name, and then display multiple part names containing that letter as candidates from which to select. This reduces input errors compared to when all parts are entered manually, and is particularly advantageous when there are many part names from which addresses are to be reused.

In the above embodiment, drawing data in SVG format is used, but the format of the drawing data is not limited to this. If the web browser 32 supports WebGL, the drawing data may be in a format compatible with WebGL.

In the above embodiment, the HMI execution device 3 is equipped with a web server 31 and a web browser 32, but it may also be configured to connect multiple client terminals to the web server 31 and display the web browser 32 on the display of each client terminal.

1...HMI design device, 1d...input/output interface (address reuse source designation means), 10...engineering tool, 11...drawing process, 12...component data generation process, 13...intra-screen component information generation process, 14...address allocation process (address allocation means), 140...address reuse process (address reuse source designation means, address reuse means), 142...address reuse information, 15...interface information generation process, 16...HMI screen data generation process, 3...HMI execution device, 32...web browser, 4...monitoring control system (PLC), 41...address area, 7...monitored device, G100...first screen, existing screen, HMI screen, 111...either-or-other button item (existing component), G200...second screen, new screen, HMI screen, 112...either-or-other button item (new component)

Claims (3)

A SCADA web HMI system that updates a display state of at least one component displayed on an HMI screen on a web browser based on a display signal corresponding to a signal received from a PLC, and is capable of transmitting an operation signal corresponding to an operation of the at least one component to the PLC,
An HMI design device for creating a plurality of HMI screens, the HMI design device having address allocation means for allocating addresses to all components on the created HMI screens,
an address diversion source designation means for designating the existing HMI screen as a first screen, the HMI screen to be added or modified as a second screen, the components on the first screen as existing components, and the components on the second screen as new components, and designating the existing components as addresses diversion sources for the new components as addresses diversion destinations;
the address diversion means diverts the address of the existing part to the new part when the address diversion source designation means designates the existing part as the address diversion source of the new part, the new part and the existing part perform the same processing, and an address has already been assigned to the existing part by the address assignment means;
The web browser displays the HMI screen, updates the display of the existing parts on the first screen and the new parts on the second screen based on a common display signal, and transmits the operation signals corresponding to operations of the existing parts and the new parts to a common address of the PLC. The SCADA web HMI system described in claim 1, wherein the existing components and the new components are display components that update the display state on the first screen and the second screen based on the display signal, or operation components that send the operation signal to the PLC. The SCADA web HMI system of claim 1 or claim 2 further comprises an address reuse result generation means for generating address reuse information containing the part names of the existing parts and the part names of the new parts.