Computer-implemented method and engineering system for generating plant image hierarchy for operating and observing process plant

Abstract

The aim of the invention is to generate a plant image hierarchy (60) in which plant images (61, 62, 63) for operating and observing the process plant (1) to be controlled are stored in a structured manner and the plant images can be selected and opened by an operator during the operation of the plant (1), in an efficient and error-free manner. For this purpose, according to the invention, before the structured preservation, the structured preservation is carried out, hierarchical information (HI) relating to a device image of a first hierarchy level (E1) and sequence information (RI) relating to a sequence of other device images of a second hierarchy level (E2) relating to the same device image assigned to the first hierarchy level (E1) are assigned to at least part of the device images (62, 63). The device images are then output in a pre-structured form for subsequent structured interconnects. These plant images are preferably plant images of modular and pre-configured process engineering plant components (kits) in a hybrid process engineering plant, such as module type packages (MTPs).

Description

Technical Field

[0001] The present invention relates to a computer-implemented method for generating a device image hierarchy for operating and observing a process engineering device according to claim 1 and an engineering system according to claim 8. Background Art

[0002] In order to operate and observe large-scale process engineering devices, symbolic device images are presented to an operator (i.e., a person who operates and observes the device), and these symbolic device images abstractly display the process flow correlations between process objects (hereinafter referred to as "process objects") that are particularly carried out in the device.

[0003] Device images are, for example, composed of static symbols (such as lines, rectangles, etc.), dynamic symbols (such as lines with color changes according to process values, rectangles with filled heights, etc.), tile symbols (for dynamic visualization of process flow process objects), symbols for operation dialog boxes (such as so-called "faceplates"), complex controls (such as trend displays, information sequence displays, etc.), and visualizable containers for enabling content from independent and unconstrained sources (such as device images of modular device components (complete units), Apps (such as regulator optimizers, KPI calculations)).

[0004] According to EP 3 623 891 A1, it is already known that, in order to navigate between device images in an operator workstation client, a so-called "device image hierarchy" is used to be operated and observed by the operator, that is, by means of a hierarchical (scrollable and collapsible) tree structure, device images preset for operation and observation are provided to the operator. Via this tree structure, device images can be selected and opened during the operation of the technical device.

[0005] Here, each node of the image hierarchy references a device image and a so-called group alarm state. The group alarm state shows the alarm state of the corresponding device image, that is, according to the alarm category, all alarms of the process objects in the device image are respectively summarized and displayed in the image hierarchy. Thus, the operator of the control system of the technical device can immediately identify, when viewing the image hierarchy, in which device image there are process objects that issue alarms. By means of so-called Loop-In, the operator can directly navigate to these process objects. This is still possible even when the process objects cannot be identified in the compactly displayed image hierarchy.

[0006] The image hierarchy is statically planned in the engineering environment of the control system of a technical device, and the image hierarchy often contains a large number (sometimes even hundreds) of device images. Therefore, for reasons of conciseness, the image hierarchy is usually only displayed in a compact mode during the operation of the technical device. To enable more efficient navigation between the images that are individually most important for each operator of the control system, in addition to the static image hierarchy planned in engineering design, an image hierarchy that can be dynamically personalized during operation can also be provided. The operator can, with the help of a personalization service, create, optimize, and maintain this image hierarchy during the operation of the technical device in order to be able to efficiently navigate between the device images of their preference. Thereby, the operator can, for example, more quickly identify the cause of an alarm.

[0007] Therefore, the device images for operating and observing the process engineering device to be controlled are stored in a structured manner in the device image hierarchy with respect to the hierarchy and sequence, and the device images can be selected and opened by the operator during the operation of the device. In the structured storage, the device image hierarchy includes at least a first (higher) hierarchy level and a second (lower) hierarchy level, wherein a plurality of device images of the second hierarchy level are assigned to one device image of the first hierarchy level, and the plurality of device images of the second hierarchy level that are respectively assigned to the same device image of the first hierarchy level are in turn assigned to a sequence, in particular to a sequence related to the process engineering structure of the device. For example, such a device image hierarchy is known from US 2019 / 137962 A1.

