Information provision system, information provision method, and information provision program

Abstract

To efficiently perform the shift from an existing system to a new system.SOLUTION: An information provision system includes a control device that provides an operation screen for accessing a tag set in a component of a controller for controlling equipment in a plant, and a management device for managing tag information. The management device includes an acquisition unit for receiving first tag information about a first tag set in a first component of a first controller from a first system, and acquiring second tag information about a second tag set in a second component of a second controller from a second system, and a change notification unit for detecting, based on the first tag information and the second tag information, whether a valid tag has changed from the first tag to the second tag, and notifying the control device of a detection result. The control device includes a setting change unit for changing an access destination of the valid tag to the second controller based on the detection result.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to an information providing system, an information providing method, and an information providing program. [Background technology]

[0002] By introducing an automation system into a plant, the processes for manufacturing various products are automated. For example, Patent Document 1 discloses a technology relating to an automation system.

[0003] When migrating an existing automation system (hereinafter referred to as the "existing system") to a new automation system (hereinafter referred to as the "new system"), it is required to perform the system migration using a method called hot cutover whenever possible.

[0004] Hot cutover is a technique in which, without stopping plant operations, the wiring to field devices is reconnected from the I / O (Input / Output) of the existing system to the I / O of the new system, on a control loop basis, and the function blocks connected to the I / O are also transferred from the existing system to the new system at the same time. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent Publication No. 2022-46438 Summary of the Invention [Problem to be solved by the invention]

[0006] However, in the past, there were cases where migration from an existing system to a new system could not be carried out efficiently.

[0007] For example, assuming the system configuration in Figure 4, the plant will continue to operate with a mixture of I / O and function blocks from the existing and new systems until all I / O and function blocks of the existing system are switched over to those of the new system. When changing the tag allocation used in the HMI (Human Machine Interface) used in plant operations from the existing system to the new system, the allocation must be completed in a short time. If this work takes too long, the control loop to be migrated will not be able to resume in a timely manner, and there is a high possibility that the plant will have to be stopped.

[0008] Also, unlike Figure 4, in the case of a hot cutover with both the HMIs of the existing and new systems in operation, a team of workers, including the plant operation and monitoring operators, checks the relevant drawings of the tags that are the target of the hot cutover every time before starting work. At this time, they use screen copies of the old and new HMIs to check the risk assessment to respond to events that are likely to occur during the hot cutover, and the changes to the plant's operation methods and complex procedures to respond to those events. However, during the system transition period, the tags that can be monitored change every time between the old and new HMIs, and it is necessary to operate the old and new HMIs to respond to events, which increases the probability of human error and may lead to plant shutdowns, etc.

[0009] In one aspect, an object of the present invention is to provide an information providing system, an information providing method, and an information providing program that can assist in efficiently migrating from an existing system to a new system. [Means for solving the problem]

[0010] An information providing system according to one aspect includes a control device that provides an operation screen for accessing tags set in a component of a controller that controls equipment in a plant, and a management device that manages tag information. The management device includes an acquisition unit that receives first tag information related to a first tag set in a first component of the first controller from a first system (e.g., an existing system) and acquires second tag information related to a second tag set in a second component of the second controller from a second system (e.g., a new system), and a change notification unit that detects whether a valid tag has changed from the first tag to the second tag based on the first tag information and the second tag information and notifies the control device of the detection result. The control device includes a setting change unit that changes the access destination of the valid tag to the second controller based on the detection result.

[0011] In one aspect of an information providing method, a management device receives first tag information regarding a first tag set in a first component of a first controller from a first system, obtains second tag information regarding a second tag set in a second component of a second controller from a second system, detects whether a valid tag has changed from the first tag to a second tag based on the first tag information and the second tag information, notifies a control device of the detection result, and the control device changes the access destination of the valid tag to the second controller based on the detection result.

[0012] An information providing program according to one aspect causes a computer to execute a process of receiving from a first system first tag information regarding a first tag set in a first component of a first controller that controls equipment in a plant, acquiring from a second system second tag information regarding a second tag set in a second component of a second controller that controls equipment in the plant, detecting whether a valid tag has changed from the first tag to the second tag based on the first tag information and the second tag information, and notifying a control device of the detection result. Effect of the Invention

[0013] According to one embodiment, it is possible to assist in efficiently implementing migration from an existing system to a new system. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram for explaining an example of the process of migrating from an existing system to a new system. [Diagram 2] FIG. 2 is a diagram for explaining an example of the process of migrating from an existing system to a new system. [Diagram 3] FIG. 3 is a diagram for explaining an example of the process of migrating from an existing system to a new system. [Figure 4] FIG. 4 is a diagram for explaining an example of the process of migrating from an existing system to a new system. [Diagram 5] FIG. 5 is a diagram for explaining an example of the process of migrating from an existing system to a new system. [Figure 6] FIG. 6 is a diagram for explaining an example of the process of migrating from an existing system to a new system. [Figure 7] FIG. 11 is a diagram illustrating an example of a tag information table. [Figure 8] FIG. 13 is a diagram illustrating an example of an updated tag information table. [Figure 9] 11 is a diagram illustrating an example of a structure of a tag held by a monitoring and control application. FIG. [Figure 10] FIG. 13 illustrates an example of a progress status screen. [Figure 11] 2 is a functional block diagram showing a functional configuration of a tag information providing server according to the embodiment; FIG. [Figure 12] FIG. 4 illustrates an example of an information management table. [Figure 13] FIG. 2 is a functional block diagram showing a functional configuration of a control device according to the present embodiment. [Figure 14] 10 is a flowchart showing a flow of processing by the tag information providing server of the present embodiment. [Figure 15] FIG. 2 is a diagram illustrating an example of a hardware configuration. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, the information provision system, the information provision method, and the information provision program disclosed in the present application will be described in detail with reference to the drawings. Note that the present invention is not limited to these embodiments. In addition, the same elements are given the same reference numerals, and duplicated descriptions are omitted as appropriate. Each embodiment can be appropriately combined within a range that does not cause inconsistency.

[0016] (Embodiment) (Regarding migration from existing system to new system) An example of a process of migrating a plant automation system from an existing system to a new system will be described below. Figures 1 to 6 are diagrams for explaining an example of a process of migrating from an existing system to a new system.

