JP7645764B2 - 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., an integrated controller, a primary device, a secondary device, etc.) 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 constructs a facility monitoring system by having each device download (receive) the created configuration data. 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 an integrated controller, a primary device installed at the same hierarchical level as the integrated controller, a secondary device connected under the primary device, and equipment connected under the secondary device. The integrated controller monitors the status of the primary device by operating based on configuration data downloaded from the engineering equipment. The primary device monitors or controls the secondary devices under it by operating based on configuration data downloaded from the engineering equipment. The secondary device monitors or controls the equipment under it by operating based on configuration data downloaded from the engineering equipment.

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. Then, the administrator or the like performs engineering work by creating setting data using the setting screen. Then, 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, hereafter referred to as "DB") as engineering data.

JP 2020-160909 A

In general, facility monitoring systems have a large number of secondary devices, which means that the amount of configuration data for the secondary devices is large, and therefore the amount of engineering data is also large. On the other hand, multiple managers (engineers) may be involved in creating and modifying the engineering data, and if the amount of engineering data is large, it may cause problems in transferring the engineering data between managers, reducing the efficiency of engineering work.

Therefore, in facility monitoring systems, the DB constructed in the storage unit of the engineering device to store the engineering data may be divided into multiple databases in advance, and the engineering data may be divided and registered in these multiple DBs.

Here, the unit of division is, for example, a division for managing the devices (integrated controller, primary device, and secondary device) for which the setting data is to be set. This division is, for example, a division determined based on which floor of the facility the device is installed on. For example, the setting data for devices installed on higher floors of the facility is registered in a DB that is divided in advance to correspond to the higher floors, and the setting data for devices installed on lower floors of the facility is registered in a DB that is divided in advance to correspond to the lower floors. This allows the engineering device to manage the engineering data in smaller parts, making management easier than when the engineering data is managed collectively. It also makes it easier to transfer data between managers, which is expected to prevent a decrease in the efficiency of engineering work.

However, when managing engineering data that is divided and stored in this way, administrators and the like must sometimes use engineering equipment to actually access each DB and check whether or not setting data is registered in each DB in order to determine whether or not setting data is registered. This type of checking work is cumbersome for administrators and the like when managing engineering data, and improvements were needed.

This invention was made to solve the above problems, and aims to provide an engineering device that can manage engineering data stored in separate parts more easily than ever before.

The engineering device according to the present invention is characterized by comprising: a first generation unit that generates information indicating whether or not setting data to be set for a device for monitoring or controlling equipment installed in a facility is registered for each of a plurality of databases divided into predetermined first divisions; a first display control unit that causes a display device to display the information generated by the first generation unit; a reception unit that receives a management instruction for managing the setting data via the information displayed on the display device; and a management unit that manages the setting data based on the management instruction received by the reception unit.

With the above-mentioned configuration, this invention makes it easier than ever to manage engineering data that is stored in separate parts.

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. FIG. 2 is a diagram showing an example of DB construction in the first embodiment; 4 is a flowchart showing an example of the operation of the engineering device according to the first embodiment; FIG. 2 is a diagram showing an example of a matrix in the first embodiment; 1A and 1B are diagrams showing examples of new matrices in embodiment 1, where (a) is an example of a matrix newly generated when division output is performed, and (b) is an example of a matrix newly generated when partial copy output is performed. FIG. 13 is a diagram illustrating a configuration example of an engineering device according to a second embodiment. FIG. 13 is a diagram showing an example of DB construction in the second embodiment; FIG. 13 is a diagram showing an example of the configuration of a basic DB in the second embodiment; FIG. 11 is a diagram illustrating an example of a configuration of a management DB in the second embodiment. FIG. 11 is a diagram showing an example of a matrix in the second embodiment. 11A and 11B are diagrams showing examples of new matrices in embodiment 2, where (a) is an example of a matrix newly generated when partial output is performed, and (b) is an example of a matrix newly generated when partial copy output is performed. FIG. 13 is a diagram showing another example of the matrix in the second embodiment. FIG. 11 is a diagram for explaining the import of setting data in the second embodiment. 11A and 11B are diagrams showing examples of a display screen in which devices with the same physical classification are displayed in a tree structure in embodiment 2, where (a) is an example when an instruction is given to display information about devices with a physical classification of "high rise", and (b) is an example when an instruction is given to display information about devices with physical classifications of "high rise", "middle rise", and "low rise".

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, an integrated controller 20, a primary device 30, and a secondary device 40. The engineering device 10, the integrated controller 20, the primary device 30, and the secondary device 40 are connected via a network.

