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 Art

[0002] Conventionally, in factories, offices, etc. in the manufacturing industry, there are many operations that make up the manufacturing process when manufacturing finished products, etc. In each operation that makes up the manufacturing process, on-site data is generated and collected契机として when the operation is completed or a predetermined event occurs, and by analyzing this on-site data, the work efficiency in each operation is optimized. On the other hand, if the departments that manage each operation are different, it becomes difficult to share information between departments, and improvements for problems that span departments (operations) are not progressing. One of the reasons why improvements for problems that span departments (operations) are not progressing is thought to be that the systems used for business management in each department are different and the management systems are not unified. Also, in each department, since the optimization of work efficiency within the department is progressing by analyzing the collected on-site data, when seeking the overall optimization of a series of manufacturing processes, the efficiency of one's own department may deteriorate, and there is also a possibility of producing results that lower the department evaluation.

[0003] However, in the manufacturing industry, as it progresses from mass production to small-lot and multi-variety production, in order to improve the production efficiency of the entire manufacturing process, cooperation between departments is essential. In order to promote cooperation between departments, there is no other way but to present problems using fact data (factual information) that can be commonly analyzed by each department, and by associating and presenting the on-site data managed by one's own department with the on-site data managed by other departments, it is considered that cooperation between departments will be promoted.

[0004] Patent Document 1 discloses an information collection system that does not require configuring a link between databases and can efficiently collect various on-site data and supplementary information for each manufacturing process from the perspective of traceability.

[0005] Furthermore, 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] Japanese Patent Publication No. 2015-153196 [Patent Document 2] Japanese Patent Publication No. 2017-102548 [Overview of the project] [Problems that the invention aims to solve]

[0007] However, the method described in Patent Document 1 requires all relevant data to be stored in a database as supplementary information, necessitating a database with enormous storage capacity, which results in high equipment and maintenance costs. Furthermore, users cannot retrieve the desired data unless they understand the data structure of the data stored in the database.

[0008] Furthermore, the method described in Patent Document 2 limits the data generation device for generating on-site data to a specific device, making it difficult to correlate all on-site data collected or generated in a series of manufacturing processes. In addition, although the collected on-site data is assigned an identifier, it only shows the relationship between the finished product and the component corresponding to that finished product, and does not show how to correlate and display the on-site data within the series of manufacturing processes, making it difficult to effectively utilize the collected on-site data.

[0009] Therefore, the present invention has been made in view of the above problems, and aims to reduce the capacity of the storage device that stores related data by accumulating and managing the minimum necessary information for associating business information and business-related information contained in field data as related data, and to facilitate the analysis of field data at each site by using this related data to search for and display predetermined first information and second information related to said first information. [Means for solving the problem]

[0010] To solve the above problems, one aspect of the present invention provides a system including a processing unit that processes field data set or generated each time a plurality of operations included in a process are performed, and a storage unit that stores the data processed by the processing unit, wherein the system provides a data structure for relational data which is data that defines the relationships between each item of a plurality of pieces of information used in the processing, and includes an operation node representing operation data, a component node which is one or more input data when performing an operation related to a predetermined operation node among the plurality of operations, and a finished product node which is one or more output data when performing the operation, wherein a later operation node among the plurality of operations uses the finished product node output by the earlier operation node as the component node, the finished product node includes an output identifier which is an identifier for each individual item or for each lot, the component node includes an input identifier which uses the output identifier which is assigned to the finished product node output by the earlier operation and is used as the component node, and if the output identifier of the first operation node and the input identifier of the second operation node among the plurality of operations match, the first operation node is the operation preceding the second operation node.

[0011] According to the above embodiment, the minimum necessary information for linking multiple pieces of information contained in the field data is stored and managed as related data, thereby reducing the capacity of the storage device for storing related data. Furthermore, by using this related data to search for and display a predetermined first piece of information and a second piece of information related to that first piece of information, it becomes possible to easily analyze field data at each site. [Effects of the Invention]

[0012] According to the present invention, it becomes possible to easily analyze field data. [Brief explanation of the drawing]

[0013] [Figure 1] This diagram illustrates the connection relationship between the information collection and display system, the data generation device, and each storage unit that stores actual data according to the embodiment. [Figure 2] This is a block diagram illustrating the functions of the information gathering and display system. [Figure 3] This diagram illustrates an example of a data structure for relevance data. [Figure 4] This diagram illustrates an example of the structure of definition information created by the relationship data model creation unit. [Figure 5] This figure illustrates an example of the structure of definition information for other embodiments. [Figure 6] This diagram illustrates an example of each node connected based on connection information. [Figure 7] This diagram illustrates an example of the configuration information for field data. [Figure 8] This diagram illustrates an example of the connection relationships between the various pieces of information that constitute the definition information after it has been connected via connection information. [Figure 9] This is an example of relationship data, where each piece of definition information is specifically linked using relational information. [Figure 10] This is an example of relationship data, where each piece of definition information is specifically linked using relational information. [Figure 11]It is a schematic diagram explaining only the connection relationship of each piece of information of the relevance data. [Figure 12] It is a diagram explaining only the connection relationship of each piece of information constituting the relevance data according to another embodiment. [Figure 13] It is a diagram explaining the connection relationship of each piece of information constituting the relevance data according to another embodiment. [Figure 14] It is a diagram explaining an example of a model data creation screen displayed by the relevance data model creation unit. [Figure 15] It is a diagram showing a state where the display is switched from the business property screen to the 4M property screen on the node definition information sub-screen. [Figure 16] It is a flowchart explaining the process flow until the relevant data is registered in the relevance data storage unit. [Figure 17] It is a flowchart explaining the process flow until the relevant data is registered in the relevance data storage unit. [Figure 18] It is a flowchart of the generation and registration process of 4M information by the relevance data registration unit. [Figure 19] It is a flowchart of the extraction process of relevance data in the relevance data search unit. [Figure 20] It is a flowchart of the process of storing the data defined by the user in the relevance data storage unit. [Figure 21] It is a flowchart of the data analysis process performed by the data analysis tool based on the data mart. [Figure 22] It is a flowchart of the generation process of analysis data by the data providing API unit. [Figure 23] It is a diagram explaining an example of a data extraction tool displayed on the user interface.

