Information management device, information management system, information management method, and information management program
Patent Information
- Application Number
- PCT/JP2025/012783
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-03-28
- Publication Date
- 2026-10-01
Smart Images
Figure JP2025012783_01102026_PF_FP_ABST
Abstract
Description
Information management apparatus, information management system, information management method, and information management program
[0001] The present disclosure relates to an information management apparatus, an information management system, an information management method, and an information management program.
[0002] Conventionally, for example, know-how relating to factory control, operation, and the like has been accumulated, and workers check the know-how to resolve failures in the factory and achieve stable operation. Such know-how has been organized by category to facilitate workers' access to desired know-how.
[0003] As a technique for realizing management of diverse information, for example, Patent Document 1 discloses a management apparatus that can freely set a plurality of groups for management points. Specifically, the management apparatus described in Patent Document 1 manages and controls information of a plurality of managed devices as management points. Similarly to the parameters that management points have in advance, the management apparatus can define and add groups for each management point for groups arbitrarily added by a user, and is configured to allow a plurality of arbitrary keywords to be freely set for each management point.
[0004] Japanese Unexamined Patent Application Publication No. 2012-141695
[0005] According to the above-described conventional technique, searching under various conditions is enabled, and accessibility to desired information is improved. However, for example, it is not possible to check whether other information related to the searched information exists, and operations such as changing conditions and performing a search again are required.
[0006] The present disclosure has been made in view of the foregoing, and an object of the present disclosure is to obtain an information management apparatus capable of improving accessibility to information required by a user.
[0007] To solve the above-mentioned problems and achieve the objective, the information management device according to this disclosure is characterized by comprising: a node in which information to be managed is stored; a management table creation unit that creates a node management table in which management items indicating the attributes of the information and the storage location of the information are registered; an information management unit that manages the information based on the node management table; and a display processing unit that displays the nodes in a multidimensional manner on a display unit based on management items selected from among the management items and the node management table.
[0008] The information management device described herein has the effect of improving users' accessibility to the information they need.
[0009] Figures showing an example configuration of the information management system according to Embodiment 1 Figures showing an example configuration of the account management table Figures showing an example configuration of the node management table Figures showing an example of a correlation data management image displayed on a user terminal Figures showing other examples of correlation data management images displayed on a user terminal Figures showing an example of a method for displaying information managed by the information management system according to Embodiment 1 Figures showing an example of the overall operation of the information management system according to Embodiment 1 Flowchart showing an example of the operation performed by a user on the information management system according to Embodiment 1 Figure 1 Flowchart showing an example of the operation performed by a user on the information management system according to Embodiment 1 Figure 2 Flowchart showing an example of the operation performed by a user on the information management system according to Embodiment 1 Figure 3 Flowchart showing an example of the operation performed by a user on the information management system according to Embodiment 1 Nodes registered in the node management table A diagram showing an example of the procedure for changing a name. A diagram showing an example of the procedure for changing the relationship registered in the node management table. A flowchart showing an example of the operation of the information management device when the information management system according to Embodiment 1 displays a correlation data management image on a user terminal. A diagram showing an overview of the operations performed by the user when the correlation data management image is displayed on a user terminal. A flowchart showing an example of the operation of the information management system according to Embodiment 1 to change the correlation data management image displayed on a user terminal. A first diagram explaining the operation of the information management system according to Embodiment 1 to change the correlation data management image displayed on a user terminal. A second diagram explaining the operation of the information management system according to Embodiment 1 to change the correlation data management image displayed on a user terminal. A diagram showing an example of applying the information management system to a production system. A diagram showing an example of how to use the information management system according to Embodiment 1. A diagram showing an example of hardware that realizes the information management device.
[0010] The information management device, information management system, information management method, and information management program according to embodiments of this disclosure will be described in detail below with reference to the drawings.
[0011] Embodiment 1. Figure 1 shows an example of the configuration of an information management system 100 according to Embodiment 1. The information management system 100 includes an information management device 1 that manages information provided to the user, a storage device 2 that stores various types of information managed by the information management device 1, and a user terminal 500 having a display unit and an operation unit for the user to check information, etc.
[0012] The information management system 100 is a system that manages various types of information related to the factory, its equipment, and the products produced in the factory using a graph database. Examples of information managed by the information management system 100 include the factory's operational performance, information on products manufactured in the factory, manuals for the factory's production equipment, notes on precautions regarding work procedures on the production floor, and environmental information such as temperature, humidity, vibration, and noise within the factory. A graph database is a database that displays multiple pieces of information multidimensionally via nodes. That is, the display unit of the user terminal 500 displays a multidimensional group of information from the information managed in the graph database that meets the conditions specified by the user. In the following explanation, the screen on which the user terminal 500 displays the group of information multidimensionally will be referred to as the "correlated data management image."
[0013] The information management device 1 comprises a data processing unit 10 and an input / output unit 20. The data processing unit 10 reads a group of information that satisfies conditions specified by the user of the user terminal 500 from the storage device 2, and based on the read group of information, creates display data in a format that allows the relationships between the information to be visually recognized, specifically, display data that displays the group of information in a multidimensional manner, and provides it to the user terminal 500. The data processing unit 10, for example, functions as a Web (World Wide Web) server and creates a Web page that displays the group of information that satisfies the conditions specified by the user in a multidimensional manner. The data processing unit 10 transmits the created Web page to the user terminal 500 as display data of a correlated data management image. The input / output unit 20 sends and receives various types of data to and from the user terminal 500.
[0014] The data processing unit 10 of the information management device 1 includes a detailed information setting unit 11 for setting detailed information for nodes in a graph database, an information management unit 12 for managing information based on a node management table (described later), an account management unit 13 for managing user account information of the information management system 100, a management table setting information acquisition unit 14 for acquiring information to be set in the node management table, a management table creation unit 15 for creating the node management table, and a display processing unit 16 for creating a correlated data management image.
[0015] The input / output unit 20 of the information management device 1 includes an operation reception unit 21 that receives operations on the information management device 1 from a user of a user terminal 500.
[0016] The storage device 2 includes a product database (DB) 201 that stores information on products manufactured in the factory, a management information database (DB) 202 that stores account management tables and node management tables, which will be described later, and a factory operational technology database (OTDB) 203 that stores information on operational technology (OT) equipment used to manufacture the products.
[0017] In this type of information management system 100, the graph database nodes are associated with the product DB 201, the management information DB 202, and the factory OTDB 203. For example, product manuals are stored in the product DB 201 via the manual node. Users can retrieve product manuals using the user terminal 500 as needed.
[0018] Figure 2 shows an example of the configuration of the account management table. The account management table 301 registers the account information of users of the information management system 100. The account management table 301 is created by the account management unit 13. The account management unit 13 creates the account management table 301 by obtaining account information from the system administrator or the like. The account information may be entered via the user terminal 500 or via a terminal device not shown in the figure. The account management table 301 registers one or more account names (account A, account B, ...), and also registers information from one or more node management tables associated with each account name. For example, for account A, node management table A1, node management table A2, and node management table A3 are registered as associated information.
[0019] When management is performed according to the account management table 301 shown in Figure 2, a user corresponding to account A can check the information registered in node management table A1, node management table A2, and node management table A3, respectively, via the user terminal 500. Similarly, a user corresponding to account B can check the information registered in node management table B1 via the user terminal 500.
[0020] Figure 3 shows an example of the configuration of a node management table. The node management table 302 consists of node name, management items (risk level, supply chain (supplier C), engineering chain (engineer C), item A, item B), source, relationship, number, storage location, and display status. Note that the node management table 302 may also be configured to register other management items, or to register other information not included in the management items.
[0021] A node is an information management point (a starting point for managing information), and is given a name such as factory, processing machine 1, or line 1.
[0022] Management items are items that indicate the attributes of the information managed by the node. For example, a node named "Factory" manages information belonging to each of the following categories, marked with a circle in the diagram: risk level, supply chain, engineering chain, item A, and item B.
[0023] The source indicates the origin of the information managed by the node. For example, in the node management table 302 shown in Figure 3, the source of each piece of information managed by the node named "Line 1" is the factory, and the source of each piece of information managed by the node named "Processing Machine 1" is Line 1. In this embodiment, among the nodes registered in the node management table, nodes without a set source are sometimes referred to as parent nodes, and nodes with a set source are sometimes referred to as child nodes.
[0024] The relationship indicates related nodes, and this relationship is shown by a unique number assigned to each node (hereinafter sometimes referred to as the node number). For example, in the node management table 302 shown in Figure 3, the node named "Instruction Manual" has the node number #011, and the relationship of the node named "Trouble Occurred..." is also set to #011. As a result, the node named "Instruction Manual" and the node named "Trouble Occurred..." are associated using node number #11 as the key. In other words, related information is stored in the associated nodes.
[0025] The storage location indicates where each piece of information associated with a node is stored. The storage location is, for example, a designated area in product DB201.
[0026] The display status indicates the display status of nodes in the correlation data management image displayed on the user terminal 500. Nodes with a "○" (○) display status are displayed in the correlation data management image, while nodes with a "×" (×) display status are not displayed in the correlation data management image. For example, when displaying according to the node management table 302 shown in Figure 3, the three nodes with a "○" display status and node names "Factory," "Line 1," and "Processing Machine 1" will be displayed in the correlation data management image. Nodes displayed in the correlation data management image function as folders, and users of the user terminal 500 can store files, etc., in each database of the storage device 2 via the displayed nodes. Furthermore, as will be described in detail later, users of the user terminal 500 can also display nodes that are not currently displayed on the correlation data management image by performing a specified operation, and then store files, etc., in each database of the storage device 2 via the displayed nodes.
[0027] Here, the management items are candidates for the coordinate axes when displaying the information group managed in the graph database in a multidimensional manner, and coordinate axes are assigned to the management items selected by the user. For example, if risk level, supply chain, and engineering chain are selected, the display processing unit 16 of the information management device 1 creates a correlated data management image in the following procedure. That is, the display processing unit 16 assigns the X axis to risk level, the Y axis to supply chain, and the Z axis to engineering chain. Then, the display processing unit 16 plots nodes on the space having the assigned axes.
[0028] The display processing unit 16 further draws lines (connection lines) indicating relationships between plotted nodes based on the source and relationship in the node management table 302. The source and relationship are information used to draw connection lines indicating relationships between nodes. The display processing unit 16 draws connection lines between each node in which a source is registered and the node registered as a source. For example, when creating a correlation data management image based on the node management table 302, since the source of the node named "Line 1" is "Factory", the display processing unit 16 draws a connection line between the node named "Factory" and the node named "Line 1" to indicate that these two nodes are related. Similarly, the display processing unit 16 draws connection lines between the node named "Line 1" and the node named "Processing Machine 1", between the node named "Processing Machine 1" and the node named "Instruction Manual", between the node named "Processing Machine 1" and the node named "Trouble Occurred...", and between the node named "Processing Machine 1" and the node named "Notes...". In addition, the display processing unit 16 draws connection lines between each node in which a relationship is registered and the node with the node number registered in the relationship. For example, when creating a correlation data management image based on the node management table 302, node numbers #012 and #013 are registered in the relationship of the node named "Instruction Manual," and node number #011 is registered in the relationship of the node named "Trouble Occurred..." and the relationship of the node named "Notes...." Therefore, the display processing unit 16 draws connection lines between the node named "Instruction Manual" and the node named "Trouble Occurred...", and between the node named "Instruction Manual" and the node named "Notes...".
[0029] Figure 4 shows an example of a correlation data management image displayed on the user terminal 500. Figure 4 shows an example of a correlation data management image displayed based on the node management table 302 shown in Figure 3.
[0030] When a correlation data management image like the one shown in Figure 4 is displayed, that is, when nodes are plotted on a three-dimensional coordinate system, the position of each node on the X, Y, and Z axes is dynamically determined based on the area in which the node is displayed and its relationship to other nodes. Here, the correlation data management image is linked to the node management table 302. For example, if a user changes the node name on the correlation data management image displayed on the user terminal 500, the node name on the node management table 302 is also changed. Furthermore, if the connection lines indicating the relationships between nodes in the correlation data management image are changed, the "source" and "relationship" in the node management table 302 are also changed according to the result of the change. In this way, users of the information management system 100 can edit the node management table 302 by making changes to the correlation data management image displayed on the user terminal 500.
[0031] Figure 5 shows another example of the correlation data management image displayed on the user terminal 500. Other features of the information management system 100 will be explained using Figure 5.
[0032] (Other features of the first feature) The information management system 100 changes the display manner of nodes shown in the correlation data management image based on the frequency of access to the nodes. For example, nodes with high access frequency are color-coded based on the access frequency. That is, the display color of the nodes is changed according to the access frequency. In the correlation data management image of Figure 5, the node named "Supplier" and the node named "Troubleshooting" have high access frequencies, and these nodes are color-coded differently from the other nodes. This makes it easy to identify nodes with high access frequency from among many nodes, and improves accessibility to necessary information (nodes with high access frequency). Note that the display manner to be changed is not limited to color scheme. The display position of the nodes may also be changed according to the access frequency, such as displaying the nodes in a highly visible location, for example, in the center of the screen. The display size of the nodes may also be changed according to the access frequency.
[0033] (Another second feature) The information management system 100 also displays nodes on the correlation data management image by freely overlaying them based on the relationships and origins of the nodes. That is, the information management system 100 is configured to display multiple nodes hierarchically, freely derived from a specific node, based on the "relationships" and "origins" of each node registered in the node management table. For example, when a specific node is specified by the user, the information management system 100 displays other nodes that have a relationship with the specified node in a hierarchical manner. In addition, since readability deteriorates as the node hierarchy deepens, the information management system 100 is configured to allow the user to redisplay nodes at a desired hierarchy. That is, if there are many nodes and it is difficult to view them, the number of nodes displayed can be reduced by displaying nodes overlaid only in a specific selection area specified by the user. In the correlation data management image of Figure 5, some nodes are displayed overlaid, targeting nodes related to the node named "Processing Machine 1" and nodes related to the node named "Processing Machine 2". Furthermore, to improve readability, the information management system 100 allows users to identify and select nodes that do not need to be displayed, or to identify and select areas where nodes that do not need to be displayed exist, and then hide the selected nodes.
[0034] (A third feature) Furthermore, when a user changes the display direction of the correlation data management image for a group of nodes currently being displayed using a predetermined method (e.g., a rotation function), the information management system 100 changes the management items assigned to the X, Y, and Z axes according to the result of the change in display direction. For example, if risk is assigned to the X axis, supply chain to the Y axis, and engineering chain to the Z axis, the information management system 100 can reassign supply chain to the X axis, risk to the Y axis, and engineering chain to the Z axis when the display direction of the correlation data management image is changed. In other words, a user can change the management items assigned to the X, Y, and Z axes of the correlation data management image by changing the display direction of the correlation data management image displayed on the user terminal 500.
[0035] Figure 6 is a diagram illustrating an example of how the information management system 100 according to Embodiment 1 displays the information it manages. Specifically, Figure 6 shows an example of how the information management system 100 displays a group of nodes hierarchically.
[0036] When a second node belongs to a first node, that is, when a second node originates from a first node, the information management system 100 switches between storing and displaying the second node belonging to the first node each time the first node included in the correlated data management image is clicked (left-clicked) by a user. For example, when the node named "Work" is clicked in the stored state shown in the upper part of Figure 6 (Step 1), the information management system 100 expands and displays the node named "Supplier" and the node named "Notes..." that are stored in this node (Step 2). Also, when the node named "Work" is clicked in the expanded state shown in the lower part of Figure 6, the information management system 100 hides the node named "Supplier" and the node named "Notes..." and returns to the stored state shown in the upper part of Figure 6. The operation is similar when the node named "Processing Machine 1", the node named "Processing Machine 2", etc. are clicked.
[0037] The information management system 100 does not switch between storing and displaying a node if a node to which no other nodes belong, that is, a node to which no other nodes to be displayed are stored, is clicked by a user.
[0038] Furthermore, when a node is double-clicked by a user, the information management system 100 displays the information belonging to the double-clicked node. For example, if a node named "Processing Machine 2" is double-clicked, the specifications of the processing machine (specifications information of processing machine 2) will be displayed.
[0039] Furthermore, the expansion and storage of nodes stored in a given node may be performed in multiple steps (multi-stages). A specific example of the case where the expansion of nodes stored in a given node is performed in multiple stages will be explained. For example, suppose that another node (third node) is stored in the node named "Supplier" (second node), which is stored in the node named "Work" (first node) as shown in Figure 6. In this case, when the first node, which is currently storing the second node, is clicked, the information management system 100 expands and displays the second node, but does not expand the third node (it remains stored in the second node). If the second node is clicked again in this state, the information management system 100 expands and displays the third node.
[0040] Next, the overall operation of the information management system 100 will be explained using Figures 7 and 8. Figure 7 is a flowchart showing an example of the overall operation of the information management system 100 according to Embodiment 1. Specifically, the flowchart in Figure 7 shows an example of the operation of creating a node management table by the information management device 1 of the information management system 100 and storing data in each database held by the storage device 2. The creation of the node management table and the storage of data in the database are performed by the management table creation unit 15. In addition, the information set in the node management table and the data stored in the database are acquired from the outside by the management table setting information acquisition unit 14 via the input / output unit 20. Figure 8 is a first diagram showing an overview of the operations that a user performs on the information management system 100 according to Embodiment 1, and specifically shows an overview of the operations performed on the information management system 100 that execute the operations shown in Figure 7.
[0041] The operation shown in FIG. 7 is started, for example, when a user logs in to the information management system 100 with an account name assigned to the user (operation 601 in FIG. 8). After starting the operation, the management table creation unit 15 checks whether or not an installation operation for a parent node has been detected (step S11). That is, the management table creation unit 15 checks whether or not the installation operation for the parent node (operation 611 in FIG. 8) has been performed by the user. When an installation operation for a parent node is not detected (step S11: No), the management table creation unit 15 repeats the processing of step S11 until an installation operation for a parent node is detected.
[0042] When installation of a parent node is detected (step S11: Yes), the management table creation unit 15 sets the name and number of the parent node in the node management table (step S12). The name of the parent node is determined by the user. The management table creation unit 15 sets the name of the parent node determined by the user as the "node name" in the node management table. The management table setting information acquisition unit 14 acquires the name of the parent node determined by the user from the user terminal 500. The management table creation unit 15 determines the number of the parent node. That is, the management table creation unit 15 determines a unique number for the installed parent node and sets the number as the "number" in the node management table.
[0043] Next, the management table creation unit 15 checks whether or not an operation to store data in the parent node has been detected (step S13). That is, the management table creation unit 15 checks whether or not an operation to store data in the parent node has been performed by the user. When an operation to store data in the parent node is not detected (step S13: No), the management table creation unit 15 executes step S16 described later.
[0044] When an operation to store data in the parent node is detected (step S13: Yes), the management table creation unit 15 associates a data storage destination (address) with the parent node, and sets information of this storage destination as the "storage destination" in the node management table (step S14).
[0045] Next, the management table creation unit 15 stores data in the data storage destination associated with the parent node (step S15).
[0046] Next, the management table creation unit 15 extracts management items to be managed in association with the parent node, and sets the extracted management items in the node management table (step S16). Specifically, the management table creation unit 15 detects an input operation of a management item to be managed in association with the parent node (operation 612 in FIG. 8), extracts the input management item, and sets it in the node management table.
[0047] Next, the management table creation unit 15 checks whether an installation operation for a child node has been detected (step S17). Specifically, the management table creation unit 15 checks whether the installation operation for a child node (operation 621 in FIG. 8) has been performed by the user. If the installation operation for a child node is not detected (step S17: No), the management table creation unit 15 ends the operation.
[0048] If the installation operation for a child node is detected (step S17: Yes), the management table creation unit 15 sets the name and number of the child node in the node management table (step S18). The name of the child node is determined by the user. The management table creation unit 15 sets the name of the child node determined by the user to the "node name" field of the node management table. The management table setting information acquisition unit 14 acquires the name of the child node determined by the user from the user terminal 500. The number of the child node is determined by the management table creation unit 15. Specifically, the management table creation unit 15 determines a unique number for the installed child node and sets it in the "number" field of the node management table.
[0049] Next, the management table creation unit 15 checks whether an operation for storing data in a child node has been detected (step S19). Specifically, the management table creation unit 15 checks whether the operation of storing data in a child node has been performed by the user. If the operation of storing data in a child node is not detected (step S19: No), the management table creation unit 15 executes step S22 which will be described later.
[0050] If the operation of storing data in a child node is detected (step S19: Yes), the management table creation unit 15 associates the data storage address with the child node, and sets the information of this storage address to the "storage address" field of the node management table (step S20).
[0051] The management table creation unit 15 then stores the data in the data storage location associated with the child node (step S21).
[0052] The management table creation unit 15 then detects connection lines between nodes and sets the source and relationship in the node management table (step S22). That is, the management table creation unit 15 detects the input operation (operation 622 in Figure 8) of a connection line connecting any two nodes among the installed nodes (parent node or child node), and sets the source and relationship in the node management table according to the input result of the connection line. After executing step S22, the management table creation unit 15 returns to step S17 and continues its operation.
[0053] By following the above procedure, a node management table can be created that serves as the basis for displaying the correlated data management image. This allows users to store files and other data in the installed nodes (parent nodes and child nodes), and to read and use files and other data from the nodes. The files and other data stored in the nodes can be, for example, document files, image files, audio files, etc., but the data format can also be HTML (HyperText Markup Language), and the type of file is not restricted.
[0054] Next, the operation of setting detailed information for nodes managed by the information management system 100 will be explained using Figures 9 to 11. Figure 9 is a flowchart showing an example of the operation by which the information management system 100 according to Embodiment 1 sets detailed information for nodes. Specifically, the flowchart in Figure 9 shows an example of the operation by which the information management device 1 of the information management system 100 sets detailed information for nodes in the node management table. Figure 10 is a second diagram showing an overview of operations performed by a user on the information management system 100 according to Embodiment 1, and specifically shows an overview of the operation procedure performed on the information management system 100 that executes the operation shown in Figure 9. Figure 11 is a third diagram showing an overview of operations performed by a user on the information management system 100 according to Embodiment 1, and specifically shows an overview of the operation procedure performed on the information management system 100 that executes the operation shown in Figure 9. The process of setting detailed node information in the node management table is performed by the management table creation unit 15. In addition, detailed node information is acquired from the outside by the management table setting information acquisition unit 14 via the input / output unit 20.
[0055] The management table creation unit 15 detects the start operation for setting information to a node (step S31) and checks whether a specific node has been selected (step S32). For example, if the management table creation unit 15 detects that the user has performed the operation shown in the upper part of Figure 10, that is, the operation of selecting one node as the target for setting information and selecting detailed settings from multiple operation menus (operation 711), it determines that a specific node has been selected. The management table creation unit 15 also detects that the user has performed the operation shown in the upper part of Figure 11, that is, the operation of selecting all nodes as the target for setting information and selecting detailed settings from multiple operation menus (operation 721), it determines that a specific node has not been selected.
[0056] If a specific node is selected (Step S32: Yes), the management table creation unit 15 displays the detailed information setting screen for the specific node on the user terminal 500 (Step S33) and accepts the operation to set the detailed information (Operation 712 in Figure 10) (Step S35).
[0057] If no specific node is selected (Step S32: No), the management table creation unit 15 displays a detailed information setting screen for the entire node management table on the user terminal 500 (Step S34) and accepts the operation to set the detailed information (Operation 722 in Figure 11) (Step S35).
[0058] After receiving a detailed information setting operation for a specific node in step S35, or after receiving a detailed information setting operation for the entire node management table, the management table creation unit 15 updates the node management table according to the received operation (step S36).
[0059] Detailed information is set for each node using the above procedure. After this setting is complete, the information management system 100 provides the user with the information set for the managed node in response to the user's request. That is, the user can view the information stored in the node by performing a predetermined operation via the user terminal 500. For example, when a user clicks on a node in the correlated data management image displayed on the user terminal 500, the information management device 1 displays the information stored in the clicked node (e.g., equipment manual) on the user terminal 500. The information management device 1 may update the node management table by directly writing the detailed information into the node management table, or it may update the node management table by writing an address such as a URL (Uniform Resource Locator) of the detailed information into the node management table.
[0060] Next, the operation of the information management device 1 to modify the node management table will be explained using Figures 12 to 14. Here, as an example, the operation to change the node name and relationship registered in the node management table will be explained. Figure 12 is a flowchart showing an example of the operation of the information management device 1 to modify the node management table according to Embodiment 1. Figure 13 is a diagram showing an example of the operation procedure for changing the node name registered in the node management table. Figure 14 is a diagram showing an example of the operation procedure for changing the relationship registered in the node management table.
[0061] The management table creation unit 15 first detects a user's operation to rename a node (step S41). For example, the management table creation unit 15 detects the operations shown in Figure 13, namely, the operation of selecting a node to rename and selecting rename from a set of operation menus (operation 811 in Figure 13) and the operation of changing the node's name (operation 812 in Figure 13).
[0062] The management table creation unit 15 then detects an operation by the user to change the relationships between nodes (step S42). For example, the management table creation unit 15 detects the operations shown in Figure 14, namely, the operation of selecting a connection line that indicates the relationship between nodes and selecting the relationship change menu (operation 911 in Figure 14) and the operation of changing the destination node of the selected connection line (operation 912 in Figure 14).
[0063] The management table creation unit 15 then updates the node management table according to the change operations detected in steps S41 and S42 (step S43).
[0064] Next, the operation of the information management system 100 to display a correlation data management image on the user terminal 500 will be explained using Figures 15 and 16. Figure 15 is a flowchart showing an example of the operation of the information management device 1 when the information management system 100 according to Embodiment 1 displays a correlation data management image on the user terminal 500. Figure 16 is a diagram showing an overview of the operations performed by the user when the correlation data management image is displayed on the user terminal 500.
[0065] When the information management device 1 detects that the operation 1001 shown in Figure 16 has been performed, it executes the processes shown in steps S51 to S56 in Figure 15 and displays a correlation data management image on the user terminal 500. In the operation 1001 shown in Figure 16, a node that will be the starting point for displaying the correlation data management image is selected. In the example shown in Figure 16, the node named "Factory" is selected as the starting point for display, and as a result, the node selected as the starting point for display (hereinafter referred to as the starting point node) and nodes related to the starting point node are displayed in a multidimensional correlation data management image. Here, the starting point node is located at the highest level among the group of nodes displayed as the correlation data management image. That is, nodes higher than the starting point node are not displayed as part of the correlation data management image. For example, if the node named "Line" is selected as the starting point node in the operation 1001 shown in Figure 16, the node named "Factory" is a higher-level node than the starting point node and is therefore not displayed as part of the correlation data management image. Nodes below the display starting node are nodes that are related to the display starting node (nodes displayed as the correlation data management image). The display starting node corresponds to the parent node in the correlation data management image.
[0066] When the information management device 1 detects that the display starting node of the correlation data management image has been selected, it checks the previous display state of the correlation data management image (step S51). Specifically, the display processing unit 16 refers to the node management table and checks whether each node related to the display starting node (sub-nodes of the display starting node) is displayed or not.
[0067] The information management device 1 then checks the management items on the display area (step S52). Specifically, the display processing unit 16 checks the management items to be displayed in the correlated data management image. The user may specify in advance which management items to display in the correlated data management image, or the user may be asked in step S52, for example, a menu screen may be displayed on the user terminal 500 to allow the user to select the management items to be displayed.
[0068] The information management device 1 then checks the management items of the nodes to be displayed (step S53). Specifically, the display processing unit 16 refers to the node management table and checks the management items to be displayed in the correlation data management image for nodes where "○" is set for "Display availability".
[0069] The information management device 1 then determines the placement of each node within the display area based on the position of the parent node to be displayed, the number of nodes to be displayed, and the management items associated with the nodes to be displayed (step S54). The position of the parent node may be predetermined, such as at the center of the display area, or the user may be allowed to decide where within the display area it should be. In step S54, the display processing unit 16 determines the placement (display position) of each node within the display area (display position) using, for example, the following procedure. The display processing unit 16 arranges all nodes, including the parent node, so that the distance between adjacent nodes becomes uniformly close. At this time, the management items associated with each node are taken into consideration. For example, if the coordinate axes displayed in the correlation data management image are the X-axis, Y-axis, and Z-axis, and the management items assigned to these axes are "risk level," "supply chain," and "engineering chain," then the display processing unit 16 places the nodes associated with "risk level" and "supply chain" on a plane including the X-axis and Y-axis (positions where the Z-axis component is 0). The display processing unit 16 may further determine the arrangement by considering that related nodes are close together. The relationships between data stored in each node become relatively stronger or weaker depending on the selected viewpoint (corresponding to the axes in the correlation data management image). Determining the strength of these relationships is difficult by managing them only in a two-dimensional table, but it becomes easier by adjusting the distance between data in three dimensions. In other words, by using the correlation data management image, it is possible to easily grasp the changing relationships between data from the selected viewpoint. For example, by changing the viewpoint, the number of nodes connected to the node of interest increases or decreases. Note that the relative strength or weakness of relationships between data means that the relative strength of data relationships changes depending on the combination of viewpoints selected.
[0070] The information management device 1 then displays the nodes based on the arrangement decision (step S55) and displays the connection lines between the nodes (step S56). That is, the display processing unit 16 displays each node in the display area according to the arrangement decided in step S54, and further displays connection lines between related nodes according to the settings of "source" and "relationship" in the node management table. In practice, the user terminal 500 displays the correlation data management image, so the display processing unit 16 creates display data to display the correlation data management image on the user terminal 500 and sends it to the user terminal 500. The user terminal 500 displays the correlation data management image using the received display data. This makes it possible to organize the complex relationships between the data stored in each node along a desired axis and view those relationships at a glance.
[0071] Next, other characteristic operations of the information management system 100 will be described. After displaying the correlation data management image on the user terminal 500, the information management system 100 changes the display according to the operations performed by the user on the correlation data management image. For example, if the user rotates the displayed correlation data management image, the information management system 100 rotates the correlation data management image displayed on the user terminal 500. This operation will be explained using Figures 17 to 19.
[0072] Figure 17 is a flowchart showing an example of an operation in which the information management system 100 according to Embodiment 1 changes the correlation data management image displayed on the user terminal 500. Each of the processes in steps S61 to S67 shown in Figure 17 is executed by the display processing unit 16 of the information management device 1.
[0073] The display processing unit 16 of the information management device 1 detects the rotation angle of the node objects included in the correlation data management image when the user terminal 500 is displaying the correlation data management image (step S61), and checks whether the rotation angle is greater than or equal to a predetermined threshold (step S62). The threshold for the rotation angle is, for example, 90 degrees. The user rotates the node objects by operations such as drag and drop. The system may also be configured so that the user can freely change the setting of the rotation angle threshold.
[0074] If the detected rotation angle is less than the threshold (step S62: No), the display processing unit 16 executes step S61 again to re-detect the rotation angle of the node object.
[0075] If the detected rotation angle is greater than or equal to a threshold (step S62: Yes), the display processing unit 16 slides the currently displayed management item from the node management table according to the rotation direction (step S63). Specifically, the display processing unit 16 slides the management items assigned to each of the coordinate axes displayed in the correlation data management image on the node management table according to the rotation direction of the node object. The display processing unit 16 slides the corresponding display item (currently displayed management item) in the node management table shown in Figure 18 in the direction indicated by the arrow, changing the position of each management item in the node management table. For example, if the node object included in the correlation data management image shown in Figure 19 is rotated in the direction indicated by the arrow, the display processing unit 16 slides the management items "Supply Chain," "Engineering Chain," and "Risk Level" assigned to each coordinate axis within the node management table. Figure 18 is a first diagram illustrating the operation of changing the correlation data management image displayed on the user terminal 500 by the information management system 100 according to Embodiment 1, and Figure 19 is a second diagram illustrating the operation of changing the correlation data management image displayed on the user terminal 500 by the information management system 100 according to Embodiment 1.
[0076] The display processing unit 16 then checks the node management table after sliding the management items (step S64), and determines the placement of each node within the display area based on the position of the parent node to be displayed, the number of nodes to be displayed, and the management items associated with the nodes to be displayed (step S65). This step S65 is the same process as step S54 in Figure 15 described above.
[0077] The display processing unit 16 then displays the nodes based on the arrangement determination result (step S66) and displays the connection lines between the nodes (step S67). Steps S66 and S67 are the same processes as steps S55 and S56 in Figure 15 described above.
[0078] Furthermore, the user may be allowed to directly specify the rotation angle. For example, when the information management system 100 detects that a predetermined operation has been performed, it may display a rotation angle selection menu (rotate 90 degrees around axis XX, rotate 180 degrees around axis YY, etc.) on the user terminal 500 and allow the user to specify the rotation direction and rotation angle from the options.
[0079] Here, the management items in the node management table are set so that items with similar attributes are placed next to each other. Therefore, by rotating the correlation data management image, users can slide the displayed management items and display other management items with similar attributes. If a user wants to significantly change the displayed items, they can, for example, rotate the correlation data management image 180 degrees to skip adjacent management items and display management items from a different perspective. When rotating the correlation data management image, the rotation is around the axis that represents the management items, so the information management system 100 slides the management items relative to the management items on the rotation axis according to the rotation angle. However, for some users, the desired management items may not be displayed even after rotation. In that case, the user sets the management items using a pull-down menu. When the displayed management items are changed by user operation, the arrangement of management items is changed so that the management items displayed at that time are the management items with similar attributes to the user.
[0080] As explained above, the information management system 100 displays the information it manages and the associated node groups in a multidimensional manner, thereby improving user accessibility to the information they need. Furthermore, the information management system 100 displays connection lines indicating relationships between nodes associated with related information, making it easy for users to understand the relationships between the managed pieces of information.
[0081] Embodiment 2. This embodiment describes an example of applying the information management system 100 described in Embodiment 1. Figure 20 shows an example of applying the information management system 100 to a production system.
[0082] In the application example shown in Figure 20, the information management device 1 acquires production information from the production management device 3 of the production system, including operational information of OT equipment, production results, defect information, worker work history, and information entered by workers via terminal devices, and stores the acquired production information in the product DB 201 or factory OTDB 203. In other words, when the production management device 3 acquires production information, it transmits it to the information management device 1 in real time. When the information management device 1 acquires production information from the production system, it creates a production information management table 303 to manage the acquired production information in association with nodes in the node management table 302, and stores the acquired production information in the product DB or factory OTDB 203. The production information management table 303 consists of "production information" indicating production results (quantity), production time (start time, end time), errors that occurred on the production line, "production information acquisition source" indicating the source of the production information, and "node name" indicating the node to which the production information is associated.
[0083] Furthermore, if a user wishes to use the production information stored in each database (product DB 201 and factory OTDB 203), the information management device 1 displays a correlated data management image on the user terminal 500.
[0084] When the information management device 1 is displaying the correlation data management image on the user terminal 500, it acquires production information from the production management device 3 and stores it in the corresponding database (product DB 201 or factory OTDB 203), and then notifies the user. That is, when the information management device 1 acquires production information, it changes the display mode of the node corresponding to the acquired production information among the nodes that make up the currently displayed correlation data management image, based on the node management table 302. For example, the information management device 1 changes the color scheme of the node corresponding to the acquired production information. Also, if the production information stored in the node contains error information, the information management device 1 changes the display mode of the node based on the error information to make it easier to distinguish it from nodes that do not have error information stored. The display mode, such as the display color, may be changed according to the number of errors and the content of the errors. Furthermore, the information management device 1 may display statistical data of the acquired production information when a node that makes up the correlation data management image is clicked (right-clicked) by the user. The statistical data of the production information is calculated by statistically analyzing the production information stored in the node. When displaying statistical data on production information, the information management device 1, for example, displays a function selection menu when the node containing the production information of the processing machine 1 (the node named "Processing Machine 1") is right-clicked. Furthermore, when statistical analysis is selected from the displayed menu, the production information stored in the node is analyzed. The statistical analysis is performed by the information management unit 12. Examples of statistical data include changes in production volume over time, production volume per unit time, and error frequency. In other words, the node also serves as an interface for providing data to external parties.
[0085] As explained above, in the information management system 100, the information management device 1 generates a correlation data management image that displays each node associated with each piece of information to be managed in a multidimensional manner, and displays it on the user terminal 500. This allows each piece of production information acquired from the production system to be displayed to the user along with its relationships with other pieces of production information. By viewing the correlation data management image, the user can understand the acquisition status of production information (what kind of information is being collected and to what extent) and the relationships between the acquired production information based on the connection status of the nodes. In other words, the information management system 100 improves the accessibility of information for users. Furthermore, it allows workers to easily understand the circumstances of troubles that occurred during past work.
[0086] Here, we will explain how to use the information management system 100. Figure 21 is a diagram showing an example of how to use the information management system 100 according to Embodiment 1. With the information management system 100, for example, as shown in Figure 21, a user can view a correlation data management image using VR (Virtual Reality) goggles. In addition, the user can rotate the correlation data management image they are viewing using gestures and change the information that can be viewed in the correlation data management image.
[0087] Next, we will describe the hardware that realizes the information management device 1 of the information management system 100.
[0088] Figure 22 shows an example of hardware that realizes the information management device 1. The information management device 1 can be realized by the processor 91, memory 92, and communication interface 93 shown in Figure 22. An example of the processor 91 is a CPU (Central Processing Unit, also called a central processing unit, processing unit, arithmetic unit, microprocessor, microcomputer, or DSP (Digital Signal Processor)) or a system LSI (Large Scale Integration). An example of the memory 92 is a non-volatile or volatile semiconductor memory such as RAM (Random Access Memory), ROM (Read Only Memory), flash memory, or magnetic disk.
[0089] The data processing unit 10 of the information management device 1, namely the detailed information setting unit 11, the information management unit 12, the account management unit 13, the management table setting information acquisition unit 14, the management table creation unit 15, and the display processing unit 16, are realized by the processor 91 executing information management programs for each of these units. The information management programs for the detailed information setting unit 11, the information management unit 12, the account management unit 13, the management table setting information acquisition unit 14, the management table creation unit 15, and the display processing unit 16 are pre-stored in the memory 92. The processor 91 reads the information management programs from the memory 92 and executes them, thereby operating as the detailed information setting unit 11, the information management unit 12, the account management unit 13, the management table setting information acquisition unit 14, the management table creation unit 15, and the display processing unit 16.
[0090] The memory 92 holds the information management program executed by the processor 91 and is also used as temporary memory when each part of the data processing unit 10 performs various processes.
[0091] The input / output unit 20 of the information management device 1 is implemented by the communication interface 93.
[0092] The above information management program is assumed to be pre-stored in memory 92, but is not limited to this. The above information management program may be supplied to the user in a state where it is written on a recording medium such as a CD (Compact Disc)-ROM or DVD (Digital Versatile Disc)-ROM, and the user may install it in memory 92. Alternatively, the above information management program may be provided to the user via a network such as the Internet.
[0093] In the above embodiment, an example was described in which the node management table is created and modified by the user performing operations such as placing objects in a predetermined area. However, the configuration may also be such that the node management table is created by the user directly inputting the necessary information. In other words, the information management device 1 may acquire the information to be set in the node management table (various information necessary to display the correlation data management image) by any means.
[0094] The configurations shown in the above embodiments are merely examples, and it is possible to combine them with other known technologies, combine different embodiments, and omit or modify parts of the configuration without departing from the gist of the invention.
[0095] For example, the information management system 100 may have a configuration that further includes the following features.
[0096] The information management system 100 displays connection lines between nodes based on the relationships set in the node management table, but it may also display connection lines based on other information. For example, it may display connection lines between nodes based on causal relationships between nodes. That is, it may display connection lines indicating relationships between nodes that have a causal relationship. It may also display connection lines between nodes based on the relationships of the information stored in the nodes. That is, it may display connection lines indicating relationships between nodes that store related information. It may also display connection lines between nodes based on the access history of the nodes. That is, it may display connection lines indicating relationships between nodes that are frequently accessed consecutively.
[0097] Furthermore, while the information management system 100 selects the nodes to display in the correlated data management image based on the order of the nodes set in the node management table, it is not limited to this, and may also select the nodes to display in the correlated data management image based on the access history to the nodes and the importance of the information stored in the nodes.
[0098] Furthermore, if there are nodes that are accessed infrequently, the information management system 100 may remove the connection lines in the correlation data management image that indicate the relationship between those nodes and other nodes. This hides unnecessary relationships (connection lines) between nodes, improving the readability of the relationships between nodes.
[0099] Furthermore, although the information management system 100 stores information for each node, it may also be possible to enable the transfer of information between nodes via connection lines between nodes.
[0100] Furthermore, the information management system 100 may change the color scheme of nodes included in the correlation data management image depending on the relationship between the nodes. For example, nodes that are related may be displayed in the same color.
[0101] Furthermore, the information management system 100 may also display the relationships between nodes in the correlation data management image by using the color scheme and intensity of the colors of the nodes. This eliminates the need to display connection lines.
[0102] Furthermore, the information management system 100 may indicate relationships between nodes in the correlation data management image by the distance between them. For example, nodes that have a relationship may be displayed closer together. This eliminates the need to display connecting lines to indicate relationships.
[0103] Furthermore, the information management system 100 may change the thickness of the connection lines between nodes in the correlation data management image according to the strength of the relationship between the nodes. For example, the thickness of the connection lines may be changed so that the connection lines between nodes with a strong relationship are thicker than the connection lines between nodes with a weak relationship.
[0104] Furthermore, the information management system 100 may change the display shape of the node (e.g., circle, triangle, square, or circle, or an icon) in the correlated data management image depending on the type of information associated with the node.
[0105] Furthermore, the information management system 100 may change the display size of nodes in the correlated data management image according to the importance of the information associated with the node.
[0106] 1 Information management device, 2 Storage device, 3 Production management device, 10 Data processing unit, 11 Detailed information setting unit, 12 Information management unit, 13 Account management unit, 14 Management table setting information acquisition unit, 15 Management table creation unit, 16 Display processing unit, 20 Input / output unit, 21 Operation reception unit, 100 Information management system, 201 Product database, 202 Management information database, 203 Factory operational technology database, 301 Account management table, 302 Node management table, 303 Production information management table, 500 User terminal.
Claims
1. An information management device comprising: a management table creation unit that creates a node management table in which nodes where managed information is stored, management items indicating the attributes of the information, and the storage location of the information are registered; an information management unit that manages the information based on the node management table; and a display processing unit that displays the nodes in a multidimensional manner on a display unit based on management items selected from the management items and the node management table.
2. The information management device according to claim 1, characterized in that the display processing unit assigns the selected management items to coordinate axes and displays the nodes in a space having the coordinate axes.
3. The information management device according to claim 1 or 2, characterized in that the relationship between the node and other nodes is registered in the node management table, and the display processing unit displays connection lines between related nodes based on the node management table.
4. The information management device according to claim 3, characterized in that the display processing unit changes the display mode of the connection lines based on the strength of the relationship between the nodes to be displayed.
5. The information management device according to any one of claims 1 to 4, characterized in that when the display processing unit detects that a user has performed an operation to change the content displayed on the display unit, it modifies the node management table based on the content of the operation performed by the user.
6. The information management device according to any one of claims 1 to 5, characterized in that the display processing unit changes the display mode of the node based on the frequency of user access to the node.
7. The information management device according to any one of claims 1 to 5, characterized in that the display processing unit changes the display mode of the nodes based on the strength of the relationship between the nodes to be displayed.
8. The information management device according to any one of claims 1 to 5, characterized in that the display processing unit changes the display mode of the node based on the importance of the information stored in the node.
9. The information management device according to any one of claims 1 to 8, characterized in that the source of the information stored in each of the nodes is registered in the node management table, and the display processing unit displays the nodes hierarchically based on the source.
10. The information management device according to any one of claims 1 to 9, characterized in that the display processing unit changes the display direction of the node displayed on the display unit in accordance with user operation.
11. The information management device according to claim 10, characterized in that when the display processing unit changes the display direction of the nodes displayed on the display unit, it updates the display showing the arrangement of the nodes displayed on the display unit and the relationships between the nodes based on the result of the change.
12. The information management device according to any one of claims 1 to 11, characterized in that the information subject to management is production information collected at the factory.
13. The information management device according to claim 12, wherein the production information includes production results, production time, and error information, and the display processing unit, when a node displayed on the display unit is selected and a predetermined operation is performed, displays the production information stored in the selected node on the display unit.
14. The information management device according to claim 13, characterized in that the display processing unit causes the statistical data of the production information to be displayed on the display unit.
15. An information management system comprising: an information management device according to any one of claims 1 to 14; a storage device for holding the node management table and the information; and a user terminal having a display unit for displaying the nodes in a multidimensional manner.
16. An information management method characterized by comprising: a first step of creating a node management table in which nodes where managed information is stored, management items indicating the attributes of the information, and the storage location of the information are registered; a second step of managing the information based on the node management table; and a third step of displaying the nodes in a multidimensional manner on a display unit based on management items selected from the management items and the node management table.
17. An information management program characterized by causing a computer to perform the following steps: a first step of creating a node management table in which nodes where managed information is stored, management items indicating the attributes of the information, and the storage location of the information are registered; a second step of managing the information based on the node management table; and a third step of displaying the nodes in a multidimensional manner on a display unit based on management items selected from the management items and the node management table.