Automatic configuration of field devices for industrial plants

Abstract

A computer-implemented method (100) for configuring a field device (2) used in an industrial plant (1) comprises the steps of creating an instance (2a) of a configuration of the field device from device description information of the field device and / or a template configuration T, the template configuration T being stored in association with the field device and / or in association with a type of the field device; setting values of configuration parameters (2b) in the instance to default values given by the device description information and / or values given by the template T; determining semantic meanings (2b*) of the configuration parameters (2b) in the instance; obtaining from a data store (3) configuration parameter values (3b) and semantic meanings (3b*) stored in association with the field device; writing (150) each value obtained from the data store (3) to a configuration parameter (2b) in the instance, wherein the semantic meaning (2b*) of the instance matches the semantic meaning (3b*) of the value; and providing (170) the field device with the configured instance.

Description

Technical Field

[0001] This invention relates to the configuration of field devices in industrial plants, and more particularly to the batch configuration of a number of field devices. Background Technology

[0002] Industrial plants used to execute industrial processes include multiple field devices connected to a distributed control system (DCS) via a network within the industrial plant. These field devices need to be configured before they can perform their intended functions within the industrial plant. WO2021 / 249655A1 discloses a method for configuring field devices based on an OPCUA server of the same type of already configured field devices.

[0003] Field device configuration is typically performed manually using a user interface defined by the Electronic Device Description (EDD) or Device Encapsulation (DP) of the field device. Summary of the Invention

[0004] Therefore, the object of the present invention is to automate the configuration of field devices, at least in part.

[0005] This objective is achieved by the method according to the main claim. Further advantageous embodiments are detailed in the dependent claims.

[0006] This invention provides a computer-implemented method for configuring field devices used in industrial plants.

[0007] The method begins by creating a configuration instance for the field device. This instance defines a set of configuration parameters and stores the values ​​of these parameters. Specifically, each configuration parameter may be labeled with a name, which serves as a "handle" for accessing that configuration parameter. The instance is created based on the field device's device description information and / or template configuration T, which is stored in association with the field device and / or with the type of the field device. Specifically, the device description information may include the field device's Electronic Device Description (EDD) and / or Device Package Description (DP).

[0008] In this example, the configuration parameter values ​​are set to default values ​​provided by the device description information and / or values ​​provided by the template T. The main difference between the default values ​​provided by the device description information and those provided by the template T is that the default values ​​are provided by the device manufacturer, while the parameters in the template are provided by the factory operator. Specifically, the EDD and DP, which serve as device description information, are industry standards used to describe the functionality of field devices. The same field device can be used in many types of industrial equipment, but the field device will always have the same EDD and / or DP. Field devices can be shipped with the EDD and / or DP, but the EDD and / or DP can also be provided or updated later by the field device manufacturer.

[0009] In contrast, the values ​​given by template T are specific to the field device and / or the type of field device, and also specific to the industrial plant that uses it. Specifically, template T can be created by a plant operator installing multiple field devices of the same type, and it can store values ​​for configuration parameters that need to be set to the same value across many field devices. For example, a field device may have an option to automatically restart or wait for the operator to press a physical key before restarting, and this option may need to be set to "automatic restart" in all field devices in the industrial plant. Furthermore, field devices handling fresh water from a water supply system may need to know the degree of water hardness, which is common to all field devices in that particular plant.

[0010] Device description information and / or template T may have already populated many configuration parameters of the field device with values. However, at least some configuration parameter values ​​are specific to each individual field device. In order to populate these configuration parameters with values, and / or to overwrite already set configuration parameters with new values, the semantic meaning of the configuration parameters in the instance is determined. From the data storage, the configuration parameter values ​​and semantic meanings stored in association with the field device to be configured are obtained. The association with the field device to be configured can be established, for example, via the name or other identifier of the field device, which is stored in the data storage along with the values ​​of the configuration parameters and their semantic meanings.

[0011] Each value obtained from the data storage is written into the configuration parameters of the instance, and the semantic meaning of the instance is matched with the semantic meaning of the value from the data storage. The configured instance is then provided to the field device.

[0012] The names of the configuration parameters on field devices are unique identifiers for these parameters, but they are not standardized. Instead, each manufacturer of the field device is free to assign names in whatever way they deem appropriate. For example, a pressure setpoint might be named "pset" on one field device, "set-p" on another, and "p-set-bar" on a third. The names can even change with subsequent revisions or updates to the field device.