[0008] In engineering design, the device image hierarchy is usually created by a project engineer with the help of a specialized device image hierarchy editor, where the device image hierarchy often resembles the structure of the technical hierarchy. In this case, often hundreds of device images for operating and observing the process engineering device have to be taken into account. Since all the device images present in the device image hierarchy editor are provided at the same level, i.e., within a flat list, the planning of the device image hierarchy is both costly and potentially error-prone. According to the prior art, even with the increasing use of modular and pre-configured device components (packages), which usually also provide multiple device images, this situation does not change. In new device concepts, such device components are flexibly integrated into the device or can also be removed again. When integrating a new package with new device images, all newly added device images must always be individually added to the hierarchy. For example, modular and pre-configured device components (packages) are known from US 2022 / 0147025 A1. Summary of the Invention

[0009] In view of this, the object of the present invention is to enable the generation of a device image hierarchy to be more efficient and less error-prone.

[0010] This object is achieved by a computer-implemented method according to claim 1 and an engineering system according to claim 8. Advantageous design options are the subject matter of the dependent claims respectively.

[0011] The subject matter of claim 9 is a computer program comprising instructions which, when the program is executed by a computer, cause the computer to perform the method according to any one of claims 1 to 7.

[0012] The subject matter of claim 10 is a computer-readable storage medium comprising instructions which, when executed by a computer, cause the computer to perform the method according to any one of claims 1 to 7.

[0013] The method according to the present invention is used to generate a device image hierarchy in which device images for operating and observing a process engineering device to be controlled are stored in a structured manner with respect to the hierarchy and sequence, and can be selected and opened by an operator during device operation. In the structured storage,

[0014] - the device image hierarchy includes at least a first (higher) hierarchy level and a second (lower) hierarchy level,

[0015] - a plurality of device images at the second hierarchy level are assigned to one device image at the first hierarchy level,

[0016] - each device image at the second hierarchy level assigned to the same device image at the first hierarchy level is assigned to a sequence, in particular to a sequence regarding the process engineering structure of the device.

[0017] According to the present invention, the method comprises the following steps:

[0018] a) Assigning respectively to at least some of the device images at the second hierarchy level:

[0019] - hierarchy information regarding the device image at the first hierarchy level, and

[0020] - sequence information related to the sequences of other device images at the second hierarchy level assigned to the same device image at the first hierarchy level, this sequence being in particular a sequence regarding the process engineering structure of the device, wherein this assignment is carried out before the device images are stored in a structured manner,

[0021] b) Outputting the device images for selection (for example, outputting to the project engineer of the device image hierarchy)

[0022] c) Record the selection information regarding the selection of the device image output in step b) (e.g., by the project engineer of the device image hierarchy), which is used for the subsequent structured interconnection between the hierarchy and the sequence.

[0023] d) Output the device image selected in step c) for its subsequent structured interconnection, wherein the device image with the assigned hierarchy information and sequence information is automatically pre-structured according to the corresponding assigned hierarchy information and sequence information.

[0024] Due to the pre-structuring of the device image by means of the hierarchy information and sequence information, it is possible to achieve the subsequent structured interconnection and thus the planning of the device image hierarchy with significantly less cost and a lower probability of errors. In the best case, the pre-structuring is already complete and accurate, so that no subsequent additional device image interconnection is required at all.

[0025] These advantages particularly come into play when using modular and pre-configured process engineering equipment components (often also referred to as "Package Unit"). An example of such equipment components is the so-called "ModuleType Package" (MTP), as defined, for example, by NAMUR (the Community of Interest of Users of Automation Technology in the Process Industry) in the standard VDI / VDE / NAMUR 2658 and used, for example, in hybrid process engineering equipment. Here, the module type package can be flexibly integrated into the process flow or can also be removed from it again. Such equipment components often provide multiple device images, which must be integrated into the device image hierarchy when merged into the process. Therefore, the device image that at least partially includes the assigned hierarchy information and sequence information advantageously relates to modular and pre-configured process engineering equipment components, especially the module type package (MTP).

[0026] According to an advantageous design, the device image is defined or provided by the technical (i.e., process flow) hierarchy of the device.

[0027] According to another particularly advantageous design, in step b), the device image is output in a structured manner according to the technical hierarchy of the device. Thereby, the clarity when selecting the device image can be further improved, and thus the efficiency when generating the device image hierarchy can be further increased.

