Data management device and data management system

Abstract

A data management device (10) that visualizes dependencies of the equipment hierarchy and dependencies between the modules (244) and signals input and output to the modules (244) based on data collected from a plant (20) having a facility (21), equipment (22) belonging to the facility (21), an equipment hierarchy including devices (23) belonging to the equipment (22), and a module (244) that executes data processing. The data management device (10) includes a dependency analysis unit (11) that generates dependency data (121) indicating the dependencies of the equipment hierarchy and the dependencies between the modules (244) and the signals based on equipment hierarchy data (31) and input / output signal data (33), and a screen display unit (13) that generates screen data for a plant management screen indicating the dependencies of the equipment hierarchy and the dependencies between the modules (244) and the signals based on the dependency data (121).

Description

[Technical field]

[0001] The present disclosure relates to a data management device and a data management system that manage data collected from multiple facility hierarchies. [Background technology]

[0002] 2. Description of the Related Art Plants such as sewage treatment plants, water purification plants, industrial product manufacturing plants, chemical plants, and power plants have a plurality of facilities, each of which includes one or more pieces of equipment, and each piece of equipment includes one or more pieces of equipment.

[0003] To operate a plant normally, it is necessary to process data indicated by signals output from each device in an information processing device called a module to generate processed data, and to control each device based on signals indicating the processed data output from the module. The processed data generated by a module may be input to another module and used to generate processed data in the other module.

[0004] Therefore, in order to operate the plant normally, it is necessary to manage the signals input to and output from the modules.

[0005] In recent years, as plants have become larger and more complex, the number of facilities, equipment, and devices that make up the plants has tended to increase, and as a result, the total number of signals input to and output from modules has also increased.

[0006] When the total number of signals input to and output from a module is large, if the meanings and definitions of the signals input to and output from the module are personalized, when the plant manager is changed, it becomes difficult to understand the purpose for which the module was installed. For this reason, it is desirable to visualize the dependencies between modules and signals so that anyone can understand the purpose for which the module was installed.

[0007] Patent Document 1 discloses a technique for analyzing and visualizing the software structure of software. [Prior art documents] [Patent documents]

[0008] [Patent Document 1] International Publication No. 2012 / 011145 Summary of the Invention [Problem to be solved by the invention]

[0009] However, while the technology disclosed in Patent Document 1 makes it possible to visualize the software structure, it is not possible to visualize the dependencies between modules and signals, such as in which module a signal output by equipment constituting a plant is used, and whether a signal output by a module is used in yet another module.

[0010] The present disclosure has been made in consideration of the above, and has an object to provide a data management device that can visualize dependencies between modules and signals. [Means for solving the problem]

[0011] In order to solve the above-mentioned problems and achieve the object, a data management device according to the present disclosure visualizes the dependency of the equipment hierarchy and the dependency between modules and signals input and output to the modules based on data collected from a plant including a facility, equipment belonging to the facility, an equipment hierarchy including devices belonging to the equipment, and a module that executes data processing. The data management device includes a dependency analysis unit that acquires equipment hierarchy data indicating a structure of the equipment hierarchy and input / output signal data indicating signals input and output to the module from the plant, and generates dependency data indicating the dependency of the equipment hierarchy and the dependency between the modules and the signals based on the equipment hierarchy data and the input / output signal data, and a screen display unit that generates screen data of a plant management screen indicating the dependency of the equipment hierarchy and the dependency between the modules and the signals based on the dependency data. The module outputs a signal indicating processed data generated by performing data processing on data indicated by a signal output from the equipment or another module. Effect of the Invention

