JP7699521B2 - ENGINEERING APPARATUS AND ENGINEERING METHOD - Google Patents

Description

This invention relates to an engineering device and an engineering method for performing various settings on devices that make up a facility monitoring system.

Conventionally, there is known an engineering device that creates configuration data for operating multiple devices (e.g., a primary device and a secondary device) that monitor or control equipment installed in a facility (see, for example, Patent Document 1). The engineering device creates configuration data for each device, and downloads (receives) the created configuration data to each device, thereby constructing a facility monitoring system. Each device operates based on the configuration data downloaded from the engineering device, and monitors or controls other devices other than itself, or one or more pieces of equipment installed in the facility.

For example, a facility monitoring system includes a primary device, a secondary device connected to the primary device, and equipment connected to the secondary device. The primary device monitors or controls the secondary device by operating based on configuration data downloaded from the engineering device. The secondary device monitors or controls the equipment by operating based on configuration data downloaded from the engineering device.

When constructing a facility monitoring system, the engineering device operates in engineering mode and, for example, displays a setting screen on the display device. The setting screen is a screen for creating and checking setting data, and has items (cells) that indicate the setting data. The administrator or the like performs engineering work by creating setting data using the setting screen. Note that this setting screen is not only a screen for creating and checking setting data for the primary device, but also a screen for creating and checking setting data for the secondary device. The engineering device stores a compilation of the setting data obtained through the engineering work of the administrator or the like in a single storage unit (database) as engineering data.

Figure 10 shows an example of writing setting data to a device by an engineering device in a conventional facility monitoring system. As shown in Figure 10, in a conventional facility monitoring system 2000, an engineering device 60 writes the setting data for a primary device 70, which is among the engineering data stored in the storage unit, to the primary device 70. The engineering device 60 also writes the setting data for a secondary device 80, which is among the engineering data stored in the storage unit, to the secondary device 80. Note that an administrator or the like usually writes the setting data to the primary device 70, and then writes the setting data to the secondary device 80. However, conversely, if necessary, the setting data may be written to the secondary device 80 before the setting data is written to the primary device 70 (advance adjustment).

Another example of the above is shown in FIG. 11. As shown in FIG. 11, the engineering device 60 writes the setting data for the primary device 70 from among the engineering data stored in the storage unit to the primary device 70, as in FIG. 10 (reference symbol (1)). On the other hand, for the secondary device 80, the engineering device 60 may directly connect to the secondary device 80 installed on-site after shipment from the factory using a pre-installed "connect mode" and write the setting data (reference symbol (2)). In the "connect mode", the engineering device 60 directly connects to a device in the network and can edit the setting data for the connected device, as well as obtain (back up) the setting data from the device.

In addition, since the secondary devices 80 often have similar configurations, once writing of the configuration data to one secondary device 80 is complete, the configuration data may be backed up and the backed up configuration data 810 may be deployed to another secondary device 80 (symbol (3)). In addition, after the backed up configuration data 810 is deployed, the configuration data 810 may be partially changed on the destination secondary device 80.

JP 2020-160909 A

However, since the facility monitoring system 2000 generally has a large number of secondary devices 80, the amount of configuration data for the secondary devices 80 is large, and therefore the amount of engineering data stored in the engineering device 60 is also large. In the facility monitoring system 2000, the engineering data stored in the engineering device 60 is managed as master data.

On the other hand, editing (creating, modifying, deleting, etc.) engineering data may involve multiple administrators (engineers). For example, as shown in FIG. 12, editing of the setting data for the primary device 70 may be performed by administrators A and B, while editing of the setting data for the secondary device 80 may be performed by administrators C and D. In such a case, if the volume of engineering data stored in the storage unit 610 of the engineering device 60 is large, there is a problem that the efficiency of engineering work may decrease, as it may become necessary to divide the engineering data into multiple pieces of data and transfer it between administrators.

This invention has been made to solve the above problems, and aims to provide an engineering device that can suppress the decrease in efficiency of engineering work that occurs due to an increase in the volume of engineering data.

The engineering device according to the present invention is characterized by comprising: a reception unit that receives a deletion instruction to delete setting data set in a device that belongs to a lower hierarchical level than the hierarchical level to which any one of the devices belongs from engineering data that compiles setting data set in each device in a network in which multiple hierarchical levels to which one or more devices belong, and a deletion unit that deletes from the engineering data the setting data set in a device that belongs to a lower hierarchical level than the hierarchical level to which any one of the devices belongs, based on the deletion instruction received by the reception unit.

