Method for checking a measurement point in an automation system

Abstract

The invention comprises a method for designing a component of an automation system (A), wherein the component (FG1) has a plurality of subcomponents, wherein the subcomponents have defined dependencies with respect to one another, wherein the subcomponents are divided into nodes (KN1, KN2, KN3, KN4) and leaves (BL1) according to their dependency with respect to one another, wherein a node (KN1, KN2, KN3, KN4) is characterised by the fact that it has at least two adjacent nodes (KN1, KN2, KN3, KN4) or leaves for which dependencies exist, wherein a leaf is characterised by the fact that it has an adjacent node (KN1, KN2, KN3, KN4) for which dependencies exist, the method comprising: - selecting a type and / or at least one property of a first node (KN1), from a plurality of available types or properties, for the first node (KN1); and - checking the first node (KN1) for stability, wherein stability is confirmed if, in accordance with the correspondingly defined dependencies, the respective types or properties of the nodes (KN2, KN3) or leaves (BL1) adjacent to the first node (KN1) are compatible with the selected type of the first node (KN1) or the at least one selected property of the first node (KN1).

Description

[0001] Method for checking a measuring point in an automation system

[0002] The invention relates to a method for checking a measuring point in an automation system, wherein at least one field device is used in the measuring point for detecting and / or influencing at least one physical, chemical and / or biological measured quantity.

[0003] Field devices are already known from the state of the art and are used in industrial plants. They are widely used in process automation as well as in manufacturing automation. In principle, field devices are defined as all devices that are used close to the process and that provide or process process-relevant information. Thus, field devices are used to acquire and / or influence process variables. Measuring devices or sensors are used to acquire process variables. These are used, for example, for measuring pressure and temperature, conductivity, flow rate, pH, level, etc., and acquire the corresponding process variables such as pressure, temperature, conductivity, pH value, level, and flow rate. Actuators are used to influence process variables.These include, for example, pumps or valves that can influence the flow of a liquid in a pipe or the fill level in a container. In addition to the aforementioned measuring devices and actuators, field devices also include remote I / Os, radio adapters, and generally any devices located at the field level.

[0004] A large number of such field devices are produced and distributed by the Endress+Hauser Group.

[0005] In modern industrial plants, field devices are typically connected to higher-level units via communication networks such as fieldbuses (Profibus®, Foundation® Fieldbus, HART®, etc.). These higher-level units are usually control systems (DCS) or automation systems, such as a PLC (programmable logic controller). The higher-level units are used, among other things, for process control, process visualization, process monitoring, and commissioning of the field devices. The measured values ​​acquired by the field devices, especially sensors, are transmitted via the respective bus system to one (or possibly several) higher-level unit(s). Data transmission from the higher-level unit to the field devices via the bus system is also necessary, particularly for configuring and parameterizing field devices and controlling actuators.The complexity of systems in process automation is constantly increasing. More and more system components and field devices are being interconnected to form measuring points. Measuring points can consist of a single field device, such as a flow meter, or be composed of several products. The field devices themselves are also increasing in complexity and software options (especially ordering options and / or activation codes for functions). This means that field devices often consist of a multitude of subcomponents.

[0006] For example, a measuring point intended for pH measurement consists of one or more sensors installed in a fitting. A cable runs to each sensor, which, depending on the application and fitting, must have a certain minimum length to connect the sensors to a transmitter. Each sensor requires a calibration or storage solution for calibration. The possible combinations quickly become virtually endless and are no longer manageable for a human.

[0007] As an example, a user selects a pH sensor based on measurement requirements (e.g., measuring hydrofluoric acid). Next, a suitable fitting must be selected. This fitting must meet several requirements: First, it must be compatible with hydrofluoric acid and must not corrode upon contact with it. Second, the fitting must be compatible with the selected sensor and available in various installation lengths. Third, the fitting must be suitable for the relevant industry and its specific requirements (e.g., food, pharmaceuticals, hygiene, etc.). Furthermore, a suitable cable, transmitter, and any other necessary accessories (e.g., calibration fluid) must also be selected for this measurement point.