[0012] According to the present disclosure, it is possible to obtain an effect of providing a data management device capable of visualizing dependencies between modules and signals. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 shows a configuration of a data management device according to a first embodiment. [Diagram 2] FIG. 1 is a diagram showing an example of facility hierarchical data used by the data management device according to the first embodiment for analyzing dependencies between modules; [Diagram 3] FIG. 1 is a diagram showing an example of signal management data used by the data management device according to the first embodiment for analyzing dependencies between modules; [Figure 4] FIG. 1 is a diagram showing an example of input / output signal data used by the data management device according to the first embodiment for analyzing dependencies between modules; [Diagram 5] FIG. 1 is a diagram showing an example of dependency data generated by a data management device according to a first embodiment; [Figure 6]FIG. 13 is a diagram showing an example of a plant management screen for which screen data is generated by a screen display unit of the data management device according to the first embodiment; [Figure 7] FIG. 13 is a diagram showing a configuration of a data management device according to a second embodiment. [Figure 8] FIG. 11 is a diagram showing a first example of a plant management screen for which screen data is generated by a screen display unit of a data management device according to a second embodiment; [Figure 9] FIG. 13 is a diagram showing a state in which a signal with a low importance level is displayed on a first example of a plant management screen of the data management device according to the second embodiment; [Figure 10] FIG. 11 is a diagram showing a second example of a plant management screen for which screen data is generated by the screen display unit of the data management device according to the second embodiment; [Figure 11] FIG. 13 is a diagram showing a state in which modules with low importance are displayed on a second example of a plant management screen of the data management device according to the second embodiment; [Figure 12] FIG. 11 is a diagram showing a third example of a plant management screen for which screen data is generated by the screen display unit of the data management device according to the second embodiment; [Figure 13] FIG. 11 is a fourth example of a plant management screen for which screen data is generated by the screen display unit of the data management device according to the second embodiment; [Figure 14] FIG. 13 is a diagram showing a configuration of a data management device according to a third embodiment. [Figure 15] FIG. 13 is a diagram showing an example of clustering processing in the data management device according to the third embodiment; [Figure 16] FIG. 13 is a diagram showing an example of data generated in a clustering process in a data management device according to a third embodiment. [Figure 17] FIG. 13 is a diagram showing a configuration of a data management system according to a fourth embodiment. [Figure 18] FIG. 1 is a diagram showing an example of a hardware configuration for implementing a data management device according to a first to third embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A data management device and a data management system according to an embodiment will be described in detail below with reference to the drawings.

[0015] Embodiment 1 FIG. 1 is a diagram showing a configuration of a data management device according to a first embodiment. The data management device 10 according to the first embodiment is connected to a plant 20. The plant 20 may be a sewage treatment plant, a water purification plant, an industrial product manufacturing plant, a chemical plant, a power generation plant, or the like, but is not limited to a specific type. The plant 20 has one or more facilities 21, the facility 21 includes one or more pieces of equipment 22, and the equipment 22 includes one or more pieces of equipment 23. Hereinafter, the facilities 21, the equipment 22, and the equipment 23 constituting the plant 20 are collectively referred to as an "equipment hierarchy." The plant 20 includes a plant control device 24. The equipment 23 outputs a signal indicating data measured by a sensor or the like. The plant control device 24 includes an equipment hierarchy data storage unit 241 that stores equipment hierarchy data 31, which is data regarding the structure of the equipment hierarchy, a signal management data storage unit 242 that stores signal management data 32 indicating the history of signals output from the equipment 23, an input / output signal data storage unit 243 that stores input / output signal data 33 indicating input / output signals of a module 244 described later, a module 244 that performs data processing on the input signal and outputs a signal indicating processed data generated, and a controller 245 that controls the equipment 23 based on the signal output by the module 244.

[0016] The data management device 10 includes a dependency analysis unit 11, a dependency data storage unit 12, and a screen display unit 13. The dependency analysis unit 11 acquires facility hierarchical data 31 from a facility hierarchical data storage unit 241. The dependency analysis unit 11 also acquires signal management data 32 from a signal management data storage unit 242. The dependency analysis unit 11 also acquires input / output signal data 33 from an input / output signal data storage unit 243.

[0017] 2 is a diagram showing an example of equipment hierarchical data used for analyzing dependencies between modules by the data management device according to embodiment 1. The equipment hierarchical data 31 includes facility data 311 indicating the relationship between the facility 21 and the equipment 22, equipment data 312 indicating the relationship between the equipment 22 and the device 23, and device data 313 indicating the relationship between the device 23 and an output signal.

[0018] The facility data 311 is data that associates a facility ID (Identifier) ​​that is an identifier individually assigned to each facility 21, a facility name that is the name of the facility 21, and an equipment ID that is an identifier individually assigned to each piece of equipment 22. The equipment data 312 is data that associates a facility ID, a facility name that is the name of the facility 22, and an equipment ID that is an identifier individually assigned to each piece of equipment 23. The equipment data 313 is data that associates a equipment ID, an equipment name that is the name of the equipment 23, and a tag ID that is an identifier individually assigned to a signal.

[0019] 3 is a diagram showing an example of signal management data used for analyzing dependencies between modules by the data management device according to embodiment 1. The signal management data 32 is data in which a tag ID, a date and time indicating the timing at which an output signal is output, and a sensor value indicating a data value of the output signal are associated with each other.

