Data management device and data management system

Abstract

Provided is a data management device (10) that uses data collected from a plant (20) equipped with a module (244) for executing data processing and a facility hierarchy including a facility (21), equipment (22) belonging to the facility (21), and a device (23) belonging to the equipment (22) as a basis to visualize the dependency relationship of the facility hierarchy and the dependency relationship between the module (244) and signals input to and output from the module (244), said data management device (10) comprising: a dependency relationship analysis unit (11) that generates dependency relationship data (121) indicating the dependency relationship of the facility hierarchy and the dependency relationship between the module (244) and the signals on the basis of facility hierarchy data (31) and input / output signal data (33); and a screen display unit (13) that uses the dependency relationship data (121) as a basis to generate screen data for a plant management screen indicating the dependency relationship of the facility hierarchy and the dependency relationship between the module (244) and the signals.

Description

Data Management Device and Data Management System

[0008] , ,

[0007] , ,

[0006] ,

[0001] The present disclosure relates to a data management device and a data management system for managing data collected from a plurality of facility hierarchies.

[0002] Plants such as sewage treatment plants, water purification plants, industrial product manufacturing plants, chemical plants, and power generation plants have a plurality of facilities, each facility having one or more pieces of equipment, and each piece of equipment having one or more devices.

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

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

[0005] In recent years, with the increase in the size and complexity of plants, the number of facilities, equipment, and devices constituting the plant has tended to increase, and accordingly, the total number of signals input to the module and signals output from the module has also increased.

[0006] When the total number of signals input to and output from the module is large, if the meaning and definition of the signals input to and output from the module become personalized, when the plant administrator changes, it becomes unclear for what purpose the module is installed. Therefore, it is desired to make the purpose of installing the module understandable to anyone by visualizing the dependency relationship between the module and the signal.

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

[0008] International Publication No. 2012 / 011145

[0009] However, while the technology disclosed in Patent Document 1 above allows for the visualization of the software structure, it was not possible to visualize the dependencies between modules and signals, such as which modules utilize signals output by the equipment constituting the plant, and whether signals output by modules are further utilized by other modules.

[0010] This disclosure is made in view of the above and aims to provide a data management device that can visualize the dependency relationship between modules and signals.

[0011] To solve the aforementioned problems and achieve the objectives, the data management device according to this disclosure visualizes the dependencies of the equipment hierarchy and the dependencies between modules and signals input and output to the modules, based on data collected from a plant comprising a facility, equipment belonging to the facility, equipment belonging to the equipment, a facility hierarchy including the facility, and modules that perform data processing. The data management device acquires equipment hierarchy data showing the structure of the equipment hierarchy and input / output signal data showing signals input and output to the modules from the plant, and comprises a dependency analysis unit that generates dependency data showing the dependencies of the equipment hierarchy and the dependencies between modules and signals based on the equipment hierarchy data and input / output signal data, and a screen display unit that generates screen data for a plant management screen showing the dependencies of the equipment hierarchy and the dependencies between modules and signals based on the dependency data. Modules output signals showing processed data generated by performing data processing on data indicated by signals output from equipment or other modules.

[0012] This disclosure provides the benefit of obtaining a data management device that can visualize the dependencies between modules and signals.

[0013] Figure showing the configuration of the data management device according to Embodiment 1. Figure showing an example of equipment hierarchy data used by the data management device according to Embodiment 1 for dependency analysis between modules. Figure showing an example of signal management data used by the data management device according to Embodiment 1 for dependency analysis between modules. Figure showing an example of input / output signal data used by the data management device according to Embodiment 1 for dependency analysis between modules. Figure showing an example of dependency data generated by the data management device according to Embodiment 1. Figure showing an example of a plant management screen generated by the screen display unit of the data management device according to Embodiment 1. Figure showing the configuration of the data management device according to Embodiment 2. Figure showing a first example of a plant management screen generated by the screen display unit of the data management device according to Embodiment 2. Figure showing a state in which signals of low importance are displayed in the first example of the plant management screen of the data management device according to Embodiment 2. Figure 2 shows a second example of a plant management screen where the screen display unit of the data management device according to Embodiment 2 generates screen data. Figure 3 shows a third example of a plant management screen where the screen display unit of the data management device according to Embodiment 2 generates screen data. Figure 4 shows a fourth example of a plant management screen where the screen display unit of the data management device according to Embodiment 2 generates screen data. Figure 5 shows the configuration of the data management device according to Embodiment 3. Figure 6 shows an example of clustering processing in the data management device according to Embodiment 3. Figure 7 shows an example of data generated in the clustering processing in the data management device according to Embodiment 3. Figure 8 shows the configuration of the data management system according to Embodiment 4. Figure 9 shows an example of hardware configuration for realizing the data management devices according to Embodiments 1 to 3.

