System and program

Abstract

To provide an information collection display system and program that reduce the capacity of a storage device of the system and facilitates analysis of site data.SOLUTION: An information collection display system 1 in which a data generation device 5 that generates site data 100 and a transaction data accumulation section 4 that stores the site data are connected, includes: a relevance data accumulation section 15 that stores relevance data 200 for defining relevance of each of a plurality of pieces of information included in the site data; a relevance data retrieval section 12 that retrieves second information relevant to first information included in the plurality of pieces of information on the basis of the relevance data; and a user interface 7 that displays connection relation of the plurality of pieces of information associated by the relevance data. The relevance data retrieval section 12 retrieves the second information relevant to the first information displayed on the user interface 7 and displays the first information and the second information together with the connection relation of the plurality of pieces of information on the user interface 7.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a data structure and an information collection system. [Background technology]

[0002] Conventionally, in factories and offices in the manufacturing industry, there are many tasks that constitute the manufacturing process when manufacturing finished products. In each task that constitutes the manufacturing process, on-site data is generated and collected when the task is completed or a specified event occurs, and the work efficiency of each task is optimized by analyzing this on-site data. On the other hand, when the departments that manage each task are different, it becomes difficult to share information between the departments, and improvements to problems that cross departments (tasks) are not progressing. One of the reasons why improvements to problems that cross departments (tasks) are not progressing is that each department uses a different system to manage the tasks, and the management system is not unified. In addition, each department analyzes the collected on-site data to optimize the work efficiency within the department, so if an overall optimization of a series of manufacturing processes is sought, the efficiency of the own department may decrease, which may result in a lower evaluation of the department.

[0003] However, in the manufacturing industry, cooperation between departments is essential to improve the production efficiency of the entire manufacturing process as we move from mass production to small-lot, high-mix production. In order to promote cooperation between departments, there is no other way than to present problems using factual data (factual information) that can be used by all departments to analyze the problems in common, and it is believed that cooperation between departments can be promoted by presenting the on-site data managed by one department in relation to the on-site data managed by other departments.

[0004] Patent Document 1 discloses an information collection system that can easily and efficiently collect various on-site data and supplementary information for each manufacturing process from the perspective of traceability, without the need to configure links between databases.

[0005] Moreover, Patent Document 2 discloses a production management device that can manage traceability data for each individual workpiece without using ID tags and can easily identify traceability data from defective products. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2015-153196 A [Patent Document 2] JP 2017-102548 A Summary of the Invention [Problem to be solved by the invention]

[0007] However, the system described in Patent Document 1 requires that all related data be stored in a database as supplementary information, and therefore requires a database with a huge storage capacity, resulting in high equipment and maintenance costs. Furthermore, unless the user himself understands the data structure of the data stored in the database, he or she cannot obtain the desired data.

[0008] In addition, in the technology described in Patent Document 2, the data generating device that generates the on-site data is limited to a specific device, making it difficult to associate all the on-site data collected or generated in a series of manufacturing processes. Also, although an identifier is attached to the collected on-site data, it only shows the association between the finished product and the parts corresponding to the finished product, and does not show how to associate and display the on-site data in a series of manufacturing processes, making it difficult to effectively utilize the collected on-site data.

[0009] Therefore, the present invention has been made with attention to the above-mentioned problems, and aims to reduce the capacity of the storage device that stores the association data by accumulating and managing the minimum amount of information required to associate business information and business-related information contained in the field data as association data, and to facilitate analysis of field data at each field by using this association data to search for and display specific first information and second information related to the first information. [Means for solving the problem]

[0010] In one aspect of the present invention for solving the above problem, in a system including a processing unit that processes on-site data that is set or generated each time a plurality of tasks included in a process are performed, and a storage unit that stores data processed by the processing unit, the data structure of relationship data is data that defines a relationship between each of a plurality of items of information used by the process, the data structure including a task node representing task data, a part node that is one or more input data when a task related to a specific task node among the plurality of tasks is performed, and a finished product node that is one or more output data when the task is performed, wherein a subsequent task node among the plurality of tasks is defined to use the finished product node output by the previous task node as the part node, the finished product node includes an output identifier that is an identifier for each unit or for each lot, the part node includes an input identifier using the output identifier assigned to the finished product node output by the previous task that is used as the part node, and when the output identifier of a first task node among the plurality of tasks matches the input identifier of a second task node, the first task node is the previous task of the second task node.

[0011] According to the above aspect, the minimum amount of information required to associate multiple pieces of information contained in the site data is accumulated and managed as association data, thereby making it possible to reduce the capacity of the storage device for storing the association data, and by using this association data to search for and display specific first information and second information related to the first information, it becomes possible to easily analyze the site data at each site. Effect of the Invention

[0012] The present invention allows for easy analysis of field data. [Brief description of the drawings]

[0013] [Figure 1] 1 is a diagram for explaining the connection relationship between an information collecting and displaying system according to an embodiment, a data generating device, and each storage unit that stores actual data. [Diagram 2] FIG. 2 is a block diagram illustrating functions of the information collecting and displaying system. [Diagram 3] FIG. 2 is a diagram illustrating an example of a data structure of relationship data. [Figure 4] 10 is a diagram illustrating an example of a structure of definition information created by a relevance data model creating unit. FIG. [Diagram 5] FIG. 13 is a diagram illustrating an example of a structure of definition information according to another embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of nodes connected based on connection information. [Figure 7] FIG. 2 is a diagram illustrating an example of configuration information of on-site data. [Figure 8] 11 is a diagram illustrating an example of a connection relationship between pieces of information constituting definition information after being connected by connection information. FIG. [Figure 9] This is an example of relational data in which each piece of definition information is specifically related to each other by relational information. [Figure 10] This is an example of relational data in which each piece of definition information is specifically related to each other by relational information. [Figure 11]FIG. 2 is a schematic diagram illustrating only the connection relationships of each piece of information in the association data. [Figure 12] FIG. 13 is a diagram for explaining only the connection relationships of each piece of information constituting association data according to another embodiment. [Figure 13] FIG. 13 is a diagram illustrating a connection relationship between each piece of information constituting association data according to another embodiment. [Figure 14] 13 is a diagram illustrating an example of a model data creation screen displayed by a relevance data model creation unit. FIG. [Figure 15] FIG. 13 is a diagram showing the state in which the display has been switched from the business property screen to the 4M property screen on the node definition information sub-screen. [Figure 16] 10 is a flowchart illustrating a process flow up to the point where related data is registered in a related data storage unit. [Figure 17] 10 is a flowchart illustrating a process flow up to the point where related data is registered in a related data storage unit. [Figure 18] 13 is a flowchart of a process for generating and registering 4M information by a related data registration unit. [Figure 19] 13 is a flowchart of a process of extracting relational data in a relational data search unit. [Figure 20] 13 is a flowchart of a process for storing user-defined data in a relationship data storage unit. [Figure 21] 13 is a flowchart of a data analysis process performed by a data analysis tool based on a data mart. [Figure 22] 13 is a flowchart of a generation process of analysis data by a data provision API unit. [Figure 23] FIG. 13 is a diagram illustrating an example of a data extraction tool displayed on a user interface. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, an information collecting and displaying system 1 according to an embodiment of the present invention will be described with reference to the drawings. In this embodiment, the information collecting and displaying system 1 will be described as an example applied to a system that collects and displays on-site data generated in each manufacturing process in a manufacturing factory.

