AUTOMATIC CONFIGURATION OF REPLACED FIELD DEVICES IN AN INDUSTRIAL PLANT

Description

FIELD OF THE INVENTION

[0001] The invention relates to the configuration of field devices in industrial plants that are to replace previously used field devices.BACKGROUND

[0002] Industrial plants for executing industrial processes comprise a plurality of field devices that are connected to a distributed control system, DCS, via a network of the industrial plant. Field devices need to be configured before they can perform their intended function in the industrial plant. WO 2021 / 249 655 A1 discloses a method to configure a field device based on an OPC UA server of an already configured field device of the same type.

[0003] When a field device needs to be replaced by a new one temporarily (for maintenance of the field device) or permanently (if the field device is broken), the new field device very frequently needs to be configured manually.

[0004] WO 2015 / 075 615 A1 discloses a method for replacing a first field device with a second field device. A device description file associated with the first field device is retrieved and analyzed. A first object is generated by mapping parameters of the second field device to one or more parameters of the first field device based on a first index and a second index. A configuration file for the second field device is generated based on this generated first object and the device description file. The configuration file is then transmitted to the second field device.

[0005] EP 3 309 632 A1 discloses a method for implementing an automatic on-demand configuration or re-configuration in a building automation system or sub-system during runtime based on information or data representing a plurality of devices of the building automation system. In a unified information model, information or data is commonly available in a machine-readable format based on a semantic abstraction of the devices.

[0006] CA 2 559 642 A1 discloses a converter for abstracting network devices away from manufacturer specific syntax and / or semantic capabilities by making the network devices configuration independent through syntax and / or semantic conversion. The converter allows the user to choose from any input module to program end devices.

[0007] (H. Koziolek et al. "OpenPnP: A Plug-and-Produce Architecture for the Industrial Internet of Things", 2019 IEEE / ACM 41st International Conference on Software Engineering: Software Engineering in Practice, doi: 10.1109 / ICSE-SEIP.2019.00022, pages 131-140) discloses the vendor-neutral OpenPNP reference architecture that can largely automate the configuration and integration tasks for the commissioning of field devices.OBJECTIVE OF THE INVENTION

[0008] It is therefore the objective of the invention to at least partially automate the configuration of a new field device that replaces a previously used field device in the industrial plant.

[0009] This objective is achieved by a method according to the main claim. Further advantageous embodiments are detailed in the dependent claims.DISCLOSURE OF THE INVENTION

[0010] The invention is defined by the appended claims. Embodiments and examples not covered by the claims are presented to illustrate, and facilitate the understanding of, the claimed invention.

[0011] The invention provides a computer-implemented method for configuring a new field device in an industrial plant that replaces a previously used field device in the industrial plant.

[0012] The method starts with detecting that the new field device is connected to a network of the industrial plant. This may be done in any suitable manner. For example, a user, such as a plant operator, may enter the new field device in a database of field devices. But any suitable automatic method may be used as well.

[0013] Driver information and / or software for the new field device is obtained. This driver information and / or software allows communication with the new field device and is indicative of which configuration parameters of the new field device may be set, and how. For example, the driver information may comprise a list of names of configuration parameters, and optionally information regarding which type of value (such as strings, integer values in a particular numeric range, or Boolean variables) can be written into each configuration parameter. The driver information may also comprise instructions how to write a given value to a given parameter, and / or a driver software may provide an API call for writing a value to a parameter.

[0014] The previously used field device is determined. This is the field device that is to be replaced by the new field device. For example, the plant operator may flag the old field device as non-functional in the database of field devices. But any suitable automatic method may be used as well. The new field device may, for example, take the place of the previously used field device in the sense that it is mounted in the same location as the previously used field device. But it may also be mounted in a different location. The new field device only needs to provide, to the industrial plant as a whole, the functionality that the previously used field device previously provided.