[0014] The data management device and data management system according to the embodiment will be described in detail below with reference to the drawings.

[0015] Embodiment 1. Figure 1 is a diagram showing the configuration of a data management device according to Embodiment 1. The data management device 10 according to Embodiment 1 is connected to a plant 20. The plant 20 is a sewage treatment plant, a water purification plant, an industrial product manufacturing plant, a chemical plant, and a power generation plant, but is not limited to any particular type. The plant 20 has one or more facilities 21, each facility 21 is equipped with one or more pieces of equipment 22, and each piece of equipment 22 is equipped with one or more devices 23. Hereinafter, the facilities 21, pieces of equipment 22, and devices 23 that constitute the plant 20 are collectively referred to as the "equipment hierarchy". The plant 20 is equipped with a plant control device 24. The devices 23 output signals indicating data measured by sensors and the like. The plant control device 24 includes an equipment hierarchy data storage unit 241 that stores equipment hierarchy data 31, which is data relating to the structure of the equipment hierarchy; a signal management data storage unit 242 that stores signal management data 32, which shows the history of signals output from the equipment 23; an input / output signal data storage unit 243 that stores input / output signal data 33, which shows the input / output signals of a module 244, which will be described later; a module 244 that outputs a signal showing processed data generated by performing data processing on an input signal; and a controller 245 that controls the equipment 23 based on the signals 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 equipment hierarchy data 31 from the equipment hierarchy data storage unit 241. The dependency analysis unit 11 also acquires signal management data 32 from the signal management data storage unit 242. The dependency analysis unit 11 also acquires input / output signal data 33 from the input / output signal data storage unit 243.

[0017] Figure 2 shows an example of equipment hierarchy data used by the data management device according to Embodiment 1 for dependency analysis between modules. The equipment hierarchy data 31 includes facility data 311 showing the relationship between facility 21 and equipment 22, equipment data 312 showing the relationship between equipment 22 and device 23, and device data 313 showing the relationship between device 23 and output signals.

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

[0019] Figure 3 shows an example of signal management data used by the data management device according to Embodiment 1 for analyzing dependencies between modules. The signal management data 32 is data that associates a tag ID with a date and time indicating when the output signal was output and a sensor value indicating the data value of the output signal.

[0020] Figure 4 shows an example of input / output signal data used by the data management device according to Embodiment 1 for analyzing dependencies between modules. The input / output signal data 33 is data that associates the module name, which indicates the name of module 244, the tag ID of the input signal, and the tag ID of the output signal.

[0021] The dependency analysis unit 11 generates dependency data, which is data that shows the relationship between the equipment hierarchy of plant 20 and module 244 in a directed graph, based on the equipment hierarchy data 31, signal management data 32, and input / output signal data 33. In the example shown in Figures 2 to 4, the dependency analysis unit 11 identifies that plant 20 has facilities A and facilities B by referring to the facility data 311. The dependency analysis unit 11 also identifies that the facility name of facility 21 with facility ID de_0001 is facility A, and that it has facilities 22 with equipment ID f_0001 and facilities 22 with equipment ID f_0002 below it by referring to the facility data 311. It also identifies that the facility name of facility 21 with facility ID de_0002 is facility B, and that it has facilities 22 with equipment ID f_0003 below it.

[0022] Furthermore, the dependency analysis unit 11, by referring to the equipment data 312, identifies that the equipment name of equipment 22 with equipment ID f_0001 is the initial sedimentation equipment and that equipment 23 with equipment ID m_0001 is subordinate to it, and that the equipment name of equipment 22 with equipment ID f_0002 is the reaction tank equipment and that equipment 23 with equipment ID m_0002 is subordinate to it. Furthermore, the dependency analysis unit 11, by referring to the equipment data 312, identifies that the equipment name of equipment 22 with equipment ID f_0003 is the initial sedimentation equipment and that equipment 23 with equipment ID m_0003 is subordinate to it.