Modes for Carrying Out the Invention

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

[0015] [Overall structure] Figure 1 is a diagram illustrating the connection relationship between the information collection and display system 1, the data generation device 5, and the respective storage units 3 and 4 that store actual data.

[0016] As shown in Figure 1, the information collection and display system 1 is connected to network 2. Network 2 is connected to a plurality of data generators 5a, 5b, and 5c (hereinafter, when data generators 5a, 5b, and 5c are not specifically distinguished, they will simply be referred to as data generator 5), a master data storage unit 3, and a transaction data storage unit 4 that stores actual data (hereinafter referred to as field data 100). These data generators 5, master data storage unit 3, and transaction data storage unit 4 are connected to the information collection and display system 1 via network 2.

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

[0018] The master data storage unit 3 is a storage device such as a server or memory, and stores a model that defines what kind of information to store in the transaction data storage unit 4, etc. 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 kind of field data 100 (types of information to collect) is collected from the data generation device 5. The master data of this 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 memory, and stores field data 100 that includes information defined in the master data of the master data storage unit 3. In this embodiment, the transaction data storage unit 4 stores field data 100 (see Figure 7) such as identification information, occurrence date and time, and measured values.

[0020] [Information Collection and Display System] Next, the main functions of the Information Acquisition and Display System 1 will be explained. The Information Acquisition and Display System 1 includes a Central Processing Unit (CPU) that controls the entire system, a Read Only Memory (ROM) that stores control programs for controlling the Information Acquisition and Display System 1, and a Random Access Memory (RAM) and Hard Disk Drive (HDD) that temporarily store information processed by the CPU. The following functions are realized when the CPU executes the control programs stored in the ROM. Figure 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 includes a relevance data model creation unit 10, a relevance data registration unit 11, a relevance data search unit 12, a stored data acquisition unit 13, an analysis data storage unit 14, a relevance data storage unit 15, a data provision API unit 16, a comparison data definition unit 17, and a temporary storage unit 18.

[0022] As mentioned above, the information collection and display system 1 is connected to the dictionary database 6, transaction data storage unit 4, data generator 5, and master data storage unit 3 via the network 2. Furthermore, the relationship data model creation unit 10 and relationship data search unit 12 of the information collection and display system 1 are connected to a user interface 7 such as a display, and the information processed by the information collection and display system 1 is displayed on the user interface 7 and provided to the user, or the user can input predetermined information to the relationship data model creation unit 10 or relationship data search unit 12 via the user interface 7. In addition, the information collection and display system 1 has an analysis data storage unit 14 and a data provision API unit 16 that can provide the information processed by the information collection and display system 1 to an external application 8 of the information collection and display system 1.

[0023] The relationship data model creation unit 10 reads 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) as described later. The definition information 300 (400) created by the relationship data model creation unit 10 has a predetermined data structure and defines what data structure the relationship data registration unit 11 will use to acquire the field data 100 from the data generator 5.

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

[0025] Here, the relationship data registration unit 11 is connected to the comparison data definition unit 17. The comparison data definition unit 17 defines the relationship between the 4M information determined by the relationship data registration unit 11 and the identification information assigned to the field data 100. Based on this definition, the relationship data registration unit 11 relates the 4M information determined by the relationship data registration unit 11 to the field data 100 that has actually been acquired (it maps the identification information of the field data 100 to the 4M information). The relationship data registration unit 11 transmits the 4M information after the field data 100 has been related to it to the relationship data storage unit 15. Furthermore, the relationship 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 it stores information for configuring the connection relationships (generating connection lines) between each piece of information (business information and 4M information) contained in the field data 100.

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

[0027] When a user selects 4M information (first information) for a given task from the user interface 7, the related data search unit 12 searches for other 4M information (second information) related to the task based on the identification information attached to the 4M information (first information), and presents the retrieved 4M information (second information) to the user interface 7 by displaying it with hatching or color coding. The related data search unit 12 also transmits the connection relationship between the selected 4M information (first information) and the retrieved 4M information (second information) to the analysis data storage unit 14. An example of how the related data search unit 12 searches for 4M information will be explained later.

[0028] The analysis data storage unit 14 stores the connection relationships between the selected 4M information (first information) transmitted from the relevance data search unit 12 and the retrieved 4M information (second information). By transmitting these stored 4M information connection relationships to the application 8, the analysis data storage unit 14 enables the use of other 4M information related to the selected 4M information in various analysis methods.

[0029] The data provision API (Application Programming Interface) unit 16 transmits the data associated with the relevance data 200 to the application 8. Here, the data provision API unit 16 is connected to the dictionary database 6. Here, the item names of the 4M information used in each manufacturing process (business) may differ from one manufacturing process to another. Therefore, the dictionary database 6 is registered with different words that have the same meaning as the item names of the 4M information used in each manufacturing process, and the data provision API unit 16 can accurately retrieve the data associated with the relevance data 200, including not only the same words but also different words with the same meaning.