[0015] [Overall configuration] FIG. 1 is a diagram for explaining the connection relationship between an information collecting and displaying system 1, a data generating device 5, and storage units 3 and 4 that store actual data.

[0016] As shown in Fig. 1, an information collecting and displaying system 1 is connected to a network 2. A plurality of data generating devices 5a, 5b, 5c (hereinafter, when the data generating devices 5a, 5b, 5c are not particularly distinguished from each other, they will be simply referred to as data generating devices 5) that collect or generate actual data, a master data storage unit 3, and a transaction data storage unit 4 that stores actual data (hereinafter, referred to as on-site data 100) are connected to the network 2, and these data generating devices 5, master data storage unit 3, and transaction data storage unit 4 are connected to the information collecting and displaying system 1 via the network 2.

[0017] The data generating device 5 is, for example, a barcode reader that obtains the work log of a worker, a PC or a server that collects the work log (for example, data generating device 5a), a machine that processes parts or assembles finished products (for example, data generating device 5b), a sensor that collects inspection information of RFID (Radio Frequency IDentifier) ​​attached to parts or finished products (for example, data generating device 5c), etc. The field data 100 (actual data) collected or generated by these data generating devices 5 is transmitted to the information collecting and display system 1, the master data storage unit 3, or the transaction data storage unit 4 via the network 2.

[0018] The master data storage unit 3 is, for example, a storage device such as a server or memory, and stores a model that defines what information is to be stored in the transaction data storage unit 4 or the like. This model is also called master data. In other words, by changing the master data (model) defined in the master data storage unit 3, it is possible to change what on-site data 100 (type of information to be collected) is to be collected from the data generating device 5. The master data in the master data storage unit 3 can be set or changed via an external device (not shown).

[0019] The transaction data storage unit 4 is, for example, a storage device such as a server or a memory, and stores site data 100 including information defined by the master data in the master data storage unit 3. In the embodiment, the transaction data storage unit 4 stores site data 100 (see FIG. 7) such as identification information, occurrence date and time, and actual measurement values.

[0020] [Information collection and display system] Next, we will explain the main functions of the information collecting and display system 1. The information collecting and display system 1 has a central processing unit (CPU) that performs overall control of the information collecting and display system 1, a storage device (Read Only Memory: ROM) that stores each control program for controlling the information collecting and display system 1, a primary storage device (Random Access Memory: RAM) that temporarily stores information processed by the CPU, and a hard disk drive (HDD), and the following functions are realized by the CPU executing each control program stored in the ROM. FIG. 2 is a block diagram illustrating the functions of the information collection and display system.

[0021] As shown in Figure 2, the information collection and display system 1 has a relationship data model creation unit 10, a relationship data registration unit 11, a relationship data search unit 12, an accumulated data acquisition unit 13, an analysis data accumulation unit 14, a relationship data accumulation unit 15, a data provision API unit 16, a comparison data definition unit 17, and a temporary accumulation unit 18.

[0022] As described above, the information collection and display system 1 is connected to the dictionary database 6, the transaction data storage unit 4, the data generating device 5, and the master data storage unit 3 via the network 2. Furthermore, the relevance data model creation unit 10 and the relevance data search unit 12 of the information collection and display system 1 are connected to a user interface 7 such as a display, and information resulting from processing by the information collection and display system 1 is displayed on the user interface 7 and provided to a user, or the user can input predetermined information to the relevance data model creation unit 10 or the relevance data search unit 12 via the user interface 7. Furthermore, in the information collection and display system 1, the analysis data storage unit 14 and the data provision API unit 16 are capable of providing information resulting from processing by the information collection and display system 1 to an application 8 outside the information collection and display system 1.

[0023] The relevance data model creation unit 10 reads out master data corresponding to the model data from the master data storage unit 3 based on the model data input from the user interface 7, and creates definition information 300 (400) described below. The definition information 300 (400) created by the relevance data model creation unit 10 has a predetermined data structure, and defines in what data structure the relevance data registration unit 11 acquires the site data 100 from the data generating device 5.

[0024] The relevance data registration unit 11 receives the site data 100 from the data generating device 5, and structures the site data 100 based on the data structure defined in the definition information 300 (400) acquired from the relevance data model creation unit 10. The relevance data registration unit 11 then determines whether the site data 100 acquired according to the definition information 300 (400) is business information, worker, machine, work procedure, or material (parts) based on the identification information given to the site data 100. Hereinafter, these worker (Man), machine (Machine), work procedure (Method), and material (Material) may be referred to as 4M information (or 4M node) or business-related information, taking the initial letter M of the worker (Man), machine (Machine), work procedure (Method), and material (Material).

[0025] Here, the relational data registration unit 11 is connected to the comparison data definition unit 17. The relational data definition unit 17 defines the relationship between the 4M information determined by the relational data registration unit 11 and the identification information assigned to the site data 100, and the relational data registration unit 11 relates the 4M information determined by the relational data registration unit 11 to the actually acquired site data 100 based on this definition (maps the identification information of the site data 100 to the 4M information). The relational data registration unit 11 transmits the 4M information after the site data 100 is related to the relational data storage unit 15. Furthermore, the relational data registration unit 11 is connected to the temporary storage unit 18. The temporary storage unit 18 is a storage device such as a memory, and information for configuring a connection relationship (generating a connection line) between each piece of information (business information and 4M information) included in the site data 100 is registered.

[0026] The stored data acquisition unit 13 acquires the field data 100 from the transaction data storage unit 4 and the master data storage unit 3 based on the relationship data 200 stored in the relationship data storage unit 15 .

[0027] When a user selects 4M information (first information) of a predetermined task from the user interface 7, the association data search unit 12 searches for other 4M information (second information) of the task related to the 4M information (first information) based on the identification information given to the 4M information (first information), and presents the searched 4M information (second information) to the user by displaying it on the user interface 7 using hatching, color coding, or the like. The association data search unit 12 also transmits the connection relationship between the selected 4M information (first information) and the searched 4M information (second information) to the analysis data accumulation unit 14. An example of a method for searching 4M information by the association data search unit 12 will be described later.

[0028] The analytical data storage unit 14 stores the connection relationship between the selected 4M information (first information) and the searched 4M information (second information) sent from the relationship data search unit 12. The analytical data storage unit 14 sends the connection relationship of this stored 4M information to the application 8, so that other 4M information of the business related to the selected 4M information can be used in various analytical methods.