[0015] It is determined whether the driver information and / or software for the new field device matches the previously used driver information and / or software for the previously used field device. If this is the case, i.e., if the old field device has been replaced by an identical new one of the same model and version, then the new field device is provisioned with the previously used configuration parameters for the previously used field device. That is, all configuration parameters of the new field device may be set to the values that are still on file for the previously used field device. Even without knowing any details about the semantic meanings of the configuration parameters, copying over all configuration parameters makes the new field device behave in exactly the same manner as the previously used field device.

[0016] But this is not the normal case in an industrial plant. Because field devices have a service life that is much longer than the innovation cycle for updates and upgrades, and the service life may be extended further by repairs, it is quite common that an identical copy of the previously used field device is no longer available at the time where this field device finally fails. This means that a different field device will need to be configured to take over the functionality of the previously used one.

[0017] To this end, an instance of a configuration for the new field device is created from device description information of the new field device. In particular, such device description information may comprise an Electronic Device Description, EDD, and / or a Device Package, DP, of the new field device. EDDs and DPs are industry standards for describing the functionality of field devices. However, these standards do not yet guarantee that one and the same parameter may be written to every field device in the same manner. In particular, names of parameters are not standardized. Rather, every manufacturer of field devices is free to assign names in any manner he deems fit. For example, a pressure set-point may be named "pset" in one field device, "set-p" in another and "p-set-bar" in a third.

[0018] Therefore, semantic meanings of new configuration parameters in the newly created instance of the configuration are determined. Likewise, semantic meanings of previously used configuration parameters for the previously used field devices are determined. This may be done by using lookup tables, or by any other suitable form of analysis. In the example mentioned above, all three names for the pressure set-point would resolve to the common semantic meaning "pressure set-point".

[0019] If the semantic meaning of a new configuration parameter matches the semantic meaning of a previously used configuration parameter, then the value of this new configuration parameter is set to the value of this previously used configuration parameter. That is, the value of the previously used configuration parameter that is still on file for the previously used field device is re-used in the newly created configuration for the new field device. Herein, "on file" may, in particular, comprise an offline data set (persistence storage) of a management system where configuration parameters are stored in association with field devices.

[0020] After the values of the configuration parameters have been set in this manner, the new field device is provisioned with the new instance of the configuration.

[0021] It is not required, and also not probable, that all values of the new configuration parameters will be filled with corresponding values from the previously used configuration parameters. For example, newer versions of field devices and / or corresponding drivers tend to have more functionality than old versions, so they offer configuration parameters for which there is no counterpart in the previously used field device. Also, old functionality that is no longer needed may be deprecated over time, so that some of the old configuration parameters have nowhere to go in the configuration of the new field device. But it can be expected that the new field device will be provisioned with at least a subset of the configuration parameters that is sufficient to get it working somehow. Every single configuration parameter of the new field device that may be automatically set saves time and counts here.

[0022] In particular, this is very valuable in situations where a field device suddenly fails. If this happens on a weekend or holiday, only a technician who knows how to replace field devices, but has no deeper knowledge about the details of the industrial process being run with the field device, might be available at short notice. This will suffice to get the industrial process going again because the new field device can be automatically configured at least partially. Fine tuning of parameters can then be performed later, when an engineer with knowledge about the industrial process is available.

[0023] In a particularly advantageous embodiment, the detecting that the new field device is connected to a network of the industrial plant may comprise listening for discovery requests broadcasted by the new field device on the network. For example, on an Ethernet network, a newly connected device may broadcast DHCP requests. Alternatively or in combination to this, the network may be scanned and / or probed for newly connected devices. For example, numeric addresses that are available in the network may be enumerated one by one to check whether a newly connected device responds.

[0024] In a particularly advantageous embodiment, to obtain driver information and / or software, an identifier of the new field device may be determined. Based on this identifier, the driver information and / or software may be obtained from at least one library of driver information and / or software. This library can be a local one, but it can also comprise a library that is accessible over a network.

