Engineering apparatus and engineering method

Abstract

To provide an engineering device capable of suppressing a reduction in efficiency of engineering work in association with an increase in capacity of engineering data.SOLUTION: An engineering device 10 comprises: a common data receiving unit for receiving, from among setting data set for a plurality of individual devices which monitor or control instruments set in a facility, the setting data set in common to two or more of the devices as common data; and a registration unit 102 for registering, on a holding unit 104, the common data received by the common data receiving unit distinctively from the setting data set separately in the plurality of individual devices.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to an engineering device and an engineering method for performing various settings on devices constituting a facility monitoring system.

Background Art

[0002] Conventionally, an engineering device for creating setting data for operating a plurality of devices (for example, a primary device and a secondary device, etc.) for monitoring or controlling devices installed in a facility has been known (see, for example, Patent Document 1). The engineering device creates setting data for each device and downloads (receives) the created setting data to each device to construct a facility monitoring system. Each device operates based on the setting data downloaded from the engineering device and monitors or controls other devices other than itself or one or more devices installed in the facility.

[0003] For example, a facility monitoring system includes a primary device, a secondary device connected under the primary device, and a device connected under the secondary device. The primary device operates based on the setting data downloaded from the engineering device to monitor or control the subordinate secondary devices. Also, the secondary device operates based on the setting data downloaded from the engineering device to monitor or control the subordinate devices.

[0004] When constructing a facility monitoring system, the engineering device operates in an engineering mode and, for example, displays a setting screen on a display device. The setting screen is a screen for creating and checking setting data and has items (cells) indicating the setting data. Then, an administrator or the like performs engineering work by creating the setting data or the like using the setting screen. Note that this setting screen is prepared not only as a screen for creating and checking setting data for a primary device but also as a screen for creating and checking setting data for a secondary device. Then, the engineering device holds, as engineering data, data obtained by collecting the setting data obtained through engineering work by an administrator or the like in one holding unit (database).

[0005] For example, as shown in FIG. 20, in a conventional facility monitoring system 2000, an engineering device 60 writes setting data for a primary device 70 among the engineering data held in the holding unit to the primary device 70. Further, the engineering device 60 writes setting data for a secondary device 80 among the engineering data held in the holding unit to the secondary device 80. Note that an administrator or the like usually writes the setting data for the primary device 70 first and then writes the setting data for the secondary device 80. However, conversely, there are cases where the setting data for the secondary device 80 is written before the setting data for the primary device 70 (prior adjustment).

[0006] Also, as shown in FIG. 21, for the primary device 70, similar to FIG. 20, the engineering device 60 writes the setting data for the primary device 70 among the engineering data held in the holding unit to the primary device 70 (reference sign (1)). On the other hand, for the secondary device 80, the engineering device 60 may directly connect to the secondary device 80 installed at the site after factory shipment by the "connect mode" pre-installed in the device itself and write the setting data (reference sign (2)). In the "connect mode", the engineering device 60 can directly connect to the devices in the network constructed in the facility monitoring system, edit the setting data for the connected device, etc., and can also acquire (backup) the setting data from the device.

[0007] In addition, since the secondary device 80 often has a similar configuration, after the writing of the setting data for one secondary device 80 is completed, the backup of the setting data 810 may be performed, and the backed-up setting data 810 may be deployed to other secondary devices 80 (reference sign (3)). Also, after the deployment of the backed-up setting data 810, the setting data 810 may be partially changed in the secondary device 80 at the deployment destination.

Prior Art Documents

Patent Documents

[0008]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0009] By the way, in the facility monitoring system 2000, generally, since the number of secondary devices 80 is large, the capacity of the setting data for the secondary devices 80 also becomes large, and as a result, the capacity of the engineering data held in the engineering device 60 also becomes large. Note that in the facility monitoring system 2000, the engineering data held in the engineering device 60 is managed as master data.

[0010] On the other hand, when editing (creating, changing, deleting, etc.) engineering data, a plurality of administrators (engineers), etc. may be involved. For example, as shown in FIG. 22, the setting data for the primary device 70 is edited by administrator A and administrator B, and the setting data for the secondary device 80 is edited by administrator C and administrator D. In such a case, if the capacity of the engineering data held in the holding unit (reference numeral 610 in FIG. 22) of the engineering device 60 is large, there is a problem that the efficiency of the engineering work may decrease, such as the need to divide and transfer the engineering data to a plurality of data when transferring the engineering data between administrators.

[0011] The present invention has been made to solve the above-described problems, and an object thereof is to provide an engineering device capable of suppressing a decrease in the efficiency of engineering work due to an increase in the capacity of engineering data.

Means for Solving the Problems

[0012] The engineering device according to the present invention includes a common data reception unit that receives common data set in common for two or more devices among the setting data set for each of a plurality of devices that monitor or control devices installed in a facility, an individual data reception unit that receives individual data that is data other than the common data among the setting data, and a registration unit that registers the common data received by the common data reception unit and the individual data received by the individual data reception unit in a holding unit while distinguishing them.

Effects of the Invention

[0013] According to the present invention, since it is configured as described above, it is possible to suppress an increase in the capacity of engineering data and suppress a decrease in the efficiency of engineering work.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

MODE FOR CARRYING OUT THE INVENTION

[0015] Hereinafter, embodiments 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 an 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.

[0016] In FIG. 1, the facility monitoring system 1000 is provided with one primary device 20 and three secondary devices 30. However, the number of primary devices 20 and secondary devices 30 is not limited to this. Also, although devices to be controlled or monitored are connected to the secondary devices 30, their display is omitted in FIG. 1.

[0017] The engineering device 10 performs engineering processing including creation of the above-described setting data to construct 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 subordinate secondary devices 30, and setting data for the secondary device 30 for the secondary device 30 to monitor or control subordinate devices. Also, the engineering device 10 holds, as engineering data, data obtained by combining the setting data for the primary device 20 and the setting data for the secondary device 30 in a holding unit 104 (see FIG. 2).

[0018] The primary device 20 downloads, from the engineering device 10, setting data corresponding to itself among the engineering data held by the engineering device 10, and monitors or controls subordinate secondary devices 30 by operating based on the downloaded setting data.