[0020] 4 is a diagram showing an example of input / output signal data used for analyzing dependency relationships between modules by the data management device according to embodiment 1. The input / output signal data 33 is data in which a module name indicating the name of the module 244, a tag ID of an input signal, and a tag ID of an output signal are associated with each other.

[0021] The dependency relationship analysis unit 11 generates dependency relationship data, which is data showing the relationship between the equipment hierarchy of the plant 20 and the modules 244 in a directed graph, based on the equipment hierarchy data 31, the signal management data 32, and the input / output signal data 33. In the example shown in Figs. 2 to 4, the dependency relationship analysis unit 11 specifies that the plant 20 includes a facility A and a facility B by referring to the facility data 311. Furthermore, the dependency relationship analysis unit 11 specifies that the facility name of the facility 21 with the facility IDe_0001 is facility A, and that the facility 22 with the facility IDf_0001 and the facility 22 with the facility IDf_0002 are subordinate to the facility 21 with the facility IDe_0002. Furthermore, the dependency relationship analysis unit 11 specifies that the facility name of the facility 21 with the facility IDe_0002 is facility B, and that the facility 22 with the facility IDf_0003 is subordinate to the facility 21 with the facility IDf_0003.

[0022] Furthermore, by referring to the equipment data 312, the dependency relationship analysis unit 11 specifies that the equipment name of the equipment 22 with equipment IDf_0001 is "first-settling equipment" and that it has an equipment 23 with equipment IDm_0001 at a lower level, and that the equipment name of the equipment 22 with equipment IDf_0002 is "reaction tank equipment" and that it has an equipment 23 with equipment IDm_0002 at a lower level. Furthermore, by referring to the equipment data 312, the dependency relationship analysis unit 11 specifies that the equipment name of the equipment 22 with equipment IDf_0003 is "first-settling equipment" and that it has an equipment 23 with equipment IDm_0003 at a lower level.

[0023] Furthermore, by referring to the device data 313, the dependency relationship analysis unit 11 specifies that the device 23 with device ID m_0001 has a device name of a first system device and outputs a signal with tag ID 0001 and signals with tag IDs 0002 and 0004. Furthermore, by referring to the device data 313, the dependency relationship analysis unit 11 specifies that the device 23 with device ID m_0002 has a device name of a first system device and outputs a signal with tag ID 0003. Furthermore, by referring to the device data 313, the dependency relationship analysis unit 11 specifies that the device 23 with device ID m_0003 has a device name of a second system device and outputs a signal with tag ID 0005.

[0024] In addition, by referring to the input / output signal data 33, the dependency analysis unit 11 determines that the plant 20 includes a module A which receives signals with tag IDs 0001, 0002, and 0003 and outputs signals with tag IDs 0001_a, 0002_a, and 0003_a, and a module B which receives signals with tag IDs 0001, 0002, and 0001_a and outputs signals with tag IDs 0001_b and 0002_b.

[0025] Through the above operations, the dependency analysis unit 11 identifies the relationship between the equipment hierarchy constituting the plant 20, the module 244, and the signal input / output to the module 244, and generates dependency data 121 indicating these dependencies. FIG. 5 is a diagram showing an example of dependency data generated by the data management device according to the first embodiment. The dependency data 121 indicates the dependency of the equipment hierarchy constituting the plant 20 and the dependency between the module 244 and the signal. In FIG. 5, a solid line frame is a facility label indicating the facility 21, a dashed line frame is an equipment label indicating the equipment 22, a dot-dash line frame is an equipment label indicating the equipment 23, a double-dot-dash line frame is a signal label indicating the signal, and a double-dot line frame is a module label indicating the module 244. In the dependency data 121, the relationship between the equipment hierarchy of the plant 20, the module 244, and the signal is shown in a directed graph.

[0026] The dependency data storage unit 12 is a database capable of storing data on a network topology indicating equipment hierarchies constituting the plant 20 and input / output signals of the modules 244. A graph database can be applied to the dependency data storage unit 12, but is not limited to this.

[0027] Based on the dependency data 121 stored in the dependency data storage unit 12, the screen display unit 13 generates screen data for a plant management screen showing the dependencies of the equipment hierarchies that make up the plant 20 and the dependencies between the modules 244 and signals.