[0017] First, Fig. 1 will be described. An existing system 10 shown in Fig. 1 is an automation system before the installation of a new system. For example, the existing system 10 includes a plant 1 and a controller 5.

[0018] Plant 1 is a production facility for petroleum / petrochemicals, gas, iron / non-ferrous metals, chemicals, electricity, food and pharmaceuticals, etc.

[0019] A plurality of devices are provided at various locations in the plant 1. In the example shown in FIG. 1, devices 2a, 2b, 2c, and 2d are shown. For example, the devices 2a and 2c are transmitters. The devices 2b and 2d are valves. Note that the plant 1 may also be provided with other devices. The other devices may be pressure sensors, temperature sensors, flow rate sensors, pH sensors, speed sensors, acceleration sensors, pumps, motors, etc.

[0020] The controller 5 is a hardware or software component that maintains process variables, such as flow rate, pressure, level, temperature, etc., within set ranges of the plant 1. The controller 5 has I / O and function blocks.

[0021] The I / O is an information processing hardware component that receives control output from the controller 5 and transmits it to the devices of the plant 1, and receives process values ​​from the devices of the plant 1 and transmits them to the controller 5.

[0022] The function block is a control (PID) that calculates and adjusts the control signal based on the difference (error) between the current state of the controlled object and the target state.<Proportional Integral Derivative> The function block is connected to the equipment of plant 1 via I / O to form a control loop.

[0023] Tags are set to the I / O and function blocks of the controller 5. For example, “Tag AI1”, “Tag AO1”, “Tag AI2”, and “Tag AO2” shown in FIG. 1 are tags set to the I / O of the controller 5. “Tag PID1” and “Tag PID2” are tags set to the function blocks of the controller 5.

[0024] For example, an I / O with "Tag AI1" is connected to device 2a by wire 3a and receives a process value from device 2a. A function block with "Tag PID1" generates a control signal based on the process value from device 2a and outputs the generated control signal to an I / O with "Tag AO1". An I / O with "Tag AO1" is connected to device 2b by wire 3b and transmits a control signal to device 2b.

[0025] The I / O with "Tag AI2" is connected to device 2c by wiring 3c and receives a process value from device 2c. The function block with "Tag PID2" generates a control signal based on the process value from device 2c and outputs the generated control signal to the I / O with "Tag AO2". The I / O with "Tag AO2" is connected to device 2d by wiring 3d and transmits a control signal to device 2d.

[0026] At the stage shown in Fig. 1, an operator of the existing system 10 operates the HMI of the existing system 10 to communicate with the I / O and function blocks of the controller 5. The operator of the existing system 10 also checks Alarms and Trends. Alarms are information that indicates abnormalities or problems that occur in the existing system 10. Trends are information that visualizes historical changes related to process values ​​in the existing system 10 using graphs or the like.

[0027] The existing system 10 has various types of application software 6. For example, the various types of application software 6 include a historian, a model predictive control (MPC), and an asset management system (AMS).

[0028] A historian is a process database that records the history of process variables, alarms, and events.

[0029] MPC utilizes a predictive model of the plant to predict future plant output.

[0030] AMS is an asset management system that monitors and manages a plant's assets.

[0031] 2 will now be described. A communication relay device 11 is added to the existing system 10. The communication relay device 11 is an Open Platform Communications Unified Architecture Server (OPC UA Server) or the like, and communicates with a Gateway 31 of the new system 20. The communication relay device 11 publishes data of I / O and function blocks of the existing system 10 to a monitoring and control application 30 of the new system 20.

[0032] In FIG. 2, a new system 20 is added. A monitoring and control application 30 is set in the new system 20. The monitoring and control application 30 has a Gateway 31, various application software 32, and an HMI, Alarms, and Trends. The Gateway 31 is an OPC UA Client or the like, and communicates with the communication relay device 11 of the existing system 10 to receive data of the I / O and function blocks of the existing system 10. The Gateway 31 also functions as an OPC UA Server that provides data of the existing system to the various application software 32 and the HMI, Alarms, and Trends. The various application software 32 includes a historian, a soft controller, an MPC, and an AMS. The monitoring and control application 30 also provides the HMI, Alarms, and Trends to the operator of the new system 20.

[0033] A soft controller is a type of controller that is a software component that does not have I / O but has the ability to control process variables.

[0034] We now move on to the description of Fig. 3. As shown in Fig. 3, the Gateway 31 of the monitoring control application 30 is connected to the communication relay device 11 via the switches 7a and 7b. The switches 7a and 7b virtually indicate the connection destination of the Gateway 31. The Gateway 31 acquires tag information set in the controller 5 from the communication relay device 11, and stores the acquired tag information. For example, the Gateway 31 communicates with the communication relay device 11, acquires a set of "Tag AI1", "Tag AO1", and "Tag PID1", and a set of "Tag AI2", "Tag AO2", and "Tag PID2" set in the I / O and function blocks of the controller 5, and records them.

[0035] 3, an operator of the new system 20 can read and write to the I / O and function blocks of the controller 5 of the existing system 10 by operating the HMI of the monitoring and control application 30. The HMI, Alarms, Trends, and various application software 6 of the existing system 10 are migrated to the monitoring and control application 30 of the new system 20. This allows the operator to become familiar with the operation of the existing system 10 by using the monitoring and control application 30 of the new system 20.

[0036] We move on to the explanation of FIG. 4. An operator other than the operator of the newly installed system 20 installs the controller 40 in the newly installed system 20. The controller 40 has an OPC UA Server function. The controller 40 and the inspection HMI 45 are connected to each other via a switch 7c. The switch 7c virtually indicates the connection destination of the controller 40.

[0037] An operator inspects in advance a control loop having the same functions as the existing system 10, with the same names as the tag names of the existing system 10. The operator operates the inspection HMI 45 to set the same tags as the I / O and function blocks of the controller 40 as those of the I / O and function blocks of the controller 5, and constructs the same control loop. In the example shown in FIG. 4, the operator sets "Tag AI1", "Tag AO1", and "Tag PID1" to the I / O and function blocks of the controller 40, and constructs a control loop.

