ENGINEERING APPARATUS AND ENGINEERING METHOD

Abstract

To provide an engineering device capable of managing, more easily than before, engineering data that is divided and held.SOLUTION: An engineering device 10 includes: a first generation unit 101 that, for each of a plurality of databases divided according to each predetermined first division, generates information indicating whether or not setting data to be set for a device for monitoring or controlling an apparatus installed in a facility is registered; a first display control unit 102 that causes a display device 50 to display the information generated by the first generation unit 101; a reception 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 reception unit 103.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to an engineering apparatus and an engineering method for performing various settings on devices that constitute a facility monitoring system. [Background technology]

[0002] Conventionally, there is known an engineering device that creates setting data for operating a plurality of 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 setting data for each device, and constructs a facility monitoring system by having each device download (receive) the created setting data. 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 pieces of equipment installed in the facility.

[0003] 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 state of the primary device by operating based on setting data downloaded from the engineering equipment. The primary device monitors or controls the secondary device under the primary device by operating based on setting data downloaded from the engineering equipment. The secondary device monitors or controls the equipment under the secondary device by operating based on setting data downloaded from the engineering equipment.

[0004] When constructing a facility monitoring system, the engineering device operates in an 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, an 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 by the administrator or the like in a single storage unit (database, hereinafter referred to as "DB") as engineering data. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2020-160909 A Summary of the Invention [Problem to be solved by the invention]

[0006] Generally, a facility monitoring system has a large number of secondary devices, which results in a large volume of configuration data for the secondary devices, and therefore a large volume of engineering data. On the other hand, multiple managers (engineers) may be involved in creating and modifying the engineering data, and if the volume of engineering data is large, it may cause problems in transferring the engineering data between managers, which may reduce the efficiency of the engineering work.

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

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

[0009] However, when managing the engineering data stored in such a divided manner, the administrator or the like must actually use an engineering device to access each DB and check whether the setting data is registered in each DB in order to determine whether the setting data is registered in each DB. This type of checking work is cumbersome for the administrator or the like when managing the engineering data, and an improvement was required.

[0010] The present invention has been made to solve the above-mentioned problems, and has an object to provide an engineering device that makes it easier than ever to manage engineering data that is stored in a divided manner. [Means for solving the problem]

[0011] The engineering device of the present invention is characterized in that it comprises 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 within a facility is registered for each of a plurality of databases divided into predetermined first divisions, a first display control unit that displays the information generated by the first generation unit on a display device, a reception unit that receives management instructions 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 instructions received by the reception unit. Effect of the Invention

[0012] According to the present invention, since it is configured as described above, it becomes possible to manage the divided and stored engineering data more easily than ever before. [Brief description of the drawings]

[0013] [Figure 1] 1 is a diagram showing an example of the configuration of a facility monitoring system including an engineering device according to a first embodiment; [Diagram 2] FIG. 1 illustrates an example of the configuration of an engineering device according to a first embodiment. [Diagram 3] FIG. 2 is a diagram showing an example of DB construction in the first embodiment. [Figure 4] 5 is a flowchart showing an operation example of the engineering device according to the first embodiment. [Diagram 5] FIG. 2 is a diagram showing an example of a matrix according to the first embodiment. [Figure 6] FIG. 11 shows examples of new matrices in embodiment 1, 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. [Figure 7] FIG. 11 is a diagram illustrating an example of the configuration of an engineering device according to a second embodiment. [Figure 8] FIG. 11 is a diagram showing an example of DB construction in the second embodiment. [Figure 9]FIG. 11 is a diagram illustrating an example of a configuration of a basic DB in the second embodiment. [Figure 10] FIG. 11 is a diagram illustrating an example of a configuration of a management DB according to the second embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a matrix in the second embodiment. [Figure 12] 11A and 11B show examples of new matrices in the second embodiment, 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. [Figure 13] FIG. 11 is a diagram showing another example of the matrix in the second embodiment. [Figure 14] FIG. 11 is a diagram for explaining the import of setting data in the second embodiment. [Figure 15] FIG. 11 shows 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". DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] 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 an example of the configuration 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.