[0029] The data providing API (Application Programming Interface) unit 16 transmits data associated by the association data 200 to the application 8. Here, the data providing API unit 16 is connected to the dictionary database 6. Here, the item names of 4M information used in each manufacturing process (business) may differ for each manufacturing process. Therefore, different words with the same meaning for the item names of 4M information used in each manufacturing process are registered in association with each other in the dictionary database 6, and the data providing API unit 16 can accurately acquire data associated by the association data 200, including not only the same words but also different words with the same meaning.

[0030] Here, an example of the data structure of the relationship data 200 managed by the information collecting and display system 1 will be described.

[0031] 3 is a diagram illustrating an example of the data structure of the relationship data 200. This relationship data 200 is data stored in the relationship data storage unit 15 described above.

[0032] As shown in FIG. 3, the data structure of the relationship data 200 can express how workers, machines, parts, etc. are related to a specific task (manufacturing process) in a certain work procedure by associating the site data 100 generated from various devices (data generating devices 5) in each manufacturing process. In the embodiment, the relationship data 200 is composed of a task node 210 at the center, a part node 220 indicating materials required to perform the task, a worker node 230 performing the task, a machine node 240 used to perform the task, a finished product node 250 generated as a result of performing the task using parts as materials, and a work procedure node 260 defining the procedure for performing the task. The finished product node 250 generated by performing the task node 210 becomes a material (part) used in the subsequent process, and the part node 220 that becomes the material of the task node 210 is a finished product generated in the previous process. In other words, the part node 220 and the finished product node 250 have the same meaning of attributes, and when there is no particular distinction between the two, they may be collectively called material nodes. As described above, the part node 220, the worker node 230, the machine node 240, and the work procedure node 260 are called 4M information or 4M nodes.

[0033] In the information collecting and displaying system 1, when a problem occurs with the finished product itself, the 4M information associated with the finished product can be searched for using the association data 200, and the cause of the problem in a specific manufacturing process (task) can be identified. In the embodiment, a case will be described in which identification information is assigned to the on-site data 100 collected or generated by the data generating device 5 in each manufacturing process. In the information collecting and displaying system 1, the association between tasks can be managed by accumulating association data 200 that defines the association of machines, workers, etc. with tasks across multiple manufacturing processes (tasks).

[0034] Basic information of this association data 200 is identification information indicating each piece of information and timing (date and time) related to the association between the identification information. On-site data 100 (actual data) indicated by each identification information of the association data 200 is stored in a transaction data storage unit 4 managed externally, and a method of accessing the on-site data 100 stored in the transaction data storage unit 4 (such as a memory address for accessing the transaction data storage unit 4) is managed by the information collecting and displaying system 1.

[0035] The aforementioned relational data 200 is composed of business nodes 210 and 4M information. The connection lines connecting each node have as input what is necessary to execute the business and as output the finished product generated by the action of those inputs, and are expressed as a directed graph. If this is expressed as a manufacturing process in which multiple businesses are linked together, it can be displayed as shown in Figures 9 and 10, which will be described later.

[0036] FIG. 4 is a diagram for explaining an example of the structure of the definition information 300 created by the relevance data model creating unit 10. As shown in FIG.

[0037] As shown in FIG. 4, definition information 300 is held by the aforementioned relationship data model creation unit 10, and is composed of business information 310 as definition information for business node 210, worker information 320 as definition information for worker node 230, part information 330 as definition information for part node 220, finished product information 340 as definition information for finished product node 250, machine information 350 as definition information for machine node 240, and work procedure information 360 as definition information for work procedure node 260.

[0038] The task information 310 includes task identification information 311 , operating time information 312 , historical data access information 313 , and connection information 314 .

[0039] The task identification information 311 is identification information that defines what kind of task it is in the task node 210, and for example, identification information that can uniquely identify a chassis press processing task or an assembly task in a vehicle manufacturing process is set. This task identification information 311 is identification information that specifies the relationship with other tasks, and has a function of relating a plurality of tasks. This task identification information 311 also includes key information for acquiring the site data 100 (actual data) from the transaction data storage unit 4 or the master data storage unit 3 based on the operational data access information 313.

[0040] The operating time information 312 is set with information related to the start time and end time when a specific task is performed, and for example, when a specific task involves producing a finished product from parts, the input time of the parts is set as the start time, and the production time of the finished product is set as the end time. This operating time information 312 is used as information for narrowing down the search from the viewpoint of time when referring to operation information of workers, parts, machines, etc. By having this operating time information 312, the definition information 300 can provide the user with time series data when the task is performed, even if the time series data is difficult to associate from a viewpoint other than time series.

[0041] The operational data access information 313 is used when accessing the field data 100 stored in the transaction data storage unit 4 managed outside the information collecting and display system 1. Specifically, the operational data access information 313 includes the memory addresses of the field data 100 stored in the transaction data storage unit 4 or the master data storage unit 3. The connection information 314 describes the From-To of the connection information for associating the above-mentioned business node 210 with the 4M node. The connection information 314 will be described in detail later (see FIG. 6).

[0042] The worker information 320 includes worker identification information 321 and operational data access information 322. The worker identification information 321 is set with an identifier for identifying the worker in charge when the work was performed in the worker node 230 described above. This worker identification information 321 is used as a key for accessing the work record (log) of the worker stored in the transaction data storage unit 4 or the master data storage unit 3 based on the operational data access information 322.

[0043] The part information 330 is configured to include part identification information 331 and operation data access information 332. The part identification information 331 is defined to identify materials (parts) used in the business, and the operation data access information 332 includes memory addresses for accessing information such as the material and processing history of the parts stored in the transaction data storage unit 4 or the master data storage unit 3.

[0044] The finished product information 340 includes finished product identification information 341 and operational data access information 342. The finished product identification information 341 is defined to identify a finished product generated in a business, and the operational data access information 342 includes a memory address for accessing information such as the processing history of the finished product stored in the transaction data storage unit 4 or the master data storage unit 3.

[0045] The machine information 350 includes machine identification information 351 and operation data access information 352. The machine identification information 351 defines information for identifying a machine used in a business. For example, the machine identification information 351 can identify whether the machine used in a business is a press machine, a coating machine, an assembly machine, or the like. When a user wishes to refer to operation data when a business is being performed by a machine, the user can refer to the operation data by using the operation data access information 352 and the machine identification information 351.

[0046] Finally, the work procedure information 360 is configured to include work procedure identification information 361 and work procedure data access information 362. The work procedure identification information 361 defines identification information for identifying the work procedure manual for the target business. The work procedure data access information 362 includes a memory address that serves as a key for accessing the work procedure manual data stored in the transaction data storage unit 4 or the like that is managed outside the information collecting and display system 1.

[0047] In order to shorten the access time to the transaction data storage unit 4 managed outside the information collecting and display system 1, information that is frequently used in the field data 100 may be retained in the definition information.

[0048] FIG. 5 is a diagram for explaining an example of the structure of the definition information 400 according to the other embodiment of FIG.