[0038] The worker connects the I / O of the controller 40 to which "Tag AI1" has been assigned to the process simulator 50 via wiring 51a. The worker connects the I / O of the controller 40 to which "Tag AO1" has been assigned to the process simulator 50 via wiring 51b. The worker uses the process simulator 50 to inspect the control loop set in the controller 40.

[0039] We now move on to the explanation of Fig. 5. If no abnormality is found in the result of the control loop inspection of the controller 40, the worker applies physical protection to the devices that receive control signals from the controllers 5 and 40 so that the process values ​​do not fluctuate significantly during loop transition. For example, the worker fixes the opening of the device 2b (valve) of the plant 1.

[0040] After providing protection to the equipment, the worker changes the wiring of the equipment. For example, the worker removes the wiring between the I / O of the controller 5 and the equipment 2a and 2b. The worker connects the I / O of the controller 40 with "Tag AI1" to the equipment 2a via the wiring 52a. The worker connects the I / O of the controller 40 with "Tag AO1" to the equipment 2b via the wiring 52b.

[0041] We now move on to the explanation of Fig. 6. Although not shown in Figs. 1 to 5 described above, this system includes a tag information providing server 100. In the following explanation, the existing system 10, the new system 20, and the tag information providing server 100 shown in Figs. 1 to 6 are collectively referred to as the "information providing system."

[0042] During the process of migrating from the existing system 10 to the new system 20, the tag information providing server 100 is in constant communication with the communication relay device 11 and the controller 40, and when it detects a change in the wiring, it switches the OPC UA Server used for communication with the tags of the controller from the existing system 10 to the new system 20.

[0043] The worker removes the physical protection applied in Fig. 5. For example, the worker releases the fixed opening of the device 2b (valve) of the plant 1. The controller 40 of the newly installed system 20 starts a control loop for the I / O to which "Tag AI1" is set and the I / O to which "Tag AO1" is set and the function block to which "Tag PID1" is set.

[0044] For example, when the migration from Figures 1 to 6 is completed, the HMI of the new system 20 communicates with the new system 20 for each tag "Tag AI1", "Tag AO1", and "Tag PID1", and communicates with the existing system 10 for each tag "Tag AI2", "Tag AO2", and "Tag PID2".

[0045] Every time the remaining wiring is reconnected by a worker, the tag information providing server 100 changes the communication destination in the same manner for the remaining control loops.

[0046] As described above, in the plant operation during the period when the existing system 10 and the new system 20 coexist, the consistency of the plant operation monitoring is provided, and the tag names on the operation screen can be changed automatically and in a short period of time, so that the system migration work efficiency is high, operation errors can be prevented, and the risk of plant shutdown can be reduced. For example, the information provision system can support efficient migration from the existing system 10 to the new system 20.

[0047] (Functions of the information provision system) The information provision system has a tag information provision function, a change notification function, a setting change function, and a system transition status monitoring function in order to provide a single interface for plant operation and monitoring during the period when the existing system 10 and the new system 20 coexist. The tag information provision function, change notification function, setting change function, and system transition status monitoring function of the information provision system will be described below in order.

[0048] For example, in the information providing system shown in FIG. 6, the existing system 10 is an example of a "first system." The controller 5 is an example of a "first controller." The components (I / O, functional blocks) of the controller 5 are an example of a "first component." A tag set in the components (I / O, functional blocks) of the controller 5 is an example of a "first tag." Information relating to the tag set in the components (I / O, functional blocks) of the controller 5 is an example of "first tag information."

[0049] In the information providing system shown in FIG. 6, the newly installed system 20 is an example of a "second system." The controller 40 is an example of a "second controller." The components (I / O, functional blocks) of the controller 40 are an example of a "second component." The tags set in the components (I / O, functional blocks) of the controller 40 are an example of a "second tag." Information relating to the tags set in the components (I / O, functional blocks) of the controller 40 is an example of "second tag information."

[0050] (About tag information provision function) The tag information providing function will be described. For example, the tag information providing function is a function that provides tag information of I / O and functional blocks to the monitoring control application 30. For example, the tag information providing function is a function that the tag information providing server 100 has.

[0051] For example, the tag information providing server 100 has the role of a Global Discovery Server and an Alias ​​Name Server built in compliance with OPC UA Part 12: Discovery and Global Services and Part 17: Alias ​​Names.

[0052] The tag information providing server 100 communicates with the communication relay device 11 of the existing system 10 and the controller 40 of the new system 20, and registers the tag names of the I / O and functional blocks set in the controller 5 of the existing system 10 and the controller 40 of the new system 20 as alias names in the tag information table.

[0053] 7 is a diagram showing an example of a tag information table. As shown in FIG. 7, the tag information table 141 has an alias name, a server index, and an OPC UA Server name associated with the server index. The alias name is a clearly defined alternative name for any control node (for example, an I / O, a controller, etc.) in the information providing system, and information is made public to the monitoring and control application 30. In this embodiment, the alias name is treated as an alternative name for the tag name, and has information such as the namespace name and server index of the OPC UA Server.

[0054] The server index is an index for identifying an OPC UA Server. In this embodiment, the server index of the communication relay device 11 functioning as an OPC UA Server in the existing system 10 is "SA11". The server index of the controller 40 functioning as an OPC UA Server in the new system 20 is "SA40".

[0055] 7, the alias names "AI1", "PID1", and "AO1" are set for the server index "SA11". In addition, the OPC UA Server name "communication relay device (existing system)" is associated with the server index "SA11". This indicates that the tags "AI1", "PID1", and "AO1" are present at the position of the controller 5 under the communication relay device 11 corresponding to the server index "SA11".

[0056] The tag information providing server 100 notifies the information in the tag information table 141 shown in FIG. 7 to the monitoring control application 30 (e.g., an OPC UA client of an HMI) that uses the tag, and the monitoring control application 30 uses the tag information table 141 to communicate with the OPC UA server.

[0057] Here, it is assumed that the tag name "PID1" is set in the controller 40 functioning as an OPC UA Server in the new system 20. The tag information providing server 100 communicates with the controller 4 and updates the tag information table 141 as shown in FIG.