[0008] Within the various products, there are overarching dependencies: direct and indirect dependencies across multiple levels. For example, the selected sensor type influences the fitting, or rather the fitting's configuration options, but also affects the selection and configuration of the cable, transmitter, and accessories. If an option of the selected devices is changed, this in turn affects the options of the other connected products – a change to these products would then retroactively affect the remaining products, and so on.

[0009] The example mentioned describes a relatively simple case. However, the complexity of this task increases steadily with the number of components required. For instance, n sensors might be needed in a fitting with one transmitter, or a measuring point with n sensors in m fittings with x transmitters might need to be planned. These dependencies are no longer comprehensible to a user – today, only a few experts can even verify them. There is no structured approach for this planning; often, a "trial and error" approach is used. This approach can be highly error-prone, as experts cannot know all possible combinations due to the variance. The sheer number of possible combinations – depending on the number of components – is simply too much for humans to grasp.

[0010] Based on this problem, the invention aims to present a method that simplifies the design of plant components.

[0011] The task is solved by a method for designing a component of an automation system, wherein the component has several subcomponents, wherein the subcomponents have defined dependencies on each other, wherein the subcomponents are divided into nodes and leaves according to their dependencies on each other, wherein a node is characterized by having at least two neighboring nodes or leaves to which dependencies exist, wherein a leaf is characterized by having a neighboring node to which dependencies exist, comprising:

[0012] Selecting a type and / or at least one property of a first node from a multitude of available types or properties for the first node;

[0013] Checking the first node for stability, whereby stability is affirmed if, according to the correspondingly defined dependencies, the respective types or properties of the nodes or leaves adjacent to the first node are compatible with the selected type of the first node or at least one selected property of the first node.

[0014] The method according to the invention enables a structured and machine-assisted configuration or planning of measuring points or plant components with one or more plant components, which plant components have several subcomponents. The method uses an algorithm that checks the dependencies of subcomponents on each other and is intended to achieve a stable measuring point configuration.

[0015] For this purpose, the subcomponents of a system component are divided into so-called nodes and leaves. The assignment of subcomponents to nodes and leaves is not based on their function, but rather on their interdependencies. All subcomponents are then successively configured, meaning their types are selected and / or properties are added. Such configuration of a subcomponent influences the available types or properties of neighboring subcomponents, depending on the structure of the nodes or leaves. After assigning a type or property to a subcomponent, the system checks whether the neighboring nodes or leaves are compatible with this property, i.e., whether at least one suitable sensor type or property is available for each. If this is possible for all neighboring nodes or leaves, stability is achieved.

[0016] The method according to the invention eliminates the need for manually guessing compatibilities. It achieves a structured approach that prevents incorrect combinations.

[0017] According to an advantageous embodiment of the method, it is provided that, in the event that stability is denied, types and / or at least one property of the nodes or leaves adjacent to the first node are selected from a multitude of available types or properties for the corresponding adjacent nodes or leaves, wherein the available types or properties for the corresponding adjacent nodes or leaves are restricted depending on the selected type or at least one property of the first node.

[0018] If the stability check of the first subcomponent reveals that the directly dependent subcomponents (the neighboring nodes and leaves) are incompatible, these are then checked and any conflicting or excluded configuration options in these subcomponents are corrected.

[0019] Subsequently, according to one embodiment of the procedure, the stability of the first node can be rechecked after selecting the respective types or properties of the nodes or leaves adjacent to the first node. The originally configured subcomponent is thus retested against the now-adapted product configurations of the immediately adjacent subcomponents (corresponding to the structure of the nodes or leaves).

[0020] If stability is again denied, according to an advantageous embodiment of the method, the steps of selecting the types or properties of the first node and its neighboring nodes or leaves, and subsequently checking the first node for stability, are repeated until the stability of the first node is confirmed or until a predetermined number of repetitions is reached. In the rare case that the predetermined number of repetitions is reached, the method is terminated and, in particular, restarted. In such a case, a suitable configuration or combination cannot be found in this combination. The method must then be restarted, and initial conditions or requirements, for example, must be changed.