In FIG. 1, the facility monitoring system 1000 is provided with one integrated controller 20, one primary device 30, and three secondary devices 40, but the number of integrated controllers 20, primary devices 30, and secondary devices 40 is not limited to this. Furthermore, the integrated controller 20 is not a required component and may be omitted. Furthermore, the secondary devices 40 are connected to devices that are to be controlled or monitored, but the display of these devices is omitted 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 integrated controller 20, which allows the integrated controller 20 to monitor the state of the primary device 30, setting data for the primary device 30, which allows the primary device 30 to monitor or control the secondary device 40 under it, and setting data for the secondary device 40, which allows the secondary device 40 to monitor or control the equipment under it. In addition, the engineering device 10 stores data that combines the setting data for the integrated controller 20, the setting data for the primary device 30, and the setting data for the secondary device 40 as engineering data in the storage unit 105 (see FIG. 2).

The integrated controller 20 downloads from the engineering device 10 the configuration data corresponding to its own device among the engineering data held by the engineering device 10, and operates based on the downloaded configuration data to monitor the status of the primary device 30. The integrated controller 20 displays information indicating the status of the primary device 30 on a display device (not shown), such as a display, so that an administrator or the like can grasp the status of the primary device 30. The integrated controller 20 and the primary device 30 are installed at the same hierarchical level.

The primary 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 secondary device 40 under its control.

The secondary device 40 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.

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 first generating unit 101, a first display control unit 102, a receiving unit 103, a management unit 104, and a storage unit 105. The engineering device 10 is also connected to a display device 50 such as a display.

The storage unit 105 stores various information used by the engineering device 10. For example, the storage unit 105 stores engineering data that is a compilation of the setting data set in the integrated controller 20, the setting data set in the primary device 30, and the setting data set in the secondary device 40.

In addition, in the holding unit 105, a plurality of DBs are constructed, which are divided into physical sections. Here, the physical section is, for example, a section for managing devices such as the integrated controller 20, the primary device 30, and the secondary device 40 (hereinafter, referred to as the "device management section"). As an example, when the physical section is the "device management section", the physical section is a section determined based on which floor of the facility the integrated controller 20, the primary device 30, and the secondary device 40 are installed in, and for example, as shown in FIG. 3, four layers are set: a common layer, a high layer, a middle layer, and a low layer. In addition, in the holding unit 105, DBs corresponding to these four layers (a common layer DB, a high layer DB, a middle layer DB, and a low layer DB) are constructed. In addition, the high layer, the middle layer, and the low layer are independent layers and correspond to lower layers. The common layer corresponds to an upper layer that spans at least some of the lower layers (the high layer, the middle layer, and the low layer).

For example, the high-level DB stores setting data for the integrated controller 20, primary device 30, and secondary device 40 installed on the high level of the facility. The mid-level DB stores setting data for the integrated controller 20, primary device 30, and secondary device 40 installed on the mid-level of the facility. The low-level DB stores setting data for the integrated controller 20, primary device 30, and secondary device 40 installed on the low level of the facility. The common-level DB stores setting data that is commonly registered in at least some of the high-level DB, mid-level DB, and low-level DB.

In the above, an example was described in which the physical division is determined based on the floor of the facility on which the device is installed, but the physical division is not limited to this. For example, when the devices are installed on the same floor, the division may be determined based on the direction in which the device is installed (north, south, etc.), or it may be an arbitrary division determined for managing the device, independent of where in the facility the device is installed.

The storage unit 105 is composed of, for example, a hard disk drive (HDD), a solid state drive (SSD), or a memory. In addition, while FIG. 2 shows a case where the storage unit 105 is provided inside the engineering device 10, the storage unit 105 may be provided outside the engineering device 10.

The first generating unit 101 refers to each of the multiple DBs constructed in the holding unit 105 by dividing them into predetermined physical sections as described above, and generates information indicating whether or not the setting data to be set in the integrated controller 20, the primary device 30, and the secondary device 40 is registered in these DBs. The information generated here is, for example, a matrix or a character string indicating whether or not the setting data is registered in each of the multiple DBs constructed in the holding unit 105.

The first display control unit 102 causes the information generated by the first generation unit 101 to be displayed on the display device 50.

The reception unit 103 receives management instructions for managing the setting data from an administrator or the like via the information displayed on the display device 50. Here, the "management instructions" include, for example, a display instruction for displaying the setting data on the display device 50, or an output instruction for outputting the setting data.

The management unit 104 manages the setting data based on the management instruction received by the reception unit 103. For example, if the management instruction received by the reception unit 103 is a display instruction, the management unit 104 causes the display device 50 to display the setting data. Furthermore, if the management instruction received by the reception unit 103 is an output instruction, the management unit 104 outputs the setting data.

When outputting setting data, the management unit 104 either deletes the setting data to be output from the DB from which it was registered, or copies and outputs the setting data to be output without deleting it from the DB from which it was registered, in accordance with instructions from the administrator, etc. In the following, for ease of explanation, the former output is referred to as "split output" and the latter output as "partial copy output."