[0058] Fig. 8 is a diagram showing an example of the tag information table after updating. As shown in Fig. 8, a set of the alias name "PID1", the server index "SA40", and the OPC UA Server name "Controller (new system)" is added to the tag information table 141. Note that the tag information table 141 allows different server indexes to be set for the same alias name. For example, the tag information table 141 in Fig. 8 indicates that the tag "PID1" exists in both the controller 5 and the controller 40 under the communication relay device 11.

[0059] (About the change notification function) Next, the change notification function will be described. For example, when the location of a useful tag changes, the change notification function notifies the monitoring control application 30 of such a change. The change notification function is a function that the tag information provision server 100 has.

[0060] When the tag information providing server 100 detects that a server index has changed to another server index for a specific alias name, the tag information providing server 100 notifies the monitoring control application 30 of information on the changed server index for the specific alias name. For example, when the tag information providing server 100 detects that a valid server index for the alias name "PID1" has changed from "SA11" to "SA40", the tag information providing server 100 notifies the monitoring control application 30 that the valid server index for the alias name "PID1" is "SA40".

[0061] The tag information providing server 100 detects a change in the server index as follows: The tag information providing server 100 is in constant communication with the communication relay device 11 and the controller 40.

[0062] The communication relay device 11 transmits information including the alias name of the tag set in the controller 5, its own server index, and quality identification data to the tag information providing server 100. The quality identification data is "GOOD" when the tag is connected to a device by a wire and is accessible. On the other hand, the quality identification data is "BAD" when the tag is not connected to a device by a wire and is inaccessible. The quality identification data corresponds to "communication quality."

[0063] For example, when a tag "Tag PID1" is set in a functional block of the controller 5, a tag "Tag AI1" is connected to device 2a via wiring 3a, and a tag "Tag AO1" is connected to device 2b via wiring 3b, the communication relay device 11 transmits information "alias name: PID1@{server index: SA11} quality identification data: GOOD" to the tag information providing server 100.

[0064] On the other hand, when the tag "Tag PID1" is set in the functional block of the controller 5 and the tags "Tag AI1" and "Tag AO1" are not connected to the devices 2a and 2b via wiring, the communication relay device 11 transmits the information "alias name: PID1@{server index: SA11} quality identification data: BAD" to the tag information providing server 100.

[0065] For example, when the tag "Tag PID1" is set in its own functional block, the tag "Tag AI1" is connected to device 2a via wiring 52a, and the tag "Tag AO1" is connected to device 2b via wiring 52b, the controller 40 transmits the information "alias name: PID1@{server index: SA40} quality identification data: GOOD" to the tag information providing server 100.

[0066] On the other hand, when the tag "Tag PID1" is set in the controller 40's functional block and the tags "Tag AI1" and "Tag AO1" are not connected to the devices 2a and 2b via wiring, the controller 40 sends the information "alias name: PID1@{server index: SA40} quality identification data: BAD" to the tag information providing server 100.

[0067] When the tag information providing server 100 receives the information "alias name: PID1@{server index: SA11} quality identification data: BAD" from the communication relay device 11 and the information "alias name: PID1@{server index: SA40} quality identification data: GOOD" from the controller 40, it detects that the valid server index for the alias name "PID1" has changed from "SA11" to "SA40".

[0068] When the tag information providing server 100 detects that the valid server index for the alias name "PID1" has changed from "SA11" to "SA40," it multicasts a "Model Change Event" containing the detected content to the communication network, thereby allowing the monitoring and control application 30 to know the change in the server index.

[0069] (About the setting change function) Next, the setting change function will be described. For example, the setting change function detects a change in the server index corresponding to a tag and changes the name of the OPC UA Server connected to the tag. The setting change function is a function possessed by the monitoring and control application 30.

[0070] The monitoring and control application 30 has an OPC UA Client function, and communicates with the communication relay device (OPC UA Server) 11, the controller (OPC UA Server) 40, and the tag information providing server 100 via the OPC UA Client function. The OPC UA Client of the monitoring and control application 30 supports a function of receiving a Model Change Event transmitted from the tag information providing server 100.

[0071] The monitoring and control application 30 holds the name of the OPC UA server with which it communicates as a parameter. FIG. 9 is a diagram showing an example of a tag structure held by the monitoring and control application 30. The tag structure shown in FIG. 9 is a data structure related to a tag with the tag name "PID1". A plurality of item names are defined under the tag name "PID1" 60. Various parameters are defined under each item name. For example, various parameters are included under the item name "MV" as shown on the right side of FIG. 9, and one of these parameters is the "OPC server name (similar to the OPC UA server name)".

[0072] For example, when the monitoring and control application 30 receives a “Model Change Event” from the tag information providing server 100 indicating that the valid server index for the alias name “PID1” has changed from “SA11” to “SA40”, the monitoring and control application 30 updates the OPC UA Server name set in “OPC Server Name (same as OPC UA Server Name)” from the name associated with the server index “SA11” to the name associated with “SA40”.

[0073] Although not shown in the figure, the monitoring and control application 30 updates the OPC UA Server name set in the "OPC Server name" included under all item names under the tag name "PID1" 60 from the name associated with the server index "SA11" to the name associated with "SA40." As a result, the monitoring and control application 30 communicates with the controller 40 (new OPC UA Server) for the changed tag "PID1."

[0074] The information regarding each tag is set in the gateway 31 of the monitoring control application 30.

[0075] (System migration status monitoring function) Next, the system migration status monitoring function will be described. For example, the system migration status monitoring function provides a screen that displays the progress status of system migration as a list. The system migration status monitoring function is a function possessed by the tag information providing server 100. In the following description, the screen that displays the progress status of system migration as a list will be referred to as a "progress status screen."

[0076] Fig. 10 is a diagram showing an example of a progress status screen. As shown in Fig. 10, a progress status screen 70 includes a tag name, a migration status, an OPC UA Server name, a latest process value, a data update timestamp, and quality identification data.

[0077] The tag name is a character string assigned to the tag. The migration status expresses the migration status with the color of the marker. The OPC UA Server name is the name of the OPC UA Server that has the tag corresponding to the tag name under it, and for example, the communication relay device 11 of the existing system 10 and the controller 40 of the new system 20 are set. The latest process value is the latest process value corresponding to the tag corresponding to the tag name. The data update timestamp indicates information on the time when the corresponding data was updated (year, month, date, time, etc.). The explanation regarding the quality identification data is the same as the explanation above. In the explanation of FIG. 10, the tag set in the controller 5 of the existing system 10 is written as the "existing tag", and the tag set in the controller 40 of the new system 20 is written as the "new tag".