[0021] However, if stability is confirmed, the selection and testing steps are repeated for each additional node according to one implementation of the procedure, until stability is confirmed for each further node. The configuration is then complete, and the system component could be ordered with the determined configurations.

[0022] The term "component" of an automation system should be interpreted broadly here:

[0023] According to a first variant of the method, a field device for automation technology is used as a component, comprising several subcomponents, in particular at least one sensor unit, at least one transmitter, a control unit, a housing, at least one communication interface, and / or at least one cable. The list of possible subcomponents is to be understood as exemplary. A person skilled in the art would also consider other common types of subcomponents for field devices based on their experience.

[0024] A second variant of the procedure uses a measuring point as the main component, with field devices from automation technology serving as subcomponents. Other subcomponents include containers, pipelines, etc.

[0025] A third variant of the method uses a plant component, with measuring points serving as subcomponents. A measuring point contains several field devices and can further include subcomponents such as tanks or pipelines.

[0026] Other types of components are also conceivable. Entire systems could even be considered components. Their subcomponents would then be system parts. Alternatively, specific parts or subcomponents of a field device could be defined as components themselves, for example, its electronics unit. Its subcomponents would then be, for example, various chipsets or electronic components.

[0027] According to an advantageous embodiment of the method, a subcomponent comprises several subsubcomponents, which are analogously divided into nodes and leaves. Types and / or properties are selected for these nodes, and the respective stability is then verified. This allows one or more levels to be added to the method. It is also possible to include subsubsubcomponents or even more detailed subcomponents. For example, a plant component can be used. Its subcomponents could then be, for example, field devices, which in turn might have sensors, etc., as subsubcomponents. The method then begins with a component, where the subsubcomponents of that subcomponent are first designed according to the method. Subsequently, the subsubcomponents of another subcomponent are designed until all subcomponents are stable relative to each other.

[0028] According to an advantageous embodiment of the method according to the invention, a software application is used, which is executed, in particular, on a cloud-based platform. This application is used to select the types or properties and to perform stability testing. A cloud-based platform is accessible, in particular, via the internet and is set up on one or more servers. One or more software applications, designed, for example, for processing data, can be stored and executed on such a platform.

[0029] An advantageous embodiment of the method provides that, prior to selecting the type and / or at least one property of the first node, information on the component's application is collected. Based on this application information, the types and / or properties available for selection for the first node, subsequent nodes, and sheets are reduced. Certain types and / or properties can be excluded from specific applications from the outset. For example, for hygienic applications, only fittings or housings of field devices made of specific materials, such as stainless steel, are permitted. The other types and / or properties are then hidden from the process, thus reducing its complexity from the beginning.

[0030] The invention is explained in more detail with reference to the following figure. It shows

[0031] Fig. 1 : an embodiment of the method according to the invention.

[0032] Figure 1 shows a schematic diagram of a measuring point (MS) in plant A of the process automation system. Measuring point MS is currently in the planning phase and is intended to be part of plant A. During the planning phase, the planning personnel define specific requirements for measuring point MS, which are then used to design the measuring point. For example, it is specified that measuring point MS pertains to an application in which a beer tank is provided, the volume and flow of which are to be monitored. Accordingly, measuring point MS consists of the tank AK1 and the pipeline AK2 for the outflow of the measuring medium (beer). The volume of tank AK is to be determined metrologically by measuring the fill level. To measure the fill level of tank AK1, a field device FG1 is designed during the planning phase, for example, a radar level gauge, which is attached to tank AK.To measure the flow rate of the process medium flowing through the pipeline AK2 as an outflow from the container AK1, the measuring point MS shall include a field device FG2, for example a flow meter based on the Coriolis principle, which shall be attached to the pipeline AK2.