[0030] Here, we will describe an example of the data structure of the related data 200 managed by the information collection and display system 1.

[0031] Figure 3 illustrates an example of the data structure of the relevance data 200. This relevance data 200 is the data stored in the aforementioned relevance data storage unit 15.

[0032] As shown in Figure 3, the data structure of the relationship data 200 associates field data 100 generated from various devices (data generation devices 5) in each manufacturing process, making it possible to represent how workers, machines, parts, etc., are related to a given task (manufacturing process) in what work procedures. In this embodiment, the relationship data 200 is centered around a task node 210 and consists of a parts node 220 indicating the materials needed 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 a later process, and the parts node 220 that becomes the material for the task node 210 is a finished product produced in the earlier process. In other words, the meaning of the attributes of the parts node 220 and the finished product node 250 are of the same kind, and if there is no particular distinction between the two, they may be collectively called material nodes. Furthermore, as mentioned above, the parts node 220, the worker node 230, the machine node 240, and the work procedure node 260 are referred to as 4M information or 4M nodes.

[0033] In the information collection and display system 1, if a problem occurs with the finished product itself, the 4M information associated with the finished product can be searched using the relevance data 200, and the cause of the problem in a predetermined manufacturing process (task) can be investigated. In this embodiment, the example will be explained in which identification information is attached to the field data 100 collected or generated by the data generation device 5 in each manufacturing process. In the information collection and display system 1, the relationships between tasks can be managed by accumulating relevance data 200 that defines the relationships between tasks such as machines and workers across multiple manufacturing processes (tasks).

[0034] The basic information of this related data 200 consists of the identification information that represents each piece of information, the relationship between the identification information and the related timing (date and time). The field data 100 (actual data) that each identification information of the related data 200 represents is stored in an externally managed transaction data storage unit 4, and the method of accessing the field data 100 stored in this transaction data storage unit 4 (such as the memory address for accessing the transaction data storage unit 4) is managed by the information collection and display system 1.

[0035] The aforementioned relationship data 200 consists of business nodes 210 and 4M information. The connecting lines between each node take the necessary inputs for executing the business and the finished product generated by their interaction as outputs, and this is represented as a directed graph. When this is represented as a manufacturing process in which multiple businesses are linked together, it can be displayed as shown in Figures 9 and 10 described later.

[0036] Figure 4 illustrates an example of the structure of the definition information 300 created by the relationship data model creation unit 10.

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

[0038] The business information 310 consists of business identification information 311, operating time information 312, operational data access information 313, and connection information 314.

[0039] The business identification information 311 is identification information that defines what kind of business it is at the business node 210. For example, in the vehicle manufacturing process, identification information is set that uniquely identifies the chassis press work and assembly work. This business identification information 311 is identification information that defines the relationship with other businesses and has the function of linking multiple businesses. In addition, this business identification information 311 also includes key information for obtaining field 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 contains information regarding the start and end times when a predetermined task is performed. For example, in a predetermined task where a finished product is produced from parts, the time when the parts are input is set as the start time, and the time when the finished product is produced is set as the end time. This operating time information 312 is used to narrow down the information from a time perspective when referring to operating information of workers, parts, machines, etc. By having this operating time information 312, the definition information 300 can provide users with time-series data that is difficult to associate from perspectives other than time series, as time-series data of when a task was performed.

[0041] The operational data access information 313 is used when accessing field data 100 and other data stored in the transaction data storage unit 4, which is managed outside the information collection and display system 1. Specifically, the operational data access information 313 includes the memory address of the field data 100 stored in the transaction data storage unit 4 or the master data storage unit 3. The connection information 314 contains the From-To information for associating the aforementioned business node 210 with the 4M node. Details of the connection information 314 will be described later (see Figure 6).

[0042] The worker information 320 consists of worker identification information 321 and operational data access information 322. The worker identification information 321 is set with an identifier to identify the worker in charge when they performed a task at the aforementioned worker node 230. This worker identification information 321 is used as a key to access the worker's work records (logs) 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 consists of part identification information 331 and operational data access information 332. The part identification information 331 is defined to identify the material (part) used in the business, and the operational data access information 332 includes memory addresses for accessing information such as the material and processing history of the part stored in the transaction data storage unit 4 or the master data storage unit 3.

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

[0045] The machine information 350 consists of machine identification information 351 and operational data access information 352. The machine identification information 351 defines information that identifies the machine used in the business. For example, this machine identification information 351 can be used to identify whether the machine used in the business is a press, a painting machine, or an assembly machine. The operational data access information 352 allows users to access operational data when a machine is performing a task by using the operational data access information 352 and the machine identification information 351.

[0046] Finally, the work procedure information 360 consists of work procedure identification information 361 and work procedure data access information 362. The work procedure identification information 361 defines identification information that identifies the work procedure document 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 document data stored in the transaction data storage unit 4 or other location managed outside the information collection and display system 1.

[0047] Furthermore, in order to reduce the access time to the transaction data storage unit 4, which is managed outside the information collection and display system 1, information with high usage rates in the field data 100 may be stored within the definition information.

[0048] Figure 5 is a diagram illustrating an example of the structure of definition information 400 according to another embodiment of Figure 4.