[0028] Fig. 6 is a diagram showing an example of a plant management screen for which the screen display unit of the data management device according to the first embodiment generates screen data. The plant management screen 131 for which the screen display unit 13 generates screen data includes a plant structure display field 132 showing the dependency relationships of the equipment hierarchies constituting the plant 20 in a tree structure, and a module display field 133 showing input / output signals of each module 244. In Fig. 6, a solid-line frame is a facility label indicating the facility 21, a dashed-line frame is an equipment label indicating the equipment 22, a dashed-dotted-line frame is an equipment label indicating the equipment 23, a double-dashed-line frame is a signal label indicating a signal, and a double-line frame is a module label indicating the module 244. The module display field 133 displays the input / output signals of each module 244 on a module-by-module basis.

[0029] The dependency analysis unit 11 may generate the dependency data 121 by distinguishing a signal that is indicated to be used in any of the modules 244 in the input / output signal data 33 but has no record of a sensor value output in the signal management data 32 from a signal that has a record of a sensor value output. By the dependency analysis unit 11 generating the dependency data 121 by distinguishing between a signal that has no record of a sensor value output and a signal that has a record of a sensor value output, it is possible to distinguish between a signal that has no record of a sensor value output and a signal that has a record of a sensor value output in the plant management screen 131. This allows the manager of the plant 20 to more accurately grasp the state of the plant 20 by referring to the plant management screen 131.

[0030] In this way, the data management device 10 according to the first embodiment can visualize the dependency relationship of the equipment hierarchy constituting the plant 20. In addition, the data management device 10 according to the first embodiment can visualize the dependency relationship between the module 244 and the signal, such as which module 244 uses the signal output by the device 23, and which module 244 uses the signal outputting the result of data processing in the module 244. For example, in order to minimize the power consumption of the entirety of a specific type of device 23 present in the plant 20, the power consumption of one device 23 and the power consumption of another device 23 are added in a certain module 244, and the power consumption of yet another device 23 is added to the sum result in another module 244 to calculate the power consumption of the entirety of the multiple devices 23. In this way, the manager of the plant 20 can easily grasp the state of the plant 20 by referring to the plant management screen 131.

[0031] Embodiment 2 7 is a diagram showing a configuration of a data management device according to the second embodiment. The data management device 10 according to the second embodiment differs from the data management device 10 according to the first embodiment in that it includes an importance calculation unit 14. The importance calculation unit 14 calculates the importance of a module 244 and a signal. In the data management device 10 according to the second embodiment, the screen display unit 13 changes the display mode of each module 244 and each signal based on the importance calculated by the importance calculation unit 14. The screen display unit 13 generates screen data for a plant management screen 131 that emphasizes modules 244 with high importance more than modules 244 with low importance and emphasizes signals with high importance more than signals with low importance.

[0032] The importance calculation unit 14 calculates the importance of a signal based on the frequency with which the signal is used by the module 244. For example, the importance calculation unit 14 calculates the importance based on the number of times the signal is used by the module 244. In the example of the input / output signal data 33 shown in Fig. 4, the signal with tag ID 0001 is used by module A and module B, so the importance is calculated to be 2. Also, the signal with tag ID 0001_a is used by module B, so the importance is calculated to be 1.

[0033] Alternatively, the importance calculation unit 14 calculates the importance of a signal based on the frequency of use of signals belonging to the same device 23. For example, the importance calculation unit 14 calculates the importance of each signal output by the module 244 based on the number of times that signals belonging to the same device 23 are used by the module 244. In the example of device data 313 shown in FIG. 2, the 1-system device with device ID m_0001 outputs three signals with tag IDs 0001, 0002, and 0004, and each of the signals with tag IDs 0001 and 0002 is used by module A and module B, so the importance of each signal output by the 1-system device with device ID m_0001 is calculated as 4. In addition, the 1-system device with device ID m_0002 outputs a signal with tag ID 0003, and this signal is used by module A, so the importance of the signal output by the 1-system device with device ID m_0002 is calculated as 1.

[0034] 4, the signal with tag ID 0004 output by the 1-system device with device ID m_0001 is not used by any of the modules 244, but the other signals with tag IDs 0001 and 0002 output by the 1-system device with device ID m_0001 are used by multiple modules 244, and it is highly likely that the signal with tag ID 0004 will also be used by one of the modules 244 in the future. The data management device 10 according to the second embodiment calculates the importance of signals based on the frequency of use of signals belonging to the same device 23, thereby making it possible to set high the importance of signals that are not currently being used but have a high possibility of being used in the future.