[0013] Therefore, when configuration parameters are stored in data storage associated with their names, the operator entering the configuration parameters needs to know which field device is in use and at which revision or update level. If the operator does not have this information or the information is no longer accurate, they may refer to the configuration parameters with an incorrect name that the field device to be configured does not know. The same situation can occur if the operator confuses field devices with different names for configuration parameters when entering values ​​for several different field devices of the same type. As a result, when an instance of configuration is provided for a field device, the configuration parameter set to a specific value in that instance will not be written to the field device. The field device will operate using different values ​​of that configuration parameter, or even refuse to start if the missing value of the configuration parameter is the value required for startup. This is particularly disadvantageous if the actual provision is done as an unattended task, such as in batches overnight for many field devices.

[0014] In contrast, when configuration parameters are referenced to their semantic meaning, such as "pressure setpoint" in a data storage device, the stored value is written precisely to the configuration variable whose semantic meaning is resolved to an instance of that value's semantic meaning. This eliminates the aforementioned sources of error, making the automatic configuration of field devices more reliable. Furthermore, the data storage device is easier for plant operators to read and interpret. For example, a table showing the contents of the data storage device can be sorted by the column "semantic meaning," and all values ​​related to the semantic meaning "pressure setpoint" will be shown in a single box. Sort by the name of the configuration parameters is far less meaningful, as even names that ultimately resolve to the same semantic meaning may be scattered throughout the alphabet.

[0015] In a particularly advantageous embodiment, for the same configuration parameter, the value obtained from template T takes precedence over the default value given by the device description information. As mentioned above, the value from template T is motivated by plant-specific knowledge and can therefore be more appropriate than a fixed default value that may not take into account the specific industrial plant where the field device will be used.

[0016] Similarly, in another particularly advantageous embodiment, for the same configuration parameter, the value obtained from the data storage takes precedence over the default value given by the device description information and / or the value obtained from the template T. A value fixed considering the purpose of the particular field device is more likely to be appropriate than a value fixed solely based on general knowledge about the industrial plant, or even without such knowledge.

[0017] In another particularly advantageous embodiment, determining the semantic meaning includes retrieving the semantic meaning from a library in which the semantic meaning is stored in association with the names of field devices and configuration parameters. In the example above, if different field devices are named pressure setpoints “pset,” “set-p,” and “p-set-bar,” the library can store the semantic meaning of “pressure setpoint” associated with each field device and the corresponding name of the pressure setpoint. One method of creating and using such a library is described in detail in the published common pending application EP3929673A1.

[0018] In another particularly advantageous embodiment, multiple field devices connected to the network of an industrial plant are provided in batches. That is, a single data storage device can store the values ​​of configuration parameters for a large number of field devices, and the task of fixing the configuration parameters in the data storage device can be time-independent of the actual rollout of the configured instances. For example, rollout can be performed at night, when field devices may be temporarily inactive with less inconvenience, while their configuration parameters are updated. For example, updating certain configuration parameters may require restarting the field devices.

[0019] Another reason for performing a rollout at a later time could be network load. That is, instances of providing configuration to multiple field devices can be performed in response to predetermined conditions regarding the load on the network. Specifically, if only limited bandwidth is available, provisioning can be performed when less bandwidth is required for normal operation of the industrial plant. Furthermore, provisioning to different field devices can be scheduled at different times. If the field devices are connected to a network with a bus topology, this is a shared medium, and providing all field devices simultaneously could lead to congestion on that shared medium. Additionally, the schedule can be modified to ensure that not too many field devices are being updated in certain segments of the plant and momentarily unresponsive at exactly the same time, thus keeping that segment operational as a whole at all times.

[0020] Exemplary scenarios with bandwidth limitations include situations where field devices are connected to the network via two-wire connections and / or via wireless connections limited to a duty cycle of at most 1%. In particular, if a duty cycle limitation exists, a central management entity sending configuration instances to numerous field devices may quickly exhaust its duty cycle and then be temporarily unable to send any further commands to the field devices.

[0021] In another particularly advantageous embodiment, the user is prompted to enter configuration parameter values ​​that are required to start the field device, but are not provided by any of the device description information, template T, and data storage. In this way, unintentional omissions in the data storage may be discovered before the configuration instance is rolled out to the field device. For example, a nighttime rollout of a configuration with omitted critical parameters can be avoided, preventing the field device from malfunctioning overnight.

[0022] Specifically, field devices can be devices that directly and physically interact with an industrial plant and / or with an industrial process performed on that industrial plant. Specifically, field devices can be sensor devices and / or actuator devices, where sensor devices provide at least one measured value of a physical quantity to a distributed control system (DCS) of the industrial plant, and actuator devices initiate control commands received from the DCS on the plant.

[0023] In a particularly advantageous embodiment, the method steps described so far can be performed by an asset management system (AMS) for an industrial plant. This AMS can maintain the configuration parameter values ​​of all field devices in files in offline storage. Specifically, the AMS can manage or even control the master data storage.