[0023] Furthermore, the dependency analysis unit 11, by referring to the device data 313, identifies that the device name of device 23 with device ID m_0001 is a System 1 device and outputs signals for tag ID 0001 and tags IDs 0002 and 0004. Furthermore, the dependency analysis unit 11, by referring to the device data 313, identifies that the device name of device 23 with device ID m_0002 is a System 1 device and outputs a signal for tag ID 0003. Furthermore, the dependency analysis unit 11, by referring to the device data 313, identifies that the device name of device 23 with device ID m_0003 is a System 2 device and outputs a signal for tag ID 0005.

[0024] Furthermore, the dependency analysis unit 11, by referring to the input / output signal data 33, identifies that the plant 20 includes module A, which receives signals for tag IDs 0001, 0002, and 0003 and outputs signals for tag IDs 0001_a, 0002_a, and 0003_a, and module B, which receives signals for tag IDs 0001, 0002, and 0001_a and outputs signals for 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 signals input and output to the module 244, and generates dependency data 121 that shows these dependencies. Figure 5 is a diagram showing an example of dependency data generated by the data management device according to Embodiment 1. The dependency data 121 shows the dependencies of the equipment hierarchy constituting the plant 20 and the dependencies between the module 244 and the signals. In Figure 5, the solid line frame is a facility label indicating facility 21, the dashed line frame is an equipment label indicating equipment 22, the dashed-dot line frame is an equipment label indicating device 23, the dashed-dot line frame is a signal label indicating a signal, and the double line frame is a module label indicating module 244. In the dependency data 121, the relationship between the equipment hierarchy of the plant 20, the module 244, and the signals is shown as a directed graph.

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

[0027] The screen display unit 13 generates screen data for a plant management screen that shows the dependencies of the equipment hierarchy constituting the plant 20 and the dependencies between the module 244 and the signals, based on the dependency data 121 stored in the dependency data storage unit 12.

[0028] Figure 6 is a diagram showing an example of a plant management screen generated by the screen display unit of the data management device according to Embodiment 1. The plant management screen 131 generated by the screen display unit 13 includes a plant structure display section 132 that shows the dependency relationships of the equipment hierarchy constituting the plant 20 in a tree structure, and a module display section 133 that shows the input and output signals of each module 244. In Figure 6, a solid line frame is a facility label indicating a facility 21, a dashed line frame is an equipment label indicating a piece of equipment 22, a dotted-dash line frame is an equipment label indicating a device 23, a double-dotted-dash line frame is a signal label indicating a signal, and a double line frame is a module label indicating a module 244. The module display section 133 displays the input and output signals of each module 244 on a module-by-module basis.

[0029] Furthermore, the dependency analysis unit 11 may generate dependency data 121 for signals that are used by any module 244, even though the input / output signal data 33 indicates that they are being used by one of the modules 244, by distinguishing them from signals for which there is a record of sensor value output in the signal management data 32. By having the dependency analysis unit 11 distinguish between signals for which there is no record of sensor value output and signals for which there is a record of sensor value output and generate dependency data 121, the plant management screen 131 can also distinguish between signals for which there is no record of sensor value output and signals for which there is a record of sensor value output. As a result, the plant manager can more accurately grasp the status of the plant 20 by referring to the plant management screen 131.

[0030] As described above, the data management device 10 according to Embodiment 1 can visualize the dependencies between the equipment hierarchy constituting the plant 20. Furthermore, the data management device 10 according to Embodiment 1 can visualize the dependencies between modules 244 and signals, such as which module 244 uses a signal output by equipment 23, and whether a signal outputting the result of data processing in module 244 is used in yet another module 244. For example, even in cases where the power consumption of multiple specific types of equipment 23 in the plant 20 is minimized by adding the power consumption of one piece of equipment 23 to another piece of equipment 23 in a module 244, and then adding the power consumption of yet another piece of equipment 23 to the summation result in another module 244 to calculate the total power consumption of multiple pieces of equipment 23, the dependencies between modules 244 and signals can be visualized. As a result, the manager of the plant 20 can easily grasp the status of the plant 20 by referring to the plant management screen 131.