[0015] 1, the facility monitoring system 1000 is provided with one integrated controller 20, one primary device 30, and three secondary devices 40, but the numbers of the integrated controller 20, the primary devices 30, and the secondary devices 40 are not limited to this. Also, the integrated controller 20 is not an essential component and may be omitted. Also, the secondary device 40 is connected to a device to be controlled or monitored, but the display of this device is omitted in FIG. 1.

[0016] The engineering device 10 performs engineering processing including the creation of the setting data described above, and constructs the facility monitoring system 1000. The setting data is, for example, setting data for the integrated controller 20 for the integrated controller 20 to monitor the state of the primary device 30, setting data for the primary device 30 for the primary device 30 to monitor or control the subordinate secondary device 40, and setting data for the secondary device 40 for the secondary device 40 to monitor or control the subordinate equipment. The engineering device 10 also 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 a storage unit 105 (see FIG. 2).

[0017] The integrated controller 20 downloads setting data corresponding to its own device from the engineering data held by the engineering device 10, and operates based on the downloaded setting data to monitor the state of the primary device 30. The integrated controller 20 displays information indicating the state 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 state of the primary device 30. The integrated controller 20 and the primary device 30 are installed at the same hierarchical level.

[0018] The primary device 30 downloads configuration data corresponding to itself from the engineering data held by the engineering device 10, and monitors or controls the secondary devices 40 under its control by operating based on the downloaded configuration data.

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

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

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

[0022] 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 setting data set in the integrated controller 20, setting data set in the primary device 30, and setting data set in the secondary device 40.

[0023] In addition, in the holding unit 105, a plurality of DBs are constructed, which are divided by physical division. Here, the physical division is, for example, a division for managing devices such as the integrated controller 20, the primary device 30, and the secondary device 40 (hereinafter, referred to as "device management division"). As an example, when the physical division is the "device management division", the physical division is a division 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 from each other 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).

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

[0025] In the above, an example was given of a case where the physical classification is determined based on the floor of the facility on which the device is installed, but the physical classification is not limited to this. For example, when the devices are installed on the same floor, the classification may be determined based on the direction in which the device is installed (north, south, etc.), or it may be any classification determined for managing the devices, regardless of where the device is installed in the facility.

[0026] The storage unit 105 is configured, for example, by a hard disk drive (HDD), a solid state drive (SSD), a memory, etc. In addition, although the case where the storage unit 105 is provided inside the engineering device 10 is shown in FIG. 2, the storage unit 105 may be provided outside the engineering device 10.

[0027] The first generating unit 101 refers to each of the multiple DBs constructed in the holding unit 105 by dividing the DBs 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.

[0028] The first display control unit 102 causes the display device 50 to display the information generated by the first generation unit 101 .

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

[0030] The management unit 104 manages the setting data based on the management instruction accepted by the reception unit 103. For example, if the management instruction accepted 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 accepted by the reception unit 103 is an output instruction, the management unit 104 outputs the setting data.

[0031] When outputting setting data, the management unit 104 either deletes the setting data to be output from the DB where it was registered, or copies and outputs the setting data to be output without deleting it from the DB where it was registered, in accordance with instructions from the administrator, etc. For ease of explanation, the former output will be referred to as "split output" and the latter output as "partial copy output" below.

[0032] When the setting data is output by the management unit 104, the first generating unit 101 regenerates information reflecting the output of the setting data. Furthermore, the first display control unit 102 causes the display device 50 to display the information regenerated by the first generating unit 101.

[0033] 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 CPU (Central Processing Unit) (not shown) provided in the engineering device 10 executing a predetermined program expanded in a memory (not shown).

[0034] For ease of explanation, 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 include a registration unit that registers setting data created by an administrator or the like in the corresponding DB according to the physical classification.

[0035] 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 the sake of 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, in the following, 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.