[0024] In another advantageous embodiment, the method further includes performing at least one industrial process on the industrial plant with the participation of new field devices. In this context, the method offers the advantage of more reliable industrial processes because all field devices in the industrial plant are more likely to actually operate at the expected values ​​of configuration parameters stored in data storage. Furthermore, the risk of industrial process interruption due to significant omissions in the configuration is reduced.

[0025] This method is implemented by a computer and therefore can be implemented in software. Therefore, the present invention also provides a computer program comprising machine-readable instructions that, when executed on one or more computers and / or computing instances, cause the one or more computers and / or computing instances to perform the above-described method. In particular, process controllers, microcontrollers, and other electronic devices capable of executing machine-readable instructions can also be considered computers. Computing instances include virtual machines, containers, and any other execution environments in which machine-readable instructions can be executed. The present invention also relates to machine-readable data carriers and / or downloadable products having computer programs. Downloadable products are products that can be sold in online stores for immediate implementation via download. The present invention also provides one or more computers and / or computing instances having one or more computer programs and / or having one or more machine-readable data carriers and / or downloadable products. Attached Figure Description

[0026] In the following description, the invention is illustrated using accompanying drawings, which are not intended to limit the scope of the invention.

[0027] The attached diagram shows:

[0028] Figure 1 An exemplary embodiment of a method 100 for configuring field devices 2 used in an industrial plant 1;

[0029] Figure 2 The exemplary settings of method 100 can be adopted. Detailed Implementation

[0030] Figure 1 This is a schematic flowchart of an embodiment of a method 100 for configuring field devices 2 used in an industrial plant 1.

[0031] In step 110, configuration instance 2a of field device 2 is created from the following:

[0032] • Device description information for field device 2, and / or

[0033] • Template configuration T stored in association with field device 2 and / or in association with the type of field device 2.

[0034] exist Figure 1 In the example shown, the device description information includes an Electronic Device Description (EDD) and / or a Device Package Description (DP) as Field Device 2. However, device description information may also be provided in any other suitable form or format.

[0035] In step 120, the value of configuration parameter 2b in instance 2a is set to the default value given by EDD and / or DP, and / or the value given by template T. Here, according to box 121, for the same configuration parameter 2b, the value obtained from template T may take precedence over the default value given by EDD and / or DP.

[0036] In step 130, the semantic meaning 2b* of the configuration parameter 2b in instance 2a is determined. According to block 131, this may include obtaining the semantic meaning 2b* from a library in which the semantic meaning 2b* is stored in association with the field device 2 and with the name of the configuration parameter 2b.

[0037] In step 140, the value of the configuration parameter 3b stored in association with the field device 2 and its semantic meaning 3b* are obtained from the data storage 3.

[0038] In step 150, each value obtained from the data storage 3 is written into the configuration parameter 2b in instance 2a, the semantic meaning 2b* of which matches the semantic meaning 3b* of the value. Here, according to box 151, for the same configuration parameter 2b, the value obtained from the data storage 3 may take precedence over the default value given by EDD and / or DP, and / or over the value obtained from template T.

[0039] exist Figure 1 In the example shown, in step 160, the user is prompted to enter the value of configuration parameter 2b, which is required to start field device 2, but is not provided by any of EDD, DP, template T and data storage 3, in order to avoid unintentional omission.

[0040] In step 170, an example 2a of the configuration is provided to the field device 2.

[0041] According to box 171, multiple field devices connected to network 1a of industrial plant 1 can be provided in bulk.

[0042] According to box 171a, in response to a predetermined condition that the load on network 1a is met, instance 2a of providing configuration to multiple field devices 2 is executed.

[0043] In step 180, at least one industrial process is performed on industrial plant 1 with the participation of field device 2.

[0044] Figure 2 An exemplary scenario in which method 100 can be used is illustrated. An industrial plant 1 includes multiple field devices 2, 2'. The field devices 2, 2', a distributed control system (DCS), and an asset management system (AMS) are connected to a network 1a of the industrial plant 1. The AMS houses a data storage device 3, in which the values ​​of configuration parameters 3b are stored in association with the field devices 2, 2' and semantic meanings 3b*. The AMS also stores electronic device descriptions (EDDs) and / or device encapsulation descriptions (DPs) as device description information for the field devices 2, 2'.

[0045] exist Figure 2 In the scenario shown, a configuration instance 2a for field device 2 is created. In this instance 2a, the value of configuration parameter 2b is partly composed of values ​​from EDD and / or DP, partly composed of values ​​from template T, and partly composed of values ​​from data storage 3. If the value from data storage 3 matches the semantic meaning 2b* of configuration parameter 2b in instance 2a, then the value from data storage 3 is written into configuration parameter 2b in instance 2a.

[0046] List of reference numerals in the attached diagram:

[0047] 1 Industrial plant

[0048] 2.2' Field Equipment