With the above-mentioned configuration, this invention makes it possible to suppress the decrease in efficiency of engineering work that accompanies an increase in the volume of engineering data.

1 is a diagram showing a configuration example of a facility monitoring system including an engineering device according to a first embodiment; FIG. 1 is a diagram illustrating a configuration example of an engineering device according to a first embodiment. 11 is a flowchart showing an example of an operation of a deletion process by the engineering device according to the first embodiment; FIG. 13 is a diagram showing an example of an editing screen for setting data in the first embodiment. FIG. 5A is a diagram illustrating an example of an icon displayed in the operation area of the editing screen, and FIG. 5B is a diagram illustrating the state in which the configuration data set for the secondary device has been deleted from the engineering data. FIG. 13 is a diagram illustrating a configuration example of an engineering device according to a second embodiment. 13 is a flowchart showing an example of an operation of a restoration process by an engineering device according to the second embodiment; FIG. 11 is a diagram for explaining an overview of restoration of engineering data in the second embodiment. FIG. 11 is a diagram showing an example of an editing screen for registering information regarding the type, etc., of a secondary device in embodiment 2. FIG. 1 is a diagram illustrating an example of writing setting data to a device by an engineering device in a conventional facility monitoring system. 11 is a diagram illustrating another example of writing of setting data to a device by an engineering device in a conventional facility monitoring system. FIG. FIG. 1 is a diagram illustrating an example in which a plurality of managers are involved in editing engineering data in a conventional facility monitoring system.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.
Embodiment 1.
Fig. 1 is a diagram showing a configuration example of a facility monitoring system 1000 including an engineering device 10 according to embodiment 1. As shown in Fig. 1, the facility monitoring system 1000 includes the engineering device 10, a primary device 20, and a secondary device 30. The engineering device 10, the primary device 20, and the secondary device 30 are connected via a network.

In FIG. 1, the facility monitoring system 1000 has one primary device 20 and three secondary devices 30, but the number of primary devices 20 and secondary devices 30 is not limited to this. Also, the secondary device 30 is connected to a device to be controlled or monitored, but this device is not shown in FIG. 1.

The engineering device 10 performs engineering processing including the creation of the above-mentioned setting data, and constructs the facility monitoring system 1000. The setting data is, for example, setting data for the primary device 20 for the primary device 20 to monitor or control the secondary device 30 under it, and setting data for the secondary device 30 for the secondary device 30 to monitor or control the equipment under it. The engineering device 10 also stores data that combines the setting data for the primary device 20 and the setting data for the secondary device 30 as engineering data in the storage unit 104 (see FIG. 2).

The primary device 20 downloads from the engineering device 10 the configuration data corresponding to itself among the engineering data held by the engineering device 10, and operates based on the downloaded configuration data to monitor or control the secondary device 30 under its control.

The secondary device 30 downloads from the engineering device 10 the configuration data corresponding to itself among the engineering data held by the engineering device 10, and operates based on the downloaded configuration data to monitor or control the equipment under its control. The equipment is installed within the facility and is composed of, for example, a sensor, a thermometer, a motor, a damper, or a power meter.

In FIG. 1, the network NW constituting the main part of the facility monitoring system 1000 is configured with two hierarchical layers: an upper layer including the primary device 20, and a lower layer including the secondary device 30. Note that, although an example is described here in which the network NW is configured with two layers stacked, each layer including one or more devices, the network NW is not limited to this, and may be configured with three or more layers stacked, each layer including one or more devices.

Next, a configuration example of the engineering device 10 according to the first embodiment will be described with reference to FIG. 2.

As shown in FIG. 2, the engineering device 10 includes a reception unit 101, a deletion unit 102, a display control unit 103, and a storage unit 104. The engineering device 10 is also connected to a display device 50 such as a display.

The storage unit 104 stores engineering data that summarizes the configuration data set for each device in the network NW, which is composed of multiple stacked hierarchies to which one or more devices belong. In the example of FIG. 1, the network NW is composed of two stacked hierarchies to which one or more primary devices 20 and one or more secondary devices 30 belong.