[0049] As shown in FIG. 5, the basic structure of the definition information 400 according to the second embodiment is the same as that described for the definition information 300 in FIG. 4, but the extension information 470 is added to each piece of information. The information collection and display system 1 manages the association data 200 indicating the connection relationship of each piece of on-site data 100 collected or generated in each manufacturing process, and acquires the actual data of the on-site data 100 from the transaction data storage unit 4 managed outside the information collection and display system 1, so that it may take time to acquire the on-site data 100. Therefore, in the information collection and display system 1, when it is desired to acquire the on-site data 100 more quickly, the extension information 470 serving as a storage area for selectively storing information with a high utilization rate in advance is set in the definition information 400. In this way, the information with a high utilization rate in the on-site data 100 can be directly held in the definition information 400, so that the information with a high utilization rate can be acquired quickly. Furthermore, the extension information 470 may store information important for managing the operation information of information such as business and parts. In this way, it is possible to easily analyze the operation of the flow of the manufacturing process (line).

[0050] Next, an example of the connection information 314 constituting the task information 310 explained in Fig. 4 will be explained. The connection information 314 is information that defines the connection relationships among the task nodes 210, part nodes 220, worker nodes 230, machine nodes 240, finished product nodes 250, and work procedure nodes 260 in the above-mentioned relationship data 200. In other words, data on the connection relationships of the nodes connected based on the connection information 314 matches the relationship data 200 explained in Fig. 3, and is stored in the relationship data accumulation unit 15.

[0051] Fig. 6 is a diagram for explaining an example of each node connected based on the connection information 314. In Fig. 6, the description of information such as the above-mentioned each identification information and each data access information (see Figs. 4 and 5) is omitted, and only information necessary for explaining the connection information 314 is described.

[0052] As shown in FIG. 6, the connection information 314 is composed of a label 311a included in the task identification information 311, a manufacturing ID 311b, a worker ID 314a included in the connection information 314, a part ID_input 314b, a part ID_output 314c, a machine ID 314d, a procedure ID 314e, a previous process ID 314f, and a next process ID 314g.

[0053] 6, all elements required to execute a task are defined as flowing from each 4M node (part, worker, machine, work procedure) to task node 210, and the output resulting from the execution of the task is defined as flowing from task node 210 to finished product node 250. The connection relationship between the nodes is defined by recording the IDs set for each node in connection information 314. As a result, for example, a part ID (ID:Met001) set for part node 220 is associated with the part ID (ID:Met001) of task node 210, and a connection line is created from part node 220 to task node 210.

[0054] Similarly, for the other worker nodes 230, machine nodes 240, and work procedure nodes 260, the IDs set for each node match and are associated with the corresponding IDs for the business node 210, and a connection line is defined from each node to the business node 210. For the finished product node 250, the finished product ID set for the finished product node 250 is associated with the finished product ID of the business node 210, and a connection line is defined from the business node 210 to the finished product node 250.

[0055] Next, a description will be given of an example of the configuration of the site data 100. The site data 100 collected or generated by the data generating device 5 is acquired by the related data registration unit 11 according to the items and structure shown in the configuration shown in Fig. 7 described below.

[0056] FIG. 7 is a diagram illustrating an example of the configuration of the site data 100. As shown in FIG.

[0057] As shown in FIG. 7, the site data 100 includes task information 110, worker information 120, part information 130, finished product information 140, machine information 150, and work procedure information 160.

[0058] The task information 110 is configured to include task identification information 111, occurrence date and time information 112, and performance value 113. The task identification information 111 is an identifier that defines the type of task for which the site data 100 was generated. The occurrence date and time information 112 is date and time information on when the site data 100 was generated, and for example, the date and time when the site data was collected or generated by the data generating device 5 is recorded. The performance value 113 is performance value information added by the data generating device 5, and for example, when the task is press processing, the number of finished products produced in one press operation and the number of non-defective products sent to a subsequent process are recorded as performance value information.

[0059] The worker information 120 includes worker identification information 121, occurrence date and time information 122, and a performance value 123. The worker identification information 121 is an identifier for identifying the worker who performed the work, and the worker identification information 121 for identifying the worker can be obtained, for example, by reading an ID card held by the worker before the work. The occurrence date and time information 122 is information on the date and time when the worker started the work, and for example, when the worker performs a pressing operation, the date and time when the worker started one pressing operation is recorded as the date and time information. The performance value 123 is information on the period during which the worker performed the work, and for example, when the worker performs a pressing operation, the work period (time) required for one pressing operation is recorded as the period information.

[0060] Part information 130 is configured to include part identification information 131, generation date and time information 132, and performance value 133. Part identification information 131 is an identifier for identifying materials (parts) used in an operation. Generation date and time information 132 is information indicating the date and time when the part was produced. Performance information 133 is information such as the number of parts produced.

[0061] The finished product information 140 includes finished product identification information 141, generation date and time information 142, and performance value 143. The finished product identification information 141 is an identifier for identifying a finished product produced in an operation. The generation date and time information 142 is information indicating the date and time when the finished product was produced. The performance information 143 is information such as the number of finished products produced in the operation.

[0062] The machine information 150 includes machine identification information 151, occurrence date and time information 152, and performance value 153. The machine identification information 151 is an identifier for identifying the machine used in the work, and for example, this identifies the type of machine, such as a press machine, a coating machine, or an assembly machine. The occurrence date and time information 152 is information indicating the date and time when the machine started the work. The performance information 153 is information such as the operating time of the machine.

[0063] The work procedure information 160 is configured to include work procedure identification information 161, occurrence date and time information 162, and actual results 163. The work procedure identification information 161 is an identifier for identifying a work procedure manual required for work. The occurrence date and time information 162 is information indicating the date and time when the work procedure manual was acquired. The actual results information 163 is information indicating the time required to perform work according to the work procedure.

[0064] Next, an example of the connection relationship of each piece of information constituting the definition information 300 (definition information 400) after being connected by the connection information 314 (connection information 414) will be described. This connection relationship is stored in the relationship data storage unit 15. FIG. 8 is a diagram for explaining an example of the connection relationship between the pieces of information constituting the definition information 300 (definition information 400) after connection is made by the connection information 314. In FIG.

[0065] 8, each piece of information constituting the definition information 300 (FIG. 4) or the definition information 400 (FIG. 5) (for example, the task information 310 and the worker information 320, the task information 310 and the part information 330, etc.) is associated with each other by relationship information 500. This relationship information 500 is generated by expanding the connection information 314 (414) of the task information 310 (410) of the definition information 300 (400) described above on a database.

[0066] The relationship information 500 includes relationship identification information 501 , relationship data access information 502 , and connection information 503 .

[0067] The relationship identification information 501 is information that defines the connection relationship between each piece of information, and is, for example, identification information that defines the relationship between the task information 310 and the part information 330, or the connection between the task information 310 and the worker information 320. In other words, the relationship identification information 501 can be said to be an identifier that specifies the connection line between each piece of information.