[0049] 2a Example of configuration for field device 2

[0050] Configuration parameters in 2b of 2a

[0051] The semantic meaning of configuration parameter 2b*

[0052] 3 Data Storage

[0053] Configuration parameters of 3b in data storage 3

[0054] The semantic meaning of configuration parameter 3b

[0055] 100 Method for configuring field device 2 110 Create instance 2a 120 Set configuration parameter 2b to default value 130 Determine the semantic meaning of configuration parameter 2b 2b*

[0056] 140 Obtain configuration parameter 3b from data storage 3. 150 If semantic meanings 2b* and 3b* match, write the value from data storage 3. 160 Prompt the user that the value of configuration parameter 2b is missing.

[0057] 170 Providing field devices using configuration example 2a 171 Providing multiple field devices in bulk 2

[0058] 171a provides 180 pairs of industrial plants 1 to execute industrial processes in response to conditions regarding the load on network 1a.

[0059] AMS Asset Management System

[0060] EDD electronic device description

[0061] DCS Distributed Control System

[0062] DP device packaging

[0063] T Template Configuration

Claims

1. A computer-implemented method (100) for configuring field devices (2) used in an industrial plant (1), comprising the steps of: • Create (110) an instance (2a) of a configuration for the field device (2) based on the device description information of the field device (2) and / or based on the template T configuration, wherein the template T configuration is stored in association with the field device (2) and / or in association with the type of the field device (2); • Set (120) the value of the configuration parameter (2b) in the instance (2a) to the default value given by the device description information and / or the value given by the template T; • Determine the semantic meaning of the configuration parameter (2b) in the instance (2a) described in (130). ), wherein the semantic meaning (2b) The determination of (130) includes obtaining (131) the semantic meaning (2b) from the library. The semantic meaning described in the library (2b) The configuration parameters (2b) are stored in association with the names of the field device (2) and the configuration parameters (2b); • Obtain (140) from the data storage (3) the values ​​and semantic meanings (3b) of the configuration parameters (3b) stored in association with the field device (2). ); • In response to the semantic meaning of the configuration parameter (2b) in the instance (2a) The semantic meaning of the obtained value of the configuration parameter (3b) and the configuration parameter (3b) Matching, each value obtained from the data storage (3) is written (150) into the configuration parameters (2b) of the instance (2a) to populate configuration parameters not yet set from the template with values, and to overwrite already set configuration parameters with new values; and • Provide (170) the field device (2) using the instance (2a) of the configuration described above.

2. The method according to claim 1, wherein the device description information includes the Electronic Device Description (EDD) and / or Device Package Description (DP) of the field device (2).

3. The method (100) according to any one of claims 1 to 2, wherein for the same configuration parameter (2b), the value obtained from the template T takes precedence over the default value (121) given by the device description information.

4. The method (100) according to any one of claims 1 to 2, wherein for the same configuration parameter (2b), the value obtained from the data storage (3) takes precedence over (151) the default value given by the device description information and / or the value obtained from the template T.

5. The method (100) according to any one of claims 1 to 2, wherein multiple field devices (2) are provided in batches (171) to a network (1a) of the industrial plant (1).

6. The method (100) according to claim 5, wherein an instance (2a) of providing configuration to the plurality of field devices (2) is performed in response to a predetermined condition that the load on the network (1a) is satisfied.

7. The method (100) according to any one of claims 1 to 2 and 6, further comprising: Prompt (160) The user enters the value of configuration parameter (2b), which is required to start the field device (2), but is not provided by any of the device description information, the template T and the data storage (3).

8. The method (100) according to any one of claims 1 to 2, 6, wherein the field device (2) is a device that directly physically interacts with an industrial plant and / or with an industrial process performed on the industrial plant (1).

9. The method (100) according to claim 8, wherein the field device (2) is a sensor device and / or an actuator device, the sensor device being used to provide at least one measurement of a physical quantity to the distributed control system (DCS) of the industrial plant (1), and the actuator device being used to execute control commands received from the DCS of the industrial plant (1).

10. The method (100) according to any one of claims 1 to 2, 6, and 9, wherein the creation step, setting step, determining step, obtaining step, and writing step of the method are performed by the asset management system (AMS) of the industrial plant (1).

11. The method (100) according to any one of claims 1 to 2, 6, and 9, further comprising performing (180) at least one industrial process on the industrial plant (1) with the participation of the field equipment (2).

12. A computer program product comprising machine-readable instructions that, when executed on one or more computers, cause the one or more computers to perform the method (100) according to any one of claims 1 to 11.

13. A machine-readable data carrier and / or downloadable product having a computer program product according to claim 12.

14. One or more computers having a computer program product according to claim 12 and / or a machine-readable data carrier or downloadable product according to claim 13.

Images