[0028] Advantageously, the generation of the device image hierarchy is implemented in the engineering system, wherein preferably, the assignment of the hierarchy information and sequence information is implemented when the device image is imported into the engineering system.

[0029] The allocation of hierarchical information and sequence information can be achieved manually by a project engineer or automatically based on the construction information already provided together with the device image, such as in the case of modular and pre-configured process engineering device components.

[0030] In a very operator-friendly design, the selection information is defined by movement operations that can be performed by a project engineer, such as dragging and dropping of graphics or copy and paste operations.

[0031] To further improve the efficiency when generating the device image hierarchy, for the selection in step b), only device images that are not yet included in the device image hierarchy can be output.

[0032] Device images for operating and observing the process engineering device to be controlled are saved in a structured manner in the device image hierarchy with respect to the hierarchy and sequence, and can be selected and opened by an operator during device operation, wherein, in the structured saving,

[0033] - The device image hierarchy includes at least a first hierarchy level and a second hierarchy level.

[0034] - A plurality of device images at the second hierarchy level are assigned to one device image at the first hierarchy level.

[0035] - Each device image at the second hierarchy level assigned to the same device image at the first hierarchy level is assigned to a sequence, in particular to a sequence regarding the process engineering structure of the device.

[0036] The engineering system for generating a device image hierarchy according to the invention includes at least one processor connected to a memory, wherein the at least one processor is configured to execute the method described above.

[0037] The advantages mentioned for the method according to the invention correspondingly apply to the engineering system according to the invention.

[0038] A computer program according to the invention includes instructions which, when the program is executed by a computer, cause the computer to implement the method described above.

[0039] A computer-readable storage medium according to the invention includes instructions which, when executed by a computer, cause the computer to implement the method described above. Description of the Drawings

[0040] Hereinafter, the invention and other advantageous design options of the invention according to the features of the dependent claims will be explained in more detail based on the embodiments shown in the drawings; in the drawings:

[0041] Figure 1 An industrial plant having an automation system characterized by an engineering system according to the invention is shown,

[0042] Figure 2 According to the prior art, the generation of a plant image hierarchy by a plant image hierarchy editor is shown,

[0043] Figure 3 An object model for generating a plant image hierarchy according to the invention is shown,

[0044] Figures 4 to 7 According to the invention, the generation of a plant image hierarchy by a plant image hierarchy editor is shown, and

[0045] Figure 8 A process flow according to the invention is shown. Detailed Description

[0046] Figure 1 An industrial plant 1 having an industrial automation system 2 is shown in a simplified diagram. Such a plant 1 is used in a variety of industrial sectors, for example in process industries (such as chemical, pharmaceutical, metal, oil and gas, paper), discrete manufacturing, and energy generation. The original industry-specific processes 3, such as production processes or energy generation processes, are controlled and / or regulated and monitored by the automation system 2. The automation system 2 includes one or more industrial controllers (here controller 4) and two or more automation servers 5, 6, which are also often referred to as "application servers" or "operator workstation servers".

[0047] Then, each of the controllers 4 controls the sub-process 3a or 3b of the process 3 to run respectively according to its operating state, wherein the sub-processes 3a, 3b are connected in series in the process flow direction of the process flow, that is, the sub-process 3b is connected in series downstream of the sub-process 3a. The process 3 includes actuators 7 that can be controlled by the controller 4. This can be a single actuator (such as a motor, pump, valve, switch), or a group of such actuators, or an entire section of the plant. The process also includes sensors 8 that supply the controller 4 with actual values of process variables (such as temperature, pressure, speed). The automation server 5 is assigned to the sub-process 3a, and the automation server 6 is assigned to the sub-process 3b. An automation system 2 without field devices (i.e., without actuators 7 and sensors 8) is also often referred to as a "process control system".

[0048] At a higher level, the communication network of device 1 includes a device network 10 (such as an industrial Ethernet network), via which the automation servers 5, 6 communicate with the operation and observation stations 18, which are also often referred to as "operator workstation clients"; the communication network also includes a control network 9 (such as an industrial Ethernet network), via which the controllers 4 are interconnected and communicate with the automation servers 5, 6. The controllers 4 can be connected to the actuators 7 and sensors 8 via separate signal lines 13 or via a field bus 15.