[0049] As shown in Figure 5, the basic structure of the definition information 400 according to the second embodiment is the same as that described in the definition information 300 in Figure 4 above, but each piece of information has extended information 470 added to it. The information collection and display system 1 manages relational data 200 that shows the connection relationships of each field data 100 collected or generated in each manufacturing process, and acquires the actual field data 100 from the transaction data storage unit 4 which is managed outside the information collection and display system 1, so it may take time to acquire the field data 100. For this reason, the information collection and display system 1 has set extended information 470 in the definition information 400, which is a storage area that selectively stores information with a high utilization rate in advance, in order to acquire the field data 100 more quickly. In this way, information with a high utilization rate in the field data 100 can be directly stored in the definition information 400, so that information with a high utilization rate can be acquired quickly. Furthermore, information that is important for managing operational information of information such as business and parts may be stored in the extended information 470. In this way, it is possible to easily analyze the operation of the flow of the manufacturing process (line).

[0050] Next, an example of connection information 314 that constitutes the business information 310 described in Figure 4 will be explained. Connection information 314 is information that defines the connection relationships between the business node 210, part node 220, worker node 230, machine node 240, finished product node 250, and work procedure node 260 in the aforementioned relationship data 200. In other words, the data of the connection relationships of each node connected based on connection information 314 matches the relationship data 200 described in Figure 3 and is stored in the relationship data storage unit 15.

[0051] Figure 6 illustrates an example of each node connected based on connection information 314. In Figure 6, the previously mentioned identification information and data access information (see Figures 4 and 5) are omitted, and only the information necessary for explaining connection information 314 is included.

[0052] As shown in Figure 6, the connection information 314 consists of a label 311a included in the business 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 preceding process ID 314f, and a succeeding process ID 314g.

[0053] In Figure 6, all elements necessary for executing a task are defined as moving from each of the 4M nodes (parts, workers, machines, and work procedures) towards the task node 210, and the output resulting from the execution of the task is defined as moving from the task node 210 towards the finished product node 250. The connection relationships of each node are defined by including the ID set for each node in the connection information 314. For example, this associates the part ID (ID:Met001) set for the part node 220 with the part ID (ID:Met001) for the task node 210, creating a connection line from the part node 220 to the 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 are matched with the corresponding IDs in the business node 210 and associated, and connection lines are 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 in the business node 210, and connection lines are defined from the business node 210 to the finished product node 250.

[0055] Next, an example of the configuration of the field data 100 will be described. The field data 100 collected or generated by the data generator 5 is acquired by the related data registration unit 11 according to the items and structure shown in the configuration of Figure 7, which will be described below.

[0056] Figure 7 illustrates an example of the structure of field data 100.

[0057] As shown in Figure 7, the field data 100 consists of business information 110, worker information 120, parts information 130, finished product information 140, machine information 150, and work procedure information 160.

[0058] The business information 110 consists of business identification information 111, occurrence date and time information 112, and actual values ​​113. The business identification information 111 is an identifier that defines what type of business the business in which the field data 100 was generated is. The occurrence date and time information 112 is the date and time information in which the field data 100 was generated, for example, the date and time when the data generation device 5 collected or generated the field data is recorded. The actual values ​​113 are actual value information assigned by the data generation device 5, for example, if the business is press working, the number of finished products produced in one press operation or the number of good products sent to the next process are recorded as actual value information.

[0059] The worker information 120 consists of worker identification information 121, occurrence date and time information 122, and actual value 123. The worker identification information 121 is an identifier that identifies the worker in charge of the work. For example, the worker identification information 121 that identifies the worker in charge can be obtained by reading an ID card held by the worker before the work is performed. The occurrence date and time information 122 is the date and time information of when the worker started the work. For example, when a worker performs a press operation, the date and time when one press operation starts is recorded as date and time information. The actual value 123 is the period information of when the worker performed the work. For example, when a worker performs a press operation, the work period (hours) taken for one press operation is recorded as period information.

[0060] The part information 130 consists of part identification information 131, occurrence date and time information 132, and actual value 133. The part identification information 131 is an identifier for identifying the material (part) used in the work. The occurrence date and time information 132 is information indicating the date and time the part was produced. The actual value information 133 is information such as the number of parts produced.

[0061] The finished product information 140 consists of finished product identification information 141, occurrence date and time information 142, and actual value 143. The finished product identification information 141 is an identifier for identifying the finished product produced in the work. The occurrence date and time information 142 is information indicating the date and time the finished product was produced. The actual value information 143 is information such as the number of finished products produced in the work.

[0062] Machine information 150 consists of machine identification information 151, occurrence date and time information 152, and actual value 153. Machine identification information 151 is an identifier for identifying the machine used in the work, for example, by which the type of machine such as a press machine, painting machine, or assembly machine is identified. Occurrence date and time information 152 is information indicating the date and time when the machine started work. Actual value information 153 is information such as the operating time of the machine.

[0063] The work procedure information 160 consists of work procedure identification information 161, occurrence date and time information 162, and actual value 163. The work procedure identification information 161 is an identifier for identifying the work procedure manual required for the work. The occurrence date and time information 162 is information indicating the date and time the work procedure manual was obtained. The actual value information 163 is information indicating the time required when the work is performed according to the work procedure.

[0064] Next, an example of the connection relationships between the information that constitutes the definition information 300 (definition information 400) after it has been connected by the connection information 314 (connection information 414) will be explained. These connection relationships are stored in the relationship data storage unit 15. Figure 8 illustrates an example of the connection relationships between the various pieces of information that make up the definition information 300 (definition information 400) after they have been connected by the connection information 314.

[0065] As shown in Figure 8, each piece of information constituting definition information 300 (Figure 4) or definition information 400 (Figure 5) (for example, business information 310 and worker information 320, business information 310 and part information 330, etc.) is linked by relationship information 500. This relationship information 500 is generated when the connection information 314 (414) of the business information 310 (410) of the definition information 300 (400) described above is expanded on the database.

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