[0035] Furthermore, the importance calculation unit 14 may calculate the importance of a signal whose sensor value is output frequently to be higher than the importance of a signal whose sensor value is output infrequently, based on the signal management data 32. In the example of the signal management data 32 shown in Fig. 3, the signal of tag ID 0001 outputs a sensor value more frequently than the signals of tag ID 0002 and tag ID 0003, so the importance calculation unit 14 can calculate the importance of the signal of tag ID 0001 to be higher than the importance of the signals of tag IDs 0002 and 0003.

[0036] Further, the importance calculation unit 14 calculates the importance of the module 244 based on the number of signals input and output to the module 244. For example, the importance calculation unit 14 assigns a lower importance to a module 244 having the same number of input signals and the same number of output signals than a module 244 having a different number of input signals and the same number of output signals. For example, in the example of the input / output signal data 33 shown in FIG. 4, the module A has three input signals and three output signals, so it is highly likely to be a module 244 that performs intermediate processing to convert data for processing in the subsequent stage. On the other hand, the module B has a different number of input signals and a different number of output signals, so it is highly likely to be a module 244 that performs data processing to generate data to be used for analysis. For this reason, the importance calculation unit 14 calculates the importance of the module A to be lower than that of the module B.

[0037] Note that even if modules 244 have the same number of input and output signals, if the units of the input and output signals are different, there is a possibility that some kind of processing such as simulation is being performed in the module 244. For this reason, the importance calculation section 14 may calculate the importance of only modules 244 having the same number of input and output signals and the same units for the input and output signals to be low, and may calculate the importance of modules 244 having the same number of input and output signals but different units for the input and output signals to be the same as that of modules 244 having a different number of input and output signals.

[0038] The screen display unit 13 generates screen data for a plant management screen 131 in which the display mode of the signals and modules 244 is changed based on the dependency data 121 stored in the dependency data storage unit 12 and the importance calculated by the importance calculation unit 14.

[0039] FIG. 8 is a diagram showing a first example of a plant management screen for which the screen display unit of the data management device according to the second embodiment generates screen data. In FIG. 8, a solid frame is a facility label indicating the facility 21, a dashed frame is an equipment label indicating the equipment 22, a dot-dash frame is an equipment label indicating the equipment 23, a two-dot-dash frame is a signal label indicating a signal, and a double-line frame is a module label indicating the module 244. The plant management screen 131 of the first example uses the importance of signals and hides signals with low importance by folding. An unfold icon 134 is displayed in a portion where a hidden signal exists, and by pressing the unfold icon 134, the hidden signal becomes visible. In the example shown in FIG. 8, a signal with a tag ID 0004 that is not used by any of the modules 244 is hidden. FIG. 9 is a diagram showing a state in which a signal with low importance is displayed in the first example of a plant management screen of the data management device according to the second embodiment. 9, pressing the unfold icon 134 displays the signal of tag ID 0004, and a fold icon 135 is displayed around the signal of tag ID 0004. Pressing the fold icon 135 folds the signal of tag ID 0004 and makes it invisible. The importance value that serves as the threshold for whether to display or hide a signal can be set arbitrarily by the user.

[0040] Fig. 10 is a diagram showing a second example of a plant management screen for which the screen display unit of the data management device according to the second embodiment generates screen data. In Fig. 10, a solid-line frame is a facility label indicating the facility 21, a dashed-line frame is an equipment label indicating the equipment 22, a dot-dash-line frame is an equipment label indicating the device 23, a two-dot-dash-line frame is a signal label indicating a signal, and a double-line frame is a module label indicating the module 244. The plant management screen 131 of the second example uses the importance of the modules 244, and folds up modules 244 with low importance to hide them.

[0041] An expand icon 134 is displayed in the portion where the hidden module 244 exists, and by pressing the expand icon 134, the hidden module 244 becomes visible. In the example shown in FIG. 10, module A, which has the same number of input / output signals, is hidden. FIG. 11 is a diagram showing a state in which modules with low importance are displayed on a second example of a plant management screen of the data management device according to the second embodiment. In the example shown in FIG. 11, module A is displayed by pressing the expand icon 134, and a fold icon 135 is displayed around module A. By pressing the fold icon 135, module A is folded and becomes invisible.