[0068] The relational data access information 502 is information including a memory address for accessing logic that defines the connection relationships of each piece of information in the definition information 300 (400) stored in a database separate from the relational data accumulation unit 15 (information collecting and displaying system 1). A process that defines the connection relationships of each piece of information is performed by the logic applied by this relational data access information 502. Here, logic is information such as a flow chart that defines the process for connecting a specific piece of information with other information. In other words, the relational data access information 502 can also be said to be information that indicates the meaning of the connection between each piece of information.

[0069] The connection information 503 is information necessary for connecting each piece of information, and includes information that defines the start point of a given piece of information (e.g., part information 330) and information that defines the end point of other information related to the given piece of information (e.g., business information 310). This makes it possible to determine the start point and end point of the given information (e.g., part information 330) and other information (e.g., business information 310), and to determine the direction of the connection line.

[0070] All information constituting the definition information 300 (400) is related to each other by this relationship information 500. An example of the relationship data 200 in which each piece of information in the definition information 300 (400) is specifically related to each other by this relationship information 500 is shown in FIG.

[0071] 9 and 10, a pre-process task 710 and a post-process task 720 are related to each other with respect to a specific task 700, and each task 700, 710, 720 is further connected to each of the tasks by relationship information 500, such as machines and workers, with a specific relationship. Note that, for the sake of convenience, only a portion of the relationship information 500 connecting each piece of information is shown in Fig. 9 and 10, but in reality, all connections between each piece of information are set.

[0072] In the above embodiment, a case has been described in which a plurality of tasks are connected in a straight line and each task is associated with information on parts, machines, etc., but it is also possible that information associated with a given task is associated with a plurality of other tasks, and that each piece of information related to each of a plurality of tasks is associated with a given task. In addition, when a manufacturing process includes a plurality of tasks, the tasks may not be directly connected to each other through the relationship information 500 described above, but may be associated with other tasks via information associated with each task.

[0073] Figure 11 is a schematic diagram that explains only the connection relationships of each piece of information (nodes) in the relationship data 200, and illustrates a case in which a part B node 1010 associated with a given business B node 1011 is used as an input for multiple other business nodes (business C node 1020 and business E node 1030), and a part D node 1061 generated in business D node 1060 and a part F node 1071 generated in business F node 1070 are used as inputs for a business G node.

[0074] As shown in FIG. 11, a task B (node ​​1011) corresponding to a previous process is performed to produce a plurality of parts B (node ​​1010), and the plurality of parts B (node ​​1010) are used as materials for tasks C (node ​​1020) and E (node ​​1030) corresponding to subsequent processes. In addition, in task G (node ​​1040), a part D (node ​​1061) produced in task D (node ​​1060) and a part F (node ​​1071) produced in task F (node ​​1070) are used as materials to produce a finished product 1080. In this case, in the operation data access information 313 constituting the task information 310 shown in FIG. 4 described above, a plurality of parts B may be lot-managed (i.e., a single identifier is assigned to a plurality of parts B) in the actual operation information, or a single part B may be individually managed (i.e., a single identifier is assigned to a single part B). For example, if part B is managed by lot, then part B is used by lot in tasks D and E, whereas if part B is managed by individual item, then part B is used by individual item in tasks D and E.

[0075] The connection relationships of each piece of information constituting the relationship data 200 are not limited to the example shown in FIG. 11. For example, as shown in FIG. 12, multiple information nodes may be associated with one business node.

[0076] 12, in the embodiment, two part A nodes 1110 and part B node 1120, two worker A nodes 1130 and worker B node 1140, two machine A nodes 1150 and machine B node 1160, which are defined as 4M nodes, are associated with one task G node 1111. In other words, in a given task G node 1111, a plurality of workers A and B may process a plurality of parts A and B using a plurality of machines A and B. Here, the work procedure node 1170 defines the task content (work procedure) of the task G node 1111, so one work procedure node 1170 is associated with the task G node 1111.

[0077] Also, as shown in FIG. 13, a connection relationship may be established in which a part produced in a specific business is passed through another business and then returned to the specific business for use.

[0078] In the embodiment, part A (node ​​1210) produced in task C (node ​​1250), which is a subsequent process, is input as a material for task E (node ​​1260), and part B (node ​​1220) is output as a finished product. Part B (node ​​1220) is input again as a material for task C (node ​​1250). This shows a flow in which, in the process of producing a finished product through a manufacturing line consisting of tasks A, B, C, and D having the same identification information, part A (node ​​1210) is once output in task C (node ​​1250), and as a result of processing in task E (node ​​1260), part A is changed to part 1 (node ​​1230) equivalent, and task C is performed again. For example, task C is a task such as inspection, and as a result of inspection, the quality is found to be problematic, so the part is removed from the line, corrections are made in task E, and the part is performed again from task C. The business nodes in the diagram indicate manufacturing processes having identification information that indicates a specific finished product, and when the same identification information passes through the same business, it is input to the business node created so far, in this case business C (node ​​1250). Since a part with the same identification information has been input multiple times into business C (node ​​1250), the fact that it has been input multiple times is stored as operation data, or the fact that it has been input multiple times is stored in the aforementioned extended information 470 (see FIG. 5).

[0079] [Model data creation screen] Next, an example of a model data creation screen 600 by the relevance data model creation unit 10 will be described with reference to Fig. 14. This model data creation screen 600 is displayed on a display, which is an example of a user interface 7 connected to the relevance data model creation unit 10. While visually checking this model data creation screen 600, a user creates model data of a manufacturing process.

[0080] As shown in FIG. 14, the model data creation screen 600 is composed of a business candidate sub-screen 610 that displays a list of business candidate sub-screens, a location sub-screen 620 that indicates in which manufacturing plant the manufacturing process is performed, a line sub-screen 630 that shows overall information about the manufacturing line (business) within the manufacturing plant, a data model display sub-screen 640 that defines the relationship with a specific manufacturing line (business), and a node definition information sub-screen 650 that defines the property values ​​of the nodes of a specific manufacturing line (business) displayed on the data model display sub-screen 640.

[0081] The business nodes (business 1 node to business 16 node) registered in the business candidate sub-screen 610 are registered in advance as system information and are set in advance according to the user's business contents. The line sub-screen 630 can define the process sequence of each business in the manufacturing process by sequentially connecting each business node using the business 1 to 16 nodes displayed in the business candidate sub-screen 610. The above-mentioned 4M node is associated with each business 1 to 16 node, and details of the 4M node and details of the business node are input using the data model display sub-screen 640 and the node definition information sub-screen 650. In the node definition information sub-screen 650, a business property screen 651 for setting the property of the business node and a 4M property screen 652 for setting the property of the 4M node can be selectively switched.

[0082] In the embodiment, since the business 1 node is selected in the line sub-screen 630 (see the colored part in FIG. 14), the data model display sub-screen 640 associates each piece of information such as parts and workers with the business 1 node. Since the business 1 node is selected in the data model display sub-screen 640 (see the colored part in FIG. 14), the business property screen 651 of the node definition information sub-screen 650 registers the business node name (business 1 node), the period during which the selected business 1 node is applied in the system, and the application start date and time (for example, January 1, 2018, 8:30 a.m.) and the application end date and time (for example, March 31, 2018, 5:30 p.m.). Here, when changing the property value of the business 1 node to use a new business 1 node, the application end date and time of the previous business 1 node and the application start date and time of the new business 1 node are matched, and the new business 1 node can be updated by revising it up.