When the management unit 104 outputs setting data, the first generation unit 101 regenerates information that reflects that the setting data has been output. In addition, the first display control unit 102 causes the display device 50 to display the information regenerated by the first generation unit 101.

The functions of the first generation unit 101, the first display control unit 102, the reception unit 103, and the management unit 104 are realized, for example, by a central processing unit (CPU) (not shown) provided in the engineering device 10, which executes a predetermined program deployed in a memory (not shown).

For simplicity's sake, it is assumed that predetermined setting data is registered in advance in each of the DBs illustrated in FIG. 3. However, the engineering device 10 may also be provided with a registration unit that registers setting data created by an administrator or the like in the corresponding DB according to the physical classification.

Next, an example of the operation of the engineering device 10 according to the first embodiment shown in FIG. 2 will be described with reference to the flowchart in FIG. 4. In the following, for simplicity, an example will be described in which the physical division is the management division of the device, and this physical division (the management division of the device) is a division determined based on the hierarchy of the facility in which the device is installed. In addition, an example will be described in which each DB illustrated in FIG. 3 is constructed in the holding unit 105 based on this physical division.

An example will be described in which the first generating unit 101 generates a matrix as information indicating whether or not setting data is registered for each of the multiple DBs constructed in the holding unit 105. An example will be described in which the first generating unit 101 generates a matrix for the DBs (high-tier DB, mid-tier DB, and low-tier DB) excluding the common-tier DB among the DBs illustrated in FIG. 3. An example will be described in which the receiving unit 103 receives an instruction to output setting data as a management instruction via the matrix.

First, the first generation unit 101 refers to each of the high-tier DB, mid-tier DB, and low-tier DB that are divided by physical division and constructed in the storage unit 105, and generates a matrix indicating whether or not setting data is registered for these DBs (step ST401).

Here, an example of a matrix generated by the first generation unit 101 is shown in FIG. 5. As shown in FIG. 5, the matrix indicates whether or not setting data is registered for the high-tier DB, mid-tier DB, and low-tier DB constructed in the storage unit 105. In FIG. 5, a display value of "1" is displayed for DBs in which setting data is registered. On the other hand, for DBs in which setting data is not registered, a display value of "0", for example, is displayed. In this way, by the first generation unit 101 generating a matrix, an administrator or the like can easily see at a glance whether or not setting data is registered in each divided DB.

Note that the matrix shown in FIG. 5 is merely an example, and the matrix configuration and display values are not limited to those in FIG. 5. For example, the matrix may have other configurations and display values as long as it can indicate whether or not setting data is registered for the high-tier DB, mid-tier DB, and low-tier DB.

Next, the first display control unit 102 causes the display device 50 to display the matrix generated by the first generation unit 101 (step ST402).

Next, the reception unit 103 receives an output instruction to output desired setting data from the administrator or the like via the matrix displayed on the display device 50 (step ST403). For example, when the administrator or the like selects the "high floor" item in the matrix displayed on the display device 50, the reception unit 103 receives an output instruction for setting data registered in the high floor DB. Also, when the administrator or the like selects the "low floor" item in the matrix displayed on the display device 50, the reception unit 103 receives an output instruction for setting data registered in the low floor DB. At this time, the reception unit 103 also receives an instruction from the administrator or the like as to whether to perform "split output" in which the setting data to be output is deleted from the DB from which it was registered, or "partial copy output" in which the setting data to be output is copied and output without being deleted from the DB from which it was registered. The reception unit 103 is set to receive "split output" in the initial setting (default), and may be set so that the administrator or the like can change it to "partial copy output" if necessary.

Next, the management unit 104 outputs the setting data based on the output instruction received by the reception unit 103 (step ST404). At that time, the management unit 104 performs "split output" or "partial copy output" according to the instruction of the administrator, etc.

Next, the first generating unit 101 regenerates a matrix that reflects the fact that the setting data has been output by the management unit 104 (step ST405). The first display control unit 102 also causes the display device 50 to display the matrix regenerated by the first generating unit 101 (step ST406).

Here, an example of a matrix regenerated by the first generation unit 101 is shown in FIG. 6. FIG. 6(a) is an example of a matrix regenerated when the setting data to be output is setting data of a low-level DB and the management unit 104 performs divided output, and FIG. 6(b) is an example of a matrix regenerated when the setting data to be output is setting data of a low-level DB and the management unit 104 performs partial copy output.

When the management unit 104 performs split output of the setting data of the low-level DB, the regenerated matrix has the display value of the low-level DB set to "0", as shown in FIG. 6(a). This indicates that the setting data set in the low-level DB has been deleted by the split output.