[0019] The secondary device 30 downloads, from the engineering device 10, setting data corresponding to itself among the engineering data held by the engineering device 10, and monitors or controls subordinate devices by operating based on the downloaded setting data. The devices are installed in the facility and are composed of, for example, sensors, thermometers, motors, dampers, or power meters.

[0020] In FIG. 1, the network NW that constitutes the main part of the facility monitoring system 1000 is composed of two layers: an upper layer including the primary device 20 and a lower layer including the secondary device 30. Here, for the sake of easy understanding, an example in which the network NW is composed of two layers will be described. However, the network NW is not limited to this and may be composed of three or more layers. Further, the network NW does not necessarily have to have a hierarchical structure with an upper-lower relationship as shown in FIG. 1.

[0021] Next, a configuration example of the engineering device 10 according to Embodiment 1 will be described with reference to FIG. 2.

[0022] As shown in FIG. 2, the engineering device 10 includes a reception unit 101, a registration unit 102, a display control unit 103, a holding unit 104, and a transmission unit 105. Further, the engineering device 10 is connected to a display device 50 such as a display.

[0023] The reception unit 101 is configured to include a common data reception unit 1011, an individual data reception unit 1012, and a device information reception unit 1013.

[0024] The common data reception unit 1011 receives common data that is commonly set for two or more of the setting data set for each of a plurality of devices that monitor or control the devices installed in the facility.

[0025] Specifically, the common data reception unit 1011 is configured to include a group information reception unit 10111 and a data reception unit 10112.

[0026] The group information reception unit 10111 receives information indicating each group (hereinafter also referred to as "group information") when a plurality of devices are divided into a plurality of groups with common setting data.

[0027] The method for receiving group information by the group information reception unit 10111 is not particularly limited. For example, the group information reception unit 10111 may receive group information via a first registration screen (to be described later) displayed on the display device 50 by the first display control unit 1031.

[0028] The data reception unit 10112 receives, as common data, setting data that is commonly set for at least two or more devices belonging to each group indicated by the information received by the group information reception unit 10111.

[0029] The method for receiving common data by the data reception unit 10112 is not particularly limited. For example, the data reception unit 10112 may receive common data via a second registration screen (to be described later) displayed on the display device 50 by the second display control unit 1032.

[0030] The individual data reception unit 1012 receives individual data, which is data other than the common data among the setting data set for each of the above-mentioned plurality of devices.

[0031] Specifically, the individual data reception unit 1012 receives, as individual data, setting data set for a device that does not belong to any of the groups indicated by the information received by the group information reception unit 10111.

[0032] The device information reception unit 1013 receives information indicating at least two or more devices belonging to each group indicated by the information received by the group information reception unit 10111.

[0033] The method for receiving device information by the device information reception unit 1013 is not particularly limited. For example, the device information reception unit 1013 may receive device information via a third registration screen (to be described later) displayed on the display device 50 by the third display control unit 1033.

[0034] The registration unit 102 registers, while distinguishing them, the common data received by the common data reception unit 1011 and the individual data received by the individual data reception unit 1012 in the holding unit 104.

[0035] The display control unit 103 is configured to include a first display control unit 1031, a second display control unit 1032, and a third display control unit 1033.

[0036] The first display control unit 1031 causes the display device 50 to display a first registration screen for registering information (group information) indicating a group to which at least two or more of the plurality of devices belong. A configuration example of the first registration screen will be described later.

[0037] The second display control unit 1032 causes the display device 50 to display a second registration screen for registering setting data (common data) that is commonly set for at least two or more devices belonging to the group indicated by the group information received by the group information reception unit 10111. A configuration example of the second registration screen will be described later.

[0038] The third display control unit 1033 causes the display device 50 to display a third registration screen for registering information (device information) of at least two or more devices belonging to the group indicated by the group information received by the group information reception unit 10111. A configuration example of the third registration screen will be described later.

[0039] The holding unit 104 holds engineering data including common data and individual data registered by the registration unit 102. Note that in the holding unit 104, the common data and the individual data are held separately.

[0040] The transmission unit 105 transmits the engineering data held in the holding unit 104 to each device in the network NW via a communication unit (not shown) provided in each device in the network NW.

[0041] At this time, based on the information (device information) received by the device information receiving unit 1013, the transmission unit 105 transmits the common data received by the data receiving unit 10112 to at least two or more devices belonging to each group indicated by the information received by the group information receiving unit 10111.

[0042] Specifically, the transmission unit 105 refers to the device information received by the device information receiving unit 1013 and checks whether the destination device belongs to any group. If the destination device belongs to any group, the transmission unit 105 transmits the common data commonly set for at least two or more devices belonging to the group to the device.

[0043] Also, in the group, if there is "specific individual data" described later and the destination device is the application target of the specific individual data, the transmission unit 105 also transmits the specific individual data to the destination device.

[0044] On the other hand, if the destination device does not belong to any group, the transmission unit 105 transmits the individual data corresponding to the destination device to the device.

[0045] The functions of the receiving unit 101, the registration unit 102, the display control unit 103, and the transmission unit 105 are realized, for example, when a CPU (Central Processing Unit) (not shown) provided in the engineering device 10 executes a predetermined program expanded in a memory (not shown). Also, the holding unit 104 is composed of, for example, an HDD (Hard Disc Drive), an SSD (Solid State Drive), or a memory.

[0046] Note that in FIG. 2, the case where the holding unit 104 is provided inside the engineering device 10 is shown, but the holding unit 104 may be provided outside the engineering device 10.

[0047] Next, an operation example of the engineering device 10 according to Embodiment 1 shown in FIG. 2 will be described with reference to the flowchart of FIG. 3. In FIG. 3, an example of registering common data by the engineering device 10 will be described.

[0048] Hereinafter, for the sake of simplicity of explanation, it is assumed that the group information reception unit 10111 receives group information from an administrator or the like via the first registration screen displayed on the display device 50 by the first display control unit 1031. Also, the data reception unit 10112 receives common data from an administrator or the like via the second registration screen displayed on the display device 50 by the second display control unit 1032. Further, the device information reception unit 1013 receives device information from an administrator or the like via the third registration screen displayed on the display device 50 by the third display control unit 1033.

[0049] Also, hereinafter, it is assumed that the administrator or the like registers the secondary device 30 as a device belonging to the group indicated by the group information. As described above, the secondary device 30 often has a similar configuration and is suitable for setting common data as a device belonging to the group.