[0025] In a particularly advantageous embodiment, the determining of the previously used field device may comprise detecting that a previously used field device is no longer reachable on the network. Alternatively or in combination to this, it may be detected that the new field device is connected to a network port to which a previously used field device was previously connected. If one previously used field device goes offline and one new field device is connected, and in particular if it is connected to the same network port as the previously used field device, it is very probable that the new field device is intended to replace the old one.

[0026] In a particularly advantageous embodiment, the determining whether the driver information and / or software for the new field device matches the previously used driver information and / or software for the previously used field device may comprise determining whether the type of the new field device matches the type of the previously used field device. It may then be determined whether version information of the driver information and / or software for the new field device matches the corresponding version information of the previously used driver information and / or software for the previously used field device. If both the type and the version information match, then the driver information and / or software for the new field device may be considered to match the previously used driver information and / or software, so that the previously used configuration parameters may be re-used without considering and understanding their semantic meanings.

[0027] When the instance of a configuration for the new field device is created, the configuration parameters of this instance may be populated with values from multiple sources. For example, values of configuration parameters in the instance may be set to default values given by the device description information. If there is a template configuration stored in association with the type of the new field device, configuration parameters in the instance may also be set to values given in this template configuration. In particular, these values may partially supersede the values given by the device description information, thereby including plant-specific knowledge into the instance of the configuration. Such plant-specific knowledge may also be included by setting values of configuration parameters in the instance to values obtained from an engineering system of the industrial plant.

[0028] In a further particularly advantageous embodiment, the determining of the semantic meaning of a configuration parameter may comprise obtaining the semantic meaning from a library where it is stored in association with the respective field device and with a name of the configuration parameter. In the example mentioned above, if different field devices name a pressure set-point "pset", "set-p" and "p-set-bar", the library may store the semantic meaning "pressure set-point" in association with each field device and the respective name for the pressure set-point. One way of creating and using such a library is detailed in published co-pending application EP 3 929 673 A1.

[0029] In a further particularly advantageous embodiment, at least one correspondence between a previously used configuration parameter and a new configuration parameter may be received from a user via a user interface. It may then be determined that this new configuration parameter on the one hand and this previously used configuration parameter on the other hand have a matching semantic meaning. In this manner, additional knowledge of the user with respect to correspondences between configuration parameters may be exploited.

[0030] The new field device may, in particular, be a device that is in direct physical interaction with an industrial plant, and / or with an industrial process executed on this industrial plant. In particular, the new field device may be a sensor device that is to supply at least one measurement value of a physical quantity to a distributed control system, DCS, of the industrial plant, and / or an actor device that is to enact a control command received from the DCS on the plant.

[0031] In a particularly advantageous embodiment, the method steps described so far may be performed by an Asset Management System, AMS, of the industrial plant. Such an AMS may keep values of configuration parameters for all field devices on file in offline storage, so that they are still available if a field device is replaced and the previously used field device is no longer accessible online.

[0032] In a further advantageous embodiment, the method further comprises executing at least one industrial process on the industrial plant with the participation of the new field device. In this context, the method provides the advantage that the industrial process can resume faster after the field device has been replaced with a new one.

[0033] The method is computer-implemented and can therefore be embodied in software. The invention therefore also provides computer program, comprising machine-readable instructions that, when executed on one or more computers and / or compute instances, cause the one more computers and / or compute instances to perform the method described above. In particular, process controllers, microcontrollers and other electronic devices that are able to execute machine-readable instructions may be regarded as computers as well. Compute instances comprise virtual machines, containers and any other execution environments in which machine-readable instructions may be executed. The invention also relates to a machine-readable data carrier, and / or a download product, with the computer program. A download product is a product that may be sold in an online shop for immediate fulfillment by download. The invention also provides one or more computers and / or compute instances with the one or more computer programs, and / or with the one or more machine-readable data carriers and / or download products.DESCRIPTION OF THE FIGURES