[0078] The tag information providing server 100 determines that the new tag is communicating normally when the quality identification data corresponding to the existing tag is "BAD" and the quality identification data corresponding to the new tag is "GOOD". For a newly installed tag that is communicating normally, that is, a tag for which migration has been completed, the tag information providing server 100 displays the background color of the square marker indicating the migration status in a first color (e.g., green). For example, for the tag names "AI1" and "AO1" on the progress status screen 70, migration from the existing system 10 to the new system 20 has been completed, and the tag information providing server 100 displays the background color of the markers 71 and 72 in the first color.

[0079] The tag information providing server 100 determines that the existing tag is communicating normally when the quality identification data corresponding to the existing tag is "GOOD" and the quality identification data corresponding to the new tag is "BAD". When the existing tag is communicating normally, that is, when the existing tag is a tag for which migration has not started, the tag information providing server 100 displays the background color of the square marker indicating the migration status in a second color (e.g., yellow). For example, for the tag name "AI2" on the progress status screen 70, migration from the existing system 10 has not started, and the tag information providing server 100 displays the background color of the marker 73 in the second color.

[0080] When the quality identification data corresponding to the existing tag is "BAD" and the quality identification data corresponding to the new tag is "BAD", the tag information providing server 100 determines that the new tag and the existing tag are not communicating normally. When the new tag and the existing tag are not communicating normally, that is, when the tag is in transition, the tag information providing server 100 displays the background color of the square marker indicating the transition status in a third color (e.g., orange). For example, for the tag name "AO2" on the progress status screen 70, the tag information providing server 100 displays the background color of the marker 74a in the third color because the new tag and the existing tag are not communicating normally.

[0081] Furthermore, when the quality identification data corresponding to the existing tag is "BAD" and the quality identification data corresponding to the new tag is "BAD" for a period of time that continues for more than a predetermined time (for example, a default value is 60 seconds), the tag information providing server 100 causes the background color of the square marker indicating the transition status to blink in the fourth color (for example, red) and the fifth color (for example, black) every 500 milliseconds. For example, for the tag name "AO2" on the progress status screen 70, when the quality identification data corresponding to the existing tag is "BAD" and the quality identification data corresponding to the new tag is "BAD" for a period of time that continues for more than a predetermined time, the tag information providing server 100 causes the background color of the marker 74b to blink in the fourth color and the fifth color.

[0082] In FIG. 10, for the sake of convenience, marker 74a and marker 74b are shown separately, but there is only one marker corresponding to the tag name "AO2" on the progress status screen 70, just like the markers corresponding to the other tag names.

[0083] By referring to the progress status screen 70 displayed by the system migration status monitoring function, workers can quickly recognize the progress of the work, which contributes to completing the system migration on schedule.

[0084] (Functional configuration of tag information providing server 100) Next, a configuration example of the tag information providing server 100 shown in FIG. 6 will be described. FIG. 11 is a functional block diagram showing a functional configuration of the tag information providing server according to this embodiment. As shown in FIG. 11, the tag information providing server 100 has a communication unit 110, an input unit 120, a display unit 130, a storage unit 140, and a control unit 150. Note that the functional units of the tag information providing server 100 are not limited to those shown in the figure, and the tag information providing server 100 may have other functional units. Note that the tag information providing server 100 may be realized by a plurality of server computers. The tag information providing server 100 is an example of a "management device."

[0085] The communication unit 110 executes data communication with the communication relay device 11 of the existing system 10 and the monitoring and control application 30 and controller 40 of the new system.

[0086] The input unit 120 inputs various pieces of information to the control unit 150 of the tag information providing server 100. The input unit 120 is a keyboard, a mouse, a touch panel, or the like.

[0087] The display unit 130 displays information output from the control unit 150 of the tag information providing server 100. For example, the display unit 130 displays the progress status screen 70 described with reference to FIG.

[0088] The storage unit 140 stores a tag information table 141 and an information management table 142. The storage unit 140 is realized by a memory, a hard disk, or the like.

[0089] The tag information table 141 stores an alias name, a server index, and an OPC UA Server name associated with the server index in association with each other. The tag information table 141 is the same as that described with reference to FIG.

[0090] The information management table 142 is a table that holds information obtained from the controller 5 of the existing system 10 and the controller 40 of the new system 20. FIG. 12 is a diagram showing an example of the information management table 142. As shown in FIG. 12, the information management table 142 has an alias name, a server index, quality identification data, the latest process value, and a data update timestamp. The explanations regarding the alias name and the server index are the same as those explained in FIG. 7. The explanations regarding the quality identification data, the latest process value, and the data update timestamp are the same as those explained in FIG. 10.

[0091] The control unit 150 is a processing unit that controls the entire tag information providing server 100, and is realized by, for example, a processor. The control unit 150 has a tag information providing unit 151, a change notifying unit 152, and a system transition status monitoring unit 153. The tag information providing unit 151 is an example of an "acquisition unit." The system transition status monitoring unit 153 is an example of a display control unit.

[0092] The tag information providing unit 151 executes the process described above in the “tag information providing function” and provides the monitoring and control application 30 with tag information of I / O and functional blocks.

[0093] The tag information providing unit 151 communicates with the communication relay device 11 of the existing system 10 and the controller 40 of the new system 20 to obtain various information related to the tag. For example, the various information related to the tag includes an alias name, a server index (including an OPC UA Server name), quality identification data, the latest process value, and a data update timestamp. The tag information providing unit 151 registers the obtained tag information in the information management table 142. Note that the various information related to the tag may include information other than the above.

[0094] The tag information providing unit 151 sets the relationship between the alias name and the server index registered in the information management table 142 in the tag information table 141. The tag information providing unit 151 provides the information of the tag information table 141 to the monitoring control application 30.