On the other hand, when the management unit 104 performs a partial copy output of the setting data of the low-layer DB, the regenerated matrix has the display value of the low-layer DB still set to "1", as shown in FIG. 6(b). This indicates that the setting data that was set in the low-layer DB due to the partial copy output remains as it is, without being deleted from the low-layer DB.

In this way, with split output, the output setting data is not left in the engineering device 10 (the DB from which it was registered), so the division of labor as to which administrator will be responsible for editing the output setting data, etc., is clear. In addition, after output, the sum of the data sizes of the setting data left in the engineering device 10 and the output setting data is approximately equal to the sum of the setting data held by the engineering device 10 before output. Furthermore, since the data size of the output setting data is smaller than the sum of the setting data held by the engineering device 10 before output, the output setting data is easier to handle and can also be easily transferred between administrators via email, etc.

In addition, the engineering device 10 can also import setting data from other engineering devices. In this case, if the setting data to be imported has already been output in parts, the setting data can be imported in a single batch on a DB basis (file basis) from the other engineering device, so that the import process can be completed quickly and work efficiency is improved.

On the other hand, with partial copy output, even after the setting data is output, the data size of the setting data remaining in the engineering device 10 remains the same as before the output. Also, when importing setting data from another engineering device, since the output setting data remains in the engineering device 10, it is necessary to import only the difference between the data to be imported and the data remaining in the engineering device 10, which takes more processing time than importing all at once on a DB basis (file basis). However, partial copy output is effective when you want to hold the setting data to be output as a master on the engineering device 10. Even in this case, as with divided output, the output setting data is easy to handle, and it is also easy to transfer between administrators by email, etc.

In the above example, when partial copy output is performed, the matrix regenerated by the first generation unit 101 does not change from the matrix generated initially. Therefore, when partial copy output is performed in step ST404, the generation and display of the matrix again in steps ST405 and ST406 may be omitted. In the above example, a case was described in which the management instruction is an output instruction, but when the management instruction is a display instruction, there is no change to the matrix, and therefore steps ST405 and ST406 may be omitted.

In the above example, the first generation unit 101 generates a matrix for the DBs exemplified in FIG. 3 (high-tier DB, mid-tier DB, and low-tier DB) excluding the common layer DB. However, the same processing as above can be performed even when generating a matrix including the common layer DB.

As described above, according to the first embodiment, the engineering device 10 includes a first generating unit 101 that generates information indicating whether or not setting data set for a device for monitoring or controlling equipment installed in a facility is registered for each of a plurality of DBs divided into a first predetermined division, a first display control unit 102 that displays the information generated by the first generating unit 101 on the display device 50, a receiving unit 103 that receives a management instruction for managing the setting data via the information displayed on the display device 50, and a management unit 104 that manages the setting data based on the management instruction received by the receiving unit 103. This allows the administrator to easily check whether or not setting data is registered in each divided DB, making it easier to manage the divided and stored engineering data than ever before.

The reception unit 103 also receives an instruction to output the setting data as a management instruction via the information displayed on the display device 50, and the management unit 104 outputs the setting data from the DB where the data was registered based on the output instruction received by the reception unit 103. This allows the administrator, etc., to output the desired setting data more easily than ever before.

Furthermore, when performing output, the management unit 104 either deletes the setting data to be output from the DB from which it was registered, or copies and outputs the setting data to be output without deleting it from the DB from which it was registered. As a result, in divided output, the division of labor regarding which administrator will be responsible for editing the output setting data, etc., is made clear, and the output setting data can also be imported from outside in a batch on a DB basis (file basis), improving work efficiency. Furthermore, in either output case, the output setting data is easy to handle, and can also be easily transferred between administrators via email, etc.

When the management unit 104 outputs setting data, the first generation unit 101 generates information again, and the first display control unit 102 causes the display device 50 to display the information generated again by the first generation unit 101. This allows the administrator or the like to easily understand that the setting data has been output.

The first generation unit also generates a matrix as information. This allows the administrator or the like to easily see at a glance whether or not setting data is registered in each of the divided DBs.

Embodiment 2.
In the first embodiment, an example was described in which the DBs constructed in the holding unit 105 are divided into physical partitions in advance. In contrast, in the second embodiment, an example is described in which each of the DBs constructed for each physical partition is further divided into partitions different from the physical partitions.

Figure 7 is a diagram showing an example configuration of an engineering device 10b according to embodiment 2. In the engineering device 10b according to embodiment 2, the holding unit 105 is changed to a holding unit 105b, and a second generating unit 106 and a second display control unit 107 are added to the engineering device 10 according to embodiment 1. The other configurations of the engineering device 10b are the same as those of the engineering device 10 according to embodiment 1, so the same reference numerals are used and the description thereof is omitted.