[0050] First, the first display control unit 1031 causes the display device 50 to display a first registration screen for registering information (group information) of a group to which at least two or more devices among a plurality of devices in the network NW belong (step ST301).

[0051] Next, the group information reception unit 10111 receives group information from an administrator or the like via the first registration screen displayed on the display device 50 by the first display control unit 1031 (step ST302).

[0052] An example of this first registration screen is shown in FIG. 4. An administrator or the like can register group information from the first registration screen 401 shown in FIG. 4. In the example of FIG. 4, information indicating groups such as "rest room", "locker room", and "janitor's break room" is registered as group information. An administrator or the like can register new group information by, for example, entering a desired group name in the last item (cell) of the "Name" column and performing a predetermined registration operation (for example, pressing the registration icon 4011).

[0053] Note that the "total number of individual settings" displayed on the first registration screen 401 indicates the total number of "specific individual data" existing in each group. For example, among a plurality of items constituting common data that is commonly set for devices belonging to each group, there may be a case where, for a certain item, an individual setting value is to be set for each device. In that case, an administrator or the like can cancel the common setting for that item within the group and switch to individual settings. In this way, information regarding an item that has been switched from common settings to individual settings among the plurality of items constituting the common data is additionally registered in the holding unit 104 as specific individual data separately from the common data. That is, the "total number of individual settings" indicates the total number of specific individual data in each group.

[0054] An administrator or the like can confirm the total number of individual settings displayed on the first registration screen 401, which has the following advantages. For example, since individual settings are set under each group, they may be discarded due to deletion or change of the group. Therefore, an administrator or the like can confirm the impact before deleting or changing the group by checking the total number of individual settings displayed on the first registration screen 401. Note that the engineering device 10 may hold the individual settings as they are without discarding them due to deletion or change of the group, or may output them externally as a file.

[0055] Also, for example, when the total number of individual settings is extremely large, instead of registering group information and setting common data, it may be better to adopt the conventional data setting method (the method of setting setting data for each device) in some cases, as the capacity of the entire engineering data may decrease. Therefore, an administrator or the like can also make a judgment as to whether it is appropriate to perform management in groups by checking this total number of individual settings.

[0056] Next, the second display control unit 1032 causes the display device 50 to display a second registration screen for registering setting data that is commonly set for at least two or more devices belonging to the group indicated by the information received by the group information reception unit 10111 (step ST303).

[0057] Next, the data reception unit 10112 receives, as common data, the setting data registered via the second registration screen displayed on the display device 50 by the second display control unit 1032 (step ST304).

[0058] An example of this second registration screen is shown in FIG. 5. An administrator or the like can register setting data (common data) that is commonly set for at least two or more devices belonging to the group from the second registration screen 501 shown in FIG. 5. In the example of FIG. 5, one record of common data is registered. This common data is, for example, commonly set for devices belonging to the "rest room" group. An administrator or the like can add common data in record units from the second registration screen 501 as needed and perform a predetermined registration operation (for example, pressing a registration icon (not shown)) to register new common data.

[0059] Next, the third display control unit 1033 causes the display device 50 to display a third registration screen for registering information (device information) indicating at least two or more devices belonging to the group indicated by the information of the group received by the group information reception unit 10111 (step ST305).

[0060] Next, the device information reception unit 1013 receives device information from an administrator or the like via the third registration screen displayed on the display device 50 by the third display control unit 1033 (step ST306).

[0061] An example of this third registration screen is shown in FIG. 6. An administrator or the like can register information (device information) indicating at least two or more devices belonging to a group from the third registration screen 601 shown in FIG. 6. In the example of FIG. 6, it can be seen that the secondary device 30 named "11-001 1F Rest Room" belongs to the "Rest Room" group, and the secondary device 30 named "11-002 1F Locker Room-1" belongs to the "Locker Room" group.

[0062] Also, the "number of individual settings" in FIG. 6 indicates the number of specific individual data applied to the secondary device 30. For example, in the example of FIG. 6, there are two pieces of specific individual data applied to the secondary device 30 named "11-001 1F Rest Room" belonging to the "Rest Room" group, and it can be seen that there is no specific individual data applied to the secondary device 30 named "11-002 1F Locker Room-1" belonging to the "Locker Room" group.

[0063] Note that in FIG. 6, the sum of the numbers of individual settings for the secondary devices 30 belonging to the same group is the total number of individual settings for each group shown in FIG. 4. For example, in the example of FIG. 6, the sum of the number of individual settings "2" for the secondary device 30 named "11-001 1F Rest Room" belonging to the same "Rest Room" group and the number of individual settings "5" for the secondary device 30 named "13-001 3F Rest Room" is the total number of individual settings "7" in the "Rest Room" group shown in FIG. 4.

[0064] On the other hand, the secondary device 30 named "11-003 1F Locker Room-2" does not belong to any group. In this case, common data is not applied to the secondary device 30 named "11-003 1F Locker Room-2", and the setting data (individual data) individually set for the secondary device 30 is applied as before. The administrator or the like links the secondary device 30 and the group via this third registration screen 601 and performs a predetermined registration operation (for example, pressing the registration icon 6011) to register the device information.

[0065] Next, the registration unit 102 registers the common data received by the device information reception unit 1013 in step ST306 in the holding unit 104 separately from the individual data (step ST307).

[0066] Note that the individual data reception unit 1012 receives individual data which is data other than the common data among the setting data. Then, the registration unit 102 registers the individual data received by the individual data reception unit 1012 in the holding unit 104 separately from the common data.

[0067] Thereafter, in response to an instruction from the administrator or the like, the transmission unit 105 transmits the engineering data held in the holding unit 104 to the secondary device 30 in the network NW via a communication unit (not shown) that communicates with a device other than the engineering device 10.

[0068] At this time, the transmission unit 105 refers to the above-described device information and checks whether the destination secondary device 30 belongs to any group. If the destination secondary device 30 belongs to any group, the transmission unit 105 transmits the common data corresponding to the group to the secondary device 30. Further, if there is specific individual data applied to the destination secondary device 30, the transmission unit 105 also transmits the specific individual data to the destination secondary device 30.

[0069] For example, when the device information is registered as shown in FIG. 6, the transmission unit 105 transmits the common data corresponding to the "Rest Room" group to the secondary device 30 named "11-001 1F Rest Room" belonging to the "Rest Room" group. Also, since there are two pieces of specific individual data applied to the secondary device 30, after transmitting the common data corresponding to the "Rest Room" group, the transmission unit 105 transmits the two pieces of specific individual data applied to the secondary device 30.