[0083] Here, when a 4M node such as a worker node or a machine node is selected on the data model display sub-screen 640, the properties of the selected 4M node are displayed on a 4M property screen 652. FIG. 15 differs from FIG. 14 in that a machine candidate sub-screen 653 is displayed in place of the task candidate sub-screen 610 at the position of the task candidate sub-screen 610. The machine candidate sub-screen 653 displays a list of pre-registered machine nodes, and one machine node selected from this list of machine nodes can be assigned to a machine node on the node definition information sub-screen 650. In the embodiment, the machine 2 node is selected from the machine node list (see the colored part in FIG. 15) and assigned to the machine node on the node definition information sub-screen 650.

[0084] Furthermore, in the node definition information subscreen 650, the property values ​​of the selected machine 2 node can be set, and the machine node name (e.g., machine 2 node), application start date and time (e.g., January 1, 2018, 8:30 a.m.), application end date and time (e.g., March 31, 2018, 5:30 p.m.), machine ID (e.g., M002), and access key (e.g., ZZ-XXXX-M002) can be input and set. The access key is an access key for accessing a database in which the operation information of the 4M node (e.g., machine node) is stored. The relationship data registration unit 11 can acquire the operation information of a specific 4M node from the database based on this access key.

[0085] [Relationship data registration process] Next, the flow of processing up to the point where the relationship data 200 is registered in the relationship data storage unit 15 will be described.

[0086] 16 and 17 are flowcharts illustrating the flow of processing up to the point where the association data 200 is registered in the association data storage unit 15. FIG.

[0087] First, in each manufacturing process (task), the data generating device 5 collects or generates the site data 100 (step S101), and then transmits the site data 100 to the information collecting and display system 1 via the network 2 (step S102).

[0088] In the information collecting and displaying system 1, when the site data 100 is received (step S103), the relevance data registering unit 11 acquires the identification information (the identification information 111, 121, 131, 141, 151, and 161 shown in FIG. 7) included in the received site data 100 (step S104), and acquires the definition information 300 (or 400) corresponding to each acquired identification information from the relevance data model creating unit 10 (step S105). In addition, the relevance data registering unit 11 judges whether the definition information 300 (or 400) acquired from the relevance data model creating unit 10 is the task information 310 (410) or 4M information such as other worker information 320 (420), part information 330 (430), machine information 350 (450), and work procedure information 360 (460) (step S106).

[0089] When the relationship data registration unit 11 determines that the acquired definition information 300 (400) is the business information 310 (410) (step S106: Yes), it searches the relationship data storage unit 15 for a business node corresponding to the business information 310 (410) (step S107). When the relationship data registration unit 11 cannot find a business node corresponding to the business information 310 (410) (step S108: No), it generates a corresponding business node based on each acquired identification information and the definition information 300 (or 400) (step S109). When the relationship data registration unit 11 finds a business node corresponding to the business information 310 (410) (step S108: Yes), it proceeds to step S111.

[0090] The relationship data registration unit 11 acquires occurrence date and time information (e.g., 112, 122, 132, 142, 152, 162) included in the site data 100 for the generated business node, and registers it in the relationship data accumulation unit 15 as start information of the generated business node (step S110).The relationship data registration unit 11 then updates the property value of the business node, for example, the data in the extended information 470 (step S111).

[0091] Then, as shown in Fig. 17, the relationship data registration unit 11 constructs connection lines between the nodes. Specifically, the relationship data registration unit 11 determines whether or not a related node (connection destination) exists based on the definition information 300 (400) acquired from the relationship data model creation unit 10 (step S112), and if it is determined that a related node exists (step S112: Yes), constructs a connection line based on the definition information 300 (400) (step S113) and updates the property value of the connection line (step S114). Here, the property value of the connection line refers to information added to the connection line, such as the relationship identification information 501, the relationship data access information 502, and the connection information 503 of the relationship information 500 shown in Fig. 8.

[0092] After the connection line from the business node is constructed, the relationship data registration unit 11 acquires information (connection line information) for generating the connection line stored in the temporary storage unit 18, and constructs the connection line (step S115). If the connection line information is not stored (step S116: No), the relationship data registration unit 11 ends this process. If the connection line information is stored in the temporary storage unit 18 (step S116: Yes), the relationship data registration unit 11 returns to step S112 and generates the connection line and updates the properties until it is determined that the temporary storage unit 18 does not store the connection line information. If the relationship data registration unit 11 determines in step S112 that there is no connection destination (step S112: No), it stores the connection line information in the temporary storage unit 18 (step S117) and ends this process.

[0093] 16, if the relationship data registration unit 11 determines in step S106 that the identification information acquired from the site data 100 is 4M information different from the business information (step S106: No), it searches for 4M information corresponding to the identification information from the relationship data storage unit 15 (step S118). If the relationship data registration unit 11 determines that the 4M information corresponding to the identification information is stored in the relationship data storage unit 15 (step S119: Yes), since the registration of the 4M information has already been completed as existing when the manufacturing process was constructed, it updates the property value (step S120) and proceeds to step S112. If the relationship data registration unit 11 determines that the 4M information does not exist (step S119: No), it discards the site data 100 received from the data generating device 5 (step S121) and ends this process.

[0094] [4M information generation and registration processing] Next, the generation and registration process of 4M information by the relational data registration unit 11 will be described. Among the above-mentioned 4M information, the worker information, machine information, and work procedure information are defined in advance by the user when the manufacturing process is introduced, and are not generated each time a predetermined process is performed like the task information. Although the work shift of the worker information may change depending on the predetermined task unit, the worker himself is registered in this information collecting and displaying system 1, and the machine that performs the task is also already decided and installed when the task is started. Therefore, this information is registered in advance before the site data is routinely operated by the information collecting and displaying system 1.

[0095] FIG. 18 is a flowchart of the generation and registration process of 4M information by the relational data registration unit 11.

[0096] First, the relevance data model creation unit 10 generates configuration information (definition information 300 or 400) of the relevance data based on the master data stored in the master data storage unit 3 (step S201), and transmits the generated configuration information to the relevance data registration unit 11 (step S202). The relevance data registration unit 11 receives the configuration information transmitted from the relevance data model creation unit 10 (step S203), generates 4M information according to the received configuration information (step S204), and registers the generated 4M information in the relevance data storage unit 15 (step S205). This allows the relevance data registration unit 11 to generate 4M information according to the configuration information received from the relevance data model creation unit 10, and to register the 4M information in the relevance data storage unit 15.

[0097] [Related data extraction process] Next, the process of extracting relational data in the relational data search section 12 will be described.

[0098] 19 is a flowchart of the process of extracting the association data 200 by the association data search unit 12. The process of extracting the association data 200 by the association data search unit 12 is performed using a data extraction tool 800 (see FIG. 23) displayed on a user interface 7 such as a display.