[0034] In the following, the invention is described using Figures without any intention to limit the scope of the invention. The Figures show: Figure 1: Exemplary embodiment of the method 100 for configuring a new field device 3; Figure 2: Exemplary setting where the method 100 may be employed.

[0035] Figure 1 is a schematic flow chart of an embodiment of the method 100 for configuring a new field device 3. This field device 3 is to replace a previously used field device 2 in an industrial plant 1.

[0036] In step 110, it is detected that the new field device 3 is connected to a network 1a of the industrial plant 1.

[0037] According to block 111, the detecting may comprise listening for discovery requests broadcasted by the new field device 3 on the network 1a. According to block 112, the detecting may comprise scanning and / or probing the network 1a for newly connected devices.

[0038] In step 120, driver information and / or software 3a for the new field device 3 is obtained. This driver information and / or software 3a allows communication with the new field device 3 and is indicative of which configuration parameters 3b of the new field device 3 may be set, and how.

[0039] According to block 121, the obtaining of driver information and / or software 3a may comprise determining an identifier of the new field device 3. According to block 122, based on this identifier, the driver information and / or software 3a may be obtained from at least one library of driver information and / or software.

[0040] In step 130, the previously used field device 2 is determined. This is the field device that is to be replaced by the new field device 3.

[0041] According to block 131, this determining may comprise detecting that a previously used field device 2 is no longer reachable on the network 1a. Alternatively or in combination to this, according to block 132, it may be detected that the new field device 3 is connected to a network port to which a previously used field device 2 was previously connected.

[0042] In step 140, it is determined whether the driver information and / or software 3a for the new field device 3 matches the previously used driver information and / or software 2a for the previously used field device 2. If this is the case (truth value 1), in step 150, the new field device 3 is provisioned with the previously used configuration parameters 2b for the previously used field device 2.

[0043] According to block 141, the determining whether the driver information and / or software 3a for the new field device 3 matches the previously used driver information and / or software 2a may comprise determining whether the type of the new field device 3 matches the type of the previously used field device 2. According to block 142, it may then be determined whether version information of the driver information and / or software 3a for the new field device matches the corresponding version information of the previously used driver information and / or software 2a for the previously used field device 2.

[0044] If the driver information and / or software 3a for the new field device 3 does not match the previously used driver information and / or software 2a for the previously used field device 2 (truth value 0 in step 140), in step 160, an instance 3c of a configuration for the new field device 3 is created from device description information of the new field device 3. In the example shown in Figure 1, the device description information comprises an Electronic Device Description, EDD, and / or a Device Package, DP, of the new field device 3. The creating of the instance 3c may comprise: setting values of configuration parameters 3b in the instance 3c to default values given by the EDD and / or the DP, according to block 161; and / or setting values of configuration parameters 3b in the instance 3c to values given in a template configuration stored in association with the type of the new field device 3, according to block 162; and / or setting values of configuration parameters 3b in the instance 3c to values obtained from an engineering system of the industrial plant 1, according to block 163.

[0045] In step 170, semantic meanings 3b* of new configuration parameters 3b in the instance 3c of the configuration are determined. Likewise, in step 180, semantic meanings 2b* of previously used configuration parameters 2b for the previously used field device 2 are determined. According to blocks 171 and 181, this determining may comprise obtaining the semantic meaning 2b*, 3b* from a library where it is stored in association with the respective field device 2, 3 and with a name of the configuration parameter 2b, 3b.

[0046] In step 190, values of new configuration parameters 3b whose semantic meanings 3b* match semantic meanings 2b* of previously used configuration parameters 2b are set to the values of these previously used configuration parameters 2b.

[0047] According to block 191, at least one correspondence between a previously used configuration parameter 2b and a new configuration parameter 3b may be received from a user via a user interface. According to block 192, it may then be determined that this new configuration parameter 3b on the one hand and this previously used configuration parameter 2b on the other hand have a matching semantic meaning 3b*, 2b*.