[0067] Relationship identification information 501 is information that defines the connection relationships between each piece of information. For example, it is identification information that defines the relationship between business information 310 and parts information 330, or the connection between business information 310 and worker information 320. In other words, relationship identification information 501 can be said to be an identifier that identifies the connection lines between each piece of information.

[0068] The relational data access information 502 is information that includes memory addresses and other information for accessing the logic that defines the connection relationships of each piece of definition information 300 (400) stored in a database separate from the relational data storage unit 15 (information collection and display system 1). The logic applied by this relational data access information 502 performs the process of defining the connection relationships of each piece of information. Here, logic refers to information such as flowcharts that define the process for connecting one piece of information with other pieces of information. In other words, relational data access information 502 can also be said to be information that shows the meaning of the connections 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 starting point of a predetermined piece of information (e.g., part information 330) and information that defines the ending point of other information (e.g., business information 310) related to the predetermined piece of information. This allows the starting and ending points of the predetermined piece of information (e.g., part information 330) and the other information (e.g., business information 310) to be determined, and the direction of the connection line is determined.

[0070] This relationship information 500 links all the information that constitutes the definition information 300 (400). An example of relationship data 200, which specifically links each piece of definition information 300 (400) using this relationship information 500, is shown in Figures 9 and 10.

[0071] In Figures 9 and 10, a predetermined task 700 is centrally linked to the preceding task 710 and the subsequent task 720. Furthermore, each of the tasks 700, 710, and 720 is connected to various pieces of information, such as machines and workers, through relational information 500, each with a predetermined relationship. Note that in Figures 9 and 10, only some of the relational information 500 connecting each piece of information is shown for illustrative purposes; in reality, it is set for all connections between each piece of information.

[0072] In the embodiments described above, we illustrated and explained a case where multiple tasks are connected linearly (in a line), and information such as parts and machinery is associated with each task. However, it is also possible that information associated with one predetermined task is associated with multiple other tasks, and that each piece of information associated with multiple tasks is associated with one predetermined task. Furthermore, when multiple tasks exist in a manufacturing process, it is possible that the tasks are not directly connected by the aforementioned relationship information 500, but rather are connected to other tasks through the information associated with each task.

[0073] Figure 11 is a schematic diagram illustrating only the connection relationships of each piece of information (node) in the related data 200. It illustrates a case where a component B node 1010 associated with a predetermined business B node 1011 is used as input for multiple other business nodes (business C node 1020 and business E node 1030), and where a component D node 1061 generated in business D node 1060 and a component F node 1071 generated in business F node 1070 are used as input for business G node.

[0074] As shown in Figure 11, when task B (node ​​1011), which corresponds to the preceding process, is performed, multiple parts B (node ​​1010) are produced, and these multiple parts B (node ​​1010) are used as materials for tasks C (node ​​1020) and E (node ​​1030), which correspond to the subsequent processes. Furthermore, in task G (node ​​1040), it can be seen that part D (node ​​1061) produced in task D (node ​​1060) and part F (node ​​1071) produced in task F (node ​​1070) are used as materials to produce the finished product 1080. In this case, in the operational data access information 313 that constitutes the operational information 310 shown in Figure 4 above, multiple parts B may be managed as a lot (i.e., multiple parts B are assigned one identifier), or a single part B may be managed as an individual item (i.e., one part B is assigned one identifier). For example, if part B is managed by lot, part B will be used in lot units in operations D and E. If part B is managed individually, part B will be used individually in operations D and E.

[0075] Note that the connection relationships of the information constituting the related data 200 are not limited to those illustrated in Figure 11; for example, as shown in Figure 12, multiple information nodes may be associated with a single business node.

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

[0077] Furthermore, as shown in Figure 13, a connection relationship may be established in which parts produced in a designated task are returned to the designated task via other tasks for use.

[0078] In this embodiment, part A (node ​​1210), produced in the subsequent process C (node ​​1250), is input as material for process E (node ​​1260), and part B (node ​​1220) is output as a finished product. Part B (node ​​1220) is then input again as material for process C (node ​​1250). This illustrates a process in which a finished product is produced via a manufacturing line composed of processes A, B, C, and D, all of which share the same identification information. In process C (node ​​1250), part A is output once as part A (node ​​1210), and as a result of processing in process E (node ​​1260), part A is transformed into something equivalent to part 1 (node ​​1230), and process C is then performed again. For example, process C may be an inspection process, and as a result of the inspection, if there is a quality problem, the product is removed from the line, corrected in process E, and then the process is repeated from process C. The business nodes in the diagram represent manufacturing processes that have identification information indicating a specific finished product. When the same identification information passes through the same business, it is entered into the business node created so far, in this case business C (node ​​1250). Since the same identification information for a part has been entered into business C (node ​​1250) multiple times, the system stores that it has been entered multiple times as operational data, or it stores that it has been entered multiple times in the aforementioned extended information 470 (see Figure 5).

[0079] [Model data creation screen] Next, an example of the model data creation screen 600 by the relationship data model creation unit 10 will be explained using Figure 14. This model data creation screen 600 is displayed on a display or the like, which is an example of a user interface 7 connected to the relationship data model creation unit 10. The user creates model data for the manufacturing process while viewing this model data creation screen 600.

[0080] As shown in Figure 14, the model data creation screen 600 is composed of a business candidate subscreen 610 that displays a list of business candidates, a location subscreen 620 that shows which manufacturing plant the manufacturing process will be carried out at, a line subscreen 630 that shows overall information about the manufacturing lines (businesses) within the manufacturing plant, a data model display subscreen 640 that defines the relationships for a given manufacturing line (business), and a node definition information subscreen 650 that defines the property values ​​of the nodes of a given manufacturing line (business) displayed on the data model display subscreen 640.

