Method for configuring a component of an automation system

Abstract

The invention comprises a method for configuring a component (FG1, KO1) of an automation system, wherein the component (FG1) comprises at least one subcomponent, wherein the configuration comprises a plurality of queries (AF1, AF1', AF1'') for selecting application information, types and / or properties for the component (FG1) and / or the subcomponents thereof, the method comprising: - selecting first application information, a first property of the component (FG1) or of one of the subcomponents, or a first type of one of the subcomponents, from a first number of options available for the component (FG1) or the corresponding subcomponent, within the scope of a first query (AF1); - selecting further application information, a further property of the component (FG1) or of one of the subcomponents, or a further type of one of the subcomponents, from a second number of options available for the component (FG1) or the corresponding subcomponent, within the scope of a second query (AF1'), wherein the options available for the second query (AF1') are restricted on the basis of the selection made in the first query (AF1); and - repeating the selection process up to and including a final query (AF1''), wherein the options available in each case are restricted on the basis of the results of each of the preceding queries (AF1, AF1').

Description

[0001] Method for designing a component of an automation system

[0002] The invention relates to a method for designing a component of an automation system, wherein the component has at least one subcomponent, and wherein the design comprises a plurality of queries for selecting application information, types and / or properties for the component and / or its subcomponents.

[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 control units, 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. The possible combinations quickly become virtually endless and impossible for a person to manage. Furthermore, there are interdependencies between different products: direct and indirect dependencies across multiple levels. For example, the chosen sensor type influences the fitting and its configuration options, but also affects the selection and configuration of the cable, transmitter, and accessories.

[0007] As an example, let's consider setting up two measuring points. At one point, the redox and pH values ​​of a sample medium will be measured. At the other point, the oxygen concentration in the sample medium will be measured. Both measuring points should be located directly next to each other. The problem is that it's up to the person setting up the measuring points to determine if any optimizations are possible. For example, one fitting could be used for measuring the redox and pH values, and a second fitting for measuring the oxygen values. Alternatively, one fitting could be used that can accommodate all three sensors.

[0008] Today's product configurator tools and measurement design tools commonly used in the process industry are always linear and do not support the inclusion of multiple measuring points or even their comprehensive optimization.

[0009] Configuration tools known from other industries also do not help with this problem:

[0010] Configurators familiar from the automotive industry, for example, allow the configuration of exactly one vehicle at a time, which can then be ordered. While optimizations do occur, these always relate to that single vehicle and not to a comprehensive, cross-product optimization. Similarly, in online shopping, only individual products can be selected. No product-wide optimization takes place.

[0011] Overall, it is therefore not possible today to map dependencies and, based on these, to carry out a guided, comprehensive measurement point configuration and optimization, or validation.

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

[0013] The task is solved by a method for designing a component of an automation system, wherein the component has at least one subcomponent, and wherein the design includes a multitude of queries for selecting application information, types and / or properties for the component and / or its subcomponents, comprising:

[0014] Selecting an initial application piece of information, a first property for the component or one of the subcomponents, or a first type of one of the subcomponents from an initial set of options available for the component or the corresponding subcomponent in an initial query; selecting a further application piece of information, a further property for the component or one of the subcomponents, or a further type of one of the subcomponents from a second set of options available for the component or subcomponent.the corresponding subcomponent, available options in a second query, wherein the options available for the second query are restricted based on the selection made in the first query; and repeating the selection process up to and including the last query, wherein the available options are restricted based on the results of each of the preceding queries.

[0015] 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 may have several subcomponents. The method enables the design of components based on the user's prior inputs or selections.

[0016] According to a preferred embodiment of the method, it is provided that one or more further components are designed, each of the further components having at least one subcomponent, the design of each of the components comprising a plurality of queries for selecting application information, types and / or properties for the corresponding further component and / or its subcomponents, queries being performed analogously to the steps of selecting the first component, wherein the options available within the queries are restricted based on the results of each of the preceding queries and the results of the queries of the first component, or of the previously designed further components.

[0017] The inputs, or rather the respective selection of subcomponents, by a user from one or more previous components are used for the design of further components. This allows the design to be carried out across components, resulting in a more precise and targeted outcome that can potentially be achieved more quickly.

[0018] The time aspect is further improved if, in cases where only one option is available in a query, that option is automatically selected. This eliminates the need for query steps where the choice is clear from the outset.

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

[0020] 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.

[0021] 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.

[0022] 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.

[0023] Other types of components are also conceivable. Even entire systems could be built as...

[0024] Components can be considered. Their subcomponents would then be plant components. However, certain parts or subcomponents of a field device could also be defined as components themselves, for example, its electronics unit. Its subcomponents would then be, for example, various chipsets or electronic components.

[0025] 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, via which the selection of types or properties is made. A cloud-based platform is, in particular, accessible 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.

[0026] According to an advantageous embodiment of the method, it is provided that basic requirements, particularly concerning the industry and / or the application, are recorded in advance, whereby the options available for selection in the queries are restricted based on these basic requirements. Certain types and / or properties of subcomponents can thus be excluded from certain applications from the outset. For example, for hygienic applications, only fittings or housings of field devices made of certain materials, such as stainless steel, are permitted. The other types, or rather,

[0027] Properties are then hidden from the process, thus reducing the complexity of the process from the outset.

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

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

[0030] 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 relates to an application in which a measuring medium is provided, the chemical and physical properties of which are to be checked.

[0031] 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, the field devices FG1 and FG2 are installed at the measuring point and commissioned. Each field device FG1 and FG2 communicates with a higher-level PLC (Programmable Logic Controller) 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 plant's control center (LS) 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 KN.

[0032] The method according to the invention deals with the aspect of the design of the measuring point:

[0033] The field device FG1, as the first component KO1, is intended to determine the pH value of a measuring medium. The field device FG1 consists of several subcomponents. For the sake of simplicity, the number of subcomponents is kept small in the following example. In real field devices, the number of available subcomponents is sometimes many times higher.

[0034] The subcomponents consist of a sensor and a fitting.

[0035] 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.

[0036] At its core, the procedure shown in Fig. 2 consists of several queries AF1 , AF1', AF1“, which are created by the software application SA, presented to the user and require a selection from the user.

[0037] The first query, AF1, requires the user to select the measurement principle. In reality, there are many possible answers; for clarity, only two options are given here: pH measurement and oxygen measurement. The user selects "pH measurement".

[0038] The next query, 'AF1', is generated dynamically and prompts the user to select a sensor. The number of available sensor options (here: three sensors) is influenced by the measurement principle selected in the previous query, AF1. Sensors that cannot measure pH are hidden. The user then selects one of the options.

[0039] The next query, "AF1", is dynamically generated based on the selected options from the previous queries, "AF1" and "AF1'". Here, the user selects a fitting. The available options (in this case, two fittings) depend on the selected sensor.

[0040] The user has now reached the end of the configuration process for the first component KO1, i.e., the first field device FG1. As shown in Fig. 3, the user is now asked whether another component KO2 is required at this measuring point MS. The user confirms this (field device FG2) and is then immediately asked again in a query AF2 about the measuring principle, which they answer with "Oxygen measurement".

[0041] Certain requirements are already known from the selected options of the previous queries AF1, AF1' of the previous component KO1 and do not need to be queried again. For example, a fitting that can hold two or more sensors will be selected. Thus, a query tree is dynamically built, in which the dependencies of individual options are mapped.

[0042] This can be extended to a multiple of n components KOn, as shown in Fig. 4. The corresponding queries AFn, AFn' are then created according to the previously selected options. At a certain point, it is even possible for the dynamically created tree to contain so much information that automatic selection is possible, since no further questions need to be asked (the number of available options is then 1 in each case).

[0043] Certain basic requirements can also restrict the selection options for individual queries in the user interface to the relevant options. For example, if "food sector" is selected as the industry sector, then glass sensors may not be used. Sensors containing glass will be filtered out as available options.

[0044] 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.

[0045] 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. Reference symbol list

[0046] A facility

[0047] AF1, AF1', AF1" Queries regarding the first component AF2, AF2' Queries regarding the second component

[0048] AFn, AFn' queries regarding the nth component

[0049] AK1, AK2 plant components CP cloud-based platform

[0050] FG1, FG2 field devices, components KN communication network

[0051] KO1, KO2, KOn components

[0052] LS control center of the facility

[0053] MS measuring station

[0054] SA software application PLC control unit

Claims

Patent claims 1. Method for designing a component (FG1 , KO1) of an automation system, wherein the component (FG1) has at least one subcomponent, wherein the design includes a plurality of queries (AF1 , AF1', AF1“) for selecting application information, types and / or properties for the component (FG1) and / or its subcomponents, comprising: Selection of an initial application information, an initial property for the component (FG1) or one of the subcomponents, or an initial type of one of the subcomponents from an initial number of options available for the component (FG1), or the corresponding subcomponent, within the framework of an initial query (AF1); Selections of further application information, a further property for the component (FG1) or one of the subcomponents, or a further type of one of the subcomponents from a second set of options available for the component (FG1) or the corresponding subcomponent within a second query (AF1'), wherein the options available for the second query (AF1') are restricted based on the selection made in the first query (AF1); and Repeat the selection process up to and including the last query (AF1"), restricting the available options based on the results of each of the preceding queries (AF1 , AF1 ').

2. The method of claim 1, wherein one or more further components (FG2, KO2, KOn) are designed, each of the further components (FG2, KO2, KOn) comprising at least one subcomponent, the design of each of the further components (FG2, KO2, KOn) comprising a plurality of queries (AF2, AF2', AFn, AFn') for selecting application information, types and / or properties for the corresponding further component (FG2, KO2, KOn) and / or its subcomponents, the queries (AF2, AF2', AFn, AFn') being performed analogously to the steps of selecting the first component (FG1), the options available within the queries (AF2, AF2', AFn, AFn') being selected based on the results of each of the preceding queries and the results of the queries (AF1, AF1', AF1") of the first component (FG1), or of the previously designed further components. Components will be restricted.

3. Method according to one of the preceding claims, wherein in the case that only one option is available in a query (AF1 , AF1 ', AF1“, AF2, AF2', AFn, AFn') this option is automatically selected.

4. Method according to one of the preceding claims, wherein a field device of automation technology is used as component (FG1 , KO1), 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.

5. Method according to one of claims 1 to 4, wherein a measuring point is used as component (KO1), and field devices of automation technology are used as subcomponents.

6. Method according to one of claims 1 to 4, wherein a plant component (KO1) is used, and measuring points are used as subcomponents.

7. 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 corresponding selection is made.

8. Method according to one of the preceding claims, wherein basic requirements, in particular relating to the industry and / or the application, are recorded in advance, wherein, on the basis of the basic requirements, the options available for selection for the queries (AF1 , AF1', AF1“, AF2, AF2', AFn, AFn') are restricted.

Images