[0048] In step 200, the new field device 3 is provisioned with the instance 3c of the configuration that has been populated with values of configuration parameters 3b as described above.

[0049] In step 210, at least one industrial process is executed on the industrial plant 1 with the participation of the new field device 3.

[0050] Figure 2 illustrates an exemplary situation where the method 100 may be used. An industrial plant 1 comprises 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 stores driver information and / or software 2a, as well as values of configuration parameters 2b, for the field devices 2, 2'.

[0051] In the situation shown in Figure 2, the field device 2 is broken and replaced by the new field device 3. According to the method 100, the new field device 3 can be provisioned with the previously used values of configuration parameters 2b to the extent that these are compatible with the new field device 3.List of reference signs:

[0052] 1industrial plant 1anetwork of industrial plant 1 2, 2'previously used field device 2adriver information / software for field device 2 2bconfiguration parameters of field device 2 2b*semantic meanings of configuration parameters 2b 3new field device 3adriver information / software for field device 3 3bconfiguration parameters of field device 3 3b*semantic meanings of configuration parameters 3b 3cinstance of configuration for field device 3 100method for configuring new field device 3 110detecting that new field device 3 is connected to network 1a 111listening for discovery requests 112scanning and / or probing network 1a for newly connected devices 120obtaining driver information and / or software 3a 121determining identifier of field device 3 122obtaining driver information and / or software 3a from library 130determining previously used field device 2 131detecting that previously used field device 2 is no longer reachable 132detecting that new field device 3 is connected to previous network port 140determining whether driver information / software is unchanged 141determining whether new field device 3 has unchanged type 142determining whether driver information / software has unchanged version 150provisioning new field device 3 with configuration parameters 2b 160creating instance 3c 161using default values from device description information 162using values from template configuration 163using values from engineering system 170determining semantic meanings 3b* of configuration parameters 3b 171obtaining semantic meanings 3b* from library 180determining semantic meanings 2b* of configuration parameters 2b 181obtaining semantic meanings 2b* from library 190setting values of parameters 3b to values of corresponding parameters 2b 191receiving correspondence between configuration parameters 2b, 3b 192determining that semantic meanings 2b*, 3b* match 200provisioning new field device 3 with instance 3c 210executing industrial process with participation of new field device 3 AMSasset management system DCSdistributed control system

Claims

1. A computer-implemented method (100) for configuring a new field device (3) in an industrial plant (1) that replaces a previously used field device (2) in the industrial plant (1), comprising the steps of: • detecting (110) that the new field device (3) is connected to a network (1a) of the industrial plant (1); • obtaining (120), for the new field device, driver information and / or software (3a) that allows communication with the new field device (3) and is indicative of which configuration parameters (3b) of the new field device (3) may be set, and how; • determining (130) the previously used field device (2) which is to be replaced by the new field device (3); • determining (140) whether the driver information and / or software (3a) for the new field device (3) matches the previously used driver information and / or software (2a) for the previously used field device (2); and • in case of a match, provisioning (150) the new field device (3) with the previously used configuration parameters (2b) for the previously used field device (2), and • in case of no match, provisioning the new field device (3) with new configuration parameters (3b) by: ∘ creating (160), from device description information of the new field device (3), an instance (3c) of a configuration for the new field device (3); ∘ determining (170) semantic meanings (3b*) of new configuration parameters (3b) in the instance (3c) of the configuration; ∘ determining (180) semantic meanings (2b*) of previously used configuration parameters (2b) for the previously used field device (2); ∘ setting (190) values of new configuration parameters (3b) in the instance (3c) of the configuration whose semantic meanings (3b*) match semantic meanings (2b*) of previously used configuration parameters (2b) to the values of these previously used configuration parameters (2b); and ∘ provisioning (200) the new field device (3) with the instance (3c) of the configuration, wherein the creating (160) an instance (3c) of a configuration for the new field device (3) comprises: • setting (161) values of configuration parameters (3b) in the instance (3c) to default values given by the device description information; and / or • setting (162) values of configuration parameters (3b) in the instance (3c) to values given in a template configuration stored in association with the type of the new field device (3); and / or • setting (163) values of configuration parameters (3b) in the instance (3c) to values obtained from an engineering system of the industrial plant (1).