[0042] FIG. 12 is a diagram showing a third example of a plant management screen in which a screen display unit of a data management apparatus according to Embodiment 2 generates screen data. In FIG. 12, a solid-line frame is a facility label indicating that it is Facility 21, a dashed-line frame is a facility label indicating that it is Equipment 22, a one-dot chain-line frame is a device label indicating that it is Device 23, a two-dot chain-line frame is a signal label indicating that it is a signal, and a double-line frame is a module label indicating that it is Module 244. The plant management screen 131 of the third example uses the importance level of signals and the importance level of Module 244, and non-important signals and Module 244 with a low importance level are made non-displayable by folding. Also in the plant management screen 131 of the third example, by pressing the expansion icon 134, it is possible to display non-important signals and Module 244 with a low importance level.

[0043] FIG. 13 is a diagram showing a fourth example of a plant management screen in which a screen display unit of a data management apparatus according to Embodiment 2 generates screen data. In FIG. 13, a solid-line frame is a facility label indicating that it is Facility 21, a dashed-line frame is a facility label indicating that it is Equipment 22, a one-dot chain-line frame is a device label indicating that it is Device 23, a two-dot chain-line frame is a signal label indicating that it is a signal, and a double-line frame is a module label indicating that it is Module 244. The plant management screen 131 of the fourth example uses the importance level of signals and makes the size of signals with a low importance level smaller than the size of signals with a high importance level. In the example shown in FIG. 13, signals with a high importance level are emphasized by changing the display size of signals in two steps, but the display size of signals may be changed in three or more steps. Also, if signals with a high importance level can be emphasized, methods other than changing the display size may be used. For example, signals with a high importance level may be emphasized by displaying them in a color different from that of signals with a low importance level.

[0044] Also, while an example has been shown here in which signals of high importance are emphasized more than signals of low importance by changing the display size of the signals, modules 244 of high importance may also be emphasized more than modules 244 of low importance by changing the display size or display color of the modules 244.

[0045] The data management device 10 according to the second embodiment can highlight and display signals and modules 244 that are important in managing the plant 20, compared with signals and modules 244 that are less important in managing the plant 20. This makes it possible to improve the visibility of signals and modules 244 that are important in managing the plant 20 on the plant management screen 131 used for managing a large-scale plant 20 having many signals and modules 244.

[0046] Embodiment 3 14 is a diagram showing a configuration of a data management device according to the third embodiment. The data management device 10 according to the third embodiment differs from the data management device 10 according to the second embodiment in that it includes a clustering processing unit 15. The clustering processing unit 15 performs clustering processing on the dependency data 121 stored in the dependency data storage unit 12, and generates dependency data 121 that partially shows the network topology showing the equipment hierarchy constituting the plant 20 and the input / output signals of the modules 244, with the equipment 23 having a high importance being placed higher than the equipment 22. Hereinafter, the dependency data 121 generated by the clustering processing unit 15 is referred to as dependency data 121a.

[0047] FIG. 15 is a diagram showing an example of clustering processing in the data management device according to the third embodiment. In FIG. 15, a solid line frame is a facility label indicating a facility 21, a dashed line frame is an equipment label indicating a facility 22, a dashed line frame is an equipment label indicating a device 23, and a dashed line frame is a signal label indicating a signal. In FIG. 15, the importance of the first system equipment is calculated to be high by the calculation of the importance based on the dependency relationship data 121. In the dependency relationship data 121a generated by the clustering processing, the dependency relationships of the equipment hierarchies are rearranged so as to show the plant 20 in a tree structure in the order of the facility 21, the device 23, and the equipment 22. In addition, in the dependency relationship data 121a generated by the clustering processing, the dependency relationships are shown only for the equipment hierarchies and signals related to the first system equipment with high weight.

[0048] FIG. 16 is a diagram showing an example of data generated in the clustering process in the data management device according to the third embodiment. The clustering processing unit 15 refers to the facility data 311 and the equipment data 312 to identify the equipment 23 in a lower layer of the facility 21, and generates the clustering facility data 314. The clustering processing unit 15 also refers to the equipment data 312 to generate the clustering equipment data 315. The clustering processing unit 15 also refers to the equipment data 312 and the equipment data 313 to identify the signal output from the equipment 23 of the equipment 22, and generates the clustering equipment data 316. The clustering facility data 314 is data in which a facility ID, a facility name, and an equipment ID are associated with each other. The clustering equipment data 315 is data in which an equipment ID, an equipment name, and a facility ID are associated with each other. The clustering equipment data 316 is data in which a facility ID, a facility name, and a tag ID are associated with each other.