[0031] Embodiment 2. Figure 7 shows the configuration of the data management device according to Embodiment 2. The data management device 10 according to Embodiment 2 differs from the data management device 10 according to Embodiment 1 in that it includes an importance calculation unit 14. The importance calculation unit 14 calculates the importance of modules 244 and signals. In addition, in the data management device 10 according to Embodiment 2, 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 the 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 how often the signal is used by module 244. For example, the importance calculation unit 14 calculates the importance based on the number of times the signal is used by module 244. In the example of input / output signal data 33 shown in Figure 4, the signal with tag ID 0001 is used by module A and module B, so its importance is calculated as 2. Also, the signal with tag ID 0001_a is used by module B, so its importance is calculated as 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 module 244 based on the number of times signals belonging to the same device 23 are used by module 244. In the example of device data 313 shown in Figure 2, device ID m_0001 outputs three signals with tag IDs 0001, 0002, and 0004, and since the signals with tag IDs 0001 and 0002 are used by module A and module B respectively, the importance of each signal output by device ID m_0001 is calculated to be 4. Also, device ID m_0002 outputs the signal with tag ID 0003, and since this signal is used by module A, the importance of the signal output by device ID m_0002 is calculated to be 1.

[0034] According to the input / output signal data 33 shown in Figure 4, the signal for tag ID 0004 output by the first system device with device ID m_0001 is not used by any of the modules 244. However, other signals output by the first system device with device ID m_0001, namely the signals for tag ID 0001 and tag ID 0002, are used by multiple modules 244, and it is highly likely that the signal for tag ID 0004 will also be used by one of the modules 244 in the future. The data management device 10 according to Embodiment 2 calculates the importance of signals based on the frequency of use of signals belonging to the same device 23, thereby setting a higher importance for signals that are not currently used but are highly likely to be used in the future.

[0035] Furthermore, the importance calculation unit 14 may calculate the importance of signals that have a high frequency of sensor value output as higher than the importance of signals that have a low frequency of sensor value output, based on the signal management data 32. In the example of signal management data 32 shown in Figure 3, the signal for tag ID 0001 has a higher frequency of sensor value output than the signals for tag ID 0002 and tag ID 0003, so the importance calculation unit 14 can calculate the importance of the signal for tag ID 0001 as higher than the importance of the signals for tag IDs 0002 and 0003.

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

[0037] Furthermore, even if modules 244 have the same number of input / output signals, if the units of the input / output signals are different, it is possible that some kind of simulation or other processing is being performed in that module 244. For this reason, the importance calculation unit 14 may calculate a lower importance only for modules 244 that have the same number of input / output signals and the same units for the input and output signals, and may calculate the importance of modules 244 that have the same number of input / output signals but different units for the input and output signals to be the same importance as modules 244 that have a different number of input / output signals.

[0038] The screen display unit 13 generates screen data for the plant management screen 131 with modified display modes for signals and modules 244, 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] Figure 8 shows a first example of a plant management screen generated by the screen display unit of the data management device according to Embodiment 2. In Figure 8, the solid line frame is a facility label indicating facility 21, the dashed line frame is an equipment label indicating equipment 22, the dashed line frame is an equipment label indicating device 23, the dashed line frame is a signal label indicating a signal, and the double line frame is a module label indicating module 244. The plant management screen 131 in the first example uses the importance of signals to hide signals with low importance by collapsing them. In the parts where there are hidden signals, an expand icon 134 is displayed, and by pressing the expand icon 134, the hidden signals will be displayed. In the example shown in Figure 8, the signal with tag ID 0004, which is not used in any module 244, is hidden. Figure 9 shows the state in which signals with low importance are displayed in the first example of the plant management screen of the data management device according to Embodiment 2. In the example shown in Figure 9, pressing the expand icon 134 displays the signal for tag ID 0004, and a collapse icon 135 is displayed around the signal for tag ID 0004. Pressing the collapse icon 135 collapses and hides the signal for tag ID 0004. The importance value used as a threshold for displaying or hiding the signal can be arbitrarily set by the user.