First, an example of the configuration of the storage unit 105b is shown in FIG. 8. As shown in FIG. 8, in the storage unit 105b, each of the DBs (high layer DB, mid layer DB, and low layer DB) except for the common layer DB, which is divided into physical divisions, is constructed by further dividing them into divisions (functional divisions in this case) different from the physical divisions. Here, the functional divisions are divisions that are determined in advance based on, for example, the function (type) of the setting data, and for example, as shown in FIG. 8, four types are set: "data for integrated controller", "data for device", "data for graphics", and "program for device".

The integrated controller data is setting data for the integrated controller 20. The device data is setting data for the primary device 30 and the secondary device 40. The graphics data is setting data for the integrated controller 20, and is particularly data for generating a display screen when the integrated controller 20 displays the status of the primary device 30 on a display device. The device program is a program that is installed in the primary device 30 and the secondary device 40. Note that the four types of functional divisions described here are merely examples, and divisions other than those described above may be set.

The "basic data" shown in FIG. 8 is data that includes specific key items for associating multiple DBs with the same physical division but different functional divisions. The basic data is registered in the basic DBs (reference numbers 65, 75, and 85 in FIG. 8). The "management data" shown in FIG. 8 is data that includes specific key items for associating basic DBs with different physical divisions.

For example, DB61 stores setting data whose physical classification is "high floor" and whose functional classification is "data for integrated controller", i.e., setting data set for an integrated controller 20 installed on a high floor of a facility. DB62 stores setting data whose physical classification is "high floor" and whose functional classification is "data for device", i.e., setting data set for a primary device 30 and a secondary device 40 installed on a high floor of a facility.

DB63 also stores setting data with a physical classification of "high floor" and a functional classification of "graphics data", i.e., setting data set for the integrated controller 20 installed on the high floor of the facility, and particularly data for generating a display screen when the integrated controller 20 displays the status of the primary device 30 on a display device. DB64 also stores setting data with a physical classification of "high floor" and a functional classification of "device program", i.e., programs to be installed on the primary device 30 and secondary device 40 installed on the high floor of the facility.

DB65 is a basic DB, and basic data including a specific key item for relating DB61 to DB64, which are in the "high floor" physical classification, to each other is registered in DB65. The specific key item is, for example, device information (such as a device ID), and in this case, DB61 to DB64 are related to each other using the device information as a key item.

Similarly, DB71-74 and DB81-84 also have configuration data registered that is specified by a combination of physical and functional classifications. In addition, basic DB75 has data registered therein that includes specific key items for associating DB71-DB74, which have a "middle tier" physical classification, with one another, and basic DB85 has data registered therein that includes specific key items for associating DB81-DB84, which have a "low tier" physical classification, with one another.

Furthermore, DB90 is a management DB, in which management data including a predetermined key item for relating basic DBs 65, 75, and 85 to each other is registered. The predetermined key item is, for example, device information (such as a device ID), and in this case, basic DBs 65, 75, and 85 are related to each other using device information as a key item. As a result, all DBs constructed in holding unit 105b are related to each other using device information as a key item. Configuration examples of basic DBs 65, 75, and 85, and management DB 90 will be described later.

The second generation unit 106 generates data showing a display screen that displays devices with the same physical classification in a tree structure based on the management data registered in the management DB 90.

The second display control unit 107 causes the display device 50 to display a display screen indicated by the data generated by the second generation unit 106. A display example of the display screen in this case will be described later. Note that the second generation unit 106 and the second display control unit 107 are not essential components and may be omitted.

Next, configuration examples of basic DBs 65, 75, and 85, and management DB 90 will be described. Note that since the configuration examples of the basic DBs are all similar, the configuration example of basic DB 65 will be described here as a representative.

Figure 9 shows an example of the configuration of basic DB 65. In basic DB 65, data including a specific key item for relating DBs with the same physical division but different functional divisions is registered as basic data. For simplicity of explanation, it is assumed here that the specific key item is device information ("KEY_NO" in Figure 9).

In the basic DB 65 of FIG. 9, "DEVICE_TYPE" indicates the type of device, with "1" indicating the integrated controller, "2" indicating the primary device 30, and "3" indicating the secondary device 40. Also, "PARENT_KEY" indicates the primary device that is the parent of the secondary device, and "DEVICE_MODEL" indicates, for example, the model number of the device.

For example, in FIG. 9, a device with a "KEY_NO" of "20" is the integrated controller, devices with "KEY_NO"s of "1" to "4", "10", "12", and "14" are primary devices, and devices with "KEY_NO"s of "21" and "25" to "31" are secondary devices. Also, the primary device that is the parent of the secondary device with a "KEY_NO" of "21" is the device with a "KEY_NO" of "14".