[0049] The automation servers 5, 6 store one or more device-specific application programs, which are executed during the operation of device 1. These application programs are used, for example, to configure the controllers 4 in device 1, record and execute operator activities at the operation and observation stations 18 (such as setting or changing the rated values of process variables), or generate information for the device personnel and display it on the operation and observation stations 18.

[0050] The automation system 2 also includes an engineering server 17 and an engineering client 11, which are also connected to the device network 10. The engineering server 17 and the engineering client 11 form an engineering system 19, which is used to create or project-plan device-specific application programs in the automation servers 5, 6.

[0051] There can also be other operator workstation clients and / or engineering clients, as well as other engineering servers, archive servers, batch processing systems, etc., which are not shown, and they can be connected to the device network 10.

[0052] The servers 5, 6, 17 each include a web server that provides a web application. A web browser is installed and running on the operation and observation stations 18 and the engineering stations 11, and the web browser communicates or can communicate with the web servers of the servers 5, 6, 17 via the network 10.

[0053] Engineering system 19 is used to generate and configure device-specific application programs in automation servers 5, 6. This includes creating a hierarchy 20 of the technology (i.e., process technology) of the device using suitable software of the engineering system 19. This technology hierarchy 20 is also often referred to as the "equipment hierarchy" and is stored in the memory 25 of the engineering server 17. In this technology hierarchy 20, process objects such as measurement points, tanks, valves, sensors, actuators, Continuous Function Chart (CFC), Sequential Function Chart (SFC), etc. are entered or saved in a structured manner according to a tree structure. After creation, the technology hierarchy 20 is compiled by the engineering system 19 and then loaded into the automation servers 5, 6 and thus into the runtime environment of the automation system 2. Then, in the automation servers 5, 6, the technology hierarchy 20 forms the basis of the process image, which has a data structure of process objects assigned to the respective automation server.

[0054] For operating and observing the device 1, during the runtime of the device 1, different device images are presented to the operator on the graphical user interface of the operator workstation client 18 by the application servers 5, 6. Navigation between the device images is carried out using a so-called device image hierarchy, i.e., the device images for operation and observation are presented hierarchically in a (scrollable and collapsible) tree structure. Using this tree structure, the operator can select and open device images during the operation of the technical device via this tree structure.

[0055] Each node in the image hierarchy references a device image and preferably also references a so-called group alarm status. The group alarm status shows the alarm status of the corresponding device image, i.e., according to the alarm categories, all alarms of the process objects in the device image are summarized separately and displayed in the image hierarchy. This allows the operator of the automation system 2 of the device 1 to immediately identify, when viewing the image hierarchy, in which device image there are process objects that have triggered an alarm. Using so-called Loop-In, the operator can directly navigate to these process objects. This is still feasible even if the process objects cannot be identified in the compact image hierarchy.

[0056] Engineering system 19 is also used to (statically) generate or plan a device image hierarchy 21 and to store the attached hierarchy information in a memory 25. For this purpose, the engineering system includes a dedicated device image hierarchy editor 22, which is also stored as a program in the memory 25 of the engineering server 17. The engineering server 17 also includes at least one processor 26, which is connected to the memory 25 and is configured to execute the method for generating the device image hierarchy 21 described below.

[0057] Since it is often necessary to use hundreds of device images to operate and observe the device 1, in the prior art, the generation of the device image hierarchy 21 is time-consuming and error-prone.

[0058] In addition, Figure 2 Exemplarily, it is shown that, according to the prior art, a graphical output 30 of the device image hierarchy editor 22 is performed on the display 12 of the engineering client 11. The graphical output includes three regions 31, 32, 33.

[0059] In the left region 32, the technical hierarchy 20 of the device 1 with different process objects is shown. In the exemplary embodiment, at the first highest level, the technical hierarchy includes the device 1 as the "device 1" with the assigned device image "start image". At the second hierarchy level below, the device 1 is subdivided into "sub-device 1", "sub-device 2" and the complete set unit "PU(MTP)1". Then device components are assigned to them, such as the first tank "tank 1", the first stirrer "stirrer 1", the second tank "tank 2" and the second stirrer "stirrer 2", and each device component has process objects hierarchically subordinate to them, such as device images (image 1, image 2, image 3, etc.) and continuous flowcharts CFC1, CFC2, CFC3, etc.