[0033] The field devices FG1 and FG2 are designed according to the requirements and receive a specific configuration and parameterization during the ordering process to fulfill the measurement tasks. After production and delivery of the field devices FG1 and FG2, they are installed at the measuring point and commissioned.

[0034] Each of the field devices FG1 and FG2 should establish a communication link with a higher-level PLC via a 4-20 mA current loop or, alternatively, a fieldbus. The PLC queries the measured values ​​from the field devices FG1 and FG2 and transmits them to the control center (LS) of the plant via another network segment. The entirety of all network segments (the 4-20 mA current loops or the fieldbus, and the other network segment) is referred to below as the communication network (CN).

[0035] The method according to the invention deals with the aspect of the design of the field devices FG1, FG2 and is described in more detail using the design of the field device FG1 as an example:

[0036] The field device FG1 is intended to determine the fill level of container AK1. Field device FG1 consists of several subcomponents. For the sake of simplicity, the number of subcomponents in the following example is kept low to five. In real-world field devices, the number of available subcomponents is sometimes many times higher.

[0037] The subcomponents include a sensor for determining the fill level, a transmitter, a housing, a communication interface, and a cable.

[0038] The individual subcomponents are defined for the design of the field device FG1. This design process takes place on a software application SA, which is executed, for example, on a cloud-based platform CP. A challenge in the design is that the subcomponents have various dependencies on one another. For instance, certain sensors can only be installed in specific housings. Similarly, only certain cables are available for various communication interfaces. These dependencies result in a large number of possible combinations, which even trained experts can only partially grasp. The method according to the invention enables a simpler and error-free design of the field device FG1.

[0039] For this purpose, the individual subcomponents of the field device FG1 are divided into so-called nodes KN1, KN2, KN3, KN4 and so-called leaves BL1. This division into leaves and nodes is based on the dependencies of the individual subcomponents to each other. If a subcomponent has dependencies on two or more subcomponents, it is referred to as a node. If a subcomponent has dependencies on only one other subcomponent, it is referred to as a leaf. The dependencies of the subcomponents to each other are stored in the software application SA and can be determined, for example, by analyzing product data.

[0040] Fig. 2 shows the division of the subcomponents of the field device FG1 into nodes KN1, KN2, KN3, KN4 and sheets BL1. For example, node KN1 relates to the sensor, node KN2 to the housing, node KN3 to the transmitter, and node KN4 to the communication interface. Sheet BL1 then relates to the cable.

[0041] In the first step of the process, the user configures node KN1, which corresponds to the subcomponent "Sensor". Based on the application requirements, the user selects a suitable sensor type. Alternatively, the user may pre-enter the application information into the software application SA, which then reduces the available subcomponents to those that are actually suitable for the application.

[0042] In this example, the user selects a sensor of the "non-contact radar" type. The next step involves performing a stability check on the neighboring nodes KN2 and KN3. This means verifying whether the current properties of these nodes KN2 and KN3 are compatible with the newly configured node KN1.

[0043] Currently, subcomponent types or properties are preset for nodes KN2 and KN3. For example, node KN2 is assigned a housing, which is incompatible with the selected sensor. Therefore, the stability check results in a negative result.

[0044] In the next step, the user adjusts the housing accordingly by selecting a different type. After selection, another stability check is performed. If this is successful, the process continues with node KN3.

[0045] This process is repeated until mutual stability of all subcomponents has been confirmed. Finally, the fully configured FG1 field device can be ordered.

[0046] If stability is denied, the selection process for the corresponding node is repeated. This may be repeated until stability is confirmed. A maximum number of attempts can be set. Once this maximum is reached, the process is terminated. It can then be restarted with different starting values, such as a different sensor selection.

[0047] The example described above is greatly simplified. Typically, several properties must be selected for each subcomponent. The total number of subcomponents is also usually much higher.

[0048] It is also possible to apply the procedure to other types of components. In the example described above, the field device FG1 was selected as the component. However, a measuring point (MS) or a plant section could also be selected as the component. The corresponding subcomponents would then be field device FG1, FG2, or measuring points (MS), respectively.