The reception unit 101 receives a deletion instruction from an administrator or the like. The deletion instruction is an instruction to delete the setting data set for a device that belongs to a lower hierarchical level than the hierarchical level to which any of the devices belongs from the engineering data stored in the storage unit 104, i.e., the engineering data that compiles the setting data set for each device in the network NW, which is made up of multiple stacked hierarchical levels to which one or more devices belong. There is no particular limitation on the method by which the reception unit 101 receives the deletion instruction, but for example, the reception unit 101 may receive the deletion instruction via an editing screen, described below, displayed on the display device 50 by the display control unit 103.

Specifically, the display control unit 103 causes the display device 50 to display an editing screen of the setting data set for a device (e.g., the primary device 20) selected by an administrator or the like (user) as an arbitrary device from among the devices in the network NW, based on the engineering data stored in the storage unit 104. Then, when a deletion instruction is given by the administrator or the like via the editing screen displayed on the display device 50, the reception unit 101 receives the deletion instruction.

At this time, the display control unit 103 may display an icon for accepting a deletion instruction on the editing screen. In this case, the accepting unit 101 accepts the deletion instruction when the administrator or the like operates (e.g., presses) the icon on the editing screen.

Based on the deletion instruction received by the reception unit 101, the deletion unit 102 deletes the configuration data set for a device that belongs to a lower hierarchy than the hierarchy to which the device selected by the administrator or the like as an arbitrary device belongs from the engineering data held in the holding unit 104.

The functions of the reception unit 101, the deletion unit 102, and the display control unit 103 are realized, for example, by a central processing unit (CPU) (not shown) of the engineering device 10 executing a predetermined program deployed in a memory (not shown). The storage unit 104 is configured, for example, by a hard disc drive (HDD), a solid state drive (SSD), or a memory.

Note that while FIG. 2 shows a case where the holding unit 104 is provided inside the engineering device 10, the holding unit 104 may also be provided outside the engineering device 10.

Next, an example of the operation of the engineering device 10 according to the first embodiment shown in FIG. 2 will be described. In the first embodiment, the engineering device 10 mainly performs a deletion process to delete from the engineering data the configuration data set for devices that belong to a lower hierarchy than the hierarchy to which the device selected by the administrator or the like belongs. This deletion process will be described with reference to the flowchart in FIG. 3.

In the following, for simplicity of explanation, it is assumed that the engineering data is stored in advance in the storage unit 104. Also, the administrator or the like selects the primary device 20 as an arbitrary device, and the display control unit 103 causes the display device 50 to display an editing screen of the setting data set in the primary device 20 in response to this selection. Also, the administrator or the like presses an icon on the editing screen displayed on the display device 50, and the reception unit 101 accepts a deletion instruction based on the administrator or the like pressing the icon on the editing screen displayed on the display device 50.

First, the display control unit 103 causes the display device 50 to display an editing screen for the configuration data set in the primary device 20 selected by an administrator or the like as an arbitrary device (step ST301).

An example of this editing screen is shown in FIG. 4. On the editing screen 401 shown in FIG. 4, it is possible to edit (create, change, delete, etc.) the setting data set in the primary device 20. In this case, the setting data to be edited (setting data for the primary device 20) is the setting data for the primary device 20 included in the engineering data held in the holding unit 104.

The editing screen 401 shown in FIG. 4 is broadly composed of three areas (item display area 402, detail display area 403, and operation area 404). Of these, the item display area 402 displays a tree of multiple items that make up the setting data for the primary device 20, and multiple items that make up the setting data for the secondary device 30. Here, the part where the former items are displayed is referred to as the "primary device part 4021," and the part where the latter items are displayed is referred to as the "secondary device part 4022."

When an administrator or the like selects a desired item from these items, the setting data for the selected item is displayed in the details display area 403. In addition, the operation area 404 displays various menus for editing the setting data displayed in the details display area 403. Although not explained here, the editing screen 401 may also include an attribute display area that displays more detailed information such as the attributes (properties) of the item.

Here, the administrator or the like can edit the setting data for the primary device 20 by selecting a desired item from the primary device portion 4021 displayed in the item display area 402. Similarly, the administrator or the like can edit the setting data for the secondary device 30 by selecting a desired item from the secondary device portion 4022 displayed in the item display area 402. At this time, the setting data to be edited is the setting data included in the engineering data held in the holding unit 104.