[0049] The clustering processing unit 15 extracts records related to 1-system devices having high importance from the clustering facility data 314, the clustering device data 315, and the clustering equipment data 316. That is, the records related to 1-system devices in the clustering device data 315 are a record associating device IDm_0001 with device IDf_0001 and a record associating device IDm_0002 with device IDf_0002, so the clustering processing unit 15 extracts these records. Also, in the clustering facility data 314, the records related to device IDs m_0001 and m_0002 are a record associating facility IDe_0001 with device IDm_0001 and a record associating facility IDe_0001 with device IDm_0002, so the clustering processing unit 15 extracts these records. Furthermore, in the clustering equipment data 316, the records related to equipment IDf_0001 and f_0002 are a record associating equipment IDf_0001 with tag ID0001, a record associating equipment IDf_0001 with tag ID0002, a record associating equipment IDf_0001 with tag ID0004, and a record associating equipment IDf_0002 with tag ID0003, so the clustering processing unit 15 extracts these records. Based on each extracted record, the clustering processing unit 15 generates dependency data 121a indicating dependency relationships only for equipment hierarchies and signals related to the 1-system devices. In the plant 20, there are two devices 23 with the device name "System 1 device", one with device ID m_0001 and the other with device ID m_0002. However, in the dependency data 121a, the devices 23 with the same name are grouped together, and a network topology is shown in which the device 23 is ranked higher than the equipment 22 and only the equipment hierarchy and the signal dependency are indicated.

[0050] The screen display unit 13 generates screen data of a plant management screen 131 indicating dependencies of equipment hierarchies related to the first-system devices among the equipment hierarchies constituting the plant 20 and dependencies between the module 244 and signals, based on the dependency data 121a generated by the clustering processing unit 15. Note that the screen display unit 13 may generate both the screen data of the plant management screen 131 based on the dependency data 121 generated by the dependency analysis unit 11 and the screen data of the plant management screen 131 based on the dependency data 121a generated by the clustering processing unit 15.

[0051] Depending on the type of plant 20, it may be equipped with multiple treatment systems, and multiple pieces of the same type of equipment 22 and devices 23 may exist within the facility 21. For example, in a sewage treatment plant, pollutants in sewage are removed in stages, and since the plant is equipped with facilities 21 for two treatment systems, each of which is called System 1 and System 2, the same type of equipment 22 and devices 23 exists for each system.

[0052] For this reason, depending on the type of plant 20, there is a need to grasp the state of the plant 20 for each processing system. However, in the plant management screen 131 for which the screen display unit 13 of the data management device 10 according to the first embodiment generates screen data, even if the devices 23 are of the same processing system, they are displayed separately for each facility 22, making it difficult for the user to grasp the state of the plant 20 for each processing system. In contrast, in the data management device 10 according to the third embodiment, the clustering processing unit 15 generates dependency data 121a indicating dependency only for the equipment hierarchy and signals related to the devices 23 with high weight, so that the screen display unit 13 can generate screen data of the plant management screen 131 indicating the state of the plant 20 for each processing system using the dependency data 121a. This makes it easy for the user of the data management device 10 according to the third embodiment to grasp the state of the plant 20 for each processing system.

[0053] Embodiment 4 17 is a diagram showing a configuration of a data management system according to embodiment 4. The data management system 100 according to embodiment 4 includes a data processing device 40 and a data storage device 50. The data processing device 40 includes a dependency analysis unit 11 and a screen display unit 13, and the data storage device 50 includes a dependency data storage unit 12.

[0054] The data management system 100 according to the fourth embodiment can visualize the dependencies between collected data and processed data, similarly to the data management device 10 according to the first embodiment. Therefore, the manager of the plant 20 can easily grasp the state of the plant 20 by referring to the plant management screen 131.

[0055] Next, a description will be given of the hardware configuration of the data management device 10. Fig. 18 is a diagram showing an example of a hardware configuration for realizing the data management device 10 according to the first to third embodiments. The data management device 10 is realized as a computer system by a processing circuit including a processor 91 that executes various processes, a memory 92 that is a main memory, and a storage device 93 that stores information.