[0040] Figure 10 shows a second example of a plant management screen in which the screen display unit of the data management device according to Embodiment 2 generates screen data. In Figure 10, the solid line frame is a facility label indicating facility 21, the dashed line frame is an equipment label indicating equipment 22, the dashed line frame is an equipment label indicating device 23, the dashed line frame is a signal label indicating a signal, and the double line frame is a module label indicating module 244. The plant management screen 131 in the second example utilizes the importance level of module 244, hiding modules 244 with low importance by collapsing them.

[0041] Where the hidden module 244 exists, an expand icon 134 is displayed, and by pressing the expand icon 134, the hidden module 244 becomes visible. In the example shown in Figure 10, module A, which has the same number of input and output signals, is hidden. Figure 11 is a diagram showing a second example of the plant management screen of the data management device according to Embodiment 2, in which modules of low importance are displayed. In the example shown in Figure 11, module A is displayed by pressing the expand icon 134, and a collapse icon 135 is displayed around module A. By pressing the collapse icon 135, module A is collapsed and hidden.

[0042] Figure 12 shows a third example of a plant management screen in which the screen display unit of the data management device according to Embodiment 2 generates screen data. In Figure 12, the solid line frame is a facility label indicating facility 21, the dashed line frame is an equipment label indicating equipment 22, the dashed line frame is an equipment label indicating device 23, the dashed line frame is a signal label indicating a signal, and the double line frame is a module label indicating module 244. The plant management screen 131 in the third example utilizes the importance of signals and modules 244 to hide signals and modules 244 with low importance by collapsing them. In the plant management screen 131 of the third example, it is also possible to display signals and modules 244 with low importance by pressing the expand icon 134.

[0043] Figure 13 shows a fourth example of a plant management screen generated by the screen display unit of the data management device according to Embodiment 2. In Figure 13, the solid line frame is a facility label indicating facility 21, the dashed line frame is an equipment label indicating equipment 22, the dashed line frame is an equipment label indicating device 23, the dashed line frame is a signal label indicating a signal, and the double line frame is a module label indicating module 244. The plant management screen 131 of the fourth example utilizes the importance of signals, making the size of less important signals smaller than the size of more important signals. In the example shown in Figure 13, the display size of the signals is changed in two steps to emphasize the more important signals, but the display size of the signals may be changed in three or more steps. In addition, methods other than changing the display size may be used to emphasize the more important signals, as long as they can be emphasized. For example, the more important signals may be emphasized by displaying them in a different color than the less important signals.

[0044] Also, here, an example was shown in which a signal with a higher importance is emphasized over a signal with a lower importance by changing the display size of the signal. However, the module 244 with a higher importance may be emphasized over the module 244 with a lower importance by changing the display size or display color of the module 244.

[0045] The data management device 10 according to the second embodiment can emphasize and display a signal and a module 244 with a higher importance in managing the plant 20 as compared with a signal and a module 244 with a lower importance in managing the plant 20. Therefore, in the plant management screen 131 used for managing the large-scale plant 20 with a large number of signals and modules 244, the visibility of the signals and the module 244 important in managing the plant 20 can be enhanced.

[0046] Embodiment 3. FIG. 14 is a diagram showing the configuration of a data management device according to the third embodiment. The data management device 10 according to the third embodiment is different 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 relationship data 121 stored in the dependency relationship data storage unit 12, and generates dependency relationship data 121a that partially shows the network topology indicating the input / output signals of the facility hierarchy and the module 244 constituting the plant 20, with the device 23 having a higher importance being higher than the facility 22. Hereinafter, the dependency relationship data 121 generated by the clustering processing unit 15 is referred to as dependency relationship data 121a.