[0081] The business nodes (business node 1 to business node 16) registered in the business candidate subscreen 610 are pre-registered as system information and are pre-configured according to the user's business content. The line subscreen 630 allows the user to define the process sequence of each business in the manufacturing process by sequentially connecting each business node using the business nodes 1 to 16 displayed in the business candidate subscreen 610. Each business node 1 to 16 is associated with the aforementioned 4M node, and the details of the 4M node and the business node are entered using the data model display subscreen 640 and the node definition information subscreen 650. The node definition information subscreen 650 allows the user to selectively switch between the business property screen 651 for setting the properties of business nodes and the 4M property screen 652 for setting the properties of 4M nodes.

[0082] In this embodiment, since the business 1 node is selected in the line sub-screen 630 (see the colored section in Figure 14), the data model display sub-screen 640 associates various pieces of information such as parts and workers with the business 1 node. Furthermore, since the business 1 node is selected in the data model display sub-screen 640 (see the colored section in Figure 14), the business properties 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 (e.g., January 1, 2018, 8:30 AM) and application end date and time (e.g., March 31, 2018, 5:30 PM). When changing the property values ​​of business 1 node and using a new business 1 node, the application end date and time of the previous business 1 node can be matched with the application start date and time of the new business 1 node, and the new business 1 node can be updated by revising it.

[0083] Here, when a 4M node such as a worker node or a machine node is selected in the data model display subscreen 640, the properties of the selected 4M node are displayed in the 4M properties screen 652. In Figure 15, the difference is that the machine candidate subscreen 653 is displayed in the same location as the business candidate subscreen 610 in Figure 14. The machine candidate subscreen 653 displays a list of pre-registered machine nodes, and one machine node selected from this list can be assigned to the machine node in the node definition information subscreen 650. In this embodiment, machine node 2 is selected from the machine node list (see colored section in Figure 15) and assigned to the machine node in the node definition information subscreen 650.

[0084] Furthermore, the node definition information sub-screen 650 allows the user to set the property values ​​of the selected machine 2 node, and allows the user to input and set the machine node name (e.g., machine 2 node), application start date and time (e.g., January 1, 2018, 8:30 AM), application end date and time (e.g., March 31, 2018, 5:30 PM), machine ID (e.g., M002), and access key (e.g., ZZ-XXXX-M002). The access key is used to access the database where the operational information of the 4M node (e.g., machine node) is stored. Based on this access key, the relationship data registration unit 11 can obtain the operational information of the specified 4M node from the database.

[0085] [Relationship data registration process] Next, we will explain the processing flow until the relevance data 200 is registered in the relevance data storage unit 15.

[0086] Figures 16 and 17 are flowcharts illustrating the processing flow until the related data 200 is registered in the related data storage unit 15.

[0087] First, in each manufacturing process (operation), the data generation device 5 collects or generates on-site data 100 (step S101), and then transmits this on-site data 100 to the information collection and display system 1 via the network 2 (step S102).

[0088] In the information collection and display system 1, upon receiving field data 100 (step S103), the related data registration unit 11 acquires the identification information contained in the received field data 100 (identification information 111, 121, 131, 141, 151, 161 shown in Figure 7) (step S104), and also acquires definition information 300 (or 400) corresponding to each acquired identification information from the related data model creation unit 10 (step S105). The related data registration unit 11 also determines whether the definition information 300 (or 400) acquired from the related data model creation unit 10 is business information 310 (410) or 4M information such as other worker information 320 (420), part information 330 (430), machine information 350 (450), or work procedure information 360 (460) (step S106).

[0089] If the related data registration unit 11 determines that the acquired definition information 300 (400) is business information 310 (410) (step S106: Yes), it searches the related data storage unit 15 for the business node corresponding to the business information 310 (410) (step S107). If the related 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 the acquired identification information and definition information 300 (or 400) (step S109). If the related 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 the occurrence date and time information (e.g., 112, 122, 132, 142, 152, 162) contained in the field data 100 for the generated business node and registers it in the relationship data storage unit 15 as the start information for the generated business node (step S110). The relationship data registration unit 11 then updates the property values ​​of the business node, for example, the data in the extended information 470 (step S111).

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

[0092] The relationship data registration unit 11, after a connection line from a business node is established, retrieves information for generating a connection line (connection line information) stored in the temporary storage unit 18 and constructs the connection line (step S115). If no connection line information is stored (step S116: No), this process ends. If 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 its properties until it determines that no connection line information is stored in the temporary storage unit 18. Also, if the relationship data registration unit 11 determines in step S112 that no connection destination exists (step S112: No), it stores the connection line information in the temporary storage unit 18 (step S117) and terminates this process.

[0093] Returning to Figure 16, in step S106, if the related data registration unit 11 determines that the identification information obtained from the field data 100 is 4M information different from business information (step S106: No), it searches the related data storage unit 15 for the 4M information corresponding to the identification information (step S118). If the related data registration unit 11 determines that the 4M information corresponding to the identification information is stored in the related data storage unit 15 (step S119: Yes), it updates the property value (step S120) because the 4M information was already registered as existing when the manufacturing process was built, and proceeds to step S112. If it determines that the 4M information does not exist (step S119: No), it discards the field data 100 received from the data generator 5 (step S121) and terminates this process.