[0056] The processor 91 may be a calculation means such as an arithmetic device, a microprocessor, a microcomputer, a CPU (Central Processing Unit), or a DSP (Digital Signal Processor). The memory 92 may be a non-volatile or volatile semiconductor memory such as a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, an EPROM (Erasable Programmable Read Only Memory), or an EEPROM (Electrically Erasable Programmable Read Only Memory). The storage device 93 stores a program for executing a process of generating dependency data 121 indicating the dependency relationship of the equipment hierarchy constituting the plant 20 and the dependency relationship between the module 244 and a signal. The processor 91 reads the program stored in the storage device 93 into the memory 92 and executes it. The processor 91 reads the program stored in the storage device 93 into the memory 92 and executes it, thereby realizing the function of the data management device 10. The data processing device 40 constituting the data management system 100 according to the fourth embodiment can also be realized as a computer system by the processing circuit shown in FIG. 18.

[0057] The configurations shown in the above embodiments are merely examples of the contents, and may be combined with other known technologies. Parts of the configurations may be omitted or modified without departing from the spirit of the invention. [Explanation of symbols]

[0058] 10 data management device, 11 dependency analysis unit, 12 dependency data storage unit, 13 screen display unit, 14 importance calculation unit, 15 clustering processing unit, 20 plant, 21 facility, 22 equipment, 23 device, 24 plant control device, 31 equipment hierarchical data, 32 signal management data, 33 input / output signal data, 40 data processing device, 50 data storage device, 91 processor, 92 memory, 93 storage device, 100 data management system, 121, 121a dependency data, 131 plant management screen, 132 plant structure display field, 133 module display field, 134 expansion icon, 135 collapse icon, 241 equipment hierarchical data storage unit, 242 signal management data storage unit, 243 input / output signal data storage unit, 244 module, 245 controller, 311 facility data, 312 equipment data, 313 device data, 314 Clustering facility data, 315 Clustering equipment data, 316 Clustering equipment data.

Claims

1. 1. A data management device that visualizes dependencies of an equipment hierarchy and dependencies between a module and a signal input / output to / from the module, based on data collected from a plant including a facility, equipment belonging to the facility, an equipment hierarchy including devices belonging to the equipment, and a module that executes data processing, the data management device comprising: a dependency analysis unit that acquires from the plant equipment hierarchy data indicating a structure of the equipment hierarchy and input / output signal data indicating the signals input and output to the modules, and generates dependency data indicating dependencies of the equipment hierarchy and dependencies between the modules and the signals based on the equipment hierarchy data and the input / output signal data; a screen display unit that generates screen data of a plant management screen showing the dependency relationships of the equipment hierarchies and the dependency relationships between the modules and the signals based on the dependency data, A data management device characterized in that the module outputs the signal indicating processed data generated by performing the data processing on data indicated by the signal output from the device or another module.

2. an importance calculation unit that calculates the importance of at least one of the module and the signal; The data management device according to claim 1, characterized in that the screen display unit generates screen data for the plant management screen in which the modules with higher importance are emphasized more than the modules with lower importance, and the signals with higher importance are emphasized more than the signals with lower importance.

3. 3. The data management device according to claim 2, wherein the importance calculation section calculates a higher importance for a device having a larger number of modules that use the signal to be output.

4. The data management device according to claim 2, characterized in that the importance calculation unit calculates the importance of a module in which the number of input signals and the number of output signals are different to be higher than the importance of a module in which the number of input signals and the number of output signals are the same.

5. 5. The data management device according to claim 2, wherein the screen display unit generates screen data for the plant management screen in which at least one of the modules and the signals with low importance is hidden by folding.

6. The data management device according to any one of claims 2 to 4, characterized in that it is further provided with a clustering processing unit that generates the dependency data that partially indicates the network topology indicating the equipment hierarchy and the input / output signals of the modules, with the equipment of higher importance being higher than the equipment.

7. A data management system that visualizes dependencies of the equipment hierarchy and dependencies between the modules and signals input / output to the modules based on data collected from a plant including a facility, equipment belonging to the facility, an equipment hierarchy including devices belonging to the equipment, and a module that executes data processing, the data management system comprising: a dependency analysis unit that acquires from the plant equipment hierarchy data indicating a structure of the equipment hierarchy and input / output signal data indicating the signals input and output to the modules, and generates dependency data indicating the dependency of the equipment hierarchy and the dependency between the modules and the signals based on the equipment hierarchy data and the input / output signal data, and a screen display unit that generates screen data for a plant management screen indicating the dependency of the equipment hierarchy and the dependency between the modules and the signals based on the dependency data, and a data management system having a dependency data storage unit that stores the dependency data.

Images