The setting data registered in DBs 61 to 64 also contains device information ("KEY_NO"). DBs 61 to 65 are associated with each other using this device information as a key item. Therefore, by referencing the basic data registered in basic DB 65, it is possible to know in which DB the setting data set for a device with a physical classification of "high floor" is registered.

Figure 10 shows an example of the configuration of management DB 90. In management DB 90, data including a specific key item for relating basic DBs 65, 75, and 85, which have different physical divisions, to each other is registered as management data. For simplicity of explanation, it is assumed here that the specific key item is device information ("KEY_NO" in Figure 10).

In the management DB 90 in FIG. 10, "ORG_NO" indicates a serial number. Also, "DB_ID" indicates the physical division, with "1" indicating the high floor, "2" the middle floor, and "3" the low floor. Also, when a new device is added, "NEW_NO" displays the added device information.

The "KEY_NO" shown in FIG. 10 corresponds to the "KEY_NO" in the basic data registered in basic DBs 65, 75, and 85. Therefore, for example, it can be determined that a device with a "KEY_NO" of "28" is a secondary device with a physical classification of "middle tier," and that the parent primary device is a device with a "KEY_NO" of "10."

In this way, in the engineering device 10b, for example, the management DB 90 is associated with the basic DBs 65, 75, and 85 using the device information contained in the management data as a key item, and the basic DBs 65, 75, and 85 are further associated with DBs 61-64, DBs 71-74, and DBs 81-84, respectively, using the device information contained in the basic data as a key item. As a result, in the engineering device 10b, the management unit 104 can individually or collectively manage the setting data registered in multiple DBs divided by physical and functional divisions based on the management data registered in the management DB 90 and the basic data registered in the basic DBs 65, 75, and 85.

Note that an example of operation of the engineering device 10b according to the second embodiment is substantially the same as the example of operation of the engineering device 10 according to the first embodiment described with reference to the flowchart of FIG. 4, and only the configuration of the matrix generated by the first generating unit 101 is different. Therefore, in the following, a detailed explanation of the example of operation of the engineering device 10b according to the second embodiment will be omitted, and the configuration of the matrix generated by the first generating unit 101 will be explained in detail.

In the second embodiment, an example of a matrix generated by the first generating unit 101 is shown in FIG. 11. As shown in FIG. 11, the matrix indicates whether or not setting data is registered for DB61-64, DB71-74, and DB81-84 constructed in the holding unit 105b. In FIG. 11, a display value of "1" is displayed for DBs in which setting data is registered. On the other hand, a display value of "0" is displayed for DBs in which setting data is not registered. The matrix shown in FIG. 11 also indicates whether or not management data is registered for the management DB 90. If this management data is registered in the management DB 90, a display value of "1" is displayed, and if it is not registered in the management DB 90, a display value of "0" is displayed.

Note that the matrix shown in FIG. 11 is merely an example, and the matrix configuration and display values are not limited to those in FIG. 11. For example, the matrix may have a different configuration and display values as long as it can indicate whether or not setting data is registered in DBs 61-64, DBs 71-74, and DBs 81-84, and whether or not management data is registered in management DB 90.

Also, in the second embodiment, the reception unit 103 receives an output instruction to output desired setting data or management data from the administrator or the like via the matrix displayed on the display device 50. For example, when the administrator or the like selects the items "high layer" and "program for device" in the matrix displayed on the display device 50, the reception unit 103 receives an output instruction for setting data registered in DB 64 specified by "high layer" and "program for device". Also, when the administrator or the like selects the items "low layer" and "data for device" in the matrix displayed on the display device 50, the reception unit 103 receives an output instruction for setting data registered in DB 82 specified by "low layer" and "data for device". At this time, the reception unit 103 also receives an instruction from the administrator or the like as to whether to perform "split output" in which the setting data to be output is deleted from the DB from which it was registered, or to perform "partial copy output" in which the setting data to be output is copied and output without being deleted from the DB from which it was registered.

Then, the management unit 104 performs divided output or partial copy output of the setting data or management data based on the output instruction received by the reception unit 103. Next, the first generation unit 101 regenerates a matrix that reflects that the setting data has been output by the management unit 104, and the first display control unit 102 causes the display device 50 to display the matrix regenerated by the first generation unit 101.

Here, an example of a matrix regenerated by the first generation unit 101 is shown in FIG. 12. FIG. 12(a) is an example of a matrix regenerated when the setting data to be output is the setting data of DB64 and DB82, and the management unit 104 performs divided output of this setting data. FIG. 12(b) is an example of a matrix regenerated when the setting data to be output is the setting data of DB64 and DB82, and the management unit 104 performs partial copy output of this setting data.