[0047] FIG. 15 is a diagram showing an example of clustering processing in the data management device according to Embodiment 3. In FIG. 15, a solid-line frame is a facility label indicating that it is Facility 21, a dashed-line frame is an equipment label indicating that it is Equipment 22, a one-dot chain-line frame is a device label indicating that it is Device 23, and a two-dot chain-line frame is a signal label indicating that it is a signal. In FIG. 15, it is assumed that the importance of the first system devices is calculated to be high by calculating the importance based on the dependency data 121. In the dependency data 121a generated by the clustering process, the dependency relationships of the facility hierarchy are rearranged to show the plant 20 in a tree structure in the order of Facility 21, Device 23, and Equipment 22. Further, in the dependency data 121a generated by the clustering process, the dependency relationships are shown only for the facility hierarchy and signals related to the first system devices 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 Embodiment 3. The clustering processing unit 15 identifies the device 23 in the lower hierarchy of the facility 21 by referring to the facility data 311 and the equipment data 312, and generates the clustering facility data 314. Further, the clustering processing unit 15 generates the clustering device data 315 by referring to the equipment data 312. Further, the clustering processing unit 15 identifies the signal output from the device 23 possessed by the equipment 22 by referring to the equipment data 312 and the device data 313, and generates the clustering equipment data 316. The clustering facility data 314 is data associating the facility ID, the facility name, and the device ID. The clustering device data 315 is data associating the device ID, the device name, and the equipment ID. The clustering equipment data 316 is data associating the equipment ID, the equipment name, and the tag ID.

[0049] The clustering processing unit 15 extracts records related to high-priority system 1 equipment from the clustering facility data 314, clustering equipment data 315, and clustering facility data 316. Specifically, in the clustering equipment data 315, the records related to system 1 equipment are the record associating equipment ID m_0001 with facility ID f_0001 and the record associating equipment ID m_0002 with facility ID f_0002, so the clustering processing unit 15 extracts these records. Similarly, in the clustering facility data 314, the records related to equipment IDs m_0001 and m_0002 are the record associating facility ID de_0001 with equipment ID m_0001 and the record associating facility ID de_0001 with equipment ID m_0002, so the clustering processing unit 15 extracts these records. Furthermore, in the clustering equipment data 316, the records relating to equipment IDs f_0001 and f_0002 are the records relating equipment ID f_0001 to tag ID 0001, the records relating equipment ID f_0001 to tag ID 0002, the records relating equipment ID f_0001 to tag ID 0004, and the records relating equipment ID f_0002 to tag ID 0003. Therefore, the clustering processing unit 15 extracts these records. Based on each of the extracted records, the clustering processing unit 15 generates dependency data 121a that shows dependencies only for the equipment hierarchy and signals relating to one system of equipment. In plant 20, there are two pieces of equipment 23 whose name is "System 1 Equipment," one with equipment ID m_0001 and the other with equipment ID m_0002. However, in dependency data 121a, the two pieces of equipment 23 with the same name are combined into one, so that equipment 23 is placed higher than equipment 22, and the network topology is shown with only equipment hierarchy and signal dependencies.

[0050] The screen display unit 13 generates screen data for the plant management screen 131, which shows the dependencies of the equipment hierarchy related to one system of equipment among the equipment hierarchy constituting the plant 20, and the dependencies between module 244 and signals, based on the dependency data 121a generated by the clustering processing unit 15. The screen display unit 13 may generate both the screen data for the plant management screen 131 based on the dependency data 121 generated by the dependency analysis unit 11 and the screen data for 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 have multiple treatment systems, and there may be multiple identical pieces of equipment 22 and machinery 23 within the facility 21. For example, in a sewage treatment plant, pollutants in the sewage are removed in stages, and each plant has two treatment systems, referred to as system 1 and system 2, and therefore, identical pieces of equipment 22 and machinery 23 exist for each system.

[0052] Therefore, depending on the type of plant 20, there is a need to understand the status of the plant 20 for each processing system. However, in the plant management screen 131 generated by the screen display unit 13 of the data management device 10 according to Embodiment 1, even if the equipment 23 is in the same processing system, it is displayed separately for each piece of equipment 22, making it difficult for the user to understand the status of the plant 20 for each processing system. In contrast, in the data management device 10 according to Embodiment 3, the clustering processing unit 15 generates dependency data 121a that shows the dependency relationship only for the equipment hierarchy and signals related to the equipment 23 with high weight. Therefore, the screen display unit 13 can use the dependency data 121a to generate screen data for the plant management screen 131 that shows the status of the plant 20 for each processing system. As a result, it is easy for the user of the data management device 10 according to Embodiment 3 to understand the status of the plant 20 for each processing system.

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