[0036] Also, 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 a plurality of DBs constructed in the holding unit 105. Also, an example will be described in which the first generating unit 101 generates a matrix for DBs (higher layer DB, middle layer DB, and lower layer DB) excluding the common layer DB among the DBs exemplified in Fig. 3. Also, an example will be described in which the receiving unit 103 receives an output instruction for setting data as a management instruction via the matrix.

[0037] First, the first generation unit 101 refers to each of the high-tier DB, mid-tier DB, and low-tier DB constructed in the holding unit 105 by dividing them into physical divisions, and generates a matrix indicating whether or not setting data is registered for these DBs (step ST401).

[0038] An example of the matrix generated by the first generating 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, the mid-tier DB, and the low-tier DB constructed in the holding 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 generating unit 101 generating the matrix, the administrator or the like can easily grasp at a glance whether or not setting data is registered in each of the divided DBs.

[0039] Note that the matrix shown in Fig. 5 is merely an example, and the configuration and display values ​​of the matrix are not limited to those in Fig. 5. For example, the matrix may have a configuration and display values ​​other than those described above as long as it can indicate whether or not setting data is registered for the high-tier DB, the mid-tier DB, and the low-tier DB.

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

[0041] Next, the reception unit 103 receives an output instruction for outputting 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 item "high floor" 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 item "low floor" 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. Also, 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 of the registration source, or "partial copy output" in which the setting data to be output is copied and output without being deleted from the DB of the registration source. 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.

[0042] 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 "divided output" or "partial copy output" in response to an instruction from an administrator or the like.

[0043] 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). Also, the first display control unit 102 causes the display device 50 to display the matrix regenerated by the first generating unit 101 (step ST406).

[0044] 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-tier 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-tier DB and the management unit 104 performs partial copy output.

[0045] When the management unit 104 performs divisional output of the setting data of the low layer DB, the regenerated matrix has the display value of the low layer DB set to "0" as shown in Fig. 6(a). This indicates that the setting data set in the low layer DB has been deleted by the divisional output.

[0046] 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 shows that the display value of the low layer DB remains at "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 is not deleted from the low layer DB and remains as it is.

[0047] In this way, since divided output does not leave the output setting data in the engineering device 10 (the DB from which it was registered), the division of labor becomes clear as to which administrator will be responsible for editing the output setting data, etc. Furthermore, after output, the total data size of the setting data left in the engineering device 10 and the output setting data becomes approximately equal to the total data size 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 total data size of the setting data held by the engineering device 10 before output, the output setting data becomes easier to handle and can also be easily handed over between administrators via email, etc.

[0048] Furthermore, 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 divided and output, the setting data can be imported from the other engineering device in a batch in DB units (file units), so that the import process can be completed quickly and work efficiency is improved.

[0049] On the other hand, in 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 in DB units (file units). However, partial copy output is effective when it is desired to hold the setting data to be output as a master in the engineering device 10. Also, in this case, as in the case of divided output, the output setting data is easy to handle, and it is also easy to transfer between administrators by e-mail or the like.

[0050] In the above example, when partial copy output is performed, the matrix regenerated by the first generating 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, the case where the management instruction is an output instruction has been described, but when the management instruction is a display instruction, there is no change in the matrix, so steps ST405 and ST406 may be omitted.

[0051] In the above example, the first generation unit 101 generates a matrix for DBs (higher layer DB, middle layer DB, and lower layer DB) excluding the common layer DB among the DBs illustrated in FIG. 3, but the same processing as above can be performed even when generating a matrix including the common layer DB.

[0052] 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 to be set for a device for monitoring or controlling equipment installed in a facility is registered for each of a plurality of DBs divided into predetermined first divisions, a first display control unit 102 that causes the display device 50 to display the information generated by the first generating unit 101, 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 manager or the like to easily check whether or not setting data is registered in each of the divided DBs, making it possible to manage the divided and held engineering data more easily than ever before.

[0053] Furthermore, the reception unit 103 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 in which the setting data was registered, based on the output instruction received by the reception unit 103. This allows the administrator or the like to output desired setting data more easily than ever before.