However, the administrator in charge of editing the setting data for the primary device 20 does not necessarily need the setting data for the secondary device 30, and there are many situations in which the setting data for the secondary device 30 is not needed. Also, as mentioned above, there are many secondary devices 30, and the volume of the setting data for the secondary devices 30 tends to be large.

As shown in FIG. 5A, an icon 4041 labeled "Delete secondary device information" is displayed in the operation area 404. This icon 4041 is for accepting a deletion instruction to delete from the engineering data the configuration data set for a secondary device 30 that belongs to a lower hierarchical level than the primary device 20 selected by the administrator or the like as an arbitrary device. The administrator or the like issues the above-mentioned deletion instruction by pressing this icon 4041.

The reception unit 101 receives a deletion instruction based on the administrator or the like pressing the icon 4041 (step ST302).

Next, based on the deletion instruction received by the reception unit 101, the deletion unit 102 deletes the configuration data set in the secondary device 30 that belongs to a lower hierarchy than the primary device 20 from the engineering data held in the holding unit 104 (step ST303).

As a result, in the engineering device 10, as shown in FIG. 5B, the configuration data set in the secondary device 30 is deleted from the engineering data stored in the storage unit 104, reducing the volume of the engineering data. This also eliminates the need for administrators, etc. to perform tasks such as dividing data when transferring engineering data by email, etc., improving the efficiency of engineering work.

As described above, according to the first embodiment, the engineering device 10 includes a reception unit 101 that receives a deletion instruction to delete setting data set in a device that belongs to a lower hierarchical level than the hierarchical level to which an arbitrary device belongs from engineering data that summarizes setting data set in each device in a network NW in which multiple hierarchical levels to which one or more devices belong are stacked, and a deletion unit 102 that deletes from the engineering data the setting data set in a device that belongs to a lower hierarchical level than the hierarchical level to which the arbitrary device belongs, based on the deletion instruction received by the reception unit 101. This makes it possible for the engineering device 10 to suppress a decrease in efficiency of engineering work that occurs due to an increase in the volume of engineering data.

In particular, as described above, by deleting the configuration data set for secondary devices 30, which are greater in number than primary devices 20, from the engineering data stored in the storage unit 104, it is possible to effectively suppress the decrease in efficiency of engineering work that accompanies an increase in the volume of engineering data.

Note that unlike the setting data for the primary device 20, the setting data for the secondary device 30 is rarely referenced by other functions (other devices). Furthermore, even if the setting data for the secondary device 30 is temporarily deleted from the engineering data, it is possible to restore it as engineering data by acquiring (backing up) it from the secondary device 30 and integrating it into the engineering data. In light of this, the engineering device 10 makes it possible to delete the setting data for the secondary device 30 from the engineering data. Note that the restoration of the engineering data will be described in detail in the second embodiment.

The engineering device 10 also includes a display control unit 103 that causes the display device 50 to display an editing screen 401 of the setting data set for a device selected by the user from among the devices in the network NW as an arbitrary device, and the reception unit 101 receives a deletion instruction via the editing screen 401 displayed on the display device 50 by the display control unit 103. This allows the administrator or the like to easily issue a deletion instruction to the engineering device 10.

The display control unit 103 also displays an icon 4041 for accepting a deletion instruction on the editing screen 401, and the accepting unit 101 accepts the deletion instruction when the icon 4041 on the editing screen 401 is operated by a user. This allows an administrator or the like to issue a deletion instruction to the engineering device 10 by the simple action of operating the icon 4041.

Embodiment 2.
In the first embodiment, an example was described in which setting data set in a device that belongs to a lower hierarchical level than a hierarchical level to which an arbitrary device belongs from engineering data that summarizes setting data set in each device in a network NW in which multiple hierarchical levels to which one or more devices belong is deleted. In the second embodiment, an example is described in which engineering data from which setting data has been deleted as described above is restored to the state before deletion.

In the facility monitoring system 1000, the engineering data stored in the storage unit 104 may be managed as master data. In that case, if the engineering data in the storage unit 104 is the engineering data after the above-mentioned deletion process, the setting data for the secondary device 30 has been deleted from this data, which may cause problems with subsequent engineering work. Therefore, the engineering device 10 restores the engineering data in the storage unit 104 to the state before the deletion process in response to instructions from an administrator, etc.