[0054] The data management system 100 according to Embodiment 4, like the data management device 10 according to Embodiment 1, can visualize the dependencies between collected data and processed data. Therefore, the manager of the plant 20 can easily grasp the status of the plant 20 by referring to the plant management screen 131.

[0055] Next, the hardware configuration of the data management device 10 will be described. Figure 18 is a diagram showing an example of a hardware configuration that realizes the data management device 10 according to Embodiments 1 to 3. The data management device 10 is realized as a computer system by a processing circuit that includes a processor 91 that performs various processes, a memory 92 which is the main memory, and a storage device 93 that stores information.

[0056] The processor 91 may be an arithmetic unit, microprocessor, microcomputer, CPU (Central Processing Unit), or DSP (Digital Signal Processor). The memory 92 can be a non-volatile or volatile semiconductor memory such as RAM (Random Access Memory), ROM (Read Only Memory), flash memory, EPROM (Erasable Programmable Read Only Memory), or EEPROM® (Electrically Erasable Programmable Read Only Memory). The storage device 93 stores a program for generating dependency data 121 that indicates the dependencies between the equipment hierarchy constituting the plant 20 and the dependencies between the module 244 and the signals. The processor 91 reads the program stored in the storage device 93 into the memory 92 and executes it. The function of the data management device 10 is realized when the processor 91 reads the program stored in the storage device 93 into the memory 92 and executes it. The data processing device 40 constituting the data management system 100 according to Embodiment 4 can also be realized as a computer system by the processing circuit shown in Figure 18.

[0057] The configurations shown in the above embodiments are merely examples of the content, and can be combined with other known technologies. It is also possible to omit or modify parts of the configuration without departing from the gist of the invention.

[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 Machinery, 24 Plant control device, 31 Equipment hierarchy 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 Expand icon, 135 Collapse icon, 241 Equipment hierarchy 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 Machinery data, 314 Clustering facility data, 315 clustering equipment data, 316 clustering facility data.

Claims

1. A data management device that visualizes the dependencies of the equipment hierarchy and the dependencies between the module and signals input and output to the module, based on data collected from a plant comprising a facility, equipment belonging to the facility, equipment belonging to the equipment, and modules for performing data processing, comprising: a dependency analysis unit that acquires equipment hierarchy data showing the structure of the equipment hierarchy and input / output signal data showing the signals input and output to the module from the plant, and generates dependency data showing the dependencies of the equipment hierarchy and the dependencies between the module 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 showing the dependencies of the equipment hierarchy and the dependencies between the module and the signals based on the dependency data, wherein the module outputs a signal showing processed data generated by performing the data processing on the data shown by the signal output from the equipment or other modules.

2. The data management device according to claim 1, comprising an importance calculation unit that calculates the importance of at least one of the modules and the signals, wherein the screen display unit generates screen data for the plant management screen that emphasizes the modules with high importance more than the modules with low importance, and emphasizes the signals with high importance more than the signals with low importance.

3. The data management device according to claim 2, characterized in that the importance calculation unit calculates a higher importance for devices that have a larger number of modules that utilize the output signal.

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. The data management device according to any one of claims 2 to 4, characterized in that the screen display unit generates screen data for the plant management screen in which at least one of the modules and signals of low importance is hidden by folding.

6. The data management device according to any one of claims 2 to 4, characterized in that it includes a clustering processing unit that generates dependency data that partially shows the network topology showing the equipment hierarchy and the input / output signals of the modules with higher importance placed above the equipment.

7. A data management system for visualizing the dependencies of the equipment hierarchy and the dependencies between the module and signals input and output to the module, based on data collected from a plant comprising a facility, equipment belonging to the facility, and equipment belonging to the equipment, and a module for performing data processing, the data management system comprising: a dependency analysis unit that acquires equipment hierarchy data showing the structure of the equipment hierarchy and input / output signal data showing the signals input and output to the module from the plant, and generates dependency data showing the dependencies of the equipment hierarchy and the dependencies between the module and the signals based on the equipment hierarchy data and the input / output signal data; a data processing unit that generates screen data for a plant management screen showing the dependencies of the equipment hierarchy and the dependencies between the module and the signals based on the dependency data; and a data storage device having a dependency data storage unit for storing the dependency data.

Images