When the management unit 104 performs split output, as shown in FIG. 12(a), in the matrix that is regenerated, the display values of the items "High Layer" and "Device Program" and the display values of the items "Low Layer" and "Device Data" are "0". This indicates that the setting data that was set in DB64 and DB82 has been deleted by the split output.

On the other hand, when the management unit 104 performs a partial copy output, the regenerated matrix has the display values of the items "high layer" and "program for device" and the display values of the items "low layer" and "data for device" remaining at "1", as shown in FIG. 12(b). This indicates that the setting data that was set in DB64 and DB82 as a result of the partial copy output remains as it is, without being deleted from DB64 and DB82.

As an example of a matrix other than the above, a matrix in which the presence or absence of setting data is indicated by a "circle" and the output mode is indicated by a "check mark" or the like may be used, as shown in FIG. 13. In the example of FIG. 13, DBs with a display value of "circle" indicate that setting data is registered, and DBs with a "check mark" show an example in which setting data is output in separate parts.

In addition, the engineering device 10b can also import setting data from other engineering devices, similar to the engineering device 10 according to the first embodiment. In this case, if the setting data to be imported is output in parts, the engineering device 10b can import the setting data from the other engineering devices in a single DB unit (file unit) in the same way as the first embodiment.

For example, as shown in FIG. 14, in the case where the setting data of DB63 (physical classification "high layer" and functional classification "device program") has already been divided and output in the engineering device 10b, the display value of the column specified by "high layer" and "DDCPROGRAM" in the matrix is "0". In this case, the setting data can be imported in a batch on a DB basis (file basis) from another engineering device 10c, so that the import process can be completed quickly and work efficiency is improved.

In addition, in the second embodiment, the second generation unit 106 generates data showing a display screen that displays devices with the same physical classification in a tree structure based on the management data registered in the management DB 90, and the second display control unit 107 can cause the display device 50 to display the display screen shown by the data generated by the second generation unit 106.

An example of this display screen is shown in FIG. 15. FIG. 15(a) is an example of a case where, for example, an administrator or the like has instructed that information about devices with a "high floor" physical classification be displayed. In this case, the display screen displays information about the integrated controller 20 and primary device 30 with a "high floor" physical classification in a tree structure. Note that since the secondary device 40 is linked to its parent primary device 30, it may be omitted from display on this screen, and expanded to a level below the primary device 30 when the name of the primary device 30 is double-clicked, etc.

In addition, when an administrator or the like instructs to display information on devices with physical classifications of "high tier," "middle tier," and "low tier," the display screen displays, in a tree structure, information on integrated controllers 20 and primary devices 30 with a physical classification of "high tier," information on integrated controllers 20 and primary devices 30 with a physical classification of "middle tier," and information on integrated controllers 20 and primary devices 30 with a physical classification of "low tier," as shown in FIG. 15(b).

In addition, the administrator, etc. can switch between the displays of FIG. 15(a) and FIG. 15(b) as appropriate by inputting a display switching command via the display screen. This allows the administrator, etc. to select and display the desired information, improving convenience. Furthermore, the engineering device 10b can reduce the amount of information used for display by displaying devices for a specific physical division, particularly as in FIG. 15(a).

Next, we will explain the effects of the engineering device 10b according to embodiment 2.

As described above, the setting data set in the device is classified into several functions (types). Furthermore, the creation of this setting data is not done collectively by a specific administrator, but rather in many cases, administrators in charge of creating each type of setting data create the setting data for the function (type) for which they are responsible. In such cases, if the DB is only divided by a hierarchy such as the physical divisions (e.g., high, middle, and low) described in embodiment 1, the setting data can only be managed in units of these physical divisions, which is not necessarily convenient for administrators, etc.

Therefore, in the second embodiment, in addition to dividing the DB by physical division, the DB is divided by divisions different from the physical divisions (here, functional divisions). As a result, in the second embodiment, it is possible to handle setting data in units that take into account not only physical divisions but also functional divisions, and the efficiency of engineering work is further improved compared to the first embodiment. Also, in the second embodiment, information (e.g., a matrix) indicating whether or not setting data is registered for each of the multiple DBs is generated, and management instructions can be received via this information, so that the administrator, etc. can easily check whether or not setting data is registered in each divided DB, and it becomes possible to manage the divided and stored engineering data more easily than before.

As described above, according to the second embodiment, each of the multiple DBs divided into first divisions is further divided into second divisions different from the first division, and the first generation unit generates information indicating whether or not setting data is registered for the DB specified by the combination of the first division and the second division. This allows the administrator, etc., to easily check whether or not setting data is registered in each divided DB, as in the first embodiment, and makes it easier than ever to manage the divided and stored engineering data. In addition, it becomes possible to handle setting data in units that take into account not only the first division but also the second division, improving the efficiency of engineering work compared to the past.