[0094] [4M information generation and registration process] Next, the generation and registration process of 4M information by the related data registration unit 11 will be explained. Of the aforementioned 4M information, worker information, machine information, and work procedure information are predefined by the user when introducing the manufacturing process, and are not generated each time a predetermined process is performed, unlike business information. Although work shifts may change depending on the predetermined work unit, the workers themselves are registered in this information collection and display system 1, and the machines used to perform the work are also determined and installed when the work begins. Therefore, this information is pre-registered from the field data before the information collection and display system 1 starts normal operation.

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

[0096] First, the relationship data model creation unit 10 generates relationship data configuration information (definition information 300 or 400) based on the master data stored in the master data storage unit 3 (step S201), and transmits this generated configuration information to the relationship data registration unit 11 (step S202). The relationship data registration unit 11 receives the configuration information transmitted from the relationship 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 relationship data storage unit 15 (step S205). In this way, the relationship data registration unit 11 can generate 4M information according to the configuration information received from the relationship data model creation unit 10 and register this 4M information in the relationship data storage unit 15.

[0097] [Relevance Data Extraction Process] Next, we will explain the process of extracting related data in the related data search unit 12.

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

[0099] First, the user uses the data extraction tool 800 displayed on the user interface 7 to input the period, scope of work, etc., into the input form 802 to identify the range from which to extract the relevant data 200 (step S301). The relevant data search unit 12 displays multiple business nodes 801 in the manufacturing process that are to be extracted from the relevant data 200 extracted based on the identified range (step S302). The user selects the node they want to search for from the displayed business nodes 801 (for example, machine 2 node shown in Figure 23) (step S303), and the relevant data search unit 12 displays a list of actual value names associated with the node selected by the user (step S304). In this embodiment, based on the user's selection of machine 2 node, the relevant data search unit 12 displays a list of actual value names for items 10 to 14 related to machine 2 node.

[0100] Next, the user selects one item from the list of actual values ​​(for example, item 12 shown in Figure 23) (step S305), and a sample of the extracted related data is displayed on the data display subscreen (not shown) at the bottom of the data extraction tool 800 screen (step S306). The user repeats steps S301 to S306 multiple times until they have extracted a list of data items that are necessary for data analysis and that the user has determined to be related (step S307: No). Once the selection is complete (step S307: Yes) and the process is executed, the related data search unit 12 retrieves 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] Figure 20 is a flowchart of the process for storing user-defined data in the related data storage unit 15. The process for extracting user-defined data (steps S401 to S408 shown in Figure 20) follows the same flow as the flowchart explained in Figure 19. The process from analyzing the related data extracted by ETL (Extract / Transform / Load) to displaying the analysis results is defined. A connection line for related data is constructed between the data necessary for analysis by ETL, and an access key that calls the logic defined by ETL is registered in the access information.

[0102] [Data Analysis Processing] Next, we will explain the data analysis process performed by data analysis tools such as Application 8 based on the data mart (analysis data) created by the processing in steps S301 to S308 (or steps S401 to S408).

[0103] Figure 21 is a flowchart illustrating the data analysis process performed by a data analysis tool such as Application 8 based on the data mart (analysis data) created by the processing in steps S301 to S308 (or steps S401 to S408). This data analysis process is carried out by Application 8 analyzing the analysis data stored in the analysis data storage unit 14.

[0104] Application 8 (data analysis tool) retrieves the data mart extracted and stored in the analysis data storage unit 14 through the processes described in steps S301 to S308 (or steps S401 to S408) (step S501). The user of the data analysis tool displays the retrieved data on the screen using the data analysis tool and performs data analysis (step S502).

[0105] [Data generation process for analysis] Next, we will explain the process of generating data for analysis using the data provision API unit 16.

[0106] Figure 22 is a flowchart of the data generation process for analysis by the data provision API unit 16.

[0107] First, application 8 instructs the data provision API unit 16 to search for relevant data 200 necessary for generating data for analysis (step S601). Specifically, application 8 sends a search key to the data provision API unit 16 to search for the necessary relevant data 200. The data provision API unit 16 uses the search key obtained from application 8 to search for the relevant data 200 from the relevant data storage unit 15 (step S602). The data provision API unit 16 obtains data access information for the obtained relevant data 200 (step S603) and sends this information to the storage data acquisition unit 13 (step S604). Based on the received data access information, the storage data acquisition unit 13 obtains the transaction data to be acquired from the transaction data storage unit 4 (step S605). The storage data acquisition unit 13 sends the acquired data to the data provision API unit 16 (step S606). The data provision API unit 16 formats the acquired data and sends it to application 8.

[0108] [Data Extraction Tool] Next, we will describe the data extraction tool 800 displayed on the user interface 7, such as a display. The user can easily extract relevant data 200 visually using the data extraction tool 800 displayed on the user interface 7.

[0109] Figure 23 illustrates an example of a data extraction tool 800 displayed on a user interface 7, such as a display. In Figure 23, each node and connecting line of the related data registered in the related data storage unit 15 is represented by circles and lines.

[0110] An input form 802 is provided at the top of the screen of the data extraction tool 800, where the search range for the required related data 200 is entered. At the bottom of the screen of the data extraction tool 800, multiple business nodes 801 corresponding to the entered search range are displayed. In these business nodes 801, the related data 200, constructed with circles and lines, can display data items 803 registered in the node. If it is a machine node, this data item 803 displays the actual value name of the machine node and is obtained from the master data storage unit 3. The actual value name obtained from the master data storage unit 3 is converted by the dictionary database 6 from the name managed by the machine that the machine node is targeting to a name that is easy for the user to recognize. The hatched parts of the data items are the data specified by the user and the data related to the specified data, and the hatching display is performed by the process shown in Figure 19.