[0070] Similarly, for the secondary device 30 named "13-001 3F Rest Room" belonging to the "Rest Room" group, the transmission unit 105 transmits the common data corresponding to the "Rest Room" group. Also, since there are five pieces of specific individual data applied to the secondary device 30, after transmitting the common data corresponding to the "Rest Room" group, the transmission unit 105 transmits the five pieces of specific individual data applied to the secondary device 30. As a result, the same common data is transmitted to the secondary devices 30 belonging to the same group.

[0071] On the other hand, when the destination secondary device 30 does not belong to any group, the transmission unit 105 transmits the individual data corresponding to the secondary device 30 received by the individual data reception unit 1012 to the secondary device 30.

[0072] For example, when the device information is registered as shown in FIG. 6, the secondary device 30 named "11-003 1F Locker Room-2" does not belong to any group. Therefore, the transmission unit 105 transmits the individual data corresponding to the secondary device 30 received by the individual data reception unit 1012 to the secondary device 30.

[0073] In the above description, an example was described in which after receiving common data in steps ST303 to ST304, device information is received in steps ST305 to ST306. However, the engineering device 10 may receive device information first and then receive common data next, or these receptions may be performed in parallel.

[0074] As described above, in the engineering device 10, taking advantage of the tendency that the configurations of a plurality of secondary devices 30 are often the same, as shown in FIG. 7, the same setting data portion is made common (unified) on the holding unit 104 as common data. As a result, the engineering device 10 can suppress an increase in the capacity of engineering data and suppress a decrease in the efficiency of engineering work compared to the case where all setting data is held for each device. In addition, when there is a change in the common data, an administrator or the like can reflect the change in other secondary devices 30 that are expected to have the same common data setting by simply changing only the common data, leading to an improvement in maintainability.

[0075] As described above, according to the first embodiment, the engineering device 10 includes a common data reception unit 1011 that receives common data that is commonly set for two or more devices among the setting data set for each of a plurality of devices that monitor or control devices installed in the facility, an individual data reception unit 1012 that receives individual data that is data other than the common data among the setting data, and a registration unit 102 that distinguishes and registers the common data received by the common data reception unit 1011 and the individual data received by the individual data reception unit 1012 in the holding unit 104. Thereby, the engineering device 10 can suppress a decrease in the efficiency of engineering work due to an increase in the capacity of engineering data.

[0076] In addition, the common data reception unit 1011 includes a group information reception unit 10111 that receives information indicating each group when a plurality of devices are divided into a plurality of groups with common setting data, and at least two or more devices belonging to each group indicated by the information received by the group information reception unit 10111. A data reception unit 10112 that receives the setting data set in common as common data. The individual data reception unit 1012 receives the setting data set in the devices that do not belong to any of the groups indicated by the information received by the group information reception unit 10111 as individual data. Thereby, the engineering device 10 can receive common data or individual data according to whether the device belongs to a group or not.

[0077] In addition, the engineering device 10 includes a first display control unit 1031 that causes the display device 50 to display a first registration screen for registering information indicating each group. The group information reception unit 10111 receives information indicating a group via the first registration screen displayed on the display device 50 by the first display control unit 1031. Thereby, an administrator or the like can easily register information indicating a group.

[0078] In addition, the engineering device 10 includes a second display control unit 1032 that causes the display device 50 to display a second registration screen for registering common data. The data reception unit 10112 receives the setting data registered via the second registration screen displayed on the display device 50 by the second display control unit 1032 as common data. Thereby, an administrator or the like can easily register common data.

[0079] In addition, the engineering device 10 includes a device information reception unit 1013 that receives information indicating at least two or more devices belonging to each group indicated by the information received by the group information reception unit 10111, and based on the information received by the device information reception unit 1013, a transmission unit 105 that transmits the common data received by the data reception unit 10112 to at least two or more devices belonging to each group indicated by the information received by the group information reception unit 10111. Thereby, the engineering device 10 can appropriately transmit common data to the devices belonging to the group.

[0080] In addition, the engineering device 10 includes a third display control unit 1033 that causes the display device 50 to display a third registration screen for registering information indicating at least two or more devices belonging to each group indicated by the information received by the group information reception unit 10111. The device information reception unit 1013 receives information indicating at least two or more devices belonging to each group via the third registration screen displayed on the display device 50 by the third display control unit 1033. Thereby, an administrator or the like can easily register information indicating at least two or more devices belonging to the group.

[0081] Embodiment 2. In Embodiment 1, an example of registering, as common data, setting data that is commonly set for two or more devices among the setting data set for each device in the network NW has been described. In Embodiment 2, an example of registering the "specific individual data" described in Embodiment 1 will be described.

[0082] For example, among a plurality of items constituting common data that is commonly set for devices belonging to each group, there may be a case where, for a certain item, individual setting values are to be set for each device. In such a case, an administrator or the like can cancel the common setting for that item within the group and switch to individual settings. In this way, among the plurality of items constituting the common data, information regarding an item that has been switched from common settings to individual settings is additionally registered in the holding unit as specific individual data separately from the common data.

[0083] FIG. 8 is a diagram showing a configuration example of the engineering device 10b according to Embodiment 2. The engineering device 10b according to Embodiment 2 has an additional cancellation instruction reception unit 1014 with respect to the engineering device 10 according to Embodiment 1, and the registration unit 102 has been changed to a registration unit 102b. Since other configurations of the engineering device 10b are the same as those of the engineering device 10 according to Embodiment 1, the same reference numerals are given and the description thereof is omitted.

[0084] The cancellation instruction reception unit 1014 receives a cancellation instruction to cancel the common setting (registration as common data) in units of items constituting the setting data registered in the holding unit 104 as common data.

[0085] The method of receiving the cancellation instruction by the cancellation instruction reception unit 1014 is not particularly limited. For example, the cancellation instruction reception unit 1014 may receive the cancellation instruction via the second registration screen displayed on the display device 50 by the second display control unit 1032.

[0086] When a cancellation instruction is received by the cancellation instruction reception unit 1014, the registration unit 102b additionally registers information regarding an item whose common setting has been cancelled by the cancellation instruction in the holding unit 104 as specific individual data.