[0054] Furthermore, when performing output, the management unit 104 either deletes the setting data to be output from the DB of the registration source, or copies and outputs the setting data to be output without deleting it from the DB of the registration source. As a result, in divided output, the division of labor regarding which administrator will be in charge of editing the output setting data, etc., can be clearly determined, and the output setting data can 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 can be easily handled, and can also be easily transferred between administrators by email, etc.

[0055] Furthermore, when the setting data is output by the management unit 104, 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.

[0056] In addition, the first generating unit generates a matrix as information, which enables an administrator or the like to easily see at a glance whether or not setting data is registered in each of the divided DBs.

[0057] Embodiment 2 In the first embodiment, an example has been described in which the DB constructed in the holding unit 105 is divided into physical partitions in advance. In contrast, in the second embodiment, an example will be described in which each of the multiple DBs constructed for each physical partition is further divided into partitions different from the physical partitions.

[0058] 7 is a diagram showing a configuration example 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, compared to the engineering device 10 according to embodiment 1. Since the other configurations of the engineering device 10b are similar to those of the engineering device 10 according to embodiment 1, the same reference numerals are used and the description thereof will be omitted.

[0059] First, a configuration example of the storage unit 105b is shown in Fig. 8. In the storage unit 105b, as shown in Fig. 8, each of the DBs (high layer DB, middle layer DB, and low layer DB) except for the common layer DB divided by physical division is constructed by further dividing it into divisions (here, functional divisions) different from the physical divisions. Here, the functional division is a division that is 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".

[0060] 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 state of the primary device 30 on a display device. The device program is a program 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.

[0061] Moreover, the "basic data" shown in Fig. 8 is data including predetermined key items for relating multiple DBs with the same physical division but different functional divisions to each other. The basic data is registered in the basic DBs (reference numerals 65, 75, and 85 in Fig. 8). Moreover, the "management data" shown in Fig. 8 is data including predetermined key items for relating basic DBs with different physical divisions to each other.

[0062] For example, DB 61 registers setting data whose physical category is "high floor" and whose functional category is "integrated controller data", i.e., setting data set for the integrated controller 20 installed on the high floor of the facility. DB 62 registers setting data whose physical category is "high floor" and whose functional category is "device data", i.e., setting data set for the primary device 30 and secondary device 40 installed on the high floor of the facility.

[0063] DB63 also registers setting data whose physical category is "high floor" and whose functional category is "graphics data", i.e., setting data set in 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 state of the primary device 30 on the display device. DB64 also registers setting data whose physical category is "high floor" and whose functional category is "device program", i.e., programs to be installed in the primary device 30 and secondary device 40 installed on the high floor of the facility.

[0064] DB65 is a basic DB, and basic data including a predetermined key item for relating DB61 to DB64, which have a physical division of "high floor", to each other is registered in DB65. The predetermined 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.

[0065] Similarly, setting data specified by a combination of a physical division and a functional division is registered in DB71 to DB74 and DB81 to DB84. In addition, in basic DB75, data including a predetermined key item for associating DB71 to DB74, which have a physical division of "middle layer", with each other is registered, and in basic DB85, data including a predetermined key item for associating DB81 to DB84, which have a physical division of "low layer", with each other is registered.

[0066] Furthermore, DB90 is a management DB, and management data including a predetermined key item for relating the 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, the basic DBs 65, 75, and 85 are related to each other with the device information as the key item. As a result, all DBs constructed in the holding unit 105b are related to each other with the device information as the key item. Note that configuration examples of the basic DBs 65, 75, and 85 and the management DB 90 will be described later.

[0067] The second generating unit 106 generates data for showing a display screen on which devices having the same physical classification are displayed in a tree structure, based on the management data registered in the management DB 90.

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

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

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

[0071] 9, "DEVICE_TYPE" indicates the type of device, "1" indicates the integrated controller, "2" indicates the primary device 30, and "3" indicates the secondary device 40. "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.

[0072] 9, for example, the device with "KEY_NO" "20" is the integrated controller, the devices with "KEY_NO" "1" to "4", "10", "12", and "14" are primary devices, and the devices with "KEY_NO" "21" and "25" to "31" are secondary devices. Also, the primary device that is the parent of the secondary device with "KEY_NO" "21" is the device with "KEY_NO" "14".