[0049] Reference symbol list

[0050] A facility

[0051] AK1, AK2 plant components BL1 sheets

[0052] CP Cloud-based platform

[0053] FG1, FG2 field devices

[0054] KN1, KN2, KN3, KN4 nodes

[0055] LS control center of the MS measuring station

[0056] NW Communication Network

[0057] SA Software Application

[0058] PLC control unit

Claims

Patent claims 1. Method for designing a component of an automation system (A), wherein the component (FG1) has several subcomponents, wherein the subcomponents have defined dependencies on each other, wherein the subcomponents are divided into nodes (KN1 , KN2, KN3, KN4) and leaves (BL1) according to their dependencies on each other, wherein a node (KN1 , KN2, KN3, KN4) is characterized by having at least two adjacent nodes (KN1 , KN2, KN3, KN4) or leaves with which dependencies exist, wherein a leaf is characterized by having an adjacent node (KN1 , KN2, KN3, KN4) with which dependencies exist, comprising: Selecting a type and / or at least one property of a first node (KN1) from a multitude of available types or properties for the first node (KN1); Checking the first node (KN1) for stability, whereby stability is affirmed if, according to the correspondingly defined dependencies, the respective types or properties of the nodes (KN2, KN3) or leaves (BL1) adjacent to the first node (KN1) are compatible with the selected type of the first node (KN1) or with at least one selected property of the first node (KN1).

2. Method according to claim 1, wherein, in the event that stability is denied, types and / or at least one property of the nodes (KN2, KN3) or leaves (BL1) adjacent to the first node (KN1) are selected from a plurality of available types or properties for the corresponding adjacent nodes (KN2, KN3) or leaves (BL1), wherein the available types or properties for the corresponding adjacent nodes (KN2, KN3) or leaves (BL1) are restricted depending on the selected type or at least one property of the first node (KN1).

3. Method according to claim 2, wherein the stability of the first node (KN1) is checked again after selecting the respective types or properties of the nodes (KN2, KN3) or leaves (BL1) adjacent to the first node.

4. Method according to claim 3, wherein, in the event that stability is again denied, the steps of selecting the types or properties of the first node (KN1) and its neighboring nodes (KN2, KN3) or leaves (BL1), and subsequently checking the first node (KN1) for stability, are repeated until the stability of the first node (KN1) is affirmed or until a predetermined number of repetitions is reached.

5. The method according to claim 4, wherein, in the event that the predetermined number of repetitions is reached, the method is terminated and, in particular, restarted.

6. Method according to one of the preceding claims, wherein, in the event that stability is confirmed, the steps of selecting and testing are repeated for each further node (KN2, KN3) until stability is confirmed for each further node (KN2, KN3).

7. Method according to one of the preceding claims, wherein a field device (FG1 , FG2) of automation technology is used as a component, which comprises several subcomponents, in particular at least one sensor unit, at least one transmitter, one fitting unit, one housing, at least one communication interface and / or at least one cable.

8. Method according to one of claims 1 to 6, wherein a measuring point (MS) is used as a component, and field devices (FG1 , FG2) of automation technology are used as subcomponents.

9. Method according to any one of claims 1 to 6, wherein a plant component is used as a component, wherein measuring points (MS) are used as subcomponents.

10. Method according to one of the preceding claims, wherein a subcomponent has several sub-subcomponents which are analogously divided into nodes and leaves, for which analogous types and / or properties are selected and wherein the respective stability is subsequently checked.

11. Method according to one of the preceding claims, wherein a software application (SA) is used, which in particular is executed on a cloud-based platform (CP), via which the selection of the types or properties is made and which performs the stability test.

12. Method according to one of the preceding claims, wherein, prior to the step of selecting the type and / or the at least one property of the first node (KN1), information on the application of the component is acquired, wherein, based on the information on the application of the component, the types or properties available for selection for the first node (KN1), the further nodes (KN2, KN3), or leaves (BL1) are reduced.

Images