[0111] For example, using the data extraction tool 800, the user inputs the period, scope of work, etc., from the input form 802 to identify the range from which to extract relevant data 200 (step S301 in Figure 19). The relevant data search unit 12 then displays multiple business nodes 801 in the manufacturing process that are to be extracted from the relevant data 200 based on the identified range (step S302 in Figure 19).

[0112] The user selects a node they want to search for (for example, machine 2 node) from the displayed business nodes 801 (step S303 in Figure 19), and the related data search unit 12 displays a list of actual value names (data items 803) associated with the node selected by the user (step S304 in Figure 19). In this embodiment, based on the user's selection of machine 2 node, the related data search unit 12 displays a list of actual value names for items 10 to 14 related to machine 2 node.

[0113] Next, when the user selects one item from the list of actual values ​​(for example, item 12) (step S305 in Figure 19), the related data search unit 12 searches for item 4 of machine 1 in other operations 2 that is related to item 12 selected by the user, and displays it using hatching or other methods, thereby extracting item 4 related to item 12. Similarly, when the user selects item 14 of machine 2 node, the unit searches for item 6 of machine 1 in other operations 2 that is related and displays it using hatching or other methods. This makes it easy to visualize the results of searching for items (second information) in other operations that are related to the selected item (first information) of a given operation, making it easier to perform subsequent relationship analysis.

[0114] As described above, in this embodiment, the information collection and display system 1 is connected to a data generation device 5 that generates field data 100 and a transaction data storage unit 4 that stores the field data 100 generated by the data generation device 5, A relationship data storage unit 15 stores relationship data 200 that defines the relationships between each of the multiple pieces of information contained in the field data 100, The system includes a relationship data retrieval unit 12 that searches for other 4M information (second information) related to a predetermined 4M information (first information) included in a plurality of pieces of information based on relationship data 200 stored in a relationship data storage unit 15, and a user interface 7 that displays the connection relationships of the plurality of pieces of information linked by the relationship data 200. The related data search unit 12 searches for second information related to the first information based on the related data 200, in response to the selection of the first information in the connection relationships of multiple pieces of information displayed on the user interface 7, and displays the first information and the second information together with the connection relationships of the multiple pieces of information on the user interface 7.

[0115] With this configuration, the information collection and display system 1 only needs to generate and manage relationship data 200 as definition information that defines the connection relationships of the field data 100. It does not need to store data that associates all of the field data 100, and the storage device that stores the relationship data 200 can be made small in capacity. In addition, the information collection and display system 1 searches for second information related to a first piece of information for a given task by selecting first information from the user interface 7, and displays the first and second pieces of information together with the connection relationships of the field data 100 on the user interface 7, making it easy to analyze the relationships visually.

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

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

[0118] Furthermore, some of the configurations of the embodiments described above may be added to, deleted from, or replaced with those 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 generator, 6: Dictionary database, 7: User interface, 8: Application, 10: Relationship data model creation unit, 11: Relationship data registration unit, 12: Relationship data search unit, 13: Stored data acquisition unit, 14: Data storage unit for analysis, 15: Relationship data storage unit, 16: Data provision API unit, 17: Comparison data definition unit, 18: Temporary storage unit, Relationship 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 processing unit for processing field data related to operations, and a related data storage unit for storing the data processed by the processing unit, The system is connected to a data storage device that stores the field data, The aforementioned processing unit, Based on definition information including information regarding the types of field data and information regarding the connection relationships between the field data, the type of the field data is determined. Based on the determined type of the field data and the definition information, the field data is associated with other field data, and relationship data is generated, including access information to the data storage device where the field data of which type has been determined is stored. The aforementioned relationship data is stored in the relationship data storage unit. system.

2. Among the multiple tasks included in the process, a specific task is defined as taking one or more input objects as input and outputting one or more output objects each time that task is performed. The subsequent task among the aforementioned predetermined tasks is defined as using the output target output by the preceding task as the input target. Each of the aforementioned tasks, which each performs one or more of, is assigned a unique output identifier for each of the aforementioned output targets, both for each task and for each target. The input identifier for the input target is defined as the output identifier assigned to the output target, which is the output of the previous business process, and is used as the input target. The definition information defines, for each of the multiple operations, a type of information that includes one or more input targets and output targets related to each of the multiple operations. The system according to claim 1.

3. The aforementioned definition information includes, in the type of on-site data, worker information, machine information, work procedure information, parts information, and finished product information. The processing unit determines, from the field data, that the input identifier corresponds to the part information and the output identifier corresponds to the finished product information. The system according to claim 2.

4. The aforementioned definition information includes, as the type of field data, business information that defines the content of the business, The system according to claim 2 or 3.

5. The aforementioned business information includes the start date and end date and time for each instance in which the aforementioned business is performed. The processing unit receives input of search conditions including a period, and extracts relevant data related to the business that falls within the period, based on the start date and time and end date and time included in the business information, from the relevant data. The system according to claim 4.

6. A system including a processing unit for processing field data related to operations and a related data storage unit for storing the data processed by the processing unit, wherein a program causes the processing unit to process the field data, The system is connected to a data storage device that stores the field data, The program instructs the processing unit to: Based on definition information including information regarding the type of field data and information regarding the connection relationships between the field data, the type of the field data is determined. Based on the determined type of the field data and the definition information, the field data is associated with other field data, and relationship data is generated, including access information to the data storage device where the field data of which type has been determined is stored. The relationship data is stored in the relationship data storage unit. program.

Images