[0073] Meanwhile, the setting data registered in DBs 61 to 64 also includes device information ("KEY_NO"). DBs 61 to 65 are associated with each other using this device information as a key item. Therefore, by referring to 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.

[0074] Fig. 10 shows an example of the configuration of the management DB 90. In the management DB 90, data including a predetermined key item for relating the basic DBs 65, 75, and 85, which have different physical divisions, to one another is registered as management data. For the sake of simplicity, it is assumed here that the predetermined key item is device information ("KEY_NO" in Fig. 10).

[0075] In the management DB 90 in Fig. 10, "ORG_NO" indicates a serial number. Also, "DB_ID" indicates a physical division, with "1" indicating the high floor, "2" the middle floor, and "3" the low floor. Also, when a device is newly added, information about the added device is displayed in "NEW_NO".

[0076] 10 corresponds to the "KEY_NO" in the basic data registered in the 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 in the "middle tier" physical classification, and that its parent primary device is a device with a "KEY_NO" of "10."

[0077] In this way, in the engineering device 10b, for example, the management DB 90 is associated with the basic DBs 65, 75, and 85 with the device information included in the management data as a key item, and further the basic DBs 65, 75, and 85 are associated with DBs 61-64, DBs 71-74, and DBs 81-84, respectively, with the device information included 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 a plurality of DBs divided by physical division and functional division, based on the management data registered in the management DB 90 and the basic data registered in the basic DBs 65, 75, and 85.

[0078] An operation example of the engineering device 10b according to the second embodiment is substantially similar to the operation example of the engineering device 10 according to the first embodiment described with reference to the flowchart in Fig. 4, and differs only in the configuration of the matrix generated by the first generating unit 101. Therefore, in the following, a detailed explanation of the operation example 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.

[0079] 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 in 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 in 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.

[0080] It should be noted that the matrix shown in Fig. 11 is merely an example, and the configuration and display values ​​of the matrix are not limited to those in Fig. 11. For example, the matrix may have a configuration and display values ​​other than those described above, so long as it can indicate whether or not setting data is registered in DB61-64, DB71-74, and DB81-84, and whether or not management data is registered in management DB90.

[0081] Also in the second embodiment, the receiving unit 103 receives an output instruction for outputting 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 items "high layer" and "program for device" in the matrix displayed on the display device 50 are selected by the administrator or the like, the receiving unit 103 receives an output instruction for setting data registered in the DB 64 specified by "high layer" and "program for device". Also, when the items "low layer" and "data for device" in the matrix displayed on the display device 50 are selected by the administrator or the like, the receiving unit 103 receives an output instruction for setting data registered in the DB 82 specified by "low layer" and "data for device". At this time, the receiving 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 of the registration source, or to perform "partial copy output" in which the setting data to be output is copied and output without being deleted from the DB of the registration source.

[0082] 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 the fact 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.

[0083] 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 setting data in 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 setting data in DB64 and DB82, and the management unit 104 performs partial copy output of this setting data.

[0084] When the management unit 104 performs the divided output, as shown in Fig. 12(a), in the matrix that is regenerated, 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" are "0." This indicates that the setting data that was set in DB64 and DB82 has been deleted by the divided output.

[0085] On the other hand, when the management unit 104 performs 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 set in DB64 and DB82 remains as it is without being deleted from DB64 and DB82 as a result of the partial copy output.

[0086] As an example of a matrix other than the above, a matrix in which the presence or absence of setting data is represented by "o" and the output mode is represented by "check marks" or the like may be used, as shown in Fig. 13. In the example of Fig. 13, a DB with a display value of "o" indicates that setting data is registered, and a DB with a check mark indicates that the setting data is output in a divided manner.

[0087] The engineering device 10b can also import setting data from other engineering devices, similar to the engineering device 10 according to the embodiment 1. In this case, if the setting data to be imported is output in divided portions, the engineering device 10b can import the setting data from the other engineering devices in a batch on a DB basis (file basis) similar to the embodiment 1.