[0095] The tag information providing unit 151 communicates with the communication relay device 11 of the existing system 10 and the controller 40 of the new system 20, and repeats the above process every time it acquires various pieces of information related to the tag. Other explanations regarding the tag information providing unit 151 are the same as those of the "tag information providing function" described above.

[0096] The change notification unit 152 executes the process described in the "change notification function" above, and when the location of a useful tag changes, notifies the monitoring and control application 30 of the change.

[0097] When the change notification unit 152 detects that a server index (for example, SA11) has changed to another server index (SA40) for a specific alias name based on the information management table 142, the change notification unit 152 notifies the monitoring control application 30 of information on the server index after the change, which is the server index for the specific alias name. For example, the change notification unit 152 multicasts a "Model Change Event" in which information on the specific alias name and the server index after the change is set, to the communication network.

[0098] Change notification section 152 repeatedly executes the above process every time information management table 142 is updated. Other details regarding change notification section 152 are the same as those described above for the "change notification function."

[0099] The system transition status monitoring unit 153 executes the process explained in the above-mentioned "system transition status monitoring function" and causes the display unit 130 to display the progress status screen 70.

[0100] The system transition status monitoring unit 153 identifies the transition status regarding the tag name (alias name) based on the information management table 142, and expresses the transition status by the color of the square marker.

[0101] For example, if, for a certain tag name, the quality identification data corresponding to the server index "SA11" is "BAD" and the quality identification data corresponding to the server index "SA40" is "GOOD," the system transition status monitoring unit 153 determines that the transition of the tag is complete and displays the background color of the square marker indicating the transition status of the certain tag name in a first color (for example, green).

[0102] If, for a certain tag name, the quality identification data corresponding to the server index "SA11" is "GOOD" and the quality identification data corresponding to the server index "SA40" is "BAD", the system transition status monitoring unit 153 determines that the transition of the tag has not begun and displays the background color of the square marker indicating the transition status of the certain tag name in a second color (for example, yellow).

[0103] If, for a certain tag name, the quality identification data corresponding to the server index "SA11" is "BAD" and the quality identification data corresponding to the server index "SA40" is "BAD", the system transition status monitoring unit 153 determines that the tag is in transition and displays the background color of the square marker indicating the transition status of the certain tag name in a third color (for example, orange).

[0104] When the quality identification data corresponding to the server index "SA11" for a certain tag name is "BAD" and the quality identification data corresponding to the server index "SA40" is "BAD" for a period of time that continues for more than a predetermined time (for example, the default value is 60 seconds), the system transition status monitoring unit 153 causes the background color of the square marker indicating the transition status of the certain tag to blink in the fourth color "for example, red" and the fifth color "for example, black" every 500 milliseconds.

[0105] The rest of the explanation regarding the system transition status monitoring unit 153 is the same as the explanation of the "system transition status monitoring function" described above.

[0106] (Functional configuration of a device having a monitoring and control application function) Next, a functional configuration of a device having the functions of the monitoring and control application 30 will be described. Here, the device having the functions of the monitoring and control application 30 will be described as a "control device 200." Note that the control device 200 may be realized by multiple computers, or may be realized as a virtual machine.

[0107] 13 is a functional block diagram showing the functional configuration of the control device according to this embodiment. As shown in FIG. 13, the control device 200 includes a Gateway 210, an input unit 220, a display unit 230, a storage unit 240, and a control unit 250.

[0108] The Gateway 210 is an OPC UA Server or an OPC UA Client, and corresponds to the Gateway 31 described above.

[0109] The input unit 220 inputs various information to the control unit 250 of the control device 200. The input unit 220 is a keyboard, a mouse, a touch panel, or the like.

[0110] The display unit 230 displays information output from the control unit 250 of the control device 200. For example, the display unit 230 displays an operation screen by an HMI, and information on Alarms and Trends.

[0111] The storage unit 240 stores various types of data used by the control unit 250. The storage unit 240 is realized by a memory, a hard disk, or the like.

[0112] The interface providing unit 251 causes an operation screen by the HMI to be displayed on the display unit 230. In addition, the interface providing unit 251 causes the display unit 230 to display information on Alarms and Trends.

[0113] The interface providing unit 251 connects to the communication relay device 11 or the controller 40 via the Gateway 210, and enables access to a valid tag. For example, in the Gateway 210, as described in Fig. 9, a relationship between a tag name and a server index corresponding to the tag name is set, and the Gateway 210 switches the connection destination of the interface providing unit 251 based on the relevant information.

[0114] For example, it is assumed that "SA11" is set as a server index corresponding to the tag name (alias name) "PID1" in the Gateway 210. In this case, when the interface providing unit 251 accesses a valid tag corresponding to the tag name (alias name) "PID1", the connection destination becomes the communication relay device 11 by the Gateway 210, and the tag (tag of PID1) of the controller 5 is accessed via the communication relay device 11.

[0115] On the other hand, it is assumed that "SA40" is set as a server index corresponding to the tag name (alias name) "PID1" in the Gateway 210. In this case, when the interface providing unit 251 accesses a valid tag corresponding to the tag name (alias name) "PID1", the connection destination becomes the controller 40 via the Gateway 210, and the tag of the controller 40 (the tag of PID1) is accessed.

[0116] The execution processing unit 252 has functions corresponding to the various application software 32 described with reference to FIG.

[0117] The setting change unit 253 executes the processing described in the "setting change function" above, detects that the server index corresponding to the tag has changed, and changes the OPC UA Server name corresponding to the tag name set in the Gateway 210.

[0118] The setting change unit 253 receives a Model Change Event transmitted from the tag information providing server 100, and when the server index corresponding to the tag name (alias name) is changed, sets the changed server index.

[0119] For example, when the setting change unit 253 receives from the tag information providing server 100 a “Model Change Event” indicating that the valid server index for the alias name “PID1” has changed from “SA11” to “SA40”, the setting change unit 253 updates the OPC UA Server name set in the “OPC Server Name (same as the OPC UA Server Name)” from the name associated with the server index “SA11” to the name associated with “SA40”. The setting change unit 253 also updates the OPC UA Server names set in the “OPC Server Name” included under all of the subordinate item names 60 of the tag name “PID1” from the name associated with the server index “SA11” to the name associated with “SA40”.