2. The method (100) of claim 1, wherein the device description information comprises an Electronic Device Description, EDD, and / or a Device Package, DP, of the new field device (3).

3. The method (100) of any one of claims 1 to 2, wherein the detecting (110) that the new field device (3) is connected to a network (1a) of the industrial plant (1) comprises: • listening (111) for discovery requests broadcasted by the new field device (3) on the network (1a); and / or • scanning and / or probing (112) the network (1a) for newly connected devices.

4. The method (100) of any one of claims 1 to 3, wherein the obtaining (120) driver information and / or software (3a) comprises: • determining (121) an identifier of the new field device (3); and • obtaining (122), based on the identifier, from at least one library of driver information and / or software, the driver information and / or software (3a).

5. The method (100) of any one of claims 1 to 4, wherein the determining (130) of the previously used field device (2) comprises: • detecting (131) that a previously used field device (2) is no longer reachable on the network (1a), and / or • detecting (132) that the new field device (3) is connected to a network port to which a previously used field device (2) was previously connected.

6. The method (100) of any one of claims 1 to 5, wherein the determining (140) whether the driver information and / or software (3a) for the new field device (3) matches the previously used driver information and / or software (2a) for the previously used field device (2) comprises: • determining (141) whether the type of the new field device (3) matches the type of the previously used field device (2), and • determining (142) whether version information of the driver information and / or software (3a) for the new field device matches the corresponding version information of the previously used driver information and / or software (2a) for the previously used field device (2).

7. The method (100) of any one of claims 1 to 6, wherein the determining (170, 180) of the semantic meaning (2b*, 3b*) of a configuration parameter (2b, 3b) comprises obtaining (171, 181) the semantic meaning (2b*, 3b*) from a library where it is stored in association with the respective field device (2, 3) and with a name of the configuration parameter (2b, 3b).

8. The method (100) of any one of claims 1 to 7, wherein the setting (190) values of new configuration parameters (3b) further comprises: • receiving (191), from a user, via a user interface, at least one correspondence between a previously used configuration parameter (2b) and a new configuration parameter (3b); and • determining (192) that this new configuration parameter (3b) on the one hand and this previously used configuration parameter (2b) on the other hand have a matching semantic meaning (3b*, 2b*).

9. The method (100) of any one of claims 1 to 8, wherein the new field device (3) is a device that is in direct physical interaction with an industrial plant, and / or with an industrial process executed on this industrial plant (1).

10. The method (100) of claim 9, wherein the new field device (3) is a sensor device that is to supply at least one measurement value of a physical quantity to a distributed control system, DCS, of the industrial plant (1), and / or an actor device that is to enact a control command received from the DCS on the plant (1).

11. The method (100) of any one of claims 1 to 10, wherein the method steps 110 to 200 are performed by an Asset Management System, AMS, of the industrial plant (1).

12. The method (100) of any one of claims 1 to 11, further comprising executing (210) at least one industrial process on the industrial plant (1) with the participation of the new field device (3).

13. A computer program, comprising machine-readable instructions that, when executed on one or more computers and / or compute instances, cause the one more computers and / or compute instances to perform the method (100) of any one of claims 1 to 12.

14. A machine-readable data carrier, and / or a download product, with the computer program of claim 13.

15. One or more computers and / or compute instances with the computer program of claim 13, and / or with the machine-readable data carrier or download product of claim 14.