[0087] At this time, the registration unit 102b adds and registers, as specific individual data, data in which a setting value individually set for an item whose common setting has been canceled by a cancellation instruction is associated with information indicating a device to which the setting value is applied, in the holding unit 104.

[0088] Next, an operation example of the engineering device 10b according to Embodiment 2 shown in FIG. 8 will be described with reference to the flowchart of FIG. 9. In the following, for the sake of simplicity of explanation, it is assumed that the cancellation instruction reception unit 1014 receives a cancellation instruction from an administrator or the like via the second registration screen displayed on the display device 50 by the second display control unit 1032.

[0089] First, the second display control unit 1032 causes the display device 50 to display the second registration screen in response to an instruction from an administrator or the like (step ST901).

[0090] Next, the cancellation instruction reception unit 1014 receives a cancellation instruction via the second registration screen displayed on the display device 50 by the second display control unit 1032 (step ST902).

[0091] An example of this second registration screen is shown in FIG. 10. FIG. 10 shows an enlarged part of the second registration screen 501. In FIG. 10, one record of common data is registered for the "rest room" group. Also, an operation area 5011 is provided at the right end of the second registration screen 501, and information indicating the affiliated group and a cancellation icon 5012 are displayed in this operation area 5011. In the example of FIG. 10, the set value of the "heating and cooling setting deviation" item, which is one of the items constituting the common data, is "2°C".

[0092] Here, when an administrator or the like wants to change the set value of the "heating and cooling setting deviation" item to "4°C" for a specific secondary device 30 within the "rest room" group, while the "heating and cooling setting deviation" item is selected, for example, the cancel icon 5012 is pressed. Then, the common setting for the "heating and cooling setting deviation" item is canceled, and it becomes possible to set "4°C" as an individual set value. At this time, in the operation area 5011, the display of the belonging group is changed from "rest room" to "individual", and for the "heating and cooling setting deviation" item, it is changed from a common setting to an individual setting. Among the common data, for items other than the "heating and cooling setting deviation" item, the common setting is maintained.

[0093] Next, when the registration unit 102b receives a cancellation instruction from the cancellation instruction reception unit 1014, it additionally registers, as specific individual data, information regarding the item whose common setting has been canceled by the cancellation instruction in the holding unit 104 (step ST903).

[0094] At this time, as shown in FIG. 11, the registration unit 102b additionally registers in the holding unit 104 data that associates, as specific individual data, the set value individually set for the item whose common setting has been canceled by the cancellation instruction with information indicating the device to which the set value is applied.

[0095] Note that the engineering device 10b may make the display color of the item changed to an individual setting different from the display colors of other items on the second registration screen 501. Thereby, an administrator or the like can easily grasp the item changed to an individual setting.

[0096] Note that, similar to the first embodiment, the transmission unit 105 transmits, in response to an instruction from an administrator or the like, the engineering data held in the holding unit 104 to the secondary device 30 within the network NW via the communication unit. At this time, for the secondary device 30 to which the additionally registered specific individual data is applied, the transmission unit 105 transmits the specific individual data in addition to the common data.

[0097] As described above, according to the second embodiment, the engineering device 10b includes a cancellation instruction reception unit 1014 that receives a cancellation instruction to cancel the common setting in units of items that make up the setting data registered in the holding unit 104 as common data. When a cancellation instruction is received by the cancellation instruction reception unit 1014, the registration unit 102b additionally registers, in the holding unit 104, information regarding the items for which the common setting has been cancelled by the cancellation instruction as specific individual data. Thereby, an administrator or the like can flexibly switch between the common setting and the individual setting in units of items that make up the setting data registered as common data.

[0098] Further, the registration unit 102b additionally registers, in the holding unit 104, data in which a set value individually set for an item for which the common setting has been cancelled by the cancellation instruction and information indicating the device to which the set value is applied are associated as specific individual data. Thereby, an administrator or the like can appropriately set the device to which the specific individual data is applied.

[0099] Embodiment 3. In Embodiment 3, as another method for suppressing an increase in the capacity of engineering data, an example of deleting the setting data set in a device belonging to a lower layer than the layer to which an arbitrary device among the devices in the network NW belongs from the engineering data will be described.

[0100] Note that in Embodiment 3, it is assumed that the network NW has a hierarchical structure and is configured by stacking a plurality of layers to which one or more devices belong. For example, as shown in FIG. 1, the network NW is configured by stacking two layers to which one or more primary devices 20 and one or more secondary devices 30 belong. However, the network NW is not limited to this, and three or more layers may be stacked.

[0101] FIG. 12 is a diagram showing a configuration example of the engineering device 10c according to Embodiment 3. The engineering device 10c according to Embodiment 3 has a deletion instruction reception unit 1015, a fourth display control unit 1034, and a deletion unit 106 added to the engineering device 10b according to Embodiment 2. Since other configurations of the engineering device 10c are the same as those of the engineering device 10b according to Embodiment 2, the same reference numerals are given and the description thereof is omitted.

[0102] The deletion instruction reception unit 1015 receives a deletion instruction from an administrator or the like. The deletion instruction is an instruction to delete the setting data set in the devices belonging to the layer lower than the layer to which an arbitrary device belongs from the engineering data held in the holding unit 104, that is, the setting data collected from the setting data set in each device in the network NW in which a plurality of layers to which one or more devices belong are stacked.

[0103] The method for receiving the deletion instruction by the deletion instruction reception unit 1015 is not particularly limited. For example, the deletion instruction reception unit 1015 may receive the deletion instruction via an editing screen described later displayed on the display device 50 by the fourth display control unit 1034.

[0104] Specifically, the fourth display control unit 1034 causes the display device 50 to display an editing screen for the setting data set in the device (for example, the primary device 20) selected by an administrator or the like (user) from among the devices in the network NW as an arbitrary device based on the engineering data held in the holding unit 104. Then, when a deletion instruction is given via the editing screen displayed on the display device 50 by an administrator or the like, the deletion instruction reception unit 1015 receives the deletion instruction.

[0105] At this time, the fourth display control unit 1034 may display an icon for receiving the deletion instruction on the editing screen. In that case, the deletion instruction reception unit 1015 receives the deletion instruction when the icon on the editing screen is operated (for example, pressed) by an administrator or the like.