[0120] The rest of the explanation regarding the setting change unit 253 is the same as the explanation of the "setting change function" described above.

[0121] (Processing flow) Next, a process flow of the tag information providing server 100 of this embodiment will be described. Fig. 14 is a flowchart showing the process flow of the tag information providing server 100 of this embodiment. As shown in Fig. 14, the tag information providing unit 151 of the tag information providing server 100 communicates with the communication relay device 11 of the existing system 10 and the controller 40 of the new system 20, acquires various information related to tags, and registers the acquired various information in the information management table 142 (step S101).

[0122] The tag information providing server 100 identifies the relationship between the alias name and the server index based on the information management table 142, and updates the tag information table 141 (step S102). The tag information providing server 100 notifies the monitoring control application 30 (control device 200) of the information in the tag information table 141 (step S103).

[0123] The change notifier 152 of the tag information providing server 100 determines whether or not the server index of the communication relay device 11 has changed to the server index of the controller 40 for a specific alias name based on the information management table 142 (step S104).

[0124] If there has been a change (step S105, Yes), change notification unit 152 multicasts a Model Change Event that sets the relationship between the changed server index and a specific alias name to the communication network (step S106).On the other hand, if there has been no change (step S105, No), change notification unit 152 proceeds to step S107.

[0125] The system transition status monitoring unit 153 of the tag information providing server 100 generates the progress status screen 70 based on the information management table 142 (step S107). The system transition status monitoring unit 153 causes the progress status screen 70 to be displayed on the display unit 130 (step S108).

[0126] If the tag information providing server 100 continues the process (step S109, Yes), the process proceeds to step S101. On the other hand, if the tag information providing server 100 does not continue the process (step S109, No), the process ends.

[0127] (effect) Next, the effect of the information providing system according to this embodiment will be described. The tag information providing server 100 of the information providing system receives first tag information on a first tag set in a component of the controller 5 of the existing system 10, and receives second tag information on a second tag set in a component of the controller 40 of the new system 20. The tag information providing server 100 detects whether or not a valid tag has changed from a first tag to a second tag based on the first tag information and the second tag information, and notifies the monitoring control application 30 (control device 200) of the detection result. The control device 200 of the information providing system changes the access destination of the valid tag to the controller 40 based on the detection result of the tag information providing server 100. This can support efficient implementation of migration from the existing system 10 to the new system 20.

[0128] In addition, according to the information provision system, tag name allocation is changed automatically and in a short period of time, so the delay in resuming control is limited to the time it takes to reconnect the on-site wiring, reducing the risk of plant shutdown.

[0129] Furthermore, the information provision system can shorten the loop transition time and reduce the stress of operators who operate and monitor the plant.

[0130] Furthermore, according to the information providing system, the tag names on the operation screen by the HMI are automatically transferred, so that the time required for transfer from the existing system 10 to the new system 20 can be shortened.

[0131] In addition, the information provision system can provide a consistent plant operation and monitoring environment during the transition period from the existing system 10 to the new system 20, and even if an unforeseen event occurs, it is possible to respond in the same way as usual, except for the tags during cutover.

[0132] Furthermore, a communication relay device 11 is disposed in the existing system 10, and the tag information providing server 100 acquires various information on the first tag (server index, tag name (alias name), quality identification data) from the communication relay device 11, and acquires various information on the second tag (server index, tag name (alias name), quality identification data) from the controller 40. This allows the tag information providing server 100 to easily grasp the status of the tags in the controller 5 of the existing system 10 and the status of the tags in the controller 40 of the new system 20.

[0133] The tag information providing server 100 detects whether or not a tag corresponding to the same identification information has changed from a first tag to a second tag based on the communication quality of the first tag and the communication quality of the second tag. For example, when the communication quality included in the second tag information is better than the communication quality included in the first tag information, the tag information providing server 100 detects a change in a tag corresponding to the same identification information from a first tag to a second tag. This allows the change in a valid tag to be appropriately identified.

[0134] When the control device 200 detects whether the tag has changed from the first tag to the second tag, it changes the access destination for the tag corresponding to the same identification information from the communication relay device 11 to the controller 40. This allows the operator of the new system 20 to easily access the destination tag via the operation screen.

[0135] The tag information providing server 100 displays the migration status from the first tag to the second tag (for example, the progress status screen 70). This allows the manager or the like involved in the system migration project using the hot cutover method to easily understand the migration status of the tag.

[0136] (Hardware) Next, a hardware configuration example of the tag information providing server 100 will be described. Fig. 15 is a diagram for explaining the hardware configuration example. As shown in Fig. 15, the tag information providing server 100 has a communication device 6a, a HDD (Hard Disk Drive) 6b, a memory 6c, and a processor 6d. Moreover, each unit shown in Fig. 15 is connected to each other by a bus or the like.

[0137] The communication device 6a communicates with the communication relay device 11 of the existing system 10, and the monitoring and control application 30, controller 40, etc. of the new system 20. The HDD 6b stores programs and DBs that operate the functions shown in FIG.

[0138] The processor 6d reads out a program that executes the same processes as the respective processing units shown in Fig. 11 from the HDD 6b or the like and loads it in the memory 6c, thereby operating a process that executes the respective functions described in Fig. 11 or the like. For example, this process executes the same functions as the respective processing units possessed by the tag information providing server 100. Specifically, the processor 6d executes a process that executes the same processes as the tag information providing unit 151, the change notifying unit 152, the system transition status monitoring unit 153, and the like.

[0139] In this way, the tag information providing server 100 operates as a tag information providing server that executes an information providing method by reading and executing a program. The tag information providing server 100 can also realize functions similar to those of the above-mentioned embodiment by reading the above program from a recording medium using a medium reading device and executing the read program. Note that the program in these other embodiments is not limited to being executed by the tag information providing server 100. For example, the present invention can be similarly applied to cases where another computer or server executes a program, or where these execute a program in cooperation with each other.

[0140] This program can be distributed via a network such as the Internet. This program can also be recorded on a computer-readable recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, a magneto-optical disk (MO), or a digital versatile disk (DVD), and can be executed by being read out from the recording medium by a computer.

[0141] (others) Some examples of combinations of the disclosed technical features are set out below.