[0060] In the prior art, in the region 31, all the device images existing in the technical hierarchy 20 are provided to the project engineer in a flat list at the same level, which is excerpted here as images 4 to 26.

[0061] The region 33 of the device image hierarchy editor 22 is used by the project engineer to create a device image hierarchy 34.

[0062] To this end, the project engineer must select individual device images by clicking on the device images in the selection area 31, move them to area 33 using a graphical drag & drop operation (represented by arrow 39'), arrange them there, and connect them to other device images in a structured manner to form a device image hierarchy 34 (represented by connection 39). Advantageously, by dragging the selected device image onto the device image in area 33, the connection 39 is automatically generated in a particularly simple manner. This subordinates the selected device image to the device image in which it is located.

[0063] In this case, below the start image 35, the device image hierarchy 34 includes a first hierarchy level E1, a second hierarchy level E2 below the first hierarchy level, and a third hierarchy level E3 below the second hierarchy level.

[0064] Device images 36, 37, 38 are respectively assigned to device images of a higher hierarchy level. In this case, device images 36, 37 of the second hierarchy level E2 are assigned to device image 35 of the first hierarchy level E1, while device image 38 of the third hierarchy level E3 is assigned to device image 36 of the second hierarchy level E2.

[0065] Device images 36, 37 located on the same level are assigned to a sequence of the technical method structure. For example, according to Figure 1 , device image 36 relates to subprocess 3a, and device image 37 relates to the subsequent subprocess 3b. Thus, device images 36, 37 are arranged in the sequence of process flow 3 from left to right.

[0066] However, selecting device images in area 31 and arranging and interconnecting them in area 33 is time-consuming and potentially error-prone.

[0067] To reduce this cost and likelihood of errors, according to the present invention, pre-structuring of the device images is performed in time before the structuring process.

[0068] By means of the method flow 80 shown in Figure 8 , a method for pre-structuring according to the present invention is described:

[0069] In the first step 81, for at least part of the second hierarchical level E2 and the lower hierarchical level E3, the engineering system 19 has respectively recorded hierarchical information related to the device images of the higher hierarchical levels and sequence information related to the sequences of other device images respectively assigned to the same hierarchical levels before the actual structured storage of the device images by the project engineer (i.e., the structuring through interconnection), and stored them in the memory 25. In this case, the sequence relates to the process engineering structure of device 1.

[0070] When the device images are imported into the engineering system 19 (e.g., through a request by the project engineer for data input on the engineering client 11), this information can be automatically recorded, or manually recorded by the project engineer at a later time point. In the case of providing modular, pre-structured device components of the device images, the construction information regarding the hierarchy and sequence of these device images already provided (supplied) by these device components is automatically taken into account.

[0071] In the second step 82, this hierarchical information and sequence information are stored in the memory 25 of the engineering server 17.

[0072] In the third step 83, the device images are output to the project engineer for selection in the area 31 of the editor 21. Preferably, the device images are output in the same structure as in the technical hierarchy shown in area 32 of device 1.

[0073] In the fourth step 84, the selection information recorded by the project engineer, which is related to the selection of the device images output in the area 31 in the third step 83. This selection is used for their subsequent structured interconnection related to the hierarchy and sequence.

[0074] In the fifth step 85, in the area 33 of the editor 21, the device images selected in the fourth step 84 for their subsequent structured interconnection are output to the project engineer. The selected device images assigned with hierarchical information and sequence information are automatically pre-structured regarding the hierarchy and sequence in the area 33 according to these assigned information.

[0075] Then this pre-structuring can be corrected or supplemented as needed in the sixth step 86 to complete the device image hierarchy 21.

[0076] In addition, Figure 3 The attached object module 40 feasible in the engineering server 17 is shown.

[0077] Here, the core components are different device images 41, each assigned a graphical object 44, which graphical objects include, for example, tile symbols 45 and panels 46. The device image hierarchy is defined by a structure folder 42, which in turn is assigned to a specific device item 43. The device image hierarchy is defined using a device image hierarchy editor 22 (extended according to the invention). According to the invention, as described above, hierarchy information HI and sequence information RI can be assigned to the device images 41 respectively. The pre-structured device images 41 can still be planned by the project engineer 50 (represented by arrow 53). However, this can also be achieved when importing the presentation 48 of a modular, pre-configured process engineering equipment component (Package Unit), which presentation also includes the presentation of the device images to be generated and their interrelationships. A dedicated package unit import / export editor 49 can be used to read the package unit presentation 48 (represented by arrow 51) and generate device images with hierarchy information HI and sequence information RI (represented by arrow 52).

[0078] Now, Figures 4 to 7 An exemplary embodiment of working according to the invention using the (extended) device image hierarchy editor 22 is shown.

[0079] As in Figure 1 area 32, Figure 4 The technical hierarchy of device 1 is shown in the left area 32. Currently, in area 31, device images of the device structured according to technology that have not been assigned to the device image hierarchy in area 33 are output. Hierarchy information and sequence information are assigned to the images marked with an asterisk "*" respectively (here, image 1 and image 2 are from tank 1 and image 1, image 2, and image 3 are from PU(MTP)1), that is, these device images have been pre-structured.

[0080] According to Figure 5 , currently, the device images in area 31 can be selected by clicking on them, and then they can be placed in area 33 by drag-and-drop (represented by arrow 65) and interconnected to form a device image hierarchy 60. Different hierarchy levels of the device image hierarchy 60 are labeled with E1, E2, and E3.

[0081] In Figure 5 the case of, for example, by clicking on the corresponding higher-level structure node, device image 63 "image 2" and device image 64 "image 1" are selected from the device component "tank 1", and device image 62 "image 3" is selected from the device component "agitator 1", and they are placed in area 33 by drag-and-drop.

[0082] If there are pre-structured device images below, this structuring is automatically taken into account by the device image hierarchy editor 22, here the device images 63 "Image 2" and 64 "Image 1" of the component "Tank 1" as shown. Although these two device images 63, 64 are at the same level in the technical hierarchy, the pre-structuring can indicate, for example, that the device image 64 "Image 1" is subordinate to the device image 63 "Image 2".

[0083] By selecting the corresponding higher-level structure node in the area 31 and then directly placing it on the device image 61 using drag and drop, the pre-structured device images 63, 64 and the device image 62 "Image 3" of the component "Stirrer 1" can be made subordinate in the hierarchy under the device image 61. This automatically creates the interconnection represented by the connecting line 69. Optionally, this can be achieved by the project engineer in the editor 22 by creating a manual connection.

[0084] As Figure 6 shown, only the device images that have not yet been used in the hierarchy 60 are displayed in the area 31 for selection. Thus, further generation or project planning of the device image hierarchy 60 can be carried out very efficiently.

[0085] In the case of the complete unit PU(MTP)1, it is assumed that after being imported into the engineering system 19, this complete unit is also pre-structured with hierarchy information and sequence information, where the device images "Image 3" and "Image 2" are respectively subordinate to "Image 1", and in the process engineering sequence, "Image 3" is before "Image 2".

[0086] If now these device images of the complete unit PU(MTP)1 are selected by clicking and dragging the higher-level structure node PU(MTP)1 and placed in the area 33, according to this pre-structuring, they are output in the area 33 (see the device images 71, 72, 73 in Figure 6 . The project engineer now only needs to interconnect them with the existing device image hierarchy 60, in this case, for example, making them subordinate to the device image 62, represented by the connecting line 74. By selecting the higher-level structure node PU(MTP)1 and directly placing it in the device image 62 using drag and drop, this interconnection has been particularly advantageously automatically achieved.

[0087] As Figure 7 shown, the technical structuring list of the device images in the area 31 is thus further reduced.

[0088] In principle, all device images can also be pre-structured by correspondingly assigning hierarchical information and sequence information. Then, in area 31, simply click on and select the top structural node (here, "Device 1") and use drag-and-drop to place it in area 33. Immediately in area 33, the device image hierarchy 60 defined by the hierarchical information and sequence information is automatically output. In this way, the highest efficiency can be achieved when generating the device image hierarchy 60.

[0089] Of course, even if the device image has been pre-structured, it is still possible to elaborate on the adjustment of the device image hierarchy 60 in area 33 at any time. The pre-structuring of the device image and the technical and structural organization in area 31 are essentially used to ensure efficient "initialization".

[0090] In this exemplary embodiment, the engineering system 19 is described in the form of a client-server architecture. However, this should not be construed as restrictive. Other architectures are also feasible. For example, the engineering system 19 can also be implemented by a single computer.

[0091] In summary, by pre-structuring device images according to the present invention, it is possible to generate or project-plan device image hierarchies more efficiently and with fewer errors, especially by improving the integration or replacement of modular device components in hybrid process engineering equipment, particularly via modular, pre-configured process engineering equipment components (package units), especially MTP.

Claims

1. A computer-implemented method for generating a device image hierarchy (60), in which device images (61, 62, 63) for operating and observing a process engineering device (1) to be controlled are stored in a structured manner with respect to the hierarchy and sequence, and the device images can be selected and opened by an operator during the runtime of the device (1), wherein, In structured storage: - The device image hierarchy (60) includes at least a first hierarchy level and a second hierarchy level (E1, E2), - The device images of the second hierarchy level (E2) are assigned to the device images of the first hierarchy level (E1), - Each device image of the second hierarchy level (E2) assigned to the same device image of the first hierarchy level (E1) is assigned to a sequence, in particular to a sequence regarding the process engineering structure of the device (1), It is characterized by the following steps: a) Assign respectively to at least some of the device images (62, 63) of the second hierarchy level (E2): - Hierarchy information (HI) regarding the device images of the first hierarchy level (E1), and - Sequence information (RI) related to the sequences of the other device images of the second hierarchy level (E2) assigned to the same device image of the first hierarchy level (E1), the sequence being in particular a sequence regarding the process engineering structure of the device (1), wherein the assignment is carried out before the structured storage of the device images, b) Output the device images for selection, c) Record selection information regarding the selection of the device images output in step b), the selection information being used for the subsequent structured interconnection of the device images regarding hierarchy and sequence, d) Output the device images selected in step c) for the subsequent structured interconnection of the device images, wherein the device images with assigned hierarchy information (HI) and sequence information (RI) are automatically pre-structured according to the correspondingly assigned hierarchy information (HI) and sequence information (RI).