[0099] First, the data extraction tool 800 displayed on the user interface 7 is used to input a period, a scope of work, etc., into an input form 802 to specify a range from which the association data 200 is to be extracted (step S301). The association data search unit 12 displays a plurality of business nodes 801 in the manufacturing process to be extracted from the association data 200 extracted based on the specified range (step S302). The user selects a node (e.g., the machine 2 node shown in FIG. 23) that the user wishes to search from among the displayed business nodes 801 (step S303), and the association data search unit 12 displays a list of performance value names associated with the node selected by the user (step S304). In the embodiment, based on the selection of the machine 2 node by the user, the association data search unit 12 displays a list of performance value names of items 10 to 14 associated with the machine 2 node.

[0100] Next, the user selects one from the list of performance values ​​(for example, item 12 shown in FIG. 23) (step S305), and a sample of the extracted relationship data is displayed on a data display sub-screen (not shown) under the screen of the data extraction tool 800 (step S306). The user repeats the processes of steps S301 to S306 multiple times until a list of data items that are necessary for data analysis and that the user judges to be related is extracted (step S307: No). When the selection is completed (step S307: Yes) and the process is executed, the relationship data search unit 12 acquires actual data from the transaction data storage unit 4 and the master data storage unit 3 based on the operational data access information held by each node, and creates a data mart in the temporary storage unit 18 (step S308).

[0101] Fig. 20 is a flowchart of the process of storing user-defined data in the relational data storage unit 15. The process of extracting user-defined data (steps S401 to S408 shown in Fig. 20) follows the same flow as the flowchart explained in Fig. 19. The relational data extracted by ETL (Extract / Transform / Load) or the like is analyzed and then displayed as the analysis result is defined. A connection line of the relational data is constructed between data required for analysis by ETL or the like, and an access key that calls the logic defined by ETL or the like is registered in the access information.

[0102] [Data analysis processing] Next, a data analysis process performed by a data analysis tool such as application 8 based on the data mart (analysis data) created by the processes in steps S301 to S308 (or steps S401 to S408) will be described.

[0103] 21 is a flowchart explaining the data analysis process performed by a data analysis tool such as application 8 based on the data mart (analysis data) created by the processes of steps S301 to S308 (or steps S401 to S408). This data analysis process is performed by application 8 analyzing the analysis data stored in analysis data storage unit 14.

[0104] The application 8 (data analysis tool) acquires the data mart extracted by the processing of steps S301 to S308 (or steps S401 to S408) described above and stored in the analysis data storage unit 14 (step S501). A user of the data analysis tool displays the acquired data on a screen using the data analysis tool and performs data analysis (step S502).

[0105] [Data generation process for analysis] Next, the process of generating analysis data by the data providing API unit 16 will be described.

[0106] FIG. 22 is a flowchart of the process of generating analysis data by the data providing API unit 16.

[0107] First, the application 8 instructs the data providing API unit 16 to search for the relationship data 200 required to generate the analysis data (step S601). Specifically, the application 8 transmits a search key for searching for the required relationship data 200 to the data providing API unit 16. The data providing API unit 16 uses the search key acquired from the application 8 to search for the relationship data 200 from the relationship data storage unit 15 (step S602). The data providing API unit 16 acquires data access information for the acquired relationship data 200 (step S603) and transmits the information to the accumulated data acquisition unit 13 (step S604). The accumulated data acquisition unit 13 acquires the transaction data to be acquired from the transaction data storage unit 4 based on the received data access information (step S605). The accumulated data acquisition unit 13 transmits the acquired data to the data providing API unit 16 (step S606). The data providing API unit 16 formats the acquired data and transmits it to the application 8.

[0108] [Data Extraction Tool] Next, a data extraction tool 800 displayed on a user interface 7 such as a display will be described. Using the data extraction tool 800 displayed on the user interface 7, a user can easily extract the relationship data 200 by visually checking it.

[0109] Fig. 23 is a diagram illustrating an example of a data extraction tool 800 displayed on a user interface 7 such as a display. In Fig. 23, each node and connection line of the relational data registered in the relational data storage unit 15 is represented by a circle and a line.

[0110] An input form 802 is provided at the top of the screen of the data extraction tool 800, and the necessary search range of the association data 200 is input into this input form 802. A plurality of business nodes 801 corresponding to the input search range are displayed at the bottom of the screen of the data extraction tool 800. In this business node 801, the association data 200 constructed by circles and lines can display data items 803 registered in the node. If this data item 803 is a machine node, the actual value name of the machine node is displayed and acquired from the master data storage unit 3. The actual value name acquired from the master data storage unit 3 is converted by the dictionary database 6 into a name that is easily recognizable by the user from the name managed by the machine that the machine node is the counterpart of. The hatched parts of the data items are data specified by the user and data related to the specified data, and are displayed as hatched by the process of FIG. 19.

[0111] For example, using the data extraction tool 800, a period, scope of work, etc. is entered into an input form 802 to specify the range from which the relationship data 200 is to be extracted (step S301 in FIG. 19), and the relationship data search unit 12 displays multiple business nodes 801 in the manufacturing process to be extracted from the relationship data 200 extracted based on the specified range (step S302 in FIG. 19).

[0112] The user selects a node (e.g., machine 2 node) that the user wishes to search from among the displayed business nodes 801 (step S303 in FIG. 19), and the relationship data search unit 12 displays a list of performance value names (data items 803) linked to the node selected by the user (step S304 in FIG. 19). In the embodiment, based on the user's selection of the machine 2 node, the relationship data search unit 12 displays a list of performance value names of items 10 to 14 related to the machine 2 node.

[0113] Next, when the user selects one item (e.g., item 12) from the list of performance values ​​(step S305 in FIG. 19), the relationship data search unit 12 searches for item 4 of machine 1 of other business 2 that is related to item 12 selected by the user, displays it by hatching or the like, and can extract items 4 related to item 12. Similarly, when the user selects item 14 of the machine 2 node, item 6 of machine 1 of other business 2 that is related is searched for and displayed by hatching or the like. This makes it easy to visually confirm the results of searching for items (second information) of other business related to the selected item (first information) of a specific business, making it easier to perform subsequent analysis of the relationship.

[0114] As described above, in the embodiment, the data generating device 5 that generates the on-site data 100 and the transaction data storage unit 4 that stores the on-site data 100 generated by the data generating device 5 are connected to the information collecting and display system 1. A relational data storage unit (15) that stores relational data (200) that defines the relation between each of the plurality of pieces of information included in the site data (100); The system includes an association data search unit 12 that searches for other 4M information (second information) related to predetermined 4M information (first information) included in a plurality of pieces of information based on association data 200 stored in an association data accumulation unit 15, and a user interface 7 that displays a connection relationship between the plurality of pieces of information related to each other by the association data 200, The relationship data search unit 12 is configured to search for second information related to the first information based on the relationship data 200 in response to selection of first information in the connection relationships of multiple pieces of information displayed on the user interface 7, and to display the first information and the second information on the user interface 7 together with the connection relationships of the multiple pieces of information.