According to the second embodiment, basic DBs 65, 75, and 85 in which basic data including a predetermined key item for associating a plurality of DBs having the same first division and different second divisions is registered, and a management DB 90 in which management data including a predetermined key item for associating the basic DBs 65, 75, and 85 having different first divisions is registered are constructed in the storage unit 105b, and the management unit 104 can individually or collectively manage the setting data registered in the plurality of DBs divided by the first division and the second division based on the basic data registered in the basic DBs 65, 75, and 85 constructed in the storage unit 105b and the management data registered in the management DB 90 constructed in the storage unit 105b. This allows the administrator, etc., to individually or collectively manage the setting data registered in the plurality of DBs divided by the first division and the second division.

The engineering device 10b also includes a second generation unit 106 that generates data showing a display screen that displays devices having the same first classification in a tree structure for each first classification based on the management data registered in the management DB 90, and a second display control unit 107 that causes the display device 50 to display the display screen shown by the data generated by the second generation unit 106. This allows the administrator, etc., to easily identify devices having the same first classification even when the DB is divided into first and second classifications.

Furthermore, according to the second embodiment, the first classification is determined based on the floor of the facility in which the device is installed, and the second classification is determined by the function of the setting data. This allows the administrator to handle the setting data in more detail than in the first embodiment, improving the efficiency of engineering work.

In the second embodiment, as in the first embodiment, an example was described in which the first generation unit 101 generates a matrix targeting DBs (high-tier DBs, mid-tier DBs, and low-tier DBs) excluding the common layer DB. However, in the second embodiment, even when generating a matrix including the common layer DB, the same processing as above can be performed.

In addition, any of the components of the embodiments of the present invention may be modified or omitted within the scope of the invention.

1000 Facility monitoring system 10, 10b Engineering device 10c Other engineering device 20 Integrated controller 30 Primary device 40 Secondary device 50 Display device 65, 75, 85 Basic DB
90 Management DB
101: First generation unit 102: First display control unit 103: Reception unit 104: Management unit 105, 105b: Storage unit 106: Second generation unit 107: Second display control unit

Claims (10)

a first generating unit that generates information indicating whether or not setting data to be set for a device for monitoring or controlling equipment installed in the facility is registered for each of a plurality of databases divided into predetermined first sections;
a first display control unit that causes a display device to display the information generated by the first generation unit;
a reception unit that receives a management instruction for managing the setting data via the information displayed on the display device;
a management unit that manages the setting data based on a management instruction received by the reception unit;
Engineering equipment with. the reception unit receives, as the management instruction, an instruction to output the setting data via information displayed on the display device;
2. The engineering device according to claim 1, wherein the management unit outputs the setting data from a database in which the setting data is registered, based on an output instruction received by the reception unit. The engineering device according to claim 2, characterized in that, when performing the output, the management unit deletes the setting data to be output from the database from which it was registered, or copies and outputs the setting data to be output without deleting it from the database from which it was registered. The first generation unit regenerates the information when the setting data is output by the management unit,
The engineering device according to claim 3 , wherein the first display control unit causes the display device to display the information regenerated by the first generation unit. Each of the plurality of databases divided into the first divisions is further divided into second divisions different from the first divisions,
5. The engineering device according to claim 1, wherein the first generation unit generates information indicating whether the setting data is registered in a database identified by a combination of the first category and the second category. a basic database in which basic data including a predetermined key item for relating a plurality of databases having the same first division and different second divisions to each other is registered, and a management database in which management data including a predetermined key item for relating the basic databases having different first divisions to each other is registered,
The engineering device according to claim 5, characterized in that the management unit is capable of individually or collectively managing the setting data registered in a plurality of databases divided into a first division and a second division based on the basic data registered in the basic database constructed in the storage unit and the management data registered in the management database constructed in the storage unit. a second generation unit that generates data showing a display screen in which devices having the same first category are displayed in a tree structure for each first category based on management data registered in the management database;
a second display control unit that causes the display device to display a display screen indicated by the data generated by the second generation unit;
7. The engineering device according to claim 6, further comprising: the first division is a division determined based on a floor of the facility in which the device is installed,
8. The engineering device according to claim 5, wherein the second classification is determined by a function of the setting data. The engineering device according to any one of claims 1 to 8, characterized in that the first generation unit generates a matrix as the information. An engineering method using an engineering device, comprising:
a step in which a first generation unit generates, for each of a plurality of databases divided into a first predetermined division, information indicating whether or not setting data to be set for a device for monitoring or controlling equipment installed in the facility is registered;
A step in which a first display control unit causes a display device to display the information generated by the first generation unit;
a receiving unit receiving a management instruction for managing the setting data via the information displayed on the display device;
a management unit managing the setting data based on the management instruction received by the reception unit;
An engineering method having the following features:

Images