Figure 6 is a diagram showing an example of the configuration of an engineering device 10b according to the second embodiment. The engineering device 10b according to the second embodiment has a communication unit 105, an acquisition unit 106, and a data integration unit 107 added to the engineering device 10 according to the first embodiment. The other configuration of the engineering device 10b is similar to that of the engineering device 10 according to the first embodiment, so the same reference numerals are used and the description thereof is omitted.

The communication unit 105 communicates with each device within the network NW.

The acquisition unit 106 communicates with the device in which the setting data deleted by the deletion unit 102 is set via the communication unit 105, and acquires the setting data from the device.

The data integration unit 107 integrates the setting data acquired by the acquisition unit 106 with the engineering data deleted by the deletion unit 102, and restores the engineering data to the state before deletion.

Next, an example of the operation of the engineering device 10b according to the second embodiment shown in FIG. 6 will be described. In the second embodiment, the engineering device 10b mainly performs a process of restoring the engineering data. This restoration process will be described with reference to the flowchart in FIG. 7.

In the following explanation, it is assumed that the setting data for the secondary device 30 has been deleted from the engineering data by the deletion process described in the first embodiment, and an example will be described in which the engineering device 10d restores the engineering data from which the setting data for the secondary device 30 has been deleted to the state before the deletion.

First, the acquisition unit 106 communicates with the secondary device 30 via the communication unit 105 and acquires (backs up) configuration data from the secondary device 30 (step ST701).

Next, the data integration unit 107 integrates the setting data acquired by the acquisition unit 106 with the engineering data stored in the storage unit 104 that has been deleted by the deletion unit 102, and restores the engineering data to the state before deletion (step ST702).

The communication with the secondary device 30 by the acquisition unit 106 and the acquisition (backup) of the setting data are performed in the "connect mode" that is pre-installed in the engineering device 10. In the "connect mode", the engineering device 10 directly connects to a device in the network NW and can edit the setting data for the connected device, as well as acquire (backup) the setting data from the device as described above.

The data integration unit 107 restores the engineering data in a "difference check mode" that is pre-installed in the engineering device 10. In the "difference check mode," as shown in FIG. 8, the setting data 801 acquired (backed up) from the secondary device 30 is compared with the engineering data held in the holding unit 104 to extract differences, and the extracted differences can be incorporated into the engineering data held in the holding unit 104.

In this case, the engineering data stored in the storage unit 104 has had the setting data for the secondary device 30 deleted by the above-mentioned deletion process, so the setting data 801 acquired (backed up) from the secondary device 30 is directly imported into the engineering data in the storage unit 104 as a difference.

In the above, an example of performing the restoration process according to the flowchart in FIG. 7 has been described, but the administrator may perform the restoration process in a manner other than the above. For example, information regarding the type of the secondary device 30 is registered in the engineering device 10 as setting data for the primary device 20 so that the primary device 20 can grasp information regarding the type of the secondary device 30 subordinate thereto. This registration is performed in advance by the administrator, for example via the editing screen 401 in FIG. 4 described above.

An example of the editing screen in this case is shown in FIG. 9. In the example of FIG. 9, information relating to the type, etc. of the secondary device 30 (for example, secondary device type 901 in FIG. 9) can be registered via the editing screen 401. This information relating to the type, etc. of the secondary device 30 is registered as setting data for the primary device 20. Therefore, it will not be deleted by the above-mentioned deletion process.

The engineering device 10 also has a function of automatically generating initial setting data for the secondary devices 30 based on the information about the type of each secondary device 30 registered as described above.

The administrator, etc., can then use this automatic generation function to generate initial setting data for the secondary device 30. After that, the administrator, etc. can connect to the secondary device 30 using the above-mentioned "connect mode," and while checking the setting data that is actually set on the secondary device 30, correct the automatically generated initial values to the actual setting data, thereby restoring the final engineering data.

In addition, the engineering device 10 can perform advance adjustment without any problems by performing the restoration process described above. Advance adjustment means that when a primary device 20 and a secondary device 30 exist in the network NW, before creating setting data for the primary device 20, setting data for the secondary device 30 is created first, and the created setting data is sent to the secondary device 30 for writing or the written setting data is changed.