[0115] With this configuration, the information collecting and display system 1 only needs to generate and manage the relationship data 200 as definition information that defines the connection relationships of the site data 100, and there is no need to hold data that associates all of the site data 100, making it possible to reduce the capacity of the storage device that stores the relationship data 200. Furthermore, in the information collecting and display system 1, by selecting first information for a predetermined task from the user interface 7, second information related to this first information is searched for, and the first information and second information are displayed on the user interface 7 together with the connection relationships of the site data 100, making it easy to analyze the relationship by visual confirmation.

[0116] While one example of an embodiment of the present invention has been described above, the present invention may be implemented by combining all of the above-described embodiments, or by arbitrarily combining any two or more of the embodiments.

[0117] Furthermore, the present invention is not limited to having all of the configurations of the above-mentioned embodiments, and some of the configurations of the above-mentioned embodiments may be replaced with configurations of other embodiments, and the configurations of the above-mentioned embodiments may be replaced with configurations of other embodiments.

[0118] Furthermore, some of the configurations of the above-described embodiments may be added to, deleted from, or replaced with the configurations of other embodiments. [Explanation of symbols]

[0119] 1: Information collection and display system, 3: Master data storage unit, 4: Transaction data storage unit, 5: Data generation device, 6: Dictionary database, 7: User interface, 8: Application, 10: Relevance data model creation unit, 11: Relevance data registration unit, 12: Relevance data search unit, 13: Stored data acquisition unit, 14: Analysis data storage unit, 15: Relevance data storage unit, 16: Data provision API unit, 17: Comparison data definition unit, 18: Temporary storage unit, Relevance data 200: Business node, 220: Part node, 230: Worker node, 240: Machine node, 250: Finished product node, 260: Work procedure node, 300: Definition information, 310: Business information, 320: Worker information, 330: Part information, 340: Finished product information, 350: Machine information, 360: Work procedure information, 800: Data extraction tool

Claims

1. A system including a data storage device that stores on-site data that is set or generated each time a plurality of tasks included in a process are performed, a processing unit that processes the on-site data stored in the data storage device, and a storage unit that stores data processed by the processing unit, comprising: a program that causes the processing unit to process the on-site data, The data structure of the association data, which is data defining the relationship between each of the multiple items of information included in the site data and is used in the process, is as follows: A business node representing business information; a part node which is one or more pieces of input data when performing a task related to a predetermined task node among the plurality of tasks; A finished product node which is one or more output data when performing the business; Including, Among the plurality of tasks, a subsequent task node is defined as using the completed product node output by a previous task node as the part node, the finished product node includes an output identifier, which is an identifier for each unit or for each lot, and first access information to the data storage device in which information about the finished product corresponding to the output identifier is stored; the part node includes an input identifier using the output identifier assigned to the finished product node output by a previous task, which is used as the part node, and second access information to the data storage device storing information on the finished product corresponding to the output identifier; If the output identifier of a first operation node among the plurality of operations matches the input identifier of a second operation node, the first operation node is determined to be a previous operation of the second operation node; the program causes the processing unit to display the business node corresponding to a search condition and a part node and a finished product node related to the business node, and when the finished product node is selected, to obtain information relating to the finished product from the data storage device based on the first access information and display the information, and when the part node is selected, to obtain information relating to the part from the data storage device based on the second access information and display the information. program.

2. Each of the plurality of operations is defined as having one or more parts as input and one or more finished products as output, each time the operation is performed; The processing unit includes: definition information defining items including one or more of the parts and the finished product used to identify the on-site data to which an identifier is assigned, the on-site data relating to each of the plurality of operations; The program is determining the item corresponding to the on-site data stored in the storage unit based on the definition information; The program according to claim 1.

3. The definition information includes, as the items, worker information, machine information, work procedure information, part information, and finished product information, The program causes the processing unit to determine, among the on-site data, the input identifier as the part information and the output identifier as the finished product information, The program according to claim 2.

4. The definition information includes, as the item, business information that defines the content of the business. The program according to claim 2 or 3.

5. The task information includes, as an item, a start date and an end date and time for each execution of the task, The storage unit records the start date and time and the end date and time each time the task is performed, The program causes the processing unit to determine the start date and time and the end date and time for the item of the task information. The program according to claim 4.

6. The program causes the processing unit to generate relationship information that associates the plurality of on-site data determined to fall into any one of the items of the association data with each other. The program according to any one of claims 1 to 5.

7. The association data includes access information to the on-site data stored in the data storage device. The program according to any one of claims 1 to 6.

8. A data storage device that stores on-site data that is set or generated each time a plurality of tasks included in a process are performed; an information system for processing the on-site data stored in the data storage device; A system comprising: A predetermined task among the plurality of tasks is defined as having one or more parts as input and one or more finished products as output each time the task is performed; The subsequent task among the predetermined tasks is defined as using the finished product output by the previous task as the part; For each of the operations, each of which performs one or more operations, a unique output identifier is assigned to the finished product for each operation and for each individual item or lot; The input identifier for the part is defined as using the output identifier assigned to the finished product, which is the output of the previous task, to be used as the part; The data storage device includes: accumulating the input identifier and the output identifier as part of the on-site data for each of the plurality of tasks; The information system includes: generating association data for each of the plurality of tasks, the association data including the input identifier, the output identifier, second access information to the data storage device in which information on the part corresponding to the input identifier is stored, and first access information to the data storage device in which information on the finished product corresponding to the output identifier is stored, the association data defining an association between task information included in the on-site data relating to the execution of the task and task-related information related to the task information; An information collection system that, for a plurality of pieces of relationship data, if the output identifier of the relationship data for a first task among the plurality of tasks matches the input identifier of the relationship data for a second task, associates and records the respective pieces of relationship data as the first task being a predecessor task of the second task.

9. The information system includes: definition information defining items including one or more of the parts and the finished product used to identify the on-site data to which an identifier is assigned, the on-site data relating to each of the plurality of operations; determining the item corresponding to the on-site data stored in the data storage device based on the definition information; The information collecting system according to claim 8.

10. The definition information includes, as the items, worker information, machine information, work procedure information, part information, and finished product information, The information system distinguishes the input identifier from the on-site data as the part information and the output identifier from the on-site data as the finished product information, The information collecting system according to claim 9.

11. The definition information includes, as the item, business information that defines the content of the business.

11. The information collecting system according to claim 9 or 10.

12. The task information includes, as an item, a start date and an end date and time for each execution of the task, the data storage device records the start date and time and the end date and time each time the task is performed; The information system determines the start date and time and the end date and time for the item of the task information. The information gathering system according to claim 11.

13. The information system generates relationship information that associates the plurality of on-site data determined to fall into any one of the items of the association data with each other. The information collecting system according to any one of claims 9 to 12.

14. The association data includes access information to the on-site data stored in the data storage device. The information collecting system according to any one of claims 8 to 13.

Images