[0106] Based on the deletion instruction received by the deletion instruction receiving unit 1015, the deletion unit 106 deletes the setting data set in the devices belonging to the layer lower than the layer 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.

[0107] Next, an operation example of the engineering device 10c according to Embodiment 3 shown in FIG. 12 will be described. In Embodiment 3, the engineering device 10c mainly performs a deletion process of deleting the setting data set in the devices belonging to the layer lower than the layer to which the device selected by the administrator or the like belongs from the engineering data. This deletion process will be described with reference to the flowchart of FIG. 13.

[0108] Note that hereinafter, for the sake of simplicity of explanation, it is assumed that the engineering data is previously held in the holding unit 104. Also, the administrator or the like selects the primary device 20 as an arbitrary device, and the fourth display control unit 1034 causes the display device 50 to display an edit 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 edit screen displayed on the display device 50, and the deletion instruction receiving unit 1015 receives a deletion instruction based on the fact that the icon on the edit screen displayed on the display device 50 by the fourth display control unit 1034 has been pressed by the administrator or the like.

[0109] First, the fourth display control unit 1034 causes the display device 50 to display an edit screen of the setting data set in the primary device 20 selected by the administrator or the like as an arbitrary device (step ST1301).

[0110] An example of this editing screen is shown in FIG. 14. In the editing screen 1401 shown in FIG. 14, 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 (the 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.

[0111] The editing screen 1401 shown in FIG. 14 is mainly composed of three regions (an item display region 1402, a detailed display region 1403, and an operation region 1404). Among these, in the item display region 1402, a plurality of items constituting the setting data for the primary device 20 and a plurality of items constituting the setting data for the secondary device 30 are displayed in a tree form. Here, the part where the former items are displayed is referred to as the "primary device part 14021", and the part where the latter items are displayed is referred to as the "secondary device part 14022".

[0112] When a desired item is selected from these items by an administrator or the like, the setting data for the selected item is displayed in the detailed display region 1403. Also, in the operation region 1404, various menus for editing the setting data displayed in the detailed display region 1403 are displayed. Although the description is omitted here, the editing screen 1401 may include an attribute display region for displaying more detailed information such as the attributes (properties) of the items.

[0113] Here, an administrator or the like can edit the setting data for the primary device 20 by selecting a desired item from the primary device part 14021 displayed in the item display region 1402. Similarly, an administrator or the like can edit the setting data for the secondary device 30 by selecting a desired item from the secondary device part 14022 displayed in the item display region 1402. At this time, the setting data as the editing source is the setting data included in the engineering data held in the holding unit 104.

[0114] However, for the administrator in charge of editing the setting data for the primary device 20, the setting data for the secondary device 30 is not always necessary, and there are many scenarios where the setting data for the secondary device 30 becomes unnecessary. In addition, the number of secondary devices 30 is large, and the capacity of the setting data for the secondary devices 30 tends to be large.

[0115] Therefore, as shown in FIG. 15A, an icon 14041 displayed as "Secondary Device Information Deletion" is displayed in the operation area 1404. This icon 14041 is for receiving a deletion instruction to delete the setting data set in the secondary device 30 belonging to a lower hierarchy than the primary device 20 selected by an administrator or the like as an arbitrary device from the engineering data. The administrator or the like gives the above-described deletion instruction by pressing this icon 14041.

[0116] The deletion instruction reception unit 1015 receives a deletion instruction based on the fact that the icon 14041 has been pressed by an administrator or the like (step ST1302).

[0117] Next, based on the deletion instruction received by the deletion instruction reception unit 1015, the deletion unit 106 deletes the setting data set in the secondary device 30 belonging to a lower hierarchy than the primary device 20 from the engineering data held in the holding unit 104 (step ST1303).

[0118] As a result, in the engineering device 10c, as shown in FIG. 15B, the setting data set in the secondary device 30 is deleted from the engineering data held in the holding unit 104, and the capacity of the engineering data is reduced. In addition, this eliminates the need for operations such as splitting the data when transferring the engineering data by mail or the like, improving the efficiency of the engineering work.

[0119] Note that the deletion process described above can be executed in combination with the registration of common data described in, for example, Embodiment 1 and Embodiment 2. For example, if only the registration of common data is not sufficient to reduce the capacity of engineering data, the deletion process may be performed when it is desired to further reduce the capacity of engineering data.

[0120] However, as described in Embodiment 1 and Embodiment 2, when group information is registered in the engineering device 10c and there is a secondary device 30 belonging to the group, the above deletion process may also delete the group information and device information together. Therefore, in order to avoid the disappearance of the group information and the like, it is desirable for the administrator or the like to check whether there is any registration of group information and the like for the secondary device 30 before performing the above deletion process. In addition, when there is registration of group information and the like for the secondary device 30, it is desirable for the administrator or the like to output the group information and the like to an external file or the like before performing the above deletion process.

[0121] As described above, according to Embodiment 3, the engineering device 10 includes a deletion instruction reception unit 1015 that receives a deletion instruction to delete setting data set in a device belonging to a layer lower than the layer to which an arbitrary device belongs from engineering data that is a collection of setting data set in each device in a network NW in which a plurality of layers to which one or more devices belong are stacked, and a deletion unit 106 that deletes the setting data set in the device belonging to a layer lower than the layer to which the arbitrary device belongs from the engineering data based on the deletion instruction received by the deletion instruction reception unit 1015. Thereby, in the engineering device 10c, it is possible to suppress a decrease in the efficiency of engineering work due to an increase in the capacity of engineering data.

[0122] In particular, as described above, by deleting the setting data set in the secondary device 30, which has a larger number than the primary device 20, from the engineering data held in the holding unit 104, it is possible to effectively suppress the reduction in the efficiency of the engineering work due to the increase in the capacity of the engineering data.

[0123] Note that the setting data for the secondary device 30 is rarely referred to from other functions (other devices), unlike the setting data for the primary device 20. Also, even if the setting data for the secondary device 30 is temporarily deleted from the engineering data, it can be restored as engineering data by being acquired (backed up) from the secondary device 30 and integrated into the engineering data. Against this background, the engineering device 10c can delete the setting data for the secondary device 30 from the engineering data. Restoration of the engineering data will be described in detail in Embodiment 4.

[0124] Further, the engineering device 10c includes a fourth display control unit 1034 that causes the display device 50 to display an editing screen 1401 of the setting data set in the device selected by the user from among the devices in the network NW as an arbitrary device. The deletion instruction reception unit 1015 receives a deletion instruction via the editing screen 1401 displayed on the display device 50 by the fourth display control unit 1034. Thereby, an administrator or the like can easily give a deletion instruction to the engineering device 10c.

[0125] Further, the fourth display control unit 1034 displays an icon 14041 for receiving a deletion instruction on the editing screen 1401, and the deletion instruction reception unit 1015 receives a deletion instruction when the icon 14041 on the editing screen 1401 is operated by the user. Thereby, an administrator or the like can give a deletion instruction to the engineering device 10c by a simple operation of operating the icon 14041.

[0126] Embodiment 4 In Embodiment 3, an example was described in which setting data set in each device in a network NW in which a plurality of layers to which one or more devices belong are stacked is deleted from engineering data obtained by collecting the setting data. In Embodiment 4, an example in which the engineering data from which the setting data has been deleted as described above is restored to the state before deletion will be described.

[0127] In the facility monitoring system 1000, the engineering data held in the holding unit 104 may be managed as master data. In that case, if the engineering data in the holding unit 104 is the engineering data after the above-described deletion process, since the setting data for the secondary device 30 has been deleted from this data, there is a possibility that subsequent engineering work may be hindered. Therefore, the engineering device 10d according to Embodiment 4 restores the engineering data in the holding unit 104 to the state before the deletion process in response to an instruction from an administrator or the like.

[0128] FIG. 16 is a diagram showing a configuration example of the engineering device 10d according to Embodiment 4. The engineering device 10d according to Embodiment 4 is obtained by adding an acquisition unit 107 and a data integration unit 108 to the engineering device 10c according to Embodiment 3. Since the other configurations of the engineering device 10d are the same as those of the engineering device 10c according to Embodiment 3, the same reference numerals are given and the description thereof is omitted.

[0129] The acquisition unit 107 communicates with a device in which the setting data deleted by the deletion unit 106 is set via a communication unit (not shown), and acquires the setting data from the device.

[0130] The data integration unit 108 integrates the setting data acquired by the acquisition unit 107 into the engineering data after deletion by the deletion unit 106, and restores the engineering data to the state before deletion.

[0131] Next, an operation example of the engineering device 10d according to Embodiment 4 shown in FIG. 16 will be described. In Embodiment 4, the engineering device 10d mainly performs restoration processing of engineering data. This restoration processing will be described with reference to the flowchart of FIG. 17. In the following description, it is assumed that the setting data for the secondary device 30 has been deleted from the engineering data by the deletion processing described in Embodiment 3, and an example in which the engineering device 10d restores the engineering data with the setting data for the secondary device 30 deleted to the state before deletion will be described.

[0132] First, the acquisition unit 107 communicates with the secondary device 30 in which the setting data deleted by the deletion unit 106 is set via the communication unit, and acquires (backs up) the setting data from the secondary device 30 (step ST1701).

[0133] Next, the data integration unit 108 integrates the setting data acquired by the acquisition unit 107 into the engineering data held in the holding unit 104 on which the deletion processing by the deletion unit 106 has been performed, and restores the engineering data to the state before deletion (step ST1702).

[0134] Note that the communication between the secondary device 30 by the acquisition unit 107 and the acquisition (backup) of the setting data are performed in the "connect mode" pre-mounted on the engineering device 10d.

[0135] In addition, the restoration of engineering data by the data integration unit 108 is performed in the "differential check mode" pre-installed in the engineering device 10d. In the "differential check mode", as shown in FIG. 18, the setting data 1801 acquired (backed up) from the secondary device 30 is compared with the engineering data held in the holding unit 104 to extract the difference, and the extracted difference can be incorporated into the engineering data held in the holding unit 104.

[0136] Here, since the setting data for the secondary device 30 has been deleted from the engineering data held in the holding unit 104 by the above deletion process, the setting data 1801 acquired (backed up) from the secondary device 30 is directly incorporated as the difference into the engineering data in the holding unit 104.

[0137] In the above, an example of performing the restoration process according to the flowchart of FIG. 17 has been described. However, an administrator or the like may perform the restoration process by a method other than the above. For example, in the engineering device 10d, information regarding the type of each secondary device 30 under the primary device 20 can be grasped, and information regarding the type of each secondary device 30 is registered as setting data for the primary device 20. This registration is performed in advance by an administrator or the like, for example, via the editing screen 1401 of FIG. 14 described above.

[0138] An example of the editing screen in this case is shown in FIG. 19. In the example of FIG. 19, information regarding the type of each secondary device 30 (for example, secondary device type 1901 in FIG. 19) can be registered via the editing screen 1401. This information regarding the type of each secondary device 30 is registered as setting data for the primary device 20. Therefore, it is not deleted in the above-described deletion process.

[0139] In addition, the engineering device 10d has a function of automatically generating initial values of setting data for each secondary device 30 based on the information regarding the type and the like of each secondary device 30 registered as described above.

[0140] Therefore, an administrator or the like uses this automatic generation function to once generate the setting data for each secondary device 30 with the initial values. After that, the administrator or the like connects to each secondary device 30 using the above-described "connect mode", and while actually checking the setting data set in each secondary device 30, modifies the automatically generated initial values to the actual setting data, thereby enabling restoration of the final engineering data.

[0141] Further, in the engineering device 10d, by performing the above-described restoration process, the preliminary adjustment can be performed without any trouble. The preliminary adjustment means that when the primary device 20 and the secondary device 30 exist in the network NW, before creating the setting data for the primary device 20, the setting data for the secondary device 30 is created first, and the created setting data is transmitted to and written in the secondary device 30, or the written setting data is changed.

[0142] The preliminary adjustment is performed for the purpose of, for example, checking the connection between the secondary device 30 and a device (such as a damper) connected under the secondary device 30 before the setting 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 a device such as a damper during installation work. However, depending on the progress of the installation work, the construction worker may not be able to enter the site, and it may become impossible to check the operation of the secondary device 30 installed in the attic or the like. Therefore, by the preliminary adjustment, before the setting data for the primary device 20 is created, the setting data is written to the secondary device 30 and the operation is checked.

[0143] Even when such preliminary adjustment is performed, the setting data for the secondary device 30 may be deleted from the engineering data by the deletion process described in Embodiment 3. However, in the engineering device 10d, as described above, for example, by performing a restoration process of the engineering data by a method of acquiring (backing up) the setting data from the secondary device 30, the engineering data can be restored to the state before deletion. Therefore, the engineering device 10d can perform the preliminary adjustment without any trouble.

[0144] Note that even when the preliminary adjustment is not performed, that is, when the setting data for the secondary device 30 is created after the setting data for the primary device 20 is created, in the same manner as above, by performing a restoration process by a method of acquiring (backing up) the setting data from the secondary device 30, the engineering data can be restored to the state before deletion.

[0145] As described above, according to Embodiment 4, the engineering device 10d communicates with a device in which the setting data deleted by the deletion unit 106 is set via a communication unit that communicates with each device in the network NW, and an acquisition unit 107 that acquires the setting data from the device, and a data integration unit 108 that integrates the setting data acquired by the acquisition unit 107 into the engineering data after deletion by the deletion unit 106 and restores the engineering data to the state before deletion. Thereby, the engineering device 10 can restore the engineering data for which the deletion process has been performed to the state before deletion. Also, for example, even when the setting data for the secondary device 30 created by the preliminary adjustment is deleted from the engineering data after the preliminary adjustment is performed by an administrator or the like, the deleted setting data can be integrated into the engineering data and restored to the state before deletion.

[0146] In addition, within the scope of the invention of the present application, free combinations of each embodiment, modifications of any constituent elements of each embodiment, or omissions of any constituent elements in each embodiment are possible.

Explanation of Signs

[0147] 1000 Facility Monitoring System 10, 10b, 10c, 10d Engineering Device 20, 70 Primary Device 30, 80 Secondary Device 50 Display Device 60 Engineering Device 101 Reception Unit 102, 102b Registration Unit 103 Display Control Unit 104 Holding Unit 105 Transmission Unit 106 Deletion Unit 107 Acquisition Unit 108 Data Integration Unit 401 First Registration Screen 501 Second Registration Screen 601 Third Registration Screen 610 Holding Unit 810 Setting Data 1011 Common Data Reception Unit 1012 Individual Data Reception Unit 1013 Device Information Reception Unit 1014 Release Instruction Reception Unit 1015 Deletion Instruction Reception Unit 1031 First Display Control Unit 1032 Second Display Control Unit 1033 Third Display Control Unit 1034 Fourth Display Control Unit 1401 Editing Screen 1402 Item Display Area 1403 Detail Display Area 1404 Operation Area 1801 Setting Data 1901 Secondary Device Type 2000 Facility Monitoring System 4011 Registered Icon 5011 Operation Area 5012 Release Icon 6011 Registered Icon 10111 Group Information Reception Section 10112 Data Reception Section 14021 Primary Device Portion 14022 Secondary Device Portion 14041 Icon for Deleting Secondary Device Information

Claims

1. A common data reception unit that receives common data that is commonly set for two or more devices among the setting data set for each of a plurality of devices that monitor or control devices installed in a facility; An individual data reception unit that receives individual data that is data other than the common data among the setting data; A registration unit that registers the common data received by the common data reception unit and the individual data received by the individual data reception unit in a holding unit separately; A cancellation instruction reception unit that receives a cancellation instruction to cancel a common setting in units of items constituting the common data registered in the holding unit; comprising The registration unit When a cancellation instruction is received by the cancellation instruction reception unit, information regarding an item whose common setting has been cancelled by the cancellation instruction is added and registered in the holding unit as specific individual data An engineering device characterized by the above.

2. The registration unit As the specific individual data, data in which a set value individually set for an item whose common setting has been cancelled by the cancellation instruction and information indicating a device to which the set value is applied are associated is added and registered in the holding unit The engineering device according to claim 1, characterized by the above.

3. Among the setting data set for each of a plurality of devices that monitor or control devices installed in a facility, a common data reception unit that receives common data that is commonly set for two or more devices; An individual data reception unit that receives individual data that is data other than the common data among the setting data; A registration unit that registers the common data received by the common data reception unit and the individual data received by the individual data reception unit in a holding unit separately; A network is configured in which multiple layers to which one or more devices belong are stacked by the plurality of devices, and from engineering data that summarizes the setting data set for each of the devices, a deletion instruction to delete the setting data set for a device belonging to a layer lower than the layer to which an arbitrary device among the devices belongs is received. A deletion instruction receiving unit; Based on the deletion instruction received by the deletion instruction receiving unit, a deletion unit that deletes the setting data set for a device belonging to a layer lower than the layer to which the arbitrary device belongs from the engineering data; An engineering device comprising:

4. An engineering method by an engineering device, comprising: A step in which a common data receiving unit receives common data that is commonly set for two or more of the setting data set for each of a plurality of devices that monitor or control equipment installed in a facility; A step in which an individual data receiving unit receives individual data that is data other than the common data among the setting data; A step in which a registration unit registers the common data received by the common data receiving unit and the individual data received by the individual data receiving unit in a holding unit separately; A step in which a cancellation instruction receiving unit receives a cancellation instruction to cancel a common setting in units of items constituting the common data registered in the holding unit; When the cancellation instruction is received by the cancellation instruction receiving unit, a step in which the registration unit additionally registers information regarding the item for which the common setting has been cancelled by the cancellation instruction as specific individual data in the holding unit; An engineering method having:

5. An engineering method by an engineering device, comprising: A step in which a common data reception unit receives common data that is commonly set for two or more of a plurality of devices that monitor or control devices installed in a facility, among the setting data set for each of the plurality of devices; A step in which an individual data reception unit receives individual data that is data other than the common data among the setting data; A step in which a registration unit registers the common data received by the common data reception unit and the individual data received by the individual data reception unit in a holding unit separately; A network is configured in which a plurality of hierarchies to which one or more devices belong are stacked by the plurality of devices, and a deletion instruction reception unit deletes the setting data set for a device belonging to a hierarchy lower than the hierarchy to which an arbitrary device among the devices belongs, from the engineering data obtained by summarizing the setting data set for each of the devices. A step in which a deletion unit deletes the setting data set for a device belonging to a hierarchy lower than the hierarchy to which the arbitrary device belongs, from the engineering data, based on the deletion instruction received by the deletion instruction reception unit; An engineering method having the above.

Images