Advance adjustment is performed for the purpose of, for example, checking the connection between the secondary device 30 and equipment (e.g., a damper, etc.) connected under the secondary device 30 before configuration data for the primary device 20 is created. For example, the secondary device 30 may be installed in an attic or the like together with equipment such as a damper during installation work, but depending on the progress of the installation work, construction workers may be unable to enter the site, making it impossible to check the operation of the secondary device 30 installed in the attic or the like. Therefore, advance adjustment is used to write configuration data to the secondary device 30 and check its operation before configuration data for the primary device 20 is created.

Even if such advance adjustment is performed, the setting data for the secondary device 30 may be deleted from the engineering data by the deletion process described in the first embodiment. However, in the engineering device 10b, as described above, the engineering data can be restored to the state before deletion by performing a restoration process of the engineering data, for example, by acquiring (backing up) the setting data from the secondary device 30. Therefore, in the engineering device 10b, advance adjustment can be performed without any problems.

Even if advance adjustment is not performed, i.e., if the setting data for the secondary device 30 is created after the setting data for the primary device 20 is created, the engineering data can be restored to the state before deletion by performing the restoration process in the same manner as described above, by obtaining (backing up) the setting data from the secondary device 30.

As described above, according to the second embodiment, the engineering device 10b includes a communication unit 105 that communicates with each device in the network NW, an acquisition unit 106 that communicates with a device in which the setting data deleted by the deletion unit 102 is set via the communication unit 105 and acquires the setting data from the device, and a data integration unit 107 that integrates the setting data acquired by the acquisition unit 106 with the engineering data deleted by the deletion unit 102 and restores the engineering data to the state before the deletion. This allows the engineering device 10 to restore the engineering data that has been deleted to the state before the deletion. Also, for example, even if the setting data for the secondary device 30 created by the advance adjustment is deleted from the engineering data after the administrator or the like performs advance adjustment, the deleted setting data can be integrated into the engineering data to restore the state before the deletion.

In addition, within the scope of the present invention, it is possible to freely combine the various embodiments, modify any of the components of each embodiment, or omit any of the components of each embodiment.

1000, 2000 Facility monitoring system 10, 10b, 60 Engineering device 20, 70 Primary device 30, 80 Secondary device 50 Display device 101 Reception unit 102 Deletion unit 103 Display control unit 104 Storage unit 105 Communication unit 106 Acquisition unit 107 Data integration unit 401 Edit screen 402 Item display area 403 Details display area 404 Operation area 610 Storage unit 801 Setting data 810 Setting data 901 Secondary device type 4021 Primary device section 4022 Secondary device section 4041 Icon

Claims (3)

Based on engineering data that summarizes the configuration data set for each device in a network that has multiple layers in which one or more devices belong,
a display control unit that causes a display device to display an editing screen for the setting data set in a device selected by a user from among the devices in the network , the editing screen including an icon for receiving a deletion instruction for deleting the setting data set in a device that belongs to a lower hierarchy than the hierarchy to which the device selected by the user belongs;
a receiving unit that receives the deletion instruction via a user's operation on the icon ;
a deletion unit that deletes, based on the deletion instruction received by the reception unit, configuration data set for a device that belongs to a lower hierarchy than a hierarchy to which the device selected by the user belongs from the engineering data;
Engineering equipment with. A communication unit that communicates with each device in the network;
an acquisition unit that communicates with a device in which the setting data deleted by the deletion unit is set via the communication unit, and acquires the setting data from the device;
a data integration unit that integrates the setting data acquired by the acquisition unit with the engineering data deleted by the deletion unit to restore the engineering data to a state before the deletion;
2. The engineering device according to claim 1, further comprising: An engineering method using an engineering device, comprising:
A display control unit
Based on engineering data that summarizes the configuration data set for each device in a network that has multiple layers in which one or more devices belong,
displaying on a display device an editing screen for the setting data set in a device selected by a user from among the devices in the network , the editing screen including an icon for receiving a deletion instruction for deleting setting data set in a device that belongs to a lower hierarchy than the hierarchy to which the device selected by the user belongs;
a receiving unit receiving the deletion instruction via a user's operation on the icon ;
a deletion unit deleting, based on the deletion instruction received by the reception unit, configuration data set for devices belonging to a lower hierarchy than a hierarchy to which the device selected by the user belongs, from the engineering data;
An engineering method having the following features:

Images