[0088] For example, as shown in Fig. 14, when the setting data of DB63 (physical classification: "high layer" and functional classification: "program for device") 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 in DB units (file units) from another engineering device 10c, so that the import process can be completed quickly and work efficiency is improved.

[0089] Furthermore, in the second embodiment, the second generation unit 106 generates data indicating a display screen that displays devices having 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 indicated by the data generated by the second generation unit 106.

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

[0091] Furthermore, when an administrator or the like instructs that information on devices whose physical classifications are "high layer," "middle layer," and "low layer" be displayed, as shown in FIG. 15(b), information on the integrated controller 20 and primary device 30 whose physical classification is "high layer," information on the integrated controller 20 and primary device 30 whose physical classification is "middle layer," and information on the integrated controller 20 and primary device 30 whose physical classification is "low layer" are displayed in a tree structure on the display screen.

[0092] In addition, the administrator or the like can switch between the displays of Fig. 15(a) and Fig. 15(b) as appropriate by inputting a display switching instruction via the display screen. This allows the administrator or the like to select and display desired information, improving convenience. In addition, the engineering device 10b can reduce the amount of information used for display by displaying devices by targeting a specific physical division, as in Fig. 15(a).

[0093] Next, the effects of the engineering device 10b according to the second embodiment will be described.

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

[0095] Therefore, in the second embodiment, in addition to dividing the DB according to physical division, the DB is divided according to divisions different from the physical divisions (here, functional divisions). As a result, in the second embodiment, it becomes 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 a plurality of 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 held engineering data more easily than before.

[0096] 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 divisions, and the first generating unit generates information indicating whether or not setting data is registered in a DB specified by a 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 to manage the divided and held engineering data than before. 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 before.

[0097] According to the second embodiment, the 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 with each other are registered, and the 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 with each other are 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.

[0098] The engineering device 10b also includes a second generating unit 106 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 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 generating unit 106. This allows the administrator or the like to easily grasp devices having the same first category even when the DB is divided into first and second categories.

[0099] According to the second embodiment, the first division is determined based on the floor of the facility where the device is installed, and the second division 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.

[0100] In the second embodiment, as in the first embodiment, an example has been described in which the first generation unit 101 generates a matrix targeting DBs (higher layer DB, middle layer DB, and lower layer DB) excluding the common layer DB. However, in the second embodiment, even in the case of generating a matrix including the common layer DB, the processing can be performed in the same manner as described above.

[0101] It should be noted that, within the scope of the present invention, any of the components of the embodiments may be modified or omitted. [Explanation of symbols]

[0102] 1000 Facility Monitoring System 10, 10b Engineering Equipment 10c Other Engineering Equipment 20 Integrated Controller 30 Primary Devices 40 Secondary Devices 50 Display device 65, 75, 85 Basic DB 90 Management DB 101 1st generation part 102 First display control unit 103 Reception 104 Management Department 105, 105b Holding part 106 Second generation part 107 Second display control unit

Claims

1. 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 the management instruction received by the reception unit; Engineering equipment with.

2. the reception unit receives, as the management instruction, an instruction to output the setting data via information displayed on the display device; The management unit outputs the setting data from the database in which the setting data was registered, based on the output instruction received by the reception unit.

2. The engineering device according to claim 1.

3. 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.

4. the first generating unit regenerates the information when the setting data is output by the management unit; The first display control unit causes the display device to display the information regenerated by the first generation unit.

4. The engineering device according to claim 3.

5. Each of the plurality of databases divided into the first divisions is further divided into second divisions different from the first divisions, The first generation unit generates information indicating whether the setting data is registered in a database specified by a combination of the first category and the second category.

5. An engineering device according to claim 1, wherein the engineering device comprises:

6. 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.

7. a second generation unit that generates data showing a display screen in which devices having the same first classification are displayed in a tree structure for each first classification 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:

8. 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.

9. 9. The engineering device according to claim 1, wherein the first generating unit generates a matrix as the information.

10. 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 of a first display control unit causing 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; The engineering method has the following features:

Images