[0142] (1) An information providing system having a control device that provides an operation screen for accessing tags set in a component of a controller that controls equipment in a plant, and a management device that manages information on the tags, The management device includes: an acquisition unit that receives, from the first system, first tag information related to a first tag set in a first component of the first controller, and acquires, from the second system, second tag information related to a second tag set in a second component of the second controller; a change notification unit that detects whether a valid tag has changed from the first tag to the second tag based on the first tag information and the second tag information, and notifies the control device of the detection result; The control device includes: a setting change unit that changes an access destination of the valid tag to the second controller based on the detection result; An information providing system comprising:

[0143] (2) The information providing system according to (1), wherein the first system further includes a communication relay device that relays communication between the control device and the first controller.

[0144] (3) The information providing system described in (2) is characterized in that the acquisition unit acquires, as the first tag information, from the communication relay device, identification information of the communication relay device, identification information of the first tag, and communication quality related to the first tag.

[0145] (4) The information providing system described in (3) is characterized in that the acquisition unit acquires, as the second tag information, from the second controller, identification information of the second controller, identification information of the second tag, and communication quality related to the second tag.

[0146] (5) The information providing system described in (4) is characterized in that the change notification unit detects whether a tag corresponding to the same identification information has changed from the first tag to the second tag based on the communication quality included in the first tag information and the communication quality included in the second tag information.

[0147] (6) The information providing system described in (5) is characterized in that the change notification unit detects a change in the tag corresponding to the same identification information from the first tag to the second tag when the communication quality included in the second tag information is better than the communication quality included in the first tag information.

[0148] (7) The information providing system described in (5) or (6), characterized in that the setting change unit changes the access destination for the tag corresponding to the same identification information from the communication relay device to the second controller based on the detection result.

[0149] (8) The information providing system according to any one of (1) to (7), wherein the management device further comprises a display control unit that displays a transition status from the first tag to the second tag.

[0150] (9) An information providing method for an information providing system having a control device that provides an operation screen for accessing tags set in a component of a controller that controls equipment in a plant, and a management device that manages information on the tags, comprising: the management device receives, from a first system, first tag information regarding a first tag set in a first component of a first controller; the management device acquires, from a second system, second tag information relating to a second tag set in a second component of a second controller; the management device detects whether a valid tag has changed from the first tag to the second tag based on the first tag information and the second tag information, and notifies the control device of the detection result; The control device changes an access destination of the valid tag to the second controller based on the detection result. How information is provided to perform the process.

[0151] (10) To the computer: receiving, from a first system, first tag information regarding a first tag set in a first component of a first controller that controls equipment of a plant; acquiring, from a second system, second tag information relating to a second tag set in a second component of a second controller that controls equipment of the plant; Detecting whether a valid tag has changed from the first tag to the second tag based on the first tag information and the second tag information, and notifying a control device of the detection result. An information providing program that executes processing. [Explanation of symbols]

[0152] 1. Plant 2a,2b,2c,2d equipment 5,40 Controller 10 Existing system 11. Communications relay equipment 20 New System 30 Supervisory Control Applications 31,210 Gateway 50 Process Simulator 70 Progress Screen 100 Tag information server 110 Communications Department 120,220 Input section 130,230 Display section 140,240 storage section 141 Tag Information Table 142 Information Management Table 150,250 Control section 151 Tag Information Department 152 Change Notification Section 153 System Transition Status Monitoring Department 200 Control device 251 Interface Provisioning Department 252 Execution Processing Unit 253 Setting change section

Claims

1. An information providing system including a control device that provides an operation screen for accessing tags set in a component of a controller that controls equipment in a plant, and a management device that manages information on the tags, The management device includes: an acquisition unit that receives first tag information related to a first tag set in a first component of the first controller from the first system and acquires second tag information related to a second tag set in a second component of the second controller from the second system; a change notification unit that detects whether a valid tag has changed from the first tag to the second tag based on the first tag information and the second tag information and notifies the control device of the detection result; The control device includes: a setting change unit that changes an access destination of the valid tag to the second controller based on the detection result; An information providing system comprising:

2. 2. The information providing system according to claim 1, wherein the first system further comprises a communication relay device that relays communication between the control device and the first controller.

3. The information providing system according to claim 2, characterized in that the acquisition unit acquires, as the first tag information, from the communication relay device, identification information of the communication relay device, identification information of the first tag, and communication quality related to the first tag.

4. The information providing system according to claim 3, characterized in that the acquisition unit acquires, as the second tag information, from the second controller, identification information of the second controller, identification information of the second tag, and communication quality related to the second tag.

5. The information provision system described in claim 4, characterized in that the change notification unit detects whether a tag corresponding to the same identification information has changed from the first tag to the second tag based on the communication quality included in the first tag information and the communication quality included in the second tag information.

6. The information provision system described in claim 5, characterized in that the change notification unit detects a change in a tag corresponding to the same identification information from the first tag to the second tag when the communication quality included in the second tag information is better than the communication quality included in the first tag information.

7. The information providing system according to claim 5 or 6, characterized in that the setting change unit changes the access destination for the tag corresponding to the same identification information from the communication relay device to the second controller based on the detection result.

8. 7. The information providing system according to claim 1, wherein the management device further comprises a display control unit that displays a transition status from the first tag to the second tag.

9. 1. An information providing method for an information providing system having a control device that provides an operation screen for accessing tags set in a component of a controller that controls equipment in a plant, and a management device that manages information on the tags, comprising: the management device receives, from a first system, first tag information regarding a first tag set in a first component of a first controller; the management device acquires, from a second system, second tag information relating to a second tag set in a second component of a second controller; the management device detects whether a valid tag has changed from the first tag to the second tag based on the first tag information and the second tag information, and notifies the control device of the detection result; the control device changes an access destination of the valid tag to the second controller based on the detection result; How information is provided to perform the process.

10. On the computer, receiving, from a first system, first tag information regarding a first tag set in a first component of a first controller that controls equipment of a plant; acquiring, from a second system, second tag information relating to a second tag set in a second component of a second controller that controls equipment of the plant; Based on the first tag information and the second tag information, it is detected whether or not a valid tag has changed from the first tag to the second tag, and the detection result is notified to a control device. An information providing program that executes processing.

Images