2. The method according to claim 1, wherein, At least some of the device images with assigned hierarchy information and sequence information (HI, RI) relate to modular and pre-configured process engineering device components (PU(MTP)1), in particular module type packages.

3. The method according to any one of the preceding claims, wherein, The device images are defined by the technical hierarchy (20) of the device (1).

4. The method according to claim 3, wherein Output the device images in a structured manner in step b) according to the technical hierarchy (20) of the device.

5. The method according to any one of the preceding claims, wherein, Generate the device image hierarchy (60) in an engineering system (19), and wherein the hierarchy information and sequence information (HI, RI) are assigned when importing device images into the engineering system (19).

6. The method according to any one of the preceding claims, wherein, Define the selection information by a mobile operation that can be performed by a project engineer.

7. The method according to any one of the preceding claims, wherein, For the selection in step b), only output device images that are not yet included in the device image hierarchy (60).

8. An engineering system (19) for generating a device image hierarchy (60) in which device images (61, 62, 63) for operating and observing a process engineering device (1) to be controlled are stored in a structured manner with respect to the hierarchy and sequence, and the device images can be selected and opened by an operator during the runtime of the device (1), wherein, In structured storage: - The device image hierarchy (60) includes at least a first hierarchy level and a second hierarchy level (E1, E2), - The device images of the second hierarchy level (E2) are assigned to the device images of the first hierarchy level (E1), - Each device image of the second hierarchy level (E2) assigned to the same device image of the first hierarchy level (E1) is assigned to a sequence, in particular to a sequence regarding the process engineering structure of the device (1). The engineering system includes at least one processor (26) which is connected to a memory (25). It is characterized in that at least one of the processors (26) is configured such that the processor executes the method according to any one of the preceding claims.

9. A computer program comprising instructions which, when the program is executed by a computer, cause the computer to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium comprising instructions which, when executed by a computer, cause the computer to implement the method according to any one of claims 1 to 7.

Images